Database Info

Taking the risk of GB radiofor the sake of science.

Just talked to a friend from vzw, he told me that if something happened he will hook me up with a replacement for my tbolt.
I've been using gb radio since the 1st day it was leaked, i have no problems on my phone, just some random FCs but that's given.
Since we don't have a solid demographics on how many people got bricked, Im going to take the risk and see if i get bricked.
This morning i just got into a bootloop but looks like its just the battery giving false stats. Its been more than 6 hours now in my external charger and i assume battery doesn't hold charge anymore, Im going tommorow to vzw to have it replaced.
Question is, will logcat be enough to monitor my phone in case i got bricked so i can pull some important data regarding how it happen?, that way we can find a clue on how to fix a radio-bricked tbolt.

Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App

Wow. Very cool that you're willing to do this. Looking forward to seeing what you find out.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
From what I've read, that's not possible as the bootloop happens even booting into recovery.

kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes i have cleared my battery stats. My previous battery is now dead. I think i discharged it too much, now its not holding any charge. My phone still runs on gb bamf and loving my lockscreen. Will let you know if i get bricked.
Sent from my ADR6400L using XDA App

i too am sticking it through, im too in love with this to revert back.

yakitori2 said:
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
Click to expand...
Click to collapse
Lol you obviously didn't read his post. No risk involved.

I hope someone could shed a light to my questions.
1st. How does the radio firmware work on our phone? Does it work like a driver where it acts a mediator between the roms(software) to the phone's hardware.
2nd. What are the possible trigger to recreate the bootloop of death? There are some cases that my phone overheats because of non responsive apps and ever since i flashed on GB rom there i times i can feel my phone hot, which could be the case from some of the boot loop victim that they fried something inside their phone.
3rd. What are the chances that same bootloop of death could also occur in froyo radio? Just because vzw officially released the radio doesn't mean it has same risk like the leaked GB radio. It is like how HTC manufactured the phone, they tested most of it but some are still lemons.
Everything is in theory right now, there are no fix because it happens in random and the reason is still unknown. I'd choose to participate for the fix instead of waiting for someone to figure out the fix. We all do take a bold step in rooting our phone, flashing different roms, putting our faith on the battery that it wouldn't fail during the flashing process. Once we modified our phone from its stock settings we acknowledge the risk, and that risk is the one of the few factors the fuels the development of the rom/kernel community.
I've noticed several repacks of the GB radio:
http://www.multiupload.com/HU471CMQI0 ----
MD5: EE2A824E51CB148A2256F93E30A3B9F9
http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ---- MD5: fda2a314975dd829b4e3611ecc8cfa13
PG05IMG_gingerradio.zip <- from http://forum.xda-developers.com/showthread.php?t=1082001 links alread removed. This is the same radio from androidpolice.com----
MD5: 52DD83AA40E30186C9FBEFAFD1BAB534
For the record, i flashed mine with the MD5: EE2A824E51CB148A2256F93E30A3B9F9
right now im using das bamf 2.0-5 running on imoseyon_leanKernel_v2.5.4GBtest6
Im keeping a close watch on my temp running on "extreme settings" 1.4ghz extremely undervolt.
SetCPU profile set to minimum setting when temp goes more than 97F

I just called verizon 611. My phone is not bricked and still functioning properly, but i told the operator that my phone constantly reboots( I pretended that my phone was bricked), i was passed to higher level tier support and they said they will be sending a new phone to me and there will be an extra envelop where i need to put my old phone to return to them. The call only took me 10-15 minutes and I believe VZW is aware that Tbolt has this issue even if its GB or the stock froyo rom.

i reverted back last night but i will def be back once things are more stable.. i already miss it

Going back to Gingerbread.

I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.

Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.

Dnakaman said:
Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.
Click to expand...
Click to collapse
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Man, that sucks. I know I've seen you post about the issue, but you seem to be the only one that actually has this issue that has actually posted anything concrete here.
Others that have posted about "bricks" sounded like they just didn't know what they were doing and were actually recoverable.
But like Mike said, enough for me to wait until more evidence is uncovered.
Thanks for the info.

miketoasty said:
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?
Click to expand...
Click to collapse
And to add to the above I do all my rooting via adb, I have never used a one click root. I'm also an Official Themer on another forum, so I know my way around Android a little.
I had insurance that made me send it off to try to have it repaired first. I just got a new one yesterday.
I'm waiting on a new Gingerbread radio to come out before going back to Gingerbread even though how much I miss it.

