Database Users

Android for HTC Touch / Elf

Hello,
I'm french, so please excuse-me for my eventually English mistakes.
I've seen that topic : http://forum.xda-developers.com/showthread.php?t=385129&page=10
But I don't see if there is a application for HTC Touch or HTC Elf in order to have the famous Android from Google. I've seen on the Internet that there was the application for HTC Vogue, but it doesn't work on our phones Touch / Elf. (white screen)
Is this application exist ? Or is it in developpement maybe ?
Thanks for your answers.

There aren't any applications. Android is an OS, like Windows Mobile. You can choose between WM and Android, but can't have both on your Elf.

Ok. Thanks. So how can I have Android on my HTC Touch ? I need to change my rom if I've understand. But where is it ?
Thanks.

there is no android rom for the elf. only for the elfin.

freaksey said:
there is no android rom for the elf. only for the elfin.
Click to expand...
Click to collapse
never heard about this one... just linwizard on elfin for now

ehh i'm sorry, it's not a rom yet, but you can boot it from wm
-> http://forum.xda-developers.com/showthread.php?t=382265

freaksey said:
ehh i'm sorry, it's not a rom yet, but you can boot it from wm
-> http://forum.xda-developers.com/showthread.php?t=382265
Click to expand...
Click to collapse
It's for Vogue, not Elf or Elfin.

Android??? Elfin??? GOOGLE!!!!
Can anyone confirm if the Android OS will be avalable for Elfin units please????

I don't think there will be any official version. Maybe some Elfin user will create it.

was anybody successful with running that on an elfin?!

Android on htc touch/elfin
this is the phone i am talking about
http://pdadb.net/index.php?m=specs&id=952
OK so i am trying to get all the info together first before i brick this phone so i am doing alot of tech research below is everything i could find for this device
if you have more info please add. and eventually it will all come together.....I hope
This is info i researched for the phone i will use it to make a default.txt
# TMOBILE mda TOUCH 256, ELF0300, HTC elfin 0300
# this is an over view of my devices settings and tech info.
#
# Storage on device is........ 173.79 mb
# storage card is.............. 964.50 mb
#
#DEVICE INFORMATION
# rom version.................. shadow_2.1 WWE
# rom date .................... 10/02/08
# Radio version................ 03.08.90
# Protocol version............ 4.1.13.52
# ExtROM version............ Touch-edition
#
# HARDWARE
# CPU........................... 32 bit texas instument OMAP_850
# CPU core................... ARM926EJ-S
# Instruction set............ ARMv5TEJ
# level1 cache .............. 16KiB D-Cache / 8KiB l-Cache
#
# phone controller............ TI TMS320C54x
# CPU CLOCK/Speed .......... 201 Mhz/ 201 000 000hz
# rom type .................. FLASH EEPROM
# RAM size..................... 128 mib
# FLASH ROM size ......... 256 mib
# DATA bus ................. 16 bits
# display resolution....... 240 X 320
# Display type ............. color transflective TFT, 65536 scales
# display diagonal......... 2.8 inches
# colors 65536
# microphone............ mono
# loudspeaker........... mono
# audio output ......... proprietary
# cellular networks..... GSM900, GSM1800, GSM1900
# cellular data links...... CSD,GPRS,EDGE
# call alert ................. 64 -chord melody
# vibrating alert......... supported
# speakerphone............ supported
# audio controller.......... AGC
# Bluetooth................ 2.0
#
#CONTROL PERIPHERALS
# positioning device......... touchscreen
# primary key board......... not supported
# directional pad............ 5-way
# scroll wheel................ not supported
#
#INTERFACES
# Expantion slot.............. microSD,microSDHC,Transflash,SDIO
# USB.......................... USB 1.1 client-12Mbit/s mini-USB
# wireless lan................... 802.11b, 802.11g 54Mbit/s
# infared ....................... not supported
#
# main camera................. 1.9 mp
# optical zoom............... 1x
# battery capacity............ 1100 mah
#
# IDENTITY
# model number.............. ELF0300
# Platform..................... Pocket pc
# IMEI ......................... 35678901099446301
ok that is all for now here is to hoping

freaksey said:
there is no android rom for the elf. only for the elfin.
Click to expand...
Click to collapse
I've got the elfin but I can't find the rom.
Thanks.

really interested in this.... The Htc Vogue (another processor) has achivied this, The Htc Niki too.. but they are not OMAP like elf or elfin...

