yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] jordirpz:
Francisco, you ll add ondemamd in n7 II?

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 5 Original Android Development] big_adventure:
A few (more) things on music:

1. There is a huge difference in processing overhead between 128kbps MP3 and 320kbps MP3 (and the versions in between). It is entirely possible that people who have never seen an issue are using (relatively) low bitrate encodes, which are much easier to process. Hence the crazy that TGM sees with 320kbps, but someone who doesn't know what they've got doesn't see anything.

2. I stated before that I had no glitches at all with r43 [MENTION=1785406]300m[/MENTION]hz low freq running 320kbps AAC - well, that turned out to be false. I tested for an hour and had nothing, then tested again, and had some small glitches at screen-off. I bumped the min CPU to 345mhz and don't have any problem there. Reference for convenience: [MENTION=2918197]The Gingerbread Man[/MENTION]

Also, TGM, why are you using 320kbps MP3 instead of AAC? I'm not a fan of clipping highs at 16khz...
[Nexus 5 Original Android Development] RobbieL811:
Bumping up the min frequency while listening to music seems to have fixed it for another user here.

Sent from my Nexus 5
[Nexus 5 Original Android Development] GodSlayer:
From r39 to r43: SOD with each kernel. Less with r43, none with r36. Stock ROM, stock settings, UV -75 from PVS1 clocks (725 for 300mhz).
[Nexus 5 Original Android Development] G-Bus:
Ill try it thanks a ton man!!

Sent from my Nexus 5
[Nexus 5 Original Android Development] guywmustang:
Same for me too. Stock ROM, stock settings, no UV/UC.
[Nexus 5 Original Android Development] chikimonke:
Alright, new and improved version of the bug report form is up, give it a looksee and let me know what you think. Especially [MENTION=4148153]TJKV[/MENTION] [MENTION=4860519]Tzfardaya[/MENTION] [MENTION=2918197]The Gingerbread Man[/MENTION] [MENTION=2434290]big_adventure[/MENTION] and [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 5 Original Android Development] galaxykeks:
I also get SOD since r39.

I had -50mV currently trying only -25mV on the lowerst 3 freq.
[Nexus 5 Original Android Development] big_adventure:
Like it!

Probably ought to add a text field right at the start to identify the problem, or at least to "Audio Problem". "Audio Problem" needs context. SoD and reboot are fine without, clearly. But it gathers the info well, and doesn't yell when you don't have the info it needs.
[Nexus 5 Original Android Development] icethegreat:
When you fill the form out where does it go?

Great job btw
[Nexus 5 Original Android Development] big_adventure:
Just an FYI, I am trying to grab logs of the screen-off audio glitch, and, of course, when I'm trying to recreate it, I cannot.

My initial tests were just going screen off inside of Spotify or from the homescreen with Spotify in the background, and I couldn't cause a glitch.

My second batch of "tests" was walking along with my BT headphones on, using WhatsApp, and going screen-off - I got a brief hesitation each time.

I'm now testing again, ready to cap logs, and am getting nothing. I've tried from inside games, inside the Kindle App (which uses the lowest PAM on my phone), from inside WhatsApp - I get ZERO hesitation at all.

On the bright side, I'm spending a lot of time listening to Nirvana, Jane's Addiction and Black Lips. Without glitches. That makes me happy.
[Nexus 5 Original Android Development] chikimonke:
Right now it just goes to a spreadsheet that I have access too, I'll give access to Franco later once I'm/we are all happy with it.
[Nexus 5 Original Android Development] snorfu:
Is anybody testing ondemand? How are your impressions in terms of performance?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
To /dev/null
[Nexus 5 Original Android Development] chikimonke:
Alright, see if this works the way you were thinking.
[Nexus 5 Original Android Development] Tzfardaya:
Should have a spot to add xda username...

Should generate a ticket number that they can then post here in forum to let Franco and others with access to the Ss know there's a new report...
[Nexus 5 Original Android Development] icethegreat:
I see. Would be cool if we had access (read only) of the spreadsheet to compare and help the dev (or be nosey)... Like when you hit submit, you would be taken straight there or a link appears... ?
[Nexus 5 Original Android Development] big_adventure:
Better still!

Add what [MENTION=4860519]Tzfardaya[/MENTION] suggests and it's gold.

---------- Post added at 11:03 PM ---------- Previous post was at 11:01 PM ----------

The first should be priority.

The second is still incredibly useful, but a bit less necessary. Maybe just a test field to let them indicate that they've created a post on the issue in the thread?
[Nexus 5 Original Android Development] chikimonke:
Added the username option, couldn't find a way to generate the ticket number. But the spreadsheet does show when the response was submitted and couple that with the username and we should be able to figure it out.
[Nexus 5 Original Android Development] ben_pyett:
Also reporting repetitive sod, multiple while on 39/40/41 test/42, all clear so far on 43 this evening, as I read mentioned by another user, I can see my notification leds still running light flow colours, but screen truly knackered...
[Nexus 5 Original Android Development] Tzfardaya:
My only worry is we are making it too complex and users wont want to use it....

Also, each device should get its own spreadsheet, and the spreadsheet should default sort by kernel version number..

---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------

What is your Hotplug load_threshold set to? Try 0.

---------- Post added at 03:10 PM ---------- Previous post was at 03:10 PM ----------

My battery life sucks... 9 hrs on battery, 2hrs 45 minutes screen on time....

9% charge left..
[Nexus 5 Original Android Development] msgfromside3:
I am. It is less snappy/responsive than interactive in some cases as expected. I am more to conserving battery than a few less millisecond response, so it is okay with me.

"Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency."

http://xdaforums.com/showthread.php?t=1736168
[Nexus 5 Original Android Development] chikimonke:
If people got used to filling out a form that walks you through everything, I would like to think that would make MORE people want to do it properly. Now when people give the typical "It's broken, fix please" posts, we can point them to the form link. I've done most of the work in listing only the options available in FKU, and even found links to tutorials of how to do the different things. (which reminds me, if people have better links, please feel free to share)

As for the different devices having their own forms, I'll let [MENTION=3292224]franciscofranco[/MENTION] make that call. Still need his input in general :D
[Nexus 5 Original Android Development] Tzfardaya:
Not separate forms, just separate spread sheets...
[Nexus 5 Original Android Development] KTT16:
To be honest I rarely get SODs, and when I do, I don't care too much because they are so few and far between... Lucky I guess.. Well... If you guys are interested, I've posted the last SOD I got on r43. Thanks so much for being such an awesome community and thanks Franco for kicking ass!

https://www.dropbox.com/s/vdofzj0sn9cxtej/last_kmsg
[Nexus 5 Original Android Development] chikimonke:
Ah, that would be nice, but I'm not seeing an option to link responses from a question (the device one) to a specific spreadsheet. Anyone out there know some Google-Fu that I'm unaware of that can make that happen?
[Nexus 5 Original Android Development] ben_pyett:
I'm running all defaults, so it's set to 60, don't want all cores running on chewing up my battery for no reason
[Nexus 5 Original Android Development] big_adventure:
To second [MENTION=4860519]Tzfardaya[/MENTION], try HPT 0 to see if that changes anything - AFAIK, nobody has yet received an SoD on that setting.
[Nexus 5 Original Android Development] chikimonke:
The jury is still out on whether or not all 4 cores running is actually worse for the battery. The theory being that all 4 cores could get the job done more quickly, so the system is able to return to idle faster.
[Nexus 5 Original Android Development] big_adventure:
What were you doing?

Playing games can kill a phone in less than that, but, outside of bad signal or a runaway app, I don't see how it's dead that quickly.
[Nexus 5 Original Android Development] Tzfardaya:
Try it, Vomer and tgm have both said it's minimal(under 15 minutes sot) cost...

---------- Post added at 03:28 PM ---------- Previous post was at 03:27 PM ----------

Stuck at work as always... Sot is normal for me, but usually at about 30% at this time...

Elevators and office towers just rape my battery....
[Nexus 5 Original Android Development] big_adventure:
That, plus, you can UC with it, never remotely see a lag, and do quite nicely. My load_threshold 0 settings are more aggressive than most, and I usually do just as well on battery (at least) as I ever did with hotplugging at 60. PAMs for games help a lot.
[Nexus 5 Original Android Development] ben_pyett:
After popular demands I'm now trying it, what's gets me is what change caused this to be required?

I've also noticed that my battery consumption appears to have increased of late, no significant amount of evidence to back this up just gut feeling.
[Nexus 5 Original Android Development] big_adventure:
Ah, yes, I know that feeling well.

---------- Post added at 11:36 PM ---------- Previous post was at 11:30 PM ----------

I hear that. I went through the commits, and, though I'm not a kernel genius, I didn't really see anything that would absolutely tie hotplugging to a dead-screen condition - it was just the only thing I noticed consistent between the SoD reporters and those who never saw one. Plus, the kernel log seems to show jack. Unintended consequences can suck.
[Nexus 5 Original Android Development] psp9000333:
is ondemand worth it for this kernel?
[Nexus 5 Original Android Development] neriamarillo:
[MENTION=4860519]Tzfardaya[/MENTION] [MENTION=4809179]yorici[/MENTION] Got a new device and this is one of the new one. It has a stock 2.0-2.1 gamma (Display Tester app) and my old one that's 1.8. Let me know if you need testing or whatever.
[Nexus 5 Original Android Development] msgfromside3:
Depends on what you are looking for and your priority. You should find out if it is worth for "you".
[Nexus 5 Original Android Development] island3r:
http://xdaforums.com/showpost.php?p=51792581&postcount=26028

I know it's not a sod per se, but it could be a clue.
[Nexus 5 Original Android Development] Enddo:
i was unable to get the governor tunables working properly for input boost with ondemand so i am using interactive until it (hopefully) gets fixed
[Nexus 5 Original Android Development] Tzfardaya:
Worst part is Franco nearly doubled my sot....
[Nexus 5 Original Android Development] prstorero:
I was actually talking to my C++ professor about this today. He's worked with C++ and assembly language for years in the industry so he knows a ton. He agrees having all cores running at a slower clock helps with the battery because the tasks get split up between the cores. So the more cores you have running the more the tasks get split up and you don't need the higher frequencies to do the same amount of work; which makes sense to me.

prshosting.org
[Nexus 5 Original Android Development] island3r:
Franco already fixed that on his github.
[Nexus 5 Original Android Development] armymax:
Just had a SoD with r43 (UV: -25; vibration: 90), PA 4.2 beta4. I also noticed that sometimes I need to press two times to wake up display.
[Nexus 5 Original Android Development] Tzfardaya:
Because you're not losing cycles from task switching... 4 cores running one thread each @ x mhz is actually faster than 2 cores running 2 threads each ( both systems running 4 threads) @ 2x mhz.. The dual core system has to waste cpu cycles switching from one thread to the other and back..
[Nexus 5 Original Android Development] exxpired:
Didn't get a log but I got a SoD after hanging up a phone call, got it back on by connecting charger, it woke the screen.
[Nexus 5 Original Android Development] spec0071:
Anyone else having problems with headphones on r43?

Only one side is working, only reboot is fixing it.
[Nexus 5 Original Android Development] Tzfardaya:
Nope.. Better rma your phone..
[Nexus 5 Original Android Development] The Gingerbread Man:
Iv looked through your log and couldn't see anything but the glitches never show up only the long pauses which start with an io error. Sorry

I won't pretend to know much about all the codec types but in future il look out for AAC versions. I always just thought they were the same but not really looked into it.

The glitches don't really show up. I haven't had an issue since bumping my min speed.
[Nexus 5 Original Android Development] yorici:
I appreciate your offer, but I do have come to the conclusion that without a colorimeter it's hard to check anything properly. I have been a bit busy, though I have learned a lot about calibration thanks to [MENTION=2617206]supercurio[/MENTION] . I still need to find a good way to test all 256 values using the colorimeter. Right now it's hard to reproduce the same measurements twice with some accuracy.
[Nexus 5 Original Android Development] The Gingerbread Man:
Looks quite good but a couple of things if I may?

1 Galaxy nexus and nexus 7 (2012) will work with CAF stuff, its only the Qualcomm devices which don't like the CAF display drivers without matching user space stuff.

2 about the under volting, if you were to bullet point each freq then a box to type each value. Example

300mhz - ___

345mhz - ___

422mhz - ___

3 with the logs perhaps make it a required field so people have to submit logs if they want to submit one of these.

Other than that looks pretty good, I like the idea :)
[Nexus 5 Original Android Development] chikimonke:
Hmm, this is pointing more and more to maybe needing a different form for each device. I don't imagine the different frequencies are the same across all devices. I can take out the device selection and then make individual versions for each device. Pretty sure I can copy one form and just update the values for each, but I will need to know what all these different values are for each device.
[Nexus 5 Original Android Development] The Gingerbread Man:
I don't know how to code but isn't this the sort of thing that you would use else/if for. Different answers can change the out come for the next scenario. Also about finding the freq for each device could potentially be done using osm0sis android image kitchen, extacting a boot.img until you find sys/devices/system/CPU/cpu0/scaling available freq
[Nexus 5 Original Android Development] franciscofranco:
Pushed r44:

* Revert a couple patches that could be problematic

* Fix a bug on a piece of code that I introduced on Ondemand where input_boost_freq was not being properly applied

Hopefully SoDs are no more with this one!
[Nexus 5 Original Android Development] chikimonke:
You and me both (on not knowing how to code). While this sounds like a good idea, since I'm trying to use Google Docs, I'm limited to its functionality, and it doesn't get that involved. I could probably fake it, but it will make one hell of a form, and will make the results spreadsheet quite hard and difficult to read.

---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------

Hey Franco, since you're here now, and the thread moved very fast, can you take a look at this bug report form I'm working on for you? Thanks
[Nexus 5 Original Android Development] The Gingerbread Man:
Hmm maybe one per device would be easier then... I can get the CPU freqs available for n5 and n7 2013 if that helps?
[Nexus 5 Original Android Development] Enddo:
thank you for the quick fix :good:
[Nexus 5 Original Android Development] chikimonke:
Realistically I think I need the Frequencies, Governors and Schedulers available for each device. I wonder if there is an easy way for Franco to just pull those and send them to me?

Also, does each device have the PVS Bin # too? And if so, are they all 0-6?
[Nexus 5 Original Android Development] pkelly517:
Totally devil's advocate here...

But how many of the common apps will take advantage of the additional cores? The professor lives in an academic world. We live in the real one. I would bet a bunch that tapatalk doesn't immediately grab those other cores. Games grab them and run them full blast for no reason.

I'm still on the fence. Mostly because I've tried both methods, and really haven't noticed a significant difference between them. Per app modes, when used correctly, are probably the biggest improvement you'll find. But that is the anti flash and forget. That's all user input/work.

Anyhow...
[Nexus 5 Original Android Development] Tzfardaya:
Each app uses at least one thread, system processes are at least one thread each... So there are already multiple threads running concurrently even just sitting at the launcher...

Btw, debate on this is always a good thing, since it forces both sides to look at both sides realistically... :P

On any true multitasking system/os additional cores is usually a good thing... Unless the cost of running those cores out weighs the benefits...

Which is one reason why we still need to test these theories more..
[Nexus 5 Original Android Development] chikimonke:
Actually, [MENTION=2918197]The Gingerbread Man[/MENTION] with Google docs now allowing Pivot Tables in their spreadsheets, I probably could use one form to rule them all, and then set up different pivot tables for each device. This make take a little while longer. Anyone else have any more feedback on my bug report form?
[Nexus 5 Original Android Development] franciscofranco:
That's cool, just made one to test. One question though, if I use that and when a user fills that I'm gonna get an e-mail with the form right? I don't need governors, or frequencies or anything else, as for what it is I think the form is perfect.
[Nexus 5 Original Android Development] chikimonke:
Honestly I'm not sure if there is a way to have it e-mail you after a response, it seems like there should be, but I haven't found said option yet. So since this is for you, tell me which things you actually want in the form. The fewer things there are, the easier it is for me to create :D

Edit: Nevermind, you can get an e-mail when a response is given, you have to set it up in the Spreadsheet, not the form itself.
[Nexus 5 Original Android Development] Tzfardaya:
just the ordering...

should get all the device info... hardware, kernel version, rom type (maybe a field for the rom name as well with custom rom), runtime etc.

before getting into the reported issue...

also, page 3 (audio issues) should only appear if that's what the user selected for the reported problem on page 2...

If the user answers "yes" to "do you undervolt?" the report should end with the prompt for the user to test the issue again WITHOUT any undervolt..

same with overclocking... rather than having a greyed comment on the logs page about testing without UV/OC...

