yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] acuicultor:
Hi folks, I'm trying to add splash image into a kernel but have problems to convert splash.raw to final.img(already converted from png to raw successfuly) I'm getting a file with 0 size and I'm stuck there, can someone help me out? Any help will be appreciated. Thanks

Sent from my Nuclear bacon
[ONE Original Android Development] ak:
I have posted a guide in the thread some time ago.

Sent from my A0001
[ONE Original Android Development] Nos_20:
Just tried Nenamark 2

Everything seems OK on my device.

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

ROM : SlimSaber Latest by Fusionjack

Kernel : ☆ AK ☆ Latest Beta by AK
[ONE Original Android Development] acuicultor:
I know but using search function don't get me to the guide. I'm looking for it all day but unable to find, just have the link to the commit you show me but stuck at step 2, I keep continue looking for the answer, thanks

Sent from my Nuclear bacon
[ONE Original Android Development] Pradhan_89:
Off topic. Found some very good ak walls: https://plus.google.com/u/0/101509247546633442048/posts/iy4Dwg6wBMF
[ONE Original Android Development] rolear8:
Hello, I'm using Slimsaber.. I would like to use the ak kernel which contains the screen firmware that fixed the ghost touch screen and slowness.. Could you please point me out which one I can download ?
[ONE Original Android Development] indian84:
The latest beta.. :) it's beta just for namesake..
[ONE Original Android Development] ethauvin:
I'm using the latest CM 12.1 nightly and CM gapps with AK 267 and I've noticed that when my OnePlus One hasn't been used for while, hitting the power button takes a few seconds to turn the screen on. Double tapping the screen seems to wake it up a bit faster, but maybe that's just me.

Same when receiving a phone call, it takes a couple rings for the display to light up.

Is that normal behaviour?

Thanks,

E.
[ONE Original Android Development] Lar5:
Running CM12.1 nightly (0621) + AK 267 earlier today, I had to force a reboot after receiving a call.

I wasn't able to pick up the call cause the screen didn't turn on. No response from any of the buttons or from opening the magnetic cover.

It just played the ring tone to the end. The capacitive buttons didn't turn on.

No kmsg... sorry.
[ONE Original Android Development] sambaeallegria:
CM12.1 (21/06) and AK 267beta... Beta???really???
[ONE Original Android Development] Stylo King:
This version is already declared stable by [MENTION=3475639]ak.[/MENTION] It was named beta for testing as it is based on the new linux version 3.4.108

Performance is butter smooth.
[ONE Original Android Development] sambaeallegria:
Yes I know. Mine was sarcasm. :)
[ONE Original Android Development] Spaulding89:
Sarcasm is my Best friend :)

Sent from my Hardcore Bacon
[ONE Original Android Development] maxver0:
I keep getting DCs even on stock settings.

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

It didn't fixed issue for me. I don't have WiFi issue on 14052015 cyanogen nightlies plus boeffla kernel beta17 with new touchscreen firmwares from 02062015 but the sources are before 0106 AFAIR.

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

This WiFi issue bugs me so much. Especially with mobile radio active bug still here.
[ONE Original Android Development] Formhault:
Mobile radio active bug? You mean the situation where mobile data consumes twice as much battery compared to Wi-Fi? Nah, that's normal :) axjalkfrkjagxgfxajgajfcascafasdzARATGSDTGasdafsdg

---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------

Someone please tell me this has ramifications and can fix the Wi-Fi dying with screen-off...
[ONE Original Android Development] ak:
These are old ROM problems ... Associated to a kernel with no aggressive attitude. Change governor to smartmax or tune interactive a bit. Check if your phone service is killed by aggressive lmk or greenify.

Inviato dal mio G620S-L01
[ONE Original Android Development] ak:
ROM problem.

Inviato dal mio G620S-L01
[ONE Original Android Development] ak:
If you have a solution from another dev point me to necessary commits For fix the Wi-Fi issue. Thanks.

Inviato dal mio G620S-L01
[ONE Original Android Development] Jikul:
I really like the interactive governor, but hate that the screen takes so much time to turn on. Sometimes I almost miss calls. What setting should I change to fix this?
[ONE Original Android Development] newellj79:
I switched from interactive to slim becuz of the same problem. Couldn't be happier. Battery and performance are great.
[ONE Original Android Development] obtained:
Ondemand resolved that issue for me.
[ONE Original Android Development] MurdererFight:
Last V.247 i very very smooth on BrokenOS! Good Job!
[ONE Original Android Development] maxver0:
I don't have solution from other dev. I made my own conclusions. Lastest known configuration is 25 05 2015. So now, looking at this: http://review.cyanogenmod.org/#/q/status:merged+WiFi

