yashsingh1/xdaforums huggingface dataset:
[ONE General] Odysseus1962:
Anyone know where to properly file a bug report? Last night's build (8/11) has serious regressions with the proximity sensor that need addressing ASAP. I flashed last night's build and used for awhile before going to bed and all seemed to be working fine. Then this morning when the phone's alarm rang to wake me I was unable to wake the screen to shut off the alarm (usually opening my cover wakes the device), DT2W didn't work, nor did pressing the power button. I was forced to hold the power button for a hard reboot to get back to the screen and turn off my alarm. Later in the morning after being in my pocket for several hours I went to Google an address so I could map a route to my next stop, the screen again failed to respond and required a hard reboot.

Then I flashed back to yesterday's (8/10) ROM which restored the correct functionality to my handset. So whatever changes were made to the 8/11 build which affected the proximity sensor need to be reverted back ASAP. TIA
[ONE General] MASantangelo:
Weird, maybe semi-related bug? I flashed 8/11 build last night and woke up to a phone that I couldn't wake up no matter what I did. I tapped power, got a gray/black screen. DT2W, gray/black screen. Let my alarm go off, swiped alarm away, got a gray/black screen. Power Off/Power On and screen normal. Tap power, waited a bit, tap power again, once again got a gray/black screen.

Flashed back to 8/7 build and that behavior is gone. Very strange and frustrating.
[ONE General] Odysseus1962:
It definitely sounds like either the same or a related problem as what I'm experiencing. Does anyone have a solution or experiencing the same issue too? All I know is this is most definitely a show stopper bug for me. Hopefully it's fixed tonight.
[ONE General] Coraz:
Just plugged the phone to the computer, couldn't access the files when the device was locked, and also when I unplugged it couldn't get to get the screen on (don't know if it's the same bug you are discussing about or something related to pc-plugging)

Sent from my OnePlus One
[ONE General] ianseer:
thanks a lot for saving me here... I noticed I lost my lockscreen at first, usually i do restore from my twrp, but this time, i only change my system profile to default and VOILA :D my lockscreen is back
[ONE General] Coraz:
That's not the issue I'm experiencing. The black screen-not turning on bug happened when trying to wake up the phone, not after the reboot, and I was always on Default profile. Must be addressed as a different bug, but atm I can't seem to figure out the reasons.

Sent from my OnePlus One
[ONE General] hogze94:
https://jira.cyanogenmod.org/browse/NIGHTLIES
[ONE General] tiny4579:
There were no proximity changes in 8/11. It's all audio and memory management mostly.
[ONE General] shoman94:
Either way... Whatever changed with 8/11 continues on 8/12. Screen wakes up but remains black... You can see the backlight come on.
[ONE General] :
For me the same :(
[ONE General] rasobey:
Yes, and it was still happening with the July 30th nightly at least. Makes videos interesting, and I've had to flash Calkulins ROM based on CMOS12.
[ONE General] tiny4579:
I think it downgraded the modem in either 8/11 or 8/12. That must be the source of the issues. I'm not seeing anything but this doesn't seem right.
[ONE General] AcmE85:
Still 241 baseband here on today's nightly.

Same goes for 0811.

I'm using the same TWRP version I used a couple days ago to flash from COS11 to CM12.1 0809 Nightly (OPO back from RMA),

so the baseband should be flashed correctly each time.

edit:

I can confirm the "grey screen of death" with today's and yesterdays nightly.

It happened once on each nightly so far.

Also what's strange is that the proximity sensor still works in this case. Whenever it is covererd the device does not light up to a grey screen.
[ONE General] lephoenix73:
I checked NON-HLOS.bin images from 08/10, 08/11, 08/12, there are exactly the same.

If modem came from here, there is no reason to get a "downgrade" isn't it ?

I dig into binaries and see 00241 referenced :

strings modem.b18 | grep DI.3.0.c6-00241
MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1
MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/wcdma/l1/offline/src/mcalwcdma_decdata.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/wcdma/l1/offline/src/wl1xlm.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_sm_idle_lte.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_mdb_idle.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_mdb.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_sm_idle.c
N/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_mdb_tds.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_sm_suspend_stm.c
/local/mnt/workspace/CRMBuilds/MPSS.DI.3.0.c6-00241-M8974AAAAANAZM-1_20150120_025837/b/modem_proc/lte/ML1/search/src/lte_ml1_sm_conn_inter_freq_stm.c

Are you using TRWP 2.8.6.x or 2.8.7.x to flash ?
[ONE General] tiny4579:
2.8.6.x. But I also used cyandelta as some were saying its completely fine and I haven't had issues. Guess I'll re- download the nightly and see if modem updates.
[ONE General] xzil3d:
Me too - I tried downgrading back to 8/8 (after wiping system, cache and dalvic) and still no dice. I might have to wipe absolutely everything...
[ONE General] nsmart:
Downgrading by installing older nightlies over newer nightlies is always a bad idea. Even if you wipe system, the data in your data-patition is still newer and does not match the older nightly. If you want to downgrade, do it by restoring a nandroid backup that includes system and data-partition together. Doing a nandroid backup before upgrading nightlies is strongly recommended.
[ONE General] Odysseus1962:
I too can confirm the issue "grey screen of death" remains in last night's build (08/12). On my device it appears to be a black screen because I have my backlight set to a low setting by default. I have no idea what changes were made to cause this issue as the change logs give no indication as to which commit is the culprit. However using either of the last 2 builds renders the device useless after any extended period of inactivity. This bug (regression) is a definite showstopper for me.
[ONE General] AcmE85:
In my case, it only happened when I quickly powered the screen off and back on again.

No problems powering it on after a longer sleeping period.
[ONE General] xzil3d:
I see this now. I'll definitely be doing nandroid backups now, before every update. Thank you.
[ONE General] detted:
Black screen on waking.

the black screen syndrome has happened 3 times on 08-11. I can't duplicate at will. It seems happening when the phone is placed facing down over some period of time.
[ONE General] tiny4579:
Most of the time it should be safe. But there's always a risk. The main concern is db downgrades, which isn't possible so we get force closes on the apps that try yo have downgraded db. In most every nightly that doesn't happen.

The actual data doesn't actually upgrade each nightly unless that apps db has had an upgrade. That's basically just system apps that have db upgrades.

It's still safer to nandroid when in doubt as there's still a risk depending on what nightly you're downgrading from and to. Just saying what you're saying isn't 100% true. Officially though a downgrade isn't supported.
[ONE General] Coraz:
To me, it happened twice on 08-11 after quickly powering off and then trying to turn back on.

Sent from my OnePlus One
[ONE General] shoman94:
I went back to 8/10 no issue
[ONE General] f231f:
Happened to me several times on 8/11 as well, so I flashed 8/12 on top of it this morning. Same problem.

Also tired of the battery drain in the recent builds, so I reverted back to a 7/25 build which I find to be the last stable nightly.
[ONE General] tiny4579:
1.4% an hour for me on 8/12 with the wrong radio. Its no worse really. If you flash every night you can't really honestly compare. Run one build for several days and take an average. Your usage will still vary. Its not really a fair comparison.

Google apps have and probably will remain the issue.
[ONE General] f231f:
I don't flash every night. I do give builds multi-day use tests. The only reason why I did back-to-back flashes today was due to the black screen of death issue. The newer builds all have a significant idle battery drain as compared with the 7/25 build that I am now set on sticking with for the time being.
[ONE General] Coraz:
Does anyone have problems during calls? I an hear the other person, but not viceversa.

Sent from my OnePlus One
[ONE General] davidfi01:
Telephone Dialer/Contacts

For the past week or so (since about 8/7) I have been experiencing significant delays in accessing the Speedial/Recents/Contacts and contact searches when trying to start another call from the dialer app.

I am either getting the screens with no contacts showing or if I get to the speedial screen, the contact pictures, and the dialer is completely unresponsive.

Some times I get Contact not responding message, wait, close or cancel dialog.

Eventually after 5-20 seconds, the system starts behaving again. The phone gets real hot while waiting.

David
[ONE General] lephoenix73:
Did someone have a copy of 07/25 ROM, since it seems the one the more stable for now.

Thanks
[ONE General] :
well if your updating firmware on twrp latest version dont. It just doesnt work right

everyone else, clean install might fix a lot of stuff
[ONE General] lephoenix73:
[MENTION=5461670]bachera[/MENTION], do you means you have no issues (grey/black screen, battery drain...) when flashing with TWRP 2.8.6.x (TWRP 2.8.7.x is reported to have problems).
[ONE General] :
nope, clean install all the way
[ONE General] AcmE85:
I did a fully clean install after my new OPO arrived from RMA, coming from CM11s.

TWRP 2.8.6.0.6 materialised. Baseband is uptodate.

Nothing has been on my device except for the nightly and gapps.

Immediately unlocked the bootloader on first power-on, flashed twrp, booted to cm11s,

copied nightly and gapps, booted to twrp and flashed with factory reset and system wipe.

I flashed 0809, 0810 without any issues.

On 0811 and 0812 I had the blackscreen issue once on each nightly so far.

The fact that it did not occur yet on your device does not mean that the bug does not exist.

As I said, it only happened once today and once yesterday.

Both times after quickly pressing power off and back on.

Nobody knows if there is a specific constelation of settings or apps which causes this.

Might be automatic LiveDisplay which I disabled today after the reboot. It did not work anyway...

Same goes for random reboots. I never had any but I well acknowledge the fact that users

suffered from them, even after a clean flash and correct baseband.

I don't have any battery drain btw. :)
[ONE General] Lar5:
Yes, but only if i use handfree (speaker).

Disabling the speaker agian and closing/opening the flip cover, brings back the sound at the receiver - most of the times.
[ONE General] Coraz:
I'm using stock dialer, unfortunately. Tried disabling and enabling again the mic, didn't work.

Sent from my OnePlus One
[ONE General] f231f:
I still have the file on my phone so I uploaded it for you:

http://hugefiles.net/6bya4xw3ch1a

MD5: F976F6AD077E8B85A07A58A00E86F955
[ONE General] lephoenix73:
download is progress. Thanks :)
[ONE General] KaZo58:
Check THIS out. ketut.kumajaya uploaded his newest TWRP and fixed firmware flashing and backup.
[ONE General] giaur:
Already tried that... no thanks. Restore always fails without any reason. Some options cause phone to completly hang, for example - reboot system hangs and I need to make hard reset with power button.

