Database Develop

Need help LEARNING more!!!

I've been experiencing multiple ANR's so I tired to run an adb logcat and all i get is a scrolling "failed binder transaction". From what I can find, by searching, it has to do with rogue applications... I'm very new to this stuff, but I dont want to just ask for an answer or someone to hold my hand, I am here to LEARN.
If someone can help me understand what or where to look I would appreciate any type of help.
CLIFF NOTES:
(problem)
Market stuck loading or FC and ANR's
(what i've done)
-search
-wiped
-reformat ext3 partition
-cleared dalvik cache
-re-flash
-re-download
-Nand-BU, manually and through recovery
-run "fix_permissions"
(what I am running on the phone)
-Cyanogen 3.9.7
-Cyanogen 1.4 recovery
-8 gig Class 6
(what I am looking for)
-help
-to learn
-understand adb and fastboot better
-to be able to help others and myslef in the future
I'd also like to add I can run 3.8.6.1 completely STABLE. Once I flash 3.9.7 the everything reverts???
If you need me to give more info/backstory to my problem or have questions, links or answers I will appreciate it.
Thanks in advance,
Jay

Agh... good one. And you've done all the steps required. Send a log to Cyan (pm him) he should be able to help you.
In the mean time, try doing this
Flash last stable configuration that you had (make sure there's no theme)
Download 3.9.1, wipe, flash 3.9.1 and WITHOUT wiping flash 3.9.7.
From there, drop in console and clear your dalvik-cache and reboot.
Do you have comcache or linux-swap running? I would disable those as well for the time being until u stabilize
Good luck... let us know how it turns out.

Actually this seemed to work pretty well. last time I got results like this was when I wiped the EXT3 partition. Seems to be holding. I will report back later today and tomorrow morning. Thanks Borodin... I owe you considering you're the only one who has tried to help on this board. If you'd like me to donate something to any dev on your behalf let me know! Even if it ROM breaks again the offer still stands!
UPDATE: I can actually browse the market, but when I click to DL, it doesn't prompt into the notifaction bar.
Any takers on this one??? Market not prompting DL's to start

All~G1 said:
Actually this seemed to work pretty well. last time I got results like this was when I wiped the EXT3 partition. Seems to be holding. I will report back later today and tomorrow morning. Thanks Borodin... I owe you considering you're the only one who has tried to help on this board. If you'd like me to donate something to any dev on your behalf let me know! Even if it ROM breaks again the offer still stands!
UPDATE: I can actually browse the market, but when I click to DL, it doesn't prompt into the notifaction bar.
Any takers on this one??? Market not prompting DL's to start
Click to expand...
Click to collapse
@ All~G1 thanks for pointing me to this thread and even i had your problem..for me sometimes random times it wouldn't just download the app n show in the notifications bar but when i restart the phone it would automatically pop up the download n finish it off
and for me the market isn't even able to open..i just think that i screwed my database tho...even the browser has got same error .../databases/browser.db is null
For me probably a wipe would work but want to know if this is a bug in the rom or the app pls ?am going to skool right now so i'll come back n try to wipe n update the post
[highlight]NOTE: Am posting below my original post that i posted in the cyanogen rom thread[/highlight]

hey guys...i din update my g1 for a long time...just upgraded from 3.6.7.1 to 3.9.7 today i did the backup from the app backup for root users n everything went fine...i restored them after having done a wipe and installing 3.9.7 but market gimmes me a fc and it seems that assets.db din get restored...everything else got restored fine(sms,call log,etc)...i saw the error from the log which is below..i tried to browse the /data folder via astro but couldn't.
Code:
08-07 15:55:59.593 I/ActivityManager( 1378): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.android.vending/com.android.vending.AssetBrowserActivity} }
08-07 15:55:59.683 I/ActivityManager( 1378): Start proc com.android.vending for activity com.android.vending/.AssetBrowserActivity: pid=3317 uid=10006 gids={3003}
08-07 15:56:00.103 I/ActivityThread( 3317): Publishing provider com.android.vending.SuggestionsProvider: com.android.vending.SuggestionsProvider
08-07 15:56:00.353 E/Database( 3317): sqlite3_open_v2("/data/data/com.android.vending/databases/assets.db", &handle, 6, NULL) failed
08-07 15:56:00.363 D/AndroidRuntime( 3317): Shutting down VM
08-07 15:56:00.363 W/dalvikvm( 3317): threadid=3: thread exiting with uncaught exception (group=0x40019a68)
08-07 15:56:00.373 E/AndroidRuntime( 3317): Uncaught handler: thread main exiting due to uncaught exception
08-07 15:56:00.553 E/AndroidRuntime( 3317): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.vending/com.android.vending.AssetBrowserActivity}: android.database.sqlite.SQLiteException: unable to open database file
p.s trying to restore again with backup for root users failed...any suggestions please??
Would just pushing the file via adb or terminal work guys ??
The browser too fc's n gives me this error in logcat n followed by a bunch of other stuff
Code:
sqlite3_open_v2("/data/data/com.android.browser/databases/browser.db", &handle, 6, NULL) failed

