Is there any rom based on cm13 enables to customize screen colours saturation ????
like the features present in custom kernel for miui (screen colour)
I'm currently working on CM13 based kernel with KCAL support. The first beta should be ready in the next couple of days. Can't give exact time because I'm testing it right now, but boy with the lack of custom kernels currently for RMN3, this probably will be on every rooted phone here
ktomov said:
I'm currently working on CM13 based kernel with KCAL support. The first beta should be ready in the next couple of days. Can't give exact time because I'm testing it right now, but boy with the lack of custom kernels currently for RMN3, this probably will be on every rooted phone here
Click to expand...
Click to collapse
Could you add kernel same page merging to it? It reduces RAM usage a lot
Grantius said:
Could you add kernel same page merging to it? It reduces RAM usage a lot
Click to expand...
Click to collapse
Yeah, but on cost of cpu. I don't really see a reason to have it on a device with 3gb of ram. Will think about it but that's on the end of the feature list that I need.
Edit: Well that was easy. You'll have KSM in the kernel.
Personally, i don't understand why people complain about "omg ram usage too high" on 2gb or 3gb devices. It's like they expect to see 80% free ram all the time. Some even have a habit of constantly killing all apps/processes to get ram back from the system. The truth it though, letting android fill it up with cache seems to make more sense to me. Like in a PC, what's the point of having 16gb ram if i'm going to make sure it's always 80% free ram. Android clears the ram out when it needs it anyway. But that's just a personal opinion.
I think i would settle for Qualcomm Assertive Display, quite useful under sunlight. Then again, contrast/gamma adjustment would be awesome too. HAHAHA looks promising
shaanyt said:
Personally, i don't understand why people complain about "omg ram usage too high" on 2gb or 3gb devices. It's like they expect to see 80% free ram all the time. Some even have a habit of constantly killing all apps/processes to get ram back from the system. The truth it though, letting android fill it up with cache seems to make more sense to me. Like in a PC, what's the point of having 16gb ram if i'm going to make sure it's always 80% free ram. Android clears the ram out when it needs it anyway. But that's just a personal opinion.
I think i would settle for Qualcomm Assertive Display (QAD), quite useful under sunlight. Then again, contrast/gamma adjustment would be awesome too. HAHAHA looks promising
Click to expand...
Click to collapse
True, I'm happy with 3GB of RAM, and always running my phone with all of my favourite apps till the Free RAM is just about 300MB. Killing apps like a Madman is not Multitasking. Just run it and minimise it, let the Android manage the tasks for us, switching between apps would be quicker, no constabt apps reload, and so on.
Forget about it because I would like to discuss about Qualcomm Assertive Display.
In every CM13 ROMs out there, the property for QAD was present in the build.prop, but it's pointing to the wrong path, the config file for QAD was never existed in CM13. So I study how MIUI handles QAD and modify current CM13 build.prop (I'm using the TheStrix build with F2FS support, plus TWRP he made for F2FS) on my phone.
Original property for QAD on CM13 ROM:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/data/misc/display/ad_calib.cfg
Check that '/data/misc/display/ad_calib.cfg' on your phone, it's missing and nowhere to be found.
So I take the calibration config file from MIUI 8 (/system/etc/calib.cfg) for the QAD and then put the file into current CM13 setup on my phone (/system/etc) and edited the CM13 build.prop following the MIUI build.prop, to become like this:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/calib.cfg
ro.qcom.ad.sensortype=2
And LiveDisplay now works flawlessly by setting it on Automatic, not bugged/stuck anymore.
Dude, let's try and share your experience. My eyes are not that color sensitive, so maybe you could see the difference.
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
True, I'm happy with 3GB of RAM, and always running my phone with all of my favourite apps till the Free RAM is just about 300MB. Killing apps like a Madman is not Multitasking. Just run it and minimise it, let the Android manage the tasks for us, switching between apps would be quicker, no constabt apps reload, and so on.
Forget about it because I would like to discuss about Qualcomm Assertive Display.
In every CM13 ROMs out there, the property for QAD was present in the build.prop, but it's pointing to the wrong path, the config file for QAD was never existed in CM13. So I study how MIUI handles QAD and modify current CM13 build.prop (I'm using the TheStrix build with F2FS support, plus TWRP he made for F2FS) on my phone.
Original property for QAD on CM13 ROM:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/data/misc/display/ad_calib.cfg
Check that '/data/misc/display/ad_calib.cfg' on your phone, it's missing and nowhere to be found.
So I take the calibration config file from MIUI 8 (/system/etc/calib.cfg) for the QAD and then put the file into current CM13 setup on my phone (/system/etc) and edited the CM13 build.prop following the MIUI build.prop, to become like this:
Code:
# Qualcomm
ro.qualcomm.cabl=2
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/calib.cfg
ro.qcom.ad.sensortype=2
And LiveDisplay now works flawlessly by setting it on Automatic, not bugged/stuck anymore.
Dude, let's try and share your experience. My eyes are not that color sensitive, so maybe you could see the difference.
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
I'll try later tonight hahaha. But i think it's easier to notice if u point a flash light at the light sensor, then drag down notification, if the super dark gray toggles become like light gray (since QAD is mainly for sunlight visibility, it changes "dark stuff" into less dark so that we can see that there's something there), then it works that's how i tested last time when i was using MIUI... it's very very high tech testing method.
Update : Just tried it. it boots, but no changes in contrast / black level under intense light. Usually for QAD if there's strong light on the ambient light sensor, QAD causes the black levels to become more gray so we see better, i tried this and nothing happened. Perhaps it needs to be kernel supported or something. #sad hahahha
shaanyt said:
Check that '/data/misc/display/ad_calib.cfg' on your phone, it's missing and nowhere to be found.
So I take the calibration config file from MIUI 8 (/system/etc/calib.cfg) for the QAD and then put the file into current CM13 setup on my phone (/system/etc) and edited the CM13 build.prop following the MIUI build.prop, to become like this:
And LiveDisplay now works flawlessly by setting it on Automatic, not bugged/stuck anymore.
Dude, let's try and share your experience. My eyes are not that color sensitive, so maybe you could see the difference.
Sent from my Redmi Note 3 using XDA Labs
I'll try later tonight hahaha. But i think it's easier to notice if u point a flash light at the light sensor, then drag down notification, if the super dark gray toggles become like light gray (since QAD is mainly for sunlight visibility, it changes "dark stuff" into less dark so that we can see that there's something there), then it works that's how i tested last time when i was using MIUI... it's very very high tech testing method.
Update : Just tried it. it boots, but no changes in contrast / black level under intense light. Usually for QAD if there's strong light on the ambient light sensor, QAD causes the black levels to become more gray so we see better, i tried this and nothing happened. Perhaps it needs to be kernel supported or something. #sad hahahha
Click to expand...
Click to collapse
Then I'm sure it's that 'Automatic Contrast' settings under MIUI which controls the QAD. And unfortunately there are no custom kernel at this point that supports that MIUI feature since no source code given.
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
Then I'm sure it's that 'Automatic Contrast' settings under MIUI which controls the QAD. And unfortunately there are no custom kernel at this point that supports that MIUI feature since no source code given.
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
i suppose the config library thingy depends on a certain variable being set to tell it to start its job. Maybe if we know what it depends on, we can activate it or something. Or, just a random thought, the sensortype thing is wrong, at least, for CM13, maybe it should be another number? Since i have no idea what that string means.... i know it declares sensortype, but i don't know what 2 is
shaanyt said:
i suppose the config library thingy depends on a certain variable being set to tell it to start its job. Maybe if we know what it depends on, we can activate it or something. Or, just a random thought, the sensortype thing is wrong, at least, for CM13, maybe it should be another number? Since i have no idea what that string means.... i know it declares sensortype, but i don't know what 2 is
Click to expand...
Click to collapse
I shall try to compare Stock MIUI kernel with CM13 kernel later...
Sent from my Redmi Note 3 using XDA Labs
MOVZX said:
I shall try to compare Stock MIUI kernel with CM13 kernel later...
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Weird thing is, even the QCOM AOSP 5.1.1 ROM that was "leaked" doesnt have assertive display activated LOLLLL
Update : BTW I have two redmi note 3s; 1 on MIUI, 1 on CM13. QAD (when it works) does make the screen easier to look at under strong lighting as it shifts the black level and contrast, but i found out that QAD is very buggy on China Developer ROM MIUI 8, it rarely works. Sometimes u need to reboot a few times for it to work, then if u reboot, it's gone again...
So I'll just wait for this kcal kernel hahaha
@ktomov Elementalx nice man. Looking forward to this kernel. Then we can unlock our dragon
Related
]Finally is here. Marshmallow 26.3.A.0.131 update bring us so wanted improvements.
Here you can post your thoughts, performance reports, or possible bugs you may found.
First what get better:
1. Overall performance - is so smooth, every menu scroll fast.
2. Camera - i can't confirm, seems little bit better
3. WIFI - Wow so much better, before i was trying couple times until get connected, now is instant.
4. Actual perfomance - I make test with Antutu, Asphalt etc. Is much, much better. Antutu score on Android 5 was around 29 k and 30 k max. Marshmallow wake the beast and score now is 32 k. Asphalt 8 is playable on medium settings, before very low settings was only way to play it normal. Do you know why? CPU isn't limited anymore 4 cores on 1.46 Ghz and 0.8 Ghz for the second 4 cores.
What wasn't fix, or improve:
Apps opening time
Overheating is same as before
Low storage
More perfomance needed
Sites loading is slow as before
I found two bugs, the one bug is in the dialer the letters under the numbers are repositioned a little bit, and idk if this is a bug but the status bar doesn't take the color of the app you are using
nrokos said:
...
and idk if this is a bug but the status bar doesn't take the color of the app you are using
Click to expand...
Click to collapse
I think it's called "feature", you may want to try What's New (Play Store) themes if you'd like colourful status-bar. It looks like that stock themes prefer black status bars now.
http://forum.xda-developers.com/cro...ix-stock-mm-themes-black-statues-bar-t3392565
Seems to be a bug, Detect USB device does not make sense without OTG.
The update is fine but a little bit disappointed specially on performance, apps are still opening very slow although UI is faster, at least now we have a better multitasking performance and no more bugs on RAM.
I had about 35k score in Antutu so MM sucks.
Mobile Data got buggy for me, didn't work until restart. Guys what happening with the Speaker it was so loud before now is very reduced i check settings nothing to about it.
depressed_ said:
I had about 35k score in Antutu so MM sucks.
Click to expand...
Click to collapse
I have 35k on MM... E2303 Model.
Performance will always be the same coz of the ****ty chipset thats inside m4 aqua. Yes, Snapdragon 615 is pile of crap
well, this is my MM result on antutu.
Andrew21P said:
well, this is my MM result on antutu.
Click to expand...
Click to collapse
Damn, did u anyhow change settings, tweaked MM or something like that?
depressed_ said:
Damn, did u anyhow change settings, tweaked MM or something like that?
Click to expand...
Click to collapse
Nope, my M4 Aqua is almost out of the box, 100% stock, bootloader locked, never root, just updated via Xperia Companion a few hours ago.
I don't like the fact that mpdecision is not included in the new update. it gives me huge battery drain.
Anyone have problems with gallery apps? My pictures doesn't render to be watched, only a black screen, the files are ok and the SD Card is new
7564321 said:
Mobile Data got buggy for me, didn't work until restart. Guys what happening with the Speaker it was so loud before now is very reduced i check settings nothing to about it.
Click to expand...
Click to collapse
I also found that speaker was louder and clear on LP plus even have a little bit of distortion at max volume now, and in mi case, performance in 3D games was smoother in LP 3.120 with ondemand CPU governor. It might fix again if i change governor in MM but still not rooted as im waiting for a method for locked bootloader.
Morfarj said:
I don't like the fact that mpdecision is not included in the new update. it gives me huge battery drain.
Click to expand...
Click to collapse
Snapdragon 615 does not need it nor it's compatible with mpdecision..
Sony won't be adding any hotplug as they don't make
Custom kernel or drivers.. It's just qualcomm,s fault..
Is somebody else bothered with the weird gap between the signal bars and the battery icon?
Also, does anyone know how can I remove agv Antivirus? I'll appreciate it.
Guys i noticed that the brightest is very low for out side
Sent from my E2333 using XDA-Developers mobile app
I like New update, everything seems to work ok, i have made adoptable sfor?ie tru adb (mixed 50) and i am pleased with result. I think rom needs a day or two to settled down... Yesterday i run AnTuTu and obtained 35k scor and today i got 36.7k... maybe tomorrow i'll get 40k... :laugh:
Everything is just great, but i miss the real stamina mode from Sony..
Sent from my E2303 using Tapatalk
http://www.xda-developers.com/andro...every-car-through-updated-app-on-smartphones/
Looks like it may run on LP ROMs. Didn't tried yet.
That looks really interesting. Might be the reason I've been waiting for to upgrade to 5.1
Sent from my SM-G920F using Tapatalk
pa.ko said:
http://www.xda-developers.com/andro...every-car-through-updated-app-on-smartphones/
Looks like it may run on LP ROMs. Didn't tried yet.
Click to expand...
Click to collapse
Not installing on my LP unit running @dsa8310 October ROM. Starts the installation and after a few seconds - App not installed. At first I thought it's location-based but installed OK on my Samsung phone (Marshmallow)
m00n61 said:
Not installing on my LP unit running @dsa8310 October ROM. Starts the installation and after a few seconds - App not installed. At first I thought it's location-based but installed OK on my Samsung phone (Marshmallow)
Click to expand...
Click to collapse
i think you installed the arm64 version. You need the arm version. Mine is working. Make sure you installed the google app and google play music app before installing. Normally android auto is installing this in its installation, but than it goes in a loop (in mine case). So install them first.
For the rest android auto is slow, because it's using google maps, which is slow in the android 5.1 version. Spotify is working fine btw.
I'm working for a MAnufacture which produces HU for cars. Right now there is a native Android System for cars in discussion.
Source:
http://www.computerworld.com/articl...auto-making-your-car-a-big-mobile-device.html
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
dcdttu said:
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
Click to expand...
Click to collapse
try DSA room, its best 5.1 rom I used
dcdttu said:
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
Click to expand...
Click to collapse
It's not exactly the ROM. It's the combination Google Maps + Google Now + Android Auto. I tried it on a clean ROM with only root and pretty much everything removed and it's unusable.
I also noticed that a 5.1 ROM will run OK as long as you only have either Google Maps or Google Now. When you have both it's barely working.
m00n61 said:
It's not exactly the ROM. It's the combination Google Maps + Google Now + Android Auto. I tried it on a clean ROM with only root and pretty much everything removed and it's unusable.
I also noticed that a 5.1 ROM will run OK as long as you only have either Google Maps or Google Now. When you have both it's barely working.
Click to expand...
Click to collapse
Don't know if it is only RAM related. These units have very poor CPU profile - throttling. stepup clock control settings which use highest clock only rarely so most of the time CPU is running slow so many processes suffer especially when multiple apps are running in background.
I'm not using 5.1 ROM (as I see still issues and people complaining) so I cannot test if and what apps mix causes issues.
You may try some kernel tools for testing different governors, CPU throttling (yes I would try also thermal throttling if you want to be on the safe side as rumours are Chinese used above mentioned downclocked setup in order to save CPU from overheating as there is no heat sink).
It would be interesting to open new thread for this. Much improvements may be achieved only by tuning kernel. And that needs some experimenting and practising.
Also, regarding 5.1 it is well known that it is 'heavy' and one of the main points of 6 (MM) was to reduce resource usage. So instead jumping to LP and having resource issues, I'll wait to see if there will be progress on MM which may resolve much of the problems around.
pa.ko said:
Don't know if it is only RAM related. These units have very poor CPU profile - throttling. stepup clock control settings which use highest clock only rarely so most of the time CPU is running slow so many processes suffer especially when multiple apps are running in background.
I'm not using 5.1 ROM (as I see still issues and people complaining) so I cannot test if and what apps mix causes issues.
You may try some kernel tools for testing different governors, CPU throttling (yes I would try also thermal throttling if you want to be on the safe side as rumours are Chinese used above mentioned downclocked setup in order to save CPU from overheating as there is no heat sink).
It would be interesting to open new thread for this. Much improvements may be achieved only by tuning kernel. And that needs some experimenting and practising.
Also, regarding 5.1 it is well known that it is 'heavy' and one of the main points of 6 (MM) was to reduce resource usage. So instead jumping to LP and having resource issues, I'll wait to see if there will be progress on MM which may resolve much of the problems around.
Click to expand...
Click to collapse
I agree. From monitoring resource usage under 5.1 I have to say that while RAM usage will rarely go over 700 MB CPU is aggressively downclocked. However, I need to first add a heatsink and then play with governors.
However, not sure how much would that really help with Android Auto, it's so damn slow it takes like 20 seconds just to start
m00n61 said:
I agree. From monitoring resource usage under 5.1 I have to say that while RAM usage will rarely go over 700 MB CPU is aggressively downclocked. However, I need to first add a heatsink and then play with governors.
However, not sure how much would that really help with Android Auto, it's so damn slow it takes like 20 seconds just to start
Click to expand...
Click to collapse
Heatsink issue is to be investigated also. For instance many phones do not have heatsinks and still endure very heavy usage. So it may be not necessary. For instance, thermal throttling may be sufficient.
Thus, both governor and thermal control should be investigated. I believe it is possible with little effort to tune these units to work very nicely without much hw poking.
SW in these units is just so bad and poor it is almost unbelievable! Beside designers didn't have basic knowledge on architecture, they even 'tuned' many things in just opposite of what is needed. They could have better situation if only leaves everything by default in AOSP
Open build.prop from system/
Edit then find line
ro.sys.fw.bg_apps_limit=30 (default in emui)
And change to
ro.sys.fw.bg_apps_limit=60 try "60" or more
Save and reboot.
It will make ram managament better.
It means more apps in memory (better using of 4gb ram).
WYPIERDAALAAC said:
Open build.prop from system/
Edit then find line
ro.sys.fw.bg_apps_limit=30
And change to
ro.sys.fw.bg_apps_limit=60
Save and reboot.
It will make ram managament better.
Click to expand...
Click to collapse
Any verified source for this, and maybe a detailed explanation of what the setting does?
All my searching has only turned out info from the Oneplus 3 folks who did this to force use of their 6GB RAM. Even setting this to =42 on the OP3 resulted in RAM use of around 5GB... which is 1GB more than what we have.
With that in mind, going to =60 might just give us OOM errors earlier. Or not.
To begin with, my Nougat Honor 8 (L19) doesn't even have the original ro.sys.fw.bg_apps_limit line in build.prop.
That said, gonna test the setting nonetheless, but not with such an extreme value as 60 right off the bat.
eiraku said:
Any verified source for this, and maybe a detailed explanation of what the setting does?
All my searching has only turned out info from the Oneplus 3 folks who did this to force use of their 6GB RAM. Even setting this to =42 on the OP3 resulted in RAM use of around 5GB... which is 1GB more than what we have.
With that in mind, going to =60 might just give us OOM errors earlier. Or not.
To begin with, my Nougat Honor 8 (L19) doesn't even have the original ro.sys.fw.bg_apps_limit line in build.prop.
That said, gonna test the setting nonetheless, but not with such an extreme value as 60 right off the bat.
Click to expand...
Click to collapse
Ok. I tried this with buggy Lollipop on LG G2M.
And it worked.
30 value is default in Honor 7 , so in Honor 8 we can increase it even more than 60 i think.
It will gives you more apps in memory. Ram managament of emui is very agressive and it kills apps in memory too often.
WYPIERDAALAAC said:
Ok. I tried this with buggy Lollipop on LG G2M.
And it worked.
30 value is default in Honor 7 , so in Honor 8 we can increase it even more than 60 i think.
It will gives you more apps in memory. Ram managament of emui is very agressive and it kills apps in memory too often.
Click to expand...
Click to collapse
I'm trying out 40-50 for now, as the OP3 folks do 60 and they have 6GB RAM lol.
What's actually important is that we find documentation on this setting and how it works. If that value is absolute or is taken in percentage form (e.g. is 60 = 60 or 60 = 60% of the total RAM).
If it's absolute, too high might be a problem. If it's a taken in percentage, it might not matter.
Plus, like I said before, I didn't even have the string to begin with in my original build.prop lol.
eiraku said:
I'm trying out 40-50 for now, as the OP3 folks do 60 and they have 6GB RAM lol.
What's actually important is that we find documentation on this setting and how it works. If that value is absolute or is taken in percentage form (e.g. is 60 = 60 or 60 = 60% of the total RAM).
If it's absolute, too high might be a problem. If it's a taken in percentage, it might not matter.
Plus, like I said before, I didn't even have the string to begin with in my original build.prop lol.
Click to expand...
Click to collapse
No matter if 6 or 4 gb ram. Is not about percent, its about apps in background, for example:if default 30 you can have only 30apps at once. Low devices have for example just 12 etc
Yeah, if no line like this in our build.prop it does not mean we cant test it. System anyway has some default value.
Just tweak the LMK values. It's a whole lot easier to test.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Just tweak the LMK values. It's a whole lot easier to test.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Any recommended settings for LMK?
eiraku said:
Any recommended settings for LMK?
Click to expand...
Click to collapse
I use this one.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
I use this one.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Thanks, testing those settings out through Kernel Auditor, which I need running to hack SELinux anyway, it's good that it has LMK setting too for me to test out.
I went to the battery settings page and turn off the Close All after screen lock option, then added a handful of apps that are listed as power intensive and ones I don't mind re-launching, works great.
Hello everyone!
I've been on smallEUI for a while, and I've decided that it's not worth it to keep anymore. SOT is inconsistent, there are small bugs here and there, and some major that begin to appear after a while.
I've been looking at Mokee and Ressurection Remix (sadly, author has stopped development of a buggy nougat version and moved to oreo)
I'm not looking for spectacular SOT that will blow me away. 4-5 hours is enough for me.
Stability is a huge must for me, i use my phone everyday and I need to be able to depend on it. EUI ROMs have aggressive RAM management (I have the 6gb RAM version and EUI treats it as if I only have 2gb, removing apps from RAM like my launcher). I need basic features like VoLTE and Bluetooth to work without fail.
I don't really care about safetynet, so I'm fine without that.
EDIT: I'm a fool, I said OmniROM instead of Slim. Sorry about that.
Thanks!
EDIT
Alright, I've actually installed Slim. Its superior to SmallEUI in almost every way.
Camera is almost as good as stock, no noticable difference.
Battery life is much more consistant (Expect 4 h 30m of SOT with mixed usage.)
No more crappy EUI RAM management (Its really bad, it treats 6GB of RAM like its 512MB of ram, killling any background processes, including your launcher, forcing frequent redraws)
Slim handles thermals MUCH BETTER than EUI. Way better!
Noticably faster UI, and smoother sustained performance under heavy load.
Nougat!
VoLTE works on T-Mobile US.
Fingerprint sensor works perfectly, and works faster in Slim than EUI, and more accuratly too!
Bug free so far.
And OTA updates!
This is hands down the most stable experience I've seen so far.
Better than Lineage, better than Mokee, and SmallEUI.
Go for this ROM, you won't regret it.
The_Rusty_Geek said:
Hello everyone!
I've been on smallEUI for a while, and I've decided that it's not worth it to keep anymore. SOT is inconsistent, there are small bugs here and there, and some major that begin to appear after a while.
I've been looking at Mokee and Ressurection Remix (sadly, author has stopped development of a buggy nougat version and moved to oreo)
I'm not looking for spectacular SOT that will blow me away. 4-5 hours is enough for me.
Stability is a huge must for me, i use my phone everyday and I need to be able to depend on it. EUI ROMs have aggressive RAM management (I have the 6gb RAM version and EUI treats it as if I only have 2gb, removing apps from RAM like my launcher). I need basic features like VoLTE and Bluetooth to work without fail.
I don't really care about safetynet, so I'm fine without that.
Thanks!
Click to expand...
Click to collapse
Hi I'm currently using MOKEE and it's actually pretty stable. I haven't found any bugs at all but I'm not sure if VoLTE works and if you download it there will be almost everyday update but you don't have to download them because they don't change anything for our device
LameMonster82 said:
Hi I'm currently using MOKEE and it's actually pretty stable. I haven't found any bugs at all but I'm not sure if VoLTE works and if you download it there will be almost everyday update but you don't have to download them because they don't change anything for our device
Click to expand...
Click to collapse
Thanks!
If I were to switch to Mokee, should I download the stable version?
The nightlies seem to be auto compiled and they look really unstable.
EDIT: Also, how is SOT?
The_Rusty_Geek said:
Thanks!
If I were to switch to Mokee, should I download the stable version?
The nightlies seem to be auto compiled and they look really unstable.
EDIT: Also, how is SOT?
Click to expand...
Click to collapse
It's recommend to download the stable and the nighties are almost the same so don't worry downloading them.
Also I'm not sure what do you mean by SOT.
LameMonster82 said:
It's recommend to download the stable and the nighties are almost the same so don't worry downloading them.
Also I'm not sure what do you mean by SOT.
Click to expand...
Click to collapse
You have never heard of the term?
I'm just kind of surprised. It means "screen on time".
The_Rusty_Geek said:
You have never heard of the term?
I'm just kind of surprised. It means "screen on time".
Click to expand...
Click to collapse
I just haven't come across it but I don't have any problem SOT but I'm not a lot on my phone so I can't say a lot.
I’m in a similar position as you are. Using LOS 14. It’s been really stable. Best ROM i’ve used so far for the Le max 2. Small eui was a buggy mess when I used it. RR was good at first, but more bugs made me switch. Happily using LOS as a daily driver now.
mkerr said:
I’m in a similar position as you are. Using LOS 14. It’s been really stable. Best ROM i’ve used so far for the Le max 2. Small eui was a buggy mess when I used it. RR was good at first, but more bugs made me switch. Happily using LOS as a daily driver now.
Click to expand...
Click to collapse
How is Lineage os in general?
Does gps work fine?
Fingerprint scanner can be fixed easily with a firmware update, so I don't mind that.
How is SOT?
Does camera quality match EUI?
Thanks!
Los if probably my favourite flavour android. RR has more options, though seems slower and more prone to issues (in my experience).
Camera is great. I've installed the Google hdr released camera app though, it's excellent.
Not too sure about sot sorry. Phone is usually around 20% when I finish the day. That's from 6am till say 10pm. I'd say average use for anyone that's on XDA.
This phone has never had good battery for me, except for small eui. But that was at the expense of an unusable rom with no SMS or push notifications working.
Finger print works perfectly.
Heyyo, for most stable? I'd say OmniROM 7 or LineageOS 14.1. They tend to not get the newest changes right away which is good for stability.
OmniROM is unique in the sense that it actually gets certified official builds signed by Google so they do come with SafetyNet Certification. It's the only custom ROM for the LeEco Le Max 2 that gets that.
Hopefully once GalacticSryder receives his Le Max 2 he can get his Mach LeEco kernel working for it and get official signed builds of Paranoid Android as that is the only other ROM that I know of that gets Google signed builds. Tbh I'm really stoked for this as I failed to port his Mach LeEco kernel haha.
Oh, if you plan on using MultiROM? OmniROM play store certification only works if you install it as the internal ROM and not secondary ROM as it mounts the system as writeable. You'd then need to do Magisk plus Universal SafetyNet fix module to spoof the Play Store.
The only downside to OmniROM is Andr68rus has moved onto Oreo development so it probably won't get Le Max 2 specific upgrades but thus far from my testing all Le Max 2 bugs have been squashed much like LineageOS 14.1.
If you want better screen on time with OmniROM or LOS? You can always root with Magisk and then install the AKT Profiles App and use something like Project X.A.N.A. balanced or battery.
If screen on time is your goal though? Slimroms I'd say currently has the best balance of screen on time and performance.
Anywho? Lots to choose from and there isn't really a wrong answer except for say the AOKP or other discontinued ROMs.
ThE_MarD said:
-snip-.
Click to expand...
Click to collapse
Thanks for the detailed reply!
Sorry for the late reply.
So, I'm deciding between Lineage and Omnirom right now. Are there are basic features that differ between the two ROMs? Like included customization options or small tweaks that give the ROM it's unique personality?
It's amazing to see that a relatively not that known device has such a large and dedicated community to support it even when the company is going down under.
Thanks!
The_Rusty_Geek said:
Thanks for the detailed reply!
Sorry for the late reply.
So, I'm deciding between Lineage and Omnirom right now. Are there are basic features that differ between the two ROMs? Like included customization options or small tweaks that give the ROM it's unique personality?
It's amazing to see that a relatively not that known device has such a large and dedicated community to support it even when the company is going down under.
Thanks!
Click to expand...
Click to collapse
LineageOS has weekly build updates so it does still receive the Google Monthly Security updates which is nice. It also has a lot more customization options than OmniROM
OmniROM as I mentioned is the only custom ROM for the Le Max 2 with official SafetyNet certification as a main feature. I've also noticed because of it that it's the only ROM I know of where fingerprint unlocking works with stuff like my RBC banking app.
OmniROM tends to not get as many flashy features as LineageOS but it has a few unique ones built into it such as OmniSwitch which is an alternative to the recent apps screen where it slides a small panel from the side of the screen and has the same functionality as recent apps but without the need of exiting your current app.
There's also their open source clock app as another example.
For Le Max 2 specifics? OmniROM has Dolby Atmos built into it for better sound quality and also the LeEco infrared app for using the IR blaster built into this phone so both work out of the box without the need of flashing Magisk Modules or anything like that.
ThE_MarD said:
-snip-.
Click to expand...
Click to collapse
Thank you!
I will be installing Lineage OS and try it out!
Actually pulled a switcharoo at the last moment. I decided to go with Slim instead of Lineage because Lineage doesn't have VoLTE, and users report various problems with Lineage.
If anyone here is deciding on what to install, go for Slim.
Safetynet+Magisk passes safteynet, and everything is very fast.
UI and interface is really smooth, phone tempratures are much better than stock EUI, and SmallEUI
If gaming performance is your thing, expect a 20-30% increase in FPS than EUI based ROMS.
Battery life is a bit worse than EUI, but its consistent. In SmallEUI SOT would vary from almost 6 hours to as little as 1 hour and 30 minutes. Slim has a consistant 4 hour 30 min with mixed usage (Reddit, Gaming, and YouTube).
And best of all, no more annoying EUI RAM management! I have 6GB of RAM in my phone! Stop treating it like its 512MB and killing all background apps! It even killed Nova Launcher occasionally!
Slim is amazing. Simply amazing. I'm glad I made the switch now, and not later. I love it.
EDIT: I'm a fool, I said Omni instead of Slim. Sorry about that everyone.
Yep, tried them all and Omni's the best. Was worried that I'd miss functionality from EUI but everything actually works better. There's no reason at all to stick with stock roms. Do you know does Vulkan work with Omni?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~~A custom kernel for (most) V20 variants~~
Swan2000 is an android kernel based on the very latest Qualcomm 4.4 CAF sources for MSM8998 (which is also compatible with MSM8996), aiming to bring new features and updates over official kernels, and also improve LGE MSM8996 devices with some extra tuning, fixing and additional features tailored specifically for their performance characteristics and feature sets, while trying to maximize the battery life and responsiveness of those devices at the same time.
Its name comes from a merge between Swankernel(@AShiningRay) and mk2000(@askermk2000), as they were the main heads behind this kernel's development.
__Disclaimers__First and foremost: DO NOT bother official LineageOS threads with bugs if you're using this kernel, only bug reports with logs pointing to the official kernel will receive support there!!!
Now for the usual XDA disclaimer:
We are not responsible for bricked devices, dead SD cards, tactical nukes being set up (with the V20 you never know), alien invasions, google spying on you, or you getting fired because the alarm app failed after you removed all traces of google services from your phone so that google couldn't spy on you.
YOU are choosing to make these modifications, and if you point the finger at us for somehow messing up your device despite YOU being the one explicitly making these modifications, we will laugh at you.
DO NOT expect support on official ROM threads if you are running this kernel. Also don't try to hide it because we will know, and we will also laugh at you.
Your warranty is most likely void at this point anyway, but nevertheless, it is now definitely void if you tamper with any part of your device / software.
Click to expand...
Click to collapse
__Which V20 variants/models does this kernel support?__
The kernel currently supports the following V20 variants:
H910 / H915
H918
H990(DS / TR)
LS997
US996
US996D(Dirtysanta)
VS995
Those seem to cover every rootable variant thus far, but additional variants can be added in case a breakthrough happens on F800 for example.
__What does this kernel intend to achieve?__
The main goal here is to have a kernel that not only has extra features and improvements, but is also clean and concise, having only features that are truly needed from a kernel that will run alongside a Android 12.1-based ROMs and beyond.
This kernel does have a battery life bias, but will still scale up to maximum performance when needed. Gaming variants basically mean that the kernel comes overclocked by default, no additional tweaking is needed.
__Does it have any features over official?__
Yes, quite a few. The kernel is divided into two variants and their respective gaming modes, here are the features all variants have over Lineage's 4.4 kernel:
GPU and CPU/Cache Undervolt for better power efficiency on load.
Almost no unnecessary debug flags on the kernel for better kernel performance.
USB Fast Charge.
KCAL Control (although not really needed for LOS, other custom roms might surface with the need for this)
Multiple cherry-picks from different msm8996 sources with fixes and improvements to the kernel.
Built with newer GCC toolchains (GCC 12) with optimized inlining and other compiler optimizations for 8996
Updated LZ4 libraries for faster ZRAM
Cryptographic function optimizations, slightly improving the phone's performance when calculating hashes and so on.
The Extreme variant really only has one extra feature over the Safe variant, that being:
Stronger Undervolts (i'm talking about borderline unstable undervolts here, so i really recommend that you flash the Safe variant first).
The "Gaming" versions are basically overclocked variants of Safe and Extreme, which means they also only differ in undervolt levels.
__Are there any bugs?__
As of now, the only actual kernel bug the V20 and G5 have comes down to their insanely over-engineered USB ports. You can't use them as a MacBook by plugging a fully powered hub into them like you could in 3.18 yet.
__Download & Installation__
The folders containing each kernel variant can be found here (use Ctrl+F to search for your phone model and kernel variant, there's just too many versions to neatly organize in folders and such as it would take too much time):
GITHUB KERNEL RELEASES
To install the kernel, it's the standard procedure:
Download the kernel you want for your device
Place it into the phone's storage
Boot into recovery, select it and then flash
Wipe Dalvik Cache (optional, you only need to wipe it if you face random Force Closes, but it is a good practice anyway)
Reboot.
Use AIDA64, go into the "Android" tab and look for "Kernel Version", where it should show "4.4.302-Swan2K-...".
Enjoy the experience!
As usual, we do not take responsibility if you fail to make backups before flashing this kernel, you have been warned!
__Changelog__
Spoiler: Changes done in recent versions:
*********** Swan2000 V0.1-BETA8+ ***********Small release with BCL tweaks for all devices, some msm8998 merges and minor hotspot fixes for G6.
_________________________________________
*********** Swan2000 V0.1-BETA8 [First Release] ***********This one is pretty straightforward: Basically lineage's kernel with all the features and improvements listed above, plus a few additional tweaks that would take too much space to note.
__Closing notes__
If you have any suggestion or idea that can possibly improve the kernel, do not hesitate to share, i will try to implement it when time allows it. If there are any problems that only happen on this version of the kernel, submit a log and i'll try to look at it.
I'll say it again: Please DO NOT bother official Lineage with bugs if you're running this kernel, only lineage's official kernel is supported over there.
___________________________________
The kernel's source code can be found here. It is also shared between G5 and G6!
And last but not least, special thanks to those that helped this major revamp on LGE_8996 become a reality by developing, testing, and even helping things indirectly, the dev community on all three phones had to come together for this:
@xxseva44
@npjohnson
@askermk2000
@thewolfsvk
@ROMSG
@bernardobas
@VortexHD
@Michele_Catella
And many, many others
Reserved.
Might need an additional post at the top later.
First of all thanks! To everyone involved, you guys rock!
A little tangent (bear with me for a while, please)
I had an OP3 before this V20, and like some "developers toy's" received a good attention for some time that phased out and was replaced by many more quickly than his predecessors in my opinion.
Besides SultanXDA Lineage 14 that he customized the kernel+ROM (achieving 6h screen time with ease), the thing that had me impressed was EAS and was beautifully implemented by mcdachpappe in this kernel. That really was responsive and also have some endurance. Other device that I still have it's my LG G4 and the devs ported so many kernels (I used blu_active most of all), but I didn't have the time needed to tweak.
After that detour, I would like to know: (no pressure, complains, just curiosity from my part)
1) EAS it's still relevant? Did you have any plans to implement it? Since the OP3 "has the same msm8996" could it be ported or benefit from this governor?
2) I noticed that you have on this kernel the "basic" governors : interactive, conservative, ondemand, userspace, powersave, performance. Do you consider other addition? Or it's an unnecessary problem?
3) I would love to not need any app than necessary, but to reduce some "image retention" there are many posts to help mitigate this issue, but the configuration it's for some app and trying to replicate in the system settings won't have near the results. Do you have any suggestion?
4) Any recommendations for applications to adjust the kernel? I used many moons ago the Kernel Audtor but the most close replacement that I'm aware it's the SmartPack-Kernel Manager?
5) A feature that always intrigue me in some Sony devices was the ability from stock to limit/manage the battery, "setting a max capacity" to stop charging at determined percentage, theoretically "extending" the life-span. How demanding, and it would benefit our devices this feature?
6) You mention the USB issue. Right now I don't have any hub and would be a nice thing in the future to plug an ethernet cable, be able to use a mouse + keyboard in some situation, and technically the V20 has HDMI out. But in this new kernel the problem comes only to being able to charge with any hub or I didn't get properly what the exact problem was?
7) The "only bug" on my H990DS that I encountered so far it's when I installed the SmartPack-Kernel Manager and in the "Overall Statistics" the CPU temperature are "-4.0°C" (I didn't install this app before with the stock kernel because I didn't needed this app). So how to properly report it?
I can't believe how much more responsive the device is, looks like magic!
dextructor said:
First of all thanks! To everyone involved, you guys rock!
A little tangent (bare with me for a while, please)
...
Click to expand...
Click to collapse
1 - No, not really. While EAS was included in this kernel's earlier versions, we opted to drop it from both official and Swan2000 when shipping lineage. EAS just doesn't bring that many benefits, if any, to msm8996 and 8998 devices when the device sources are already well tuned. And that's what we saw by going back to HMP: No significant perf/power difference on V20, G5 or G6, although the results favored HMP a bit since EAS boosted too much.
2 - No other CPU governor additions are planned, interactive can be configured to do pretty much everything you need (our device trees on lineage already have it pretty balanced), and if you can use conservative if a inherent battery life bias is needed.
3 - Lineage 19.1 has LiveDisplay support by default(Settings->Display->Color->LiveDisplay), not needing any kernel additions on that front. Those guides use KCAL control, which is there on the kernel in case other custom roms show up without LiveDisplay. Personally i use a LiveDisplay Color Calibration profile of 94%R, 90%G, 92%B to nearly eliminate image retention on mine, though that's because my display has a green tint ever since i bought it, might not be the same for you. Intensity and contrast values don't seem to affect retention that much so it's up to you.
4 - SmartPack is pretty much the continuation of Kernel Adiutor in case you really need a kernel manager.
5 - It is possible to do that, but requires ROM integration and can also be buggy sometimes (my Xiaomi Mido has that feature on its custom rom and sometimes it simply doesn't charge if i enable the battery limit and it hits the threshold, only charging again after a cold reboot). Since the V20 has a user-replaceable battery, that's not a big deal.
6 - The bug is not on the usb features themselves. HDMI support is perfect, as is OTG, mouse and keyboard as well (and i also think ethernet). The problem arises when fully powered hubs come into play: The phone simply refuses to charge at the same time it's in Host/OTG mode because we didn't fully figure out USB-PD on the new kernel just yet, and as a result powered hubs don't work, though you can still use simpler hubs that don't need additional power, or charge the phone. Since the V20 and G5 are pretty much the only 8996 devices on 4.4 that have this fully-featured usb port, it's hard to conceptualize a fix that doesn't break something else.
7 - SmartPack reporting incorrect cpu temps has always happened in 4.4. Apparently it's a bug in the app because AIDA64 doesn't suffer from the same issue, nor does CPUFloat (although CPUFloat does seem to invert GPU and CPU temps in some roms). I guess that's because there aren't that many Snapdragon 82x devices running 4.4 so most apps focus on 3.18's sensor configuration.
AShiningRay said:
1 - ...No significant perf/power difference on V20, G5 or G6, although the results favored HMP a bit since EAS boosted too much.
2 - No other CPU governor additions are planned
Click to expand...
Click to collapse
Beautifully explained, much more than I needed, and very well tuned.
AShiningRay said:
3 - Lineage 19.1 has LiveDisplay support by default(Settings->Display->Color->LiveDisplay), not needing any kernel additions on that front
Click to expand...
Click to collapse
I was aware, but thanks for the reminder, and your settings. When I was using the OP3 in the beginning I disliked very much the punchy color calibration that was used until they released "sRGB" profile that I used ever since (I guess that I couldn't have a Samsung device with their saturated profiles). And I tried to replicate some of the configs but the values don't match if you don't try to calculate. For example I liked this config that I copied from this video description and give me an very soft and neutral color spectrum (too bland for some, and with more time I would search for how to improve it):
Red 256 | Green 241 | Blue 226
Minimum RGB Value 0 | Saturation Intensity 12 | Screen Hue 0
Screen Value 128 | Screen Contrast 128
The color values are really straightforward, but "Minimum RGB"? The "Saturation Intensity" it's separated in 2 distinct values like "Saturation" and "Intensity"? Do you understand the difference?
AShiningRay said:
4 - SmartPack is pretty much the continuation of Kernel Adiutor in case you really need a kernel manager.
5 - requires ROM integration and can also be buggy sometimes
Click to expand...
Click to collapse
Clear enough, it was just as a suggestion.
AShiningRay said:
6 - The phone simply refuses to charge at the same time it's in Host/OTG mode because we didn't fully figure out USB-PD on the new kernel just yet
Click to expand...
Click to collapse
No problem, I was just mention because my ex-wife had a Pixel XL and I bought to her this USB Hub (UCN 3273) and everything worked (except HDMI because Google intentionally disable HDMI out just to sell more Chromecasts) including PD charging. It was used with ethernet (because a real gigabit connection beats many wifi speeds and consistency, and spots with bad coverage) and even an external USB mic to make video-calls (that without powering the HUB won't work). OK if this features could come to the device, until then no need to rush.
AShiningRay said:
7 - has always happened in 4.4
Click to expand...
Click to collapse
Ok, I didn't know. It's better to know than make trouble unnecessarily.
I remember reading about low volume on audio recording and decided to test on both OP3 and H990DS with Audio Recorder (M4a +48kHz +256kbps + stereo settings). Both devices recording the same initial 20s dialogue from this video at the same distance from the speaker of my computer but very different results.
I even analyzed in Audacity on the computer and it was indeed not only much lower, but was mono instead of stereo.
How can I help you guys properly identify this problem?
Thanks again!
dextructor said:
The color values are really straightforward, but "Minimum RGB"? The "Saturation Intensity" it's separated in 2 distinct values like "Saturation" and "Intensity"? Do you understand the difference?
Click to expand...
Click to collapse
Minimum RGB is pretty useless, it was supposed to deal with the black levels (in essence, how dark should the darkest pixels be on the screen) but never seen it do anything useful on any of my phones, OLED or not.
As for Saturation and Intensity being separated... "Saturation Intensity" is just "Saturation" on LiveDisplay, while "Intensity" on LiveDisplay is the same as "Screen Value", which dictates the overall brightness of the screen's pixels (just don't go too far on this one, or else you'll get overblown whites, also balance it with contrast and you get a nifty max brightness boost for free).
dextructor said:
No problem, I was just mention because my ex-wife had a Pixel XL and I bought to her this USB Hub (UCN 3273) and everything worked (except HDMI because Google intentionally disable HDMI out just to sell more Chromecasts) including PD charging. It was used with ethernet (because a real gigabit connection beats many wifi speeds and consistency, and spots with bad coverage) and even an external USB mic to make video-calls (that without powering the HUB won't work). OK if this features could come to the device, until then no need to rush.
Click to expand...
Click to collapse
It might come at some point since we really want to fix every major hardware feature of all three phones, though it's one of the peskiest issues to deal with on the kernel side since we have 5 or 6 usb drivers that communicate with each other.
dextructor said:
I remember reading about low volume on audio recording and decided to test on both OP3 and H990DS with Audio Recorder (M4a +48kHz +256kbps + stereo settings). Both devices recording the same initial 20s dialogue from this video at the same distance from the speaker of my computer but very different results.
I even analyzed in Audacity on the computer and it was indeed not only much lower, but was mono instead of stereo.
How can I help you guys properly identify this problem?
Thanks again!
Click to expand...
Click to collapse
AFAIK that's a known problem on AOSP roms as a whole (happens in 3.18, happens in 4.4, not kernel-side), mics on V20 and others just don't work as intended compared to stock. It's on the list of things we're gonna look at, but it's not a priority right now because we're trying to sort out Bluetooth in order to bring Lineage 20 in.
Once we start debugging the mics, i'll see if i can get one of our rom-side devs to approach you with more info if you're still available by then. Thanks!
AShiningRay said:
Once we start debugging the mics, i'll see if i can get one of our rom-side devs to approach you with more info if you're still available by then. Thanks!
Click to expand...
Click to collapse
No problems, you guys are really good at improving/fixing this devices. And I'll be here if I can help in anyway.
Very good explanations, really good knowledge on this thread. Thanks!
dextructor said:
No problems, you guys are really good at improving/fixing this devices. And I'll be here if I can help in anyway.
Very good explanations, really good knowledge on this thread. Thanks!
Click to expand...
Click to collapse
Yea in regards to the mic level, this has been a known issue on the v20. However i was not aware of it recording in mono, that is very odd. The level issue is mixer path related, but the mono recording, i'm not too sure. I will admit, it may be a while until this issue is fixed as we're heading into los 20 and getting that ready. But this will definetly get looked at. Could you grab logs of when you record? I wand to see what the audio hal is doing and how it sets up for recording.
xxseva44 said:
Could you grab logs of when you record? I wand to see what the audio hal is doing and how it sets up for recording.
Click to expand...
Click to collapse
Since I couldn't download the latest build because the page error 502, I clean flash 2023-04-23 build and only install the Magisk so I could get an dmesg and the Recorder app mentioned before.
Have 2 sets of archives, the stock kernel and the Swan2000 with logcat and dmesg.
If I can provide more help, please just ask.
What's the significance of H830, H850, H870?
andruyd said:
What's the significance of H830, H850, H870?
Click to expand...
Click to collapse
Those are G5 and G6 models. This kernel supports all three LGE_8996 phones, we just separated the threads for each of them.
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
@xxseva44
Was the logs that I send any useful to help diagnose the audio recording issues?
Thank you all!
dextructor said:
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
Click to expand...
Click to collapse
BCL is enabled by default on all 4.4 builds since it's nowhere near as aggressive as 3.18, but you can disable it from userspace but it requires root... though i don't really recommend doing that.
dextructor said:
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
@xxseva44
Was the logs that I send any useful to help diagnose the audio recording issues?
Thank you all!
Click to expand...
Click to collapse
Ah yea, so far i haven't found anything odd. If possible, can you reboot, record something and then send the logs right after? It'll help with locating the issue if that's all that audio did the entire time the device was on.
AShiningRay said:
BCL is enabled by default on all 4.4 builds
Click to expand...
Click to collapse
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
xxseva44 said:
If possible, can you reboot, record something and then send the logs right after? It'll help with locating the issue if that's all that audio did the entire time the device was on.
Click to expand...
Click to collapse
I'm sorry, but I didn't fully understand what you requested me. So let's recapitulate:
1) Reboot
2) Record
3) Log (Only logcat or with dmesg as well)?
Little off-topic: I noticed a strange behavior last night, when for the first time I tried to record an video with GCam (if you/anyone have another version, build to suggest, I'll be grateful) and no audio at all. So I opened the stock Camera and the audio was loud and clear. And with the stock audio recorder was also very low volume as with the other app.
Are those things even remotely related?
Thanks!
dextructor said:
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
Click to expand...
Click to collapse
Yes
dextructor said:
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
I'm sorry, but I didn't fully understand what you requested me. So let's recapitulate:
1) Reboot
2) Record
3) Log (Only logcat or with dmesg as well)?
Little off-topic: I noticed a strange behavior last night, when for the first time I tried to record an video with GCam (if you/anyone have another version, build to suggest, I'll be grateful) and no audio at all. So I opened the stock Camera and the audio was loud and clear. And with the stock audio recorder was also very low volume as with the other app.
Are those things even remotely related?
Thanks!
Click to expand...
Click to collapse
All logs, grab them via adb right after running the recording. As for the wonky audio levels in different apps, yes they are related. Something does not seem to be right in terms of the mixer levels so I'll need you to log all the apps that behave weird so i know what routes to look at.
So far so good. I've only had one random reboot and that was on the Safe kernel. I'm now on the Extreme kernel and no issues so far. My H990 definitely doesn't get as warm compared to the stock kernel and it still looks and feels snappy.
xxseva44 said:
I'll need you to log all the apps that behave weird so i know what routes to look at.
Click to expand...
Click to collapse
Ok I'll do probably today or tomorrow and post it later.
Since I don't play any games anymore on my phone since Clash Royale many, many years ago, the most intensive thing that I do it's occasionally video-calling via Telegram FOSS. But let me tell about my history with this V20 H990DS
I bought this device used, and the seller said that the battery needed to be replaced, and randomly it gave me green-screen reboot messages when below 30% and the thermals wasn't great because it was the end of summer here in Brazil. Since everywhere that I searched about buying new LG batteries anyone tells that it's hard to find a real original and reliable I decided to try this one from Aliexpress, and also ordered some copper shims (0.5mm and 0.6mm) to put thermal paste and improve things. And a 128GB SDcard since it was cheap now (compared to years ago... I tested with H2testw and it works perfectly)
So the battery arrived first, and even before it arrived I installed the Lineage 19 and with the new 4.X Kernel it almost never gave me more green-screen reboots, but few random reboots when below 35%.
With Lineage 18 + SwanKernel Extreme gave the most stable scenario but only one time I did try to video-call with Telegram and it went stable, but slow (probably due underclock, maybe?)
But last Friday using the new battery I tried to video-call through Telegram some relatives that live abroad, and with only 5 minutes of calling it rebooted and was warm-ish? So the copper shims arrived early that week and I decided to do the thermal mod this week.
With the 0.6mm it pressed the LCD giving a darker spot, so I decided to replace with the 0.5mm, put new thermal paste and try again... So no dark spot on the screen.
I installed Telegram on other computer and tried to call and test the V20, but it still reboots after some time, but the strange thing it never reaches 62 or higher.
I tried the CPU Throttling Test to test the thermals and it barely reaches 60 with the Extreme+Gaming or with only Extreme as well.
So after all of this, I remember that H990DS have the reputation for drawing a lot of power:
1) Even a "compatible non OEM" battery can't provide what this device demands in terms of power consumption?
2) Having a dual-sim gives me freedom in terms of separate personal-work calls etc and not having to carry 2 phones. Could a dual sim card adapter could be a better approach?
3) There's a chance that this H990DS motherboard it's problematic/defective somehow and replacing with another H990DS would fix things (or even a H990 non-DS with that dual-sim adapter)?
4) The random reboots could give some useful information somehow for you devs? And how the best way to collect it?
5) Are video-calling that demanding, even if it don't reach the same temperatures that the pure CPU stress?
6) Any tips, suggestions?
Thanks!
PS: @xxseva44 sorry I couldn't give you the logs, but the instability/problems here are taking much more time that I initially planned.