After doing the same as you (installing exceed kernel on 3.0.7), now suddenly no touch is being registered anymore, can't unlock, can't reboot nothing, screen just goes off again like nothing has been touched..
[ROM]InsertCoin 5.0.8 | 3.28.401.9•ART | 4.4.4 | Kontrol Tweaks•Market•IconPacks
- Thread starter xXminiWHOOPERxX
- Start date
-
- Tags
- development
Disable D2W, I also had this issue. D2W is the problem.
I'm running InsertCoin 4.0.6 (android 4.4.4) with the latest Xceed kernel for 4.4.3
I know most are on 3.0.7 but this version runs fine for me. I have some BT issues every now and then with my Moto 360 (not connecting etc..) but that's acceptable I think. I'd rather stay on 4.4.4
I'm experimenting with battery life, governors and I/O schedulers. I'm trying to max out the battery / performance rate.
I am willing to sacrifice some performance in the form of stuttering / lag / loading times for a better battery life.
My aim is to use my phone for a full 2 days (starting 07:00 the first day, ending at 23:00 the last day) and not changing my habits too much. The main issue I had was the screen-on time. As described in this post by user @pure.by you can gain some performance with the MSM-DCVS CPU governor.
Please figure out your own device's sleep yourself, I do not care about screen-off time, I already have this covered by reducing wake locks etc and removing apps I don't need. I use Amplify (go get that) for wake control. I assume that you can optimise your device's sleep yourself. This is all about screen-on time on the M4.
(Please read pure.by his post, it's very usefull as it also was my starting point)
However, I still had a lot of battery drain during the screen-on time. I was wondering how this came to be? I figured that it had to be something to do with the clock rates of the CPU and voltages. I've read about underclocking and undervolting before but as a new guy on this block I was a bit scared to play with those values at first. (I do now)
I figured that, after monitoring a lot, the MSM-DCVS governor scales the CPU clocking rates (and voltages) a LOT up and down. It gave me the feeling that it was either all or nothing (in terms of MHz). Apps like CoolTool and BetterBatteryStats told me that my CPU was either in 384 MHz or 1728 MHz.. nothing in between really. I also noticed that the MSM-DCVS governor had a sample time (the amount of time that a CPU stays in a certain speed before going back down) that was longer than expected.
I figured that there has to be an other way to just 'apply a governor and hope for the best' by tweaking certain parameters to my needs. Notice that this is MY setup for MY needs based upon MY experiences. This does not mean that it can be useful for you as well.
Apps I've used to get the results I wanted (before reading any further):
- Synapse (for disabling krait voltage boost, checking the C2 sleep state to true)
- Trickster Mod (for setting the maximum frequency, does not work in Synapse and also for playing around with MinFree)
I've been reading and searching a lot in these forums to get the best battery life with a governor, I found the most interesting to be the "Interactive" governor, not only due to it's great capabilities, but also for it's tweakabilities.
After reading this post, starting from there I learned the logic from this post that included changing the parameters to my needs.
After tweaking and experimenting for weeks and weeks I've come to these settings in both Synapse and Trickster Mod (I have both installed)
- Synapse:
Max core frequency: 1404 MHz (you really do not need any more)
Min core frequency: 384 MHz(if you have a custom kernel, the frosted kernel for example, you can also set it to 192 MHz)
Governor: Interactive
Min_sample_time: 30000 (the amount of time before we upscale in MHz, in this case 30ms, this is quite low to still have performance)
Boost: 0 (no boost enabled)
Hispeed_Freq: 864000 (864 MHz as target frequency once the load has exceeded 90% (as stated in go_hispeed_load))
Timer_Rate: 20000 (timer tick rate, in my case 20ms.. I tried setting it to 30ms but then my phone reboots on regular basis)
Above_hispeed_delay: 60000 (the amount of time before we downscale in MHz, in this case 60ms to keep some speed when scrolling and releasing) (once your finger untouches the screen the CPU easily goes back to 384 MHz due to the load being 'gone' and thus causing stuttering)
go_hispeed_load: 90 (the amount of load in % before we go to the hispeed_freq (in my case 864 MHz)) (it will upscale even more if the load is even more)
The thing is, that in the first post which I linked to, there is a mention of the target_load variable. I could not find this variable in the Xceed 4.4.3 kernel.. I think the developer didn't include this in the kernel.
That's to bad.
Set lower frequencies undervolt: 50 mV
Set higher frequencies undervolt: 50 mV
Krait voltage boost: Disabled
Krait C-states settings:
[Checked] Enable C0 (WFI)
[Checked] Enable C2 (stand alone power collapse)
[Unchecked] Enable C3 (power collapse)
GPU didn't change.
I/O Scheduler: SIO (I've also tried deadline, that's also a really nice scheduler)
Internal storage read-ahead: 512 kB
[Unchecked] I/O Stats (only logs stuff and eats battery, don't need this unless you're doing something with it)
Small scheduler readout:
I've tried many schedulers and found out that they really have an influence on battery life, a significant one, especially in the Interactive governor. I think that the I/O scheduler sort of determines the amount of load on the processor (and thus controls more of the MHz scaling since we trigger via a % of load to set a higher MHz).
FIOPS is the best in performance I've noticed, but with the same setup (and only a different scheduler) I have had 12 hours of battery life with it. With other schedulers such as SIO and Deadline it was much much better (I think mostly due to the CPU scaling correctly/better)
D2W and HTC logo remapping are all DISABLED. DO NOT USE D2W it's a battery killer!!!
Vibrator Intensity Control:
set to 1600 mV (less volt is less battery usage! I can still feel it thou)
Min core frequency: 384 MHz(if you have a custom kernel, the frosted kernel for example, you can also set it to 192 MHz)
Governor: Interactive
Min_sample_time: 30000 (the amount of time before we upscale in MHz, in this case 30ms, this is quite low to still have performance)
Boost: 0 (no boost enabled)
Hispeed_Freq: 864000 (864 MHz as target frequency once the load has exceeded 90% (as stated in go_hispeed_load))
Timer_Rate: 20000 (timer tick rate, in my case 20ms.. I tried setting it to 30ms but then my phone reboots on regular basis)
Above_hispeed_delay: 60000 (the amount of time before we downscale in MHz, in this case 60ms to keep some speed when scrolling and releasing) (once your finger untouches the screen the CPU easily goes back to 384 MHz due to the load being 'gone' and thus causing stuttering)
go_hispeed_load: 90 (the amount of load in % before we go to the hispeed_freq (in my case 864 MHz)) (it will upscale even more if the load is even more)
The thing is, that in the first post which I linked to, there is a mention of the target_load variable. I could not find this variable in the Xceed 4.4.3 kernel.. I think the developer didn't include this in the kernel.
That's to bad.Set lower frequencies undervolt: 50 mV
Set higher frequencies undervolt: 50 mV
Krait voltage boost: Disabled
Krait C-states settings:
[Checked] Enable C0 (WFI)
[Checked] Enable C2 (stand alone power collapse)
[Unchecked] Enable C3 (power collapse)
GPU didn't change.
I/O Scheduler: SIO (I've also tried deadline, that's also a really nice scheduler)
Internal storage read-ahead: 512 kB
[Unchecked] I/O Stats (only logs stuff and eats battery, don't need this unless you're doing something with it)
Small scheduler readout:
I've tried many schedulers and found out that they really have an influence on battery life, a significant one, especially in the Interactive governor. I think that the I/O scheduler sort of determines the amount of load on the processor (and thus controls more of the MHz scaling since we trigger via a % of load to set a higher MHz).
FIOPS is the best in performance I've noticed, but with the same setup (and only a different scheduler) I have had 12 hours of battery life with it. With other schedulers such as SIO and Deadline it was much much better (I think mostly due to the CPU scaling correctly/better)
D2W and HTC logo remapping are all DISABLED. DO NOT USE D2W it's a battery killer!!!
Vibrator Intensity Control:
set to 1600 mV (less volt is less battery usage! I can still feel it thou)
- Trickster Mod:
First of all, I've bought (donated) for the PRO version of this, I recommend you do this for all the features!
Minfree control:
I've experimented with this, didnt really work out for me. I can imagine that we can save some RAM and thus have less stuttering and more performance, but to date I didnt mess around with it too much.
Scheduler as set in Synapse (if you set it in one it will also be in the other)
CPU Frequency Control:
Frequency Lock [ON] (VERY IMPORTANT!!! Else the CPU will still go to 1728 MHz!!)
Max core frequency: 1404 MHz (you really do not need any more)
Min core frequency: 384 MHz (if you have a custom kernel, the frosted kernel for example, you can also set it to 192 MHz)
Governor as set in Synapse (if you set one it will be in the other)
MP-Decision [OFF]
I've noticed that when turning this on, the CPU does not scale as I want it to scale, It starts to act like 'all or nothing' again so I can't really set the proper frequency trough the load % trigger!
In other words, it easily sets the load to 100% VERY fast and thus maxxing out the frequency VERY fast (we do not want this)
Minfree control:
I've experimented with this, didnt really work out for me. I can imagine that we can save some RAM and thus have less stuttering and more performance, but to date I didnt mess around with it too much.
Scheduler as set in Synapse (if you set it in one it will also be in the other)
CPU Frequency Control:
Frequency Lock [ON] (VERY IMPORTANT!!! Else the CPU will still go to 1728 MHz!!)
Max core frequency: 1404 MHz (you really do not need any more)
Min core frequency: 384 MHz (if you have a custom kernel, the frosted kernel for example, you can also set it to 192 MHz)
Governor as set in Synapse (if you set one it will be in the other)
MP-Decision [OFF]
I've noticed that when turning this on, the CPU does not scale as I want it to scale, It starts to act like 'all or nothing' again so I can't really set the proper frequency trough the load % trigger!
In other words, it easily sets the load to 100% VERY fast and thus maxxing out the frequency VERY fast (we do not want this)
That's about it! The rest is not modified so just leave it as it.
Keep in mind that I:
- Whatsapp a lot
- Check Facebook every now and then
- Play a game called 'Trivia Crack' every now and then
- Browse websites a lot
- Make a phone call every now and then
The results are in the attachments!
Attachments
Thanks for all the info, though i'm looking for something specific now.
When i first installed the kernel and Synapse, i selected the "msm-dcvs" governor, using that, the second core would go idle (off) when not being in use much and come online if needed (just like my M9 does with the 4 extra cores).
But after that issue, I installed the frostbricked kernel. But this one didn't had that, the gov would actually be like stuck around 1400-1700+ and not go lower.
So i reinstalled the exceed kernel, but now the same gov doesn't do as it did before anymore, but still stuck in those high values
So how can I get it back so core no.2 will go idle/off when not in use/needed?
When i first installed the kernel and Synapse, i selected the "msm-dcvs" governor, using that, the second core would go idle (off) when not being in use much and come online if needed (just like my M9 does with the 4 extra cores).
But after that issue, I installed the frostbricked kernel. But this one didn't had that, the gov would actually be like stuck around 1400-1700+ and not go lower.
So i reinstalled the exceed kernel, but now the same gov doesn't do as it did before anymore, but still stuck in those high values
So how can I get it back so core no.2 will go idle/off when not in use/needed?
No problem, the battery saving post was not specific related to your reply though.Thanks for all the info, though i'm looking for something specific now.
When i first installed the kernel and Synapse, i selected the "msm-dcvs" governor, using that, the second core would go idle (off) when not being in use much and come online if needed (just like my M9 does with the 4 extra cores).
But after that issue, I installed the frostbricked kernel. But this one didn't had that, the gov would actually be like stuck around 1400-1700+ and not go lower.
So i reinstalled the exceed kernel, but now the same gov doesn't do as it did before anymore, but still stuck in those high values
So how can I get it back so core no.2 will go idle/off when not in use/needed?
Frostbricked kernel is for Cyanogen mod based ROM's only..
I'm sorry, could you rephrase this bit? I don't understand what you mean here.. even when I translate it 1-on-1 to Dutch. You can also type in in Dutch if you like. What do you want / what are your intentions?
Whilst re-installing Xceed, did you clear dalvik/cache?
Well the kernel did work lol, not a single issue with it being just stock as they deliver
I meant to say that when I first used the Exceed kernel and used the gov "msm-dcvs", whenever my phone would idle and not use CPU, the secondary core would go "offline/idle", as the M9 4 other cores does (see attachment what I mean). (meaning it would show core 1 as 384Mhz and second core was offline.)
But now I cannot get that back anymore, with no idea what's gone wrong.
I meant to say that when I first used the Exceed kernel and used the gov "msm-dcvs", whenever my phone would idle and not use CPU, the secondary core would go "offline/idle", as the M9 4 other cores does (see attachment what I mean). (meaning it would show core 1 as 384Mhz and second core was offline.)
But now I cannot get that back anymore, with no idea what's gone wrong.
Last edited:
Hi guys,
InsertCoin Enhanced [ICE] is looking for you
InsertCoin Enhanced [ICE] is looking for you
I have uninstalled Xceed because I had too much problem with IC 3. 0.7.
Now I have installed a clean 3.0.7. There are still two issues for me. IC market app doesn't work, I can't connect to my account.
I would like also to use vocal command to do a phone call, pushing the mic button and say... "call John". But it doesn't work, the mic stay on for an half of a second and then it shuts down
Does anybody know how to fix it?
Now I have installed a clean 3.0.7. There are still two issues for me. IC market app doesn't work, I can't connect to my account.
I would like also to use vocal command to do a phone call, pushing the mic button and say... "call John". But it doesn't work, the mic stay on for an half of a second and then it shuts down
Does anybody know how to fix it?
Any update on this? I just got my mini back from repair and want to install the latest software and let it catch dust as my back-up phone.
I see I'm still on 2.22 hboot, while 4.14 is around (at least if my sleepy brain isn't deceiving me.. Any advantages of using that with IC3.0.7 or won't that work?
Does anybody have problem to connect to IC Market ?
I can't... it always says "timeout error".
I would like to try InsertCoin 4.0.6, where can I find it ?
Anyway, IC 3.0.7 works well without Xceed
I can't... it always says "timeout error".
I would like to try InsertCoin 4.0.6, where can I find it ?
Anyway, IC 3.0.7 works well without Xceed
Same problem with 3.07 and IC Market (timeout!).
I´be installed xeed kernel (M4-KK-442-prod-bld1.zip) and used gov "msm-dcvs". All is working fine, the second core turns on when needed.
How do I uninstall the xeed kernel? Where can I download the original kernel?
I´be installed xeed kernel (M4-KK-442-prod-bld1.zip) and used gov "msm-dcvs". All is working fine, the second core turns on when needed.
How do I uninstall the xeed kernel? Where can I download the original kernel?
Ok, so I'm not the only one with IC Market issue!
Why do you want unistall Xceed if it works ?
I think that with Xceed + Synapse the phone works faster.
So... I still have two questions
- Where can I download IC 4.0.6 ?
- Does IC 3.0.8 (4.4.2 KK) have Xceed kernel inside ?
I've always boot loops issue with 3.0.7 + Xceed.
Thanks !
Marco
Why do you want unistall Xceed if it works ?
I think that with Xceed + Synapse the phone works faster.
So... I still have two questions
- Where can I download IC 4.0.6 ?
- Does IC 3.0.8 (4.4.2 KK) have Xceed kernel inside ?
I've always boot loops issue with 3.0.7 + Xceed.
Thanks !
Marco
Thanks but that's the one I tried flashing earlier without success. Tried downloading several times both to pc and phone.
Edit: weird. Now it worked
Edit: weird. Now it worked
Last edited:
No, IC 3.08 does not have the Xceed Kernel in by default.So... I still have two questions
- Where can I download IC 4.0.6 ?
- Does IC 3.0.8 (4.4.2 KK) have Xceed kernel inside ?
I've always boot loops issue with 3.0.7 + Xceed.
As for the boot loops:
- Wipe [Cache] + [Dalvik Cache]
- Install latest Xceed kernel (for Android 4.4.3)
- Wipe [Cache] + [Dalvik Cache]
- Reboot
Good luck!
Edit (kernel):
Last edited:
I've seen several ppl say disable dt2w, but how about s2w and logo remap?
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
- Location: Deny
Skype
- Stay awake: Deny
Google Play Music
- Stay awake: Deny
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
- Place notification: Deny
- 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)
- 1512 MHz
Set Minimum Core frequency
- 384 MHz
CPU Governors
- Interactive
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
- 10 mV (same as above)
Krait Voltage Boost
- Disabled
----------------------------------------
I/O Scheduler!
------------------------------------------
Internal Storage
- FIOPS
Internal storage read-ahead
- 512 kB
---------------------------------------
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
Last edited:
So, as we see all development for M4 has stopped. Which means we -- unlocked and rooted users -- are stuck with one of the current custom ROMs until we get a new phone.
From all I can say, the most stable and usable ROM I've had on M4 up till now is InsertCoin 3.0.7 with corresponding Xceed kernel, NO Synapse, NO Xposed, NO heavy tweaking.
I know that's pretty limited but basically it's the only configuration under which most functions of the phone work more or less reliable in the long run. From my experience, any set-up more advanced than that will cause major instability problems sooner or later.
From all I can say, the most stable and usable ROM I've had on M4 up till now is InsertCoin 3.0.7 with corresponding Xceed kernel, NO Synapse, NO Xposed, NO heavy tweaking.
I know that's pretty limited but basically it's the only configuration under which most functions of the phone work more or less reliable in the long run. From my experience, any set-up more advanced than that will cause major instability problems sooner or later.
Last edited:
New posts
-
[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi- Latest: opel astra screen
-
[MOD][XPOSED][3.1.1] CustoMIUIzer - Customize your MIUI ROM
- Latest: nikdrlecter
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone