yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] néonaloj:
You did not read about how to do with multirom!

1. prepare a cm12.1 nightly as a secondary

2. swap this rom with your primary

3. in primary recovery: wipe factory reset, install [MENTION=4800121]Sultanxda[/MENTION] 's rom+ gapps

4. swap then rom as secondary with your original primary

5. done, reboot.
[ONE Original Android Development] dark_saian:
The theme I tried worked just fine with 11/07 build

What is rebooting in safe mode? Never heard of that option on Android.

Edit: Just found about safe mode. Awesome thing to know. Thank you so much !
[ONE Original Android Development] siju2012:
Unfortunately,still it dint solve
[ONE Original Android Development] Mauzii:
You can use it as a daily driver for sure, just some minor bugs here and there.
[ONE Original Android Development] Solid-Dado:
I disabled the WiFi and Bluetooth scanning but the miscellaneous drain still persist
[ONE Original Android Development] Perilla_:
That settings are under Location -> Three dots -> Search.

Turn off the phone. Turn it on, and when you see the first logo press and hold VOL down until it boots.
[ONE Original Android Development] lullo88:
I have an huge battery drain of 44% due to "Miscellaneous"... Please help on how to fix that!
[ONE Original Android Development] nikhil18:
Just remove debug from ro.build.type in build prop and it will solve miscellaneous battery drain
[ONE Original Android Development] albi97x:
To work with multirom is this Jo correct?

1) flash the latest cm 12.1 nightly as secondary

2)Swap it with the primary ROM

3)in the primary ROM wipe factory reset (no system)

4) install sultan's ROM + gapps

5) swap as secondary the sultan's ROM

6)Reboot

Is this Right?
[ONE Original Android Development] XDASaber:
same issue..
[ONE Original Android Development] Khizar:
Read my reply above, the app needs to be updated.
[ONE Original Android Development] XDASaber:
see,then I'll be waiting for the upadate:eek:
[ONE Original Android Development] davidvoo:
Is this kernel going into any current or future releases?
[ONE Original Android Development] DerRomtester:
It isnt just the thermal driver that has Sultan written by himself. CM is also based in CAF sources but they do sometimes weird things that arent necessary at all e.g. huge backports, merging the upstream changes from the 3.4y linux branch; weird patches. And if it aint broken dont fix it. So all in all we can say that sultans source is more close to CAF and more clean with less bugs. Also the thing i like most is the camera. The pictures are 10000 times better just try it. It is a difference between night and day.

I guess yes :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] kenzolo:
[MENTION=4800121]Sultanxda[/MENTION]

Hi mate,

do you think you will re-add panorama feature in your camera? I use often it and so I always need to install two camera app :(

Thanks anyway
[ONE Original Android Development] droidzeus:
Iam on the 11/1 build

And having constant crashed of root explorer

Also

As soon as I change DPI from setting or remove any app from system, the phone stucks on bootloop
[ONE Original Android Development] Khizar:
Could you please read before reporting bugs. I've mentioned that root Explorer FC is a app bug twice already today. The app needs to be updated.

As for changing dpi and/or removing system apps, I don't have bootloop.
[ONE Original Android Development] alonroz:
Not the same wakelock, the service name is different in your screenshot. Search for that service.
[ONE Original Android Development] Genericxx:
Facebook and Facebook Messenger uses Analytics thus wakes up the device more often as necessary. Download Disable Service from Play Store, give root permissions, and disable Analytics for Facebook and Messenger and you're fine. But as mentioned before: There's absolutely no need for the Facebook Client. It's a battery drainer in general and you will gain much more battery life if you get rid of it and use the mobile site via chrome for example. Nearly same functionality, no battery drain and you even get notifications through it.
[ONE Original Android Development] mekanismen:
Can confirm this. Removed the Facebook app last week and it's had a dramatic effect on my phone's battery life.
[ONE Original Android Development] Cissiboy:
+1

which other app do you use for panorama ? snapcamera sucks in that and abcu is a bit cumbersome.

I used to use photaf panorama back in gingerbread ages but i think it got stuck there..
[ONE Original Android Development] Voyager03:
I flashed it last night and the phone made it well past the '50%' switch off time this morning.

However before I ran it flat yesterday I had been looking for where the problem might be and had deleted 'batterystats.bin' before it died and once it was on charge (switched off) let it charge for longer than usual (I left it for around 3hours) as I read somewhere this can help - I've no idea if they or the kernel have helped but it does seem better at the moment.
[ONE Original Android Development] Genericxx:
Notification from DevDB this morning but no Update? :confused:
[ONE Original Android Development] hamma:
The batterystats.bin has nothing to do with it: https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
[ONE Original Android Development] Voyager03:
It may, it may not. I don't know what to believe these days. There are so many people willing to give advice without any real knowledge. But I read more than one bit of advice to remove it (including one on this monster thread I think) before I did it.

Another has been created, so it doesn't matter much.
[ONE Original Android Development] Genericxx:
batterystats.bin is nothing more than a container which collects usage to display the battery stats. it will be deleted by the system each time you've charged your phone over 95% and unplug the charger. so deleting the file means absolutely nothing. everything you get is a blank statistics view for a couple of minutes.
[ONE Original Android Development] Voyager03:
Yes, I am capable of reading that too. :p

I posted what I did so [MENTION=4800121]Sultanxda[/MENTION] would be fully informed of the few things I did to my phone in an attempt to get a working battery % along with flashing his new kernel, I even said 'I've no idea if they have helped' because I have no idea if they did. I'm sorry if that upsets some of the tedious pedantic know-it-alls, but if you were more bothered to post when people have problems rather than flock to whine about something that I already said it might be more useful, eh?
[ONE Original Android Development] xxDominatorxx2:
Off topic

What's the best settings for the camera on this rom?

Or do you guys just leave it at default?

Also how is the general quality compared to say COS camera or cameranext mod?
[ONE Original Android Development] KnightGalahad:
Great Stuff

I'm running my OPO with this ROM and Kernel and I have to say, it's pretty great. :D It's completely stable, and battery life is 5+H SOT. The one issue that I have is that the option for quick unlock for a PIN is gone from CM12.1. Not a big issue at all, but I'm just saying. :p
[ONE Original Android Development] akuma48465:
You are right see the last update date in first post

Send From Unknown Device
[ONE Original Android Development] dorian1326:
Sorry for the late reply but I had some work related things to take care lately. I did try it twice to charge it from like 50% to 70% and it did shut down again much earlier than even 10%. Those tests were made before flashing the new kernel (didn't check the forum till now). To answer the question, this can be replicated 100% of the time. Only way to go around it is to keep my phone longer to charge even if it says 100%.

Now, I'll flash this new kernel and give it a try. As always thank you for your work!:good:
[ONE Original Android Development] BaronLager:
I think it's funny also. I've been running this ROM for months, and I have had issues, but with a quick search and / or read thru this forum, I always find a fix. I guess it helps that I don't have Facebook, and I have the correct version of TWRP installed, and I'm not running some funky kernel, and I know how to read, so I can properly install firmware, etc.

This forum would be about 500 pages smaller, if people would learn to read and search.

Thanks for your efforts, [MENTION=4800121]Sultanxda[/MENTION]!
[ONE Original Android Development] Brian325:
That's my point. So many people with issues and most of the time its wrong recovery,exposed,multirom or some other craziness. The ROM works great if you follow the correct instructions.
[ONE Original Android Development] siddardha21:
Hi [MENTION=4800121]Sultanxda[/MENTION].

Flashed your newest kernel in the morning, wiped cache partitions just to be sure though kernel flashing doesn't need that. Drained my phone completely which is 20% and shut off. Charged it to 100% and off the charger for nore than 2 hrs andbattery is still at 100%. I had no problems with your rom from November builds to jan 11th. Had this issue in official cos 12 roms.
[ONE Original Android Development] Lupin The Third:
Maybe the logo #neversettle has infected the opo users.

Sometimes I i'm afraid of saying with a loud voice: I'm an opo user. That doesn't sound nice nowadays, I'm afraid that people will read it like: "hey I'm an opo user, i don't know what I'm doing with my phone, but I know how to turn it on and reboot to recovery. For everything else I can ask in the forums. Everyone should answer me, will answer because, hey I have an opo"
[ONE Original Android Development] abhibnl:
Man this Wi-Fi keeping itself ON (even though i use WiFi at all from Mon-Fri) is murdering the battery life. I'm on 1/6 build with the new kernel with updated fuel gauge drivers by [MENTION=4800121]Sultanxda[/MENTION]. Even after a reboot WiFi is still ON and i had to check 20 times a day if some app has turned WiFi scanning ON. I have tried rebooting, soft rebooting, turning WiFi ON and then OFF - it still is there and it happens randomly. First i thought it's cosmetic, but it is consuming battery. Can anybody else or [MENTION=4800121]Sultanxda[/MENTION] suggest any solution? Let me know if i can provide any logs.
[ONE Original Android Development] XBrav:
Try changing your Location Settings to Device Only. I found that helped a lot.
[ONE Original Android Development] abhibnl:
I don't use location at all. It's always off for me until required.
[ONE Original Android Development] gaspolo:
i use the build 10 january , with xposed 3/4 modules, disabled ambientdisplay, (i use screen notification instead), whazzap , fb , 2 mail push, usually i made 5 hours of screen , and 2 day battery ;).

is the best rom at moment with best kernel.
[ONE Original Android Development] mcgrabowski:
I haven't seen anyone else mention this and I'm wondering if it's just me, but since the January builds the pop-up volume slider doesn't go away on its own like it used to. It will stay up until the screen is touched now. Anybody else see this?
[ONE Original Android Development] Lupin The Third:
No, it's working fine.
[ONE Original Android Development] Khizar:
No issues on my end.
[ONE Original Android Development] itechy:
Is it possible to dirty flash this over the old CM12.1 branch you had?
[ONE Original Android Development] Khizar:
Be prepared for insane amount of issues and a lot of time wasted trying to fix those issues, which wouldn't have been there in the first place if you clean flashed.

So to answer your question, no, clean flash.
[ONE Original Android Development] panxe:
Possible to change thermal throttling parameters or should i go for a kernel..
[ONE Original Android Development] davidvoo:
Mine is ok
[ONE Original Android Development] TheImpalaKid:
OPO will not boot with later versions of Cyanogenmod 13

I just bought my OPO on 12/31/2015 used after a couple of years with the HTC One M7. So far it's all good, though it took me all day for various reasons to get it set up correctly.

The first thing I did was root it and install this version of CyanogenMod 13.0, dated December 31, 2015. It has worked great, with only a few random reboots, etc.

I've tried to update the ROM to the current release dated January 11, 2016. I did a wipe, then installed the updated ROM, then rebooted. The phone goes into the boot animation and just sits there. I let it go for 10 minutes just to make sure, but it never booted into Android.

Does anyone have any tips or help to offer? Thanks in advance.
[ONE Original Android Development] 99piotrek:
Hey

Flashed 1/11 but before that Flashed latest CM13 nightlies. Don't have any battery problems or WiFi On problem.

Think everybody experiencing problems should do the same and than check if problems persist
[ONE Original Android Development] stephenta:
Hi, I have reverted to 2.8.6.0 as the instructions said and flashed the cm13 nightly and the january 11th build. However sometimes my service does not work even though the H/LTE logo is there and the bar is full. When people call me they hear it ring twice and it goes to voicemail but my phone does not receive the call. The data tends to phase in and out inconsistently as well. I was wondering if there are any suggestions?
[ONE Original Android Development] sneakerspark:
Do a clean flash. Follow these steps.

Flash twrp 2.8.6.0

Wipe cache, dalvic cache, system and data.

Flash official cm13

Now without wiping, flash sultan cm13,

Flash gapps.

Wipe cache again

Reboot .

This should work fine
[ONE Original Android Development] ryanmat:
Are you using the right version of TWRP to flash, as mentioned all over the thread only Official TWRP 2.8.6.0 or the Unofficial TWRP will flash the firmware/modem files correctly.

Check to make sure your APN settings are correct for your carrier. You can also search for the radio thread that has links to all the different modems and flash different ones to see which works better for you.
[ONE Original Android Development] tofu:
Any chance to add a delay modifier for "kill app with back button" -feature? Currently the delay is too long to be really useful. I noticed that someone asked the same thing on page 440, but did not get an answer.

Other than that.. Amazing ROM. Thanks for all the hard work.
[ONE Original Android Development] syla:
Hello guys,

I'm new on this rom and I was wondering if any custom kernel is recommended for better battery life or performance, or is the built-in kernel good enough ?

Thanks

cheers
[ONE Original Android Development] Khizar:
Not possible AFAIK.

I use built-in one and get amazing battery and performance.
[ONE Original Android Development] stephenta:
in terms of the radios, can i just flash any prior zip file from this thread? http://xdaforums.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734

or is there only certain radios i can flash due to being on 6.0?
[ONE Original Android Development] PlayersHeaders:
my battery isnt good cuz wakelocks and i have random reboots 20160111
[ONE Original Android Development] payne_307:
[MENTION=4800121]Sultanxda[/MENTION] ... I heard that CM13 moved to a stable branch .... Is that true? If yes, can we now expect user builds instead of user-debug builds?
[ONE Original Android Development] D_black84:
do you have xposed, facebook app, facebook messenger installed?
[ONE Original Android Development] balleny:
facing following problems tho i flashed clean: hangouts not acting on incoming messages and system not remembering the connection mode to the computer (wired)
[ONE Original Android Development] mustang_ssc:
Anyone who is using Souncloud has problems with reproducing the music in 01/11? Suddenly stop reproducing the music many times and i must to force close the app.

Most probably it's Souncloud problem but i don't know.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Sultanxda:
This means that it is a hardware bug that cannot be solved by hacking the kernel. Battery readings come directly from the fuel-gauge hardware (BQ27541), so if it's reporting 100% the entire time, then that means nobody can do anything with software to fix it.

This is a Marshmallow bug that even affects the Nexus 5X and 6P.

I saw that and had a good laugh. We'll remain on the nightly branch until the next stable branch comes.
[ONE Original Android Development] TonySuperPony:
Guess they just went to stable for COS. Poor COS users. They are getting a really bad mm update..
[ONE Original Android Development] Metacloud:
Using latest soundcloud beta from day 12.1 and it's working perfectly. All music working as it should!
[ONE Original Android Development] PlayersHeaders:
[MENTION=4800121]Sultanxda[/MENTION] please fix heads up bug, this heads up are so annoying, i cant turn em off :/

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

yes fb and messenger, at the moment i fight with wakelocks cuz this both very bad apps (sorry that i say that:) suck my batterie so hard, I was 2½ hours training, no deep sleep, 2hours fb and messenger triggered my device, thats such terrible, i hate facebook for these bad apps.
[ONE Original Android Development] hammer-is:
I did that two weeks ago and it worked. Remember to backup before you do it...
[ONE Original Android Development] mustang_ssc:
Very strange, i already reverted to an older version and now it's working without problems. I'm not very sure but i think that this didn't happen on others roms like temasek and nuclear reborn, and was the same SoundCloud version.
[ONE Original Android Development] payne_307:
Ok [MENTION=4800121]Sultanxda[/MENTION] ... Thanks for your note.

BTW with so many commits going on now for Snap camera for Bacon, I was just curious to know, will you be using the Snap camera from CM when it gets introduced by CM on the device, or will you continue to use what we currently have which uses Oxygen OS libraries? I mean in those CM commits is there any improvement to the HAL and/or libraries that will improve the picture quality from existing CM13 or CM/COS 12.1? Or is it just about enabling a new app/apk from CM?
[ONE Original Android Development] bulletmark:
[MENTION=4800121]Sultanxda[/MENTION], can you please confirm the above post is incorrect - as it conflicts with your instructions in the OP here?

I installed this 6.0.1 ROM recently coming from OxygenOS which I have been on since it came out. I followed your instructions exactly, i.e. even though I had (official) TWRP 2.8.7.0 installed I just did a clean install of 11-Jan-2016 and got no errors. If the above post is correct then it means that I still have an old or substandard radio/modem even though my phone seems to be working on your new ROM just fine. I have never flashed CM13 but if the above post is correct then I will have to start again using TWRP 2.8.6.0 and this time install CM13 first.
[ONE Original Android Development] ryanmat:
Direct from the OP:

If you get an error when trying to install ("oppo.verify_trustzone" error), then first you must install/use TWRP recovery 2.8.6.0 (TWRP 2.8.7.0 cannot properly update the modem). Next, download and flash the latest official CM13.0 nightly. Then, without rebooting from recovery, wipe /system and flash my ROM. This process is necessary to update various firmwares (including TrustZone), as the updated firmware is needed by my ROM. After flashing my ROM, flash a Google apps package, and then reboot.

Also, if you search the thread you will see that this has been mentioned time and time again, not just by me, but by many others.
[ONE Original Android Development] bulletmark:
Ryan, you are completely missing the point. Sultan's OP says to flash first and only if you get errors then TWRP 2.8.6.0 + CM13 is required. I just want to clarify if this is correct.
[ONE Original Android Development] mekanismen:
The point is that you should always be using 2.8.6.0.
[ONE Original Android Development] alroger:
Nope.
[ONE Original Android Development] bulletmark:
So Sultan's instructions in the 1st OP here are wrong? Sultan, can you please comment?
[ONE Original Android Development] ryanmat:
I just did a thread search for "2.8.6.0" and in this thread there are over 200 mentions all related to flashing updates. Sultan's ROM doesn't have the firmware or modem baked in anymore, which is why your flash was successful. But, if you want the latest firmware/modem from CM you need to use 2.8.6.0 and flash CM13 then dirty flash Sultan over it.

http://xdaforums.com/search.php?searchid=401323805
[ONE Original Android Development] D_black84:
yup these apps are well known as battery killer.
[ONE Original Android Development] urgali:
Hey there!

Just wanted to thank you for the great ROM :D
[ONE Original Android Development] rahulbhasme:
hey is anyone facing WiFi regularly disconnecting when screen off and getting connected only when screen on and I go into WiFi settings and tap on available network?
[ONE Original Android Development] PlayersHeaders:
Hi, a guy said me that i cant write here bugs from the rom, where i can report bugs? this heads up are really annoying...
[ONE Original Android Development] Brian325:
Turn it off
[ONE Original Android Development] PlayersHeaders:
That's the problem what i and other users have, even if we turn it off they appear by some apps.
[ONE Original Android Development] JJHunterx:
Yes, there for a few days it was doing that, then suddenly stopped...not sure what happend.
[ONE Original Android Development] d3thstalker:
While there is an inclination for people to interpret the OP in a variety of ways (which explains why many face flashing problems/errors), it has been said again and again to use the recommended version of TWRP. If you read a few pages back, someone faced a problem where his flashing process went smoothly, however, the phone bricked when he flashed a subsequent update. And of course, the culprit was his TWRP version. He used the same version as yours, and when the new updated ROM included the updated firmware, everything turned into a big mess.

Everything may seem to work fine for now, but I can assure you, that you will face problems in the future when updating. I would advise you to flash the correct version of TWRP and reflash everything again to avoid future conflicts.

This is a PSA to everyone, please use TWRP 2.8.6.0 or the materialized custom version floating somewhere on the forum. If you can't follow simple instructions and cry about it later, that's honestly your problem.

---------- Post added at 06:01 PM ---------- Previous post was at 05:55 PM ----------

No such problems here.

This is the correct place to report bugs. Be sure to use the search function to make sure that problem hasn't been reported before. Also, do include a logcat of your problem if it applies.
[ONE Original Android Development] PlayersHeaders:
Same problem here! I have it sometimes. On my Google Nexus 7.2 with Stock 6.0 i have this always. Idk why, i dont found a solution in the internet.

---------- Post added at 11:21 PM ---------- Previous post was at 11:06 PM ----------

Hello, here's the logcat for the heads up problem :)

https://www.dropbox.com/s/ty5n6vkl4hicxol/2016-01-15-00-13-55.txt?dl=0

(file was 100kb to big for xda)
[ONE Original Android Development] highdiver_2000:
Yesterday I learn there is a multi rom version of TWRP. Make sure you are on the single.
[ONE Original Android Development] marcosius:
any fix for google play services constant battery drain?
[ONE Original Android Development] threetwentyfizzle:
Anybody still experiencing mobile data disconnects when switching from a WiFi network? Haven't read any recent posts or reports of this bug. Data dropped 3 times today for me
[ONE Original Android Development] siddardha21:
After 8 hrs removing off the cable the battery is draining normally. It stays at 100% for long time and drains till 20%.

But I never had this bug on your rom till 11th jan build. :-/ I was running your builds since November. So I doubt it's hardware fault [MENTION=4800121]Sultanxda[/MENTION]. And only solution for this problem is charge it in offline mode till 100%. It'll drain till 0%.

Thank you so much for your effort :D. Cheers!!