[ROM][03.23.13] CyanogenMod 10 on HTC DNA; Audio WIP)

idkwhothatis123 · Feb 20, 2013

Re: [ROM] CyanogenMod 10.0/10.1 on HTC DNA [Updated: 02.18.13]

Bigandrewgold said:
What, I only got access to moon pie. Where are you getting quiche from?

Sent from my HTC6435LVW using xda app-developers app

Its emulator only. Its pretty sweet. It even tickles your balls for you.

Sent from my HTC6435LVW using Tapatalk HD

drewX2 · Feb 20, 2013

Almost done updating Bionic files. This should fix a majority of random errors and help with porting to any rom.

As I might have mentioned prior and according to some of the HTC/CM devs I spoke to before, there is no current interest to port to our phone yet because our build is very different; one reason being the kernel as we are 3.4+ and they are 3.0 ish I think. I was told they are pushing towards 3.4 asap tho. That and our trees screw up a bunch of stuff regarding common files. I can only speak to what I've been told, but nonetheless, we push on!

aFancyTickler · Feb 20, 2013

drewX2 said:
Almost done updating Bionic files. This should fix a majority of random errors and help with porting to any rom.

As I might have mentioned prior and according to some of the HTC/CM devs I spoke to before, there is no current interest to port to our phone yet because our build is very different; one reason being the kernel as we are 3.4+ and they are 3.0 ish I think. I was told they are pushing towards 3.4 asap tho. That and our trees screw up a bunch of stuff regarding common files. I can only speak to what I've been told, but nonetheless, we push on!

so its possible we might see dna officially supported by cm ? and what exactly do you mean by bionic files if you dont mind me asking

drewX2 · Feb 20, 2013

FeaR_x_KhAoS said:
so its possible we might see dna officially supported by cm ? and what exactly do you mean by bionic files if you dont mind me asking

http://en.wikipedia.org/wiki/Bionic_(software)

Bionic needs to be updated with proper kernel headers for use when running programs. I did not update them with CM10, which surprised me considering it ran rather stable. Nonetheless, CM10.1 is a whole other beast and boots to a screwed up screen atm. It could be other things, but I need to update this anyhow so everything else will work properly.

I guess a basic way of thinking of it is imagine you have a toolbox with certain tools available. It works well for most projects, but sometimes you buy a slightly modified version of a tool for a new project. The old tool might be able to work still (and maybe fairly well if no changes, or subtle), however it may not even work at all. You could also think of it as a floorplan with room layouts and details like the location of outlets. In CM10, that toolbox is setup for a completely different phone and there are slight differences throughout. Best analogy I could come up with and I hope it helps.

chad0989 · Feb 20, 2013

FeaR_x_KhAoS said:
so its possible we might see dna officially supported by cm ? and what exactly do you mean by bionic files if you dont mind me asking

Official support doesn't really mean anything significant. It just means that someone who wants to be maintainer cleans everything up the way they want it and submits the device tree and any other necessary commits that won't break other devices.

I'd also like to point out that s-off really isn't all that exciting. While its nice to have, it makes it dangerously easy to brick, especially if you're developing. Honestly HTC dev unlock is great IMO, you can develop as much as you want and you're almost brick proof. Now if there wasn't already the CID hack, s-off would be the greatest thing ever.

A third note is that I really don't think the phone is going to be hard to dev for. S4s are all the rage right now and have all the support and source we can hope for since the nexus 4 uses the same platform.

aFancyTickler · Feb 20, 2013

drewX2 said:
http://en.wikipedia.org/wiki/Bionic_(software)

Bionic needs to be updated with proper kernel headers for use when running programs. I did not update them with CM10, which surprised me considering it ran rather stable. Nonetheless, CM10.1 is a whole other beast and boots to a screwed up screen atm. It could be other things, but I need to update this anyhow so everything else will work properly.

I guess a basic way of thinking of it is imagine you have a toolbox with certain tools available. It works well for most projects, but sometimes you buy a slightly modified version of a tool for a new project. The old tool might be able to work still (and maybe fairly well if no changes, or subtle), however it may not even work at all. You could also think of it as a floorplan with room layouts and details like the location of outlets. In CM10, that toolbox is setup for a completely different phone and there are slight differences throughout. Best analogy I could come up with and I hope it helps.

Thanks for the link, and i understand clearly now and that analogy was a perfect way to put it.

chad0989 said:
Official support doesn't really mean anything significant. It just means that someone who wants to be maintainer cleans everything up the way they want it and submits the device tree and any other necessary commits that won't break other devices.

I'd also like to point out that s-off really isn't all that exciting. While its nice to have, it makes it dangerously easy to brick, especially if you're developing. Honestly HTC dev unlock is great IMO, you can develop as much as you want and you're almost brick proof. Now if there wasn't already the CID hack, s-off would be the greatest thing ever.

A third note is that I really don't think the phone is going to be hard to dev for. S4s are all the rage right now and have all the support and source we can hope for since the nexus 4 uses the same platform.

ohhh , well i think nightlies are quite significant. something new to flash daily

chad0989 · Feb 20, 2013

FeaR_x_KhAoS said:
Thanks for the link, and i understand clearly now and that analogy was a perfect way to put it.

ohhh , well i think nightlies are quite significant. something new to flash daily

Anyone can build nightlies. Once there's a solid device tree with everything working there will be dozens of people building more AOSP ROMs than you could ever hope for.

drewX2 · Feb 20, 2013

Example for code differences: can anyone spot a potential problem?

Correct

Code:

#ifndef _ARCH_ARM_MACH_MSM_MDM_IOCTLS_H
#define _ARXH_ARM_MACH_MSM_MDM_IOCTLS_H

#define MODEM_ERRMSG_LEN	256			/* HTC added */

#define CHARM_CODE		0xCC
#define WAKE_CHARM		_IO(CHARM_CODE, 1)
#define RESET_CHARM		_IO(CHARM_CODE, 2)
#define CHECK_FOR_BOOT		_IOR(CHARM_CODE, 3, int)
#define WAIT_FOR_BOOT		_IO(CHARM_CODE, 4)
#define NORMAL_BOOT_DONE	_IOW(CHARM_CODE, 5, int)
#define RAM_DUMP_DONE		_IOW(CHARM_CODE, 6, int)
#define WAIT_FOR_RESTART	_IOR(CHARM_CODE, 7, int)
[B]
#define GET_MFG_MODE   	_IO(CHARM_CODE, 94)     /* HTC added */
#define GET_RADIO_FLAG   	_IO(CHARM_CODE, 95)     /* HTC added */
#define SET_MODEM_ERRMSG	_IOW(CHARM_CODE, 96, char[MODEM_ERRMSG_LEN])	/* HTC added */
#define EFS_SYNC_DONE		_IO(CHARM_CODE, 99)	/* HTC added */
#define NV_WRITE_DONE		_IO(CHARM_CODE, 100)	/* HTC added */[/B]

enum charm_boot_type {
	CHARM_NORMAL_BOOT = 0,
	CHARM_RAM_DUMPS,
};

#endif

Wrong in CM10.1 build.

Code:

#ifndef _ARCH_ARM_MACH_MSM_MDM_IOCTLS_H
#define _ARXH_ARM_MACH_MSM_MDM_IOCTLS_H


#define CHARM_CODE		0xCC
#define WAKE_CHARM		_IO(CHARM_CODE, 1)
#define RESET_CHARM		_IO(CHARM_CODE, 2)
#define CHECK_FOR_BOOT		_IOR(CHARM_CODE, 3, int)
#define WAIT_FOR_BOOT		_IO(CHARM_CODE, 4)
#define NORMAL_BOOT_DONE	_IOW(CHARM_CODE, 5, int)
#define RAM_DUMP_DONE		_IOW(CHARM_CODE, 6, int)
#define WAIT_FOR_RESTART	_IOR(CHARM_CODE, 7, int)
#define GET_DLOAD_STATUS	_IOR(CHARM_CODE, 8, int)

enum charm_boot_type {
	CHARM_NORMAL_BOOT = 0,
	CHARM_RAM_DUMPS,
};

#endif

aFancyTickler · Feb 20, 2013

chad0989 said:
Anyone can build nightlies. Once there's a solid device tree with everything working there will be dozens of people building more AOSP ROMs than you could ever hope for.

Ohh ok i wasnt aware of that lol and i hope for alot of Aosp . this phone looks sick and runs sick with cm so far

skynet11 · Feb 20, 2013

Re: [ROM] CyanogenMod 10.0/10.1 on HTC DNA [Updated: 02.18.13]

idkwhothatis123 said:
Respect is fine. But to find answers you gotta read. This is the 1746391728629479 time that's been asked in some fashion and probably the 1746391728629472 time its been answered.

