yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy 551 Callisto] Mu7ammad3adel:
Many thanks psyke83 for the excellent CM11 rom.

I have inquiries about storage (forget about system storage) if anyone can help.

In link2sd, In addition to:

/data

/data/sdext2 (I've partitioned it as ext4)

/cache

/system

,I noticed that I have:

/Storage/sdcard0

/mnt/media_rw/sdcard0

with the exact values of total, free, and used size in both, is that normal??

and after installing facebook (70mb total size) I was left now with a very low internal storage (unfortunately I use the free version of link2sd, so I can't link apps data).

May be it's a "built-in sdext" ROM like the cm7.2 by ajay while I'm not making use of that?? and if not, how can I have more space for user apps?

Excuse my confusion, and thanks alot.
[Samsung Galaxy 551 Callisto] Ansh2000:
since 24/05 nighties we lost camera i.e getting fc within 2 or 3 seconds of opening camera.
[Samsung Galaxy 551 Callisto] kronflux:
am I the only one getting a weird glitchy blackish barely-usable screen when the phone is unlocked after being locked for a few minutes?
[Samsung Galaxy 551 Callisto] Ansh2000:
I don't have such problem.
[Samsung Galaxy 551 Callisto] kronflux:
seems that "force GPU Rendering" may be the cause. I'll have to test further. but I accidentally turned it on :P

I will say, however, that the wifi seems to suck. at least with my network(using WPA2 Personal)

I can connect most of the time, the first time I turn on wifi. but it disconnects shortly after, and has a hard time seeing the network again.

Also, I sometimes get random reboots. This may also be caused by force gpu rendering, but again, requires more testing.

EDIT: nope. wasn't Force GPU Rendering. I think it happens more frequently when it's on, because sometimes I can lock the device, wait a few minutes, wake it, and the screen is fine again.

here's a picture:
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] is double tap to wake possible in our device kernel?
[Samsung Galaxy 551 Callisto] Halogoop:
Good work on this ROM, I've been a fan of your work for a long time

This ROM is currently running smoothly. But about the

Google play services I am still a bit disappointed although

I can understand as the system space is about 3mb left since the

Kitkat Os takes a lot of space. My only request is to add a better camera

Preferably the one used in cm10.1 with the touch to focus feature.
[Samsung Galaxy 551 Callisto] psyke83:
New OTA builds will not install until you install an updated recovery image. Before I provide the image, however, I need some information on the partition sizes for this device. Please, don't perform any OTA updates until I've given you further details.

Can someone please give the output of this command?

adb shell cat /proc/LinuStoreIII/bmlinfo

Thanks.
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] partitions stats we have the following.

System 181 MB

Data 171 MB

Cache 20.90 MB
[Samsung Galaxy 551 Callisto] darblack:
Original Systema Samsung Gingerbread 2.3.6

FSR VERSION: FSR_1.2.1p1_b139_RTM

minor position size units id

1: 0x00000000-0x00180000 0x00180000 6 1

2: 0x00180000-0x00200000 0x00080000 2 2

3: 0x00200000-0x002c0000 0x000c0000 3 3

4: 0x002c0000-0x01bc0000 0x01900000 100 4

5: 0x01bc0000-0x03400000 0x01840000 97 23

6: 0x03400000-0x03900000 0x00500000 20 25

7: 0x03900000-0x05200000 0x01900000 100 5

8: 0x05200000-0x05400000 0x00200000 8 6

9: 0x05400000-0x05e00000 0x00a00000 40 7

10: 0x05e00000-0x06800000 0x00a00000 40 8

11: 0x06800000-0x068c0000 0x000c0000 3 9

12: 0x068c0000-0x12800000 0x0bf40000 765 21

13: 0x12800000-0x1dc00000 0x0b400000 720 22

14: 0x1dc00000-0x1f500000 0x01900000 100 24

(0)(0) bad mapping information

No BadUnit RsvUnit
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] we can flash today cm ota build with old recovery or wait for new recovery?
[Samsung Galaxy 551 Callisto] psyke83:
Please wait. I've queued a build on Jenkins to generate an updated recovery that will be compatible (and will also fix sd partitioning). I'll provide the link soon.

Thanks to everyone for providing the information that I requested.
[Samsung Galaxy 551 Callisto] steve8x8:
I can confirm darblack's table on my 2.3.6 XWKPB device (*), also by reading /dev/bml8 (a.k.a. arm11boot) which contains the same information (@ 0x61600~0x6182f).

Does this mean the low-level boot would check (and possibly fix) the actual partitioning of the flash? (In that case, a patched recovery wouldn't be enough. :crying:)

(*) The partitioning, and also the "cover-all" bml0 "partition", ends with unit # 2003 (of 2047 as counting starts at 0), where the last few (5?) units seem to store bad-block remapping information, and on my device, units 2034~2042 are already in use.

(Edited as "units" are 256kB in size.)
[Samsung Galaxy 551 Callisto] psyke83:
Here's the updated recovery (note: don't try flashing the actual .zip build - it won't work properly): http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1054/

Assuming the file is copied to /sdcard/recovery.img, this procedure will flash the new recovery (requires root privileges in terminal):

adb shell
su
flash_image recoveryonly /sdcard/recovery.img

You don't need to worry, as I didn't modify the partition mapping on callisto. It doesn't make any sense to do this on devices with a larger system partition. The updated recovery is still needed (for compatibility with the hardware TLS register).

It seems that only galaxy5 has a smaller system partition. The way that I remapped the partitions didn't involve any hacks to the bootloader or kernel - it was just to change the assigned partitions for system and data in the fstabs (boot and recovery).
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks a lot for the update and additional information!

Although I'm more used to fastboot, I'll try. Would this recovery work with a stock ROM as well? Just asking, I might be a coward, wanting to go back... (What about packing the recovery.img into a md5'ed tar, and using Odin?)

That's good news at least. Partition mapping may be a serious PITA. I guess I've got to do some serious "zip reading" next - did I get it right that the 0726-NIGHTLY would be fine with your updated recovery?

Well, as I'm leaving for two weeks of vacation at the sea soon, I guess I'll wait until I'm back - I might drop my phone, making all these efforts obsolete (NOOOO....!)

Thanks again!
[Samsung Galaxy 551 Callisto] Ansh2000:
26/7 nighty working fine with updated recovery and also i noticed some improvement in performances.
[Samsung Galaxy 551 Callisto] marniel647:
Hi Psyke thanks for this. any stable gapps out there. Thanks
[Samsung Galaxy 551 Callisto] kronflux:
Still encountering this problem.

After the device has been locked for a few minutes and I wake the device, I get this ^

If I lock the device and wait another few minutes, sometimes I can wake it and it will be normal, but once it goes like that, it's typically stuck like that.

I will mention that my device is the GT-I5510M, however the hardware -should- be identical, and only the radio/modem differs(and I flashed a european radio to get CWM installed in the first place and cannot go back to the Canadian/US radio/modem, as it's only compatible with froyo(which CWM is not compatible with on our device)

That having been said, again, the hardware should be identical, so I really haven't any idea why this happens on my device and nobody else's. I can also say that previous roms(CM10.1) do not have this issue.
[Samsung Galaxy 551 Callisto] darblack:
Friends say that this new version behaves stable RC9?

It works much better than the previous builds?

When calls works smoothly and unhindered?
[Samsung Galaxy 551 Callisto] Ansh2000:
new version behaves same as previous nighty build.
[Samsung Galaxy 551 Callisto] piterdemon:
Calls isnt smooth even on galaxy nexus so dont except magic on callisto -.-

Wytapatano z Galaxy Nexus PA 4.5 beta2 [MENTION=280772]Dirty[/MENTION]Vkernel
[Samsung Galaxy 551 Callisto] psyke83:
I need someone to test an experimental build which aims to fix the Gingerbread libcamera (in order to get a more colourful camera). The link to the build is in this thread: http://xdaforums.com/galaxy-ace/orig-development/patch-video-recording-fix-cm11-t2813168/page9

If you're using an OTA build, you won't be able to install experimental builds without doing a data-wipe (or manually editing the updater-script of the experimental ROM to remove a hash check). For that reason, I recommend that you perform a full CWM backup before flashing the experimental build.

If you do test the build and it doesn't work, please don't forget to provide a logcat (and it's better to reply in the other thread, not this one). Thanks!
[Samsung Galaxy 551 Callisto] steve8x8:
GApps?

Any suggestion which GApps to use? I have https://goo.im/devs/BaNkS/GApps/4.4.4/ on my list but that one seems to be empty now (or my browser is fooling me)

Edit 0: I have found some old (July) zip files of different dates, the minimal gapps one installs fine but both Genie and CalSync fail (out of space?)

Edit 1: OK; I found that Banks has retired, and handed over to PA guys. Whose "nano" gapps package is almost three times the size Banks's minimal one was, and there seems to be no CalendarSyncAdapter :( Would I be able to extract the two APKs, and install them by hand? That would at least give me a starting point...

Edit 2: Apparently the gapps installation had failed as well - the RC9 ROM had 2.6MB free space in /system, and after the OTA update to RC10 (I'm surprised it worked at all, with so little space) that has shrunk to 2.2MB.

As I haven't been able to identify _anything_ large enough in the ROM that might be dropped (TTS would give 1.4MB, and LiveWallpapers another 1 though), I somewhat lost hope it could be done at all... I've seen other ROMs moving some of the apks to /data, but that would be erased by a wipe... Hm :(
[Samsung Galaxy 551 Callisto] darblack:
Link2SD uses the program to mount a partition, and when you have it copies the Phonesky.apk and GmsCore.apk in that partition and using RootExplorer you link the folder System / priv-app will believe so the system is installed on the system itself and with that you will save space for other things.

NOTE: Sorry but my English is not good
[Samsung Galaxy 551 Callisto] steve8x8:
I know about Link2SD, and my phone's life would have ended long ago without it. Unfortunately, Link2SD and recovery-installable zips don't go together very well, and it's a major PITA to unpack a zip by hand, move all the stuff into places (if there's any), and then let Link2SD move it off to the SD again.

I understand that KK on Callisto isn't something for the General Public... and perhaps it was never the goal to have it run with PlayStore at all.
[Samsung Galaxy 551 Callisto] psyke83:
I don't recommend using Link2SD, especially on OTA-enabled ROMs. The app replaces a core system binary (/system/bin/debuggerd) with its own mount script. This is disastrous for OTA-enabled ROMs, because:

installing a full OTA package will delete Link2SD's mount script, which causes your moved apps to break (until you re-launch Link2SD and recreate the script), and:

the modification of the debuggerd binary causes delta update packages to break (as the file's signature is changed, which blocks the update from proceeding).

I suggest that you try my modification of S2E: simple2ext_mod. It's fully compatible with both delta and full OTA updates, unlike most other app2sd apps.

As for gapps, this package is recommended (system version): http://xdaforums.com/showthread.php?t=2623802

P.S. If you've already installed Link2SD, you'll need to remove the mount script and restore the original debuggerd binary before simple2ext_mod (and delta updates) will work correctly. Alternatively, you can just install a full OTA package to undo the damage caused by Link2SD.
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks a lot for this explanation, I hadn't thought about this. No harm done yet as I've gone back to stock GB for a while, but I'll certainly be back!

The instructions say

Need a minimium of 12 MB free space in system partiton

IIRC there wasn't with the ROM I had tried (RC10) - which cleanups would you recommend?
[Samsung Galaxy 551 Callisto] psyke83:
OK, callisto may not have enough space on /system for gapps. Can someone who has CM11 installed without any modifications to /system (including gapps) please tell precisely how much free space is available?

From terminal app:

df /system

From ADB:

adb shell df /system

If someone can provide this information, I can probably find a way to make some free space for gapps in a future version of the ROM.

Additionally, you can verify if gapps installed correctly by looking at the last recovery.log:

adb pull /cache/recovery/last_log

Check the contents of this log, and see if it complains about insufficient disk space near the end of the file.

For S2E users:

If you want to try the /sd-ext version of gapps and you're also using my S2E mod, don't install [MENTION=5165022]Bhargav97[/MENTION]'s mount script, as it will conflict. If you've already installed this package, delete the script:

su
mount -o remount,rw /system
rm /system/etc/init.d/11link2sd

His dalvik cache patch also won't function correctly (as it tries to run before /sd-ext is mounted by S2E's script), but it won't break S2E.
[Samsung Galaxy 551 Callisto] steve8x8:
Don't know whether that's precise, but I jotted down some "/system 2.6M free" after installing RC9. After OTA to RC10, the number shrunk to 2.2M.

I couldn't even flash Genie and CalSyncAdapter (if I'm not mistaken, from BanKs' mid-July builds).

As I had to go back to 10.2, and eventually reflash GB, I can't provide you with anything more precise right now :(
[Samsung Galaxy 551 Callisto] psyke83:
[MENTION=5165022]Bhargav97[/MENTION]'s current sd-ext gapps package isn't compatible with S2E (unrelated to the mount script that I mentioned before). When I have some time, I'll do some tests to see if I can find a satisfactory solution.
[Samsung Galaxy 551 Callisto] nikosddesign:
cant instal installation aborted(status 0)
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] after flashing today Jenkins build recovery I am unable to go in recovery mode always system boot.
[Samsung Galaxy 551 Callisto] psyke83:
Try to enter recovery using the T + power key combination (from the phone off state).
[Samsung Galaxy 551 Callisto] steve8x8:
Any news about GApps, and sd-ext?
[Samsung Galaxy 551 Callisto] berturion:
I am testing cm11 RC11 with Mounts2sd because this app has a functionnality to store system apps into the sd-ext. Using this, I hope to be able to install the recommended Gapps v2.2 package (8Mo).

But, I saw that it fails sometimes with cm11... I will report the results.
[Samsung Galaxy 551 Callisto] berturion:
After installing Mounts2sd and tick "System apps" to move them into the sd-ext partition, and reboot multiple times, the system apps are note moved. It does nothing.

I saw something interesting thow, it is called Aw3som3 : http://xdaforums.com/htc-explorer/orig-development/mod-aw3som3-dynamic-partition-table-t2793929

But it is for the HTC Pico and I am not crazy enough to try it on my callisto.
[Samsung Galaxy 551 Callisto] psyke83:
Here's a gapps sd-ext package that needs testing: http://www.mediafire.com/download/fr9r1hm1488bira/gapps-kk444-20141028-sdext-v2.1.zip

Here's an overview of what I changed compared to [MENTION=5165022]Bhargav97[/MENTION]'s previous sd-ext package:

1. Rebased gapps files to actual kk versions (taken from 160dpi version of minimal gapps package here). I omitted the SetupWizard due to the problem with wifi activation, but it doesn't seem necessary.

2. The gapps files are now extracted to /sd-ext/gapps in order to avoid collisions with any apps2sd/S2E folders that may already be present.

3. I've included a userinit.d script that mounts /sd-ext, and (re)creates the necessary symlinks for both the gapps files on /system, and also the dex cache files, on each boot.

The advantage of using the userinit.d script is that it is now 100% compatible with full OTA updates. The older packages would break gapps when installing a full OTA package, but now the gapps will continue working correctly (as long as you don't wipe /sd-ext and/or delete the userinit.d script).

Something to note: the userinit.d script will mount /sd-ext if necessary, but in such a way as to avoid any conflict with S2E.

If someone could test this on callisto and confirm it works, I'd appreciate it. The other Samsung devices could benefit from this as well. I've tested on totoro, and it seems to be working fine.
[Samsung Galaxy 551 Callisto] Ansh2000:
Installed successfully but g apps didn't appear in apps drawer.
[Samsung Galaxy 551 Callisto] psyke83:
Run this in a terminal:

su
/data/local/userinit.d/update_gapps_links

Is there any output from the last command?
[Samsung Galaxy 551 Callisto] Ansh2000:
link failed Read-only file system
[Samsung Galaxy 551 Callisto] psyke83:
There was a problem with the script failing to remount /system correctly for the ext4 filesystem (it wasn't giving problems on my device that uses yaffs2). I've reuploaded the package with the fixed script (the link/filename is the same). It should be working correctly now.
[Samsung Galaxy 551 Callisto] Ansh2000:
result is same as before.
[Samsung Galaxy 551 Callisto] psyke83:
OK, I need someone to do some troubleshooting. I need this done via ADB in order to see the exact output.

su
/data/local/userinit.d/update_gapps_links

Paste the output here for me to see.

Another thing that will be handy is the output of this command:

su
busybox mount | grep /system
[Samsung Galaxy 551 Callisto] Ansh2000:
Gapps logcat attached.
[Samsung Galaxy 551 Callisto] psyke83:
Thanks - it seems to be a problem with busybox's mount applet. I've updated the package (still the same link/name) to hopefully fix the problem, as well as improve the script a bit further. Please redownload and try one more time.

Edit: For some reason, the busybox mount applet refuses to work when remounting /system. I've changed the script to use toolbox, so it should work now. Please redownload the archive again - I know, it's a pain.
[Samsung Galaxy 551 Callisto] aldweb:
Hello.

Could anyone tell me how to update the keyboard files for the AZERTY (French) keyboard?

Would using files from CyanogenMod 7.2 work?

Thanks.
[Samsung Galaxy 551 Callisto] Ansh2000:
Thanks it is working fine.
[Samsung Galaxy 551 Callisto] psyke83:
It might, but you need to ensure that Android is attempting to load the azerty keylayout (which you can discover by monitoring the logcat during boot). If not, you'll need to replace the qwerty.kl with the azerty keymap, which can break OTA updates.

I'd need to see a logcat taken after a fresh boot to help.
[Samsung Galaxy 551 Callisto] aldweb:
Thank you psyke83 for the quick answer.

You will find attached my boot logcat after a fresh install.

So, after reading it, I guess I have no choice but go for replacing the qwerty.kl file with the azerty keymap.

No big surprise, this is what we French owners of the 551 used to do in previous CM releases.

Will it be enough to update the qwerty.kl file?

I remember updating other files whith CM 7.2 (I also attached my working version).

Cheers.
[Samsung Galaxy 551 Callisto] psyke83:
The qwerty.kl doesn't seem to be used; you need to replace the sec_keypad.kl and sec_keypad.kcm.bin files from the archive you attached. Replacing these files won't break delta updates (as those files are rarely/never modified), but a full update will cause your modifications to be lost due to the fact that full updates format the /system partition.

I can't do much to fix this for you in the actual build, as the physical keyboard isn't any different to the qwerty type (they just printed different letters onto the keys).
[Samsung Galaxy 551 Callisto] aldweb:
Just one more issue maybe: sec_keypad.kcm.bin is the file I have (binary ; less than 1 Kb) when your file is a sec_keypad.kcm (not binary? ; some 15 Kb), so I guess there will be a problem there.

Next step will be to try your gapps sd-ext package and report the logcat if you still need it...
[Samsung Galaxy 551 Callisto] psyke83:
Actually, you may not need to replace the .kcm file at all. Just try the sec_keypad.kl and let me know if your keypad works as expected.

The gapps package has already been confirmed as working on callisto and galaxy5, so I don't need any more feedback from the earlier troubleshooting steps. Just make sure that you're not using an older version of the package.
[Samsung Galaxy 551 Callisto] aldweb:
Hello. Sorry for the late answer, but I was busy these last days.

I indeed confirm that gapps works fine. This is really great, thanks.

Since nothing worked out of the box for the French keyboard, I took the time to rewrite the sec_keypad.kcm and sec_keypad.kl files, and then to package them in a recovery zip update package.

Everything works fine now, and it did not break OTA. So, basically one only needs to apply again the azerty-recovery-signed.zip file in recovery after each OTA update to get back the French AZERTY keyboard.
[Samsung Galaxy 551 Callisto] psyke83:
Testers required for experimental cm11 callisto build using kernel 3.0
[Samsung Galaxy 551 Callisto] psyke83:
Thanks. I added a link to your post in a new section of post #2 (Useful Resources). Your package will survive OTA delta updates, but full OTA updates will wipe your changes, so keep that in mind.

Don't forget my post above, folks... I need testers for the experimental build using kernel 3.0. My hope is to officially switch to this kernel in the official OTA builds (if it proves to be stable), but I can't do that without people to help test and provide me with feedback/logs (as there will inevitably be bugs that need fixing). If nobody helps, then it won't be possible to avail of the new kernel.
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] Thanks for your hard work. I spent around one an half hour including installing and testing and found all hardware components working fine subject to wifi could not test. performance wise it is better than regular build only problem i found, that is black strip approx one cm down side of screen.
[Samsung Galaxy 551 Callisto] Ansh2000:
sorry for forget to attach dmesg and logcat.
[Samsung Galaxy 551 Callisto] psyke83:
Can you please clarify - you couldn't test wifi, but does the wifi driver actually turn on?

Unfortunately, your logs were too short to see all of the information I need. From what I did see in your logs, I do see some minor issues to clean up with some of the callisto drivers. I'll also try to figure out the black strip problem.
[Samsung Galaxy 551 Callisto] Ansh2000:
Tested WI-FI is working.
[Samsung Galaxy 551 Callisto] aldweb:
Hello.

So I tried this new kernel 3 version.

1st feedback: wah, it is much smoother and quicker than last kernel 2 version! Wonderful.

What the previous tester reported, you will understand thanks to the 2 photos I attached. (Funny enough: native device's screenshots are fine, so I had to take pictures from another device).

Wifi works fine, network (at least browser) seems OK.

Bluetooth could play a music to the external sound player linked to the Callisto.

Calculator, keyboard (even physical keyboard), moving around the launcher, etc... no issue so far but the same as the one reported above.

I also attach full logcat and dmesg from initial boot and all of playing around with this version.

If I can help any further, just ask, I will be happy to help you enhancing this kernel 3 version.

Cheers.