yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy 551 Callisto] psyke83:
I merged your keypad/keychars to the CM10.2 and CM11 branches - thanks.

I'm afraid that I didn't understand the problem clearly. Since you appear to know how to modify files, here's what I suggest: create an input device calibration file for the keyboard (sec_keypad). From looking at a recent log, I can see that the sec_keypad device is not configured as a built-in keyboard:

I/EventHub( 466): New device: id=3, fd=90, path='/dev/input/event3', name='sec_keypad', classes=0xa3, configuration='/system/usr/idc/sec_keypad.idc', keyLayout='/system/usr/keylayout/sec_keypad.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

However, that log is from an old build that didn't have fixed keys, so you should check if your log says "builtinKeyboard=true" in the latest build.

Look here: http://source.android.com/devices/tech/input/keyboard-devices.html

This is the example configuration:

# This is an example input device configuration file for a built-in
# keyboard that has a DPad.

# The keyboard is internal because it is part of the device.
device.internal = 1

# The keyboard is the default built-in keyboard so it should be assigned
# an id of 0.
keyboard.builtIn = 1

# The keyboard includes a DPad which is mounted on the device. As the device
# is rotated the orientation of the DPad rotates along with it, so the DPad must
# be aware of the display orientation. This ensures that pressing 'up' on the
# DPad always means 'up' from the perspective of the user, even when the entire
# device has been rotated.
keyboard.orientationAware = 1

Try the example configuration first without any changes, and if it doesn't work, try different settings to see if it solves the problem. The file should be placed in /system/usr/idc/sec_keypad.idc and requires a reboot to take effect.

I would also appreciate if you could show me a log taken from the most recent build that includes the fixed keypad.
[Samsung Galaxy 551 Callisto] darblack:
Creating sec_keypad.idc and placing keyboard.builtIn = 1 option achievement that the chain says "builtinKeyboard = true" but does not solve the problem.

Upon logcat I find this

I/SystemServer( 472): Input Method Service

W/EventHub( 472): Unable to disable kernel key repeat for /dev/input/event3: Function not implemented

I/EventHub( 472): New device: id=3, fd=89, path='/dev/input/event3', name='sec_keypad', classes=0xa3, configuration='/system/usr/idc/sec_keypad.idc', keyLayout='/system/usr/keylayout/sec_keypad.kl', keyCharacterMap='/system/usr/keychars/sec_keypad.kcm', builtinKeyboard=true, usingSuspendBlockIoctl=false, usingClockIoctl=false

D/AwesomePlayer( 139): printFileName fd(20) -> /system/media/audio/ui/Unlock.ogg

I/EventHub( 472): New device: id=4, fd=95, path='/dev/input/event2', name='sec_touchscreen', classes=0x14, configuration='/system/usr/idc/sec_touchscreen.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

D/EventHub( 472): No input device configuration file found for device 'sec_jack'.

W/EventHub( 472): Unable to disable kernel key repeat for /dev/input/event0: Function not implemented

I/EventHub( 472): New device: id=5, fd=96, path='/dev/input/event0', name='sec_jack', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/sec_jack.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

D/EventHub( 472): No input device configuration file found for device 'msm_touchscreen'.

I/EventHub( 472): New device: id=6, fd=93, path='/dev/input/event1', name='msm_touchscreen', classes=0x4, configuration='', keyLayout='', keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

W/InputMethodManagerService( 472): Couldn't create dir.: /data/system/inputmethod

Sorry for not explaining well, I'm not good with English.

To use the virtual keyboard I go to options and disable the physical keyboard this must be done each time the device is restarted.

Used included file.
[Samsung Galaxy 551 Callisto] psyke83:
OK, I understand. You want the virtual keyboard to pop up each time, correct? In that case, you should actually set keyboard.builtIn = 0. I actually set this to zero in an older build that had incorrect mappings (which is probably the build where I took the logcat): http://review.androidarmv6.org/#/c/6355/2/prebuilt/usr/idc/sec_keypad.idc,cm

The newest build has no .idc file, so I think that it would set keyboard.builtin to true by default. Your latest logcat seems to be taken after you created the idc file, but the configuration will be the same as with no file present. Therefore try setting keyboard.builtIn to 0. If that doesn't work, set device.internal to 0 instead.
[Samsung Galaxy 551 Callisto] darblack:
Place keyboard.builtIn to 0 and nothing.

Place keyboard.builtIn to 0 with device.internal to 0 and nothing.

Place keyboard.builtIn to 1 device.internal to 1 with nothing.

Place keyboard.builtIn to 0 with device.internal to 1 and nothing.

Place keyboard.builtIn to 1 device.internal to 0 with nothing.

Made all possible combinations and does not operate.

logcat:

I/SystemServer( 472): Input Method Service

D/EventHub( 472): No input device configuration file found for device 'accelerometer_sensor'.

D/EventHub( 472): No input device configuration file found for device 'magnetic_sensor'.

W/EventHub( 472): Unable to disable kernel key repeat for /dev/input/event3: Function not implemented

I/EventHub( 472): New device: id=3, fd=92, path='/dev/input/event3', name='sec_keypad', classes=0x800000a3, configuration='/system/usr/idc/sec_keypad.idc', keyLayout='/system/usr/keylayout/sec_keypad.kl', keyCharacterMap='/system/usr/keychars/sec_keypad.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

I/OMXNodeInstance( 139): OMX_FreeBuffer for buffer header 0x21ec8 successful

I/EventHub( 472): New device: id=4, fd=93, path='/dev/input/event2', name='sec_touchscreen', classes=0x14, configuration='/system/usr/idc/sec_touchscreen.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

D/EventHub( 472): No input device configuration file found for device 'sec_jack'.

W/EventHub( 472): Unable to disable kernel key repeat for /dev/input/event0: Function not implemented

I/EventHub( 472): New device: id=5, fd=94, path='/dev/input/event0', name='sec_jack', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/sec_jack.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false

D/EventHub( 472): No input device configuration file found for device 'msm_touchscreen'.

I/EventHub( 472): New device: id=6, fd=95, path='/dev/input/event1', name='msm_touchscreen', classes=0x4, configuration='', keyLayout='', keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
[Samsung Galaxy 551 Callisto] rishabhsingh:
cm 11

cm 11 is awesome .thanks.

can't add google account.what to do ?
[Samsung Galaxy 551 Callisto] sauja:
I used this one.

http://xdaforums.com/showthread.php?t=2240652

was able to sync contacts, app install works though the download bar was not showing in the notification drawer

I removed the SetupWizard apk from the zip (was force closing and was not able to proceed)

Tested with CM 10.2

Also, any new build of CM 10.2? jenkins did not had any callisto build for Jan 18
[Samsung Galaxy 551 Callisto] darblack:
There will be more compilaciondes to keep trying?
[Samsung Galaxy 551 Callisto] Ansh2000:
Hi Psyke83

after 13th Jan did not see any cm11 experimental build on Jenkins.
[Samsung Galaxy 551 Callisto] sauja:
[MENTION=3950887]piterdemon[/MENTION]; which gapps did you use?

flashing gapps did not workk with cm11

I deleted some files in system(unwanted apps, some media files) then

had to manually copy the core gapps files, set the permissions, and install PrebuiltGmsCore.apk and Phonsky.apk to get them running

Contacts sync was fine after that.
[Samsung Galaxy 551 Callisto] psyke83:
Build #786 (cm11) has been queued for callisto. This release should hopefully fix the camera. Please test and leave feedback, especially related to the camera.

P.S. A friendly reminder. I don't own a callisto, which means that I completely rely on user feedback to fix bugs. If the camera is not working, then I need a logcat captured after attempting to open the camera app. Please spend the 5 minutes and do this if you want to see the ROM improve. Thanks.
[Samsung Galaxy 551 Callisto] stevenanggelo:
ok downloading now :)

how about cm10.2 development?

do you gonna drop cm10.2 development? :)

Edit :

the camera and keyboard works

thx psyke :D

but the camera quality really bad

and some options like white balance,exsposure,color effect didn't work

here some screenshots from the latest kitkat build
[Samsung Galaxy 551 Callisto] piterdemon:
How about battery on this release ? On previous battery drain fast

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] psyke83:
See above. I always need logs, really.

Does video recording/panorama also work? If not, capture a log taken after the recording failure.
[Samsung Galaxy 551 Callisto] stevenanggelo:
didn't know about that

i'm gonna test it today

sorry

i'm forget about it

video recording work

panorama also work

here is the logcat for the camera options
[Samsung Galaxy 551 Callisto] rishabhsingh:
??

is playstore and wifi working ?in first build playstore was not working...
[Samsung Galaxy 551 Callisto] Atermors:
Playstore and WiFi work fine in both releases. It is necessary to make some room on /system, though. Overall very stable, works best with dalvik-cache on sd-ext and swap partition for me.

Did not find anything not working with the newest build, although I killed my SD card playing around with sd-ext :D
[Samsung Galaxy 551 Callisto] sauja:
Could you please mention which files did you delete from /system?

Also the link for gapps which you flashed plz
[Samsung Galaxy 551 Callisto] stevenanggelo:
sorry for late reply

here it is

when the wifi is connected (you can see in the scrrenshot) i'm downloading some games

like cut the rope, icon pop song, etc

when the wifi turn off i'm going out listening some music about 30 minutes, playing games about 20 minutes

and here is the result

it's working

remove some apps that you don't use at system/app

and follow this instruction Link
[Samsung Galaxy 551 Callisto] rishabhsingh:
???

is usb and wifi tethering working??
[Samsung Galaxy 551 Callisto] stevenanggelo:
it's working :o
[Samsung Galaxy 551 Callisto] darblack:
Everything works fine. The camera works and allows video. Wifi is stable. proximity sensor works fine. is fluid but sometimes occurs closures applications.

In some programs is unstable. you must disable the physical keyboard option if you want to use the virtual keyboard.

Keep equipment so they are doing a fantastic job.
[Samsung Galaxy 551 Callisto] psyke83:
Please test the recovery.img from android-experimental #832 and let me know if it works correctly. This build includes some changes to the recovery graphics intended to fix blue screen problems on Gio and Ace, but I need to be sure that it doesn't break any of the other Samsung devices.

Download recovery.img to sdcard, then:

adb shell
flash_image recoveryonly /sdcard/recovery.img

Thanks in advance!
[Samsung Galaxy 551 Callisto] Ansh2000:
Thanks recovery is working well.
[Samsung Galaxy 551 Callisto] piterdemon:
For me showing error "2"

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] psyke83:
You probably tried flashing without superuser privileges. From ADB, you can run "adb root" to get permanent root. Otherwise you can run "su" (from non-rooted ADB shell or from terminal app).
[Samsung Galaxy 551 Callisto] piterdemon:
I try with adb root and adb say its allready rooted . newest version is 6.0.4.7 ? If yes then I succes

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy 551 Callisto] vvaklnprm:
NIGHTLY build

[MENTION=3877378]psyke83[/MENTION]

I saw a new NIGHTLY build on Jenkins 1/2/14 of CM-11.0

Any news of what is changed?
[Samsung Galaxy 551 Callisto] psyke83:
The stable builds from Jenkins should now be suitable for use on Callisto without having to wait for me to advise you. However, there are still a few patches still up for review on gerrit that will not be present in these builds. One such patch greatly improves general responsiveness and multitasking.

I've queued build #858 which includes these patches for your convenience. Apart from the improved multitasking, the main difference with this build is fixed RenderScript. This means that the Gallery editor and live wallpapers now work correctly.

P.S. If you don't like CM11 and prefer CM10.2, I have been keeping the older branch updated with the important fixes. RenderScript is also fixed on this branch, so you can grab a CM10.2 build from Jenkins if you want.
[Samsung Galaxy 551 Callisto] darblack:
Where you can download CM10.2 with those last major corrections?

In this version the camera and proximity sensor are working?
[Samsung Galaxy 551 Callisto] darblack:
The user Ankur850 used a q fix corrects the problem Physical keyboard. It might include the fix to solve the problem.

Project:

http://xdaforums.com/showthread.php?t=2438393
[Samsung Galaxy 551 Callisto] vvaklnprm:
Patches

[MENTION=3877378]psyke83[/MENTION]

The patches you mentioned you had included in that build, will they be included automatically in the future jenkins builds or only you can manually include those patches in the builds you trigger?
[Samsung Galaxy 551 Callisto] darblack:
You could compile CM10.2 with improvements included. I would greatly appreciate it.
[Samsung Galaxy 551 Callisto] psyke83:
Just catching up with the thread now. I've submitted [MENTION=4839120]ankur850[/MENTION]'s physical keyboard change to gerrit (on both branches). Providing that the change is working correctly, these builds should be suitable for use:

CM10.2: http://jenkins.androidarmv6.org/job/submission-test/1579/

CM11.0: http://jenkins.androidarmv6.org/job/submission-test/1580/

