yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kcls:
Just flashed r25 test, and for some reason it turned my phone into an utter lagfest. I came from r23, which was smooth as silk, but I was getting 6+ hours of msm_hsic_host wakelock. Apps take much longer to start up with r25, and when locking and unlocking the phone, I am greeted with a black screen for a couple of seconds before the lockscreen actually shows up.

Are you supposed to wipe cache or dalvik before flashing? I've only ever done it via the app or fastboot before.
[Nexus 4 Original Android Development] Luigiesin:
Yup... Did that too... Twice... But don't want to over do it..
[Nexus 4 Original Android Development] tmhiott:
I ran r24 all day with no problems at all, literally 0 battery loss when on idle/wifi, and no reboots/force closes and I didn't find myself having a problem with data connections (I used cellular data when I went out for about 3 hours, rest of the time I was on wifi. 16 hours on time, 3.5 hours screen on time, and I have 38% left and that's with location/gps on and gmail/Facebook synced.

I'll flash r25 and ill be testing all day tomorrow.

Love it, thanks for all your work Francisco!
[Nexus 4 Original Android Development] drdrewdown:
it might help if you're having issues. but otherwise i never do.

r25-test is fine, no "lagfest" here.
[Nexus 4 Original Android Development] franciscofranco:
I cannot replicate this, 200% as smooth as before.
[Nexus 4 Original Android Development] Ballastatuz:
Me either. Its super smooth. I'm at 1250 max 418min. The only thing is my signal bars go up and down but I can still use the internet it is stabilzing on r24 I couldn't even go on the forums.
[Nexus 4 Original Android Development] Skillfulshoe:
Got a little toasty over here on r23 but nothing to worry about since I was streaming music and playing it over Bluetooth while taking pictures and sending them over 3g. Good part was that the battery barely went down during that period of time. Excellent. Can't wait for the milestone.
[Nexus 4 Original Android Development] Luigiesin:
Just flashed R25 test.... It's definitely smoother over here... Plus I can see the data a bit faster than R23... Going to check stats tomorrow during the day for wakelocks and report back...

Thanks Franco!

Lu
[Nexus 4 Original Android Development] dwang:
Getting tons of log cat spam with r25
[Nexus 4 Original Android Development] tim.smart:
I get that on r23 as well. There is an issue on Google's bug tracker for Android filed already.
[Nexus 4 Original Android Development] drawde40599:
Ya that's what 24 did for me 25 seems legit so far , YouTube didn't wanna load a video but YouTube is 2 unpredictable to say kernel related , 25 data back , and is smooth fast and lag free.
[Nexus 4 Original Android Development] Luigiesin:
Delete.
[Nexus 4 Original Android Development] Pure Drive GT:
Nope he is just looking at the percentage, but i think you know that ;) Imo there are way to many freq. steps atm. I find it makes sense to use only useful states. You could (if you wanted to) dump a few of them. If its possible and reasonable to throw out steps.

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] AxelCM1:
still do not know, after the restart I changed the two files in the folder data / misc / audio. not if you have something to do.
[Nexus 4 Original Android Development] hamad138:
Its incredible ,how can franco make better kernels than the google devs. If u compare stock to franco 176 u see how laggy stock is and how much battery it drains.

Are the devs amateurs?
[Nexus 4 Original Android Development] pkelly517:
Maybe it would help if you posted a larger image.

Or looked at the actual time each freq was used, instead of the percentage.

:good:
[Nexus 4 Original Android Development] zephiK:
The picture is in full resolution? :confused:
[Nexus 4 Original Android Development] waleedshiekh:
I'm not looking only at percentages. I just compared it Stock kernel provided with PA. If I use interactive/deadline on that it goes through different states to reach max and vice versa. Thanks.
[Nexus 4 Original Android Development] Luigiesin:
I agree almost totally... Google devs work with ondemand.. Including apple.. I guess is the smoothest for consumer purposes... But I know even working with ondemand they could do some tweaks like Franco does and improve performance and battery overall... Don't think it would get the same results as interactive, but ondemand is the safest consumer approach.

I'm sure if Franco would be working with them, Android kernels would be on higher level... Same with the PA team... Those guys are geniuses as well... So I don't know what's the deal with Google... Maybe Franco can explain a bit more.
[Nexus 4 Original Android Development] trillo69:
You have to think that there are many other aspects to consider in a kernel, not just smoothness and battery drain: hardware compatibility (wifi, camera, audio), stability,... and I bet that the same developers work in another devices kernels.

