Related
I am wondering given that this device just got honeycomb.. is there any chance of it getting ICS?
Part of the reason I'm wondering is because I am getting my flyer sometime between the 10th and the 17th coming up according to the "estimated delivery date" when I hit buy.
I have had ICS on my captivate before I ever even got to play with Honeycomb.. my mom got the transformer yesterday.. and there are a few minor quirks with honeycomb that I really don't like.. major example being if you pull up the task manager in ICS you can remove windows and close out the programs.. Honeycomb will pull up windows that aren't open.. and it gets cluttered fast if your done with something and seeing 5 or more windows you don't want open, but can't get rid of..
no sign of ICS anytime soon but maybe if kernel source is released and CM9 development someone will port it here. In regards to the task management, yes it can get cluttered but it is better than not having it at all like gingerbread
I'm hoping they'll have the decency to update us or at least release the source code required...
IANAL, but I believe HTC legally has to release the kernel source for anything it releases. If they never release ICS, we may never get a kernel for ICS.
Honeycomb kernel might work, but I'm not sure if HTC is legally required to release honeycomb kernel source.
As far as I am aware, they did/may have use some proprietary software which would screw up our porting efforts.
So it becomes an issue of "will they" and that is what I am wondering.
Personally I don't think we will ever see ICS on the Flyer. Here are my reasons:
1. Not a lot of Flyers were sold so there is not a large user base. Thus, there is not much developer interest.
2. Sense - From what I understand from what developers have said, the kernels that HTC makes are made to work with Sense and will not work with an AOSP build.
These two things combine to make bringing ICS to the Flyer difficult and there is no one around who appears willing to do it.
I really hope that I am wrong about this but I don't think that I am.
Someone want to educate a noob?
How is it that several other devices (including HTC ones, like the Sensation) are getting ICS ports, but the Flyer/View can't? I mean, it seems unlikely that HTC released AOSP kernel sources for other devices, and even if they did, they're certainly not ICS kernels. Why is it so important for us to have an AOSP kernel (and an ICS one, at that) from HTC in order to get CM on the Flyer/View?
Oh, and then there's devices that didn't even have Android like the TouchPad, and devices that don't have their source code released, like the Kindle Fire.
I'm definitely not a developer, so I'm sure there's something I'm missing...I'm just trying to figure out what it is.
I'm repeating what developers told me or wrote here. I don't know if it is right or wrong.
I think the bottom line is that it is easier to have an AOSP kernel.
I think you can build your own kernel but that is much more work and maybe a hard thing to do.
All of the custom ROMs that we have seen for the Flyer are just modified HTC ROMs that come with certain software preinstalled or other kinds of enhancements.
More popular devices have much more developer interest. I would imagine that some less popular device owners get lucky because some developer also owns the device and is willing to spend the time.
So far, one developer said he would try to bring ICS to Flyer. He tried but gave up because of kernel issues. I don't get the impression that he did too much but at least he gave it a go. No other developer has said anything one way or the other.
I'm not holding my breath..
but, I definitely won't give up hope just yet..
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
DigitalMD said:
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
Click to expand...
Click to collapse
Makes sense to me.
Shame this device hasn't received more attention.
DigitalMD said:
The most likely path would be a port of another HTC device that uses the same processor or very similar. SO when some of the other HTC devices are released with ICS around March or so, we might see some goodness, depends on how close the hardware is and if HTC releases some source code.
Click to expand...
Click to collapse
This is correct and likely the only way we see ICS in a timely manner.
Sent from my HTC_Flyer_P512_NA using Tapatalk
https://plus.google.com/105502178297258827378/posts/PxQ6cVjVdUd
dingnecros said:
https://plus.google.com/105502178297258827378/posts/PxQ6cVjVdUd
Click to expand...
Click to collapse
He's been debunked several times.
Sent from my HTC_Flyer_P512_NA using Tapatalk
So I guess the big question as far as an official update goes.. is how much effort would HTC have to put out in order to do the upgrade...
And will it be worth it for them to do so..
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
ytwytw said:
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
Click to expand...
Click to collapse
Would it be possible to take the pen code from honeycomb and implement it in CM9?
ytwytw said:
I guess the pen is the biggest issue prevent the ICS update
Since it only works in Sense ROM, so even we have a perfect CM9, the pen function is wasted
Click to expand...
Click to collapse
I'd be content with an AOSP rom now, with the pen worked in later.
Sent from my HTC Flyer P510e using Tapatalk
We will see... if any devs are willing, I am sure as heck willing to help and take a crack at it myself..
You can't do AOSP without HTC's help for the kernel and drivers and since HTC only does sense kernels I'm thinking that's not going to happen. I still think a port of an HTC ICS ROM from another device is the most likely path, unless HTC is feeling exceptionally benevolent toward the Flyer. Perhaps the Jetstream tablet will get ICS and that can be ported...
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Dark Reality said:
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Click to expand...
Click to collapse
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
tatperson said:
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Click to expand...
Click to collapse
Try not to think of it in terms of Android versions, but rather, Linux Kernel versions. I believe it is because the 2.6.32 kernel is considered near perfect in terms of stability. Many Linux distributions use that kernel when they want to offer an extremely stable experience to their user base. For bleeding edge features but less stability, most distributions will use version 3+ of the Linux kernel. My guess is that since it is a standard of sorts because of being well-tested, it's just easier to rely on until we are provided with a later version. Just my two cents.
And why wait for Google release of Android 5.0? Why won't we do it ourselves.
tatperson said:
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Click to expand...
Click to collapse
Well, that would make sense if we had the GB kernel, 2.6.35. We have the Froyo kernel, and, AFAIK, there's not even a Froyo ROM for the Photon. Why would there be? It's a Gingerbread phone.
Acvice said:
Try not to think of it in terms of Android versions, but rather, Linux Kernel versions. I believe it is because the 2.6.32 kernel is considered near perfect in terms of stability. Many Linux distributions use that kernel when they want to offer an extremely stable experience to their user base. For bleeding edge features but less stability, most distributions will use version 3+ of the Linux kernel. My guess is that since it is a standard of sorts because of being well-tested, it's just easier to rely on until we are provided with a later version. Just my two cents.
Click to expand...
Click to collapse
This makes sense, and I understand what you mean about Linux kernel versions. I understand the kernel is modular. Once when I was trying Ubuntu, I got a kernel update. Didn't affect anything, just had to reboot. Couldn't tell what it changed.
Also, I just noticed that AOKP Build 8 uses kernel 3.0.1, according to the screenshot on the left. Kinda torn on trying AOKP. On one hand, I'm not a "pink unicorns" kind of guy. On the other, the default wallpaper and status bar icons are nice. Another AOKP ROM featured a pretty cool textured status bar. But when I asked what AOKP had over CyanogenMod, the only answer I got was "swagger". In fact... well, that's a completely different topic. New Topic button, here I come. Hopefully the powers that be will see this as valuable conversation, not spamming up the boards...
//edit: AOKP screenshot lies, it uses the same kernel as the rest (screenshot is of another device, to be fair).
Dark Reality said:
Well, that would make sense if we had the GB kernel, 2.6.35. We have the Froyo kernel, and, AFAIK, there's not even a Froyo ROM for the Photon. Why would there be? It's a Gingerbread phone.
This makes sense, and I understand what you mean about Linux kernel versions. I understand the kernel is modular. Once when I was trying Ubuntu, I got a kernel update. Didn't affect anything, just had to reboot. Couldn't tell what it changed.
Also, I just noticed that AOKP Build 8 uses kernel 3.0.1, according to the screenshot on the left. Kinda torn on trying AOKP. On one hand, I'm not a "pink unicorns" kind of guy. On the other, the default wallpaper and status bar icons are nice. Another AOKP ROM featured a pretty cool textured status bar. But when I asked what AOKP had over CyanogenMod, the only answer I got was "swagger". In fact... well, that's a completely different topic. New Topic button, here I come. Hopefully the powers that be will see this as valuable conversation, not spamming up the boards...
Click to expand...
Click to collapse
AOKP has more features than cyanogen, and dont mind the pink unicorn. Its only a boot animation. And the AOKP team changed it here recently so it really doesnt look as obtrusive as it used to. CNA happens to be my personal favorite.
Well, I kept the boot animation from CM10, which I really like, so whatever ROM I stick with will probably just use that, unless I find something better.
Using AOKP now. A little annoying that I can't add lock slider items, but I can live with it. I see what they mean by swagger -- it's a toggle. I think it's like "Awesomeness Detection" in Rockband 2. That is, a toggle option that does nothing but confuses the user or makes them think they're doing something special. A placebo. But in reality there is no code to it. (I'm assuming about AOKP. Harmonix confirmed this about Rockband 2 -- 3 years after the game shipped.) But yeah, boot animation is fine for now (if a little small). And I'm actually using an AOKP wallpaper. It's the one with the shadow of the guy with the swords. Pretty awesome. (Is that what UnicornPorn.apk is? The wallpapers?)
Curious about CNA but I'm going to give AOKP a few days to settle in. Battery is a big thing for me though.
its actually a nvidia thing, i imagine a quick google search between linus and nvidia will tell ya how he feels about them ;P. (if you dont believe me the transformer lineup has 2.6.39 as its ICS kernel)
you can use any kernel version you want so long as it has all the proper stuff in it, the big thing most people overlook tho is not a lot of people look at the linux kernel and see all the commits. which if you are making kernels i highly suggest you do as there was some awesome battery saving stuff in 2.6.38 as well as some overall speedups.
the version number changing is used to signify a stable release. like 3.0 or 3.1, 3.2 etc.
its entirely possible (hell sometimes needed for some kernel sources) to take what the OEM provides take the corresponding linux kernel (in this case 2.6.32) and overlay the oem code. the reason why most dont do it is cuz it takes a long time. once you have the linux tree merged with your device specific files you can then backport patches much easier.. and at that point you could have a 3.x kernel using the same 2.6.32 stuff from the oem. wont help you overall on booting and fixing camera etc in ics but it will give ya plenty of improvements in just the kernel itself
Dark Reality said:
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Click to expand...
Click to collapse
well from a laymen point of view i run and love most of th3bills roms(PORTS) from jokersax.com and considering my mopho(photon) is over a year old and getting almost 7000 antutu and 4000+ quadrant scores(which makes a new GALAXY NEXUS STOCK LOOK SLOW)...i don't care what kernel when im blazing like that.lol If its kicking azz dont fix
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
Would be nice to get rid of it since I'm WiFi only now. i keep it in airplane mode 24/7 now.... I found this...
http://forum.xda-developers.com/showthread.php?t=1813655
What is the agenda for the new midstream development? Ics? sense 4.x?
Has that been determined?
first thing will be to get a new kernel that allows ics/jb versions on it
i think the work will be porting a version from the closest device - htc flyer.
i don't sense will be a part of it...but its too soon to tell
guru_shastri said:
first thing will be to get a new kernel that allows ics/jb versions on it
i think the work will be porting a version from the closest device - htc flyer.
i don't sense will be a part of it...but its too soon to tell
Click to expand...
Click to collapse
I think the Vivid guys have got a working kernel for ICS for the hardware of our device. It was posted at http://forum.xda-developers.com/showpost.php?p=30762078&postcount=33
So I guess that would be a head start in the kernel's direction.
Any news about the dev getting the device/and or having started work on it? I am sure we all would love to know what the progress is on that front.
Hello,
I've been a fan of this site for a while, and I just created an account tonight.
I noticed that the ICS kernel source was released by HTC today. I am looking forward to having a nice ICS AOSP rom with working video. Thank you DEVS!
With the ICS kernel source, are we limited to ICS versions of android? Can the kernel source be modified to work with Jelly Bean? Maybe CM10.1?
From a verizon customer holding on to unlimited data,
thanks again to all of the DEVs and individuals that contribute to the Thunderbolt community.
blackshoes said:
Hello,
I've been a fan of this site for a while, and I just created an account tonight.
I noticed that the ICS kernel source was released by HTC today. I am looking forward to having a nice ICS AOSP rom with working video. Thank you DEVS!
With the ICS kernel source, are we limited to ICS versions of android? Can the kernel source be modified to work with Jelly Bean? Maybe CM10.1?
From a verizon customer holding on to unlimited data,
thanks again to all of the DEVs and individuals that contribute to the Thunderbolt community.
Click to expand...
Click to collapse
From what I understand it's being worked on, maybe not actively right now but it seems to be a strong possibility.
HTC released their kernel version 3.0.16. That will out-of-the-box support Ice Cream Sandwich. Jelly Bean needs 3.0.31 (or higher). I think what the kernel developers now need to do is back port the necessary bits and pieces to HTC's version to make it compatible.
hallstevenson said:
HTC released their kernel version 3.0.16. That will out-of-the-box support Ice Cream Sandwich. Jelly Bean needs 3.0.31 (or higher). I think what the kernel developers now need to do is back port the necessary bits and pieces to HTC's version to make it compatible.
Click to expand...
Click to collapse
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
What a tease!
Sent from my Blissful Bolt using Tapatalk 2
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
That is great news Santod!
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
I think I just soiled myself. Oh the amazing things I miss while I'm at work.
santod040 said:
Already have one patched up to around 3.0.80, just gotta finish adding in the new board files, LTE drivers and defconfig.
As we all know though, older kernels can also be made to run versions they aren't intended for as well.
Also already have CM10.1 running pretty darn well...
Click to expand...
Click to collapse
Is the RIL working for you?
video of cm1.1 on the tbolt
blackshoes said:
Hello,
I've been a fan of this site for a while, and I just created an account tonight.
I noticed that the ICS kernel source was released by HTC today. I am looking forward to having a nice ICS AOSP rom with working video. Thank you DEVS!
With the ICS kernel source, are we limited to ICS versions of android? Can the kernel source be modified to work with Jelly Bean? Maybe CM10.1?
From a verizon customer holding on to unlimited data,
thanks again to all of the DEVs and individuals that contribute to the Thunderbolt community.
Click to expand...
Click to collapse
HTC Thunderbolt Runnig cm10.1 Video:good:
jacobmacek said:
HTC Thunderbolt Runnig cm10.1 Video:good:
Click to expand...
Click to collapse
loving this! :good:
Cyanogenmod 10.1 official support?
I'm curious. Once the devs are able to get the kernel ready for cyanogenmod 10.1, has anyone thought about submitting that kernel to cyanogenmod for official Thunderbolt cyanogenmod builds?
From the posting linked below, cyanogenmod requires a tested kernel and a developer or group of developers that will maintain the kernel for official support. Is cyanogenmod official support a possibility with the kernel the DEVs are working on?
forum.cyanogenmod.com/topic/72612-can-i-get-cyanogenmod-on-my-device/
Thanks for the info!
blackshoes said:
I'm curious. Once the devs are able to get the kernel ready for cyanogenmod 10.1, has anyone thought about submitting that kernel to cyanogenmod for official Thunderbolt cyanogenmod builds?
From the posting linked below, cyanogenmod requires a tested kernel and a developer or group of developers that will maintain the kernel for official support. Is cyanogenmod official support a possibility with the kernel the DEVs are working on?
forum.cyanogenmod.com/topic/72612-can-i-get-cyanogenmod-on-my-device/
Thanks for the info!
Click to expand...
Click to collapse
I can't speak for everyone, but let's get "that" kernel worked out first.
It's now possible, but still not exactly a simple task.
Having already knocked out a custom Sense ICS kernel from the source was done without much hassle already.
And Jelly Bean has come pretty far for the Bolt already, but making a fully functional Jelly Bean kernel from HTC's ICS source may take a bit more dilligence.
So I would just say let's take it one step at a time.
Official builds would require dedication on a dev or multiple devs parts to continue updating and supporting it.
There aren't a lot of candidates left, that may still have enough personal interest in doing so when that time comes.
Basically, that's just not something that can be predicted at this point, as there are still uncertainties surrounding such a thing, from several different aspects/angles.
It would of course be great to see the old Bolt be added to the list of devices which are officially supported.
Who knows what else the future may hold for this faithful beast that keeps getting surprises, even if long overdue.
jacobmacek said:
HTC Thunderbolt Runnig cm10.1 Video:good:
Click to expand...
Click to collapse
I want.
Sent from my Blissful Bolt using Tapatalk 2