If I'm reading the patch correctly, there are two separate changes being implemented. The first change will make the physical keyboard accessible when the "lid" is open. The second change will rotate the display to -90 (90 degrees counter-clockwise). Are both of these changes needed, or just the first? It's hard for me to know without owning the device. Please report back - thanks.
[Samsung Galaxy 551 Callisto] ankur850:
these changes working, as tested already by testers. :)
[Samsung Galaxy 551 Callisto] darblack:
I thank you for the fantastic work you do.

Works well the physical keyboard, and not have to disable it to use the virtual keyboard. :D :good:

The first change works correctly.

The second change does not work.

Furthermore the proximity sensor work correctly. :laugh:
[Samsung Galaxy 551 Callisto] vvaklnprm:
Thank you so much for including the patches in cm 11 and 10.2

Hoping for a smooth, stable cm 11 build in the near future :D
[Samsung Galaxy 551 Callisto] Ansh2000:
Thanks Psyke83 you gave new life to Callisto.
[Samsung Galaxy 551 Callisto] stevenanggelo:
did anyone tried to install v6 supercharge at cm11 and cm10.2?

i can't pass the boot splash screen
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] please make queue of omni rom for Callisto.

Thanks in advance
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] today i flashed jenkins build swipe enable recovery image but it doesn't boot in system always go back in recovery any solution please.

edit after second try it is working perfectly.
[Samsung Galaxy 551 Callisto] psyke83:
The recovery images that are created alongside ROMs are not recommended, as the kernel for recovery needs a different kernel configuration from the regular kernel used by Android. The build system currently doesn't allow building a separate recovery kernel, so it's better to stick to recovery images that are built using the correct kernel. I'll try to find a link to a good recovery image that doesn't have this bug and upload it somewhere.
[Samsung Galaxy 551 Callisto] psyke83:
Hey everybody,

We've now enabled OTA updates in the androidarmv6 builds for Callisto. I've updated post #1 with the instruction on how to install an OTA build (as well as a quick explanation on how to perform OTA updates). Now that the OTA builds are available and working, please refrain from installing android-experimental builds (unless I specifically ask for a certain build to be tested in this thread).

Thanks and enjoy!

P.S. CM10.2 will not be getting OTA updates - it makes no sense, as the upstream code base has been frozen.
[Samsung Galaxy 551 Callisto] marniel647:
Thanks Psyke will try the build with OTA enabled. Just a question some build i test in jenkins does not have a transparent status bar in the upper screen. Any workaround on this. Thanks
[Samsung Galaxy 551 Callisto] Ansh2000:
enable developer option by touching seven times on build no and go to performance setting and tick on force high - end graphic such as transparent status / navigation bar and reboot.
[Samsung Galaxy 551 Callisto] marniel647:
Thanks Ansh. But my boot animation still not looks good like the previous build.

[MENTION=3877378]psyke83[/MENTION] i already flashed the 3-20 build with OTA update but the quick panel does not work i click the button beside the clock in quick setting but no effect it does not go to the quick panel. Also cannot switch the runtime to ART. But overall the rom is smooth
[Samsung Galaxy 551 Callisto] Ansh2000:
Philz Recovery

Philz Recovery 6.221 /CWM 6.0.4.7 Advance edition available for callisto.

http://xdaforums.com/showthread.php?p=51277506
[Samsung Galaxy 551 Callisto] marniel647:
OTA update is working. my only problem is the boot animation. :)
[Samsung Galaxy 551 Callisto] psyke83:
The ROM uses a half-resolution bootanimation in order to economize space on the /system partition (needed for gapps). If you can't tolerate the quality, then:

1. Download the 240.zip bootanimation from here: https://github.com/androidarmv6/android_vendor_cm/tree/cm-11.0/prebuilt/common/bootanimation

2. Rename 240.zip to bootanimation.zip

3. Copy bootanimation.zip either to /system/media or /data/local/.

If you transfer to /system/media, this customization will be lost after performing a ROM upgrade. If you transfer to /data/local/, the customization will survive ROM upgrades, but will be lost when you perform a data-wipe.
[Samsung Galaxy 551 Callisto] marniel647:
Thanks Pskye83 Already change my boot animation. :) now the rom is good and fast but cannot switch to ART. :)
[Samsung Galaxy 551 Callisto] Ansh2000:
Art will not work on our device due to low memory art takes lot of space and more memory so it is not possible for our device.
[Samsung Galaxy 551 Callisto] marniel647:
Thanks for the clarification Ansh. :)
[Samsung Galaxy 551 Callisto] psyke83:
I would appreciate if someone could test and leave feedback on this build to see if it fixes the keyboard orientation: http://jenkins.androidarmv6.org/job/submission-test/1635/

