SetCPU causing volume issues - EVO 4G General

FYI to anyone using SetCPU. I have discovered an issue with my ringer volume caused by running SetCPU. The issue is intermittent but quite annoying. Regardless of the volume of my ringtone the phone will either start out with a normal ring volume and get extremely loud or just start out as if you had the volume turned all the way up. I changed ringtones, turned off quiet ring on pickup, changed Kernels and even wiped and re-flashed ROMs. This was driving me crazy. I tried all kinds of volume apps to remedy the issue also to no avail. This is not ROM specific as it happened to me on Fresh, Evio, Elite, MikFroyo and Azrael. I don’t know if this happens with all Kernels but it did happen on HTC stock #15 and Netarchy 4.3.1 havs-nosbc. I do know this…..as soon as I removed SetCPU the issue immediately went away. I was not running any profiles in SetCPU. The strange thing is….on an AOSP ROM (Cyanogen/MIUI) this does not occur with SetCPU running. Has anyone else run into this? Hope this was helpful if anyone else has experienced this issue. Hopefully someone has a fix/workaround to this issue.
After going crazy with this issue that seemed to pop out of nowhere I decided to backup my crucial data from my sdcard and format it. I then did a full wipe (2x using Amon Ra 2.3) and flashed MikFroyo 4.5. I installed some basic apps (Weather Channel, Walgreens, Zynga Poker, Go SMS, Blacklist, Dr. Web). So far I have not had any volume issues (without SetCPU). I will install and test with SetCPU and provide feedback. Although I may just test out my battery life as is for now. Some of these tweaked ROM's and newer Kernels just about eliminate the need for SetCPU or Overclock widget (IMO). In other postings I've read they just cause issues negating the purpose of a HAVS Kernel altogether. We shall see.
I finally found others with this issue. Apparently this is a feature?? Anyone else heard of this? I suppose I didn't take notice that my phone only does this when in the belt case (sensors covered). Certainly there must be a way to disable this.
http://forum.xda-developers.com/showthread.php?p=11781327#post11781327
http://forum.androidcentral.com/showthread.php?p=669629#post669629

Man, I have a friend that has been having trouble with his volume control and we couldn't figure it out. He uses setCPU, and I don't... I think I better send a link to this post.

I've been running SetCPU on my Evo for 6 months with many different ROMs/kernels and I've never experienced this. Sounds to me like you have a volume, or music app/widget that's conflicting.

12MaNy said:
I've been running SetCPU on my Evo for 6 months with many different ROMs/kernels and I've never experienced this. Sounds to me like you have a volume, or music app/widget that's conflicting.
Click to expand...
Click to collapse
I thought so too. However, after a fresh flash of a ROM and installing SetCPU this issue starts. Really strange.
See changes in my first post. It's not SetCPU.

Related

leedroid lag?

Hi, I've just flashed leedroid but I seem to be suffering with some small amount of lag that I didn't experience on the stock Rom..... when I open messages or emails for example there is a small pause, and u can visibly see the screen refresh. I never suffered with this this beforehand. Also I have noticed that I'm getting some lag when changing certain settings, the leedeoid Icon pops up whilst its thinking..... now, so far I haven't gotten around to installing the LeeDrOiD Ace V2.2.5 R2 Kernel, is that likely to fix my little issue?
Cheers
Steve
After flashing, have you done another reboot? Sometimes I find a new ROM doesn't settle until I've rebooted a couple of times. Give it a try and see how it feels then report back either way
Let it bed in steve, should have dropped this in the rom thread
LeeDroid said:
Let it bed in steve, should have dropped this in the rom thread
Click to expand...
Click to collapse
New members aren't allowed to post in Dev section until they hit a certain post count
Yup...reboot will fix your problem..
Sent from my Desire HD using XDA App
Thanks for the reply Lee, but as citizenlee said, I'm unable to post in that section at present.
So far i still seem to be having the slow refresh issue on sms and emails, do u think that the fact I haven't flashed the Ace V2.2.5 R2 Kernel yet could be part of the issue? I'm certainly going to try flashing it to see if it helps..... I know know you've put a heck of a lot of work into this and believe me it is appreciated, just hope I can get it working as well as it was intended.
You could try the kernel... and failing that a full wipe and reflash of the ROM should sort you out
problem
LeeDroid said:
Let it bed in steve, should have dropped this in the rom thread
Click to expand...
Click to collapse
dear lee i have installed your PERFECT rom 2.2 1.8 ghz
but it has frozen 2 times the screen and after rebooting it stays frozen...?
this also happened with coredroid ..any suggestions my friend?
regards(i am new here^^)
Ok, i think i got to the bottom of my lag problems. I have been playing around with set cpu today. I think the minimum speed of 245mhz in smartass was too low and was causing the lag (usually when waking the phone from screen off) I have now changed settings to 'ondemand' with a minimum speed of 245mhz and maximum of 1344mhz but i also created a 'screen off' profile with a working range of 245mhz to 576mhz which seems to give it a bit more poke when waking from screen off No more lag! ( i still have the visible refresh issue i mentioned, maybe i'm imagining that one though, maybe it did do it on the stock rom but i didn't take note of it....??)
So, i really have no idea if i've done the right thing with the way i have set up setcpu so if anyone would care to comment on the settings i've used please do so.
Many thanks again for all the help.
Steve

[Q] Random lock ups freeze

I keep getting random lockups, at least more than once a day, and sometimes several reboots in a row.
It appears that i can happen almost any time, whether it be at a lock screen, while titanium is asking for root, or opening twitter or facebook, even the gmail app. It simply freezes, and requires me to long press the off button and reboot.
Unfortunately, i can't get adb via usb to work on the nook, so i can't get a reliable logcat.
Is this common? I have had two nook devices so far, tranferred the rom over through nandroid and have had lock ups on both, I am flashing regular cm7 nightlies now (emmc), but it occured using phiremod too.
Help?
I never had one, maybe I'm lucky
Have you tried fixing permissions in clockwork?
Sent from my LG Optimus V using Tapatalk
I am having the same problem. I loaded CM7 to my emmc yesterday and I have had it freeze on me a couple of times now. All have been random. I do have performance set to 1.1 and on demand gov set.
So I can just go to ROM manager to fix permissions? Hopefully that works.
EDIT**
Did not work. Was fine, then I uninstalled market updates, connected to wifi, opened the old market, searched for flash and it froze up. Any ideas?
EDIT 2**
uninstalled beautiful widgets (read that somewhere), so far no lockups (fingers crossed).
i had mine lock-up twice last night
i was in dolphinHD and i had just installed swype beta
i have only had 1 time that it has locked up before then in the last 1-2 months that i have had it.
im blaming swype, since i havent had the problem in the past
perhaps not your problem, if you dont have it installed.
I get lockups pretty regularly. It's irritating. Not sure what the cause is. I thought overclocking had something to do with it but everyone else is overclocked and this problem doesn't seem to be common.
How low do you have the voltage settings in tweaks? Having a voltage just barely too low for your CPU can cause a lot of weirdness. Also, it could be any one of the stepping voltage settings, not necessarily either the min/max frequency.
Folks, playing with the voltage settings in nook tweeks is not for the average user. These settings can really bork your nook. That's why you get a warning when you open those settings.
That being said, I have been running cm7 on eMMC for months and have never had a lockup. I am overclocked to 1200 mHz but have left the voltages alone.(cm7.1 nightly 160).
If you are running on eMMC,try fix permissions first. If that does not help, start looking at the apps you are running to determine if one of them might be the problem. Several people have reported issues running beautiful widgets. There are other apps that can cause issues. If you have good backups of all your apps, try removing apps one at a time. In the process, you might learn something about your system.
Worst case, reinstall cm7, wipe data, cache, and dalvic cache. Start over with a clean system and add your apps (apps only, not apps+data) one at a time. This will ensure that a possibly currupt data set was not causing the issue.
The key to a fast, well functioning nook is to start slowly and ensure each change works well before moving on to the next step.
While it's true I have more time than most to play (retired), my nook can run circles around most competitors but only because I took the time to set it up right the first time and I am not afraid to wipe everything and start over.
Sent from my NookColor using Tapatalk
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
I had been getting irritated by these these random locks up for a while. It seems that uninstalling beautiful widgets fixed the problem for me. I thought it might be that BW was trying to access the GPS, but it still locked up after disabling geo location in BW.
liam.lah said:
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
Click to expand...
Click to collapse
In case you're still interested, BeWeather is a great substitute for BW and FlexT9 in place of Swype.
Also, I had issues with lockups no matter my overclocking and formatting the eMMC and possibly reseating the SD card fixed it.

Why does my DZ fail me when I need it the most

Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html

[Q] Troubleshoot shutdown on 4.3/4.4 based roms

My phone shuts down on 4.3 and 4.4 based roms.
It happens much less often on 4.2 and stock based roms.
It seems to happen when the screen is off. It doesn't shut down when I'm in the middle of doing something. I've seen that on other phones.
If the screen is off, but I'm listening to the music player or Pandora, it does not shut down.
It does not seem to be overheating.
I'm on my 3rd sim card in 2 months and my second class 4 SD card. I only bought a new one b/c used the one from my old phone and thought it was best to start fresh.
Currently I'm running the first CM11, but this has been happening on CM 10.2, AOKP, and a variety of other roms.
My recovery is TWRP 2.6.3.0
I use the regular GAPPS, not PaGAPPS and the appropriate GAPPS for the given AOSP base; 4.2/3/4
I flash SuperSu-v1.65 after a full wipe when installing new roms.
The current apps I have installed in addition to what comes with CM are:
Evernote
Freecell
Google Voice
gReader Pro
Pandora
Quickoffice
Rom Toolbox Pro
Scanner Radio
Shuttle+
SMS Backup+Restore
Solitaire
Tapatalk Pro
UPM - Universal Password Manager
Xposed Installer - I don't have any modules installed at the moment and the last time today it shut down by itself was before I installed Xposed.
I know that logcats are good for tracking down errors for apps that FC, though I don't know yet how to read logs.
Is there an app I can use that can show me activity before the last shutdown?
How can I track down what's causing it?
TIA
please delete
On 2nd thought I did not feel I could contribute well.
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
aviwdoowks said:
please delete
On 2nd thought I did not feel I could contribute well.
Click to expand...
Click to collapse
Thanks for trying though.
ATTACK said:
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
Click to expand...
Click to collapse
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
FirePsych said:
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
Click to expand...
Click to collapse
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Thanks,
I had read that the SOD had been reported elsewhere, but never saw any solutions. Just lots of folks replacing their phones.
I haven't had one in the last 24 hrs on the 12/08 CM nightly and flashed the 12/09 this morning.
I also made the MPdecisions change. We'll see if it sticks. I assume since it's a system file, I'll have to make the change every time I flash a new nightly or or new rom, but that's not a big deal.
Oh, and yes SOD is probably more accurate than "shutdown" because I've noticed that the led will flash if I've received a message, but I can't revive the phone, so obviously it's not complete shut down.
ATTACK said:
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Click to expand...
Click to collapse
@ATTACK.
Thank you!
I hate to jynx myself, butthis seems to have done the trick. Only had 1 or 2 BSOD since your response and I think both times were because I forgot to make the change after flashing a new rom.
Happy Holidays
FP
This thread may have saved my phone. I keep waking up to find my phone with a blinking LED notification and me being unable to get the screen to turn on. I renamed the MPdecision file and I'll hope for the best. (^^)

KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel

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...

Categories

Resources