Related
Okay so hope this is the right spot to post this....
My phone about two hours ago was on working fine. At about 30% bat...
I took a nap and now when i plug it in to the charger it will not turn on at all.. only thing that happens is the LED blinks that orangy color over and over...
If i remove the battery and put it back in.. still nothing at all ever comes on the screen.
After removing the battery and while plugged into the charger if i hold the power button it will vibrate once and thats it...
not sure whats happening.
I was on gingeritis 1.0 and everything was great up to this point.
any ideas??
Let is attempt to charge for a while, maybe 2 hours. Then see if you can power up into the bootloader. See if that works.
I had that happen once as well. I just let it sit on the charger for about 15-20 minutes, and it booted up with no problems after that. In my case, it looked like the battery was just completely dead and needed to build up enough juice to last until after it booted up.
FreemanB said:
I had that happen once as well. I just let it sit on the charger for about 15-20 minutes, and it booted up with no problems after that. In my case, it looked like the battery was just completely dead and needed to build up enough juice to last until after it booted up.
Click to expand...
Click to collapse
Yup, ditto.
Sent from my ThunderBolt using XDA App
Questions like this do not belong in the development section.
Please post in the Q&A section.
http://forum.xda-developers.com/forumdisplay.php?f=1103
Wrong section brother.
^_^_^
Ditto, try pulling battery out for 5-10 seconds, put the charger. It will not blink, then it will flash orange blinks let it sit for some 15. Minutes. Remember that TB takes alot of juice to reboot sometimes 5%.
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
That's a sign of a hardware failure I had a bad touch screen and once it went out it wouldn't boot past the splash, I'm sure it's similar with other hardware failures so it's a bad device not the gingerbread roms
Atleast that's my opinion
>--The Game--<
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
Sounds like you didn't wipe data.
jcase said:
Sounds like you didn't wipe data.
Click to expand...
Click to collapse
But if he flashed Gingeritis, wouldn't the script have done in for him in cwr?
Sent from my ADR6400L using XDA Premium App
I had this happen to just a few ago.
Picked up the phone and screen was off,Normal, I hit power and nothing.
Pulled battery, went bootloaded mode recovery and wiped and loaded bamf.
I have all the roms on my SD now.
Serious now, that was the second time I loaded th3ory.
The first time, I went to uninstall something and when I hit uninstall the button started flickering wild.
I kept mashing uninstall,I got it to switch to the next screen where you hit ok.
Then got a pop up over and over, phone force close sorry.
Pulled battery and went recover and loaded bamf.
So th3ory came out with v4 I thought ok why not.
Then I had the dead phone problem like you are talking about.
I don't want to bash any dev or Rom but I'm not sure about th3ory Rom guys.
I posted because this just happend to me and many post are talking about battery.
I don't think its a battery problem guys
jcase said:
Sounds like you didn't wipe data.
Click to expand...
Click to collapse
Of course I did...and not just once.
Sent from my ADR6400L using XDA App
superchilpil said:
That's a sign of a hardware failure I had a bad touch screen and once it went out it wouldn't boot past the splash, I'm sure it's similar with other hardware failures so it's a bad device not the gingerbread roms
Atleast that's my opinion
>--The Game--<
Click to expand...
Click to collapse
If it was a hardware failure it wouldn't have worked with my froyo backup.
Sent from my ADR6400L using XDA App
tanium said:
I had this happen to just a few ago.
Picked up the phone and screen was off,Normal, I hit power and nothing.
Pulled battery, went bootloaded mode recovery and wiped and loaded bamf.
I have all the roms on my SD now.
Serious now, that was the second time I loaded th3ory.
The first time, I went to uninstall something and when I hit uninstall the button started flickering wild.
I kept mashing uninstall,I got it to switch to the next screen where you hit ok.
Then got a pop up over and over, phone force close sorry.
Pulled battery and went recover and loaded bamf.
So th3ory came out with v4 I thought ok why not.
Then I had the dead phone problem like you are talking about.
I don't want to bash any dev or Rom but I'm not sure about th3ory Rom guys.
I posted because this just happend to me and many post are talking about battery.
I don't think its a battery problem guys
Click to expand...
Click to collapse
For one all GB ROM have the data load issue when trying to uninstall. Second, if it was a issue, more people would have reported it.
Titanium Backup, a App you use in every ROM, CPU setting to low, not wipe to save some time, a multitude of things could cause you a issue.
In my defense, if it were my ROM, it would be heard.
Sent from my ADR6400L using XDA App
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
Dude. Stop bashing the GB dev Rom. You run the risk of bricking with any Rom. Plenty of people are using GB and the 2.5 radio with no problems, myself included. If it docent work right on your phone then put something else on it. Not every phone is going to react the exact same way to a flash. Your always going to have those few exceptions, even with OTA's.
Sent from my Rooted Remixed BAMF URBaN Thunderbolt.
kriskmk said:
STAY AWAY FROM ALL GINGERBREAD ROMS
My phone got stuck on the white htc screen this morning all of a sudden without any perceivable reason at all. Luckily I was able to restore to a backup.. BUT... It wouldn't install any new roms on my phone anymore for some reason.. they all get stuck on the white htc screen.
My advice.. GB is f&&&ked somewhere deep down.. and which is probably why it isn't officially released yet. Keep off of it if you don't wanna brick your phones.
Click to expand...
Click to collapse
Not good advice at all.
Check your charging cable! I just had a bad cable the other day and my phone was doing the same exact thing... light bliking on and off. I found if I plugged it in and then lightly pulled it half way out the orange light stayed solid, but it took some work.
Before you start freaking out, just try another cable... hopefully its not the connectors inside your phone.
RootandBoot said:
Dude. Stop bashing the GB dev Rom. You run the risk of bricking with any Rom. Plenty of people are using GB and the 2.5 radio with no problems, myself included. If it docent work right on your phone then put something else on it. Not every phone is going to react the exact same way to a flash. Your always going to have those few exceptions, even with OTA's.
Sent from my Rooted Remixed BAMF URBaN Thunderbolt.
Click to expand...
Click to collapse
no need to get your panties in a bunch.. My advice is only worth whatever it is.. (which may be nothing too).. and I am not thrusting it on anyone to follow it.
Where the hell do you figure I am bashing devs??? The more time one spends on xda the more you come across these noob "police figures" who go around poking into unrelated stuff getting all worked up for nothing.. Like I said.. it is probably something to do with how the alpha gingerbread works at the core level which is causing all these problems.. it has nothing to do with devs.. and look around you.. plenty of people are reporting the same. I didn't see anyone complaining when devs reported the same with the earlier GB and asked people to stay away from it. Were they doing it so that they can bash other devs who had their GB roms out before they did? I don't think so. So quit shooting from your hips and move along.
If the led is blinking it means the phone is totally dead. If you let it sit the light will eventually become solid and be fine
Sent from my ThunderBolt using XDA Premium App
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
kdub2000 said:
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
Click to expand...
Click to collapse
My guess is that something is screwing up kernal wise or your flashing. If your phone was fine stock then something got dicked during the flash.
Is there anything I can do to a clean wipe and start fresh again? Or should I try to figure out why the Superwipe isnt working? Or do I have to flash all the stock back on and turn the s-on and get a new phone? I think the digitizer is causing these issues.
Hey guys, long time xda user but never really bothered making an account and posting lol, but **** just got serious so I need some specific help. So I have been flashing roms almost since the first day I got this phone, never had a problem not even flashing ICS roms. But in this case, I was running [ROM] Blue 2.2 Frankenstein-FishmanMod Final and it was working perfect, had battery for days, no lag , and everything was smooth as usual. Then out of the blue, my vibrant decides to shutdown(no I still got plenty of battery left), so I wouldnt call this an infinite reboot because it doesnt reboot it just shuts down every time I turn it back on! It usually shuts down a couple of secs after I turn it on. And now im having a hard time even getting to CWM. I tried odin(multiple times) but no cigar, problem still persist. WTF . Does anyone know what I can do?
You could try to wipe everything if the phone dosent shutsdown, did you try using Heimdall(I think thats the name) and what especific problem you have with Odin?
Hob0dan-T959
I'm wondering if anyone is having trouble with their phone rebooting constantly? I recently changed recoveries to 5.5.0.4, and now my phone reboots constantly. Never had this problem with the buggy no off-charging CWM (although I had the worst time getting my phone to boot after the battery died ), and I don't think I've changed anything else (same ROM) since then except recovery, but I don't think it's from recovery.
This is how it started: I was playing Tiny Tower last night to drain my battery, so I could have a fresh charge. When it got around 3% life, it rebooted, and now it has been rebooting whenever I turn the screen on for a few minutes. I tried fixing permissions and reinstalling NRGZ stock kernel, but it's still rebooting.
Has anyone else had this happen?
Edit: Went ahead and wiped everything and re-installed Energy ROM, and it seemed to have fixed the problem, but it just rebooted again. Starting to think it's a hardware problem now.
Also just for clarification, it's not a full reboot (no HTC splash screen); it just goes back to the boot animation.
Update: I went into the bootloader and did a factory reset and then wiped everything from CWM again and reinstalled Energy. I have slowly been restoring apps fron Titanium Backup, and I think the reboots were being caused by RootDim (possibly reacting negatively with NRGZ button backlight tweak). I'm not 100% sure about this, but it didn't start until I used RD to completely turn off the button lights. Anyways, the reboots seemed to have stopped for now...
I had a similar problem happening after I installed RootDim, but I never really inquired about it so I just left it uninstalled.
However, I saw on the forums that people solved these types of constant rebooting issues by going into CWM recovery > advanced > fix permissions.
I never tried it, but I kind of wish you didn't factory reset and reflash so you could give it a shot and let us know if it solves the problem
adslee said:
I had a similar problem happening after I installed RootDim, but I never really inquired about it so I just left it uninstalled.
However, I saw on the forums that people solved these types of constant rebooting issues by going into CWM recovery > advanced > fix permissions.
I never tried it, but I kind of wish you didn't factory reset and reflash so you could give it a shot and let us know if it solves the problem
Click to expand...
Click to collapse
I tried fix permissions, but it didn't work.
Are you sure you're flashing the kernel properly? Flash the ROM, then reboot the phone from recovery and let it boot before using the kernel flasher.
My buddy had a constant reboot issue (along with other issues) using that recovery when I tried rushing and flashing the kernel right after the ROM while still in recovery.
Sent from my HTC_Amaze_4G using Tapatalk
It was root dim that was causing the issue.
Sent from my HTC_Amaze_4G using Tapatalk
MildewMan said:
It was root dim that was causing the issue.
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
I used Morrislee's Mod init.post_boot.sh to just perm kill those lights
Sent from my HTC_Amaze_4G using Tapatalk 2
There are a few apps that have been noted to cause reboots. Unfortunately I heard Pandora was one of them. If you call T-Mobile tech they can give you short list of reboot app culprits.
Sent from my SGH-T989 using xda premium
glacierguy said:
I used Morrislee's Mod init.post_boot.sh to just perm kill those lights
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Yeah I went back and pushed this to my phone. It works great!
Having same fake reboot prob too
I just bought an Amaze from Ebay and it is running Energy rom. Once a day, it goes to that boot up screen with the spinning rings. However it's not a full reboot like you said, it just freezes the phone then I have to take out the battery and restart it. I am not a developer, so I have to ask, what is root dim? Sounds like that might be my problem. How do I fix it?
Androidica said:
I just bought an Amaze from Ebay and it is running Energy rom. Once a day, it goes to that boot up screen with the spinning rings. However it's not a full reboot like you said, it just freezes the phone then I have to take out the battery and restart it. I am not a developer, so I have to ask, what is root dim? Sounds like that might be my problem. How do I fix it?
Click to expand...
Click to collapse
Go to energy Rom thread in dev section and flash the stock kernel using the stock kernel flasher in post 4
Rootdim is an app...
Sent from my HTC Amaze running Sense 3.5
Androidica said:
I just bought an Amaze from Ebay and it is running Energy rom. Once a day, it goes to that boot up screen with the spinning rings. However it's not a full reboot like you said, it just freezes the phone then I have to take out the battery and restart it. I am not a developer, so I have to ask, what is root dim? Sounds like that might be my problem. How do I fix it?
Click to expand...
Click to collapse
Like GlacierGuy said, RootDim is an app that I was using to shut the capacitive button lights off, but it was causing my phone to reboot. It's been fine ever since I took it off.
UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist