yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] showmrock:
Can't wait for the "0" bug to be eliminated....spare parts shows it running more than the whole android system! :(
[Epic 4G Android Development] Rodderik:
thats what i need tested with that kernel build
[Epic 4G Android Development] Rodderik:
http://www.youtube.com/watch?v=H3avYUPVPJI

this build also has the kernel splash image re-enabled...

when you turn on your phone the first thing you see on the screen is the logo.jpg located in the param.lfs

then when the kernel is loaded it swaps to an image in the kernel

and then finally loads your boot animation

so when you turn on the phone it plays 2 pictures before the boot animation. in EB13 the kernel splash was disabled. should provide us with a clear indicator of which kernels we are running :)

other kernel changes are in the README on github except what i am testing with that build
[Epic 4G Android Development] wto605:
Results of 1.0.1

After 1.5 hours of continuous uptime, ~1 hour of idle, ~30 mins of use (10 minutes continuous).

kswapd0's CPU time is 29 seconds, 0 does not appear.

Looks like that fixed it... when I get a chance I'll flash back to 1.0 and see if the changes AutoKiller Memory cause the issue.
[Epic 4G Android Development] burgerpimp07:
I'm one of the ones affected by the 0 bug. Not sure if you already know this or not, but right after I installed SFR and this kernel on my phone, after a full wipe/odin I didn't have the bug, and battery life was great.

After a few reboots/days, the bug seems to be back and taking up more than 2x the network usage of android system.

Will flash this kernel and report back.

*edit*

I know it is a little early to say, but its already showing in spare parts as 2x android system.
[Epic 4G Android Development] showmrock:
I only see the single boot image (silver genocide logo) when I boot. Running SFR 1.1....should I have flashed this over another kernel? Not sure if I have the kernel running properly.
[Epic 4G Android Development] KennyG123:
This "0" bug only shows up in network usage right? I show it higher than Android also.
[Epic 4G Android Development] wto605:
No, this is the CPU bug. kswapd0 is occasionally only identified as 0 by the CPU tracking.
[Epic 4G Android Development] KennyG123:
0 shows up in Network usage in Spare Parts as a little greater than Android but nothing in CPU usage.
[Epic 4G Android Development] burgerpimp07:
Im having this issue. Didn't have it after a fresh install of rom/kernel.

Battery life started suffering when 0 appeared in network usage. Also not experiencing any 0 usage in CPU.
[Epic 4G Android Development] wto605:
On linux (and therefore android) UID 0 is the root user, anything that cannot be identified but is running as root is dumped into this bin... some android forums claim to have various circumstantial evidence evidence that qualcomm baseband stuff being reported as UID 0... since we have qualcomm radio's this is entirely possible.
[Epic 4G Android Development] KennyG123:
OK, so in layman's terms, would apps using 3G be considered as unknown and dumped in here on network usage? Like XDA and Wordfeud or Words with Friends?
[Epic 4G Android Development] theimpaler747:
No, they should show up as their respective app.
[Epic 4G Android Development] KennyG123:
In Spare Parts under network usage I am only getting the "0", Android, and Dialer showing up. Does this mean I have this bug or is it nothing to worry about?
[Epic 4G Android Development] theimpaler747:
Possibly. Try the new kernel posted by Rod, should fix it :)
[Epic 4G Android Development] wto605:
https://encrypted.google.com/search?q=android+uid+0+network+usage

This shows some possible culprits, the biggest of which is probably certain forms of tethering. Also, think of UID 0 as a catch-all... a million little things may make up more data than anything else.
[Epic 4G Android Development] showmrock:
I've always had the "0" bug....since flashing the test kernel from today I still see it after about an hour but its dramatically less than dialer and system. Maybe its reducing.....ill keep you posted
[Epic 4G Android Development] KennyG123:
OK so a LOT of people are seweing this bug. It's TWS all over again.
[Epic 4G Android Development] wto605:
Yes, but again I think this is a reporting error... the network usage may well be occurring (or it may not be) but it isn't even necessarily from the same source. If a computer (or phone) tried to keep perfect track of everything it was doing it would spend all its cpu cycles doing that.
[Epic 4G Android Development] wto605:
AutoKiller

OK, I reverted to 1.0 with AutoKiller disabled and after ~20 mins of uptime I am seeing kswapd0 reaching 70%+ cpu usage... so while AutoKiller does mess with the built-in task killer it doesn't seem to be the only source of the issue. Glad the update fixed it! Hopefully it didn't roll back anything that was supposed to have a big benefit.
[Epic 4G Android Development] KennyG123:
I'm sooooo confused!!! So then this "0" in the network usage is not the bug Rod is trying to fix and is common and may or may not be something to worry about. So the new kernel won't stop this?
[Epic 4G Android Development] XxLostSoulxX:
New? its been 1.0 since a month ago and 26 days close enough to being 2 months haha
[Epic 4G Android Development] KennyG123:
See about 10-15 posts back. He put up a kernel to fix the cpu usage bug.
[Epic 4G Android Development] wto605:
No, this bug is to fix kswapd0

CPU

usage... which sometimes gets reported as UID 0 (see above)
[Epic 4G Android Development] KennyG123:
OK, so if Spare Parts doesn't report UID 0 or kswapd0 in cpu usage I don't have this bug. And the "0" in network usage is basically every network call lumped into one tab and is a reporting issue with Spare Parts and not to be concerned with at this time. I got it right?
[Epic 4G Android Development] wto605:
Yup, some of that stuff about UID 0 in network usage may be an opinion or assumption on my part... but the fact surrounding it is that there is no way to know what UID 0 means.
[Epic 4G Android Development] theimpaler747:
No. He changed the source today.
[Epic 4G Android Development] Rodderik:
not 2 months...it's been a little over 3 weeks

here is the post to the test kernel

http://xdaforums.com/showpost.php?p=13227626&postcount=1743
[Epic 4G Android Development] Krazy_P@:
So you obviously didn't look back maybe 10-15 posts hua? Itz not an official release just a test build....
[Epic 4G Android Development] showmrock:
Rodderick........I'm only seeing one boot image (silver genocide).....I'm on the latest SFR running EC05....does that mean there was an issue installing?
[Epic 4G Android Development] Rodderik:
unless you changed the logo before hand in the param.lfs you should see the samsung screen then the kernel logo before the boot animation
[Epic 4G Android Development] showmrock:
I see the samsung screen, the genocide logo, and boot animation.....however I do not see the red skeleton giving the bird image.....is that ok?
[Epic 4G Android Development] Rodderik:
yes it is right...the reason the video had the skull is because where i explained about being 2 logos i had to take one of them out of the equation....you will have to pull up my old thread about changing the logo in param.lfs partition
[Epic 4G Android Development] musclehead84:
I've been running this kernel since its first release and its very stable and fast. I can't thank team viper enough for this. Can't wait also for official froyo to get more done to this kernel.

Sent from my Evo Killer!!!
[Epic 4G Android Development] BeerChameleon:
Question, is the kernal build suppose to say, genocide or does it just have numbers?

Sent from my Bonsai Epic 4g

Seems to feel faster and better battery so far, hopefully didn't flash bad and didn't change.
[Epic 4G Android Development] professoroak:
I'm pretty sure it's supposed to stay the same with the numbers. But if you check setCPU, you'll see that you have an option to set the max to 1.2GHz. And if you check "info" it should match the screenshot in the original post.
[Epic 4G Android Development] BopChie:
goto ingo in set cpu.. or just see if u can set to 1200mhz.. ifso then ur fine, you wont currently see genocide in the "about" panel of settings
[Epic 4G Android Development] Rodderik:
above 2 posts are correct....i didn't add any markings to show anything different in about phone yet
[Epic 4G Android Development] BeerChameleon:
Oh ok, thanks, i figured since it let me goto 1.2 ghz in set cpu.
[Epic 4G Android Development] lazyart:
Saw what I did wrong. I'd set it to 100, not 1000. Funny how that made a difference. :o
[Epic 4G Android Development] vocaltreat:
So far soo good!!....Roddrick.....He makes dreams come true ;-)

Can i get a HOT TUB!!
[Epic 4G Android Development] mattallica76:
Actually, unless you intend to lower the max clock at 1Ghz, just uninstall SetCPU and let it fly. This kernel scales better on it's own without SetCPU. Sometimes SetCPU can cause these issues.
[Epic 4G Android Development] Rodderik:
correct for now it scales to 1.2ghz even w/o setcpu...i'm working on compiling another version so we can verify it install in about phone and not have to rely on setcpu

eventually i want to make the kernel default to 1ghz and we have to install setcpu to bump it up...but for now setcpu is not needed if u want 1.2...just flash and it will fly
[Epic 4G Android Development] jirafabo:
Oc widget