I'm also very interested in this android "rom"
I read that some people was successful with the linuxboot on elfin.
Is there anyone who knows how to achieve it?

Martin2 said:
Hello,
I'm french, so please excuse-me for my eventually English mistakes.
I've seen that topic : http://forum.xda-developers.com/showthread.php?t=385129&page=10
But I don't see if there is a application for HTC Touch or HTC Elf in order to have the famous Android from Google. I've seen on the Internet that there was the application for HTC Vogue, but it doesn't work on our phones Touch / Elf. (white screen)
Is this application exist ? Or is it in developpement maybe ?
Thanks for your answers.
Click to expand...
Click to collapse
it won't run on the htc touch's CPU

THIS IS OUR ONLY CHANCE, buy that sucker somebody
http://www.engadget.com/2009/02/10/keepin-it-real-fake-part-clxxxii-hkc-touch-clone-sports-andro/

Ok, here's what I have found after a day of very disappointing reading:
There is a WM booting version of android for the vouge (which is a qualcomm processor)
That processor is also the same (similar) architecture as the one in the dream/g1. Which is why it works I assume. As a result the rom should also work on the titan, diamond, HD, etc.
As for the Elf and Elfin. They use the TI OMAP 850 board. Google did write a version of android that worked on that board for a tech show, but it has not appeared anywhere around in a usable form for a phone. (No USB or keyboard or anything)
IMO someone should just have to take the kernal from that example and the development for the vouge and run with it
But that is probably way harder than it sounds (and hasn't happened yet as far as I can tell)
Also, the severe limitations of the Elf's ram will mean it probably not work booting from WM (since it needs 32mb at a BARE not even usable minimum)

The Herald forums has been porting android to the Omap850. They're still early on in the development stages, but I would imagine that helping them out (for those of you who can actually program and make drivers) would set a layout to port it easily to the elf (since they have the same CPU and chipset.)

Please DO NOT GIVE UP. I want android on my Elf

Android ROM can resolve the problem of the Bricker HTC with CID locked ?
How ?
it's possible to install Adroid ROM from bootloader !! with SD card (FAT32) Now ?

[Q] From Android back 2 WinMobile?

Hi there,
I want to make first steps in Android on my HTC HD2, but I´m unsure to do it.
The Problem is - I have absolutely no practice on Android and need to switch back to WinMobile if I don´t like AndroidOS...
Is there a way to switch back in case of wurst case?
Sorry for that bad english, but schooltime was a long, long time ago...
Update:
I thought, android replaces WinMob... Am I right? some threads made me unsure..
Or will Android simply running in a VM on WinMob?
Thanks for help
Patrick

Hi Patrick,
Let me try to answer that one before someone hits you that you have to start reading!
There is absolutely no problem to test this out!
All that happens is that you start Android from WinMobile so Winmobile will stay on your HD2.
You have to 'install' Android on your SD-card. I placed 'install' between ' ' because you just copy the files on the card and it works like that!
If I was you I would get a clean SD-card and copy the Android build on it.
Just make sure that you have a folder called Android with files called Zimage etc copied in that folder. Copy the 1GB data.img file also in that Android folder (makes 1st start faster).
So now that you have done that just maybe reboot your HD2.
Go to your speicherkarte and VERY important !! click first CLRCAD.exe. It will do nothing but it is needed. Then you can press haret.exe which will start Android.
The first time it can take minutes.
Ok now go and enjoy Android and use the search button to look for answers and problems.

OK, Thanks...
I´ve started reading a lot, but it was still too much for me...
All I needed to know was answered by you in 20 words, I hoped to become an answer like this...
thanks a lot

Happy android, bro
try the angry bird and guns&glory, the phone will glue on your hand whole week XD

[email protected] said:
OK, Thanks...
I´ve started reading a lot, but it was still too much for me...
All I needed to know was answered by you in 20 words, I hoped to become an answer like this...
thanks a lot
Click to expand...
Click to collapse
Android ersetzt WM nicht, es wird einfach nur von WM aus von der SD-Karte gestartet. Wenn du dein HD2 wieder neustartest wird WM wieder gestartet
Wenn dir Android nicht mehr gefällt (was ich bezweifle) schmeißte es einfach von der SD Karte runter und gut ist

good form
nice to see a noob question not being flamed, good form lukesan

[TUTORIAL] -Simple way to switch from one 2.1 version to another

Hi all,
I've just finished proving that this works on my own phone and wanted to share..
I started with UK Generic 1.6 firmware.. and tricked my phone into thinking it was Nordic to get the Nordic Combined 2.1 upgrade (following "1 click rooting")..
Then I thought to myself.. sh!t.. how do I get 2.1 Generic UK when that comes out..!!!..
Done some reading and thanks to thanss (!) I've just done the following and confirmed that I now have World Generic 2.1
I used "Super1click" root method to root my 2.1 (you need 32 bit java from what I've read) and switched the USB debugging off and on a few times during the process.. and it worked. (I used 1.5.3 shortfuse and have attached the zip file now below)
Then using root explorer I edited "build.prop" from within the system folder.
I changed
ro.semc.version.cust=xxxx-xxxx
and
ro.product.name=X10_xxxx-xxxx
I changed the xxxx-xxxx to 1232-9897 (World generic)
saved the settings and exited from the file.
I also changed the ro.semc.version.cust=xxxx-xxxx file in...
/etc/customization/settings/cust.prop
saved and exited.
Then I switched the phone off and on again..
Then off one more time..
Then I used SEUS...
It will say that you have the latest software (because you do!).. but if you do a repair then it will replace your current one with the one associated with the codes you entered...
and bingo.. job done..
CODES here..http://forum.xda-developers.com/showthread.php?t=826875
Make sure you use the first of the codes for your brand/region.
Obviously this only works with firmware that has been released into SEUS.
UPDATE - IF SWITCHING BACK TO A REGION THAT YOU WERE PREVIOUSLY ON YOU WILL NEED TO DO THIS...
(Courtesy of ARKEDK's 1.6-2.1 method!)
Clear out your db folder in either PC Companion or SEUS, which ever one you use.
Press your Windows Key+R or type "run" in your start menu.
Then insert the path to what ever program you use and press enter.
Then delete the folder named with numbers in it.
SEUS db folder can be found here:
Code:
%programfiles%\Sony Ericsson\Update Service\db\
PC Companion db folder can be found here:
Code:
%programdata%\Sony Ericsson\Update Engine\db\
Reboot your phone and use SEUS to re-install your phone to 2.1.
Upgrading from 1.6 to 2.1 - this method was the one I used.. http://forum.xda-developers.com/showthread.php?t=824711

im_iceman said:
Done some reading and thanks to thanss (!) I've just done the following and confirmed that I now have World Generic 2.1
Click to expand...
Click to collapse
Or you could just run x10 Flash 2.1 Final + Global World Firmware 2.1. But at least you have shown you can just change the codes in the build.prop so you can get your regions FW. Cheers.

You could.. but this method is repeatable for any available 2.1 firmware.

im_iceman said:
You could.. but this method is repeatable for any available 2.1 firmware.
Click to expand...
Click to collapse
Yeah, just edited my post as you posted that.

Hmm now I know I will definately be able to get uk version of 2.1 when its released this is very tempting to try....
Hmmm
I wouldn't be so bad if we just had dates set in place or just a rough estimate. The lack of no news from them is giving me itchy fingers and annoyed.
How much time do they need, I mean no of us are getting any younger lol!!!!
Thanks for all your work btw guys your are truely legendary
Sent from my X10i using XDA App

im_iceman said:
Hi all,
I've just finished proving that this works on my own phone and wanted to share..
I started with UK Generic 1.6 firmware.. and tricked my phone into thinking it was Nordic to get the Nordic Combined 2.1 upgrade (following "1 click rooting")..
Then I thought to myself.. sh!t.. how do I get 2.1 Generic UK when that comes out..!!!..
Done some reading and thanks to thanss (!) I've just done the following and confirmed that I now have World Generic 2.1
I used "Super1click" root method to root my 2.1 (you need 32 bit java from what I've read) and switched the USB debugging off and on a few times during the process.. and it worked.
Then using root explorer I edited "build.prop" from within the system folder.
I changed
ro.semc.version.cust=xxxx-xxxx
and
ro.product.name=X10_xxxx-xxxx
I changed the xxxx-xxxx to 1235-9897 (World generic)
saved the settings and exited from the file.
I also changed the ro.semc.version.cust=xxxx-xxxx file in...
/etc/customization/settings/cust.prop
saved and exited.
Then I switched the phone off and on again..
Then off one more time..
Then I used SEUS...
It will say that you have the latest software (because you do!).. but if you do a repair then it will replace your current one with the one associated with the codes you entered...
and bingo.. job done..
CODES here..http://forum.xda-developers.com/showthread.php?t=826875
Obviously this only works with firmware that has been released into SEUS.
Click to expand...
Click to collapse
Although you have gone into much more detail, provided links etc this sounds very similar to what I suggested to su_007 on the 2nd of this month, page 810 of the 2.1 discussion / news thread.
I would post a link but I'm using xda on my phone, here's copied and pasted text;
****My best guess is ask someone with a different fw to nordic and get the numbers ( the same ones that you used to do the nordic method ) but for that country and try running a repair on seus or pc comp.
This is only a guess and accept no responcibity if it goes horribly wrong.
Sent from my X10i using XDA App****
Not trying to take any credit or the wind out your sail so to speak, just thought id note it.
Sent from my X10i using XDA App

steve.adams.x10 said:
Not trying to take any credit or the wind out your sail so to speak, just thought id note it.
Click to expand...
Click to collapse
Well at least no one one has to trawl through 810 pages now to find it. And now we know it does actually work thanks to iceman.

I tried your method, but SEUS keep saying that i have the lastest FW and there are no Install button, only Finish button appear.
PC Com say that cannot download software for my fone.
Im stucking

XperiaX10iUser said:
Well at least no one one has to trawl through 810 pages now to find it. And now we know it does actually work thanks to iceman.
Click to expand...
Click to collapse
Ah yes, how easy it is for usefull information to get all jubbled up with all the other crap.
I'm glad it works, congrats on proving it does iceman.
Sent from my X10i using XDA App

this is a much easier way I think ...
In theory it involves only two major steps
1. change the product code...ie the region via [ 1 root access]
2. connect to Sony Update service ...so simple....

im_iceman said:
Hi all,
I've just finished proving that this works on my own phone and wanted to share..
I started with UK Generic 1.6 firmware.. and tricked my phone into thinking it was Nordic to get the Nordic Combined 2.1 upgrade (following "1 click rooting")..
Then I thought to myself.. sh!t.. how do I get 2.1 Generic UK when that comes out..!!!..
Done some reading and thanks to thanss (!) I've just done the following and confirmed that I now have World Generic 2.1
I used "Super1click" root method to root my 2.1 (you need 32 bit java from what I've read) and switched the USB debugging off and on a few times during the process.. and it worked.
Then using root explorer I edited "build.prop" from within the system folder.
I changed
ro.semc.version.cust=xxxx-xxxx
and
ro.product.name=X10_xxxx-xxxx
I changed the xxxx-xxxx to 1235-9897 (World generic)
saved the settings and exited from the file.
I also changed the ro.semc.version.cust=xxxx-xxxx file in...
/etc/customization/settings/cust.prop
saved and exited.
Then I switched the phone off and on again..
Then off one more time..
Then I used SEUS...
It will say that you have the latest software (because you do!).. but if you do a repair then it will replace your current one with the one associated with the codes you entered...
and bingo.. job done..
Obviously this only works with firmware that has been released into SEUS.
Click to expand...
Click to collapse
Hi, I'm from Argentina and I have the firmware 1.6 which I would like to know
I have steps to follow in order to do this trick SEUS, which would
the numbers that I have to use? because the list does not understand anything haha
Sorry for my bad traduction, google translate sucks xD
thx!!
xD

So nice one but im woundering.......
is there a need to use the Global World Firmware?
What are the differences between die Nordic and the Global one?

great!!! good to know this work, now i can switch easily to dutch generic when it comes out. (without downgrading to 1.6)

Sometimes you might consider deleting the db folder in the SEUS install folder.

Olli80 said:
So nice one but im woundering.......
is there a need to use the Global World Firmware?
What are the differences between die Nordic and the Global one?
Click to expand...
Click to collapse
My thoughts exactly! What is the difference?

I don't seem to have
ro.semc.version.cust=xxxx-xxxx
and
ro.product.name=X10_xxxx-xxxx
in my build.prop file. my file reads as follows:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=R2BA026
ro.build.display.id=R2BA026
ro.build.version.incremental=1277951075
ro.build.version.sdk=4
ro.build.version.codename=REL
ro.build.version.release=1.6
ro.build.date=Thu Jul 1 11:24:52 JST 2010
ro.build.date.utc=1277951092
ro.build.type=user
ro.build.user=semc-android
ro.build.host=jptolnxbld004.corpusers.net
ro.build.tags=rel-keys
ro.product.board=es209ra
ro.product.cpu.abi=armeabi
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SonyEricssonX10i
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=X10-user 1.6 R2BA026 1277951075 rel-keys
# end build properties
# SEMC Specific define
ro.semc.product.device=RACHAEL
ro.semc.version.fs=1227-4607
ro.semc.version.fs_revision=R2BA026
ro.semc.version.fs_variant=GENERIC
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
ro.sf.lcd_density=240
use_csp_plmn=1
ro.qualcomm.proprietary_obex=1
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
any thoughts?

abo999 said:
I don't seem to have
ro.semc.version.cust=xxxx-xxxx
and
ro.product.name=X10_xxxx-xxxx
in my build.prop file. my file reads as follows:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=R2BA026
ro.build.display.id=R2BA026
ro.build.version.incremental=1277951075
ro.build.version.sdk=4
ro.build.version.codename=REL
ro.build.version.release=1.6
ro.build.date=Thu Jul 1 11:24:52 JST 2010
ro.build.date.utc=1277951092
ro.build.type=user
ro.build.user=semc-android
ro.build.host=jptolnxbld004.corpusers.net
ro.build.tags=rel-keys
ro.product.board=es209ra
ro.product.cpu.abi=armeabi
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SonyEricssonX10i
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=X10-user 1.6 R2BA026 1277951075 rel-keys
# end build properties
# SEMC Specific define
ro.semc.product.device=RACHAEL
ro.semc.version.fs=1227-4607
ro.semc.version.fs_revision=R2BA026
ro.semc.version.fs_variant=GENERIC
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
ro.sf.lcd_density=240
use_csp_plmn=1
ro.qualcomm.proprietary_obex=1
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
any thoughts?
Click to expand...
Click to collapse
this is OS 1.6 the instructions are for OS 2.1
in OS 1.6 you can do these changes in system/default.prop

oops! was looking for a way to switch my 1.6 to a region so I can download 2.1. I guess the way forward is to switch 1.6 to nordic, download nordic 2.1, switch to my desired region and download again?

Hi - Switching from 1.6 to 2.1 - http://forum.xda-developers.com/showthread.php?t=824711
You can use this method to switch to ANY published 2.1 firmware from 1.6..

Just checked the code (1235-9897) in the code list and couldn't find it... but I could find 1232-9897...
Which one is it?
Just checking!

needed steps to port Gingerbread to i9000

Hi!
First, i want to indroduce myself. Im a software developer form germany. I own an i9000 and i want to port gingerbread to it.
I dont know if some people here ware working in it, but if we dont collect our knowledge we will get to nowhere.
So i already worked on a android port to a windows device (meizu m8) so i think i have basic knowledge on how this should go.
So here are the steps i would go, and i already starting uop a bit:
1) We need to get a 2.6.34 kernel running on the device. With our ROM.
This includes: Here are proble which already compiled kernels. Who does this work with the drivers? Are there .config files from the i9000 kernel?
We should DL the nexus S kernel sources from android git (they are there) and give it a shot. Just compile and install a 2.6.34 kernel which should be configured as near as pssible to the i9000 kernel. If we get such a kernel to run with our phonr we are nearly there.
2) if we get such a kernel, we can just DL/compile gingerbread. Then we create an update.zip file from the generated img files. We would need to collect the config scripts from out froyo and put them into this rom too.
3) let it update and see. For me, this sounds not very hard. The hardest part is the driver part, but as there are people here, which supply compiled kernels, they
a) have the driver sources, if they are build in
or b) the drives are modules, and so we hopefully should be able to use them on a 2.6.34 kernel too.
So the first thing we would need:
Are there any people out there which know about compiling kernels etc, which compiled/hacked a kernel for galaxy already. If so, please post here about the details, drivers config etc.
c'mon guys, we can do this, this isnt that hard.
greets

