yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] adinkwok:
I think that comes after installing the driver... Try using SuperSU and rebooting the phone!
[ONE Android Development] johnb380:
You need Super Su for V4a to work built in Su won't work for some reason.
[ONE Android Development] Zeus20:
https://www.androidfilehost.com/?fid=24052804347798113

Is the link the caf 8-20 build on the afh mirror
[ONE Android Development] inffy:
Damn I miss the caf build. Hopefully we start to get custom roms for OP2 not so distant future.

Still need the kernel sources to be released
[ONE Android Development] adinkwok:
If any of you guys have spare invites available... ;)
[ONE Android Development] inffy:
Not yet but I will propably get some soon. Will definately spread them to devs ;)
[ONE Android Development] kalapapa:
[MENTION=947981]Lord Boeffla[/MENTION]is trying to get op2 kernel source but is having trouble with oneplus team
[ONE Android Development] andip71:
Yes, they are - as always - very slow and reluctant.

Maybe it helps when we push the thread altogehter...

https://forums.oneplus.net/threads/kernel-source.343335/

Andi
[ONE Android Development] inffy:
Well he needs to be patient with it. They don't need to release them straight away.
[ONE Android Development] andip71:
Well, don't want to get too much off topic, but I have a slightly different view.

They are shipping an official product, with a Linux kernel included that is covered by GPL. So they are obliged to release the sources, in my understanding latest when they ship a commercial product (which they do with OxygenOs).

Unfortunately violations to that are not followed up, so we have to wait and hope.

Andi
[ONE Android Development] inffy:
Yeah I know

But Oneplus is not the only one who takes their time with these, just look at Xiaomi

But yeah I really hope they release them soon. Will keep asking about them.
[ONE Android Development] union1mc:
Anyone else getting stuck in a bootloop with Boeffla beta20 kernel? Tried twice now (re-downloaded it) but still getting bootloop. First time I've ever had issues with it. Running SlimSaber 8/16 build
[ONE Android Development] Hetalk:
You cannot directly flash boeffla's kernel on slim builds. Wait for the builds by [MENTION=4876554]Mrwargod[/MENTION]
[ONE Android Development] adinkwok:
Let's do this :cool::cowboy:
[ONE Android Development] union1mc:
It is Mrwargods version
[ONE Android Development] Setting.Out:
Also if you've flashed another kernel, you'll need to return to "stock", the kernel original to the rom, before flashing the "slim" version to avoid issues..
[ONE Android Development] union1mc:
Even coming from beta 19? I only use this kernel and have never had to do this
[ONE Android Development] kantjer:
Double post
[ONE Android Development] kantjer:
I flashed beta20 on top of beta19 yesterday without any issues.

#whiteuimustdie
[ONE Android Development] union1mc:
Was this with your latest build? Maybe I will download and try it.
[ONE Android Development] kantjer:
Yes, running my latest ROM build with my beta20 Boeffla build.

#whiteuimustdie
[ONE Android Development] union1mc:
And is this Mrwargods Boeffla build? I thought I saw a while back that you made your own build to play nice with your SlimSaber build.
[ONE Android Development] kantjer:
Like I mentioned I'm using my own kernel build. Everything is uploaded to my AFH

#whiteuimustdie
[ONE Android Development] Genericxx:
Using 20150819 Version of CAF Build sind two days (one full charge cycle). Appreciate that builds and they are working flawlessly for me. Got slightly better battery life with CAF, but this might also be placebo, coz i've renounced to install facebook shiet this time which is also a battery hog. Got 4h 20m SOT with playing Ingress at last charge cycle which is very impressive, while using smartmax_eps. Only things i customize for battery life is disabling analytics services through MyAndroidTools and dimming the Screen Brightness. So nothing special at all. Curious about Camera. Really seems like the modified Oxygen Libraries do their job way better than the cm ones. At least they are much faster. Quality wise i doubt big differences as the pictures taken seem very similar to me.
[ONE Android Development] Mrwargod:
Weird, it is booting fine for me. :-/

If you wish to try, i upload my builds into my AFH for safekeeping reasons, so you can try to DL last night build and try beta20 with it.

There should be no problem dirty flashing it on top of official build.
[ONE Android Development] BrandoHD:
Is anyone having issues with the max cpu frequency on the latest CAF (20th) build?

Edit: scratch that, I think it was the thermal throttling....maybe
[ONE Android Development] union1mc:
[MENTION=3306843]kantjer[/MENTION] working great with your rom and kernel build. Thank you. [MENTION=4876554]Mrwargod[/MENTION] I'll try with your build and see if it works. Like I stated earlier, it's weird, I've never had issues with it before.
[ONE Android Development] ~KV:
To all CAF users,

