• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Bizarre battery problems cropped up during romming

About fixing permissions in cwm, I accidentally (lol) hit it one time when I was on blu Kuban and when it finished and I booted the phone up, lots of stuff was glitchy. Volume bars were all whacky. You sure I should mess with it?
 
greg schmeg said:
About fixing permissions in cwm, I accidentally (lol) hit it one time when I was on blu Kuban and when it finished and I booted the phone up, lots of stuff was glitchy. Volume bars were all whacky. You sure I should mess with it?
Click to expand...

If I remember right Bil said that was all embedded in the rom at startup, but not to say that it may fix your problem, I used it a lot and never had any issues as you suggested but each rom is different I don't see were it could make things worse if your going to install 2.8, maybe worth a try....:)
 
Maybe just a redo, know you only clean flash sir of 3.0 would work? Posted a few screenshots in parent forum if you will to this solution portion. Only differences pretty much from what it comes with other than some apps are undervolting 25 per step, are bc I like to use SwiftKey dropped default keyboard, but reckon that's an app too lol. Will send xtra stock battery this week so lemme know how you want it sent at some point, and hope it helps.
 
There's confusion in the world on what permission fixing is all about. Good news - anything that Stericson says you can take to the bank.

He explains the basic deal in his app -

https://play.google.com/store/apps/details?id=com.stericson.permissionfix

If fixing permissions from recovery made something wonky, use his app - and maybe check to see if your recovery is really right. :eek:

Bad flashes can happen anywhere.
 
When I originally flashed el29 direct boot .tar.md5 in mobile Odin I selected to Wipe Data and Cache, and Wipe Dalvik Cache before selecting he flash firmware button. After redownloading the el29 kernal just now and verifying md5 sum, I noticed that in the xda thread I got it from, the creator of it says in his instructions to simply select the file and flash it, and to not select the wipe data and wipe dalvik options. Did I mess something up by doing this when I originally flashed over project x 3.0, because it was at this time when this whole battery thing started happening. Did I mess up the partition somehow or is that unrelated? Any thoughts?
 
greg schmeg said:
When I originally flashed el29 direct boot .tar.md5 in mobile Odin I selected to Wipe Data and Cache, and Wipe Dalvik Cache before selecting he flash firmware button. After redownloading the el29 kernal just now and verifying md5 sum, I noticed that in the xda thread I got it from, the creator of it says in his instructions to simply select the file and flash it, and to not select the wipe data and wipe dalvik options. Did I mess something up by doing this when I originally flashed over project x 3.0, because it was at this time when this whole battery thing started happening. Did I mess up the partition somehow or is that unrelated? Any thoughts?
Click to expand...

Hmm well, I will tell you how I install all roms, one the only thing I use mobile odin for is to flash kernel's, not saying that you cant or shouldn't, a lot of people do use it without any issues, but there have been issues flashing with it and for that one reason I always use my pc, download the rom, check md5sum, then making sure I have the correct recovery, then move over the zip to the ext sd card and reboot into recovery and install the rom

Everyone has there own way of doing roms, this is my way and has always worked for me but again not saying you cant use mobile odin to do the same but again I have seen were people have had issues.

Hope that helps......:)
 
I just did a clean flash over to project x 2.8 from a newly downloaded el29 direct boot and battery still srems bad. Ive lost 7% battery in ten minutes. What could it mean if im on a newly flashed rom and still having trouble? Wouldnt that fix any permission issue right there? What could I have done that would alliw the battery issues between roms when everything is wiped?
 
EarlyMon said:
Always wipe cache and Dalvik after flashing.

Always.

Regardless of any other instructions.
Click to expand...

I was talking about before flashing. Before flashing the el29 kernel I was making sure I was supposed to select the wipe.data cache and dalvik options, for flashing the kernel itself
 
greg schmeg said:
I just did a clean flash over to project x 2.8 from a newly downloaded el29 direct boot and battery still srems bad. Ive lost 7% battery in ten minutes. What could it mean if im on a newly flashed rom and still having trouble? Wouldnt that fix any permission issue right there? What could I have done that would alliw the battery issues between roms when everything is wiped?
Click to expand...

It could be the after market battery you just replaced may not be working correctly....
 
This is possible. Just seems weird that even my original battery went bad overnight, going from perfectly fine and usable to totally shot. And then for this new battery to have issues immediately after Iinstallation independently of the old battery would be a weird coincidence. Thats what makes me lean towards a problem not involving the battery itself, but something the phone is doing.
 
:thumbup:
 

Attachments

  • 1375658367172.jpg
    1375658367172.jpg
    51.1 KB · Views: 30
  • 1375658487420.jpg
    1375658487420.jpg
    46.8 KB · Views: 64
  • 1375658508352.jpg
    1375658508352.jpg
    46.8 KB · Views: 63
greg schmeg said:
I was talking about before flashing. Before flashing the el29 kernel I was making sure I was supposed to select the wipe.data cache and dalvik options, for flashing the kernel itself
Click to expand...

Wiping cache and Dalvik before flashing does nothing.

The Dalvik cache is an association of apps to one another.

Example - you cannot launch the dialer without launching contacts.

Android = embedded Linux operating system (including the kernel) + Dalvik Virtual Machine + apps that run inside the Dalvik and use Linux services

The main cache is the operating system cache - just like your browser has.

Those two caches are in a separate partition from the kernel.

Shouldn't matter to ever wipe those before flashing. If a developer says to with his payload, fine. There's probably an exception that I can't think of.

But always wipe afterwards, no matter what.

The first sign of app trouble, what's the right thing to do?

Fix permissions, wipe cache and Dalvik.

By default, you're going to end up doing it at some point after any flash anyway - get the first one out of way, do it right after flashing.

Next to checking md5 sums, and always making nandroid and app/data backups, that's an essential flashing habit to pick up.

Make sense?? :o

PS - and for some apps, you want to wipe their individual caches while attacking trouble.

Android has a lot of caches lol.

greg schmeg said:
This is possible. Just seems weird that even my original battery went bad overnight, going from perfectly fine and usable to totally shot. And then for this new battery to have issues immediately after Iinstallation independently of the old battery would be a weird coincidence. Thats what makes me lean towards a problem not involving the battery itself, but something the phone is doing.
Click to expand...

Remind me - have we replaced the cable?

Cables can and do go intermittent and can develop faults where they appear to be correct - but simply aren't.

Never underestimate Murphy's Law in any of this. Coincidences, however bizarre and unrealistic, happen. Never rule them out.

Let's just say that they keep life interesting.

greg schmeg said:
I just did a clean flash over to project x 2.8 from a newly downloaded el29 direct boot and battery still srems bad. Ive lost 7% battery in ten minutes. What could it mean if im on a newly flashed rom and still having trouble? Wouldnt that fix any permission issue right there? What could I have done that would alliw the battery issues between roms when everything is wiped?
Click to expand...

I've been on a rom development team - I've had to fix permissions on my team's roms, which passed every test flashing and beating - right up to the point where I went ahead and did a final clean flash so I could enjoy my own work.

:rofl:

Bad flashes can happen any time and take any form. ;)

Titchener17 said:
:thumbup:
Click to expand...

Outstanding! :)

Sorry for flood posting - can merge all of those in a little bit if you prefer. :( :o

Done! :)
 
Yes I have replaced the cable with the same exact kind. But as of recently it seems to be charging okay. Even though it wasnt at one point. The battery drain is just rediculous. Im on a clean flash of proj x 2.8 with no debloating, hardly any apps added, its essentially totally stock. I was playing a little music here and there in a 4 1/2 hour discharge a little earlier without running any apps.except dolphin browser. Screen off almost whole time. Those four.and half hours took a mere 85% off my battery.... this is nuts... do I have a hardware issue?

Only apps I restored were apollo music player, titanium bu, chesstime, and gsam battery.
 
Let's rule out everything - please take off chess time and Apollo, see what happens.

I know right - but it's the only way to be sure.

After that, let's hope the battery coming (seriously cool dude, thanks) will fix it.
 
Solution- buy a new legit rated battery that matches the mah of your old battery.

Of course you are going to lose battery percentage compared to a stock battery rated at 1/4 more than your old one.

I think the only way to isolate this is to one-click to stock rom which will reformat everything correctly (unlike these manual wipes from CWM and zip wipes which look for an S line which doesn't even exist anymore). From this point re-root, flash your modem kernel, recovery and rom. If this doesn't do it, then you know it's not the software or user error- then buy a new battery. These aftermarket cheap POS batteries aren't worth the cost of shipping. Go with stock or an anker and be done with it.
 
BLVCKHVLO said:
Solution- buy a new legit rated battery that matches the mah of your old battery.

Of course you are going to lose battery percentage compared to a stock battery rated at 1/4 more than your old one.

I think the only way to isolate this is to one-click to stock rom which will reformat everything correctly (unlike these manual wipes from CWM and zip wipes which look for an S line which doesn't even exist anymore). From this point re-root, flash your modem kernel, recovery and rom. If this doesn't do it, then you know it's not the software or user error- then buy a new battery. These aftermarket cheap POS batteries aren't worth the cost of shipping. Go with stock or an anker and be done with it.
Click to expand...

Ya im out of state right now and dont have a computer around til I get back in a week. I would like to do a one click to see if that helps, but cant do anything aside from off of the phone itself for another week
 
If you send me your mail info and how you want it done and will get that stock battery off to you esse. Will cover shipping, just get me back when you can no worries
 
Ok so this is what I did. I charged phone to 94% with the phone off for a faster charge. Then I unplugged phone, then booted it up. Didnt touch it til next mornimg. It booted and stayed untouched for 9 hours. I woke up and found that my battery was still at 83%. Thats awesome. Maybe it wouldve been less if I had pulled up some apps before went to bed or something. Ill post my screenshots from last night and later Iill take new ones showinge using the phone today.
 
You must log in or register to reply here.
Back
Top Bottom