yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] acuicultor:
Its a beta version i have removed ukm from the zip cuz i have to modify ukm to properly work with the features on the kernel btw this is a leaked version no official support from me at this point.
[ONE Original Android Development] lokesh.3440:
That doesn't have any FC's right ??
[ONE Original Android Development] KenjiHannya:
You can use the main features, up to HD 50 MP
[ONE Original Android Development] kdb424:
Update your firmware to the latest CM 12.1 firmware by flashing a nightly using TWRP 2.8.6.0 (specifically that one, others won't work) then restore your backup. I use that every day and haven't seen a single force quit on that one at all. Cameranext force quits on close, but google camera is absolutely perfect.
[ONE Original Android Development] Xerosnow:
Thanks for the reply. I was on omnirom earlier so had to flash the latest nightly in order to be able to install this rom. Also, I'm on TWRP 2.8.6 from a very long time now. Camera is not a major part of my day to day life. I can live with this for now.

However, I don't know why I have an idle drain. I don't have many apps. My 'partial wakelocks' section of BBS is pretty clean[0%]. I see a whopping 52% of GMS alarms.

Is anyone else facing this? Your inputs are appreciated.
[ONE Original Android Development] kdb424:
Had something to do with wifi causing fake drain. It's not real. It's so many pages back I couldn't find it if I tried. If you search this throed for "drain" you'll find it in the massive mess that it's become, but know it's not real drain. It's a miscalculation, and there is a reading fix, but if you don't care too much, just ignore it. I had massive drain issues myself, till I deleted the NfcNci.apk but now I can get between 2 and 4 days of use on a single charge with this rom, so I'm not complaining.
[ONE Original Android Development] Xerosnow:
I've deleted the nfc apk and have disabled the wifi scanning. 2 days with normal is a far cry for me. 6hrs of SOT and 1.5 days of battery is more than enough for me. I'm only thinking about where I'm losing the battery when I'm not using it.
[ONE Original Android Development] kdb424:
Try reflashing your rom and then flashing these gapps. I know they aren't the "recomended" but they are what I've been using and having awosemo success. Don't forget to clear cache/dalvik.

http://downloadmirror.co/android/ss

I'm also using AK kernel undervolted 100mv and underclocked a little bit, though even fully stock I was getting amazing battery with just the tweaks listed before. In Battery Monitor Widget, ironicly, I don't use the widgets, I get an estimated 8h24 min SOT anh over 2 days standby, though that's global average, and I've been using my phone harder. Lighter days I have pushed 3 days with battery still left. I have screenshots to prove all of this if anyone really wants them, because I know some people think I'm trolling. I promise that I'm not. Make sure Doze is enabled onder battery optimizations also. Mine wasn't enabled by default for whatever reason. I've also used this app

http://xdaforums.com/android/apps-games/root-doze-settings-editor-android-t3235130

And haven't seen a massive difference, but may help you more than it did me. Those Gapps, and hde NFC apk deletion were the only things I did to get great battery life personally. The rest were done after just to see how far that I could push it. Maybe if none of that works, run a battery calibration on your phone, apps in the play store, and follow the instructions fully. As for if you want to try out the kernel, make sure you grab teh CM version, not the CAF version, and after flashing it, use synapse in the play store to do some tuning. It helped I can say.

EDIT:

Here is to solve the incorrect MISC bug BTW.

http://xdaforums.com/oneplus-one/or...ndroid-6-0-t3225725/post63528335#post63528335

EDIT2: That's the explination. Change userdebug to user in the build.prop "fix" the not real problem.
[ONE Original Android Development] Xerosnow:
[MENTION=3397082]kdb424[/MENTION] Thank you. I've already made the userdebug changes. Couldn't find doze option in the battery settings[option was present in omnirom though]. Will try the latest ak cm kernel. At work right now. Will do a clean flash with the gapps you suggested once I reach home.
[ONE Original Android Development] kdb424:
It's under battery, then battery optimizations. If everything is optimizedd, it's enabled. If there were other options, the app that I've listed can do them, and probably more.
[ONE Original Android Development] Xerosnow:
Flashed ak311 and lost d2tw. I'll give it another go with a fresh install. Lets see how things go.
[ONE Original Android Development] kdb424:
I know for a fact it works. Make sure if you reflashed the rom/new gapps, to make the file edit to Generic.kl, and then in synapse (install from play store) to enable it in there. I use it daily. The other gestures don't work, but that definately did after I followed those steps.
[ONE Original Android Development] KenjiHannya:
Try Resurrected Kernel for M
[ONE Original Android Development] Xerosnow:
This worked. Thank you :highfive:
[ONE Original Android Development] nadiros:
How do versions beyond 2.0 work for you guys?
[ONE Original Android Development] Xerosnow:
I flashed v2.5. Working great for me even though it's alpha build.
[ONE Original Android Development] KenjiHannya:
Great mate ??
[ONE Original Android Development] dkv2222:
This is still the best MM ROM out there. Cudos to the dev
[ONE Original Android Development] nadiros:
Thanks, but how's your cpu usage? And do cpu freq settings stick?
[ONE Original Android Development] Xerosnow:
Sorry, I used the stock settings. Can't test it now as I moved to a different MM ROM.
[ONE Original Android Development] kdb424:
Kernel Adiutor should work. I use AK Kernel on this rom, with synapse, and those settings stick. Underclocked pretty hard, and working amazingly. Deep sleep most of the day on this rom to be honest, so kernel shouldn't matter much.
[ONE Original Android Development] dark_saian:
I'm looking for a kernel which is compatible with wake gestures. Now that xposed is available, there is a way to add those thanks to a module.
[ONE Original Android Development] nadiros:
I don't see any reports about the new xposed for MM. I'll be trying it soon and will report back.
[ONE Original Android Development] nadiros:
Can't edit my post in the new xda app so just reporting that the new xposed v78 works a treat. Happy Happy.
[ONE Original Android Development] Jahdiel2011:
Rom is great if it wasn't for Facebook FC everytime I would keep it as my daily driver.
[ONE Original Android Development] nadiros:
If you search the thread, you'll find a few different solutions. Well they're more like work arounds. A few older Facebook versions work as well as other wrapper apps and then you could always use a good internet browser
[ONE Original Android Development] Jahdiel2011:
The latest version fixes the issue both in Facebook and Messenger.. Thanks for your concern buddy.
[ONE Original Android Development] nadiros:
Right on, I don't use either app but glad you figured it out.
[ONE Original Android Development] pumaworld:
Anyone can post the 20151027 build.prop file?

Inviato dal mio Oneplus One con Tapatalk.
[ONE Original Android Development] nadiros:
*edit (link removed)

Cheers
[ONE Original Android Development] pumaworld:
Thank you but i search the 20151027 file

Inviato dal mio Oneplus One con Tapatalk.
[ONE Original Android Development] JohnM109R:
Gonna give this ROM a try. Other mm are giving me headaches...with the no data connection....
[ONE Original Android Development] kdb424:
Definately do. This is the most stable MM rom I've run and I have tested most of them. Works exactly as I'd want. Only issue at ALL I've had is G+ updated and now won't launch, but probably isolated to my phone as no one has complained about it. No, it's not permissions or anything. I'm not too worried about it as I'm near a computer most times that I actually care about it.
[ONE Original Android Development] thx84:
Do you use a Layers theme?

Envoyé de mon A0001 en utilisant Tapatalk
[ONE Original Android Development] aclup3:
this rom isnt updated since october 27th? any update coming in coming days?
[ONE Original Android Development] kdb424:
I'm such a moron, thank you.

Don't ask for ETA's is in the rules of XDA. On top of that, they stated in the OP when it would be updated. "Whet I have time" is basically what was said. On top of that, it's friggen stable, so I can't ask for more. If you want something updated more often, there are some CM roms coming to the scene, or even AOSParadox. Those may be more suited to you.
[ONE Original Android Development] aclup3:
just asking because im new here and updates could be coming ota instead of dowload links. some developers are doing that
[ONE Original Android Development] Santhosh M:
Does anyone know the fix for this ? SystemUI fc while pressing for recents via hardware keys

11-24 20:50:04.405 3125 3125 E AndroidRuntime: Process: com.android.systemui, PID: 3125

11-24 20:50:04.405 3125 3125 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'com.android.systemui.assist.AssistOrbView com.android.systemui.assist.AssistOrbContainer.getOrb()' on a null object reference
[ONE Original Android Development] Neroga:
Use gravitybox and change the hardware buttons from there. Google search via hardware buttons causes systemUI fc's.
[ONE Original Android Development] ganja5000:
Question on stability of rom

I have been using this rom for a while now and it is pretty stable, with only a few glitches here and there. I am wondering since this rom is no longer supported, has anyone moved on to the CM13 nightlies? I mean has anyone tried them and shown that they are just as stable? If not should I just stick with this rom for another month before CM fixes their stuff? Opinion on daily drive of the official CM13's please.
[ONE Original Android Development] therohanchawla:
Been a while using cm13... Daily Driver for sure..
[ONE Original Android Development] kdb424:
Did I miss them dropping support? I though there just hasn't been an update as it didn't need one. I'm sticking to this rom. I've tried the CM roms before, and this was definately better for me. I haven't messed with it for a while, and it's still working amazingly.
[ONE Original Android Development] ganja5000:
I may have been wrong in using the words 'no longer supported'. I feel that without an update in over a month with a rom that still has problems that pretty much sums it up for me. Also when asking about CM, I meant the official release nightlies, not the other CMs that other devs are working on. Thank you for the reply though.
[ONE Original Android Development] aclup3:
Is this ROM really dead? No more uodates? Android 6.0.1?
[ONE Original Android Development] dkv2222:
Okay believe it or not. This was the most stable ROM for me with best battery.

Not even kidding.

I'd love for it to be resurrected.
[ONE Original Android Development] aclup3:
I woukd like it to.... I want an aosp ROM, but this onde and aosparadox are the only ones and both are not updated for almost 4 months.... I tired of cm roms
[ONE Original Android Development] dkv2222:
Use darkobas
[ONE Original Android Development] aclup3:
Still no 6.0.1?? Cmon devs
[ONE Original Android Development] dkv2222:
Chill. I don't think they're into it now.

Move on to darkobas if you really love aosp
[ONE Original Android Development] j€nish:
Please developer sir take our nokia x2 custom rom cm12.1 Only rill bug solve for help
[ONE Original Android Development] dkv2222:
No offence but are you crazy?

How will a dev with an opo help for and x2?

And I've seen you've been spamming many communities. Including moto e communities.

Please don't do it.
[ONE Original Android Development] copi:
ooh.. let me try that mini later, I've download the mm fix one earlier, maybe I will have gps and now on tap like yours.. thank u bro.

fyi guys, just sharing I've read somewhere that after u activate multi window, u should change buildprop to user ( ro.build.type=user ) again for battery not draining much. I just change it but havent notice yet. this rom default is userdebug. and multi window is still will be active
[ONE Original Android Development] Crazy-Silver:
There is a way to enable key long press actions?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] L0X0R:
Battery life is my main concern. General app compatability and stability.

