Hi guys!
Since two days I'm trying to create a ROM based on HTC Sense, porting from HTC Desire to our Nexus One using, as a base, the RCADSmixHD ROM.
I've been able to complete the entire package .zip and installing succesfully, BUT at reboot I'm stuck at the Nexus logo...
Do you think it's a kernel-related issue?
I really don't have any other ideas...
EDIT: I'd also like to know how to develop/modify a kernel for our Nexus One, but based on HTC roms... Someone has guides/links?
Try to Flash this Kernel: 2.6.35.6-eViL--10-7--1-wmcfg by eViL D:
You can find dl link here : http://forum.xda-developers.com/showpost.php?p=16995049&postcount=2
I had problems with the kernel include in RCADS on my N1
Thanks but no changes here... BTW the kernel included in RCADS rom works with my Nexus.. But here in this new ROM that I'm trying to develop I don't know what's wrong...
My guess there's something wrong with the ROM itself you probably have a few lines of code somewhere that are not working right. Were you able to compile the code on your computer?
Well, actually I'm trying to port a Sense ROM from HTC Desire with 250mb fit into /system/... I think that's the problem because my Nexus One could have bad blocks and/or less space into /system/, so this ROM wouldn't fit. I think so.
Regarding the code, I haven't written any kind of code, apart from looking at updater-script to be ok... Other suggestions? Thanks anyway, much appreciated
Now I'm trying to port a different ROM, the Desire S Gingerbread 2.3.5 with Sense 3.0!
But after replacing many folders and files from a Sense Rom of the Nexus One and the target Sense Rom that I'm developing, I have replaced boot.img and edited the updater-script properly (I think).
After installation, it's stuck at the Nexus logo... always!
What's wrong????????
Look at your logcat.
And at your /proc/kmsg.
If you don't know what these 2 mean - read up on those, use some googling.
If you can't - I believe you won't be able to develop anything worthy, or anything at all.
Moreover, Nexus has 145MB on /system partition. You need to utilize SD-EXT partition and symlink parts of the ROM to make it fit.
If I'm speaking Chinese and you can't figure it out - read the previous paragraph
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
rugmankc said:
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
Click to expand...
Click to collapse
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Iperzampem0 said:
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Click to expand...
Click to collapse
What did you add to the updater-script? And which folders specifically did you replace and change? And did you use a rooted ROM or the OTA one for the desire?
@Ace42:
Hi, I had used a rooted ROM from the Desire thread and I have followed this pretty useful guide which illustrates how to port Sense Roms:
http://forum.xda-developers.com/showthread.php?t=1222746
I have also had a look at almost all the files into each folders to see if there was differences in the code between the 2 roms..!
BTW the problem is in the updater-script...
For example I'm not able to mount "sd-ext", which is one of the most important steps to do for the Rom to being able to run into the device.
Look at that link properly, porting sense to OTHER SENSE DEVICES.
N1 isn't a sense device.
First, porting is more than replacing your boot.img and changing your update-script.
Like the other user said, you need to symlink files to your SD card cause N1 just isn't big enough.
Second, you're taking roms from other devices, most probably you'd have to re-write or mod the drivers.
Third, Porting just isn't that easy.
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Iperzampem0 said:
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Click to expand...
Click to collapse
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
illuminarias said:
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Iperzampem0 said:
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Click to expand...
Click to collapse
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
@Deep-Knight:
Yep, I was working yesterday evening with the official Desire gingerbread update from HTC, but, as always, I'm stuck at the Nexus logo, after the installation is done... :/
I think I'm doing something wrong with system partition.. I know that our N1 can handle only 150mb for /system...
But I must admit that I'm using almost the same updater-script and boot.img as the N1Sensation v0.5 rom or RCADSmixHD rom..
Deep-Knight said:
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
Click to expand...
Click to collapse
Just make a thread and upload your beta version, theres a plenty of people here able to test and help.
Thank you Menelkir for your interest!
But first I'll have to create something useful.. Maybe later on I'll create a new thread..
Till now I'm using some HTC Desire's ROM from the dedicated section here at XDA.
Stay tuned guys
As always graphical glithces will not be solved, until HTC releases Desire's Source Code..
The code is released already.
Unfortunately, the real trouble with porting ROMs is fixing the things that don't work - which will include trackball, hotspot etc - and this is the part where most of ROMs fail, because very few developers are skilled enough for that.
Related
Ok, so i began porting Froyo to the Legend this morning.
So far ok, It boots.
But the touch screen does not respond? I can use the optical pad to select things, i can recieve calls. but that is it. I need to use the touch screen to test if other things work.
Any hints?
Total noob here, so just guessing, but do you have all the necessary drivers?
Well i am using the stock rom as a base.
Just using Basic Kitchen to port it, So I'm not too sure if i am meant to add extra things to it, i assumed that the kitchen would extract the drivers from the stock rom into the port one?
I'm not an experienced dev at all, just that no-one seems to interested in the Legend so i thought i would give it a shot.
MichaelAlexanderBull said:
Well i am using the stock rom as a base.
Just using Basic Kitchen to port it, So I'm not too sure if i am meant to add extra things to it, i assumed that the kitchen would extract the drivers from the stock rom into the port one?
I'm not an experienced dev at all, just that no-one seems to interested in the Legend so i thought i would give it a shot.
Click to expand...
Click to collapse
Unfortunately I'm even less experienced than you, so I cannot help you here. Perhaps one of the more experienced chefs can chime in here?
But if you manage to make a working ROM and you need help with testing, I'd be glad to give a hand ..
give me a week (or 2) and I'll join in on the froyo cooking (exams + party time).
I do think you should copy the driver files from the latest available official rom... which one 2 copy and which one not 2, that's a guess, trial and error ?
Yeah, i've been trying to, just that there are so many different files. (222)
I'm not even sure if i am in the right folder haha!
Is it the System/lib folder where the drivers are?
or the System/bin folder? Or is it somewhere completely different!?
It looks like the drivers is in /system/lib and in /system/bin the android file system tools. I'm just a n00b so I could be wrong but when I ls /system/lib it contains libcamera.so and other driverlike files. So i'm guessing it's the place to look.
MichaelAlexanderBull said:
Well i am using the stock rom as a base.
Just using Basic Kitchen to port it, So I'm not too sure if i am meant to add extra things to it, i assumed that the kitchen would extract the drivers from the stock rom into the port one?
I'm not an experienced dev at all, just that no-one seems to interested in the Legend so i thought i would give it a shot.
Click to expand...
Click to collapse
Which stock rom do you mean?
SDK ?..........................................
Eh, the Rooted WWE 2. something rom - the newest one.
maybe you can put it on modaco too?
Yeah i will when i have finished, I am making progress but don't expect much as the build i am porting barely works on the G1 atm.
But it will get better
I'm also trying to port the G1 Cynanogen rom aswell, but same driver problem! so trying to figure out what the hell to do atm haha
EDIT:
AAAAH, Someone help me... I have the drivers i need for it too work, i got them from the HTC legend kernel source code?
So How am i meant to put these in the new ported kernel? as i cannot open the boot.img in windows?
Maybe you should contact rodriguez for info. He was able to customize the modaco rom. I think it's nice to see someone trying. Keep up the good work m8
OK, I contacted Rodriguez.
He says he does not think the Froyo rom i am porting will work :/
So i will hold this rom at the moment, until someone can help me.
But instead i will begin to try and remove sense from MoDaCo r2, should be easyish
that's nice a rom without sense I would like that very much
good luck with it.
I hope the froyo port will work eventually
I have made a rom without sense (ish)
I stripped the R2 but there are still some sensish things, as the HTC keyboard looks and works much better, and the top bar is still black, but apart from that it is stock 2.1
I had one FC first time i flashed it, but it has not come back.
I will upload tonight, as i have to go to school now.
MichaelAlexanderBull said:
I have made a rom without sense (ish)
I stripped the R2 but there are still some sensish things, as the HTC keyboard looks and works much better, and the top bar is still black, but apart from that it is stock 2.1
I had one FC first time i flashed it, but it has not come back.
I will upload tonight, as i have to go to school now.
Click to expand...
Click to collapse
i can't wait for this rom can you please make it with livewallpaper?
Aargh. I was looking forward to froyo on our legend. Maybe we have to wait for the official release, that is if we will get it. Well thanks for trying
MichaelAlexanderBull said:
I have made a rom without sense (ish)
I stripped the R2 but there are still some sensish things, as the HTC keyboard looks and works much better, and the top bar is still black, but apart from that it is stock 2.1
I had one FC first time i flashed it, but it has not come back.
I will upload tonight, as i have to go to school now.
Click to expand...
Click to collapse
Can't wait for tonight
MichaelAlexanderBull said:
Ok, so i began porting Froyo to the Legend this morning.
So far ok, It boots.
But the touch screen does not respond? I can use the optical pad to select things, i can recieve calls. but that is it. I need to use the touch screen to test if other things work.
Any hints?
Click to expand...
Click to collapse
Hello,
You seem to be doing an interesting attempt.
In the case of HTC Legend, I think that the touchpanel control-codes are different from other devices. (such as Nexus One
----
# getevent &
...
add device 6: /dev/input/event1
name: "synaptics-rmi-touchscreen"
...
/dev/input/event1: 0003 003a 00000001
/dev/input/event1: 0003 0039 8ddb05f5
/dev/input/event1: 0003 003a 00000001
/dev/input/event1: 0003 0039 8de005f3
/dev/input/event1: 0003 003a 00000001
/dev/input/event1: 0003 0039 8df305f3
/dev/input/event1: 0003 003a 00000001
/dev/input/event1: 0003 0039 8df305f5
...
----
Basically, most case of multi-touch-type, touchpanel drivers report 0x35(MT_POSITION_X)/0x36(MT_POSITION_Y) and more.
However, Legend's one reports only 0x3a(MT_AMPLITUDE)/0x39(MT_POSITION).
According to the source code of AOSP, these control codes are NOT DEFINED in RawInputEvent.java.
Therefore, there are two solutions.
1. Modify the kernel driver (synaptics_i2c_rmi.c) and rebuild
with CONFIG_TOUCHSCREEN_COMPATIBLE_REPORT.
# however, i'm afraid that it is enough...
2. Modify RawInputEvent.java and KeyInputQueue.java
to let Android to receive control codes(0x3a/0x39).
# Now it cannot test because FroYo has not been released yet but it is effective in AOSP Eclair on Legend.
Thanks,
k-yosa
Hey guys,
Now that Gingerbread is out, I think most questions on people's minds are: Can it happen? What's needed?
Sent from my Tattoo using XDA App
I'm trying to do something about it stay tuned...
i just saw a youtube video about a wildfire running an early built,
so i thinks its not a matter of resolution.
I just hope the CM can be work on ROM.
We need AOSP sources before it can be built properly. The ones on Wildfire etc are just hacked together from an emulator image, and they run quite slowly. For the Tattoo, I'm a bit uncertain if it can be used with kernel 2.6.29, or if 2.6.32 or higher is required.
It will eventually - Froyo took a while but is here. But I can't wait for the new UI and it will be speedy if Google are telling the truth
I was WAITING for someone to ask this question
Anyway, fingers crossed
It has to be possible: http://androinica.com/2010/12/07/go...droinica+(Androinica+-++A+Google+Android+Blog)
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
aliwaqas said:
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
Click to expand...
Click to collapse
I guess it will be pretty soon, because Gingerbread AOSP is already available to create ROMs like fyodor's or spartm's, and Cyanogen is working on modded Gingerbread too already
gingerbread on tattoo would be GREAT
Sent from my HTC Tattoo using XDA App
@those who try to port 2.3 for tattoo: If you're successfull, plz change the icon for mobile data... it's just too tiny for our small screen!
the source code for the nexus one is out, i dont know how difficult it is to port it to another device but i hope someone tries it already
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Aaroneke said:
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Click to expand...
Click to collapse
Stuck when compiling or when booting?
Compiling i've managed this problem, but i changed some stuff and now i got it again, i'm trying to make new vendor files step by step using fyodor,..etc (and google ref) files just for reference, but it can take a while(if i'll get it working..)
Hey guys I'm a noob and sprint decided to give me a hero do to my defective noment I took it over the intercept because of the support here on XDA and I've been lookin around and I like but my question remains what's the best rom for the cdma hero that will still allow the flasplayer to work any ideas or ways to keep makin it work. THANX
Unfortunately, full flash support can not be achieved. There's a light version out there, but I don't know how well it works.
charlie95113 said:
Hey guys I'm a noob and sprint decided to give me a hero do to my defective noment I took it over the intercept because of the support here on XDA and I've been lookin around and I like but my question remains what's the best rom for the cdma hero that will still allow the flasplayer to work any ideas or ways to keep makin it work. THANX
Click to expand...
Click to collapse
I believe Nfinite's Roms have Flash Lite, and then using a browser like Skyfire gives additional flash support as it deals with it server side.
Use Nfinites rom http://forum.xda-developers.com/showthread.php?t=849024 there and then do a search for Zen's Any Kernal with no Perflock. It makes it an extremely snappy Sense Rom. Only Sense has the Flash working, none of the AOSP roms do I believe.
Only downside is Nfinite is on Hiatus due to some personal stuff but he has popped back in and said he isn't gone, just dealing with it and plans to update again soon.
my replyo
ok thanx so fo example even I port the flash light apk (htc flash player) can I at least use that on the aosp rom or the cm 6 or does they need the sense to even aollow it to work ? I just want to be ready to root asap when the hero arrives tomorow
You cannot use those functions in an AOSP rom, has to be with sense.
Ok one last thing before I do this once I get my recovery going and I'm rooted of course I do a data wipe then apply a zip (rom) file correct and if I want to try other roms repeat the proscces. Right just want to make sure. That's how I would do it on my moment
charlie95113 said:
Ok one last thing before I do this once I get my recovery going and I'm rooted of course I do a data wipe then apply a zip (rom) file correct and if I want to try other roms repeat the proscces. Right just want to make sure. That's how I would do it on my moment
Click to expand...
Click to collapse
Yes you would go to recovery, do a factory reset, wipe Dalvik, Cache, etc and then you can flash the new zip for the rom you wish to try.
Most roms will have a sort of guide or instructions, some have things specific to the rom being flashed, so make sure and read the full post, and maybe browse the thread for tidbits that users have had to say about the rom.
Sent from my Dark Horse CM6 Hero using XDA app.
What is porting a rom? I think it is just taking a rom from different phone and making it work on another device....is that right?
If that is right I want to port a rom or roms from the Nexus One to the HTC Hero CDMA.
But can anyone list what tools and knowledge I will need? I'm running windows 7. So any programs or books I need to read can someone give links to information about the book, or links to download/buy the program that I'll need to get started on porting roms to our HTC Hero CDMA.
Also can someone tell me the pros and cons of porting roms as well?
Thanks, I can't wait to get started on this
Try using the ultimate theme injector is what I've been using
Sent from my DROIDX using XDA App
If you really want to get into it I suggest running a Linux distro. I run ubuntu 10.04. Haven't had windows on my computer since August of last year. Took a little while to get use to, but I now like it better. Also gives you the ability to get repos, compile Android and kernels, and much more.
Depending on what you are porting it might require new drivers, xml edits and resizing, the theme injector will only do so much. I think it will only replace and resize images.
Sent from my dual-booted liquidsense 2.1
spleef said:
Try using the ultimate theme injector is what I've been using
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
so i use this for resizing/replacing images.....
unCoRrUpTeD said:
If you really want to get into it I suggest running a Linux distro. I run ubuntu 10.04. Haven't had windows on my computer since August of last year. Took a little while to get use to, but I now like it better. Also gives you the ability to get repos, compile Android and kernels, and much more.
Depending on what you are porting it might require new drivers, xml edits and resizing, the theme injector will only do so much. I think it will only replace and resize images.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
and then you say use my linux distro for everything else.....but where are the links tutorials/books i need to read/tools i'll need to get started on the rest of the stuff for porting roms?
thanks for helping btw
Have you built any roms yet? I'd suggest getting a kitchen and playing around with a known good rom - get used to what's there, what you can change, things like that. I've been playing around with dsixda's HTC Android Kitchen (on WinXP using Cygwin) lately with a few ROMs (my stock rom, liquid sense, aosp, and CM6). That's the best way to learn IMO.
TJinWV said:
Have you built any roms yet? I'd suggest getting a kitchen and playing around with a known good rom - get used to what's there, what you can change, things like that. I've been playing around with dsixda's HTC Android Kitchen (on WinXP using Cygwin) lately with a few ROMs (my stock rom, liquid sense, aosp, and CM6). That's the best way to learn IMO.
Click to expand...
Click to collapse
OOOOOOOOOH!!!!!11
that sounds like that might actually work....once i get a kitchen set up on linux mint. play around with a few different roms and see what i'm able to change, find out what it is that i'm changing and what changing it does.....AAAAHHH YOU'RE A GENIUS!
That sounds like that will work for learning to begin to develope beginner roms, and improve roms.
But now that you've got me set for like the first few months of learning. I don't want to post another thread about porting roms, so anyone know any information on porting roms? I know the user above said use a theme injector but that is for resizing and editing the images of the rom im porting. There has to be more to porting a rom than just resizing images. I'm trying to get all my information ahead of time so that i can just jump into developing with little to no questions for our device
kifno, that kitchen also has "experimental" porting tools in the Advanced Menu. I meant to say that in my original post.
TJinWV said:
kifno, that kitchen also has "experimental" porting tools in the Advanced Menu. I meant to say that in my original post.
Click to expand...
Click to collapse
Thanks for letting me know. Now once I begin porting roms I'll have at least a start. Thanks everyone
Sent from my DROIDX using XDA App
kifno said:
Thanks for letting me know. Now once I begin porting roms I'll have at least a start. Thanks everyone
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If your open to Suggestions... Try going to theunlockr.com, and Select the "How to's" Then Look for the Rom Development section... Know what, I'll do it for you!
Hold on!!
Ok here you go:
Watch these videos, see if they Help you out a bit!
http://theunlockr.com/category/howt...-development-how-tos/rom-development-how-tos/
Sent from my Hero using XDA App
From the Hero section:
flashinglights said:
Found this while searching around google. It's a leaked RUU for the HTC Pico "explorer" which is a light version of Sense 3.5 on android 2.3.5 or most commonly known as "sense zero". I thought I would post it up so that you'll can start porting over to the hero.
The Pico specs are rather similar to our phone so it shouldn't be to difficult for someone to port it over, it's also mdpi so no resizing will be necessary.
If you are already considering taking on this project then more than likely you already know how to setup a flashable rom from a ruu but in case you need some refreshing the following will help:
Instructions:
- dsixda kitchen will need to be installed prior to starting.
1. Run RUU and leave open
2. Type %TEMP% in your computers start menu search bar.
3. Search through the folders in there with the long names with numbers and letters, you'll find a zip file named "rom.zip" in there.
4. Place the rom.zip in the original_update folder located in the "kitchen" directory
5. From there follow the steps on the kitchen menu to setup the rom.
6. Then proceed to porting to the hero. :]
- Download Pico RUU
Credits to capychimp for posting the leak up.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1275108
First ROM port to Hero: http://forum.xda-developers.com/showthread.php?t=1284083
EDIT: Sorry, i read this on the XDA front page where they wrote that Pico has QVGA resolution which apparently it has not. It´s HVGA.
...The interesting thing about the Pico is the fact that it is loaded with Sense 3.5, which happens to be called Sense Zero for this particular device. Due to having similar specs such as QVGA resolution and ARMv6 processor....
Click to expand...
Click to collapse
EDIT 2: It boots on QVGA brother Wildfire: http://forum.xda-developers.com/showthread.php?t=1285694
Now that is a progress.....
Sent from my HTC Tattoo using xda premium
Wow, fingers crossed. There haven't been any bigger breakthroughs ever since KalimochoAz figured out the cam drivers for 2.3...
I dont think this would be possible.. First of i dont think the tattoo is capable of running it smoothly enough.. And second the Hero's resolution is bigger than the one on the tattoo, so it would need to be resized..
And last .. Im afraid theres no devs with enough skill back with a tattoo
I'm interested on working on this but I have never worked on a rom before. I just have experience in java/c++ and some android app programming. Can anybody point me to the right direction? I think i can devote much time to this project.
i hope if this can be run on tattoo )))
KrisInfinity said:
I'm interested on working on this but I have never worked on a rom before. I just have experience in java/c++ and some android app programming. Can anybody point me to the right direction? I think i can devote much time to this project.
Click to expand...
Click to collapse
From what i can remember on my time with rom cooking you will need a so called "Rom kitchen" .. Try searching for it here.. Maybe you could ask someone who has more experience, and get them to point you to the right direction ?
Following links are at least a start
[DEV][SENSE] Porting sense to other sense devices
How To: Create Your Own Custom ROM for Android
[KITCHEN][September 10 '11] Android Kitchen, v0.179 [Linux / Mac / Windows]
Thank you for the links. I'll be starting right now reading.
KrisInfinity said:
Thank you for the links. I'll be starting right now reading.
Click to expand...
Click to collapse
you might want to consider my earlier post to have more system space, while you work on porting
[SCRIPTS][GUIDE] Resizing Tattoo partitions
it would give you flexibility to flash these ROMs with out an issue of system memory.
rallapag said:
you might want to consider my earlier post to have more system space, while you work on porting
[SCRIPTS][GUIDE] Resizing Tattoo partitions
it would give you flexibility to flash these ROMs with out an issue of system memory.
Click to expand...
Click to collapse
Thank you.
I had a look at the Wildfire section and saw a similar project. They had managed to get it booting, but at the moment it was unusable.
http://forum.xda-developers.com/showthread.php?t=1285694
In the meantime, to get more comfortable with the tools and development I've decided to resume the development of the Sense 2.2 Rom port from the wildfire.
KrisInfinity said:
Thank you.
I had a look at the Wildfire section and saw a similar project. They had managed to get it booting, but at the moment it was unusable.
http://forum.xda-developers.com/showthread.php?t=1285694
In the meantime, to get more comfortable with the tools and development I've decided to resume the development of the Sense 2.2 Rom port from the wildfire.
Click to expand...
Click to collapse
Hey good thinking, then you could use following ROMs as base (not exclusive):
Build Number : 2.37.415.1
Android Freedom Wildfire 2.2.1 Arabic sense
STEAM V1.0 by o TRiPPiNz (Also supports Arabic for Arabic users)
Based on official: 2.34.75.1
WildPuzzleROM_2.2.1 v0.8
as you know TatFroyoSense is based on build 2.22.405.1
2.22.405.1 r1 - MoDaCo Custom ROM (Froyo 2.2.1)
Later version had the contacts apk fixed and the live wallpaper support and slightly faster.
I could build a dirty ROM from DanneJo's Wildpuzzle ROM, but it has problem with wifi and accelerometer.
a dirty hack had activated wifi.
I am not a dev and had very poor programming experience.
If you can do this project, that is best for us to get a decent product.
rallapag said:
Hey good thinking, then you could use following ROMs as base (not exclusive):
Build Number : 2.37.415.1
Android Freedom Wildfire 2.2.1 Arabic sense
STEAM V1.0 by o TRiPPiNz (Also supports Arabic for Arabic users)
Based on official: 2.34.75.1
WildPuzzleROM_2.2.1 v0.8
as you know TatFroyoSense is based on build 2.22.405.1
2.22.405.1 r1 - MoDaCo Custom ROM (Froyo 2.2.1)
Later version had the contacts apk fixed and the live wallpaper support and slightly faster.
I could build a dirty ROM from DanneJo's Wildpuzzle ROM, but it has problem with wifi and accelerometer.
a dirty hack had activated wifi.
I am not a dev and had very poor programming experience.
If you can do this project, that is best for us to get a decent product.
Click to expand...
Click to collapse
Thank you for the links.
I've also seen RemPuzzleRom which is a continuation of WildPuzzleRom and contained some interesting hacks, especially one on keeping the launcher in memory (which TatFroyoSense lacked).
I'll try porting STEAM tomorrow and see how everything works. Once I get some concrete results I'll start a new thread as this is moving away from the original topic.