Develop Bugs

[Vendor Tree] Cyanogenmod for GSM Hero (Community Edition)

Ok so instead of five billion different ports of the CyanogenMod 5 for the GSM Hero, I have simply forked Darchstar's CDMA Hero port of CyanogenMod 5 on github.
It will be WAY more productive & efficient if all the developers work together instead of fragment the process of this port.
If anyone wants to be added as a collaborator, just PM your Github name.
Github: link

Re: [ROM-DEV] CyanogenMod 5 for the GSM Hero (Community Edition)
I think it is very good idea
-------------------------------------
Sent via the XDA Tapatalk App

bump..
tenchar

Free bump.
There needs to be some order around here. The amount of seeming "best" "fastest" Builds are a pain in the arse. Can people just not get their **** together? This forum is a proper mess.

Detol Loki said:
Free bump.
There needs to be some order around here. The amount of seeming "best" "fastest" Builds are a pain in the arse. Can people just not get their **** together? This forum is a proper mess.
Click to expand...
Click to collapse
I entirely agree.

you need to modify the AndroidBoard.mk to actually point to the hero libs and proprietary files to not get errors during compilation. and also, you may also want to use actual hero proprietary stuff in the vendor tree too.
also, rename the thread to "[Vendor Tree] Cyanogenmod for GSM Hero (Community Edition)"

darchstar said:
you need to modify the AndroidBoard.mk to actually point to the hero libs and proprietary files to not get errors during compilation. and also, you may also want to use actual hero proprietary stuff in the vendor tree too.
Click to expand...
Click to collapse
I don't know how to do any of this this. I have simply set this up to push the community into a direction of hopefully working together & get this working on the GSM Hero faster.

jaymac407 said:
I entirely agree.
Click to expand...
Click to collapse
As do I.. But then, I am still on an 1.5 rom, as I found them to be the fastest, least power-hungry.
The only thing I am missing is some Google Maps updates and some software I can not install as it requires 1.6+, but whenever I tried a 2.x rom, I found I only used it for a little while and then restored the nandroid backup of my trusty 1.5 setup, it's just fast and stable.

Sorry for this stupid quesiton, but how can i compile/sign/whatever it to run this on my hero?

I'm sure when the time comes there will be a release version. For now this is for the devs to work on.

Android 2.3 (Gingerbread) Being Pushed To AOSP

http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )

These are very good news
I already see my Hero running CM 7
:happy face:

Excellent News Lets see who get's their GingerBread ROM out first

Sweet, if the hero really will be supported!

Cooooooooooooooool man very nice go go go go gooooooooooooooogle

Tchuup-tchuup! Hotness train is leaving the stations

ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.

dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...

Good news
Sent from my HTC Hero

C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress

I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor

I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero

l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.

Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?

That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project

Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero

I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...

Especially the repo syncing... that just takes ages ;

krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!

Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents

[Q] The problem with ROM developement?

The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??

AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.

Jubakuba said:
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Click to expand...
Click to collapse
Yea I see what you mean, im just wondering how Cydia for iOS interacts with the ROM to apply patches then..?? how have they managed to implement this kind of system?
FNV looks interesting but a little dead. On the other hand, I like how actively updated CM10 is, and it doesn't look like support is going to stop there anytime soon which is a big plus.

UKROB86 said:
The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
Click to expand...
Click to collapse
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2

akash3656 said:
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yea I get what your saying.
Im not complaining about dead ROMs just was trying to think if there was a workaround. But yes I see your point about how a ROM developed from source would be less likely to lag.
I've been on CNA for awhile now, since AOKP slowed right now, and CNA is amazing. I guess CM10 is always a good backup if any of these ROM's stop updates.
thanks anyways.

Dont worry, you'll get your precious roms - this is an aosp device, after all.
Sent from my i9250

AOSP Rom

Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!

Sarmiento_Luise said:
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Click to expand...
Click to collapse
As of now, Geodev is the only one in development. If you're trying to get your post count up, go to the XDA General section and post in the new members forum or the off topic lounge.

postcount++
imho that geodev thing sounds shady at best.
If you would decide to port a custom rom to a new device, would you really start by porting KitKat if the device
currently only runs jellybean? Wouldn't it be easier to use the stock kernel for now to get cm10 running
and then wait paitiently until htc releases the kernel src to make it a full unofficial cm10 build.
Instead this sounds more like taking the existing source of a hopefully hardware compatible build
and bending it until it brea.. ehm works.
I may be biased, but if you plan to make any kind of release you usually don't go and announce it to the world.
This only encourages the rather impatient endusers to come up with many variations of the same old:
"i need my rls now!", "I am entitled to a release because I found this thread","GIMME RLS!!!11oneeleven"
posts that will just annoy the crap out of every dev I've ever met. Also there is absolutely no point in asking for
beta testers before you even have a working build ready.
Combine that with the recent e-begging post and draw your own conclusions.
DroidTwe4kz said:
[...] I can't continue developing until someone gift me new computer (or motherboard only). [...]
Click to expand...
Click to collapse
In any case, for the time being it might be a good idea to check if there are some services you could deactivate
in order to get a little bit more speed out of your phone. I personally have no problems with lags, but maybe
it's because I don't expect the phone to run every app ever made at the same time since it has only 512MB RAM.

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