LCD density?

check f2fs with terminal-mount.?
[ONE Original Android Development] bagadj:
so it's confirmed that titanium backup fc ??
[ONE Original Android Development] Arju:
Woah thanks for testing!!! Looking forward for a stable build :D
[ONE Original Android Development] thenessus:
I installed it.

Confirmed, Mobile Radio Bug still exists.

Haha, lame.
[ONE Original Android Development] fmc000:
compass
[ONE Original Android Development] weihan1102:
Compass working
[ONE Original Android Development] tekanina:
Quick tip, instead of changing brightness to 0 and changing permission just change max brightness to 0 and save. Also in the Aosparadox thread someone built a tasker app that does this automatically.
[ONE Original Android Development] Bobbi lim:
What makes you think the bug is still there?

Android 6.0 has that squashed :rolleyes:
[ONE Original Android Development] weihan1102:
What gapps are you using for the voice search?
[ONE Original Android Development] ~KV:
Anybody here played around with DPI? Can you change it?

AFAIK, if you change it Google Now launcher FCs...

Everything looks just so big...:eek:
[ONE Original Android Development] thenessus:
These results from my device. attached.

and also look at M bug tracker
[ONE Original Android Development] lokesh.3440:
That must be due to the gapps you are using(Nexus 4 which has different DPI ). we need to wait for TK multi-dpi gapps or similar like it to work for all DPI's and resolutions. Till then we need to stick with 480 DPI which is definitely huge
[ONE Original Android Development] copi:
i use the mm fix. now after full wipe again, I am on the mini, voice search is working, but gps still not working, I dont have a clue.

