yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy 551 Callisto] stevenanggelo:
Well from what i got after a few hour with this rom :

1.Quite stable with only 600mhz clock

2.I can receive file's with bluetooth without 3rd app

3.Wifi scan work perfectly and can detect my home network

4.Network data work

Bug :

1.Camera didn't work

2.Home button became up button and power button became down button, enter button became backscpace and ok became enter
[Samsung Galaxy 551 Callisto] psyke83:
Thanks for the report. I'll investigate the camera problem, it may be a missing kernel driver or a problem with the libcamera library... I'll check it out.

As for the issue with buttons, please reboot into recovery, then choose the option advanced -> key test. Then check all of the keys that you have identified as being incorrectly mapped, and let me know the key value that is reported for each one.

For example:

Vol. up = 115

Vol. down = 114

etc.

Edit: it would also help if you could send me a dmesg log (taken after trying to use the camera).
[Samsung Galaxy 551 Callisto] stevenanggelo:
okay i will report it to you after i get home

sorry for late reply

Edit :

okay sorry for being too long to reply

i'm a little bit busy

for the key test :

power button (became down button): 107

home button (became up button): 102

backspace button (didn't work) : 352

enter button (became backspace): 14

ok button (became enter button): 28

alt button (didn't work) : 56

shift button (didn't work) : 42

question mark (didn't work) : 214

stock camera didn't show at app drawer

so i use camera 360
[Samsung Galaxy 551 Callisto] vvaklnprm:
Download link?
[Samsung Galaxy 551 Callisto] Ansh2000:
any update is coming.
[Samsung Galaxy 551 Callisto] psyke83:
Hi,

I've updated the first post with a new CM10.2 build that needs testing. Please test and leave feedback. I'd really appreciate if someone could post dmesg and logcats after trying the stock camera app.

N.B.: please test only the build that I linked in post #1. Random builds from Jenkins will not have the same device-specific fixes - I need feedback from testers before I can push certain device-specific fixes into the repository with confidence.
[Samsung Galaxy 551 Callisto] stevenanggelo:
can't boot into homescreen

stuck at black screen after reboot from recovery

already to try to pull out the battery

but still no success
[Samsung Galaxy 551 Callisto] Ansh2000:
Not booting stuck on black screen.
[Samsung Galaxy 551 Callisto] psyke83:
Can you try flashing this boot image via Odin to see if it fixes the problem? http://www.mediafire.com/download/571d42f93e4ba54/callisto-boottest1.tar

I also have a request for anyone that's still running CM10.1. Please give me the output of this command:

adb shell strings -fn1 /sys/class/i2c-adapter/*/*/name

The output should look similar to this:

/sys/class/i2c-adapter/i2c-0/0-0020/name: sr200pc10
/sys/class/i2c-adapter/i2c-0/0-0030/name: mmc31xx
/sys/class/i2c-adapter/i2c-0/0-0038/name: bma_accel
/sys/class/i2c-adapter/i2c-2/2-002c/name: synaptics-rmi-ts
/sys/class/i2c-adapter/i2c-3/3-0025/name: fsa9280

Thanks.
[Samsung Galaxy 551 Callisto] stevenanggelo:
the rom can boot into homescreen with that kernel thx psyke

and the stock camera can be launch right now

but can't be use to take photos

and for the cm10.1

/sys/class/i2c-adapter/i2c-0/0-003c/name: s5k5ca
/sys/class/i2c-adapter/i2c-2/2-004a/name: qt602240-ts
/sys/class/i2c-adapter/i2c-3/3-0009/name: kr3dm_accel
/sys/class/i2c-adapter/i2c-3/3-0025/name: fsa9280
/sys/class/i2c-adapter/i2c-3/3-0030/name: mmc31xx
/sys/class/i2c-adapter/i2c-3/3-0044/name: gp2a

edit :

i forgot to include logcat and dmesg
[Samsung Galaxy 551 Callisto] psyke83:
Thanks, I'll keep looking into the camera problems. There are also camera issues on the Mini and Gio, so this is probably the same problem.

Are the hardware keys now working properly?
[Samsung Galaxy 551 Callisto] stevenanggelo:
i didn't test the all of the hardware keys but the home and menu button now working properly

i forget to test it all :p

but i read at the facebook group, the previous build at jenkins has a microphone bug.

after 30sec of phonecall the mic turn off

i didn't know if the bug is persist in your build

i'm gonna test it when i'm have some spare time :D

Edit :

almost all the hardware key working

but the alt,shift,and enter button not working

and the ? button became '

here i include you the stock gingerbread keylayout and ankur cm10.1 keylayout

Download

and i already test the microphone for call about 1 minute and the microphone is working perfectly :good:
[Samsung Galaxy 551 Callisto] marniel647:
I want to test this also but i cannot find the DL link. Will wait for the next build. :)

Thanks for the dev.
[Samsung Galaxy 551 Callisto] Ansh2000:
http://jenkins.androidarmv6.org/job/android-experimental/627/
[Samsung Galaxy 551 Callisto] piterdemon:
I tested it with that boot.img via odin and on first boot proximuty incall was working but bluetooth doesnt work, after reboot proximity dont work but bluetooth now work

EDIT

attached logcat

EDIT2

after attaching logcat proximity start working but sometimes wont work

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] zst123:
Hi,

I have flashed the below CM11 build with 3.0 kernel from post #3. My phone is cooper.

The phone doesn't boot up. It goes in a "forever" boot (The boot animation goes on and on without restarting).

I have taken a logcat. At 11-12 03:27:05.359: is where the system services dies.
[Samsung Galaxy 551 Callisto] psyke83:
This was a problem with the source that was unrelated to the new kernel, and was happening for several different builds. It should be solved now, so I've queued a rebuild (#1153) that should boot properly for you.
[Samsung Galaxy 551 Callisto] hikibavuong:
kernel 3.0.x development has been on bcm21553-common ( galaxy y )
[Samsung Galaxy 551 Callisto] psyke83:
No, these are completely different devices. I have no plans to work on kernel 3.x for bcm21553.
[Samsung Galaxy 551 Callisto] hikibavuong:
ok.sure the device bcm21553 is not able to develop cm12.(android lollipop 5.0 )
[Samsung Galaxy 551 Callisto] ehsan-black:
Device:beni

build : #1151

Hi, [MENTION=3877378]psyke83[/MENTION]

I use kernel 3 build as a daily rom. performance is really better than kernel2.6. good job!

I just want to report an issue . when phone app wants to wake the device , display has a delay . it turns on after 5 or 6 sec. same problem with alarm.

I attached the logcat and dmesg of the event.

sometimes MTP and adb (All USB connections) diconnects and reconnects by itself.

battery consumption is good. WIFI connection is stable.

I also tested USB transfer speed. the results are here:

http://xdaforums.com/showpost.php?p=56692830&postcount=438

tell me if i missed anything for testing :)

thanks again for sparing your time to make a stable kernel 3.:o
[Samsung Galaxy 551 Callisto] psyke83:
Thanks for the report, it was helpful.

Please test this new build that disables CONFIG_PM_RUNTIME in the kernel config: http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1165/

The kernel config CONFIG_PM_RUNTIME has been identified as causing slowdowns (and audio stutter) with the MMC driver, so that would explain the low performance for your SD benchmarks compared to the 2.6 kernel. It's also possible (but not certain by any means) that this config could also be cause of slow wakeup from idle, so it would be great if you could test if my suspicion has any merit. I am worried that disabling this config may increase battery consumption, however.

With these issues in mind, please focus your testing on SD/MMC performance, wakeup delay, and battery usage.
[Samsung Galaxy 551 Callisto] marniel647:
Hi pskye. Thanks for the new build i already flash the CM11 build with kernel 3.0. Attached is the logfiles.

Device :Callisto.

I think it can be use as a daily driver but the max in Processor is only 600mhz. (after some usage it still runs smoothly like the 600+mhz). Will check at the battery after a day of use. SD performance is ok. Wakeup delay is 3-5 seconds.

Thanks will provide feedback when i encounter problem. But i think this build is ok.
[Samsung Galaxy 551 Callisto] aldweb:
So far, so good.

I had no time to play with the device too much, but it stayed still while consuming almost no battery over 3 days of deep sleep (see attached image).

Cheers.
[Samsung Galaxy 551 Callisto] ehsan-black:
device: beni

Build #1165

hi [MENTION=3877378]psyke83[/MENTION] . well, two days of testing. Audio stutter issue fixed but Usb low transfer speed and delay in waking up(Received Calls and Alarm) didn't fix.

Battery consumption increased(Compare to prevoius build)! it seems deep sleep doesn't work correctly. after full charge i haven't used my phone for about 18 hours. after 5 min battery suddenly droped to 30%!

that's all.thanks. :)
[Samsung Galaxy 551 Callisto] Ansh2000:
can an experimental build be triggerd for callisto with latest fix ?
[Samsung Galaxy 551 Callisto] psyke83:
Build #1174 started. Don't forget to provide the requested logs and feedback after some testing; without your feedback, bugfixes and improvements won't be possible.
[Samsung Galaxy 551 Callisto] Ansh2000:
I am using build # 1174 since 5 hours.

Bootanimation - When reboot the phone black screen appears for 2,3 seconds before cm bootanimation starts.

Sensor - Checked compass work fine.

Performance is better than previous kernel 2.6.35 build.

Wake up - There is no difference in wake up time of this build and previous one.
[Samsung Galaxy 551 Callisto] steve8x8:
Excuse my stupidity, but I cannot find anything about where the recovery.img present in the Jenkins cm-experimental 1174 directory would fit in. Do I still need the file from cm-recovery 24?

Would it be possible to flash that (after converting it into a tar.md5 of course) directly using Odin?

I'm starting from scratch, i.e. 2.3.6 GB on my Callisto, and would like to avoid the "via cm10.2"
[Samsung Galaxy 551 Callisto] kronflux:
Don't worry, I screwed up my device and needed to flash the latest recovery through odin as well. So if you're starting from scratch, this should help you out quite a bit.

Latest Callisto Recovery (as of Nov 21 2014)
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks, that's the one that comes with Jenkins cm-experimental 1174. [...]

Edit:

With this recovery installed, the device doesn't boot into stock ROM anymore. Is this expected behaviour? Okay, as I wanted to install CM11 anyway, no big deal :)

As my Callisto had been in the drawer for several weeks now, I don't have a direct speed / response comparison, but in general it behaves nicely (although the OnePlusOne is a bit faster :P). CPU power is hardly sufficient for panorama images ("too fast"), and there seems to be no way to access the SD via USB (mass storage mode doesn't work, and OTG isn't possible due to the HW limitations), got to use ADB then if I can get that to work (? "adb devices" shows nothing right now although ADB debugging *is* on).

For my QWERTY keyboard with "ß" and "?" at the right end, I'll try to come up with a flashable keyboard zip later. (Got to perform some more tests, when I'm done with GPS Status and Z Device Test.)
[Samsung Galaxy 551 Callisto] aldweb:
Hello. If you want me to prepare this keyboard for you, I can do it since I already did this same job for the French AZERTY keyboard layout.

Just attach a picture of your real keyboard in your answer.

Cheers.
[Samsung Galaxy 551 Callisto] steve8x8:
Thanks for your friendly offer - I'd like to try myself first (in particular, Umlaut and other special characters which I had on my GB keyboard). I'll come up with a photo then.

Re tests of Jenkins 1174, done with WiFi but without a Google account:

GPS Status & Toolkit (some older copy I found in my GB backup) doesn't start at all :(

Edit: Must've been an outdated version or something else, a newer version starts fine. Never mind.

Got a fix using A-GPS within half a minute or so, which is reasonable.

(Still I prefer to connect a BT GPS to save battery power.)

Zausan DeviceTest reports "flash" although there is none, and the camera app also offers flash settings.

Z also gets a GPS fix within reasonable time, without using A-GPS data (gets the longitude sign wrong)

Edit: a later version has this issue fixed.

Battery life seems to be, um, complicated: a few-minutes-long "crash" from the lock screen left the keyboard light on, and sent the battery percentage down to 75% from the nineties (I had to press Power for 15 seconds to reboot the device)

Edit: Facing several sudden discharges (from 95% to 70s in seconds)

Also sometimes the device doesn't wake up although the hw kbd get illuminated :( Connecting power plays the sound, but display stays dark. (I've seen this on my OPO as well, might be a general CM11 bug?)

