Develop Bugs

Returning EVO unless....

Unless someone knows why I keep getting these errors now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the large imgs but I'm not able to shrink them on my iPad right now.

Zethmir said:
Unless someone knows why I keep getting these errors now.
Sorry for the large imgs but I'm not able to shrink them on my iPad right now.
Click to expand...
Click to collapse
If I was you and having these problems, the first thing I would do would be to run the RUU and get back to stock. Easiest way to find out if it's the Rom or the phone.

in ur settings to a factory reset

You are on a rooted phone and you are going to return it due to errors that might be a result of the root?
No root and I mean no ROOT is perfect and each phone can act differently. Try to reflash again and clear out all your data/cache and try it again.
Try another ROM just to see.

Yet another user error. This is YOUR fault. Heck they could report your to HTC if they didn't like you.

WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.

I'm still confused as to why anyone would ever return this phone except for physical damage(screen ripping off). Everything software based can be fixed. And its only been 2 weeks. In another 2 weeks, we'll probably have Gingerbread running on this thing. The devs here are simply just amazing. Hell i got these errors BEFORE i rooted. So I'm guessing it was just the network being raped by a new device. I haven't seen them for awhile now.

WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
Click to expand...
Click to collapse
Whoa whoa whoa hey now... can I have a job?
-------------------------------------
Sent via the XDA Tapatalk App

Zethmir said:
WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
Click to expand...
Click to collapse
You asked people to make assumptions, so thanks for being so offended by it. You come here with an immature ultimatum, "Help me or I'm sending this back!" and give us no other information. Only your signature gives any information about your phone, "rooted." Now you fly off the handle and insult everyone.

Probably because your an apple fanboy and god hates you.

It has nothing to do with being a "noob" or "super cool neeto phone pro". I has to do with the ultimatum of returning a phone that you messed up.
Everything will be ok.

Zethmir said:
Unless someone knows why I keep getting these errors now.
Sorry for the large imgs but I'm not able to shrink them on my iPad right now.
Click to expand...
Click to collapse
Yeah, I'd like to know where in your original post we could safely assume you knew what you were doing. You gave absolutely NO information, except that you have no patience. This is a developer's forum, which means if you don't give out useful information that people can use to help you, they're going to assume you don't know what you're doing.

I simply asked if anyone knew about these errors. I didn't say fix them.
BTW if I was an Apple fanboy I would have preordered a iPhone 4 instead of the EVO. But sorry your way off on that lol. I am just a gadget person. My iPad and MacBook are for work and school. Heck if I wouldn't be getting so much for my student loan I would of never gotten either, well maybe the iPad because it was a great replacement for the iPhone.
I am going to stick with android, and going to go buy a Nexus One. I am thankful for your guys help, sorry if I offended anyone but it just struck a nerve. This is the reason I don't post on forums often for help. Anyways I will keep an eye on the EVO for future possible purchase. I guess when it came down to it, the screen issue (separation and faulty grounding), the meh battery life (I didn't say it was bad it was just sub par), the 30fps limit (which shows), and the poor service in my area were the downfalls for me with the EVO.
I hope you guys all have better luck then me and enjoy your great phone.

I love that your screen shots show the Evo battery as yellow. Thats the only color my battery ever is...
Im wondering why you didn't just exchange the phone for a new one if you suspected a hardware problem?

Zethmir said:
I am going to stick with android, and going to go buy a Nexus One. I am thankful for your guys help, sorry if I offended anyone but it just struck a nerve. This is the reason I don't post on forums often for help. Anyways I will keep an eye on the EVO for future possible purchase. I guess when it came down to it, the screen issue (separation and faulty grounding), the meh battery life (I didn't say it was bad it was just sub par), the 30fps limit (which shows), and the poor service in my area were the downfalls for me with the EVO.
I hope you guys all have better luck then me and enjoy your great phone.
Click to expand...
Click to collapse
The screen separation isn't rampant, and a silly reason to dump the phone if you're not suffering from it.
I have a Nexus One and an EVO 4G. I also have every version of the iPhone from day 1, and should be receiving an iPhone 4 this afternoon if FedEx delivers as promised, so I can speak to each of these with some experience.
I think you'll be EXTREMELY disappointed in the Nexus One if you switch to it after having an EVO 4G. The Nexus One's screen is over-saturated and biased towards too much, I mean TOO MUCH, red. The camera puts a large pink blurred circle into every picture you take. The touch input is very flakey, regardless of ROM you use. It's almost impossible to type accurately on it unless you install Swype or ShapeWriter. It's extremely difficult to see the screen outdoors - I couldn't even get a podcast playing while walking to lunch the other day until I found a big shade tree to stand under. Battery life on the Nexus One is probably the worst of any phone I've ever owned, though that may be a network lack of signal issue (T-Mobile). Speaking of T-Mo, if you get T-Mobile version instead of AT&T you can look forward to lots of missed calls and lots of no 3G coverage areas.
The Nexus One has some great features, including the awesome speaker phone and noise canceling mic, a beautiful hardware design that puts even the legendary styling of iPhones to shame, and it fits great in your hand. And don't forget the fantastic ROMS by Cyanogen and Modaco, but if you're not happy with an EVO 4G I think we'll see you posting over in the Nexus One sections soon enough with some ultimatum about "fix the touchscreen or I'm returning this phone" or some other such issue.
Good luck with whatever phone you pick, because with Android phones, there's ALWAYS some glitch or flaw with the phone that will annoy you, and there's ALWAYS a much better phone coming out next month or two (Droid, then N1, then Desire, then EVO, and upcoming Galaxy S). iPhones have issues too, but at least with your iPhones you don't have to worry about a new better model but once per year - but then you have far fewer options for hacking and the latest hardware. ;-)

Zethmir said:
WoW just wow. You talk to me like I am the biggest noob on the forums.
For your information the root was fine for over 2 weeks and this just started last Friday. I had a launch evo and rooted it the first day it was available. Also I flashed back to stock ruu and had the same problem.
Maybe before you open your mouth and let the **** flow out ask yourself a simple question : Is my comment going to help or just make me look like an ass.
Also I would like to comment on the fact I am pretty good at phone jailbreaking and rooting. I know how to read guides and I have been doing this kind of stuff since the pocket pc's. I have never ran into a much ruder group then the people that posted on this topic. Heck even a rom dev talked to me nicer then you guys did when I asked about a project he hadn't worked on in months.
I have returned my EVO but haven't lost hope in you guys. Just let me know if you guys ever apply at my work so I can avoid you at all costs.
Note: This only applies to the ones that deserve it. Thanks for mentioning the stock RUU Roman G, and for mentioning the factory reset toenail78. I had already tried that but to no avail. Also note I even told the store I rooted the phone and flashed it back to stock and neither worked and they were just as puzzled as I was. I am not your 15 year old teenager, but thanks for treating me like one.
Click to expand...
Click to collapse
I know it's too late to help in this instance, but in the future try asking your questions over at ppcgeeks. They play nicer over there. Most of us here on xda seem to have personality problems and can't play too well with others. You said you might try a nexus one. I have one of those too. I prefer the Evo hands down... If I were you I would go back to Sprint and buy another Evo, You will be much more satisfied down the road. Don't let these folks get under your skin!!

i know its a late reply but ill post anyway. i had the exact same problem. a sprint tech helped me out and called me throughout the day to see if it was working. basically he helped me do a reset of the phone to attempt a fix of the low reception. after that we had to grab a tower and because the tower was down i was getting the exact same problem as OP.
he noted that the phone couldnt be processed in the system yet because of the tower so he would call me and let me know if it went through or not. and if it did to continue troubleshooting it.
i kept on trying all day and it went through a couple of minutes before he called me as if he knew i got through. then it was fixed.
dont remember what we did because we entered a bunch of numbers in the dialer, but i know we reset everything and updated everything. it was durring the update that was causing the problems and recurring errors like what the OP had.
if its rooted id say update but i dont know which not to update since you could lose root. i would unroot, run all updates and register phone automatically and if it works then root. if not call tech and see if it can be registered automatically somehow. when it works, root.
just posting this for future reference because i didnt see anyone mention something like this here

My Story

Alright... So there I was, walking through the wilderness, all alone.. When all of the sudden..
Just kidding. Okay, so I was running AOKP for a few days (Awesome ICS rom by the way, for those looking). I was trying to figure out why my MMS.apk was cutting me off at 160, instead of going to page 2. I asked about it and a lovely gentlemen told me that I needed to flash the Mirror'd link because it supported SMS split (or something along those lines). Okay, awesome. I downloaded it to my SD card, boot into Rogue Recovery and flash it. I was watching something on TV (can't remember what it was). About 3 minutes go by and there was no real sign of progress from the phone. Me, being distracted by the TV and not thinking, decided to restart it and try to flash it again. I held down the volume down and power, and attempted to reboot recovery in the middle of a flash. OPPS.
Phone shut off. I tried to turn it back on, and all I got was a pretty blue light from the LED. There was no sign of anything on the screen, at all. No button combination worked. Download mode, recovery, nada. I pulled the battery (duh) and it still did nothing. I researched how to fix brick's and found a tutorial by another wonderful gentlemen explaining a USB Jig (I hadn't heard of such a device). He walked through how to make one. I accepted the challenge. Tore apart a phone charger I had, soldered 300k oHm resistors in a series from 4-5, and crossed my fingers. Pulled the battery, plugged in my home-made Jig AND... Nothing. Actually, that's a lie, it made the pretty blue light come back on. Not quite the outcome I was hoping for, but still pretty cool, right? Whether I made the Jig incorrectly or not is debatable, I hadn't made one before, so it's possible I did something wrong, but the phone did recognize something being plugged into it, so that's kind of cool.
Anyways, phone still wouldn't do anything. I called the Sprint store and they closed at 8:00pm, it was 7:45. Got in the car, 110mph on the highway and walked in the door at 7:57. I figured he would be completely unhelpful since I walked in RIGHT before he closed, but he was actually really cool. He was a new guy too, which helped tremendously. I handed him my GS2 and told him that it was "Not working anymore". I told him that "The screen won't come on. The only thing that works is that LED at the top, which as awesome as that is, doesn't help with the whole 'phone' aspect." He asked when it started doing it. I told him that "It started earlier this morning. I thought maybe it would straighten itself out. I'm new to this whole 'smart phone thing'." He laughed at me and asked if I had downloaded any new apps or if the phone had updated. I said, "No sir. I woke up this morning, was running late for something. Jumped in the shower and when I got out I pulled my phone off the charger. That blue light always came on when the phone was fully charged, so I didn't suspect anything. I walked out to my car and tried to turn the screen on and it wouldn't do anything. I have no idea what caused it to do that. Maybe it over heated?..." He said "Man, that's strange. These are really good phones, I haven't ever heard of one doing that before." Then, the words that I wanted to here.. "Here's what's going to happen Mr. Kuhns. I'm going to do an Advanced Exchange. You have insurance, so that's covered. Can you sign *here* and *here* please."
My new phone will be here on Friday. If not Friday, then it will ship to the store on Monday. I ordered a USB Jig from Ebay for $5 and it will be here around the same time, so if this happens again, maybe I can save myself the hassle.
I know this is a REALLY long and drawn out story, but I wanted to share in case some of you had a similar situation, or wanted to know what I said in order to talk him into getting me the new phone. I thought about trying to pull the "Can I have a white one..?" card, but didn't want to push my luck. I may bring it up when I go in Friday. Oh, and in the mean time, I have to use an old Black Berry 8703e. It's not AWFUL, but it's pretty ****ing close. Only a few more days and I'll have my baby back.
Also, I was serious about AOKP. Those of you looking for an ICS rom that is customizable and smooth, you aren't going to find one right now that can do better than AOKP. There are plenty of customizations, and the rom runs super smooth. I can't really tell you about battery life. I run a 3800mAh battery, so I don't really pay attention, but it really is an awesome ROM. Check it out if you're into the ICS game.
Here's a shot of the BB I'm currently on. Pitiful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Cool story bro.
Too long to read tho

yeah i dont feel like reading all of that.

I ended up reading it. Felt guilty for poking him.
Its got all the makings of a great movie. Random opening scene. Drama, intrigue, a plot twist... Hell, its even got a teaser at the end hinting at a sequel!
Sadly, no gratuitous frontal nudity.

No sexy girls? No sex or stripers party? Hellz no! How dare you!

Answer to your question
If you try that again at the moment with the new phone it will probably have the same result. For now the general consensus is to not recommend flashing anything by CWM while the ICS kernel is installed. Instead, use ODIN or Mobile ODIN to flash a GB kernel (such as EL26/EL29)
That *might* be subject to change soon so do keep an eye on a couple of threads such as the "How Not to Brick Your E4GT" stickied at the top of this forum. It will be one of the first to be updated should the situation change.
Glad you got your phone swapped out though.

Lmao. Glad you enjoyed the story. There was some serious thought put into that writing. As for flashing in GB, I knew that.. and I read about that.. but there was that whole "I don't need to do that.. That's stupid" thought, and well... Yup, this Black Berry is dreadful. From now on, or until an update is out.... Flash ICS with GB. Lol don't try to rebel, your phone will give you the finger.

That blackberry is horrid but its better than nothing :thumbup:
Sent from my SPH-D710 using xda premium

AAAAHHHH!!!

Easy AE at any Sprint service center - just make sure you can't get into download mode. If they can't verify your ODIN count, then you have no way to prove that you rooted it, flashed any custom kernels, etc.
Worked great for me, and I used to work for Sprint, so I know for a fact that this method works - as long as there's no physical or board-level damage, make sure you can't see the ODIN count and you're golden.

Everyday Legend said:
Easy AE at any Sprint service center - just make sure you can't get into download mode. If they can't verify your ODIN count, then you have no way to prove that you rooted it, flashed any custom kernels, etc.
Worked great for me, and I used to work for Sprint, so I know for a fact that this method works - as long as there's no physical or board-level damage, make sure you can't see the ODIN count and you're golden.
Click to expand...
Click to collapse
Good to know. I ordered that Jig for future uses, but hopefully I won't have to use it.
This BB is awful. If I get a MMS, it texts me a link that I have to load in the browser, and the browser is unGodly slow. It's all around dreadful. Not to mention EVERYTHING was on that GS2. You don't really realize what you have until it's gone. Lol music, pictures, work schedule, notes.... The list grows each day I go to find something. -_-

And it is possible you made the jig right. In that type of situation with the blue led hard brick a USB jig won't work.

MeWarning said:
And it is possible you made the jig right. In that type of situation with the blue led hard brick a USB jig won't work.
Click to expand...
Click to collapse
That would make sense. I will admit, I'm not entirely sure what the difference is between a hard and soft brick. I assumed a hard brick would be absolutely no response from phone at all, and the blue LED made me think there was a light at the end of the tunnel.
Apparently not. :/

Just another blue light of death horror sorry containing AOKP/AOSP+ICS+CMD9. My friend i have done it all on cwm rougue. From flashing ICS ROMS to wiping and restoring. Now the only 2 times I've used cmd9 (luckily i was on GB) and nearly bricked both times. First time i was on a rogue kernel and flashed to cmd9. seemed ok, then my phone randomly crashed. Tried to reboot and went to blank black screen with only blue light. Tried to restore and my recovery looked like a mix of rogue and cwm9. Didn't work anyhow. So tried to reboot and threw me into a boot loop. Luckily it went into download mode. Tried to Odin to stock GB- failed. Tried Odin again, boot loop + yellow triangle that it didn't have before. Odined back again-passed and booted. Whew. That was on gb. I'm sure i would have bricked had i been on ICS at that time. I won't even tell you about the other time with cmd9. Anyway i realized that you need to Odin between cmd and anything else and before flashing but while on stock one should do a full wipe and factory data reset. And if on ICS Odin back to GB before wiping or backing up or flashing. Sorry bud but i respectfully disagree with you about cmd9. You already bricked one device. Hope you learned something by this experience. Good luck with your new phone man. Oh and one more thing, of you update to GB or ICS it z also updates your boot loader. Everything after eg30 has an updated boot loader and your jig won't work. You would have to flash the eg30 boot loader to whatever ROM you're on prior to abrick. And still no guarantee. So hopefully you won't have to do the walk of shame back into sprint.

timmetal6669 said:
Just another blue light of death horror sorry containing AOKP/AOSP+ICS+CMD9. My friend i have done it all on cwm rougue. From flashing ICS ROMS to wiping and restoring. Now the only 2 times I've used cmd9 (luckily i was on GB) and nearly bricked both times. First time i was on a rogue kernel and flashed to cmd9. seemed ok, then my phone randomly crashed. Tried to reboot and went to blank black screen with only blue light. Tried to restore and my recovery looked like a mix of rogue and cwm9. Didn't work anyhow. So tried to reboot and threw me into a boot loop. Luckily it went into download mode. Tried to Odin to stock GB- failed. Tried Odin again, boot loop + yellow triangle that it didn't have before. Odined back again-passed and booted. Whew. That was on gb. I'm sure i would have bricked had i been on ICS at that time. I won't even tell you about the other time with cmd9. Anyway i realized that you need to Odin between cmd and anything else and before flashing but while on stock one should do a full wipe and factory data reset. And if on ICS Odin back to GB before wiping or backing up or flashing. Sorry bud but i respectfully disagree with you about cmd9. You already bricked one device. Hope you learned something by this experience. Good luck with your new phone man. Oh and one more thing, of you update to GB or ICS it z also updates your boot loader. Everything after eg30 has an updated boot loader and your jig won't work. You would have to flash the eg30 boot loader to whatever ROM you're on prior to abrick. And still no guarantee. So hopefully you won't have to do the walk of shame back into sprint.
Click to expand...
Click to collapse
Good to know. The walk of shame isn't too bad as long as you have a decent story backing it up. I just pretend to know absolutely nothing about the phone at all. "Has the phone installed any updates or anything recently?" - "You know, I couldn't tell you. I barely know how to text on this thing. My friend does everything for me when it comes to technical stuff."
Anyways, hopefully I won't have to through with it again. Maybe I should just stick to a GB Rom until the bricks have cleared out. I'm not entirely sure though. I liked AOKP, but it's not worth resorting back to this BB while the Sprint people order my new one. Lol

funny...i just did the same thing tryin to get Aokp on my et4g(i wanted to try the tablet mod)...needless to say i bricked!..panicked...thought about how my warranty is surely voided,then about all the private pics and everything i lost(and that sprint might see..lol)..luckily i had a senior member kinda walk me thru the process of what to do and how to do it...used my touchpro 2 for a few days and my new et4g came in today!(about to root now..)..had to laugh while reading your post cause i thought about goin white too...decided against it when i saw the most feminine lookin dude i ever seen rokin a white iphone..haha...good luck and good flashing!

Pissed off at sprint

So I was under the impression that an OTA update required me to confirm yes or no if I wanted it or not. Apparently I was wrong. Sprint decided to push the ICS OTA to my phone last night, my phone which had MIUI on it. The phone is completely bricked, so my alarm didn't go off (Late for work) and now I have to go through the painstaking process of setting up a new phone from scratch. Fun, but annoying because I had JUST gotten my phone to where I was very happy with it. There will be a raging complaint in the sprint store today.

Don't tell them you had custom software on it. No warranty then if they want.

cknuth said:
So I was under the impression that an OTA update required me to confirm yes or no if I wanted it or not. Apparently I was wrong. Sprint decided to push the ICS OTA to my phone last night, my phone which had MIUI on it. The phone is completely bricked, so my alarm didn't go off (Late for work) and now I have to go through the painstaking process of setting up a new phone from scratch. Fun, but annoying because I had JUST gotten my phone to where I was very happy with it. There will be a raging complaint in the sprint store today.
Click to expand...
Click to collapse
People in the stores have no control over this whatsoever. All you are going to do is ruin the day of one innocent associate.
My question is, if it did this overnight, to where you didn't know it had happened, how can you be sure it was the OTA update? And is it truly completely bricked, or is it soft bricked, and one of sfhubs Odin files could fix it?
Sent from my SPH-D710 using xda app-developers app

cknuth said:
So I was under the impression that an OTA update required me to confirm yes or no if I wanted it or not. Apparently I was wrong. Sprint decided to push the ICS OTA to my phone last night, my phone which had MIUI on it. The phone is completely bricked, so my alarm didn't go off (Late for work) and now I have to go through the painstaking process of setting up a new phone from scratch. Fun, but annoying because I had JUST gotten my phone to where I was very happy with it. There will be a raging complaint in the sprint store today.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

lickarock said:
People in the stores have no control over this whatsoever. All you are going to do is ruin the day of one innocent associate.
My question is, if it did this overnight, to where you didn't know it had happened, how can you be sure it was the OTA update? And is it truly completely bricked, or is it soft bricked, and one of sfhubs Odin files could fix it?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
When I say "Raging" it's really not that much "raging"...I'm too passive to get worked up about stupid stuff..though when I woke up late for work I was full beast mode, good thing the sprint guys don't live at my house, also clearly not the guy at the stores fault.
All I can get is a blue light. No recovery. No Odin mode. No boot logo. My computer doesn't see it. It shows all the symptoms of a hard brick.
I assume it was the OTA because it came out yesterday. What are the odds my phone bricks by itself, for some random other reason, the very same day they pushed the OTA? I went to bed with the phone working fine. Woke up to a BLOD. My most reasonable conclusion is...OTA...

Is this even possible ?

Rob the plumber said:
Don't tell them you had custom software on it. No warranty then if they want.
Click to expand...
Click to collapse
I have insurance on it. I am sure though all I have to say is it bricked after the OTA... and thirdly I know a guy at this store at the tech/repair desk, he knows i'm rooted, is totally cool with it, and will replace it no problem.

I've never seen a pushed OTA without assent from the user.

xjacko7x said:
I've never seen a pushed OTA without assent from the user.
Click to expand...
Click to collapse
Unless I sleep-flashed (horrible new symptom of flashaholic disease?) then it had to be that, but i'm open to alternative ideas. Like I said, went to bed working fine, woke up BLOD. Unless the phone got a random reboot in the middle of the night and decided to brick itself...?
EDIT: If anyone who is way smarter with me when it comes to these phones has an alternative theory that's why I posted the thread really in the first place...

the update would've failed if you weren't on stock touchwiz.

cknuth said:
So I was under the impression that an OTA update required me to confirm yes or no if I wanted it or not. Apparently I was wrong. Sprint decided to push the ICS OTA to my phone last night, my phone which had MIUI on it. The phone is completely bricked, so my alarm didn't go off (Late for work) and now I have to go through the painstaking process of setting up a new phone from scratch. Fun, but annoying because I had JUST gotten my phone to where I was very happy with it. There will be a raging complaint in the sprint store today.
Click to expand...
Click to collapse
AOSP roms dont get OTA updates so it couldnt be sprints fault

Which is why I delete all sprint apps and bloat ware. But if you have insurance, look at the bright side, newer phone. And as for the comment above about not telling them about custom firmware, i wouldn't offer the information, but if they find out there is nothing they can do. In fact Sprint headquarters released a memo stating to treat all rooted devices like any other customer's device. Its your property. If you want to root it, blow it up or smash it with a hammer, that's your right.

JOEOZUNA4U said:
AOSP roms dont get OTA updates so it couldnt be sprints fault
Click to expand...
Click to collapse
If there was an error in the particular build or even when he flashed the phone it *MIGHT* have caused it to push through. And since its aosp and not supposed to do that, I could see where it could potentially happen. I still am not sure that's it, but it could be possible.
Sent from my SPH-D710 using xda app-developers app

timmetal6669 said:
Which is why I delete all sprint apps and bloat ware. But if you have insurance, look at the bright side, newer phone. And as for the comment above about not telling them about custom firmware, i wouldn't offer the information, but if they find out there is nothing they can do. In fact Sprint headquarters released a memo stating to treat all rooted devices like any other customer's device. Its your property. If you want to root it, blow it up or smash it with a hammer, that's your right.
Click to expand...
Click to collapse
While true that it is your property, it is their right to state conditions of insurance and hold you to those conditions.
WIth a hard bricked phone they can't tell if it was rooted though. Any other issue and just flash back to stock and uninstall super user before taking it in.

cknuth said:
I have insurance on it. I am sure though all I have to say is it bricked after the OTA... and thirdly I know a guy at this store at the tech/repair desk, he knows i'm rooted, is totally cool with it, and will replace it no problem.
Click to expand...
Click to collapse
so why make a crazy thread like this if u already know the answer?

lickarock said:
If there was an error in the particular build or even when he flashed the phone it *MIGHT* have caused it to push through. And since its aosp and not supposed to do that, I could see where it could potentially happen. I still am not sure that's it, but it could be possible.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
even IF that was the case (highly doubt) you still have to accept the update, its not a silence update like on the kindle fire...

As others have stated, OTA would have FAILED. I havent heard of ANYONE getting the OTA pushed to their phones yet anyway. Your phone bricked for some other reason. How would you know it was the OTA that bricked it anyhow if you were sleep? Lol WTF

cknuth said:
When I say "Raging" it's really not that much "raging"...I'm too passive to get worked up about stupid stuff..though when I woke up late for work I was full beast mode, good thing the sprint guys don't live at my house, also clearly not the guy at the stores fault.
All I can get is a blue light. No recovery. No Odin mode. No boot logo. My computer doesn't see it. It shows all the symptoms of a hard brick.
I assume it was the OTA because it came out yesterday. What are the odds my phone bricks by itself, for some random other reason, the very same day they pushed the OTA? I went to bed with the phone working fine. Woke up to a BLOD. My most reasonable conclusion is...OTA...
Click to expand...
Click to collapse
It started coming out yesterday but is on an 8 day roll out schedule so there's really no way to determine if it did hit your phone yesterday, also as others have stated if you weren't on stock it would've failed anyway.

timmetal6669 said:
Which is why I delete all sprint apps and bloat ware. But if you have insurance, look at the bright side, newer phone. And as for the comment above about not telling them about custom firmware, i wouldn't offer the information, but if they find out there is nothing they can do. In fact Sprint headquarters released a memo stating to treat all rooted devices like any other customer's device. Its your property. If you want to root it, blow it up or smash it with a hammer, that's your right.
Click to expand...
Click to collapse
Apple would have a fit if they heard this!
Sent from my SPH-D710 using xda app-developers app

Power surge?
Sent from behind you.

[Q]i317 Note 2 No Sim Card Connection *Plz Respond

