yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Se7enpoint62:
Anyone verify if 9.1 fixed the drain?
[ONE Android Development] dmt-300:
I can confirm there is no more battery drain anymore ????. I dirty flash v9.1 and all seems going the way it should be.

Thank you so much guys for the great work and effort to fix this beautiful ROM ????.

Regards All ????
[ONE Android Development] djha53k:
Confirmed NO battery drain anymore. Thank you very much :good: :victory:
[ONE Android Development] syndrome:
Drain still there, dirty flash. BT turns off from self. 1 Hour 15% lost.
[ONE Android Development] vonstarr:
Dirty flash from 8.4. Working perfectly, drain is gone. Even fixed an issue where Facebook Messenger kept force closing and I had to uninstall it. Excellent work!
[ONE Android Development] Sicron:
The issue was not fixed with 9.1

Initially it seemed like the battery drain was gone, but after a couple of hours it returned. It is definitely a location issue.

http://m.imgur.com/QJSUd4l

http://m.imgur.com/aWkklIU
[ONE Android Development] zagzag99:
Right, there's still a lot of battery usage accounted to location service.

And some location based apps can't get location. For example waze at setup won't recognize country. Location is later provided by GPS only.
[ONE Android Development] kalpik:
Like I previously said, it's the QC location stack.
[ONE Android Development] djha53k:
I have GPS OFF, I do switch it ON only for navigation... so for me the battery drain is gone :fingers-crossed:

The most battery taken for last 12 hours of my One+1 is Viber :victory:
[ONE Android Development] vonstarr:
I'm figuring something else went wrong somewhere, since everyone had a drain issue from 8.6, whether or not they used GPS. That was the case for me, and 9.1 has sorted that out. My location is always on set to device only, and there's a marked difference between 8.6 and 9.1. Hopefully it will be completely sorted asap.
[ONE Android Development] Sicron:
The location battery drain issues only happen when you set the location to batterysaving option that uses Wifi. (And the most accurate option as well)

When you turn it off, you won't get the millions of wakelocks.
[ONE Android Development] katenaccio:
I can confirm that battery drain wasn't fixed... It's still present. So I'm turning back to the last good build... 8.4.

This rom is still the best.... However

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] Micalus:
Hey guys

I have a little probmen with calls. Every time i'm calling someone, i get an echo and the other person as well. The echo is even stronger when i put the call on speaker.

It has to be a problem with my phone, since my OP2 doesn't have the same problem with the same person i call.

Installed Temasek 9.1 with opengapps nano latest, boeffla kernel beta25, superSU v2.74 and viper4android + sonybeats 4.8.1.

i searched for a solution via search option, but couldn't find one. If someone could give me a hint how to resolve it or what is the culprit here i would be really thankful.

Cheers

Mike
[ONE Android Development] dragoi90:
Maybe the problem is with the audio mod you are using.Check the call quality before and and after the audio mod.

P.S

Check A.R.I.S.E mod.
[ONE Android Development] RukusX7:
Okay, so whats the fix? I am experiencing this on my builds as well, and am at a loss.
[ONE Android Development] kalpik:
There was a commit a few days ago about switching to the Qualcomm location stack. I'd start by looking at how to revert it.
[ONE Android Development] katenaccio:
Me too.... I had the same problem with 8.8 and 9.1.

Switching back to 8.3 or 8.4 calls are good and no battery drain.

The problem is not due to the mods.... Because I installed only rom and open gapps Pico.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] RukusX7:
Still doesn't explain what broke, when CM works for my device fine.... Anyway offtopic for this thread. wrong device. Thanks for the help anyway!
[ONE Android Development] tssphysicsboi:
For some odd reason I'm having lag issues on wifi on this ROM. Playing clash royale on wifi it lags but with 3g it's fine. My Nexus 7 on same wifi has no lag. Very odd.
[ONE Android Development] kaibosh99:
I can assure you it has nothing to do with your rom, wi-fi, or anything else but the game itself. CR lags on wi-fi for a lot of people, and yes that makes no sense at all. Can you make any other game do this, including the other Supercell games? Nope.
[ONE Android Development] djha53k:
Guys, I'm not having any of those issues you meantioning here.

The v9.1 is just perferc as all ROMs of [MENTION=2332422]temasek[/MENTION] before. Thank you!
[ONE Android Development] vonstarr:
I noticed something similar with Walking War Robots, with the game disconnecting and sticking. Never happened before, but I wasn't sure if it was 9.1. Still not sure it's the Rom, but I can't think of anything else. Game had an update recently.
[ONE Android Development] RukusX7:
QC Location fix

[MENTION=3814731]katinatez[/MENTION]

I found a temporary fix for the location high cpu use and logcat spam. I applied this patch to my builds and for now I see it as a work around until we figure things out. This allows us to use High Accuracy without logcat spam and high cpu use / battery drain.

This is worded from the patch itself:

msm8974: Don't use QC location stack

* The QC fused provider still has serious issues with location
injection, which leads to it being unable to hold a fine location.
* Use the Google fused/network provider instead.

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

The patch is marked as abandoned because I guess this issue doesn't exist on CM and I verified on my device that this is true. So it looks like whatever CM fixed to improve this injection, isn't quite the same on Temasek's CM 13. I hope this can help one of us get to the bottom of the issue.

Edit: I did not apply my equivalent of this patch tho. https://review.cyanogenmod.org/#/c/134685/

I wonder if it matters? I do want QC Location stack working, so if i figure anything out I will let you know.
[ONE Android Development] envied:
I have the exact same problem, when I play on my nexus7 using same wifi there is a world of difference in the delay

Kaibosh I know what you are saying because I do still see some Lag on the nexus 7 from time to time but no where near what it is on my opo with this rom while connected to wifi.
[ONE Android Development] kaibosh99:
On the CR reddit sub a lot of people play the game on 3G instead of Wi-Fi, the game seems extremely sensitive to any lost packets and it is theorized that it is because of aggressive anti cheat measures. It isn't just this phone or ROM.
[ONE Android Development] RukusX7:
[MENTION=3814731]katinatez[/MENTION]

That patch I gave you earlier broke my coarse location services and I had GPS only. So RM -rf my device folder and sync'd it to revert the changes. I figured out something that works, try editing your izat.conf file located in /gps/etc of your device tree folder.

look for NLP_MODE = 3 and change the value to NLP_MODE = 1

For now this has stopped the logcat spam on my device and coarse location appears to work. Sorry to post about another device in here, but hey if it helps us both, why not?

Edit: Actually this is totally with merit, because I DO run your builds on my Oneplus One. :)

Edit: Don't bother with setting to 1, that didnt fix it. setting to 2 fixed it. Its not perfect and doesn't appear to scan with wifi off, but hey, better than what it was before!
[ONE Android Development] Guido83:
file izat.conf is located in /system/etc
[ONE Android Development] RukusX7:
I was referring to source code. But yeah I suppose any user can do this workaround their self!

anyway, NLP_MODE = 2 works so far.

Good luck!!!

My solution is going to be removing QC location stack altogether in my ROM if need be.
[ONE Android Development] ashutoshmn:
What do these stand for?

1. GNP Only 2. QNP Only

So, NLP_MODE = 2 acc. to you works fine and eliminated the batt. drain? or NLP_MODE = 1 works better?

Cheers!
[ONE Android Development] RukusX7:
You tell me! My best guess is, that GNP is for GNSS, QNP is for QUIPC .... now what do those stand for? xD

NLP_MODE = 2 works for me on my device.
[ONE Android Development] ashutoshmn:
Wait, what the heck is going on here? xD

If GNP is for GNSS and QNP is for QUIPC, then find out the gravitational field of Mars. :p:D
[ONE Android Development] katinatez:
Thanks for the clue, my approach is to just switch device branch to

https://github.com/katinatez/android_device_oneplus_bacon/commits/stable/cm-13.0-ZNH2K

The reason is because those commits are already in there.

https://github.com/katinatez/androi...mmit/7cef4f344e5d09a9839a9e3d027a19089e6cd309

and

https://github.com/katinatez/androi...mmit/2ff1b461a51fd6d0e26392ec8e7b753512e07a4a

Switching branches will also get rid of Gello browser; I don't like it.

I will have a new build out tomorrow it's very late here, going to bed.
[ONE Android Development] TheQuarterMile:
Any of you'll face issues where the phone just suddenly stops charging and then you have to reconnect the cable for it to start again?
[ONE Android Development] parvesh:
[MENTION=3814731]katinatez[/MENTION] thanks sir .. just want to check can we dirty flash over previous build or do we need to make a clean install as you changed the device tree from nightly to stable :)
[ONE Android Development] katinatez:
I dirty flashed but if drain is still there then try clean flash.

Some 20-30 commits have been removed with new branch so I would suggest a clean flash then test for battery drain.
[ONE Android Development] GirishSharma:
What about mobile radio active bug, is it solved?
[ONE Android Development] katinatez:
Not aware of this bug care to elaborate.