Possible (to be confirmed) workaround: connect to power, wait for the standby sound, disconnect, press Power. (Even stranger.)

Speaking of lockscreen: after waking up, quite often the right third stays black.

I won't complain about the compass as that'd been a desaster with GB before as well ... might well be just my device.

Edit: Re-calibrating it using GPS Status seems to fix this.
[Samsung Galaxy 551 Callisto] ehsan-black:
[MENTION=3877378]psyke83[/MENTION] Hi!i was wondering if you could help me with builing Kernel3 . i was trying to compile Kernel3 (your sources) for beni but i ran into this :

SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Building modules, stage 2.
MODPOST 2 modules
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/boot/compressed/decompress.o
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
[COLOR="Red"]/home/esy/devel/kernel3/arm-eabi-4.4.3-master/bin/arm-eabi-ld: error: arch/arm/boot/compressed/piggy.gzip.o: unknown CPU architecture
/home/esy/devel/kernel3/arm-eabi-4.4.3-master/bin/arm-eabi-ld: error: arch/arm/boot/compressed/lib1funcs.o: unknown CPU architecture
make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2[/COLOR]

I use linaro 4.4.3 toolchain and i've already installed Gzip.

thanks in advance. :)
[Samsung Galaxy 551 Callisto] psyke83:
Your custom toolchain is most likely the problem. The linaro (and regular gcc) 4.4.x toolchain is quite outdated (older than the kernel branch you're trying to build, in fact), so you should try a later version. Android 4.4.x's default EABI toolchain uses gcc 4.6, so you should try that version of the linaro toolchain, too.

Actually, I would suggest that you don't even bother using Linaro's toolchain at all. All of Linaro's performance optimizations have been exclusively focused on armv7+ architectures.
[Samsung Galaxy 551 Callisto] psyke83:
I checked the callisto dmesg provided by [MENTION=5364545]Ansh2000[/MENTION] and noticed that the touchscreen driver is not resuming from suspend correctly. I've triggered callisto build #1177 which includes a patch to the i2c-core driver that may potentially fix the problem. I'd ask for any callisto owners to test and give feedback.

I only need to see a dmesg log from this build to know if the problem is solved, and you can also test the build to see if battery consumption behaviour changes (good or bad).
[Samsung Galaxy 551 Callisto] Ansh2000:
after five hours of use I can say wake up delay is significantly improved. performance is better than all of previous build. Battery consumption is more or less same as regular build kernel 2.6.35

dmesg log attached
[Samsung Galaxy 551 Callisto] ehsan-black:
Well , kernel compiled successfully with toolchain 4.6 :) . thanks for your help .

i've added SmartassV2 and Lulzactive governors to kernel. rom is now smoother.

but i have a problem with wifi driver. when i want to turn on wifi i got this error in logcat:

[COLOR="Red"]E/WifiStateMachine( 742): Failed to load driver[/COLOR]

should i add *.ko file to boot.img? or ramdisk? How?

I remember .ko files for wireless used to be in wifi folder in root of /system :confused:

i also applied your patch for i2c-core driver and it was useful. screen turns on faster than before. thanks
[Samsung Galaxy 551 Callisto] steve8x8:
Here's my QWERTZ keyboard (based on aldweb's work and the adjustments I had made for GB) - which fits my QWERTZ / KLß / NM? hardware very well. I know that there are several hw keyboards around :(

I suppose the new ROM can be dirty-flashed over the 1174 one? Anything that will be lost except the keyboard?

(BTW, I like the idea of adding the smartass governor.

The "failed to load driver" reminds me of GB which had this issue quite often, and some *#*#526#*#* not always restored WiFi. Could this be a hw issue?)

Edit, 20141126: dirty flash (+qwerty) apparently worked; for now I ignored the new recovery.img.

Flash is still reported by ZDeviceTest, and the Camera app.

adb now works via USB connection (but without authentication, and directly into the root account). Nice, makes backups easier.

Is OTG supposed to work, or is there no support by the USB chip? (Connecting an OTG adapter seems to do "something" as adb doesn't work anymore afterwards, so there's also no logcat :()

Any suggestions how to use the builtin fm radio?
[Samsung Galaxy 551 Callisto] ehsan-black:
[MENTION=3877378]psyke83[/MENTION] I could fix wifi . i should compile the whole wifi module each time that i compile a kernel. :cowboy: (Sorry for noob questions)

by the way i was wrong about improvement in delay of waking up. it didn't fix.

now that I have the source I can test everything. tell me if you need any feedback . :)
[Samsung Galaxy 551 Callisto] aldweb:
Indeed, I confirm that the device still wakes up in a very lazy manner...
[Samsung Galaxy 551 Callisto] steve8x8:
To better investigate the USB mass storage mode and OTG issues, I finally managed to run a series of "dmesg" and "logcat" queries.

The attached files are the "overall" ones, with the "linecount" file pointing to several events, 0 after boot, 1 after connecting PC via USB (OS reported "install media" but wasn't able to mount), 2 after disconnecting again, 3 after attaching USB key via OTG adapter, 4 after disconnecting that. (There are no proper timestamps available, which is a pity.)

Note that USB didn't work properly afterwards: no ADB access, no PC connection (although there still was a notification on the Callisto)

Hope that helps debugging the issue a bit...
[Samsung Galaxy 551 Callisto] aldweb:
Device waking up with latest kernel 3 suffers from various side effects:

- either it is really very slow and uses a lot of CPU

- or the device even freezes (screen remains black even though keyboard is lighted), usually I end up by removing the battery to hard-reboot the device

So, attached are my latest dmesg and logcat from my last attempt today (ended up with frozen device).

I hope it helps debugging.
[Samsung Galaxy 551 Callisto] kronflux:
By the way, nobody seemed to be having the same problem as I was, but the 3.0 kernel has fixed the weird glitchy display issue I was having after the device goes to sleep.

Works great now!
[Samsung Galaxy 551 Callisto] Ansh2000:
can an experimental build be triggered for callisto with latest fix of kernel 3 ?
[Samsung Galaxy 551 Callisto] Mm7:
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1193/
[Samsung Galaxy 551 Callisto] steve8x8:
1193 has finished about half an hour ago. Too bad my Callisto had drained its battery... which doesn't come unexpected as it's been on for 3 or 4 days (no GSM, stable WiFi). Spare battery is out of reach. Got to recharge before dirty-flashing.

OK, with 92% I tried... Wiped cache and Dalvik, but not data, flashed ROM, forgot the keyboard zip.

After about 8 minutes of rebuilding the Dalvik cache, I saw the greeting screen background.

The system appears even slower than before, but it might just be me tired after a working day.

WiFi is greyed out, and repeatedly trying to activate it nonetheless gives a reboot.

Neither GPS Status nor Z-DeviceTest are willing to start, and I'm just too lazy to wipe everything and re-install (S2E, GApps, some test apps). Will do so later.

Attached are dmesg and logcat, taken after the unvoluntary reboot, via adb shell, as Terminal Emulator FC'ed as well.

Edit:

Factory reset, no s2e installed yet, no apps available for testing, this time TE starts. Camera allows to set "flash on" (there is none). Connecting to PC using MTP works (starts Rhythmbox on my Debian). UMS remains a mystery.

dmesg and logcat again taken via adb shell. BTW, WiFi is still greyed out...

Back to 1177 for now - is 1141 still available somewhere?
[Samsung Galaxy 551 Callisto] Ansh2000:
Tested it. all the apps got fc except trebuchet , after reboot fixed frequent fc without disabling zram. Wifi doesn't turn on and rare wakup delay found in this build.
[Samsung Galaxy 551 Callisto] ehsan-black:
Device:beni

build : #1151 (I Compiled Kernel from handymen sources)

I compiled kernel from HandyMen sources and tested it on #1151.

- USB transfer rate on UMS didn't fix

- wifi doesn't work...

- wake up delay partitialy solved. it depends on cpu governor . when I set smartassV2 as the governor screen wakes up after 3 secs and with Ondemand it wakes up after 7 secs.

I attached logcat and dmesg and also logcats and dmesges of wifi and wakeup issues.
[Samsung Galaxy 551 Callisto] Mm7:
callisto: New build #1201

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1201/

The following things should be tested: wakeup delay, mmc performance, kernel latency / audio stutter, zram, bluetooth, data connectivity indicators, vpn connectivity (l2tp), general stability and battery life

Thank you
[Samsung Galaxy 551 Callisto] Ansh2000:
Thanks for your hard work. I didn't see wakeup delay ( rarely 2 seconds normally less than 1 sec.) bluetooth , data connectivity indicators, vpn connectivity working well, wifi and Zram are stable too. I will edit post after few hours of testing.

Edit 1

audio shutter present in this build. Copy files to sd card is slow. Battery life is better than all previous build. stability is fine didn't get random reboot in 12 hours.
[Samsung Galaxy 551 Callisto] ehsan-black:
could you triger a new build with new changes in gerrit for beni? this one doesn't have 7660 7661 7664 7665 7666 7667 7668 7669 changes from gerrit:

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1202/

thanks in advance :)
[Samsung Galaxy 551 Callisto] Mm7:
Here:

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1203/
[Samsung Galaxy 551 Callisto] steve8x8:
Quick Q regarding keyboards, etc.: Would it be possible / make sense to have a /system/addon.d/* script for the keyboard install zip so the kbd settings get preserved during updates? (In the updater-script, backuptool is invoked which should be able to take care of this.) Would make us more OTA-ready...
[Samsung Galaxy 551 Callisto] aldweb:
Hello.

I've got issue while installing this update over my previous kernel 3 install, it says "symlink: some symlinks failed", then Status 7 and installation aborted.

Do we need to go for a fresh install?
[Samsung Galaxy 551 Callisto] aldweb:
Yes, that was required in my case.
[Samsung Galaxy 551 Callisto] steve8x8:
Like this? (see attachment, to be installed once before upgrading)
[Samsung Galaxy 551 Callisto] aldweb:
Overall, same feedback as Ansh2000 here. Wakeup delay which was a nightmare in previous build is really solved, great.

I could notice that after a long device's sleeping time, wifi does not reconnect automatically. I have to turn it off and on again to regain wifi connection.