yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Technecium:
Ok, just checking.

In FKU - Settings, do you have "Disable PerAppModes service" checked?
[Nexus 5 Original Android Development] sir*mez:
I have yet to see my phone sit on 300, it's always sitting on 422. Clean flash, dirty flash, clean install, stock rom, slim rom, etc. Can't do 300 at all no matter what I do with this kernel.
[Nexus 5 Original Android Development] tlrsax54:
Can't say I am having the same issue....
[Nexus 5 Original Android Development] simonarturo:
This topic again....

Its by design. Frequencies change faster than what Monitor can log them. It IS going to 300, you just can't see it.

Advice, stay away from the monitor and enjoy the experience.

As for me, the max freq is lowered only when booting and after a bit (30 secs to 1 minute) it goes back to normal.
[Nexus 5 Original Android Development] nitinvaid:
since i flashed This kernel My NTFS formatted 32GB usb OTG Drive not working

Device is not detecting it no status
[Nexus 5 Original Android Development] Wh1t3Rose:
Use fat32
[Nexus 5 Original Android Development] nitinvaid:
i cant use that its 32GB drive not 4GB

looks like i had to switch to other kernel

I like This One soo battery friendly and smooth
[Nexus 5 Original Android Development] Wh1t3Rose:
You can use fat32 on a 32 GB SD Card. The only limitation is you can not have files larger then 4 gbs on the card. But size of the card does not matter.
[Nexus 5 Original Android Development] nitinvaid:
i know that and my card has files more then 4 GB
[Nexus 5 Original Android Development] armymax:
"The service is enabled". It's ok?
[Nexus 5 Original Android Development] pchtc:
fat32 has a max 4gb minus 1 byte per file not per volume

the volume can be up to 2TB

Limits

Min. volume size	32 MB-4.5 KB (with 65525 clusters and 512 byte sectors)

256 MB-36 KB (with 65525 clusters and 4 KB sectors)

Max. volume size	2 TiB (with 512 byte sectors)

8 TiB (with 2 KB sectors and 32 KB clusters)

16 TiB (with 4 KB sectors and 64 KB clusters)

Max. file size	2,147,483,647 bytes (2 GB - 1) (without LFS)

4,294,967,295 bytes (4 GB - 1)[1] (with LFS)

274,877,906,943 bytes (256 GB - 1) (only with FAT32+[2])

-----------------

edit - sandman beat me to it
[Nexus 5 Original Android Development] Tzfardaya:
Need stick mount or similar to mount the SD card, and the ntfs fuse files so the kernel knows how to read that filesystem...
[Nexus 5 Original Android Development] Technecium:
Yes, I'm just trying to reproduce the problem. This is as close as I have been able to come.

At first, everything works as expected but after the max freq gets adjusted multiple times it appears to get stuck like you mentioned.

However, I didn't have to reboot to get it working properly again.

Can you try something and see if you get the same results?

Reproduce the problem, so that the temp exceeds the threshold and the max freq gets locked at 1.5 GHz like you described.

Wait a few minutes until the temperature is below the threshold. Check FKU to confirm it is still set to 1.5 GHz. Hit the Home button and return to your launcher. Now swipe FKU away from the recent app list and check your max freq again in FKU.

Is it still at 1.5 GHz?

Mine appeared to get stuck when I would jump between the app I was using to drive the temperature up and FKU to see if it had raised the max freq back to 2.2GHz after the temperature had gone down. Only after swiping away FKU did it appear to issue the command to return the max freq to 2.2GHz.

Can you reproduce what I did or is it still stuck at 1.5 GHz?

---------- Post added at 01:30 AM ---------- Previous post was at 01:20 AM ----------

This is perfectly normal. Even though you are not interacting with the device there are still processes running that request cpu time. The changes Francisco made to interactive just handle the load differently.
[Nexus 5 Original Android Development] sjknight413:
Yes. Same happens with it checked or unchecked though.

It's a confirmed issue, you're just not checking CPU frequencies as much as us obsessive compulsive lot ;)
[Nexus 5 Original Android Development] tlrsax54:
Hah I suppose...I never check it but when I do it is always at default I guess lol.
[Nexus 5 Original Android Development] Nocturnal86:
This has happened to me still and it seems to only happen when Im charging the phone and it throttles then locks in place even after the phone has cooled and the charger has been removed.
[Nexus 5 Original Android Development] RobLudo:
You must use StickMount and check if root is provided by SuperSu.

