yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] zman519:
@Rodderik

Last Saturday or firday I was doing some tests with weird tether & genocide 2.0 I had rebooted many times. Then staruday night when I was out my phone totaly started to freckout. Voice calls would not have any sound all kinda stuff. I had to restore a nandroid from b4 I was testing wired tether The reason I tested in the first place was that dave said on srf1.2 wired tether said "unsuported kernel" and just so you know on my phone midnight 5.2 with 2.0 kernel it never gave any error. Idk if that helps or any thing.

Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
[Epic 4G Android Development] Grommish:
YES Please! Pershoot is trying, but....
[Epic 4G Android Development] CapsLockKey:
Did you install the Epic drivers from Samsung's website? I had to do that before it would work on one of my computers.

I should probably point out that I'm running stock froyo with Genocide 2.0.
[Epic 4G Android Development] Shoulon:
Wireless tether don't work? I'm on srf 1.2 it just reboots my phone (yes I changed settings to epic 4g)
[Epic 4G Android Development] Rodderik:
wireless tether should work perfectly...uninstall it and reinstall from the market
[Epic 4G Android Development] darren.wlsn1:
just did a little testing and im on srf 1.2 and wifi pre9/12/14 work fine as well as wired.
[Epic 4G Android Development] JohnCorleone:
Pre 14 is great for me as well
[Epic 4G Android Development] styles420:
If you're referring to the usb tethering issue, take a look at the one included in SRF 1.2 - it works fine, I used it to connect my laptop using 4g for several hours two days ago (thereby connecting the wireless router, which provides a connection to an xbox, a ps3, there other phones and two other computers). No lag, not even with two players on Black Ops ;)
[Epic 4G Android Development] mjben:
My success has been spotty with both wired and wireless tethers.

Getting wired tether to work took multiple restarts of both my phone and PC. Then after passing about 26mb of data it just broke and stopped working.

I really only got wireless to work once; a friend was able to jump on with his optimus. Otherwise, I've seen it connect but no data would transfer.

Neither one has worked perfectly, the trick is to keep trying, but expect it to fail. I find the tethers to be rather unreliable. More of a novelty, really.

Sent from a secret underground bunker
[Epic 4G Android Development] Shoulon:
I had to install the latest beta from the google project link. But it works =) I had hotspot running for 5hrs with 4 devices. Was awesome =)
[Epic 4G Android Development] zman519:
Yes i have the drivers installed i was using wired tether way back on DI18, All though i have not had a lot of use for it the last mouth or so.
[Epic 4G Android Development] pvtjoker42:
So, curiously I've run into a problem. It's a combination of Bonsai rom and Genocide kernel. Seems to break something with root and busybox. Mainly Titanium backup stops working and won't find root. superuser still runs, but doesn't prompt for any apps to allow root. Not sure what the cause is. Not an issue with SRF 1.2, just seems to be a Bonsai issue. (4.1.1 and 4.1.3) Don't know if anyone else has run into a similar issue. Tried both Genocide 1.1 and 2.0, same issue. Tried from clean install as well as upgrades. Even manually installed busybox from the market, and no go.
[Epic 4G Android Development] Razor1973:
I'm on the same boat here with the newest Bonsai 4.1.3. I installed the ROM first and then the Genocide kernel and lost root. In case it makes a difference, I flashed the kernel with Bonsai recovery.
[Epic 4G Android Development] thomasskull666:
This is the problem with mixing open community software with closed community software: we don't know what they're doing. My guess is they decided to put root in the ROM and then using Genocide messes that up. If Genocide messes it up, then all the other XDA kernels will too just because Rodderik and I are using DRockstar's method of adding root to the kernel. Try DRockstar's Clean EC05 Kernel and see if it does the same thing. If so, you may have to manually remove whatever root setup Bonsai has put in their ROM.
[Epic 4G Android Development] Rodderik:
agreed...our kernels have a self contained root so i'm 99% positive any kernel using our method like Clean Kernel will fail in the same manner. i don't know what bonsai has done to our normal root method without downloading it and poking around.
[Epic 4G Android Development] Razor1973:
Understood, guys. Thank you. They must have changed this in 4.1.3, since there are reports in this same thread of Genocide working fine with Bonsai 4.1.1 (4.1.2 did not exist or was very short-lived).
[Epic 4G Android Development] duce102:
Hey Rodderik or Thomasskull,

