yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] DesertVelo:
The N5 is only compatible with fku beta at the moment until Franco merges the changes to the paid app. Once merged, the app will work on the N4 and N5. The new version will have the same functionally but with a different interface/UI.

Sent from the singletrack...
[Nexus 5 Original Android Development] nexusmaniac:
That put a smile on my face ;)
[Nexus 5 Original Android Development] P.Mobile:
anyone get reboots when running antutu benchmark app? everytime i try to run it using this kernel i get a reboot.. but when i run antutu running any of the other custom kernels i dont get any reboots
[Nexus 5 Original Android Development] bleuxeon:
Would you mind to use the search function?
[Nexus 5 Original Android Development] zephiK:
yep that is correct. no need to be sorry, were all here to ask/answer questions.

only way people would get upset at a question would be if its asked so many times that it bothers people repeating the answer over 10 times.
[Nexus 5 Original Android Development] P.Mobile:
lol.. i did.. but dont really see what im looking for.. i read franco say its the antutu app.. just wonderin why i only get it with this kernel that is all..
[Nexus 5 Original Android Development] PresidentMcCain:
This one trades the LGE thermal-engine (throttling manager) for Franco's custom solution, which is missing the aggressive throttling mechanism that is needed to keep some lesser-well-binned CPUs stable under all conditions.
[Nexus 5 Original Android Development] Testraindrop:
You (and all others running only benchmarks apps) can use Per-App settings to replicate stock behavior.

Just put for Antutu a very low Thermal throttle temperature and there you go, it throttles like stock and doesn't reboot.

Problem solved.
[Nexus 5 Original Android Development] PhantomGamers:
This is only a solution for people who purchase FKU though, and people experiencing this problem might be disheartened by it and wouldn't want to spend money to fix it.

I own FKU myself, but you can't expect EVERYONE to.
[Nexus 5 Original Android Development] yanner2012:
i know it, but I thought it could also work with other, why not?:laugh:
[Nexus 5 Original Android Development] Testraindrop:
I'm not expecting everyone to do so, but I'm not expecting Franco to solve it either.

According to PlayStore comments it might also be a Chip "feature" and Qualcomm forgot to put a workaround for this Errata.
[Nexus 5 Original Android Development] franciscofranco:
Exactly my guess.
[Nexus 5 Original Android Development] donwhall70:
Franco.. Can you solve world hunger while you are at it?

Sent from my Nexus 5
[Nexus 5 Original Android Development] DashingGentleman:
Is there a command to change bluetooth audio amplification? The minimum volume level is too loud for bedtime listening when using my BT headphones. Would really appreciate an option to lower the gain.
[Nexus 5 Original Android Development] franciscofranco:
I wish I could :( Bill Gates is doing his best at it though.
[Nexus 5 Original Android Development] franciscofranco:
Nope, BT audio doesn't go through the sound chip, its all digital.
[Nexus 5 Original Android Development] danyh_rrt:
Franco add two touches? for display on

sorry i'm spanish
[Nexus 5 Original Android Development] ahse0w:
Seems like r40 makes the device stutter. Try open XDA forum on chrome and use double tap to zoom in.

The device freezes for awhile then I am able to move again.

I am on stock with xposed.. No change to settings

Sent from Dog.
[Nexus 5 Original Android Development] PainfulLover:
There is your problem, stock rom! :o

Tried to replicate your freezing, no dice.

Cataclisma, r40, xposed, etc.
[Nexus 5 Original Android Development] jv.batista:
As promised, here are the logs
[Nexus 5 Original Android Development] Tylog:
I've made the fun in the last few days and version 38/39/40 tested over a long period , I can't really understand the issues from the most people, I never had in this days any significant lag, stuttering or whatever. The only, and that's really the only issues that I found is that the screen doesn't wake up from time to time with the first hit on power button , it happens sometimes I have to click two or three times, this is the only thing I noted, all other works without any problems. The most problems people have comes from the massive uv because people still believe the have thereby can extremely save battery which has been disproved by tests with instruments. All in all i can tell that all of the last builds works good.

Just my 2 cent. Have a nice day :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] jwee5467:
I concur. I don't understand all the UV everyone does here. All it will do is lead to a more unstable device. I think you can run this ROM stock and have killer battery and snappiness. Or you can run max freq between 1Ghz- 1.5Ghz for a longer discharge time.
[Nexus 5 Original Android Development] Peanuts.:
r38, r39, r40 absolutely no issues. Fast & smooth. I have undervolted, Xposed, Moto X, Adreno drivers.

