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
Sent from my HTC One VZW using Tapatalk 4
Htc has to release the source code first. Please bug them on Twitter or HTC DevWhen 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
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.But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
+1 very well 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.
Those kernels are for AOSP. For a sense kernel, you would probably be better off waiting for kernel source to drop from HTCFrom 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
Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lolThose kernels are for AOSP. For a sense kernel, you would probably be better off waiting for kernel source to drop from HTC
maybe verizon is making htc delay on releasing kernel source to try and slow down development lolUnfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
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.Unfortunately, waiting on HTC to drop kernel source is like waiting on a Verizon OTA lol
Sent from my HTC6500LVW using Tapatalk 4
That never happens lol only for GE HTC One it was released the same day or somethingExcept 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.
Whassup my vivo brethren...? I may try to patch said kernel to Verizon soon...no promises though.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)
Yeah...But whether they actually do it or not is another thing. "Timely" isn't actually defined very concretely.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.
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.But isn't cm 10.2 a custom kernel
Sent from my HTC One VZW using Tapatalk 4
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 itWhassup my vivo brethren...? I may try to patch said kernel to Verizon soon...no promises though.
If it doesnt work on sprint, a cdma carrier, why would it work for verizon?Has anyone tried flashing faux123's kernel that states it works on all carriers except Sprint?
The 4.2.2 version?
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...If it doesnt work on sprint, a cdma carrier, why would it work for verizon?
As long as there is ril support and all drivers work then it's a simple build prop tweakI 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.