yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] aleksik:
Awesome! Going to sleep now, but gonna change to your build tomorrow for sure! :)

Sent from my OPO powered by CM12 & AK kernel
[ONE Android Development] DespairFactor:
Damn [MENTION=4911350]RobbieL811[/MENTION], I am working on doing this with my kernel which is a fork of AK.

EDIT: Mind shooting me that pull request?:) my github is https://github.com/RIPng/AK-OnePone
[ONE Android Development] RobbieL811:
Are you having trouble getting it to compile? I actually just compiled w/ no problem. Idk what the f*** was going on earlier. Just merge in CM's cm-12.0 branch. Or I can submit a pull request if you want. Give me a sec.
[ONE Android Development] DespairFactor:
I meant the pull request with the new cm kernel changes:) I am not too sure where you grabbed all of those from. I will run a build after I merge them. Thank you in advance!

EDIT: I see where you pulled it, don't worry about the pull request
[ONE Android Development] ludester:
which gapps should we use?

edit: ended up using the one on here (https://s.basketbuild.com/gapps)
[ONE Android Development] RobbieL811:
Yeah. Any L gapps should be good. Hang on and I'll give a link to the ones I use.
[ONE Android Development] ludester:
First bug to report, can't seem to play any music with google play or apollo (getting playback error as soon as I play any mp3). Youtube works fine.
[ONE Android Development] jgcaap:
Nice... Cm 12 working stable?
[ONE Android Development] DespairFactor:
I am not sure how you got it to compile, I am getting errors on busybox:/
[ONE Android Development] RobbieL811:
Try this:

cd vendor/cm

then:

./get-prebuilts

Then try to start the compile again. That should fix the problem.
[ONE Android Development] DespairFactor:
I run that every time I build:( It's part of my script
[ONE Android Development] RobbieL811:
Idk then. I didn't do anything special. I got that busybox error then ran that and it compiled.
[ONE Android Development] DespairFactor:
Did you modify source at all? All I did was change envsetup for my kernel toolchain and added my own kernel into the the manifest. I also changed the defconfig to the correct one for my kernel.
[ONE Android Development] RobbieL811:
You should not even touch envsetup.sh. That is not the proper way to build w/ another toolchain. Look at what I did here. I basically removed the 4.8 toolchain from the default.xml and then told default.xml to pull from Sabermod's github into the directory that WAS the 4.8 toolchain. Look. https://github.com/RobbieL811/manifest/commit/c1d2df7b062a868b99d28f67fca23f48af8ed6cf Disregard the androideabi-4.8 toolchain, as it is for ROM compiling and it doesn't work. The only thing that you want to change is the 4.9 toolchain. That may be your problem.
[ONE Android Development] DespairFactor:
Thanks, I will give it a go.
[ONE Android Development] RobbieL811:
You should never touch envsetup when changing ROM or kernel toolchains. It is an old and HACKY way of doing it. They way that I posted still isn't the exactly proper way lol. But is a little bit better.
[ONE Android Development] chayjinn:
is there any pico gapps package for lollipop?
[ONE Android Development] DespairFactor:
I only used to maintain PAC on S4:P I don't know much about modifying ROM source still haha
[ONE Android Development] RobbieL811:
Well, the way that you were doing it, I think, used to be a widely accepted way. I just think it's better to tell the compiler to use a different toolchain. That's what I normally do w/ Slim. I am not super familiar w/ CM's build, so I'm not exactly sure how to do it in CM's source and I was lazy, and didn't feel like hunting a way lol so I just did what I showed you. In Slim's source, I actually tell the compiler to use a 4.9 toolchain in build, and in Boardconfig of the device.
[ONE Android Development] DespairFactor:
Still no luck:/ exact same error
[ONE Android Development] RobbieL811:
I'm not sure man. It's compiling fine for me. I have done several builds. You have to be missing something somewhere.
[ONE Android Development] DespairFactor:
I am getting a couple errors at the beginning that I honestly can't be bothered to figure out since everyone else is building CM12 right now anyhow.
[ONE Android Development] RobbieL811:
I mean, I can't help you with ANYTHING like this. Lol. I need to see some errors. Lol. I haven't seen one. Pastebin. I will try.
[ONE Android Development] DespairFactor:
I wasn't asking for help:) I just wasn't sure if you ran into the error at the beginning. I will pastebin the error though, just give me a moment, I will actually send the build into a log file
[ONE Android Development] RobbieL811:
Either way is fine. Just so that I can see a log. I'll help if I can.

Sent from my Nexus 7²
[ONE Android Development] DespairFactor:
This is what I got thus far. http://pastebin.com/PrxSHnnj

I need to up the resources on my VM before I get angry enough to smash my PC
[ONE Android Development] RobbieL811:
Yeah. I can't help you w/ that one. I don't think it's a busybox error though. My advice to you would be to rm -rf that folder and repo init again. Something isn't right. I didn't see any of that tonight when I built and I am building again right now w/ Sabermod. Are you sure that you repo init the right address? I would redo it if I were you.
[ONE Android Development] DespairFactor:
I did it a few times:( I repo init git://github.com/CyanogenMod/android.git -b cm-12.0
[ONE Android Development] RobbieL811:
Idk man. Stock source is compiling fine for me. I repo init w/ that address. Then I repo sync again w/ the blobs in manifest, then I cd vendor/cm and get prebuilts, then I start my build. Works fine. You are trying to compile for OPO right?
[ONE Android Development] DespairFactor:
Yes sir, this is weird. I repo init, add my local manifests with the blobs and my kernel source, then repo sync.
[ONE Android Development] RobbieL811:
What kernel source? You aren't using stock kernel source?
[ONE Android Development] DespairFactor:
My kernel source is based on AK which is based on stock.

How are you adding AK into it?
[ONE Android Development] RobbieL811:
Don't you think it would be best to do a build w/ all stock sources first??? That way you can make sure that stock source is working. Here you have me hunting errors and you aren't even using stock source lol. I had problems compiling w/ ak. I had to update it. I think that AK has already done it just a little while ago, but I would strongly advise you to compile w/ stock first. I ALWAYS do that.
[ONE Android Development] RobbieL811:
Alright guys and gals. Here it is. Sabermod CM-12.0. Rom compiled w/ Sabermod 4.8 and AK kernel compiled w/ Sabermod 4.9! Finally got it done! Was much easier than on KK! Enjoy.
[ONE Android Development] ksenhuck:
First thanks for your work. Second, the biild has the latest cm sources? Because I think they fixed the video playback...

Thanks in advance
[ONE Android Development] Nickamina:
Does this include the justarchi optimisations from the cm11 builds too?
[ONE Android Development] nathlynn22:
[MENTION=4911350]RobbieL811[/MENTION] does your build of cm12 include any type of non stock mods? So the ability to edit quick settings tiles. And is it using google keyboard or aosp keyboard thanks.
[ONE Android Development] RobbieL811:
It's the same as it's always been. CM built with Sabermod.
[ONE Android Development] nathlynn22:
Just realised you don't have any bundled gapps for your build. Would any 1 know of a set of lollipop gapps to give me aosp keyboard instead of google? As I like the extra key functions for punctuation? Would rather not bother with Swiftkey either thanks.

---------- Post added at 11:21 AM ---------- Previous post was at 11:19 AM ----------

Sorry mate never ran your cm11 sabermod always been on sabermodded slim build of yours but wanted to try out a 5.0 build and currently running bpears build
[ONE Android Development] RobbieL811:
https://s.basketbuild.com/devs/RobbieL811/Gapps/L/

I think that these will give you the desired effect.
[ONE Android Development] nathlynn22:
Thanks I'll give it a go in a bit best get back to the job and get this alarm fitted... :D

---------- Post added at 12:15 PM ---------- Previous post was at 11:33 AM ----------

Yeah that's the gapps I'm looking for great thanks. I'm guessing there are no mods etc unless I've missed them. And cannot seem to get root using supersu 2.27 which is odd as I managed on 2 other 5.0 builds.
[ONE Android Development] funCrash93:
Thanks :)

just some Questions :

what AK Version is inside.? (020 or 021)

synapse and UKM works on Lollipop.?

root inside or have to flash SuperSU.? (2.27Beta right.?)
[ONE Android Development] TiVON:
1. Since the latest sources are used I assume 21 is inside.

2. Worked for me on the latest K900 CM12 Build.

3. No idea. Just flash it directly after you flash the ROM. Little trouble and that way you are sure :)
[ONE Android Development] jgcaap:
Cm11 was removed?
[ONE Android Development] DiluTe:
Looks like it, some older versions can be found here:

https://www.androidfilehost.com/?w=files&flid=19175
[ONE Android Development] noky76:
What cm12 build is based your ROM?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] Sick1:
Its build directly from cm12 source provided by cyanogenmod.

