yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
Oh.. No.. This issue appeared when i changed my theme.. Able to get back tiles by adfing a tile.. All tiles are visible again.. For sure something is messed up.. You are right.
[ONE Q&A, Help & Troubleshooting] indesisiv:
I have all the tiles I use still there. I updated from the 18/01 nightly to the 19/01.
[ONE Q&A, Help & Troubleshooting] giaur:
Visible again.... try to reboot :) and don't apply any custom theme
[ONE Q&A, Help & Troubleshooting] elmer_fudd:
I use Euphoria Dark CM13 Theme. Works like a charm. No problems with the tiles.

I flash every nightly.
[ONE Q&A, Help & Troubleshooting] fards:
Can you try a different scheduler?

bfq is default, suspect that might be causing that one.
[ONE Q&A, Help & Troubleshooting] AcmE85:
If you mean ok with showing tiles, then yes it was ok with yesterday's nightly.

But a 3x3 layout was not possible on yesterday's nightly.

I want my tiles this way:

but this is what I got on 01/18:

As you can see, I have more tiles on the second page. But there should be three tiles at the bottom -> BUG

I asked about this a week ago. Nobody replied so I did a clean flash which did not help up until today's nightly.

All fine now and 3x3 is working again.

I don't get why you are quoting me though, when I was clearly acknowledging your point that

Against this post here

As you can see on my description, tiles did

not work

as intended before.

Also, tiles were fine 2 weeks ago

but

switching themes was buggy and caused the tiles/status bar not to be updated until reboot or triggering a system ui force close by tapping the "mute"-tile.

They fixed the themes but messed up the tiles layout -> 3x3 not possible. I guess they will fix each bug one at a time, I don't worry that much ;) they are already working on this http://review.cyanogenmod.org/#/c/128894/
[ONE Q&A, Help & Troubleshooting] giaur:
Seems themed users are not affected this time, but issue is serious
[ONE Q&A, Help & Troubleshooting] hypern0va:
EDIT: Useless post.
[ONE Q&A, Help & Troubleshooting] akuma48465:
I did today a clean install of cm 2016/01/19 and tiles are gone, after read some users that doesnt have problems with titles when they update from cm 2016/01/18 to cm 2016/01/19, I flash cm 2016/01/18 first boot the system and then update to cm 2016/01/19 but the problems persist so I will wait to cm 2016/01/20 nightly
[ONE Q&A, Help & Troubleshooting] AcmE85:
Pull down status bar, longpress the settings button for a couple seconds and let go.

Now scroll to the very left and disable/enable or enable/disable "Enlarge first row".

Tiles should be back now.
[ONE Q&A, Help & Troubleshooting] giaur:
But will disappear after reboot. I would not expect any fix on 20.01 nightly. Please vote bug report
[ONE Q&A, Help & Troubleshooting] AcmE85:
That's where you are wrong. I can tell you that with the way I posted, the tiles did not disappear after a reboot with stock theme. Only with a custom theme. I just tested this once again with the stock theme to be sure. Tiles are still there after a reboot.

The commit I linked to will fix it with custom themes.

I voted btw

edit: I just did another reboot with Liv Theme applied and the tiles are still there and 3x3. All good here.
[ONE Q&A, Help & Troubleshooting] giaur:
I tried the same and tiles were gone after reboot. Stock theme. Bug confirmed on jira, let's wait for fix.
[ONE Q&A, Help & Troubleshooting] Elius2676:
Doing this for my boy, Ray Walters, who said, "The next time someone says that CM doesn't care, would you point them to this thread?" So here you are, man:

http://forum.cyanogenmod.org/topic/119253-spontaneous-reboots-with-cm13-601/page__st__180

If you don't feel like they're doing anything, feel free to read this thread and see how the community (read: users willing to help fix the problem and not just complain about it) and CM worked together to get these spontaneous reboots fixed. It took a while, yes, and I was afflicted with these reboots for over a month, but we got it done!