So I don't think that they are so bad, they aren't as stock kernel is great actually, it's just that they aren't focused in Nexus devices as ours devs. Moreover, you should think that franciscofranco and other work in over google or aosp kernel base, not from scratch from a linux kernel (am I wrong here?), so I think that Google devs deserve some credit too.
[Nexus 4 Original Android Development] Mercado_Negro:
I don't think they are, in fact, the stock kernel is much better now. To me, performance-wise, there is no real difference, from a user stand point. This is just my opinion, from my experience with both for days. Your millage may vary.
[Nexus 4 Original Android Development] jewellsimon:
Hi quick report I have the display control app and I constantly get a notification stating that the app is running. Even when I choose not to display notifications in the apps config. Also I get very large lags when utilizing the kernel(most visible when typing). I am running slim 4.3 by the way. Also long time fan of Franco's work, not complaining, I know work 4.3 is a progress

Sent from my Brain
[Nexus 4 Original Android Development] rest0ck:
Hey I just flashed franco after updating PA and now everything is .. hm i dont know how to explain it (maybe it was mentioned before but I wasnt sure what to search for).. everything looks like I dont use fixed FPS in a game (Vsync). So when theres a widget and I scroll between pages the upper half is more forward than the upper one. Or when i drag down the notification bar entrys look like they are above the line at the end etc. I can't use the phone like that so I flashed the Stock PA again.

I got the same error with Faux Kernel btw.
[Nexus 4 Original Android Development] franciscofranco:
Well you formated data so the device won't boot... best thing you should do is go to the bootloader, lock & unlock it (you'll lose everything including sdcard) so that the device gets reset to factory state.

There is a difference between building Kernel drivers from scratch and building the entire board files and doing smaller Kernel optimizations and modifications. I don't do board files and I don't build hardware drivers from 0 like CAF does and Google had to do for the first Nexus, the G1. Its not hard to build drivers, but its a bit painful and needs proper documentation. What Google does is making it work. They won't waste much time trying to get that last 5-10% extra performance, they just make it work with what they have. If I worked for Google on the Kernel department I wouldn't be doing much more than what they are doing, I would basically just fix bugs, do instrumentation, and make stuff work. Sure I build nice hacks and nice optimizations across the board, but thats nothing compared what true upstream Kernel Developers do, its just another level. Fortunately I helped Google a couple times to fix some bugs on the Kernel level, specially on Interactive and that felt good.

Hope that answered it :)

Google made that notification on purpose, Dianne Hackborne wrote about that on G+ some weeks ago. I'll fix it today or tomorrow, I've been really busy with A LOT of things at the same time ;) about the lag, you're probably not using the correct Kernel version for that rom.
[Nexus 4 Original Android Development] franciscofranco:
Anyone tested the latest FKU beta? If so, any problems to report or last minute suggestions?
[Nexus 4 Original Android Development] rikkoko:
So I kind of fixed it. I just had to use N-Cry toolkit to flash 4.3 again since I completely wiped my phone. Luckily I had a helium backup. Hopefully anyone who encounters this same problem will see this post haha.

I might have tapped on "auto-flash" a second time while it was already flashing or something when trying to get r176 on my phone because I thought I didn't tap it the first time. So maybe that was the problem? Well anyways, thanks for trying to help guys!
[Nexus 4 Original Android Development] jewellsimon:
That's good to here. I am using the jss version of the kernel. Am I utilizing the wrong kernel? Slim indicate they are using jss...

Sent from my Brain
[Nexus 4 Original Android Development] franciscofranco:
No idea then. You're using the correct version.
[Nexus 4 Original Android Development] Redneck Trash:
Setting max GPU to 320 works. Creating, applying and changing default system modes works. I know there was something else reported but I don't remember what it was. A new issue. App force closes when clearing app data.
[Nexus 4 Original Android Development] LibiSC:
Well it's not the fstab.mako so must something in the init... Are those changes for interactive sysfs necessary for the kernel to work... Also will it be Ok to run francoscript in the init.d like any other script except for the part where it checks for the folder?
[Nexus 4 Original Android Development] rest0ck:
Uhm sorry for the latest question. I used the JSS Version because I thought PA is still considered as JSS.

