{
"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"
}
Are you a ParanoidAndroid user on P500?
Welcome to the Discussion thread, here you shall ask all the general questions/ queries/ problems related to this specific ROM.
The development thread isn't meant for asking questions on HOW-TO, its meant to report serious bugs and should be used if you are ready to help in the development.
This thread is only for Bytecode's build from source ROMs based on Android 4.1.2 JellyBean.
Downloads can be found here.
Have any questions? Shoot! I will and others also who are aware of your answers shall try and help you
Until then I will upload some F.A.Q. to the post #2
:Reserved:
I was wondering about the picture quality taken with the camera.
sovikhaque said:
I was wondering about the picture quality taken with the camera.
Click to expand...
Click to collapse
Its the exact same as ICS
Have tried to flash ICS and JB ROMs (lupohirp, hephappy, Arjen, Adfad666. laz3r96, Rashed , incl. Bytecode's PA v2.2. and 2.52) on LG P500, however the device with all those ROMs failed to be detected as USB modem by Linux machine. It's not happened with openOptimus GB ROM (franco kernel), where p 500 is detected as USB modem out of the box. I think its related with how the kernel is configured (ppp and setserial). Unfortunately, I'm incapable to compile android kernel myself, but linux. I tried flash both DJNoXD and thachtunganh's kernel, but failed, while franco kernel just for GB!
Have anyone experienced such issue and how to fix it? Which kernel you used it? Really, I'm very much expecting to use ICS/JB p500 as usb modem (not usb tethering!). Well no need to buy a new USB GSM Modem
Any help is highly appreciated
xu3sno said:
Have tried to flash ICS and JB ROMs (lupohirp, hephappy, Arjen, Adfad666. laz3r96, Rashed , incl. Bytecode's PA v2.2. and 2.52) on LG P500, however the device with all those ROMs failed to be detected as USB modem by Linux machine. It's not happened with openOptimus GB ROM (franco kernel), where p 500 is detected as USB modem out of the box. I think its related with how the kernel is configured (ppp and setserial). Unfortunately, I'm incapable to compile android kernel myself, but linux. I tried flash both DJNoXD and thachtunganh's kernel, but failed, while franco kernel just for GB!
Have anyone experienced such issue and how to fix it? Which kernel you used it? Really, I'm very much expecting to use ICS/JB p500 as usb modem (not usb tethering!). Well no need to buy a new USB GSM Modem
Any help is highly appreciated
Click to expand...
Click to collapse
Even if it doesn't show "USB Modem" in ICS/ JB ROMs, still then have you tried to use it as a modem?
Wow thank you for this thread! Anyway,about the USB,I think it's because of netd's UsbController (we were using a custom one on gb but it was removed in ics),I'll try building with that.
Hi!
Do you plan to fixe wi-fi and bluetooth tethering?
Thanks.
Anyone got tips to increase battery life? My god I love this rom but it eats my battery to death just from sitting on my desk.
Herox said:
Anyone got tips to increase battery life? My god I love this rom but it eats my battery to death just from sitting on my desk.
Click to expand...
Click to collapse
Same here. I remember having Rashed's build with Performance CPU governor but now I had to change to SmartAssV2 since, for some reason I can't identify yet (even looking at BetterBatteryStats) the phone stays awake much longer than before, which means more time at higher CPU speed. With Wifi the battery will drain in just a few hours... In those weekends at home I can't leave it with wifi on. Do any of you guys have a good battery experience?
Herox said:
Anyone got tips to increase battery life? My god I love this rom but it eats my battery to death just from sitting on my desk.
Click to expand...
Click to collapse
filipeataide said:
Same here. I remember having Rashed's build with Performance CPU governor but now I had to change to SmartAssV2 since, for some reason I can't identify yet (even looking at BetterBatteryStats) the phone stays awake much longer than before, which means more time at higher CPU speed. With Wifi the battery will drain in just a few hours... In those weekends at home I can't leave it with wifi on. Do any of you guys have a good battery experience?
Click to expand...
Click to collapse
The battery life is pretty good with this ROM but YES! some minor tweak here and there are still required and Bytecode is already aware of that :highfive:
Secondly, never compare battery life with higher CPU frequencies. Bugs are excepted only at maximum freq. set to 600MHz. Higher frequencies suck battery life sometimes and you should choose an apt governor, performance is not good for battery.
Thirdly, make sure you have uninstalled all the apps you have installed before reporting anything. Background apps like facebook, maps, IMs etc acquire a lot of RAM which equates on using more battery life.
Lastly, try to keep "sync" switched off when you don't need it, provides you with some extra battery life.
Remember this, you are running Jelly Bean on a low end device, bugs and problems are expected, all you have to do is to cope and choose the right ROM according to your requirements :angel:
DJoptimus-One said:
Even if it doesn't show "USB Modem" in ICS/ JB ROMs, still then have you tried to use it as a modem?
Click to expand...
Click to collapse
Yep. I tried out to use it as USB modem on all ROMs (ICS and JB) and the results were same. When I run wvdialconf command on linux machine, the message is as follow:
wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S0 S1 S2 S3
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://alumnit.ca/wiki/?WvDial
while on GB:
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S0 S1 S2 S3
WvModem<*1>: Cannot get information for serial port.
ttyACM0<*1>: ATQ0 V1 E1 -- OK
ttyACM0<*1>: ATQ0 V1 E1 Z -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyACM0<*1>: Modem Identifier: ATI -- Manufacturer: LG Electronic Inc
ttyACM0<*1>: Speed 4800: AT -- OK
ttyACM0<*1>: Speed 9600: AT -- OK
ttyACM0<*1>: Speed 19200: AT -- OK
ttyACM0<*1>: Speed 38400: AT -- OK
ttyACM0<*1>: Speed 57600: AT -- OK
ttyACM0<*1>: Speed 115200: AT -- OK
ttyACM0<*1>: Speed 230400: AT -- OK
ttyACM0<*1>: Speed 460800: AT -- OK
ttyACM0<*1>: Max speed is 460800; that should be safe.
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found an USB modem on /dev/ttyACM0.
Modem configuration written to /etc/wvdial.conf.
ttyACM0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
---------- Post added at 01:12 PM ---------- Previous post was at 01:04 PM ----------
Bytecode said:
Wow thank you for this thread! Anyway,about the USB,I think it's because of netd's UsbController (we were using a custom one on gb but it was removed in ics),I'll try building with that.
Click to expand...
Click to collapse
Understood, since you built optimusOne yourself. Hope you can build with JB too. :good: Wish you luck! Can't wait to have that custom kernel!.
DJoptimus-One said:
The battery life is pretty good with this ROM but YES! some minor tweak here and there are still required and Bytecode is already aware of that :highfive:
Secondly, never compare battery life with higher CPU frequencies. Bugs are excepted only at maximum freq. set to 600MHz. Higher frequencies suck battery life sometimes and you should choose an apt governor, performance is not good for battery.
Thirdly, make sure you have uninstalled all the apps you have installed before reporting anything. Background apps like facebook, maps, IMs etc acquire a lot of RAM which equates on using more battery life.
Lastly, try to keep "sync" switched off when you don't need it, provides you with some extra battery life.
Remember this, you are running Jelly Bean on a low end device, bugs and problems are expected, all you have to do is to cope and choose the right ROM according to your requirements :angel:
Click to expand...
Click to collapse
I changed now for max 600 and expect to have a slight gain in battery life. On the background apps do you use any alternatives? As for now I can only increase the time interval for sync on FB. I dont use IMs although I have google+. I have no replacement for facebook or maps.
DJoptimus-One said:
The battery life is pretty good with this ROM but YES! some minor tweak here and there are still required and Bytecode is already aware of that :highfive:
Secondly, never compare battery life with higher CPU frequencies. Bugs are excepted only at maximum freq. set to 600MHz. Higher frequencies suck battery life sometimes and you should choose an apt governor, performance is not good for battery.
Thirdly, make sure you have uninstalled all the apps you have installed before reporting anything. Background apps like facebook, maps, IMs etc acquire a lot of RAM which equates on using more battery life.
Lastly, try to keep "sync" switched off when you don't need it, provides you with some extra battery life.
Remember this, you are running Jelly Bean on a low end device, bugs and problems are expected, all you have to do is to cope and choose the right ROM according to your requirements :angel:
Click to expand...
Click to collapse
Yes but this may be a bug here. My wifi does not turn off when the phone is idle/asleep. Wifi stays on and that burns battery too. Last rom I had before this was cm7.2 nightly I think and yea, it turned my wifi off after so long. Is there a way to make it time out after like a minute of idle?
Herox said:
Yes but this may be a bug here. My wifi does not turn off when the phone is idle/asleep. Wifi stays on and that burns battery too. Last rom I had before this was cm7.2 nightly I think and yea, it turned my wifi off after so long. Is there a way to make it time out after like a minute of idle?
Click to expand...
Click to collapse
You have benefits of apps, search the play store for wifi related apps, I am quiet sure that you will get what you need :highfive:
Herox said:
Yes but this may be a bug here. My wifi does not turn off when the phone is idle/asleep. Wifi stays on and that burns battery too. Last rom I had before this was cm7.2 nightly I think and yea, it turned my wifi off after so long. Is there a way to make it time out after like a minute of idle?
Click to expand...
Click to collapse
Superpower will let one set up stuff like this. There may be other small apps just for wifi and gs data shutdown as well.
Thanks for the tips guys. I also set the cpu so it can down clock as far as it can. That way when its idle it uses less power too. No need to sit at 300mhz when its not being used. And I switched the governor to conservative. Not sure which governor is best for balanced power usage.
Herox said:
Thanks for the tips guys. I also set the cpu so it can down clock as far as it can. That way when its idle it uses less power too. No need to sit at 300mhz when its not being used. And I switched the governor to conservative. Not sure which governor is best for balanced power usage.
Click to expand...
Click to collapse
You are using the right governor, stick to it.
Things have been soooo quiet in paranoid-land lately, hiding out I guess
2.54? Mic-fix?
I noticed that build.prop is set for ... triple buffering. Is this nonsense or is this actually implemented? Vsync is disabled and likely kernel mods are needed to use that.
The 4.2 buzz:
There is no room for that keyboard on system but I have swype anyway. I actually installed the 4.2 KB as a user-app but it fc'd. Did not have the libs so that might have been the problem (the first apks, zips that listed were missing some pieces). Could try it again, properly, but nothing really compelling here. Google is playing catch-up with this one.
I have the gallery installed along with its three libs/jni's. Camera crashes the gallery and hides the dialog with an artifact--tapping there will dismiss normally. The new photo edit functions will sometimes work, more usually simply blink and disappear. The legacy-camera still works independently so no harm in keeping this around (but I suspect it might be causing lagginess elsewhere!). For the photosphere capability, a modded camera version will need to use the compass/magnetometer instead of the gyroscope--I do not think we have one.
Put on the new Play and gmscore (which was with the gallery/camera zip!). Works like the older one, see no changes. I do not use gmail app but this new one has impressive improvements--worth a try if one makes use of it.
Clock looks interesting, might play with that tomorrow, but users of more advanced handsets have had fc's with it.
In all, there are 175 meg work of gapps. Do not dare attempt to flash this. Like no room for any of it. Extract items one wants to try and install as user apps. Specific libs and be pushed to /system/lib. However, all those jni's are likely not opensource and may be compiled for ARMv7 rendering them useless for our phones. No harm trying them out.
More 4.2 Buzz:
Put on the clock. Not very pretty but nice new functionality. I replaced with the blue version on the 4.2 goodies thread, a bit nicer. This widget could use some visual design improvement. Layout of world-clock functions (and others as well) is too large but we have the means to fix that, huh!
New Maps and StreetView. Maps has little more pizzazz. Problem I encountered was continued GPS activity after closing it, attempting to toggle on the status bar caused a reboot. I had not rebooted after updating the apps so might be my fault. See if problem repeats. (I have been having problems with the status bar lately and I suspect memory problems or other caused by the Gallery.) That the new streetview works without a hitch would indicate that the Camera/Gallery problems are not ARMv6 related.
Google TTS has no "certificate" so could not simply reinstall. I have this as a user APP from before but might have achieved this manually (I do really believe I saw it once installable from Play!) like I did for a transparent-modded GenieWidget found on XDA. I leave this one for now.
I placed the ThinkFree doc viewer instead of the Kingsoft Office which I had uninstalled before flashing this ROM (since these larger-dexed apps need to be uninstalled before reflash). I'll decide which to use later on--editing docs on this device does not seem too practical so the viewer, which works really nicely, might stay.
Related
After being a long time lurker here in XDA and having successfully fulfilled some requests on another thread, I thought I'd try to give something to the great community here.
You probably remember Ivan's kernels that provided the community with a version of intersectRaven's Hybrid AVS with 1113MHz overclocking. Unfortunately it looks like Ivan been very busy and is unable to update his kernels. So I have provided recent updates of intersectRaven's truly awesome kernels that includes the 1113MHz overclock for you all to enjoy. (I see this request a lot so maybe now intersectRaven won't be bothered by it again )
I absolutely take no creative credit in making these kernels as all I have done is used the open source code on intersectRaven's github and compiled it. The real credit goes to all the other coders here in this forum (cyan, pershoot, and especially intersectRaven).
When time permits, I'll try to update these kernels when improvements and/or bug fixes are made but I realistically only see myself updating these once or twice a week.
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions. Edit: Due to having virtually no free time, I don't think I can get fulfill requests in a timely manner... I'll try but I can't promise it. So sorry everyone -_-;
If you have the time and the will, I highly suggest you learn how to compile for yourself as I find it pretty fun and rewarding to make something for yourself. Guides and instructions can be found throughout the XDA forum and also on Cyanogen's wiki.
Before updating with these kernels, all I ask is that you make a nandroid backup in case something goes wrong.
Q & A:
-What's the difference between CFS and BFS?
See this short post for the difference between Completely Fair Scheduler and Brain F*** Scheduler. In summery, CFS is better for multitasking, BFS is better for user interactions (keyboard, homescreen swiping, etc).
-What's the difference between SVS and AVS?
Static Voltage Scaling will change the voltage based on a set table created by the kernel maker. Example: At a certain speed, say 245MHz, 925mV is feed into the CPU. At 998MHz, 1225mV is used.
Adaptive Voltage Scaling will change the voltage depending on temperature and CPU needs. Personally, AVS is running rock solid for me but I can't say for sure if it will be for everyone so SVS kernels will continue to be made available.
-What is this "No Audio Boost Version"?
Many of the custom kernels posted in this forum and the kernels used by default in the CM6 roms have this feature where it increases the loudness of the speakers during calls. Its been reported that some bluetooth headsets are overly sensitive to the increased loudness and some have reported that it distorts the audio quality even though volume has been lowered by the user. Due to an overwhelming request to make a kernel without this feature, I have included a separate set with each release that does not boost the volume.
-Can you make a higher overclock version of your kernel?
I was really against this because when I first tried to do this, my phone got really hot. But the requests kept on coming so I revisted this and possibly discovered a way to keep the temperature under control by limiting the max voltage to 1300mV. You'll find a 1190MHz version of my kernel here (Mirror Link).. Most users should be able to handle 1152MHz without any problems but some won't on 1190MHz. You'll know when your CPU can't handle a certain speed if you start to experience a sudden decrease in performance, lag, force closes, and spontaneous reboots. This won't be alievated unless more voltage is feed to the CPU but I'm not comfortable going beyond 1300mV. Now before you try these kernels out I gotta say this. I am not responsible if these kernels result in damaging your phone. Its purely for testing purposes and I really dont recommend using it as your everyday use kernel. If you do continue to use it, you should limit the max to 1113MHz or better yet 1075MHz (see previous question for the reason) if you care about battery life.
-I'm getting a black screen whenever I launch the camera app. Why? (720p related question)
The latest kernels with the 720p code only works with roms that has the 720p stock camera app and now the HTC camera app on Enomther's [ROM] as of 8/10/10. The latest cm6 nightly that has the 720p camera app as well as a few other roms out there that are based on cm6. You can try flashing charnsingh_online zip that contains the updated camera app if you don't want to use the nightly but I don't know for sure if his camera app is compatible with roms under RC2. Another alternative is to send in a request for a custom kernel and I'll make one for you without the 720p code.
2.6.38 kernels:
(Tested on Cyanogenmod 7 Nightlies)
Grab the kernels here: Mediafire
-Changes since 090311
-Set default sleep ideal freq to 128mhz for smartassV2 governor
-Bug fix for 1190MHz kernels, properly set max voltage to 1325mV
-Compiled HAVS 1190MHz kernels for those phone that can handle it
-Changes since 062411
Rebase source from IntersectRaven's Github
Highlights include:
-msm: Add support for voice call recording
-PM: Back off suspend if repeated attempts fail
-lib/sha1: use the git implementation of SHA-1
-arm: remove “optimized” SHA1 routines
-Fix AVS thread not being started.
-Added erasmux’s Smartass governor Version 2
-Changes since 062311
-Fixed ext4 partition support on sdcard.
-Changes since 052711
-Rebase to kernel version 2.6.38.8 from IntersectRaven's Github, with it 2 new governors (InteractiveX and SavageZen)
-Changes since 052611
-Rebased kernel source from intersectRaven's Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn't want to take a chance in WiFi not working for some.)
-Changes since 042111
-Rebased kernel source from intersectRaven’s Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn’t want to take a chance in WiFi not working for some.)
-Changes since 040911
-Bug fixes relating to USB file transfer speeds and addressed probable cause of WiFi problems for some.
____________________________________________________
If you want, you can buy me a drink (I like orange juice)
Have these kernels been tried and tested? Does the following work:
- Youtube
- Camcorder
- Googles
- Flash
- Unmounting sd card
- Wifi locations
and can you tell us more about the battery life by using this kernel?
p.s. Thanks for posting this btw...
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
Click to expand...
Click to collapse
Thats gr8...what about battery life? how do yo fare by using this kernel?
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Well....i like 800mV UV and OC, giving me the best balance between battery life and speed.
couldnt do an excact test on the time, but it lasts enough for my usage ^^
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
Click to expand...
Click to collapse
Glad you like it! You know it was partly you that made me want to start this thread.
great! i am really looking forward to it!
wildmonks said:
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
Glad you like it! You know it was partly you that made me want to start this thread.
Click to expand...
Click to collapse
"partly"
^^
xD
everything including goggles seems working on 800 bfs.. 41 linpacks.. cool
That was my result with linpack and this kernel!
{
"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"
}
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
wildmonks said:
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions.
Click to expand...
Click to collapse
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
mardox said:
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
Click to expand...
Click to collapse
CFS: http://de.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
nazrin313 said:
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
Click to expand...
Click to collapse
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
hondaguy said:
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
Click to expand...
Click to collapse
Im gonna charge it to 100% then leave it whilst I sleep...Tommorow im gonna im actually gonna use it
from my own usage since installing Froyo here is what I have found from testing various kernels (Unplugged at 7am)
- Froyo Kernel: Lasted till 10pm ish (Display on > 3 hrs)
- Preshoot 33.4 kernel: lasted me till 3pm ish (Display on approx 2 hrs)
P.s:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
daveid said:
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
Click to expand...
Click to collapse
Here yah go:
2.6.33.5_AVS-925mV_CFS_NoAudBoost_v2_060210.zip
I think all those years of listening to loud music has affected my hearing so I need the audio boost
I tested it out and it seems audio levels are back to standard (noticeably lower) but let me know if it doesn't work or if there are any other problems with it.
Update: Doh! I found a bug that I introduced into this no audio boost version. Seems that I broke music playback O_O. I fixed it and updated the above link. Sorry to those that download the other version -_- . . .
Audioboost is so necessary, i cant use any kernels without!
RinTinTigger said:
That was my result with linpack and this kernel!
Click to expand...
Click to collapse
t0ol said:
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
Click to expand...
Click to collapse
nazrin313 said:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
Click to expand...
Click to collapse
Interesting observation you all are getting. Must be the combination of BFS and OC? But I would not be surprised if battery life suffers a little... But very cool nonetheless
image sources: mik_os' profile and franciscofranco's dev thread
{
"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"
}
True, there are (tho outdated) threads like [Q] CM7 + Franco's Kernel??? and [Q] MIk + Franco but now this is NOT ONLY A THREAD FOR QUESTIONS.
As I've seen many people asking questions about this combination in one of the ROM/Kernel thread and they can't get answers from experienced users of this combination,
(some in mik's thread dont use franco, some in franco uses devoid only)......
QUESTIONS ARE NOW OPEN!
But make sure yourself is not a noob! if you are, try [READ FIRST] [REF] Dictionary for n00b - What is.../What does ...mean? first
Introduction
Many users have found that this combination is totally cool right?
however there may still be bugs in this combination
because mik_os' ROM is Android 2.3.x Gingerbread
and franco.Kernel is made for Android 2.2 Froyo <<< Yay BFS version for 2.3 is out XD
If you want to ask questions based only on mik_os' rom?
Here: [discussion]LG P500 mik_os's port of cyanogenMOD7, problems, questions, and answers.
If you want to ask questions based only on franco.Kernel?
Here: [Q] franco kernel problem
If you want to ask questions about the fantastic combination?
If you absolutely want to flash and try yourselves, but sometimes would prefer searching in XDA in advance and see what the others' results are?
or if you have tried this combination out, and would like to share to others so they can take your results as references before flashing?
Here, this thread, is what you want.
Btw, feel free to vote the poll at the top
Their Development Threads
[DEV][UNOFFICIAL][ROM][stable:version/testing:version] CyanogenMod version
[KERNEL][date of update] franco.Kernel |version|VR|CFS|SLQB|SMARTASS|TinyRCU|ZRAM|GPU+|. 39 |
Main Purpose of This Thread
- To share our results after flashing the combination
- When they update, we update!
- Confirm it if a bug has solved in later versions!!
- Questions are now open! Just make sure you've searched around and not wasting time here
- Only share your results after you confirm the errors are bugs of the combination instead of your own problem
- Also, we can directly answer the problem of a result if you know it is just human error instead of a bug BETWEEN THE COMBINATION!
- All other discussions are totally welcome!
Complete Results Sharing Form (if needed)
Italic words as examples
Bold words for you to copy
ROM version: 6.5.2
Kernel version: v15.1
App2SD: Darktremor 2.7.5.3-beta04
Data2SD: None
Additional information: ZRAM enabled
Stable Overclocking: 600/806 InteractiveX
Benchmark scores:
Quadrant 2000
Neocore 60fps
Error(s) or bug(s) discovered:
Bluetooth doesnt work
Call waiting disabled
Any suggestions for this thread are totally welcome!!
Hope this can help other users which are new to this combination but get tempted by the great performance comments everywhere
Remember, only share your results after you have tested the combination for at least 12 hours, thanks!
Myself as the first
ROM version: 6.5.2
Kernel version: v15.0
App2SD: Darktremor 2.7.5.2-1
Data2SD: None
Additional information: ZRAM enabled
Stable Overclocking: 122/729 SavagedZen
Benchmark scores: (if you want to share)
Quadrant 1534
Error(s) or bug(s) discovered: (if there is)
Random shutdowns/reboots!
with the latest v16 franco's kernel cmparts error on boot is gone
overclock settings are applied correctly, no need of setcpu anymore.
well done! there's still just the battery temperature bug though
vizzze said:
with the latest v16 franco's kernel cmparts error on boot is gone
Click to expand...
Click to collapse
what do you mean by cmparts error on boot?
You mean, there wont be random shutdowns when im using the phone?
there was, when it is v15
Miasmic said:
what do you mean by cmparts error on boot?
You mean, there wont be random shutdowns when im using the phone?
there was, when it is v15
Click to expand...
Click to collapse
never happened to me the shutdown problem... i mean the cmparts process that couldn't start on andoid boot because of franco's kernel
vizzze said:
never happened to me the shutdown problem... i mean the cmparts process that couldn't start on andoid boot because of franco's kernel
Click to expand...
Click to collapse
oooh would appreciate a lot if someone can tell me whether the shutdown problem has solved in v16
anyway thanks
for me
Cm7 6.5.2
kernel v15.1
zram enabled
oc 480/768 smartass
neocore 59.9
quadrant 1638
bug, kernelpanic with oc at 806 Mhz
indian65 said:
for me
Cm7 6.5.2
kernel v15.1
zram enabled
oc 480/768 smartass
neocore 59.9
quadrant 1638
bug, kernelpanic with oc at 806 Mhz
Click to expand...
Click to collapse
cool!! there are no random shutdowns in 15.1? did u experience v15.0 before
Sent from my LG-P500 using XDA Premium App
No random shutdowns in v16 ...
I'm on miks cm 6.5.2 with Franco kernel + zram and 320/748 oc on interactiivex.
Sent from my LG-P500 using XDA Premium App
I just flashed this kernel and zram and the quadrant scores at 806 mhz are almost the same scores I get with the original CM 7 kernel. Performance wise I think in games and just regular use it feels a lot more smoother. I just don't see it in the scores.
Heheheh Im now flashing the combination of miks 6.5.4 and franco's v16 BFS version
report to u guys 2 days later!
Cyanogenmod 7 by mik_os 6.5.4-stable with Franco's Kernel v16fix @729/480 smartass governor, no App2sd nor Data2sd due to my ****ty stock SD...
Linpack >= 8.8
Neocore (w/ audio): 57.3
Neocore (no audio): 60.5
Quadrant: 1486
6.5.4 Stable + v16.0 BFS Results
Ok so hey guys after using the newest combination for about a day ive come up with a detailed report for u
ROM version
6.5.4 Stable
Kernel version
v16.0 BFS for andy and mik
App2SD
Darktremor 2.7.5.2-1
Data2SD
None
Additional information
ZRAM enabled
Stable Overclocking
122/710 SavagedZen
Benchmark scores
Quadrant ~1400
(idk may be i got too many apps lol around 400)
LIST OF BUGS OR UNUSUAL ISSUES DISCOVERED AND COMMENTS
*"pure" = mik's rom + mik's kernel (the one attached with the rom)
- USB debugging icon is missing even it has solved in 6.5.4
- (already found this in older versions of the combination but didnt post) the keyboard sometimes doesnt pop out when necessary and wastes one more click (for me, App Protector Pro password insert page)
- My phone was stable @748 max using this combination but yesterday it panics at 729 and i was like =.=
- Performance boost is not as significant as when i was at 6.5.3 + v15.0 + zram
- (very disappointing) The CPU is not sensitive/reactive as before, even less reactive than pure 6.5.3, so i had to increase the minimum from 122 to 480 (I tested this with SeePU on at 0.5 second interval and scrolling homescreens, launching benchmarks etc.)
- Yea the camera crashes when restoring defaults in recording mode as stated in mik's dev thread
- The phone's temperature is average 39 degree vs pure's 33 degree
- Temperature displays incorrectly (39 degree as 3.9 degree) vs correctly in pure
CONCLUSION
lol mainly because of the insignificant performances boost even zram is on, im back to mik's pure now
good luck to u all and hope these help
Miasmic said:
Ok so hey guys after using the newest combination for about a day ive come up with a detailed report for u
ROM version
6.5.4 Stable
Kernel version
v16.0 BFS for andy and mik
App2SD
Darktremor 2.7.5.2-1
Data2SD
None
Additional information
ZRAM enabled
Stable Overclocking
122/710 SavagedZen
Benchmark scores
Quadrant ~1400
(idk may be i got too many apps lol around 400)
LIST OF BUGS OR UNUSUAL ISSUES DISCOVERED AND COMMENTS
*"pure" = mik's rom + mik's kernel (the one attached with the rom)
- USB debugging icon is missing even it has solved in 6.5.4
- (already found this in older versions of the combination but didnt post) the keyboard sometimes doesnt pop out when necessary and wastes one more click (for me, App Protector Pro password insert page)
- My phone was stable @748 max using this combination but yesterday it panics at 729 and i was like =.=
- Performance boost is not as significant as when i was at 6.5.3 + v15.0 + zram
- (very disappointing) The CPU is not sensitive/reactive as before, even less reactive than pure 6.5.3, so i had to increase the minimum from 122 to 480 (I tested this with SeePU on at 0.5 second interval and scrolling homescreens, launching benchmarks etc.)
- Yea the camera crashes when restoring defaults in recording mode as stated in mik's dev thread
- The phone's temperature is average 39 degree vs pure's 33 degree
- Temperature displays incorrectly (39 degree as 3.9 degree) vs correctly in pure
CONCLUSION
lol mainly because of the insignificant performances boost even zram is on, im back to mik's pure now
good luck to u all and hope these help
Click to expand...
Click to collapse
Excuseme how can i found mik_os's kernel??
chessy018 said:
Excuseme how can i found mik_os's kernel??
Click to expand...
Click to collapse
It is attached with the zip mik has provided in his dev thread
you have to flash the rom in order to get the attached kernel
for reference, the version of the kernel is displayed 2.6.32.41 on about-phone now
good luck!
ok guyz
i haven't tried 6.5.4 yet coz 6.5.3 working well until now ..
i have 6.5.3+ franco kernel 16 (old one) no zram nothing else
and performance is quit Good bt i think it was more better in Franco 15 kernel ..bt may b its only my thinking coz i analyze when we use data 3g wi fi phone getting heated nt tht much bt u can feel it don;t know..may b its only me feeling bt i have seen some users who already told me about that ..ok then as far as performance concern here check my attachment
battery is nt that bad at normal uses its around 30 hr long
Y.u.v.i said:
ok guyz
i haven't tried 6.5.4 yet coz 6.5.3 working well until now ..
i have 6.5.3+ franco kernel 16 (old one) no zram nothing else
and performance is quit Good bt i think it was more better in Franco 15 kernel ..bt may b its only my thinking coz i analyze when we use data 3g wi fi phone getting heated nt tht much bt u can feel it don;t know..may b its only me feeling bt i have seen some users who already told me about that ..ok then as far as performance concern here check my attachment
battery is nt that bad at normal uses its around 30 hr long
Click to expand...
Click to collapse
lol yea for me even zram activated there are significant performance regression of v16, could really feel it! i think its probably the "cpu responsiveness" ive mentioned
but well the 15 gives random shuts hate it
thx for ur info
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
franciscofranco said:
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
Click to expand...
Click to collapse
Haha franco thx for giving advice in this thread
oh ur tempting me mate thats cool
just a side question do i have to wipe anything except cache, dalvik, battery stats? if i give it a try to swap from mik's to andy's
or do i have to wipe everything and do a complete titanium lol
also why cant i see ppl using or comment about savagedzen? i personally use it idk why
and yeah thanks ive been searching for that for a while but cant find the clue and you answered me directly all my profile mins are 480 now!
franciscofranco said:
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
Click to expand...
Click to collapse
yes excuseme how do i change mik to andy? wipe which? thanks very.
Formerly: X-Ray USSR (Un-Scientific Study of ROMs)
Update: Background of the tests moved to the lower post. First post contains only the results and analysis.
Part 1
{
"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"
}
Part 2
Update: 18th September
Added 2 new ROMs - Jelly Sandwich 5 and GxG Jellybread
Click to expand...
Click to collapse
Update: 10th September
Added 3 new ROMs - Jelly Sandwich 5.1, Superleggera, and Flylight
Click to expand...
Click to collapse
Remarks
Ice Cream Purenesss Build 11
Switching to Airplane mode switched of WiFi
No 'clear' to remove all notifications at once
Uninstalling apps shows a dirty error - android.process.acore has stopped
JJ's Hybrid 3.3b
Antutu benchmarks terminated prematurely twice and the phone was running quite hot
After initial caching and media scanning, the ROM sped up incredibly
Xperia Stock 587
<didn't take down any notes for this>
Xperia Stock 587 (minus bloatware)
There still seems to be bloatware after the bloatware remover is applied - so there is more potential to gain performance
Rayonium ICS v6.2
<no notes here too>
Rayonium ICS v7
Credential manager stopped during one uninstallation, and keeps occurring during apps usage
Feels laggy while using - can't validate for sure
MIUI v4 2.8.17 (NeilDownx)
Great usability. While it seems to be laggy at times, it is not, as the results show
FXP 134 CM9
For some reason, graphics performance doesn't seem to be great though the CPU performance is top notch.
Even using the latest Adreno ICS / JB drivers is not helping
Jelly Sandwich 5
Similar installer like KA21. However looks a lot more customizable - gives you so many customizing options that I was almost lost.
I gather this is what is the Aroma installer. (Can compare this installer to others like -> Mandriva to Slackware Linux)
Ewwww.... bootanimation is gross -> needs a change first if I stick to this ROM
GXG Jellybread
Oh well, it is still Gingerbeard. Never going to be my long(er) term ROM. GB just feels so outdated now after ICS and performance was not so great that it could win me over.
Superleggera V3 ICS
Incredible graphics performance in Antutu. Literally blew everything else out of the water. The first time I have seen the knights scene touch 50fps, and this thing went on till 60fps.
Flylight ICS
Camera takes very fuzzy shots. First focus is slow, and then subsequent focus are quick.
Jelly Sandwich 5.1
This ROM is so much better than its last version. Looks like something to do with the drivers.
The camera seems a tad faster, but I get this feeling that there is some sort of IO issue on the ROM.
On Antutu, the IO scores were quite low and pulled the overall scores down. Also while taking burst shots on the camera, there was a feeling that it as struggling after 3-4 shots - looked like write delays
And as far as bootimages go, this is clean and professional
KA21
Easily the awesomest installation procedure/UI of any ROM that I have seen to date (my first experience with Aroma). The ROM felt very laggy.
KA21 Barebones
Even the barebones version of KA21 feels very laggy and is just not able to multitask
Analysis, Background and Testing Process
Analysis
After all the tests, it turns out that good ol' CM ROMs are still the best. CM9 is quite awesome on this phone and my primary 'focus' - the camera runs the best and fastest on CM9/FXP. Only trouble was with the graphics benchmarks - it performed well on some and not so well on others. Wonder why? Even the latest graphics drivers did not help.
I thought MiUI ROMs are heavy, but surprisingly it performed rather well. So did the stock ROMs though it had a lot of bloatware. I guess that the stock ROMs are highly optimized since they are made for the phone in the first place.
On the other hand, a ROM that had been quite hyped - KA21 quite simply sucked. And not just with Benchmarks, but it was just plain unusable and was all laggy and slow. I couldn't even go through with the tests and got fed up midway through.
What was interesting was on that on a whole all ROMs behaved almost the same. So its just a matter of preference whether you install a lot o 3rd party apps - then you need the ones with higher internal memory free after installation. Also, with 3rd party apps - like music, browser, movies etc. behave almost exactly the same - which is why you see it grayed out. The difference between the ROMs seemed to be in how efficient their media scanner and IO throughput was. After the first few runs of each app, the next runs were pretty much identical. So when your app is already buffered, then subsequent access is superfast.
Unfortunately subsequent accesses are limited by the amount of free RAM. And some heavy ROMs here leave very little free RAM to the apps. This is where you need a good balance of free ROM and good memory management in the ROMs.
The best balance that I found - for my needs, was FXP/CM9 and I am sticking to that.
All in all, it will just come down to personal preference of look and feel - whether someone prefers Sony's look, or stock Android's look,or MiUI's convenience and ease of use.
18th September:
I added a couple more ROMs to the mix. I tried the much demanded Jelly Sandwich - it felt nice and looked very promising, but somehow did not deliver. I had a lot of expectations from this ROM. Benchmark scores turned out quite pathetic and this ROM ranks among the low ones. I felt so bad that I even tried a barebones version by removing almost everything and choosing the lightest components but performance did not improve significantly enough even to pull it from the orange or yellow band to one band higher.
I also benchmarked a gingerbread ROM, but even that did not deliver to my expectation. Looks like some of the best ROMs are the ICS roms. In fact I even tried a JB rom, but most of it did not work and I just did not continue with the benchmarking.
20th September:
Looks like some new ICS GPU drivers are doing the rounds. I've never seen the Ray pull off such great FPSes before. Flylight has got the best driver yet, hope it rubs off on the others.
Background
I had thought of starting off a new thread for a personal comparison that I am doing. I felt this would benefit others as well who loves playing around with ROMs, or who is looking for a ROM that suits their needs on paper.
I have tried out almost all ROMs on the forum for the Xperia Ray and like a spoilt child, I am never satisfied with any one. Probably the longest that I have had one is for 2 weeks. When I think back, I realize that most ROMs were chucked away - primarily because of boredom; but an other reason was that the performance deteriorated or I was not able to play some touted games.
I have now settled down to the following facts
1. Xperia Ray is not meant to play games (debatable - but that's my stand)
2. If you fill the last MB on the phone with apps, the performance is bound to drop
So, I have decided to do a un-scientific study of the various ROMs that are currently there to decide on one ROM and settle on it for a while (1-2 months at least :silly: )
The control device is my 5 month old Ray. It has a 16GB Class 10 card. The kernel is a XRay v7.3.431 overclocked to 1.4GHz. (the only exception would probably be the FXP ROMs which comes with its own kernel and I don't suppose it runs on the XRay)
The device will have a factory reset, all possible wipes, all possible formats, before installing the ROM and taking readings. There will be some measurements, some benchmarks, and some 'feeling' measurements. Nothing will be installed other than the benchmark tools and I will remove all apps from the recently-run apps before taking each measurement.
Testing Process
The setup of the phone is as follows for the tests
Preparation
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. Format system
5. Format data
6. Format cache
ROM Installation
1. Install ROM
2. Install any dependent patches
3. Flash compatible Kernel (if required, else stick to XRay 7.3.431)
4. Do initial setup - without using a google account
5. Overclock to 1.4GHz (use built in configuration, or install No-Frills CPU)
6. Set CPU Governer = SmartAssV2, IO Scheduler = noop (where possible)
7. Let phone rest for 5 minutes
8. Switch on WiFi
9. Activate GPS and location usage
10. Switch on installation from unknown sources
11. Add a google account and sync only browser and contacts
12. Let phone rest for 5 minutes after sync is complete
13. Go into Airplane mode
14. Keep charger plugged in
15. Start tests
Tests
1. Unload all apps from recent apps
2. Install app for testing (other than stock or whatever exists on the phone)
3. Run tests
4. Uninstall app
5. Repeat for next test
Note: All apps (for testing loading times) are opened once to dismiss off with popups and notifications and so that any caching and optimization can be done. They are then unloaded and tests are started. Theory is that the user is concerned with the speed of loading for commonly used apps, so they would have been opened many times and optimized/cached.
Q: Is there a way to integrate the google docs spreadsheet inline in this forum? Will make my life that much easier. Or at least a way to embed a HTML table into this post?
Good luck.. I've tried them all (unlocked bootloaders).
And there isn't better combination than
Kernel: Aire V2 + initd
Rom: RayoniumICS 6.2 (just because i don't like nxt pack)
stebenwulf said:
Good luck.. I've tried them all (unlocked bootloaders).
And there isn't better combination than
Kernel: Aire V2 + initd
Rom: RayoniumICS 6.2
Click to expand...
Click to collapse
well could you post a simple step by step walkthrough to achieving this result...
rom study?
i figured (using gxg jellybread right now) that my ram is getting less.
after flashing and using some certain apps my complete ram was about 300mb, after restoring my (about 200, lot of games) via apk-installer, my ram (as you can check via applications -> running services) went down to about 220-230mb
how is that possible? i dont get it.
with ics i did not have this problem (afair) but ics is too slow for the ray imho.
JB is fun, but it is still in infancy. I wouldn't use it as my daily ROM yet. So I will stick to ICS comparisons for now, and will add JB as the ROMs get more stable. I could have added GB to the comparison too, but then GB is soo boring that I wouldn't want to have it around on my phone for even a while.
geekoo said:
JB is fun, but it is still in infancy. I wouldn't use it as my daily ROM yet. So I will stick to ICS comparisons for now, and will add JB as the ROMs get more stable. I could have added GB to the comparison too, but then GB is soo boring that I wouldn't want to have it around on my phone for even a while.
Click to expand...
Click to collapse
jellybean is not ready for daily use yet, i agree. the rom (the android version) i was talking about was gingerbreaed.
gxg jellybread is just a gb-rom that looks a little bit like jellybean, nothing more, but its still gingerbread
yeah, gb might be "boring", but its the fastest and fulliest functional rom you can get for ray right now.
if this weird ram-issue wouldnt occur i wrote about...
i am currently using Paranoid Android v1.4.1 (ICS Version) and right now, i am pretty satisfied.. it's smooth enough for daily use..
i used 2 extra apps..
automemory killer pro - set to extreme
ram manager pro - set to hard gaming
cpu governor - performance
max- 1ghz
min- 158mhz
this is the result of using FPS2D..
Updated the charts with my measurements and comments. Hope you find this useful if you are looking for a new ROM.
Nice thread, I really like the evidence-based, unbiased methods. As a scientist myself this is important in any comparison This was something I was contemplating doing myself - now I don't have to!
thanks for the chart
I think I will still stick with JJ's 3.3b
JJ's may not be the fastest rom but it still on the fast side and offer a lot feature too.
And I modded the hell out of this so I will miss my mod when install other rom.
foggyflute said:
thanks for the chart
I think I will still stick with JJ's 3.3b
JJ's may not be the fastest rom but it still on the fast side and offer a lot feature too.
And I modded the hell out of this so I will miss my mod when install other rom.
Click to expand...
Click to collapse
Oh, JJ is definitely one of the fastest ROMs there. In fact JJ, Stock, and FXP are almost on par (what's 1 or 2 points?) In fact the only thing that let JJ down was the amount of free RAM. Other than that, in the benchmarks, it was indeed consistently the fastest ROM.
Voodooguru said:
Nice thread, I really like the evidence-based, unbiased methods. As a scientist myself this is important in any comparison This was something I was contemplating doing myself - now I don't have to!
Click to expand...
Click to collapse
Thanks
Spent almost a week without a life getting this chart ready - wiping, rewiping, installing, uninstalling, measuring etc etc
Did you uninstalled the bloatware from stock ROM using any automatic bloatware removal tool or uninstalled the applications manually?
According to my experience : after I removed bloatware one by one using 'root uninstaller' the free internal memory became 332 MB. (I removed facebook inside xperia, google maps, talkback etc also)
and before i started installing the applications and mods the the free RAM was around 200 - 195 MB.
I can play most of the games (which are playable on Ray) very smoothly.
The last game I played was NFS hot persuit. The graphics ran super smooth, but the sound sometimes become choppy though.
I actually don't see a very big reason to jump from stock ROM 4.1.B.0.587 (minus bloatware, plus some of the very very useful mods and tweaks available in this forum) to a custom ROM.
Some people may have different views. I respect their views, but for me, I am happy with 4.1.B.0.587
Really nice thread
By Rizal Lovins [email protected]"Love Indonesia"
JJ's is the best .. at least for me
i've been flashing different rom, but i been missing the GB experience.. GxG's Jellybread is quite amazing for it's ICS-GB-JB experience.. but it's actually GB. i haven't tried the new stock 587 though, because of your chart i can see the performance increase with the new stock.. i will give it a try thanks mate..
tintin100 said:
Did you uninstalled the bloatware from stock ROM using any automatic bloatware removal tool or uninstalled the applications manually?
According to my experience : after I removed bloatware one by one using 'root uninstaller' the free internal memory became 332 MB. (I removed facebook inside xperia, google maps, talkback etc also)
and before i started installing the applications and mods the the free RAM was around 200 - 195 MB.
I can play most of the games (which are playable on Ray) very smoothly.
The last game I played was NFS hot persuit. The graphics ran super smooth, but the sound sometimes become choppy though.
I actually don't see a very big reason to jump from stock ROM 4.1.B.0.587 (minus bloatware, plus some of the very very useful mods and tweaks available in this forum) to a custom ROM.
Some people may have different views. I respect their views, but for me, I am happy with 4.1.B.0.587
Click to expand...
Click to collapse
can i ask for the list of playable games the run in your stock 587? i would be thankful for that
tintin100 said:
Did you uninstalled the bloatware from stock ROM using any automatic bloatware removal tool or uninstalled the applications manually?
Click to expand...
Click to collapse
I used just the automatic bloatware removing tool that knight has posted on the forum. I have mentioned in the comments in the chart there is still so much scope to remove bloatware, so obviously a lot more space and memory could be freed up.
I think Sony has done quite a good job with their ROM - not considering the bloatware.
Do you really prefer the CM9 camera instead of SE stock camera?
can you test Jellysandwich Mr. Tapa ROM
{
"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"
}
DESCRIPTION
This is a custom based Kernel for the D855/D852/D851/D850/VS985/LS990 variants of the LG G3 with performance enhancements and bug fixes that I have been using personally for a few months, thought it is time to share since I have had no inconvenient bugs and quite a big performance increase and smooth UI benefits. The intention is to have a minimal light-weight kernel that is fine tuned for the device.
FEATURES
User space voltage control
Backport MSM devfreq features from 3.18 Kernel for the smoothest experience, includes adding cache fabric frequency scaling and better bus utilization as well as the mincpubw governor
User space display color calibration (KCAL)
Deeper memory controller power savings on suspend (deeper power savings while sleep)
Two new L2 cache frequency steps: 1.88 & 2.03 GHz, allows for better multi-core utilization and hit rates
Wireless roaming disconnecting is now fixed
IRQ Balancer enabled with proper SELinux support to spread out the interrupts of our SoC
IntelliPlug to allow lower thermal dissipation by keeping some cores alive to distribute loads and keep frequencies lower accross SoC die
Reduced heat when using wireless chargers
Memory and cache subsystem optimizations, you will feel it int the UI
Adreno Idler to get better GPU frequency utilization and battery life [removed as msm-adreno now idles properly]
Interactive governor tweaks to focus on lower frequencies while still maintaining fluidity in the UI
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Undervolted the Adreno 330 GPU voltage rail to keep things cooler, and reduced the GPU min frequency to 27 MHz while keeping it's temperature cool to reach 620 MHz overclock
Default thermal values work ok, since GPU voltage rails and others were shaved a few mV
100 Hz tick to prevent excessive battery usage, the smoothness of the UX does not come alone from raw processing -- there are many other changes in the subsystem that helped achieve the fluidity
An ultra low value in the interactive min_sample_time so that the interactive governor does not hover on excessive frequencies
Heavily tuned the GPU bandwidth and bus requirements to match closer the capabilities of the device and thus preventing micro-stutters
Optimized the MSM crypto engines thanks to @waau
Updated the KGSL drivers so that we can use the Adreno userspace drivers version Adreno-MOB30M-for-LG-G3-AOSP.zip
DOWNLOADS
AnyKernel: Click Here (Check Top of the Post, Download Tab)
SOURCE
D85X-Kernel-Gamma GitHub Source
NOTES
I recommend turning NFC off for way better idle battery consumption :victory:
KNOWN BUGS
FM Radio is causing hangs, still needs investigation
<< If you like my work here is my hat, please donate! >>
XDA:DevDB Information
Gamma Kernel , Kernel for the LG G3
Contributors
Omar-Avelar
Source Code: https://github.com/oxavelar/D85X-Kernel-Gamma
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 90.0.0
Stable Release Date: 2018-05-10
Created 2016-08-09
Last Updated 2018-05-13
Thank you for this kernel, I have a question:
Fast charging is implemented?
Thanks again
@Omar-Avelar Download link for d855 leads to d851 version and vice versa..
Sent from my caseless LG G3, because I believe in myself
Is there a sound mod for headphone gain?
download link need to update, will try it and report.
THANK YOU!!!!!
after instelling the kernel on my d855 with the xenon rom it doesnt charge via usb in the pc... i am at work right now and cant check in the wall socket.
@agdish84, I have now updated the links, thanks... I missed that.
Hey @jochem86, USB charging is working on CM ROM's so I wonder if Xenon ROM is doing anything funky, mmm... I will check if Xenon has anything strange but it is not touching anything charge related.
This Kernel does not support USB force fast charge because fast charging will cause batteries to age faster. It's a trade-off, and usually ends up providing more heat. Not sure if I will put support on forced USB fast charge or not.
Omar-Avelar said:
@agdish84, I have now updated the links, thanks... I missed that.
Hey @jochem86, USB charging is working on CM ROM's so I wonder if Xenon ROM is doing anything funky, mmm... I will check if Xenon has anything strange but it is not touching anything charge related.
This Kernel does not support USB force fast charge but might do add it in the week if a lot of people feel the need of it. [Btw, personally this is the main reason why I did not enable fast charging enabled sysfs force control - URL]
Click to expand...
Click to collapse
Dirty flashed the xenon again and it charges again without any problem. I have to say some other roms it doesnt charge in usb when i am using it... with xenon it doest but very slow, that is normal. But also in deep sleep, it doenst charge a bit... i guess in xenon the fast charge is enabled and other roms not bu default. i hope you figure out whats messign it up.
jochem86 said:
Dirty flashed the xenon again and it charges again without any problem. I have to say some other roms it doesnt charge in usb when i am using it... with xenon it doest but very slow, that is normal. But also in deep sleep, it doenst charge a bit... i guess in xenon the fast charge is enabled and other roms not bu default. i hope you figure out whats messign it up.
Click to expand...
Click to collapse
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Omar-Avelar said:
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Click to expand...
Click to collapse
That was my intention to give you my experience but my batt was pretty low so i changed it back to stock kernel... as i am on my work right now but for those few minutes i tried it felt pretty smooth.
Omar-Avelar said:
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Click to expand...
Click to collapse
In terms of performance? Oh yes, give me time to flash CM13 and test UI smoothness, I have feeling this is right thing for that. Waiting for this for a long time.
@Omar-Avelar do you have any plans on adding gamma control? I'm really enjoying myself atm running it with Zephyr os rom. Ty for your hard work!
Sent from my caseless LG G3, because I believe in myself
AICP booted, the 10 seconds I have had it on it seems really snappy, will let you know how it goes.
stuck on splash screen after installing...
D855 32GB - Fullmics ROM
grymmy said:
stuck on splash screen after installing...
D855 32GB - Fullmics ROM
Click to expand...
Click to collapse
Fulmics is stock based from what I have read (I've never installed it personally). But I am glad to hear that you tried it out there but too bad it doesn't work on Fulmics!
I will add some notes to the thread to let other people know.
Jagdish84 said:
@Omar-Avelar do you have any plans on adding gamma control? I'm really enjoying myself atm running it with Zephyr os rom. Ty for your hard work!
Sent from my caseless LG G3, because I believe in myself
Click to expand...
Click to collapse
I think I will do that, it might be about the only things that are do needed and won't interfere as much with stability. Gimmie a few weeks to get some free time.
Omar-Avelar said:
Fulmics is stock based from what I have read (I've never installed it personally). But I am glad to hear that you tried it out there but too bad it doesn't work on Fulmics!
I will add some notes to the thread to let other people know.
Click to expand...
Click to collapse
thank you for such speedy feed back. I'm about to install Zephyr os rom and test...thanks again
Using this kernel made me love my phone again. Was using Latest CM 13 and UI was time to time laggy and slow. Flashed this kernel and device runs smooth as butter. Love that kernel does not overclock anything so i know that i don't shorten life span of my cpu. Kudos to @Omar-Avelar for developing something like this!
Could you add DT2S and DT2W on your kernel?
#ParanoidAndroid
Phone heats up a lil while charging... Didn't use it or anything, just picked it up to see the time and it felt rather warm to me, using zephyr rom and a lil undervolting. Btw, during regular usage phone is stone cold, kudos!
Sent from my caseless LG G3, because I believe in myself
{
"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.