yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] bigmem:
Hi [MENTION=3292224]franciscofranco[/MENTION] been testing r34, and i'm no longer getting redraws on go launcher or sound issues, memory seems to be ok but i'm still having major reboots when I disconnect from casting please please can you see if you can sort this. There is no issue with this on r32, problem first appeared for me on r33 and seems to have been carried over to r34, major issue for me as I cast a lot. But i'm loving r34 just not the freeze then reboot. Hope you can help. Logs attached. Also can anyone else check this out on r33 and r34 I can't be the only person with reboots after stop casting.
[Nexus 5 Original Android Development] laureanop:
Running the latest test 34 and the battery is insane at stock Franco settings.

I'm at the point where per app modes will only be used if I'm gonna be two days away from a charger!!!
[Nexus 5 Original Android Development] matesc:
Hey [MENTION=3292224]franciscofranco[/MENTION]!! Thank you for the new build. Unfortunately the right-ear-clipping-thingy is still there after a call. Have you please read my newest observations with logs?

http://xdaforums.com/showthread.php?p=50622885

Also it seems that you have to turn off and on the screen for a color profile to apply...

(But I didn't read the git, so maybe it is intended...)

Thank you in advance!
[Nexus 5 Original Android Development] joyj112:
Memory management is insane .... always stays around 1.3g free...
[Nexus 5 Original Android Development] FAdrums:
Flashed new test 34 and as expected and usual working beautifully!

Thank you [MENTION=3292224]franciscofranco[/MENTION]

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] bigmem:
Ok i've been away and tested on all music setting being stock and your right this happens as you say in your link. I just tested on r32, r33 and r34 as well as stock. Starts to have issues on r32 with sound being distorted in one ear then by r33 and r34 major clips and chirps and cut out of right earphone. No issue on stock kernel. I'm guessing something to do with the way kernel deals with power for sound. As the issue appears after using hp's then to speaker on phone and then back to hp's. Hmmmm. Def a problem here......maybe something that allows for the gains to be adjusted is having side effects? All my settings are stock on stock rom, not under volting or touched any sound settings in fku. Not using a dsp on google play as well as youtube, not an app issue imo,
[Nexus 5 Original Android Development] matesc:
Thank you. Maybe the issue has nothing to do with a call, but only with switching between HP's to speaker and vice versa. I've got to test it.

edit: nah.. you´ve got to make a call and then or before to call set gain to minus 1 and play music after for the issue to happen.
[Nexus 5 Original Android Development] Luigi_2:
How long have you been up ?
[Nexus 5 Original Android Development] zukа:
Hey everyone,

I'm still experiencing memory leaks on Franco's R34 test build. After around 10 hours of uptime (and especially after using the camera) everything seizes up, I can only one run app and I have to hard reboot to fix it.

How can I best help Franco to troubleshoot this issue? How would I generate good logs etc to help next time it happens?
[Nexus 5 Original Android Development] Stevemeister:
Why do you need 1,3GB free RAM memory? Free memory is wasted memory.
[Nexus 5 Original Android Development] i860:
Same her, went back to r32, till franco will find a solution.
[Nexus 5 Original Android Development] kraehetest:
this ist not possible with a stock rom? Have you Googles Android or a Mod or exposed...?

If you have googles android, can you open your stock cam, take a picture, close cam, and then take another screenshot from your memory management.
[Nexus 5 Original Android Development] Vollspacken:
what changes will be on the new r34? cause i can't find any changelog on his github for his test-kernels.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] bigmem:
I'm not even playing with the gain settings. All stock even player no external eq or secondary amp app and still same issues as you. Its def to do with aux and speaker diversion of power or how the kernel deals with sound management, n5 has only one speaker on bottom and one for ear piece. So when its going single to dual stereo headphones is where the problem happens.
[Nexus 5 Original Android Development] antypas:
Definitely a problem with memory management with r33. I'm experiencing redraws with some apps. Unacceptable for a 2GB device...
[Nexus 5 Original Android Development] fasolka:
When WiFi is on and screen off battery drain very fast, but if you use screen off and WiFi off battery life is good. I use like this 2 days without changing and I still have 30%

Paranoid Android beta 6 + Franco 33
[Nexus 5 Original Android Development] The Gingerbread Man:
Unacceptable to come with a tone like that when the kernel is made for free. Please at least try to be a little more courteous. Anyway if you use the latest test version you will find many improvements on memory management.

Your settings should be

Sleep policy=never

Always scanning =off

WiFi optimisation = on
[Nexus 5 Original Android Development] big_adventure:
Is it possible that this is related to the known amp imbalance in the N5? Anandtech did a breakdown and found that there is massive clipping in the top couple of volume clicks in one channel on the N5. It's kind of a shame, since the phone did beautifully below that - like, significantly better than the iPhone 5S or some other devices. Their advice? Don't use the top couple of notches and everything is fine. I use two sets of headphones: SE535's on a cord and Ziks without. I can't physicaly take the volume of the Shures in the top two clicks without ear bleeding, so it's not a problem there, and, as the Parrots are BT, there's clearly no issue there.

Why the issue would be different between different kernel builds, I can't say. Just that, according to empirical testing done with expensive test kit, you're never going to be totally happy on a cord (thus, using the integrated amp) on the N5 in the top two volume notches.

Here's the link to Anandtech's piece. link

What is odd is that you are seeing your issue in the right channel, where they saw the issue consistently in the left. Either it's hardware differences, or, as they state in the article, the Nexus is actually pushing a TON of voltage from the headphone amp and maybe it's causing your setup to futz up in the channel that is "working" while leaving the channel that is "broken" alive? Especially since you've modded up the amp output in the mixerpaths.xml file?
[Nexus 5 Original Android Development] antypas:
:cyclops:

Unacceptable to say things I didn't say ... defender of the universe.

Did I say the kernel is unacceptable? Did I say Franco is unacceptable? Did anything offensive come out of my keyboard?

No! I did say that

having redraws and app reloading on a 2GB device

, without using any heavy app in the meanwhile, is unacceptable.

What I really did is ... state the OBVIOUS. :cool:
[Nexus 5 Original Android Development] akash3656:
#StartOfRant

Who said free RAM is wasted RAM ??? Android uses what you call as "free" to cache apps.

As of today, most if not all OS use "free" RAM for caching. So technically, you want the OS to use less RAM so you have more RAM to cache apps and services (which is why I bought a Nexus device as the OS has a lesser overhead).

EDIT: There is a reason why when you have hardly any RAM for caching apps, you will get a lot of redraws. The Galaxy Nexus does this even with 4.4 ROMs.

#EndOfRant
[Nexus 5 Original Android Development] vomer:
I have been looking into it, but they will likely remain the same as I have not seen much battery impact with more changes.

Sent from my Nexus 5
[Nexus 5 Original Android Development] The Gingerbread Man:
Blimey, got a bit of roid rage this afternoon have we? The way I understood it is that the redraws are unacceptable when we have so much ram. If you kept up with the thread you would know its an old issue and tomorrow fingers crossed the official r34 should be ready for general public. Please, chill
[Nexus 5 Original Android Development] bigmem:
This only occurs on with loss of channel in one ear and only on r33 and r34 not on stock kernel. Test it yourselves. Even on stock everything no extra amp app. So it must be in the kernel build after 33.
[Nexus 5 Original Android Development] franciscofranco:
3.4.82 or not its redundant. Sabermoded what?

Yep.

Yeah the display controller was not happy for some reason, I don't know why.

