yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] nerotix:
Hmm weird.. nothing special about the log, it does say cable was removed, disconnect and was rebooted by key, seems like something randomly derped.
[Nexus 5 Original Android Development] Tzfardaya:
Thanks, got it, but it would have been quicker if you had grabbed the backup script from the link in my signature and just posted/linked the resulting file... :P (I know, I know, I still have to finish the directions on how to use it...)

---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------

About 93 days....
[Nexus 5 Original Android Development] The Gingerbread Man:
Just about this music thing...

R43 fixes it but you have to bump your min speed from 300mhz to 345mhz. It seems certain devices can't decode mp3 correctly at super low speeds, others can.

Since using 345mhz min my music has played back flawlessly, screen on or off. It does cost a little in battery, not much.

Iv updated my personal settings post to reflect this and made some other changes.

I want to say a huge thank you to Franco for being patient with me while conducting tests and stuff. I can now enjoy my device to its full potential and this kernel is now pretty much perfect!

Anyone else who has music **** problems just boost your min speed to 345 MHz, if it works for me it would work for you, I had it worse than most....
[Nexus 5 Original Android Development] PresidentMcCain:
Sod on r43 after alarm went off while connected to charger.

#edit log attached
[Nexus 5 Original Android Development] jdec529:
That was the wrong log. Sorry.

Check this log out.

https://www.dropbox.com/s/zeof64vpmiughqh/2014-04-10_07.29.zip
[Nexus 5 Original Android Development] big_adventure:
I actually have that on my to-do list for later today. I'm home with one of my boys and he gets in the way of script execution. I'll pop it up a bit later and not be a lazy douche.
[Nexus 5 Original Android Development] Piereligio:
It is in my signature..
[Nexus 5 Original Android Development] floepie:
Wait, doesnt that profile set hot plug to 0? In which case it would dispel the notion that hot plug 0 prevents an sod.
[Nexus 5 Original Android Development] jdec529:
Yes but it wasn't a SoD from what I can tell. It just rebooted. And after looking over I realized that I didn't untick the set on boot option for my UV settings. Could have be caused by that. Raised voltages back to stock and will go from there
[Nexus 5 Original Android Development] :
[MENTION=4860519]Tzfardaya[/MENTION], I remember you posted a script a while ago with default Franco values, with the description of all the variables next to it? Could you link that, please? Thanks.
[Nexus 5 Original Android Development] Tzfardaya:
It's in the learner lounge... Search for all-in-one
[Nexus 5 Original Android Development] shaker2k:
[MENTION=470754]Franco[/MENTION].

You have been working your ass off pumping out updates and making this the best Damn kernel going!

So appreciate all you do.

Been a while since I've seen anyone(including myself) make a donation!

0C341344HM129753B

Here is $10. For you bro. Thanks so much for your development and keeping up communication with us. Truly feels like we are a team and not just users.
[Nexus 5 Original Android Development] AmmarGitham:
SOD on r42. last_kmsg attached.
[Nexus 5 Original Android Development] SunamY:
Sound on recorded videos don't work for me

send from my OMNIfied Hammerhead with the power of Trinity 5
[Nexus 5 Original Android Development] aeroseek:
Any changes to FastCharge? Doesn't seem to be charging as quickly on r43.
[Nexus 5 Original Android Development] MrMarques01:
SoD on r43. OmniROM latest nightly, kernel stock settings.
[Nexus 5 Original Android Development] thucoisao:
Is there any issues with sound on the right, guys?
[Nexus 5 Original Android Development] hellsgod:
Sould be fixed with r43.

hells

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] granets:
fixed in r43 :)
[Nexus 5 Original Android Development] SunamY:
Ok after clean flash all issues solved

send from my OMNIfied Hammerhead with the power of Trinity 5
[Nexus 5 Original Android Development] shaker2k:
[MENTION=1363323]vomer[/MENTION] or [MENTION=682880]gbm[/MENTION]

Are you still noticing better results with your settings with r43 as opposed to stock settings? Thanks!
[Nexus 5 Original Android Development] big_adventure:
Music stuff in r43 -

With my settings (leaving CPU min @ 300), Viper at High quality and r43:

Using plugged-in headphones: I do not get sound glitches on screen off using Spotify Extreme quality local downloads (320kbps AAC), something I saw consistently before.

Using BT headphones: same - no sound glitching on screen-off - something I ALWAYS saw before.

