yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] manulemaboul:
Yep, one core at input boost on single touch, that's right.

It fires up the 2nd on 2nd touch or maybe after 2s, hard to figure out if I moved or not.

Edit: if I understood the commit, it's if boosted time >1s and it's load dependent. Still the gov doing its gov job, just doing it better :)

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] PelegK:
LOL
[Nexus 4 Original Android Development] McKael:
FWIW I've had that twice with r148. I've also had to reenter the SIM PIN code - I had never experienced that before.

I'm running stock ROM.
[Nexus 4 Original Android Development] steviewevie:
Please, not unless the radio/data issues are definitely gone.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Floydfire:
Your kernel damaged me, now even tapatalk 4 beta is more smooth and my girlfriend broke with me because her iPhone 5 isn't so smooth. So pay me the damage!

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] thebryceee:
Lol I've never had any data issues with any build. Anyone in the US having that problem?
[Nexus 4 Original Android Development] Danny.ns:
Indeed, I have tried every build of the 14X series and wi-fi + data has worked flawlessly. I'm in Sweden, if that even matters.
[Nexus 4 Original Android Development] Mo'HAWK:
Uh there are major problems with r151.... Xda keeps up with my finger... All jokes aside I really enjoy this update.
[Nexus 4 Original Android Development] nachordez:
I had it twice today (on stock), once in 150, once in 1111.

By now, it didn't happen in 151, we'll see...

BTW: not carrier problem. My wife's phone didn't suffer this drops

nexus4 / stock / last Franco.kernel nightly / V4A sound

gt-p5110 / PAC rom / V4A sound
[Nexus 4 Original Android Development] Mo'HAWK:
I can honestly say I've have experienced drops in the US but I think now that it is T-Mobile and not the kernel.
[Nexus 4 Original Android Development] Allosaur:
Best one yet Franco. Don't know how you do it! Sent you a beer via PayPal donation. Cheers.
[Nexus 4 Original Android Development] franciscofranco:
Its simple, I code my ideas :) Thanks!
[Nexus 4 Original Android Development] Testraindrop:
If one of you with radio issues wants to support Franco, you can easily grab a adb radio logcat. First enable all logging, reboot, reproduce, grab log.

Maybe this will help Franco.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Floydfire:
It's not simple to have good ideas + good skill to coding the ideas!

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] manulemaboul:
Franco, couldn't you merge the faux sound module now that they got a script to have default n4 values with it by default in the prima + faux version ?

I'm using their version just because of faux sound, I don't need prima actually.

My speaker can handle louder volumes, it's OK with some compression and I do ear notifications.

With the script, it's transparent for users without an app to tune it, just like stock.

Users who would want to tune it would just have to install faux' app :)

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] pikachukaki:
Why everytime im decide to try another kernel franco updates!??

Yeah franco faux sound is great i want to hear my phone!pls added!
[Nexus 4 Original Android Development] limeaide:
This is not true it can be carrier.

If you happen to be a slight distance farther from the tower then she is and it swapped you to a tower that is suppose to be closer.

My daughters phone will jump to a tower that is farther than the one Im on just because she walks ten feet from me.

As for having data drop outs how many of the in the states are on att or straight talk att? Ive been having some weird signal problems but I attribute that to being on ST-ATT.
[Nexus 4 Original Android Development] manulemaboul:
Prima even breaks my push notifications actually, but they're useless if I don't ear them, right ? :p

Envoyé depuis mon Nexus 4
[Nexus 4 Original Android Development] gravitysandwich:
Well I got a random reboot. From turning my phone off. Kernel panic to be specific. So its late here in Poland (1:16 here for vacation) and my phone was running dry so I plugged it in (hit 4%) then after an hour I realized it stayed at 7% for like a year so I'm like I'll turn off my phone and go to sleep while charging. So while the turning off phone turning off dialog popped up, the phones screen turned off but not the backlight and boom random reboot. It booted with 0% battery remaining and I had to unplug and replug several times before this dumbass realized its ac not USB. So here's a log and sorry for the Chinese letters at the bottom Idk wtf happened. And I'm on the go so I have to use pastebin. I'll repost it if you want those Chinese letters gone.

http://pastebin.com/eHh1gFrx

I read the log and it said something bout hotplug so I'm guessing Franco you derped in the coding??????? But Idk I just want to have this phone off while charging lol

Edit: 2nd time i tried to turn off the phone while plugged in:no reeboot
[Nexus 4 Original Android Development] LaboDJ:
Thanks for the answer... in your lib/vsprintf.c you have 2 lines like so:

#if BITS_PER_LONG != 32 || BITS_PER_LONG_LONG != 64

And if BITS_PER_LONG is defined here and there in kernel sources (but undefined in vsprintf.c and apparently in its included files)

BITS_PER_LONG_LONG isn't present in sources... I can't find it.

I usually use

grep -R "string to I want to find"

and no file contains BITS_PER_LONG_LONG :eek:
[Nexus 4 Original Android Development] franciscofranco:
I'll add static speaker boost sometime in the future.

Hmm thanks for the log. I don't know exactly what triggered cause the panic. :(
[Nexus 4 Original Android Development] republitarian:
[MENTION=3292224]franciscofranco[/MENTION] you did it!! 151 is amazing on battery life and very stable in ANY game played, including temple run 2 :D. I'm not having any stutter issues as some suggest after a few hours. Its perfect!

On a side note my brother just got a nexus 4 and the first thing I had him do was unlock, root and purchase f.Ku! Many thanks again! Continue the great work.
[Nexus 4 Original Android Development] lorolouis:
2 things

Just 2-3 things remain unconfirmed 120% regarding 151 :)

- Overall battery life (it needs some time, of course) ?

- Occasional data/ radio drops - are they completely gone since some of r143+ on all radios, what is/was causing them ?

- Issues like one 2-3 posts up - I think and hope it was a co-incidence to happen on r151 exactly ... but needs close follow-up

The rest is perfect!

Thanks Franco !!!

Take some rest, man. :cool:: This work of improvement never ends.
[Nexus 4 Original Android Development] defffizz:
Just to confirm, everything is great with latest nightly, with default settings in fku it's smooth and battery friendly. I'm sticking with r151 :)
[Nexus 4 Original Android Development] RandomDude:
Hi Franco - can you please provide any insight on why it appears the first touch on the lock screen after waking is not recognised?

I'm now on r151 and the bug is still present.
[Nexus 4 Original Android Development] tacosrdelicioso:
Bro, nobody has this issue. Dirty flash your ROM then reflash kernel then if it still exists your ROM sucks
[Nexus 4 Original Android Development] trailblazerz11:
Lockscreen on wake quite fast for me and no lag lately, though I do experience the status bar coming down issue every so often. Think Franco mentioned it as a touchscreen driver issue.
[Nexus 4 Original Android Development] 3dupunk:
I've tried to find differences in battery time through keeping records of usage throughout Franco's kernels builds and honestly they seem not to fluctuate all that much. There was one though, 140-something that literally sucked the life out of my phone at record breaking speeds but other than that it's been pretty consistent at least for me.

151 does seem pretty sweet, less laggy even when under-clocked....sadly, I'm not impressed, I've come to expect that from a Franco kernel. I find myself thinking at times while going through this thread that "it must suck to be Franco". think about it, we're never satisfied and we expect SO much....all jokes aside, I can't thank you enough man!
[Nexus 4 Original Android Development] RandomDude:
At least one other person notices this too. It is noticed especially on the pin unlock screen, where the first tap on a number is not recognised. I thought it was worth asking the question.
[Nexus 4 Original Android Development] rmead01:
I wonder how many people with signal issues are on the new modem. I was on it and kept having issues. Flashed back to .48 and it's much smoother newer doesn't slays mean better
[Nexus 4 Original Android Development] Cuzz1369:
New radio is a godsend for me. I have a much better signal here at work. No drops at all.

Carbonized and francofied N4
[Nexus 4 Original Android Development] rmead01:
Yeah that's what I thought at first. Then it was taking forever to make a data connection to update numerous different apps. Back to .48 and I can connect right away.
[Nexus 4 Original Android Development] iamhacked:
I think there's keyboard lag again in the new build. I'm using Swype
[Nexus 4 Original Android Development] jarjar124:
No lag here
[Nexus 4 Original Android Development] 3r1k:
Had similar issues... Using M2 now... Much better
[Nexus 4 Original Android Development] Mo'HAWK:
There is no lag for me when using Swype. Do you use gesture or not.
[Nexus 4 Original Android Development] ChongoDroid:
I dunno what you guys are doing but 151 is great for me. I've been dirty flashing mods and all sorts of stuff and haven't run into half these problems.

