yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] molonad:
If you Dont know how to help and you only post nonsenses you should not post at all. He is not rude and he is asking for help and you acted like chump.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] robbieast:
So is this kernel no longer CAF? Doesn't seem to work for slimsaber 5.1.1 CAF which has been discontinued since november
[ONE Android Development] Gobbenobber:
Yeah it should be CAF but I've read in this thread that other people experience v27 to be the last one working on L 5.x.x builds :)
[ONE Android Development] xjampong:
Wifi wont turn on on OmniROM. Weird.
[ONE Android Development] NickosD:
Yeah. Weird. Using a caf kernel on omni. Weird.

Sent from my bacon!!!!!
[ONE Android Development] xjampong:
Haha. I'm sorry. Just read that it wont support OMNI anymore. LOL.
[ONE Android Development] PlusOne3k:
Aha :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] Velkn:
LP

Sent from my bacon
[ONE Android Development] v1ks:
Thankss...trying this profile with Darkobas rom. so far 2h28m SOT with 57% left. WIFI always on, location (batt saving), brightness 30%...

will see how it goes....
[ONE Android Development] MrVoshel:
Is now this kernel stable by switching clock speed?

I really want to reinstall this kernel on my device because of customization and speed :)
[ONE Android Development] w0rinal:
i clean flashed darkobas feb23-0 and v34r and it just wouldn't boot, so i checked tombstones and it said "error creating /data/dalvik-cache/arm: no such file or directory", then i created the folder(s) and it said "error changing owner: permission denied" or something similar. after some time of googleing i figured it might be due to init.rc which seems to be created from boot.img. then i restored the boot partition from a working backup and the devices booted up fine. looking at the about section in android settings it says it's lightningkernel v32 now.

v33 didn't work well for me either. if anyone is facing similar issues (bootloop) try downgrading. no idea why that's happening

---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------

you mean if it's stable when underclocking/undervolting? this rather depends on ROM/device or even binning (good/mediocre/bad quality hardware parts)

but overall this kernel is quite solid :)
[ONE Android Development] Nicolas_g134:
[MENTION=3573347]v1ks[/MENTION] Thanks for the profile, I am using it right now, is it possible that in the hotplug section there is none selected of the possibilities? :)
[ONE Android Development] nikhil18:
Let the ROM boot with stock kernel then reboot and flash my kernel
[ONE Android Development] w0rinal:
I think the Governor will take care of this if you don't use a dedicated Hotplug Driver. pegasusq is said to be a "multi-core aware governor" so I'm sure it'll work anyway. The worst case would be no hotplugging so every core would be always online.

Thanks, I'll try that.

BTW is init.rc called only once or on every boot?
[ONE Android Development] Ruvy:
Settings sticking on Synapse after reboot ? Came a long way to reach here after v33 almost fried my phone. :D Willing to try it again.
[ONE Android Development] dude6595:
That wouldn't work for me... Always have to flash v32 boot then flash 33 or 34
[ONE Android Development] rituj_b:
The phone is having trouble sleeping. Orion OS 2.2

View attachment 3657880
[ONE Android Development] molonad:
Hello nikhil can you please look into this? Maybe you overlooked it. Thank you

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] nikhil18:
How can the phone not sleeping be a kernel problem check your wakelocks please

How many times I have told you not to undervolt while testing different because you have reported this to me before bro the nightmare governor is from ak kernel untouched so it can't give reboots
[ONE Android Development] molonad:
I wasnt undervolted

Odesláno z mého A0001 pomocí Tapatalk

---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------

If Yes i would not post this here. But if was iam sorry for my mistake.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] nikhil18:
Then what is this did the phone modifiy its self to cool it self down
[ONE Android Development] molonad:
Oh okay, iam sorry. I was undervolted - random reboot, then i use normal voltage and random reboot - so maybe i didnt change voltage exactly to stock value. Sorry, iam going to try again without undervolt(i Dont even touch it).

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] Nicolas_g134:
Thank you, however for me smartmax eps is selected with this profile , is that right? :)
[ONE Android Development] joro666:
Hello,

work wake option Circle2Camera with this kernel? I'm on Darkobas ROM.
[ONE Android Development] easy_mac:
Working fine here on sultan's latest build
[ONE Android Development] return.of.octobot:
I can appreciate the KA related development, but I've just never been able to wrap my head around why some find it to be more appealing than Synapse, which offers a higher level of control in many aspects. Is it because you need to reload Synapse profiles on reboot w/ MM, is it just a design preference?
[ONE Android Development] nikhil18:
Synapse onboot settings has been fixed in the recent updates
[ONE Android Development] w0rinal:
I don't use the profile but it doesn't depend on it anyway