Any reason to use setcpu over oc widget? I like the widget so i can see how b a my phone is.
[Epic 4G Android Development] mattallica76:
I personally prefer SetCPU over OC widget. Has more options and has it's own widget also. But like I said before, I would rather just let the kernel do it's thing and not have a program telling it what to do.
[Epic 4G Android Development] HeisRisen:
What's the adb terminal command to set clock freq? I thought I knew it, but it ain't working for me on this kernel.
[Epic 4G Android Development] thesals:
Thanks for the kernel, been running it since it was released. My phone is a bit snappier than stock dk28. The major change I've noticed is battery life is drastically improved. Usually I have to charge my battery every night, I've been up for 2 days without charging and my battery just hit 25%. This includes listening to music, wifi tethering a little bit, and playing angry birds as well as a few calls here and there and texts and whatnot.
[Epic 4G Android Development] Rodderik:
thats awesome...thanks for the feedback
[Epic 4G Android Development] HeisRisen:
How have you been up for two days with this kernel? Looks like it was dropped yesterday? Are you one of this testers?
[Epic 4G Android Development] wphend00:
My only issue is that I am unable to use USB storage mode on my phone now...

I am running Supernova's 1.6 EXT4 with the Kernel...
[Epic 4G Android Development] mattallica76:
Enable USB debugging and see if that helps.
[Epic 4G Android Development] tbob18:
Awesome kernel, runs really smooth.. Benchmark results at 1.2ghz with Midnight v3.3 are very good (17.223 in linpack, and 2259 in quadrant)

Another suggestion is modifying the Bluetooth stack to work with the wiimote apps. (not sure of the work involved or if it is even feasible)
[Epic 4G Android Development] tpike:
I've been on it since 5:30 pm yesterday fully charged overnight and unplugged this am at 7 and have 25% left. Id say average use more or less. Am on 4g all day no wifi gps on. Sound reasonable for 10.5 hrs?
[Epic 4G Android Development] burgerpimp07:
Maybe somebody can be so kind as to freeze every single app/service with titanium backup individually and see what it is that is causing the 0 network usage bug :)

I believe that it is not some application we are downloading causing the insane amount of network usage, I've been plagued with is ever since eclair, and my battery life becomes very ****ty because of it. I have to wipe everything and refash for it to go away, but even then its a matter of days before it returns. I have even tried keeping my phone bone stock to see if it happens, and it never fails.
[Epic 4G Android Development] bryanfritz1:
As far as the network usage rod suggested a while back to reboot and that seems to keep the "0" at bay as far as network goes, I wasn't really aware of the cpu usage but I may have just assumed the network "0" was the culprit and not looked any further.

sent from "The Other Woman"
[Epic 4G Android Development] JohnCorleone:
Just so I know I am looking for the right thing here (phone sticking at processing) when trying to go back pages, I go in Spare Parts,then Usage Statistics, then down the list of what's been used and for how long, and should see "network 0" if I have the bug? Sorry just trying to clarify. Thanks
[Epic 4G Android Development] JohnCorleone:
Well, I found that big fat network 0. Going to flash the new kernel now..
[Epic 4G Android Development] KennyG123:
As far as I can tell, the "0" in network usage is badsically all apps using 3G. It must be a big secret to Spare Parts what programs go through there so all get lumped into the "0". Running Words with Friends all day and only had 0, Android, and dialer in Network usage. Got home and switched to wifi and all of a sudden Words with Friends and anything else like XDA appeared in network usage and the 0 and Android dropped down to the bottom. So it is nothing to worry about. If you want to see 0 drop, turn data off for awhile.
[Epic 4G Android Development] Custodian:
That 0 has something to do with apps that are accessing root .speculation[OFF]
[Epic 4G Android Development] JohnCorleone:
One of the many mysteries of this phone. I am on 4g all of the time. Since I applied the new kernel, I actually have a little red in the 0 network bar that was solid blue before
[Epic 4G Android Development] KennyG123:
What does the red part mean?

Do you BONSAI?
[Epic 4G Android Development] Custodian:
Red part indicates the decline of whatever the usage is...
[Epic 4G Android Development] KennyG123:
Ah so red part may be like 50% usage at that point and dropping off.

Do you BONSAI?
[Epic 4G Android Development] JohnCorleone:
So the red part would indicate a good sign if previously it was a solid blue bar across with a "0"?
[Epic 4G Android Development] wto605:
In Network:

Red = Upstream

Blue = Downstream

The patch is for UID 0 appearing in CPU
[Epic 4G Android Development] JohnCorleone:
Forgive me. That's what I get for posting without any sleep. Thanks
[Epic 4G Android Development] Rodderik:
so what is the verdict of the test build?

reply 'yes' if it's better and i will leave the lowmemkiller patch out for now

