yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks, I'm currently downloading. Will update as soon as I've inspected the ROM. (I'm sitting at the end of a very slow line... still 11 minutes after quite some typing.)

Re changes: most of the growth seems to be caused by png files having grown in size - one of the most prominent examples is the res/ folder inside the /system/app/Apollo.apk package (which has grown from 974571 to 1598001 bytes - +60%!):

2014-03-07 13:21:10 ..... 42826 42826 res/drawable-nodpi/app_widget_large.png
2014-03-07 13:21:10 ..... 24035 24035 res/drawable-nodpi/app_widget_large_alternate.png
2014-03-07 13:21:10 ..... 51175 51175 res/drawable-nodpi/app_widget_recents.png
2014-03-07 13:21:10 ..... 94741 94741 res/drawable-nodpi/app_widget_recents_stack_preview.png
2014-03-07 13:21:10 ..... 12325 12325 res/drawable-nodpi/app_widget_small.png
2014-03-07 13:21:10 ..... 1588 1588 res/drawable-nodpi/background_holo_dark.png
2014-03-07 13:21:10 ..... 13429 13429 res/drawable-nodpi/header_temp.png
2014-03-07 13:21:10 ..... 17608 17608 res/drawable-nodpi/theme_preview.png

vs.

2008-02-29 02:33:46 ..... 147385 147385 res/drawable-nodpi/app_widget_large.png
2008-02-29 02:33:46 ..... 79020 79020 res/drawable-nodpi/app_widget_large_alternate.png
2008-02-29 02:33:46 ..... 176259 176259 res/drawable-nodpi/app_widget_recents.png
2008-02-29 02:33:46 ..... 353928 353928 res/drawable-nodpi/app_widget_recents_stack_preview.png
2008-02-29 02:33:46 ..... 36377 36377 res/drawable-nodpi/app_widget_small.png
2008-02-29 02:33:46 ..... 1495 1495 res/drawable-nodpi/background_holo_dark.png
2008-02-29 02:33:46 ..... 29240 29240 res/drawable-nodpi/header_temp.png
2008-02-29 02:33:46 ..... 34115 34115 res/drawable-nodpi/theme_preview.png

If the new build could use the same png files (their geometric size in unchanged, but something must have happened regarding their compression/quality), the resulting ROM might fit better. Let's see what has changed with the 0914 build... (to be continued)
[Samsung Galaxy 551 Callisto] Mm7:
Ok, I think I discovered the problem.

Cyanogenmod optimizes PNGs in 2 ways:

lossy optimizations: Ok for most of PNGs, high size reduction

lossyless optimizations: needed by 9.png (9 png markers must not be touched), low size reduction.

In my system a lossyless tool was installed (pngcrush), but a lossy was not, so the build system silently skipped lossy optimizations. I've just installed pngquant (a lossy optimizer tool) and rebuilt the rom:

-rw-r--r-- 2 mm7 mm7 116761959 Sep 4 18:57 cm-11-20150904-UNOFFICIAL-callisto.zip
-rw-r--r-- 2 mm7 mm7 116765452 Sep 14 23:00 cm-11-20150914-UNOFFICIAL-callisto.zip
-rw-r--r-- 2 mm7 mm7 112765916 Sep 15 19:14 cm-11-20150915-UNOFFICIAL-callisto.zip

I'll provide you a download link as soon as possible. :)

EDIT: Here's the download link: http://www.mediafire.com/download/rgx73rgmtwsux4h/cm-11-20150915-UNOFFICIAL-callisto.zip
[Samsung Galaxy 551 Callisto] steve8x8:
;) (*happy*)

Meanwhile the download finished, and I was able to check the size of the /system tree when unpacked on my harddisk:

$ du -sh 2015*/system
177M	20150211/system
181M	20150904/system
176M 20150914/system

