yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] neriamarillo:
Thing is that all the releases after r32, including r36 test image, my sensors don't work (auto rotate, GPS, etc) so I stick with r32.
[Nexus 5 Original Android Development] Boonyard:
So fku (paid), does not show you test builds in updater even once you've signed up through g+?
[Nexus 5 Original Android Development] PetritH:
Even if you are signed up it wont show test kernel builds, it will show FKU beta app updates.
[Nexus 5 Original Android Development] Boonyard:
Hmm... OK, that's a shame. So where do you get the test builds?!
[Nexus 5 Original Android Development] Tzfardaya:
seriously? That's messed up, what rom are you on?

no, the g+ beta channel is only for the fku beta builds,

the kernel is entirely separate, you can download and use them with release fku, beta fku, or no fku...

the test kernels are always in the links off the first post, boot images, in the test folder.
[Nexus 5 Original Android Development] franciscofranco:
Yeah you need the latest Kernel. You're using an encrypted phone?

Impossible, I just tested it with two different N5, all works as intended.
[Nexus 5 Original Android Development] franciscofranco:
Coincidence, there are no changes on any sensor code on r36. I use auto-rotate and GPS everyday...
[Nexus 5 Original Android Development] Boonyard:
Excellent, thanks.

Now I've found it, just need to work out how to download it as right now it's just taking me to a page of nonsense.
[Nexus 5 Original Android Development] Tzfardaya:
the nonsense is probably your browser trying to open the binary file, just right click and save as. :P
[Nexus 5 Original Android Development] PetritH:
Here
[Nexus 5 Original Android Development] Peanuts.:
Everything seems to working as it should now. I'm not sure whether it's because I had to clear FKU data or from the FKU beta update that was just pushed through.

Either way I very much appreciate your work & help. It's only 10am here and FKU beta has been updated 3 times? And respond so quickly on xda.

Your a machine!
[Nexus 5 Original Android Development] Tzfardaya:
[MENTION=2044650]Boonyard[/MENTION], were you able to get it from [MENTION=3750674]PetritH[/MENTION]'s link?
[Nexus 5 Original Android Development] Boonyard:
Eventually, yes. I was using uc browser and that wouldn't work, used chrome instead.
[Nexus 5 Original Android Development] Tzfardaya:
yeah, I still think the browser was trying to open the file instead of downloading it..
[Nexus 5 Original Android Development] dastinger:
Here in Portugal it's 11pm :p But, yeh, that doesn't make Franco less of a machine :D
[Nexus 5 Original Android Development] franciscofranco:
I've updated FKU beta about 5 times today :p
[Nexus 5 Original Android Development] Tzfardaya:
5 times today? I though it was 5 time in the last 10 minutes. :P
[Nexus 5 Original Android Development] valter09:
I got exellent battery results with almost 5h on screen. Thank you Franscisco
[Nexus 5 Original Android Development] amphi66:
Even with CPU restricted, won't running 4 cores generate more heat and trigger thermal throttle?
[Nexus 5 Original Android Development] Tzfardaya:
you never did say which rom you were on, but I would try a full (clean) flash of the rom and rebuild your device that way, shouldn't have any issues with your sensors then... I've used all the franco kernels/tests since before the 30's and any time I've had an issue with sensors, bootloops, or the like it was the rom messing up, not the kernel.. clean rebuild fixed everything... (except for those pesty ram leaks in 33-35...)
[Nexus 5 Original Android Development] franciscofranco:
Well... being capped to a lower max frequency will save more heat than running with 2 cores.
[Nexus 5 Original Android Development] Moh_Jay:
I've been running 4 cores (1.5ghz, -50 UV) and my phone temperature has been normal

Edit: it actually gets colder.
[Nexus 5 Original Android Development] neriamarillo:
It only happens on AOSP Roms. Stock and custom. On CM based ones everything works fine with their kernels. I DO NOT want to go that route lol.

Not that I know of. I've never touched that.

Yeah I know this is a very isolated issue with my phone and maybe 5 or 6 cases I've seen randomly on the interwebz but I know it works fine for everyone. I was trying to see what was going on in my phone (even though I went to stock and still the same) but I couldn't find the problem so I gave up and stuck with r32.

I always do clean flashes on any ROM I flash and I've flashed the stock image countless times. Since I don't have warranty I can't RMA and get it over with lol so I either find a solution to my problem or stick with r32 :) no way I'm flashing anything else than Franco.
[Nexus 5 Original Android Development] blueren:
Um.. unable to restore backed up kernel via the latest app. It just keeps spinning and nothing happens. No reboot, new kernel not applied.

Edit - my mistake. Wrong naming convention.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Peanuts.:
I must have missed the other 2 while I was asleep Lol. :eek:
[Nexus 5 Original Android Development] Circaflex:
then you have nothing to complain about
[Nexus 5 Original Android Development] Mnemoch:
Thanks Franco for the switch to disable the backlight changes (in the beta). Much too dark for me with it on so giving the option saved me!
[Nexus 5 Original Android Development] Tzfardaya:
Why no warranty, either way, lets really mess around with it. :P

how do you run clean flashes? via fastboot? or through a toolkit?
[Nexus 5 Original Android Development] linqdesires:
I'm getting all 4 cores running and stuck at 1574MHz.. latest test 36 and latest fku beta

min freq in fku is 1574Mhz
[Nexus 5 Original Android Development] neriamarillo:
Warranty.. Ugh I know now the importance.Got the phone from some poor soul on Craigslist. If I'm flashing a ROM or anything of the sort via TWRP. Otherwise I use adb for the stock images. Never have used a toolkit.

This is kind of a challenge for me because it forces me to learn deeper into the system. [emoji4]
[Nexus 5 Original Android Development] Tzfardaya:
good good, though not sure how you'd use adb to flash stock... :P adb requires an os to be loaded...

fastboot then... so you use the flash_all script to flash the stock images?
[Nexus 5 Original Android Development] neriamarillo:
I meant fastboot lol!!! But yes I use the flash_all script and it always goes fine.
[Nexus 5 Original Android Development] Tzfardaya:
and after you flash the stock image, cwm/twrp and root right away? then flash the kernel or do you boot once between each?
[Nexus 5 Original Android Development] neriamarillo:
I let it boot. After first boot I flash back to fastboot flash TWRP and then root. Then continue on with life. Is there a way to completely erase phone including root folders? Or does flashing the stock image take care of that?

BTW Franco if this too much OT I can take it to PM. You let me know.
[Nexus 5 Original Android Development] Tzfardaya:
using the flash all script erases everything on the phone, but, if you'd like to be sure, flash-all, boot, factory erase, then flash-all again.. :P redundant, but eveything will be wiped...
[Nexus 5 Original Android Development] neriamarillo:
This is what I did this last time (2 days ago) and nada. What u find weird is that on CM and CM based it works fine. I want to stick to aosp.
[Nexus 5 Original Android Development] Tzfardaya:
so, do all the sensors work right after running flash-all? before you install franco's kernel.
[Nexus 5 Original Android Development] neriamarillo:
Unfortunately they don't until I flash r32 then they work. [emoji20]
[Nexus 5 Original Android Development] slojko:
how do you enable 4 cores at all times?
[Nexus 5 Original Android Development] Tzfardaya:
they don't work on the stock kernel?!?!?!

I'd flash back to stock and talk to google about an rma anyways....
[Nexus 5 Original Android Development] neriamarillo:
It works fine on 4.4 but not on 4.4.2. I'll have to see if LG can take a look and fix it at a charge since I can't RMA with Google.
[Nexus 5 Original Android Development] psp9000333:
set hotplug threshold to 0
[Nexus 5 Original Android Development] Tzfardaya:
have you tried flashing 4.4 then stepping through the updates before installing franco?
[Nexus 5 Original Android Development] psp9000333:
so for the 4 cores running all the time do I under clock? because currently I'm running all 4 cores at maximum 2.4 GHz
[Nexus 5 Original Android Development] Tzfardaya:
I would, but then I underclock when not running all 4 cores...

If I recall, when franco first suggest we test it he also suggested UC to 1ghz...
[Nexus 5 Original Android Development] aow1980:
I think Francos test is to see if you can get better performance and battery by running all 4 cores at a lower frequency vs 2 cores with hotplugging at a higher frequency.

The best thing to do is test it various ways to see how it works for you. So far I'm liking the way it works.
[Nexus 5 Original Android Development] justibasa:
A little OT but thought you might like to see this as your in Portugal [MENTION=334712]francisco[/MENTION]. http://www.androidpolice.com/2014/0...ay-store-devices-in-8-new-european-countries/

Don't like me........BITE ME!!!
[Nexus 5 Original Android Development] franciscofranco:
About bloody time.
[Nexus 5 Original Android Development] WettbackMartyr:
Just wanted to take a moment and give a big thanks to our hero [MENTION=3292224]franciscofranco[/MENTION] for all his hard work, in particular over the past 24 hours with the fku beta. Working perfectly on my end now :thumbup: very grateful indeed
[Nexus 5 Original Android Development] Tzfardaya:
now you can order your nexus 5 direct and not need to have it routed through a friend from Germany.... :P
[Nexus 5 Original Android Development] dastinger:
AMAGAD! This is great news.
[Nexus 5 Original Android Development] Tzfardaya:
it's Ehrmahgerd, not amagad.... but I'll allow for an accent.. :P
[Nexus 5 Original Android Development] Fluidification:
Is anyone else having extremely laggy shut down time?

Latest R36 beta
[Nexus 5 Original Android Development] Pete182:
I don't know if this is kernel or room related but after prolonged use the screen goes crazy and looks like a TV that has no reception... Like all the colours get distorted and the screen flickers random colours for split second at a time. Does anyone else get this? Running r35 with cataclysm rom
[Nexus 5 Original Android Development] neriamarillo:
Yeah once I update to 4.4.2 everything stops working. I'll keep trying to find the solution. If not I'll have to send it to LG.
[Nexus 5 Original Android Development] Tzfardaya:
what happens if you flash 4.4, upgrade to 4.4.1, flash franco...

do all the sensors still work?

(I have the zips to step through 4.4 to 4.4.1 and 4.4.2 if you want/need them)
[Nexus 5 Original Android Development] bigknowz:
Just updated fku beta and noticing an issue with PAM. set min CPU to 652 for music ( Rocket Player), start music and then go to fku system monitor, which shows cpu1 and cpu2 at 300. Cleared fku data, reset min cpu for music to 652 and start music. Message popup says PAM enabled, hit home to emulate normal usage (phone into my pocket) and another popup says PAM disabled.
[Nexus 5 Original Android Development] neriamarillo:
Hmm now that I haven't tried yet. I would be willing to stay in 4.4.1 if it allows me to run all latest and future Franco releases. If you want you can send me the link for them, or I can look for them w no problem [emoji14]
[Nexus 5 Original Android Development] HenryDCase:
I had the same issue on r33. I decreased the amount I was undervolting and the problem was resolved.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tzfardaya:
pm'd you
[Nexus 5 Original Android Development] franciscofranco:
That's how it works, it sets modes for the foreground application. You hit home or put the device to sleep and the mode stops being applied.
[Nexus 5 Original Android Development] TJKV:
But what do the usual logs say? Anything in them?
[Nexus 5 Original Android Development] neriamarillo:
This is what usually comes up

E/qcom_sensors_hal(835): hal_acquire_resources: Failed for handle 0 @ samp 15 Hz rpt 0 Hz WuFF 0 batched 0