1.566 max 486min deadline, westwood. Running on primerunner
[Nexus 4 Original Android Development] kyokeun1234:
If you're talking about the lag when tapping, it was always there. Even with other kernels or older version of Franco kernel, tapping will be laggy until the dev actually fixes it. That said, not experiencing any notifiable lag with Swype, Kii, and Swiftkey
[Nexus 4 Original Android Development] Luigiesin:
After an hour or so of using 151 I started getting a lot of micro stutters again.. Not as much as 150 but definitely. I went back to 146 and everything is smooth again.

I don't know if there's an issue still with cpu1.. But seems similar to the issue we had on 150.. Just not as much.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r146-Linaro

T-Mobile
[Nexus 4 Original Android Development] admiez:
Had a random reboot earlier today when the phone was sitting idle. Not concerned about it since I had set for the day the governor to Performance, max freq. to 1728MHz and Thermal threshold at 55-60C. Phone always felt cool when in use, but logs show there was thermal throttling at some point. It's not clear why it rebooted. I see 'Early Suspend stopping Hotplug work...', 'Last boot reason: watchdog'.

Here's the last_kmsg in case there is something else of interest: https://www.dropbox.com/s/ryzm8vm2u7taodv/last_kmsg-20130606.txt

Note: this was in test r1111.
[Nexus 4 Original Android Development] hern1989:
I also had issues with the new modem. It wouldnt let me call. And when i could call it would drop right after.
[Nexus 4 Original Android Development] jarjar124:
I'm almost there Franco :)
[Nexus 4 Original Android Development] Traxex_:
I'm experiencing some micro stuttering after some uptime too.

Hope you can fix it in the next release.
[Nexus 4 Original Android Development] ÜBER™:
Still quite a ways away from my score on top there. :p
[Nexus 4 Original Android Development] realtalker:
Such a wonderful game :good:
[Nexus 4 Original Android Development] FaLCoN.007:
No wifi turn on after flashing kernel, anyone know how I can fix this? :(

Thanks!
[Nexus 4 Original Android Development] ceejay83:
Did you flash the one with prima drivers before?
[Nexus 4 Original Android Development] Ballastatuz:
It is a little less bright. I think it helps save a little battery and makes it not as intense. I think sometimes things may have looked washed out because the screen is so bright.
[Nexus 4 Original Android Development] wobbu:
I guess that means no Faux's gamma control?
[Nexus 4 Original Android Development] lazer155:
With the stock kernel my record screen on time was 4 hours 32 minutes (average is between 3.5-4.5 hours). That was with all the stock gps, syncing, autobrightness, ect. settings. I had data off and was using wifi the whole time. I was mainly browsing with chrome. I didn't play any games or watch any videos. Signal strength is one big factor.

I haven't had a chance to test the screen on time with franco's kernel since I just installed it and I am currently trying to drain it.
[Nexus 4 Original Android Development] co0kie:
Thanks for editing my post but the rest of the sentence was "and i'm still clueless as to..." so there's your answer. Sorry for not being as smart as you are.

3G data vs. WiFi makes a huge difference so i guess i'm on ~par with your results. Those who post 8h of screen on are basically using their phone to look at a "screen on" phone without touching it so they can say they got 8 hours :P

Do you calibrate after each kernel flash?
[Nexus 4 Original Android Development] franciscofranco:
Like a boss.
[Nexus 4 Original Android Development] lazer155:
:good: It has amazing battery life so far. Great work!

That makes a lot more sense now. I couldn't figure out how they were actually using it and getting those screen on times.

I didn't know I was supposed to calibrate it after each kernel flash. How do I do that?
[Nexus 4 Original Android Development] JNewms:
I know a lot of you guys want to see certain things. Here's the thing, Franco is taking the kernel where he wants to go, if you want the features of another kernel flash that one. Franco had stated that he isn't adding gamma, or uv for that matter until he's satisfied with where he's at with the kernel. This should really be all bug reports and lst/kmsg stuff. The quicker we can help him make this stable the quicker he will add his favored bells and whistles.

Sent from a Paranoid N4
[Nexus 4 Original Android Development] syncopy:
Gamma control was Supercurio's work, wasn't it?

Correct me if I'm wrong.
[Nexus 4 Original Android Development] ayamary:
faux didn't invent gamma so maybe we will get it some time
[Nexus 4 Original Android Development] benrees21:
Gonna try this, let you know what I think soon.

Because I'm a Nexus b!tch and I like to run the latest source and binaries!!
[Nexus 4 Original Android Development] TheByteSmasher:
All calibrate means is after the phone is fully charged, leave it charging about 20 more minutes, reboot to custom recovery, wipe battery stats, turn off, unplug and reboot. It won't change battery life but it will "calibrate" the battery meter by resetting it so maybe the percentage will be more accurate and the "time on X" lists will be more precise.
[Nexus 4 Original Android Development] evie12604:
No need to calibrate at all.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Franco r22 is just icing on the cake it just gets better and better everyday. Thank you:thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] benrees21:
Seems cool so far. I'm a loyal Trinity user but I'm just trying everything lately to see what's what, brings back memory's of my Nexus S days when I couldn't settle and flashed something different everyday. God I loved that phone, it was my first Nexus and I still wish I had it today.

Because I'm a Nexus b!tch and I like to run the latest source and binaries!! AOSPA!
[Nexus 4 Original Android Development] cpom1:
Hey Franco which ROM are you running?

Sent from my Nexus 4
[Nexus 4 Original Android Development] syncopy:
MiNCO!

Sent from my Nexus 4
[Nexus 4 Original Android Development] JNewms:
I feel you, this is my first Nexus, and it's almost overwhelming to have all of these choices. But, I'd heard of Franco long before getting the N4 so naturally I gravitated toward his kernel, and after reading the man's thoughts on the process I don't think I'll go to another kernel. I feel that Franco is a legit tech genius. I only hope that once I get through school I'm half as good as he is.

Sent from a Paranoid N4
[Nexus 4 Original Android Development] benrees21:
Seriously, when I think of the Nexus S I get a rush Lol. You never forget your first Nexus. I so wanna buy another one Lol.

Because I'm a Nexus b!tch and I like to run the latest source and binaries!! AOSPA!
[Nexus 4 Original Android Development] Vanhoud:
He's a stock ROM kinda guy. I assume he keeps it stock (he's said so in the past) because he tests his kernels on stock because it's a baseline

Sent from my Franco'd Nexus 4
[Nexus 4 Original Android Development] djemgee:
I'm just going to say that since I've had my n4 (nov23) I've tried most of the popular ROMs with a select few kernels (trinity, franco, etc. But the best pair up for speed and ridiculous battery life is this latest code fire ROM + Franco #20 by far. If you get the chance try these 2 together I promise you you'll be amazed!!!
[Nexus 4 Original Android Development] FaLCoN.007:
Yes, r147 + prima drivers.
[Nexus 4 Original Android Development] ceejay83:
You probably could have found the answer if you searched, a lot of people ask this. Flash your rom again
[Nexus 4 Original Android Development] Tzfardaya:
query about the fku app

So, what's the issue with the checksum verification?

I've noticed that I'm not the only one on this site (or with the app, from the reviews on the play store) who is having bad checksums nearly every time I try to update through the app.

Is there anywhere else from franco's site or here to grab the md5 checksums for me to verify my download manually?
[Nexus 4 Original Android Development] franciscofranco:
How can you have lag being a dual core boosted to 1188MHz when typing? Sorry I dont see how can that be related to the Kernel.

Need more info... Whats happening exactly?

I also hope to get better info, what happens? Freq gets stuck, cpu1 doesnt kick in...?

1- no

2- no

3- no -.-
[Nexus 4 Original Android Development] ChongoDroid:
That is correct, I experience none of these just stating that it's what has been reported as of lately (last few pages) and that its not hard to read through it.

Whether they're actually bugs or just noobs reporting "user error" issues, that is for you and I (the more experienced users who frequent this thread) to determine and solve.
[Nexus 4 Original Android Development] franciscofranco:
Oh yes, I misunderstood your post, sorry!
[Nexus 4 Original Android Development] Luigiesin:
Same problem we had with 150 and the test boots. Only lighter.. When swapping through my home screen I still see a lot of dropped frames, micro stutters.. Also with apps like Instagram... I dint have problems with that one... Neither with Currents... I still see those stutters a lot.

I know you changed the code, simplified it... But with 146 everything is super smooth and the battery is great.

Don't know how much info I can give you since everything works fine... Just that the whole UI is not as fluid as it used to be.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r146-Linaro

