Develop Bugs

[Q] 4G Starts at Boot, any fix?

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...

[Q] Laggin, Freezing, and Making me mad!

Ok, I'm finally reporting this Uber annoying problem.
My phone will just lock up for anywhere between 2 and 15 seconds. I thought this was maybe a bad backup from titanium, so I stopped using it. I cleared my SD card, I've tried multiple roms, I'm formatted everything including SYSTEM during each different ROM install.
It seems the issue happens after I use SMSBACKUP+ to restore my txt messages. *EDIT But I've had it happen without installing SMSBACKUP+ EDIT* Handcent has been force closing on me for weeks as well. I just removed Handcent, and installed ChompSMS. The problem is still happening.
It happens very randomly, and without any cause that I can tell. I'll hit the power button, and unlock the screen, and then the touchscreen is completely unresponsive for seconds at a time. The touch buttons (home,back,etc) are also unresponsive. Then all the sudden, the phone will try to catch up to every one of my touchs.
Also, whatever it is is killing my battery. Yesterday I installed MikFroyo, and the phone was good for over 12-15 hours. Then I charged it, and something in the past 2 hours caused the issue and completely drained my battery in those 2 hours.
I've had this problem with
FreshEVO (multiple versions)
SprintLovers
Burnt Droid (multiple versions)
Ava-Froyo
OMJ's EVO
BakedSnack
I've also tried ASOP mods like MIUI and Cyanongen Mod, and as far as I can remember, the problem didn't happen with them, but I really would like to have my 4g work.
I just want my phone back!!!!

Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.

First backup your apps and data. Then flash calkulins format all, then flash your rom and start from there it should work
Sent from my PC36100 using XDA App

I've been using calkulins format all for the past 2 weeks (7 flashs)

teh roxxorz said:
Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.
Click to expand...
Click to collapse
I've used every kernel I could get my hands on, thinking it was the problem. I've been using stock kernels for the past 2 months now with the same problems.
I just haven't heard anything else bad about SMSBACKUP+, but I have read some issues with locking up, freezing etc regarding SMS in general.

Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App

davidc23 said:
Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Been there, done that about 50 times too. I'm just gonna go without HandCent for a few days and a new ROM install and see what happens.
Have you had any other complaints about this?

None, what's your hardware version
Sent from my PC36100 using XDA App

davidc23 said:
None, what's your hardware version
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Current
HW: 0003
MikFroYo 4.5
2.6.32-17-gee557fd [email protected] #15
3.70.651.1

Are u using setcpu
Sent from my PC36100 using XDA App

Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
EDIT: Also, what PRI version and Radio/baseband version do you currently have? The latest? 1.90 PRI and 2.15.00.11.19? If you are on the 1.90 PRI, try downgrading it to the 1.77. The 1.90 PRI is definitely known to cause issues that you speak of on some phones. Just anothing thing to double check. Here is an attatchment of the 1.77 PRI. It sounds like you don't have anything to lose by trying. Everyone's phone acts differently with different software and what not.

davidc23 said:
Are u using setcpu
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nope... Complete stock roms, with little to no apps. I can only think to point at bad hardware, the base sms operation, smsbackup+, handcent, or titanium backup. All of which I'd had issues without one or the other installed.

k2buckley said:
Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
Click to expand...
Click to collapse
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.

4g still scans
Sent from my PC36100 using XDA App

mintee said:
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.
Click to expand...
Click to collapse
Check the Edit in my previous post as well

k2buckley said:
Check the Edit in my previous post as well
Click to expand...
Click to collapse
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.

mintee said:
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.
Click to expand...
Click to collapse
Dang!! That's an old radio / pri combo! I've never rolled back that far, so can't say much about it, but are you sure that's not contributing to the issue? Maybe it doesn't like the 3.70 build.
Sent from my PC36100 using XDA App

Notification LED not working?

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.

[Q] 4g turned on at reboot

OK, I found some other threads, and they have said to reload the rom, and go through the apps that were installed previously to see what is causing the issue. I've done that and I've gotten all my apps installed no issues for the last 1-2 weeks. My phone went dead and i rebooted now the 4g is turned on by default again. I rebooted again after turning off 4g and it is turned by default again. Is there a settings or some config file that I can change to prevent this from happening.
HW Ver: 3
Sw Ver: 3.70.651.1
ROM: Calkulin's EVio 2 v1.8
Kernal: HTC #15
PRI: 1.77_003

Some applications may affect it. Last time I installed call blocker and 2 other apps (don't remember which 2 right now) and 4G start power up on restarts. I just restore my nandroid backup and that is how I got rid of it. After that I installed call blocker itself and everything is fine.

Did some testing... at end just tried to enable and disable 4G. After that 4G start automaticly on phone restart. So its not any app, it is calkulin rom itself... once you start 4G no metter if you disable, on every next restart will start by itself. Hope fix is coming soon because I hate this, and I dont want to change rom.
Sent from my PC36100 using XDA App

erik077 said:
Did some testing... at end just tried to enable and disable 4G. After that 4G start automaticly on phone restart. So its not any app, it is calkulin rom itself... once you start 4G no metter if you disable, on every next restart will start by itself. Hope fix is coming soon because I hate this, and I dont want to change rom.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This also seems to happen to me. Im running Myn's Warm TwoPointTwo RLS5. I just turn off the 4g. And it doesnt do it all of the time, sometimes when it reboots, 4g will be active, then turn itself off and revert to 3g like it should.

When this happened to me I found out it was due to the notification bar widget controls

This happened to me on a stock Evo, not rooted. I took it to Sprint & they couldn't figure it out. Later, my 4g went out altogether, even without rooting the device. I still don't know why, but they gave me a new one.

CM9 on Epic 4g Touch CONSTANT restarts!

I just recently installed CM9 alpha 6 on my Epic 4g Touch but ever since my phone restarts so much! Its just super buggy and it acts as if im holding down the power button showing the options for Reboot, Airplane mode, etc. After that it restarts. It will does this almost constantly to the point where the phone is barely usable. Anyone experience similar issues? Any suggestions?

Using it the last few days w zero issues. Which one are you using and how did you flash?
Sent from my SPH-D710 using xda app-developers app

I just installed it myself yesterday, but all has been good. I haven't had any of those problems. You probably should download it again and flash it again.

kdubhotsauce said:
I just recently installed CM9 alpha 6 on my Epic 4g Touch but ever since my phone restarts so much! Its just super buggy and it acts as if im holding down the power button showing the options for Reboot, Airplane mode, etc. After that it restarts. It will does this almost constantly to the point where the phone is barely usable. Anyone experience similar issues? Any suggestions?
Click to expand...
Click to collapse
Really stupid question, but did you use "Calkulin's_FORMAT_ALL_for_E4GT" zip file before flashing CM9? I only ask because I have had issues in the past with other roms by forgetting to wipe everything beforehand. Even the savvy tech could forget something sometimes :silly:

I'm running the exact same ROM. I underclocked mine down to 800Mhz to save battery and it was causing constant restarts. I moved it up to 1000Mhz and they stopped. If you tried messing with the clock speeds that might have caused it

OP, did you fix your problem or did it just go away? I recently flashed mine to cm9 alpha 6 and am having the exact same problem. Never has this phone had problems before.