our desire x runs with more than 512mb of ram and samsung galaxy s3 has the same android version so will we get it or not?
I don't think so. The update to KitKat would need HTC developers upgrading our kernel along with their proprietary drivers, so we would have to do that on our own...
I imagine lots of these threads being started and closed as they were for Jellybean & Sense5, So i'll try to sum it up... If we get it officially (Highly unlikely) then we'll be waiting quite a while and then alot longer for kernel sources, A custom rom will most likely be in the Works Once a simialar device (e.g. OneS) gets an update or Rom. And we will most Likely Get a CM Port aswell which will also take a while to be fully working.
So don't expect it anytime soon, and before anyone says "But the One/Max/S4/S3/etc Already has it" Just to Remind some new users The DesireX is not a flagship Device and is therefor Probably not on the first halve of HTC's priority Support/Update list.
And Just heads up, Mods will probably start Locking these threads and dealing out warnings to people constantly making these threads, Spamming, or Trolling/Flaming
Well it will have a better support for lower-medium end devices,so it might be easier to compile it for our device,then previous versions. But i strongly doubt that there will be an official official release.
Thank you :victory:
Yes! we will get kit Kat! XD
Edit:
HTC wrote: "Hi, Christopher. Our priority will be updating the HTC One family. At this point, we're still working to determine whether we’ll be updating other devices in our product portfolio. Continue to follow us here and we'll keep you posted on upgrade info. Thanks for your patience."
Sent from my HTC Desire X Android KitKat 4.4
As it's fairly unlikely, at least for now, that this device will get the 4.4 update there's no point in keeping this open.
If it's confirmed to get KitKat eventually then I'll get this reopened for discussion.
Until then, thread closed!
Related
Would I be correct in assuming (at least until recently with the Nexus One and ICS), that every Android phone can run the latest version of the software, and the fragmentation of the platform that people generally refer to are the skins that developers layer over stock that aren't getting the updates? Thanks ahead of time for the answer.
Not every single Android device will be able to run it, but many will. Even devices which won't get it officially will still get it ported/developed unofficially.
I guess, what I was meaning to ask is, when ICS is released, what is stopping every phone except for the Nexus One from running it, since that is the only phone that Google specifically said wouldn't be able to run it? Note, I'm not talking about HTC Sense etc., but but just basic Android underneath it. Is Android more unified than competitors would have others believe?
Ratlegion said:
I guess, what I was meaning to ask is, when ICS is released, what is stopping every phone except for the Nexus One from running it, since that is the only phone that Google specifically said wouldn't be able to run it? Note, I'm not talking about HTC Sense etc., but but just basic Android underneath it. Is Android more unified than competitors would have others believe?
Click to expand...
Click to collapse
Actually, the Nexus One can run it. See here: http://www.youtube.com/watch?v=dyPeT-ZUbBw . A device may not be found fit to run ICS (based on hardware specs), which will cause them not to get the update officially. The hardware requirements may be the main thing stopping some devices from getting the update, since weak hardware with little power will not allow the system to run as it should. On the other hand, this does not stop developers from porting/making unofficial roms to devices which are claimed unable to run it or just not getting the update officially.
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...
Ok, please don't blast me, and I am not starting this thread to start a fight. I just really want some advice. I love the rezound, and I would like to get it over the Gnex as I don't like a lot of things about the Nex. However, I had the TB, and now the Bionic and I just don't want to be waiting on a never ending cycle to get to the lastest software(IE 4.0, 5.0 etc.) The reason I say this, is I know like with the TB it seems like the Devs have to build a whole new RIL in order to get the software to work with the hardware(at least in the GB and now the ICS update for the TB) and I don't want to have to wait for the same thing when JB comes out at the end of the year, but I also don't want to upgrade again in 6-9 months. I hope I have made my dilemma clear. I would like to know if you, as rezound owners, think this may happen, as I may just jump (regretfully) to the Gnex.
Also, Let me make this clear, I am in NO WAY degrading the Devs work here or else where, I am just impatient. And don't want to wait for many months for fully working roms that may or may not come. But there are a few main things I REALLY like on ICS, but the current build are just so buggy on my current devices that it's not worth using as a DD. Please don't think this is me fussing, or anything of the sort, it's just I'm looking for advice. Thanks.
The current ICS builds are pretty good. The devs did a great job with them.
As to your question about JB, only time will tell. I don't think that anyone has an answer to that.
I've had both BAMF's and Scott's ROMs on my Rezound, they are both very stable. The only thing HTC has said about the update regarding the Rezound is that it'll come later this year. It is not listed in the first batch of phones.
"According to HTC, we can expect to see the updates begin to roll out by the end of March for the original Sensation, Sensation 4G, Sensation XE, followed shortly there after by the Sensation XL. The following batch of devices will include the Rezound and Incredible S, but there is no time frame listed for that device other than, “later this year."
-Quoted from droid-life.com
I don't mean as much for ics as it appears to be currently working well on the device. I'm not shy about flashing. I'm just worried that the next version jelly bean may miss the device and it will be left to the devs to get it up and running. But that's been even harder on them recently, Atleast with my experience with the tbolt, as they have to built the Ril from the ground up, or so I understand. So I don't want to be stuck on current software. I'm not saying it will happen, I just want advice on whether I should take the chance with the rezound. I do really like the device.
It was my understanding that Jelly Bean was more like a Honeycomb release...
The operating system's next version jelly bean will be optimized for tablets
Click to expand...
Click to collapse
Oh, I hadn't seen that. Thanks for the heads up.
Is this ever going to happen? CM7 had easily the longest run time on my DINC. Just curious if we're going to get it or not!
It doesnt officially name any devices but they put together a little chart to help figure out if you will get an official cm9 release. Check it out. http://androidspin.com/2012/03/14/will-your-device-get-cm9-the-cyanogenmod-team-has-that-answer-for-you/
Honestly, I don't think it's going to happen. Based on the No answer to Does it currently have an official CM7 Release?, the next question is answered No as well.
Most people I've talked to about this seem to skip that and go to the question Is the manufacturer releasing ICS?
Based on the chart linked above (which is official and I saw it on their Google+), I don't think we have a high chance. I'll most likely be returning mine today unless my wife wants it when the SGS3 comes out.
The first rule about CyanogenMod ETAs...You don't ask for CyanogenMod ETAs.
Nobody asked for an ETA. Asked if we'd be getting an official release, whether it's now or next year.
No reason to troll someone just for asking a question.
There's an ongoing thread for it in the Dev section as to where it stands, probably some good info in there...
The only way it will ever get official support is one of two ways:
1) A current CM developer gets a Rezound and ports it, or
2) One of you guys ports it yourself and becomes an official maintainer of it, keeping the project active by continuing to merge in all the official CM9 changes as they occur.
There are still a lot of technical issues preventing AOSP builds from functioning fully on the Rezound. Once those are sorted out, eventually somebody will build a CM9 port. Whether or not it becomes officially supported by CyanogenMod as an official release is entirely up to the developers who ported it and whether or not they want to work with the CM team to make it official.
As soon as we get ics kernel source its very likely that a dev will attempt to port cm9.
Sent from my ADR6425LVW using xda premium
Hello All,
As you all know I've been part of Xda and assiting in a positive resolution from HTC in requests from Bootloaders to source codes. Well seeing we have a great device that seemed to be given EOL to early in its game.. in my opinion due to lack of marketing skills. Well I will be posting in HTC FB to get our voice out to them for the Source Code release for our device.
Please comment "Like" and comment to request this so we can continue development for the Flyer.
https://www.facebook.com/photo.php?fbid=10151213297764443&set=o.165420456859572&type=1&ref=nf
And Here:
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Um, source code of what? They release sources of Honeycomb, and there are no sources of ICS or Jelly Bean, so what's the whole point?
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
There is the kernel which is low level device specific, the kernel is mostly based on open source linux code, htc adds some board and device specific configuration on top of that.
Then there is the aosp which is also open source, an operating system provided by google that makes up most part of any ROM.
Then you have your aosp derivative like CM or AOKP, which provides board specific fixes and some customization. HTC's ROM is also based on aosp, but they add their own sense look and feel to it.
And finally and most importantly you have your close source proprietary drivers provided by chip manufactures like Qualcomm and TI. They control cameras, wifi, BT...etc. So in reality there is very little HTC could do as they don't have the rights to release these code. And that's is where most ppl run into issues.
So to create a ROM is not hard at all, anybody can download the source code and compile it to generate a ROM as most of the source code are all open source. What will be helpful is if Qualcomm releases the source code for their drivers, which I doubt they will ever do, otherwise they wouldn't be close source in the first place. The only thing we could do is try to reverse engineer the device base on logs and understanding of how each component should work and make educated guesses.
Due to HTC lack of effort on this device (No ICS - HC was slow joke) I will never buy another HTC product again, same goes for sony, though they did eventually update xperia x10i it was only due to huge pressure not because they wanted to.
I want to buy an electronic product that potentially remains relevant at least a year later otherwise forget it.
so i sent this letter to HTC
after reading this page where HTC discusses 4.1 upgrades i decided to drop them a line "
DIRECTLY FROM YOUR WEBSITE:
When will additional devices receive Android 4.1?
In addition to the HTC One X and HTC One S, we are actively reviewing our product portfolio to identify candidates to receive Jelly Bean. Our goal is to prioritize review for devices launched in 2012 with our numerous carrier partners across multiple regions and then consider our ability to provide updates to products from 2011.
What devices will not get Android 4.1?
We work hard to ensure each of our products has the optimal user experience and therefore some products will remain at their current version of Android. In general, devices with 512MB RAM or less will not be upgraded to Android 4.1. At present, these devices include the HTC One V and the HTC Desire C. As we identify other devices that will not be upgraded, we'll provide updated information.
What about a development version of Android 4.1?
For our developer community, we plan to make generic development ROMs of Jelly Bean available for both the HTC One X and HTC One S. As soon as the ROMs are ready, they will be posted to our HTCdev site (www.htcdev.com). We strongly recommend customers take the time to understand the limitations of the development software along with the terms and conditions on the site before downloading to their device.
REALLY!? have you listened to what your customers have asked/said about the HTC flyer at all?! where is OUR 4.1 DEVELOPMENT ROM! wtf! where are you for us!? I can tell you where... you are giving us 3.2 HC that takes away two very important features i bought the device for #1 GPS! completely broken by your newest update to HC. #2. Hardware Keys.... WHY?! i understand that HC introduced soft keys. so you say you "We work hard to ensure each of our products has the optimal user experience" BULL! you clearly weren't thinking about the end user when you pushed out that HC update for the flyer. Would have been smarter for you to leave us on working GB and go straight to ICS or JB when it was ready! this is lunacy! who ever is making decisions in your company needs fired. you are bleeding money from everywhere. why don't you bring it back to the old school HTC that CARED! ABOUT! IT'S CUSTOMERS! listen to what we are saying! hear our voice! we have signed petitions. we have pleaded on multiple forums. WE have poured over your FB and twitter pages asking for you to throw us a freaking bone here.... when is it gonna happen? ever?!
I still have my flyer and i love it dearly. but without updates it's falling behind the pack. I recently bought a 10.1 galaxy note. while i'm happy with it's speed and what not. it's not the form factor i want. which is what the flyer is for me. perfect. PLEASE DON'T GIVE UP ON US OR THIS DEVICE! PLEASE RELEASE A DEVELOPER ROM FOR OUR FLYER! "
this was their reply (you will want to read it for sure)
Dear Matt,
Thanks for contacting HTC!
We completely understand your concern and I thank you for your patience and am deeply sorry if this issue has caused you any dissatisfaction with HTC or its phones. I hope that it will not detract from your overall perspective of the device or the company. You are the most important part of the HTC Family.
We listen to our community and feedbacks like yours are the ones that make us revise our decisions, and try to find the correct balance between the device’s performance and usability. We cannot announce or say anything about the Flyer right now but what I can tell you is that we are, indeed, paying attention to the community´s feedback and opinions.
Should you require further assistance, please do not hesitate to contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a great day!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Carlos
HTC
I appreciate the passion here, but HTC left this device for dead along with the Jetstream and View shortly after releasing it. We received what would amounted to a Beta of Honeycomb then they closed up shop. You live and learn, and although I still use my Flyer and enjoy it I will not buy another HTC device
I completely agree with you .. HTC should give us ICS or JB for our Flyer as a good faith. We must keep GB because honeycomb is a joke..
I use my Flyer and i try as much as possible with the optimized news on GB .. and share with you.
Hoping for a good action on their part for JB!!
Fatal1ty_18_RUS said:
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
Click to expand...
Click to collapse
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
gersto said:
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
Click to expand...
Click to collapse
that the honeycomb kernel .
doesn't do you much good for ICS or JB
yncconsulting said:
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
.
.
.
Click to expand...
Click to collapse
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
DigitalMD said:
that the honeycomb kernel .
doesn't do you much good for ICS or JB
Click to expand...
Click to collapse
well they must be of some good since we have ICS/JB ROMs out there that are "mostly" complete, slick and usable, although slightly buggy, so obviously yeah i get that it doesn't solve all the issues we have, since some drivers are missing: as evident by the non-working FC, no hardware decoding for video, and semi-working BT
DigitalMD said:
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
Click to expand...
Click to collapse
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
DigitalMD said:
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
Click to expand...
Click to collapse
Thanks for clarification. So I was not wrong about the drivers, which are the device and vendor specific components. In other words if you can get the vendor to release their sources or make their chip/board manufacturers to release their sources is the only way to go. Seems a bit unrealistic though but who knows...
Sent from my GT-I9100G using xda app-developers app
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
freworld said:
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
Click to expand...
Click to collapse
+1