yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] ArclightX:
Oh yeah?

Well I'll go a little further and mention that my wife is complaining about feeling unfulfilled sexually, and you better believe I place the blame squarely on Francisco's doorstep. Specifically with his r148 update.

What I want to know is what does Messere Franco intend to do to rectify my wife's unfulfilled sexual needs? >:(
[Nexus 4 Original Android Development] Net.silb:
Default first level is 60 or 70?

In the code you pushed its 70 and in the r999 after clearing app data and rebooting its 60...
[Nexus 4 Original Android Development] Polv89:
Why in r148 isn't possible to activate wifi?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] Arstoien:
On the #999 I'm experiencing noticeable animation lag when changing home screens, app drawer screens, and when scrolling through the recently contacted people in the Phone app. I changed to 148 and it's gone. Switched back to the test version and after some time and normal usage it starts stuttering.

Sent from my Nexus 4
[Nexus 4 Original Android Development] bokagavrilov:
coz probably you are coming from some other kernel that messed up your wifi ( for example if u come from the one with prima driver you have to flash the revert and then this )
[Nexus 4 Original Android Development] Polv89:
From angela kernel..where can i find the revert? On previous kernel thread? Thanks

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] atub:
Same here...
[Nexus 4 Original Android Development] trailblazerz11:
New code looks good, quite simple actually. Felt some lag to start but just had to turn on input boost and it is dreamy smooth!!!!! Stays on single/dual core on touch most of the time too just as I would like. Rarely bursts momentarily to quad core when seemingly not needed like the old Hotplug would.

I don't game much so haven't tested that but this really is perfect for my usage. I'd expect some battery gain for staying single/dual most of the time now and no needless switching of core2&3

Thanks Franco :)
[Nexus 4 Original Android Development] Net.silb:
Same here as well now...
[Nexus 4 Original Android Development] Cuzz1369:
Should be one there. You can always dirty flash your ROM and then flash Franco again.

Carbonized N4
[Nexus 4 Original Android Development] LaboDJ:
After rebooting it's always 0 here... Franco see here: http://xdaforums.com/showpost.php?p=42237977&postcount=94
[Nexus 4 Original Android Development] drawde40599:
Exact Same here after using stock settings, first time ive ever felt a studder with any build i didn't know what was going on :P back on 148 now, but what u described sums it up
[Nexus 4 Original Android Development] monkey hung:
Battery life has been amazing for me. YouTube, Vine, Reddit, heavy gaming for 45 minutes and 20 hours on time with 4 hours and 30 minutes screen time on the latest PA with r148
[Nexus 4 Original Android Development] Pure Drive GT:
Headset Volume Control Buttons

Hi [MENTION=3292224]franciscofranco[/MENTION], I just bought a Headset for my nexus 4 and noticed that the Volume Buttons do not work on the little controller with the mic on it. The center button luckily works but it would be nice if the other two would too. I then found out that these are supposed to work on Apple products.... I would like to know if there is any way to get this working with a "moded" kernel/enhancement/app/hack/tweak whatever it may be.

Best regards and thanks in advance!
[Nexus 4 Original Android Development] Joshr:
Been getting signal drops pretty regularly in a while with r147 and now r148 too. Completely lose signal and it goes to a black triangle. Also, I'm getting duplicate sms messages from several contacts since I've flashed r147 and r148, not sure if it's related.

Going to try out 999 now hopefully that fixes it.

Does it matter what radio you're on? I've got the 48 version and I see there is a newer version available now.
[Nexus 4 Original Android Development] Cuzz1369:
That's an android issue. Not a kernel issue. Needs to be taken up with google

Carbonized N4
[Nexus 4 Original Android Development] trailblazerz11:
Think he just accidentally removed line 380 in the commit.
[Nexus 4 Original Android Development] LaboDJ:
Yup! Error found! :good:
[Nexus 4 Original Android Development] Dimatchka:
I'am also having my radio cycle through drop signals, lost 50% battery in 8 hours due to RILJ wake lock. Im on 178 and the phone is in deep sleep 16% of the time.
[Nexus 4 Original Android Development] franciscofranco:
Eheh probably that yeah ;)
[Nexus 4 Original Android Development] Beremus:
Definitly having kind of lag in UI. Scrolling isn't as smooth has it used to be. (I'm on r999).
[Nexus 4 Original Android Development] franciscofranco:
Ok I fixed the derp, test here:
[Nexus 4 Original Android Development] Savant:
Awesome, thanks Franco.
[Nexus 4 Original Android Development] iboj007:
Noticed this as well since I went from M2 to the nightlies around 145.

