This is the support thread for the T-Mobile / U.S. Cellular variant of the StarKissed Note 4 kernel.
This kernel currently supports all North American carriers through the use of specialized release packages that will detect your device version and make appropriate adjustments.
Kernel Development Thread:
http://forum.xda-developers.com/showthread.php?t=2915824
Direct installation available via Flashify (for root users) - Android Apps on Google Play
Heimdall with the S5 patch is needed to flash from a computer. Odin cannot flash this kernel.
Additional information for T-Mobile / U.S. Cellular variant:
Potentially Unavailable:
Potentially Unsafe:
Incomplete / Inactive:
Courtesy of the Sprint thread:
egodriver07 said:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Misterjunky said:
Hi twistedumbrella
I have a question.
Is there any benefit whatsoever in flashing any custom
kernels if the user never plans to modify or change any
of the default settings in the custom kernel?
If it's beneficial to flash a custom kernel without changing
any of the kernel's default settings what are the benefits?
Thanks!
Click to expand...
Click to collapse
The advantage to a custom kernel is the updated code. Even if defaults are left as is, they are not necessarily stock features. Stock kernels are only released with firmware updates, so a lot of the Linux updates can take a long time to arrive. Sometimes the carrier or manufacturer may not even perform Linux or upstream updates, only what it took to match any system changes.
Custom kernels often include additional battery saving or performance updates from the community. These updates may never be officially submitted. These updates may also be too specialized for the "general" kernel most manufacturers maintain, so they are intentionally bypassed.
Configuration is personal preference based on intended use. There is no benefit to using defaults other than lack of desire to customize. The defaults are generally what will be just enough of a starting point for everyone to easily tweak it to their desires, not necessarily what is best.
I configure my defaults based on averages. Some use what they consider the best overall setup for typical usage. Some aim for a specific usage scenario. I have to reconfigure the settings when I install because the defaults don't fit how I use the device (testing games for class projects).
It really is about finding what works for you even by trial and error.
On boot.tmo.11-08-2014_22.12.img
Can't change clock freq values at all. max and min stays at 1.498 GHz at all times.
Same issue is there a way to fix or should I just revert to an older kernel
seriousneo said:
On boot.tmo.11-08-2014_22.12.img
Can't change clock freq values at all. max and min stays at 1.498 GHz at all times.
Click to expand...
Click to collapse
nique0201 said:
Same issue is there a way to fix or should I just revert to an older kernel
Click to expand...
Click to collapse
It's being fixed. It was an issue with the defaults for umbrella_core. Temporary solution is to change governors.
Its stuck for me with every governor...... Just reverted... Anyway this kernel doesn't have BFQ... What's the next best scheduler for HD video recording.. Or are any if the included schedulers based off bfq? I just want to assign it as my SD cards scheduler because that's where I record everything .
nique0201 said:
Its stuck for me with every governor...... Just reverted... Anyway this kernel doesn't have BFQ... What's the next best scheduler for HD video recording.. Or are any if the included schedulers based off bfq? I just want to assign it as my SD cards scheduler because that's where I record everything .
Click to expand...
Click to collapse
CFQ is the closest. I forget if that was already built in. If not, row.
I will second Confirm the stuck govs and clock issue I get 1.4 low and 2.6 high and nothing changes no matter what app I use, also had 2 uncommanded reboot with screen off. Rolled back to previous one.
Compusmurf said:
I will second Confirm the stuck govs and clock issue I get 1.4 low and 2.6 high and nothing changes no matter what app I use, also had 2 uncommanded reboot with screen off. Rolled back to previous one.
Click to expand...
Click to collapse
Confirmations aren't needed when issues are already being addressed. If you are worried nothing is being done, here is a summary of my morning:
32bc62f89416ca66c6ad5c7d1c369540da47edfa
hardlimit: Clearer comparison to base definitions
9bdd4cf3fc402ab31867b262369cfeb581a3110f
Build: Cleanup .orig files when initiating builds
614697abf3ac21bfe1682ec5e0c67f545af1ea35
Linux 3.10.1
7411a44bf9e63e1a678461f9489a7b82b12c831b
Linux 3.10.2
5a0a353611bf3c225c0b8dbc31d1753f49d2b03a
Linux 3.10.3
daa76fd53838d19e54870e0490f044ee1d2b77f2
Linux 3.10.4
604d95229a2fe25533228e003d9221aadb5bf18f
Linux 3.10.5
668f731fd1dad78a2fbd7f3965bee42624782acb
cpufreq: Fixes for Linux 3.10.5, hardlimit
I'm testing the fixes now. There will be a slight delay because Sunday is a recurring project deadline for my degree, but something will be available later on
Lol, not worried at all. Your time and your life come first. Glad with your school project. College can be rough
Compusmurf said:
Lol, not worried at all. Your time and your life come first. Glad with your school project. College can be rough
Click to expand...
Click to collapse
It's just a lot of busy work. Since it's online, we have to record presentations, record an explanation of all our changes, demonstrate the code in action, talk about plans, etc.
After all that I have to question why I had to submit an outline, repo, and binary. It's not like they're going to read the book when they can watch the movie instead.
Pushing an update now that appears to have resolved the issue. It was not the governors at all. Like any other frequency or screen issue thus far, it was hardlimit
I understand completely. I have an IT degree and been working in IT professionally since 1987. It has served me well so far.
After a lot of digging for where something is setting 1497600 (1.49) because the one place I had has long since been removed, I came across:
Code:
#define MIN_TOUCH_LOW_LIMIT 1497600
in cpufreq.h which is part of the stock kernel code. This is used to make sure that when the screen is being used, the CPU ramps up enough to make sure touch is smooth. That is NOT something I added into the kernel. Hardlimit added the capability to adjust these values, but they are still being set by waking the phone.
Anyway, the point is that I am doing what I can to resolve them getting "stuck" on this value, but the purpose of this post is to say that it may still be a "favored" value, but that is just how Samsung intended it.
custom kernel
WHY does this kernel go makes my cpu only go from 1497 MHz to 2457 MHz???
Even if I change the frequency of the cpu to max 2.8 GHz and min 268 MHz, it stays from 1497 and 2457MHz.
y11ohan said:
WHY does this kernel go makes my cpu only go from 1497 MHz to 2457 MHz???
Even if I change the frequency of the cpu to max 2.8 GHz and min 268 MHz, it stays from 1497 and 2457MHz.
Click to expand...
Click to collapse
It hates you. It obviously isn't any of the huge discussion in the main development thread or this one if you still had to ask, so that's the only other answer I can come up with.
-_-
twistedumbrella said:
It hates you. It obviously isn't any of the huge discussion in the main development thread or this one if you still had to ask, so that's the only other answer I can come up with.
Click to expand...
Click to collapse
Omg just LOL so sorry :/
y11ohan said:
Omg just LOL so sorry :/
Click to expand...
Click to collapse
It hates me as well.Lmao
Sent from my SM-N910T using XDA Free mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:05 PM ----------
Can anyone confirm if the stock builds are working better than the deported builds. Thanks In advance!!!
Sent from my SM-N910T using XDA Free mobile app
xda23 said:
It hates me as well.Lmao
Sent from my SM-N910T using XDA Free mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:05 PM ----------
Can anyone confirm if the stock builds are working better than the deported builds. Thanks In advance!!!
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Ouch. That is like "can anyone verify this developer is worthless?"
Anyway, there is an untested update being pushed. The untested part should fix the frequency issue. It's untested because the change is swapping two lines. High was getting written to low and low to high. The result was everything reading invalid and defaulting to mid.
Related
I put together a simple custom voltage interface which can be used to change both the ARM (CPU) and the internal voltage. It is the perfect companion for LiveOC, but does not depend on it.
In /sys/class/misc/customvoltage the ARM and internal voltages for the different frequency states are set by passing a string of voltage values in mV to armvolt or intvolt (for example 'echo "1250 1200 1000 950 950" > armvolt').
This should work no matter the number of frequency states implemented in the kernel. This replaces the custom UV interface most kernels have implemented and both tweaks do not work together. So if you decide to include this tweak, you will have to remove the other and this will break the voltage control with SetCPU and Proton. and it is compatible to SetCPU and similar tools.
Changes to the source: http://www.pastie.org/2806507
BUGFIX:
Made Custom Voltage compatible with the typical CPUfreq UV interface (UV_mV_table) found in many kernels thus making it compatible with SetCPU and similar tools.
Bugfix: http://www.pastie.org/2806920
BUGFIX #2:
Added the entries 'max_arm_volt' and 'max_int_volt' to the sysfs interface which can be used to change the maximum values allowed for the ARM and internal voltages.
Bugfix: http://www.pastie.org/2812494
No further patches will be published here. I have set up a git repo for all my tweaks. Each mod has its own branch to keep the tweaks cleanly separated and one can simply pull the latest patches from the corresponding branch.
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/customvoltage
omg... you with another great mod... we CANNOT CATCH UP AT ALL.. you know
Made Custom Voltage compatible with the typical CPUfreq UV interface (UV_mV_table) found in many kernels thus making it compatible with SetCPU and similar tools.
Bugfix: http://www.pastie.org/2806920
True professionalism
Thank you Ezekeel, you never stop surprising me. I'll test this in a bit.
Ezekeel said:
I put together a simple custom voltage interface which can be used to change both the ARM (CPU) and the internal voltage. It is the perfect companion for LiveOC, but does not depend on it.
In /sys/class/misc/customvoltage the ARM and internal voltages for the different frequency states are set by passing a string of voltage values in mV to armvolt or intvolt (for example 'echo "1250 1200 1000 950 950" > armvolt').
This should work no matter the number of frequency states implemented in the kernel. This replaces the custom UV interface most kernels have implemented and both tweaks do not work together. So if you decide to include this tweak, you will have to remove the other and this will break the voltage control with SetCPU and Proton. and it is compatible to SetCPU and similar tools.
Changes to the source: http://www.pastie.org/2806507
BUGFIX:
Made Custom Voltage compatible with the typical CPUfreq UV interface (UV_mV_table) found in many kernels thus making it compatible with SetCPU and similar tools.
Bugfix: http://www.pastie.org/2806920
Click to expand...
Click to collapse
wow...
just amazing!
Thanks Ezekeel~! your name will forever be engraved on the hall of NS!
Ezekeel i know that you are a God in mods
But, can you explain to me how i will put this mod?
I don't understand what i have to do, i have to change some code lines? replace? or other thing?
if you made a superfast "how to" i will be vert grateful
Yusei said:
Ezekeel i know that you are a God in mods
But, can you explain to me how i will put this mod?
I don't understand what i have to do, i have to change some code lines? replace? or other thing?
if you made a superfast "how to" i will be vert grateful
Click to expand...
Click to collapse
This is kernel code.
franciscofranco said:
This is kernel code.
Click to expand...
Click to collapse
and how i change it?
With all these mods why don't you publish your own kernel Ezekeel?
Yusei said:
and how i change it?
Click to expand...
Click to collapse
a little get starter for u..
Code:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
wait a minute
this is a mod that the kernel builders will put in their own kernel right?
i'm so stupid
sorry guys
I guess I will have to update Spark to include all these new additions from Ezekeel. Give me a few weeks and I will try and have a bit of a toolkit ready!
Sent from my Nexus S
Edit: also, great work Ezekeel! Just a question though, what was the reason for wanting to put together your own? Is it simpler, more stable, or something else? Sorry, I haven't compared anything either, I can't easily do so on my phone.
Jonathon Grigg said:
I guess I will have to update Spark to include all these new additions from Ezekeel. Give me a few weeks and I will try and have a bit of a toolkit ready!
Sent from my Nexus S
Edit: also, great work Ezekeel! Just a question though, what was the reason for wanting to put together your own? Is it simpler, more stable, or something else? Sorry, I haven't compared anything either, I can't easily do so on my phone.
Click to expand...
Click to collapse
hey good going..
i was going to check out app dev over the weekend to get all of ezekeels mods into one app...
mind if i try?
Sent from Divinus Nexus S...
Jonathon Grigg said:
I guess I will have to update Spark to include all these new additions from Ezekeel. Give me a few weeks and I will try and have a bit of a toolkit ready!
Sent from my Nexus S
Edit: also, great work Ezekeel! Just a question though, what was the reason for wanting to put together your own? Is it simpler, more stable, or something else? Sorry, I haven't compared anything either, I can't easily do so on my phone.
Click to expand...
Click to collapse
it could be a great idea, I think.
Me, I use script, but I see a lot of people how wants to use Ezekeel Mods without knowing a thing about scripts,
or even don't know how to use terminal emulator.
thanks for this great idea.
No more question to the kernels devs about how to activate this or this...
I think many of them will be gratefull for that.
Jonathon Grigg said:
I guess I will have to update Spark to include all these new additions from Ezekeel. Give me a few weeks and I will try and have a bit of a toolkit ready!
Sent from my Nexus S
Edit: also, great work Ezekeel! Just a question though, what was the reason for wanting to put together your own? Is it simpler, more stable, or something else? Sorry, I haven't compared anything either, I can't easily do so on my phone.
Click to expand...
Click to collapse
this mod will not only enable you to modify armvolt but also intvolt.
psygbert said:
this mod will not only enable you to modify armvolt but also intvolt.
Click to expand...
Click to collapse
can any1 explain the differences??? and what is exacly each one?
yaronyud said:
can any1 explain the differences??? and what is exacly each one?
Click to expand...
Click to collapse
The ARM voltage is for the CPU, the internal voltage for the bus (and also GPU I believe). If you increase the bus/GPU speeds with LiveOC you might have to increase the internal voltages additionally to the ARM voltages to get it stable.
Made a small improvement.
Added the entries 'max_arm_volt' and 'max_int_volt' to the sysfs interface which can be used to change the maximum values allowed for the ARM and internal voltages.
Bugfix: http://www.pastie.org/2812494
Jonathon Grigg said:
I guess I will have to update Spark to include all these new additions from Ezekeel. Give me a few weeks and I will try and have a bit of a toolkit ready!
Sent from my Nexus S
Edit: also, great work Ezekeel! Just a question though, what was the reason for wanting to put together your own? Is it simpler, more stable, or something else? Sorry, I haven't compared anything either, I can't easily do so on my phone.
Click to expand...
Click to collapse
Where can I find this app of yours? Does it have a thread?
more stable Live OC?
Ezekeel said:
The ARM voltage is for the CPU, the internal voltage for the bus (and also GPU I believe). If you increase the bus/GPU speeds with LiveOC you might have to increase the internal voltages additionally to the ARM voltages to get it stable.
Click to expand...
Click to collapse
Ah!
more stable Live OC?
excessive +percentage got the phone to lose IMEI
I had my device repaired in samsung A/S center. (reentering IMEI)
and I backuped "/efs/" folder to SD, PC just in case
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
ellesshoo said:
Where can I find this app of yours? Does it have a thread?
Click to expand...
Click to collapse
[App] Spark Mod Manager - Beta 1 [5/9/2011]
Here we go - What I believe is the first custom kernel built from source for GT-N7000 ICS.
READ THIS POST INCLUDING KNOWN ISSUES BEFORE POSTING!
Driving Always For User Quality - DAFUQ!!!!
This is built by applying some small fixes to the GT-I9100 update4 source base so that the stylus and charger drivers build properly.
Source code is at: https://github.com/Entropy512/kernel_galaxys2_ics/commits/entropy_kernel_main
Initramfs git is at: https://github.com/Entropy512/initramfs_galaxynote_ics/commits/master
It has been tested so far with Criskelo's XXLPY-based release, but should work with most other Touchwiz-based N7000 ICS releases. AOSP firmwares are not supported by this kernel. They may boot and sort-of run, but no bug reports will be accepted if you're running an AOSP-based firmware. No bootloader flashing is required.
Features:
See my I777 ICS kernel thread for now - it's built off of the same source base (but N7000 users should post here)
The one specific feature I should advertise here - This is built from I9100 Update4 sources. This appears to be the only source base so far for Samsung Exynos4 kernels that doesn't carry a high risk of permanent damage to your eMMC chip. (e.g. it should be safe from all of the nightmares people have encountered with ICS leaks here, however I cannot make any guarantees.)
Known issues:
Some of you are used to kernels that autoroot a ROM for you - this one will not and never will especially now that two different Superuser packages exist. Flash SuperSU or Superuser in CWM, pick your poison.
Camera preview is black
Hardware accelerated video display is not working
Because of these known issues, the primary use for this kernel is to reset the flash counter with TriangleAway (which DOES work on this kernel)
Change Log
5/27/2012:
Pulled in some changes from the N7000 source release. Wifi and speakerphone are now working with XXLPY, however - hwaccel video is still broken.
Fixing hwaccel video requires major work or just trashing everything and starting from the N7000 source release and readding features there.
5/2/2012:
Charging now works normally. It turns out some devices have an SMB136 charger, others have an SMB328 - Now both are enabled.
4/26/2012:
Call audio fixed (Note only)
Bumped first GPU step default up to 100 MHz from 66 (Note only)
Increased conservative governor freq step from 5% to 10%
4/24/2012:
Initial release
FAQ
Q: What's up with the name?
A: Since I run CM9, this can no longer be considered my "daily driver" - so the Daily Driver name no longer really applies. I haven't picked a good name yet, expect this to change with my mood. Names may get more sensible as the mental damage caused by watching the ZOMBIE ASS trailer heals.
Something goes here...
Having issues uploading the ZIP file with EGL libs... please bear with me. XDA seems to have some silly upload timeout that makes me unable to post anything larger than 8-9 megabytes.
Find them at https://github.com/koush/proprietar.../ics/galaxys2-common/proprietary/graphics/lib for now - these go in /system/lib
Edit: Hopefully the "upload from dropbox" hack worked... not sure.
Awesome great work..
Wooohoooo!!time for note to enter the next dimension!!thank yo sooo much bro!!!
Sent from my GT-N7000 using xda premium
.zip fails to flash. installation aborted
I'll post more details and documentation later this week. I'm kinda tired now.
mikeyinid said:
.zip fails to flash. installation aborted
Click to expand...
Click to collapse
What did you flash it from? I had no problems flashing it.
The upload process from dropbox may have failed - can you manually unzip it? (Edit: Just checked, seems to be fine.)
Entropy512 said:
What did you flash it from? I had no problems flashing it.
The upload process from dropbox may have failed - can you manually unzip it? (Edit: Just checked, seems to be fine.)
Click to expand...
Click to collapse
re downloaded and it flashed fine. is this a stock kernel built from source? i mean did you uv it or add oc?
mikeyinid said:
re downloaded and it flashed fine. is this a stock kernel built from source? i mean did you uv it or add oc?
Click to expand...
Click to collapse
Hey Mikey, are you using this on stunner or did you flash off of that today? Just curious before I try it on it myself.
Sent from one of my Galaxies
skyhigh2004 said:
Hey Mikey, are you using this on stunner or did you flash off of that today? Just curious before I try it on it myself.
Sent from one of my Galaxies
Click to expand...
Click to collapse
im on lp6. it takes like 2-3 seconds for my screen to turn on when pressing the power button and noticeable lag when opening app drawer in nova. definitley didnt do those things before
lag is the wrong word. there is a stutter during transitions.
mikeyinid said:
re downloaded and it flashed fine. is this a stock kernel built from source? i mean did you uv it or add oc?
Click to expand...
Click to collapse
See the I777 thread and the git commits for what's in there.
It is in general battery-optimized - Mali 3-step defaults are battery-oriented, default governor is a tuned conservative, reduce the polling interval of it for better results.
As this is built off of I9100 sources, there might be some Note-specific things missing. I never did Gingerbread kernel development on the Note. One thing is - this should not burn out your eMMC like many of the leaks can.
Entropy512 said:
See the I777 thread and the git commits for what's in there.
It is in general battery-optimized - Mali 3-step defaults are battery-oriented, default governor is a tuned conservative, reduce the polling interval of it for better results.
As this is built off of I9100 sources, there might be some Note-specific things missing. I never did Gingerbread kernel development on the Note. One thing is - this should not burn out your eMMC like many of the leaks can.
Click to expand...
Click to collapse
its usable for sure, was definitely not saying it wasnt. cant wait to see where this goes from here. i know an ics kernel from source is probably the only thing stopping official cm build.
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
disregard the stutter post lol. went intio setcpu and changed to ondemand and this thing is butter smooth. and undervolts
mikeyinid said:
its usable for sure, was definitely not saying it wasnt. cant wait to see where this goes from here. i know an ics kernel from source is probably the only thing stopping official cm build.
Click to expand...
Click to collapse
I'm working with codeworkx and xplodwild on getting that going. I need to clean up extract-files.sh and the vendor/prop repo, among a few other things. I won't have time to work it the next few days though.
If you want to improve performance, try bumping up the GPU frequency for the lowest step and reduce its staycount to 0. For battery-saving purposes, the first GPU step is a bit on the low side. I might bump it up a little, there's a BIG jump between 66 and 100 MHz.
Instead of being 166/266 MHz, it's 66/166/266 MHz. Should improve screen-on battery life.
Entropy512 said:
I'm working with codeworkx and xplodwild on getting that going. I need to clean up extract-files.sh and the vendor/prop repo, among a few other things. I won't have time to work it the next few days though.
If you want to improve performance, try bumping up the GPU frequency for the lowest step and reduce its staycount to 0. For battery-saving purposes, the first GPU step is a bit on the low side. I might bump it up a little, there's a BIG jump between 66 and 100 MHz.
Instead of being 166/266 MHz, it's 66/166/266 MHz. Should improve screen-on battery life.
Click to expand...
Click to collapse
ok, so for ~5 seconds after you unlock the phone there is a noticeable stutter during transitions, even using ondemand.
scrolling is very smooth tho, even in plume...
Try increasing the frequency for the lowest GPU step, or reduce its staycount to 0.
Another option, try conservative but change freq_step to 15. I'm probably going to change that as the default.
Where can I find a nightly build to get initial extract-files ?
Entropy512 said:
Try increasing the frequency for the lowest GPU step, or reduce its staycount to 0.
Another option, try conservative but change freq_step to 15. I'm probably going to change that as the default.
Click to expand...
Click to collapse
seems the same using conservative with freq_step at 15. the first time you open the app drawer it stutters but the 2nd and 3rd times it get smoother til it doesnt stutter any more. turn the screen off and back on and its the same again.
---------- Post added at 09:25 PM ---------- Previous post was at 08:59 PM ----------
flashed to stunner and the stutter is even more noticable.
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
FORMAT 1:
CPU
- [FREQ1] [VOLTAGE1]
- [FREQ2] [VOLTAGE2]
- [FREQ3] [VOLTAGE3]
- ,,,
Click to expand...
Click to collapse
FORMAT 2:
CPU GLOBAL: [OFFSET]
Click to expand...
Click to collapse
I also accept 1 frequency result. You don't have to undervolt everything. I favor the last known voltage that crashes as well if you can send this I am even more happy.
Undervolted mine by 50mv
Sent from my Nexus 7 using Tapatalk 2
djjonastybe said:
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
Click to expand...
Click to collapse
In order to use "advanced mathematics" and "complex formulas".. You might want to provide a format for "the results" you want people to provide.. Without a stream of formatted data to input your "complex formulas" and "advanced mathematics" is impossible..
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
djjonastybe said:
..I will make a undervolted kernel that's stable for everyone
Click to expand...
Click to collapse
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
simms22 said:
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
Click to expand...
Click to collapse
I actually came back to post exactly this but Simms22 was too quick, as usual!
Sent from my GT-I9300 using xda premium
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
styckx said:
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
Click to expand...
Click to collapse
Might as well be honest, set him on the right track early in his dev career rather than him rely on buzzwords and fud like some people do.
These are forums for android devices, not Apple devices, the reality distortion field doesn't work here, fancy marketing terms should be left at the door.
Sent from my GT-I9300 using xda premium
My Galaxy Nexus is proof of undervolting being unstable using software while being stable with manually programming the voltages. So I am going to give this a good shot anyway.
My Galaxy Nexus uses SmartReflex to undervolt.
Look at this table I made:
https://docs.google.com/spreadsheet/ccc?key=0AuqacKmGLKJ6dEdJZG5QTmNtQnoyYk0zbm5IanluMHc#gid=1
You see the core or gpu was already crashing at 974mV, which was the reason why I stopped undervolting using the thread. But don't give up, I tried again using SmartReflex because I felt I should be able to get lower. And now I am at 911mV but I did not try to get lower yet.
I plan on undervolting by actually programming it. I don't know how you guys undervolt for the Nexus 7, since I am fairly new with this device.
READ FIRST POST for formatting
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Student's_t-distribution
Using that I can calculate which voltage to take that will work for 90% of us or 99% of us or maybe 100% ?
For that I need some results. The more the better.
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
nodstuff said:
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
^^ Truth
I've done a bit of pc overclocking over the years and we'd always seek out the best steppings to find cpu batches that would give a better clock speed for less volts. What would work on one person's cpu wouldn't work on another sometimes even within the same stepping. (My current machine is getting long in the tooth but it's running a 33% OC below stock volts and stable as a rock.)
When the N7 cpu's are tested the stock voltage is the point where 100% of them will run without issue. Certainly there are many, maybe even most N7's that will run undervolted but until you try it you just won't know. Undervolting needs to be done on a case by case basis.
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
sorry to break the fun lol
Opened a thread with undervolting settings in different situation. For now i think its the lowest possible
bervin said:
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
Click to expand...
Click to collapse
That's exactly the same as what I have done. 100mV right across the board, and I have also never had a reboot or any other negative effect from doing it. Just a bit more battery life.
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
phonic said:
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
Click to expand...
Click to collapse
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
davidoff59 said:
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
Click to expand...
Click to collapse
When either OCing or UVing, you should ALWAYS test out the changes prior to saving them as a persistent boot state. This way, if you set something too high/low and it proves to be unstable, if you restart the device it will revert back to normal.
In the event that you OC/UV too much, yes, you would see signs of instability. In some cases it could show up as soon as you applied to change, in other cases it could take a while to notice. For example, some games or other high processing powered activities could FC/crash. Or your tablet might freeze or reboot. But again, as long as you didn't save your changes as a boot setting, it will be fine once it reboots.
In the event that you did save it, and the settings were unstable for your device, you could boot up into recovery and then manually erase them from taking effect. Recovery doesn't use those settings, as it's technically a different OS. But that can be complicated a process for some. So test test test save. Or don't save and just apply them manually.
Two other points:
Yes, most (all?) devices do have safeguards to protect itself against permanent hardware damage from OC/UVing. If it gets too hot, they will often shut down to protect themselves.
And just because one device can handle being OC'd or UV'd to a certain level doesn't mean they all can. Very minor differences in each component can impact one devices ability from another. The manufacturers only test to see if they can handle the published speeds/etc., but in many cases they can go higher if set to. In others, not so much.
Thanks for that phonic. Given the range of ROMs and kernel's available and the improvements already built in, under volting may not help a lot but every bit helps. Eg this screen on time is pretty good.Close to six hours screen on time with iirc 35% battery remaining.
Paranoid android with motley kernel. I don't over clock the nexus 7 as its fast enough. In fact I under clocked it to 1000 MHz max before and it was still fast but the screenshots are at stock volts and speeds.
it's actually plain simple. If everyone posts results. I can make a kernel with voltages that work for 75% of all people or maybe for 95% of all Nexus 7 owners.
It's called mathematics. But to do that I need as much results as possible.
Easy to do if you know what you are doing, right ?
http://en.wikipedia.org/wiki/Confidence_interval
Hello,
Just curious if folks have started testing with this app. I am using version Tegra Overlock 1.5.1 (newer versions don't open for me.) I've read of folks overclocking the GPU up to 520 Mhz which leads me to believe the default clock speeds CPU and/or GPU may be underclocked. Also it looks as though the Extras are not enabled by default. I know there is currently no custom Kernel which is ideal for overclocking but I'm just surprised there isn't a thread for this as I feel there should be a starting point and I think there is a stable performance gain that can be achieved with just the app and the basics (custom ROM, root etc.)
Please post here with any results you've had using this app. Also, would be very interested in the version of XBMC you're using and any noticeable improvements.
I'm on StockPlus, XBMC Alpha 6. When I clock the GPU to 520 it definitely seem to run noticeably faster but a video I was watching crashed after a couple minutes and XBMC closed down entirely. Watched the same movie at the default GPU, extras enabled and it didn't crash once.
Thanks!
Pretty sure the default GPU speed is already 520Mhz.
brandogg said:
Pretty sure the default GPU speed is already 520Mhz.
Click to expand...
Click to collapse
i don't think so...If you google and read the Specs for the OUYA it says "Nvidia GeForce ULP @ 520 MHz (12.48 GFLOPS) " for the GPU but i can tell you that the Default GPU clock speed was not 520Mhz it was around the 200Mhz, i've been messing with this "Tegra Overclock" app for 2 months now and i can tell you that it works and speeds things up...you can do a lot of things with this app and offers lots of features, This is how i have it set up, i got FPS(Frames per Second) locked to 60fps all the time, GPU clocked to 520Mhz that's all ...i use a different app to control the CPU clock speed, the only version of "Tegra Overclock" app that works for me so far is v1.5.1 but for some reason the screen shrinks down but also v1.5.7 works and it fits the screen perfect...Any version from 1.6.x and up don't work for some odd reason...
cronikman84 said:
i don't think so...If you google and read the Specs for the OUYA it says "Nvidia GeForce ULP @ 520 MHz (12.48 GFLOPS) " for the GPU but i can tell you that the Default GPU clock speed was not 520Mhz it was around the 200Mhz, i've been messing with this "Tegra Overclock" app for 2 months now and i can tell you that it works and speeds things up...you can do a lot of things with this app and offers lots of features, This is how i have it set up, i got FPS(Frames per Second) locked to 60fps all the time, GPU clocked to 520Mhz that's all ...i use a different app to control the CPU clock speed, the only version of "Tegra Overclock" app that works for me so far is v1.5.1 but for some reason the screen shrinks down but also v1.5.7 works and it fits the screen perfect...Any version from 1.6.x and up don't work for some odd reason...
Click to expand...
Click to collapse
Thanks for that information! :good:
I upgraded to 1.5.7, much easier to work with now and more options than 1.5.1.
I tried running 1.5.9 but it won't open so looks like this is the highest version it will work with.
What settings do you use for the Thermal Guard?
Have you tinkered with any of the other options? For some reason I can't get the Extras to save ex. Tegra Prism Technology enabled, even when I save on boot the setting doesn't appear to save. Tried rebooting, still showing as "currently disabled". Any suggestions?
Which app are you using for the CPU clock speed and what are your settings?
Tested with the game Ravensword on your settings and it's running super smooth, no lag.
Many thanks!
I talked to the developer of the app and he says you shouldn't use this right now he's got a special version coming out for the ouya.
Asadullah said:
I talked to the developer of the app and he says you shouldn't use this right now he's got a special version coming out for the ouya.
Click to expand...
Click to collapse
nice to know that but for now best bet would be to just include the propper values into an ini script in init.d
when it comes to overclocking, fixed fps etc. the app doesn't do anything else but setting values in config files.
BlissfulBeast said:
Thanks for that information! :good:
I upgraded to 1.5.7, much easier to work with now and more options than 1.5.1.
I tried running 1.5.9 but it won't open so looks like this is the highest version it will work with.
What settings do you use for the Thermal Guard?
Have you tinkered with any of the other options? For some reason I can't get the Extras to save ex. Tegra Prism Technology enabled, even when I save on boot the setting doesn't appear to save. Tried rebooting, still showing as "currently disabled". Any suggestions?
Which app are you using for the CPU clock speed and what are your settings?
Tested with the game Ravensword on your settings and it's running super smooth, no lag.
Many thanks!
Click to expand...
Click to collapse
:good: I'm glad my settings worked for you...i haven't messed around with the "Thermal Guard" feature yet, i also can't get the extra setting to stick on boot and i've tried every version of "Tegra Overclock" available and i can't get extra setting to save so i'm on the same boat as you...As for the CPU i use nothing special but No Frills CPU Control app, why do i use No Frills CPU Control and not the "Tegra Overclock" to control the CPU is because the CPU feature on "tegra overclock" won't set the clock speed you choose, it will just set its own clock speed so i just don't use that feature and No Frills CPU Control sets what ever clock speed i want...another feature i think is amazing Tegra Overclock is "Core Count" but it doesn't work right, i set it to activate only 2 cores on boot and it slowed down my OUYA hard meaning real SLOW the OUYA didn't like it at all so i set it back to activate all 4 cores...i hope they are really making a version of Tegra Overclock for the OUYA :fingers-crossed:...
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
i can install Tegra Overclock 1.6.x+ on my OUYA and the app opens, but when i select CPU it does nothing so then i select GPU and again NOTHING,so then i select Core Count, Extras and still NOTHING!!...
update from app dev
I asked about ouya support for the overclock app and here is what i just got back.
"We are a little busy right now but yes we have the device and are working on it. It should get ready by October's end or maybe even before that. Just want to make the OUYA version have that exclusive feel that we are looking forward to... Just a little wait remains "
.. and .. dont try to push it beyond 520 .. mine is suddenly freeze right after apply the value .. watchout ..
metalman3797 said:
I asked about ouya support for the overclock app and here is what i just got back.
"We are a little busy right now but yes we have the device and are working on it. It should get ready by October's end or maybe even before that. Just want to make the OUYA version have that exclusive feel that we are looking forward to... Just a little wait remains "
Click to expand...
Click to collapse
This is GREAT news! Thank you for the update! Even at 520 I've noticed HUGE improvements, particularly in the gameplay for games. It's like night and day. I can only image what an Ouya exclusive version will be capable of. Very excited for this. Thanks again! :victory:
BlissfulBeast said:
This is GREAT news! Thank you for the update! Even at 520 I've noticed HUGE improvements, particularly in the gameplay for games. It's like night and day. I can only image what an Ouya exclusive version will be capable of. Very excited for this. Thanks again! :victory:
Click to expand...
Click to collapse
.. yep .. give more fps .. tested on asphalt 8 at high setting .. since custom kernel is not available yet .. this is the only thing to pumping ouya performance ..
Please post if you have news regarding this app. Thanks
Ipse_Tase said:
Please post if you have news regarding this app. Thanks
Click to expand...
Click to collapse
nope, no news yet that i know off...
Can over clock improve video play?Like XBMC......
What issues are you experiencing/expecting?
Gesendet von meinem HTC One X+ mit Tapatalk-4
This app made Ravensword playable! If it can increase performance like it does in it's current state, then I can't wait to see what an OUYA optimized version would do.
philburkhardt said:
This app made Ravensword playable! If it can increase performance like it does in it's current state, then I can't wait to see what an OUYA optimized version would do.
Click to expand...
Click to collapse
Guys...how did you install it and what version? I tried 1.6.5a and it doesn't even show the CPU clock.
Ipse_Tase said:
Guys...how did you install it and what version? I tried 1.6.5a and it doesn't even show the CPU clock.
Click to expand...
Click to collapse
It's 1.6.5a. I purchased it from the Play Store on my PC, and sent over to my OUYA. My OUYA shows up in my list of devices on the Play Store, and I can purchase and send apps to it like any of my other android devices. I only have the GPU overclocked and the FPS locked at 60, but I was able to get into the CPU clock settings without issue.
philburkhardt said:
It's 1.6.5a. I purchased it from the Play Store on my PC, and sent over to my OUYA. My OUYA shows up in my list of devices on the Play Store, and I can purchase and send apps to it like any of my other android devices. I only have the GPU overclocked and the FPS locked at 60, but I was able to get into the CPU clock settings without issue.
Click to expand...
Click to collapse
Wow...that's a mystery. I have the exact same setup and when I fire the app, it shows the GUI with different selections, but none of them works. Not even the CPU graph bars.
Not sure what the difference is...I run StockPlus 519r2 if that matters.
Ipse_Tase said:
Wow...that's a mystery. I have the exact same setup and when I fire the app, it shows the GUI with different selections, but none of them works. Not even the CPU graph bars.
Not sure what the difference is...I run StockPlus 519r2 if that matters.
Click to expand...
Click to collapse
i can tell you this, the v1.6.5a didn't work on the old update, the only ones that worked was where you can set things up was on the the v1.5.1-v1.5.7, now v1.6.5a must work on OUYAS last update....
---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------
Ipse_Tase said:
Wow...that's a mystery. I have the exact same setup and when I fire the app, it shows the GUI with different selections, but none of them works. Not even the CPU graph bars.
Not sure what the difference is...I run StockPlus 519r2 if that matters.
Click to expand...
Click to collapse
i don't think this app works on stock plus, if anything try one of the old versions first like v1.5.1 or 1.5.7...
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
Ipse_Tase said:
Wow...that's a mystery. I have the exact same setup and when I fire the app, it shows the GUI with different selections, but none of them works. Not even the CPU graph bars.
Not sure what the difference is...I run StockPlus 519r2 if that matters.
Click to expand...
Click to collapse
cronikman84 said:
i can tell you this, the v1.6.5a didn't work on the old update, the only ones that worked was where you can set things up was on the the v1.5.1-v1.5.7, now v1.6.5a must work on OUYAS last update....
---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------
i don't think this app works on stock plus, if anything try one of the old versions first like v1.5.1 or 1.5.7...
Click to expand...
Click to collapse
then try an earlier version...
First time posting here. And first time user of custom ROMs.
I recently unlocked my Incredible S and flashed VivoKat 4.4 by szezso on it. It is a nice build and most things work in beta quite well; however, I don't have permissions to post on that board to report bugs and ask other build related questions, like how is battery life compared to other ROMs.
I noticed I barely get 1 battery charge per day, whereas I used to get 2 days with my old gingerbread.
So I was wondering if I should go with an older ROM, feature complete, that might have better battery life. If so, which build do you recommend?
Thanks
PS: to the guys on the VivoKat thread (since I can't post there), here are some of the bigger bugs I found:
- microphone doesn't work on speaker mode
- physical buttons don't work if you disable touch-vibration on them
- main screen icons/shortcuts disappear from time to time if the apps crash
Question:
- to install today's update of VivoKat do I need to wipe everything (all data) and flash the new version, or can I update without wiping everything clean?
- I have the full "ROM manager" app, but it doesn't find updates for this build. Will that be available at some point?
(I really like the look of 4.4 on this custom ROM so it's be nice to help out with finding bugs - good work szezso)
goodrix said:
First time posting here. And first time user of custom ROMs.
I recently unlocked my Incredible S and flashed VivoKat 4.4 by szezso on it. It is a nice build and most things work in beta quite well; however, I don't have permissions to post on that board to report bugs and ask other build related questions, like how is battery life compared to other ROMs.
I noticed I barely get 1 battery charge per day, whereas I used to get 2 days with my old gingerbread.
So I was wondering if I should go with an older ROM, feature complete, that might have better battery life. If so, which build do you recommend?
Thanks
PS: to the guys on the VivoKat thread (since I can't post there), here are some of the bigger bugs I found:
- microphone doesn't work on speaker mode
- physical buttons don't work if you disable touch-vibration on them
- main screen icons/shortcuts disappear from time to time if the apps crash
Question:
- to install today's update of VivoKat do I need to wipe everything (all data) and flash the new version, or can I update without wiping everything clean?
- I have the full "ROM manager" app, but it doesn't find updates for this build. Will that be available at some point?
(I really like the look of 4.4 on this custom ROM so it's be nice to help out with finding bugs - good work szezso)
Click to expand...
Click to collapse
That's the actual battery life. With each new android version, you have a lot more processes running in the background. A lot more Google processes too
It should be ok to just flash the update, but if you run into bugs, don't report them as developers don't have a way of telling whether its from issues caused from dirty flash or from the actual ROM itself.
No it will never be available in the ROM manager app. ROM Manager does not search XDA for ROMs and VivoKat is ported by Szeszo personally.
Thanks.
That answers my questions.
And battery life improved after turning off "Location"
You can also log-out from different accounts such as fb, and so one. some of apps are eating battery. For example some email clients...
moreover, you can turn off wifi
you use Vivokat as your daily driver, that one seems still in beta stage
according to my search, i have see many kernel of the ROM is overclock feature.
but the overclock is power consumption.
for now i have using the cyanvivo,
i de-overclock his GPU and it seems become normal.
otakux said:
according to my search, i have see many kernel of the ROM is overclock feature.
but the overclock is power consumption.
for now i have using the cyanvivo,
i de-overclock his GPU and it seems become normal.
Click to expand...
Click to collapse
Overclocking uses more battery because of both freq and voltage
Simple equation is this
Power used= freq * voltage^2
So if you lower the voltage to the same as the prev max freq, then you will be using more power still. Just fyi cause I don't think it's ever been brought up around here
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Overclocking uses more battery because of both freq and voltage
Simple equation is this
Power used= freq * voltage^2
So if you lower the voltage to the same as the prev max freq, then you will be using more power still. Just fyi cause I don't think it's ever been brought up around here
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
according to my test, i just lower the frequency to the normal.
and it actually consume less power.
so de-overlock is work for me.
otakux said:
according to my test, i just lower the frequency to the normal.
and it actually consume less power.
so de-overlock is work for me.
Click to expand...
Click to collapse
Voltage changes should make a lot of difference too. But not as evident on the vivo as on big quad core snapdragons
The Gpu oc is not really overclock, it's forcing to 245mhz to up performance
Sent from my HTC One using XDA Premium 4 mobile app
i did not explain my kernel.
the kernel that i using is default overclocking.
my work just tweak it to the normal.
before tuning, in idle situation, one day could consume a battery.
after tuning, a battery could use more than one day.
i just want it back to normal.
i do not know that it is really OC, but according to my test.
the frequency is actually higher that it default.
up to 353Mhz, default is 245M.
so i could sure it is overclocking.
this data is collected in it's kernel, the real runtime data.
otakux said:
i did not explain my kernel.
the kernel that i using is default overclocking.
my work just tweak it to the normal.
before tuning, in idle situation, one day could consume a battery.
after tuning, a battery could use more than one day.
i just want it back to normal.
Click to expand...
Click to collapse
Ahh, so you've got the stock acpuclock freq table I get it
You have git public so we can understand?
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Ahh, so you've got the stock acpuclock freq table I get it
You have git public so we can understand?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
my work just tweak back the GPU, not CPU.
i am still think that i need to tweak the CPU back to normal or not.
because i did not ask the author that i could post or not.
now the code just store in my computer.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
this is the original kernel that i used.
tesco kernel
https://github.com/szezso/T.E.S.C.O-kernel_vivo
otakux said:
my work just tweak back the GPU, not CPU.
i am still think that i need to tweak the CPU back to normal or not.
because i did not ask the author that i could post or not.
now the code just store in my computer.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
this is the original kernel that i used.
tesco kernel
https://github.com/szezso/T.E.S.C.O-kernel_vivo
Click to expand...
Click to collapse
kernel code is GPL, if you got it from a publicly available source then no permissions really needed
If you come up with anything that you think may be beneficial.. maybe me or @szezso can work on integrating it or you can post it somewhere
poondog said:
kernel code is GPL, if you got it from a publicly available source then no permissions really needed
If you come up with anything that you think may be beneficial.. maybe me or @szezso can work on integrating it or you can post it somewhere
Click to expand...
Click to collapse
OK, i will.
the most benefit thing to me for now is to create other branch that did not overclock the GPU.
it will help solve the battery consume problem.
And split the kernel version, i need to manually search commit to find the cm 10.2's kernel.
otakux said:
OK, i will.
the most benefit thing to me for now is to create other branch that did not overclock the GPU.
it will help solve the battery consume problem.
And split the kernel version, i need to manually search commit to find the cm 10.2's kernel.
Click to expand...
Click to collapse
Coolies
The CM 10, 10.1, 10.2, 11 kernels are built from the same source
poondog said:
Coolies
The CM 10, 10.1, 10.2, 11 kernels are built from the same source
Click to expand...
Click to collapse
yes, but now the newest master is a beta version branch.
building that kernel will causing error.
you maybe need to post which the commit url that the cm version is using
by the way, i also patch another new feature in my kernel.
otakux said:
yes, but now the newest master is a beta version branch.
building that kernel will causing error.
you maybe need to post which the commit url that the cm version is using
by the way, i also patch another new feature in my kernel.
Click to expand...
Click to collapse
Maybe the git is not up to date, have not tried compiling his CM kernel, or any vivo kernel for that matter for MONTHS
What is the error? And what is this feature
poondog said:
Maybe the git is not up to date, have not tried compiling his CM kernel, or any vivo kernel for that matter for MONTHS
What is the error? And what is this feature
Click to expand...
Click to collapse
i have compile the newer code.
the error is after boot, nothing show on the screen.
feature is about disk IO, know as BFQ.
it could use just by apply patch, no need to change code by manually
otakux said:
i have compile the newer code.
the error is after boot, nothing show on the screen.
feature is about disk IO, know as BFQ.
it could use just by apply patch, no need to change code by manually
Click to expand...
Click to collapse
Oh nice. I do have the best results on my One with fiops, deadline, row though
poondog said:
Oh nice. I do have the best results on my One with fiops, deadline, row though
Click to expand...
Click to collapse
yep, but according to my linux desktop test, bfq is more better than cfq.