From experience sod is usually caused by too much undervolt on the lowest cpu freq.
[Nexus 5 Original Android Development] Enddo:
because if you dont understand it. then that must make it useless right? what a narrow minded way of thinking
[Nexus 5 Original Android Development] SedyBenoitPeace:
With r39 I haven't any SOD.. But now with r40 yes.. Now I will flash r41-test and I will let you know!

Inviato dal mio fantastico Nexus 5 con Franco's kernel
[Nexus 5 Original Android Development] floepie:
Cataclysm is the stock Rom. Nothing is added to make it perform better.

I can also confirm sod on t41 after removing from charger.
[Nexus 5 Original Android Development] Shane_IL:
I'm on SlimKat 4.2, r41 now, no SoD now or when I was on r40.

Using ART runtime if that makes a difference.
[Nexus 5 Original Android Development] Technecium:
http://xdaforums.com/showthread.php?p=51600672
[Nexus 5 Original Android Development] jwee5467:
No. I know what UV does, but it does not improve battery life significantly enough to sacrifice the stability of your device. Especially for some of the amounts people are UVing to.
[Nexus 5 Original Android Development] mibtnt:
No UV here. The only setting I changed were:

Deadline

Temp threshold: 50 (was 60 and go sod also)

Vib amp: 60

Headset gain:-6

Only last night I dropped my GPU to 389 and temp threshold to 65 out of boredem.

Probably its because of an app?

I'm seeing some random/heavy drain due to android system and kernel. But then again these days I'm mostly on H+ and not WiFi

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] floepie:
Just looking for other commonalities. I for one do not lock my device (I do use Delayed Lock however), so no lock screen in use. Any with SoD who does keep their device locked?
[Nexus 5 Original Android Development] big_adventure:
I still have not heard of a single person having an SoD with load_threshold 0. Has anyone doing this had an SoD? This seems to be the only sure common factor so far. I also don't THINK I've heard of SoD's when people are using lower-than-max top frequencies, but that's not sure.

I have not seen any on r38, r39, r40. I have not tried r41-t, because I don't get SoD on r40.

I do use pattern lock, and I basically never have my phone time out into lock: I almost always click the power button to lock it manually, though the timeout is configured at 1 minute.

One thing I have not done is plug the phone in over USB - I do that very rarely; I use a Qi charger and use Dropbox or WiFi File Transfer if I need to move files.

I've mentioned this a few times before, but here goes again:

1. Does anyone running load_threshold 0 see SoD's?

2. Could someone seeing relatively consistent SoD's try configuring load_threshold 0 to see if that changes anything?
[Nexus 5 Original Android Development] eigokyoukan:
1) I've run load threshold from zero on up to 70 playing around and never had a SoD. The ONLY time I had SoD on Franco kernel is when I was UV a little too far down and a background task would lock it up in sleep mode.

2) pretty much same answer. UV was the cause of any SoD on my end and upping them solved it. Seemed to always coincide with certain background tasks wanting to process and I was too low on voltage and phone derped... Basically user error haha
[Nexus 5 Original Android Development] big_adventure:
Sure - I'm specifically talking about the "new" SoD's coming from r38-41t. There are a ton of user having SoD's running basically completely stock settings, kernel logs aren't being particularly helpful, so I'm trying to isolate what could be causing such a thing.

Obviously, too much UV is bad, but many of these folks aren't UV'ing at all.
[Nexus 5 Original Android Development] floepie:
How about SoD with or without fku app? I do have both fku app and have experienced sod. I do disable backlight dimmer and reduce vib. Other than that, stock.

Anybody with sod without fku app?
[Nexus 5 Original Android Development] Arstoien:
Most people UV to keep the temperature lower. Also it makes the device unstable if you go too far. Sensible UV helps with temperature, and if there's battery saving with it, it's a nice bonus.
[Nexus 5 Original Android Development] Tzfardaya:
Yes, and I've said that in several posts that the results I'm getting will be a result of my colorimeter and display... But... Since others in the faux gamma app thread determined that there seems to be two classes of displays, others with the same class as mine may get similar results....
[Nexus 5 Original Android Development] jwee5467:
Yeah I understand the temperature decrease, but for me it doesn't really impact the device too much unless I am watching a long video or something. As for the stability point of view that is the most important thing to me and I still manage to get at least 3 hours SOT even with a snappy and stable kernel like Trinity. I used to UV maybe -75 back in the day but found that tho you get a small battery life increase, it really wasn't worth it (maybe getting a extra 10-20 minutes SOT is nice but reboots are rough)
[Nexus 5 Original Android Development] cdx47:
Fair enough. Right now I am getting almost perfect 2.2 gamma with Piereligios version 6.6.
[Nexus 5 Original Android Development] Tzfardaya:
Glad to hear it... But keep in mind that the display tester app that most are using (and I'm assuming you are too) only checks the gamma at only one point in the range....
[Nexus 5 Original Android Development] big_adventure:
That's why, if you are going to UV, you need to test to ensure that you don't get reboots.

I have not had a single reboot or SoD on my N5 since I've owned it, I think. I use Franco, and I conservatively undervolt (because why not, if there is no penalty at all?), meaning 675@300, 700@422 and -25 everywhere else. Extensive testing by a number of folks has shown that you can UV much more at the low and high freqs than in the middle - Qualcomm/LG/Google are already pretty aggressive there. Since the phone spends most of it's time at 300 when not in DS, that's the biggest gain and biggest heat reduction in any case.

In my case, is there a significant difference in anything? No, probably not, but it's effectively free for me, since it has never once caused me a problem.

But again, a number of people claiming SoD's on the newest kernel versions are not UV'ing - they say that they are running stock voltages.
[Nexus 5 Original Android Development] zacomaco:
Audio Stuttering

Firstly, thanks [MENTION=4429898]bigknowz[/MENTION] for creating the issue and log cat. I was having stuttering issues for a while on slimkat without knowing it was a kernel issue. I've since tried all the popular kernels and, like you, the only one that has been decently successful is faux's.

However you're right [MENTION=3292224]franciscofranco[/MENTION] it does have significantly more battery drain (most probably because of the reason you stated) and I'm having to preserve battery like a ninja now when not using audio. Would the audio stack patches you talk about in r32-35 potentially fix this issue at the expense of possible side-effects? As I'm open to try possible solutions.
[Nexus 5 Original Android Development] edwardeutsch:
Hi guys! Little OT: i'll go to a concert next week...but audio camera quality is really bad with loud music. Is there a trick that can help me record a good quality audio/video? Thanks to everyone!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
Yes, buy a dedicated video camera...
[Nexus 5 Original Android Development] edwardeutsch:
Ohh tanks! Lol

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] coux:
No SoDs here, working perfect :D

-------

Nexus 5 - Cataclysm - franco.Kernel r40
[Nexus 5 Original Android Development] PetritH:
take a look here, give it a try

http://xdaforums.com/google-nexus-5/development/mod-jishnus-camera-t2516061
[Nexus 5 Original Android Development] Enddo:
if you're getting reboots then you're doing it wrong. UVing properly will decrease heat and keep the same stability. period
[Nexus 5 Original Android Development] Tzfardaya:
Problem is most people are too impatient to do it properly.... Takes a while to dial it in.. :P
[Nexus 5 Original Android Development] leAndroid91:
Hi guys,

since yesterdays nightly and franco r40 i had this problem for 2 times:

when my nexus's screen is of, i can't turn it back on by pressing the power-button.

nothing happens.

i can see that it's still running, because the notifiacation-led was blinking.

long press for restart still worked.

then everything went fine again.

is something like this known?

any advice?
[Nexus 5 Original Android Development] Tzfardaya:
Heh, always an idea to read the last 5 pages of the thread... This screen off death is the issue of the day lately...
[Nexus 5 Original Android Development] snives:
I'd be pissed if I could only get 3 hours SOT. I get 4 hours SOT while gaming, 6 hours of more basic use. But yeah... you should never get reboots unless you are doing something wrong like UV too far.
[Nexus 5 Original Android Development] icethegreat:
I was about to mention on how I haven't gotten any SOD's since I flashed 41 but I got a phone call at work, hit the power button, 30secs later tried to wake phone and it would not respond. Doh! Wasn't charging phone, and I'm on latest purity with Franco r41 all stock settings. I think the consensus that I've read that are having issues are people with stock settings or near stock settings on Franco... Will try to capture a log.
[Nexus 5 Original Android Development] jv.batista:
Another SoD with r40

will update to the r41t this afternoon
[Nexus 5 Original Android Development] yorici:
Actually, since I have a colorimeter, I have come to the conclusion that the gamma image is highly unreliable. Not only does it test just 1 value out of 256, it is also exposed to multiple uncertainties:

- viewing angle, changing the angle makes such a difference to the way you perceive the screen

- the screen is not perfectly uniform. It will matter where the 2,2 box is at

- Ambient light. Your environment also influences your perception

- Brightness

- The screen needs to get warmed up to for 30 minutes.

I can't say anything else than that the Display Tester should not even be used as reference for that singular value it tests. Too many variables...

(Of course you already knew that, Tzfardaya ;) just wanted to add to your statement)
[Nexus 5 Original Android Development] castaway1:
I had SoD with r41 test.stock settings, MAHDI ROM. Tryed to catch log but in syslog app there was grayed "Last kernel log" and had no time much for discovering whats problem.(work).
[Nexus 5 Original Android Development] tcat007:
My reference: r41, no flu app (I use trickster), uv -25 (only mod from default), don't use mobile data (always on WiFi), purity 4/6, charge at night (don't turn off), no exposed. No sod, no sound issues. I do believe battery is worse on r41, but not bad.
[Nexus 5 Original Android Development] vomer:
That makes sense :good: all the more reason to use the tweak! :D
[Nexus 5 Original Android Development] improperburial:
--------- beginning of /dev/log/main

I/dalvikvm( 5981): Enabling JNI app bug workarounds for target SDK version 11...

D/dalvikvm( 5981): GC_CONCURRENT freed 319K, 15% free 14268K/16596K, paused 3ms+2ms, total 29ms

D/dalvikvm( 5981): GC_CONCURRENT freed 270K, 14% free 14510K/16788K, paused 1ms+2ms, total 15ms

D/dalvikvm( 5981): GC_FOR_ALLOC freed 130K, 15% free 14621K/17004K, paused 15ms, total 16ms

D/dalvikvm( 5981): GC_FOR_ALLOC freed 51K, 13% free 14929K/17108K, paused 16ms, total 16ms

W/InputEventReceiver( 5981): Attempted to finish an input event but the input event receiver has already been disposed.

D/dalvikvm( 5981): GC_CONCURRENT freed 244K, 13% free 15079K/17332K, paused 3ms+1ms, total 21ms

W/InputEventReceiver( 5981): Attempted to finish an input event but the input event receiver has already been disposed.

Started having this issue after flashing to 40. I'm not able to get audio to come out of headphones if they're plugged in or from headset during call unless its on speakerphone.

Audio over Bluetooth works for calls and streaming without issue.
[Nexus 5 Original Android Development] rho789:
SoD with R40. Testing R41 since this morning. No SoD! Don't know if it help... Peace.

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] ChazzMatt:
Had SOD with r41 last night. Couldn't get the log -- was trying to type all that stuff into the terminal emulator and it just didn't work. Sorry. My first time trying to get a log like that. Was going to bed, so just turned off the phone.

Wasn't charging at the time of the SOD. I had just taken it off the charging pad. Turned the screen on (worked fine), saw I had some emails but didn't read them at that moment. Carried the phone into another room to do something, put the phone down. Picked the phone back up like 5 minutes later to read the emails, but screen wouldn't come on.

Rebooted the phone, tried to get the log. I messed up typing somewhere in the emulator. Wouldn't work. Went to bed. Wanted to sleep late this morning, so turned the phone off.

:(

No overclocking, no undervolting.
[Nexus 5 Original Android Development] Moh_Jay:
So what you're saying is that using the rgb sliders on stock calibration would be more accurate than having a color profile at 2.2 gamma on the display tester app?
[Nexus 5 Original Android Development] gparmar76:
I think its time for Franco to release a Milestone... I haven't had any issues with the kernel since r33...plus 4.4.3 is around the corner...timing for a Milestone seems about right.
[Nexus 5 Original Android Development] Tzfardaya:
Well, looks like another sod for test 41..

Stock rom, art,default fku settings.. (including voltages)

Logs in the zip...

Edit: oh, and cpu bin 4
[Nexus 5 Original Android Development] WettbackMartyr:
First SoD on r40. Everything became really laggy and system monitor showed all cpu's online around 1.5ghz. I run stock ROM, stock Franco settings, no mods or tweaks. No other problems to report. Very weird.

http://pastebin.com/VccDp4gr
[Nexus 5 Original Android Development] Tzfardaya:
Yes... A Milestone when multiple users are experiencing Screen off Deaths....

---------- Post added at 08:39 AM ---------- Previous post was at 08:38 AM ----------

No, we are saying that the display tester app is too limited to be of use testing the profiles....
[Nexus 5 Original Android Development] yorici:
No, you can have an accurate profile, but you can't be sure unless you have tested it using a colorimeter. The Display Tester app just isn't reliable.

The RGB sliders limit the range of colours. It's a fun tool, but I don't see it being useful other than for capping blue and green. The stock calibration already does for the first 8 values (I.e: First value Red = 255 (255- input), Green =184, Blue = 169). We don't need to limit blue and green for the rest of the range, which is what the sliders also do.. (Correct me if I'm wrong about the sliders here).