T-Mobile
[Nexus 4 Original Android Development] ChongoDroid:
Haha never apologize brother, I'm just happy that we have a kernel dev as patient as you (without being boring) and someone who is willing to experiment and that doesn't bull**** users about frequency tables.
[Nexus 4 Original Android Development] JNewms:
I flashed 151 this morning right after it was pushed. I spent a couple hours doing some surfing between Google+, XDA(via tapatalk), and android circle jerk(via reddit sync). Topped off my battery and went to work. Idle drain has been really good. I jumped on here and there to check messages and stuff throughout my shift. A friend of mine was texting me on hangouts while I was working. I had thought he was busy and had stopped the convo, but then about 12 minutes ago I received a message from him with a time stamp of 9:24 (eastern time, U.S.).

Sorry if I rambled, I was trying to give my full experience. I haven't seen any lag, but haven't pushed it yet. I'm curious about the delayed notification with hangouts though. Also, I'm very pleased with the idle drain so far.
[Nexus 4 Original Android Development] trailblazerz11:
The problem with 150 only occurred after several hours with core1 not onlining. It appears fixed in 151 so far, core1 onlines fine. I have no lag now or in 150 when the bug didn't occur, very smooth including my home screen and Instagram. Only lag is on apps that were laggy to begin with.

Really feels like Milestone 3, from what I remember of past experience smoothest its been on franco (well... besides the quad core testing ^^)
[Nexus 4 Original Android Development] FaLCoN.007:
I managed to solve my problem, I apologize for my lack of information!
[Nexus 4 Original Android Development] zellleonhart:
I am amazed with r151, even the usually laggy xda tapatalk is very smooth in scrolling now. M3 candidate :D

Beamed from my Paranoid HALO r151 Nexus⁴
[Nexus 4 Original Android Development] JNewms:
You should try the beta of tapatalk 4. It's a lot smoother than any other tapatalk, and has the new Google UI guidelines.

Sorry for OT, but it's a good one to try.
[Nexus 4 Original Android Development] ChongoDroid:
Continuing with the OT but it's missing the "see all posts by" feature which is kinda weird that they left that one out.
[Nexus 4 Original Android Development] zellleonhart:
I have it installed, but I really prefer the feeling of using XDA version, especially it display posts on full width. Tapatalk beta has an awkward empty space beside the posts...

Beamed from my Paranoid HALO r151 Nexus⁴
[Nexus 4 Original Android Development] thebryceee:
Check your inbox
[Nexus 4 Original Android Development] JNewms:
Good point, now that you mention it, it's missing from tapatalk HD as well. I was using that on my 10. It's the same dev for both of them. I wonder if he'd change that, it's really useful to be able to do that.
[Nexus 4 Original Android Development] Vangelis13:
Hate it when they change everything in an app and on top of that remove good functions. Just fix the code da#n it..!
[Nexus 4 Original Android Development] leets4uc3:
Thanks Ima try it now
[Nexus 4 Original Android Development] thebryceee:
Search within threads is missing from Tapatalk 4
[Nexus 4 Original Android Development] Redneck Trash:
Haven't had any lag on r151. Cpu1/2/3 go offline on conservative. Battery life remains good. Waiting for your next ideas to be implemented.
[Nexus 4 Original Android Development] ChongoDroid:
Yeah I recently had a bit of a "discussion" with their dev.. I had asked him about it and gotten a slightly snarky response.

Nobody out-snarks me... nobody.

Well I don't know if they fully rebuilt it from scratch or what, but I hope they don't forget about that feature... and by forget I mean ignore the thousands of bug reports they'll be getting if they continue to ignore me :)

anyways back on topic ;)
[Nexus 4 Original Android Development] emam damon:
r151 is awesome in terms of smoothness and battery life.

tanx a lot sir franco.:laugh:
[Nexus 4 Original Android Development] ChongoDroid:
Seems to be a current theme of making a "clean UI" aka axing half the features and having lots of empty space... *cough*hangouts*cough* ...

I think even Google needs to take a look at FKU as how their guidelines apply and how they can be used. (Like use of themes, pull out tabs, beta in playstore... aka everything included with android app development right now lol)
[Nexus 4 Original Android Development] republitarian:
So here is my first battery run from 100% on r151. Still have 13% left...full brightness/WiFi!
[Nexus 4 Original Android Development] JNewms:
I wish I would have seen this a few minutes earlier. I just emailed the developer through play and asked if there was a forum for bug reports and such. Lol, I hope he doesn't snark me too!