yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] nazfalas:
Thank you for the reply. Just wondering, because I can't replicate my heat related touch issues (some preliminary testing). Only fix until now (yes, I tried every CM11S, CM11, COS12, ColorOS, OxygenOS, etc.) was the new firmware where I had to disable screen gestures/double tap to wake to stop the drain.

Very smooth btw. :-> Will have to see how battery life holds up through the day and if the touch issues are magically cured. :D
[ONE Original Android Development] Aka91:
[MENTION=4800121]Sultanxda[/MENTION] ...I am on CM12 2015-15-04 nightly,Franco r42

Can this be flashed on top?
[ONE Original Android Development] Sultanxda:
I rewrote half of the Synaptics touchscreen driver in the kernel (over 2500 lines of code modified), but I don't think my changes could've helped with the touchscreen issues. I have a friend who has a serious case of the ghost touches, and my modifications did nothing for him :/

You must be using the CM12.1 nightly, not CM12.
[ONE Original Android Development] Aka91:
[MENTION=237269]sultan[/MENTION] no i am on cm12 builds..
[ONE Original Android Development] Sultanxda:
Derp, my English has failed me :p

You need to be on the CM12.1 builds.
[ONE Original Android Development] Aka91:
Haha..

Ok

Thanks. ?
[ONE Original Android Development] nazfalas:
As we have learned from the ghost touch discussions and the new synaptics firmware: there are apparently many different kinds of touch issues. Some heat related, some static related and some grounding related. Others just plainly have a completely faulty digitizer.

In my case it is heat related. I was able to replicate it multiple times by gently heating it with a hair dryer (even mild heat caused the issue) - cooling the device also removed any touch issues. For me it was also the special case of the x-axis issue where only one finger was recognized when both where on the same x-axis. This does currently not happen on your kernel - no matter the heat (not heating to the point where anything could be damaged, of course ;) ) making my OPO very usable again!

10 finger recongnition is still a little faulty, but who honestly needs that. :D
[ONE Original Android Development] adinkwok:
[MENTION=5438598]RenderBroken[/MENTION] :victory:

[MENTION=4800121]Sultanxda[/MENTION] you sir deserve a
[ONE Original Android Development] Aka91:
[MENTION=4800121]Sultanxda[/MENTION] Sorry to bug you again.

but CM says that 12.1 can be flashed over CM12.

So can i flash on top?
[ONE Original Android Development] Sultanxda:
Lol, didn't notice that 10-finger recognition was faulty. That's a firmware issue that I probably can't fix through the kernel driver. The firmware sends touch data (number of fingers and their coordinates on the screen) to the kernel driver, and then the kernel driver parses this data and registers the touches accordingly. So if the kernel receives faulty data from the firmware then there's not much that can be done (trying to filter out bad data through the kernel driver is very difficult).

Funny that my changes actually made a difference for you, I totally didn't expect that. Now we wait to see if it'll stop working again after a day's use :p
[ONE Original Android Development] Sultanxda:
wat

Flash the official 5/28 CM12.1 nightly first, then flash my ROM. The official CM12.1 nightlies contain firmware updates that are necessary if you are coming from CM12.
[ONE Original Android Development] Aka91:
Ok Tenks.

:)
[ONE Original Android Development] _ASSASSIN_:
Omni has a read me that can explains how to set it up

https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-5.1
[ONE Original Android Development] Sultanxda:
New build uploaded. CM fixed the DHCP WiFi issue :victory:

Read it and I still dunno how to set it up (and it looks too tedious to set up).
[ONE Original Android Development] skeetzor:
Yeah I wouldn't bother.

AFAIK, you gotta use a proper server with it anyway, you can't delta update using AFH and the likes
[ONE Original Android Development] real_sl4cker:
Wow, sultanxda developing for the OPO. I loved your ROMs on the HTC Sensation and am very excited to try your OPO ROM ?

(mobil gesendet / sent from mobile)
[ONE Original Android Development] _ASSASSIN_:
[MENTION=5438598]RenderBroken[/MENTION] offers his server for free for people here on xda to use. :D

That is if you want to use opendelta.
[ONE Original Android Development] PhillyFlyer:
I still use Sultan's HTC-Sensation ROM. hehe
[ONE Original Android Development] primo14z:
I am very pleased with the ROM , but i have a strange problem with overheating when using any kind of games...
[ONE Original Android Development] dev.meena:
The rom download keeps failing.
[ONE Original Android Development] joefso:
[MENTION=4800121]Sultanxda[/MENTION]