One new commit was pushed to the build 27 05 2015. Which is this, http://review.cyanogenmod.org/#/c/99264/

Another one was pushed at 07 06 2015 http://review.cyanogenmod.org/#/c/99588/

Now comments got my attention.

Also this commit, pushed at 27 05 2015, wasn't merged with stable cm12.1: http://review.cyanogenmod.org/#/q/5b37e609c44ea78125c77df27fd03ffd2f585c4c,n,z

[MENTION=3685904]ak[/MENTION] Can you revert these commits back to the last known good, before 27.05. I can test it.
[ONE Original Android Development] ethauvin:
Thanks. That did fix it.
[ONE Original Android Development] obtained:
Wouldn't those be ROM specific? I don't see anything referring to kernel_oneplus_msm8974?
[ONE Original Android Development] flyaway718:
Can someone yell me what can I do about audiomic?
[ONE Original Android Development] Hussainally:
I had some weird drain yesterday after updating to the latest beta version.. Phone was constantly awake... I am so sorry I did not investigate further on why and reverted back to v 265 and drain is gone.. Love this kernel so much with 6+ hours sot with mixmash v9 profile
[ONE Original Android Development] chikimonke:
[MENTION=3685904]ak[/MENTION] So I've been testing for a while now, and no matter what I do, I'm having the same GPU issues others are reporting. Spend all my time at 200 or 578 depending on the Gaming Boost. I've tried to play with the Simple GPU stuff, but nothing seems to make it better. My phone also slows way down for periods of time, turning the screen off and back on after a second seems to fix that temporarily. Usually it's when I'm trying to use SlimPie that it seems to lock up, I'm guessing this is GPU related in trying to draw the overlay? Anyway, would it be possible to try the current kernel with the gaming boost stuff reverted? Thanks.
[ONE Original Android Development] rolear8:
I have jumped finally from 5.0.1 to 5.1.1.. I have tested AK kernel 251 NEW TC and also AK 265 OLD TC and my phone still feels slow when typing ... And while scrolling sometimes Click on something instead of keep scrolling .. This issue was fixed on the lastest Slimsaber 5.0.1 with the screen frimeware.. Any ideas ?

Edit: reflashed cm firmware solve the issue, and reflaahed again lastest beta
[ONE Original Android Development] ak:
Because the behavior is the same, GPU govenor is not changed. before the freq most used was 330MHz and now 200MHz, the way how it scale it not changed. why dont you try to lift the minimum?

do you have lag on gaming or scrolling?
[ONE Original Android Development] ak:
rom related, not kernel.
[ONE Original Android Development] bender_8:
If the wifi bugs are rom related too, which current rom would you guys recommend? Got too many problems with euphoria.
[ONE Original Android Development] maxver0:
That's strange. Because when I m on 14.05 which is way before this commit and I flash lastest custom kernel, I get the issue.

Can I just copy this file(before commit 27.05) over to the rom via recovery file manager or adb? Will it work?

---------- Post added at 08:15 AM ---------- Previous post was at 08:15 AM ----------

Resurrection remix
[ONE Original Android Development] ManuBBXX:
I seek for an alternative to Eu^horia too.

Resurrection is better than Euphoria or SlimSaber for you ?

I like slimsaber, but no theme chooser :(
[ONE Original Android Development] maxver0:
Yes it is way better than Slimsaber. Haven't tried Euphoria tho. Resurrection Remix has slim features as well, so you will find your settings :)
[ONE Original Android Development] 1337jay:
You should definitely try Exodus! ;) v.267 BETAv1 working like a charm here ak, thanks!
[ONE Original Android Development] bombadier:
No themes but uses layers and that opens a whole world of possibilities
[ONE Original Android Development] vraciu4you:
Stock cm12s....no wi fi disconnects...ever :)
[ONE Original Android Development] nosphor:
Hi everyone,

Is the latest ak kernel compatible with the Slimsaber Rom ?
[ONE Original Android Development] Formhault:
No Wi-Fi dropouts?!

---------- Post added at 11:53 AM ---------- Previous post was at 11:53 AM ----------

