Database Develop

Fragamentation

I think HTC Tattoo, are to fragamented.
There should be only one rom, with all the developers, and them diferent packs with diferente window manager, apps etc..
Its a pitty that there is Roms based in CM6 but in CM6 website there is no maintainers for Tattoo..
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
Work togelher and we can go a long way...
P.S: Sorry for me English..

Start porting and developing MIUI than CM6....

inluxc said:
I think HTC Tattoo, are to fragamented.
There should be only one rom, with all the developers, and them diferent packs with diferente window manager, apps etc..
Its a pitty that there is Roms based in CM6 but in CM6 website there is no maintainers for Tattoo..
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
Work togelher and we can go a long way...
P.S: Sorry for me English..
Click to expand...
Click to collapse
I agree with you but I think that developers like approaching a rom in their own way

It's like with Linux. There's different distributions of it. Some prefer this, and some prefer that, like some wants to have Sense and some don't.
Regarding official CM for the Tattoo, I don't think they will do that unless at least the camera works. I would have loved it if some of their clever developers could have helped getting it to work, as that's about the only thing missing to make Froyo perfect for the Tattoo.

yes camera is the only thing missing to make froyo perfect but without help from htc i don't think anyone will make it work on froyo

[Question] Gingerbread on Tattoo?

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..)

Developing Sense ROM

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.

[RUU][DEVS ONLY][For Porting] HTC Pico [Sense 3.5][Android 2.3.5][Sense Zero]

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.

Samsung S2/S3 Rom on Captivate

Hello ,
few days ago i updated my gf's s2 to new JB that was leaked offical samsung but from odin, then i got an idea, cuz i have Captivate Armani I9010 and i was using Remics JB as last rom, cuz it was look rly nice likly s3 rom, but i didn't like aops dialer layout and some more staff and i got idea of porting S2 or even S3 rom to captivate, and i was playing with some tutorials and android kitchen but without lucky, as I have rly bad knowledge of programing thinks , but I'm trying and want to learn more, my point was that maybe its posible to use some custom aops rom as base(ofc if developer agree) and port s2 rom over, i know that to port stock apk's form s2 that i like i need to port aslo framework, but what else?
Is someone with knowledge are up to help me or take this project if it interesting?
Or if this is totally wrong , what is real way to go of port s2 rom to captivate? I'm sure that its posible i saw some video of s2 rom on i9000 with is pritty much same as capativate. (it was GB i think because video is old) but if it able to port one rom there is no difference but what is good way to start.
I am really sorry about my English , its not my main language, and I am interesting in learning as much as i can about android dev.
Ps. OR mabye it would be easy to just port some of apk instead of porting whole rom. (secphone seclaucher secmms seccontacts systemui etc etc)
Greetings.

bg.stefan90 said:
Hello ,
few days ago i updated my gf's s2 to new JB that was leaked offical samsung but from odin, then i got an idea, cuz i have Captivate Armani I9010 and i was using Remics JB as last rom, cuz it was look rly nice likly s3 rom, but i didn't like aops dialer layout and some more staff and i got idea of porting S2 or even S3 rom to captivate, and i was playing with some tutorials and android kitchen but without lucky, as I have rly bad knowledge of programing thinks , but I'm trying and want to learn more, my point was that maybe its posible to use some custom aops rom as base(ofc if developer agree) and port s2 rom over, i know that to port stock apk's form s2 that i like i need to port aslo framework, but what else?
Is someone with knowledge are up to help me or take this project if it interesting?
Or if this is totally wrong , what is real way to go of port s2 rom to captivate? I'm sure that its posible i saw some video of s2 rom on i9000 with is pritty much same as capativate. (it was GB i think because video is old) but if it able to port one rom there is no difference but what is good way to start.
I am really sorry about my English , its not my main language, and I am interesting in learning as much as i can about android dev.
Ps. OR mabye it would be easy to just port some of apk instead of porting whole rom. (secphone seclaucher secmms seccontacts systemui etc etc)
Greetings.
Click to expand...
Click to collapse
The best way to go about porting a ROM would be to ask one of your fav dev and read one hell of a lot!
Theming is fairly easy, you open the app with something like apktool and work your way through (or can use kitchen). As far as porting apps, it would mainly be the framework but you gotta keep in mind functionality that the Cappy doesn't have.
Reading and guides are really your best friends here. It can all be self learnt but it requires a lot of patience, gotta expect some good old headbanging lol
Here's a thread that could help you: http://forum.xda-developers.com/showthread.php?t=916814

Thanks,
I will probably start with port some apks but, as its not that hard job, but should like to learn how to port rom really i was reading some guides with was like its ok for any phone from same generation cpu like armv7 ported and base rom need to be same version, used same manifecture of device . and what i did used deo-dexed s2 rom JB 4.1.1 official one (aslo found one slimed s2 rom 4.1.1 aslo) and tryed few different as base CM10 for cappy was one of them its 4.1.2 but i think there is no big difference i tryed some 4.1.1 roms as base with was work on phone ok but when i made rom trought those guides its stack on bootanimation and logcat just spam that like every apk die
That was one of guides where it's says that it will work for all stock/cm/aokp roms ICS and JB updated.
There are few really easy steps and what i expected is that phone will boot and will be buggy as **** till a lot of tweaks but it didnt even boot ((
PS. I was looking around and i found that there are some custom rom (this was for s2 ) that are based on samsung base not aokp or cm. And they have all features of custom rom with all stock samsung look witch i like and stock phone/dialer/contact/tw/systemui/ etc etc/
My questions is there mabye that kind of rom for captivate or at least i9000 since i think its easier job to port from i9000 then from s2. And what would be base because last fw for cappy or galaxy s is GB, is there any posiblilty to get ISC or JB samsung based rom on this device?

bg.stefan90 said:
Thanks,
I will probably start with port some apks but, as its not that hard job, but should like to learn how to port rom really i was reading some guides with was like its ok for any phone from same generation cpu like armv7 ported and base rom need to be same version, used same manifecture of device . and what i did used deo-dexed s2 rom JB 4.1.1 official one (aslo found one slimed s2 rom 4.1.1 aslo) and tryed few different as base CM10 for cappy was one of them its 4.1.2 but i think there is no big difference i tryed some 4.1.1 roms as base with was work on phone ok but when i made rom trought those guides its stack on bootanimation and logcat just spam that like every apk die
That was one of guides where it's says that it will work for all stock/cm/aokp roms ICS and JB updated.
There are few really easy steps and what i expected is that phone will boot and will be buggy as **** till a lot of tweaks but it didnt even boot ((
PS. I was looking around and i found that there are some custom rom (this was for s2 ) that are based on samsung base not aokp or cm. And they have all features of custom rom with all stock samsung look witch i like and stock phone/dialer/contact/tw/systemui/ etc etc/
My questions is there mabye that kind of rom for captivate or at least i9000 since i think its easier job to port from i9000 then from s2. And what would be base because last fw for cappy or galaxy s is GB, is there any posiblilty to get ISC or JB samsung based rom on this device?
Click to expand...
Click to collapse
They can all be ported, it's mostly framework. Although, I never ported a ROM so I'm not the best one to guide you through this. If I'm not mistaken, there are guides in XDA-U. Also, there are quite a few nice Devs around here that could help you through it.

Thanks, I saw some of those guides some are generic some are on example but i for porting samsung (s2) based rom i need to use some jb base for captivate cm or aokp but there some difference when porting roms even if both base and port are same version JB . Cuz they are not on same base. And i hope it is not difficult to make. If it's not hard I would please ask some od dev to give me some guide. On what i have to take care . What to do and i will gief all effort and time to make it working.