yashsingh1/xdaforums huggingface dataset:
[ONE General] Lupin The Third:
my first unintended reboot, while installing my apps from playstore.

Clean flash 0526 nightly, with slim's latest zero gapps.

Not a good start!

Edit: and the second! great!!!! :(
[ONE General] fmc000:
To the people experiencing unattended reboots: are you all on stock kernel? I ask this because I'm running Boeffla Kernel with zzmoove governor and I've never had the problem so far. The latest one has all the CM commits (plus many other functions, of course) and it works really well.

Another option could be trying to change the governor on stock kernel, maybe that will help.
[ONE General] giaur:
Stock kernel, no reboots
[ONE General] waterdaan:
+1
[ONE General] LeroViten:
No reboots on today's nightly. Only GooglePlaySevices FCing every time the location gets verified.

Had to set it to "device only" to be able to normally work with the device.
[ONE General] Tromzy:
Happened here too. Installed latest nightly, rebooted, no optimizing process. But the nightly seems running good. Weird...
[ONE General] 19deimon90:
Settings, apps, all, Google Play services, manage spade, clear all data. This should work.
[ONE General] TorchaOne:
Boeffla &zzmoove with latest nightly. 2 reboots in 10mins when typing.. First hangouts and second replying this message... Annoying.. Morning went well, first 3 hours after update. Back to 25th ;)
[ONE General] hughfollett:
I have play services 7.5.71 on COS12 stock and have no problems with location. And I play Ingress every day

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] fmc000:
OK, thanks, this makes the problem kernel-independent. So it must be related to some configuration or apps installed, as there are people like [MENTION=5411589]giaur[/MENTION] or myself who never had the problem (I tried also some graphic-intensive game for some ten minutes without problems).
[ONE General] TorchaOne:
Yeps. I had new WiFi etc applied too. Anyway, this 25th & boeffla has been solid. Love it.
[ONE General] shoman94:
No fc's with Google play services (7.5.71) and I'm set to high accuracy on 5/26
[ONE General] fards:
They are the Same thing.
[ONE General] nonoperez:
Clean flash, all stock, latest slim zero gapps. No problems, reboots or fc. Wi-Fi, BT and GPS working. Testing for 6 hours or so
[ONE General] novren:
I am getting an astounding battery life, or least way better than I used to have with the latest nightlies. Currently running 0526 nightly with 0517 boot.img I think it is, with the touchscreen fix, woke up at six, two hours SoT as of now and 19 hours to go according to graph. No wakelocks at all, nada.
[ONE General] RichAP:
Anyone receiving CMAS/WEA Alerts?

Is anyone receiving CMAS/WEA Alerts with 12.1 nightlies?

I posted this in the Oneplus Q&A Forum, but started thinking it could be a ROM issue. I do have all the alerts enabled in the settings.

We had a few Tornado & Flash Flood warnings this weekend and oddly my old Moto X that doesn't have a SIM card received the alerts but none on the 2 OPOs we have.

Thanks!

http://xdaforums.com/oneplus-one/help/receiving-wireless-emergency-alerts-cmas-t3118153
[ONE General] soralz:
Asking, this change:

Is this suppose to add Native H/W+ Decoder support for MX Player? Because on 4.4 KitKat I can play most MP4 videos with it, but now on Lollipop it can't.
[ONE General] elmerq:
I also had fc with GPS but only when i switched off few things in GPS under Privacy Guard like (do not know in English) keep awake, do not sleep, automatic start - these three options mentioned many times in other threads in case to increase battery life.
[ONE General] giaur:
This is what I suspected. People messed things in privacy guard and fcs are their fault.

---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------

Nope, it's for hevc decoder and 1080p only. But most files plays for me without any problems with hw+ and mx player
[ONE General] Gold Ribbed:
+2
[ONE General] WislaHD:
Does anyone have the download link to the May 14 (20150514) nightly?

