Develop Bugs

CM9 Alpha testing for the PrimoC/CDMA...?

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.

Image sense chip

what other camera app uses the image sense chip in our HOX

only the sense one uses it as far as I know, as the drivers to use it are closed source.

are there news about the chip?
the new focal application of cyanogenmod work whit this chip?

None. HTC are a pain in the arse
Sent from my HTC One X using xda app-developers app

danyshotbang said:
what other camera app uses the image sense chip in our HOX
Click to expand...
Click to collapse
Drefsab said:
only the sense one uses it as far as I know, as the drivers to use it are closed source.
Click to expand...
Click to collapse
The HTC Imagechip is used exclusive by the Sense camera, which is only compatible within the Sense framework.
There is NO camera for AOSP that makes use of it in any fashion.

Tigerlight said:
The HTC Imagechip is used exclusive by the Sense camera, which is only compatible within the Sense framework.
There is NO camera for AOSP that makes use of it in any fashion.
Click to expand...
Click to collapse
Ok then my next phone will be the nexus.
if a company makes chips without source code then it is a thief

MT88 said:
Ok then my next phone will be the nexus.
if a company makes chips without source code then it is a thief
Click to expand...
Click to collapse
Only android is open source, sense is HTC's work and is not released under the open source licence.
They haven't stole anything, what they are doing is stopping people from steal their work.
Sent from my HTC One X using xda app-developers app

treebill said:
Only android is open source, sense is HTC's work and is not released under the open source licence.
They haven't stole anything, what they are doing is stopping people from steal their work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Much like ALL of the SoC developers who actually build Android for our devices using closed-source, obfuscated hardware interfaces.
Qualcomm is closed-source. NVIDIA is closed-source. Samsung release parts of it, I believe.
Every company protects their work in one form or another. Can't say I have a problem with it.

[Q] Alternatives? (CyanogenMod dropping Exynos support)

So, I was all excited to get a Note 2, but then I heard about CyanogenMod being unlikely to support new Exynos devices: http://codeworkx.de/wordpress/
So with that in mind... does anyone have a competing phablet to suggest?

Nothing going on in the stickied thread for whose gonna develop for it. Any ideas?
Sent from my XT875 using XDA Premium App

That seems awfully silly to drop such an anticipated world wide device. Maybe he can't meat the demand of both SG3, and Note 2?

adampa1006 said:
Nothing going on in the stickied thread for whose gonna develop for it. Any ideas?
Sent from my XT875 using XDA Premium App
Click to expand...
Click to collapse
We are still waiting for us release date to even be announced so some devs may not even be that worried about notifying me until they get to see the device hands on.
Sent from my Rezound using xda app-developers app

StelardActek said:
So, I was all excited to get a Note 2, but then I heard about CyanogenMod being unlikely to support new Exynos devices: http://codeworkx.de/wordpress/
So with that in mind... does anyone have a competing phablet to suggest?
Click to expand...
Click to collapse
You do know that codeworkx isn't the only developer for CyanogenMod or for Samsung devices. Him dropping support for Exynos devices isn't the end of the world. So what if he left, that's his personal choice & I understand why & completely support him but not everyone shares his views of dropping support for Exynos devices because devices like the S & Note series are very popular & its just a matter of time before some developer get his hand on the device & CyanogenMod will be developed for it. This is just needless panic.
Sent from my GT-I9100 using Tapatalk 2

The HTC One X5 looks good, but no clue on when it'll come out...
And yes #illidan, I realise that another developer may step up, and I do hope that happens. But from the sounds of things, it's not just codeworkx that is dropping Samsung support:
Entropy512 said:
Not likely to happen. If CM comes to the Note 2, it will only be if a new maintainer steps up.
Most of the current Exynos maintainer team (myself, espenfjo, codeworkx) and others have all decided that our current devices will be our last non-Nexus Exynos devices. I'm not sure about xplodwild, but I have a feeling he's highly unlikely to take up another Haxxinos with the rest of us gone and given his prior experiences with it.
If Samsung changes their attitude towards developers, this might change, but their attitude lately (zero documentation, zero platform source code, a trend towards bootloader locking - Only the Verizon S3 has a locked bootloader now, but Samsung has had the infrastructure in place since the S2 and they are constantly adding more checks) has led to the current Exynos maintainer team deciding that enough is enough. I don't think any of us are going to do anything to make Samsung's Exynos devices more attractive to any particular market segment until they provide assistance (in the form of technical documentation and source code) in return. I don't know about the others, but if they offer me a free device I'll say no - I refuse to participate in a PR stunt like the I9100 donations were.
Pretty much the only way I'll go back is if I see reference platform source that is up to the same standards as CAF and omapzoom, or they actually start providing real documentation and source code for the devices I'm currently working with.
Click to expand...
Click to collapse

StelardActek said:
The HTC One X5 looks good, but no clue on when it'll come out...
And yes #illidan, I realise that another developer may step up, and I do hope that happens. But from the sounds of things, it's not just codeworkx that is dropping Samsung support:
Click to expand...
Click to collapse
Yes I'm well aware of the entire so called Exynos development team giving up because of Samsung's retarded ways but as of now I believe it's a 50-50 gamble for device support. Maybe a new maintainer steps up to the batting plate or an old one does (highly unlikely). It's basically up to you & seeing as the Note is the only choice for now if your looking for a phablet. I still believe that the device will receive support.
Sent from my GT-I9100 using Tapatalk 2

A popular device like the Note II will surely get CM. But a point worth considering is the lack of help being provided by Samsung regarding the Exynos processor. So, in the future , development may slow down or there may be loss of particular functionality due to the lack of code or compatible blobs from Samsung for the Exynos.
Of course, there are many talented devs that gonna work on the Note II, but the Team Hacksung not supporting this is definitely a big blow, as they have shown the awesome work they can do with Samsung devices as well as the fact that they have tremendous experience on Samsung devices.

Hrm, this may not be concerning for the veteran android user,but as I plan(ned?) this to be my first android device, it makes me wonder if I should wait and see if there is support for it. I can't a stock anything, let a lone a phone. And unfortunatly this is the only android device I'm really looking forward to.

I've heard some chit chatter as well, as far as development / support not going to be strong but its not going to sway me from buying this phone.. It's still going to be awesome.. Even if its just stock rooted to get rid of system things you don't need
-TeaM VeNuM Like A Boss

I have a developer question, what company is actually giving the developers what they want? HTC? I know Motorola hasn't been that developer friendly ( at least on Verizon I know its better on other carriers). Cm10 will be on the note 2. If my Bionic is getting JB cm10 then for sure the Note 2 will
Sent from my XT875 using XDA Premium App

adampa1006 said:
I have a developer question, what company is actually giving the developers what they want? HTC? I know Motorola hasn't been that developer friendly ( at least on Verizon I know its better on other carriers). Cm10 will be on the note 2. If my Bionic is getting JB cm10 then for sure the Note 2 will
Sent from my XT875 using XDA Premium App
Click to expand...
Click to collapse
The nexus line is the way to go
Sent from my Galaxy Nexus using xda premium

adampa1006 said:
I have a developer question, what company is actually giving the developers what they want? HTC? I know Motorola hasn't been that developer friendly ( at least on Verizon I know its better on other carriers). Cm10 will be on the note 2. If my Bionic is getting JB cm10 then for sure the Note 2 will
Sent from my XT875 using XDA Premium App
Click to expand...
Click to collapse
Apparently if has more to do with the processor. The Snapdragon, TI OMAP, NVidia etc are more forthcoming with code for CM. Sammy however is not, since exynos is a proprietary chip (aka apple).
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

fear not
erick161 said:
Apparently if has more to do with the processor. The Snapdragon, TI OMAP, NVidia etc are more forthcoming with code for CM. Sammy however is not, since exynos is a proprietary chip (aka apple).
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I believe that the Exynos CPU in the Galaxy Note 2 is exactly the same as the CPU in the Galaxy S III, Just higher Clocked. And the International Galaxy S III has Cyanogenmod Already, So fear not it will be a easier port. Correct me if I'm wrong

johnwazhere said:
I believe that the Exynos CPU in the Galaxy Note 2 is exactly the same as the CPU in the Galaxy S III, Just higher Clocked. And the International Galaxy S III has Cyanogenmod Already, So fear not it will be a easier port. Correct me if I'm wrong
Click to expand...
Click to collapse
I would assume so, but not sure. Personally, I won't stray away from a stock base. I want those features touted by Samsung. That's why I'm upgrading.
I'm not sure however, how well CM10 runs on the SGS3...and according to what I've read, its not a very good port.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

Custom kernel

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

everyone has 4.4 but us you've gotta be kidding me...

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.