How many of you all are getting better battery life (SOT) than the stock SlimSaber?

I found idle drain rate higher on CAF....do share your stats..:)
[ONE Android Development] imam.krismanto:
How big storage i need to download and build source of slim? i newbie :D
[ONE Android Development] kantjer:
The ROM source itself is about 30GB, you need about 100-150 GB disk space for the source an build the ROM
[ONE Android Development] kantjer:
There is an issue with my today's build, it reboots when making a call.

I removed it from AFH.
[ONE Android Development] kantjer:
A little off topic is allowed here :D

We need to keep it light and have fun
[ONE Android Development] netcitizen:
Slightly off topic - has anyone got next word prediction working in AOSP keyboard?. It works fine on Google keyboard. But I miss the alternate keys though.
[ONE Android Development] iPusak Gaoq™:
[MENTION=3306843]kantjer[/MENTION] : i'm planning to try your rom (coming from fusionjack rom) and dirty flash on top of fusionjack build work right?

also did you somehow add the toggles in settings on your rom?
[ONE Android Development] kalapapa:
It works fine but sometimes on certain texts like website addresses in chrome it won't pop up. What you can try is go to settings>language and input>android keyboard AOSP and change the settings so it will be more agressive
[ONE Android Development] kantjer:
See post #2

#whiteuimustdie
[ONE Android Development] joefso:
5.5 - 6 hours of SOT, same as on CM12.1 basicly. Difference is that this feels smoother.
[ONE Android Development] adinkwok:
From my settings (stock with smartmax_eps instead), I get 4.5-6 sot hours depending on how much music I've listened to that day. On an average usage, its closer to 4.5-5.5. That is because the idle drain is more present, but the usage drain is better while the screen is on.
[ONE Android Development] KenjiHannya:
With TYR Kernel and my config. With Render Kernel does not give much difference.
[ONE Android Development] adinkwok:
I don't know how you guys get such crazy SOT!! I can't even get past 7 hours! Could you explain in detail your config? (firmware version, screen brightness, kernel settings, 2g/3g/4g/lte, Greenify or wakelock blocker, daily usage, etc.) I am really curious as to how some people get such crazy battery life!

---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------

Also, I am making a new build with more sched changes to the kernel that will boost the calculations :good:.
[ONE Android Development] HamsterHam:
[MENTION=3306843]kantjer[/MENTION] - I'm still getting lockscreen lag, hmm. I've not changed any kernel settings (using your boeffla build v20). I'm confused as to what is causing it. Any ideas? Few builds ago I never had this issue.
[ONE Android Development] pgarza:
Lol I can't get passed 4 hrs sot
[ONE Android Development] TemplesOfSyrinx:
I did a clean install of the 21st build with boeffla v20 and experienced the reboots when making a call. Reflashed using stock kernel and everything is fine now.
[ONE Android Development] adinkwok:
New build with latest SlimSaber changes as well as some optimized scheduler commits. You can look at my kernel source to see the specifics. Remember that you need SuperSU in order for V4A to work!

SuperSU

SlimSaber-CAF-bacon-5.1.1-20150821.zip
[ONE Android Development] mammenj:
Just flashed the caf, getting a weird pictures while playing Webem..

Attached
[ONE Android Development] netcitizen:
oh is it. it never worked for me. i have to type a character and only then some words are predicted never got the contextual prediction working similar to google kb or swiftkey. changing it to " aggressive " mode also didnt help.
[ONE Android Development] ~KV:
Well, I average on about 9-11 hours of SOT....but that's on stock SlimSaber...with stock kernel and smartmax_eps:D

I would get the same on CAF if idle drain wasn't high...

