yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] The Dork Knight Rises:
2.7.4.0?? Isn't that OLD? I use 2.8.6.0 for flashing fw/modems, and latest MultiROM recovery normally.

Use 2.8.6.0, it should work fine.
[ONE Original Android Development] copi:
1. To get rid the miscellaneous battery drain u should change userdebug to user in buildprop

2. To get rid wifi battery drain u should turn off wifi scanning in wifi setting and then go to setting>backup restore>network reset and then reboot
[ONE Original Android Development] spences10:
can you share your script pls??
[ONE Original Android Development] natheux:
I'll give it a try

Thanks updateing for your work and the community for all tips/fix/... :)
[ONE Original Android Development] h2s4o6:
Sleep battery drain.

Will wait when this is fixed thanks a lot for the build OP!
[ONE Original Android Development] Jole7:
Anyone here tried Antutu for this Rom?
[ONE Original Android Development] Manav Bhagia:
Yes
[ONE Original Android Development] :
i did, it crashes when it comes to 3d graphics testing (that forest and water lol)...
[ONE Original Android Development] Manav Bhagia:
It scores around 32k but it stops once it comes to 3d benchmark so add about 14k and you get 46k.

That is pretty high for a caf ROM .
[ONE Original Android Development] suaverc118:
Sorry 2.8.7.0 lol! Ill try 2.8.5.0. Also I have a signal showing but can't go online unless I'm using WiFi. I have T-Mobile.
[ONE Original Android Development] nikhil18:
Charging speed is too low anyone else?
[ONE Original Android Development] LuqmaanMathee:
Already changed build type.
[ONE Original Android Development] naveenjohnsonv:
Anyone able to confirm whether the new app data backup on Google drive is working in this build or not?
[ONE Original Android Development] suaverc118:
OK tried 2.8.6 and got same issue. Flashed twrp and rebooted. Then rebooted into recovery again and flashed that firmware zip and got same binary error.
[ONE Original Android Development] Misfit77:
"Layers on M:

•Make sure you have latest SuperSU (Beta 2.52 as of now) and install Stericson Busybox.

•Get the latest Layers Manager app. Grant it root access.

•Download Layers that support M.e.g. Inversion UI. Older Lollipop themes might not work fully.

•After applying Layers, (soft) reboot"

Those are the exact steps that I took. I even tried Inversion UI and it still says that it's applying and then it unchecks all the boxes and after the soft reboot nothing has changed.

**By the way Updateing, the rom is awesome so far. Thank you so much for the work you've done to make it work so well so soon.
[ONE Original Android Development] suaverc118:
I'm also getting this with messaging. Anything I can do on my end?
[ONE Original Android Development] roemicha:
Fixed this by going to Backup & Reset - Network Setting Reset - Reset Settings
[ONE Original Android Development] suaverc118:
My other issue is I have no data. As you can see in my photo I have the signal showing but if I take WiFi off, I can't go online or send pics and etc.
[ONE Original Android Development] roemicha:
The resetting fixed this problem on my end. I couldn't send messages. As soon as I reset, messages instantly went out.
[ONE Original Android Development] rogisha:
Then it's your firmware that happend to me bro with hydrogen firmware
[ONE Original Android Development] jukiewalsh:
Already discussed 1000 times. Radio/modem problem
[ONE Original Android Development] Semper80:
CameraNext V22 creates bootloop and CameraNext V10 blue / black is not installed
[ONE Original Android Development] ernestnwanu:
Anybody else stuck on just 2G as far as mobile data goes?
[ONE Original Android Development] suaverc118:
OK thank y'all. Is this the latest firmware from the cm12 nightly? Just making sure if I did this right.
[ONE Original Android Development] suaverc118:
Sorry forgot to attach
[ONE Original Android Development] lokesh.3440:
BTW how did you enabled dark theme or it is some layer you have applied ??
[ONE Original Android Development] suaverc118:
Its the invert layer. It works well.
[ONE Original Android Development] suaverc118:
OK got data working by doing this. I'm only getting 4g and not LTE, but its working now.
[ONE Original Android Development] kdb424:
Actually I ended up finding out that no data wasn't a modem thing for me. I had to change under Celular Networks -> APN -> Tmobile GPRS -> APN Protocol IPv4/ipV6 and APN Roaming Protocol IPv4

Then I was online no issues. May work for others even on other networks for their APN.
[ONE Original Android Development] lokesh.3440:
I am unable to find invert layer on play store. Did you mean Inversion UI layer ?
[ONE Original Android Development] Fast0n:
Please fix MultiRom :(
[ONE Original Android Development] albi97x:
Are these results OK?
[ONE Original Android Development] suaverc118:
Sorry you are correct.
[ONE Original Android Development] ~KV:
I don't know how you lost that much:eek:

I lost only 1.5% overnight....
[ONE Original Android Development] kdb424:
It's a first build, not intended to actually be used as a rom, and multirom works fine. Move your primary to secondary, and install it as primary.
[ONE Original Android Development] roemicha:
I think that for a first build, the ROM is a daily driver. I never used NFC, so that not an issue. Wish I had DT2W, bit isn't the end of the world. Overall extremely happy. I can remember my Galaxy 3 days when first build were just that. No functionality, simply previews of what was to come. Great work on the first build.
[ONE Original Android Development] The Dork Knight Rises:
CameraNext Mod v10 installed for me without any issues but once I tried to turn off the 'Power shutter' option it crashed and wouldn't start anymore even after a reboot.

I'm using ColorOS camera port by [MENTION=6384125]infinityplus[/MENTION] and everything seems to work (I don't use 4K recording, which apparently doesn't work). Oh and after taking a pic with Super Macro module, the app hangs, just gotta restart it (photo gets saved)

Works as primary. That's good enough for me I guess.

Move your current primary to secondary and flash MM on primary partition.
[ONE Original Android Development] h2s4o6:
No xposed or anything like that.

Just stock marshmallow.
[ONE Original Android Development] Spider-Vice:
The ROM is extremely fast but Instagram kept crashing for me unfortunately. And is it normal for fonts to be missing? Like on lock screen the time is a different font than on Lollipop and on the menus too. Great effort on a M ROM though!
[ONE Original Android Development] cumanzor:
Heh, so Swiftkey absolutely **** the bed after changing the density to 420 using the command

wm density 420

. Never seen this happen before with SK.
[ONE Original Android Development] kdb424:
I'm running 280 and it's as happy as can be.
[ONE Original Android Development] KINGVADER:
Its not a CMbased rom-_-
[ONE Original Android Development] cumanzor:
I'll try 400, maybe it won't freak out then. Did you use the wm command to change density or did you do something else?
[ONE Original Android Development] The Dork Knight Rises:
You don't need a CM-based to run CameraNext -_- :P

Try changing it in build.prop
[ONE Original Android Development] ~KV:
Lol, as if I used Xposed!

Even I was on stock! Complete stock....
[ONE Original Android Development] KINGVADER:
Yes totally forgot ???try adjusting the DPI or try flashing an older version ?

---------- Post added at 05:50 PM ---------- Previous post was at 05:48 PM ----------

Or maybe the ROM ain't compatible ....

---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------

Since its made for 5.1.1. And the ROM is based on 6.0 it won't install
[ONE Original Android Development] suaverc118:
So you uninstalled NFC correct? Or was that someone else? Anyways with your small drop, what did you do to sleep so well? Turn off WiFi and data? What can I do during the day when I use it but want the best deep sleep possible without turning off data and etc?
[ONE Original Android Development] therohanchawla:
Can someone help me on NFC.......Whenever i delete/ change extension of system/app/nfcnfi i keep getting FC's

Unfortunately com.android.nfc has stopped
[ONE Original Android Development] pankspoo:
The build is not compatible with f2fs

And don't try to use it with f2fs as it's causing revertion f2fs to ext4

Automatically and all u r sd data will get erased(really annoying to me when i losed my all data)

And may cause unmounting of data partition ( as data partition only become on ext4 and others are on f2fs after flashing the ROM)
[ONE Original Android Development] nikhil18:
Just turn of NFC and then delete NFC apk and reboot worked for me

And if you can't turn it off then just delete and reboot
[ONE Original Android Development] Semper80:
You do not really know what you're saying. It is a ported app for other ROMs. I tested it in a pure 5.1.1 AOSP and it works perfectly.
[ONE Original Android Development] h2s4o6:
I just enabled soft keys.

You edited build.prop?
[ONE Original Android Development] Fast0n:
[MENTION=5782089]The Dork Knight Rises[/MENTION] [MENTION=3397082]kdb424[/MENTION] Thx man ;)
[ONE Original Android Development] suaverc118:
This rom looks promising. But its hard to keep it especially when I'm losing signal at times or not getting my group messages. I'll keep it as a back up until more updates come. Keep up the great work.
[ONE Original Android Development] Snottierwhale:
Yup same thing happened to me lost all my stuff cause i was on f2fs, unable to mount any partitions. Had to fastboot flash the latest cm12s.
[ONE Original Android Development] jahideu:
I m using this ROM as secondary. Just need to remove verification code after ROM flash in updater script. It's indeed a great ROM.... :)
[ONE Original Android Development] lokesh.3440:
No problem buddy...you were really helpful.
[ONE Original Android Development] KingBeike:
Which line ?
[ONE Original Android Development] lokesh.3440:
Sorry buddy but you are wrong. I have installed camera next apk and it works amazingly well.
[ONE Original Android Development] The Dork Knight Rises:
Or you could just swap ROMs in MultiROM menu. ;)

Boots fine as a secondary. :D
[ONE Original Android Development] jahideu:
Use this only

(!less_than_int(1444742359, getprop("ro.build.date.utc"))) || abort("Can't install this package (2015年 10月 13日 星期二 21:19:19 CST) over newer build (" + getprop("ro.build.date") + ").");

get_device_compatible("bacon") == "OK" || abort("This package is for "bacon" devices; this is a "" + getprop("ro.product.device") + "".");

assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0123") == "1");

ui_print("Target: oneplus/aosp_bacon/bacon:6.0/MRA58K/hamster10132117:userdebug/test-keys");

show_progress(0.750000, 0);

ui_print("Patching system image unconditionally...");

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

show_progress(0.050000, 5);

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

show_progress(0.200000, 10);
[ONE Original Android Development] Semper80:
Which version? It gives me boot loop.:confused:
[ONE Original Android Development] lokesh.3440:
Try installing the one from here :

http://xdaforums.com/showthread.php?t=3086513
[ONE Original Android Development] Semper80:
K. Thanks. I'll try.

I tried V10 BLUE but it gives me error
[ONE Original Android Development] Falster:
Just want to leave some battery stats for you. My 2nd cycle with M, 2 days with over 6h SOT. For me this is way better than every rom I used with lollipop. Thanks for that nice rom.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] scorpionhd2:
Exactly what I did. Swap my Primary to secondary. Flash this ROM as new primary. Then swapped ROMs back and it works perfectly as a secondary, including booting into it from multirom widget.
[ONE Original Android Development] chachin:
anyone know if ak kernel works with this rom?
[ONE Original Android Development] kingbobski:
Please check the first post.. Short Answer.. No it is not
[ONE Original Android Development] chachin:
oh i see in the Q&A #1 thanks for the info oh well i guess we gonna have to wait until next month to see some good stuff show up heh but time will tell how well opo will play with marshmallow.
[ONE Original Android Development] Spider-Vice:
Anyone else having crashes with Instagram? Because it's a bit annoying, and other than that the ROM is actually pretty stable for a first build.
[ONE Original Android Development] :
This happens every Android update. Many apps won't work right on the new version until the app developers update their apps.

Takes time, and very few devices have M yet still. ;)
[ONE Original Android Development] zaphodbeeb:
And Marshmellow lives on the OPO. F2FS didnt work but ext4 is fine. I used the 2.52 beta supersu and all seems fine.
[ONE Original Android Development] rogisha:
Actually latest instagram app from the playstore had some FC's for some time but when i tried to share a photo on the instagram everything worked after that, so here for me it's all good

And yes for the first build with few tips and tweaks here and there from this thread, rom is very stable and battery is awesome,

I did all what people suggested only phone app icon is unchanged for me everything else is just awesome..

Btw when u turn off wifi - tap on screen and u'll see the hidden menu fir wifi/bt scanning

Great job dev and the rest of the people with tips in this thread most of them was very helpful

Btw #2 Search is working on tapatalk just fine

Btw #3 SystemUI Tuner looks promising for future features and tweaks

Thanks to everyone
[ONE Original Android Development] LLStarks:
This rom is quite nice once you apply a stock-ish gapps and enable on tap.

Couple of issues though.

* Dialer icon doesn't update even after icon fix and proper chmod permissions (Edit: nvm, had to disable/reenable app)

* Hardware home button still works after enabling softkeys and disabling the other hardware buttons

* Can I use firmware newer than CM's? What about the 4.0.x modem?