Also will finally have and update to cm-12.1 tomorrow; have to add a few commits.

Package Complete: /home/katinatez/android/cm-12.1-temasek/out/target/product/bacon/cm-12.1-20160615-UNOFFICIAL-bacon.zip

make: Leaving directory '/home/katinatez/android/cm-12.1-temasek'

#### make completed successfully (16:23 (mm:ss)) ####
[ONE Android Development] timbuctoo:
Dirty flash returns to recovery (TWRP) after two reboots

How did the dirty flash work for you? I dirty flashed on top of 9.1 and it rebooted twice (without reaching the UI, no boot logo displayed either) and was back to recovery (TWRP).

Is a Gapps flash required? I did not do it as ROM flashing alone should do. Also, did you have a private build from your new branch before flashing 9.2? Am not sure if the branch change is causing this.

-- Update --

I (dirty) flashed back 9.1 and it works perfectly fine! Not sure if I'm the only one having issues flashing 9.2. Will wait for confirmation.
[ONE Android Development] netbuzz:
Format /system and then flash 9.2 + gapps. Your apps and data will still be there.
[ONE Android Development] GirishSharma:
Thank you sir for your reply. I requested for well known mobile radio active aka MRA bug, which causes for high battery drain:

https://code.google.com/p/android/issues/detail?id=190396
[ONE Android Development] RukusX7:
[MENTION=3814731]katinatez[/MENTION]

CM devs for my device left everything the way it was except for this commit. I've stopped building temasek, so i dunno how it works with temasek.

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

Just thought I'd share. maybe this is something that would work for you, so you happen to choose to go back.
[ONE Android Development] ashutoshmn:
Master [MENTION=3814731]katinatez[/MENTION]

What is the current libraries for camera that you are using, oxygenos libs or cm ones? Cuz the thing is I'm on build 18.6 and while using snap camera, the graphical glitch (random lines) while focusing sometimes is visible. I've never had such issue with oxygenos cam libs, so to make a guess you might be using cm libs, yes? Can we see our ROM implementing oxy libs in future?
[ONE Android Development] fischwrap:
Dirty flash worked fine so long as I didn't flash boeffla kernel. Flashing the kernel cause a boot back into recovery. It's weird. But 9.2 running well on it's own so far
[ONE Android Development] katinatez:
I will look at this closer on my days off

Thanks for pointing this commits out

Using cm currently. Definitely will switch this on my days off (my wife still using 1+1)
[ONE Android Development] djha53k:
Thank you, gonna use your build again, I´m not sure that I did the branch switch correctly :rolleyes:
[ONE Android Development] GirishSharma:
Sir,

It would be greatest commit if you please look into MRA bug, which is highest threat to whole android community. I am sorry, if it will keep you busy in your free time, but I am sure, world will be highly thankful to you. I am hope, you, temasek, chainfire, AK, Andi (boeffla) and some other wonderful xda members discuses, Google will reward your team as a International Android Award.

---------- Post added at 04:41 PM ---------- Previous post was at 04:41 PM ----------

Sir,

It would be greatest commit if you please look into MRA bug, which is highest threat to whole android community. I am sorry, if it will keep you busy in your free time, but I am sure, world will be highly thankful to you. I am hope, you, temasek, chainfire, AK, Andi (boeffla) and some other wonderful xda members discuses, Google will reward your team as a International Android Award.
[ONE Android Development] chenrp:
Anyone uses v9.2 with boeffla kernel? I get boot loops with v9.2 and boeffla kernel. With v9.1 no issues.
[ONE Android Development] THB211:
GOOD

Good to force the issue in China drawback I phone 4G signal sometimes automatically dropped the other rom no problem hope that the author of view is what the situation!
[ONE Android Development] djha53k:
Check few posts above!!!

The v9.2 is different branch, you cannot use other kernel!

[MENTION=2332422]temasek[/MENTION] [MENTION=3814731]katinatez[/MENTION] > battery drain is gone with v9.2 [19:30 took off charger ... 7:05 => still 100% ]... great! [emoji106]
[ONE Android Development] chenrp:
why is it different from CM13.1 nightly?

why should it be on a different branch?

