Any chance of running a vanilla version of gingerbread?
r_3 said:
Any chance of running a vanilla version of gingerbread?
Click to expand...
Click to collapse
Once HTC releases the kernel source code for the Inspire, then the work on a CM 7 compatible kernel can begin.
If you want to play around with it, you can install the DHD version. It runs quite well besides having no audio. The source code is needed to build a kernel that supports the inspires audio.
tpbklake said:
Once HTC releases the kernel source code for the Inspire, then the work on a CM 7 compatible kernel can begin.
Click to expand...
Click to collapse
How long after releasing a device is the manufacturer supposed to release the source code? I'm not too familiar with the whole open source thing
HTC is quite good about it. Usually a couple of weeks or so.
JaysFreaky said:
HTC is quite good about it. Usually a couple of weeks or so.
Click to expand...
Click to collapse
Ahh cool, hopefully sooner than later xD I haven't had any Cyanogen love since my Nexus One
r34p3rex said:
Ahh cool, hopefully sooner than later xD I haven't had any Cyanogen love since my Nexus One
Click to expand...
Click to collapse
Yeah I hear you. I've never had a device that was really supported (loaded it on my Streak, but next to nothing worked). I've always flashed my friends devices with it and I'm quite jealous. lol
Good news is that they plan to support it. If you go to their forums they've added the Inspire to the Desire HD.
This is great news I have also installed a ton of cm7 on all of my buddies phones and can't wait to actually run it myself.
Sent from my Desire HD using XDA App
tpbklake said:
Once HTC releases the kernel source code for the Inspire, then the work on a CM 7 compatible kernel can begin.
Click to expand...
Click to collapse
What is it that htc does or doesn't do that makes so many of its phones compatible with cm? Or does the cm crew simply prefer to support htc phones compared to others?
peachpuff said:
What is it that htc does or doesn't do that makes so many of its phones compatible with cm? Or does the cm crew simply prefer to support htc phones compared to others?
Click to expand...
Click to collapse
well, for starters, they use the standard mtd partition layout (unlike Samsung who uses bml) which means the "fastboot" commands can work. on top of that, their devices are also usually extraordinarily similar between generations which leads to most of the exploits and such working on multiple phones. so you have a LARGE number of devices being worked on by a LARGE number of developers with extreme similarities. this leads to a lot of tools working on multiple devices (the Inspire is actually a good example of this, seeing as how it's basically a Desire HD... it's even got the Ace codename--same as the Desire HD) which makes the rapid pace of development understandable.
Add to the fact that htc and tmobile (who had the first android phone which also happened to be htc) both encourage this "hobbyist" attitude from the developer community on non-dev phones (all dev phones were htc until the Neuxs S... G1/ADP, Magic/Ion, Nexus One... and they are almost entirely open source from my understanding) to both encourage people to buy their phones and also to ENJOY their phones. HTC provides software they consider to be the best "overall user experience" and I think that means they provide android (usually with Sense UI) so that it will appeal to the widest range of people. But then there are people who want that vanilla UI without buying the dev phone (such as myself and possibly you) and I'm betting htc doesn't want to actively discourage people having this option because it means improved sales from the hobbyist community. Now I have no inside info, but I'm sure the only exploits and such that they patch are security vulnerabilities (which are the ones exploited to get root). htc even fixed cyanogen's personal Nexus One due to a faulty power button even though his "hackery" voids the warranty. Tmobile provided/collaborated with cyanogenmod with the theme-ing engine for CM7. This history of collaboration between google, htc, tmobile, and the developer community has led to strong ties and familiarity with the platform.
tl;dr:
tmobile likes having the developers on their service because it means more subscribers; htc likely wants to appeal to both the average consumer and the developers so offers an out of the box experience that most can enjoy (Sense) but doesn't actively try to discourage developers.
Kaik541 said:
well, for starters, they use the standard mtd partition layout (unlike Samsung who uses bml) which means the "fastboot" commands can work. on top of that, their devices are also usually extraordinarily similar between generations which leads to most of the exploits and such working on multiple phones. so you have a LARGE number of devices being worked on by a LARGE number of developers with extreme similarities. this leads to a lot of tools working on multiple devices (the Inspire is actually a good example of this, seeing as how it's basically a Desire HD... it's even got the Ace codename--same as the Desire HD) which makes the rapid pace of development understandable.
Add to the fact that htc and tmobile (who had the first android phone which also happened to be htc) both encourage this "hobbyist" attitude from the developer community on non-dev phones (all dev phones were htc until the Neuxs S... G1/ADP, Magic/Ion, Nexus One... and they are almost entirely open source from my understanding) to both encourage people to buy their phones and also to ENJOY their phones. HTC provides software they consider to be the best "overall user experience" and I think that means they provide android (usually with Sense UI) so that it will appeal to the widest range of people. But then there are people who want that vanilla UI without buying the dev phone (such as myself and possibly you) and I'm betting htc doesn't want to actively discourage people having this option because it means improved sales from the hobbyist community. Now I have no inside info, but I'm sure the only exploits and such that they patch are security vulnerabilities (which are the ones exploited to get root). htc even fixed cyanogen's personal Nexus One due to a faulty power button even though his "hackery" voids the warranty. Tmobile provided/collaborated with cyanogenmod with the theme-ing engine for CM7. This history of collaboration between google, htc, tmobile, and the developer community has led to strong ties and familiarity with the platform.
tl;dr:
tmobile likes having the developers on their service because it means more subscribers; htc likely wants to appeal to both the average consumer and the developers so offers an out of the box experience that most can enjoy (Sense) but doesn't actively try to discourage developers.
Click to expand...
Click to collapse
And this is why HTC is full of win
If only the Inspire had a front facing camera, it'd be perfect.
r34p3rex said:
And this is why HTC is full of win
If only the Inspire had a front facing camera, it'd be perfect.
Click to expand...
Click to collapse
I agree! I have heard on XDA that there should be an HTC Android device on At&t later this year with the front facing camera and all that.
Sent from my Desire HD using XDA App
mentalcase said:
If you want to play around with it, you can install the DHD version. It runs quite well besides having no audio. The source code is needed to build a kernel that supports the inspires audio.
Click to expand...
Click to collapse
Can we install CM7 then install our original radio to get sound back?
kirbo20 said:
Can we install CM7 then install our original radio to get sound back?
Click to expand...
Click to collapse
Sounds more like a kernal issue.
kirbo20 said:
Can we install CM7 then install our original radio to get sound back?
Click to expand...
Click to collapse
No. It's the kernel...not the radio.
Sent from my Desire HD using XDA App
I have never tried out CM at all so I will deffinately check it out once it is available for the Inspire
Just tried out CM7, no audio as expected. Someone needs to figure out what makes the Inspire kernel different from the standard Desire HD kernel, then port it to the CM7 kernel xD
r34p3rex said:
Just tried out CM7, no audio as expected. Someone needs to figure out what makes the Inspire kernel different from the standard Desire HD kernel, then port it to the CM7 kernel xD
Click to expand...
Click to collapse
You need the source first.
Sent from my Captivate.
From what I understand CM7 RC1 was released for the Desire HD last night so all we should need is an appropriate kernel to flash over that. I also read some people were able to get sound from a TELUS kernel for that device. Can anyone confirm that?
Sent from my Inspire 4G using XDA App
rootdude said:
From what I understand CM7 RC1 was released for the Desire HD last night so all we should need is an appropriate kernel to flash over that. I also read some people were able to get sound from a TELUS kernel for that device. Can anyone confirm that?
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Seems any dhd Rom will work. If cm7 was ported then it should work like any other Rom with the TELUS.
Inspire (rooted)
Leedroid v2.0.0
TELUS kernel
Related
Since I have very little technical knowledge, I want to ask the people who do: Do you think the signed HTC bootloaders can be cracked?
Are they bulletproof? Is it just a matter of time? No idea?
Lord Panzer said:
Since I have very little technical knowledge, I want to ask the people who do: Do you think the signed HTC bootloaders can be cracked?
Are they bulletproof? Is it just a matter of time? No idea?
Click to expand...
Click to collapse
My knowledge on the topic is probably as limited as yours, but consider this: if someone figured out how to crack an iPhone, someone will undoubtedly figure out how to crack a signed bootloader.
The SE X10 bootloader was locked too and xda devs have unlocked it...though it took them a year to do it
Now knowing that hTC devices are way more popular here in xda, the unlocking process will take much less time, the incredible S are already temp rooted and it wouldn't take much time to be permanently rooted.
Now if you want to play on the safe side and love HTC then buy the DHD, it's still a stong device,rooted and plenty of roms
I like to believe my knowledge is limited as well.
From what I understand, a signed bootloader will require a leak of an internal engineering build to unlock. This was done on the HTC Thunderbolt for example.
An encrypted bootloader is tougher to unlock. This is why most of us won't buy a Motorola device.
By the way we still don't have any confirmation if it will be locked or not.
Htc said that their approach to security is "unchanged." If their approach is unchanged from devices like the Incredible S, which has an encrypted bootloader, the Sensation is unlikely to see custom firmware. If, however, their approach is unchanged from the Thunderbolt, then we are in luck: that phone has already been unlocked and rooted.
kgbkny said:
My knowledge on the topic is probably as limited as yours, but consider this: if someone figured out how to crack an iPhone, someone will undoubtedly figure out how to crack a signed bootloader.
Click to expand...
Click to collapse
Except that Apple products seem to be very crackable, sometimes even before the launch date.
Once again they are not signed they are locked meaning there is a possible way to crack them. Motorola signed theirs. HTC just locked them in a different way. Making harder for us to crack. Bootloader locked and bootloader are signed two different things.
Sent from my HTC Glacier using XDA Premium App
Perhaps but when you see the poor Incredible S users who tried everything possible to root it and couldn't...
vegetaleb said:
Perhaps but when you see the poor Incredible S users who tried everything possible to root it and couldn't...
Click to expand...
Click to collapse
The ps3 couldn't be hack someone did it its mostly about popularity. They said the same thing about the g2 and the thunder bolt it got hacked. Its not impossible.
Sent from my HTC Glacier using XDA Premium App
Not if, but when?
For me personally, the issue is not if the Sensation will be rooted, but WHEN. I'm personally thinking I might not want any new Android device before its rooted. I mean, although the Sensation has a lot to offer, unrooted it's going to be a resource hog that I won't be able to manage as I'd desire. I won't even be able to use Titanium Backup and some of my other apps till its rooted.
So I'm debating with myself about holding off on getting the Sensation till after it's rooted and an "unroot" path is also developed.
The only form of Android I've ever known is ROOTED, so going to a locked down version is not a pleasing option to me.
See this is what I love about Android and Opensource in general, and XDA in particular. You can go directly to the best and brightest and get answers! Thanks, everyone!
It shouldn't be a problem stock as bad as other phones gingerbread fixes alot of problems. The real fix is from ext4 but. It shouldn't be as bad as before though I hate sense the only thing I like is the camera apps ui and the fact that it doesn't lose data speeds.
Sent from my HTC Glacier using XDA Premium App
The main thing I like in Sensation is the Sense 3.0, but the low benchmark score is a clear indication that it needs root to speed up some things like kernel OC.
Rooting a phone is not sufficiant, you need a bunch of happy devs to build roms and kernels, look at the beautiful xperia Arc for exemple, it has same power as DHD and its rooted for 2 weeks, but due to lack of devs we still don't have recovery nor roms,it's like if you bought a ferrari but can't drive it because of lack of petrol
HTC devices are the most loved ones at XDA for the time being and they get tons of roms BUT things can change if HtC wanna lock all their new devices like the Incredible S, even Paul from Modaco is not willing to buy the Sensation if it will be locked like IS, the SGS2 will win the hearts of the devs here...
vegetaleb said:
The main thing I like in Sensation is the Sense 3.0, but the low benchmark score is a clear indication that it needs root to speed up some things like kernel OC.
Rooting a phone is not sufficiant, you need a bunch of happy devs to build roms and kernels, look at the beautiful xperia Arc for exemple, it has same power as DHD and its rooted for 2 weeks, but due to lack of devs we still don't have recovery nor roms,it's like if you bought a ferrari but can't drive it because of lack of petrol
HTC devices are the most loved ones at XDA for the time being and they get tons of roms BUT things can change if HtC wanna lock all their new devices like the Incredible S, even Paul from Modaco is not willing to buy the Sensation if it will be locked like IS, the SGS2 will win the hearts of the devs here...
Click to expand...
Click to collapse
Before there was ever Android, there was Windows Mobile and locked ROMs. And this very same site, XDA Developers was the place to come to unlock and get new ROMs.
So HTC locking down Android devices is old hat, as is unlocking them .
This site's history is rooted in HTC devices and so long as HTC makes something even marginally competitive I don't see it changing. The developers here have been hacking HTC devices before Android came to town. In fact, Android is the new kid on this block . Here, a lock is simply an exciting challenge to overcome, and a source for some developer to earn our $upport .
Don't count on a lock in the Sensation causing any wave of developers here to go running to Samsung.
Can you say the same to Incredible S users?
vegetaleb said:
Can you say the same to Incredible S users?
Click to expand...
Click to collapse
Inc S is Verizon right? We all know in the US VZW is the largest CDMA Carrier cell co. They usually get what they want. To me VZW is like Steve Jobs bunch of corporate jerks
Sent from my HTC Glacier using XDA Premium App
I recall the old Touch Pro 2 also took a little time to crack, but it was also unlocked. Even the old Treo Pro was eventually cracked, both the GSM and CDMA versions. They all get unlocked, some take a little more time than others.
Which is why my only question is when? The Sensation being a device that will be with GSM carriers, having a good degree of pre-sale marketing and being made by HTC. It's going to have development somewhere to the level we see with the HD2. Most of us HD2 owners that frequent this site moved to Android and the Sensation is the next suitable upgrade.
epsix said:
Inc S is Verizon right? We all know in the US VZW is the largest CDMA Carrier cell co. They usually get what they want. To me VZW is like Steve Jobs bunch of corporate jerks
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Incredible S is a GSM phone that is attracting attention since it has T-Mobile's AWS band support. Verizon is coming out with a dual-mode GSM/CDMA sister of the Inc S.
OK Guys, I am straight copying this from, fcreeves, the one he put up about the Virtuous ROM
I have had more MT4G's (not SLIDE - Glacier) for quite some time. I run nightlys on it and I REALLY miss the hell out of it. I like sense, it's nice and all but I REEEEALLY don't need it. I also really need the Power Options that CyanogenMod offers.
Here I am now with a MT4GS. NO Custom ROMs. I am sick of checking this Dev Section for a custom ROM(s) and decided to copy someone that had an idea about doing something about it.
CyanognMod Donate Page
You don't have to be logged in but if you are they give you some type of status on your name.
I have donated $40 to the CyanogenMod Team and requested that they make a version for MT4GS aka DoubleShot.
The team NEEDS a device to make substantial development possible. That is understandable.
I have donated 40$ USD, via paypal.
Transaction ID: 09J16268PM889413E
Note I put in Special Instructions:
This is for CyanogenMod 7 on the Doubleshot A.K.A. T-Mobile myTouch 4G Slide. Thank you for all you do.
I hope others will follow.
If you want the CyanogenMod 7 ROM on your MT4GS... PLEASE SPEAK UP AND DONATE! <---PLEDGE FOR NOW
Please only replay with ACTUAL TRANSACTION IDS! Show them you are VERY Serious.
#34124112jt9835317
$25.00
Though I'm not replying with transaction ID, I AM SERIOUS. I just got a MT4GS and was quite satisfied with the hardware, but being an old CM (CyanogenMod for Milestone, an official port with excellent quality thanks to its great developer nadlabak) user Sense can be disappointing in every sense (except the cute colorful icons of the Settings menu).
I have quite some Linux development experience, a little embedded system experience, and (hopefully) a friend who is doing Android driver development, so I'm looking forward to participating in porting CM to MT4GS. However, by any means NO GUARANTEE here; therefore I'm not asking nor accepting any donation (for now). I can start the development at most as early as the Chinese winter vacation begins (which is roughly Jan. 15th next year).
Additionally, some words on porting CM to MT4GS: MT4GS and MT4G share quite some hardware, so development should start as porting MT4G's CM to MT4GS. The major difference between the two models, namely the hi-resolution rear camera and the dual-core CPU would pose the main challenge. The keyboard should be trivial; but I really appreciate the design of Caps Lock and Alt Lock light and making it work may take some time.
We are not getting any cm7 support until HTC releases the source code needed to produce an aosp based rom (The Kernel) So you guys need to chill for a bit. We are stuck with sensed base roms until then.
Sent from my Supercharged MT4G Slide Running Undead's Stock Sense ROM using xda premium
I haven't got much experience in ROM development, so I'm quitely likely to wrong; if so, point me out.
Undeadk9 said:
We are not getting any cm7 support until HTC releases the source code needed to produce an aosp based rom (The Kernel) So you guys need to chill for a bit. We are stuck with sensed base roms until then.
Click to expand...
Click to collapse
Yes, we are not getting official CyanogenMod support because we can't build an AOSP kernel (yet). But after all, Android (and CyanogenMod) is mostly about the Dalvik VM, which is fortunately above the kernel. Thus a port is not necessarily an official one with an AOSP kernel.
The Motorola Milestone, for instance, has its bootloader locked, which leads to locked kernel, but the developer (nadlabak) was able to build a CyanogenMod port on top of the stock kernel - that is, the init scripts, a customized Dalvik VM, and all the system apk's. Modification of the kernel is still possible through dynamic loading of kernel modules (.ko files), which is quite tedious but nevertheless still possible. The Milestone port of CM is by any means CM except the kernel which is stripped from stock ROM and included as a binary blob along with everything else built from scratch (or from source, from AOSP, from CM).
The case with MT4GS is a little better and a little worse. It is a little better because MT4GS has an open bootloader and therefore we can use a customized kernel as soon as we can build one. (In the case of Milestone, the locked bootloader will only load kernels signed by Motorola.) It is a little worse because Milestone has a sister model with almost identical hardware (Motorola Droid) with official CM support; the closest model to MT4GS with official CM support is MT4G, which is still substantially different.
You are comparing apples to oranges my friend.
Sent from my myTouch_4G_Slide using xda premium
Undeadk9 said:
You are comparing apples to oranges my friend.
Click to expand...
Click to collapse
As I claimed, I'm likely to be wrong. But, care to explain a little bit? I'm not a native speaker and I don't quite get the simile.
Also, I'm curious about where I can find out whether HTC has released, for any certain model, the code necessary to build a kernel. Please share some links.
www.htcdev.com
Sent from my myTouch_4G_Slide using xda premium
xiaq said:
As I claimed, I'm likely to be wrong. But, care to explain a little bit? I'm not a native speaker and I don't quite get the simile.
Also, I'm curious about where I can find out whether HTC has released, for any certain model, the code necessary to build a kernel. Please share some links.
Click to expand...
Click to collapse
I thought the MT4GS was the twin of the htc sensation with slight differences.
Noooooo not really.
Sent from my myTouch_4G_Slide using xda premium
They are more like cousins then twins. Lol
Sent from my myTouch_4G_Slide using xda premium
Dont know if this is a dumb qustion but will android 4.0 be released for desire s?
This is what HTC had to say about the occasion:
"We are excited about the latest update for Android, Ice Cream Sandwich, and are currently reviewing its features and functionality to determine our upgrade plans. Our goal for Android updates is to give every customer an improved user experience, which means balancing each phone's unique hardware, HTC Sense experience and the Android kernel. While our goal is to upgrade as many of our recent devices as possible, we are committed to maintaining every phone's performance and usability first. Please stay tuned for more updates on specific device upgrade plans."
Maybe yes, maybe not!
I also want to know.....pls cm will let it come true
Sent from my HTC Desire S using XDA App
If not by HTC, then you most probably will find some ports or AOSP on Dev section.
If the only criterium they use is the technical capability of the phone (as they say they will) I would definitely say yes: the cpu can easily be overclocked to 1.2 gHz, and they recently published a phone (bliss) with identical characteristics as the desire s. I don't think that they are not going to provide an update for a device of about one month old.
On the other hand: many people will consider switching to a new device if they don't update it.
We'll just have to wait for an official statement, I'm afraid...
Looking forward to this coming out on our phones! Looks fantastic.
Call me cynical, but I can't see HTC releasing ICS on older devices where they perceive a possibility that the customer may buy a new device in order to upgrade.
The profit motive usually wins over all others!
Desire S isn't that old, it deserve to have ICS.
Sent from my HTC Desire S
ngek202 said:
Desire S isn't that old, it deserve to have ICS.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Yea,desire s is young
And anyway the sensation will have ics so we ll also have our ics
With a port.i think desire s ll have android 4,it s an hight-end devices.if htc know how to build a rom we ll have our ics.
Sent from my HTC Desire S using XDA Premium App
The challenge is that we do have physical buttons, when ICS it is part of UI. That has to be taken into consideration.
Have no idea, how that will reflect in real life. For example, I do preffer deactivating physical buttons on Desire S and using UI, since I love it on my Tab.
As with all custom ROM scene, if there is not an official release, then this community will take the best/popular parts of ICS and blend them into existing builds, or port from the Nexus S entirely. (I like the idea of native photo correction software and face recognition security, both of which I already have with 3rd party apps.)
The problem is that Sense is so deeply integrated into the vanilla Android experience that HTC will look at the cost of brining that to devices that have already been paid for. They'll make a decision on whether or not it's worth spending time (and money) on doing this, or trying to dangle a new carrot in front of you to buy.
They will be well aware that those of us on XDA who are after the bleeding edge, are also able to put custom/ported ROMs on for free. This also relieves them of warranty responsibilities, and makes them less inclined to spend money developing an official update for our "older" handsets.
My view is that if we see ICS on our Desire S, it'll be an AOSP port from the Nexus S with maybe an official Sense release way down the line. Before then I'm sure someone will do an ICS-style launcher.
Just my thoughts.
Our device is not old.our desire is 400€ yet
And it s the top of the single core devices
I don t think an old device is 400€
Htc have to built an ics for us because this phone went out in april 2011 and i bought it for a lot of money xd
Sent from my HTC Desire S using XDA Premium App
kylon said:
Our device is not old.our desire is 400€ yet
And it s the top of the single core devices
I don t think an old device is 400€
Htc have to built an ics for us because this phone went out in april 2011 and i bought it for a lot of money xd
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
+1 for you man!!!
All,
looking for insight regarding currently available ROM's that would offer the closest thing to CM9 (from what I’ve read CM9 is only available on Tegra3 handsets)? Looking for a 'stock android experience' or AOSP based build... your suggestions are much appreciated.
currently unlocked, running 1.85FW, with CWT recovery...
many thanx,
The closest thing available right now would probably be CleanROM Dev edition 2.0. Check it out in the development section.
CleanROM DE 2 is what I'm running and it's great. It's pretty clean.
Thanks for the input, been running CleanRom v2.2 since yesterday afternoon, and I must say not very impressive at all... guess I’ll just need to keep waiting for that true android experience I crave so badly.
The change log listed for CleanRom v2.2. does not give any indication that carrierIQ has been removed (which is another huge disappointment for this ROM)
any idea how long we're looking at for a decent AOSP ROM to be released? month? two months?
100%digital said:
Thanks for the input, been running CleanRom v2.2 since yesterday afternoon, and I must say not very impressive at all... guess I’ll just need to keep waiting for that true android experience I crave so badly.
The change log listed for CleanRom v2.2. does not give any indication that carrierIQ has been removed (which is another huge disappointment for this ROM)
any idea how long we're looking at for a decent AOSP ROM to be released? month? two months?
Click to expand...
Click to collapse
Clean ROM DE is different from what you are running. Check the dev section. As for an AOSP ROM...who knows. There are a lot of factors involved.
Rabble rabble rabble.
If I understand correctly, you'll have to wait until we get S-Off so we can flash boot.img. Once that's achieved, it will be possible to flash full ROM's. But there are still a lot of things that need to be figured out, like getting the camera working, Wifi, GPS, data, etc.
Maybe the Cyanogenmod developers will get lucky and it'll work out of the box.
jmattp said:
Maybe the Cyanogenmod developers will get lucky and it'll work out of the box.
Click to expand...
Click to collapse
You know that never happens =)
jmattp said:
If I understand correctly, you'll have to wait until we get S-Off so we can flash boot.img. Once that's achieved, it will be possible to flash full ROM's. But there are still a lot of things that need to be figured out, like getting the camera working, Wifi, GPS, data, etc.
Maybe the Cyanogenmod developers will get lucky and it'll work out of the box.
Click to expand...
Click to collapse
That's not correct. We can flash boot images just fine through fastboot now. Just need s-off to flash kernels through recovery. Once HTC releases the source for our phone more ROMs will follow, including AOSP ROMs I'm sure. Source is needed to help create custom kernels.
I've never understood that rationale, buy an HTC phone that you know will be packed with sense etc then go back in time to bare bones android. Why not save your money and buy something like a Samsung, Motorola, LG, etc. With a barebones android os? Lol my rant
Sent from my HTC One X using xda premium
eraste said:
I've never understood that rationale, buy an HTC phone that you know will be packed with sense etc then go back in time to bare bones android. Why not save your money and buy something like a Samsung, Motorola, LG, etc. With a barebones android os? Lol my rant
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Because the only device running stock Android 4.0 is the Galaxy Nexus. I've gone through several of them and they all had the same purple tint, weird crosshatch pattern visible on white images, distortion/noise at low brightness, and other issues related to the Pentile SAMOLED display. Besides that, I can't think of any other device that runs stock Android.
I especially can't think of any Android phones that look as nice as the One X. I like its unibody construction, machined earpiece grill, soft-touch case (the black one anyway, not sure if the white is glossy), the way the glass is slightly above the case like old iPod Nano, and the display itself is really good.
Before Ice Cream Sandiwch, we had maybe the Motorola Droid, the Nexus One, and then the Nexus S. I hate physical keyboards, the Droid was out. Currently, there aren't many choices if you want a vanilla Android device. Actually... there's only one, and the display is a disappointment to me.
In my opinion, the best Android phone available right now is the One X. Knowing that developers are always making custom ROM's for the majority of Android devices, I know that I don't need to let the software dictate my purchasing decision.
eraste said:
I've never understood that rationale, buy an HTC phone that you know will be packed with sense etc then go back in time to bare bones android. Why not save your money and buy something like a Samsung, Motorola, LG, etc. With a barebones android os? Lol my rant
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You realize those manufacturers slap their own crap on top of stock android too, right? Samsung - TouchWiz, Moto - Blur, LG - Whatever the heck they do. Unless you're buying a Nexus device then you're getting a manufacturer skin.
Personally, I buy for the hardware. Though, the stock software has to be tolerable enough to last me until custom roms start coming out.
pside15 said:
That's not correct. We can flash boot images just fine through fastboot now. Just need s-off to flash kernels through recovery. Once HTC releases the source for our phone more ROMs will follow, including AOSP ROMs I'm sure. Source is needed to help create custom kernels.
Click to expand...
Click to collapse
so without nand access the One X isn't going to see any AOSP builds? I’m not sure I entirely understand how nand is that important... I mean if you can boot a your own ROM, who cares.
Does HTC typically release the source for their phones as ‘pside15’ indicated that is an important factor in creating ROMs?
Seems like the Cyanogenmod team already has AOSP build for the Tegra handset. HTC One X (with Tegra) source isn’t released…
pside15 said:
That's not correct. We can flash boot images just fine through fastboot now. Just need s-off to flash kernels through recovery. Once HTC releases the source for our phone more ROMs will follow, including AOSP ROMs I'm sure. Source is needed to help create custom kernels.
Click to expand...
Click to collapse
Thanks for the correction.
100%digital said:
Thanks for the input, been running CleanRom v2.2 since yesterday afternoon, and I must say not very impressive at all... guess I’ll just need to keep waiting for that true android experience I crave so badly.
The change log listed for CleanRom v2.2. does not give any indication that carrierIQ has been removed (which is another huge disappointment for this ROM)
any idea how long we're looking at for a decent AOSP ROM to be released? month? two months?
Click to expand...
Click to collapse
qft.
I LOVE the htc one x for the hardware and its physical appeal, but i also cant wait for some stock android ROMs. The aroma one thats out gets pretty darn close, but its no CM9. Im hoping that in the next two weeks with our new freedom with the unlocked bootloader etc etc.. that we will get more than 2 roms... thats ALL I see currently in the dev section. I shouldnt complain though because obviously I'm no dev.
I feel like the AT&T version was a waste of my money though :/ it just doesnt have enough attention. The only reason I have it instead of the tegra 3 is because of the battery and lte. Otherwise there is literally no other reason I should keep this phone. Does anyone know if the battery life has been improved at all for the international version?
dufort said:
qft.
I LOVE the htc one x for the hardware and its physical appeal, but i also cant wait for some stock android ROMs. The aroma one thats out gets pretty darn close, but its no CM9. Im hoping that in the next two weeks with our new freedom with the unlocked bootloader etc etc.. that we will get more than 2 roms... thats ALL I see currently in the dev section. I shouldnt complain though because obviously I'm no dev.
I feel like the AT&T version was a waste of my money though :/ it just doesnt have enough attention. The only reason I have it instead of the tegra 3 is because of the battery and lte. Otherwise there is literally no other reason I should keep this phone. Does anyone know if the battery life has been improved at all for the international version?
Click to expand...
Click to collapse
I'm working on one myself....but because I do not want to release trash and because I have been limited on time over the last week or two...I have not released yet. Sit tight and chill out. Phone hasnt even been out for a month yet...
Sent from my HTC One X using XDA
Good to see you h8 I liked your stuff on the infuse you taught me a lot
Sent from my HTC One X using xda premium
h8rift said:
I'm working on one myself....but because I do not want to release trash and because I have been limited on time over the last week or two...I have not released yet. Sit tight and chill out. Phone hasnt even been out for a month yet...
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Oh I'm sitting tight, stoked to see what the future is with this device. Just had to vent a bit :banghead:
Sent from my HTC One X using xda premium
100%digital said:
so without nand access the One X isn't going to see any AOSP builds? I’m not sure I entirely understand how nand is that important... I mean if you can boot a your own ROM, who cares.
Does HTC typically release the source for their phones as ‘pside15’ indicated that is an important factor in creating ROMs?
Seems like the Cyanogenmod team already has AOSP build for the Tegra handset. HTC One X (with Tegra) source isn’t released…
Click to expand...
Click to collapse
Source has been released for one x tegra...
Sent from my HTC One X using XDA
There are only so many ways you can debloat the stock roms lol.
Things will pick up once the source is released and devs can start going crazy.
+1
jmattp said:
Because the only device running stock Android 4.0 is the Galaxy Nexus. I've gone through several of them and they all had the same purple tint, weird crosshatch pattern visible on white images, distortion/noise at low brightness, and other issues related to the Pentile SAMOLED display. Besides that, I can't think of any other device that runs stock Android.
I especially can't think of any Android phones that look as nice as the One X. I like its unibody construction, machined earpiece grill, soft-touch case (the black one anyway, not sure if the white is glossy), the way the glass is slightly above the case like old iPod Nano, and the display itself is really good.
Before Ice Cream Sandiwch, we had maybe the Motorola Droid, the Nexus One, and then the Nexus S. I hate physical keyboards, the Droid was out. Currently, there aren't many choices if you want a vanilla Android device. Actually... there's only one, and the display is a disappointment to me.
In my opinion, the best Android phone available right now is the One X. Knowing that developers are always making custom ROM's for the majority of Android devices, I know that I don't need to let the software dictate my purchasing decision.
Click to expand...
Click to collapse
Exactly!
First off, yes I know this is not the HTC One S forums. Let me explain my reasoning for posting this here
The HTC One S is part of our family of devices (which includes this device, the One S, Evo 4G LTE, and Incredible 4G LTE). Although it doesnt matter much in terms of Sense development, for AOSP development, this family of devices is the family that we share many files with, including kernel source releases and other files which make up the ROM such as proprietary files.
For AOSP devices, these files are essential in keeping our device up to date and running on the latest Android version. These files from Sense such as proprietary files are essential in this. Generally speaking, the latest version of these files is used in AOSP ROMs.
If the One S is kept alive, it will offer another device that we can grab these files from, if HTC decides to kill off our device and keep theirs, or visa versa. If they release 4.2.2 Sense for the One S first, then we can use those files from their release in ours. So if their device is kept alive, ours can be greatly affected by it as well.
tl;dr Their situation affects our device too, so sign this petition to help show HTC that the community wants the device to be supported.
Here is the petition: http://www.change.org/petitions/htc-give-the-one-s-continued-support-like-the-one-x
P.S. to anyone who thinks that these petitions do nothing, I will point to the Desire HD (I believe? one of the desires) that had so much community support that HTC ended up releasing a firmware update for it through RUU to ICS specifically for developers and modders. HTC is listening.
Signed.
Sent from my HTC One X using xda app-developers app
Signed.
Sent from my Evita
Yuuuuuuup
rohan32 said:
First off, yes I know this is not the HTC One S forums. Let me explain my reasoning for posting this here
The HTC One S is part of our family of devices (which includes this device, the One S, Evo 4G LTE, and Incredible 4G LTE). Although it doesnt matter much in terms of Sense development, for AOSP development, this family of devices is the family that we share many files with, including kernel source releases and other files which make up the ROM such as proprietary files.
For AOSP devices, these files are essential in keeping our device up to date and running on the latest Android version. These files from Sense such as proprietary files are essential in this. Generally speaking, the latest version of these files is used in AOSP ROMs.
If the One S is kept alive, it will offer another device that we can grab these files from, if HTC decides to kill off our device and keep theirs, or visa versa. If they release 4.2.2 Sense for the One S first, then we can use those files from their release in ours. So if their device is kept alive, ours can be greatly affected by it as well.
tl;dr Their situation affects our device too, so sign this petition to help show HTC that the community wants the device to be supported.
Here is the petition: http://www.change.org/petitions/htc-give-the-one-s-continued-support-like-the-one-x
P.S. to anyone who thinks that these petitions do nothing, I will point to the Desire HD (I believe? one of the desires) that had so much community support that HTC ended up releasing a firmware update for it through RUU to ICS specifically for developers and modders. HTC is listening.
Click to expand...
Click to collapse
Thank you for spreading the word.
rohan32 said:
P.S. to anyone who thinks that these petitions do nothing, I will point to the Desire HD (I believe? one of the desires) that had so much community support that HTC ended up releasing a firmware update for it through RUU to ICS specifically for developers and modders. HTC is listening.
Click to expand...
Click to collapse
The petition does work, I was the one that did the DHD one
Sent from my HTC One X using Tapatalk 4 Beta
Signed.
Sent from my GT-N8013 using Tapatalk HD
I see the trolls post is gone. I guess that little report button works well.
Sent from my One X using xda app-developers app
Signed!
SIGNED
Signed
Sent from my now S-Off HTC OneXL
signed...
the sensation didn't get jellybean, but the galaxy s2 did.
however, the successor to the sensation (one s) not getting jellybean is beyond ridiculous.
((EDIT: ignore mistake, explained in next post))
I had a HTC Aria, HTC Inspire and an One X. The lack of support is a known issue with HTC. People will buy them no matter what. I think I'm done with them though. The build quality is phenomenal and on par with Moto I think (who also sucks at continuing updates). I am probably getting the Note 3 because Samsung is exceptional at continuing updates to their phones. And the 3gbs of ram is another huge factor
I don't hate HTC but I don't want to rely solely on XDA for my updates.
Sent from my HTC One X using xda app-developers app
raz0rf1sh said:
signed...
the sensation didn't get jellybean, but the galaxy s2 did.
however, the successor to the sensation (one s) not getting jellybean is beyond ridiculous.
Click to expand...
Click to collapse
The One S has Jelly Bean, just not the latest version. In fact, 4.1 was released last July. My girlfriend and I didn't get it from Vodafone until December 25, and I've read that T-Mobile US users didn't get it until recently! That's dreadful, especially for a relatively new device like this.
I hope if the device is continued to be updated that the updates come a little quicker!
DylRicho said:
The One S has Jelly Bean, just not the latest version.
Click to expand...
Click to collapse
oops, my bad, by updates, I also meant getting a UI update...
and even though the sensation did somewhat badly, at least it got a major update (2.3.4 to 4.0.3), and a newer version of sense (although not the lastest version available which was stupid!!)
raz0rf1sh said:
oops, my bad, by updates, I also meant getting a UI update...
and even though the sensation did somewhat badly, at least it got a major update (2.3.4 to 4.0.3), and a newer version of sense (although not the lastest version available which was stupid!!)
Click to expand...
Click to collapse
You can blame HTC's 18-month update policy for that. Also something that they don't stick to, and now they're bringing out crappy devices like the Desire 200 to hopefully make up the revenue loss.
When will HTC realize that releasing 20 phones per year is a bad concept? Update the phones you've already released, dammit!
Signed! I didn't realize how much the One S meant to One X development. I hope it works!
Sent from my One X using xda app-developers app
[I accidentally "thanked" a post about leaving HTC for Samsung. Oops]
Signed. This is a fantastic device with a fantastic community, really. I learned so much about android from the Evita. I hope we get enough signatures to save the One S.
Sent from my HTC One X using xda premium
Thank you for your support.
Signed with a good reason! :good: