In theory this should be quite useful, no?
Just putting this up here for those who may have lost hope, but on a whim I checked their source repository today and it would seem they've at least uploaded Kernel source!
ftp://Kernel_End_User:[email protected]/
Directory: Pure XL P0010UU (it's a bit of a mess, you may wish to CNTRL+F this)
I haven't checked their software repo yet for ROM source, but it was not uploaded when I initially found this information about a month and a half ago.
The kernel is only VANILLA STOCK source, I haven't compiled it or anything, I'm only linking their servers because I imagine that this isn't getting checked on a regular basis (not much to expect would happen). But, something has happened, so I figured I'd draw some attention to it.
Many thanks to those ROM and kernel devs who have been working to bring us some solid software. It's honestly my only major gripe with the phone.
We (me, acheron, root-expert) tried to compile this several times with CyanogenMod repos with no luck. It's from 7th December 2015 so nothing changed.
bemolx said:
We (me, acheron, root-expert) tried to compile this several times with CyanogenMod repos with no luck. It's from 7th December 2015 so nothing changed.
Click to expand...
Click to collapse
Darn. If only they were more willing to facilitate development.... the software is my only real issue with the phone. Thanks for your work, however.
Same thing here... I would love to have the latest CyanogenMod
Only for updating this post:
Kernel source, mostly ready for Marshmallow ROMs, you can find here on 'cm-13.0' branch.
Linux upstream 3.10.103
Still trying to boot it up.
Gonna update CyanogenMod thread soon.
Cheers
bemolx said:
Only for updating this post:
Kernel source, mostly ready for Marshmallow ROMs, you can find here on 'cm-13.0' branch.
Linux upstream 3.10.103
Still trying to boot it up.
Gonna update CyanogenMod thread soon.
Cheers
Click to expand...
Click to collapse
Great news @bemolx
TheLastCanadian said:
Darn. If only they were more willing to facilitate development.... the software is my only real issue with the phone. Thanks for your work, however.
Click to expand...
Click to collapse
Out of curiosity, how have other manufacturers "facilitated" this sort of development for their products?
vicks1008 said:
Out of curiosity, how have other manufacturers "facilitated" this sort of development for their products?
Click to expand...
Click to collapse
Some lend active support to the venture, LG has a dedicated team for liason, better documentation, etc.
I think it's probably pretty telling that it's only now the BLU source has worked - and it took them 5 months to even release it.
BLU releases kernel source codes upon request instead of proactively providing them. If they're asked for on launch, then the kernel source is released shortly after. So I don't believe the claim that it took 5 months to release.
Can you show me proof of other manufacturers lending support to show BLU?
NVMD.
TheLastCanadian said:
Your belief is irrelevant. They have had many requests, and always it is a referral to the FTP site they host. This site did not populate with the kernel/rom source for quite a few months after I bought the phone, and I was already behind the curve by about 2. I purchased mine on the 30th of December, 2015. I made this post the day after I noticed they had Kernel/Rom. If the URL was still working, I could verify for you the time limit. With that said, it was approximately 5 months.
As for other manufacturers lending support.... ZTE for instance is collaborating with Cyanogenmod, LG proactively provides source and has actually tried to make the process quite simple for most of their phones, and ultimately, contacting BLU about the matter is functionally worthless, as BLU is a reseller and at the whim of Gionee. BLU can't help because they don't do R&D or software as I can tell for the phone.
I'm particularly pissed about the fact I asked before I bought the phone if source was available and it was GPL compliant and I was told yes. 5 months is just a little outside of Amazon's return policy. The Pure XL is a good phone, but the software is quite lacklustre. CM would really be the bees' knees.
Click to expand...
Click to collapse
Well I'm obviously not going to bother contacting my connections at BLU with that attitude. Good luck guys!
vicks1008 said:
Well I'm obviously not going to bother contacting my connections at BLU with that attitude. Good luck guys!
Click to expand...
Click to collapse
I should correct myself slightly. Supposing my e-mail record is correct, they released it 4 months after the phone. I say your belief isn't relevant because a fact is a fact.... as of April 5th, I was still getting apologies from them about Kernel source not being available, specifically, "No ETA on source at this time". Ergo, it could have been longer.
As for BLU, I'm just being honest. They don't develop, they're a reseller.
bemolx said:
Only for updating this post:
Kernel source, mostly ready for Marshmallow ROMs, you can find here on 'cm-13.0' branch.
Linux upstream 3.10.103
Still trying to boot it up.
Gonna update CyanogenMod thread soon.
Cheers
Click to expand...
Click to collapse
Just a small update;
Linux kernel upstream: 3.10.104
Regenerated defconfig as well, the same branch.
I'll try it with full build today.
Related
Ok, I know this is a subjective question and I probably wont get an exact answer but does anyone have a estimate when the first Honeycomb based ROM beta will be available for testing? I'm interested to see if it will make a better remote access platform than the current phone based ROMs.
Search... My friend. All good things come to those who wait. Of course, if you want Honeycomb now, you could just swing over to Best Buy and pick one up.
still waiting for the source
source still hasn't been uploaded
I thought Google was in the habit of releasing the source at the same time as the product?
jbirdvegas said:
source still hasn't been uploaded
I thought Google was in the habit of releasing the source at the same time as the product?
Click to expand...
Click to collapse
No they generally wait 30 days and release source. Of course honeycomb source based on gpl will be released but it doesnt force nvidia to release proprietary drivers or anything else that is proprietary from google.
Heres the ETA for honeycomb........Now if you buy a xoom.....sometime between now and 2020 for everyone else.
thebadfrog said:
No they generally wait 30 days and release source. Of course honeycomb source based on gpl will be released but it doesnt force nvidia to release proprietary drivers or anything else that is proprietary from google.
Heres the ETA for honeycomb........Now if you buy a xoom.....sometime between now and 2020 for everyone else.
Click to expand...
Click to collapse
HAHAHA! Your posts make me laugh every day. Seriously though, people need to relax. I'm having tons of fun every day bug hunting and streamlining current dev projects. Stop waiting around for the future and make the current community projects better by testing roms and communicating with devs. Dive in to the guts of a real and current build and strive to make what we have better. And have fun for gods sake. That's why we are all here in the first place.
Closing thread. Answered time and time again.
For those familiar with Ziggy's work, he finally compiled a kernel for the Thunderbolt. It is a beta kernel so there will be bugs, so test it out. For reporting bugs please comment on his website. He is a great kernel dev. Please donate to him if you like his work. I am in no way affiliated with Ziggy, just wanted to spread the news.
UPDATE: My previous thread was closed because of a direct link I provided. I decided to create a new thread just for discussion purposes and bug tracking. You can google "ziggy471" to get to his site for the kernel. You can also google the name of the latest kernel update for the link.
Latest Kernel Update:
Beta Kernels 10 Apr 11
Running BFS kernel, and getting the best battery life I've ever experienced. HIGHLY HIGHLY HIGHLY RECOMMEND.
Last thread was closed because ziggy is not following GPL and is not posting his source, which is required. XDA cracks down hard on people who do not follow GPL.
nemesys504 said:
For those familiar with Ziggy's work, he finally compiled a kernel for the Thunderbolt. It is a beta kernel so there will be bugs, so test it out. For reporting bugs please comment on his website. He is a great kernel dev. Please donate to him if you like his work. I am in no way affiliated with Ziggy, just wanted to spread the news.
UPDATE: My previous thread was closed because of a direct link I provided. I decided to create a new thread just for discussion purposes and bug tracking. You can google "ziggy471" to get to his site for the kernel or use the pic attached for reference. You can also google the name of the latest kernel update for the link.
Latest Kernel Update:
Beta MECHA Kernel 6 Apr 11
Click to expand...
Click to collapse
You don't get it...
cabagekiller said:
Last thread was closed because ziggy is not following GPL and is not posting his source, which is required. XDA cracks down hard on people who do not follow GPL.
Click to expand...
Click to collapse
You are correct and I spoke to Ziggy on this issue and was told when his kernel is stable enough he will release his source.
adrynalyne said:
You don't get it...
Click to expand...
Click to collapse
Whether I get it or not, I think his kernel deserves a forum for discussion. Thank you for your 2 cents.
I agree, my battery life is amazingly good.
Sent from my ADR6400L using XDA Premium App
His new test ones are out.
ridobe said:
His new test ones are out.
Click to expand...
Click to collapse
Yeah and it comes with a script! lol
Anyone else's phone running super hot with the new kernel that was released today? Mine is just too hot to touch almost...thinking about going back to the kernel before this update if it doesn't change soon.
Thunderbolt Rooted!
andrew53517 said:
Yeah and it comes with a script! lol
Click to expand...
Click to collapse
I don't have access to a computer all the time (or very often). Is there a way to copy/paste that script into the init.d folder through Root Explorer (or another app) instead of having to push it with ADB? Thanks in advance for any help!
Edit: Nevermind I figured it out. Having random restarts with the Kernel though so I'm reverting back to the BFS 4-6-11 kernel. That one was rock solid and the only issue was the proximity sensor.
I have his 4-10 BFS, what are you suppose to do with the script and why?
Going by what Ziggy said on his blog, the script is used to lower voltages/save a lot of power. I didn't have good luck with the kernel/script combo or just the kernel itself. It ran super hot and I was getting random lockups and random reboots on even the stock clock frequency. I moved back to the 040611 BFS kernel since the only issue I had with that kernel was the proximity sensor. The 040611 kernel also had insanely good battery life (or at least for how I use the phone, it did).
LSUstang05 said:
Going by what Ziggy said on his blog, the script is used to lower voltages/save a lot of power. I didn't have good luck with the kernel/script combo or just the kernel itself. It ran super hot and I was getting random lockups and random reboots on even the stock clock frequency. I moved back to the 040611 BFS kernel since the only issue I had with that kernel was the proximity sensor. The 040611 kernel also had insanely good battery life (or at least for how I use the phone, it did).
Click to expand...
Click to collapse
+1. It locked up on me too and ran super super hot. Reverted back till fixed.
Thunderbolt Rooted!
nemesys504 said:
Whether I get it or not, I think his kernel deserves a forum for discussion.
Click to expand...
Click to collapse
+1
LSUstang05 said:
Going by what Ziggy said on his blog, the script is used to lower voltages/save a lot of power. I didn't have good luck with the kernel/script combo or just the kernel itself. It ran super hot and I was getting random lockups and random reboots on even the stock clock frequency. I moved back to the 040611 BFS kernel since the only issue I had with that kernel was the proximity sensor. The 040611 kernel also had insanely good battery life (or at least for how I use the phone, it did).
Click to expand...
Click to collapse
mine didn't lock up, but it was warm all the time (even when i wasn't using it) and had insane battery drain, like 40% in 2 hours. i reverted to 4-6-11 kernel and all is well again
edit: this is obvious to xda regulars, but noobs should download & flash the MECHA kernels for Tbolt. all other roms are for other devices. if you flash your new Tbolt with an EVO rom, you will be a very sad panda
Where is the source for this kernel?
jlevy73 said:
Where is the source for this kernel?
Click to expand...
Click to collapse
This has been asked several times, so I figured i would jump in and share what I know...
I speak to Ziggy almost daily when helping him debug stuff and he has spoken rather openly about this. He's not playing games or avoiding the issue and is going to post his sources and patches soon. There are one-and-a-half reasons he hasn't so far:
The half reason: There are some voltage issues and frankenstine tree problems that are causing some non-booters that need to be fixed before a public release can be considered safe. Now, the reason this is a "half reason" is because some may argue that he still needs to release it under GPL terms even though it's a beta, while others would argue that HTC doesn't release their betas under the GPL until they are safe either. If they did, HTC would have dropped their source 6 months ago, but they didn't. So it's an argument of where you stand semantics. I'm not telling you where to stand on that one - make up your own mind. However, it is worth noting that Ziggy himself never started a TB kernel thread SPECIFICALLY for the reason that he did not want to violate XDA's terms in accordance with the GPL. Other users started their own Ziggy threads independently
The bigger reason: He is currently in talks with an intellectual property attorney in order to retain personal IP rights on some of the code he has personally written, and was advised by that attorney to not release his full source under the GPL since that source would include the code he is trying to secure. Once that is taken care of, he will release the bulk of his source and patches, while retaining a few flashable patches for himself of his own personal code to further enhance the kernel - assuming he gets that all worked out with the IP lawyer.
That may frustrate some people, while making others very happy. I can also tell some of the devs are getting anxious since they see Ziggy added/changed/removed over 35,000 lines of code in the TB kernel and their eyebrows raise a little and they want his source so they can see what he's up to I don't know where you stand on the issue, nor will I tell you which side to take. I already have his source so quite frankly I don't care either. Again, I'm just the messenger sharing what I know. Don't hate on me if you don't like the info above - it's not my call
You'll all get the source/patches soon enough
i can't say i blame ziggy for doing things this way. it's his kernel, he has the right to do what he wants with it, including seeking intellectual rights. i'm glad he made his kernels available for the rest of us to try. more rom/kernel options is good for all of us
IANAL but sounds like walking a fine line...any of the witheld patches will be designed specifically for the purpose of merging with GPL licensed code. I'm sure the attorney knows his stuff, but at minimum doesn't seem in the spirit of AOSP.
eschelon said:
This has been asked several times, so I figured i would jump in and share what I know...
I speak to Ziggy almost daily when helping him debug stuff and he has spoken rather openly about this. He's not playing games or avoiding the issue and is going to post his sources and patches soon. There are one-and-a-half reasons he hasn't so far:
The half reason: There are some voltage issues and frankenstine tree problems that are causing some non-booters that need to be fixed before a public release can be considered safe. Now, the reason this is a "half reason" is because some may argue that he still needs to release it under GPL terms even though it's a beta, while others would argue that HTC doesn't release their betas under the GPL until they are safe either. If they did, HTC would have dropped their source 6 months ago, but they didn't. So it's an argument of where you stand semantics. I'm not telling you where to stand on that one - make up your own mind. However, it is worth noting that Ziggy himself never started a TB kernel thread SPECIFICALLY for the reason that he did not want to violate XDA's terms in accordance with the GPL. Other users started their own Ziggy threads independently
The bigger reason: He is currently in talks with an intellectual property attorney in order to retain personal IP rights on some of the code he has personally written, and was advised by that attorney to not release his full source under the GPL since that source would include the code he is trying to secure. Once that is taken care of, he will release the bulk of his source and patches, while retaining a few flashable patches for himself of his own personal code to further enhance the kernel - assuming he gets that all worked out with the IP lawyer.
That may frustrate some people, while making others very happy. I can also tell some of the devs are getting anxious since they see Ziggy added/changed/removed over 35,000 lines of code in the TB kernel and their eyebrows raise a little and they want his source so they can see what he's up to I don't know where you stand on the issue, nor will I tell you which side to take. I already have his source so quite frankly I don't care either. Again, I'm just the messenger sharing what I know. Don't hate on me if you don't like the info above - it's not my call
You'll all get the source/patches soon enough
Click to expand...
Click to collapse
I do appreciate the quite thorough explanation regarding the rationale of not releasing his kernel source. While GPL is a discussion for another day, the whole thing for me is by definition, Android is AOSP. I'm seeing a disturbing trend not amongst developers so much but from manufacturers re-writing the rules on being Open Source. Take Motorola for example. They release all phones with a hardware lock on their bootloaders. Poor folks using the Atrix have to go through a ridiculous side loader app to download anything not from the market. Perhaps Google should start a new branch called the Android Unopen Source Project
Anyway, I don't know all the specifics behind Ziggy's IP issues so not knowing the full extent of the facts I won't comment on that. I respect Ziggy and appreciate what he brings to Android. I just don't want to see developers close their source code because if Cyanogen took that some approach where do you think the development community would be today?
Post removed
We need to bomb HTC's website with comments to encourage them to release the kernel source code for our device. I suggest we all go to the following link daily and request its release;
http://htcdev.com/contact
HTC just sent me a link to take a survey, another good tool to blast them with.
http://survey.htc.com/worldwide
Code has been released, I like to think all our complaints helped. Feel free to lock this thread if need be!
http://www.htcdev.com/devcenter/downloads
We have been. I've sent them several notices on a near daily basis.
Sent from my myTouch_4G_Slide using xda premium
I doubt that that link is anything more than a placebo.
http://www.htc.com/us/about/contact-by-email
Say something along the lines of "you're in violation of GPLv2 which requires that source be released along with binary. GPLv2 does not allow for anything besides release of source NOT being ANY LATER than binary distribution."
I.e., though GPLv2 doesn't specify an exact time frame, the implication of this is that the source must be made available by the EXACT MOMENT that the binary is distributed. It *does* allow for the source to be released BEFORE the binary, but does NOT allow for the binary to be released before the source.
IMO, the kernel source archive should be included within the system partition of the phone, at least for early releases while there is sufficient storage space for it all to fit. This would greatly simply source distribution.
Even though I went to that page and asked for the kernel source code to be released, it looks like they're on a pretty routine schedule as far as what and when they release things and we're probably still a little ways out on the source code. But it can't HURT to keep trying, right?
Submitted. Hopefully they'll listen up.
BiggJurk said:
We need to bomb HTC's website with comments to encourage them to release the kernel source code for our device. I suggest we all go to the following link daily and request its release;
http://htcdev.com/contact
Click to expand...
Click to collapse
Yeah, we have been. As unclespoon said they are on a fairly set release schedule that they must be comfortable with [legal-wise].
Read my replies here, there is another link that got me a response that was from a human:
http://forum.xda-developers.com/showthread.php?t=1247374
HTC does this **** on purpose. They have a bunch of new devices coming out and if they were to release the code that would impact there profit margins. This processor can handle 1.5 ghz as a daily driver. The new HTC amaze has exact same processor but is overclocked 300mhz more then our device. And it has a 1gb of RAM. Samsung has gotten great at releasing there code within 1 week or even earlier. HTC PLEASE TAKE NOTES FROM SAMSUNG.
Sent from my myTouch_4G_Slide using xda premium
FYI
I filled out a customer service survey from HTC and gave them all bad ratings in regards to their non-response for the kernel source code. A representative just personally called me and is trying to get an eta on the release if not email me a copy of the code. I would suggest everyone completes a survey with negative comments at the following location:http://survey.htc.com/worldwide. I know surveys like this affects their metrics and gets managements attention. The guy on the phone also said that Android is released under the Apache license agreement.
Regards,
Filled out the survey.
Let's see if they respond.
cal3thousand said:
Filled out the survey.
Let's see if they respond.
Click to expand...
Click to collapse
I think it took them 2 weeks to get back to me.
BiggJurk said:
I think it took them 2 weeks to get back to me.
Click to expand...
Click to collapse
My guess is that they'll "get back to you" in a month or however long until they would have normally released the source code. I think they're too big to be bothered by people complaining about lack of source code. Bottom line is there probably won't ever be any "consequences" as a result of them taking their time on releasing kernel source. We only complain because we want it, but it's not like they are really doing anything wrong by just releasing it on their own schedule.
BiggJurk said:
The guy on the phone also said that Android is released under the Apache license agreement.
Click to expand...
Click to collapse
I've heard that before, but I don't see how that's possible since Android is based on Linux. If it were based on BSD that'd be another matter.
BiggJurk said:
The guy on the phone also said that Android is released under the Apache license agreement.
Click to expand...
Click to collapse
Wow, congrats to phone guy!! Unfortunately, either he was trying to get you to shut-up or misunderstood what you wanted them to release. Google mostly licensed Android with the Apache 2.0. This allows others to customize Android and they don't have to release their changes i.e. customizations made by phone manufacturers (it means other things too but this was Google's main reason for this license). HTC doesn't have to give us their Android source. The Linux kernel is GPL - there is no way around that. The GPL states that the source must be released at the same time as the binary is released to the end-user (it even states that the source should be no harder to obtain than the binary is i.e. we should get the kernel source with our devices - on the sd card or something). Still have no idea where HTC gets 90-120 days from the GPL wording.
I sent a note to EFF asking if they were aware of whats going on. They said they were and were researching the situation.
---------- Post added at 06:50 PM ---------- Previous post was at 06:37 PM ----------
unclespoon said:
but it's not like they are really doing anything wrong by just releasing it on their own schedule.
Click to expand...
Click to collapse
They are though. They are directly violating the GNU GPL but you are right - there are too few of us who actually want the kernel source for them to really worry. Can't believe one of the actual Linux kernel devs hasn't caught wind of this and made a statement.
I sent a couple of requests. Let's hope they move their asses.
Source has been released:
http://www.htcdev.com/devcenter/downloads
HebrewToYou said:
Source has been released:
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
I think you were the first one to find it. I thanked you elsewhere you've mentioned it as well.
Maybe the OP can come through and update the thread title.
Edit to add - download reads 94.0MB on the HTC page, but my download over Tmo 4g is saying out of 89.6MB and my home pc is saying 89.7MB...so we'll see what's up when I get it.
YES!!! Time to OC this bad boy..
Please get on it Devs..!!!
RazoE said:
YES!!! Time to OC this bad boy..
Please get on it Devs..!!!
Click to expand...
Click to collapse
All ready on it
Sent from my Senseless Doubleshot using xda premium
That's funny.
I just received the HTC reply to my request. I'm going to play like my request was the straw for that camel's back... Your Welcome Everybody!!!
j/k. This is wonderful news though. I'm stoked
Thread locked by OP request
I sent a request to HTC regarding their timeframe for releasing the kernel source code for the ATT/Rogers One X. This is,what they said:
"I love customizing my device and I will be glad to advise you regarding the source code for the One X. HTC will typically publish on http://developer.htc.com or htcdev.com the Kernel open source code for recently released devices as soon as possible. HTC will normally publish this within 90 to 120 days. This time frame is within the requirements of the open source community."
Looks like we have a while to go gang! Fortunately we some resourceful folks here that make magic happen with available information!
Sent from my HTC One X using xda premium
90-120 days - is "as soon as possible"??? HTC, you do realize that time frame is 1/4 - 1/3 of the year, right?
IMO the strategy here is by that time a new device will be born and people would forget about old one...
This may be a stretch, but it could also be that they want to give users a time to use the device as is in order to discover any bugs that may be present and would need to be patched in a future update. No one is more adept at finding bugs than users...thousands of them.
Tell them that is a complete lie.
The HTC Sensation received the ICS source code within 15 days of its release. They got the ICS update on the 16th and they received the source code not long after.
Read what I wrote to them
http://forum.xda-developers.com/showthread.php?t=1679112
Hey Guys, we are working on the same issue in the Desire C community. I see you have plenty of custom ROMs, but let me ask if HTC has released the full source for you, and if yes how did happen, what was the process?
Thanks a lot in advance, I'm really curious about your case. Click on my signature if you want to see our email thread
And actually, we are currently sending organised emails to HTC, if you have a couple of minutes free it would be a huge help if you sent some of our templates to them.
Here are the details:
http://forum.xda-developers.com/showthread.php?p=40051652
Thank you and see you later!
neoyoli said:
Hey Guys, we are working on the same issue in the Desire C community. I see you have plenty of custom ROMs, but let me ask if HTC has released the full source for you, and if yes how did happen, what was the process?
Thanks a lot in advance, I'm really curious about your case. Click on my signature if you want to see our email thread
And actually, we are currently sending organised emails to HTC, if you have a couple of minutes free it would be a huge help if you sent some of our templates to them.
Here are the details:
http://forum.xda-developers.com/showthread.php?p=40051652
Thank you and see you later!
Click to expand...
Click to collapse
I believe we have source for all Jelly Bean bases except AT&T.
My guess is that HTC pays no attention to these petitions and letter-writing campaigns.
It's a bit more complicated in our case, since we don't have very experienced devs, and did not even know what was going on with our kernel, and we started to roll the issue up only recently, partly due to the info we got from HTC through our emails. They are more communicative now and the case got escalated, thanks to the community effort
HTC sometimes wait up to 90days(or slightly over) to release source code.
It would be an extremely rare case that after 90 days source is not released.
HTC appear to prioritize source releases based on the sales volume of the device. The more a device sells, the faster its source tends to arrive.
Also similarities in hardware to existing devices also seems to help. The newer never before seen platforms tend to take longer.
High end phones always tend to get more love.
You have source for 4.0(2.xx ROM's), what source are you waiting on?
Has you device received 4.1? If so when? Has it been 90 days yet?
Last I head Desire C will not receive Jelly Bean from HTC due to 512mb RAM. I just checked numerous of the carriers and none show updates for 2.00 ROM's, the 2.00 have source released.
You are right, we ruled out the possibility of the official JB. Although some say it would be even faster, but I'm not expert on this. What I understood so far is even if it is so, they are not doing it because it is an entry-level device. Fair enough (well, given the conditions), we can do it for ourselves.
The problem is the WiFi driver "ath6kl_sdio.ko", it fails to compile with any other ROMs then a Sense-based. It creates the folder but will be empty. However we are trying to patch it atm, and some more experienced devs joined recently.
What we still don't know is, that there might be a problem with the source of which HTC might not even aware of, since they did not test it with custom ROMs, and atm they say (in a credible, non-brush-off manner) the source is full, but escalated the case further. So we are waiting for that as well.
So things just started to cook lately. Actually if you have an experienced kernel dev, it would be a huge help if he could look into our source and tell what is going on with it:good: So that we can communicate it effectively to HTC or maybe even solve the issue directly.
https://www.change.org/p/people-xio...are_petition&utm_term=share_for_starters_page
Sign the petition guys....
nothing gonna happen by going to that site.. pretty much useless..
But a petition like this gave success to moto g4 plus for getting official oreo
If Xiaomi decides to put out kernel source, they will do it regardless of the petition or community begging. If they don't want to do it, they won't do it. Simple as that.
matcho13579 said:
If Xiaomi decides to put out kernel source, they will do it regardless of the petition or community begging. If they don't want to do it, they won't do it. Simple as that.
Click to expand...
Click to collapse
They will surely, but it might take months to release it.
Guys, let's be patient, if they released source for pretty much all their other recent devices running QCOM there is no real reason to doubt they will for this device as well, just wait, we already have stock android, so need to suffer the horrors of MIUI while we wait
matcho13579 said:
If Xiaomi decides to put out kernel source, they will do it regardless of the petition or community begging. If they don't want to do it, they won't do it. Simple as that.
Click to expand...
Click to collapse
That is not an option this time. As it is a Google device they open themselves up for a lawsuit if they don't.
Was wondering if this was gonna happen.
Also remember that the source only has to be provided upon request. Most post-it to github.com just to cut down on having to fill the request. Has anyone asked them about it?
It seems they are planning to release the kernel source within the next three months, according to this post.