yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] RobbieL811:
Alright guys/gals. New build is up! Synced up w/ a LOT of CM. Also, I did a little tinkering w/ [MENTION=3685904]ak[/MENTION] kernel. Had a little trouble w/ UBER 6.0, so I downgraded to UBER 5.0. But please do not think that you have lost something! It is blazing fast for me, and I underclock! Lots of kernel/device updates. Also, bug w/ NFC tile not showing is back!!! I hate that DAMNED thing!!!! Also I added flip phone to mute/reject calls. Nifty little feature. I think that one will come in handy. Can be found in call settings by the speaker phone proximity stuff, or blacklist. Other than the kernel updates + the one feature and syncing w/ CM, that's it. Enjoy. Let me know if you have any trouble w/ reboots or SOD. I haven't had any yet.

Edit

- Also forgot to add that I removed CM's setup wizard. Had problems with people on other devices complaining about it. Let me know if it ends up being an issue on bacon please.

ROM - cm-12.1-20150419-ROBBIEL811-UBER4.8-bacon

GAPPS - gapps.BETA.5.1.x.build.0.x-20150418
[ONE Android Development] chikimonke:
For the life of me, I can't get root with this build, I lost it after flash, and I can't get it to work with built in or flashing SuperSU. Anyone else?
[ONE Android Development] dickenam:
Got built in to work after a dirty reflash without flashing supersu 2.48, can't find where to manage root in settings though..but supersu definitely no go.

Sent from my A0001
[ONE Android Development] topp10:
ROM - cm-12.1-20150419-ROBBIEL811-UBER4.8-bacon

GAPPS - gapps.BETA.5.1.x.build.0.x-20150418[/QUOTE]

Hi, I just tried to flash this latest build using my usual process with Boeffla kernel.

I never had any issues before but this one kicks me straight back into recovery.

I tried twice before going back to previous build which booted up no problem...

Anyone else had any issues before I give it another go?

Cheers!
[ONE Android Development] Nos_20:
I have just been battling the same problem. First I installed normally. Ie, wipe caches, flash rom then gapps and supersu.zip. when i rebooted, No su binary installed. Thought oh dear!

So I rebooted and just wiped cache/dalvik then flashed only ROM/gapps.

Went to SuperSu icon this time it installed the binary and root was restored.

Sent from my A0001
[ONE Android Development] chikimonke:
Yeah, tried flashing ak217 to test the root issue I am having, and same thing happened to me as well. I would steer clear of this build for now. I'm guessing it's new CM commits that need to be matched in the kernel.
[ONE Android Development] Spaulding89:
+1
[ONE Android Development] tofuboi01:
Agreed, SuperSU doesn't seem to work, I'll reflash ROM and test with the built in Su.
[ONE Android Development] Nos_20:
SuperSU working OK for me after some fiddling about!

Sent from my A0001
[ONE Android Development] tofuboi01:
I flashed yesterdays build back, how did you manage to get it to work?
[ONE Android Development] Nos_20:
See my post on the previous page!

http://xdaforums.com/showthread.php?p=60209530

Sent from my A0001
[ONE Android Development] tofuboi01:
I tried this but didn't seem to work for me =(
[ONE Android Development] Infinityyy:
Works great overall, but I had an SOD yesterday and just now. Going to give the new build a go.
[ONE Android Development] Nos_20:
Working here I was flashing supersu 2.46 and getting no binary and supersu cant install it.

Try uninstalling supersu. Then flash just ROM and gapps and reinstall from Play?

Sent from my A0001
[ONE Android Development] tofuboi01:
Did as you suggested and managed to get cm su working but when I try to change the DPI to 380 and install viper driver..it crashes and boot loops..will stick with 18th April build for now.
[ONE Android Development] dickenam:
I was able to make this work. Reflashed ROM and gapps, skipped SuperSU zip in recovery, booted, gained built-in root, installed SuperSU binary from Play store and rebooted. All is well with the world, this build is top notch as usual. DAT Slim governor too boiiiiiiiii.

Sent from my A0001
[ONE Android Development] drwazi:
boot bug??

i just tried installing the 19/4 built and i went into boot loop with ak kernel.i was on 18/4 built earlier.anyone with similar issues?:confused:
[ONE Android Development] PresidentMcCain:
The problem with this approach is, the next time you flash the ROM, now you'll have to redo this entire thing all over again, whereas before you could just flash the 3 zips and call it a day.

Anyway I think I found the commit that's the culprit here: http://xdaforums.com/showthread.php?t=1538053&page=892
[ONE Android Development] Zeus20:
I see they yanked the cm12.1 build from the download page. Maybe they noticed the supersu issue.
[ONE Android Development] HaTrED_:
You have to wait until ak update his kernel with latest commits from cm!

Tapatalked!
[ONE Android Development] Andromendous:
I have a weird little issue, running 04/18 build, my phone wont sleep while its charging, anyone ells? It still charges fine tgo
[ONE Android Development] Spaulding89:
Your Phone will never sleeps while it charges ;)
[ONE Android Development] Foxje:
Still on 18/4 with AK 217. Issues with device not waking (buttons lighten up, black screen).
[ONE Android Development] johnb380:
Are you UV a lot? If so try to up the voltage 25mv and see if that helps also you can try to set your min CPU to 345 also try to set your max cores screen off to 2 instead of 1. I think some CPUs have problems with some of these settings.

Hope this helps and good luck friend!
[ONE Android Development] EkiFox:
with your last rom the notification sound looks fixed.

Thanks a lot again
[ONE Android Development] Andromendous:
I've been having this problem too, 2-4 times a day on 04/18, only changed a few things with Synapse, like lowered cpu 1,2,3 to 145mhz, no u/v,

As a matter of fact, i just had a SOD happen just now,

I looked at last_kmsg and i dont see any warnings or anything, I can do a paste bin if you want robbie.
[ONE Android Development] bissa:
I had the (buttons lighten up, black screen) with blisspop with AK 217 too. I suspect the kernel. I was using AK 213 and never has this issue while using but once I updated to 217, I got the black screen issue some hours later. I'm back to AK 213 for some days now and no black screens. I use the default kernel settings.
[ONE Android Development] johnb380:
Maybe try to get last kmsg and logcats and post here and in Aks thread I'm not a dev so I don't know about reading logs but there are a lot of devs and super power users that maybe able to help more than me if you post the logs!

I was try to troubleshoot the problem the best I can because I never have any of the issues other people have and I have my kernel settings set like my suggestions. Also I get good battery life with them too!
[ONE Android Development] LiquidSolstice:
I've been reading the last few posts, and I still can't quite figure out what the su issue is.

Somehow, during the dirty flash, I lost my google apps (minus chrome). As in, I couldn't open the Play Store, Play Services was missing, etc. I dirty flashed the Google Apps package (really weird), but I also can't get Su to work either.

I don't really have much in the way to add as far as a solution goes, but I wanted to warn you all in case you choose to dirty flash; something is definitely somewhat up with this build.
[ONE Android Development] gacalderon:
Facing the same issue here
[ONE Android Development] johnb380:
I'm glad I skip every other build! Seems like the latest is a lil skrewy!
[ONE Android Development] MobileThrowAwayAcc:
Also couldn't flash xposed 5.1 on the last build in addition to losing gapps
[ONE Android Development] mazdarati2:
Hmmmm, should I dirty flash the newest update coming from the 20150407 build?
[ONE Android Development] Zeus20:
I would not recommend that until the superuser issue is solved.
[ONE Android Development] mazdarati2:
Wasn't aware of that issue. Thanks!
[ONE Android Development] Zeus20:
Read back other user report posts.
[ONE Android Development] expiredd:
When device goes into deep sleep after a long time Wifi is disconnected. I know I can solve this editing build.pro and setting.:

persist.radio.add_power_save = 0

Is this normal? I've already checked that "Keep Wi-Fi on during sleep" is set to "Always". It's better to edit this line or use any app to keep alive WiFi (I don't know if this works with deep sleep)

Problem I've is that I've a Tasker setup that switches to 2G when I'm connected to WiFi at work.. but when phone goes into deep sleep mode WiFi goes off and phone doesn't connect to 2G network (reception signal icon with exclamation) and I stop receiving any message or notification because it's fully disconnected from WiFi or mobile internet.

Maybe I should force Tasker to reconnect to 2G when WiFi is off is screen is turned off.
[ONE Android Development] HaTrED_:
In my case, SuperSu has a strange behavior: It works! It gives/grants root permissions when needed and all seems to be working really well but, the thing is, i can't access the app... it's like it doesn't exist because i can't find it anywhere! Used 2.48 beta along with 18/04 release! :confused:
[ONE Android Development] pkrstr:
Too bad SuperSU isn't working properly.
[ONE Android Development] RobbieL811:
What's up guys? I just woke up to see a ton of people having all kinds of problems that I am not having lol. I have 0 sleep of deaths and root working fine. Also, AK kernel was synced w/ CM. I did it. I will get to work here in a little bit.
[ONE Android Development] Spaulding89:
My only Problem is SuperSu but inbuilt root works good. So i have no Problem [emoji14]
[ONE Android Development] foomanjackel:
Hey robbie, no problems here running since yesterday afternoon....BUT I did have a SOD yesterday morning while using fusionjacks slim + ak v217, so as soon as I installed you're ROM in the afternoon, I quickly installed ak's latest v220 and have had no issues thus far.

Root is functioning fine, but I do not see the superSU app intstalled anywhere....should I?? And thanks as always for you're outstanding work my friend :)
[ONE Android Development] RobbieL811:
Yeah. That's likely an issue with the app then. Personally I use the superuser that comes with the ROM. I have inbuilt a little feature that allows you to hide the hash tag when root is active. Working great here.

No. The ROM has root built in. Look in developer options.
[ONE Android Development] Nos_20:
I see the SuperSU app in my app drawer? Lol!!

Sent from my A0001
[ONE Android Development] HaTrED_:
Pic's or it dind't happen! :D

Edit: owned!!! Which version is it?
[ONE Android Development] Nos_20:
[emoji3] [emoji3] [emoji3]

Sent from my A0001
[ONE Android Development] Lither:
Can't wait for the Delta updates! :)
[ONE Android Development] P1f:
I only had 2 SOD on the 18.04 version, but battery-wise is a solid build, lasted 2 days for me with wifi on all the time.

I stayed clear from the 19 version when I read about the issues reported here but I look forward for a new version hopefully with no more SOD ;)

Thanks for the great rom Robbie !
[ONE Android Development] akj24:
Running the 18/04 build! No sod. Just stable! Thanks [MENTION=4911350]RobbieL811[/MENTION]
[ONE Android Development] RobbieL811:
I haven't had ANY issues. About to push a new build if data will allow.

This came from you. My ROM doesn't install SuperSU.
[ONE Android Development] EasyGoingXD:
[MENTION=4911350]RobbieL811[/MENTION] How is the awesomeness going on? :)
[ONE Android Development] RobbieL811:
New build is up. Don't have time for change log. In theater.
[ONE Android Development] herubrand:
OT

http://www.gsmarena.com/oneplus_paused_cm_os_12_ota_to_add_ok_oneplus_feature-news-11971.php

Voice Activation is coming back :D
[ONE Android Development] Nos_20:
Yes I reinstalled from Play to get root to work!

Sent from my A0001
[ONE Android Development] vitalym:
Anyone having issues launching YouTube or MxPlayer?

These 2 specific apps crash immediately when launched.

