yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] mll2:
wow, this looks promising; keep up the good work, willing !
[Android Q&A, Help & Troubleshooting] :
I just fixed gsm problem. I`m rebuild with new wifi config.
[Android Q&A, Help & Troubleshooting] Rapier07:
@willingmagic

Hey man great job so far.. I've been following this thread. I have a galaxy3 but my girlfriend owns a galaxy 551.

One of our G3 devs [URL="xdaforums.com/member.php?u=3404423:]marcellusbe[/URL], has successfully ported CM7 to G3. May be you could pm him about the graphics glitches. I'm sure he will help you out.

Great job and best luck ahead :)

You can find the CM7 port thread [URL="xdaforums.com/showthread.php?t=1101218]here[/URL]
[Android Q&A, Help & Troubleshooting] kraka23:
Very good job WillingMagic!. Cheers!
[Android Q&A, Help & Troubleshooting] :
Graphics glitch[logcat]:

Settings in Polish language:

Current I fight with no sound.
[Android Q&A, Help & Troubleshooting] hpx70:
Your work is much more than great willingmagic.

this phone is totally ignored by samsung , even it doesn't have a proper name, some say its callisto but when i search it another phone pops up

i think samsung is somehow ashamed of building this phone!

they also may have some mental problems, they did not give this phone gingerbread , calling it old, but some other phones that recieved gingerbread were much older or the same age! where did these fellas learned to use a calendar!

now everybody are looking at you and your progress.

good luck
[Android Q&A, Help & Troubleshooting] karandpr:
Hey those are my lines !!!! :D

It's callisto for sure .People (Websites)confuse Europa I5500,I5503 with callisto due to similar numbers

.
[Android Q&A, Help & Troubleshooting] MajinkenSword:
Awesome! Keep up the good work. Always remember that you have a lot of beta testers available if you need 'em.

Keep it coming!

Kudos!

Sent from my GT-I5510
[Android Q&A, Help & Troubleshooting] mnmlmnn:
Jo, WillingMagic.. as all the others, I am rly thankful that you are doing that for our little device.

I wish I could support you somehow.. but I am just a lazy ass who hopes, that you finish your gingerbread-porting-project successfully.

I sent you a pm.

greets from ger.
[Android Q&A, Help & Troubleshooting] hpx70:
an update on the work status would be appreciated.

currently what are you working on?

what does work? what doesn't?

thanx in advance
[Android Q&A, Help & Troubleshooting] himsplash:
WillingMagic where are you? Any Progress? please reply!
[Android Q&A, Help & Troubleshooting] Torreip:
nice work WillingMagic !

By the way, I guess the I guess the Clockwork recovery is still not compatible with our phone ?
[Android Q&A, Help & Troubleshooting] :
Clockwork recovery will be done later. I`m still fighting with no audio. When basic function as calling works I will release official alpha-zero build.
[Android Q&A, Help & Troubleshooting] freesoul394:
Great. . Very good news. .
[Android Q&A, Help & Troubleshooting] :
Today I order jlink jtag. It cost 97 PLN(~24.30 EUR or ~34.56 USD) with delivery. Now left only second 551 for test.
[Android Q&A, Help & Troubleshooting] hpx70:
jtag for what?

did you brick your phone?
[Android Q&A, Help & Troubleshooting] :
No I didn`t but I`ll able to play safe with clockwork recovery and other stuff.
[Android Q&A, Help & Troubleshooting] MajinkenSword:
Nice, we can't wait! :D
[Android Q&A, Help & Troubleshooting] psyke83:
You don't need to worry about bricking with ClockworkMod Recovery as long as you define the proper devices. Your callisto device has boot at bml9 and recovery at bml10.

You absolutely need these two boardconfig lines to set the proper devices:

BOARD_BML_BOOT := /dev/block/bml9
BOARD_BML_RECOVERY := /dev/block/bml10

