yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] akash3656:
Good job! Its time you learn what something is before you wipe. I'm hoping you didn't wipe your efs or factory. Anyway, flash back stock nexus factory image and start all over again. Google "return to stock nexus 5" and I think you'll find plenty of guides online.

Your radio issues might have been simply because of using an older recovery version lol.
[Nexus 5 Original Android Development] usaff22:
ADB sideload rom.zip in recovery. It will flash automatically once you specify the path to the file.
[Nexus 5 Original Android Development] vomer:
How come I didn't know about this app :eek:

looks nice :good:
[Nexus 5 Original Android Development] blueren:
It's featured in android police.
[Nexus 5 Original Android Development] Wenzo2:
This problem isn't related to the setting but... Sampling down factor isnt right! Set a value like 40000-80000

Set Timer rate to 40000 or 30000 for battery...

Set Timer slack to stock value is better...

Set up threshold any CPU freq to 1400000 Or 1600000 for more battery life...

Set min sample time to 40000 for battery...

Your settings are very disproportionate...
[Nexus 5 Original Android Development] 5FOOTER:
If yours stutters at all go to developer options and put all 3 animations to .5 that will smooth things out quit a bit.

Destro warlock on WOW burnall
[Nexus 5 Original Android Development] pikachukaki:
As I said I'm just testing I'm search each one of the values to see what they are doing that's why they seem so strange... And I need to Google translate the disproportionate word to see what is the meaning... :P thx btw... I make you changes...

Also about the sampling_down_factor i read this and i thought i could test it :

"When set to 1 (the default) decisions to reevaluate load

are made at the same interval regardless of current clock speed."

Σεντ φρομ μυ Νεχυς 5
[Nexus 5 Original Android Development] Wenzo2:
I think that sampling down factor is in µs like min sample time..
[Nexus 5 Original Android Development] big_adventure:
You need to wait at least a couple of minutes after a reboot before Per App modes will work. If you try too early, it will never work. Basically, Android sends a "I'm booted" message to registered processes. They can elect to do something on that information. FKU waits until it sees that before starting and implementing anything.

It had nothing to do with flashing a third time or anything. I mean, it's not really possible for that to happen - per app modes are an FKU (thus, userspace) thing, not a kernel thing. If your kernel supports changing CPU frequency limits, FKU will work, even if it isn't Franco's kernel.
[Nexus 5 Original Android Development] pikachukaki:
sampling_down_factor: this parameter controls the rate at which the

kernel makes a decision on when to decrease the frequency while running

at top speed. When set to 1 (the default) decisions to reevaluate load

are made at the same interval regardless of current clock speed. But

when set to greater than 1 (e.g. 100) it acts as a multiplier for the

scheduling interval for reevaluating load when the CPU is at its top

speed due to high load. This improves performance by reducing the overhead

of load evaluation and helping the CPU stay at its top speed when truly

busy, rather than shifting back and forth in speed. This tunable has no

effect on behavior at lower speeds/lower CPU loads.

https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt
[Nexus 5 Original Android Development] Wenzo2:
Yes... But Franco probably have changed how this parameter work. Isn't a multipler... For example if min sample time is 40000 microsecond and this value is set to 100 I think it should be equivalent of 40000000 microsecond... Stock value is 120000 so I think that isn't a multiplier but is in microsecond...
[Nexus 5 Original Android Development] dankoman:
look, i know this is WAY off topic, but it had me OTFL for like ten minutes, and i thought you guys might enjoy :laugh:. found it over at androidpolice under a post about franco's new per-app modes app. pay attention to the peoples' names:
[Nexus 5 Original Android Development] FAdrums:
LMAO Stalin nailed it!

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Tzfardaya:
That app looks like what Francisco has said is coming in the next fku beta....
[Nexus 5 Original Android Development] vomer:
ya, guess he can't really mention it as xda might see it as promotion
[Nexus 5 Original Android Development] FAdrums:
Btw guys, since I had those issues (fc's) I'm thinking of reflashing my setup again but with other FK version. What do you guys reckon? Should I just go back to r33 or earlier? My only "must" is the color control. Having doubts here... ?

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] tandxcstar1:
I would just go with R32 until issues are resolved.
[Nexus 5 Original Android Development] JNewms:
It doesn't matter. The fcs you're having don't have anything to do with the kernel
[Nexus 5 Original Android Development] FAdrums:
So what do you reckon it was then?

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] JNewms:
Not sure, but it is user space side. What is your current setup with ROM and mods, and what all was force closing?
[Nexus 5 Original Android Development] FAdrums:
Did a clean install (from a factory images reinstall) of PA 4.1 and PA gapps stock 1st of march. Then did the whole setup and flashed r34 test. Rebooted and flashed Viper sound mod and rebooted. After that changed to ART and used my phone "normally".

