Hello everyone,
I'm trying to compile my own source ROM for my Sensation 4g (TMOUS) My HBoot is 1.17.000 revolutionary unlocked. My compile from google source gingerbread 2.3.4 (to match version htc is using) went ok however with no lunch or envsetup option for the Sensation my full-user make showed compiling for generic. I have tried fastboot flashing my compiled userdata and system img files to my phone along with my default sense kernel (kernel from TMOUS rom 1.5 made from clockwork recovery) to find that it doesn't get past the white htc screen. I'm interested in compiling and sharing this ROM with the public however finding I'm a little lost on next steps.
In the court of public opinion, what would my next steps be? Is my lack of booting due to the sense kernel and instead should I try using a kernel like trinity cm7/asop kernel? Is my lack of booting even kernel related?
Any advice I would greatly appreciated and once I can get this thing running I will be glad to give credit where due and distribute any modified files. Also, if I run across any additional information that might help anyone I will update this post.
PS - I know ICS is out and it might seem odd to try with gingerbread to start (along with using 2.3.4 instead of 2.3.7) however my rationale is that by trying to stay as close to the gingerbread rom HTC provides version wise I might have the best shot at compatibility.
Thanks everyone.
Various ROM developers have IRC channels. It might be worthwhile trying and asking a developer on there, just don't bug them too much.
Related
Has anyone tried to use the new Kernel from Rogers Rom , to make roms wich need to be ported work on NEw radio? Thanks
well from looking at it, no one else has been releasing anythign since 2.1 came out but klothius and i, so hmmmmm.......
Sorry i didnt explain myself. For instance, we have now a new HTC kernel. Can this be used to port Cyanogenmod rom ? I would like to see how it worked with the nwe HTC drivers
not sure it would go well, cause if you take a kernel from cyanogen and put in sense, not everythign will work, might not even start, so going the other way from sense to aosp i don't think but who knows, or you could try out new .34 kernel we released in froyorider today
Am I the only one who is unhappy with the slim pickings of ROMs that are available for the SK4G?
Does anyone know anything about an ASOP ROM?
It's AOSP (Android Open Source Project) and you're not the only one not happy with the current SK4G options. I personally want MIUI or CM7, but seeing as we're currently stuck with Froyo, we'll have to see what the devs can cook up.
Sent from my SGH-T839 using XDA App
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
sduvick said:
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
Click to expand...
Click to collapse
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
ayoteddy said:
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And so anticipation had set in, i can't wait ayoteddy. im very excited. SMX was great, and SMGC was awesome, and now with this? whewwww. think i better go lay down, lol.
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Thank you for joining the Sidekick 4G section , & we welcome you but if you want you could pause the game's for the ROM if anything & Question 1 is a no & Question 2 no cause they have to be compiled with the 2.3 kernel .
- Said by Sduvick
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
Revolution, thanks for relaying my responses.
jmpz, I tried building the source before, but was unable to build it completely, but that was possibly because of some errors with my dependencies. The kernel compiles fine from source, you just need to pull initramfs, or you can get it from Dr. Honk's github.
Thank you for your answers.
So, can anyone enumerate the list of drivers which we should extract from kernel?
I can name these:
1) Keyboard
2) Mic
3) 2 speakers
4) buttons
5) front camera
6) rear camera
7) trackpoint
8) lcd
9) digitizer
10) 3.5 jack
Please correct me and add missing
If I understanding it rightly the key problem is getting proprietary drivers from the kernel. Right?
nope, the key problem is trying to build the system entirely, without any errors, which may be easier with someone following a stock designed build environment. I don't use Ubuntu which is what has the listed dependencies for every tutorial I can find. You can get the drivers out of Dr. Honk's voodoo kernel ramdisk here: http://forum.xda-developers.com/showthread.php?t=1145139
There shouldn't be any problems if you just set up a build environment following the directions in any of the tutorials, then add the platform from the samsung source.
I'm a linuxoid - so these tutorial are for me. Thank you for the link.
By the way, drivers are in Linux Kernel, so I don't think that I need to use Samsung Platform from the source. Instead I wanna use platform from AOSP or Cyanogen. Correct me if I'm wrong.
I think that grabbing drivers from kernel source from samsung would be enough to build the rom.
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
I 100% support your efforts. I want Cyanogen on the SK4G badly, but I'm not sure what kind of help a non-programmer like me could do, but do have some experience with flashing phones and such, so if there is anything you need let me know.
If you do get rolling heavily on this, I'd be willing to donate monetarily to your efforts.
If anyone can get CyanogenMod 7 on the Sidekick they would definetely get a donation from me. Id be thrilled. Glad to see its going to be worked on.
Sent from my Sidekick 4G using XDA Premium App!
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
I was wondering if anyone could point me in the direction of some information on porting from one version of android to a higher version. Preferably from 1.6 Donut to 2.2 Froyo or 2.3 Gingerbread. Is this even possible?
Also, could anyone tell me what phone I could use that is similar to the Behold II (SGH-t939)? Is the Behold II in the cyanogen repo? If it is, anyone know it's codename?
I have a build environment set up for cyanogenmod, and I followed this guide. I have got to the gpg import and was wondering if the gpg block is device specific somehow or if it is universal.
Tying in to my first question, is whether there is any way I could get the proprietary files and kernel information out of a rom file instead of off the phone. I have a custom rom installed on the phone that isn't working 100% but I don't really want to put the oem rom back on. Unless I absolutely have to.
Also, once I do actually get the proprietary information and kernel stuff, how exactly do I incorporate all that into a new build?
Sorry, I am just starting to learn about android development and need some guidance. Any help would be greatly appreciated.
Thanks