@ All~g1 I read somewhere that sometimes the notifications dont come cuz of the gtalk service not logging in and stuff....so once check that too...hope tat helps....
[highlight]update on my condition:[/highlight]
i wiped it completely again and just when restoring deleted the files that werre causing the trouble i.e the asses.db n database.db n everything is fine...sorry about the posts guys if caused any problem with all the postings...hope this helps some1 else...

Dare{D}evil said:
@ All~g1 I read somewhere that sometimes the notifications dont come cuz of the gtalk service not logging in and stuff....so once check that too...hope tat helps....
[highlight]update on my condition:[/highlight]
i wiped it completely again and just when restoring deleted the files that werre causing the trouble i.e the asses.db n database.db n everything is fine...sorry about the posts guys if caused any problem with all the postings...hope this helps some1 else...
Click to expand...
Click to collapse
Did you erase .db manually or just by wiping??? if you did do it manually what was the commands you used to do so?

:::UPDATE:::
I finally broke down and used my barnd new sd card and to my amazement I have not seen one FC, ANR and my market is FLYING. I hope I dont jinx myself since its only been an hour. I figured it was worth a shot so worse case scenario get a new card.... I'll update again tomorrow!

All~G1 said:
Did you erase .db manually or just by wiping??? if you did do it manually what was the commands you used to do so?
Click to expand...
Click to collapse
just by wiping...then restored using backup for root users.....

Just an FYI.... before you guys wipe completly, try going into app management and clear the data from application that causing troubles (like market or google talk). A lot of times that will fix the problem and you will not have to set up your phone all over again. Also, if you it has anything to do with google - clear "google apps" data as well. Yeah, you will have to sign-in again but it's better then re-setting you phone again.
all~g1: if you feel like donating -donate to whoever is your rom builder (JF, cyan) I don't care. It seems like everyone is expecting donation for every little thing they do so I don't want to be behind I have a very limited knowledge though so I'd prefer to keep our pro's happy.
I don't always check these forums, you can gtalk to me if you have any problems
borodin79 a t g m a i l . com
Good luck.

Are there any detrimental effects from deleting .odex files?

I found that whenever I flash an updated ROM or apply some themes that quite a few of my apps stopped working and had to be re-installed, especially private apps. The fix has always been re-install. This drove me nuts as some of the apps required a reboot (i.e. mobiledefense) I took a look at my logcat and saw an error (sorry, don't have exact as I figured it out after closing the logcat) regarding a mismatch between odex and dalvik cache. I went through and deleted my app-private/*.odex files. They ALL started working without a reinstall. I have since gone through and removed all of my .odex files and have created a script to do so in assuming this could happen again.
I had a hard time figuring it out because it wasn't all apps, just some. What I discovered was the userinit.sh and user.conf here as a default set this:
odex_auto=1 # perform auto create or del odex for applications installed or removed within 3 days
So it would create .odex files within the parameters outlined. I've since turned it off.
I know .odex has something to do with optimization, and I noticed they are not re-created at any noticeable time. My question is, are there any detrimental effects from deleting them? Will it decrease performance or have any other ill effects on the applications?
If it actually helps performance, I can delete and rebuild them after I do a flash that has this issue. I just don't know if it is worth the effort.
Thanks for any input that may be coming!

Usually there isn't a problem deleting odex files since the system recreates them anyway, but on a similar note, instead of doing that, since you run latest Cyan recovery..go into console mode and type "FIX_PERMISSIONS", it should fix the force closes issues you may be having. This basically fixes the mismatch issues you may be having.

prash said:
Usually there isn't a problem deleting odex files since the system recreates them anyway, but on a similar note, instead of doing that, since you run latest Cyan recovery..go into console mode and type "FIX_PERMISSIONS", it should fix the force closes issues you may be having. This basically fixes the mismatch issues you may be having.
Click to expand...
Click to collapse
Thanks Prash. I've tried fix_permissions from the recovery console and even the new and improved one here previously, which I think is now integrated into Cyanogen's build with no luck. That's when I decided to look a little deeper. I don't know if it was a timing issue with the userinit being set the way it was, but deleting them always worked.
Question from this then for curiosity's sake. When do they get recreated? I have rebooted, updated (maybe not re-installed) numerous times and still don't have any new ones since disabling it in the userinit script.
I also remembered and re-found this, where Cyanogen himself said "Don't .odex your apps, it's a waste of time.".
So, I guess I'll start blowing them away Thanks!

Odex script and optimised donut build

Our devices don't have very much flash memory and it's easy to fill up /data with apps but here is a quick solution that can give you a bit more space.
In /data is a directory called dalvik-cache, this is a cache of the classes.dex from every app on the device, including those in /system.
On most android devices this doesn't happen, the system applications and the framework are stored as optimised dex files with a .odex extension.
People have spent a lot of time figuring out how to recreate the apks from the odex files and this is good if you have enough space to put all your apps on the device twice because it allows them to be easily swapped for theming.
The attached script goes through each app and jar in /system, creates an odex file and deletes classes.dex. It will give you about 30M extra space on /data while making /system about 10% bigger.
To run it do the following:
Backup you device
Make sure you have at least 15% free on /system, this is important because if you run out of space things will go badly wrong.
unzip odex.zip and then do:
adb push odex /data/odex
adb shell /data/odex/odex.sh
Wait till it finishes and then reboot the phone.
Another reason for odexing is that it boots very quickly and when testing kernels its nice not to have to wait too long.
If you want to see a simple odexed system try this:
http://www.mediafire.com/download.php?qjyniynyqzz
Rename it to androidinstall.tar and it will give you the donut system in the attached screenshots.
The main disadvantage of odexing is that it means you can't change the theme without reinstalling /system so find a theme you like before doing this to your device.
Thanks to Paul O'Brien for writing the original script.
Have fun.

dzo, once again, Thank you.
This should provide ALOT more breathing room in Eclair and Sense builds. Not to mention more flexibility for ROM devs too.
Thanks!

so would this only be useful for people who are making roms and stuff like that I'm kinda a noob still sorry

Unfortunately with my eclair build, /system is almost full
App2SD or /data on sd card look better
but that's device dependant
thank you for the tip anyway

I was about to ask if this will mess up the zipaligning but then I looked a the script and it also does zipaligning.

jadenj5 said:
so would this only be useful for people who are making roms and stuff like that I'm kinda a noob still sorry
Click to expand...
Click to collapse
The end user could run it, too...
Any thoughts on adding this to the install menu? That way you could install system, apply themes, then odex.

I updated the system tar in the first post to fix the broken calendar. I've been running this on my primary phone for a few days now and it seems much faster than it was. Perhaps there's are fewer file accesses with an odexed system and it needs to keep less data in the fs cache. Whatever the reason, give it a try.

is there anyway to do this from the phone without adb?

Include in vogue tools?
Thanks DZO, great that more performance can be squeezed out of our aging devices!
Just a thought: Could this be included in Vogue tools?

Two strange things with this build (on a Kaiser and I've added Wifi so maybe that has to do with it?)
- It never sleeps, I haven't run any Donut build for very long but I think I had this issue when trying the Warm Donut once.
If I turn off the screen (or if it times out by itself) this shows up in /dev/kmsg:
stop_drawing_early_suspend: timeout waiting for userspace to stop drawing
- When I run GPS Test and use the time screen the updates are irregular and sometimes skips a couple of seconds and sometimes several updates comes quickle after each other (with less than a second between them). I actually spent some time debugging my GPS code before I tried on eclair and realized it was not the GPS code that was causing it.
Perhaps both issues are related. I've a panel 1 Kaiser.
Other than that it feels very quick and snappy but no sleeping is terrible for the battery life.
Oh, and I tried turning off both wifi and background transfer but that doesn't help.

Tried this on Incubus's Tattoo and it got to HTCCamera.apk and failed:
Code:
--- BEGIN 'HTCCamera.apk' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3751
--- END 'HTCCamera.apk' --- status=0xff00, process failed
Unable to create '/tmp.odex': File exists
rm: cannot remove '/data/dalvik-cache/*': No such file or directory
It repeated Unable to create '/tmp.odex': File exists but i removed them from the code above because it's not necessary to have them in there 9473975394 times.
I rebooted and reinstalled the system to be safe.

preardon said:
Tried this on Incubus's Tattoo and it got to HTCCamera.apk and failed:
Code:
--- BEGIN 'HTCCamera.apk' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3751
--- END 'HTCCamera.apk' --- status=0xff00, process failed
Unable to create '/tmp.odex': File exists
rm: cannot remove '/data/dalvik-cache/*': No such file or directory
It repeated Unable to create '/tmp.odex': File exists but i removed them from the code above because it's not necessary to have them in there 9473975394 times.
I rebooted and reinstalled the system to be safe.
Click to expand...
Click to collapse
it might have something to do with most of the apk's already being odexed

I've posted an odex:ed and zipaligned CM5.0.7 port here: http://forum.xda-developers.com/showthread.php?t=700669
It also odexes every app in /data/app on boot (and clears the dalvik cache).

great donut build!
Thanks Dzo, you managed to pull together a great, snappy no frills donut build! it is fantastic on my Kaiser - and it is only a by-product of yet another great contributions of your! Thanks!

how is this donut build for use?

thoughtlesskyle said:
how is this donut build for use?
Click to expand...
Click to collapse
Great, I am using it daily on my kaiser at the moment. I understand that Kalt_Kaffe had problems with sleeping and battery life, but it works fine for me.

yea i shouldnt have the sleep and battery life problems because i run a vogue and they do things a little differently.
i wish i wasnt changing builds like every other day anymore

this is an excellent vanilla donut build dzo. it's very responsive and stable running from my sd card on the vogue so far. i really like myn's warm donut rom but it would frequently lock up requiring a restart; not the case with this build. thanks.
edit: is it possible to run the odex script again considering that i've been funning this build on my sd card? i wanted to odex the additional apps i added since the first install. also, would i have to manually remove the odexed files after updating an apk?

Had this running for a day on my old Kaiser and it's nearly as fast as my Hero! Fantastic work! Thanks!

This is the "snapiest" android build I have run on my vogue.
loving it thus far.

CM7.0.3 any non-stock keyboard instantly force closes

so I really need thumb keyboard, or for that matter anything other than the stock keyboard. in cm7.0.3 (fresh wipe), literally as soon as I switch to any keyboard other than the stock keyboard, it instantly force closes and continuously keeps force closing until i switch back to the stock keyboard. the same thing happens on the latest nightly build (86). anyone else had this issue?
things tried that didnt work:
thumb keyboard is installed in system/app
tried clearing the data on thumb keyboard
fixed permissions in CWM.
re-partitioned to 2048 / 0

did You try to clear data and cache on thumb keyboard? or to move it to system/app instead of user apps?

I already moved it to the system/app folder (it wont let me even come close to use it unless its in system/app). and I just tried clearing the data (there wasnt any cache to clear) and nothing changed.

You might want to fix permissions in clockworkmod. That will often fix recurrent force closes.

raphenucleus said:
You might want to fix permissions in clockworkmod. That will often fix recurrent force closes.
Click to expand...
Click to collapse
fixing permissions did not fix this problem. gahhh I really like CM7 but I NEED thumb keyboard.

Funny that you are having such troubles. With CM7 and other built form scratch type of ROM's, I have never had issues with Thumb Keyboard. I don't even need to put it in system.
Maybe try a fresh format and reinstall of your rom. Maybe even nvflash to stock and repartition the SDCARD. I know it seems extreme, but that will probably work bc soo many people use thumb keyboard on CM7 and its variants.

I'm running CM 7.0.3 on one of my gTabs and also installed Thumb Keyboard straight from the Market without any tweaking or moving it to this folder or that folder and it works fine for me.

ramerco said:
Funny that you are having such troubles. With CM7 and other built form scratch type of ROM's, I have never had issues with Thumb Keyboard. I don't even need to put it in system.
Maybe try a fresh format and reinstall of your rom. Maybe even nvflash to stock and repartition the SDCARD. I know it seems extreme, but that will probably work bc soo many people use thumb keyboard on CM7 and its variants.
Click to expand...
Click to collapse
I nvflashed to stock, but it went into a bootloop for some reason. I was able to nvflash clockworkmod on it so I was able to save myself from being bricked but after that, I wiped and re-partitioned but still no dice. here is the error line from the log:
W/dalvikvm( 1607): No implementation found for native Lcom/beansoft/keyboardplus/BinaryDictionary;.openNative (Ljava/nio/ByteBuffer;II)I
D/AndroidRuntime( 1607): Shutting down VM
W/dalvikvm( 1607): threadid=1: thread exiting with uncaught exception (group=0x40015560)
I/Process ( 1607): Sending signal. PID: 1607 SIG: 9
W/KeyCharacterMap( 1596): No keyboard for id 0
W/KeyCharacterMap( 1596): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

really? no one else has this issue???

[Q] - Is my phone allergic to JVR?

I've been having an issue when attempting to flash DLev 5.0 or Apex 9.2. This particular issue never happens when I flash back to Mosiac V.
What happens:
Initially everything looks good on either ROM. I push a few apps to my phone via TiBu and/or Market, great. Then I reboot...when I come back up, any app that I got from the Market or restore via TiBu show up as a generic android icon with the letters 'SD' on the icon. This is true either in the App Drawer or the homescreen. Apps that come with the ROM are fine.
When I attempt to launch the app in this state I get these results:
On Apex I get tiny pop up -> The application is not installed.
On Dlex I get a GMail compose message to the tw4 developer->message below *
I have tried all the following, all are no joy:
- Change launcher and reboot
- Convert to Voodoo ext4
- Re D/L the .zip with the ROM on it
- Flash to DarkCore 2.9 (which I've been using fine on Mosiac V)
Apps that I move to SD card before the reboot ARE there and available for use after the reboot...obviously not all apps can be moved from the phone.
My flashing process is consistently wipe Dalvik, wipe cache partition, wipe data/factory reset, and then flash. Like I said, doesn't happen on Mosiac V which I'm also flashing via .zip everytime (not Nandroid).
Thanks in advance...this has been a very vexing issue.
* Error message referenced above:
tw4 launcher bugreport - stacktrace SGH-I897 v1.4.3
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.noshufou.android.su/com.noshufou.android.su.Su}; have you declared this activity in your AndroidManifest.xml?
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1405)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1379)
at android.app.Activity.startActivityForResult(Activity.java:2827)
at com.sec.android.app.twlauncher.Launcher.startActivityForResult(Launcher.java:2239)
at android.app.Activity.startActivity(Activity.java:2933)
at com.sec.android.app.twlauncher.Launcher.startActivitySafely(Launcher.java)
at com.sec.android.app.twlauncher.MenuManager$4.onClick(MenuManager.java:3233)
at android.view.View.performClick(View.java:2538)
at android.view.View$PerformClick.run(View.java:9152)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3687)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
at dalvik.system.NativeStart.main(Native Method)

look in those rom zips, is there a /data folder?

studacris said:
look in those rom zips, is there a /data folder?
Click to expand...
Click to collapse
Yes, both do at the root of the zip whereas Mosiac V zip does not...do I move this folder elsewhere and repack the zip?
Thanks!
Sent from my GT-I9000 using XDA App

Take all the apps in the data folder and put them in /system/app delete the data folder, grab the meta-INF folder from mosaic and replace it with the one in those.
We had the same problems with the data folder, that's why it's not in mosaic.

studacris said:
Take all the apps in the data folder and put them in /system/app delete the data folder, grab the meta-INF folder from mosaic and replace it with the one in those.
We had the same problems with the data folder, that's why it's not in mosaic.
Click to expand...
Click to collapse
Thanks Studacris, I will try that. Just so I am clear, do I grab the whole meta-INF folder from Mosiac zip and swap with the meta-INF from one of the other zips? I shouldn't need to keep anything in the meta-INF folder that I'm replacing?
Thanks again.

Yes, the whole folder.
Or I guess you can go into com/google/android and just transfer the updater-script. From mosaic to whichever rom...
either one should work.

studacris said:
Yes, the whole folder.
Or I guess you can go into com/google/android and just transfer the updater-script. From mosaic to whichever rom...
either one should work.
Click to expand...
Click to collapse
Okay, pasted all apps from /data, deleted data, and copied over entire meta-INF from the Mosiac V zip file...is repackaging zip now.
Thanks and I'll let you know how this works!

Solution!
Studacris is right on the money. This solution worked!
Took some time unpacking the zip and re-packaging into zip (did it all on my phone) after making the necessary edits, but my issue is now resolved.
Studacris and Team Phoenix FTW!!!

I am having the same problem, can I use mosaic VI ? I can not find download link for version V

Yeah, its the same script.
btw Madtowndave i'm kind of impressed you did that all in your phone, good job

Worked perfect! Thank you!!
Hopefully this fix will be included in future updates.

Another solution that can fix most issues with ROM's. Any time you're having problems with a install(your issue is a great example) a practice that people are forgetting about is Flash back to stock/Master Clear. It will remove ANY software based issues like this(Not to disregard studacris's fix in any way)

I thought about that too but was not sure about going back to stock with Gingerbread bootloaders installed.

typ44q said:
I thought about that too but was not sure about going back to stock with Gingerbread bootloaders installed.
Click to expand...
Click to collapse
When I change roms, I ALWAYS fts/mc then flash the new ROM. It gives me a clean slate, and ensures no left over stuff. Might not be necessary completely, but that's how I do it
Sent from a autonomous device