I have a HD2 with an older version of android cooked on. Android version 2.3.7 Kernel version 2.6.32.15_tytung_r12.4-heebf2c Mod version is CyanogenMod-7.1.0 Desire (Typhoon_v3.7.0 Magldr) I think my radio is 2.15.50.14
I really need the wifi calling feature on my phone to work. Do all the roms have this problem on our phones? Would it be easier for me to just install a new rom? Every time I turn on wifi, the phone freezes completely. I read through the post regarding this issue, but there was no specific information given about how to overclock the phone. I downloaded nofrills cpu control and have tried random combinations, but was wondering the ideal oc speed?
resevil83 said:
I have a HD2 with an older version of android cooked on. Android version 2.3.7 Kernel version 2.6.32.15_tytung_r12.4-heebf2c Mod version is CyanogenMod-7.1.0 Desire (Typhoon_v3.7.0 Magldr) I think my radio is 2.15.50.14
I really need the wifi calling feature on my phone to work. Do all the roms have this problem on our phones? Would it be easier for me to just install a new rom? Every time I turn on wifi, the phone freezes completely. I read through the post regarding this issue, but there was no specific information given about how to overclock the phone. I downloaded nofrills cpu control and have tried random combinations, but was wondering the ideal oc speed?
Click to expand...
Click to collapse
I never used Tytung's GB rom but wifi generally works very well. I used it all the time with Typhoon GB, Tytung's ICS and JB.
For overclocking Install Setcpu from the Play Store.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Can you give me an estimated range I should set my cpu to? I can't find the thread, but somewhere along the line I read something about how you should over clock your processor in multiples of something. I'm not describing it well, but maybe it had something to do with a mhz speed and then a frequency or another unit of measurement for power. Like volts. I have no idea, what I'm trying to say is that I read there is some sort of calculation you need to figure out in order to properly adjust your cpu settings.
ny_limited said:
I never used Tytung's GB rom but wifi generally works very well. I used it all the time with Typhoon GB, Tytung's ICS and JB.
For overclocking Install Setcpu from the Play Store.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Click to expand...
Click to collapse
resevil83 said:
Can you give me an estimated range I should set my cpu to? I can't find the thread, but somewhere along the line I read something about how you should over clock your processor in multiples of something. I'm not describing it well, but maybe it had something to do with a mhz speed and then a frequency or another unit of measurement for power. Like volts. I have no idea, what I'm trying to say is that I read there is some sort of calculation you need to figure out in order to properly adjust your cpu settings.
Click to expand...
Click to collapse
I think that all better apps for this already take care of much of what you are looking for. I know SetCPU does - in fact it has profiles for numerous phones, including the HD2. The one disadvantage that I tend to forget is that it isn't free. If you look at the app's description on Google Play you will get a lot of ideas. Likewise, the developer's web site also has some good info.
Briefly, I do not set any profile's low frequency below 245 MHz (potential SODs). The high-end you can experiment - if the HD2 locks up reboot and set it lower.
I have a default profile and change it to faster MHz if plugged in (I don't care about using more power when plugged in) or lower frequencies for sleep or overheating and such. If you do get SetCPU you can plug in the attached profiles (don't forget to unzip it first!) and see if you like any of them. They can all be changed or deleted, of course.
I tried to search for a thread relating to this but couldn't find anything, if anyone knows of one a link would be appreciated.
OK, so I flashed Motleys kernel 2 days ago. Everything was running fine, I had it OC'd to 1.6 and it was super fast and smooth. I had set the governor to "on-demand" to try and save some battery life(over "performance"), and also because it seemed like the CPU would run at full 1.6 constantly if it was set to performance (I don't know if that's how it should be or not, but this isn't the issue). I used System Tuner to OC it like he recommended in his thread.
Yesterday I set it to performance to run some benchmarks, and then continued using it on performance to see how it felt. About an hour and a half later I also started messing with my home screen and apps and ended up accidentally using Quick Boot to take me to the bootloader. After powering it back on I checked System Tuner to set the governor and once I did I noticed, according to System Tuner, that 2-4 of the cores are running at full 1.6 and the CPU usage is from 25%-100% even though I have nothing open.
I flashed my recovery via Clockworkmod Recovery, Motleys kernel is now replaced by the stock kernel, however I'm still having the same issue, but just at 1.3. Any idea why the CPU is running so high, for apparently no reason?
.....
OK, so I just checked System Tuner again and the CPU doesn't seem to be doing as bad now, but it's still all over the place and I don't have anything else open. Here are the times:
Offline - 77%
340MHz -11%
475Mhz 1%
1.2Ghz - 5%
1.3Ghz - 1%
Compared to yesterday when it had said 1.3GHz 79% or something like that (and was running nothing but system tuner).
So, yeah, that does seem a lot better but one thing remains; the CPU usage still jumps up to almost 50% and once again, I am running nothing but System Tuner, so something still doesn't feel right.
I think ondemand governor is causing the CPU to shoot up so often and quickly.(That's all I can think of.) I always use interactive and it's usually the preferred governor. Ondemand is more for people who play lots of games and they need the extra boost. If you game a lot then I guess you should still to it.
Sent from my Nexus 4 using Tapatalk 2
SO... in regards to the KT-SGS4 KitKat 4.4 TouchWiz kernel, the vast majority of users seem to have no problems with it, but there ARE KNOWN issues that appear to be caused by this kernel for some users, with varying degrees of rarity. WHY certain users have these issues when others do not is not currently known, but it would be great if we could figure this out. I am HOPING this thread (and it will only be a THREAD with input from others) will help us find cures for the issues we face with this kernel.
KNOWN ISSUES:
#1. Sound skipping - This seems to be the most common issue experienced with the kernel and I actually would not call it rare. Some possible fixes for this are to: A) increase the Media/Music Min Mhz and Bluetooth Profile Mhz to around 702 Mhz or so, B) try using a different I/O Scheduler and try adjusting the Internal and External Read Ahead Buffers, C) change disable_hotplug_media from a 0 to 1.
#2. Phone freezes/locks up while charging
#3. Screen flickers when a window is open over the desktop
#4. Mobile connection/data (and possibly also GPS) loss a while after booting phone - this may be the rarest issue, but it is OBVIOUSLY the most serious. I have suffered from it personally. I contacted Ktoonsez regarding this and he denies it being a known issue since many thousands of users use his kernels and don't have this issue... I have confirmed multiple other users who DO have this issue and the only thing I see we have in common is the KT-SGS4 kernel. It appears that this issue MAY be fixable by using the "right" choice of governor and settings. The problem is that what the "right" choice of governor and settings are MAY be determined by your ROM. On stock rooted NAE with MF9 bootloader, using largely the kernel default settings, including the interactive governor, APPEARS to have cured this issue for me (as well as the freeze while charging), while using the ktoonserativeq governor or the pegasuq governor appear to have caused this issue (I am still in the process of investigating this...).
This is not meant to be in any way negative towards Ktoonsez and I certainly appreciate all the work he does to provide us kernels, but there ARE issues that some of experience and I hope this thread can help us work TOGETHER to solve them! If there are any other issue that you believe should be listed, please post them. If you have any possible cures, please post them. If you need any help, please ask. If you have any input, please post! :highfive:
I can't get his kernel to run on my phone for the life of me so I stuck with Negalite NAE Stock Kernel, but I use his kernel religiously on my wife's s3. Even using basically the same setup I still get skipping on music, phone goes unresponsive after charging a few hours. And a few others.
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)? I think the governor and adjustments are also critical in solving this problem. I've been using ondemand and somebody said interactive is also helpful. The other thing here is that it could be an issue of I/o scheduler. I've been using sio. I'm getting minimal skipping at this point. You're right that ktoonservativeq caused MAJOR skipping, even with tons of governor tweaks.
After switching to ondemand, my phone hasn't locked up while charging, but it has randomly locked up at other times. Weird.
On issue #4, I've lost data less with ondemand but it hasn't completely solved the problem. Sometimes I can toggle Airplane Mode on and off and get going again, but mostly that toggle won't even work and I have to reboot.
JesseAaronSafir said:
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)?
Click to expand...
Click to collapse
That is an interesting question, now that you mention it. I had been using ViPER4Android, probably while I was having the skipping issue, but I stopped using it in the long process of attempting to cure my mobile connection issue (I read something that made me think it could be related) and I'm actually not sure if I ever had the skipping issue without it.
Of all the issues though, this one is very common in the KT-SGS4 kernel thread, so I DOUBT (but don't know) that everyone experiencing it is using
ViPER4Android.
(Also, I THINK it skipped for me without Convolver turned on).
I haven't used v4a since I was on Negalites
elwood said:
I haven't used v4a since I was on Negalites
Click to expand...
Click to collapse
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
rsngfrce said:
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
Click to expand...
Click to collapse
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
arikdahn said:
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
Click to expand...
Click to collapse
I didn't forget it, it is issue #2!
#2. Phone freezes/locks up while charging
In my experience, the phone does NOT have to be off while it is charging to have this issue, it would happen to me when I was charging my phone with it on. Fortunately, on NAE stock rooted with MF9 bootloader, using the mostly default kernel settings with the interactive governor seems to have fixed this issue for me, as well as the mobile connection/GPS issue (knock on wood still...). I mainly just adjusted the I/0 Sceduler to noop and the Media/Music and Bluetooth Min Mhz to 702 Mhz from the stock settings. The only issue I am personally left with now is the screen flicker.
I don't think the screen being on or off relates THAT much to the music skipping issue, it skipped for me too with the screen on. Definitely I would say, using the ktoonservativeq governor with Ktoonsez' settings WILL result in music skipping... BUT, IMO, this MUST BE TAKEN INTO ACCOUNT, Ktoonsez DOES NOT HAVE OUR PHONE... how can his settings POSSIBLY be OPTIMAL for our phone? Think about that!
As far as your WiFi tethering issue, I am well aware of it personally, having read your other posts, but I don't know much about this (don't use it myself) and in another thread I was going to direct you to a link you are already aware of that didn't help. If anyone can help arikdahn with this, please jump in! :good:
I definitely had more problems with music skipping when the screen would turn off. Using ondemand or interactive with sio and 2048 read ahead caches seems to have almost completely resolved the issue for me. I'm still not sure which I/o scheduler is best.
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
rsngfrce said:
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
Click to expand...
Click to collapse
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
arikdahn said:
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
Click to expand...
Click to collapse
Hey, I'm not in any way disputing what you are saying, the point of this thread is to figure these things out! I'm certainly not presenting myself as the expert on these issues! I'm just a lucky one who seems to have mostly resolved the issues on MY phone. (BUT... I AM NO ANDROID EXPERT EITHER and will never claim to be, but I am not saying it is a limited-resources issues, what I am saying is that I believe the default settings will allow the governor to throttle down to below the level necessary to play music without skipping... I could be wrong, but that it what it looks like to me.)
Because SO MANY people APPARENTLY don't have MOST of the issues mentioned, I personally think this is highly related to which ROM you are using... though I don't know what ROM those other people are using...
So, XT1575 running LineageOS 14.1, rooted.
As we all know, this model is known for killing the battery after a few years, and I have already done one replacement myself, and that replacement is already starting to misbehave, shutting down randomly or at 10% battery and so on.
So, before replacing it one last time (since I really like the phone), I wanted to try some fine tune via clock frequency and hottplugs with a custom kernel in order to reduce power consumption and heat generation since the stock Clark is like a little fusion reactor.
I downloaded and installed HandBag Kernel 2.3.1, and everything works wonders except for one thing, It apparently wont allow me to change neither governors or frequency's of the two BIG cores, and they just keep going full speed when underclocking the four LITTLE cores, which is an improvement from stock configurations, but it's not what I intended.
I'm using Kernel Adiutor to setup any configuration, and every other option seems to be working perfectly fine.
Any insight would be much appreciated, and I will provide any extra info if needed so.
Thanks in advance!
I have problem on my OP 8 Pro, I no can set in Franco Manager kernel minimi frequently for little core 300, the same change to 1000? Does anyone have any idea what causes this effect? I no used any app to boost phone... After reboot is normal, i can set 300. Help?
Any advice?
So depending on what kernel you're on it may reset or the settings could be forced.
So EX allows me to go to 300 and stay there, also allows me to lower the max to 100MHz lower. (no performance hit, much cooler phone)
So my advice would be ask in the kernel thread, chances are it's forced to be at 1GHz as Is stock
dladz said:
So depending on what kernel you're on it may reset or the settings could be forced.
So EX allows me to go to 300 and stay there, also allows me to lower the max to 100MHz lower. (no performance hit, much cooler phone)
So my advice would be ask in the kernel thread, chances are it's forced to be at 1GHz as Is stock
Click to expand...
Click to collapse
Ok, I understand, but I restart phone and its normal, I can set 300, after a few hours, I set 300, the same set 1000...
Testing 3 kernels.