* APNs are less than ideal. I have no expectation that MMS will work.
[ONE Original Android Development] kdb424:
APN needed tweaked, though I don't send MMS, so don't know if that will work. I'll have someone send me an image, as for newer firmware, I believe that most new versions will work. I honestly don't know what I had on here when I bought it from a friend as I unlocked and rom'd before I even booted it once, so it's pretty generous I'd say, and home button working? You missed something for sure as I use softkeys and all of my hard buttons are dead once I tweaked the file, as I set it to. You need to commend out 3 lines. If you still are having issues, PM me and I'll send you the guide I used to get mine working proper.
[ONE Original Android Development] LLStarks:
I'll keep tweaking, but I'm quite happy for now.
[ONE Original Android Development] Vekhez:
Enabling softkeys is like weird, like in some apps (eg. Snapchat), the softkeys overlap the UI making it hard to use when sending things etc.
[ONE Original Android Development] kdb424:
That's more of an android thing than anything with this rom. That being said, I haven't personally had a single app that had problems with the softkeys, though I don't use snapchat.
[ONE Original Android Development] Vekhez:
It's definitely a this ROM thing. If I enable softkeys on CM11/12/12.1 snapchat doesn't show the main parts of the UI UNDER the softkeys. But on this ROM it does.
[ONE Original Android Development] kdb424:
Have you had that problem with any other app? Just curious as it may, though not likely, have problems on other 6.0 devices. I'm just at a loss to what it could be if that's the only app. Then again, I run a 280DPI in my build.prop, so it may just be me not noticing these issues.
[ONE Original Android Development] Misfit77:
I used a theme in layers called slate free and after it applied and I clicked soft reboot it normal rebooted. After that it got stuck on the Android logo and I had to restore my LP backup.
[ONE Original Android Development] kdb424:
That's a first hearing that. You can just uninstall the layers from recovery with the file browser BTW and it would have booted. Not all layers are working properly it would seem, though mine all work.
[ONE Original Android Development] NoobInToto:
In MX player,the volume doesn't increase beyond certain limit. For me ,its 10. After I increase it beyond 10(with no effect),and after the volume bar disappears,when I try to increase,it shows that it was less than 10 already

Creepy bug

Anyone else experiencing this?

---------- Post added at 04:04 AM ---------- Previous post was at 03:26 AM ----------

Installed the rom build, installed gapps mm fix, and followed the steps to resolve wifi drain - by turning the scanning off, & resetting the wifi settings from backup & reset settings.

Phone is not sleeping still. Charge cycle - 24 hours, SOT - close to 5 hours
[ONE Original Android Development] rudolf895:
perhaps when we get a Android M kernel most of the bugs would be fixed. Its still the first build
[ONE Original Android Development] DerkMatter:
Well .. This is my CPU Usage .

I switched off WiFi Scanning and NFC and my phone started sleeping like a boss :P
[ONE Original Android Development] kdb424:
Disable NFC. It's bugged. Check for wakelocks and that should be the culperate. I couldn't disable it, so I deleted it and rebooted the phone.
[ONE Original Android Development] cumanzor:
huh, how do you uninstall a Layer? I got into a System UI crash loop myself : /

edit: here http://xdaforums.com/android/apps-games/official-layers-bitsyko-apps-rro-t3012172
[ONE Original Android Development] kdb424:
You have to reboot after you uninstall them. They are in use when you are booted with them, so when you take the resources away, you need to reboot so they use the standard resources in the apk files themselves.

As for uninstall, they are in /system/vendor/overlay I believe.

Edit: you found it.
[ONE Original Android Development] updateing:
I think the failed verification may be the cause of this failure. You can try removing the verification in updater-script.

* However, since this is a CAF build, it may not boot from secondary even if you get it installed...
[ONE Original Android Development] updateing:
Now I've managed to fix this. :p
[ONE Original Android Development] kdb424:
I can't say about that modification to get it to boot, but installing as primary, then moving to secondary works. I have the same rom in both spots booting fine.
[ONE Original Android Development] pumaworld:
The ROM often completely block the device.

Reboot with power botton.

Others have this problem?
[ONE Original Android Development] kdb424:
What? It is working fine for me. Install as primary rom if using multirom.
[ONE Original Android Development] nikhil18:
If you want to report a hanging or sod problem then just help the developer by giving him a dmesg and kmesg so that he can narrow down the problem and from next time search the thread before asking if people have this or that bug
[ONE Original Android Development] Crazy-Silver:
There is a tip to enable longpress actions on hw Keys?
[ONE Original Android Development] capitanouncino:
Same here...Tim Italy

Have you resolved?
[ONE Original Android Development] Crazy-Silver:
Try to change APN Protocol of your apn in IPV4/IPV6
[ONE Original Android Development] The Dork Knight Rises:
Does this....update time coming Soon™ :D

It's not really a this ROM thing, its primarily an APP thing. If the app doesn't expect softkeys, it'll overlap. The build.prop edit is a crude way of enabling softkeys, so it doesn't tell certain apps to expect softkeys.

CM uses some other way to enable softkeys (when you use the switch I'm Buttons section). Try enabling with build.prop and you should have the same issue on CM too.

1. Did you just install ALL overlays without looking? If a single app has more than one layer applied, it could cause a bootloop. Always apply layers smartly.

2. Is the theme M compatible? (Though that should hardly cause a bootloop)

Yeah it's been mentioned before. I have personally been trying to gather logcat but it never happens when plugged into PC for me. (I prefer full logcat vs last_kmesg/dmesg)

Yeah newer firmwares will work, but the normal zip won't flash on top of them as it looks for older version. You can flash firmware AFTER the ROM though. Use TWRP 2.8.6.0

As for APN settings, you can always edit them can't you? Figure out your perfect settings (maybe from some other ROM?) and configure them.
[ONE Original Android Development] Killer.shubham:
Nice work on 20151018

Nice work again [MENTION=4812336]updateing[/MENTION] worked pretty good 20151018

Uploaded mirror on Dev Host for people having trouble downloading from google drive.

Mirror link here

Build 20151018
[ONE Original Android Development] neothechosenone:
How did you activate now-on-tap?

Seems like it wont work for me...

Here's what i did so far:

Flashed rom

Flashed gapps mm mini + fix

Started device, added gmail account

disabled HW keys, enabled SW keys

Everything is working like a charm so far, except google app in general.

There's no way i can activate "Ok google everywhere" and if i long press home it just sends me back to default Google Now page.
[ONE Original Android Development] vindows18:
does xposed framework work ?

ps: please don't kill me for asking this :)
[ONE Original Android Development] Vekhez:
For everyone who doesn't want to manually run commands,

download: https://play.google.com/store/apps/details?id=com.kislay.bootshellcommand

You can add the command in and it will automatically run at boot.

And for [MENTION=4812336]updateing[/MENTION], another thing to add.

echo 100 > /sys/class/leds/button-backlight/brightness

will turn on the capacitive LED's at normal brightness.
[ONE Original Android Development] marcovittori:
I have tim (italy), it works well, but i've flashed the last cm12.1 nightly before flash it, try to do that
[ONE Original Android Development] nikhil18:
Then why do you ask if you don't want to get killed
[ONE Original Android Development] The Dork Knight Rises:
Why do that shell command thingy and install another app just for that when you can:

1. Edit the file itself (proc/touchpanel/doubletap_enable) to 1 using a root explorer? It seems to stick across reboots.

(No need for additional app)

2. Use Kernel Adiutor to enable DT2W after adding the 255 key mapping in Generic.kl and then set apply on boot?

(Kind of an alternative method USING an additional app, with more functions)

PS, DT2W works on first build too. But there is a high chance of pocket wakeup...
[ONE Original Android Development] capitanouncino:
I tried, but it was the same ... now I flashed the latest build and it works fine. Mysteries of life :)
[ONE Original Android Development] noahvt:
[MENTION=4812336]updateing[/MENTION] , any ideas on why long press on hardware keys doesn't work? Throw anything you got at me cause i'm trying to find the problem, I've been thinking about porting cm's button options in settings over to 6.0 lol
[ONE Original Android Development] The Dork Knight Rises:
I'm not a dev or anything, but I think a good start would be to compare the Generic keylayout file to another ROM with long press actions working. Look for key maps missing in the MM kl file (especially ones which are mapped to SEARCH or APP_SWITCH which are I believe the default mappings for the home and menu buttons)

I got the idea from the fact that the reason DT2W wasn't working was cuz the key mapping was missing.
[ONE Original Android Development] miguepereira77:
But, it will stay on all the time... how can be set it off at..let´s say 5 seconds without input??
[ONE Original Android Development] noahvt:
It's not the kl file unfortunately, it's probably something missing in the framework, i'm trying the framework of the z1 which is about the only one I can try as i think that the only phone running 6.0 that has hardware keys is the oneplus one :/ not a single samsung device has it, not a single htc device has it...