Rom: Modaco 3.1
Firmware: 1.5
Radio: 63.18.55.06JU_6.35.09.26
The problem only occurs when I have the Modaco Rom installed. Basically a force close error occurs about 3-4 times a day, with the message:
"The process system has stopped unexpectedly. Please try again."
This leads to the phone booting to the HTC logo screen and the error message popping up again. This can only be stopped if I reboot the phone. I have ran adb logcat, the results of which are posted. I was hoping someone could identify the problem for me. Cheers
try to wipe everything and reinstall
Code:
E/ActivityThread( 1749): Failed to find provider info for com.htc.launcher.setting.LauncherSettingProvider
E/SettingUtil( 1749): loadSettings(), cursor == null, content provider is not ex
ist
...
E/AndroidRuntime( 1760): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 1760): java.lang.RuntimeException: Unable to get provider android.content.SyncProvider: java.lang.IllegalStateException: not initialized
E/AndroidRuntime( 1760): at android.app.ActivityThread.installProvider(ActivityThread.java:3857)
Add HTC Checkin Service in exclusions of your task killer
I have tried wiping everything including the sd card but doesn't seem to change anything. I have just added HTC Checkin Service to the exclusions list so hopefully that will work.
burgess_boy said:
I have tried wiping everything including the sd card but doesn't seem to change anything. I have just added HTC Checkin Service to the exclusions list so hopefully that will work.
Click to expand...
Click to collapse
yo dude, does it help?
Related
I've got a problem with the Android Market whereby it will work as normal, allowing me to search for and download apps, but shows the error message "the server is not available..." whenever I select my apps. So, I can't see my apps at all.
I'm running AceSmod ROM and have cleared the market data but to no avail.
I found this in the logcat. Not sure if it helps...
"[24] BaseAction.run(): ApiException: com.android.vending.api.ApiException: Error from backend. Request=com.android.vending.model.AssetRequest, Response=INTERNAL_SERVICE_ERROR
I/vending (16292): [1] BaseAction.displayErrorUi(): Server error in com.android.vending.MyDownloadsActivity$MyDownloadsLoader: com.android.vending.api.ApiException: Error from backend. Request=com.android.vending.model.AssetRequest, Response=INTERNAL_SERVICE_ERROR"
Any help would be appreciated.
Ta.
scutworker said:
I've got a problem with the Android Market whereby it will work as normal, allowing me to search for and download apps, but shows the error message "the server is not available..." whenever I select my apps. So, I can't see my apps at all.
I'm running AceSmod ROM and have cleared the market data but to no avail.
I found this in the logcat. Not sure if it helps...
"[24] BaseAction.run(): ApiException: com.android.vending.api.ApiException: Error from backend. Request=com.android.vending.model.AssetRequest, Response=INTERNAL_SERVICE_ERROR
I/vending (16292): [1] BaseAction.displayErrorUi(): Server error in com.android.vending.MyDownloadsActivity$MyDownloadsLoader: com.android.vending.api.ApiException: Error from backend. Request=com.android.vending.model.AssetRequest, Response=INTERNAL_SERVICE_ERROR"
Any help would be appreciated.
Ta.
Click to expand...
Click to collapse
Sorry, no help from me but same issue since yesterday evening. CM7.1 final HTC Desire Market 3.1.5. Hope omeone will post a solution, i tried delete cache/data, install old market, restore links with titanium backup and rom toolbox. With market 2.3.6 i got the server fail message like u, with 3.1.5 a blank screen. Will do also a logcat soon
There's another thread on this
http://forum.xda-developers.com/showthread.php?t=1273843
Boot problem
Hey guys
Since today I have this problem:
youtube/watch?v=CVQnRhazofk
I can still unlock it and use everything till it reboots.
Infos:
Android Version: 4.4.2
Kernel Version: 3.4.0-gac9222c
[email protected] #1
Wed Nov 20 14:50:44 PST 2013
Build Number: KOT49H
That's all I could find about my device.
I hope someone can help me fix this problem.
sasuke12096 said:
Hey guys
Since today I have this problem:
youtube/watch?v=CVQnRhazofk
I can still unlock it and use everything till it reboots.
Infos:
Android Version: 4.4.2
Kernel Version: 3.4.0-gac9222c
[email protected] #1
Wed Nov 20 14:50:44 PST 2013
Build Number: KOT49H
That's all I could find about my device.
I hope someone can help me fix this problem.
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you rooted? Installed a custom Rom? Kernel? Recovery?
What do you mean by bootloader unlocked? I didn't change anything. So no custom rom , not rooted etc.
I have the same problem, running 4.4.4 (KTU84P)
I'm rooted with Xposed + GravityBox, Xprivacy, and a couple others, but disabling Xposed didn't seem to help at all.
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
elbenny said:
I have the same problem, running 4.4.4 (KTU84P)
I'm rooted with Xposed + GravityBox, Xprivacy, and a couple others, but disabling Xposed didn't seem to help at all.
Click to expand...
Click to collapse
I flashed stock system.img and that didn't help either, so I can't blame root or Xposed.
Some googling found a few references to others with similar problems. One post mentioned quickly unlocking and disabling wifi (+ mobile data if you have it) stops the boot loops, and I was able to reproduce that. Unfortunately, a tablet with no internet access isn't very useful.
I've since tried flashing latest 5.1.1 (LMY48P) which did not boot loop. Maybe I will finally suck it up and move to Lollipop.
turning out the wifi really helped. It stopped to reboot but it's not really useful without internet
elbenny said:
I've since tried flashing latest 5.1.1 (LMY48P) which did not boot loop. Maybe I will finally suck it up and move to Lollipop.
Click to expand...
Click to collapse
Looks like I spoke too soon. 5.1.1 bootloops (earlier, though) if I restore my /data from 4.4.4 nandroid.
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
sasuke12096 said:
turning out the wifi really helped. It stopped to reboot but it's not really useful without internet
Click to expand...
Click to collapse
I agree, no wifi is pretty pointless and hopefully Google will come up with a proper fix.
I'd post the link but I can't yet, anyway you can search "Google product forums" for a thread called "Unable to start up nexus 7"
Maybe you can chime in over there too
This fixed it:
I haven't seen this on a Nexus 4 yet, but I had this happen last night on a Nexus 5 and got it fixed this evening. A call to T-mobile indicated that they haven't run across it yet either, but I found an XDA thread where they were seeing on a Galaxy S4. I'll post some steps for a somewhat tricky fix and then a write-up on what I think is happening based on what I found. Hopefully this will help.
1) Power off phone. Hold power button down until you see the Google logo come up and then disappear. That should stop the "boot loop" and keep the phone powered off. If it comes back on, try again and just hold the power button down a little longer than you thought you needed to.
2a) Steps 2-5 below can probably be replaced by putting the phone into airplane mode quickly while it's temporarily alive during the boot loop. If you put it into airplane mode and the boot loop stops, skip to step 6 and just disable airplane mode for steps 9/10.
2) Eject SIM card. You should have the little tool (round with a short, narrow point) that presses into a tiny hold on the side of the phone to eject the sim card. If you are uncertain on this step, get some help.
3) Power on phone. If you were connected to Wi-Fi when this started, it will still boot loop so we need to disable Wi-Fi as well. This is the tricky part. You may find it easy if you power off your wireless router before trying to turn off Wi-Fi on your phone.
4) Disable Wi-Fi as quickly as possible by swiping lock screen, pulling down the settings "drawer" at the top of the phone, clicking on wi-fi and click it off.
5) The phone should no longer reboot, but will start to reboot again if you give it a network connection (wi-fi or mobile) so don't reconnect it to the network until you are done with the next couple steps.
6) Go to Settings -> Apps and scroll over to ALL.
7) Scroll down to Google Services Framework and click it
8) Click on CLEAR DATA and hit Ok. I also hit CLEAR CACHE and while I'm not sure it's necessary, I recommend doing that as well.
9) Power off phone, re-install SIM card and power on phone.
10) Assuming you don't immediately go into a boot loop again, it's probably fixed. Re-enable wi-fi and go back to enjoying life
The trickiest part here is being fast enough to disable wi-fi before the reboot happens. It may be a non-issue if turning off the wireless router helps.
As a caveat, we haven't been running the phone for very long after clearing that data, but it's acting a little sluggish at times. I'm going to let it run for a day or two and then maybe do a full factory reset if it doesn't clear up. At the very least, the boot loop is gone.
------------------------------------------------
Now for the nerdy stuff in the hopes someone from the major providers and/or Google is watching this...
Late last night, I hooked up ADB to the phone after getting Wi-Fi disabled and USB Debugging enabled. A logcat dumped out a huge amount of data, but thankfully caught the reboot when I re-enabled Wi-Fi. Here's a partial dump from the log:
I/iu.SyncManager( 1201): NEXT; no task
I/CheckinRequestBuilder( 1201): Checkin reason type: 12 attempt count: 1
D/dalvikvm( 1087): GC_CONCURRENT freed 417K, 4% free 18384K/19056K, paused 2ms+2ms, total 19ms
W/dalvikvm( 744): threadid=13: thread exiting with uncaught exception (group=0x41564ba8)
E/AndroidRuntime( 744): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.bg
E/AndroidRuntime( 744): java.lang.NullPointerException
E/AndroidRuntime( 744): at android.content.PeriodicSync.syncExtrasEquals(PeriodicSync.java:150)
E/AndroidRuntime( 744): at android.content.PeriodicSync.equals(PeriodicSync.java:129)
E/AndroidRuntime( 744): at com.android.server.content.SyncStorageEngine.setPeriodicSyncTime(SyncStorageEngine.java:1625)
E/AndroidRuntime( 744): at com.android.server.content.SyncManager$SyncHandler.scheduleReadyPeriodicSyncs(SyncManager.java:2097)
E/AndroidRuntime( 744): at com.android.server.content.SyncManager$SyncHandler.handleMessage(SyncManager.java:1881)
E/AndroidRuntime( 744): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 744): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 744): at android.os.HandlerThread.run(HandlerThread.java:61)
I/Process ( 744): Sending signal. PID: 744 SIG: 9
I/ServiceManager( 176): service 'package' died
I/ServiceManager( 176): service 'batterystats' died
I/ServiceManager( 176): service 'usagestats' died
W/Sensors ( 1876): sensorservice died [0x7645fde0]
D/AndroidRuntime( 1087): Shutting down VM
many more services dieing
Note the null pointer exception in android.bg on a "PeriodSync" I don't know what that's supposed to do, but it clearly can only trigger with a valid network connection and it is very displeased with life. A search for some key words from the traceback led me to XDA (http://forum.xda-developers.com/showpost.php?p=62943303&postcount=2119). The symptoms matched what I was seeing and they mention going into Airplane mode to stop the boot loop which may be an even better approach than my somewhat heavy handed solution above. Speculation in that thread indicates a google apps update of some sort which I assume probably came through on my wife's phone last night with automatic updates.
Hello,
I keep getting the following error messages in the adb logs of my T800 every 5 seconds or so. I'm using the official 5.0.2 Android version supplied by Samsung.
[SDP.PUB_CRYPTOD] ERROR - Failed to open the netlink socket with error: Protocol not supported
[SDP.PUB_CRYPTOD] ERROR - Exiting
What can I try to solve that issue, or at least to stop the system from trying to relaunch the failing sdp_cryptod daemon?
I'm getting the same error all the time, and when it happens I cannot access Internet... Did you figure it out?
Are you using encryption?
Hi guys,
SO I have no idea how to solve this issue. I'm running Viper ROM and everything works perfect, if I switch to any other ROM Resurrection Remix, Dirty Unicorns, AIPC it installs fine and boots no problem, but in the initial setup when I pick a wifi Network (or LTE) it sticks on the "Checking Network - adding a few finishing touches, this may take a minute (or something)" screen.
If I choose don't use network and setup later, the ROM boots fine but all google services Play store, Gmail, anything it goes to a white screen that says "error contacting Google servers - Please try again later"
I have NO Idea what to do, I have used RR ROM for quite a while a few releases back with no issues and I have a hunch my trouble started after Linage OS became a thing, everything seemed fine before that. If anyone has had this issue or can offer any help it would be really really appreciated!
I'm using a International HTC 10 on the canadian Bell network. I'm still using the MM firmwear but multiple people have confirmed these ROMS work fine on MM Firmwear.
PLEASE HELP!!!
Thanks
John
I just installed Lineage OS, and have exactly the same problem. Can't complete "adding a few finishing touches" completing setup using network, if I skip that step and try to do anything needing a Google account I get the message about connecting to Google servers.
I did notice using adb logcat when I try to add a google account this message:
Code:
]02-02 18:13:48.903 5041 8347 E CheckinTask: Checkin failed: https://android.clients.google.com/checkin (request #0): java.io.IOException: Rejected response from server: invalid hardware identifier: "HTC 10 (unknown international)" is not a valid device
cumber said:
I just installed Lineage OS, and have exactly the same problem.
Code:
]02-02 18:13:48.903 5041 8347 E CheckinTask: Checkin failed: https://android.clients.google.com/checkin (request #0): java.io.IOException: Rejected response from server: invalid hardware identifier: "HTC 10 (unknown international)" is not a valid device
Click to expand...
Click to collapse
I've heard that different versions of Gapps will make a difference but I've tried them all... I have no Idea what to try. Are you on MM Firmwear?
Google apparently started rejecting devices with bogus device ids. I have changed, and will soon push, a change to fix that for lineage. Other ROMs will likely include all my changes in their next build.
Recently was installing an app that required permissions that need the password to give - a VPN (a trusted one) - and when I inputted my pin it lagged for a moment and then said settings has stopped. so I tried just changing my password which I had done just a few days before and it also crashed. so I tried a few times and restarted a few times and checked for updates and I cleared settings cache and I uninstalled the VPN and I tried all of the above again but still, it kept stopping no matter what I tried. I looked at the summary and it seems that it is trying to verify on a null object reference or something like that - I will copy it below. any suggestions on how to fix this?
error summery
------------------
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:353)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int com.android.internal.widget.VerifyCredentialResponse.getResponseCode()' on a null object reference
at android.os.Parcel.readException(Parcel.java:2022)
at android.os.Parcel.readException(Parcel.java:1962)
at com.android.internal.widget.ILockSettings$Stub$Proxy.checkCredential(ILockSettings.java:642)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:370)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:422)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:409)
at com.android.settings.fj.doInBackground(LockPatternChecker.java:133)
at com.android.settings.fj.doInBackground(LockPatternChecker.java:130)
at android.os.AsyncTask$2.call(AsyncTask.java:333)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more
Facing same issue. Any fixes on this?
viveksuryavanshi said:
Facing same issue. Any fixes on this?
Click to expand...
Click to collapse
Or any suggestions on why this happened.