I checked the code, and the value that ankur850 set for config_lidOpenRotation (-90) is not an accepted input. The testing build will set the orientation to 270 degrees.

Edit: the orientation may need to be either 90 or 270 degrees. I can't test this personally, so please let me know if 270 degrees is correct or not. If not, we can try 90 degrees.
[Samsung Galaxy 551 Callisto] Ansh2000:
270 degrees orientation is not working need to test with 90 degrees.
[Samsung Galaxy 551 Callisto] psyke83:
What do you mean by not working? No difference to before, or the screen is the wrong orientation (upside down)?
[Samsung Galaxy 551 Callisto] Ansh2000:
[MENTION=3877378]psyke83[/MENTION] I mean to say no difference to before, I couldn't understand where is keyboard orientation problem . I request other user to confirm . I have never faced such problem after change of keyboard layout and fix virtual keyboard pop up without disable of physical keyboard by you.
[Samsung Galaxy 551 Callisto] ame316:
Good job psyke, the rom works perfect. I have only a question, which gapps should i use? There isn't enought space to install them.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Samsung Galaxy 551 Callisto] psyke83:
I don't have a gapps package that I know will work on callisto, but I can tell you that you will need a very slimmed down version. For galaxy5, we need to install gapps to sd-ext as we have virtually no free space on system (2mb).

Try Bhargav97's package here (intended for galaxy5), but I can't guarantee if it will work: http://xdaforums.com/showthread.php?t=2623802
[Samsung Galaxy 551 Callisto] psyke83:
Delta updates are now activated for all androidarmv6 devices. I've updated the instructions on the cm-ota page, please read it.

The first delta update that will be available for callisto will update the 25th build to 26th. If you want to test, make sure that you're already running the 20140325 build, and then wait a couple of hours for today's callisto cm-ota build to complete. When today's build becomes available, perform an OTA update on your phone using the regular procedure (written in the link above). If you're definitely updating from the 25th build (and no other), the updater will use the delta update package, which will be around 3MB.

Keep something in mind about delta updates: if you've modded any system files on the /system partition, then the update will most likely refuse to install, as delta patching requires 100% unmodified files in order for the patch process to work correctly. Modders will need to manually install the full OTA builds.

Enjoy, and please let me know if you find any problems with the delta updates.
[Samsung Galaxy 551 Callisto] ame316:
I've installed this gapps with the ext-patch and no problem so far.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Samsung Galaxy 551 Callisto] AshuGite:
Rom is smooth but i am getting some random freezes...
[Samsung Galaxy 551 Callisto] darblack:
such that the system behaves in calls? out come the information of the call?
[Samsung Galaxy 551 Callisto] AshuGite:
when receiving a call the system freezes some times..this needs to be fixed...
[Samsung Galaxy 551 Callisto] darblack:
Well several things:

* I tried it and it does not work. By deploying the keyboard does not rotate the screen anywhere to stay upright all the time.

* Calls and answer are a little later would be good to revise that.

That's all for now. waiting for performance improvements. thanks
[Samsung Galaxy 551 Callisto] darblack:
Friends could add the Spanish dictionary to default keyboard.
[Samsung Galaxy 551 Callisto] darblack:
Here in the reporting of calls the delete button is well visualisa number.

I add some pictures. First picture (01) is not delete button. Second picture (02) is displayed as it should see the button.

Use build (RC4)
[Samsung Galaxy 551 Callisto] marniel647:
Cannot update the latest build (RC4) thru OTA.
[Samsung Galaxy 551 Callisto] Ansh2000:
download full file and flash it is not incremental ota.
[Samsung Galaxy 551 Callisto] darblack:
I've placed the button to delete the number in Dialer. Dialer.zip patch with recovery.

The plain, unformatted ic_dial_action_delete.rar contains the correct image for the delete button number.

Use build (RC4)
[Samsung Galaxy 551 Callisto] berturion:
azerty keyboard and FM Radio

Hello, thank you very much for maintaining a very recent Android build on this old device ! It's not an easy task :D I want to try this ROM but it would be for my girlfriend and I need to know 2 things before I install the ROM :

- is there an azerty keyboard layout available for the physical keyboard. If not, how can I do it myself (modify Generic.kl) ?

- does built-in FM Radio work ?

Hav a nice day :good: