In the past few days, I installed JFv1.31, wiped the phone, moved all my caches to the SD card, set up the phone&sdcard to run apps off the SD card, and installed a BUNCH of apps. Everything works great, except, oh right, the phone.
Whenever I get or try to make a call, the phone app crashes, with the error message 'The process android.process.acore has stopped unexpectedly. Please try again.'
Is there any reasonably simple way for me to figure out what's making the process crash? I'd really rather not have to rewipe the phone and redo everything I did.
Probably because you are messing with the filesystem. While it make work for some moving the cache and apps to the SD card has unknown longterm effects.
You may have just found the reason why most of us read the warnings and decided not to do such a risky procedure.
neoobs said:
Probably because you are messing with the filesystem. While it make work for some moving the cache and apps to the SD card has unknown longterm effects.
You may have just found the reason why most of us read the warnings and decided not to do such a risky procedure.
Click to expand...
Click to collapse
.......Yeah, that doesn't really make any logical sense. Linux doesn't care where any given part of the filesystem is, and if something works in the short term, then it works in the long term. It's not going to degrade on it's own. I'm reasonably sure that the problem is some kind of conflict with one of the apps I installed, but I have no idea how android is logging things, so no idea what log to check.
Plus, none of the core system apps are moved to the SD card, just the stuff installed off the market. And considering that reversing the process is ridiculously easy, it's not really a risky procedure unless you don't know what the commands do AND aren't careful about copying them over.
If you know what log to check to see what's happening immediately before the crash, great, let me know. If all you've got is 'zomg, I don't understand the filesystem and find it scary' then you're no help to me, but thanks for the....doom and gloom I guess.
And, ya know, if there is a problem with moving apps? (I'm sure the problem isn't moving caches, I'd had that done for months) How do you think the problem will get FOUND without people trying it, and then reporting on and troubleshooting the errors? Saying 'You had a problem, clearly you shouldn't have tried it' isn't going to lead to things getting better developed and more stable.
Some info on android.process.acore:
http://groups.google.com/group/android-platform/browse_thread/thread/87f075abebf2a557
You might also want to look for entries in logcat.
heldc said:
.......Yeah, that doesn't really make any logical sense. Linux doesn't care where any given part of the filesystem is, and if something works in the short term, then it works in the long term. It's not going to degrade on it's own. I'm reasonably sure that the problem is some kind of conflict with one of the apps I installed, but I have no idea how android is logging things, so no idea what log to check.
Plus, none of the core system apps are moved to the SD card, just the stuff installed off the market. And considering that reversing the process is ridiculously easy, it's not really a risky procedure unless you don't know what the commands do AND aren't careful about copying them over.
If you know what log to check to see what's happening immediately before the crash, great, let me know. If all you've got is 'zomg, I don't understand the filesystem and find it scary' then you're no help to me, but thanks for the....doom and gloom I guess.
And, ya know, if there is a problem with moving apps? (I'm sure the problem isn't moving caches, I'd had that done for months) How do you think the problem will get FOUND without people trying it, and then reporting on and troubleshooting the errors? Saying 'You had a problem, clearly you shouldn't have tried it' isn't going to lead to things getting better developed and more stable.
Click to expand...
Click to collapse
Excuse me?
I didn't give attitude just the fact that messing with the filesystem can cause errors. Many people have had SD card issues, SD card mounting/unmounting, corruption and just plain not working for various reasons.
So far we don't have enough information to find the problem. But these problems can cause other problems. If you keep your cache and apps on a SD card and it is unmounted randomly, or becomes corrupt, or for some reason just plain stops working this would cause corruption through the entire system.
If you used this guide http://forum.xda-developers.com/showthread.php?t=468959 then you have infact moved system data. Since the system apps do push and pull files from the /data/app* directories.
It is hard to figure out what logs you would need to check if you have moved things. The easiest way is to use ddms since that shows everything that has happened and is happening. But this may not help you. Give it a shot and post the part of the log in red and we can all see what is causing it.
Don't get mad that the problem might be something you did. We are trying to help. I gave you my suggestion, revert back to normal and stop trying to mess with the filesystem. If you don't like it that is great but that doesn't mean I didn't help.
neoobs said:
Don't get mad that the problem might be something you did. We are trying to help. I gave you my suggestion, revert back to normal and stop trying to mess with the filesystem. If you don't like it that is great but that doesn't mean I didn't help.
Click to expand...
Click to collapse
I'm not mad that the problem is something I did, I'm sure it is, that's why I listed what hacks I'd applied. I'm annoyed at the attitude you seem to have toward 'if there's a problem, that means you shouldn't have tried to mod in the first place.' That's not helpful, it just leads to people not trying things, not finding bugs, not troubleshooting, and not advancing the knowledge of how to work with this phone. Sorry to snap about it, it's just a pet peeve of mine, people trying to trouble shoot stuff and getting told 'oh that's risky you shouldn't have done it in the first place'.
I mean, the entire xda forum is for hacking and modding and developing. When someone tries a hack in full knowledge of the risks they run, and then they have a problem, come looking for trouble shooting help, and get told 'you shouldn't have tried the hack cos it's risky' that's just....against the whole idea of hacking your hardware!
did you run the sh script to change your app's caches ? if you did, please provide it here and we will see which lines you shouldn't run
I had the same exact problem. I had to wipe my phone and now everything runs fine again, for now.
namsir said:
did you run the sh script to change your app's caches ? if you did, please provide it here and we will see which lines you shouldn't run
Click to expand...
Click to collapse
I ran a slightly modded script. Maybe that is the problem, I did the cache moving manually when I did it before, and used the script this time.
Code:
chmod 0777 /data/local/bin/transfer.sh
mkdir /sdcard/cache
mkdir /sdcard/cache/files
cd /data/data/com.google.android.apps.maps
mkdir /sdcard/cache/files/maps
busybox cp -a files /sdcard/cache/files/maps
rm -R files
ln -s /sdcard/cache/files/maps/files files
cd /data/data/com.android.browser/cache
rm -R webviewCache
mkdir /sdcard/cache/webviewCache
ln -s /sdcard/cache/webviewCache webviewCache
cd /data/data/com.google.android.street
rm -R cache
mkdir /sdcard/cache/streetCache
ln -s /sdcard/cache/streetCache cache
cd /data/data/com.android.vending
rm -R cache
mkdir /sdcard/cache/marketCache
ln -s /sdcard/cache/marketCache cache
heldc said:
I'm not mad that the problem is something I did, I'm sure it is, that's why I listed what hacks I'd applied. I'm annoyed at the attitude you seem to have toward 'if there's a problem, that means you shouldn't have tried to mod in the first place.' That's not helpful, it just leads to people not trying things, not finding bugs, not troubleshooting, and not advancing the knowledge of how to work with this phone. Sorry to snap about it, it's just a pet peeve of mine, people trying to trouble shoot stuff and getting told 'oh that's risky you shouldn't have done it in the first place'.
I mean, the entire xda forum is for hacking and modding and developing. When someone tries a hack in full knowledge of the risks they run, and then they have a problem, come looking for trouble shooting help, and get told 'you shouldn't have tried the hack cos it's risky' that's just....against the whole idea of hacking your hardware!
Click to expand...
Click to collapse
I understand.
This goes beyond hacking thou. This has been said by quite a few that this just isn't good. It isn't stable and we aren't advancing it. Basically this has become a stale hack that will not be improved upon because there is no method to improve it. It is a hack that is unstable and sloppy. No offense to the finder but it is a crude fix.
Ok, I ran ddms, and made it crash. This is the output before I hit the call button, through the crash message and me hitting force close. I don't code, so this means next to nothing to me. I think I am going to be lazy tho, and just wipe. I'd like a working phone before going out tonight. Maybe someone can find something of some use in the log tho.
Code:
01-19 19:39:10.102: DEBUG/dalvikvm(90): GC freed 1541 objects / 74928 bytes in 96ms
01-19 19:39:22.522: INFO/ActivityManager(57): Starting activity: Intent { action=android.intent.action.CALL_BUTTON flags=0x10000000 comp={com.android.contacts/com.android.contacts.DialtactsActivity} }
01-19 19:39:22.942: DEBUG/dalvikvm(231): GC freed 2646 objects / 156288 bytes in 92ms
01-19 19:39:23.322: ERROR/ActivityThread(231): Failed to find provider info for call_log
01-19 19:39:23.332: ERROR/ActivityThread(231): Failed to find provider info for call_log
01-19 19:39:23.332: WARN/dalvikvm(231): threadid=19: thread exiting with uncaught exception (group=0x40013e28)
01-19 19:39:23.332: ERROR/AndroidRuntime(231): Uncaught handler: thread AsyncQueryWorker exiting due to uncaught exception
01-19 19:39:23.342: ERROR/AndroidRuntime(231): java.lang.IllegalArgumentException: Unknown URI content://call_log/calls
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.content.ContentResolver.update(ContentResolver.java:409)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.content.AsyncQueryHandler$WorkerHandler.handleMessage(AsyncQueryHandler.java:89)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.os.Handler.dispatchMessage(Handler.java:88)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.os.Looper.loop(Looper.java:123)
01-19 19:39:23.342: ERROR/AndroidRuntime(231): at android.os.HandlerThread.run(HandlerThread.java:60)
01-19 19:39:23.382: INFO/Process(57): Sending signal. PID: 231 SIG: 3
01-19 19:39:23.382: INFO/dalvikvm(231): threadid=7: reacting to signal 3
01-19 19:39:23.512: VERBOSE/DumpStateReceiver(57): Running: /system/bin/dumpcrash
01-19 19:39:23.522: INFO/dalvikvm(231): Wrote stack trace to '/data/anr/traces.txt'
01-19 19:39:23.752: INFO/ActivityManager(57): Displayed activity com.android.contacts/.DialtactsActivity: 1229 ms
01-19 19:39:23.922: INFO/DumpStateReceiver(57): Finished: 2282 bytes read; status 0
01-19 19:39:24.002: INFO/DumpStateReceiver(57): Added state dump to 1 crashes
01-19 19:39:28.363: INFO/Process(231): Sending signal. PID: 231 SIG: 9
01-19 19:39:28.393: INFO/ActivityManager(57): Process android.process.acore (pid 231) has died.
01-19 19:39:28.393: INFO/WindowManager(57): WIN DEATH: Window{431088a8 com.android.launcher/com.android.launcher.Launcher}
01-19 19:39:28.393: INFO/WindowManager(57): WIN DEATH: Window{4323db80 com.android.contacts/com.android.contacts.DialtactsActivity}
01-19 19:39:28.402: INFO/ActivityThread(241): Removing dead content provider: im
01-19 19:39:28.412: INFO/ActivityManager(57): Killing app com.google.process.gapps (pid 241) because provider com.android.providers.im.ImProvider is in dying process android.process.acore
01-19 19:39:28.412: INFO/Process(57): Sending signal. PID: 241 SIG: 9
01-19 19:39:28.482: INFO/ActivityManager(57): Start proc android.process.acore for activity com.android.launcher/.Launcher: pid=272 uid=10014 gids={3003}
01-19 19:39:28.482: INFO/ActivityManager(57): Process com.google.process.gapps (pid 241) has died.
01-19 19:39:28.492: WARN/ActivityManager(57): Scheduling restart of crashed service com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService in 5000ms
01-19 19:39:28.582: INFO/jdwp(272): received file descriptor 10 from ADB
01-19 19:39:28.712: INFO/ActivityThread(272): Publishing provider im: com.android.providers.im.ImProvider
01-19 19:39:28.782: INFO/ActivityThread(272): Publishing provider com.android.googlesearch.SuggestionProvider: com.android.googlesearch.SuggestionProvider
01-19 19:39:29.092: DEBUG/dalvikvm(272): GC freed 1702 objects / 115144 bytes in 96ms
01-19 19:39:29.252: DEBUG/dalvikvm(272): GC freed 421 objects / 30424 bytes in 76ms
01-19 19:39:29.552: INFO/ActivityManager(57): Displayed activity com.android.launcher/.Launcher: 1123 ms
01-19 19:39:33.512: INFO/ActivityManager(57): Start proc com.google.process.gapps for service com.google.android.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService: pid=281 uid=10000 gids={3003}
01-19 19:39:33.562: INFO/jdwp(281): received file descriptor 10 from ADB
01-19 19:39:33.652: INFO/ActivityThread(281): Publishing provider gmail-ls: com.google.android.providers.gmail.MailProvider
01-19 19:39:34.312: DEBUG/dalvikvm(57): GC freed 15232 objects / 765512 bytes in 216ms
01-19 19:39:35.232: DEBUG/dalvikvm(281): GC freed 4466 objects / 359648 bytes in 118ms
01-19 19:39:35.452: INFO/gmail-ls(281): MailCore.setConfig
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: included: 9/^r
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 2/^f
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 3/^i
01-19 19:39:35.452: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 31/info
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 11/lj
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 12/mysshop
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 35/work
01-19 19:39:35.462: INFO/gmail-ls(281): MailCore.setConfig
01-19 19:39:35.462: DEBUG/gmail-ls(281): MailCore.setConfig: included: 9/^r
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 2/^f
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 3/^i
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 31/info
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 11/lj
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 12/mysshop
01-19 19:39:35.472: DEBUG/gmail-ls(281): MailCore.setConfig: partial: 35/work
01-19 19:39:35.602: DEBUG/gmail-ls(281): Purging old attachments
I had trouble with acore crashing when I restored my contacts using mybackup. Deleting all of my contacts from the phone letting it resync them automatically fixed the problem.
It is trying to find something that isn't there, looks like call logs. The log to look at is /data/anr/traces.txt but you can't get to taht even with root.
i just had this same problem and all i did was move my caches to the sdcard and thats it. i understand a little of what i did in the process but i know i implemented the hacks that are tried and tested and known to not be able to brick ur g1. The most i have done with the contacts and call logs is applying the carbon glow theme to my g1 and thats it so could it be something with adding themes onto the g1 and something that might not have been done right in the zip files. im not saying that the person did something wrong with his theme but maybe themes just dont work fully in some parts of the os.
heldc said:
In the past few days, I installed JFv1.31, wiped the phone, moved all my caches to the SD card, set up the phone&sdcard to run apps off the SD card, and installed a BUNCH of apps. Everything works great, except, oh right, the phone.
Whenever I get or try to make a call, the phone app crashes, with the error message 'The process android.process.acore has stopped unexpectedly. Please try again.'
Is there any reasonably simple way for me to figure out what's making the process crash? I'd really rather not have to rewipe the phone and redo everything I did.
Click to expand...
Click to collapse
have u maybe installed mono after the install.. for some reason i think that messed me up the first time and time after that..
i installed mono for a short time and then unistalled it
I'm having the same thing happening on my g1, except it happens after i hang up a call. After it force closes, it seems to reload after a few seconds, and brings me back to the home screen. There's really no problems I can see, aside from the force close warning and the 5 second lag time to reload it, but it would be nice to get to the bottom of this. I can't remember if this happened before I moved the caches to the storage card or not, but I will perform a wipe and see if it continues. Can we confirm that this is due to the relocation of the cache?
Related
Hello everybody,
I keep getting this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
I can not acces my contact, gmail or the market.
It started yesterday but i didn't do anything special to have caused this error. Does anyone have an idea what to do?
Thanks for helping.
G1Dennis said:
Hello everybody,
I keep getting this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
It started yesterday but i didn't do anything special to have caused this error. Does anyone have an idea what to do?
Thanks for helping.
Click to expand...
Click to collapse
gmail error, I believe... uncheck autosync and recheck it and manually sync all. if that fails... remove battery while phone is on and sim. boot up and if that fails you may want to clear your mail via pc/mac while phone if off. Also, you can change the amount of days to sync mail and that should do it. Sorry I can't be more specific... that error happened to me months ago and I can't remember which one worked specifically.
Didn't work
Now i get a second error:
Your suggestions did not work yet.
SORRY!
The proces com.google.process.acore has stopped unexpectedly. Please try again.
Have you used any methods (symlink or the new one) to move your apps and cache to the SD card? If so, I suggest undoing the cache move and seeing if that fixed the problem.
What build are you coming from?
I ran into that yesterday. A wipe was the only thing that fixed it.
G1Dennis said:
Hello everybody,
I keep getting this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
I can not acces my contact, gmail or the market.
It started yesterday but i didn't do anything special to have caused this error. Does anyone have an idea what to do?
Thanks for helping.
Click to expand...
Click to collapse
definitely need more info .. what processes are done .. have you tried moving /data/data back to the phone? etc
this happened to me on saturday when i wasn playing around with the file system. it could simply be some corrupted files in dalvik-cache. try rm /data/dalvik-cache/* and then reboot (must do this thru adb, because everything will crash soon after rm). the phone will take sometime to recreate the files and then it should work fine.
edit:
if you're using a2sd, you should try move dalvik-cache back first.
sometimes a single app at startup will cause the "acore" crash. A couple of themes did that also. Yeah, we definately need more info... build name and number, plus a2sd or regular, theme or no theme, etc.
I was getting that same error and a wipe didn't correct it, my best guess was that the google apps file that contains the login info was still on my memory card from when i had moved /data to sd, and was confilicting with the same file on the phones memory. After deleting that file off the sd and a reboot it hasn't popped up since.
pgiuoco said:
I was getting that same error and a wipe didn't correct it, my best guess was that the google apps file that contains the login info was still on my memory card from when i had moved /data to sd, and was confilicting with the same file on the phones memory. After deleting that file off the sd and a reboot it hasn't popped up since.
Click to expand...
Click to collapse
and how did you do that, and which file was it?
ok so i am havving a issue with themes and process.gaps..
ive tried just about everytheme and non seem to like my gmail account...
ive wiped..fix_permission..cleared cache and everything...i try to open my data sync in my data sync. in my setting (menu>setting>data sync) it just opens then closes right off the back.. also my gmail wont sync when i do i manually!.. herre is my log cat!
anyone please help!!!!!!!!
D/dalvikvm( 234): GC freed 4310 objects / 215352 bytes in 127ms
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.androi
d.gm/.ConversationListActivityGmail }
I/ActivityManager( 144): Start proc com.google.android.gm for activity com.goog
le.android.gm/.ConversationListActivityGmail: pid=736 uid=10036 gids={3003}
I/ActivityThread( 736): Publishing provider com.google.android.gm.attachmentspr
eviews: com.google.android.gm.AttachmentPreviewProvider
I/ActivityThread( 736): Publishing provider com.google.android.gmail.Suggestion
Provider: com.google.android.gm.SuggestionsProvider
I/ActivityThread( 736): Publishing provider com.google.android.gm.status: com.g
oogle.android.gm.SenderStatusProvider
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x2800000 cmp=com.google.android
.gm/.ConversationListActivity }
V/Gmail ( 736): onCreate(), id=com.google.android.gm.ConversationListActivity
@43679d08
I/ActivityManager( 144): Starting activity: Intent { flg=0x2000000 cmp=com.goog
le.android.gm/.WaitActivity (has extras) }
I/ActivityManager( 144): Displayed activity com.google.android.gm/.Conversation
ListActivity: 88 ms (total 539 ms)
W/InputManagerService( 144): Starting input on non-focused client com.android.i
nternal.v[email protected] (uid=10036 pid=736)
W/InputManagerService( 144): Client not active, ignoring focus gain of: com.and
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
[email protected]
D/ForecastProvider( 510): query() with uri=content://com.androidapps.widget.wea
ther2/appwidgets/5
D/ForecastProvider( 510): query() with uri=content://com.androidapps.widget.wea
ther2/appwidgets/5
D/dalvikvm( 510): GC freed 853 objects / 448232 bytes in 80ms
I/ActivityManager( 144): Process com.google.android.gm (pid 736) has died.
D/dalvikvm( 234): GC freed 3207 objects / 163008 bytes in 132ms
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/
.Launcher }
I/ActivityManager( 144): Starting activity: Intent { act=android.settings.SETTI
NGS flg=0x10200000 cmp=com.android.settings/.Settings }
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
W/InputManagerService( 144): Starting input on non-focused client android.view.
[email protected] (uid=1000 pid=144)
W/InputManagerService( 144): Client not active, ignoring focus gain of: android
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 144): Starting activity: Intent { cmp=com.android.providers.
subscribedfeeds/com.android.settings.SyncSettings }
W/InputManagerService( 144): Starting input on non-focused client android.view.
[email protected] (uid=1000 pid=144)
W/InputManagerService( 144): Client not active, ignoring focus gain of: android
[email protected]
W/InputManagerService( 144): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 144): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/
.Launcher }
W/InputManagerService( 144): Starting input on non-focused client com.android.i
[email protected] (uid=1000 pid=699)
Got the error as well. Fixed it by going into "Settings>Manage Applications" and selecting Google Apps and Clearing Data and then do the same for GMail and any other Google App you are having a problem with. After this you will have to re-enter your account info again and everything should sync back up without problem. Hope this helps. try it it will work just wipe the data from all google apps
Hello folks. Here's a quick and dirty way to solve your problems:
I started to get the com.google.process.gapps and the com.htc.bg FC's a few days back. And I didn't have a clue why. After 2 days spent doing logcats and stuff... In the end i noticed that my google sync account and the facebook & facebook for htc sense account gave error messages when sync-ing contacts. So... I cleared all data for those programs (go to settings - applications - manage applications). Removed the google sync and facebook sync accounts. Erased all of the contacts from my phone (afer previously backing them up to the sd).
And... reboot the phone, configure the sync accounts for google and facebook, do a full sync with contacts... and afterwards restore only the phone contacts back... Re-link the contacts and everything is running perfectly right now.
Hope it helps.
same problem traced to my calendar
diaz2611 said:
Got the error as well. Fixed it by going into "Settings>Manage Applications" and selecting Google Apps and Clearing Data and then do the same for GMail and any other Google App you are having a problem with. After this you will have to re-enter your account info again and everything should sync back up without problem. Hope this helps. try it it will work just wipe the data from all google apps
Click to expand...
Click to collapse
This worked for me. I traced the problem to my calendar - it wouldn't sync. I'm not sure how it 'got broke'. Opening the Apps management and stopping anything dealing with the calendar and clearing the cache did the trick.
Running Apex 1.4 - BWC theme DX
com.google.process.gapps stopped unexpectedly
I have tried tracing the problem.
My conclusion.
There is no need to reboot or hard reset.
It will not solve the problem.
The problem is hidden calls that are being made by certain applications
especially the Market. Whenever you enter market and try a new app, one of the hidden call is made for screen capture.
And the captured screen is then sent via network connection to somewhere.
This procedure call seems to create the error.
Either screen capture fails or the network connection fails.
The procedure call stays in memory and is activated at variable interval based on network connection status.
During this activation and subsequent failure the com.google.process.gapps stops.
I simply went into the running services and stopped the mobile tracking service and screen capture service (if it is active)
The android becomes stable after that.
Frequent use of Task Manager to clear level 1 and 2 memory also provides stability after use of Market.
Removed...
So I followed this excellent page to get the FM Radio installed on my DX running RubiX 2.0.1.
http://free-apk.appspot.com/2010/09/7/develop.html
However, when it launches, it hangs at the "FM Radio is being launched, please wait...". I can hit the back button and enter the app, but nothing happens, no signal is picked up, no static even. I'm wondering if the problem is in the new FMRadio.apk (which I renamed FMModRadio.apk) trying to talk to the also new FMRadioService.apk (which I renamed FMModRadioService.apk) or it's something else that I can't decipher from the logcat. I believe the line below is the relevant error (The whole logcat is attached, from when I start the application, it hangs at the "FMRadio is being launched...", to when I hit back, settings, and exit FM radio.):
Code:
03-25 09:48:44.120 3999 4003 W ActivityManager: Unable to start service Intent { act=com.motorola.android.modradio.FMRADIO_SERVICE }: not found
Now, I'm not very good at reading these things yet, so if someone could help me decipher what I need to do to make that service intent findable, that would be GREAT!
If I had to guess -- it would be a very uneducated guess -- but I would guess that I need to further rename something so that it fits with my renaming scheme:
com/motorola/fmradio/
becomes
com/motorola/modradio/
com/motorola/android/fmradio/
becomes
com/motorola/android/modradio
com.motorola.fmradio
becomes
com.motorola.modradio
com.motorola.android.fmradio
becomes
com.motorola.android.modradio
I used this command:
Code:
find ./ -type f | xargs perl -pi -e 's/motorola\/fmradio/motorola\/modradio/g'
substituting the proper pieces where appropriate. I used it on both the FMRadio.apk and the FMRadioService.apk. My guess would be I need to rename the intent IN the radio.apk to what the new name is in the radioservice.apk...
Any ideas? I would really appreciate some help from someone who knows more about this than I do.
I, for the life of me, can't get the Evo 4G to start the Netflix app correctly. It shows a white screen, and then after a bit of time it throws a message saying
"Error : Please make sure the device's date and time settings are updated to the current date."
It's operating on the auto-time, and no matter what I do - reboot, re-install Netflix, etc - I still get that error. I can see it transferring data - so I am not sure what this means. I even tried flashing back to my stock ROM, the backup I have right after I rooted the phone - and it still doesn't do it (I was running Azrael's 4.0 sense rom prior).
I've seen other folks mention this - has anyone else run into this or figured out a resolution?
+1 same issue here running Calkulin 1.8
Sent from my PC36100 using XDA App
It seems like each phone has a different issue. I don't have an evo, but I'm working on ironing out the issues, unless Netflix beats me to it. I haven't seen this issue yet. Could you provide a logcat from right before starting Netflix up.
Sent from my HERO200 using XDA App
I was having the same problem with my wife's Evo including the error message. I went and resynced everything and after that Netflix started working. Hope that helps.
Mine plays but has no sound?
Sent from my PC36100 using Tapatalk
Cleared cache and dalvik and now it works....
Sent from my PC36100 using Tapatalk
I'm having the same issue as the original poster -- re-installed, rebooted, cleared cache, still no luck. Novice smartphone user, so everything is original equipment, no rooting, etc.
unCoRrUpTeD said:
It seems like each phone has a different issue. I don't have an evo, but I'm working on ironing out the issues, unless Netflix beats me to it. I haven't seen this issue yet. Could you provide a logcat from right before starting Netflix up.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I'll try - gimme today to fiddle with it, never messed with logcat, so I'll need to learn what to do with that.
unCoRrUpTeD said:
It seems like each phone has a different issue. I don't have an evo, but I'm working on ironing out the issues, unless Netflix beats me to it. I haven't seen this issue yet. Could you provide a logcat from right before starting Netflix up.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Attached is a ZIP that has logfiles for just netflix activity from starting it up to closing it out, as well as another file that has all entries during that same time period. Also, here's the logs surrounding Netflix:
Code:
Process Monitor Widget (logcat)
===============================
Process Netflix(com.netflix.mediaclient)
D/08:32:22.469 GC_EXPLICIT freed 89 objects / 4456 bytes in 78ms
D/08:32:22.139 GC_EXPLICIT freed 1826 objects / 358504 bytes in 104ms
D/08:32:17.269 GC_FOR_MALLOC freed 9684 objects / 414472 bytes in 35ms
D/08:32:11.769 GC_FOR_MALLOC freed 4151 objects / 506824 bytes in 46ms
D/08:32:06.029 GC_FOR_MALLOC freed 5213 objects / 342464 bytes in 32ms
D/08:32:00.429 GC_FOR_MALLOC freed 33 objects / 1352 bytes in 95ms
D/08:31:57.809 GC_EXPLICIT freed 431 objects / 24816 bytes in 30ms
D/08:31:57.659 GC_EXPLICIT freed 2834 objects / 194272 bytes in 42ms
D/08:31:55.179 queueRequest with mProxyHost=null for https://uiboot.netflix.com/apps/mobileui/upgrade_policy?v=2.0&e=NFANDROID1-HTC==PC36100S-44533132&device_type=NFANDROID1-&certification_version=1.2.0%20build%20819145-1.2.0-102
D/08:31:55.179 setProxyConfig mProxyHost=null
D/08:31:55.179 queueRequest to set proxy
D/08:31:55.179 [JWebCoreJavaBridge::resume] >> do resume
D/08:31:55.159 GC_FOR_MALLOC freed 2666 objects / 342392 bytes in 30ms
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.059 Settings::setMixedPluginEnabled 1
I/08:31:55.049 PluginManager::getPluginDirectories target:/data/data/com.adobe.flashplayer/lib
I/08:31:55.049 PluginManager::getPluginDirectories add:/system/lib/
I/08:31:55.039 PluginManager::getPluginDirectories target:/data/data/com.htc.flashliteplugin/lib
E/08:31:55.039 CheckOMX drm.play is not available done
E/08:31:55.039 CheckOMX drm.play is not available
I/08:31:55.039 listNode return 38
I/08:31:55.029 OMX interface is valid
I/08:31:55.029 Got IMediaPlayerService interface
I/08:31:55.029 Got IBinder interface to media.player
I/08:31:55.029 PluginManager::getPluginDirectories
I/08:31:55.009 Got IServiceManager interface
D/08:31:55.009 Shared lib '/data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so' already loaded in same CL 0x4656e988
D/08:31:55.009 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:55.009 Added shared lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 htcFlashPlugin::htcFlashPlugin
D/08:31:54.939 GC_EXTERNAL_ALLOC freed 291 objects / 17992 bytes in 26ms
D/08:31:54.909 GC_EXTERNAL_ALLOC freed 1296 objects / 92008 bytes in 29ms
well now it works....
With Android Market, I updated Adobe Flash to 10.3 (as well as Youtube and Google Maps updates), and now it works. Right before that I also resynced everything (but that didn't do diddly).
So I don't know if the Adobe Flash update fixed it. I could try removing the update and re-running Netflix - but that's what *seems* to be my case at first glance.
My girlfriend's Evo is doing the very same thing - and hers is stock and unrooted (brand new, just purchased yesterday) - so when she gets home tonight, I'll try the same thing - update to Flash 10.3, and see if her Netflix then runs correctly. I'll follow up with results here afterwards.
Wifflepig said:
Attached is a ZIP that has logfiles for just netflix activity from starting it up to closing it out, as well as another file that has all entries during that same time period. Also, here's the logs surrounding Netflix:
Code:
Process Monitor Widget (logcat)
===============================
Process Netflix(com.netflix.mediaclient)
D/08:32:22.469 GC_EXPLICIT freed 89 objects / 4456 bytes in 78ms
D/08:32:22.139 GC_EXPLICIT freed 1826 objects / 358504 bytes in 104ms
D/08:32:17.269 GC_FOR_MALLOC freed 9684 objects / 414472 bytes in 35ms
D/08:32:11.769 GC_FOR_MALLOC freed 4151 objects / 506824 bytes in 46ms
D/08:32:06.029 GC_FOR_MALLOC freed 5213 objects / 342464 bytes in 32ms
D/08:32:00.429 GC_FOR_MALLOC freed 33 objects / 1352 bytes in 95ms
D/08:31:57.809 GC_EXPLICIT freed 431 objects / 24816 bytes in 30ms
D/08:31:57.659 GC_EXPLICIT freed 2834 objects / 194272 bytes in 42ms
D/08:31:55.179 queueRequest with mProxyHost=null for https://uiboot.netflix.com/apps/mobileui/upgrade_policy?v=2.0&e=NFANDROID1-HTC==PC36100S-E9616F100D03D7657E858E038D039C3ACEEB08871A7088736019A9013578DFF1&device_type=NFANDROID1-&certification_version=1.2.0%20build%20819145-1.2.0-102
D/08:31:55.179 setProxyConfig mProxyHost=null
D/08:31:55.179 queueRequest to set proxy
D/08:31:55.179 [JWebCoreJavaBridge::resume] >> do resume
D/08:31:55.159 GC_FOR_MALLOC freed 2666 objects / 342392 bytes in 30ms
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.069 Settings::setMixedPluginEnabled 1
D/08:31:55.059 Settings::setMixedPluginEnabled 1
I/08:31:55.049 PluginManager::getPluginDirectories target:/data/data/com.adobe.flashplayer/lib
I/08:31:55.049 PluginManager::getPluginDirectories add:/system/lib/
I/08:31:55.039 PluginManager::getPluginDirectories target:/data/data/com.htc.flashliteplugin/lib
E/08:31:55.039 CheckOMX drm.play is not available done
E/08:31:55.039 CheckOMX drm.play is not available
I/08:31:55.039 listNode return 38
I/08:31:55.029 OMX interface is valid
I/08:31:55.029 Got IMediaPlayerService interface
I/08:31:55.029 Got IBinder interface to media.player
I/08:31:55.029 PluginManager::getPluginDirectories
I/08:31:55.009 Got IServiceManager interface
D/08:31:55.009 Shared lib '/data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so' already loaded in same CL 0x4656e988
D/08:31:55.009 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:55.009 Added shared lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 Trying to load lib /data/data/com.netflix.mediaclient/lib/libnetflixmp_jni.so 0x4656e988
D/08:31:54.999 htcFlashPlugin::htcFlashPlugin
D/08:31:54.939 GC_EXTERNAL_ALLOC freed 291 objects / 17992 bytes in 26ms
D/08:31:54.909 GC_EXTERNAL_ALLOC freed 1296 objects / 92008 bytes in 29ms
Click to expand...
Click to collapse
Just want to verify..
Are you getting the "device not supported" error?
Or are you getting a black screen?
Or does it work?
Sent from my HERO200 using XDA App
unCoRrUpTeD said:
Just want to verify..
Are you getting the "device not supported" error?
Or are you getting a black screen?
Or does it work?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Nope, I was getting the red Netflix logo, then a white screen and a message saying I should make sure my date and time was correct, then it'd exit (I'm the OP).
What fixed it for me was strange - I updated my Adobe Flash to 10.3 (as well as Google Maps and Youtube updates) and then it worked. Mine was a custom ROM (Azrael 4.0).
My GFs Evo 4G - had the very same issue - and hers is stock, unrooted - brand new. I tried updating her Flash to 10.3, also did a update to her Maps and Youtube - and it *didn't* fix it. That is, until she rebooted her phone, and let it sit for about 10 minutes and tried once more - then it worked.
It seems really odd that there'd be a wait time that would make it work - maybe it's something network related (with their network), or just a crap shoot. Dunno, but we're both working now.
Anyone who can actually get it to work (getting it to work defined as actually streaming audio and/or video without crashing ever) able to post their logcat file right before and during the first few seconds of streaming?
Would prefer logs from htc devices since that's what I have, but any would be appreciated.
I'd just like to compare it to the logcats showing errors. If audio/video quality is not perfect on your device for netflix, please note that so it can be factored in.
I found a reference to drm.play in /system/lib/libstagefrighthw.so compiled library for some of the htc sense 2.3 roms. Not sure how relevant it is at the moment since it's just a error message string.
@mem addr: 00003180h
drm.play.error: StagefrightSurfaceOutput7x30::createRenderer returning NULL!
Wifflepig said:
Nope, I was getting the red Netflix logo, then a white screen and a message saying I should make sure my date and time was correct, then it'd exit (I'm the OP).
What fixed it for me was strange - I updated my Adobe Flash to 10.3 (as well as Google Maps and Youtube updates) and then it worked. Mine was a custom ROM (Azrael 4.0).
My GFs Evo 4G - had the very same issue - and hers is stock, unrooted - brand new. I tried updating her Flash to 10.3, also did a update to her Maps and Youtube - and it *didn't* fix it. That is, until she rebooted her phone, and let it sit for about 10 minutes and tried once more - then it worked.
It seems really odd that there'd be a wait time that would make it work - maybe it's something network related (with their network), or just a crap shoot. Dunno, but we're both working now.
Click to expand...
Click to collapse
I remember that now (and thats what the title says). Jumping through different threads starts getting me confused. I'm not able to use flash 10.3 or 10.2 on my phone, so hopefully I can work around that. Could you post another logcat now that it is working?
Have flash 10.3, Netflix starts, I select a movie and play it. It switches to the red load screen, then flickers and goes back to the Netflix home menu screen....won't play the video....
Jeremy
Evo 4g, unrevoked 3.2, fresh evo 4.0.0.4
I had this problem on my Asus TF300T tablet running Android 4.2.1. After clearing the data, removing all updates for the Netflix app and updating again, the issue was still there. It turns out that Netflix is very finicky about the network you're connected to. Mine has two routers: one for the wired devices and one for the wireless devices. The gateway is on the wired router and the wireless router goes out through it. Some posts advice to run a WAN test on the router and that's when I realized that the internal tools in the wireless router do not have access to the internet, although every wireless device connected to it has internet access, including my tablet in question. I switched the operation mode on the wireless router from router to access point. That fixed the Netflix sign in problem for me.
If you find that nothing works for you at home, try connecting somewhere else. If you have specific DNS servers in your (Android) network setup try without them.
Ronnie Barabas
Context: [DEV] Touchwiz for Transformer - xda-developers This was moved because there were no files to test.
What is this? This is based on Prime 1.6. All the samsung galaxy tab 10.1 specific files that run UX have been merged in. Then I decompiled the framework for both the TF and GT10.1, and merged in functionality into the TF framework. It has come a long way, and the launcher is usable. However, the statusbar does not come up because systemui.apk FC's.
PrimeUX: Download THIS IS NOT USABLE YET, PEOPLE WHO EDIT SMALI ONLY
You will get FC's from systemui, media, and myfiles. Media and myfiles could be avoided by leaving out more of the samsung files that fguy did not include in his. I assume it is because of the FC's.
This is meant for others to work on the systemui issue, not for any real use.
Porting Process:
Here was what I was using to decompile the framework. Drop all the files into the framework directory, then run decompile.bat and it'll all go into respective folders under an out folder. Then you can do this to the samsung framework, then diff them with winmerge or something like that.
When you find an error in logcat, search for a term related to it within Notepad++'s search in files feature. Generally, this will point you into the direction of a missing class. Then you can copy the class over into the associated TF framework file by right clicking on the highlighted missing class within Winmerge. However, sometimes it isn't so easy because Samsung and Asus have heavily modified the HC framework. Asus to add the dock functionality, samsung for the touchwiz stuff.
Tools: Decompile Framework
Good to see this happening! quick question, there isn't any resizing needing to done yea? Just smali edits?
Sent from my Desire HD using XDA Premium App
Gtj94 said:
Good to see this happening! quick question, there isn't any resizing needing to done yea? Just smali edits?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
I guess I'm unsure what you mean by resizing.
Currently it is at a point where more merging needs to happen(i think) to get the mini apps working. The systemui.apk has a major dependency on the mini apps working, so it crashes without them working.
The main problem I have is there is a FC by systemui, pointing to the mini apps as the problem. However, there is no way to find out why the mini apps aren't running. So, I don't know if more framework porting needs to happen, or what.
Hey rothnic. Great work so far. I don't envy you task of trying to merge the frameworks but you have my full support. I'm no smali expert by any means but I'll help out if I can.
I suggest keeping a healthy supply of beer at hand as smali editing drives me to drink
Ported going to interface with applications such keyboard? I do not like asus keyboard
Roach2010 said:
Hey rothnic. Great work so far. I don't envy you task of trying to merge the frameworks but you have my full support. I'm no smali expert by any means but I'll help out if I can.
I suggest keeping a healthy supply of beer at hand as smali editing drives me to drink
Click to expand...
Click to collapse
Yeah, not the most fun stuff in the world. Was going to get around to touching base with you if I ever get it working. I'll package it up as a delta so it's not a full on release to manage. If there is a way to get it working, I hope to document the changes I made so it could be applied to TF updates as they come out.
stitoo said:
Ported going to interface with applications such keyboard? I do not like asus keyboard
Click to expand...
Click to collapse
If it works, I'll probably alter Prime 1.6 as little as possible. Have you tried Thumb Keyboard from the market? Worth the cost.
Just comparing smali files and in "smali\com\android\systemui\statusbar\tablet" the TableyStatusBar$H file in the Prime UX, when compared to the A500 UX rom exact file. There are many differences between the two. Now Myself have only done minimal smali editing. However I was just wondering if this has already been looked at and/or whether they theoretically should be the same?
Thanks
Dan
dwillMUFC said:
Just comparing smali files and in "smali\com\android\systemui\statusbar\tablet" the TableyStatusBar$H file in the Prime UX, when compared to the A500 UX rom exact file. There are many differences between the two. Now Myself have only done minimal smali editing. However I was just wondering if this has already been looked at and/or whether they theoretically should be the same?
Thanks
Dan
Click to expand...
Click to collapse
I started using the A500 UX version of systemui.apk. I had the errors that we still have now. But, I thought maybe the version that Fguy used for the Acer might not work well with this specific implementation of honeycomb. So I tried a newer version of the samsung UX files, but it had no impact.
So that is why you would find differences between the one in PrimeUX versus Fguy's ROM. I tried talking to him about it, but I think the language barrier is too great to really communicate well enough.
I'm not sure if he added anything to the SystemUI.apk or not, but my intuition was that the changes were mainly to the framework files. That is a consideration to make, though.
this is great, I was wondering if and when we were gonna see this ported. Its great to see the DEV'n really starting to take off!!
Why are you guys concetrating on the keyboard so much for this port, it just gives extra unneeded problems with it, maybe it's a better thing to leave the keyboard as it is for now, i guess that can take alot of headaches away,
br13an said:
Why are you guys concetrating on the keyboard so much for this port, it just gives extra unneeded problems with it, maybe it's a better thing to leave the keyboard as it is for now, i guess that can take alot of headaches away,
Click to expand...
Click to collapse
We, as in the people trying to get this to work, aren't messing with the keyboard at all. One person had a hard to understand comment about the keyboard, and I was just being a nice person about an off topic comment.
The keyboard is definitely the last of my worries.
Okay, so I thought I'd take a look at what is causing the systemui to crash, but upon decompiling in apkmanager I am getting an error. I've done the menuitem 9 and 10 (with both frameworkres and twframeworkres).
I DO get Smali files to edit, but the errors make me not want to try to recompile and put them in there, lol.
nex7er said:
Okay, so I thought I'd take a look at what is causing the systemui to crash, but upon decompiling in apkmanager I am getting an error. I've done the menuitem 9 and 10 (with both frameworkres and twframeworkres).
I DO get Smali files to edit, but the errors make me not want to try to recompile and put them in there, lol.
Click to expand...
Click to collapse
Take some courage, try it
I've had luck despite errors (although unlikely).
Well, I'm at another stop. I was going to use files from a real Galaxy Tab rom to see what differences there are. Perhaps the OP missed something (obv). I can't seem to decompile them. Not even giving me any smali folder. Hmm.
This would be a lot easier if OP listed all the files he has edited to add functions from normal prime 1.6 smali files. If not, I might as well have to start all over just so I'll know what files to edit and which not to. When Winmerge lists a different item, how am I supposed to know it's really just an identical file with some added Asus bonus without checking every single file?
Is anyone able to decode what this exception is? Doing some merges and running logcat while booting, this one comes up (untouched PRIMEUX.zip, just flashed back to the stock zip in OP).
08-22 02:55:12.200: WARN/PackageManager(161): Exception reading jar: /system/framework/twframework-res.apk
08-22 02:55:12.200: WARN/PackageManager(161): java.io.IOException: /system/framework/twframework-res.apk
08-22 02:55:12.200: WARN/PackageManager(161): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
08-22 02:55:12.200: WARN/PackageManager(161): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:904)
08-22 02:55:12.200: WARN/PackageManager(161): at com.android.server.PackageManagerService.main(PackageManagerService.java:706)
08-22 02:55:12.200: WARN/PackageManager(161): at com.android.server.ServerThread.run(SystemServer.java:155)
08-22 02:55:13.440: WARN/PackageManager(161): Failed verifying certificates for package:com.android.systemui
Click to expand...
Click to collapse
nex7er said:
Okay, so I thought I'd take a look at what is causing the systemui to crash, but upon decompiling in apkmanager I am getting an error. I've done the menuitem 9 and 10 (with both frameworkres and twframeworkres).
I DO get Smali files to edit, but the errors make me not want to try to recompile and put them in there, lol.
Click to expand...
Click to collapse
What are you using to decompile? Also, I havn't had much luck compiling apk's, so if anyone knows for sure how, let me know. I can decompile/compile framework files just fine with the files I posted.
nex7er said:
Well, I'm at another stop. I was going to use files from a real Galaxy Tab rom to see what differences there are. Perhaps the OP missed something (obv). I can't seem to decompile them. Not even giving me any smali folder. Hmm.
This would be a lot easier if OP listed all the files he has edited to add functions from normal prime 1.6 smali files. If not, I might as well have to start all over just so I'll know what files to edit and which not to. When Winmerge lists a different item, how am I supposed to know it's really just an identical file with some added Asus bonus without checking every single file?
Click to expand...
Click to collapse
Not sure what you mean by from a real Galaxy Tab rom. I used the files from Fguy's Iconia port at first, then a stock deodexed samsung ROM. I had the same problem I still have, but PrimeUX that I uploaded has untouched samsung applications (everything that goes in /app). I have merged classes from samsung to asus framework files: android.policy.jar, framework.jar, and framework-res.apk. All those errors were related to missing classes, so I merged them.
So what I'm saying is, it doesn't really matter what has already been merged, because those classes now exist. I have approached it by decompiling frameworks from samsung or fguy's rom and prime 1.6. Then i diff them, and then all you can do is use winmerge to let you know if they are different or not. If a file looks like it could have something to do with the status bar etc, then you can double click on that file and winmerge shows a side by side view where you can see the differences and merge lines or not.
This works isn't a clean, let me see which files are different so i can copy them around. It requires digging into each and every class file in the framework to see if something needs to be merged. Also, when you use different ROMs for the touchwiz files, many of the files will differ, so be careful there when mixing stuff.
nex7er said:
Is anyone able to decode what this exception is? Doing some merges and running logcat while booting, this one comes up (untouched PRIMEUX.zip, just flashed back to the stock zip in OP).
Click to expand...
Click to collapse
I'm not sure on that one, but my guess is something went wrong when they deodexed the file. I tried replacing these files from different ROMs, including Fguy's and it always showed that error. I'm thinking maybe it's not a critical error and it still functions since those others work fine.
Oh sweet, you're here! Well, I was using apkmanager but I noticed a few minutes later that you posted working tools in your opening post. My bad, hehe.
I'm not used to editing smali at all, which is why I'm at a stop. There are so many differences (comparing omftab 1.0.5 to your primeux) for it to be a realiable testing ground for just one person. Some files reference different lines than the other (like omftab might have Line 293 somewhere in the file, and your primeux has Line 292 in the same spot). I have no idea if I should be touching those.
Also, running Logcat, I can not see any major problems with systemui popping up. Only the one I posted at the general bootup but it doesn't seem to mean anything. There are also many errors pertaining to mounting the sd-cards, but they still work just fine.
Meaning, it's hard to know what errors are real or not.
Just got done firing up some pokemon on my tab. I guess it's time for a nandroid and try again.
Found the *****y systemui message while doing first boot after flashing.
Code:
08-22 15:32:08.860: ERROR/AndroidRuntime(736): FATAL EXCEPTION: main
08-22 15:32:08.860: ERROR/AndroidRuntime(736): java.lang.RuntimeException: Unable to create service com.android.systemui.SystemUIService: java.lang.NullPointerException
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2046)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.app.ActivityThread.access$2500(ActivityThread.java:122)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1056)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.os.Handler.dispatchMessage(Handler.java:99)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.os.Looper.loop(Looper.java:132)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.app.ActivityThread.main(ActivityThread.java:4025)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at java.lang.reflect.Method.invokeNative(Native Method)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at java.lang.reflect.Method.invoke(Method.java:491)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at dalvik.system.NativeStart.main(Native Method)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): Caused by: java.lang.NullPointerException
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.sec.minimode.manager.MiniModeAppManager.registerCallback(MiniModeAppManager.java:80)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.systemui.statusbar.tablet.MiniModeAppsPanel.onFinishInflate(MiniModeAppsPanel.java:440)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.view.LayoutInflater.rInflate(LayoutInflater.java:732)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.view.LayoutInflater.inflate(LayoutInflater.java:479)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.view.LayoutInflater.inflate(LayoutInflater.java:391)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.view.LayoutInflater.inflate(LayoutInflater.java:347)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.view.View.inflate(View.java:11630)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.systemui.statusbar.tablet.TabletStatusBar.addPanelWindows(TabletStatusBar.java:352)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.systemui.statusbar.tablet.TabletStatusBar.makeStatusBarView(TabletStatusBar.java:718)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.systemui.statusbar.StatusBar.start(StatusBar.java:61)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.systemui.statusbar.tablet.TabletStatusBar.start(TabletStatusBar.java:473)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at com.android.systemui.SystemUIService.onCreate(SystemUIService.java:79)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2036)
08-22 15:32:08.860: ERROR/AndroidRuntime(736): ... 10 more
I would also like to know what rom you have been using to compare and import from. This would make it easier so I don't use an older or newer rom and **** something up.
I'm pretty sure those line references won't be an issue. It is more to do with things like Environment.smali from android.policy.jar. It has overlapping capability that looks very hard to merge.
Also, about not knowing what are errors. You will see a lot of red stuff coming from samsung related files. A lot of it is just samsung printing out debug information, but for some reason they print them like exceptions. They did this a lot when I was porting the original galaxy tab's email app to the Gtablet. The main issue is the one you pasted. That is all that is given, and it doesn't really tell you much.
I'll try to post later today which samsung ROM I was using. I think it might have been the deodexed one from here: http://forum.xda-developers.com/showthread.php?t=1198921 . I'll find out for sure.
Good stuff. Yeah I've been using that one as well. Right now I am going over services.jar and comparing with omftab and the primeux service.jar is missing a bit. Including one that has to do with TW, apparently.
Differences like this " const v1, 0x10402d3" are all over. I have no idea what they are, but I'm going to guess I'm not to touch these even if they differ?
EDIT ADD: Without having looked much further (just started again), I came upon errors pertaining to GsmSignalBar, referenced from systemui. Could this be what causes the SystemUI.apk to not launch itself?
Code:
08-23 01:14:07.570: WARN/dalvikvm(1113): VFY: unable to resolve virtual method 441: Landroid/telephony/SignalStrength;.getGsmSignalBar ()I
Hmm, now to decide to take time to check this out or try something else. Really hard when you're alone and not working as a team on several parts.
EDIT ADD 2: Hmm, at some point, it IS launching the statusbar without crashing. It's not until later when that errormsg I pasted a few posts up, that it disappears. The remaining errors between it loading and the crashing are all related to phone stuff. Here's a full paste from when it loads till it crashes and starts doing other stuff: http://pastebin.com/4AnEX6kq
Code:
08-23 01:14:07.440: DEBUG/SystemUIService(1113): loading: class com.android.systemui.statusbar.tablet.TabletStatusBar
08-23 01:14:07.490: DEBUG/SystemUIService(1113): running: [email protected]
Not sure what the deal is with the getGsmSignalBar, because that didn't even have to be merged. It was already within framework.jar.
Try this services.jar, I did find something in there critical to the status bar and fixed it:
http://www.multiupload.com/3Q2WD076XI
I'm not setup atm to test. The wife has been needing the tablet and I've been working on the car. However, I should be free to work on this, this afternoon.
Hi,
I was seeing lot of problems there with my G3 i never saw before. Firstly, Browser.apk was fine on my XXJPS. No FC. No reboots. Then, for some stupid reason i don't know my browser started crashing on sites like forum.xda-developers.com - or any other site with lot of stuff on it, when it was almost finishing loading. It doesn't even show FC. just closed and android was fine again after it closes.
Then, i thought it was only caused by Firmware, so i flashed to XXJPQ. Again the same thing, that has never happened to me on even that firmware.
I tried lots of custom roms, like Kyrillos' ROM 9.5, CyanogenMOD 7 a8 and on every android OS with EVERY alternative browser i tried, (Opera Mini, Dolphin,...) they get closed. No matter its stock or not, they got closed. Now, on Purumod Special Edition v2.0 it even forces ANDROID to reboot itself by opening the same huge page.
I checked logcat and opened xda-developers forum again with G3, and i figured those things.
===================================
V/browser ( 5315): BrowserActivity.onStart: [email protected]
V/browser ( 5315): BrowserActivity.onResume: [email protected]
V/browser ( 5315): BrowserActivity.onPageStarted: url = http://forum.xda-developers.com/
V/browser ( 5315): onReceive : info.isAvailable() - true
V/browser ( 5315): BrowserActivity.onPageStarted: url = http://forum.xda-developers.com/setcompact.php?true
V/browser ( 5315): BrowserActivity.shouldOverrideUrlLoading: url = http://forum.xda-developers.com/setcompact.php?true webview = [email protected]
V/browser ( 5315): BrowserActivity.onPageStarted: url = http://forum.xda-developers.com/
V/browser ( 5315): BrowserActivity.shouldOverrideUrlLoading: url = http://forum.xda-developers.com/ webview = [email protected]
W/PowerManagerService( 4908): Timer 0x3->0x3|0x0
--------- beginning of /dev/log/system
I/ActivityManager( 4908): Process com.sec.android.providers.downloads (pid 5168) has died.
I/ActivityManager( 4908): Process com.google.android.apps.uploader (pid 5296) has died.
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process android.process.acore (pid 5036) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.android.providers.contacts/.ContactsStartupService in 5000ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.google.process.gapps (pid 5023) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.google.android.gsf/.gtalkservice.service.GTalkService in 14666ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.siine.ime:Capptain (pid 5351) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.siine.ime/com.ubikod.capptain.android.service.CapptainService in 24323ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.sec.android.app.sns (pid 5199) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.sec.android.app.sns/.SnsService in 249930ms
I/ActivityManager( 4908): Low Memory: No more background processes.
D/WifiService( 4908): releaseWifiLockLocked: WifiLock{capptain-service type=1 [email protected]}
I/ActivityManager( 4908): Process com.sec.android.providers.drm (pid 5192) has died.
W/ActivityManager( 4908): Scheduling restart of crashed service com.sec.android.providers.drm/.OmaDrmConfigService in 33655ms
I/ActivityManager( 4908): Low Memory: No more background processes.
I/ActivityManager( 4908): Process com.sec.android.provider.logsprovider (pid 5062) has died.
I/ActivityManager( 4908): Low Memory: No more background processes.
E/installd( 2537): eof
E/installd( 2537): failed to read size
I/installd( 2537): closing connection
I/ServiceManager( 2522): service 'telephony.registry' died
I/ServiceManager( 2522): service 'batteryinfo' died
I/ServiceManager( 2522): service 'usagestats' died
I/ServiceManager( 2522): service 'meminfo' died
I/ServiceManager( 2522): service 'cpuinfo' died
I/ServiceManager( 2522): service 'permission' died
I/ServiceManager( 2522): service 'wifi' died
=========================================
and so on.. service 'blablabla...' died... then it reboots the system.
i also thing that may be caused by JavaScript. Without it it doesnt close.
But i dont wanna see pages without javascript. Some pages are buggy without it.
Any solutions?
I have the same problem too. even with dolphin brower it FC and reboot system. And i have an other problem with the stock android browser : when I try to log in somewhere the secure connection is needed Browser force close and I don(t know why. some help is welcome
same problem already discussed here:
http://forum.xda-developers.com/showthread.php?t=1536521
Problem is not there on stock eclair 2.1, also no memory drain there that leads to the crash. I had crashes on both kyrillos 9.5 and stock JPU/JPQ and JPS, so I assume it's an OS thing, and certainly not a custom rom issue.
Maybe android 2.2 's OS itself or browser support specific webpage features that cause this crash (flash?)
XDA page loads normal on eclair 2.1
p.s. still impressed by the speed of eclair, when you have some spare time....re-try it
Br.
Michel
vleutmans said:
Problem is not there on stock eclair 2.1, also no memory drain there that leads to the crash. I had crashes on both kyrillos 9.5 and stock JPU/JPQ and JPS, so I assume it's an OS thing, and certainly not a custom rom issue.
Maybe android 2.2 's OS itself or browser support specific webpage features that cause this crash (flash?)
XDA page loads normal on eclair 2.1
p.s. still impressed by the speed of eclair, when you have some spare time....re-try it
Br.
Michel
Click to expand...
Click to collapse
Which eclair rom ?
Sent from my GT-I5800 using Tapatalk 2 Beta-5
I5800XXJK1 the latest...and greatest I hope.
I just rooted this rom (superoneclick), then disabled some bloatware and for the rest didn't touch it.
despite eclair not being able to be a wifi hotspot by default,it still can be with separate software. So feature wise I don't miss anything at the moment.
If you want to have app2sd/hybrid data2sd on eclair without the usual delays, you can even install link2sd from market, and happily install lots of software with no lag.
Br.
Michel
if this issue is staying despite the change in roms then its one of two things... either its a problem deeply buried in your system and in which case PM hillbeast and ask him very nicely as im sure he has a zip file that can completely wipe your phone.
or its hardware... does your phone get very hot?
Ava.tar said:
if this issue is staying despite the change in roms then its one of two things... either its a problem deeply buried in your system and in which case PM hillbeast and ask him very nicely as im sure he has a zip file that can completely wipe your phone.
or its hardware... does your phone get very hot?
Click to expand...
Click to collapse
I think it's a problem in android 2.2 Froyo itself, so the OS.
I'm not underestimating the developers on Froyo, but I think they cannot solve OS malfunctions as they are used to focus on customizing only (feature and GUI wise).
Eclair is just a better platform for the i5800 hardware...to my humble opinion
Even the youtube audio/video out-of-sync is almost not present in eclair...imagine.
it reboots the phone?? dude, if dolphin and other browser force close, then i'm sure it's not the software problem.......
When I checked on froyo, then just before browser FC, I say a memory peak just before.
So when you open de xda page and monitor the memory usage of browser, then it goes from example 25 to 150 mb in a few seconds, then browser FC.
I will try purumod soon if I have some playing-time to check and combine it with link2sd, because app2sd always seems to cause lags and link2sd is fast.
guys i've no such issues over here& if someone is looking for zerofill.tar like avatar suggested above...you can find it in my mediafire...
btw: i can fully load xda page in following browsers: Maxthon, Operamini, Operamini next, Boat browser...idk for stock browser as i don't use it coz it's so slowww
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can do this...
Flash your phone with zerofill.tar..
Then remove the partition from sd card using minitool and repartition using kernel used in cm7alpha8....
Just give it a try.
I used to get this problem once.not anymore.
Sent from my GT-I5800 using Tapatalk
prohank said:
You can do this...
Flash your phone with zerofill.tar..
Then remove the partition from sd card using minitool and repartition using kernel used in cm7alpha8....
Just give it a try.
I used to get this problem once.not anymore.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
i recommend partitioning sdcard with minitool on a comp...coz if partitioned through cwm it could result a mass storage failure later on...it happened to me...and i always use minitool since then
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rkoby13 said:
i recommend partitioning sdcard with minitool on a comp...coz if partitioned through cwm it could result a mass storage failure later on...it happened to me...and i always use minitool since then
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Weird! I always partition through cwm.never had a problem..
When did u try this?..it must have been an old cwm
Sent from my GT-I5800 using Tapatalk
prohank said:
Weird! I always partition through cwm.never had a problem..
When did u try this?..it must have been an old cwm
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
rkoby13 said:
i recommend partitioning sdcard with minitool on a comp...coz if partitioned through cwm it could result a mass storage failure later on...it happened to me...and i always use minitool since then
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.0
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Yep, it happened the same to me as rkoby13 explained. Sounds weird/strange, prohank,
i know. But it is true.
You better use minitool as rkoby already said to avoid failures later on.
Just search for google to find it - it's free (type: MiniTool Partition Wizard)
regards
Galaxy3User said:
Yep, it happened the same to me as rkoby13 explained. Sounds weird/strange, prohank,
i know. But it is true.
You better use minitool as rkoby already said to avoid failures later on.
Just search for google to find it - it's free (type: MiniTool Partition Wizard)
regards
Click to expand...
Click to collapse
Any problems mate?
I said i never got such a problem still.does that mean i said "don't use minitool"?
i think i did not.:sly:
so i asked if it still happens in new cwm's as well? If it does then i wouldn't do it anymore.
And if you haven't heard of partitioning through cwm.
May be you should open google web page which is www.google.com and type "partitioning through cwm?" And then enter key.
And as for minitool thing i already use it.thx for the description.
So keep your kind info with yourself if you aren't asked.
I respect rkoby.he has helped me a llot of times.i don't think he will take this in a negative way
Cheers
Sent from my GT-I5800 using Tapatalk