what kernel do you recommend using in this different branch?
[ONE Android Development] djha53k:
- this it [MENTION=2332422]temasek[/MENTION] ROM build by [MENTION=3814731]katinatez[/MENTION] so, they are who should provide fully qualified answer, I´m still to young in this topic, I´m able to build ROM, but I still not understand how it works ... :(

- to fix the GPS battery drain :good:

- standard CM13 kernel :cowboy:
[ONE Android Development] timbuctoo:
Thanks for the confirmation

So that was the culprit. I was indeed using Boeffla kernel!

Thanks for the confirmation. Several other users have encountered the same issue.

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

Thanks. Are you using Boeffla kernel with this workaround? It's causing bootloops.
[ONE Android Development] ashutoshmn:
Use Andy Kernel w/ Kernel Adiutor Mod, works fine on v9.2

Edit: Though I haven't tested the latest version of Andy (20160614), I'm using this ver HERE

You can test the latest one and report.
[ONE Android Development] cybot_x1024:
9.2 runs a lot smoother and drains the battery a lot less. I was beginning to get frustrated by previous builds. Even after downgrading to 8.3 I still had settings FC several times a day and still couldn't use GPS without my phone heating up and draining my battery.

Without an under clock 9.2 with 50% battery on 3G lasts longer than the last few builds I've flashed at 100% battery under clocked & undervolted while on WiFi

Thank you very much [MENTION=3814731]katinatez[/MENTION] and [MENTION=2332422]temasek[/MENTION] for this.
[ONE Android Development] djha53k:
camera

About hour ago I made some videos... and I have to say it is quite bad :crying:

Camera re-focusing all the time of video, so it is almost not watch-able :( :eek:

Any idea which better camera to use? :confused:

Thank you.
[ONE Android Development] TheQuarterMile:
Are you using Color Os camera?
[ONE Android Development] djha53k:
Nope, I´m using in build [MENTION=2332422]temasek[/MENTION] CM camera, but I will have to find other one, as this is horrible :(

edit: I just tested OpenCamer and CameraMX and both do same re-focusing all the time (example attached)... :( so it seems it is some HW issue of my One :crying:
[ONE Android Development] Sicron:
Version 9.2 seems to have fixed the battery issues concerning wifi location! So far, 5 hours in and I have 30 minutes of wake time. I'll update after I wake up again to see how it did overnight.

Are you sure you do not have any smudging on your camera lens? Try cleaning it, it may help with focusing. I've had focusing problems before because I had a big fat fingerprint on my lens.
[ONE Android Development] djha53k:
[MENTION=3505186]Sicron[/MENTION] yes, I'm sure it is clean, no finger print, no dust, nothing... I tried to re-clean it, but still same [emoji22]
[ONE Android Development] ArimanRandez:
Hi, i'm on V9.2 and it's work ok, but if i flash boeffla....not reboot
[ONE Android Development] HTCTOUCHPRO91:
flash boeffla cos 13.1 kernel. it works ;)
[ONE Android Development] kryptonite02:
Hi [MENTION=1711586]kartin[/MENTION]atez, i have something problem about this rom 9.2. i don't outgoing call. after i press outgoing call sudenly my phone restart. do you have fix this problem. Thanks before
[ONE Android Development] stab244:
That works? Guess I'll try that.

Edit: It works. Thanks.
[ONE Android Development] chenrp:
So boeffla cos kernel works with this rom? Why? Is this rom based on cos now?
[ONE Android Development] kalapapa:
It works cause temasek changed I guess from the nightly branch to the stable branch which is what COS is based off of
[ONE Android Development] katinatez:
I changed the entire device branch to remove battery drain, besides nightly branch is used for testing commits and usually have more bugs.

Thanks for feedback

I will be making changes to camera libs in the next release, to address this issues

Thanks for feedback

yes, already answered switched to stable branch to remove as many bugs and next step is to fix camera.

Trying to leave a solid build of temasek on bacon, and then retire.
[ONE Android Development] Warsonex:
How to root the ROM?
[ONE Android Development] FrenchSparda:
Your LP ROM's (18.6/ 18.8 non-CAF or CAF) are such great stable builds. Perfect for daily usage on my wife's OPO ;)
[ONE Android Development] katinatez:
Actually supposed to release update for LP 5.1! It's up to v19.5. Will release on Monday, my day off
[ONE Android Development] djha53k:
Thank you for camera fix... :good:

Seems that [MENTION=2332422]temasek[/MENTION] ROM for OP3 will come, so seem I should start thinking of upgrade my mobile after 2 years with OPO :cowboy:
[ONE Android Development] stab244:
Just got mine. Very nice phone for sure. Good to hear this ROM coming to the OP3 too.
[ONE Android Development] djha53k:
I dunno, do you? :confused: I just wrote>>>

Nothing about it will :cool: [MENTION=2332422]temasek[/MENTION] neither [MENTION=3814731]katinatez[/MENTION] confirmed/denied this information yet...

:fingers-crossed: :fingers-crossed: :fingers-crossed:
[ONE Android Development] stab244:
I see. One issue I do have with the OP3 is that the screen doesn't get as dim as the OPO. At least unless I make the screen black.

Edit: I lied. It does get dimmer but have to turn off adaptive brightness. Sorry for off-topic. Just going to say that 9.2 fixed location battery drain for me.
[ONE Android Development] chenrp:
1.Ok... So this rom is cos now... Why not change the thread name?

2.what is lp5.1?

3.what's wrong with the camera?
[ONE Android Development] kalapapa:
1. COS and CM are two different things, don't confuse the two. All he said was that he changed the build tree from nightly to stable and it just turns out that COS is also based off the stable branch

2. Lp5.1 is Android lollipop 5.1

3. Idk what's wrong with camera
[ONE Android Development] djha53k:
[MENTION=348788]chenrp[/MENTION] camera re-focus all the time when I'm taking video, pls find my example video couple posts back
[ONE Android Development] Neon Strive:
What configuration do you have on Boeffla Kernel for this ROM?
[ONE Android Development] tssphysicsboi:
For those with clash royale lag on wifi, I believe it is rom based issue since I'm back on COS 13.1 and there is no More lag on wifi
[ONE Android Development] Klewe:
Bluetooth bug

Maybe I found a bug with Bluetooth.

When listening to music over Bluetooth the time is shifted. Will explain better: when I start a song you hear the song on the device connected to Bluetooth but the time of the song on the player goes on less than half of speed. The result is that after the song is finished you have silence for a long time until it switches to next song.

This does happen on 2 players I tried, one is the native one, the other is double twist.

The error does net occur when not connected to Bluetooth neither on one nor the other player.
[ONE Android Development] necosino:
This is an android bug, if you google it it's nothing new. Either plug in a 3.5mm, use an app that can offset the video/audio, or just deal with it.
[ONE Android Development] Klewe:
Ok, I see, but do not understand why it didn't happen until this last version of the rom...
[ONE Android Development] lolihunter:
Holy cow, if you could do this it would be amazing. I am still using the caf 12.1 build as it gives me hands down the best battery life. If you update the 5.1 I would flash it faster than light.
[ONE Android Development] katinatez:
oh right here is the update to cm-12.1

Here

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

and here

https://www.sendspace.com/pro/dl/apz4lj
[ONE Android Development] kalpik:
Love how a lot of "DO NOT MERGE" commits were merged :laugh:
[ONE Android Development] necosino:
Maybe they mean not to merge it into the main branch, since it's being built off a separate branch, now?
[ONE Android Development] Fufu2:
What a smooth Rom , top function and good batterie.

Great Job
[ONE Android Development] DarKAngel1234:
What Camera/HAL/Blobs, does this rom currently use?
[ONE Android Development] Fufu2:
Cyanogen snap cam Version 2.0
[ONE Android Development] katinatez:
I left the camera alone, still running cm HAL, & blobs with Snap camera.
[ONE Android Development] timbuctoo:
Worked great!

That worked like a charm! Had tried dirty flashing 9.2 (without any third party kernel or Gapps flashed) on it's own, but to no avail.

After becoming almost hopeless for getting off 9.1, am finally on 9.4 with Boeffla's COS kernel. Many thanks for helping out. Have already hit the 'Thanks' button.
[ONE Android Development] godzulu:
using latest download and latest gapps - clean flash. Gapps wont install - getting error code 64. Any ideas? Thanks :)
[ONE Android Development] don2dare:
bro....

please release caf version of 5.1.1 too for us

it's better as it is compatible with lightning kernel caf

Thank you..
[ONE Android Development] timbuctoo:
Viper4Andoird not working

Is Viper4Android working for anyone? It's hanging everytime I start.

-- Update --

Re-installed busybox and Viper got installed
[ONE Android Development] phierce:
Why don't we have truecaller?
[ONE Android Development] juliusedward:
Can be installed from play store.

It's promoted by COS not CM
[ONE Android Development] ljstreak:
If coming from latest RR, do i need to flash firmware too? Please help me,,forgive me of this basic query
[ONE Android Development] Adduu:
Please edit your post and remove the quote of the first post. It makes it too long to read.

As for your original query, you don't need to flash firmware. Just don't forget to take a nandroid before you flash this rom. That way you always have a backup in case something goes wrong.