So my Epic is doing someting strange. Whenever I leave my house and any other place where I connect to wifi, my Epic partially crashes. I get the "buzz...buzz, buzz, buzz" which indicates an FC, but my screen goes black and I hear the startup sound and my phone will reset to the home screen within a few seconds. It will continue to do this while I'm out of wifi range, unless I turn off the wifi radio. I can turn the wifi radio back on right after I turn it off and not have a problem. Its like the phone crashes because I move outside wifi coverage. The steps I have taken to solve the issue include:
flashing from EC05 (which I was on) to EF02 - no effect
re-flashing to EC05 - no effect
wiping the phone through CWM and flashing EF02 Plus - no effect
flashing the radio from EC05 to EF02 (no effect), then to EF10 no effect
Currently I am on EF02 stock with the EC05 radio. I've had this Epic for 8 days as my last one I dropped to the ground and that killed it so Sprint gave me this new one, and I do mean NEW ONE because the repair center was out of the refurbished replacements they give for phone repair exchanges. Any advice, tricks, omens, or portents are welcome as I am tired of my Epic crashing.
radugb out
When you say you flashed to EC05, do you mean you Odin'd in a stock EC05 and ran that for awhile? And you still had this issue? Try this thread to get back to stock and see if you still have the issue:
http://forum.xda-developers.com/showthread.php?t=1052813
If anything your phone would just be roaming all the time if it was searching for that and not finding it. I know nothing about tower boosters or how they work sorry.
Sent from my SPH-D700 using XDA Premium App
I've had his replacement Epic for 7 days now. The first evening I brought it back from the Sprint store, no problems. When I left the house the next day I had only driven about 2 blocks from my house before I started getting the Forced Close vibrations/crashes & partial restarts. That was with EC05 stock, no modifications. Since then I have flashed EC05 Plus, EF02, and EF02 Plus, trying each version with each of the EC05, EF02, and EF10 modems. Each time I flashed I went into CWM and wiped the cache 3 times, as well as the cache partition and dalvik cache. There were no problems or errors when flashing (at least none that Odin reported) so I can only assume its a new conflict with something the ROM's don't change/update or this new phone's hardware is faulty.
If it did this right out of the box when you brought it home, it is a bad phone.
Muchas garcias. I figured it was probably a bad phone, just needed confirmation. So if I Odin back to EC05 and use the PIT file to repartition, will that eliminate all evidence that I rooted my phone (or at least any that the repair techs could see)?
radugb said:
Muchas garcias. I figured it was probably a bad phone, just needed confirmation. So if I Odin back to EC05 and use the PIT file to repartition, will that eliminate all evidence that I rooted my phone (or at least any that the repair techs could see)?
Click to expand...
Click to collapse
Wait, did you root and put a custom ROM on your phone? You said the night you got it the issues happened. I was wondering your setup at the time because I have had random issues similar to yours.
Sent from my SPH-D700 using XDA Premium App
No, this problem started with stock EC05. I rooted and flashed custom ROM (EC05+, EF02) in hopes it would correct the problem. But it has not. The night I recieved this replacement the phone did not act up. It was the next day when I drove away from my house that it started to behave weird. The phone was still on EC05 ROM at that time with no rooting.
radugb said:
No, this problem started with stock EC05. I rooted and flashed custom ROM (EC05+, EF02) in hopes it would correct the problem. But it has not. The night I recieved this replacement the phone did not act up. It was the next day when I drove away from my house that it started to behave weird. The phone was still on EC05 ROM at that time with no rooting.
Click to expand...
Click to collapse
Ok, then that does sound like a bad phone. If the phone is doing the multiple vibrate thing, something is wrong. Especially if it does that on stock setup
Sent from my SPH-D700 using XDA Premium App
So then my final question: if I Odin back to EC05 and use the PIT file to repartition, will that eliminate all evidence that I rooted my phone (or at least any that the repair techs could see)?
radugb said:
So then my final question: if I Odin back to EC05 and use the PIT file to repartition, will that eliminate all evidence that I rooted my phone (or at least any that the repair techs could see)?
Click to expand...
Click to collapse
Yes. You will be good to go. Shouldn't even be a question since you just got it.
Related
When ending a call help?
Stock ec05
Sent from snarf
churro7 said:
When ending a call help?
Stock ec05
Sent from snarf
Click to expand...
Click to collapse
You know we're gonna need more info than that...
Texted while driving
like what?
You've been here for a while, I'm surprised you wouldn't know by now...
ROM, Kernel, etc.
lets see i can make calls and receive but as soon as the call ends. well when i end it with the end button it vibes once then few seconds later vibes trice and phone apps FC's. Plus it seems to reset the radio as well. i odined to stock ec05 since SRF hates my phone above 1.02. it may be a problem with something I removed?
rooted stock ec05 stock kernel
A bad ODIN? Sounds like your radio specifically. I would reODIN all of EC05 if not at least the modem to see if that fixes it. You're on stock? No custom ROM? What did you remove?
churro7 said:
lets see i can make calls and receive but as soon as the call ends. well when i end it with the end button it vibes once then few seconds later vibes trice and phone apps FC's. Plus it seems to reset the radio as well. i odined to stock ec05 since SRF hates my phone above 1.02. it may be a problem with something I removed?
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
Get this. One time, during a call, the phone app force closed. But the call still kept going, and the controls still worked. Idk how that happened, but I was glad my call didn't end abruptly.
Sent from my always stock, EC05 Epic 4G
i removed too much to remember haha but stock odin didnt work
i just odind to di18 then ota to ec05
no it is only stock
Its funny battery life and sensor usage usage much better than srf
Sent from Snarf phone
So I've had this issue for a long time now where my 3g radio will reset randomly (i think). What happens is that i lose 3g and the icon will disappear from the top bar. The phone makes a small sound (sounds like when you first power up the phone and it connects to the cell tower / 3g). Then about one second later it makes the same noise and then 3g turns back on. It takes it a few seconds to regain signal and then its usually fine. I know its the 3g because the problem stop when data is turned off, and also when wifi is on.
I've tried reflashing roms, reflashing my modem via odin, and even a factory reset. I can't seem to get this issue to go away. The only thing i can think of how i may have caused this issue was when upgrading to EC05 i forgot to include the pit file one time when flashing the modem with odin.
Any input or ideas would be greatly appreciated. I'm still learning when it comes to android so if I haven't tried it yet its because I either don't know about it or don't know how.
Running Syndicate rom frozen EC05
xm1337 said:
So I've had this issue for a long time now where my 3g radio will reset randomly (i think). What happens is that i lose 3g and the icon will disappear from the top bar. The phone makes a small sound (sounds like when you first power up the phone and it connects to the cell tower / 3g). Then about one second later it makes the same noise and then 3g turns back on. It takes it a few seconds to regain signal and then its usually fine. I know its the 3g because the problem stop when data is turned off, and also when wifi is on.
I've tried reflashing roms, reflashing my modem via odin, and even a factory reset. I can't seem to get this issue to go away. The only thing i can think of how i may have caused this issue was when upgrading to EC05 i forgot to include the pit file one time when flashing the modem.
Any input or ideas would be greatly appreciated. I'm still learning when it comes to android so if I haven't tried it yet its because I either don't know about it or don't know how.
Click to expand...
Click to collapse
It may be a Sprint issue...happened to me last week then cleared up.
kennyglass123 said:
It may be a Sprint issue...happened to me last week then cleared up.
Click to expand...
Click to collapse
Its been happening to my phone for easily over a month now. And a friend of mine also has an epic that runs the exact same rom. Its also very annoying when playing music and videos cause it cuts out the sound to play the tone when it losses/gains 3g.
xm1337 said:
Its been happening to my phone for easily over a month now. And a friend of mine also has an epic that runs the exact same rom. Its also very annoying when playing music and videos cause it cuts out the sound to play the tone when it losses/gains 3g.
Click to expand...
Click to collapse
Try updating PRL and Profile.
Just tried updating the prl and profile and i still have the issue : /
after i updated both i restarted the phone and let it sit. After about 10 mins the 3g reset.
xm1337 said:
Just tried updating the prl and profile and i still have the issue : /
after i updated both i restarted the phone and let it sit. After about 10 mins the 3g reset.
Click to expand...
Click to collapse
Does your friend's epic with the same ROM also.do this?
Do you BONSAI?
Actually I used to use bonsai. This problem started when I upgraded to i want to say 3.0. When the problem first started it also had a terrible battery glitch (when i restarted the phone i lost 50% battery. but a restore fixed this but left the 3g problem). I upgraded to 4.0 and the problem still hadn't been fixed. So thinking maybe it had something to do with the rom, I switched to Syndicate Rom Frozen and thats what I'm using now. My friend still has a DK28 Bonsai on his phone because I'd rather not somehow give him this annoying issue. But as of now his phone does not have this issue, so think it has to be my phone and not sprint.
Could flashing the modem .tar in odin without selecting the .pit file do this? I feel like it might have changed something it shouldn't. From what i recall it completed successfully without the .pit.
Edit: also thanks a lot for your help so far kenny
Very happy i got a quick response and that my thread wasnt just ignored.
Have you ever Odin'd back to stock DI18? Do that and let it update OTA to EC05 and see if that fixes it. Then flash your ROM and see if your issue returns.
Do you BONSAI?
When I switched from Bonsai to SRF I odin'd back to DI18/stock and it still didnt fix the issue. However I didn't let it update OTA and just odin'd from DI18 to EC05 then installed SRF. When i get the time to do all that ill give it a try doing the OTA and get back to you.
xm1337 said:
When I switched from Bonsai to SRF I odin'd back to DI18/stock and it still didnt fix the issue. However I didn't let it update OTA and just odin'd from DI18 to EC05 then installed SRF. When i get the time to do all that ill give it a try doing the OTA and get back to you.
Click to expand...
Click to collapse
If you got the same issue with stock DI18 then you may have a flaky 3G radio in that phone. When you OTA maybe you should let Sprint look at it. You may get a new phone.
So as the title states, my Epic has been plagued by random reboots since installing EG22. The unit was a new replacement, not a refurbished replacement that tech support normally gives. I've had it all of four weeks now. It ran EF02 pretty perfectly. I have tried reloading EC05 (with ODIN) then loading EG22, and no dice. Before I flash EG22 I wipe the phone, cache, and dalvik 3 times. I've also redownloaded and hash checked the EG22 update I use (using the stock/deodexed EG22 update.zip from the development forum). Still no improvement, the phone will randomly reboot every 1-2 hours. Any advice on what I could try next is appreciated.
radugb out
UPDATE: also I cannot get into the "SYSTEM UPDATES" menu in the Settings/About Phone menu. Each time I try I get a forced close then a system reboot. Could the phone just not like EG22?
I have experienced reboots on both EE03 and EF02. I haven't tried EG22 as of yet. I hae never had it happen on EC05. I figure I'll just wait until the release because my phone just doesn't like the beta/leaked stuff.
Any test software has a chance that it will not work 100%
All Gingerbread leaks crash and reboot in low signal areas. I am assuming this is one of the reasons official hasn't been released yet.
Sent from my SPH-D700 using XDA App
Ok, but one I have an airave about 12 ft away from my phone so I get a great signal. And two, I'm still getting FC's when I try to enter the system updates menu. So I still think it could be something wrong with my phone.
radugb said:
Ok, but one I have an airave about 12 ft away from my phone so I get a great signal. And two, I'm still getting FC's when I try to enter the system updates menu. So I still think it could be something wrong with my phone.
Click to expand...
Click to collapse
How did you install EG22? If you did it through CWM it could have just been a bad flash. For the system menu problem. The crashes occur for me too, like above post low signal areas are not a gb leaks friend.
Sent using TouchPal Curve Input
I have been flashing zip versions thru CMW. I'll look up an ODIN-able EG22 tar or md5 and try it that way. But I will ODIN back to EC05 (with repartition to wipe the phone) then update to EG22. I'll let you all know.
As far a signal goes though, I'm getting full bars right now because my Airrave is so close to me.
radugb said:
I have been flashing zip versions thru CMW. I'll look up an ODIN-able EG22 tar or md5 and try it that way. But I will ODIN back to EC05 (with repartition to wipe the phone) then update to EG22. I'll let you all know.
As far a signal goes though, I'm getting full bars right now because my Airrave is so close to me.
Click to expand...
Click to collapse
You are right, that shouldn't happen with an Airave. A reflash may fix the issues you are having. Also don't use any CPU managers like SetCPU or Voltage Control on GB until source code and custom kernels show up.
Sent from my SPH-D700 using XDA App
Yup. That was it. Bad flash. This time I d/l'ed a .tar version of EG22 to flash with ODIN. Much better than before. No more FC's from the system menu and its been running 8 hours straight with no reboots. Muchas garcias.
radugb out
Glad to help.
Sent from my SPH-D700 using XDA App
Spoke too soon. I've had two random reboots, one yesterday, one today. So it definitely fits with what all y'all said that leaked GB ROMs tend to crash. Still not as bad as before, and I no longer get the FC's from the system updates menu.
I had one last night and one tonight at my house which I get a crap signal at in what Sprint describes as an "excellent coverage area" No other problems anywhere else.
I've had my first random reboot. Phone was WIFI connected, and forced roaming (Sprint has a tower down in my area, going on 7 days now). It was in the middle of a content update for an application I run, so I'm wondering if there is a memory leak for the network user or kernel space.
Does anyone know of an application that will keep a log of memory usage to track if a process is not releasing its resources?
Yup, same here. About once every two days I get a reboot. I haven't been able to connect anything I'm doing to the reboots, and it usually does it while the phone is just sitting.
Trouble is, Gingerbread is soooo much better than Froyo I don't want to go back
I really think it is the modem crashing.
You may want to try another modem.
also, i realised that on my wife's epic with eg22, it rebooted about 5 times a day, most of the time, it was right after using the slide out keyboard.
i deleted the keyboard counter slide apk thingy, since then, 1 reboot a day.
not great, but definitely better than 5.
x130844 said:
I really think it is the modem crashing.
You may want to try another modem.
also, i realised that on my wife's epic with eg22, it rebooted about 5 times a day, most of the time, it was right after using the slide out keyboard.
i deleted the keyboard counter slide apk thingy, since then, 1 reboot a day.
not great, but definitely better than 5.
Click to expand...
Click to collapse
Are you sure it is not a loose battery connection? My phone would do that with the extended battery and case. Had to put a little piece of thick paper in there to hold it tighter.
Definitely was the modem. I flashed the EE02 modem & now no random reboots. Signal(s) & battery life have gotten better too. I would have flashed the EF02/EF10 modem but that downgrade notice is oh so damn annoying!
Me and my friend have the same issue on our Epics OP, Its annoying but Im dealing with it cause these roms are so much better than pre eg22.
I dont have any random reboots but I get a random double vibrate. I have no idea where that is coming from
I've had two random boots since I've odin'd from EC05.. though I feel it was memory leak,and the phone just shutdown without sufficcient ram.
SchizioPunk's Epic Experience 2.1 Eclair -> Odin to EC05 Froyo. Rooted. Bloatware Removed. Voodoo Sound V9 Module Loaded. TouchWiz4. Enjoying my Customized Stock Experience.
Yeah well I tried the EH06 modem and it broke the 4G (amongst other things). So I got ol' reliable EE03 to fall back on.
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
bbecker42 said:
Hello xda community. I have a pretty large issue that affects my Epic. I recently had my Epic broken by blunt impact to the screen. So I sent it in and they sent a replacement in less than a day. I had Frozen 1.2 on my old Epic, and I had zero issues. But since I got my replacement, its been nothing but a hassle.
It doesnt get nearly as good battery life, it randomly reboots to the ACS logo, then endlessly cycles until the battery is pulled. Then when its turned back on, everything force closes, rendering the phone un-usable. The only remedy is to go to Clockwork and repair permissions. This will fix it for half the day.
Any advice?
Click to expand...
Click to collapse
The force closing is probably due to not having Journaling on.
I believe in the SRF 1.2 OP, there is a JournalingOn.zip, flash that (no wipes) and that should stop the force closing.
If it still is unstable for you, I recommend just reflashing the ROM.
Hope this helps.
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
nikon120 said:
Follow Acer's directions. If for some reason you still have an issue, then I'd recommend redownloading the rom.
You may also want to try a different kernel.
Click to expand...
Click to collapse
Exactly right
Sent from my SPH-D700 using XDA Premium App
I had friend who had the same issue. He went back to SFR1.1.1
then installed ACS updater and flashed SFR 1.2. That fixed his problem. I did it that way too and have not had any issues. Calibrate battery after flashing.
Sent from my SPH-D700 using XDA App
That sort of worked. It made it take longer for things to get hosed over again.So I tried resetting it to stock then flashing EG22, but each time I flash EG22, it doesnt do anything.The version stays at 2.2.1. What am I doing wrong?
What did you flash that is EG22?
Sent from my SPH-D700 using XDA Premium App
In order to better assist you, can you give us a step-by-step listing of everything you are doing? The files you are using with version #'s and your computer OS (with bit version).
I would recommend a full wipe of the phone, to remove any corrupted data
then do a clean install of SRF 1.2
then install the zip to turn on journaling
note: DO NOT use the reboot option until AFTER you have turned on journaling
What I did last night was returned it to factory stock EC05.
Im working with Windows 7 Home x64 on a Mac Pro, because for some reason neither Epic I've ever had will work with my custom built computer.
I flashed the EG22modem.bin with Odin 1.61. That didnt seem to do anything.
So later today, I am going to try this
http://forum.xda-developers.com/showthread.php?t=1184134
The modem only changes the baseband..
regardless, imo it sounds like the problems you are having are due to restoring backups.. is that the case?
I installed this
http://forum.xda-developers.com/showthread.php?t=1205024
and everything is hunky dory in the hood. Thanks for all the help
PLEASE READ THIS FULLY BEFORE CONTINUING!
looks like all the modem.bin files out there are the eg12 version (as i flashed to fix my phone also)
and my mom's has the eg30.
on further inspection this creates a problem, even after returning to stock and resetting everything if you plug your phone into kies the eg12 version gives a "this version of the device cannot be upgraded" while the eg30 says "this device is up to date" (both were hacked and returned to stock to check this)
At the moment there is no way to get eg30 back (will update post when found)
EDIT
Let it be known if you flash eg12 at the moment you cannot go back. you most likely will not be able to get a new modem until sprint/sammy release an update. whenever that may be.
Some people are saying the eg12 modem is causing the phone not to wake from sleep to answer calls. at the moment from what i can tell this is a small percentage of the total number of people who have installed eg12. this issue may or may not be caused by the eg12 modem on it's own. but we cannot jump to conclusions and really do not have nearly enough data on the issue.
that being said I and many others do not have an issue with the phone waking from sleep either on or off the charger.
but it would probably help others if we could collect enough data to be sure.
So if you have an issue with your phone sleeping please post in this thread.
include at least: (these are mine)
baseband: EG12
Kernel: 2.6.35.8-lostkernelexp+
Build: Starburst 10.22.11
how often does this problem occur: NEVER
if we can get at least this much info together we can get a better picture of what's going on and take it from there.
PLEASE do not go complaining in the [guide] thread that is for instructions on how to flash not for phone issues.
also posts 53/54/63 may help
probably wouldn't hurt to read through the thread either.
Perhaps the EG12 modem is why my phone is not waking to take calls.
mine was doing that for a little while also but reflashing the stock-eg30 filesystem and kernel seemed to fix it and i havn't had it happen again even after all the roms and kernels i've been throwing at it lately. so you may give that a try. could have just been the dead spots in my house though so ??
I'm betting the first time sprint/samsung release an update for the modem we'll be able to hijack it. but until then i was hoping for a solution to see if it helped my weak signal in parts of my house.
just a note the modem.bin gets flashed to....
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9 (mmcblk0p8)
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 720896
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin
i'm rusty at this anyone think...
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/backup/modem.bin bs=720896"
made a 16mb file ..... seems right. now i just need a test or two then to see if i can find a way to borrow moms phone again
EDIT
Knew it couldn't be that easy. when flashed back to phone gives version unknown and no signal at all . BLAH.
maybe someone will chip in with what i'm doing wrong. or samsung has some wackness with this partition that i don't know how to deal with and it's not possible this way.
edit bs=4096 doesn't help
I went back to stock, no root and all. Even did a factory reset and made is to hands free activation again. I ended up restoring a nandroid from a while back, the kernel is zedomax V3, I have the min cpu freq at 400 and it will wake to receive calls just before the caller is sent to voicemail, lol.
you may give the latest lostkernel a shot and see if that helps.
http://forum.xda-developers.com/showthread.php?t=1296348
mjcollum said:
you may give the latest lostkernel a shot and see if that helps.
http://forum.xda-developers.com/showthread.php?t=1296348
Click to expand...
Click to collapse
I'm currently on the latest lostkernel build stable 1.0.2.0 and it still will not wake for a phone call unless it's asleep on the charger I also flashed the modem on the sticky about a week ago. I have great reception where I live (San Francisco) and I've just tested it five times. It doesn't wake when called unplugged. Minimum cpu is 200-500 asleep. I'm going to odin back to completely stock to do more testing.
Maybe try the non experimental build without overclocking?
Mine seems to wake on calls both on and off the charger but you never know.
Wish we could figure out a way to get a eg30modem.bin as that may be part of the problem.
my original was EG30
tried to root, but messed up my phone, then i managed to unroot back, now i have the EG12 version.
same thing here, Kies can't update the firmware version.
first time here, thank you so much for you guys hardwork, i was able to get my phone working again!
I am beginning to think that modem.bin is bad for our devices!!!
Many who have flashed it are not getting calls while the phone is sleeping...
what do you mean "sleep mode"... means when cell screen is locked?
I just called my cell from office, cell phone responses after two rings(from office phone), then another 3 rings(from office) to enter the voice mail mode.
Update: I just noticed I have the same problem after flashed....
cordell12 said:
I am beginning to think that modem.bin is bad for our devices!!!
Many who have flashed it are not getting calls while the phone is sleeping...
Click to expand...
Click to collapse
dee_zee said:
what do you mean "sleep mode"... means when cell screen is locked?
I just called my cell from office, cell phone responses after two rings(from office phone), then another 3 rings(from office) to enter the voice mail mode.
Update: I just noticed I have the same problem after flashed....
Click to expand...
Click to collapse
Sleep mode is a couple minutes after screen goes off, phone not connected to USB or charger. All I know is while I am in sleep mode my calls do not come through. This is something that started around the time I flashes that modem.bin I bet many others are having the same issue but just don't know it yet.
Sent from my SPH-D710 using xda premium
The modem.bin isn't bad it's just an older build. The modem. Zip should probably be pulled so that this doesn't continue to spread. We're screwed until we get an official tar. Then the modem can be updated. The OTA probably won't fix it cause the upgrade path is EG30 to whatever the new build is.
We'll have to odin the modem. Bin most likely. Mine works fine. Occasional problems but not much. We just need the tar.....
Sent from my SPH-D710 using xda premium
I was going to suggest using the modem.bin from this thread, which I thought was EG30:
http://forum.xda-developers.com/showthread.php?t=1284602
But then I downloaded the one from the sticky, ran a checksum and discovered both came out the same. This is the same one on ACS. So apparently all the modem.bin's are EG12?
MD5: 7725e312721878079db180407e9364c1
ptfdmedic said:
The modem.bin isn't bad it's just an older build. The modem. Zip should probably be pulled so that this doesn't continue to spread. We're screwed until we get an official tar. Then the modem can be updated. The OTA probably won't fix it cause the upgrade path is EG30 to whatever the new build is.
We'll have to odin the modem. Bin most likely. Mine works fine. Occasional problems but not much. We just need the tar.....
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
You have the EG30 modem.bin?
If you have the EG12 try something, make sure nothing is running then manually turn off screen. Wait about 2 minutes then call your device....
if it happens to ring, try it again. Mine will ring sometimes, it will ring about a half a ring before the caller gets shot to voicemail.
sfhub said:
I was going to suggest using the modem.bin from this thread, which I thought was EG30:
http://forum.xda-developers.com/showthread.php?t=1284602
But then I downloaded the one from the sticky, ran a checksum and discovered both came out the same. This is the same one on ACS. So apparently all the modem.bin's are EG12?
MD5: 7725e312721878079db180407e9364c1
Click to expand...
Click to collapse
This is the one I used, it is RG12. If you look around the forum people are noticing they are not getting call while screen is off. If it isnt this modem.bin then what can it be? Going back to stock does not resolve the issue either. I had my device 3 weeks now and this started arounf the time I odin'd the modem.bin as someone claimed it as a fix for LOS.
cordell12 said:
You have the EG30 modem.bin?
If you have the EG12 try something, make sure nothing is running then manually turn off screen. Wait about 2 minutes then call your device....
if it happens to ring, try it again. Mine will ring sometimes, it will ring about a half a ring before the caller gets shot to voicemail.
Click to expand...
Click to collapse
I have the EG12. I have experienced that a few times but rarely. I've been on this modem since week one. I just didn't realize it.
Kaddaj said:
I'm currently on the latest lostkernel build stable 1.0.2.0 and it still will not wake for a phone call unless it's asleep on the charger I also flashed the modem on the sticky about a week ago. I have great reception where I live (San Francisco) and I've just tested it five times. It doesn't wake when called unplugged. Minimum cpu is 200-500 asleep. I'm going to odin back to completely stock to do more testing.
Click to expand...
Click to collapse
My old Android's alarm wouldn't go off if the clock was set to below 400Mhz. Definitely try setting the clock higher and see if that works.
IA-32e said:
My old Android's alarm wouldn't go off if the clock was set to below 400Mhz. Definitely try setting the clock higher and see if that works.
Click to expand...
Click to collapse
Tried all kernels, higher clocks, everything in the book, lol. Could just be a defective device, but I am leaning towards the modem.bin. Only because all was well beforehand.
yes, you are right. I tested couple of times, unless with data cable attached to charger/PC, it won't ring.
cordell12 said:
Sleep mode is a couple minutes after screen goes off, phone not connected to USB or charger. All I know is while I am in sleep mode my calls do not come through. This is something that started around the time I flashes that modem.bin I bet many others are having the same issue but just don't know it yet.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I took my phone to sprint this morning because I hadn't put 2 and 2 together yet. They ordered me a new one (backordered too!). However if we can get the EG30 somehow I will just cancel the replacement. Anybody with EG30 and the knowledge care to pull it for us?
Sent from my SPH-D710 using xda premium
cordell12 said:
Tried all kernels, higher clocks, everything in the book, lol. Could just be a defective device, but I am leaning towards the modem.bin. Only because all was well beforehand.
Click to expand...
Click to collapse
I agree with Cordell12, i think its the modem.bin file that is causing our phone to not ring while idle/sleep mode without being connected to a computer/charger. Mine started happening when i flashed the modem.bin file about a week ago. Sprint service center couldnt figure out the problem when i brought it in, so they're replacing it.