Sent from my HTC6435LVW using Tapatalk HD

I think you're off by 11 or so

---------- Post added at 11:31 PM ---------- Previous post was at 10:48 PM ----------

To be honest, the progress on this device is impressive. Major roadblocks thrown up by Verizon and HTC have been overcome very early in the device's life cycle.

I think the main reason why people first got the idea that achieving S-Off somehow opens the floodgates to AOSP is that some well-regarded developers reportedly refused to develop for S-On devices, which led many users to speculate that S-On somehow presents a technical hurdle to running AOSP ROMs (it doesn't).

As Drewx2 and many others have said, the biggest hurdle to getting functional AOSP on the DNA is the RIL, and it seems the biggest obstacle to getting official CM support is that our kernel is so far ahead of theirs

.

Frankly, while official support is nice, you can still have a rewarding AOSP experience with unofficial builds. I haven't had an official build of any kind on my Galaxy Nexus or my Nexus 7 in months (I think the Chicago Bears had a chance to win the NFC North division the last time I ran an official build

).

Also, I wish XDA's forum software would quit merging consecutive posts by the same user all the time :banghead:

EmericanX · Feb 20, 2013

Re: [ROM] CyanogenMod 10.0/10.1 on HTC DNA [Updated: 02.18.13]

drewX2 said:

Example for code differences: can anyone spot a potential problem?

Correct

Code:

#ifndef _ARCH_ARM_MACH_MSM_MDM_IOCTLS_H
#define _ARXH_ARM_MACH_MSM_MDM_IOCTLS_H

#define MODEM_ERRMSG_LEN256/* HTC added */

#define CHARM_CODE0xCC
#define WAKE_CHARM_IO(CHARM_CODE, 1)
#define RESET_CHARM_IO(CHARM_CODE, 2)
#define CHECK_FOR_BOOT_IOR(CHARM_CODE, 3, int)
#define WAIT_FOR_BOOT_IO(CHARM_CODE, 4)
#define NORMAL_BOOT_DONE_IOW(CHARM_CODE, 5, int)
#define RAM_DUMP_DONE_IOW(CHARM_CODE, 6, int)
#define WAIT_FOR_RESTART_IOR(CHARM_CODE, 7, int)
[B]
#define GET_MFG_MODE   _IO(CHARM_CODE, 94)     /* HTC added */
#define GET_RADIO_FLAG   _IO(CHARM_CODE, 95)     /* HTC added */
#define SET_MODEM_ERRMSG_IOW(CHARM_CODE, 96, char[MODEM_ERRMSG_LEN])/* HTC added */
#define EFS_SYNC_DONE_IO(CHARM_CODE, 99)/* HTC added */
#define NV_WRITE_DONE_IO(CHARM_CODE, 100)/* HTC added */[/B]

enum charm_boot_type {
CHARM_NORMAL_BOOT = 0,
CHARM_RAM_DUMPS,
};

#endif

Wrong in CM10.1 build.

Code:

#ifndef _ARCH_ARM_MACH_MSM_MDM_IOCTLS_H
#define _ARXH_ARM_MACH_MSM_MDM_IOCTLS_H


#define CHARM_CODE0xCC
#define WAKE_CHARM_IO(CHARM_CODE, 1)
#define RESET_CHARM_IO(CHARM_CODE, 2)
#define CHECK_FOR_BOOT_IOR(CHARM_CODE, 3, int)
#define WAIT_FOR_BOOT_IO(CHARM_CODE, 4)
#define NORMAL_BOOT_DONE_IOW(CHARM_CODE, 5, int)
#define RAM_DUMP_DONE_IOW(CHARM_CODE, 6, int)
#define WAIT_FOR_RESTART_IOR(CHARM_CODE, 7, int)
#define GET_DLOAD_STATUS_IOR(CHARM_CODE, 8, int)

enum charm_boot_type {
CHARM_NORMAL_BOOT = 0,
CHARM_RAM_DUMPS,
};

#endif

I see a lot missing

Btw: I can say that what you've been told about our device tree is indeed true! It doesn't play nice with native cm code. Haven't even attempted AOSP... On a side note I synced the cm10-dna10.1 the other night to start contributing.. build fails out of the gate and repo sync again is a no go... Did someone accidentally break it?

lol... Which git are you building from so I can start on the same page? We can catch up via pm to exchange gtalk info

Sent from my HTC6435LVW using Tapatalk 2

nitsuj17 · Feb 20, 2013

chad0989 said:
Official support doesn't really mean anything significant. It just means that someone who wants to be maintainer cleans everything up the way they want it and submits the device tree and any other necessary commits that won't break other devices.

I'd also like to point out that s-off really isn't all that exciting. While its nice to have, it makes it dangerously easy to brick, especially if you're developing. Honestly HTC dev unlock is great IMO, you can develop as much as you want and you're almost brick proof. Now if there wasn't already the CID hack, s-off would be the greatest thing ever.

A third note is that I really don't think the phone is going to be hard to dev for. S4s are all the rage right now and have all the support and source we can hope for since the nexus 4 uses the same platform.

well said, 2 things that drive me nuts lately are

a) people assuming s-off somehow means something to rom/kernel development in general and specifically as it pertains to aosp
b) that aosp only means something if you have *official* support from cm/aokp/whatever

cryptworks · Feb 20, 2013

chad0989 said:
Not sure about it as we don't have it. It does appear to be needed by the prebuilt rild and libril.so for the dna though. Is it causing an issue?

It's really tempting to pick up a DNA from amazon wireless for $99 but I'm not sure if I want to use my upgrade or wait for the next wave, or get off vzw all together.

I have to say, The DNA is one of the nicer phones going right now. Still prefer it over the moto and samsung offerings. i even like it more than the N4 despite its obvious advantages.

whojabacod · Feb 20, 2013

Re: [ROM] CyanogenMod 10.0/10.1 on HTC DNA [Updated: 02.18.13]

I'm just a nobody in the dev world but just wondering now that we have s-off and CM will look into deving for s-off phones that if someone of stature reached out to CM at this point and perhaps have their team help in getting this thing full running and supported.

Sent from my HTC6435LVW using Tapatalk 2

cryptworks · Feb 20, 2013

orangechoochoo said:
You know there are 24 hours in a day, what did you waste the other 9 hours doing?

Eating, sleeping, If he is lucky a little nookie..

phydo · Feb 20, 2013

whojabacod said:
I'm just a nobody in the dev world but just wondering now that we have s-off and CM will look into deving for s-off phones that if someone of stature reached out to CM at this point and perhaps have their team help in getting this thing full running and supported.

Sent from my HTC6435LVW using Tapatalk 2

You still need a device maintainer for CM. Generally CM will support a device once it's running pretty well on it. you won't get the team to just "do it", but they almost always will make suggestions if you need help. If you buy someone big on the project a DNA you might be able to talk them into it

nitsuj17 · Feb 20, 2013

phydo said:
You still need a device maintainer for CM. Generally CM will support a device once it's running pretty well on it. you won't get the team to just "do it", but they almost always will make suggestions if you need help. If you buy someone big on the project a DNA you might be able to talk them into it

you dont need an existing cm device maintainer to get official support

you need to get aosp as functional as possible and make sure your patches and tree doesnt break anything in the mainline...submit for official support and then *you* can be the device maintainer

heck thats how most of people that are device maintainers became that

there are only a handful of people who are really on the main cm team

atishpatel2012 · Feb 21, 2013

nitsuj17 said:
you dont need an existing cm device maintainer to get official support

you need to get aosp as functional as possible and make sure your patches and tree doesnt break anything in the mainline...submit for official support and then *you* can be the device maintainer

heck thats how most of people that are device maintainers became that

there are only a handful of people who are really on the main cm team

haha well, if that is the case then good luck to drew! ;D He seems to be doing a great job developing for the device, and if or when he can get cm working on the DNA. I think it'd be great for the DNA, drew, and errrrrbody.

drewX2 · Feb 21, 2013

Who wants to join in on the fun? It may not be some fancy high tech setup, but it gets the job done. Thought I'd share a random pic for the hell of it.

Edit: wow that came out huge... I'm on my phone and just got into bed lol

alchemist316 · Feb 21, 2013

Re: [ROM] CyanogenMod 10.0/10.1 on HTC DNA [Updated: 02.18.13]

Samsung 55 smart as monitor I have no current pics I just got a replacement DNA :/ ..... Anyways thanks for all the work with this everyone

Sent from my HTC6435LVW using xda premium

[ROM][03.23.13] CyanogenMod 10 on HTC DNA; Audio WIP)

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Member

Senior Member

Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Attachments

Similar threads

Top Liked Posts