yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] sperelli:
I keep on being stuck...

Miui has no /etc/init.d/ ... should I had support?

Tbh, BLN works but just for a while.

Then lights turns off..

:confused:
[Nexus S Android Development] Daniel.Stevens:
Just flashed SlimBean 2.8.0 but everytime I try to flash marmite 6.2 my phone goes belly up...

Tried everything. The Rom´s working fine but after flashing 6.2 it just won´t start anymore...

I thought SLimBean for the Nexus S came with marmite (granted an older version but still marmite)

What´s up with that ?

P.s.: Could somebody please let me know what Version of marmite this is (stock Slim 2.8.0) as long as it´s not some 5.x Version I´m happy ;0)

(Sorry I´m a real n00b when it comes to figuring out what all the "gb179fd6-tarak"-stuff means *lol*)
[Nexus S Android Development] gregorypeg1000:
Install the cm version
[Nexus S Android Development] Daniel.Stevens:
Just to clarify (Sorry) : The version for the CM Nightlies ?!? I always flashed the "all other roms"-Version. They must have changed the rom.
[Nexus S Android Development] leap_ahead:
Yes the cm version
[Nexus S Android Development] stojshic:
Media scanner indicates, probably, a problem with some file on your SD. Try mounting it to PC and backing up everything needed, and after that format SD card
[Nexus S Android Development] alen1901:
Thats the latest bedalus kernel you got there.

Sent from SpeedMachine i9023
[Nexus S Android Development] polobunny:
In 11 minutes he has 1 minute 7 seconds of media scanner. Nothing indicates it's abnormal. We need a bigger sample than 11 minutes of being booted to judge what could be the problem.
[Nexus S Android Development] BenHeng:
I've also noticed that at boot I always have a "big drain" from media scanner (every single reboot) but that it settle down to normal after a few minutes

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] polobunny:
Yep that's normal, there's a media scan scheduled at boot completed. :)
[Nexus S Android Development] metalgear873:
Why would you want to overclock, it's already buttery smooth. Keep the cpu @ stock and enjoy a stable and smooth experience.
[Nexus S Android Development] caliban2:
Quiet as it is in here, v6.2 must be bloody perfect. :)
[Nexus S Android Development] polobunny:
It's pretty boring yeah. No other crashes so far so maybe just a fluke. :/
[Nexus S Android Development] benoit2600:
How can I compile a CM version of this kernel ? ( I already know how compile a "normal" version of it)
[Nexus S Android Development] CrackerTeg:
Been doing good for me at 1200. I honestly think the fsb OC for 1096 is what didn't work for me. 6.2 just works and it had both flavors for everyone. Kudos to bed.
[Nexus S Android Development] qu3becker:
Well, for the first time in a while, I got terrible Android OS drain on Marmite 6.2. I just flashed it yesterday night before charging it. I just installed BetterBatteryStats so there is no data yet. I'm currently charging my phone. I am running Rascarlo's Rasjelly bean latest version with Brainmaster tweak (no mem tweak). I'll gather more information tomorrow.

http://img.tapatalk.com/d/12/10/25/utanaqu2.jpg http://img.tapatalk.com/d/12/10/25/yjuqaze4.jpg http://img.tapatalk.com/d/12/10/25/yvu8a6y4.jpg http://img.tapatalk.com/d/12/10/25/uguhadan.jpg

Hmm seems like there's a toast blocking the last screenshot.

http://img.tapatalk.com/d/12/10/25/a7etudyn.jpg

Sent using Kirby's Warp Star.
[Nexus S Android Development] :
Create a CM branch then

cp /home/dave/android/androidkernel/drivers/video/samsung/s3cfb.c.cm /home/dave/android/androidkernel/drivers/video/samsung/s3cfb.c
cp /home/dave/android/androidkernel/drivers/video/samsung/s3cfb.h.cm /home/dave/android/androidkernel/drivers/video/samsung/s3cfb.h
cp /home/dave/android/androidkernel/drivers/video/fbmem.c.cm /home/dave/android/androidkernel/drivers/video/fbmem.c

let me know if that solves it.

Just a note for Slim Bean users, tchaari is building my kernel into the ROM itself, so you don't need to flash marmite.
[Nexus S Android Development] :
Well, you gave me some inspiration to investigate whether this was possible, so thanks!
[Nexus S Android Development] kwibis:
This morning had 2 reboots while listening to music on 6.2 but was oc to 1200. At 1000 it seems solid. Now running at 1200 again and so far no reboots!