I'm running:

cm-12.1-20150418-ROBBIEL811-UBER4.8-bacon

Slim_normal_gapps.BETA.5.1.x.build.0.x-20150418

Since YouTube was baked into the gapps, it didn't let me uninstall it.

I uninstalled with Titanium Backup and reinstalled from Play Store - still crashes.

MxPlayer crashed on startup but I was able to fix that by uninstalling and reinstalling it. Now it crashes when I pause a video. But if I let the video play through all the way it works fine.
[ONE Android Development] Spaulding89:
Tested right now. No Problems for me with 20/4 build.
[ONE Android Development] MobileThrowAwayAcc:
dirty flashed 4/20 build, still couldn't flash xposed and still lost gapps. Phone restarted soon after booting and having all the gapps fc. I'll try a clean install later
[ONE Android Development] vitalym:
I just flashed the 4/20 build of Uber and Gapps and both issues seem to have been fixed :D

Appreciate you offering to test for me though.
[ONE Android Development] el*Loco:
Since I had some problems with 04-18 I did a fresh install of 04-20 after a factory reset. Now the Android AOSP keyboard keeps crashing on startup so I cannot enter any Wifi password or other credentials.

Trying to boot a CM12.1 nightly...
[ONE Android Development] meetpatel:
Just flashed but supersu shows this error.flashed supersu v2.46
[ONE Android Development] meetpatel:
This error
[ONE Android Development] RobbieL811:
What Gapps are you using? Also, why are you flashing SuperSU??? Did you not just read the past couple of pages???
[ONE Android Development] tofuboi01:
So I just flashed latest build, seems to be working fine with the inbuilt Su.

Now just one nitpick... When I edit build.prop to change DPI to 380..it bootloops..any idea why?

Thanks!
[ONE Android Development] expiredd:
Flashed today build, SuperSu not working. Reflashed ROM and Gapps without SuperSU this time. Now built in root is working.

SmartLock is working again on today's build :good: :good:
[ONE Android Development] el*Loco:
No SuperSU installed, just 04-20 of your ROM and the gapps package from slimdevs page.

I am back on 04-15 without any problems...

btw: AK kernel 211 is the only kernel version I can access my Wifi AP with, all other kernels - even CM12.1 nightly - can't get beyond "fetching IP address". Any ideas?
[ONE Android Development] Foxje:
Enjoy yourself! You deserve it :) :beer:
[ONE Android Development] RobbieL811:
I am lol. Flying the drone right now. Added a built in density changer while waiting on the drone batteries to charge! Will be in next build. Gotta test it a little bit first.
[ONE Android Development] Spaulding89:
This Rom gets Better and Better and Better and Better and...... [emoji1]
[ONE Android Development] byAidan:
You are the very best sir, enjoy flying your drone I saw your video of it and it's very nice ;)

Can't wait for the density changer :good:
[ONE Android Development] expiredd:
[MENTION=4911350]RobbieL811[/MENTION] Was flip to mute finally added?
[ONE Android Development] Zeus20:
see call settings
[ONE Android Development] RobbieL811:
Finally??? I added it like 10 minutes after the guy posted the commits lol. Finally...Lol.
[ONE Android Development] expiredd:
Sorry, english is not my main language. Didn't want to be disrespectful. I misunderstood your post, I had not clear in my mind if the feature was built into the ROM or you was testing/thinking to add it in a near future build. :(
[ONE Android Development] MobileThrowAwayAcc:
Is anyone having any success in flashing xposed on the builds post 4/18?

This definitely isn't my wheelhouse, but I wonder if it's failing for the same reason flashing super su is also failing. (I fully get that there is built in root options, and I use and love it)

Thanks!
[ONE Android Development] Natakranta:
Guys, anybody tried to boot Apr.20 build as secondary on MultiROM? I have MultiROM error and it doesn't boot, I've already reported on MultiROM thread. I'm curious if anybody else uses MultiROM and have this problem.

