Related
dont know what happened I installed serendipity 5.7 and speedmod then noticed the problem after i put a new modem to fix bluetooth i noticed later that I wasnt getting calls. I could see them come in for about 1 sec then it looked like a force close happened. i have since tried new modems now im on UGJK3 as well as switched to firebird. any help is greatly appreciated and as this is my first post i hope i placed it right thanks ahead of time
ok i used odin to go back to stock seems to be seredipity odd since it worked at first o well back to tweeking some more
just in case this happens to someone else i believe the issue comes from titanium backup restoring user data that shouldn't be there. after rereinstalling serendipity i used just the app recovery part of titanium and it works fine now oddly it sent the kernal back to speedmod rather than firebird
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.
I see people have less chances to deal with call issues if they install CM10 through the clean way.
Please DON'T vote if you didn't install CM10 "correctly" and DON'T mention another issues here beside network related.
I think everyone has issues with CM10 no matter what....
At least one bug I got all the time: You can't make a video call in gtalk, it gets FC'ed immediately.
LarsPT said:
I think everyone has issues with CM10 no matter what....
At least one bug I got all the time: You can't make a video call in gtalk, it gets FC'ed immediately.
Click to expand...
Click to collapse
he's talking about calling through the cellular network, not gtalk or other issues. Please keep on topic.
I did a clean install of CM10 from the very start and had no call issues. I did experiment with an SU660 baseband before returning to V21b - and that also required a clean install. I guess I'm one of the lucky ones.
The problem I see here is what do you consider a clean install? I am not so sure myself.
Is smartflashing a BB then install CM10 clean enough?
I think of my installation as clean because
1) I came from CM7 (Temasek's last kang) after a factory reset.
2) Before that, I came from NVflash of Homero's ROM to recover from a corrupted CM9 leak flash
Since the first Nightly, I didn't have the "no audio in network calls" EXCEPT once with a Viber call where the other side could not hear me. It was fixed with a reboot.
BTW, I smartflashed 1 time during the 2-3rd nightly, to match RC's BB...
Now on yesterday's Nightly, 6 November, with auto time zone working finally.
machoman1337 said:
he's talking about calling through the cellular network, not gtalk or other issues. Please keep on topic
Click to expand...
Click to collapse
Oops sorry, I missed the "call".
Anyways, I always do a clean install, and I always get the audio bug (First nightly, and nightlies 3 and 4).
i have no problem on clean install.. wipe data partition,wipe cache,then advance wipe dalvic cache then format/system and format/cache then install zip from sd card,then wait till finish then use it more than 2 mins then reboot again to recovery then flash the gapps,then reboot.. voila i have no call issue,so far.. BTW i came from CM7 of gueste v3.7..
new2city said:
The problem I see here is what do you consider a clean install? I am not so sure myself.
Is smartflashing a BB then install CM10 clean enough?
I think of my installation as clean because
1) I came from CM7 (Temasek's last kang) after a factory reset.
2) Before that, I came from NVflash of Homero's ROM to recover from a corrupted CM9 leak flash
Since the first Nightly, I didn't have the "no audio in network calls" EXCEPT once with a Viber call where the other side could not hear me. It was fixed with a reboot.
BTW, I smartflashed 1 time during the 2-3rd nightly, to match RC's BB...
Now on yesterday's Nightly, 6 November, with auto time zone working finally.
Click to expand...
Click to collapse
the problem i think like new2city posted is misconception regarding clean install (full wipe)...
i myself didnt know what full wipe was but i googled it as i needed for flashing paranoid android rom(as it was my first custom rom) n what i found was...
1) wipe data/factory reset
2) wipe cache partition
3) mounts and storage/ format cache,data and system
4) advanced/ wipe dalvik cache
i do this before every installation whenever possible..
correct me if im wrong
EDIT: oops sorry didnt read the above post properly..
Allways did clean install. First time had audio problem after a few calls. Problem was gone when i changed bb
Sent from my LG-P990 using xda premium
why wait for 2 minutes?, before installing gapps. every time i just install it right after the nightly install finishes
up untill nightly 05 (always with clean install) tried like 5 different basebands and still had problems, am back gueste hybrid for now or if someone actually makes a stock-like ics I'll go there cause I need stability over nice and new software and to actually be able to use the phone side of my optimus at all times . I LOVE CM but for now it's a only a hassle.
the issues with calls dont appear just after flashing a new rom..they take from some hours to a day or two to start.
i reverted to cm7 with a nandroid backup with a factory wipe and...
cm10 call bug and plugging in the charger bsod bugs showed up
Sent from my Optimus 2X using xda premium
I continue with the problem
clean is installed, it worked perfectly after a day the problem a terrible noise.
Reinstall one baseband and followed the problem ..
Even if nothing gets fixed, thanks for this thread, now I've REALLY flashed a clean install
I formatted everything, my phone was even unbootable!!! Put the latest nightly in the external sd card and had to hold volume down to access CWM! It might be random or placebo, but the instead of the phone being a bit unresponsive at first, like the other times I flashed, it was great right from the first boot!! Even if doesn't fix the audio bug, thanks for this
Cheers!
With latest nightly of CM10 and clean instal i have more issues then before... very strange... i have baseband v20s and i am from Romania
Hello, I'm using Semaphore + CM10 JB for few weeks (installed with your support).
However I have a problem. The stability. My phone likes to resets byself, even few times per day. It happens irregularly. What's interesting, sometimes phone resets to the CWM. Sometimes resets and backs to work, sometimes totally offs the phone (and i need to pull out the battery) or freeze on cyanogenmod start screen (but not on normal start, only when resets)
Sometimes it happens when i'm using the phone, sometimes not. He likes to do that when i'm sleeping (for example, goes to the CWM and discharge the battery by whole night on full bright).
And much smaller, but maybe important issue: when the phone starts, shows the message Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
Firstly I installed CM10, i had the problems with the network, but after @xsenman's help (reinstall with older ROM before flashing CM10) everything works correctly and i can see IMEI too. I made an EFS backup in that old ROM, should i use that? This message doesn't intrude me, but i'm just thinking if this could be connected with reseting problems. My SGS works really nice, but that one issue is really annoying.
100 views and really no one can help?
Come on, i feel so lonely
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
thanks for your answer. However, maybe it's not a ROM problem? Maybe some application makes an issue. Is there any log where i can check that?
That IMEI stuff definitely isn't app-caused. I can only repeat my statement above. Don't worry about data, you can backup everything using Titanium Backup and SMS Backup+.
Btw: What ROM are you on?
Best regards
Sent from my Gameboy Color
True, IMEI not, but it's not a real issue for me. Actually, i'm absolutely satisfied of my i9000 (maybe flashlight absence, but it's hardware). Everything works fine, but reseting problem makes me nervous when I use the phone as car dvr or for endomondo ect.
I use Cyanogenmod 10, one of october's nightly versions.
So basically you don't want to change anything but you want us to help you? Sorry, that's not the way a community works.
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
przemek211 said:
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
Click to expand...
Click to collapse
Since when has this problem occurred? I doubt an app makes a phone reset itself.
Edit: I looked around your post history and you seem to have posted in the semaphore thread. Maybe something is wrong with the kernel?
Sent from my GT-I9000
Thanks for your answer. It's hard to say because I've flash a ROM and out of hand I installed the applications. It's the worst type of problems, because it doesn't happen instantly or regularly. Actually since i wrote the topic, i didn't see the problem, however i saw two-three times the attention about IMEI, so i think, the phone resets, but not seen.
/// amerkiller: you are using i9000 too, could you recommend me any other ROM? Probably I will need to install a ROM and wait, two-three days and check if the ROM makes any issues.
/// maybe, but how can i check it? It looks like work nice, my question in Semaphore's thread was about the features
I use Remics-JB, you can try it out if you want a Samsung touchwiz feel, and apps from the S3.
Slimbean if you want a minimalist ROM.
Hopefully, the problem will disappear.
Powodzenia
Edit: regarding the kernel, you can flash Devil and see if the problem persists.
Sent from my GT-I9000
So I will try Devil + Slimbean, thank you
amerkiller1995 said:
Powodzenia
Click to expand...
Click to collapse
Poles everywhere?
pozdrawiam
BlueFlame4 said:
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
przemek211 said:
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
Click to expand...
Click to collapse
You can find tutorials about flashing to stock.
http://forum.xda-developers.com/showthread.php?t=1102881
Flashing the stock ROM will recover your IMEI number if you currently don't have it and will wipe your personal files. Backup your IMEI while you're on GB and if you lose it, then restore it. Fyi I never lost my IMEI, it's not common. You should flash JB / cm10 twice, ICS/cm9 should be okay after one flash. Remember to wipe if the instructions say so.
When you'll attempt to flash cm10 in recovery, you'll get a warning about partition change. You'll have to chose to flash second time, this time it should work and the phone will reboot into a bootloop. Pull out the battery and enter recovery and flash cm10 again. This time it well install and reboot successfully.
Sent from my GT-I9000
It's everything working nicely? Asking out of curiosity.
Sent from my GT-I9000
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
przemek211 said:
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
Click to expand...
Click to collapse
Restarts shouldn't happen that was some unusual circumstance. The video problem is weird, post here if it happens again, lets hope its just bad luck.
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
przemek211 said:
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
Click to expand...
Click to collapse
In regards to two way recording, i don't think it's solved...
http://forum.xda-developers.com/showthread.php?t=863074&page=38
I never needed that feature, so i won't be much help, try different apps and remember some apps are on XDA, not only the play store.
Sent from my GT-I9000
I saw that, but it is only for Froyo, when i installed it into gingerbread i needed to re-flash my SGS
I tried a lot of apps, however it looks like being locked (if worked they made 0kB files)