02-24 10:05:42.992

E/qcom_sensors_hal(835): hal_process_buffering_resp: Result: 1, Error: 502-24 10:05:42.992

E/qcom_sensors_hal(835): hal_process_buffering_resp: 0 Error: 4 Reason: 16

This repeats over and over and over. Other times it doesn't even show anything wrong...
[Nexus 5 Original Android Development] justibasa:
So 17 hours in, all 4 cores running, 1728 max, 300 min, 5 hours sot, 21% remaining. Might get 6 hours sot. Not switching back with battery like this.

Don't like me........BITE ME!!!
[Nexus 5 Original Android Development] Peanuts.:
Wow 6 updates in 1 day. TCP congestion algorithm. Everything looks fine now. Again... What a machine :eek:
[Nexus 5 Original Android Development] GeekMcLeod:
I'm assuming this is on the latest test?

I'm still on r35 with absolutely no issues and around the same battery life. Might give r36 a try soon, or maybe just wait until it's not in the testing phase anymore.

Posted from under your bed.
[Nexus 5 Original Android Development] justibasa:
Yeah. On the latest test kernel.

Don't like me........BITE ME!!!
[Nexus 5 Original Android Development] JNewms:
Are the only two tunables that you changed the hotplug to zero and max frequency to 1728?
[Nexus 5 Original Android Development] psp9000333:
what ate your voltage settings? my max is 1267 and undervolted minimum frequency to 675 with no issues, lag or excessive heat, even in cpu-intensive apps.
[Nexus 5 Original Android Development] guywmustang:
R35 is still pretty dang dim...
[Nexus 5 Original Android Development] BTT8:
I feel the same way
[Nexus 5 Original Android Development] shinesthru:
That's because it is an old release. There is no purpose in complaining about known issues on an old version.
[Nexus 5 Original Android Development] Tzfardaya:
they're talking about r35, which is the latest stable...

not everyone reads the backpost in the thread or wants to run test kernels... :P if they were complaining about r34 or earlier, then I'd agree with you.. :P

nvm, looks like franco snuck r36 out on me...
[Nexus 5 Original Android Development] franciscofranco:
And after testing r36 for 4 days straight I'm confident that its time for release:

* Rebased the Kernel completely from scratch

* Ram problems are fixed

* Audio bugs on the right earbud are fixed

* Improved the backlight dimmer algorithm to not dimm the display too much. Minimum brightness is still lower than stock

* Still as awesome as ever

Update it even if you're on the latest r36-test.

Have fun!
[Nexus 5 Original Android Development] Tzfardaya:
*scrolls up to try and find franco's release announcement*

found it... :P
[Nexus 5 Original Android Development] abimael08:
Still as awesome as ever lol good one ? keep up the great work
[Nexus 5 Original Android Development] Bobtehblob:
Out of curiosity does r36 still have the changes to the wifi timer?
[Nexus 5 Original Android Development] tuncan:
Awesome as expected for now :good:

Thank you.

My only problem with latest two versions was slow brightness response (when call ends for example). In Slovenia it is early, so I have to wait that someone calls me :laugh:
[Nexus 5 Original Android Development] nym27jrey:
Love the new release!
[Nexus 5 Original Android Development] shaker2k:
[MENTION=470754]Franco[/MENTION] how is your testing going running 4 cores at 1190?
[Nexus 5 Original Android Development] foxdigital2k2:
Thanks Franco nice release
[Nexus 5 Original Android Development] iPsychoGeek:
CPU temp limit is 60 now on r36.

Also, is it worth to upgrade from r35 to r36 if i hadn't any problems? Asking because so many CAF commits was reverted.