or

reply 'no' if it isn't better and i will put it back in

thanks for testing and responding
[Epic 4G Android Development] wto605:
YES, infinitely better.
[Epic 4G Android Development] JohnCorleone:
I would say Yes....
[Epic 4G Android Development] ezsoulja:
I love this kernel but i cant figure out why is it everytime im using this kernel i get hella FCs and would have to reflash a rom.. usually happens when i undervolt and it locks up :confused:
[Epic 4G Android Development] JohnCorleone:
All of our Epics are different. Some can undervolt a lot, mine I can't seem to undervolt mine much if at all or I get a force close somewhere. I get such good battery life anyway that I can't complain
[Epic 4G Android Development] Rodderik:
if you read the OP in big red letters you would have seen your answer
[Epic 4G Android Development] wto605:
Also, if you are on EXT4 and your phone locks up and/or restarts you may corrupt your /data/ partition since journaling is off for the EXT4 support.

Mine's the same way... I don't even bother to undervolt anymore. In reality, undervolting is kind of like threading a needle, you need enough electrons to move into the gate before the next clock edge but that threshold isn't really that far below the number of electrons the gate can hold in the first place. The only savings you get are from the resistance through the chip and power circuitry, but if your undervolt is too aggressive the FCs, Lockups and bad checksums are going to take up more power just by the number of extra cycles you'll need... let alone if you cause (undetected/uncorrectable) data corruption.
[Epic 4G Android Development] computerkid23:
trying to save u from fire from my boy Rod lol jk but look in the OP my dude all you need is there lets you know exactly what your asking

REQUIRED READING: IF YOU DO NOT READ ALL OF THIS THEN I WILL NOT PROVIDE SUPPORT FOR YOU UNTIL YOU DO!!!!

good luck bro
[Epic 4G Android Development] JohnCorleone:
Thanks again Rodderik for more great work. Like the boot ani by the way...leave no doubt whose kernal is powering these Epics! Always seems like you look out for us too. Your "test" versions never seem to let anyone down.
[Epic 4G Android Development] KennyG123:
The best thing you can do is to turn journaling on. The easiest way to do that is restore a known good nand backup. I have had several lockups playing with undervolting with no force closes or data corruption.

Do you BONSAI?
[Epic 4G Android Development] Paleryder:
I would also ask before turning Journaling on, what ROM are you on if the answer is not SRF 1.1 DO IT
[Epic 4G Android Development] JohnCorleone:
Yeah get the journalling on. If the undervolt is too much, it won't corrupt thev data causinf FCs
[Epic 4G Android Development] KennyG123:
I prefer the peace of mind of journaling.

Do you BONSAI?
[Epic 4G Android Development] BeerChameleon:
Honestly i dont care if i have journaling on or off...

i have titanium backup all my stuff nightly so if i get corrupted data i can just wipe everything reflash the rom and restore my back up in a matter of a half hour, i hardly ever use nandroid backup anymore, not very efficient... and sometimes doesnt fix issues with corrupted data or issues, so i really dont use it ever...
[Epic 4G Android Development] p3dr0maz:
Testing 1.1. Like the Genocide logo btw.
[Epic 4G Android Development] Paleryder:
Thats what ive found myself doing as well. I have exp. a few either drops and battery popping out due to thin rear door and sometimes a text or call while tethering will cause a reboot followed by FCs its bound to happen with Journaling off unless your phone is in a glass case. Either way will give you piece of mind.

David what does paid Titanium version get ya any idea?
[Epic 4G Android Development] musclehead84:
I can't remember what the differences are between the paid titanium and free but I know one big is that u can freeze apps.

Sent From My Evo Killer!
[Epic 4G Android Development] MysteryEmotionz:
You can freeze. Upload backups to dropbox. You can make more then on backup. You dont have to hit install on every app when doing a batch restore.(this one is what got me to buy sucks hitting install 133 times)
[Epic 4G Android Development] KennyG123:
Paid app allows you to freeze running apps and have multiple backups.

Oops Mystery beat me to it.

Do you BONSAI?
[Epic 4G Android Development] Rodderik:
now now we cant have the kernel falling off the front page :)
[Epic 4G Android Development] JohnCorleone:
Heck no, this kernel(s) have been pure magic for my Epic! Although its not the recommended route, my phone loves SETCPU at 1400/200 "on demand" CPU Spy makes me smile every time I check to see how the kernel is distributing the power.
[Epic 4G Android Development] Custodian:
Now now, us leechers want daily updates but doesn't mean we get them lmao.....
[Epic 4G Android Development] KennyG123:
Falling off the front page just means it works great! No support needed. OK, I got a question for everyone. I put this on my gf's phone running Bonsai 3.0.1. Now after a short while the ringers stop working and she has to reboot to make them come back. Phone vibrates only when a call comes in. I set all the OC and UV to stock numbers. Any ideas? Thanks.
[Epic 4G Android Development] Custodian:
Reinstall the rom. I believe this bug is from aggressive uv's associated with the phone not going into deep sleep when idle. Happened to me quite often. Hope this helps, as it could be a number of reasons why....
[Epic 4G Android Development] JohnCorleone:
Rumor has it that the next Bonsai automatically changes your recovery to 3.0.2.4 and makes your nandroids and some other saved files unattainable ...
[Epic 4G Android Development] KennyG123:
Actually it is 3.0.2.5 and that still needs to be tested. I had trouble going from 3.0.2.4 to 3.0.0.6 backups. It required rerooting of 3.0.0.6 to clear the Clockwork errors. Not unattainable, just a few extra hoops to jump through if you need to go back.

Do you BONSAI?
[Epic 4G Android Development] KennyG123:
Never undervolted her phone and set bottom step to 200Mhz. But she leaves the screen and phone on for long periods of time. Didn't happen before the kernel.

Do you BONSAI?
[Epic 4G Android Development] Custodian:
Well my friend, as stated. This has happened before to me, and I refashed the rom. Not saying its the same problem for you, as I have been running geno for some time. Now, if you feel like your GF phone is having difficulties with this kernel, reflash to see if the problem persists, if it does then this kernel at its current release is not for her. Flash her previous kernel, or tryout others vision/bonsai/twilight etc...
[Epic 4G Android Development] JohnCorleone:
Thanks for clearing that up. I had the issue while testing 3.0.2.4. I freaked because my lappy is so fickle and I had major problems getting back to 3.0.0.6. Was so happy to see the orange and black screen again finally. I am sure Dameon has best of intentions in upgrading CWM but I was scrambling for about 15 hours...hehe
[Epic 4G Android Development] Rodderik:
i believe you may have been using a new CWM from koush...your friendly epic devs have been trying to work with him on getting a rom manager support back on the epic
[Epic 4G Android Development] JohnCorleone:
Thanks Rodderik. I didn't try it for very long though so any judgement on my part would be unfair. As soon as I had a little problem accessing my SD files, I went running for 3.0.0.6. I was just going to beta test a ROM (as I fortunately get to on a few). When the features didn't work exactly like 3.0.0.6, I just went back to what I was comfortable with. It automatically installed with a beta version of an unreleased ROM....WISH IT WAS VIPER I GOT MY HANDS ON!,LOL
[Epic 4G Android Development] KennyG123:
Yes, you are right. The first thing tried should always be a reflash. I don't think it is the kernel, but hoping it was something minor I could tweak. I break into a cold sweat everytime I mess with her phone. I will reflash Bonsai and leave her with that. Thanks.

Do you BONSAI?
[Epic 4G Android Development] KennyG123:
Yes Rod, they are working with Koush on the 3.0.2.5.

Hope it works out and nands are compatible.

Do you BONSAI?
[Epic 4G Android Development] JohnCorleone:
Not too sure the nands were compatible if my memory serves me right. Of course I was already in panic mode at this point but I swear I wiped everything 3x went to restore one of my two multi tested restores and the same ROM I threw on there to beta test was right back again. Hope this is helpful. Those who know about the new version know which ROM will most likely be implementing it.
[Epic 4G Android Development] JohnCorleone:
By the way Rodderik, the kernel has been outstanding for me. I haven't heard much about the new version but its great for me.
[Epic 4G Android Development] Rodderik:
thats good to hear...i've got a few things i'm working on for you guys
[Epic 4G Android Development] JohnCorleone:
Oh by the way, decided to check TWS (Time Without Signal)....0!
[Epic 4G Android Development] stir fry a lot:
For whatever reason running SetCPU at Conservative enabled my phone to handle 1.4ghz. Twilight, Vision and this kernel would normally insta freeze anytime 1.4ghz got selected but I was messing around earlier and somehow pulled this off.

What's weird though is that SetCPU always shows it topping out at 1.3ghz and CpuSpy is showing it maxed at 1.3ghz as well. However SetCPU allows the 1.4ghz option and my benchmark program gives me results stating that its running @ 1.4ghz. Games are also smoother and the UI is snappier. Whatever the case is thanks for the great work.