jgarci40 / battery-indicator

Automatically exported from code.google.com/p/battery-indicator
Other
0 stars 0 forks source link

Impossible number of hours unplugged #48

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Not sure how to reproduce it. 
2. Android battery usage meter currently reports 3 days 16 hours 48 minutes on 
battery, but app notification drawer section reports 59803 hrs unplugged, so a 
bit under 7 years.
3. Currently using CM7.1 stable on Galaxy S GT-I900.

What branch (Free or Pro) and version (number) of the app are you using?
Pro version 4.0.4

Which device are you using?
Galaxy S International

Which carrier are you using?
Virgin Mobile Australia

What language is your device set to?
English US

Which version of Android are you using?
2.3.7

Please provide any additional information here:

Original issue reported on code.google.com by AIM120.S...@gmail.com on 29 Oct 2011 at 4:29

GoogleCodeExporter commented 8 years ago
If you plug your phone in, what does that message change to?  And when you 
unplug it again?

Original comment by andr...@darshancomputing.com on 31 Oct 2011 at 11:47

GoogleCodeExporter commented 8 years ago
Issue 51 has been merged into this issue.

Original comment by andr...@darshancomputing.com on 5 Nov 2011 at 1:17

GoogleCodeExporter commented 8 years ago
I'd give you more info but in the course of trying to update it to 5.0.1 to see 
if that would fix the bug it decided that it wouldn't install properly and 
prompts me to an uninstall and reinstall loop. Clearing relevant caches don't 
help so I don't have anything further to add at this point.

Original comment by AIM120.S...@gmail.com on 5 Nov 2011 at 1:24

GoogleCodeExporter commented 8 years ago
So you're having the same upgrade problem as Issue 40?  If so, I'll say the 
same thing to you as I said there -- I have no idea how that could happen, and 
I would need to work with you directly over email in order to figure it out.  
Would you be willing work with me over email, running a few test builds and 
sending me system logs?

Original comment by andr...@darshancomputing.com on 5 Nov 2011 at 1:30

GoogleCodeExporter commented 8 years ago
I could give it a go, though I'll just warn that I might be a bit slow to reply 
because I'm a little swamped with things to do now.

Original comment by AIM120.S...@gmail.com on 5 Nov 2011 at 1:39

GoogleCodeExporter commented 8 years ago
Thanks for the system log.  Here's the really interesting bit:

W/PackageManager(190): Couldn't remove app data or cache directory for package: 
com.darshancomputing.BatteryIndicatorPro, retcode=-1

When you tried to uninstall, for some really strange reason, Android "couldn't" 
actually fully uninstall it.  That definitely explains why the new version of 
the app is having a problem, but I don't yet know why the uninstall failed or 
what to do about it.  I'll give it some thought/research and get back to you 
soon.

Thanks,
Darshan

Original comment by andr...@darshancomputing.com on 6 Nov 2011 at 3:57

GoogleCodeExporter commented 8 years ago
Issue 40 has been merged into this issue.

Original comment by andr...@darshancomputing.com on 7 Nov 2011 at 9:00

GoogleCodeExporter commented 8 years ago
So I'm taking a stab in the dark, because this is a weird issue that really 
shouldn't happen -- uninstall should always work!

I'm thinking that perhaps some builds of Android (or perhaps any build, but 
only under certain circumstances?) are getting confused by the change in 
sharedUserId.  (This is the big change in v5 that both allows the icon plugins 
to work and requires an uninstall.)  So I've created a package versioned just 
like BIP 4.0.4 that does nothing but initiate an uninstall, and similarly for 
5.0.0.  Since I can't reproduce the issue and it doesn't make any sense, I'm 
going to recommend this process:

1) Download and run the attached 4.0.4 package.
2) Download and run the attached 5.0.0 package.
3) Download and run the attached 4.0.4 package.
4) Download and run the attached 5.0.0 package.

That is, use the 4.0.4 attachment, then the 5.0.0, then repeat.  I'm really 
hoping that this will ensure a successful uninstall.  So after doing that, try 
again to install the new version from the Market.

Please report back whether this is successful or not.  If not, if someone could 
send me a system log immediately after trying, that would be great.  But 
fingers are crossed that this does the trick.

Thanks!

Original comment by andr...@darshancomputing.com on 7 Nov 2011 at 9:11

Attachments:

GoogleCodeExporter commented 8 years ago
Tried it, didn't work. Sent you the log.

Original comment by AIM120.S...@gmail.com on 7 Nov 2011 at 10:37

GoogleCodeExporter commented 8 years ago
Okay, since the data still isn't being deleted during the uninstall, try this:

1) Go to "Manage Apps" and then the listing for Battery Indicator Pro.
2) Press "Force stop", then "Clear data", then "Uninstall".

3) Install the 4.0.4 APK attached to comment 8. (But don't run it.)
4) Go back to the manage apps listing for it.
5) Press "Force stop", then "Clear data", then "Uninstall".

6) Install the 5.0.0 APK attached to comment 8. (But don't run it.)
7) Go back to the manage apps listing for it.
8) Press "Force stop", then "Clear data", then "Uninstall".

For steps 2, 5, and 8, "Force stop" might not be pressable -- press it if you 
can, and don't worry if you can't.

Then you should hopefully be able to successfully install the current version 
from the Market.

Original comment by andr...@darshancomputing.com on 7 Nov 2011 at 11:01

GoogleCodeExporter commented 8 years ago
Force stop isn't available at any stage because the app isn't running. Neither 
is Clear data. Log sent again.

Original comment by AIM120.S...@gmail.com on 7 Nov 2011 at 11:13

GoogleCodeExporter commented 8 years ago
Well, since you're on CyanogenMod, you should be able to fire up a terminal and 
run:
  rm -rf /data/data/com.darshancomputing.BatteryIndicatorPro/

If you don't already have a terminal, I know of one called Terminal Emulator in 
the Market, but any should work.  You'll just want to type that command (be 
sure to get it exact) into the terminal and then press Enter/Return.

Original comment by andr...@darshancomputing.com on 8 Nov 2011 at 2:59