yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Droid_ALM2ND:
I reverted back to Froyo. Not because I was scared of bricking, I just didn't want a replacement because I haven't met a Tbolt kernel my phone couldn't handle.

BUT... I came back to GB. I have no issues getting replacements and I have a Droid Incredible for backup. If I end up bricking I'll let you know.
[Thunderbolt Android Development] :
Yes I have noticed on

1.6.3 froyo was getting avg of 260 memory being free

gb 2.0 remix was getting avg of 175 memory free

Was oc at 1.4 as well

:rolleyes:

Cheers,
[Thunderbolt Android Development] KDKobes:
It's all quite troubling, but in

MY OPINION

I feel that it is an undervolting/overclocking issue combined with usage. Been running Gingersense since it was released and been messing with different things. When running the phone for a while and allowing a bunch of stuff to run it drops the memory so low that I believe it would force a reboot to free it up. Screen freezes, for me anyway, seem to occur if I let a large amount run when the screen is off (most likely due to the undervolting) and wouldn't turn on unless I do a battery pull. Since leaving the overclock adjusted at 1024 I haven't had a single reboot. Undervolting on the other hand seems OK at 245, but will give me screen freezes on the occasion if something too large is running in the background; for instance if I let beautiful widgets live wallpaper run with cpu hog on I get screen freezes when the screen is off which requires me to pull the battery to restart. By turning it off the screen freezes stop occuring, so essentially 245 is quite possibly too low of a number to run with depending on each persons usage. Obviously requires more testing and this is all based on MY PERSONAL EXPERIENCE WITH THE CURRENT ROM I AM USING SO FAR. FYI I have been using Advanced Task Manager to watch my memory levels and kill useless tasks when the screen turns off. (beautiful widgets is allowed to run along with select other items)

**THIS DOES NOT MEAN ANYTHING IS SAFE, THIS IS ALL BASED OFF MY ASSUMPTION**
[Thunderbolt Android Development] Dstu03:
Sorta agree with you I also think that it is linked to overheating and battery reading errors but we will see
[Thunderbolt Android Development] sublimaze:
You're lucky to have a phone with high tolerances, which is all the more reason to be conservative & not take any chances. A replacement Tbolt may not handle OC/UV like your current one
[Thunderbolt Android Development] onyx_64:
Got what you are saying.. But I want to correct a small thing here: Many ppl are under the assumption that undervolting meant running at a low frequency. That is not entirely true. Voltage will definitely reduce as u move to lower frequency slots, but what Undervolting really means, in this context, is that we are lowering the voltage down even further so that almost all the frequency slots run at a lower voltage than the stock voltage at those slots. eg: if 245Mhz has 0.95V at stock, thats not undervolting. It is when you run 245MHz at 0.90V, that you undervolt.
[Thunderbolt Android Development] KDKobes:
correct which you are referring to are the difference between undervolting and underclocking essentially. undervolting wont damage the cpu but will cause freezing. what i feel is going on is when running gingerbread it cant handle the higher overclock that people might be pushing, along with the high usage of the device its frying it.
[Thunderbolt Android Development] Droid_ALM2ND:
Sigh..... Now you're making me wanna go back to froyo lol. That's the only thing thats bothers me. I would hate to get a replacement that can't handle OC/UV like this one.
[Thunderbolt Android Development] drozek:
GB kernel

I think it has to do with the battery I was using wireless tether this evening, battery was low, so i plugged into the wall. And now when I boot to gintertis it shuts down after startup.

Well now it is back up and charging uptime is at 4 mins so glad I didn't brick it. But Kernel has some battery charging or staying on issues.
[Thunderbolt Android Development] joshnichols189:
Same here.. and during the initial scare I flashed CM7 and everything works hahaha settings just stick and 4G pops in and out but for the most part sticks.. themes stick.. etc :P
[Thunderbolt Android Development] JWMayes:
Ehh, I was running BamfGB until the scare, and went back to froyo, but I can't handle it anymore, back to GB I go.
[Thunderbolt Android Development] jaymccoubrey:
I'll send u my phone when it bricks.
[Thunderbolt Android Development] usafle:
Well not that my little bit of info really matters. But I'm running G.B. and I have the CPU set to 245 / 1.4 with the interactiveX govenor.

I've never had a "spontaneous" reboot at all with the phone since day one. Just to be safe, I put the CPU back on "stock" settings though after reading through here.

I've also noticed that the GB consumes A LOT more memory then the Froyo did. On boot, I've only got around 111MB free. I use task killer and get the memory up to around 230-250 free. I've noticed in taskiller I've got a process in there that has a "google icon" and it says "Loading, this can take a few minutes". Don't know what it is, or what it does but it is there every time I reboot the phone. I can safely kill the task and it never shows back up again.

I leave my phone plugged in and on all the time with the clock "desktop" running while I am sleeping. I've flashed GB and have been running it since last week. I've shut my phone off and on multiple times (due to Google Voice not being able to send a message out for whatever reason) and haven't had any issue.

Anything that you need me to dump from the phone to see if mine is any different? Not sure what kind of help I can offer.

But, I can say this, I AM DAMN NERVOUS NOW with all this "bricking" talk.
[Thunderbolt Android Development] onyx_64:
exactly.. was trying to explain the difference between undervolting and underclocking. Guess you already knew the diffference. :)
[Thunderbolt Android Development] chucklehead:
I'm not particularly interested in OC/UV. Are people bricking or experiencing these issues when just running stock?

I was running BAMF 2.0.5 with the included kernel and wasn't having any issues to speak of. Moderate to heavy usage with no issues.

Everything seemed to work perfectly as far as I could tell. I've since reverted back to Froyo, as I have no desire to risk bricking, but would love to go back to GB.
[Thunderbolt Android Development] ERIFNOMI:
When I was on GB I had that appear instead of the stock launcher. I use ADW so after it installed and I hit home a pop-up appears asking which action to perform and from there I set ADW to be default. The other option was exactly as you described though. So, if you use a 3rd party launcher I would say you were killing the stock launcher and it was never being loaded back into memory so you never saw it again.

Or it was something entirely different, just trying to help.
[Thunderbolt Android Development] MrKleen1:
I had no choice but to go back to Gingerbread. Bamf 2.0-5 was so much better than Froyo I couldn't take it. The battery life is so horrible on 1.6.3 I just couldn't take it anymore. As soon as I got 2.0-5 back up and running earlier I couldn't believe how much better it was... wow what a difference. Now I can leave the radio on all day instead of having to shut it off to keep the battery from free falling.

Obviously I would rather run the risk of a brick than have to continue with sub par software.
[Thunderbolt Android Development] Jlluna87:
TBH, I've honestly experience more random reboots reverting back to Froyo from GB. Before reverting back, I had no problems what so ever. So I'm about to switch back to GB. Although one issue I've noticed when going back to froyo is that I can no longer see my device in ADB when using CMD. anyone else having this issue?
[Thunderbolt Android Development] jhr:
ok, after flashing back and forth from one GB rom to another including CM7 (since a new one is released), I finnally got the continous reboots.

I stood solid running on Das BAMF 2.0-4.01 for a week,never did I update to 2.0-5, until tonight. I do not want to point at no fingers, but as soon as i restored 2.0-4.01 and while still in revovery i went ahead and flashed over 2.0-5. THEN BAM

Then when i was browsing the web it reseted itself, twice. Then as i type this i went pulled the battery and got the micro sd in a reader on a computer got the froyo radio, or so I thought it was the ginger radio and flashed it under hboot.

As I realized that I went ahead and reboot in recovery, wiped data, wiped cache and wiped dalvik in that order three times.

then restored das bamf remix 1.6. then when in recovery i select reboot now, then i pulled battery out along with micro sd.

found froyo radio put that on root of sd card and put it all back together. Pressed power and volume down and in hboot went ahead and flashed froyo radio.

after it was done select power to reboot.

I am going to plug in to PC and get ADB running and look for that command. Not sure if this will help any but this reboots is something I never had until I flashed BAMF 2.0-5

Again not to point at no fingers this is just my experience. I am still at DAS BAMF 1.6 remix and no reboot. with the leaked .7 cdma/ old LTE combo.

ok its fifteen minutes now and my phone has not rebooted at all. I can post later what roms and what order and when kids and wife fall asleep will put in ADB and run test so far froyo is working and no reboots
[Thunderbolt Android Development] joshnichols189:
If you recovered the phone it's not the same thing..
[Thunderbolt Android Development] jaymccoubrey:
I went back just to fry my phone. Boredom sucks.
[Thunderbolt Android Development] quepaso:
If you could fix your problem, then its not the same issue. The issue being discussed is unrecoverable.
[Thunderbolt Android Development] 52brandon:
back when I was on the D1, a "bricked" phone was simply one that somebody hadn't figured out how to fix. Never saw one that was 100% unrecoverable. So I think his sharing what brought his phone back is relevant to this. Following those steps MAY fix other "bricked" phones
[Thunderbolt Android Development] corenojoe:
The word "bricked" itself implies that it is unrecoverable (meaning your phone is as useless as a brick). If it didn't reboot while in recovery and he was able to get it working again then it wasn't the problem that this thread was made to discuss and therefore it is not relevant whatsoever.

Don't me to flame you guys too bad and I'm not trying to be a ****, but ppl need to understand the reboot issue is much more serious than just going into recovery and doing some steps to fix it. That's why its a big deal.

Hope its figured out soon, miss me some GB.
[Thunderbolt Android Development] itsDollar:
GB reboots several times before it settles it seems. The first time I ran it I didn't get that but when I flashed again Friday night same thing happened to me but after the 5th one it settled and I haven't had anymore. I thought I read somewhere that it's a kernel issue for now.
[Thunderbolt Android Development] thewebsiteisdown:
Wrong thread case. I was high that's all lol. It fixes the reboot issues with a stock not touched but by htc and verizon ROM, not related to this issue at all, my bad. :p
[Thunderbolt Android Development] thewebsiteisdown:
i'm back on GB now on my thunderbolt, mine shuts it self down one time the first boot after a install not all the time. Then when I turn it back on, it's fine.. It did this the last time i flashed and this time. Two different kernels too mind you now. The last time I flashed this ROM, i was using an older at the time new, kernel by imo.
[Thunderbolt Android Development] KDKobes:
I think this is happening because at startup (especially after install) too many processes are running essentially forcing a reboot to free memory until the phone sets up and settles.....as far as the kernel causing the issue I think its still releated to the overclocking/low memory on device not the kernel itself.
[Thunderbolt Android Development] thewebsiteisdown:
Not all the time mind you just after an install, first boot.
[Thunderbolt Android Development] KDKobes:
Again I think this depends on the ROM you are using, what overclock you are running and how much usage on the device also relating to if you are using a task manager also. What I am trying to say is each rom comes with different overclock speeds some higher than others and some lower. Depending on a persons usage, lets say they dont have a task manager to kill tasks and you are on the phone running a bunch of applications and then the memory gets really low its going to force a reboot to clear the memory. Now if this were to happen over and over without change then you are going to eventually fry it which would explain why it wont stay booted for more than a few seconds. I hope this helps explain

MY THEORY

a little better. And again some phones can handle more than others.
[Thunderbolt Android Development] jhr:
Remember this is not my first time installing a GB rom. I never had the reboots the one that you get with data on 1x, reboots then 3g and reboots etc. I had reaped several times times my backup. But once I restored it and at the same time flashed the latest and greatest over it without wiping data since its the same rom higher version.that is when I got the reboots. Well after I settle some some things here on my day off I will just fresh install 2.0-5 without my 2.0-4.1 backup and see what happens maybe since I flashed the netflix patch on old rom and new one had it cooked in, maybe. Well tune in for more as currently I am still on froyo and just woke up
[Thunderbolt Android Development] darkuni:
I don't profess to knowing a damn thing .. jcase says we're all on thin ice; and I believe him (thanks for everything you do man) - and I'm good with taking that risk. Hopefully, if and when it bricks, my thunderbolt will be able to divulge some helpful information. I'm insured - so I'm not concerned.

THAT being said ...

It seems that everyone that gets bricked is using the browser when it happens. At least, all the cases I've read about say "I was browsing and things got really slow ..." and it goes on from there.

I don't use the web browser - hardly at all - I use Tapatalk or dedicated applications to access web content (for whatever that is worth).