If you would not like to read this, I admit its size is a bit unsettling, then please jump to the bottom in big bold letters and see if there is some passive way of helping.
But seriously, it's not that bad of a read. :fingers-crossed:
Hey guys, hows it goin? :laugh:
I Know this looks long but bear with me. I've made it
Enjoyable.....​
To warn you before hand.... I AM A NOOB OOOOOoooOOOoooHhhHHHhhh.......
I'm new to forums, I'm new to roots, but I'm not new to technology. Help me and I will be able to figure things out.
If you find yourself saying "Hey ya i know whats goin on hea!" help me with this, and I will Love you mercilessly.
So I'm going to give you all of the details that I can about my phone and its history.
I can imagine that maybe the solution to my problem is somewhArrr on the XDA but i just cant find a thread with my exact problems and history and I am just going to throw this up here and hope that someone can walk me through this hard time.
Alright, Ive never jumped into anything without a little bit of research first BUT like my legos, when I was a kid I just did it without reading the manual. I just kind of looked at the end result and just did it. Terrible thing to do, I know, but I'm a pretty clever guy. I usually find everything out no matter how long it takes me. But this time I fear i have taken a road that I cant really go back.
Ok ok I'll start. I got my Note II at least a year ago (pretty sure my warranty is over) and a little while ago I really realized what power my phone held and I had to have it rooted. :laugh:
So I did research and I rooted with the all powerful Auto Odin.
I have a friend who professionally works/jailbreaks/fixes all things Apple. A long time ago he rooted my Nook.
He knows his **** and he's educated. He knows Titanium backup, CWM, SuperUser, ya know, The Basics....
He saw me working on my phone one day and said "Oh i know Cyanogen mod. Its awesome!"
So at the time I had Rom toolbox (Pro) and was just window shopping different Roms. I liked a couple like Carbon, but I just decided to stick with CM. I picked a nightly mod because I'm all about the looks
So I stuck with that for a while but it wasn't enough. I missed my multi-window, s note, etc.
Then I heard about....
JEDI X.....​
Must have...... (Jedi.... I have chubs for you......)
|||||| SIDE NOTE ||||||||​Around this time I got a 64gb micro SD. And AGAIN, Research/deadlinks/descriptionsAndXDAThreadsThatNeverAppliedPerfectlytoMe/FailureTo FindDownloads&ModDescriptionsCommentsAlwaysTalkedAbout/nonfreeServices and other stuff.
The card worked but never how I wanted to and my Internal was always running out of space. Couldn't partition. Couldn't get app2sd to work.
Jedi would Flip it so Internal and SD were swapped but sometimes i would get traded my 64 into a 10 and **** was con-FUZE-ing.
If I see the light after this tunnel..... Simple and honest help would be greatly appreciated.
|||||||||||||||||||||||||||||\​
My first-firstJedi was a failure. GApps didnt work and other stuff. And no SU, CWM, Rom Toolbox. Downloading apps was hard but I got a couple. It was Hard. AAAAAHHHHHHH!!!!!! I used my SD card to quickly add .Zips, .Img, and other stuff I needed for bootloading. So I got it and when I installed it (btw I'm still not 100% on what Flashing is) I Did not wipe because I was afraid of losing my data. I never knew It would be Dirty Flashing. It was Jedi 19 I believe, or maybe 18... Well then It started to Boot loop. Info of "No root" on bootloader would cause more Bootlooping upon Install. Even after more Odin. Then waves of Battery pulls, button holds, Usb links, Odin re-roots. Eventually I wiped Enough times and re-installed Jedi and it began to work again. Some things never really worked so I did research and research. Which was always filled with links that that eventually ended in the same place they started. Or Downloads that were either lost in time or locked. Then available .exe files that never worked like 2nas and other stuff. Tried Odin again and again. Other Odin .tar file downloads again and again.
I can find everything I ever used and compile a list if it would help.
Because of all of this I experienced sleepless nights, filed with protein bars, X-files, Adderall, and a whole war brought on by my phone against me and my Lappy. Guys, I miss the taste of Sunlight. I miss my Gf. Poor thing. She emails me quite often. She really hasn't heard anything form me because.....
No
Mobile
Connection​
SIM card cannot be read. I about lost my ****. But not immediately because I hadn't noticed it. At first I was celebrating. "Yay! Beloved Jedi! I Finally have you! FN Notifications you're so sexy! (Being A HUGE Bioshock Enthusiast, Portholes is my favorite theme) Icon changer! Sweet! Jedi Tricks! Yah!" But then I noticed I couldn't get data. At first I was fine. Nothing could touch me. I could fix anything. So I gracefully took out my sim, cleaned it, and stuck it back, Nothing. Reboot. Nothing. Recovery. Nothing. Then,
FLASH-REINSTALL-JEDI/18/19/20-WIPE-REINSTALL-GOODYBAG-ODIN-.EXES-ROMS-TARS-BACKTOCM-THENTOJEDI/18/19/20-SDSWITCHERS-PARTITIONS
Nothing worked and I fear I have only been picking at old wounds and perhaps making it worse. Idk. but other than that everything is perfect.
Then last night I realized. Duh! must be the SIM card! ill just get a new one! went down to mah At&t store and a brother hooked me up. My mom is the only authorized user so I couldn't switch my number right there but I went home, Called customer support, fixed it, set up my new card, read him the digits, read em back, that was good, then he said it should work right then. Hung up. Powered down. Took out old one, put in new one. Happy/psyched. Get to talk to people again and be a human once more. Turned that sucker on and
No
Mobile
Connection​
DAMMITs followed by research..... and research..... corn nuts and tea..... and research..... found a couple of promising leads though. then I Lost them or they didn't work. Lots of people said stuff like "Lost it" "Bricked" "New Phone" Sent it in" "...Guys in texas fixed radio....' "Kernel" "stock" "unroot" "nothing worked" and worst of all "I think it's funny that no body noticed that this question was from 2 months ago" *Shivers* please don't make me wait that long. And i found a couple of "Ya I've seen people get helped and make it through this". Hope is a dangerous thing people.
So now I'm going to upload pictures and information about my phone
This is my basic "About Device"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​I can't imagine that any of this is necessary but you've got to remember I am not as Skillz as some of you guys so its just insurance.
This is where I am at now. I will be doing little to no work on my phone to keep it as close to this list as possible.
I would love comments out the WAZOO. Anything helps. I really don't want to take "Get a new phone" or anything of that nature because 1.) Money related options aren't really, well, an option. 2.) I hate giving up.
All info is good info
If you know how to fix this
I will kiss you​
If you know another way around this, such as reliable means of WiFi communications
ummmmm I'll thank you?​
If you can refer me to a specialist in my area-ish
If you can refer me to a website/forum admin
If you can give me contacts/emails/numbers
If you know how much At&t would charge me to sent my phone in
If you know if At&t will refuse/charge extra because my phone is rooted could you tell me and guide on how I may Un-Root my phone for fear of Bricking it myself without proper knowledge?
I will forever be in your debt​
Anything you need from me I would love to do anything. If you need more info/pictures. Questions. 1-on-1 emailing. I will be checking this regularly.
Think of us as children on a playground. I have fallen and scraped my knee. This is the first time this has happened to me and I don't know what to do. And I'm a bit afraid. If you're a student like me go get one of the "Teachers". If you're a teacher. Help would be awesome.\
I hope that if this thread is helpful towards me, it may be full of information towards someone else in the same position in the future. So please.
LINKS LINKS LINKS LINKS. (if necessary) Oh and ya, I know I must sound really pathetic. I just like doing things right.
Thank You,
Aveytair
5/9/2014 - 2:33 A.M.​

