Seems that the CDMA guys have got overclocking working on 2.1 roms, without making camera broken and messing up a lot of other things too.. Just wanted to point this out to GSM developers. I really hope you can do the same for us european users Thanks.
i think all the devs already know that, its been discussed numerous times
It's because they have a proper kernal from HTC, there isn't one availible for GSM Hero's for 2.1. that is the cause of all the problems, so until the offical update comes out, theres nothing they can do
If you have nothing relevant to say to thread, then say nothing.
@ madsborelli - Before creating a new thread, search that an existing one or similar topic hasn't been discussed before. Also, ask yourself which forum your thread would be best served in
The Roms created by Developer are already impressive. Just imageine if they were to be cobntented with the new kernel, thier development process would be much more easier and will be improved significantly. Just wait for it.
now THIS is a new dimension of censorship!
On the new cronos rom, they use the .29 kernel. Does this mean that developers now can make overclocking on 2.1 gsm roms fully working with no bugs now?
so far the "dev" of the cronos rom has yet to prove he has done anything with the kernel. the kernel that was packed with the first release of his rom was identical to the last bit with all the other leaks. some libs might have been recompiled, not sure what impact that has exactly on performance.
i amy be wrong, but is'nt this the g2 touch, htc hero forum, Not the cdma one, that has its own one here http://forum.xda-developers.com/forumdisplay.php?f=641
kendong2 said:
so far the "dev" of the cronos rom has yet to prove he has done anything with the kernel. the kernel that was packed with the first release of his rom was identical to the last bit with all the other leaks. some libs might have been recompiled, not sure what impact that has exactly on performance.
Click to expand...
Click to collapse
That was the fix mate.
Related
I'm new to Android but not new to Linux and wondering what is necessary to get these ROMs (and others) working on the CDMA Hero. What are the major differences, proprietary drivers? Kernel modules?
New Cyanogen ROM, just released
http://forum.xda-developers.com/showthread.php?t=567610
In other words, what's stopping us from running these ROM's right along with G1/Dream users?
I'm curious also... would love to try his roms...
Since Android 1.6 was supposed to add CDMA support I would think they should work as well as 2.0 unless the developers have taken the cdma support out of the code in their roms to shrink the size to fit on the G1's.
If I had a Hero I would be giving it a try most likely. I might try picking one up this week since Best Buy has them down to $99. I just wish it had a keyboard.
I'll try when I get home from work.
On a side note, even if this rom doesn't work, I should be able to boot into the recovery rom no matter what... riiiiiiight?
herzzreh said:
I'll try when I get home from work.
On a side note, even if this rom doesn't work, I should be able to boot into the recovery rom no matter what... riiiiiiight?
Click to expand...
Click to collapse
Correct! The recovery image isn't touched by normal ROMS typically.
I'm tempted. Can this be applied right over the MoDaCo ROM?
I have tried a couple things with these. I tried flashing it outright. Wouldnt get past the initial htc boot screen. So I replaced the kernel in the boot.img of Cyans rom with ours, that still didnt work. Then I tried replacing the entire boot.img and still no boot working. I think Donut uses the 2.6.29 kernel or whatever it is. Ours is .27 so I think we would need to recompile the .29 kernel and pray our drivers work with it. Please, someone else try it too and see if they can get it working. I would love you forever if you could. If not, we will just have to wait until HTC gets us Eclair.
Thanks
Thanks for trying this, chuckhriczko and others.
I'm mainly coming at this from the pure Linux point of view: shouldn't these ROM's run anywhere (barring proprietary bits)? Shouldn't we be able to "share and share alike" between platforms, Hero/Dream/G1/whatever? If there is a chip architecture difference, fine then we need a recompiled kernel. Obviously there is also the question of firmware, but that's a given on all phones.
Otherwise, shouldn't these ROM's be fairly universal? Or if they are not, I'd like to know what makes ROM building such a unique endeavor for each phone.
5tr4t4 said:
Thanks for trying this, chuckhriczko and others.
I'm mainly coming at this from the pure Linux point of view: shouldn't these ROM's run anywhere (barring proprietary bits)? Shouldn't we be able to "share and share alike" between platforms, Hero/Dream/G1/whatever? If there is a chip architecture difference, fine then we need a recompiled kernel. Obviously there is also the question of firmware, but that's a given on all phones.
Otherwise, shouldn't these ROM's be fairly universal? Or if they are not, I'd like to know what makes ROM building such a unique endeavor for each phone.
Click to expand...
Click to collapse
I believe it's mostly the proprietary drivers for some of the hardware as well as needing a kernel recompile...once HTC releases the CDMA kernel, I'm sure we'll see a lot more (that or some genius will reverse engineer it...either way!)
The other thing to consider is that most of these ROMs are based on something...they take what's existing and tweak the heck out of it (I'm willing to bet that the vast majority of ROMs can trace their roots back to an official vendor image at some point).
I'm actually trying to setup a build environment and poke around but I'm starting from ground zero on the mobile platform side of things so I wouldn't hold out for me (and finding a Java 1.5 runtime is surprisingly hard these days ).
I'm noticing that we're seeing more and more ROM's pop up (primarily gutted ROMs focussed on eeking more speed as opposed to MoDaCo who went for more features).
thecodemonk said:
I believe it's mostly the proprietary drivers for some of the hardware as well as needing a kernel recompile...once HTC releases the CDMA kernel, I'm sure we'll see a lot more (that or some genius will reverse engineer it...either way!)
The other thing to consider is that most of these ROMs are based on something...they take what's existing and tweak the heck out of it (I'm willing to bet that the vast majority of ROMs can trace their roots back to an official vendor image at some point).
I'm actually trying to setup a build environment and poke around but I'm starting from ground zero on the mobile platform side of things so I wouldn't hold out for me (and finding a Java 1.5 runtime is surprisingly hard these days ).
I'm noticing that we're seeing more and more ROM's pop up (primarily gutted ROMs focussed on eeking more speed as opposed to MoDaCo who went for more features).
Click to expand...
Click to collapse
What OS are you using? If your using a Debian based linux then you can get it from the Debian Lenny repositories. One word about this though, it killed my existing Java 1.6 so I had to reinstall it when I needed it. Otherwise that works.
And yeah, we are primarily doing gutted roms because that is all we know up to this point. It is very difficult to find help from those who know all about recompiling a kernel and things like that. Like I said, I couldnt get Cyanogen to even boot on my phone but obviously, it should at the very least do that. But only one dev on these forums ever helped me with my CDMA roms and that was Mlign from the Dream forums. Everyone else (understandably busy) ignored me. Im not saying anything bad about them but it's just harder for people to learn. Patience will give us what we desire though.
vendor tree for cyanogen heroc
im a noob and dont know how to build it but its here:
http://github.com/darchstar/vendor_cyanogen_heroc
Thread gravedigging much?
yes haha i want cyanogen on my hero lol
Anyone else notice that the frequency of new ROMs and updates are scarce on the N1? I assume its because the phone is overkill for the now and doesn't need too many optimizations. Just an observation I made coming from the G1.
P.S. I am not criticizing cyanogen, enomother, modaco, etc. at all, if I thought it was truly a problem, I would try to learn it myself. I am just curious as to why and what other people thought.
crazyyellowguy said:
Anyone else notice that the frequency of new ROMs and updates are scarce on the N1? I assume its because the phone is overkill for the now and doesn't need too many optimizations. Just an observation I made coming from the G1.
P.S. I am not criticizing cyanogen, enomother, modaco, etc. at all, if I thought it was truly a problem, I would try to learn it myself. I am just curious as to why and what other people thought.
Click to expand...
Click to collapse
The phone is just over 1 month old... so, not every dev has made the switch, and Cyan Enom and Modaco kinda did about the only things that could be done right now; Make an AOSP ROM and a modded version of the stock ROM.
They got us a kernel with the missing RAM, root for our devices, and Amon got us his custom recovery. We have every feature any other hacked Android phone has, except a SenseUI ROM, and that is going to take a couple things before it can happen, namely a dump of a SenseUI ROM scaled to our screen resolution.
Hey guys and girls!
Sorry for the long absence. Divorce is... sticky. Ha.
So, I was coming back considering working on HappyRom again, I've seen a few other roms have taken some pieces of what I've done, which is great - also sad though because they've given themselves some of the same old issues I was working on fixing. On the other hand though, I've seen a lot of good stuff going on, new roms, new work, NEW DEVELOPERS!
So, someone give me the lowdown - whats going on, what's hot and what should I be working on?
Well you already have a request for a 2.2 sense rom above you in this thread. If its even possible right now.
sent from my superfroyo dream
Froyo on G1, that's hot! First AOSP released source code for Froyo, then Cyanogen started to work on it and when CM6 RC1 and nighlies was released, every dev started to release their ROMs based on CM6. In short - CM6 and it's modifications are hot.
If it's about Sense ROMs - nothing interesting, maybe ZXHero and Hero2G1 are still updated, I think everyone gave up on them since they are slow and newer firmware is available.
For me very nice work is what Firerat is doing - scripts! His MTD Partition Hack eliminates need of using Haykuro, since you can freely repartition your /system, /data and /cache partitions on your G1. You can also fake your SPL which is awesome, brick-free method of installing too big for stock layout.
His all-in-one script and a2sd (included in all-one) also rocks, they enable swap, a2ext and few other really handy functions.
Erm, I don't know what else. Maybe a new radio? 2.22.23.02 was released, for some it has better signal reception, for some worse, few reports way better battery life, while others see no difference.
Hope I helped, if you want more intel please ask .
This is a request to all the developers developing for HD2, If you want a fully working, fully stable build on HD2 with top performance you would have to stop treating your device as Bravo, everywhere i look from recoveries to kernel i see Bravo, Evo, Passion. For God's sake the phone is different from all other snapdragon phones.The display, the drivers etc are different. Also please stop keeping the source of your edited files to yourself, if you open source them, they can be improved upon and HD2 can be made faster and better device. Also developers thing beyond overclocking. There are other things HD2 needs in the kernel. If you waste your energy in just overclocking then i would say its pretty dumb. Just a kind request to everyone. Your device is htcleo/leo not bravo/passion/supersonic. They are similar but not same. use htcleo as device name in build, init rather than bravo/passion/supersonic. Your device isnt a mix of device anymore, its a different device that stands apart
im not a dev but ... yes , is time when all work must be unified.
+1 on this.
All devs should work together and share their results.
Bump.
This thread needs to be looked at and acknowledged. Charansingh is trying hard to get our device working to its best possible method and not just patch everything constantly. If some kernel developers (Tytung, rafpigna, iamgpc, etc.) set up conversations with charansingh, I'm pretty sure all outstanding issues could be worked on and we could even fix issues we didn't know we had. Come on, devs! Work together to bring our HD2s to truly compete with android devices out there as a native solution!
Definitely worth a bump
Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.
rottenjello138 said:
Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.
Click to expand...
Click to collapse
The Nexus is a native Android device. Of course the ROM development will be different. It's a miracle we have Android on the HD2 at all. It was always going to be a painful development process. That said, wise words from charnsingh.
Keep rocking, Devs.
I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.
mzebrowski13 said:
I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.
Click to expand...
Click to collapse
if you read craefully pongster thread,his build still use desire base..from source of desire
ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Hhhmmm I don't want to be a Pongster lawyer And I hope that HE will not feel offended but let me quote some parts of tread Hyperdroid CM7
Drawing inspiration from the Desire AOSP based Custom ROMs
Click to expand...
Click to collapse
Again, THIS is NOT a PORT... its Completely Built FROM SOURCE, Fully Optimized and Tweaked for the HD2!
Click to expand...
Click to collapse
ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
The source is built from the following: Base is Pure AOSP, Framework Tweaks and Settings is Redux, Cool Features & Functions from CyanogenMod.
Click to expand...
Click to collapse
from the gbx thread.
ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Have you bothered checking the source I use? and the device specific stuff by charan for the HD2 in there? I don't use the desire base. The source of the ROM is something any device can use, given the right kernel and proprietary libs the device may need. Just like CM7 is not just for the HD2, but for a myriad of different devices, the source can be used by anyone with the right device specific stuff.
In my ROM, I use the device specific stuff that charan has done for CM7 HD2 (with a few edits for GBX overlays and HD2 specific Settings).
Like charan has mentioned, most of what we currently have here (ROMs) are ports/kangs from other devices. In fact my old SD build was one of them.
His hard work paved the way for a device specific ROM, that being the CM7 RC's he builds (and you can build, which I also do for testing, from source) and the GBX I build now. If you take the source and add the device specific stuff (drivers, ramdisk, kernel, libs) you can build a ROM for other devices using the the device specific stuff available in the CM7 git. (Desire HD, Nexus One, etc. can be built using the source on Git)
As I understand it, from my limited knowledge on this, the device specific stuff is where the difference lies, from the 2D and 3D drivers, to the overlays for every device, down to the kernel for each device.
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.
pongster said:
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.
Click to expand...
Click to collapse
Well said pongster
Sent from my HTC HD2 using XDA Premium App
Hes right,we have to treat our HD2 like a native android device otherwise were not gonna advance that far if we treat it like anougher device.Our HD2s are amazing so lets advance and be happy
I'm in no way a dev, but its great to see common sense prevailing. I wish I had more time to get my head into these ROM's/kernal's etc but I don't. And I for one am eternally grateful for all the hard work done on this site to keep the likes of me interested in the HD2. It's a crackin phone, lets keep it that way!
i agree with you in lots of things but some roms just have to be ported.
htc won´t release a sense build for the hd2 or just a rom to get ported.
guys that want sense just need a ported rom.
and sorry buti dont´t think this is right in the development section.
maybe you should contact them on irc
I agree it would be nice if everything was done just for the LEO, but Im not going to say anything bad about Typoon his ports rock, are uber stable, and anything but half baked.
The reason why the bravo/passion base is used is:
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
d) Sense ROM's aren't open source.
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal.
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!
DarkStone1337 said:
The reason why the bravo/passion base is used is:
Click to expand...
Click to collapse
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
Fixed- We only need to change the fingerprint of the build, same is done for bravo etc using passion fingerprint for gingerbread
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
Fixed - It works
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
Fixed - The CM7 nightlies and RC i am compiling.
d) Sense ROM's aren't open source.
Fixed - For sense Roms it isnt an option
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal. It is there lol
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!
i am not a dev but there are some roms in this forum that we must give credit to as not being half baked like motomans mytouch rom everything work on it and it is very snappy and responsive also typhoons rom is really good too i can see from there rom that there are those who really treat hd2 like a really android phone
I finally decided to ask a question that's been bugging me for a few days now, with all android development going around in a very impressive pace.
Now I am completly new to kernel concept so don't me too harsh if I said something wrong.
The question: Isn't there really a way to modify/update our kernel since we have locked bootloader?
As far as I understood, most of us are running ICS UI on top of GB kernel (even some on top of Froyo kernel) but this does not give us the advantage of running ICS on it full force and take full advantage of your harware.
I know Endless7 had a method to downgrade kernel, and I thought may be there can be a similar way to upgrade it.
With JB just around the corner, that would be a great improvement IMHO for our device.
Megalith27 said:
I finally decided to ask a question that's been bugging me for a few days now, with all android development going around in a very impressive pace.
Now I am completly new to kernel concept so don't me too harsh if I said something wrong.
The question: Isn't there really a way to modify/update our kernel since we have locked bootloader?
As far as I understood, most of us are running ICS UI on top of GB kernel (even some on top of Froyo kernel) but this does not give us the advantage of running ICS on it full force and take full advantage of your harware.
I know Endless7 had a method to downgrade kernel, and I thought may be there can be a similar way to upgrade it.
With JB just around the corner, that would be a great improvement IMHO for our device.
Click to expand...
Click to collapse
I'm no expert but I think this has to be done by motorola, since the kernel is the one responsible for the hardware management, and given the bootloader is locked we can't put custom kernels in our phone
Caesarivs said:
I'm no expert but I think this has to be done by motorola, since the kernel is the one responsible for the hardware management, and given the bootloader is locked we can't put custom kernels in our phone
Click to expand...
Click to collapse
Thanks for the reply. I do realize that and as Moto stated clearly that MS2 will not see official ICS there is not hope to get it from Moto.
But I thought maybe it can be ported from other device, or some modules, which share same CPU.
I am pretty sure our devs have looked into this but since we even got HWA working lol anything is possible these days.
There is a new bootloader hijacker called kexec which allows loading custom kernels. Hashcode is doing it for the Droid 3, and if I'm not wrong, it's designed specially for Motorola Phones with locked bootloaders. But you have to implement new drivers for video and such, so it's a lot of work.
Sent from my XT860 using xda app-developers app
elleypo Ière
Megalith27 said:
Thanks for the reply. I do realize that and as Moto stated clearly that MS2 will not see official ICS there is not hope to get it from Moto.
But I thought maybe it can be ported from other device, or some modules, which share same CPU.
I am pretty sure our devs have looked into this but since we even got HWA working lol anything is possible these days.
Click to expand...
Click to collapse
The problem is that it's not *only* a "same cpu" problem, it's the whole hardware solution.... camera, sound, gpu, and so on.
It's one of the reasons the dev on MS2 is so "slow", with the locked bootloader, non support from Motorola, the multiple versions (Droid2/Droid2 Global, MS2 EU/CH/NA and so on), getting the hardware to work (specially with newer android like ICS/JB is/was a pain, and most of the work was done "porting" those from the Defy/Atrix and so on who have, somewhat, partially the same hardware and can be adapted.
On top of that, changing the kernel as already said would mean to find a security flaw/hole in the bootloader that could be exploited for that.
(the downgrade solution was patched/fixed with the latest european, and now Latin America bootloader/kernel upgrades if i remember well, hence why most europeans who upgraded to the latest OTA don't really have a working CM7, since it requires to flash fixed sbf and other things to make it work (a patched recovery partition i think)).
But really, having the dev (forgot his name, danthingyabak ) getting full HW acceleration, and a working ICS port and pretty much everything working now, while LA and China starts getting remotely the same versions, we might see more develeoppement coming, since it's no longer "region specific" devs. Maybe even one day Droid 2/Droid 2 Global and MS will share the same developpements, who knows (or, maybe by Miracle, now that Google owns Motorola, maybe one day we will see unlocked bootloaders for all phone yeah i'm dreaming ).
What about us now?!
http://androidcommunity.com/motorola-finally-unlocking-bootloaders-for-real-this-time-20120726/
I hope it's true!
PS. But if it's not about us again, we hope that this method will work even be
xenusr said:
I hope it's true!
PS. But if it's not about us again, we hope that this method will work even be
Click to expand...
Click to collapse
I think that thing was just a false alarm...or early celebration...
Sent from my MotoA953
Looks like we're finally getting there
http://androidcommunity.com/motorol...live-finally-can-unlock-bootloaders-20120817/