Now, I never had the derps that [MENTION=2918197]The Gingerbread Man[/MENTION] had : I'd see 0.5 - 2 seconds of dead space on screen off, and OCCASIONALLY a slight hiccup switching from WiFi to mobile or back with screen off. I have tested pretty extensively here, and can't force the derp at all.
[Nexus 5 Original Android Development] thucoisao:
I'm on r43 but having problem with sound on the right.
[Nexus 5 Original Android Development] granets:
remove all other sound mods. clear fku data and reflash the kernel. I have no trouble with r43
[Nexus 5 Original Android Development] vipinbp:
Audio was getting clipped for me.. That too after I dropped my phone from about 2 feet (with spigen ultra hybrid case on) got scared if it was due to that.. But this isn't happening constantly.. Not sure if this is due to kernel.. Reverted to my last favorite r37.. Gotta test if the issue is still there..
[Nexus 5 Original Android Development] GtrCraft:
Sod here and sod over there. I guess I am one of the guys that enjoy's the kernel like every franco kernel is. The best you can get
[Nexus 5 Original Android Development] big_adventure:
It might certainly do so for version r43, if it is indeed the case that the user has the settings properly configured. It wouldn't say anything about other versions and, if it isn't repeated by others, it could just be some kind of unrelated userspace derp.

Fact remains that a number of us who use their phones extensively don't get SoD's, and we still don't know the common factor. Forming a hypothesis is a pretty important step when it isn't totally clear. Now we just try to wait for verification.
[Nexus 5 Original Android Development] Tzfardaya:
Well, seeing as the person reporting said reboot, not SoD, it shouldn't have any effect on the hypothesis... And he later said it was likely due to UV...
[Nexus 5 Original Android Development] The Gingerbread Man:
I haven't had chance to run a complete battery cycle since flashing yet but so far with my settings it seems OK, nothing to complain about yet. I have changed my settings also. Post as ever with full details in sig

So your sayings its fixed? That's good, tested without your tasker profile forcing performance gov for a short period also?

and your saying still broken. Kernel version? Rom? Mods? Undervolt? Etc etc.

If no to all the above and your on r43 bump min speed to 345mhz...

Can you go into more detail please. Volume levels, particular tracks, mp3 / flac ??
[Nexus 5 Original Android Development] jdec529:
Since raising voltage back to stock haven't had a single hiccup. So if anyone is having trouble please run stock voltage 1st. The voltages I was running were the same I have had since day one. Just because u ran them before doesn't mean u can run them now
[Nexus 5 Original Android Development] floepie:
I have also read several accounts of receiving a notification which triggers a Led flash after which sod occurs. I wonder if there could be a link there and also if those who experience the sod also have a helper app installed such as light flow or led blinker, etc.

BTW. I'm running governor set to performance. Its just sublime. We'll see if battery life takes a hit. Tapatalk is smooth as hell.
[Nexus 5 Original Android Development] aeroseek:
Got SoD on r43. Managed to get logcat via ADB while it was in a coma. Also got last_kmsg after force reboot. Hope it's of some help.
[Nexus 5 Original Android Development] vipinbp:
The issue i came across was in r43.. Stock rom.. UV: lowest freq is at 700mv.. rest at about -50mv.. Using V4A..

I read your earlier post about bumping the min speed to 345mhz.. The issue was definitely reduced, observed it may be just once..

Now i'm in r37.. i'm yet to test it.. will report if there's anything..

Edit: verified on r37.. No clipping of audio..
[Nexus 5 Original Android Development] granets:
remove the viper mod. it's useless. bump up the volume boost in FKU, results will be better at no additional battery life. viper mod is so heavy on CPU I would not recommend it to anyone.
[Nexus 5 Original Android Development] vipinbp:
Lol.. No ways.. Stock music quality sucks.. Viper is a must have for me.. I practically can't imagine listening to music without viper and my personalized settings.. Thanks for the advice though..
[Nexus 5 Original Android Development] LibiSC:
No it's not... This is Android not ios and everything related to audio Mostly sucks
[Nexus 5 Original Android Development] big_adventure:
Lacking timestamps in the logcat means it's hard to precisely see when everything is happening. At the tail of your log, you can see the screen trying to turn on, then actually timing out and turning off. This happens at least once, maybe more. I have only reviewed the very tail end of the log, I'll keep looking (and I hope some others will as well).

Here is my favorite line, though:

W/art (21476): Failed to find ELF magic in /system/app/DeskClockGoogle.odex: dey