Switch to the CPU tab and look at the graph. Smartmax eps doesn't scale up fast so there should be only one core online if there isn't anything going on in the background.

One core means the governor supports hotplugging - otherwise all cores would be online.

Now scroll up and down, pull down the status bar, that causes the CPU to start working and eventually you can see the second core go online. That means the governor is aware of the other cores.
[ONE Android Development] Holymartyr:
Having a problem with Synapse and the latest kernel. Moved the new Styloking profile into the normal Synapse profiles folder, and Synapse didn't find it even after several Synapse Restarts/Data Clears. Tried rebooting the phone as well. Tried re-installing synapse. Tried deleting the Synapse folder using TWRP. Now Synapse won't re-create the folders.

Advice?

(Using Sultans latest CAF build)

P.S. Also just updated SuperSU to the latest version, and verified Synapse has SU privilege.
[ONE Android Development] DarKAngel1234:
Enable Super SU at boot, in Super Su settings. Also give storage permission s to synapse.
[ONE Android Development] Holymartyr:
Already enabled SuperSU at boot, but don't know what you mean by storage permissions.
[ONE Android Development] kalapapa:
Hold the app icon and go to app info. There go to permissions and allow storage
[ONE Android Development] Holymartyr:
Um. The only option I have under Privacy guard is "Auto Start". Nothing about allow storage. It does show the app can "modify or delete the contents of your usb storage/read the contents of your usb storage" under App Info.

Edit: If I try setting a random config name in synapse, and export it, I get this error (image): http://imgur.com/B45pYz9
[ONE Android Development] molonad:
Hello so now i get random reboot with darknes with stock uv, stock virtual memory settings

Here logs - https://www.dropbox.com/s/kzel4go6cg23ewc/logs darkness.zip?dl=0

Thanx for help.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] Holymartyr:
Tried V33 of the kernel with no success. Will try to set the synapse profile manually for now using Stylokings screenshots, but hoping for a solution eventually.
[ONE Android Development] return.of.octobot:
Has anyone had any success with getting v34r, or v33 for that matter, to boot? I've tried the aforementioned reflash ROM w/ stock, reboot, and then flash Lightning. Bootloop.

v32 is the last build working as expected, for me anyway. I've also tried flashing v32, and then v34r on top of it. No luck there either. Any suggestions?
[ONE Android Development] dude6595:
did you flash 32 and then booted up and then reboot to recovery and flashed v34 without clearing caches?
[ONE Android Development] Holymartyr:
Both V33 and V34 have booted for me AFTER first booting stock kernel. My only issue appears to be the synapse bug I mentioned earlier.
[ONE Android Development] nikhil18:
Bro try flashing version 32 see if synapse works then flash the latest version
[ONE Android Development] daltonhrrll:
Think I'll make a profile for this
[ONE Android Development] lordsinasina:
Hi Guys, Been using Sultan's MM build for a while now with stock kernel. I am just wondering in comparison what would be the benefits of this kernel ( End user perspective ) since I am hearing a lot about it.
[ONE Android Development] nikhil18:
Have you ever used ak kernel before if yes then the benefits will mostly will be the same if not then you can ask other users because I can't comment about my kernel based on my useage for an honest review
[ONE Android Development] lordsinasina:
yes but back in CM11 days. The thing is I don't have any issue with Sultan's Stock but I am also up for better experience and more feature.

---------- Post added at 05:48 AM ---------- Previous post was at 05:46 AM ----------

Well I can see you've done a great job since lot of users are talking about and using your Kernel so I trust you with any explanation :)
[ONE Android Development] Holymartyr:
Is it just me or does your downloads section skip v32? I only see v34/33/31...
[ONE Android Development] nikhil18:
Oops sorry download 31
[ONE Android Development] Cissiboy:
i can boot with 34r on temasek/sultan caf by vivek_neel

synapse creates its folders just nice

i downloaded the profile from TheAwesomeRay (it's a .tgz file)

placed it into

/synapse/Saved_profiles

went into Synapse and restarted it, then restored the profile (which synapse sees)

but all i get is a

Invalid file

I downloaded the file 3 times already so i doubt it's a corrupted download
[ONE Android Development] phanipk:
hi guys

can i flash this Lightning Kernel im on cm-13 20160222 nightly with stock kernel.

can any one tell me the procedure how to flash this.
[ONE Android Development] nikhil18:
There is another thread in original android dev section you can download the latest version 16r

Can you open the .tgz file in es file explorer
[ONE Android Development] Holymartyr:
Running v31 now, synapse created the right folders, but still does not see Stylokings profile. Phone is also running quite hot now, obviously it's not ramping down frequency. Will try flashing v34 over v31 to see if there's any difference.
[ONE Android Development] nikhil18:
Bro do a clean flash or wipe your internal storage or go back to cm11s because this a very rare problem
[ONE Android Development] Holymartyr:
v27 Of your kernel was working just fine...that was the last version of your kernel I used before doing this update to v34 and Sultans rom.

I can't spend the time doing a full wipe/clean install currently. Guess I have to go back to the v27 backup. If I get time to do a full wipe in the future I'll let you know. I'm sorry I can no longer update my phone. =(
[ONE Android Development] molonad:
Hello nikhil. Iam sorry, but i didn't really change voltage or virtual memory and still i get random reboot with darknes. Maybe it is my faulth in settings. But I changed minimum. Please can you look at it? Thank you much

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] nitrobg:
The same thing happened to me. Follow these steps and it will/should work:

1) Select the profile

2) Press Apply

3) Press Restore Selected Profile. Synapse will restart.

4) Press Cancel
[ONE Android Development] joefso:
quick question, does the installer script also clean up previous kernel stuff?
[ONE Android Development] gicifix:
Got r34 working on Sultan's rom 20160221

Hello everybody,

I flashed lightning kernel yesterday, later at night and it didn't seem to work with Sultan's rom.

I then decided to keep the original sultan's kernel.

Today, I tried to give another try flashing this one and it worked, these are the steps I followed:

1) Wipe data-cache

2) Install Sultan's rom (I flashed the latest 20160221 build)

3) Install Gapps

4) Boot into stock rom.

5) Reboot to recovery

6) Flash lightning kernel (WITHOUT wiping)

7) Reboot to system

8) Wait about 3-4 minutes (don't know why, but first boot took some time to me)

9) Enjoy

I hope these steps will work for everybody!
[ONE Android Development] nikhil18:
No you need to dirtyflash the ROM to avoid problems

My battery life with styloking profile
[ONE Android Development] cossali98:
Hey mates which is the best build to use with darkobas ?
[ONE Android Development] joefso:
Man i need to look for that script AK wrote... it removed all the previous kernel stuff. Though not sure if it was for nexus 4 or bacon
[ONE Android Development] Holymartyr:
So I did more playing. I'm not 100% certain, but it sure seems that the latest SuperSU (UPDATE-SuperSU-v2.65-20151226141550) is the culprit. I restored my working v27 Kernel backup that was working, then installed ONLY Sultans latest Rom. It booted just fine. I then installed only your v34 Kernel, and it didn't boot. So I then installed your v31 Kernel and it booted. I checked Synapse and it was working, I was able to load the Styloking profile. I then tried installed the SuperSU update, and I was stuck at the boot logo for about 20m before I had to hard restart it. I restored my working backup again. I then installed the latest Sultan Rom, and your v31 Kernel. Worked fine. Then I installed your v34 Kernel and both the system and Synapse are working fine.

TL/DR: SuperSU (UPDATE-SuperSU-v2.65-20151226141550) appears to either interfere with your kernel, or Synapse or both.
[ONE Android Development] return.of.octobot:
That is an interesting theory, and one that I've considered also. However, my investigation went in reverse order. I'd started by trying to get 34r to boot w/ v2.52 installed, tried all the previously suggested orders of operation, various clean flash ROM, boot with stock kernel, then flash v34r (sometimes flashing v31/32 in between as an intermediary, like some have recommended), no luck. I then attempted the same after upgrading to v2.67 and.. unfortunately I've still yet to make it boot.

As of now, v32 is the last build I can flash per usual without issue. The only thing I haven't tried are the aforementioned steps without wiping dalvik/cache in between. If that turns out be what works, I'm going sh*t.
[ONE Android Development] joefso:
thank you for the info w0rinal

Attention darkobas users!

This will get V34 working for you. I tested it using darkobas-bacon-20160225-1.zip

- so you flash darkobas, gapps and supersu (optional)

- you flash v31

- wipe cache/davlik

- reboot

setup device & reboot into recovery

- flash V34 and reboot.

Done!

proof is in attacfhment.
[ONE Android Development] return.of.octobot:
For the love of christ, the secret was in fact to flash v34r after booting w/ stock kernel without wiping caches in between. I feel like such an idiot, well, I've never had to do such a thing to make a kernel boot so not that big of an idiot. Still, just glad I know now... back to work on DARKSiDER.
[ONE Android Development] easy_mac:
Dirty flash is so easy
[ONE Android Development] joefso:
Tried this, after reading the ops sugesstion on g+, it did not work.

Love your work.

---------- Post added at 07:31 AM ---------- Previous post was at 07:12 AM ----------

I see what you mean but it sucks to do that when you have been modding the system. Found AK his twrp script, needs some modding before it could be used...
[ONE Android Development] Holymartyr:
Iirc, that is also what I ended up doing. Not clearing the cache in-between seems to be the secret.
[ONE Android Development] easy_mac:
True, all my system mods are through flashable zips so I just keep them in a folder with my rom to reapply them easily.
[ONE Android Development] aswinrulez:
with jgcaap's 24th feb build, camera wont work if i flash this kernel
[ONE Android Development] nikhil18:
Bro there is another thread in original android dev section flash that this is only for ROMs which have sultans camera HAL
[ONE Android Development] aswinrulez:
The non CAF one?
[ONE Android Development] nikhil18:
Both are CAF but that has cm camera drivers
[ONE Android Development] Holymartyr:
Think I've found a bug: if you go to Synapse and turn KCal inverted colors on, the whole screen goes white. In older builds, this feature worked as intended. Be careful if you enable this, as you won't be able to see your screen to disable it. I had to go into TWRP and delete the Synapse APP folder to prevent the profile from loading. (Don't know if there was an easier way, but that was the first method that came to mind)
[ONE Android Development] nikhil18:
That's actually stock cm kernel bug
[ONE Android Development] dkv2222:
Holy crap. ROM?
[ONE Android Development] nikhil18:
dirtyunicorn
[ONE Android Development] dkv2222:
Please please please share your settings.
[ONE Android Development] nikhil18:
i said no it was styloking profile with -85 undervolt
[ONE Android Development] Stylo King:
Announcement

- If you want a Stylo King profile for Kernel Adiutor, Smash the thanks button..

I am thinking of working on a profile as I am getting a lot of requests for KA profile..

So lets Vote!
[ONE Android Development] molonad:
I Dont really know if you are you still looking into my logs. I just want to assure you that I changed minimum, no undervolt, no overclock, no change in virtual memory (swapiness untoched too)..

Maybe it will not make any change. But now i get next random reboot with tweaking msm hotplug

Here logs - https://www.dropbox.com/s/zgdv6czs8q9tz8j/msmhotplug random reboot.zip?dl=0

Btw. Iam using logs from kernel adiutor, so I dont know if is all ok with them.

Thanx for help

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] kalapapa:
Just out of curiosity does anybody else have CPU settings not saving in singularity kernel adiutor. Every time I reboot my phone, the CPU settings, even though I have apply on boot turn on, never save and always reset. Everything else does save but only the CPU doesn't save.

Anybody else? I think I saw someone else having the same problem and just saving the CPU settings in stock kernel adiutor. Is there anyway to make singularity kernel adiutor work.
[ONE Android Development] nikhil18:
You can try increasing the delay for settings to be applied on boot
[ONE Android Development] DerRomtester:
Taking logs from kernel adiutor is absolutly fine.

btw nice crash

1726.009894] Unable to handle kernel NULL pointer dereference at virtual address 00000038

[ 1726.009983] pgd = c0004000

[ 1726.010027] [00000038] *pgd=00000000

[ 1726.010151] Internal error: Oops: 5 [#1] PREEMPT SMP ARM

[ 1726.010197] Modules linked in:

[ 1726.010283] CPU: 0 Not tainted (3.4.110-lightning-kernel-v34-gaca09a5-dirty #2)

[ 1726.010374] PC is at ion_unmap_iommu+0x78/0x2d0

[ 1726.010420] LR is at ion_unmap_iommu+0x6c/0x2d0

[ 1726.010499] pc : [] lr : [] psr: 20000013

[ 1726.010499] sp : de715e40 ip : 00000000 fp : de69fcc0

[ 1726.010578] r10: edb548dc r9 : c01024dc r8 : 00000005

[ 1726.010622] r7 : c1614080 r6 : d7d99ac0 r5 : 00000000 r4 : 00000020

[ 1726.010701] r3 : e7cdbac0 r2 : 00000001 r1 : 00000000 r0 : c1614080

[ 1726.010746] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel

[ 1726.010825] Control: 10c5787d Table: 0280006a DAC: 00000015
[ONE Android Development] molonad:
Thank you for looking to my logs.did you look to my both logs? Iam sorry but i dont know what does it mean. I wish i know what i see. ?

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] nikhil18:
Why are you the only person getting reboots with my kernel I have been using it on my device from day 1 and its rock stable if you don't know what kernel settings your messing then don't mess with just use a profile and be happy or else use another kernel
[ONE Android Development] molonad:
I Dont know. Iam tweaking with hotplugs and governors, thats all(so i know what iam tweaking). That random reboot was caused by tweaking msm hotplug (so i know exactly what settings caused it). People Dont have reboots becouse they Dont try kernel deeply like me (try all governors all hotplugs and tweaking them). Do you know why it was caused with darknes(log before this log and without uv and other tweaks which was Causing reboots)?

Also i notice that with wheatley iam getting reboots(try yourself use it for a while)..

Ok you are looking upset to me becouse of random reboots which i caused. I think it should not behave like this if i only tweak msm hotplug..

Odesláno z mého A0001 pomocí Tapatalk

---------- Post added at 11:47 AM ---------- Previous post was at 11:43 AM ----------

Also iam happy with your kernel, but i always will have some reboots becouse of tweaking. And iam posting you logs only when that reboot happened when i know it should not reboot.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] dwaipayanray95:
All Day Battery -v2- extreme

- Changed Hotplug to AutoSMP (Better Hotplug)

- Completely and heavily changed the voltage tuning till 1574 MHz and partially till 1978Mhz for those who might increase the frequency

- Better Battery life as the CPU is supplied with very less mv

- Under the hood a few changes

http://goo.gl/Wtr85c

(Next version I'll incorporate [MENTION=5683095]styloking[/MENTION] 's changes as well)

EDIT: AVOID DOWNLOADING THIS, WOULD WORK IF WE SHARE SIMILAR PVS BINS. HOLD ON UNTIL I MAKE A TUTORIAL...OR ELSE TRY IT OUT, ITLL WORK IF YOU ARE LUCKY!
[ONE Android Development] dead0:
heres my stats with darkobas build 02/16-4 and lightning v32 :) no reboots whatsoever, set for both performance and battery. also only with mobile data always on, no wifi so reckon I could probably get more juice out of it if using wifi

https://plus.google.com/106836350679352605950/posts/Q6cABJ523bR

found v34r to be a bit more battery hungry, v32 hits the sweet spot ;) I have modded the kernel slightly by adding init.d support along with a few customer settings
[ONE Android Development] return.of.octobot:
So, just a few questions, comments after using 34r for a few days. No major showstoppers or critical issues, just some properties or lack thereof that've thrown a bit of a monkey wrench into my approach.

I read about the apparent thermal issues that some encountered with a previous build, is this the reason why the ability to set thermal parameters has disappeared in 34r? I'll attach a screenshot for reference of what it was, versus what it is now i.e. only being able to set the temp threshold. Just my thoughts on the matter, but I certainly appreciated the ability to set the thermal step and freq limits. Honestly, if users are unable to comprehend these settings and use them properly then whatever problems may arise are their own fault. I'm not sure that it really warrants a reduction in functionality and at the very least would recommend the reinclusion of Sultan's simple thermal driver for those of us that would like to set our own thermal limits.

My other pseudo-gripe is the missing/new parameters for the alucard hotplug. I imagine this is an upstream change from alucard himself, but I am particularly missing the ability to set the minimum core limit.
[ONE Android Development] prstorero:
Unfortunately, after I applied your new profile earlier, my phone rebooted about 5 seconds later, I'm guessing due to the lower voltage. So for now I reverted back to V1 ??
[ONE Android Development] dwaipayanray95:
Yes do that....somehow this didn't happen to me... Before the reboot was your phone frozen...or randomly it rebooted?
[ONE Android Development] pamposmouskos:
Frozen and the rebooted. Later synapse was a black screen with one error
[ONE Android Development] NickosD:
Just increase the voltage.

Sent from my bacon!!!!!
[ONE Android Development] prstorero:
It froze up before the reboot. In my other post, the two question marks were supposed to be a Smiley face, not sure why that happened.

---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------

I attempted to after applying it, but it would freeze before I could do so.