In order to use NTFS drive you have to put the ntfs-3g driver in /system/bin with 755 permission.

Here you are the zip containing the driver, extract, put in the folder and set permissions

https://www.dropbox.com/s/risg53yqxgam3z0/ntfs-3g.zip
[Nexus 5 Original Android Development] Wh1t3Rose:
With how much overal time is that? 12 hours? only 6 hours?
[Nexus 5 Original Android Development] rowdyw:
Typically about 18 hours total time with 3-4 hours SOT. I also listen to podcast/music over BT headphones about 6 hours a day. Google Now on, location high accuracy.
[Nexus 5 Original Android Development] Tzfardaya:
Lucky you, I usually get 2-3 hrs so, in 8 hrs on battery....

But I'm in an out of office towers all day, chewing up my battery due to mobile data signal fluctuations...
[Nexus 5 Original Android Development] rowdyw:
I use Tasker to automate a lot of things like turn WiFi off when I'm at work, turn off LTE when I'm connected to WiFi, ect. So I'm sure that helps some.
[Nexus 5 Original Android Development] Tzfardaya:
Same, what are you using to turn off lte? Custom Rom or xposed? Or are you just turning off mobile data?
[Nexus 5 Original Android Development] rowdyw:
Purity ROM and secure settings
[Nexus 5 Original Android Development] Tzfardaya:
Purity.. That explains it.. Can't switch lte off on stock directly... Can turn off mobile data though..
[Nexus 5 Original Android Development] rowdyw:
Yeah, but mobile data turned off means no MMS.
[Nexus 5 Original Android Development] Tzfardaya:
Which is why I don't turn it off...
[Nexus 5 Original Android Development] mendozaram:
Francisco and his magic *.*

- Default settings

- Slimkat
[Nexus 5 Original Android Development] pulsar_swift:
Location is SET to OFF or Device only ?

Please confirm
[Nexus 5 Original Android Development] JazzMozz:
A couple of days ago my daughter accidentally spilled some orange juice over my Nexus 5. After that the phone wasn't charging anymore. I brought it to a shop where they fix damage caused by fluids. Yesterday I got my phone back and they have been able to repair it (they replaced the charging port which they believed short circuited). Although I had applied a SIM-lock, they have been able to access my Android environment. Everything seemed untouched (i.e. all icons were where they should be, no apps installed through the Play Store), except for one thing: the screen. It had a yellow teint, the one I got rid of after installing FKU (r12 or so) and applying a colour profile. When I checked FKU, the same colour profile was still enabled. I got the suspicion that maybe this was a completely different device that they returned to me (because one screen may produce a yellowish teint while the other doesn't).

Am I seeing ghosts here or could there be a logical explanation? Of course I asked them and obviously they said that it was the same device and that they hadn't tampered with anything.
[Nexus 5 Original Android Development] tmihai20:
One way to be sure it is your device is by checking its IMEI or any other serial number. You should have one or the other. Maybe the short circuit solved something or it fixed something.
[Nexus 5 Original Android Development] deepakanand:
Not sure if its cable issue coz after reflashing kernel, it start charging just fine. For now I have flashed stock kernel and will observe for some time whether issue appears in stock too or not.

Thanks! :)
[Nexus 5 Original Android Development] xristoforosth:
Well , maybe it's not a different device (you will confirm that by checking IMEI), but maybe they changed the screen to an OEM screen and now you have a different screen.

You can never be sure, but sometimes small shops do that . (They take an original,working part from your phone and replace it with an OEM part)
[Nexus 5 Original Android Development] slater_g:
My phone gets gradually longer screen-wake times, the longer the last reboot was in the past.

Can you try to repuduce (you should have not rebootet the phone for at least a day)?

Wake the display by pressing the power button. Then, press the power button two times in rapid succession, to turn the screen off an on again. Do this a couple of times. Get a feel for the duration the screen takes to switch on.

Then do a reboot and repeat the experiment. Do you notice the off-on cycle is much faster? I do; it's very noticeable for me.

Thanks!
[Nexus 5 Original Android Development] mendozaram:
OFF. I turn On only when im gonna use it, i did use it like 3 times on that cycle
[Nexus 5 Original Android Development] Skyrocket2Paradise:
Unbelievable battery life. I was almost never on Wi-Fi pretty much all lte I was connected to my g watch the ENTIRE time. So bluetooth always on. Running paranoid android with r53. r53 has been the 4.4.4 gem for me. Thanks for all your hard work franco!!
[Nexus 5 Original Android Development] alcurtis93:
If that were the case don't you think chip manufacturers would have realised by now and Qualcomm etc would have drivers that did just that...?
[Nexus 5 Original Android Development] menting:
you mean like this?

