Related
Have a question... What's the main benefict of using a stock based ROM? It will have all stocks apps, and have functional 4k recording and all those problems aosp suffer, or it's just because it's based on the stock ROM?
Like for example what does Cloudy ROM can have, that another ROM that isn't stock based can't.
Thanks in advance,
Hope you understand my question
Hgneto said:
Have a question... What's the main benefit of using a stock based ROM? It will have all stocks apps, and have functional 4k recording and all those problems aosp suffer, or it's just because it's based on the stock ROM?
Like for example what does Cloudy ROM can have, that another ROM that isn't stock based can't.
Thanks in advance,
Hope you understand my question
Click to expand...
Click to collapse
The "gimp" depends on which variant you have. Like the D855 has great aosp ROMs while others are getting issues here and there cause the 5.0 source hasn't been released for them yet.
So if you're one of those other variants, you can expect things like bad (or not as good) camera, sound issues (mainly music), not as good battery life (not major though) and modem/radio connection issues. That being said, some devices aren't getting those issues.
Also, stock is Kitkat while AOSP is on Lollipop. You gotta ask yourself if the extra features you're getting off AOSP are worth the bad things.
P.S.: I personally prefer AOSP but am waiting on source to use it as my daily.
I'm on 855, but I was talking about the stuff that I can do on Stock vs stock based ROM vs aosp ROM. Like 4k recording for example and duo window screen...
Sent from my G3
BWolf56 said:
The "gimp" depends on which variant you have. Like the D855 has great aosp ROMs while others are getting issues here and there cause the 5.0 source hasn't been released for them yet.
So if you're one of those other variants, you can expect things like bad (or not as good) camera, sound issues (mainly music), not as good battery life (not major though) and modem/radio connection issues. That being said, some devices aren't getting those issues.
Also, stock is Kitkat while AOSP is on Lollipop. You gotta ask yourself if the extra features you're getting off AOSP are worth the bad things.
P.S.: I personally prefer AOSP but am waiting on source to use it as my daily.
Click to expand...
Click to collapse
I'm on 855, see my previous post to see if you can understand what I'm asking.
Thanks in advance!
Hgneto said:
I'm on 855, see my previous post to see if you can understand what I'm asking.
Thanks in advance!
Click to expand...
Click to collapse
First, a tiny bit for Lollipop defenders. Yes, i always did a full wipe, always installed same apps set up in the same way manually. I always updated cust, rpm and tz to relevant versions. And i always gave system 24h to make all needed background syncs.
Official 5.0 is bad, because of:
1) Lags. Animation is still choppy. Applications are slow to launch, etc.
2) Heat. Phone heats up way more than on KK.
3) Battery. SOT is noticeably worse.
Since LL came out not too long ago, all AOSP roms based on it are still in alpha phase. I believe that most issues will be sorted out later.
AOSP LL is bad because of:
1) Lags. There is way less lags than on official LL, but there are sudden and unpredictable slowdowns.
2) Battery. It is worser than official LL, which makes it almost unusable. 4h SOT (in the same conditions in which official LL lasted 6 and KK 8) is bad.
3) Everything proprietary is more or less broken. Worse (Or none at all?..) low light algorithms in camera software, no Qmemo, etc etc etc.
My advice? Stay on KK for now. LL still needs a lot more polishing...
YaDr said:
First, a tiny bit for Lollipop defenders. Yes, i always did a full wipe, always installed same apps set up in the same way manually. I always updated cust, rpm and tz to relevant versions. And i always gave system 24h to make all needed background syncs.
Official 5.0 is bad, because of:
1) Lags. Animation is still choppy. Applications are slow to launch, etc.
2) Heat. Phone heats up way more than on KK.
3) Battery. SOT is noticeably worse.
Since LL came out not too long ago, all AOSP roms based on it are still in alpha phase. I believe that most issues will be sorted out later.
AOSP LL is bad because of:
1) Lags. There is way less lags than on official LL, but there are sudden and unpredictable slowdowns.
2) Battery. It is worser than official LL, which makes it almost unusable. 4h SOT (in the same conditions in which official LL lasted 6 and KK 8) is bad.
3) Everything proprietary is more or less broken. Worse (Or none at all?..) low light algorithms in camera software, no Qmemo, etc etc etc.
My advice? Stay on KK for now. LL still needs a lot more polishing...
Click to expand...
Click to collapse
Not deciding between lolipop or kitkat, just trying to decide either to go stock based ROM or aosp ROM...
Hgneto said:
Not deciding between lolipop or kitkat, just trying to decide either to go stock based ROM or aosp ROM...
Click to expand...
Click to collapse
Then read the last part Stay on stock, customs aren't ready yet.
Hgneto said:
Not deciding between lolipop or kitkat, just trying to decide either to go stock based ROM or aosp ROM...
Click to expand...
Click to collapse
YaDr said:
Then read the last part Stay on stock, customs aren't ready yet.
Click to expand...
Click to collapse
There are stock based (KK) custom ROMs that do just fine. I would definitely go with stock based atm. AOSP needs polishing.
BWolf56 said:
There are stock based (KK) custom ROMs that do just fine. I would definitely go with stock based atm. AOSP needs polishing.
Click to expand...
Click to collapse
So basically you are all saying that for AOSP only on Kitkat and for lollipop I should stay on stock based ROM's for now?
Thanks!
Sent from my G3
Hgneto said:
So basically you are all saying that for AOSP only on Kitkat and for lollipop I should stay on stock based ROM's for now?
Thanks!
Sent from my G3
Click to expand...
Click to collapse
I believe that most if not all AOSP ROMs are on LL.
Idk about D855 LL stock based ROM but KK performs great. Imo, just test them and see which one your prefer.
What is this:
This is Stuxnet a custom kernel for Android, this kernel focuses on simplicity and stabiilty. All features on this kernel are based on long hours of testing and all are thoroughly tested to give end users the best experience for their device.
Stuxnet is mostly stock with optimizations and features that are often used by users that are not affecting performance on their device. Future development of this kernel will focus on Performance and Stability.
So enough with the intro and start testing this on your device.
Features:
Based on Xiaomi kernel source
Fully Optimized Kernel
Sound Control
FSYNC Control
Voltage Control
MSM Hotplug
Thermal Enhancements
USB Fast Charge
Check Github and/or Gitlab for full changelog
How To's:
Install in recovery
No need to wipe (unless you want to wipe your a$$)
Reboot
Kiss yo' mama
***** Slap an iPhone user.. Smile!
Enjoy
Credits:
Google
CyanogenMod
Linux
SimpleAOSP
and all custom kernel devs
Download:
CM
MIUI
Kernel has two builds Stable and Nightlies
WARNING!
This kernel is only compatible on CM based ROMs.
~End
Donations:
@morpheus620 - $15
@gary138.138 - $15
@Riichard63 - $20
Thanks man!
Will test it soon! Sorry for the Noob question but can you tell me if it can be used for building cm11. I am a noob in android development.
I'm using this at the moment on XenonHD. So far everything is working. And that smoothness....its off the charts! xD Btw Dev @Gnome, can you add Lionheart and Sio on the next release?
And LCD KCAL please.
Gnome said:
One More!
Click to expand...
Click to collapse
Thanks
Sent from my MI 3W using XDA Free mobile app
I just flashed this kernel on the XeonHD 4.25 build.
Hoping that they are good partners.
This is just a preview, I'll be adding some stuff from my previous kernels soon... just checkout my git for changelogs and also check the download page for new releases.
Gnome said:
This is just a preview, I'll be adding some stuff from my previous kernels soon... just checkout my git for changelogs and also check the download page for new releases.
Click to expand...
Click to collapse
Ooohh yeaahh! E. A. G. E. R. L. Y waiting. XD
Working on Bitti09's CM12.1 confirmed
No new governors yet! Waiting!
On Revolution Remix rom, i got camera fixed, and after using the GPS fix app, it fix the gps fery fast.. so, so far everything working!
Thanks a lot, @Gnome!
Jhayzt said:
And LCD KCAL please.
Click to expand...
Click to collapse
+1
I used KCAL controls on StellAR and the difference was AMAZING! (alas StellAR doesn't gel with XenonHD for me)
SharksT said:
On Revolution Remix rom, i got camera fixed, and after using the GPS fix app, it fix the gps fery fast.. so, so far everything working!
Click to expand...
Click to collapse
*Resurrection
UPDATE: @Gnome I flashed the kernel, everything seems to be working fine (WiFi, Sound mods etc).
But call bug v1 seems to be present (touchscreen active during call)...can't comment about call bug v2 (screen-off death) yet, but I hope it's not here, cuz I plan to use this kernel as my driver...
The Dork Knight Rises said:
UPDATE: @Gnome I flashed the kernel, everything seems to be working fine (WiFi, Sound mods etc).
But call bug v1 seems to be present (touchscreen active during call)...can't comment about call bug v2 (screen-off death) yet, but I hope it's not here, cuz I plan to use this kernel as my driver...
Click to expand...
Click to collapse
Sorry, can you make difference in V1 call bug and V2.
I missed something obviously
P.s. OP thanks for 1st OPEN ANDROID development thread wort mention
Gonna try after Worker's day
sudy_freak said:
Sorry, can you make difference in V1 call bug and V2.
I missed something obviously
P.s. OP thanks for 1st OPEN ANDROID development thread wort mention
Gonna try after Worker's day
Click to expand...
Click to collapse
Yeah, call bug v1 is something most ppl who recently joined the Mi3 forums won't have faced.
It is one of the major bugs (aside from deep sleep reboot) that was there in the original Lollipop ROMs for cancro. It was fixed a long time ago (by audahadi and Bitti I believe, as Ivan's ROMs had the bug for a long time afterwards too).
The bug was that the touchscreen would remain active when you're in a call and the proximity sensor turns the screen off. It would cause the notification/quicksettings panel to be pulled down or brightness to be changed due to contact with ear or cheeks. Other more complex things could also happen like when I once turned on Airplane mode while talking and got disconnected :laugh:
And call bug v2 is a new bug that seems to affect ROMs (except I believe Ivan's AOSP and SOKP which switched to Ivans kernel I think) since 5.1...
While calling (or sometimes VERY RARELY while doing something else) the phone kind of hangs, the screen goes dark and it goes into a screen of death mode. Nothing can be done, your only option is to press and hold Power button for a very long time (approx 12-15 secs; much longer than a normal hard reset ~8secs) to hard reboot your phone.
Hope you got it. :good:
PS. Yes, try this kernel. You won't be disappointed.
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Gnome said:
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Click to expand...
Click to collapse
Thanks Dev @Gnome! I'm trying it at the moment.
Wow, using alpha 3 working great even on temasek 10.6 by moonlight, just waiting another hotplug, IO Scheduler, CPU & GPU Governors, btw can you make a little downclock and overclock cpu freq tables? Thx for great kernel....
Gnome said:
Added some under the hood stuff on 3rd build, also check if fast charge works, since it works fine on my end.
Click to expand...
Click to collapse
Fast charge!
Very useful!
I'll try this asap.:laugh:
@Gnome , Buddy thanks for your work gonna try it soon
just a query
there are two build dated 30-4-15
Alpha 3 and Alpha Z
whats the difference which one to flash
ZenR2 said:
@Gnome , Buddy thanks for your work gonna try it soon
just a query
there are two build dated 30-4-15
Alpha 3 and Alpha Z
whats the difference which one to flash
Click to expand...
Click to collapse
dont mind the Lettered version, just flash the numbers.
Gnome said:
dont mind the Lettered version, just flash the numbers.
Click to expand...
Click to collapse
buddy flashed the alpha 3 build , but now wifi is not working on latest Xenon Hd rom
What is the current most stable Android Lollipop ROM? Need one that is closest to AOSP and least amount of bugs with things like the Camera etc.
@Ziyan's zmod is a stable basic rom. All 5.1 roms for GN have ~250MB less available RAM than 4.x roms, because of a deficiency with the kernel. The lack of optimization for 5.1 means skippy performance and worse multitasking. So the problem now isn't stability
What exactly is that about deficiency of the kernel @bamtan2?
-V-O-Y-A-G-E-R- said:
What exactly is that about deficiency of the kernel @bamtan2?
Click to expand...
Click to collapse
Apparently the combination of Android 5 and the old 3.0 kernel means the developers must reserve RAM permanently for some features, like the camera. This is called a memory "carveout". The 3.4 kernel would let developers stop wasting that RAM. But making a new kernel is a lot of work...
Here is a list of (some) developers who have helped bring Galaxy Nexus from Android 4.3 up to 5.1: https://github.com/MWisBest/android_manifest THE OMAP4XXX TEAM by @MWisBest
So that's why all the 5.x ROMs I've tried so far become sluggish in matter of hours
So the best solution would be going back to 4.4?
-V-O-Y-A-G-E-R- said:
So that's why all the 5.x ROMs I've tried so far become sluggish in matter of hours
So the best solution would be going back to 4.4?
Click to expand...
Click to collapse
If ZMOD + whatever tweaks you choose is still too slow for you, then yes, 4.x would be more polished in some ways! But some of the best 4.x ROMs are unfortunately disappearing from the internet even though they work well. Software doesn't "age" the same way hardware does Ideally the old releases would be re-built with the latest security patches and kept online for people to download. Exactly what ROM is best for you is hard to say without a lot of personal testing.
Thanks for a new keyword to google (ZMOD)
GNE is my secondary phone, I'd like to have it around and to be able to count on it should I need it.
I like to have Xposed and even the stock ROM would be totally acceptable then (well, "stock" feature-wise), without any bloat. Any recommendations for 4.4 or 5?
Thanks for the info so far.
I was leaning towards ZMOD, thanks for explaining the kernel issue.
-V-O-Y-A-G-E-R- said:
Thanks for a new keyword to google (ZMOD)
GNE is my secondary phone, I'd like to have it around and to be able to count on it should I need it.
I like to have Xposed and even the stock ROM would be totally acceptable then (well, "stock" feature-wise), without any bloat. Any recommendations for 4.4 or 5?
Thanks for the info so far.
Click to expand...
Click to collapse
Best bet is to stick with Ziyan
Howdy!
I hereby offer an alternative build of the latest visi0nary's kernel.
The original thread is located here
Please note that the credits remain with BlueFlame4 (the maker of visi0nary's kernel), as this is the same kernel, just differently built.
Some years ago I spent many months trying to optimize UI smoothness and power consumption for a kernel of a different device, in which I succeeded.
From this time I remember some build flags and kernel config settings that improved (scrolling) smoothness and power consumtion for that device at that time.
So, in an attempt to do the same for the P9000, I re-built the latest visionary's kernel with the following differences:
different/improved build flags
minor changes in kernel defconfig
compiled using a self-compiled sabermod toolchain
With these changes in the build process I try to achieve the following things:
improved smoothness/snappiness of the UI (NOT higher benchmarks - I just want the user experience to be as smooth as possible, benchmarks do not really matter)
improved (lower) power consumption
The built kernel feels improved in smoothness to me, but this might be my own biased opinion.
Anyway, I would appreciate, if some of you good people could use this kernel as a daily driver, in order to see after a few days, if there are really any noticable improvements over the original build of visi0nary's kernel. Please report back in this thread, thank you.
Installation: just flash in recovery - delete cache & dalvik cache afterwards (also in recovery, after kernel flash)
Attention: this build is not for cyanogenmod - it's for Stock P8000 ROM or other Stock-based ROMs like Eragon (I'm using it on the latest Eragon myself).
To verify that you are running the alternative build, you will see a "-gueste" (that's me) appendend to the kernel version number (see attached screenshot).
Thanks mate.
I will flash it to See if something is different/improved
Wish you all the best for this project!
Thanks Allways glad to see effort.
Testing will return with feedback.
Thanks for the kernel. I've just flashed it and so far I see that when you go directly to the battery menu from the notification bar, that menu is much snappier. On the stock and on visionary's kernel you had to wait a little bit to see the details of specific apps draining the battery. That's the feedback which I can say now, I'll try to give information about the power consumption in the future. Thanks for developing!
Thanks in advance at all.
For me so far power consumption seems to be very good (while it is not bad on the original build either). I'm anxious to see, how it will compare to the original build after 2 more days.
Hello! I have just fleshed the phone with this kernel. Seems great for now. Will update you for the power consumption in the near future.
P.S Im so happy that someone has taken over this project, and I hope it will keep you developing it!
boka18 said:
Hello! I have just fleshed the phone with this kernel. Seems great for now. Will update you for the power consumption in the near future.
P.S Im so happy that someone has taken over this project, and I hope it will keep you developing it!
Click to expand...
Click to collapse
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Stefan Gündhör said:
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Click to expand...
Click to collapse
Feel free - that's the spirit of open source! My P8000 is already on eBay so I'll visit this forum less and less. It's good to see people picking up my work though!
Stefan Gündhör said:
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Click to expand...
Click to collapse
I understand completely, but I DO hope that u will be able to continue optimising this great kernel!
What new in this kernel?
What the bug fix?
Okalash said:
What new in this kernel?
What the bug fix?
Click to expand...
Click to collapse
Pro Tip: Read the OP :laugh:
For me so far battery life seems to be very good.
After 2 days and 10 hours of uptime I still got 42% battery.
Now this value is not very informative, as it depends heavily on the usage of the phone.
Compared to the original build of the kernel at least power consumption seems to be better on my phone.
During phone uptime I occasionally played games (not very long though), was connected to bluetooth and wifi many hours, browsed through the web regularly and had only few and short phone calls. Over night for some hours I was in flight mode, while last night I wasn't.
Thank you for continuing the project! I flashed the rebuilt kernel because I had a "feeling" that the battery performance of the original Visi0nary kernel was somewhat lower than the stock kernel. (But maybe I am mistaken.)
So far I have no problems with the rebuild kernel. It is too early to comment on battery performance.
Does it make sense to run Skeleton's Seeder app (part of Eragon ROM) in conjunction with this custom kernel?
Moreover, is there any chance to port the P7000 kernel scripts that enable Android device encryption into this P8000 kernel/Eragon ROM? See http://forum.xda-developers.com/elephone-p8000/general/dev-cwm-elephone-p8000-t3200296/page11 The lack of device encryption is my main gripe with the P8000. Apart from that, I love this phone.
-Tiz- said:
Does it make sense to run Skeleton's Seeder app (part of Eragon ROM) in conjunction with this custom kernel?
Click to expand...
Click to collapse
This rebuild of visionary's kernel is feature-equivalent to the original build. So, yes, you can use the seeder app (I use it myself).
Regarding device encryption you need to understand that it has been left out of the ROM most likely on purpose, because this is a China-phone, and the chinese government is quite restrictive on encryption. And as Eragon (same as other stock-based ROMs) is based on the stock ROM, this feature is missing there as well.
This means, depending on the effort, Elephone made, to remove this feature from Android, it might be possible to reactivate it, it's just a matter of (testing) time.
I haven't tried with other ROMs like Cyanogenmod, but in theory it should work there.
As far as I have seen, the to enable encryption for P8000 stock and stock-based ROMs we would need to modify one or more scripts of the P8000 ramdisk (for example the russian guy you linked added in init.environ.rc:
Code:
export LD_PRELOAD libsigchain.so
And there are also a couple of other differences in the other rc scripts. It's not exactly clear (to me), which changes in the end are required for encryption to be enabled. Also we don't know if after these changes, the encryption option will magically appear in the device settings, or if we need to enhance the menu ourselves.
Furthermore, the russian guy mentions, that we might have to modify and rebuild the sepolicy binary file located in the ramdisk, in order to get selinux (security enhanced linux) to permit our changes (but I don't know if we would need that just for the encryption feature, as init.d already works for P8000 as opposed to P7000 - correct me if I'm wrong).
So to sum up, this sounds like a lot of testing, which I personally don't have the time for But maybe someone else does.
Don't take the Android encryption feature too seriously - at least not, if you are trying to hide from government. However, if you are trying to protect your data from normal people, it surely would be nice to have.
Stefan Gündhör said:
Tin order to get selinux (security enhanced linux) to permit our changes (but I don't know if we would need that just for the encryption feature, as init.d already works for P8000 as opposed to P7000 - correct me if I'm wrong). ...
However, if you are trying to protect your data from normal people, it surely would be nice to have.
Click to expand...
Click to collapse
Thanks. It is also my understanding that init.d already works for Eragon ROM. Therefore, I was hoping that it might be relatively easy to enable encryption. On the P7000, it seems that the menus simply appeared once the scripts were implemented. Wooster even talked about the possibility to make a "blind" patch for the the P8000.
Moreover, I agree that Android device encryption might not be 100% bullet-proof. However, it would allow me and others to sufficiently protect private email passwords and work-related data (e.g. if the phone gets lost or stolen). By contrast, the screen lock is no protection at all. In particular, if a custom recovery is installed ...
It appears that I am not the only P8000 owner who has a vital interest in device encryption:
http://bbs.elephone.hk/thread-6924-1-1.html#.Vow51hBukwE
http://bbs.elephone.hk/thread-9012-1-1.html#.Vow51xBukwE
Tonight I will download and test it
I don't care much about encryption, but God, I would pay for someone who could actually SOLVE the sub-15% sudden battery charge. Any chance you can look into/fix it, Stefan? You look like one of our potential hopes, haha
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
BlueFlame4 said:
Feel free - that's the spirit of open source! My P8000 is already on eBay so I'll visit this forum less and less. It's good to see people picking up my work though!
Click to expand...
Click to collapse
Hi, sorry to ask but why exactly? Got a new/better phone? Got tired of the P8000 bugs/camera? In time, which phone did you get?
Best regards
Rizera said:
Hi, sorry to ask but why exactly? Got a new/better phone? Got tired of the P8000 bugs/camera? In time, which phone did you get?
Best regards
Click to expand...
Click to collapse
No problem, haha. Well, I bought this phone because I want to learn how to port CM or ROMs in general onto other devices and how Android works internally. Unfortunately MediaTek SoCs are quite beginner-unfriendly so I'll go for Qualcomm for now. Just got my Elephone Trunk btw Also there's basically zero "from source" development going on the the P8000 and it's not really fun to do all the things completely alone.
Cheers!
1.
Battery performance of the newly built kernel seems to be good. Heavy WLAN browsing still quickly kills the battery. But I could imagine that this is a hardware issue (power inefficient Mediatek WLAN modem?).
2.
"Also there's basically zero "from source" development going on the the P8000 and it's not really fun to do all the things completely alone. " Sad but true.
Announcing kernel "guestekrnl" (based on the latest version of visi0nary's kernel): http://forum.xda-developers.com/elephone-p8000/orig-development/kernel-guestekrnl-v1-6-2-t3287518
Hello dear community. I want to change to a cm/AOSP ROM but i dont know who to Choosing. I want a Stable rom with good battery life. And If You want guys , please share you'r kernel setting for best battery life. Thanks ( i have a medium usage with FB,messenger,Instagram,YouTube) not games.
Hey, when i use cm or aosp based roms i always come back to aicp because of features like aokps fling navigation bar. But all CM based roms will have same bugs as cm/lineage itself
I always use the kernel wich comes with the rom and i dont know about kernel tweaks and settings
This is a real personal choice. I use only MM based ROMs because of the issues all N ROMs currently have. I hope that they get those issues fixed and encryption will work some day but atm this all is a no go for me to go to N.
Regarding battery life there are 2 main components regardless of any ROM you choose:
1) use MSM hotplug (enable that with the app kernel adiutor)
The kernel needs to support that which is maybe not the case for all ROMs but you can always flash llama kernel which supports that
2) display
It makes a dramatically difference how much you increase the max brightness level of the display
There are thousands of other things especially logd process and Google services which could drain battery and there are thousands of tweaks out there trying to give you more battery life but my personal experience is that the above 2 things are the most important ones.
#
Sent from my LG-H815 using XDA Labs
steadfasterX said:
This is a real personal choice. I use only MM based ROMs because of the issues all N ROMs currently have. I hope that they get those issues fixed and encryption will work some day but atm this all is a no go for me to go to N.
Regarding battery life there are 2 main components regardless of any ROM you choose:
1) use MSM hotplug (enable that with the app kernel adiutor)
The kernel needs to support that which is maybe not the case for all ROMs but you can always flash llama kernel which supports that
2) display
It makes a dramatically difference how much you increase the max brightness level of the display
There are thousands of other things especially logd process and Google services which could drain battery and there are thousands of tweaks out there trying to give you more battery life but my personal experience is that the above 2 things are the most important ones.
#
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Thanks for information man, i think i flash RessurectionRemix with llama sweet , i will activate hotplig and apply zzgovernor. But wich program to use to reduce wakelocks because amplify and xposed isn't ready for android N
piturcaandrei97 said:
Thanks for information man, i think i flash RessurectionRemix with llama sweet , i will activate hotplig and apply zzgovernor. But wich program to use to reduce wakelocks because amplify and xposed isn't ready for android N
Click to expand...
Click to collapse
See that is just one more reason why Nougat on this device is not production ready ... Imho..
Edit:
I recommend RR 5.7 + llama + greenify (donation edition ) + Xposed to enable advanced greenify settings
You could also give slim rom MM a try in general forum..
Sent from my LG-H815 using XDA Labs
You can try resurrection remix 5.7.4 mm I think is full and more stable rom.
For kernel I am comfiest too and try to found the good settings too.
Don't use N roms are not ready yet for me.
Good luck.
steadfasterX said:
This is a real personal choice. I use only MM based ROMs because of the issues all N ROMs currently have. I hope that they get those issues fixed and encryption will work some day but atm this all is a no go for me to go to N.
Regarding battery life there are 2 main components regardless of any ROM you choose:
1) use MSM hotplug (enable that with the app kernel adiutor)
The kernel needs to support that which is maybe not the case for all ROMs but you can always flash llama kernel which supports that
2) display
It makes a dramatically difference how much you increase the max brightness level of the display
There are thousands of other things especially logd process and Google services which could drain battery and there are thousands of tweaks out there trying to give you more battery life but my personal experience is that the above 2 things are the most important ones.
#
Click to expand...
Click to collapse
What are the issues on N, apart from encryption and video recording? I'm torn between 13 and 14, my inner self is not OK with running without encryption ;d
goorek said:
What are the issues on N, apart from encryption and video recording? I'm torn between 13 and 14, my inner self is not OK with running without encryption ;d
Click to expand...
Click to collapse
its not stable as MM. and has lot of bugs. no video recording unless you select api2. no xposed and its no longer CM its LAOS. and they building again like they started to build from scratch so i believe.
That's my question, apart from video recording I don't see any bugs. And they don't start from scratch, it's just cm with different name.
goorek said:
What are the issues on N, apart from encryption and video recording? I'm torn between 13 and 14, my inner self is not OK with running without encryption ;d
Click to expand...
Click to collapse
I just followed the cm thread since a while and saw issues but I don't remember all of them. there were issues with screen lock with f2fs with camera with Xposed and some more. What's left is my feeling that I don't trust in N for the moment..
Sent from my LG-H815 using XDA Labs