Related
Looking to import the Donut power widget into Amon_RA's 1.1 ROM - can someone tell me where it is? I couldn't find any .apk related to it in the /data folder of a ROM which does use it. Is it part of the launcher or something strange like that?
Thanks in advance.
If I remember correctly, it's in the hofo ion rom that hotweiss has posted.
jfive74 said:
If I remember correctly, it's in the hofo ion rom that hotweiss has posted.
Click to expand...
Click to collapse
Thanks, but looking for which specific file or files are responsible so I can add it to a different ROM.
Think it says power.apk and there is a patch for it aswell. Check dream forum, punch in power.apk, you must find it. I did.
jfive74 said:
Think it says power.apk and there is a patch for it aswell. Check dream forum, punch in power.apk, you must find it. I did.
Click to expand...
Click to collapse
sorry I cant find it must be blind but did as you suggested and came up blank
Nope, I can't find this either.
Hello,
I don't know if this can help you, but there is my logcat when I click on "Power Control" on the panel to add Widget on desktop. With the Dionanos' rom.
Perhaps it's in the "com.android.settings" ?
I don't known why the voicedialer appears here, i do it several times, and i have this log at every time.
D/HomeLoaders( 522): application intent received: android.intent.action.PACKAGE
_CHANGED, replacing=false
D/HomeLoaders( 522): --> package:com.android.settings
D/HomeLoaders( 522): --> sync package com.android.settings
D/VoiceDialerReceiver( 625): onReceive Intent { action=android.intent.action.PA
CKAGE_CHANGED data=package:com.android.settings comp={com.android.voicedialer/co
m.android.voicedialer.VoiceDialerReceiver} (has extras) }
D/RecognizerEngine( 625): deleteCachedGrammarFiles /data/data/com.android.voice
dialer/files/openentries.txt
D/Launcher( 522): dumping extras content=Bundle[{appWidgetId=6}]
W/InputManagerService( 56): Window already focused, ignoring focus gain of: co
[email protected]
And then, when i delete the Power control widget :
D/VoiceDialerReceiver( 625): onReceive Intent { action=android.intent.action.PA
CKAGE_CHANGED data=package:com.android.settings comp={com.android.voicedialer/co
m.android.voicedialer.VoiceDialerReceiver} (has extras) }
D/RecognizerEngine( 625): deleteCachedGrammarFiles /data/data/com.android.voice
dialer/files/openentries.txt
D/HomeLoaders( 522): application intent received: android.intent.action.PACKAGE
_CHANGED, replacing=false
D/HomeLoaders( 522): --> package:com.android.settings
D/HomeLoaders( 522): --> sync package com.android.settings
Scargoll.
@scargoll,
I think you are right. Not sure if you can just push/install these onto your phone and expect them to work unfortunately. ;/
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??
Trying to open any links sent to me via Google Talk crashes the app with the generic "Unfortunately, Google Talk has stopped."
I just flashed Android Revolution HD last night.
Did you do "Superwipe" before flashing this ROM?
I did, it said there were no problems.
So, as an update, I SuperWiped twice and re-flashed. Gtalk still crashed when clicking a link.
I decided I'd use BeejiveGT as a "for now" solution. Clicking a link in there, however, still crashed the program. BUT! Beejive was nice enough to leave a crash report. Hopefully someone smart can tell me what's going wrong and how to fix it
Report collected on Wed Jun 20 07:51:32 EDT 2012
System Info :
==============
deviceID= 355066040364582_c799cf5d0e73e026_GTALK
versionName= 3.5.7
deviceModel= HTC Sensation 4G
osBuildBrand= tmous
deviceOS= 4.0.3
deviceDisplay= IML74K
deviceHost= ABM011
deviceBuildID= IML74K
deviceBuildModel= HTC Sensation 4G
deviceBuildUser= root
deviceManuacturer= HTC
apphash= PKF6dH2ES10HzdnU940CXA==
Total Internal memory : 1233059840
Available Internal memory : 240840704
Stack :
=======
android.content.ActivityNotFoundException: Unable to find explicit activity class {com.htc.HtcLinkifyDispatcher/com.htc.HtcLinkifyDispatcher.HtcLinkifyDispatcherActivity}; have you declared this activity in your AndroidManifest.xml?
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1634)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1510)
at android.app.Activity.startActivityForResult(Activity.java:3244)
at com.beejive.im.controller.AbstractBeejiveActivity.startActivityForResult(AbstractBeejiveActivity.java:151)
at android.app.Activity.startActivity(Activity.java:3351)
at com.beejive.im.controller.AbstractBeejiveActivity.startActivity(AbstractBeejiveActivity.java:145)
at android.text.style.LinkifyURLSpan.onClick(LinkifyURLSpan.java:73)
at android.text.method.LinkMovementMethod.onTouchEvent(LinkMovementMethod.java:212)
at android.widget.TextView.onTouchEvent(TextView.java:8776)
at android.view.View.dispatchTouchEvent(View.java:5579)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:1965)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1734)
at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1983)
at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1442)
at android.app.Activity.dispatchTouchEvent(Activity.java:2414)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1931)
at android.view.View.dispatchPointerEvent(View.java:5759)
at android.view.ViewRootImpl.deliverPointerEvent(ViewRootImpl.java:2963)
at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2522)
at android.view.ViewRootImpl.processInputEvents(ViewRootImpl.java:862)
at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2531)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:4944)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
at dalvik.system.NativeStart.main(Native Method)
Cause :
=======
**** End of current Report ***
Click to expand...
Click to collapse
Same problem
Also experiencing the same problem on the desire S after installing the ICS RUU update. Anyone know of a solution?
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.
Hey there, I'm trying to port MIUI 6 from MI4 to our OnePlusOne. Of course it bootloops and maybe someone here may got some idea.
What I did :
On base ROM ( CM11 M11 ), deleted
/system/app
/systel/priv-app
/system/media
/system/font
/system/framework
I replaced by the ported ROM ( Mi4/MI3W MIUI 6 5.1.23 )
I added missing libs from port to base without replace
I replaced libdvm.so and libjavacore.so by the one from ported rom
I replaced framework.jar with the one from CM 11 ( base ) ROM.
(I didnt get to fix errors from framework until replace it entirely)
I edited bootclasspath to the one from MIUI 6 kernel
I replaced updater-script permissions set
Here's the log : http://cjoint.com/?EBsm3ZvDkv7
Main error for me :
F/libc ( 3863): Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 3863 (zygote)
Here's the ROM : https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing
Base link : http://download.cyanogenmod.org/get/jenkins/86415/cm-11-20141008-SNAPSHOT-M11-bacon.zip
Port link : https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing ( Uploading )
Thanks for any help or suggestion.
If you do upload, I would be grateful
Thanks
The libnetcmdiface errors are bogus material. You can, more often than not, ignore those.
MrColdbird said:
The libnetcmdiface errors are bogus material. You can, more often than not, ignore those.
Click to expand...
Click to collapse
Yes. I saw this. Thanks for reply anyway
luigirenna said:
If you do upload, I would be grateful
Thanks
Click to expand...
Click to collapse
I will upload it
Tapatalké depuis mon OnePlus One MIUI !
@Kingzak34
off topic Q
Which version of AK you are using with MIUI 5 on OPO?
sajid533 said:
@Kingzak34
off topic Q
Which version of AK you are using with MIUI 5 on OPO?
Click to expand...
Click to collapse
77 CM11
Miui V6
try to see here
http://en.miui.com/thread-84084-1-1.html
luigirenna said:
try to see here
http://en.miui.com/thread-84084-1-1.html
Click to expand...
Click to collapse
I saw this, but it's broken, and doesnt even work with multirom.
I want to try to port myself for now.
I didnt not upload my work yet, cause I started over from scratch, and I didnt fix enough for now.
I am also experimenting with Mi4W rom to make a port. trying in multi rom. stuck in boot step
sajid533 said:
I am also experimenting with Mi4W rom to make a port. trying in multi rom. stuck in boot step
Click to expand...
Click to collapse
Boot animation or before ? Got logcat ?
V6
I tried the version, actually the Wi-Fi and the camera did not work.
I guess with a logcat active (I hope) to see why it does not work.
There are problems with shutting down.
but it's a good start.:good:
Here is my last-kmsg file when I booted with miui 6 with official miui5 rom boot.img
No bootloop. No boot animation
Just stuck at one+ logo
https://mega.co.nz/#!Ghp01JwB!sK6FhYyf6xYZ2c_OgdI66fvoCrv6rAooCek71Ty3jmI
Sent from my One+ using XDA Free mobile app
My ROM is uploading.
Kingzak34 said:
My ROM is uploading.
Click to expand...
Click to collapse
Problem solved? how?
No its not solved. It's still on the same state.
Dalvik VM starts working then fatal signal from libc
Tapatalké depuis mon OnePlus One MIUI !
Here will be the ROM when uploaded :
https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing
WARNING : Remember that ROM doesnt boot and it's only for work.
I updated logcat on 1st post. Here we are for now.
Kingzak34 said:
I saw this, but it's broken, and doesnt even work with multirom.
I want to try to port myself for now.
I didnt not upload my work yet, cause I started over from scratch, and I didnt fix enough for now.
Click to expand...
Click to collapse
You can try to fix wifi ,sound and camera and Make it multirom ready ???
Its easier because its booting and yours not ??
jamal2367 said:
You can try to fix wifi ,sound and camera and Make it multirom ready ???
Its easier because its booting and yours not ??
Click to expand...
Click to collapse
stop talking.
Kingzak34 said:
Here will be the ROM when uploaded :
https://drive.google.com/folderview?id=0Bx5Izzyb5WF-a0FpU21peVJSWGc&usp=sharing
WARNING : Remember that ROM doesnt boot and it's only for work.
I updated logcat on 1st post. Here we are for now.
Click to expand...
Click to collapse
this mostly refers to missing resources, but i'm not quite sure atm :/
Code:
F/libc ( 3894): Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 3894 (zygote)
maybe to:
Code:
D/idmap ( 3992): error: no read access to /vendor/overlay: No such file or directory
and:
Code:
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-2.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-2.apk'
try move this stuff to data and reboot, want to see the log if the files are present
OldDroid said:
this mostly refers to missing resources, but i'm not quite sure atm :/
Code:
F/libc ( 3894): Fatal signal 11 (SIGSEGV) at 0x00000014 (code=1), thread 3894 (zygote)
Click to expand...
Click to collapse
For this one, I must give some search on internet, I saw many people having this but didnt find solution for now.
OldDroid said:
Code:
D/idmap ( 3992): error: no read access to /vendor/overlay: No such file or directory
Click to expand...
Click to collapse
There is no overlay folder or file in vendor folder of both ROM. I think it can be ignored. ( But I may be wrong )
OldDroid said:
Code:
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.sdk-2.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-1.apk'
D/dalvikvm( 3894): Unable to stat classpath element '/data/app/com.miui.framework-2.apk'
try move this stuff to data and reboot, want to see the log if the files are present
Click to expand...
Click to collapse
These, are written in the bootclasspath of MIUI ROM ( so it's looking for it ), but doesnt exist in the ROM. I saw same kind of errors on a working ROM, so I think it can be ignored too.
jamal2367 said:
You can try to fix wifi ,sound and camera and Make it multirom ready ???
Its easier because its booting and yours not ??
Click to expand...
Click to collapse
I want to work on my ROM. I need my phone working so I use mine that works with multirom.