yashsingh1/xdaforums huggingface dataset:
[Android Development on Bada] ishikawa13:
hi, first of all thanks for your hard work.

since you are working to wave's sensors,have you considered proximity sensor and light sensor(if wave has this one can't use it with bada)?
[Android Development on Bada] Fahrenheit51:
Thanks Rebellos. I would like to help you but I don't have any knowledge in writing kernel or such a thing. I can only give you my availability to use my QuadCore CPU if you have to, maybe, compile something that require a lot of time in your machine.

And .. "working dual booting Android" .... This sounds sooooooo good!!! :D
[Android Development on Bada] DarkRidder:
This day is now part o History! A 13th Friday! The dey we had a working kernel! Thank you guys! You are my pride! :D

Now, some questions that I think that common user would like to know:

-Is it dangerous to make the modifications needed to dual boot OS? Can we accidently brick the phone?
[Android Development on Bada] gdrdasky:
I am not expert but i will anwser you with my little knowledge....

No because the bada system is not touched from this process and if something goes wrong you will be able to open your phone into download mode and to flash your phone again with untouched bada OS...

right?
[Android Development on Bada] Rebellos:
Yes. The probability isn't very high, but is much higher than during sending and reading SMS.
[Android Development on Bada] DarkRidder:
Sorry, I did not understand to which question you did answear.

Can we brick the phone?

If so, how can we put it good again?

PS: Can you go to IRC?
[Android Development on Bada] adfree:
Please, at the moment it is experimental status... under construction..

oleg_k has JTAG Hardware to repair if something goes wrong...

Our other "testgroup", as only srg.mstr has made correct Cable to log Boot, as you can see in Videos...

Without JTAG higher risk. As every mistake can not easily repaired without JTAG. Bootloader kill during "accident".

I know this. :)

Stupid Question. :D

According to this:

http://xdaforums.com/wiki/index.php?title=Androidonwave

Can we not now use oleg_k working part?

As he see Android on Display? :confused:

Best Regards
[Android Development on Bada] jake792:
@ Rebellos,srg,mijoma & nbates; Congrats for acheving a great milestone!:)

The dual boot which you are working on is it similar to jetdroid? so after accomplishment will we need ubuntu to create partition on MoviNAND??

Also in the kernel log I saw memory as 256+80=336mb.. is it physical memory?:confused:
[Android Development on Bada] lowgitek:
Yes that was my question to Rebellos on irc.

Why not use the working part of Oleg, He told me the problem was with something like mounting the filesystem
[Android Development on Bada] Rebellos:
Oleg achieved much more as we did, as he reflashed oneNAND with original I9000 files, that mean kernel could load GUI. Our kernel isn't loading GUI, as it isn't mounting any drives, so even if it is using correct video driver it wouldn't show anything, as it doesn't even try to show anything and won't try to do so until we manage to mount some filesystem with I9000 Platform files.

We aren't sure if we are going to use moviNAND as primary filesystem, but it MAY be necessary to use some linux to format SD card to the filesystem (ext2 or so) which can be used as Android primary partition.

Yes, 336MB is in fact available physical RAM of Wave.

Altought I can't be sure for 100%, but everything seems like we've got one SDRAM bank of 256MB (under 0x4000_0000-0x5000_0000 address space) and one oneDRAM bank of 128MB (under 0x3000_0000-0x3800_0000 after reconfiguration of DDR controller), BUT only 0x30 - 0x35 area of oneDRAM are being mapped as available (exactly 80MBytes) as 0x35~ is shared with Qualcomm modem chipset and from level of S5PC110 it should, and is accessed directly only from modem driver, so it cannot be mapped system-used RAM. However I think it may be possible to map around 16MB more from oneDRAM, like 0x37~0x38, but I don't think it is needed and worth of trying before we get fully working system.

Also, what is interesting, Samsung's oneDRAM seems to be much faster than normal DDR, as starting kernel from 0x44~~ offset takes longer than starting it from 0x32~~
[Android Development on Bada] adfree:
Maybe my logical brain problem. :o

The 2 GByte moviNAND contains "bada" user data... to prevent erasing something during accident.

Safest solution would be SD card ""Booting"" I think. So Android should run from SD card. SD Card solutions are known from S8000 and many other Android ports...

I think this part is not finished yet.

oleg_k known working status is all Android stuff runs from OneNAND + moviNAND = bada complete destroyed

NO way back to bada without JTAG.

So mix oleg_k stuff with FOTA is not finished yet, as not safe.

Risk to erase something... = risk to brick.

Best Regards
[Android Development on Bada] srg.mstr:
As i know (info from oleg) Mijoma made a unique SBL for oleg. It's not 100% equal "Sbl2FOTA_mijoma2". And oleg used a Primary Bootloader from i9000, which initi RAM correctly for SBL work. Mijoma, is it right?
[Android Development on Bada] mijoma:
For the clarification:

The SBL oleg used has only modifications to address display GPIO. There's still screen rotation problem, but I'd need some screen documentation to know what changes to apply to SBL to make it normal. I assume that having the documentation, oleg would be able to apply that to kernel as well. Without that, what we have left is comparing Wave BL3 and SGS SBL. The problem with comparing is that they do not use exactly same interface for driving the screen (RGB and SPI).

As for the SBL2FOTA file, it's just same (modified already modified) SBL with additional callback for kernel loading from memory rather than from the NAND partition.
[Android Development on Bada] Rebellos:
Just found confirmation of my oneDRAM theory

Kernel_2.6.32\drivers\onedram\dpram.h:

So that means we can theoretically gain 32MB more memory for system & apps.
[Android Development on Bada] nbates66:
worth reading : http://www.samsung.com/global/business/semiconductor/products/fusionmemory/Products_OneDRAM.html

it's faster because thats the point, it's suppose to work as some sort of fast data bridge between the Application processor, Call processor and RAM. If it's laid out the same as on a Galaxy S there would perhaps be 1x128MB oneDRAM chip and 384MB of DRAM?
[Android Development on Bada] adfree:
Samsung GT-S8500L Wave Training Manual HW.ppt

http://xdaforums.com/showthread.php?t=901416

4G, 2G, 1G we can see also in Service Manuals... so:

512 MB OneNAND, 256 MB DRAM, 128 MB OneDRAM

But like months ago. I don't understand how it works. :o

As it seems very often swap data... as not enough space to hold whole OS in RAM... :confused:

I hope some day we find Training Manual for S8530... maybe then more clear. :)

Best Regards
[Android Development on Bada] lowgitek:
I'm so sorry, but what's the point to be messing around with memory by now, should not be priority other things like others pointed like, FS stuff and modem's should come first didn't it?

By the way I bought another phone just to be messing around when ou guys put something here out to be tested ;), my wave is prepared to the sacrifice :p
[Android Development on Bada] adfree:
Memory handling is important. As you know oleg_k is the ONLY user, who has seen Android on Wave.

It makes no sense to kill handsets...

Priority is to find safe way to start Android from Wave... Then more testers, then more user can help to fix major and minor problems...

Thanx.

Maybe good task would be to support srg.mstr with Logging... so you need an cable:

http://xdaforums.com/showpost.php?p=13446044&postcount=8

Thanx.

Best Regards
[Android Development on Bada] lowgitek:
;) Shure

Just a dumb question it is a serial-to-usb or usb-to-usb, cause if serial as it looks like, I have to get an usb-to-serial adaptor as I'm a macbook.
[Android Development on Bada] Rebellos:
Its micro usb to serial UART, which can be connected to the pc serial rs232 only through buffering chip like MAX232.
[Android Development on Bada] jake792:
Thanks for all relevant info:D.. Considering all the above details by you, 'Total' amount of RAM in wave is 128(oneDRAM) and 256(SDRAM)=384 mb RAM??
[Android Development on Bada] darkcheater:
Just a question, maybe it has been talked about yet, but I only read the last 50 pages of this article (in that case, excuse me):

Why don't u guys contact those guys who already managed to port android to wave and remove the lag? =)

h ttp://ww w.youtube.com/watch?v=FHehTXZmuAA
[Android Development on Bada] Brickpsp:
Because it is fakeeeee :D
[Android Development on Bada] alex_manow:
Remember, androbada it was fake. It was only played video(recorded on I9000). Stop talking about this ****.
[Android Development on Bada] srg.mstr:
you can remake your old data cable (usb-to-serial) having soldered it to micro-USB (i got it from data cable USB-to-microUSB, bought it in the nearest supermarket)

just for example:
[Android Development on Bada] darkcheater:
I don't see any fake in the video...
[Android Development on Bada] arwiz:
...but it is fake !!

if you want to talk about it... go to irc chat ... not here !!!
[Android Development on Bada] duxxyuk:
fantastic work lads. have been following carefully.... keep up this fantastic work...
[Android Development on Bada] pauldmps:
Please no discussion on AndroBada. They are obviously fake.

Read this: http://xdaforums.com/showthread.php?t=1006796

If you're still interested in them, head to their forums. Don't discuss it here.
[Android Development on Bada] cfernr:
Take a look, please

http:/*/ww*w.kandroid.org/android_pdk/index.html

thanks!
[Android Development on Bada] wongwing:
S8500 users in China has been quietly support many of the oleg_k, thank you!

S8500 users in China has been quietly support many of the oleg_k, thank you!:)
[Android Development on Bada] wongwing:
Thank you very much!oleg_k!!!! Really!
[Android Development on Bada] baza14:
Any news oleg? Your last post is almost week ago.
[Android Development on Bada] mushrom:
they are working on mounting things on the sd card (you should read the irc logs.)
[Android Development on Bada] sabianadmin:
he was talking to oleg_k in regards his work with the kernel not the people who are working on booting.
[Android Development on Bada] mushrom:
omg isnt a 1person project. if you wanna stalk someone there are easier ways.
[Android Development on Bada] sabianadmin:
Im sorry i don't get that at all, do you mind re-phrasing it so it makes sense please? Thank you.
[Android Development on Bada] adfree:
At the moment I'm playing with I9000 JTAG dump...

Interesting.

From 0 to 0x200 only 2 Bytes different... to XXJEE Boot from S8500...

No idea what the first 512 Bytes are...

Best Regards

Edit 1.

0	boot.bin
00AD4000	SBL
00C1E000	SBL
1F7C4000	modem.bin

Is SBL twice ?

:D

CJKT and DWD is typical Infineon stuff...

:D

First time I saw this in Apoxi A58 from Siemens... 2006... then in hundrets LG handsets...

WoW, it seems modem.bin is at the end of 512 MB... :eek: :confused:

You can compare attached piece of I9000 Boot with decrypted XXJEE Boot...

I9000 dump from here:

http://forum.gsmhosting.com/vbb/f665/share-full-flashes-1245293/
[Android Development on Bada] charsi:
@sabian, @mushrom

Can you guys please continue this bilateral dialouge in PMs, as it does not affect anybody else. Thanks
[Android Development on Bada] nbates66:
yeah you can see there's the boot partition, pit partition and then two sbl partitions by looking at the partition table that shows in olegs bootlogs, and the bootlog of any i9000 :) the 2nd SBL partition gets used in the event that the first is corrupt.
[Android Development on Bada] m90ultimate:
why dont you guys have a look at jetdroid project.could get some useful idea
[Android Development on Bada] ShadowAS1:
I don't think that will be of any use

because Bada is way diffrent in booting then TouchWiz (Which runs on the jét)

(correct me if i'm wrong)
[Android Development on Bada] nbates66:
well, we are somewhat managing to boot the kernel already, as has been posted. We're having problems configuring the kernel to mount filesystems from external SDcard instead of oneNAND though.

I did infact make a post on their forum here: http://www.jetdroid.org/forum/viewtopic.php?f=89&t=494&start=20

but that was 2 days ago, Since i had to create a new account the post had to be verified before appearing, it hasn't been verified yet D:
[Android Development on Bada] cfernr:
maybe we can open a thread in Android hacking subforum.

http://xdaforums.com/forumdisplay.php?f=565

nbates, i think youare the best person to post there and make all your questions.
[Android Development on Bada] anghelyi:
Hi nbates66! Do you use the kernel config from oleg which is in the first post?
[Android Development on Bada] adfree:
Same situation here.

That's life.

Best Regards
[Android Development on Bada] cadiga:
if ("Oleg Kalugin, a former KGB general who was a Soviet spy in the United States" == oleg_k)

{

samsung.phone.8530.state = result.success;

}

else

{

samsung.phone.8530.state = result.god_knows;

}

Bye I will not post anymore but will be watching the forum regularly
[Android Development on Bada] srg.mstr:
ADB command line mode

Thanks to (in alphabetical order) Mijoma, Nbates66, Oleg_k, Rebellos, Srg.mstr (last but not least) now we have ADB command line mode (in recovery mode now).

For this we use only standard USB data cable:

0. For experts only who will not ask stupid questions in the future.

1. make kernel ( https://github.com/Oleg-k/initramfs_2.6.32_S8500 https://github.com/Oleg-k/S8500_Kernel_2.6.32 ) with modified initramfs/recovery.rc http://code.google.com/p/badadroid/source/browse/trunk/initramfs/recovery.rc?spec=svn179&r=179

2. create "galaxyboot" folder at internal mmc0 card and put there:

2.1 sbl.bin http://code.google.com/p/badadroid/downloads/detail?name=Sbl2FOTA_mijoma2.zip&can=2&q=#makechanges

2.2 zImage

3. create on external mmc2 primary FAT partitions p1, p2 and p3 ( <=1GB ). put there files from factoryfs.rfs > p1, dbdata.tar > p2, cache.rfs > p3.

4. make and upload to phone FOTA http://code.google.com/p/badadroid/source/browse/trunk/FOTA/kernel_boot_sbl.asm?r=179

5. connect USB to phone and hold POWER and CALL buttons.

6. after ~30sec reconnect USB and try to use $ ./adb shell
[Android Development on Bada] nbates66:
i'd like to point out that since a "dd" utility is included we *may* be able to create direct file dumps from oneNAND partitions at will, useful to anyone?

EDIT: just managed to mount factoryfs as /system in Samsungs native rfs format.
[Android Development on Bada] nbates66:
i remembered, we need a warning here, most of the current FOTA code is limited to XXJEE Wave S8500 bootloader and XPKA bootloader on S8530, if you don't have either of these then flashing one of these FOTA files might prevent your wave from booting bada, it will ask for a compatible FOTA file, make sure you have the correct bootloader and don't get yourself into trouble!
[Android Development on Bada] Rebellos:
Or, rather it just won't start, don't cry then guys and girls, just put off battery, put it back in, start in download mode and flash the original FOTA module.

Or, if you cannot find original FOTA, you can compile our, with changing

in macros_S8530/8500 (according to your model, that is important)

to

or something similiar, the thing is that it would be nice if it had the same length (4 bytes), but eventually removing the whole db 'BPDZ' will do too.

Such modified & compiled FOTA module shouldn't block booting after flashing it.
[Android Development on Bada] oleg_k:
I am sorry for the lack of, a big load on the main work.

But, I'm back))))

latest news about my kernel - keyboard driver full work,

currently working on sensors drivers.

Mijoma, Nbates66, Rebellos, Srg.mstr and other - we are the BEST)))
[Android Development on Bada] nbates66:
ok i worked out why the kernel was only starting in recovery: the atag_cmdline setting sbl.bin is using includes "bootmode=2", the reason for this is probably because it can't find "param.lfs", current workaround is either recompile the kernel set to ignore the cmdline atag parameter and set the kernel default cmdline in boot options instead, or rename init.rc to recovery.rc

i've started attempting to boot in normal mode with most partitions mounted(have pretested the mounts in recovery.rc), the result of init.rc execution appears to be a stall however, with no adb service starting, i'm going to upload my current init.rc to googlecode. If possible can someone with a debug cable get a log?

the file: http://code.google.com/p/badadroid/source/detail?r=190

(could my stall be caused by incorrect factoryfs.rfs platform files?)

also, log of my last run of recovery.rc which appears to be successfuly (yields adb control etc), extracted using "adb shell toolbox dmesg"

http://code.google.com/p/badadroid/source/browse/trunk/adb+logs/dmesg2.log?spec=svn188&r=188

EDIT again, for those who want to reconfig the kernel to ignore atag rather than rename init.rc > recovery.rc:

http://h1.pargon.nl/wiki/index.php?title=Bootloader

"Bypass SBL arguments using Linux"
[Android Development on Bada] Rebellos:
Wonderful, debug messages without UART! :D

Try to use following code in fota_callback, just before LDMFD

LDR R0, [sbl_boot_mode]

MOV R1, 1 ;any value that differs from 4

STR R1, [R0]

useful pointers (you can place it after LDMFD):

sbl_boot_params dw 0x40704AD4

sbl_boot_mode dw 0x40704AE0
[Android Development on Bada] anghelyi:
Hi Oleg! Could you update your kernel and initramfs on github, please? I think all the devs would be happy :)
[Android Development on Bada] nbates66:
such a thing isn't exactly necessary as far as i know, we shouldn't need any of the additional drivers just to boot the OS, and oleg's files are configured for oneNAND booting anyway.
[Android Development on Bada] nbates66:
i *think* i managed to execute standard boot on init.rc with adb interface, zygote and android services appear to be stuck in a restart loop:

http://code.google.com/p/badadroid/source/detail?r=192

EDIT: would like to note that while "VIBETONZ" is appearing on the log, the phone is not vibrating, nothing is appearing on the display either. If possible i'd like a check on my kernel sources Oleg. EDIT AGAIN: the phone does actually vibrate, my bad

line 3150ish you can see the zygote service and various others getting killed and restarting.

EDIT2: another debug log extracted using "adb bugreport" (very large, will want to download in order to view)

http://code.google.com/p/badadroid/source/detail?r=193

http://badadroid.googlecode.com/svn/trunk/adb logs/bugreportnb190511.log

see if that second link works :/

EDIT3: it's possible that the restart loop is caused by lack of memory, this could be caused by the memory mapping of the current bootloader we're using, will have to ask rebellos and srg about that.

added a log to googlecode for procedure to boot kernel using init.rc with adb interface working ( i'm not exactly sure why this works) i may upload the zImage i'm using for this, but it'll only work if you partition your memory card in the correct layout and format.

http://code.google.com/p/badadroid/source/detail?r=194

http://code.google.com/p/badadroid/downloads/detail?name=initscriptedkernel190511v2&can=2&q=
[Android Development on Bada] srg.mstr:
nbates66, i look at your partition table and think it's better to use one SD card partition "mmcblk1" and put at it "/android" folder. like this:

mkdir /mnt_ext

mount vfat /dev/block/mmcblk1 /mnt_ext

symlink /mnt_ext/android/system /system

symlink /mnt_ext/android/data /data

symlink /mnt_ext/android/cache /cache

in that way no need to format sd card for many BADA users. I checked it - works fine.
[Android Development on Bada] anghelyi:
I use the same (I took the idea from your recovery.rc) and it seems to be working fine. But as vfat doesn't support chown/chmod maybe we should use ext2/3/4...
[Android Development on Bada] srg.mstr:
as you know in linux chown/chmod apply to all folder with subs (you can't use file from other owner for example). just need to set chmod/chown to top folder "/system" (it's link at root). And for what u need multiuser mode?
[Android Development on Bada] anghelyi:
But does chmod/chown works on fat filesystems, too? Because from my previous experiences (on desktop linux) I remember that it isn't. And init.rc and recovery.rc is full of chmods and chowns... I don't need multiuser mode.
[Android Development on Bada] srg.mstr:
chmod/chown applies only for top level folder which is placed on virtual ram fs (not on FAT). it folder is mount point for FAT partition. and all FAT files/folder have access level as parents folder.
[Android Development on Bada] anghelyi:
Finally I understood it :D So back to testing!
[Android Development on Bada] sabianadmin:
Wow a lot of the phones functionality seems to be on that chip, does anyone know of a data sheet for it or any other phones that utilize that chip?
[Android Development on Bada] alex_manow:
Please stop talking about androbada, this is fake for 100%. From start to end it will be fake. They are waiting for ported android and than they will say - "we don't need to finish project bc other ported android is running on wave".

There are only scammers and cheaters. This is the end.

Now i want to say: good luck for all ppl who help Oleg_k with porting. Good job guys. I keep my fingers crossed.
[Android Development on Bada] t0mm13b:
Hmmm... is it this one?

Info on MAX17042 here. and here...

:o
[Android Development on Bada] sabianadmin:
Ha did you just find the kernel module for that chip?? if so fair play!! save use creating or sourcing one!

Doing the country proud :)
[Android Development on Bada] oleg_k:
we have max8998.it's top secret device))))not description,not datasheet. nothing!!

in the kernel source has its driver but without fuel gauge.
[Android Development on Bada] sabianadmin:
Yeah we know, hence why i am devoting my effort into helping oleg_k
[Android Development on Bada] mijoma:
The bootloader has a lot of MAX8998 code - it handles RTC, timers, power management (charging, voltages) for display, USB, etc. Communication with the chip is done though I2C
[Android Development on Bada] oleg_k:
i know.but i need fuel gauge via this chip ;)
[Android Development on Bada] francipanzer:
This is good for something:

http: // kerneltrap.org / mailarchive / linux-kernel /2010 /6 /11 /4581899

http:/ / us.generation-nt.com / s/ max8998/

I feel silly if what I post, but trying to help from my zero knowledge.

Thank you very much for your work.

Greetings comrades.
[Android Development on Bada] sabianadmin:
Why don't you both work together, one modifies the boot loader and the other creates the Android image? When you both have you're end working you can put them together into a flashable imagine.

P.S as soon as you manage to find a bootable kernel the first thing I'm doing is porting Cyanogenmod 7 to the device ha.
[Android Development on Bada] oleg_k:
http://www.globenewswire.com/newsroom/news.html?d=213619

about max8997.Cool device!
[Android Development on Bada] qcn85:
I found this code:

h t t p :// w w w . oschina.net/code/explore/linux-2.6.36/drivers/mfd/max8998.c

But dunno what it does... it's distributed under GNU License.

Hope it may be useful.

EDIT: h t t p :// w w w .spinics.net/lists/mm-commits/msg79905.h tml

EDIT 2: h t t p s :// groups.google.com/group/fa.linux.kernel/browse_thread/thread/c87cad2a88f53409?hl=ja
[Android Development on Bada] mkz14:
I think that second link might be useful for oleg_k seems like it contents IRQ conf
[Android Development on Bada] adfree:
About S8500 RAM, please check Bootloader ELF... you can find more adresses for SDRAM...

I found this:

0x28000000 HEX Value converted in Decimal =

671.088.640 Bytes

Found in BL2_1_univ_evt0.elf

Best Regards