[ROM][3.4 Kernel][4.4.4] Unofficial SlimKat 9.1 (pyramid)

[ivanich]

That's correct. My latest version bypasses the need for that file. However, that file does serve a purpose and I was actually going to implement it when I found it already available. The purpose is that if you don't want volume rocker wake, having that tunable will keep the phone in sleep mode if the volume buttons are pressed. Without that file or with that file bypassed, if you have volume rocker wake disabled in display settings the phone comes out of sleep mode and just doesn't turn on the display.

So, with my next version you will need to enable the setting in 89kernel and in display settings for it to work.

This is probably an simpler way https://github.com/ivanich/android_...mmit/19b2f27d79c846ad42b6b9098b0a029899e20917

 

[wieman01]

Thank you. I have been a Linux user for many years, so this is really great help. At least I have now learned how to create init scripts in Android and where to make the changes relating to Wake.

 

[gc2712]

fstrim command not working

Have just installed this ROM after Revolution HD. Fstrim command worked in Revolution HD, but not in this ROM. Error mesage is:
"fstrim: FITRIM: Operation not supported on the transport endpoint".

Is there some way to enable this in this Unofficial SlimKat(Pyramid) on my Sensation?

Also, is there a way to control the max/min cpu speeds and governors? Are these both kernel related issues, and if so is there a stable kernel that supports these features that I can install?

 

[ThatsABigOne]

Have just installed this ROM after Revolution HD. Fstrim command worked in Revolution HD, but not in this ROM. Error mesage is:
"fstrim: FITRIM: Operation not supported on the transport endpoint".

Is there some way to enable this in this Unofficial SlimKat(Pyramid) on my Sensation?

Also, is there a way to control the max/min cpu speeds and governors? Are these both kernel related issues, and if so is there a stable kernel that supports these features that I can install?

Trim is already included in this rom and it works automatically.

 

[LordNerevar]

Also, is there a way to control the max/min cpu speeds and governors?

You can edit /etc/init.d/89kernel for this with a root explorer or use one of the apps in the play store if you like that better. Kernel Tuner is one of the often recommended apps.

P.S. An article about trim being built into Android since 4.3 is here.

 

[gc2712]

Trim is already included in this rom and it works automatically.

Thanks for the response. I did know that TRIM was included as of 4.3 as I have a Nexus 7 (2012) as well. But I found that if I also ran trim command in a terminal on the Nexus regularly a) it trimmed a lot and b) the device sped up noticably. This was the case for many months of use. I therefore concluded that I would continue to run fstrim manually despite the seeming illogicality if TRIM is already running in background. I also did this with the Sensation phone running Revelation HD with similar results. The error message I referred to above occurring with this Unofficial SlimKat Rom made me wonder if there was some issue with partitioning/file format that was interfering with the TRIM function (even as a background process) that was revealed by the failure to execute when invoked in a terminal. Thus maybe inbuilt TRIM works, maybe it doesn't?

[LordNerevar]
"Kernel Tuner is one of the often recommended apps"

I had tried several CPU control apps, but none of them would maintain the minimum frequency setting for CPU for some reason. Had never seen Kernel Tuner before. Downloaded and installed. Its a great app!:good:

Was able to display both cores and set max and min speeds without breaking anything (So far!). My main reason for wanting to control this is to manage what seemed like high battery drain and sure enough, the cpu was running 1500Mhz most of the time even though the phone is in standby most of its life. Overall, I am very happy with the ROM and will use it from now on. Thank you for your efforts and the link to article on TRIM

 

[LordNerevar]

Thanks for the response. I did know that TRIM was included as of 4.3 as I have a Nexus 7 (2012) as well. But I found that if I also ran trim command in a terminal on the Nexus regularly a) it trimmed a lot and b) the device sped up noticably. This was the case for many months of use. I therefore concluded that I would continue to run fstrim manually despite the seeming illogicality if TRIM is already running in background. I also did this with the Sensation phone running Revelation HD with similar results. The error message I referred to above occurring with this Unofficial SlimKat Rom made me wonder if there was some issue with partitioning/file format that was interfering with the TRIM function (even as a background process) that was revealed by the failure to execute when invoked in a terminal. Thus maybe inbuilt TRIM works, maybe it doesn't?

Thank you for this information. I'll see if there's anything that can be done to get fstrim working manually.

Update: I've found that the TRIM command has been disabled in the kernel (fs/ext4/ioctl.c line 405 if interested). This appears to be due to some bricking issues (google: CONFIG_ENABLE_FITRIM). We'll have to wait for it to be re-enabled upstream.

 

[gc2712]

Thank you for this information. I'll see if there's anything that can be done to get fstrim working manually.

Update: I've found that the TRIM command has been disabled in the kernel (fs/ext4/ioctl.c line 405 if interested). This appears to be due to some bricking issues (google: CONFIG_ENABLE_FITRIM). We'll have to wait for it to be re-enabled upstream.

Many thanks for the follow up. Much appreciated. I thought the problem may be something I was doing wrong. I look forward to the day fstrim works with F2FS too. Both are certainly a boon to older systems.

 

[wieman01]

For anyone who is interested in a generic solution (that works for all Slimkat versions) to the "Volume Rocker Wake" problem, here is what I was able to figure out thanks to LordNerevar & ivanich.

Before you proceed enable "Volume Rocker Wake" in the Display settings.

Use Root Browser or a similar tool to create this file:

/data/local/userinit.sh

Change permissions to Read (Owner, Group), Write (Owner), Execute (Owner, Group, Others). Now edit the file and add this line:

echo 1 > /sys/keyboard/vol_wakeup

Save & exit. Reboot your phone and your are done. The userinit script gets executed upon startup and ensures that vol_wakeup is set to 1 (it normally resets itself to 0 when you reboot the phone).

 

[LordNerevar]

The new 8.4 build is up. This build incorporates the HTC proprietary blobs from TheLoonyBin on github. They seem to be pretty darn good. The camera seems to be focusing better on stills and video now which is something I've always wanted from KitKat. Also, the ROM just seems smoother. Give it a spin and let me know what you think. Cheers!

 

[ivanich]

The new 8.4 build is up. This build incorporates the HTC proprietary blobs from TheLoonyBin on github. They seem to be pretty darn good. The camera seems to be focusing better on stills and video now which is something I've always wanted from KitKat. Also, the ROM just seems smoother. Give it a spin and let me know what you think. Cheers!

LOL, TheLoonyBin uses the same blobs, so it's a placebo.

 

[LordNerevar]

LOL, TheLoonyBin uses the same blobs, so it's a placebo.

Argh! Well, I diff'd the folders and you appear to be correct. Other than the libhtc_ril.so, the htc blobs are the same. There are diffs with a number of other .so files that aren't proprietary though. Now I'm really curious as to what fixed my camera focusing. It's never focused this well on a KK ROM.
EDIT: P.S. What type of tethering did your radish addition fix? Wifi tethering with WPA2 PSK seems to work fine w/o the radish blob. Google mentions ipv6. Is that the only reason it's needed?

 

[ivanich]

Argh! Well, I diff'd the folders and you appear to be correct. Other than the libhtc_ril.so, the htc blobs are the same. There are diffs with a number of other .so files that aren't proprietary though. Now I'm really curious as to what fixed my camera focusing. It's never focused this well on a KK ROM.
EDIT: P.S. What type of tethering did your radish addition fix? Wifi tethering with WPA2 PSK seems to work fine w/o the radish blob. Google mentions ipv6. Is that the only reason it's needed?

I can't actually remember for which type of tethering it required, perhaps for bt, but previously it complains about missing radish binary in logcat. Anyway, I've tried all type of tethering except mobile internet as input. wifi, usb, bt tether between all interfaces works fine.

Edit: Maybe it's just some upstream changes improves camera focus for you?

 

[wieman01]

I can't actually remember for which type of tethering it required, perhaps for bt, but previously it complains about missing radish binary in logcat. Anyway, I've tried all type of tethering except mobile internet as input. wifi, usb, bt tether between all interfaces works fine.

Edit: Maybe it's just some upstream changes improves camera focus for you?

And there was a massive amount of upstream changes when I looked at the log files the other day, including this one:

"CameraWrapper: increase size of scene-mode buffer"

 

[ivanich]

And there was a massive amount of upstream changes when I looked at the log files the other day, including this one:

"CameraWrapper: increase size of scene-mode buffer"

Where did you find this? Doubt this was for our device

 

[wieman01]

Not sure if this relates to our device, but you can check the log files on Slimkat's website.

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1256-pyramid

Simply open the latest change log.

 

[ivanich]

Not sure if this relates to our device, but you can check the log files on Slimkat's website.

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1256-pyramid

Simply open the latest change log.

CameraWrapper: increase size of scene-mode buffer [Chirayu Desai]2014-10-05 | rhine: Use Sony camera workaround hack (HEAD, m/kk4.4-caf, github/kk4.4) [Chirayu Desai]

This is for sony devices

 

[wieman01]

Are you sure? Because the line that mentions Sony is missing a line break. I think these are two separate lines outlining two separate issues.

Anyway, who knows... doesn't matter.

 

[ivanich]

Are you sure? Because the line that mentions Sony is missing a line break. I think these are two separate lines outlining two separate issues.

Anyway, who knows... doesn't matter.

Yes, I am sure, there are no changes were made to pyramid device tree github repos.

 

[gc2712]

8.4 CPU/Governor settings

You can edit /etc/init.d/89kernel for this with a root explorer or use one of the apps in the play store if you like that better. Kernel Tuner is one of the often recommended apps.

I updated to 8.4 without reset/wipe. No problems so far. But using Kernel Tuner I have been unable to get minimum CPU frequency to stick. (same in 8.2). I can configure each core separately using the app, but have set them to be the same. However after a short time the minimum CPU setting reverts to a much higher state. eg 384MHz rises to 1128Mhz (roughly). I change it again and within a minute it has reverted. Is there some way of making the settings stick?

Also, does anyone know what the best governor setting is for a smooth response and good battery life. I use the Sensation for a little web surfing and mostly just as a phone.