...that definitely made me giggle, I've not come across that before.

EDIT: For info, what settings are you running? Stock in FKU? UV? UC? LT0? LT60? etc. etc.
[Nexus 5 Original Android Development] Tzfardaya:
So reset back to stock/default settings to see if the issues go away... It's a valid diagnostic suggestion to help narrow down the cause...
[Nexus 5 Original Android Development] PetritH:
I use v4a since forever, set Fx Compatible Mode to Compatible and never had problems with battery.
[Nexus 5 Original Android Development] big_adventure:
Saying it is "fixed"? Well, for me, so far, with my use case, it seems like r43 takes care of the glitches I had. More testing will be required, but it's nice for the moment.

I don't actually use a tasker profile to bump to performance - that was someone else (I don't recall who).

---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------

Like anything else - in case of weirdness, make sure you try stock to identify the culprit. In other words, motion seconded and passed.
[Nexus 5 Original Android Development] bigknowz:
Tasker

That's me. I'm still on faux until the SOD issue is resolved.
[Nexus 5 Original Android Development] granets:
Dunno, I tried it, didn't hear much of a difference, and even in the app it is said that it loads the CPU and can reduce battery life(high performance mode requires a dual-core CPU!!!). So I decided it's not worth it. I guess you need really good headphones and a high quality track to hear any sort of difference. I manage to achieve a very good sound quality with just some FKU tweaks and some tweaks to Poweramp's EQ.
[Nexus 5 Original Android Development] big_adventure:
There's the guy!

FWIW, I still can't make an SoD happen on 4-core settings.
[Nexus 5 Original Android Development] aeroseek:
I did see the screen on attempts at the end. That was me pushing the power button probably.

Stock android. ART. Force GPU on. Stock franco except UV -50 across the board and Max GPU @ 320 with up_threshold@25 and down_threshold@15

I think the elves trapped inside my phone are revolting.
[Nexus 5 Original Android Development] The Gingerbread Man:
So when your getting the clipping is it screen on or off? Try so see with no undervolt. When your say clipping do you mean little micro lags in the music or long pauses for 5 seconds?

Haha my bad....
[Nexus 5 Original Android Development] PetritH:
Yeah, depends on user preference, i use high quality not super high, and with my headphones (10$) i really feel the difference.
[Nexus 5 Original Android Development] big_adventure:
I only loaded it in effort to bypass the audio glitch on screen-off, and it didn't help there, however, I have not noticed a real battery penalty in using it, and it does let you nicely customize sound to your liking. I'll put it this way, I'm not uninstalling it until Android builds a better default sound mousetrap, and I don't see that happening in the short (hell, the long) term.

You can correct sound in individual apps, sure, but it's so much more convenient to do it in one place and then leave the apps alone.

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

I mean, that's definitely what I'm guessing. No ELF magic sounds grim and dull.
[Nexus 5 Original Android Development] dastinger:
First SoD ever. On r43. Log attached.

Btw, couldn't get the last_kmsg don't know why. Isn't it available when the reboot is forced by pressing the power button for 10 seconds? Anyway, this is the dmesg, no idea if it's useful :/
[Nexus 5 Original Android Development] jdec529:
I do notice a small but to the battery with viper but for me it's worth it. If you know how to set it up and what settings do what it makes a big difference, even with my cheaper Phillips earphones. But I'm picky with how my music sounds. Just for the record in using viper and don't notice any clipping or stuttering with Google music, local & streaming
[Nexus 5 Original Android Development] vipinbp:
I've updated my previous post in reply to TGM.. I didn't see the issue in r37..
[Nexus 5 Original Android Development] granets:
well they did improve it a bit. it was so much worse on android 2.3... I think that maybe we are on the verge of a totally new android version - one that has ART on by default, maybe some F2FS support and audio fixes. I don't think it's too much to ask for those, maybe for the nexus 6 release?
[Nexus 5 Original Android Development] vipinbp:
Screen was on.. It was not stutter.. It felt like my earphones had a cut wire and the audio kept breaking.. Felt same with a brand new headphones as well.. Will test with stock voltage later and report..
[Nexus 5 Original Android Development] i860:
I don't undervolt and with screen on/off i have micro lags in the music with r43. Revert back to r42
[Nexus 5 Original Android Development] WettbackMartyr:
Another SoD using r43 completely stock ROM and Franco settings, no mods at all. Last_kmsg linked

http://pastebin.com/YiCh4byb
[Nexus 5 Original Android Development] big_adventure:
Oh, it's not BAD, it's just not all that flexible - there is no easy way to globally modify the base sound - no global EQ, no high and low processing like Viper offers.

I mean, I used stock android and spotify's extreme quality downloads for a long time with my SE535's and my Ziks with no real complaints. I care a LOT about how my music sounds.

OTOH, I wish I'd never developed an addiction to good headphones - before my first pair of high end 'cans, I was perfectly happy with crap buds. Now? I'd rather not listen than listen with a packaged headset.

---------- Post added at 07:03 PM ---------- Previous post was at 06:43 PM ----------

Quick note to everyone setting voltages using FKU:

The addition of 345 has messed up your custom voltages. It's nothing too bad, but 345 takes the place, and the assigned voltage, of 422, 422 grabs 652, etc.

Before the update, I had:

300 = 675mV

422 = 700mV

652 = 770mV (so, -25mV)

729 = 780mV

etc.

After installing r43, I have:

300 = 675mV

345 = 700mV

422 = 770mv

652 = 780mV

etc.

This isn't going to cause anyone any problems - it is actually increasing your voltages at most places - but it's not the curve you had before.
[Nexus 5 Original Android Development] GR0S:
Franco, can you add headset button click detection resistance sysfs?
[Nexus 5 Original Android Development] daniel84cs:
R43 SOD for the first time since I use the Franco Kernel.

No UC no governor and Hotplug custom setting.

Only UV with my stable table....

Last log here

http://pastebin.com/mrRXzG2c

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] chikimonke:
Log? Or at least settings you were using?
[Nexus 5 Original Android Development] Tzfardaya:
Think we need to write up a post on how to properly report bugs, with a step by step procedure of what to do prior to the bug report?
[Nexus 5 Original Android Development] chikimonke:
I know [MENTION=4790322]kufikugel[/MENTION] (from Slim ROM) wrote a satirical post on the Paranoid Android G+ page about how to write a good bug report, but he's far too active on XDA for me to search through all his posts to find the link =) I'm sure he'll see this and give us the link soon though. That man doesn't sleep...

Edit: But to answer your question, yes, maybe even put together a google form that asks for specific info and allows the user to attach a log file. I could try working on something if people think this would be a good idea?
[Nexus 5 Original Android Development] kufikugel:
This one? :p

https://plus.google.com/107859134357373490612/posts/cL6VfFN1D8R
[Nexus 5 Original Android Development] chikimonke:
Yes, that would be the one, you animal.
[Nexus 5 Original Android Development] Meowdib:
Just had an SOD, so I went back to r32 for now. v43 + stock
[Nexus 5 Original Android Development] Tzfardaya:
And I'm curious why you felt the need to inform us of your decision to revert....
[Nexus 5 Original Android Development] The Gingerbread Man:
If playing at 345mhz helped try with 422mhz.

Again try using a higher min freq. For me that was the only solution to use 345mhz.

Also both of you guys should know if your trying to play Flac tracks that won't work out well as its a know 4.4 bug.

I'm running 345mhz at the same voltage as 300mhz, 650mv in my case. No sod or reboot etc
[Nexus 5 Original Android Development] unknown1205:
was on r41 and had 2 SOD, then updated to r43 and less than an hour, had another SOD. stock settings
[Nexus 5 Original Android Development] chikimonke:
Alright, here is my first draft for a bug report form. [MENTION=3292224]franciscofranco[/MENTION] send me a PM with your e-mail and I'll share the form with you so you can see the results. Also, everyone, let me know what you think. Should I change or add anything?

Second draft already, added option question about Dalvik vs ART
[Nexus 5 Original Android Development] Bobtehblob:
I feel like the sound issues really highlight the fact that not all chips are equal as a wise man once said ;) I've not had a single playback issue the entire time I've owned this device and this is using r1-r43! Perhaps I'm just lucky!
[Nexus 5 Original Android Development] Web_E:
SOD on R43 (previous versions as well)

- Stock ROM

- Stock Settings in FKU.

- Sorry, couldn't collect the log. But before flashing r43, I cleared FKU app data. Almost 10 hour without SOD. Then I remembered I have not loaded the color profile in FKU. After loading color profile, within an hour got SOD. (bit busy these days, so now back to r36, can't confirm whether this is the issue)
[Nexus 5 Original Android Development] Tzfardaya:
Looks good, can't think of anything to add right now, but we can always tweak it later..
[Nexus 5 Original Android Development] TJKV:
Maybe add some data validation there..see the entry I just made :p

Also allow editing the entry?
[Nexus 5 Original Android Development] chikimonke:
I'm going to plead ignorance on this, I see what you did, but how do I keep that from happening?
[Nexus 5 Original Android Development] Tzfardaya:
Maybe a field where they can list which dalek exposing modules they're using...
[Nexus 5 Original Android Development] marf28101995:
Pa 4.2 Beta 3

R43 uc uv so far so good.. Not a single SoD

Obrigado Franco pelo excelente trabalho (; ( thanks Franco for the great work)

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] chikimonke:
Done and added a section for any other system mods like v4a
[Nexus 5 Original Android Development] TJKV:
Simple really. If you used the text/paragraph text/checkbox fields you can see a Data Validation tick box under Advanced Settings. You can enter simple number/text patterns or use Regular expressions :)
[Nexus 5 Original Android Development] The Gingerbread Man:
When your done let me know and I'll link it in my learner lounge thread (universal post) ;)
[Nexus 5 Original Android Development] chikimonke:
Hmm, still not sure. I want to make it so that if you select None in settings changes, you can't select anything else. Not seeing how to do that in that option. I figured out that I can make the text boxes for logs to require an URL in them, though that doesn't allow the None response anymore. Even simple coding like this is not my strong suit, I'm a mechanical engineer by trade. =)
[Nexus 5 Original Android Development] neriamarillo:
Maybe an option to add the PVS ? To see if someone is undervolting way too much for that chip?
[Nexus 5 Original Android Development] chikimonke:
What are all the options? 1-4?
[Nexus 5 Original Android Development] Tzfardaya:
0 to 6 iirc

---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------

But there should be a disclaimer on that page similar to the cm one about "errors with overclock and undervolt should be ran with default freq/voltages to replicate before logging."

---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------

Since UV can cause many different issues, and when Franco put in the oc option he said he wouldn't offer tech support for them...
[Nexus 5 Original Android Development] ConMcCRay:
Just had a SoD on r43 how do I get a log?
[Nexus 5 Original Android Development] zmafreak:
Almost 5 hrs 30 mins On screen time with r42.. -25mv undervolt without underclock. Is this good ? Pls suggest if I can increase on screen time.
[Nexus 5 Original Android Development] Tzfardaya:
Syslog app from play store
[Nexus 5 Original Android Development] G-Bus:
I still have right ear sound clipping even on r43.

Sent from my Nexus 5
[Nexus 5 Original Android Development] ConMcCRay:
https://docs.google.com/file/d/0B7CYvtWmT0uZeENkODJjcGg4Zk0/edit?usp=docslist_api that's the last kernel log I hope it helps. I was listening to music on r43 and had a SoD
[Nexus 5 Original Android Development] big_adventure:
Liking the bug form.

You may want to convert the ROM choice into one radio "stock" one radio + field "other AOSP ROM - list rom and version." This will a) maybe limit some issues to certain roms or versions and b) help weed out those using CAF ROMs who don't know it.

You also might want to add text fields for EACH mod class done - knowing what governor mods or what hotplug mods could be useful.
[Nexus 5 Original Android Development] i860:
I try with 422mhz and still the same, just normal mp3. Full log attached.
[Nexus 5 Original Android Development] snives:
That's about what I got on R39 when using my phone for phone/text/web browsing. If I use it for gaming I get more along the lines of 4 or 4.5 hours.
[Nexus 5 Original Android Development] RobbieL811:
Are you undervolting? When I reduced my undervolt, it made my headphones work properly. Test playing music with stock voltages & see if it works.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Exostenza:
Got my first SoD ever on r43 on this phone. I tried to get the kmsg with a program but apparently I deleted the text and can't retrieve it....
[Nexus 5 Original Android Development] G-Bus:
Nope, just flashed the kernel didn't change anything.

Sent from my Nexus 5
[Nexus 5 Original Android Development] RobbieL811:
Have you tried setting min frequency at 345 or 422?

Sent from my Nexus 5
[Nexus 5 Original Android Development] apeiron6:
I'm using this kernel since version r37. I tried every versjon since and never experienced SOD. I undervolt CPU 50 mv , running Slim 4. PVS 1. Great kernel , thanks Franco.

Sent fra min Nexus 5 via Tapatalk
[Nexus 5 Original Android Development] G-Bus:
I usually dont play with frequency. I reverted back to r37.

Sent from my Nexus 5