What are your thoughts on roms known for their battery life, such as exodus vanir? Can you see what they have done to increase the juice and integrate it in this rom? - perhaps even improve and contribute - My personal experience with the exodus rom has been that my battery life is way better and I would like to see this in this rom too. Thanks for the great contribution.
[ONE Original Android Development] MobileThrowAwayAcc:
Just a bit more constructive feedback- I wish the kernel had a bit more options available. I feel like my battery use is a bit higher with this ROM than with others. Obviously the UX is buttery smooth and that trumps battery in my book, but if small things like being able to undervolt, change the IO scheduler and TCP algorithm, disable kernel same page merging, enabling laptop mode get me a bit more battery, I'd be pretty happy.

Also, I still super miss the options of the cm cam, but am happy to wait and see what you come to with.

Thanks for an awesome ROM!

Edit: also, the update feature has worked flawlessly the last two times for me.
[ONE Original Android Development] byAidan:
Hi [MENTION=4800121]Sultanxda[/MENTION] first of all I love this ROM it is by far the best in my opinion :D

However after leaving my phone locked when I go to unlock it the touchscreen appears to be disabled, the system is still working (can change volume up and down etc) but the touchscreen doesn't work at all so you have to hold power etc to turn it off.

This happens rarely and has only happened twice so far, someone a few posts/pages back also had the same problem.

I have attached a logcat and kmsg, not sure if they will be any help though!

Running latest build, everything stock.

Last KMSG:

http://pastebin.com/y8f3Wd58

Logcat:

http://pastebin.com/ykW7UFDW

Thank you for your time!

EDIT: Here is the other post
[ONE Original Android Development] Sultanxda:
Never tried a different ROM, so I have no clue. Power efficiency in my kernel should be pretty good, and my personal battery life is good (5+ hours SOT, and I even have bad cell signal), so I don't think I'll be tweaking battery-related stuff any time soon.

Undervolting the CPU is silly; the benefits can barely be measured and the impact on stability can be tremendous. The CPU is too important to play with.

ROW is the recommended I/O scheduler from Qualcomm for B-family chipsets, and our eMMC is plenty fast and functioning fine with ROW. You can change it to Deadline if you want, but I won't be adding a zillion I/O schedulers.

You won't notice a difference between TCP congestion algorithms unless you have really, really special network needs (you probably don't).

Kernel samepage merging (KSM) makes absolutely no sense on this device, so the feature is not even available in my kernel.

Laptop mode is for spinning down HDDs to save power. We use solid-state storage, so this feature doesn't do anything for us.

I miss the options of the CM cam too, but I'm going to be traveling overseas in less than 2 weeks, so I really want my camera to work perfectly. When I first got the OPO, I recorded a few videos with CM's camera libraries and I saw those glitches; I'd be pretty disappointed if I found glitches in my videos while traveling. These glitches have existed even since CM11S, so until CM acknowledges them and fixes them (or until I fix them myself), I won't budge from the shiny oxygen camera libraries.

I tried fighting this issue again with the new build (see the kernel changelog). Does it still happen with the new build (6/04)?

EDIT: I'm blind, you are running the latest build. Do you have DT2W or gestures enabled?
[ONE Original Android Development] efrai3:
[MENTION=4800121]Sultanxda[/MENTION]

Problem with unresponsive touchscreen also occurs to me with 3/6 build.Couldn't unlock phone and have to hold power button to reboot.Otherwise rom,rocks!!!

Had DT2W enabled but no gestures.
[ONE Original Android Development] 69gm:
Me too! LOL! Runs fine!
[ONE Original Android Development] byAidan:
Haha it's okay and I only have DT2W enabled, I also dirty flashed from the 2nd to latest (wiped caches) if that's any help

Thanks for your help
[ONE Original Android Development] chaka809:
Same here on latest build when the phone goes to sleep I have to click the power bottom lime 20 times so it can turn on. Sometimes it just soft reboots.
[ONE Original Android Development] Sultanxda:
Think I've got it fixed: https://github.com/sultanxda/androi...mmit/35f7da32e8a388abdafdc80c0a039f5908cd62dd
[ONE Original Android Development] 69gm:
LOL. My reference was that I still use your old ROM on my Sensation. But hopefully this is good news!
[ONE Original Android Development] Sultanxda:
Derp, I quoted the wrong guy :silly:
[ONE Original Android Development] 69gm:
Don't be silly...I'm NEVER the wrong guy! LOL!
[ONE Original Android Development] The_cobra666:
When I remove the password and then reconnect, the wifi works without any issue. It only happens after flashing a new ota or rebooting the phone.
[ONE Original Android Development] endriuss:
If you are referring to the situation that when you turn on wifi mobile data is still active there is a workaround:

https://forums.oneplus.net/threads/mobile-radio-active-the-fix-is-in.323219/

First of all I would like to say thank you to all Devs involved in this project. This rom is wonderfull! I haven't noticed any single bug and battery life is awesome!

Also I would like to share my experience with battery usage on all 5.1.1 roms. The main problem for me for the last 3-4 months is/was idle battery drain.

I've noticed that when I do the clean install without installing Gapps then the idle battery drain is 6-9 mA (I'm using Battery Monitor Widget from 3c)

When I install Gapps reboot the phone and configure my account everything is still ok - idle battery drain is still 6-9 mA

Unfortunately when I reboot my phone - then idle battery drain is 17-19 mA please see attachments

I thought that this was related to my apps (but even without installing any the problem stil presist). I've tried different kind of Gapps - still the same.

I've tried different kind of firmware (installed through the fastboot) - no change

Finally I've found a workaround which work for me:

1. Clean install of the ROM

2. Install all your apps

3. Install Gapps

4. Reboot and enjoy the iddle battery drain 6-9 mA (untill you reboot :) )

(When you accidentially reboot your phone then simply format system partition, flash rome once again, boot up, reboot, install Gapps, boot up, configure account once again and you are ready to go... until next restart)

I know that this is silly but this works for me and I have OnePlus battery on this ROM like it was on KitKat.

Please find my first discharging cycle with this awesome rom: 3h35m SOT and still 54% left - everything stock (kernel, recommended Open Gapps)

My assumption is that idle battery drain is something about correlation between pure rom and Gapps.

I'm not developer so please forgive me if I'm ridiculous but this is how I feel.

If you know permament solution in order to have idle battery drain 6-9 mA of any 5.1.1 rom, please share your experience :)

Once again! One of the best roms out there! Keep up the great work. Really appreciate!
[ONE Original Android Development] wingedpanther:
Let me try your methods because am also have this issue :good:
[ONE Original Android Development] damage98:
You should ask this question in the multirom thread. Answers are there. FYI I'm running exodus main only so I can boot this rom in secondary this is my daily driver and has been since sultan uploaded v1 so not really sure why I run multirom[emoji58]
[ONE Original Android Development] Vivek_Neel:
Flash boeffela kernel based on your ROM in primary slot.

And flash this ROM in secondary slot.
[ONE Original Android Development] sramtam:
I have boeffla kernel already, my target is to make this ROM primary
[ONE Original Android Development] Biiz:
this is interesting....

are u able to install the other apps before installing the GApps? i don't remember if it's possibile :/

but, if the smartphone reboot, u have to do it again? :(
[ONE Original Android Development] endriuss:
You can install as many aps as you need before installing the GApps. Also when you finally flash gapps and boot up your phone, configure google account - you can use your phone as usual - updating existing apps and installing new through play store. The case is that when you reboot your phone after that - the idle battery drain will be 16-19 mA instead of 6-9...

First of all I would like to ask you to install Battery Monitor Widget from 3c, leave the phone for about 30 minutes and check what is your idle drain under history tab.

Please also note that when testing I don't have any sync, wifi, mobile data enabled
[ONE Original Android Development] gondsman:
[MENTION=4800121]Sultanxda[/MENTION] I'm super happy with the latest version, the compass finally works consistently!

One thing I think could be made better is if the sensor register is cleaned during the flash as part of the install script rather than as a part of the boot sequence. While the compass works now, it requires recalibration everytime I reboot (which is still infinitely better than before).

Anyway congrats for finally cracking the issue, your work is amazing!
[ONE Original Android Development] Biiz:
what do you think about my consumption? i whink it's a little bit higher :(
[ONE Original Android Development] gwindlord:
Same for me, seems to be even on clean install, but not 17-19 mA - the lowest possible idle drain for me is 25 mA (and the highest is up to 400 mA) - with data, WiFi, sync and location turned off. Will try the reinstall soon. Could you please check the logcat in the meantime? One logcat for 6-9 idle drain and for 17-19 for maybe 30 minutes - to compare and possibly find the guilty app.
[ONE Original Android Development] endriuss:
I see that your case is different. You have a lot of wakelocks from the New Republics, Google Play Services and App Google.

You have to solve this issue first. Try to block Auto Start, Do not sleep and wake up for those application under Setting/Privacy

The problem I'm referring to in my post is completely different.

I have no wakelocks at all and clean system, wifi,mobile data, and sync off - then I'm checking idle battery drain for this configuration.
[ONE Original Android Development] ZenR2:
Hi to all , am new to OPO world recently got the device and after using Cyanogenmod 12.1 the first rom to try is this , totally satisfied great work [MENTION=4800121]Sultanxda[/MENTION] :)