most of the "custom settings" probably aren't needed, since they really shouldn't be causing any issues, (other than possibly lag or stutter)
[Nexus 5 Original Android Development] daniel84cs:
R44 lags compared to the R43. Is it just me?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] chikimonke:
Hmm, that's how the Audio stuff was supposed to work, I must bored something while playing around. I'll look at it later, I'm off to do my fatherly duties.

Edit, there is a custom ROM section too, is it not showing?
[Nexus 5 Original Android Development] omvir:
Just you. Try re-flashing kernel again.
[Nexus 5 Original Android Development] mibtnt:
I was about to come in and b1tch about r42 having a sh1t ton of issues then I realized we're on r44 [emoji33]

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] casonswag:
R44 seems smooth for me on pa rom
[Nexus 5 Original Android Development] armando_rod:
Is saw you reverted some commits about bam_dmux, it has anything to do with the patches you merged from Motorola for modem drain?
[Nexus 5 Original Android Development] P.Mobile:
havent posted in a while.. :) been gettin SOD on last few build just flashed r44 and all is well so far! will post back in a day or so with my findings.. thanks!
[Nexus 5 Original Android Development] mibtnt:
Franco. Is there any reason why when I boot up after an autoflash my Max freq is always never set to 2265 and something way lower? I assume I got thermal throttled. Thing is. My temps dropped back down and it still showed as 1190

BTW. Ellie sounds better on my headphones :3

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] wendiko:
My FKU is not fixing the values every time I reboot the values come back to stock. I ticked the box to set it on boot but it doesn't work.

What do I have to do?
[Nexus 5 Original Android Development] icethegreat:
Is this before or after the 2-3mins it takes FKU to load?
[Nexus 5 Original Android Development] aeroseek:
SOD on r44...got the logcat via adb again while phone comatose. Also last_kmsg after reboot attached.

Stock android. ART. Stock franco with -50mv uv across the board.

Gonna remove the uv.
[Nexus 5 Original Android Development] powerkid39:
so much updates in such a short time! Thanks!

just letting you know my N5 froze some time after flashing r44. I don't know why, normal usage but the notification light is on. Currently reflashing though, hope it'll fix it.
[Nexus 5 Original Android Development] psp9000333:
that's a first, no lag on Tapatalk.
[Nexus 5 Original Android Development] PetritH:
Im not gonna be rude but what's the point reporting sod's while u UV?
[Nexus 5 Original Android Development] franciscofranco:
Bloody paypal :)
[Nexus 5 Original Android Development] zephiK:
Yeah he did.
[Nexus 5 Original Android Development] GoldElocks:
0fb42a48ec5808f1ca3dc77b119467fb
[Nexus 5 Original Android Development] eRadicant:
Cheers man
[Nexus 5 Original Android Development] the1dynasty:
This single URL would be great if it was posted somewhere in the OP... Thanks [MENTION=4916017]cobyman7035[/MENTION] for sharing that...

---------- Post added at 07:11 PM ---------- Previous post was at 07:05 PM ----------

I'm not gonna do this back-n-forth... Sure this kernel is free and I appreciate the work that goes into something like this especially since I develop themes and even have a template that I let others use... I know the kind of work that goes into coding... At the same time, the main app to control this kernel stuff isn't free and its not very encouraging for a brand new person to want to spend $5 on an app that I don't even know if the kernel is one that I want to use or not... So indirectly, posting even the link to the changelog would help out sales... I for sure would buy the app if I knew in detail what this kernel could do for me... As of now, idk what it can do so the $5 app holds no value to me...
[Nexus 5 Original Android Development] franciscofranco:
I just posted that link in the OP. Its XML formatted but yeah its better than nothing.
[Nexus 5 Original Android Development] the1dynasty:
After viewing the changelog, I noticed the vibration was changed from stock 63% to 100%... Is there a way I can change that back? I liked the subtle vibration from before vs this much more aggressive vibration...
[Nexus 5 Original Android Development] Marck527:
Yes. If you got the app FKU, you can edit it, I changed it from 100 to 80.

Sent from my Nexus 5
[Nexus 5 Original Android Development] DesertVelo:
Yes, the vibration intensity can be changed from within the FKU application.

Sent from the singletrack....