The one on the official download page gives a 404 error. I heard from others that they found the May 14th to be the most stable of the recent builds and I'd rather not take my chances.
[ONE General] hroo772:
Here is the official 5/14

https://drive.google.com/file/d/0Bz7PeoKOlLLDSm5FQ0VUcmtDbm8/view?usp=sharing
[ONE General] Chikko:
14/05 il the best release for me. 5h sot since i woke up at 7 am to 00am, with a 14% battery residual

Inviato dal mio A0001
[ONE General] PtaZs:
Is the 0526 working fine? I dont know if i should install it.
[ONE General] shade1996:
I am using 17-5. Can i clear system and flash 26-5 on it??
[ONE General] fards:
26/5 should be stable as long as you don't block the wrong things with appops.

I've found 25/5 to be solid

On target for 30h battery and 4h50 screen with 20% left
[ONE General] hroo772:
Could you give any guidence on what can and what shouldn't be blocked. I know for me that blocking wake up on google play services saves battery life but I get some FC's. I'd rather not use xposed to deal with certain wakelocks but I'm not sure there is another way.
[ONE General] fards:
I don't block Google play service
[ONE General] fmc000:
You shouldn't block "wake up", only "keep awake".
[ONE General] NWKENT:
O526 Seems very stable and overall a good ROM..

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device 2 of 2)
[ONE General] sambaeallegria:
I keep it off instead and it works flawlessly. I noticed that I disabled auto start for Google service framework, that was the problem.
[ONE General] Zedoki:
Cannot get IP from dhcp

Hello everyone,

Since cm 25/05, my Oneplus cannot manage to connect to wifi. It can't obtain an IP address (it fail at this state). All other device laptop, mum's phone can.

I tried, wiping cache, alternative kernel, reflash, and delete AP from the list. Nothing works...

What can I do before wiping all to clean flash?
[ONE General] tiny4579:
If you have stability issues here is a suggestion.

1. Flash 5/14 nightly.

2. Flash one of the 5/19 boot.img from my post 1461.

3. Push [MENTION=265575]fards[/MENTION] GPS/WiFi file.

4. Profit.

It's what I'm currently rolling with and not too bad. I think the issue is kernel side and my boot.img should not have any of the problematic commits.

What this option does is keeps the stable nightly but also allows for either the new or old touchscreen drivers based on preference. It also has updated WiFi drivers and WiFi/GPS configuration.
[ONE General] shoman94:
I don't like seeing com.qualcomm.display (PPPreferences) showing up on my battery usage especially in the top 3.

5/26 stock cm12.1
[ONE General] razorloves:
delete these 2 folders then reboot.

/data/misc/dhcp

/data/misc/wifi

they will be rebuilt upon reboot.

doing this will erase all saved wifi passwords and wifi settings.
[ONE General] Ogrillion01:
Its not actually Qualcomm thing, its actually android system just using the wrong icon
[ONE General] tiny4579:
Something is jacked with the icons, I think it's always Android system.

BTW, BT revert merged:

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

Yay for BT users who were having speedup/disconnect issues. The icon issue I don't think happened after 5/14. I have 5/14 and an updated kernel with only the new latest WiFi and touchscreen drivers and it shows the CyanogenMod icon.
[ONE General] tiny4579:
Know how to remove a WiFi password fro. Google's servers? I really want to remove this 2.4 GHz AP but it restores the password on reboot after I forget it because my 2.4 network is saturated. I tried unchecking and rechecking backup and backup and restore in settings to no avail.
[ONE General] razorloves:
not sure man. i've never used that backup/restore function thats built into android.

i would guess that turning off the "backup my data" setting also disables the restore function, but you've tried that.

have you checked your google dashboard, under Android? https://www.google.com/dashboard
[ONE General] tducote:
Just a progress report: After a couple of days using the boot.img from [MENTION=3500210]tiny4579[/MENTION] , I don't believe I've had any random reboots. Just updated to tonight's 5/26 nightly and reflashed the boot.img. Thank's for the help, tiny.
[ONE General] dmarden:
Your passwords aren't the same for the two bands, are they?
[ONE General] conorkickass:
I just updated to the 27th May nightly with Boeffla Kernel and I am getting reboots about every three minutes. Had to turn my phone right off for a while until I can download the 26th May nightly again.
[ONE General] Not_A_Dev:
Ditto, but on the stock kernel. The latest nightly is a disaster with the perpetual rebooting. Back to the 5-14 nightly, and all is good.
[ONE General] TorchaOne:
HMM.. I got reboots yesterday when I applied those WiFi commits from 27th build beforehand. So its no for 27 to me.
[ONE General] :
Was/is for me the same :(
[ONE General] sax0406:
I'm on the 23rd nightly (clean flash). Whenever I get any calls, the screen won't switch on, even if I press the power button. The screen gets on on pressing the power button after the call is ended. Anyone got any idea how to solve this??
[ONE General] batwingnz:
I'm on latest nightly and getting a few endless sleeps and fast reboot if I press power button.

Also occasional persistent blinking of notification light but no visible notification
[ONE General] Zedoki:
I tried your solution, but /data is already empty... There are some folders that might match, even if I think It's not what you mean, /etc/wifi, /etc/dhcpcd.
[ONE General] giaur:
I have no idea how can it be? I have no any single issue. Latest nightly, all stock. Guys who are reporting that weird issues - make sure you are on stock kernel, you don't have xposed and similar mess and you didn't messed anything in privacy guard.
[ONE General] batwingnz:
Stock, no xposed and never touched privacy guard :)
[ONE General] Spewmonic:
Same issue. If I dirty flash 5-26, I get an endless bootloop.
[ONE General] giaur:
No bootloops at all. Maybe you should wipe data.
[ONE General] Spewmonic:
I flashed 5-27 then had reboots. I dirty flashed 5-26 and had an endless bootloop with "Android is starting..."

Just wiped and flashed 5-26. I hate wiping when am at the office. :silly:
[ONE General] giaur:
Evetytime I tried to downgrade by dirty flash, I was finished with endless bootloop. So it seems you can't downgrade. Upgrade, clean flash or restore backup are the only options.
[ONE General] LeroViten:
Endless bootlooping on dirty flashback 26/05 either. Random reboots on 27th... What the hell...

All stock, nothing like xposed, privacy guard mess. Only PlayServices denied for wake up and keep awake.
[ONE General] giaur:
Why? Disable it
[ONE General] LeroViten:
Ok, disabled now. ;)

There was some problem few weeks ago with the wakelock. So I did that.

The strangest thing is that I simply dirty flashed 27th nightly again and all is fine. Half hour active working without reboots.
[ONE General] giaur:
I have no wakelocks. Try also disabling it.
[ONE General] smwln:
Phone stuck at endless loop after the 27th May Update.

Android is starting - Optimizing apps, reboot, the same thing over and over again.
[ONE General] LeroViten:
Just did that.

Read my post above. Try dirty flashing 27th nightly again.
[ONE General] smwln:
Dirty flashed it, still the same. Android is starting, Optimizing 1 of 147 apps. :mad:
[ONE General] LeroViten:
Wait till the update and boot finished. It worked for me.
[ONE General] lallolu:
27th nightly is definitely broken

I was on the 26th nightly but it seemed not to be goof on battery so I was happy to flashg the 27th but after flashing, I was having endless reboots like others have pointed out.

I have now flashed the 26th back and waiting for android to finish optimisation.
[ONE General] dolphin77:
I have the same sttarting point (nightly from 26th, all standard). After update to 27th, phone booted and started optimizing all of the apps (yesterday did only 4 apps). Then it rebooted again. First I was afraid that it is a bootloop, but I decided to give it a chance. Just left the phone and it did boot and it is working now without any hookups.