Nexus 5 with Tapatalk Pro
[Nexus 5 Original Android Development] frozenhotchocolate:
I'm running new r36 with all four cores running after turning hotplug load to zero. Clocked at 1.7 and everything is running smooth. I did undervolt -75 across the board and 300 to 625 to deal with a little extra heat from all four cores running. After undervolting excessive heat seems to have vanished, or that could just be in my head.
[Nexus 5 Original Android Development] lndeed:
Odd issue here. Switching from Dalvik to ART causes infinite bootloops on r36. I'd just flashed the 4.4.2 factory image, so there shouldn't be anything on my end causing trouble.
[Nexus 5 Original Android Development] BullHorn7:
GPU clock speeds menu has each frequency twice.
[Nexus 5 Original Android Development] misterviolinguy:
That's odd. I'm currently running r36 and ART fine (I'm running PA 4.2), though I did switch to art before installing r36.
[Nexus 5 Original Android Development] carlese:
So hotplug load_treshold should be set to 0 and not 100 to have 4 cores?
[Nexus 5 Original Android Development] fatspirit:
Are you using something like Barometer+?
[Nexus 5 Original Android Development] frozenhotchocolate:
I've just read people saying it should be set to 0. In system monitor I have all four cores always on with hotplug set to 0.
[Nexus 5 Original Android Development] jmartino5920:
Franco,

This is THE kernel to run if one is a Nexus user! Thank you so much for your time and dedication!

My phone is exactly how I want it: Stock, rooted, TRWPd and running FK all day using the "beta" of FKU.

Thanks for making the auto-dimming feature a feature! Not that I couldn't type the code in terminal but you are saving ME a step.

Everything is legit on my end...no audio, PAM, or any other derps which you have vowed to squash.

For the user who doesn't get why ART and this new release bootlooped: it happened to me once with a Franco.kernel update. I ran ART for a bit until it fücked my setup. Thankfully, I backup my shït. So when a Dev part of Android derped my setup, I knew it was time to go back to the tried and true Dalvik. There's a reason ART is not yet the standard. I'm not saying I didn't reap its benefits for a short time but a bootloop is a symptom of the runtime and not this kernel.

franco.Kernel FTW!

Much love,

jmar

P.S. I remember there used to be a franco.Kernel boot animation on the GNex. Any chance that makes a return?

Sent from my Nexus 5
[Nexus 5 Original Android Development] lndeed:
You're right; switching to ART before flashing r36 works without issue.
[Nexus 5 Original Android Development] jmartino5920:
ART is finicky like that.

And may I say that love my Moto G almost as my Nexus?

Sent from my Moto G
[Nexus 5 Original Android Development] Ben36:
Ok because I can't be arsed reading through 30+ pages.... Why are people setting hotplug to 0 now?
[Nexus 5 Original Android Development] edwinpang:
Would anyone explain to me why this kernel seems to have more heat dissipation with the same voltage setting,though on a different kernel, compared to cm11?
[Nexus 5 Original Android Development] chrisch91:
There is still the ram issue for me. After rebooting 1.3 gb free ram. At night (after killing all apps) not more than 700 mb free ram.
[Nexus 5 Original Android Development] Nocturnal86:
My max CPU gets stuck at 1.5Ghz im not to sure why or when it happens I had the issue on r35 and the last couple FKU betas but im on r36 and the latest FKU beta. I decided to clear FKU data and start fresh then applied r36 I then played a decently long gaming session with the charger plugged in with a PAM mode of 1Ghz and the phone got pretty hot/warm and after stoping the game and going back to FKU it showed 1.5Ghz and even after unplugging the phone and letting the phone cool down to below 40c it was still stuck. Im stock rooted with Xposed and gravity box thats it.
[Nexus 5 Original Android Development] JoshuaOrphir:
Its framework-pac.jar ;)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] bigmem:
[MENTION=3292224]franciscofranco[/MENTION] oh my very very tasty! Dude you have surpassed yourself. All issue not only fixed but phone is so amazingly fast : ) sound perfect! Graphics respect! BT perfect! Ram perfect! And my main bug bear, reboots on disconnect from casting fixed! R36 full is my new R32 lol. Just when I thought it couldn't get better. Dude seriously the only way I see you topping this build is if the phone starts charging itself from it being used. Human kinetic recharge lol. Only you could given time lol.
[Nexus 5 Original Android Development] kecinzer:
I like new backlight dimmer, exept when I on phonecall and end it, after I put my phone from ear, display is very dark. I don't remeber that this behaviour was there before dimmer.
[Nexus 5 Original Android Development] Arstoien:
For testing purpose on the "quad core mode" it's good to underclock, but for general use and performance, I'd tune the governor tunables to control the usage of higher frequencies. Currently using the settings someone mentioned earlier (sorry, couldn't find you to quote), though instead of underclocking to 1.5 GHz, I keep it at 2.3 GHz and change the target_loads to "90 1500000:95". This, combined with 1.2 GHz hispeed, and fairly high above_hispeed_delay, makes usage of freqs 1.2–1.5 GHz more conservative, and anything above used only when it's really needed. Needs more testing, of course.
[Nexus 5 Original Android Development] icomar:
Very interested in this, post your results here in the forum mate, pleaaase :)
[Nexus 5 Original Android Development] Arstoien:
Sure, I'm all for helping each other. You could test and post results too ;)
[Nexus 5 Original Android Development] ironjon:
RAM usage is absolutely fixed in r36