I excuse bad download, I downloaded twice and had matching md5s. I exclude bad flash because I flashed 3 times to check and always got MultiROM error.

Apr.15 build boots both with it's karnel which was ak 213 iirc and with ak 220

Apr.18 build boots with it's karnel ak 217 and with latest ak 220, which I'm currently running.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] RenderBroken:
I have had the same problem trying to test this rom.

[MENTION=4911350]RobbieL811[/MENTION]

Here is the log:

http://pastebin.com/1M3hKNv7
[ONE Android Development] Black Adam:
Flashed latest with slim 5.1 gapps and got an aosp keyboard crash that wouldn't let me get through the setup. Weird because I've used that exact version of gapps every time I flash older versions of this ROM.
[ONE Android Development] bkayy:
Hi guys just flashed latest rom and got no root access so flashed supersu v248 but still having issues any ideas. I had to restore backup from 18th
[ONE Android Development] RobbieL811:
Which gapps packages did you flash? You probably flashed Google Keyboard. I am using AOSP keyboard without problem, and haven't had a problem from it since day 1. I don't flash ANY kind of keyboard. The keyboard is built in. If you are flashing a keyboard in Gapps, remove it. That isn't AOSP keyboard. It is Google keyboard.

Root access is working just fine. Enable it in developer options. People, QUIT FLASHING SUPERSU!!!! Also, READ a little bit!
[ONE Android Development] foomanjackel:
Robbie, no ak kernel in todays build?
[ONE Android Development] bkayy:
Thanks saw it in developer settings appreciate the good work!
[ONE Android Development] Black Adam:
I flashed slim gapps 5.1 from the OP. No other keyboard. I'll try again with the zero gapps.
[ONE Android Development] RobbieL811:
Yeah. Try just for testing. If you still get FC, do you know how to take a logcat?
[ONE Android Development] LiquidSolstice:
I don't remember who asked (and I'm not in a position to search for it now), but it looks like CM fixed the Notification/Ringer volume linkage.

http://review.cyanogenmod.org/#/c/95329/
[ONE Android Development] musashiken:
The thing is some of us have been flashing SuperSU together with your builds for quite some time already. I personally do not like CM's own superuser but of course that's a personal thing.

So to suddenly not be able to flash SuperSU is kinda sucky but I understand if you don't want to support it. Looks like some of us have to force ourselves to get away from supersu.
[ONE Android Development] RobbieL811:
It's already in the upcoming build. About to release it.

Idk. I am providing built in root that works FLAWLESSLY. I'm not sure if it's Chainfire that needs to update something or something from CM that needs reverting but in the mean time, just use built in root. It WORKS! Why flash another app to handle root when there's already something that works perfectly?
[ONE Android Development] Crisisx1:
Okay I have a serious problem...

After doing a complete clean flash of 4/20 build and slim gapps (12.1) my phone is completely dead. It will not power on.

First the blue capacitive buttons were lit up and now nothing.

Tried everything to boot it up.
[ONE Android Development] johnb380:
Maybe try putting it on the charger and see if you can get to recovery friend. Also idk how often you clean flash but it can take up to 15 mins to boot up... Also you getting the ak splash screen and cm boot animation?
[ONE Android Development] PresidentMcCain:
Because CM's Superuser fork does NOT work perfectly. For example, ES File Manager causes the built-in root to freeze. i.e. always display the "#" symbol, even long after closing the app. The app also retains a lock on root access with the built-in root even when I have it set to "Always ask" for root permissions and "Remember choice" is unchecked, until a reboot.

Personally I've always been using SuperSU since CM12, and up until the 4/16 sync of CM12.1 it was working just fine. Newer syncs of CM12.1 completely broke the ability to flash SuperSU.. both 2.46 stable and 2.48 BETA.

