Alright, so im itching to tryout the Blur ROM. Last night I wanted to try out the preliminary rom Drizzy had up on my 32A Magic. I figured since the rom is based off of cupcake a version of the cupcake kernel should make it work.
I then tried the rom with Cyan's 4.04 kernel. No luck. After this i tried watever kernels i had on my SD card at the time. So that included myhero, evilhero (these two were really just for kicks), hofo kernel. None of these worked.
So I wanted to know if you guys know which kernel will make it work if there are any existing ones which will make it work... And if not could someone make a kernel ? Thanks for the input
Yea, same problem here. Cant wait till someone ports it or points to a working 32a kernel.
Is there a nice Dev that has ported this over for us 32B handset users?
I am new to the whole rom flashing thing, and have been hesitant to root and flash my phone with the existing sense roms because I don't want to lose functionality and/or make my phone any more lagtastic than it already is.
The official HTC 1.5 Sense rom seems to be right up my alley.. And with a Dev porting it (perhaps with some of their slick optimization settings) that should make for one awesome rom to flash.
If anyone has some info, that would be awesome.
Thanks!
I second this. Show some love to your 32B counterparts.
this was asked yesterday
and it's been said countless times but the Dream forum is the place to go for 32B ROMs. You'll find that 32B gets more love than 32A does, actually
I don't want to lose functionality and/or make my phone any more lagtastic than it already is.
The official HTC 1.5 Sense rom seems to be right up my alley..
Click to expand...
Click to collapse
That's wrong, unfortunately. SenseUI needs more RAM than your phone has and will always make 32B devices lag. The G1 Devs have managed to get it to a usable state using Swap and tweaks but from what I know it's still that... laggy.
I've been searching and trying many different roms for the MT3g that are android 2.1, and there are many many talented developers on this website it's too hard to just try them all.
Can anyone point out there most "stable" and working rom for 2.1 32B they have use / are using
It's been annoying having to change and reflash different roms every other week for something new / need something else to work that I wonder if anyone has their preferred roms they could point out
Thanks in advance
icepally said:
I've been searching and trying many different roms for the MT3g that are android 2.1, and there are many many talented developers on this website it's too hard to just try them all.
Can anyone point out there most "stable" and working rom for 2.1 32B they have use / are using
It's been annoying having to change and reflash different roms every other week for something new / need something else to work that I wonder if anyone has their preferred roms they could point out
Thanks in advance
Click to expand...
Click to collapse
where have you been?? lol.. cyanogen mod 5.0.7... go check it out in the g1/dream forum...
oh yea it is marked as experimental but i think its pertty solid compaired to anyother eclair rom..
...and for new Radio?
...and for new Radio??
edit: nevermind, smoki is only for 32A
I'm at my wits end.. I've downloaded and compiled GB 2.3.5 to find no auto-rotate on my 9020A NS.. So I downloaded 2.3.4 and compiled that, STILL no auto rotate..
I downloaded and extracted into the code the 4 binaries from google but the accelerometer isnt among them.
Is this a problem for the AOSP builds of 2.3.4 and 2.3.5?
Am I nuts?
Is there a patch?
Any info would be awesome.
Take libakm.so from stock rom and put it in your build.
Worked perfectly! Thanks a bunch Pete!
As this thread floats into oblivion, if there is any interest in a unmodified completely 100% AOSP compile of 2.3.5 for the Nexus S, (I couldnt find one that was 100% unmodified, perhaps I didnt look hard enough) everyone let me know I'll produce a cwm zip of my build. I realize AOSP is easy for the semi initiated, but some people might not have the time/desire/knowhow,etc..
My goal of starting this is to port over some aspects of Honeycomb I like, including the launcher, lockscreen and what not by modifying existing functioning gb code..
Hopefully I'll finally make my first dev ROM in a couple of weeks.
Thanks again to Pete for the accelerometer fix.
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
kostistheo said:
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
Click to expand...
Click to collapse
hey mate
your're actually talking about two different things: porting a ROM and flashing a ROM.
Porting means, you take a ROM from another device and modify it so it works on your device too.
flashing means, you take a ROM which is already optimized for your device
and install it, so you wipe the stock firmware and get a custom rom.
which of the two things is what you want to do? i think its just the flashing.
so you can take any ROM from the "development section", and if you follow the guides that you can find everywhere here im sure you will be succesfull and happy with it.
bytheway
there is no "best" ROM for your device. it all depends on what you need and want. there are alot sense 3.5 Roms, Endymion 3.4 is the one i would recommend. you can also try AOSP ROMs (android open source project, means no sense), cyanogenmod7 could be a good first choice. and you can also try ics right now, since there are at least 3 (?) ICS AOSP ROMs right now:
CM9, Virtuous Quattro RC3, IceColdSandwich
have fun!
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
kostistheo said:
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
Click to expand...
Click to collapse
i would never recommend to flash an official ROM over a custom ROM. But anyways, i think if you would have done a full wipe before flashing the official rom you wouldnt have got a "you call it brick"
a real "BRICK" is a useless phone, where there is no way to use it again.if there is still a way, its no brick.. but who cares about definitions
I recommend you to flash the ROMs only through recovery mode. AND ALWAYS DO A FULL WIPE BEFORE FLASHING A NEW ROM. very important
and dont forget to backup as always
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Start flashing different roms and trying them for a day or two. First
Sens 3.0 and then sense 3.5 roms to see the difference. Only then you will know which rom is best for you.
+1 for Endymion 3.4,
+1 for Endymion
Swyped from my Desire S using XDA Premium
+1 Endymion
Sent from my HTC Desire S using xda premium
edymion, will try it
+1266592.23 for Endymion
kostistheo said:
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Click to expand...
Click to collapse
Each ROM type suits different personal tastes, so there isn't an 'best' ROM for everyone. Trial and Error which ones suit you!
General opinions:
Stock
Pro: Straight from HTC, *newest kernel/drivers*, least likely to have compatibility issues.
Cons: HTC is slow to release updates, and sense interface is usually resource hungry.
Sense-like
Pro: usually keep the Sense interface, but custom kernals offer speed / various other improvements.Runnymead versions are kernals ported across from HTC Sensation (which offer some of the goodies like Beats Audio etc. that were not originally developed for Saga.
Cons: Sense interface is resource hungry...
CyanogenMod based
Pro: offer lots of customisations
Cons: not the most user friendly
AOSP
Pro: Roms from the android source, usually less resource hungry, so lighter and faster.
Cons: Obviously, no sense.
ICS Alpha/Beta
Not strictly a new category, but builds from the new Android 4.0 (ICS).
Currently some things (like camera) isn't fully working yet.
Note: new Desire S may suffer from camera/video lag bug with non-stock / non-sense ROMs, this is due to HTC putting in new hardware / driver into the new DS phones and the other kernels not reflecting this change yet.
Personally, I use SenseMOD Lite V1.2 build 2 as it is one of the few AOSP like builds that don't have the camera bug. Oxygen would have been best choice for me but unfortunately camera bug makes it unusable.
Hey guys. I don't want to drive over your feet, but I think the OP is already very satisfied with all those replies. specially the post above is really trying to help, but you spend much time to type what has already been written on the first page.
I appreciate your intend to help, bit I think the OP isn't gonna read this anymore..
Btw: endy!...
Sent by my fingers to your head