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.
So I recently made the plunge and rooted my Nexus S. It was well worth the trouble. But maybe not for the reason most people might think.
Obviously, my aim was to try out different ROMs and get more power/battery life/functionality out of my phone. I agree on the functionality, but I have great doubts about the other two.
For the last week I've been testing Cynogenmod against Inf1nity against NSCollab and the results have been poor on most accounts.
Improved battery life:
Absolutely no way. My battery life has never been worse. No matter what I try, the battery drain is pretty bad. Not helped by the fact that in all three ROMs there are serious bugs which means auto-syncing even though it's switched off and constant notifications, even though they are all switched off. And that's just on the surface. System processes are going berserk on all three ROMs for no good reason at all.
Improved speed:
If there is, it's a bloody small one. In my opinion, it's quite the opposite. Maybe there's a performance improvement in certain areas, like gaming or audio. But in general the phone was prone to sluggish behaviour, no matter what settings were selected. Only Infinity felt snappy. In all cases you have to remove whatever non-stock launcher was on there and switch off many things.
The only thing you get from all of them is more functionality. But to be honest, I'm back on the stock 2.3.4, rooted and flashed the kernel and my phone is the snappiest it's ever been and so is the battery life. And there was no ROM in sight to get it there.
I'm new to this, so if I have been testing the wrong ROMs then please do point me in the right direction. If not, I'm just going to stick to my rooted phone and customize the parts I want when I have a need for it.
For some reason there is often a disparity between the experience that one individual has with a ROM, and that which another person may have. Even on the same make/model device and the same ROM, peoples 'luck' may be completely different. Perhaps it's the interaction of ROM + Apps installed, configuration, usage, variations at the silicon level...sheer luck...? Who knows?
My device hates Stock ROMs but excells with CM7, whereas others with the same device often have the opposite experience. That's why we're lucky to have a diverse dev culture and usually many options available to us. You just have to find one that fits.
Well, I'm not giving up, that's for sure The Nexus S compatible ROMs seem to be quite new, so I'm hoping future versions will show improvement.
In the meanwhile I have to applaud the community spirit and the work some people put in this. Just a pity it's not translating into results on my phone quite yet. I hope to see a real lean and fast ROM run on my phone soon.
just orderd my htc hd7s what can i expect? going to install mango as soon as i get it. how is the batter life? i get 8-12 hours on my infuse
Not sure about the HD7, but it's pretty dismal. Prepare to turn off push, limit your live tiles, turn the brightness down, turn off location, etc.
Probably not as bad as Androids, but not the best either.
sure haven't said:
Not sure about the HD7, but it's pretty dismal. Prepare to turn off push, limit your live tiles, turn the brightness down, turn off location, etc.
Probably not as bad as Androids, but not the best either.
Click to expand...
Click to collapse
hmm....i leave all of that running on my android and still get the 8-12 hours. might have to return the phone or get some extra batteries
I get about 32 hours out of a charge on my HD7. 2 email accounts, hotmail and gmail. Not really a real heavy user though, too busy doing work and other stuff.
I'm in the habit of charging it every night so it never runs out. My phone hasn't been off in about 2 months for any reason (unless you count resets for firmware flashes).
I am a heavy user of my HD7, 2 email accounts with push enabled lots of web browsing, reading on kindle and listening to music, it has never failed to get me through my 16 hour day, i charge it every night.
Not sure what heavy use means to you people. I'm a heavy user and there's no way in hell the HD7 can last 16 hours with that battery. Just not gonna happen.
HD7s is an AT&T phone. If you want a WP7 phone on AT&T then get the focus. The extra 0.3 inches is not worth getting the HD7s.
Good rule of thumb is don't buy any smartphone with less than a 1400 mAh battery unless it's a blackberry. Really high end devices, you prolly want at least 1600. On T-Mobile there wasn't a choice unless you wanted to buy from Dell, but that creates issues in cases when you get DOA and defective devices (have to ship back, get shipped a new one, etc. instead of just driving 10 minutes to a carrier store), so we had to deal with it. I don't recommend this phone. The battery is the primary reason, but aside from that this phone has the worse sound of all the WP7 launch devices.
N8ter said:
Not sure what heavy use means to you people. I'm a heavy user and there's no way in hell the HD7 can last 16 hours with that battery. Just not gonna happen.
HD7s is an AT&T phone. If you want a WP7 phone on AT&T then get the focus. The extra 0.3 inches is not worth getting the HD7s.
Good rule of thumb is don't buy any smartphone with less than a 1400 mAh battery unless it's a blackberry. Really high end devices, you prolly want at least 1600. On T-Mobile there wasn't a choice unless you wanted to buy from Dell, but that creates issues in cases when you get DOA and defective devices (have to ship back, get shipped a new one, etc. instead of just driving 10 minutes to a carrier store), so we had to deal with it. I don't recommend this phone. The battery is the primary reason, but aside from that this phone has the worse sound of all the WP7 launch devices.
Click to expand...
Click to collapse
Well, I also get 16 hours of use easily with my HD7s. Also, having previously owned a Focus, I much prefer the HD7s and I am having better success with battery life vs the Focus.
I'm not sure what you mean about the sound, but no issues on my end. The HD7s has a much better look and feel and reading text is much better than it was on the Focus. The SAMOLED may be great for movies, but it is sub par for reading text. HTC also provides much more useful OEM apps and add-ons than Samsung.
N8ter said:
Not sure what heavy use means to you people. I'm a heavy user and there's no way in hell the HD7 can last 16 hours with that battery. Just not gonna happen.
HD7s is an AT&T phone. If you want a WP7 phone on AT&T then get the focus. The extra 0.3 inches is not worth getting the HD7s.
Good rule of thumb is don't buy any smartphone with less than a 1400 mAh battery unless it's a blackberry. Really high end devices, you prolly want at least 1600. On T-Mobile there wasn't a choice unless you wanted to buy from Dell, but that creates issues in cases when you get DOA and defective devices (have to ship back, get shipped a new one, etc. instead of just driving 10 minutes to a carrier store), so we had to deal with it. I don't recommend this phone. The battery is the primary reason, but aside from that this phone has the worse sound of all the WP7 launch devices.
Click to expand...
Click to collapse
I have a slightly different experience w/ the sound - so far the sound is better than the focus. Everything else though, is in the Focus' favor (outside viewing of the screen turned out to be much more important than I thought - it was awesome on the focus).
The battery is dreadfully inadequate on this device. My calling, e-mail, browsing, etc., ran it out of charge by the end of the workday and I was charging it up in the car on the way home. I could make it all the way to bed w/ my Focus (since once home I tended to use my device less).
An acceptable workaround for me has been the Power Skin (other's milage will vary greatly since it's a personal thing) .
The Power Skin gives me an extra 1500 (?) on the battery. It's different than I thought it would be - the phone works like it's pluged in and charging all day. When the skin is out of juice I slip it off and return to the nice sleek phone again. Pushing the power and volume buttons throgh the thick protective skin took some getting used to, but they're ok I guess.
If I'm going out and want to slip the phone in my pocket I just take off the skin and run w/out it. For me, it's more versitile than a larger battery w/ a new back cover since I have the best of both worlds (more power when I want or need it, slim phone when that's what I want or need).
N8ter said:
Not sure what heavy use means to you people. I'm a heavy user and there's no way in hell the HD7 can last 16 hours with that battery. Just not gonna happen.
Click to expand...
Click to collapse
I also get confused when I read things like this. I have the LG Quantum, 3.8". Wouldn't it take even less power than the HD7? With moderate use, I'm charging it by 3pm (off the charger at 7am). Or on the commute home at 6pm. Cause if not, it's dying by dinner time. And I've got a 1500 battery (which I believe is 100 more than the HD7 has).
-edit-
HOWEVER, to the OP:
I do recommend this phone. It just works. No fuss, no muss. Someone else has said it on here, but you just pick which set of limitations you're willing to live with. There's no HDMI out, XviD support, or robust DLNA functionality, which I'm finding is more important to me than previously thought. But everything works sooo well. Seemless, smooth, zero lag, graphically pleasing. Fantastic.
I've said it before, just head into a store and play with one until they kick you out.
I use my HD7s all the time (exchange, email, internet, music, games, wi-fi, games) so I'll occasionally have to charge mine at my desk at work. But if i'm not messing around with it all times of the day (like I usually am b/c I love my phone so much)...the battery lasts all day from when I wake up til I go to bed at night.
N8ter seems to have a knack for coming on the boards and slandering what he can, so I wouldn't put much trust in him.
I myself came from a Focus to an HD7S and it's pretty okay. The battery lasts quite a long time for being such a small one. I get about 14-16 hours of use if I'm checking my phone a lot, using FB, playing games, making a call and refreshing my email. I am on WiFi most of the time but I really don't see any difference using cellular data. I can get easily 24+ hours off one charge if I'm just using it a few times during the day.
The one gripe I really have about the HD7S is the screen. The ghosting on it is absolutely horrible. With the Mango update installed, I noticed it wasn't much of a problem reading scrolling white text as much, but grey text still was unreadable and tiles had a "streaking" effect still. Either way, my next phone won't be an HTC unless they change their panels. It's not really the blacks of the AMOLED screen that draw me in as much as outdoor visibility, brightness/vibrance and the ability to actually read text while you're scrolling. The Focus has it beat there. I reckon once a good price is found on eBay for one, I'll be switching over to a Focus S. The 4.3'' screen size is awesome, but WP7 really isn't made for SLCD.
thanks for the feedback. i decided against the focus because my other samsung phone seems to have really bad service, even my brother mom and dad that have the same phone said it about their samsung. i am really excited about mango.im a little confused on what i need to do to get mango installed. seems to be a lot of diff mango threads for this phone. does the htc come with a different live weather tile then the htc hub?
N8ter said:
Not sure what heavy use means to you people. I'm a heavy user and there's no way in hell the HD7 can last 16 hours with that battery. Just not gonna happen.
HD7s is an AT&T phone. If you want a WP7 phone on AT&T then get the focus. The extra 0.3 inches is not worth getting the HD7s.
Good rule of thumb is don't buy any smartphone with less than a 1400 mAh battery unless it's a blackberry. Really high end devices, you prolly want at least 1600. On T-Mobile there wasn't a choice unless you wanted to buy from Dell, but that creates issues in cases when you get DOA and defective devices (have to ship back, get shipped a new one, etc. instead of just driving 10 minutes to a carrier store), so we had to deal with it. I don't recommend this phone. The battery is the primary reason, but aside from that this phone has the worse sound of all the WP7 launch devices.
Click to expand...
Click to collapse
Sadly, the Focus BL isn't any better than the HD7. They both are pretty much horrible.
I predict the OP will be returning his WP7 phone before long...unless he just loves the style, smoothness and elegance of WP7 enough to live with it...even with Mango.
---------- Post added at 04:43 PM ---------- Previous post was at 04:40 PM ----------
speedfreak228 said:
thanks for the feedback. i decided against the focus because my other samsung phone seems to have really bad service, even my brother mom and dad that have the same phone said it about their samsung. i am really excited about mango.im a little confused on what i need to do to get mango installed. seems to be a lot of diff mango threads for this phone. does the htc come with a different live weather tile then the htc hub?
Click to expand...
Click to collapse
Don't expect much help from the devs. They tend to ignore questions because they believe any question that can ever be posted is already answered out there in the world wide web...so read.
And the rooting of WP7 phones is quite complex and vague.
i might just buy extra batteries if the battery life is that bad. so i root then install a rom with mango, right? just like my android
It's not root, it's unlock. All it does is allow you to sideload apps such as homebrew. With official unlock, you can unlock anytime. The Chevron method must be done before NoDo. Just find a pre-NoDo ROM for the HD7(S) & flash away. Chevron Unlock & upgrade to NoDo. Passing it into Mango is a bit more work as, at least with the leaks, Mango relocks WP7. there's a way to do it with ProvXML & HTC's Connection setup app. There will be an official Chevron labs Unlock for Mango that will cost money, but cut out a lot of the work. There is work on a root tool by Heathcliff & a FullUnlock (Unofficial name) by Cotulla in the works. These look promising, plus the custom update CAB's for custom ROM's that'll allow you to apply custom updates to the ROM (Change registry, patch system files, possibilities are endless).
As for battery life, I'm pretty sure I already said it. I get 8 hrs of work on moderate to heavy usage on & have 50+% left at least. I browse the internet, check Facebook, use Bing Maps, Check Emails, make calls, send SMS/MMS, all the normal stuff. Sometimes I even forget to turn off WiFi, which is supposed to eat battery life. Today alone, I used Bind Maps for directions from one delivery to another twice for a total of 1 hr with the screen on constantly, no car charger, just ordered one for work. I honestly don't know why people are complaining about battery life, it's not bad at all IMHO.
drkfngthdragnlrd said:
It's not root, it's unlock. All it does is allow you to sideload apps such as homebrew. With official unlock, you can unlock anytime. The Chevron method must be done before NoDo. Just find a pre-NoDo ROM for the HD7(S) & flash away. Chevron Unlock & upgrade to NoDo. Passing it into Mango is a bit more work as, at least with the leaks, Mango relocks WP7. there's a way to do it with ProvXML & HTC's Connection setup app. There will be an official Chevron labs Unlock for Mango that will cost money, but cut out a lot of the work. There is work on a root tool by Heathcliff & a FullUnlock (Unofficial name) by Cotulla in the works. These look promising, plus the custom update CAB's for custom ROM's that'll allow you to apply custom updates to the ROM (Change registry, patch system files, possibilities are endless).
As for battery life, I'm pretty sure I already said it. I get 8 hrs of work on moderate to heavy usage on & have 50+% left at least. I browse the internet, check Facebook, use Bing Maps, Check Emails, make calls, send SMS/MMS, all the normal stuff. Sometimes I even forget to turn off WiFi, which is supposed to eat battery life. Today alone, I used Bind Maps for directions from one delivery to another twice for a total of 1 hr with the screen on constantly, no car charger, just ordered one for work. I honestly don't know why people are complaining about battery life, it's not bad at all IMHO.
Click to expand...
Click to collapse
thanks for the mango rom explenation.i might have to pm you for help. that is really good battery life, seems alot better than my android
Over8ted said:
N8ter seems to have a knack for coming on the boards and slandering what he can, so I wouldn't put much trust in him.
I myself came from a Focus to an HD7S and it's pretty okay. The battery lasts quite a long time for being such a small one. I get about 14-16 hours of use if I'm checking my phone a lot, using FB, playing games, making a call and refreshing my email. I am on WiFi most of the time but I really don't see any difference using cellular data. I can get easily 24+ hours off one charge if I'm just using it a few times during the day.
The one gripe I really have about the HD7S is the screen. The ghosting on it is absolutely horrible. With the Mango update installed, I noticed it wasn't much of a problem reading scrolling white text as much, but grey text still was unreadable and tiles had a "streaking" effect still. Either way, my next phone won't be an HTC unless they change their panels. It's not really the blacks of the AMOLED screen that draw me in as much as outdoor visibility, brightness/vibrance and the ability to actually read text while you're scrolling. The Focus has it beat there. I reckon once a good price is found on eBay for one, I'll be switching over to a Focus S. The 4.3'' screen size is awesome, but WP7 really isn't made for SLCD.
Click to expand...
Click to collapse
The SLCD screen is decent. The screen is much better than the panel on the original HD7.
That being said. I'm not slandering anything. Anyone who claims to be getting 16 hours with "heavy use" on this phons either lying or using a definition of "heavy use" that none of us have ever heard before. The phone never goes that long on heavy use. It's practically impossible to do it.
If they get 16 hours of heavy use on an HD7, then I get 400 hours of heavy use on my Vibrant. That's how ridiculous that sounds, and is.
What kind of plan that AT&T require you to stick with the HD7s?
Strike_Eagle said:
What kind of plan that AT&T require you to stick with the HD7s?
Click to expand...
Click to collapse
i have the unlimited data plan
Sent from my Windows Phone 7
Like what can you choose on your plan? Or you must stick with only one plan that At&T provide for hd7s?
Sent from my Schubert using XDA Windows Phone 7 App
I love the Droid Charge's hardware, I really do. Those first-gen Galaxy S PenTile AMOLED displays drove me nuts, LTE is the effing truth, and thankfully, the Wolfson DAC is just as killer as it was last time around -- I came from a Vibrant on T-Mobile.
As you can probably imagine, I'm loathe to give up LTE. And I've got incredible respect for the work that imnuts, imoseyon, the GummyCharged bros, and all the other developers here and at RW are putting into this phone to make it usable -- seriously, you guys are awesome. But the day-to-day with this phone is just wearing on me hard, and I really miss the serene world of stable CyanogenMod. These days, my battery will randomly choose days to die before I'm even home from work, the GPS chip doesn't seem any better than the Vibrant's was, the phone is noticeably less responsive than a CM7 device with similar internals, I still occaisionally get launcher redraws, and though it's improved considerably with EP3HA I still sometimes get data dropouts.
I know it's the same **** you guys all complain about, I guess I just wonder if anyone else has literally gotten so frustrated with it that they gave up the sweet nectar of LTE to get the hell away from this disaster of a software implementation. I joined the Galaxy S party late in the Vibrant's lifespan so I had a really positive experience thanks to all the great development people had done for it. I didn't really get the full flavor of "Samsung Disease" until this phone, and for chrissake, I can see why people were running the hate parade.
Has anyone else here gone back (or thought about going back) to an Ev-DO phone just for a better software experience? We can pretty much guarantee that the resale value of this phone is going to completely tank after the G-Nexus launches so I'm thinking it makes sense to get some cash out of it now. I literally won a clean ESN Fascinate auction on eBay last night for $81, so I'm psyched about that.
Incidentally I'll probably just buy another Charge for 81 dollars at this time next year after it's rocking official CM7. Then again, maybe the Galaxy Nexus will be cheap by then.
Thoughts?
Here's my thought: The grass is always greener. This is the Groundhog Day of phone forums.
If you want to go back to a 3G phone, how about you set your Charge to 3G only? That way it behaves the same as a Fascinate.
Cm7 is far from stable my friend. Try getting a nightly that doesn't play well with your kernal. Once you've bricked from this you will understand. In a year this will all be different. Phones are being released to developers first now to tweak them for the hard release. Think of it this way... The linux command for superuser, or "su" does not hurt the machine, but opens up commands to fine tune to the user's preferences. If we are given the base framework to recover to, there is no harm in supercharging the system, just so long as we can "reset" it in case of a system failure or resource exhaustion. Just wait until google buys MORE into samsung's development.
Speed rules...
fortesquieu said:
If you want to go back to a 3G phone, how about you set your Charge to 3G only? That way it behaves the same as a Fascinate.
Click to expand...
Click to collapse
No kidding.. my thoughts exactly. This phone is without a doubt superior to the fascinate... then again, to each his own.
Sent from my SCH-I510 using Tapatalk
As much as I love my rock solid stable fascinate tsm poolparty 1.5 with glitch v13 rc, Im moving on to the charge bought off funzy32. Why? because I got it for $185. I dont plan on having issues with the charge, because ive never had problems with any android device in three years which seems un-realistic, but Im sticking with my good luck reasoning. The charge in terms of development is still in its infancy. Hell, my first verizon device was an htc incredible and over a year later it is still being improved. I have absolute faith that the charge will be continually developed on. The fact is that it is not a low end device or a middle of the road device either. As many problems as the failure device known as the fascinate has. It currently has an Ics sdk port that from my understanding is pretty insane in its infancy. If the fascinate can make it, the charge will be doing the same.
I'd go back in a second! Sadly I had to send in my fassy to get this garbage.
I was thinking the same thing a couple days ago. I miss my fassy a lot, but it had its issues like calls never coming in or texts not going out. 4g is unbelievably fast...didn't expect it to be this fast, it trumps home internet like many have said.
The fassy was the better phone overall though no doubt. I regret getting the charge as a replacement. I don't have any issues with it but it just doesn't feel right.
You guys are quite the whiney lot.
OP, why don't you post what setup you were running so that maybe we could help diagnose your issues.
Obviously battery life on the Fascinate is going to be much better than on the Charge, with its larger screen and battery sucking LTE.
I've found the battery life to be tolerable on the Charge as long as I'm not doing anything ridiculous like streaming audio/video for long periods of time. I live outside of LTE service location so I have my phone set to CDMA only. As of right now, after a typical day of use (probably 30 texts, 30 minutes of Pandora streaming, 20 minutes of phone calls, and probably 3 solid hours of screen-on time while browsing) my battery has 40% charge after 7 hours and 20 minutes unplugged.
If your conscious about how you are using the battery it is pretty manageable. Turn off LTE when you don't need it. Turn off mobile data when you aren't using it. Switch onto a wifi signal when one is available. Turn off GPS when you're not using it. This is pretty common sense stuff.
As far as screen redraws, use V6 Supercharger. I used to be annoyed to no end because of redraws. Since loading the script, I've had maybe 4 redraws in about a month. I don't even notice it anymore.
Also, if you miss TSM, the latest GummyCharged has it. Just have to go over to Rootzwiki to get it, they don't care for xda anymore.
nowens0520 said:
You guys are quite the whiney lot.
Click to expand...
Click to collapse
This. I'm tired of people bashing this phone. Sure, it has some issues, but if you're that fed up with is just get rid of the phone. No sense in continuously *****ing about it.
Sent from my Droid Charge running Infinity Beta
kvswim said:
This. I'm tired of people bashing this phone. Sure, it has some issues, but if you're that fed up with is just get rid of the phone. No sense in continuously *****ing about it.
Sent from my Droid Charge running Infinity Beta
Click to expand...
Click to collapse
Agreed. I really don't even understand the gripes. I guess its just me, but I believe this is hands down the best smartphone I've ever owned. Sure, I miss CM7 a bit which I too had on my fassy, but as I've heard mentioned before, what can the fassy do that the Charge cannot? Unless I'm being an absolute phone hog, I can easily go 12 hours a day without turning ANYTHING off. I don't get screen redraws, static phone calls, data drop offs, or any of the other complaints. I occasionally have some minor Rom nuances but you get that with just about any Rom and Android phone. I'm seriously loving my Droid Charge experience! I don't get the whining or the constant threads on this topic. If you don't like it, you don't need our approval to move on. Just get rid of the phone and move on already!
Sent from my SCH-I510 using Tapatalk
I thought I was pretty clear in my OP, but maybe not. I miss CyanogenMod. That is the main thing that I miss. The Charge doesn't have it. I guess I also miss having a small device, but that's not a fair complaint right now -- LTE radios are chunky, and I recognize that.
The battery life has been a really big sore spot for me, too. I've tried setting the phone to CDMA/Ev-DO only (completely ignoring the ridiculousness of carrying a larger, more expensive device and toggling off its best feature) to get a feel for what I'd be getting into speedwise if I switched to a Fascinate. I rarely use GPS, and leave it turned off.
It doesn't seem to have any effect on the battery; on Wednesday I ran it CDMA-only and barely used the device at all outside of an hour or so of PowerAmp playback and a handful of Google searches and GV messages. I took it off the charger with 100% juice at 7:15 AM, and it was dead by 6:30 PM. The maddening part is that it's crazy inconsistent: there are days where it makes it through the whole day with 30% or so left,even though I've had LTE turned on all day and have been using the phone fairly extensively. I definitely don't think it's a hardware problem -- Engadget swears they got two days in their review of this thing. The best guess I've been able to piece together is that the battery loss has something to do with with the phone's poor tower handoffs, because I've noticed a pattern of having a dead Charge on days where I move from place to place a lot. Days where my only destinations are home and work don't seem to exhibit the issue as much.
I suppose I'm past the point of being interested in solving it, and the device's limited community uptake (relative to something like the Nexus phones, or several of the more popular HTCs) doesn't help. That's the hugely exciting thing about the Galaxy Nexus -- we at least know it'll be crazy popular here, at Rootzwiki, and everywhere else. I just hope it's got a decent DAC and headphone amp, because otherwise the Fascinate and the Charge are still going to be my future.
Someone asked me to post my setup, so I guess I'll repeat myself. I'm running EP3HA debloated. I've tried it with the stock kernel and with imoseyon's kernel -- didn't notice major differences either way. Compared to its predecessors, EP3HA has been an incredible improvement -- I ran the gamut and tried everything before, but I probably spent the most time with assorted builds of GummyCharged FE. I switched to EP3HA once I saw that imoseyon got Voodoo Sound working on his kernel, and I definitely believe that's currently the best way to use the Charge. I get fewer launcher redraws, and data drops less -- but make no mistake, there are still redraws and drops. I do firmly believe that this phone is headed toward greatness; in a year or so it's going to be a really amazing choice if it keeps improving at this rate. So, I'm coming back in a year. I've just grown weary of living with a problematic phone when Android itself has been done so much more gracefully on other devices -- how can any Charge owner deny that? Even if you love the device's hardware (as I do), have somehow had no issues (lol), and intend to keep it... the ability to run AOSP ROMs and to consistently get through the day on a single charge are irrefutably pretty big advantages.
One of my pals got a Droid Charge the same day as me, and has been experiencing all these same issues. In fact, our decisions to switch -- me to the Fascinate and him to the DInc -- were born out of frequent griping to each other about how poor the day-to-day with the Charge has been. Of course we hate losing LTE, it's obnoxious. The biggest reason we're paying Verizon's hilariously awful prices was to get access to LTE 700, and hopefully we'll get to come back to it soon. It's kind of a bummer because this has been his first Android device (he came from an iPhone 3GS). I told him the day we got our phones that I really wished Verizon had a solid LTE device with mature CyanogenMod support, because Samsung puts out a really embarassing version of Android and it's a super ****ty first impression to show him of the platform I've grown to love. "But," we said, "having LTE should make up for it."
It almost does. Almost.
kvswim said:
This. I'm tired of people bashing this phone. Sure, it has some issues, but if you're that fed up with is just get rid of the phone. No sense in continuously *****ing about it.
Click to expand...
Click to collapse
Do you work for Samsung? Why on earth could you possibly be bothered by people objectively stating their complaints about a half-baked product? I signed a two-year contract for an overpriced unfinished smartphone too, dude. I'm in the same boat as you.
fortesquieu said:
If you want to go back to a 3G phone, how about you set your Charge to 3G only? That way it behaves the same as a Fascinate.
Click to expand...
Click to collapse
Look how bad your post is. This is a bad, bad post.
kalibar said:
I thought I was pretty clear in my OP, but maybe not. I miss CyanogenMod. That is the main thing that I miss. The Charge doesn't have it. I guess I also miss having a small device, but that's not a fair complaint right now -- LTE radios are chunky, and I recognize that.
The battery life has been a really big sore spot for me, too. I've tried setting the phone to CDMA/Ev-DO only (completely ignoring the ridiculousness of carrying a larger, more expensive device and toggling off its best feature) to get a feel for what I'd be getting into speedwise if I switched to a Fascinate. I rarely use GPS, and leave it turned off.
It doesn't seem to have any effect on the battery; on Wednesday I ran it CDMA-only and barely used the device at all outside of an hour or so of PowerAmp playback and a handful of Google searches and GV messages. I took it off the charger with 100% juice at 7:15 AM, and it was dead by 6:30 PM. The maddening part is that it's crazy inconsistent: there are days where it makes it through the whole day with 30% or so left,even though I've had LTE turned on all day and have been using the phone fairly extensively. I definitely don't think it's a hardware problem -- Engadget swears they got two days in their review of this thing. The best guess I've been able to piece together is that the battery loss has something to do with with the phone's poor tower handoffs, because I've noticed a pattern of having a dead Charge on days where I move from place to place a lot. Days where my only destinations are home and work don't seem to exhibit the issue as much.
I suppose I'm past the point of being interested in solving it, and the device's limited community uptake (relative to something like the Nexus phones, or several of the more popular HTCs) doesn't help. That's the hugely exciting thing about the Galaxy Nexus -- we at least know it'll be crazy popular here, at Rootzwiki, and everywhere else. I just hope it's got a decent DAC and headphone amp, because otherwise the Fascinate and the Charge are still going to be my future.
Someone asked me to post my setup, so I guess I'll repeat myself. I'm running EP3HA debloated. I've tried it with the stock kernel and with imoseyon's kernel -- didn't notice major differences either way. Compared to its predecessors, EP3HA has been an incredible improvement -- I ran the gamut and tried everything before, but I probably spent the most time with assorted builds of GummyCharged FE. I switched to EP3HA once I saw that imoseyon got Voodoo Sound working on his kernel, and I definitely believe that's currently the best way to use the Charge. I get fewer launcher redraws, and data drops less -- but make no mistake, there are still redraws and drops. I do firmly believe that this phone is headed toward greatness; in a year or so it's going to be a really amazing choice if it keeps improving at this rate. So, I'm coming back in a year. I've just grown weary of living with a problematic phone when Android itself has been done so much more gracefully on other devices -- how can any Charge owner deny that? Even if you love the device's hardware (as I do), have somehow had no issues (lol), and intend to keep it... the ability to run AOSP ROMs and to consistently get through the day on a single charge are irrefutably pretty big advantages.
One of my pals got a Droid Charge the same day as me, and has been experiencing all these same issues. In fact, our decisions to switch -- me to the Fascinate and him to the DInc -- were born out of frequent griping to each other about how poor the day-to-day with the Charge has been. Of course we hate losing LTE, it's obnoxious. The biggest reason we're paying Verizon's hilariously awful prices was to get access to LTE 700, and hopefully we'll get to come back to it soon. It's kind of a bummer because this has been his first Android device (he came from an iPhone 3GS). I told him the day we got our phones that I really wished Verizon had a solid LTE device with mature CyanogenMod support, because Samsung puts out a really embarassing version of Android and it's a super ****ty first impression to show him of the platform I've grown to love. "But," we said, "having LTE should make up for it."
It almost does. Almost.
Do you work for Samsung? Why on earth could you possibly be bothered by people objectively stating their complaints about a half-baked product? I signed a two-year contract for an overpriced unfinished smartphone too, dude. I'm in the same boat as you.
Look how bad your post is. This is a bad, bad post.
Click to expand...
Click to collapse
... and people wonder why the Gummy team left XDA.
If you wanted a phone that ran CM7, why'd you buy a phone that didn't have it? You should be well aware of how development works, there are no guarantees. I just think it's hilarious that you're going to pay your own hard earned money to downgrade your phone just because your particular favorite toy isn't on there.
I mean sucks that you're having some relatively minor problems with your Charge, but the Fascinate was no angel either. Have fun with your dropped / missed calls, front buttons that push themselves and total garbage GPS lock times.
To be honest, it sounds like you know the game here, so I assume you did your homework before your bought it, so really, you have no one but yourself to blame.
Fivecent said:
... and people wonder why the Gummy team left XDA.
If you wanted a phone that ran CM7, why'd you buy a phone that didn't have it? You should be well aware of how development works, there are no guarantees. I just think it's hilarious that you're going to pay your own hard earned money to downgrade your phone just because your particular favorite toy isn't on there.
I mean sucks that you're having some relatively minor problems with your Charge, but the Fascinate was no angel either. Have fun with your dropped / missed calls, front buttons that push themselves and total garbage GPS lock times.
To be honest, it sounds like you know the game here, so I assume you did your homework before your bought it, so really, you have no one but yourself to blame.
Click to expand...
Click to collapse
Since when was usability a toy? Maybe it's his fault for buying a phone that doesn't have CM7, but it's not his fault the phone's stock firmware is garbage. Why are you all apologists for this device? Is it because you bought it? Do you guys go around, telling people how your phone is the best phone no matter what, all because you paid money for it and to do otherwise would make you feel stupid?
Just be honest. The phone kinda sucks. It'd be one thing if the battery life was just bad, but the fact that it varies from day to day is like having a car that gets 25mpg on some days and 12mpg on others. It's one thing to tolerate mediocrity, but to defend it is absolutely despicable. You all should be ashamed.
Multiple times, across multiple firmwares (humble, gummy, fe and gbe, infinity beta w/ ep3ha) I've had the phone lag at inappropriate times that resulted in committing an action that I absolutely did not want.
For example, and I think this was on Gummy 2.0 GBE (laughably bad compared to even the release candidates that came before it), one time I pressed the power button to wake the phone, and it didn't wake (I have a case that makes it so you have to push a little harder), so I pressed it again and it did. I then slid to unlock, but instead of that happening, the phone shut off. It was so laggy that it actually did detect the first power button press, and the second one I held slightly too long (which brings up the reboot/poweroff/silent/etc dialog) and when I thought I was sliding to unlock, the phone registered it as pressing the power off option on the popup dialog that hadn't yet appeared when I was trying to unlock the phone. Phone powers off. I tried to unlock my phone and instead got a powered off device.
That's ****ing unacceptable. It's 2011, we should have devices that are responsive and stable. But instead, we get a holocaust. This isn't my fault. This isn't kalibar's fault. It's Samsung's fault. We thought we could count on them to make something with perhaps not the best experience, but a passable one at least. And we weren't just a little wrong, we were really wrong.
If you honestly believe this phone is good, you've never used an iPhone. I'm not trying to start an Android vs iOS argument, but when it comes to having a phone with reliable battery life and a consistently responsive user experience, the iPhone never fails. And although I've heard the 4S has ****ty battery life at the moment, there is no doubt in my mind that it will actually get fixed because Apple actually gives a ****. In a year when you can run AOSP ROMs on this phone, I would bet money that the official offering from Samsung remains an abortion.
Anyone who claims to have no issues with this phone is either a liar, or a good majority of Droid Charges are lemons. Either does not bode well.
And stop called the Fascinate, "Fassy." It immediately reveals that you're a neckbeard virgin.
p.s. The Gummy team left XDA not because people complain about the shortcomings of devices but because people do things like irrationally defend utter crap and spout cringe-inducingly stupid nonsense.
@jhonas, The phone is fairly new and the bugs will be worked out, I have complete faith in our developers.
Someone is an internet tough guy...
The Gummy Team left XDA from people like you just constantly whining about EVERYTHING. I don't have any problems with this phone beyond the battery life. That's it.
It's not like some of us defend our phones just for the hell of it...it's because we know this can be potentially a great phone. Things can take time. Look at how the FASSY (you mad?) was at the very beginning - everyone hated it. Now that it's a mature phone, it can be appreciated. Development for this device is in its infancy-unfortunately some people can't or won't see that and insist on bashing it.
Sent from my Droid Charge running Infinity Beta
Jhonas said:
Since when was usability a toy? Maybe it's his fault for buying a phone that doesn't have CM7, but it's not his fault the phone's stock firmware is garbage. Why are you all apologists for this device? Is it because you bought it? Do you guys go around, telling people how your phone is the best phone no matter what, all because you paid money for it and to do otherwise would make you feel stupid?
Just be honest. The phone kinda sucks. It'd be one thing if the battery life was just bad, but the fact that it varies from day to day is like having a car that gets 25mpg on some days and 12mpg on others. It's one thing to tolerate mediocrity, but to defend it is absolutely despicable. You all should be ashamed.
Multiple times, across multiple firmwares (humble, gummy, fe and gbe, infinity beta w/ ep3ha) I've had the phone lag at inappropriate times that resulted in committing an action that I absolutely did not want.
For example, and I think this was on Gummy 2.0 GBE (laughably bad compared to even the release candidates that came before it), one time I pressed the power button to wake the phone, and it didn't wake (I have a case that makes it so you have to push a little harder), so I pressed it again and it did. I then slid to unlock, but instead of that happening, the phone shut off. It was so laggy that it actually did detect the first power button press, and the second one I held slightly too long (which brings up the reboot/poweroff/silent/etc dialog) and when I thought I was sliding to unlock, the phone registered it as pressing the power off option on the popup dialog that hadn't yet appeared when I was trying to unlock the phone. Phone powers off. I tried to unlock my phone and instead got a powered off device.
That's ****ing unacceptable. It's 2011, we should have devices that are responsive and stable. But instead, we get a holocaust. This isn't my fault. This isn't kalibar's fault. It's Samsung's fault. We thought we could count on them to make something with perhaps not the best experience, but a passable one at least. And we weren't just a little wrong, we were really wrong.
If you honestly believe this phone is good, you've never used an iPhone. I'm not trying to start an Android vs iOS argument, but when it comes to having a phone with reliable battery life and a consistently responsive user experience, the iPhone never fails. And although I've heard the 4S has ****ty battery life at the moment, there is no doubt in my mind that it will actually get fixed because Apple actually gives a ****. In a year when you can run AOSP ROMs on this phone, I would bet money that the official offering from Samsung remains an abortion.
Anyone who claims to have no issues with this phone is either a liar, or a good majority of Droid Charges are lemons. Either does not bode well.
And stop called the Fascinate, "Fassy." It immediately reveals that you're a neckbeard virgin.
p.s. The Gummy team left XDA not because people complain about the shortcomings of devices but because people do things like irrationally defend utter crap and spout cringe-inducingly stupid nonsense.
Click to expand...
Click to collapse
First off, there are plenty of decaffeinated brands on the market that taste just as good as the real thing, think about it.
I don't believe fivecent was referring to usability as a toy. He was referring to CM7 as a toy. It didn't come pre-installed on the phone - it's an extra or a "toy." It is well known Samsung is notorious for great hardware and crappy software. If you and kalibar have been around on Android at all, you should have already known this. And if you didn't do enough research to find this out, shame on both of you. Albert Einstein said insanity is doing the same thing over and over again and expecting different results. In this case expecting Samsung to suddenly put out a phone with great software given their track record, I would call naive.
Apple isn't better at fixing things because they care more, it's because they only have on phone to work on. All other phone manufacturers prefer to offer customers options and choices. Apple tells it's sheeple (customers) this is what we make, you will buy it and like it.
The Charge was only the third LTE phone on Verizon. Like davwaman said, there are still bugs and they will be worked out. Verizon and all phone manufacturers are encountering occasional problems related to 4G LTE. No 4G LTE phone has a functional CM7 because of the 4G radios/RIL.
And TeamGummy and several other developers didn't leave XDA for either your reason or the other reason stated. It's not my place to say why they left. You can ask them yourself, which you obviously haven't done based on your post.
And finally, you've been a member here since 2007 and this rant is your first post? Really? Not one productive or helpful post before now?
Jhonas said:
Since when was usability a toy? Maybe it's his fault for buying a phone that doesn't have CM7, but it's not his fault the phone's stock firmware is garbage. Why are you all apologists for this device? Is it because you bought it? Do you guys go around, telling people how your phone is the best phone no matter what, all because you paid money for it and to do otherwise would make you feel stupid?
Just be honest. The phone kinda sucks. It'd be one thing if the battery life was just bad, but the fact that it varies from day to day is like having a car that gets 25mpg on some days and 12mpg on others. It's one thing to tolerate mediocrity, but to defend it is absolutely despicable. You all should be ashamed.
Multiple times, across multiple firmwares (humble, gummy, fe and gbe, infinity beta w/ ep3ha) I've had the phone lag at inappropriate times that resulted in committing an action that I absolutely did not want.
For example, and I think this was on Gummy 2.0 GBE (laughably bad compared to even the release candidates that came before it), one time I pressed the power button to wake the phone, and it didn't wake (I have a case that makes it so you have to push a little harder), so I pressed it again and it did. I then slid to unlock, but instead of that happening, the phone shut off. It was so laggy that it actually did detect the first power button press, and the second one I held slightly too long (which brings up the reboot/poweroff/silent/etc dialog) and when I thought I was sliding to unlock, the phone registered it as pressing the power off option on the popup dialog that hadn't yet appeared when I was trying to unlock the phone. Phone powers off. I tried to unlock my phone and instead got a powered off device.
That's ****ing unacceptable. It's 2011, we should have devices that are responsive and stable. But instead, we get a holocaust. This isn't my fault. This isn't kalibar's fault. It's Samsung's fault. We thought we could count on them to make something with perhaps not the best experience, but a passable one at least. And we weren't just a little wrong, we were really wrong.
If you honestly believe this phone is good, you've never used an iPhone. I'm not trying to start an Android vs iOS argument, but when it comes to having a phone with reliable battery life and a consistently responsive user experience, the iPhone never fails. And although I've heard the 4S has ****ty battery life at the moment, there is no doubt in my mind that it will actually get fixed because Apple actually gives a ****. In a year when you can run AOSP ROMs on this phone, I would bet money that the official offering from Samsung remains an abortion.
Anyone who claims to have no issues with this phone is either a liar, or a good majority of Droid Charges are lemons. Either does not bode well.
And stop called the Fascinate, "Fassy." It immediately reveals that you're a neckbeard virgin.
p.s. The Gummy team left XDA not because people complain about the shortcomings of devices but because people do things like irrationally defend utter crap and spout cringe-inducingly stupid nonsense.
Click to expand...
Click to collapse
so much BUTTHURT lol
no but seriously I loved my FASSY and I love my Charge, sure they both have issues but are incredible phones none the less.. there are always problems and always will be as no phone is perfect, and this constant whining about how bad it is isn't helping anyone unless its an actual constructive question about how to fix something or why something's happening
Lufc or Scotsman where you at buddies, lock this thread up
blazing through on my 4G Droid Charge
Jhonas said:
If you honestly believe this phone is good, you've never used an iPhone. I'm not trying to start an Android vs iOS argument, but when it comes to having a phone with reliable battery life and a consistently responsive user experience, the iPhone never fails. And although I've heard the 4S has ****ty battery life at the moment, there is no doubt in my mind that it will actually get fixed because Apple actually gives a ****. In a year when you can run AOSP ROMs on this phone, I would bet money that the official offering from Samsung remains an abortion.
Click to expand...
Click to collapse
Chopping the rest because this is all I'm going to respond to. I came to this phone from an iPhone. You couldn't pay me to go back.
That is all.
I don't understand how this thread is still going on. We have a parade of "blame the OP" for daring to purchase the flagship Samsung Verizon phone and expecting it to actually work, then people pretending like a battery that goes 12 hours, barely, if you micro it, is perfectly acceptable, then we have people blaming other posters for not making enough nice posts before a rant?
Seriously, what the hell? The phone seems pretty crappy from all the reviews and I don't think that the OP was asking for people to leap in and white-knight it, I'm pretty sure he wanted opinions on things he would miss or whatever if he downgraded to a Fascinate.
(Honestly, "Fassy"? Makes you sound like you're 5.)
So I'm looking over the current options and right now it's not really looking like it's promising. I have my Galaxy S3 rooted and with the help of tools like TitantiumBackup I've managed to clean up the stock ROM pretty well. Another thing of note is I actually get some surprisingly good sound quality out of my SGS3. I realize the US models aren't supposed to have the Wolfson DAC, but somehow mine sounds absolutely incredible with no noise that I can hear or anything (it's enough that I've been wondering if Samsung might have slipped the Wolfson into this one and perhaps there is variance in the DACs actually being used.) It even drives my headphones (modified HD555s -- basically you can consider them to be like the HD595s since of course I did the foam mod, but with the soundstage mod and a custom cable they're actually a bit better possibly) extremely well. It's worth noting that I have frozen the built in equalizer or whatever it was that I thought seemed like it was meant to mess with the sound (I like my devices to produce a relatively neutral sound.) Despite some complaints out there, I actually like the sound out from my US model SGS3 better than things like my Cowon D2 (which, btw, has a Wolfson DAC) and don't even use my CMoy (which has an AD8620 OPAMP that makes it sound far better than a typical OPA2132 CMoy IMO at only the cost of a bit of battery life) which I love the sound of because to me it sounds amazing on its own.
I only mention all of this because while I'm not a true audiophile per se, quality is of extreme importance to me all the same and I'm reading of issues with sound in the current custom ROMs which is not something I'm ok with. I want it to continue to sound this amazing. The idea of losing sound quality with a custom ROM bothers me. I like the idea of a few of the updates like Project Butter (though it's worth noting that mine does run fairly smoothly since I keep the number of programs running all the time as minimal as I can) and I really like the idea of having a custom ROM where I could maybe tweak more things (perhaps including better battery life options like maybe a better CPU governor built in? It drives me crazy how much my phone can run down over just a few hours while the screen is off even with SetCPU set to set the CPU to 384MHz and switch to the powersave governer with WiFi and mobile data both disabled and me not receiving any calls or texts.) For that matter, even while on it's not helping as much as it seems like it should, but I can't help but to notice that there are some more advanced CPU governors that I don't seem to have as an option and I wonder if perhaps a custom ROM could even help there as well. Plus I just plain like being able to tweak more things to my exact preferences instead and again a custom ROM helps. But, if I have to give up that sound quality that's a big problem. I think also it might be a problem to lose the camera. I don't use it a lot, but every now and then I really do kind of want to have it. Especially it would absolutely suck to lose the ability to scan QR codes or to have to do so via the front camera, but every now and then I do take some actual photos to share.
So my question is, have any of the custom ROM options out there reached that level of stability and quality to actually be worth updating and without losing those two things? The SGS3 has been out a fair while now, so it's hard for me to believe that there hasn't been a bit more progress along these lines, but I realize that it's no simple process to create a custom ROM all the same. (In fact, I only think more progress would have been made than what I've read thus far because the SGS3 is just so very popular. If it had been a less popular phone I wouldn't necessarily expect that much, but between its features, hardware, and etc, it's a pretty popular phone.) I want all the benefits of a custom ROM, but what I've read so far of them says to me that it's just not worth the trouble. Once I find one that really works I kind of want to stick to it as much as I can as I have a lot of apps installed and configured just so for my preferences. It sounds like I'm going to have to wait a good while yet though. Or have any of the custom ROMs finally "gotten there yet"?
ive been using CM10 roms for daily use and tehy do everything i need them to do without any limitations.
i suggest you make a nandroid of all your current setup and play with some custom roms. you can always revert back if you dont liek it or cant configure them match your usage. it made my S3 experience much better, btu everyone is dfferent.
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
there are also sound mods and stuff that are accessible with ROMs. ive never tried them but some people swear by them
You don't have any sound issues of any kind? Does the rear camera work perfectly?
BTW, I don't want any sound mod that actually changes the sound. I want it to basically leave the sound alone and produce it as well as it can without modification. None of that Beats or whatever like some do (I think that was what HTC was pushing?)
beats is a sound thing, yeah. it hink its just an equalizer though. i have used audio through headphone jack and over bluetooth to my headphones and the quality is fine for me. im not an audiophile though. it all kinda sounds the same to me lol
the only sound issues i have with my ROM are after flash some sounds do not function until you slide the volume slider from 100 to 0 then to 100 again. Its these types of quirks that come with custom rom sometimes.
my camera is working perfectly. its not as good as the touchwiz one however.
edit: heres a sound mod that might/might not interest you
http://forum.xda-developers.com/showthread.php?t=1883262
long as you do a nandroid you can always revvert back to your preferred current setup. you should also backup your IMEI
There are roms that are optimized stock. Maybe CleanRom. Don't think he adds sound mods but may be wrong. You may have used app to underclock CPU and it shows UC but probably not actually working on stock kernel as clocking must be enabled on kernel. Know this is true with overclocking.
I actually prefer to avoid all sound modifications whatsoever. Even equalizer. I like the results of a relatively neutral sound being fed to these headphones, it comes out just perfect for me. That's part of what I was worried about as some of the custom ROMs sometimes try to have stuff like that built in (and I guess that equalizer or whatever it was was Samsung or Verizon kind of doing that in the stock ROM even.)
About the camera, I actually have a commercial camera app anyway. If the only problem people have been having was the built-in app, that's a non-issue.
What's this about sounds not working until you go to zero and back though? Does this interfere with anything such as receiving phone calls (eg does it sometimes not ring because the sound isn't playing?)
BTW, where do I actually find the "official" CM10 for this phone?
no the sound works all the time after the adjustment. it takes 2 secodns to do. open volume, slide them all to 100, then all to 0, then all to 100 again.
http://get.cm/?device=d2vzw&type=snapshot
i think that these M builds are the monthyl most stable ones.
Personally I'm waiting for something built on the official VZW JB release. And yes I know I have months to wait... :-\
Sent from my SCH-I535 using xda app-developers app
There is no DAC from Wolfson but yes it sounds kick ass! Qualcom is a beast! There S4 chip is there pride and joy so they didn't want to lag behind when it comes to quality audio! God does it sound so much better then my galaxy nexus. Qualcom is making the best arm chips right now. Can't wait to see how insane the 4 core S4 is!
I COMPLETELY AGREE WITH MY FELLOW MEMBERS WHEN IT COMES TO AVOIDING ALL THOSE STUPID AUDIO MODS LIKE BEATS AND SOME OTHERS OUT THERE. THEY SUCK AND DISTORT THE AUDIO!
Sent from my SCH-I535 using xda premium
ddurandSGS3 said:
no the sound works all the time after the adjustment. it takes 2 secodns to do. open volume, slide them all to 100, then all to 0, then all to 100 again.
Click to expand...
Click to collapse
Ah, have I misunderstood? Do you just mean it only needs this to be done after the initial flash of the custom firmware itself? That's definitely no big deal at all...
prdog1 said:
There are roms that are optimized stock. Maybe CleanRom. Don't think he adds sound mods but may be wrong. You may have used app to underclock CPU and it shows UC but probably not actually working on stock kernel as clocking must be enabled on kernel. Know this is true with overclocking.
Click to expand...
Click to collapse
Well, I want to try to do this just once or at least no more than minor updates after this hopefully, so if I'm going to go ahead I want to go ahead and go straight to Jelly Bean.
I think SetCPU wouldn't be sold as only requiring root access to do its work if it required a custom kernel. It probably just works with the internal power management features that should be built in more or less by default.
mike216 said:
There is no DAC from Wolfson but yes it sounds kick ass! Qualcom is a beast! There S4 chip is there pride and joy so they didn't want to lag behind when it comes to quality audio! God does it sound so much better then my galaxy nexus.
Click to expand...
Click to collapse
Interesting... I do definitely wonder why some people have complained about hearing noise and such then. Perhaps a bad setting and/or that MusicFX app (finally had time to dig through the list to find out what exactly it was called and that's the one that I just assumed was probably an equalizer/effects processing thing that would modify the sound, but honestly I never had any use for it even if it's not and never bothered to try it.) I'm glad to hear that I'm not the only one who thinks that the US SGS3 actually sounds good. I was beginning to wonder if my ears were maybe just getting that bad somehow even though I'm still far pickier than everyone I personally know, lol.
Let me ask you this, is the so called "Voodoo Mod" any good at least? I was never clear on exactly what it was supposed to do for audio. I know things like Beats probably mostly rely on a bit of processing to increase bass and probably play with things like stereo separation or something, but I've never been clear on what that one was trying to do exactly other than that people claim it's actually an improvement for many devices.
Anyway, back on the topic at hand, I think I'm more or less convinced to at least go ahead and give CM10 a shot. I'll use that newer monthly build from earlier this month after clearing enough space to make a full backup. (Besides CWM's backup option I've already backed up my apps and settings using TitaniumBackup, so in a worst case scenario it shouldn't be too painful if things go wrong and I have to go all the way back to a stock image with a factory reset or something. Is that option in CWM the correct thing, or must I use something separate for a Nandroid backup?) Also, it may sound silly, but how exactly do I backup my IMEI? I was looking for that already upon digging through a large tutorial thread a while back and it seemed to require something I couldn't get to work (when I try the numbers mentioned in the dialer I don't get any hidden menus, just a dialtone. Other than that I could only find something about manually restoring it if it has been completely damaged or lost which wasn't a fun looking process.)
Nazo said:
I think SetCPU wouldn't be sold as only requiring root access to do its work if it required a custom kernel. It probably just works with the internal power management features that should be built in more or less by default.
Click to expand...
Click to collapse
It is sold that way. Depends on the manufacturer of the device. On stock HTC kernel it will lock 2nd core at max speed, kill battery life and cause heating problems. That is why I said it may not work correctly and without another app to monitor CPU you don't know what it is doing. How it works with Samsung I wouldn't know as I run custom kernels when possible and don't worry about clocking on stock kernels as they are under performing already.
Don't restore system apps with titanium backup! Only data apps (apps from the market)
CM is great good choice. I love the theme engine CM10 has and all CM10 based roms.
I'll tell you a super easy way to backup your IMEI! Need Root!
Download (terminal emulator)
Enter these commands. su (hit enter)
reboot nvbackup (hit enter)
It will reboot and create the backup on a built in backup partition on your SD card. The only way you could delete the backup is if you formated your SD. Super easy I just hope it works lol....
Sent from my SCH-I535 using xda premium
Two quick questions before I take the final plunge.
1. Is the CWM backup to external flash function sufficient, or do I need something further for a true backup? (It says "Nandroid" in one part, but otherwise I'm not sure if it's truly "Nandroid." It seems like it just backs up each individual file or something and I get the impression that Nandroid is more of an image of the firmware? If it isn't sufficient, what should I use?
EDIT: Found this tutorial. Basically that's what I've done except instead of bothering with Odin I used the EZ-Recovery app to flash CWM directly from the phone itself (along with EZ-Unlock 1.2 from here to unlock the bootloader) as per another tutorial. The other tutorial just didn't call it a "Nandroid" backup, so I wasn't sure.
2. If anything goes wrong, is there a stock ROM image I can use for the Verizon SCH-I535 with Odin? So far my searching has taken me to a site that practically has every stock ROM for the SGS3 but that one... (Or at least if it has that one I couldn't find it on there, which isn't saying much since every single region was listed separately...)
The best way to get recovery is to get the latest recovery from the man who's created them all from the very beginning.
Get rom manager and flash the latest straight from that app. You must make sure your bootloader is unlocked. If you took the latest OTA from Verizon it locked your bootloader.
As long as your unlocked and rooted you can go straight in rom manager and flash touch recovery especially for your Verizon galaxy s3.
I've been using the latest touch recovery on my D2tmo, nexus 7,galaxy nexus and Asus infinity and it's worked perfect.
Make a backup of your current rom for safety before flashing. You can create a backup and rename it to whatever you want straight from rom manager!
I personally wouldn't back up to the external. It might work fine but when it comes to backups I just go straight to the internal
Sent from my SCH-I535 using xda premium
---------- Post added at 08:33 AM ---------- Previous post was at 08:26 AM ----------
I soft bricked my phone because after taking the latest OTA it locked my bootloader! Recovered it fully from here
http://forum.xda-developers.com/showthread.php?t=1840030
I seen the take to your local Verizon store bla bla bla.
Got in download mode at 4am and recovered in 15 minutes.
I wish I had someone that knew what I now know and that's why I'm here to help my fellow members!
Sent from my SCH-I535 using xda premium
Hehe, funny thing about that. It tried to automatically update without bothering to ask. I presume because I had the FWupdate app frozen (for I guess fairly obvious reasons) it utterly failed and then complained, then demanded that I update again after a while, giving me an option to defer it. (I never did figure out how to get it to stop pestering, but I guess that's a non-issue.) So I didn't ever get a locked bootloader simply because it failed to do what it was trying to do.
Anyway, I've installed CM10 and so far so good. Well, I gave myself a good scare by forgetting to do a factory reset (*sigh* I wish I didn't have to do that, but, after all, it's a significant change going from a highly modified VZW infested ICS to a cleaner custom Jelly Bean) and it sat there stuck on the boot logo until I reread the instructions and rebooted to fix it (at least CM doesn't wipe out the CWM recovery like the stock ROM does...) I still have a LOT to do to get everything all reinstalled and reconfigured. I'm not going to be able to finish it all tonight, so won't really be able to comment about the results of the switch until tomorrow I guess. It's not helping that it's taking absolutely forever to download the Google Play package and all (and then I get to redownload a lot of the apps, though hopefully TitaniumBackup can safely restore a lot of it.)
EDIT: BTW, is it just me or do they really REALLY need to provide basic info on how to do simple tasks like the actual installation process itself, installing Google Play, and etc? I'm no stranger to googling for info, but wow what a pain to figure this all out (especially it never occurred to me that the gapps zip would have to be installed using CWM. I thought it was for the firmwares themselves only, not them and apps...)
EDIT2: Oh wow. I had no idea how much work this was really going to be! I said before that a full ROM install is something I wanted to do once. Well, I definitely want to never do this again. I'm having to fight all sorts of things. Google didn't even want to recognize my phone at first despite successfully connecting my accounts and registered apps such as, oh, I don't know, Titanium Backup Pro just for instance weren't showing up as already purchased... -.- I think I finally got it all restored and they now properly show up as owned, but I've lost hours just fighting with all of these various things...
It also seems to have serious issues with my WiFi. I haven't figured out what is going on exactly, but it seems like I'm having to turn wifi off and on a bit to get it to properly connect again -- I've put in my password so many times I'm about to go absolutely insane (unfortunately, for various reasons I'm still stuck on WEP 128-bit, so I have to type in a large hexidecimal encryption key and I'm just about ready to go postal.) Hopefully once everything is finally all setup and configured all will be well, but at the moment I've lost a pretty good bit of sleep while fighting this and barely have it up and running. I probably should have waited for an off day to do this.
Nazo said:
Hehe, funny thing about that. It tried to automatically update without bothering to ask. I presume because I had the FWupdate app frozen (for I guess fairly obvious reasons) it utterly failed and then complained, then demanded that I update again after a while, giving me an option to defer it. (I never did figure out how to get it to stop pestering, but I guess that's a non-issue.) So I didn't ever get a locked bootloader simply because it failed to do what it was trying to do.
Anyway, I've installed CM10 and so far so good. Well, I gave myself a good scare by forgetting to do a factory reset (*sigh* I wish I didn't have to do that, but, after all, it's a significant change going from a highly modified VZW infested ICS to a cleaner custom Jelly Bean) and it sat there stuck on the boot logo until I reread the instructions and rebooted to fix it (at least CM doesn't wipe out the CWM recovery like the stock ROM does...) I still have a LOT to do to get everything all reinstalled and reconfigured. I'm not going to be able to finish it all tonight, so won't really be able to comment about the results of the switch until tomorrow I guess. It's not helping that it's taking absolutely forever to download the Google Play package and all (and then I get to redownload a lot of the apps, though hopefully TitaniumBackup can safely restore a lot of it.)
EDIT: BTW, is it just me or do they really REALLY need to provide basic info on how to do simple tasks like the actual installation process itself, installing Google Play, and etc? I'm no stranger to googling for info, but wow what a pain to figure this all out (especially it never occurred to me that the gapps zip would have to be installed using CWM. I thought it was for the firmwares themselves only, not them and apps...)
EDIT2: Oh wow. I had no idea how much work this was really going to be! I said before that a full ROM install is something I wanted to do once. Well, I definitely want to never do this again. I'm having to fight all sorts of things. Google didn't even want to recognize my phone at first despite successfully connecting my accounts and registered apps such as, oh, I don't know, Titanium Backup Pro just for instance weren't showing up as already purchased... -.- I think I finally got it all restored and they now properly show up as owned, but I've lost hours just fighting with all of these various things...
It also seems to have serious issues with my WiFi. I haven't figured out what is going on exactly, but it seems like I'm having to turn wifi off and on a bit to get it to properly connect again -- I've put in my password so many times I'm about to go absolutely insane (unfortunately, for various reasons I'm still stuck on WEP 128-bit, so I have to type in a large hexidecimal encryption key and I'm just about ready to go postal.) Hopefully once everything is finally all setup and configured all will be well, but at the moment I've lost a pretty good bit of sleep while fighting this and barely have it up and running. I probably should have waited for an off day to do this.
Click to expand...
Click to collapse
Strange that you are having so many issues. First off, when I flash a new ROM I put the ROM and the latest GApps on the sdcard. Do a factory reset, clear dalvik cache, install the ROM then the GApps. As far as wifi, I didn't have a problem when I ran CM10, but maybe there is something messed up in the latest version. Are you running the nightlies or the M versions?
The M version from the link above (the 2012 10-11 one.) At first I thought the issue I was having was the one from before where it would decide that my network with the hidden SSID was out of range automatically the moment it lost connection (either me leaving the area or turning off WiFi) but I not only tried to use the hidden SSID enabler, but also even went so far as to just re-enable the SSID broadcast on the router, so it's no longer hidden. It seems like it's having troubles initializing the WiFi. Maybe I somehow managed to freeze/remove an app that did something or other along these lines (though I just can't see how given that it can work, it just has issues.) I'm having to turn it off and on once or twice to get it to finally reconnect. I guess it's not bad since I have the power widget in the notifications tray that makes this a bit easier, but that doesn't make this any more fun at all to deal with. EDIT: In fact, whereas the hidden SSID issue I ran into previously had it just show up as being out of range after it lost the connection until I "forgot" the network setting and reconfigured it again, it looks like nothing shows up at all until I turn it off and on -- but I don't have to redo the network setting, so this is definitely a completely different issue. I think actually it's like it's just not correctly enabling the wifi on startup if it was left on when I rebooted so I have to turn it off and back on to get it to truly turn it on in the first place.
And yeah, I cleared the cache and did a factory reset before installing. Well, bear in mind that it naturally was showing up as a different device and all. So some initial configuration was definitely going to be required to even get started, and I was switching from ICS to JB (and completely different sorts of ROMs besides) so some initial fight was inevitable even if CM10 were the most established and stable build ever made just going from the one to the other. Actually, one interesting feature of Titanium Backup Pro (once I finally got it to recognize that I had the Pro version in the first place) is apparently the ability to change the device ID to seem to be the same as far as installed programs and such go, so now Google Play among other things thinks this is the same exact device as before now as opposed to being a new device. It's actually weird because the "new" one doesn't even show up on Google Play's settings anymore (and Google still hasn't gotten around to fixing it such that we can remove devices, so I still have my old Archos 43 PDA listed in there for instance.) Between everything, Google now is letting me once again access my software without re-buying or relying on backups (which is especially good because a few things seem to just get stuck when I try to restore them -- it just sits there forever, not ever really installing.)
BTW, I lost all the Verizon-specific special numbers such as *86 for voicemail. Apparently CM10 doesn't bother to list them (but then as they are vendor specific I guess that's not a big surprise.) Is there any sort of list of the numbers Verizon uses out there -- maybe even including whatever special numbers that might be more specific to this phone itself (such as that hidden menu or whatever)?
EDIT: Ok, so far things are starting to come together slowly but surely. One oddity though, I noticed at the end of my work shift that, rather than the usual 10% or so of battery time lost, it seemed to have lost about 20%. I wouldn't go so far as to say it's double -- it might be more like 15% many times -- but it is very odd all the same. I thought I was seeing a bad trend along these lines last night, so went ahead and put SetCPU back on there with the profile to do powersaving and serious underclocking when the screen is off and in both cases I used the "conservative" CPU governor for the normal use with the maximum CPU speed at about 1GHz (conservative is supposed to be like ondemand with a better tendency towards power saving at the expense of taking longer to scale the CPU upwards when needed.) As this is CM10, there should be no room for doubt that the CPU is being scaled down -- in fact in the performance menu I often see the CPU at a mere 384MHz (which is my minimum setting) -- so I'm just not sure what to think just yet. The settings menu for the battery life shows mostly just basic system processes like the screen, idle, and etc being the main culprits for battery usage, so again odd since the screen is the main thing yet is off during my working hours (with the very short exception of my breaks.) I don't think the automatic brightness setting is any higher or anything either and, in fact, configured it to use generally lower settings until the maximum brightness.
Guess more tweaking and testing is needed to be sure, but it's odd all the same. If anything CM10 is running LESS all the time by way of hidden services and such (though as far as things that actually show up in the likes of Android Assistant I'm having to fight far more things including an "analog clock" that isn't even in the app list so I'm hoping is just the normal clock despite the fact that "analog clock" in normal firmwares is actually a separate extra thing.) Guess I'll still have to wait and see to some extent.
Edit2: Haha, I just read that you have to recalibrate the battery meter after flashing, so it'd probably just not being very accurate is all. I grabbed an app to help do that so hopefully this is all that was going on (and if I go by Android Assistant's voltage status I'd say that it definitely is off.)
Edit3: (Just kind of adding as I go along here.) Now that all the basics are in place and I had some time and the desire to drain the battery more quickly (as part of the recalibrate process you're supposed to drain it until it automatically shuts down) so I plugged in my headphones and started listening. So far so good. I was really hoping that one of the advantages of a custom ROM would be a more precise volume control (Google really dropped the ball on that one! Sometimes you're trying to get it just right and end up stuck between either a bit painfully too loud or annoyingly too quiet with no in-between) but other than some dissapointed wishful thinking, it seems sound-wise this release of the SGS3 CM10 is just fine. I don't really hear any bloat or distortion in the bass and in general the usual modifications that they do to the sound just aren't there (or at least if they are they are subtle enough to fool my, let's say "bronze" ears since I'm definitely at the bottom of the audiophile chain, lol.) In one thread where someone asked how the Qualcom compared to the Wolfson sound-wise someone said it was a bit tinny, but if it is it's far too subtle for me to notice (and this is bearing mind that these are headphones with a slight bass roll-off, so it does seem like I'd notice any significant loss in the lower ranges pretty quickly. In this respect I'm happy or at least satisfied that nothing has gone wrong.
Also, one way or the other the wifi issue seems to have gone away. I'm guessing it was an app I had frozen that I reenabled, but that's just a guess. It's so hard to be 100% sure with these things unless you apply a long painful scientific process every single step of the way...
I'm STILL trying to figure out a way to configure the haptic feedback level. It seems to be all on or all off with no ability to reduce strength of feedback that I've found so far.
Another word to the wise, backup your imei. Not sure if that was mentioned yet
Also, your ROM will work better after a charging cycle or two. It will initially scam for media and such I believe which maybe part if the reason you're seeing slightly higher usage at first. Also, in general you'll get slightly less battery life on aosp. I don't find much use in most battery stats though. They're easily manipulated.
Sent from my Galaxy Nexus using xda app-developers app
Well, I had a small accident. I was replacing some fonts and manually selecting which ones to replace with what when I threw in Arial Unicode and another font that was still slightly large. I'm assuming because the font files were so big, but it completely stopped booting. After fighting with it for hours upon hours (and I have since found what might be a font zip file for CWM now that it's far too late to do me any good -- though of course it would have had to replace those particular fonts and it seems like most of my attempts to replace them ended up replacing everything but them.) I just couldn't get a driver to install for the phone while CWM was running (I don't know if you can maybe get an adb shell or what, but without the driver you obviously can't.) In the end, I ended up having to reformat and reinstall CM10 from scratch. So far (knock on wood) none of the real problems I was having before have really repeated. (And this time around I just kept my font changes minor and no gigantic overkill fonts.) Sadly, TitaniumBackup can't restore all apps it seems (it just sort of freezes on some) but overall I've managed to restore most of it. I was waiting to make a backup in CWM until I had fully gotten everything configured and running the way I wanted it. Guess I should have done one sooner, but now I'm close to the original goal of having it basically right where I want it before making the backup (thank goodness TitaniumBackup at least was able to get the bulk of the work. And I love how it can even restore the device ID so that as far as everything is concerned this is the same phone I've always been using.)
It does still have a worse battery life compared to the stock ROM, but I guess it's not too bad. Still better than most phones no matter how you look at it. I'm not entirely sure it wasn't the battery being somewhat at fault though. I was using a third party battery by Anker. By the feel of it, it actually is surprisingly dense for a third party battery -- it weighs about the same amount as the stock battery -- so it might actually have a pretty good capacity, but at the same time I'm not 100% sure it truly is every bit as good. At first it certainly seemed to be, but maybe it's starting to wear down more quickly overall. For now I guess I'll switch back to stock (my original plan was to just store it at some 70% or so capacity so it should last and then punish these two third party batteries, but now I guess I'll consider them to be the backups instead. I don't like that the charge goes as high as 4.33V or so though. 4.2V is supposed to be considered pushing things pretty hard as it is, so I have a bad feeling about the overall lifetime of these batteries...) Again I have SetCPU hopefully helping out a bit (I like that CM10 has options for this that it can set on boot, but it doesn't have any other options than that and I like how I can have SetCPU actually lower things much further while the screen is off. I don't care if some processes take longer to, well, process while the screen is off after all, so there's no reason not to use a lower CPU setting IMO.) Actually, I was beginning to become quite concerned because the battery was actually going down just doing a few basic things like restoring backups while plugged into the charger despite having the governor on conservative, the maximum CPU frequency at 1066MHz, and the I/O set to SIO (which at least one person claims is better, though I wasn't 100% convinced from what little I could tell -- if anyone has any suggestions for the best balance between battery life and performance in this respect I'm curious. I try to keep it on something that kind of scales so that games and such still work fine without me having to change it specifically for each or something while it could still at least not kill the battery when it's not being pushed as hard.)
Interesting thing about the whole WiFi thing. I read on one thread where someone suggested changing the device name (in the developer options) to no longer have a dash in it to stop the intermittent WiFi dropouts. It's kind of ridiculous and should have absolutely no effect whatsoever on this, but so far it actually seems like it might have worked. Again, knock on wood... It's odd though because I never had that trouble with the stock firmware (then again, for all I know it didn't have a dash in its default device name and I doubt I ever changed it if it was even an option though I can't really remember one way or the other if I could have.) I won't know for sure for a while as it was kind of random before, but so far it's looking promising at least. And I haven't had any trouble with it picking up my network yet either.
BTW, I forgot to do the IMEI backup before somehow. Is it too late to for it to be any good now? I know, I know, but I was a bit excited about the prospect of going to CyanogenMod 10 in the first place and just forgot along the way I guess. I went ahead and ran it ("reboot nvbackup" from the terminal anyway -- it sure would be nice if it actually properly shut down first instead of doing a cold reboot -- but other than some tiny blue text in the corner that might or might not have said something to the effect of that it was making a backup it just flashed by and booted up normally. I was expecting a recovery menu or something.) But I don't know if it's going to do any good to have run it now. Is there anything other than the IMEI itself contained in that data that I should be concerned about? I think the IMEI is correct still (I checked the numbers in the settings at least and they seem to correspond to what I wrote down from under the battery) but I'm not sure about anything beyond the numbers themselves.
Nazo said:
Well, I had a small accident. I was replacing some fonts and manually selecting which ones to replace with what when I threw in Arial Unicode and another font that was still slightly large. I'm assuming because the font files were so big, but it completely stopped booting. After fighting with it for hours upon hours (and I have since found what might be a font zip file for CWM now that it's far too late to do me any good -- though of course it would have had to replace those particular fonts and it seems like most of my attempts to replace them ended up replacing everything but them.) I just couldn't get a driver to install for the phone while CWM was running (I don't know if you can maybe get an adb shell or what, but without the driver you obviously can't.) In the end, I ended up having to reformat and reinstall CM10 from scratch. So far (knock on wood) none of the real problems I was having before have really repeated. (And this time around I just kept my font changes minor and no gigantic overkill fonts.) Sadly, TitaniumBackup can't restore all apps it seems (it just sort of freezes on some) but overall I've managed to restore most of it. I was waiting to make a backup in CWM until I had fully gotten everything configured and running the way I wanted it. Guess I should have done one sooner, but now I'm close to the original goal of having it basically right where I want it before making the backup (thank goodness TitaniumBackup at least was able to get the bulk of the work. And I love how it can even restore the device ID so that as far as everything is concerned this is the same phone I've always been using.)
It does still have a worse battery life compared to the stock ROM, but I guess it's not too bad. Still better than most phones no matter how you look at it. I'm not entirely sure it wasn't the battery being somewhat at fault though. I was using a third party battery by Anker. By the feel of it, it actually is surprisingly dense for a third party battery -- it weighs about the same amount as the stock battery -- so it might actually have a pretty good capacity, but at the same time I'm not 100% sure it truly is every bit as good. At first it certainly seemed to be, but maybe it's starting to wear down more quickly overall. For now I guess I'll switch back to stock (my original plan was to just store it at some 70% or so capacity so it should last and then punish these two third party batteries, but now I guess I'll consider them to be the backups instead. I don't like that the charge goes as high as 4.33V or so though. 4.2V is supposed to be considered pushing things pretty hard as it is, so I have a bad feeling about the overall lifetime of these batteries...) Again I have SetCPU hopefully helping out a bit (I like that CM10 has options for this that it can set on boot, but it doesn't have any other options than that and I like how I can have SetCPU actually lower things much further while the screen is off. I don't care if some processes take longer to, well, process while the screen is off after all, so there's no reason not to use a lower CPU setting IMO.)
Interesting thing about the whole WiFi thing. I read on one thread where someone suggested changing the device name (in the developer options) to no longer have a dash in it to stop the intermittent WiFi dropouts. It's kind of ridiculous and should have absolutely no effect whatsoever on this, but so far it actually seems like it might have worked. Again, knock on wood... It's odd though because I never had that trouble with the stock firmware (then again, for all I know it didn't have a dash in its default device name and I doubt I ever changed it if it was even an option though I can't really remember one way or the other if I could have.) I won't know for sure for a while as it was kind of random before, but so far it's looking promising at least. And I haven't had any trouble with it picking up my network yet either.
BTW, I forgot to do the IMEI backup before somehow. Is it too late to for it to be any good now? I know, I know, but I was a bit excited about the prospect of going to CyanogenMod 10 in the first place and just forgot along the way I guess.
Click to expand...
Click to collapse
No your OK you can get your IMEI underneath where your battery is. There's a tutorial on YouTube
Sent from my SCH-I535 using xda premium