Well right before the news was posted, I noticed some connection issues, it was kind of a weird issue. So I reverted back right after seeing the brick thread....
SCARY!

I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!

bp328i said:
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Question for you. Did you have a third-party or extended battery in it?

want a droid said:
I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!
Click to expand...
Click to collapse
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Nope, stock battery and charger.
Sent from my ADR6400L using XDA App

SirVilhelm said:
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.
Click to expand...
Click to collapse
This is what I figured.

A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX

want a droid said:
A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX
Click to expand...
Click to collapse
I think that is where the real problem is.
The issue is so random, there is no set explaination at this time to explain why/how it happened.
Since the one person that I know of sounds like a very creditable person based on feedback on these forums, I myself am going to error on the side of caution.
I was running GB with no issues as well, but I would hate to kill my phone, just because I "thought" it was safe to reload GB.

I have been on BAMF since they came onto the TB scene. Less than a week from phone release I rooted and started rom'ing. I loaded the new ginger radio about a day before the first report of the brick came out. I havent had any problems. But I have been keeping my eyes open to see when or what will cause a brick so every two seconds I cheack my phone BUT i can't post in the development forum yet So i gotta wait till ten UGH

i'll wait for our developers to give the thumbs up on going over to GB roms, whats the rush vs the risk? Not a big deal to wait another week or two considering what u could be going thru. BAMF remix 1.7 is running flawlessly for me after I dropped back from GB.

I was using Gingeritis from Beta 3 to Gingeritis IX. Honestly, I haven't had a single random reboot or any problem at all.
However, I did have a data issue. If my phone would change to a 3g signal, it wouldn't bring back 4G. But, once I rebooted the phone one time, the problem was fixed from there on.
I still have Gingeritis IX on my phone, and its great. I'm running Imo's test6 kernel as well.

miketoasty said:
I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.
Click to expand...
Click to collapse
Honestly the bricking thing threw me off first, then I noticed it takes forever to charge, drains quicker and camera and camcorder sucks on gingerbread. So I'm sticking on froyo Bamf for awhile.

Yeah I'm back on froyo. And to those who are "watching my phone and no signs of bricking", there will be no signs. You'll pull your phone from your pocket and have a bootlooping phone, unfortunately. I'm running CM7 gb, 95% of things work like they should, and since it's a froyo radio, I'm immune to the brick of death.
Sent from my ThunderBolt using XDA Premium App

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Hmmm... I was wondering this myself. I'm on GB BAMF 2.05 and only have random reboots when I have my 3rd party battery in. The stock battery doesn't seem to have any issues.

Anyone else disappointed with multitasking?

I'm coming from a samsung vibrant and although it's slower it seems like it multitasks a lot better. I'm pretty sure this is due to sense taking up way too much ram. The phone is pretty fast opening up apps and I'll probly end up keeping it but I'm very disappointed in the multitasking. Also I can't count how many times I have pressed the home screen button and it has to reload the home screens because it runs out of ram. Is anyone else having this issue?
Sent from my HTC VLE_U using XDA

McQueefus said:
I'm coming from a samsung vibrant and although it's slower it seems like it multitasks a lot better. I'm pretty sure this is due to sense taking up way too much ram. The phone is pretty fast opening up apps and I'll probly end up keeping it but I'm very disappointed in the multitasking. Also I can't count how many times I have pressed the home screen button and it has to reload the home screens because it runs out of ram. Is anyone else having this issue?
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
I haven't had this issue have u thought about rooting it and installing a custom rom. I haven't had any ram issues at all. I'm on zero one rom
Sent from a guy living in a van down by the river

Yes I have thought about rooting it but I'm kinda scared. I'm not new to rooting phones( I've rooted every Android phone I have had) but this one scares me because of no removable battery. My vibrant was nice because of a program called Odin that saved me quite a few times when I've had a bad flash. Odin was a program that would flash the phone back to stock firmware no matter what happend to your phone which made the vibrant virtually unbrickable. Does HTC have any software that will do that?
Sent from my HTC VLE_U using XDA

McQueefus said:
Yes I have thought about rooting it but I'm kinda scared. I'm not new to rooting phones( I've rooted every Android phone I have had) but this one scares me because of no removable battery. My vibrant was nice because of a program called Odin that saved me quite a few times when I've had a bad flash. Odin was a program that would flash the phone back to stock firmware no matter what happend to your phone which made the vibrant virtually unbrickable. Does HTC have any software that will do that?
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
I know about Odin and no HTC software like that but if u follow the guides u wont break it. The T-Mobile guide here in the general swction works perfectly if your on tmobile Plus koush just released a stable recovery today through the rom manager app. So just follow that guide but instead of using that recovery he suggested in the thread just use the one in rom manager
Sent from a guy living in a van down by the river

Oh and if hold the power button for ten seconds or so it will do a hard reset of the phone no matter if the phone is stuck in a boot loop or not. I was stuck in a boot loop because I was trying to theme something and it was just boot looping and I held the power button and sure enough it turned off the phone and I was able to get into boot loader again. So not having a removable battery shouldn't be an issue
Sent from a guy living in a van down by the river

McQueefus said:
I'm coming from a samsung vibrant and although it's slower it seems like it multitasks a lot better. I'm pretty sure this is due to sense taking up way too much ram. The phone is pretty fast opening up apps and I'll probly end up keeping it but I'm very disappointed in the multitasking. Also I can't count how many times I have pressed the home screen button and it has to reload the home screens because it runs out of ram. Is anyone else having this issue?
Sent from my HTC S using XDA
Click to expand...
Click to collapse
Let's see your vibrant do this...https://www.youtube.com/watch?v=8o4mHPcZOsE&feature=youtube_gdata_player
You are right, this phone sucks!/sarcasm/
Sent from my cm_tenderloin using Xparent Cyan Tapatalk 2

lol, I watched that video before I bought this phone however, what the video doesn't show is that when you click on a app in the recent apps menu it usually has to reload the app so its not really truly multitasking. Android has a built in task manager that closes out the other apps when it needs more ram for the new app and because sence is a ram hog sometimes It will only allow me to run one app at a time. And i never said the phone sucks, I just said I was disappointed. I like the phone and I even like sence, ( its very sexy) but it uses way to much ram. Probably doesn't help that my home screens are loaded with Widgets too. : P
Sent from my HTC VLE_U using XDA

@ jriv,
My vibrant would also do a hard reset when you hold the power. However when I would bootloop and did that it would only reboot into a bootloop. Are u saying that you can reboot into recovery this way during a boot loop? I also had a Motorola cliq that I almost bricked but was able to pull out my SD card and put it in my computer so I could put another file on it and reflash the rom. With no external SD I am also hesitant.
Sent from my HTC VLE_U using XDA

McQueefus said:
@ jriv,
My vibrant would also do a hard reset when you hold the power. However when I would bootloop and did that it would only reboot into a bootloop. Are u saying that you can reboot into recovery this way during a boot loop? I also had a Motorola cliq that I almost bricked but was able to pull out my SD card and put it in my computer so I could put another file on it and reflash the rom. With no external SD I am also hesitant.
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Yes if you hold power it will turn off the phone then you can hold the power button plus volume down and it boot into boot loader then from there u can select recovery.
Sent from a guy living in a van down by the river

And u shouldn't worry about external SD because the holding of the power button will turn the phone off no matter what and from there u can reboot into boot loader then recovery
Sent from a guy living in a van down by the river

Maybe I will check it out. I know if I keep it i will end up rooting it eventually but I am still trying to decide. The phones I had before the vibrant ( Motorola cliq and HTC my touch 3g) were a bit of a pain with radio compatability and roms. That is another reason I'm a little weary. I can't remember the last time ive had to use adb. Everything was so easy with the vibrant
Sent from my HTC VLE_U using XDA

McQueefus said:
Maybe I will check it out. I know if I keep it i will end up rooting it eventually but I am still trying to decide. The phones I had before the vibrant ( Motorola cliq and HTC my touch 3g) were a bit of a pain with radio compatability and roms. That is another reason I'm a little weary. I can't remember the last time ive had to use adb. Everything was so easy with the vibrant
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Rooting is simple there is just a program you run and it roots you're phone for you.the other part is un locking the bootloader but there is instructions for that. As of right now there are no radios to choose from so all roms work pretty easy.
Sent from a guy living in a van down by the river

Is there a way to relock the bootloader and return to factory settings just in case I need to return the phone?
Sent from my HTC VLE_U using XDA

McQueefus said:
Is there a way to relock the bootloader and return to factory settings just in case I need to return the phone?
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Yes on the htc site they tell u how to relock bootloader its just a command u run in adb
Sent from a guy living in a van down by the river

McQueefus said:
I'm coming from a samsung vibrant and although it's slower it seems like it multitasks a lot better. I'm pretty sure this is due to sense taking up way too much ram. The phone is pretty fast opening up apps and I'll probly end up keeping it but I'm very disappointed in the multitasking. Also I can't count how many times I have pressed the home screen button and it has to reload the home screens because it runs out of ram. Is anyone else having this issue?
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
"Loading" message on the home screen is caused by enabling a setting in "Developer options" called "Dont"t keep activities". This setting instructs the phone to "destroy" every activity as soon as you leave it. So in essence, everytime you leave the home screen to do anything else, the phone "destroys" HTC Sense. The loading message is HTC Sense being restarted once you exit to the home screen. Unchecking this "feature" will eliminate the "Loading" message.

Destroy activities seems clear by default. Was wondering if anyone played with the background process setting though...it has a default and 1-4 processes allowed.

el_smurfo said:
Destroy activities seems clear by default. Was wondering if anyone played with the background process setting though...it has a default and 1-4 processes allowed.
Click to expand...
Click to collapse
I think I hit it by mistake while in the developer options. It was only after being in here that the "loading" started happening. Clearing it resolved it for me. Not sure how the background processes setting changes things. I left it at default.

forget the developer options or scripts. they don't help.
as many of you know there're no multitasking issues on other recent android phones. you can leave games or streaming apps and come back to them half an hour later and still be in the same spot. with HOS as soon as you leave them, you're going to start over. the oom values don't help much with the situation as the phone has plenty of memory for any applications. the issue isn't the memory available, but how the phone manages saved states and KERNEL is responsible for that. so until a talented soul would be able to fix it on KERNEL level for us we're are stuck with it.

I have a Vibrant that I still mess with, if you ask me Odin sucks big time. It's more of a crutch then anything if you ask me. Of all the 5 android devices I hate the Vibrant the most. That being said it still is a good phone and the one I use currently is run Slim ICS.
I can tell you that you don't have to worry about the non-removable battery. Holding down the power button will always power off the phone. No need for a battery pull.
I can also tell you that multitasking SUCKS on the stock One S rom. The phone reloads apps much much more often then my other android devices.
See this 77 page thread on the ATT One X forum if you disagree. http://forum.xda-developers.com/showthread.php?t=1646409&highlight=multitasking
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
mannequin said:
forget the developer options or scripts. they don't help.
as many of you know there're no multitasking issues on other recent android phones. you can leave games or streaming apps and come back to them half an hour later and still be in the same spot. with HOS as soon as you leave them, you're going to start over. the oom values don't help much with the situation as the phone has plenty of memory for any applications. the issue isn't the memory available, but how the phone manages saved states and KERNEL is responsible for that. so until a talented soul would be able to fix it on KERNEL level for us we're are stuck with it.
Click to expand...
Click to collapse
Bingo! Mannequin is spot on about the multitasking problem.

I tried....I really did!

I hate posting threads with questions cause I hate feeling like a noob who doesn't read but in this instance I really tried to fix the problem myself and just can't.
My wife's infuse keeps rebooting. It did it when on stock and I thought I could solve it by rooting and loading a custom ROM. In my experience loading custom ROMs almost always makes things better.
So far I've tried yumaporn ICS and Scott's broccoli ICS. I've tried the v6 supercharger. I've made her get rid of all her apps and even change off of go launcher. Which I had used on my infuse without problems.
I'm thinking of bringing her back to gingerbread but I am not sure its software related.
I've checked the battery connections and they look just like mine. I don't see anything broken. The battery is a little loose but I put a piece of paper around it and it doesn't move at all anymore.
I don't think its the power button because it doesn't loop.
I don't know how to get a kmsg or ksmg? Log cats I don't think will help because it isn't any 1 thing that causes it.
I tried the supercharger thinking it was a memory thing. Tried setting background processes to 2.
Got rid of all task managers, tried wiping caches.
I just don't have the knowledge to do anything more than I have done. I really think its a hardware problem and am hoping someone can prove me wrong.
10 post thanks and a +1 to whoever can fix this. If it can be fixed!
Sent from my SGH-I997 using xda app-developers app

csandman1977 said:
I hate posting threads with questions cause I hate feeling like a noob who doesn't read but in this instance I really tried to fix the problem myself and just can't.
My wife's infuse keeps rebooting. It did it when on stock and I thought I could solve it by rooting and loading a custom ROM. In my experience loading custom ROMs almost always makes things better.
So far I've tried yumaporn ICS and Scott's broccoli ICS. I've tried the v6 supercharger. I've made her get rid of all her apps and even change off of go launcher. Which I had used on my infuse without problems.
I'm thinking of bringing her back to gingerbread but I am not sure its software related.
I've checked the battery connections and they look just like mine. I don't see anything broken. The battery is a little loose but I put a piece of paper around it and it doesn't move at all anymore.
I don't think its the power button because it doesn't loop.
I don't know how to get a kmsg or ksmg? Log cats I don't think will help because it isn't any 1 thing that causes it.
I tried the supercharger thinking it was a memory thing. Tried setting background processes to 2.
Gog rix of
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
try taking out the microSD if there is one.
take off all important stuff in the internal sdcard
factory reset from in the phone under /privacy
heimdall or odin back to gb stock..i like the heimdall x2 with boot loaders for complete repartition.
if you are still rebooting or looping in complete gb stock, it's prolly hardware related

I should have known the avatar would have some idea. Will try that now. Thanks!
Sent from my SGH-I997 using xda app-developers app

Well. I tried to heimdall the thing and my computer about blew up. Hoping I can at least boot it to safe mode and somehow get all the pictures off before it finally explodes. So. I couldn't heimdall so I put a stock uclb 3 ROM on it. Its running now and I hate it. Thankfully its not mine. I can't stand stock. What's worse is we went to a store today and they had an s3 on display. Shouldn't have even touched it. Even being the display phone the damn thing was zippy. No upgrade for another few months. Hoping the note 2 is that fast
Sent from my SGH-I997 using xda app-developers app

Battery wipe?

Here is my question... im getting different reading of battery on my a2.. let say i have around 80% after a reboot it went to 85%.. also i have different reading in bmm.. around 5% difference.. i wipe my batt fo a few time b4.. now it seems messed up.. XD
Sent from my MB865 using Tapatalk 4 Beta

hafizkris90 said:
Here is my question... im getting different reading of battery on my a2.. let say i have around 80% after a reboot it went to 85%.. also i have different reading in bmm.. around 5% difference.. i wipe my batt fo a few time b4.. now it seems messed up.. XD
Sent from my MB865 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Wiping battery stats does nothing but delete a log file. Will not calibrate or anything of the sort.
Google it for those of you that dont believe.
But as far as the different readings. This device is so messed up with the BS that is put on it....mainly BMM. we nolonger have a standalone system, so nothing will ever be right. Call me old school. but first phone with BMM and worst phone I've ever had. Coinicidence? you tell me

Strange, my phone certainly isn't perfect, but I like it much more since installing BMM and custom roms. My battery life has suffered but I'm much happier the way it is.
My thoughts are dig in and fix it or flash back to stock. Nothing wrong with pointing out issues, but but it's not very productive to run custom software and just complain about how crappy it is.
Sent from my MB865 using xda app-developers app

Haha.. Guess its normal for multibooter to suffer this kinda stuff constant reboot and stuff.. Tho i think i only have this with one rom.. Im tryin to use other rom for a while and see the difference..
bmm and bs is the only way around so like or hate it.. Its a tool to at least feel what flashing means.. When I bought this phone I've see this coming but I took the risk..
Sent from my MB865 using xda premium

MotoMudder77 said:
Wiping battery stats does nothing but delete a log file. Will not calibrate or anything of the sort.
Google it for those of you that dont believe.
But as far as the different readings. This device is so messed up with the BS that is put on it....mainly BMM. we nolonger have a standalone system, so nothing will ever be right. Call me old school. but first phone with BMM and worst phone I've ever had. Coinicidence? you tell me
Click to expand...
Click to collapse
Don't blame BMM, blame Motorola and the locked bootloader. If it wasn't for that we wouldn't have so many hoops to jump through just to flash these ROMs. You should instead, be thankful to whirleys for BMM and giving you a workaround so that you can have something other than MotoBlur running on your phone.:thumbup:
Brought to you by time and relative dimensions in space.