Gotta test this, i think i start building my own when official nightlies start rollin.
[ONE Android Development] RobbieL811:
EVERYTHING IS STOCK FOR NOW! Except for toolchains. For everyone asking if this has this or this has this. No, it doesn't Geez! It's my first freaking build lol. Give me some time. This is not the only project that I work on.
[ONE Android Development] nathlynn22:
OK darling only asked [emoji28] thank you very though.
[ONE Android Development] RobbieL811:
Lol. I don't mean to sound like a di**. I'm really not, but a few things have been asked already. I can see where this is going. It is all stock for now. My main focus right now is SlimRoms. Whenever I get some extra time, I will try to add in a few optimizations and such. Sorry if I came off sounding like an @$$hole.
[ONE Android Development] nathlynn22:
Not at all all good here.
[ONE Android Development] byAidan:
You didn't at all bro :good:

Thank you for making this ROM! ;)

Have a good day
[ONE Android Development] acuicultor:
I been waiting for this and finally here it is. Im always Happy with Robbie's buids. Thanks sir.

Sent from my Crispy Bacon
[ONE Android Development] gacalderon:
Just did a clean install. The build is running smoothly as expect. However, Backlit keys delay turning off when the screen is turned off.
[ONE Android Development] mr_clean5953:
Do we need to install root? I can't get synapse to work
[ONE Android Development] noky76:
Download link gives page not found
[ONE Android Development] ukhoughsx:
I had to install SuperSU Beta 2.27 to get root on a different CM12 rom
[ONE Android Development] byAidan:
Anyone else having trouble getting root to work?

