[DISCUSSION] HTC One S C2 CM, AOSP and 3.4 kernel development

Search This thread

qzem

Senior Member
Jun 23, 2010
1,594
1,030
Only for HTC One S C2!!

This is a discussion thread, about the progress on 3.4 kernel development for cyanogen mod, and other aosp based roms. There is posibility that testers will be needed...
 

Spii

Senior Member
Oct 20, 2012
67
86
Logcat Error

There is one error in logcat, which appears all the time:

Code:
I/auditd  ( 7220): Starting up
E/auditd  ( 7220): Failed on audit_set_pid with error: Protocol not supported
I/auditd  ( 7220): Exiting

Possible this is causing any kind of problems?
 

ElectroPug

Senior Member
Nov 18, 2012
215
113
You already have me, I'll write you when I have some spare time, you can also involve Robin he's willing to help :D

Gesendet von meinem HTC One S mit Tapatalk
 

qzem

Senior Member
Jun 23, 2010
1,594
1,030
It looks like things are moving into the right direction. But I am leaving for London today so I won't be able to test until my return.

Good luck!

Sent from my HTC One S using XDA Free mobile app
 

Spii

Senior Member
Oct 20, 2012
67
86
It looks like things are moving into the right direction. But I am leaving for London today so I won't be able to test until my return.

Good luck!

Sent from my HTC One S using XDA Free mobile app

League of Legends Championship Series in Wembley stadium? :eek:
 

Sultanxda

Recognized Developer
Tried porting new framebuffer drivers from CAF. Attached to the bottom of this post are the kernels with the new framebuffer drivers (one for PAC and one for CM11). All I need to know is whether or not it boots. Graphical glitches do not matter.

Also, I don't plan on getting too involved in the development here as I don't own the device.
 

Attachments

  • Sultan-VilleC2-CAF-msmfb-PAC_6-21-2014.zip
    5.5 MB · Views: 22
  • Sultan-VilleC2-CAF-msmfb-CM11_6-21-2014.zip
    5.5 MB · Views: 46

Spii

Senior Member
Oct 20, 2012
67
86
Tried porting new framebuffer drivers from CAF. Attached to the bottom of this post are the kernels with the new framebuffer drivers (one for PAC and one for CM11). All I need to know is whether or not it boots. Graphical glitches do not matter.

Also, I don't plan on getting too involved in the development here as I don't own the device.

Hey, first of all thanks for doing this. Your work is highly appreciated! :good:

About the kernel: I've flashed the CM Kernel, first it was bootlooping but I somehow booted it successfully into Safe Mode

And Screenshot is working ;)

fy9lub4w1gi5.png


EDIT: At the 3rd loop it's booting successfully!
 
Last edited:

Sultanxda

Recognized Developer
Hey, first of all thanks for doing this. Your work is highly appreciated! :good:

About the kernel: I've flashed the CM Kernel, first it was bootlooping but I somehow booted it successfully into Safe Mode

And Screenshot is working ;)

fy9lub4w1gi5.png


EDIT: At the 3rd loop it's booting successfully!
I can't believe it actually booted on my first attempt without the device :eek: It probably bootlooped because you're on a very recent build of CM, and I used the ramdisk of a CM build made 3 months ago. New framebuffer drivers means that graphics are overall much smoother and display glitches are gone. They also allow you to use display-caf instead of display-legacy.

Sent from my Nexus 5 using Tapatalk
 

sunnyvijay

Member
Aug 13, 2013
29
12
Tried to install the CM11 file but failed.

Error is

assert failed: getprop("ro.product.device") == "villec2
E:Error executing updater binary in zip '/sdcard/downlo......
Error flashing zip........
 

sunnyvijay

Member
Aug 13, 2013
29
12
Thanks.

However could not wait and googled to fix the updater-script and was successful.

It was bootlooping but after 6th loop the phone was on and working :)

The Kernel Version in the About reflects 3.4.750Sultan-CAF-msmfb-g08a97af-dirty
 

qzem

Senior Member
Jun 23, 2010
1,594
1,030
I can't believe it actually booted on my first attempt without the device :eek: It probably bootlooped because you're on a very recent build of CM, and I used the ramdisk of a CM build made 3 months ago. New framebuffer drivers means that graphics are overall much smoother and display glitches are gone. They also allow you to use display-caf instead of display-legacy.

Sent from my Nexus 5 using Tapatalk

Is there any progress on kernel? Or you don't have time to work on it?

Sent from my HTC One S using XDA Free mobile app
 
  • Like
Reactions: ClarkOwen

Sultanxda

Recognized Developer
Is there any progress on kernel? Or you don't have time to work on it?

Sent from my HTC One S using XDA Free mobile app

All of the completed source is on my GitHub.

Kernel: https://github.com/sultanxda/android_kernel_htc_liberty-villec2
Device tree: https://github.com/sultanxda/android_device_htc_villec2
Vendor tree: https://github.com/sultanxda/proprietary_vendor_htc
Media-caf: https://github.com/sultanxda/android_hardware_qcom_media-caf
Display-caf: https://github.com/sultanxda/android_hardware_qcom_display-caf

Note that for display-caf and media-caf all you need are these patches:
For display-caf: https://github.com/sultanxda/androi...mmit/d8374d512958a02f05cac8261dc419efedde07c9
For media-caf: https://github.com/sultanxda/androi...mmit/67e47694cb00e70916b97e4308e1d8eef21f192f

Otherwise media-caf and display-caf are exactly the same as the CyanogenMod versions.

Now you guys have hardware vsync and the latest framebuffer drivers, along with the latest display and media HALs :)
 
Last edited:

Top Liked Posts