I am having the feared random reboots in my recently acquired Droid 3.
It is rebooting more than 10 times a day randomly, both when idle and when doing anything in the phone.
The only pattern I've been to able to catch is that around 30 seconds before a reboot, I loose phone signal (the signal strength meter is empty and showing a cross). WiFi keeps working until the reboot.
I am located in Spain and using the phone in GSM/UMTS mode, with CDMA disabled. Some times when I loose the signal prior to a reboot, I get a pop-up asking if I want to put the phone in "global" mode for it to search for CDMA signal.
I am using rooted Steel Droid 3 with OTA 5.6.890, but it happened with Verizon's stock ROM as well.
I have googled extensively for the last couple of days and did everything I have found about possible solutions:
- Factory reset and disabling Google restoring features on initial config (to prevent restoring WiFi hotspot data, alleged to cause reboots)
- Manually wiping all WiFi hotspot info
- Disable WiFi
- Running with no apps installed
- Formatting sd card
- Wiping user data and cache from Recovery
- Checking if the battery is loose, wedge a piece of paper to lock it in place
None of this have prevented or even alleviated the random reboots.
I'm fearing my phone might be a total lemon, but unfortunately as I am in Spain I can't return it and get a replacement. Anyway I have been reading that people have returned their Droids four or five times and still get random reboots in every new or refurbished Droid they get.
Other than that the phone works perfectly well, and I really love it. But having reboots when you are in the middle of something is going to get more and more annoying and I fear I will throw it out of the window sooner or later. I really need to solve this.
I run adb logcat in hopes of finding what is causing it, but it didn't see anything revelatory. Here are the tails of my last 3 logs before a crash:
Code:
12-06 22:39:43.764 512 3986 W Smack/Packet: notify conn break (IOEx), close connection12-06 22:39:43.764 512 3986 D Smack : [XMPPConn] close connection, notifyClosed=false
12-06 22:39:43.921 512 608 I GTalkService: [GTalkConnection.18] connectionClosed: connId=28343, error=CONNECTION FAILED
12-06 22:39:43.921 317 323 D ConnectivityService: reportNetworkCondition(1,0)
12-06 22:39:43.929 317 370 D ConnectivityService: Inet connectivity change,net=1, condition=0,mActiveDefaultNetwork=1
12-06 22:39:43.929 317 370 D ConnectivityService: starting a change hold12-06 22:39:43.936 512 608 I GTalkService: [GTalkConnection.18] (WORKER THREAD) update account status
12-06 22:39:43.999 512 608 I GTalkService: [GTalkConnection.18] (WORKER THREAD) update account status - done, took 58 ms
12-06 22:39:46.944 400 400 D StatusBarPolicy: the netConditon of netType 1 is updated as 0 by android.net.conn.INET_CONDITION_ACTION,icon color should be white.
12-06 22:39:46.944 400 400 V StatusBarPolicy: NetworkInfo: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, inetCondition= 0
12-06 22:39:46.944 400 400 V StatusBarPolicy: mModemIsResetting=false
12-06 22:39:46.944 317 370 D ConnectivityService: Inet hold end, net=1, condition =0, published condition =100
12-06 22:39:59.702 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 22:39:59.702 195 237 D libmdmctrl:
12-06 22:39:59.702 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 22:39:59.702 195 237 D libmdmctrl:
Code:
12-06 23:12:14.951 533 1016 I EventLogService: Aggregate from 1323209010096 (log), 1323207734851 (data)12-06 23:12:16.654 317 382 D dalvikvm: GC_EXPLICIT freed 143K, 38% free 8201K/13063K, external 5433K/6784K, paused 158ms
12-06 23:12:21.990 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 23:12:21.990 195 237 D libmdmctrl:
12-06 23:12:21.990 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 23:12:21.990 195 237 D libmdmctrl:
12-06 23:12:24.591 4743 4754 W googleanalytics: Problem with socket or streams.
12-06 23:12:24.591 4743 4754 W googleanalytics: java.net.ConnectException: google-analytics.com/127.0.0.1:80 - Connection refused
12-06 23:12:24.591 4743 4754 W googleanalytics: at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)
12-06 23:12:24.591 4743 4754 W googleanalytics: at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:437)
12-06 23:12:24.591 4743 4754 W googleanalytics: at java.net.Socket.connect(Socket.java:983)
12-06 23:12:24.591 4743 4754 W googleanalytics: at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
12-06 23:12:24.591 4743 4754 W googleanalytics: at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
12-06 23:12:24.591 4743 4754 W googleanalytics: at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
12-06 23:12:24.591 4743 4754 W googleanalytics: at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingEvents(Unknown Source)
12-06 23:12:24.591 4743 4754 W googleanalytics: at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
12-06 23:12:24.591 4743 4754 W googleanalytics: at android.os.Handler.handleCallback(Handler.java:587)
12-06 23:12:24.591 4743 4754 W googleanalytics: at android.os.Handler.dispatchMessage(Handler.java:92)
12-06 23:12:24.591 4743 4754 W googleanalytics: at android.os.Looper.loop(Looper.java:130)
12-06 23:12:24.591 4743 4754 W googleanalytics: at android.os.HandlerThread.run(HandlerThread.java:60)
12-06 23:12:24.849 445 467 D dalvikvm: GC_CONCURRENT freed 1098K, 49% free 4008K/7815K, external 2692K/3351K, paused 2ms+2ms
12-06 23:12:24.896 445 445 W KeyCharacterMap: Can't open keycharmap file
12-06 23:12:24.896 445 445 W KeyCharacterMap: Error loading keycharmap file'/data/usr/keychars/omap-keypad.kcm.bin'. hw.keyboards.0.devname='omap-keypad'
Code:
12-06 23:46:26.576 677 1930 W IdleConnectionHandler: Removing a connection that never existed!
12-06 23:46:33.584 1480 1491 W googleanalytics: Problem with socket or streams.
12-06 23:46:33.584 1480 1491 W googleanalytics: java.net.ConnectException: google-analytics.com/127.0.0.1:80 - Connection refused
12-06 23:46:33.584 1480 1491 W googleanalytics: at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)
12-06 23:46:33.584 1480 1491 W googleanalytics: at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:437)
12-06 23:46:33.584 1480 1491 W googleanalytics: at java.net.Socket.connect(Socket.java:983)
12-06 23:46:33.584 1480 1491 W googleanalytics: at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
12-06 23:46:33.584 1480 1491 W googleanalytics: at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
12-06 23:46:33.584 1480 1491 W googleanalytics: at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
12-06 23:46:33.584 1480 1491 W googleanalytics: at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingEvents(Unknown Source)
12-06 23:46:33.584 1480 1491 W googleanalytics: at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
12-06 23:46:33.584 1480 1491 W googleanalytics: at android.os.Handler.handleCallback(Handler.java:587)
12-06 23:46:33.584 1480 1491 W googleanalytics: at android.os.Handler.dispatchMessage(Handler.java:92)
12-06 23:46:33.584 1480 1491 W googleanalytics: at android.os.Looper.loop(Looper.java:130)
12-06 23:46:33.584 1480 1491 W googleanalytics: at android.os.HandlerThread.run(HandlerThread.java:60)
12-06 23:46:36.334 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 23:46:36.334 195 237 D libmdmctrl:
12-06 23:46:36.334 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 23:46:36.334 195 237 D libmdmctrl:
I have seen that the most common before-reboot output is
Code:
12-06 22:39:59.702 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 22:39:59.702 195 237 D libmdmctrl:
12-06 22:39:59.702 195 237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 22:39:59.702 195 237 D libmdmctrl:
But I have googled for libmdmctrl and there is only 1 result that has nothing to do with anything.
I am really in the dark, thanks for any help!
I'm gonna have to go out on a limb here, but if this is happening on two different ROMs, and after you reset all data and cache, etc. Then its probably a hardware issue. I'm not positive, but software problems will go away when you reset/flash a different ROM.
Sent from my DROID3 using XDA App
Thanks, my last shot is to try CyanogenMod 7 but I have read camera and GSM doesn't work in Droid 3, which would render my phone almost useless.
Anyway will serve to rule out hardware if it doesn't reboot in with that ROM.
I also saw when I read the log, that your phone is having issues with the hardware keyboard, I doubt that would cause a reset though.
Sent from my DROID3 using XDA App
mccoy51 said:
Thanks, my last shot is to try CyanogenMod 7 but I have read camera and GSM doesn't work in Droid 3, which would render my phone almost useless.
Anyway will serve to rule out hardware if it doesn't reboot in with that ROM.
Click to expand...
Click to collapse
Yeah try all different ROMs. That's all you can try.
Sent from my DROID3 using XDA App
ChaoticWeaponry said:
I also saw when I read the log, that your phone is having issues with the hardware keyboard, I doubt that would cause a reset though.
Click to expand...
Click to collapse
I am using Spanish language and the keyboard is English layout, basically it lacks Spanish characters as ñ ´ ¡ ¿...
I think that might be it, a layout mismatch. But the keyboard works fine when typing so I think this is not a big issue. It crashes when idling with the keyboard closed so I really think it's not related.
mccoy51 said:
I am using Spanish language and the keyboard is English layout, basically it lacks Spanish characters as ñ ´ ¡ ¿...
I think that might be it, a layout mismatch. But the keyboard works fine when typing so I think this is not a big issue. It crashes when idling with the keyboard closed so I really think it's not related.
Click to expand...
Click to collapse
Have you ran any deboating scripts or frozen/uninstalled system apps? Any scripts that you have run recently??
Sent from my DROID3 using XDA App
No, no debloating or messing with system apps when using stock, no special scripts except rooting.
Okay then its probably ROM or hardware related. I had the same problems when I removed some system control apps.
Sent from my DROID3 using XDA App
Do you use Titanium Backup or something similar? Try just installing the ROM and customize it manually and download and set everything up manually. If it don't work then call CS and tell them your phone is rebooting, try their troubleshooting steps, and get a warranty refurb shipped to your house.
Sent from my DROID3 using XDA App
Crap, I saw you were in Spain. Well if you don't have any warranty or insurance you are screwed probably.
Sent from my DROID3 using XDA App
Just installed CyanogenMod 7, and no reboots so far. Will keep it on overnight to make sure.
GSM doesn't work so I can't make phone calls or SMS. WiFi works fine.
As the pattern for my reboots was loosing signal prior to a reboot, if I don't get any reboots now it means the problem is related to telephony...
Thanks for the help so far!
mccoy51 said:
Just installed CyanogenMod 7, and no reboots so far. Will keep it on overnight to make sure.
GSM doesn't work so I can't make phone calls or SMS. WiFi works fine.
As the pattern for my reboots was loosing signal prior to a reboot, if I don't get any reboots now it means the problem is related to telephony...
Thanks for the help so far!
Click to expand...
Click to collapse
Someone in the Development forums made a GSM patch for CM7
Tried this patch
http://forum.xda-developers.com/showthread.php?t=1357350
But still get only CDMA and EvDO as network options, no GSM / 3G... under settings -> Wireless & networks -> Mobile networks -> Network Preferences
mccoy51 said:
Tried this patch
http://forum.xda-developers.com/showthread.php?t=1357350
But still get only CDMA and EvDO as network options, no GSM / 3G... under settings -> Wireless & networks -> Mobile networks -> Network Preferences
Click to expand...
Click to collapse
Nothings going right for you today.. haha try reinstalling everything.
Format /system
Factory data reset
Reinstall CM7
Boot
Turn off
Install Patch
Factory data reset
Boot.
-Try that..
Installed Liberty 2.0 in the end.
Still having reboots, but much less often. Same symptoms: Loose of signal, and 30 seconds later, reboot.
So it's something to do with telephony, but for some reason the amount of reboots seems to be lower with Liberty 2.0.
Found a solution!
I tried a different approach, seeing the problem was with radio / telephony...
I put in another SIM from a different carrier, and so far I am having no reboots!
What is the difference? My main carrier is a "virtual carrier", a company that rents other company's network to offer their service, usually with more competitive prices.
The SIM I'm using now is from a traditional carrier that owns the network directly.
What I think happens is that when using a virtual carrier, you are having a sort of permanent roaming: the phone has to first get into the network owning carrier and then join the virtual network of the virtual carrier. Somehow this is making the Droid 3 crazy.
The signal strength meter was indeed showing a small "R" indicating I was in roaming. I assumed this was because being an US phone, it took any non-US network as roaming, but now that I am using the regular carrier SIM, the signal strength bar is not showing "R" anymore.
Seems I will have to change my carrier to a network owner, which unfortunately have much less competitive prices. But at least I found a way of using the Droid 3 without constant reboots!!
For future reference to other Spanish users: I am having the reboots using a Simyo SIM (which runs on the Orange network), but with a Movistar SIM there are no reboots.
is it an XT860??
It's an XT862 (Verizon)
had me confused since you are overseas!
Related
I'm having issues modifying framework-res.apk
I already checked some of the other posts and guides.
I'm working on a Motorola Backflip running j_r0dd's Preclair v1.0.3
I just switched my carrier from AT&T to T-Mobile.
I get stuck in a boot loop or get no results at all depending on whether I push or copy/paste the new file and whether I do it when the phone is running or in recovery mode.
Any help would be greatly appreciated.
Here is what I had posted on modmymobile.com:
Ok. I'll try again. Thanks for the help. I'll let you know how it goes.
What about signing? If I am using App Manager can I just recompile and sign with App Manager? I am about to try this. I'm performing a nandroid backup now. I'll report back how it works out. The only value I changed was the onsText maxLength value from 18 to 3.
1. I decompiled with App Manager
2. I edited the status-bar.xml file.
3. I choose 11. Compile apk option in Apk Manager.
4. I answered Y to system file and to the option for the keep folder.
5. I deleted status-bar.xml and the resources file from the keep folder.
6. I pressed enter to continued in Apk Manager
7. I selected 12. Sign apk option in Apk Manager.
8. I am now pushing the framework-res.apk to the phone in recovery mode
9. Restarted just fine but no changes have taken place.
I checked the file sizes of the original and the modified framework-res.apk files and the original is 2899KB and the modified is only 1731KB. After I changed the file and rebooted the one on the phone was back to 2899KB.
I'll try copying the file with root explorer instead of pushing just to make sure it is overwriting.
After this operation I get this in the logcat:
11-19 11:22:30.666 195 204 W WallpaperService: Wallpaper service gone: ComponentInfo{a
ndroid/com.android.internal.service.wallpaper.ImageWallpa per**
11-19 11:22:30.666 195 204 W WallpaperService: Reverting to built-in wallpaper!
11-19 11:22:30.666 195 204 W dalvikvm: threadid=15: thread exiting with uncaught excep
tion (group=0x4001e278)
11-19 11:22:30.676 195 204 E AndroidRuntime: Uncaught handler: thread android.server.S
erverThread exiting due to uncaught exception
11-19 11:22:30.676 195 204 E AndroidRuntime: *** EXCEPTION IN SYSTEM PROCESS. System
will crash.
11-19 11:22:30.746 195 204 E AndroidRuntime: java.lang.IllegalArgumentException: Unkno
wn component ComponentInfo{android/com.android.internal.service.wallpaper.ImageWallpa per**
11-19 11:22:30.746 195 204 E AndroidRuntime: at com.android.server.WallpaperMan
agerService.bindWallpaperComponentLocked(Wallpaper ManagerService.java:476)
11-19 11:22:30.746 195 204 E AndroidRuntime: at com.android.server.WallpaperMan
agerService$WallpaperConnection.onServiceDisconnec ted(WallpaperManagerService.java:191)
11-19 11:22:30.746 195 204 E AndroidRuntime: at android.app.ActivityThread$Pack
ageInfo$ServiceDispatcher.doConnected(ActivityThre ad.java:1130)
11-19 11:22:30.746 195 204 E AndroidRuntime: at android.app.ActivityThread$Pack
ageInfo$ServiceDispatcher$RunConnection.run(Activi tyThread.java:1151)
11-19 11:22:30.746 195 204 E AndroidRuntime: at android.os.Handler.handleCallba
ck(Handler.java:587)
11-19 11:22:30.746 195 204 E AndroidRuntime: at android.os.Handler.dispatchMess
age(Handler.java:92)
11-19 11:22:30.746 195 204 E AndroidRuntime: at android.os.Looper.loop(Looper.j
ava:136)
11-19 11:22:30.746 195 204 E AndroidRuntime: at com.android.server.ServerThread
.run(SystemServer.java:469)
11-19 11:22:30.776 288 288 W Launcher.Model: Nobody to tell about the new app. Launch
er is probably loading.
11-19 11:22:30.846 195 204 E CheckinService: Can't find package android
11-19 11:22:31.076 1020 1024 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.086 596 602 I ActivityThread: Removing dead content provider: subscribe
dfeeds
11-19 11:22:31.086 293 305 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.096 744 749 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.106 691 810 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.106 674 679 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.106 552 557 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.116 488 495 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.126 403 407 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.126 284 299 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.126 284 299 I ActivityThread: Removing dead content provider: com.motor
ola.android.providers.settings
11-19 11:22:31.126 284 299 I ActivityThread: Removing dead content provider: com.motor
ola.android.server.checkin
11-19 11:22:31.126 288 301 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.136 282 297 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.136 270 274 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.136 370 376 I ActivityThread: Removing dead content provider: com.motor
ola.android.providers.settings
11-19 11:22:31.146 705 710 I ActivityThread: Removing dead content provider: com.motor
ola.android.server.checkin
11-19 11:22:31.216 641 645 I System.out: util.Log 4: ActivityThread :Removing dead co
ntent provider: settings: android.os.DeadObjectException
11-19 11:22:31.226 155 155 E vold : Framework disconnected
11-19 11:22:31.236 596 601 I ActivityThread: Removing dead content provider: settings
11-19 11:22:31.246 160 160 E installd: eof
11-19 11:22:31.246 160 160 E installd: failed to read size
11-19 11:22:31.256 641 645 W System.err: android.os.DeadObjectException
11-19 11:22:31.256 155 155 E vold : Unable to read framework command (Bad file numb
er)
11-19 11:22:31.256 155 155 E vold : Error processing framework command (Bad file nu
mber)
11-19 11:22:31.266 155 155 E vold : Unable to read framework command (Bad file numb
er)
11-19 11:22:31.266 155 155 E vold : Error processing framework command (Bad file nu
mber)
11-19 11:22:31.286 420 429 I System.out: util.Log 4: ActivityThread :Removing dead co
ntent provider: settings: android.os.DeadObjectException
11-19 11:22:31.286 420 429 W System.err: android.os.DeadObjectException
11-19 11:22:31.306 641 645 W System.err: at android.os.BinderProxy.transact(Native
Method)
11-19 11:22:31.306 641 645 W System.err: at android.os.ICheckinService$Stub$Proxy.l
og(ICheckinService.java:327)
11-19 11:22:31.316 641 645 W System.err: at android.util.Log.logCheckin(Log.java:16
1)
11-19 11:22:31.316 641 645 W System.err: at android.util.Log.i(Log.java:273)
Then this just loops:
11-19 11:22:32.356 1341 1341 E QC-QMI : Client: qmux_client ID is 53d
11-19 11:22:33.566 1340 1340 E AudioHardwareMSM72XX: start AudioHardware
11-19 11:22:33.576 1340 1340 E AudioHardwareMSM72XX: constructed (0 SND endpoints)
11-19 11:22:33.576 1340 1340 E AudioHardwareMSM72XX: AudioHardware::initChec
11-19 11:22:33.576 1340 1340 E AudioHardwareMSM72XX: AudioHardware::initChec
11-19 11:22:33.606 1340 1354 E AudioHardwareMSM72XX: msm72xx_enable_audpp: 0x0000
11-19 11:22:33.786 1342 1342 I SamplingProfilerIntegration: Profiler is disabled.
11-19 11:22:33.836 1342 1342 I Zygote : Preloading classes...
11-19 11:22:37.326 1342 1342 W ResourceType: Resources don't contain package for resourc
e number 0x010b0001
11-19 11:22:37.326 1342 1342 W dalvikvm: Exception Landroid/content/res/Resources$NotFou
ndException; thrown during Landroid/text/AutoText;.<clinit>
11-19 11:22:37.346 1342 1342 E Zygote : Error preloading android.text.AutoText.
11-19 11:22:37.346 1342 1342 E Zygote : java.lang.ExceptionInInitializerError
11-19 11:22:37.346 1342 1342 E Zygote : at java.lang.Class.classForName(Native Met
hod)
11-19 11:22:37.346 1342 1342 E Zygote : at java.lang.Class.forName(Class.java:237)
11-19 11:22:37.346 1342 1342 E Zygote : at java.lang.Class.forName(Class.java:183)
11-19 11:22:37.346 1342 1342 E Zygote : at com.android.internal.os.ZygoteInit.prel
oadClasses(ZygoteInit.java:295)
11-19 11:22:37.346 1342 1342 E Zygote : at com.android.internal.os.ZygoteInit.main
(ZygoteInit.java:582)
11-19 11:22:37.346 1342 1342 E Zygote : at dalvik.system.NativeStart.main(Native M
ethod)
11-19 11:22:37.346 1342 1342 E Zygote : Caused by: android.content.res.Resources$NotFou
ndException: Resource ID #0x10b0001
11-19 11:22:37.346 1342 1342 E Zygote : at android.content.res.Resources.getValue(
Resources.java:891)
11-19 11:22:37.346 1342 1342 E Zygote : at android.content.res.Resources.loadXmlRe
sourceParser(Resources.java:1865)
11-19 11:22:37.346 1342 1342 E Zygote : at android.content.res.Resources.getXml(Re
sources.java:779)
11-19 11:22:37.346 1342 1342 E Zygote : at android.text.AutoText.init(AutoText.jav
a:160)
11-19 11:22:37.346 1342 1342 E Zygote : at android.text.AutoText.<init>(AutoText.j
ava:76)
11-19 11:22:37.346 1342 1342 E Zygote : at android.text.AutoText.<clinit>(AutoText
.java:56)
11-19 11:22:37.346 1342 1342 E Zygote : ... 6 more
11-19 11:22:37.356 1342 1342 W dalvikvm: threadid=3: thread exiting with uncaught except
ion (group=0x4001e278)
When I reboot I get that second loop over and over while the motorola "m" is on the white screen.
I'm not sure about motorola but on the hero and many other devices, the carrier name is in the eri.xml. I'm with cellular south but I always put my wife's name on her phone.
Did you add the necessary(original) amount of spaces when hex editing that file?
I'm with dean.d though. Mine was in eri.xml too
are you both on CDMA phones? The text fields are T-CDMA. Is this just generic or does it refer to CDMA only? I'm on a GSM network.
From my understanding with 2.1 for the Backflip Motorola set the carrier to always show in the notification bar. Maybe its in the moto-res.apk file...I'll look there.
Immediately following the OTA update to Android Wear 2.0, my LG Urbane started turning itself off (or crashing? dead screen needs long button press to boot) every few minutes. I tried factory resets, and even before pairing with a phone, this still happens. After drawing a dead-end with LG and seller support (the watch is 1.5 years old in the UK, but there is only a 1 year manufacturer warranty, and the seller's policy is 1 year warranty despite EU regs), I ended up unlocking the bootloader and flashing various ROMs (such as [ROM][KERNEL] Ext4All by Skin1980 [M1D64S][Update 10.12.2016]), and formatting cache and userdata. Despite this, I have the same problem in every case... I tried adb logcat, but there are no useful messages, even when the crash happens (often after a screen dim).
Unhelpful logcat:
Code:
01-01 01:36:59.989 569 1037 I PowerManagerService: Nap time (uid 1000)...
01-01 01:36:59.989 569 605 I PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
01-01 01:36:59.990 569 605 I DreamManagerService: Entering dreamland.
01-01 01:36:59.990 569 605 I PowerManagerService: Dozing...
01-01 01:36:59.990 569 594 I DreamController: Starting dream: name=ComponentInfo{com.google.android.wearable.ambient/com.google.android.wearable.ambient.AmbientDream}, isTest=false, canDoze=true, userId=0
01-01 01:36:59.999 569 569 E InputMethodManagerService: Ignoring updateSystemUiLocked due to an invalid token. uid:1000 token:null
01-01 01:36:59.999 569 569 E InputMethodManagerService: Ignoring updateSystemUiLocked due to an invalid token. uid:1000 token:null
01-01 01:37:00.051 999 999 V DreamService[AmbientDream]: onBind() intent = Intent { act=android.service.dreams.DreamService flg=0x800000 cmp=com.google.android.wearable.ambient/.AmbientDream }
01-01 01:37:00.063 999 999 I AmbientService: Ambient Created
01-01 01:37:00.063 999 999 V DreamService[AmbientDream]: Calling onDreamingStarted()
01-01 01:37:00.063 999 999 I AmbientService: Ambient Starting
01-01 01:37:00.065 999 999 D WristGestureCtrl: Stopping detectors: GesturesEnabled-true gestureDetector-true ungazeEnabled-true ungaze-true
01-01 01:37:00.065 999 999 D DefaultUngazeDetector: stopping
01-01 01:37:00.144 569 605 V KeyguardServiceDelegate: onScreenTurnedOff()
01-01 01:37:00.152 569 602 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
01-01 01:37:00.156 186 186 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb8cbbdf0
01-01 01:37:00.168 999 1011 I AmbientService: Current ambient activity gets paused: AmbientActivity[component=ComponentInfo{com.google.android.wearable.app/com.google.android.clockwork.home.HomeActivity}, [email protected], running=false, ambient=true]
01-01 01:37:00.169 999 1011 W AmbientService: we need an ambient activity, but nothing to use
01-01 01:37:00.184 200 2052 D audio_hw_primary: disable_audio_route: reset and update mixer path: audio-record
01-01 01:37:00.192 200 2052 D audio_hw_primary: disable_snd_device: snd_device(63: voice-rec-mic)
01-01 01:37:00.610 186 225 I qdhwcomposer: handle_blank_event: dpy:0 panel power state: 0
01-01 01:37:00.610 569 714 D SurfaceControl: Excessive delay in setPowerMode(): 458ms
01-01 01:37:00.615 569 605 D PowerHAL: IDLE_MODE(touch) -> 1
01-01 01:37:00.626 569 698 E WifiStateMachine: Fail to set up pno, want false now false
01-01 01:37:00.626 200 383 D audio_hw_primary: adev_set_parameters: enter: screen_state=off
The fact that this started after the OTA update points to software issue, but rolling back to earlier versions does not resolve the issue.
Any one have any ideas? Any advice would be welcome.
My son's Moto X with unofficial Lineage OS 13 has been working just fine until today, when it suddenly stopped finding any network operators. The SIM card is still recognized, I may enter the pin, but then it says "No service", and when I go to network operators choice, I find that not a single operator is displayed.
I tested the SIM in another phone, it seems to be fine. I also inserted different sim, which I know to work into this phone, but that did not help.
This is what I get from adb logcat, but I can't make sense of it:
XXXXXXXXXXX simSlotIndex=0 displayName=Willkommen carrierName=No service nameSource=0 iconTint=-16746133 dataRoaming=0 [email protected] mcc 26
2 mnc 7 mUserNwMode=9}]
01-07 18:11:59.254 1572 1572 D NetworkSettings: onSubscriptionsChanged: Slot matched SimSlotIndex: 0
01-07 18:11:59.257 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1572 3902 D OpenGLRenderer: endAllStagingAnimators on 0x99f02e00 (RippleDrawable) with handle 0x9d070520
01-07 18:11:59.361 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.361 1833 1833 D KP2AAF : event: 32, package = com.android.phone
01-07 18:11:59.361 1833 1833 D KP2AAF : event package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : root package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : URL=androidapp://com.android.phone
01-07 18:11:59.368 1833 1833 D KP2AAF : Cancel notif
01-07 18:11:59.438 1881 6159 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.458 1881 1903 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.575 1572 1572 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
01-07 18:11:59.579 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.634 1572 1572 I art : Explicit concurrent mark sweep GC freed 29733(3MB) AllocSpace objects, 7(156KB) LOS objects, 40% free, 10MB/17MB, paused 610u
s total 41.233ms
01-07 18:11:59.656 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.676 1572 1572 I art : Explicit concurrent mark sweep GC freed 13973(846KB) AllocSpace objects, 2(80KB) LOS objects, 39% free, 9MB/15MB, paused 640u
s total 19.563ms
01-07 18:11:59.676 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.691 1881 1901 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.695 1572 1572 I art : Explicit concurrent mark sweep GC freed 3(96B) AllocSpace objects, 0(0B) LOS objects, 40% free, 9MB/15MB, paused 579us total
19.136ms
01-07 18:12:00.121 21030 21030 W ps : type=1400 audit(0.0:1428831): avc: denied { getattr } for path="/proc/1" dev="proc" ino=3578 scontext=u:r:untrusted_app:s0:c5
12,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
01-07 18:12:00.145 1833 1833 D KP2AAF : OnAccEvent
01-07 18:12:00.145 1833 1833 D KP2AAF : event: 2048, package = com.android.systemui
01-07 18:12:00.145 1833 1833 D KP2AAF : return.
Could it be that suddenly the hardware has become faulty? Does anybody have suggestions how to test for the cause?
Thanks very much in advance!!!
Did a factory reset, which did not solve it. Still no network operators found.
Trying to understand the problem. logcat reveals that when it scans for networks, something goes wrong:
IsDataRoamingFromRegistration=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false IsDataRoamingFromRegistration=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1
Can someone enlighten me, what CSS stands for?
Now I spotted more errors:
01-10 15:54:50.960 2132 2132 D DCT : [0]stopNetStatPoll
01-10 15:54:50.964 2132 2132 D DCT : [0]overall state is IDLE
01-10 15:59:14.763 2132 2795 D RILJ : [4000]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB0]
01-10 15:59:14.770 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_req_log: req QMI NAS, msg id: 67, e len:0
01-10 15:59:14.804 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_resp_log: rsp - QMI NAS, msg id: 67, e len:7
01-10 15:59:14.804 2132 2243 D RilRequest: [4000]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
01-10 15:59:14.804 2132 2132 D GsmSST : [GsmSST] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-10 15:59:14.804 2132 2795 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
01-10 15:59:14.805 2132 2795 D GsmSST : [GsmSST] getCellLocation(): X empty mCellLoc and CellInfo mCellLoc=[-1,-1,-1]
01-10 15:59:14.817 1929 3007 D TelephonyManager: getCellLocation returning null because CellLocation is empty
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): return last, back to back calls
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
This "Generic failure" sounds spooky to me. As if something about the hardware is broken.
yahya69 said:
Did a factory reset, which did not solve it. Still no network operators found.
Click to expand...
Click to collapse
Have you tried restoring to the stock firmware? If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
VitaTaf said:
Have you tried restoring to the stock firmware?
Click to expand...
Click to collapse
Yes, but that also did not help, so I returned to LineageOS again.
If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am not clear what that does. Seemingly, it erases two partitions. Is their content rebuilt after? Are those two partitions shipped with the custom rom? I did several google searches and each time I found it accompanied by the instruction to flash something else in the next step. So before nuking a partition I certainly would want to know., but so far I have not found an explanation of the partition layout.
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
Click to expand...
Click to collapse
I know. There it says it has no cellular network. As the logs I posted indicate, something goes badly wrong while searching for cells.
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
yahya69 said:
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
Click to expand...
Click to collapse
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related. Which method did you use to restore to the stock firmware?
VitaTaf said:
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related.
Click to expand...
Click to collapse
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
VitaTaf said:
Which method did you use to restore to the stock firmware?
Click to expand...
Click to collapse
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
yahya69 said:
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
Click to expand...
Click to collapse
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
VitaTaf said:
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
Click to expand...
Click to collapse
I reflashed them but as a result, the sim card is no longer recognized, rebooted several times.
Update: Reflashed lineageOS and now I got my sim card back, although still not connecting to the network. Reflashed the stock firmware with twrp (not sure how this would be done via fastboot), I got my phone to re-connect to the network for a few seconds, which made me jump up and down in excitement, but then the connection dropped again, before I could even make a phonecall
Update 2 Tried a different sim card, but again, when I try to register automatically, this is what I see:
}
D/PHONE (15915): [ServiceState] setDataRegState=1
D/PHONE (15915): [ServiceState] setDataRadioTechnology=0
D/GsmSST (15915): [GsmSST] 0handlPollStateResultMessage: GsmSST setDataRegState=1 regState=0 dataRadioTechnology=0
D/PHONE (15915): [ServiceState] setVoiceRegState=1
E/PHONE (15915): [ServiceState] setState deprecated use setVoiceRegState()
D/GsmSST (15915): [GsmSST] 0handleSIB5LackIssue: no cell location change and config is 'on'
D/GsmSST (15915): [GsmSST] 0Poll ServiceState done: oldSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1 realOldType=Unknown realNewType=Unknown mNewReasonDataDenied=-1
D/PHONE (15915): [ServiceState] setNullState=1
Needless to say it fails.
a simple yes or no would be helpful. At least on my 3 different Moto Z phones its not possible!
Maybe I will answer here myself:
Looks like I am not the only one having that problem with the "formatting sd as internal memory"
https://github.com/omnirom/android_d...thene/issues/3
So why is no one confirming this issue here. I asked for a while....
I think, that it is a very important thing, that is not working and s..o. should already have discovered it right? Its not s. th. like Emojis are not working
here is what the guy posted:
"Formatting micro sd cards fails #3
Open
odomiel opened this issue on Jan 3 · 0 comments
Comments
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant @odomiel @odomiel
odomiel commented on Jan 3
If you try to format a micro sd card as an internal memory, the memory app crashes with the following error message:
attempt to invoke virtual
method 'java.lang.String
android.os.storage.VolumeInfo.getID()' on a
null object reference"
This is exactly the same problem I have......
ischninet said:
Maybe I will answer here myself:
Looks like I am not the only one having that problem with the "formatting sd as internal memory"
https://github.com/omnirom/android_d...thene/issues/3
So why is no one confirming this issue here. I asked for a while....
I think, that it is a very important thing, that is not working and s..o. should already have discovered it right? Its not s. th. like Emojis are not working
here is what the guy posted:
"Formatting micro sd cards fails #3
Open
odomiel opened this issue on Jan 3 · 0 comments
Comments
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant @odomiel @odomiel
odomiel commented on Jan 3
If you try to format a micro sd card as an internal memory, the memory app crashes with the following error message:
attempt to invoke virtual
method 'java.lang.String
android.os.storage.VolumeInfo.getID()' on a
null object reference"
This is exactly the same problem I have......
Click to expand...
Click to collapse
Same problem here. I have the error:
Code:
java.lang.String
android.os.storage.VolumeInfo.getID()
This is on a Moto G4+. I think these are the relevant lines from logcat:
Code:
07-22 08:47:08.039 909 922 I ActivityManager: Displayed com.android.settings/.deviceinfo.StorageWizardInit: +211ms
07-22 08:47:09.358 909 2583 D MotoSensors: ALS 28
07-22 08:47:09.485 534 534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:09.485 534 534 I cnss-daemon: NDA_DST received: 192.168.0.177 ul: 2969610432
07-22 08:47:09.485 534 534 I cnss-daemon: NDA_LLADDR received
07-22 08:47:10.319 909 2958 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:10.511 431 937 D SurfaceFlinger: duplicate layer name: changing com.android.settings/com.android.settings.deviceinfo.StorageWizardInit to com.android.settings/com.android.settings.deviceinfo.StorageWizardInit#1
07-22 08:47:12.398 909 2958 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:12.481 909 3230 I ActivityManager: START u0 {cmp=com.android.settings/.deviceinfo.StorageWizardFormatProgress (has extras)} from uid 1000
07-22 08:47:12.484 909 3230 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:12.534 431 630 W SurfaceFlinger: Attempting to set client state on removed layer: Dim Layer for - Task=649#0
07-22 08:47:12.534 431 630 W SurfaceFlinger: Attempting to destroy on removed layer: Dim Layer for - Task=649#0
07-22 08:47:12.537 7896 7896 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
07-22 08:47:12.538 431 10391 W SurfaceFlinger: Attempting to set client state on removed layer: com.android.settings/com.android.settings.deviceinfo.StorageWizardInit#1
07-22 08:47:12.538 431 10391 W SurfaceFlinger: Attempting to destroy on removed layer: com.android.settings/com.android.settings.deviceinfo.StorageWizardInit#1
07-22 08:47:12.571 355 367 V vold : /system/bin/sgdisk
07-22 08:47:12.571 355 367 V vold : --zap-all
07-22 08:47:12.571 355 367 V vold : /dev/block/vold/disk:179,64
07-22 08:47:12.572 3187 3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:12.572 3187 3187 D StorageNotification: type=PRIVATE diskId=disk:179,64
07-22 08:47:12.572 3187 3187 D StorageNotification: partGuid=E1B03B53-818E-4ECB-A0B4-2A40A42E6829 mountFlags=0 mountUserId=-1
07-22 08:47:12.572 3187 3187 D StorageNotification: state=REMOVED
07-22 08:47:12.572 3187 3187 D StorageNotification: fsType= fsUuid= fsLabel=
07-22 08:47:12.572 3187 3187 D StorageNotification: path=null internalPath=null
07-22 08:47:12.690 909 3499 E QCOM PowerHAL: Failed to acquire lock.
07-22 08:47:13.796 355 367 I sgdisk : GPT data structures destroyed! You may now partition the disk using fdisk or
07-22 08:47:13.797 355 367 I sgdisk : other utilities.
07-22 08:47:13.806 355 367 D vold : Persisted key for GUID 58909d9abe6a4fb98cae092dc0b968b8
07-22 08:47:13.806 355 367 V vold : /system/bin/sgdisk
07-22 08:47:13.806 355 367 V vold : --new=0:0:+16M
07-22 08:47:13.806 355 367 V vold : --typecode=0:19A710A2-B3CA-11E4-B026-10604B889DCF
07-22 08:47:13.806 355 367 V vold : --change-name=0:android_meta
07-22 08:47:13.806 355 367 V vold : --new=0:0:-0
07-22 08:47:13.806 355 367 V vold : --typecode=0:193D1EA4-B3CA-11E4-B075-10604B889DCF
07-22 08:47:13.806 355 367 V vold : --partition-guid=0:58909d9abe6a4fb98cae092dc0b968b8
07-22 08:47:13.807 355 367 V vold : --change-name=0:android_expand
07-22 08:47:13.807 355 367 V vold : /dev/block/vold/disk:179,64
07-22 08:47:13.838 355 367 I sgdisk : Creating new GPT entries.
07-22 08:47:13.845 355 367 I sgdisk : Setting name!
07-22 08:47:13.845 355 367 I sgdisk : partNum is 0
07-22 08:47:13.845 355 367 I sgdisk : REALLY setting name!
07-22 08:47:13.846 355 367 I sgdisk : Setting name!
07-22 08:47:13.846 355 367 I sgdisk : partNum is 1
07-22 08:47:13.846 355 367 I sgdisk : REALLY setting name!
07-22 08:47:14.309 909 2583 D MotoSensors: ALS 33
07-22 08:47:14.715 909 3001 D BatteryService: Processing new values: info={.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 286863, .maxChargingVoltage = 4240240, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 84, .batteryVoltage = 4240, .batteryTemperature = 292, .batteryCurrent = -286, .batteryCycleCount = 0, .batteryFullCharge = 2630000, .batteryChargeCounter = 2531920, .batteryTechnology = Li-ion}, mBatteryLevelCritical=false, mPlugType=2
07-22 08:47:14.716 909 3001 D BatteryService: Sending ACTION_BATTERY_CHANGED. scale:100, info:{.chargerAcOnline = false, .chargerUsbOnline = true, .chargerWirelessOnline = false, .maxChargingCurrent = 286863, .maxChargingVoltage = 4240240, .batteryStatus = CHARGING, .batteryHealth = GOOD, .batteryPresent = true, .batteryLevel = 84, .batteryVoltage = 4240, .batteryTemperature = 292, .batteryCurrent = -286, .batteryCycleCount = 0, .batteryFullCharge = 2630000, .batteryChargeCounter = 2531920, .batteryTechnology = Li-ion}
07-22 08:47:14.716 909 3001 D BatteryService: mLastMaxChargingCurrent = 286863 mLastMaxChargingVoltage = 4240240 maxChargingMicroWatt = 1212640
07-22 08:47:14.721 4174 4252 W QCNEJ : |CORE| CNE received unexpected action: android.intent.action.BATTERY_CHANGED
07-22 08:47:14.915 355 367 I sgdisk : The operation has completed successfully.
07-22 08:47:14.917 355 363 D vold : Disk at 179:64 changed
07-22 08:47:14.919 355 363 V vold : /system/bin/sgdisk
07-22 08:47:14.919 355 363 V vold : --android-dump
07-22 08:47:14.920 355 363 V vold : /dev/block/vold/disk:179,64
07-22 08:47:14.981 355 363 V vold : DISK gpt A3459EC3-4B21-4E26-9EB7-55499980E9D4
07-22 08:47:14.981 355 363 V vold :
07-22 08:47:14.981 355 363 V vold : PART 1 19A710A2-B3CA-11E4-B026-10604B889DCF D86DEB87-8EFB-4DBF-9760-789BA2BFDA29 android_meta
07-22 08:47:14.981 355 363 V vold :
07-22 08:47:14.981 355 363 V vold : PART 2 193D1EA4-B3CA-11E4-B075-10604B889DCF 58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 android_expand
07-22 08:47:14.981 355 363 V vold :
07-22 08:47:14.982 355 363 D vold : Found key for GUID 58909d9abe6a4fb98cae092dc0b968b8
07-22 08:47:14.982 355 363 D vold : Device just partitioned; silently formatting
07-22 08:47:14.983 355 363 E Cryptfs : Cannot remove dm-crypt device
07-22 08:47:14.985 355 363 I Cryptfs : Extra parameters for dm_crypt: (null)
07-22 08:47:14.985 355 363 I Cryptfs : target_type = crypt
07-22 08:47:14.985 355 363 I Cryptfs : real_blk_name = /dev/block/vold/private:179,66, extra_params = (null)
07-22 08:47:16.572 909 2583 E MotoSensors: Proximity covered 1
07-22 08:47:16.877 909 2583 D MotoSensors: ALS 23
07-22 08:47:17.484 534 534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:17.484 534 534 E cnss-daemon: Stale or unreachable neighbors, ndm state: 4
07-22 08:47:19.917 909 5295 W StorageManagerService: Thread Binder:909_E still waiting for partitionPrivate...
07-22 08:47:20.016 355 363 E Cryptfs : Cannot load dm-crypt mapping table.
07-22 08:47:20.016 355 363 E vold : private:179,66 failed to setup cryptfs: Invalid argument
07-22 08:47:20.017 355 363 D vold : Resolved auto to f2fs
07-22 08:47:20.017 355 363 V vold : /system/bin/make_f2fs
07-22 08:47:20.017 355 363 V vold : -f
07-22 08:47:20.018 355 363 V vold : -d1
07-22 08:47:20.018 355 363 V vold : -O
07-22 08:47:20.018 355 363 V vold : verity
07-22 08:47:20.018 355 363 V vold : /dev/block/dm-0
07-22 08:47:20.075 355 363 I make_f2fs:
07-22 08:47:20.076 355 363 I make_f2fs: F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
07-22 08:47:20.076 355 363 I make_f2fs:
07-22 08:47:20.076 355 363 I make_f2fs: Info: Disable heap-based policy
07-22 08:47:20.076 355 363 I make_f2fs: Info: Debug level = 1
07-22 08:47:20.076 355 363 I make_f2fs: Info: Label =
07-22 08:47:20.076 355 363 I make_f2fs: Info: Trim is enabled
07-22 08:47:20.077 355 363 I make_f2fs: Info: No support kernel version!
07-22 08:47:20.077 355 363 I make_f2fs: Info: Segments per section = 1
07-22 08:47:20.078 355 363 I make_f2fs: Info: Sections per zone = 1
07-22 08:47:20.078 355 363 I make_f2fs: Info: sector size = 512
07-22 08:47:20.079 355 363 I make_f2fs: Info: total sectors = 0 (0 MB)
07-22 08:47:20.079 355 363 I make_f2fs: Info: zone aligned segment0 blkaddr: 512
07-22 08:47:20.079 355 363 I make_f2fs: Error: Device size is not sufficient for F2FS volume
07-22 08:47:20.079 355 363 I make_f2fs: Error: Failed to prepare a super block!!!
07-22 08:47:20.079 355 363 I make_f2fs: Error: Could not format the device!!!
07-22 08:47:20.079 355 363 I make_f2fs: make_f2fs terminated by exit(255)
07-22 08:47:20.080 355 363 E vold : private:179,66 failed to format: Invalid argument
07-22 08:47:20.084 355 363 E Cryptfs : Cannot remove dm-crypt device
07-22 08:47:20.086 355 363 I Cryptfs : Extra parameters for dm_crypt: (null)
07-22 08:47:20.087 355 363 I Cryptfs : target_type = crypt
07-22 08:47:20.087 355 363 I Cryptfs : real_blk_name = /dev/block/vold/private:179,66, extra_params = (null)
07-22 08:47:20.645 534 534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:20.645 534 534 E cnss-daemon: Stale or unreachable neighbors, ndm state: 16
07-22 08:47:21.165 534 534 I cnss-daemon: RTM_NEWNEIGH message received: 28
07-22 08:47:21.165 534 534 E cnss-daemon: Stale or unreachable neighbors, ndm state: 16
07-22 08:47:24.918 909 5295 W StorageManagerService: Thread Binder:909_E still waiting for partitionPrivate...
07-22 08:47:25.119 355 363 E Cryptfs : Cannot load dm-crypt mapping table.
07-22 08:47:25.119 355 363 E vold : private:179,66 failed to setup cryptfs: Invalid argument
07-22 08:47:25.124 3187 3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:25.124 3187 3187 D StorageNotification: type=PRIVATE diskId=disk:179,64
07-22 08:47:25.124 3187 3187 D StorageNotification: partGuid=58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 mountFlags=0 mountUserId=-1
07-22 08:47:25.124 3187 3187 D StorageNotification: state=UNMOUNTED
07-22 08:47:25.124 3187 3187 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 08:47:25.124 3187 3187 D StorageNotification: path=null internalPath=null
07-22 08:47:25.124 7896 10833 W StorageSettings: Missing mounted volume of type 1 hosted by disk disk:179,64; trying again
07-22 08:47:25.127 355 362 V vold : /system/bin/blkid
07-22 08:47:25.128 355 362 V vold : -c
07-22 08:47:25.128 355 362 V vold : /dev/null
07-22 08:47:25.128 355 362 V vold : -s
07-22 08:47:25.128 355 362 V vold : TYPE
07-22 08:47:25.128 355 362 V vold : -s
07-22 08:47:25.128 355 362 V vold : UUID
07-22 08:47:25.128 355 362 V vold : -s
07-22 08:47:25.128 355 362 V vold : LABEL
07-22 08:47:25.128 355 362 V vold : /dev/block/dm-0
07-22 08:47:25.130 3187 3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:25.130 3187 3187 D StorageNotification: type=PRIVATE diskId=disk:179,64
07-22 08:47:25.130 3187 3187 D StorageNotification: partGuid=58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 mountFlags=0 mountUserId=-1
07-22 08:47:25.130 3187 3187 D StorageNotification: state=CHECKING
07-22 08:47:25.130 3187 3187 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 08:47:25.130 3187 3187 D StorageNotification: path=null internalPath=null
07-22 08:47:25.172 909 2583 D MotoSensors: ALS 18
07-22 08:47:25.193 355 362 E vold : Failed to pclose /system/bin/blkid -c /dev/null -s TYPE -s UUID -s LABEL /dev/block/dm-0 : No such file or directory
07-22 08:47:25.193 355 362 W vold : blkid failed to identify /dev/block/dm-0
07-22 08:47:25.194 355 362 E vold : private:179,66 failed to read metadata
07-22 08:47:25.196 909 2963 E StorageManagerService:
07-22 08:47:25.196 909 2963 E StorageManagerService: android.os.ServiceSpecificException: (code -5)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.Parcel.createException(Parcel.java:1964)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.Parcel.readException(Parcel.java:1918)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.Parcel.readException(Parcel.java:1868)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.IVold$Stub$Proxy.mount(IVold.java:773)
07-22 08:47:25.196 909 2963 E StorageManagerService: at com.android.server.StorageManagerService$StorageManagerServiceHandler.handleMessage(StorageManagerService.java:622)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.Handler.dispatchMessage(Handler.java:106)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.Looper.loop(Looper.java:193)
07-22 08:47:25.196 909 2963 E StorageManagerService: at android.os.HandlerThread.run(HandlerThread.java:65)
07-22 08:47:25.197 3187 3187 D StorageNotification: Notifying about private volume: VolumeInfo{private:179,66}:
07-22 08:47:25.197 3187 3187 D StorageNotification: type=PRIVATE diskId=disk:179,64
07-22 08:47:25.197 3187 3187 D StorageNotification: partGuid=58909D9A-BE6A-4FB9-8CAE-092DC0B968B8 mountFlags=0 mountUserId=-1
07-22 08:47:25.197 3187 3187 D StorageNotification: state=UNMOUNTABLE
07-22 08:47:25.197 3187 3187 D StorageNotification: fsType= fsUuid= fsLabel=
07-22 08:47:25.197 3187 3187 D StorageNotification: path=null internalPath=null
07-22 08:47:25.233 909 925 I ActivityManager: Start proc 10871:com.android.externalstorage/u0a58 for broadcast com.android.externalstorage/.MountReceiver
07-22 08:47:25.254 10871 10871 E externalstorag: Not starting debugger since process cannot load the jdwp agent.
07-22 08:47:25.331 10871 10871 D ExternalStorage: After updating volumes, found 2 active roots
07-22 08:47:25.348 909 4267 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
07-22 08:47:25.350 909 4267 I ActivityManager: Killing 10254:com.google.android.gms.ui/u0a50 (adj 906): empty #17
07-22 08:47:25.339 10871 10871 I chatty : uid=10058(com.android.externalstorage) identical 1 line
07-22 08:47:25.346 10871 10871 D ExternalStorage: After updating volumes, found 2 active roots
07-22 08:47:25.351 909 926 W libprocessgroup: kill(-10254, 9) failed: No such process
07-22 08:47:25.351 909 923 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
07-22 08:47:25.390 390 390 I Zygote : Process 10254 exited due to signal (9)
07-22 08:47:25.397 909 926 W libprocessgroup: kill(-10254, 9) failed: No such process
07-22 08:47:25.397 909 926 I libprocessgroup: Successfully killed process cgroup uid 10050 pid 10254 in 46ms
07-22 08:47:25.418 7896 10833 W StorageSettings: Missing mounted volume of type 1 hosted by disk disk:179,64; trying again
07-22 08:47:28.709 493 493 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
07-22 08:47:28.292 7896 10833 I chatty : uid=1000(system) com.android.settings identical 10 lines
07-22 08:47:28.585 7896 10833 W StorageSettings: Missing mounted volume of type 1 hosted by disk disk:179,64; trying again
07-22 08:47:28.713 4078 10880 I Authzen : [DeviceStateSyncManager] The server is in sync with current state. Nothing to do
07-22 08:47:28.719 493 493 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
07-22 08:47:28.720 909 925 I ActivityManager: Start proc 10890:com.sonelli.juicessh/u0a151 for broadcast com.sonelli.juicessh/.services.CloudSync$Receiver
Thank you very much! So it is not only a Moto Z issue. All others using their sd card as external storage?
i use my card as external storage, aswell as my microusb flash drives, they are also external storage
It is working now since the the build from 28.07.2019! Problem solved, thank you!
will there be new weekly updates of this great rom?
Hello everyone,
Something happened to my ROG II that caused my mic and speakers to completely stop working.
Had a call in the morning and everything was ok, two hours later another call and other person couldn't hear me.
I've rebooted the phone and after that audio stopped working too. I tried to use headphones but audio jack doesn't recognize them even though they work.
Also I noticed that games that worked before now crash on startup.
I haven't installed anything before the issue occured nor did I interact with the phone in any way between those two phone calls I mentioned.
I'm running Android 11 version 18.0210.2201.215
Also, I'll attach screenshots of errors I got in sound recorder and AudioWizard.
I would really appreciate some ideas or thoughts on what to do because in its current state the phone is pretty much useless.
Edit: Forgot to mention that I've tried to run phone in safe mode and also factory reset but it didn't help.
So I've managed to connect to the phone via adb and checked the logs with logcat. There is a constant spam of following messages:
06-30 14:51:00.115 2863 4748 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
06-30 14:51:00.115 2863 4748 W AudioManager: updateAudioPortCache: listAudioPorts failed
06-30 14:51:00.115 1598 3027 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
06-30 14:51:00.116 1598 3027 W AudioManager: updateAudioPortCache: listAudioPorts failed
06-30 14:51:00.116 2588 3508 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
06-30 14:51:00.116 2588 3508 W AudioManager: updateAudioPortCache: listAudioPorts failed
06-30 14:51:00.116 2985 3894 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
Click to expand...
Click to collapse
Also, since now it takes significantly longer to reboot the phone, I looked at the boot logs and found several that look like they might be related to the issue but I'm not 100% sure:
Spoiler
06-29 21:27:12.983 0 0 E KERNEL : [ 81.323548] init: Control message: Could not find '[email protected]::ISoundTriggerHw/default' for ctl.interface_start from pid: 629 (/system/bin/hwservicemanager)
06-29 21:27:13.983 0 0 E KERNEL : [ 82.323886] init: Control message: Could not find '[email protected]::ISoundTriggerHw/default' for ctl.interface_start from pid: 629 (/system/bin/hwservicemanager)
06-29 21:27:14.986 0 0 E KERNEL : [ 83.324231] init: Control message: Could not find '[email protected]::ISoundTriggerHw/default' for ctl.interface_start from pid: 629 (/system/bin/hwservicemanager)
Click to expand...
Click to collapse
06-29 21:27:43.232 1598 4773 I SoundTriggerService: getModuleProperties()
06-29 21:27:43.233 1598 4773 E SoundTriggerService: SoundTriggerService Crash
06-29 21:27:43.233 1598 4773 E SoundTriggerService: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.hardware.soundtrigger.SoundTrigger$ModuleProperties.toString()' on a null object reference
06-29 21:27:43.233 1598 4773 E SoundTriggerService: at com.android.server.soundtrigger.SoundTriggerService$SoundTriggerServiceStub.getModuleProperties(SoundTriggerService.java:700)
06-29 21:27:43.233 1598 4773 E SoundTriggerService: at com.android.internal.app.ISoundTriggerService$Stub.onTransact(ISoundTriggerService.java:419)
06-29 21:27:43.233 1598 4773 E SoundTriggerService: at com.android.server.soundtrigger.SoundTriggerService$SoundTriggerServiceStub.onTransact(SoundTriggerService.java:251)
06-29 21:27:43.233 1598 4773 E SoundTriggerService: at android.os.Binder.execTransactInternal(Binder.java:1154)
06-29 21:27:43.233 1598 4773 E SoundTriggerService: at android.os.Binder.execTransact(Binder.java:1123)
Click to expand...
Click to collapse
Does anyone have any idea what could be the cause?
Is it software? Hardware? Is there even anything I can do about it?