Any solution or update?
[Nexus 4 Original Android Development] Savant:
Trolling because apparently on XDA that's where they spawn.
[Nexus 4 Original Android Development] ÜBER™:
Flashable for said kernel.
[Nexus 4 Original Android Development] Talvathir:
Le smooove extraordinare :cool:
[Nexus 4 Original Android Development] Mo'HAWK:
I was a little too late and already flashed the boot but we'll take that zip you made there. Thanks!
[Nexus 4 Original Android Development] ArclightX:
None of you have a sense of humor. Must be something in the water....
[Nexus 4 Original Android Development] pikachukaki:
Im sorry but at 1st pic where are all others in hotplug settings and on 2nd pic what is the boost_touch?
[Nexus 4 Original Android Development] kaiser_tytnii:
Whatever you did, this is the smoothest experience ever:eek: THANKS!

EDIT: seems like battery life is taking a hit though
[Nexus 4 Original Android Development] italia0101:
+1
[Nexus 4 Original Android Development] Net.silb:
Actually seems to have been fixed in the latest r999 Franco posted on the previous page. No lag or stutters, buttery smooth!
[Nexus 4 Original Android Development] italia0101:
Oh thanks I missed that!
[Nexus 4 Original Android Development] schmitzekater:
I was facing the Sim-unlock problem once more. Had to enter the code like every two minutes.

R148 on RasSaber,no UV, no Oc, .54 modem.

Last time I had this was on r146, same settings.

Is there a log somewhere I could provide? There was no last_kmsg since there was no boot.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] italia0101:
Is that normal fire the latest r999 , or do I need to reflssh
[Nexus 4 Original Android Development] resynx:
Seems to be normal.
[Nexus 4 Original Android Development] italia0101:
Also , would love that feature ... badly want it lol
[Nexus 4 Original Android Development] franciscofranco:
Not at all, my battery is considerably better along with much cooler temperature and I've been flashing hundreds of boot.imgs so my battery reporting is all ****ed up. I drained it all, full charger and boom, everything is goodz :)
[Nexus 4 Original Android Development] franciscofranco:
They are gone on r999, soon to be r150. Don't enable that input_boost, not needed and it will be removed soon too because its obsolete.
[Nexus 4 Original Android Development] Net.silb:
What do you think of minimum two cores online all the time?

If no, why?
[Nexus 4 Original Android Development] blankit:
I'm on latest pa with Franco's milestone 2 and my battery life is horrible doesn't even last me 3 hours with just looking at pictures and browsing the web
[Nexus 4 Original Android Development] lordvj:
cores don't go offline on the latest 999.. phone is sitting idle with all cores on :|
[Nexus 4 Original Android Development] Beremus:
Monitor your wakelocks. It's not a kernel problem.
[Nexus 4 Original Android Development] blankit:
So why are my cores on milestone 2 always active even when idle?
[Nexus 4 Original Android Development] Mauijpm:
Maybe I am looking at this wrong, but that doesn't seem to be my experience.
[Nexus 4 Original Android Development] kaiser_tytnii:
Sorry, r999 was definitely better compared to nightly (r147/148); what i was comparing to was the r999 from last night, in terms of on-screen battery drain... no actual measure, just noticed that the number dropped a bit faster than the prior r999

will do more observation then report

---------- Post added at 01:30 PM ---------- Previous post was at 01:28 PM ----------

it does go offline, based on my experience too
[Nexus 4 Original Android Development] Beremus:
Oh well, no wonder why your battery sucks. Your device doesn't stay in deep sleep. Did you installed an app before the problems started? Happened to me a while ago and it was because I installed Engadget App. I removed it and problem was solved.
[Nexus 4 Original Android Development] kaiser_tytnii:
they do go offline, based on my experience too
[Nexus 4 Original Android Development] Chintao:
Same problem here!
[Nexus 4 Original Android Development] lordvj:
Thats strange, none of my cores went offline. Flashed 146 now everything is fine again
[Nexus 4 Original Android Development] pikachukaki:
Its so hard to check your wakelocks first and then commenting on why your cores don't go idle!!its more helpful when you do it and then comment!!!
[Nexus 4 Original Android Development] franciscofranco:
Of course cores go offline, I would be making a dumb picture of myself if I released Hotplug code which didn't offline cores. I tested in 3 different Nexus 4, all were fine.
[Nexus 4 Original Android Development] italia0101:
Lol that would be kinda funny , "hi guys, New and amazing hotplug code" .......... Franco it doesn't offline cores ... Lol
[Nexus 4 Original Android Development] PetritH:
working fine here too, cores going offline as they should, waiting for r150 :)
[Nexus 4 Original Android Development] immunityx:
Nope no task killers I save my profile and load it... Back button then use phone like normal. I screen off at times I notice the colors go back to default even though the settings are correct in the RGB panel. I have to adjust the color again or load up my profile to get it back.
[Nexus 4 Original Android Development] drawde40599:
http://xdaforums.com/showthread.php?t=2002782
[Nexus 4 Original Android Development] franciscofranco:
Alrighty, thanks!
[Nexus 4 Original Android Development] franciscofranco:
The fix is meant to reduce the excessive wakelock, not remove it.

