yashsingh1/xdaforums huggingface dataset:
[Android Development on Bada] neoxigen:
about gauge fuel

Hi everyone,

This is my first post in this forum, but I'm very interested in this project.

I've found some information that may be useful...

In the website h t t p s : / / patchwork . kernel . org / patch / 615331 / they are talking about the MAX8997 (I know it's not MAX 8998 but maybe they have smthg in common). They say "The fuel gauge is not supported by this mfd driver and is supported by a separated driver of MAX17042 Fuel Gauge (yes, the fuel gauge part is compatible with MAX17042)."

Here some information about MAX17402 gauge fuel:

h t t p : / / lwn . net / Articles / 423118 /

Hope this help
[Android Development on Bada] oleg_k:
Colleagues, we now have the same problems that as the project JetDroid.

It's a fuel gauge. Without the correct information from accum, the kernel does not start correctly and does not power on LCD.

must be in original bootloader some functions about fuel gauge.

mijoma and adfree, need help ;)

and other idea - download the native modem s8500 and get the battery capacity via AT commands.

Need to check what AT commands are responsible for guel gauge.
[Android Development on Bada] adfree:
We could try to research deeper in ELF files:

http://xdaforums.com/showpost.php?p=10304951&postcount=3

Best Regards
[Android Development on Bada] mijoma:
I don't know whether this is what you need, but LDI_TL2796_Power_On and LDI_PortInit (used by FIMD_Drv_INITIALIZE) use LCD_ldo_control(1).

LCD_ldo_control looks like this:

void LCD_ldo_control (onoff)

if (onoff == 0)

{

Set_MAX8998_PM_REG(0x67, 0); //0x67 is ELDO7

Set_MAX8998_PM_REG(0x71, 0); //0x71 is ELDO17

}

else

{

Set_MAX8998_PM_REG(0x67, 1); //0x67 is ELDO7

Set_MAX8998_PM_OUTPUT_Voltage(0x91, 0x2F); // 0x91 is LDO17, 0x2F is VCC_3p200

Set_MAX8998_PM_REG(0x71, 1); //0x71 is ELDO17

}

Is that a good lead?
[Android Development on Bada] oleg_k:
Yes, it's a function to power on(off) display.

LDO7 and LDO17.

Power supply in S8500 and S9000 the same.

Maybe in LDI_PortInit initialize GPIO for LCD and LCD_RST?
[Android Development on Bada] oleg_k:
i found in amss(modem) QmochaBattery_fuel_gauge.c and i2c routines.

who have a working S8500 with bada? Test please this AT command:

AT+BATTTEST

AT+FUELGAIC

AT+CALIDATE

AT+TEMPTEST

AT+MAXPOWER
[Android Development on Bada] Rebellos:
Long researches done again, managed to fully boot kernel from 0x32~~ without sbl from fota. However, kernel seems to be very unstable, don't know why yet...

Also I've got still problems to reloc kernel into 0x20~~ memory space, which is needed to boot modem correctly.

For now this is 100% sure needed in FOTA to boot kernel
[Android Development on Bada] sabianadmin:
Full boot would suggest that you got dalvik and the UI running, ill hazard a guess and say that this not the case?
[Android Development on Bada] mushrom:
i think he said kernel, not android.
[Android Development on Bada] sabianadmin:
You make a valid point, but if the kernel where to be booting successfully using the init scripts they are using, then it would include fully initialized UI, just wanted to clarify.
[Android Development on Bada] Rebellos:
Full boot of kernel, bypassing all init scripts except adb, it usually gets through whole process and hangs after few minutes. Dalvik and all apps are not kernel modules. And no, all drivers are not required for kernel boot, web browser and mp3 player also.
[Android Development on Bada] smokestack76:
Did alot of cleaning again. :(
[Android Development on Bada] hukerrs:
already posted about two thousand times, yet still seems to be invisible for a lot of people... READ BEFORE POSTING ANNOYING QUESTIONS!!!

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

this thread should be locked for new xda members... including me
[Android Development on Bada] peyman_mi:
oleg where are you ?

why does it release?
[Android Development on Bada] adi4u4882:
These guys really know how to be a pain in the ASS :D
[Android Development on Bada] midas5:
For the port, how is the phone made to boot from the external sd card? Does to do it from the IROM or in the PBL or SBL ? I ask because we are trying to get an I9000 to boot from sd card, but are having problems finding a way to do it.
[Android Development on Bada] saeedsis:
oleg where are you ?
[Android Development on Bada] CartmanxD:
so i really want to help... but i have some questions:

- you need a changed bootloader to load android and bada.. but in the boodloader is the IMEI number saved. So how does it works to flash a bootloader without changing the imei??

- you put the android on a sdcard linux-partition. Doesn´t it work on the normal sdcard partition with fat32 with a "android" folder? would be easier if it works.

- and i tried to look into the normal bootloader from bada but i can`t it is protected. There are only strange signs. How did you encrypt it.??

- I want to help testing or do sth. else. I have no jtag but a s8500 wave and a brain :). So what can i do? :confused:

CartmanxD
[Android Development on Bada] anghelyi:
Basically all the information is here:

http://xdaforums.com/showpost.php?p=13859219&postcount=971

here:

http://code.google.com/p/badadroid/

and here:

http://grpower.ath.cx/~charsi/freenode/#androidonwave.log

to get started, but read it carefully because you can brick your phone!
[Android Development on Bada] lordfarhan40:
Hey why not porting android of "SAMSUNG GOOGLE NEXUS S I9020A" as it also got a led flash while samsung galaxy s does not. please do not get angry if it is a stupid suggestion please.
[Android Development on Bada] vitaliukas:
i think hardware is different as i found in

ifixit. com/ Teardown/ Nexus-S-Teardown / 4365/1
[Android Development on Bada] Fahrenheit51:
I think that talking about general hardware, the Wave is more similar to the Galaxy S than to the Google Nexus S. This has the led flash, but the rest of hardware should be different. Instead the hardware of the Galaxy S is just a bit near to the Wave's one. It's just my noob's opinion. :confused: :p
[Android Development on Bada] adi4u4882:
Dude i know it would be so irritating to answer noob questions but you are the devs so you have to help us! Dont tell us to go to logs and check because i need answers from devs not from noobs,So please answer my questions!

Will doing this atleast will it give something with GUI or just give an error message? And by doing so will it damage my bada os or can i dual-boot? Can i run application or atleast use some feature of Android through this recevory mode? And is this the ALFA part of your porting? And give us a clearer guide! Please you have to answer our questions because if we do something it will brick our phone as you said!

Thanks in Advance :) And sorry for wasting your time!
[Android Development on Bada] Fahrenheit51:
Just like srg.mstr said at this post http://xdaforums.com/showpost.php?p=13859219&postcount=971 .. this is the guide for you. Stop asking what to do .. if you'll brick your phone or which stupid version is the project now! Devs are working. that's enaugh. If you want to try just do what nbates66 said and good luck.

P.S. : IMHO (in my honestly opinion) Devs DOESN'T have to do anything for you.. This is just to reply to your "you are the devs so you have to help us!"
[Android Development on Bada] mushrom:
now is in prealpha, alpha would mean something usefull is working, but is not, only adb, if you have knowledge about linux drivers, android porting, or extensive knowledge of the wave hw, go, and compile (ive compiled, not a big deal), and contribute. if not, just wait like many others...
[Android Development on Bada] adi4u4882:
Thanks for your info! And if i compile and try to boot what will happen? And please tell wethere bada will work if i do that! Thanks in Advance! :)
[Android Development on Bada] mushrom:
that thread is not for that...

you will get adb service runing, and you can comunicate with the phone through it, and somehow you can get screenshots from the phone and do some debugging work.

(ive compiled, but not installed cuz you need JEE, and i like bada 1.2)

android gets installed on sdcard, so bada still untouched:

you press callbutton while powering up -> android

normal power up -> bada
[Android Development on Bada] mijoma:
clarification:

1. You don't need JEE - just JEE bootloader, works with the JL2 apps without problems.

2. You don't need JEE bootloader if you compile FOTA with the right include file (for your bootloader version). I don't know the current status whether there are all the necessary addresses for JL2 bootloader in the .inc file, but finding them is 10 minutes of disassembly.
[Android Development on Bada] nbates66:
currently our XXJL2.inc file contains next to nothing compared to our XXJEE.inc file, after the weeks we were attempting to find the functions inside XXJL2 it almost seems possible that whoever was compiling these firmwares opted to include less functions in the newer bootloaders (such as JL2) or the actual code for the functions was altered somewhat. The main reason creating .inc files for XXJEE and JPKA(an S8530 bootloader) was easier is because the bootloader symbols for these versions were readily available.

S8500XXJEE.inc: http://code.google.com/p/badadroid/source/browse/trunk/FOTA/inc/S8500XXJEE.inc

S8500XXJL2.inc: http://code.google.com/p/badadroid/source/browse/trunk/FOTA/inc/S8500XXJL2.inc

S8530JPA1.inc: http://code.google.com/p/badadroid/source/browse/trunk/FOTA/inc/S8530JPKA1.inc
[Android Development on Bada] mijoma:
I don't see a reason for looking up stuff that's not going to be used, so it doesn't matter that not every address known for JEE is known for JL2. Anything needed can be found in several minutes. What is missing (be specific)?
[Android Development on Bada] srg.mstr:
dump from OneNAND

I made dump from OneNAND:

# toolbox dd if=/dev/block/bml0!c of=/mnt_ext/bml0.bin bs=1024
513024+0 records in
513024+0 records out
525336576 bytes transferred in 154.195 secs (3406962 bytes/sec)

and sent it to oleg. He will write my dump into his OneNAND. If BADA will works fine on his phone, at the next step i'll write his android dump into my S8500.

Is there somebody who analyzed file "S8500_0x00000000_512M_RAW.bin"? Need info about placing "boot_loader.mbn" in it.

Edit1:

bml0.bin (offset=0x0 size=0x20000) = decrypted_boot_loader.bin (offset=0x0 size=0x20000)

bml0.bin (offset=0x40000 size=0x180000) = decrypted_boot_loader.bin (offset=0x20000 size=0x180000)

last 1024 bytes of "decrypted_boot_loader.bin" not found, maybe it's used for secure ROM...

Edit2:

bml0.bin (offset=0x200000 size=0x44b84) = dbl.mbn (offset=0x0 size=0x44b84)
[Android Development on Bada] nbates66:
i did manage to find some functions, but this is one that i never found, and seemed to be necessary(looking into fota thread you can see it was mis-identified at least once):

from XXJEE:

tfs4_opendir	equ 0x424C7AC4

from XXJL2:

tfs4_init equ 0x424C2CE4
tfs4_mount equ 0x424C3A1C
tfs4_open equ 0x424C76F0
tfs4_close equ 0x424C7864
tfs4_read equ 0x424C7C20
[Android Development on Bada] mijoma:
XXJL2:

tfs4_opendir equ 0x424C6804

tfs4_closedir equ 0x424C6B00

tfs4_rmdir equ 0x424C6F44

tfs4_readdir equ 0x424C704C

tfs4_rewinddir equ 0x424C71E8
[Android Development on Bada] Utu_:
I was wondering if you guys have contact with members of samfirmware.com, they have almost al the firmwares for wave as for the galaxy S, so they have to have some sources where they get them from (probably from people within samsung). So those people are likely to have more information about the firmwares and probably have some files you guys are looking for!
[Android Development on Bada] Rebellos:
first part is BL1, BL2_1 and BL2_2, it is equivalent to I9000 PBL (it is too splitted into few parts)

BL1 is loaded by iROM into iRAM, it does nothing but load BL2_1 into iRAM, BL2_1 can check integrity of BL2_2 (if SECKEY found under 0xE0E00_0000 reg) using SHA algorithm, does init of DMC0 and DMC1 (LPDDR & OneDRAM control) and some CPU flags, then loads BL2_2 into LPDDR.

Second part is BL3 - the final and main bootloader.

Decrypt tools doesn't cut last 1024 bytes of BL image and use the same decrypt function for them, so mess comes out, these are in fact Multiloader data, they aren't flashed, so you won't find them on oneNAND.

Note: In S8530 dbl.mbn is being written under 0x400000.
[Android Development on Bada] CartmanxD:
i found something maybe important for the display.

h t t p : //blog.ribomation.com/index.php?s=droid

its a java programm witch shows you the display on your pc.

maybe usefull...:)

CartmanxD
[Android Development on Bada] mylove90:
already have a one made by Dokugogagoji

look at here : http://xdaforums.com/showpost.php?p=14049427&postcount=31

don't forget to say thanks to Dokugogagoji if you found his post useful
[Android Development on Bada] CartmanxD:
yes but i think this programm its only for bada.. and my programme is for android or ? sorry if not... :confused:

because of the notworking displaydriveres maybe this is the way to see the screen :D
[Android Development on Bada] mushrom:
the screenshots are solved with the dalvik debug monitor.
[Android Development on Bada] mijoma:
that is only partly true - look closer
[Android Development on Bada] srg.mstr:
DDMS

screenshot get with DDMS (Dalvik Debug Monitor Service):

Vol +/- move selector "reboot... apply... wipe... wipe... format..."
[Android Development on Bada] oleg_k:
Guys,need help with modem for s8500.

where is stored in s8500 the nv_data?

in m130k we have efs partition with nv_data.bin,

but for s8500 i don't know.
[Android Development on Bada] Rebellos:
Maybe Call Processor has it own flash memory? It can control up to 2 external flash devices.
[Android Development on Bada] nbates66:
perhaps that could explain these functions?

XXJEE.inc

GetDBLBlkData	equ 0x424CDEE8

DRV_Send_ModemBootloader	equ 0x424CDEF4

DRV_Wait_ModemInit	equ 0x424CDF5C

DRV_CopyModemBootBinary	equ 0x424CE004

DRV_Send_BinaryCopyComplete	equ 0x424CE0A8
[Android Development on Bada] cfernr:
Hi, ive trying to compile my own FOTA for JL2 and i v seen S8500XXJL2.inc file is not complete.

At least is not as completed as JEE, and I cant compile any kernel_boot.asm

I'm a bit lost right now
[Android Development on Bada] Rebellos:
If anyone wonders about analysing call processor DBL - first step:

0x4EB4 bytes from dbl.mbn at offset 0x200 (after header, first part of dbl) are loaded (through HDLC packets by BL3 I think) under 0x70800000 (QSC mem mapping) and executed there.

Aint sure if QSC boot from its iROM first and then wait for getting DBL through HDLC packets or it doesn't use iROM and wait for bootloader immediately after power-on (it is configureable by its GPIO pins).

Btw, call processor can be used even to decode MP3 and MP4, it is second very powerful composite unit packed into Waves.

More research to come when I get time, would be good if anyone familiar with IDA will continue it too.

Disassembly and analyse of next 2 QSC bootloaders may show some answers. On first sight of eye It looks like DBL does not much more than basic configuration of QSC DDR controller (to map oneDRAM) and wait for the next parts of code in oneDRAM share.

one more note:

oneNAND drivers are included in dbl, there are 2 possibilities - there is hidden partition on oneNAND/QSC has got its own flash mem.
[Android Development on Bada] adfree:
NV items are in OneNAND. So I think this is what Qualcomm part means with access to memory.

Content of nvm folder is in 512 MB OneNAND.

Check JTAG dumps.

To make folders nvm and NV visible:

http://xdaforums.com/showpost.php?p=12436452&postcount=1

Here are Screenshots...

http://xdaforums.com/showpost.php?p=12532416&postcount=14

Best Regards
[Android Development on Bada] nbates66:
contents of my "nv" and "nvm" folders, Running S8500XXJL2 firmware with XXJEE bootloader.

EDIT: file removed, shall perhaps redo with sim removed and phone reset? :P
[Android Development on Bada] adfree:
@ nbates66

@ all

Please remember that NV items can store PRIVAT data... sometimes Passwords... maybe own phone number...

But Minimum IMEI, BT adress...

Not ever best idea to share public.

Best Regards
[Android Development on Bada] nbates66:
yeah thanks adfree, i wasn't thinking at the time :P

fortunately my wave hasn't been used to handle any sort of passwords etc, own number however :P

as for IMEI, i haven't found it clearly stated anywhere in the files yet...
[Android Development on Bada] nbates66:
Just succeeded in getting display WORKING using SBL with a modified version of the "kernel_boot_srg.asm" code, later can try applying the modifications to the SBL-less bootloader, for now i'm attempting to use anghelyi's solution for stabilizing services.
[Android Development on Bada] Fahrenheit51:
@nbates66 .. What?? really did you manage to get your display working? wow! that's awsome! Hoping in other good news soon! (I'll write an article about this 'cause I'm a writer of StyleTechBlog, and we're following this project)
[Android Development on Bada] cfernr:
display is working, but looks a bit offset.

not GUI yet

thanks to nbates
[Android Development on Bada] anghelyi:
We have GUI :D But it breaks after a minute or less. Here are some screenshots. But be warned, it is'n functional yet!

All the work was done by oleg, mijoma, rebellos, nbates66, srgmstr, etc. I'm just lucky to be the first who managed to put it together with their help...
[Android Development on Bada] nbates66:
i'd like to point out that while anghelyi did manage to get a gui with stable services it is using the emulator platform files, we need to get services stable under the I9000XXJPX platform files. The display going blank after a few minutes issue also shows under ddms, and did so before we got display working, we need that fixed to.
[Android Development on Bada] Danieliko:
Sorry to bother you, I know you hate when people post here, but I have a little question:

When you finish the project, will I be able to change the language to hebrew, or at least the keyboard language?

Any chance you guys will be adding this option in the future?

Thanks.
[Android Development on Bada] vivekforbes:
Languages are comes with OS and i think you need to wait long time for this..once they finished porting then might be some developer will do..
[Android Development on Bada] reaper24x:
I'm pretty sure any final port will come with root access, so (if it doesn't already come with one) you could at least install a Hebrew font and then keyboards are available on the market. At least that's what I did on my old android phone.
[Android Development on Bada] greendoki:
where are the pics?
[Android Development on Bada] wilmervanheerde:
He removed them, because 'it's too early'
[Android Development on Bada] s4tch:
I saw it in the other board, and it looks promising. ;) Best of luck!
[Android Development on Bada] wilmervanheerde:
Gimme the link of the board :P Also check this video of showing the successful but unstable boot: h t t p : / / youtube.com/watch?v=TN03HInkFZg
[Android Development on Bada] srg.mstr:
android from FAT

who want to use FAT for /system folder just need to replace any ext2 symlink to renamed toolbox file, for example: symlink "cat"=32b, after copy "toolbox" with "cat" name it's 79,5k
[Android Development on Bada] greendoki:
this

who did this? :D

h t t p s : / /w w w.y o u tu be . c o m /wa tc h?v=TN0 3HInkFZg&feature=player_em b edd ed

ok now i see sry i can't delete my post
[Android Development on Bada] jakeythesnake:
If this port ever becomes functional I will definitely donate. Hell, I'm buying a wave just for when it does, so you can be sure I will.
[Android Development on Bada] bong4316:
im praying for this project's success!

really hope that it becomes successful!

the video strikes me as showing that wave has the same bootup procedure as the gs1 but once the system wakes up the hardware is not getting the right commands to keep itself functional. suggest that you look into the bada firmware to compare with the android port and observe what happens after bada boots. record the logs like what you did now.

Godbless!
[Android Development on Bada] Rebellos:
I need SBL.bin from SGS I9003, can anyone help me finding? Also Sbl.bin from M130K would be useful for me.

Starting work on S8530 LCD drivers.
[Android Development on Bada] cfernr:
Here you have SBL.bin from I9003DXKB2.

Bye
[Android Development on Bada] cfernr:
SBL.bin m130k

here you have SBL.bin from m130k.

bye
[Android Development on Bada] sabianadmin:
When idiots pretend to know what they are talking about they look like bigger idiots. :)
[Android Development on Bada] funkym0nk3y:
and when pros like you quotes those replies, they look more bigger idiots, why dont you guys just chill out ? Stop replying to any nonsense query, or still if you want to reply, then help someone out with a proper/helpfull reply, i dont knw a thing about anything technical which is been discussed onto this thread, but i also wont post ****full queries,

FFS please read the WHOLE THREAD BECAUSE MOST OF THE THINGS WERE DISCUSSED ALREADY, otherwise you will get a reply like above from the same guy, what else :/.

btw i sold my wave long back just to try out android and bought galaxy s vibrant, personally android is nothing in front of bada in terms of stability, responsiveness but is only ahead in terms of apps, only following this thread to see progress of this port :). Kudos @ sgr.mstr,rebellos,oleg,adfree, and all other for thr great work and support to this port.
[Android Development on Bada] bong4316:
Im sorry ok but theres a more than a hundred pages already and i cant read all of it in one go but ill try.

@sabianaadmin

One of the important differences between the galaxy s and the samsung wave 8500 is the unique way of memory management that the wave 8500 is using.

Disabling the touchwiz on the android firmware from the galaxy before bootup on the wave can free up resources to keep android booting further on the wave and without having to deal with the complexity of resource management on the wave.

It was just an idea it wasnt meant to be insulting, childish like your comment.

I even wished the project well and for its sucess. I dont know why you have to be so negative really. I didnt insult his mother or anything to deserve your reaction. dont worry this forum is now yours to troll in from now on.
[Android Development on Bada] oSandmaNo:
@ Rebellos

here is I9003 Sbl.bin extracted from I9003DXKB2 firmware :D
[Android Development on Bada] sabianadmin:
No no i don't mind you not knowing anything and just thanking the developers all that much, but when you pretend you know what the f*$k you're on about you look pretty stupid, my reputation remains intact, :)
[Android Development on Bada] cfernr:
at least you could search for another firmware. dont you think?
[Android Development on Bada] oSandmaNo:
Oops i saw only your other post

sorryyy!!
[Android Development on Bada] oleg_k:
Rebellos,for support SLCD on s8530 you need:

1)check my kernel souce code on GITHUB - device name is LATONA!

2)choice in config file - CONFIG_FB_S3C_LTE480WV.

3)in s6e63m0.c you need select one of two configurations - Hitachi Panel (r61408) or Sony Panel (nt35580)

And about s9003 - don't use this SBL,phone used omap cpu Omap 3630.

Try to use s9001 sbl or korean SHW-M115S (SHW-M135K).
[Android Development on Bada] anghelyi:
Hi oleg_k,

could you share your init.rc or initramfs with us? It would be great help for us!

TIA!
[Android Development on Bada] Rebellos:
@Oleg

I think it can be Hydis, LCD_ID GPIO is 0 in my case, in LATONA and M130K kernel this is Hydis.

Also there seems to be difference in S8500 and S8530 GPIO.

In S8530 GPIO_MP01(5) is LCD_ID, I guess it is NC in S8500, is it? (It isnt mapped under any specific name in your header file)

BL3 of S8530 supports initialization of few different types of panels, they are identified by hwrev of board and LCD_ID pin.

Didnt know that I9003 uses OMAP, thanks. Anyway It'll be still useful for me as I want to compare panel init sequences with these I can find in I9000, I9003 and M130K drivers.
[Android Development on Bada] oleg_k:
i posted my initramfs on april

github.com/Oleg-k/initramfs_2.6.32_S8500.git