I'm able to change dpi to 400, my google service is auto update to 8.108 - 438, and no fc. havent try now on tap yet. only gps

edit : now on tap working yes
[ONE Original Android Development] ahoneybun:
As usually the community got 6.0 working before OnePlus did. Nice work!
[ONE Original Android Development] turdbogls:
I'm curious as well
[ONE Original Android Development] copi:
yes gapps & supersu
[ONE Original Android Development] weihan1102:
So you got now on tap and voice serach both working?
[ONE Original Android Development] Vekhez:
How did you do Now on Tap? Do you have softkeys on?
[ONE Original Android Development] stefanero313:
pretty cool for a first shoot,

once all the minor issues, gps for example, are worked out could be a daily driver ^^

nice job
[ONE Original Android Development] copi:
Yes, and gps already working. I have to switch to device only first and then voila the maps is locking. Layer also working. Wow, now test the battery. I think its related to gapps. Okay i'm on the road now

---------- Post added at 06:09 PM ---------- Previous post was at 06:09 PM ----------

Yes I activated the softkey. Without turning off hardware button
[ONE Original Android Development] tkruijer:
GPS is working just fine over here....
[ONE Original Android Development] L0X0R:
No DPI access yet?

Or recent app switcher?

battery life ok ?
[ONE Original Android Development] expiredd:
omg, mobile radio bug wasn't fixed in M?
[ONE Original Android Development] weihan1102:
What radio bug are you talking about?
[ONE Original Android Development] tkruijer:
I set recent app switcher at the left hw key, working just fine.

