[ROM] Olympus CyanogenMOD 9 (with Kernel 3.1.10)

[asparaz43]

Hi everyone,

Below you have kernel that can be considered as a daily driver (if it works for you). It is also the first of new kernel for undervolting test spreadsheet. I implemented temporary wakeup on call solution. Also it has implemented my alternative screen tearing solution. If you have screen tearing on it (default dsi settings are the same as v1 has) you can change those using echo command e.g.:

echo 4 > /sys/kernel/olympus/dsi/h_ref_to_sync
echo 1 > /sys/kernel/olympus/dsi/v_ref_to_sync
echo 16 > /sys/kernel/olympus/dsi/h_sync_width
echo 1 > /sys/kernel/olympus/dsi/v_sync_width
echo 32 > /sys/kernel/olympus/dsi/h_back_porch
echo 1 > /sys/kernel/olympus/dsi/v_back_porch
echo 32 > /sys/kernel/olympus/dsi/h_front_porch
echo 2 > /sys/kernel/olympus/dsi/v_front_porch

For it to take effect, you have to turn screen off/on. Values used in screen tearing tests you will find here:

panel settings

Kernel is here: new kernel

All the issues related to voltages (like hangs, wakeup issues, proviously not present random reboots, etc) should be reported here: undervolting tab of spreadsheet

One more thing... changes in panel settings are valid until next phone's reboot.

Thanks Krystianp this kernel is only for the CM 9 ?

 

[krystianp]

Thanks Krystianp this kernel is only for the CM 9 ?

yes

 

[Feche]

Latest kernel (if you have problems downloading)

 

[youcef82]

The big problems with me I want to Skype works with me for this ROM used it so much... I hope you can find solution Thank you in advance ^_^
Sent from my MB860 using xda app-developers app

 

[palmbeach05]

The big problems with me I want to Skype works with me for this ROM used it so much... I hope you can find solution Thank you in advance ^_^
Sent from my MB860 using xda app-developers app

hasn't this been discussed on several threads. Skype, Viber, etc, have issues with the kernel build. not the rom.

 

[kevinchg]

Hi everyone,

Below you have kernel that can be considered as a daily driver (if it works for you). It is also the first of new kernel for undervolting test spreadsheet. I implemented temporary wakeup on call solution. Also it has implemented my alternative screen tearing solution. If you have screen tearing on it (default dsi settings are the same as v1 has) you can change those using echo command e.g.:

echo 4 > /sys/kernel/olympus/dsi/h_ref_to_sync
echo 1 > /sys/kernel/olympus/dsi/v_ref_to_sync
echo 16 > /sys/kernel/olympus/dsi/h_sync_width
echo 1 > /sys/kernel/olympus/dsi/v_sync_width
echo 32 > /sys/kernel/olympus/dsi/h_back_porch
echo 1 > /sys/kernel/olympus/dsi/v_back_porch
echo 32 > /sys/kernel/olympus/dsi/h_front_porch
echo 2 > /sys/kernel/olympus/dsi/v_front_porch

For it to take effect, you have to turn screen off/on. Values used in screen tearing tests you will find here:

panel settings

Kernel is here: new kernel

All the issues related to voltages (like hangs, wakeup issues, proviously not present random reboots, etc) should be reported here: undervolting tab of spreadsheet

One more thing... changes in panel settings are valid until next phone's reboot.

Dear K.
I've a very strange problem not associated with screen tearing,
even more , i never encounter screen tearing issue no matter v9, v11 or latest uv kernel (your CM9 ROM)
but I found my wifi lost connection quite often every couple minutes, it last just 5 seconds then connected again,
every time i upload my CWM backup(1GB single data file) to server through ftp or local lan, it fail because lost connection,
do you have any idea ?
this not happen in Eprinter's latest cm10.1 ROM (with his kernel),.
thanks

 

[todobarato]

Hello,

I have the same issue, wifi disconnects short and connect again. This is with the last kernel UV.

Dear K.
I've a very strange problem not associated with screen tearing,
even more , i never encounter screen tearing issue no matter v9, v11 or latest uv kernel (your CM9 ROM)
but I found my wifi lost connection quite often every couple minutes, it last just 5 seconds then connected again,
every time i upload my CWM backup(1GB single data file) to server through ftp or local lan, it fail because lost connection,
do you have any idea ?
this not happen in Eprinter's latest cm10.1 ROM (with his kernel),.
thanks

 

[krystianp]

Dear K.
I've a very strange problem not associated with screen tearing,
even more , i never encounter screen tearing issue no matter v9, v11 or latest uv kernel (your CM9 ROM)
but I found my wifi lost connection quite often every couple minutes, it last just 5 seconds then connected again,
every time i upload my CWM backup(1GB single data file) to server through ftp or local lan, it fail because lost connection,
do you have any idea ?
this not happen in Eprinter's latest cm10.1 ROM (with his kernel),.
thanks

If you connect USB cable is this issue still present?

 

[kevinchg]

If you connect USB cable is this issue still present?

Dear K.
Do you mean connected to usb power charger ?
if so , yes . I connected when i was uploading file,
BTW, I've done again with clean system only installed uploading app,
and I noticed not only latest uv kernel , several kernels have this problem on my Atrix,
original kernel come with 1016ROM, v9. v11 and ov, all lost wifi connection,
but...the lost only lasts really limited time period,
usually only last about 1 second , even less, but enough to make uploading fail.
also, it all happen on uploading large 1GB data backup file,

 

[earthworm1102]

How come download link on CM9 doesn't download completely on dev link?It says 100% but actually it is not complete.
Is there any other link? Tried it on laptop, and phone and same result. Thanks!!

 

[lightlord]

Does anybody else have a case of phone not entering deep sleep with latest UV kernel ?

Sent from my MB860

 

[krystianp]

New cm9 build in the first post.

Changelog:

- storage places fixed
- dsi panel init settings loaded from the script (/system/etc/init.d/89olympusinit)
- back to original hwcomposer lib
- I've added ExtDispService.apk, it causes 3 message boxes to show up after boot (it's needed to fix hdmi ipc error). I'm working on adding missing motorola framework parts but until then you either have to delete it or just press 3 times OK.
- option to change focus mode in camera (only photos for now)
- temporary fix for proximity issue on calls
- stock voltages

 

[lightlord]

Thanks for new update, my first observation is that it swapped my memory, looks like external is primary and says I have no sdcard.
I do use dual boot however , but till now it was fine.

Sent from my MB860

 

[krystianp]

Thanks for new update, my first observation is that it swapped my memory, looks like external is primary and says I have no sdcard.
I do use dual boot however , but till now it was fine.

Sent from my MB860

Did you flash any other kernel over this rom? Do mount in terminal and check if you have vold (probably) 179:18 as sdcard0 and if you have external card, there should be something higher maybe 179:97 as sdcard1. Also check if you have selected use internal storage in storage settings.

 

[lightlord]

Did you flash any other kernel over this rom? Do mount in terminal and check if you have vold (probably) 179:18 as sdcard0 and if you have external card, there should be something higher maybe 179:97 as sdcard1. Also check if you have selected use internal storage in storage settings.

Thanks for Response. Checked and it is as you said :18 sdcard0 and :97 sdcard1. However I found it funy that you can have oposed settings for storage, under storage configuration vs under advanced settings. Do they apply to the same thing ? I now checked both to internal and now the internal is primary, but file manager still cries there I no sdcard.

Edit: no other kernel flashed

Sent from my MB860

 

[drZeT]

no more camera


"Can't connect to the camera" error now every time with a click sound form back camera.

 

[Feche]

Did you flash any other kernel over this rom? Do mount in terminal and check if you have vold (probably) 179:18 as sdcard0 and if you have external card, there should be something higher maybe 179:97 as sdcard1. Also check if you have selected use internal storage in storage settings.

I am having the exact same issue with 20/11 build, also I cannot see any images from gallery, I already reinstalled the ROM and I had no success..

Here is my mount:

[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,noatime,nodiratime,user_xattr,barrier=1,da
ta=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,b
arrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,
barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/loop0 /pds ext3 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:18 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $

I also have checked to use internal storage on settings, thanks.

 

[madmax59]

sd card not working for me

My mount

[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/loop0 /pds ext3 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:18 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $

MB860 cihazımdan Tapatalk kullanılarak gönderildi

 

[todobarato]

Hello,

I have exactly the same.

and additional: I get one complete freeze by wakeup, the other wear was by wakeup again the display was in negative, I try to make one screenshot but with the memory card issue was impossible to save it, error cannot save...

Krystianp, why you change the memory? It was working perfect before.

Best regards,

Did you flash any other kernel over this rom? Do mount in terminal and check if you have vold (probably) 179:18 as sdcard0 and if you have external card, there should be something higher maybe 179:97 as sdcard1. Also check if you have selected use internal storage in storage settings.

Sent from my MB860 using xda app-developers app

 

[Feche]

20/11 kernel for 16/10 ROM