I acknowledged the problem some are having but I cannot reproduce. I've tried three different headphones, I simply cannot :'( Without reproducing its very hard. Besides I looked into the logs and seen nothing wrong. I don't know what else to do at this point.
[Nexus 5 Original Android Development] matesc:
:(

did you follow these steps?

set headphone GAIN to minus 1,

make a call without headphones

play music on highest volume step

....ta daaaa- issue here..

i will do a clean instalation with flash.all script when i come home, to reproduce again..
[Nexus 5 Original Android Development] sirovai:
If i set Sleep policy=never, when screen is off the wifi connection is disabled? In this case if i set 2G only (when i'm on 2G the data connection is broken because the roaming) i'll not receive notification?
[Nexus 5 Original Android Development] Wenzo2:
[MENTION=3292224]franciscofranco[/MENTION]

There was a discussion in these pages for a better management of thermal throttling and the ability to disable some core with per-app mode. Probabily you don't read these posts so i linked it. http://xdaforums.com/showthread.php?t=2508284&highlight=core&page=1951

Maybe 3 core at 1,2ghz had better performance and lower battery drain than 4 core at 960mhz...

only read this...
[Nexus 5 Original Android Development] ArtieQ:
This kernel should improve the battery life right? I'm not sure what to say yet, but I think the battery drains a bit too quick under usage..
[Nexus 5 Original Android Development] The Gingerbread Man:
Sorry your right I got mixed up then, the wording is different than I remember! Here's a screen shot showing how to correctly set it. Apologises to those who I answered wifi related stuff to I gave you the wrong advice! Below image shows how to set it correct
[Nexus 5 Original Android Development] Tzfardaya:
Well now... That's interesting....

Try to post a message about a test on mega34 and encounter a potential issue with test34(feb27)...

Might just be the settings I had left over from the test though... (looks like it was the settings.. Didn't happen this attempt)

Anyways, had dev-settings to kill activities and no background processes set and left the phone idle overnight... Ram used grew from 30% to 50%... No phone usage... But again, this test is out of date... I'll run the same on test34 today (will be some phone usage though)

I'm trying to see if the Android system/kernel/gel are the issue for growing ram usage vs used apps...

If I screenshots the ram usage prior to an app, them again after using an app on these devices settings, used ram should be the same if the app isn't leaking, if the ram use grows while the phone is idle, then it's likely to be the system leaking. (or the few apps that still exist backgrounded)
[Nexus 5 Original Android Development] sirovai:
Actually it was very strange. :p

---------- Post added at 02:47 PM ---------- Previous post was at 02:32 PM ----------

I think you can try to increase load_treshold to reach this situation.
[Nexus 5 Original Android Development] Wenzo2:
Yes... But you can't do that with thermal throttling
[Nexus 5 Original Android Development] The Gingerbread Man:
Here's a couple of new screen profiles from me

TGM_WP31(V1) (white point at 31) https://www.dropbox.com/s/r7hlcnzq52jhuei/TGM_WP31(V1)

TGM_WP32 (V1) (white point 32) https://www.dropbox.com/s/fkhq350cscnj2rq/TGM_WP32(V1)

Not sure if these will be final, hence the V1 but I'm happy with them. Feed back is welcome.

Wp31 aimed to have slightly lower gamma, wp32 has slightly higher gamma.
[Nexus 5 Original Android Development] sirovai:
You can increase thermal throttling too
[Nexus 5 Original Android Development] Wenzo2:
It was only a suggestion for improve thermal throttling control to get better performance and better battery saving...
[Nexus 5 Original Android Development] bigmem:
I news on my issue with reboots after disconnecting from casting?
[Nexus 5 Original Android Development] franciscofranco:
I've read that, I'm still thinking about the matter.

Don't do that, killing activities in the BG is really bad for the device!
[Nexus 5 Original Android Development] vomer:
added :good:
[Nexus 5 Original Android Development] The Gingerbread Man:
You can remove the v4 one, the wp32 replaces it :thumbup:
[Nexus 5 Original Android Development] joseph168:
I have problem with r34 connecting with my home WiFi, I run YouTube and search, there is no image show. Please see below picture. Anyone face the same problem?
[Nexus 5 Original Android Development] franciscofranco:
No idea at the moment, saw a crash on the iommu stack, don't know why.
[Nexus 5 Original Android Development] franciscofranco:
No.
[Nexus 5 Original Android Development] bigmem:
Have you tried to re create the issue? It happens at every disconnect from cast on r33 and r34, not an issue on r32.
[Nexus 5 Original Android Development] bigknowz:
Portfolio Link

[MENTION=3292224]franciscofranco[/MENTION], the Portfolio link in your signature isn't working http://franco.3-seiten.com/resources.html

Also, are you going to make a CruzerLite case for the N5?

Looking forward to r34, r33 is amazing. Not sure how you have at least doubled battery life vs. GNex with a battery that has 30% more capacity.
[Nexus 5 Original Android Development] maksud_ans:
hai franco today test r34 battery backup very well but when I playing game after 5 minutes mobile very hit .battery temperature 42° goes.
[Nexus 5 Original Android Development] sirovai:
Just flashed the latest r34. It seems a little more stutter than the previous r34, especially when open/close an app.
[Nexus 5 Original Android Development] Tzfardaya:
For daily use I don't.. I thought (perhaps incorrectly) that it would keep apps from launching In the background and the few apps I launched to set up from interfering with the test I was running...

Is the killing activities what caused the 2/3's growth In ram usage?

For daily use I run all dev-settings I'm their default States...
[Nexus 5 Original Android Development] sirovai:
I'm=in?...
[Nexus 5 Original Android Development] Tzfardaya:
Yes.. . You caught that the same time I did... :P

Edit, only caught the first one... Oops, both fixed now... Evil autocorrect.... :P
[Nexus 5 Original Android Development] Luigi_2:
The gnex's chipset is old and it uses alot of power :rolleyes:
[Nexus 5 Original Android Development] sirovai:
Excuse me for the "grammar's Rambo mode ON" but it was very difficult to read, especially for non anglophone users and mostly for me. :cowboy:
[Nexus 5 Original Android Development] vomer:
no issues here... give it some time to settle
[Nexus 5 Original Android Development] thecryof:
Latest r34 all good here so far... :)
[Nexus 5 Original Android Development] Tzfardaya:
No worries, I usually check for things like that before I hit submit..

I've been known to do the same for rouge vs rogue... (red/pink/makeup vs unruly/uncontrolled/rascall)
[Nexus 5 Original Android Development] sirovai:
Ok! P.S.: vomer_balanced is amazing. I tried every colour profile but this still remain the best for me! :good:
[Nexus 5 Original Android Development] SuperiorTek:
This happens to me as well my phone reach 46° after 20 mins of playing a game. Very hot. Is this normal?
[Nexus 5 Original Android Development] vomer:
Always happy to hear back how people are liking it :D :good:
[Nexus 5 Original Android Development] fcisco13:
I know it's your phone, i know it's your ears... But why would you listen to music at 100% volume? I have viper4android set up and i never go over 50% volume.

Whatchu talking bout willis!
[Nexus 5 Original Android Development] franciscofranco:
Battery temperature != cpu temperature.
[Nexus 5 Original Android Development] matesc:
And how exactly does your question help with that issue? :confused:
[Nexus 5 Original Android Development] pikachukaki:
Im having glitses and distrosion with latest preligio v6 color profile... (Sorry if i wrote the name wrong..) :P i can't replicated cause even that i record the screen i view it with amoled color profile and the distorsion isnt there!!
[Nexus 5 Original Android Development] yorici:
Something like this? http://en.m.wikipedia.org/wiki/Colour_banding

If so, it means the profile is not for you. Every display is quite different. Test banding with display tester app in the playstore.
[Nexus 5 Original Android Development] gknnn':
Franco you're killing me.

I'm at vacation in Amman (Jordan).

I bought an external charger for the trip but i won't need it thanks for #34.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
Here's how that question helps with the issue...

Yes, people say the the issue wasn't as prevalent in earlier kernels, so maybe a commit recently has made the issue more noticeable, but, what happens if you lower the volume and adjust the boost/gain to get the same volumes?

(when I get everything after work I'll try to cause the issue on my phone, and see what happens with gain/boost too, but I'd still like to see your results.)
[Nexus 5 Original Android Development] pikachukaki:
Something like this with red lines at the side of the distorsion...

But it dosen't show all the time....i apply the profile again and when i see them again i will take a pic from another phone
[Nexus 5 Original Android Development] yorici:
Maybe a noob question, but is anyone experiencing that com.android.systemui is taking up a lot of battery. It's always active (Dev-cpu stats) even when I freeze systemui in Titanium Backup. Gsam Battery Monitor Pro says the same thing. On previous builds I didn't have this kind of usage. Any explanations/solutions? Or is systemui part of Rom and not kernel? (could also be due to rom updates ofc)

(Omni Rom, r33, Gnow turned off)
[Nexus 5 Original Android Development] Tzfardaya:
Rom stuff
[Nexus 5 Original Android Development] yorici:
Please tell me if it is persistent in this image.
[Nexus 5 Original Android Development] yorici:
Thx
[Nexus 5 Original Android Development] matesc:
Please read my detailed report about that issue:

http://xdaforums.com/showthread.php?p=50622885

I wrote, that boosting only the volume isn't a solution for me, because the the music sounds weird and crappy then...

It may be a an issue in general on N5, but it doesn't happen elsewhere, so there must be a fix for it. No matter what anandtech wrote..
[Nexus 5 Original Android Development] italia0101:
I actually thought the same thing, it seemed switched the input boost back to 1574000 fixed that for me
[Nexus 5 Original Android Development] pikachukaki:
Right now no....but it will....after a reboot...or if the screen stays in sleep for a long time
[Nexus 5 Original Android Development] PresidentMcCain:
Android OS wakelock on latest test 34

AudioMix according to BBS

1% drain every 20 minutes.

Repro steps:

1. Set an alarm

2. Plug in AC

3. When alarm goes off, unplug AC, dismiss alarm

4. Turn screen off

5. Wait 30 min, observe heavy drain

Only way to get battery back to normal is by turning volume up and down or reboot.
[Nexus 5 Original Android Development] sirovai:
Like [MENTION=1363323]vomer[/MENTION] said to me: give it some time to settle. Now it's working fine for me!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
No, and it likely never will..

Screenshots record the image that was sent to the screen, not what the screen is displaying... So if the screen is incorrectly displaying the image sent, you will need to use a separate camera to take the picture...
[Nexus 5 Original Android Development] big_adventure:
Latest r34-test, using my Shures, and I get your issue, following your steps.

Going down 2 volume clicks corrects the problem. so it's (almost) definitely the amp pushing out more than it can.

It doesn't matter to me, since I can't possibly put those things in my ears at that volume.
[Nexus 5 Original Android Development] churchrickshaw:
Vomer settings

hey guys

I'm trying to follow [MENTION=1363323]vomer[/MENTION] custom settings, not sure who else is testing/running his setup. I'm a bit confused on two settings and I'm not sure what to input

above_hispeed_delay:120000

target_loads:90

He only has one number typed in, whereas the default values look like this:

above_hispeed_dealy:20000 1400000:40000 1700000:20000

target_loads:85 1500000:90 1800000:90

what should be changed?
[Nexus 5 Original Android Development] usaff22:
We're on page 2014! No posts for another year (after the last post on this page)

/offtopic
[Nexus 5 Original Android Development] matesc:
I don't listen to music at such a high volume- I just wanted to reproduce the issue. Anyway the clipping happens also on lower volume at my side. On lower volume the right earphone doesn't stop immediately, just for a millisecond.
[Nexus 5 Original Android Development] Red5:
I'm still getting higher than normal ram consumption on r33.
[Nexus 5 Original Android Development] JassyNL:
No real issue here on r34. Haven't rebooted since a couple of days.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[Nexus 5 Original Android Development] Stanlehh:
same for me on r33, I didn't face this issue on r34 test
[Nexus 5 Original Android Development] willblake13:
Absolutlely Love your work!

Great to see you here Franco! I loved your work on the Nexus 4, and can't wait to try out what you have done with the Nexus 5!
[Nexus 5 Original Android Development] yorici:
From his first description it looked like he just had banding issues from one profile. Showing him a red gradient would test that idea. If banding was present, he would immediately see it. It's basically the same banding image as in the Display Tester App just only red and only from red-black, not white to red.

The images he uploads that have distortions on his screen and will indeed not appear on our screens.

His second description is different. That issue might have to do with a commit franco mentioned that he is going to revert in r34.
[Nexus 5 Original Android Development] Tzfardaya:
Yeah, I read it wrong, I thought he was posting the image asking if we saw the distortion in the pic... Mea culpa. :P
[Nexus 5 Original Android Development] pikachukaki:
[MENTION=4437173]Piereligio[/MENTION] Here it is...sorry about the quality of the pics its my older phone....as you can see the distorsion happents only in the right half of the screen...
[Nexus 5 Original Android Development] yorici:
Are you sure this only happens on this profile. The colour profiles don't have influence on what side of the screen is to be adjusted. This more looks like an error in your display.

Can you take a screenshot of pictures in which this occurs and load it in this app? https://play.google.com/store/apps/details?id=com.andreyaleev.colorpicker

Then tell us what the distorted RGB-values are. I hope for you it's due to the colour profile, but it doesn't sound like it...

Furthermore, have you applied a profile on boot? I would untick the box. Reboot to stock profile and check if the distortion persists.
[Nexus 5 Original Android Development] pikachukaki:
The distorsion happent last night for the 1st time after i apply this profile..never before and even when i load the amoled profile...it didn't show on screenshots thats why i had to take a picture with another phone....
[Nexus 5 Original Android Development] yorici:
I know it doesn't show on screenshots you take and upload to us. But if you take screenshots with the profile (containing distortions for you) and view these screenshots in the Color Picker App, you would still see distortions right? Because the image never changed, just loaded in another app.