Bro...too long. I skimmed, didn't catch anything about you attempting to go back to stock rom/kernel. So...did you? At this point, getting things to work may corrupt your install more than you may immediately notice. Start from the beginning, if your SIM card works there, it's a software issue. If not, it's a hardware issue that we will most likely not be able to fix.

Ya I know I just have a hard time knowing when to quit. Thanks for being quick. Um originally no-
Didn't know to.
But I couldn't get my sticky fingers away from my phone and now its worse.
Now I'm not necessarily looking for help.... i guess because i tried some more things today and now its Soft-Bricked ( i think).
I only get down loader and kies firmware screen. I can hear my comp find my phone through a notification. But android toolkit cant find it, and today I finally noticed my custom binary download count...... 8. I'm really not proud of myself.
Anyways i guuuueeeessss im still looking for help even though odin/conventional stock roms never "pass" anymore.
But i guess maybe i just need help finding what step i should take next. thanks

Flash stock img from sam mobile then flash skynote 9.3
Sent from my SAMSUNG-SGH-I317 using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:40 PM ----------
Happens to mine everyrime trying to flash dn3
Sent from my SAMSUNG-SGH-I317 using Tapatalk

I had precisely the same thing happen to me the first time I flashed a rom. I didn't know about all the different versions and flashed a rom for the 7100 rather than the 317 and it stopped detecting my sim. What I had to do was flash the stock rom, then flash the new custom rom (that you did research on and it is designed for your device). I am running CM10.2 now on my i317 with full functionality.

Earpiece problems.

I'm going insane trying to find a solution for this. All my calls are really quiet, and for some reason I believe are being routed to the back speaker of the phone. If I rotate it towards the back, it's much louder. Speaker phone is twice as loud. I'm more worried about people listening into my calls or me looking stupid with a backwards phone on my ear.
I tried reflashing roms, rebooting, using soundabout to redirect audio to earpiece, and also swapping the earpiece out with a new earpiece. (The long ribbon cable with the earpiece at the top) and it's still super quiet so I'm beginning to believe it's not a hardware issue. Has anyone else encountered this? I haven't been able to find much information. I love this phone but god damn this is driving me nuts.

Are you running stock or custom?

And have you tried flashing your firmware with Odin and factory resetting? (Will wipe internal sdcard)

I'm running crom 7.1 and I haven't. I lost my backup when I had a hard drive die on me. Was hoping I didn't have to go back to stock though.

Its the best way to tell if its hardware or firmware/rom related. Otherwise you'll have to get with some long time cm users to start investigating it. I dont use cm roms so im not familiar enough to troubleshoot a problem like this.
I have seen other reports of similar issues with cm. Most who flashed stock firmware found it worked fine so it wasn't hardware. I have seen some thst were hardware related though, but it is more likely related to the rom in your case.....I think.
If you're worried about going back to stock though, why not make a new nandroid backup so you can restore back to it after testing stock?

DocHoliday77 said:
Its the best way to tell if its hardware or firmware/rom related. Otherwise you'll have to get with some long time cm users to start investigating it. I dont use cm roms so im not familiar enough to troubleshoot a problem like this.
I have seen other reports of similar issues with cm. Most who flashed stock firmware found it worked fine so it wasn't hardware. I have seen some thst were hardware related though, but it is more likely related to the rom in your case.....I think.
If you're worried about going back to stock though, why not make a new nandroid backup so you can restore back to it after testing stock?
Click to expand...
Click to collapse
I guess that works. ^.^, honestly, I just don't like touchwiz and the bloat. I guess since I'm rooted I can find a way to debloat though. I'll give it a try in a bit.
So the best thing I can do would be to flash
Wind VLFNF1
PDA: T999VVLUFNF1
CSC: T999VYVLFNF1
Version: 4.4.2 KK
Date: June 23,2014
From the http://forum.xda-developers.com/showthread.php?t=1949687 thread, use towelroot to reroot (or will I lose root going back to official firmware?), and test. If it's botched there, it might be a hardware defect, correct?
I am with Wind Mobile, I just don't know if I am able to flash back to an older version or if I should stay on KK.

After 4.3, you can only flash the same or newer builds, so if you flash NF1 firmware, that's alk you can flash from now on. You can still flash old roms though.
Other than that, youve pretty much got a handle on it. And yes, you'll need to reroot. See my Towelroot thread in General for instructions.

DocHoliday77 said:
After 4.3, you can only flash the same or newer builds, so if you flash NF1 firmware, that's alk you can flash from now on. You can still flash old roms though.
Other than that, youve pretty much got a handle on it. And yes, you'll need to reroot. See my Towelroot thread in General for instructions.
Click to expand...
Click to collapse
Yeah I remember hearing about not being able to revert to a certain version and wanted to ensure I didn't brick my device. I guess I'll flash the latest KK one then. Thanks so much Doc!

Well I flashed the OTA 4.4.2 and it still has the same problem, this sucks big time doc.

Have you factory reset? Sorry if i missed it when going back over the thread.
If you've done that after having flashed the stock firmware with Odin (not Mobile Odin), it usually means its got a good chance of being a hardware problem. But you said you already replaced the speaker right? That tells me if it really is hardware, it may be on the motherboard. Perhaps a shorted or broken connection. Or just some component going bad.
Unfortunately, the only way to know this for sure is to put your motherboard in another S3 and see if you get the same result.
Maybe try swapping SIM cards with someone else who uses Wind. Its not likely to be a SIM card problem, but its an easy thing to test, just to make sure.
I hate to say it, but other than that, im out of ideas... Maybe someone else might chime in with something I haven't thought about, or overlooked. Ill still try to think of anything else you could try and will let you know if I do. I am very sorry I dont have more for you now though...

DocHoliday77 said:
Have you factory reset? Sorry if i missed it when going back over the thread.
If you've done that after having flashed the stock firmware with Odin (not Mobile Odin), it usually means its got a good chance of being a hardware problem. But you said you already replaced the speaker right? That tells me if it really is hardware, it may be on the motherboard. Perhaps a shorted or broken connection. Or just some component going bad.
Unfortunately, the only way to know this for sure is to put your motherboard in another S3 and see if you get the same result.
Maybe try swapping SIM cards with someone else who uses Wind. Its not likely to be a SIM card problem, but its an easy thing to test, just to make sure.
I hate to say it, but other than that, im out of ideas... Maybe someone else might chime in with something I haven't thought about, or overlooked. Ill still try to think of anything else you could try and will let you know if I do. I am very sorry I dont have more for you now though...
Click to expand...
Click to collapse
I'm with Koodo now since I moved where Wind has no reach so that meant a new sim card already.. I hope it's not motherboard, that'd be indicative of this phone being toast eh? I did factory reset. When taking the motherboard out the components appeared fine. Unfortunately I don't know anyone else with an s3. Crap.

It may not be hardware still, but I am kind of leaning that way if it acts the same on any setup, including different versions of full stock.
It is possible it could be an account, SIM card, or other firmware corruption issue. (Firmware as in, not the partitions that are generally flashed when using Odin) I dont know of any way to determine if it is, or how to fix it if confirmed to be that though. Im not sure if there is anything in the NV Data that is used for audio. I will try to take a look later on.
Did it work fine previously on Koodo?
Anyone else out there have any ideas? @Perseus71 @Aerowinder @serio22 ?

DocHoliday77 said:
It may not be hardware still, but I am kind of leaning that way if it acts the same on any setup, including different versions of full stock.
It is possible it could be an account, SIM card, or other firmware corruption issue. (Firmware as in, not the partitions that are generally flashed when using Odin) I dont know of any way to determine if it is, or how to fix it if confirmed to be that though. Im not sure if there is anything in the NV Data that is used for audio. I will try to take a look later on.
Did it work fine previously on Koodo?
Anyone else out there have any ideas? @Perseus71 @Aerowinder @serio22 ?
Click to expand...
Click to collapse
I moved up north so I switched to Koodo about a month ago. It never worked on Koodo, but it also did not on Wind. This problem surfaced about half a year ago where I literally couldn't hear people. I was struggling cancelling my internet 3 months before I left. In between then and when I moved I had changed the piece (I've been building PC's for the majority of my life) I know I did the swap correctly. Sucks. It seems twice as loud reversing the phone (back of phone on my ear) or top of phone on ear, are most phones like this but at a higher volume? I wonder if the speaker relocated itself or flipped during reassembly. It does work better than when it did when I initially had problems but it's still not where it used to be, it's highly diminished.
Thanks for the help so far Doc.

Hmm.. have you checked if something is blocking the earpiece section? Or maybe try cleaning it. It would make sense why you can hear it better through the back but I don't know, that's the only thing I can think of right now that I haven't seen covered.. definitely doesn't sound like a software issue

@ chevymeister
Please try 2 things for me.
1. Use a good Bluetooth device for calls. See how the quality of sounds is over that one compared to the phone itself.
2. There are several known complaints with C-Rom's Volume issues. Some CM commits have borked it and those need to be reverted. From your point of view, please try another AOSP Rom such as Liquidsmooth or my personal SlimKat. Especially since you don't like Stock.
Make sure you do factory reset before flashing these roms. First thing you should do after flashing these roms is checking in-call volume before you restore any of your apps.

Perseus71 said:
@ chevymeister
Please try 2 things for me.
1. Use a good Bluetooth device for calls. See how the quality of sounds is over that one compared to the phone itself.
2. There are several known complaints with C-Rom's Volume issues. Some CM commits have borked it and those need to be reverted. From your point of view, please try another AOSP Rom such as Liquidsmooth or my personal SlimKat. Especially since you don't like Stock.
Make sure you do factory reset before flashing these roms. First thing you should do after flashing these roms is checking in-call volume before you restore any of your apps.
Click to expand...
Click to collapse
Come to think of it, ever since I got my bluetooth deck in my car my calls started acting up on my earpiece but that was awhile ago so maybe I'm just imagining it.. In call volume is fine using bt though compared to my in call. I'll try your rom a bit later tonight. I'll let you know. Ever since returning to stock my 15hr uptime turned into 3hr uptime. God I hate stock.

Can't help myself.
People talk about stretching a dollar. I stretched the battery to prove a point to some other users.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Perseus71 said:
Can't help myself.
People talk about stretching a dollar. I stretched the battery to prove a point to some other users.
Click to expand...
Click to collapse
That's what I'm talkin about!
I installed slimkat a few minutes ago, call volume definitely didn't improve. I'm going to tear this phone apart this weekend and see what I find I guess. This is depressing. I guess trying to be optimistic at least I'm off that stock battery sucking abomination. Haha.

Quit hating on stock guys, I got 2 days on a single charge right now on stock with 1:13hr screen time
But I'll admit I haven't used it heavily but I got similar results as you guys on aosp/cm when this was my main phone

I think each OS just has a particular way it likes to be held. If it doesn't like the way you are handling it, it takes its revenge by sucking up your battery!
Can't think of any other reason why TW is great for some and only cm/aosp for others!
Just a theory! Lol!
Sorry for going OT, couldn't help it!