Database Info

My phone reboots when I launch the camera app

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

[Q] Google Talk crashes when clicking a link

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?

Scheduled contextual profiles doesn't seem to work (now with logcat)

I searched the forum titles for "contextual" and didn't get any hits.
Then I searched the Q&A thread and found three hits but nobody responding with fixes or saying it worked for them.
I've set up Scheduled Contextual Profiles (day vs night theme). I can restore each theme without issue. And the automatic scheduling *says* it's applied one theme or the other, but the theme remains unchanged from what it was.
Is this feature still being worked on or is it actually working for anyone?
Me: Oreo 8.1 on OnePlus 5T running AOSP Extended ROM with SElinux enforcing (I only just now thought to try unenforcing but it'll be hours before I know if that helped).
Here are the other three posts in the Q&A with the same question, which is why I'm posting in the main forum. To see if we can get some traction on whether the feature is currently broken or if maybe we're just doing something wrong because it works for everyone else?
thedr34m13 said:
Scheduled contextual profiles aren't getting applied on my phone. I have a Moto g5 plus running NOS-Mod (with sysserv) 8.1. A notification pops up saying that the profile has been applied, but nothing changes. Manually changing profiles does work though. I tried with Andromeda, but it says debugging disabled, even though it isn't. Is there a possible fix?
Click to expand...
Click to collapse
KNGPN Q w Q said:
Hello everyone,
I just have a little question: is the automatic contextual profile switching actually working or do you manually need to do something to get it to work?
I have set it up to switch between Belo and Mono/Art during respectably day and night times and I noticed it actually tried switching between said themes, but didn't completely go through with it. What I mean with that, is that the theme of some elements did change, but not of all elements which made, for example, reading my notifications impossible. So again, is the automatic contextual profile switching completely working or did I simply have to wait a bit longer or are there some steps to be manually taken?
Click to expand...
Click to collapse
Dugatoembridge said:
I'm sorry if this has already been reported, but I searched on xda and other places but found nothing!
My problem is: automatic profile (day and night) does not work here! I get notification at the scheduled time saying that the profile will be applied as soon as the screen turns off, but this never happens. Deleted substratum data and re-created profiles, but problem persists.
Titan Xt1069 - EAX 4.4
Click to expand...
Click to collapse

I set up a profile to activate at 10:16AM and here are the logs of what happened (or didn't happen) for this activity.
My selinux was set to "permissive" at this time.
Code:
07-19 10:15:20.526 1319 3196 I ActivityManager: Start proc 12950:android.substratum.service/1000 for service android.substratum.service/.SubstratumHelperService
07-19 10:15:20.527 12612 12949 E SubstratumService: There was an exception when trying to apply profile
07-19 10:15:20.527 12612 12949 E SubstratumService: java.lang.NullPointerException: Attempt to invoke interface method 'void com.android.internal.substratum.ISubstratumHelperService.applyProfile(java.lang.String)' on a null object reference
07-19 10:15:20.527 12612 12949 E SubstratumService: at android.os.Parcel.readException(Parcel.java:2011)
07-19 10:15:20.527 12612 12949 E SubstratumService: at android.os.Parcel.readException(Parcel.java:1951)
07-19 10:15:20.527 12612 12949 E SubstratumService: at android.content.substratum.ISubstratumService$Stub$Proxy.applyProfile(ISubstratumService.java:493)
07-19 10:15:20.527 12612 12949 E SubstratumService: at projekt.substratum.common.platform.SubstratumService.applyProfile(SubstratumService.java:203)
07-19 10:15:20.527 12612 12949 E SubstratumService: at projekt.substratum.services.profiles.ScheduledProfileService$ApplyProfile.doInBackground(ScheduledProfileService.java:246)
07-19 10:15:20.527 12612 12949 E SubstratumService: at projekt.substratum.services.profiles.ScheduledProfileService$ApplyProfile.doInBackground(ScheduledProfileService.java:111)
07-19 10:15:20.527 12612 12949 E SubstratumService: at android.os.AsyncTask$2.call(AsyncTask.java:333)
07-19 10:15:20.527 12612 12949 E SubstratumService: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
07-19 10:15:20.527 12612 12949 E SubstratumService: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
07-19 10:15:20.527 12612 12949 E SubstratumService: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-19 10:15:20.527 12612 12949 E SubstratumService: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-19 10:15:20.527 12612 12949 E SubstratumService: at java.lang.Thread.run(Thread.java:764)
Full logcat attached.

Does anyone know if this feature will ever come back to Substratum?

System UI restart

Hi,
I have some issues with my HTC U12+. I had the issue before, I updated to the latest release (stock) and I still have this problem. I am on 1.53.401.5 version.
The issue is that randomly (not related to keeping the phone in my pocket or anything similar) the phone starts glitching and I see the "System UI Stopped working" message. On the screen it looks like it continuously tries to restart the System UI. Once or twice I was able to press the "Send report" button but I am not sure it worked.
It happens once 2-3 days and I cannot use the phone anymore. However, I am able to press the bower button and restart it, but otherwise, I cannot use it. Most of the times it happens when I do not use my phone at all. It is next to me, locked, and I see the screen glitching...
Did something similar happened to you as well? I use only "normal" applications, I do not have some strange configuration etc.
Any idea why this might happen?
Regards,
Mihai

Have you tried a Factory Reset?

MihaiTest said:
Hi,
I have some issues with my HTC U12+. I had the issue before, I updated to the latest release (stock) and I still have this problem. I am on 1.53.401.5 version.
The issue is that randomly (not related to keeping the phone in my pocket or anything similar) the phone starts glitching and I see the "System UI Stopped working" message. On the screen it looks like it continuously tries to restart the System UI. Once or twice I was able to press the "Send report" button but I am not sure it worked.
It happens once 2-3 days and I cannot use the phone anymore. However, I am able to press the bower button and restart it, but otherwise, I cannot use it. Most of the times it happens when I do not use my phone at all. It is next to me, locked, and I see the screen glitching...
Did something similar happened to you as well? I use only "normal" applications, I do not have some strange configuration etc.
Any idea why this might happen?
Regards,
Mihai
Click to expand...
Click to collapse
I've been having the exact same issue but not as often, like once every two weeks or so. haven't tried a factory reset yet but I think if I'll try that in case it gets worse

You guys are using Amazon music on different devices with the same account?
Sent from my HTC U12+ using XDA Labs

DeeZZ_NuuZZ said:
You guys are using Amazon music on different devices with the same account?
Click to expand...
Click to collapse
as a matter of fact I am using amazon music on my phone, my fire tv, and my laptop using the same account, obviously. what makes you think this could be the reason for the system ui restarts? thanks for looking into it!

hojnol said:
as a matter of fact I am using amazon music on my phone, my fire tv, and my laptop using the same account, obviously. what makes you think this could be the reason for the system ui restarts? thanks for looking into it!
Click to expand...
Click to collapse
my parents had one account on the u11+ and u11 and they both had problems. I told them to deactive the app on one phone and the systemUI related bugs didn't happen anymore. several other people also had the exact same issue. it's something related to an update from amazon music and their server... I don't know if the new music app update changed something... but HTC and probably Amazon are aware of that

good hint, thanks!
Same issue happening here and yes, amazon music is installed...

I've now deactivated background data for amazon music and see if that does anything, I'll report back

Thank you for support!
However, I never had Amazon Music installed and it happened to me multiple times.
I removed some applications (including Spotify considering it might act similar) and I will let you know if it happens again!

My mother just told me, that it happens again, even though Amazon music is only activated on one device. Gonna try to find out what could be else the problem. If it's definitely not related to Amazon I gonna contact someone, so they can investigate further
Sent from my HTC U12+ using XDA Labs

Well, it just happened to me again. I do not have Amazon Music or any strange app...
However, I've seen on some other discussions that Google App might be responsible. I uninstalled updates for Google App, forced stopped it and Disable it.
I will let you know if this still happens. You can also try this possible "solution".
Edit: I also cleaned up and now I have more than 25 GB available. Just to be sure "not enough free space" is not an issue anymore.

MihaiTest said:
Well, it just happened to me again. I do not have Amazon Music or any strange app...
However, I've seen on some other discussions that Google App might be responsible. I uninstalled updates for Google App, forced stopped it and Disable it.
I will let you know if this still happens. You can also try this possible "solution".
Edit: I also cleaned up and now I have more than 25 GB available. Just to be sure "not enough free space" is not an issue anymore.
Click to expand...
Click to collapse
Thanks, please report back if something like that happens again. My parents told me that it happened after the u11+ update came out. Before that the u11 (which got its update last summer or so) was totally fine and the u11+ too. After the latest u11+ update and when the Amazon music app was updates those things happened. At first it was fine with disabling Amazon music on one phone. But after some weeks it started again, app still disabled... I gonna flash a ruu on the u11 from my mother. She also has wifi issues, there the phone doesn't connect with the router anymore, even after re-applying the password or completely reset the network settings
Sent from my HTC U12+ using XDA Labs

Well, I am sorry to come with bad news, but it happened again. After 2 days. It is also strange that it happened last time, two days ago, around the same hour...
This means that, at least for me, uninstalling Google App and having a lot of free space, do not solve the issue.
I will continue to find a solution and I will keep you posted. Thank you for support!
Edit: I tried to fine something useful in the logs. This is a grep -i systemui (after the issue happened, unfortunately):
Code:
03-14 11:06:36.835 1270 1337 W PackageParser: Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.CONFIGURE_WIFI_DISPLAY in package: com.android.systemui at: Binary XML file line #128
03-14 11:06:36.859 1270 1270 I PackageManager: /system/priv-app/SystemUI changed; collecting certs
03-14 11:06:36.914 1270 1270 E PackageManager: Adding duplicate user id: 10003 name=com.android.systemui
03-14 11:06:37.732 1270 1270 W PackageManager: Failed to migrate com.android.systemui: android.os.ServiceSpecificException: Failed to mark default storage /data/data/com.android.systemui (code 95)
03-14 11:06:39.351 1270 1270 W InputMethodManagerService: null called updateSystemUiLocked(mCurToken=null, vis=0) from com.android.server.InputMethodManagerService.systemRunning(InputMethodManagerService.java:1445) <- com.android.server.InputMethodManagerService$Lifecycle.onBootPhase(InputMethodManagerService.java:1227)
03-14 11:06:39.393 1270 1270 I SystemServer: StartSystemUI
03-14 11:06:39.399 1270 1270 I ActivityManager: Start proc 1637:com.android.systemui/u0a3 for service com.android.systemui/.SystemUIService
...
03-14 11:06:46.427 1270 1296 W PackageManager: Failed to migrate com.android.systemui: android.os.ServiceSpecificException: Failed to mark default storage /data/data/com.android.systemui (code 95)
...
03-14 11:06:58.429 2723 2723 W InputMethodManagerService: null called updateSystemUiLocked(mCurToken=null, vis=0) from com.android.server.InputMethodManagerService.systemRunning(InputMethodManagerService.java:1445) <- com.android.server.InputMethodManagerService$Lifecycle.onBootPhase(InputMethodManagerService.java:1227)
03-14 11:06:58.508 2723 2723 I SystemServer: StartSystemUI
03-14 11:06:58.523 2723 2723 I ActivityManager: Start proc 3012:com.android.systemui/u0a16 for service com.android.systemui/.SystemUIService
03-14 11:06:58.718 2723 2723 V WallpaperManagerService: bindWallpaperComponentLocked: componentName=ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper}
...
03-14 11:07:20.358 2723 2752 W BroadcastQueue: Permission Denial: broadcasting Intent { act=com.htc.cover.closed flg=0x1000030 (has extras) } from null (pid=-1, uid=-1) requires com.htc.permission.APP_DEFAULT due to registered receiver BroadcastFilter{9ea0fc2 u0 ReceiverList{178f40d 3012 com.android.systemui/10016/u0 remote:c9cdea4}}
...
03-14 11:07:54.673 2723 2723 V FingerprintService: startAuthentication(com.android.systemui)
03-14 11:07:54.674 2723 2723 V FingerprintService: starting client AuthenticationClient(com.android.systemui), initiatedByClient = true)
03-14 11:07:54.687 2723 2753 D StatusBarManagerService: setSystemUiVisibility(0x408608)
03-14 11:07:54.687 2723 2753 D StatusBarManagerService: setSystemUiVisibility(0x408608)
03-14 11:07:54.687 2723 2753 D StatusBarManagerService: setSystemUiVisibility(0x408608)
03-14 11:07:54.704 2723 2723 W FingerprintService: client com.android.systemui is authenticating...
...
03-14 11:09:33.612 2723 2723 V FingerprintService: onAuthenticated(owner=com.android.systemui, id=-1298556996, gp=0)
03-14 11:09:33.617 2723 2723 V FingerprintService: Done with client: com.android.systemui
...
03-14 11:14:04.812 3012 18215 D MediaPlayer: ANDROID_HTC_INVOKE_GET_CALLING_PROCESS packageName: com.android.systemui
03-14 11:14:04.872 3012 3012 I zygote64: Deoptimizing void com.android.systemui.statusbar.NotificationContentView.selectLayout(boolean, boolean) due to JIT inline cache
03-14 11:14:04.895 3012 3012 I chatty : uid=10016(u0_a16) com.android.systemui identical 380 lines
03-14 11:14:05.393 3012 18215 I chatty : uid=10016(u0_a16) com.android.systemui expire 3 lines
03-14 11:14:06.418 3012 18274 I chatty : uid=10016(u0_a16) com.android.systemui expire 8 lines
...
03-14 11:25:29.780 3012 3012 I zygote64: Deoptimizing float com.android.systemui.statusbar.stack.StackScrollAlgorithm.updateChildZValue(int, float, com.android.systemui.statusbar.stack.StackScrollState, com.android.systemui.statusbar.stack.StackScrollAlgorithm$StackScrollAlgorithmState, com.android.systemui.statusbar.stack.AmbientState) due to JIT inline cache
03-14 11:25:29.780 3012 3012 I zygote64: Deoptimizing void com.android.systemui.statusbar.stack.StackScrollAlgorithm.updateClipping(com.android.systemui.statusbar.stack.StackScrollState, com.android.systemui.statusbar.stack.StackScrollAlgorithm$StackScrollAlgorithmState, com.android.systemui.statusbar.stack.AmbientState) due to JIT inline cache
03-14 11:25:29.782 3012 3012 I zygote64: Deoptimizing void com.android.systemui.statusbar.stack.ExpandableViewState.animateTo(android.view.View, com.android.systemui.statusbar.stack.AnimationProperties) due to JIT inline cache
03-14 11:25:30.020 3012 3012 I chatty : uid=10016(u0_a16) com.android.systemui identical 6 lines
...
03-14 11:26:18.628 2723 3950 D BoostFramework: perfHint : hint: 0x1081 pkg_name(userDataStr): com.android.systemui:tuner duration(userData1): 2000 type(userData2): 1
03-14 11:26:18.630 2723 3950 I ActivityManager: START u0 {act=com.android.settings.action.DEMO_MODE cmp=com.android.systemui/.DemoMode} from uid 1000 pid 13556
03-14 11:26:18.639 2723 3950 D ANDR-PERF-ACT-TRIG: start activity com.android.systemui/com.android.systemui.DemoMode/26
03-14 11:26:18.639 2723 3950 D ActivityTrigger: activityStartTrigger: Activity is Triggerred in full screen ApplicationInfo{67c3891 com.android.systemui}
03-14 11:26:18.639 2723 3950 E ActivityTrigger: activityStartTrigger: not whiteListedcom.android.systemui/com.android.systemui.DemoMode/26
03-14 11:26:18.639 2723 3950 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{67c3891 com.android.systemui} is now in focus and seems to be in full-screen mode
03-14 11:26:18.640 2723 2753 D StatusBarManagerService: setSystemUiVisibility(0xa618)
03-14 11:26:18.643 2723 3950 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{67c3891 com.android.systemui} is now in focus and seems to be in full-screen mode
03-14 11:26:18.654 2723 3950 I ActivityManager: Start proc 21509:com.android.systemui:tuner/u0a16 for activity com.android.systemui/.DemoMode
03-14 11:26:18.655 2723 3950 D BoostFramework: perfHint : hint: 0x1081 pkg_name(userDataStr): com.android.systemui:tuner duration(userData1): -1 type(userData2): 3
03-14 11:26:18.657 2723 2753 D StatusBarManagerService: setSystemUiVisibility(0xa618)
03-14 11:26:18.657 7747 7763 I [B+]AppInfoService: [onVisiblePackageChanged] packages:com.android.systemui
03-14 11:26:18.657 7747 7763 I [B+]AppInfoSyncManager: [onAppInfoEvent] app:com.android.systemui
...
03-14 11:26:18.668 7747 7763 I [B+]TopPkgCallbackHelper: sendVisiblePackageChanged-- PackageName: com.android.systemui, TimeStamp: 1552555578657, ExtraPackageName: NULL, Extra2PackageName: NULL
03-14 11:26:18.671 2723 2753 D StatusBarManagerService: setSystemUiVisibility(0xa618)
03-14 11:26:18.673 2723 3950 D InputDispatcher: setFocus: AppWindowToken{3e916da token=Token{23012b8 ActivityRecord{195f11b u0 com.android.systemui/.DemoMode t8600}}}
...
03-14 11:45:20.230 3012 3051 W zygote64: Checksum mismatch for dex SystemUI.apk
03-14 11:45:20.230 3012 3051 W zygote64: Checksum mismatch for dex SystemUI.apk
I think this might be important: 03-14 11:45:20.230 3012 3051 W zygote64: Checksum mismatch for dex SystemUI.apk
Maybe the APK was corrupted somehow?
If you have any ideas, please let me know.

Another opinion : chech your SIM.
If your nano-SIM is part of a normal-SIM or micro-SIM (knife cut) it may not fit well and causes problems (random restarts).

pavlidisc said:
Another opinion : chech your SIM.
If your nano-SIM is part of a normal-SIM or micro-SIM (knife cut) it may not fit well and causes problems (random restarts).
Click to expand...
Click to collapse
Not the problem here/ for my mother's u11 and father's u11+
Sent from my HTC U12+ using XDA Labs
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
@MihaiTest
Thanks for the log, gonna forward it. Couldn't get a log on my parents phones, because it happened when I wasn't at home
Sent from my HTC U12+ using XDA Labs

DeeZZ_NuuZZ - My pleasure!
I also did a full dump (bug report) and sent an email to HTC (hopefully, in the right direction).
They mentioned I should receive something back in maximum 48 so I will update you as soon as possible.

Are you registered to Google Search App beta, or are you using stable release channel. In the past such errors were thrown a lot and only if an update of Google App had errors.
Sent from my HTC U12+ using XDA Labs

I am using the stable release channel, no beta for Google App (did not even know about this) which is also uninstalled right now.
PS: I also copied the SystemUI.apk. Is there anyone (who does not have this issue - or who does) who can copy it and share it? I would like to "diff" it, to see if my APK is somehow corrupted.

