yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] martinoff:
It will work

I have add it with all the other export commands in your script

---------- Post added at 02:33 AM ---------- Previous post was at 02:27 AM ----------

LANG=C is nothing else that telling the session to use the default locale, so it could help other distros too or other settings or any mess with locale

Also as arch is very bleeding edge that glibc maybe will come to other distros later
[ONE Android Development] Mrwargod:
I guess that in that case it could be good to add it then. :good:
[ONE Android Development] mammenj:
In latest CAF, when long pressing power button, device reboots - doesn't show power button option. Is this same for all or just me
[ONE Android Development] Almayce:
Works here no problem.
[ONE Android Development] Heisenberg:
No such problem here, power button is fine for me. Are you using stock kernel? Any theme?
[ONE Android Development] gugas123:
Also everything fine here (caf build)
[ONE Android Development] Tn_wijaya:
Is it still required to flash Sultan' disable CPU underclock for this Rom build?
[ONE Android Development] Heisenberg:
It isn't required. But if you want to access frequencies above 1958MHz you'll need to. I don't think it really needs those frequencies though, my phone runs like a dream topped out at 1958MHz.
[ONE Android Development] MurdererFight:
So it's possible to flash AK Kernel?
[ONE Android Development] abhibnl:
AK kernel doesn't support CAF roms. So no, it won't work on slimsaber caf. However, it would work on original slimsaber.

Sent from OnePlus One
[ONE Android Development] Whaaaaa:
I have the exactly same issue on the 08/26 build. Stock Kernel and i dont change kernel settings.

Edit: with no layer installed I don't have this bug, but with layer I Have soft reboot. I've tried with two layers.
[ONE Android Development] Ofthecats:
I think he is developing a caf version
[ONE Android Development] mammenj:
OK, so there could be an issue... anyway I am doing a system wipe and then flash and see.
[ONE Android Development] TemplesOfSyrinx:
I think it is layers that are causing this problem. I had Graphite layer installed and had the same problem. Long press the power button and instant reboot. I uninstalled all layers, rebooted and the problem is gone.
[ONE Android Development] gugas123:
Just tested the ROM against the new certifi-gate vulnerabilities aaannnd no problem was detected in this ROM :)
[ONE Android Development] HaTrED_:
Well, I'm using it without any problem at all... We're you using SuperSU back then?
[ONE Android Development] TemplesOfSyrinx:
Yes. I clean flashed latest CAF Slim with latest custom gapps and SuperSU 2.46

Should I skip SuperSU now?
[ONE Android Development] kantjer:
Good guess, cm sdk implementation is causing the issue.

I have reverted androidfw: Declare and load cmsdk resource package w/ id. and androidfw: fix cmsdk attribute lookup and the ROM is booting again with all layers loaded.

I'm not sure what the commits are supposed to do exactly but they are causing the ROM not to boot when layers are used.

EDIT: The recent layers commit in package settings is just a comment change.
[ONE Android Development] soto2080:
I'm using Graphite too.

And I also had this issue.

Remove and all fine.
[ONE Android Development] abhibnl:
Can you please share a link to the post where he has mentioned that he is working on a pure CAF kernel? i haven't hecked his thread from almost 10 days and man it's too many pages to read. :D
[ONE Android Development] mammenj:
Anyway I clean flashed and without any layers and it works fine.

So it could be layers or dirty flash, not the ROM.
[ONE Android Development] gordon.shameway:
http://xdaforums.com/oneplus-one/orig-development/kernel-ak-t2832168/page1942
[ONE Android Development] soto2080:
Here you are

https://github.com/anarkia1976/AK-OnePone-Reborn-CAF/tree/ak-12.1-official-CAF
[ONE Android Development] HaTrED_:
No, I don't think that's necessary but I've noticed now that you're under slim caf version, right?

My feedback was for normal version... My bad!
[ONE Android Development] Whaaaaa:
Well, with 08/24 build i don't have this issue., only with 08/26 .

So, i don't know if it's layer or rom related.
[ONE Android Development] CounterC:
I have been following the thread for a while now. I'm on normal slimsaber. What benefits do you guys notice CAF vs AOSP? are all the features of AOSP slim still included? I would like to know more...

Sent from my A0001
[ONE Android Development] kantjer:
It's clear there is an issue with layers when using the 26/8 build.

But the good news, 27/8 build is running fine again.

Showing off new app :p
[ONE Android Development] abhibnl:
It's 100% slimsaber with kernel sources based on caf. So all the slimsaber features are still present just some of the device sources are caf based.