Sent from my Nexus S
[Nexus S Android Development] :
Brainmaster's thread may give you some clues on how to add init.d support: http://xdaforums.com/showthread.php?t=1454289
[Nexus S Android Development] CrackerTeg:
I do what I can.
[Nexus S Android Development] Hawkw1nd:
Try this - http://xdaforums.com/showthread.php?t=1680052 . It should be device independent, so don't worry about it being in the HTC One X/XL forum ...
[Nexus S Android Development] jayjay3333:
http://xdaforums.com/show...&postcount=786

"You need to flash the CM edition mate. It is beacause of enabling vsync in the kernel" http://review.cyanogenmod.com/#/c/23406/
[Nexus S Android Development] grotesque02:
For paranoid android I have to install version for CM or all other roms?
[Nexus S Android Development] qu3becker:
Paranoid Android is based on CM. So use the CM version.

Sent using Kirby's Warp Star.
[Nexus S Android Development] Erythnul:
MediaScanner isn't wakelocking badly, it's probably just the initial scan, as polobunny mentioned. So you've either got a kernel wakelock problem, or your problem stems from something else. If necessary, grab some screenshots from the other screens of BBS.

First thing that occurred to me, as soon as you mentioned SystemUI: Do you have widgets in the navbar? (I think that's a possibility with AOKP, right?) If so, maybe one of them isn't playing nice with SystemUI. Try removing them and see if that fixes it.

If that doesn't help, try fixing permissions or ultimately, if nothing helps, reflash the ROM and kernel from a clean wipe, then fix permissions. If that doesn't help either, it'll be a tough one to crack, so let's try all this first :P

You've got a real problem there, but unfortunately, I can't help you without some more info from BetterBatteryStats ;) As soon as you put up more info, I'll be sure to have a look at it!
[Nexus S Android Development] Jamalsid:
May be worth linking this post in the OP Bedalus as it is a way to add init.d support to any rom without the need for a custom kernel.
[Nexus S Android Development] :
Thanks, but my kernel already supports init.d

The problem with MIUI is with the ROM itself. Perhaps all it needs is busybox installing.

Edit: here we are...

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

Looks like the solution was right under our noses!
[Nexus S Android Development] spider623:
Bedalus about miui your kernel doesn't work with the stock Chinese version but works with the British translation port of mini android any ideas why?
[Nexus S Android Development] :
I believe there are some incompatibilities between their version and aosp. I'm not going to be pursuing support of miui since there are working versions
[Nexus S Android Development] dadaz007:
v6.2 works really great on my French MIUI, even init.d I think.
[Nexus S Android Development] grotesque02:
I flash the 4.7 CM version (I think is the most stable for now) but rom and nstools don't want remember deadline, only cfq, why?
[Nexus S Android Development] :
Deadline has been removed from my kernel over concerns of it hanging. In my tests I showed that CFQ performs consistently better than deadline despite deadline being able to achieve peaks of higher throughput.
[Nexus S Android Development] grotesque02:
But I flash old 4.7 version, and that version have deadline.
[Nexus S Android Development] :
Yes, my approach to kernel development is to release the finished article, then work backwards through time, slowly destroying it.

Other developers may frown on this, but it works for me.
[Nexus S Android Development] Articudos:
Imho, Secured boot.img can cause that issue:/
[Nexus S Android Development] qu3becker:
Ok, today's Android OS drain is back to normal. Thanks anyway :) .

I unplugged my phone at midway charging yesterday and bbs seemed to report various Maps related wake lock in the "other" tab if I remember correctly. So I unstalled Maps with Titanium Backup and downloaded it on the play store. It was just a coincidence that it occured at the same time as flashing the new Marmite version.

Thumbs up to Bedalus. He may be not a real developer but he sure make a fabulous Kernel. I won't switch soon for sure. Thank you.

Sent using Kirby's Warp Star.
[Nexus S Android Development] :
There are a few original things in this kernel ;)
[Nexus S Android Development] KrisMurdrum:
I9020t

Flo's 100.1% Stock Google

Marmite v6.2

Default kernel settings

Had had my phone sitting while giving my daughters a bath and into bed. After unlock I fired up Bad Piggies. Had some lag at app startup, nothing unusual. After about two minutes of playing, the game bogged down, screen went off and a minute or two later I had a reboot.

Last_kmsg_2

Aaaaand I posted this turned my screen off. Few seconds later I heard the screen-off sound and when I looked my phone was in mid hard reboot...

Last_kmsg_3

Carved into the void with my Magic Rune Stone
[Nexus S Android Development] Basche:
Well I say he's a great developer, from what he started with this kernel, to how it is now, a great developer indeed :)
[Nexus S Android Development] alen1901:
He got from rookie dev to hardcore dev. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] qu3becker:
Sure, I was wrong. You are right. :)

