Related
Hi,
I've had my Archos G9 80 updated to the latest android official 4.0.5 from and since then i'm expriencing lots of crushes and freezes. I'm getting them randomly with no specific app working.
Also, i have tried to do full formats (Android + Data), and still having same issues.
Does anyone have any idea what else i can try?
Thanks.
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
DeeDroid said:
I changed the CPU govenor from "hotplug" to "interactive".
Click to expand...
Click to collapse
how this is done? Ι have the same problem!
africa_twin said:
how this is done? Ι have the same problem!
Click to expand...
Click to collapse
Yes, can this be done from the phone itself? Within the ROM?
You can set this in any tool that is intended for overclocking. I don't overclock, I only changed the Govenor.
I use "SetCPU". ("No-frills CPU Control" should do the same.)
So does this have any other effects on the phone?
RichWPX said:
So does this have any other effects on the phone?
Click to expand...
Click to collapse
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.
I downgraded the device to 4.0.4 and since then, no crushes.. I guess for some reason 4.0.5 isn't stable on my device.. ill stick with this version unroll they get another one out..
To downgrade, just install official update file of the version you want to upgrade to..
DeeDroid said:
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.
Click to expand...
Click to collapse
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.
RichWPX said:
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.
Click to expand...
Click to collapse
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.
DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
changing govenor from "hotplug" to "interactive" seems to help against random freezes. 4 days without problems until now i had freezes with ics, but never with honeycomb.
device: archos 101g9
[ROM] Archos ICS - Firmware 4.0.5(4.0.3) - ROOT & BUSYBOX , Only for SDE (thanks surdu_petru)
DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
That seems to be my problem too. Setcpu requires root. is there a very easy way to do this, just to run this setcpu? There used to be a z4 tool, but can't seem to find it anymore.
Edit I see that I need superoneclick. Will temporary root suffice or will I need permanent root to change the governor setting.and keep it so.
Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S
DeeDroid said:
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.
Click to expand...
Click to collapse
I have the same experience. Hc was laggy and slow. Ics is much faster and smoother.
Sent from my ARCHOS 80G9 using Tapatalk
gen_scheisskopf said:
Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S
Click to expand...
Click to collapse
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Will "Superoneclick" not root my device ?
sbtwister said:
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Click to expand...
Click to collapse
Special Developer Edition
sbtwister said:
Will "Superoneclick" not root my device ?
Click to expand...
Click to collapse
No, it won't. Gen9 system layout is different than for most other devices
hey, back to topic
5 days without freeze with govenor "interactive". i witched back to "hot plug" this morning and had to reboot my tablet 2 times today. for my case, "interactice" seems to help against random freezes.
mines performance intstead of interactive... experienced some freezing n interactive..
Man I'm really pissed.
Yesterday I had to hard reboot 7 times
Sent from my X8 using xda premium
hmm,
sounds not good. archos stands not for high quality i guess. we get what we pay . i had an archos 101g8, now a 101g9 and trouble with hard-/firmwares since 2010. i think, this was the last one - no furthermore advantures
@IrishStuff09: you did reformat for ics or upgrade from honeycomb? the best way is to start from scratch and skip upgrades.
I have a couple of questions regarding some options under "Developer Options" in the settings menu. The first questions I have is regarding GPU Rendering. Should we enable it and has anyone noticed any positive/negative effects after enabling it? The next question I have is about the option to limit background processes. I have been limiting the processes to 4 but it seems like every time I go back into this sub menu. it is always back to it's stock setting of "Standard Limit'. Does anyone know how to make it stay on 4?
Force gpu rendering in theory makes ui more responsive and fluid, but if apps are not specifically coded for that, they can look weird with black bars and abnormal colors. I noticed this in few apps and turned it off. I am not sure why ur background process number is not sticking, but honestly u will be more happy if u leave it at default coz with 2 gb ram there is enough memory to run all ur background services and some more.
Sent from my SGH-T999
jrwingate6 said:
I have a couple of questions regarding some options under "Developer Options" in the settings menu. The first questions I have is regarding GPU Rendering. Should we enable it and has anyone noticed any positive/negative effects after enabling it? The next question I have is about the option to limit background processes. I have been limiting the processes to 4 but it seems like every time I go back into this sub menu. it is always back to it's stock setting of "Standard Limit'. Does anyone know how to make it stay on 4?
Click to expand...
Click to collapse
Dude my background processes keep reverting back to i noticed when i went back in i know it stuck for me on complete stock but i am on free gs3 rom right now and think it might be something conflicting with the modified build.prop tweaks he may have in there. ??? Anyways that switched to limiting 4 background processes and putting window animation and transition animation to 0.5 i noticed a difference . Although i dont really think our phones need this because of the 2gb of ram now maybe the g2x did and as far as gpu rendering u will only notice a difference in some apps that are optimized for this. If not u will notice some artifacts on the screen thats usually your first hint to switch it off because it isnt playing nicely with that particular App. But yes especially in some games u should notice a slight difference. Again if it was the g2x having no hardware accelaration then having it u saw a big difference....our gs3's our such beasts that its minimal to our eyes
sarni84 said:
Dude my background processes keep reverting back to i noticed when i went back in i know it stuck for me on complete stock but i am on free gs3 rom right now and think it might be something conflicting with the modified build.prop tweaks he may have in there. ??? Anyways that switched to limiting 4 background processes and putting window animation and transition animation to 0.5 i noticed a difference . Although i dont really think our phones need this because of the 2gb of ram now maybe the g2x did and as far as gpu rendering u will only notice a difference in some apps that are optimized for this. If not u will notice some artifacts on the screen thats usually your first hint to switch it off because it isnt playing nicely with that particular App. But yes especially in some games u should notice a slight difference. Again if it was the g2x having no hardware accelaration then having it u saw a big difference....our gs3's our such beasts that its minimal to our eyes
Click to expand...
Click to collapse
the processes reset on mine too. This happened on my amaze too. It's ICS doing it not just our phone.
Sent from my SGH-T999 using xda app-developers app
Its now been more than a year and half since Ice Cream sandwich was released. While many apps now use gpu rendering, the older ones that don't get a huge smoothness increase when this setting is enabled. I have been using this setting since I got my galaxy nexus over a year ago and the difference between on and off is huge. Its even worse on devices like the nexus 10 where without the setting on many apps are almost unusable but become butter smooth with it on. I think it is time for google to enable this setting by default, especially now that they hid the developer settings menu away.
Does it increase battery usage?
No they shouldn't. If an app benefits from GPU rendering then that's up to the app developer to implement. Forcing it causes problems with some apps.
Is op to lazy to turn it on every time he/she flash a ROM ? Lol
Sent from my Galaxy Nexus using xda premium
Alton (Halo 2) said:
Is op to lazy to turn it on every time he/she flash a ROM ? Lol
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, I always have it on. But most people don't even know to turn it on (people that aren't into tech) and it makes a huge difference when its on. Also I have yet to see any apps that have issues with it on and it doesn't increase battery life. In fact it improves it in many cases. Go use a nexus 10 and open adobe reader without the setting on. Then use it again with it on. The difference is huge. It goes from like 5 fps to nearly 60fps. Many app developers are still targetting gingerbread which means that gpu rendering is off on those apps. On these 720p and 1080p phones it makes scrolling very laggy when performed in software.
Yeah, viewing pdf files without gpu rendering on is pure nightmare. Just like scrolling in xda app. The difference is huge.
Sent from my Galaxy Nexus using xda premium
Yeah, the benefits far outweigh any cons and for every one app it breaks (i haven't found any in over a year) there is 1000 that it improves greatly.
I forgot about this option thanks for reminding me
How beneficial is the force 4x MSAA do you think?
Sent from my Galaxy Nexus
blackhand1001 said:
Its now been more than a year and half since Ice Cream sandwich was released. While many apps now use gpu rendering, the older ones that don't get a huge smoothness increase when this setting is enabled. I have been using this setting since I got my galaxy nexus over a year ago and the difference between on and off is huge. Its even worse on devices like the nexus 10 where without the setting on many apps are almost unusable but become butter smooth with it on. I think it is time for google to enable this setting by default, especially now that they hid the developer settings menu away.
Click to expand...
Click to collapse
wat
This is a developer setting and apps who are intended to be accelerated, already are. There are too many fags playing with those options and then ranting on the Play Store about app behavior. Dev settings were hidden with a reason with 4.2.2. Jesus, there just isn't a month where this **** isn't brought up again.
madd0g said:
wat
This is a developer setting and apps who are intended to be accelerated, already are. There are too many fags playing with those options and then ranting on the Play Store about app behavior. Dev settings were hidden with a reason with 4.2.2. Jesus, there just isn't a month where this **** isn't brought up again.
Click to expand...
Click to collapse
Name me an app that doesn't work with it turned on. I haven't seen any.
The issue is that there is no way to turn on acceleration by default in an app unless you target honeycomb or higher which means you'll have to make a seperate gingerbread app. The pros of making this on by default far outweigh the cons and any apps that don't work with it will finally be pushed to update to use it.
blackhand1001 said:
Name me an app that doesn't work with it turned on. I haven't seen any.
The issue is that there is no way to turn on acceleration by default in an app unless you target honeycomb or higher which means you'll have to make a seperate gingerbread app. The pros of making this on by default far outweigh the cons and any apps that don't work with it will finally be pushed to update to use it.
Click to expand...
Click to collapse
Survivalcraft. Check the FAQs. http://kaalus.wordpress.com/faq/ First one.
jesusice said:
Survivalcraft. Check the FAQs. http://kaalus.wordpress.com/faq/ First one.
Click to expand...
Click to collapse
Well then google should make it an opt out setting for app developers and not an opt in. I still haven't seen any other apps with the issue. This is how it is when targeting ice cream sandwich but for gingerbread theres no way to enable it.
Even if that one app has issues, thousands of other apps get huge performance increases and no issues. I'd say the benefits are still worth the drawbacks.
blackhand1001 said:
Well then google should make it an opt out setting for app developers and not an opt in. I still haven't seen any other apps with the issue. This is how it is when targeting ice cream sandwich but for gingerbread theres no way to enable it.
Even if that one app has issues, thousands of other apps get huge performance increases and no issues. I'd say the benefits are still worth the drawbacks.
Click to expand...
Click to collapse
Enabling it causes some pictures not to show in the xda app
Sent from my Galaxy Nexus using xda app-developers app
[Q] Anyone can explain the difference in "Disable HW Overlay" on 4.1.2 and 4.2.2
Using AOKP 4.2.2 ROM and disabling HW Overlay drammaticly increased phones speed so it was butter smooth on any launcher. Switched to CM10 4.1.2 ROM and launcher performance was medium without enabling this option . Went to turn on "Disable HW Overlay" and made my phone 10 times slower instead... Now, does anyone care explaining me why is this option boosting my performance in 4.2.2 and slowing it down on 4.1.2?
I would really like to use 4.1.2 with boost like in 4.2.2.
srtjko said:
Using AOKP 4.2.2 ROM and disabling HW Overlay drammaticly increased phones speed so it was butter smooth on any launcher. Switched to CM10 4.1.2 ROM and launcher performance was medium without enabling this option . Went to turn on "Disable HW Overlay" and made my phone 10 times slower instead... Now, does anyone care explaining me why is this option boosting my performance in 4.2.2 and slowing it down on 4.1.2?
I would really like to use 4.1.2 with boost like in 4.2.2.
Click to expand...
Click to collapse
Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping.
Basically, using hardware overlays can reduce CPU usage by quite a bit, so I would leave it enabled, if only we had a much more capable hardware. Disable it and the latency period for applications and the OS (any OS, not just Android) itself to render things will go way way up because it has to check to make sure it's not screwing with memory that is supposed to be dedicated to another task than its own. Hardware overlay ensures everyone has their own partition of memory so they don't have to do those checks and so latency to render things on the screen decreases dramatically. I've never experienced your issue, because I've never tried a 4.1.2 ROM... Always been on either 2.3.7 or 4.2.2... Enabling the HW Overlay does cause certain applications such as Gallery to run faster, but on an overall, its laggy due to our hardware restrictions.
XZP 120Hz QUEST
First i would like to push this thread forward cause i thing phone has some potential still to unlock. There is much writen about XZP - 120hz but nothing concrete or usable in stock, before i write something of mine i would like to credit a developer which inspired me to snoof around a bit:
thanks to "kholk @ Github" and here is kholk,s work:
https://github.com/sonyxperiadev/ke...si-panel-somc-synaptics-sharp-4k-cmd-ID6.dtsi
https://forum.xda-developers.com/newthread.php?do=newthread&f=6237
thanks to Paranoid Team for developing a great rom for XZP
http://paranoidandroid.co/downloads/maple
So lots of us have rooted device and in root explorer i triggered search for "SHARP" word just from curiosity, after minutes of waiting search completed and 4 folders stand out:
qcom,mdss_dsi_sharp_4k_dsc_cmd
qcom,mdss_dsi_sharp_4k_dsc_video
qcom,mdss_dual_sharp_1080p_120hz_cmd
qcom,mdss_dsi_sharp_1080p_cmd
Is it possible to enable this mode from this folders and sub files in stock rom? And how would i an amateur user switch this modes?
I will make backups in twrp and then myself try to mess up with files or at least go through them if something punches me in the eye i will report, what i meant to say it would be nice if above links could be used to inject it into our stock roms?
Oh, i recently installed paranoid android and there are settings to enable 120hz but are not yet working, you can google it, so xzp is at least in good hands and path, hope we wount wait too long for this goodies
If annyone has some succes or ideas, observations please write it down maybe some devs will look into them
stipi69 said:
XZP 120Hz QUEST
First i would like to push this thread forward cause i thing phone has some potential still to unlock. There is much writen about XZP - 120hz but nothing concrete or usable in stock, before i write something of mine i would like to credit a developer which inspired me to snoof around a bit:
thanks to "kholk @ Github" and here is kholk,s work:
https://github.com/sonyxperiadev/ke...si-panel-somc-synaptics-sharp-4k-cmd-ID6.dtsi
https://forum.xda-developers.com/newthread.php?do=newthread&f=6237
thanks to Paranoid Team for developing a great rom for XZP
http://paranoidandroid.co/downloads/maple
So lots of us have rooted device and in root explorer i triggered search for "SHARP" word just from curiosity, after minutes of waiting search completed and 4 folders stand out:
qcom,mdss_dsi_sharp_4k_dsc_cmd
qcom,mdss_dsi_sharp_4k_dsc_video
qcom,mdss_dual_sharp_1080p_120hz_cmd
qcom,mdss_dsi_sharp_1080p_cmd
Is it possible to enable this mode from this folders and sub files in stock rom? And how would i an amateur user switch this modes?
I will make backups in twrp and then myself try to mess up with files or at least go through them if something punches me in the eye i will report, what i meant to say it would be nice if above links could be used to inject it into our stock roms?
Oh, i recently installed paranoid android and there are settings to enable 120hz but are not yet working, you can google it, so xzp is at least in good hands and path, hope we wount wait too long for this goodies
If annyone has some succes or ideas, observations please write it down maybe some devs will look into them
Click to expand...
Click to collapse
I wish to have it in Android pie coz of this I really like this phone
I'm building Zest Kernel got this device soon and that surely seems like a great idea. I'm personally thinking of trying to force 120Hz as I forced 90Hz on the Essential phone with celtaire. The only problem is it seems the userland side of things may have limitations to 60fps which would need a bypass somehow, as Razer did.
PA seems interesting that they have a switch so I'll try look at they code to see (if they have the piece of the puzzle I was missing that would be amazing).
Great this would be awesome :fingers-crossed:
can't wait, 60 hz really hurts my eyes.
amakuramio said:
can't wait, 60 hz really hurts my eyes.
Click to expand...
Click to collapse
Lol, as in its pretty smooth anyways. But 120Hz is likely darn water flowing.
Any update on this lol went back to my xz premium
I've been thinking about how to get this working, but it seems tweaking the qcom,mdss-dsi-panel-framerate value on the default configuration (1080p) alone is not enough, although from an initial diff between the original 60Hz configuration and kholk's newly added 120Hz configuration on SonyOpenDevices kernel showed only the framerate value was changed (there are probably things I didn't find).
I've tried changing it from 60 to 90 and 120. Changing to 90 has no apparent effect (the system still renders at 60 FPS), while changing to 120 caused everything to be rendered at 24 FPS (very sluggish). Still, it seems the refresh rate change is indeed set to the value, as this app (which looked rather dated and unreliable) did show the system's refresh rate (rr) is configured to the value written in the dtsi.
From the looks of it, it seems the dtsi file controls what refresh rate be configured at kernel level, but something's probably needed in the userland to get it function properly. But still, it's interesting that setting the value to 120 would cause the system to render everything at 24 FPS, while setting the value to 90 doesn't have any impact.
I posted some details here yesterday as I was mainly building my own CarbonROM zips with some own configurations. For CarbonROM, the dtsi file is located in arch/arm/boot/dts/qcom/dsi-panel-maple.dtsi.
Back to the OP... I've found the entries as well. However, even after I modify the dsi-panel-maple.dtsi and that the modified value is registered somewhere, the value in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dsi_sharp_1080p_cmd is still 60 (003c). This file is probably the one representing the original 60Hz command:
https://github.com/CarbonROM/androi.../boot/dts/qcom/dsi-panel-sharp-1080p-cmd.dtsi.
And there's the 120Hz configurations placed in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dual_sharp_1080p_120hz_cmd.
This file might be related to it. However, this file is significantly different from the 1080p (60Hz) one and I'm wondering if this is indeed for the same panel our device is using.
https://github.com/CarbonROM/androi...com/dsi-panel-sharp-dualmipi-1080p-120hz.dtsi
Not sure if there are any hope on getting 120Hz working on existing Oreo custom ROMs as SonyOpenDevices is now working on 4.9 kernel (which is used by Pie), and I'm yet to be able to build a working AOSP ROM for it. The last time I built an AOSP Pie ROM and flashed the generated images resulted in a lot of crashes and then the phone powered off by itself... it was completely unusable.
EDIT: It seems the value I previously changed was reflected in /sys/devices/mdss_dsi_panel/change_fps (which can be viewed via cat). As I set it to 90 in the dtsi, the value here is also 90.
raven213 said:
Any update on this lol went back to my xz premium
Click to expand...
Click to collapse
I haven't got round to modding the display on my kernel yet, I'm firstly trying to fix WiFi lol.
---------- Post added at 09:10 PM ---------- Previous post was at 08:56 PM ----------
LSS4181 said:
I've been thinking about how to get this working, but it seems tweaking the qcom,mdss-dsi-panel-framerate value on the default configuration (1080p) alone is not enough, although from an initial diff between the original 60Hz configuration and kholk's newly added 120Hz configuration on SonyOpenDevices kernel showed only the framerate value was changed (there are probably things I didn't find).
I've tried changing it from 60 to 90 and 120. Changing to 90 has no apparent effect (the system still renders at 60 FPS), while changing to 120 caused everything to be rendered at 24 FPS (very sluggish). Still, it seems the refresh rate change is indeed set to the value, as this app (which looked rather dated and unreliable) did show the system's refresh rate (rr) is configured to the value written in the dtsi.
From the looks of it, it seems the dtsi file controls what refresh rate be configured at kernel level, but something's probably needed in the userland to get it function properly. But still, it's interesting that setting the value to 120 would cause the system to render everything at 24 FPS, while setting the value to 90 doesn't have any impact.
I posted some details here yesterday as I was mainly building my own CarbonROM zips with some own configurations. For CarbonROM, the dtsi file is located in arch/arm/boot/dts/qcom/dsi-panel-maple.dtsi.
Back to the OP... I've found the entries as well. However, even after I modify the dsi-panel-maple.dtsi and that the modified value is registered somewhere, the value in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dsi_sharp_1080p_cmd is still 60 (003c). This file is probably the one representing the original 60Hz command:
https://github.com/CarbonROM/androi...boot/dts/qcom/dsi-panel-sharp-1080p-cmd.dtsi.
And there's the 120Hz configurations placed in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dual_sharp_1080p_120hz_cmd.
This file might be related to it. However, this file is significantly different from the 1080p (60Hz) one and I'm wondering if this is indeed for the same panel our device is using.
https://github.com/CarbonROM/androi...com/dsi-panel-sharp-dualmipi-1080p-120hz.dtsi
Not sure if there are any hope on getting 120Hz working on existing Oreo custom ROMs as SonyOpenDevices is now working on 4.9 kernel (which is used by Pie), and I'm yet to be able to build a working AOSP ROM for it. The last time I built an AOSP Pie ROM and flashed the generated images resulted in a lot of crashes and then the phone powered off by itself... it was completely unusable.
EDIT: It seems the value I previously changed was reflected in /sys/devices/mdss_dsi_panel/change_fps (which can be viewed via cat). As I set it to 90 in the dtsi, the value here is also 90.
Click to expand...
Click to collapse
Okay so I've been looking into this for quite some time and have even got a 90Hz Essential PH-1. But the thing is while we CAN force the display Hz, we aren't telling the display/graphics HAL to run at that frequency. So we need to find a way (or just find the way) to tell HAL to support by default this FPS. Razer clearly does this and that's why even on GSIs the display HAL in its /vendor position loads it up to normal.
Sony's SOMC kernel seems to have the display driver a bit wonky to the AOSP standards as you've seen. It seems this way for their method of HAL switching to 4K. Little OT tip: wm set doesn't change the resolution you see, only changes the resolution that's processed ?.
TL;DR it's pretty obvious (if you spend some time) to see the display references in the kernel where the Hz of the panel is displayed HOWEVER we need to rather focus on finding a way to force/tell the display/graphics HAL to process those 90 or 120 fps otherwise you'll have 60fps on your 120Hz panel .
There is the monitor (Hz) and the processed refresh rate (FPS) and one can usually get used the both being the same when using a desktop system however this is incorrect. They are 99% of the time aligned but it IS possible to have them not aligned (which is what happens when we're changing the kernel here).
LazerL0rd said:
Okay so I've been looking into this for quite some time and have even got a 90Hz Essential PH-1. But the thing is while we CAN force the display Hz, we aren't telling the display/graphics HAL to run at that frequency. So we need to find a way (or just find the way) to tell HAL to support by default this FPS. Razer clearly does this and that's why even on GSIs the display HAL in its /vendor position loads it up to normal.
Sony's SOMC kernel seems to have the display driver a bit wonky to the AOSP standards as you've seen. It seems this way for their method of HAL switching to 4K. Little OT tip: wm set doesn't change the resolution you see, only changes the resolution that's processed .
TL;DR it's pretty obvious (if you spend some time) to see the display references in the kernel where the Hz of the panel is displayed HOWEVER we need to rather focus on finding a way to force/tell the display/graphics HAL to process those 90 or 120 fps otherwise you'll have 60fps on your 120Hz panel .
There is the monitor (Hz) and the processed refresh rate (FPS) and one can usually get used the both being the same when using a desktop system however this is incorrect. They are 99% of the time aligned but it IS possible to have them not aligned (which is what happens when we're changing the kernel here).
Click to expand...
Click to collapse
So it seems we need to also alter the HAL to get the correct FPS. But the interesting phenomenon is, altering the kernel to use 120Hz, without touching any other code, triggers the HAL to render at 24 FPS instead of 60 FPS. This might be a hint on where we need to look at in the HAL code, if possible. I haven't tried other combinations, only 90 and 120, with the former having no impact (60 FPS).
As for you saying the SOMC kernel using a driver wonky to the AOSP standard might explain why it's been so complicated to get DRS (Dynamic Resolution Switching) to actually work despite the functionality's already been implemented in the SonyOpenDevices project (which is NOT what current CarbonROM is based on). Not sure about the functionality in AOSP now, but it's been non-working for quite a while (at least up to the point of switching to the 4.9 kernel as it wasn't complete on 4.4 kernel). At that time, the functionality itself existed, but it did nothing.
And as for the wm not changing the resolution we see... does it mean the panel is still outputting at 1080p even when instructed to change to 4K? If so, the "4K" is actually achieved via GPU scaling (which is also possible on desktop video cards, to attain a virtual 4K resolution on a 1080p-only monitor). This makes the 4K support claim fake, as it's not a real 4K resolution, but rather 4K rendered in background then downscaled to 1080p when outputting to the panel as the panel is operating at 1080p.
LSS4181 said:
So it seems we need to also alter the HAL to get the correct FPS. But the interesting phenomenon is, altering the kernel to use 120Hz, without touching any other code, triggers the HAL to render at 24 FPS instead of 60 FPS. This might be a hint on where we need to look at in the HAL code, if possible. I haven't tried other combinations, only 90 and 120, with the former having no impact (60 FPS).
As for you saying the SOMC kernel using a driver wonky to the AOSP standard might explain why it's been so complicated to get DRS (Dynamic Resolution Switching) to actually work despite the functionality's already been implemented in the SonyOpenDevices project (which is NOT what current CarbonROM is based on). Not sure about the functionality in AOSP now, but it's been non-working for quite a while (at least up to the point of switching to the 4.9 kernel as it wasn't complete on 4.4 kernel). At that time, the functionality itself existed, but it did nothing.
And as for the wm not changing the resolution we see... does it mean the panel is still outputting at 1080p even when instructed to change to 4K? If so, the "4K" is actually achieved via GPU scaling (which is also possible on desktop video cards, to attain a virtual 4K resolution on a 1080p-only monitor). This makes the 4K support claim fake, as it's not a real 4K resolution, but rather 4K rendered in background then downscaled to 1080p when outputting to the panel as the panel is operating at 1080p.
Click to expand...
Click to collapse
The 24 thing seems more like a glitch to me, personally. Since Android was never designed to support high refresh rates. Maybe in Android Q, hey?
By wonky I meant they use a different.. unusual method of seemingly having a display for each resolution (and one for 120hz) which are switched between or something like that. An interesting fact is if you're watching 4k and screenshot you get a black screen. I've noticed Windows 10 doing a similar thing in their recent closed Insider beta.
Yes the panel outputs 1080p even with a 4k resolution as the window manager (wm) only controls how much it processes not the output, without the HALs allowance. Yupp is 4k rendered them down to 1080p and breaks screenshots. You can easily tell by looking at a 4k picture in any app and then album with the stock wm.
Is 120Hz still being worked on? its been nearly a year since it was discovered and i thought it would be working by the end of the year at least. coming from the XZ
XxperexX said:
Is 120Hz still being worked on? its been nearly a year since it was discovered and i thought it would be working by the end of the year at least. coming from the XZ
Click to expand...
Click to collapse
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
LazerL0rd said:
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
Click to expand...
Click to collapse
I follow your project[emoji6]
Envoyé de mon G8141 en utilisant Tapatalk
LazerL0rd said:
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
Click to expand...
Click to collapse
im running omni 8.1.0 custom rom on my XZ and it has the toggle for it, but it doesnt work i understand that u probs only work on the XZP, but at least work is being done on it
Any new updates? or is it still WiP?
LazerL0rd said:
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
Click to expand...
Click to collapse
Which roms?
razerphynx said:
Which roms?
Click to expand...
Click to collapse
Idk but it's been available to all SODP for some time.