yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] adrok76:
Screen still doesn't turn on after sleep on r187

here's the last kmsg <script src='http://pastie.org/8370859.js'>

</script>

Hope it worked, I'm a pastie virgin!

EDIT: That didn't come out as I expected, sorry! Looks like you're on to it anyway..
[Nexus 4 Original Android Development] Rhodesfreak:
Thanks!!

My nexus works again!

But still issues with wifi, it keeps turning off.
[Nexus 4 Original Android Development] Floydfire:
Sorry for another question about it but I'm a little confused... For pa I have flashed from some days now jwr, but fku download jss... What is the right version? I'm on rc2 from 20 September...

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
I'm not able to fix this in the short future, so I'll just remove the piece of code that is giving these headaches. Its a stupid race condition.

I'll push r188 now with that piece of code removed.

It will be reverted to JWR again. I told them to stop with this, no point in moving past JWR at the moment.
[Nexus 4 Original Android Development] genkralyz:
I flashed r185, r186, r187 and no issues at all ;)... working great on rasbean....

thanks franco.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Waldos:
That's sad :( some of us have the kernel ok. But it's ok the revert, because many user have these hot-reboots.
[Nexus 4 Original Android Development] franciscofranco:
Ok r188 is pushed and that piece of code is removed until further notice. All should be back to normal now. I'm sorry about this, shít happens :)
[Nexus 4 Original Android Development] thebryceee:
I found that trying to flash r174 (last zip I had downloaded on my SD card) after flashing 186, it boot looped. Ram disk maybe corrupted? Idk.
[Nexus 4 Original Android Development] franciscofranco:
Its no big deal. It only happened if the device was thermal throttled and the user turned the display off. Some weird race condition. r188 should be fine, the problematic code has been removed.
[Nexus 4 Original Android Development] Waldos:
It's not weird, something is crashing. :) Thanks for your time and support!
[Nexus 4 Original Android Development] fozzie:
Yep. Screen off/on ok again (stock ROM). Thanks.
[Nexus 4 Original Android Development] ciprianruse88:
This is my r188 md5 checksum -- 12eb3dc4348ba90dfca75c410c3cb676 -- is this correct?
[Nexus 4 Original Android Development] fozzie:
Yup.
[Nexus 4 Original Android Development] Floydfire:
Franco for pa3.99 rc2 the kernel in his topic is jwr but fku download the jss, which kernel should I flash? Jss or jwr? Thanks for the reply...

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] namurt:
you should flash jwr.

fku is a little "dumb" in how it detects whether your rom is jwr or jss (it's just reading from the build.prop) and for some reason rc2 of pa has jls (jss) flagged in the build.prop.
[Nexus 4 Original Android Development] hotnikkelz:
everything back to normal here as well, thanks Franco
[Nexus 4 Original Android Development] franciscofranco:
Yes FKU is as dumb as a brick wall, I need to give it moar vitamins.
[Nexus 4 Original Android Development] Bobtehblob:
Yes it is something to do with the mic gain, it's set way too loud! Franco said a while back that he was going to implement some sort of control for it. I think it was personally requested by his gf too if I remember correctly! Just has to happened yet! Hopefully we see it soon because that's the last feature that I really want on this otherwise brilliant kernel :D

Sent from my Nexus 7 (2013)
[Nexus 4 Original Android Development] combatdeity:
Just a small bug in FKU to report, when you download the latest nightly as a .zip, it saves it to /downloads instead of /Download.
[Nexus 4 Original Android Development] edbertin:
give a break have #kitkat
[Nexus 4 Original Android Development] namurt:
it's not your fault there's no simple, elegant way to detect the base build of the user's rom.

google is dumb for creating the fork in the branches.

fku is a very robust app, and you certainly do the best you can. :good:
[Nexus 4 Original Android Development] fozzie:
You know you can pick where it is saved to now, in the mini file explorer now built in to the app?
[Nexus 4 Original Android Development] Floydfire:
Thanks BTW updater is also a little slow for me, sometime don't charge the change log... I noticed that for me is difficult to open the second link of the op, flu use that for downloading? Maybe you can give the user the possibility to change it? Or fix the problem at server? Because I have purchased the app and if you will fix the build prop problem for me is a little problematic download through the app... Another thing that I have noticed (I think is the combo pa-fk) is that the aptic feedback sometime doesn't work and WiFi sometime drop to work and you have to off/on I don't have this problem on stock so I'm only telling you for the future when you'll work with pa... I can't wait to see you two married, Thanks for your awesome work

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] adrok76:
Screen turns back on again on r188 :good:
[Nexus 4 Original Android Development] genkralyz:
just flashed r188, so far so good :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] hmillos:
Flashed r188 over r184, my ROM is PA 3.99 RC2, flashed jwr version and everything is normal.
[Nexus 4 Original Android Development] handols:
R188 is back on interactive from ondemand by default?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Mercado_Negro:
And here I was, thinking my phone was broken. Fortunately, it was just Franco and those viruses his kernels inject when we flash them :p

Thanks for fixing that so quick, man. It was terrifying for a couple of hours til I got home :D
[Nexus 4 Original Android Development] svnhvn:
r188 works great on stock ROM. Thanks Franco.
[Nexus 4 Original Android Development] drawde40599:
It was changed few builds ago 183or 184
[Nexus 4 Original Android Development] sordna:
Did you remove the tap-to-wake improvements too? Because I can turn on the phone by tapping one end of the screen, waiting 3-4 seconds and then tapping the other end of the screen. So neither the 100 pixel thing restriction, nor the 1 second reset works. As far as I can tell, the tap feature works the same on 188 as it did on the test 185.
[Nexus 4 Original Android Development] drawde40599:
Try a stable rom, every other person here has issues with PA. I have No issues downloading from app or h feedback or wifi on stock or CM its your rom
[Nexus 4 Original Android Development] Mercado_Negro:
Somehow the datasheet was incomplete when I downloaded it yesterday, probably just a bad download. That's why I couldn't understand some specifics. Now I have a better picture. I'll play with these parameters for a couple of days, thanks.
[Nexus 4 Original Android Development] galaxys:
So far so good with 188 on RBJ! Kernel rocks!! Cool
[Nexus 4 Original Android Development] Mercado_Negro:
Are you sure the parameter compression_rate works? I also tried compression_ratio and no such file or directory.

Also, why is the fixed_gain fixed to 10 steps increase/decrease?

My mistake, fixed_gain is working fine on lower steps. Now I just need to figure out how to work with the compressor.
[Nexus 4 Original Android Development] franciscofranco:
That feature is the same as in the last preview. The changes I've been making are not yet deployed because they need more work.

Back on interactive, and its for good.

Did you echo 1 > comp_rate? That is 2:1 compression ratio, 2 for 4:1 and 3 for 8:1.

I loaded the defaults based on your feedback yesterday.
[Nexus 4 Original Android Development] sordna:
Ok, thanks. I'll keep using this feature anyway, I'm spoiled for life :) Looking forward to testing any improvements! The main drawback for me is is that it tends to drain more battery but that's expected. However anything you can do to make the feature more power efficient would be welcome. I'd rather have to tap more times to wake up the phone from deep sleep if it saves more battery,

than having a code loop that polls and drains more battery.
[Nexus 4 Original Android Development] franciscofranco:
Current code does not loop at all. The device deep sleeps, the only thing that isnot powered down is the digitizer ;)
[Nexus 4 Original Android Development] Mercado_Negro:
Yes, I figured it out a few minutes later but didn't edit my post because I was testing, thanks.

The compressor is off by default, that's nice and expected, at least for me. Thanks for letting me know about 1, 2 and 3 to change ratios, I was missed in that part because I thought it was something like 2 for 2:1, 4 for 4:1 and 8 for 8:1 heh stupid me. What's the range for attack and release? I can't seem to go past 270ms for the release.

I switched the compressor on, set it to 2:1, set fixed_gain to 18 and rel_time to 250. That sounded pretty good on one of the songs we mastered today in the studio. I'll test more... Man, it'll be great once it gets some sliders in FKU :D
[Nexus 4 Original Android Development] 1ceb0x:
[MENTION=3292224]franciscofranco[/MENTION], I know it is an incomplete solution but I have one for your app: when you tap "download the latest nightly" it would be good to make a popup window that will say: "download latest JWR kernel or download latest JSS kernel" - two radio buttons. It's our duty as users to KNOW what kernel to flash on which ROM.

Thank you for your latest kernel! You rock man!
[Nexus 4 Original Android Development] theclaytons:
I agree. Make the kernel choice the responsibility of the user.
[Nexus 4 Original Android Development] Mercado_Negro:
Agreed
[Nexus 4 Original Android Development] Tex99:
Sorry what is tap to wake ? I also used "search" button but without results. Thank you

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] 1ceb0x:
Double tap on the screen and your phone will wake up. Not recommend it though.
[Nexus 4 Original Android Development] fozzie:
That's odd; I just searched this thread with those exact words "tap to wake" and got 85 results!
[Nexus 4 Original Android Development] Puzzlegirl:
No. Every other person does *not* have issues with PA - what a sweeping statement! Only the fact that fku downloads JSS, so I dl JWR and flash through Flashify. No other problems whatsoever here on PA RC2... In fact I haven't flashed 188 yet as I went to bed after flashing 186, which I didn't have any problems with and 187 which I'm still on and haven't had any problems with either. Just catching up with the thread over breakfast :)
[Nexus 4 Original Android Development] Floydfire:
So you with Franco kernel didn't notice that sometime haptic feedback doesn't work for some tap? WiFi seems to work pretty well maybe it's my router, but the app... Slowness if is the ROM... Why the hell also on stock do the same for me? Well PA is working good as far as I can see just some little bug...

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] drawde40599:
Well good morning :D but if u have time read backwards ull c PA is mentioned here with more strsnge issues than any other rom even when correct kernel is installed and its by people that no what there doing . All i was saying is with all the crazy crap that guy had going wrong for him that no body else did he should try a stable rom.
[Nexus 4 Original Android Development] Puzzlegirl:
No such problems at all and PA + Franco is an incredibly speedy combination. Perhaps you need to wipe and install a clean flash of ROM and kernel.

Well perhaps people only come here to complain most of the time :eek: However, keeping up with PA and Franco threads, it would appear that there are a hell of a lot of people running the combination without a problem :)
[Nexus 4 Original Android Development] Tricepz:
On R188, again wonderfull tweaks glad interactive governor is the only choice again.

Keep it up Franco.
[Nexus 4 Original Android Development] Floydfire:
I have flashed fresh and clean with wipe data pa399rc2 + r184 then now I'm on 188 is a strange bug that doesn't happen for all touches only some isolated touch doesn't vibrate...

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] theclaytons:
+1 on this using cataclysm rom on 188 JWR
[Nexus 4 Original Android Development] GalaxyGusta:
R188 works great again!
[Nexus 4 Original Android Development] Tex99:
Sorry my fault. I m on tapa and I used general search and not into the thread

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] eluspo:
Now flashing r188 but i never had any issues with r186 using purity rom. Thanks for the fast update [MENTION=470754]Franco[/MENTION].
[Nexus 4 Original Android Development] sir_fz:
Hi, probably asked a lot but is there a guide which explains all the various settings? As I bought the app but didn't change anything since it's not clear what the recommended changes are..
[Nexus 4 Original Android Development] 1ceb0x:
recommended changes are the ones already set :)
[Nexus 4 Original Android Development] sir_fz:
And no guide at all about the settings? Also, is it me or is the screen extremely bright with Franco? I'm on PA RC2 with r188 but it wasn't like that with PA RC1 and default kernel. Tried to modify gamma settings but nothing changed.
[Nexus 4 Original Android Development] Goku80:
can people stop putting +1 and actually give a bit more detailed info on what is happening to there phone...bugs the hell out of me and i hope xda does something about it:D
[Nexus 4 Original Android Development] xanthrax:
Screen on/off for colours to stick

The answer above was referring to kernel settings not colours

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] hughfollett:
Load the halfbreed colour profile and then screen off/on

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Original Android Development] 1ceb0x:
Come on dude... Really? That's because PA RC kernel has PA HALFBREED colors in it and they kick in when you boot the rom. Franco uses stock LG colors and you have a nice section where you can set your own profile or load other GREAT profiles. As per the guides... you have internet, right? If you search "interactive governor" on google, I'm sure you will find a gazzilion of websites that can competently explain what that is. Or any other setting for that matter.
[Nexus 4 Original Android Development] :
guys franco.Kernel-Milestone.3.zip is the last kernal for 4.2 right? does this have the double tap 2 wake feature?
[Nexus 4 Original Android Development] Goku80:
no

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

