Database Develop

[SOLVED]Phone crashes on boot

I am not sure why I am experiencing this problem. My phone was working fine last week, then I flashed xTHEME v1.2 on cm 4.0.4 and my phone gets stuck at the 2nd bootscreen. I wiped, then flashed 4.0.4 again and I can boot normally, but then it happened again today. Logcat below, hopefully someone can explain the error.
http://pastebin.com/f362fbdc3
Lemme know if you need more information

Code:
E/AndroidRuntime( 4678): Uncaught handler: thread android.server.ServerThread exiting due to uncaught exception
E/AndroidRuntime( 4678): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 4678): java.lang.IndexOutOfBoundsException: Invalid location 1, size is 1
E/AndroidRuntime( 4678): at java.util.ArrayList.get(ArrayList.java:353)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.readStateFromFileLocked(AppWidgetService.java:972)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.loadStateLocked(AppWidgetService.java:750)
E/AndroidRuntime( 4678): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:125)
E/AndroidRuntime( 4678): at com.android.server.ServerThread.run(SystemServer.java:346)
uncaught exception there right before everything crashes.... do you have any widgets installed?

The only widgets I use are Weather Widget - Donate + addon, GPS OnOff, and tCalendar.

unknown.soul said:
The only widgets I use are Weather Widget - Donate + addon, GPS OnOff, and tCalendar.
Click to expand...
Click to collapse
Try to disable them, boot up, reenable them one by one to see whats causing it to happen. I can't see anything else in the log that could be the cause of it, but im not an expert

tCalendar seemed to be the culprit and I found out that tCalendar != tCalendarWidget. The former is not for 1.5, but according to the market description it should be compatible. Thanks for isolating the issue from that log.

unknown.soul said:
tCalendar seemed to be the culprit and I found out that tCalendar != tCalendarWidget. The former is not for 1.5, but according to the market description it should be compatible. Thanks for isolating the issue from that log.
Click to expand...
Click to collapse
no problem, glad to see you got it to work. I thought that would be an app problem to cause trouble because I used the other two on cyans exp. builds. Hadn't heard of the tcalendar app.
Thanks for providing links to the app, it makes it much more useful for someone searching for an answer to find one. Also, could you edit the thread title to include [SOLVED] ?
btw it wasnt the tcalendar widget itself, but the tcalendar app? thats weird. does it have a widget of its own packaged with the app?

It's just a name difference, tCalendar is only a widget.

Appmanager crash

Anyone know what could be causing this? Appmanager Pro is crashing when I try to launch it. Only thigns on my phone are Cyan 4.25 and the navigation_update.zip.
Heres a logcat:
Code:
11-17 22:07:10.156 W/dalvikvm( 665): threadid=15: thread exiting with uncaught exception (group=0x4001e170)
11-17 22:07:10.156 E/AndroidRuntime( 665): Uncaught handler: thread Thread-9 exiting due to uncaught exception
11-17 22:07:10.166 E/AndroidRuntime( 665): java.lang.NullPointerException
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.FileUtils.getDirSize(FileUtils.java:171)
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.FileUtils.getDirSize(FileUtils.java:175)
11-17 22:07:10.166 E/AndroidRuntime( 665): at com.think_android.appmanagerpro.AppManagerPro$ResourceLoaderThread.run(AppManagerPro.java:449)
11-17 22:07:10.196 I/Process ( 143): Sending signal. PID: 665 SIG: 3
11-17 22:07:10.196 I/dalvikvm( 665): threadid=7: reacting to signal 3
11-17 22:07:10.326 I/dalvikvm( 665): Wrote stack trace to '/data/anr/traces.txt'
11-17 22:07:10.866 D/dalvikvm( 515): GC freed 528 objects / 294640 bytes in 128ms
11-17 22:07:12.036 I/Process ( 665): Sending signal. PID: 665 SIG: 9
11-17 22:07:12.066 I/ActivityManager( 143): Process com.think_android.appmanagerpro (pid 665) has died.
11-17 22:07:12.076 I/WindowManager( 143): WIN DEATH: Window{43938b48 com.think_android.appmanagerpro/com.think_android.appmanagerpro.AppManagerPro paused=false}
11-17 22:07:12.126 W/UsageStats( 143): Unexpected resume of com.android.launcher while already resumed in com.think_android.appmanagerpro
11-17 22:07:12.156 W/InputManagerService( 143): Got RemoteException sending setActive(false) notification to pid 665 uid 10038
11-17 22:07:14.886 I/XT9IME ( 351): [finishInput]
11-17 22:07:15.216 D/dalvikvm( 192): GC freed 2925 objects / 133408 bytes in 123ms

Has it been updated for 1.6? NullPointerException usually require looking through the code to troubleshoot lol. its probably not programmed well

B-man007 said:
Has it been updated for 1.6? NullPointerException usually require looking through the code to troubleshoot lol. its probably not programmed well
Click to expand...
Click to collapse
I'm thinking it has something to do with the update_navigation.zip I flashed cause I know it did something with the build.props and whatnot. And it also worked before I flashed this.

I don't use that but how much did it modify your build.prop?
does your phone say android 2.0 or is it still showing 1.6?

B-man007 said:
I don't use that but how much did it modify your build.prop?
does your phone say android 2.0 or is it still showing 1.6?
Click to expand...
Click to collapse
I believe it changed 1-2 lines and yes my phone still shows 1.6. I just looked at my app drawer to and it shows I have 2 settings apps, odd I'm going to restart my phone see if it goes away.

I hate to say this but it's not nav....
And I don't think it's CM4.2.5.
I know this because I was fine on a fresh install until I reinstalled all my other apps. Then I started getting crashes. I think it was a combination of advanced launcher,and google voice that started the misbehavior.
Maybe it's just one of them.
My solution was...
I dropped appmanager. I loved that program, but discovered that Astro can back-up your apk's too. It just doesn't uninstall existing apks.
But... advanced task manager does have an uninstall feature, and it allows me to slap mis-behaving programs around as well as services.
The simplicity of one program, replaced by the combination of 2 more powerful programs.
But hey, what do I care....I have Apps2sd!

[email protected] said:
I hate to say this but it's not nav....
And I don't think it's CM4.2.5.
I know this because I was fine on a fresh install until I reinstalled all my other apps. Then I started getting crashes. I think it was a combination of advanced launcher,and google voice that started the misbehavior.
Maybe it's just one of them.
My solution was...
I dropped appmanager. I loved that program, but discovered that Astro can back-up your apk's too. It just doesn't uninstall existing apks.
But... advanced task manager does have an uninstall feature, and it allows me to slap mis-behaving programs around as well as services.
The simplicity of one program, replaced by the combination of 2 more powerful programs.
But hey, what do I care....I have Apps2sd!
Click to expand...
Click to collapse
I sent a email to the dev with the situation and what not. but Google voice to me never interfered before with app manager. Hopefully I get it figured out soon cause appmanager made my life alot simpler ><, I am willing to try new things but if this gets repaired it would be greater!

i have all 3 google voice..nav..and app manager pro working.. just fine on mine..

Just to clarify...
I am almost certain it's not nav because I had stopped using app manager, before even thinking of adding nav to the system.
That didn't really come out in the first post.

http://code.google.com/p/cyanogenmod/issues/detail?id=744#c0
Issue with the latest mod
did you guys try reinstalling the app? maybe it requires additional permissions after the latest rom upgrade

B-man007 said:
http://code.google.com/p/cyanogenmod/issues/detail?id=744#c0
Issue with the latest mod
did you guys try reinstalling the app? maybe it requires additional permissions after the latest rom upgrade
Click to expand...
Click to collapse
Seems like im not the only one experiencing the issues though >< I guess I'll just try out astro

had the issue also and I had it before I decided to flash the update_navigation zip file so I know its not that... it was working then it stopped after something dont know what it is... didnt have a theme nothing completely fresh install wiped everything didn't have ext partition so its something weird

I got a hold of the dev and gave him a complete catlog. He released an update on the market and problem solved!

[Q] Browser won't work w/ SIM card in place, why?

Update:
I just happened to try this again with no SIM in the phone, using wifi, and the browser worked perfectly. I even had an email from last night stuck in the outbox, and it went right out. So, what is it about the SIM card that is preventing the browser, Gmail app, and maybe more, from connecting? I get data for the widgets, apps, suggested search, etc. As soon as I put the SIM in, all data to and from the browser & Gmail stalls out. What is it about having a SIM card in place that is killing connectivity to selected apps?
So, I've flashed a bunch of different ROMs and I simply can't get the web browser to function. At all. It just times out, period. Everything but the browser itself works fine. I posted this thread [XDA-Developers] about three months ago before I gave up and bought another phone. This is still bugging me though, and I want to learn how to fix it. I don't want to re-post all the troubleshooting steps again from the other post, so I've got the logcat and a screenshot of the browser. What am I missing?
Here's the logcat copy, it's also a an attachment below:
__________________________________________________________________
I/ActivityManager( 355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.android.browser/.BrowserActivity }
I/ActivityThread( 1613): Publishing provider contacts;com.android.contacts: com.android.providers.contacts.ContactsProvider2
I/ActivityManager( 355): Start proc com.android.browser for activity com.android.browser/.BrowserActivity: pid=1622 uid=10023 gids={3003, 1015, 1003}
I/ActivityThread( 1622): Publishing provider browser: com.android.browser.BrowserProvider
D/dalvikvm( 1613): GC freed 3240 objects / 245584 bytes in 278ms
W/ContactAggregator( 1613): No more aggregation requests
W/TabControl( 1622): Fail in restoreState, load home page.
I/ActivityManager( 355): Displayed activity com.android.browser/.BrowserActivity: 2424 ms (total 25427 ms)
I/WindowManager( 355): WIN DEATH: Window{43f7faf0 com.android.settings/com.android.settings.ApplicationSettings paused=false}
I/ActivityManager( 355): Process com.android.settings (pid 1309) has died.
I/WindowManager( 355): WIN DEATH: Window{43d9fb20 com.android.settings/com.android.settings.ManageApplications paused=false}
I/ActivityManager( 355): Low Memory: No more background processes.
I/ActivityThread( 1613): Publishing provider call_log: com.android.providers.contacts.CallLogProvider
D/Gmail ( 569): MailProvider.query: content://gmail-ls/labels/[email protected]/(null, null)
D/skia ( 355): purging 167K from font cache [16 entries]
D/dalvikvm( 355): GC freed 5859 objects / 258664 bytes in 919ms
I/ActivityManager( 355): Process android.process.acore (pid 1613) has died.
I/ActivityManager( 355): Low Memory: No more background processes.
D/dalvikvm( 569): GC freed 494 objects / 22544 bytes in 529ms
D/dalvikvm( 549): GC freed 1171 objects / 47768 bytes in 353ms
D/dalvikvm( 634): GC freed 186 objects / 7680 bytes in 447ms
D/skia ( 545): purging 68K from font cache [9 entries]
D/dalvikvm( 545): GC freed 789 objects / 35576 bytes in 987ms
D/dalvikvm( 792): GC freed 34 objects / 1200 bytes in 881ms
D/GpsLocationProvider( 355): NetworkThread out of wake loop
D/GpsXtraDownloader( 355): Downloading XTRA data from http://xtra1.gpsonextra.net/xtra.bin
I/ActivityManager( 355): Start proc com.levelup.beautifulwidgets for broadcast com.levelup.beautifulwidgets/.HomeWidget14: pid=1641 uid=10045 gids={3003, 3002, 3001, 1015, 1003}
D/WifiService( 355): ACTION_BATTERY_CHANGED pluggedType: 2
I/power ( 355): *** set_screen_state 0
D/WifiService( 355): ACTION_SCREEN_OFF
D/SurfaceFlinger( 355): About to give-up screen, flinger = 0x11f140
I/power ( 355): *** set_screen_state 1
D/WifiService( 355): ACTION_SCREEN_ON
D/SurfaceFlinger( 355): Screen about to return, flinger = 0x11f140
D/GpsXtraDownloader( 355): error java.net.SocketTimeoutException: Socket is not connected
D/dalvikvm( 355): threadid=119 wakeup: interrupted
D/GpsXtraDownloader( 355): Downloading XTRA data from http://xtra2.gpsonextra.net/xtra.bin
E/browser ( 1622): onReceivedError -6 http://www.google.com/m The connection to the server was unsuccessful.
D/dalvikvm( 1622): GC freed 7289 objects / 285672 bytes in 104ms
W/dalvikvm( 1622): JNI WARNING: DeleteLocalRef(0x43c204e8) failed to find entry (valid=1)
W/ActivityManager( 355): Activity idle timeout for HistoryRecord{43f74fe0 com.android.browser/.BrowserActivity}
D/GpsXtraDownloader( 355): error java.net.SocketTimeoutException: Socket is not connected
D/dalvikvm( 355): threadid=119 wakeup: interrupted
D/GpsXtraDownloader( 355): Downloading XTRA data from http://xtra3.gpsonextra.net/xtra.bin
D/GpsXtraDownloader( 355): error java.net.SocketTimeoutException: Socket is not connected
D/dalvikvm( 355): threadid=119 wakeup: interrupted
D/GpsLocationProvider( 355): NetworkThread wait for 299998ms
D/dalvikvm( 792): GC freed 4 objects / 152 bytes in 1693ms
I/ActivityManager( 355): Start proc com.android.settings for broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=1651 uid=1000 gids={3003, 3002, 3001}
I/ActivityManager( 355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.fede.launcher/.Launcher }
W/InputManagerService( 355): Starting input on non-focused client [email protected] (uid=10023 pid=1622)
I/ActivityManager( 355): Process com.levelup.beautifulwidgets (pid 1641) has died.
I/ActivityManager( 355): Start proc com.levelup.beautifulwidgets for broadcast com.levelup.beautifulwidgets/.HomeWidget14: pid=1657 uid=10045 gids={3003, 3002, 3001, 1015, 1003}
I/ActivityManager( 355): Process com.android.settings (pid 1651) has died.
D/dalvikvm( 545): GC freed 3603 objects / 312392 bytes in 109ms
I/ActivityManager( 355): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.term/.Term }
I/ActivityManager( 355): Start proc com.android.term for activity com.android.term/.Term: pid=1663 uid=10004 gids={}
E/Term ( 1663): onCreate
D/dalvikvm( 1663): Trying to load lib /system/lib/libterm.so 0x43bf4338
D/dalvikvm( 1663): Added shared lib /system/lib/libterm.so 0x43bf4338
I/Exec ( 1663): JNI_OnLoad
I/Term ( 1663): waiting for: 1669

Weird problem -> weird idea and possible solution!
Perhaps you have some kind of NAND error in the memory area where the browser app lies. This may sound kind of random, especially as it happens with different ROMs, but: I guess when installing a Rom, everything goes alphabetically. This means that the *a*pps folder goes first. It contais *b*rowser.apk which is installed as the third or 4th app. So it will be roughly in the same position for *any* Rom (Except the newer ones that contain ADWLauncher.apk).
You could try the following:
1) Install a ROM of your choice, best one of those that didn't work (just to test the theory...)
2) extract the browser.apk from the rom zip to /data/myapp/browser.apk on the phone
3) delete the original browser.apk in /system/app
4) create a symlink on the new browser.apk with 'ln -s /system/app/browser.apk /data/myapp/browser.apk'
5) Cross fingers and surf to google.com to see what happens
Plan B to test this: Install CM6 RC3 which contains ADWLauncher. If there is an error in your nand it should now affect the launcher instead of the browser, as the launcher is quite big...
€: If this really is the problem, you could use a custom version of Firerats MTD Patch to move your system partition a few MB so the defective area is not used anymore. It would cost you a few mb nand space, but everything should be fine then.

Thanks for the reply, mblaster. It looks like I edited my post as you were typing the reply.
For some reason, the one thing I never tried was using the phone with no SIM. I pulled the SIM out of my G1 and gave up in disgust again (this problem has been plaguing me for 3+ months now...). I put it in my new phone, and left the new one to charge. I powered the G1 back on, SIM removed, just for the heck of it.
Everything works perfectly with no SIM! Except I'm stuck using wifi, no calls or mobile data, obviously. I'm smart enough to guess this is an important clue, but not smart enough to identify and correct the root cause. I'll keep searching until I get it, or someone points out what is wrong.
I suspect this has something to do with the Google apps add-on, too. I can't get any ROMs to a stable boot if I flash the ROM and Google add-on zips together. I have to get the ROM loaded and running, then flash an older version of the add-ons to get my market & Gmail, etc. If I don't do it that way, I can't even get through the initial sign in, even to press the "skip" button to do it later. It's error after error until I just pull the battery. Not singling out any ROM in particular here, I've tried dozens of variations.
I hope this SIM clue is what helps me figure out what's wrong. I don't have a clue about the NAND on the phone, and I'd like to know how to check it's integrity, or flash a known good copy again in case it's become corrupted. Way over my head now, I'm going to read some more and search again.

