Related
I apologize for my noobish question, but how are the ASOP builds starting to roll out w/o source being released?? I understand you can compile aosp builds on your own, but doesnt the source code provide all the tweaks you need to optimize it on a device to device basis?
There's no ICS source for the Captivate either, but we are officially supported on CM9. Very glad!
Sent from my Captivate using Tapatalk!
if there is good source from another device that is near this one then porting could be possible.
The short answer is a combination of two things based on what I can tell.
They are actually using the existing kernel for the leaked ICS roms and beginning to dissect them. As far as I know, the current AOKP roms being used are using either an unmodified original kernel from ULD3 or 'very slightly' modified/patched kernel from ULD3 with a few tweaks for overclocking support and whatnot.
As far as what is happening with the Captivate, I believe they are taking heavy sections from the Gingerbread source code and splicing it in to their ICS kernel and changing what they need to for ICS compatibility.
Also, similar devices that have ICS source code floating around can also be spliced up.
I am only speculating here since I am not involved in the projects, if someone knows more than I, feel free to speak up.
Hi Kazuni et al, are you developing a non-Samsung themed JB ROM for the I9305? Something like the many CM10/ParanoidAndroid ROMs that are available for the I9300? Would be great to have a "purer" ROM for this new flagship....less of the Samsung customization
This has been discussed several times before but the I9305/I9300 share most of the same components, less the radio correct? If so, would the I9300 ROMs work if they're used w/ a 9305 radio instead? So it would be an easier way to port 9300-developed ROMs over?
Would love to see this, esp if it's built on the new 4.1.2!
There are other differences as well like a different partition layout, but I guess that they might partially work if configured with a compatible layout, would likely have no sound or modem functionality without proper work, a Rom compiled for this model would be better.
Sent from my GT-I9305 using xda app-developers app
I have asked xplodwild in the cm10 thread uf any if team hacksung are able time work on a port. We can but hope!!!
mys3 said:
I have asked xplodwild in the cm10 thread uf any if team hacksung are able time work on a port. We can but hope!!!
Click to expand...
Click to collapse
I have my fingers crossed. After putting CM10 on a relatives SG3 I want in on the action bad.
I intend to jump in and have a go at CM10 for the i9305 when I receive mine this week. It will be my first attempt at a complete ROM so don't hold your breath or anything.
farnsbarns said:
I intend to jump in and have a go at CM10 for the i9305 when I receive mine this week. It will be my first attempt at a complete ROM so don't hold your breath or anything.
Click to expand...
Click to collapse
:good: You go champ! Let us know how you progress!
Man I hope there is a CM10 rom soon. I want to get started on rooting, I am an iOS refugeee!!! All im doing is watching people on youtube with CM10/Paranoid Android and being jealous. =(
farnsbarns said:
I intend to jump in and have a go at CM10 for the i9305 when I receive mine this week. It will be my first attempt at a complete ROM so don't hold your breath or anything.
Click to expand...
Click to collapse
Oh I will be holding my breath!
bleepsake said:
Man I hope there is a CM10 rom soon. I want to get started on rooting, I am an iOS refugeee!!! All im doing is watching people on youtube with CM10/Paranoid Android and being jealous. =(
Click to expand...
Click to collapse
Don't get me wrong, but didn't you notice the big ****storm about samsung being developer unfriendly and the exynos platform being the hell on earth?
Some of our guys are very sick of samsung and are not going to touch any of the new samsung devices.
Not saying that nobody will port it, but i recommend you to sell this device as fast as possible and get a new upcoming nexus device if you really wanna run AOSP based roms.
If you like laggy and buggy AOSP roms and especially waiting for round about 6 months to get a new android version, stay on what you're currently owning.
codeworkx said:
Don't get me wrong, but didn't you notice the big ****storm about samsung being developer unfriendly and the exynos platform being the hell on earth?
Some of our guys are very sick of samsung and are not going to touch any of the new samsung devices.
Not saying that nobody will port it, but i recommend you to sell this device as fast as possible and get a new upcoming nexus device if you really wanna run AOSP based roms.
If you like laggy and buggy AOSP roms and especially waiting for round about 6 months to get a new android version, stay on what you're currently owning.
Click to expand...
Click to collapse
I didn't really expect you to add something positive to this topic.!. I really hope that all of us that just got the I9503 didn't buy it for only running AOSP based roms. If that was the case I would buy the upcoming LG nexus that's NOT the case for me. And SamsungExynos posted a tweet today "full availability of integrated source code for #Exynos 4 family of processors on OrigenBoard by the end of 2012"
I wonder what will happen to all these devs that left the GS3 because of samsung not releasing the Source. And then now it looks like they will b releasing something soon, Are you all going to come back? Or just let new and upcoming devs take over. I Feel that with all sources released on this device with the Quad Core and 2gb Ram DAMMMM how smoooth will a proper built CM10 run. And to be honest My device is very smooth as it is. I am not dying for CM10 i actually like the new touchwiz, I like features and animations. And with all of that , this is still hell smooth in my opinion. Either way To me its a win win, if they release the source GREAT if not oh well still very good!!... But i do believe they will release it.
btemtd said:
I wonder what will happen to all these devs that left the GS3 because of samsung not releasing the Source. And then now it looks like they will b releasing something soon, Are you all going to come back? Or just let new and upcoming devs take over. I Feel that with all sources released on this device with the Quad Core and 2gb Ram DAMMMM how smoooth will a proper built CM10 run. And to be honest My device is very smooth as it is. I am not dying for CM10 i actually like the new touchwiz, I like features and animations. And with all of that , this is still hell smooth in my opinion. Either way To me its a win win, if they release the source GREAT if not oh well still very good!!... But i do believe they will release it.
Click to expand...
Click to collapse
-----> "for OrigenBoard" <-----
It's a exynos development board and has not much to do with samsung smartphones.
The ICS code was broken, outdated and mostly unusable on phones.
The same code is now available again.
I really don't expect a wonder.
From what andreilux has seen and stated below it does not seem like the old stuff and samsung continue to update. Last update was done earlier today here is what andreilux said in the exynos petition page in the i9300:
(They released the 5250 development board and site together with a 800 page user's manual, something which we didn't have before for any SoC. I'll have to see what they uploaded on the Git as it's quite a lot.
Edit: from what I can see at first glance they have 4.1.1 Jellybean sources up there and apparently the newest stuff.
Sent from my GT-I9305 using xda app-developers app)
So it seems samsung is pulling up there sox and getting **** done. Maybe christmas came early i also have news from a great dev getting our devic. (I9305) but must not say who at this point
btemtd said:
From what andreilux has seen and stated below it does not seem like the old stuff and samsung continue to update. Last update was done earlier today here is what andreilux said in the exynos petition page in the i9300:
(They released the 5250 development board and site together with a 800 page user's manual, something which we didn't have before for any SoC. I'll have to see what they uploaded on the Git as it's quite a lot.
Edit: from what I can see at first glance they have 4.1.1 Jellybean sources up there and apparently the newest stuff.
Sent from my GT-I9305 using xda app-developers app)
So it seems samsung is pulling up there sox and getting **** done. Maybe christmas came early i also have news from a great dev getting our devic. (I9305) but must not say who at this point
Click to expand...
Click to collapse
Will this dev build ROMs or only Kernels?
All i want for my nice i9305 is a real good dev
Stony-D said:
Will this dev build ROMs or only Kernels?
All i want for my nice i9305 is a real good dev
Click to expand...
Click to collapse
kernel is the most important thing here atm...but a good cm or aosp were pretty hell for this phone !
i heard miui will release a jb version for i9300 soon so this porting would be easy
Yes he does. But not saying anything more for now
Sent from my GT-I9305 using xda app-developers app
Omfg sorry for spam but the dev will build really ROMs?
Sorry Spaming here but a CM10 Rom for my I9305 would be realy Great.
+1 to non-Samsung-based JB rom like CM10, PA or PACman's mix of all three I'm picking up my i9305 this weekend (South Africa) and really hope that some of the big dev's take to this handset.. number of roms at current is dis-heartening :crying: :crying:
---------- Post added at 04:15 PM ---------- Previous post was at 03:32 PM ----------
codeworkx said:
-----> "for OrigenBoard" <-----
It's a exynos development board and has not much to do with samsung smartphones.
The ICS code was broken, outdated and mostly unusable on phones.
The same code is now available again.
I really don't expect a wonder.
Click to expand...
Click to collapse
Hi codeworkx.. this is a copy of a post I made on another i9305 thread, it seems more relevant here tho..
Samsung have released the source code for the i9305.. here and I noticed it's also on Github here does this mean there's a chance of more dev's buying into this device for custom rom and kernel devving
defibitely deserves a plus one on this. cm10 porterssss please i would love to experience a proper stock jb theme
Sent from my Beautiful GT-I9305 using Tapatalk
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
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
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?