yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mpjoe2000:
i think they saw this video yesterday

http://youtu.be/J-e7LnJblm8

xD
[Nexus S Android Development] deani77:
I'm using latest PA 2.21 or Daxx says 2.22 with CM Marmite (5.0.2)
[Nexus S Android Development] :
That's an excellent demo. I watched the whole thing. I think it's quite persuasive, but I have reservations about the transferability of those results to Android running off flash, and also how multitasking works on mobile devices, and usage patterns on mobile devices.

The only way to know for sure is to test, but I'm unwilling to do this personally because previous testing I've done indicates this would be a waste of time!
[Nexus S Android Development] sperelli:
hi there, i would only report back that

with latest SB 2.7.0 and your 5.0.2 (all other roms version)

BLN in-rom settings are available, yet

BLN is not working.

could you please give a look at it?

thx
[Nexus S Android Development] benoit2600:
I actually use the extra ram kernel and I have a lot of reboot. Here is one of all my last_ksmg : http://pastebin.com/XAdnZA4U

The phone freeze and reboot during screen off while music play (with Google music player) and a little time before, et rebooted (without freeze this time) in the same condition, after passing all the night on without reboot.

Edit2 : I was before on an old CyanogenMod, with some nightlies installed over, and it reboot maybe 2 times a day.

As you can see,there is nothing inside that file about the kernel, so it could be the ROM, but I do a full wipe yesterday (including sdcard) and install slim ROM 2.7 with slim apps, and it reboots 2 times since.

So, because it's not the ROM, it may be my kernel setting, so I change smartassV2 by on demand, and have the same problem. It also could be because of low battery, but crash happens at 9% battery, and also 97%, so it's not that. I forgot to precise, but I run all this test over clocked to 1200Mhz Actually, I have two hypothesis about the reboot:

-the extra ram kernel is not stable

- my device can't support over clock

* The first solution is false, because we are a very few number to report reboot, so your kernel is stable, congratulation :)

* The second solution is false too, because my phone can since the beginning support 1200Mhz overclock, and also the 1320Mhz morfic's kernel.

So, the problem could be the voltage you introduce some kernel before (my phone doesn't reboot before that). I actually test your kernel without over clock, but could you create the extra ram kernel with the old voltage? :)

Thank you in advance, and if you want me to do tests or something else, or if you have an other idea, tell me ;)

Edit1 : sometimes the kernel is stable, I ran yesterday during 1 hour with music and GPS activated, and except some glitch in the music, it was stable! (The glitch can be reproduced when we download something and listen to music screen off, with smartassV2 or Ondemand (but it's less frequent with Ondemand))

Edit 3 : here is some other last_ksmg that happens with my old cyanogenrom : http://pastebin.com/01LzsHvC and http://db.tt/e6feRRVv
[Nexus S Android Development] kwibis:
You say that since you installed slim bean you had 2 reboots. Doesn't this indicate that it is rom related?

Sent from my Nexus S
[Nexus S Android Development] anshumandash:
I think today is the actual birthday of Bedalus. So wish Bedalus a very happy birthday !!!
[Nexus S Android Development] benoit2600:
Not really, because I have a lot of reboot before that with a cyanogen ROM. I don't report the reboot here before because my cyanogen installation was old and with plenty of nightlies updates, and I thought the crash came from that.
[Nexus S Android Development] caliban2:
Well, from what I can see it's a new version of bfq. Maybe it still sucks, but why not try it? I'm certain he added it for a reason - Kali isn't just another script-kiddie. He's up pretty high in the dev-foodchain.
[Nexus S Android Development] alen1901:
Bedalus, finally i got a reboot with your name on it!! :p heres the last_kmsg. Marmite v5.0.2 with 413mb of RAM. I dont remember what i was doing, its either xda or browsing. :D

EDIT: no oc. Also i throw an eye on kmsg and i see a lot of suspends and restartings in there. Dunno if thats normal. And in the end, it says, no errors detected. Hmm.

http://db.tt/gmpPvgX8

Sent from SpeedMachine i9023
[Nexus S Android Development] CrackerTeg:
Since it's bedalus's birthday today, an official happy birthday is in order.

Happy birthday you old dog!
[Nexus S Android Development] spider623:
I don't have time to watch it but if the added bfg or bfs patches on a risk processor device they mad like hell, risc technology is fast because it has a standard command and buffer size unlike cisc that has a huge buffer and random command size and it can actually benefit from bfq and bfs since as the name implies it does complex calculation while we with our phones we do simple calculations and that is why we are faster when not multitasking or playing a simple game but don't expect multipoligon games to run on non tegra processors or to see what bfg can do without playing one

---------- Post added at 02:37 PM ---------- Previous post was at 02:35 PM ----------

P.s. happy birthday
[Nexus S Android Development] JokerAce:
Happy Birthday :victory:
[Nexus S Android Development] Accidd:
I got few freezes and reboots when using Tapatalk and oc to 1200. Doesn't matter which marmite version and governor. It's just a report as I normally use 1ghz clock.

But there's something with it. The same was some time ago when using morfic 1.2ghz kernel on ICS.

But 1320 always worked fine.

Maybe voltages?

Sent from my MIUI Nexus S Jelly Bean.
[Nexus S Android Development] mpjoe2000:
KalimochoAz has merged lastest BFQ v5, released on 2012/10/03, the video is from June so, from that time MAYBE it has been fixed enough and gain even better performance to be stable on our phones, but if we/they/you don't test it we will not know then. CM10 is still in testing period.

BTW, the video is about BFQ vs CFQ performance on a hard disk.

http://algo.ing.unimo.it/people/paolo/disk_sched/

https://groups.google.com/forum/?fromgroups#!forum/bfq-iosched
[Nexus S Android Development] :
I think BFQ is dreadful. I think perhaps the new version may have improved things. I would be hard to make it worse. Since they've been implemented in the new Cyanogenmod kernel, anyone who installs their nightly will have this scheduler. So before flashing marmite, boot it, and run some disk benchmarks of both CFQ and BFQ. If it looks like BFQ is standing up to CFQ I will add it, and test it myself.

Doesn't look like a kernel issue. Have you got any settings where you can adjust the amount of free RAM? I keep 75MB free if given the choice. There may be a memory management issue that is causing all the apps to be killed in one go, or it may be a ROM bug. The kernel didn't request a reboot though.

Apart from the last sentence, I think you're saying BFQ and BFS benefit CISC but not RISC, which might be why BFQ measures badly on phones, but good on desktops. I'm not sure exactly what you mean about tegra processors. Do they like BFS? I tested BFS on the two kernels that had BFS versions, and they both showed about a 3% increase in processor efficiency, but caused graphics issues.

I don't want to supply complete voltage control, but I do appreciate that some devices may want higher or even lower voltages to function reliably when OC'd. I will consider if it's possible to add a function to change the voltages at the OC step only.
[Nexus S Android Development] mpjoe2000:
Happy birthday bedalus, you should be reading this messages tomorrow, today you should be partying!!!
[Nexus S Android Development] deani77:
Just installed 16/10 Jellybro... Using Antutu for benchmarking using BFQ and CFQ on Performance 1000-100mhz

CFQ

BFQ
[Nexus S Android Development] :
Can you run just the Database IO, SD card Read, and SD Card Write tests five times on CFQ and five times on BFQ, and post the results as text please? That would be quite useful.
[Nexus S Android Development] capoooro:
We say "auguri" :beer:
[Nexus S Android Development] :
Thanks again to everyone for the birthday wishes! We've just been to the zoo, had a delicious lunch, and my daughter is wiped out! She fell asleep in the car just before we got home, so my wife is sitting in there with the nook color, playing something called Airport Tycoon, and I've escaped to the computer to do some kernel stuff! On my birthday!! As soon as my daughter wakes up I'm gonna be all about the birthday cake though.
[Nexus S Android Development] alen1901:
I can use sysctl command to keep it like that, but that was never problem before, it might be a ROM problem, yes. Will test it more without RAM script.

Sent from SpeedMachine i9023
[Nexus S Android Development] stojshic:
Had a reboot, again. I installed fresh Rasbean and marmite v5. I dunno if it's placebo, or whatever, but I think that my phone reboots few times on first 2-3 after fresh install, but then it looks like it settles, and works better. Anyway, here's kmsg, maybe it helps?

last_kmsg link
[Nexus S Android Development] polobunny:
s3cfb s3cfb: [fb0] video memory released
request_suspend_state: wakeup (0->0) at 5123338340962 (2012-10-15 22:25:23.300977228 UTC)
init: untracked pid 1029 exited
Unable to handle kernel NULL pointer dereference at virtual address 0000012c
pgd = c0004000
[0000012c] *pgd=00000000
Internal error: Oops: 17 [#1] PREEMPT
Modules linked in:
CPU: 0 Tainted: G W (3.0.45-bedalus-03320-gb64f614-dirty #172)
pc : [<c01ee840>] lr : [<c0415eb0>] psr: 60000013
sp : d7507938 ip : d7507960 fp : d750795c
r10: d604e2c0 r9 : 00000000 r8 : d604e2c0
r7 : d15d0500 r6 : d2d01724 r5 : d2d01720 r4 : 00000124
r3 : 00000124 r2 : 00002759 r1 : d604e2c0 r0 : d15d0500
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 56ca8019 DAC: 00000015

Maybe those addtional 4Mb of RAM we should have left alone...
[Nexus S Android Development] benoit2600:
Bedalus, when you have a little time ( so not today :p ) can you update your "build a kernel" guide ? I try to compile my kernel, and there is actually some incoherance with your tuto and my result.

For exemple, the adresse of your kernel is not

https://github.com/bedalus/bedalusKERNEL.git

anymore, but

https://github.com/bedalus/marmite.git

, right ?

and I have a problem with this command :

git remote add upstream https://github.com/bedalus/bedalusKERNEL.git

is "upstream" the good branch to add ? I think it must be change to

git remote add bedalusv5.1 https://github.com/bedalus/marmite.git

but I'm not sure, and I don't really know if it work, because after doing

git fetch bedalusv5.1

the command

git branch

give me :

$ git branch
* (no branch)
bedalusv4.4

:silly:

Edit : And happy birthday :)
[Nexus S Android Development] :
I'll get back to you on this soon!
[Nexus S Android Development] polobunny:
bedalusv5.1 seems like the good branch, it was update a day ago. When bedalus did not come here, if his wife asks. :p
[Nexus S Android Development] caliban2:
Maybe. On the other hand I had these entries in my own last_kmsg's as well, and that was a looong time ago. (Long in marmite-years ^^) So it could be a symptom just as well, not the cause.
[Nexus S Android Development] polobunny:
You and your out of the blue problems. :p

So maybe not last changes then? I wonder if we'll ever get to something stable. :/
[Nexus S Android Development] caliban2:
My system seems to be stable. :p

I'm not going to say it is because I'd jinx myself. Damn, I guess I just did. :banghead:
[Nexus S Android Development] :
I've set up a system in my building now that automatically makes a backup of the System.map file, so I can match up the kernel build time to its individual map, and grep the individual functions, so if the above kmsg is from a recent build then there's a good chance I can work out what function threw a null pointer dereference. Working out why is a different matter!
[Nexus S Android Development] polobunny:
You tell me. That's what happened last time I told everyone post 4.8.3 debug was stable. :p

That's good. No more klutzing around.
[Nexus S Android Development] sidnoit22:
I cant see the links for 5.0.3? Its not released yet?
[Nexus S Android Development] CommanderDuplex:
please set 1,2ghz Vcore @1,3V :crying:
[Nexus S Android Development] alen1901:
Its a test version. Look couple of pages back somewhere. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] beppegg:
Happy birthday beddy! :D

All fine here with 5.0.3-rc!
[Nexus S Android Development] kiden:
happy birthday man! thanks for the great kernel.
[Nexus S Android Development] ebs512:
Yay bedalus you can legally drink now!
[Nexus S Android Development] granets:
Happy BDay bedalus. One request - can you bump up the voltage on 1,2GHz, because I'm having some reboots now and then on the current setup. kernel is 5.0.2 marmite stockOTA, rom is rascarlo's rasbean jelly (no problems on 1GHz, I just like the speed from time to time with 1,2G's)

p.s. just saw some posts couple of pages back, and your response. It would be nice as a compromise for us who need more volts to be able to change it when OCing. so +1 on that feature, if you are considering it.
[Nexus S Android Development] BenHeng:
I had a reboot today at work so couldn't grab a kmsg immediately, hope it's still use full.

I'm using bb5, latest test marmite w OC at 1.2ghz

http://www.mediafire.com/view/?wzx78z1gdp7s3ac

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] caliban2:
Maybe I'm just getting old, but I remember a time when reporting any bug while overclocking was considered an offense, useless and a waste of time - has that really changed?
[Nexus S Android Development] polobunny:
Same for me, but Bedalus went along and touched the voltage and accepts bug reports from people overclocking, so... *shrugs*
[Nexus S Android Development] Ser Gilgoroth:
Thanks for all the work! It's much appreciated!

Congrats on completing another lap of the Sun! It's my father's birthday today as well.
[Nexus S Android Development] benoit2600:
I finally arrived to do something with the source, but I think it can be useful for beginner to have an newer guide :good:

So, I compile my own zimage with this modification :

- Based on the last bedalus commit

- change the 1200Mhz step to 1320Mhz

- overclocked GPU to 240 (need testing by myself)

- based on trinity voltage

- 65pfs refresh rate

the last thing I would add to this list is the extra ram to go up to 413MB with Slim Rom. How can I do that ?

For all other user, I could bring you the zimage to test by yourself, but only if you ask by MP. I don't want to flood bedalus' topic. And I don't give support because I don't even know how to change the name of the kernel, so debugging wiill be difficult :silly:
[Nexus S Android Development] BenHeng:
Sorry, i'm kinda new in the android word and I didn't knew.

I understand that it is awkward but:

-bedalus kernel is hard to crash. I guessed that if the log was useful it might be a good idea. I'm fact, I've read the log myself and couldn't even understand where was the reboot... (I'm no dev).

- I use marmite since some times w/ the same OC (since bedalus changed the voltage, to be able to report in fact) and never had issue so I assume it's not due to OC. (I was quick replying a SMS while on tapatalk if I remember correctly )

Edit: I didn't took offense from Caliban but wanted to point out why I choose to clutter this topic with my maybe-not-so-relevant kmsg.

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] doa4ever:
aokp_crespo_unofficial_Oct-14-12.20121014-1149 with marmite_v5.02 working perfect with the best battery stat I ever had with JB.

Top combo.:good:
[Nexus S Android Development] XxSilent22xX:
What happened: Phone froze upon wakening at lock screen.

description: a blurred double image of lockscreen with artifacts almost like video noise. (tv snow)

Rasbeanjelly 9-26

marmite 5.0.2
[Nexus S Android Development] polobunny:
I don't believe this is against you or your post, but rather caliban wondering if it's really helping bedalus fix the problems the kernel already has if overclocking is mixed in. :)
[Nexus S Android Development] caliban2:
Exactly. :)

If bedalus accepts it - okay, his thread. But you never can be sure what's causing the troubles, because every phone is different. Some can't even run 1100, mine was never really stable at 1200 and then there are those who run it at 1440 and just smile at you. This goes way back to gingerbread times and ICS, long time before that bloke called "bedalus" catched our attention. ^^

Don't forget, our CPU is tested and approved to run at 1000 MHz, 1200 is 20% overclock. That's pretty much in oc-land, be it phone, PC, or any other device. When they make CPUs, with each batch there are good (1000 MHz) and better exemplars (capable of 1000+ MHz). Which you get depends on your luck. :)
[Nexus S Android Development] Epic_VS:
5.1 upped :D thanks bedalus
[Nexus S Android Development] :
v5.1 is here: http://goo.gl/HvUrp

