Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?
Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.
Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?
I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?
One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...
For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms
Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.
For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ
Related
There seems to be a major issue with the 4.06 radio and my phone - every time I have tried to flash it (from both validated .img's and update.zips) my phone becomes extremely unstable afterwards.
It goes into booting loops, hangs at the X, when I get it to boot it crashes while using heavy 3G or WiFi data, reboots when plugged into USB and receiving a call and it becomes almost impossible to get into recovery mode etc, etc.
The only way to get back to a working phone is to revert to stock 4.04. I have tried 5 different times over the last 2 weeks now with the same results every time.
I am starting to wonder if it is a AT&T/Rogers N1 issue or something specific to my device. If it was my device I would think that flashing back to 4.04 would also cause problems but that is not the case. This makes me believe there is there maybe an incompatibility with the leaked Froyo radio.
Appreciate any thoughts/comments.
I'm not having that problem. I flashed Modaco's first FroYo repack with root and the new radio, and things have been fine. To be honest, the only thing I've noticed is that Bluetooth seems to sync a lot faster to the head unit in my car.
Did you do a complete wipe before you installed the update and what applications have you added that may not like the radio?
Edit to add: By the way, you guys have a kick-ass little HTC Magic up there. It may not be a Nexus One, but it more than holds it's own running cyanogen. I have an import that my wife is playing with. I really like it.
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
I just verified my version - it's definitely the 4.6.00.12_7 Froyo radio firmware.
codesplice said:
Have you tried the 4.6.00.12_7 radio as well ast the 4.6.00.2_2? The 12_7 is working flawlessly for me both on Froyo and on CM 5.0.8-derived ROMs.
Click to expand...
Click to collapse
I tried the 12_7 last night and after flashing it using fastboot, my phone got stuck in a reboot loop. I could get back into fastboot and saw the new radio version on the screen but could not for the life of me get my phone to boot into either the rom or recovery mode - I pulled the battery, took out the SD card etc but nothing worked. This prevented me from flashing a ROM and I could not get into Recovery. After about an hour of trying, I managed to get the 4.04 radio flashed using fastboot and then my phone booted with no problems.
Previously, I tried the various Froyo builds and with no additional apps installed I would still get random roboots when using data via either 3G or WiFi - usually when I try to do something big like downloading/syncing a large file.
This is the story every time I try a 4.06 radio. 4.04 is rock solid.
Have you tried flashing the 4.6 radio via an update.zip as opposed to through fastboot? It's about the only other idea I can think of lol...
Just checked, I flashed the 2_2 last night, not 2_7.
I have flashed the radio via update.zip before and my phone worked but would be unstable. I will have to double check which version I used, could have been 2_2 as well.
codesplice said:
Come to think of it, that's the radio version I'm currently using, and that's where I got mine while I was running his ROM. So yes, flash that zip, flash Kangorama, and you should be square.
Click to expand...
Click to collapse
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Maybe try the 12_7 radio from http://forum.xda-developers.com/showthread.php?t=692609 ? I'm fairly certain that is the same radio update that I have applied on my AT&T N1.
edit: disregard....
I'm running out of ideas, dude
codesplice said:
I'm running out of ideas, dude
Click to expand...
Click to collapse
I appreciate your input. Thank you. I will try _7 again.
DvTonder said:
This is the same radio image I flashed two days ago and it worked for me quite well for an entire day (light 3G use) and then started crashing the phone when I tried downloading larger files (using the Audible app) via both WiFi and 3G in the evening. Once it started crashing I could not get into recovery until after I pulled my SD card. Once it booted OK without the SD card I put the card back and it booted ok again. It would still crash on heavy data use though.
Click to expand...
Click to collapse
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
attn1 said:
Did you try not running/removing the audible app and see about stability then? What else are you using? Not every app is going to play nice with newer firmware.
Click to expand...
Click to collapse
The crashes started just after I got the Rom installed.
I did the following:
- Nandriod backup (thank goodness for this!)
- I wiped all as per instructions
- Installed radio, rebooted OK
- Installed ROM (Rodriguesstyle 1.6)
- Booted OK into setup
- Configured my phone - first crash just after entering my gmail ID and the syncing of all the apps from the market started
- Rebooted, configured my phone again - apps installed this time but while configuring ChompSMS the phone rebooted again
- Rebooted, phone came up clean, ran OK all day
- Got home and tried syncing Audible content - phone crashed
- Could not get into recovery or boot the phone normally for almost an hour (pulling battery etc did not help)
- Pulled the SD Card and the phone booted, shut down, put the sd card in again, phone booted OK
- Got a phonecall, phone rebooted
- Got fed up and restored 4.04 radio and stock ROM
- Phone stable since
I was running the following apps:
- Autokiller
- Doubletwist Player
- Audible beta
- Silent Sleep
- ChompSMS 4.2
- Switchpro Widget
- Barcode Scanner
- ADW Launcher
- newsRob
- File manager
- Backgrounds
- Rom Manager
DvTonder said:
The crashes started just after I got the Rom installed.
I did the following:
...
- Installed ROM (Rodriguesstyle 1.6)
...
Click to expand...
Click to collapse
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
attn1 said:
What kernel is the Rodrigessstyle ROM using?
Try Modaco's straight up Froyo repack - it has a stock kernel. I'd get as close to stock Froyo ROM/Radio as possible, see what I have and then go from there.
Also, make sure you're using an updated version of chompsms. I think I heard that reports were that it was not compatible with Froyo, but that it's been updated.
Click to expand...
Click to collapse
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
DvTonder said:
I used the stock kernel. ChompSMS 4.1 and later is compatible and I was using 4.2. I am planning on trying the new Kang-o-rama 0.8b1! (CM-5.0.8+2.6.34 Kernel) rather than Froyo - if only I can get the radio to flash.
Click to expand...
Click to collapse
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
attn1 said:
Why not start with FroYo - the ROM the radio was meant to work with - before flashing anything else? If it doesn't run then, you have a real problem. otherwise, you have no idea where the problem is.
Click to expand...
Click to collapse
Point taken. Back to the basics.
I came straight from Rodriguesstyle 1.6 with the included add-on OV/UV kernel to Kang 0.8b1 without any issues. Even got the 720p hack working beautifully
well i am using the new froyo radio with my ATT nexus one, and its been no different than the old radio. no crashes or anything. however, i had NO idea that there were 2 froyo radios. is that what someone just posted on the first page?
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Let's hope that's not OPs issue, though the problem seems to be pointed in that kind of direction. Hope you get your situation resolved under warranty.
chordmasta said:
I have had a simmilar experienc, but it is NOT froyo related.
I was rooted, on the desire ROM
It was restarting at seemingly random (and frequent) times through the day -
I reflashed to stock 2.1.
During setup, phone rebooted.
Got through sign-in. Installed some apps. Phone rebooted.
Phone was absolutely fine, as long as I didn't touch it. I would use it - browse, etc. Seemed to be fine. Would then reboot. FLashed it up to froyo. Same.
I think it's the bad RAM issue i've seen reports of, but I'm not sure. Sent in for a replacement.
Click to expand...
Click to collapse
Heh, never thought I'd be posting here but I want some ideas before I unroot and bring my phone in :/
For the last I'd say month and a half or so my gps hasn't been working properly. If I'm running an aosp rom (AOSP, CM, my own compiled roms, etc) gps will not get a fix.
I've tried using both the GPS Status app and GPSTest app to reset the 'aiding data/agps data' to no avail.
I've ran the RUU, re-rooted and done a fresh wipe/flash of a rom that I know had working gps for me in the past (an aosp rom again), still nothing.
Just recently today I wiped my userdata, cache, and system partitions via fastboot. Then proceeded to do a clean flash of the Mau5 CM6 rom. - repeated this process for AOSP's, and CM 6.1. All of which had the same results, no gps fix.
As I said for some reason it only seems to be a problem on aosp rather than senseUI. If I flash the stock sprint rom or any of nfx's sense roms for that matter I get a gps fix within a minute. Same goes for the stock RUU.
So my question is this: what other ideas do you guys have for me?? I'm fresh out
Edit: yes i've updated my prl and profile plenty of times, it doesn't help.
kyouko said:
Heh, never thought I'd be posting here but I want some ideas before I unroot and bring my phone in :/
For the last I'd say month and a half or so my gps hasn't been working properly. If I'm running an aosp rom (AOSP, CM, my own compiled roms, etc) gps will not get a fix.
I've tried using both the GPS Status app and GPSTest app to reset the 'aiding data/agps data' to no avail.
I've ran the RUU, re-rooted and done a fresh wipe/flash of a rom that I know had working gps for me in the past (an aosp rom again), still nothing.
Just recently today I wiped my userdata, cache, and system partitions via fastboot. Then proceeded to do a clean flash of the Mau5 CM6 rom. - repeated this process for AOSP's, and CM 6.1. All of which had the same results, no gps fix.
As I said for some reason it only seems to be a problem on aosp rather than senseUI. If I flash the stock sprint rom or any of nfx's sense roms for that matter I get a gps fix within a minute. Same goes for the stock RUU.
So my question is this: what other ideas do you guys have for me?? I'm fresh out
Edit: yes i've updated my prl and profile plenty of times, it doesn't help.
Click to expand...
Click to collapse
alright, you may get pissed but here it is. Turn on navi on your phone, leave it alone for a while (obviously don't do this whilst in a nuclear fallout shelter)
I have had to WAIT (the first time) for gps every time I flash a rom (or a kernel) that's aosp base, usually pick up a signal somewhere between 5 and 10 minutes, then every time I use gps after that it's fine. There was even a guy's post way back in the early november area of deca's kernel thread that said he got a lock around the 30 minute mark on a CFS using gps status.
hope you can get a lock If you already did the gps status fix reset download and waited, then disregard, otherwise try waiting a while, it might work, it did for me. Good luck bro.
il Duce said:
alright, you may get pissed but here it is. Turn on navi on your phone, leave it alone for a while (obviously don't do this whilst in a nuclear fallout shelter)
I have had to WAIT (the first time) for gps every time I flash a rom (or a kernel) that's aosp base, usually pick up a signal somewhere between 5 and 10 minutes, then every time I use gps after that it's fine. There was even a guy's post way back in the early november area of deca's kernel thread that said he got a lock around the 30 minute mark on a CFS using gps status.
hope you can get a lock If you already did the gps status fix reset download and waited, then disregard, otherwise try waiting a while, it might work, it did for me. Good luck bro.
Click to expand...
Click to collapse
I've done the reset, download and waited upwards of 30+ minutes before (I usually have it connected with the wake-lock on so the screen doesn't time out) I've gotten a signal doing that once or twice, but as soon as i close the app using gps, be it either one of the two gps fix apps or google maps, and open it back up, I have no signal again.
Same thing happens if after I wait however long until I get a fix and then later I reset the phone, I don't get gps signal after the boot.
Thanks for the ideas though
Edit: I also want to add I've done the suggested steps from the earlier roms where you boot up a sense rom, get a gps fix, then flash an aosp rom. And I've also tried a few of Deca's kernels. Same deal
Just wanted to add I ran the RUU again and did a nandroid restore of a Darchdroid 2.8 rom that I know had working gps. Same problem.
Sooo.. After finals this week I'm just going to bring it in and see what my options are.
Have you updated to the newest radio and PRL?
dmcaylor said:
Have you updated to the newest radio and PRL?
Click to expand...
Click to collapse
Yes, I've tried 4 radios, and both 60671/60672 for the PRL.
Thanks for the help though
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
muziling said:
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
Click to expand...
Click to collapse
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
kifno said:
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
Click to expand...
Click to collapse
radio: 2.42.02.10.29.zip
PRL: 2.20_003
ROM: aospCMod-HC-20110421-signed.zip
no tweaks
carrier: china telecom
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
kifno said:
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
Click to expand...
Click to collapse
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
Hmp, stick with a rom that works THAT YOU LIKE, not by what I tell you. But did you try these rom's?
- CM v7.0.2?
- GingerSense?
- AOSP 0.9.9.2 Froyo?
- CM6.1-RC2?
- NFX Stock Rom?
- My Sense Roms?
Try all of those and for whichever the phone calls work, take note of that. And then also I'd like for you choose what you like the best. Also did you try the update prl/pri on a sense rom? Try doing it on the rom you're on now
And glad to see it worked for ya bud
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
il Duce said:
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
Click to expand...
Click to collapse
Yes oldghost uses a Chinese carrier and I don't think he had any issues at all. But first try updating the prl/pri
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
hareofthedog said:
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
Click to expand...
Click to collapse
Try troubleshooting the problem by doing the following things one at a time to see if they work:
- Try a different radio that works for the SPRINT HERO CDMA ONLY (else you will brick your phone, if you need help finding radios let me know)
- Try without firerat's
- Try wiping everything using the latest official clockwork mod 3.0 after backing up everything
- Try s0be's kernel
- Try the official CM7 v7.0.2
i can come up with more options for you to try one by one but that should last you for about an hour or so
after doing all those let me know what happens
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
hareofthedog said:
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
Click to expand...
Click to collapse
Glad to see its working now. If you need any more help feel free to PM me or post again in the q n a forum and the community and myself will gladly answer your question asap.
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
muziling said:
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
Click to expand...
Click to collapse
if a rom isn't broke, don't fix it...stick with gingerbread, its fresh out the oven
but seriously if cm7 works, then use it. unless if you really don't like cm7....but i doubt that..i hope
i used this shipped rom when i got my n1 6 months ago,
Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
i received all the updates, it was working fine.
the other day, i decided to use the same passimg.zip file,
when phone read the sd card, i accidently selected recovery, it started to do recovery process, middle off the process i freaked out because that was not i wanted to do so i turned off the phone and install passimg.zip
i install all the programs i use and received all the updates,
now n1 sound level goes very low even it shows sound level is max,
its impossible to hear when it rings or playing music.
when i turn off and on the phone i get the sound back, after some time sound level goes very very low even sound level in max. so i turn off and on again and i get sond back,
i dont have any problem during calls i can hear,
right now
version 2.3.6
build number GRK39F
how can i fix this?
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
i downloaded same passimg file and installed it to my nexus one, same proprem continuous.
when i turn off and on, everthing normal.
any ideas?
Dude Random21 said:
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
Click to expand...
Click to collapse
"full wipe" means, using passimg file and install it again?
Full wipe means to do a factory reset, usually from recovery.
i figured it out. i dont know why but the problem was a program called voipraider,
i uninstalled it, problem solved, thanks for your replies...
Ok well I'm glad you got it resolved
I have this same problem. I don't have the app mentioned above installed, so I'm hoping someone can chime in with another app that may cause this issue? I've done a full factory reset, reinstalled everything (MIUI rom.) Rebooting the phone doesn't always fix the problem.. sometimes rebooting a few times will bring the sound back to normal, yet randomly all sound on the phone is barely audible at max settings. If a normal reboot doesn't work, normally wiping dalvik will fix it. Would this mean the problem lies in one of my apps somewhere? Any advice?
Are you using DarkTremor's a2sd? If so, it is a well-known problem. And wiping dalvik or just the regular cache will reset it. Due to this reason (and a few other minor ones), I switched to S2E for my app2sdext purposes, but I am not sure how well it works with MIUI (it was designed to work with CM7).
@bassmadrigal
Thanks. As I think about it, DTs a2sd is the only common thing I had in my testing. Even switching between ROMs, I kept flashing DT. Since I always have issues with MIUI's stock A2SD (based of DT).. I went back to CM7. I looked into S2E and will take that route.
I hope this fixes it.. the sound was frustrating when my alarm is going off in the AM and it's not making a peep. I'll post back in a few days in hopes that it's ceased to be a problem.
Thanks again for hopefully solving my major nuisance.
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl