yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Targaeryan:
No issues here although I'm running with dalvik. Please paste logs so anarkia can help you. :) did you check the WiFi advanced options to make sure WiFi is always on? And disable WiFi optimization?
[Nexus 4 Original Android Development] :
You may use Trickster Mod.
[Nexus 4 Original Android Development] llevo3:
yes, wifi is always on and I have never disable wifi optimization
[Nexus 4 Original Android Development] Targaeryan:
WiFi optimization throttles WiFi speeds in my exp. Anyway you should paste logs so its easier to figure out the issue. Maybe you can try running dalvik for a while and see if the issue is there..
[Nexus 4 Original Android Development] ak:
What modem?

Ak kk inside ;)
[Nexus 4 Original Android Development] ak:
You have to post last kmsg ... Logcat is for ROM trouble.

Ak kk inside ;)
[Nexus 4 Original Android Development] ak:
Change your ROM.

Ak kk inside ;)
[Nexus 4 Original Android Development] llevo3:
If you ask for my baseband, it is 84
[Nexus 4 Original Android Development] Targaeryan:
You should try the hybrid radios. They are really good. I'm using the .33-.84 hybrid.
[Nexus 4 Original Android Development] ak:
Have you see also disconnections with old kernel (v106)?
[Nexus 4 Original Android Development] :
[MENTION=3685904]anarkia1976[/MENTION]… I set the minimum number of cores at two with hispeed freq at 1350MHz, N5 Kitkat Port v4, my phone runs as smooth as when it was it 4.3. I'm amazed! Any projection how will affect battery life?

---------- Post added at 12:30 AM ---------- Previous post was at 12:29 AM ----------
[Nexus 4 Original Android Development] eluspo:
Any feedback on the new kernel?
[Nexus 4 Original Android Development] Targaeryan:
Gets better every release! ;)

---------- Post added at 12:06 AM ---------- Previous post was at 12:02 AM ----------

Hahaha I'm using it with gnome's build and its smooth and great battery life.. I'm on 3 hours SOT with 48% remaining.
[Nexus 4 Original Android Development] eluspo:
Which one is ak 111 kk?
[Nexus 4 Original Android Development] Targaeryan:
http://xdaforums.com/devdb/project/dl/?id=1607
[Nexus 4 Original Android Development] poondog:
I am forced to use 487 max gpu also on am kernel, but I don't care. I don't game much on my flo. Regardless the battery lasts long enough :)
[Nexus 4 Original Android Development] bart.found:
This sounds great! For me would be enough the possibility to set 400 MHz also in an overclocked 487 MHz kernel! ;)

Obviously I'd use this kernel despite of the gpu frequency.. kernel is a choice.. and every choice is a compromise.. I tried other kernels in the past, then found this one! :D
[Nexus 4 Original Android Development] gorilla p:
Yeah 400 seems to be the optimal/most efficient setting.

While some like the 487 overclock, I doubt the majority care about it.

I also believe that a lot of those that do like the 487 overclock option, don't want it to completely replace the 400mhz freq

Just my $.02

Sent via Mental Telepathy
[Nexus 4 Original Android Development] Italico:
Hope normal means 1.7GHz max, so with a tiny bit of overclock ;)

Great kernel BTW
[Nexus 4 Original Android Development] TheXorg:
When creating AnTuTu Benchmark, I'm getting something like Red Light Of Death.

Steps to reproduce:

1. Start AnTuTu

2. Wait some time

3. Screen turning black, device is unresponsive

4. Connected to PC

5. LED blinking red

6. Disconnected / Connected to PC

7. Battery charging symbol appears

8. If trying to turn on, Google logo appears, then LED red for ~2 secs, then everything off again [same with boot to bootloader]

9. Battery charging symbol appears

10. Waiting some time (~15 mins), Android boots and turns off again because battery empty (mine had 77%)

11. Turning on again, everything works again