So it just reboots one additional time and thats it. Give it time.
[ONE General] smwln:
I let it do its thing and then it rebooted again, again optimizing.

I guess I have to restore the nandroid backup of 05-26 :rolleyes:
[ONE General] mootmaina:
I still have issues with mms. On tpg Melbourne on latest nightly. Done everything. Deleted apn.used hangouts, textra. Done the other suggestions. I got no idea wth is going on. Since updating to lolly no mms for me. Doesn't make sense. Anyone. I don't really want to go back to cm11s..
[ONE General] giaur:
MMS is broken from beginning. Use 3rd party app, google messenger or textra
[ONE General] lordsinasina:
Finally another user from Australia :)
[ONE General] fmc000:
For those who are having reboot problems: have a loook at this commit. Doesn't explain why some people had the problem before the commit went in, though.
[ONE General] razorloves:
if data is empty, then you just wiped data, which you said you didn't want to do yet. lol

or were you trying to do this in adb and didn't mount the data partition?

just open cm file manager and enable root access (or use any other file manager with root access) and delete the 2 folders i listed.
[ONE General] Gold Ribbed:
Gone back to 05/26 as like others I get reboots.:confused:
[ONE General] LeroViten:
So they say disabling WiFi may stop reboots on 27th nightly. But I do have it enabled and all works fine, except some small lags when typing.
[ONE General] Eeelgen:
Can someone with nightlies pre 27th upload WCNSS_qcom_cfg.ini from system/etc/wifi ?
[ONE General] Zedoki:
Thanks it's seems to be solved with your solution.

I said that /data was empty because I haven't enable root access to my file manager. One it's enable, I was able to list files in /data and delete following folders /dev/misc/wifi and /dev/misc/dhcp.

I will confirm tonight if it really work with my home AP.

Thanks a lot again!
[ONE General] tiny4579:
No reboots on a dirty flash from 5/14 but I got a force close from system. WiFi wasn't disabled either.

Logcat from force close.

https://www.dropbox.com/s/c31ahb9zz4bhpj4/2015-05-27-04-50-59.txt?dl=0.

Anyone here run into issue in their logcat?
[ONE General] nonoperez:
27/5 is unusable, reboots and reboots. Coming from clean install 26/7. All stock. Restoring 26/7 back up.
[ONE General] bissa:
reboots with 27/5 too but I'm trying to flash old version and now the phone will reboot after optimizing apps message with any build rom, any fix ?
[ONE General] tiny4579:
Wipe data is the easiest. I took a nandroid before going to 5/27 just in case.

How many times did you guys let it reboot or is curiosity? I was chatting with someone about this lay night. They got a couple reboots but it cleared up.
[ONE General] Igazine:
I also had endless bootloops even with 5-25. Ultimately I reflashed 5-27 and weirdly now it looks okay, no reboot since then (phone is on charger since then)
[ONE General] tiny4579:
Two bands - separate virtual AP's but the same password.
[ONE General] tiny4579:
We need to get to the bottom of this and prove there is an issue starting like 5/15 kernel side.
[ONE General] TorchaOne:
This? Quite a lot changes...
[ONE General] karangupta:
I'm on 27-05 nightly via cyandelta! Its working perfectly fine. Not a single reboot, no crashes! WiFi+location services working fine.

Xposed also working fine.
[ONE General] totoybibo:
same here! it's my first time experiencing this issue on CM12.1
[ONE General] TorchaOne:
Can you post /etc/wifi/WCNSS_qcom_cfg.ini or check its size a bytes?
[ONE General] tiny4579:
It'd be better to md5 sum it for comparison than size check. Mine from 5/27 is

File: System/etc/wifi/WCNSS_qcom_cfg.ini

MD5: f4:40:27:9a:c6:05:84:be:f3:b0:51:26:58:ab:d7:a9