You need other stuff defined too. I haven't had time to find out if there are any remaining lines that are obsolete, but they're not causing problems anyway. This is the I5500's current configuration (with 100% working CWM): http://pastebin.com/ztMKZnEt

In particular you need to compare my /proc/LinuStoreIII/bmlinfo with your own device's, and if necessary, adjust the size of the partitions. Keep in mind that I converted the sizes from hexidecimal to decimal, otherwise the build process fails when creating the device container. You should do the same.

If your graphics in recovery are distorted in a similar way to your screenshot in post #1, try using my graphics.c (needs to be defined in boardconfig like shown in my port): http://pastebin.com/Xuq5xvyb

Flashing CWM with Odin is perfectly safe - just make absolutely sure you have the correct parameters before trying any operations related to writing to boot/recovery.

A quick check to make sure that it's safe:

$ strings /sbin/flash_image | grep bml

If the output is bml9 and bml10, you're safe. If it's bml7,8, don't try to flash anything, as flashing to bml8 (arm11boot) will hard brick your phone.
[Android Q&A, Help & Troubleshooting] psyke83:
I recently reworked my port (changing it so that no files are needed in vendor/cyanogen/products), and I got the same problem as in those screenshots.

The problem is that you're not adding some of the the core Cyanogen packages, including ADWLauncher, and the corruption you're seeing is due to the fallback (Launcher2) being buggy/incompatible with our hardware configuration.

Add this line to device_callisto.mk (just after the first line - languages_full):

# Inherit some common cyanogenmod stuff.
$(call inherit-product, vendor/cyanogen/products/common_full.mk)

Do a clean rebuild and you should (hopefully) have the full Cyanogen package set including ADWLauncher.
[Android Q&A, Help & Troubleshooting] :
Thanks Subpsyke. I`m making new build with fix. About playing with recovery

Ajay bricked his phone with broken recovery, and only solution was send phone to Samsung warranty.
[Android Q&A, Help & Troubleshooting] psyke83:
Until very recently, koush hardcoded clockworkmod to access bml7 (for boot) and bml8 (for recovery) - those are the partitions for the ace/mini, and koush wasn't aware that other Samsung phones were different.

If your friend used an older CWM, and tried to flash recovery (bml8, which is our arm11boot), it would overwrite the bootloader and completely brick the phone. I suspect that's what happened with your friend. I came very close to bricking my phone as well; I was trying to flash boot (bml7) multiple times, but nothing harmful happened as it appears to be an unused partition. If I tried to flash a recovery image, my phone would be in the service centre now.

The latest code lets you specify the partitions (see my last post). When you've flashed CWM, just make sure to verify that it's really using bml9/10.
[Android Q&A, Help & Troubleshooting] :
Ok I made new build still no sound.

Graphics work correctly.

After flash is needed to use adb shell when available.

!!!This pre-alpha software!!!

Second pre-alpha

!!!

TYPE THIS AFTER FLASH OR YOU WILL STUCK IN BOOTLOOP.

adb shell
bash
mkfs.ext2 /dev/block/stl13
reboot

My logcat

Known bugs:

No sound

No 2g/3g network

No wifi

No bluetooth

No video media working
[Android Q&A, Help & Troubleshooting] karandpr:
Videos work with soft decoders .

Camera doesnt work

2G network is there but no data connection

Apps can be installed easily

Sound doesnt work

Qwert H/W special keys are

First Row : *123+%&$()

Second row :#456-[]"';

Third row :789=<>!'

Which is a minor annoyance.

Messaging works

good pre-alpha
[Android Q&A, Help & Troubleshooting] hpx70:
what a great news!

i am really eager to flash and test it but i have 2 questions

which software should i use to flash it? ODIN?

is it safe? is there any danger of bricking my device? (BTW i have flashed arkas and it was pretty safe)
[Android Q&A, Help & Troubleshooting] hpx70:
I used ODIN to flash it but it's 15 minutes now that it has stuck in the boot animation!

it just repeating boot animation
[Android Q&A, Help & Troubleshooting] :
DID you done this? If not it won`t work!!!!

adb shell
bash
mkfs.ext2 /dev/block/stl13
reboot
[Android Q&A, Help & Troubleshooting] hpx70:
thanks for the tip!

it worked and I am in ;)
[Android Q&A, Help & Troubleshooting] hpx70:
as far as i noticed in addition to those things you mentioned above:

i tried to make a call but i wasn't able to hang up( and as i am using a pre-paid gsm plan so it used all of my money in my account! ;) never mind, a sacrifice in the name of science!)

video playback does not work at all

camera does not work at all

i know there is no sound working in this but the sound visualizer live wallpaper some how shows that there is some sort of sound playing.

I know this doesn't count as a bug but it's stock keyboard does not support persian and it was the main reason that i flashed back to stock rom from Arkas.

I have to restore stock ROM for now but i will give it another try tomorrow
[Android Q&A, Help & Troubleshooting] :
Little benchmark of my rom:

Linpack 1.2.3
MFLOPS: 8.246
Time: 10.17
Norm Res: 5.68
Precision: 2.220446049250313E-16

Neocore 1.9.13:
61-62 fps

Nenamark1 1.5:
26.5 fps

Quadrant:
Not working (omx libs)

No overclock included.
[Android Q&A, Help & Troubleshooting] karandpr:
Pretty nice .It is fast .

780Mhz of Froyo achieved only a slightly higher bench in neo core .
[Android Q&A, Help & Troubleshooting] :
First alpha is out.

Download link here

Changelog:

Audio is fixed

Media playing now work correctly

You can make photo using camera app.

Performance of last build is lower, because I added some fix to adreno drivers. Backport of newer adreno drivers is in way.

Not work:

Wifi.

Bluetooth.

Radio FM.
[Android Q&A, Help & Troubleshooting] karandpr:
Audio through headset doesnt work :)
[Android Q&A, Help & Troubleshooting] hpx70:
Thank you.

very great news indeed! I am downloading it right now!
[Android Q&A, Help & Troubleshooting] hpx70:
well done. it is wonderfull

shows this error on boot:

"the application ROM manager (process com.koushikdutta.rommanager) has stopped unexpectedly. please try again later." which I thinks is becuase of CWM

Camera doesn't have focus/autofocus

G sensor is not working

Theme manager works perfectly

By the way if it had headset support it could be a quite usable rom

P.S.: please update the first post. this last update really deserves a place in the first post
[Android Q&A, Help & Troubleshooting] himsplash:
wow! going to try it now; but never flashed a rom, please someone give a step by step guide on how to do it, tools required and which stock rom to use from samfirmware in case i want to switch to stock rom again.
[Android Q&A, Help & Troubleshooting] didhiy:
I already tested the 2nd pre alpha yesterday for less than hour, I hope will stick this alpha and the following updates.
[Android Q&A, Help & Troubleshooting] ToJa92:
Registered just to say thank you for your awesome work thus far. I bought this device knowing that Froyo might be newest thing available for it, but I'm happy to discover that work is being done to port gingerbread.
[Android Q&A, Help & Troubleshooting] :
Current I'll focus on kernel development. I'm going to apply some patch to 2.6.32.* tree and then port kernel 2.6.35 or newer.
[Android Q&A, Help & Troubleshooting] spitfire_:
The issue with 3G is related to kernel, or not?
[Android Q&A, Help & Troubleshooting] ToJa92:
Will everything work eventually?

EDIT: Just sent $10 to you, hoping that we will have a fully working Gingerbread port someday.
[Android Q&A, Help & Troubleshooting] didhiy:
Just hoping the 3G connection works.. so I can stick with this till the following updates.

Anyway, setcpu detected 667MHz on this alpha build :D it's really great
[Android Q&A, Help & Troubleshooting] hpx70:
this thing is a bit thirsty! 3 hours off the plug in stand by mode and it has about 80% battery.
[Android Q&A, Help & Troubleshooting] NorTrek:
Thank you all, i have been watching this thread for good time and waiting.