okay i am being really stupid and i have read like the last ten pages of the thread and i can not find anything about double tap to wake or tap to wake..isn't it enabled no more?
[Nexus 4 Original Android Development] Pipusz:
Nope, r165 is the last one for 4.2 and it doesn't have that feature. Development for 4.2 has been ceased.

Disabled by default, you have to enable it through scripts or terminal of root explorer.
[Nexus 4 Original Android Development] Goku80:
forgot the path on rootexplorer to enable it again...plus the damn search button has gone again:(
[Nexus 4 Original Android Development] Pipusz:
I believe this should be it:

/sys/module/lge_touch_core/parameters/doubletap_to_wake

Open the doubletap_to_wake and then change the N to 1 then save and exit.

Or run terminal emulator and type:

Su

Echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake

If I recall correctly, these settings go back to 0 once you reboot, so you have to enable them again.
[Nexus 4 Original Android Development] Bill Gamble:
echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake
[Nexus 4 Original Android Development] Goku80:
many thanks i really appreciate it..:) and yeah i do remember that it is okay though last time i managed to get a script done so it would be okay on reboot
[Nexus 4 Original Android Development] sir_fz:
Yeah dude, it's called a manual/guide...etc (documentation), shame we don't have that for this. Thanks for explaining :)
[Nexus 4 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] hey mate you have just done something amazing with the latest update... Awesome, awesome, awesome!!! All the features I could possibly want from a kernel, super fast and responsive, absolute lighting with Neo ROM v7.1 Thanks mate, keep up the great work and get some rest :thumbup:
[Nexus 4 Original Android Development] peikojose:
Have you or someone else tested the effects on battery life having double tap to wake on?

I lost 11% overnight today.. When usually it ranges from 3% to 5%... Coincidence ? I don't see anything strange in battery stata and wakelocks..

Best regards...
[Nexus 4 Original Android Development] CamoGeko:
I think for everyone that wants to use it, the benefits outweigh any kind of battery drain downside.

If there is any at all...
[Nexus 4 Original Android Development] rofik_gitara:
now im on PA 3.99 RC 2 and use franco 184,

if i'ill update to 188 what i need wipe anything after flash 188?

thanks for good respons
[Nexus 4 Original Android Development] mohitgalaxy3:
Hi Franco, last night flashed R186 and got a hot reboot and my fav game data got corrupted, dont know why and how.

Want to flash R188 but just want to confirm whether that bug has been fixed or not.

Thanks.
[Nexus 4 Original Android Development] CamoGeko:
No need to wipe anything.
[Nexus 4 Original Android Development] rofik_gitara:
cache and dalvik no need??

oke flashing update now..
[Nexus 4 Original Android Development] PetritH:
Never wipe for flashing kernels
[Nexus 4 Original Android Development] Fenvarien:
With the latest cm 10.2 nightly 10/2 I get massive graphic distortion.

Switching back to the cm nightly before solves the problem.
[Nexus 4 Original Android Development] Nburnes:
[MENTION=3292224]franciscofranco[/MENTION].......... and it begins!
[Nexus 4 Original Android Development] onbeskarakterli:
Same here. I thought 188 is the problem, but 184 also has it.
[Nexus 4 Original Android Development] bruce7373:
After enabling, I have singletap-to-wake (r188 on latest Cataclysm). Anyone else ?
[Nexus 4 Original Android Development] rofik_gitara:
any problem if i wipe cache and dalvik?
[Nexus 4 Original Android Development] zygis10:
Nope
[Nexus 4 Original Android Development] franciscofranco:
That is all cool and dandy. Then I'll get emails ans messages asking "WHAT KERNAL SHULD I INSTALL? I NOOB KKTHX". Always the same. But I agree that thats the best short term solution. I'm working on the next generation FKU though.

There is no actual guide, but I'm working on the next generation FKU and that will have documentation for every option so that less-knowledgeable users won't feel weird about abusing the app settings :)

That is normal, the digitizer is kept active so even if you're device is deep sleeping the battery has to keep powering the touchscreen otherwise it won't receive input touches.