I would not recommend that build, sorry
[ONE General] KaZo58:
not rly... you used the new GUI which is under gerrit review. flash the materialised one. it works for me.
[ONE General] batwingnz:
Getting soft reboots even with boeffla kernel now since 7th august.

And this weird clock business https://imgur.com/a/mfNCy

---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------

https://imgur.com/a/mfNCy
[ONE General] giaur:
You are wrong. Materialised on still hangs. Sorry it's not stable. Reverted to stock twrp and it works again.

---------- Post added at 11:59 AM ---------- Previous post was at 11:46 AM ----------

P.S. is this bug with flashing firmware already reported to official twrp dev? Everytime I try any custom twrp build, I find it's broken with some trivial bugs, like restore always failed, now I even can't reboot from recovery to system.

I'm bored with that and decided to use only official builds, but firmware flashing bug looks as serious.
[ONE General] AcmE85:
TWRP 2.8.6.0.6 Materialised works perfectly fine here with restoring and flashing baseband.

Unlike official TWRP, it also supports the builtin cyanogen updater: automatic reboot to TWRP, automatic flash and reboot back to system. Official TWRP always shows an error and can't execute the flashing script.

btw, today's nightly 0813 has been finally released
[ONE General] KaZo58:
you don't need to be sorry :) i've just shared to you all to get rid of fw problems. it works very nice for me. it's unofficial custom which is based on official (stable) TWRP. The official one is not really "stable" ... a recovery which can't flash firmware... nope. i respect those guys fixing the custom recovery for us and fitting it to our devices.
[ONE General] giaur:
Hmm you are wrong latest official works with cm updater without any problems
[ONE General] AcmE85:
Ok thanks for the clarification then. I guess the last one I've tested was 2.8.6.0. sorry for the misinformation. :good:

Today's nightly flashed fine, will report possible blackscreen-issues.
[ONE General] giaur:
Also cmxlog seems to be broken
[ONE General] tiny4579:
2.8.6.1 and newer work for cm updater as far as officials go.

Yep. Noticed that as well.
[ONE General] tiny4579:
It has been reported a while back with 2.8.7.0 was released. I updated it with logs as they requested.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/444

I also pinged dees_troy on the IRC channel and he'll try to look into it, but not before Monday.
[ONE General] Coraz:
Nevermind, my dialer issue seems to be provider related.

Sent from my OnePlus One

---------- Post added at 01:27 PM ---------- Previous post was at 01:09 PM ----------

Also, the bug of waking up even with "Prevent accidental wakes" and the proximity sensor covered is back...
[ONE General] FOSI17:
What is this new recovery?

cm-12.1-20150813-NIGHTLY-bacon-recovery.img http://download.cyanogenmod.org/?device=bacon
[ONE General] lephoenix73:
Hi guys

I tried to flash TWRP from twrp-2.8.6.0.1-bacon-materialised-signed.zip (unzip it and get recovery.img) using this command :

sudo fastboot flash recovery recovery.img

