yashsingh1/xdaforums huggingface dataset:
[ONE General] JoeF2:
CTS is the Google Compatibility Test Suite, which any OS that wants to get the GApps has to pass.

So, that is important for factory ROMs like CM12s.

---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------

Patch Set 3 is supposed to fix all that. I am building with that as cherry-pick right now.

If it fixes things, it could be merged soon.

---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------

It depends on when the build for each device is started. There are a few 0522 builds, but the build for bacon is probable scheduled in Jenkins for a time before the fix was applied.

This is all automated, that's what Jenkins is for.
[ONE General] :
By any chance, will you upload today's nightly too?

Many, many thanks in advance!
[ONE General] :
how?

from bootloader or from recovery?

thanks
[ONE General] fards:
Flashify will do it if you don't know how otherwise
[ONE General] :
I don't use Flashify.
[ONE General] lordsinasina:
I did it with flashify root which is on play store
[ONE General] JoeF2:
Well, it is still building, so it would be tomorrow morning, assuming it builds ok.
[ONE General] :
thanks.

But also you can flash it manually, via fastboot, extracting the boot.img from the nightly zip: http://xdaforums.com/showthread.php?t=1752270
[ONE General] giaur:
You can also flash boot.img via twrp
[ONE General] hib1000:
Does the boot image from the 17th contain the screen firmware update?
[ONE General] :
yes, cm has removed in nightly from May 18
[ONE General] crisis_trustee:
Where are new CM12.1 ROMs after 18/05/15?

What's up?
[ONE General] scormax:
flash the 05/13 nightly... it has no new touchscreen fix therefore no extra battery drain.... no random restarts... i have been sticking to this rom for almost a week...very stable in my opinion
[ONE General] hammer-is:
I've been doing a couple of builds from the "cm-12.1" branch after the 2015/05/18 official nightly but they have all suffered from random reboots.

Yesterday evening I tried building with the kernel before all the "alarm" commits but with the revert to old touchscreen firmware cherry-picked. I've been running this all day without any reboots so maybe the reboots are related to some of the "alarm" commits.

cd ~/src/$branch/kernel/oneplus/msm8974
git checkout 3462df8fb0cf73e8a7566acc895810e3e362ec45 #get kernel before all the "alarm" changes
git cherry-pick 3fffa90652cc1c9523cf40969f23497e7410cc5a #Revert "synaptics: Update firmware to 14001227"
[ONE General] waterdaan:
They failed to build
[ONE General] :
They failed to build due to this commit: http://review.cyanogenmod.org/#/c/98966/
[ONE General] karangupta:
But then if it is due to this ^ commit, it should be across all the phones and not only opo. Many other phones have got their nightlies.

There must be something else to it! :confused:
[ONE General] ch-vox:
according to PsychoI3oy (Admin on cyanogenmod forums) :

Source
[ONE General] tiny4579:
That's what I've noticed as well that they're kernel related. You can also use the new firmware if you don't care about idle drain or are willing to sacrifice dt2w if you care about idle drain. The updated WiFi drivers seem fine as well.

Also, this may help with the drain issue with double tap to wake or just general proximity drain. I haven't validated it yet, but I'm curious and may test at some point this evening.
[ONE General] Spannaa:
Even if that's fixed, the next nightly will probably need another commit reverting first or it may not flash on bacon.

Sent via Bacon...
[ONE General] chrismoses:
Same thing is happening with Nexus 10 and other nightlies, no updates since 5/18. Sucks. I tried going back to 5/17 but it was quite buggy. 5/18 is almost as bad for me (lots of random reboots) but at least the battery life isn't totally terrible. I may still flash back to 5/14 if this keeps up much longer, that was a pretty stable build.
[ONE General] JoeF2:
Yup. That's what I see on my own unofficial build.

