Related
Ok a rewrite
Monster rom 1.1i is what I've been on all day and there is an update to 1.1j that just came out so my thought are of the 1.1I
Theme of the rom is very little at this time its still very new. The notification bar is a metallic black with white symbols and a battery meter that shows 1%. Very nice. The dialer is also themed with a metallic look.
The rom is I would say looks like an OASP rom even though its not. I like the look and feel of the launcher.
I think that its faster then stock. Feels snappier do to the adrenaline shot that he gave it. I don't know what that does but I like it. No lag or slow downs of any kind.
There is a bloated and a debloaded rom as well.
Also the free ram has been really good. Every time I look I have at least 200 to 230mb of free ram all the time. Can't beat that. The battery has also been good for me as well, as of 12 hour of moderate use I still have 50% left. That's good for me.
I've had no issues with it as of now so im really liking it and im looking forward to more updates. He updates it every couple of days wich I ike. They are not big updates but good ones.
Rom is by 05gsxrk5 and BenLand150
Im sorry if i left someone out.
Sent from my DROID3 using DroidForums
I like the idea of rom reviews.. but no disrespect I think you should put more detail maybe pros and cons in each to you, other specifics and structure your paragraphs better.
Sent from my DROID3 using XDA App
I read it back and you are right. When I do the next one I will add more I was pressed for time I had somewhere to go so it was a fast reveiw. I am far from a good writer and was never great in english class either I think a teacher said the same thing to me once its why I got a c in that class. I think the next one I will make a paragraph for each specific thing. I think that way we can get a better idea of the pros and cons. Thanks for the insight
Sent from my DROID3 using XDA App
Monster ROM is by 05gsxrk5. I'm just supporting it on Droidforums so people know about. The first post gives credit to him, too. Just pointing that out.
Yes thank you for doing that. I did not think about the other people involved with the rom.
Sent from my DROID3 using XDA App
I rerwrote it. A little better now
Sent from my DROID3 using XDA App
Monster Rom is not AOSP, it just doesn't use Blur launcher.
I know that its not it just looks that way I will update my post
Sent from my DROID3 using XDA App
Is this thread meant for anyone to chime in? I like that idea too. If you ever want to read reviews without searching through what will end up probably being 100+ pages of questions/comments in the actual respective ROMs threads u could just come here search for the name and read up.
Please chime in. I think its great to here from people who are using these rims. I like one place where we can go to read what people are saying about the rims. As of now im on 1.1k just came out last night. So far I like the changes. Later im going to steel DROID and try out 3.0 that just came out.
Sent from my DROID3 using XDA App
Ok time for steel DROID 3.0
Ive been running this for a full day now and
It very snappy. Opening apps is ferry fast it just kinda snaps open very quick. I have not ran into any slow downs or lag. Been very happy with the speed. It also has the adrenaline shot along with some ram tweaks. This rom is the only one out that I've seen with tweaks that I think are done to make a faster rom.
It is also themed a little bit. It has a 1% battery meter on top a black notification bar. The wifi and bars are changed to a blue and look like ice theme. I do like the look
It is running on the blur launcher as of now.
I've ran into no problems that I needs to be fixed with away. There were a few issues but since have been fixed. He also has some addons that you can put back onto the phone if you need certain Apps that he took off. It is debloated rom, I also think there is a bloated rom as well.
The free ram is not as high as the monster rom but still better then stock. Im usually at 120 to 180mb of free ram.
With every update it gets better and better.
Sent from my DROID3 using DroidForums
Sent from my DROID3 using XDA App
Actually, dpwhitty is doing the poll on his themed rom
Sent from my DROID3 using Tapatalk
Ya I got my rom switched up. Thank you for that im updating my post.
Sent from my DROID3 using XDA App
bump let's hear more reviews
I just put Liberty on my phone last night and I like it even better than Monster. It's heavily debloated imo which made me nervous, but Titanium made it easy to restore apps I needed and now i probably have a more refined list of back ups geared towards how I use the phone, so not a bad thing all in all. It moves quicker on my phone than Monster, the way i measure it is hit home on the homescreen of LauncherPro and it no longer glitches when the screens zoom out into formation.
The only bug i've noticed is I can't dial *228. I was able to still call voicemail so I'm wondering if this says anything to the effect of it needing to be provisioned like what I used to have to do in WinMo, but unless I see a problem surface I doubt i'll investigate into that too much. Not really a big deal for me. A lot of people said they had bugs like front facing camera force closing but I haven't had those problems. I used the blur camera as well as the blur calendar/email in the customization options and it all works well.
Liberty is as good as always and will only get better. After Hashcode is done with this new version of safestrap: http://goo.gl/FDYlE I will be dual booting this and CM7 indefinitely.
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39892
it's pretty sad that there's only 45 votes on this issue. Here's a hint: bugs won't get fixed if people don't speak up about them. And don't think your voice exactly resonates here on XDA.
Just star it, and leave a comment. Doesn't have to be anything long winded either.
Sent from my Nexus 10 using xda premium
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Troute said:
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Click to expand...
Click to collapse
While agree it's not the end of the world, it's a complaint I see often here in kernel and ROM threads. While a lot of it is due to wonky behavior due to OC (either CPU or GPU), it's really just exacerbating an issue that is already present.
Besides, UI bugs are some of the most prevalent and immediately noticeable to more "common" end users. While functionally it's not debilitating, it's an aesthetic scar that doesn't need to be there.
Sent from my Nexus 10 using xda premium
Hmmm.. So I assume it doesn't matter that I need exactly 15 seconds everytime I get a notification to pull down the status bar, caused by flipbacks. Okay I'm like 1000% sure Google noticed it anyway, cause its on most devices, also 100% stock ones (like me) so...
Sent from my Galaxy Nexus using xda premium
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
jbdan said:
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it would bounce back after a reboot one time, I wouldn't care, but its always there, it doesn't matter what I do, it bounces every time... So its a bit annoying.. This is the only thing which sometimes makes me want to throw the 7 at a wall...
Sent from my Galaxy Nexus using xda premium
Thanks OP, have added my star.
I had not noticed this problem but I was intrigued.
I could not duplicate the problem, but I am using Apex launcher, not the stock launcher. Does the problem occur in all launchers? Also I am not using the stock ROM.
I wonder if this problem happens with only some units, or perhaps it relates to those user's expectations. Maybe they expect their device to react more quickly than it is able to.
Far be it for me to be dismissive of people's satisfaction with their devices, but that bug-report thread has a lot of problems. It contains over-reaching claims and supposed knowledge of the problem's causes and solutions.
Again, I don't write off these people's unhappiness but I personally would not star that issue.
i too have this problem when on stock rom..now on PA beta 9 with m-kernel, the problem still exist...and it's very annoying...i even thought there was a problem with my touch screen panel and sent it to asus for repair but when i got it back, the same problem still remains..
Not starring because it does not bother me.
Life has too many other issues to worry about having to occasionally re-swipe.
Now pop-up ads in the Yahoo app could get me started...
squshy 7 said:
Come on guys, with all the members here and all the people who like to complain, it's pretty sad that there's only 45 votes on this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
I noticed this issue minutes after pulling this thing out of the box, this might not bother you people who casually use their tablets, but top those of us who have been using android since the G1 notice this. It bothers me so much that I am considering taking this junk back and using the money to get a real tablet from Samsung.
This issue is so annoying to me, I not only notice it on the stock launcher, but also Nova and Apex. Now, the launcher I can deal with, but where I becomes a deal breaker for me is the browser, whether it's chrome or the stock browser in CM10. Trying to scroll around the OS that requires some flicking reminds me of trying to flick scroll on a resistive touch screen, I think that best describes the issue.
I just wanna know if it's fixable through a software update or a hardware problem, cause if it's the latter, this thing is going back, and that's too bad because it was a Santa gift, so I'll have some explaining to do.......
compact_bijou said:
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
Click to expand...
Click to collapse
As I stated (not in precise terms sorry) in the OP, it would be a mistake to think that xda threads are the first place companies like Google and Asus check to see what issues people are having. They have issue and bug trackers for a reason. The universe does not revolve around our little community.
Also, this issue pertains to the general consensus that touch screen issues (like bounce back) have become exacerbated on 4.2 and above. Not anything regarding physical QC issues (though, to be fair, may very well be the root cause, but that is an entirely different issue; the fact of the matter remains that anecdotally it appears the touchscreen responded better on 4.1.2)
And besides, I'm just looking out for the well being of this device's future. Reporting bugs on bug trackers is important to these developers.
Sent from my Nexus 10 using xda premium
to be honest, this annoys me a lot.
starred and commented.
This really annoys me as well. I voted and commented. Hopefully they can get this fixed soon. Otherwise I might switch to CM10.
Sent from my Nexus 7 using xda app-developers app
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
leonclement said:
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
Click to expand...
Click to collapse
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
farmerbb said:
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
Click to expand...
Click to collapse
Yea the notification bar is better on 4.2.2, but the launcher still does it, nova prime does it too, and even when on dolphin or boat browser sometimes when you flick it will scroll nicely & sometimes a flick wont move the page much at all, weird and annoying, would be a much better experience if it was fixed!
This is a huge issue for me. Is there a way to increase or decrease sensitivity? Maybe that would help.
Sent from my Nexus 7 using xda app-developers app
Interesting, I thought I was the only one who had noticed this. Don't know why I haven't seen this thread earlier.
For me I solved this by using apex launcher, somehow you never get those annoying jumpbacks. I tried nova launcher as well but it worked as bad as the original launcher. Going to star tomorrow.
Sent from my GT-I9300
I want to take another stab at unlocking the bootloader, I see the forums seem to be next to dead and i believe if we can successfuly unlock this thing it will breath a bit of new life into our device. anyone who is willing to help and has some information to share please post it here. ive got a few ideas on people to talk to.
until then
lets brain storm
Not trying to be a negative Nancy but why? We got Kexec but just a lack of good developers.
Sent from my DROID3 using xda app-developers app
MrObvious said:
Not trying to be a negative Nancy but why? We got Kexec but just a lack of good developers.
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Because we have a pretty good device, and development was great for a while but the bootloader has kept this device from being truly great for a long time. i think if we can crack it it would bring back some development. and not only that but if we can find a way to crack this maybe we can put our information forward to other motorola devices with the same issue. id love to have the kernel options, and variety of roms available ive had on past devices. the og evo was awesome for that one reason. and i honestly believe its possible....
idontwanttobeanoob said:
Because we have a pretty good device, and development was great for a while but the bootloader has kept this device from being truly great for a long time. i think if we can crack it it would bring back some development. and not only that but if we can find a way to crack this maybe we can put our information forward to other motorola devices with the same issue. id love to have the kernel options, and variety of roms available ive had on past devices. the og evo was awesome for that one reason. and i honestly believe its possible....
Click to expand...
Click to collapse
An unlocked bootloader would make no difference. With kexec we can bypass and use a custom kernel anyways. However the custom kernel is still in development as motorola never released an ics/JB kernel
Sent from my DROID3 using xda premium
idontwanttobeanoob said:
I want to take another stab at unlocking the bootloader, I see the forums seem to be next to dead and i believe if we can successfuly unlock this thing it will breath a bit of new life into our device. anyone who is willing to help and has some information to share please post it here. ive got a few ideas on people to talk to.
until then
lets brain storm
Click to expand...
Click to collapse
Lmao
I think it would be great to crack the bootloader. However, has any phone with a locke bootloader been cracked without a leak from the manufacturer?
Moto must be using pretty large bit keys to lock the bootloader. You'll have to be lucky to crack it, not good.
I don't really see the actually bootloader lock changing in anyway. As said above kexec is a good system, just have to be patient.
The-Captain said:
I don't really see the actually bootloader lock changing in anyway. As said above kexec is a good system, just have to be patient.
Click to expand...
Click to collapse
Patient for what? Hashcode himself said "What do you want me to improve on JB for D3?!". I don't really see D3 getting camera on 4.x anymore
DoubleYouPee said:
Patient for what? Hashcode himself said "What do you want me to improve on JB for D3?!". I don't really see D3 getting camera on 4.x anymore
Click to expand...
Click to collapse
He didn't specify camera in OP. I don't care about camera TBH. I have an actual camera I carry around. I though he wanted 4.2
Sent from my XT862 using Tapatalk 2
The-Captain said:
He didn't specify camera in OP. I don't care about camera TBH. I have an actual camera I carry around. I though he wanted 4.2
Sent from my XT862 using Tapatalk 2
Click to expand...
Click to collapse
well glad to see my dumb post has gotten a bit of attention.... lol
id not touched my d3 since long before kexec, found it in a drawer and got a bit carried away.
went back and looked into kexec after everyone mentioned it and i agree its a pretty good system so im gonna start doing my research and see if there is anything i might be able to do.
sorry guys
idontwanttobeanoob said:
well glad to see my dumb post has gotten a bit of attention.... lol
id not touched my d3 since long before kexec, found it in a drawer and got a bit carried away.
went back and looked into kexec after everyone mentioned it and i agree its a pretty good system so im gonna start doing my research and see if there is anything i might be able to do.
sorry guys
Click to expand...
Click to collapse
Focus on the camera.
Sent from my DROID3 using xda app-developers app
The-Captain said:
He didn't specify camera in OP. I don't care about camera TBH. I have an actual camera I carry around. I though he wanted 4.2
Sent from my XT862 using Tapatalk 2
Click to expand...
Click to collapse
Amen. Motorola DROID 3's camera is a total bs anyways.
Hey guys, can anyone tell me in a nutshell what's wrong with our D3's cam? For example It doesn't work under CM7. Is it that special?
Sent from my LG-P990 using xda app-developers app
paleee said:
Hey guys, can anyone tell me in a nutshell what's wrong with our D3's cam? For example It doesn't work under CM7. Is it that special?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
For CM7 you need a 3rd party app like camera 360
I know that we have Kexec on D3, but I'm going to try an experiment on the Bootloader this weekend to see if I can unlock it. Reason being other devices do not have kexec and something crazy happened last night at work. In short, I cracked an AES encryption on a Motorola Radio(the ones Ambulances use). I know that may not sound like much, but I think I might have a way to do the same method on the Bootloaders for our Motorola Phones. I don't wanna go into too many details on it, but I'll try to get you guys a response next week sometime.
Please lol no trolling, I just like trying things. Chances are the method may not work.
Peperm1nt said:
I know that we have Kexec on D3, but I'm going to try an experiment on the Bootloader this weekend to see if I can unlock it. Reason being other devices do not have kexec and something crazy happened last night at work. In short, I cracked an AES encryption on a Motorola Radio(the ones Ambulances use). I know that may not sound like much, but I think I might have a way to do the same method on the Bootloaders for our Motorola Phones. I don't wanna go into too many details on it, but I'll try to get you guys a response next week sometime.
Please lol no trolling, I just like trying things. Chances are the method may not work.
Click to expand...
Click to collapse
Good luck
Peperm1nt said:
I know that we have Kexec on D3, but I'm going to try an experiment on the Bootloader this weekend to see if I can unlock it. Reason being other devices do not have kexec and something crazy happened last night at work. In short, I cracked an AES encryption on a Motorola Radio(the ones Ambulances use). I know that may not sound like much, but I think I might have a way to do the same method on the Bootloaders for our Motorola Phones. I don't wanna go into too many details on it, but I'll try to get you guys a response next week sometime.
Please lol no trolling, I just like trying things. Chances are the method may not work.
Click to expand...
Click to collapse
Hopefully waiting
Sent from my MILESTONE3 using xda app-developers app
I am sure many of us are experiencing the annoying auto brightness bug on our Nexus 7 that got introduced with version 4.2. Please go to the link below and vote for this issue (star it), as it doesn't seem to be on Google's radar right now more votes will definitely put it there. Thank you!
[Edit] looks like I don't have enough posts to add links yet. Can someone please post a link to issue 39841 on code.Google.com for me?
Auto-brightness has never worked right on any Android-device I have ever owned, it's the first thing I always turn to manual, and I doubt that'll change anytime soon.
If it were up to me, I would remove it from Android altogether.
jadephyre said:
Auto-brightness has never worked right on any Android-device I have ever owned, it's the first thing I always turn to manual, and I doubt that'll change anytime soon.
If it were up to me, I would remove it from Android altogether.
Click to expand...
Click to collapse
Agreed. On my aging HTC Wildfire, still running FroYo, I have Auto-brightness disabled.
On my Nexus 7, I have both Auto-brightness and PRISM/SmartDimmer disabled.
...and I doubt the supposed battery saving benefits of either are much to get excited about...
Rgrds,
Ged.
jadephyre said:
Auto-brightness has never worked right on any Android-device I have ever owned, it's the first thing I always turn to manual, and I doubt that'll change anytime soon.
If it were up to me, I would remove it from Android altogether.
Click to expand...
Click to collapse
Well, that's pretty sad. It works so seamless on iOS devices, you don't even notice it working.
AW: Auto brightness bug - Please vote
konradsa said:
Well, that's pretty sad. It works so seamless on iOS devices, you don't even notice it working.
Click to expand...
Click to collapse
Well, i don't know about iDevices, i only ever used the first iphone for a few months before I bailed and went to Android.
Also, don't know why it doesn't work right on Android, probably because every manufacturer uses different light-sensors.
sent from my N7
jadephyre said:
Well, i don't know about iDevices, i only ever used the first iphone for a few months before I bailed and went to Android.
Also, don't know why it doesn't work right on Android, probably because every manufacturer uses different light-sensors.
sent from my N7
Click to expand...
Click to collapse
Well, anecdotally it worked much better on the N7 up to 4.2 came around, even if it wasn't perfect. So at the very least they can go back to that behavior. Please vote!
+1 vote for this thread to be closed..
Sent from my Nexus 7 using xda app-developers app
Lim Wee Huat said:
+1 vote for this thread to be closed..
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
And the reason is?
At this point all I really care about is something that will keep my data connection from frequent and random drops. If not it's time to look at other options.
Sent from my HTCONE using xda app-developers app
tommason1968 said:
At this point all I really care about is something that will keep my data connection from frequent and random drops. If not it's time to look at other options.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
NEVER happens to me so I doubt 4.2.2 will remedy for ya. Maybe look into other avenues to resolve this issue
I don't know what else it could be. Others with different devices hold their connection from the same location while mine drops. Whatever the case, it's getting old. I'm done talking to Sprint about it as the answer of "we are working on the towers right now“ doesn't work for me. If they were truly working on them the guys I work with would have the same problem.
Sent from my HTCONE using xda app-developers app
The main reason I want 4.2 is so I can play with non-daily driver ROMs without dealing with the SD card when I go back. Anyone else?
Sent from my HTCONE using Tapatalk 4 Beta
Embluss said:
The main reason I want 4.2 is so I can play with non-daily driver ROMs without dealing with the SD card when I go back. Anyone else?
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
That's probably the only practical reason.
tommason1968,
I know exactly what you are talking about! I had a thread complaining about the same thing. Took my phone into the Sprint store and it failed "once" a test and they gave me a new phone and the exact same thing happens to my current phone. Can't go down the street (or even sometimes sitting still) and I lose data connection. Listen to streaming radio on Tune-In and it cuts out constantly. Used the Scout (Telenav) GPS and always got "There is no cell phone coverage / Now there is cell phone coverage" during a trip to Wisconsin and Mississippi this month.
Heard the excuse that the towers are being upgraded and that is the reason service is so poor. Almost tempted to say well put that in writing so that I can go to another wireless company without an ETF.
Came from the HTC LTE and never had so many drop outs. Yes, there were marginal spots that I would lose service, but in the past I have made it to Wisconsin and back without dropping service once not to mention 50 - 100 times, so like you think it is directly related to the phone. When you take the phone into the Sprint store, they are like well nothing what we can do, or well that is a lot of work and doubt we will find something. It is tempted to reactive my old HTC LTE and see how it does because I know where the marginal areas are at and the areas that are not marginal that I still lose connectivity on a constant basis with my HTC One.
Just wonder if like the first I-phone made of solid shell, that the metal casing isn't affecting how well the phone does in the terms of the ability to connect and stay connected to the cell towers.
For me, it's gotta be the way ZOE clips will be captured as a single video file instead of 20+ images. Each time I take a ZOE clip all those 20 pics get backed up on my G+ cloud.
elrey75 said:
For me, it's gotta be the way ZOE clips will be captured as a single video file instead of 20+ images. Each time I take a ZOE clip all those 20 pics get backed up on my G+ cloud.
Click to expand...
Click to collapse
And the charging speed. And the quick toggles. And hopefully the focus on the camera. And the OS efficiency.
I've managed to get rid of all the lag by turning off all animations. I just need better battery life. Everything else has been promised.
I just want the added features of 4.2.2. I want quick toggles, lock screen widgets, etc. And the added battery percentage and what not.
eXplicit815 said:
I just want the added features of 4.2.2. I want quick toggles, lock screen widgets, etc. And the added battery percentage and what not.
Click to expand...
Click to collapse
What if I told you...
EQS and percentage are already available on Viper and HTC will not incorporate lock screen widgets.
4.3
Who cares about 4.2? 4.3 began rolling out to the Google Experience/Play HTC Ones a few days back which has a functional IR blaster! That, with CM's new camera and this phone is going to be pretty awesome, pretty quickly.
sauprankul said:
What if I told you...
EQS and percentage are already available on Viper and HTC will not incorporate lock screen widgets.
Click to expand...
Click to collapse
I'm with explicit. I like the aosp toggles much much more along with HTC's version of the battery percent. Also, the update will come with lockscreen widgets. They already have the implemented in the Intl version.
I for one am pretty stoked about this update. It will include everything that I like in aosp plus it will have IR.
Sent from my One using Tapatalk 4
Gumby63 said:
I'm with explicit. I like the aosp toggles much much more along with HTC's version of the battery percent. Also, the update will come with lockscreen widgets. They already have the implemented in the Intl version.
I for one am pretty stoked about this update. It will include everything that I like in aosp plus it will have IR.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I just want native AVRCP 1.3!!!!!
sauprankul said:
What if I told you...
EQS and percentage are already available on Viper and HTC will not incorporate lock screen widgets.
Click to expand...
Click to collapse
What if I told you...
That the EQS included with Viper looks hideous to some of us?
Just ribbing you, but seriously-- I cannot stand how it looks in the slightest. Native quick toggles are also one less app needed to replicate functionality, which is nice if you're trying to keep things slim.
Rirere said:
What if I told you...
That the EQS included with Viper looks hideous to some of us?
Just ribbing you, but seriously-- I cannot stand how it looks in the slightest. Native quick toggles are also one less app needed to replicate functionality, which is nice if you're trying to keep things slim.
Click to expand...
Click to collapse
Yeah. I think that the EQS are stupid looking too. Just wanted to make sure it was known that most of these features already exist in some form. I love the Holo style EQS, though. In the meantime, I'm using Floating toucher. Its pretty cool.
I'm more excited about the camera improvements. The number of pictures out of focus is too damn high!
I expect that it will be the only update released for this phone.
sonicice said:
I expect that it will be the only update released for this phone.
Click to expand...
Click to collapse
No way. This is a flagship device that's barely 4 months old. Support has to be for at least a year.
sauprankul said:
No way. This is a flagship device that's barely 4 months old. Support has to be for at least a year.
Click to expand...
Click to collapse
Good one
I'd be willing to guess the 4.2.2 delay is a Sprint issue more than an HTC one.
I personally am not even excited about the 4.2.2 update anymore, due to how long it's taken and now that 4.3 is out.
FlowingAway said:
I'd be willing to guess the 4.2.2 delay is a Sprint issue more than an HTC one.
I personally am not even excited about the 4.2.2 update anymore, due to how long it's taken and now that 4.3 is out.
Click to expand...
Click to collapse
I'm not excited about either one. I have a Nexus 7 with 4.3 on it and it doesn't look/feel much different from when I used CM on my LTE. There just isn't anything to really worry about other than the kernel.