-New stable release

-Various measures taken to help ensure stability

-Improvements in colour for people who don't use voodoo (or init.d to set voodoo)

-Re-enabled Coresight (got disabled for IDLE2, but never turned it back on)

-Bumped the system timer from 200Hz to 256Hz (easier division in several processes, saves a few CPU cycles)

-Changed from slub memory allocator to slab (after reading some worrying stuff about memory pages being numbered wrong)

-Enabled GPU overclock when the top frequency is set to 1.2GHz

-Focussed the default values for smartassV2 to be more appropriate for gaming. Battery life won't be impacted for people who stick to 1GHz and Ondemand.

-Disabled memory CGroups, has unacceptable overheads

For the next release I'm going to consider the voltages for the 1.2GHz step, and see what I can do to add a level of user control at this step.

I have a wedding to attend on Thursday, so I'm still not entirely free. But I will sweep over all the posts here since around Sunday, and pick up any loose threads as soon as I have time. Until then, please keep reporting, upload any last_kmsges if you have reboots, and I'll get around to them asap. :D
[Nexus S Android Development] asphantix:
5.1 could be smoother. For me it's not as snappy as it was before. Maybe it's just a feeling

But again thanks for your effort :)
[Nexus S Android Development] ebs512:
Let it settle in
[Nexus S Android Development] asphantix:
You're right. It got absolutely smooth now. Sorry for judging so early :)
[Nexus S Android Development] CrackerTeg:
I'm getting ready to flash it along with the new version of rasbean. My two favorite components to flash on my NS. I'm itching for all the "new".
[Nexus S Android Development] spider623:
@bedalus yes they benefit desktops better and tegra has bigger memory buffers so it experience some improvements but it loses then since the graphic card is inside the cpu and that is why the quality goes down with the more load on the foreground
[Nexus S Android Development] caliban2:
Aww, 407 mb... :p

