[KERNEL][UBERTC 5.0]Despair Kernel R1 - YU Yureka Original Android Development

This is the home of the new refined Despair Kernel. If you submit bug reports without a log, you may be prosecuted... or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Features:
UBERTC 5.0
O3, Graphite & Miscellaneous Optimizations
Extra CPU Governors & IO Schedulers
Advanced TCP Congestion
Links:
Pushbullet: https://www.pushbullet.com/channel?tag=despairfactor
Downloads: http://renderserver.net/devs/DespairFactor/
Source:
Github: https://github.com/RIPng/Despair-yu
Yureka Forums: http://forums.yuplaygod.com/threads/kernel-despair-kernel.4648/
Changelog:
R1
Code:
Rebase to CM code
Initial release
Credits:
faux123
Google
CyanogenMod
imoseyon
Cl3Kener
LoungeKatt
Zyxxeil
TheShoxter

working very well sir.
Very excited to see you sir in YU yureka development forum.
Intelliplug working very well.
Thanks for adding new governor and I/O..

:good::good:

Have tested the kernel on dumtara's CM11 build, Very stable with all the features working very well and smooth. Used kernel Aduitor app to tune kernel parameters and to verify things like core plugging features. Daily Driver :good:

By any chance is it possible to enable screen color calibration with the help of kernel?

Jimmyz0r said:
By any chance it is possible to enabled screen color calibration with the help of kernel?
Click to expand...
Click to collapse
It is, I would have to look at the drivers for it and see if they are compatible on this device or not. If they are I can get it added.

Confused?
thnku sir i am running stock firmware 11.0-XNPH05Q .i have unlocked bootloader and rooted my device so simply i have to flash it?

jghiya said:
thnku sir i am running stock firmware 11.0-XNPH05Q .i have unlocked bootloader and rooted my device so simply i have to flash it?
Click to expand...
Click to collapse
Yes

Need This Features in Kernel
IO schedulers
FLOPS
CPU GOVERNERS
SMART ASS V2
SMOTHASS

ela1103 said:
Need This Features in Kernel
IO schedulers
FLOPS
CPU GOVERNERS
SMART ASS V2
SMOTHASS
Click to expand...
Click to collapse
FIOPS is already there, those two governors are not worth merging

DespairFactor
Thank you for The New Kernel .We are all expecting more Feature
---------- Post added at 11:20 PM ---------- Previous post was at 11:15 PM ----------
DespairFactor said:
FIOPS is already there, those two governors are not worth merging
Click to expand...
Click to collapse
why that two governors not worth

ela1103 said:
DespairFactor
Thank you for The New Kernel .We are all expecting more Feature
---------- Post added at 11:20 PM ---------- Previous post was at 11:15 PM ----------
why that two governors not worth
Click to expand...
Click to collapse
AFAIK its because the governors were built for single core devices during the ICS period. Those governors have poor performance handling over multicore architecture. Correct me if i am wrong.

Does this kernel enables quick charging 2.0. does it improves the charging speed

janajackie said:
Does this kernel enables quick charging 2.0. does it improves the charging speed
Click to expand...
Click to collapse
Quick charging is not based solely on kernel, the battery must be able to accept it, I do not wish to up the amperage going to the battery at this time. It is not exactly safe and we don't know the limits of the device's battery yet, I would hate for you to wake up with your battery exploded.

its good to see development of this kernel going on a great pace.

Your opinion pls
Thank you for the kernel,
@DespairFactor........ Just curious to know what Cpu governor and I/o scheduler combo you would suggest for a user who is not much into gamig but heavy 3g web browsing and music fanboy.
I need good battery life.
Thank you once again and keep up the good work sir... :good:

[email protected] said:
Thank you for the kernel,
@DespairFactor........ Just curious to know what Cpu governor and I/o scheduler combo you would suggest for a user who is not much into gamig but heavy 3g web browsing and music fanboy.
I need good battery life.
Thank you once again and keep up the good work sir... :good:
Click to expand...
Click to collapse
From my experience. Ondemand/noop with min/max frequency at 400Mhz/1036Mhz gives good battery backup. Make sure you enable the core plugging option.

PRRash said:
From my experience. Ondemand/noop with min/max frequency at 400Mhz/1036Mhz gives good battery backup. Make sure you enable the core plugging option.
Click to expand...
Click to collapse
Core plugging means? intelli Plug feature?