But when I came in recovery (power + vol up), I get in fastboot mode and not TWRP.

Did I did something wrong ?

I already did fastboot oem unlock

Thanks
[ONE General] FOSI17:
(power + vol DOWN)
[ONE General] giaur:
SystemUI FC ater switch from guest to owner account. Anybody else?
[ONE General] lephoenix73:
Yeah, it works, wondering why I used Power + Volume Up :)

Thanks :)

---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------

TWRP propose to install SuperSU.

Is it required for proper CM 12.1 operations ?
[ONE General] FOSI17:
CM nightlies already have root/supersu, see developer options...
[ONE General] lephoenix73:
My bad, I was looking in stock CM11S (OPO is back from RMA), and didn't see it.

---------- Post added at 04:48 PM ---------- Previous post was at 04:42 PM ----------

Trying to install cm-12.1 with TWRP 2.8.6.0.6 end with error

Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/Download/cm-12.1-20150725-NIGHTLY-bacon.zip'

What should I do guys ?

Thanks for your help
[ONE General] Coraz:
Did you do a clean wipe?

Sent from my OnePlus One
[ONE General] lephoenix73:
Yep, but when I did that, I lost my zip files stored in /Download/

---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------

Should I copy zip files (CM12.1 and gapps) to / ?
[ONE General] giaur:
Wipe data, system and cache and try again
[ONE General] lephoenix73:
I move both zip files to / and wipe dara, system, cache.

When I try to install /cm-12.1-20150809-NIGHTLY-bacon.zip I've :

E:Mount: Unable to find partition for path '/cm-12.1-20150809-NIGHTLY-bacon.zip'
Error flashing zip '/cm-12.1-20150809-NIGHTLY-bacon.zip'

I'm puzzled
[ONE General] FOSI17:
flash TWRP 2.8.6.0

download latest nightly again

try again
[ONE General] lephoenix73:
I'm using TWRP 2.8.6.0.6 (materialized).

CM12.1 zip are all ok (i double check md5).

What could be wrong ?

If I do a factory reset and reboot OPO, will I be back to CM11S or with a broken OPO ?
[ONE General] FOSI17:
humm, don't know... maybe encryption problem...

try TWRP 2.8.7.0
[ONE General] Coraz:
TWRP 2.8.7.0/2.8.6.0.6 are broken as far as I know. Try with 2.8.6.0

Sent from my OnePlus One
[ONE General] lephoenix73:
I used an OTG cable with USB key to hold zip files (CM12.1 and Gapps for opengapp).

Flashed from OTG, Android 5.1.1 is now starting, optimizing 123 applications.

Crossing fingers: )

---------- Post added at 05:41 PM ---------- Previous post was at 05:33 PM ----------

CM12.1-20150725 installed, baseband 00241.

Yes :)
[ONE General] MurdererFight:
Can someone upload the stock browser for me? Please :)
[ONE General] Coraz:
If I knew how to extract apk...

Sent from my OnePlus One
[ONE General] Ok_Kaleidoscope5109:
Isn't it in the ROM itself? Why not just download it and extract the APK?
[ONE General] Ok_Kaleidoscope5109:
Sorry but I also don't get all the fuss about TWRP. I understand its currently broken for modem partitions, but honestly, just stick to the latest. Why risk a more borked TWRP? We know the existing TWRP works just fine for every other piece of flashing. I'd recommend just sticking to 2.8.7.0 and only when there's a modem change, you go and use fastboot. Plus, fastboot is more reliable of a modem flash anyway. and it's not like the modem changes every week....
[ONE General] lephoenix73:
Guys, hiw did you update to latest CM ?

Twrp zip install or cyanogen built-in updater ?

Thanks
[ONE General] Coraz:
I use cyandelta

Sent from my OnePlus One
[ONE General] zBear:
I used this metod 3-4 times for dirty install

no problem so far
[ONE General] Odysseus1962:
I've been on last night's build for about 6 hours now. So far no "grey screen of death," however, the proximity sensor still isn't functioning properly. Opening my cover isn't waking the device, but DT2W seems to be working fine so far. Let's keep our fingers crossed that the screen freezes no longer rears its ugly head.
[ONE General] TheNerd:
latest... many issues. cant play videos at all, whatsapp mic recording doesn't work

UPDATE: false alarm. all is fine. I messed something up.
[ONE General] AcmE85:
There you go, from 08/14 http://www48.zippyshare.com/v/w26oefSc/file.html

The nightlies aren't built this way for a couple months already. There is a whole sytem image inside the zip, no more folders with apks and stuff...

