Related
Well, me Hero started acting up about 2 weeks ago or so. At first i thought it
was the new 2.1 firmwares, but i went back to 1.5 and it still existed.
Here is what happens:
Whenever i wake it up, it acts really really slow, sometimes it wont even wake
up.
I think it happened when i updated the baseband to 2.41.05.02.03, but im not sure.
Doe anyone else have this problem??
jvz555 said:
Well, me Hero started acting up about 2 weeks ago or so. At first i thought it
was the new 2.1 firmwares, but i went back to 1.5 and it still existed.
Here is what happens:
Whenever i wake it up, it acts really really slow, sometimes it wont even wake
up.
I think it happened when i updated the baseband to 2.41.05.02.03, but im not sure.
Doe anyone else have this problem??
Click to expand...
Click to collapse
i had the same problem but mine seem like the screen wouldnt turn on.
when it doesnt turn on push menu and then hold end.
does it vibrate when you do that
Argh Matey! I hate when me hero acts up..... sorry couldn't resist.
brian2220 said:
i had the same problem but mine seem like the screen wouldnt turn on.
when it doesnt turn on push menu and then hold end.
does it vibrate when you do that
Click to expand...
Click to collapse
no it does not
jvz555 said:
Well, me Hero started acting up about 2 weeks ago or so. At first i thought it
was the new 2.1 firmwares, but i went back to 1.5 and it still existed.
Here is what happens:
Whenever i wake it up, it acts really really slow, sometimes it wont even wake
up.
I think it happened when i updated the baseband to 2.41.05.02.03, but im not sure.
Doe anyone else have this problem??
Click to expand...
Click to collapse
Have you tried RUUing the phone? If not, do that and then install 1.5 and see what happens. People seem to be experience far to many problems with these 2.1 ROMS, probably best to hold off until the official release by Sprint via OTA.
pseudoremora said:
Have you tried RUUing the phone? If not, do that and then install 1.5 and see what happens. People seem to be experience far to many problems with these 2.1 ROMS, probably best to hold off until the official release by Sprint via OTA.
Click to expand...
Click to collapse
there really are not that many problems with the 2.1's there are bugs but that is to be expected from a leak. I noticed I had this problem when I was using the flipz radio as well.
have u make a format or a factory set or unistalling the update.... have one -or more- of this work well ... don't forget to make a backup ... my wishes
wtphoto said:
there really are not that many problems with the 2.1's there are bugs but that is to be expected from a leak. I noticed I had this problem when I was using the flipz radio as well.
Click to expand...
Click to collapse
True. I'm running 2.1 right now, besides some minor sync issues, everything's okay. I'm thinking about making a ROM, but want to make sure everything works before releasing it. FriendStream seems to not be working, expect only on DarchLegend. I pulled the apks from DL and pushed them to DC.2 -- but got force closes, so I'm trying to figure that out now.
How do i uninstall the radio update? to downgrade.
jvz555 said:
How do i uninstall the radio update? to downgrade.
Click to expand...
Click to collapse
Av posted a thread with all the nec tools and guides. Search is your friend
I flashed RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe and now no problems with Bluetooth ....works 100% ...no force closed no skips, nothing at all ..
amazing that i have tried all the ROMs out there and they all had crappy BT and now all is working ....
rgildoss said:
I flashed RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe and now no problems with Bluetooth ....works 100% ...no force closed no skips, nothing at all ..
amazing that i have tried all the ROMs out there and they all had crappy BT and now all is working ....
Click to expand...
Click to collapse
as in you ran the exe from your computer or flashed the zip someone made of it?
regaw_leinad said:
as in you ran the exe from your computer or flashed the zip someone made of it?
Click to expand...
Click to collapse
i ran the exe from PC ..however further testing i think im stuck at the new bootloader .. i havent tried my nandbackup yet but no biggy ..all i wanted was the damn BT to work good as i use the phone to play nusic more then i use it to make calls...lol
had to re-root the phone , all worked fine except for the recovery image part but i was able to fix that ...all seems good right now ..gona test further and see what else i can break...
rgildoss said:
I flashed RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe and now no problems with Bluetooth ....works 100% ...no force closed no skips, nothing at all ..
amazing that i have tried all the ROMs out there and they all had crappy BT and now all is working ....
Click to expand...
Click to collapse
Damit, you suck
Although my bluetooth is much improved from the other roms I have tried it's still not as good as 1.5! 1.5 was running flawless!
Roman G said:
Damit, you suck
Although my bluetooth is much improved from the other roms I have tried it's still not as good as 1.5! 1.5 was running flawless!
Click to expand...
Click to collapse
LOL well i have just walked around the house and sure enough got some disconnects to ...like you said , not 100% but better then other roms... if i leave it on the table and sit in the same room, it works 100% no skips at all ...
well suppose i should change the title of this thread to 50% maybe 70% better then other ROMs ....
I hope this is NOT the final release for sprint, cause that will suck ....
PS... i have NOT recived one FC at all when using the BT ..the other roms i did every 5 min
rgildoss said:
LOL well i have just walked around the house and sure enough got some disconnects to ...like you said , not 100% but better then other roms... if i leave it on the table and sit in the same room, it works 100% no skips at all ...
well suppose i should change the title of this thread to 50% maybe 70% better then other ROMs ....
I hope this is NOT the final release for sprint, cause that will suck ....
PS... i have NOT recived one FC at all when using the BT ..the other roms i did every 5 min
Click to expand...
Click to collapse
just wanted to ask what it is that cause problems with b/t on the other roms. I use b/t on darch's rom every day for about 2 hours when I go to the gym and have never had a problem
looneylu said:
just wanted to ask what it is that cause problems with b/t on the other roms. I use b/t on darch's rom every day for about 2 hours when I go to the gym and have never had a problem
Click to expand...
Click to collapse
what head u use?
I have a s9-HD ... BT cuts out constantly
looneylu said:
just wanted to ask what it is that cause problems with b/t on the other roms. I use b/t on darch's rom every day for about 2 hours when I go to the gym and have never had a problem
Click to expand...
Click to collapse
Like I have always said it seems to be 50/50 across the board on 2.1 roms, some work great and some don't!
It skips and pauses atleast 5 time per minute of song in the 2.1 roms and 1.5 it runs flawless!
I don't think anyone really knows what causes the problems, I even ran a logcat while using bluetooth to see what was causing it, and each time it skipped noting came up!
rgildoss thats crazy **** on the FC's, I never had that on 2.1 roms it just did not work worth a ****!
I have to agree that if 2.1 comes out and this is still a problem I will definitely be returning the phone!
rgildoss said:
what head u use?
I have a s9-HD ... BT cuts out constantly
Click to expand...
Click to collapse
I am using the Samsung SBH-500 and have also tried the S9's with the same results!
Roman G said:
Like I have always said it seems to be 50/50 across the board on 2.1 roms, some work great and some don't!
It skips and pauses atleast 5 time per minute of song in the 2.1 roms and 1.5 it runs flawless!
I don't think anyone really knows what causes the problems, I even ran a logcat while using bluetooth to see what was causing it, and each time it skipped noting came up!
rgildoss thats crazy **** on the FC's, I never had that on 2.1 roms it just did not work worth a ****!
I have to agree that if 2.1 comes out and this is still a problem I will definitely be returning the phone!
Click to expand...
Click to collapse
i hear that the samsung leak has no problems at all with BT ..to bad we couldnt port the ad2p stuff over to our phones to see if it improves it
rgildoss said:
i hear that the samsung leak has no problems at all with BT ..to bad we couldnt port the ad2p stuff over to our phones to see if it improves it
Click to expand...
Click to collapse
I wish we could do that! I do know that Darch is trying to look into what is causing the problems with BT!
rgildoss said:
what head u use?
I have a s9-HD ... BT cuts out constantly
Click to expand...
Click to collapse
I use rocketfish rf-mab2.... and for me it's the complete opposite... I used to had constant skips on 1.5.... not anymore though
rgildoss said:
what head u use?
I have a s9-HD ... BT cuts out constantly
Click to expand...
Click to collapse
I had an S9 back in the day, used to cut out when I went running with my LG Dare and the bluetooth worked flawlessly for every other device.
Bluetooth is dependent on reflections. If you take any bluetooth device out into the middle of an open field, and expect it to work, you will most likely be disappointed.
This is why your bluetooth works fine when you're indoors, starts skipping when you're outdoors, then starts working again when you get into your car.
The human body is one of the best shields there is. All those nice organics and all that water, soaking up all those incredibly low-power microwaves.
posguy99 said:
Bluetooth is dependent on reflections. If you take any bluetooth device out into the middle of an open field, and expect it to work, you will most likely be disappointed.
This is why your bluetooth works fine when you're indoors, starts skipping when you're outdoors, then starts working again when you get into your car.
The human body is one of the best shields there is. All those nice organics and all that water, soaking up all those incredibly low-power microwaves.
Click to expand...
Click to collapse
The problems that we are having are totally unrelated to this!
For the ones that it does not work for, it just does not work, regardless of where we are!
rgildoss said:
i ran the exe from PC ..however further testing i think im stuck at the new bootloader .. i havent tried my nandbackup yet but no biggy ..all i wanted was the damn BT to work good as i use the phone to play nusic more then i use it to make calls...lol
had to re-root the phone , all worked fine except for the recovery image part but i was able to fix that ...all seems good right now ..gona test further and see what else i can break...
Click to expand...
Click to collapse
Are you able to use an older RUU to flash it back to factory?
i did try to run the old 1.5 ruu ..didnt work because this new RUU uses a new bootloader ..i havent tried anything else yet ...
rgildoss said:
i did try to run the old 1.5 ruu ..didnt work because this new RUU uses a new bootloader ..i havent tried anything else yet ...
Click to expand...
Click to collapse
Interesting...I wonder if you will be able to get an official Sprint OTA update when the final release is available. It is a good thing the test release seems to work or it sounds like you could brick your phone by running the .exe utility without an option to flash back to a previous factory rom.
bige3345 said:
Interesting...I wonder if you will be able to get an official Sprint OTA update when the final release is available. It is a good thing the test release seems to work or it sounds like you could brick your phone by running the .exe utility without an option to flash back to a previous factory rom.
Click to expand...
Click to collapse
Nope. I ran the .exe utility and now I'm back to Fresh 2.0d with the new PRI . You can still root and reflash recovery to the phone after using the installer.
danknee said:
Another (pain in the ass) option is to nandroid your current install >> install the official RUU using the .exe installer. This upgrades the PRI to 2.10_003 >> Then you can update your PRL to 60663 >> Then you have to manually push flash_image to /system/bin >> You have to give flash_image permissions
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
A bit ridiculous, but at least you get the 2.10_003 PRI.
Click to expand...
Click to collapse
danknee said:
Nope. I ran the .exe utility and now I'm back to Fresh 2.0d with the new PRI . You can still root and reflash recovery to the phone after using the installer.
Click to expand...
Click to collapse
Same here. Only I'm on DC 2.06, so it's confirmed it works on both ROM versions
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
XxsydenxX said:
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
Click to expand...
Click to collapse
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
flipzmode said:
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
Click to expand...
Click to collapse
Thanks Flipz, I appreciate the feed back, yes I'm on sprint. Using chompSMS, which to my understanding uses Mms.apk as it's middle man.
Anyways i'll update and get back to you on it. And no i didn't replace it.
EDIT: Also tested it using the default messaging app.
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
XxsydenxX said:
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
Click to expand...
Click to collapse
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
flipzmode said:
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
Click to expand...
Click to collapse
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
XxsydenxX said:
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
Click to expand...
Click to collapse
That's actually a known bug with this leak and affects all roms based on it. It's some type of conflict with HTC music. You can check here for a possible fix: http://forum.xda-developers.com/showthread.php?t=657244
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
XxsydenxX said:
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
Click to expand...
Click to collapse
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
flipzmode said:
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
Click to expand...
Click to collapse
Just like a tootsie-pop.... THE WORLD MAY NEVER KNOW.
I want to know when will the sound problem be fixed completely? im currently using fresh 1.5 because all of the 2.1 have problems with the sound.. when someone calls i cant hear them and they cant hear me! i cant be resetting my phone everytime this happens. the fix that they have dont work also it might prevent it from happening so often but all my calls are important... does any one know when this will be fixed fully or why is this happening? how to prevent it ? mayb its the cdma settings? Thanks alot
The audio problem for the effected phones will be fixed when official 2.1 comes out.
i found whats causing it.... so who has a nice rom with the older kernel before .29 .. wats the kernel ? lol
The issue is caused by audio drivers in the kernel not resetting. we do not have the source for .29 kernel so there is no fix. we dont know why this effects some people and not others. Since the audio drivers do not reset it does not allow anything to read them. so it continues resetting and resetting and this causes the cpu to be pegged by the constant retry and retry.
Any 1.5 or overclocked 2.1 Rom
The audiofix posted by avalaunch worked briliantly for me. I have not had the issue once since he posted his fix about two weeks ago.
Also just so you know, zens my touch Rom did not have the audio issues for me. Just be sure to reboot after the first boot to completely get everything working.
which fix the audiofx or audiorc?? or u on the newest one for testers? i hate the my touch roms omg lol whats the older kernel version
wait another thing could it be because we didnt update the radio ?? or u guys doubt that 1?
I have had the audio issue with every ROM i had used until i flashed the Dachdroid 2. Ever since i have not had any kind of issues with phone freezing or caller not hearing me when i answer. Its very strange, but i wanted to post to see if any of the Devs can find out the differences between whats in this ROM and all the othersthat would make it work. Again i have had audio issues with all except this one.
What is this Audio problem?
I've run ROMs with both the .29 and hacked up .27 kernels.
Is this a bluetooth audio problem? Or handset audio?
The problem occurs randomly, for me at least. It's an issue I've had as others have that no audio at all comes through after an unknown time. I notice mine is triggered when I get off the phone with someone, I get 'call lost' and then all my audio is gone and have to reboot to get audio back. It affects BT and handset for me.
Iv never had the problem and iv changed my radio quite a few times. I think im on my 4th radio.
Maybe later at night you could flash a 2.1 rom, change to a newer radio and give it a few test to see if it works.
Flipz has alot of radios and I think the stock one on his site.
(IF anyone trys flashing a radio this is really the only way you can brick your phone. DO not flash any radio unless it says CDMA htc hero. All of them are on flipzmode website. You cant go wrong if you get them from him.)
the issue will hopefully be fixed when they release 2.1 officially. and im still looking into the issue a little at a time. 99% of people reported that one of the two updates put together fix it.
the only other cause could be a hawrdware issue. like the moved one resistor on the board and this causes something in the kernel to restart drivers. idk that is a very very very simple thought. but anyways like i said hopefully it get fixed!
Dont know if this is related but its absolutely killing me
Just today the headset icon popped on and wont go away. I cant hear anything when using the phone because its stuck in this mode. I plug in headphones and the voice dialer starts. I can hear through the headphones, but taking them out does nothing.
Anyone have any info on this or if there is anything I can do?
yea thats y im on fresh 1.5 i hate the 2.1 simply because of the audio problem coming from the headset !!! andn darch droid2? does everything work correctly like camera ect ... i hope its not that dam mytouch theme that 1 sucks ill try tonight
killacammiami said:
yea thats y im on fresh 1.5 i hate the 2.1 simply because of the audio problem coming from the headset !!! andn darch droid2? does everything work correctly like camera ect ... i hope its not that dam mytouch theme that 1 sucks ill try tonight
Click to expand...
Click to collapse
yeah...Ive come to the conclusion that 2.1 is just not going to work for me...went back to fresh 1.1 and everything is good. Its funny though, Ive been on 2.1 since all of the work was done and never had a problem until now. Ive been on damn near every 2.1 rom and didnt have an issue. Now all of the sudden the handset icon shows up and I cant hear anything unless I put in headphones. Tried all of the audio fixes and searched the entire net looking for a resolution. Hopefully the official comes soon. I am definitely going to miss 2.1.
No1Lives said:
Just today the headset icon popped on and wont go away. I cant hear anything when using the phone because its stuck in this mode. I plug in headphones and the voice dialer starts. I can hear through the headphones, but taking them out does nothing.
Click to expand...
Click to collapse
That's more than likely a mechanical problem. Take it in to Sprint.
posguy99 said:
That's more than likely a mechanical problem. Take it in to Sprint.
Click to expand...
Click to collapse
I would think so too, but I went back to fresh 1.1 and its fine...
I'd go back, but then I'm stuck with not being able to receive picture messages. So far I get the audio problem every other day, and it's a simple reboot.
DexSade said:
I'd go back, but then I'm stuck with not being able to receive picture messages. So far I get the audio problem every other day, and it's a simple reboot.
Click to expand...
Click to collapse
a simple reboot ? a simple headache lol idk about u guys i dont want to have to restart my phone when i just got a call that i couldnt answer !! ..... is there any newer roms with the older kernel?? because i dont understand the whole kernel thing...
This audio loss issue is reason number one why all of the people who say "Who cares when HTC and Sprint release 2.1? We already have it!" are just total idiots.
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
It's network related. They better pay this months bill for you. Call Sprint and find out.
Sent from my PC36100 using XDA App
I've had a similar problem lately of not getting calls. I'm not missing all of them, but at least once or twice a day, all of a sudden I'll get a nerw Voice Mail, yet the phone never rang. And, I've had people tell me that when they call, it goes straight to Voice Mail
I just attributed it to having WiFi only on, although that is just a longshot guess on my part.
Ive been unable to receive texts girl 3 days now. Anybody find a fix?
Sent from my PC36100 using XDA Premium App
what rom? if it's calkulin's evio 1.8, there's your problem.
Cm7 final
Sent from my PC36100 using XDA Premium App
dkdude36 said:
what rom? if it's calkulin's evio 1.8, there's your problem.
Click to expand...
Click to collapse
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
dschoenike said:
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
Click to expand...
Click to collapse
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
dkdude36 said:
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
Click to expand...
Click to collapse
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
dschoenike said:
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
Click to expand...
Click to collapse
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
dkdude36 said:
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
Click to expand...
Click to collapse
wish i woulda asked you guys earlier i unrooted, went back to stock, spent 4 hours in a sprint store, now have a different evo coming in from sprint on tuesday. guess ill try what you said tomorrow before doing the exchange. cant today as im not home. thank you again for all that info. really appreciate it.
derek
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
JoshuaD80 said:
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
Click to expand...
Click to collapse
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
dschoenike said:
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
Click to expand...
Click to collapse
i'm not convinced it's your fault at all. sometimes funky things happen in the back end on sprint's side.
best of luck to you!
don't think this is a rom specific issue, it's most likely the network.
I'm having the same problem on savage-zen rom rc2...
What may help is updating your radios, prl, etc. I haven't done that in a while, not too sure that it will make a significant difference though.
dschoenike said:
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
Click to expand...
Click to collapse
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
just letting you know, the pri is different than the radio, and we are talking about evio 1.8 starting problems like this for many, including me.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
dschoenike said:
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
Click to expand...
Click to collapse
If you have the time I would try my suggestion and or dkdude36 suggestion. He is correct in that the PRi is not the radio. I was in a hurry to type out the message. But I do mean the PRI, and I use the 1.77. You'll have to root the phone again, and nan-unlock. Then install a ROM and a recovery. If it doesn't work you'll have to restore it to stock before you return the phone so it will take some time to do all that. I was running Evio 1.8 for a while then one day I couldn't receive calls. I tried many things but the PRI fixed my phone. It's really up to you and how much time you have.
calkulin's evio 1.8
dkdude36 i think is right, i had the same problem a month ago, had to call *2 for help.
want ah guess what rom i was running....evio 1.8!
now i'm on Eternal Prophecy 5.8 got to read the hole thread, zero bugs!