but facing ghost toch/sensitive touch issues, is anyone else facing this , can anyone help me out with it .

thanks :)
[ONE Original Android Development] sdbgl:
Finally Compass is working as intended in today's build... great work [MENTION=4800121]Sultanxda[/MENTION]... Thanks..
[ONE Original Android Development] venky716:
Yup its the same for me.

17-20 Idle drain with data, Wifi, sync off.

21-30 with Wifi and sync

30+ with data

Reboot with airplane mode on gives me 6-7 though, but as soon as I switch on Wifi or data on its back to 20+

I've tried with non CAF ROMS and it's the same.

I'm guessing it has to do with Google play services.
[ONE Original Android Development] endriuss:
You have higher idle values on clean install probably because you are configuring your phone slightly different. I mean that during first start of rom I always disable:

GPS, mobile data, NFC, Live Display, Addaptive display, accident wake-up, and all gestures (excluding DD2W). I don't mind using those features in the future but for test purposes i disable them at the beginning.

---------- Post added at 03:14 PM ---------- Previous post was at 03:09 PM ----------

Because of that fact I've started this discussion :) I feel that we loose our great OnePlus battery because of the google fault :( Hopefuly one smart DEV will solve this :)
[ONE Original Android Development] gwindlord:
I've tried to disable them too and got no difference unfortunately (can't wait to resume my tests again). This should be something with gapps, that's why I've asked the logcat - at least any chance to find that Small App with a Big Hunger.
[ONE Original Android Development] endriuss:
Please find my logs I've did using SysLog. What I did between these two logs - I just simply restarted my phone. During booting 3 of my newly installed apps was probably updated but this shouldn't be the problem to diagnose.

Unfortunately I'll be unavailable for few hours from now but feel free to check the logs...
[ONE Original Android Development] DerRomtester:
The last_kmsg isnt helpful at all. It is from a different rom.

Linux version 3.4.108 (kingbig****@brokenos) (gcc version 5.1.1 20150715 (UBERTC-5.1.1) ) #1 SMP PREEMPT Fri Jul 31 13:38:03 CDT 2015

Maybe i can find sth on the other logs.
[ONE Original Android Development] infatality:
Able to push both commits to gerrit? I only saw one been push. =D
[ONE Original Android Development] jark99:
Not really a fan of the work around! As pretty much what this does is Disable Mobile Data when connecting to Wifi, which I could technically do myself when I come to my home wifi. Its interesting development though and keeping an eye on how it progresses, appreciate the automation aspect
[ONE Original Android Development] Galactus:
Yep I already have this set up using the built in "System Profiles". I have a profile that disables mobile data when I'm on my home WiFi
[ONE Original Android Development] jark99:
Omg, I keep forgetting about System Profiles! I should really utilize that a lot more.... smh
[ONE Original Android Development] hammer-is:
I think the same workaround can be done by Smart WiFi Toggler (Settings->Miscellaneous->Toggle Mobile Data (when connected to WiFi)).

This app main functionality is to enable/disable WiFi based on cell tower information.
[ONE Original Android Development] jark99:
Awesome app! This is why I love XDA. This app does everything in one. Thanks!
[ONE Original Android Development] endriuss:
This is because I use mulitrom and my primary rom is brokenos and secoundary this one. I've tried almost every rom to check if idle battery drain presist...

But the zip files with logs were generated automatically so they are for sure only based on this rom. When I have time I'll try to clean install as a primary and do all these tests again.
[ONE Original Android Development] Sultanxda:
Yeah, Danny Baumann told me the proper way to update the sensor registry (I forgot to change the version strings). Here is the correct version: https://github.com/sultanxda/propri...mmit/2d48d254d3d330d3d2304e64fef68978611a4d1f

I thought I updated the version string before and it did nothing. Oh well, this is why I shouldn't be programming at 1am in the morning :silly:
[ONE Original Android Development] sdbgl:
Thanks for all the hard work.. Take care of yourself :)
[ONE Original Android Development] skanadian:
I have the same problem. If the phone is landscape above my head north and south are switched.
[ONE Original Android Development] patstar5:
My GPS isn't working anymore after latest update
[ONE Original Android Development] move_some:
This is caused by Google play service (gps)

You can try to disable it and you'll see that it will drain 6-10 mA.

I have the same issue and I modified my gapps. I replaced PrebuiltGmsCore.apk with Version 7.3.23 as with this Version the drain is low.

After flashing the modded gapps, set up you Google account, then update gps to the Version you want to use.

Drain will stay low (until reboot). The strange thing is that you will keep the low drain while ota.

If you reboot and see the drain at 20mA while idle, just delete user data of gps, deactivate it (updates will be removed), reactivate it and reconfig you Google account and after that, update to your Version, again.
[ONE Original Android Development] redlag:
I don't know weather it's related to the rom or the applications instead but I am having issues where applications like Facebook and browser would have trouble with loading stuff and the loading would go on and on. I need to kill the app and restart it and then it'll work fine. It's happening to me from 10-15 days. Today experienced it with instagram too!
[ONE Original Android Development] kalpik:
So the other commit isn't needed anymore after this?

Sent from my A0001
[ONE Original Android Development] Sultanxda:
Correct.
[ONE Original Android Development] LenMetallica:
Thank you! This worked perfectly. CM12S booted just fine after I installed Boeffla and I didn't reset anything.
[ONE Original Android Development] fards:
So are you reuploading 5th build with correct change?

Just changing the last commit manually on the 804 build fixed compass for me .
[ONE Original Android Development] rajarshi10:
If I flash SlimGapps which has CameraNextMod in it, will it replace the existing camera app on this rom?
[ONE Original Android Development] Sultanxda:
Nah, I'll just make an Aug. 6th build with it. I'm not sure what's left for me to fix though, so that might be the only change :p

It won't.
[ONE Original Android Development] simmer14:
dude this last update is just awesome just took a 9.21mb pic wt snapdragom camera wt iso 100 awesome work man hats off..
[ONE Original Android Development] mikecantreed:
Sorry for the dumb question but could someone provide a link to the snapdragon camera?
[ONE Original Android Development] CNDow:
its an attachment to the above post
[ONE Original Android Development] 69gm:
Just FYI, that SnapDragon camera is different than the one baked into Sultan's ROM. Sultan did some modifications on his version so if you use that one and have issues, there is nothing he can do.
[ONE Original Android Development] Sultanxda:
Thank you! CM's camera HAL does not support HSR, and the A/V framework didn't properly support it either; I had to fix both my HAL and that low bitrate issue to get it working without it being potato quality. Also, a new app was needed to support it (Snapdragon Camera) since none of the existing camera apps have it, so there were actually quite a few things needed for HSR.
[ONE Original Android Development] 69gm:
"Potato quality"? :confused::D
[ONE Original Android Development] jark99:
Google really needs to hire this man! Such a good job you've done here Sultan. No other Rom has this feature!
[ONE Original Android Development] runderekrun:
Wi-Fi is still draining bad on my work/corporate Wi-Fi. Anyone else?
[ONE Original Android Development] nsmart:
To those who use device encryption and want to give this rom a try: I dirty flashed from cm-12.1-20150802-NIGHTLY-bacon.zip to cm-12.1-20150805-UNOFFICIAL-Sultan-bacon.zip without errors. Reverting back to cm12.1 nandroid was successful, too.
[ONE Original Android Development] dontwatch:
WiFi networking stops after several hours

Brand new phone, vintage Nov 2014.

After several hours connected to an access point, the network fails - it retains it's ip but will not support traffic in or out.

Have not yet checked against a different WiFi...

Anyone else have some feedback about WiFi connections?

Oh, and thanks very much for the ROM and your work!
[ONE Original Android Development] SomeFormOFhuman:
[MENTION=4800121]Sultanxda[/MENTION], Your compass is working perfect! Thanks! I've updated the annotations on my video and linked to your thread. Hopefully this will help spread the word on a work well done!

https://www.youtube.com/watch?v=cXsB2LG1ftM

You're awesome!