This is kind of ironical because with CPU Hotplugging (Min. cores online is set to 1, whereas on stock SlimSaber it's 2) and max CPU freq fixed at 1958MHz...battery life should actually be better!
[ONE Android Development] netcitizen:
7 hours damn.. normally get 4.5 hours only. what kernel and settings do you recommend ?
[ONE Android Development] ~KV:
May I ask what your idle drain rate is?......it seems you don't let your phone rest from your graph:p
[ONE Android Development] David:
how did you do that ?:eek:
[ONE Android Development] mammenj:
Looks like a Google photo issue but this issue was not there in prior caf version.
[ONE Android Development] renaltosonylevi:
OK post some screen shots or it never happened.:o

If I use my phone as a tablet I can get about 8 hours but I did not purchase this phone to spend it's days on WiFi or hobbled for battery saving.

Having said that I would appreciate any tips on killing these @#$#$&$* wake locks that plague android 5.1:mad:
[ONE Android Development] adinkwok:
I just tried it out and it's working fine for me... Are you sure it's not just a messed up webm?
[ONE Android Development] mammenj:
No because it works fine on bsplayer not on photos.
[ONE Android Development] kantjer:
Thanks, so Boeffla's kernel is causing the reboot on the last Rom build.

If that's the case I expect lots of reports if [MENTION=1228651]fusionjack[/MENTION] released his build today.

#whiteuimustdie
[ONE Android Development] kantjer:
Try to disable ambient display

#whiteuimustdie
[ONE Android Development] HamsterHam:
It's off already. Really strange but I think it started happening when weather lockscreen was implemented. My just be coincidence though. I may try stock kernel and see if it happens.
[ONE Android Development] just4u32:
What Tyr version works for you? (and on what SS build?)
[ONE Android Development] astrall:
[MENTION=5284595]YoshiShaPow[/MENTION]

Bug report on latest CAF build, 08/21

Having random reboots while playing Spotify.

Stock kernel on Smartmax_eps. Attached are the logs after the second random reboot.
[ONE Android Development] kantjer:
I have been experimenting with today's build and Boeffla's kernel. But even with today's SlimSaber ramdisk and adding the latest CM kernel commits added to the kernel the ROM keeps giving a system settings FC at boot and reboots when making a call. Stock kernel is working fine. For now I'm back to stock kernel.

#whiteuimustdie
[ONE Android Development] HamsterHam:
Is this build on afh? So far stock kernel has fixed my laggy lockscreen.
[ONE Android Development] kantjer:
No I wanted to test it first. I will upload when I'm back home.

#whiteuimustdie
[ONE Android Development] cmoG530:
How did you change your font?
[ONE Android Development] Hetalk:
I use iFont app from play store and works fine.
[ONE Android Development] HamsterHam:
Cheers. Scrap my thoughts, stock kernel still laggy. Hopefully new build somehow will stop it.
[ONE Android Development] kantjer:
wasn't expecting the kernel to fix that. still strange I never experienced the issue.

FYI, I don't use the stock smart unlock.
[ONE Android Development] HamsterHam:
Yeah, really odd. Might just be placebo but it hasn't happened since. I don't use smart unlock at all.

If I do what app do you use?
[ONE Android Development] kantjer:
New build is up

#whiteuimustdie
[ONE Android Development] Natakranta:
Up and running. I left stock karnel this time. So far no screen wake / lock screen lag. Let's see.

Thanks!

#whiteuimustdie
[ONE Android Development] KenjiHannya:
screen brightness - auto

kernel settings - smartmax, min 300, max 1267 ~ 1574 (no lag), bosst frequency disable for 4 CPU, CPU governo my config, Hotplug all change, CPU volt -75, I/O 1024 tripndroid or row, RQ Affinity agressive, GPU 462 max, Memory all change and Render Kernel with UKM Render.

And good ROM ??

---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------

v11 ?

---------- Post added at 10:19 PM ---------- Previous post was at 10:15 PM ----------

Ah

Just Greenify, 4g and wi fi
[ONE Android Development] dead0:
a newbie question: does this file: recovery-from-boot.p make any difference? so no issues caused if removed from the rom prior to install?
[ONE Android Development] kalapapa:
Just out of curiosity why do you want to remove it
[ONE Android Development] assassin0408:
Anyone here using xmod in latest slim build?i dont want to download the rom yet to save my quota.i need to know first whether xmod is functional in latest slim build. Someone please tell me because xmod is really important app for me
[ONE Android Development] rogi19:
Is it just enough to install the snapdragon.apk to get the snapdragon camera working on kantjers builds?
[ONE Android Development] fusionjack:
i also never experience screen unlock lag issue.

i'm using google's smart unlock, ambient display disabled, prevent wake accidental disabled and weather lockscreen enabled.
[ONE Android Development] netcitizen:
double tap to wake aint working properly. have to go the gesture setting disable and enable to get this going again. But after a while it stops working again. I am on the latest CAF build.
[ONE Android Development] bombadier:
https://forums.oneplus.net/threads/snapdragon-camera-v2.335704/

You need the libs as well

Instructions included
[ONE Android Development] fusionjack:
[MENTION=3306843]kantjer[/MENTION], [MENTION=4876554]Mrwargod[/MENTION], since you are using or building boeffla kernel, i want to mention that since integration of cm sdk, the content of init.environ.rc has changed. the system server path has now additional entry for org.cyanogenmod.platform.jar

this is now needed so that live display thing works.

i'm not sure if this file belongs to ramdisk thing. you might to check that.
[ONE Android Development] kantjer:
I checked org.cyanogenmod.platform.jar is included in the ramdisk. I have made a Boeffla build with the latest SlimSaber ramdisk (it includes the org.cyanogenmod.platform.jar SYSTEMSERVERCLASSPATH) but still I have a reboot when making a call.
[ONE Android Development] imam.krismanto:
[MENTION=3306843]kantjer[/MENTION] i think, i got new bug of your slimsaber. i can't remove contact permanent from speed dial of dialer. that is always back after remove. can you fix that? thank you for your amazing rom.
[ONE Android Development] kantjer:
I just tested it and adding or removing a contact from speed dial (favourites) is working fine for me.
[ONE Android Development] fusionjack:
connect your phone with pc, start logcat with 'adb logcat -C' and make a call. you should see something in terminal while soft-reboot.

you can copy paste the relevant lines or just forward the logcat output to file: adb logcat > logcat.txt

i'm curious what was happened. call is fine on stock kernel.
[ONE Android Development] adinkwok:
Known bug, will be fixed when the tree developer pushes his fix :)
[ONE Android Development] netcitizen:
oh ok. thanks.
[ONE Android Development] Mrwargod:
That's awkward, i never had any reboots wile doing calls.

