Well I took the plunge last night and rooted and installed the Cynogen ROM and after some pretty tense moments everything worked!!
Only thing is Cherry Rplayer, a decent radio app I liked will no longer work: I get a "Sorry! The application Cherry Rplayer (process com.leadapps.android.radio.cherryrplayer) has stopped unexpectedly. Please try again. Force close" message immediately upon launch.
I searched for a similar app & found 'A Online Radio' (which looks exactly the same as Cherry Rplayer in the screenshots in the app store?) and it does the same exact thing.
Other radio apps continue to work fine such as 'NPR News'. I've also tried re-installing and still does not work.
What's up with that?
Thanks in advance
Did you flash with the latest version, ie, 5.0.5.2? One of the changes include
* Disable V8 in Webkit and switch back to JSC due to app incompatibilities
Click to expand...
Click to collapse
No, I used 5.0.5.1. But I just upgraded to 5.0.5.2 and launching these apps result in the same immediate force close message.
In case anyone else is having the same problem, I was able to find in another thread that fixing uid mismatches in recovery (THANKS jsapp & travon802!) solves this problem...
I'm having the same problem with Power Manager Pro (I bought it, so it's kind of annoying) and fixing uid mismatches didn't solve it.
Happens since CM5.0.5. I'm currently on 5.0.5.2
Related
Is there a resource somewhere that I can use to troubleshoot a potentially busted camera?
Using the stock firmware (RC29), on a fresh install, the camera and gallery apps crash with "Activity Camera (in application Camera) is not responding", with only an option to force close. 3 out of 4 times, the device reboots when I click FC.
I've also used Cyanogen (4.2.15.1) and SuperD (1.10.3), and in both cases, the camera app crashes with "The application Camera (process com.android.camera) has stopped unexpectedly. Please try again." Force close doesn't result in a reboot, though. Also, in these cases, the gallery works fine (I've uploaded some photos, and am able to view them without a problem).
In searching for solutions, I saw some suggestions to replace the existing Camera.apk with the original google one. I did give that a go, using 3 different versions -- one from JF 1.5, the one from DRC83_Defanged, and Cyanogen's (the current firmware I'm using). Both Cyanogen's and the DRC83 apks instantly crashed (process com.android.camera FC error).
On the other hand, the one from JF's package loaded, and had the camera icon appear in the top right corner of the screen, as if it could take a picture. The screen was completely black, though. Pushing the camera icon generated the FC error.
I haven't done any log checking while swapping out the different apks, but previously, the error log matched the problem occurring with "Issue 1037" on Cyanogen's google code page. (tried to link to it, but I haven't had the restriction removed yet.)
Are there any diagnostic tools or tricks that I can use to see if the camera itself is broken? I also have no problem physically cracking my G1 open -- I've already replaced the ribbon cable. I also double-checked that the camera ribbon was seated properly...it's a nasty one to get back in with my vision problems
Thanks in advance,
Nate
nphillips said:
Is there a resource somewhere that I can use to troubleshoot a potentially busted camera?
Using the stock firmware (RC29), on a fresh install, the camera and gallery apps crash with "Activity Camera (in application Camera) is not responding", with only an option to force close. 3 out of 4 times, the device reboots when I click FC.
I've also used Cyanogen (4.2.15.1) and SuperD (1.10.3), and in both cases, the camera app crashes with "The application Camera (process com.android.camera) has stopped unexpectedly. Please try again." Force close doesn't result in a reboot, though. Also, in these cases, the gallery works fine (I've uploaded some photos, and am able to view them without a problem).
In searching for solutions, I saw some suggestions to replace the existing Camera.apk with the original google one. I did give that a go, using 3 different versions -- one from JF 1.5, the one from DRC83_Defanged, and Cyanogen's (the current firmware I'm using). Both Cyanogen's and the DRC83 apks instantly crashed (process com.android.camera FC error).
On the other hand, the one from JF's package loaded, and had the camera icon appear in the top right corner of the screen, as if it could take a picture. The screen was completely black, though. Pushing the camera icon generated the FC error.
I haven't done any log checking while swapping out the different apks, but previously, the error log matched the problem occurring with "Issue 1037" on Cyanogen's google code page. (tried to link to it, but I haven't had the restriction removed yet.)
Are there any diagnostic tools or tricks that I can use to see if the camera itself is broken? I also have no problem physically cracking my G1 open -- I've already replaced the ribbon cable. I also double-checked that the camera ribbon was seated properly...it's a nasty one to get back in with my vision problems
Thanks in advance,
Nate
Click to expand...
Click to collapse
managerd any workaround?
im having the same issue right now!
shikhar623 said:
managerd any workaround?
Click to expand...
Click to collapse
yea any fix yet bro? i threw down my g1 for a really long time now i have to run back to it after three high end phones, i also forgot why i threw it down until now when i saw a photo moment. so any fixes?
I have this weird problem that only started occurring today.. If I open up the Market and update an app it will attempt to download & update the app over and over in a continuous loop. The only way I can make it stop is if I kill the Market app.
Figuring that something may have become corrupted I just did a complete reinstall and I'm still seeing the same behavior! I just updated an app and it download & installed 6 times repeatedly before I killed the Market app! So annoying!
Anyone seen anything similar? I'm at a loss at how to fix this, I've already reinstalled everything.
OK I'm beginning to think it may be a server problem, but it would be great if anybody could provide some input.
I posted a logcat on pastebin, it captures me waking my phone up, opening the Market and updating the app RepliGo Reader.
http://pastebin.com/UswHrLKK
I have highlighted a couple lines which I think are of interest, from what I can tell the app installs fine, then CheckinService sends a checkin request and receives the following error:
Got ApiException from async request: Error from backend. Request=com.android.vending.model.GetAssetRequest, Response=INTERNAL_SERVICE_ERROR
It's at this point that D/vending states there is a download pending and attempts to download/install again.
Any input is greatly appreciated.
Do a search, there are atleast 4 threads on this. One here.
Hey, just a quick question... has anyone been experiencing problems with the market? I have been running FROYO since day one, and apart from the crappy ''new apps2sd'', it's been running flawlessly. But here I am today, trying to install apps from the market, and each time i try to install an app, it says "installation of [...] was unsuccesful''. The weird thing is that the market was working perfectly yesterday and it suddenly stopped today... i did not modify anything in the configuration of the phone and for those who might think that i have a faulty wifi connection, i tried at 3 different locations, with the same results... any help would be appreciated, thanks!
Its not the market, its actually the setpminstalllocation that makes the apps store to sd. It the apps2sd problem.
Moved as not Android Dev.
I tried changing the installation location... same problem occurs
kassemalaa said:
I tried changing the installation location... same problem occurs
Click to expand...
Click to collapse
I get this with some specific apps (not using a2sd). One of them are "Earth live wallpaper". When installing I get the "installation unsuccessful" message in the notification drawer, and in Market I get a "Installation Error: Unknown reason -18" popup.
Hi,
Recently i tried to buy a flipfont from the android market. It showed me that the transaction could not be completed because of a network error. Yet the bill has shown up on my credit card. F%^% google checkout.
But that is the least of my problems.
After exiting the errored font installation, the market app seems to have screwed up. Everytime i launch it, it crashes with a message "the process com.market.vending" has crashed unexpectedly. And i have to force close the market app.
I tried rebooting the phone a couple of times but to no avail.
Please help. How can i fix this problem. Is there anyway i can reinstall the market application.
Thanks in advance.
Maybe its because the market is being updated.
http://www.droid-life.com/2010/12/10/android-market-receiving-major-ui-overhaul/#more-21727
Problem solved [i think so]
Hey, the problem seems to have been solved. I tried uninstalling an update to the market application. It wasnt the new update (overhaul) to the application. Maybe it was just some update which was buggy.
Anyways, now the market application is working. Whats more, it remembered my purchase of the flipfont and now i am able to use that font too.
I have rooted captivate. since yesterday I can't download or update anything from market. It keeps saying 'starting downloads' and happens nothing. Even sometimes it says your item will be downloaded but again happens nothing.
I use black market too. Does it make my 'market' fail now? I don't have a clue...please help me.
Hey try re flashing the rom you have and see if that works, its worked for me before.
Sent from my T-Mobile G1 using XDA App
myzenith said:
I have rooted captivate. since yesterday I can't download or update anything from market. It keeps saying 'starting downloads' and happens nothing. Even sometimes it says your item will be downloaded but again happens nothing.
I use black market too. Does it make my 'market' fail now? I don't have a clue...please help me.
Click to expand...
Click to collapse
Make sure the Google Talk services are running.
Steps to try:
1) Clear market data, retry downloads.
2) Depending on the rom you are on, Froyo build, you may not have a unique Android ID. If this is the case, download Android ID Changer and change the ID to something other than seen. Next time you flash stock, get your unique Android ID and write it down so you can use in the future.
Good luck.
I didn't get Froyo yet, and I just rooted in order to get the permission of installing apps freely. so I didn't do anything with roms. And I realized that Google talk is not working. I never played that app becuase I'm using kakaotalk. It says signing in...but nothing happens. How can I erase maket data then. I think I should have study more before rooting. How does goolge talk running related to market?
myzenith said:
I didn't get Froyo yet, and I just rooted in order to get the permission of installing apps freely. so I didn't do anything with roms. And I realized that Google talk is not working. I never played that app becuase I'm using kakaotalk. It says signing in...but nothing happens. How can I erase maket data then. I think I should have study more before rooting. How does goolge talk running related to market?
Click to expand...
Click to collapse
Both the market and Google talk use this service called
Google Talk Service (or something like that)
If you use a program that blocks startup programs make sure both google talk and its service are greenlisted. In addition try to stop using any task killers to see if that is the problem.
And the massage "Sorry! The process com.google.process. gapps has stopped unexpectedly. please try again." comes out from time to time with 'force close' button.
What does it mean?
myzenith said:
And the massage "Sorry! The process com.google.process. gapps has stopped unexpectedly. please try again." comes out from time to time with 'force close' button.
What does it mean?
Click to expand...
Click to collapse
I think it is tied to GMail sync which is also tied to the Google Talk service I believe.
I uninstalled apps have chances auto killing that process. They are one click lag, auto killer memory, but nothing changed after rebooting. Even the same error message came out as soon as rebooted. The odd thing is that that task is still running when i check with android hackers. How can I control the start up apps?
myzenith said:
I uninstalled apps have chances auto killing that process. They are one click lag, auto killer memory, but nothing changed after rebooting. Even the same error message came out as soon as rebooted. The odd thing is that that task is still running when i check with android hackers. How can I control the start up apps?
Click to expand...
Click to collapse
try using an app called "start up auditor"
Oh my Gosh!! I love XDA developers friends!! Thanks diablo, nbs !! I just found out other thread with same issue and fixed beautifully my captivate.
Here is what I did. I downloaded google talk services apps from here, and copy them to systems/app, and reboot. They are automatically downloading all the accumulated failed downloading after rebooting. I might have deleted some gtalk related apps by mistake. Hooray!!
Thanks all!!
myzenith said:
Oh my Gosh!! I love XDA developers friends!! Thanks diablo, nbs !! I just found out other thread with same issue and fixed beautifully my captivate.
Here is what I did. I downloaded google talk services apps from here, and copy them to systems/app, and reboot. They are automatically downloading all the accumulated failed downloading after rebooting. I might have deleted some gtalk related apps by mistake. Hooray!!
Thanks all!!
Click to expand...
Click to collapse
No problem! The same thing happened to me a while back because I accidentally startup audited the service.
i cant seem to make this work for me? but I am having the same problem..