I suggest you to come to NSdev at irc.freenode.net
Lot's of developers there ready to help you, including supercurio

http://www.emoiz.com/samsung-galaxy-s-to-get-android-2-3-gingerbread-in-february-2011
read this

Hum... i dont know if i can trust what samsung says... it took nearly the complete lifecycle of froyo until they brought it to the i9000...
If they need this long to to this small port, i think we will get it in summer, just with 3.0....
Lets see and hope, but i think its not that hard to bring gingerbread to the i9000.
See android runs on linux. you can boot a normal linux system, and then start android after this. i think if we get a 34 kernel to run (thats the ginger kernel) with our drivers, we can surly compile gingerbread and create a update.zip out of this.
The main problem here (like we had it with porting android on the m8) it the driver problem. U need the hardware drivers for anything to use it. But as we already have a 2.6.32 kernel and we could inspect it how this is compiled, and we have the nexus s sources (which is in fact nearly the same phone), and we have people here who manage to compile running kernel for the i9000 i sthink we can do this.
The main info i need is if those self compiled kernel use the drivers as modules or if they are compiled into the kernel.
To be precise: The baseband/modemdriver is the main problem as for such devices its very hard to get open source drivers. For all the other things, like bt network display and sound there are surly drivers avaliable.
Anyway, i will start and see how far we come and see who is faster if samsung brings a ginger in short time, its not that bad either, then we know how to port 3.0 when it comes
greets

dadyal said:
http://www.emoiz.com/samsung-galaxy-s-to-get-android-2-3-gingerbread-in-february-2011
read this
Click to expand...
Click to collapse
I'm sure it will be postponed till october.

Thanks for working on this, check in to the IRC and work with the others in there
Sent from my GT-I9000 using XDA App

^Karlo hope you will find a way to get gingerbread(vanillastyle) to work on the sgs.
Mach weiter so, werde diesen Thread auf jeden Fall im Auge behalten. Boah ich wünschte, ich könnte programmieren und würde mich besser auskennen mit der Materie. Dann wären wir schon mal zu zweit ^^
cheers mate

i'm really looking forward to this although i will get a new phone by march
ich freu mich echt auf das was mit dem sgs hier erreicht werden wird viele neue tolle ideen
und ein clean android ist der erste weg zu was ganz grossem
Sent from my GT-I9000 using XDA App

A Dream Team wish list
In my opinion this would be a perfect team to bring AOSP gingerbread port to sgs.
supercurio experienced in kernel coding - proven NS root, voodoo etc.
Aery aka Codeworkx experienced in all areas - proven dev works on CM6.1 port
Coolya Great experienced in all areas - proven dev works on CM6.1 port
KarloRanseier - unproven jet but qualified by the statement from the first post and with a good will.
With those guys working together a 2.3 would be ready in a week. I hope my wish list will come true for the holidays

oppssss
probably february-2012
nexus ( google ) + 1 year = sam
and ... but sales ...

I just DLed the kernel sources from the nexus s (these are the android git samsung sources) and the opensource package from samsung OS center. Now we need to compare them, to find out which parts ( machine init for s5pcX and mainly drivers) are different. thats a messy work but nohting really hard.
Then i think it should be possible to port most of the changes from galaxy kernel to nexus s kernel (i think there wont be that much changes...).
then compile one and give it a shot.
I will see what happens
will try it tomorrow and then i will show up in irc and hear what the others have to say.

KarloRanseier said:
I just DLed the kernel sources from the nexus s (these are the android git samsung sources) and the opensource package from samsung OS center. Now we need to compare them, to find out which parts ( machine init for s5pcX and mainly drivers) are different. thats a messy work but nohting really hard.
Then i think it should be possible to port most of the changes from galaxy kernel to nexus s kernel (i think there wont be that much changes...).
then compile one and give it a shot.
I will see what happens
will try it tomorrow and then i will show up in irc and hear what the others have to say.
Click to expand...
Click to collapse
'
dont need to port the kernel at all. focus on the rom instead. gingerbread will run fine on 2.6.32

and btw. sgs uses some properitery drivers wich we dont got sources for. so it cant even be ported,like onenand,rfs etc.
with out them /dev/block/stl* wont even exist..

sgs uses some properitery drivers wich we dont got sources for. so it cant even be ported,like onenand,rfs etc.
Click to expand...
Click to collapse
You are right with that...
BUT if no android phone in the world has rfs, i think that android dont need rfs. Thats just a bullshitish samsung development. So if we just use a stock android,
we would get rid of rfs and just use yffs like every android in the world does. there is no need for us tu use rfs (besides of some configs which surly can configed back to original)
And a onenand driver is nearly sure gettable in opensource as there are not soo many onenand ctrls but very much devices which use them.
But oki i then will start to get gignerbread sources and have a look at this.
PS: in m8 world, we did it like that: Created a root image which was mounted at startup to /data and stuff. This way we could hold this image on sd card. i think it should be possible to do the same with a gingerbread img to give it a short try and tinker with it

"badaNEXT" - Making a better bada

I do not know whether the idea meets with interest ...
I'll throw the idea but just once in the round ...
We all know that bada shall have its flaws and missing features that only by custom ROM can be upgraded ...
Here is a point to wear ...
Even the look you could make more of bada ...
This point comes into play two ...
Meanwhile, it allows the bada-modding to get ran well to certain design elements ...
All i can say *. Rbm-Files ...
Hence my idea of ​​a completely new to tinker bada-ROM ...
Sense of it all, it should NOT be to create a second Android, but to create an entirely new concept ...
Therefore, would initially only once to clarify how the ROM should be made more technically ...
Next, you would have ran to the design ...
Here are a few people would get together, who know the one with the modding. Then people would of distress, which in terms of design e Bissel what's on the box.
This includes Flash programmers would include, for example, to craft a new lockscreen ...
I hope it will find a few people ...
Maybe we can develop something really good here ...

All i can say *. Rbm-Files ...
Click to expand...
Click to collapse
Meinst Du die aus dem RC1 ?
Ich kenne noch keine Lösung. Die Bilder auszutauschen...
Alle Versuche gingen zumindest bei mir bisher in die Hose...
Ich kann mit Ach und Krach einige Bilder ausschalten...
This includes Flash programmers would include, for example, to craft a new lockscreen ...
Click to expand...
Click to collapse
Bei Flash fangen leider wieder viele an zu weinen, wenn es um Decompile geht...
Die die Ahnung von Action Script haben, schmeissen lieber en masse Themes in den bada Markt... solange der Kopierschutz der Themes/Flash noch hält...
MfG

Taxidriver05 said:
I do not know whether the idea meets with interest ...
I'll throw the idea but just once in the round ...
We all know that bada shall have its flaws and missing features that only by custom ROM can be upgraded ...
Here is a point to wear ...
Even the look you could make more of bada ...
This point comes into play two ...
Meanwhile, it allows the bada-modding to get ran well to certain design elements ...
All i can say *. Rbm-Files ...
Hence my idea of ​​a completely new to tinker bada-ROM ...
Sense of it all, it should NOT be to create a second Android, but to create an entirely new concept ...
Therefore, would initially only once to clarify how the ROM should be made more technically ...
Next, you would have ran to the design ...
Here are a few people would get together, who know the one with the modding. Then people would of distress, which in terms of design e Bissel what's on the box.
This includes Flash programmers would include, for example, to craft a new lockscreen ...
I hope it will find a few people ...
Maybe we can develop something really good here ...
Click to expand...
Click to collapse
I thought there's no way to edit RBM files to date? I might try my hands on something (using ho1ods source) myself, but that might take a long time.

Alright, I've taken a look at the RBM files internal structure, and it doesn't look any good :-/.
While the internal structure itself is actually pretty easy, the problem lies in the embedded images. Four(!) different compression methods are used: LZ16, LZ32, QMG16 and QMG32. No way that I can do this all on my own. I could do decode/encode for LZ16/LZ32, but QMG is used for most.
The only chance that I see right now is, IF RBM is also used for Samsungs Android FWs that we'll get support from this side.

Maybe RBM step by step..
Step 1 disable Pictures... like here:
http://forum.xda-developers.com/showpost.php?p=27932409&postcount=124
Step 2 could be replace content... or replace by other Pic from other RBM...
If I have more time... I will play again with bada SDK...
Maybe easier to try modified RBM instead RC1 flashing on device...
Best Regards

adfree said:
Maybe RBM step by step..
Step 1 disable Pictures... like here:
http://forum.xda-developers.com/showpost.php?p=27932409&postcount=124
Step 2 could be replace content... or replace by other Pic from other RBM...
If I have more time... I will play again with bada SDK...
Maybe easier to try modified RBM instead RC1 flashing on device...
Best Regards
Click to expand...
Click to collapse
I hope this will help us get a little bit further:
http://forum.xda-developers.com/showthread.php?p=30648338#post30648338

Okay...
let's pick up this thread again...
Maybe it could be pinned as sticky...
I think, we should collect all improvements of FW customizations here...
E.g. Tutorials for UI Customizing...
I think, we ned a plan...
So i think, we need an overview, what UI element can be modified in what RBM file...

Wat r the flaws in bada 2
Sent from my GT-S5670 using xda app-developers app

How about replacing QMG compressed chunks with LZ ones? Should be doable, no?