yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Articudos:
As far as I remeber, trinity muenchhausen(dunno exact name, look at bedalus' rom R&D spreadsheet) waa 410mb;)
[Nexus S Android Development] stojshic:
Isn't that the version that had camcorder problems? Morfic took too much memory allocated to camera, as long as I remember...
[Nexus S Android Development] CrackerTeg:
Well said.

Is this directed at me? I don't care to look up post numbers but I'll assume it is. Like polo had said, I asked version number because it could help users help you and not just bedalus. As for your little quote, read the bottom of my signature. Get off your high horse. You're a user like the rest of us and are not helping your argument by posting like this.
[Nexus S Android Development] miklosbard:
EDIT:forgot to quote bedalus' post about debug version not failing...

just had a seminar today and they were talking about this. (different product ofc, but debug and non-debug versions working differently) and they concluded it was caused by having different complete flags set for the debug version and something else(I don't remember :() , that made the binaries to be different at the end. Probably you have something like this, so if you find what you do differently in the debug kernel, you can make the nondebug version more stable with using that.
[Nexus S Android Development] Articudos:
I heard that used cm9 ramdisk, so it should work fine with cm9. That time was w/o highbigmem except cm9 ROm..
[Nexus S Android Development] beppegg:
It took ages to break that kernel, that's not my fault! :D
[Nexus S Android Development] mishamosher:
Well, I don't see neither how your comment helps. I'm not telling you anything about your aptitude, neither what to do or not.

Is kinda disrespectful say something about a new user, put "high horse" kinda phrases, and just want to make feel that user like he is bad, that is doing nothing good to the community. But we learn, we cooperate, we are homo sapiens and argue just because of wanting does nothing.

Sorry if did something against your ideals and you're feeling like against me because of that, really sorry.
[Nexus S Android Development] polobunny:
Let's not start a fight in bedalus thread. It's clean enough from spam, we don't need any other crap flinging thread. You can go argue with zeppelin about his supercharger if you want that. :laugh:
[Nexus S Android Development] caliban2:
Did a full wipe the other day and noticed something strange:

For the first time in ages I used the save & restore feature. Phone was quite laggy afterwards and when waking it up from standby, it took the screen a second to come up (push power - wait - screen on). Didn't take 3 hours for it to freeze and reboot... Marmite 4.8.3 was rock-stable for days before that!

Another full wipe, didn't restore from my Google-account, phone-settings manually, Titanium for apps (like I normally do) -> fine and stable.

Either it was a bad flash or the restore-feature is messing things up. (again, this happened with the same rom/kernel-combo that has been stable for two days before!)

One more thing:

Marmite 4.8.7 plus CM nightly 1010 (JB 4.1.2) is a new milestone regarding speed and smoothness. :)
[Nexus S Android Development] mishamosher:
I'm wondering... how can I change kernel voltages?

I'm guessing that it must be done when building it. If so, what must I change at build? Or if I'm wrong, what I'm supposed to do?

Last DEBUG version isn't giving troubles, I'm not OC'ing, going to try at 1.2 GHz step, to see how it goes. Seems like my i9020A doesn't like the 1.3 Volts of 1.2 Ghz step...!
[Nexus S Android Development] xtracrispy:
Howdy,

Thanks for all the great work so far in creating an awesome kernel!

I'm here with a report on some visual artifacting though, presumably due to the recent buffering tweaks.

NSTools was the culprit, I have not seen other programs that do this though. Weird things happen; the app screen even stays on the notification drawer, and slides up and down with it when I swipe.
[Nexus S Android Development] mishamosher:
@xtracrispy Also had this, and it's NOT because of buffer thinngs of last kernel.

It seems like a bug of the app NSTools, when fastcharger was added to the kernel, NSTools gets weird when going down to the list and then back up in the "Tweak" tab.

If you noticed, when going to another tab and then back to "Tweak" it gets correcter, then do the scroll down and then up thing and it gets weird again.

It happens with ANY of the versions of marmite that has fastcharge, no matter of buffers thing.
[Nexus S Android Development] polobunny:
Oh oh I wonder if it's because of that! If you flash to an earlier kernel is the problem fixed?

I'd be a sad panda if bedalus had to revert back for simple stuff like this.

Edit: Good to know mishamosher!
[Nexus S Android Development] mishamosher:
Attached two images with marmite 4.8.3, wich doesn't has buffer things. The problem is there, and it borned because of adding fastcharge to the list of "Tweaks".

Sorry for the notification bar displayed. Did it to avoid "Hey, who will make sure that u're not on marmite with less frames?" things... :D
[Nexus S Android Development] CrackerTeg:
That's incredibly odd. Is this with stock/cm/whatever else? I don't see this on the any other ROM version since before and after fast charge was added along with the extra frame buffers being removed. I'm curious of what roms are being used along with tweaks installed and available memory at the timne this happens.
[Nexus S Android Development] mishamosher:
I was using CM10, October 17th. Clean install. No tweaks, no changes, no apps running, no nothing.

Also happened on MIUI, AOKP and EuroSkank JellyBro.
[Nexus S Android Development] Imppy:
Hey bedalus ...just to let you know your 3.4.7 is working well with the latest rasjelly 4.1.2
[Nexus S Android Development] CrackerTeg:
Seems like a cm based kind of thing. Though, I don't think MIUI is cm based. Not sure on that one.
[Nexus S Android Development] :
I think the crucial bit is

[12059.211393] EINT_PEND 0x6, 0x0, 0x0, 0x40

where it looks like 0x6 must be an interrupt that causes the device to restart. What I don't really understand is what this interrupt is doing there. I need to research it more, but a little googling makes me wonder if it is due to the high resolution timers. I'm trying to see if there is a patch for the high res timers now...
[Nexus S Android Development] polobunny:
Didn't you already suspect the hi-res timers from causing this? IIRC, it was mentionned when I got a reboot once.
[Nexus S Android Development] :
Yes, and I tried to avoid including them in my kernel. I might have better luck at disabling them now I know what I'm doing a bit more. I'm also considering some patches.

EDIT: Just tried building with the high res timers disabled, and it built and booted!

Played asphalt 7 to test, and seemed fine. I'm so exhausted right now, no uploads until tomorrow!
[Nexus S Android Development] mishamosher:
"Standard" official miui build are based on the last stock available for the device.

That's why there are miui v4 based on JB and ICS in concordance with the device's last stock version. Even the kernel used is stock!
[Nexus S Android Development] beppegg:
If you want to build a debug version, I will install it and give a try.

Your kernel is the best piece of custom software I've ever seen, it's unbelievable you're not an experienced developer!

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] leap_ahead:
High Android os on 4.8.7 20%
[Nexus S Android Development] :
I'm going to go ahead and upload the 'no debug' version, because I'm pretty sure the high resolution timers are causing problems. I can't remember why, but I'm going to trawl through my own posts here in a minute and see where and when I already posted about this.

