yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ej8989:
did a research and managed to fix it.

i went to root explorer data/app then deleted this line: com.maxmpz.audioplayer-1.odex

had to reinstall poweramp though.
[Nexus S Android Development] caliban2:
Isn't this kind of app-problem connected to NOT using the play store...??? :rolleyes:
[Nexus S Android Development] :
No warez thanks
[Nexus S Android Development] :
Right, I managed to get the GPU up to nearly 30FPS which is more like it. So v6.5 is on the way. The version numbering has gone a little haywire, I'm keep telling myself to be careful when I say something is a stable release in the future, but apparently I wasn't listening.
[Nexus S Android Development] caliban2:
Bedalus, old bugger here, but it got lost in the process:

pm_fast isn't working on CM, long time now. (It isn't, that's a fact. I can provide prove with screenshots from speedtest later) I think it stopped working when they introduced WiFi idle setting, but I'm not sure. Question is: Does your ROM have that feature too and it works or would it make sense to test in that direction? I'm currently not near a hotspot, so I can't test for a few hours.
[Nexus S Android Development] :
v6.5 is here: http://goo.gl/HvUrp

-GPU performance improved at 1.1GHz step

If you are on v6.4 and don't use OC, there's no point updating, but anyone making use of 1.1GHz should update.
[Nexus S Android Development] 4tticuz:
Hey bedalus,

Im running SlimBean 2.7 and your kernel (5.2).

The Android OS drain in that version(s) is really high, that is not cool.

Dose this drain is fixed in any newer version of your kernel?

Thanks so far and for your work, which I love in every moment ;)
[Nexus S Android Development] ziociccio:
hi bedalus,thanks a lot for your work.

a question: i flashed v6.4 and i don't use OC (min freq 100mhz,max 1ghz),is this v6.4 a stable version?

before i had v6.2.
[Nexus S Android Development] raducux:
I bad 3 reboots while watching some TV channel in MX player. Largest version 6.4 with bb6.
[Nexus S Android Development] :
https://github.com/bedalus/marmite/commit/e61addb8f0abf98ed0467ff5991a7d15e90f8c68

PM_FAST is forced in my kernel. Are you saying you get slow wifi speeds when the device is suspended?
[Nexus S Android Development] :
If you're interested in helping to debug the kernel, please read the guides in the OP
[Nexus S Android Development] :
Yes, 6.5 = 6.4 + one small fix for 1.1GHz
[Nexus S Android Development] :
There's no bug in any available version of the kernel, apart from one example several pages back that came with a clear warning that it would cause the bug.

There was slightly higher than normal Android OS stats when the high resolution timers were disabled, but this was a bug with the stat, not a battery drain issue.

If you have high Android OS drain, try disabling Google Now and/or Google Location & Search, or try a full wipe and reinstall your ROM and your apps from the market, not titanium backup. You might even want to backup your SDCard contents, and format that too.
[Nexus S Android Development] aladin6:
Found a great combination: AOKP + marmite. Is that a NexusS ?! Awesome performance !
[Nexus S Android Development] caliban2:
Yep.
[Nexus S Android Development] :
Public Notice: I'm a little burned out by trying to work out the problems with the OC code. It's nice to have it fixed and working well, so I'm taking some time off from building.
[Nexus S Android Development] :
Hmm. I don't think that the ROM can over-ride those particular kernel settings. There are ROM settings that can turn the wifi off during sleep, or avoid poor connections, and I suppose if there was a bug here it could affect performance. I really don't know. Maybe other users can confirm?
[Nexus S Android Development] jojoost:
Guess I have to flash your kernel again, as the last version I flashed was something like 4.6..
[Nexus S Android Development] polobunny:
You tell me yeah, hate it when my screen goes off and my download stalls.

I've been using WIFI high performance widget but have not honestly tested whether or not if affects my stuff:

https://play.google.com/store/apps/details?id=com.ratcash.wifiperf

Edit: I have a speed drop too when I turn my screen off, for the record CM10 euroskank kang
[Nexus S Android Development] caliban2:
... which is CM-nightly from 4 days in the future. ^^

let's compare notes: "avoid weak networks" is off here, "keep alive during standby only when charging", idle time is 15 minutes (-> that's the setting that might be causing it, or CM did something to wifi in general.) I'll play with the mentioned settings once I'm in wifi-range again...

what are your settings?

Bedalus: You've got your confirmation from polobunny, now wait if we can connect it to settings or not. Should save you a blind goose chase. :)
[Nexus S Android Development] polobunny:
Avoid weak networks is off too.

Wifi is set to always active while in standby (I manually trigger it when I'm at work and need internet and at home I use my wifi to disable my pattern lock for convenience)

Idle time is also 15 minutes.

The last option shouldn't cause any problem however, that's the time where the wifi will disconnect automatically if the screen is off. This setting is present since Gingerbread but they simply didn't have any GUI to set it, you needed to edit /data/data/com.android.providers.settings/settings.db and change the value of wifi_idle_ms from 15 minutes in milliseconds to whatever your preference. Used to have mine at 15 seconds. :p
[Nexus S Android Development] caliban2:
I see. Okay, nothing to do with that setting then. Great. That leaves "CM-guys doing stuff" - again. :silly:
[Nexus S Android Development] polobunny:
Have you tried with the included CM kernel to see if that happens? Might be worth it to check whenever you or someone else upgrade their ROM. :)
[Nexus S Android Development] aladin6:
euroskank kang is something that I do not understand. Why does he takes the effort to make kangs when there is official nightlies? Im a correct?
[Nexus S Android Development] polobunny:
Because of the cherry picks. Think of kangs as bleeding edge, even more so than nightlies lots of the time. Things that aren't yet brought to CM but are scheduled to be will find their way in the kangs.
[Nexus S Android Development] aladin6:
Aha, that's GREAT :)! I like that idea :good:. So, will I change my AOKP? Okay, i'll try euroskank builds ;). Sorry bedalus for the off-subject :p.
[Nexus S Android Development] caliban2:
Just to make that clear: "bleeding edge" also means "possibly bloody unstable". 99.5% of all time it's fine, but don't complain if it's unstable.
[Nexus S Android Development] pjvaliant:
There is a problem with the download link???

I try all 6.5 and 6.2 link but receive

"nginx error!"

"The page you are looking for is temporarily unavailable. Please try again later."​

Anyone the same problem???:eek::eek:
[Nexus S Android Development] mdean1981:
It appear dev host is down. Give it a bit.
[Nexus S Android Development] Hordon:
Hy, which version fit to SlimBean Rom? ty
[Nexus S Android Development] micha3lvd:
the x.xCM versions (for slimbean 2.8+, lower = other rom version)
[Nexus S Android Development] caliban2:
Just updated to 1031 and it's the same - standby and speed goes down. But is CM even supposed to have pm_fast?
[Nexus S Android Development] Hordon:
Thank you, but i don't understand it, is the 2.8 based on CM, but the older version aren't?
[Nexus S Android Development] aladin6:
SlimBean was always based on CM(no?). But I'm not sure if marmite version support SlimBean(it was not updated for a long time, not after 19th September, no?). You need a confirmation from bedalus ;). Advice: Change your ROM and choose an updated/well supported one ;).
[Nexus S Android Development] AzN MusiQ:
Yes, that's right. Since 2.8 you must use a CM Kernel.

Gesendet von meinem Nexus S mit Tapatalk 2
[Nexus S Android Development] :
Slim Bean is based on AOSP not CM, but has features from CM integrated, and also from AOKP, and some of his own mods.

There is a CM ROM/Kernel tweak that supposedly saves battery by disabling some expensive VSYNC code, which is in Slim Bean (and Stawberry too) but doesn't mean they are based on CM, to be pedantic (which strictly speaking is my preferred method of being).
[Nexus S Android Development] aladin6:
Aha, I was not correct ;). It was a long time since i did not install SlimBean. I really can't find now a ROM that has AOKP and CM features. Every one has some advantages, and can't find a ROM that joins all that features. Returned to euroskank CM10 but I miss in the same time AOKP extra features. :confused:
[Nexus S Android Development] :
You can always try and politely suggest a feature to the ROM developer, but always be prepared to hear a no.
[Nexus S Android Development] aladin6:
"but always be prepared to hear a no." :D:D. The problem is there is no place to post suggestions for CM or AOKP :/. All we have to do is following the changes. BTW bedalus, what ROM are you on?

---------- Post added at 12:49 AM ---------- Previous post was at 12:39 AM ----------

One other question bedalus, what do you think about sysctl.conf tweaks? I used to always edit the values in that file based on that topic:

http://androidforums.com/esteem-all-things-root/532317-tweak-wip-sysctl-conf-tweaking.html

Can that make a big difference ?
[Nexus S Android Development] :
I don't like to advertise what ROM I use. Uh... although, recently I started not deliberately avoiding stating what ROM I use, but I'm still not answering it directly. :p

The thing is, your ROM is a personal choice.

When I first got my phone I liked this ROM: http://xdaforums.com/showthread.php?p=16800849#post16800849

...but if you go to the OP of that thread the dev only had 22 thanks. It wasn't a hugely popular ROM, but I liked it because it had cool blue styling on everything (it was ahead of its time!) The more ROMs you try the better you understand what features you really use, and you get a feel for what you like, and what you don't. I used MIUI for a long time, but I really came to dislike it when ICS arrived.

If you go to my research page (see my signature for the link) you can see where I've analysed the performance of some ICS ROMs, and also I had another short lived project where I used sentiment analysis to try to track the 'positivity' of the feedback for every ROM and kernel thread. CyberGR's thread was very high up, as was WildestPixel's. CyberGR's had so many features crammed in, while WP's was quite minimal.

EDIT: stempox thanked me! That reminds me: http://xdaforums.com/showthread.php?t=1721856 is a very useful list
[Nexus S Android Development] Ser Gilgoroth:
I absolutely agree with the above. I've used more ROMs than I can easily count. Kernels are quite as extreme, however I now have a better understanding of what I look for/need in both. I also find that phone can differ, what works well for some, has never been successful for myself. Ultimately it's personal choice and we're lucky to have many options!
[Nexus S Android Development] FirePoncho86:
I completely agree. I know personally I like minimal-moderate amount of features, something that looks stock,but has a few mods under the hood. And kernel? Something with voodoo. Or anything Marmite ;)
[Nexus S Android Development] towelboy:
After looking at stempox's list I realised how many roms that our nexus got to taste.. especially compared to my mom's on her g2x! (Their ics source code just got released!). Since there's so much out there there's a fav for everyone so good luck and have fun! :thumbup:
[Nexus S Android Development] hiphopboy:
At 1.2 Ghz and smartass2/cfq i have reboot when i open my phone and using on time preparing sd card ... on marmite v6.2
[Nexus S Android Development] :
At the top of the download page it says "No bug reports if you are overclocking"
[Nexus S Android Development] AzN MusiQ:
Bedalus, which Rom do you use with your Kernel now?

Gesendet von meinem Nexus S mit Tapatalk 2
[Nexus S Android Development] :
I know some people only read the last page of a thread, but since I answered this on the same page, you don't really have an excuse: http://xdaforums.com/showpost.php?p=33532697&postcount=4653

One of the rules at XDA is read before you post.
[Nexus S Android Development] :
I know I said I was taking a break from building, but...

v6.6 is here: http://goo.gl/HvUrp

-Merged to Linux mainline v3.0.50

-Fixed the GPU code.

In the PLL check that I created for v6.5 I somehow accidentally changed a different check. Sorting out this GPU OC at 1.1GHz has been a real chore, so again, I'm taking some time off building, but I couldn't leave the version matrix with an error dangling at the top. Enjoy! :D
[Nexus S Android Development] caliban2:
Haha, wonder if you'll ever manage to really take a break. ^^ (this must be the 5th time I see you announcing one)

Enjoy, but please take a note for the future regarding pm_fast & CM: It isn't working, nevermind which settings we use. Also, it isn't working with CM stock-kernel, but I don't know (yet) if it's even included. Rom-details don't matter in this case, it's broken for weeks, if not months. (Worked once though)
[Nexus S Android Development] alen1901:
Im with 72hours of uptime with 6.2(i want to go for 400hours) and im fighting with myself, i really want to flash but i really dont want to haha. Nice developing here, bedalus for real, take a real brake for at least 3,4 days. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] :
Yes, I'll figure out if it's a kernel issue for the next version. I noticed in the kmsg log there's a message from dhd (wifi code) saying 'force extra suspend setting', so I have a start point for investigating.
[Nexus S Android Development] caliban2:
Thanks. One more: Lots of kernel-stuff coming up with next nightly. So just FYI: http://changelog.bbqdroid.org/#crespo/cm10/next
[Nexus S Android Development] :
All those changes appear to be from Android common and the mainline, so I'm already up to date.
[Nexus S Android Development] caliban2:
Never doubted you being up-to-date, I don't trust CM when it comes to compatibility. ^^ (still adore the ROM)

I replaced cam&gallery with the new 4.2-app and after a few test-shots I can say it's working great, so probably (!) no mem-issues to be expected in the future. :)
[Nexus S Android Development] alen1901:
So i couldnt resist anymore and i flashed 6.6. Nice. I will test battery and OS bug.

EDIT: oops i was too quick. My screen went black and i could only pull out battery. I wiped cache and fixed perm. We will se now

Sent from SpeedMachine i9023
[Nexus S Android Development] gummie:
I knew there would be a sudden update due to the fact that I saw a new Linux Mainline (also at the next CM nightly). Anyway just thinking are any of the commits at CM10 nightly (all crespo-kernel related to be specific) also updated on your CM version? Cause I saw mostly were for memory leakage and USB related.

Huh, I guess my browser haven't refreshed yet when you posted that. Disregard if commits are already updated, hope nothing breaks for I will be busy starting right now and dont want my phone to go haywire on my daughters birthday tomorrow. Thanks!
[Nexus S Android Development] :
Well, nothing is supposed to break with mainline updates. This is the stable branch we're on, so all the commits are supposed to be safe, mainly bug fixes. However, I'm reasonably sure that I managed to weed out one commit that wasn't happy in android.

Anyway, perhaps we'll get a whole new kernel with Android 4.2 soon.
[Nexus S Android Development] alen1901:
Ofcourse we will. I dont have doubt in you. ;) I love nexus s, but i hope i find some money for nexus4. :o

Sent from SpeedMachine i9023
[Nexus S Android Development] polobunny:
I don't think he was talking about his capacity to build one, rather the possiblity of the NS not getting any support from Google anymore. ;)

I did 100 hours on v6.2 before needing to reboot for a BLN bug. Still on it as we speak, bedalus updates kernel too often for me to follow. Can't be arsed flashing multiple times a week. :p
[Nexus S Android Development] destroyer12:
k

can I install this kernel on rasbean jelly? on cm10?
[Nexus S Android Development] polobunny:
Yes, take the other rom version, not the CM10 one. Rasbean is built from AOSP, not CM10.
[Nexus S Android Development] alen1901:
had soft reboot with marmite 6.6 while transfering file with usb. thats second freeze/reboot with that kernel today. going back to 6.2 to beat my uptime record. :P
[Nexus S Android Development] polobunny:
Did you fix perm?

Edit: Nvm, just saw you did. Tough luck!
[Nexus S Android Development] CrackerTeg:
Had a freeze followed by a reboot while browsing tapatalk. Rasbeanjelly 10/28 version, marmite 6.6, smartassv2 200-1200 stock voltage settings. I was actually able to pull a last_kmsg this time.

https://www.box.com/shared/m87xvbaajdnc1z1hi6ln
[Nexus S Android Development] polobunny:
First post says no bug report when overclocking. :p
[Nexus S Android Development] CrackerTeg:
I'm aware of that but if he spent as much time as he did to get the voltages right, why not share? Besides, when have you ever seen tapatalk use that much of the processor? The frequency stays low for something that light.
[Nexus S Android Development] agnostic900rr:
when I try to set 100MHz as min NS-Tools is FCing. Never had that before, only with 6.6CM. Any reason why?
[Nexus S Android Development] shivasrage:
So now I think the time has come to thank you bedalus:

For your energy you always take in this development.

For your unbelievable patience.

For your sleepless nights that you spend with and for us.

For your will to give your best... and correct any little mistake soon as possible.

For your friendly answering of stupid questions.

This is what make our community make what it is.

Maybe it sounds gay but its the truth.

And I hope the most agree with me...

Thanks a lot man.

S.R.
[Nexus S Android Development] unlinker:
Had a reboot 1 hour ago while the phone was completely idle, on 6.5CM.

No OC.

Here is the last_kmsg.
[Nexus S Android Development] kwibis:
HAA... GAAAAYY. Nah jk. You say what I guess everyone thinks ;) thanks bedalus!

Sent from my Nexus S
[Nexus S Android Development] :
What model please?
[Nexus S Android Development] :
Actually, i think you're the first victim of the fsb error in v6.5. Update to 6.6
[Nexus S Android Development] alen1901:
Bedalus im back on 6.2 with latest rasbeanjelly. 6.6 seems slower in xda app scrolling. Like little stutters. 6.2 is sooo smoooth. Little to non stutters. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] polobunny:
Am I the only person that has BLN stop working after some apparently random time? All was fine, BLN worked fine and all but sometimes will stop working until I rerun my script. :/
[Nexus S Android Development] deani77:
Reboot on latest CM6.6 and 31/10 nightlies

http://db.tt/pOeXOUmn
[Nexus S Android Development] alen1901:
You use script (with script manager) instead of init.d? Or?

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
Anyone having problems with BLX=100? Stops charging at 96, 97 and then trickles up to 100 over time. (Yes, I know it's cosmetic. No, it's not really a bug. Please spare me the lectures. :p )
[Nexus S Android Development] kwibis:
Nope no problem here. Just charged to 100 with 6.6

Sent from my Nexus S
[Nexus S Android Development] caliban2:
What ROM? CM here. (Your sig is empty)

I'm asking because it gives me standard-behaviour, says"charged" at 96%. Now question is if it's another CM-special or if it depends on how much mV the battery is capable to hold (mine is in use for 13 months, should be degrading by now).
[Nexus S Android Development] anshumandash:
I am on BB6 and it charges properly till 100% when it says charged. I have battery monitor widget installed and it actually shows % charge when it is charging. The % reduces to 8-9% after 97%. But it charges up to 100%.
[Nexus S Android Development] caliban2:
I'm logging my batt-stats now, that way it will be easier for me to see when it does what (%, mV etc). :)

PS:

As I can see, nothing has changed since the days I was testing android on my old X1. Percentage goes down, but voltage goes up... :rolleyes:
[Nexus S Android Development] unlinker:
Nexus S I9020 (non 4G).

Updated to 6.6CM right now! (I'm on Slim Bean 2.8)
[Nexus S Android Development] :
I think you might be on to something there.

Originally, the GPU power management [GPUPM] reset the minimum frequency to 200 MHz, but any attempt to change the policy caused it to get stuck there.

I then put new code into the GPUPM to check if the GPU was powered down, and reset the minimum to the user's policy, but it didn't work. It was like my code was not executing.

I saw a check that only activated the GPUPM if there was a CPU frequency transition. I removed this check, and it worked fine.

However, I realised I could put a modified version of the check back to make it more efficient. It would activate the GPUPM if the CPU frequency changed and if GPU is already known be activate.

So.... If the GPU is known not to be active, it would not do a check unless the frequency is changing.

I hope you're following the logic of this so far because, here's what I think... The check is faulty. By the time the check code is reached, the CPU frequency transition notifier has already updated to say that there has not been a change. This would explain why I needed to remove the check originally, and would also explain why putting a modified version of the check back in would cause graphical lags: the GPU/FSB does not get the opportunity to raise the minimum frequency when the CPU drops to 100MHz because by the time the check is reached the notifier has already reset.

There may be another check that I can do instead of relying on the notifier. If I just check that the current CPU frequency is above 100MHz, I don't need to run the GPUPM code. This should allow better efficiency, and prevent any lags from the FSB/GPU speed dropping.
[Nexus S Android Development] :
Don't worry about it. I think the algorithm for calculating the battery percentage is smart enough not to rely solely on the mV reading, the accuracy of which might be affected by the temperature of the device.
[Nexus S Android Development] :
There's a lot of corruption in that log, and the log also says there's bad blocks. I think you need to consider doing a full wipe, including your SDCard partition (backup the contents first) and then start again fresh.
[Nexus S Android Development] caliban2:
I know. It's just funny to see. :)

I'm running it to see what happens, especially when charging and reaching 96%.
[Nexus S Android Development] polobunny:
I use an init.d but I can also start the script manually. Bln will work fine for a good while and suddenly I'll take my phone out of my pocket only to see bln to be off but a msg has been received. Then there's pretty much nothing I can do other than running the script again to make bln work. Probably related to the other bln bug I got where bln would stay on.
[Nexus S Android Development] :
I think you are right. There must be some point in the code where something is not being reset correctly under some condition.
[Nexus S Android Development] noobiekins:
reboot on 6.6, using rasbeanjelly, graphical artifacts while being able to see image, never happened with trinity 220/240gpu kernels
[Nexus S Android Development] :
What device? Are you able to grab the last_kmsg?

Edit: are you oc'ing?
[Nexus S Android Development] alen1901:
Funny thing. For me bln works great all the time. No problems at all from the beginning where i firstly used bln until now. Maybe some codes are messing bln up. Im on 6.2 but on 6.6 no probs too

Sent from SpeedMachine i9023

---------- Post added at 01:44 PM ---------- Previous post was at 01:41 PM ----------

Bedalus i also noticed that on 6.6 transitions when switching apps, going into apps etc are smoother in overall time more than on 6.2. It might be placebo though.

Sent from SpeedMachine i9023