Yes I can add that I/O scheduler for testing purposes.
[Nexus 4 Original Android Development] cpom1:
Awesome a** Dev. Thanks.

Sent from my Nexus 4
[Nexus 4 Original Android Development] CMNein:
The reduction in msm_hsic is phenomenal. My battery life was already nearing excellent, but I was slightly annoyed by this wakelock since I spend 95% of my time connected to a wifi network. Typical deep sleep through the night, sync on, on wifi was ~87% prior to the patch, it's now 97% which is what I'd become accustomed to on my GN.

Adds up to more screen on time the next day when I start using my phone.
[Nexus 4 Original Android Development] jundii:
Settings? ROM? Whats syncing and not syncing? What was done during screen on time? If you're going to post a screenshot of awesome battery results post the settings and dependent data so we don't have to ask :)

But besides that congrats and nice results!

Sent from my Nexus 4
[Nexus 4 Original Android Development] Luigiesin:
Hey Franco... What about input boost? It's grayed out.

Thanks
[Nexus 4 Original Android Development] Godaemon:
Hey guys how the hell do u manage this 7+ screen on time???Maybe something wrong with h me ? Seriously I'm starting to worry about my device!just for the record current setup is codefirex ROM + r22...thanks :)
[Nexus 4 Original Android Development] franciscofranco:
Its greyed out because its not available in the kernel.
[Nexus 4 Original Android Development] Hrithan2020:
The 7+ screen time is the exception rather than the rule even witn franco.Kernel. Most likely he has disabled quite a few things plus has good mobile connection/range always and is probably on wifi . Majority of the posts here are reporting 3 to 4.5/5 hours of screen on time. Plus he might be using applications that don't consume much cpu. I would be very surprised if he is getting 7+ screen time consistently.

And yes, next time if anyone is posting/showing off battery stats, it would be great if they mention their setup.
[Nexus 4 Original Android Development] jhericurls:
Can we also have a 192Mhz slot for testing purposes too ;)
[Nexus 4 Original Android Development] franciscofranco:
Nope, nothing lower than 384MHz will come to this kernel.
[Nexus 4 Original Android Development] drawde40599:
Oh god , here we go agn
[Nexus 4 Original Android Development] SchmilK:
Not sure if its the kernel that controls this but since flashing r22 when I reboot the battery stats reset.

Ideas?
[Nexus 4 Original Android Development] superbobup:
Don't even worry about that. It doesn't "reset" it just starts showing it from the value at boot. It usually does this when you reboot the phone and your current battery level is > x% where x is usually around 90
[Nexus 4 Original Android Development] :
May i ask why you think it's a bad idea? I have never heard downsides of it but i'd like to hear them if there are any.
[Nexus 4 Original Android Development] elliot.newnham:
Qualcoms developers are really smart. I wouldn't go far off the beaten path. Probably a good compromise in voltage and speed
[Nexus 4 Original Android Development] Simer03:
Can someone elaborate what ROW does exactly? And how it benefits the kernel/phone?

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] ObihoernchenDE:
Yes probably.

Same situation on S2. 200MHz was default and some kernels support 100 as well. Measurements show that 100 consumes more power because difference in voltage was too less.
[Nexus 4 Original Android Development] admiez:
Why do I still have all this?? No wonder I couldn't make sense of much until other users posted their screenshot. I even uninstalled and reinstalled the app after flashing r999. And have cleared its data a few times.
[Nexus 4 Original Android Development] kara mustafa:
Clear data and then flash a kernel, clearing data after flash is pointless in my case.
[Nexus 4 Original Android Development] blankit:
So I installed betterbatterystats and have no wake locks ....I will drain the battery and filly charge it and see if my battery life improves
[Nexus 4 Original Android Development] Savant:
I am kinda shocked how much patience Franco has with all these irrelevant questions and answers.
[Nexus 4 Original Android Development] admiez:
Thanks. I was just doing that. Flashed the updated r999 using the clear data on reboot option. Now it is ok. I was even missing the touch boost option. That could explain the performance issues.
[Nexus 4 Original Android Development] ChongoDroid:
This setup is screaming, ;)
[Nexus 4 Original Android Development] blankit:
Anyone know what that is?
[Nexus 4 Original Android Development] rmead01:
normal, that's what that is. Try monitoring over 5 hours and not 13 min
[Nexus 4 Original Android Development] pikachukaki:
The radiointerface i think is the RILs do you have poor signal?
[Nexus 4 Original Android Development] franciscofranco:
Its your device being a smartphone and being turned on.
[Nexus 4 Original Android Development] thebryceee:
He has his super saiyen moments
[Nexus 4 Original Android Development] saramon:
Any chance this can be ported to the sprint lgog, were in desperate need of great kernels
[Nexus 4 Original Android Development] ÜBER™:
Sure

Step one

Sell LG OG

Step two

Buy Nexus 4

Step three

Do the happy dance.

Seriously though... Not very probable, Franco only works on Nexus devices.
[Nexus 4 Original Android Development] Savant:
:p
[Nexus 4 Original Android Development] Net.silb:
[MENTION=3292224]franciscofranco[/MENTION]

I'm on the latest r999, in the beggining everything was smooth but it seems that after a while of using it, lagging and stuttering begin to happen while scrolling through menus, web pages, homescreens and the app drawer... Almost feels like a memory leak... Is that possible?

Anyways, something is wrong, just reporting.
[Nexus 4 Original Android Development] konfuzed:
i second this.. even [MENTION=1528666]151[/MENTION]2 im seeing some stutter while browsing this thread. gonna clear app and reflash bc im itching to flash the illusive r150 lol
[Nexus 4 Original Android Development] franciscofranco:
Hmm... I've been using since yesterday without a problem. Is the second core being onlined on boost? Is its frequency being boosted on touch? Thats pretty weird if you ask me.
[Nexus 4 Original Android Development] 75markus:
but isn´t it recommended to turn it off for best battery life ?? :p:p
[Nexus 4 Original Android Development] franciscofranco:
Yes, that is a requirement.
[Nexus 4 Original Android Development] Net.silb:
For some reason the second core is not being onlined on touch anymore... Very weird... It was working before...
[Nexus 4 Original Android Development] franciscofranco:
Is the cpu0 frequency stuck? I think I know what it is, I think its one of my vars that its an int and after a while the number thats being assigned is too big and it doesn't fit the int anymore. I just changed to a long, hoping thats the problem. Any further info would be great!
[Nexus 4 Original Android Development] drawde40599:
This was happening on first 999 to me, 2nd seems good so far
[Nexus 4 Original Android Development] italia0101:
You sure your on the latest one ? There was one a few hours ago that fixed it for me
[Nexus 4 Original Android Development] Net.silb:
cpu0 frequency is not stuck, its behaving normally. Tell me what else I should check and I'll try to give you whatever information you want.

---------- Post added at 08:58 PM ---------- Previous post was at 08:56 PM ----------

And yes, I'm sure.
[Nexus 4 Original Android Development] franciscofranco:
Its probably the int/long thing. Will release r150 after dinner!
[Nexus 4 Original Android Development] Net.silb:
Alright, glad I can help!

I'm anyways going to sleep now and I'm planning on waking up to a r150 notification in my status bar! ;)

Bon appetit! :)
[Nexus 4 Original Android Development] admiez:
Same issue here. No extra core on touch/swipe with touch_boost enabled or not. In fact, got more stutter with it on. Core 0 scaling frequencies just fine, not stuck. When I do see other cores come online it is almost always all of them at the same time. I probably need to do some tweaking.
[Nexus 4 Original Android Development] gpvecchi:
Perhaps a little late, but... I had problems with 148 build: everything worked fine until a reboot. After it I had my FKU settings reset to default by themselves and no connection to Google servers (grey bars). No way to fix it until I reflashed 147. Everything good. Oh, I always flash kernels, reset settings from Applications, then from FKU, then reboot.

Modem .54 on Vodafone Italy.
[Nexus 4 Original Android Development] defffizz:
Same thing here, everything stutters, with first and second r999, app drawer, scrolling, pretty much everything. I don't go into changing settings in fku, leave them default. Will wait for r150 to see if things become better, if not, for the first time I'm reverting to stock pa kernel
[Nexus 4 Original Android Development] noneabove:
Omg why Franco eat so slow QQ... :P
[Nexus 4 Original Android Development] admiez:
Funny. Let the guy eat in peace..
[Nexus 4 Original Android Development] thebryceee:
...or you could revert to a previous build of this kernel. I can't pry myself away from r146 D:
[Nexus 4 Original Android Development] defffizz:
Well that might be better idea :)
[Nexus 4 Original Android Development] franciscofranco:
r150:

