Hi,
i've a problem with my A2 lite with stock pie rom. I'm using an 32gb SD card (SanDisk ultra). If the phone goes into standby/sleep it unmounts the SD card every time. If i wake up & unlock the phone a short notification is shown and SD card will be mounted again. This happens every time, and in 1 out if 100 cases the mounting fails and SD card is not available. After reboot everything is fine.
How to prevent the unmounting in standby? I've formated the SD within the phone already.
Any ideas?
Hi!
Same issue here, new phone with Android Pie (no idea what happened in Oreo). It's quite annoying as it keeps reindexing the photos in google photos everytime the sd card is re-mounted, draining battery. It's quite annoying. Anyone has an idea on how to fix this?
trash2009 said:
Hi,
i've a problem with my A2 lite with stock pie rom. I'm using an 32gb SD card (SanDisk ultra). If the phone goes into standby/sleep it unmounts the SD card every time. If i wake up & unlock the phone a short notification is shown and SD card will be mounted again. This happens every time, and in 1 out if 100 cases the mounting fails and SD card is not available. After reboot everything is fine.
How to prevent the unmounting in standby? I've formated the SD within the phone already.
Any ideas?
Click to expand...
Click to collapse
Back up your sd card then format it in settings. This problem may occur sometimes if you blacklisted some system apps in adaptive battery. Be creful while you are restricting background apps..
In my case same is happening with two cards, one samsung I was using in my old phone (and was formatted by the A2Lite) and a brand new Sandisk card, also formated by the A2 Lite.
The unmounts seem to be random to me, but having so many pictures it's messing up with google photos all the time (even when if I use internal memory for the camera app, it indexes the sd card with the pictures from my previous phone and merges them with the cloud database) so the problem's still there.
Same issue here, I am using a new Kingston 64gb card formatted with this same phone. Removing apps from battery settings did not help.
I opened this thread last month but did not find any solution
https://forum.xda-developers.com/mi-a2-lite/help/constantly-scanning-sd-card-t3942996
Yes, it looks exactly the same... It's quite annoying to me, as the Google Photos app is working very badly as it keeps reindexing all the time.
I guess it may unmount the sd card in deep sleep to save some battery? I guess that should not be that bad, provided that the apps can keep their indexes instead of going crazy thinking you just added thousands of new elements...
As a workaround, maybe restricting the battery usage while the app is on the background could work for Google Photos, in the sense, preventing it to be actively reindexing?
It is incredibly frustrating. At first I thought it could be caused by an update of Naptime app, so I disabled aggressive doze but to no avail.
I don't think it is because of the sd card. Maybe caused by the June update?
I just had the phone for 5 days and I updated everything at the beginning so no idea. But I agree that's so frustrating.. Was it happening before the June update?
I got this one explicitly for the sd + 2 sims, but if the sd works buggy there's no point.
I tried to restrict the use of the google photos app using the battery in the background as I said, see if that prevents the reindexing (photos app was taking around 5% battery all the time), let's see if it works better now.
Edit: It still reindexes and finds all the pictures even when not allowing background access.
Issue was also there before june update. Changed in the mean time from 32gb sd to a new 64gb sd (formated in the phone) but issue still persits.
Anyone with rooted phone? May its possible to get some details with MatLog (during wakeup & sleep). But I'm not able to do this, cause my phone is not rooted.
trash2009 said:
Anyone with rooted phone? May its possible to get some details with MatLog (during wakeup & sleep). But I'm not able to do this, cause my phone is not rooted.
Click to expand...
Click to collapse
I have root but no SD card inserted.
I found an old one and put it in. Does it need to be adoptable or removable storage?
I have it as a removable one, but I read threads from people having issues as internal one too (I think that in that case it's worse as the phone seems to reboot when it's unmounted).
cancam said:
I have it as a removable one, but I read threads from people having issues as internal one too (I think that in that case it's worse as the phone seems to reboot when it's unmounted).
Click to expand...
Click to collapse
ok. I've got an old 4GB card and I copied my camera pictures onto it. They show up in Google Photos. I can see it scanning in logcat. So far, it hasn't unmounted though. That permanent notification is annoying
hi!
Thanks for the help.
Which permanent notification? I don't have one. I can just see the Sd card icon on the notification tray appear and disappear instantly sometimes when I wake the phone. It doesn't happen always.
But once GPhotos has syncronized and found the images, you'll see that randomly opening google photos will say that he's "getting ready to back up" again, and pictures appear duplicated while it's doing so (I guess it's just rescanning/hashing the pictures to see which ones are already in the cloud).
At least that's what is happening to me when storing the pictures in the sd card and having them set to back up from there.
It wont let me hide this notification. There's an icon and it's on the lock screen too.
In my case I think it appeared after formatting the card and afterwards I discarded it and it never came back (even after reboots). What about the reindexing, does it happen to you?
cancam said:
In my case I think it appeared after formatting the card and afterwards I discarded it and it never came back (even after reboots). What about the reindexing, does it happen to you?
Click to expand...
Click to collapse
Oh wow. Didn't think to just dismiss the notification!
I haven't seen anything odd. Card is not unmounting. I tried a few cards (but all old, class 4).
On my computer I had some notes about the logcat stuff I was doing. I hope to get it written up so that you can maybe get your phone to tell you what it's doing.
Ok, so here's my notes I was making as I looked at the logcat...
You can get logcat by enabling developer mode (not root).
Matlog can work without root (I have root, but deny Matlog root permissions when it asks).
adb logcat from a computer works without root.
These are Linux/MacOS commands. Windows is a little different (no grep). Advanced text editors generally have "find" functionality so you can filter out lines from a file.
First, lets save your logcat to a file. This runs forever (captures the current log and then writes new logs as they happen). After a few seconds, just press Ctrl+C to stop it.
Code:
adb logcat > logcat.txt
This shows various storage events (MOUNTED, EJECTING, UNMOUNTED, REMOVED, CHECKING). The one that signals a hardware issue is BAD_REMOVAL (I only get this if I eject the tray without unmounting first).
Code:
grep StorageNotification: logcat.txt
07-21 09:51:02.510 2199 2199 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-21 09:51:02.510 2199 2199 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-21 09:51:02.510 2199 2199 D StorageNotification: state=BAD_REMOVAL
07-21 09:51:02.510 2199 2199 D StorageNotification: fsType=vfat fsUuid=48C7-13E5 fsLabel=4GB
07-21 09:51:02.510 2199 2199 D StorageNotification: path=/storage/48C7-13E5 internalPath=/mnt/media_rw/48C7-13E5
This shows when Google Photos was started up due to a change in storage. These should line up with StorageNotification events.
Code:
grep ExternalStorageStateChangeBroadcastReceiver logcat.txt
07-21 09:42:50.209 2032 2048 I ActivityManager: Start proc 19428:com.google.android.apps.photos/u0a133 for broadcast com.google.android.apps.photos/.sdcard.envcache.ExternalStorageStateChangeBroadcastReceiver
I use a Magisk module (debloater) to "remove" Google Photos and then installed it from the store (so that it's a USER app, not a SYSTEM app). This allows me to do things like turning on battery restriction (ie. don't run in the background), which is probably why I see things like this:
Code:
grep -i photos logcat.txt
07-21 10:01:50.392 2032 4479 W ActivityManager: No permission grants found for com.google.android.apps.photos
07-21 10:01:58.104 2032 11555 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService (has extras) } to com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService from pid=20276 uid=10133 pkg=com.google.android.apps.photos startFg?=false
It is in theory possible to use adb commands to uninstall Google Photos and then install from the store to get the same effect without root...
I was doing some general searching and it seems that hardware issues commonly cause this. Things like bent pins, loose sockets, etc. You describe the SD card as unmounting when the phone is off, but is it perhaps that the SD card unmounts when the phone is moved around (which happens to be when it is off)?
In any event, the logcat should be able to show if the OS thinks the card is being removed.
Hi!
Many thanks for this.
I have not used ADB in a while so I'll try to find some time to set it up and try it. I guess I'd need logcat running for a while or it just dumps all the logs in a dmesg-like way?
The hardware issue theory is interesting, though in my case it's a brand new phone (Should be less likely and be a manufacturing defect), and I have seen the notification even when flat on table (just double tapping to see if there are notifications, no movement involved). Also I guess that if it was movement dependent we would see the notification also while in use around and this has never happened to me.
I tried to restrict the background access to google photos and it let me, though I didn't see any difference.
Not sure if @trash2009 can add something on this too?
a1291762 said:
Ok, so here's my notes I was making as I looked at the logcat...
You can get logcat by enabling developer mode (not root).
Matlog can work without root (I have root, but deny Matlog root permissions when it asks).
adb logcat from a computer works without root.
These are Linux/MacOS commands. Windows is a little different (no grep). Advanced text editors generally have "find" functionality so you can filter out lines from a file.
First, lets save your logcat to a file. This runs forever (captures the current log and then writes new logs as they happen). After a few seconds, just press Ctrl+C to stop it.
Code:
adb logcat > logcat.txt
This shows various storage events (MOUNTED, EJECTING, UNMOUNTED, REMOVED, CHECKING). The one that signals a hardware issue is BAD_REMOVAL (I only get this if I eject the tray without unmounting first).
Code:
grep StorageNotification: logcat.txt
07-21 09:51:02.510 2199 2199 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-21 09:51:02.510 2199 2199 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-21 09:51:02.510 2199 2199 D StorageNotification: state=BAD_REMOVAL
07-21 09:51:02.510 2199 2199 D StorageNotification: fsType=vfat fsUuid=48C7-13E5 fsLabel=4GB
07-21 09:51:02.510 2199 2199 D StorageNotification: path=/storage/48C7-13E5 internalPath=/mnt/media_rw/48C7-13E5
This shows when Google Photos was started up due to a change in storage. These should line up with StorageNotification events.
Code:
grep ExternalStorageStateChangeBroadcastReceiver logcat.txt
07-21 09:42:50.209 2032 2048 I ActivityManager: Start proc 19428:com.google.android.apps.photos/u0a133 for broadcast com.google.android.apps.photos/.sdcard.envcache.ExternalStorageStateChangeBroadcastReceiver
I use a Magisk module (debloater) to "remove" Google Photos and then installed it from the store (so that it's a USER app, not a SYSTEM app). This allows me to do things like turning on battery restriction (ie. don't run in the background), which is probably why I see things like this:
Code:
grep -i photos logcat.txt
07-21 10:01:50.392 2032 4479 W ActivityManager: No permission grants found for com.google.android.apps.photos
07-21 10:01:58.104 2032 11555 W ActivityManager: Background start not allowed: service Intent { cmp=com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService (has extras) } to com.google.android.apps.photos/com.google.android.libraries.social.mediamonitor.BackgroundThreadNotifierIntentService from pid=20276 uid=10133 pkg=com.google.android.apps.photos startFg?=false
It is in theory possible to use adb commands to uninstall Google Photos and then install from the store to get the same effect without root...
I was doing some general searching and it seems that hardware issues commonly cause this. Things like bent pins, loose sockets, etc. You describe the SD card as unmounting when the phone is off, but is it perhaps that the SD card unmounts when the phone is moved around (which happens to be when it is off)?
In any event, the logcat should be able to show if the OS thinks the card is being removed.
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:20 PM ----------
I tried it and this is what came out from logcat:
Code:
07-22 15:16:54.931 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:54.931 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:54.931 1895 1895 D StorageNotification: state=EJECTING
07-22 15:16:54.931 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:54.931 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:16:56.403 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:56.403 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:56.403 1895 1895 D StorageNotification: state=UNMOUNTED
07-22 15:16:56.403 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:56.403 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:16:56.404 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:56.404 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:56.404 1895 1895 D StorageNotification: state=BAD_REMOVAL
07-22 15:16:56.404 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:56.404 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:21:23.712 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:23.712 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:23.712 1895 1895 D StorageNotification: state=UNMOUNTED
07-22 15:21:23.712 1895 1895 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 15:21:23.712 1895 1895 D StorageNotification: path=null internalPath=null
07-22 15:21:23.713 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:23.713 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:23.713 1895 1895 D StorageNotification: state=CHECKING
07-22 15:21:23.713 1895 1895 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 15:21:23.713 1895 1895 D StorageNotification: path=null internalPath=null
07-22 15:21:24.647 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:24.647 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:24.647 1895 1895 D StorageNotification: state=MOUNTED
07-22 15:21:24.647 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:21:24.647 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
I tried to leave it for a while see if it happened again but it didn't. Will try to get a new log when I see the notification back.
To me it looks like he is actively ejecting the card, unmounting it to then for some reason show the BAD REMOVAL (though he ejected it) and then mounting it normally.
The
Code:
No permission grants found for com.google.android.apps.photos
message is also appearing a lot on the logs.
cancam said:
I have not used ADB in a while so I'll try to find some time to set it up and try it. I guess I'd need logcat running for a while or it just dumps all the logs in a dmesg-like way?
Click to expand...
Click to collapse
I dumps an in-memory buffer. So its like dmesg but it also continues to dump new data that appears. that's why you have to manually stop it.
Because it's an in-memory buffer, it's not going to go back very far in time.
cancam said:
The hardware issue theory is interesting, though in my case it's a brand new phone (Should be less likely and be a manufacturing defect), and I have seen the notification even when flat on table (just double tapping to see if there are notifications, no movement involved). Also I guess that if it was movement dependent we would see the notification also while in use around and this has never happened to me.
Click to expand...
Click to collapse
Your description does seem to rule out an actual hardware issue...
cancam said:
I tried to restrict the background access to google photos and it let me, though I didn't see any difference.
Click to expand...
Click to collapse
I was hoping that if Google photos wasn't able to run, then you'd at least delay the rescan until you manually launched it.
cancam said:
I tried to leave it for a while see if it happened again but it didn't. Will try to get a new log when I see the notification back.
To me it looks like he is actively ejecting the card, unmounting it to then for some reason show the BAD REMOVAL (though he ejected it) and then mounting it normally.
Click to expand...
Click to collapse
Yes... It does look like the system is trying to unmount the card before it fails. There may be hints in the full log as to what is triggering this. I'll see what a regular unmount looks like. If you can send some of the raw logcat before the unmount event... You can DM me if you don't want to post it publicly.
I did think that maybe newer cards need more power and the phone is unmounting to save power. I tried turning on battery saver on my phone but it didn't make any change for me.
Thank You! I sent you the logcat in a private message, but it still looks like the phone tries to eject the card, then it remounts it.
Related
My phone started restarting constantly today in apps. It was always after I clicked a button to do something.
I restored factory defaults and tried to do setup but even during setup random buttons will freeze the UI then reboot the phone.
I followed this guide http://forum.xda-developers.com/showthread.php?t=1626895 and completely reflashed the phone and it still does the same thing. Randomly one of the first couple button presses (like hitting next or sign in on gmail, or opening the gmail browser menu) will freeze the UI and reboot the phone.
What steps should I go forward with to attempt to fix this? Can I somehow get logcat to work from bootloader so I can see what's going on?
Thanks
Record a logcat via from boot until the crashes happen.
063_XOBX said:
Record a logcat via from boot until the crashes happen.
Click to expand...
Click to collapse
[Edit] Thanks, trying to figure out how to get USB debugging working for adb now.
picklefish said:
[Edit] Thanks, trying to figure out how to get USB debugging working for adb now.
Click to expand...
Click to collapse
I can't seem to get adb working on the SETUP front page. Is there some way to enable USB Debugging via a flash or root from recovery so that I can logcat?
EDIT:
My attempt to get USB debugging enabled from recovery.... I still just get a black screen on launch after doing all of this. I'm guessing I'm missing another setting somewhere...
following this http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
Installed clockworkmod recovery
http://wiki.cyanogenmod.org/w/Install_CM_for_toro#Unlocking_the_device
Section: Installing recovery using fastboot
With CWM installed I could then adb in. (I mounted system and data in the recovery menu)
updated build.prop
> adb pull /system/build.prop build.prop
open build.prop in notepad++ and add "persist.service.adb.enable=1" (without quotes)
> adb push build.prop /system/build.prop
then edited adb_enabled to 1 in settings db
> adb pull /data/data/com.android.providers.settings/databases/settings.db
edit
> adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
following this guide if you need help editing settings.db
http://forum.xda-developers.com/showthread.php?t=774507 (i would use this sqlliteadmin though http://sqliteadmin.orbmu2k.de/ but replace the dll following this stack overflow top answer http://stackoverflow.com/questions/9991162/viewing-dumping-encrypt-android-sms-database)
[EDIT 2]
I ended up just installing Cyanogen to see if it crashes on that. I am logcating it since it has USB logging on by default apparently.
[EDIT 3]
So this reboot even happens in cyanogenmod. I managed to get to USB Debugging checkbox, but when the popup showed up it froze and crashed It only happens if i click on buttons in the ui. If i never click anything (just swipe around the desktop) it will never reboot. This is so weird. as long as I don't press any UI buttons it won't reboot. I wish I could get logcat to work.
[EDIT 4]
Here's a logcat right before it crashed. I can attach the whole thing but I am not sure if there are any serial numbers in it or not that I would need to sanitize.
Code:
W/ActivityManager( 313): Permission denied: checkComponentPermission() owningUid=1000
W/BroadcastQueue( 313): Permission Denial: broadcasting Intent { act=android.appwidget.action.APPWIDGET_UPDATE_OPTIONS flg=0x10 cmp=com.android.settings/.widget.SettingsAppWidgetProvider (has extras) } from android (pid=550, uid=10045) is not exported from uid 1000 due to receiver com.android.settings/com.android.settings.widget.SettingsAppWidgetProvider
I/HeadsetService( 776): Headset=false; Bluetooth=false
I/HeadsetService( 776): Selected configuration: speaker
D/EventHub( 313): No input device configuration file found for device 'sec_jack'.
I/EventHub( 313): New device: id=12, fd=230, path='/dev/input/event6', name='sec_jack', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/sec_jack.kl', keyCharacterMap='/system/usr/keychars/sec_jack.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=false
I/InputReader( 313): Device added: id=12, name='sec_jack', sources=0x00000101
V/WiredAccessoryObserver( 313): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=4580, ACTION=change, SWITCH_NAME=h2w, SWITCH_TIME=102717987063}
V/WiredAccessoryObserver( 313): updateState name: h2w state 1
V/WiredAccessoryObserver( 313): updateState switchState: 1
V/WiredAccessoryObserver( 313): newState = 1, headsetState = 1,mHeadsetState = 0
V/WiredAccessoryObserver( 313): device h2w connected
I/HeadsetService( 776): Headset=true; Bluetooth=false
I/HeadsetService( 776): Selected configuration: headset
D/PhoneStatusBar( 401): disable: < expand icons alerts TICKER* system_info back home recent clock >
W/InputMethodManagerService( 313): Window already focused, ignoring focus gain of: [email protected] attribute=null
D/PhoneStatusBar( 401): disable: < expand icons alerts ticker* system_info back home recent clock >
W/ThrottleService( 313): unable to find stats for iface rmnet0
I/ActivityManager( 313): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.mms/.ui.ConversationList bnds=[428,1040][565,1168] u=0} from pid 550
I/EventHub( 313): Removing device sec_jack due to epoll hang-up event.
I/EventHub( 313): Removed device: path=/dev/input/event6 name=sec_jack id=12 fd=230 classes=0x1
D/dalvikvm( 313): GC_FOR_ALLOC freed 946K, 39% free 7497K/12288K, paused 52ms, total 52ms
I/dalvikvm-heap( 313): Grow heap (frag case) to 16.786MB for 380496-byte allocation
I/InputReader( 313): Device removed: id=12, name='sec_jack', sources=0x00000101
I/EventHub( 313): Removing device '/dev/input/event6' due to inotify event
V/WiredAccessoryObserver( 313): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=4835, ACTION=change, SWITCH_NAME=h2w, SWITCH_TIME=106985137942}
V/WiredAccessoryObserver( 313): updateState name: h2w state 0
V/WiredAccessoryObserver( 313): updateState switchState: 0
V/WiredAccessoryObserver( 313): newState = 0, headsetState = 0,mHeadsetState = 1
V/WiredAccessoryObserver( 313): device h2w disconnected
I/HeadsetService( 776): Headset=true; Bluetooth=false
D/libEGL ( 891): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 891): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 891): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 891): Enabling debug mode 0
I/ActivityManager( 313): Displayed com.android.mms/.ui.ConversationList: +452ms
I/HeadsetService( 776): Headset=false; Bluetooth=false
I/HeadsetService( 776): Selected configuration: speaker
I/ActivityManager( 313): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher u=0} from pid 313
D/dalvikvm( 313): GC_CONCURRENT freed 1000K, 39% free 8502K/13763K, paused 3ms+12ms, total 95ms
Is there anything left I can do to track down this problem before I go out and buy a new phone? I have several logs now but nothing in common at the point of the crash. I imagine the error isn't even making it to logcat. The fact that the reboot crash still occurs during cyanogen screams hardware problem. But what on earth kind of hardware problem only happens randomly when you open and close random apps or click on random app buttons?
Is there anything left I can do to track down this problem before giving up and buying a new phone?
Alas, I am giving up and going to buy a new phone. The phone is unusable because it reboots in about 4-5 app clicks. or going back to home screen. Sorry to anyone that comes along with this problem. I HAVE FAILED YOU.
One last question if anyone stops by. Is there anything else that could be corrupt that I can reinstall? I've completely cleared everything i can in CWM and reflashed the entire phone to factory settings. Is there anything I'm missing that could be corrupt that i could re-flash?
I have the same exact issue with my wife's GNex. It was unrooted when it began. I rooted it, installed CWM Touch recovery and Slimbean Rom but the exact same thing happens. Tapping home will crash the UI and reboot. Tapping any app to open will do the same. Has anyone else had this issue? Sorry to revive a dead thread, just trying to avoid buying a new phone.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
mantis92gsr said:
I have the same exact issue with my wife's GNex. It was unrooted when it began. I rooted it, installed CWM Touch recovery and Slimbean Rom but the exact same thing happens. Tapping home will crash the UI and reboot. Tapping any app to open will do the same. Has anyone else had this issue? Sorry to revive a dead thread, just trying to avoid buying a new phone.
Click to expand...
Click to collapse
I also noticed something weird in the logcat
I/EventHub( 394): Removing device sec_jack due to epoll hang-up event.
I/EventHub( 394): Removed device: path=/dev/input/event6 name=sec_jack
What is an epoll hang-up event. Googling this part of my logcat led me to this thread, so I am assuming this error occurs in the OP's original logcat.
Boot problem
Hey guys
Since today I have this problem:
youtube/watch?v=CVQnRhazofk
I can still unlock it and use everything till it reboots.
Infos:
Android Version: 4.4.2
Kernel Version: 3.4.0-gac9222c
[email protected] #1
Wed Nov 20 14:50:44 PST 2013
Build Number: KOT49H
That's all I could find about my device.
I hope someone can help me fix this problem.
sasuke12096 said:
Hey guys
Since today I have this problem:
youtube/watch?v=CVQnRhazofk
I can still unlock it and use everything till it reboots.
Infos:
Android Version: 4.4.2
Kernel Version: 3.4.0-gac9222c
[email protected] #1
Wed Nov 20 14:50:44 PST 2013
Build Number: KOT49H
That's all I could find about my device.
I hope someone can help me fix this problem.
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you rooted? Installed a custom Rom? Kernel? Recovery?
What do you mean by bootloader unlocked? I didn't change anything. So no custom rom , not rooted etc.
I have the same problem, running 4.4.4 (KTU84P)
I'm rooted with Xposed + GravityBox, Xprivacy, and a couple others, but disabling Xposed didn't seem to help at all.
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
elbenny said:
I have the same problem, running 4.4.4 (KTU84P)
I'm rooted with Xposed + GravityBox, Xprivacy, and a couple others, but disabling Xposed didn't seem to help at all.
Click to expand...
Click to collapse
I flashed stock system.img and that didn't help either, so I can't blame root or Xposed.
Some googling found a few references to others with similar problems. One post mentioned quickly unlocking and disabling wifi (+ mobile data if you have it) stops the boot loops, and I was able to reproduce that. Unfortunately, a tablet with no internet access isn't very useful.
I've since tried flashing latest 5.1.1 (LMY48P) which did not boot loop. Maybe I will finally suck it up and move to Lollipop.
turning out the wifi really helped. It stopped to reboot but it's not really useful without internet
elbenny said:
I've since tried flashing latest 5.1.1 (LMY48P) which did not boot loop. Maybe I will finally suck it up and move to Lollipop.
Click to expand...
Click to collapse
Looks like I spoke too soon. 5.1.1 bootloops (earlier, though) if I restore my /data from 4.4.4 nandroid.
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
sasuke12096 said:
turning out the wifi really helped. It stopped to reboot but it's not really useful without internet
Click to expand...
Click to collapse
I agree, no wifi is pretty pointless and hopefully Google will come up with a proper fix.
I'd post the link but I can't yet, anyway you can search "Google product forums" for a thread called "Unable to start up nexus 7"
Maybe you can chime in over there too
This fixed it:
I haven't seen this on a Nexus 4 yet, but I had this happen last night on a Nexus 5 and got it fixed this evening. A call to T-mobile indicated that they haven't run across it yet either, but I found an XDA thread where they were seeing on a Galaxy S4. I'll post some steps for a somewhat tricky fix and then a write-up on what I think is happening based on what I found. Hopefully this will help.
1) Power off phone. Hold power button down until you see the Google logo come up and then disappear. That should stop the "boot loop" and keep the phone powered off. If it comes back on, try again and just hold the power button down a little longer than you thought you needed to.
2a) Steps 2-5 below can probably be replaced by putting the phone into airplane mode quickly while it's temporarily alive during the boot loop. If you put it into airplane mode and the boot loop stops, skip to step 6 and just disable airplane mode for steps 9/10.
2) Eject SIM card. You should have the little tool (round with a short, narrow point) that presses into a tiny hold on the side of the phone to eject the sim card. If you are uncertain on this step, get some help.
3) Power on phone. If you were connected to Wi-Fi when this started, it will still boot loop so we need to disable Wi-Fi as well. This is the tricky part. You may find it easy if you power off your wireless router before trying to turn off Wi-Fi on your phone.
4) Disable Wi-Fi as quickly as possible by swiping lock screen, pulling down the settings "drawer" at the top of the phone, clicking on wi-fi and click it off.
5) The phone should no longer reboot, but will start to reboot again if you give it a network connection (wi-fi or mobile) so don't reconnect it to the network until you are done with the next couple steps.
6) Go to Settings -> Apps and scroll over to ALL.
7) Scroll down to Google Services Framework and click it
8) Click on CLEAR DATA and hit Ok. I also hit CLEAR CACHE and while I'm not sure it's necessary, I recommend doing that as well.
9) Power off phone, re-install SIM card and power on phone.
10) Assuming you don't immediately go into a boot loop again, it's probably fixed. Re-enable wi-fi and go back to enjoying life
The trickiest part here is being fast enough to disable wi-fi before the reboot happens. It may be a non-issue if turning off the wireless router helps.
As a caveat, we haven't been running the phone for very long after clearing that data, but it's acting a little sluggish at times. I'm going to let it run for a day or two and then maybe do a full factory reset if it doesn't clear up. At the very least, the boot loop is gone.
------------------------------------------------
Now for the nerdy stuff in the hopes someone from the major providers and/or Google is watching this...
Late last night, I hooked up ADB to the phone after getting Wi-Fi disabled and USB Debugging enabled. A logcat dumped out a huge amount of data, but thankfully caught the reboot when I re-enabled Wi-Fi. Here's a partial dump from the log:
I/iu.SyncManager( 1201): NEXT; no task
I/CheckinRequestBuilder( 1201): Checkin reason type: 12 attempt count: 1
D/dalvikvm( 1087): GC_CONCURRENT freed 417K, 4% free 18384K/19056K, paused 2ms+2ms, total 19ms
W/dalvikvm( 744): threadid=13: thread exiting with uncaught exception (group=0x41564ba8)
E/AndroidRuntime( 744): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.bg
E/AndroidRuntime( 744): java.lang.NullPointerException
E/AndroidRuntime( 744): at android.content.PeriodicSync.syncExtrasEquals(PeriodicSync.java:150)
E/AndroidRuntime( 744): at android.content.PeriodicSync.equals(PeriodicSync.java:129)
E/AndroidRuntime( 744): at com.android.server.content.SyncStorageEngine.setPeriodicSyncTime(SyncStorageEngine.java:1625)
E/AndroidRuntime( 744): at com.android.server.content.SyncManager$SyncHandler.scheduleReadyPeriodicSyncs(SyncManager.java:2097)
E/AndroidRuntime( 744): at com.android.server.content.SyncManager$SyncHandler.handleMessage(SyncManager.java:1881)
E/AndroidRuntime( 744): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 744): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 744): at android.os.HandlerThread.run(HandlerThread.java:61)
I/Process ( 744): Sending signal. PID: 744 SIG: 9
I/ServiceManager( 176): service 'package' died
I/ServiceManager( 176): service 'batterystats' died
I/ServiceManager( 176): service 'usagestats' died
W/Sensors ( 1876): sensorservice died [0x7645fde0]
D/AndroidRuntime( 1087): Shutting down VM
many more services dieing
Note the null pointer exception in android.bg on a "PeriodSync" I don't know what that's supposed to do, but it clearly can only trigger with a valid network connection and it is very displeased with life. A search for some key words from the traceback led me to XDA (http://forum.xda-developers.com/showpost.php?p=62943303&postcount=2119). The symptoms matched what I was seeing and they mention going into Airplane mode to stop the boot loop which may be an even better approach than my somewhat heavy handed solution above. Speculation in that thread indicates a google apps update of some sort which I assume probably came through on my wife's phone last night with automatic updates.
I've run into an issue where my phone is now accepting anything on the fingerprint scanner as a valid fingerprint, and I'm unable to add new prints, or clear existing ones for some reason. I'm going to try to just delete the fingerprint data before I do a factory reset, but I don't know where it is actually kept on the phone, if anyone has any idea, it'd be appreciated.
Update: I ran logcat *:E and got this when trying to remove fingerprints
07-30 20:30:21.342 960 960 E fpc_tac : fpc_tac_send_get_uint32_cmd failed with retval: -3
07-30 20:30:21.342 960 960 E fpc_fingerprint_hal: int fpc_remove(fingerprint_device*, uint32_t, uint32_t) failed -5, reloading db
07-30 20:30:21.358 960 960 E fpc_fingerprint_hal: int fpc_remove(fingerprint_device*, uint32_t, uint32_t): fpc_tac_load_user_db failed with error -4
BroseidonMOO said:
I've run into an issue where my phone is now accepting anything on the fingerprint scanner as a valid fingerprint, and I'm unable to add new prints, or clear existing ones for some reason. I'm going to try to just delete the fingerprint data before I do a factory reset, but I don't know where it is actually kept on the phone, if anyone has any idea, it'd be appreciated.
Update: I ran logcat *:E and got this when trying to remove fingerprints
07-30 20:30:21.342 960 960 E fpc_tac : fpc_tac_send_get_uint32_cmd failed with retval: -3
07-30 20:30:21.342 960 960 E fpc_fingerprint_hal: int fpc_remove(fingerprint_device*, uint32_t, uint32_t) failed -5, reloading db
07-30 20:30:21.358 960 960 E fpc_fingerprint_hal: int fpc_remove(fingerprint_device*, uint32_t, uint32_t): fpc_tac_load_user_db failed with error -4
Click to expand...
Click to collapse
did you do a restore from a previous backup which had fp security enabled?
you could delete them from recovery... not tried while your phone is booted up...
/data/system and delete all the locksettings.* files (such as locksettings.db, etc)
I'm sure you already tried this but I only had my phone for a week and it wasn't accepting any fingerprint. Came to the conclusion I had dirty thumbs. My son and I were playing Xbox one for awhile and it muddied up my thumbs and scanner. I tried deleting and adding new prints with still no light at the end of the tunnel. I ended up just washing my hands and it was like new
SacredDeviL666 said:
did you do a restore from a previous backup which had fp security enabled?
you could delete them from recovery... not tried while your phone is booted up...
/data/system and delete all the locksettings.* files (such as locksettings.db, etc)
Click to expand...
Click to collapse
The phone is accepting any contact at all as a valid fingerprint and unlocking, so I have access to the phone just fine, but I can't seem to clear the fingerprints stored on the device or add new ones, the very moment the dialog for scanning your finger opens, it says that it failed and to try again, before even touching it.
BroseidonMOO said:
The phone is accepting any contact at all as a valid fingerprint and unlocking, so I have access to the phone just fine, but I can't seem to clear the fingerprints stored on the device or add new ones, the very moment the dialog for scanning your finger opens, it says that it failed and to try again, before even touching it.
Click to expand...
Click to collapse
tried deleting the above files i mentioned?
Hi
Company's wifi requires client certificate and TLS auth type to connect. On MIUI 8 and my old Galaxy Note 2 (both rooted) it all worked fine til I decided to unlock bootloader and install Resurrection Remix. Device is Mi Max Hydrogen 3Gb / 32Gb
Currently when I try to connect I see following in logcat of my phone (took screenshot so text has OCR errors)
16:52:34.896 2696 2696 I wpa_supplicant wlan0: Associated with 0c:68:03:ae:2a:b1
1652: 34.896 2696 2696 I wpa_supplicant: wlan0: CTRL-EVENTSUBNET-STATUS-UPDATE status 0
16:52:34,896 2696.2696 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
16:52:34.902 1006 2695 I Wifi HAL : Unknown EAPOL message type
16:52:34.902 2696 2696 I wpa_supplicant: wlan0: CTRL-EWENT-EAP-PROPOSED-METHOD vendor=0 method=13
16:52:34.907 2696 2696 I wpa_supplicant: tls_connection_set params: Clearing pending, SSL error: error 0с000067:ASN.1 encoding routines: OPENSSL internal: BAD_OBJECT_HEADER
16:52:34.907 2696 2696 I wpa_supplicant: tls_сonnection_set_params: Clearing pending SSL error: error 0с00009c:ASN.1 encoding routines: OPENSSL internal: NESTED_ASN1_ERROR
16:52:34.920 412 412 E keymaster1_device: Len returned is < 0 len = 0
16:52:34.921 412 412 W export failed: -22
16:52:34.921 2696 2696 W cannot convert pubkey
16:52:34.921. 2696 2696 E wpa_supplicant: ENGINE: cannot load private key with id "USRPKEY_pdas" ASN.1 encoding routines OPENSSL internal:HEADER_TOO_LONG
16:52: 34.921. 2696 2696 I wpa_supplicant: TLS: Failed to initialize engine
Certificates are the same and get installed without any error, after installation files appear in /data/misc/keystore. Tried many attempts, different auth types, copying cert files manually, and so on and so on - this all didn't helped. Is there any workaround or where to look to resolve?
Our helpdesk said hey even can't see any auth attempt on their RADIUS server. This looks reasonable, in log it seems that process fails early, when openssl just tries to read key. Current keystore type is hardware-backed, maybe it fails because phone is unlocked? Is there any method to make it software-only?
I have the same problem (on several devices) . It seems this occurs on most (if not all) 7.1.x based ROMS (not only CM/Lineage based).
Reported that same network ok on LG G3 with RR 5.8.0. I guess it is some issue with hardware keystore. Thus device dependent. And I found no kernel tweak to store certs on file system
Finally I fixed it. Just created new WIFI connection using wpa_cli in command line (adb shell). Certificates could be placed anywhere in the system, and path to certificate files must be set in wpa_supplicant params using wpa_cli. Need to set read permission to these files (chmod) for all users, otherwise wpa_supplicant will not be able to read them. It is great that we have Linux under the green suite of our robot
DimaRUS said:
Finally I fixed it. Just created new WIFI connection using wpa_cli in command line (adb shell). Certificates could be placed anywhere in the system, and path to certificate files must be set in wpa_supplicant params using wpa_cli. Need to set read permission to these files (chmod) for all users, otherwise wpa_supplicant will not be able to read them. It is great that we have Linux under the green suite of our robot
Click to expand...
Click to collapse
May you please share detailed wpa_cli commands? I am facing the exact same problem (i think) with my OP2. As I am not into wpa_cli commands your help would be much appreciated.
DirtyHarrx said:
May you please share detailed wpa_cli commands? I am facing the exact same problem (i think) with my OP2. As I am not into wpa_cli commands your help would be much appreciated.
Click to expand...
Click to collapse
First use add_network command. It will create a new blank network. You can spot it's ID by typing list_networks.
Then use set_network <ID> <param> <value> commands to configure it. I used an example from FreeBSD man page on wpa_supplicant config.
https://www.freebsd.org/cgi/man.cgi...opos=0&manpath=FreeBSD+11.0-RELEASE+and+Ports
network={
ssid="work"
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TLS
identity="[email protected]"
ca_cert="/etc/cert/ca.pem"
client_cert="/etc/cert/user.pem"
private_key="/etc/cert/user.prv"
private_key_passwd="password"
}
It is well documented and params for set_network are the same as in config file. For keys I used only private_key= param and specified .p12 container and it's password. Finally use save_config.
Don't know why but after a few reboots network disappeared. Need to configure again.
Hello all;
Recently developed an issue with my S9. It won't connect to the computer over USB!
Unrooted, stock Galaxy S9 Firmware (Pi) with May 2019 security Update installed
Tried 4 USB cables (Original, Aukey USB 3.1, brand new USB 2.0, and brand new USB 3.0)
Tried on two different computers and on Android Auto (2017 VW GTI)
Charges perfectly fine from any computer or charger with any cable
Occasionally connects perfectly fine and will stay connected until I unplug it on either Android Auto or PC, regardless of how I move the device around
When it's wanting to connect, I can also unplug it at the phone end and plug it back in and it works fine.
No apparent correlation with 'how' I plug it in or hold the cable or temperature of the room I'm testing it in.
Connects more often to Windows 10 PC than to Android Auto
Occasionally, switching USB port on computer will make it work without replacing the plug on the phone end
On computer, will often 'Beep-beep' to indicate it connected, but doesn't show up in device manager and ADB won't detect it
When not connected, doesn't show up in ADB or Device manager
When it almost-connects on the computer, it will pop up the 'USB settings' notification and permissions dialogue, but then that disappears
Tried a full reset FROM the Settings menu.
Tried clearing cache
Carefully cleaned the USB C port on the phone with canned air and a soft plastic toothpick- didn't seem very dirty
Looking at Logcat files, I see that it starts to connect and then fail out
Other android phones and iphone work fine on Android Auto and on both computers
Any ideas? Is this most likely a hardware issue? (What Samsung support thinks)
Or is there a deeper hard reset/restore I can do? I tried a factory reset from the recovery menu but that failed saying that it had to be done from inside the OS. (New Pie security feature?)
Here's what I believe to be the relevant logcat file from connection to failure.
Code:
06-05 20:51:08.329 I/[email protected]( 725): partner added
06-05 20:51:08.331 I/[email protected]( 725): uevent received DEVTYPE=typec_partner
06-05 20:51:08.332 I/[email protected]( 725): port0
06-05 20:51:08.335 I/[email protected]( 725): connected:1 canChangeMode:1 canChagedata:0 canChangePower:0
06-05 20:51:08.335 I/UsbPortManager( 1477): ClientCallback: port0
06-05 20:51:08.343 D/UsbPortManager( 1477): addOrUpdatePortLocked()++ : portId=port0, supportedModes=dual, currentMode=ufp, canChangeMode=true, currentPowerRole=sink, canChangePowerRole=false, currentDataRole=device, canChangeDataRole=false
06-05 20:51:08.343 D/UsbPortManager( 1477): addOrUpdatePortLocked() supportedRoleCombinations=272
06-05 20:51:08.344 D/UsbPortManager( 1477): addOrUpdatePortLocked() supportedModes=dual
06-05 20:51:08.344 D/UsbPortManager( 1477): addOrUpdatePortLocked() mPorts DISPOSITION_REMOVED -> DISPOSITION_CHANGED
06-05 20:51:08.344 D/UsbPortManager( 1477): addOrUpdatePortLocked()--
06-05 20:51:08.344 D/UsbPortManager( 1477): mPorts size: 1
06-05 20:51:08.344 I/UsbPortManager( 1477): USB port changed: port=UsbPort{id=port0, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
06-05 20:51:08.345 D/UsbPortManager( 1477): mPorts(0) DISPOSITION_CHANGED -> DISPOSITION_READY
06-05 20:51:08.345 D/UsbPortManager( 1477): updatePortsLocked()--
06-05 20:51:08.348 D/UsbDeviceManager( 1477): received ACTION_USB_PORT_CHANGED
06-05 20:51:08.348 I/UsbDeviceManager( 1477): updateHostState UsbPort{id=port0, supportedModes=dual} status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}
06-05 20:51:08.358 E/BartenderActivityManager( 1477): BarTender: pid : 20445 cached=true abnormal=false kill=false stay=false release=false
06-05 20:51:08.361 E/BartenderActivityManager( 1477): BarTender: pid : 18831 cached=true abnormal=false kill=false stay=false release=false
06-05 20:51:08.362 E/BartenderActivityManager( 1477): BarTender: pid : 20756 cached=true abnormal=false kill=false stay=false release=false
06-05 20:51:08.404 V/UsbDeviceManager( 1477): USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=6847, ACTION=change, USB_STATE=CONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
06-05 20:51:08.405 I/UsbDeviceManager( 1477): updateState CONNECTED
06-05 20:51:08.405 D/UsbDeviceManager( 1477): handleMessage -> MSG_UPDATE_STATE connected = 1,configured = 0 mCurrentFunctions mtp
06-05 20:51:08.405 D/UsbDeviceManager( 1477): updateUsbNotification(false) : mConnected = true, mConfigured = false, mCurrentFunctions = 4, mHostConnected = false, mSourcePower = false
06-05 20:51:08.406 D/UsbDeviceManager( 1477): id=27, mUsbNotificationId=0, titleRes=17042083
06-05 20:51:08.411 D/ApplicationPolicy( 1477): isStatusBarNotificationAllowedAsUser: packageName = android,userId = -1
06-05 20:51:08.411 D/API test( 1477): getContainerInfo: value is
06-05 20:51:08.411 D/ApplicationPolicy( 1477): isStatusBarNotificationAllowedAsUser: packageName = android,userId = 0
06-05 20:51:08.412 D/API test( 1477): getContainerInfo: value is
06-05 20:51:08.415 D/UsbDeviceManager( 1477): updateUsbNotification : notify id = 27, title = USB for file transfer
06-05 20:51:08.415 D/UsbDeviceManager( 1477): updateUsbStateBroadcastIfNeeded functions 5
06-05 20:51:08.415 D/UsbDeviceManager( 1477): updateUsbStateBroadcastIfNeeded remainingFunctions 5
06-05 20:51:08.416 D/UsbDeviceManager( 1477): broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=true, config_changed=false, adb=true, mtp=true, configured=false}]
06-05 20:51:08.421 V/UsbDeviceManager( 1477): USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=6848, ACTION=change, USB_STATE=DISCONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
06-05 20:51:08.421 I/UsbDeviceManager( 1477): updateState DISCONNECTED
06-05 20:51:08.429 D/MTPRx (22081): In MtpReceiverandroid.hardware.usb.action.USB_STATE
06-05 20:51:08.430 D/UsbDeviceManager( 1477): sending intent : ACTION_USB_STATE : connected = true, configured = false, mCurrentFunctions = 4, mHostConnected = false, configChanged = false
I am having the same issue. My S9 SM-G960W with latest ROM stopped connecting to my PC. I also noticed that none of my OTG USB drives / cables that I have work anymore. I checked all my PC USB ports and OTG USB drives with my old S6 and my wife's S9 phone and they all connect right away and they recognize the drives with no problems. Cleared the cache. Tried different USB settings on the phone and lots of different cables. The phone just says charging no connection for file transfer. It used to work awhile back because I used the PC to transfer old phone to it and I backed it up a few times. Found the problem when I was going to do my regular backup...
i have a type c otg cable in my car and a usb on my keychain, ill have to grab the otg and give it a whirl. ill post up my results if i can remember to do this
If you dial *#0808# on the dial pad what do you get? Can you change these setting and does it stick? Does your phone recognize if you insert any USB memory stick?
Did you solve your problem yet?
this goes to show what kind of awesome memory i have, but the OTG cable was a go. I was able to read all my files and modify them. Are you still having the same issue?
Not solved. Cannot connect anything to USB and get it to work. Other than charge.
MECH_TECH said:
Not solved. Cannot connect anything to USB and get it to work. Other than charge.
Click to expand...
Click to collapse
have you enabled developer options?
Yes developer options is enabled. USB debugging is on. Default USB is set to file transfer. If I plug in my USB memory stick I get a notification that "USB device connected" then message "charging connected device via USB" and if I tap the notification I see that "USB is controlled by connected device" and cannot change that -it says failed to change.
MECH_TECH said:
Yes developer options is enabled. USB debugging is on. Default USB is set to file transfer. If I plug in my USB memory stick I get a notification that "USB device connected" then message "charging connected device via USB" and if I tap the notification I see that "USB is controlled by connected device" and cannot change that -it says failed to change.
Click to expand...
Click to collapse
might be time to nuke the OS and reflash via Odin. All the time and frustration trying to figure it out might not be worth the time itll take to set your phone back up again
When you say nuke the OS do you mean just flashing the ROM using ODIN to nuke the OS or factory reset then instill ROM with ODIN? Installing ROM with ODIN will not clear the user DATA or SD card contents correct? I have tried booting into recovery and clearing the cache, but that did not do anything.
I don't want to start new thread but similar problem , I can't connect S9 to PC. Did not have any problems until last month. Meanwhile I have done all including changing USB ports and yes I can connect my wife's S9 to PC. Still no luck. Any help will be very much appreciated