My phone reboots when I launch the camera app - Milestone XT720 General

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??

Related

Donut power widget - where is it?

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. ;/

[Dev/App/Framework] PDroid 2.0 Touchwiz port for JB OTA

Thanks
Thanks always have to go out first - Many thanks to Eschelon for the many hours of wiping/testing for me along with the rest of the Synergy team. I still don't have a gs3 so most of this was done blind and let me say that was a very difficult task. Of course thanks to all the original PDroid developers that made the base code available.
If you want to use this prebuilt into a rom - starting tonight (01Jan13 r147) Synergy builds will have this framework already ported in. You will just need to load on an APK to start blocking perms. Other rom devs I have included just the framework in post 2 - just make sure to give credit back to me/this thread- this took awhile to port over
What is it?
PDroid is a (awesome) security framework similar to superuser but allows selective blocking of app permissions. It creates a "proxy" between the actual permissions and the PDroid framework which allow passing of different return data.
Because of the proxy created this method is better than apps which just remove permissions from manifests because it should not cause any fcs- Apps will never know the difference. It also allows patching permissions such as location/android id/camera to return spoofed data.
PDroid is a very complex mod across many parts of framework. I have not seen a proper port of this done as of yet - We have spent much time verifying that this port of PDroid 2.0 successfully works with various permissions. See below screenshots for proof.
Framework Mods:
The framework portion of this mod is a port of the 20121017 patch of pdroid2.0 for cyanogenmod rewritten by me to work on TW.
The main patches are located here: https://github.com/mateor/auto-patcher/tree/master/patches/pd2.0/jellybean/cm/ I believe it is based off of CollegeDev's source from
http://forum.xda-developers.com/showthread.php?t=1923576
Downloads section below contain the modded services.jar/core.jar/framework.jar from the JellyBean OTA.
PDroid Application:
The app I preferred and what most of our testing was done on is called PDroid Manager - This is one of the only GPL licensed PDroid apps I have seen. The original thread is up here - http://forum.xda-developers.com/showthread.php?t=1994860
I needed to make some changes to deal with exception errors the original source was throwing. The original code is GPL'ed, my source is up in the Downloads section
If you do not want to use Pdroid Manager you can switch to the PDroid 2.0 App by installing it from original thread http://forum.xda-developers.com/showthread.php?t=1923576
**when switching apps you probably want to uninstall old one, delete /data/system/privacy.db reboot then install new app. I do not believe 2 can coexist**
Verifying PDroid Works:
A good test app is "Network Info II" from market. You can also use my Logging Test App to test some values such as android id. Other valid tests are items such as blocking Phone from Calls and verifying you get a call error or blocking maps from location.
The one thing we did notice was the stock camera app was not able to be blocked, but any 3rd party app that uses camera blocking will work (probably due to samsung's app using some hidden calls in framework via reflection)
Downloads:
PDroid 2.0 Framework + Application Zip (Its flashable, but untested. Really meant for rom devs) - http://www.androidfilehost.com/?fid=9390248398092763894
PDroid Manager - TrevE Mod APK Only (you must have framework installed aleady to use) - http://www.androidfilehost.com/?fid=9390248398092763896
PDroid Manager - TrevE Mod Source - http://www.androidfilehost.com/?fid=9390248398092763895
Screenshots:
Screenshots of PDroid 2.0 using PDroid Manager Application (Thanks Esch)
asdgfdadsfa
MINE!! awesome work mane
Nice work guys!! :good:
Guess this means my GTalk will finally quiet down some.
Great work guys.
Z
ziggy471 said:
Guess this means my GTalk will finally quiet down some.
Great work guys.
Z
Click to expand...
Click to collapse
I assume the synergy build will be out soon. Or already has. Just happened to see this first. Great work guys. :thumbup:
Sent from my SCH-I535 using xda premium
so I'm on the newest synergy and trying to get the hang of pdroid.
if I deny facebook access to anything it won't open and force closes. when i reallow it to access everything it still FCs until I purge pdroid settings. Not really sure what's happening.
im_on_fire said:
so I'm on the newest synergy and trying to get the hang of pdroid.
if I deny facebook access to anything it won't open and force closes. when i reallow it to access everything it still FCs until I purge pdroid settings. Not really sure what's happening.
Click to expand...
Click to collapse
Hmm, it's working properly on my end. It really shouldn't ever FC since PDroid just spoofs fake data, and it doesn't allow you to block full internet access since that would arguably cause most apps to FC, which would defeat PDroid's purpose.
Try deleting facebook and reinstalling fresh from the market. If it still FCs, post a logcat for us so we can take a look and maybe see what's going on.
eschelon said:
Hmm, it's working properly on my end. It really shouldn't ever FC since PDroid just spoofs fake data, and it doesn't allow you to block full internet access since that would arguably cause most apps to FC, which would defeat PDroid's purpose.
Try deleting facebook and reinstalling fresh from the market. If it still FCs, post a logcat for us so we can take a look and maybe see what's going on.
Click to expand...
Click to collapse
so this is me opening facebook successfully then opening pdroid and denying facebook gps location. then i try opening facebook again and it force closes:
Code:
--------- beginning of /dev/log/main
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
W/IInputConnectionWrapper(24989): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
I/Term (24989): Subprocess exited: 129
W/IInputConnectionWrapper(24989): showStatusIcon on inactive InputConnection
E/Term (24989): onCreate
D/Term (24989): TermService started
I/TermService(24989): Activity called onBind()
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Term (24989): Bound to TermService
I/TermService(24989): Activity binding to service
I/Term (24989): waiting for: 28326
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
W/IInputConnectionWrapper(24989): showStatusIcon on inactive InputConnection
E/Term (24989): onCreate
I/Term (24989): Bound to TermService
I/TermService(24989): Activity binding to service
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
let me know if this is incorrect. i used my phone to make the logcat. if not ill make one from my computer tonight. (also, i can't access pastebin from work)
I should also add that this happens with any app, not just facebook.
im_on_fire said:
so this is me opening facebook successfully then opening pdroid and denying facebook gps location. then i try opening facebook again and it force closes:
Code:
--------- beginning of /dev/log/main
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
W/IInputConnectionWrapper(24989): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(24989): endBatchEdit on inactive InputConnection
I/Term (24989): Subprocess exited: 129
W/IInputConnectionWrapper(24989): showStatusIcon on inactive InputConnection
E/Term (24989): onCreate
D/Term (24989): TermService started
I/TermService(24989): Activity called onBind()
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Term (24989): Bound to TermService
I/TermService(24989): Activity binding to service
I/Term (24989): waiting for: 28326
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
W/IInputConnectionWrapper(24989): showStatusIcon on inactive InputConnection
E/Term (24989): onCreate
I/Term (24989): Bound to TermService
I/TermService(24989): Activity binding to service
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
I/Adreno200-EGLSUB(24989): <ConfigWindowMatch:2087>: Format RGBA_8888.
let me know if this is incorrect. i used my phone to make the logcat. if not ill make one from my computer tonight. (also, i can't access pastebin from work)
I should also add that this happens with any app, not just facebook.
Click to expand...
Click to collapse
Do this: Plug you phone into a computer via USB and wait for your mass storage to open up, then in a command prompt type:
adb remount
adb logcat >log.txt
then hit enter and it will create that log.txt file in whatever filepath your command prompt is showing at will start logging (nothing will show up in that command prompt, but it will be actively logging in that file you just made). Then while that's running open facebook, let it crash, then go back to command prompt and hit ctrl+C
Throw that log.txt file on dropbox or something and send me or Trev a PM with a link to it
eschelon said:
Do this: Plug you phone into a computer via USB and wait for your mass storage to open up, then in a command prompt type:
adb remount
adb logcat >log.txt
then hit enter and it will create that log.txt file in whatever filepath your command prompt is showing at will start logging (nothing will show up in that command prompt, but it will be actively logging in that file you just made). Then while that's running open facebook, let it crash, then go back to command prompt and hit ctrl+C
Throw that log.txt file on dropbox or something and send me or Trev a PM with a link to it
Click to expand...
Click to collapse
i tried sending it to you last night but im not sure if it sent. it's not in my outbox
Always good to see another port. Great post!
If anyone is looking to use Pdroid Manager on other roms or devices you can use my tool the auto-patcher . Works on Cyanogen, PA, AOKP, Evervolv and AOSP along with many others. Touchwiz , Sense and smaller device specific roms usually fail to patch. We support CM7 to Android 4.1.2 for now.
Those source patches you got from my github are based off svyat's source. Additions were made by me, pastime1971 and CollegeDev.
i wonder if this can work on other gs3 variants such as tmobile version
I wonder if this could work on the stock Galaxy Note 2. Is there a reason that this PDroid port is variant/phone specific?
ayysir said:
i wonder if this can work on other gs3 variants such as tmobile version
Click to expand...
Click to collapse
This is for stock touchwiz roms.. based on your signature you're running a CM kang, under the assumption that the developer of your kang hasnt drastically modified any of the core components (unlikely) there are already instructions on how to patch pdroid into your rom.
Taken from the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1923576
http://forum.xda-developers.com/showthread.php?t=1719408
PDROID!!!
I saw this and said WHOA! out loud to myself. My main problem with Android has been and remains it's excessively permissive permissions (lol). Lack of PDroid was literally the number one reason I was hesitant to move from my Galaxy Nexus with AOSP to a Galaxy Note II with TouchWiz. Now that this is looking like it has legs, is there anything I can do to get this into the G Note II version of TouchWiz? Don't mind running an international ROM on my T-Mobile version in order to do this. I'm going to try and patch it at as is at a normal hour when I get up tomorrow, and I will report back! THANK YOU SO MUCH!
Edit: Got too excited and didn't the original posts thoroughly. Realistically I need to decompile and diff the core.jar, framework.jar and services.jar and see how difficult it would be to merge the changes into the GN2 JB builds. I thought originally this was a patch that would function like the autopatcher and do all the work for me . I may need guidance here when I inevitably bork this :-/
Tomorrow(ish)!
slycog said:
This is for stock touchwiz roms..
Click to expand...
Click to collapse
Soooooo I can use this on my ELLA (latest samsung) based ROM for the I9300 (international SGS3)?? or do i need to try any decompile and merge the source myself?
im_on_fire said:
so I'm on the newest synergy and trying to get the hang of pdroid.
if I deny facebook access to anything it won't open and force closes. when i reallow it to access everything it still FCs until I purge pdroid settings. Not really sure what's happening.
Click to expand...
Click to collapse
Exact same issue for me....same rom
nitric13 said:
Exact same issue for me....same rom
Click to expand...
Click to collapse
That's weird. My experience with Facebook and PDroid on AOSP ROMs hasn't caused a single force close... Which is really amazing when you think about it.

[Q] Google Play Store Doesn't Open

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.

[Q] JB 4.2.2 MMS issue

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?

[Q] Check flash memory for errors

Hey,
Can someone tell me how to check my flash memory? After 2-3 weeks of using my phone I get trouble with some apps like SwiftKey which is forgetting the settings and poping up with the first time usage wizard.
I already wiped everything and then it works for some weeks as I said but its really annoying. I am using the Cyanongenmod 12 .
Thanks
md
Edit:
When I get the wizard I can see following in the logcat:
03-06 11:44:44.962 11586-11614/com.touchtype.swiftkey E/SharedPreferencesImpl﹕ Couldn't rename file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml to backup file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml.bak
03-06 11:44:44.964 11586-11586/com.touchtype.swiftkey E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
03-06 11:44:45.545 11586-11614/com.touchtype.swiftkey E/SharedPreferencesImpl﹕ Couldn't rename file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml to backup file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml.bak
03-06 11:44:47.417
But no problem to rename the file by my own

Categories

Resources