Related
First off, I'll be honest - I'm not 100% certain this is the correct place for this, so apologies in advance if it isn't.
For all sorts of reasons I decided to downgrade my Wildfire from CM7 (2.3.3) to the last official rom (2.2.1).
I did the usual wipe alongside titanium backups and reinstalled the old rom.
A little after restoring my backups, I realized SQLite databases weren't restored properly.
So obviously, being the geek that I am, I dug in and realized that CM7 uses SQLite 3.7 while the other rom uses 3.6, and the database files aren't backwards compatible.
This leaves two options:
1. Upgrade libsqlite on the old rom
Which would save all sorts of DB conversions but I can't figure out how to do it, I assume all sorts of files are linked against a specific version of libsqlite, in which case it will be very complicated.
2. Convert all the DB files down to 3.6
I decided to go that route.
I wrote a small script that used sqlite to dump the databases back to sql statements and then recreate them using sqlite 3.6.
Everything seemed to work, but when I replaced the actual files in /data/data I ran into this exception
(taken from XBMC remote but happens with other apps):
Code:
E/Database( 1561): Failure 1 (table hosts already exists) on 0x26cc90 when preparing 'CREATE TABLE hosts (_id INTEGER PRIMARY KEY,name TEXT,address TE
XT,http_port INTEGER,user TEXT,pass TEXT,esport INTEGER,timeout INTEGER,wifi_only INTEGER,access_point TEXT,mac_addr TEXT,wol_port INTEGER,wol_wait IN
TEGER);'.
E/SQLiteOpenHelper( 1561): Couldn't open xbmc_hosts.db for writing (will try read-only):
E/SQLiteOpenHelper( 1561): android.database.sqlite.SQLiteException: table hosts already exists: CREATE TABLE hosts (_id INTEGER PRIMARY KEY,name TEXT,
address TEXT,http_port INTEGER,user TEXT,pass TEXT,esport INTEGER,timeout INTEGER,wifi_only INTEGER,access_point TEXT,mac_addr TEXT,wol_port INTEGER,w
ol_wait INTEGER);
....
E/AndroidRuntime( 1561): java.lang.RuntimeException: Unable to start activity ComponentInfo{org.xbmc.android.remote/org.xbmc.android.remote.presentati
on.activity.HomeActivity}: android.database.sqlite.SQLiteException: Can't upgrade read-only database from version 0 to 4: /data/data/org.xbmc.android.
remote/databases/xbmc_hosts.db
Which, I figure means it couldn't lock the DB file, probably to permission issues.
But in addition to running the well known fix_permissions script, I actually observed the permissions of a newly created xbmc_hosts.db (by removing the old one) and compared them to mine, they appeared to be the same but still mine crashed and the other one worked flawlessly.
I must be missing something stupid, but I can't for the life of me figure out what it is.
Any ideas (or pointers as to how I can upgrade the SQLite library) in the rom would be appreciated.
Thanks
Hi there,
I think the title of the topic is quite explicit. The first time I encountered this issue was on MIUI rom. So I thought it will be solved by flashing the stock rom but it's still there. What could be the cause of this problem and how can I solve it ? Thanks
Try to flash stock rom with RSD lite
http://forum.xda-developers.com/showthread.php?t=753170
That's what I did but the problem is still there :s
The class of the card has a lot to do with the write speed and may cause some interuption, which can cause a reboot, although unlikely. If you are using the Class 2 that came with the phone, maybe try a higher one and see if that helps out. They come in 2,4,6,10 and the price goes up with the higher class. 4 seems to be a good all around general purpose class. I would say that it is either something to do with your SDcard or maybe the sensors/ buttons in the phone that don't like that function.
Do you have more info on how it happens?
When you reboot, do you have in your media gallery a grey box with an ! inside and triangle icon in you notification bar?
Hi
Well I have a class 4 sd card so I think it's ok. About the issue, it occurs whenever I launch an app which needs the camera (or the flash of the camera).
About the gallery, I saw none of the things you mentioned.
Thats weird... will be software compatibility? What stock rom you flash?
Sent from my Milestone using XDA App
qnguyen88 said:
Hi there,
I think the title of the topic is quite explicit. The first time I encountered this issue was on MIUI rom. So I thought it will be solved by flashing the stock rom but it's still there. What could be the cause of this problem and how can I solve it ? Thanks
Click to expand...
Click to collapse
I had these issues today running on the XDA special. it would freeze then reboot when trying to use the camcorder. i was able to use it and record but it happened 3 times. I didn't used to have this problem with 2.1 or the builds from Dexter's i don't think at least I don't remember it ever happening. It happened first just from loading the cam and not recording yet.
Ps... it does seem to be an issue with the Sdcard or how the phone interacts with it though https://supportforums.motorola.com/message/310526
Seems to be an issue no matter what ROM we are on. Really it's one of the bugs Motorola should have fixed. Has anybody ever heard an excuse why they dropped support? It's really messed up when they sold the phone on how great the camera is and it turned out to be crap!
DarkMD said:
Thats weird... will be software compatibility? What stock rom you flash?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
I used the stock rom from france. Maybe I should try another one
Edit : I've just tried the UK Rom : same result :s
qnguyen88 said:
I used the stock rom from france. Maybe I should try another one
Edit : I've just tried the UK Rom : same result :s
Click to expand...
Click to collapse
Try to use SouthEast Asia... im using that
Sent from my Milestone using XDA App
I had a simular issue flashing back to stock & reformating my sd card fixed it for me.
Similar problem
I have the same problem, on opening anything that uses the camera or camcorder the phone reboots, what i've tried sofar;
-wiping cache
-wiping data
-changing roms, XDA special, MIUI, XDA RC2 , Cyanogen
-reflashing singapore sbf
-flashing uk sbf
-Reformating sd card
-launching camera with sd card out
-changing camera settings from androidiani OR
none of the above worked.
I got the stuff below by doing adb logcat, dunno if it anyone can find the problem in there, HELP!!!
Code:
D/AnalogClock( 1438): BroadcastReceiver() act = android.intent.action.TIME_TICK
I/ActivityManager( 1378): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.motorola.Came
ra/.Camera }
I/ActivityManager( 1378): Start proc com.motorola.Camera for activity com.motoro
la.Camera/.Camera: pid=1843 uid=10010 gids={1006, 3003, 1015}
I/dalvikvm( 1843): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
I/WindowManager( 1378): Setting rotation to 1, animFlags=0
W/SurfaceFlinger( 1378): timeout expired mFreezeDisplay=1, mFreezeCount=0
I/ActivityManager( 1378): Config changed: { scale=1.0 imsi=502/12 loc=en_SG touc
h=3 keys=1/1/2 nav=1/2 orien=2 layout=34}
I/dalvikvm( 1843): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=42)
D/PhoneApp( 1431): updateProximitySensorMode: state = IDLE
D/PhoneApp( 1431): updateProximitySensorMode: lock already released.
D/MotoCamera Engine Proxy( 1843): new Cam Utility instance
D/MotoCamera( 1843): Camera:onCreate:Enter onCreate 1314179342346
D/LocationManager( 1843): Constructor: service = android.location.ILocationManag
[email protected]
D/MotoCamSetting( 1843): CamSetting:load:load
V/MotoCamSetting( 1843): CamSetting:load:get preferences
D/MotoCamSetting( 1843): new CamSetting instance
D/ ( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_pref_flex.xml.bak': No such file or directory (errno=2)
D/ ( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_pref_loadsetting.xml.bak': No such file or directory (errno
=2)
D/MotoCamera( 1843): Check caller returns true
E/MotoCamera( 1843): in initView
D/dalvikvm( 1843): GC freed 2214 objects / 207360 bytes in 58ms
E/FocusView( 1843): in initFocusView,
D/dalvikvm( 1843): GC freed 368 objects / 16784 bytes in 48ms
D/dalvikvm( 1843): GC freed 111 objects / 5200 bytes in 99ms
D/dalvikvm( 1843): GC freed 9 objects / 352 bytes in 44ms
D/dalvikvm( 1843): Trying to load lib /system/lib/libsoundpool.so 0x0
D/dalvikvm( 1843): Added shared lib /system/lib/libsoundpool.so 0x0
D/SensorManager( 1843): found sensor: KXTF9 3-axis Accelerometer, handle=0
D/SensorManager( 1843): found sensor: AK8973 3-axis Magnetic field sensor, handl
e=1
D/SensorManager( 1843): found sensor: AK8973 Temperature sensor, handle=3
D/SensorManager( 1843): found sensor: SFH7743 Proximity sensor, handle=4
D/SensorManager( 1843): found sensor: Orientation sensor, handle=2
D/SensorManager( 1843): found sensor: LM3530 Light sensor, handle=5
V/MotoCamera( 1843): Camera:onCreate:finish onCreate 1314179343245
D/MotoCamera( 1843): Camera:onStart:Enter onStart 1314179343246
V/MotoCamera( 1843): Camera:onStart:finish onStart 1314179343255
D/AudioHardwareMot( 1138): AudioMgr:bufSize from kernel = 8192
D/MotoCameraGlobalTools( 1843): zoom value 1.0
D/MotoCameraGlobalTools( 1843): resolution : 8.0
D/MotoCameraGlobalTools( 1843): remaining : 5837
D/ ( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_preferences.xml.bak': No such file or directory (errno=2)
D/dalvikvm( 1843): GC freed 443 objects / 49080 bytes in 47ms
V/MotoOnScreenController( 1843): OnScreenController:initTagsSet
V/MotoCamera( 1843): mController.show()
D/MotoOnScreenController( 1843): OnScreenController::rightSetFadeIn:
V/MotoCamera( 1843): ----OnResume, restartPreview-----
V/MotoCamera( 1843): Enter restartPreview
V/MotoCamera( 1843): surfaceView's width or height = 0
V/MotoCamera( 1843): ------------------------------
V/MotoCamera( 1843): getCameraStartMode-0
V/MotoCamera( 1843): ------------------------------
D/Sensors ( 1378): using sensors (name=sensors)
V/MotoCamera( 1843): Camera:onResume:finish onResume 1314179343760
D/MotoCameraGlobalTools( 1843): zoom value 1.0
D/MotoCameraGlobalTools( 1843): resolution : 8.0
D/MotoCameraGlobalTools( 1843): remaining : 5837
D/MotoCamera( 1843): onWindowFocusChanged:: hasFocus true
W/IInputConnectionWrapper( 1438): showStatusIcon on inactive InputConnection
V/MotoCamera( 1843): mSurfaceHolderCreating:------------------true
I/ActivityManager( 1378): Displayed activity com.motorola.Camera/.Camera: 2594 m
s (total 2594 ms)
D/dalvikvm( 1843): GC freed 810 objects / 37120 bytes in 88ms
D/MotoCamera Engine Proxy( 1843): CameraUtility:android.hardware.Camera.open()
D/CameraService( 1138): CameraService::connect E (pid 1843, client 0x24c40)
D/CameraService( 1138): Client::Client E (pid 1843)
D/CameraHal( 1138): CameraSettings constructor
D/CameraHal( 1138): CameraHal constructor
D/CameraHal( 1138): Software ID 2.1-update1
I/HPAndroidHAL( 1138): Version 4115. 4115STBr Build Time: 2010-02-19 10:24:19.
I had problems with the cam causing the [phone to reboot when the OC seetings where to high....
What are you Over Clocked @?
I am not very versed at reading Logcats but does this have anything to do with it, (com.motorola.Camera_pref_loadsetting.xml.bak)?
Usually when we don't want the phone to recognize an app we rename it .bak instead of .apk? Just a though b/c there are .baks all over that Logcat.
hellmonger said:
I had problems with the cam causing the [phone to reboot when the OC seetings where to high....
What are you Over Clocked @?
Click to expand...
Click to collapse
I dont think the problem is overclocking coz it persisted even after flashing alternative sbf's and i believe that undoes whatever overclocking right??
Woodrube said:
I am not very versed at reading Logcats but does this have anything to do with it, (com.motorola.Camera_pref_loadsetting.xml.bak)?
Usually when we don't want the phone to recognize an app we rename it .bak instead of .apk? Just a though b/c there are .baks all over that Logcat.
Click to expand...
Click to collapse
Code:
( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_pref_flex.xml.bak': No such file or directory (errno=2)
D/ ( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_pref_loadsetting.xml.bak': No such file or directory (errno
=2)
Thanks problem is probably something to do with that bit, just browsed to /data/ found it empty, is it supposed to be empty??
lennyoks said:
Code:
( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_pref_flex.xml.bak': No such file or directory (errno=2)
D/ ( 1843): unable to unlink '/data/data/com.motorola.Camera/shared_prefs
/com.motorola.Camera_pref_loadsetting.xml.bak': No such file or directory (errno
=2)
Thanks problem is probably something to do with that bit, just browsed to /data/ found it empty, is it supposed to be empty??
Click to expand...
Click to collapse
Ok so I looked at mine and niether
com.motorola.Camera_pref_flex.xml.bak nor
data/data/com.motorola.Camera/shared_prefs/com.motorola.Camera_pref_loadsetting.xml.bak have .bak at the end. Open Root Explorer and hit the r/w button at the top to be able to make changes/rename and delete the.bak from the end of both.
My _pref_felx.xml shows a size of 235 and my pref_loadsetting.xl shows a size of 958
Once you take out the .bak, then reboot and it should work. If not the I would think that you could either go into /system/apps and uninstall the camera.apk file (make a back up first) or you can just take your original ROM system.img and restore that.
I really think that deleting the .bak in the above and rebooting will work though. It seems that it isn't able to link b/c the the .bak is screwing with the .apk settings. Like I said before, if we want the phone to ognore an app but don't neccessarily want to delete it, we just rename it .bak and then go from there. Seems that this may be the issue.
Woodrube said:
Ok so I looked at mine and niether
com.motorola.Camera_pref_flex.xml.bak nor
data/data/com.motorola.Camera/shared_prefs/com.motorola.Camera_pref_loadsetting.xml.bak have .bak at the end. Open Root Explorer and hit the r/w button at the top to be able to make changes/rename and delete the.bak from the end of both.
My _pref_felx.xml shows a size of 235 and my pref_loadsetting.xl shows a size of 958
Once you take out the .bak, then reboot and it should work. If not the I would think that you could either go into /system/apps and uninstall the camera.apk file (make a back up first) or you can just take your original ROM system.img and restore that.
I really think that deleting the .bak in the above and rebooting will work though. It seems that it isn't able to link b/c the the .bak is screwing with the .apk settings. Like I said before, if we want the phone to ognore an app but don't neccessarily want to delete it, we just rename it .bak and then go from there. Seems that this may be the issue.
Click to expand...
Click to collapse
I thought of doing that but my data folder is entirely empty there is no data/data, only an empty /data perhaps if i could copy a clean one from another phone!
lennyoks said:
I thought of doing that but my data folder is entirely empty there is no data/data, only an empty /data perhaps if i could copy a clean one from another phone!
Click to expand...
Click to collapse
I'm quite puzzled by that. Maybe you're looking in the wrong place? I don't see how it can be empty. Even when you do a factory reset (which erases both /data and /cache) by the time you've booted up /data is populated with all sorts of stuff. Just to be clear, we're talking about /data on the internal memory of the phone not the SD card (i.e. /data not /sdcard/data)?
Although, I must say I'm not optimistic these *.bak files are a problem at all--back in the day I used to have problems like this when using the SD card that Motorola shipped with the phone. I replaced it and those problems disappeared. I think Motorola shipped the cheapest (consequently buggiest) SD card they could find.
lennyoks said:
Thanks problem is probably something to do with that bit, just browsed to /data/ found it empty, is it supposed to be empty??
Click to expand...
Click to collapse
That usually happens if You browse to /data/data without enough permission (e.g. without root access and without the right browser).
Can You do :
Code:
adb shell
then inside this shell
Code:
su
if on the phone (unlock it) is displayed superuser popup, agree
then continue on the phone shell
Code:
busybox ls -la /data
Mioze7Ae said:
I'm quite puzzled by that. Maybe you're looking in the wrong place? I don't see how it can be empty. Even when you do a factory reset (which erases both /data and /cache) by the time you've booted up /data is populated with all sorts of stuff. Just to be clear, we're talking about /data on the internal memory of the phone not the SD card (i.e. /data not /sdcard/data)?
Although, I must say I'm not optimistic these *.bak files are a problem at all--back in the day I used to have problems like this when using the SD card that Motorola shipped with the phone. I replaced it and those problems disappeared. I think Motorola shipped the cheapest (consequently buggiest) SD card they could find.
Click to expand...
Click to collapse
That usually happens if You browse to /data/data without enough permission (e.g. without root access and without the right browser).
Click to expand...
Click to collapse
Sorry for the amateur error. You were right i was browsing the folders without root permissions thats why it looked empty,
however this time i did notice that I do not have the com.motorola.Camera folder in /data/data my folder list has com.motorola.android, com.motorola.motophone..., and com.motorola.usb , no camera. I think that should be the root of the problem.
sooo ... can i borrow a com.motorola.Camera folder from one of you guys??
Hi everyone,
it' my first messagg over here but i read you all the times, it's the most powerful forum i've ever heard, But now, I need you because I have a problem with my phone.
Well, some weeks ago I installed on my device Nexus S Europe (model version, I9023 i think) a custom rom called Nexus Beam, faboulus let's say, ICS, battery drain , never had problem...but a day all the processes started to crash, system.android.process, system.android.markert, etc ...let's say: all the processes, so i thought: "reboot" , it has always been so useful. Not this time...i rebooted the phone and again after 2-3 housrs of usage, the same crashes.
So i decided to put on it the latest MIUI rom (2.3.30)...everything was wonderful, everything was so speedy that "wowww" but again...2-3 hours of usage the same error messages...rebooted again, and..."Google" text for ever!!
SO agaia, deleted EVERYTHING from my sd card, i've done all the kind of formatting thing proposed by cwm (data, system, boot, cache), then tryed to flash an older version on MIUI with Gingerbread. Same stuff! after one hourse the same errors and now i really don't know what to do.
I've tried everytinhg but i'm always on the Google texct while the system is trying to reboot. Tried also with fastboot but it doesn't recognize the device.
Please, can you give me some suggestions?"! I'm really, resperate!!
Just for knowledge, attached here you can find the error i got for all the applications installed on my device. It's always the same, and change only the name of the app:
app_vercode:15
device_model:crespo
build_version:2.3.30
condition:1
processName:com.android.calendar
pid:3280
uid:10006
tag:null
shortMsg:android.database.sqlite.SQLiteException
longMsg:android.database.sqlite.SQLiteException: attempt to write a readonly database
stackTrace:java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:278)
at java.util.concurrent.FutureTask$Sync.innerSetExcep tion(FutureTask.java:273)
at java.util.concurrent.FutureTask.setException(Futur eTask.java:124)
at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:307)
at java.util.concurrent.FutureTask.run(FutureTask.jav a:137)
at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)
Caused by: android.database.sqlite.SQLiteException: attempt to write a readonly database
at android.database.DatabaseUtils.readExceptionFromPa rcel(DatabaseUtils.java:179)
at android.database.DatabaseUtils.readExceptionFromPa rcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(Content ProviderNative.java:358)
at android.content.ContentResolver.query(ContentResol ver.java:311)
at android.content.CursorLoader.loadInBackground(Curs orLoader.java:56)
at android.content.CursorLoader.loadInBackground(Curs orLoader.java:42)
at android.content.AsyncTaskLoader.onLoadInBackground (AsyncTaskLoader.java:255)
at android.content.AsyncTaskLoader$LoadTask.doInBackg round(AsyncTaskLoader.java:66)
at android.content.AsyncTaskLoader$LoadTask.doInBackg round(AsyncTaskLoader.java:55)
at android.os.AsyncTask$2.call(AsyncTask.java:264)
at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:305)
It would be really great if you could help me!
Thank you so much and happy easter to everyone!
So, in the end of the past year I have finally got to root my china replica (fake) Galaxy SIII
Everything was working just fine, until I remove some app from the /system/app directory, because this replica comes with almost no internal space, although I thought I was removing only unnecessary apps. I removed two that should not have been removed, the phone started to act erratically, it would fully start, but the screen just showed the wallpaper a blinked nonstop.
After my first moment of despair, I tried to solve it, throwing everything back on it, that stopped the blinking screen and showed the apps shortcuts on the main screen again. Then I started removing one app at time interspersed with a reboot. After removing what I didn't want left, except the only two necessary apps, I went to the Play Store, to download some apps and enjoy the new freed up internal space, only to discover that it simply didn't open anymore.
At first it would load, then show the upgrading screen (from market to play store) and when I tapped *continue" the app would just shutdown, and I was back at the app launcher, then I tried again just to even attempt open the app, the screen would change to the loading, but very quickly, it would shutdown again.
After my second moment of despair, I tried installing apps via ADB, and it worked, and so did the apps, every app that I installed worked just fine, but it wouldn't be updated unless I could find the .apk file and install it again via ABD. What, in some cases, is simply impossible.
Than I found a site, that would send the download link of the .apk file to my email, and I could download it in my phone, which was not an update but it was better than have to install anything via ADB. Then I tried to launch one of those apps, only to discover that my browser would crash with a F/C when I tapped save in the download pop-up.
After weeks searching for solutions and for any clue in this issue, I discovered that within the Dropbox's application directory contained a lot of .txt files.
Reading these files, I discovered what is causing the malfunction of the Play Store and the download function in the Browser, and it is the same thing. The problem is I don't know what to do to solve this.
Following below are some examples of the .txt files:
Location: /data/system/dropbox
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
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.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Subject: Finsky
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
android.util.Log$TerribleFailure: [27] DownloadProgressManager.makeNewCursor: Download progress cursor null: content://downloads/my_downloads
at android.util.Log.wtf(Log.java:275)
at android.util.Log.wtf(Log.java:254)
at com.google.android.finsky.utils.FinskyLog.wtf(FinskyLog.java:40)
at com.google.android.finsky.download.DownloadProgressManager.makeNewCursor(DownloadProgressManager.java:126)
at com.google.android.finsky.download.DownloadProgressManager.onDownloadProgress(DownloadProgressManager.java:234)
at com.google.android.finsky.download.DownloadProgressManager.access$000(DownloadProgressManager.java:28)
at com.google.android.finsky.download.DownloadProgressManager$2.run(DownloadProgressManager.java:97)
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.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.browser
Flags: 0x9be45
Package: com.android.browser v10 (2.3.5)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.android.browser.BrowserActivity.onDownloadStartNoStream(BrowserActivity.java:3737)
at com.android.browser.BrowserActivity$18.onClick(BrowserActivity.java:3603)
at android.view.View.performClick(View.java:2485)
at android.view.View$PerformClick.run(View.java:9080)
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:3690)
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:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Does anyone knows what it means? Or how to solve it? I really want this to work and despite it is taking up all of my free time, and I cannot come up with a solution.
Thanks in advance
Sorry for the bad English.
Hugo Bler
What were the two apps removed?
H_Bler said:
So, in the and of the past year i've get to root my china replica (fake) Galaxy SIII
Everything was working just fine, until I remove some app from the /system/app directory, 'cause this replicas come with almost none internal space, althogh I thought I was removing only unecessary apps, I removed two that wasn't sopposed to be removed, the phone bricked, it would fully start, but the screen just showed the wallpaper a blinked nonstop.
After my depair, I tried to solve it, throwing everything back on it, what stopped the blinking screen and showed the apps shortcuts in the main screen again. Then I started removing one app at time interspersed with a reboot, after removing what I didn't want lefting only that two necessary apps, I went to the Play Store, to download some apps and enjoy the new freed internal space, only to discover that it simply didn't open anymore, at first it would load, then show the upgrading screen (from market to play store) and when I touched "continue" the app would shutdown, and I was back at the app luncher, then I tried again just to it don't even open, the screen would change to the loading, but in notime it would shutdown again.
After my second despair, I tried installing apps via ADB, and it worked, and so did the apps, everyone that I installed worked just fine, but it wouldn't be updated unless I could find the .apk file and install it again via ABD. What, in some cases, is simply impossible.
Than I found a site, that would send the download link of the .apk file to my email, and I could download it in my phone, wich wasn't an autoupdate but it was better than have to install anything via ADB. Then I tried it, only to discover tha my browser would crash an FC when I thouched save in the download pop-up.
After weeks seeking solutions and searching any clue in the phone root directories, if found the Dropbox directory that contain a lot of .txt files.
Reading this files I discoverd what is causing de malfunction of the Play Store and the download function in the Browser, and it is the same thing. The problem is I don't know what to do to solve this, following below are some exemples of the .txt files:
location: /data/system/dropbox
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
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.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Subject: Finsky
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
android.util.Log$TerribleFailure: [27] DownloadProgressManager.makeNewCursor: Download progress cursor null: content://downloads/my_downloads
at android.util.Log.wtf(Log.java:275)
at android.util.Log.wtf(Log.java:254)
at com.google.android.finsky.utils.FinskyLog.wtf(FinskyLog.java:40)
at com.google.android.finsky.download.DownloadProgressManager.makeNewCursor(DownloadProgressManager.java:126)
at com.google.android.finsky.download.DownloadProgressManager.onDownloadProgress(DownloadProgressManager.java:234)
at com.google.android.finsky.download.DownloadProgressManager.access$000(DownloadProgressManager.java:28)
at com.google.android.finsky.download.DownloadProgressManager$2.run(DownloadProgressManager.java:97)
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.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.browser
Flags: 0x9be45
Package: com.android.browser v10 (2.3.5)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.android.browser.BrowserActivity.onDownloadStartNoStream(BrowserActivity.java:3737)
at com.android.browser.BrowserActivity$18.onClick(BrowserActivity.java:3603)
at android.view.View.performClick(View.java:2485)
at android.view.View$PerformClick.run(View.java:9080)
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:3690)
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:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Does anyone knows what it means? Or How to sove it? I really want to this, it's taking all my free time, and I can't come up with a solution.
Thanks in advance
sorry for the bad english.
Hugo Bler
Click to expand...
Click to collapse
Hello Hugo, total noob here. Thanks for informing us of your issue. I'm almost near the rooting process, I'm pretty sure we have the same unit. Just out of curiousity, what were the two apps you removed that caused your phone to malfunction?
I'm still stuck with rooting the device because everytime I use the DOOMTOOL I get up to the point where it says, "read only memory"... As previously discussed in the other thread: http://forum.xda-developers.com/showthread.php?t=2061069&page=4
Thanks for all your inputs... I'm so confused with these China clones
It seems to me you should just do a factory reset if that is an option.
Yeah...
rpjwalter said:
It seems to me you should just do a factory reset if that is an option.
Click to expand...
Click to collapse
I've tried that, three times actually, after I pushed back those two apps in the /system/app directory, I did a factory reset, but it didn't work :/
SOLVED.
H_Bler said:
So, in the end of the past year I have finally got to root my china replica (fake) Galaxy SIII
Everything was working just fine, until I remove some app from the /system/app directory, because this replica comes with almost no internal space, although I thought I was removing only unnecessary apps. I removed two that should not have been removed, the phone started to act erratically, it would fully start, but the screen just showed the wallpaper a blinked nonstop.
After my first moment of despair, I tried to solve it, throwing everything back on it, that stopped the blinking screen and showed the apps shortcuts on the main screen again. Then I started removing one app at time interspersed with a reboot. After removing what I didn't want left, except the only two necessary apps, I went to the Play Store, to download some apps and enjoy the new freed up internal space, only to discover that it simply didn't open anymore.
At first it would load, then show the upgrading screen (from market to play store) and when I tapped *continue" the app would just shutdown, and I was back at the app launcher, then I tried again just to even attempt open the app, the screen would change to the loading, but very quickly, it would shutdown again.
After my second moment of despair, I tried installing apps via ADB, and it worked, and so did the apps, every app that I installed worked just fine, but it wouldn't be updated unless I could find the .apk file and install it again via ABD. What, in some cases, is simply impossible.
Than I found a site, that would send the download link of the .apk file to my email, and I could download it in my phone, which was not an update but it was better than have to install anything via ADB. Then I tried to launch one of those apps, only to discover that my browser would crash with a F/C when I tapped save in the download pop-up.
After weeks searching for solutions and for any clue in this issue, I discovered that within the Dropbox's application directory contained a lot of .txt files.
Reading these files, I discovered what is causing the malfunction of the Play Store and the download function in the Browser, and it is the same thing. The problem is I don't know what to do to solve this.
Following below are some examples of the .txt files:
Location: /data/system/dropbox
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
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.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.vending
Flags: 0xabe45
Package: com.android.vending v8016010 (3.10.10)
Subject: Finsky
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
android.util.Log$TerribleFailure: [27] DownloadProgressManager.makeNewCursor: Download progress cursor null: content://downloads/my_downloads
at android.util.Log.wtf(Log.java:275)
at android.util.Log.wtf(Log.java:254)
at com.google.android.finsky.utils.FinskyLog.wtf(FinskyLog.java:40)
at com.google.android.finsky.download.DownloadProgressManager.makeNewCursor(DownloadProgressManager.java:126)
at com.google.android.finsky.download.DownloadProgressManager.onDownloadProgress(DownloadProgressManager.java:234)
at com.google.android.finsky.download.DownloadProgressManager.access$000(DownloadProgressManager.java:28)
at com.google.android.finsky.download.DownloadProgressManager$2.run(DownloadProgressManager.java:97)
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.os.HandlerThread.run(HandlerThread.java:60)
File name: [email protected]
Code:
Process: com.android.browser
Flags: 0x9be45
Package: com.android.browser v10 (2.3.5)
Build: sprd/sprdroid_base/hsdroid:2.3.5/MocorDroid2.3.5/W12.20_P12_20121105.115851:user/test-keys
java.lang.IllegalArgumentException: Unknown URL content://downloads/my_downloads
at android.content.ContentResolver.insert(ContentResolver.java:600)
at com.android.browser.BrowserActivity.onDownloadStartNoStream(BrowserActivity.java:3737)
at com.android.browser.BrowserActivity$18.onClick(BrowserActivity.java:3603)
at android.view.View.performClick(View.java:2485)
at android.view.View$PerformClick.run(View.java:9080)
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:3690)
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:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Does anyone knows what it means? Or how to solve it? I really want this to work and despite it is taking up all of my free time, and I cannot come up with a solution.
Thanks in advance
Sorry for the bad English.
Hugo Bler
Click to expand...
Click to collapse
SOLVED.
The issue was caused by lack of a system application, the application "donwloadprovider.apk".
The problem was identified by comparing the "/system/app" directory in two similar devices, and noticing that the application was missing.
The solution:
Copy the application from the working device(A) to a computer.
Push via ADB the application to the malfunctioning device (B) "/system/app" directory.
Reboot device B.
Thanks Everyone for the help.
Especial thanks to Chico_PinoyCracker, Since he's the owner of "Device A".
Thanks Man.
As the title say, someone got into my phone.
Now, i am not a geek but I have learned some stuff throughout the years since I've been using Android. Recently I have recognized some new system apps on my phone which they were not installed by me. I did'nt panic, quickly removed my sd card erased all content and set it up as new phone. I did'nt signed into google play store or downloaded any apps, and I have kept my sd card out of the phone. So I just used the phone for text message, and calls. Just for fun (since I knew that I will erase all the content, I choosed to be a developer and started remove permissions from a lot of apps and soon enough I found something interesting in my download folder which was a pdf file, which you will see in a moment.
English is not my first language but I understood that it has someones report maybe generated I dont know. But I have a few questions.
What is this about?
Who might have been created this?
Who is that for? (Some kind of a report?)
Thanks a lot!
(This is an extract from a pdf file)
`2020年01月02日 04:05:16 Product Model: BV5500Pro,android: 9 versionCode = Unable to start activity ComponentInfo{com.mediatek.camera/com.mediatek.camera.CameraActivity}: java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked StackTrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mediatek.camera/com.mediatek.camera.CameraActivity}: java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2947) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3101) at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78) at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java: 108) at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1839) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:193) at android.app.ActivityThread.main(ActivityThread.java:6724) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911) Caused by: java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked at android.app.ContextImpl.getSharedPreferences(ContextImpl.java:420) at android.app.ContextImpl.getSharedPreferences(ContextImpl.java:405) at android.content.ContextWrapper.getSharedPreferences(ContextWrapper.java:174) at android.preference.PreferenceManager.getDefaultSharedPreferences(PreferenceManager.java:526) at com.mediatek.camera.common.relation.DataStore$SharedPreferencesWrapper.getPreferencesFromSco pe(DataStore.java:287) at com.mediatek.camera.common.relation.DataStore$SharedPreferencesWrapper. (DataStore.java:240) at com.mediatek.camera.common.relation.DataStore.getSharedPreferencesWrapperSync(DataStore.java :200) at com.mediatek.camera.common.relation.DataStore.getValue(DataStore.java:171) at com.mediatek.camera.common.mode.CameraModeBase.getDeviceUsage(CameraModeBase.java:274) at com.mediatek.camera.common.mode.ModeManager.createDeviceUsage(ModeManager.java:307) at com.mediatek.camera.common.mode.ModeManager.create(ModeManager.java:137) at com.mediatek.camera.CameraActivity.onCreateTasks(CameraActivity.java:198) at com.mediatek.camera.PermissionActivity.onPermissionCreateTasks(PermissionActivity.java:103) at com.mediatek.camera.QuickActivity.onCreate(QuickActivity.java:129) at android.app.Activity.performCreate(Activity.java:7136) at android.app.Activity.performCreate(Activity.java:7127) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2927) ... 11 more
Hi
I'm not a pro too, but looks like a log file from an app written in Java for me... Not neccessarily a threat, it uses the camera and some standard system stuff, afaik. Can't tell you more either, sorry.