Sent from OnePlus One
[ONE Android Development] CounterC:
What about the features Sultan XDA has been working on? Custom hal and his added features on the camera? Are you using CAF? What do you find better or worse?...

Sent from my A0001
[ONE Android Development] inffy:
Maybe read this thread. All those are already answered
[ONE Android Development] CounterC:
Sorry I'm a little bit late to the thread. Got some reading to do...

Sent from my A0001
[ONE Android Development] abhibnl:
You should go through the thread quickly looking for CAF posts. It'll answer all your queries as someone already proposed to you. However let me answer this one. Yes this rom uses sultan's device tree so all the hardware features are present. The difference is, his rom is based on pure CM12.1 and this one is based on slimsaber. So custom hal is present and snapdragon apk is supported. I used caf for almost a month and it's really smooth but the idle drain is really high. As of now, i'm on newly released COS12.1 and it's amazing. :good:
[ONE Android Development] Zeus20:
[MENTION=3306843]kantjer[/MENTION] because viper requires SuperSU have you looked into building it into the rom from install.
[ONE Android Development] martinoff:
new build

https://www.androidfilehost.com/?fid=24052804347802393

if anyone want to try it be aware that I'm building again with partition format and not with zip format

so to avoid troubles you have to flash with rom also gapps & supersu. Also any script for surviving dirty flash won't work (supersu,layers,adaway etc)

how to flash

boot on recovery

flash rom

flash gapps

flash supersu

reboot

v4a is buitin now thanks to [MENTION=5131448]reS28raM[/MENTION] and [MENTION=3306843]kantjer[/MENTION]
[ONE Android Development] just4u32:
I've tried various combinations, including of course newest of everything.

I've tried clean flashing, dirty flashing, flashing over Render's. Nothing worked.

Would you try it yourself mate?
[ONE Android Development] chikimonke:
Besides the format of how it's installing, what is different about your build? Just curious.
[ONE Android Development] martinoff:
build with oracle jdk and removed packages browser,calendar,mail,exchange,gallery,almost all scrensaver,audiofx (replaced by v4a)
[ONE Android Development] kantjer:
If I remember correctly [MENTION=1228651]fusionjack[/MENTION] did that in KK for a while but there where issues so he reverted.

#whiteuimustdie
[ONE Android Development] fusionjack:
ok, i'll revert them and revisit them again later. i suspect the id might be wrong or clash with layers theme.
[ONE Android Development] fusionjack:
i think i saw [MENTION=2095315]ezio84[/MENTION] has supersu commit back then.

if you find commit for it, i also interested to integrate it.
[ONE Android Development] ezio84:
Yes mate, it's in the commit list:

https://github.com/ezio84/scripts/blob/lp5.1/My_mods-commits_and_tips/Commits-list-with-links.txt

("add supersu" and if you want it also "launch supersu from settings") ;D

Ps: using latest supersu beta since it's been released, no issues so far.
[ONE Android Development] astrall:
[MENTION=5284595]YoshiShaPow[/MENTION]

Any news on OTA implementation on your CAF builds?
[ONE Android Development] adinkwok:
Uuuh, soon. When i get the time to set it up :D :good:
[ONE Android Development] ~KV:
Is idle drain still high on the latest CAF build?:(
[ONE Android Development] Heisenberg:
Nope, my idle drain seems to be fine.
[ONE Android Development] ~KV:
Can you explain with numbers?
[ONE Android Development] CounterC:
2 questions:

What's amazing about new COS12.1?

Can you link me up?

PS: the latest Sultan update is based on stable COS 12.1 as of today.

Sent from my A0001
[ONE Android Development] Heisenberg:
Nope, not really, I don't waste time collecting data about voltage levels during idle state. All I can say is that my phone only lost about 5% overnight last night.
[ONE Android Development] ~KV:
Well, 5% drain is a bit too much, don't you think?:(

On stock SlimSaber it is like around 2%...
[ONE Android Development] Heisenberg:
Are you joking? 5% in an eight hour period with cell service turned on is good. Honestly, people expect ridiculous things from their battery, if the device is on, even in deep sleep, it uses power.
[ONE Android Development] Almayce:
For some reason some apps start to "ignore" the fact that I have navigation bar enabled and stretch through the whole screen, like you see in screenshot. The problem is that I can't access those buttons under the navbar. Any of you noticed that or that's just me?

/oops, now you all know where I live! Luckily the address is wrong :D
[ONE Android Development] abhibnl:
Google is your best friend ??

If you still won't find anything, which is highly impossible, hit me up a PM.

Sent from OnePlus One
[ONE Android Development] FloorFox:
The caf version has snapdragon camera already installed or i have to install it myself?
[ONE Android Development] gugas123:
It is already instaled ;)
[ONE Android Development] BrandoHD:
I have experienced this issue with Snapchat, so because of this, I had to use the "Expanded Desktop" feature to hide the Nav bar so that I can have access to all the controls, when I need the Nav bar, I just swipe up :sly:
[ONE Android Development] kantjer:
Thanks,

Are you sure these commits are correct.?

The first commit places UPDATE-SuperSU.zip in system/addon.d.

If I understand the full script the zip is extracted and installed after the ROM flash. Still system/addon.d doesn't feel like a logical place to place the zip.
[ONE Android Development] fusionjack:
agree.

there is now a folder 'install' inside rom zip file. we can use this like backup tool thing. this should be more appropriate place.

example: https://github.com/SlimSaber/vendor_slim/commit/504446c0de01011c83991ac9bc9c25448110a1a6
[ONE Android Development] fusionjack:
i think this needs to be fixed from app side. it should be possible to query whether the rom has enabled navbar or not and then put the bottom area on top of navbar.

i did similar thing for clear-all recents button.
[ONE Android Development] Almayce:
Good idea, thanks! I haven't used expanded desktop whatsoever, I didn't even know what it does.
[ONE Android Development] BrandoHD:
I already sent feedback to snapchat about it, don't really know if that would do anything though
[ONE Android Development] ravvio:
Guys can i dirty flash ur builds over Fusionjack's build? Also can we expect these builds to be Daily Driver, the basics should work hopefully. :o
[ONE Android Development] rogi19:
[MENTION=3306843]kantjer[/MENTION]

http://review.cyanogenmod.org/#/c/107828/

Maybe this could fix the mobile radio active bug, would be cool if someone could make a build with the commit implemented for people to test
[ONE Android Development] martinoff:
Don't know for caf builds but kantjer and my build yes you can dirty flash over fusionjack builds

I flash new rom once a week ~10 days, so yes it is my daily driver and I'm sure kantjers build are rock stable also
[ONE Android Development] ezio84:
Uh yes good catch guys, i added it long time ago and forgot it :D
[ONE Android Development] kantjer:
interesting, I was just about to start a test build with SuperSU integrated so added this also :fingers-crossed:

Edit: SuperSU integration not working yet
[ONE Android Development] CounterC:
Guys the search function is down on the website so sorry if these questions are already answered:

- @ kantjer, can I dirty flash your CAF builds?

- is the xposed version mentioned in the normal SlimSaber thread also working in this CAF ROM?

Thanks!
[ONE Android Development] chikimonke:
I don't believe [MENTION=3306843]kantjer[/MENTION] has a CAF build, but there is linked to in the OP and yes, if you manually wipe system, cache and dalvik you can dirty flash CAF SlimSaber over regular SlimSaber. Just make sure you're using the stock rom kernel or a CAF compatible one.
[ONE Android Development] ~KV:
Lol no, I wasn't joking ...I lose around 2% overnight (over a span of 7 hours)...with cell service turned on.
[ONE Android Development] CounterC:
Sorry you're right, it's [MENTION=2270252]yoshis[/MENTION]haPaw build. Can he answer instead? Can I dirty flash your incremental updates?

What about xposed guys?
[ONE Android Development] chikimonke:
That's the build I'm on, once you follow the directions I put above or clean flash the build, dirty flash shouldn't be an issue. No idea about Xposed, don't use it myself, I find it does more harm than good in the long run.
[ONE Android Development] gugas123:
Ive dirty flashed from the slim custom caf to the normal custom slim and back.

Did not even erased system and ROM (in both versions) work with no problem when dirty flashing between them.

I've done this since the the slimcaf are being build, though I use no layers, custom kernel neither xposed
[ONE Android Development] ravvio:
[MENTION=3306843]kantjer[/MENTION] In your latest build 08/27 i am unable to start Google now when we swipe up from home button. The circle comes sometimes and most of the times it doesn't. I was facing same issue on 08/22 build of [MENTION=1228651]fusionjack[/MENTION].
[ONE Android Development] Heisenberg:
I meant the part about 5% being too much drain overnight.
[ONE Android Development] adinkwok:
Currently cooking up a CAF build with a possible fix for the modem battery drain that plagues all lollipop ROMs. Thanks to [MENTION=4296062]abhibnl[/MENTION] for showing it to me. I have no idea whether or not this will work so let's test this out.
[ONE Android Development] adinkwok:
DEV-UPDATE: Yeah so I kinda messed up the changelog because I forgot to upload it before wiping it from my build server. The build is uploaded but I am not able to provide a changelog... Sorry for the inconvenience :crying:

SlimSaber-CAF-bacon-5.1.1-20150828.zip
[ONE Android Development] kalapapa:
Thanks so much. Does it have the mobile radio activity fix?
[ONE Android Development] adinkwok:
Hopefully, maybe, possibly. Please test it out!
[ONE Android Development] kantjer:
I have added the radio active bug patch by CM and also the SuperSU integration was reported to be working by a builder on Hangouts that used my commits.

I forgot to remove the SuperSU backup/restore script when flashing the ROM so hadn't tested SuperSU integration in the last build myself.

I will post a test version soon for those who want to test.
[ONE Android Development] CounterC:
I would be happy too...
[ONE Android Development] adinkwok:
Sorry guys, I just made a newer CAF build with the above changes. If you do not want to reflash the rom, just flash the boot.img above. Sorry about this :crying::crying:

SlimSaber-CAF-bacon-5.1.1-20150829.zip
[ONE Android Development] arifqur:
The last version that you posted did not boot for some reason.

Going to try the new one
[ONE Android Development] beany>:
Just for info, both dirty flashed fine here.
[ONE Android Development] dead0:
it seems if u have a theme installed, it breaks the power menu as if u press the power button for the reboot options, it restarts
[ONE Android Development] beany>:
On the latest build, max CPU seems to be locked on 2457. Was that the intention?
[ONE Android Development] nonoperez:
Booting fine here, testing new radio fix.
[ONE Android Development] beany>:
I've seen a few Bluetooth related issues, so thought it might be worth mentioning here, in case it may help. [MENTION=5284595]YoshiShaPow[/MENTION] 29/8, Bluetooth would not connect at first. I had to switch it off and back on. When switched off, the quick tile disappeared. Bluetooth then paired and worked, although it did disconnect once after five minutes (with headphones and phone in pocket). After that all was fine.
[ONE Android Development] soto2080:
[IMG="fre"]http://i.imgur.com/FK9SxFy.png[/IMG]

CAF version

It seems work fine.

And in 8/29 layers still break Power Menu.
[ONE Android Development] Whaaaaa:
Not for me, dirty flash don't work with 08/29 build.
[ONE Android Development] kantjer:
SlimSaber-bacon-5.1.1-20150828.zip
[ONE Android Development] Whaaaaa:
The same, still present in the 08/29 build :(

Edit: no soft reboot wihtout framework- res installed ( in layer manager)
[ONE Android Development] kantjer:
Radio active bug seems to be fixed.

Used mobile data for about 3 hours.

#whiteuimustdie
[ONE Android Development] track909:
OTA is working? To official rom or to your mod rom?

---------- Post added at 04:17 PM ---------- Previous post was at 04:13 PM ----------

OTA is working? To official rom or to to your mod rom?

How can I set settings menu with double columns?
[ONE Android Development] FloorFox:
The dev said battery drain is also fixed. Did you noticed that?
[ONE Android Development] Stylo King:
What battery drain? There isn't any excessive drain using mobe data..Just the counter that shows up in battery stats..

When mobile data is on with screen on, it will drain more than wifi (Common sense)

When mobile data is on with screen off, It will result in idle drain ( Also a common thing, You can notice on kitkat too).

People just go mad with Mobile radio active bug because they see it in the battery stats.
[ONE Android Development] FloorFox:
Mobile radio active bug isn't just a bug in battery stats. It's a big battery killer
[ONE Android Development] Nos_20:
Not got the same results here [MENTION=3306843]kantjer[/MENTION]

------------------------------------------------------

ROM : SlimSaber Latest by Fusionjack

Kernel : ☆ AK ☆ Latest Beta by AK
[ONE Android Development] bombadier:
http://xdaforums.com/showpost.php?p=62571377&postcount=3274
[ONE Android Development] Whaaaaa:
[MENTION=1228651]fusionjack[/MENTION] [MENTION=3306843]kantjer[/MENTION] [MENTION=5284595]YoshiShaPow[/MENTION] Would it be possible to add soft reboot in the power menu ?

Thanks a lot.
[ONE Android Development] Promez:
As Fusionjack said some time ago the soft reboot can cause some problem
[ONE Android Development] Whaaaaa:
I was not aware of that. :(
[ONE Android Development] adinkwok:
I unlocked the remaining max freqs since the thermal driver is very strong. Max cpu was never able to be changed with the CAF kernel... until now. I have a new kernel build that allows the changing of the max freq. I will just be releasing the kernel but it will be implemented in the next SlimSaber CAF build I make :good:
[ONE Android Development] FloorFox:
Quoted from developer

"

Some people are writing that this patch "only" fix the battery radio active counter. I say that if you know java and take a look on the code you will note that the side effects of this bug includes, among others, not calling various NetworkManagementEvent observers that will have role in other modules of the inner core of Android, and not only the battery stats. So you say me what are the other side effect"
[ONE Android Development] just4u32:
/

Mine is just broken. Can't switch it on and detect devices... 29/8 as well
[ONE Android Development] dwaipayanray95:
Does your build have all the changes from SultanXda's build? Including the Oxygen OS camera mods? I'm planning to try a slimsaber rom!
[ONE Android Development] elargento:
Great job man, keep it up! I am on CM12.1, can i flash the Slimsaber CAF rom over the CM12.1?
[ONE Android Development] kalapapa:
Nope you'll have to wipe system data and cache
[ONE Android Development] elargento:
Thx, do i need to do a factory reset aswell?
[ONE Android Development] kalapapa:
Well that's pretty much a factory reset but doesn't wipe pictures and photos
[ONE Android Development] adinkwok:
Yes!
[ONE Android Development] chikimonke:
You are switching ROMs, you need to clear data too or you will have issues. Data is where all the rom settings are kept too. You can certainly try without wiping data, but don't expect any help here until you've done a clean flash.
[ONE Android Development] dwaipayanray95:
I just flashed your build! It is so fast! So smooth! So beautiful! Will report back soon!

EDIT: [MENTION=5284595]YoshiShaPow[/MENTION] does it support xposed? If yes which one? and where can I get it? Please point me in the right direction?
[ONE Android Development] elargento:
I don't know what happened, i did all the wipes the rom was flashed correctly and now i lost the imei.
[ONE Android Development] gugas123:
Lol, and I dirty flashed and is working perfectly ;)

If you lost imei and the nandroid don't work, you'll need to go fastboot
[ONE Android Development] adinkwok:
I do not know, but I'm sure others in the thread do. I don't use xposed
[ONE Android Development] Heisenberg:
Use the search to search for "Xposed" in this thread...
[ONE Android Development] abhibnl:
Then i'm afraid you are wrong. I personally tested and this bug does affect battery life. Kitkat is way more battery friendly on mobile data than lollipop. I'm a heavy mobile data user (90-95% of the time) and i know lollipop has made things worse for mobile data users. But it sure is smooth and a more up-to-date OS. I hope this introduced alleged fix, won't only fix the "statistical readings" but the battery drain as well.

Sent from OnePlus One
[ONE Android Development] CounterC:
Yes you can use xposed.

This one works for me: http://xdaforums.com/showpost.php?p=61620150&postcount=11249
[ONE Android Development] elargento:
I went back to cm12.1 got imei back.

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] gugas123:
Better then! And believe I'm glad for you! :D

Once my imei disappeared and the only way i was able to bring him back was by bootloading. It was a long night, and i did not went to sleep without having my phone again ;)

I know the feeling

The positive side, is that we learn how to solve it ;)
[ONE Android Development] Stylo King:
Then my friend you should know that on wifi too kitkat gave much better battery life, So it is not the fault of mobile data itself.

The bug itself is nothing more than just a counter, If you can observe that on kitkat too.. using WIFI all the time gave you 1-2 hours more SOT than lollipop,same goes for mobile data.

and if you keep mobile data on in sleep whether in kitkat or lollipop, it will result in idle drain.

The difference is that on lollipop it shows up in battery stats but on kitkat it doesn't,I agree it drains more on lollipop but that is not due to that radio active bug but because of lollipop itself.

I myself tested this and can confirm there is a very less effect of this mobile radio active thing in actual life.

Even my other testers have confirmed battery life is normal, Getting 5+ hours SOT with 3G and 8+ hours with wifi.. Now I am using SlimSaber CAF with latest beta and the results are outstanding.

Different people have different approaches, Hard to digest fact..
[ONE Android Development] FloorFox:
Then you should read the fact given by developer
[ONE Android Development] Stylo King:
and you should read what I posted twice if you didn't understand, I am satisfied with the battery life I am getting on mobile data and wifi considering the fact kitkat was better in terms of battery life than lollipop.

Still I am satisfied with lollipop thus far, You guys can carry on this discussion..

End of the story.

And yes The developer has done a nice job in resolving this bug,much appreciated.
[ONE Android Development] kanyazsombor:
Why is rebooting a pain?
[ONE Android Development] kantjer:
Share you building problems, I'm sure there is somebody here that can help you.