I've built mine the 21st night.

I'm doing a new build right now and try to see if that bug pops out.
[ONE Android Development] kantjer:
Made a new build with the ramdisk from today's build and Boeffla's kernel is working again. Made a call and no reboot. I made a build 2 day's ago with an updated ramdisk but I think I then accidentally flashed the wrong kernel build [emoji33]

beta 20.1 (updated the version number so you won't make the same mistake I did) in my afh and is working with the latest SlimSaber release.

It's the same as beta 20 only using the updated ramdisk and Update defconfig to bring it inline with CM's commits.

#whiteuimustdie
[ONE Android Development] imam.krismanto:
yes it working fine for 1-10 minutes (uncertainty ), but if we back to speed dial for next time the contact that we removed is back.
[ONE Android Development] Poesini:
Trying to build CAF SS with Xposed art (romracer's one), got this:

{standard input}: Assembler messages:
{standard input}:248: Warning: partial line at end of file ignored
arm-eabi-gcc: internal compiler error: Segmentation fault (program cc1)
0x40c1e4 execute
../.././../gcc/gcc-UBER/gcc/gcc.c:2856
Please submit a full bug report,
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/mauricio/SlimSaber5.1/kernel/oneplus/msm8974'
build/core/tasks/kernel.mk:227: recipe for target 'TARGET_KERNEL_BINARIES' failed
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....

Seems a GCC error (I have applied this commit https://github.com/SlimSaber/android_art/commit/5d91c9e129fc7e44fbfec6b59f1443105bf14bd1 ) , maybe I am missing anything else [MENTION=1228651]fusionjack[/MENTION] ?
[ONE Android Development] kanyazsombor:
And what about cmera HAL? Does it need the modified camera HAL from sultanxda?
[ONE Android Development] bombadier:
Dont know about that,someone with more knowledge will need to help you, not sure if his improvements are in the rom or part of the camera
[ONE Android Development] fusionjack:
something is wrong with your kernel setup
[ONE Android Development] Poesini:
Its weird because with normal art it does compile...
[ONE Android Development] martinoff:
[MENTION=3306843]kantjer[/MENTION] can you share the commits for v4a please, do I have to remove the audiofx from local manifest and replace it with v4a repo?
[ONE Android Development] kantjer:
Everything is in my github, but I will post an easier way to add v4a tomorrow. I'm off to bed now.

#whiteuimustdie
[ONE Android Development] dead0:
an old windows habit lol I like to slim down with only the essentials included in the rom. does that patch file do anything?
[ONE Android Development] fusionjack:
that defconfig is not for our device.
[ONE Android Development] fusionjack:
normal art is slimsaber art?

which repos did you replace beside art? have you removed toolchain? the error should have something to do with kernel.
[ONE Android Development] kanyazsombor:
Slim down a slim rom, wow
[ONE Android Development] kantjer:
To remove Audio_FX and add the v4a source add this to your local_manifest

<remove-project name="CyanogenMod/android_packages_apps_AudioFX" />
<project path="packages/apps/ViPER4Android" name="vipersaudio/viper4android_fx" remote="github" revision="master" />

You can manually cherry-pick the commits (but you will have to do that after every repo sync) or fork the repo's and add them there and use those, but then you will need to keep the repo's updated.

I suggest to use "repo start", see this post by [MENTION=1228651]fusionjack[/MENTION]

If you go that route the commits will be added after every repo sync.

I have the script attached I used to add the v4a commits using "repo start"
[ONE Android Development] martinoff:
I'm already using repo start thanks to master [MENTION=1228651]fusionjack[/MENTION] so I will go with that for sure

I saw you have forked v4a repo, have you changed something?
[ONE Android Development] kantjer:
I changed the permissions of /system/etc/addon.d/91-v4a.sh to 0755

https://github.com/kantjer/viper4android_fx/commit/2951b7fbb604f1241f79d270e6bddaf82410c388
[ONE Android Development] just4u32:
Was anyone able to run the latest CAF build with the latest (or any) Tyr kernel? For me it won't boot.

Will greatly appreciate it if someone can respond.
[ONE Android Development] kantjer:
[MENTION=4876554]Mrwargod[/MENTION] you might want to add this commit to your Boeffla build.

See the discussion with [MENTION=947981]Lord Boeffla[/MENTION] starting here
[ONE Android Development] Mrwargod:
Thanks. But first i have to fix my rom's build. It's failing everytime, i guess i may be missing a commit in there to make it build but i didn't had time to look further into it over the weekend. :-/
[ONE Android Development] mrmcshagbag:
I currently have slim saber 5.1.1 installed. Today i tried to install twrp 2.8.6.0 with twrp 2.8.7.0 and it failed now i cant access a recovery at all. I fastboot flashed twrp 2.8.6.0 200 times all ready and still cant access a recovery at all. Im getting very mad at how this damn thing isnt flashing. it says it flashed but cant get into twrp at all. Need help flashing twrp since the correct way of doing it via fastboot actually doesnt do sh**. Thanks for any help. and yes fastboot and adb work all commands work it just wont boot into the recovery after flashing. I tried with flashify and it also didnt work.
[ONE Android Development] rkuijpers:
You might have better luck with "fastboot boot recovery.img" instead of "fastboot flash recovery recovery.img".

That way you'll temporarily boot into recovery. When in there, flash recovery by zip file. Should work after that!

Verstuurd vanaf mijn XT1039 met Tapatalk
[ONE Android Development] fusionjack:
you are not using ubuntu right? it should be issue caused by linux distribution.
[ONE Android Development] Mrwargod:
Nope, i'm on Manjaro linux.

What package may be causing it?
[ONE Android Development] johnb380:
I recently saw someone else with your exact same issue and the solution was only to flash CWM Phil's recovery and that solved the issue. Other than that idk what else you can do. You really don't wanna mess with recovery to much it can leave your phone a brick.

Good luck friend.
[ONE Android Development] imam.krismanto:
Waiting for new slimsaber build with latest [MENTION=4800121]Sultanxda[/MENTION] caf kernel.
[ONE Android Development] KenjiHannya:
Me too ?
[ONE Android Development] adinkwok:
Well wait no longer because I just made a fresh build! This includes ALL the latest changes including the removal of smartmax as a governor. That being said, I did not remove smartmax_eps because I haven't had any random reboots with it so far.

SlimSaber-CAF-bacon-5.1.1-20150824.zip
[ONE Android Development] nadiros:
Does DT2W work on these new CAF builds?

Just curious. I've recently switched from AOSPAL to Kantjers Slim builds and am really enjoying Slim. I figured I might just jump on this CAF train.

This thread has such a positive energy too. Thanks guys [emoji106] [emoji6]
[ONE Android Development] KenjiHannya:
Not removed? Thank you. Only Smartmax use.

One person said that is using Kernel AK ROM CAF. Can be used?
[ONE Android Development] KenjiHannya:
AK Kernel with CAF ROM?
[ONE Android Development] adinkwok:
:o another BCian? Yes it works but every 1/40 times it doesn't work

---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------

I don't see anything about ak kernerl with CAF there >.>
[ONE Android Development] BIG-bone:
Does your build include Sultans snapdragon camera?
[ONE Android Development] skeetzor:
Yes
[ONE Android Development] BIG-bone:
Yes, flashing right away

Sent from my B V C O N
[ONE Android Development] adinkwok:
It has his SnapdragonCamera with CameraNextMod removed.
[ONE Android Development] BIG-bone:
Awesome, already downloaded bout to flash this thx

Sent from my B V C O N
[ONE Android Development] Zeus20:
The mirror of the latest CAF build is up.

https://www.androidfilehost.com/?fid=24052804347800735
[ONE Android Development] mrmcshagbag:
cannot load 'recovery' : no such file or directory

Thats what it says to that command