Meant no disrespect. So far, no issue related to the kernel on 6.2. I'm very happy with my 2 year old phone.

Sent using Kirby's Warp Star.
[Nexus S Android Development] polobunny:
I don't know if it's placebo, but v6.0.3 felt faster than v6.2 does with identical settings. Anyone else?
[Nexus S Android Development] dvdy:
Just got a reboot running 6.2 on Slim. Not sure what the cause was but I'd gotten a text recently and was turning the screen on, but it stayed black and rebooted. The only setting I change in the kernel is enable BLN

last_kmsg attached
[Nexus S Android Development] granets:
I feel the same. 6.0.3 (a.k.a. 6.1) felt somewhat smoother
[Nexus S Android Development] :
Thanks. This looks like it might have been caused by

my wifi deadlock fix. I definitely fixed an issue, but also I think I fixed a different issue at the same time that wasn't an issue. I don't think this is serious enough to release a new version just yet.

My GPU fix means some extra code is running, because I had to remove a check that allowed a function to abort early. Perhaps I can find a more elegant solution.
[Nexus S Android Development] :
You need to tell me what device you own too thanks
[Nexus S Android Development] leap_ahead:
bedalus what is the default voltage for 1.1Ghz with 220Bus on trinity kernel if you know ?
[Nexus S Android Development] caliban2:
A "default"-voltage for a step that's out of spec. Find the logical error in that sentence.
[Nexus S Android Development] leap_ahead:
sorry i dont know ..
[Nexus S Android Development] _yaz_:
confirmed. i had regular reboots (mainly soft but sometimes hard either) when i woke up the phone and it tried to to reconnect wifi at the same time. in any other situation it's stable as hell. i switched 'keep wifi on during sleep' and kept checking. now rb is much rare but stricktly correlates with wake up and wifi reconnection at the same time. (i guess, my rooter started dying, so reconnection occurs frequently) so, for me, it's "serious enough" :p
[Nexus S Android Development] ahmmyreal:
which one should i download for miui jb?
[Nexus S Android Development] :
It's the same as what I've included. Looks like me and morfic feel the same way about voltage at that step.
[Nexus S Android Development] :
Ah, I take your point. I always had my wifi advanced settings 'Always On'

Anyway, I've fixed my fix for my wifi deadlock fix fix (yes, you read that right). Nth time's the charm. Also there were a couple of new wifi commits in android-3.0/common which I've merged in.

I'm just looking if there's anything else I can do with this GPU code. I feel like scrolling is noticeably better, so I want to keep my implementation, but I think there must be a way to make it more efficient. If I come up with something I'll release a new incremental version.
[Nexus S Android Development] beppegg:
After loooooong time, it's bug report time again! :DDDD

Just using my phone for wifi tethering, I've noticed it rebooted (I don't know if google logo showed).

My data: Marmite 6.2 on RasBeanJelly 26Sept, i9023 no overclock (default kernel settings)

I always wipe cache, dalvik and fix permissions on each kernel flash.

Last_KMsg here: https://www.dropbox.com/s/dm32teqe00aoyah/last_kmsg_20121026_rascarlo26Sept_marmite620.txt

I think it could be linked to the above posts...
[Nexus S Android Development] alen1901:
You really dont have to wipe anything while flashing kernel, only Fix permission if you notice something strange. I flash all the time like that and no probs. :)

Sent from SpeedMachine i9023
[Nexus S Android Development] Hawkw1nd:
I've had this happen not only with Bedalus' kernel, but with my Gnex. I come out of sleep, turn on Wi-Fi, and it instantly reboots. If I don't turn off the Wi-Fi as soon as the boot cycle ends, it will reboot within 15 seconds and the cycle will repeat again and again.

I turn off the phone's Wi-Fi as soon as it has rebooted and then reset my router. Problem fixed - at least for a few weeks anyway :P
[Nexus S Android Development] :
Thanks for reporting thoroughly. Yes, it looks like the same thing. Just change your advanced wifi settings to 'Always On' or wait for the patched version. I'm busy working on something else at the moment.

EDIT: I'm just done some more work on the GPU code. I think I've optimised it a bit. It's working as intended anyway.

Originally the code checked to see if there was GPU activity, and raise the minimum frequency to 200MHz to achieve full speed FSB. However, it only did this check if the cpu frequency policy had changed. It also never reset the minimum frequency after the GPU finished its work.