[email protected] said:
Core plugging means? intelli Plug feature?
Click to expand...
Click to collapse
Yes.. Use the app Kernel Aduitor from playstore. Does the job pretty neat.
---------- Post added at 04:50 PM ---------- Previous post was at 04:41 PM ----------
DespairFactor said:
Quick charging is not based solely on kernel, the battery must be able to accept it, I do not wish to up the amperage going to the battery at this time. It is not exactly safe and we don't know the limits of the device's battery yet, I would hate for you to wake up with your battery exploded.
Click to expand...
Click to collapse
Not even sure if the Soc has the feature for this device. Any way to figure that up??, On S3 mini i could check the receiving current Amps to verify using an app.??
615 Soc spec says its available within, But under devices section yureka is not mentioned on the Qualcomm website for QuickCharge. AFAIK i know nexus 6 with bigger battery, charges faster.

PRRash said:
Yes.. Use the app Kernel Aduitor from playstore. Does the job pretty neat.
---------- Post added at 04:50 PM ---------- Previous post was at 04:41 PM ----------
Not even sure if the Soc has the feature for this device. Any way to figure that up??, On S3 mini i could check the receiving current Amps to verify using an app.??
615 Soc spec says its available within, But under devices section yureka is not mentioned on the Qualcomm website for QuickCharge. AFAIK i know nexus 6 with bigger battery, charges faster.
Click to expand...
Click to collapse
On nexus 6 our battery has extra components to allow for the amperage provided by the quick charge chargers. The SoC can have features, but if the OEM doesn't enable them with the components or code required it won't work. We have LED on Nexus 6 for example, but it doesn't blink, this is because it was not coded to work.

Related

[KERNEL][ICS]JARVIS-v8 for LGP990

JARVIS Kernel for LGP990
Only for CM/Miui or AOSP roms​
Deceided that XDA needs a thread too. I won't look through it really often. I hope that other more experienced members can answer some easy questions, so I can focus on developing things.
Features:
3.0.y Kernel
Interfaces to control a bunch of Features (Like vibration strength)
Overall optimized parameters to provide a smooth user experience
working UMS - thanks Harsh
App which controls all the interfaces
Disclaimer:
I'm not responsible if your phone is fried by the kernel or you miss some important phone call! I'm not forcing you to install this Kernel and so it isn't my fault.
Download:
Download
Or Update via my app:
​
Don't use profiles, because they can lead to instabilities.. and they're unnecessary.
Stay away from SetCPU or any other app. Could lead to problems because of the customizable OC. Wait for my app until it's not ready use command line coupled with a init.d script.
You don't need to optimize any values in the ram disk. It should work perfectly without any other tweaks.
When you experience problems like random reboots, SODS, etc. try to go back to stock settings. And apply my 1 GHz frequency table. If this isn't fixing your problems report a bug with detailed informations. Like ROM, Settings, etc.
If a person reported a bug and you experienced it too, +1 this bug report or whatever. In this case I know that the bug isn't only happening on one specific device.
Changelog:
I'm damn lazy. So just use my github commit history (here).
Source Code:
Github
Thanks to:
Dekudan/Victor Von Zeppelin - for creating awesome icons for the app
Arcee - Setting up CyanogenMod and everything.. Just awesome
wkpark - for his cherry-pick marathon.. This guy really has endurance hehe
Ezekeel - Really innovative dev with impressive ideas.
Everyone who open sourced their work
Interfaces:​
CPU Control:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Used to set the minimum frequency.
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Used to set the maximum frequency.
​
Fsync Control:
/sys/class/misc/fsynccontrol/fsync_enabled (Read and Write)
Enable/disable single file/filessystem sync.
WARNING: This could lead to potential data loss after a unwanted reboot (battery pull)
enable=1, disable=0 (default enabled)​
Vibrator Control:
/sys/class/misc/vibratorcontrol/vibrator_strength
Set the vibration strength.
possible values: 1500-3600​
Force Fast Charge:
/sys/kernel/fast_charge/force_charge_mode
changes the usb charging mode. We have 3 modes:
Fast - Forces fast AC charging. Disable data transfer!
Slow - Always charges slow (like on a normal PC USB bus)
Auto - automatical detects which mode should be set.
Possible values: fast=1, slow=2, auto=0​
Example
Use adb to connect to your device and then in adb shell (with su) (you can setup a init.d script to auto apply everything)
We want more vibration because we can hardly notice it and want to pwn our friend with benchmarks. Additionally we want to charge our device faster.
Code:
echo 3500 > /sys/class/misc/vibratorcontrol/vibrator_strength
echo 1 > /sys/kernel/fast_charge/force_charge_mode
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
And that's it
reserved2
Ics only right? cool stuff man I'll give it a try
Verstuurd van mijn Optimus 2X met Tapatalk
awesome, benee
Thanks!
Sent from my LG-P990 using xda premium
Hi
Installed and testing over half day. Until now seems to be a quite good kernel. No problems, no bsod. Battery drain its difficult to tell now
Tnx for new kernel.
Sent from my Tapatalk
great kernel!
I've use it since JARVIS-1
most stable one for me so far.
works fine so far !
looking forward to your kernel control app !
Awesome post! Thanks for sharing.
Really fast Kernel.
Two Screenshots with 1,4GHz and 1,2GHz.
Sent from my LG-P990 using XDA Premium App
Edit:
Your going to update your Sources to 3.0.32?
zerocoolriddler said:
Really fast Kernel.
Two Screenshots with 1,4GHz and 1,2GHz.
Sent from my LG-P990 using XDA Premium App
Edit:
Your going to update your Sources to 3.0.32?
Click to expand...
Click to collapse
Later. Doesn't benefit so much and only clutters the git history. (I don't like to squash the commits)
zerocoolriddler said:
Really fast Kernel.
Two Screenshots with 1,4GHz and 1,2GHz.
Sent from my LG-P990 using XDA Premium App
Edit:
Your going to update your Sources to 3.0.32?
Click to expand...
Click to collapse
damn... really fast. grats benee
---------- Post added at 01:41 PM ---------- Previous post was at 01:35 PM ----------
zerocoolriddler said:
Really fast Kernel.
Two Screenshots with 1,4GHz and 1,2GHz.
Sent from my LG-P990 using XDA Premium App
Edit:
Your going to update your Sources to 3.0.32?
Click to expand...
Click to collapse
damn, it really is fast, never seen any kernel score so high when it comes to cpu, just need a lil I\O tweaking and its perfect. i think
I think CPU and Mem is more important than I/O, but not so easy to do.
skylinegt77 said:
damn, it really is fast, never seen any kernel score so high when it comes to cpu, just need a lil I\O tweaking and its perfect. i think
Click to expand...
Click to collapse
It's pretty much io tweaked. If you want more disable fsync (interface)
zerocoolriddler said:
I think CPU and Mem is more important than I/O, but not so easy to do.
Click to expand...
Click to collapse
When I finished my app I will work on live gpu oc and maybe a ram only oc is possible (havn't looked deeply into it and the stuff what we can do easily is damn limited)
CM7 support?
CM9
---------- Post added at 03:10 PM ---------- Previous post was at 03:04 PM ----------
Benee said:
It's pretty much io tweaked. If you want more disable fsync (interface))
Click to expand...
Click to collapse
How to disable this? I´m not able to do it. Tried it via Console and Estrong File Explorer but always changes back to 1 after a Reboot.
zerocoolriddler said:
CM9
---------- Post added at 03:10 PM ---------- Previous post was at 03:04 PM ----------
How to disable this? I´m not able to do it. Tried it via Console and Estrong File Explorer but always changes back to 1 after a Reboot.
Click to expand...
Click to collapse
that is the way sysfs works
you will need to make a init.d script for it so it will set the values at boot time
or just wait for the app
Benee said:
It's pretty much io tweaked. If you want more disable fsync (interface)
When I finished my app I will work on live gpu oc and maybe a ram only oc is possible (havn't looked deeply into it and the stuff what we can do easily is damn limited)
Click to expand...
Click to collapse
not only that, if you try to change it in sys it will never even save the changes to the file, we gotta do it sumwhere else
+ im waiting 4 the app coz from what i saw it apears to be really great
PAIIITET said:
CM7 support?
Click to expand...
Click to collapse
I flash the kernel on cm7 and the phone do not appear usb storage when link to pc.
It can boot on cm7.
rexren said:
I flash the kernel on cm7 and the phone do not appear usb storage when link to pc.
It can boot on cm7.
Click to expand...
Click to collapse
i had to change some things in my rom to support UMS on 3.0.y kernel (since it differs really alot from 2.36.x kernel) i think that is the cause

[KERNEL] Gamma Custom Kernel XT890 (Version 6.0.2, Linux 3.0.101+)

DESCRIPTION
So this is a cooked RazR i boot.img that contains a custom compiled Kernel for our device, it was patched to be kept up to date and has some changes to help on battery savings, plus some cpu-freq drivers which which help our device a lot.
InteractiveX2 CPU Governor -- Like Interactive, and fine tweaked to only jump to 1.8 GHz on lighter/faster load increases, comes with a screen-off profile to lock down the frequency and offlinining of the rest of the CPU's defined as non-boot -- being an SMT processor this makes it easier to get the phone to deep sleep even when it wakes up to do something by reducing the complexity of the system.
Conservative CPU Governor -- Similar to ondemand. However, before the governor takes this lower frequency and slower clocked in the upper area, which has positive effects on the battery life.
Ondemand CPU Governor (Re)added -- it was originaly on ICS stock Kernel, it adjusts the CPU frequency to the given requirements, however quickly clocked in the upper frequency range to ensure smooth working.
Performance CPU Governor -- this will clock the CPU frequency to the top, not recommended for prolonged use.
SimpleIO Scheduler (Default) -- is a mixture of Noop & Deadline and one of my favorites.
V(R) IO Scheduler -- is the best scheduler for benchmarks, in everyday use can become unstable.
BFQ IO Scheduler -- A proportional-share storage-I/O scheduler that also supports hierarchical scheduling with a cgroups interface with Low latency and high throughput.
ROW IO Scheduler -- This one is very battery friendly and now my favorite for mobile decies by it's simplicity and responsiveness.
It is known to work on stock & stock based ROM's (such as this one where it is included).
As of other differences there are a lot of GNU compiler flags optimizations, by knowing that the compiler wouldn't know some vital information since it is a remote target different than from where I am compiling so I decided to be pretty explicit.
DOWNLOADS
[For Motorola's Android 4.4 KitKat, unsure if this works at the moment]
boot.custom.gamma_v6.0.2.img
[For Motorola's Android 4.1 JellyBean]
boot.custom.gamma_v5.0.2.img
boot.custom.gamma_v3.0.0.img
boot.custom.gamma_v2.2.1.img
boot.custom.gamma_v1.8.0.img
SOURCE
XT890-Kernel-Gamma GitHub Source
NOTES
For more information regarding governors, schedulers, modules, etc visit this thread by forum member droidphile.
This is my personal experience to other people on compiler flags, if you guys want to try -O3 straight ahead you will face issues on battery readings unless you remove the -ftree-vectorize flags on the battery modules that get compiled.
[IMPORTANT] For changing the CPU governor please use No-frills CPU Control, Since other apps such as SetCPU and AnTuTu CPU Master both only change CPU0 and may cause conflicts.
INSTRUCTIONS
You MUST be unlocked, and to take full advantage of other modules it is recommend to be rooted.
I will put something more descriptive here, but you can flash it with fastboot by doing: fastboot -i 8888 flash boot <boot.img>.
THANKS TO OTHERS
First of all thanks to Matorola/Intel for putting the main source and for Turl on giving me some info when unpacking/packing the boot images. Also to mattlgroff for the tutorial on unlocking the phone, more thanks to imoseyon and Mike Chan for providing the interactiveX2 source code and changes, it it is now my favorite CPU governor and also to HSD-Pilot for posting this originally on another forum -- I based my formatting from his post.
<< If you like my work here is my hat, please donate! >>​
​
<< And thanks to you guys for the support and help >>​
So is this kernel designed for speed or battery life, or a mixture of both?
Also will this work on the 91.2.26001 JB.EU rom?
cuben said:
So is this kernel designed for speed or battery life, or a mixture of both?
Also will this work on the 91.2.26001 JB.EU rom?
Click to expand...
Click to collapse
By default for a mixture of both. But can be further chose different governors and parameters of the governors for different choices for the user. You can for example choose conservative governor and get more battery life and less performance.
And yes It can be used on that ROM. :good:
It works on jelly bean alright... but with this I'm missing the features of the Arman AIO boot v4 and I just can't live without it...
Updated the OP, added SavagedZen CPU governor.
Omar-Avelar said:
Updated the OP, added SavagedZen CPU governor.
Click to expand...
Click to collapse
Any changelog will be great , last version 1.4 now 1.7 its only "added SavagedZen CPU governor"?
skupi20 said:
Any changelog will be great , last version 1.4 now 1.7 its only "added SavagedZen CPU governor"?
Click to expand...
Click to collapse
Yeah, it was internal changes and some screwing around while playing with it. Aiming for more features and once a 'finalized' kernel build is there I will probably do change-logs and change the scheme of numbering.
Hey, what are the changes in V1.7.1 compared to 1.7?
HSD-Pilot said:
Hey, what are the changes in V1.7.1 compared to 1.7?
Click to expand...
Click to collapse
Tried to fix and make SavagedZen more reponsive, but it is a weird governor, and also included InteractiveX in the meantime (no bug there).
Will probably just put into Github after this change so other people can see the changelogs.
Thanks for reply - Flashed it already :good:
well I would comment on your topic of rom ([ROM] Stock 4.1.2 JB optimized - Deblurred AOSP + 4.2 Kernel + extras). but as it only involves the kernel decided to post it here ..
good this new government "SavagedZen" is weird! I did not like, played some games, subway surfers, temple run 2, etc ... all caught. then modified to smartassV2, and now games are perfect and without lagg, I have helped with my feedback
Paulinhip said:
well I would comment on your topic of rom ([ROM] Stock 4.1.2 JB optimized - Deblurred AOSP + 4.2 Kernel + extras). but as it only involves the kernel decided to post it here ..
good this new government "SavagedZen" is weird! I did not like, played some games, subway surfers, temple run 2, etc ... all caught. then modified to smartassV2, and now games are perfect and without lagg, I have helped with my feedback
Click to expand...
Click to collapse
Yeah, I am defaulting to smartassV2 back again...
sounds great your kernel mods.
i will try your stuf spin, i wait for a more stable release.
but think at weekend i will go with IT.
regards
Little Bug Report: I get some freezes and Hot reboots with the Interactive X Governor. No big deal, just to let ya know
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
Little Bug Report: I get some freezes and Hot reboots with the Interactive X Governor. No big deal, just to let ya know
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Attempted to fix that on 1.7.3 -- unsure on the results yet. :highfive: Thanks for helping man!
Alright, just flashed V1.7.3 and set Interactive X as default. Will report back if I get any issues.
I'm @ work so I had to pack an flashable Zip with the Smartphone. It's a lot faster on my PC
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:09 PM ---------- Previous post was at 05:28 PM ----------
Sorry dude, again no luck. As soon as I turn off my Screen my Phone is dead. I have to force the reboot by Power + Vol. down.
Tried it 3 times now > back to SA V2 :thumbup:
Gesendet von meinem XT890 mit Tapatalk 2
HSD-Pilot said:
Alright, just flashed V1.7.3 and set Interactive X as default. Will report back if I get any issues.
I'm @ work so I had to pack an flashable Zip with the Smartphone. It's a lot faster on my PC
Gesendet von meinem XT890 mit Tapatalk 2
---------- Post added at 06:09 PM ---------- Previous post was at 05:28 PM ----------
Sorry dude, again no luck. As soon as I turn off my Screen my Phone is dead. I have to force the reboot by Power + Vol. down.
Tried it 3 times now > back to SA V2 :thumbup:
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Damn, ok and thanks! ... so InteractiveX is not functional yet sounds like it must have something to do with the early suspend portion -- will eventually fix it. Good thing is that smartassV2 works flawless!
Nice work on the governors!
I remembered some governor benchmarks I read a while ago on this forum, and I thought you might be interested in it:
[REF][GUIDE] Battery Saving Governor Benchmarks
Some interesting quotes from the above thread:
the difference between the best (smartassV2) and worst drain (lazy) is 0.05mA (a tiny amount)
Click to expand...
Click to collapse
choosing SmartassV2 over Lazy would prevent about 600mA being wasted in one hour. To put this in context, that is enough to power your screen for 3 seconds (assuming a drain of 200mA).
Click to expand...
Click to collapse
Furthermore, I remember another thread (which I have not found), which showed that governors which did not jump straight to the highest frequency could actually negatively impact the battery life. The reason behind it is that CPU usage is only a fraction of the battery drain, and having a slower CPU means applications have to spend longer in active state, thereby also causing other components battery drain over a longer period of time. The display is the biggest battery eater, followed by the radios.
Basically, what I trying to say, is (most) governors have no perceptible impact on battery life, and I believe users who report otherwise suffer from the placebo effect. So I think focusing on a stable default governor which gives a smooth lag free experience is the way to go.
arman68 said:
Nice work on the governors!
I remembered some governor benchmarks I read a while ago on this forum, and I thought you might be interested in it:
[REF][GUIDE] Battery Saving Governor Benchmarks
Some interesting quotes from the above thread:
Furthermore, I remember another thread (which I have not found), which showed that governors which did not jump straight to the highest frequency could actually negatively impact the battery life. The reason behind it is that CPU usage is only a fraction of the battery drain, and having a slower CPU means applications have to spend longer in active state, thereby also causing other components battery drain over a longer period of time. The display is the biggest battery eater, followed by the radios.
Basically, what I trying to say, is (most) governors have no perceptible impact on battery life, and I believe users who report otherwise suffer from the placebo effect. So I think focusing on a stable default governor which gives a smooth lag free experience is the way to go.
Click to expand...
Click to collapse
I agree for the most part but that really depends a lot on the type of processor and SoC capabilities, for phones like us I focused on the tweaked smartassV2 further to get it to ramp up and down faster, and it is noticeable smoother. , good battery life since it ramps down better than the on-demand or interactive governors here!
SmartassV2 was the winner on our testing too so we left that one . I just wanted to get InteractiveX working on it for future flexibility and the days that I messed up with SavagedZen it was just an experiment as I had never tried it before -- the results was that I did not like it a lot or I ported it wrong! haha
Friend'm using interactiveX governor since yesterday, andthe results seem to be good and had no lagg dabateria useful life is good (since I am a hard-user).
but honestly the samatassV2 is better, it seems that runs smoother on my device!
but just wanted to note that the InteractiveX is working!
sorry for bad english

[Q] Incredible S ROMs and battery life

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.

[Kernel] Deported / Stockish: Issues, Reports, & Configuration

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.

[Kernel][Uber][CAF] Rudolph V4 Mark-I [LA.BF.1.1.3-02310-8x26.0]

Hi everyone,
This is my kernel based on Sultan's sources upstreamed merged with LA.BF.1.1.3-02310-8x26.0. I have put tons of work into this over the last few months, and before I get started I would just like to thank those who have helped me get a better grasp on programming over the last year or so:
Mathew Alex (DespairFactor), Chad Russel, Rohit Poroli, dingermtb, Adesh15, Lord Boeffla, ZaneZam, NoSpamDan, Nachiket Namjoshi, Martinusbe, Joshwin Aranha, SHM, Sultan, DerRomtester, Franco, AK, myfluxi, GalaticStryder, Gandalf, and maxwenn!
Were it not for these people, you would not have this kernel.
I want to go with the KISS philosiphy on this one and make the redundant claim that if you want a proper changelog, use GitHub. I do a lot for every release so maintaining it all in the thread without a bunch of clutter and wasted time is pointless. If I think it's cool or notable, I will bring it up.
I always compile this with the latest version of Uber, it has Sultans thermal driver, it uses Blu Plug as the default hot plug, and I left CPU input boost in tact (not CPU boost) from Sultan's kernel. There are several other features of this kernel that I will not go over quite frankly because it would take forever. Just believe me when I say I put a lot of effort into it
As usual, disrespect will not be tolerated. Failure to exemplify respect will get you reported to a mod. Case closed. Be excellent to one another.
Disclaimer!
HTML:
I am not responsible for any issues you may have. Those are all on you. If you step in dog **** while walking at night due to the flash burning out, if your phone goes Note 7 on you, or if you encounter any Nazi's or anything of that nature, then I refutre all responsibility. Your flash, your choice.
Downloads
https://www.dropbox.com/sh/8a3zaq7g0gfckca/AABAEEzcCUzRClZf2EQlJqW6a?dl=0
Enjoy!
XDA:DevDB Information
Rudolph, Kernel for the OnePlus X
Contributors
CertifiedBlyndGuy
Source Code: https://github.com/CandyDevices/kernel_oneplus_onyx
Kernel Special Features: A CAF kernel baked by a blind 16 year old American student of CS
Version Information
Status: Stable
Current Stable Version: V4 Mark-I
Created 2016-12-23
Last Updated 2017-02-17
Reserved
Recommended Settings
Sit back and let the post boot script handle it all. On Sultans ROM and Candy, you should be fine with Interactive as the default governor though on all other ROMs, I do urge you to use Smartmax
Reserved
Thnks bruh
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
What the best setup for ur amzing kernel?!
---------- Post added at 11:29 AM ---------- Previous post was at 11:14 AM ----------
Btw ur kernel make livedisplay work perfectly ,,beofre this all nougat rom have bug with livedisplay
RJ, I am glad to see your kernel again. Can't wait to try it when I move to Nougat since I'm still on Sultan. Thanks for sharing.
LolHacker17 said:
Thnks bruh
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
What the best setup for ur amzing kernel?!
---------- Post added at 11:29 AM ---------- Previous post was at 11:14 AM ----------
Btw ur kernel make livedisplay work perfectly ,,beofre this all nougat rom have bug with livedisplay
Click to expand...
Click to collapse
Oh cool! I didn't know it fixed LiveDisplay. I'll post recommended settings later today
Added recommended settings to screenshots
Good to see you back again RJ. No time for testing on Christmas, but after that I will give it a try again. Happy Holidays!
CertifiedBlyndGuy said:
Oh cool! I didn't know it fixed LiveDisplay. I'll post recommended settings later today
Click to expand...
Click to collapse
Hahahaha i was shock went livedisplay run perfectly ,,btw in ur recommended setting the min cpu is 1.5ghz sure?
@CertifiedBlyndGuy - Where do i get your latest ROM?
No undervolt?
LolHacker17 said:
Hahahaha i was shock went livedisplay run perfectly ,,btw in ur recommended setting the min cpu is 1.5ghz sure?
Click to expand...
Click to collapse
Its dynamic. 268mhz is recommended
LolHacker17 said:
No undervolt?
Click to expand...
Click to collapse
That's device specific and I'm not touching that with a 10ft pole
BrokenBee said:
@CertifiedBlyndGuy - Where do i get your latest ROM?
Click to expand...
Click to collapse
Its not up right now.
You can find our source at https://github.com/CandyRoms
Update coming at you later today after I do a bit more testing
What's planned:
1. Blu Plug (disabled)
2. Improved NEON implementation
3. BFQ instead of Zen as the default IO schedular. I prefer it's greater precision over the deduced latency... On top of that external write speeds seem rk be faster which is a huge bonus for me. Heavy workloads should benefit as well
4. I updated my thermal driver with Franco's latest patches and an additional throttling step. Throttling will also kick in at 42c instead of 40c for those of you living in areas with higher ambient temperatures
5. 2.5ghz was enabled by default for PVS8 users with the optimal voltage. I have spent hours testing it and thus far haven't encountered any issues
6. Faster vmstat
7. Improvements made to CPU boost
8. Improvements to sound control
9. More hidden kernel addresses
10. Several other performance improvements and bugs fixed
Mark XV is up!
1. Blu Plug (disabled)
2. Improved NEON implementation
3. BFQ instead of Zen as the default IO schedular. I prefer it's greater precision over the deduced latency... On top of that external write speeds seem rk be faster which is a huge bonus for me. Heavy workloads should benefit as well
4. I updated my thermal driver with Franco's latest patches and an additional throttling step. Throttling will also kick in at 42c instead of 40c for those of you living in areas with higher ambient temperatures
5. 2.5ghz was enabled by default for PVS8 users with the optimal voltage. I have spent hours testing it and thus far haven't encountered any issues
6. Faster vmstat
7. Improvements made to CPU boost
8. Improvements to sound control
9. More hidden kernel addresses
10. Several other performance improvements and bugs fixed
11. HTC Async
I'm quite happy with this release and it truly is a milestone from where deCAF first started. Hosts of improvements have been made and the kernel has been shaping up nicely with my no unneeded BS policy this time around.
Merry Christmas everyone! I hope the best for all of you
Quick question... Does this support usb fast charge??
Sent from my ONE E1003 using Tapatalk
gouthamgoumi said:
Quick question... Does this support usb fast charge??
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
All the features are in the OP. It only supports CLI
Same recommended setup?
LolHacker17 said:
Same recommended setup?
Click to expand...
Click to collapse
Yes

Categories

Resources