Yes that is true. CM is following a weird path by merging Mako and Flo Kernels together using CAF's tree and not AOSP tree and they started using a different hardware composer... there's nothing I can do about that at this point. CM is being CM, doesn't surprise me.﻿
[Nexus 4 Original Android Development] TheByteSmasher:
[MENTION=3292224]franciscofranco[/MENTION] your kernels aren't compatible with JLS, but the app still downloads the JSS version... which throws all the colors out of whack. Also, since 4.3 the app only pretends to download zips again. Thanks
[Nexus 4 Original Android Development] ..Cory..:
Keep doing what you do bro, you never fail to impress me with your work!
[Nexus 4 Original Android Development] franciscofranco:
?

Of course FK is compatible with JLC, there are almost no changes between JSS and JLC. Unless you're using the latest CM nightly, read my post above.
[Nexus 4 Original Android Development] TheByteSmasher:
I'm using AOKP... I'll take a screenshot and show you if you'd like...
[Nexus 4 Original Android Development] TheByteSmasher:
Jss-188

Blues should be red... yellow is supposed to be Holo blue (ff33b5e5)... the shot of your app is using the Holo green theme....
[Nexus 4 Original Android Development] RootTheMachine:
Franco, your app thinks that the kernel has finished downloading when connectivity changes during the download. It displays "null has been downloaded" and will even try to auto flash it.
[Nexus 4 Original Android Development] 1ceb0x:
All this JSS and JWR kernel will be gone when 4.4 arrives...
[Nexus 4 Original Android Development] Testraindrop:
Thats some problem on your end, JLS36G Nightly CM is working fine (before 02102013) with JSS Kernel and always has.
[Nexus 4 Original Android Development] santeana:
To all those having issues with colours and black screens on the latest 188 kernels.... IT'S NOT THE KERNEL, IT'S YOUR ROM! The latest CM10.2 and some AOKP builds in the last 24 hours or so are having issues with the latest Franco Kernel. I have experienced it as well. Went back to my previous aokp version and all is well.
[Nexus 4 Original Android Development] TheByteSmasher:
OK... here's the weird thing. Those shots I took were all screwed up, I switch back to stock kernel and those screenshots look normal now (and makes the post look silly)... I don't know enough about kernels and screen drivers to understand this...
[Nexus 4 Original Android Development] franciscofranco:
Thats probably because AOKP is just pulling stuff from CM and then all hell breaks lose. Its a shame that they've went down that path. I won't ever let PA cater to CM or any other bull**** changes.

Sorry, I don't deal with connectivity changes during the download, maybe I should though.
[Nexus 4 Original Android Development] TheByteSmasher:
OK.. so if I'm building my own aokp... which source tree is the jacked up one that screws with your kernel, because I'd rather use your kernel...
[Nexus 4 Original Android Development] TheDarkDefender:
Hmm i guessed the same. I think aokp started using cm's unified caf kernel(/device repositories?) which is causing all the trouble. Looks like it.

About PA, well im sure moles would never cater to cm. He already hates the cm cherry picks he has done and has "sworn" to write all the cm kanged features from scratch for kitkat, lol :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] zygis10:
Hi guys after trying some other kernels I came back to fk. It os awesome with ondemand governor, but with interactive it is quite laggy, am I the only one who thinks that ondemand governor on this kernel works better, cause I have seen that most of you are using interactive? Do I have to change some of the governor values to make it smooth or what?
[Nexus 4 Original Android Development] RootTheMachine:
You probably don't want users auto-flashing nonexistent downloads... It should at least throw an error or refuse to auto flash if the download doesn't complete successfully.
[Nexus 4 Original Android Development] Liebhild:
FKU 10.3.3 / r188

In the SuperSU-Log I have every few minutes one of the following entries:

echo 1512000 > max_freq
exit
sh: <stdin>[1]: can't create max_freq: Read-only file system

echo 384000 > min_freq
exit
sh: <stdin>[1]: can't create min_freq: Read-only file system
[Nexus 4 Original Android Development] PeQuEsan:
I think pretty much the same... I've given interactive a go again with fk188, but I'm sure I'll be back to ondemand in short... With interactive there's a little delay between you touch the screen and it reacts... it's so small that you shouldn't realise... but if you test ondemand then you see what's instant reaction! :)

I'm a little bit concerned about some issues that Franco saw to his ondemand implementation, that made him go back to interactive in the end... :( I haven't seen mayor issues with ondemand, though... No big battery drain, no nothing.

bye!
[Nexus 4 Original Android Development] CamoGeko:
Most use Interactive because it has more tweakable properties and thus is easier on the battery.

Ondemand keeps the CPU in the higher frequencies longer.