Tiznom said:
...
I hope this SIM clue is what helps me figure out what's wrong. I don't have a clue about the NAND on the phone, and I'd like to know how to check it's integrity, or flash a known good copy again in case it's become corrupted. Way over my head now, I'm going to read some more and search again.
Click to expand...
Click to collapse
The NAND is the physical memory of your phone, like a harddisk on your computer. One way to check for errors could be to copy some files to your device and back and check if they are still the same.
You could e.g. "adb shell md5sum /system/app/browser.apk" (or any other file) and then compare it with an md5sum calculated from the browser.apk extracted from the .zip of the flashed rom file on your pc (need to get some extra software for that as windows can't do it out of the box).
If the numbers differ, there is definitely something wrong. Don't know if there is a better way to test this.
Still this does not explain why it works without a sim card, but this could be coincidence.
€: If you suspect the google addon, you can easily try to flash a rom without a google addon and see if everything works properly.

It's the Google add-ons somehow. I'm having all kinds of problems with Google sites reloading very quickly, and I don't have a clue how to correct it. I started out troubleshooting the phone and now it's worse. I've pulled the battery out of the G1 again and now I can use Google sites in my desktop browser fine.
I'll try comparing the md5 sums and see what I get. I'm using Ubuntu and I learned how to do it from troubleshooting the ROMs.
I think I'm looking at something I will never solve. I bought a second Android phone that I won't dare experiment with until I get all this sorted out. It's never been rooted and everything on it works perfectly. While I like the idea of rooting and experimenting, I still need a phone that will actually work. Plus, I can always revert the G1 to the stock un-rooted 1.6 ROM, it works fine. As soon as I try rooting, I get nothing but problem after problem.

I had this problem with my Magic on CM 5.0.8. It was the default APN settings that was causing the problem for me. I just manually added the essential APN settings and it worked. I'm on 2degrees mobile in New Zealand. This only happened with this sim, worked fine with a vodafone one.

Market downloads view fails

I just ran into an interesting problem and was able to solve it, I figured I'd post it here in case anyone else runs into it.
So I got my NC on Thursday and promptly rooted it on Friday morning, everything was smooth sailing until I started installing a bunch of apps and noticed that some things were randomly failing. Specifically baffling was the "Downloads" view in the market app. I used the Log Collector app to take a look at the logs and saw some exceptions like so:
12-21 12:08:54.890 E/AndroidRuntime( 1719): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: no such table: main.audio: , while compiling: SELECT album_art FROM album_info
12-21 12:08:54.890 E/AndroidRuntime( 1719): at android.app.ActivityThread.installProvider(ActivityThread.java)
Some snooping around revealed that there's a missing sql view in /data/data/com.android.providers.media/databases/internal.db. Sometime during NC startup some app tries to delete the view and rebuild it, but since the view was already gone it couldn't delete and therefore failed:
12-21 13:42:30.475 E/Database( 1867): Failure 1 (use DROP TABLE to delete table audio) on 0x2c50e0 when preparing 'DROP VIEW IF EXISTS audio'.
12-21 13:42:30.475 D/AndroidRuntime( 1867): Shutting down VM
12-21 13:42:30.475 W/dalvikvm( 1867): threadid=3: thread exiting with uncaught exception (group=0x4001b170)
12-21 13:42:30.475 E/AndroidRuntime( 1867): Uncaught handler: thread main exiting due to uncaught exception
12-21 13:42:30.491 E/AndroidRuntime( 1867): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: android.database.sqlite.SQLiteException: use DROP TABLE to delete table audio: DROP VIEW IF EXISTS audio
Solution - pull internal.db off the device, create a dummy view named audio in the database (I used Sqliteman on ubuntu) and push it back to the NC.
Reboot, problem fixed. Hope someone finds some use in this writeup.

App causes reboot

Hi guys
There's this app called buienalarm. It's really helpful, but sometimes it works and other times it causes the phone to soft reboot, crash and reboot. Events are happening in this order FYI. I have no idea what is causing this, but I used alogrec for record the logcat. Can someone tell me what's going on?

E/ ( 6050): netstack: STAT_HUB - App org.yoki.android.buienalarm isn't supported
W/dalvikvm( 1016): threadid=11: thread exiting with uncaught exception (group=0x41737658)
D/AdSDK ( 6050): ***** StartLoadContent, url=http://merlin.nakko.com/index.php?count=1&key=6&mcc=204&mnc=08&site=289&resizable=1&ua=Mozilla%2F5.0�%28Linux%3B�%3Bɷ殢❾�.3%3B�nl%3B஝詗�%2F12.1.A.1.205%29ʚ敹枛⨫�%2F534.30�%28KHTML%2C阩Ỹ果�%29嗪�%2F4.0㊆槶�%2F534.30&zone=1&request_counter=0&package_name=org.yoki.android.buienalarm&uid=WIFIMAC%3A00%3Aeb%3A2d%3A6c%3A79%3A96&android_id=b073a717e4807c87&bucket=%7B%7D
D/AdSDK ( 6050): ***** runWithHttpURLConnection, START HTTP EXECUTION
D/AdSDK ( 6050): ***** headerUserAgent=Buienalarm/121
D/AdSDK ( 6050): ***** runWithHttpURLConnection, END HTTP EXECUTION
E/AndroidRuntime( 1016): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 1016): java.lang.IllegalArgumentException: provider doesn't exisit: null

Another part of the log states:
I/ValueStore( 6050): Creating new value store instance
V/GCMRegistrar( 6050): Registering receiver
D/GCMRegistrar( 6050): resetting backoff for org.yoki.android.buienalarm
V/GCMRegistrar( 6050): Unregistering app org.yoki.android.buienalarm
D/dalvikvm( 6050): GC_FOR_ALLOC freed 2401K, 32% free 8577K/12496K, paused 15ms, total 16ms

Weird case you've got there.
I use Buienrader almost everyday and I have absolutly no issues.
From what I understand from the parts of the logcat it makes the system crash when loading content..

@mrjraider
You're using buienradar or buienalarm? Two different apps can you tell how I can get this back to work? Or who I should contact for this

Haha sorry, I do use both actually and also buienalarm gives no issues..

Can you recommend someone who I can contact with for this log?

I think no one because the buienalarm app hasnt been updated since january 2014

I mean who can figure out exactly what's crashing and how I can fix it