When will see some custom kernels? If we have cm 10.2 ROMs thejbwe should have kernels right.
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
When will see some custom kernels? If we have cm 10.2 ROMs thejbwe should have kernels right.
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
Htc has to release the source code first. Please bug them on Twitter or HTC Dev
Sent from my HTC6500LVW using xda app-developers app
But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
coldconfession13 said:
But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
You really need to give it some time. The Verizon One is still new and locked because of yours truly. I'm just as anxious as you are but development takes time; especially with devices on VZW.
DroidOnRoids said:
You really need to give it some time. The Verizon One is still new and locked because of yours truly. I'm just as anxious as you are but development takes time; especially with devices on VZW.
Click to expand...
Click to collapse
+1 very well said.
Patience is a virtue in the Android world.
I've got one in the works
EDIT: It's not gonna be anything major or groundbreaking right now, but it'll be based on cm's and have most of the cool features on m7ul custom kernels
From what I've read the international LTE kernel source is what is being used to make custom kernels for our device. I haven't seen it implemented yet, so it would be great to see a kernel with system write protection disabled.
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
From what I've read the international LTE kernel source is what is being used to make custom kernels for our device. I haven't seen it implemented yet, so it would be great to see a kernel with system write protection disabled.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Those kernels are for AOSP. For a sense kernel, you would probably be better off waiting for kernel source to drop from HTC
sonicxml said:
Those kernels are for AOSP. For a sense kernel, you would probably be better off waiting for kernel source to drop from HTC
Click to expand...
Click to collapse
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
DroidOnRoids said:
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
maybe verizon is making htc delay on releasing kernel source to try and slow down development lol
DroidOnRoids said:
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Except HTC is legally required to release the code in a timely fashion. The code will not drop until after 4.3 is out and they usually take 2-3 months to release it. It has absolutely no bearing on an exploit or root. When the DNA got the 2.04 update, HTC took about a month to release it. AOSP kernels like CM do not rely on this. Luckily, the M7 has a nice device tree so whoever is maintaining it now (I am assuming flyhalf) does not need to modify it drastically (much much unlike the DNA). So CM wise, we seem to be fine. You will not see a custom sense kernel until the source is released.
123421342 said:
Except HTC is legally required to release the code in a timely fashion. The code will not drop until after 4.3 is out and they usually take 2-3 months to release it. It has absolutely no bearing on an exploit or root. When the DNA got the 2.04 update, HTC took about a month to release it. AOSP kernels like CM do not rely on this. Luckily, the M7 has a nice device tree so whoever is maintaining it now (I am assuming flyhalf) does not need to modify it drastically (much much unlike the DNA). So CM wise, we seem to be fine. You will not see a custom sense kernel until the source is released.
Click to expand...
Click to collapse
That never happens lol only for GE HTC One it was released the same day or something
As for kernel, it could be patched from international One but then it would be a hacky impllementation.. imo not good. Because most AOSP ROMs are based of a derivative of the CM One kernel, the CDMA Ones use this same kernel: maybe there are a few patches to get it working but most of it is just from the international AOSP kernels.
Thats why there are Verizon AOSP kernels and not sense kernels. No one has patched a sense kernel to work on Verizon yet (whether they can't or are simply waiting for proper source is irrelevant, however I would lean towards the latter)
i not???
poondog said:
That never happens lol only for GE HTC One it was released the same day or something
As for kernel, it could be patched from international One but then it would be a hacky impllementation.. imo not good. Because most AOSP ROMs are based of a derivative of the CM One kernel, the CDMA Ones use this same kernel: maybe there are a few patches to get it working but most of it is just from the international AOSP kernels.
Thats why there are Verizon AOSP kernels and not sense kernels. No one has patched a sense kernel to work on Verizon yet (whether they can't or are simply waiting for proper source is irrelevant, however I would lean towards the latter)
Click to expand...
Click to collapse
Whassup my vivo brethren...? I may try to patch said kernel to Verizon soon...no promises though.
123421342 said:
Except HTC is legally required to release the code in a timely fashion. The code will not drop until after 4.3 is out and they usually take 2-3 months to release it. It has absolutely no bearing on an exploit or root. When the DNA got the 2.04 update, HTC took about a month to release it. AOSP kernels like CM do not rely on this. Luckily, the M7 has a nice device tree so whoever is maintaining it now (I am assuming flyhalf) does not need to modify it drastically (much much unlike the DNA). So CM wise, we seem to be fine. You will not see a custom sense kernel until the source is released.
Click to expand...
Click to collapse
Yeah...But whether they actually do it or not is another thing. "Timely" isn't actually defined very concretely.
---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------
coldconfession13 said:
But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
Click to expand...
Click to collapse
The reason there is AOSP source even though there is no Verizon kernel source is because CM commonizes the kernels by related device families to minimize the amount of work that needs to go into it. There is one and only one kernel for all the M7 variants, with a couple options changed, etc, but it's the exact same source tree.
brymaster5000 said:
Whassup my vivo brethren...? I may try to patch said kernel to Verizon soon...no promises though.
Click to expand...
Click to collapse
Hathoiught i might see one of you guys here one day.. Hopefully I get my One back from repair (having huge issues with their and my carriers services) so I can start doing stuff to it
I reckon there's not much harm in waiting, and that's better for the long run anyway
Has anyone tried flashing faux123's kernel that states it works on all carriers except Sprint?
The 4.2.2 version?
brymaster5000 said:
Has anyone tried flashing faux123's kernel that states it works on all carriers except Sprint?
The 4.2.2 version?
Click to expand...
Click to collapse
If it doesnt work on sprint, a cdma carrier, why would it work for verizon?
123421342 said:
If it doesnt work on sprint, a cdma carrier, why would it work for verizon?
Click to expand...
Click to collapse
I was thinking that because it is 4GLTE (which I read was bridging the gap between CDMA and GSM...or eventually going to), it may work. We ported a kernel from the international Incredible 2 (GSM) onto the Verizon Incredible 2 (CDMA) without issues...
Just thinking out loud.
brymaster5000 said:
I was thinking that because it is 4GLTE (which I read was bridging the gap between CDMA and GSM...or eventually going to), it may work. We ported a kernel from the international Incredible 2 (GSM) onto the Verizon Incredible 2 (CDMA) without issues...
Just thinking out loud.
Click to expand...
Click to collapse
As long as there is ril support and all drivers work then it's a simple build prop tweak
Sent from my HTC6500LVW using xda app-developers app
Related
Every rom I see by that team is always a alpha version I have yet to see a fully completed rom by that team.
Sent from the official iPhone killer
Yes they do? How about cm 7?
Sent from my SPH-D710 using xda premium
aimbdd said:
Yes they do? How about cm 7?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
or CM6, CM5 etc...
A better question would be is a rom ever complete? There will always be bugs that are found that do need to be fixed just like Android in general it's never really "done" there are always updates to it that fix things.
What gingerbread rom do they have for our phone. Looking to try them out.
Sent from the official iPhone killer
blackdragon79 said:
What gingerbread rom do they have for our phone. Looking to try them out.
Sent from the official iPhone killer
Click to expand...
Click to collapse
Well you do realize that our phone is CDMA, Proprietary code is not available for some of the hardware which greatly increases the time it takes to develop our phones ports.
If you like the idea of a Complete CyanogenMod you should grab an international GSM phone preferably a stock AOSP device. You will have a "complete" rom alot faster than you ever will with a sprint device.
The OG epic only became officially supported not long ago.
blackdragon79 said:
What gingerbread rom do they have for our phone. Looking to try them out.
Sent from the official iPhone killer
Click to expand...
Click to collapse
There is no "official" GB rom from CM for this phone. Rootzwiki has an "unofficial" CM7.1/2 that's no longer supported however. We are getting "official" CM9 and the Alpha 1 is in the Dev section.
Lol wut? Is this your first android device?
nickwn88 said:
Lol wut? Is this your first android device?
Click to expand...
Click to collapse
Lol
Sent from my SPH-D710 using xda premium
cidica said:
There is no "official" GB rom from CM for this phone. Rootzwiki has an "unofficial" CM7.1/2 that's no longer supported however. We are getting "official" CM9 and the Alpha 1 is in the Dev section.
Click to expand...
Click to collapse
I was told that the Alpha 1 wasn't official.?
There are at least 3 or 4 Cyanogenmod attempts for our phone, isn't that a set team that always develops or can anyone attempt a Cyanogenmod? Don't understand how there can be multiple Cyanogenmod ROMs for our phone?
darklavalizard said:
There are at least 3 or 4 Cyanogenmod attempts for our phone, isn't that a set team that always develops or can anyone attempt a Cyanogenmod? Don't understand how there can be multiple Cyanogenmod ROMs for our phone?
Click to expand...
Click to collapse
I think you mean to say there are multiple AOSP-based (original ICS w/o Touchwiz) ROMs for our phone.
Sbrissen and Darchstar are currently working on CM9 for our phone.
T.C.P. has released AOKP, Gummy, and Codename Android for our phone.
darklavalizard said:
There are at least 3 or 4 Cyanogenmod attempts for our phone, isn't that a set team that always develops or can anyone attempt a Cyanogenmod? Don't understand how there can be multiple Cyanogenmod ROMs for our phone?
Click to expand...
Click to collapse
Anyone is free to take the CM code and build their own ROM. That's the beauty of open source. All they ask is that such derivative builds are labeled as kangs or otherwise make note that they are using CM9's codebase.
Anyone can become a member of CM if they do good work such as committing bug fixes to the project and take a role in supporting CM on a particular device
Darchstar's build should be considered the "official" CM9 build for our phone. He's part of the CM team. However, until he or others are able to build a working kernel from source for the E4GT and not use Samsung's we won't have a truly CM9 build.
blackdragon79 said:
Every rom I see by that team is always a alpha version I have yet to see a fully completed rom by that team.
Sent from the official iPhone killer
Click to expand...
Click to collapse
No rom is complete without official ice release.. they don't even have source for our phones yet for ics. Therefore it cannot be completed.. plus kudos to the person who said it will never be complete based off of bugs plus there are always ways to improve a rom regardless; of how "complete" it is.. would you want a dev to make a rom then never update it? They can't make it official until everything is working..
Sent from my SPH-D710 using XDA
Nothing is ever finished in android
Notice the carriers always pushing fixes. ICS will probably be updated within a month after official drops.
Just the nature of the beast.
Sent from my SPH-D710 using xda premium
Android has become more and more complex to develop for (both in terms of skill and computing power), and the true developers (not including people who just modify existing roms) have become more spread out across devices.
Sent from my SPH-D710 using Tapatalk
I would be willing to run logcats, test installs, and check features for alpha testing, but I am curious to learn more about whether or not HTC has released the source code on the PrimoC yet. If anyone knows...I wud appreciate the help.
Molikai1988 said:
I would be willing to run logcats, test installs, and check features for alpha testing, but I am curious to learn more about whether or not HTC has released the source code on the PrimoC yet. If anyone knows...I wud appreciate the help.
Click to expand...
Click to collapse
No, they haven't.
Sent from my HTC One V using Tapatalk 2
I am beginning to wonder if this is Virgin Mobile not letting them. If they won't release the source to the cdma but they will for the GSM then perhaps a reverse compile is possible. If the code is similar enough then using the source from the GSM as a base could yield some source.
Molikai1988 said:
I am beginning to wonder if this is Virgin Mobile not letting them. If they won't release the source to the cdma but they will for the GSM then perhaps a reverse compile is possible. If the code is similar enough then using the source from the GSM as a base could yield some source.
Click to expand...
Click to collapse
CDMA CM9 needs custom kernel for audio. That's all I known
Sent from my HTC Desire using xda premium
Lloir said:
CDMA CM9 needs custom kernel for audio. That's all I known
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
So the hardware should be close, but I see that this is true about the audio...will have to keep one eye on HTC for the source...till then I guess its NoN-sEnSe primo-c 1.1.
I don't think it would be Virgin Mobile calling the shots imo. They would lose potential sales whereas HTC will find a different carrier.
Yeah I just checked with a guy I know that works support for htc. He said its scheduled soon. So at least its soon lol. Just wish he cud say when.
Sent from my HTC One V using xda app-developers app
Molikai1988 said:
Yeah I just checked with a guy I know that works support for htc. He said its scheduled soon. So at least its soon lol. Just wish he cud say when.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
really? cause im honestly saying close to the end of august or beginning of september. This is their track record....
I also talked to them about the kernel source for CDMA/Virgin Mobile USA HTC ONE V, they do have plans to release the source however it takes longer for CDMA vs GSM, something to do with the more proprietary nature of CDMA, we've seen this cause delays with AOSP build on CDMA Nexus Devices, so it doesn't surprise me that it's taking longer to release. However in the mean time the hardware differences between GSM and CDMA variants should be minuscule (cellular data being the obvious one) so could we continue making the build without data/sound and just add those when the drivers are available so time isn't wasted on waiting for sources to be released? I would be willing to test.
MtDewFella said:
I also talked to them about the kernel source for CDMA/Virgin Mobile USA HTC ONE V, they do have plans to release the source however it takes longer for CDMA vs GSM, something to do with the more proprietary nature of CDMA, we've seen this cause delays with AOSP build on CDMA Nexus Devices, so it doesn't surprise me that it's taking longer to release. However in the mean time the hardware differences between GSM and CDMA variants should be minuscule (cellular data being the obvious one) so could we continue making the build without data/sound and just add those when the drivers are available so time isn't wasted on waiting for sources to be released? I would be willing to test.
Click to expand...
Click to collapse
I already have a thread up for CM9. I am releasing a new one today that has sound working and is on par with the GSM version status.
jmztaylor said:
I already have a thread up for CM9. I am releasing a new one today that has sound working and is on par with the GSM version status.
Click to expand...
Click to collapse
Yup just found it, like I said over there, I'll risk my phone in testing (joking, I don't actually believe your build will destroy my phone, this isn't my first beta testing rodeo) for the benefit of the Greater android community.
nearly every phone except Endeavor got the new kernel source (including evita). is that means that they stopped developing on the one x?
ereneren564 said:
nearly every phone except Endeavor got the new kernel source (including evita). is that means that they stopped developing on the one x?
Click to expand...
Click to collapse
i think with new big update frmo htc we will get newer kernel
One-X-master said:
i think with new big update frmo htc we will get newer kernel
Click to expand...
Click to collapse
you see since that they released it for one s too i cant be really sure
ereneren564 said:
you see since that they released it for one s too i cant be really sure
Click to expand...
Click to collapse
It also depends on nvidia...we have a tegra inside and the one s snapdragon...and with every big update a newer kernel came out...lol
Gesendet von meinem HTC One X mit Tapatalk 2
ereneren564 said:
nearly every phone except Endeavor got the new kernel source (including evita). is that means that they stopped developing on the one x?
Click to expand...
Click to collapse
from the first day they sell one x, one x's kernel version is older than other devices
One-X-master is right.
It was related to nVidia and Qualcomm.
Qualcomm is faster than others, not really wanted to write much regarding this.
I believed someone here on xda can write essays on the topic.
One-X-master said:
It also depends on nvidia...we have a tegra inside and the one s snapdragon...and with every big update a newer kernel came out...lol
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
well linus Torvalds said **** you nVidia read here http://arstechnica.com/information-technology/2012/06/linus-torvalds-says-f-k-you-to-nvidia/ having said that it also depends on phone manufacturer Nexus 4 has most latest kernel.
smokin901 said:
well linus Torvalds said **** you nVidia read here http://arstechnica.com/information-technology/2012/06/linus-torvalds-says-f-k-you-to-nvidia/ having said that it also depends on phone manufacturer Nexus 4 has most latest kernel.
Click to expand...
Click to collapse
Nexus 4 has a qualcomm/snapdragon processor....therefore it also has More newer kernel releases then one x...and it shouldn't be a problem...theywill release if its really necessary ....
Sent from my HTC One X using xda app-developers app
One-X-master said:
Nexus 4 has a qualcomm/snapdragon processor....therefore it also has More newer kernel releases then one x...and it shouldn't be a problem...theywill release if its really necessary ....
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No i meant more newer version than even qualcomm based HTC devices
smokin901 said:
No i meant more newer version than even qualcomm based HTC devices
Click to expand...
Click to collapse
Ah okay yes...hm ah I don't care about that ...
Sent from my HTC One X using xda app-developers app
smokin901 said:
No i meant more newer version than even qualcomm based HTC devices
Click to expand...
Click to collapse
Uh, HTC One uses 3.4.10, Nexus 4 uses 3.4.0. I don't see how Nexus 4 has a newer kernel
pandaball said:
Uh, HTC One uses 3.4.10, Nexus 4 uses 3.4.0. I don't see how Nexus 4 has a newer kernel
Click to expand...
Click to collapse
I my memory serves me correctly one of my colleague's N4 had 3.6 kernel
smokin901 said:
I my memory serves me correctly one of my colleague's N4 had 3.6 kernel
Click to expand...
Click to collapse
That's probably a custom kernel. I know the stock N4 kernel is 3.4.0 for 4.2.2
Anyway, we've digressed from the topic at hand (not that there was much to discuss about to begin with )
Nvidia is the problem. The Nexus 7 with Tegra 3 is also still @ 3.1.x :/
theliquid said:
Nvidia is the problem. The Nexus 7 with Tegra 3 is also still @ 3.1.x :/
Click to expand...
Click to collapse
Nah. Google never updates the kernel after a device has been released. It has always been like that for Nexus devices.
pandaball said:
Nah. Google never updates the kernel after a device has been released. It has always been like that for Nexus devices.
Click to expand...
Click to collapse
Lol
Look at Third party Linux OS
They have 3.8 now lol
Its all Google's and OEM reluctantacy
Sent from my HTC One using xda premium
razer1224 said:
Lol
Look at Third party Linux OS
They have 3.8 now lol
Its all Google's and OEM reluctantacy
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Your point being...?
As far as the Linux kernel goes, while they merged some patches to allow for Android to run on the mainline Linux branch, the Android kernel is more or less a fork of the Linux kernel to enable full compatibility with Android and ARM. Its not exactly the easiest thing to do, so of course the Android kernel is behind the mainline Linux kernel. Besides, whatever kernel 4.3 runs on will be the kernel that OEMs use, since the kernel base is already there and it saves OEMs time. Mainline Linux moves forward much faster than Android's yearly releases so you can't expect the Android kernel to keep up with the mainline kernel.
Sent from my C6603 using Tapatalk 4 Beta
pandaball said:
Your point being...?
As far as the Linux kernel goes, while they merged some patches to allow for Android to run on the mainline Linux branch, the Android kernel is more or less a fork of the Linux kernel to enable full compatibility with Android and ARM. Its not exactly the easiest thing to do, so of course the Android kernel is behind the mainline Linux kernel. Besides, whatever kernel 4.3 runs on will be the kernel that OEMs use, since the kernel base is already there and it saves OEMs time. Mainline Linux moves forward much faster than Android's yearly releases so you can't expect the Android kernel to keep up with the mainline kernel.
Sent from my C6603 using Tapatalk 4 Beta
Click to expand...
Click to collapse
i know but still
atleast 3.6 should be suffice on 2013
razer1224 said:
i know but still
atleast 3.6 should be suffice on 2013
Click to expand...
Click to collapse
Given that there hasn't been any Android update out this year, no one will move beyond 3.4 until Google does so. What features are there in 3.6 that are absolutely necessary anyway? It seems to me like you want an update to 3.6 because it has a larger number
pandaball said:
Given that there hasn't been any Android update out this year, no one will move beyond 3.4 until Google does so. What features are there in 3.6 that are absolutely necessary anyway? It seems to me like you want an update to 3.6 because it has a larger number
Click to expand...
Click to collapse
Yep I also don't get it why always newer if its not always better
Gesendet von meinem HTC One X mit Tapatalk 2
even the defy i had now have a cm11 build(pretty good even! they have 250+ ram free most stuff works)
and we dont get it on a great device such as out hox?
what is the status of trying and running the 4.4?
is the devices status that bad when it comes to new versions?(the defy dont even have an open bootloader, at all!)
yossi2010 said:
even the defy i had now have a cm11 build(pretty good even! they have 250+ ram free most stuff works)
and we dont get it on a great device such as out hox?
what is the status of trying and running the 4.4?
is the devices status that bad when it comes to new versions?(the defy dont even have an open bootloader, at all!)
Click to expand...
Click to collapse
Well... Its been said a thousand times read through the general threads
Sent from my EndeavorU using Tapatalk 4
What always worried me about HoX development is that the hardware is very similar to the 3G nexus 7 2012 which gets its source code released,
i know there must be different things, different brand ram, the nexus 7 has a slower version of the Tegra 3, not sure if the radio, bluetooth and sensor chips are the same,
and the screen controller is clearly different.
Even the evita now has a cynaogenmod 11 build out
Sent from my HTC One X using xda app-developers app
Tegra . Tegra......
Envoyé de mon HTC One X en utilisant Tapatalk
xeloni said:
Tegra . Tegra......
Envoyé de mon HTC One X en utilisant Tapatalk
Click to expand...
Click to collapse
... Amazing really. A couple posts above someone mentioned the nexus 7 has 4.4. Now suddenly the tegra chipset is the problem again. It is htc not releasing sources for **** sake people. Its no wonder we dont achieve anything as a whole.
We have thomy a great dev but his hands are tied without sources. We would be rockin cm11 for sure by now
Sent from my EndeavorU using Tapatalk 4
2011 Sony Ericsson Xperia Devices Taste Android 4.4 KitKat
Also xperia devices not have code from sony but the developers have only complicated by the codes and are 4.4 ///I'm with 3.8.0 kernel jb !!!
It not just kernel source I think...because it seem LG optimus 4x hd where have same chipset as us already have kit kat. Please let our dev focus on bringing stable 4.3 first.
Sent from my EndeavorU using Tapatalk
audahadi said:
It not just kernel source I think...because it seem LG optimus 4x hd where have same chipset as us already have kit kat. Please let our dev focus on bringing stable 4.3 first.
Sent from my EndeavorU using Tapatalk
Click to expand...
Click to collapse
We don't need 4.3 the changes between 4.2.2.and 4.3 is to small we need the new 4.4 directly
One X seem be dead. Miui discontinued support for porting HOX on official site of Miui
Why not make a petition to get HTC releasing the kernel source code? I've already tell them on twitter to stop violating GPL
Or we will go with the old kernels if we want cm11. This could also happen
Sent from my EndeavorU using Tapatalk 4
Yeah, you're right, but this doesn't make any sense.
HTC have to release the source so the dev can work on it!
Damn you HTC, I'm glad you're failing.
and313 said:
... Amazing really. A couple posts above someone mentioned the nexus 7 has 4.4. Now suddenly the tegra chipset is the problem again. It is htc not releasing sources for **** sake people. Its no wonder we dont achieve anything as a whole.
We have thomy a great dev but his hands are tied without sources. We would be rockin cm11 for sure by now
Sent from my EndeavorU using Tapatalk 4
Click to expand...
Click to collapse
Have you done ROM development on a new android release for a device?
Sent from my Nexus 5 using Tapatalk
Lloir said:
Have you done ROM development on a new android release for a device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No. Im just saying what the devs said. Waiting for sources
Sent from my EndeavorU using Tapatalk 4
and313 said:
No. Im just saying what the devs said. Waiting for sources
Sent from my EndeavorU using Tapatalk 4
Click to expand...
Click to collapse
The Motorola defy doesn't even have an open bootloader they use a software trick called 2ndinit to boot into a custom recovery.
I bet they don't have kernel source either yet they have come from 2.1 until 4.4 with a mere gingerbread base.
How comes can't we do the same trick?
yossi2010 said:
The Motorola defy doesn't even have an open bootloader they use a software trick called 2ndinit to boot into a custom recovery.
I bet they don't have kernel source either yet they have come from 2.1 until 4.4 with a mere gingerbread base.
How comes can't we do the same trick?
Click to expand...
Click to collapse
Because as said devs are waiting for sources which means they want to use the new one because they are more updated as the old ones which means more customization. Something in that way. Nothing stays in the way using a old kernel though. But when new sources are released they need to port it again. Something in that way again
So nobody wants to work for free double time... Which is normal i guess
Sent from my EndeavorU using Tapatalk 4
Some time ago I read that HTC got no other choice besides releasing kernel source because of some legal stuff.
Is this true? If it is it's just a matter of time and we will definitely get the new kernel source and 4.4
Also we could use this argument to force HTC to release the source faster.
We have passed the land of arguments very long ago and now we are in the land of get a lawyer and a looot of money or forget about it
Sent from my EndeavorU using Tapatalk 4
Maybe you guys should flood HTC's social media channels with kernel source requests.
It's really rediculous they haven't release 4.2.2 kernel sources yet.
I know OEM's really dislike negative attention via social media so that's probably the best way.
How does HTC compare to Samsung?
Is *everything* HTC produces available to devs? Or does HTC refuse to release proprietary source code like Samsung does?
Will 'unofficial' builds be able to be rated as stable?
Sent via my Markox/Gustavo_s powered KitKatted S2
HTC does release source and stable builds of aosp are typically achieved. The main thing you have to worry about is when HTC decides end of update lifecycle. That's when stable releases for aosp base becomes really slow.
Since there's a gpe version, I'm hoping the update lifecycle will be longer than previous HTC phones.
I owned an Evo 3d and one xl previously.
Sent from my HTC One_M8 using XDA Free mobile app
Thanks @exad
How quickly does that happen?
What sort of update life cycle can the M8 expect?
Sent via my Markox/Gustavo_s powered KitKatted S2
Hmmm a year and a halfish? As for what we can expect for the m8.. I am without a crystal ball.
Sent from my HTC One_M8 using XDA Free mobile app
exad said:
Hmmm a year and a halfish? As for what we can expect for the m8.. I am without a crystal ball.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Lol....I wasn't expecting an exact answer, just wondered if HTC had a policy of updating for a specified set duration irrespective of model.....
Sent via my Markox/Gustavo_s powered KitKatted S2
Not that I know of.
Sent from my HTC One_M8 using XDA Free mobile app
keithross39 said:
Lol....I wasn't expecting an exact answer, just wondered if HTC had a policy of updating for a specified set duration irrespective of model.....
Sent via my Markox/Gustavo_s powered KitKatted S2
Click to expand...
Click to collapse
They're committed to two years on major Android updates for North American phones.
The ever necessary source so that the naysayers are kept at bay: http://www.reddit.com/r/Android/comments/1xxjfx/hi_were_the_htc_usa_product_team_amaa/
jdk2 said:
They're committed to two years on major Android updates for North American phones.
The ever necessary source so that the naysayers are kept at bay: http://www.reddit.com/r/Android/comments/1xxjfx/hi_were_the_htc_usa_product_team_amaa/
Click to expand...
Click to collapse
That's not so bad.......
The average phone contract here in the UK is 2 years........
By the time my current contract is up and I get the M8, the end of my new 2 year contract will put me about 6 months past that 2 year update life cycle........
I can live with that.......
Sent via my Markox/Gustavo_s powered KitKatted S2
keithross39 said:
How does HTC compare to Samsung?
Is *everything* HTC produces available to devs? Or does HTC refuse to release proprietary source code like Samsung does?
Will 'unofficial' builds be able to be rated as stable?
Sent via my Markox/Gustavo_s powered KitKatted S2
Click to expand...
Click to collapse
well it IS proprietary...meaning it isn't open source so they don't have to release it.
and yes, they refuse to release sources for Sense and many of their Sense applications.
Hellscythe said:
well it IS proprietary...meaning it isn't open source so they don't have to release it.
and yes, they refuse to release sources for Sense and many of their Sense applications.
Click to expand...
Click to collapse
THAT I can understand.....it'll be the same for any manufacturer.......
But then Sense, Touchwiz and the like isn't strictly needed for AOSP.
What I was asking about (and probably should have been clearer about) was device source code......
Case in point......
Samsung and Exynos.......source code needed to make the device function correctly irrespective of what is running on it.....
Sent from my GT-I9100 using XDA Free mobile app
keithross39 said:
THAT I can understand.....it'll be the same for any manufacturer.......
But then Sense, Touchwiz and the like isn't strictly needed for AOSP.
What I was asking about (and probably should have been clearer about) was device source code......
Case in point......
Samsung and Exynos.......source code needed to make the device function correctly irrespective of what is running on it.....
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I understood what you meant and answered you. They do for all versions until support for the device ends
Sent from my HTC One_M8 using XDA Free mobile app
keithross39 said:
How does HTC compare to Samsung?
Is *everything* HTC produces available to devs? Or does HTC refuse to release proprietary source code like Samsung does?
Will 'unofficial' builds be able to be rated as stable?
Sent via my Markox/Gustavo_s powered KitKatted S2
Click to expand...
Click to collapse
HTC refuses to release proprietary code. This has always been a problem with HTC and will likely continue to be one. Don't believe me ask kernel developer @flar2. The first source code they released not too long had a fair amount of code lopped off of it. The only truly open source is AOSP. Even the Nexus line diverges a bit from true open source as they have closed source certain apps like google calendar, maps and keyboard. But these can at least be downloaded from play store.
So is HTC still perceived as the least (or so I have read) 'dev friendly' manufacturer?
Sent from my rooted debloated thingy
keithross39 said:
So is HTC still perceived as the least (or so I have read) 'dev friendly' manufacturer?
Sent from my rooted debloated thingy
Click to expand...
Click to collapse
There definitely up there, I think Samsung especially the exynos version is worse. At the least we have access to Code Aurora (Qualcomm source code) and they are very good about releasing source.
jlevy73 said:
There definitely up there, I think Samsung especially the exynos version is worse. At the least we have access to Code Aurora (Qualcomm source code) and they are very good about releasing source.
Click to expand...
Click to collapse
EDIT: Sorry @jlevy73 - I quoted the wrong person.
They all have things that include IP that is closed, including Google Nexus, which is also different from AOSP.
Some of the things aren't even HTC related, there are proprietary drivers & such that they themselves license from Qualcomm, & other component manufacturers. I would say that they are much more developer friendly than most of the OEM's.
Well, none of that is going to affect my decision to get the M8.......
I just want to be able to proceed with all the relevant information......
So long as I can.....
A) root it
B) install some root access apps
C) debloat (if necessary)
D) *maybe* flash a custom rom
(In that order, with D being a possibility rather than a certainty)
Sent from my rooted debloated thingy