ROM: latest Barebones (based on LiquidSmooth) (Android 4.4.4 | LINK)

Prev. Kernel: Stock Barebones (=LiquidSmooth)

Kernel: AK335 CM

Kernel Settings: nothing changed

Version of kernel settings: latest Synapse (0.39)

edit: booting again, battery seems to be super-uncalibrated (before RLOD 77%, after 1%)
[Nexus 4 Original Android Development] Italico:
Hey AK, may I ask about 'sampling rate' and 'ignore nice load' values of ondemand governor? Are they changed in the latest 335 kernel version?

Mine are respectively 10000 and 0, but if I remember well they were 50000 and 1 before...

Thanks!

EDIT: I find myself very satisfied with the speed of 1.9GHz OC @ 1225mV. So, now... I'm undecided about supporting OC or not :-/

Before I would have said 'no', but now... scrolling, app switching... everything is smooth, and the phone flies! ;)

I will test battery life in the next days.

Tried Wheatley, conservative intelliplug and conservative GPU governor, ROW also; but now I'm again on ondemand for both CPU and GPU, balanced intelliplug and FIOPS.

It's a razor! :)

PS: as soon as possible I will donate to you, AK. Maybe a beer or a coffee, that's what I can do as a student, but you deserve this and a lot more!
[Nexus 4 Original Android Development] Gallardo994:
Normal IS 1.7ghz, our board is supposed to run 1.7 max according to Qualcomm (check wikipedia table), and ours is underclocked by default to 1.5ghz.
[Nexus 4 Original Android Development] Italico:
Exactly ;)
[Nexus 4 Original Android Development] T-luvR:
It happens for me too thats because of too high cpu

If I helped thank T-luvR
[Nexus 4 Original Android Development] Italico:
Happened something similar to me in a certain way, yesterday, with blinking red LED for a couple of seconds and big battery percentage jumps.

I think it was because of too much UV and multiple consecutive reboots, high frequency and wall charging at the same time.

Today with 25000mV less UV it runs great at 1,9GHz.

Maybe I should calibrate the battery, but it seems not bad for now.
[Nexus 4 Original Android Development] T-luvR:
That happens whaen using with high freq and cpu is under pressure it happens for me while oc my pc!! Today u arent using your phone as heqvy as yesterday that happens when cpu device cant feed cpu and it makes a contact in voltages and so the battery drains very fast i recommend not to use at that clock that can end your battery as it did mine once three monces ago

If I helped thank T-luvR
[Nexus 4 Original Android Development] Italico:
You think?

Because today with 75mV of UV it is totally stable and not hot at all... Normal average temperature on the back...

And both Synapse and the hidden settings menu says that the battery condition is good, as it is its temperature too.

BTW, yesterday the charger was an 1.8A one from Amazon Kindle, not the original 1.2A... so maybe it heated more...

Thanks for your words! [emoji6]
[Nexus 4 Original Android Development] T-luvR:
But it has happend for me twice without charger :D ok tbat wqs what happens on pc and once happend for my phone :D maybe I couldnt tell my word because ofy bad english :D

If I helped thank T-luvR
[Nexus 4 Original Android Development] Italico:
No problem, I understood [emoji6]

I thought it was all right if temperatures stay low and voltage is low too... I have a faster binned CPU so it supports OC in a very good way... What was your binning, instead?

I've seen that wheatley uses the top frequency more that ondemand, too...
[Nexus 4 Original Android Development] ak:
This is an old question, and this is the motivation because i reverted overclock.
[Nexus 4 Original Android Development] TheXorg:
I haven't overclocked. It's only when i usw AnTuTu, even when i overclock to 1.9GHz and all cores are idle, nothing happenes. Idk why...
[Nexus 4 Original Android Development] ak:
Because you can, with antutu and overclock, reach the max temperature and your phone shutdown automatically. RED is related to this. :good:
[Nexus 4 Original Android Development] shadeMe:
The battery life extender limit doesn't work when the phone is connected to through USB (as oppose to AC power). Is this a bug or intended? I don't have USB OTG or fast charge enabled.
[Nexus 4 Original Android Development] montbazon:
I'm using 1.9ghz with conservatived intellplug.

There is no heat issue and filled with smooth!
[Nexus 4 Original Android Development] pincher65:
not correctly to look only on the table of opportunities of the processor because at different devices cooling and power supply of the processor is differently realized. for dispersal it is necessary to improve the cooling system, it is the alphabet of an overclockers
[Nexus 4 Original Android Development] leather.face:
Hello ak and all members :) ... [MENTION=3685904]ak[/MENTION], thanks for your great kernel here but I have two questions:

1/ When I come from a previous version of the ak kernel, I must after the flash process every time wipe the dalvik and cache partition? Or is that not necessary with this kernel?!

2/ You write in your OP post, flash stock kernel of your rom but this is not necessary when I come from a previous ak kernel, or I have to flash with every kernel update the stock boot.img?! I`m not sure :confused: ...

[MENTION=3685904]ak[/MENTION] have many thanks for your help and I`m very happy with your kernel, keep it up the good work here!!! :good: :cowboy:

Best regards

leather.face :)
[Nexus 4 Original Android Development] arffrhn:
Hi there,

1. No need to wipe anything for kernel flashing.

2. No need to flash stock if you are just updating the kernel. But you might wanna clear cache and data of synapse and also init.d scripts related to the kernel before updating. This is optional of course (not a necessity). :)
[Nexus 4 Original Android Development] T-luvR:
Hey there i get a really overheated device while oc but no reboot is it cause of binning 0?! I mean it gets around 67-68! Battery 45

If I helped thank T-luvR

---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------

Our cpu is clocked at 1.5 default check official Qualcomm or the wiki ;) for more info