I'm not experienced in C or android especially, but I did start programming at about age 10, and carried it on til about age 20. Turbo pascal isn't hugely different from C. That was more than ten years ago though. Anyway, I seem to have picked it up without too much strain. Without wanting to blow my own trumpet (but then going ahead and doing it anyway) I'd say my main strength is in problem solving. It's a mathematician thing.
[Nexus S Android Development] :
Here are some v5 candidates

-Non 4G Non CM: http://d-h.st/kL3

-Non 4G CM base / knzo Strawberry: http://d-h.st/40Y

I found where I got the notion about high resolution timers. Apparently disabling them seemed to completely solve stability in my ICS kernel. However, testing wasn't quite as rigorous as it is now. But around the time I originally did that, all reports of reboots stopped (could have been co-incidence). The other post I found was when I first tried this in Jelly Bean, and I wound up re-enabling them, but I can't find any other posts about why I felt this was necessary. I did try and re-enable them again recently, but it didn't work because systimer was defined twice, but it turns out I solved this when I went on a mission to correct all the minor compiler warnings.

Anyway, try it out and feedback. Fastcharge is a new feature, plus the extra RAM is pretty cool, so I'm going to be jumping up a version number. :D
[Nexus S Android Development] sidnoit22:
I can use CM base for Paranoidandroid right?
[Nexus S Android Development] mustatir:
Yup
[Nexus S Android Development] polobunny:
Strangely enough I started doing BASIC myself around the same age, on those little kids computers that my parents bought me thinking it would further improve my already somewhat strength in academics. Good times haha!
[Nexus S Android Development] CrackerTeg:
So should we call this marmite vX?
[Nexus S Android Development] beppegg:
I'll flash that too! :D I was just giving my consent to be your guinea pig :D

So you're a methematician? That explains all: Computer Science can be viewed as a child of Mathematics!
[Nexus S Android Development] polobunny:
It would be right if it was Marmite v10, but it's 5. Marmite vV! lol
[Nexus S Android Development] DarkhShadow:
Why hello there MR random reboot