But yeah, it feels very very smooth! (coming from 5.0.1)
[Nexus S Android Development] towelboy:
Very eye pleasing, mouth watering colors now (not a voodoo color user) :p
[Nexus S Android Development] wujiyu305:
Governor is not available here on 5.1, How about you guys?
[Nexus S Android Development] CrackerTeg:
Mine is fine. Fix permissions in recovery.
[Nexus S Android Development] wujiyu305:
yeah, it's back!

Thanks!
[Nexus S Android Development] Daniel.Stevens:
Just another update to my "Android OS" Problem. After (clean) flashing everything AGAIN I decided to just let my phone sit there for a day.. That´s what happened (screenshot). I didn´t touch the thing for a whole day and used my backup-phone.

That can´t be right. Nearly 9% battery drain per hour. Android OS on 82%. Slim Bean 2.7.0 with marmite 5.0.1 (ondemand, 1200)

I never had this problem before marmite 4.8.3 regardless of Google Now, Search&Location... The problem first occured with marmite v5 and CNA 3.6.6.

I did battery wipes, permission fixes etc. The whole nine yards

Any ideas anyone ?!? ;0(

SlimBean 2.7.0 marmite 5.0.2

and

CNA 3.6.6 marmite v5 and 5.0.2

Google Now is active (traffic and weather), location and search are on (with gps when needed). ondemand, cfq, 1200.zRam 18%, Kernel samepage merging active. Background process limit max. 4... (Bear in mind these are the same setting I used before with CNA 3.6.6 and marmite 4.8.3 and I had a battery drain of 2-3% per hour)
[Nexus S Android Development] CrackerTeg:
Don't forget that thanks button. It's gold on this forum.
[Nexus S Android Development] sdhanjal15:
http://db.tt/VyeSczdT

Reboot on stable 5.1 :p
[Nexus S Android Development] gregorypeg1000:
On 5.0.2 and 5.1 my phone does something like micro-lag.Dont know how else to explain it.v5 is a lot smoother.

On slimbean 2.7
[Nexus S Android Development] blakmazk:
I am facing exactly same problem, i didnt install gapps and never use location services and other stuff...

Sent from my Nexus S
[Nexus S Android Development] Daniel.Stevens:
Yeah, tried that too. Just flashed the naked rom without google now/Google Apps etc (but with marmite v5), deactivated location&search etc. Nothing helped... What I´m trying now is to take the battery out for 10 min. recharge it to full and reboot.. Maybe that helps...

If nobody has any idea about that I will try to go back to marmite 4.8.3
[Nexus S Android Development] jark99:
+3. Having this android os problem as well. Using aokp build 4 and maramite v5 :/

Sent from my Nexus S
[Nexus S Android Development] kiden:
Yep, I reverted to 4.8 because anything above that gives me high android OS usage. 4.8 though runs fantastic. I too have disabled the location, and Google Now is off completely and I keep having to hunt down high android OS usage.
[Nexus S Android Development] Daniel.Stevens:
I´m using Google Now and Location & search quite frequently. Could you tell me what happens if you activate it (I´m sorry but I didn´t quite understand the "hunting down" part)? Does the Android OS usage get high again? Because if it doesn´t I can forget about all the experiments I´ve been doing and just go back to 4.8.3 ;0)

P.s.: After taking out my battery for about 10 min. and recharging the phone fully while it´s still off and then rebooting it I´m back to 4% "Android OS". Let´s see how long that lasts...
[Nexus S Android Development] deani77:
Link to the test result here...
[Nexus S Android Development] kiden:
I just meant that anything over 4.8 I keep getting high Android OS usage. I usually can get it to go away for a short amount of time by clearing the cache and fixing permissions and rebooting.

I'm going to enable Google Now and Location and see what happens. I'll report back in the morning.
[Nexus S Android Development] Daniel.Stevens:
Thank you but there´s no need for you to test that for me anymore. After my Android OS usage was climbing by the minute (after 15 min. I had over 60%) I now have flashed marmite 4.8.3 again and try it myself. No need for you to mess up your running system for me.. Thx so much though ;0)
[Nexus S Android Development] caliban2:
Maybe betterbatterystats would've told you what's eating your battery...
[Nexus S Android Development] Daniel.Stevens:
After flashing marmite 4.8.3 and resetting the battery my Android-OS usage actually declined from 7% to 4% in the first 5 minutes... (With v5 and above it would have climbed above 20% by now. I tried the same with cna 3.6.6 and slim bean 2.7.0 the only difference is/was the marmite kernel version.)

I´m going to let it sit for a while and report back if there´s any interest ?!?

So I really think that there´s something wrong with marmite above 4.8.3 in my case. Btw my phone´s a i9023 if that helps (Didn´t include that in my previous posts/descriptions)