But now Ive another problem: I lose root access when I flash franco Kernel?
[Nexus 4 Original Android Development] inculto:
flash supersu
[Nexus 4 Original Android Development] GForceXIII:
deleted
[Nexus 4 Original Android Development] rest0ck:
I still have the inbuild superuser from PA but it ..wont work?
[Nexus 4 Original Android Development] nuwan32:
[MENTION=3292224]franciscofranco[/MENTION] anything?
[Nexus 4 Original Android Development] zephiK:
Don't believe there is a bump, heard him mentioned a couple weeks ago that franco took out the bump
[Nexus 4 Original Android Development] franciscofranco:
Oh really? Thats ironic. I know what it is though, its the ****ing context being lost somehow I think. Thanks for the tests.
[Nexus 4 Original Android Development] franciscofranco:
That has been fixed. The bump was just the UI being dumb enough because the Thread was a bit slower than the UI when updating the view. Its fine now.
[Nexus 4 Original Android Development] scandalousk:
No when you flash franco's kernel it breaks root on PA.

[MENTION=3292224]franciscofranco[/MENTION], speaking of which. Going by your response here: http://xdaforums.com/showpost.php?p=44623209&postcount=43429

You seem to know as to why root breaks with the PA rom. Would you be able to fix it in due time or is it something that is out of your hands? Using supersu is no biggie, I'm just curious to know why it breaks.
[Nexus 4 Original Android Development] franciscofranco:
I'll fix on the next release. Its because I have to add the daemon start init in the ramdisk for superuser, which I haven't.
[Nexus 4 Original Android Development] LibiSC:
you mean this?

# su daemon
service su_daemon /system/xbin/su --daemon
oneshot

on property:persist.sys.root_access=0
stop su_daemon

on property:persist.sys.root_access=2
stop su_daemon

on property:persist.sys.root_access=1
start su_daemon

on property:persist.sys.root_access=3
start su_daemon

edit:

the guy from unofficial franco kernel from jss made the change i will pick it from his ramdisk :good:
[Nexus 4 Original Android Development] Mercado_Negro:
Thanks, looking forward to it. I'm about to flash PA now because those new improvements in Halo look very interesting and they're exactly what I've been waiting for from it. I'll have to stick to that halfbreed kernel in the meantime.
[Nexus 4 Original Android Development] runningreturning:
Hey, just flashed the pa3.97 update and noticed that you put up r197 for JSS builds so i flashed that as well... But animations were very choppy so i went back to halfbreed. Sorry if this has been brought up already no time read 45+ pages of posts lol. Jw if i made an error here somewhere? I know pa merged jwr/jss so does this mean i should attempt the non jss version of your kernel?
[Nexus 4 Original Android Development] riza_hakam:
franco,

it seems i still face reboot to recovery problem when flashed your r176 build.. i already download again but it still happen..

i am in stock rom rooted, i flash your kernel via cwm and restart.. it past google and nexus logo and enter rom.. but after 5 seconds it will reboot to recovery..

where do my step wrong? anyone can explain it to me?
[Nexus 4 Original Android Development] Mercado_Negro:
You need Franco's JWR66V for PA because now it's based on JWR66V with JSS15V improvements.
[Nexus 4 Original Android Development] runningreturning:
Thanks for quick reply. I guess i only assumed that it was still based on jss. Makes sense now though appreciate the help
[Nexus 4 Original Android Development] CdTDroiD:
Running nice on official CM10.2 nightlys
[Nexus 4 Original Android Development] scandalousk:
Thanks for explaining mate. I'm glad to see it'll be fix upon the next release. Keep up the awesome work!
[Nexus 4 Original Android Development] franciscofranco:
Only need this:

# su daemon

service su_daemon /system/xbin/su --daemon

oneshot
[Nexus 4 Original Android Development] franciscofranco:
No idea, never had that happen to me. Can you get me a logcat please?
[Nexus 4 Original Android Development] runningreturning:
Feels good to be back on your kernel franco, i must say that a few weeks without it was a lot more painful than i expected. It runs exponentially better than stock kernel. Once again, thanks for sharing your work with the community.

One quick question- does headphone volume boost/gain boost work on 4.3 nightlys?
[Nexus 4 Original Android Development] ranasrule:
on this kernel is there any way to wake up the devices by swiping the screen?? it doesnt support TouchControl....does it have Swipe2Wake ??
[Nexus 4 Original Android Development] zephiK:
no. read faq

no it is not working atm.
[Nexus 4 Original Android Development] riza_hakam:
i will try get you the logcat when i have access to my pc
[Nexus 4 Original Android Development] svnhvn:
When i installed recovery from mskip toolkit and updated it (img or zip) it always happened like you. But when i installed via ncry those problem vanished.

