Im currently using CM 7.0.3 and the GPS is pretty much useless. Does it work well in 7.1 or in any of the nightlys? Also I see that the nightlys stopped in the download page, just end of life for the N1?
I'm on CM7 nightly, my GPS is always good.
Do you use GPS Status and Toolbox? It's a good app that download GPS data
to help for faster lock.
+1. What BBF said ^. Using 7.1 myself.
Sent from my Nexus One using XDA App
After reading your title i started to think about when was the last time i had a phone that got a GPS lock in under a minute with no extra apps. The last time i can remember is when i had a my Mytouch 3g about 2 years ago. I had great GPS locks on CM when i had that phone but since (G2, G2X, nexus one) have all has horrible locks unless i download the GPS toolbox and even then it isn't very fast.
Has there been something in the last two years that would cause cell phones to lock GPS signal at a slower pace?
may be your area, but almost always and now on Nightly 253--almost instant locks
Lythandra said:
Im currently using CM 7.0.3 and the GPS is pretty much useless. Does it work well in 7.1 or in any of the nightlys? Also I see that the nightlys stopped in the download page, just end of life for the N1?
Click to expand...
Click to collapse
I haven't had any issues with my phone getting quick locks. And that is throughout my whole time with CM7 (and I never use GPS Status to refresh my agps data). When you upgrade to 7.1, I would highly recommend wiping the device completely including MANUALLY wiping the /system partition through recovery. Then install 7.1 and gapps.
You can back up apps and app data, but don't back up any system settings as restoring those could bring your gps problems back.
Oh, and the reason for no nightlies is the build machine for CM is having hardware problems (and there are no nightlies for any device, not just the N1). There is still life left with our N1
I'll probably upgrade the ROM this weekend. My GPS was great pre-CM 7.0.3 where I was using CM 6.xxx which is why I was asking.
Thanks for the answers.
I use CM 7 and it works well, it's really true that you can get a better signal with other mods?
Thanks
I downgraded to Enomther's last froyo mod a few weeks ago because I have no luck getting similar performance with any gingerbread mod. I've tried CM7,7.1,as well as a lot of the nightlies, Oxygen Mod, and stock gingerbread. The GPS performance just isn't anywhere near as good as on froyo, which is quite frustrating since I depend on it a lot. I've tried the GPS status app which helps occasionally, but it becomes a hassle if you constantly need to use it. :/
Still searching for a good gingerbread mod though.
Lythandra said:
I'll probably upgrade the ROM this weekend. My GPS was great pre-CM 7.0.3 where I was using CM 6.xxx which is why I was asking.
Thanks for the answers.
Click to expand...
Click to collapse
The reason is because CM 6 was based on froyo and CM 7 is based on gingerbread. Same reason my Enomther's mod works so well. There is a huge post on google's message board regarding the GPS problem in gingerbread, and they have claimed that a fix was released, but it never fully solved the problem I think it's fairly clear that the issue is with gingerbread and that any mod based on gingerbread will have this problem.
I haven't had any issues with GPS on my phone, and I have been running CM7 since the alphas started back in December (or maybe January). I have always had quick locks, and I haven't had it lose it signal while using it (and I use it frequently for both short and long distances). I use the 5.08 radio (but I have used the 5.12 as well, and had no issues with GPS while on it).
bassmadrigal said:
I haven't had any issues with GPS on my phone, and I have been running CM7 since the alphas started back in December (or maybe January). I have always had quick locks, and I haven't had it lose it signal while using it (and I use it frequently for both short and long distances). I use the 5.08 radio (but I have used the 5.12 as well, and had no issues with GPS while on it).
Click to expand...
Click to collapse
Very odd. So you'd say it performs equal to froyo?
I'm inclined to believe that it's not hardware related since, as i mentioned, on froyo it's near perfect -- close to instant lock, definitely within 10 seconds, and it never loses it.
I'm going to try another gingerbread mod soon because I miss some of the GB features. I'm also on 5.08. hmm
I would say it performs better than froyo, but it is probably just because my phone tends to run cooler, so I don't have freezing issues.
Make sure when you install the Gingerbread ROM that you MANUALLY wipe the /system partition from within recovery and perform a Factory Reset/Data Wipe. You can back up your apps and app data with a program like Titanium Backup, but stay away from restoring settings as restoring those could restore any incompatibilities between Froyo and Gingerbread. CyanogenMod recommends doing a full wipe when upgrading between Froyo and Gingerbread based ROMs (well, at least for their own).
My cm 7.1 works well
Sent from my Nexus One using XDA App
bassmadrigal said:
I would say it performs better than froyo, but it is probably just because my phone tends to run cooler, so I don't have freezing issues.
Make sure when you install the Gingerbread ROM that you MANUALLY wipe the /system partition from within recovery and perform a Factory Reset/Data Wipe. You can back up your apps and app data with a program like Titanium Backup, but stay away from restoring settings as restoring those could restore any incompatibilities between Froyo and Gingerbread. CyanogenMod recommends doing a full wipe when upgrading between Froyo and Gingerbread based ROMs (well, at least for their own).
Click to expand...
Click to collapse
Thanks. Works like a charm. Locking gps used to take at a least 10+ minutes, it now lock in less than 10 seconds. BTW using kang-o-rama 1.3 s2e version, which is based on CM 7.1.
P.S. was previously on same Rom before. I just did a full wipe without restoring any system data.
Sent from my Nexus One using XDA App
Try FasterFix
Code:
https://market.android.com/details?id=com.Double.FasterFix&hl=en
and select the server that is nearest to you to see if it improves.
Very odd. Tried a CM 7.1 based rom today, and the same GPS issue persists. I cleared the /system partition and everything else, but the GPS would not lock for one, and if it got a lock after minutes, it wouldn't stay locked. After restoring a backup to froyo, the GPS worked perfectly again.
And yes, I tried GPS tools, I tried fasterfix, but no go.
I'm on 7.1.0 and my GPS locks on within around 3 seconds.
zeesix said:
Very odd. Tried a CM 7.1 based rom today, and the same GPS issue persists. I cleared the /system partition and everything else, but the GPS would not lock for one, and if it got a lock after minutes, it wouldn't stay locked. After restoring a backup to froyo, the GPS worked perfectly again.
And yes, I tried GPS tools, I tried fasterfix, but no go.
Click to expand...
Click to collapse
I have been struggling with the same/similar problem ever since the2.3 upgrade.
The GPS doesn't lock for the first time, it gives up after couple of seconds ( no flashing GPS thingy ) and if locks it easily looses signal and never tries to lock again ( no flashing GPS sign ) unless I restart the app.
very annoying since since I'm using mytracks/sports-tracker to record my tracking/cycling.
is there any workaround? other than buying a new phone?
s.illes79 said:
is there any workaround? other than buying a new phone?
Click to expand...
Click to collapse
I think using a Froyo ROM is the only way certain way to fix the GPS issue but you have to be willing to sacrifice battery life.
I haven't heard anything about how GPS is on the latest ICS builds though, so maybe there is hope?
Stock, Cyanogen and Evervolv all support GPS on my Nexus One, it works fine on all of them. It's probable that you're chip's busted.
Edit: that's Evervolv ICS p13, by the way. Previous versions worked too.
Related
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
AndroidDeer said:
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
Click to expand...
Click to collapse
I have had CM7.0.2 installed for a few days now and have not had any issues with it. Did you wipe /system and /data before installing? It sounds like it could be a hardware issue if this is the case.
migrax
Dunno about the apps not running, but the wifi borking like that is a common problem.
You just have to "forget" your known wifi hotspots. I've heard people saying that forgetting just one will work. The one time it happened to me i just took them all out.
See sig...
My wifi works fine after installing 7.0.2 and the OC kernel, but the indicator in the notification bar no longer works. It shows zero bars no matter what. It's the same on two different brands of routers. No big deal though, just an aesthetic thing I guess.
I didn't wipe /system or /data, for whatever that's worth.
edit: forgetting the network and reconnecting fixed it.
I'm having the same issues...
Sent from my NookColor using XDA Premium App
I also noticed the same on 7.0.2. Perhaps is it is just aesthetics but I was noticing other minor glitches (simi clock fails and battery gauge) so fell back to 7.0 and things are moving along swimmingly.
One thing to keep an eye out for is that CM7.0.0 and 7.0.2 apparently dont like AES encryption on wifi. I had a hell of a time getting my wifi to work on my new nook as of Wednesday (omg so much fun) but once I switched my router to TKIP it works great. Kind of annoying, but a simple fix.
2.6.32 is coming *soon* and it allows me to build a new wifi driver. This will hopefully fix the AES issue that some people have.
phiremod's 6.2 has solved this wifi issue.....not sure what build he is using
AndroidDeer said:
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
Click to expand...
Click to collapse
I was in the same pain, but backed down one version to the nightly 55 release and it's been beautiful. Clearly they're working on the new version, since there hasn't been a nightly in about a week. I'm fairly new to CM, and it wasn't hard. Download the ZIP, boot into recovery - flash the ZIP, wipe cache and came right up. Do your backups (nandroid and titanium) just in case, as always. ;-)
I had same problem. Then I did install official Nook Color Stock firmware. Wifi works perfectly... So CM 7.0.2 has software based problem...
By the way, I have never used OCed setting...
nemir said:
I had same problem. Then I did install official Nook Color Stock firmware. Wifi works perfectly... So CM 7.0.2 has software based problem...
By the way, I have never used OCed setting...
Click to expand...
Click to collapse
I've never used the overclocked settings beyond what CM will offer.. the 925mhz. Considering going to the 1.1ghz since others are reporting that's stable.
But seriously - go to the 55 version of the nightly build. In my experience, the WiFi is FAR more stable than the official 7.0.2 release.
http://mirror.cyanogenmod.com/?device=encore&type=nightly
Thanks, worked as a charm
ylixir said:
Dunno about the apps not running, but the wifi borking like that is a common problem.
You just have to "forget" your known wifi hotspots. I've heard people saying that forgetting just one will work. The one time it happened to me i just took them all out.
Click to expand...
Click to collapse
had tried hard reset, multiples on/off of wi-fi
but forgetting one network did the trick
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Pinpong blockbuster rom - ticks all your boxes. Get faster fix from market.
Your gps will never be 100% satisfactory in the city, in fact it will probably always be poor - no matter what custom rom you use.
Halkus said:
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Click to expand...
Click to collapse
Have you think about CM7? Great Rom, works well on my phone, and add many new things.
Hi Mate, I tried many custom roms and finally settled for
(ROM)GingerCriskeloV77-9LS-CamHack- SIP + NoIncRing I9000/T/M JVP 2.3.4
Cheers
Well, I managed to get it on. Booting up is weird though, it looks for a long time as if the screen is broken, but eventually ti comes on to the Blockbuster lock screen and then everything is fine. It does seem faster - but I'll only really know when I get to one of those situations where I feel the phone is frustratingly slow.
Thanks very much Woolf!
Time allowing I'll give the other roms a shot, although this Blockbuster one does seem to be good enough for me.
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Halkus said:
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Click to expand...
Click to collapse
Check you got the installation right for that rom, maybe you had to flash a jvp stock first or some similar omission?
Sent from my GT-I9000 using XDA Premium App
Sorry to hear you're having issues. Try flashing to a totally stock JVQ first (with repartition) once you've backed up, then if you don't like that, try a custom ROM. I don't think many JVQ custom ROMs are worth trying if you want a taste of custom ROMs. Better to try CM7 or MIUI for something fast and different.
As a side note, the best tip I've seen for fixing the dreadful GPS we have with the i9000 is to buy a Nexus S or just ANY other phone! Yes, some radios appear better than others, but nobody can prove anything and it's almost all subjective feedback. A drop in the ocean of improvement needed for satisfactory function. If you must use it, a bluetooth GPS receiver and 3rd party navigation app seem the best way to deal with it.
I've now stepped away from Blockbuster. Even doing the a perfect install it crashed often and repeatedly. I did try upgrading to the very latest and that crashed several times in the past hour. Part of the problem was the rom starts with a lockscreen that has a messaging unlock on it, but it isn't set to an app that comes with the rom, so it reboots every time. Sadly that wasn't the only problem, as I was still getting loads of reboots.
So that's out of the way.
I'm now a lot more comfortable using Odin so I'll be able to try other options. I'll try the other two suggested in this thread first of all.
Next to test is CM7.
Thanks for the help folks!
CM7 aborted. Instructions are incorrect, the file they say to download doesn't actually match the instructions so that's out. Plus it clearly states it's not suitable for day to day use... so I don't thnk the time in working out how to fix it is justified since it looks like it wouldn't be useful.
I'm going back to the original question in the thread, to say that I'm looking for something stable. I now think that a custom rom is not the way to go. However some modifications may well be.
Can anyone suggest some kind of lagfix/speedup that isn't a complete overhaul like CM7, Blockbuster etc, that is very stable and that'll make my phone faster?
Edit : Part of what I was doing to install Blockbuster was install Speedmod kernel. So I've gone and put that on, and used the clockwork mod to root it, and also convert to ext4. I think things are looking pretty fast so far. I'm not sure if there's a lagfix for this, but I'm quite comfortable just now footering around - unlike the complete rom I don't feel out of my depth. So I think I'll be ok for now.
I'm really starting to miss the GPS rapid lock from my Thunderbolt. As soon as I'd start maps up that thing would pinpoint me in my bathroom. Since I've gotten this bionic, it won't even lock on me in my house and it's slow to do it even when I'm outside.
If you haven't tried it, TopNTP is a good app to try. It updates/changes the gps to use only addresses in your area to cut down on the fix time*. It's not instant like you referred to on your thunder bolt, but I've found it to help a lot in my case.
I'll come back and post a link if i run into one again.
Link to thread - http://forum.xda-developers.com/showthread.php?t=2198319
*I retract this statement. You can choose servers based on your location, but he advises this is not always best. Some times other servers are faster or more frequently updated for accuracy. He explains/understands better than I.
typed on a Bionic running Eclipse 1.3 on ICS build 232.
I think that helped a little. It locked on in a couple of minutes. The first time I tried it today.
A couple minutes is really slow, I couldn't say mines ever been that bad, unless of course i was in a position where i wasn't going to get a lock at all.
Just curious, what's your bionic running? Stock ICS, JB? Rooted, ROM'd?
chrisp6825 said:
A couple minutes is really slow, I couldn't say mines ever been that bad, unless of course i was in a position where i wasn't going to get a lock at all.
Just curious, what's your bionic running? Stock ICS, JB? Rooted, ROM'd?
Click to expand...
Click to collapse
IT's running the Carbon rom
There's not much else i could help you out with, unfortunately. I'm running the same setup as you, and usually get locks in about 15 seconds or less.
I've seen some people mention a free app called gps status i think. It can time how long it takes to grab a lock, and clear & grab new settings for the gps.
I haven't had a look at it myself, but it may be worth a shot if you get a chance. If i find anything helpful, or for some reason start needing to fix mine at some point, I'll pop back in
typed on my Bionic
Might have fixed itself. When I was in Rockford with my parents I uninstalled maps and reinstalled, next thing I know it was locking on instantly.
SuperSquirrel0129 said:
Might have fixed itself. When I was in Rockford with my parents I uninstalled maps and reinstalled, next thing I know it was locking on instantly.
Click to expand...
Click to collapse
If you run into this again, I'd recommend a couple troubleshooting tips.
1) Boot to recovery, wipe cache, wipe dalvik cache, fix permissions. Reboot.
If the issue persists
2) Force close Maps and wipe it's cache and data. You'll have to re-configure Maps as you like.
3) Download GPS Status & Toolbox. Download the GPS data in here before opening Maps or Navigation. This should get you quicker GPS fixes. It's free in the market btw.
I'm having trouble getting my gps to work on cm10.1, I restored a previous backup of 10.1.2 and it didn't work. I've dirty flashed, wiped everything and reflashed, cleared the cache & dalvik, gps status clear, rebooted to stock and it worked, and the gps worked before I installed the backup. Running the latest nightly. Any ideas?
Sent from my XT875 using Tapatalk 2
jethead102 said:
I'm having trouble getting my gps to work on cm10.1, I restored a previous backup of 10.1.2 and it didn't work. I've dirty flashed, wiped everything and reflashed, cleared the cache & dalvik, gps status clear, rebooted to stock and it worked, and the gps worked before I installed the backup. Running the latest nightly. Any ideas?
Click to expand...
Click to collapse
I had a similar problem I posted under CM10.1 ROM topic. What I ended up doing is I boot back to stock (Icarus, actually) and ran GPS Test app. Confirm the baby worked. Went Safestrapped booted back to CM10.1 (slot 1) and ran the same app and this time it worked. It's almost as if there's something "stuck" in the hardware despite using a different ROM.
I just say the lockon was quite a bit slower in the Bionic. My old Droid (original) locks on in about 15 seconds. Bionic under stock ROM locks on in 35-39 seconds, and CM10.1 locks in 43 seconds.
I'll try the recommended app and see if that helps.
Problem is intermittent. I tried that recommended top BTM app and did not see any noticeable changes I reverted back to factory and there are no changes noticeable either. The phone just sometimes refuse to see any satellites the GPS test app shows 0 satellites. If I reboot the phone the GPS make sure a few satellites brawl with low signal and it takes about 2 minutes to get a fix. This did not seems to happen under Ice Cream Sandwich.
Sent from my XT875 using Tapatalk 4
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore