Database Develop

Rosie.apk with Cyanogen Rom?

Has it been done? I couldn't tell if this http://forum.xda-developers.com/showthread.php?t=532822 is compatible with the cyanogen roms or this only applies for hero roms that have been worked with thus far. Otherwise, would love to see this done if possible.
Thanks for the input.

mekaziah said:
Has it been done? I couldn't tell if this http://forum.xda-developers.com/showthread.php?t=532822 is compatible with the cyanogen roms or this only applies for hero roms that have been worked with thus far. Otherwise, would love to see this done if possible.
Thanks for the input.
Click to expand...
Click to collapse
Rosie is tied to HTC's framework, trust me your not the first to bring this up.I asked this q months ago, even installed the rosie.apk and nothing happened.

Nope
Rosie is HtC Framework diffrent than Aosp Google

mekaziah said:
Has it been done? I couldn't tell if this http://forum.xda-developers.com/showthread.php?t=532822 is compatible with the cyanogen roms or this only applies for hero roms that have been worked with thus far. Otherwise, would love to see this done if possible.
Thanks for the input.
Click to expand...
Click to collapse
Not gonna happen, it relies on Htc's closed-source frameworks- thus only Sense based roms can use it (and older ones at that)
p.s. Post in the correct section next time

RE:
Think it will ever be open sourced or highly doubtful?
I mean, I without a doubt love kingklick's 0.6's rom, but it has some bugs that needs tweaking out such as everyone's problem it seems... the camera and bluetooth.
p.s. - please push this thread to Dream Q&A (sorry, my mistake).

mekaziah said:
Think it will ever be open sourced or highly doubtful?
I mean, I without a doubt love kingklick's 0.6's rom, but it has some bugs that needs tweaking out such as everyone's problem it seems... the camera and bluetooth.
p.s. - please push this thread to Dream Q&A (sorry, my mistake).
Click to expand...
Click to collapse
A mod will move it when they see it.
HTC wouldnt open source it unless they want it to be copied by other people which would be bad for business.The you would have hero widgets running on the liquid or droid and you get my point.

Froyo legend build

The source code for Froyo was released today
I am building a Vanilla Froyo rom for Legend, and should have the beta ready for download soon!

Great news
Just a stupid question: Froyo is available on AOSP. That means the sources of the OS are available. With this as a starting point, what is required to port it to a specific device (ie the legend)? Do you need the sources of the kernel (that HTC published), specific drivers (which ones?), something else?
Thanks!

MichaelAlexanderBull wel all love you!!!

gooooooood jub

Yeahhh!!!! Can´t wait.
Thanks!!!!

If you are succesfull, you will be our hero. Ohw and please put htc sens on it

This is really good news! I'm currently running the rom from Ali Ba, and I already prefer stock Android over Sense. Keep up the good work!

Great news!!!!
please let me enjoy legend without looking at my brother's nexus one with froyo

good news. cannot wait for the new ROM

qzem said:
If you are succesfull, you will be our hero. Ohw and please put htc sens on it
Click to expand...
Click to collapse
sorry i won't be able to put sense on it

MichaelAlexanderBull said:
sorry i won't be able to put sense on it
Click to expand...
Click to collapse
I think most of us would prefer it without sense ..

Y is sense so bad? I don't mind having sense maybe not the news and footprint but a lot of the sense I think its great
Sent from my HTC Legend using XDA App

I guess it will be very hard to port Froyo to the Legend because HTC devices often depend on com.htc.framework which will most likely not work with Froyo.
I'm going to try to port Froyo too once I get Vanilla Bean 0.3 ready, but this is hard work.
Sorry, not that I think MichaelAlexanderBull is doing bad work, but he simply doesn't have the source code for a few of the libraries needed to run HTC devices (especially some libraries that implement proprietary hardware calls). So don't expect a fully functional release.
I'm sure will see Froyo on the Legend though, just be patient.

ali ba said:
I guess it will be very hard to port Froyo to the Legend because HTC devices often depend on com.htc.framework which will most likely not work with Froyo.
I'm going to try to port Froyo too once I get Vanilla Bean 0.3 ready, but this is hard work.
Sorry, not that I think MichaelAlexanderBull is doing bad work, but he simply doesn't have the source code for a few of the libraries needed to run HTC devices (especially some libraries that implement proprietary hardware calls). So don't expect a fully functional release.
I'm sure will see Froyo on the Legend though, just be patient.
Click to expand...
Click to collapse
You know more than me, But im still going to try
EDIT:
I have managed to get the G1 port to boot and run on my legend in the past, it could recieve calls etc, but the touchscreen problem was there.
So i'm feeling confident that we will get a good stable release working with the ASOP release! Will probably take a bit of time, but it is going to happen

W00T!?
MichaelAlexanderBull said:
sorry i won't be able to put sense on it
Click to expand...
Click to collapse
NOT ?! You are fired!
Vanilla will be nice anyway
This is a good reason for me to root my Legend.

MichaelAlexanderBull said:
You know more than me, But im still going to try
EDIT:
I have managed to get the G1 port to boot and run on my legend in the past, it could recieve calls etc, but the touchscreen problem was there.
So i'm feeling confident that we will get a good stable release working with the ASOP release! Will probably take a bit of time, but it is going to happen
Click to expand...
Click to collapse
i'm sure you'll do just fine

MichaelAlexanderBull said:
You know more than me, But im still going to try
Click to expand...
Click to collapse
If my comment had made you run away and stop development I'd be very disappointed!
No, really, I'm confident you'll learn how to compile and port Froyo in no time. It's hard at the beginning, but once you get into it, it can be lots of fun too.
I wish you great success.

I would like to know if Flash would work in the browser.
That would be AWESOME

Froyo FTW
Cant wait for this ROM. It will be awesome
Will

you guys (michael and ali ba) should work together. this will make porting froyo to legend faster. =)

Rom cooking

so i am looking of getting into some rom and kernel cooking. haven't done it yet, but i am willing to give it a go. anybody have any tutorials on rom cooking? what do i need to set up to be able to create roms and save them etc.
any help will be appreciated. i am looking at starting to play with some HC for our beloved tablet.

I am going to stop dropping hints. Until we have all the drivers, a port will be useless. Ask all the devs over in the Vibrant Forums why theey still cann't get the GPS to work? Thye have had GB ported for a LONG time. But I'm not going to push this anymore. Now if Dell releases them, then we are in business, or if there is a possible way to extract the drivers from the stock img(s). Or if someone knows how to write the drivers for the hardware. And we will need a new kernel that is compatible with our device and hardware (that we do not have drivers for yet) because our stok kernel will only be compatible with froyo.
If you guys just wanna list reasons why I am wrong, don't waste your time typing them out. If i am wrong I will admit it if I am proven wrong. What I am hoping is that I am wrong, So prove me wrong PLEASE so we can get HC, if it is possible.

DJ_Steve who has worked with the streak 5 and has made other roms has said our kernel will work for gingerbread, it wouldnt work with HC without having to be recomplied but it should work with gingerbread. Also before you make the build you run a script called extract-files.sh (with your device connected via usb) and it will grab all the proprietary files and drivers that it needs from your working rom. and includes them in the build

i don't think i will get soo deep into cooking, but i will take my current rom and do a few mods to it, do a nandroid of it and post it here
i get home later tonight and i will try and work on something, but i won't promisse.

bogdi1988 said:
i don't think i will get soo deep into cooking, but i will take my current rom and do a few mods to it, do a nandroid of it and post it here
i get home later tonight and i will try and work on something, but i won't promisse.
Click to expand...
Click to collapse
Im ready to beta test them.

lou0611 said:
Im ready to beta test them.
Click to expand...
Click to collapse
i got home. will work on something for a couple of hours tops, but i won't promise anything.

ok. something with advanced launcher and a couple of extras will be coming soon.

ROM is up.

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.