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
Related
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
I just rooted my Nexus yesterday to Cyans mod. I ve rooted before (tons of ROMS on my G1) so Im not a complete noobie. The ROM runs absolutely perfect and smooth EXCEPT for when I try to record video. Every time, and I do mean every time I try to record a video, the phone freezes for like 3 secs, and then reboots.
Camera shoots photos fine, and this is the only problem I have, but it is becoming a problem, considering I just bought the phone I searched the forms for this problem, and used multiple search strings and found no results.
Has anyone ran into this problem, and if so have you found a fix for it?
**MODS..I deeply apologize if this is in the wrong section.I worked a 10 hour shift and am half asleep while writing this. Please feel free to move if you see fit**
**EDIT..ok..NOT COOL...I just tried to watch a video, and that also no longer works. Anyone know of a fix for this?
Same issue here. Meh...
Ended up switching to Froyo. Hope Cyanogen keeps up.
drpfenderson said:
Same issue here. Meh...
Ended up switching to Froyo. Hope Cyanogen keeps up.
Click to expand...
Click to collapse
If you've flashed the 'Froyo' radio then you'll have to downgrade it before video will work, or move (back) to Froyo.
If you haven't changed radio then I have no idea!
same here. the test video i took when i got the (ph)one was amazing quality so i'm looking forward to this working again!
If you guys were EVER on Froyo. It updated your radio. If you then went back to CM builds, you will need to downgrade your radio to the eclair radios in order for the camcorder to work properly.
The phone hasnt been on Froyo (that I know of), so thats not causing my problem. I tried to flash the prerelease before I was rooted, but it was US only and didnt work. I didnt however update my radio when I flashed to Cyan, but I was told this wasnt causing the problem. At this point, anything to get my cam and videos working again!
Would be awesome if Cyan, the man himself, could hook us up with a fix or some advice on this one!
Dai323 said:
The phone hasnt been on Froyo (that I know of), so thats not causing my problem. I tried to flash the prerelease before I was rooted, but it was US only and didnt work. I didnt however update my radio when I flashed to Cyan, but I was told this wasnt causing the problem. At this point, anything to get my cam and videos working again!
Would be awesome if Cyan, the man himself, could hook us up with a fix or some advice on this one!
Click to expand...
Click to collapse
if you attempted to flash the froyo stock update, it included the new radio. its very possible that it successfully flashed your radio, but failed to install the froyo ROM. you can easily check if you have the new radio by going into your settings and checking the baseband version. i bet you are on the new froyo radio, which is known to break video with all 2.1 ROM's. and vice versa, the old radio breaks camcorder on 2.2 ROMs.
so each time you jump between a 2.1 and 2.2 ROM, you have to flash the associated radio as well.
GOOD POINT BRO. I will check this now...
**EDIT** that was it..I must have went to Froyo radio unknowingly. I flashed the stock Nexus radio, and vids and video recording are now working just fine.
Hope this thread helps the others. I foolishly searched "cant record videos" and found nothing, when I should have searched "cant play videos", as there are many threads on that one.
Again, thanks for your help!! Didnt expect a solution so quickly!!
It also seemed to give me 3g problems when I just flashed back, but I ll deal with that one tomorrow after work
Same issue
I have a n1 with 5.0.7.1 and my phone also reboots upon trying to launch the camcorder feature. I'm going to try out the new 5.0.8 test3 with 720p hack add-on and see how that goes.
htctouch1313 said:
I have a n1 with 5.0.7.1 and my phone also reboots upon trying to launch the camcorder feature. I'm going to try out the new 5.0.8 test3 with 720p hack add-on and see how that goes.
Click to expand...
Click to collapse
Any luck? I recently upgraded to CyanogenMod 5.0.8 and immediately after updating I noticed the change. I can watch videos in Gallery just fine, but trying to record (or open Settings) in the camcorder mode causes the phone to hang and then reboot.
I never once tried to get anywhere near Froyo. I'm still waiting for CM6. Any advice on how to restore video functionality? Should I downgrade to the previous version of CyanogenMod? Is that even possible?
As I said, I highly doubt this is a Froyo issue, but it's clearly related to upgrading to CM 5.0.8.
ronocdh said:
Any luck? I recently upgraded to CyanogenMod 5.0.8 and immediately after updating I noticed the change. I can watch videos in Gallery just fine, but trying to record (or open Settings) in the camcorder mode causes the phone to hang and then reboot.
I never once tried to get anywhere near Froyo. I'm still waiting for CM6. Any advice on how to restore video functionality? Should I downgrade to the previous version of CyanogenMod? Is that even possible?
As I said, I highly doubt this is a Froyo issue, but it's clearly related to upgrading to CM 5.0.8.
Click to expand...
Click to collapse
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
prettyboy85712 said:
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
Click to expand...
Click to collapse
I am not aware of ever having modified any "radio" functionality on my Nexus One. I bought the phone retail at the beginning of May, so it had stock 2.1. About a week later I flashed via USB to whatever version of CyanogenMod was current then. (I'm sorry and embarrassed I can't be more specific.) Everything worked flawlessly.
Then about three days ago, I downloaded the CyanogenMod Updater app from the Marketplace and used that to move to CM 5.0.8. I also performed a backup with Titanium, from which I restored after updating to CM 5.0.8. Since this was done, I my phone freezes and reboots whenever I try to record video. I mentioned the Titanium backup because perhaps the Restore System Data feature resulted in broken settings. But I do recall seeing "720p video" in the changelog to CM 5.0.8, so I'm guessing that's probably the culprit.
I don't understand how the radio would be affecting my camera, but I'm willing to try anything. If we assume that somehow the CM update did change my radio settings, how would I go about correcting that? Should I just wait for CM6, or is this radio problem likely to persist if I don't address it specifically? Is regressing to an earlier version of CM an option?
prettyboy85712 said:
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
Click to expand...
Click to collapse
D'oh. This was clearly it. Because I got CM 5.0.8 via the CyanogenMod Updater app, I did not see that I was supposed to update the radio to Froyo independently of installing CM.
I tracked down the radio image (the Full Update Guide has all the info, for any interested persons) and flashed with that, and sure enough, I know have smooth 720p video recording.
Thank you so much for bluntly and persistently calling my attention to the radio image issue. I'm going to go back to playing with my favorite toy now. =)
Hey Guys I put together a Q&A thread for this rom to prevent tons of new threads about rom Spicific questions from new users.. Please feel free to post any questions here.
As Aslways there is no Flaming, name calling or the such.
No question is too noobish, But please look for your answer first.
Now for the info needed to help. In your post make sure to included the version of the rom you are using, modem, kernel, ext...
Also please give it some time for your question to be answered.
Pheonix FAQ
Hi. I'm currently on Phoenix 4.5. If i would like to flash to Phoenix 5.2 or Supernova 2.3, would I need to odin it first or can I just flash it over my current ROM?
Also will I need to clear cache, factory reset, etc before flashing?
Thank you.
oblivianz said:
Hi. I'm currently on Phoenix 4.5. If i would like to flash to Phoenix 5.2 or Supernova 2.3, would I need to odin it first or can I just flash it over my current ROM?
Also will I need to clear cache, factory reset, etc before flashing?
Thank you.
Click to expand...
Click to collapse
Really, it's up to you. Some people like to go back to stock. Some don't. I NEVER odin back unless I want to get rid of voodoo quickly. Here is my procedure; boot into CWM recovery, factory reset, clear dalvik cache, install rom. I have never had any problems with this method.
yay! a dedicated Q&A!
maybe here ill get a better answer regarding this:
thanks for answering, although it may be true, i have a feeling that it isnt exactly correct for some of the questions i asked. can any one else comment/confirm?
All captivates are not created equally. Meaning you could have two side by side and flash both with the same rom and have one perform better with it than the other. So its all about finding what works best for you
Originally Posted by Trusselo
damn it i just flashed the darkfire blue theme last night!
redo....
i feel dumb asking but ive been wondering for a while, and havent found a clear answer,
can someone explain what the advantage of having a jpy and a js5 version is?
whats the difference? different base rom ya, but whats different? and why do some people prefer one over the other even when they are torn appart and customized anyway? is it a regional thing?
Click to expand...
Click to collapse
new phoenix 5.2
2 questions:
1. What's the difference between the regular download and js5 base?
2. How is the overall speed and stability?
Thanks!
oblivianz said:
Hi. I'm currently on Phoenix 4.5. If i would like to flash to Phoenix 5.2 or Supernova 2.3, would I need to odin it first or can I just flash it over my current ROM?
Also will I need to clear cache, factory reset, etc before flashing?
Thank you.
Click to expand...
Click to collapse
majinzen said:
Really, it's up to you. Some people like to go back to stock. Some don't. I NEVER odin back unless I want to get rid of voodoo quickly. Here is my procedure; boot into CWM recovery, factory reset, clear dalvik cache, install rom. I have never had any problems with this method.
Click to expand...
Click to collapse
As for me, I disable lag-fix, always Odin back to JF6, Master Clear, then install my new ROM. In the end it's up to you. I've rarely had any issues while doing my flashes this way. majinzen may rarely have any issues doing it his way.
I can only tell you what works for me.
FC from Test-to-speech settings
I'm getting an FC when clicking "Text-to-speech settings" in the "Voice input and output" settings. Anyone else confirm this?
I'm using 5.2 JS5. I did flash to stock and MC before installing (twice).
EDIT: 5.2 JPY does not have this problem.
drothenberger said:
I'm getting an FC when clicking "Text-to-speech settings" in the "Voice input and output" settings. Anyone else confirm this?
I'm using 5.2 JS5. I did flash to stock and MC before installing (twice).
EDIT: 5.2 JPY does not have this problem.
Click to expand...
Click to collapse
if you want that feature you will need to grab the tts.apk from another ROM and put it in system/app.
h0ckey10 said:
2 questions:
1. What's the difference between the regular download and js5 base?
2. How is the overall speed and stability?
Thanks!
Click to expand...
Click to collapse
Regular link is JPY and JS5 link is well, JS5.
Speed on regular is awesome and speed on JS5 is even better. Battery is not an issue on either for me and many others. Keep in mind your results may vary depending on use, modem and kernel should you choose to change it.
adamholden85 said:
drothenberger said:
I'm getting an FC when clicking "Text-to-speech settings" in the "Voice input and output" settings. Anyone else confirm this?
Click to expand...
Click to collapse
if you want that feature you will need to grab the tts.apk from another ROM and put it in system/app.
Click to expand...
Click to collapse
Thanks, Adam! I grabbed PicoTts.apk from Darky's v9.3B1 and that solved my problem.
no Bootani anymore
ok so im a bit of a novice flash whore but ive not seen this , i downloaded Pr 5.2JS5, then upgraded the new "c' kernal, all doing well except i cant get the tts.apk to install (stole it from FF 2.2), (ohwell) but i changed my bootani to the new "ashes" via renaming and putting in system/media (overwrite).. now i have nothing....its pauses with a black screen for the alotted time as is there would be one, then it loads the home screen. i tried to revert to the original one by downloading it from -hq , but same result ... did i screw up?
EDIT: This Q&A is a nice touch , i read the hell outa the dev forums, but still have some basic questions now and again .. Thanks!!
Edit: so i pulled the original Bootani from the system/media from a copy on my pc and reapplied it and it works , there may be an issue with the compatability of the "add ons" boot animations at phoenix-hq and the current version "5.2' at the moment , so i guess patience is in order....still having force closes after applying the ttsservice.apk to the rom from other roms..... force closes.
edit: so i hope this helps someone else cause its makin me look like an idiot....the file need for the "Voice input/output" in the settings to stop FC's is "PicoTts.apk", i stole it from the "PR 5.2 JSY" and placed it in the "PR 5.2 JS4"...works fine now! .. but i hear that "adam" isnt going to be supporting the JS4 build any longer....sheesh. lol
I love 4.5 but I have one problem, bluetooth does not want to pair with my Ford sync system, any suggestions or changes I can make? I have tried every thing I can think of but it will not find my phone.
[Q] Phone Call Recorder
I am getting ready to flash Phoenix 5.2. Really like Adam's Roms. however I keep seeing more roms with the call recording in the phone dialer. Does anyone know of a way to transport that feature into Phoenix?
Is it just a matter of grabbing the phone.apk?
Is it even worth it?
Any input is appreciated on the matter. I want to try it but not enough to pull me away from Phoenix, Firefly, or Supernova.
A real noob
I am new to the droid phone, and i have flashed my phone to froyo 2.2. I really like to go to the phoenix rom but have a few questions.
1. I am a very visual person and was wondering if there are any videos on how to install phoenix to captivate phone.
2. I looked at the options for phoenix and still did not see if phoenix supports playing call through car speakers, which is why i'm changing roms in the first place.
3 Which phoenix version would be best suitable for a noob.
Hey,I'm using Phoenix since 2.5 now i'm on 5.2 and it's the best rom I've flashed.The problem is I'm backup everything using Titanium Backup since 3.5 (all apps+system data).Before crossing from 4.5 to 5.2 I've backup everything and then restore all of them.Will this mess up my rom ? I didn't found any problems yet.
Sorry for my bad English
ck9035 said:
Hey,I'm using Phoenix since 2.5 now i'm on 5.2 and it's the best rom I've flashed.The problem is I'm backup everything using Titanium Backup since 3.5 (all apps+system data).Before crossing from 4.5 to 5.2 I've backup everything and then restore all of them.Will this mess up my rom ? I didn't found any problems yet.
Sorry for my bad English
Click to expand...
Click to collapse
General rule of thumb is to back up your user apps and data, but do NOT restore your system settings(data).
Wraith04 said:
I love 4.5 but I have one problem, bluetooth does not want to pair with my Ford sync system, any suggestions or changes I can make? I have tried every thing I can think of but it will not find my phone.
Click to expand...
Click to collapse
Are you able to pair the phone with other bluetooth devices? I'm not familiar with Ford sync or the process for pairing with one... could you describe briefly the normal steps you take to pair to it?
dstewart4520 said:
I am new to the droid phone, and i have flashed my phone to froyo 2.2. I really like to go to the phoenix rom but have a few questions.
1. I am a very visual person and was wondering if there are any videos on how to install phoenix to captivate phone.
2. I looked at the options for phoenix and still did not see if phoenix supports playing call through car speakers, which is why i'm changing roms in the first place.
3 Which phoenix version would be best suitable for a noob.
Click to expand...
Click to collapse
Just to be clear... you've already flashed your Captivate to a 2.2 ROM? If so, which one are you on currently?
1. I don't know of any videos specific to flashing phoenix, however there are videos available on the forums that demonstrate the flashing process (which you've apparently already done once). The process is fairly straight forward even when just following written instructions.
2. Are you talking about playing your call via a built in phone system (such as the previously mentioned sync?)
3. All the Phoenix ROMs have been solid, so I would always recommend going with the latest.
circuitjerker said:
ok so im a bit of a novice flash whore but ive not seen this , i downloaded Pr 5.2JS5, then upgraded the new "c' kernal, all doing well except i cant get the tts.apk to install (stole it from FF 2.2), (ohwell) but i changed my bootani to the new "ashes" via renaming and putting in system/media (overwrite).. now i have nothing....its pauses with a black screen for the alotted time as is there would be one, then it loads the home screen. i tried to revert to the original one by downloading it from -hq , but same result ... did i screw up?
EDIT: This Q&A is a nice touch , i read the hell outa the dev forums, but still have some basic questions now and again .. Thanks!!
Edit: so i pulled the original Bootani from the system/media from a copy on my pc and reapplied it and it works , there may be an issue with the compatability of the "add ons" boot animations at phoenix-hq and the current version "5.2' at the moment , so i guess patience is in order....still having force closes after applying the ttsservice.apk to the rom from other roms..... force closes.
edit: so i hope this helps someone else cause its makin me look like an idiot....the file need for the "Voice input/output" in the settings to stop FC's is "PicoTts.apk", i stole it from the "PR 5.2 JSY" and placed it in the "PR 5.2 JS4"...works fine now! .. but i hear that "adam" isnt going to be supporting the JS4 build any longer....sheesh. lol
Click to expand...
Click to collapse
I haven't totally ruled it out as there are small differences. Who knows, I am working on my new ROM Orange Chicken, ATM.
JoeDV said:
Just to be clear... you've already flashed your Captivate to a 2.2 ROM? If so, which one are you on currently?
1. I don't know of any videos specific to flashing phoenix, however there are videos available on the forums that demonstrate the flashing process (which you've apparently already done once). The process is fairly straight forward even when just following written instructions.
2. Are you talking about playing your call via a built in phone system (such as the previously mentioned sync?)
3. All the Phoenix ROMs have been solid, so I would always recommend going with the latest.
Click to expand...
Click to collapse
I'm on Froyo.ucji6 currently.
I'm also having trouble with my droid explorer. Do i really need that to flash or can i use something different. And just to let you know i really do appreciate you taking the time to help a noob out, really. I have researched this but everytime i have tried it, it does not work. I think i have messed up my vcard cause i'm getting an error when trying to import contacts to my phone so i'm just trying to find the easiest way to do this. So thanks now, thanks later for your help.
i downloaded and have been running asops 2.2 rom but i just changed my phone number with sprint and I cant figure out how to update the msid. obviously sprint cant help me since im not using stock rom. anyone know where to look or an app i can download, because under settings: about phone: phone status: shows my old phone number, and i cant make calls or send msgs because of it.
they kept giving me ## codes but they wont work it just tries to dial the number.
Sorry woulda responded sooner, been busy. You need to flash a sense rom to use dialer codes our have sprint modify the phone or account info tied to it.
ugh... ok can you recommend a quick and simple rom so i can do that real quick
hate flashing it takes forever without a highspeed usb. anyways, downloading a sense rom now. thanks
arrg! ok i downloaded and flashed over to herocs 2.2 sense rom, tried doing the ## codes and nothing happens.
anyone??? im kinda screwed here.. cant use my phone until i get the prl updated
If all you need to do is update prl, and you have a sense rom flashed, you can do that from phone settings. I believe it is under "about phone".
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
user7618 said:
If all you need to do is update prl, and you have a sense rom flashed, you can do that from phone settings. I believe it is under "about phone".
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
Click to expand...
Click to collapse
it should be, but its not. under about phone, this is what i have :
network
phone identity (no update option)
battery
hardware information
software information
legal information
MyHerox25 said:
it should be, but its not. under about phone, this is what i have :
network
phone identity (no update option)
battery
hardware information
software information
legal information
Click to expand...
Click to collapse
Just use LiquidSense to update it.
what is liquidsense?
this is the rom i flashed to for temporary purposes
It is a 2.1 Sense ROM that can be found in the Development section.
well i guess no need to worry about this anymore, the charging dock on my phone is now broken or something because nothing will charge my phone.
Try a different battery. Or a different usb cable.
Root/Hack-Mod_Always*
ok i was in panic mode earlier being without my phone and all...
got liquidsense, updated all info. all good there. however when i flashed back to aosp rom its suddenly really glitchy, i cant get passed the "touch the android" set up screen!
attempting to reflash and see if that helps any...
nope....man this is a nightmare. btw gave thanks to everyone who replied in this post.
well... i flashed back to LS and even that one glitches out at the set up menu. so im still nowhere with my phone.
**UPDATE**
i found a backup copy of aosp rom that i originally downloaded in another folder on my sd. everything is working just fine now couldn't have done this without your help (all of you)
MyHerox25 said:
well... i flashed back to LS and even that one glitches out at the set up menu. so im still nowhere with my phone.
**UPDATE**
i found a backup copy of aosp rom that i originally downloaded in another folder on my sd. everything is working just fine now couldn't have done this without your help (all of you)
Click to expand...
Click to collapse
Glad you got it up and running.
First Just for your future reference so your not crappin all over yourself.lol (Been there) If you haven't already make a nadroid of the LS Rom or sense Rom that you used.
Second,I believe alot of the people around here that flash between sense and CM and AOSP do a factory rest or wipe from fastboot(look in this guide for instructions on this http://forum.xda-developers.com/showthread.php?t=1063843 by forum memeber il Duce )the reason being is that (from what I've read) is that sense roms leave bits and pieces of files behind that can corrupt a flash,or make you phone wonky after it boots up.
P.S. If you ever have to RUU or unroot when you re-root makea nandroid of that after you root and keep it some where safe so you can go back to it.
Yes, wipe data, cache, and dalvik every time you change roms. Especially between sense and aosp. The only exception us when flashing an update to the rom you're currently running. Even then, it may require a cache and dalvik wipe. Wipes are not necessary when restoring a nand. Also, keeping a sense nand is a good idea, as out makes it quicker when prl updates are needed.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
My title was abit too long, cause it was copied from a reddit post I made on Cyanogenmod's reddit. R/s means "Receive or Send"
I tried going to Cyanogenmod's Reddit, asking for help with this issue, but there was no luck at all, one user did respond to me and tried to help me out, but hasn't responded for the past 3 days. Looking around for more help, I was directed here to ask. If at all, I'm doing something wrong, can you please tell me.
FYI: My Nexus 6 is using Cyanogenmod 13.0 NIGHTLY, running 6.0.1
Besides that, the reddit post is basically this:
"Please direct me in the correct area, at the moment I don't see much to go to for some help, but I felt like making post.
After a while, I've been using Bell Canada on my phone without any issues, but I never tried voicemails or calls. Recently, trying to get into my telegram account cause they won't send a SMS (For what ever reason), the app offered to call my phone, waiting for the timer to tick down before they call my phone, it just shut it's self off.
I was aware of my phone crashing due to voice mails, cause before I activated my sim card, I had a voicemail that wouldn't go away, trying to view it, the phone would crash. I was hoping this would've been fixed after a couple updates, but it doesn't seem like it was fixed at all. I can't even tell if this issue is my problem (the phone/sim card) or cyanogenmod.
If anyone knows any fixes for this, I'd be really happy, because currently my phone is useless to most things I'd use it for, other than SMS."
On the reddit post, the user that was replying to it did mention something about c-apps not being compatible with Cyanogenmod 13.0 and told me to try to uninstall it, but when I tried to uninstall it through adb, apparently such a directory doesn't exist. I do hope I can get some help here, because I'm currently on a plan with unlimited text and calls, paying alot of money for it, but one feature is completely useless.
--Something I want to add, I tried the same sim card in my HTC One M7 running Android 5.1 with Cyanogenmod 12, calls worked perfectly fine with it.
Please do correct me if I'm doing something wrong, but reading the forum rules, I don't see anything about "bumping", so... Here's my bump.
I haven't had a reply for 5 days now, the possible answer to why my topic wasn't replied to, is most likely because noone knows how to fix this or why this might be happening.
But, I do wish I could get a post or something to show that people do see this, or maybe a post telling me that my issue has a unknown fix.
Edit; I see this rule #5, but, I don't know if that applies to bumping, I don't know how else I could explain my issue. I've explained it the best I've could.
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Darth said:
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Click to expand...
Click to collapse
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
Look in the Nexus 6 Android Development and Nexus 6 Original Android Development subforums, there are tons of options available.
Read over this- [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. A brief guide to clean flashing ROMs. Using TWRP, wipe everything except internal storage (system, data, cache, dalvik). Flash the ROM and then gapps package (some ROMs based on stock don't require gapps so look in the thread). There you go, you have a clean flash of a new ROM.
If you have issues with CM13, try ROMs based off of AOSP like Chroma, Pure Nexus, Dirty Unicorns, AOSiP, etc...
Darth said:
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
Click to expand...
Click to collapse
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
MoonieHorse said:
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
Click to expand...
Click to collapse
You will not "brick" flashing a rom. You can have issues, sure, but that's what the nandroid backup is for.
Honestly, if you're that worried, I'd restore the stock image and not tinker with it.
But if you leave it as is, I doubt you'll fix your issue.