Always with builtin updater for a couple months. No issues.

Maybe this could help with proximitysensor issues http://review.cyanogenmod.org/#/c/105904/

Regarding the "grey screen of death", so far no issues on 08/13 and 08/14.

No such problems here on 08/14.
[ONE General] MurdererFight:
Thank you!! :)
[ONE General] Spannaa:
For future reference, you can use [MENTION=4896512]Alexey71[/MENTION]'s SystemExtractor to extract any system apks/files from the rom zip.
[ONE General] SoRiNuS:
I see on the cyanogen website that now they have posted some files called bacon-recovery.img Does anyone know what are those for?
[ONE General] Spannaa:
They'll be recovery images ?

Stock CM recovery.

Sent via Bacon...
[ONE General] :
I've never had a single problem with 2.8.6. No reason to update to 2.8.7, particularly as it is known to have issues. Newest doesn't necessarily mean best.
[ONE General] TheNerd:
what's the current (latest) modem in cm12.1 nightlies?

wanna make sure I'm updated
[ONE General] Bwyan Benton:
I'm almost certain it's .241
[ONE General] TheNerd:
then seems like I'm fine:
[ONE General] Bwyan Benton:
Yep. Believe so.
[ONE General] tijuanacartel:
My Bluetooth headset is fine listening to music/games, but always disconnects itself a couple minutes into a call. Highly annoying especially when the microphone on my phone doesn't work for calls. Any fix?
[ONE General] Bwyan Benton:
I think this is a bit of an ongoing bug. Not sure if it's fixed yet or what solves it tho as I don't use Bluetooth headsets.
[ONE General] AcmE85:
So far no blackscreen bug since the 08/13 nightly.

Also updated to 08/14 to 08/15 today.

Can someone confirm?
[ONE General] TheNerd:
thread too big so hard to follow accurately.

what that black screen bug?
[ONE General] AcmE85:
Simply put, you just want to power on your display and only see a black screen.

It is noticeable that the backlight does indeed power on and you can hear the notification sound

when you press the volume buttons to change the volume for example, or on incoming calls...

The device is running fine in the background, but there is nothing visible.

Only way to temporarily fix it is to hold power until the device reboots.

Some people like me experienced it after quickly powering the display off and on.

Others after a longer period of deepsleep. A friend of mine could not disable his alarm in the morning...

It only occured twice on my OPO. First time was on 08/11 and second time on 08/12.
[ONE General] lephoenix73:
08/13 up to 08/15 updates using Cyanogen built-in each time ?

If so how did you wipe cache/dalvik ?

Thanks
[ONE General] AcmE85:
Yes, I only use the built-in cyanogen updater.

I never wipe cache/dalvik (art). Why should I? Never did on galaxy s2, nexus 4 and 5.

All needed wipes are handled by cyanogen's flashing script.

Also apps are beeing rebuilt after flashing regardless if you wipe cache/dalvik or not.
[ONE General] lephoenix73:
I guess wipe cache/dalvik are old habbits in Android.

Thanks for your feedback
[ONE General] JohnMcW:
Messaging Bug 20150814 nightly

Running the nightly 20150814

regardless of what keyboard I choose,

In the messaging app, while entering a

text, the keyboard constantly closes

in the middle of typing.

The keyboard does not close in other apps.

rebooting does not resolve the issue.

Catlog shows a repeat of the following:

WindowManager V Adding window Window{3d2d0bc7 u0 PopupWindow:ca8f2cf} at 6 of 9

(after Window{e4ff9e2 u0 SurfaceView})

Spannable StringBuilder E SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

Spannable StringBuilder E SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

these lines then repeat multiple times.
[ONE General] GRLDT:
Right after I read this posts about black screen, I immediately get black screen when I lock my OPO. Had to reboot. After I reboot, off screen gestures won't work. Running 08/14 nightly atm. Downloaded 08/15 but the md5 from zip is different from the cyanogenmod download site. Built-in updater says the same thing after 08/15 download.

Sent from my A0001
[ONE General] lephoenix73:
For 8/15 it's Sha1 and not md5

---------- Post added at 09:00 PM ---------- Previous post was at 08:54 PM ----------

Just downloaded latest update, 8/15. CM updater say a compatible recovery is required. Will it works with twrp 2.8.6.0.6 (matérialized) ?
[ONE General] GRLDT:
Is it different from md5? I didn't notice it.

Sent from my A0001
[ONE General] lephoenix73:
Yes for 3/4 releases they use sha1 instead of md5.