Installed the Gingerbread update that was leaked last week and packaged into a zip file (along with new radio). Everything went smooth, everything's running fine and pretty damn snappy too, I'm loving it so far. Only one issue, and it's an annoying one cuz I use it all the time: Google Talk is not working; in fact, it force-closes every time when trying to open it.
Anyone else encountering this and if so, is there a fix? Thanks!
I saw other people were having problems with it too.
Related
Hey Guys,
Bell has released a new ROM 1.17.666.1, Radio 1.59.10
http://www.howardforums.com/showthread.php?t=1301200
I will be trying it this week and report any changes.
Kewl. But I heard nothing has changed on this one except the ROM and Radio numbers...
Anyone tried it and seen anything different?
So far users have reported that it runs smoother and faster than the previous ROM.
No other changes have been noted yet.
I wish there was an official changelog!
shifty646 said:
So far users have reported that it runs smoother and faster than the previous ROM.
Click to expand...
Click to collapse
That can't be accurately verified because users were comparing the fresh, clean new ROM to their old ROMs with all their extra apps loaded in.
We will have to wait and see if there's a continued consensus of this once more people install it. I never install Firmware/ROM updates right away, I always wait to see if there are any unforeseen problems or incompatibilities.
im the op of that post
Nothing to report on in terms of the rom. I guess battery life with the battery life tweaks is good as long as I don't stay on messenger
Freezes improovement
I just read that we should not experient voice call freezing with this rom... So far, it works !!
There have been many reports of in-call freezing with the new ROM on HoFo.
I have personally experienced freezing with the new ROM as well.
Seems like the issue happens when the phone tries to establish a data connection while in-call.
well, i had in call freezing with the old rom. i have in call freezing with this rom, however not hear as often as the original shipped rom. this rom does seem to be better at memory managment though.
I checked my phone and it already has the same ROM and Radio as the new update. I bough my phone around Dec 29, 07. So I guess I don't need to update it yet.
I used it..
I just updated to the most recent bell winmo 6.1 rom last night, and after hassling with Verizon for 45 min to get my phone re-authenticated, I discovered the picture messaging feature is gone. Anyone have any ideas? Also, I do really like the i-phone style txt conversations.
I just wanted to share some info here in case anyone else was having this problem. I installed a Kenwood KIV-700 with the KCA-BT300 bluetooth addon. It connected and paired with the phone just fine, however, I noticed that I could not get contacts to sync, tried deleting and reconnecting the phone from head unit several times. Then it occurred to me that it could be my ROM (was using CM6 RC1 at the time). I flashed to AVA-FROYO6, thinking that maybe since it is closer to the stock ROM, that the phonebook would sync. It worked and now I am completely syncing with the unit. To be fair, I have not updated CM beyond RC1, as I was happy with it, so didn't feel the need to update to 2 yet, so maybe this worked in the later version.
My guess is that Kenwood works off of stock ROMS and this could be the reason that CM6 did not work completely with it. Anyway, hope this helps someone.
Cool I've got that BT add on sitting in the garage awaiting my install.
Thanks.
dougdascenzo said:
I just wanted to share some info here in case anyone else was having this problem. I installed a Kenwood KIV-700 with the KCA-BT300 bluetooth addon. It connected and paired with the phone just fine, however, I noticed that I could not get contacts to sync, tried deleting and reconnecting the phone from head unit several times. Then it occurred to me that it could be my ROM (was using CM6 RC1 at the time). I flashed to AVA-FROYO6, thinking that maybe since it is closer to the stock ROM, that the phonebook would sync. It worked and now I am completely syncing with the unit. To be fair, I have not updated CM beyond RC1, as I was happy with it, so didn't feel the need to update to 2 yet, so maybe this worked in the later version.
My guess is that Kenwood works off of stock ROMS and this could be the reason that CM6 did not work completely with it. Anyway, hope this helps someone.
Click to expand...
Click to collapse
Well back to the drawing board. Eventually I got the same Hf-68 error again with Ava's ROM. Then I went to CM6 (release version this time) with King's first CM6 kernel and it worked for the entire time I ran that (about 3-4 weeks). Then i started having some unrelated issues so I decided to try Virus's new sense ROM based off of 3.28 leak release (RC2) with King CFS7 and low and behold I get the error again every time during the point when it is downloading the phonebook.
I am going to try Virus's senseless when he finishes uploading it and try that. I wonder if it has anything to do with the sense contacts...
So frustrating when you buy an expensive piece of equipment and it works so inconsistently.
Hey guys,
I've clicked around a bit but can't seem to find anyone with the same issue, and I went through about 40 pages on Calkulin's ROM but I really don't want to go through all 200 and some if somebody here can provide a solution.
I've used his ROMs for the past year, really fantastic, no complaints at all. I flashed his beta ICS build a few months ago and it worked well with the exception that it would randomly reboot for no apparent reason. I could be in the middle of a text message or it could be sitting on my desk and all of a sudden, reboot. I went back to his old ROM and decided to put off ICS for a few months to work out the bugs. Today I put his newest ICS ROM up and once again, random reboots. It doesn't seem that others are having the same problem so I'm not sure what to make of it. And for the sake of putting it out there, it's always a clean install - Format All, flash modem and ROM.
Anybody have any ideas? Suggestions? Any help is seriously appreciated.
Thanks guys.
Ive heard of someone else having this issue before have you tried a fresh install with a new download of EL29 or EL26? When i have had issuez in the past that could be the culprit try a new download also you could try one of the new kernals posted that may help as well.
Sent from my SPH-D710 using XDA
Are you using 4g?? This is a known issue with leaving 4g enabled.
Sent from my SPH-D710 using XDA
It is a known issue that if the hacked Hotspot is installed and you are running on 4G that you will experience random reboots. Mijjah74 has implemented a fix for it in his ROMs and it is beginning to go out among the other developers as well.
Until your developer implements the fix the cure is to not use 4G.
Awesome, thanks a ton. What a goofy bug. Yes I frequently use 4g, hourly even, and although I rarely use the hot spot, it is installed. I wonder if un installing it would fix the issue.
Thanks again.
Any idea if using am older modem would fix it?
iJoshh said:
Awesome, thanks a ton. What a goofy bug. Yes I frequently use 4g, hourly even, and although I rarely use the hot spot, it is installed. I wonder if un installing it would fix the issue.
Thanks again.
Any idea if using am older modem would fix it?
Click to expand...
Click to collapse
No, reinstalling won't help. I was testing 4g for this and (for me at least) it would reboot at about exactly the 1 hr mark if 4g is running constantly. Pretty strange but it did it several times in a row that way. I think someone said that they have the timing down pretty well and I can't recall exactly what the recommendation was, turn 4g off and back on right before it's going to reboot (you should time yours to see when it does it). Something like that.
Addendum: FYI, I'm running stock EL29 modem. A different modem won't change the 4g reboot issue either, sorry.
I had random reboots on every ROM. I went all the way back to stock unrooted, and started back over. Haven't has any issues since.
Sent from my SPH-D710 using xda premium
So about 4-5 months ago, I became frustrated with the GPS woes on my otherwise perfectly operational Evo 4g and went ahead and bought a "refurbished" Epic 4g instead. I miss my Evo 4G like crazy and with work slow for the next couple weeks, I decided to revisit the issue to see if i can maybe fix the problem and re-activate my Evo 4G.
I am a relative n00b but know enough to have exhausted every possible solution I could find using the "search" function. GPS Status AGPS resets, ##GPSCLRX# fixes, as well as pretty much every single driver fix listed here: http://forum.xda-developers.com/showthread.php?t=1132412
thinking back to when the issue began, I think what I did was install a CM7 AOSP ROM over my then stock-rooted ROM, when the GPS didn't work, I kinda freaked out and nandroid flashed back to what i had before but the GPS issues persisted.
I thought about unrooting completely back to stock but if the GPS is the only thing not working, I'm wondering if that would even fix the problem.
It could be a kernel issue perhaps? I'd be more than happy to provide any info/screenshots/logs that might be helpful.
Any thoughts/suggestions would be very very much appreciated
*Edit : in the time since I made the post, I decided to follow this thread and install everything anew, ROM, kernel, GPS drivers/fix (AOSP all the way, CM7 + Savagezen + CM7 N39 Driver ). Still nothing with the GPS, the GPS Status app just will not lock on to a satellite.
ankur079 said:
So about 4-5 months ago, I became frustrated with the GPS woes on my otherwise perfectly operational Evo 4g and went ahead and bought a "refurbished" Epic 4g instead. I miss my Evo 4G like crazy and with work slow for the next couple weeks, I decided to revisit the issue to see if i can maybe fix the problem and re-activate my Evo 4G.
I am a relative n00b but know enough to have exhausted every possible solution I could find using the "search" function. GPS Status AGPS resets, ##GPSCLRX# fixes, as well as pretty much every single driver fix listed here: http://forum.xda-developers.com/showthread.php?t=1132412
thinking back to when the issue began, I think what I did was install a CM7 AOSP ROM over my then stock-rooted ROM, when the GPS didn't work, I kinda freaked out and nandroid flashed back to what i had before but the GPS issues persisted.
I thought about unrooting completely back to stock but if the GPS is the only thing not working, I'm wondering if that would even fix the problem.
It could be a kernel issue perhaps? I'd be more than happy to provide any info/screenshots/logs that might be helpful.
Any thoughts/suggestions would be very very much appreciated
*Edit : in the time since I made the post, I decided to follow this thread and install everything anew, ROM, kernel, GPS drivers/fix (AOSP all the way, CM7 + Savagezen + CM7 N39 Driver ). Still nothing with the GPS, the GPS Status app just will not lock on to a satellite.
Click to expand...
Click to collapse
there might not be a fix. i once did something similar of flashing a rom over another rom and my gps also stopped working so i got another evo
alexandroid5 said:
there might not be a fix. i once did something similar of flashing a rom over another rom and my gps also stopped working so i got another evo
Click to expand...
Click to collapse
that would be very sad indeed. Did you try going back to stock completely (unrooted) to see if that would help? that's the one thing i've not tried and I guess i'm just wondering if anyone thought/knows whether that would make any difference in this case.
(in the meanwhile I flashed miui's ice cream rom on the evo 4g using it mostly as music/media device and it's so freaking gorgeous...looks like i'll have to go get an S3 after all)
Ive looked everywhere for a solution but cant seem to find one. My N7, currently running CM11, will randomly reboot for seemingly no reason. Sometimes i can go a day or two and nothing but just when i get comfortable, BLAM! Im not particularly worried just frustrated. I dont know what to do and I have read that its sort of common whether stock or custom(ROM). Im debating on trying to revert to stock because i cant seem to remember having this problem before CM, but i really cant be sure. Id rather not revert to stock if im just gonna have this issue but if it seems to work for others then id just go stock. Anyway I guess im saying that I need some advice here on what others experienced or think. Has reverting to stock worked for anyone else? Any other advice/insight would be greatly appreaciated!
-Thanks
The fix is coming, when Google releases Android 4.4.3, by the end of the month.. Sit tight
--=={BSnapp} ==--
My stock N7 reboots randomly from time to time. It might go a week or more then reboot twice in one day. No apparent pattern to it.
Sent from my BN Nook HD using XDA Free mobile app
I am experiencing precisely the same issue described in the OP. So I am also pretty interested in knowing if there's a fix.
@BSnapp, how can you be so sure of that upcoming fix? Is there a known issue with 4.4.2 for the N7 that was resolved for the next version? Any sources worth mentioning?
Thanks.
It's all over the Android news sites that Google is including a fix for the random reboot, plus several other fixes.. Just Google Android 4.4.3 update, and you will find the answers you seek...
--=={BSnapp} ==--