yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] blackt5:
Found a bug in the most recent beta. If you open system monitor and change to light theme it will fc. Once you get the first fc, you can't go back in and change to dark because it will fc over and over. The only way to make it stop is to wipe flu data.

Per app modes also do not work for me. Once everyone said they stopped I noticed that I don't see the toast when I use Chrome, one of the 2 modes I have made. I assigned cf bench the chrome mode and ran it. It still when to 2.2ghz even though it should have stopped at 1.4, no toast either.
[Nexus 5 Original Android Development] UpSpin:
I don't have this problem.

- Have you verified to permanently give FKU root access and not just temporarily?

- Have you tried to manually remove FKU from the list of allowed apps in the SuperSU app (or whatever you use) and afterwards allow it again.

- Do other apps, which need root access, work or do you also have to give them root access each time?
[Nexus 5 Original Android Development] tsubus:
Question about cm compatibility (no, I'm not asking to add it, I'm just curious about this): is it an issue of keeping compatibility for both aosp and cm roms or just hard to add the needed caf patches to get it working on cm at all?
[Nexus 5 Original Android Development] abra5umente:
Yes, yes, and no.

This leads me to believe that there is a problem with the app.
[Nexus 5 Original Android Development] lesp4ul:
+1 i thought it was screen defect.
[Nexus 5 Original Android Development] snives:
The necessary CAF patches break AOSP compatibility but CAF ROMs need the related portion removed to work with an AOSP kernel, so the two are mutually exclusive.
[Nexus 5 Original Android Development] tsubus:
Thanks, that's what I was hoping :)
[Nexus 5 Original Android Development] snives:
It is a hardware limitation. The backlight has minimum power requirements to maintain consistent brightness, with each cell in it having a different minimum. As we push the power down to that minimum some start to fade out faster than others, giving you darker/brighter zones. This is different device to device. Setting the minimum pushed in the kernel higher would make people with 'better' lights unable to go to lower brightness, but would prevent 'worse' lights from behaving like that. If yours has issues like that, and you are using a ROM with adjustable lighting levels (most custom ROMs, not sure about stock) then just increase the lowest levels slightly until the issue goes away.
[Nexus 5 Original Android Development] Briaann:
In the download link all files are "nightly" is there a stable version for this kernel?
[Nexus 5 Original Android Development] psyren:
Bug report(?): I seem to be getting data drops every now and then. In addition to this, I occasionally try to send SMSs, but repeatedly encounter errors saying it failed to send. Toggling airplane mode on and off seems to fix the issue. I'll try and get a logcat next time it happens, but is this a kernel or a ROM issue? Or perhaps it's my ****ty carrier...
[Nexus 5 Original Android Development] jmartino5920:
All versions that aren't tests at considered stable. Franco doesn't label his builds stable anymore.

Sent from my Moto G
[Nexus 5 Original Android Development] Briaann:
Okay. thanks men!
[Nexus 5 Original Android Development] Tzfardaya:
Only the ones in the "test" folder are not considered stable...
[Nexus 5 Original Android Development] armando_rod:
Anyone using Stickmount with r35? It doesn't work for me. Stock rom and latest SuperSu.
[Nexus 5 Original Android Development] RobbieL811:
I am using it on Test 36 and I used it when I was on r35. I don't remember ever having a problem with it. I always have to use SuperSU to get it to work though. Sounds like you are doing that though. All I use it for too though is to mount a USB drive. Never tried to mount anything else. What are you trying to mount with it?
[Nexus 5 Original Android Development] The Gingerbread Man:
Can you try music play back with min CPU speed of 422mhz. That's the only thing I can do to make it stop. It seems 300mhz isn't enough for the audio bit of the SOC to be able to decode mp3 correctly.
[Nexus 5 Original Android Development] Wenzo2:
[MENTION=3292224]franciscofranco[/MENTION] I've got a bug in the hotplug driver... I don't know how to reproduce it (I was changing the hotplug settings)... Is the second time that I've got it. One core Number 3-4 stay online at the CPU boost freq.

I've reselected Max freq value (it was 2,3 GHz after and before) and I've fix it.

I've attacked some log but I don't know if they can be useful.
[Nexus 5 Original Android Development] nerotix:
So what are u saying? That the audio glitches dissapear when u set the minimum cpu freq 422Mhz? interesting =o
[Nexus 5 Original Android Development] The Gingerbread Man:
Yes I am saying precisely that. As a temporary solution use 422mhz as min speed or use a per app mode.

Franco is aware of this solution we had a conversation about it last night
[Nexus 5 Original Android Development] jmartino5920:
You Gingery man, you! Great find!

Sent from my Nexus 5
[Nexus 5 Original Android Development] blueren:
Bwahahaha!
[Nexus 5 Original Android Development] Briaann:
Flashed the Kernel and immediately happened to me. I'm on stock ROM and never encountered this problem before.
[Nexus 5 Original Android Development] vomer:
added + zips updated :good:
[Nexus 5 Original Android Development] The Gingerbread Man:
Well it was Franco's suggestion to try increasing the min CPU speed it was just a matter of me finding where it stopped. I'm hoping the next kernel will use 350mhz or 384mhz as lowest CPU speed, but that's up to Franco to decide.
[Nexus 5 Original Android Development] vomer:
I lol'ed at that way too much :laugh:
[Nexus 5 Original Android Development] tylerdurden83:
I don't really think that I'm following you here. Let's assume that 300 mhz isnt enough to decode mp3, which can be fair when you think about it ofc. Shouldnt the frequency raise to make up for it? I mean, 300 isnt enough to play games either, but as you'd expect, the cpu's frequency is raised to make up for it, so what's special about this single usage case (mp3 playback)?
[Nexus 5 Original Android Development] Tzfardaya:
It's less that 300 isn't enough to handle mp3 playback, and more the system doesn't react fast enough at 300 to raise the freq if something else happens... By raising the min limit slightly, you allow some extra idle time for the cpu to process other events while keeping the mp3 playback smooth.
[Nexus 5 Original Android Development] oddlyshapedstickman:
Been running f.K since the GN and it's been brilliant, but it's time to say goodbye. Ordered my iPhone 5s because I need it for work and my life is gonna get a hella lot more complicated and an iPhone just works. Not saying Android doesn't, but with an iPhone at least I can't tinker with it ;)

Thanks for some amazing times guys, especially the genius [MENTION=3292224]franciscofranco[/MENTION] !!! See y'all sometime in the future :good: :fingers-crossed:
[Nexus 5 Original Android Development] DREWHAMM974:
An iPhone is what it is. That's the thing there is absolutely NO OPTIONS. You bow down to lord Apple and hope he doesn't make your life worse, but if he does you must accept it because there is nothing you can do about it.
[Nexus 5 Original Android Development] floepie:
Could be a fast dormancy issue if your carrier doesn't support it. In that case modify your build.prop to turn it off.
[Nexus 5 Original Android Development] armando_rod:
Mounting an USB drive as well, I flashed back r32 (was the only one I had to flash right away) and it worked
[Nexus 5 Original Android Development] omvir:
[MENTION=3292224]franciscofranco[/MENTION] hello, I use the PA ROM and they just recently merged this https://gerrit.paranoidandroid.co/#/c/3752/ would this help with the per-app-mode service to keep it alive and not get killed?
[Nexus 5 Original Android Development] RobbieL811:
Idk. Give test-36 a try. It's working fine for mW on that version. 36 also fixes some other problems I believe.

Sent from my Nexus 5
[Nexus 5 Original Android Development] snives:
Apparently the temptation to break things was too great for him :P I have spare devices and use MultiRom just for that reason myself :P OmniRom or Stock + FK stable releases for daily use, and dozens of 'toy' setups that I only use in the middle of the night when I don't have to worry about anything important happening :P
[Nexus 5 Original Android Development] psp9000333:
try making the minimum ram available to a low setting. I had this same problem before with android always killing the service. now I have no issue whatsoever.
[Nexus 5 Original Android Development] Enddo:
but 300MHz is enough for stock

i'm not liking the direction this is going. . .
[Nexus 5 Original Android Development] Tzfardaya:
oooh, I hope no one introduces him to jailbreaking iphones then... :P
[Nexus 5 Original Android Development] The Gingerbread Man:
A small bump of 50-84hz won't hardly touch your battery life.
[Nexus 5 Original Android Development] Enddo:
it's just funny that franco has been so adamant about not letting us use 100MHz as well as not letting us disable 3 cores because 'qualcomm stock settings aren't setup that way'. yet here we get changes like this
[Nexus 5 Original Android Development] Tzfardaya:
stock also uses a much different scaling system.