I know some roms allow for "more than default" windows open in the browser. Could this modification be contributing? Is everyone that got bricked using the stock browser? A third party browser?

I develop software for a living - and bug squashing is all about pattern recognition. No one else seems to have mentioned this - so I'm throwing it out there.

I went back to CM7 for a short period of time in panic mode - but honestly? I'd rather brick my phone and get a new one than deal with non-GB anymore. I've become a spoiled brat Generation Gimmie. ;)
[Thunderbolt Android Development] jhr:
Why cuz I did not wait for it to brick, the reboots was the beginning and was caught early enough. Don't worry I am flashing back and try to repeat what happened and also start a fresh instal versus flashing over from a backup
[Thunderbolt Android Development] joshnichols189:
I appreciate your input, we all do but the nature of these bricks is that there are no signs.. you can't "catch it early enough" because they just spontaneously happen. And being that it's called a 'brick' it is unrecoverable.
[Thunderbolt Android Development] thewebsiteisdown:
My wifes phoneis is brand new and still stock and she's having weird issues with hers again out of no where after I thought I had it fixed with a factory reset by the word of HTC.. We're going to try returning it for another one and see how the new one acts.
[Thunderbolt Android Development] theryanguy:
I feel you on that. I'm trying to figure out if my wallet can afford this boredom. I'm not scared, just cheap.

Sent from my super duper deluxe rooted re-romed Thunderbolt. ( and yes, it can also wash my car AND do the dishes)
[Thunderbolt Android Development] rafaelvelasquez2:
My wifes phone is tripping too. Rebooting, unresponsive touchscreen , making random calls . And this is the one Verizon sent us after the first one had rebooting issues. We got another one the way needless to say, it should be here Tuesday.
[Thunderbolt Android Development] Immolate:
Perhaps only wives phones are having the problem? Fascinating...

/pondering imponderables
[Thunderbolt Android Development] techspecs:
Throw that on the is/ is not chart... Wow, this issue just keeps getting more complex. :)
[Thunderbolt Android Development] djkeller3:
On everything root, I am not a frontiersman. I am not a developer. I'm just a layman who bought an OG Droid a couple of years ago, rooted and ROMed it, and became a phone geek or sorts, but still very much a layman.

That said, I prefer squeezing all the speed I can from my devices, which include the OG Droid, Incredible, and now TB. I almost always boot my devices at full-speed in Performance mode, all the time, max and min. My OG would occasionally overheat at any clock speed and bootloop, though never anything I couldn't get out of. My Incredible could handle an over-clock up to 1.2Ghz, and I ran it that way day in and day out. My TB is stable up to 1.6Ghz, but I keep it over-clocked at 1.4 max and min and only get an occasional reboot, never a loop. With the exception of the OG, I've never had a problem with overheating, AND I NEVER USE A TASK KILLER. I don't believe in task killers with our Linux base, and especially with how GB works.

In conclusion, I'm not sure that *safe* over-clocking has had much to do with bricking. My experience certainly may not be indicative of most, but I'm thinking that if over-clocking is to blame, it is the likely result of clocking beyond the stable range and then keeping it there assuming it will smooth out, but instead your CPU gets fried.
[Thunderbolt Android Development] jmin9012:
I was using Gingeritis a week back when I noticed that my battery did not fully charge even after 8 hours of being on the charger. Stock kernal, so my thunderbolt wasn't overclocked at all, and I even reset the phone prior to charging to ensure no unwanted apps were running in the background.

My fix was flashing over the MR1/OTA update, and I got amazing battery life and the battery went back to being normal. However, I have a unknown hatred for Sense, so I am thinking of going back ginger with Gingeritis IX. I will report back with how the battery life is.

Hoping I don't get bricked!
[Thunderbolt Android Development] patdroid1:
if you hate sense why not go to CM7??? all gingerbread, no sense, and no risk of bricking
[Thunderbolt Android Development] jbdavies:
Soooo... still think this?

HTC Unlocking Bootloaders

Verizon WILL ALLOW Unlocked Bootloaders
[Thunderbolt Android Development] Archangel:
even so where are all the bricked phones? I have heard of like maybe ten. I would submit that you get that with any new rom,,,there will be ten bricked phones dealing with careless flashing???
[Thunderbolt Android Development] Dstu03:
Who knows why they brick. Mine bootlooped and bricked. I'm back on froyo, its an alpha release if you brick point the finger at your self. Personally gb isn't all that much better and definatly not worth a brick.

Also to the dumbass that blamed jcase who forced you to root your phone and also who taught you how to read cause they failed you
[Thunderbolt Android Development] Dstu03:
Roms don't brick phones and I think most devs would challenge you that their Roms cause at least 10 bricks
[Thunderbolt Android Development] patdroid1:
If you have a working phone then YOU DID NOT BRICK...there is a reason why they call it a brick. i'm not trying to be a smartass, it just doesn't help jcase and adrynalyne to say you bricked when it was a bad flash or bootloop or whatever. i've bootlooped a hundred times...it's not a big deal...and it's certainly NOT A BRICK. sorry man not picking on you but people keep talking about how they bricked their phone and then flashed back to froyo...that's not even close to a brick
[Thunderbolt Android Development] Archangel:
obviously you did not read what I wrote I said that there are some bricked phones due to careless flashing how you got that I was saying roms bricked phones is beyond me LOL but ok
[Thunderbolt Android Development] Dstu03:
How do you flash carelessly there's one way to flash if you screw it up you should play in traffic.
[Thunderbolt Android Development] Dstu03:
Oh I didn't brick is that why I had to go get a new phone,good thing I had insurance
[Thunderbolt Android Development] Archangel:
Dude c'mon now your debating this really LOL There is so many things you could do with bad radio versions and trying to flash through cwm when you should through fastboot that could screw up your phone,,,, prob not brick but def cause problems,, what you have to remember is that with HTC style phones you have to sometimes flash a new radio and some newer users get that confused with flashing through cwm instead of fastboot, can def cause problems and some think they are bricked.

dont worry dude, your good thanks for writing
[Thunderbolt Android Development] Dstu03:
And all my point was is that its not all that common to brick BUT that it can happen. And if you think that its some how user related your absolutely wrong.
[Thunderbolt Android Development] Archangel:
Gotcha LOL thanks
[Thunderbolt Android Development] bigdaddy rob:
With all the warnings about not to load GB on the phone, I still see so many people upgrading to GB. I've also noticed that devs are putting out new or updated versions of GB.

So does that mean, it's ok to install the newer version of GB (ex. Gingeritis IX)?

Sorry for the stupid question. Just got back from vacation and haven't been on the computer for 3 days.

Thanks
[Thunderbolt Android Development] corenojoe:
Bricks are sometimes due to bad leaks or something similar. However, they are much more often a result of user error, whether it be not following directions or simply not knowing what they are doing.
[Thunderbolt Android Development] Immolate:
Nothing has changed really, other than a general realization that the bricking issue isn't about to turn into an epidemic. I think people who root and ROM are a hardy sort, and not usually risk averse. If they were, they'd be stock right?
[Thunderbolt Android Development] Dstu03:
Yes I agree
[Thunderbolt Android Development] tazman19:
With all the talk of overheating, what is a dangerous temperature for the phone? It's about 90 out today an playing with my phone outside it got up to 46 c or 114 f.
[Thunderbolt Android Development] azturbomini:
Just my 2 cents...IMO that is pretty hot. I have never gone over 109f and would shut my phone off or pull the battery if it got as hot as yours did.

Shot from my BAMFing Gingerbreaded (Rom "O" Death) T-Bolt
[Thunderbolt Android Development] distortedloop:
I don't recall the temp, but I do recall my Thunderbolt popping up an overheat warning once.

Check your battery stats where it gives the health indicator, if you're to hot that should say overheat.
[Thunderbolt Android Development] funkybside:
I just saw 47C, was charging in a car dock while playing pandora, full brightness. About 90F outside but was rocking a/c in car on full. Didn't reboot, but I pulled the charger to be safe.
[Thunderbolt Android Development] jaysckap:
I was on the beach today and was at 119f the whole time about 4 hours

Sent from my ADR6400L running the Death ROM
[Thunderbolt Android Development] gsxraddict:
+1 we take that risk regardless of the disclaimers :)