FC's: SuperSu, Google Search and Google Keyboard.

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] JNewms:
Hmm. I was just on the newest PA yesterday, the one that was just released. Used the latest PA Gapps. I too was running ART with it, along with the 34 test. I had no fcs. So I'm assuming that maybe the sound mod you flashed is causing you the issues.
[Nexus 5 Original Android Development] FAdrums:
Probably! But had the FC's in morning after a night charging. Weird. I will sacrifice the sound for the sweet pie! :p

Oh and thanks! :D

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] pikachukaki:
So we have two apps in battery drain... First is a game Royal Revolt 2 that is a tower defense 3D game that run 42minutes (not in a row) and Android system that also run for 40minutes...so both of them drain about 10% of battery... How this is possible I mean the Android system drain the same amount of battery as a 3D game?

Σεντ φρομ μυ Νεχυς 5
[Nexus 5 Original Android Development] sohell:
I'm going to flash this Kernel for the first time - is r32 or r33 or something else the most stable? I have a few of the earlier pages - it seems that r32 is the most stable, but thought I should confirm
[Nexus 5 Original Android Development] Rooster85:
Impressed!
[Nexus 5 Original Android Development] shinesthru:
So strange, I'm running that exact same setup with no FC's. I would try a fresh download of the gapps package and re flash. Did you flash the stock or full package?
[Nexus 5 Original Android Development] FAdrums:
Stock dude! That's really weird! I'm about to reflash the whole thing but without Viper! :(

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] shinesthru:
Like I said, I would try a fresh download. For good measure you could even check the md5 checksum. While your at it, try downloading from a PC and transferring to your device to flash.
[Nexus 5 Original Android Development] FAdrums:
Ok I'll do that. But can you describe all your steps of your full setup please (comparative reasons only). Thank you

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] zechizen:
Yes, I flashed r32 for my first time. Everything is awesome so far compared to stock. I've read that problems started from r33 build.
[Nexus 5 Original Android Development] ArtieQ:
Can I just flash the r32 zip over the r33? Or do I need to uninstall something first?
[Nexus 5 Original Android Development] shinesthru:
I didn't take any of the precautionary steps I recommend you take, but I do those when I run into problems. I just dl'd the ROM and latest stock gapps from the PA server onto my phone, factory reset, flashed ROM and gapps, and booted up. From there I setup my Google account, downloaded a few apps from the Play Store, downloaded Franco's test kernel v34, and flashed that through the Flashify app (allows easy flashing of img files, highly recommended). I installed the Viper4Android apk which I keep a copy of in my device's storage, installed the sound driver through the app, and rebooted to complete the installation of kernel and driver. That's it, not too fancy.

Edit: I should mention that I'm using Philz recovery as TWRP has been giving me big problems, like wiping my data partition.
[Nexus 5 Original Android Development] Tzfardaya:
Just flash 32 over 33
[Nexus 5 Original Android Development] FAdrums:
Thanks for your description. I did pretty much the same. The only difference is that I flash a Viper zip which installs it on pvt app folder + some libs (to make sure it will work 100% everytime - recommended on the thread). So I'm pretty sure it's the zip somehow messing it up! Going to reflash everything but I will also just install the viper app "normally"!

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Enddo:
I'm looking for some tips on extremely conservative FK tunables. This is what I have set so far

______________________________

Kernel Settings

- FSYNC = Disabled

- Logcat = Disabled

CPU Manager

- GPU = 200MHz

- Above Hispeed Delay = 125,000

- Boostpulse Duration = 10,000

- Hispeed Frequency = 1,574,400

- Input Boost Frequency = 652,800

- Min Sample Time = 40,000

- Timer Rate = 40,000

______________________________

Is there anything that's configured incorrectly or anything else that can be done to get an extremely conservative configuration with this kernel?
[Nexus 5 Original Android Development] Aerowinder:
Turn down the hispeed frequency. To the one that's around 1100Mhz, I don't remember the exact value. You can also turn up the load threshold.
[Nexus 5 Original Android Development] pkelly517:
You could always turn the phone off. That will save more battery than you could imagine.

Lower your max frequency to 960 MHz. It's all a balance.

Turning fsync off is risky. Try all the other stuff you want. But an odd reboot can make your phone non-bootable. A corrupt filesystem somewhere isn't worth the risk to me. But, it's your phone.
[Nexus 5 Original Android Development] matesc:
Maybe add these two:

-Raise load threshold from 60 to 80.

-Lower the synq freq.

Wasn't there something like go hispeed load with 90? If yes, raise it also to 99 or 100 (maybe it prevents to online cpu2 and cpu3- not sure)

:thumbup:
[Nexus 5 Original Android Development] Enddo:
hispeed frequency is like 2% of my usage. i picked 1.5GHz because i remember reading franco say it utilizes a higher frequency of ram at that level.

i have like 80% usage at 300mhz and then the last 18% of usage is at my touch boost at 600mhz

this is why i dont feel the need to lower my max frequency either. my phone just doesn't use that much juice

---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------

you joke, but with airplane mode on and low brightness, i get double digit screen on time with my kernel settings and using wifi.

im just looking for additional tips with some settings like io is busy, or timer slack or sampling down factor that i have no idea what they do or some settings that i might have tuned in the wrong direction or maybe some settings that i could tweak even further
[Nexus 5 Original Android Development] Tzfardaya:
there's a couple types of logs, dmesg/kmesg which is the kernel log (of it's activities etc) logcat, which is a userspace event log, and after a crash or unexpected reboot last_kmesg, which is a copy of the dmesg/kmesg log from before the reboot.. if the phone is rebooting itself, that's usually the one you'll find the answers in... hopefully... I use syslog to grab the logs myself, (haven't looked at catlog, I'll do that in a minute, to see which log(s) it looks at ...

I'd try 32, and what fc's are we talking about? I missed them somewhere... :P
[Nexus 5 Original Android Development] blueren:
Caused too much heating. By too much I mean above average heating. Reset everything and now back to stock franco settings. Let's see what franco has in line next.

Sent from my Nexus 5
[Nexus 5 Original Android Development] FAdrums:
Well basically the phone was charging through the night and when I woke up I went to check if had any messages, etc and it seemed it had rebooted because greenify was asking for super user permissions and then SuperSU, Google search and keyboard force closed. Haven't had anymore through out the day though.

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] inscythe:
An update to the Bluetooth LE issues with Pebble yesterday. I made it (for the first time) through the night without disconnected. I can definitively say that r34test has a Bluetooth connection problem (or at least the Bluetooth LE connection problem).
[Nexus 5 Original Android Development] kid1da:
I have a strange issue. My CPU max sticks at 960 MHz. It won't change. I've tried several apps to try and change it but it won't stick to any other setting. Running the latest carbon nightly and r33.
[Nexus 5 Original Android Development] Tzfardaya:
Ah, gotcha, and this was right after a fresh flashing of rom/gapps?

Probably, we should just add it to the list of "minor" issues with 34... (possibly 33 as well)

hmm, what apps are you using? do you have them all installed at once?