Its no kernel related, at least on my device.
[Nexus 4 Original Android Development] swiftyy:
Hi Franco or anyone else that can help me.

I had a random reboot on the r176 JWR version of the kernel. I'm on PA 3.96. I'm attach my last_kmsg for your reference. Thanks.
[Nexus 4 Original Android Development] Mercado_Negro:
Heh Franco will fix those deadlock issues we've been experiencing on JSS15V builds... A legendary fix, it shall be :D
[Nexus 4 Original Android Development] franciscofranco:
No errors detected

Boot info:

Last boot reason: watchdog

Probably the modem that crapped itself - nothing about me or FK in specific.
[Nexus 4 Original Android Development] LibiSC:
that didnt work... but this did

# su daemon
service su_daemon /system/xbin/su --daemon
class main
oneshot

on boot
start su_daemon

I had to check the ramdisk in pa stock kernel... now finally i dont lose root and because i dont lose root i dont mess up my wifi with wpa :cyclops:
[Nexus 4 Original Android Development] AxelCM1:
Edit:

Ok. Steps to operate the volume boost.

Requirements:

Franco Kernel #176

PA 3.96 and 3.97 (not sure if it works in other Roms)

Franco Kernel Updater.

Steps:

1.Enter in FKU and Increase maximum volume in the two sections.

2. Increase all volumes on the system to the fullest.

3. Enter the settings / sounds / volume panel style / switching Between expanded and none, the N4 will reboot and you will Have to run the Increased volume in headphones and the speaker.

Enjoy!

Comment if they worked

I solved as [MENTION=3292224]franciscofranco[/MENTION] asked me. Please put in the beginning of the thread for people to enjoy. thanks
[Nexus 4 Original Android Development] Redneck Trash:
And the flood of people looking for the nonexistent r177 begins in 3...2...
[Nexus 4 Original Android Development] muldersam:
Franco, i am using PA 3.96 and kernel r176, screen tearing issue. Any solution?
[Nexus 4 Original Android Development] dunghnguyen:
my rom is Cataclysm so it is jwr66v...I flashed r176...but I saw it indicates #177

[MENTION=470754]Franco[/MENTION]: pls advise ...tks.
[Nexus 4 Original Android Development] Mercado_Negro:
Which kernel version did you download? JSS?
[Nexus 4 Original Android Development] elite_gamer04:
Not atm in its 'official' form, [MENTION=3292224]franciscofranco[/MENTION] is currently 'thinking' about adding module support back in as Android 4.3 pulled it out by default - citing concerns over security. There is currently a debate going on about how real these concerns are etc... Hoping he does add it in though :)
[Nexus 4 Original Android Development] muldersam:
Yes JSS kernel kernel
[Nexus 4 Original Android Development] Mercado_Negro:
Then that's your problem, PA needs a JWR66V kernel. Download the other.
[Nexus 4 Original Android Development] runningreturning:
I think that may have worked :) still messing with it to be sure
[Nexus 4 Original Android Development] freezeburn:
Is color control working? I'm using PA latest and in not able to make changes to the color control.
[Nexus 4 Original Android Development] schizophrenia:
it's a typo.

search "177" on this thread and you can see many people asked and answered already
[Nexus 4 Original Android Development] svnhvn:
.......

Lock off and on your screen.
[Nexus 4 Original Android Development] Redneck Trash:
Reading. A lost art.
[Nexus 4 Original Android Development] swiftyy:
Any suggestions on a possible fix? Do I need to update my modem? I'm on the .84 modem right now. Thanks
[Nexus 4 Original Android Development] shahabk818:
Guys I have a question, I want to finally upgrade to 4.3. Does AOSP 4.3 works on Paranoid? What works and what doesn't? Headset gain and headset volume is so important for me! How stable is it?
[Nexus 4 Original Android Development] 5526859:
Asop gps bad
[Nexus 4 Original Android Development] ridikolous:
Delete
[Nexus 4 Original Android Development] wildestpixel:
That's a confusing question. AOSP refers to a kind of ROM as does PA. In response to what I think the question actually is, if you are using PA you need to use a JWR66V kernel at the moment so in short the standard JWR66V Franco kernel is what is needed and works.
[Nexus 4 Original Android Development] shahabk818:
Ok just tell me what doesn't work? Is it stable yet or not?
[Nexus 4 Original Android Development] wildestpixel:
Try it and find out. I'm on stock and also have the ability to read back less than 10 pages in this thread also.
[Nexus 4 Original Android Development] alanwyl:
No audio hack is available now