mpdecision, which franco removes and replaces with his own.

franco's kernels also run at a much lower freq than stock more often than not, to improve battery life.

It's been a while for me so I don't remember the exact freq's, but if you want to run a quick test, reflash stock, rename the 2 .bak files and run a cpu freq monitor while using stock kernel, then reflash back to franco and do the same thing... Depending on your stock kernel, franco's freq's will be substantially lower. (iirc from my last test with this, 300 on franco vs 1200 on stock)
[Nexus 5 Original Android Development] The Gingerbread Man:
Well nothing has been set in stone, it's up to franco at the end of the day. The thing is this is the only solution iv found to stop music skipping which does detract a little from over all enjoyment and I'm sure there are others out there who arent as forgiving as me. Let's wait for Francos verdict :)
[Nexus 5 Original Android Development] Tzfardaya:
I doubt franco will actually change the lowest freq point... (if he does, it might be just by hiding the 300 freq point and using the next highest as min)

and as to the 3 cores disable, that's a different issue.

during tests franco determined that the power saving from only running one core while screen on was negligible when compared to the cost of continuously turning the second core on and off... power savings vs device latency... by leaving the second core on, the device responds quicker at low freq's will minimal cost to battery life.
[Nexus 5 Original Android Development] shaker2k:
If any of you follow Franco on g+, he is asking us to try running 4 cores always on. 300 min, 1190 max.

Options are a good thing.

Edit. I'm finding 1190 max a bit laggy so as [MENTION=622900]danillo[/MENTION] suggested I'm trying 1764 max.
[Nexus 5 Original Android Development] harshalkatakia:
I'm facing an issue wherein I do not receive WhatsApp messages when the screen is turned off, but the moment I turn it on, I start receiving them. WiFi is always on. Not sure if it's an issue related to kernel or not.
[Nexus 5 Original Android Development] Enddo:
and you can set this on your phone. it's the same with us asking for ondemand governor but franco saying interactive tunables is enough for everyone to customize it to how they like it

why can't you customize yours since you're having this issue. im not seeing this music playing bug and if this is the one im remembering, franco can't reproduce it either

i dunno, im not saying the sky is falling and all, but it just seems funny. we'll see what franco decides
[Nexus 5 Original Android Development] Tzfardaya:
heh, the impression I got from the initial post of "try this" was for people experiencing the issue, not for all of us...

it's another reason why I doubt that franco will mess around with the min freq step.. as it's simple enough to have a per app module for the music players...
[Nexus 5 Original Android Development] Enddo:
are you on stock rom? i've heard people talk about this before and end up installing a 3rd party application to help push those notifications. i dont have this issue with whatsapp and wifi though
[Nexus 5 Original Android Development] harshalkatakia:
Yes, on stock ROM. This happens most of the time, but the rest, messages are delivered properly. I thought it must be because the WiFi shuts off to save battery, but when I turn on the screen, WiFi is on, and it's not in the inactive mode(orange color)
[Nexus 5 Original Android Development] blueren:
Looks interesting.
[Nexus 5 Original Android Development] m52 power!:
It seems like this thread is one long trial proving the theory "if it were possible to do it would have been like that stock". With every gain there is almost always a loss somewhere else.
[Nexus 5 Original Android Development] The Gingerbread Man:
The difference is on demand is a feature request, not what I'm asking as I'm trying to help solve the issue of a much discussed problem and that's the only solution iv come up with. Me and Franco tested several different potential fixes but none of which worked. You right though I could use a per app mode but that service is still being killed after time and I'd rather use a lower CPU speed than 422 as min for the same reason you don't want to increase from 300 as it will cost a little in battery but not much. The issue is defiantly there, it exists, just not everyone is experiencing it.
[Nexus 5 Original Android Development] AhmedFaiz:
Running r35 since it was out. everything on default settings. Performance and battery life is the best so far I used. PA + Franco killer combo. ;)

Nexus5/PA4.1 Beta2/Franco r35
[Nexus 5 Original Android Development] bigknowz:
Played around with faux to see if there was audio glitch there too. There wasn't because cpu stays at hispeed_freq when music is playing with interactive. 1.5 GHz in my case.
[Nexus 5 Original Android Development] The Gingerbread Man:
Thanks for taking the time to test! Obviously 1.5ghz is way over kill for music lol
[Nexus 5 Original Android Development] ckarv:
Hi,

I have a question I haven't gotten a definitive answer to.

Does the franco kernel support encrypted file systems?

I have a stock Nexus 5, with an encrypted file system, because of work related requirements, and would really like to continue using this kernel.

So, is this supported? And if not, will it be in the future?

Thank you!
[Nexus 5 Original Android Development] The Gingerbread Man:
I think it works on r32 or r33 but not newer ones.
[Nexus 5 Original Android Development] SedyBenoitPeace:
I'm using the r36 of test and it seems that the audio glitches are gone! I can tell that the battery is better but probably is a placebo! Thanks for the great kernel now i really enjoy it! [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 5 Original Android Development] sbslammer:
getting 5 hrs screen on with 24hr standby on r10...avg about an hour of downloading or google music a day... looking forward to r11!
[Nexus 5 Original Android Development] The Gingerbread Man:
%2 battery drain over 9 hours sleep. The best I ever had
[Nexus 5 Original Android Development] jumparound246:
Why does betterbatterystats for you guys seem to work fine and mine tells me "battery Info could not contacted" or something similar stupid like that?! :(
[Nexus 5 Original Android Development] Andrew025:
Are you using the latest .apk from xda?
[Nexus 5 Original Android Development] jumparound246:
Nope, Mr.dumbass here :rolleyes:

Working fine now, thy for the hint and sorry for ot
[Nexus 5 Original Android Development] hotweiss:
How would this improve performance when anti-aliasing slows down the framerate?
[Nexus 5 Original Android Development] Lownita:
Same for asphalt 8. But time will come!
[Nexus 5 Original Android Development] Langduscher:
I'm getting nowhere near that idle drain that you guys seem to have. I'm getting 1% dain per hour.

I suppose that's got to do with the fact that I'm on mobile data & you are on wifi?
[Nexus 5 Original Android Development] Aerowinder:
Mobile data is not the reason, at least not the entire reason (that and wifi have similar usage). If you post some BBS logs, we could havee a look for you?
[Nexus 5 Original Android Development] chugger93:
Where do you find this? I searched XDA and couldn't find betterbatterystats. Nor one that works with kitkat
[Nexus 5 Original Android Development] DerItaliener:
I actually have the same "problem" I did intentionally not touch my phone after fully charging for 4 hours to see what mobile data is causing.

As you can see in the attached Screenshots the relative percentage is HUGE, without seeing any reason in BBS :(
[Nexus 5 Original Android Development] The Gingerbread Man:
Using WiFi and turned off location reporting and location history and as per the suggestion I turned location to device only
[Nexus 5 Original Android Development] tontiv:
won't it use more juice since it's using GPS instead of wifi/mobile network?
[Nexus 5 Original Android Development] eep2378:
Here, use the Latest beta(beta 5): http://xdaforums.com/showthread.php?t=1179809
[Nexus 5 Original Android Development] bloot:
Quite ironically, it doesn't. Some apps doesn't use the location when it's adjusted to "device only" (google now for example), maybe that's why.
[Nexus 5 Original Android Development] chugger93:
Thank you!
[Nexus 5 Original Android Development] jericho7:
what are the appropriate values for the headphone and headset boost? is it just the higher the number, the louder it is?
[Nexus 5 Original Android Development] noneabove:
Hey franco, for some reason auto-brightness seems to have a minimum value of about 20%... when I cover up the light sensors it doesn't want to go any lower. This seems really high... What's going on here? I know you made adjustments to autobrightness so that's why I'm asking here
[Nexus 5 Original Android Development] bryanlimy:
Even with stock Rom stock kernel, I think the N5 auto brightness is airways higher than needed

Nexus 5 and Nexus 7 (2013) with Franco Kernel
[Nexus 5 Original Android Development] noneabove:
Agreed, but one release (r9 or r8 or whatever) he said he had improved autobrightness by changing it to an exponential rate rather than linear, causing reduced brightness at all early levels, but it still seems insanely bright and the fact that ~20% is the minimum is odd
[Nexus 5 Original Android Development] shinesthru:
Coming into someone's development thread to talk crap about their creation is the pinnacle of internet trolling. Who asked you?
[Nexus 5 Original Android Development] gee2012:
Encryption has caused a lot of issues for some users as they cannot access any data if there is a phone failure of some kind.
[Nexus 5 Original Android Development] Tzfardaya:
Seems to me he had a perfectly valid point... All of Franco's improvements are an adjustment of battery vs performance. the reason why so much of his work seems to create battery life out of thin air is that the device is so overpowered that you can throttle it back a large amount with little perceptible loss of performance.

So yes, this is one long thread of trying to find the "best" balance point of performance/battery for the default settings. From that, each of us is free to tune the settings a little more to our favour, some prefer battery and don't mind a little stutter in the ui, others prefer pure performance and don't tolerate any stutter.

example

mpdecision verses franco's throttle system... mpd runs a much higher frequency than may be necessary to ensure a consistently smooth ui. franco drops cpu freq faster to preserve battery, as a result it may stutter a bit as the cpu ramps back up.

While he may have over simplified it, I don't see it as "talking crap"

However, attacking someone for stating an opinion (rightly or wrongly) seems as much an attempt at trolling....
[Nexus 5 Original Android Development] shinesthru:
It seemed plain to me what was being said was basically, "The stock kernel is ideal and any attempt to improve upon it will break it in another way." If I misread that, then I apologize.
[Nexus 5 Original Android Development] ckarv:
That's probably true, but then again that's a "feature" in a way :) You can access the encrypted partition with TWRP, if you can access recovery..

But you guys have no idea if support for this is going to be added in the future or not?

Cheers.
[Nexus 5 Original Android Development] Tzfardaya:
oh, but the stock kernel is ideal... for the masses, who want their stuff to *just work*

same as a stock car engine is ideal...

Both leave room for improvements, and ideal does not mean the same as perfect... :P

perhaps I'm just more forgiving of people and tend not to read posts as attacks, but as differences in languages...

What custom tuners do, is try to take the ideal, and perfect it for a purpose. Each kernel generally tunes with a specific goal in mind, in this case, it's battery life.

Car tuners may take stock and tune for performance (racers), fuel economy (hypermilers), etc, etc....

But, there is almost always a tradeoff... with car tunes racers sacrifce fuel economy, hypermilers sacrifice performance.. same with kernel tunes...
[Nexus 5 Original Android Development] Briaann:
Do I download and flash this or what?
[Nexus 5 Original Android Development] shinesthru:
I work the night shift so I just woke up. I haven't had near enough coffee to argue semantics. The bottom line is that I understood the comment as a blanket criticism of this kernel. Like I said before, if I misunderstood, then I apologize.
[Nexus 5 Original Android Development] Tzfardaya:
download it, and unzip it... not for flashing.

it's just a collection of files you can import to fku to use the preset colors others have come up with.

---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------

no worries, for all I know, you might be right... :P

I just took your post as an excuse to expand and teach others who may come in and read about the kernel. :)
[Nexus 5 Original Android Development] Momotani-Hitoshi:
R32 works with encryption, but R34-36beta doesn't. Phone will not be able to turn wake after it goes to deep sleep. You'll have to force reboot it.

---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------

Some people like me use work related exchange email and it's policies force users to encrypt their devices. TWRP can mount encrypted data, but always good to keep backups in case of failure.
[Nexus 5 Original Android Development] Briaann:
Do i paste it in the kernel zip file and then flash the kernel again? Sorry for all this noob questions.
[Nexus 5 Original Android Development] vomer:
you do not flash any file...

unzip the files and put it under the franco.kernel_updater > color_profiles directory
[Nexus 5 Original Android Development] Momotani-Hitoshi:
But... then you can jailbreak your iPhone and the world of tinkering begins all over again.
[Nexus 5 Original Android Development] gee2012:
Install the FKU app and then look in Root Explorer (or similar) and you see a Franco folder where you can copy&paste the profile in the folder with color profiles afaik.