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.
Related
I installed Joe RCU kernal and im using cm7, How can i undervolt my sensation for better battery life?
Thanks
malberti1993 said:
I installed Joe RCU kernal and im using cm7, How can i undervolt my sensation for better battery life?
Thanks
Click to expand...
Click to collapse
System tuner by 3c available in the market.
Matt
yeah i did that but under voltage it says not available.
Mike
Remove any overclocking app you have, if you are using one.
Go to the market, download System Tuner app by a developer named 3c.
Set your clock frequency to whatever you want to by opening the app and going to th tab named Tweaks.
Then, once on the Tweaks tab, click Voltage.
On the bottom left, there will be a button that says "-12.5mV", hit that exactly 7 times. That's the safest voltage that I have seen it can go, altough certain phones can go lower.
To the right, click boot setting and click on re-apply cpu settings at boot, and you're set.
You are now undervolted.
---------- Post added at 10:27 PM ---------- Previous post was at 10:26 PM ----------
malberti1993 said:
yeah i did that but under voltage it says not available.
Mike
Click to expand...
Click to collapse
Did you give it Super User permission? Did you also hit the cpu tab before the voltage tab?
I updated superuser and it worked.
Whats a safe undervolting voltage and also how much battery life is going to be improved?
playing with undervolts and it seems the lowest voltage is fixed to 812500
i'm guessing, it's set by kernel, but i wonder, if i can lower it even more?
The phone is extremely slow with this kernel. Am i doing something wrong!? What app to use with this kernel to set the speeds and all that?
Ok so I just played with daemon tool and the phone is a lil faster. What settings are h guys running and what governor? Also what's the difference between them?
Help please i dont want to damage my phone running the wrong settings.
Am running min freq. 192000
Max freq on 1536000
Governor smartassV2.
antrax360 said:
Am running min freq. 192000
Max freq on 1536000
Governor smartassV2.
Click to expand...
Click to collapse
Hi,
192000 & 1512000 are good settings.
malybru said:
Hi,
192000 & 1512000 are good settings.
Click to expand...
Click to collapse
I dont have 151. 153 is the lowest on the 150 range
antrax360 said:
I dont have 151. 153 is the lowest on the 150 range
Click to expand...
Click to collapse
Hi,
153 is fine as well.
switch to ondemand governor. and you might want to switch to 1.4r1 bricked kernel for sense 3.0 aka (3.6.x) thats the best version next to 0.91 for sense 3.0
rddocke said:
switch to ondemand governor. and you might want to switch to 1.4r1 bricked kernel for sense 3.0 aka (3.6.x) thats the best version next to 0.91 for sense 3.0
Click to expand...
Click to collapse
What's the difference between ondemand and smartass?
To my experience smartass is more conservative than ondemand but ondemand is better at performing and conserving energy when not in use. It has a better balance it will know when you max out performance and when not to so battery still lasts long and performance is maximized
Sent from my HTC Sensation Z710e using XDA App
antrax360 said:
The phone is extremely slow with this kernel. Am i doing something wrong!? What app to use with this kernel to set the speeds and all that?
Click to expand...
Click to collapse
Have you tried a reboot? Most of the time, flashing a new ROM/kernel requires a reboot before the phone acts normal.
Matt
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.
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.
@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)