I register here also to tell you how glad i am for you working on this.

Cheers from Norway.
[Android Q&A, Help & Troubleshooting] ToJa92:
Tried it out today, looks nice but obviously isn't working correctly. Flashed to the Arkas firmware, and I'm now waiting for gingerbread.
[Android Q&A, Help & Troubleshooting] dgenx210:
Been literally stalking this thread in the past few weeks and I'm very happy that development is still going on for our phone.

As much as I'd like to test this build, unfortunately this is my production phone but it looks good. Hoping to flash this when it turns to at least beta.
[Android Q&A, Help & Troubleshooting] hpx70:
i write this just to ask a status update

whats going on now?

thanks for your wonderful work

I had your alpha release on my device for about a week and it was great but because i needed headphones i flashed back to stock rom
[Android Q&A, Help & Troubleshooting] :
I builded kernel 2.6.35.7 from source, but no success with it. It doesn`t boot and I don`t why, other broken kernel just hang on android subtitle, but that don`t pass samsung subtitle. I think problem is bootloader, but I can`t check it. I disassemble my 551, but there is no chance to plug jtag to board without soldering direct to msm7227 chip.
[Android Q&A, Help & Troubleshooting] hpx70:
i am somehow a novice in android programming so pardon me if this seems ridiculous, but what is the problem with the previous kernel? your last build that i had flashed was great, can't you just add BT wifi and headphone support to that? that seems enough to me
[Android Q&A, Help & Troubleshooting] splattx_x:
Hi WillingMagic,

Congratulations on your alpha!! It sure looks promising!! :) I think you're right with your bootloader guess. As I understand Froyo bootloader is not compatible with Gingerbread kernel. At least I was told that regarding Galaxy mini and devices are similar. Speaking of which, how are you dealing with amss files? amss files are different between Froyo and Gingerbread versions, is there any way to decompile/edit those files? I have googled for a while but haven't found any information about them
[Android Q&A, Help & Troubleshooting] :
Little update:

1. Amss files are no connected too bootloader.

2. I will deal with bootloader after I return from Polcon.

3. I was force to rollback libgralloc, I updated it but it need new adreno drivers in kernel so I will update it when new kernel is ready.

4. Little change in build config, and updated source, so new build should be available before Wednesday.

5. There is no kitchen for callisto and I won`t make any kitchen for 551.

6. I`m working on flashing tool for linux, something similar to heimdall, but supporting ops files. It will be cli and later will get interface in qt.
[Android Q&A, Help & Troubleshooting] kraka23:
Keep the good work!!!!. Cheers.
[Android Q&A, Help & Troubleshooting] karandpr:
Dont worry about the kitchen .I am working on it already .Need more ideas to be implemented . :)
[Android Q&A, Help & Troubleshooting] hpx70:
Yeeeeha!

It is really good news.Happy to hear about new release.

I am trying to learn these android programming stuff but there is too much to learn and I seem drowned in codes!
[Android Q&A, Help & Troubleshooting] spitfire_:
What is kitchen?

Does wifi/3G work in newer builds?
[Android Q&A, Help & Troubleshooting] hpx70:
It's Friday now. :confused:
[Android Q&A, Help & Troubleshooting] karandpr:
A.) You dont ask a dev "when"

b.)Polcon started yesterday :p
[Android Q&A, Help & Troubleshooting] hpx70:
I know the rules my friend, I am not demanding any thing or expecting willing to do any thing for me, I just wanted to know what happened to the release date that willing said, as simple as that.
[Android Q&A, Help & Troubleshooting] karandpr:
Polcon started yesterday :p

http://www.polcon.fandom.art.pl/aktualnosci.shtml

Willing wont be present till 28th
[Android Q&A, Help & Troubleshooting] hpx70:
Hope he has a good time. And thank you for the information.
[Android Q&A, Help & Troubleshooting] psyke83:
Did you try my ace2europa kernel sources? Note that I had to create the board-europa.c based on the .32 kernel version and fix up a fair few files to make it boot. You'll need to do the same, because I suspect that the europa and callisto-specific code is not properly maintained in this kernel source.