Flashing fails, due to an assert in the updater-script.
[ONE General] hammer-is:
Yup. Also had to revert that on my build
[ONE General] Gold Ribbed:
I flashed 5/17 then updated with Cyan/Delta.. I have no reboots or FC's. very stable. I do not have the new firmware installed and using stock rom.
[ONE General] fards:
I've not had any reboots using the 18 build with boot image with new TS firmware.

Wonder what the common factor is that's causing it.

Currently on 42% after 11 hours (7 hours of Google play music and 2 hours screen on time ).

For those who are having reboots let's try and work out a pattern.

Do you have WiFi on in sleep or set to off?

Do you have alarms? are you using a specific alram/clock app?

Are you using network time automatic or manual?

Anything else different?

Kernel/multi boot/recovery/
[ONE General] crisis_trustee:
OK. Will wait.
[ONE General] karangupta:
Post you kernel and baseband versions! I also did the same, and surprisingly I haven't got any of the restart problems. I feel cyandelta doesn't update everything every time.

Using WiFi/3g,automatic time update, pico-gapps.
[ONE General] NullyOne:
I have the same and no restart problem (just once from may 18th until today, phone rebooted himself). Also, no battery or touch problem.

I updated using CM updater.
[ONE General] fmc000:
This is very interesting, actually. If I'm not misunderstanding everything, it seems that since Jan22 the CM recovery has the capability to parse different TZs and therefore is happy with this change, which introduces a second TZ:

require version-trustzone=TZ.BF.2.0-2.0.0109|TZ.BF.2.0-2.0.0123

However, it looks like that TWRP up to 2.8.6.0 isn't capable to do that and thus the check on OPO fails just because the commit has in the first position the older TZ:

Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0123
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cmupdater/TEST_cm-12.1-20150522-UNOFFICIAL-bacon.zip'
Error flashing zip '/sdcard/cmupdater/TEST_cm-12.1-20150522-UNOFFICIAL-bacon.zip'

So, after this commit it won't be possible to flash the nightlies anymore with TWRP until the recover is modified accordingly. I wonder if Philz will have this problem too (most likely IMHO).
[ONE General] giaur:
So nobody will able to flash it
[ONE General] fmc000:
Nobody using custom recovery.
[ONE General] prinz3nroll3:
i use twrp... i am now unable to flash the newest nightlys?

thx
[ONE General] fmc000:
Well, I don't know for sure and I didn't try flashing unofficial builds. I wrote in #1816 just what I understood reading the last 7 comments added to this commit. I'm not an English native speaker and therefore there's always the possibility I'm misunderstanding everything.
[ONE General] Spannaa:
So is it just a case of switching the the TZ positions?
[ONE General] giaur:
Everybody use custom recovery.
[ONE General] fmc000:
That would be an interesting test, yes.

---------- Post added at 10:31 PM ---------- Previous post was at 10:31 PM ----------

Everybody but the actual CM committers it seems...
[ONE General] Gold Ribbed:
Just the same so I am a happy bunny.
[ONE General] giaur:
What is that "trust zone"??
[ONE General] fards:
This is fairly comprehensive.

https://www.blackhat.com/docs/us-14/materials/us-14-Rosenberg-Reflections-on-Trusting-TrustZone.pdf
[ONE General] JoeF2:
I have TWRP 2.8.6.1, and it doesn't work with that, either.

I opened a bug report with TeamWin: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/413
[ONE General] NullyOne:
There could be a problem with TWRP? Sorry I don't understand technical things.

I have unofficial_twrp_2860.
[ONE General] robuser007:
I'm on latest official nightly: autoswitching between lte and h(+) don't work: I have lte or 2g, but no h(+) !
[ONE General] JoeF2:
Yes, until that is changed or TWRP is updated.

---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------

Not just "could".

It will not be possible to flash upcoming nightlies with TWRP until that is fixed in CM or TWRP is updated.
[ONE General] giaur:
Yes, I can confirm. I just finished compiling and I can't flash my build due to tz error. No more nightlies unfortunately, we need to wait for next twrp version.
[ONE General] JoeF2:
That's a workaround, but the real fix is for TWRP to read more than the first position.

