Related
I'm still using an htc inspire, and I've tried att latest and greatest like the note and one x and they haven't been perfect or lack of Rom support that made me run. I just want to be able to flash cm 7 or 9 roms, any other roms I may wish and this att device dev support seems to be going strong. This device is probably considered older now and with the sgs3 coming soon, well by the time it reaches att who knows. Does this device lag with its older processor??
SysAdmNj said:
I'm still using an htc inspire, and I've tried att latest and greatest like the note and one x and they haven't been perfect or lack of Rom support that made me run. I just want to be able to flash cm 7 or 9 roms, any other roms I may wish and this att device dev support seems to be going strong. This device is probably considered older now and with the sgs3 coming soon, well by the time it reaches att who knows. Does this device lag with its older processor??
Click to expand...
Click to collapse
One word. Yes.
The device is amazing, I highly reccomend.
What answer do you really expect us to give you other than "yes"? Do you really think people in this forum is going to tell you no? Sounds to me like you already made up your mind to get this phone if you didnt like the Note or the OneX.
How about bln support, is that compatible with most roms? Say cm custom builds whether built in or not?
Red5 said:
What answer do you really expect us to give you other than "yes"? Do you really think people in this forum is going to tell you no? Sounds to me like you already made up your mind to get this phone if you didnt like the Note or the OneX.
Click to expand...
Click to collapse
Well people here could also say,just wait for the sgs3....etc etc...just curious to see if it's still highly recommended at this point.
SysAdmNj said:
I'm still using an htc inspire, and I've tried att latest and greatest like the note and one x and they haven't been perfect or lack of Rom support that made me run. I just want to be able to flash cm 7 or 9 roms, any other roms I may wish and this att device dev support seems to be going strong. This device is probably considered older now and with the sgs3 coming soon, well by the time it reaches att who knows. Does this device lag with its older processor??
Click to expand...
Click to collapse
I would absolutely recommend this device. It may be considered last year's technology, but the dual core Exynos is still a great processor. The phone doesn't lag on stock firmware, and on the better custom firmwares, it flies. Rom support is unparalleled for a US based phone, partially because of the commonality between the i777 and the international i9100.
It is true that the S3 is on the horizon, but I would honestly rather have my S2 than that monstrosity.
SysAdmNj said:
How about bln support, is that compatible with most roms? Say cm custom builds whether built in or not?
Click to expand...
Click to collapse
Sort of. I'm running AOKP right now, which is a purely Google-based rom, and BLN works flawlessly for me(with the right kernel, of course). However, if you run a Samsung based rom, BLN will not natively work for SMS messages. There are workarounds using Tasker profiles, but theyre usually pretty sketchy. Short answer...yes, if you're running the right rom and kernel, BLN is supported.
SysAdmNj said:
How about bln support, is that compatible with most roms? Say cm custom builds whether built in or not?
Click to expand...
Click to collapse
Depends on the rom and kernel... But really, is BLN going to make or break your decision?
jthatch12 said:
Depends on the rom and kernel... But really, is BLN going to make or break your decision?
Click to expand...
Click to collapse
Not a deal breaker but a handy feature when you lack an led notification light, I'm using the BlackICE Rom which uses it.
@mattdm that is a good point,dev support seems huge compared to other att android devices.
jthatch12 said:
Depends on the rom and kernel... But really, is BLN going to make or break your decision?
Click to expand...
Click to collapse
BLN can be pretty important to some people. I came from a BlackBerry, so it's almost essential to me to be able to see if I have a text from across the room.
Yes, I still like this phone. Hell the original Galaxy S is still going strong development wise and this one should do the same.
mattdm said:
BLN can be pretty important to some people. I came from a BlackBerry, so it's almost essential to me to be able to see if I have a text from across the room.
Click to expand...
Click to collapse
Agreed, that's the only thing I miss from my blackberry
Sent from my SGH-I777 using xda premium
Red5 said:
What answer do you really expect us to give you other than "yes"? Do you really think people in this forum is going to tell you no? Sounds to me like you already made up your mind to get this phone if you didnt like the Note or the OneX.
Click to expand...
Click to collapse
Btw, you seem to have a one x as well. What do you think when compared to your sgs2?
Sent from my Desire HD using Tapatalk
jthatch12 said:
Agreed, that's the only thing I miss from my blackberry
Click to expand...
Click to collapse
I miss the keyboard too. It was the one thing that made me choose a BlackBerry over an iPhone four years ago. I still hate the iPhone keyboard because of the lack of haptic feedback and the complete lack of customization options. Android is better though...with so many options for keyboards and setups, it almost makes up for not having physically keys...but I still miss them occasionally.
SysAdmNj said:
Btw, you seem to have a one x as well. What do you think when compared to your sgs2?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Honestly? Out of the box, the OneX works great. Even though the bootloader is currently locked, the phone works just fine the way it is and nothing really needs to be added to it. However, the OneX does have root and so you can install customs roms, just nor kernels or radios. Several tweaks, mods and roms have been created and flashes successfully.
On the flipside, the GSII is completely unlocked and there are several rom/kernel choices. There is some of the best Dev work done on XDA right here in this forum, so if your really interested in Dev support and choices, this is the phone to get.
Both phones are great. You just have to look at hardware specs, Dev support and see which road you want to take.
A yes from me as well.
For future, up-coming device such sgs3, if it will be released next week or two, then it might worth waiting but in this case, just a rumor, no officially released date yet, it could be months from now and even if released, what happen if it gets locked bootloader? It's not worth waiting if you're ROM-flashaholics.
votinh said:
A yes from me as well.
For future, up-coming device such sgs3, if it will be released next week or two, then it might worth waiting but in this case, just a rumor, no officially released date yet, it could be months from now and even if released, what happen if it gets locked bootloader? It's not worth waiting if you're ROM-flashaholics.
Click to expand...
Click to collapse
Take a look through this thread. No locked bootloaders. I think the dev support on the S3 is going to be huge.
mattdm said:
Take a look through this thread. No locked bootloaders. I think the dev support on the S3 is going to be huge.
Click to expand...
Click to collapse
Oh geez, I'm so behind, honestly I don't have time looking elsewhere but the i777 , thanks m8
I picked up the SGSII a month ago and absolutely love it. A huge upgrade from the previous generation (captivate).
I suspect that, much like desktop computers, going from one to two cores is significant, but you get diminishing returns after that.
Only downside is if you want true 4G. I spend so much time with wifi that I don't care.
Sent from my Omega'd ICS i777
Red5 said:
Honestly? Out of the box, the OneX works great. Even though the bootloader is currently locked, the phone works just fine the way it is and nothing really needs to be added to it. However, the OneX does have root and so you can install customs roms, just nor kernels or radios. Several tweaks, mods and roms have been created and flashes successfully.
On the flipside, the GSII is completely unlocked and there are several rom/kernel choices. There is some of the best Dev work done on XDA right here in this forum, so if your really interested in Dev support and choices, this is the phone to get.
Both phones are great. You just have to look at hardware specs, Dev support and see which road you want to take.
Click to expand...
Click to collapse
I'm definitely taking the dev support road. Thanks.
One of my last concerns is battery life. More of it having to do with charging time. I think I remember with the stock Rom charging times were slow from a wall charger if I remember reading this. Have charging times improved with custom roms/kernels?
I think Samsung devices in general have a bad rep with charging times?
I haven't seen any issues with charge times, but my expectations may be low. I have not timed it, but I would estimate under 3 hours to charge from less than 20% to full.
Sent from my Omega'd ICS i777
Coming from ATT, thinking about the DNA, my question is will it be receiving DEV support here? AOKP? Just wanting your opinions because I don't know your community. Thanks for any responses
Sent From my HOX, Swagger Initiated
seems harder to get aosp/aokp on cdma devices, but its not for lack of trying. RIL is almost always tougher. Most htc devices on verizon have an aosp ROM or 2, but they usually have broken features.
nrfitchett4 said:
seems harder to get aosp/aokp on cdma devices, but its not for lack of trying. RIL is almost always tougher. Most htc devices on verizon have an aosp ROM or 2, but they usually have broken features.
Click to expand...
Click to collapse
Meh, bout the only thing that's normally broken is Bluetooth, and sometimes video recording, other then that, it works. :good:
Argumentation said:
Meh, bout the only thing that's normally broken is Bluetooth, and sometimes video recording, other then that, it works. :good:
Click to expand...
Click to collapse
don't forget gps wonkiness.
Which do you prefer and why?
I prefer stock touchwiz, 100% reliable and the TW camera takes better pictures than AOSP.
Sent from my SCH-I605 using xda app-developers app
There is already a thread discussing this, though it has been derailed by the asinine "battery life" talk. Why people want to see how many days their phone can go without charging it I don't know.
I prefer aosp, but I use TW more because so far voice dialing over BT doesn't work on aosp and the volume is very low.
The theme engines on aosp as well as the reassigning soft button functions are very nice features.
I hardly use the s-pen or the multi window.
I prefer AOKP (AOSP) simply because of the look and certain functionality... You have a lot more features in AOKP than TW. But it also depends on the TW based ROM you install.. If you like the s-note and multi windows functions of TW you're better off with that ROM but things like ribbons soft keys 4.2.+ only apps (dash clock for example) and general UI themes, if you like that and can sacrifice the volume and the aforementioned calling over BT than AOKP is the way to go.. But over all stability and stock features that identify this phone as a Note 2, then a TW based ROM is what you want.. I recommend Jellybeans ROM
To be honest. It really depends on the user. Samsung spent a lot of time putting in features for their own version of Android. SPen functions that work for the people that use them and extras that keep the phone at the for front of app ability. If you have no intention of using the phone for what it was built for,love the essential specs then AOSP is for you. I myself like the functions and capability of Sammy in this aspect. As a long time HTC lover and Avid Sammy hater, have come to like the built in Samsung features. I love to hate this phone. As a person that is currently with a group of others suing Sammy over the Behold. I actually like this phone. Like all other companies, Samsung has created a very decent hardware phone and the feature set from them has made it work even better. Do I miss my HTC Sense features. OF course. Sense makes phones easy. But I've learned to make it work for me. End result, AOSP is too bland and short for me. I like ANDROID because I can make it my own. Customization is almost as easy on this is the same as others. I don't like Samsung's blatant Apple icon copy, but I know how to make it my own.
I prefer TW
I prefer AOSP, but until there's no gps issues I don't run it all the time. A lot Iof people say there are work a rounds, but I've learned from other phones that if gps isn't 100% working it'll mess up when you really need it even if it has been working. I really love multi window but not enough to overcome everything I hate about touchwiz.
TW until PA3.5 is ported I use multi windows too much and as far as I know the sammy keyboard is the only one that supports one-handed operation AND swype.
Sent from my SCH-I605 using xda premium
TW. I cant live without multiwindow
Sent from my SCH-I605 using xda premium
dragonstalker said:
To be honest. It really depends on the user. Samsung spent a lot of time putting in features for their own version of Android. SPen functions that work for the people that use them and extras that keep the phone at the for front of app ability. If you have no intention of using the phone for what it was built for,love the essential specs then AOSP is for you. I myself like the functions and capability of Sammy in this aspect. As a long time HTC lover and Avid Sammy hater, have come to like the built in Samsung features. I love to hate this phone. As a person that is currently with a group of others suing Sammy over the Behold. I actually like this phone. Like all other companies, Samsung has created a very decent hardware phone and the feature set from them has made it work even better. Do I miss my HTC Sense features. OF course. Sense makes phones easy. But I've learned to make it work for me. End result, AOSP is too bland and short for me. I like ANDROID because I can make it my own. Customization is almost as easy on this is the same as others. I don't like Samsung's blatant Apple icon copy, but I know how to make it my own.
Click to expand...
Click to collapse
So let me get this straight. You hate Samsung, and you are commenting on a Note 2 Poll, you own the Note 2 and are a part of a group suing Samsung, but you say you love to hate this phone and later say you " I actually like this phone" And you say you prefer HTC but your sig reveals that you use a Rezound, which is not a very good HTC phone... pardon me but can I have some of what your smoking:silly:
Lightyear25 said:
So let me get this straight. You hate Samsung, and you are commenting on a Note 2 Poll, you own the Note 2 and are a part of a group suing Samsung, but you say you love to hate this phone and later say you " I actually like this phone" And you say you prefer HTC but your sig reveals that you use a Rezound, which is not a very good HTC phone... pardon me but can I have some of what your smoking:silly:
Click to expand...
Click to collapse
Have you read why there is a lawsuit against Samsung for the Behold "scandal"?
Check it out:
http://gizmodo.com/5549228/samsung-behold-ii-users-consider-suing-over-android-20-snub
In my mind that's a frivolous lawsuit.....
Sent from my SCH-I605 using XDA Premium HD app
They pulled an Apple.
shangrila500 said:
Have you read why there is a lawsuit against Samsung for the Behold "scandal"?
Check it out:
http://gizmodo.com/5549228/samsung-behold-ii-users-consider-suing-over-android-20-snub
In my mind that's a frivolous lawsuit.....
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
shangrila500 said:
Have you read why there is a lawsuit against Samsung for the Behold "scandal"?
Check it out:
http://gizmodo.com/5549228/samsung-behold-ii-users-consider-suing-over-android-20-snub
In my mind that's a frivolous lawsuit.....
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
And here I thought I was an idiot for buying a Droid Eris for my first Android phone :laugh:
Dang that Behold is an old phone released in 2008. Here I thought my 2010 Epic 4G is old.
AOSP doesnt show my external sd card
Just to throw out my 2 cents..... Coming from a GNex, I was running 4.2.2 and thought it was great. I was due for an upgrade and got the Note 2. I thought I was taking a step back with 4.1.2, but I have to say, everything just works! No issues with GPS anymore, no battery drain (although there is no comparison to the battery of the gnex next to the note 2). I am reluctant to flash anything 4.2.2, because I don't want to have to worry if the things I need my phone to do for both work and personal use is going to work. I have to say, I would love to flash a couple AOSP roms, they look like they are making progress on the bugs by leaps and bounds, but until I can "count" on 99% of my phone working without issue..... Ima sticking to touchwiz based roms.
I prefer TW because of two main reasons.
1. Group texting
2. Better radio
With AOSP based roms, I get a constant roaming message at home. I don't get service here and have a network extender. Don't have this roaming issue with TW based stuff.
Group texting just doesnt work on AOSP. Yes I have the settings for group texting checked and all that I've read states that group texting works in 4.2.2 but I surely haven't seen it work.
Sent from my SCH-I605 using Tapatalk 4 Beta
Touchwiz for the fact I need to everything to function properly on my device. I use to play with AOSP alot but these days TW is spot on and all I use. I do like AOSP 4.2.2 on my Transformer...its my new crack flash device.
I remember the HTC Evo days. Boy, I spent hours-a-day browsing the development section on XDA to get my flash fix. That carried over with my Samsung Galaxy S2 and then the S3. Now that I'm considering coming back to HTC for a fresher experience, I found myself jaw-dropped at how ghostly the development forums are. I figured this could be a result of the phone being so young; so I went to the GS4 to see if that holds true. Wow... what a difference. Those forums seem busier than hell. And it's only been about a month since it was released as well.
Anyone have any idea why that is? I've been trying to convince myself to get the HTC One. I got over the fact that it lacks a replaceable battery, a MicroSD card, and recently, I got over the fact that the images are just not all that it's hyped up to be. I figured I'd be transitioning to the Moto X Phone when that comes out later in the year, so I might as well put-up with these shortcomings. But not having the development support that I experienced with the earlier HTC devices, and recently with the Samsung devices is just not something I think I can get over.
I am constantly thinking of the word "potential" when referring to this phone. What a shame. HTC had all the tools to flip the market on its feet, but it seems as if they came up short... again.
Check out the non-carrier-specific forum...it's pretty active.
EDIT: HTC didn't come up short, this phone is considered quite a success.
My theory for this specific forum being dead is that T-Mobile's national release of this phone was yesterday (06/05/2013). Before that, it was only available in their "high-volume" locations.
Oh wow. And all of those will work with the Tmo version?
Sent from my badass Samsung Galaxy SIII.
yea all the development is in the international forum. all roms on that forum will work on the tmo htc one and they work very well. i have flashed every sense based rom and most of the aosp roms. definitely not a ghost town over there:good:
Yeah, they should. But as always, continue at your own risk.
akarol said:
Oh wow. And all of those will work with the Tmo version?
Sent from my badass Samsung Galaxy SIII.
Click to expand...
Click to collapse
yes but the 4.2 sense roms havent implemented support for tmo yet they still work as im running trickdroid 7.0 now just no wifi calling yet but the 4.1 versions have wifi calling and most other tmo stuff
akarol said:
I remember the HTC Evo days. Boy, I spent hours-a-day browsing the development section on XDA to get my flash fix. That carried over with my Samsung Galaxy S2 and then the S3. Now that I'm considering coming back to HTC for a fresher experience, I found myself jaw-dropped at how ghostly the development forums are. I figured this could be a result of the phone being so young; so I went to the GS4 to see if that holds true. Wow... what a difference. Those forums seem busier than hell. And it's only been about a month since it was released as well.
Anyone have any idea why that is? I've been trying to convince myself to get the HTC One. I got over the fact that it lacks a replaceable battery, a MicroSD card, and recently, I got over the fact that the images are just not all that it's hyped up to be. I figured I'd be transitioning to the Moto X Phone when that comes out later in the year, so I might as well put-up with these shortcomings. But not having the development support that I experienced with the earlier HTC devices, and recently with the Samsung devices is just not something I think I can get over.
I am constantly thinking of the word "potential" when referring to this phone. What a shame. HTC had all the tools to flip the market on its feet, but it seems as if they came up short... again.
Click to expand...
Click to collapse
As you've noticed by now, there's plenty of developer support for the HTC One. It's all just confined to the general HTC One forums, which makes sense, as the various roms can be used on the AT&T, T-Mobile, and international HTC One's. Most developers don't want to have to maintain 3 or more separate threads for the same thing.
As was pointed out though, if you're looking for T-Mobile wifi calling compatibility, be careful about the ROMs you flash. Since the 4.2.2 OTA for T-Mobile isn't out yet, no 4.2.2 ROM is going to support it. I'd suggest Android Revolution 9.4, or a similar 4.1.2 ROM if WIFI calling is essential to you.
Also, since a Google edition of the phone is going to be coming out in the near future, developer support is likely going to expand even further.
So I think it's safe to say you can put your fears to rest and buy an HTC One. I don't think you'll regret it.
Yea I've been hanging out in the International One forums as almost all their ROMs work for us.
This forum really shouldn't even have a development section since there's not really any specific T-Mo stuff that needs to be done.
Every single ROM in the GSM section will work for T-Mo. There isn't a single one that won't work. The only thing you lose is T-Mo's branded stuff and T-Mo's wifi calling (as they are the only ones who do Wifi calling)/
LiquidSolstice said:
This forum really shouldn't even have a development section since there's not really any specific T-Mo stuff that needs to be done.
Every single ROM in the GSM section will work for T-Mo. There isn't a single one that won't work. The only thing you lose is T-Mo's branded stuff and T-Mo's wifi calling (as they are the only ones who do Wifi calling)/
Click to expand...
Click to collapse
Thanks you guys so much for your replies. I'm happy to see that the development forums for the One is indeed thriving. I'm more confident in snagging a one over the GS4 now.
Indeed, I don't see a reason as to why even bother with a Tmo specific section.
Sent from my badass Samsung Galaxy SIII.
akarol said:
Thanks you guys so much for your replies. I'm happy to see that the development forums for the One is indeed thriving. I'm more confident in snagging a one over the GS4 now.
Indeed, I don't see a reason as to why even bother with a Tmo specific section.
Sent from my badass Samsung Galaxy SIII.
Click to expand...
Click to collapse
Psssst... psssttt hey if u come we will welcome you!:screwy:
Sent from my SGH-M919 ddr3 13mp bad ass s4 using xda app-developers app
Firov said:
As you've noticed by now, there's plenty of developer support for the HTC One. It's all just confined to the general HTC One forums, which makes sense, as the various roms can be used on the AT&T, T-Mobile, and international HTC One's. Most developers don't want to have to maintain 3 or more separate threads for the same thing.
As was pointed out though, if you're looking for T-Mobile wifi calling compatibility, be careful about the ROMs you flash. Since the 4.2.2 OTA for T-Mobile isn't out yet, no 4.2.2 ROM is going to support it. I'd suggest Android Revolution 9.4, or a similar 4.1.2 ROM if WIFI calling is essential to you.
Also, since a Google edition of the phone is going to be coming out in the near future, developer support is likely going to expand even further.
So I think it's safe to say you can put your fears to rest and buy an HTC One. I don't think you'll regret it.
Click to expand...
Click to collapse
I was able to dig up an old link for Android Revolution 9.4 but can't find a description or list of features etc for it. Are you positive it has wi-fi calling in it?
I haven't owned an HTC since the OG Nexus One (had all Nexus devices since) so I'm reading up on S-OFF etc before I flash a new ROM. I really want to try out wifi calling though so that's why I'd like to make sure. Thanks in advance!
PS - link to ROM if anyone wants it: http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_9.4.zip
the7thson said:
I was able to dig up an old link for Android Revolution 9.4 but can't find a description or list of features etc for it. Are you positive it has wi-fi calling in it?
I haven't owned an HTC since the OG Nexus One (had all Nexus devices since) so I'm reading up on S-OFF etc before I flash a new ROM. I really want to try out wifi calling though so that's why I'd like to make sure. Thanks in advance!
PS - link to ROM if anyone wants it:
Click to expand...
Click to collapse
9.4 definitely has wifi-calling. I'm on 9.3 at the moment and wifi-calling works perfectly for me on T-Mobile. In the installer, just be sure to select T-Mobile as your carrier and it will install all the necessary files for wifi calling.
Also, note that S-Off isn't required to flash this ROM. All you need to do is unlock your device through HTC Dev, located at the HTC Dev site. I'd give you a direct link, but asinine restrictions in place on this forum are preventing that at the moment. Just Google HTC Dev and it will be the first result. You can't miss it.
Anyway, unlike with earlier HTC devices, this unlock method allows you to flash everything you need to update the ROM. Only some of the "black box" partitions like the radio and bootloader aren't flashable when it's unlocked with this method, but to my knowledge, no ROM requires that, and furthermore, the Nexus devices are very similar in that respect.
The only real advantage to S-Off is if you plan on flashing a different carrier's RUU, altering the radio, or changing your CID. Anyway, just something to be aware of.
Good luck.
Firov said:
9.4 definitely has wifi-calling. I'm on 9.3 at the moment and wifi-calling works perfectly for me on T-Mobile. In the installer, just be sure to select T-Mobile as your carrier and it will install all the necessary files for wifi calling.
Also, note that S-Off isn't required to flash this ROM. All you need to do is unlock your device through HTC Dev, located at the HTC Dev site. I'd give you a direct link, but asinine restrictions in place on this forum are preventing that at the moment. Just Google HTC Dev and it will be the first result. You can't miss it.
Anyway, unlike with earlier HTC devices, this unlock method allows you to flash everything you need to update the ROM. Only some of the "black box" partitions like the radio and bootloader aren't flashable when it's unlocked with this method, but to my knowledge, no ROM requires that, and furthermore, the Nexus devices are very similar in that respect.
The only real advantage to S-Off is if you plan on flashing a different carrier's RUU, altering the radio, or changing your CID. Anyway, just something to be aware of.
Good luck.
Click to expand...
Click to collapse
Sweet, thanks I'll definitely try 9.4 then! Reception in my office all day is terrible so I'm excited to try wi-fi calling.
I think I understand in theory why S-OFF would not be needed. but the nerd in me wants full control with S-OFF.. Also, if I use S-OFF, i can return my phone to bone-stock and keep warranty right? As amazing as the hardware on the HTC One is (I've gotten used to sub-standard hardware with the Nexus line), I'm not 100% sure yet I want to keep it.
Any chance you could educate me on what CID is for? Evidently it may restrict/allow flashing ROMS from certain regions?
Also, I believe I have a basic understanding of what an RUU is, but could you elaborate for me by any chance? I believe it's basically an all i one installer for a full stock ROM?
Sorry if this is a bit off-topic, but this T-Mo sub forum seems a bit more forgiving than some other areas
the7thson said:
Sweet, thanks I'll definitely try 9.4 then! Reception in my office all day is terrible so I'm excited to try wi-fi calling.
I think I understand in theory why S-OFF would not be needed. but the nerd in me wants full control with S-OFF.. Also, if I use S-OFF, i can return my phone to bone-stock and keep warranty right? As amazing as the hardware on the HTC One is (I've gotten used to sub-standard hardware with the Nexus line), I'm not 100% sure yet I want to keep it.
Any chance you could educate me on what CID is for? Evidently it may restrict/allow flashing ROMS from certain regions?
Also, I believe I have a basic understanding of what an RUU is, but could you elaborate for me by any chance? I believe it's basically an all i one installer for a full stock ROM?
Sorry if this is a bit off-topic, but this T-Mo sub forum seems a bit more forgiving than some other areas
Click to expand...
Click to collapse
It's worth doing to S-OFF. If you do, you'll have the ability to relock the phone and put it back to S-ON with zero indication that you ever messed with it. Also, CIDs are used to restrict ROMs from certain carriers to only be installed on certain devices. It's really only a stock or stock-leak ROM limitation, I don't think a single ROM in either the regular or original development section is CID-locked. Either way, if you are S-OFF, you can change your CID code to whatever you want it to be (the code "111111") is referred to as "SuperCID" because that allows you to in theory run an RUU/OTA from ANY Carrier regardless.
You are correct about what an RUU is. However, each RUU is specific to a build of Android made by the carrier, and so far, I think only the Sprint RUU is out. No one has a T-Mo RUU yet (but you really don't need one, all you have to do is flash the stock rooted ROM from our section here and then unroot from the SU app options).
Enjoy tinkering.
LiquidSolstice said:
It's worth doing to S-OFF. If you do, you'll have the ability to relock the phone and put it back to S-ON with zero indication that you ever messed with it. Also, CIDs are used to restrict ROMs from certain carriers to only be installed on certain devices. It's really only a stock or stock-leak ROM limitation, I don't think a single ROM in either the regular or original development section is CID-locked. Either way, if you are S-OFF, you can change your CID code to whatever you want it to be (the code "111111") is referred to as "SuperCID" because that allows you to in theory run an RUU/OTA from ANY Carrier regardless.
You are correct about what an RUU is. However, each RUU is specific to a build of Android made by the carrier, and so far, I think only the Sprint RUU is out. No one has a T-Mo RUU yet (but you really don't need one, all you have to do is flash the stock rooted ROM from our section here and then unroot from the SU app options).
Enjoy tinkering.
Click to expand...
Click to collapse
Perfect, thanks for confirming all that. I think I'm ready to get the HTC-noob stink off of me The phone feels so amazing in hand, it's making me look at all these Nexus devices (Nexi?) I have in a bit of a different light.. And once the Google Experience software drops, hopefully I won't miss having a Nexus as my daily driver!
You guys are so awesome. I'm counting down the days until July 1st now when I'll get my hands on my own HTC One. =)
Sent from my badass Samsung Galaxy SIII.
the7thson said:
Perfect, thanks for confirming all that. I think I'm ready to get the HTC-noob stink off of me The phone feels so amazing in hand, it's making me look at all these Nexus devices (Nexi?) I have in a bit of a different light.. And once the Google Experience software drops, hopefully I won't miss having a Nexus as my daily driver!
Click to expand...
Click to collapse
akarol said:
You guys are so awesome. I'm counting down the days until July 1st now when I'll get my hands on my own HTC One. =)
Sent from my badass Samsung Galaxy SIII.
Click to expand...
Click to collapse
You're going to enjoy the One. It's the first Android phone to have the build quality of an iPhone with specs that beat the pants off it
The only thing that sucks about the One is that because it has such a high pixel density, you will be extremely sensitive and aware of pixels in all your other displays (laptop/desktop/tablet etc).
I own an ASUS Zenbook, which is a 13" ultrabook with a full 1920x1080p display which is retina-levels of dense on such a small screen (I think it's almost 170 pixels per inch). The One? The one is a whopping ~470 pixels per inch. It is stupidly dense and I promise you won't find a single pixel no matter how hard you look.
the7thson said:
I was able to dig up an old link for Android Revolution 9.4 but can't find a description or list of features etc for it. Are you positive it has wi-fi calling in it?
I haven't owned an HTC since the OG Nexus One (had all Nexus devices since) so I'm reading up on S-OFF etc before I flash a new ROM. I really want to try out wifi calling though so that's why I'd like to make sure. Thanks in advance!
PS - link to ROM if anyone wants it: http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_9.4.zip
Click to expand...
Click to collapse
would anyone happen to have a working link for Android Revolution 9.4???
jjohn999 said:
would anyone happen to have a working link for Android Revolution 9.4???
Click to expand...
Click to collapse
Look like they took it down. I have it in my local computer here and I can upload it for you somewhere if you like. PM me if you have access to somewhere I can put it for you.
Good Morning to you all!
Sorry if this has already been posted but I couldn't find much of anything on this topic. Does a "Google Edition" Rom exist for the EVO 4G LTE? I know we have the AOSP and AOKP roms but this is something I've wanted to ask for a while. I love the pure Google experience and I just have to wait about a year until i can upgrade to a new phone like a Nexus.
Thank you again for taking the the time to read this and for all the awesome work all you Developers put in for making this awesome phone even better.
Sent from my EVO using xda app-developers app
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
I'm with you on that one. Not sure why anyone with knowledge of rooting (who doesn't mind a voided warranty) would want to buy a GE phone.
______________________________
HTC Evo 4G LTE
I don't have any problem with any AOSP Rom other than signal and connectivity issues. But its really just curiosity for me and I'm a big fan of Google so the idea of having a Google Editon EVO sounds cool to me.
Sent from my EVO using xda app-developers app
Well it won't happen.
And aosp is just as much Google as a GE would be.
Sent from my Nexus 7 using xda premium
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
scottspa74 said:
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
ZamoraDC said:
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You could always try Evervolv. That's probably the closest to AOSP, that is, with the least customization.
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
How difficult is this to do?
Sent from my EVO using xda app-developers app
ZamoraDC said:
How difficult is this to do?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I can't say.
For the DNA it was extremely simple (but zarboz is a boss so he would've gotten it anyway) since the two devices are almost identical (One and DNA).
But the fact that you guys have a 3.4.x official HTC kernel should help.
hacked together using core binaries from other devices when necessary.
Click to expand...
Click to collapse
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
If you think about it, this site probably wouldn't even exist if OEMs made good software. They often do have access to proprietary drivers and documentation, but most of that is slowly getting open sourced anyway.
That type of reasoning is a fallacy because more often then not OEMs are just too plain cheap to do things properly. They just need to hit their deadlines. So your only real options are to either buy a nexus device, or invest a little time in helping fix any issues that you may find.
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
Have you ever used one of the IRC builds of cm10 or cm10.1? They're more stable and are more feature rich than the stock ROM that shipped with this device or any of the updates that they were gracious enough to let sense users download over the air. The 3.0 kernel was seriously stable, but the 3.4 kernel is (nearly as) stable _and_ leaves more RAM for your silly animation effects and whatever. It's based on the reference kernel for the chip set, if I'm not making an arse of myself. So pick a build. I know 1/16 was an awesome cm10, and like I said in another topic I had 191 hours uptime on the 7/23 cm10.1 before I rebooted to rule out the ROM when I was having data issues(it was the network) </rant>
Sent from my EVO using xda app-developers app
xHausx said:
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
Click to expand...
Click to collapse
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
xHausx said:
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
Click to expand...
Click to collapse
Ha! That was my first smartphone! I first signed up on xda (under a different name) when that phone launched (I got it as the att tilt) so that I could run manila and then android on it! That display driver issue was so frustrating. Sorry for ot, but I haven't thought about that in ages.
CNexus said:
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
Click to expand...
Click to collapse
It's not accurate to say the binaries are made for other devices when the devices are all basically the same. The MSM8960, for example, has it's own binaries, but the same chip is used in a range of devices from the Evo LTE, Blackberry Z10, One X (LTE), One XL, Windows Phone 8X, LG Mach, Moto Droid Razr M, Droid Razr, Razr Max, Atrix HD, Incredible HD, Xperia GX TL SX & V, Galaxy S III... the list goes on
The binaries all of those devices use were developed for the Qualcomm devkit I've linked below.
When you're working with a sense ROM versus an AOSP ROM there are many differences in not only appearance but the framework as well, but once you start getting down to the kernel level the hardware is all basically the same. Where we have the advantage over OEMs is that most companies know it's counterproductive and a waste of money to go after enthusiasts who borrow their binaries from one device to use on something else. If an OEM did that they would be sued in a heartbeat.
https://developer.qualcomm.com/mobile-development/development-devices/snapdragon-s4-msm8960-mdps
edit: probably actually this instead, but same difference: http://shop.intrinsyc.com/products/dragonboard-members-only
To digress back to the OP's original question though, the google edition One is basically just the one with AOSP on it. If you can find a pure AOSP ROM it'll be the exact same thing.
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
ZamoraDC said:
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Why don't you just build AOSP? You can use the CM kernel and pull the relevant vendor files from an existing AOSP ROM (or find an up-to-date github with them).
That way you don't have to worry about having the extra customizations, but you'll still have a kernel built from Qualcomm source along with the ROM.
asop aokp cm
I have tried a lot of ROMs and I find these devs do a much better job than stock ROMs yes you have some bugs in some but the always work them out cudos to the devs I'm just glad they still support my device and having gabe up on it