Well, I'm having some issues this morning using GPS and Maps. I tried to start up Google Navigation which prompted me to turn on my GPS. I enabled GPS and went back to Navigation. The whole time I never received a GPS signal, gave it a good 20 minutes. So I decided to close navigation and just use the Maps app to find out where I needed to go.
When I opened Maps, it errored out stating I had no network connection which was false, as I could run a speedtest which confirmed 3G connectivity. I tried to toggle airplane mode which didn't work nor has a reboot. I've taken screenshots of said errors as I've never seen them in these 2 apps before. Other than that, I haven't had any other issues to this point.
This is the first time using Maps and Navigation on this ROM if that's any pertinent info.
ERRORS:
View attachment 59060
View attachment 59061
Thanks
I haven't seen this before, but I have seen install issues with Gapps. A few times when Maps or other apps that use maps was erroring out, it was because the google maps jar in frameworks was corrupt. I don't know why, but after looking at the file it was smaller than the one in the Gapps zip. So I copied to the correct place and everything worked again. I don't think this is the problem you are having but I have no idea what is happening. If the problem persists go to recovery and flash Gapps again. Sorry I can't be of more help, but you seem to be the only one to report this issue.
July 31st release is running great, but only problem is browser randomly closes.
How often does this happen? I have had a couple of apps do this but there has been no rhyme or reason and it is very random and also rare.
Last night's road trip got canceled so no testing of the GPS/Navigation...
Just wanted to report that I have had the Messaging app randomly closing like it was doing on the July 24 build, with seemingly no rhyme or reason, or pattern to it. Has anyone else experienced this issue? I just had the random thought that perhaps it has something to do with my settings for it, or even maybe that it's somehow related to me transferring my SMS/MMS messages with Titanium Backup. (Pro version 6.0.1, if that means anything to anybody.)
Before anyone asks... I do not restore the app itself, just the messages themselves.
I also use TI and use the xml to restore messages. I have not had the messaging app close on me at all. So it may be a memory leak and related to any other app doing the same thing. We all use our phones differently so while you may be getting the mms app closing somebody else is getting the browser app closing. It may be the launcher, I think I read somewhere about trebuchet issues with memory.
I am having huge problems with touch latency. For example: Sometimes when I enter a phone number it takes several seconds for the touch event to execute, which usually leads to duplicate numbers as hit it repeatedly thinking it registered nothing.
I have also been getting the random Roam of Death (RoD for short) where my 3G drops to roaming and does not recover until reboot or plane mode is engaged. This is without using WiFi what-so-ever (I have not switched on WiFi at all since loading this ROM).
The phone also flashes constantly when I hold it up to my ear during a phone call. I have not had any trouble with apps or GPS not working, though I admittedly use very few apps.
Just to head you off at the pass, I did a complete wipe before installing this ROM. Including Dalvik Cache. I do not use any recovery program to reinstall apps, I recover apps the long way.
Also, I used CWM 6.0.1.2
I have to ask which version are you using?
The JULY 31st release should have taken care of most of the latency issues, and also should have taken care of the proximity sensor. I may have not cleaned before I built so it may be using the kernel image from before I made the change back to the old CM9 proximity code.. If you would like to test this theory I have built a CM9 with the same setup that can be found in The BSydz Triumph Collection thread.
As far as the ROD, I have not gotten that since like 10 buids ago, so I can't do any kind of debugging. If you run in to this again do this:
open terminal and type su
allow root priv
logcat -b radio >/sdcard/radiolog.txt
Then PM me the log, or edit out your MEID and phone number, and post it. I say to PM me cause it wil contain all of your radio info such as phone number, MEID and stuff, so you don't want that to be public knowledge.
I think leaving WIFI ON prevents the roaming issue. I get these drops a lot too. I never get the issue when I leave my WIFI ON, although it drains the hell out of the battery. I believe the RoD problem usually occurs in areas of low signal so that's why some experience it and others don't.
Also I do recommend using CWM 5.5.0.4, it is more stable than 6.0.1.2.
I agree, only some people experience this.
As for the recovery, I use 5.0.2.7 on my good phone cause it is the most stable as far as backups and such go, Basically any recovery above that has issues with the correct filesystem being used when backing up and restoring. They back up froyo as ext4 and that will make the backups not load after restore. But I use 6.0.1.2 on my dev phone cause the option to sideload a ROM is one of the most useful options when reloading ROM after ROM. Other than the backup issue everything should work fine in any of the available recoveries.
hi been testing this rom for a week allmost in my opinion it is very sluggish the touch screen latency is almost unusable it shuts down at least once a day it is very slow overall.
thank you this is just my input ......thank you for all the work u guys do ..
Which version are you using? On the July 31st release, I have not had any shut down or hard reboots at all. I have only had one soft reboot, which is when the device resets to the PA boot logo, not the Moto logo. This is a RAM issue I believe. And was during a very ram intensive game.
I've turned off the following settings which IMHO have helped greatly with touch latency:
- System Settings > Sound > Vibrate on touch
- System Settings > Language & input > Android keyboard settings > Vibrate on keypress
BSydz awesome work on the 7/31 build!
I have been looking at the vibe patterns that are in our device files and they are all greater than stock, so this may be the issue. The haptic latency may be because the vibe is vibing too long and has to wait to vibe again. I can't promise this is the cause but sounds logical.
I was enjoying the snappiness of this ROM compared to the July 24 tester, but I am also having huge problems with the prox. sensor. The screen constantly flashes on and off (about once per second) while on a call. I may need to go back to an earlier ROM.
My phone has the auto brightness on and still strobes the screen on and off while talking on it.
The proximity sensor is in the kernel So if it was good before then you could try flashing the MAY 6th kernel to test the theory, and to get back just reflash the ROM and Gapps to get this kernel back. No need to wipe since it is the same system.
I havent been on this forum in a long time as I have moved on to the Nexus 4 running PA 3.69. My wife is still using her triumph. I previously ran cm7 on it. it ws getting sluggish so i cam back to see if there were any updates to that rom. It appears that development has stopped on that and you guys have moved on to PA. Awsome! PA is the future. you should see what they are doing with the nexus line of phones.
Anyway, i installed this rom (july 31 build) and her phone is gettting a wake lock of DEATH. android os will not sleep. after a few hours this morning her battery was dead. battery stats show that android OS has been awake for 7+ hours. any idea what might be causing this? Im about to factory reset and re flash the rom to see if that helps. any suggestions are welcomed
I have been getting great battery life and haven't even gotten to a point of looking at wakelocks. So any more details would definitely help. It may be an app, but I can't say for sure.