The problem with the sliders is that you can't increase it, while you can increase values in the Faux Gamma App in a way that RGB-values are higher than normal. Calibration isn't done by limiting, but by adjusting. When you have a perfect calibrated screen, you might limit the reds too increase the colour temperature overall (for those that prefer higher colour temperatures). Although, I haven't tested yet if limiting red evenly increases colour temperature..
[Nexus 5 Original Android Development] ChazzMatt:
:confused:

Exactly. I couldn't figure out whether he was trying to be funny or just hadn't been keeping up in the thread. The last few pages are all about Screen of Death reports -- two separate incidents just above that post.

Plus, Franco says he doesn't do "milestones" anymore:
[Nexus 5 Original Android Development] Tzfardaya:
Another sod...

Logs in the zip...

Changing threshold to 0 now to see if it helps...
[Nexus 5 Original Android Development] floepie:
I suspect there is a link between SOD and having the FKU app installed. On r40 I discovered that simply clearing the app's data resolved a CPU issue, and I have never adjusted any CPU settings, always at default settings. Is there anyone who does NOT have the FKU app installed but HAS experienced the SOD?
[Nexus 5 Original Android Development] gparmar76:
I haven't had any SODs...a few people having it doesn't mean its kernel related...
[Nexus 5 Original Android Development] zmafreak:
I've been using r40 since 8 hours and my turned dead twice. I've undervolted -50mv and the rest is stock. Is this normal ?

PS- I'm running stock ROM and what is SoD ?
[Nexus 5 Original Android Development] Tzfardaya:
Don't undervolt then... And sod is "screen off death" or "sleep of death" basically when the phone earlier won't wake up from sleep, needing a hard reboot...
[Nexus 5 Original Android Development] zmafreak:
Thanks.. I'll bump +25mv and I'll try again. Can you guide me to a stock nexus 5 kernel ? KOT49H
[Nexus 5 Original Android Development] Tzfardaya:
In the links of the op.....
[Nexus 5 Original Android Development] icethegreat:
Dude its kernel related. If you go back the last 20 pages, you'll learn something.
[Nexus 5 Original Android Development] Tzfardaya:
True, but the fact that it started for most of us on the same kernel, across various roms, various setups... And right after Franco included another batch of caf patches implies it might....
[Nexus 5 Original Android Development] ChazzMatt:
SOD is acronym for Screen of Death. Your phone is on, but when you hit the power button activate the display, the screen does not turn on. Like it's dead, even though the phone is still on and even though you may have just used it a few minutes before and everything was fine.

So, you have to press the power button for several seconds to force the phone to reboot. In the old days, you would just do a battery pull, but since the Nexus 5 has a non-removable battery, you have to do the "hold the power button for 15 seconds" trick.

Sometimes undervolting or overclocking and stuff like that can cause an SoD. What's peculiar about this rash of SODs is most people are not doing that. Just running stock voltages/frequencies, with a variety of ROMs. You are undervolting, but others aren't. I'm not, and had SODs with r39 and test r41.

I'm sure Franco will get it sorted out.
[Nexus 5 Original Android Development] msgfromside3:
If you mean paid fku, I am the one. I only have free fku. I had only one sod with r40 yesterday after running it without an issue for more than 24 hrs. I am on t41 and I haven't had sod yet.

Edit: wait. It seems I uninstall it after starting using flashify. I thought I still had it. So I didn't have fku at all when sod happened.
[Nexus 5 Original Android Development] Tzfardaya:
Well, you could pop the back off, remove a couple screws, possibly a backing plate then disconnect the battery from the main board, but it's usually quicker to use the buttons to reset it... :P
[Nexus 5 Original Android Development] zmafreak:
^ trolling doesn't end does it ?