I have an epic 4g rooted running froyo 2.2 dk28 with VIPERrom Frozen 4.0.3.
How can I speed this up. Im only getting high 9's in Quadrant, but I was getting that on stock 2.1 DI18...how can I get that up to over 2000? Also how can I change the bootup animations?..I checked in viper store and downloaded one and flashed it but it still doesn't appear.. also how can I overclock it? Also my internet is always going in and out for no reason. I've also noticed that it's not as responsive and snappy, did i do something wrong? With this rom do I have to worry about lagfix and gps lock?
Related
Hey all, this isn't a major issue, but whenever I reboot my EVO, the 4G radio turns on. Since I'm, running SwtchPro, I see it and never leave it on too long, but it is a bit irksome. I originally thought it was the ROM when I was running Fresh 3.1, but last night I switched to Baked Snack 1.3 and I still have the same problem. I never use 4G normally so it's off at shutdown, but it turns on at every boot. Anyone have a similar problem or know a fix? I have the latest Radios as of 2.2's release...
PSULightingGuy said:
Hey all, this isn't a major issue, but whenever I reboot my EVO, the 4G radio turns on. Since I'm, running SwtchPro, I see it and never leave it on too long, but it is a bit irksome. I originally thought it was the ROM when I was running Fresh 3.1, but last night I switched to Baked Snack 1.3 and I still have the same problem. I never use 4G normally so it's off at shutdown, but it turns on at every boot. Anyone have a similar problem or know a fix? I have the latest Radios as of 2.2's release...
Click to expand...
Click to collapse
I have the same issue if I use launcher pro or adw, the 4g toggle seems the culprit for me. I made a shortcut to the wireless and network tab and turn it on from there, it is an extra step but it works.
Bump... Still having this problem. Currently on Baked Snack 1.3 (1.4 later today) running Netarchy Kernel, ADW Launcher, SwitchPro widget. Every reboot, I see the 4G toggle come on...
This could be a kernel/rom combination issue but I have noticed lately that my touchscreen starts acting up. I was running Myns rom with Nets kernel and decided to give SBC a try. Wiped, flashed, booted and everything thing appeared fine but once I unlocked the screen, it became unresponsive and actually started opening icons on my homescreen that I wasnt even trying to press. Now its possible its hardware issue (i hope not) but it seems to only do it on certain occasions. Wondering if anyone else has experienced this.
Thanks.
are you on rsl4 myn? or the rsl5 beta ( for the rom? )
I have tired both Ms79737 and netarchys kernels with out issues. Also what is your PRI? and what versiion ROM are you on? a 1.90 PRI can cause issues ( like lag that can affect the screen ) with a 3.30 rom. 3.30 roms need the 1.77 PRI. 1.90 PRI needed a 3.70 rom.
mroneeyedboh said:
are you on rsl4 myn? or the rsl5 beta ( for the rom? )
I have tired both Ms79737 and netarchys kernels with out issues. Also what is your PRI? and what versiion ROM are you on? a 1.90 PRI can cause issues ( like lag that can affect the screen ) with a 3.30 rom. 3.30 roms need the 1.77 PRI. 1.90 PRI needed a 3.70 rom.
Click to expand...
Click to collapse
Running PRI 1.77 and Myns RSL4. I sure hope it isnt my phone. Im gonna try flashing back to Nets kernel and see if the issue goes away.
Its really strange. I can sometimes fix the issue by turning the screen off and back on.
One thing could be a too aggressive HAVS kernel. Which one were you running?
I experience it occasionally, when I swype it leaves jagged lines too, a reboot fixes it
mroneeyedboh said:
One thing could be a too aggressive HAVS kernel. Which one were you running?
Click to expand...
Click to collapse
Yeah, I was running the more aggressive version. I'll try the less aggressive and see what happens. It's definitely a kernel issue cause I have been running the Rom as stock and have not had an issue.
Sent from my PC36100 using XDA App
Flashed the less aggressive havs. Seems to be working just fine. Ill keep testing and let you know if it happens again. Otherwise Ill just keep using the less havs kernels. Thanks again guys.
i was running Froyo on my epic for the longest time and i used odin to go back to 2.1 just recently because i missed how smooth it was. i noticed that no matter what i do, my notification light won't work anymore. even when the screens off. im running stock DI18 right now (unrooted) and i have no idea why it hasnt worked. any ideas? they would be greatly appreciated.
sniperwitagun said:
i was running Froyo on my epic for the longest time and i used odin to go back to 2.1 just recently because i missed how smooth it was. i noticed that no matter what i do, my notification light won't work anymore. even when the screens off. im running stock DI18 right now (unrooted) and i have no idea why it hasnt worked. any ideas? they would be greatly appreciated.
Click to expand...
Click to collapse
Weird, why not run Bonsai, midNIGHT or Viper 2.2 ROMs?
I have been using midNight for about 3 months (since I got my epic for xmas) and it is VERY fast with no lagginess what so ever
Mine didn't work on 2.1 either.
Sent from my Evo Killer!!!
does it work if you odin back to dk28?
try it first and see what happens
musclehead84 said:
Mine didn't work on 2.1 either.
Sent from my Evo Killer!!!
Click to expand...
Click to collapse
Mine has worked on 2.1 stock, 2.1 epic experience, 2.1 noobnls rom and other 2.1 roms ive tried as well as now running bonsai..
i was running bonsai. i switch roms every day until i find one i like. ive run almost all of the dk28 roms at this point. i was running viper with the gingerbread theme with ext4 and i really liked that setup. but the notification led let me stealthily text at work or school so really miss it. i re-rooted my epic and put the latest epic experience for eclair back on my phone and ran phoenix kernel but for some reason the newer builds of that for me make my touchscreen unresponsive whenever it feels like it, so i went back to fluff kernel. however, the notification light still doesnt work. ive tried wiping the phone, using odin to go back to stock, ive tried third party notification led programs, tried playing with the stock settings, installing handcent again and playing with those led settings, and just about everything else i can think of. im thinking there must be something i can run in the terminal emu to make it reset or something. im a pretty avid linux user, but im no expert when it comes to android so this is something slightly out of my expertize. but from googling and browsing xda somewhat, its a growing problem. most people dont care enough to fix it though and like 75% of xda members with epics moved to froyo anyway.
Ive experienced this on both Myns 2.2 and Vael Paks ROM. Where theres an instance of my phone slowing down with 4G, turn it off, and BAM, everything snappy again. Why is this and how can I fix it?
dw3bb10 said:
Ive experienced this on both Myns 2.2 and Vael Paks ROM. Where theres an instance of my phone slowing down with 4G, turn it off, and BAM, everything snappy again. Why is this and how can I fix it?
Click to expand...
Click to collapse
I've never experienced that before, and my 4G is constantly on. Have you tried using a different kernel? What about wiping cache and dalvik cache? Does this happen every time you use 4g?
I've seen this too. Major lag with 4g on sometimes
-mark
dw3bb10 said:
Ive experienced this on both Myns 2.2 and Vael Paks ROM. Where theres an instance of my phone slowing down with 4G, turn it off, and BAM, everything snappy again. Why is this and how can I fix it?
Click to expand...
Click to collapse
When I initially purchased my EVO, I experienced a lag when initiating 4G, but heck, that has long since been corrected. I use 4G often and there is no lag whatsoever and I, too, am running Warm TwoPointTwo RLS5 so I can safely tell you that it is NOT the rom. Have you tried updating your profile? (Menu-Settings-System Updates-update profile)
Posting & replying via the XDA Premium app
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Haven't had any issues gonna try the latest stable build of cm7 I always use amon 2.3 for a full wipe a lot of the time that fixes issues for people .
ginjeet said:
I am having pretty much the same issues on my evo. Tried just about the same tweaks to try to rectify them. Right now I'm going to under clock and see if it helps. I noticed a lot more things residing in memory after a restart than usual, including fota kill which is a cm product. All I think I can do now is fire up catlog and see if anything is obvious. I'm no genius so likely I'll just send it in and hope for the best. I was almost sure my hardware was failing, but now not so much.
Click to expand...
Click to collapse
Well, n66 after a day on tiamets 4.0.1 kernel seems stable. Let me know how the undervolting goes. I tried vipers v2 and it started freezing after about 20 minutes. The -50 script did the same thing. -25 actually worked out pretty well right up until this morning. My alarm went off and I hit snooze and it threw it into constant reboot.
I'm going to run just n66 with 4.0.1 all day no script and see what I get. I dunno what has changed for my phone but it seems to have leveled out. *knocks on wood*
Sent from my PC36100 using XDA Premium App
So far on the 7.0.3.1 build GPS works like a champ market mms and everything camera and such you tube app plays everything on hq. Picky at time at times tho on HQ.
blizzard1017 said:
Way back in the 30's I was getting fantastic results with CM7 and tiamets kernel. I recently wanted to go back to it until the Sense 2.1 guys ironed out a few more bugs for me to comfortably daily drive them. I installed n63....had issues 7.0.3.1.... had issues.... n65.... had issues.
By issues I mean random restarts, force closes, 3g won't stick, overall signal for 1x was horrible, no amount of gps fixing would keep my gps locked in or lock better than 20 meters and mms won't work.
I tried stock kernel, tiamets, SZ ect.... clean install, clean wipe, reinstall apps from market vs restore from TB. Tried the mms fix, gps status app, msl reset trick, you name it I have tried it. My phone does not like CM7 right now at all. It's like feeding a baby strained carrots.
I was just curious if anyone else is having similar "no amount of tweaking will fix it" issues. I had to go back to Konis just for some sanity after 3days of this. I know all these Roms that are not based on actual Evo source are experimental but can a guy get some CM love?! lol
Click to expand...
Click to collapse
Are you u using amon 2.3
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Update* just received an mms with 7.0.3.1 and it worked
A1Lonestar said:
Cm7 is running great for me. Used nightly 65 for a week with no problems. Flashed 7.0.3.1 2 days ago and it is running like a champ with sz 2.1.0 cfs. Did GPS fix back on nightly 30 something and it has been fine ever since. Maybe you just made your phone mad and its retaliating lol. I do have the receive mms problem though . Tried multiple fixes for it with no luck.
Click to expand...
Click to collapse
What recovery are you using man? Anything better using nightly 66 advantage wise?
reaper24 said:
What recovery are you using man? Anything better using nightly 66 advantage wise?
Click to expand...
Click to collapse
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
teh roxxorz said:
Well 66 plays nicely, but I think the mms bug where you can't receive, but using 3.3.7/4.0.1 with bsm v2 and it plays nicely.
Click to expand...
Click to collapse
Well, I just went back to Koni's..............again. I was running 66 all morning with 4.0.1 and no script and while everything was working ok the battery was draining somewhat fast. It wasn't a wake issue and I even tested an hour or so on PRI177 with the same results. The battery was tolerable because Mondays are really busy for me so I know on a normal day I wouldn't complain but my data connection still drops to 1x a lot and I think the drain might have something to do with the connection searching constantly.
If I can get that Viper script moving along and figure out the data and signal drop I think I am getting somewhere.
@reaper, yes I am using Amon Ra latest and greatest.
Off topic, I love the Nand backup option. My Vibrant only uses Clockwork and even then it was not fully functional. Some of the basic options would brick the phone.
The latest cm7 stable works great.
Sent from my PC36100 using XDA App
flashing back to sense after "GPS FIX"
I have a few issues with CM7 and I keep switching back to Sense roms because they have been stable. If I do the GPS fix and stay on CM7 will my GPS still work when and if I go back to a Sense ROM?