Related
I have been talking this over with Condemned Soul but wanted to see if anyone else has ran into this problem since he & I are both confused.
My fiances phone has been force closing a lot lately aka com.android phone not responding. I saw the first force close when I tried flashing Tazzs cm7 on his phone so thats when I first put on gsb 1.2
I switched his over to Sheds GSB on the 8th and it was great everything was fine but then I decided to try to improve on a few settings and when I restarted the phone it decided to start force closing.
I reflashed the rom and the gapps and everything seemed fine but then I wanted to put cs skull theme on his phpne since we had it on Kaos v9 but then when I restarted the phone after flashing the theme it force closed again.
So then I reflashed the rom and gapps again and got all his apps and settings all back how he had it and decided to do a Nandbackup so that we wouldnt have to keep reflashing the rom again and once I restarted the phone after the nandbackup it force closed again.
Long story short I reflashed the rom and gapps and now am in the process of getting his apps and settings back how he had it once again.
Am I doing something wrong to make it keep force closing? I would like to make a nandbackup at least for him so that we wont have to keep setting up his phone.
Thank you for any help
When you say you flash the ROMs, do you also do a wipe beforehand? If not, try doing a wipe and then install and see if that changes anything.
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
labnjab said:
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
Click to expand...
Click to collapse
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
zerocool79346 said:
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
Click to expand...
Click to collapse
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
CondemnedSoul said:
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
Click to expand...
Click to collapse
That is odd.
Update:
This is still causing issues. Going to try and format the sd like tazz suggested, but moving my phone.apk to his didnt work, and yesterday he had to restart his phone and it did it again and needlessto say hes not very happy with his phone. Says its not reliable at all. If anyone else has anything else I can try it would be a big help. I have tried searching on google but dont find a whole lot of information. I just wish I could figure this out its got to be something I did or something stupid that I am missing.
There are a couple of next steps you can take.
If the problem is a software configuration issue, then it is possible that you will see the reason for the FC in the logcat.
The system logcat is designed as a "circular buffer" (in a way that it has a maximum size) - once you fill it to capacity, each new record which is added to the end causes information at the beginning to be lost. But, this also means that if a FC occurs, so long as you "dump the logcat" within a reasonable period of time after the FC happens, you will capture the moment in time that the FC occurred,
Generally, the "logcat" buffers get filled to capacity quite quickly at boot time (because there is lots and lots of "android" app activity), and quite a bit slower after the phone has been completely booted. If you are trying to capture a logcat event during the first boot, you need to continuously capture output to a file on your PC (it will be quite large) - but once the phone has completed booting, so long as you "run a logcat" within 5 or 10 minutes after a FC occurs, the relevant event(s) will be in the logcat.
If you want to capture it during the first boot cycle of a freshly flashed ROM, probably you ought to have a PC attached and dump the prodigious output to a file on the PC, as in
Code:
C:\MyWindozePC> adb shell logcat -v time > LogcatFileOnMyPC.txt
So long as the ROM you have flashed has "USB debugging" turned on by default, you can run the above command about 10-15 seconds after you see the 3 skating droids, and it will continuously place output into the local file on your PC. You need to interrupt the above command (Control-C) to get it to stop; you would usually do that a few seconds after you saw the FC, and then you would know that the log entries you are looking for at the end of the file.
(Note that logcat dumps are usually huge - don't bother trying to look at them with a text file viewer on the phone - they suck at handling large files... well, at least the ones that I have tried).
You could also instrument this on the BF's phone in a way where he can capture the info to the SD card anytime he is using the phone during the day with a couple taps of the screen, and then you could look at the logcat(s) later at your leisure - for instance by using Gscript Lite, and a simple script like this:
Code:
#! /system/bin/sh
_LOGDIR='/sdcard/logcats'
if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi
_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt
With this method, you just need to train him like a monkey to press the right keys after a FC occurs. If he's a clever monkey, you could even train him to send the logcat files to you via e-mail.
If the problem is due to an intermittent hardware issue with the phone, that will be tougher to identify. About the best you can do to make that determination is to return the phone software to stock and use the phone without installing any apps for a reasonable period of time and see if the problem continues to occur.
cheers
bftb0
Thank you for the detailed reply bfbt0 I was about to msg you when you responded.
I will have to give what you mentioned a try.
Is the gscript lite what I use for the adb shells or do I need another app as well. I have never done anything with adb or if I have it was something simple.
To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.
Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
labnjab said:
Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
Click to expand...
Click to collapse
GScript Lite is a free app on the market. It was put together by XDA member "rogro", and he has a paid version as well if you want to throw a couple bucks his way.
Using the script above with Gscript (Lite or Pro), you don't need to be tethered to a computer nor set up the SDK and drivers. (Only when you want to capture a full first ROM boot do you need to use a PC (because the logfile grows so big in that specific case).
If you can force the FC to occur, then using the Gscript Lite script I showed above will capture the information you want.
bftb0
PS There is a brief outline of how you load a script into Gscript Lite in that "Universal Root for Dummies" thread over on AF.
cheers
Thank you I will try that tonight and hopefully can figure out what the issue is
labnjab said:
To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.
Click to expand...
Click to collapse
That code I posted checks to see if a folder exists, and if not creates it - /sdcard/logcats
No need for you to do it manually; the first time the script runs it creates that folder
But, yeah - wait for the FC to happen and then run that script within the next couple of minutes (no real hurry). It is also useful to make note of the time the phone displays when the FC occurs - it will be easier to find things in the logcat file by timestamp if you do that.
bftb0
Thank you I will do that as well. Thanks also for taking the time to help me.
I did the code on my phone to make sure I did it right and it gave me an error
says cannot create/logcat_20110222-1558.txt read only file system
did I do something wrong, just want to make sure that I can get it right before attempting it on his phone tonight. Thanks in advance.
labnjab said:
I did the code on my phone to make sure I did it right and it gave me an error
says cannot create/logcat_20110222-1558.txt read only file system
did I do something wrong, just want to make sure that I can get it right before attempting it on his phone tonight. Thanks in advance.
Click to expand...
Click to collapse
If you typed that script in by hand, you made a typo.
I checked it by cutting and pasting it - and then I tested it afterward, and it worked.
Probably you bolluxed up the _LOGDIR variable, or you inserted a space in the logcat command where there should not be one.
I would suggest that you cut and paste, rather than type.
Hmmmm... it occurs to me that those little "scrolling CODE text boxes" don't render correctly on the phones browser. Here's the same script, but without enclosing it in [ CODE ] [ /CODE ] tags:
#! /system/bin/sh
_LOGDIR='/sdcard/logcats'
if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi
_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt
Thank you for all your help. I got it to work and come to find out I didnt even need to use that program because it hasnt forced closed yet. He said he wiped the phone a bunch of times the other day when he was trying to get it back up and running when it forced closed on him while at work and now i rebooted it and backed it up and that usually caused a problem, so far so good.
I am tho going to format the sd card and redo the rom again just to be sure this problem doesnt happen again. Thank you again for all the help.
On some builds (even though it shouldn't be required) it is necessary to wipe multiple times. On Tazz's earlier builds of GB, people reported having to wipe 3x or more to get it running smooth. Always make sure you do a nand backup before flashing in the future lol. Hopefully the phone stays running good! If not, people are always here to help!
Sent from my Ginger Tazz using XDA App
First, props to TeamWin, joel.bourquard, theintelligent, and maybe a few others I'm not aware of...
Second, these are Windows instructions. If you have another OS, you can open the batch files and type the commands inside (or paste them) one by one.
Third, keep in mind that the current temp root is NOT a full root even WHEN it is in place... so don't expect too much! This method has also been modified (by others) so that it does not "randomly" reset and it sticks until the next restart. As a result of how that works, however, even fewer apps recognize root with this method but some do!
Most of this is just other people's work: stuff from several different posts repackaged in a way that I found very easy to use. So I don't take credit for most of the contents, although I did modify the batch files to take care of a timing issue that was causing a fail on most machines. In the end, you should be able to use the attached prepare.bat file to prepare your phone once and then you can use root.bat after each reboot to restore temp root. Create a shortcut to root.bat on your desktop and you can just plug your phone in, click the icon, and you're (re)rooted in about 8 seconds.
The instructions are simple but I elaborate below to try to hit all the stumbling blocks. Basically you just run prepare.bat the first time you do this and from that point forward, you only need to run root.bat after every restart.
Here are the specific instructions:
THE FIRST TIME ONLY:
(1) Unzip contents of the attached ZIP to a folder you'll remember on your hard drive.
(2) Plug your phone in via USB and set it to "charge only" with "USB debugging" under "Settings", "Applications", "Development" turned on. It's best to do this after a fresh (full, not fast) boot. Your phone should be in this mode each time you connect it to root it. Trust me, if you've been using your phone for a while, reboot it first, then wait a few minutes for it to stabilize, THEN do this routine... saves a lot of headaches.
(3) Go to the folder where you unzipped the files in (1) and run prepare.bat. I prefer to do it in a DOS box but you should be able to just use Explorer and double click on the prepare.bat file.
(4) The first thing these batch files do is a check to make sure your computer can see the phone. If your phone isn't in the list, Ctrl-C and break out of the batch file. You'll have to correct the problem which will most likely be an issue with the HTC drivers. If your phone is not found, try these x64 drivers... or these if you're running a 32 bit OS. To install these, go to Control Panel and click on your Android device and do "Update Drivers" and browse to the location of the drivers you downloaded.
(5) Assuming your phone is on the list, everything should be ready to go. Press enter and the batch file will proceed and it will root your phone.
AFTER DOING THE ABOVE ONCE, AFTER EACH REBOOT:
(1) Attach phone and double click the root.bat file.
(2) Again, verify that your phone is on the list (proves your PC can see the phone). If so, press enter and the phone will be RErooted.
That's it! Works for me. Keep in mind that temp root is NOT a full root! Many apps will not run (won't see root) but that's just the nature of the current temp root. But some apps do work. Barnacle WiFi does for example: although sometimes it take two "start" presses to get it to connect as the first one sometimes produces errors. People say Titanium Backup and some other apps work: I haven't personally tested them. As temp root is really for dev and testing, test what you want and see if it works.
Hope this helps some of us to get a quick and easy temp root. If any issues are found, I'd be glad to modify this initial post and/or modify the batch files if any errors are found.
Mike
I can't get to the site to download the 64-bit drivers for windows. Anybody has an alternate links? Thanks.
Does this really work? How is this thread not blowing up??
vWvSTATICvWv said:
Does this really work? How is this thread not blowing up??
Click to expand...
Click to collapse
Really! Anyone out there? I expected to come back from lunch to find questions I needed to answer or maybe a suggested modification or two. This has been working for me for over 12 hours now. No restarts. No reverting to non-root. Barnacle Wifi Tether is still working. And the best thing is, if I have to restart the phone for some reason, I connect it to my computer, click, and 8 seconds later it is rooted again and I unplug it and go on my way.
Mike
can you run a wireless tethering app after temp root?
edit: see mikeyxda's post above this
I was hoping to be able to help some people with the Barnacle WiFi Tether app because a lot of people complain that they didn't get it to work and I suspect I got it to work with some combination of settings. Only problem is: I don't know how my Barnacle settings differ from those other people are using so I wanted to compare with others. Short on time right now but later I'll try to post my entire list of Barnacle settings. They work for me.
Edit: Oh Hell... I have a few minutes, here are my settings:
SSID: Evo 3D Tether
BSSID: <blank>
Wireless Encryption: not enabled (open)
Channel: mine is 6, probably doesn't matter
Custom Wifi Ad-hoc: none
Skip wpa_supplicant: NOT checked
Auto Associate: NOT checked
Access Control: NOT checked
New Client Actions: Notify Checked, nothing else checked
Local Mode: NOT checked
DHCP: Didn't mess with these
NAT: Didn't mess with that either
WAN: rmnet0 (whatever that means)
LAN: Blank
Mike
it seems like the link for the 32bit drivers is down also....
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
os10 said:
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
Click to expand...
Click to collapse
Try making sure fast boot is turned off and then power the phone down and power it back up. Then use the root.bat to reroot. Might not work the first time.
For those having trouble with the driver links, try this link. It's kind of a convoluted mess with countdowns, etc. but seems like the files are there. I haven't verified them yet though.
Mike
Gave it a shot, doesn't quite seem to be working for me.
johnsmusicbox said:
Gave it a shot, doesn't quite seem to be working for me.
Click to expand...
Click to collapse
What is it that isn't working: the rooting process itself or Barnacle? I was hoping to give enough feedback in this thread to get things working for the people who say "it doesn't work" because I've been watching other threads and most of these methods seem to be very inconsistent, meaning, they don't work for a lot of people. My intention was to find the kinks and get it working for the vast majority. If you can give me details like what you see during the process, whether any error messages display, and so on, we might be able to get a more reliable temp root.
Mike
Titanium backup is definitely not working with this.
So what's going on with this? Anyone got it to work?
OK, let's try this. This is a "cleaned up" version of a different method posted in another thread. Comes with 2 batch files. Run root-init the first time and then root-redo each time you restart after that. Let's see if this works better.
Mike
Ok...My guess is that people are scared and don't know exactly what they're flashing. Would you mind sharing the source of your find, Mike? If this does indeed work, I can't see people not using this method. HmMm
*EDIT* I found the source is from XHAUSX
*EDIT 2* IT WORKS!!
I'm having an issue with the wireless on the g tablet. It's stuck on "Turning Wif-Fi on... and never turns on. I've tried flashing back to stock tnt, clearing any possible cache/system files I can think of. I'm currently running on the newest version of smoother bean that I just installed for the 3rd time just to make sure I didn't have an issue when flashing the rom. I've had no issues with it up until a few days ago. My friend borrowed it, tried to connect to a different wireless network. They input the password wrong once, and then it went to turning on and has been stuck there ever since. Help, i'm at my wits end! Thanks in advance
gargator said:
I'm having an issue with the wireless on the g tablet. It's stuck on "Turning Wif-Fi on... and never turns on.
Click to expand...
Click to collapse
Get hold a dmesg output like this: Reboot the tablet. Then, after the WiFi fails, open a Terminal Emulator window and type in the command line in bold.
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
Post the .txt file here.
rajeevvp said:
Get hold a dmesg output like this: Reboot the tablet. Then, after the WiFi fails, open a Terminal Emulator window and type in the command line in bold.
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
Post the .txt file here.
Click to expand...
Click to collapse
I'm a bit of a noob using the terminal emulator. When i type that command in, it says "operation not permitted".
You are going to have to give the terminal SuperSU. Permission first. Type in "su" first and grant it the permission the enter in the command.
gargator said:
When i type that command in, it says "operation not permitted".
Click to expand...
Click to collapse
That's a strange error to get. Post a screenshot, or, exactly what you typed in and the response you got back.
Since I'd rather not troubleshoot some obscure "ROM-not-setup-correctly" bug on top of a "WiFi-not-working" bug, see if you can run the dmesg via adb (set it up first if you have to). Connect the USB cable to the gTab, then in a CMD.exe window on the PC type:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------
nobe1976 said:
You are going to have to give the terminal SuperSU. Permission first. Type in "su" first and grant it the permission the enter in the command.
Click to expand...
Click to collapse
Why do you now need Superuser permissions to run dmesg or write to /mnt/sdcard? Are you doing something non-standard on Smoother Bean, Nobe?
Not that I am aware of. I just saw that he got the permission issue and tried it myself. Got same message and went ahead and su the terminal and was able to get the text file onto internal storage. Will look into this, but it is not a major.
Sent from my DROID BIONIC using xda app-developers app
nobe1976 said:
Will look into this, but it is not a major.
Click to expand...
Click to collapse
Well, it might be.
What it says is that an app which normally has permission to write to the SD card is unable to do so for some reason. Which implies that other apps also having the same permissions (sdcard_rw) might also have problems and so act screwy.
rajeevvp said:
Well, it might be.
What it says is that an app which normally has permission to write to the SD card is unable to do so for some reason. Which implies that other apps also having the same permissions (sdcard_rw) might also have problems and so act screwy.
Click to expand...
Click to collapse
Attached to post is .txt file.
If you have an external SD card in the slot, remove it, then boot the tablet up. See if the WiFi starts working.
Also, get me another dmesg output.
rajeevvp said:
If you have an external SD card in the slot, remove it, then boot the tablet up. See if the WiFi starts working.
Also, get me another dmesg output.
Click to expand...
Click to collapse
Wow...that fixed it. You managed to determine from that .txt file that the sdcard was preventing the wifi from turning on? You are a true genius. Thanks so much for the help.
gargator said:
Wow...that fixed it. You managed to determine from that .txt file that the sdcard was preventing the wifi from turning on? You are a true genius. Thanks so much for the help.
Click to expand...
Click to collapse
So glad that you guys figured it out. The nexted step is to find out how it happened. If you can for me connect your micro sdcard to your PC and open up to view hidden files. Certain ROMs place hidden files on storage to run and if the card was running on a different device that could of been what caused the issue. Delete any hidden files and folders once they display and empty the trash can. If using Linux once you delete those files and folders another one will pop up named trash, delete that also.
Sent from my SmoOth A$$ Gtablet
nobe1976 said:
The nexted step is to find out how it happened. If you can for me connect your micro sdcard to your PC and open up to view hidden files. Certain ROMs place hidden files on storage to run and if the card was running on a different device that could of been what caused the issue.
Click to expand...
Click to collapse
Nope. This isn't a software problem at all. It's a HW fault--most likely with his microSD card: You can clearly see the kernel repeatedly trying, and failing, to read that card. And that, for some reason, causes the WiFi to go wonky because it is connected to the main system bus via a SDIO (an SDcard-like) interface.
gargator said:
You managed to determine from that .txt file that the sdcard was preventing the wifi from turning on?
Click to expand...
Click to collapse
It was actually quite simple to figure what the problem was from the error messages.
As I said above, you'll most probably have to replace your microSD card. But, to rule out bad electrical connections being the problem, it wouldn't hurt to clean the contacts on both the microSD card and inside the microSD card slot on the gTablet with some rubbing alcohol. See if you can get your data from the card after that.
rajeevvp said:
Nope. This isn't a software problem at all. It's a HW fault--most likely with his microSD card: You can clearly see the kernel repeatedly trying, and failing, to read that card. And that, for some reason, causes the WiFi to go wonky because it is connected to the main system bus via a SDIO (an SDcard-like) interface.
It was actually quite simple to figure what the problem was from the error messages.
As I said above, you'll most probably have to replace your microSD card. But, to rule out bad electrical connections being the problem, it wouldn't hurt to clean the contacts on both the microSD card and inside the microSD card slot on the gTablet with some rubbing alcohol. See if you can get your data from the card after that.
Click to expand...
Click to collapse
I will definitely give both a good cleaning just to make sure. There was no info on that sd card, and it had been working fine with it in there up until we had mistyped the wifi password. That's when the problem started. But still working fine after 24 hours. Thanks again for the help.
gargator said:
There was no info on that sd card, and it had been working fine with it in there up until we had mistyped the wifi password. That's when the problem started.
Click to expand...
Click to collapse
A wrong WiFi password didn't cause your current WiFi/SD card problem. There are 2 reasons for saying this:
1. Doing any one of Format /data, wipe data/factory reset, or Partition internal SD card in CWM would've erased your WiFi password. And, you've stated that you have done more than one of those operations in attempting to fix your problem. So, unless you typed in the wrong password each time, a wrong password is not the cause.
2. In any case, the kernel messages clearly show that it's failed to initialize the WiFi hardware, so a right or wrong password doesn't matter.
BTW, you haven't got me that follow-up dmesg output I wanted.
Long story short... I have a non-rooted SGH-M919 (Samsung Galaxy S4) with a completely broken screen. USB to PC transfer doesn't work, it's set to charge only, Kies doesn't see it...etc.
I have found that it's still on my wifi and on my google play account so I can install apps from the website. Does anybody know any apps I can install that will instantly let me access my files (and transfer them) without needing to do anything on the phone's side? Remote access would be great but I'd settle for file sharing even if only on the local network.
Any other ideas would be great! I need to recover pictures and contacts that aren't on google, or the SD card. New phone doesn't take the SIM.
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
NetworkAuditor said:
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
Click to expand...
Click to collapse
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
UnknownCloakedMan said:
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
Click to expand...
Click to collapse
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
NetworkAuditor said:
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
Click to expand...
Click to collapse
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
UnknownCloakedMan said:
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
Click to expand...
Click to collapse
Well, I've never used adb from recovery before, but a quick search makes me think it could be possible. If you're desperate to recover the data, I' m assuming anything is worth a try.
Now most of the time, stock recovery doesn't have adb access, but if you can manage to unlock your phone, you would be able to install CWM recovery and boot to it.
However, this is unlikely, as IMO, the SGS4 is one of the most painful phones to try to unlock, especially when you don't have access to the screen.
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
UnknownCloakedMan said:
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
Click to expand...
Click to collapse
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
NetworkAuditor said:
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
Click to expand...
Click to collapse
Nothing special at all. It only required:
> Phone in download mode, wired to PC with USB cable
> ADB installed on PC
> Samsung USB Drivers
> Open adb command prompt, and run the pull command (after finding the exact directory using adb shell)
I have an issue with my M20P. I got the phone 12 days ago and everything was fine with notifications up until yesterday. As of right now, I am NOT receiving notifications for whatsapp, gmail,* FB, messanger on time. They're constantly late and usually show up only when I actually go into one of the apps, then the content shows up and syncs, I guess.
I decided to manually launch important apps such as gmail, messanger, whatsapp and I checked all 3 boxes (primary, secondary and background launch). And this morning, after some 9 hours of not touching the phone, I woke up and there were some notifications (quite a few actually) and I was happy thinking the issue's gone but I was curious why there were no messanger and gmail notifications (two of my most active apps) and* I was right... as soon as I entered gmail, the mail that I did NOT receive notification for came on top of queue and messanger literally blew with how many notifications came at once. Other apps, less important, followed with some notification.
I'm worried because I actually decided to manually launch apps I use the most and still, the issue persists, even though most of users had this sorted with manual launching...
So yes, manual launching did not fix it for me
Is there anything else I should do and what?
And also, I have found out that this has only happened thus far on WiFi, my home WiFi. Mobile data doesn't seem to be affected. Will have to confirm though. I don't know if that's an important information...
Please help. I don't wanna sell the phone because other than this bs I like it very much
Go into settings/battery/more battery settings and make sure stay connected when device sleeps is toggled on.
jhs39 said:
Go into settings/battery/more battery settings and make sure stay connected when device sleeps is toggled on.
Click to expand...
Click to collapse
I already had that enabled.... anything else?
I'm still looking for any help.. please
Have you tried disabling PowerGenie.apk via adb?
https://forum.xda-developers.com/mate-20-pro/themes/remove-powergenie-to-allow-background-t3890409
Thanks to @klaus27
jhs39 said:
Go into settings/battery/more battery settings and make sure stay connected when device sleeps is toggled on.
Click to expand...
Click to collapse
kai84m said:
Have you tried disabling PowerGenie.apk via adb?
https://forum.xda-developers.com/mate-20-pro/themes/remove-powergenie-to-allow-background-t3890409
Thanks to @klaus27
Click to expand...
Click to collapse
I think this is my last resort. I really don't want to use my laptop to debug something unless completely necessary..
furiouszagreb said:
I think this is my last resort. I really don't want to use my laptop to debug something unless completely necessary..
Click to expand...
Click to collapse
That's the only fix available. You could unpack and decompile PowerGenie and see what's inside. A bunch of routines that try to identify apps that require being online, plus a bunch of hardcoded apps that are allowed to run in the background. That's Facebook and a bunch of Chinese apps. But everything else is being sent to sleep aggressively.
I tried every other setting available and still, the PowerGenie rendered any background app unusable.
You don't need to debug anything. Just turn on debugging, so you can disable PowerGenie. If you want to use your phone the way it is supposed to work, you have to get rid of PowerGenie. Using the ADB method is the only possible way I am afraid.
klaus27 said:
That's the only fix available. You could unpack and decompile PowerGenie and see what's inside. A bunch of routines that try to identify apps that require being online, plus a bunch of hardcoded apps that are allowed to run in the background. That's Facebook and a bunch of Chinese apps. But everything else is being sent to sleep aggressively.
I tried every other setting available and still, the PowerGenie rendered any background app unusable.
You don't need to debug anything. Just turn on debugging, so you can disable PowerGenie. If you want to use your phone the way it is supposed to work, you have to get rid of PowerGenie. Using the ADB method is the only possible way I am afraid.
Click to expand...
Click to collapse
I appreciate the thorough report. Before I do that, I'll run some over night tests to see if this perhaps is just due to my WiFi. For example, I'll leave the phone over night with WiFi disabled and mobile data on. If I receive all the notifications at the time they should have been received - I'll know the issue is with my WiFi and I'll update it to static and use the pre-set DNSs I found online.
I'm guessing you had the same issue... did it only work for you when you disabled powergenie? Have you tried perhaps what I will - to see if it was a WiFi issue? Or did it happen to you on mobile data too?
And what I find EXTREMELY weird - I had P20 Pro like until 15 days ago, updated to EMUI 9 and it received all the notifications on time. Is this solely M20P issue?
My issue was the Blackberry mobile device management suite, my company uses. Those apps use Android for work, so a separate encrypted partition (and a different user id), open a VPN tunnel and fetch emails in the background.
I have tried every possible solution, like turning off startup control, enabling those apps to run in the background, even checked special permissions, tried different hacks, reset my device multiple times, ... . Nothing helped. The VPN tunnel was capped after a few minutes and even if I opened it manually (by starting the app), the email app was sent to sleep hence not receiving anything.
I started digging around and found a way to disable system-apps even when you cannot disable them from the Android menus. I pulled a copy and decompiled it. This PowerGenie app has routines to identify apps that have widgets, pull a lot of power, have notifications, ... . And it has a list of package names (Android apps) that are never sent to sleep. Stuff like Facebook and Chinese apps. As I started digging around I found this to be a commonly reported issue with Huawei smartphones of all flavours. I think they built that in to mask the fact that Kirin has a higher standby drain than Qualcomm and Samsung. I am just assuming that..
For me this definitely wasn't an issue with my WLAN, DNS or the likes. Now without the PowerGenie, when I turn off the flight mode in the morning, the VPN app is connecting automatically and my Blackberry Hub is pulling all emails. WhatsApp, Gmail, even third party calendar apps now show their notifications in time. So I am happy.
Did it have any influence on my battery life? no, not at all.
I did the same for a couple of colleagues having the same phone and issues and they all are very happy now.
My company even stopped supporting Huawei phones because of these issues.
I can't comment on the P20 unfortunately as this was my first Huawei. But maybe the fact that you were upgrading from Oreo to Pie was the difference here.
furiouszagreb said:
I appreciate the thorough report. Before I do that, I'll run some over night tests to see if this perhaps is just due to my WiFi. For example, I'll leave the phone over night with WiFi disabled and mobile data on. If I receive all the notifications at the time they should have been received - I'll know the issue is with my WiFi and I'll update it to static and use the pre-set DNSs I found online.
I'm guessing you had the same issue... did it only work for you when you disabled powergenie? Have you tried perhaps what I will - to see if it was a WiFi issue? Or did it happen to you on mobile data too?
And what I find EXTREMELY weird - I had P20 Pro like until 15 days ago, updated to EMUI 9 and it received all the notifications on time. Is this solely M20P issue?
Click to expand...
Click to collapse
Thanks for explaining everything. I'll try some methods first and if they don't work I'll go with what you did.
Thank you.
@klaus27
It appears you were right. Tried everything, still some come through, some don't. This suck soooo much
furiouszagreb said:
@klaus27
It appears you were right. Tried everything, still some come through, some don't. This suck soooo much
Click to expand...
Click to collapse
Trust me, run through this short procedure and you won't regret it:
1) install Huawei ADB drivers: https://devfiles.co/download/zygGeX8N/Huawei-MediaPad-10-FHD-USB-Drivers-TeamAndroid.zip
2) install and enable ADB: https://www.xda-developers.com/install-adb-windows-macos-linux/
3) Open a CMD window, change directory to where ADB is installed. Run this:
Code:
adb shell pm uninstall --user 0 com.huawei.powergenie
4) Reboot
klaus27 said:
Trust me, run through this short procedure and you won't regret it:
1) install Huawei ADB drivers: https://devfiles.co/download/zygGeX8N/Huawei-MediaPad-10-FHD-USB-Drivers-TeamAndroid.zip
2) install and enable ADB: https://www.xda-developers.com/install-adb-windows-macos-linux/
3) Open a CMD window, change directory to where ADB is installed. Run this:
Code:
adb shell pm uninstall --user 0 com.huawei.powergenie
4) Reboot
Click to expand...
Click to collapse
I'm a total anti talent for this stuff. Do I install and do this from my phone or laptop?
furiouszagreb said:
I'm a total anti talent for this stuff. Do I install and do this from my phone or laptop?
Click to expand...
Click to collapse
1) from your laptop
2) Follow the link, perform the steps in the tutorial below "How to Setup the Android Debug Bridge (ADB)".
Then scroll down to the part titled "Microsoft Windows ADB Setup". Download the file from the link and unpack to c:\adb (you will have to create the folder).
Then you connect your phone to your laptop and will see a prompt for authenticating your laptop. This is all well documented, just follow the link
3) On your laptop, start menu, run, cmd. Now you will see a console window. Just enter the commands below
Code:
c:\adb\platform-tools
adb shell pm uninstall --user 0 com.huawei.powergenie
The reboot should obiously be done on your phone.
Sounds complicated, but is really easy.
@klaus27
Thank you for bearing with me and explaining. Just one more thing. On the second code, what do you mean by "maybe"?
furiouszagreb said:
@klaus27
Thank you for bearing with me and explaining. Just one more thing. On the second code, what do you mean by "maybe"?
Click to expand...
Click to collapse
I have checked the tutorial and adjusted my reply accordingly .
klaus27 said:
I have checked the tutorial and adjusted my reply accordingly .
Click to expand...
Click to collapse
Thank you so much for explaining everything even to a dummy like myself lol. Much appreciated.
klaus27 said:
1) from your laptop
2) Follow the link, perform the steps in the tutorial below "How to Setup the Android Debug Bridge (ADB)".
Then scroll down to the part titled "Microsoft Windows ADB Setup". Download the file from the link and unpack to c:\adb (you will have to create the folder).
Then you connect your phone to your laptop and will see a prompt for authenticating your laptop. This is all well documented, just follow the link
3) On your laptop, start menu, run, cmd. Now you will see a console window. Just enter the commands below
Code:
c:\adb\platform-tools
adb shell pm uninstall --user 0 com.huawei.powergenie
The reboot should obiously be done on your phone.
Sounds complicated, but is really easy.
Click to expand...
Click to collapse
Hey, I finally gave in and tried to do this but I am having so much trouble doing this mate. Could you please explain like you're talking to a child? My computer skills are abysmal. I downloaded these 2 links you said on my laptop. But I am stuck at step 2. Here are the screenshot to see where I got held up lol
gyazo.com/6541fa024b72309323ab6ed889e19420
gyazo.com/727b043a651185da8761ca8c72d8917a
gyazo.com/d510eef1ce22dde74362a670051b1d7d
When I right click on "platform tools" it gives me several options such as "extract to a specified folder" and I clicked on that (I dont know if thats right) and what do I do now? I am confused with the steps provided in the link. "Extract the contents of this ZIP file into an easily accessible folder (such ad C:\adb)" I dont know where and how to do that
Then it says "Open Windows explorer and browse to where you extracted the contents of this ZIP File" what does this mean?
And 3rd step dont even get me started.
Could you by any chance upload a video of going through all that and doing everything needed up until running the command to.disable power genie? Im lost man
@klaus27
As much as I would like to help you, I think it would make more sense if you ask someone physically around you for help. I don't think I can make it more simple than that and explaining that in such a detail without knowing what system you have is quite complicated.... But I am sure that if you show the instructions to someone with a little bit more experience, it would be a lot simpler...
Sorry I cannot help you further...
furiouszagreb said:
Hey, I finally gave in and tried to do this but I am having so much trouble doing this mate. Could you please explain like you're talking to a child? My computer skills are abysmal. I downloaded these 2 links you said on my laptop. But I am stuck at step 2. Here are the screenshot to see where I got held up lol
gyazo.com/6541fa024b72309323ab6ed889e19420
gyazo.com/727b043a651185da8761ca8c72d8917a
gyazo.com/d510eef1ce22dde74362a670051b1d7d
When I right click on "platform tools" it gives me several options such as "extract to a specified folder" and I clicked on that (I dont know if thats right) and what do I do now? I am confused with the steps provided in the link. "Extract the contents of this ZIP file into an easily accessible folder (such ad C:\adb)" I dont know where and how to do that
Then it says "Open Windows explorer and browse to where you extracted the contents of this ZIP File" what does this mean?
And 3rd step dont even get me started.
Could you by any chance upload a video of going through all that and doing everything needed up until running the command to.disable power genie? Im lost man
@klaus27
Click to expand...
Click to collapse
klaus27 said:
1) from your laptop
2) Follow the link, perform the steps in the tutorial below "How to Setup the Android Debug Bridge (ADB)".
Then scroll down to the part titled "Microsoft Windows ADB Setup". Download the file from the link and unpack to c:\adb (you will have to create the folder).
Then you connect your phone to your laptop and will see a prompt for authenticating your laptop. This is all well documented, just follow the link
3) On your laptop, start menu, run, cmd. Now you will see a console window. Just enter the commands below
Code:
c:\adb\platform-tools
adb shell pm uninstall --user 0 com.huawei.powergenie
The reboot should obiously be done on your phone.
Sounds complicated, but is really easy.
Click to expand...
Click to collapse
I tried following your steps, but when I put in the command, it says " 'c:\adb\platform-tools' is not recognized as internal or external command, operable program or batch file "