Related
Code:
D/AndroidRuntime( 1537): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1537): CheckJNI is OFF
D/dalvikvm( 1537): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1537): Stale deps in cache file; removing and retrying
W/dalvikvm( 1537): Size mismatch on inflated file (927937 vs 924012)
E/dalvikvm( 1537): Unable to extract+optimize DEX from '/system/framework/services.jar'
D/dalvikvm( 1537): Failed on '/system/framework/services.jar' (boot=1)
D/dalvikvm( 1537): VM cleaning up
D/dalvikvm( 1537): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1537): JNI_CreateJavaVM failed
E/AndroidRuntime( 1537): JNI_CreateJavaVM failed
As some of you know, I have been having this looping in my logcat after I flash a ROM properly. I tried to push services.jar and even services.odex from some ROMs, but none worked.
To make things work, I tried flashing the only recent ROM that worked for me (Blur 1.5.7), booted once, wiped data (not ext3) then flashed any other ROM (like Maxisma's 1.7). It worked, but some things kept force closing (clock, wallpapers, sometimes even launcher).
So...rather than focusing on a hardware/NAND problem I can't fix, could I request all you devs to modify your ROM with a different services.jar or framework files? Or could you teach me the basics so I can experiment for myself how I can modify your ROMs?
Any help on this is greatly appreciated.
I am not a dev. But i did stay at a holiday inn last night.
Not sure if this is exactly what you want but you can push the framework-res.apk from drizzys 1.5.7 to most of the new heros. Push it to /system/framework.
Im using Maxismas 1.6 framework-res on drizzys 1.5.5
I hope this helps. If not, or i am way off of what you want, i appologize.
alpha22 said:
So...rather than focusing on a hardware/NAND problem I can't fix............
Click to expand...
Click to collapse
Myabe you should. Are you 100% that your sd card isn't toast? It sounds like it could be causing the file mismatch problems you are having.
I had a brand new class 6 sd card that was causing all kinds of trouble for me just like this.
So...it's not the fault of the phone's hardware, but rather the SD?
And I've managed to flash mdhero 1.7, mlign as well as kingklick's ROMs by pushing Blur 1.5.7's framework-res.apk and services.jar after flashing. I pushed the originals back after they've booted, though.
Some things like clock/launcher still force-close on me, so I'm not fully satisfied with my solution. Mlign's is terribly slow, too.
Ok alpha22 now that you figured out your problem please move this to Q&A ....you're choking up the dev section with this ,,,,so pretty pretty please , repost in Q&A !!!
dan0zone said:
Ok alpha22 now that you figured out your problem please move this to Q&A ....you're choking up the dev section with this ,,,,so pretty pretty please , repost in Q&A !!!
Click to expand...
Click to collapse
Nah the problem is far from solved. Everything resets after a reboot, as i just found out. And this is a legit request going out to developers to either teach me how framework works, or modify their ROMs to help me. I could PM them if you think I'm clogging up this board.
Ok then put this in the q&a section!!!
your_helpfull_hand said:
Ok then put this in the q&a section!!!
Click to expand...
Click to collapse
I don't know how to move this. Only a mod can. And if I post this in Q&A, the devs will never get to read it.
Whatever, I'm done here. Thank you all for trying to help, especially Drizzy and Cyanogen. They're like the only devs who truly bother.
I shall convert to Apple soon enough.
Mikey, you can close this. Thanks.
alpha22 said:
I don't know how to move this. Only a mod can. And if I post this in Q&A, the devs will never get to read it.
Whatever, I'm done here. Thank you all for trying to help, especially Drizzy and Cyanogen. They're like the only devs who truly bother.
I shall convert to Apple soon enough.
Mikey, you can close this. Thanks.
Click to expand...
Click to collapse
done here? we are trying to help you, but all people are trying to say is next time please post in the correct subforum.
now, what exactly are you trying to do. framework-res.apk? are you trying to change/add animations from blur or what?
also, between ROMs you should wipe ext or at least /system/sd/app* and /system/sd/dalv*. maybe this is causing the mismatch/FC between switching ROM's
and one last thing, asking devs to modify all their ROMs per one users request seems farfetched. while some devs will probably be more than happy to help you on a single basis, its quite hard to ask all devs to do this. shoot me a PM or hit me on gtalk- [email protected] and i will see if i can get you up and running again, in the meantime Mikey can you move this thread over to Q&A.
lets get you back up and running again alpha.
palosjr said:
now, what exactly are you trying to do. framework-res.apk? are you trying to change/add animations from blur or what?
Click to expand...
Click to collapse
Which files are related to the blur animations, if I may ask?
AGx-07_162 said:
Which files are related to the blur animations, if I may ask?
Click to expand...
Click to collapse
in the blur rom, go to frameworks pull those files and push them into your current rom its something like 45 files... just do a search for "blur animations"
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??
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.
Is it a framework problem? I can't send mms but i can receive mms.
kanch86 said:
Is it a framework problem? I can't send mms but i can receive mms.
Click to expand...
Click to collapse
We need additional information to help you. What phone do you have, is it rooted, if yes which ROM do you use?
You can use Skype, Facebook, Google+ or WhatsApp instead.
H3llwar said:
We need additional information to help you. What phone do you have, is it rooted, if yes which ROM do you use?
You can use Skype, Facebook, Google+ or WhatsApp instead.
Click to expand...
Click to collapse
Hi,
Yes my phone is rooted. My phone is sony LWW and im using CM 10.1 coconut rom.
I checked the logcat and it says
"V/TransactionSettings( 1887): APN setting: MMSC:192.168.050.165 looked for: current IS NOT NULL AND apn=?
D/CMStats ( 1795): Waiting for next sync : 21 hours
W/ActivityManager( 523): Unable to start service Intent { act=com.jb.gochat.im.service.GOIMService } U=0: not found
W/DrmManagerClient( 1887): You should have called release()
D/dalvikvm( 1887): GC_CONCURRENT freed 1417K, 47% free 6579K/12184K, paused 3ms+4ms, total 101ms
D/dalvikvm( 1887): WAIT_FOR_CONCURRENT_GC blocked 83ms
E/Mms:transaction( 1887): Url: <url>
E/Mms:transaction( 1887): Host name may not be null
E/SendTransaction( 1887): java.io.IOException: Host name may not be null
E/SendTransaction( 1887): at com.android.mms.transaction.HttpUtils.handleHttpConnectionException(HttpUtils.java:296)
E/SendTransaction( 1887): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:278)
E/SendTransaction( 1887): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:175)
.........
E/SendTransaction( 1887): ... 4 more
E/SendTransaction( 1887): Delivery failed.
"
But I can receive MMS messages. So i dont thinks it's a problem of APN.
Any idea?
TL;DR : working photo pro for systems without Sony telemetry services: AFH
Hey guys I've been running a GSI of Descendant OS on my Xperia 5 II and I have been trying to get this photo pro app to work. All the versions I found on apkmirror crashes on launch, not to mention the ones that refuse to install. So after tinkering with some magisk modules I decided to decompile it and see what's going on inside. After a bit of log checking, I discovered some unimplemented telemetry functions which seems to be the cause of those crashes. After patching these the app runs like how it should be. I also removed the restrictions in AndroidManifests.xml that prevents the app to be installed on devices without com.sony.device lib, so any system should be able to install it just fine (not sure why Sony set restrictions for photo pro but not cinema pro).
Let me know if there's more issues to be solved
I've been running the APK from Photopro III for months and have had no significant issues. I got my APK from, I think, ADK.
2nd post down its from the Xperia 1 iii
@hx64 any chance for a patch for the latest version, or a guide as to how to patch it?
That would be awesome!
SeventhRaven said:
@hx64 any chance for a patch for the latest version, or a guide as to how to patch it?
That would be awesome!
Click to expand...
Click to collapse
I'm a bit busy these days so maybe I'll work on that a few weeks later.
Meanwhile, what I did is fairly simple and anyone can do it themselves. Once the app crashes, grab the crash log with `adb logcat --buffer=crash` and find the entry with the package name. There will be an attribute that points to a specific line of code which caused the crash, usually an explicit error `throw` action. You'll then need to decompile the .apk file and modify the corresponding file. I use an extension called apklab in VScode but you can do it with apktool too. You should be able to edit the source code (.smali or .java, depending on the tools you used) and locate the lines that throw errors (based on my experience it is usually the unimplemented methods in com.sonyerricsson.idd.api.Idd component that caused the errors so I just removed those `throw` statements in .java files or replace them with `return-void` statements in .smali files). The last step is to recompile and sign the package (using the same tool you used to decompile). You may need to test and repeat these steps a few more times to resolve all the error throws but the process is fairly straight forward and you can find a lot of tutorials online.
Good luck fiddling!
hx64 said:
I'm a bit busy these days so maybe I'll work on that a few weeks later.
Meanwhile, what I did is fairly simple and anyone can do it themselves. Once the app crashes, grab the crash log with `adb logcat --buffer=crash` and find the entry with the package name. There will be an attribute that points to a specific line of code which caused the crash, usually an explicit error `throw` action. You'll then need to decompile the .apk file and modify the corresponding file. I use an extension called apklab in VScode but you can do it with apktool too. You should be able to edit the source code (.smali or .java, depending on the tools you used) and locate the lines that throw errors (based on my experience it is usually the unimplemented methods in com.sonyerricsson.idd.api.Idd component that caused the errors so I just removed those `throw` statements in .java files or replace them with `return-void` statements in .smali files). The last step is to recompile and sign the package (using the same tool you used to decompile). You may need to test and repeat these steps a few more times to resolve all the error throws but the process is fairly straight forward and you can find a lot of tutorials online.
Good luck fiddling!
Click to expand...
Click to collapse
I tried working on that by simply removing the requirements (although I actually have zero development experience), but I would always get a parsing error (probably an issue with the signing? No idea how to do that properly) when trying to install it.
As for the unmodified version, I cannot install it at all, as it says it's not compatible. So a crash technically never occurs.
But I don't mind waiting for a patch. Just glad to see it's an option still.
SeventhRaven said:
I tried working on that by simply removing the requirements (although I actually have zero development experience), but I would always get a parsing error (probably an issue with the signing? No idea how to do that properly) when trying to install it.
As for the unmodified version, I cannot install it at all, as it says it's not compatible (using a custom ROM). So a crash technically never occurs.
But I don't mind waiting for a patch. Just glad to see it's an option still.
Click to expand...
Click to collapse
Oh I forgot to mention the install issues. There's a `use-library` line in the AndroidManifest.xml that requires the `com.sony.device` library which you'll need to remove in order to install it on non-official systems.
And be sure to use deCOMPILE tools first (it won't work if you deCOMPRESS and edit since a signature is required), google for apktool or check out the apklab github page. I have little java knowledge previously but in this case fortunately you don't need much
I'll try switching to my dev environment as soon as possible.
hx64 said:
Oh I forgot to mention the install issues. There's a `use-library` line in the AndroidManifest.xml that requires the `com.sony.device` library which you'll need to remove in order to install it on non-official systems.
And be sure to use deCOMPILE tools first (it won't work if you deCOMPRESS and edit since a signature is required), google for apktool or check out the apklab github page. I have little java knowledge previously but in this case fortunately you don't need much
I'll try switching to my dev environment as soon as possible.
Click to expand...
Click to collapse
Yeah I tried apktool and I guess I recompiled it with Android Studio. All I changed was setting the requirement for com.sony.device lib to false.
I'll try my luck with the tool you've linked, thanks!
hx64 said:
I'm a bit busy these days so maybe I'll work on that a few weeks later.
Meanwhile, what I did is fairly simple and anyone can do it themselves. Once the app crashes, grab the crash log with `adb logcat --buffer=crash` and find the entry with the package name. There will be an attribute that points to a specific line of code which caused the crash, usually an explicit error `throw` action. You'll then need to decompile the .apk file and modify the corresponding file. I use an extension called apklab in VScode but you can do it with apktool too. You should be able to edit the source code (.smali or .java, depending on the tools you used) and locate the lines that throw errors (based on my experience it is usually the unimplemented methods in com.sonyerricsson.idd.api.Idd component that caused the errors so I just removed those `throw` statements in .java files or replace them with `return-void` statements in .smali files). The last step is to recompile and sign the package (using the same tool you used to decompile). You may need to test and repeat these steps a few more times to resolve all the error throws but the process is fairly straight forward and you can find a lot of tutorials online.
Good luck fiddling!
Click to expand...
Click to collapse
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
(I didn't touch anything else, though...so idk about analytics, but I firewall apps anyway so not like it can send anything)
SeventhRaven said:
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
Click to expand...
Click to collapse
Nice work!
Glad I could help xD
SeventhRaven said:
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
Click to expand...
Click to collapse
Any chance someone could do this for the Video Pro app (1.0.a.0.26)?
I took a shot at trying to mod the apk..
I successfully installed with the Manifest.xml library edit, but upon crashing here's my log:
Code:
04-27 16:54:12.702 8085 8148 E AndroidRuntime: FATAL EXCEPTION: IddManagerThread
04-27 16:54:12.702 8085 8148 E AndroidRuntime: Process: jp.co.sony.mc.videopro, PID: 8085
04-27 16:54:12.702 8085 8148 E AndroidRuntime: java.lang.RuntimeException: Not an implementation
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at com.sonyericsson.idd.api.Idd.addEvent(Idd.java:114)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager.addAppData(IddManager.kt:99)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager.handleMessage(IddManager.kt:88)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager.access$handleMessage(IddManager.kt:17)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at jp.co.sony.mc.videopro.idd.core.IddManager$Companion$init$1$1.handleMessage(IddManager.kt:50)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
04-27 16:54:12.702 8085 8148 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
And this is where I get lost. Swapping the throw code in com.sonyerricsson.idd.api.Idd doesn't seem to solve the crashes, and I'm not sure where to go next. I don't see any HandlerThread or loop smali files, and in jp.co.sony.mc.videopro.idd.core.IddManager, I'm not familiar with the code in the lines where the errors are defined.
SeventhRaven said:
Welp, that was easy. Used VScode with the extension, swapped the lib flag to false and removed the component you mentioned. Now it works (although that bokeh setting still crashes it if selected, but whatever).
I've attached the patched .apk for your convenience. Big thanks again for pointing me towards those tools!
(I didn't touch anything else, though...so idk about analytics, but I firewall apps anyway so not like it can send anything)
Click to expand...
Click to collapse
Just installed your patched version on the latest Pixel Experience GSI (v414/June security patch) on a Xperia 1 III and it worked perfectly including bokeh.
Any chance you'll be sharing patched versions of more recent releases of the app?
Thanks!
Patched version of the latest (1.4.A.0.20-2621460) attached.
Thanks for your work around this @hx64.
@delfuhd I also could not untangle the logcat so I ended up replacing all instances of 'throw p0' in com.sonyericsson.idd.api.Idd with 'return-void' and there doesn't seem to be an issue (yet).
Is the app asking for some Sony exclusive features? I mean, do we lose something like postprocessing or image management? thanks!
Not working
Double post.
The 70mm lens causes the app to crash in Auto mode in every 1.4 and 1.5 version I tested. The only one that seems to work is the older 1.3 version.
Still here is the latest patched 1.5 version that I tried. Thanks for the guide above!
cari66eam said:
The 70mm lens causes the app to crash in Auto mode in every 1.4 and 1.5 version I tested. The only one that seems to work is the older 1.3 version.
Still here is the latest patched 1.5 version that I tried. Thanks for the guide above!
Click to expand...
Click to collapse
Thank you so much for providing the patched version!!! I'm on lineageos 20, no gapps etc. and the 1.2 works great. Haven't tried 1.3, but 1.4 and 1.5 don't work for me...