See this commit: https://github.com/psyke83/ace2europa_kernel/commit/00bf6aa6d81c7cca17444df919be96ec7cbc9bc8

I had a lot of trouble getting this kernel to boot (when I could get the codeaurora .35 sources ported much more easily). I eventually isolated the problem to the file arch/arm/mach-msm/io.c. See the above commit to see the difference.
[Android Q&A, Help & Troubleshooting] :
Thanks subpsyke.

I made my kernel working, but I need to fix my initscripts.
[Android Q&A, Help & Troubleshooting] didhiy:
I have two kernel 2.6.35 sources from android git & samsung open source for ace/mini. Is it possible to compile it to froyo? I already compiled the original one from samsung opensource successessfully with the guide from previous post in this thread. But I have no knowledge to compile other version.. I've heard that newest kernel have some advantages on power management so I wanna try to build it. Thx in advanche :)
[Android Q&A, Help & Troubleshooting] splattx_x:
@subpsyke and @WillingMagic: sorry to interrupt but I'm working in porting Gingerbread to Latin Galaxy mini (officially stuck in Froyo and european ROMS cause us to lose connectivity) and there are some points in common with this thread. If I make some progress I'll start new thread.

How do you deal with amss (MODEM) file? Because amss file from Froyo does not work in Gingerbread. I think I only need to port this one file (much easier than the superb job WillingMagic is doing with Callisto) but I can't seem to find much information anywhere... Have you guys found a workaround for your Europa/Callisto ports?? Or haven't got that far yet? Do you think it would be good to start a new thread to share information about these amss files?

Cheers!! Keep up the good work!!
[Android Q&A, Help & Troubleshooting] psyke83:
The baseband/amss is a proprietary binary file/partition. It's impossible to "port" it - you're forced to use whatever Samsung has released for your phone.
[Android Q&A, Help & Troubleshooting] psyke83:
You could get the FSR drivers working? Can you give more detail please?
[Android Q&A, Help & Troubleshooting] :
Subpsyke no still not working but I got little progress, I slowly write onenand driver for msm7*** so I think in this month I will get working driver.

THERE IS NO NEW RELEASE

I will not release new build until I do something important, like made something working like bluetooth or make clockwork recovery.

THERE IS NO WORKING CLOCKWORK RECOVERY FOR 551

I builded one but there was a lot of problems.I will do recovery after done writing onenand driver.
[Android Q&A, Help & Troubleshooting] smoke87:
Willing,

After days searching and testing how to see internal partitions in 2.6.35.7 for our device, i finally got it..

Just get gmini kernel from opensource.samsung.com, do make callisto config , change only the file that subpsyke mencioned in his post(arch/arm/mach-msm/io.c) and boot with galaxy mini(S5570XXKPK) fsr and rfs modules.

But to me happen bad things after i load this fsr modules.

Attached Kernel log messages after mounted system and data on android boot.

My stl12(system) and (stl13)data are ext2 formatted.

After reboot the phone always stops on line 478 in log attached:

<4>[ 3.236063] multipdp_init:multipdp_rx_noti_regi calling

The next step should be:

<6>[ 3.241924] Freeing init memory: 160K

Now i'm trying wakeup the phone... but i no have idea what happened. (OneNAND or RAM Bricked/Corrupted?)
[Android Q&A, Help & Troubleshooting] :
Using fsr and other samsung driver is bad idea. Ok we got kernel 2.6.35.* working, but we can't use newer because there is not newer driver for onenand.

I'm writing (with big help Tom3q) support for generic onenand driver, which use mtd partition system, so we will get ubifs support which is fastest file partition system for flash memory.
[Android Q&A, Help & Troubleshooting] vipul955:
willing magic

i can be the tester

as soon you get a good news..

let me know
[Android Q&A, Help & Troubleshooting] :
There is working clockwork for 551. It will released after finish onenand driver. I already uploaded it so maybe you can find it in dark corners of internet:)
[Android Q&A, Help & Troubleshooting] didhiy:
Great news :D
[Android Q&A, Help & Troubleshooting] karandpr:
Without a SHA-256 value to cross check,the dark corners of internet remain dark.

Good Job

Saves me a lot of work :D.I can shelve Gearloose Advanced Backup Manager for good .
[Android Q&A, Help & Troubleshooting] :
0c43d169ca0e4a0833d5b60763d82ade112b3d5a5d546955a55f72b6c3b3cd14 CLOCKWORK_RECOVERY_551.7z
[Android Q&A, Help & Troubleshooting] ferreinf:
A link please... :-)
[Android Q&A, Help & Troubleshooting] :
Ok, I'll need 15 testers for new rom. It has kernel 2.6.35 with new onenand driver and clockwork recovery.

No PM only in this topic.

I need info about skills. Test should begin in this week.
[Android Q&A, Help & Troubleshooting] didhiy:
I compiled kernel 2.6.32 for myself, have a build environtment on my ubuntu then I used Arkas since the unstable version that hang or reboot randomly :) maybe you can choose me as one of the testers.
[Android Q&A, Help & Troubleshooting] asbirim:
i can test it anyway. please add me to tester list.

thanks for helping to us
[Android Q&A, Help & Troubleshooting] karandpr:
I got nothing else to do . I can make funny one liners .

Not much skills if you ask me .

Can Make Decent Frameworks .
[Android Q&A, Help & Troubleshooting] vipul955:
me ready to be the tester..:D
[Android Q&A, Help & Troubleshooting] didhiy:
Not much skills :p hehe

but better you wrote that, because if you tell all what you & enigma team has done for galaxy 551 maybe this page will fulfilled with your words :D
[Android Q&A, Help & Troubleshooting] hpx70:
I have no special skills but I know how to make an OS crash and overload it with programs untill some bugs show up! Is it enough for being a beta tester?
[Android Q&A, Help & Troubleshooting] pinkflozd:
i would like to voulounteer, my skills: kernel knowledge and unix knowledge, i'm workin with karan on the arkas builds.

hope i can help
[Android Q&A, Help & Troubleshooting] ferreinf:
+1 ;)
[Android Q&A, Help & Troubleshooting] Mitter21:
Quite curious http://xdaforums.com/showthread.php?t=997436&page=33 this is a Brazilian website that is offering the manual for Galaxy 551 with android 2.3.
[Android Q&A, Help & Troubleshooting] kraka23:
Well, no much to say ... I'm a regular user, some incursions in compiling AOSP recovery and some kernel but nothing more. Cheers
[Android Q&A, Help & Troubleshooting] :
Here is official mailing list:

http://groups.google.com/group/samsung-galaxy-551
[Android Q&A, Help & Troubleshooting] hpx70:
sorry for noob question Willing magic

I know how to flash this CWM recovery but I do not have the guts to do it myself. So could you possibly explain how to flash it? Can we flash back to original samsung recovery in case we need samsung guaranty? If yes, how?

It would be kind of you to answer these questions.

Wish you best of the best!

good luck
[Android Q&A, Help & Troubleshooting] :
Install instruction will be released with new kernel 2.6.35 .

This file overwrite samsung recovery. To remove clockwork recovery you flash samsung pda(it contain kernel, recover-kernel, system.rfs, data.rfs),
[Android Q&A, Help & Troubleshooting] hpx70:
I have flashed it using callisto.ops in the samfirmware.com and one package option

it boots in recovery and following each key press keeps writing "E:Can't mount /cache/recovery/command/ log etc..."

And the main problem is that phone just boots into recovery and it's not possible to boot into Android itself nor the Download mode. but emergency DL mode is accessible.

I know there is no obligation for you to answer this but it would be kind of you to help me!

S.O.S. ;)