Update: I can confirm that switching the positions works. I just flashed my build created after switching the positions.
[ONE General] giaur:
What if I remove assert trustzone from update scritpt?
[ONE General] JoeF2:
Yeah, that works as well. I've done that to be able to flash my build.
[ONE General] TorchaOne:
Are they doing this on purpose on cm side? all little tricks and treats to make flashaholics life hard :)
[ONE General] prinz3nroll3:
is swaping to an nother recovery an option?

clockworkmod?

thx
[ONE General] Gold Ribbed:
So they are releasing a nightly that no one can flash. Will this have a nock on effect of all other CM based ROM's?

I really like twrp so hope this can be resolved. There will not be many testers otherwise.:confused:
[ONE General] NWKENT:
Darn it.. just got a dependable TWRP version..if a new compatible TWRP version is awhile in the making..is you'alls tz error workaround something that can continue without repercussion(s).?

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device 2 of 2)
[ONE General] giaur:
Try this: https://mega.co.nz/#!VgkVRaxa!ooAkpfNqP5MsRPXZlKIaNDFNOR3Rp-Eq-nbZwbwETYk - it should work without any issues with twrp. Compiled 2 hours ago.

I can confirm custom dpi problem with Chrome is fixed. Also I can see some wifi fixes in changelog.
[ONE General] tiny4579:
So for the random reboot issues, a nightlies JIRA ticket or posting to this commit witha logcat should help gain some traction in getting this resolved.

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

Ideally, I'd like to find the specific commit causing it and request a revert or fix, but there are a lot of alarm commits. I think it's this one as it's the one tied to wakelocks, and I have noticed a few wakelock related errors in logcat when running the latest kernel.
[ONE General] giaur:
It actually happened to me only one single time. Now I'm on my own fresh build, no reboots so far. There was bunch of changes merged since 18.05
[ONE General] NWKENT:
Thanks..I'm on 0518 (official)..I'll give yours a flash..

:)

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device 2 of 2)
[ONE General] ch-vox:
Flashed without any issue. I'm testing it tonight, no problem so far.
[ONE General] pijas82:
Nightlie is out

Sent from my A0001
[ONE General] doalittledanse:
Is it flashable with TWRP? Since it looks like people are saying it isn't going to be.
[ONE General] ch-vox:
absolutely.

dirty flashed through TWRP 2.8.6.1 over [MENTION=5411589]giaur[/MENTION]'s unofficial 0522, and optimisation done after wipes.

I'm going to test it now to see if it's working well.
[ONE General] doalittledanse:
I flashed it a couple hours ago and I saw at least one reboot.
[ONE General] TheNerd:
did u wipe?

I never had any reboot with any nightly yet.
[ONE General] phonepersonality:
Quick question - Does the nightly have the touchscreen firmware or no?
[ONE General] JoeF2:
Yes, interestingly, it installed. They must have been some other change that made it work.
[ONE General] ch-vox:
it's been removed since 0518 mainly due to batery drain.
[ONE General] dmarden:
Tonight's official 5/23 nightly flashed fine in TWRP for me (2.8.6.1)... Not enough time to comment on the build's quality or anything, but the flashing process was fine.
[ONE General] tiny4579:
It has the pre 5/15 nightly firmware due to this commit:

https://github.com/CyanogenMod/andr...mmit/3fffa90652cc1c9523cf40969f23497e7410cc5a

This is the same touchscreen firmware that has been in the nightlies since like January. No it doesn't have the new one that was only present on the 5/15-5/17 nightlies.
[ONE General] tiny4579:
Yeah, I was surprised with all the complaints. Did you flash directly in TWRP or through CM updater? I flashed through CM updater.
[ONE General] dmarden:
Directly in TWRP.
[ONE General] Not_A_Dev:
Confirming that Cyandelta successfully updates the 5-18 build to the 5-23 build via TWRP 2.8.6.
[ONE General] t2jbird:
Flashed in TWRP 2.8.6.1 from 5/18 to 5/23 without a hitch.
[ONE General] jdonk:
Coming from 5/16 to 5/23 using TWRP 2.8.6.1/ Cyandelta. So far so good.
[ONE General] lordsinasina:
AnTuTu test shows around 46000 on today's nightly, 3000 less than usual that I get
[ONE General] usmave:
anyone got problems with transfering larger files about 500mb via smb? tried solid explorer and foldersync.