Obrigado Francisco!
[Nexus 5 Original Android Development] The Gingerbread Man:
I'm quite surprised at just how well these CPU settings are working out, no lag etc that I can see (no played graphic intensive stuff yet)

CPU Max 1267

GPU 320

Touch boost 652

Duration 300000

Go hi speed load 95

Hi speed freq 1190

Hot plug load threshold 0
[Nexus 5 Original Android Development] tylerdurden83:
Just out of curiosity, could you pinpoint the offending commits for ram and audio issues? Or they are simply too many so you aren't sure which one that you didnt reapply after the rebase was causing the issues?

One last question, have you reapplied the change to the wifi timer to lower wlan_rx_wakelocks? Cheers!
[Nexus 5 Original Android Development] BullHorn7:
I undervolted the CPU to 600mV at 300MHz and 422MHz,

610mV at 652MHz and it still won't crash. Of course I changed the governor to Performance and limited the min and max CPU frequencies to the one I'm testing.

I'm stress testing by playing games and loading apps.

Am I doing something wrong?
[Nexus 5 Original Android Development] italia0101:
R36 feels quite a bit smoother to me than r35, not sure what changed but it's goooood
[Nexus 5 Original Android Development] Nbsss:
Wow seems a tad aggressive lol, any lag when unlocking phone from sleep? Since your Hi speed load is so high, you can make your hispeed_freq higher I reckon
[Nexus 5 Original Android Development] The Gingerbread Man:
I changed it to 1190, I'll go back and edit my post. No lags that I can see its all good. Not played heavy games yet but doom works great, moving around android is fine. Give it a try :)
[Nexus 5 Original Android Development] Bobtehblob:
I've brought this up with Franco a few times but no one's been able to figure out what's happening. There has to be something messing with the the thermal throttle somewhere. The only way I can reproduce it is by plugging in my charger, then play a game for a while. CPU will be throttled and then it gets pegged at whatever freq it was throttled to.
[Nexus 5 Original Android Development] icomar:
I'm stuck at 1,5ghz too with r36, dunno why... I just updated kernel via fku

Sent by my Nexus 5 AOSPA4.2&francokernel using tapatalk
[Nexus 5 Original Android Development] nerotix:
Thermal throttle?
[Nexus 5 Original Android Development] icomar:
Can you explain your question? What do you want me to check?

Sent by my Nexus 5 AOSPA4.2&francokernel using tapatalk
[Nexus 5 Original Android Development] justibasa:
Yes.

Don't like me........BITE ME!!!

---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------

Voltage settings are stock.

Don't like me........BITE ME!!!