I'm on CM12.1 nightlies and I do get Wi-Fi dropouts. I don't see any Wi-Fi driver-related commits since CM12S so... umm... or are there... :confused: :(
[ONE Original Android Development] indian84:
Yes it is.. A little bit of reading would have helped you.
[ONE Original Android Development] ak:
do you use custom theme?
[ONE Original Android Development] Formhault:
Since I last transitioned back to CM12.1 nightlies (a few days ago), no, I've been using the stock theme.

Besides, COME ON, how can a freaking theme interfere with... :eek: :eek: :eek: :(
[ONE Original Android Development] nosphor:
I always prefer asking to someone just to be sure.

In any case, thanks for your answers :)
[ONE Original Android Development] JaylanPHNX:
Why use 251? Why not 265? (If there's an old tc version, wouldn't that mean the standard one has the new tc?)

From my SlimTab Pro 8.4
[ONE Original Android Development] 1337jay:
I still get occasional WiFi disconnects while in deep sleep, using latest Exodus rom. But no other problems whatsoever.
[ONE Original Android Development] Formhault:
So... 1~5 minutes after screen off. Nay, no yay :(

---------- Post added at 01:21 PM ---------- Previous post was at 12:52 PM ----------

When a new build comes out...
[ONE Original Android Development] foomanjackel:
^^ thats great Formhault ^^ So true...lol, love it!! :laugh:
[ONE Original Android Development] FunkyRasta:
I second that ! GPU is far too much conservative , scrolling is jerky because of that. Games are good because they put much load on GPU and it scales well. UI is not as demanding and GPU is at 200 MHz making it laggy. Enabling simple algorith just makes it stick to 200 MHz even in games.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] DrkLrd:
Nice battery

With new AK 267 (beta) + Arch Power Enabled + Temasek's CM 12.1 ROM by katinatez = 7+ hours of screen and 20% battery left (so it's about 8 hours of screen juice).

Thanks for the efforts AK!
[ONE Original Android Development] bender_8:
No wifi problem with temasek?
[ONE Original Android Development] nuwan32:
nope im using temasek v14 and v267beta and no problems at all.
[ONE Original Android Development] gargeya_369:
I don't have any problem scrolling.....
[ONE Original Android Development] FunkyRasta:
Perhaps you weren't using nexus device before then , I'm just spoiled by constant 60 fps correctly frame paced animations [emoji14] I see every little bit of judder.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] Formhault:
So... No Wi-Fi dropouts?! What drivers are these cookers using :confused:
[ONE Original Android Development] gargeya_369:
Did u try any profiles like Demonpheonix and Styloking's profiles...?
[ONE Original Android Development] FunkyRasta:
Nah mate, when even four cores on with smartmax don't solve this, it must purely GPU gov fault :) Don't get me wrong, it isn't that bad , just few frames dropped here and there.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] gargeya_369:
Then you need a nexus may be.....
[ONE Original Android Development] FunkyRasta:
Totally happy with my OPO, in nearly every way better it's better than my nexus 5. And using AK battery life is outstanding.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] Formhault:
Y'all so-happy-about-this-awesome-battery-life people ever disconnect from Wi-Fi? :)
[ONE Original Android Development] Pipodi93:
[MENTION=3685904]ak[/MENTION] Can you get the Intelliactive governor in the next release? I think it would be great! :D
[ONE Original Android Development] venky716:
I've the same issue.

It has to do with WiFi router.

It is specific to certain routers, mine is D-link.

It happens only with CM based kernels, occurs on all my devices running CM based ROMs.

No wakelocks with stock ROMs, tested on Moto G, Xperia Z.

Have reported the issue on jira , with no response.

Would be greatful if AK could do something about it, the only other option is to change my router.

[MENTION=4462636]nadavar[/MENTION] try this, disable multicast from your router settings and see if it reduces the event wakelocks.

Source
[ONE Original Android Development] nadavar:
@ak, yes, tried softkeys without success. hardware keys I meant the capacitative.

Now I tried disabling network notification, and I'll see if it helps.

[MENTION=4252252]venky716[/MENTION] thanks for your post.

I actually saw that link, but multicast was disabled on my router. I have d-link as well.

I also set DHCP to give static ip to my OPO.

I'll let you know if anything helps. in the short time the phone was sitting idle it seems a little better, but too soon to tell.

BTW, I'm on Mahdi which is based on AOSP... maybe because of all the CM commits...
[ONE Original Android Development] ak:
I have see the same wakelocks but it seems related to audio mix ... But its difficult to derivate ... Do you have see the same problem with b 04?