In terms of what I think caused SuperSU to break, here are my findings: http://xdaforums.com/showthread.php?p=60207352#post60207352
[ONE Android Development] RobbieL811:
I have added a feature to remove the hash tag if that is the only issue. I will test ES File Explorer right now.

Edit --- AAAAAAANNNNNNNNDDDDDDDDDDD root works JUST FINE on ES file explorer. Created files in /system just fine and deleted files in /system just fine. Hash tag did stay, but root worked fine!
[ONE Android Development] RobbieL811:
Hey bud. PM me and I will try to help.
[ONE Android Development] LiquidSolstice:
For what it's worth, Viper4Android has never properly installed with Superuser. It always fails, citing a busybox issues. It has been this way since kitkat. Even now, on this build, it fails.
[ONE Android Development] RobbieL811:
Ok. Yall have made your point. I guess root fuc**** sucks! I got it. Idk what's up w/ SuperSU. Idk. I guess talk to Chainfire or CM developers. I'm tired of hearing about it. Works great for what I use it for and that's what I'm making the ROM for.
[ONE Android Development] musashiken:
Hey don't get us wrong. We love your work and we are not blaming you for the supersu thing.

So it looks like cm did something that made supersu not work. We'll go bug them instead.
[ONE Android Development] RobbieL811:
I have found the problem, but I don't want to revert it. I have busted my ass to add it and I don't wanna remove it.
[ONE Android Development] furrycurry:
Most apps which use root privileges for me leave the hash tag in the status bar until the app is terminated by force closing or clearing my recents. This is not a bug, nothing is freezing. *mindblown*
[ONE Android Development] Crisisx1:
After 15 minutes my phone booted up.. That was a bit scray lol. I did a bug report from dev options after the boot up but idk if that will help you any.

I seriously started thinking of what phone to buy next lol!
[ONE Android Development] JasonEddie:
Does the built in root in developer settings not work for you guys? I've been using that for quite a while now without any issues. No need to flash SuperSU in recovery IMO..
[ONE Android Development] RobbieL811:
I'm glad you got it going! It can take a while to boot up sometimes.

Also, to anyone that wants it, a new build. And NO, SuperSU doesn't work. I guess use one of the older builds if you want it. Added density changer and synced up w/ a bunch of CM stuff! Kernel version is at AK ver 220. Go get it....

ROM - cm-12.1-20150421-ROBBIEL811-UBER4.8-bacon

GAPPS - gapps.BETA.5.1.x.build.0.x-20150420
[ONE Android Development] MWilkenson:
Thanks for all your hard work man! Flashing now!

Edit: [MENTION=4911350]RobbieL811[/MENTION] , do you know what the DPI was on the previous builds by chance? Noticed things seem a little bigger haha. If not its no big deal! Thanks again for your amazing work!
[ONE Android Development] Genericxx:
Was @ 400 all the time, if i remember correctly
[ONE Android Development] MWilkenson:
Thanks for the response! I should have looked first, but there's options instead of manually entering it! Wasn't expecting that. I'll try 400 and see how it looks! Thanks man!

Edit: looks like 408 to me!
[ONE Android Development] Genericxx:
Mh... Strange... I thought it was 400. Multiple Roms use 400 as it is more eye-candy as stock 480. Personally i prefer 360, but that's too small for some people. I just got accustomed to it.
[ONE Android Development] RobbieL811:
It was 400 , but I changed it back to stock since I implemented the DPI changer that I was writing about when I did my little change log post. Also I edited it into the OP.
[ONE Android Development] Foxje:
Got some serious issues with latest (20 and 21) builds and GAPPS 20. Problems with Google Play Services, AOSP Keyboard crashes, Google Now missing (home app missing), Google account gone. No trying to go back to 18th with GAPPS of 8th.
[ONE Android Development] Mich2027:
Latest zero gapps 20/4 won't work for me says something about 5.1 blablabla...
[ONE Android Development] EkiFox:
Flash the previous gapps, it's working for me