Develop Bugs

[Problem] Unknown reason for force close

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?

Random reboot on LG G4 H815 after factory reset/update to V10C

Hello all,
After a factory reset or an update to V10c (update was available immediately after factory reset) my G4 keeps rebooting at random moments. I saved an logcat log to my computer via ADB which I will add as an link because it exceeds the forum limits. Personally I suspect the following error:
Code:
E/SQLiteDatabase( 7825): Failed to open database '/data/data/com.google.android.apps.messaging/databases/bugle_db'.
on line 44088 but I don't know for sure. I tried removing all SMS messages but one of them keeps returning after I deleted it.
I would like to get rid of this problem as soon as possible. Also, when booting back up I get an error message 'Unfortunately MirrorLink has stopped'.
Anyone?
Thanks in advance,
kvanzuijlen
Link to logcat adb log: https://www.dropbox.com/s/yw43mnxhjuec607/logcat.txt?dl=0

[T800] recurring SDP.PUB_CRYPTOD errors in log

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?

Messaging crashing repeatedly on upgrade from CM 12.1 to CM 13 - Permissions? SOLVED

Code 14: Could not open database. Some sort of permissions problem?
I have had CM 12.1 on a Nexus 5 for a while. Every time I upgraded to CM13 everything would work fine EXCEPT messaging would keep throwing "Sorry, messaging has stopped" message. So I Stayed on CM12.1. I just upgraded to a Nexus 5X and there is no CM12.1 for it so I tried Cm13 (Latest Nightly 6-18) and it seemed to work fine, just on WiFi and setting it up. I loaded what I always do, Android Firewall, checked all my permissions in Privacy Guard, used SU2.95 so I would have root. It still worked fine connected to my WiFi. I just got back from TMobile where I had to switch from MicroSIM to NanoSIM. put the sim in and the same messaging error shows up. So, working backwards, I unchecked ALL privacy guard, turned OFF the firewall, and rebooted. Still gives me the messaging error. So, I finally read the error message and its SQLite Error 14 on some database. Any ideas what I could try next? I suppose I can reload CM and set it all up again, and see where it starts to fail but that would be throwing away 4 hours from yesterday. I'm also not certain that the native App permissions aren't involved somehow. The phone IS encrypted but I have tried it both ways in the past.
I know there are all sorts of geniuses on here, and I am not smart enough.
Code:
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: android.database.sqlite.SQLiteException: unknown error (code 14): Could not open database
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:179)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:421)
at android.content.ContentResolver.query(ContentResolver.java:493)
at android.content.ContentResolver.query(ContentResolver.java:435)
at com.android.messaging.util.f.oH(SourceFile:53)
at com.android.messaging.util.f.doInBackground(SourceFile:34)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 4 more
EDIT : so i got into App permissions (new to MM?) and made sure the messaging service had storage and read and write on SMS. still looking deeper and searching the net...
EDIT : APN issue? reset to default TMobile settings and rebooted. still fails.
EDIT : could it be that I used the PICO version of OpenGAPPS? anyone had a problem with that? been searching still...
SOLVED : I'm such an idiot. I have been moving my blacklist.db database from version to version so I dont have to put all the numbers in again (wouldn't it be nice if there was a blacklist manager? I have all these spam numbers attached to a contact but you still have to choose them one by one) and of course between CM 12.1 and CM 13 they changed the database format or something so thats why it was crashing. Just one of the many steps I took getting my new phone set up.

If you pull SIM card out of the phone, does the crash still happen?

Stuck on "Checking Network" setup screen on all non sense roms

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.