ak@a0001
[ONE Original Android Development] venky716:
Sorry bro I've tried everything possible, all combinations of wifi settings. Nothing worked. So now I've decided to change my router :crying:

I'm sure this is solely related to WiFi. I have no 'event' wakelocks when on data.

Is there something you need, kmsg, catlog etc ?

Anything at all I'm ready to provide, pls try to resolve this problem, my battery drains 2-3% per hour when on wifi.

So should I postpone my router purchase ? :fingers-crossed:
[ONE Original Android Development] ak:
This is your choice my friend ... I'm not engineering ... So I can't promises any resolution for the problem ... But I can see if there is a possible fix for reduced wakelocks.

ak@a0001
[ONE Original Android Development] timothydonohue:
i can tell you that since upgrading from 25R, my phone was dropping wifi at my work apartment (yes, i have a work apartment, because i live two hours from work), on the POS standard verizon router. i would go to sleep with wifi connected, wake up, and it would be disconnected.

at home, i actually haven't used the wifi i used to have, because i upgraded from 25R to 33R while at work residence. and, i just upgraded my home router. but, no home wifi automatic shutoffs. however, i'm not sure it would have dropped anyway. i did not upgrade my home router for this reason. i did it because i had money burning a hole in my pocket, and i thought a brand new home theater sound system was a bit of overkill, lol.

in short, i think my drops were due to crappy intermittent connection on my work residence. if your connection is crappy, i'd call the company and have them work on your 'last mile' connection. there should be methods to evaluate your router drops.

---------- Post added at 04:32 PM ---------- Previous post was at 03:51 PM ----------

i've noticed a lot of comments about faux sound in this thread recently...

is that really so much better than the sound fx we get on 11s? i am actually quite happy with the way sound fx tunes my sounds. is faux sound that much better? i know it is a little off topic, but i also know ak has been working hard at getting it in, and i'm just wondering why...
[ONE Original Android Development] RobbieL811:
[MENTION=3685904]ak[/MENTION] I could use a little help here. I have built your kernel from my current source, and straight from your nightly branch both, and I am still not seeing the new settings in Synapse. Is it something that I need to enable before building?
[ONE Original Android Development] lowrider82:
I have these files in init.d.. Should I delete any?

Sent from my OnePlus One
[ONE Original Android Development] chachin:
um I dont know if it's been asked before. but if updating from ak035-b04 do i have to wipe anything in order to update to b08? and should I wait for paranoid to update to 4.5b5 or if they decide to update to something new then that.. or stay on 4.5b3 :P
[ONE Original Android Development] solrac.dc:
Generally what I do is wipe cache and dalvik cache when updating nightlies. Also there is no need to wait for a PA update. Hope this answers your Q.
[ONE Original Android Development] chachin:
oh well i can always wait and see what pa will offer on 4.5b5 hehe im on b4 and i hope we get ak35 very soon and ak36b001 brings gpu oc :3
[ONE Original Android Development] chikimonke:
There's no reason to wipe anything when upgrading kernels.
[ONE Original Android Development] RobbieL811:
REALLY, there's no reason to wipe anything ever when updating anything. Did that make sense? Lol.

Sent from my 1+1
[ONE Original Android Development] chikimonke:
Eh, I find a manual system wipe has served me well when flashing ROMs, I seem to have fewer issues dirty flashing than those that just straight dirty flash.
[ONE Original Android Development] solrac.dc:
Seems like everyone has thier own methods. I have always found to have no problems when wiping. Again that's just me :)
[ONE Original Android Development] ak:
You can delete 00ak, for ukm you can use uninstaller.
[ONE Original Android Development] RobbieL811:
Yeah. That's true. I forgot about that. I normally do that also.

Sent from my 1+1
[ONE Original Android Development] mcbyte_it:
multitouch

I started using nightly b08 since only yesterday afternoon and it was ok.

I woke up this morning, and I had no multitouch, all the device was ok, wifi, etc, but when doing multitouch it started acting strange: YAMTT tester showed than when more than 1 finger is touching the display it started getting mad. FYI: my device never suffered ghost touches or anything, this is the 1st time it happens.

I rebooted and it seems to have solved the issue.

anybody else got this?
[ONE Original Android Development] RobbieL811:
Pretty sure that there are lots of users out there right now with multi touch issues. I'm sure it's being worked on.
[ONE Original Android Development] DrkLrd:
Nope, never. Try Temasek's UNOFFICIAL by katinatez, you also won't have ant disconnects.
[ONE Original Android Development] kantjer:
Don't think it's ROM or kernel related. I see posts on the SlimSaber thread from users getting WiFi disconnects. I never had them using the same ROM/kernel
[ONE Original Android Development] ak:
this isnt a fault, can you try to raise min freq of gpu? you have the same effect to old style.
[ONE Original Android Development] FunkyRasta:
Yes I can and it solves that but is not optimal solution because of battery drain, because here GPU doesn't idle at 27 MHz. Another governor like interactive or simple would solve it better. Or idling at 27.

In anyway I'm not complaining, just sharing my ideas, and appreciate your work :)

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] abhi08638:
It does idle at 27mhz no matter what min freq you have set. I have it set to 330 and I can still reach 27
[ONE Original Android Development] FunkyRasta:
Oh, that would change a lot. But for me both Synapse and Kernel Adiutor show GPU idle at 200, no sign of 27 MHz.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] abhi08638:
You have to use the live reading, since 27 is not a setable step, it won't have any stats
[ONE Original Android Development] FunkyRasta:
Tried it and you are right !! I'm surprised because on other Snapdragon devices Synapse showed 27MHz even if it was not a step. Thank you very much. But I still think less conservative gov is a way to go if it could be an option.

Edit: MAGIC, after using CPU-Z synapse started showing 27MHz o.O

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Original Android Development] xlollomanx:
Strange, I don't have any problem with reading GPU clock with Synapse. If this is what you are talking about. I'm using official cm nightly (build 22/06/2015) and ak v.267
[ONE Original Android Development] kalpik:
For what it's worth, bumping the minimum GPU frequency to 330mhz made a hell lot of a difference in UI smoothness.

Sent from my A0001
[ONE Original Android Development] hermit911:
"AK kernel updater no more in Play Store"

its broken, its there any other resource i know its on github , then how to install ?
[ONE Original Android Development] DemonPhoenix:
AK i feel that the changes u made to the GPU was a good thing but it had its drawbacks that the threshold on the 200MHZ for it to go higher is too high. When it needs to go 330MHz it doesn't which is quite bad as it doesn't allow for smoothness.

When u tested this with Adreno ilder, battery life was the same as adding this but was the smoothness the same? asking cause curious. This is mainly because if Adreno idler gives the same battery life as the current 200Mhz commit u did but allows for better smoothness and better scaling wouldn't it mean better for Idler to be in?
[ONE Original Android Development] sneakerspark:
Set the min freq to 330 and you'll be good to go.
[ONE Original Android Development] expiredd:
After seeing this posts I'm thinking of going back to CM11S or SlimKat 9 if I can flash AK kernel. Is the last update also working for you guys?

I will need to flash in the following order:

- Wipe Cache/Dalvik/Date

- Flash 44S firmware/Modem

- Flash Stock44S CM11S

- Flash new CM12.1 firmware (may 15th)

- Flash AK kernel

- Flash [MENTION=3306843]kantjer[/MENTION] UKM_v3.8.3.3.1_Special_Ed.zip
[ONE Original Android Development] bombadier:
[MENTION=3685904]ak[/MENTION] Got a wee problem with drivedroid When I try to mount the image the phone reboots, posted in the thread and the developer suggested there was a bug in the kernel

Can reproduce the error and pulled these logs

dmesg

last_kmsg I had this working when I was still on CM11S and your 239 kernel, happy to provide anything else I can thanks
[ONE Original Android Development] ak:
I do not know the application.

the patch is correctly merged.

because he knows that it is a bug can you ask how to solve it?

thanks a lot.

ps

this user have the same problem with stock slimsaber kernel:

http://xdaforums.com/showpost.php?p=58106947&postcount=99

so are you sure the app is compatible with lollipop?
[ONE Original Android Development] bombadier:
Hopefully the developer gets back to me with how to fix and will let you know,cheers
[ONE Original Android Development] ak:
thanks a lot for logs, i'm checking if i can found a fix ...
[ONE Original Android Development] kantjer:
[MENTION=3685904]ak[/MENTION] I'm having a the problem that a few setting are lost when doing a reboot and also a profile restore doesn't set them back.

Settings I loose are:

Enabling:

power-efficient workqueues

software CRC control

simple Governor Tunables

Arch power

All other settings are kept during a reboot and also restored with a profile restore.

I already removed all profile backups and made a new one to be sure the settings are inlcuded.

Ant tips how to solve this (running the beta kernel atm)