Related
I was excited when I got this phone, everything was going cool and all that....
The battery is the worst thing I have ever seen. I've tried all the radios, got all the power tweaks applied, I get down to 75% battery on EDGE, only texting in less than 5 hours. WTF is this? Is this a joke? It's not even funny! And not to mention the unreliabilty of the phone. I plan to send an email to HTC and ATT to see if I can work out anything. Never buying a phone from HTC again.
I think it's your rom. I get through a full day on H no problem. Which roms have you tried?
Also it could be radio and what most likely is the signal strength. As weaker the signal, as more power required to compensate.
WAAAAHHHH! Don't buy a smart phone then.
I get a full days use. About 2 hours of music playing, signed into an IM client and do some msg and talking and still have 75% at the end of the day.
My guess that its your rom, but i am betting you didn't change the setting in HTC's task manager.
Go to Settings > system > Task manager and change the close action button actually close the buttom. The default action for WM task manager and HTC task manager is to minimize or hide the apps.
So let's say i open WMPlayer, Google Maps, Contacts, Text, Microsoft word. I hit the X, but if i don't change that setting, when i press the X, those programs are still running consuming battery and memory.
Try making sure no unneeded tasks are running and update your radio to 1.14.25.05, and Da_G's 6.5 rom and lets see how ya do next week.
PwnCakes193 said:
I was excited when I got this phone, everything was going cool and all that....
The battery is the worst thing I have ever seen. I've tried all the radios, got all the power tweaks applied, I get down to 75% battery on EDGE, only texting in less than 5 hours. WTF is this? Is this a joke? It's not even funny! And not to mention the unreliabilty of the phone. I plan to send an email to HTC and ATT to see if I can work out anything. Never buying a phone from HTC again.
Click to expand...
Click to collapse
Yo PwnCakes193..
I feel yur agony.. I used to experience shi tty battery life too.. My raphael can only sustained for like 5 hours.. without battery draining applications like music player even running..
However, Things took a turn when i flashed my raphael to the following rom and radio:
ROM Version: ROMeOS v1.95.4 WWE
Radio: 1.12.25.19 (With matching rilphone version)
It is so much better now !! I have calls and sms coming in while Garmin GPS is running for like an hour with battery dropping only 15% from 100% to 75%... !! And i **** u not.. And by the way.. my raphael's been with me for like 5 months now.. I'm loving it more each day..
Good luck and hav fun!
Too advanced for you?
PwnCakes193 said:
I was excited when I got this phone, everything was going cool and all that....
The battery is the worst thing I have ever seen. I've tried all the radios, got all the power tweaks applied, I get down to 75% battery on EDGE, only texting in less than 5 hours. WTF is this? Is this a joke? It's not even funny! And not to mention the unreliabilty of the phone. I plan to send an email to HTC and ATT to see if I can work out anything. Never buying a phone from HTC again.
Click to expand...
Click to collapse
Well go buy an iPhone and stop cluttering our forum. They are made for the mainstream trendy techno gadget people who cant solve their own problems, but still want to look cool and smart in public when they pull out their phone. Neither ATT or HTC is going to change their whole hardware because of your e-mail.
Do you even realize what youre saying? Do you listen to yourself when you talk? First off, anyone that knows how to use their phone, and sets up the correct ROM/RIL/Radio combination gets a full day charge off of it, sometimes even a couple days. Second, do you realize that is a small PC in your pocket, and youre complaining about battery life?? Have you ever used a laptop? You know that brand new laptops only get 2-3 hours of battery life right?
Really, go get a regular phone, HTC phones are not made for everyone, and apparently this one is too complicated for you.
I echo what's been said in above posts and would add as a suggestion only to try the new htc rom with the 1.14.xx radio both are the latest from htc. Boring I know, but very stable. Don't throw your device away without trying it. The custom roms can be frustrating as they can be unstable at times, but very fun to tweak and experiment with.It sounds like yourmore a user who wants stability over the rest. Go to htc site and search for latest rom, try that 1.14 radio and report back.
I use a 1800 mAh battery in my pro and I always charge everynight. Not a big deal. I also have prolly less than the 75% you reported at the same time, another not a big deal. "it is what it is" You can adapt or you can get a diff phone. I have an LG dumb phone my work supplies me for calls only, that battery lasts 2 weeks . LOL!!
wow, harsh words.
It's not like this complaint is an isolated one. There are other forums out there(AT&T, and Howard) that have the same observations about battery life. To say that it is a portable pc and that someone should be happy with 6-8 hours of battery life is pretty silly too. It is a smartphone, like the blackberry, like the treo, like the blackberry. And when people complained about the battery life of the Iphone, it's not like everyone said, deal with it. Apple released another firmware to try and remedy this. Blackberrys seem to go for a couple if not more days without charging with 3G, push email etc running, so why would this not be expected from the Fuze?
I own both the Tilt and the Fuze and find I can squeeze out about 3 days with push email, a bluetooth headset, about an hour or two a day of listening to music through the headset and 3G enabled. The Fuze is supposed to be the successor of the tilt, so wouldn't it be logical to think i should be able to do the same with this product? I have flashed several different roms and radios(with the rilphone.dll) and right now cannot get past 8 hours of usage on it. I thought it was the radio but I have tested it without a sim in it and get the same results. So either the battery is faulty, or it just stinks.
I am going through troubleshooting it right now, and based on some helpful hints on other forums, am trying to discharge the battery fully in hopes that it resets the battery guage.
I think helpful posts, like those that say try a new radio/rom are good ways to respond. Saying "go get an Iphone" or "this is a ppc, deal with the battery" are not helpful to people who search the forums for solutions.
Just my 2(maybe a lot more) cents
Reefermattness said:
Well go buy an iPhone and stop cluttering our forum. They are made for the mainstream trendy techno gadget people who cant solve their own problems, but still want to look cool and smart in public when they pull out their phone. Neither ATT or HTC is going to change their whole hardware because of your e-mail.
Do you even realize what youre saying? Do you listen to yourself when you talk? First off, anyone that knows how to use their phone, and sets up the correct ROM/RIL/Radio combination gets a full day charge off of it, sometimes even a couple days. Second, do you realize that is a small PC in your pocket, and youre complaining about battery life?? Have you ever used a laptop? You know that brand new laptops only get 2-3 hours of battery life right?
Really, go get a regular phone, HTC phones are not made for everyone, and apparently this one is too complicated for you.
Click to expand...
Click to collapse
Really? Listen a**hole, I know what I'm dealing with. I'm running the 21210 build of 6.5 that I cooked in Da_G's Kitchen with the .20M1 radio AND RIL. Yes, I know i'm being picky, but a phone should last at least a little while, no matter what. I get a full day charge, but just texting and no calling, on EDGE, I should easily be down to 85% in 24 hours. I know it's a small PC, but that is no excuse. I am a mainstream tech savvy person, and I mod/hack everything I own, use everything to it's full potential. I don't want an iPhone because its an overhyped and, in my opinion, horrible phone. I was never trying to look cool when I bought this phone. I even helped a few members out here when they bricked their phones, and I taught a few how to cook ROMs!
Next time think before you post, you troll.
baboola said:
I think it's your rom. I get through a full day on H no problem. Which roms have you tried?
Click to expand...
Click to collapse
I have tried almost all the ROMs, my favorite being At0mAng's, but he's gone now . I'm cooking my own 6.5 ROMs now
The Fuze is supposed to be the successor of the Tilt? I guess according to the order that ATT purchased their HTC phones, but probably not according to HTC...
The HTC Touch Pro is the successor of the Diamond. Just because ATT replaced the Tilt with the Fuze does not mean its the successor. Tmobile is calling the TP2 the "Wing 2" in America, does that mean it's the successor to the wing?? NO. If anything most hardcore HTC follower will agree the TP2 is the successor to the Tilt (kinda obvious isn't it?).
Regardless of what order they came in, or what phone its supposed to replace, the Fuze has a bigger processor, twice as much ram, and twice as high resolution LCD. Its hard to compare the 2 on battery life. My Tilt gets a faster GPS lock, and the battery lasts way longer, than the Fuze. Does that mean its better? NO.
If you're such a badass 'hacker' then you should obviously understand how much power the hardware in your device uses vs the size of the battery.
I'm the troll? You joined XDA a month ago....
If you have an honest question where you need help then please ask, and im sure someone will help you get MUCH better battery life! All i really meant by what i was saying before i got sidetracked, is that if you don't like your HTC products, or it doesn't fit your lifestyle like you thought it would, then take it back, and get something else. Just don't come into a HTC forum, and start badmouthing products, because that will get you nowhere, and you should have been expecting the answer you got.
I'm with leak73 on this one. I think this forum is great, but I do think there are too many people that jump on someone as soon as they say anything negative about this phone.
I bought this phone to make my life easier, to manage work and personal tasks on the same device. I thought this device was the one I had been waiting for.
I am also disappointed with the performance of the Raphael. And I don't think it should be asking too much to expect the device to work properly straight out of the box. Yes, I appreciate that this is a windows mobile device that has massive flexibility and can be customised, but those possibilites should be in addition to a stock device that does the basics properly.
I have had a number of issues with the phone - battery life, dailer issues, poor reception (and I know this can contribute to poor battery life, but why should it be so much worse than other devices I have used in the same areas?).
The members on this forum have helped me out a lot over the past few months (which I am very grateful for) tweaking and trying to get this phone to be what it should have been in the first place. And while I am now enjoying tweaking and customising my phone, I will never criticise anyone who points out the shameful fact that this device is virtually unusable without putting time and effort into sorting it out.
Reefermattness said:
If you're such a badass 'hacker' then you should obviously understand how much power the hardware in your device uses vs the size of the battery.
I'm the troll? You joined XDA a month ago....
Click to expand...
Click to collapse
Where'd you get badass? I just said I hacked/modded a lot of the things I owned.... I haven't gotten into the processing specs and all that stuff yet...
And since when does being a troll have to do with what time you joined? I have yet to troll on this forum, I have either asked questions, or have helped people who are having trouble....
jjjacksonjjj said:
I'm with leak73 on this one. I think this forum is great, but I do think there are too many people that jump on someone as soon as they say anything negative about this phone.
I bought this phone to make my life easier, to manage work and personal tasks on the same device. I thought this device was the one I had been waiting for.
I am also disappointed with the performance of the Raphael. And I don't think it should be asking too much to expect the device to work properly straight out of the box. Yes, I appreciate that this is a windows mobile device that has massive flexibility and can be customised, but those possibilites should be in addition to a stock device that does the basics properly.
I have had a number of issues with the phone - battery life, dailer issues, poor reception (and I know this can contribute to poor battery life, but why should it be so much worse than other devices I have used in the same areas?).
The members on this forum have helped me out a lot over the past few months (which I am very grateful for) tweaking and trying to get this phone to be what it should have been in the first place. And while I am now enjoying tweaking and customising my phone, I will never criticise anyone who points out the shameful fact that this device is virtually unusable without putting time and effort into sorting it out.
Click to expand...
Click to collapse
I hear that, I can relate as I've had my s**t jumped a few times on this forum as well and I always learned from it. I'm not an expert at all and thats the reason I come here to learn about my various wm devices, currently the touch pro. I undestand the issues especially with battery and stability.Except for battery I don't have any complaints that you mention. My RF which I value as a number 1 priority is very good. No dialer issues here either. I also think it would be nice to have perfectly operating devices right out of the box and considering what we pay for these things, it seems we should get better. In my experience all the wm devices I've ever had have had inadequate batteries. It's just the way it is. I did not expect my pro to be any diff. in that regard. I got it anyway and bought a better battery. In the past few weeks I've tried various 6.5 roms with differing results and none were very stable. It's the way it is and I don't really expect it to be better, but I love it anyway. I've used symbian s60 nokia devices and thought some of the e series have outstanding stability and battery life. So I have choices.
My choice is to continue learning and I'll get extended batteries when I think I need it. When I get tired of the wm BS I'll go back to E series for awhile.
For anyone who is calling themselves proficient in wm and the various ins and outs of flashing and obviously has some experience apparently, I find it kinda strange that they would be surprised by the battery life. Stability can be had from diff rom combos. But bad battery life is a given with wm. we get used to it and move on or go check out e series. It also rocks! Lotsa choices.
Maybe I am one of the unluck ones that have experienced more than my fair share of problems. I have had more issues than I mentioned in my last post - obviously the GPS problem, keyboard lag (although it seams to be fixed now with tweaking), dodgy call acceptance/ring delay (this seems sorted in the new HTC Rom), active sync issues (not sure if this is the software though) and the general lock up issues.
Don't get me wrong though when this device works it is everything I hoped for, I just wish it worked like that all (or at least most) of the time.
jjjacksonjjj said:
Maybe I am one of the unluck ones that have experienced more than my fair share of problems. I have had more issues than I mentioned in my last post - obviously the GPS problem, keyboard lag (although it seams to be fixed now with tweaking), dodgy call acceptance/ring delay (this seems sorted in the new HTC Rom), active sync issues (not sure if this is the software though) and the general lock up issues.
Don't get me wrong though when this device works it is everything I hoped for, I just wish it worked like that all (or at least most) of the time.
Click to expand...
Click to collapse
what tweaks did you apply to fix the keyboard lag?
wow, boys, calm down. *****ing at each other is oh so productive. maybe we could try to HELP each other out and be friends! just a thought...
i'm getting maybe 12 hours on a full charge running the leaked att stock rom and it's really starting to tick me off. i bought a portable power pack that can give me a full charge on its full charge (Xpal harry II) but i want to be able to get AT LEAST a full day without having to pop it onto a usb or wall charger for 20 minutes. im thinknig of flashing to da_g's or natf's 6.1 roms witihn the next couple weeks hoping that they'd be able to improve my battery life. i'm pretty happy with the radio and i'm in boston so no major signal issues there. maybe it's just a sh*tty rom draining my battery?
and now that i wasted 10 minutes reading this thread, i'm giong to go back to studying for finals. joy.
EDIT: I installed the fuzeberry theme a week or two ago and that's caused a TF3D problem (see my thread here about this here: http://forum.xda-developers.com/showthread.php?t=511760) but is there any chance that THIS is also killing my battery? hate the att manila but i might have to revert back if it gets me more hours :\
PwnCakes193 said:
what tweaks did you apply to fix the keyboard lag?
Click to expand...
Click to collapse
****, sorry mate I can't remember now, I changed a setting in the registry and installed a keyboardincrease cab? Maybe others on here will be able to point you in the right direction. I am a noob at this type of stuff really and just follow instructions that members on here suggest - once the problems fixed I forget about it.
nhshah7-
try using a 6.5 ROM I cooked now, it's doing fairly well, i would Hard-SPL, then try and flash a new radio or ROM, should help you out, turn off 3G, which should help. Also download advanceconfig and turn on the power saving items there.
FWIW, I have never had good results with the gps, but since I flashed the htc 5.05.401.1 with radio: 1.14.25.05 I now get very quick lock times. Also battery is a bit better even tho I'm running shell3.
After a bunch of ROMS with near Zero support for WiFi Calling/MMS, Im left with no choice but to go back to stock as TMO has no coverage in my community.
The closest I've gotten is by "RELOCKING" the bootloader and trying to load the latest stock rom, but I get this error;
Hboot version is older! Update Fail! Press <power> to reboot.
Any ideas?
You could always run Bulletproof, MikTouch, or Undeads Expresso. They are all based on stock (MikTouch is the latest and is basically stock). This will allow you to pull nandroids and back up your apps using the root required apps that are available. I don't remember the stock ROMs doing MMS over wifi but if they did those ROMs would do it too.
I have no advice for getting back to stock other than using the search fcn. Then again I don't see what the point is in going back when there are ROMs that do everything the stock one does and more.
Hastily spouted for your befuddlement
Warranty Return
I would like to know how to return to factory-delivered S-ON. I've read that many people return HTC phones S-Offed and unlocked and such, with no issue, but I still prefer to put it back to factory condition. I had a digitizer hardware failure completely unrelated to ROMs and I don't want to give them any reason to snub their noses at me.
I've gotten the phone back to a factory ROM but when I go into bootloader it says "*** RELOCKED ***" (kinda like, "we know what you did last summer"). Anyone know how to get back to the original locked state?
I'm currently S-ON, never S-Offed. Was rooted, and fastboot flashed my kernels and recovery flashed my ROMs, and to return to stock ROM I used the PG59IMG.ZIP from November 2011. The 1.55 one. It wouldn't let me do the 1.28 one.
cj chitwood said:
I would like to know how to return to factory-delivered S-ON. I've read that many people return HTC phones S-Offed and unlocked and such, with no issue, but I still prefer to put it back to factory condition. I had a digitizer hardware failure completely unrelated to ROMs and I don't want to give them any reason to snub their noses at me.
I've gotten the phone back to a factory ROM but when I go into bootloader it says "*** RELOCKED ***" (kinda like, "we know what you did last summer"). Anyone know how to get back to the original locked state?
I'm currently S-ON, never S-Offed. Was rooted, and fastboot flashed my kernels and recovery flashed my ROMs, and to return to stock ROM I used the PG59IMG.ZIP from November 2011. The 1.55 one. It wouldn't let me do the 1.28 one.
Click to expand...
Click to collapse
If you'll go to This Thread & scroll down to the HBoot section I have a link to the OTA HBoots that were sent by TMobile that match your build. Two of them look like they would probably match your issue (not positive which one). Both being OTA they have to be the signed ones and would most likely give you a "Locked" bootloader. Good Luck.
I thought I had an OTA, and flashing it returned me to stock build with stock apps and no root, but didn't return the bootloader to the factory state. I'll download one of these that matches and maybe have better luck?
Are these supposed to relock the bootloader?
Also, there is an "HTC Update" available when I go on wifi and check. I should avoid using that, right?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Turns out, there are three OTAs I found (I couldn't find your handle there specifically, but I found the OTA links) and I have the middle one. The kernel, the HBoot version, and the radio all match up byte for byte.
And just to be clear (I think you know what I'm doing, just making sure), going S-ON isn't what I need, as I never was S-OFF. I had the HTCDev-unlocked bootloader and upon relocking it, it says "Relocked" like a tattletale. Does T-Mo care if that's even on the phone as far as warranty goes?
From everything I heard, they couldn't care less since it was provided by HTC in the first place. I returned my last one with S-Off and all they did was check the little tattletail moisture dot. Had a new one in 3 days.
Yeah, I understood you were just looking to get a "locked" header again that's why I kinda figured the OTA HBoot would get you there. It did everyone that accidently took the OTA when they were already S-Off and they ended up Locked, S-On with the 1.45.xxx HBoot and had to do the wire trick to get back to where they were before. I DO think you're worrying about something you don't need to though.
Just flash a PG59IMG.zip via bootloader if you really want to unroot.
WeekendsR2Short said:
From everything I heard, they couldn't care less [...] I returned my last one with S-Off and all they did was check the little tattletail moisture dot. [...] It did everyone that accidently took the OTA when they were already S-Off and they ended up Locked, S-On with the 1.45.xxx HBoot and had to do the wire trick to get back to where they were before. I DO think you're worrying about something you don't need to though.
Click to expand...
Click to collapse
Okay, then I shall quit worrying about it. Thanks!
I'll go ahead and download the HTC update then, too, just to see what it does. Since I'm not keeping this particular phone anyway... Before I do, I'll say, I expect it not to go back to locked because if they're going to go through the trouble of making it tattle like that in the first place, they'll check for that particular tattle in the updates and not reset that part of it. But I could be wrong. Lemme OTA update this thing and see what happens! :highfive:
Thanks again!
-=-=-=-=-=-=-=-=-
Congratulations! My phone has been updated successfully to version 1.63.531.2 710RD. Sys Info says radio is 11.59.3504.00_11.16.3504.20_2. Seems to match the latest offering here.
Okay, let's reboot to bootloader and see what it says.
Nope, still "*** RELOCKED ***". Oh well, no biggie.
Those stinkers! LOL. You were right. I guess they're just not going to allow us the cover THOSE footprints. I sure do appreciate the feedback!
WeekendsR2Short said:
Those stinkers! LOL. You were right. I guess they're just not going to allow us the cover THOSE footprints. I sure do appreciate the feedback!
Click to expand...
Click to collapse
I figured this was coming. I've said for months that HTC is starting to adopt crApple's business model, and now they're starting to sell phones with no replaceable battery and no SD slot in addition to no hardware keyboard (the One series).
Sent from Spaceball One.
Yep. In my searching around here, someone was asking how it was done that e.g. Revolutionary and Juopunutbear were able to change their banners. If there were a tool or method for that, I'd consider it, but since HTC and T-Mo don't seem to care (and since I have a hardware issue and I never messed with anything that could have damaged that particular piece of hardware) I'm really no longer worried about it.
I've been on Google+ too much lately. I keep wanting to +1 the posts I agree with.
blackknightavalon said:
I figured this was coming. I've said for months that HTC is starting to adopt crApple's business model, and now they're starting to sell phones with no replaceable battery and no SD slot in addition to no hardware keyboard (the One series).
Sent from Spaceball One.
Click to expand...
Click to collapse
BOY! They're sure going to loose alot of support if they start adopting those ideas! And I'd not even heard about the "no replaceable battery" issue. That alone will cause me to jump ship considering the lousy battery they insist on using. I'm not about to buy one of those car batteries to hang off my belt so I can make phone calls in the afternoon PLUS I just don't trust a car charger after I cooked my CrackBerry on one.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
cj chitwood said:
Yep. In my searching around here, someone was asking how it was done that e.g. Revolutionary and Juopunutbear were able to change their banners. If there were a tool or method for that, I'd consider it, but since HTC and T-Mo don't seem to care (and since I have a hardware issue and I never messed with anything that could have damaged that particular piece of hardware) I'm really no longer worried about it.
I've been on Google+ too much lately. I keep wanting to +1 the posts I agree with.
Click to expand...
Click to collapse
This is just a guess on my part but I ASSUME that a person would have to decompile the code for that particulat HBoot then find the area that the graphics for the banner is contained in, then with a hex editor change the text that it displys then recompile it again. BUT.....I'm no programmer either.
WeekendsR2Short said:
BOY! They're sure going to loose alot of support if they start adopting those ideas! And I'd not even heard about the "no replaceable battery" issue. That alone will cause me to jump ship considering the lousy battery they insist on using. I'm not about to buy one of those car batteries to hang off my belt so I can make phone calls in the afternoon PLUS I just don't trust a car charger after I cooked my CrackBerry on one.
Click to expand...
Click to collapse
I didn't believe it until I had a coworker's brand-new One S in my hand. My first question was "how do you change the battery in this thing?" Then I looked it up and saw that you actually had to take the phone apart for that.
blackknightavalon said:
I didn't believe it until I had a coworker's brand-new One S in my hand. My first question was "how do you change the battery in this thing?" Then I looked it up and saw that you actually had to take the phone apart for that.
Click to expand...
Click to collapse
GEEZE! What are they afraid of? Someone will put one in that doesn't overheat the cpu & kill it prematurely?
blackknightavalon said:
I didn't believe it until I had a coworker's brand-new One S in my hand. My first question was "how do you change the battery in this thing?" Then I looked it up and saw that you actually had to take the phone apart for that.
Click to expand...
Click to collapse
The HTC EVO LTE is the same way with the battery. A buddy of mine got a brand new one when they came out and shortly later it hard bricked overnight on charge and was replaced with a refurb. So this is the crap we are gonna have to start dealing with from HTC.
Sent from my myTouch 4G Slide using Tapatalk 2
strapped365 said:
The HTC EVO LTE is the same way with the battery. A buddy of mine got a brand new one when they came out and shortly later it hard bricked overnight on charge and was replaced with a refurb. So this is the crap we are gonna have to start dealing with from HTC.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
"We" are not dealing with this. If Samsung keeps coming out with slider phones with high-end specs like the Relay I won't be dealing with HTC's bulls**t.
If this is the path that HTC has chosen for their future then they are well on their way to becoming the Hasbeen Telephone Corporation.
@BlackKnightAvalon: Fully agreed.
If I may go further OT for a moment here, this nonsense about hermetically sealing the phones together reminded me of shopping for the G1.
See, back then, I made a list of things I required in a phone. It was to be my first phone, one I would pay for myself (instead of using someone else's old hand-me-down they no longer were using). My now wife at the time had the old Sidekick LX, which while not a smartphone by today's standards opened my eyes to a realm of possibilities beyond handheld computers like the Palm and iPaqs. I had a personal cheapie freebie Nokia bar phone, and my work phone was the top of the line version of the same form factor. Then work provided me with a flip about the same time my wife upgraded from her flip to a Sidekick. So at the time, I had her flip, and it was more than I needed. But the work flip, being a motorola, was hackable, by design. I was able to put my own sounds, ringtones, bootup sequence graphics, all that into it. So I knew what I wanted.
My list included a few things:
Be Linux based or at least open source so I could hack it to suit my tastes (I was thinking more along the lines of theming)
Be GSM so I can swap SIMs when I need to (if another phone borks, and I want to loan them mine without giving out *my* number to everyone...)
have a qwerty keyboard and not just a number pad (I hadn't considered the possibility of a touchscreen keyboard)
have a camera
have a standard USB charging port
have Internet capability (back then this wasn't on every phone you could buy)
have wifi
GPS was a plus, but not a requisite
Bluetooth was a plus
And a whole slew of other things, but basically, the G1 satisfied that list and more.
Because of iPhone and now HTC practices, I'm now forced to add a few things to that list, and I'm not sure my next phone won't be a Samsung. I really hate the bluish hue of the AMOLEDs, but it may be worth it. Depending on whether Google can bring Motorola out of crapzone I might consider a moto. Anyway, the new list will include all of the old one, plus:
Removable battery of at least 1800mAH rating
PHYSICAL keyboard -- my MT4GS just proved the need for that, though admittedly if the screen wasn't a slider the cable inside might not have failed
PHYSICAL Call Start/Stop buttons a definite plus, almost a requirement
REMOVABLE media
Headphone jack
TV Out, whether HDMI (MHL/microUSB) or composite (headphone jack)
For that matter, digital TV OTA receive and low-power transmit
FM Radio receive, preferably transmit
HD Screen
1.5GHz+ dual+ core
Doodooflinger capable
2-meter and 70-cm Amateur Radio band capable, a definite plus (should be not too difficult to do methinks and would help for those times when I'm out of signal in the mountains). The 33- and 23-cm amateur bands should be easy enough to come into, at the very least.
Satellite TV dish aiming
Dishwasher autoloader
... ?
EDIT: Add Police scanner and aircraft band receive...
Clearly, I have raised the bar by which I will judge handset manufacturers.
I'm not joking about that amateur radio bit. That's some serious geek creds waitin' to happen right there.
But yeah, back on-topic, I think I'm okay with HTC / T-Mo knowing I rooted the phone, as long as they don't start holding software choices against me in the realm of hardware failure. After all, I know the difference, and nothing I've done with the software had any bearing on their hardware breaking down before designed lifespan is up.
Here's something to be sure NOT to include:
Genius button
.com/www. button
duplicated buttons from the faceplate on the slideout keyboard
similar stupidity
cj chitwood said:
[*]PHYSICAL keyboard -- my MT4GS just proved the need for that, though admittedly if the screen wasn't a slider the cable inside might not have failed
Click to expand...
Click to collapse
I'll risk a failed cable
( neither of my doubleshots have that problem - my original one has slid the keyboard in/out in the terminal command cycle so much words simply can't express the heightened level of wear it's suffered through...consider how much dev i've done on the device...)
Over a worthless, aggravating, real-estate stealing, non-feeling, spelling error making (chrome-dome, etc...etc... - enter tin-tin)
...
Seriously, my spelling and grammer have dropped significantly. I pretty much only type in landscape because portrait is just impossible.
I've gotten to the point where I just let some go through in defeat, simply because I have to edit EVERY OTHER WORD on this worthless S3.
The bigger screen is nice, but losing the feel of individual buttons pretty much guarantees what you intend to type is only a close approximation of what appears on the screen at the best of times.
From now on I am either going to have to figure out how to get one of my doubleshots back on service that reaches nowhere, usa like the verizon S3 does, or move on to some qwerty device "the network" can handle.
I mean, my professional image is being held hostage by a lack of proper hardware. Sometimes I may only have a minute, maybe two at the most to snap out a reply.
So either I send something that looks so unprofessional I might have been better off just not sending it and forging a reputation for being unreliable, or preserve the respect of those above me in my company as far as the grasp of language goes and embrace that horrid representation of myself as someone who couldn't be bothered to respond to someone who needed my response.
Seriously, I don't have time to turn on bluetooth and connect s keyboard, even if I could carry it on shift, and then deal with keeping it powered too on top of it.
I sure can't talk-to-text when talking about a client within earshot, amongst a variety of other situations where the information i'm conveying is confidential to the people around me
I'm really not liking losing the keyboard, it's literally and solely ruined my android experience by making me dislike to the point of _hate having to input textual data. Be it commands or communication I see having to do so as a chore, one I hate, one I can't stand and annoys the living .... outta me.
It makes trying to work on the device downright scary, if not the equivalent of playing russian roulette. When the result of spelling errors in your command can have disastrous results, 10 times out of 10 I abstain. So here I sit with a device i'm afraid to hack on because I know i'll miss catching something stupid and wreck it.
To be quite blunt - having to fix every other word, if not every word for the majority of all of this reply has taken gargantuan strength not to snap the phone in half on my steering wheel. If I wasn't nestled in the depth of a valley located in a state park miles from any kind of civilization, i've freakin had it with this and this just could've been that time.
This S3 owes nature big time.
I'll never own an android phone without a hardware keyboard again, and being required to have a smartphone for my job will see me end up rocking froyo or something if it comes to it.
Sorry for all the hate, but really passionate about this. The S3 has become my most hated and aggravating electronic device i've ever owned. I'll never get another like it.
Quick question.
I got a warranty exchange last week BUT, turns out the cursed headphone jack does not work on the "new" replacement plus the camera has a circular area where its a tint of red, not too noticeable tho. i want to return it to stock even with a relocked bootloader but i was wondering, since i have a backup of the stock rom (which is what im restoring to on nandroid right now), can i just relock the bootloader or do i have to flash the PG591IMG.zip?
Hope I'm posting this in the right place...
Had the Sensation for a little over a year now, and it's been a real eye-opening experience into the world of Android development. It's hard to imagine going back to stock, unrooted Android. Saying that, I'm one of those unlucky owners who got a Sensation which can't achieve higher overclocks without sacrificing major stability - anything above 1566MHz wouldn't run, and anything over Stock tends to overheat. On top of that, I also get random reboots and even more overheating when I don't have a piece of card or something to jam the battery into the connectors. I've also been venturing into the real world a bit more this year and found that even on full brightness it's not easy to see. Also, managing apps between SD card and internal memory can get tedious between flashing new ROMs due to the pitiful amount of storage...
Now that I've finished bashing my phone and the reasons I want to ditch it, what reasons do I have to stay? How many people are in my situation? Is it worth upgrading to a newer model? Am I asking too many questions one after another?
Basically, I'm thinking it's time for a change. I already know why it's a good idea, what reasons do you have for staying with your Sensation right now?
I never had any problems with overheating or overclocking on my Sensation XE, so maybe it's got something to do with your particular handset. I'm still loving my SXE, because of all the developer support and the continuously upgrades for the phone. Cache partition isn't really used since GB, so I just use it as swap partition for RAM. I don't like the three-button lay-out on newer HTC's (or two-button lay-out on HTC One).
If I were to get a new phone, I'd wait 'till the HTC One is upgraded (HTC usually releases an updated version of their flagship device after a few months) with a newer/faster cpu/gpu and better battery
PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
I am going to post what recently happened to my D850 G3 and see if anything similar has happened to others.
Now before I tell what happened to my phone, judging from the past posts I've made generally one of two things will occur.
1. Nearly all forum members who read it will ignore it and move on. (That's expected, if it didn't happen to them why respond?)
2. Those members (with the exception of the civil-mannered ones) who have post counts in the thousands will respond back with an inappropriate comment.
The civil-mannered ones usually always will respond with a suggestion or viewpoint which helps me understand the issue.
[This site is supposed to be about sharing knowledge and helping others, and I realize the "goober factor" does come into play at times.]
My phone got REALLY hot a couple of weeks ago and died. Sent it back to LG repair facility in Ft. Worth TX.
I got it back this last week and the tech stated on the paperwork that came with the repaired phone that the 32GB NAND flash memory chipset was replaced.
When I went online to see exactly where this chipset is located in the phone, it was the location where all the heat was coming from.
I am not a newcomer to computers and their associated hardware and I realize that smartphones are a different beast, so to speak. I've experienced and diagnosed hard drive failures, motherboard and DIMM RAM failures, CPU failures, CD/CD-R RW/DVD DVD-R/ failures, and so on. I have custom built over 50 computer for myself and customers, I have diagnosed and repaired close to 200 computers. All the previous in mostly the desktop format. Mobile phones and smartphones are in which I'm still in a big learning curve here.
What would cause the NAND ROM chipset to overheat like that? Could it be linked to using a custom ROM firmware? Could I have done something wrong?
Was it just hardware failure? I am extremely curious about this.
Anyone who has any constructive comments or suggestions are encouraged to share their opinions and/or views.
Many Thanks in Advance! :fingers-crossed:
Did you have a custom ROM installed on it? I would be surprised if LG covered you even if you had a custom ROM on it. I had the same problem as you once, and I returned it. No idea why my chip decided to fail though.
Likely simply just a case of random factory defect.
I would agree with shimbob, NAND overheating and failing before the processor doesn't follow the logical path of a custom ROM. For the NAND to overheat that would mean an insane amount of data calls and for that to happen the CPU/GPU has to be driving it. That should land up overheating the CPU/GPU first before the memory. What ROM were you running? Did you tinker with the any of the processor settings?
I don't think he'll answer, guys. He's not really asking for help or he would have provided the info you asked about in the first place. He's here to complain about how a genius such as himself could end up with a bad memory chip.
And to the OP (should he read this), that's what you had.
If it makes you feel any better, we felt just as bad as you when we read your post, which divides the world into three camps: the ignorant, the impolite, and those who help you over your little hurdles.
Very edifying.