Hello there,
So, I installed JPM, Root and CFLagfix with Autokiller. Everything works to my liking, and is snappy enough for me until Voodoo comes out.
But here is my prolem, and since this is a phone, it is a big problem.
I can make calls out no problem with great reception, and great call quality. But as soon as my phone recives a call, it vibrates once, and then I see a forced close, and I guess the dialer is crashing. The caller just gets one ring tone, and then they get hung up on as well. I get a notification that the network is gone, but about 1 second after I look at the notification, I get full bars again. It happens the same way every time.
Any ideas?
Edit:
I found the solution.
What I did was upgrade to Froyo, and then apply ALL my settings from Titanium back-up from my 2.1 ECLAIR back-up. I even applied system settings...and that is where the big mistake was. The two system settings aren't compatible.
So I actually went back to Android 2.1, and then used Kies to upgrade to Froyo. And I left the settings alone (and only imported apps from titanium), and everything works perfectly.
And I am digging this Froyo (with CFRoot and CF Lagfix)...it is as good as My 2.1 rooted and lagfixed, with some extra features.
Had (sometimes still have) almost the same problem, mostly on JPK. Since i flashed to JP6 its better.
Sometimes when i make or receive calls the phone apk crashes and the phone turns offline mode on by itself.
Dont know why.
I'm also experiencing this problem. Did you guys restore backups before it occured? I think it might has something to do with some theme that may not be supported in Froyo?
Really looking for an answer, cause this sucks!
Related
Some time after I upgraded to froyo, i started finding my phone switched to vibrate mode few times per day. I haven't touched anything, it just goes to vibrate without obvious pattern or reason...
anyone else?
p.s.
i've installed quite few programs since the upgrade as well, so cant be sure its froyo...
but dont feel like uninstalling one by one to locate the problem...
I'm running Froyo leak from day 1 and never occurd this issue. Froyo is running perfectly some problems with few apps but not that big. It has to be a app that you installed.
No problems here with things changing that I didn't change.
Not sure what exactly could be causing my issue.. I will point out it's probably not build related as I have been running Incubuses SuperE Cyanogenmod Eclair Beta 1 for a while and have had no call related issues.
Today I installed the superE beta 2, played around with it, then saw that Myn had released a new version of Eclair, so since I'm bored at work I figured I'd give it a try and see which I liked better.
I didn't try to make or receive a call after putting the beta 2 on there, so I don't know if it was working then or not.
My question is, could it possibly be related to some of the other files in the andboot folder?
Exact Install Steps:
replaced old androidinstall.tar with super E beta 2
rebooted phone, installed system on NAND, data on NAND, did not clear data
played around
replaced old andboot folder with the one provided in with Myn's most recent RLS1
rebooted phone, installed system on NAND, data on NAND, did no clear data
Any help or insight would be appreciated.
I have a bit more info that might be helpful.. My calls are showing in the call log as missed calls, but the phone never alerts me that there is a call coming in. I am now able to make phone calls just fine.
I've noticed that if I have ring vibrate turned on, it takes a longer time for the phone to ring. Try turning that off if it's on.
Incubus26jc also just released beta3 of superE with the Phone Prioritizer script. That seems to have helped me with ringer lag on my Vogue too.
It could be due to silly mistake. Make sure your ringtone is not set as silent. It happened to me a while back.
but even if the ringtone was set to silent, wouldn't the message come up on the screen saying I was getting an incoming call?
I'm about to try the vibrate thing and see if it works.. I'm running the beta 3 of the super E build right now.
didn't fix it..
Here's some extra info that may help.. My network status icon in the notification bar is 3G. When I call from another phone, I notice it changes to E for a second, and this is when the voice mail picks up. It then goes back to 3G after a second.
Effin weird.. I might try reburning the ROM and start with a fresh install.
well that fixed it. I reburned the latest eclair image and flashed Myn's most recent release and all is working..
Very odd.
CriMson - care to elaborate the steps you followed on the flashing and reinstall?
I'm having the same issue, but while running Donut. I believe I did a reinstall to the SD card as well and still had no luck getting calls to the phone.
Sprint HTC Hero
DarchDroid v2.8
Recovery: RA-Darchstar (v1.7... I think)
PRL: 60667
I bought this phone last week, rooted it, and attempted three or four different ROMs before settling on DarchDroid (which is awesome, by the way!). I was initially having issues with multiple FCs and it eventually became unusable until I read up that my device might not be able to handle the OC to 710mhz. I installed the OC widget and throttled it down and now it works like a champ and is still WAY faster than the stock 2.1 ROM. I am still having issues though, that hopefully, somebody can help me with or point me in the right direction. I've spent the last hour scouring almost all parts of the forum and can't find any answers to these issues. Forgive me if I looked them over...
1) All incoming calls go directly to VM. I can make calls and send / receive texts, but no incoming voice calls.
The next one is a two-parter...
2a) The phone will occasionally become so sluggish (borderline non-operational) that I need to reboot it. When I do, I clear the cache and it will reboot then function normally. Could this be a result of a widget that I have installed? (OC widget, battery monitor?)
2b) When I reboot the phone without booting into recovery (normal reboot) it goes into a continuous boot loop. When I try to restore my Nandroid, it still boot loops and I have to wipe and re-flash the ROM. Is this normal?
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
I had the same issue with the latest Fresh Rom so I ended up switching to Zen Hero and have never had a FC on an incoming call since. I tried all the fixes for Fresh and never had any luck. I would suggest trying another rom.
p.s. I was able to OC the rom also and it still works fine.
chromiumleaf said:
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
Click to expand...
Click to collapse
Thanks for the advice. I ended up biting the bullet and calling Sprint and it turns out all that was needed was a refresh on my account, the phone works like a champ now! I'm using the OC widget and throttled it down to 595mhz, and even OC'd that little bit, it still BLAZES when compared to the Pre that I came from. No hitches or waiting - when I open a program or app, IT ACTUALLY OPENS QUICKLY... an amazing concept!
One more question though: in case I need to reboot, is there a way to save all of my phone settings? I already moved all of my apps to the SD card so I don't have to download them again, but it would be really helpful if I could just load a save file that would re-set my settings to the way I had them before. Is there an app or setting in the ROM for that?
Make a nandroid backup through recovery. It saves every little detail of your phone and if you ever need to go back to that you can simply restore that backup. Titanium Backup is another popular tool but I've never used it myself so I don't know anything about it.
Before taking the plunge I am looking for success/problem comments from those who have failed with OTA and then tried the JH7_OTA.zip approach.
I have searched and I don't see many comments yet.
It flashed fine for me but now GPS is causing my phone to lock up. Happens if I turn off GPS and just now happened in google maps while driving. Had to pull the battery to reset.
Worked great for me. GPS is working like a champ too.
Thanks to all who worked so hard on the flash.
I updated with the JH7_OTA.zip and it went well, but my phone is worse than before... laggier, bottom buttons seem less responsive (could be due to the increased lag) and the GPS will not see any satellites and much less, lock. I'm sure it's not the file... just another defective unit. This is my fourth Captivate. First two simply lost the ability to connect to 3G and WIFI, the third had a great GPS but the search function would randomly self activate and the body creaked like an old rocking chair, and my current one.
bigdoug2005 said:
It flashed fine for me but now GPS is causing my phone to lock up. Happens if I turn off GPS and just now happened in google maps while driving. Had to pull the battery to reset.
Click to expand...
Click to collapse
This happened to me. You don't need to pull the battery. Just hold the up volume button and power button for about 10 seconds and the phone will shut off.
Edit Disregard my post.
It's working great for me. I usually stream radio during the day and it usually will drop out once or twice an hour. Today, it has been streaming just perfectly with no dropouts. Thanks to all of those that got this working!!!!
No problems here, either. I did remove my previously installed LagFix first, and I flashed over JH3. GPS seems to track me a little better than before, and it does seem that perhaps the radio is working a bit better and battery life is slightly better as well.
I have the same commute on the train each morning, and pretty much do the same routine each time, so that's a good way for me to compare things after a change. This morning I noticed that my streaming radio barely cut out at all in areas where the signal is low, much less than before, and when I got into work my remaining battery PCT was a little better than usual. I applied the RyanZ lag fix from the market this afternoon and overall am pretty happy so far!
My GPS is still jacked up.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Worked great for me. everything working including the 3 button, usb, and better gps/compass. Things other people were complaining about not working. I flashed odin and rooted with update.zip before i applied this rom.
luck? Sure... but...
I went with the Cognition ROM as JH7_OTA didn't do the trick for me.. All in all I like the Cog experience (install went smoothly, seems fast, no weird errors), but the GPS is definitely not fixed. Accuracy is better in that my phone can locate me on the neighborhood level, but it is still not locking and is locating me blocks away from where I'm actually at.
Worked great for me.
No problems flashing for me. That is the answer to your question, now to issues I had.
HSUPA was not working for me. So I did the revert HSUPA to get 3G back and it killed all data for me. So I did a nandroid back to my previous ROM and then I got FC so I had to Odin and then reinstall my nandroid. That is why I don't like his zip, it works fine but if you want to change ROM's you have to basically flash odin to make sure you have no issues. That is how it was for me, others might be different and then you have the nut swingers who are only for Cognition.
I will say this issue happened to me 3 times. I think the issue might stem from being unable to remove voodoo since it is packaged into his zip. Not positive why I had the issue but for the time being I am trying other alternatives.
Last edit: Just went back to his Cognition thread and see that he pulled the HSUPA zip, so it wasn't just me having issues. Unfortunately stuff like that lets me know that all in one package zips like that need to be worked on more.
flashman2002 said:
I will say this issue happened to me 3 times. I think the issue might stem from being unable to remove voodoo since it is packaged into his zip. Not positive why I had the issue but for the time being I am trying other alternatives.
Click to expand...
Click to collapse
you probably should have removed the voodoo lagfix to try to flash other roms since clockwork DOES NOT work with voodoo
alternatively you can install cognition, and install a different kernel if you dont want voodoo lagfix...
flashed it and it's great! except the gps is kind of on and off.
It has been a very long while since this is happening. I don't even remember if this was happening at the very beginning, in February when I bought it but it has been at least 4 months since I remember. I don't do much calls over the SIM network but I talk a lot over Messenger, Teams and Whatsapp. It is happening randomly but quite often. I can hear the other person's voice dropping like it simply dissappears suddenly. First I hear a few milisecond crack and then it dissappears for a second or two during Messenger. When I am doing Whatsapp calls it does the same and sometimes even drops the call and shows that I got Mic problems (Whatsapp shows that ). And when I am in a Teams call the phone might even reboot during talking. It is not hardware because when I was on Android 11 before the Update, it had similar problems but instead of rebooting the phone it simply freezes and makes a glitchy noise continuously until I reboot the phone. If I dont rboot it, The microphone simply won't work. When I am on a call via the Bluetooth Buds I don't have this issue. Both microphones work fine. The bottom one and the top ones.
It feels like it is the baseband....or whatever it is called... I don't want yet to put a cutom ROM as I lose the warranty. It is an Exynos version with 512 Gb space and I am looking for a solution first, and if I find out that a different ROM will fix this, I am OK but if I find out that it is hardware I would rather post it back to Samsung and get a replacement.
Many people like me here?
Found a small workaround. I installed an early version of the ROM via Odin and everything is working fine so far. So I assume it is Software/Hardware not just Hardware. I installed version G998XXU3AUE1 because you can't downgrade from Android 2 to an more earlier version than this. It has to do something with "3" after XXU which I think is the version of the baseband. We need Samsung to fix this so we can use the Phone with the latest ROMs... I did not test other versions asd this one works fine and the battery is even better than on newers ones. I actually missed the battery life from old verions to be hojnest, since the updates it could be noticible that it drains faster.
Another theory is that after installing Samsung weareble and starting using the buds that spoils the audio codecs ...I still didint connect it since flashed this ROM so after completing the testing with all calling apps I will put the Wearble again and see if it works.