EDIT: Wiped cache and re-flashed SuperSU and it's working :)
[ONE Android Development] DerRomtester:
No problems here. I just flashed latest super su beta version.
[ONE Android Development] garz:
2.22?
[ONE Android Development] DerRomtester:
2.27
[ONE Android Development] dansou901:
For me root is working fine with stable version (2.16)
[ONE Android Development] stryker09:
CM12 bug. I just use the onscreen nav buttons from now on.
[ONE Android Development] garz:
Can you provide the link.. I couldn't find it. Only 2.22.
[ONE Android Development] MrMarkEdward:
2.27SU
[ONE Android Development] noky76:
What is last twrp version? I have 2.8.0.1 but couldn't flash
[ONE Android Development] Setting.Out:
2.8.1.0
[ONE Android Development] gacalderon:
Contacts randomly FC
[ONE Android Development] hhp_211:
http://techerrata.com/browse/twrp2/bacon
[ONE Android Development] gacalderon:
Download Flashify from the playstore, easiest way to update.
[ONE Android Development] O.a.T.:
Haven't looked in detail at the gapps Robbie posted, but it may be due to an old Contacts.apk. Believe the latest one in CM12 fixes that, or a new Contacts.apk is floating around here on xda. You could replace the one in the Gapps package with either of the above and give that a try.

My contacts isn't FC'ing, but my GApps is still a WIP, so I'm hesitant to post them.
[ONE Android Development] byAidan:
Just a quick update, this has been working perfectly fine for the past few days, extremely smooth and the battery life is amazing as usual!

Thanks [MENTION=4911350]RobbieL811[/MENTION] :good:
[ONE Android Development] RobbieL811:
Thanks bud. Compiling an update right now!
[ONE Android Development] DJMartini:
Thanks again [MENTION=4911350]RobbieL811[/MENTION] ... There are a couple of bugs, but that's expected in the early stages and CM will work them out. Thanks for continuing to provide us updates for the fixes! =)
[ONE Android Development] EasyGoingXD:
When is it online? *_*
[ONE Android Development] gacalderon:
Looking forward to the new build!!! thanks [MENTION=4911350]RobbieL811[/MENTION]
[ONE Android Development] jukiewalsh:
When it's done.
[ONE Android Development] raycaster3:
You can use the hardware keys. At times, the delay is longer than others, but if you disable ambient display (which at this point only works for notifications, and stays lit for about 5-7 seconds at most) the keys do back to their normal behavior.

Obviously, you can just use on screen keys if you prefer, but if like the extra real estate, there's a workaround.
[ONE Android Development] EasyGoingXD:
No **** really? ^^
[ONE Android Development] gacalderon:
It worked for a period of time, 80% of the time the backlit turns off then immediately on. Only work around I have found to be 100% is to let the screen timeout.
[ONE Android Development] aleksik:
26/11 build is up guys! :)

Sent from my OPO powered by CM12 & AK kernel
[ONE Android Development] GIKE:
file size it's only 64 MB. bad upload?

edit: still uploading, I think.
[ONE Android Development] jukiewalsh:
F5 f5 f5 f5 f5 f5 f5 f5
[ONE Android Development] wozn:
Just wait for announcement. Still uploading.
[ONE Android Development] EasyGoingXD:
still uploading ^^
[ONE Android Development] RobbieL811:
GO GET IT!!!!!!!!
[ONE Android Development] RobbieL811:
Hold up guys. It didn't upload properly lol. Give me a sec.
[ONE Android Development] aleksik:
Lol, I was too excited that I didn't notice it wasn't fully uploaded yet. Noticed something was wrong when flash got aborted :D Trying again now, thanks again Robbie! :)

Sent from my OPO powered by Robbie's CM12 & AK kernel
[ONE Android Development] EasyGoingXD:
fully online now :)
[ONE Android Development] RobbieL811:
Ok go try it. Yall kept killing my upload lol. There was 30 downloads before the file even finished uplading lol!!
[ONE Android Development] latenightchameleon:
Latest build bootlooping on both clean and dirty flash
[ONE Android Development] ludester:
I'm not getting past the Cyanogenmod logo.... dirty flashed.

Edit: seems to be the kernel in my case. I flashed another kernel (Tyr version 44) and its now booting fine.... will try flashing AK kernel again
[ONE Android Development] DJMartini:
Same with bootlooping
[ONE Android Development] EasyGoingXD:
Bootlollipoping also with newest AK-Kernel :/
[ONE Android Development] RobbieL811:
uh oh.
[ONE Android Development] NikoZBK:
To those bootlooping, have you tried powering off and trying again? Sometimes that works.
[ONE Android Development] RobbieL811:
Did it boot fine for you??? Generally when 5 people bootloop, there is something else wrong. Also, to all the bootloopers, did it make it to the CM splash then loop?
[ONE Android Development] NikoZBK:
I didn't get a chance to download the build before it was removed. Just thought I would throw it out there because I see people bootlooping on the first boot from time to time and generally a power off and second boot do the trick.
[ONE Android Development] RobbieL811:
Lol. Sorry. I had to take it down. I am testing another build right now. It was a bad build.
[ONE Android Development] fusionjack:
i suspect the latest commit in device/qcom/sepolicy is causing bootloop.

i updated slim sources with it and i also ended up with bootloop. i'm still building now...
[ONE Android Development] RobbieL811:
AH! Thank you for the heads up FJ!!! I appreciate it! I was thinking that it may have been some of AK's kernel commits. But maybe not if you are experiencing the same thing.
[ONE Android Development] fusionjack:
confirmed! that is the culprit...i spent almost 3 hours to find out what causing the bootloop :eek::eek::eek:

now i can sleep peacefully :p
[ONE Android Development] RobbieL811:
Lol. Well, I'm glad that you found it and saved me needless hair pulling time!!! Lol. It's just the one single most recent commit in that repo? Or is there more than one?
[ONE Android Development] ludester:
new build working good :good:
[ONE Android Development] RobbieL811:
Yup. Just booted for me too. Everyone, new NON BOOTLOOPING build is up now. Sorry about that earlier. CM snuck one right by me!

https://s.basketbuild.com/devs/RobbieL811/Oneplus One/CM Builds

Thanks to [MENTION=1228651]fusionjack[/MENTION] for picking up on that commit! He just saved some time!!! Thanks.
[ONE Android Development] NikoZBK:
Anyone having trouble installing it as a secondary ROM?
[ONE Android Development] OmegaBlaze:
Same here. Just swap your primary rom to secondary & install as primary. Working fine here.
[ONE Android Development] acuicultor:
Dirty flashed last build over 26 version and it booted fine. Yeah!!

Sent from my Crispy Bacon
[ONE Android Development] aosimon:
And then swapping it back after? Or it'll have to stay as primary?

1+1
[ONE Android Development] OmegaBlaze:
Keep it as primary for now.. Its a problem that the dev has to fix with the installer & multirom
[ONE Android Development] fusionjack:
you can now include sepolicy commit again, but you need to cherry-pick this commit for our device:

https://github.com/CyanogenMod/andr...mmit/f99449beadbfd798d1ebc56cec184e6fe22eb486
[ONE Android Development] gacalderon:
Ugh that backlit bug is bother me. Any news on a fix in the future?
[ONE Android Development] Khizar:
Download the app capacitive buttons from play store. Deactivate back lights and then reactivate it and that'll fix the issue.

Sent From My A0001 With AK Awesomeness!!
[ONE Android Development] gacalderon:
Thank you!!!!!!!!
[ONE Android Development] AhmedFaiz:
Wrong post. Waiting for next build with support as secondary ROM.
[ONE Android Development] RobbieL811:
New build up in the usual place w/ changes from CM, and also, I added CameraNext back. Whoever flashes it first, let me know if the camera is working properly. I didn't test flash this build.
[ONE Android Development] :
I think it is a stupid question, but can I flash this over a stock cm11 build?
[ONE Android Development] dansou901:
EDIT: I didn't saw you wanted to flash CM12 over CM11. That's not advisable at all.
[ONE Android Development] kantjer:
I would never advise to flash a CM-12 based build on top of a CM-11 stock or otherwise.
[ONE Android Development] javydawg:
Just flashed the latest build (Nov 28th) with lollipop gapps 11-17 . Everything is running smoothly and the camera is too! Thank you! This rom is my new daily :P speaking of the camera tho it has the save as raw image option and works. 4k recording works, 1080p works, 1080p 60fps works, 720p works, and lastly 720p 120fps works. Great work!
[ONE Android Development] dansou901:
You're right, missed that CM11 part. I edited my post above.
[ONE Android Development] RobbieL811:
Awesome! That's fantastic news!

Sent from my 1+1
[ONE Android Development] fredzen14:
How about the front camera recording? Is it fixed? Can whatsapp send audio chat? Does it detect usb storage from setting when OTG ?

