Related
Sorry, I'm sure this was probably asked before. Is it drivers or just the parts used? I notice HTC devices seem faster to hack up. I'm going to be upgrading my device sometime in the next 6 months and would love a Galaxy S2 but if the same hardships faced with the Vibe will be present again- I think I might go back to HTC. missmysamoled.jpg
Lol. Again, sorry if this has been beaten to death.
Sent from my SGH-T959 using XDA App
Samsung lol. That's about the most fact-filled short answer you can get. Their releases are horribly late. Vibrant just got 2.2 OTA, CM is at 2.3.3. HTC has been far more supportive of AOSP as well. Samsung......not so much.
I recently moved to Sprint from T-Mobile and as you can see(sig) got me the Evo. I wish I had waited a few months for the 3d but maybe I'll sell the Evo and do my own upgrade when the time comes. I won't say I'll never buy Samsung again but I will be fully aware of what I am getting if I do.
My best answer.
It has to do with HTC phones run with stock Android and so the devs can work with the new source code faster cause they don't have to deal with proprietary or manufacturer's modded source.
sixteenbit said:
It has to do with HTC phones run with stock Android and so the devs can work with the new source code faster cause they don't have to deal with proprietary or manufacturer's modded source.
Click to expand...
Click to collapse
I thought htc used sense
It's because cyanogen team knows what to do with htc phones plus htc releases source codes unlike samsung.
Sent from my SGH-T959 using XDA App
blahbommer said:
I thought htc used sense
Click to expand...
Click to collapse
You are correct. The only htc phones I know of that are AOSP are the G2 and N1. That's off the top of my head though.
Sent from my "TriggerHappy" Vibrant!
There are a lot of differences between how HTC and Samsung do things... these guys also started and know HTC a lot more. HTC IS better about releasing source. Heck, Samsung doesn't release everything even when they do (driver source).
All that said though... I really do not understand why someone has not been able to get a solid RC for us. I honestly do not even know who is working on CM7 for the Vibrant, and it's not officially supported...
I know a lot of progress has been made, but the CM7 we have still has a lot of work to do. Just wish those more in the know could really get that ball rolling, instead of using leaks (esp I9000 leaks which have proven to be terrible on our battery).
I don't know enough, but I know people on here do....
Introduction:
This project is temporarily on hold due to financial hardships. I plan to be back very soon.
Since we have HoneyComb for the Flyer already, I wanted to start a thread to try and get HC ported to the View for us Sprint junkies. I'd like to gather information, not only for porting HC, but for the View as a whole. I've done a ton of searching and still haven't found hardly any info for it.
Questions:
These are the random questions I have for now:
-Does the View run the same hardware as the Flyer?
-What all hardware is in the View?
-What are the odds of successfully flashing the Flyers Radio.img/hboot.img to the View
-Others that I haven't thought of, or don't have the time to write out at the moment.
I'd greatly appreciate all the support I can get on this. I'm not familiar with the View or Flyer at all. I come from Evo 4G and Evo 3D development and would really like to get into the View as well.
Thanks in advance everyone.
Reserved...
Mine too...
Can't contribute much right now, but like the train of thought. I can't imagine hardware wise anything other than the radio is different.
I'd like to know what the flyers partitions look like. If someone could run adb shell df - h and paste the output here that would help immensely.
Sent from my PG86100 using Tapatalk
mbobino said:
I'd like to know what the flyers partitions look like. If someone could run adb shell df - h and paste the output here that would help immensely.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Wow, I'm very glad someone has come up and decided to do this.
1. I feel like it might be a bit of a waste considering HC is SUPPOSED to be officially released in the future. So it would suck if you did all this hard work to make the port and then like 2 weeks later we get the official version to work with.
2. I will run that command when I get home in like an hour and show you the output.
I wouldn't mind helping you in someway, if I can. I'm familiar with linux command line and such ie. i know what df -h does and what it means and all that stuff, BUT I've never played around with making ROMs or anything like that.
Any help I can give, I'm down to do. Good luck.
edit: I see you are looking for the FLYER'S parition table, not the view's.... my bad.
I feel like a complete douche in doing this but I have to put this project on hold. I've recently come into some financial trouble and had to sell my View for some extra cash. I do have plans to continue this project once I can manage to afford another View. As for the possibility of HTC releasing HC for it before I can get it going, oh well, thats the risk we take when we develop lol.
Can I help beta test this once its up again?
Would it help for the dev to own both a flyer and a view to get development done?
I haven't gotten to take a look at the flyer, but I am under impression that the view is not too much different...
We also have a donation going on in the general chat for someone to develop on the view, if this works for the OP
Apart from the 4G and CMDA capabilities, the flyer and the evo view 4G are one and the same tablet.
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
Fixter said:
Apart from the 4G and CMDA capabilities, the flyer and the evo view 4G are one and the same tablet.
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
Click to expand...
Click to collapse
Yeah, only the radios and the color are different. I suppose if you could take the official HC build for the Flyer and somehow merged the WiMax and CDMA code into that build it may work, but I'm not well versed on how to go about doing that. I see builds on the Evo 3D that are Sense 3.5 but they don't have working 4G for whatever reason.
On the OG Evo they made 4G work on CM7 by building code from the ground up to work with the hardware, but it hasn't moved over to 3D yet and there is no official build from CM for the 3D. Maybe that code could be ported? Of course it would probably have to be an AOSP build which I've not seen yet for either the View or Flyer.
I sold my Flyer Wifi and picked up an Evo View 4G so hopefully this gets sorted out. Would really like to get Honeycomb on the View. I really enjoyed it on the Flyer!
spartan1987 said:
Yeah, only the radios and the color are different. I suppose if you could take the official HC build for the Flyer and somehow merged the WiMax and CDMA code into that build it may work, but I'm not well versed on how to go about doing that. I see builds on the Evo 3D that are Sense 3.5 but they don't have working 4G for whatever reason.
On the OG Evo they made 4G work on CM7 by building code from the ground up to work with the hardware, but it hasn't moved over to 3D yet and there is no official build from CM for the 3D. Maybe that code could be ported? Of course it would probably have to be an AOSP build which I've not seen yet for either the View or Flyer.
Click to expand...
Click to collapse
Actually there are more differences that that, although that is where they all stem from for sure.
We don't even have source for the Flyer HC release yet, so the work needed would be even worse. It's really not worth looking at until we have source and by that time given the traditional HTC lag in releasing it we'll have HC on the view already.
globatron said:
Actually there are more differences that that, although that is where they all stem from for sure.
We don't even have source for the Flyer HC release yet, so the work needed would be even worse. It's really not worth looking at until we have source and by that time given the traditional HTC lag in releasing it we'll have HC on the view already.
Click to expand...
Click to collapse
Agreed
In theory...
spartan1987 said:
On the OG Evo they made 4G work on CM7 by building code from the ground up to work with the hardware, but it hasn't moved over to 3D yet and there is no official build from CM for the 3D. Maybe that code could be ported? Of course it would probably have to be an AOSP build which I've not seen yet for either the View or Flyer.
Click to expand...
Click to collapse
I was reading about here for the possibility of an AOSP build, if there is one done, it's likely we would loose pen input functionality on Flyers and Views since it seems to be based on sense.
globatron said:
Actually there are more differences that that, although that is where they all stem from for sure.
We don't even have source for the Flyer HC release yet, so the work needed would be even worse. It's really not worth looking at until we have source and by that time given the traditional HTC lag in releasing it we'll have HC on the view already.
Click to expand...
Click to collapse
Well the source code has been released for the Flyer on honeycomb, man I can't wait for development to get underway to bring it over the the view!
spartan1987 said:
Agreed
In theory...
Click to expand...
Click to collapse
Lol, eating my own words, first time I've seen them do it that quick.
Yeah that was quick, I'm sure it's no coincidence it was right before Christmas. I'll miss the hardware keys but its for my daughter anyways, don't think she'll mind
make sure to read globatron's sticky in the general section before accepting the HC OTA update. strong recommendation to wait until there is a patched hboot so that your device isn't forced back into a permanent s-on
Honeycomb for EVO View is now available!!
nativ73 said:
Yeah that was quick, I'm sure it's no coincidence it was right before Christmas. I'll miss the hardware keys but its for my daughter anyways, don't think she'll mind
Click to expand...
Click to collapse
Honeycomb for EVO View is now available. While its a huge change and many more features are available, I'm skiddish about loosing some apps which won't work in 3.2.
Please post your reviews of the new system. Many of us would love to read about your experience.
I am wondering given that this device just got honeycomb.. is there any chance of it getting ICS?
Part of the reason I'm wondering is because I am getting my flyer sometime between the 10th and the 17th coming up according to the "estimated delivery date" when I hit buy.
I have had ICS on my captivate before I ever even got to play with Honeycomb.. my mom got the transformer yesterday.. and there are a few minor quirks with honeycomb that I really don't like.. major example being if you pull up the task manager in ICS you can remove windows and close out the programs.. Honeycomb will pull up windows that aren't open.. and it gets cluttered fast if your done with something and seeing 5 or more windows you don't want open, but can't get rid of..
no sign of ICS anytime soon but maybe if kernel source is released and CM9 development someone will port it here. In regards to the task management, yes it can get cluttered but it is better than not having it at all like gingerbread
I'm hoping they'll have the decency to update us or at least release the source code required...
IANAL, but I believe HTC legally has to release the kernel source for anything it releases. If they never release ICS, we may never get a kernel for ICS.
Honeycomb kernel might work, but I'm not sure if HTC is legally required to release honeycomb kernel source.
As far as I am aware, they did/may have use some proprietary software which would screw up our porting efforts.
So it becomes an issue of "will they" and that is what I am wondering.
Personally I don't think we will ever see ICS on the Flyer. Here are my reasons:
1. Not a lot of Flyers were sold so there is not a large user base. Thus, there is not much developer interest.
2. Sense - From what I understand from what developers have said, the kernels that HTC makes are made to work with Sense and will not work with an AOSP build.
These two things combine to make bringing ICS to the Flyer difficult and there is no one around who appears willing to do it.
I really hope that I am wrong about this but I don't think that I am.
Someone want to educate a noob?
How is it that several other devices (including HTC ones, like the Sensation) are getting ICS ports, but the Flyer/View can't? I mean, it seems unlikely that HTC released AOSP kernel sources for other devices, and even if they did, they're certainly not ICS kernels. Why is it so important for us to have an AOSP kernel (and an ICS one, at that) from HTC in order to get CM on the Flyer/View?
Oh, and then there's devices that didn't even have Android like the TouchPad, and devices that don't have their source code released, like the Kindle Fire.
I'm definitely not a developer, so I'm sure there's something I'm missing...I'm just trying to figure out what it is.
I'm repeating what developers told me or wrote here. I don't know if it is right or wrong.
I think the bottom line is that it is easier to have an AOSP kernel.
I think you can build your own kernel but that is much more work and maybe a hard thing to do.
All of the custom ROMs that we have seen for the Flyer are just modified HTC ROMs that come with certain software preinstalled or other kinds of enhancements.
More popular devices have much more developer interest. I would imagine that some less popular device owners get lucky because some developer also owns the device and is willing to spend the time.
So far, one developer said he would try to bring ICS to Flyer. He tried but gave up because of kernel issues. I don't get the impression that he did too much but at least he gave it a go. No other developer has said anything one way or the other.
I'm not holding my breath..
but, I definitely won't give up hope just yet..
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
DigitalMD said:
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
Click to expand...
Click to collapse
Makes sense to me.
Shame this device hasn't received more attention.
DigitalMD said:
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
Click to expand...
Click to collapse
This is correct and likely the only way we see ICS in a timely manner.
Sent from my HTC_Flyer_P512_NA using Tapatalk
https://plus.google.com/105502178297258827378/posts/PxQ6cVjVdUd
dingnecros said:
https://plus.google.com/105502178297258827378/posts/PxQ6cVjVdUd
Click to expand...
Click to collapse
He's been debunked several times.
Sent from my HTC_Flyer_P512_NA using Tapatalk
So I guess the big question as far as an official update goes.. is how much effort would HTC have to put out in order to do the upgrade...
And will it be worth it for them to do so..
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
ytwytw said:
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
Click to expand...
Click to collapse
Would it be possible to take the pen code from honeycomb and implement it in CM9?
ytwytw said:
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
Click to expand...
Click to collapse
I'd be content with an AOSP rom now, with the pen worked in later.
Sent from my HTC Flyer P510e using Tapatalk
We will see... if any devs are willing, I am sure as heck willing to help and take a crack at it myself..
You can't do AOSP without HTC's help for the kernel and drivers and since HTC only does sense kernels I'm thinking that's not going to happen. I still think a port of an HTC ICS ROM from another device is the most likely path, unless HTC is feeling exceptionally benevolent toward the Flyer. Perhaps the Jetstream tablet will get ICS and that can be ported...
I'm not too familiar with the reasons and the technical stuff. Why isn't there a reliable AOSP ROM for the Rezound? What is it exactly that makes it difficult to develop one?
The ril hasn't been completely worked out for any AOSP roms
It has to do with the way Google has implemented support for CDMA devices. Google doesn't officially support CDMA devices in the Android framework they provide, so its up to device manufacturers (HTC) to create the necessary support and add it in. Right now, the developers who make ROMs are probably tearing apart the recent HTC leaks looking for the bits and pieces they need to put an AOSP ROM together.
It is the LTE that is the problem. Basically any CDMA device can get AOSP no problem but our device has a very complicated radio. It supports CDMA+LTE+EVDO+GSM so it is pretty much hacked together by HTC themselves.
I tell you one thing. The first developer who provides a near perfect working of ICS AOSP is going to get $15 from me.
con247 said:
It is the LTE that is the problem. Basically any CDMA device can get AOSP no problem but our device has a very complicated radio. It supports CDMA+LTE+EVDO+GSM so it is pretty much hacked together by HTC themselves.
Click to expand...
Click to collapse
Not that I know anything about this subject, how did the Thunderbolt get it solved in the end?
the non-Sense development has been disappointing so far, no AOSP and no MIUI....I think the people talking about the ril have it right, if it was LTE that was the problem we'd have AOSP roms out that don't have working LTE like some other phones do
I Am Marino said:
Not that I know anything about this subject, how did the Thunderbolt get it solved in the end?
Click to expand...
Click to collapse
Not sure but it was easier for the bolt cause s-off.
So is it right to assume that if we get full s-off then comes AOSP?
What exactly is s-off?
Cares said:
So is it right to assume that if we get full s-off then comes AOSP?
Click to expand...
Click to collapse
it's possible but can't really be proven since we literally have full access with the exception to the actual radios when flashing. devs can already view radios to iron out the issues. it's just tricky to solve a scattered puzzle
S-OFF has NOTHING I repeat NOTHING to do with AOSP. The TBOLT had more people working on it and the RIL isn't probably as complicated. They still don't have AOSP ICS working either.
Any developers actively working on this? What would it take for CM to start? Do they need the RIL figured out?
Cares said:
Any developers actively working on this? What would it take for CM to start? Do they need the RIL figured out?
Click to expand...
Click to collapse
There is an active CM9 Alpha thread in the dev section with updates on where it is.
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.