Battery life seems okay. At first Miscelaneous was high, but that was at the time it was restoring all my apps. Now it looks all fine.

What should I check for DPI? Everything looks great. Also the Google Search app looks normal (proportions). Someone said that app was magnified or something. Not over here!
[ONE Original Android Development] thenessus:
Nope.

My next device will certainly not be an Android. I'm done.
[ONE Original Android Development] L0X0R:
Like can you change it to 400? 480 is waaay too high.
[ONE Original Android Development] tkruijer:
I changed it to 360 with root dpi changer. Everything seems to be just fine :good:
[ONE Original Android Development] L0X0R:
Any other notable bugs? The mobile drain is annoying, but it's the same in L, so coulnd't be any worse.

Any issues I should be aware of?

Oh I guess f2fs would be the last thing to check ?
[ONE Original Android Development] fmc000:
Absolutely false, the bug is still present on Nexus devices too.
[ONE Original Android Development] jasi275:
Please tell me screen on time that's important to see how is doze
[ONE Original Android Development] nikhil18:
Guys how to get the google now launcher working its not showing up in home option
[ONE Original Android Development] wts1:
how did u set left hw key for recent apps? cause cant find anything in menu ..
[ONE Original Android Development] weihan1102:
You need to modify a file called generic.kl
[ONE Original Android Development] nikhil18:
Just open root explorer then navigate to system/use/keylayout/generic.kcl open this file search for 139 key replace menu with APP_SWITCH
[ONE Original Android Development] Wongher:
Is it possibile from this ROM to reboot to recovery?
[ONE Original Android Development] Falster:
I have the following issues:

- no button lights

- voice search not working from google bar widget

- no DT2W

---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------

Google Now Launcher is installed as default
[ONE Original Android Development] L0X0R:
I forgot about the DT2W issue. dang. Just flashed it :p

I seem to be stuck on the oneplus logo on boot. Has that happened before?
[ONE Original Android Development] Falster:
Not by default. But there are apps for that.
[ONE Original Android Development] rudolf895:
This app.

Edit: Or in terminal app

su
reboot recovery
[ONE Original Android Development] L0X0R:
halp. Won't boot past the oneplus logo. :S

I can't remount /data for some reason :/
[ONE Original Android Development] Falster:
Excellent, thanks. I needed to reboot to make it work.
[ONE Original Android Development] nikhil18:
Thanks got it working
[ONE Original Android Development] Falster:
Of course. I used this: https://www.androidfilehost.com/?fid=24052804347835251
[ONE Original Android Development] dwaipayanray95:
Just because you can't boot it while others can doesn't mean that the rom needs to mature more! I mean what kind of a logic is that xD xD

:eek:

Still exists! It was never addressed! Marshmallow users have still upvoted and posted the issue on the google bug tracker! The bug was never squashed just tech websites giving us false hopes :/
[ONE Original Android Development] nikhil18:
Voice search and OK google are working try reinstalling the google app because when I installed mm mini gapps google app was giving a force close so I downloaded mm mini fix from the nexus 4 thread and did a fresh install and installed google app from play store
[ONE Original Android Development] Crazy-Silver:
Titanium Back-up FC. Solutions ?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] abhibnl:
For the love of god guys!! Why can't bacon users for once treat a dev thread like a "dev only thread" and not like a General QA thread??? This is the very initial build so bugs and things not working are expected. Hell people are even asking 100 times how's the batt life, atleast give it 2 cycles to settle first guys. I would highly encourage if anyone can maintain a general section QA thread for this rom. I had to go through 17 pages of crap posts and only a few were on topic and helpful.

To OP: awesome work. I will surely test this asap. Keep it up?

Sent from OnePlus One
[ONE Original Android Development] Falster:
Thanks, that worked!
[ONE Original Android Development] nikhil18:
Use backup + alpha for backing up and restoring apps and data in bulk and I just restored 60 apps with data

And from now on every one please be on topic
[ONE Original Android Development] Syaani:
Lol if it is true :P What is your source?
[ONE Original Android Development] Bobbi lim:
I'm not seeing this issue on my friend's Nexus 5 nor my Nexus 7. In fact, our battery life has gone back to how KitKat was ._.
[ONE Original Android Development] ernestnwanu:
Over on Reddit I've seen that the mobile radio active bug is only cosmetic for some. That it doesn't actually drain your battery despite it saying it does. A malfunctioning gauge if you may.
[ONE Original Android Development] pranavthombare:
just curious, i have this left icon as voice search on my lock screen. how can i change that.
[ONE Original Android Development] dwaipayanray95:
Well reddit, Google +, Android "personal" bug tracker by google :P

Well flashing now! Will have to check! But that is what I mostly heard over nexus forums all over the internet
[ONE Original Android Development] wts1:
doesnt work for me ;/

EDIT: after reboot works fine thanks :)
[ONE Original Android Development] Bobbi lim:
Even if the bug is there, the drain isn't. Which means that either Google did a lot of under the hood optimizations to improve battery life resulting in covering up the drain from the bug or the bug is simply just being shown incorrectly and not causing any real drain.
[ONE Original Android Development] dwaipayanray95:
HALP! I have no NETWORK! HALP ME
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] xeneize1150:
Hello how are you? I'm from Argentina and I need some help, I have a tablet Samsung Galaxy Note 12.2 SM-P900 Pro, the upgrade to 5.0.2 Lollipop both the original firmaware or Custom ROM does not start, causes the screen bootloop "Samsung Galaxy Note Pro 12.2 ". Do HardReset with TWRP and does not solve my problem. All I could do is reinstall KitKat 4.4.2 to start the tablet properly. Anyone know how I can fix this and have Lollipop?

Thank you
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] Us3Less:
What do you mean by upgrade by original firmware ? How did you upgrade it ? Original firmware should replace your recovery to stock and no longer twrp if you flash the whole package . Anyway , you might not have LL bootloader installed . Grab it from https://www.androidfilehost.com/?w=files&flid=35233 and flash it via odin
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] xeneize1150:
First I did the update from the tablet and not start. Then from Odin install the downloaded firmware SamMobile from different regions and got the same inconveniences. Finally try custom rom installed from TWRP and the same thing happened.﻿ Also install the bootloader by Odin. By TWRP the kernel. Still the same, with lollipop installed tablet does not start, but with KitKat if you do, and no more trying.
[Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting] TheGasMaster4381:
I had similar problems with my device until I installed this guys custom Lollipop Rom

http://xdaforums.com/galaxy-note-pro-12/development/rom-civzp900lollipop-5-0-2-aroma-12-jul-t3155589

He mentions that you have to install a lollipop bootloader "included in the linked post" for it to work, and I was able to do that through odin. At first it didn't work for me, but seemed to work after I tried again.

This is a great rom by the way, it runs smooth and everything seems to function well.

There is also a Kernel for this rom you might try flashing with twrp

http://xdaforums.com/galaxy-note-pr...kernel-civzp900rev1-1-lollipop16-jul-t3158890