http://osxr.org/linux/source/drivers/cpufreq/exynos4210-cpufreq.c

btw, chip manufacturers not doing it doesn't mean that it's not a valid optimization.

with your logic, there would be no need to optimize any code that's been in there for a while, as the code designer would know best.

In reality, there's no doubt they know a lot, but there's still plenty of stuff they don't know (nor the rest of the world knows). That's why you can still have tons of research papers / patents regarding chip design and chip optimization.
[Nexus 5 Original Android Development] alcurtis93:
That chip has a Max frequency of 1.2ghz not 2.3ghz like this phone...
[Nexus 5 Original Android Development] menting:
and your point???

this chip has 1.7GHz and has 16 steps.

http://osxr.org/linux/source/drivers/cpufreq/exynos5250-cpufreq.c

Does that mean a 2.3GHz part should have 22 steps?

how about when it gets to 3GHz? 29 steps?

valid steps to use != all steps that you want to use.

All it means that you have the option of using them for your application. Doesn't mean it's optimized if you use all of them

in DRAM (sorry, this is what I'm most familiar with), there's tons of MRS settings, but do you want to use all of them? no way.
[Nexus 5 Original Android Development] alcurtis93:
I have no argument to that. I guess the more steps are for battery and less are for performance? :)
[Nexus 5 Original Android Development] menting:
I have no idea either. That's why I can have all the theories I want :)

edit: I do know that when changing frequencies/multipliers in DRAM as well as in our logic chips at work, there's a few hundred cycles of delay waiting for the DLL/PLL to re-lock (JEDEC spec for DRAM), so that's what I'm basing my theory off of.
[Nexus 5 Original Android Development] WettbackMartyr:
Just so you know, OEM stands for Original Equipment Manufacturer. So what you probably mean to say is that they could have swapped out his screen with another non-OEM or low grade variant and kept his as it would have a higher value since it was an original LG part. Seems likely to me if the place was shady.
[Nexus 5 Original Android Development] xristoforosth:
Yeah, you are right about the definition of OEM, but usually the term OEM is used for not original parts nowadays.

Just look on ebay.

http://www.ebay.com/itm/Black-LCD-D...e_Replacement_Parts_Tools&hash=item540b9ec12f

http://www.ebay.com/itm/USA-OEM-LG-...e_Replacement_Parts_Tools&hash=item51be5e4b80
[Nexus 5 Original Android Development] Tzfardaya:
Just because ebayers are using the term incorrectly is no reason for you to as well...
[Nexus 5 Original Android Development] sluflyer06:
Am I the only one who can't use any kernel after 55?

Non-stop Force closes in all apps, random reboots every 30-60 seconds, hard locks. 56 does it, 57 does it, 55 works perfect.
[Nexus 5 Original Android Development] nldxda:
I'm getting lock ups.. Apps randomly not responding for a moment, long enough to make the not responding dialog pop up, but the app begins working again before I can click wait..

This is r57, stock 4.4.4 xposed, no other mods.. Also happened on r56..
[Nexus 5 Original Android Development] sluflyer06:
With both 56/57 mines at the point of if I load up anythign intensive like a game, it will reboot the phone within seconds every time, and when just idle in the homescreen I'll get random FC messages from running services. :(
[Nexus 5 Original Android Development] Tzfardaya:
Sounds like something in your roms is bugger up, try a clean flash of your rom, flash Francos kernel and try those apps/games again, before reinstalling your other mods. (xposed et al)
[Nexus 5 Original Android Development] sluflyer06:
That wouldn't explain why r55 works perfectly and 56&57 both have a problem. If it was the ROM would it also not happen on 55? This install is also on a couple weeks old from a full wipe because I tried L and then went back to stable android.
[Nexus 5 Original Android Development] nldxda:
I also encountered a random reboot

This is the clean flash! I removed the dalvik and bionic patches as well as the GPU drivers.. The ROM is now stock rooted 4.4.4, r57, and xposed with a few modules... [emoji22].. Guess another reflash is in order..
[Nexus 5 Original Android Development] Tzfardaya:
Depends on what is wrong... Keep in mind, the kernel doesn't deal in apps... Only threads and processes...

It could be that r55 is more fault tolerant of a certain malformed system call..

It could be that something you did yesterday corrupted the rom...

As to you only refreshing your rom a couple weeks ago, that doesn't matter.. It is possible to bugger a rom within minutes of install... It could be that the files you flashed from were corrupt from a bad download... Did you verify the checksum?

---------- Post added at 10:28 AM ---------- Previous post was at 10:25 AM ----------

Oh. Wait... You two are undervolting, aren't you?
[Nexus 5 Original Android Development] fatspirit:
Happy r57 user here!
[Nexus 5 Original Android Development] Tzfardaya:
Are you undervolting?
[Nexus 5 Original Android Development] Bl4ck3urn:
No problems so far with r57!
[Nexus 5 Original Android Development] TR2N:
I absolutely don't understand, what people are doing to their phones..

I am on latest PA 4.5 Alpha 1 (always dirty flashed to new versions) with enabled ART, r57 with activated PAM and color profiles, the rest stock. Phone looses 1-2% over night, performance awesome. No reboots or SOT since x versions. I can't understand your problems, sorry.
[Nexus 5 Original Android Development] Tzfardaya:
Usually, the people with issues tend to dig too deep into kernel settings they do the understand, undervolt incorrectly and too much, use far too many custom mods and tunes (which don't always play nice together, but the kernel gets blamed), add mods, remove mods, add other mods, reinstall the first mod, etc etc etc, and otherwise screw up their system..

Using your phone in a sane manner with minimal tweaks means you'll rarely have an issue...
[Nexus 5 Original Android Development] TR2N:
Exactly. I would not change anything kernel related with settings I don't understand. Besides that I am happy with the stock performance the kernel gives me.

There are many placebos and reported settings out there, that are copied and pasted into the updater app settings with no background knowledge. And than people are reporting weird problems that no one understands.
[Nexus 5 Original Android Development] sjknight413:
Or the people with issues are actually reporting actual issues with the kernel. Issues that the dev seems to not want to fix and you don't notice because you don't pay enough attention to your device or are so convinced that this kernel is the best thing since sliced bread.

Case in point, the glaring thermal throttling bug that none of you seem to want to admit exists.
[Nexus 5 Original Android Development] Playe:
Most of us don't have a thermal throttle bug
[Nexus 5 Original Android Development] sjknight413:
How? this isn't a subjective thing the bug is there.

use your phone until it is hot and your frequencies get throttled to 1.1ghz (which happens all too easy anyway), then watch as your frequencies do not rise again, they'll be stuck low until you reboot, and only if you reboot when the phone is as cold as possible.
[Nexus 5 Original Android Development] Aerowinder:
I haven't seen it since r57, but only been using it for a couple days. On r55 mine would lock at 1.9GHz. It was never warm enough to throttle, either. It was doing it for no apparent reason.
[Nexus 5 Original Android Development] Tzfardaya:
Problem is that unless we can reproduce it, we can't trial solutions for it... I've tried to replicate.. (even forced thermal throttling before)

Even Franco has said he's tried to replicate it... Letting his device overheat to trip the throttle... When it cools down, max freq climbs back up to the previous default..

So, if you are adamant that there is a bug (that we can't find) clean flash your rom, root, install Franco kernel, system monitor and fku... Do nothing else... Only install what I've listed.

Force your device into a thermal state (a hair dryer works great, just be careful not to heat your phone too much) and test for the throttle bug...

We are NOT saying the bug doesn't exist, but rather that. We. Can't. Replicate. It.

Normally my device never throttles... Why? I use a conservative base setting and Pam to limit the device so it runs at max sustainable speed...

Why do I do this? Because using settings that keep my phone just below my throttle limits is actually faster than letting the device throttle down to lower speeds than I run to bleed of the extra heat...

I still think it's something else in the setup assisting in the throttle bug...

But since we can't replicate it...
[Nexus 5 Original Android Development] franciscofranco:
I've left my phone while on stability test for over 2 hours, it was throttled to 1.1GHz and sometimes to 7xxMHz. After I canceled the test the frequencies were restored just fine back to where they belong. There is no magic in the code. Besides all my code is public, anyone is free to check it and point me errors if I've done then, but in this case most likely there's no crap code.
[Nexus 5 Original Android Development] sjknight413:
Well then forgive me if it isn't actually an issue but others have reported it too.

I clean flash everytime i flash a rom, i have tried flashing PA and the zip of your kernel, flashing PA then booting and flashing via your app, and the previously mentioned on stock 4.4.4. Everytime my phone was throttled to 1.1ghz after about 5 minutes of use and once it was throttled the frequency never rose, I even left it overnight on airplane mode and in the morning the frequencies were still stuck at 1190mhz.

I'm planning to flash PA 4.5 this evening so i'll give it another test and see if i can produce something useful.
[Nexus 5 Original Android Development] franciscofranco:
I'm sorry, no offense but I can't reproduce, so I can't "fix".=/
[Nexus 5 Original Android Development] Tzfardaya:
Does PA have any inbuilt kernel tweak apps?
[Nexus 5 Original Android Development] franciscofranco:
Just got back to Portugal after a 15h airplane trip and I'm completely exhausted. Nevertheless I want to share with you what I've been working on the last days (on the airplane too ihih) and a sneak peak, obviously unfinished, of what the next FKU might look.

Welcome material design.
[Nexus 5 Original Android Development] Tzfardaya:
It's funny that I say the exact same thing several times, and they ignore me, until you say it... :(

Maybe I should just go back to trolling the thread...

---------- Post added at 02:01 PM ---------- Previous post was at 02:00 PM ----------

L designed ui?
[Nexus 5 Original Android Development] sjknight413:
No

Well funnily enough he is the developer of this kernel.
[Nexus 5 Original Android Development] franciscofranco:
I've took my time to read all the new guidelines over and over again. It's a lot of new stuff... so I started from scratch layouts until I was satisfied. That was one of the layouts I made.
[Nexus 5 Original Android Development] Tzfardaya:
And that makes my answer wrong?

---------- Post added at 02:04 PM ---------- Previous post was at 02:04 PM ----------

Can't wait to play with the full app. ;)
[Nexus 5 Original Android Development] sjknight413:
No, but it certainly makes me less inclined to care about you refuting my claims.

Anyway, like i said i'm flashing PA tonight so i'll flash r57 and see if the problem persists, whether anybody cares or not.
[Nexus 5 Original Android Development] menting:
I've got to say I had the same (well, maybe the same) issue before as well

But for me it only happens when I update the kernel when the phone is(was) running hot. After reboot it would be stuck in a lowered max freq regardless of changing it back when the phone was cool again. However, clearing the app settings and then rebooting would always fix it, so to me it's not a big deal, since I only change a few settings anyway so it's like 20 sec of extra work.
[Nexus 5 Original Android Development] 5FOOTER:
It happens to me also but the temp doesn't have to be high enough to drop frequencies. Alls I did was manually put it back to 2.3 and all is good. I uc to 1.5 now and have never seen it do it since. So it doesn't effect me so I haven't reported it and for me its all stock but kernel no mods at all. Only like 15 apps installed if that many.

Sent from my Nexus 5
[Nexus 5 Original Android Development] sjknight413:
There we go!

I just clean flashed PA and the zip of r57. Straight away, like I mean upon first boot, my Max frequency was stuck at 1.5ghz. I left it five minutes and rebooted, phone is not hot in the slightest at this point, and lo and behold! My Max frequency is stuck at 1.1ghz.
[Nexus 5 Original Android Development] danbrown162:
That's real clean right there...:D
[Nexus 5 Original Android Development] Tzfardaya:
I not to say that's not happening, but iirc (unless Franco has made changes) the initial boot sequence always results in a thermal throttle situation..

Device runs locked at max freq until the os is booted and kernel takes over...

Give the device 5—10 minutes after boot (and idle) before you check for a locked thermal max...
[Nexus 5 Original Android Development] marquimsp:
I've tried R57 and R56 and I have a feeling that battery life is better with R55, is that possible?

Just asking... no need to ask for logs, screenshots, etc.

:cool:
[Nexus 5 Original Android Development] Playe:
Really just depends on your usage so could be for you, but personally I've had great success with r57.
[Nexus 5 Original Android Development] Tzfardaya:
Not saying your wrong, but here's a video clip of my phone being pushed into a thermal throttle state (you can see the freq fall in the video) and recovering completely back to default max freq...

here you go

Can you provide a similar video indicating when your phone sticks, and what you're doing leading up to that point?
[Nexus 5 Original Android Development] Nocturnal86:
Is your phone plugged in when this is happening? That is primarily when it happens to me when Im charging my phone and the temps raise and I get thermal throttled and then they stick.
[Nexus 5 Original Android Development] Tzfardaya:
Plugged in via USB or ac?