guys...check this topic...
HTML:
http://forum.xda-developers.com/showthread.php?t=701194
if this really happens...will it be possible to port it to Hero??
is ported but is beta now...it will be a while until will see it on hero with the final form
http://forum.xda-developers.com/showthread.php?t=688523&highlight=froyo =>i've tested this and wifi,bth and some things doesn work because is a beta
VillainRom (plus others?) are developing a froyo release right now, and from what I have been told its not far from a version 1 release.
Only one thing left to fix apparently.
Lennyuk said:
VillainRom (plus others?) are developing a froyo release right now, and from what I have been told its not far from a version 1 release.
Only one thing left to fix apparently.
Click to expand...
Click to collapse
Yep, I think the VillainTeam are trying to get the mic working, then I believe it should be ready..!
ooh, thats really good to hear! Knowing our luck if HTC ever decide to give the Hero 2.2 it will probably be sometime in 2012
Well word has it that Google will be putting an end to phone manufacturers skinning Android when they release Gingerbread (3.0), as they plan on improving the interface. If so, that means no more Sense. It also means updating to newer versions of Android will be much quicker (as HTC don't have to make all the changes to Sense etc.) So if the Hero has the technical ability to take Android 3.0, we will most likely go from 2.1 to 3.0, and miss out 2.2.
Gingerbread is scheduled to be released Q4 of 2010. Either way, I'm due an upgrade in October/November anyway, so hopefully I'll get a new device sporting Gingerbread from release!
sonnysoul said:
Well word has it that Google will be putting an end to phone manufacturers skinning Android when they release Gingerbread (3.0), as they plan on improving the interface. If so, that means no more Sense. It also means updating to newer versions of Android will be much quicker (as HTC don't have to make all the changes to Sense etc.) So if the Hero has the technical ability to take Android 3.0, we will most likely go from 2.1 to 3.0, and miss out 2.2.
Gingerbread is scheduled to be released Q4 of 2010. Either way, I'm due an upgrade in October/November anyway, so hopefully I'll get a new device sporting Gingerbread from release!
Click to expand...
Click to collapse
Meh. HTC will still need to add drivers etc. and that will give them a good excuse to take forever
sonnysoul said:
Well word has it that Google will be putting an end to phone manufacturers skinning Android when they release Gingerbread (3.0), as they plan on improving the interface. If so, that means no more Sense. It also means updating to newer versions of Android will be much quicker (as HTC don't have to make all the changes to Sense etc.) So if the Hero has the technical ability to take Android 3.0, we will most likely go from 2.1 to 3.0, and miss out 2.2.
Gingerbread is scheduled to be released Q4 of 2010. Either way, I'm due an upgrade in October/November anyway, so hopefully I'll get a new device sporting Gingerbretad from release!
Click to expand...
Click to collapse
sence isnt a skin, if anything its a modification to android, also google stopping manufacturers doing anything would defeat the object of android being open source lol
pretty cool to hear some peeps are already working on porting Froyo to our beloved Hero
keeping my fingers crossed...
AndroHero said:
sence isnt a skin, if anything its a modification to android, also google stopping manufacturers doing anything would defeat the object of android being open source lol
Click to expand...
Click to collapse
Well, it's a UI overlay, which to me is the same as a skin! Lol! Either way, I can;t wait to see how it turns out.
Related
Is it for the hero
-------------------------------------
Sent via the XDA Tapatalk App
As far as I'm aware Froyo 2.2 has only been officially released for Google's own phone (the Nexus One). However they should be releasing the source code for Froyo soon.
The HTC Hero current runs on Android 1.6 although HTC may release an update (most likely for 2.1) in the near future. Unofficially ROM developers may release Froyo as soon as they can create a stable version for the Hero.
So in answer to your question in short - no.
Sherry123 said:
As far as I'm aware Froyo 2.2 has only been officially released for Google's own phone (the Nexus One). However they should be releasing the source code for Froyo soon.
The HTC Hero current runs on Android 1.6 although HTC may release an update (most likely for 2.1) in the near future. Unofficially ROM developers may release Froyo as soon as they can create a stable version for the Hero.
So in answer to your question in short - no.
Click to expand...
Click to collapse
Umm, I just got my hero and it is running 2.1! I'm not sure, but maybe you missed the official release?
http://support.sprint.com/support/a...n_your_HTC_Hero/case-gb746811-20091009-155624
For sprint...what i'm not, but just goto your carrier website and device support for download if you don't have it. Keep in mind latest update will not allow root - you can root by re-flashing back to an earlier build without any problems.
As for 2.2 - official release from sprint for hero will take awhile. We will most likely see a fully functional port before then. There is already a port of 2.2 available in the forums - but a lot is missing such as speaker, mic, and gps!
ebbinger_413 said:
Umm, I just got my hero and it is running 2.1! I'm not sure, but maybe you missed the official release?
http://support.sprint.com/support/a...n_your_HTC_Hero/case-gb746811-20091009-155624
For sprint...what i'm not, but just goto your carrier website and device support for download if you don't have it. Keep in mind latest update will not allow root - you can root by re-flashing back to an earlier build without any problems.
As for 2.2 - official release from sprint for hero will take awhile. We will most likely see a fully functional port before then. There is already a port of 2.2 available in the forums - but a lot is missing such as speaker, mic, and gps!
Click to expand...
Click to collapse
Once HTC gets Sense UI figured out for 2.2, I'm sure it won't be long before ROMs are ported over. I highly doubt the Hero will get an official release, but HTC is not stupid. They'll know that people will expect Sense UI on their new devices, and they know that new devices will start to ship with Froyo.
HTC Artemis with Android 2.2 (Froyo) is possible?
braulio_holtz said:
HTC Artemis with Android 2.2 (Froyo) is possible?
Click to expand...
Click to collapse
No offense, but keep dreaming. They're having a painful enough of a time getting 1.6 on the HD2, your handset is far too old
HTC Vogue work Android 2.2
HTC Artemis (HTC P3301) work with Android 1.5, no wifi, no sound
braulio_holtz said:
HTC Vogue work Android 2.2
HTC Artemis (HTC P3301) work with Android 1.5, no wifi, no sound
Click to expand...
Click to collapse
And you expect an Android build of 1.5 which still won't work with wifi or sound to suddenly have everything working with 2.2?
Sorry, it's not going to happen, the Artemis is simply too old and doesn't have a large enough userbase.
I'll have to buy a new smartphone
by Google Translator
braulio_holtz said:
I'll have to buy a new smartphone
by Google Translator
Click to expand...
Click to collapse
Indeed, you will have to buy a new smartphone. This is the nature of technology. Even the EVO will be obsolete within a few years time.
is, I'm just putting together a money to buy a good model
by Google Translator
LiquidSolstice said:
Indeed, you will have to buy a new smartphone. This is the nature of technology. Even the EVO will be obsolete within a few years time.
Click to expand...
Click to collapse
Years? More like months, consumer tech moves on so quickly the evo will be old hat in 6 months time.
Still a few minor bugs with the Eris Froyo ROM, but it is sweet!
Sent from my FroyoEris using XDA App
Please, forgive my ignorance here, but I'm new to Android after coming from WM, and I have some gaps in understanding that I'm hoping maybe you guys could help to fill in.
Given the so-called "open" nature of Android, I'm a bit puzzled why it seems so difficult to get the latest versions of Android running on our phones. If the SDK and resources are freely available and the basic drivers, etc. are a part of the ROMs themselves, why is it so difficult to just update the core of the OS to Gingerbread, for example?
I would have assumed it would have been simpler than it appears to be and Google touts it as being simple, so what am I missing? What's the stumbling block?
Android 2.3 was released very recently, developers are hard at work at it.
Sometimes, it is not always up to Google. As of right now, the Vibrant has access to various 2.2 leaks... HOWEVER! the kernels for vibrant has not been open-sourced. So this limits development (OC, UV and so on). The I9000 kernel source is available, but they drain battery for vibrant users and its not worth using these kernels (in my opinion).
For users without rooting, you can blame the manufacturer and/or carrier for the delays.
Pure Google: Google -> Update
Manufacturer: Manufacturer ports Android on top of their skin (HTC Sense, TouchWiz, Motoblur, and so on) -> Carrier (Adds bloat; removes features e.g. tethering, etc) -> Update
The latest leak (to date) is JL5 which contains 2.2 but not 2.2.1? Is that correct?
I've seen some builds floating around with the designation XXJPX and I don't know if XX in this case is a blank place holder, or if it signifies a series number later (alphabetically) than JL5, even so, J comes before P last I checked, so is XXJPX a later leaked build than the JL5?
donalgodon said:
The latest leak (to date) is JL5 which contains 2.2 but not 2.2.1? Is that correct?
I've seen some builds floating around with the designation XXJPX and I don't know if XX in this case is a blank place holder, or if it signifies a series number later (alphabetically) than JL5, even so, J comes before P last I checked, so is XXJPX a later leaked build than the JL5?
Click to expand...
Click to collapse
I believe JPX is the I9000 ROM
Ah, yes, I think so.
So, the JL5 is 2.2 but not 2.2.1?
donalgodon said:
Ah, yes, I think so.
So, the JL5 is 2.2 but not 2.2.1?
Click to expand...
Click to collapse
JL5 is 2.2
We have no official 2.2, and no leak of 2.2.1
That's an example. I can't understand.
Is it that there are so many significant or major changes to the OS between 2.2 and 2.2.1 which would make it so difficult to shoe-horn into a cooked ROM for the vibrant based on JL5?
I had this picture of Android in my mind of being a developers paradise/playground from listening to Google's PR team. Not so, I guess.
Two words:
Platform fragmentation.
If Google did what most of us wished they would do and unilaterally told carriers to make updates on time and to stop skinning Android, we might not be in this situation...
synaesthetic said:
Two words:
Platform fragmentation.
If Google did what most of us wished they would do and unilaterally told carriers to make updates on time and to stop skinning Android, we might not be in this situation...
Click to expand...
Click to collapse
I was under the impression that Google was making (de)fragmentation a priority. As it stands, it really does seem that Android is in danger of becoming another Windows Mobile 6.5.x
I was trying to escape that by selling my HD2.
synaesthetic said:
Two words:
Platform fragmentation.
If Google did what most of us wished they would do and unilaterally told carriers to make updates on time and to stop skinning Android, we might not be in this situation...
Click to expand...
Click to collapse
Skinning isn't really a fragmentation issue. I don't know of any OEM skins that keep ppl from running anything off the Market.
Fragmentation, as used in regard to Android, is the gap between 1.5, 1.6, 2.1, 2.2, and now 2.3, in performance and compatibility with things developers code. Meaning they can't make a single APK run on all these fragmented code-bases. Think Win95, WinNT, WinXP, WinVista, etc., but all being released within 2 years, instead of spread out over a decade and a half.
-bZj
down8 said:
Skinning isn't really a fragmentation issue. I don't know of any OEM skins that keep ppl from running anything off the Market.
Fragmentation, as used in regard to Android, is the gap between 1.5, 1.6, 2.1, 2.2, and now 2.3, in performance and compatibility with things developers code. Meaning they can't make a single APK run on all these fragmented code-bases. Think Win95, WinNT, WinXP, WinVista, etc., but all being released within 2 years, instead of spread out over a decade and a half.
-bZj
Click to expand...
Click to collapse
For the end user, the skins do seem to have a big impact, such as in the case of Samsung, who skins Android with TouchWiz and drags its feet on releasing updates as a result. Same thing happen with HTC and Sense. Sony is much worse.
They could, of course, just leave the UI alone and let the pure Android goodness flow (or hire enough people to get the job done on time if they want to skin, which I'd actually prefer, since some of those innovations really do improve the UI) but all this does seem to impact user experience, since those updates don't get to the phones in a timely manner... at least not like Google had told us they would.
It's always ALWAYS your carrier.
Froyo was released many months ago and stock Android phones, like Nexus 1, got it almost immediately. Gingerbread comes with Nexus S and Nexus 1 is getting it very soon, if it wasn't on Nexus 1 already.
So if fast official OS updates are your main concerns, I suggest you getting a stock Android phone.
i gotta say with our excellent eris devs we should have it in no time
right?
Holy hell...stop the madness.
i hope they are able to port it and get it stable honeycomb looks awesome on the g1!
I don't want honeycomb. I want Ice Cream. In fact, I scream for it.
Sent from my GSBv1.7-ERIS using XDA Premium App
I scream, you scream, we all scream for Ice Cream!
(Can we drop the "Sandwich" thing now?)
aceboogie_2 said:
i gotta say with our excellent eris devs we should have it in no time
right?
Click to expand...
Click to collapse
Doubtful, it's a lot more work than you think.
Also I just watched the video on that and he never even shows what version of the Android OS he has. Not saying it's a lie, just saying i'm skeptical because he never goes through the settings and shows the Firmware Version or any Software Information for that matter. Could very well just be a rom that's themed to the Honeycomb OS.
I have faith that every single version of AndroidOS in the foreseeable future will have a compile or port for the Eris, and in relatively quick fashion since devs put a quick compile or port out first just to show that it can be done, and then work to see if they can work out the kinks. I assume that the reason Gingerbread has been developing on the Eris so much faster than Froyo did because some of what was learned from work on Froyo is applicable to GB, as far as getting certain things working: Wifi, BT, Camera...
So, I have no trouble believing that someone will make a Honeycomb ROM for the Eris sometime sooner rather than later; it's just unknown if it'll really be worth it because of all the things that might get "broken" with it on the Eris. Especially since Honeycomb isn't meant for phones at all, just tablets.
I don't know if this is accurate; it's confusing if it is but it's a WIKI so it might not be, but at http://en.wikipedia.org/wiki/Android_(operating_system) it says that even though Honeycomb is 3.0, that a 2.4 is still planned for April, and that it's only sometime after that, 2.4 and 3.0 will be recombined into Ice-Cream Sandwich about mid-2011.
I further guess that the reason that Google had this split in their Android OS was to get a major new Android OS onto new tablets, but that they won't allow this split to get abused and continued for long at all, so 2.4 will be for phones and then Ice-Cream Sandwhich will probably be for both phones and tablets.
Okay so this may be a useless post and it is my first one so don't beat me up too badly. I have been searching all over the place to find a Froyo build with HTC Sense. It seems as though development has been halted because apparently Sense is too large for the Rhodium CPU and the screen resolution is too high. How can this be true when the Rhodium runs Sense in Windows Mobile 6.5? I want to see a Froyo build that has HTC Sense and camera support. Can or has this been done? Would someone be willing to do it if enough people were willing to donate? I just want my Rhodium to work the way I know it can. I know there is a 2.1 build with Sense but there is no camera and there are many bugs with it and is not useful to me. Any help is greatly appreciated.
If anyone finds any Froyo with sense builds for phones that are NOT the HD or HD2, please post a link to them in this forum.
Thank you.
Sense on WinMo != Sense on Android
So don't confuse them. Why do you want sense? It's just a big piece of bloat, and most of the things you can find in other places (IE Fancy Widget).
Sense in Winmo is native code, Sense in Android is Java. Unfortunately, the gains in terms of development ease gained with Java are offset by the inefficiencies of Java on lower-end hardware.
Also, the problem with Sense is that it needs to be ripped from a Sense-enabled HTC native Android device, and in many cases, the binary has enough customization that it does Bad Things on our devices.
As I understand it, the only Sense-enabled build seen on our devices so far was 2.1, and had, as you mention, resolution issues.
Also keep in mind that the Windows Mobile stock UI was very dated, so Sense was a major upgrade for it. My experience with Sense-enabled Android devices is that it offers very little and just slows the device down. Actually, this seems true for all manufacturer-provided alternate interfaces (like the crappiness of MOTOBLUR...)
Entropy512 said:
Sense in Winmo is native code, Sense in Android is Java. Unfortunately, the gains in terms of development ease gained with Java are offset by the inefficiencies of Java on lower-end hardware.
Also, the problem with Sense is that it needs to be ripped from a Sense-enabled HTC native Android device, and in many cases, the binary has enough customization that it does Bad Things on our devices.
As I understand it, the only Sense-enabled build seen on our devices so far was 2.1, and had, as you mention, resolution issues.
Also keep in mind that the Windows Mobile stock UI was very dated, so Sense was a major upgrade for it. My experience with Sense-enabled Android devices is that it offers very little and just slows the device down. Actually, this seems true for all manufacturer-provided alternate interfaces (like the crappiness of MOTOBLUR...)
Click to expand...
Click to collapse
Just to back this up, I used one of Tiad's Froyo Sense builds for a bout 2 minutes. It it not worth it. Definitely, not worth it.
ryannathans said:
Just to back this up, I used one of Tiad's Froyo Sense builds for a bout 2 minutes. It it not worth it. Definitely, not worth it.
Click to expand...
Click to collapse
Where did you get Froyo Build from Tiad including Sense? AFAIK he just released Eclaire builds containing the UI...
wavesshock said:
Where did you get Froyo Build from Tiad including Sense? AFAIK he just released Eclaire builds containing the UI...
Click to expand...
Click to collapse
He claimed they were Froyo, I only looked at it literally for a minute and never noted what it actually was. I wouldn't be surprised if it was Eclaire.
Anyway, when I get this bloody repo sync command to go through without errors I will start making my own builds I guarantee, they will be better than Tiad, and I don't exactly plan on including any warez
ryannathans said:
He claimed they were Froyo, I only looked at it literally for a minute and never noted what it actually was. I wouldn't be surprised if it was Eclaire.
Anyway, when I get this bloody repo sync command to go through without errors I will start making my own builds I guarantee, they will be better than Tiad, and I don't exactly plan on including any warez
Click to expand...
Click to collapse
Are you going to make sense-builds or do you plan to develop on stock android ports?
Entropy512 said:
Sense in Winmo is native code, Sense in Android is Java. Unfortunately, the gains in terms of development ease gained with Java are offset by the inefficiencies of Java on lower-end hardware.
Also, the problem with Sense is that it needs to be ripped from a Sense-enabled HTC native Android device, and in many cases, the binary has enough customization that it does Bad Things on our devices.
As I understand it, the only Sense-enabled build seen on our devices so far was 2.1, and had, as you mention, resolution issues.
Also keep in mind that the Windows Mobile stock UI was very dated, so Sense was a major upgrade for it. My experience with Sense-enabled Android devices is that it offers very little and just slows the device down. Actually, this seems true for all manufacturer-provided alternate interfaces (like the crappiness of MOTOBLUR...)
Click to expand...
Click to collapse
Thank you. This makes some sense of it (no pun intended). I know there are other widgets that use less resources and look better than sense but I like the look and feel of it. I am probably going to be upgrading to an Evo 4g or Evo 3g so I'll have my sense soon anyway but I was able to get some use from the 2.1 sense build once I used a new kernel and used the "clean slate" scene setting. The only thing missing was the camera. I can get by with some sluggishness as I have been using Windows Mobile for a long time but I cannot get by without that camera support seen in the newer 2.2 builds. Also, the Hero has the same CPU speed as the Rhodium. I am not sure if this makes much difference but the phones are very similar in both screen size and processor speed. As well as the Evo Shift as far as screen. I am still new to all this though and those subtle similarities may really be nothing. I'll keep searching and post if I find anything.
ryannathans said:
Just to back this up, I used one of Tiad's Froyo Sense builds for a bout 2 minutes. It it not worth it. Definitely, not worth it.
Click to expand...
Click to collapse
Where did you get those builds? That was the question I asked in the initial post lol. I love testing so I don't really care if they suck.
nickelghandi said:
Where did you get those builds? That was the question I asked in the initial post lol. I love testing so I don't really care if they suck.
Click to expand...
Click to collapse
On his website, because tiad8 has been banned from xda-devs.
@nickelghandi
Maybe you can test the panda homescreen with sense theme.
http://forum.ppcgeeks.com/android-tp2/113446-nsfw-post-your-tp2-android-home-screen-7.html
Hi,
Is there any way to install some of the Sense applications (Music, Video, Image player) on a HTC Touch Pro2 with the CBX0 Android ROM?. I have a Hero device with almost the same hardware and the Sense applications runs well and I´m use with these applications.
Regards,
clarf
clarf said:
Hi,
Is there any way to install some of the Sense applications (Music, Video, Image player) on a HTC Touch Pro2 with the CBX0 Android ROM?. I have a Hero device with almost the same hardware and the Sense applications runs well and I´m use with these applications.
Regards,
clarf
Click to expand...
Click to collapse
If you can find the APK's, maybe.
But Sense is a proprietary thing. So it's not 'open' - not easily ported/moved to other devices. All XDAndroid builds are AOSP - straight from Google. All open source.
Good luck. If you want, there's a 2.1 Eclair Sense build - but it hasn't been updated since 2010.
arrrghhh said:
If you can find the APK's, maybe.
But Sense is a proprietary thing. So it's not 'open' - not easily ported/moved to other devices. All XDAndroid builds are AOSP - straight from Google. All open source.
Good luck. If you want, there's a 2.1 Eclair Sense build - but it hasn't been updated since 2010.
Click to expand...
Click to collapse
Thanks for reply,
Well many functions on my HTC phone have issues with old kernel versions, I don´t think I could use Eclair Sense if it´s not maintained/updated.
I´ll search first for the APK´s then...
Thank you
clarf
clarf said:
Thanks for reply,
Well many functions on my HTC phone have issues with old kernel versions, I don´t think I could use Eclair Sense if it´s not maintained/updated.
I´ll search first for the APK´s then...
Thank you
clarf
Click to expand...
Click to collapse
You could always try a new kernel on an old system...
But either way, that stuff is ancient.
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...