yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] sjknight413:
I'm afraid I've now reflashed CM and I probably won't come back to this combination of PA and Franco kernel as I have tried so many times to get it to stop throttling.

I left it sitting for twenty minutes after I left that last comment about it sticking at 1.19ghz and yet still the frequency did not rise so I'm giving up.

If I return to try it again I'll do a screen recording or make a record of some kind to prove I'm not lying if that's what you really need.

EDIT: as for when it stuck and what I was doing up to that point, it stuck on boot both times, and I did nothing except check the frequency and leave it sitting after locking it at the homescreen. It's not even like it stuck at the same frequency each reboot, they were different frequencies so it can't be any app or anything interfering.
[Nexus 5 Original Android Development] Tzfardaya:
It's not that we think you're lying, it's just that we can't reproduce it.... If we can't reproduce it, we can't start trying to troubleshoot / diagnose it...

Also, are you watching the freq in a system monitor or just looking at the freq page on fku...
[Nexus 5 Original Android Development] sjknight413:
Nope, was running on about 55% battery.

---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------

Looking at the frequency page on fku and using the system monitor in the app to double check after which confirmed it.
[Nexus 5 Original Android Development] Tzfardaya:
Okay, one "issue" with the freq page in fku, it doesn't run "live", you do need to browse away (to another page) then back for it to reload...
[Nexus 5 Original Android Development] sjknight413:
Which is why I confirmed it afterwards by using the system monitor within the app...
[Nexus 5 Original Android Development] The Gingerbread Man:
I pointed something out to Franco in a conversation where I managed to get fku to report incorrect speeds but this might be different to what your describing. Do you use per app modes at all? Disable the service in the fku app and try again. If you have the stand alone app disable the service there too. Then reboot. What I managed to notice was if a per app mode was set for the fku app with a Max cpu speed the app would report the max speed for the per app mode you created for fku app. Pressing home and swiping away fku from recents kills the app and pam service, then open fku app again and it would report correctly.
[Nexus 5 Original Android Development] sjknight413:
The first thing I do upon reinstalling fku is make sure the per app service is disabled, so it shouldn't be that that causes this. I'm pretty sure it is strictly a thermal throttling issue.

Could be important to note that this doesn't happen to me on any other kernel.
[Nexus 5 Original Android Development] Nocturnal86:
It seems to happen to me when I'm charging via AC and using the phone and it heats up. I haven't tried USB
[Nexus 5 Original Android Development] Tzfardaya:
Okay, I'll try ac when I get home..
[Nexus 5 Original Android Development] justibasa:
I'm running pa and have been for some time. I've never had a problem with the thermal throttle. It's not the rom or the kernel. It's the user. Sorry dude, but it's true and I'm the only one with the cajones to say it. No offense to you Tzfardaya. I just get tired of the users of the kernel whining and moaning about problems and not providing a log. It's gotten ridiculous. No log they should be completely ignored. Just my opinion.
[Nexus 5 Original Android Development] sjknight413:
Please enlighten me as to how it is 'the user'. There is nothing wrong with the way I'm setting this up, the rom + kernel is flashed, booted, and bam! Stuck.

Seems to me I've been doing this a whole lot longer than you have, so leave it out yeah?
[Nexus 5 Original Android Development] justibasa:
No need to be rude. If less than 1% of the users are having this problem then it's not the kernel. And you've been doing this longer than me? Hahaha, ahahahahaha, bahahahahahahahahaha! You wish.

By the way, 57 is running awesome, no problems and speedy. Thanks Franco.
[Nexus 5 Original Android Development] LiquidSolstice:
Maybe your phone does that, my phone has never done that, and I've been using Franco's kernel since r12.

This isn't political, this is logical; if you're able to replicate your problem with pure stock 4.4.4 with his kernel and no other modifications, then it stands solidly to reason that the issue is on your end. Whether or not you're willing to accept that is your problem, not anyone else's. Sorry, that's just the way it goes .

Getting defensive about it and claiming that "franco knows and won't fix it" is childish and stupid.
[Nexus 5 Original Android Development] sjknight413:
I could accept that it was on my end if I hadn't have brought this up a few times in the last few weeks with people backing me up. It is too easy for me to reproduce it for it to not be an issue with the kernel and like I said it happens with no other kernel but Franco's. I have never stated that Franco knows how to fix it but initially I assumed because it had happened to other people too and because it was clearly an issue with throttling it could be an easyish fix if looked into properly. I wasn't to know whether this was actually the case because the past few times I had brought it up I hadn't got a reply from Franco himself.

But I digress, I don't know why people are keeping this going because I have stated that I will not be returning to this kernel anyway as it causes too many issues, and with everybody so convinced it is faultless clearly I'm not going to get any form of support.
[Nexus 5 Original Android Development] LiquidSolstice:
A. Calm down, these are Android custom kernels, not political parties. No one here will bat an eye or shed a tear if you leave or come back, there is no need to be so dramatic.

B. I did not say that you were the only one to have the issue. I did say that it stands to reason that if the issue is not universally happening, the problem is on your end. There may be other people with phones like yours or doing something differently that you are doing. That's not a personal attack, that is logically deduced fact. Stop getting so damn defensive.

C. You don't know whether it was "clearly an issue with throttling", and you don't know that it "could be an easyish fix if looked into properly". Unless you're a kernel developer or you know Franco's source code inside out, you don't know any of this.

If a developer cannot replicate an issue and the overwhelming majority can not replicate an issue, it's a non-issue for the dev and you as an end user are an acceptable loss when computing effort/reward calculations.....except, there is NO reward for this. You're not paying for professional support nor are you entitled to it (although you're certainly acting like it right now with all the outrage you're displaying).

If you want to leave, leave. But if you slam the door on the way out and then you come back in to continue where you left off, you better believe that no one will be inclined to help you.
[Nexus 5 Original Android Development] nldxda:
No, not undervolting.. Stock kernel settings
[Nexus 5 Original Android Development] Tzfardaya:
Okay, so stock Franco kernel, stock 4.4.4 rom, patches applied and reverted (dalvik/bionic) xposed + modules.

Which modules? And how often are you getting reboots? Consistently being triggered at with the same app/situation?

Why no last_kmesg logs?
[Nexus 5 Original Android Development] nldxda:
Here's the most recent reboot logs..

Here's my modules:

It seems random when either random rebooting or freezes/ hang ups.. I haven't noticed it consistently in Amy particular circumstance..
[Nexus 5 Original Android Development] Tzfardaya:
Hmm, I would check your xposed modules... My guess is they're conflicting with something...

How often does it reboot? Once a day, once a month?

See if you can find a way to consistently trigger them... :P
[Nexus 5 Original Android Development] nldxda:
There were only those two reboots so far.. The freezes happen regularly but not too often.. But still annoying..

Also, I find the phone is running hotter on r57... Battery is at 109.6% atm.. Nothing intensive or out of the ordinary going on.. Same use style, but hotter phone..

Might go back to r55 to compare

Edit: actually, yea I'll try disabling modules
[Nexus 5 Original Android Development] Tzfardaya:
What's the ambient temperature? Compared to when you were running 55?

---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------

I don't know if it was you or a one of the others who seemed to be having this problem... But I do recall franciscofranco saying a couple times he was unable to reproduce the problem and as such was unable to determine cause..
[Nexus 5 Original Android Development] nldxda:
How can I measure ambient temp?? I onlyhad the heat problem today..
[Nexus 5 Original Android Development] Tzfardaya:
You don't know what the weather/temperature has been for the last few days? Indoors outdoors? Has it warmed up in your area recently? If the air is warmer than it was before, that might be why your phone is hotter, it can't dissipate the heat it generates as quickly...
[Nexus 5 Original Android Development] nldxda:
Been less than 90° outside today.. 79° atm.. Been outside with my phone all day... Temps here have been about the same past few weeks.. Not too much hotter.. Phone is 103.1° atm
[Nexus 5 Original Android Development] Technecium:
I wrote a post a couple of days ago about how to reproduce the thermal throttling and how I was able to fix it without rebooting the phone. Did anyone try to reproduce what I did? I didn't see anyone quote my post. Can anyone who suffers from thermal throttling reproduce clearing the throttling without restarting?
[Nexus 5 Original Android Development] Tzfardaya:
Is this the post you were talking about?

I saw that, but it seems to deal with clearing the stick... I haven't been able to get my freq stuck yet... always returns back to original max...

The only time it has "appeared" stuck is when I forget to change fku panes and back...
[Nexus 5 Original Android Development] Technecium:
Yup. That's the one.
[Nexus 5 Original Android Development] franciscofranco:
Something told your phone to reboot, the log is clean.

EDIT: **** the jet lag.
[Nexus 5 Original Android Development] nldxda:
Odd.. Well if it ever does it again, I'll post a log.. Thnx for checkin
[Nexus 5 Original Android Development] arpitnathany:
Hey there is a new android build out there guys just got the update yesterday its ktu84q its got a new modem. Other than that I don't know it was only around 2 mb in size.

Edit. Its only for a few countries

http://www.androidpolice.com/2014/0...us-5-build-number-ktu84q-now-pushing-to-aosp/
[Nexus 5 Original Android Development] scrack26:
I did check on google factory image site. It says for some specific country only.

4.4.4 Release 2 (For 2Degrees/NZ, Telsta/AUS and India ONLY) (KTU84Q)
[Nexus 5 Original Android Development] Juzman:
I'm on Telstra. Flashed KTU84Q modem over the L. Not sure what difference is. Modem has older version than L, but guess it should be better than L for my carrier.
[Nexus 5 Original Android Development] Technecium:
That's why I posted the procedure that I did a couple of days ago. There is no issue with the cpu freqs being stuck. It's that FKU doesn't redraw the page when you load it from recent list.

Dead horse... move on.

If there are users who are still not convinced, use adb to monitor the freqs. Drive the temperature up with a stress test and check it, let it cool down, check it again.
[Nexus 5 Original Android Development] sjknight413:
Sick of saying that when my frequencies are stuck I am using fku's system monitor to check. Or does that not work too?

Anybody with half a brain knows that fku's frequency page just reads the frequency values as you load it and isn't live, stop repeating it.
[Nexus 5 Original Android Development] Technecium:
I can't answer if System Monitor works well for what you're doing. Have you tried using adb?
[Nexus 5 Original Android Development] fredfox_uk:
Yep, adb is a much better way to check stuff like this - system monitor isn't truly "live" and is an informational tool rather than a tool to use for troubleshooting issues, unfortunately that isn't always obvious.
[Nexus 5 Original Android Development] sjknight413:
You guys are unbelievable.

System monitor tells you the frequencies your CPU is running at. It also tells you the Max frequency that your CPU is hitting. Whether you like it or not it is reporting correct information.

You are all so pedantic it's unreal.
[Nexus 5 Original Android Development] fredfox_uk:
I'd beg to differ, it's not being pedantic, honest :) Whilst system monitor isn't reporting incorrectly, it's not reporting everything. On my phone it shows I'd only used 5 frequency steps in the 3 days the phone has been on, but cpu spy lists 13 frequencies although some of those are only for a few seconds or a few minutes. It also has the scaling range which is what I've used in the past to check the status of the thermal throttling.

I've always found it useful to use more than one tool when troubleshooting and system monitor is now a very good tool to do this.

I hate to get involved in stuff like this normally because people tend to get so emotional about it.

I wish you the best of luck though, each to their own.
[Nexus 5 Original Android Development] Tzfardaya:
Just to clarify... I think you're talking about this screen on system monitor, correct?

While the other gent is probably talking about this page..
[Nexus 5 Original Android Development] Kobayashi_SRK:
So I get crashes a lot. Am I doing it wrong? I don't quite know how to replicate the situation, though I get these a lot. Typically, after the reboot, Play Store will update apps. Maybe something with auto-update causing my crashes? I dunno.

- r57

- KTU84P

- Using ART

- Background data disabled

- Sync turned off on pretty much everything

- I dunno what else! Ask me!

Here's my

# cat /proc/last_kmsg

http://pastebin.com/MhQJb8Qu
[Nexus 5 Original Android Development] fredfox_uk:
Could be, but even so that's not all that much better :)

Anyway, enough said :)
[Nexus 5 Original Android Development] Kobayashi_SRK:
Flash and forget. Stock settings through FKU app.
[Nexus 5 Original Android Development] KnighthooD:
work on cm11 and Cataclysm and aosp roms?
[Nexus 5 Original Android Development] Bogusetti:
cm is not supported
[Nexus 5 Original Android Development] DesertVelo:
Having the same frustrating wakelock! Going through recommended suggestions at http://xdaforums.com/showthread.php?t=2519294. Testing to see if it makes a difference.

Sent from the singletrack...
[Nexus 5 Original Android Development] FuMMoD:
Lmfao you should have seen that coming. People don't even use the search feature so you can only imagine.
[Nexus 5 Original Android Development] zephiK:
Works on AOSP ROMs but not CM-based ROMs. This isn't just exclusive to Franco but other kernels do not work for CM either with the exception of 1 kernel.
[Nexus 5 Original Android Development] eep2378:
Slight OT. I know a lot of people mentioned setting location to device only and that will allow the device to use GPS only "when it needs to". I have noticed it does provide better battery results, but certain weather widgets can't find my location when set to device only. I've tried Dashclock and a few others all with the same results. As soon as I switch to battery saving location mode, its all good.
[Nexus 5 Original Android Development] d.kozzer:
faux kernel was giving my phone insane wlan_rx_wake wakelocks, but your kernel does soooooo much better with this. It's not perfect, but manageable. Hoping r14 will improve upon it even more once I get a chance to flash it later.
[Nexus 5 Original Android Development] franciscofranco:
Its ok the laughs outscore the 1 stars :)
[Nexus 5 Original Android Development] mendozaram:
r14 its working good on Cataclysm ROM, 25000 on antutu with no reboots. Lets see about battery life in a couple of days.

PS: Enjoy your vacations [MENTION=3292224]franciscofranco[/MENTION]

PS2: Guys let Franco enjoy his trip. He said "No updates til next weekend" so...leave him in peace xD
[Nexus 5 Original Android Development] uh60james:
I had to restart my phone before it would work, give that a try.
[Nexus 5 Original Android Development] ChriKn:
[MENTION=3292224]franciscofranco[/MENTION] did you have time to look at my audio problem report ? Do you think it might be related ? What could I do to help you eradicate the problem ?

( i just read you were on the way to the airport. Sorry. Have a Nice trip !)
[Nexus 5 Original Android Development] ddominator:
Hi Franco, great job with the kernel. Are you using the hammerhead_defconfig when you compile the kernel? Or do you have a special config?
[Nexus 5 Original Android Development] jaggyjags:
Since r14 I get short disconnections of wifi and reconnecting back some seconds after, anyone else?
[Nexus 5 Original Android Development] pwc realtor:
Anyone else having GPS issues after upgrading to r14? Drove 25 miles round trip this morning and never was able to get a reliable GPS lock for Google Maps Navigation or Ingress.
[Nexus 5 Original Android Development] jm6001:
Thanks! That worked..

ACPU PVS: 2 with a time of .824626

did again

ACPU PVS: 2 with a time of .614251
[Nexus 5 Original Android Development] Pretoriano80:
I had the same issue,after running the command no output was shown so i restarted the phone and this time it worked,you should try.

Now back on topic,with kernel R14 i'm able to run Antutu just fine but i've also noticed that the score was way too low compared to a test made previously with stock kernel,but here's more detail about it:

Specs:

CPU = PVS 0 ( 2256 Mhz@1100mV)

Kernel = Franco R14

Rom = Stock 4.4

Tweak APP = FKupdater v11

Testing:

1) First Antutu run after installing R14 kernel

The test went fine but the score was around 19000 wich is way too low compared to the previously 29000 score achieved with Stock Kernel.Considering the result i was sure that the CPU throtle was too aggresive so i've set " CPU temp threshold " to 85 in FKU app and made a second Antutu run.

2) Second Antutu run with temperature threshold set to 85 scored 29650

Well,this result is much better i would say :D .

Anyway ,i went further and started to play with UV ,went from an initial -25 mV to -75mV and both Antutu and Stability Test (at least 10 runs of Stability Test every -25 mV steps were made) worked fine,no hard reboot or FC.But i did noticed that with Stability Test the CPU speed is going from 2256 to 729 continuously,even if i set Min - Max profile [MENTION=1534256]2256[/MENTION]mHz with FKU app.Another side note is that the device never feels hot, just a bit warm,so i have no idea why throttling is so aggresive.

P.S: for me R14 kernel is the best so far in both performance and battery drain,big thanks [MENTION=3292224]franciscofranco[/MENTION] for the great work.
[Nexus 5 Original Android Development] pchtc:
i was having the issue before r14

had it on all kernels including stock

Google created an RMA for me

they say its a hardware defect
[Nexus 5 Original Android Development] franciscofranco:
Ok boarding the plane now, i wont visit the thread during vacations, so until Sunday help eachother and make this into a positive community!!
[Nexus 5 Original Android Development] franciscofranco:
You gotta give me more info. The crash shows something related to SELinux, but I don't know what. What else did you change on your device?
[Nexus 5 Original Android Development] The Gingerbread Man:
These guys are trying to help you so please show a little respect they took a few minutes to try to help.

My advice is if no one here can help and Franco can't help because he can't replicate your issue you have to take things into your own hands. Search and research. Make notes if it helps. I'm sorry but it just seems your getting adigitated by the answers your being given when all these people are doing is trying to help you.

If you live in a hot country and having a particularly warm climate will increase your chance of being throttled, maybe its that? Maybe its aliens fuxking with you? Maybe you could reduce your cpu speed to 1.5 / 1.7 GHz and see if that helps?

I hope you find the answer in the end!
[Nexus 5 Original Android Development] JNewms:
Dude, you've been arguing for days about this. When are you going to soak in the fact that there isn't an issue with the kernel getting stuck after throttle? Users have explained how to remedy the situation, by closing the app. If you're not willing to take advice or help, perhaps you should abstain from commenting in development forums.
[Nexus 5 Original Android Development] Puzzlegirl:
He's left us: we're 'pedantic' remember. Moving along now [emoji4] Kernel's working perfectly for me.
[Nexus 5 Original Android Development] cobhc:
FYI for everyone. I installed KTU84Q on my UK Nexus 5, using a UK network and everything is working fine.
[Nexus 5 Original Android Development] The Gingerbread Man:
Is your signal any better? The way I understand this update is just that it's a radio for India, Austria and New Zeeland.

Edit

I live in the uk too, just curious :)
[Nexus 5 Original Android Development] Zyphur:
Finally had a chance to let the battery run on r57. 5h 12min SOT, 2% left. :D
[Nexus 5 Original Android Development] bjoswald:
So weird that you're having so many problems when it seems to be working fine for everyone else.

Have you tried "clean-flashing" everything after wiping your data/cache folders?

Have you tried fixing permissions?

Have you tried switching from ART to Dalvik? Many apps aren't yet compatible with it (e.g. Adblock+).
[Nexus 5 Original Android Development] Kobayashi_SRK:
I recently did a fresh install of 4.4.4 via flash-all.sh.

I never did any wiping of any cache at all. Switched to ART almost immediately. Installed TWRP 2.7.1.1, SuperSU v.2.01. I'm using SoftKeyZ, made no changes to AppOps, Wave live wallpaper, no hibernator apps. I ran stock kernel for a week with all the changes I currently have before installing r.55.

I experienced one crash with stock kernel, but it wasn't kernel panic.

I've enabled 2fa on my google account, and turned off background data. Sync is off for everything

The crashes happen seemingly at random. During a phone call, using Chrome, looking at settings, etc.

I'll try to record more details the next time phone crashes. I'll write a list of all my apps installed as well.
[Nexus 5 Original Android Development] Tzfardaya:
Wait, what type of crash on the stock kernel?
[Nexus 5 Original Android Development] Kobayashi_SRK:
That didn't take long. Phone crashed while using Carbon for Twitter. After reboot, I couldn't even open Terminal Emulator before a notification popped up for Franco kernel getting elevated permissions and the phone crashed again. My last_kmsg shows how short the uptime was:

http://pastebin.com/yCdf89Ez

I forget. I didn't record it.
[Nexus 5 Original Android Development] Tzfardaya:
No, I meant reboot/force close/or the like...
[Nexus 5 Original Android Development] 5FOOTER:
Softkeyz did this to me way back in the r20 something. Restore your stock symbols and see how that works.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Kobayashi_SRK:
Oh, it was a reboot.

I've restored the stock keys, and uninstalled SoftKeyZ Root. I'll report back if my crashes continue. Hopefully by then I'll have a huge list of all my apps/settings etc.
[Nexus 5 Original Android Development] Tzfardaya:
I usually work the other way, clean flash, Franco kernel, basic apps (no mods), test for stability, then add my mods one at a time checking for stability each time... That way I know what mod I need to remove when it starts acting up. ;)
[Nexus 5 Original Android Development] Technecium:
Is it just me? I have set all the governor tunables that adjust cpu frequency: input_boost_freq, sync_freq, hispeed_freq, etc to 300. They don't seem to affect performance. It is still as fast as if you use default.

PS: I'm not complaining, it's just an observation.