I've heard that that can cause problems.. I only use fku... however, check if the phone is warm, it might just be a temp throttle... (if the cpu is warm you might not feel it... but you def feel when the battery is warm..) what is your CPU Temp Threshold at? set that too low and the phone will throttle at room temp (talking from experience here... I've had it way too low and throttle with just screen on...)
[Nexus 5 Original Android Development] FAdrums:
I clean flashed on monday morning PA 4.1 plus 1st of march google stock PAgapps. Booted the phone and completed the initial setup (google account, apps restoring). Then flashed r34 via flashify rebooted and set color profile. After that flashed Viper sound mod zip (installs the app in pvt app and some libs - to make sure it will work every time and recommended on it's thread). After that used the phone throughout the day with no issues. This happened this morning (tuesday).

I guess I will revert back to r32 and reflash the whole setup fresh but won't flash the sound mod?

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Tzfardaya:
okay, now I'm all caught up... :P as was suggested before, fresh downloads to your pc, md5checksums, then copy to the device (checksums again if you're paranoid :P ) then flash..

Yeah, I'd leave the soundmod off for now... get everything working again, then nandroid back and soundmod later...
[Nexus 5 Original Android Development] kid1da:
Its at 60. What would suggest it being? I looked through my apps and it could've been greenify. I deleted it, and a few other useless apps. Most my apps are just icon packs.
[Nexus 5 Original Android Development] FAdrums:
Lol okok but should I revert back to r32? Not sure but I don't think this is a kernel issue. The revert back is just because of the CAF commits that are causing all this mem leak.

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] Tzfardaya:
60's safe, pretty sure that's franco's stock (or close enough to) only reason the phone should be generating heat is if the cpu is running high... (mine only gets hot in the qi charger or if I'm playing games that I haven't underclocked yet)

apps on the phone shouldn't have any effect when they're not running...

Do you have a system monitor app, I'd throw that on and track what cpu clock speeds you're running... sounds like something is trying to run away and peg the cpu freqs at max, throttling your phone down to 960...

---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------

might as well, it avoids the problem issues of 33 and 34 with all the changes... I'm thinking about it.. (unless [MENTION=3292224]franciscofranco[/MENTION] sneaks out that localbuild 34 he was teasing us with yesterday... *hint hint* :P )
[Nexus 5 Original Android Development] FAdrums:
Lol I'm going to then! Wish me luck and see you in a few! :)

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] kid1da:
I rebooted after I deleted those. I installed system monitor. It seems to be sticking now. I'm gonna continue to watch it carefully, but I believe it was on of those apps I deleted. Thanks for the quick reply.
[Nexus 5 Original Android Development] bigknowz:
On second thought

Ended up having an issue leaving work. I'll mess around with some more things over the next few days, hopefully have more thoughts by Friday.
[Nexus 5 Original Android Development] Tzfardaya:
probably, but unless something glitched hard, no way it should have been greenify.. :P
[Nexus 5 Original Android Development] 5FOOTER:
I'm sure it wasn't greenify all it does is hibernate apps. Been using since it came out.

Destro warlock on WOW burnall
[Nexus 5 Original Android Development] FAdrums:
Well just reflashed everything and reverted back to r32 but it does feel slower...I might just flash r34 and just leave Viper out of equasion.

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
or just grab the r34 default tunes and see what's different. :P
[Nexus 5 Original Android Development] FAdrums:
Uh?

Well just flashed r34. Lets hope for the best. Bedtime Now! Have a good one guys!

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] puska:
mm-qcamera-daemon high battery use and cpu stuck is Google bug and will be fixed with an update so nothing to do with Franco

http://phandroid.com/2014/03/04/and...ogle-fix-arriving-in-a-future-android-update/
[Nexus 5 Original Android Development] Tzfardaya:
thanks for the link, good to see google is working on it. now, lets just hope it rolls before android 4.5 late spring/early summer...
[Nexus 5 Original Android Development] sam razzy:
When I listen to music, the right ear cuts out completely..
[Nexus 5 Original Android Development] Tzfardaya:
at max/near max volume? seems to happen in the top 3 volume notches.. turn it down a bit and it should be fine...

reset by removing headphones, fully closing the music app (settings->apps) then reinsert headphones.. (or just reboot)
[Nexus 5 Original Android Development] italia0101:
That's odd, these were the default settings for r33.. Heat Is all good over here
[Nexus 5 Original Android Development] Stormblessed:
Not that bad with old r32.. + 30+ min of calling usage. Better than mine results with r33/r34

What do you think guys?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] maksud_ans:
hai Franco I confuge battery back up my phone r34 kernal .

100%charging and regular using WiFi my battery stats down this method(all time uc browser running)

100-95=30min sot best result

95-90=20min sot best result

90-80=40min sot best result

80-70=35min sot best result

70-50=60min sot best result

50-30=40min sot very bad result

30-5=50min sot very bad result
[Nexus 5 Original Android Development] kanin_rider:
For those who are experiencing camera failure to open or a core stuck at 100%, can you try this if it solves the issue: try to disable the location option in camera menu and observe if the bug still persists after a few hours. Mine is doing good for more than 24hrs already after doing the workaround. Maybe the play service update is causing the bug. Just a guess because i think it started happening when play services got updated to latest version thats why most of us experience the same error lately regardless of kernel version and even on stock.
[Nexus 5 Original Android Development] :
mm-qcamera-daemon

A bit off topic, but have you seen this guys: http://goo.gl/zUrEiE

Looks like we might get even better battery life once Google released new Android update ;)
[Nexus 5 Original Android Development] thesebastian:
I have that issue in my N5 and my GF's Moto G. Both phones with camera location disabled.

I think this will be fixed in the next version.

Sometimes is related to the camera daemon battery drain sometimes not.

Sent from my Nexus 5
[Nexus 5 Original Android Development] pikachukaki:
Where you can apply the screen off speed??
[Nexus 5 Original Android Development] usaff22:
Pulled my phone out of my pocket, it was really hot. Battery drain was massive.

Kworker seems to have been using it. Did a reboot and it seems fine for the moment.
[Nexus 5 Original Android Development] static416:
I'll try out syslog and see if I can get something more useful. Thanks for the suggestion.
[Nexus 5 Original Android Development] Kpoch:
Well i was not busy this weekend and didnt use my phone at all and this are my battery results. . And this

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] nickmv:
Franco, I'm loving your kernel, and bought your app, but I've witnessed some major issues over the past 2 weeks. Twice over that period of time, I've had my phone go absolutely berserk, and after switching kernels, I'm convinced it's franco.kernel, unfortunately. Otherwise though, the kernel it almost always exhibiting excellent batt life.

Anyways, here goes a list of the problems:

Last night, battery drained from 100 to zero in extremely short time (like 3 hrs max). I tried to wipe cache and dalvik, and re-flashed franco kernel, but it did nothing. Still having massive drain, caused by "Android OS"

This morning, I started getting a series of cascading FCs of major Google services (Search, Now, Google Services, and more), and the battery is just all over the place. After the series of force closes, I rebooted into recovery, only to find that the battery dropped from 35% to 10% simply from the reboot. That was baffling.

I don't know what the hell is going on, but this isn't the first time it's happened. I didn't install any apps or do anything special to suddenly cause it, and I was having great battery life up until last night. Now everything is completely ****ed, with no apparent culprit........UNTIL I uninstalled franco kernel and replaced with the stock kernel/bootimg.

While having those issues, I was unable to get BetterBatteryStats to load to look at Partial Wakelocks, which is unfortunate. It would just freeze upon loading, telling me that it couldn't establish a "from" and "to" point, and refreshes wouldn't fix it.

Anyways, like I said, the instant I uninstalled franco by flashing the stock kernel/boot-img, all my problems went away. I just switched back to franco yet again to give it a shot, and everything seems ok AT THIS MOMENT. I cannot say for sure if that will stay that way, but we'll see.

Franco, is there any ideas you can come up with as to why this would happen? I'm running 4.4.2 stock ROM, with the latest versions of Xposed and GravityBox. The ONLY mods I ever have made with your kernel is to load a color profile, and increase the headphone boost by 2dB.

Any ideas?
[Nexus 5 Original Android Development] coolnow:
Honestly sounds like it's not the kernel. Could be a whole host of problems, but the kernel shouldn't be giving you high Android OS wakelocks and cause your phone to go "berserk". I've been using r33 since the beta and have had absolutely no problems. Do a complete wipe of your phone (after a thorough backup of all files) and install the rom of your choice on the fresh device, and restore only the apps you use and need.