If I helped thank T-luvR
[Nexus 4 Original Android Development] stavca:
I had kernel panic on v335
[Nexus 4 Original Android Development] leather.face:
Hi :) ... Oh have many thanks for your help and yes I understand all ... I`m very happy with this kernel, thanks again to ak and I wish a nice Sunday ... See you soon ...

Regards

leather.face :)
[Nexus 4 Original Android Development] jtwebfusion:
GPU governor

Not sure if it's just me, but when I choose a GPU governor other than ondemand in trickster, it goes back to ondemand. Anyone else seen this before? I'm on the latest version of CM and V.335.CM.
[Nexus 4 Original Android Development] Rembi:
AK,You mentioned that "normal" version will be without liability. Please leave OC functions -; 487mhz works quietly as 400mhz (900/900/900) and 1944mhz gives a clear kick N4, the screen do more than 5h.

Wysłane z Nexus 4 za pomocą Tapatalk.
[Nexus 4 Original Android Development] gorilla p:
I may be wrong, but I don't believe trickster recognizes conservative GPU governor.

I also sincerely recommend using UKM/Synapse for kernel management to take advantage of all features

Sent via Mental Telepathy
[Nexus 4 Original Android Development] shadeMe:
I've had the kernel panic and reboot on waking up my device, once on v330 and the other on v335. I've got a Faster binned CPU undervolted by -100mV and C0, C2, C3 sleep states enabled.

It seems to be a recent development though, never had this issue in the pre v330 builds.
[Nexus 4 Original Android Development] HTCTOUCHPRO91:
AK 335 @ 1.7 GHz 4 cores on GPU @ 487 on top of Rastakat stock UI by [MENTION=4770534]snak3ater[/MENTION] + z2 bionic + june graphics drivers... On ART runtime [emoji16] impressive thank you [MENTION=3685904]ak[/MENTION] [emoji7]
[Nexus 4 Original Android Development] marcus6999:
Has happened to me too, but I can't turn it on! I followed all your steps but phone keeps turning the red light blinking.

Any solution or way to turn it on?
[Nexus 4 Original Android Development] TheXorg:
Wait some time till its cooler (put it in the fridge for 5mins) then plug in the original charger and wait some time. Sometime it works again. Say if doesn't.
[Nexus 4 Original Android Development] marcus6999:
Still not working, the phone won't boot, still stucks in the Google logo and turns off to the red led blinking.
[Nexus 4 Original Android Development] Gallardo994:
Turn it off for a night, then connect it to the charger at the morning and let it charge for several hours. Then try booting. If you can boot to recovery, try flashing the kernel anew or wiping the data (backup first!)
[Nexus 4 Original Android Development] ak:
I had the same problem a month ago, you have to attach your phone off into AC charger for some hours. :good:
[Nexus 4 Original Android Development] Sp_Ark:
I think either you need to buy another battery or you should try to charge the battery with a striped usb cable. If someone you know has a n4 as well you can charge your battery at his phone. It will charge for sure. Have fixed 4 n4 devices with such problems this way.

BTW have you tried power + vol down and then just start? Most probably you have, but had to ask...
[Nexus 4 Original Android Development] marcus6999:
I will try leaving the phone connected tonight but I had it connected to the original AC charger for 3 hours and it still had the red led blinking and won't run :(

If the option mentioned above doesn't work I will try yours tomorrow.

Ufff this solution is a little bit drastic, but as if the other posted solutions doesn't work, i will have to try it!

And yes, I have tryied every combination of the hard-keys I could do and none of them worked. Even any combination and connecting to the AC charger doesn't seem to work :(
[Nexus 4 Original Android Development] ak:
Do you have the battery animation? if yes ... when charged ... off the phone from charger ... volume down + reset button ... go to recovert wipe dalvik and cache ... reboot ...

if it doesn't boot you have to reflash your rom. :good:
[Nexus 4 Original Android Development] marcus6999:
I've managed now to enter to the recovery and did a full wipe and reflashed rom, still not working :(

And the worst thing is that when it happened, it was at 55% of battery, strange thing.
[Nexus 4 Original Android Development] Gallardo994:
Keep it in recovery and connect it to the charger, then leave it for about 5 hours. Try to boot after that.
[Nexus 4 Original Android Development] marcus6999:
Left it tonight as I thought the same as you, it still doesn't work. Today i'll try to leave it disconnected from charger. Maybe by discharging the battery and after leaving it charging it will work.
[Nexus 4 Original Android Development] johnb380:
Did u try a clean flash of factory stock image?
[Nexus 4 Original Android Development] Gallardo994:
Be aware that if you make your battery fully empty it might refuse to work at all so you might need to charge it manually.
[Nexus 4 Original Android Development] stavca:
remove back cover from phone, unscrew 2 screws on battery connector and unplug that connector, then plug it again and voila, everything is ok ;)
[Nexus 4 Original Android Development] marcus6999:
This afternoon I will try to get the screwdrivers in order to dismount the back cover and pull out the battery, I hope it works! :)

---------- Post added at 11:24 AM ---------- Previous post was at 11:02 AM ----------

I tryied but everytime I get to the bootloader screen while connected to the USB cable in the PC reboots at this red led blinking without the opportunity even for the computer to detect the phone.
[Nexus 4 Original Android Development] stavca:
try it :) all you need is Torx 5 and small + screwdriver, I had the same issue and this was the only and needs to be said very quick solution, your phone thinks that your battery is "bad" so you have to unplug it and plug it again so it thinks that it's the new one ;) but if your battery really is that bad, maybe you would have to replace it...
[Nexus 4 Original Android Development] andrielau:
why when i install this kernel i dont have this file ?

/sys/android_touch/

-rw-r--r-- root root 4096 2013-11-27 11:27 doubletap2wake

-rw-r--r-- root root 4096 2013-11-27 11:25 doubletap2wake_version

-rw-r--r-- root root 4096 2013-11-27 11:25 s2w_s2sonly

-rw-r--r-- root root 4096 2013-11-27 11:27 sweep2wake

-rw-r--r-- root root 4096 2013-11-27 11:25 sweep2wake_version

before i use kernel hellscore and i want to try this kernel but i cant use sweep2wake and then i check with root explorer i not see folder android_touch
[Nexus 4 Original Android Development] poondog:
It now uses semaphore 2w and not traditional sweep2wake

You can easily use synapse for this
[Nexus 4 Original Android Development] Gallardo994:
AK kernel doesn't have sweep2wake anyway. Only d2tw and 1ttw
[Nexus 4 Original Android Development] Gallardo994:
But we all want s2w! :D
[Nexus 4 Original Android Development] zedbg:
But we don't want it
[Nexus 4 Original Android Development] iskandar1023:
i love these feature but i hate accidentally unlock my phone.

but even sema dt2w says that it won't make accindental unlock, happens too. weird
[Nexus 4 Original Android Development] GruZone:
Had the same problem.

Leave it in the charger (you will notice battery is trying to charge, animation is starting to show charging process and then turns off).

Leave it like this for an hour.

Then take another charger, preferably not a USB+ac adapter charger (from a friend or family) and start charging with it.

When it starts to charge try turning on the phone a few times then leave it charging for 1 hour.

It's not an exact recipe but I managed to wake my phone.

Update us if it worked for you.
[Nexus 4 Original Android Development] urim225:
Why do I get this ? I flashed ukm as usual and synapse. Dt2w works but I never got this error.
[Nexus 4 Original Android Development] bart.found:
Did you already tried to clear synapse's data?
[Nexus 4 Original Android Development] urim225:
I know that the error dissapears when I clear data but I don't want to clear data everytime I switch dt2w on and off
[Nexus 4 Original Android Development] bart.found:
Not all datas.. Just synapse'datas!
[Nexus 4 Original Android Development] nixie2121:
[MENTION=4362467]gorilla p[/MENTION] - what is the difference between your balanced and bat-bal profiles?

Thanks!!!!!!!!!!
[Nexus 4 Original Android Development] Nekator:
/system is mounted AS read only. Change /system/etc/init.d folder permissions to 775 and group root or Mount remount system AS read-write.

To remount type this in terminal:

$su

#mount -ro remount,rw /system
[Nexus 4 Original Android Development] urim225:
Thank you buddy that worked :D
[Nexus 4 Original Android Development] Nekator:
You're welcome, i always had this problem in pa. ;)
[Nexus 4 Original Android Development] karoli:
/system is in 755, SlimKat 4.4.4.build6-5279, AK v324, UKM 2.7.2 and Synapse v039 clean installed. Ideas?
[Nexus 4 Original Android Development] marcus6999:
This finally make my phone awake from his "red led blinking" sleep! Thank you, you are my savior, I almost thought that this phone wasn't working anymore!

As I managed to get it working I counldn't try it but thanks anyway.

Thank all of you who had helped me in this problem, without this forum I couldn't have managed to turn it on! :D

:victory::victory::victory:
[Nexus 4 Original Android Development] Nekator:
As the error says invalid argument. Look into the file that handle this option and change it in editor.
[Nexus 4 Original Android Development] karoli:
Well, Total Commander couldn't find the file. When I restart Synapse and it shows the "tick" and "x" sign and I push the "tick", it shows the previous error, but when I push the "x" sign, everything is back to normal, no error is shown. Strange.
[Nexus 4 Original Android Development] ak:
Goooooooooooooood man ... im very happy.
[Nexus 4 Original Android Development] Nekator:
Try do delete synapse cache and if that doesn't help delete data as well. It helps with most synapse problems xD
[Nexus 4 Original Android Development] arek78:
How do I turn Sweep2Wake + Sweep2Sleep?
[Nexus 4 Original Android Development] poondog:
See the last few pages please
[Nexus 4 Original Android Development] ak:
Please don't post directly log into thread ... You can use pastebin.

Always the same error with wcnss ... What ROM?

Seems there is problems with your ramdisk.
[Nexus 4 Original Android Development] shadeMe:
My sincere apologies - I'll make sure I use PasteBin in the future. I'm running Paranoid Android 4.5alpha1 (just updated, was on 4.41 earlier). How would I go about rectifying this issue? Will reflashing the stock boot image and then the ak kernel help?

PS: Thanks for the quick reply :)
[Nexus 4 Original Android Development] ak:
Yes ... But I have see this problem reported sometimes but only by users of pa.
[Nexus 4 Original Android Development] shadeMe:
I see. Well, thanks again - I shall try reflashing the stock boot image.
[Nexus 4 Original Android Development] icu64:
So I should avoid using your kernel for now if using paranoid android
[Nexus 4 Original Android Development] ak:
No ... you can use without problems.
[Nexus 4 Original Android Development] icu64:
OK good lol, I was just about to leave Franco and use your kernel then I saw your comment saying that you saw that kernel panic before with pa users and I wasn't sure lol
[Nexus 4 Original Android Development] ak:
I have see this problem only with pa, i'm using madhi daily without a single problem.
[Nexus 4 Original Android Development] icu64:
So wait, what is the problem and is it safe to use the kernel? You're confusing me lol sorry
[Nexus 4 Original Android Development] ak:
Don't worry. use it.
[Nexus 4 Original Android Development] ken_alpha24:
May have been asked before but is v 355 compatible with the Android L port?
[Nexus 4 Original Android Development] icu64:
Lol OK, loving it so far man
[Nexus 4 Original Android Development] Targaeryan:
Should work. I think you need to flash the custom kernel WiFi fix in the op of L preview thread. I'm gonna flash in a while since I'm downloading beta 4. Will report later if you don't want to try first.
[Nexus 4 Original Android Development] yellman:
did it work ? with 333 did not boot.
[Nexus 4 Original Android Development] Targaeryan:
Sorry. Forgot to post. It didn't boot.
[Nexus 4 Original Android Development] shadeMe:
@ak, reflashing the ROM's stock boot image hasn't seemed to have helped. I had a random reboot when the phone was asleep, but the error seems to be different this time (kmsg).
[Nexus 4 Original Android Development] ak:
voltages problem:

[31166.489226] L1 / TLB Error detected on CPU 1!
[Nexus 4 Original Android Development] Italico:
@ak:

I had this problems, too, and raising voltages a bit seems to help... Am I right?

PS: just asking about, no OTA: is a new version in the works? Because I am waiting to perform a clean flash...

PPS: may I find the info for a donation in your website (hidenbytes)? You deserve a beer, at least!
[Nexus 4 Original Android Development] ak:
onepone

Under my user info you can find all links.

I'm sorry but i'm waiting my new oneplusone and i have sold my n4. ;)

335 is the last ak kernel.
[Nexus 4 Original Android Development] hozjacz:
After a long time I'm back (sorry - I can't read whole thread - maybe somebody put this question).

A long time ago (when was OTA of CM11) I used this famous kernel with Cyanogenmod and then it was perfect.

Now I use SlimKat and with this I want use AOSP version of this kernel (stable or experimental version) and more times I get reboot my Nexus4, if I want wake it via DT2W: tap tap - nothing (black screen), tap tap - nothing (black screen), tap tap - nothing (black screen), short press power button - reboot.

Have this issue some solution?
[Nexus 4 Original Android Development] xenyz:
End of an era.

Thanks for all the work you've done for our makos, and have fun with your new giant phone. :)
[Nexus 4 Original Android Development] Utkarsh-ezzo:
what???

no more ak, no more mahdi

why all this so sudden, I am feeling like left over...

Anyways thank you AK for all you have done and hope to use your kernel on my next device.....
[Nexus 4 Original Android Development] ak:
Thanks a lot guys for this fantastic thread and users.

No more Madhi rom?