its just smb making problems, google drive works perfectly.
[ONE General] JoeF2:
Battery drain seems to be bad with the 0523 nightly.

Sent from my A0001
[ONE General] cshuwing:
On 0523, still experienced sleep of death as on 0518. Everything stock.
[ONE General] cshuwing:
Experienced 2nd time, and "optimizing app" appeared this time. Going back to 0517.
[ONE General] NullyOne:
Ohhh! I'm so sad this morning, I see the new nightly 05/23 and cannot install it :(

(I became addicted) :)
[ONE General] hroo772:
The thing I've found is that if I hold the power button for about 4 sec the phone boots back out of the sleep state. Sometimes clicking the power button multiple times does it as well. It can be done without doing a full hard reboot to avoid the "optimizing apps" stage. When it boots back it seems similar to what happens when using quick boot, even without quick boot enabled.
[ONE General] fmc000:
Actually it installs just fine. If you read some posts back there are people who were able to update with TWRP and I can confirm that latest Philz works too.
[ONE General] giaur:
I looked into updater script and there is no tz assert there. So it will always install fine. Actually, tz aseert is in custom builds only and needs to be removed.
[ONE General] andimae:
Installed with TWRP 2.8.6.1 just fine. No problems up to now.

Gesendet von meinem A0001 mit Tapatalk
[ONE General] benj!:
I'm still running [MENTION=3500210]tiny4579[/MENTION]'s 0519 build with the touch firmware. No reboots and battery life has been decent (with dt2w off)

Sounds like I'll be sticking with it for now!
[ONE General] lordsinasina:
Is there any way to install the new touch firmware on latest nightly ? Like a separate flashabale zip ?/
[ONE General] Spannaa:
I guess this is because the nightlies include the firmware and therefore don't need to check the trustzone.

Sent via Bacon...
[ONE General] NullyOne:
Yes, I read many messages people having different experiences.

Now I go out to have a good coffee while phone is charging. I downloaded nightly from the computer and...be back later :)
[ONE General] fmc000:
Maybe but this doesn't change the fact that there is a bug in TWRP (and possibly in Philz too) that needs to be fixed.
[ONE General] Mayday_XL:
+1

*** Mayday@O+O ***
[ONE General] PlayersHeaders:
cycle change

hello cm developer, i want to change my cycle to 18.may - 18.june, how to?
[ONE General] 19deimon90:
With mobile data on, tap on the cycle and at the bottom you will find the option to change it.
[ONE General] TorchaOne:
I had to try and same here, lowest score ever. And I still have problems connecting on/off to different wifi networks, very slow or no connection at all.

When u finally get it up, it might die when screen off. It's been since this super 241 radio :( But not giving up, I like flashing, hehe.
[ONE General] lordsinasina:
Had my share of random reboot with today's nightly. Went back to 17/5 again.
[ONE General] giaur:
I can't even finish test. Antutu crashes

---------- Post added at 10:31 AM ---------- Previous post was at 10:26 AM ----------

No reboots for me.
[ONE General] TorchaOne:
Heh... I got rid of WiFi problem at home assigning static IP... Now problem us work and other locations. Anyone can post a lunk to flashable dhcp fix? I am too blind to find it...

Fixed only connection probs.. WiFi still dies, download max 50kbs, reset helps.. Lovely.
[ONE General] lordsinasina:
Wait for it [emoji12]
[ONE General] shrubber83:
For me with 2305 Nightly is all OK... Bug i nerd the touch firmware... Someone could compile the boot.IMG of this nightly with the new touch driver?
[ONE General] highdiver_2000:
extract boot.img (using 7zip) from 15 May nightly. Flashboot it.
[ONE General] shrubber83:
I know and i have it.... But i would like to have all updates and the new firmware...
[ONE General] NullyOne:
Installed 05/23 fine. At the moment I don't have problem. I used CM updater and TWRP. Battery seems not very good.
[ONE General] HWAM:
https://forums.oneplus.net/threads/new-synaptics-firmware.310743/

http://magnamentis.com/FW_CM12.1_150514_TOUCH.zip

Anyone tried this zip on 05/23??
[ONE General] ghismo83:
wifi bad connect for me with last build
[ONE General] pijas82:
Last night

Nice WiFi,radio,touch,,livre display, no drain

I love this rom, better since July 2014
[ONE General] xodeus:
It's already implemented in our nightlies.
[ONE General] pijas82:
Clean install, dont use cyandelta guys , dirty flash ou clean ,

Dirty flash- wipe Dalvik cache,system,cache

Install ROM, gapps, maxxaudio,color os
[ONE General] HWAM:
What do you mean with "our nightlies"? Where can I find those nightlies with the new Synaptics touch firmware already in?
[ONE General] tiny4579:
5/17 is the last nightly with the new firmware. They reverted it due to battery drain with dt2w.
[ONE General] NullyOne:
Have you tested the 5/23 battery?

It seems to me I have more drain than before with version 5/18
[ONE General] HWAM:
I know! That's why I asked it in the first place! I want 05/23 up-and-running with updated drivers. Did anyone flash this zip in 05/23:

https://forums.oneplus.net/threads/n...rmware.310743/

http://magnamentis.com/FW_CM12.1_150514_TOUCH.zip

Anyone tried this zip on 05/23??
[ONE General] creepinm3:
I haven't flashed it but I know AK kernel has a touch version with it implemented.
[ONE General] Garrret:
I did. Everything look fine to me.
[ONE General] tiny4579:
I have a kernel with the new drivers and a possibly problematic commit reverted. I can post it later. I'm just doing boot.img but that's trivial to flash with flashify or fastboot. I can probably get it posted in an hour when I get back home.
[ONE General] tiny4579:
Doesn't seem that much different so far honestly.
[ONE General] highdiver_2000:
You need 2 or 3 hours of active use to see. In Battery, if any of the apps climb above Display, it is not good. If Display dropped to like 5th position, it's really bad.
[ONE General] NullyOne:
Its not a technical affirmation, is only a sensation :)

Just because quite every day battery is at about 50% after 10 hours and today is 70% after 6 hours....I'll wait 4 hours more :)
[ONE General] waterdaan:
The problem I'm having with latest nightly is that WiFi disconnects when screen is off. And then the apps in the background keep mobile radio active which causes bad battery life

I could kill the apps from recent, but...
[ONE General] tiny4579:
Why is this happening to several people now yet when I turn off my screen I still have WiFi active.
[ONE General] TorchaOne:
I have it active but traffic is dead... And seems like it stops working while surfing... Yeah, fresh installed again. Don't really want to go back to old radio ;)
[ONE General] NWKENT:
I flashed your build with no problem, 0522 UNOFFICIAL with TWRP 2.8.6.1

No reboots, No FC's as of yet..

:)

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device 2 of 2)
[ONE General] waterdaan:
Reason =6

I've got no idea what that means
[ONE General] moumouza:
Does this unofficial build have the touchscreen fix guys?
[ONE General] Genericxx:
For those having WiFi trouble, just try what's explained here. Maybe it will fix your issues.
[ONE General] giaur:
No. It was compiled yesterday evening, fully stock.
[ONE General] tiny4579:
Here you go:

https://www.androidfilehost.com/?fid=23991606952608871

Also looks like the dynamic sampling rate revert has helped at least a few devices with a2dp playback issues.

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

I'd like to see it merged, mainly since it doesn't seem to have done what it's supposed to. It won't resolve the bluetooth disconnect issues, but in that commit, that guy Pat says he's willing to work on it with one of the users.
[ONE General] HWAM:
Please explain me the following. Build 05/15 contains new Synaptics drivers. If I open the nightly 05/15 zip I see the boot.img file. Are those drivers stationed in this boot.img file? Did gave me this boot.img file from the 05/15? What about a kernel? Is the boot.img the kernel??

And how is it possible that the zip from this site, also contains driver?

https://forums.oneplus.net/threads/n...rmware.310743/

http://magnamentis.com/FW_CM12.1_150514_TOUCH.zip

Is a kernel containing more than only a driver? I want only update the driver in the new 05/23 build. Is that possible? If a boot.img is more than only a driver maybe it's better to flash the FW_CM12.1_150514_TOUCH.zip from the site I gave you.

Please explain because I don't understand the difference between a boot.img and the FW_CM12.1_150514_TOUCH.zip.

I compare it with Windows, I only want to update the touchscreen driver.
[ONE General] fiorellona:
Well, how these 4 hours are?
[ONE General] NullyOne:
[MENTION=6150541]fiorellona[/MENTION], it's perfect. Battery is 60%. Received about 70 mails, used Facebook, twitter, SMS, Viber, tapatalk and others. WiFi and LTE.
[ONE General] Badbrad17:
Minimal app load after reboot

I have tried to flash this ROM numerous ways and numerous times and am having a strange issue that I am hoping someone can help me with. I am able to flash everything fine, I go through setup and app restore etc. then when I reboot my phone I only get the boot screen, and my notification screen. I am able to drag down the notifications and settings quick menu, but any time I select anything nothing loads. I am even able to receive emails and other notifications because I can see them coming in on the notification bar.

I was also having the exact same problem when I tried to flash the Resurrection Remix Rom. When I flash Oxygen OS I have no problems.

Just to be clear, I have done a full wipe of data and SD card in order to see if it was a bad flash. But the strange thing is that everything runs perfectly fine after the first flash until I reboot then it's hooped.
[ONE General] giaur:
Don't enable profiles.
[ONE General] fards:
the ts drivers are only in the kernel, the boot.img contains kernel and ramdisk (look in / and /sys on your device to see what's usually in the ramdisk).

Those other files you linked to dont contain anything related to TS
[ONE General] fards:
we need people to start saying what theyve done differently, and provide logs !

too many variables at the moment to observe patterns.
[ONE General] NWKENT:
To the ROM Dev's here: is there any way to incorporate the function "Signal Status Style" into the 5.1.1 Nightlies, as it was in KK_05Q..This function, I adore, instead of the data bars icon, displayed is the actual signal strength, for a quick glance and testing the providers, its very helpful..the screenshot for example..please forgive me, if I have posted in the incorrect thread..

sent by my: SandStone Black 1+1

(aka) OnePlus One, OPO (Device 1 of 2)
[ONE General] Badbrad17:
That's it? I am just reflashing Oxygen, but I will give this a go. I hope it works.
[ONE General] HWAM:
Are you telling the http://magnamentis.com/FW_CM12.1_150514_TOUCH.zip doens't contains tc drivers?
[ONE General] tiny4579:
The touchscreen drivers are in the kernel.
[ONE General] fards:
Does it contain a kernel?

If the answer is no then you've answered it yourself :D
[ONE General] giaur:
There are no rom devs here
[ONE General] Badbrad17:
Thank you! Thank you! Thank you! Thank you! Thank you!
[ONE General] fiorellona:
Did you make a clean flash or use cyandelta?
[ONE General] NullyOne:
I used CM updater to download, then I went in recovery TWRP, installed, made dalvik/cache and reboot.

Again in recovery Twrp, installed zero gapps with Viper from [MENTION=6109902]mohit310[/MENTION] and reboot.
[ONE General] fiorellona:
So you did a dirty flash.. I thought that it makes problems