Change log:
Included all inazuma r5
Added many governor, i/o schedulers.
Governor: Interactive, interactive pro, impluse, powersave, performance, conservative, smartmax, intelliactive, lionfish, zzmoove, bioshock, yankactive, bluactive, elementalX, ondemand, userspace
I/o schedulers: noop, deadline, row, fiops, sio, sioplus, tripnadroid, cqf, bqf, zen
Hotplug: IntelliPlug, ClusterPlug, Alucard Hotplug, ThunderPlug
Usb fast charge
Sound controler
Adaptive Low memory killer
Powersuspend
OC cpu 1.8 ghz, GPU 650Mhz
DT2W halfscreen, fullscreen
Many TCP.
And many many optimized...
Download: Please go to downloaad tab
XDA:DevDB Information
Chriszuma Kernel, Kernel for the Moto G 2015
Contributors
nguyenquangduc2000, zeeshanhussain12
Source Code: https://github.com/nguyenquangduc2000/chriszuma-msm8916
Kernel Special Features: Dt2w, OC CPU and GPU, many governors and i/o schedulers...
Version Information
Status: Stable
Current Stable Version: V4
Stable Release Date: 2016-06-17
Created 2016-06-17
Last Updated 2016-06-17
Isn't CPU 1.8 GHz cause damage to device ?
Stock ROM supported?
Thanks for your work
Gpu clock speeds are not showing.. just showing 400 mhz and next 0 max.. min is 100 mhz
Source code?
Sent from my MotoG3 using XDA-Developers mobile app
Rahul1608 said:
Gpu clock speeds are not showing.. just showing 400 mhz and next 0 max.. min is 100 mhz
Click to expand...
Click to collapse
What about the CPU overcook, is it actually working?
arindamghosal said:
What about the CPU overcook, is it actually working?
Click to expand...
Click to collapse
Yes working.. But quickly heats up a lot..
nguyenquangduc2000 said:
Change log:
Included all inazuma r5
Add many governor, i/o schedulers.
OC cpu 1.8 ghz, GPU 650Mhz
DT2W halfscreen, fullscreen
Many other features are waiting you to explore.
Download here or you can go to download tab.
XDA:DevDB Information
Chriszuma Kernel, Kernel for the Moto G 2015
Contributors
nguyenquangduc2000, zeeshanhussain12, nguyenquangduc2000
Kernel Special Features: OC cpu, gpu, Dt2w...
Version Information
Status: Stable
Current Stable Version:V4
Stable Release Date: 2016-06-17
Created 2016-06-17
Last Updated 2016-06-17
Click to expand...
Click to collapse
Oh mate really thanks for this, nice performace. The bury_alem governor still crashing the system, maybe you remove it, the others are ok. The GPU's max frequency is 400 MHz, and when The phone turn on it start as 0 MHz. The rest are OK until now. Thanks again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
arindamghosal said:
What about the CPU overcook, is it actually working?
Click to expand...
Click to collapse
Yes it is at 1785 MHz, but don't enable the bury_allen Governor
---------- Post added at 12:28 PM ---------- Previous post was at 12:18 PM ----------
vicky90 said:
Isn't CPU 1.8 GHz cause damage to device ?
Click to expand...
Click to collapse
As he said for surnia kernel, he has already tested. The overclock in Android isn't like as PC, it's a bit different, if some issues happen, the mobile will heats up a bit, probably freezes, and reboot, then you can flash a more stable kernel. This kernel is working ok, just don't enable the Bury_Allen governor
josfer said:
Source code?
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank all of you. I will remove bary allen. Source code will be released after all the issues are fixed.
Update are available to download. Please try and report me if you have any problems.
Update:
-Removed barry allen
-Reconfiged gpu oc
Johny Cipeli said:
Oh mate really thanks for this, nice performace. The bury_alem governor still crashing the system, maybe you remove it, the others are ok. The GPU's max frequency is 400 MHz, and when The phone turn on it start as 0 MHz. The rest are OK until now. Thanks again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
Yes it is at 1785 MHz, but don't enable the bury_allen Governor
---------- Post added at 12:28 PM ---------- Previous post was at 12:18 PM ----------
As he said for surnia kernel, he has already tested. The overclock in Android isn't like as PC, it's a bit different, if some issues happen, the mobile will heats up a bit, probably freezes, and reboot, then you can flash a more stable kernel. This kernel is working ok, just don't enable the Bury_Allen governor
Click to expand...
Click to collapse
Hi,
Nice to know that the cpu overclocking is working, and probably gpu problem and the governor problem will be fixed in the next version hopefully. will try it out then. Does it support modified stock MM rom....??
Arindam
Amazing works.. OC seems really cooolll!!! Bro plejj fix Hard Disk not connecting issue..
Heres the logcat:
logcat.txt
dmesg.txt
last_kmsg.txt
Also if u want log cats of my Redmi and/or tab in which the HDD work, I can provide you..
vicky90 said:
Isn't CPU 1.8 GHz cause damage to device ?
Click to expand...
Click to collapse
No,it works well
Forever Alone said:
Amazing works.. OC seems really cooolll!!! Bro plejj fix Hard Disk not connecting issue..
Heres the logcat:
logcat.txt
dmesg.txt
last_kmsg.txt
Also if u want log cats of my Redmi and/or tab in which the HDD work, I can provide you..
Click to expand...
Click to collapse
I do not own osprey to test. I made it based on its configs. Therefore, I have released source code for any one want to fix this error.
Man, it's strange, the performance didn't increase, before I flash the kernel I had changed from ext4 to F2fs, Is is can influence in this problem?
can you give direct link to the OC commit of cpu & gpu?
Probably broke some records ;D
HelpMeruth said:
Probably broke some records ;D
Click to expand...
Click to collapse
The results here is the same, as if it had not been overclocked. Maybe Inazuma isn't compatible with Overclock
HelpMeruth said:
Probably broke some records ;D
Click to expand...
Click to collapse
Hi I got higher score than that on Optimus R11 kernel,.
Regards
Arindam
If its only pulling 530/1600 on GB3..... its worthless.
I've written extensively and performed hundreds of tests on GB using a half dozen kernels. I've pulled 570+ on single core and 1700 on multi core. Most well built and tuned kernels will average in the 550/1650 range. This Kernel falls flat on its face. As stock Kernels appear to pull about 525-535 single core, and about 1580-1600 multi-core.
The real question is: Does the GPU OC work.
I need some hard numbers to crunch using some graphic benchmarks. Then we'll see.
This is important to know, because I'm about to announce a community project that will crowdsource, and cherry pick the absolute best of the kernels currently in existence. I've long believed that this chip DOES oc, but not as high as 1.8ghz. As squid has shown, you can make it report higher speeds, but not operate at them. 1.4 is provable. Bluspark did 1.6, but theres debate as to whether it actually operated at it. There is NO debate however that the bluspark kernel scored higher than than the 1.4's have, ESPECIALLY on single core benchmarks. I think I've seen as high as 578 with it. This leads me to believe that it *may* be possible to OC the chip to the 1.5 range, before it just stops. Or it *could* be that above 1.4ghz, into the 1.6ghz range there is a disproportional gain in performance due to a)heat, b)inefficiency, or c)both.
The GPU is seriously lacking and without anyone really trying to push the limits until now, its been a mystery as to what it can do. I've seen 650 on the beserk kernel on redmi, but it was plagued by heat with extreme gaming. But users have reported that the 550ish mhz OC was both efficient and effective. So, lets see some real numbers here from some graphics benchmarks.
And to all those that cry and whine, and cry and whine, and yes... cry and whine about battery and heat and poor potty training as a child: go away. You're too far gone to understand that just because its available, you DONT have to use it. What do you guys do when you get into a car thats got 400 horsepower? or use an air conditioner in your home that goes down to 50 degrees? According to your logic, you floor it, until you crash it. Or you die from hypothermia with the latter.
Now..... on to the good stuff. Post your GPU OC vs 400-465mhz scores.
Related
This kernel uses AOSP camera driver so it's most likely compatible only with Redux 2.0 (tested) and Oxygen (not tested)
Before you do anything- make a backup
It's my lame attempt (I'm a modder, not a dev) to get more battery life without loosing stability of original kernel.
Kernel is based on current thalamus 2.6.35.14 sources
What is changed (mod8):
-Vdd levels sysfs interface is back, this time seems to be stable
-default voltages for CPU clocks <700 MHz are lowered a bit- keep this in mind when playing with UV
-headphone volume boosted a little- needs to be tested
-more optimized compilation- kernel should use CPU in more efficient way (and kernel is 500 bytes smaller )
-big thanks to paul8944 for testing
What is changed (mod7):
-removed sysfs Vdd levels interface- it seems that it was responsible for instability and FC's in mod6
-USB transfer speed is higher (was ~800kB/s, now ~2MB/s for write operations)
What is changed (mod6):
-added sysfs Vdd levels interface- VDD_MIN is set to 800 mV, VDD_MAX to 1300 mV, step is 25 mV (this works fine with IncrediControl)
-available governors: ondemand, powersave, conservative, performance and smartassV2
-conservative governor is tweaked a little (should be a little less conservative)
-USB transfer speed tweak- needs testing
-other fixes
What is changed (mod5)
-lowered minimum cpu clock to 128 MHz
-more clock speeds are available up to 1113 MHz
-added smartass and smartassV2 governors
-tinyRCU replaced with preemtive tinyRCU
-enabled call recording (not tested)
-many other fixes and improvements mainly form ch33kybutt's and elevendroids' sources
Note about smartass governor- after longer period of inactivity you have to press Power button for about 2 seconds to wake up the phone
Installation:
-make a nandroid backup (just in case)
-put zip on SD card and flash in recovery, I suggest also wiping dalvik-cache (just in case)
Download:
thalamus 2.6.35.14 mod8
md5: E526C99D4326F5B11D02DB60FEFA169F
Previous versions:
thalamus 2.6.35.14 mod7 (description above), md5: 7AB623BCC5E28D9BC8A012EDD9E9BBC7
Mod6 is not available due to instability
thalamus 2.6.35.14 mod5 (description above), md5: 7DC3E94E56FD00C49FEB5C713033DE33
thalamus 2.6.35.14 mod4 (128 MHz min cpu clock, default governors set, non-preemptive TinyRCU) md5: E7DD4637D8838A6E1A64E763C8A4D549
Kernel sources available on Github
I'll give it a try, seems good. I have one question and one suggestion:
the question is: what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
and the suggestion is to add the syscf interface for being able to change the voltages. It could save some battery life if our Desire stands it (mine does even at 800 mV )
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
blackhawk_LA said:
what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
Click to expand...
Click to collapse
I was not satisfied with default cpu clock table
-128 MHz uses ~20 mA of current less than 245- it's about 10% saving for iddle not locked phone
-for me 691 MHz max clock is really enough for my needs, it was not available in stock version
-more speeds make governors able to better match cpu speed (and save some juice)
-there are some performance fans so why not enable also 1113?
soronk said:
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
Click to expand...
Click to collapse
Looking what caused this, I'm not sure if it's wlan driver or preemtive tinyRCU (not present in mod4)
Download temporarily removed
EDIT:
It was wlan driver.
Corrected, reuploaded package
gen_scheisskopf said:
EDIT:
It was wlan driver.
Corrected, reuploaded package
Click to expand...
Click to collapse
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
soronk said:
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Me too.....
Sent from my HTC Desire using XDA App
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Tones1971 said:
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Click to expand...
Click to collapse
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
gen_scheisskopf said:
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
Click to expand...
Click to collapse
Yes it work! But without camera. MIUI needs the 720p camera drivers.
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
h_misc said:
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
Click to expand...
Click to collapse
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Click to expand...
Click to collapse
Too bad, with screen off laggy behaviour when raising the CPU-clock is exactly what I want.
With the conservative governor reaction to the power button is instant, smartass was really irritating me when pushing the power button the days I tried it.
I used setcpu with a screen off profile with conservative and ondemand with screen on (on gingervillain) which was just perfect.
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
blackhawk_LA said:
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
Click to expand...
Click to collapse
I use the FTP server with screen off, a script that functions as webserver to name two examples. So I need it to be possible for the CPU to be at more than minimal speed.
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
blackhawk_LA said:
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
Click to expand...
Click to collapse
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
So which governors do you think should be in kernel? I don't want to include all available
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
So which governors do you think should be in kernel? I don't want to include all available
Click to expand...
Click to collapse
The ones I like to use are ondemand and conservative.
You should include what you like off course
h_misc said:
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
Click to expand...
Click to collapse
I couldn't agree more
I think that the most used governors are conservative, ondemand, interactive and smartass (don't know about the new governos: smartass2 and others)
But for me, having ondemand it's enough
blackhawk_LA said:
But for me, having ondemand it's enough
Click to expand...
Click to collapse
Do you want a dedicated build?
So as for now governors will be ondemand, performance, conservative, powersave (even more conservative than conservative ) and smartass- more likely v2.
I plan to release mod6 when I'll implement SVS
I just installed the new flinny build 129 and i have been facing delay for the screen to wake up after pressing the power button ..any idea how the dealy can be removed..i have clean installed the rom.
please help
chaitu2710 said:
I just installed the new flinny build 129 and i have been facing delay for the screen to wake up after pressing the power button ..any idea how the dealy can be removed..i have clean installed the rom.
please help
Click to expand...
Click to collapse
To the Performance Setting and check your CPU governor and Max freq. "On Demand" and "Interactive" governors can give good performance. and make sure Max Freq is not below 1 Ghz
premsrj said:
To the Performance Setting and check your CPU governor and Max freq. "On Demand" and "Interactive" governors can give good performance. and make sure Max Freq is not below 1 Ghz
Click to expand...
Click to collapse
i use smartassv2 at 1 ghz and mi frequency of 245 mhz..nut he screen still takes like a second to show up
chaitu2710 said:
i use smartassv2 at 1 ghz and mi frequency of 245 mhz..nut he screen still takes like a second to show up
Click to expand...
Click to collapse
Try ondemand, it's better now
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Oh, are you using marioemp's kernel?
Hi,
I'm experiencing the same problem with build 129 - was fine in 128.
I'm using marioemp's latest kernel...changing scheduler/governor/max frequency doesn't seem to have any impact.
Cheers,
Dave
I'm using flinnys kernel that came with the rom (Build 129), ondemand 245-1200, noop. And I'm not experiencing any such wakeup lags.
teadrinker said:
I'm using flinnys kernel that came with the rom (Build 129), ondemand 245-1200, noop. And I'm not experiencing any such wakeup lags.
Click to expand...
Click to collapse
I have managed to reduce the lag by increasing the MIN frequency from 245 to 341 but it is still there.
I'll switch back to the standard 129 kernel - bit of a shame as marioemp's does seem a bit smoother/nippier!
Cheers,
Dave.
teadrinker said:
Try ondemand, it's better now
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Oh, are you using marioemp's kernel?
Click to expand...
Click to collapse
Yes I'm using marioemp's kernel.. Is it a problem with the kernel??
it does reduce with the standard kernel considerably.
Hello.
Since kernel development is pretty non existent for picassowifi I compiled one.
Version 0.1:
Updated deadline IO scheduler (new default)
Activated a bunch of tcp congestion algorithms (westwood new default)
Tweaks in interactive. Added performance governor
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE set to 0 in config so wifi works without changing build prop.
Version 0.2:
Rebased to source for version T520UEUAND1 from may... Camera works!!
Version1.0: (
Grabbed a bunch of commits from here SkyHigh Galaxy Tab S Kernel
Features from there:
CPU
CPU max frequency A15 cores = 2100 MHz (stock/default = 1900 MHz)
CPU min frequency A7 cores = 200 MHz (stock/default = 500 MHz)
Multi-core power saving control (sched_mc_power_savings)
CPU VOLT
Voltage control for:
big cores
LITTLE cores
GOV
CPU governor
interactive (default)
on-demand
userspace
CPU governor tunables
MEMORY
I/O Schedulers
BFQ (default)
DEADLINE (tweaked)
CFQ
NOOP
FIOPS
General IO tuneable
Int storage scheduler
Int storage read-ahead
Kernel SamePage Merging (KSM)
Pages to Scan
Scan delay interval
Virtual memory tuneables
GPU
GPU max frequency = 667 MHz (stock/default = 480 MHz)
GPU min frequency = 100 MHz (stock/default = 177 MHz)
GPU voltage control
POWER SUSPEND
PowerSuspend
Autosleep_hook
Userspace_trigger
DisplayPanel_hook
[*]PowerSuspend State (onlt with Userspace_trigger)
Hybrid_hook (default)
Dynamic management of dirty page writebacks
Adaptive VFS Cache Pressure on Suspend / Resume (1024 kB for 16 GB partition)
ADVANCED
Low Memory Killer (OOM LMK)
Management of not killable processes whitelist
system apps
user apps
entropy
Gentle fair sleepers control
randomize_va_space control
THERMAL
CPU thermal control
GPU thermal control
Memory interface thermal control
AUDIO
* WolfsonMicro WM5102 sound control by AndreiLux
Mono output
HeadPhone equalizer settings
BATTERY
Unstable power detection
AC mains
Standard downstream port
Dedicated charging port
Charging downstream port
Accessory charger adapter
Miscellaneous charging
MHL power
Battery Scaling Calibration (fuel-gauge chip reset)
Click to expand...
Click to collapse
Most changes are the same... for more specific changes check my Github
flash in recovery
Make a backup before flashing.
FYI: I'm by no means a kernel developer, I'm just compiling because no one else is doing it
Reserved cause yeah
Just curious (and to help out others) - stock based, or CM?
Good work tho! Glad to see some kernel development
Stock based
Sent from my Nexus 5 using Tapatalk
Glad to hear this!
---------- Post added at 12:42 AM ---------- Previous post was at 12:30 AM ----------
Do you have the ability to make one for SM-P900?
canezila said:
Glad to hear this!
---------- Post added at 12:42 AM ---------- Previous post was at 12:30 AM ----------
Do you have the ability to make one for SM-P900?
Click to expand...
Click to collapse
Sorry but no...I don't have it and I don't have much time other than weekends
Enviado desde mi SM-T520 mediante Tapatalk
How about for the t320?
LibiSC said:
Hello.
Since kernel development is pretty non existent for picassowifi I compiled one.
Version 0.1:
Updated deadline IO scheduler (new default)
Activated a bunch of tcp congestion algorithms (westwood new default)
Tweaks in interactive. Added performance governor
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE set to 0 in config so wifi works without changing build prop.
to do:
check the thermal driver
check hotplug driver
port stuff from mainstream
bugs:
Samsung camera app force closing... I hate Samsung
boot.img attached. You can use flashify, adb or Odin to flash
Make a backup before flashing.
FYI: I'm by no means a kernel developer, I'm just compiling because no one else is doing it
Click to expand...
Click to collapse
Could u link any guide or the method you use for custom kernels?
The camera is a pain for both costom roms and kernels.
Just follow the txt that comes with the source... The problem is just with Samsung camera app.... Other camera apps work just fine
Sent from my Nexus 5 using Tapatalk
CodeIndia said:
Could u link any guide or the method you use for custom kernels?
The camera is a pain for both costom roms and kernels.
Click to expand...
Click to collapse
New version... Camera works!! test please
Which one of these is it?
bootTest.img
boot02.img
I tried boot02.img and it doesn't fix camera and makes chrome and play store crash.
Boot02...i think your room has to end in nd1
Sent from my Nexus 5 using Tapatalk
Shaheer said:
Which one of these is it?
bootTest.img
boot02.img
I tried boot02.img and it doesn't fix camera and makes chrome and play store crash.
Click to expand...
Click to collapse
^
Sent from my Nexus 5 using Tapatalk
LibiSC said:
Boot02...i think your room has to end in nd1
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh lol. I was trying it on my CM port. Trying to get camera to work on there but no luck so far.
Shaheer said:
Oh lol. I was trying it on my CM port. Trying to get camera to work on there but no luck so far.
Click to expand...
Click to collapse
Try using the binaries from a ...nd1 rom in your aosp or cm rom
Sent from my Nexus 5 using Tapatalk
LibiSC said:
Try using the binaries from a ...nd1 rom in your aosp or cm rom
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Camera binaries?
Also tried this boot2 on the cm ROM, but kept fc com.android.phone
Cryonic90 said:
Also tried this boot2 on the cm ROM, but kept fc com.android.phone
Click to expand...
Click to collapse
Same
Shaheer said:
Camera binaries?
Click to expand...
Click to collapse
Makes sense cause it's not for cm roms it's for stock roms...
With binaries I meant rom binaries and libs... AFAIK aosp needs proprietary libs
Sent from my Nexus 5 using Tapatalk
New version up... big jump to version 1.0... thanks @UpInTheAir for his work and all the people that collaborate with him.
Cpu max set 2000 mhz min set to 250 mhz
Gpu max set to 533 mhz min set to 100mhz
You can try make them go higher but it's pretty unstable from there.
This is my Shield Kernel, focused on the security and stability of Android OS, you can flash it using TWRP. This use the last CM sources of MSM8916 SOC, your bug reports are important for the better stability of Android.
The Kernel was tested on XOSP ROM (based on AOSP), may be it works on stock and CyanogenMod ROMs, so it's for Marshmallow ROMs.
Note
This Kernel is only for Moto G 2015 (osprey), I am not responsible of your bricked devices, flash at your own risk.
Features
Builded with Uber 4.9 optimized
Lastest wlan drivers with size optimized
Cleaned up defconfig
Correct permissions for GENTLE SLEEPERS
ThunderPlug
LCD Notify
KCAL control calibration color (thanks @savoca)
Enabled some TCP congestions
-BIC
-CUBIC
-WESTWOOD
-HYBLA
-ILLINOIS
-YEAH
-LP
-SCALABLE
-VENO
-VEGAS
-HTCP
-HSTCP
Optimized sfck compression
Low Memory Killer by default
Marshmallow ROMs support
Lionfish Governor (thanks to @squid2)
Last zram documentation
Optimized SHA routines 256/224
Optimized some task of Shed
Silenced many log_spam
Some fixes of memory leaks
Shed controls
Writeback fixes
Reduced some wakelocks
Optimized shed domains
Cleaned some dead code
Optimized apply_slack (PERFORMANCE)
Improves on shed.h about LOAD_FREQ
Some specific optimizations for cortex A53
Many USB and WiFi IDs for correct use
CRC toogle for more performance
Used last repo sources from CyanogenMod
Arch Power enable for speed
Release history
Code:
r5: September 04, 2016
- lib: crc32: clean up spacing in test cases
- initramfs: support initramfs that is bigger than 2GiB
- sched: Use swap() macro in scale_stime()
- kernel: Add required TetherStats definitions
- arm/dt: msm8916: Enable bam_dmux fast shutdown
- lib: align source before using optimized implementation
- ANDROID: restrict access to perf events
- rcu: Move SRCU grace period work to power efficient workqueue
- net: wireless: move regulatory timeout work to power efficient workqueue
- firmware: use power efficient workqueue for unloading and aborting fw load
- workqueue: Add system wide power_efficient workqueues
- workqueues: Introduce new flag WQ_POWER_EFFICIENT for power oriented workqueues
r4: July 30, 2016
- Support for all Marshmallow ROMs
- powerpc: Align TOC to 256 bytes
- arm: crypto: Add optimized SHA-256/224
- zram: update documentation
- cpufreq: implement lionfish gov
- sched/rt: Reduce rq lock contention
r3: July 25, 2016
- timer: optimize apply_slack()
- sched: LOAD_FREQ (4*HZ+61) avoids loadavg
- Writeback sync fixes
- Added KCAL control calibration color
- xsched: Optimize build_sched_domains() for saving first SD
- zlib: clean up some dead code
- Reduced WakeLocks
r2: July 22, 2016
- Added some TCP advanced [B](the names it's avalaible on the Features section[/B]
- xz: Optimize Sfck Compression
- Added Thunderplug
- fs/pipe.c: skip file_update_time on frozen fs
- msm: mdss: Silence log spam
- fs/namei.c: fix potential memory leak in path_lookupat
- sched: Optimize task_sched_runtime()
- drivers: lmk: enable adaptive lmk by default
- Added LCD NOTIFY from LG
r1: July 20, 2016
- Initial release for users
Flash instructions
1. Download kernel zip and go to TWRP
2. Flash kernel zip without wipes
3. Reboot and enjoy
Downloads
New folder for download the last release of Shield Kernel
XDA:DevDB Information
shield-kernel-g3, Kernel for the Moto G 2015
Contributors
TechnoAnder
Source Code: https://github.com/ShieldKteam/shield_osprey
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r5
Stable Release Date: 2016-09-04
Created 2016-07-21
Last Updated 2016-09-04
Hi, I think it's a good kernel, but can you add some stuff like DT2W, CPU governors/hotplug and optional underclock (19MHz on the GPU in idle) and overclock? With these things it will be the best kernel for me.
I am going to try it now
PD: Greetings from Spain!
EvilHowl said:
Hi, I think it's a good kernel, but can you add some stuff like DT2W, CPU governors/hotplug and optional underclock (19MHz on the GPU in idle) and overclock? With these things it will be the best kernel for me.
I am going to try it now
PD: Greetings from Spain!
Click to expand...
Click to collapse
Yeah, in next release will have new things
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Welcome
TechnoAnder said:
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Welcome
Click to expand...
Click to collapse
Any way to add voltage control?
Sent from my MotoG3 using Tapatalk
TechnoAnder said:
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Click to expand...
Click to collapse
Can you add CPU governors such as impulse & alucard, as well as GPU & CPU OC such as the 1881 MHz for CPU and 650/720 MHz for GPU? For some reason though, the GPU OC seems to be really fidgety. Maybe you can take a crack at it?
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
acejavelin said:
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
Click to expand...
Click to collapse
I don't see that at all, I think adding oc options are a smart idea, for some including myself not having these options is a deal breaker. I mean.. common, the osprey with 1G of ram doesn't exactly blow me away the competition.
True, there are already two very good kernel's out with OC, but one of them currently lacks advanced TCIP westwood etc <--(firekernel) & the other AGNi, seems to have problems with changing/locking I/O schedulers unless you use the agni control centre.
Also both of these kernel's have complaints & questions off whether or not the OC works or not. And
Some people are certain that the OC worked better on blusparks kernel for 5.1.
I personally would not use a kernel without at least the option for GPU over clock.
Also KSM would be nice.
Plus we already have have squid kernel and ultra kernel and optimus kernel
We don't need another stripped down kernel .
Just keep it minimal, like Optimus
Acidfire.TM said:
I don't see that at all, I think adding oc options are a smart idea, for some including myself not having these options is a deal breaker. I mean.. common, the osprey with 1G of ram doesn't exactly blow me away the competition.
True, there are already two very good kernel's out with OC, but one of them currently lacks advanced TCIP westwood etc <--(firekernel) & the other AGNi, seems to have problems with changing/locking I/O schedulers unless you use the agni control centre.
Also both of these kernel's have complaints & questions off whether or not the OC works or not. And
Some people are certain that the OC worked better on blusparks kernel for 5.1.
I personally would not use a kernel without at least the option for GPU over clock.
Also KSM would be nice.
Plus we already have have squid kernel and ultra kernel and optimus kernel
We don't need another stripped down kernel .
Click to expand...
Click to collapse
Then build it yourself... Clone fire kernel source, add Westwood, run make and flash. There are tons of tutorials online how to do it, you really don't have to be programmer, just be able to follow a tutorial, cut & paste, and have patience. Just if you share it online, honor your sources.
Overclocking kills battery, stability, and hardware longevity... The Moto G 2015 is already overclocked at 1.4ghz. As much as you and others want better performance, others would sacrifice some performance for more battery life.
Same with DT2W, it literally increases idle/sleeping battery draw 1%-2% per hour... For me, on a device that support doze mode, I can't fathom why anyone would want that unless their power button is broken.
My point is the kernels that survive, thrive, and become the most stable and widely accepted are the ones the author built the way they wanted and didn't cave to every user request just because they said "I'd never use a kernel without (blah)".
Now, if that is the OPs purpose, to build a loaded, full-featured kernel with every whiz-bang feature... Fine, and I encourage them to do so, heck, I'll test it if they like. I've just been in the Android game a long time, and what I started seeing threw up red flags for me so I thought I would say something.
Sent from my XT1575 using Tapatalk
@acejavelin
You already said all of this, wow, defensive much?
How about you go use optimus then. Or even better.
Stock CM13 KERNEl
Red flags??. There was one user asking for some OC.... yeah,! RED FLAGS!
Also.. MotoG3 is not over locked at 1.36(1.4).
The motoE and others are underclocked at 1.2 & 1.3.
And overclocking.. Unstable??... Hotter CPU?? Less battery??
Maybe you don't know how to set up an OC properly but I haven't had any of those problems unless I'm being really cheeky and max out the frequency.
I run over clocked without hot plug at 1.6ish
And run cooler than on the stock kernels.
I'm also benchmarking all the time, so I know I'm
Getting the performance
increase also.
PS. I agree with you about the dt2w, I don't use it.
[
One suggestion if building a kernel for battery. The lionfish governor is great for battery. I've been testing this governor and battery is good for Moto G3.
Sent from my MotoG3 using Tapatalk
dazeone said:
[
One suggestion if building a kernel for battery. The lionfish governor is great for battery. I've been testing this governor and battery is good for Moto G3.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I would like to do what acejavelin suggested
And build upon firekernelv4.
I like lionfish gov, and people want advanced TCIP
. it would be battery life oriented, with performance options
.
Acidfire.TM said:
I would like to do what acejavelin suggested
And build upon firekernelv4.
I like lionfish gov, and people want advanced TCIP
. it would be battery life oriented, with performance options
.
Click to expand...
Click to collapse
That sounds good. Any hot plugs that you're thinking of to use?
Sent from my MotoG3 using Tapatalk
Acidfire.TM said:
@acejavelin
Also.. MotoG3 is not over locked at 1.36(1.4).
The motoE and others are underclocked at 1.2 & 1.3.
Click to expand...
Click to collapse
Sorry, it's been a long week... looking back I went a little overboard. I apologize for spouting off.
But the Snapdragon 410 in the Moto G is overclocked already... the Snapdragon 410 is a 1.2 Ghz processor, Moto overclocked it to 1.38 didn't they? According to Qualcomm's website the 410 is a 1.2Ghz processor, it doesn't list variants or different models of the 410 and there is only one part number of MSM8916. I know some tech sites have said they suspect it's a different variant, perhaps the 412 (MSM8916v2) but the memory clock is 533Mhz and not 600Mhz, so the numbers don't match up. Meaning the most likely case is the processor is a SD410 1.2Ghz, overclocked to 1.38Ghz (1.4Ghz).
Or am I way off base here?
acejavelin said:
Sorry, it's been a long week... looking back I went a little overboard. I apologize for spouting off.
But the Snapdragon 410 in the Moto G is overclocked already... the Snapdragon 410 is a 1.2 Ghz processor, Moto overclocked it to 1.38 didn't they? According to Qualcomm's website the 410 is a 1.2Ghz processor, it doesn't list variants or different models of the 410 and there is only one part number of MSM8916. I know some tech sites have said they suspect it's a different variant, perhaps the 412 (MSM8916v2) but the memory clock is 533Mhz and not 600Mhz, so the numbers don't match up. Meaning the most likely case is the processor is a SD410 1.2Ghz, overclocked to 1.38Ghz (1.4Ghz).
Or am I way off base here?
Click to expand...
Click to collapse
Looking back, I was about off centre myself this morning, apologies.
acejavelin said:
Then build it yourself... Clone fire kernel source, add Westwood, run make and flash. There are tons of tutorials online how to do it, you really don't have to be programmer, just be able to follow a tutorial, cut & paste, and have patience. Just if you share it online, honor your sources.
Overclocking kills battery, stability, and hardware longevity... The Moto G 2015 is already overclocked at 1.4ghz. As much as you and others want better performance, others would sacrifice some performance for more battery life.
Same with DT2W, it literally increases idle/sleeping battery draw 1%-2% per hour... For me, on a device that support doze mode, I can't fathom why anyone would want that unless their power button is broken.
My point is the kernels that survive, thrive, and become the most stable and widely accepted are the ones the author built the way they wanted and didn't cave to every user request just because they said "I'd never use a kernel without (blah)".
Now, if that is the OPs purpose, to build a loaded, full-featured kernel with every whiz-bang feature... Fine, and I encourage them to do so, heck, I'll test it if they like. I've just been in the Android game a long time, and what I started seeing threw up red flags for me so I thought I would say something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Again thanks mate
Henriquefeira said:
Just keep it minimal, like Optimus
Click to expand...
Click to collapse
Yes, sure I will do it.
Acidfire.TM said:
I don't see that at all, I think adding oc options are a smart idea, for some including myself not having these options is a deal breaker. I mean.. common, the osprey with 1G of ram doesn't exactly blow me away the competition.
True, there are already two very good kernel's out with OC, but one of them currently lacks advanced TCIP westwood etc <--(firekernel) & the other AGNi, seems to have problems with changing/locking I/O schedulers unless you use the agni control centre.
Also both of these kernel's have complaints & questions off whether or not the OC works or not. And
Some people are certain that the OC worked better on blusparks kernel for 5.1.
I personally would not use a kernel without at least the option for GPU over clock.
Also KSM would be nice.
Plus we already have have squid kernel and ultra kernel and optimus kernel
We don't need another stripped down kernel .
Click to expand...
Click to collapse
Thanks
acejavelin said:
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
Click to expand...
Click to collapse
Yes, you opinion I like a lot, may be I wrong saying "users, what features you want for this Kernel?", no problem, this forum is for say the opinion of each one, I will work focused on the battery and security, thanks for your opinion.
acejavelin said:
Sorry, it's been a long week... looking back I went a little overboard. I apologize for spouting off.
But the Snapdragon 410 in the Moto G is overclocked already... the Snapdragon 410 is a 1.2 Ghz processor, Moto overclocked it to 1.38 didn't they? According to Qualcomm's website the 410 is a 1.2Ghz processor, it doesn't list variants or different models of the 410 and there is only one part number of MSM8916. I know some tech sites have said they suspect it's a different variant, perhaps the 412 (MSM8916v2) but the memory clock is 533Mhz and not 600Mhz, so the numbers don't match up. Meaning the most likely case is the processor is a SD410 1.2Ghz, overclocked to 1.38Ghz (1.4Ghz).
Or am I way off base here?
Click to expand...
Click to collapse
I had the same suspect months ago, so I did a research and I found that osprey uses MSM8916 board of course, but its second revision which supports 1.363 GHz. Just to be clear, I'm not talking about snapdragon 412 but just about a 410 hardware revision; exactly like happened for snapdragon 810 (Qualcomm released a new 810 revision to fix the overheat issue for those who can't remember).
Motorola definitely didn't overclock it.
Source: Motorola's commit picked from qcom.
TechnoAnder said:
Hello guys, I'm preparing the release 2, it will have good improves, tell me here if you want some features inside of this Kernel.
Welcome
Click to expand...
Click to collapse
Ultra fast charge
---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------
acejavelin said:
And there it goes... right down the road of all those other bloated kernels... No offense, I have the utmost respect for developers, but @TechnoAnder you should build the kernel the way *YOU* want it, not what others want. A few throw ins are fine, but way to many kernels get out of control trying to add everything the users want and become f-ing messes in the end. There used to be like 30+ kernels for the Nexus 4, in the end there was about 4-5 because they stayed the course with their core functionality and didn't let the users dictate what was done. If you keep adding all these features it will just become a clone of the some of the other kernels.
What this device REALLY needs is a stripped down, simple kernel with almost no bells and whistles to keep battery usage down. Maybe a few governors/IO schedulers and some TCP congestion schemes, or things that have no real effect on battery usage like FauxSound. UnderVolt it slightly (most CPUs handle this with no issue) and keep it as clean and streamlined as possible. That's my two cents. worth, but I you don't need to make it for me, if I REALLY want it I can do it myself.
Click to expand...
Click to collapse
Sounds like a cracking kernel why don't you compile it
---------- Post added at 09:37 PM ---------- Previous post was at 09:32 PM ----------
acejavelin said:
Then build it yourself... Clone fire kernel source, add Westwood, run make and flash. There are tons of tutorials online how to do it, you really don't have to be programmer, just be able to follow a tutorial, cut & paste, and have patience. Just if you share it online, honor your sources.
Overclocking kills battery, stability, and hardware longevity... The Moto G 2015 is already overclocked at 1.4ghz. As much as you and others want better performance, others would sacrifice some performance for more battery life.
Same with DT2W, it literally increases idle/sleeping battery draw 1%-2% per hour... For me, on a device that support doze mode, I can't fathom why anyone would want that unless their power button is broken.
My point is the kernels that survive, thrive, and become the most stable and widely accepted are the ones the author built the way they wanted and didn't cave to every user request just because they said "I'd never use a kernel without (blah)".
Now, if that is the OPs purpose, to build a loaded, full-featured kernel with every whiz-bang feature... Fine, and I encourage them to do so, heck, I'll test it if they like. I've just been in the Android game a long time, and what I started seeing threw up red flags for me so I thought I would say something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Dunno if u got the memo but our device does not support doze
skooter32 said:
Ultra fast charge
---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------
Sounds like a cracking kernel why don't you compile it
---------- Post added at 09:37 PM ---------- Previous post was at 09:32 PM ----------
Dunno if u got the memo but our device does not support doze
Click to expand...
Click to collapse
Lol... Yeah, I knew, it's a typo. Supposed to say "that doesn't support doze'. My bad
Sent from my XT1575 using Tapatalk
@Razziell
EDIT NEW LINK:
AospExtended-v4.6-markw-20170917-1455-UNOFFICIAL
Really? Can u give us a feedback? Any bug?
N1ck474 said:
Really? Can u give us a feedback? Any bug?
Click to expand...
Click to collapse
I just bring the news. I didn't try
Sent from my Redmi 4 Prime using XDA Labs
aviranx said:
I just bring the news. I didn't try
Click to expand...
Click to collapse
Thank you.
N1ck474 said:
Really? Can u give us a feedback? Any bug?
Click to expand...
Click to collapse
Bugs:
With hal3 active there will be problems with the camera in third-party applications (the default is off)
The "menu" button is not configurable, is the "menu" always called? QRAttached fileFIX_FRAMEWORK.zip (9.27 MB)
There may be problems with the stock camera (if problems with other cameras do not go away) - QRAttached filemarkw-oss-cam.zip (724.45 KB)
It is possible to "stick" the notification of charging / connecting when disconnecting usb / charging (it is treated by resetting)
Setting it right now, it's surely more updated than Hrafninn's last RR rom, mostly for the new kernel with Wi-Fi updated drivers and hotplug, also with optional lowered Cpu freq at 400MHz. Customizations seems to be almost on par with RR, great!
Let's see with Greenify and some blocked alarms/wakelock, what autonomy can provide :fingers-crossed:
francescod said:
Setting it right now, it's surely more updated than Hrafninn's last RR rom, mostly for the new kernel with Wi-Fi updated drivers and hotplug, also with optional lowered Cpu freq at 400MHz. Customizations seems to be almost on par with RR, great!
Let's see with Greenify and some blocked alarms/wakelock, what autonomy can provide :fingers-crossed:
Click to expand...
Click to collapse
Also it have 2.21GHz max freq. that gives antutu over 65k and geekbench 4.500+. But that 400MHz is unusable. Kernel always switching between 652-2.21 GHz and when i tried to set minimum freq to 400MHz my device freeze and rebooted.
tanerwars said:
But that 400MHz is unusable. Kernel always switching between 652-2.21 GHz and when i tried to set minimum freq to 400MHz my device freeze and rebooted.
Click to expand...
Click to collapse
It depends on your specific Cpu and other variables, mine, for now seems to be stable...:fingers-crossed:
Anyway I saw there's a huge NETLINK wakelock denying the deepsleep of my device...Now I've deleted all my alarms and wakelock blocked things and from My Android Tools (maybe I was wrong on something that caused the wakelock) and it's fully charged stopped manually at 99%, let's see what happens. The wifi (maybe a little weaker than Miui) and bluetooth scanning are off. Charging was at high speed with original charger and Aukey "big" cable , Led was switched on immediately, but then I've charged with the device off, to speed up the process, and noticed that there's no percentage, only an empty animated icon. Fingerprint is ok, just few issues when trying to unlock on Nova Launcher's home page! I've found that give root to Nova instead of "administrator's privilege" is resolving this issue (Root is needed to use the "lock now button" with Nova).
I've also set the Low Cpu freq at 400MHz and limited the high at 2GHz instead of modified 2.2GHz. Today I'll test also the "equalizer" system app, that yesterday crashed when I opened up from inside Shuttle music app.
I hope to solve the wakelock problem.
Update
Using it right now and works perfectly
Is it support Substratum theming?
ghanipradita said:
Is it support Substratum theming?
Click to expand...
Click to collapse
Yes, it is full of OMS support
i notice the max cpu freq is 2.208 Mhz (overclocked) while our cpu maximum freq is 2.000 Mhz, correct me if i'm wrong, thats why the rom is so fast, is it safe for our cpu health?
rchmtsa said:
Using it right now and works perfectly
Click to expand...
Click to collapse
Share sot!
mikey000 said:
i notice the max cpu freq is 2.208 Mhz (overclocked) while our cpu maximum freq is 2.000 Mhz, correct me if i'm wrong, thats why the rom is so fast, is it safe for our cpu health?
Click to expand...
Click to collapse
Would like to know too!
mikey000 said:
i notice the max cpu freq is 2.208 Mhz (overclocked) while our cpu maximum freq is 2.000 Mhz, correct me if i'm wrong, thats why the rom is so fast, is it safe for our cpu health?
Click to expand...
Click to collapse
aviranx said:
Share sot!
Would like to know too!
Click to expand...
Click to collapse
Yes it's safe.It's a small overclock and beside that there are mechanisms like cpu throttling and core offline that prevent overheating.Also the rom is not fast because of that, you can barelly notice any improvement from a 10% speed increase.
What about battery? I'm on ViperOS right now because that Pixel Experience that offer, but I really want to try this one
---------- Post added at 05:06 AM ---------- Previous post was at 04:36 AM ----------
mikey000 said:
i notice the max cpu freq is 2.208 Mhz (overclocked) while our cpu maximum freq is 2.000 Mhz, correct me if i'm wrong, thats why the rom is so fast, is it safe for our cpu health?
Click to expand...
Click to collapse
Hey Mikey, I remember you told me that you was on Viper OS (I'm too right now). Between that one and this one, which is better in your experience?
Mangel79 said:
What about battery? I'm on ViperOS right now because that Pixel Experience that offer, but I really want to try this one
---------- Post added at 05:06 AM ---------- Previous post was at 04:36 AM ----------
Hey Mikey, I remember you told me that you was on Viper OS (I'm too right now). Between that one and this one, which is better in your experience?
Click to expand...
Click to collapse
I noticed AOSP extended faster, i like viper because it has built in dark theme
mikey000 said:
I noticed AOSP extended faster, i like viper because it has built in dark theme
Click to expand...
Click to collapse
On battery terms, have you noticed some important difference between them?
Mangel79 said:
On battery terms, have you noticed some important difference between them?
Click to expand...
Click to collapse
Haven't test battery life yet
-------
EDIT: It wasn't the ROM, it was my service, sorry. The ROM is perfect (until now)