Talking about crashes, I have noticed that if you use an animated wallpaper, after a few hours you won't be able to wake the screen anymore, it will remain black and the only solution is to force reboot.

hojnol said:
I've now deactivated background data for amazon music and see if that does anything, I'll report back
Click to expand...
Click to collapse
so far not a single ui restart after deactivation of background data for amazon music

Question Camera problem

Hi guys, I have a problem with my camera, it doesn't work anymore in aosp and in miui it only opens in video recording mode and with monochrome colors, on gcam everything works, but with monochrome colors too, I've done everything I could imagine trying to fix this, but nothing went right, does anyone have an idea what it is?
I have the error log when I try to open the camera, if anyone can help, I appreciate it.
io.reactivex.exceptions.OnErrorNotImplementedException: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Unknown Source:2)
at io.reactivex.internal.functions.Functions$OnErrorMissingConsumer.accept(Unknown Source:2)
at io.reactivex.internal.observers.LambdaObserver.onError(Unknown Source:13)
at io.reactivex.internal.observers.LambdaObserver.onNext(Unknown Source:25)
at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.drainNormal(Unknown Source:47)
at io.reactivex.internal.operators.observable.ObservableObserveOn$ObserveOnObserver.run(Unknown Source:8)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(Unknown Source:13)
at io.reactivex.internal.schedulers.ScheduledRunnable.call(Unknown Source:0)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
Caused by: com.android.camera2.vendortag.VendorTagNotFoundException: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
at com.android.camera2.vendortag.VendorTagHelper.trySetValue(Unknown Source:61)
at com.android.camera2.vendortag.VendorTagHelper.setValue(Unknown Source:4)
at com.android.camera2.compat.MiCameraCompatQcomImpl.applySaturation(Unknown Source:24)
at com.android.camera2.compat.MiCameraCompat.applySaturation(Unknown Source:2)
at com.android.camera2.CaptureRequestBuilder.applySaturation(Unknown Source:10)
at com.android.camera2.MiCamera2.setSaturation(Unknown Source:34)
at com.android.camera.module.Camera2Module.updateSaturation(Unknown Source:44)
at com.android.camera.module.Camera2Module.consumePreference(Unknown Source:258)
at com.android.camera.module.BaseModule.accept(Unknown Source:85)
at com.android.camera.module.BaseModule.accept(Unknown Source:2)
at io.reactivex.internal.observers.LambdaObserver.onNext(Unknown Source:8)
... 9 more
Caused by: java.lang.IllegalArgumentException: Could not find tag for key 'org.codeaurora.qcamera3.saturation.use_saturation')
at android.hardware.camera2.impl.CameraMetadataNative.nativeGetTagFromKeyLocal(Native Method)
at android.hardware.camera2.impl.CameraMetadataNative.setBase(Unknown Source:17)
at android.hardware.camera2.impl.CameraMetadataNative.set(Unknown Source:14)
at android.hardware.camera2.impl.CameraMetadataNative.set(Unknown Source:4)
at android.hardware.camera2.CaptureRequest$Builder.set(Unknown Source:6)
at com.android.camera2.vendortag.VendorTagHelper.trySetValue(Unknown Source:19)
... 19 more

Can You fix it ?

pudiste solucionar el problema? I have the same error

Hey guys! I also got this problem. Could you solve it? And if yes how did you do? Thanks for answears! I burnt my phone and I needed to replace two camera sensor. But now I got the shame issue.

I have same problem, any idea?

Anyone solved this? I have the same issue

allblacks19992 said:
Anyone solved this? I have the same issue
Click to expand...
Click to collapse
Test vendor image or the full fastboot rom