4.3 changes everything

Geez when will people search.......you are holding a Google phone
[Nexus 4 Original Android Development] nachordez:
Please, don't speak so loud, I'm not deaf...

Nexus4 / Cataclysm / Franco
[Nexus 4 Original Android Development] zorginho:
stable and so smoooooth but no andio mods.

so I'm waiting with slim 4.2.2 and fk r163 since they were fixed, I listen music for several hours and that audio hacks are so important for me too.

T_T

sry for my bad English.

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] elite_gamer04:
[MENTION=3292224]franciscofranco[/MENTION] - Just had a reboot on r176 (PA 3.97), does the following kmsg help at all?

http://pastebin.com/raw.php?i=Q3ZMNqd3

I'm assuming no :(...
[Nexus 4 Original Android Development] gv231089:
R176 working rock solid
[Nexus 4 Original Android Development] muldersam:
After i flashed JWR kernel on PA 3.97, i lost my root access. Any idea how to gain back root access?
[Nexus 4 Original Android Development] occtec:
This question is like only asked a million times. Flash super su v1.51
[Nexus 4 Original Android Development] jak3z:
Looks like a completely normal reboot :(

[ 7948.604360] Restarting system with command ''.
[ 7948.604512] Going down for restart now

No errors detected
Boot info:
Last boot reason: reboot
[Nexus 4 Original Android Development] Cuzz1369:
Change the damn app to say that when you change a color profile please. Obviously people don't get it.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Redneck Trash:
It's only on about every third page of the damn thread.
[Nexus 4 Original Android Development] Cuzz1369:
Its every page and highly annoying.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Pure Drive GT:
Yes I understand your concern :) But the question is what is better, not who uses more frequencies. I myself really can't tell. To be very honest, I tested stock kernel for a very long time and was very happy with it. I got very good battery life and very good performance. Out of pure boredem I ended up flashing the Franco Kernel. And I have to say, not looking at anything and simply using my phone I can't make out any differences. I use a TPU case so it's hard to judge how cool the phone is running. Performance of both is phenomenal. Battery is good on both can't simply say this is one is better than the other. The difference from stock 4.2 to FK was HUGE, this gap has become smaller in my opinion and I think that is good. Franco is not doing a worse job in any way, google has simply become better :) But like it always has been ... Franco will just do the icing on top of it and ad chocolate chips inside and make it simply yummier :D
[Nexus 4 Original Android Development] luckydude:
question about wireless problem

when i install your kernel in miui 4.2.2 wifi doesn't turn on but when i flash faux it works correctly what should i do ? any solution ??
[Nexus 4 Original Android Development] Pure Drive GT:
As far as i know MIUI is not supported and nevet will. See OP. Pretty surprised that it booted up xD

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] luckydude:
what is OP ??? i downloaded the franco kernel for miui rom
[Nexus 4 Original Android Development] hughfollett:
OP is the original poster or original post..

Inviato dal mio Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] mefistos:
Is there any fix for recommended gamma settings in works?
[Nexus 4 Original Android Development] llsantiago:
Turn screen off/on and it will work!
[Nexus 4 Original Android Development] Cuzz1369:
Obviously its just your brain that doesn't work. I suggest a factory reset.

Sent from my Nexus 4
[Nexus 4 Original Android Development] llsantiago:
I tried this on stock ROM and it is workiiing!!! :)

People may try setting the volume boost and than reboot to see the diference.
[Nexus 4 Original Android Development] Testraindrop:
Franco or anyone using a JSS build, could you do me a favor and try 3DMark and look for screen tearing?

I don't care about the scores,but just want to know if the problem is on my side or somewhere else.
[Nexus 4 Original Android Development] mefistos:
It used to work without turning the screen off and on again... I thought this procedure is tied to color setting not gamma... dumb me... :D
[Nexus 4 Original Android Development] scandalousk:
What rom are you on? Did you make sure you're using a JSS rom with the JSS kernel? If you're on paranoid android you need the JWR kernel.

Yeah it did used to work that way. It'll probably come back some day, let's just give franco all the time he needs to sort everything out.
[Nexus 4 Original Android Development] Testraindrop:
CM, as far as I know it's JSS, of course I'm using JSS kernel.

Gesendet von meinem Nexus 4 mit Tapatalk 4