Thank you very much for your help!
Should I install latest version of Xceed for 4.4.3 even if I am on IC 3.0.7 (4.4.2) ?
Is IC 3.0.8 "more compatible" with Xceed kernel than IC 3.0.7 or is it the same?
Cheer,
Marco
Same. Np I like to help
After running the rom for several months now, I find it quite unstable.. Settings which I've posted a couple of pages back turned out to be unstable.. The kernel also seems to freak out above 50mv of undervoltage.
Wifi preforms horrible, as soon as I toggle it on, my phone locks up from time to time.. RAM management I think? I dunno. I'm going to try CM soon... Support for this ROM seems to be dropped
If you're on 4.4.2 (3.07) do NOT flash a 4.4.3 kernel. only flash a kernel if the ROM and kernel android version do not match. In this case there is one exception, namely : the 443 kernel is also for Android 444 ROM's. (IC 4.06 is android 444)
cheers.
-- edit -- 25-08-15
Since I've posted as last I'll edit this post. I thought I'd make a small read out on my current performance settings since I'm really happy with it!
My phone lasts for about 2 full days now, I still get more battery drain with WiFi on than with 3G on, which to me, is really strange. I can't find the reason why this is, maybe it's because of the governor. I use interactive. When I use MSM-DCVS this issue occurs
less, I do get more battery drain and less performance than this interactive governor so, I rather stay with interactive.
My device has got a really good sleep, I've found that the Gapps process is the most consuming and wake-lock-spitting process there is. Therefore I've done some extra's in order to make sure that my device can sleep well.
I use the app called: "Amplify" for often occurring wakelocks. Here are the settings of this app:
Wakelocks (tempered)
- NlpWakeLock
- GCoreFlp
- LocationManagerService
- NlpCollectorWakeLock
- RILJ
Alarms (tempered)
- ALARM_WAKEUP_LOCATOR
- ALARM_WAKEUP_ACTIVITY_DETECTION
- com.google.android.gms/.lockbox.lockboxAlarmReceiver
Services (tempered)
- .com.htc.flexnet/FlexNetService
- com.google.android.gms/com.google.android.location.internal.PendingIntentCallbackService
- .com.android.gms/.wearable.service.WearableControlService
- .com.htc.widget.notification/.util.ProductivityService
I have found that these apps or whatever they are, were quite consuming my battery. With Amplify we control the amount of wakelocks and whatever an app can do per given time, however, I've also shut down some services for certain apps completely in the app that comes with this ROM called: "AppOps".
If we go to the AppOps 'phone' section we can set a number of permissions, the following permissions worked out for me well. Please take in mind that I only post the settings which I've changed here, everything else was and is as default.
Google Play Store
Skype
Google Play Music
Google Play Services
- Location: Deny
- Read SMS: Deny
- Stay awake: Deny
- (I've got a feeling that due to the fact that I sort of disable Google Play Services a bit I get this horrible WiFi performance the first 2 mins screen-on)
Facebook for HTC Sense
Facebook
- Location: Deny
- Stay awake: Deny
- Draw on top: Deny
This was the list for my AppOps. Now we move on to 2 apps for the CPU control. I use:
- Synapse and
- Trickster Mod
I only use Trickster Mod to set a maximum frequency. Synapse does not support this. So if you're going to adjust timings etc.. as I will explain in a couple of lines, you can do it either in Synapse or in Trickster Mod, it does not matter. We need Synapse for the undervolt and krait voltage boost disabler.. we'll get to it;
Synapse
Set Maximum Core frequency (inherited from Trickster Mod)
Set Minimum Core frequency
CPU Governors
Governor Tunables
- min_sample_time 15000 (the amount of time we stay at a frequency before scaling down)
- boost 0 (no idea why this is here and what it does, just leave it 0)
- hispeed_freq 810000 (the frequency to jump to when cpu load is at "go_hispeed_load" in %)
- timer_rate 15000 (timer.. does what it says)
- above_hispeed_delay 90000 (the amount of time we stay at a frequency before scaling up)
- go_hispeed_load 99 (the load % on the CPU before going to hispeed_freq, I've noticed that the cpu really often goes to 99 - 100% easily so therefore I use 99)
CPU Voltage Control
Set lower frequencies undervolt
- 10 mV (I've experimented a lot with this, I found that at 20 mV, the demanding apps started to freak out and lock my phone)
Set higher frequencies undervolt
Krait Voltage Boost
----------------------------------------
I/O Scheduler!
------------------------------------------
Internal Storage
Internal storage read-ahead
---------------------------------------
Advanced tab
---------------------------------------
Vibration Intensity Control
- 1600 mV (I found that this is more than enough for me to sense it even in horrible circumstances, if you wanna have a personal vibrator, I won't stop you. Remember, you probably get messages a lot, so every millivolt less is a % battery more!)
The rest which I didnt mention is just as default in Synapse.
Trickster Mod
-----------------------------------
General tab
-----------------------------------
CPU Frequency Control
- Frequency lock [ ON ]
- Frequency profile: untitled
- Min: 384
- Max: 1512
---------------------------------
Specific tab
---------------------------------
- MP-Decision [ ON ] (some have debated whether this is a good thing or not, I think it is. You may experiment with this. What it does is, it shuts down a core much like MSM-DCVS does by default, if there is no load.)
Now, that was all for the Trickster mod. I have one more thing to say that I use in the developer settings.
I like a fluid flow when I navigate through the UI so, I use these settings in the developer options to be less dependable of the CPU (which is always busy with god knows what)
- Developers options > advanced > Disable HW overlays [ Checked ]
- Developers options > advanced > Force GPU 2D rendering [ Checked ]
- Now, if you have many issues with homescreen redraws, you can also check "Force 4x MSAA" and see if that helps.
It has been quite a write-out, must have been quite a read-out for you guys. A couple of posts back I've also posted some of my settings with the interactive governor but those have not proven to be stable, these are (lucky me).
Maybe you can do something with it, maybe not. It's up to you!
Cheers