That looks better now. (I also saw that you have moved WhisperPush and LiveWallpapers to extras/ - fine with me as I wouldn't use them on the 551 ;) ).

I will try to dirty flash the new ROM over mine, and report back. (I'm sure the final build will even have Term back.)

( Edit: )

DIrty flashing didn't work - there was a request to factory reset, both with CWM6 and TWRP 2.7.0.0.

DId that under TWRP, still no cigar. Back to CWM6, which had been there all the time... and worked well with the "Latest" ROM from Feb. (TWRP, while running on virtually every other device of my collection, doesn't make me happy on the Callisto.)

"Install from sdcard complete". Wow. Too bad that "adb shell" in recovery mode doesn't show /system... wait... there's a "mount" menu, right? Indeed, in the shell I now see

/dev/block/stl12 185688 184116 1572 99% /system

Fair enough... Good work!

( Edit 2: )

Checking "About Phone" I observe that the kernel build date has changed but not the Android build date and CM version.

Also, "adb shell" now complains:

$ adb shell
id: no such tool@getprop: no such tool:/ $

(ls, pwd, ... don'r work as well - prefixing the commands with "busybox" works.)

( another edit: ) this seems to be related to File Manager complaining about missing permissions, and not starting - no chance to install apks

( Edit 2b: )

I cannot even go back to Final without Factory Reset, "trying to install on top of incompatible data" - why is this? On my OnePlus, I could even upgrade from CM11 to 12.1 without a single full wipe... /system/bin/otasigcheck.sh seems to be a bit too overambitious here? Flashing FInal and 0914 directly after each other works if not rebooted in between, hm...

I'm off for tonight. CU tomorrow...
[Samsung Galaxy 551 Callisto] Mm7:
"df" should work in recovery. Where does it fail?

Hhhmmm, works fine on my cooper. Can you generate a logcat?

You can disable it in updater-script as a workaround. I don't know how is it supposed to work.
[Samsung Galaxy 551 Callisto] Mm7:
/system is unmounted after flashing (look at the last line of updater-script). If you need it mounted you can type:

mount /system

Sorry, my fault! Last time I worked on FSR I needed a ioctl command line tool to use in recovery, so I changed toolbox's Android.mk to generate a statically linked executable (recovery can't handle dynamic libs). But when I built the recent builds I forgot to revert this change ... (i'm stupid!)

Dynamic linking do result in smaller executables.

The camera subsystem got lots of changes (and the recent ones weren't tested very well).

Situation 1: Cooper, tass, mini, gio, callisto were using "cameraHAL" as the CameraHAL (and samsung's libcamera and liboemcamera), I suppose that they were successfully taking photos and recording videos (video resolution hardcoded to 320x240). Galaxy5 was using QcomCamera as CameraHAL and QualcommHardwareInterface as libcamera, (and samsung's liboemcamera). I suppose that galaxy5 was fine.

Situation 2: Galaxy5, tass, gio, callisto: unchanged. Cooper and beni were affected by this patch that aims to use the full supported resolution (5mp - 640x480). Problem: This patch doesn't work. It simply broke video recording on cooper and beni. [probably it was untested]

Situation 3: Galaxy5's QcomCamera and QualcommHardwareInterface was moved from galaxy5 repo to msm7x27 generic repo and these interfaces were extended to tass, gio and callisto. The old "cameraHAL" was still used by cooper and beni. The 640x480 patch was extended to support also 480x320 devices (callisto, gio and tass). It seems that QcomCamera and QualcommHardwareInterface don't work very well with gio, tass and callisto (psyke83, erikcas and I tried to fix problem, but we failed: reference). I suppose that at this point video recording stopped working also for callisto, tass and gio (right?). I seems also that the camera stopped being colorful.

Situation 4: 640x480 patch was reverted for cooper/beni. This fixed video recording on cooper/beni.

Situazion 5 (now): QcomCamera was updated to support samsung's libcamera properly, so cooper and beni switched to it and the old "cameraHAL" was removed.

I think that non-320x240 video recording resolutions break the video recording. I saw it breaking video recording on cooper (and beni folks said the same for their device) and I think that it is the same for gio, callisto and tass. For example this post say that video recording was broken in callisto in January 2015 (jan 2015 = situation 5).

New build: http://www.mediafire.com/download/pmr4w1x49ok60iw/cm-11-20150916-UNOFFICIAL-callisto.zip

toolbox fixed

experimental video recording fix: revert to 320x240 resolution
[Samsung Galaxy 551 Callisto] Mm7:
Honestly, LiveWallpapers are really wasting /system space. No one will ever use them (especially on a 256MB-super-laggy device). And term can be installed from the google play.

I recall this issue (I use to get it when I was trying to extend open-libcamera to cooper). "native_set_parm" will trigger a error if ctrlCmd.status != CAM_CTRL_SUCCESS. I don't think that the kernel-space driver set this field. But I must admit that QualcommHardwareInterface is successfully working on galaxy5, so I could be wrong.

NOTE: CAM_CTRL_SUCCESS expands to 1, so memzeroing the whole struct won't pre-configure the status to success.

If my supposition is correct, removing this check may fix the bug. This is the new camera.msm7x27.so [complete path= /system/lib/hw/camera.msm7x27.so]
[Samsung Galaxy 551 Callisto] Mm7:
Ok. I'll build new CM for all devices

My build camera.msm7x27 is exactly the same as Final ROM because I'm using the same sources.

I don't know. A deeper investigation is needed.

The camera app crashes due to this:

E/CameraSource( 395): Failed to set video frame size to 320x240. The actual video size is 480x320

This is a trivial bug, which can be easily fixed. But I'm confused by:

E/mm-camera( 395): LENS ROLLOFF not supported on this SENSOR!!!

This seems something complex to fix. Moreover, samsung's libcamera is really more complex than QualcommHardwareInterface (I can see many symbols that open libcamera doesn't have), I think that we are missing crucial pieces of code.

Anyway, I'm sorry, now I don't have enough time to spend on this.

My previous post should be a good "history" map of camera developments.

Androidmeda was the maintainer of the LG msm7x27 phones. He is a great developer! That string of build.prop is automatically generated during build time.
[Samsung Galaxy 551 Callisto] Antonio Almeida Filho:
I need the new cwm! I'm on cwm 6.0.4.6 and I get status 0!

send links!!!
[Samsung Galaxy 551 Callisto] Antonio Almeida Filho:
someone could send download links of the CWM 6.0.5.3?

Enviado do meu LG-E610
[Samsung Galaxy 551 Callisto] steve8x8:
http://xdaforums.com/showpost.php?p=61722839&postcount=14 has a link to the last ROMS from Jenkins, and some other stuff, including a CWM image.
[Samsung Galaxy 551 Callisto] Antonio Almeida Filho:
Thank you!

Enviado do meu LG-E610
[Samsung Galaxy 551 Callisto] steve8x8:
Hello [MENTION=5051035]Mm7[/MENTION], I presume you're busy merging the latest (StageFright 2.0) patches into CM11.0? I'd be willing to test the 551 flavour - when it's ready.
[Samsung Galaxy 551 Callisto] JoshinPl:
I see that samsung released the source code for cooper builds, is it helpful in terms of building a stable CM?

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=S5830
[Samsung Galaxy 551 Callisto] steve8x8:
There's one for the I5510(M) too, which is closer to our Callisto target. I'm in doubt though that it would help much, but I also may have no idea at all.

Edit: Contents are dated Apr 19, 2011. That's probably not even Gingerbread.
[Samsung Galaxy 551 Callisto] steve8x8:
Half a year ago, [MENTION=5051035]Mm7[/MENTION] had built several ROMs for the Callisto but somehow missed the last step (after ironing out a few quirks that consumed too much flash memory)... and then disappeared without leaving a trace. There's still that Galaxy551 waiting for a "final" CM11 ROM. Any suggestions?
[Samsung Galaxy 551 Callisto] KIMO82:
I have the same issue at first just when the phone go sleep now when it boot too any help plz ?
[Samsung Galaxy 551 Callisto] kronflux:
Unfortunately I never found a solution to this issue, but I've LONG since moved on.

In some ways unfortunately, but in other ways very fortunately, the AndroidARMv6 project died off about a year ago, most, if not all the devs with these devices(the htc marvel, chacha and a couple others as well as the samsung callisto and a couple others) have long since moved onto devices which can actually support modern OS's without a hitch. Most of them don't even OWN the devices anymore, let alone support them.

It sucks for the select few who are still using these devices, but the reality is, ARM6 dates back all the way to 2002, and is very obsolete. A good comparison would be asking for Windows XP to continue to receive support, as it was released in 2001. It just doesn't make sense for anyone, not even enthusiasts.

Best bet is to let ARMv6 die off.
[Samsung Galaxy 551 Callisto] steve8x8:
:crying: (@Mm7, could you share your build environment?)
[Samsung Galaxy 551 Callisto] Mm7:
Hi,

You can build androidarmv6's sources by following these instructions ("getting started" section). If you need help, feel free to reply.
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks for the heads-up and the link - I had ignored the README, and was confused by my previous, and failed, attempt to get a working repo setup for the Milestone2 (also armv6, also cm-11.0 - some of the repositories listed had gone in the meantime). I'll try when I can restore my access to the build machine.

Edit: Stuck with errors during "repo sync". This seems to be a disadvantage of distributed storage: if part of the clouds evaporate, the setup as a whole is not consistent any longer. So for now this means I'm too late to clone some of the partial repos (which ones, is hard to find since "repo sync" seems to work in parallel and errors do not seem to belong to the line output before) - unless someone puts up a fresh copy (for me, or for all). Thanks so far.
[Samsung Galaxy 551 Callisto] Mm7:
androidarmv6's github is still alive, you should be able to sync.

Can you post the error please?

Anyway I should have a buildable cm-11 tree in a backup.
[Samsung Galaxy 551 Callisto] steve8x8:
Sorry for the delay, it took me a while to figure out that "repo sync --no-clone-bundle --jobs=1" would be suited best to isolate the issue.

It's "Fetching project cyngn/android_vendor_cyngn" that returns "Repository not found." - obviously a side-effect of Cyanogen's latest moves.. There's "spezi77/android_vendor_cyngn" listed by GitHub which looks like the only existing unchanged fork and might serve as a drop-in replacement (and I'm going to clone/fork it "just in case"). How would one make the change in the general context?
[Samsung Galaxy 551 Callisto] steve8x8:
Ah... I got beyond this, by replacing "cyngn" with "spezi77" (thanks [MENTION=5091819]spezi77[/MENTION] for keeping a copy) in the .repo/manifests tree, doing a "--force-sync vendor/cyngn" and restarting rhe "repo sync" step. (If one makes the changes right after "repo init", that should be a lot smoother.)

Got to "brunch callisto" which now retrieves another heap of stuff. Let's keep fingers crossed there'll be no more surprises... (except that java 1.8 is the default on a Debian Stretch machine - should I get Jessie instead?)
[Samsung Galaxy 551 Callisto] spezi77:
You are welcome, and best of luck with your cm-11 ROM. :good:
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks a lot for your wishes, I might need them. :cool:

For now I'm stuck at libaudioeffect_jni - which may be related to the high gcc version in Stretch. I'll find a Debian Jessie box (which will spare me the java 1.7 vs 1.8 hassle as well) and report back.
[Samsung Galaxy 551 Callisto] Mm7:
vendor cm shouldn't be of any use. You can safely remove it from the local repo manifest (.repo/manifest.xml should be the path, please check), this should fix "repo sync"

I remember some issues related to new patches made by upstream that broke the build. I think that the issue you are experiencing is provoked by one of these (debian's GCC should be irrelevant because android uses a bundled version of GCC [check prebuilt or prebuilts folder]).

I think that it was introduced by this commit.

Try to revert it with:

cd frameworks/av
git revert c3656a6e4151e076c20ee2e38dbcb986275b4560
cd ../..

If this change wasn't useful, you can undo it with:

cd frameworks/av
git checkout HEAD~
cd ../..

If this doesn't work, please can you post the error. Have a good day
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks, but:

fatal: bad object c3656a6e4151e076c20ee2e38dbcb986275b4560

(Tried twice, first time typing the string, second time copying it from the commit URL.)

Am I using the wrong branch?

Edit: Wrong subdirectory. Got to go to frameworks/base, revert worked!

I'm restarting from scratch now (what's Android's equivalent to "make clean"?) - and will report.

Edit 2: Here's the report.

...
target thumb C++: libstagefright_soft_rawdec <= frameworks/av/media/libstagefright/codecs/raw/SoftRaw.cpp
target thumb C++: libstagefright_soft_vorbisdec <= frameworks/av/media/libstagefright/codecs/vorbis/dec/SoftVorbis.cpp
target thumb C++: libstagefright_soft_vpxdec <= frameworks/av/media/libstagefright/codecs/on2/dec/SoftVPX.cpp
frameworks/av/media/libstagefright/codecs/on2/dec/SoftVPX.cpp: In member function 'virtual void android::SoftVPX::onQueueFilled(OMX_U32)':
frameworks/av/media/libstagefright/codecs/on2/dec/SoftVPX.cpp:137:13: error: 'IMG_FMT_I420' was not declared in this scope
frameworks/av/media/libstagefright/codecs/on2/dec/SoftVPX.cpp:158:67: error: 'PLANE_Y' was not declared in this scope
frameworks/av/media/libstagefright/codecs/on2/dec/SoftVPX.cpp:167:52: error: 'PLANE_U' was not declared in this scope
frameworks/av/media/libstagefright/codecs/on2/dec/SoftVPX.cpp:175:52: error: 'PLANE_V' was not declared in this scope
build/core/binary.mk:432: recipe for target '/scratch/CyanogenMod/cm11-callisto/out/target/product/callisto/obj/SHARED_LIBRARIES/libstagefright_soft_vpxdec_intermediates/SoftVPX.o' failed
make: *** [/scratch/CyanogenMod/cm11-callisto/out/target/product/callisto/obj/SHARED_LIBRARIES/libstagefright_soft_vpxdec_intermediates/SoftVPX.o] Error 1
make: *** Waiting for unfinished jobs....

Now StageFright is actually one of the reasons for a rebuild attempt... but the file (apparently) causing the problem hasn't been modified since Jun'13. Changes in VPX?
[Samsung Galaxy 551 Callisto] Mm7:
Yes.

Fixed by this commit.

Apply it with (in frameworks/av):

curl https://github.com/CyanogenMod/android_frameworks_av/commit/6911d18689ac58671ab1f6f09ea00a7cf3cf1082.patch | git am

Again, if you need to undo it; run (in frameworks/av):

git checkout HEAD~

Based on this site, "make clean" should be available, isn't it?
[Samsung Galaxy 551 Callisto] zelotypea:
Hello .

I'm finding that the command #flash_image recoveryonly /sdcard/recovery.img is telling me "not found"

as it - it cannot find that command (it would seem).

Can anyone offer a viable solution? I would like to install Clockwork Mod for this Samsung 551.

My end goal is to install cynogen 11 (android 4.4), as per OP.
[Samsung Galaxy 551 Callisto] Maraschalchi:
I'm already testing the ROM,

but I can not install the gapps, sync google accounts or use the play store.

Thanks to the dev.
[Samsung Galaxy 551 Callisto] psyke83:
Rather than running an entire build, I'd appreciate if someone who knows how to use ADB or the phone terminal app could test a new keylayout file.

Download this file: https://github.com/androidarmv6/android_frameworks_base/blob/cm-11.0/data/keyboards/Generic.kcm (click the raw button).

Save it to your phone's /sdcard, and then run these commands:

mount -o remount,rw /system
cp /sdcard/Generic.kcm /system/usr/keylayout/sec_keypad.kcm

Then reboot and let me know what keys are now broken/working.
[Samsung Galaxy 551 Callisto] stevenanggelo:
the problem still persist

the alt,shift, and enter button still not working

and the ? button became '
[Samsung Galaxy 551 Callisto] darblack:
Correction keyboard Callisto

I used this to correct problems callisto keyboard.

It installs recovery.

https://mega.co.nz/#!YlRnlCwK!b2jJonAqAee-0Vrn-kjpwGeMWldbhslxtLWAz7QMer0
[Samsung Galaxy 551 Callisto] marniel647:
Can anyone give me the link for the latest build in jenkins. thanks
[Samsung Galaxy 551 Callisto] Ansh2000:
http://jenkins.androidarmv6.org/job/android/
[Samsung Galaxy 551 Callisto] piterdemon:
Any changes ? Can someone write about this build ?

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] marniel647:
Thanks for the line Ansh. it has a gapps? or what gapps version can we use. Thanks
[Samsung Galaxy 551 Callisto] Ansh2000:
There is no gapp in this build . I will give you the links of gapp after some time.
[Samsung Galaxy 551 Callisto] Maraschalchi:
What has changed for the experimental 1/1/2014 to nightly 11/01/214
[Samsung Galaxy 551 Callisto] psyke83:
I've queued an experimental cm11 build: http://jenkins.androidarmv6.org/job/android-experimental/713

Please test and let me know what's working. You should ideally data-wipe if you have problems, especially before reporting any bugs.

Camera most likely won't be working and wifi will be unstable when resuming from sleep, but everything else should be ok. This build should also have a working keypad (thanks to darblack... if your files were correct).

P.S. You will need CWM 6.0.4.6 or later to flash CM11 builds. You can use ankur850's recovery build here: http://xdaforums.com/devdb/project/?id=2394#downloads - also keep in mind that the new recovery is not backwards compatible with CM10.2 or older packages, so you should make sure that you have CWM 5 ready for flashing if you want to downgrade.
[Samsung Galaxy 551 Callisto] piterdemon:
Okey, big thanks for build, waiting for finish . cwm is waiting for cm11 :D

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] darblack:
CM11 and truth testing q works well. finally the proximity sensor works well hoping to work in 10.2 CM. Keyboard works fine. would be good to have disabled auto rotation display the physical keyboard to the screen position the horizontal. hope the camera is fixed soon. thank you very much to the team for the fantastic job they are doing.
[Samsung Galaxy 551 Callisto] piterdemon:
Can someone provide gapps with working loggin to google account ?

Wytapatano z Ainol Novo 7 Fire CM 11
[Samsung Galaxy 551 Callisto] Maraschalchi:
I will test the ROM and so I find any bugs post here
[Samsung Galaxy 551 Callisto] piterdemon:
I have problem with any core gapps even if I have space in system, contacts wont sync and I cant download from playstore

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] darblack:
To use the virtual keyboard should go to Options -> Keyboard and method of introduction -> disable physical hardware keyboard. so they may use the virtual keyboard, you have to do this every time you reboot the cell. Do this for both CM11 or CM10.2