tdm
Android Expert
Don't know about the slowness but it's a dirty flash so I'm not too concerned. I'm just happy that GPS works.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM] Quattrimus JB (CM10, AOKP41)
- Thread starter tdm
- Start date
-
- Tags
- lg spectrum
Don't know about the slowness but it's a dirty flash so I'm not too concerned. I'm just happy that GPS works.
nathanhaywood
Well-Known Member
Coming from V7 by way of CM10 b3 thru rc5, I'm getting a 10 satellite lock with 32 feet error tolerance per GPS Status.
Out of curiosity, why did you go with the GB blobs instead of the V7 ICS ones?
Out of curiosity, why did you go with the GB blobs instead of the V7 ICS ones?
nathanhaywood
Well-Known Member
Also, semi-dirty flashed from r4... wiped Cache only... and had no issues on first boot
The ICS blobs need to set a flag (most likely in NV memory) to turn on. This required people to flash stock ICS, turn on the GPS, and get a full lock before flashing CM10. The GB blobs do not have this requirement and as such, brings us one step closer to official CM support.
arty:
finndo77
Android Expert
CM10 RC4 GPS status indoors, seated, 10' or more from any exterior wall on the main floor of a two story plus attic.
1 second to lock at 29' 6 Sat of 21, have not used an app that uses GPS in her a week, since before upgrading from RC1. 22' lock after 6 seconds 10 Sat of 21, screenshot is lock after 30 - 45 seconds (not planned, I already took the 22' lock and was about to exit to post when I noticed the new lock.
This is not different than what I had on RC1, b5, or b3. But is way better than I had on ZV7 or ZV6
******Update
For fun I just went outside in the rain to see what kind of lock I could get outside, yes it is cloudy and raining. 20' outside with a clear view of the cloudy sky... again on CM10 RC4, but not unusual at all for me.
It was a 9' lock with 6 of 7 Sat, but by the time the screenshot took it had changed to this and even though I had 6/7 again, I could not get a screenshot quick enough before it changed.
While on CM10 b5 I had locks of 3' with around 10/16 or so Sat.
While I am glad to say my GPS works fine, for any who are envious, although I live in solid LTE coverage for more than 30 miles in any direction (plus or minus a few miles) I only get max speed tests in the 3Mb-6Mb range anywhere in my coverage area and have never gotten more than 1.2MB up or downloads. I'd prefer no GPS and faster LTE. Many places I only get 800Kb-1.8Mb speed tests while on LTE. I used to get that our better on Sprint 3g (Sprint does not cover my area with 4g or LTE, which is why I bought a spectrum)
1 second to lock at 29' 6 Sat of 21, have not used an app that uses GPS in her a week, since before upgrading from RC1. 22' lock after 6 seconds 10 Sat of 21, screenshot is lock after 30 - 45 seconds (not planned, I already took the 22' lock and was about to exit to post when I noticed the new lock.
This is not different than what I had on RC1, b5, or b3. But is way better than I had on ZV7 or ZV6
******Update
For fun I just went outside in the rain to see what kind of lock I could get outside, yes it is cloudy and raining. 20' outside with a clear view of the cloudy sky... again on CM10 RC4, but not unusual at all for me.
It was a 9' lock with 6 of 7 Sat, but by the time the screenshot took it had changed to this and even though I had 6/7 again, I could not get a screenshot quick enough before it changed.
While on CM10 b5 I had locks of 3' with around 10/16 or so Sat.
While I am glad to say my GPS works fine, for any who are envious, although I live in solid LTE coverage for more than 30 miles in any direction (plus or minus a few miles) I only get max speed tests in the 3Mb-6Mb range anywhere in my coverage area and have never gotten more than 1.2MB up or downloads. I'd prefer no GPS and faster LTE. Many places I only get 800Kb-1.8Mb speed tests while on LTE. I used to get that our better on Sprint 3g (Sprint does not cover my area with 4g or LTE, which is why I bought a spectrum)
1linuxfreak
Well-Known Member
tdm
Android Expert
You're the second to report weird issues after an update. I wonder if anyone can get a logcat of this happening.
PlayfulGod
Extreme Android User
tdm
Android Expert
well thats kinda of a crock of shyt, the prepaid models of the S3 got official nightlies on the jellybean (cm10) branch and will most likely get nightlies on cm10.1 eventually.
Give jeagoss a hollar about it.
Sent jeagoss an email, we'll see...
goatomatic
Lurker
First of all, this rom is so good! Thanks for making such a fast and stable rom. I am experiencing a weird issue, and I've looked through this thread and didn't see anyone else with this issue.
Sometimes when I boot the phone up, the cyanogenmod boot animation won't go away. The phone will go to sleep, and when I wake it up the animation is still playing. I can tell the phone is working underneath because when I press power + vol. down it makes the screenshot noise. Reboots don't seem to help, but if I flash the dalvik cache it forces the app update process and then it works fine. Is there anything I can do to fix this?
Sometimes when I boot the phone up, the cyanogenmod boot animation won't go away. The phone will go to sleep, and when I wake it up the animation is still playing. I can tell the phone is working underneath because when I press power + vol. down it makes the screenshot noise. Reboots don't seem to help, but if I flash the dalvik cache it forces the app update process and then it works fine. Is there anything I can do to fix this?
littlenanner85
Member
I get the same boot animation stuck on some reboots. If I turn my phone sideways half the screen shows other half Is boot animation. But it freezes as soon as I try to reboot. I have to pull battery. I'm using AOKP.
I had that issues this week. It progressively became worse until the phone wouldn't start up at all, if if the battery was pulled.
I was at a conference an needed my phone, so I pulled the battery booted into recovery, did a full wipe and re install of the rom. That got it back up and running until I got home. I saw version 1 was up so I did another wipe and install.
So far so good, no more incidents since the upgrade. Based on the degradation over reboots it must be something that is being corrupted in storage somewhere. I'm not an android developer so it's all speculation as to the root cause.
But yea, you're not the only one who had this happen.