Hi all.
I have my HTC titan, and its on this rom:
Eternity_HTC_Europe_1.08.401.02_Radio_16.23.02.09_ 2_16.24.00.23U_Signed_ETERNITY_RELEASE
1.08.402.02 wont update with Zune, it gives an error.
The only problems i have in this ROM is the update, the screen is not as resposive as lets say HTC mozart, (it doesnt stick to your finger as you move, the Mozart or HD7 does, when you move it moves)
also when scrolling or panning trhoug the hubs theres ghosts trails, is nothing i xperienced before.
The worse thing is when i flash a new ROM, things gets unsuable, with 1.09 to the latest 2.1 ROM the screen it doesnt react to your touch, i have to lock/unlock, also when screen is on and im no touching the screen freezes up after like 10 secs, so when watching/playing the screen freezes, only way is to lock/unlock.
things gets better when its plugged in, the touchscreen gets responsive, as it should be, but it still freezes after 10 secs.
I beg please can you help me please. any ideas of what it could be/?
why it works well in one ROM and not in the NEWER ones.
vander09 said:
Hi all.
I have my HTC titan, and its on this rom:
Eternity_HTC_Europe_1.08.401.02_Radio_16.23.02.09_ 2_16.24.00.23U_Signed_ETERNITY_RELEASE
1.08.402.02 wont update with Zune, it gives an error.
The only problems i have in this ROM is the update, the screen is not as resposive as lets say HTC mozart, (it doesnt stick to your finger as you move, the Mozart or HD7 does, when you move it moves)
also when scrolling or panning trhoug the hubs theres ghosts trails, is nothing i xperienced before.
The worse thing is when i flash a new ROM, things gets unsuable, with 1.09 to the latest 2.1 ROM the screen it doesnt react to your touch, i have to lock/unlock, also when screen is on and im no touching the screen freezes up after like 10 secs, so when watching/playing the screen freezes, only way is to lock/unlock.
things gets better when its plugged in, the touchscreen gets responsive, as it should be, but it still freezes after 10 secs.
I beg please can you help me please. any ideas of what it could be/?
why it works well in one ROM and not in the NEWER ones.
Click to expand...
Click to collapse
What was the stock ROM on your Titan? Is it the 1.08.401?
Before you started updating process? I would suggest hard reset first and then see if your initial ROM is stable. Instead of forcing swap of ROMs from the forums, see if you get OTA updates pushed/notified for first. If reversing back notifies you of available updates, try Zune afterwards. Also see if you've got latest Zune by trying to update Zune itself before grabbing the update.
drupad2drupad said:
What was the stock ROM on your Titan? Is it the 1.08.401?
Before you started updating process? I would suggest hard reset first and then see if your initial ROM is stable. Instead of forcing swap of ROMs from the forums, see if you get OTA updates pushed/notified for first. If reversing back notifies you of available updates, try Zune afterwards. Also see if you've got latest Zune by trying to update Zune itself before grabbing the update.
Click to expand...
Click to collapse
Thank you for that, when i bought the phone from someone i know, the ROM was 1.09 , just before the 2.1 update.
Unfortuanally i have tried everything you mentioned... its weird thing cos when it comes to screen responsiveness, with ROM 2.1 it works great ONLY when plugged in (although screen still freezes)
Please have a look in this video youtu.be/QDLIl0-_Epo
Thnks for your reply
Related
After i upgraded to this radio i have had interesting problems with my phone. ithought it was bricked and it very well could be. But sometimes it decides it wants to work but after a minute or two it cuts off. when a softreset or hard reset are perfromed i get nothing but a white screen. I can tell it goes thru the whole process bekuzz usually after putting it to sleep a few times i get my regular screen but the radio doesnt seem to be connected. any help would be appreciated. also the buttons on the face of the phone dont seem to work.Thanx
What is "Regular Screen"?
Regular screen means the screen u would normally get after your boot and splash screen. Or better said my today screen. Sometimes i cant get my today screen up. i had BL 1.04 before the upgrade if that matters any
Today screen is very good! your device isn't fully bricked. It may be a bad radio flash or it may be a hardware issue that merely coincided with your radio upgrade. Next time you get a today screen, try to flash one of the other sspl based radio only updates (find in wiki under radio only upgrades). Remember to practice safe flashing techniques!
usb on rear usb port. No usb hubs!
all winapps closed
running winXP Pro
activesync connected
screensaver/sleep mode off (flashing takes 20+ minutes)
i have flashed the 1.27 radio again without having my today screen and that did nothing. It went thru the whole process of flashing and everything but same results, just a white screen when booting up and afterwards. im downloading the 1.34 radio now.
You need to flash the sspl version which requires first being on the Today Screen (not white screen). Tri-color boot screen will show v1.09-Des if you do this.
i guess i will have to wait to see if i get another today screen and hope that it doesnt reset itself
does it matter that i can put my phone to sleep and wake it up over and over, i just keep getting the white screen. bekuzz now i cant seem to get my today screen back anymore
ok i have done what u said and flashed the 1.34 radio and still have the same problem. after the flash i had my today screen for a minute then it reset itself and now is gone and back to the white screen. also when i was on the today screen i didnt have control of the buttons only touch screen.
i think i may have a different problem. it doesnt seem to be resetting itself everytime it goes blank but that the screen is dying on me. hmmmmmm....... this is quite strange. i can also recieve calls. i cant answer them but the handset rings.
This may be silly but if I were in your place I'd just reflash everything with an official rom that replaces everything (i.e. SA 1.35) and see if that fixes the problem (though i might wait until somebody who knows more then me verifies this is a good thing to try). I'm wondering if the bad flash somehow effected something in your OS or something.
When I mess something up like this, I like to get back to a place which has been known to work - then I have a better idea of where I am (ie brick or bad flash)
Hope this helps
yea i actually went back to the original cingular ROM that came with the phone. so we shall see what happens from here. i also will have Cingular send me a new phone, i was tired of the scratches anyway. So far they havent noticed that my phones are supercid yet. Keeping my fingers crossed
Hardware problem IMHO...
Sleuth u are right. No matter what i do to the phone it yields the same result. My screen still turns off and the buttons dont work. iwonder what couldve caused this. i didnt drop it. well not recently anyway. BTW.... is there anyway to get the original 1.16 radio back on there. i tried doing it but it just hangs at 0%.
Thanks Sleuth for all your help, you are definetly one of the reasons this forum is helpful. That and that good ole WIKI.
Hello Everyone,
I bought a verizon Titan with a kitchen ROM with WM 6.1. Yesterday I decided to try to cook one myself with WM 6.5. Everything was fine except ehe "start" button stopped working after some minutes. I cooked another opne with less programs. Then I thought it would be a good idea to use the Spbbackup I had to try to get some programs back. It told me that there has been a ROM update I clicked ok and it did its thing.
I had problems with that ROM so tried one that was in one called WM6.5Beta with WM 6.5 after that it boots, then I get a WM6.5 green screen and then the screen goes white. I though it was the Radio so I updated to the 3.42.5. No change, I tried the exitbootloader program no change. I tried to get another kitchen ROM into the Titan but the pc does not detect the Tytan. Ive tried everything I even used the las Sprint Stock Rom via Sdcard and it got to the Htc screen "no Radio". I installed the 3.42.5 Radio and I got to the WM6.5 green screen again and then it turns white.
The weird thing is that if I press the Powerbuton i get the "Power will be turned off and you may lose.." you know the usual. but I can not selkect either yes or no, the screen freezes and turns black. Another wird thing is that all the screens I see when I boot are the one I installed in my last kitchen ROM. I have tried millions hard resets, softresets, removing battery... I am really lost and I need my phone back!! Did I brick my phone? I can put new Roms and Radio through sd card method but this new ROMs dont seem to take effect since I always get the same screens...
Any help will be appreciated.
oh also If I slide the keyboard there is this "chimes" sound. So I guess a ROM is actually active but the screen is white and nothing else works...
The Flex Cable is going bad. Its the wiring so the screen can slide in and out. It can take abuse and go bad over time. Easy replace.
Hello everyone, how are you?
I'm new to this Board and pretty much new to Android too. I got myself a shiny new HTC Hero about 1 Month ago and this Phone is perfectly what i'm looking for. I love it to the Bits, but have one huge Problem, which i wasn't able to solve yet:
My Phone, even now after the Update is extremely lagging and behaving weird. First i noticed after some Time using it, that my Hero started to change Screens from itself, always running to the Screen on the far right Side. Now it becomes worse every day. Its most notable when i'm going out of the Standby Mode. It takes about 5 Seconds until it reacts to any Inputs. It takes like another 5 Seconds until it works in kinda normal Speed. And since 2 Days or so, i constantly see the Error "TouchFLO" not reacting. Force it to close or wait.. This appears more constant everyday now and made the Hero really difficult to use.
I have been on Symbian a long long Time and i'm very satisfied that i finally took the Jump to Android, but this annoys the Hell out of me.
So if anyone has a Hint on how to solve this Problem, i would greatly appreciate it!
Thanks
Michael
MichaelSF said:
Hello everyone, how are you?
I'm new to this Board and pretty much new to Android too. I got myself a shiny new HTC Hero about 1 Month ago and this Phone is perfectly what i'm looking for. I love it to the Bits, but have one huge Problem, which i wasn't able to solve yet:
My Phone, even now after the Update is extremely lagging and behaving weird. First i noticed after some Time using it, that my Hero started to change Screens from itself, always running to the Screen on the far right Side. Now it becomes worse every day. Its most notable when i'm going out of the Standby Mode. It takes about 5 Seconds until it reacts to any Inputs. It takes like another 5 Seconds until it works in kinda normal Speed. And since 2 Days or so, i constantly see the Error "TouchFLO" not reacting. Force it to close or wait.. This appears more constant everyday now and made the Hero really difficult to use.
I have been on Symbian a long long Time and i'm very satisfied that i finally took the Jump to Android, but this annoys the Hell out of me.
So if anyone has a Hint on how to solve this Problem, i would greatly appreciate it!
Thanks
Michael
Click to expand...
Click to collapse
I had this problem and found it was something like dust stuck under the trackball making it move. I pushed and spun the trackball a few times and that seemed to solve it for me.
i dont think the Trackball is the Problem. It seems more like a software issue, as those TouchFLO Software Issues keep appearing and appearing and make the Phone more and more not usable
MichaelSF said:
i dont think the Trackball is the Problem. It seems more like a software issue, as those TouchFLO Software Issues keep appearing and appearing and make the Phone more and more not usable
Click to expand...
Click to collapse
MichelSF, I too faced the same problem from time to time. I am not sure of what you mean when you say that the TouchFLO software keeps on appearing from time to time. In my case the screens would move over to the right automagically and all I used to do was move the trackball a bit and it would stop. I can still see that occasionally but it is fixed when i move the trackball. I would therefore concur with nicelad_uk that the trackball gets stuck and that causes this behaviour.
BTW, you said something about the update, what did you update it to? I updated mine to the modaco 2.2 rom and its been all fine ever since. I do occasionally see a stutter on certain menus but am happy with it. If it helps you any bit, you could install the android sdk and use the 'adb logcat -v time' command to view the debug messages that the phone churns out. You would also need to install htcsync and so on and that would indicate what the phone's doing while being unresponsive.
HTH.
s1977 said:
I am not sure of what you mean when you say that the TouchFLO software keeps on appearing from time to time.
Click to expand...
Click to collapse
i get an error pop-up that TouchFLO is not reacting.I can then either wait or force it to close. If i force it to close, the whole Start Screen is rebooting, but not the Phone. So i can access the Menu and Notification Bar, but it takes a bit until the Start Screen appears again - i hope you Guys get what i mean by that! A good Friend said this could be a Memory Leak, or being caused by Widgets that doesnt work well. I have now disabled most of the Widgets i have (Music Player, Mails, Messages, Weather), now just using the Clock and a Contact Bar. Strangely, the Phone works really well now again ..
...Man, this is confusing and annoying!
s1977 said:
BTW, you said something about the update, what did you update it to? I updated mine to the modaco 2.2 rom and its been all fine ever since. I do occasionally see a stutter on certain menus but am happy with it. If it helps you any bit, you could install the android sdk and use the 'adb logcat -v time' command to view the debug messages that the phone churns out. You would also need to install htcsync and so on and that would indicate what the phone's doing while being unresponsive.
HTH.
Click to expand...
Click to collapse
phew .. to be honest, i dont know really to what exactly we updated it. My Buddy updated it to the latest Version.. i'm such a newb on android, sorry
You need to ask your buddy if he wiped before he updated the ROM.
Regards,
Dave
ah yes, he did ..
thanks a lot for the suggestions so far.. still have all the widgets gone from the home screens, still all good.. strange
Hey!
I've noticed that in a few applications (or settings) i have issues with my touch-input. This is e.g when changing the default ringtone i can't just tap "ok" but have to press the "ok" button from the side with my whole finger, otherwise it won't be regocnised. Sometimes when using the keyboard, the buttons on the right side are very hard to use. That would be the "p" "l" and "backspace". Have anyone else had this problem? The weird thing is that sometimes it works perfect, but sometimes it's just a pain in the ass to get things done?
I think sometimes the touch screen can just not work properly, just luck of the draw I guess.
Has yours always been like this or is it a recent change? I am assuming its always been like this.
if it has then its a hardware failure (most likely) and will need to go back under warranty for repair.
If its a new change, then what has happened to cause it? Could just be a new rom or something causing the calibration to be off.
It hasn't always been like this. Lately it has begun to screw with me. And i don't think it has anything to do with luck, since it's always the same programs that do this. e.g. changing ringtone, accepting the google maps license on first run etc.
One could think this is a hardware failure, that's what i thought at first, but the strange thing is, that the same "area" on the screen works prefectly in other applications. I've tried several roms, but they all act like this. Perhaps I should install the stock rom and try with that.
I have a similar issue, and even more, sometimes once I am pressing the screen, the keys are starting to "dance" like the hero is trying to think which button to choose, by itself, and I am watching it, and smiling :-(
I've had it since SenseHero 1.5 and others as well. I just reinstalled the official htc rom and calibrated again the screen... but I am afraid the issue is still there, though less frequent...
Next week at the doorsteps of Orange I guess
Possibly is lag related?
Maybe the phones memory management is not working very well on the ROM you have installed and is causing large amounts of lag that the phone is interpreting touches (or not touches).
Lennyuk said:
Possibly is lag related?
Maybe the phones memory management is not working very well on the ROM you have installed and is causing large amounts of lag that the phone is interpreting touches (or not touches).
Click to expand...
Click to collapse
Possible, But with all the speed tweaks, task killer and stuff, maybe even the overclock widget that I started to use only after this issue appeared... don't know, have no idea how to solve it.
Now it is like beginning, with official htc rom, no additional apps installed neither contacts, and still, I have this issue.
Suggestion?
Got the exact same problem.
Almost exclusively buttons on the bottom of the screen and as you already said the right part of the keyboard (especially the goddamn backspace drives me nuts sometimes!).
It hasn't always been like this, started somewhen after flashing more than just Modaco I think.. And the severity varies a lot, sometimes I got barely any issues and then again I can't even finish an sms. Unnerving.
At htcpedia someone who obviously has the same problem pm'ed me his solution:
Your Problem with Screen
I had to wipe everything of.... installed the WWE original ROM, then re-root the phone and now working with Modacco 3.1, seems to be working ok now....think the problem was with LOX latest ROM.
Click to expand...
Click to collapse
I think - not sure - it startet with some lox rom for me too. Do you remember which Rom you were using when this first occured?
Well anyway, might give it a try.
I haven't tried it yet for 3 reasons:
1 - the link for the german version of the original firmware is down
2 - i don't have a windows computer, so the .exe is pretty much useless for me
3 - I'm way too lazy as currently it's not that bad
same problem
hye there, I seldomly post here..
But i got the same problem before... keyboard dances, hard to click OK... could not finish a sms without swearing F*** F***..
yep, its a hardware problem.. maybe its bcoz of the shape of the hero making its touch screen easily damage.. Not sure though..
flashed so many roms, to try to fix this problem.. thought it was a software issue.. but.... nothing..
went to HTC care centre.. and changed the touch screen (warranty, had to revert everything to stock) and now...
Good as New with Villain 3.4
hope this helps...
Oh thx guys. "Happy" not to be the only one with this issue. For starters I'll try the solution with the original rom. I think I still have some version of windows installed on one of my harddrives. If it don't work I'll have the screen changed. I'll report soon.
rehet said:
hye there, I seldomly post here..
But i got the same problem before... keyboard dances, hard to click OK... could not finish a sms without swearing F*** F***..
yep, its a hardware problem.. maybe its bcoz of the shape of the hero making its touch screen easily damage.. Not sure though..
flashed so many roms, to try to fix this problem.. thought it was a software issue.. but.... nothing..
went to HTC care centre.. and changed the touch screen (warranty, had to revert everything to stock) and now...
Good as New with Villain 3.4
hope this helps...
Click to expand...
Click to collapse
When you revert to stock Rom, do you need to reinstall a stock recovery as well? or is it automatic? because I reverted and when I try to boot into recovery with "power + home" I get a kind of error: the symbol of a triangle with an exclamation mark in it, and a phone symbol lies down beneath it.
Is there another way to go into recovery? or is it not installed actually? (I went back to the official RUU from htc site).
Thanks for the help.
Ok, I've just tried the solution with the stock rom. As a matter of fact, it does fix the keyboard-issues. However, some of the other random touch-input-issues still persist. I can't really see how this could be hardwarebased, since the same area on the screen works in other applications just fine.
The official rom from HTC completly restores your phone as it was when you got it. You'll have to install your custom recovery again, as you did the first time.
I had a similar issue.
A fix for this: VillainROM6.1-Full-signed.
Now, keyboard its ok.
Try it.
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