Related
My Atrix runs nice and smoothly for the most part. Apps are smooth as butter. My only issue is lag whenever I return to the homescreen. If I wake up the device after a while, or I return to the homescreen after using an app for a while, and I try to swipe to another homescreen, there's always a 1 second delay. It's not the biggest deal in the world, but it gets annoying seeing it all the time. The same thing happens with any launcher I try to use. Live wallpapers don't really make it lag more. I do use lots of Widgets, so maybe that's causing it. I don't know. Does anyone else have any insight on this?
I have the same issue. Using Lpro. I thought if I put into memory it won't happen but it doesn't help. A bit irritating.
Sent from my MB860 using XDA App
yes, im experiencing this too, though I do not have a solution. Is what you're experiencing like right when you unlock the phone, and you try and swipe between homescreens, it's kind of like slow motion until like 2 seconds later, then it becomes full speed and buttery smooth?
ethantarheels123 said:
yes, im experiencing this too, though I do not have a solution. Is what you're experiencing like right when you unlock the phone, and you try and swipe between homescreens, it's kind of like slow motion until like 2 seconds later, then it becomes full speed and buttery smooth?
Click to expand...
Click to collapse
Exactly. Does it happen to you when you exit an app as well?
I wonder whether this is a result of the way Tegra 2 handles processes. Maybe it slows down ADW (or other launcher) when not in use, but doesn't speed up quickly enough.
Hopefully future Gingerbread updates help fix this.
So...
I guess this is just an unfortunate side effect of Froyo not being optimized for dual-core processors? That sucks, especially considering that I haven't seen this happening with any other Android phone, dual-core or not.
I had a homescreen lag on my N1 with stock froyo, on my Nexus S with gingerbread. My MT4g hat no lag with froyo and sense. Attic has a lag occasionally. Ithink it is bad programming in android or the graphic overlay.
Sent from my MB860 using XDA Premium App
Hmm. That makes me think the upcoming Gingerbread update won't fix this.
I wonder whether there's anything I can freeze. I've already frozen the stock launcher (I use ADW) but it hasn't helped.
MdX MaxX said:
Hmm. That makes me think the upcoming Gingerbread update won't fix this.
I wonder whether there's anything I can freeze. I've already frozen the stock launcher (I use ADW) but it hasn't helped.
Click to expand...
Click to collapse
I can't speak for newer gingerbread versions. I returned my Nexus S after 3 weeks and it shipped with the original, too early released version of gingerbread that was horrible buggy. Hopefully, they fixed that in later versions. Let's see what version we get for the Atrix.
Is it just a select few people having this issue? As I browse the forums, most people say that the Atrix is perfect and has no lag.
Am I going to have to remove widgets to get rid of this homescreen stutter?
Grrr. This issue is like a grape juice stain on your white carpet. It's little, but it's there.
I'll stop bumping this, I guess not enough people are having this problem.
MdX MaxX said:
Is it just a select few people having this issue? As I browse the forums, most people say that the Atrix is perfect and has no lag.
Am I going to have to remove widgets to get rid of this homescreen stutter?
Grrr. This issue is like a grape juice stain on your white carpet. It's little, but it's there.
I'll stop bumping this, I guess not enough people are having this problem.
Click to expand...
Click to collapse
I have a notification bar lag that only a few people have. If I get an email and my phone is locked and I unlock it and try to swipe the notification bar down I need always 2 attempts to be successful...I have absolutely no idea what triggers this...
If I swipe then, in mid-swipe, I create a touch elsewhere on the screen, the first swipe becomes interrupted. This happens every time, all of the time.
See (not me): http://www.youtube.com/watch?v=8rz3uWFuDkI
I downloaded "Multitouch Visualizer 2" from the market and it confirmed the issue visually/quickly/easily/unambiguously.
I would really appreciate knowing if there is a fix.
It makes multitouch apps (especially games) impossible. I think it may contribute to the gingerbread keyboard not being as accurate as it was on my Evo while typing really fast (maybe).
Running rooted stock.2.08.651.2
In case it matters: HW revision 002. Panel Type = Panel_ID_SHR_SHARP_NT
(You can check which panel you have by going into terminal emulator and typing in "dmesg". The scroll up 40 lines or so and find "panel type.")
It is subtle enough in most UIs that I thought it was just me adjusting to the new screen, so don't feel silly if you haven't noticed it--I sure didn't!
I searched several times and I did not find this posted yet.
This is the closest I could find in search, but it is NOT my issue, mine does just fine on the "fast swipe test." As long as there is only one touch going on, it appears to work 100%! http://forum.xda-developers.com/showthread.php?t=1140997
Thanks!
Try this, and read the instructions when you run the apk.
http://db.tt/R1jVqmm
LIKES:
drinking water, smoking flower, and avoiding the giant.
Just tested with dotty, and I had that issue too.
Tested again a few minutes later and the issue was gone.
Weird.
Type *#*#3424#*#* in phone, then run a line drawing test. See if it happens there.
Sent from my PG86100 using Tapatalk
It went away for a few hours then came back. I have absolutely no idea why. I had restarted it, but that is all.
When it worked, it really worked well. All 4 points tracked beautifully.
It is now having the issue again.
-The diag line test is single touch, not multi touch, so it does not help at all.
-I have no idea what that recalibrate program did, but it did not have any impact on the issue. Thanks though!
Any other ideas as to what this even could be? Anyone else having the problem?
I seem to have this issue too :/ think replacing the touchscreen will fix it?
Sent from my PG06100 using XDA App
Restart, and it goes away (for a while, at least). That tells me that it is more likely to be a software glitch, not a hardware issue. To me, it appears as if some multi- touch reference is not being replaced properly.
Because we only multitouch occasionally, I would bet that this could happen for a lot of users a lot of the time and it would go undetected.
NICE! The Evo only had two points. looks like Evo 3D has four points you can touch it at! hellz yeah! but it is really hard to test more than 4 points on a screen. not like I have 30 fingers .lol
kneeldug said:
Restart, and it goes away (for a while, at least). That tells me that it is more likely to be a software glitch, not a hardware issue. To me, it appears as if some multi- touch reference is not being replaced properly.
Because we only multitouch occasionally, I would bet that this could happen for a lot of users a lot of the time and it would go undetected.
Click to expand...
Click to collapse
It happens to me all day every day. It is the same on sense and CM and the other AOSP roms. It makes using the keyboard a chore because I usually type really fast.
Quite frustrating. But, I have confidence that if it is a software issue (hopefully), the wonderful devs here will fix it. All in due time.
I posted a YouTube video of this problem twice in this forum, and how to re-create it. I had it replaced because of the issue and the replacement had the same exact issue. I am pretty sure its a stock kernel problem, not hardware. With some of the cooked kernels, my E3d didn't have the multitouch problem.
http://www.youtube.com/watch?v=8rz3uWFuDkI&feature=youtube_gdata_player
It looks like this problem is more widespread than I originally thought.
thanks for the video. I have the hardware version 2 of the evo3d. don't have this issue as far as I can tell. the white one. love this thing. NEVER BUY THE FIRST VERSION EVER!
Hi all. Im going to buy this phone and noticed this thread. I am really warried about this issue because i had some touch issues with my HD2.
It looked like:
http://www.youtube.com/watch?v=RTsvyRh3fqE&feature=youtube_gdata_player
I simply couldnt write fast on the keyboard because some taps was jumping over the keyboard:/
Is the same issue on evo 3d??? How we can recognize version??
tested on GSM Leedroid with stock kernel...no problems here.
Sent from my HTC EVO 3D X515m using xda premium
I have the EXACT same issues as OP. Multitouch is crazy and so is typing using the GB keyboard. No fixes so far. HW 0002.
OP ??? How to check hw version??
Thanks for all the feedback, y'all.
Hardware revision is unlikely to be the culprit. On 002 here. Check it in settings-about phone-hardware info.
Mine seems to be fine 90% of the time now. Just when I think it mysteriously fixed itself, I check and it is back (this is based on checking at random times during the day.)
I really have no idea what could cause this. Movement appears to be unrelated, as is load, time used, battery charge, or specific activity. All I know is that restarting makes it better...sometimes for a minute, sometimes for hours.
Consider making a shortcut to a multitouch tester and generating some more anecdotal data. I was pleasantly surprised that it was so infrequent.
I have the same issue, across several roms. Progressively got worse over the course of a week, to the point of getting phantom taps whenever I touched a section of the phone towards the top. Recently took it to Sprint to replace the screen, restoring it completely to stock before, even turned S-ON. They replaced it and the problem went away for a few days. Now it is doing this again. Something is definitely going on.
Why dosent anyone believe me when I say its the kernel? Flash a cooked one and it will stop.
not everyone in here has time to flash every "kernel" ever to be created by some weird guy or 12 year old. lol some of us work 80 hours a week. :-D My tummy hurts. which one of your gf's or ex's or wives wanta kiss my tummy. I'll kiss a few inches down on her to make us even. LOL! *runs away before you all kick me*
phatmanxxl said:
Why dosent anyone believe me when I say its the kernel? Flash a cooked one and it will stop.
Click to expand...
Click to collapse
I'm pretty darn happy with the stock kernel. I value simplicity and stability above everything else. This phone is plenty fast for how I use it.
Could you let us know what kernel has had modifications that are relevant to multitouch? My ideal kernal is stock (August update) with just this modification.
Also, keep in mind that it might take a while to evaluate whether it works. Mine was fine all yesterday but now is having the skittish multitouch issue.
My sister just upgraded to a razr, so i snagged her x2. My daily driver is an inc2, but I thought this might be fun to play with. Is there anything that can actually be done to this? Doesn't seem like there are a lot of roms floating around for it. Am I stuck with motoblur? Is this destined to be an angry birds platform for my kids?
I don't need hand holding about how to mod, i'm running an early CM9 kang of ICS on my inc2, I would just like to know what the options are, what's recommended, or what should be shied away from. I've not used a motorola phone before, and know they're a bit tricky on the mod side.
I've tried liberty and eclipse on my gf's bionic. Both solid roms. Could probably theme them. The Cm7 looks like it might have a few glitches but maybe they aren't dealbreakers for u.
Sent from my SGH-T989 using xda premium
CM7 is a great daily driver for the X2
http://forum.xda-developers.com/showthread.php?p=21342515
I have really not had any problems with the rom at all.
Sent from my MB870 using xda premium
Eclipse is another great option. Receives support and has its own website http://www.eclipserom.com/.
Sent from my DROID X2 using XDA App
tspderek said:
My sister just upgraded to a razr, so i snagged her x2. My daily driver is an inc2, but I thought this might be fun to play with. Is there anything that can actually be done to this? Doesn't seem like there are a lot of roms floating around for it. Am I stuck with motoblur? Is this destined to be an angry birds platform for my kids?
I don't need hand holding about how to mod, i'm running an early CM9 kang of ICS on my inc2, I would just like to know what the options are, what's recommended, or what should be shied away from. I've not used a motorola phone before, and know they're a bit tricky on the mod side.
Click to expand...
Click to collapse
Quite a few choices for our little "blessing" of a phone. As the others have mentioned, Eclipse and CM7 I'm pretty sure are the most current and popular right now. Ran them both, you can't go wrong either way.
Good place to start to see the options.
http://forum.xda-developers.com/showthread.php?t=1313103
I neglected to add that you're not stuck with blur on CM7...all blur has been removed
Sent from my MB870 using xda premium
Cm7 or eclipse. Just remember if you go to eclipse 2.0+ you will need to update to 2.3.5
Eclipserom.com for up to date info.
Cm7 is awesome no blur at all! Only problem is HDMI is not supported.
If you want to try both on the same kernal for 2.3.4 then use eclipse 1.3 very stable and solid.
i'm very familiar with CM7. I ran that up until a week ago. Just wasn't sure it was where it was at on this phone.
CM7 for the most part is fine on this phone. I'm using it now. Biggest problem with the rom is that some have wifi issues. I do at times. For some reason it loses it's connection with the router and can't get reconnected. Some just have to turn off wifi and turn it back on to get it working again. That doesn't seem to work for me. I have better luck just going into wifi settings and clicking on the wifi connection I want. Seems to connect then. Also, from time to time apps that require root access have trouble. Sometimes when I open an app, it just shows a blank window while it waits for root access. It can be fixed by rebooting but I just press the home button, then open the superuser app and remove the problem program. Then open the program again and after allowing root access, it works fine again. Those are the only real problems I have with the rom. For me, they aren't deal breakers. I can live with them.
Otherwise, like others have said, Eclipse is a good rom. However, I myself prefer Liberty. I don't know why everybody seems to bypass it as a suggestion. When it first came out, everybody was all bent out of shape about it and what a great rom it was. Now, nobody mentions it. My guess is because there hasn't been any updates to it since it first came out. However, I myself don't really see why anybody would want any updates. It ran perfect for me. Not one ounce of trouble from it no matter what I did. I still jump back to it now. Just for a change of pace.
I haven't tried MIUI. From what I've seen, too many issues that I don't want to deal with. I could be wrong about it though, as, like I said, I haven't tried it.
Just my two cents worth.
tspderek said:
My sister just upgraded to a razr, so i snagged her x2. My daily driver is an inc2, but I thought this might be fun to play with. Is there anything that can actually be done to this? Doesn't seem like there are a lot of roms floating around for it. Am I stuck with motoblur? Is this destined to be an angry birds platform for my kids?
Click to expand...
Click to collapse
Not chained to the thing with a contract? Sell it.
DaveRichardson said:
Not chained to the thing with a contract? Sell it.
Click to expand...
Click to collapse
Over an inc 2??? Hell no sell the inc 2, root and flash cm7, your phone will be beast...
SMILE It's Not Illegal Yet
Hey all,
Having a little trouble here with maps/navigation. Almost everytime i open the app and start a navigation somewhere i get the message "maps has stopped." The weird thing is that the voice will still talk to you and i can still see the navigation notification in the drop down menu.
once i click on the navigation app, however, it disappears and i must reopen it. Maps works just fine alone, but when i tell it to navigate sometimes the graphics will get glitchy and and will give me the error mentioned above. It seems like all of this started after I flashed the JellyBam 3.1 ROM with the komodo kernel...and just for the record i never got the komodo to work (almost everything force closed with it installed).
Now even after flashing various other AOKP and going back to sense ROMs, my navigation/maps app still closes on me and gets glitchy. ive already tried uninstalling and reinstalling the app.
It is an EVO 4G LTE hardware version 0003, S-OFF
Any help would be greatly appreciated
It's a known issue with Jelly Bean, not any particular ROM. Navigation apparently eats up huge gobs of memory until it eventually kills itself. I suggest an alternate navigation app. I'm using Waze and I like it.
Sent using my HTC EVO LTE and a magic wand
Travenport said:
Hey all,
Having a little trouble here with maps/navigation. Almost everytime i open the app and start a navigation somewhere i get the message "maps has stopped." The weird thing is that the voice will still talk to you and i can still see the navigation notification in the drop down menu.
once i click on the navigation app, however, it disappears and i must reopen it. Maps works just fine alone, but when i tell it to navigate sometimes the graphics will get glitchy and and will give me the error mentioned above. It seems like all of this started after I flashed the JellyBam 3.1 ROM with the komodo kernel...and just for the record i never got the komodo to work (almost everything force closed with it installed).
Now even after flashing various other AOKP and going back to sense ROMs, my navigation/maps app still closes on me and gets glitchy. ive already tried uninstalling and reinstalling the app.
It is an EVO 4G LTE hardware version 0003, S-OFF
Any help would be greatly appreciated
Click to expand...
Click to collapse
As stated, its unfortunately a known issue....seems to be nav eating up memory and crashing itself...I dealt with it for a while just like yourself and finally resolved it by going into a sprint store and they acknowledged an issue and my refurb replacement doesn't have the issue...my personal opinion is that it has to do with what batch of phone you have (mine was a release day phone)...no fix in sight...only options are try getting replacement phones til you get a more recent build phone (no way to tell besides activation date in ##786# menu) or try telenav or waze as many have done...good luck and hope that helps and let us know what you decide to do...
Sent from my EVO using xda app-developers app
Oh okay so its a JellyBean issue. That makes more sense now that i think about the timing of everything. I was running ICS roms before flashing jellyBAM. Thats a relief because i was think i may have messed something up permanently by flashing that komodo kernel.
I think ill either run an ICS rom or just use a different nav program. Dont really feel like going through the process of unrooting only to deal with whatever shenanigans sprint has waiting for me if i were to request a refurb
EDIT: btw good call on the waze...this app is awesome!
Travenport said:
Oh okay so its a JellyBean issue. That makes more sense now that i think about the timing of everything. I was running ICS roms before flashing jellyBAM. Thats a relief because i was think i may have messed something up permanently by flashing that komodo kernel.
I think ill either run an ICS rom or just use a different nav program. Dont really feel like going through the process of unrooting only to deal with whatever shenanigans sprint has waiting for me if i were to request a refurb
EDIT: btw good call on the waze...this app is awesome!
Click to expand...
Click to collapse
Yea it sux if you're trying to run a jb based Rom (ics roms were I did too for a while) but somewhere along the way the phones have a tiny manufacturing difference newer/older build wise (at least I believe so) and can't handle the jellybean update reliably...using another nav app obviously defeats running a clean uncluttered phone but it'll have to do til someone/htc/google fix whatever is causing the nav issue...IF they ever do.
Sent from my EVO using xda app-developers app
If it is a batch issue, it isn't as simple as old vs. new. I have a release day phone and haven't had any issues with Google nav and Jelly Bean.
I have a release day phone and currently had it crash 4+ times on a drive home last night, running jb as well, very weird
This happened to me, so I uninstalled maps, reinstalled from market, and the glitch has not reappeared.
Running superjelly...
Sent from my EVO using xda app-developers app
Kalvan said:
If it is a batch issue, it isn't as simple as old vs. new. I have a release day phone and haven't had any issues with Google nav and Jelly Bean.
Click to expand...
Click to collapse
Well there goes my theory somewhat...darn it...hmmm...can't pinpoint any other reason for it besides maybe bad batch of certain memory module or part inside phone.
sladehawke said:
This happened to me, so I uninstalled maps, reinstalled from market, and the glitch has not reappeared.
Running superjelly...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
That's interesting also...I think you and maybe a handful of other users have had luck doing that and having success. Looks like it'll probably be an issue that won't be fixed except by getting funtional replacement phone IF the store goes through with it for whoever does have the issue.
Sent from my EVO using xda app-developers app
Well sounds like there isnt anymore talk of getting a fix for this. Looks like I am going to have to pay the $50 for a refurbished phone... This is a hardware/software issue I think Sprint/HTC should be replacing the phone at no cost even without TEP. /endrant
evoman said:
Well sounds like there isnt anymore talk of getting a fix for this. Looks like I am going to have to pay the $50 for a refurbished phone... This is a hardware/software issue I think Sprint/HTC should be replacing the phone at no cost even without TEP. /endrant
Click to expand...
Click to collapse
Ill be surprised to hear that they charge you for it...they shouldn't...just tell em the truth, the update screwed navigtion up along with other issues, and you want to get a phone with the older software on it to have a functional phone....when you get it, just unlock and don't update your hboot and read up on how to get jb on it with older hboot (like I have my phone now) to see if nav works.. if it doesn't then you'll still have the option of going back to older ruu before jb...
Sent from my EVO using xda app-developers app
I'm surprised this is related to memory. In my experience, and I've had the app freeze/crash since Feb. update, the issue is just related to navigation when in 3D mode. If you tap the compass in top left to lock north to up (put nav in top-down mode), it does not crash. Seems to be directly related to 3D rendering.
I hate using the map in that mode, but none of the other map programs give as good a quick overview of local traffic as google nav. Waze is close, but the UI is more cluttered.
Anyway, if you still want to use google nav on JB, just tap the compass before it crashes, and it will keep that setting for future navigation.
I just think it is unbelievable that Navigation has been broken for so long and Google is doing nothing to fix it. Since the JB update, Maps has been updated at least twice, as recent as this week, and it is still broken. The issue is quite widespread. By looking at the Maps reviews on Google Play, if you filter by phone, almost every review by EVO LTE users says the same.
Nobody likes to wait. For anything, really. But especially us phone geeks when it comes to the newest software. It's like pure torture, and it leads to crack flashing and endless tweaking of our devices. Oh the hours lost trying to find the perfect combination of the latest cutting edge Android version and the function we want. There's always an annoying bug like severe battery drain, GPS failure, or poorly calibrated colors & audio. And while we again WAIT for another update to fix it, we flash away. Complaining the entire time about how we have to wait for another update.
But I've come to realize something. I already love my phone. Stock, right out of the box. It works perfectly. Everything I need, with no time wasted on trying to make it "better". Why should I care what number is after the decimal in my Android version? I don't. Because I'd rather wait until they make sure my phone experience won't diminish, that it will only improve when I update it. Maybe it's HTC that made me feel like this with the One. Maybe all the top tier phones are so good now, it doesn't matter if it's a Nexus. Or vanilla Android at all for that matter.
All I know is right now, my phone is perfect. And I'd hate to ruin that just because of a little decimal change in my software bragging rights. I'll wait. Take your time HTC, take your time T-Mobile.
Not to troll here or flame.... But really?
I stopped reading after the title...
Sent from my HTC One using xda app-developers app
ingenious247 said:
Nobody likes to wait. For anything, really. But especially us phone geeks when it comes to the newest software. It's like pure torture, and it leads to crack flashing and endless tweaking of our devices. Oh the hours lost trying to find the perfect combination of the latest cutting edge Android version and the function we want. There's always an annoying bug like severe battery drain, GPS failure, or poorly calibrated colors & audio. And while we again WAIT for another update to fix it, we flash away. Complaining the entire time about how we have to wait for another update.
But I've come to realize something. I already love my phone. Stock, right out of the box. It works perfectly. Everything I need, with no time wasted on trying to make it "better". Why should I care what number is after the decimal in my Android version? I don't. Because I'd rather wait until they make sure my phone experience won't diminish, that it will only improve when I update it. Maybe it's HTC that made me feel like this with the One. Maybe all the top tier phones are so good now, it doesn't matter if it's a Nexus. Or vanilla Android at all for that matter.
All I know is right now, my phone is perfect. And I'd hate to ruin that just because of a little decimal change in my software bragging rights. I'll wait. Take your time HTC, take your time T-Mobile.
Click to expand...
Click to collapse
The new ltd update brought me back to stock for improved reception. The only thing I really miss is the hold home as menu button. I understand your point, although I do wish they would stop being lazy and just bring it over.
woostar88 said:
Not to troll here or flame.... But really?
I stopped reading after the title...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sorry thought a fresh perspective might be nice. Instead of another thread complaining about not having 4.2.2
Thanks for contributing
Sent from my HTC One using xda premium
See I just want my sense to have my nice 2 finger pull-down menu from 4.2.2 and WiFi calling. Be nice if they would just add in a bigger app drawer and home screen.
I don't know why you wouldn't like the new updates/ including improved battery life and usability... Also, Wifi calling is only one that I miss the most... other than that, everything else is far superior in terms of speed, battery, and well... everything else.
I agree with what your saying in regards to Roms. I quit using them a while ago and have had a much better and more consistent experience with my stock phone.
As far as the carriers go.....that's all fine and good except that Google releases updates that work immediately so it's clear that you can get updates to work from day 1. That makes me questions the motives behind carriers's relentless "testing" which, as we all know, is their way of getting people to buy new phones.
Blown 89 said:
I agree with what your saying in regards to Roms. I quit using them a while ago and have had a much better and more consistent experience with my stock phone.
As far as the carriers go.....that's all fine and good except that Google releases updates that work immediately so it's clear that you can get updates to work from day 1. That makes me questions the motives behind carriers's relentless "testing" which, as we all know, is their way of getting people to buy new phones.
Click to expand...
Click to collapse
Google also doesn't have to deal with tens of thousands of paying customers threatening to end their business relationship when there's bugs/issues like the carriers do. They have to be more careful releasing updates
Sent from my HTC One using xda premium
i just want 4.2.2. i came from a nexus 4, so i'm so use to pulling down the notification bar with two fingers and accessing the little toggles right then and there. or pulling down my notification bar with one finger and being able to expand some notifications like emails so i can see more then one at a time.
ingenious247 said:
Nobody likes to wait. For anything, really. But especially us phone geeks when it comes to the newest software. It's like pure torture, and it leads to crack flashing and endless tweaking of our devices. Oh the hours lost trying to find the perfect combination of the latest cutting edge Android version and the function we want. There's always an annoying bug like severe battery drain, GPS failure, or poorly calibrated colors & audio. And while we again WAIT for another update to fix it, we flash away. Complaining the entire time about how we have to wait for another update.
But I've come to realize something. I already love my phone. Stock, right out of the box. It works perfectly. Everything I need, with no time wasted on trying to make it "better". Why should I care what number is after the decimal in my Android version? I don't. Because I'd rather wait until they make sure my phone experience won't diminish, that it will only improve when I update it. Maybe it's HTC that made me feel like this with the One. Maybe all the top tier phones are so good now, it doesn't matter if it's a Nexus. Or vanilla Android at all for that matter.
All I know is right now, my phone is perfect. And I'd hate to ruin that just because of a little decimal change in my software bragging rights. I'll wait. Take your time HTC, take your time T-Mobile.
Click to expand...
Click to collapse
Really dude?
Sent From the GREATEST DEVICE EVER using Tapatalk II
Just remove the stupid 3 dot menu and I'll stop complaining. Really though I would prefer a first party eqs than the one I'm using now. And no I don't want to mess with rooting or roms as work email doesn't work with root.
Sent from my HTC One using xda premium
s10shane said:
i just want 4.2.2. i came from a nexus 4, so i'm so use to pulling down the notification bar with two fingers and accessing the little toggles right then and there. or pulling down my notification bar with one finger and being able to expand some notifications like emails so i can see more then one at a time.
Click to expand...
Click to collapse
I had the Nexus as well. Those are small trade offs for the features of this phone. Besides it's coming lol
Sent from my HTC One using xda premium
I feel like I can wait but why did htc chose no notification toggles is weird because all the other top phones got that but it's ok they are ugly phones lol
Sent from my HTC One using xda app-developers app
ingenious247 said:
I had the Nexus as well. Those are small trade offs for the features of this phone. Besides it's coming lol
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
yeah that is true. but i can wait. im in no hurry. this phone is fantastic the way it is now. :highfive:
Have to say I agree with op. I have come hmback to complete stock 2 times. Infused a few roms and there was just something about them that wasn't working just right. Tried 4.3 and it was blah . Missed out on the stock features I'm staying stock also.
Sent from my HTC One using xda app-developers app
I returned to stock myself but I wouldn't say I actually enjoy the slow updates. I just don't enjoy custom ROM's as much as I used to. I prefer the genuine stability of what comes from the factory. Although, there are some features (a few actually) that I can't wait to receive with the 4.2 update.
Sent from my HTC One using xda premium
Funny XDA & all these One owners staying stock. Me too! This is my first truly problem free smartphone as in nothing, none, not one issue(other then the black menu bar) but I know it days are limited so I can wait. But they finally got a phone so right that even XDA members are going stock that's an accomplishment
Sent from my HTC One using xda app-developers app