Battery wipe? - Motorola Atrix 2

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.

Related

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

Those of you bricking on GB - do you have fast boot enabled?

I noticed that fast boot on the GB roms gave me issues when booting. Wondering if its a compounding factor of having this turned on. I have not seen a single reboot issue on either Froyo or GB roms and we all seem to be running the same hardware configurations....
I really don't think you understand how fast boot works. Fast boot is not bricking anyone.
Sent from my ADR6400L using XDA App
adrynalyne said:
I really don't think you understand how fast boot works. Fast boot is not bricking anyone.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
All I know is when I have my phone on fast boot and go to shut down, my phone turns off (obviously). However, sometimes the LED light goes completely dark. Upon unplugging and plugging it back in it will come back on but the phone wont turn on when I try. Takes 5-6 attempts and sometimes reboots on the HTC screen.
That's because you have an app installed that isn't playing nice.
Fast boot is a suspend to RAM like feature. It will not work or function or affect recovery. Bricked phones reboot in recovery.
Sent from my ADR6400L using XDA App
So what you are telling me is that fastboot is no longer in the bootloader and cant possibly be a problem?
I'm really starting to wonder if alot of these "bricks" are not really bricks and just people not knowing what they are doing?
I know not all, but some of the ones that are bricks maybe were caused by inexperienced users trying to do things they shouldn't be doing without knowing how to do it?
Just my two cents.
Dnakaman said:
I'm really starting to wonder if alot of these "bricks" are not really bricks and just people not knowing what they are doing?
I know not all, but some of the ones that are bricks maybe were caused by inexperienced users trying to do things they shouldn't be doing without knowing how to do it?
Just my two cents.
Click to expand...
Click to collapse
I wonder the same thing... I read the post by a very respected Thunderbolt rom maker who made the original 'go back to froyo' post... But I LOOKED and LOOKED through threads trying to find this 'high percent' and couldn't find ones that were people just messing up going to HBOOT and flashing the new baseband/radio... most were trying to flash the new radio through Rom Manager or something else... and eventually found a way out (which isn't a brick) a BRICK is something you cannot get to work ever again, as far as I'm concerned...
so... I'm not sure what the risks are, because I'm not a developer but I have faith in the guy who helps make BAMF rom... I jumped back to froyo (reluctantly) but have a nandroid backup of GB just in case I feel frisky lol
Sorry.... Deleted
Sent from my Droid Bionic using XDA Premium App
Interesting that the CM7 build, which uses the GingerBread kernel, but the Froyo radio is not impacted.... really seems to tie it to the radio.
Running CM7 AOSP - ThunderBolt using XDA Premium App

[Q&A]Doctorz rom V8.1[XXJVT][ICS]

This rom is for questions and bugs reguarding the Doctorz rom...thank you..
Sent from my Doctored Up Infuse!
This is the place for all your questions and stuff about the Doctorz v8 ROM. Ask away.....
Ever since I installed this ROM I feel like a real doctor, I can F'n fix anything! Haha.
X,
Sent from my Infuse after it's Doctorz visit.
EXPERIMENT said:
This is the place for all your questions and stuff about the Doctorz v8 ROM. Ask away.....
Ever since I installed this ROM I feel like a real doctor, I can F'n fix anything! Haha.
X,
Sent from my Infuse after it's Doctorz visit.
Click to expand...
Click to collapse
question for the "doc" lol, saw where everyone was talking about the "not working" apps in the dev thread, can we not go in and remove the apps ourselves? I just went in and removed TiBu with root explorer and re-installed the version i purchased then went in and removed all the apps that don't work or not gonna use, or was that not something I should have not did?
cablegooru said:
question for the "doc" lol, saw where everyone was talking about the "not working" apps in the dev thread, can we not go in and remove the apps ourselves? I just went in and removed TiBu with root explorer and re-installed the version i purchased then went in and removed all the apps that don't work or not gonna use, or was that not something I should have not did?
Click to expand...
Click to collapse
It's probably fine.
After you reinstalled TiBu were you able to update? I know there were a few people that were having issues with the TiBu not updating.
I once heard though, that it's better to freeze unwanted apps rather than uninstalling. Something to do with OTA updates looking for the bloatware in order to validate that your system is not hacked/rooted. Anyway, it's probably not a big deal, just ever since I read that I always just freeze rather than uninstall. Unless its an app I put on there and or I know that it's not something AT&T put on there. But myself, I would apply that same theory to any of the things included with the ROM, anything I don't want I'll freeze rather than uninstall.
Let us know if that worked for the updating of TiBu.
Where can i get themes for this tw4.5 launcher?
Sent from my SGH-I997 using XDA App
intelligencexan said:
Where can i get themes for this tw4.5 launcher?
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
I will look into seeing if I can find some direct links for themes, but until then here is the Original Doctorz thread see if anybody has the answer there,
just make sure you clarify that you are an INFUSE user, since that thread is for the Galaxy S version. If you find something come let us know. Thanks.
intelligencexan said:
Where can i get themes for this tw4.5 launcher?
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Look at the bottom of DlevRom's OP for TW4.5 Themes. Click the Thank you now. Lol
Edit: I think there are Tw4 themes. Lol
EXPERIMENT said:
It's probably fine.
After you reinstalled TiBu were you able to update? I know there were a few people that were having issues with the TiBu not updating.
I once heard though, that it's better to freeze unwanted apps rather than uninstalling. Something to do with OTA updates looking for the bloatware in order to validate that your system is not hacked/rooted. Anyway, it's probably not a big deal, just ever since I read that I always just freeze rather than uninstall. Unless its an app I put on there and or I know that it's not something AT&T put on there. But myself, I would apply that same theory to any of the things included with the ROM, anything I don't want I'll freeze rather than uninstall.
Let us know if that worked for the updating of TiBu.
Click to expand...
Click to collapse
i could not update the TiBu that came with the rom but once I removed it and re-installed from market then the key no problems.. i did not know that about freezing the apps Ill remember that from the future, i just uninstalled the add on apps anyways I.E. ext4, reboot etc... so hope I will be good to go, if not gotten really good at odin and reflashing lol. Need to learn to just leave stuff alone and quit messing with things lol!! thanks for all you all's help and hope the development doesn't stop for the infuse.
Is yhe infuse not able to use the status bar settings?
Sent from my SGH-I997 using xda premium
I installed the rom, and have used it for a little over a day now.. I love the theme, and its def snappy, but has a few problems me and a friend found. We've both put the rom on our Infuses.
For a few flashes, my home button wouldn't work, but I think that was narrowed to backing up system data.. it now works for me though. On the first flash try, all calls being made TO my phone just got a busy signal, but I could call out.. My friend's phone calls only works when calling out. When he receives a call, itll end the call about 5 seconds into it.
He cannot turn his phone on while its plugged into the charger.. it wont do anything when he holds the power button. I cannot get root explorer to work, no matter what. I've reinstalled it, fixed permissions, still nothing. I now use another app to access it. When ever I get a new email and notification, my phone will freeze and reboot. I've had quite a few random reboots today as well, with my friend having only a few. It even rebooted while in the middle of a phone call.
I've tried a few different kernels, but not sure if i know when it installs correctly other than the phone boots up... I know the voodo kernel hasnt worked at all... itll sit on the samsung screen for at least 30 mins a few different tries.
Auto-Android said:
Is yhe infuse not able to use the status bar settings?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I found that the status bar settings has not changed anything that I could see, others have confirmed this. If it doors change anything I think its limited to the lockscreen if any changes are being made at all.
X,
Sent from my Infuse after it's Doctorz visit.
jorknow said:
I installed the rom, and have used it for a little over a day now.. I love the theme, and its def snappy, but has a few problems me and a friend found. We've both put the rom on our Infuses.
For a few flashes, my home button wouldn't work, but I think that was narrowed to backing up system data.. it now works for me though. On the first flash try, all calls being made TO my phone just got a busy signal, but I could call out.. My friend's phone calls only works when calling out. When he receives a call, itll end the call about 5 seconds into it.
He cannot turn his phone on while its plugged into the charger.. it wont do anything when he holds the power button. I cannot get root explorer to work, no matter what. I've reinstalled it, fixed permissions, still nothing. I now use another app to access it. When ever I get a new email and notification, my phone will freeze and reboot. I've had quite a few random reboots today as well, with my friend having only a few. It even rebooted while in the middle of a phone call.
I've tried a few different kernels, but not sure if i know when it installs correctly other than the phone boots up... I know the voodo kernel hasnt worked at all... itll sit on the samsung screen for at least 30 mins a few different tries.
Click to expand...
Click to collapse
Sounds like you have a bad flash. I'd start over, make sure you do your proper wiping. And read over the Dev section there are a lot of additional steps spread throughout. I will try to compile them into one post when I get some free time. Good luck.
X,
Sent from my Infuse after it's Doctorz visit.
EXPERIMENT said:
Sounds like you have a bad flash. I'd start over, make sure you do your proper wiping. And read over the Dev section there are a lot of additional steps spread throughout. I will try to compile them into one post when I get some free time. Good luck.
X,
Sent from my Infuse after it's Doctorz visit.
Click to expand...
Click to collapse
I've redownloaded the flash to my computer twice, recopied it to my phone twice, started with a complete fresh rom using odin that was already rooted and CWM installed, and wiped all data possible. I've followed all the steps, done reboots in between sometimes just to try something different.. I've reflashed my rom at least 6 times in the past two days maybe trying different things .
has anyone had bad battery drain with this? last night i charged 100% before went to bed, had JD running on aggressive mode, wifi anf BT disabled as well as setcpu no OC and profile for 400/100 when screen off.... got up this morning 6 hours and was at 38%, ive been running the rom for days now so i think its had time to bake but not sure what else to do? any suggestions.
Thats odd with the battery drain...mine has been doing great....so your saying it didnt fully charge? or it was full, u unpkugged went to bed woke up and it drained that much? that doesnt make sense...no rom should do that....check your runnibg services and tell me what all is constantly running
Sent from my SAMSUNG-SGH-I997 using XDA App
The battery full notification wont go away
Sent from my SGH-I997 using xda premium
Its not going to unless you reboot...that is a hellraiser bug
Sent from my SAMSUNG-SGH-I997 using XDA App
dman3285 said:
Thats odd with the battery drain...mine has been doing great....so your saying it didnt fully charge? or it was full, u unpkugged went to bed woke up and it drained that much? that doesnt make sense...no rom should do that....check your runnibg services and tell me what all is constantly running
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
i thought something may have got messed up so i just odin back to stock before i read this sorry dman, if someone say "me" was going to start back from scratch..... just odin, root, flash community kernal to get CWM then flash rom? should just leave kernal and modem alone? i know everyone has there own personal preference but as i talked to experiment just need to leave stuff alone lol. in other words with this rom what would "you" set up with i.e. kernal, modem, tweaks/ no tweaks, etc.... thanks for the feedback
Q- Can we remove the extra sounds when plugging in, powering on or off?
I know it sounds petty but I have my phone w/me at work and every time I plug it in to charge it plays that "Charging enabled" voice over. Can this be shut off? I SO SO SO love this Rom so far!! I have flashed quite a few and this one is my favorite so far!
TIA for any ideas.
No it cant be shut off...part of the doctors programming...you can tirn the volume down
Sent from my SAMSUNG-SGH-I997 using XDA App

[Q] ICS builds and battery life.

Why is that all the ICS builds that I have tried burn through the battery VERY fast? Am I installing them right? I follow the directions to the letter.
have u let the roms settle? by this i mean going through at least 3 charge cycles without a reboot, before judging battery life? if u haven't done this then u can't really judge until u do
So theres a settling in period? I didnt know that.
yup, 3 full charge cyclss is the generally accepted rule. If u just flash and use, i guarantee ur gettin crap life. The rom needs to configure battery based an ur usage basically
icenight89 said:
yup, 3 full charge cyclss is the generally accepted rule. If u just flash and use, i guarantee ur gettin crap life. The rom needs to configure battery based an ur usage basically
Click to expand...
Click to collapse
So by 3 cycles is charge to 100% then drain to 0?
Sent from my SAMSUNG-SGH-I727 using XDA
yessir, that is correct
I had a problem installing SKY-ICS where when I clicked camera or gallery it would say "Media Scanner Running" and then close. This sucked because I couldn't use the camera and it would leave a service open Media Storage. That service would drain all my battery and heat up the phone until I did a force stop. I don't really believe you would need to do 3 full cycles, just check your battery usage under settings and see what is eating the most battery.
I had the same media scanner issue. Tried 4 different ICS Roms over a week with similar results. I was burning about 25% / hour, so I had plenty of opportunity to run through full cycles. Couldn't get MS to shut off. Finally bailed and went back to stock unrooted today. MS hasn't been over 2% since. I really like ICS, but like my battery more.
icenight89 said:
yessir, that is correct
Click to expand...
Click to collapse
Makes sense because on gb I didn't flash a rom for a month and it was amazing battery life lol
Sent from my SAMSUNG-SGH-I727 using XDA
soda0289 said:
I had a problem installing SKY-ICS where when I clicked camera or gallery it would say "Media Scanner Running" and then close. This sucked because I couldn't use the camera and it would leave a service open Media Storage. That service would drain all my battery and heat up the phone until I did a force stop. I don't really believe you would need to do 3 full cycles, just check your battery usage under settings and see what is eating the most battery.
Click to expand...
Click to collapse
sorry this is wrong, ask any dev and they will all say the same thing. After a fresh install rom needs time to calibrate battery
Altarocks said:
I had the same media scanner issue. Tried 4 different ICS Roms over a week with similar results. I was burning about 25% / hour, so I had plenty of opportunity to run through full cycles. Couldn't get MS to shut off. Finally bailed and went back to stock unrooted today. MS hasn't been over 2% since. I really like ICS, but like my battery more.
Click to expand...
Click to collapse
this is an entirely different issue, but a known one,. fix is to wipe emmc and restore bit by bit
icenight89 said:
this is an entirely different issue, but a known one,. fix is to wipe emmc and restore bit by bit
Click to expand...
Click to collapse
I tried. I slowly added apps back one by one, and never restored data. Formatted ext. SD, moved files from internal, etc. Thought I had it fixed once after changing email from push to an interval. Media server immediately stopped running, but started again a few minutes later.
I think I've devoted 2-1/2 days of the last 7 to wiping, flashing, and restoring. Finally had to cry uncle before I get fired. I'm sure someone here can make it work, but it's got me beaten. I'd feel a lot better if I at least knew what was making media scanner run.
Awesome battery life so far with sky ICS
Sent from my SAMSUNG-SGH-I727 using xda premium
Altarocks said:
I tried. I slowly added apps back one by one, and never restored data. Formatted ext. SD, moved files from internal, etc. Thought I had it fixed once after changing email from push to an interval. Media server immediately stopped running, but started again a few minutes later.
I think I've devoted 2-1/2 days of the last 7 to wiping, flashing, and restoring. Finally had to cry uncle before I get fired. I'm sure someone here can make it work, but it's got me beaten. I'd feel a lot better if I at least knew what was making media scanner run.
Click to expand...
Click to collapse
sounds like u didn't fully wipe emmc, just move files from it. Since u tried everything else, humour me. Backup both onto computer then thoroughy format emmc and external sd in cwm. Mount usb storage and copy over sky ics 4.1. Flash it. Download some apps from xda and market and monitor for a few hours.
icenight89 said:
sorry this is wrong, ask any dev and they will all say the same thing. After a fresh install rom needs time to calibrate battery
Click to expand...
Click to collapse
I'm sorry I'm a noob this is my 4th post. I thought you only had to calibrate battery to get accurate battery statistics, like time remaining and percentage, not longer life.
Sent from my SAMSUNG-SGH-I727 using xda premium
Should I wipe battery stats then go through the cycle?
Sent from my SAMSUNG-SGH-I727 using XDA
icenight89 said:
this is an entirely different issue, but a known one,. fix is to wipe emmc and restore bit by bit
Click to expand...
Click to collapse
Thank you that was my exact problem.
Kenneth.Torres said:
Should I wipe battery stats then go through the cycle?
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
wipe battery stats in cwm does nothing, its a myth bud. Just charge to 100% and drain to 10% or less before next charge, try yo do it without a reboot. Reboot after 3/or 4 and u should be golden
soda0289 said:
Thank you that was my exact problem.
Click to expand...
Click to collapse
read my post before this one, it should solve your problem, i hope lol
icenight89 said:
wipe battery stats in cwm does nothing, its a myth bud. Just charge to 100% and drain to 10% or less before next charge, try yo do it without a reboot. Reboot after 3/or 4 and u should be golden
read my post before this one, it should solve your problem, i hope lol
Click to expand...
Click to collapse
Thanks man, also I've always wondered if undclocking to about 1.2 ghz would help save battery?
Sent from my SAMSUNG-SGH-I727 using XDA
yup, im running at 1188, but make sure u turn in force gpu rendering under settings > developer, that wil keep things smooth
Don't ever drain a lithium ion battery to 0%. Never go lower than 15%.
It damages the cells.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

Is waiting 5 minutes after installing rom necessary?

On a few developments threads they seems to recommended to wait 5 minutes without doing anything after installing a rom. Why exactly? Is it necessary?
If you're on rom that's on nightly status should you do this 5 minute wait each time you install a new revision even if you don't wipe data?
I've never waited 5 minutes and my phone works flawlessly.
That's a new one for me, you sure you didn't misread them saying it may take 5 minutes to load on first boot?
Kreeker said:
On a few developments threads it seems to recommended to wait 5 minutes without doing anything after installing a rom. Why exactly? Is it necessary?
If you're on rom that's on nightly status should you do this 5 minute wait each time you install a new revision even if you don't wipe data?
Click to expand...
Click to collapse
Some people feel it's better to let the kernel settle in, I've never been patient enough to wait
Sent from my SCH-I535
nyjumpman said:
Some people feel it's better to let the kernel settle in
Click to expand...
Click to collapse
This is ridiculous and nothing but snake oil.
There's no real reason you should wait, and if you have to wait, obviously something is wrong with the ROM in question.
That's a new one on me. What would be the point?
silver1882 said:
That's a new one on me. What would be the point?
Click to expand...
Click to collapse
Mostly unnecessary for devices with the amount of RAM this has, but it was common on older devices to lose setup files still in ram because the user started doing stuff right away.
Here one thread: http://forum.xda-developers.com/showthread.php?t=1880502
I have also heard eschelon of the synergy team recommend waiting 5 minutes as well.
I heard that you have to wait 5 minutes with the phone facing south (only on Tuesdays, if it's any other day you face west), and you also have to wave your arms around while it's installing. Plus wipe battery stats after.
Sent from my SCH-I535 using Tapatalk 2
I think they just say that because the phone is doing a lot of stuff in that first 5 mins after a flash. Newer users might start trying to sync their FB calendar or install 23 widgets and cause the phone to freeze up, which consequently leads to them posting in the ROM thread saying "doesn't work - froze up" etc...
The OP is referring to the new JB TW ROM. The dev said to do that. Guess what? I didn't
Don't worry about it OP, just realize your phone is going 100 miles/hr in that first boot after an install.
Sent from my SGH-I535 using Tapatalk 2
Thanks, I was curious about the 5 minute wait as well.
It's for safety sake. But no it's not required and anyways who tells you otherwise is clueless.
Sent from my SCH-I535 using xda premium
Personally i never done that nor have i even heard/read of that on any roms. But if the instructions in a rom says to do it, ima do it.
Sent from my SCH-I535 using xda app-developers app
Part of the process of elimination when you're trying to figure out what went wrong after installing a rom. Then feel like a dumbass when that's all you had to do.
From my Paranoid SGS3 on Verizon's unlocked booty.
try running a logcat durring first boot, then you will understand..
and yes, its a tradition from the G1 days.....
Whenever I'm on my first boot from a ROM flash I just walk away for 10 min. I know it's going to take a while to boot and load the dalvik cache. And i know after boot up it has a bit to do which usually makes it a little slower at first. I have a phone and a tablet. So while one is doing its thing I can just use the other to kill time. I don't mind waiting to get the smoothest experience.
--Sent from GlaDos baked potato
I follow the instructions the ROM provides. Some may say it's not necessary but it doesn't hurt to following the instructions to get the ROM running right on your phone. It's your phone so do what you think it's best.
Also make sure to wipe three times. /s
Sent from my SCH-I535 using Tapatalk 2
sounds crazy to me..
Droosh said:
Also make sure to wipe three times. /s
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
...but if you shake it more than three times you're playing with it.

Categories

Resources