Also, you realize they're not purposely breaking things just to have to fix them, right?

Also, also, you realize you signed yourself up for bugs when you started flashing nightlies. So if you have a problem with them, it's your problem, not CM's. Don't come here just to complain - just gets in the way. Stick with your 12.1 and just wait. Best thing you can do for CM and its users is stay out of the way.
[ONE Q&A, Help & Troubleshooting] giaur:
Calm down, dude. Reboots are fixed and qs tiles bug annoyed many people, are you really suspected?

Also their priorities may be hard to understand: gps is broken, 3rd party cameras support are broken (actually, camera api) - 2 year old bug with flash and last time they "stabilized camera", they broke viewfinder also and not going to fix that. Instead of focusing to remaining serious bugs, they give us new gift, broken qs tiles.

Of course, still their hard work definitely should be appreciated.
[ONE Q&A, Help & Troubleshooting] aliffaminuddin:
i recommend you guys to go switch back to cm12. 1, im using it currently and it has like 0 issues. here is the link http://xdaforums.com/oneplus-one/development/rom-continuing-cm12-1-builds-patches-t3288460 it is build with latest patches, and all that good stuff. just pure cm12.1. im lovin it lol take a look :)
[ONE Q&A, Help & Troubleshooting] giaur:
This should resolve qs tiles bug: http://review.cyanogenmod.org/#/c/128894/
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
Yes

---------- Post added at 02:40 AM ---------- Previous post was at 02:38 AM ----------

Any idea on this commit

http://review.cyanogenmod.org/#/c/128876/

bacon: Re-introduce old-modem hack

We're reverting to an older modem for now.
[ONE Q&A, Help & Troubleshooting] Brian325:
Not sure why...new modem seems fine to me
[ONE Q&A, Help & Troubleshooting] JG:
to fix issue with T-Mobile users

I seen this comment

Jake Weinstein

6:35 PM

↩

Patch Set 1:

Why? What's broken on the new modem and blobs?

Abhisek Devkota

7:35 PM

↩

Patch Set 1:

Everything tmobile
[ONE Q&A, Help & Troubleshooting] Brian325:
I'm a T-Mobile user...all good here
[ONE Q&A, Help & Troubleshooting] JG:
So am I.

However 3 out of 5 calls wont go through or takes a long time to connect. and incoming goes straight to voicemail about the same 3 out of 5 calls without ringing through to the phone.

Issues started on after new baseband.

There is alot of reports from T-mobile users on various forums throughout the internet.
[ONE Q&A, Help & Troubleshooting] Brian325:
I've seen people reporting issues. Very strange. I haven't had a single problem
[ONE Q&A, Help & Troubleshooting] detted:
I am a t-mobile user as well in NE, US. The modem (.4.0.1.c7.00011) works very well without any issue, better than the last (242)
[ONE Q&A, Help & Troubleshooting] JG:
you are the lucky few I guess,We are not talking about data.Talking about phone calls BTW.
[ONE Q&A, Help & Troubleshooting] Brian325:
Never missed a call or dropped a call. All text and MMS work perfect too. I saw a noticeable increase in signal at my house with new firmware.
[ONE Q&A, Help & Troubleshooting] detted:
Same here.
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Are you on cyanogen nightlies or a build from someone else? Modem doesn't work on T-Mobile for calling in Texas on nightlies.
[ONE Q&A, Help & Troubleshooting] Brian325:
Now I'm on a CM nightly. But I've used it with self compiled AICP as well with no problems.

---------- Post added at 03:03 AM ---------- Previous post was at 03:01 AM ----------

I do live in Seattle and T-Mobile has a pretty hot service here. Their headquarters is here lol
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Strange, it definitely affected my calling, but not my text messages. Are you sure calling is ok on your phone? Have you tried calling someone?
[ONE Q&A, Help & Troubleshooting] Brian325:
Yes calling is fine. Been using new modem since the first nightly that included it. I can't handle bugs like that, if I had issues I would have went back to old modem
[ONE Q&A, Help & Troubleshooting] tiny4579:
Regardless of this discussion, the nightly will revert the modem. T-Mobile users with this issue can enjoy nightlies as is when the build comes.

And it built. It will be up soon. Jenkins shoes it as the last successful build.
[ONE Q&A, Help & Troubleshooting] Brian325:
Agreed.
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Yep.. I've been enjoying the newer nightlies by flashing the 241 modem firmware on top:cool: This just saves me a step.:good:
[ONE Q&A, Help & Troubleshooting] Elius2676:
I've not had the T-Mobile issue (or at least I haven't noticed it). Though, I'm a Google Voice user. Would that make a difference?
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Yes, because you are using wifi to make calls.
[ONE Q&A, Help & Troubleshooting] Elius2676:
But I'm not. I'm using cellular connection when making calls, not data/wifi. It just routes through Google so that the receiving end gets a call from my GV number, not my T-Mo one. And vice versa, the calls to my GV are forwarded to my T-Mo.
[ONE Q&A, Help & Troubleshooting] JG:
lets just say it affects enough of us to warrant a fix. and be done with the subject.I am glad they are addressing it.

Build is up so go get it http://www.cmxlog.com/13/bacon/
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
01/20 build up and running great.
[ONE Q&A, Help & Troubleshooting] geekasm:
I flashed 1.20 over 1.19. I dont see any cellular service on my phone :( any workaround ?

I am in Vodafone, India
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
What is the Modem? is it 241?
[ONE Q&A, Help & Troubleshooting] :
Reboots are back again :(
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Yep.
[ONE Q&A, Help & Troubleshooting] sona911:
Just got one also myself after updating to 20/01.
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Reboots are going to be back because they are also tied to the older modem. If you want to get rid of the reboots flash https://www.androidfilehost.com/?fid=24351979186684130 after flashing the new nightly.
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
Sad but expected ..They should have fixed tiles issue with today's Nightly and go for base band change on Next nightly.
[ONE Q&A, Help & Troubleshooting] :
Exactly the same for me, back to 18th nightly. Reboots due to this modem issue are really bad
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
Probably clean Install will fix the reboots issue?
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
Just flash the zip I posted. It fixes the issue on the new nightly.
[ONE Q&A, Help & Troubleshooting] sona911:
Reverted back to CM13 modem. Let's see how it goes.
[ONE Q&A, Help & Troubleshooting] giaur:
Lol, again .241 modem, really? There must be some good reason if they downgrade it again to older version
[ONE Q&A, Help & Troubleshooting] AcmE85:
How about the proximity sensor, does it still work?

Also the respective blobs for the baseband have been updated and the hack for 241 is back in place,

which might cause other issues, I don't know...

I guess I will wait for another baseband and stay on 01/19 which is running fine for me right now.
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
It should if you flash the new modem. I'm not sure since I've been having to flash the 241 modem over every nightly since they changed basebands anyway, due to the T-Mobile issues. I hope they get a newer modem that fixes everything from Oppo soon.
[ONE Q&A, Help & Troubleshooting] geekasm:
how to check modem version ?
[ONE Q&A, Help & Troubleshooting] AcmE85:
At least on older nightlies which still came with 241, flashing an updated baseband from hydrogen os, including this one, caused the proximity sensor to stop working.
[ONE Q&A, Help & Troubleshooting] sona911:
Proximity sensor is working.
[ONE Q&A, Help & Troubleshooting] scormax:
notification drawer prob still exists in 1.20 build.. any workaround?
[ONE Q&A, Help & Troubleshooting] AcmE85:
http://xdaforums.com/showpost.php?p=64887944&postcount=2649

This worked for me on yesterday's nightly with no issues since doing this.
[ONE Q&A, Help & Troubleshooting] giaur:
LOL they closed qs tile bug, but there is nothing fixed. Still no tiles on 20th nightly. Also, reboot 2 minutes after boot. Everything messed up. 18.01 nightly is latest not broken.

---------- Post added at 08:14 AM ---------- Previous post was at 08:11 AM ----------

So basically, nothing changed and nothing fixed. The same behaviour as before
[ONE Q&A, Help & Troubleshooting] raiashu92:
241 modem back and SEpolicy set to permissive in 20/01 nightly. I understand the modem reason but why sepolicy? Reboots were already solved werent they? I last had reboots on 06 nightly.

---------- Post added at 08:15 AM ---------- Previous post was at 08:14 AM ----------

seems like 18th is the best.
[ONE Q&A, Help & Troubleshooting] giaur:
Reboots was fixed but again broken since 20.01 nightly.
[ONE Q&A, Help & Troubleshooting] aliffaminuddin:
its time to turn back to cm12.1 for now ay mate????
[ONE Q&A, Help & Troubleshooting] giaur:
No, just install 18.01 nightly. 18.01 nightly + known GPS Fix is stable, the same as CM12.1. It's funny how they made all things broken on newer nightlies.
[ONE Q&A, Help & Troubleshooting] aliffaminuddin:
yeah funny i decided to switch to cm12.1 and im living my life to the fullest without any problem lol
[ONE Q&A, Help & Troubleshooting] AcmE85:
It's fine and we all respect your decision, but this is the Q&A section for "Official CM13 nightly builds for OPO".

I don't go into other rom threads and tell people that this or that rom is better...

Live your life and stop spamming this thread with cm12.1. peace^^
[ONE Q&A, Help & Troubleshooting] giaur:
Yes, you can but note that cm12.1 is now abandoned, so there are no new security patches.
[ONE Q&A, Help & Troubleshooting] aliffaminuddin:
theres a cm12.1 rom build with latest patches, you can check it out http://xdaforums.com/oneplus-one/development/rom-continuing-cm12-1-builds-patches-t3288460 my android security patches are from 1st of january.

---------- Post added at 03:49 PM ---------- Previous post was at 03:47 PM ----------

yeah mate just wanna point out opinion and save these people from getting broken cm13 lol have a nice day
[ONE Q&A, Help & Troubleshooting] the Doctor:
Great. I hope this means the end of off-topic discussion then. :good:
[ONE Q&A, Help & Troubleshooting] scormax:
i hate reverting back to older builds..rather will follow this workaround for a while.. thanks acme
[ONE Q&A, Help & Troubleshooting] giaur:
Better hold on and wait for new baseband again.
[ONE Q&A, Help & Troubleshooting] Crazy_Oni:
Im on 20150120 and everything works fine. Bluetooth with mi band works and the tiles are all there.

Since I applied my custom theme the times were back. On stock cm theme they are gone.

Gesendet von meinem A0001 mit Tapatalk
[ONE Q&A, Help & Troubleshooting] raiashu92:
No reboots till now. On 20.01 for 5 hours with boeffla 15.01. Call/gaming/chat all were working fine. Only that QS tile bug found till now, lets see further :fingers-crossed:
[ONE Q&A, Help & Troubleshooting] fards:
The c7 and c1 modems break quite a lot of 2100hz hspda connections
[ONE Q&A, Help & Troubleshooting] Pank9j:
Still facing issue with tiles on 20 Jan Build.
[ONE Q&A, Help & Troubleshooting] tiny4579:
See above. Just please read at least a few pages back next time as answers are likely answered multiple times.
[ONE Q&A, Help & Troubleshooting] tiny4579:
Sepolicy permissive shouldn't be needed as that commit got merged that addresses the need to do that.

I'd wait on 1/18 as others are doing.
[ONE Q&A, Help & Troubleshooting] giaur:
First they should reopen qs tiles regarding bug
[ONE Q&A, Help & Troubleshooting] Pank9j:
I did, Not worked for me.
[ONE Q&A, Help & Troubleshooting] akuma48465:
Random reboots are back on 2016/01/20 nigltly
[ONE Q&A, Help & Troubleshooting] giaur:
Maybe they reverted modem because of T-Mobile USA problems. And now, rest of the world will be hurting by random reboots.
[ONE Q&A, Help & Troubleshooting] raiashu92:
yes thinking of going back to 18th. should i clean flash? or just do dirty on 20th? The proprietary files and modem hack that they changed will be updated accordingly in dirty flash too, right?
[ONE Q&A, Help & Troubleshooting] giaur:
Dirty flash 20->18 worked for me. No issues
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
I did dirty flash from 19.01 --> 18.01... will report in case of any issues
[ONE Q&A, Help & Troubleshooting] giaur:
No issues too, already tested
[ONE Q&A, Help & Troubleshooting] payne_307:
I really want to start using the Official nightlies again. Have been on non-rooted AOSP CAF based ROM but last few days the battery & WiFi have been horrible (though I'm on the latest baseband for OPO for MM).

Unfortunately as nightlies are pre-rooted I will need to use Xposed and a mod to hide root from my official email client app. I hate to use Xposed for this but it seems I don't have any other option. I haven't kept track of the latest builds. Can someone answer me for the following -

1.) How bad is the ROM after using Xposed? Though I won't use more than 1 module which is just to hide root, still curious to know the impacts on doze and battery efficiency & bugs if any by just having Xposed framework running.

2.) Is the kernel wakelock/battery life bad since CAF 810 merger? I'm facing that in the AOSP based ROM I'm using

3.) Is WiFi stable during standby? I have an issue of WiFi getting disconnecting when left idle (or when doze has kicked in for a long period) and stays that way for hours before reconnecting or until I unlock the phone & toggle WiFi on & off again (clean flashed several times, but no luck)

4.) Is GPS accurate now indoors / outdoors on high accuracy mode?

5.) Does the flashable zip from Sultan's CM13 zip gets rid of the split exposure issue on other cams like Google Camera?

6.) Random reboots issue is resolved?

Please take out some time to give me some genuine suggestions. I would hate to go back to COS 12.1.1 after tasting MM on the OPO.
[ONE Q&A, Help & Troubleshooting] Renosh:
Look at the last two pages next time before wasting energy typing all this. Hint: stick to your current ROM, issues galore
[ONE Q&A, Help & Troubleshooting] payne_307:
Sorry mate. I did. Didn't find accurate answers to any except for few people saying GPS issue and random reboots are fixed while some others disagreeing. Rest I couldn't find or nothing more than generalized answers.
[ONE Q&A, Help & Troubleshooting] wistlo:
I really want to start using the Official nightlies again.

CM 13's reliability and function seem variable among users here. Here's my experience:

1). Went to Xposed for the first time ever in CM 13 to load a module to give me status bar traffic indicators. The new Marshmallow simplified signal-level-only WiFi indicator without traffic was slowly sapping my will to live. I'm using xPosed alpha v 78 for Marshmallow. "Alpha" is frightening, but it's been solid and trouble free.

2) Not following the CAF 810 merger timeline, but I went to CM 13 NIghtlies from the first release in late Nov. Battery life is significantly improved, especially when the screen is off. It's the best battery performance on the OPO yet.

3) WiFi for me was a mess in 12.1. Sleep for Android pulls some magic in the background that I suspect hosed up DCHP. CM 13 wifi has been better, particularly when roving around a house with two hotspots on the same LAN. Thoughput is excellent.

4) GPS has shown a few flaky instances that landed me in NE Kansas on startup (about 1000 miles away, appears to be some kind of national geographical center point). ONce GPS has a fix, it's been solid outdoors. Indoor performance is not great, though possibly marginally better than 12.1 and older. Very responsive in Maps and Waze.

5) Not tried Sultan's zip (yet). I use Camera FV-5, which has a flash workaround. SPlit flash problem still there for Google camera. It's disappointing that this problem continues.

6) Random reboots for me were horrible on Dec 9, in fact I posted the first note in the CYanogen forum about it. My reboot issues disappeared completely around 20151222 (sorry I don't have a more specific date). ROM has been reliable and reboot free since then. There seem to be a wide variety of experiences with the reboot issue, and for different reasons.

There are some nagging little problems in CM 13 that I'm tolerating. The BLE connection to Fitbits broke on 20160108, but a zip flash fix has been created for that. . QS Tiles developed an aversion to staying put with 20160119, but there's a workaround (System UI tuner, add any tile). The ROM works for me as a daily driver for phone conferences, text, camera, and daily driving (as in car). I'd say 12.1 from Aug-Nov 2015 was more stable overall, but the many improvements in 13 for me outweigh total stability.
[ONE Q&A, Help & Troubleshooting] Muralidharc22:
Yes, thanks. No issues after downgrade
[ONE Q&A, Help & Troubleshooting] giaur:
18.01 nightly is latest bugfree. No reboots and tiles are ok.

I suggest to download zip. There is no workaround for tiles bug, but that bug will be fixed soon.

Random reboot was fixed, but they decided to introduce it again, reasons why they did it are impossible to understand.

They also decided to don't answer any questions/reports saying that modem downgrade was not good idea and causes random reboots. Overall, there are no any reasons to be optimistic. Really, hold on and stick to 18.01 nightly, eventually let's see what are they going to do next (we don'y know that, because no response from them)
[ONE Q&A, Help & Troubleshooting] fmc000:
I abandoned CM long ago so I couldn't care less but to be fair the reason of the downgrade is explained here. They probably decided that a phone that can't make or receive calls is not acceptable ;)
[ONE Q&A, Help & Troubleshooting] payne_307:
Wow ... That's what I was looking for. A closest use case scenario. I use the phone almost 95% as you do so I get a fair understanding of what to expect now. I think for 5, only time will tell how it works. My only big worry always has been Xposed. First I hate anything that tinkers with ART libraries, but then I can't stop these freaks at my office who think the first think that happens with root is data piracy/theft and leave us with no choice but to use non-rooted custom ROMs or stick to outdated stock OS (one of the reasons I miss the Nexus line still). don't use Fitbits so I'm good there. Time to fire up the download zip for CM13 latest nightly. Its home coming finally.
[ONE Q&A, Help & Troubleshooting] giaur:
Do you mean T-Mobile USA issue? I have hsdpa 2100 in my country and no issues
[ONE Q&A, Help & Troubleshooting] detted:
Really don't understand why lucky without any issue with t- mobile and love the c7 modem. Can the modrm be extracted out, so one can pick to flash?
[ONE Q&A, Help & Troubleshooting] giaur:
Not really. Baseband other than the one included in nightly may be incompatible
[ONE Q&A, Help & Troubleshooting] The_cobra666:
This latest nightly is a complete mess. Wifi works like crap and makings calls is nearly impossible. Went back to 19. Instead of "fixing" the issue people had by reverting the newest baseband, they only made it much much worse.
[ONE Q&A, Help & Troubleshooting] giaur:
20.01 nightly again introduces reboots. From my tests, even worse than before. Definitely, not recommended. Avoid nightlies 20 and newer or you will be in a big troubles.

I suggest to wait for new baseband, but it won't be soon.
[ONE Q&A, Help & Troubleshooting] Thebarratt:
I have had one reboot since dirty flashing 0120, but overall I have not seen any significant problems.
[ONE Q&A, Help & Troubleshooting] fmc000:
Yup
[ONE Q&A, Help & Troubleshooting] giaur:
Hmm I antually don't care usa t-mobile but I do care random reboots.
[ONE Q&A, Help & Troubleshooting] BoboBrazil:
I posted above how to fix your reboots by flashing the newer baseband they removed. Either you get reboots or it doesn't work for most people on T-Mobile. Either way it's broken for someone.
[ONE Q&A, Help & Troubleshooting] TorchaOne:
For now since morning no problems with c7 modem and 20th day build. No reboots, only that higup with tiles. But everybody does what feels the best.