Develop Bugs

Cyanogen new AOSP Froyo rom based off sprints update?

I love the CM6 Rom because it has all AOSP apps, icons, notification bar, all that good stuff. I prefer it over sense.
However I know the CM6 Rom is ported from the Nexus one, but has Cyanogen said he will make a new build based off of the Sprint Froyo update?
I still want AOSP, but I do want working 4G and bluetooth.
I believe that the problem is, because it was from the Nexus one it will take a while to get 4G working and bluetooth because the code is different?

CM6 isn't ported from the N1.
http://source.android.com/
CM6 is made from the Froyo source code.

I'm sure he will evetually use Sprints source, it would make it a lot easier to fix current issues.
Sent from my HTC EVO 4G.

akarol said:
I'm sure he will evetually use Sprints source, it would make it a lot easier to fix current issues.
Click to expand...
Click to collapse
I'm sure he won't, since the only source Sprint/HTC are required to release is that of the kernel.
I don't know how many times people have to be told that CyanogenMod is an AOSP ROM before they actually pay attention. If it's not open-source, it's not in CyanogenMod.
Seems incredibly simple, yet people have an incredible amount of difficulty with it.

posguy99 said:
I'm sure he won't, since the only source Sprint/HTC are required to release is that of the kernel.
I don't know how many times people have to be told that CyanogenMod is an AOSP ROM before they actually pay attention. If it's not open-source, it's not in CyanogenMod.
Seems incredibly simple, yet people have an incredible amount of difficulty with it.
Click to expand...
Click to collapse
I didn't know that he only uses open source. Could you explain what the difference is?
Sent from my PC36100

everyone wants everything to work....just pick a rom and keep going time will pass and roms will keep getting updated unless google itself is releasing a rom not everything will be 100%

mjz147 said:
I didn't know that he only uses open source. Could you explain what the difference is?
Sent from my PC36100
Click to expand...
Click to collapse
www.dictionary.com said:
open source
— n
a. intellectual property, esp computer source code, that is made freely available to the general public by its creators
b. Compare closed source ( as modifier ): open source software
closed source
— n
a. intellectual property, esp computer source code, that is not made available to the general public by its creators
b. Compare open source ( as modifier ): closed source software
Click to expand...
Click to collapse
This Here ^

mjz147 said:
I didn't know that he only uses open source. Could you explain what the difference is?
Sent from my PC36100
Click to expand...
Click to collapse
Most roms use native (i.e. not covered by the Android open source license) code owned by HTC, Sprint, or Google. This includes some Google apps and system processes like the Evo's wimax code.
Cyanogen only uses open source code, period. All of the code is either modified open source code or made from scratch. The reason that 4g doesn't work on Cyanogen is that they are currently in the process of reverse engineering an opensource radio to implement on the Evo.
And now the reason - by keeping the entire rom open source, Cyanogen and the team can focus on the creating a great peice of software without having to worry about legal actions by HTC, Google, or Sprint. There is a lot of work put into the roms and it would be stupid to risk everything with stolen 4g code or a Sense port.

cath0dez said:
Most roms use native (i.e. not covered by the Android open source license) code owned by HTC, Sprint, or Google. This includes some Google apps and system processes like the Evo's wimax code.
Cyanogen only uses open source code, period. All of the code is either modified open source code or made from scratch. The reason that 4g doesn't work on Cyanogen is that they are currently in the process of reverse engineering an opensource radio to implement on the Evo.
And now the reason - by keeping the entire rom open source, Cyanogen and the team can focus on the creating a great peice of software without having to worry about legal actions by HTC, Google, or Sprint. There is a lot of work put into the roms and it would be stupid to risk everything with stolen 4g code or a Sense port.
Click to expand...
Click to collapse
Trimmed to make sense to people who weren't in the chat.
[16:57] * Now talking in #Cyanogenmod
[16:57] * Topic is 'Latest versions: STABLE=5.0.8 DS&N1/EXPERIMENT: 6.0.0-RC2 N1/DS: http://bit.ly/do0zmr (nexus=N1;testing=DS) FRF91 Gapps: http://bit.ly/ddHdcD (mdpi=DS;hdpi=N1)/ Droid users - #koush / Slide - #TeamSlide :: You must register your nick (/msg nickserv help) to speak :: Forum: http://forum.cyanogenmod.com :: Wiki: http://wiki.cyanogenmod.com | stop asking about apps2sd or ETA'
[16:57] * Set by [email protected]/rikupw on Tue Jul 27 15:27:46
[16:57] -ChanServ- [#cyanogenMod] Welcome to #CyanogenMod :: Discussing the best Custom Android Shizzle on the Planet :: visit http://wiki.cyanogenmod.com :: swapping semi-functioning giggling brat vanity for a bare knuckle bucket of DOES
[16:58] <DrMacinyasha> Awright, quicky: Is Team Douche so strict about all-OSS that they won't yank the 4G, FM, and camera drivers out of the EVO's OTA?
[16:59] <@ciwrl|work> DrMacinyasha i dont get the question?
[16:59] <@ciwrl|work> proprietary stuff will stay in for those features...if thats what youre curious about
[17:00] <jjcm> ciwrl|work: He's asking if the reason why the EVO doesn't have 4g is because of compliance to open souce standards, and if it's because they dont want to use proprietary binaries.
[17:00] <@ciwrl|work> oh...uh..no
[17:00] <DrMacinyasha> ciwrl|work: Sprint/HTC are starting to push out the EVO's Froyo OTA, but since the 4G, FM transciever, and front camera drivers are all proprietary, will the team insist that the drivers have to be remade from scratch 100% OSS, or can they just be copied from the OTA package?
[17:00] <jjcm> ciwrl|work: Or rather, 4g when custom firmware is installed
[17:00] <@ciwrl|work> its not compliance...more so, lack of openess on htc's side
[17:03] <DrMacinyasha> I know why the /current/ CM6 nightly/RC doesn't have 4G/FM/HDMI, but since there's now a publicly available 2.2 ROM with everything working, the tools to get everything going are now available. Will those tools be used, or will they have to be rebuilt completely in order to satisfy the team's "We're all Open-Source" stance?
[17:03] <DrMacinyasha> That's all.
[17:03] <DrMacinyasha> I can't... Really make it any simpler. :/
[17:03] <@ciwrl|work> DrMacinyasha they will be
[17:04] <jjcm> DrMacinyasha: They will be unless HTC pulls a google and tells cyanogen to GTFO their lawn.
[17:04] <DrMacinyasha> Sweet. One of my friends just got an EVO, and he's being all *****y about rooting it and getting CM6 because he actually lives in a 4G area and tethers.
Click to expand...
Click to collapse

cath0dez said:
Most roms use native (i.e. not covered by the Android open source license) code owned by HTC, Sprint, or Google. This includes some Google apps and system processes like the Evo's wimax code.
Cyanogen only uses open source code, period. All of the code is either modified open source code or made from scratch. The reason that 4g doesn't work on Cyanogen is that they are currently in the process of reverse engineering an opensource radio to implement on the Evo.
And now the reason - by keeping the entire rom open source, Cyanogen and the team can focus on the creating a great peice of software without having to worry about legal actions by HTC, Google, or Sprint. There is a lot of work put into the roms and it would be stupid to risk everything with stolen 4g code or a Sense port.
Click to expand...
Click to collapse
got it, thanks.

When HTC releases the kernel source Cyanogen will easily get things working.

TheBiles said:
When HTC releases the kernel source Cyanogen will easily get things working.
Click to expand...
Click to collapse
4G not working has nothing to do with the kernal. its the actual coding htc used to create the program that makes 4G work. Since htc is not going to release those codes cyanogen and team have to reverse engineer the program. Actually 4g is coming along nicely and should be here soon.

From the sound of it the new 2.2 release actually wont help them at all? I feel like that can only be some what true. I image they will still look at the coding of some of the features to guide there way to fixing some of the current issues? Either way CM6 is freakin awesome and I dont plan on changing to sprints 2.2. I am in love with froyo and not having sense on my phone is great since I like ADW anyway.

p-slim said:
4G not working has nothing to do with the kernal. its the actual coding htc used to create the program that makes 4G work. Since htc is not going to release those codes cyanogen and team have to reverse engineer the program. Actually 4g is coming along nicely and should be here soon.
Click to expand...
Click to collapse
twilk73 said:
From the sound of it the new 2.2 release actually wont help them at all? I feel like that can only be some what true. I image they will still look at the coding of some of the features to guide there way to fixing some of the current issues? Either way CM6 is freakin awesome and I dont plan on changing to sprints 2.2. I am in love with froyo and not having sense on my phone is great since I like ADW anyway.
Click to expand...
Click to collapse
See my above post.

Correct me if im wrong, but i think cyanogen has stated on his twitter a few days ago that the official 2.2 froyo update wont help out development of his rom

Well only time will tell...

drmacinyasha said:
Well only time will tell...
Click to expand...
Click to collapse
Ugh no, you can use your brain and know they have nothing to do with each other. Also as the other Guy stated, even on twitter cyanogen said the new release will not help in any way. You're wrong, go read his twitter to catch up and educate yourself as to why they are completely seperate and will not help in any way as stated before.

[DEV] Fixing/Updating the HD2 kernel and missing code

Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here

Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them

charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.

@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.

The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252

memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...

@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.

Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code

hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu

charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.

Ok I'll do it tomorrow n also maintain the list in the op

I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......

Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.

I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.

This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.

D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris

Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3

tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..

g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.

Fried my laptop charger. New one on way. Hd2 arrived

[REQ] Guess what? Right, 3.0 kernel.

@Kernel devs,
Please, congregate your forces and build 3.x kernel for our precious Arc. I bet this will be one of the most (if not The Most) appreciated works. I bet this will be one of the most useful ones too. I bet almost every Arc/S user will agree with me.
Sent from nowhere

Absolutely!

What are the features you are waiting for in 3.0?

soo what does the new kernel provide?! I've seen few comments about users wanting the new kernel, and was wondering what improvement will it do to our Xperia?!

Mods please move this thread to general or Q&A. This thread is for android development, not wish lists.
Yes we'd all love a new kernel, why not bump to 3.5, well the answer to that is closed source drivers. While we should be able to theoretically add most of the maintenance patches to get to the latest 2.6.32.xx, porting to different major versions are just unlikely to be possible for our phone. You can't link against something with a different API, it just won't work.
The first request should be made to Sony to release sources for these drivers. Good luck with that.
So instead of focusing on version numbers, instead ask "Is feature X possible with our current kernel" and the kernel devs will try to accommodate and patch it in.

First of all, this isn't for Wishes and Requests, this is where you share you dev work with everyone, if you have a request then go to general or Q&A.
Second, EVERY DEVELOPER ALREADY KNOWS ABOUT THIS. Everyone IS WORKING on Kernel 3.0, ICS was laggy and JB isn't perfect is because the the lack of support in the kernel. So they don't need a "request"
Third, it is not impossible but very very hard. There is a reason why kernel 3.0 was never ported, because even the best devs like FXP and DoomLord CAN'T. Unless Sony releases their hardware sources or some developers open up his own Arc and get it out, no kernel 3.0 can be ported!

Custom msm7x30 3.0 kernels are still really in infancy stages with no major changes. If anything it's just a facelift but still the same purpose-wise.

Well, for those saing that devs can't do something I would argue - there's a 3.0 kernel being developed for HTC Desire (which also has closed source drivers) and guys working on it are pretty close. Same goes for HTC DHD and HD2 if i'm not mistaken. So why not for our device?
Sent from nowhere

tajimura said:
@Kernel devs,
Please, congregate your forces and build 3.x kernel for our precious Arc. I bet this will be one of the most (if not The Most) appreciated works. I bet this will be one of the most useful ones too. I bet almost every Arc/S user will agree with me.
Sent from nowhere
Click to expand...
Click to collapse
+ over 9000!
---------- Post added at 09:49 AM ---------- Previous post was at 09:40 AM ----------
It would be just awesome, beacuse idiots from Sony will pobably never update our kernels. Even HTC Wildfire S (which is little, smarttoy) has 2.6.35.x. It's not big difference, but... It is!

pmdisawesome said:
First of all, this isn't for Wishes and Requests, this is where you share you dev work with everyone, if you have a request then go to general or Q&A.
Second, EVERY DEVELOPER ALREADY KNOWS ABOUT THIS. Everyone IS WORKING on Kernel 3.0, ICS was laggy and JB isn't perfect is because the the lack of support in the kernel. So they don't need a "request"
Third, it is not impossible but very very hard. There is a reason why kernel 3.0 was never ported, because even the best devs like FXP and DoomLord CAN'T. Unless Sony releases their hardware sources or some developers open up his own Arc and get it out, no kernel 3.0 can be ported!
Click to expand...
Click to collapse
Work had already begun (with a lot of help from Jimbo77). It is stopped now (holidays) but for sure it's not abandoned.
tajimura said:
Well, for those saing that devs can't do something I would argue - there's a 3.0 kernel being developed for HTC Desire (which also has closed source drivers) and guys working on it are pretty close. Same goes for HTC DHD and HD2 if i'm not mistaken. So why not for our device?
Sent from nowhere
Click to expand...
Click to collapse
Because there is no Sony msm8255t 3.x kernel released that we can use as a base. There are major changes between 2.6.3x and 3.x kernel so
-all hardware related files (read: cpu, vibra etc) must be updated
-all drivers (read: screen, keys, sound etc) must be updated or rewritten
so it takes a lot of time and learning.
It's done when it's done
Click to expand...
Click to collapse

gen_scheisskopf said:
Work had already begun (with a lot of help from Jimbo77). It is stopped now (holidays) but for sure it's not abandoned.
Because there is no Sony msm8255t 3.x kernel released that we can use as a base. There are major changes between 2.6.3x and 3.x kernel so
-all hardware related files (read: cpu, vibra etc) must be updated
-all drivers (read: screen, keys, sound etc) must be updated or rewritten
so it takes a lot of time and learning.
Click to expand...
Click to collapse
first and bigest major new funcion is ntfs suport(for me there are, also sove with batery iporvents , also ksm is form 3.0.16 or 3.0.8(with used in cm roms))

n1kolaa said:
first and bigest major new funcion is ntfs suport(for me there are, also sove with batery iporvents , also ksm is form 3.0.16 or 3.0.8(with used in cm roms))
Click to expand...
Click to collapse
I had internal functions in mind (like ssize_t(*show) ), not user level.

Why would anyone think that this thread belongs in Development section, is beyond me.
Moreover, why would anyone think that in such community, known for the breakthroughs that its developers are achieving at a daily basis, such a request thread is needed.
I would like to believe that anyone who has been here long enough knows that if something is possible, it is done.
So, all in all, please think twice before clicking the "Start A New Thread" button.
Thanks for your cooperation.
Thread closed.

[Q] What would happen if I build android from source and flash it to my One X?

What would happen if I build android from source and flash it to my One X?
With the current release, it is possible to build for Nexus 7, for some variants of Galaxy Nexus, for a variant of the Motorola Xoom, and for all variants of Nexus S and Nexus S 4G. The exact level of functionality for each device depends on the availability of the relevant proprietary hardware-specific binaries.
Click to expand...
Click to collapse
- (source)
Will I brick my device? Did HTC basically just take the code and modify it to work on the One X? Any suggestions on how to proceed if I were to build my own ROM?

If you have no experience in this you are likely to f*** things up.
Just stick to aosp roms - same result.
Sent from my HTC One X

TToivanen said:
If you have no experience in this you are likely to f*** things up.
Just stick to aosp roms - same result.
Click to expand...
Click to collapse
Well that is no fun answer. I want to learn. I make apps for a living and want to advance and build my own ROM, because I want an all custom made one. I know I can go with CM and mod their code (or, can I?), but it would be more fun to actually do it from scratch. If it is possible, not build from AOSP at all. I know it sounds retarded but I believe the best way to learn is do as much as possible completely from scratch.
With that said, do you have any suggestion on where to start? Like mod the AOSP source code and get it running on the emulator?

You can branch cm10 and build that, it's a good place to start, you'll learn a lot.
After that, you may want to say, diff the AOSP kernel against a similar HTC kernel to see how many changes you'd be required to make to pure AOSP to get it to work with all the hardware specific bits.
Due to GPL, HTC are required to release the source modifications to the kernel and android (I assume), for any released binaries, but they can be a little slow. The JB stuff should be out soon, in theory. Hopefully that's enough to get everything working, but you will also need any binary drivers from nVidia etc.
It's a long road, and you'd do well to start with something working and work backwards towards AOSP.
I'm not sure what you mean by not even with AOSP, do you intend to create your own OS?

BenPope said:
You can branch cm10 and build that, it's a good place to start, you'll learn a lot.
After that, you may want to say, diff the AOSP kernel against a similar HTC kernel to see how many changes you'd be required to make to pure AOSP to get it to work with all the hardware specific bits.
Due to GPL, HTC are required to release the source modifications to the kernel and android (I assume), for any released binaries, but they can be a little slow. The JB stuff should be out soon, in theory. Hopefully that's enough to get everything working, but you will also need any binary drivers from nVidia etc.
It's a long road, and you'd do well to start with something working and work backwards towards AOSP.
I'm not sure what you mean by not even with AOSP, do you intend to create your own OS?
Click to expand...
Click to collapse
Thanks for the thorough information! If it is possible to create your own OS, then yes, it would be awesome. Actually my idea is to make a ROM similar to the Linux distribution Tiny Core Linux; only the most essential stuff are present and bloatware and other features are removed. It could maybe serve as a good starting point for other ROMs to build on that want a minimalistic base. However, that is very, very far into the future. Now I would just like to compile a ROM that I have developed. But as I said before, if possible, skip AOSP and build my own OS definitely! Is that even possible?

Of course its possible, Android wasn't invented by some higher being or alien lifeform.
Nobody would use it though, because there would be no apps.

BenPope said:
Of course its possible, Android wasn't invented by some higher being or alien lifeform.
Nobody would use it though, because there would be no apps.
Click to expand...
Click to collapse
I see, so I am locked to AOSP then? i better start with the CM branch, thanks a bunch.

Cyanogenmod 12 (12.1) for HTC One (M9)

I just wanted to start this thread for anyone who has information regarding the development of cyanogenmod 12 for the HTC One M9 and for a general discussion on Cyanogenmod 12 and 12.1

This is something I'd be incredibly interested in. I've got a gold S6 Edge preordered; in part because the M9 is uninspiring, partly because I'm not at at all a fan of Sense 7. Having cyanogenmod on this device might be a game changer for me.

Don't you think that when a dev has that information, they will post it themselves in the development forum, instead of searching Q&A for your thread?

Why you gotta go round throwing logic into the mix?

To be fair, I think there are a decent amount of people interested in this. Why not have a little playful banter in advance.
For I will most certainly jump on the vzw variant when we get the s-off treatment and reasonably stable cm12 builds

I'm working on CM builds for the M9 (developer version for now) so I'll keep you updated when I get it to boot.

Rashed97 said:
I'm working on CM builds for the M9 (developer version for now) so I'll keep you updated when I get it to boot.
Click to expand...
Click to collapse
Heroic. Best of luck. I am hurting for vzw s-off treatment for cm12 with a better camera than m8.
Thank you for your efforts.

Someone from AICP is also building... It builds fine just can't get it to boot yet

Rashed97 said:
I'm working on CM builds for the M9 (developer version for now) so I'll keep you updated when I get it to boot.
Click to expand...
Click to collapse
Hey dude, I want to buy this device, but I'm wondering how much "friendly" is HTC with the open source about the driver binary blobs? I saw the kernel sources from HTC, but I do not found the firmware/module blob. How are you doing this job? Are fully open source or are you using the same kernel version to re-use the current binaries?
Many thanks

WalterCool said:
Hey dude, I want to buy this device, but I'm wondering how much "friendly" is HTC with the open source about the driver binary blobs? I saw the kernel sources from HTC, but I do not found the firmware/module blob. How are you doing this job? Are fully open source or are you using the same kernel version to re-use the current binaries?
Many thanks
Click to expand...
Click to collapse
You can get these from the device itself.

Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display

Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
Rashed,
Thanks for your continuing work on this. Any updates to this thread are extremely nice. Obviously I can't really do much to help, but it's fun to see what you guys are working on.
Hope everything is going smoothly. I'm super excited to boot cm on yet another device.

Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
this makes me happy in the pants. <3

Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
I have to agree this makes me very happy:victory:

I've no doubt that this will happen, and there's probably a distinct possibility of dual boot too, I haven't heard anything as of yet but HTC usually does get good stuff, the M9 is a stellar device, not without it's faults but I wouldn't swap it, coming from an iPhone 6 and a Note 4 I wouldn't swap it back, I've also had the S6 and the S6 edge to use and they simply don't compare, nothing wrong with them that's just my opinion.
Watch the original development section for development of CM12 / 12.1, it will get done, hopefully pac and dirt unicorns will follow, they're the ones to watch for.
Got to say, running viper and Leedroid at the moment, absolutely superb roms, both of them.

Rashed97 said:
Just thought I'd share, we have a booting system. Broken stuff: camera, NFC, WiFi, Audio, media. Working stuff: Bluetooth, RIL, sensors, touch, display
Click to expand...
Click to collapse
hey rashed97 how's it going, very much looking forward to having something none sense to try out on my m9.

Like @Rashed97 I'm working on a build as well. Right now I'm just trying to figure out how to get all of the proprietary stuff I need out of the sense kernel source and shoehorn it into AOSP kernel source. That's the biggest step to getting it to boot.
In past devices that didn't get a Google Play Edition, and therefore only had sense kernel source released, there had to be a way to do this... So I'm taking a trip through history of popular handsets where someone managed to port the vanilla kernel source to the phone with sense.
Barring that, I'll just strip all of sense out of a stock rom, replace the status bar icons and other assets with stock LP, and slap nova launcher on it and make a lightweight senseless rom. I'd really prefer getting a CM build on this thing though so I'm going to keep plugging away at that until either I get it to work, or someone else does and I can add my work into their release.

agentfusion said:
Like @Rashed97 I'm working on a build as well. Right now I'm just trying to figure out how to get all of the proprietary stuff I need out of the sense kernel source and shoehorn it into AOSP kernel source. That's the biggest step to getting it to boot.
In past devices that didn't get a Google Play Edition, and therefore only had sense kernel source released, there had to be a way to do this... So I'm taking a trip through history of popular handsets where someone managed to port the vanilla kernel source to the phone with sense.
Barring that, I'll just strip all of sense out of a stock rom, replace the status bar icons and other assets with stock LP, and slap nova launcher on it and make a lightweight senseless rom. I'd really prefer getting a CM build on this thing though so I'm going to keep plugging away at that until either I get it to work, or someone else does and I can add my work into their release.
Click to expand...
Click to collapse
Sounds great. Had GPE running like a dream on my M8, so it almost seemed to me like a step backwards, moving to M9 with Sense. AOSP on M8 didn't have the sound drivers, so audio quality was an issue and a deal-breaker.

Thanks for the update. I've been chomping at the bit waiting for an aosp.

agentfusion said:
Like @Rashed97 I'm working on a build as well. Right now I'm just trying to figure out how to get all of the proprietary stuff I need out of the sense kernel source and shoehorn it into AOSP kernel source. That's the biggest step to getting it to boot.
In past devices that didn't get a Google Play Edition, and therefore only had sense kernel source released, there had to be a way to do this... So I'm taking a trip through history of popular handsets where someone managed to port the vanilla kernel source to the phone with sense.
Barring that, I'll just strip all of sense out of a stock rom, replace the status bar icons and other assets with stock LP, and slap nova launcher on it and make a lightweight senseless rom. I'd really prefer getting a CM build on this thing though so I'm going to keep plugging away at that until either I get it to work, or someone else does and I can add my work into their release.
Click to expand...
Click to collapse
There's eragon rom which is de-sensed running everything you just mentioned with the htc sense camera included and few other apks. Its dead quick and dev has been around since hox days making roms like that