* New 100% re-coded Hotplug algorithm

Btw for users on the latest r999, this r150 is different - they are NOT the same.
[Nexus 4 Original Android Development] Saiger:
woho

thanks!
[Nexus 4 Original Android Development] cAase:
I cant belive that XDA was able to be run this smoothly!
[Nexus 4 Original Android Development] bokagavrilov:
Feels speedy xD thanks franco
[Nexus 4 Original Android Development] rockafellor:
Is it normal that my fku has just a value for high usage in the hotplug settings?

Using r150

Sent from my francofied paranoid Nexus 4 with Tapatalk 2
[Nexus 4 Original Android Development] vjales:
Server is being hammered. :( f.K could be less popular... ahhaah just kidding franco, I'll keep try downloading :laugh:
[Nexus 4 Original Android Development] Testraindrop:
Yes.
[Nexus 4 Original Android Development] defffizz:
Flashed r150, no stuttering like with r999.. So far so good, everything is smooth :)
[Nexus 4 Original Android Development] kara mustafa:
Is there now only 1 option for hotplug - highload ?
[Nexus 4 Original Android Development] admiez:
Should the Governor control settings include a toggle for input_boost or was it taken out?
[Nexus 4 Original Android Development] CyberDonky:
Where do you see the option highload in hotplug? :o
[Nexus 4 Original Android Development] admiez:
Yes. Answered just above your post.

---------- Post added at 05:28 PM ---------- Previous post was at 05:27 PM ----------

It's the first option followed by Suspend frequency and Cores online on touch input.
[Nexus 4 Original Android Development] nexusmaniac:
Wow r150 is even smoother than r999 I didn't think that would be possible! well done Franco, great work as normal
[Nexus 4 Original Android Development] CyberDonky:
Ah I see what you mean haha! :) Thanks.

I didn't edit things on the hotplug so I will not recognize any performance i guess
[Nexus 4 Original Android Development] italia0101:
R150 ............. smooth
[Nexus 4 Original Android Development] aventu:
You made it Franco, I have nothing left to complain about
[Nexus 4 Original Android Development] franciscofranco:
Taken out, its obsolete, I coded my own solution for this new Hotplug algorithm. Code is on github. I'd rather code stuff as I don't always agree with Google's code.
[Nexus 4 Original Android Development] xdviper:
This is it man, from now on, I'm only buying the phones you plan on working on. :p
[Nexus 4 Original Android Development] Chintao:
Flashed r150 and have the same problem i had with 999. All 4 cores are always online, watching system monitor and the Cores are at 1-3% load but don't turn off. With 148 i had no problems checked it 5 times Wirth flashing back and forth. What do i wrong?
[Nexus 4 Original Android Development] franciscofranco:
What value do you have on the First level threshold? Use my app or if you don't have it do cat /sys/class/misc/mako_hotplug_control/first_level
[Nexus 4 Original Android Development] ciprianruse88:
Try to unistall your kernel control app and reflash franco again.
[Nexus 4 Original Android Development] Cuzz1369:
Got a sweet surprise. After flashing 150 got a notification for the new gmail app. Sweet. 2 new toys.

Carbonized N4
[Nexus 4 Original Android Development] TheDarkDefender:
Its funny how we base our phone purchases on xda support. For me it was cyanogen mod and Franco's kernel. I'd keep checking the forums constantly for threads to pop up, before I confirmed my purchase. Lol. What to say, Android has changed our lives. :)

Sent from my Nexus⁴
[Nexus 4 Original Android Development] rmead01:
Just wanted to say, when I was using the latest r999 test I had the issue where the 2nd core wouldn't online with a touch. Updated to r150 and that issue has been fixed. In case anyone was looking for an update.
[Nexus 4 Original Android Development] bokagavrilov:
Just tested gaming with temple run 2 it lags still the 2core almost never gets in except when touching the screen
[Nexus 4 Original Android Development] Zlatan9.:
Yes I agree temple run 2 lags.

But when I touch my screen to swipe it stop lags for like 1/2 seconds because second core comes online
[Nexus 4 Original Android Development] Chintao:
70
[Nexus 4 Original Android Development] ki2luminati:
I just discovered that r150 lags like crazy in temple run 2. However if i change the governor to ondemand its smooth as hell. Any others experiencing this?