can either of you confirm if this is just a prank(modding scores etc.) or if its genuinely OCing

http://xdaforums.com/showthread.php?t=1178436
[Epic 4G Android Development] Djinn23:
I have been trying to isolate a battery drain. I was running gen 1.1 and srf 1.2 with stellar life. I don't know it it was 2.0 or the google plus stuff but something is toasting my battery.

In reading up I installed osmonitor and found the sensor and android system are always using cpu? I was hoping someone could tell me if this is normal. Also the system process (0) is chewing network issues. As well as some other pid I cannot find using ps in connectbot here are some screenshots but I was wondering if similiar has been seen with others?

Well actually the xda app is saying the shootme captures are not a valid format...so they will have to wait.

Thanks in advanced
[Epic 4G Android Development] Rodderik:
the network 0 process is something i havent tracked down yet...i know g+ by default is set to be pretty battery hungry...i would take that app out of the equation when trying to figure out what the battery drain is...the kernel itself didn't change much from 1.1 to 2.0 (only 3 changes really)
[Epic 4G Android Development] jeffro18:
Use the compressed pic, I get the same issue when trying to post full size pics with the app.
[Epic 4G Android Development] Djinn23:
Thanks
[Epic 4G Android Development] BrianDigital:
I flashed to my girls epic and in voodoo control the color options are not showing up odd
[Epic 4G Android Development] zman519:
Ya I was thinking the same thing? But never asked about it

Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
[Epic 4G Android Development] adamw1101:
When I try to change my display options in contacts it says scan sim card and does not allow me to alter display options
[Epic 4G Android Development] xopher.hunter:
Awesome kernel I was just wondering if you have tried overclocking the gpu, I saw this galaxy s kernel with it implemented, here's the link http://cidalan.blogspot.com/2011/07/kernel-list-galaxy-s-i9000-custom.html?m=1
[Epic 4G Android Development] thomasskull666:
Voodoo control doesn't have the color options, maybe at some point it will but as of current supercurio hasn't made it adjustable. Just turn the brightness all the way up and you'll notice.
[Epic 4G Android Development] tpike:
That sounds pretty hot. I imagine it would be valuable to see some documentation on our gpu.
[Epic 4G Android Development] zman519:
Do you remember this Kernel MixUP-20101024-847 It had Vodoo color & i'v never seen a Kernel that would go as low in brightness as Mixup did. It was grate at night in bed with the GF (or Wife)
[Epic 4G Android Development] BrianDigital:
Its adjustable on my nexus s though
[Epic 4G Android Development] thomasskull666:
Ya I've been trying so hard to get that back, unfortunately geniusdog254 doesn't do Epic work anymore :-( and to top it off the screen driver code changed from Eclair to Froyo so that same fix won't apply anymore. Doesn't mean I'll stop trying lol, I should ask supercurio sometime I'm sure he'll know.
[Epic 4G Android Development] xopher.hunter:
Screen filter (market app) not doing it for you?
[Epic 4G Android Development] thomasskull666:
Ya Screen Filter is a great app, but how sick would it be to have a third brightness level lower than the lowest?
[Epic 4G Android Development] Rodderik:
overclocking the gpu is neat and all but there really isn't a point for the extra battery usage when we have a fps cap in place...and that fps cap will remain in place until we get some proper documentation on the lcd so we don't cause any damage to people's phones
[Epic 4G Android Development] motog35:
Wow, I'm getting HORRIBLE battery life with this Kernel, running SRF 1.2.

No Overclock. No idea why. Use to get amazing battery life with SRF 1.2 and stock kernel.
[Epic 4G Android Development] hayzooos:
SRF 1.2 didn't have a stock kernel, didn't come with one. What were you using before you flahed it? My assumption is TwilightZone 1.1.1, but if you could confirm, that would be great.
[Epic 4G Android Development] Rodderik:
try flashing the kernel again and see what all is using your battery...most people report excellent battery life with the kernel...i just went 2 days with normal usage
[Epic 4G Android Development] motog35:
Typo, I was using Twilight that came with stock SRF 1.1
[Epic 4G Android Development] mouseglider:
I can't find this answer, I sometimes use ooVoo to webcam with my wife who is deployed, and has worked in the past.

I just tried to use it again and my front camera doesn't work when using ooVoo, other than that my phone is perfect - I can see her she obviously can't see me - audio works though.

I am wondering if the Genocide v2.0 breaks or has an incompatibility ooVoo? I do use UV from the OC - but like I said my phone is perfect on my stock EC05 rom with all the fix's and the Genocide kernel - I also UV and OC perfectly for my use with no issues.

I also can't remember what kernel I was using when it did work - although I think it was the stock kernel. If it is your kernel, is there a fix for that? I would hate to give up the performance of your kernel just to get ooVoo working again, as I use it that much.

Thanks!
[Epic 4G Android Development] Rodderik:
it shouldn't break compatibility...are you able to go back to the stock kernel and see if it still works with your current setup?
[Epic 4G Android Development] thomasskull666:
While the kernel does control the driver for the front facing camera (I guess), this kernel shouldn't have anything changed in the code for it. My guess is something in the ROM is conflicting with the app and thus causing the camera to not work, you can try going into the Camera app and switch to the front facing camera to see if you see yourself. That might give you an idea if it works or not and is possibly hardware related.
[Epic 4G Android Development] thomasskull666:
That has to be like the 5th time we've both responded simultaneously lmao
[Epic 4G Android Development] Rodderik:
you're so sexy thomas :D
[Epic 4G Android Development] thomasskull666:
Hahaha

I know :p
[Epic 4G Android Development] mouseglider:
I did a backup of my stock kernel with a program called sgs-kernel-flasher and it saved it in a zip format, but I have never used it - I was hoping it might work in an emergency.

So in answer to your question - I possibly can restore my stock kernel - not sure - but my front camera works as it should in all my other applications.
[Epic 4G Android Development] mouseglider:
Yes, my front camera works in all my other programs as normal - also I am on a stock rom - the only thing I have done is applied all the fix's which I understand is rom related, ie, camera lag, slow rotation fix, call log fix etc., and change the kernel and UV'd and OC'd.

Also I probably have not added any "new" programs, only updates to exsiting programs (around 130 of 3rd party) and everything truely works perfect with no glitches except this one - I also have about 205mbs of free internal memory, so I don't think that is the problem.
[Epic 4G Android Development] thomasskull666:
I would say go ahead and contact the app developer, see if he has any suggestions because if it works in other apps but not that one, it may be a bug that came with an update or something. If you have access to it, try a previous version.
[Epic 4G Android Development] Deejaydark:
wtf

My mic works when it wants...it only happened after I installed this.. help plz.... on my epic
[Epic 4G Android Development] zman519:
What rom are you on. You need to give us a little more info for anyone to really help you ;-)

Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
[Epic 4G Android Development] tpike:
In addition to the previous posters question, have you toyed with the voodoo settings through voodoo controller? There are some recording settings that[might help.QUOTE=Deejaydark;16055299]My mic works when it wants...it only happened after I installed this.. help plz.... on my epic[/QUOTE]
[Epic 4G Android Development] mouseglider:
Luckily I always keep a backup of the last 3 versions of all my software, so I tried my previous version and sure enough that solved the problem - I am glad it was the Official ooVoo that caused the problem and not the kernel.