Thanks for testing bro!
[ONE Android Development] RobbieL811:
Why don't YOU test all of that stuff and report to us if it works lol. Sounds like they are things that YOU need working.

Sent from my 1+1
[ONE Android Development] gacalderon:
11/28 Build is running smoothly as expected. Thanks [MENTION=4911350]RobbieL811[/MENTION] for updating regularly!
[ONE Android Development] javydawg:
I completely forgot to test out the front camera video recording ... I guess i was just too excited with the ROM >.< anyways I tested it and sadly the camera crashed :( BUT I found out something interesting... If you go into settings and change the audio codec from AAC-->AMR-NB the front camera recording works! But snaochat force closes when attempting a front camera video :( As for whats app I don't use it sorry I cant test that.
[ONE Android Development] merikgvr4:
Is there a workaround for an external SD card. Bought an otg microsd card reader and when I insert it, phone won't mount it.
[ONE Android Development] RobbieL811:
I will see if I can work on this this evening and get OTG automount going.
[ONE Android Development] merikgvr4:
Thanks chief. Much appreciated.
[ONE Android Development] RobbieL811:
Do you guys notice perceived performance gain like we had with the Sabermod builds on KK? The reason I ask is b/c Google started using 4.8 toolchains as stock toolchain in Android 5.0. I was just wondering if you guys noticed any jump in performance with these builds vs stock CM?

Sent from my 1+1
[ONE Android Development] :
This is by far the smoothest lollipop rom
[ONE Android Development] atlharp:
I am running it close to stock and it is pretty snappy. Solid work.
[ONE Android Development] magnamentis:
not sure so just saying

this is about hope, not about demand, just trying to explain my point of view :)

i hope that the cm11s lockscreen will not be forced down on me because albeit i respect that some like it, albeit i think often it's only about having newer, more than about better things, i will never go with that lockscreen. for me a lockscreen has to be functional and simple and certainly not colorful and fancy. so as i understood the lockscreen from cm11s can be implemented already now, if someone really wants it desperately, so i think/hope that it will not be necessary to force it upon the rest of us. as long as this rom, which is running better than cm11 nightly is closest possible to nightly but with optimizations as to smoothness and battery life, more than as to features, it makes sense, if i want more features, i could choose any cm-based or other custom rom.
[ONE Android Development] DanielFran:
You have the zedomax thread on xda: http://xdaforums.com/android/general/how-to-convert-android-smartphone-t2846303
[ONE Android Development] jgcaap:
Are those files updated? Would like to keep cm11s features.
[ONE Android Development] Roymik:
Even if the cm11s lockscreen will be set as the default one,as far as I know you can simply go in settings>lockscreen>custom lockscreen and untick the option,that way you will have the classic android lockscreen. Tested on official Cm11s and on various ROM after installing the cm11s lockscreen separately.
[ONE Android Development] jgcaap:
Ahhh so please insert here the option robbie.
[ONE Android Development] Quantum_Sensation:
Hi, newbie for this phone. Just got the device few hours ago. Is there any steps required prior to install this ROM? Do I follow the steps based on this thread http://xdaforums.com/oneplus-one/development/rom-sabermodded-slim-t2853904 ?
[ONE Android Development] magnamentis:
thanks a lot :)

that takes care of my concern, thanks for providing this helpful answer :)
[ONE Android Development] dansou901:
Not really. Just follow that steps you linked to and you will be fine.
[ONE Android Development] dansou901:
Not really. Just follow that steps you're linked to and you will be fine.
[ONE Android Development] dansou901:
Not really. Just follow the steps you linked to and you will be fine.
[ONE Android Development] Glatzi:
[MENTION=4911350]RobbieL811[/MENTION]

AK makes the assumption that perhaps some of the O3 optimizations are responsible for the kernel crash which I have posted a little bit earlier.

Could you take a look please?
[ONE Android Development] Quantum_Sensation:
Is the gapps included in this ROM?
[ONE Android Development] nikzDHD:
No you will need to flash this separately.