SHA1: 98:94:ee:66:35:02:0f:ec:bb:ad:af:99:f8:ab:17:81:b3:8f:49:95
[ONE General] bissa:
replacing /etc/wifi/WCNSS_qcom_cfg.ini fixed the reboots with 27 build, I used the one TorchaOne attached.

md5: c1de1a5a549de85623f355acc9cc55ac
[ONE General] karangupta:
It is of 8905 bytes

https://www.dropbox.com/s/rt7jwzshz0sma42/WCNSS_qcom_cfg.ini?dl=0.

Md5: f440279ac60584bef3b0512658abd7a9
[ONE General] TorchaOne:
Gee, so it works for u :) This is scary, mostly its not working for ppl.. I cant understand. Lucky the old ini works with new build.

---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------

You are right... just too busy to thing atm. The size difference was just so huge so this was easiest way to ask. My bad. :crying:
[ONE General] fmc000:
Are there people who are experiencing reboots on today's nightly after a clean flash and without restoring any app?
[ONE General] Eeelgen:
Pretty sure my issues comes from using custom kernel with this new WiFi commit. Seems like switching out ini files did the trick for me aswell
[ONE General] Tromzy:
On my side, the 27/05 build booted fine (I disabled Wifi before upgrading just in case) , but I got a reboot 2 minutes after boot. And another one just after. Going back to 26/05.
[ONE General] NullyOne:
Yes, mine has continuous rebooting.

I updated 5/27 from 5/26 and made wipe/cache after intallation.
[ONE General] Sk@ll:
Hi all, I tried to dirt flash back on 0517 after random reboot on 0527 but now I have reboot loop. Tried to backup but is still in reboot loop. Any suggestion before wipe data? My device cannot be recognized via usb and unfortunately I cancelled the 0527 just after update :crying:

Thnks!
[ONE General] fmc000:
Not what I asked. I wrote "clean flash", meaning with wiping the data partition too.
[ONE General] NullyOne:
Sorry. I'm confused by reboots.
[ONE General] oldie51:
I got the reboots after dirty flashing, then cleaned data, cache and dalvik, no reboot since.
[ONE General] Genericxx:
Maybe peope should stop complaining about issues/reboots if they dirty flash. I agree that dirty flashing may work normally, but in case of issues, after upgrading the dirty way, just try to "clean" flash and see if things calm down. And btw: "Clean" means that you'll format anthing except internal storage, not only data.
[ONE General] giaur:
Indeed. Dirty flashing may work or may not. No problems in my case though
[ONE General] karangupta:
Hey I just noted that my phone is also restarting but only when I lock the phone. If I continuously keep on using it, it doesn't restart but ASA I lock the phone it does. Sorry for the wrong info.
[ONE General] PuijkeN:
Hi,

Can someone please explain the sudden touchscreen horror with my phone? I have been on CM12.1 almost since the beginnining without any problems.

Then suddenly (half of May) I'm getting a very unresponsive touchscreen, if I put 2 fingers on the same height, it stops detecting the touches. Horrible and almost impossible to use the phone in a normal way with this.

Then around 17/05 a build appears with new touchscreen drivers which fix the issue completly. Feels like it should be again but with some battery drain because of gestures and dt2w.

Now I have read trough the topic and it seems that they reverted the touchscreendrivers again in the build of 18/05. I've tried yesterday with the build of 26/05 and still horrible touchscreen issues.

But now the question, why did the touchscreen issues appear suddenly? I have the device for 5 months now and did not have any issues. Did something change sometime in May causing the touchscreen issues and did this start the changing of touchscreendrivers?

I'm currently on build 17/05 with the new touchscreen drivers and battery drain. If some changes in May indeed caused the touchscreen issue, will it be a solution to go back to a build from before May, where both battery drain and touchscreen issues did not exist. I like 5.1, hence why I'm on CM12.1 but I would prefer an older build with perhaps some features less then this current borked up situation.
[ONE General] waterdaan:
Reboots

On clean flash 27/2 here, unfortunately...
[ONE General] dmarden:
Yeah, I figured the password was shared... hence the question. At some point a while ago CM starting doing something funny with saved wifi passwords and separate bands on a router (or at least I hope/assume it's on a router... I won't pretend to care enough to have tested that thoroughly).

I did test a little though, because some strange behavior was apparent (what you are attributing to Google having saved a password).

For example, at work I have:

Router1A and Router1B with a password of 12345678 for both bands with separate SSIDs

and

Router2A and Router2B with a password of 87654321 for both bands with separate SSIDs

My phone will only have both "A" connections saved. CM will care not and sometimes connect to a "B" connection, regardless of attempts to "forget" it (and also despite never having set it up in the first place).

I verified this with new fresh networks that I'd never used before.

It's weird, annoying, and a little troubling... but ultimately I didn't care that much to do anything about it.
[ONE General] Texan1:
Help! As many did, upgraded to the 27/5 nightly today and got stuck in the constant bootloop. Tried dirty flashing back to 26/5 and even 16/5 which were still on my phone but no luck, still had the reboots. I'm not fussed about doing a clean wipe EXCEPT I need my text messages. I had used TWRP to do a full backup, but whenever I restore that backup, bootloops.

Is it possible to clean flash an earlier build and only restore elements of the TWRP backup that would have my text messages? If so, do I restore system , data and/or boot from the backup?

Any assistance appreciated! Thanks...
[ONE General] giaur:
Don't even try to dirty flash older release, most likely it will cause bootloop. You can backup data with twrp, wipe, clen flash and then restore your data, however it may cause bootloop again. Also - what if you wipe everything (except internal storage) and restore your backup? Again bootloop?
[ONE General] Texan1:
I tried a clean wipe, flashed 16/5 build, let it boot up (which it did fine). I then rebooted into recovery and tried restoring backup - bootloops again. All I need to try and get are my text messages from the TWRP backup but not sure how?!
[ONE General] Underslung:
5/27 build working perfectly for me, no reboots. Dirty flashed from previous build.

I only flash ROM in recovery, not gapps anymore.
[ONE General] Jerommeke:
Looks like a rebootproblem with wifi on and when phone is "locked" indeed.

Just tried with wifi off when screen is off, but it doesn't solve the problem. Wifi off for now solves it for me. Meanwhile trying to find a solution.
[ONE General] lordsinasina:
Restore your backup. Then flash an earlier nightly's boot.IMG only . I would suggest 18/5 or before
[ONE General] giaur:
Instead of flashing old kernel blob, create jira report.
[ONE General] Froschface:
Same problem here... if WiFi is off I experience no reboots. However, if WiFi is on I get random reboots. Sometimes after just a few seconds, sometimes after 10-15 minutes... seems absolutely random to me.

For now I switched WiFi off and wait for the next release to see if that fixes it. Seems like the best option, because I don't have much time these days, so I don't want to go though all the hassle to clean wipe everything and reinstall an old version.

Do you guys think that flashing a new version (tomorrow or whenever it will be released) can fix this bug or is it likely that I will have to go for a clean wipe anyway?
[ONE General] lallolu:
In TWRP, clean dalvik, memory AND SYSTEM but don't clean data and internal memory. Now restore your backup. It should work.
[ONE General] Capt.Insano:
+1

I dirty flashed 27/05 over 19/05 unofficial and also flashed the latest xposed 5.1 framework: no bootloops/no reboots.

I missed the new touchscreen firmware however so I flashed the boot.img from Franco kernel r43. This Did cause a bootloop (boot animation would not end) so I just flashed 27/05 and xposed again and all still perfect (except touchscreen)

Any ideas on a touchscreen fix to flash over 27/05?
[ONE General] real_sl4cker:
Nandroid Manager from the Play Store can restore various elements from a Nandroid backup including text messages.

(mobil gesendet / sent from mobile)