So Beta ooVoo works as it should and Official ooVoo which is 3 times the file size did not work - it goes to show that some updates just plain seem to fail. :(

Thanks for your thoughts!
[Epic 4G Android Development] picklerick:
Battery life seems good to me as long as I don't reboot. After a reboot my battery percentage decreases 25-30%. Also does the ondemand governor lock anyone elses phone up?
[Epic 4G Android Development] Shoulon:
use conservative. you'll be happier. Also as for the battery, stop using "calibrate." it takes about couple days for battery status to be accurate AFTER calibrating.
[Epic 4G Android Development] JohnCorleone:
Are you using Voltage Control? If so, did you take yesterday's update for it? It didn't work right for me after the update. I was overclocked to 1.4 and phone got slow and benchmarked as if it was stock. I restored nandroid and skipped that update.
[Epic 4G Android Development] Rodderik:
or use voltage control in the OP like i've said a billion times
[Epic 4G Android Development] Rodderik:
conservative is the only gov that scales correctly so it is possible that could be the cause of the lock up....and battery dropping that much is typical when you reboot and im not sure why but it almost always happen for most every one
[Epic 4G Android Development] JohnCorleone:
I didn't word that right. Use the one in the OP, don't update it. My bad Rodderik
[Epic 4G Android Development] picklerick:
It seems to lock up when the screen goes off. It wont wake back up when in ondemand and I must pull the battery.
[Epic 4G Android Development] hayzooos:
For VC in the OP, I didn't see anything to set a minimum setting. Maybe I missed it? I took the update JC mentioned by accident, and it didn't play well with my phone either. I went back to the VC I got in SRF 1.2, which works with my phone quite well.

After the update, I deleted it and put on the VC in the OP, but didn't see anywhere to set a min, only a max.

As for locking up, that's because you're one of the unfortunate souls and your phone doesn't like 100mhz. If you can find where to set a min, set it to 200mhz, and use conservative as that will actually adhere to the min you set, where as ondemand does not.
[Epic 4G Android Development] greatlakesghost:
There is a pullup bar in vc where you check the frequencies you want to use. If you make any changes make sure to hit menu then apply changes.
[Epic 4G Android Development] picklerick:
When the phone was locking up I had 100mhz enabled with the minimum set to 200mhz. If I disable 100mhz will ondemand then not drop below 200mhz?

for example:

echo "0 0 1 1 1 1 1 1 1 0" > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

I though it was disabled by default as the OP states or does the ondemand governor not adhere to /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq?

Also the conservative governor will not go above 1000mhz for some reason even though the max_freq is set to 1200mhz. If I change the governor to interactive or ondemand it will then go past 1000mhz.
[Epic 4G Android Development] kvan1707:
I had that problem where it wouldn't run over 1Ghz, it happens everytime I flash a new rom or kernel. To fix it I set my Max to whatever I wanted with voltage control, left the undervolt settings alone, and set the settings as the boot settings and rebooted the phone. When it booted up... everything was where I set it and CPU spy showed the new frequencies being used.

sent from my Evo Killer with Genocide
[Epic 4G Android Development] thomasskull666:
Ya Samsung shafted us with horrible governor code, conservative is the only one that does actually adhere to scaling_min_freq, although I believe nubecoder managed to fix that if I remember correctly. Pretty sure the fixed code is in here, not sure why it isn't working for you.
[Epic 4G Android Development] Rodderik:
nah the govs aren't working like they are supposed to except for conservative due to some special code samsung put in it that the other lack (for now) but like thomas said nubecoder has been working on fixing them
[Epic 4G Android Development] caaznkid:
hey guys i have a weird problem. my phone only works on the frequencies 1000 1120 and 1400 for some reason....is something corrupt?
[Epic 4G Android Development] Rodderik:
give us some more information as to your setup, programs, etc
[Epic 4G Android Development] caaznkid:
I'm using SRF 1.2, Genocide Kernel, and Voltage Control to overclock. Besides that, nothing really too relevant.

When I put the max freq at 1120 or a number below that it'll work. But say if i I put 1200 or 1300 the max freq will stay at 1120. However, if I put the max freq at 1400, then it does work at 1400. I'm also using CPUSpy to monitor the frequencies my phone is at.

Oh and the EG22 modem, if that matters at all.
[Epic 4G Android Development] Rodderik:
yeah something doesn't sound right...reflash the kernel and double check your voltage control settings
[Epic 4G Android Development] caaznkid:
OK I did that still the same do you think the rom is corrupt?
[Epic 4G Android Development] Art2Fly:
Is it possible to dual boot a GB kernel with the GB intramfs?
[Epic 4G Android Development] Grommish:
What scheduler are you using. It sounds like performance, which *will* keep those clock freqs up near max..
[Epic 4G Android Development] Electrofreak:
I use my phone for audio a lot, and I have to say, the audio is phenomenal. Awesome kernel, thanks!
[Epic 4G Android Development] Rodderik:
it is possible if the initramfs is setup to dual boot...it doesn't require kernel source (just a repack) so yes...it is possible....but you will need to look in the dual boot thread for what needs to be changed
[Epic 4G Android Development] caaznkid:


My problem is not with my phone running at max but that it refuses to run at 1200 or 1300 I'm going to odin back to stock then redo the whole thing and hopefully that'll work.

Edit: Odin to stock, then installed SRF 1.2 and Genocide Kernel...still same problem. I'm going to give up now. Lmao. So weird. Phone only likes to run at 1120 and under and 1400 I guess. It's not a big deal anyway, just kind of bothered me. Thanks for all the help Rodderik.
[Epic 4G Android Development] quickstang:
I'm having a similar issue as well. 1.2 ROM & 2.0 Kernel.

I am ONLY getting 1GHz & there was one point in time I was getting 1.3Ghz. Noticed it awhile back that it was never going past 1Ghz even if set at 1120, 1200, or 1300. I know the phone will do it, because I have seen it at that before.

Tried re-installing 2.0 a minute ago, deleted SetCpu cause that's what I was using. I even had it working with SetCpu. Decided to uninstall, do VC & install CpuSpy. NOTHING. Still shows 1Ghz as max.

I'm as stumped as you are.
[Epic 4G Android Development] JohnCorleone:
I have seen this as well but I am NOT using the Voltage Control that Rodderik says to use. If I run "conservative" I don't go above 1000. If I use "on demand" and set max to 1300, it doesn't get there. 1400 is fine though. Are you using the Voltage Control from the OP of this thread? Its the ONLY ONE Rodderik supports.
[Epic 4G Android Development] quickstang:
Trying the 4.2.0 rc2 from the Market Place, but I can try the 3.0 listed in the thread.

Update....Seems the uninstall of the newer one & install of the link worked out ok. Thanks
[Epic 4G Android Development] Maui4x4:
I love this kernel but the only issue I keep having is after receiving about 5 calls, on the sith my phone will just buzz and lock up requiring battery pull. Have this issue on latest srf roms and 1.1/1.2 genocide, no overclock.
[Epic 4G Android Development] Rodderik:
that sounds like more of a rom issue
[Epic 4G Android Development] thomasskull666:
I was going to say the same thing...
[Epic 4G Android Development] Esteway.619:
I flashed this kernel and now it says I have no root.
[Epic 4G Android Development] thomasskull666:
What ROM are you using? Let me guess: Bonsai.
[Epic 4G Android Development] Maui4x4:
When I use vision 1.1 or latest twilight kernel, the problem doesn't exist. I've done odin wipes n redownloaded the rom to no avail. I really liked voodoo 10 sound... :( maybe I'll just have to try another rom.
[Epic 4G Android Development] mouseglider:
You do mean "kernel" and not rom, correct? I say that because I have been using Genocide v2.0 kernel with voodoo sound v10 and can't recall having that problem, although I am running a stock EC05 "rom".

The only exception is that I don't listen to music that much where the possibility of an incoming call would go to voicemail.
[Epic 4G Android Development] mjben:
How can I update the busybox version? Bb updater off the market isn't doing the job, and I need to put in v 1.18.2 for the v6supercharge script.

Sent from a secret underground bunker
[Epic 4G Android Development] Maui4x4:
I should hace specified better, I've re-downloded SRF roms 1.1 and 1.2 to see if that was the problem but still occurs. Some days it doesn't do it amazingly while other times I will have to pull battery.
[Epic 4G Android Development] Rodderik:
that script requires:

Busybox 1.18.2 OR LOWER - 1.18.3 or newer are VERY much a hassle with errors that should NOT be errors!

the version of busybox compiled in is actually compiled into the recovery binary itself to save about a meg of space in the initramfs and the version is below 1.18.2...its 1.17.something_minimal but it should work. i have not tested the script you are talking about though...have you tried it already?
[Epic 4G Android Development] mjben:
Haven't got it working yet. Seems the bb v I am showing is 1.16.2, which should work. I'm still trouble shooting it. I get a ton of 'no such file' and 'not found' messages.

Sent from a secret underground bunker
[Epic 4G Android Development] Rodderik:
1.16.2 sounds right...pm me a log if you can...i wont be able to try my script myself until monday
[Epic 4G Android Development] ksmullins88:
Rodderik,

would you mind if i based a custom kernel off of this?

all credit goes to you, of course.
[Epic 4G Android Development] Rodderik:
sure thing
[Epic 4G Android Development] ksmullins88:
thanks a lot. i really appreciate it
[Epic 4G Android Development] Esteway.619:
Hahaha yes. But its cool I'm back on gb lol.
[Epic 4G Android Development] caaznkid:
I used "Busybox Installer" off the market. Give it a try?
[Epic 4G Android Development] caaznkid:
I FINALLY FIGURED IT OUT. Man am I stupid lol. In the voltage control app (the latest one) there's three tabs, general, advanced, and about. Go into the advanced and it shows which frequencies that are enabled on your phone. If it is in green then it is enabled and if it is in red it is disabled. My 1200 and 1300 frequencies were disabled...thus that is why my phone could not go past 1120, but could go to 1400. So select which states you want enabled and then apply settings then it should be able to go past 1Ghz. Good luck!