I inserted some code to reset the minimum frequency back to whatever the user had set. But in order for this code to work I had to remove the check to see if the policy had changed. I didn't profile the function to see how often it was running, but without this check, every time it ran, it would run fully, which is not efficient.

I've now put the check back in, but I've modified it so that instead of checking if the policy has changed, it now checks if there have been any CPU frequency transitions. I think this is how it should have been written originally, because what they gave us doesn't really make sense. Commit here: https://github.com/bedalus/marmite/commit/1e49ff0ca39f5351c27f01d11eba688215c24ac1

I'll upload v6.2.1 now!

EDIT: Oops, I've created a rebooting monster. I think it's my new GPU code.

Confirmed. So i can't do it that way... Doesn't mean there isn't another way of doing it. I'm off to work now though. No updates til this evening!
[Nexus S Android Development] dvdy:
Oh, i9023
[Nexus S Android Development] :
There's nothing in the last_kmsg that indicates a kernel problem. If your device randomly rebooted, unfortunately on this occasion, there was no time for the kernel to backup the active log.
[Nexus S Android Development] beppegg:
Thank you for your advice, I know I don't have to do all those wipes, but I had some tricky experience in the past so I do that anyway, just to be sure, since they don't really harm anything. Am I missing something, so that it's adviceble to keep cache/dalvik/perms unless something strange happens?
[Nexus S Android Development] polobunny:
On kernel flash you don't need to do anything most of the time. If you touch your ROM though the whole cleanup is advised, including fix perms.
[Nexus S Android Development] JokerAce:
Hi I am back for the week.

Thought I might suggest that you add those in orange to the excel sheet so people are more aware of that, they are not suppose to report crashes when they OC. People like me, I just keep following the latest page of this thread, and rarely get back at the OP to see if there are any changes. #justmythought

Talking about new phone, do you have any intent on the Nexus 4? :D
[Nexus S Android Development] capoooro:
9023

Strawberry

6.2

I had 3 reboot random:

After a call

Listening music

With chrome

Going back 6.1

All OK at the moment
[Nexus S Android Development] stojshic:
3 reboots and yet not a single log... That surely gone greatly help bedalus.
[Nexus S Android Development] :
Thanks, I'll think about it.

I'm too poor for a new phone! I like the look of the lg device (if that's actually what it will look like) and the specs look good, but honestly, I can't justify the cost. I'll buy a new one when this one dies I guess!
[Nexus S Android Development] leap_ahead:
You overclock or stock ?
[Nexus S Android Development] :
Right, I've checked my wifi deadlock code for something like the tenth time, and I'm happy it's correct. I've tested it, and there doesn't seem to be any problem with advanced wifi settings (always on/always off/etc.)

The code which I thought had cleverly made the GPU check more efficient in fact caused the phone to reboot. I think this was because my code was trying to check for activity even when the device was asleep.

I went back to the drawing board, and came up with some more conservative code tweaks that improve the efficiency by allowing the GPU activity checking function to abort early.

The best way to describe it is pseudo-code:

Was the GPU already deactivated?
YES
Has the CPU frequency changed?
NO

This aborts, so it's efficient.

Was the GPU already deactivated?
YES
Has the CPU frequency changed?
YES

This has to then check if the GPU is active, then if so make sure the minimum frequency is raised to at least 200MHz. This is the least efficient.

Was the GPU already deactivated?
No

Regardless of whether the CPU frequency has changed, if we know that the GPU has not yet been deactivated, then we need to check if it is still active, and if it isn't, restore the user's minimum frequency preference.

Before I touched this function, there were two thirds as many power-state checks, so I've increased this particular function's costliness, but it's worth it for the convenience of allowing the GPU power management to work at the same time as the user-land CPU policy controls.

I'm hypothetically interested in exactly how often this function is called, and how many CPU cycles it uses, but pragmatically, I know it's a negligible fraction of something as complex as scrolling through your apps list, so I'm not particularly bothered!

Anyway, I'll build and upload now.
[Nexus S Android Development] :
v6.2.1: http://goo.gl/HvUrp

-A bit of new wifi stuff from android-3.0/common

-Definitely maybe fix the potential wifi deadlock fix fix

-Make the GPU min freq reset bug fix more efficient

It's all fairly minor stuff really, so feel free to skip this version if you are happy on v6.2. It'd be nice to see some people trying to pull a few hundred hours of uptime on v6.2 because I'm really happy with it. Unfortunately I can't personally stick to one version for long because that would stop me from testing new ideas! Anyway, enjoy!
[Nexus S Android Development] tchaari:
Nice and interesting geeky ideas :D
[Nexus S Android Development] CrackerTeg:
Woohoo! First to download!
[Nexus S Android Development] :
I stayed up until 3am messing around with a bunch of experimental tweaks. I'm too tired to explain or upload now, but the result is working fine. I'll let it sleep over night and upload in the morning, just in case any testers want to hold off on v6.2.1 for v6.2.2
[Nexus S Android Development] pan1980:
had a reboot overnight with slimjb 2.8 and its default kernel (think its 6.2)

https://www.dropbox.com/s/vlzj73bvh4v4mgi/msg.txt?m
[Nexus S Android Development] :
You didn't tell me your phone model or whether you were overclocking
[Nexus S Android Development] pan1980:
correct.

i9023, overclocked for testing to 1096 and then restored to default.

reboot happened while night and phone was default.
[Nexus S Android Development] capoooro:
Stock...sorry for not having

Last kmsg but I was a little bit busy....
[Nexus S Android Development] :
Looks like wifi. I was working hard to find a fix last night. Wait a little while and v6.2.2 might be better for you.
[Nexus S Android Development] pan1980:
hm, i use juicedefender and wifi id off while screen is off...

i will wait anyway :)
[Nexus S Android Development] babe0607:
aokp buid 5

i have crespo with aokp build 5, v6 supercharged and marmite 6.2(not cm), cpu 100-1000.i wipe cache,dalvik cache and after i installed 6.2.1 and i fixed permissions it stuck on reboot.then i restored back up (With marmite 6.2) and everything was ok.i dont know why it stuck and i'm waiting for 6.2.2

thanks in andvanced
[Nexus S Android Development] alen1901:
Holly ****, look at this awesome sleep. :eek: great kernel and rom combination so far.

Bedalus, im going to try few hundreds of uptime. If rom doesnt get updated. :P than i will start all over again, with 6.2 ofcourse, because i dont have gpu and wifi problems.

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
Nevermind.
[Nexus S Android Development] pan1980:
here is another one,

i9023, slimjb 2.8.0 no oc.
[Nexus S Android Development] :
I'm not reading it because I'm not making exceptions, because once I say how I want something, I stick to it. Teacher habbit.
[Nexus S Android Development] caliban2:
Good. One trustworthy phone as testing ground less from now on.
[Nexus S Android Development] :
This looks like it was caused by wifi. Hopefully it'll be fixed in the next version. I've been trying out some more experimental stuff today too.
[Nexus S Android Development] Nexus-S:
Awesome kernel, bedalus. :D

Sent from my Nexus S
[Nexus S Android Development] omlet:
I can't activate bln =/

I've set the init.d script but doesn't work

I'm on 2.51PA =)

thanks!
[Nexus S Android Development] BenHeng:
I had some trouble with bln. Finally, it was because copy/pasting had inserted "space" in the path of the script. Rewriting it from scratch worked.

Aldo check where is busybox on your phone (bin, xbin, sbin...)

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] spider623:
Thanks I will stick with thalamus for the time being (that think works with everything!)
[Nexus S Android Development] LibertyMonger:
Good, one less whiner we have to waste our time with. I hate whiners.
[Nexus S Android Development] mdean1981:
I think people forget this is a developers forum. Things do have bugs because they are currently in "development". Something I think people have forgotten the definition of. If you don't wanna help work out bugs then don't flash, simple as that in my opinion.
[Nexus S Android Development] aladin6:
If I were in their place, i'd put marmite as the default kernel in CM10 for NexusS. But, who's listening :D :rolleyes: ...
[Nexus S Android Development] towelboy:
Stop the fighting everyone, don't want my favorite thread to have something like this happen! :(

Paranoid Android & Marmite 6.2 CM

Anyways, good news I broke the 100hr+ on time! Did 33% 1Ghz, 33% 1.096Ghz & 33% 1.2Ghz, and wow I'm amazed by the 1.096Ghz because it is actually stable imo, and benchmarking results show its even faster then 1.2Ghz in a lot of areas! Thank you bedalus! :thumbup: :D
[Nexus S Android Development] kwibis:
Lol at caliban2 for feeling so special! Bedalus is developing for us and we may assist him in that if we're able. How can you show such arrogance.

Sent from my Nexus S
[Nexus S Android Development] Basche:
How was your usage when performing the tests?

You have just been beamed
[Nexus S Android Development] towelboy:
Regular social apps (Facebook, Pandora, instagram, messenger, xda (if that counts)) & games like dead space, final fantasy 3, jetpack joyride & temple run) also I used antutu & quadrant
[Nexus S Android Development] Basche:
Nice, did your social apps updated frequently? That's good otherwise thanks for the info :)

You have just been beamed