yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] Joeway124:
Hey OP, thanks for this.

got a question if someone can enlighten me, i set my min to 100, max to 1200 on the main screen and i noticed that under frequency itll never go down to 100, lowest 200. I tried restarting SetCPU but it still never goes down that low. what do i need to do to get it down to 100 min?
[Epic 4G Android Development] v3rk:
not sure, but i've run into my phone not waking up when the min is set to 100
[Epic 4G Android Development] ddpacino:
Running Genocide_0.3a on Nebula ROM (DK28), overclock to 1200MHz and min of 100. NO problems so far. Seem to get better battery life, if slightly. Will continue testing. Keep up the good work!
[Epic 4G Android Development] ddpacino:
Yes, my min is 100 as well, and I only see it as low as 200... like right now since it's just sitting. If it's a safety reason, no qualms here.
[Epic 4G Android Development] darrinbc:
The only thing I have noticed is that, whatever I do, I can't get the phone to charge when turned off. When it is turned off, as soon as I plug it in to charge it boots instead of going to the charging screen. If I have it plugged in already and turn it off then it simply reboots instead of turning off.

I am on the stock EB13 rom rooted with the one click root and recovery v2.5.5 with the v0.3a kernel and setcpu installed. This didn't start happening until I installed the v0.2 kernel and the issue caried over with v0.3a

Is it simply a setting somewhere that I am missing?

Thanks much for all the hard work! So far, everything is awesome other than this one minor issue.
[Epic 4G Android Development] caspertodd:
Yeah, Rodderik is aware...check out posts 537 and 577.
[Epic 4G Android Development] cpcormier3:
I'm running stock EB 13 ROM with 1 click 2.5.... I flashed the kernel and now my phone reboots every once in a while. It usually does some vibrating (I'm in silent mode) before it reboots.

When I flashed I wiped data/factory reset 3 times, cache partition 3 times and Dalvik cache 3 times, before I flashed. I manually reinstalled some of my apps from the market place. I'm not running SetCPU or anything like that. Not sure why it keeps rebooting?
[Epic 4G Android Development] iamchocho:
+1 Thank you, this drives me nuts too.

People if your going to quote someones huge post please take the time to trim it to the parts you want to refer back to, no need to have every third post in the forum be the same 12 paragraph quote and re-quoted
[Epic 4G Android Development] Rodderik:
scratch that..ok here is the latest test version...this is purely a tester release just as a update for you guys until the next version comes out...DO NOT bug me with issues with this version until the next version is released!!!!

Changelog: (so far)

Battery Status Polling Interval changed from 2000 to 30000 (30 seconds)

Added RNDIS support for Wired Tether

Added CONFIG_ARM_THUMBEE=y (as suggested by gzub)

Set 4k read ahead in mtd_blkdevs.c (faster boot?)

existz-initramfs-i9000-suckerpunch ported to Epic - broken right now

Removed CONFIG_DEBUG_INFO=y (give us smaller kernel image and modules including new cifs.ko)

CFLAGS_KERNEL	= -O2 -pipe -mcpu=cortex-a8 -mtune=cortex-a8 -mfloat-abi=soft -mfpu=neon

*Removed About Phone information (Caused FC and weird bugs in apps)

Fixed error that wouldn't let cpu drop below 200MHz
[Epic 4G Android Development] caspertodd:
Gonna give .4a a try now...
[Epic 4G Android Development] BeerChameleon:
Nice, cant wait for the official one, btw are one of these changes the keyboard fix in different wording?

Bummer u had to remove the about phone info i like it when i know what im running. :(

Thanks!
[Epic 4G Android Development] caspertodd:
.4a is working great for me. Now dropping to 100 mhz as it should. Running very smooth. Cool! Thanks for this unofficial release!
[Epic 4G Android Development] pyroswithoutfire:
I am running the new Midnight 4.0 with the .3a kernel and have notices random reboots as well. I have noticed it tends to happen after a call my phone tends to reset. Also I noticed my phone would start rebooting when I set the max frequency to 1200
[Epic 4G Android Development] QuestingHero:
I also think the keyboard fix would be a great addition.
[Epic 4G Android Development] youngpro83:
What theme is being used in the OP?? I likes!!
[Epic 4G Android Development] Rodderik:
keyboard patch has been included on github for next release

theme is viperrom 4.0.4 (slightly modified for eb13) but released version works fine with this kernel
[Epic 4G Android Development] burgerpimp07:
Just flashed 0.4a, running fine.

Not restricted to 200MHz minimum and runs at 100MHz.

My battery thanks you. :)
[Epic 4G Android Development] professoroak:
So it looks like my dl speeds are back to normal after the test update. Cool update especially with the 100MHz fix!
[Epic 4G Android Development] TheDub:
Could this be why my test build of your kernel failed so horribly earlier?! Lol I noticed the initramfs was set to this but didn't bother changing it... needless to say the compiled kernel didn't boot lol... compiled no problem though ;)
[Epic 4G Android Development] Rodderik:
yeah i gotta do some more research but the i9000 calls for an internal and external sdcard...and when that initramfs is calling for the internal storage it is nuking the sdcard (has to be reformatted) so i have shelved that initramfs until i get some more stuff in the kernel i want...then i will go back and fix that initramfs...for now just use the genocide eb13 modded initramfs and it will work fine
[Epic 4G Android Development] TorelliB:
So i just patcxhed the eb13 camera fix....do i install this the same way...?? how do i go about putting this on my phone?? im a nub :(
[Epic 4G Android Development] TheDub:
That also explains my nuked sdcard :( ... lol I was able to use Recuva to get my pictures back at least mostly..
[Epic 4G Android Development] BeerChameleon:
Wait, which kernal, nukes the sd card??!! Do i need to unistall v.03?
[Epic 4G Android Development] jeffyv2:
Hey rodd im liking the new unofficial test build feels pretty smooth...

sent from my Epic 4G
[Epic 4G Android Development] TheDub:
No no no nothing will nuke your SDCARD, I nuked mine compiling and trying stuff on my own because I compiled with an experimental option that isn't working yet.
[Epic 4G Android Development] BeerChameleon:
Oh.. lol, that sucks man. :o
[Epic 4G Android Development] darrinbc:
Ok, I am having issues which may or may not be related. I am going to flash back to the stock kernel tonight and run that all day tomorrow to see if things clear up.

Stock EB13 modem rooted with one click root 2.5.5 and installed the .4 kernel.

Bluetooth has issues. Pandora works great with it, but calls have pops and distortion. Voices drop out and get electronic distortion. So bad that I cannot use it for phone.

But the camera works great and battery life is good.

Edit: Oh, forgot to mention that 3G speeds SUCK. I don't think that's related to this however. I have cleared cache a few times and updated my profile and PRL several times to no avail.
[Epic 4G Android Development] konaman:
.4 working great for me. .3 wasn't too good on battery so ill c what this one does. .2 was amazing with the battery life.
[Epic 4G Android Development] darrinbc:
I just flashed the stock EB13 kernel and have confirmed that the issue with not being able to charge my phone while off has been corrected. Now when the phone is off and I plug it into the charger it starts charging and shows the battery instead of booting like it was on .2, .3a or the newest test beta of this rom.

Not sure if that is a real issue or not, I am just trying to give whatever feedback I can to help out.
[Epic 4G Android Development] NYYFan325:
Where is the .4 that I see being mentioned?
[Epic 4G Android Development] k0nane:
Yeah, there's a storm on the loose, sirens in my head /

Wrapped up in silence, all circuits are dead /

Cannot decode, my whole life spins into a frenzy...

Help, I'm steppin' into the Twilight Zone...

;)
[Epic 4G Android Development] sjc924:
See post below. It is not an official release!!!
[Epic 4G Android Development] Bobulus:
I've experienced some weird audio-playback issues while running the 0.3 kernel. In truth, I don't know if it's EB13 or the kernel or what, but just throwing this out there:

- While listening to google's Listen app over BT headphones, I encountered a podcast that played perfectly in the left headphone, but kept cutting in and out on the right headphone. Sounded fine with corded headphones, so I think this is a stereo-bluetooth thing.

- While listening to a different podcast over the normal Epic speaker, it suddenly stopped playing correctly and played garbled gibberish. I backed up to an earlier part of the file, and this also played as gibberish. Rebooted phone. Shut-down sounds played correctly. After reboot, entire podcast played correctly, so it's not a corrupted file.

Never encountered either of these things while using Listen or the BT headphones on DK28.
[Epic 4G Android Development] Rodderik:
congrats guys
[Epic 4G Android Development] musclehead84:
Go back a few posts

Sent From My Evo Killer!!!
[Epic 4G Android Development] k0nane:
Thanks! Don't mind my post above, I couldn't help myself. You've done some good work here.
[Epic 4G Android Development] musclehead84:
Lol... I like that

Sent From My Evo Killer!!!
[Epic 4G Android Development] k0nane:
F-in' great song, right?
[Epic 4G Android Development] readermo:
very nice! i'll take twilight zone over radar love any day
[Epic 4G Android Development] k0nane:
Absolutely. That one sucked!
[Epic 4G Android Development] KennyG123:
I am running this at 1.2Ghz and only getting benchmarks equivalent to stock epic at 1Ghz. Def improvement since I was running 300-400 lower before but what could slowing me down?
[Epic 4G Android Development] Kitteh298:
I still haven't see help for this yet. I want my stock boot animation.. how do i do that. pm me please.
[Epic 4G Android Development] konaman:
.4 is giving me way better battery life. I'm on conservative setting and the CPU at 1200max 400min. I'm at 66% battery with 26hrs unplugged.

I'm using my extended battery btw
[Epic 4G Android Development] KennyG123:
There is a subject for restoring stock boot animation in themes.
[Epic 4G Android Development] durrett syndrome:
I have midnight 4.0 ext 4 with a gingerbread theme...I flashed the .3a OC/UV kernel...My battery life sucksssss...i dont use set cpu and thought this one was just for battery life...please help
[Epic 4G Android Development] Rodderik:
refer to this earlier post and try to flash 0.4a test build and see if it helps http://xdaforums.com/showpost.php?p=11752682&postcount=630
[Epic 4G Android Development] vocaltreat:
Awesome sauce

The test build is running wonderfully...so a huge improvement in batt life gratzi rod!!!
[Epic 4G Android Development] dchawk81:
I agree with it operating well. I can't speak for battery life yet though.
[Epic 4G Android Development] Rodderik:
thank you both
[Epic 4G Android Development] dchawk81:
No, thank YOU. You put in the hard work; we just download, press a few buttons, and enjoy.

Besides working at 100mhz now, does .4a also undervolt at all frequencies?
[Epic 4G Android Development] Rodderik:
.4a does not have undervolts yet...i've got a lot of small changes i'm working on before i stress test undervolts...i want to make sure they are rock solid...or i may try to get voltage control app to work so people can undervolt to what is stable for them instead of what it stable for every one...we will see...i still have a lot of work to do
[Epic 4G Android Development] Kitteh298:
me likey genocide :3
[Epic 4G Android Development] klownin816:
Same thing is happening to me. I'm on stock EB13. I think that might be my issue since I'm not on a custom rom that is tailored to the kernel.
[Epic 4G Android Development] durrett syndrome:
I flashed the .4 verzion twice and my phone used to say the genocide .3 under firmware version now after flashing twice my epic says...

firmware version - 2.2.1

Kernel version - 2.6.32.9
[Epic 4G Android Development] Rodderik:
yeah messing with the versions broke certain applications so i had to remove them
[Epic 4G Android Development] durrett syndrome:
so am I back to the stock kernel or back to the original .3 or what? thanks a lot man.
[Epic 4G Android Development] dmarden:
Have to say... my phone was running great with .3a, but I wanted to try .4a for fun so I did. Still running great and the battery life has been phenomenal.

My profiles are very simple.

51%+ = 1200/100

50%- = 1000/100
[Epic 4G Android Development] Kitteh298:
I would totally buy you a beer if I had a little spare money!!!!

my phone just did one percent in 45 minutes, usually i get 18 minutes per percent, amazing!

ill post back at the end of the day or so, ill be streaming pandora via wifi.
[Epic 4G Android Development] Rodderik:
if you flashed 0.4a then thats what you are running...it just doesnt tell you anywhere...the only way really to know is looking at the kernel build date in say....setcpu or something for now

NICE! I will try to make them even more battery efficient soon with more undervolts!!!

It's all good I understand beer money is hard to come by...let us know how the battery life goes!
[Epic 4G Android Development] durrett syndrome:
set cpu is saying....

kernel

Linux version 2.6.32.9 (teamviper@teamviper-virtualbox) (gcc version 4.4.1 (sourvery g++ lite 2009q3-67) #40 Tue Mar 1 02:53:05 EST 2011

I flashed today so im assuming it isnt .4
[Epic 4G Android Development] Rodderik:
the date there is the build date...the date i compiled the kernel...march 1st sounds right for 0.4a...you should be good to go
[Epic 4G Android Development] MikeyLee:
Where are you guys getting 0.4a from?
[Epic 4G Android Development] Rodderik:
here is my latest unofficial build for you guys to enjoy http://dl.dropbox.com/u/7514207/Genocide0.4a_tetherfix.zip

as of now it has all the changes you can see in the README on github inlcuding wired and wireless fixes by mkasick
[Epic 4G Android Development] tpike:
Github link?
[Epic 4G Android Development] Rodderik:
Yes the link is in the OP

Here are changes anyway since I know people aren't going to look

Changelog: (since 0.3a)

RDNIS Froyo Fix by mkasick (use wired tether from http://xdaforums.com/showthread.php?t=964925)

Wireless Tether fixes by mkasick http://xdaforums.com/showpost.php?p=11808622&postcount=88 (should fix 4G tethering issues)

Keyboard patch by mkasick http://xdaforums.com/showthread.php?p=11755093

Battery Status Polling Interval changed from 2000 to 30000 (30 seconds)

Added RNDIS support for Wired Tether https://github.com/DevinXtreme/Xtreme_Epic_Kernel (tested with easytether lite)

Added CONFIG_ARM_THUMBEE=y (as suggested by gzub)

Set 4k read ahead in mtd_blkdevs.c (faster boot?)

existz-initramfs-i9000-suckerpunch ported to Epic - broken right now

Removed CONFIG_DEBUG_INFO=y (gives us smaller kernel image and all modules including new cifs.ko)

CFLAGS_KERNEL	= -O2 -pipe -mcpu=cortex-a8 -mtune=cortex-a8 -mfloat-abi=soft -mfpu=neon

*Removed About Phone information (Caused FC and weird bugs in apps)

Fixed error that wouldn't let cpu drop below 200MHz

This is still a tester build and not official yet
[Epic 4G Android Development] tpike:
Read that didn't know that referred to this .4 or the previous .4. Thanks for clearing that up for me...and others too I'm sure.
[Epic 4G Android Development] Kitteh298:
ill probably post something tomorrow. Battery didn't hold up too good, was burnign up like 2 minutes per percent when the screen was on. Ill test overnight, then again tomorrow, I've also uninstalled some things..
[Epic 4G Android Development] k0nane:
Just FYI, EasyTether works differently than Wired Tether and doesn't require RNDIS. You may want to try with the official client.
[Epic 4G Android Development] Rodderik:
yes thats why up higher in the changelog is: RDNIS Froyo Fix by mkasick (use wired tether from http://xdaforums.com/showthread.php?t=964925)

i didn't want to take credit for the original work from DevinXtreme

that is just my github change log anyway...the official change log will not have that confusion
[Epic 4G Android Development] gdbassett:
Thanks for the wired tether, the general development support, and the work on CM7. /donated.
[Epic 4G Android Development] dchawk81:
Voltage control on our end would be cool...I think. Although I'd probably end up making things worse since I don't really understand it.
[Epic 4G Android Development] BopChie:
thats why ya dont get it ;)

to little voltage and your gonna be unstable... too much and and your kitty will explode!!
[Epic 4G Android Development] dchawk81:
He said he's considering an app to give it to us. I didn't suggest it myself...

I'm saying I don't know whether I'd want that app.

At any rate, I doubt the app would let us move the voltage higher. I'd guess it would be either native or lower.
[Epic 4G Android Development] BopChie:
OIC lol, pre-coffee posting. :p
[Epic 4G Android Development] dchawk81:
No worries. Haha. :D
[Epic 4G Android Development] Silent25r:
I'm assuming it's going to be much harder than overclocking a computer (cpu, gpu). I've been doing that for almost 10 years. Was much harder back in the day. Still have not broken anything.
[Epic 4G Android Development] Rodderik:
yea if something like voltage control makes it in the kernel then i will be sure to sets some min and max values in a safe range...as well as defaults and recommended voltages
[Epic 4G Android Development] gdbassett:
Testing out wired tether (http://code.google.com/p/android-wired-tether/) and having some issues. When starting wired tether, it initially says kernel doesn't support but on starting it a second time the error doesn't appear.

However, after starting and turning on wired tether, I"ve plugged into a windows XP system (with the rndis driver from here (http://xdaforums.com/showthread.php?t=445436) installed as well as ubuntu system. Neither one picked up another network adapter (which I assume is how the wired tether manifests it's self).

However, if, after plugging in, I choose the "wired tether" button, both systems detected the phone. Unfortunately I received an error that my sprint login/password were incorrect (on the phone). Not that I wanted to use sprints capability (which I understand to not be the same), but it gives a reference point.

Update: I wonder if the sprint capability conflicts with the android-wired-tether in some way? (http://code.google.com/p/android-wired-tether/issues/detail?id=29)
[Epic 4G Android Development] Rodderik:
RDNIS Froyo Fix by mkasick (use wired tether from http://xdaforums.com/showthread.php?t=964925)

try the one from there
[Epic 4G Android Development] mattallica76:
This is an excellent idea, as each phone/chip is unique in that they don't all OC/UV the same. I would suggest though, that any folks running a ROM/setup that has Journaling disabled(Bonsai, ACS) find a way to re-enable Journaling or temporarily switch to a ROM that has Journaling enabled. While your experimenting to find the optimal voltage and frequencies for your phone, chances are you are going to have at least one lockup. With journaling disabled, there's a good chance of data corruption if this happens. On an RFS or ext4 ROM with journaling, you would just reboot and reset your voltages/frequencies, but with no journaling, you will probably have to restore from a known good backup and re-flash your ROM, which is very time consuming. Once you find out what your device can handle, switch back to whatever setup/ROM you prefer.
[Epic 4G Android Development] JudasD:
You are correct about the journaling. I think it is a great idea to have a voltage app, however, there also needs to be a way to enable/disable journaling on demand. Toying with the voltages on a journaling-disabled rom is a sure-fire way to data loss :(

JD
[Epic 4G Android Development] gzub:
There is more than one way to turn journalling on and off, the format way (like most roms do now) and the tune2fs way. The tune2fs way could probably be scripted to be done in CWM and would allow for turning it on and off.

The one negative to the tune2fs way is that it leaves some extra structures around from the journalling, but it does turn it off if you don't mind it being perfectly clean (I do not think it has a performance impact, just some extra space that is reserved and not used).

Geoff
[Epic 4G Android Development] gdbassett:
tried with the tweaked wifi tether. While it didn't work on the windows computer (unknown usb device even with the samsung drivers), it worked on the ubuntu system. As the ubuntu system is up-to-date and the windows system is xp sp3, I'll blame windows. Thanks for that extra little help.
[Epic 4G Android Development] Rodderik:
you are correct...although rfs does not have the same type of journaling as ext4 but the whole concept of re-enabling journaling while you will be purposely crashing your phone is a novel idea!

lots more factors could contribute to data loss but journaling would be one of the big ones

just my personal experience (flame at will) but turning off journaling doesn't give that much of a boost in performance versus the % of dataloss that could occur...just my 2 cents take it for what its worth
[Epic 4G Android Development] musclehead84:
I found.out that.if you restore from a nand backup on bonsai (I'm sure acs is the same) then journaling becomes enabled. You have to flash the rom again to disable journaling. I wish someone could make a flashable no mod journal. It sucks restoring from a backup on acs and if you want journaling disabled you have to.flash the.rom again and lose all your data.

Sent From My Evo Killer!
[Epic 4G Android Development] Toast95135:
I flashed .3 from Twilight (yes I wiped cache partition and dalvik) and it broke root... I flashed back to .1 and it was still broken. I tried to wipe back to stock and it showed the dual boot anis and then started vibrating and wouldn't boot. I'm restoring an older nandroid backup right now. Hopefully I won't have to ODIN back to EB13 and start over again. I'm on the deodexed stock EB13 rom, RFS, with the Gingerbread theme.

edit: the restore worked and I didnt have to ODIN.
[Epic 4G Android Development] k0nane:
Twilight Zone features kernel-based root. Rodderik has opted not to go that route. Make sure you've got su and Superuser.apk on your device.
[Epic 4G Android Development] TheDub:
I agree with you Rodderik... turning off Journaling is a big mistake.. I've had a few lock ups and I reliably lose data.
[Epic 4G Android Development] Toast95135:
I had su and the superuser.apk. before I went back to Genocide, and even though it was saying I didn't have root the apk was still there. I dunno if its related but after I restored I tried wiping to start over but the deodexed rom wouldn't flash right and would cause it not to boot. I tried restoring again and it would flash Samsung and then stay on a black screen with the buttons lit. I tried doing a complete factory wipe and it did the same thing. I ended up having to Odin. I haven't had much luck with the newer versions of Genocide though, .2 would cause black screens. I never had many problems before but maybe something just wasn't kosher with how my phone was set up.
[Epic 4G Android Development] Rodderik:
...Yet...I will bump up my time table for this to eliminate as many conflicts as I can for users switching between Genocide and Twilight Zone kernels :)
[Epic 4G Android Development] k0nane:
Good idea. :) Now to make sure the other ROM devs get rid of their superfluous binaries... ;)
[Epic 4G Android Development] JudasD:
I understand what you mean about the tune2fs way. I tried fiddling with that and did not like the outcome.

I also did a format of my data and then a data restore and using tune2fs to view the partition attributes still showed that i had journaling disabled. I have not been able to get it re-enabled.

JD
[Epic 4G Android Development] odub303:
Anyone using this on Syndicate Frozen 1.0? I like the Rom, but the kernel has memory management issues (not saying this is a global problem, but it is for my setup) that I did not have when I was running this kernel on stock eb13.