BB5 and 4.8.w/e debug version(havent updated yet)
[Nexus S Android Development] polobunny:
Sadly that's not good, that's a log from Clockworkmod Recovery. What happened exactly? What where you doing when it rebooted?
[Nexus S Android Development] DarkhShadow:
Urg, I wasn't doing much, I had just slept the phone then noticed a few mins later the boot animation xD
[Nexus S Android Development] CrackerTeg:
True but I meant it as non numbered/ experimental rather than Roman numeral.
[Nexus S Android Development] polobunny:
It's possible the last_kmsg couldn't get written in time, hence why you get the one from CWM.

Are you overclocking?

I know, just playing. :p
[Nexus S Android Development] DarkhShadow:
Nope only tried overclocking on this kernel once and it kept rebooting(before voltages were lowered) and it didn't give me much benefit
[Nexus S Android Development] Articudos:
Hmm....Using 4.8.7, battery life is great.

But, when I do heavy-multitasking, music causes terrible noise just a while...

When that causes again, I'll reboot immediately and upload last_kmsg.

Will that helpful..?
[Nexus S Android Development] BenHeng:
Marmite v.V ( :p) is perfect so far on my i9023 with BB5. Thx!

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] CrackerTeg:
Its all good. I knew you were just messing.
[Nexus S Android Development] stojshic:
Using 4.8 with rasbean, had a reboot while looking at xda thru Tapatalk...

http://db.tt/OYMBzLFX

Hope this kmsg helps...
[Nexus S Android Development] caliban2:
Tested for 6 hours - nothing wrong with it, but 4.8.7 is snappier.
[Nexus S Android Development] CommanderDuplex:
can't use 1.2ghz :/

why no Custom-Voltage table ?

your Kernel seems perfekt for the Ns atm. good battery and speed !
[Nexus S Android Development] CrackerTeg:
I noticed the same. Though I haven't been running the newest version as long.

---------- Post added at 01:05 PM ---------- Previous post was at 01:02 PM ----------

The custom voltage table will introduce entirely too many variables and crashes. Users will then complain and blame the kernel, yada yada. Bedalus has come up with the best voltages he feels the kernel needs to maintain stability. Makes for less headaches on his part.
[Nexus S Android Development] polobunny:
In other news, still on post 4.8.3 debug version. It's getting boring here, not crashing and all that jazz. I'm like 10 billion versions behind. :p
[Nexus S Android Development] micha3lvd:
Might be or might not be relevant to the kernel but i'm having some trouble with my e-mail:

I got 3 accounts synced for mail (hotmail, IMAP & IMAP) However when disabling sync for those email accounts I stop receiving mails, though the timer is set to check every hour / 2 hours.. anyone got any clue?? I've tried some stuff but with removing and adding my account twice the exchange service shows 34% usage of my battery life (of 11h on battery)

Thanks in advance :)
[Nexus S Android Development] polobunny:
That's not relevant to the kernel. It would be better for you to get help in a more general section.

I know there's bugs with exchange server in ICS/Jellybean eating a lot of resources and getting "stuck". Can't help you much more though because I don't use an exchange server myself.
[Nexus S Android Development] caliban2:
Then move on to 4.8.7, for crying out loud! :D
[Nexus S Android Development] polobunny:
I'm waiting for it to break. I might never move on if this kernel doesn't break. :p
[Nexus S Android Development] CrackerTeg:
Screw that. Go bleeding edge! Its fun not having time between versions to test. Keeps you on your toes.
[Nexus S Android Development] polobunny:
I used to do that but it's annoying to get a reboot when you're texting a lot of people or in a call. That was killer fun when I was selling my condo. :p

I'll update eventually, I expect I'll get a ROM crash at some point so it'll give me a reason to update both.
[Nexus S Android Development] CrackerTeg:
True. I gotta say though, the 4.whatever's have been pretty good to me. Then again, it may be because I'm not running anything cm based. I'm guessing the version in your sig has been the most stable so far for you?
[Nexus S Android Development] caliban2:
CM plus marmite is a stable combination for some time now. After all it's been a while since bedalus got a last_kmsg from me. :)
[Nexus S Android Development] 309041291a:
Does the newest version support Paranoid 2.1.8 (Android 4.1.2)?

Nexus S (GSM i9020a)

Paranoid Android (2.1.3 - 4.1.1)

Marmite Kernel (4.7 - Bedalus)

Ondemmand (Screen On) (800/100)

Ondemmand (Screen Off) (400/100)

Deep Idle (N/A - Deadline)

BLX (98 - Inverted Apps)

Black Exodus (Stock Voltage)
[Nexus S Android Development] mutantlx:
I installed the cm version for paranoid seems to be fine for me so far.
[Nexus S Android Development] capoooro:
OK first reboot... after a call 4.8.7

Always strawberry. I go to v.... hoping a boring day
[Nexus S Android Development] :
Battery: dropped from 80 to 70% in 20 odd hours. 0.5% per hour! That's ICS good.
[Nexus S Android Development] :
I think battery life is better in v5 (yes v5, not vV :p I didn't want to name it just in case hundreds of people wrote in with "OMFG MY PHONE BURNT DOWN TO PURE ASH THEN SOME CRAZY RED BIRD FLEW OUT OF IT AND SAID WHAT'S THE BEEF? AND I DON'T EVEN KNOW WHAT THAT'S SUPPOSED TO MEAN :( !!!!" which I was about 50% sure was going to happen. It seems to happen whenever I release what I think is a stable version. But since that hasn't happened, I'll label those downloads as v5.)

Music turning to very loud static indicates a corrupt mp3. Replay the same track. If it turns to static in the same place, it is corrupt. However, if it is just stopping and starting for a few milliseconds at a time, it may be that the system just isn't coping well enough with the playback. A higher audio buffer might help, but may cause noticeable lag in some sounds.

The voltages were calculated based on what I think is a sensible formula. I made a little spreadsheet and graph for it, and the link is still in the changelog on the download page. I suppose I could bring back 1275mV for the 1GHz step. I'm sure kalimochoAz had his reasons for that. But the current voltages are stable on my device, and I'll never add custom voltage.

It's very good of you actually. The last crash I saw from a debug kernel led me to some very interesting conclusions, and if you do finally get a different sort, it may again help to target possible sources of instability.

If you get a good combo going, do a nandroid.

Good enough seal of approval for me! I'm letting v5 loose.
[Nexus S Android Development] :
Calling all lid-lickers...

v5 is here: http://goo.gl/HvUrp

-Stable version. Several weeks in the making, thanks to all the brave testers! :D

-Disabled High Resolution Timers

Significant changes since v4.7

-Disabled high resolution timers

-Update to mainline linux 3.0.45

-Up-to-date with android-3.0/common

-there were unused frames in the frame buffer. Reclaiming it has given us 407MB! All credit to nightsky87!

-Add fastcharge

-Reduced 1GHz step volts from 1275mV (CM) to 1250mV (Samsung default)

-Reduced 1.2GHz step from 1350mV to 1300mV in accordance with my calculations (see: http://goo.gl/mEMfW)

-More memory from Ezekeel's bigmem tweak

-Fixed MTP on 4G

-Completly removed deadline

-Removed all debug stuff (separate debug builds available)

-Stability fixes

-55 files modified and maybe a hundred odd individual fixes. Most compiler warnings were meaningless, but some genuine errors solved

-Fixed colours, users without voodoo should now have a decent experience

-Added BLN modes (see OP for link to settings)
[Nexus S Android Development] CrackerTeg:
This just happened after flashing v5. I kid you not. Except instead of the bird saying "what's the beef?" it just looked at me, nodded its head and said "sup". Craziest thing.
[Nexus S Android Development] polobunny:
I just noticed my uptime is 24 hours... That means at around this time yesterday, my phone rebooted. I wasn't drunk and I just recalled rebooting to fix permissions to solve my light sensor issue (which worked). So yeah, broke my uptime on purpose, but otherwise it's not crashing. Would this mean all bugs are eradicated? That would be sweet. I watched some videos, played some games, texted, surfed the Web, and zero hiccups. :)

Edit: Totally jinxed myself here. My Nexus just went into a soft reboot loop while updating my apps. What gives! Last kmsg is useless because it's a soft reboot, thus all I got is log from recovery. Argh.

Updating to v5 and who knows. :/
[Nexus S Android Development] JokerAce:
I realize after a few days of test that, for my phone, which never run 1.2 Ghz successfully before, setting min_freq at 200 mhz helps to keep the random reboot issue at bay.
[Nexus S Android Development] anshumandash:
Is V5 is the same as marmite_v? I am currently running the marmite_v and if there are no changes, I would not flash V5 now.
[Nexus S Android Development] JokerAce:
And where did you see/get mamite_v?
[Nexus S Android Development] nightsky87:
Just a thought... Has anybody tried playing a video with the new framebuffer tweaks? I recall the GPU drivers have some separate code for video handling which might have been broken by the tweaks. I could be wrong though. I haven't updated my kernel for a while so I haven't tried this out myself.
[Nexus S Android Development] polobunny:
Just played a video via mx player in both hw decoder and sw decoder. All is fine on my side.
[Nexus S Android Development] nightsky87:
Great! No worries with video then. :D
[Nexus S Android Development] anshumandash:
The links in the below post were pointing to mamite_v. When I click on them now, they are pointing to V5. So I guess they are same.

http://xdaforums.com/showpost.php?p=32657619&postcount=3681
[Nexus S Android Development] JokerAce:
Yeah the ultimate version would be Marmite|X. Till then, we will be in numeric versions i.e. Marmite_v# where # is a number :cyclops:
[Nexus S Android Development] :
Haha, I'm trying to adhere to a numeric system. I'm trying to avoid 'showing off' with flashy names. That's why I called it marmite! I'm anti-hype.

http://xdaforums.com/showpost.php?p=31833636&postcount=2874
[Nexus S Android Development] beppegg:
More than 24 hours with marmite V.

I've just have to report speed and stableness!
[Nexus S Android Development] JokerAce:
I guess... I just can't run my sexy at 1.2 Ghz
[Nexus S Android Development] anshumandash:
I just checked android os is taking 22%. 26 mins CPU usage by android os. I am using the latest kernel on bb5.

Sent from my Nexus S
[Nexus S Android Development] leap_ahead:
same here when the phone is sleep ...
[Nexus S Android Development] BenHeng:
Same config, ni problems ( bb5+marmite v.5

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] deani77:
Still normal for me on latest kernel and CM M2
[Nexus S Android Development] caliban2:
Don't you forget the other sacred words, peng and NEEEEEEEE-WOM! :p
[Nexus S Android Development] polobunny:
And the funny coincidence is that the hardware name for the Nexus S is herring. :p
[Nexus S Android Development] :
Haha awesome lol
[Nexus S Android Development] JokerAce:
The latest kmsg I posted is not helpful? :D
[Nexus S Android Development] :
Looks like a software issue. if you're still on paranoid it's probably the cm base or app, or conflict. Update to v5 yet?
[Nexus S Android Development] polobunny:
I believe that's what the v5 means in his filename. :p
[Nexus S Android Development] :
Ah. Makes sense.
[Nexus S Android Development] alen1901:
Yeah, im back in the game. Marmite v5 flashed. Waiting for phone to explode or burnout because of speeeed. :eek::cool:

Sent from SpeedMachine i9023
[Nexus S Android Development] JokerAce:
Haha, yeah I always go for stables. But I just have to accept the fact that mine can't go 1.2Ghz.
[Nexus S Android Development] caliban2:
Regarding speeeed you're already missing out - 4.8.7 has that extra je ne sais quoi... :rolleyes:
[Nexus S Android Development] anshumandash:
I have a question about the last android os issue I posted. I had tried enabling MTP using the following commands before charging the phone.

setprop persist.sys.usb.config mass_storage,adb" <- enables mass storage.

setprop persist.sys.usb.config mtp,adb" <- enables mtp

Even though I rebooted, MTP didn't work That's fine with me. But is there a possibility it is causing android os issue?
[Nexus S Android Development] Skyline969:
So I downloaded and flashed v5 last night, and I must say it's much smoother than even matr1x 23.5. However, I've got a few questions:

* Is it true that I'd be better off with 4.8.7 if I want more performance?

* Ever since I flashed marmite, I've noticed my buttons below the screen don't come on when I have notifications. How can I set it so they do come on when I have a notification?

EDIT: Oh right, for reference, my ROM is currently Slim Bean.
[Nexus S Android Development] alen1901:
Damn. Yeah, i forgott about that version. Also 4.8.3 was great here. What the hell, i will try it out later when i get time. :rolleyes:What about battery on 4.8.7?

Sent from SpeedMachine i9023
[Nexus S Android Development] CrackerTeg:
I wish I could tell you since Marmite v? came out shortly after, followed by v5. All of them have been good to me in terms of battery usage, speed, stability, etc.
[Nexus S Android Development] polobunny:
Use this init.d:

http://xdaforums.com/showpost.php?p=32421499&postcount=3436

Change values accordingly tou your preferences.

(Also this is answered in the first post, although not very explicitely ;))
[Nexus S Android Development] Skyline969:
I did grab that and I tweaked it to my liking, although I cannot copy to /etc/init.d. From the terminal it gives me an error about it being a read-only filesystem (yes I became root prior to copying). Now that makes me wonder... would I have to change fstab to mount it as rw, or is there some other way to install this init.d script?
[Nexus S Android Development] polobunny:
Use a file manager with root support and if copying from terminal make sure to SU yourself.