There are time when people get screen flicker problems when flashing a new ROM. This either has to do with the ROM itself, for the kernel. Until full support is givien, I have a temporary fix. This fix is basically disabling HW overlay, but disabling HW overlay in the settings does not stick on reboot and this has been really annoying.
For those who want to know what Disabling HW overlay is, it is basically making the phone's gpu render the graphics instead of the cpu. This allows for better graphical rendering of everything. This is not a proven statement, but theoretically, disabling HW overlay, may increase battery consumption... not by much though.
Finally, I am not responsible for anything that goes wrong with your phone when using my method. Please don't whine that it did not work or I messed your phone up. You are doing this at your own risk!!
My fix
Step 1 - Download a build.prop editor app from the play store (I recommend JRummy's one) and run the app. MAKE A BACKUP OF ORIGINAL build.prop!!
Step 2 - Locate these four lines
a) debug.mdpcomp.maxlayer
b) debug.composition.type
c) dev.pm.dyn_samplingrate or dev.pm.cpu_samplingrate (you may not find these values; however, if you do, change the "dyn" or "cpu" to gpu) --> dev.pm.gpu_samplingrate
**If you cannot find this value add "dev.pm.gpu_samplingrate"
d) debug.sf.hw
e) debug.egl.hw
Step 3 - Edit the values of each one
a) debug.mdpcomp.maxlayer = 0 or 1 or 2 --> READ EDIT BELOW
EDIT* --> This value can be either 0 or 1 or 2. I put mine on 0 right now and I feel like I'm getting better performance. Before, I put it at 1 or 2; so, you can try it with 2 first.
b) debug.composition.type = gpu
c) dev.pm.gpu_samplingrate = 1
d) debug.sf.hw = 1
e) debug.egl.hw = 1
f ) If you are running CM10, go to setting --> performance --> surface improvement --> disable dithering (AOKP has no option for this)
Make sure to save after each edit. The saved edit will not appear changed until you reboot your device.
After rebooting, make sure to see the changed values.
Thanks to everyone who has given me info of their device. Thanks to davietr for his input on including the "dev.pm.gpu_samplingrate" value
If this helped and work, Thanks would be appreciated.
EDIT **If it's not too much of a hassle and my fix methods worked for you, please post what ROM/Kernel you are using on this page to help others!!**
Can't thank posts yet, so I'll thank you this way, Thanks! This worked for me!
Sazex said:
Can't thank posts yet, so I'll thank you this way, Thanks! This worked for me!
Click to expand...
Click to collapse
Great! I hope it can work for other people on different cm10 mods! What ROM/Kernel are you on?
Running AOKP 21st build. No flicker with stock kernel. Had flicker using instigatorx kernel. Installed Instigatorx 6.3.6 changed build.prop setting to the ones you provided (maxlayer set to "1"). No more flicker. Great work and thank you.
davietr said:
Running AOKP 21st build. No flicker with stock kernel. Had flicker using instigatorx kernel. Installed Instigatorx 6.3.6 changed build.prop setting to the ones you provided (maxlayer set to "1"). No more flicker. Great work and thank you.
Click to expand...
Click to collapse
That's great! I'm glad this method is working with the other Instigator's Kernel. Where did you get the 21st build from? I know R4INS left Skyrocket and his AOKP build for the skyrocket stopped at 9th. I loved the stability of the rom, but I had to leave it for Vincom's CM10 because of the call volume of the AOKP rom was so low.
jee'sgalaxy said:
That's great! I'm glad this method is working with the other Instigator's Kernel. Where did you get the 21st build from? I know R4INS left Skyrocket and his AOKP build for the skyrocket stopped at 9th. I loved the stability of the rom, but I had to leave it for Vincom's CM10 because of the call volume of the AOKP rom was so low.
Click to expand...
Click to collapse
http://rootzwiki.com/topic/34092-aokp-unofficial-galaxy-s-ii-skyrocket-i727-sept-21-jb-build-2/. I have no problem with in call volume on this build.
jee'sgalaxy said:
Great! I hope it can work for other people on different cm10 mods! What ROM/Kernel are you on?
Click to expand...
Click to collapse
I'm on vincom's superlite v4 with the 6.3.6 instigator kernel
I'm using sean's method for my phone (vincom v4 and X 6.3.4) and it works great too, anyone can explain what is different?
Sean's method: - debug.mdpcomp.maxlayer = 0
- disable dithering in performance setting
View attachment 1360158All I did was edit the line "debug.mdpcomp.maxlayer=2" to read "debug.mdpcomp.maxlayer=1". Thank you. This got rid of the flicker I was seeing in Poweramp. Here's a shot of what I am running.
Hello,
I have done some testing that I think you might find some of my results interesting.
I applied your build.prop setting and they did get rid of the home screen and gallery flicker problems for me. But, I was still seeing stuttering while playing videos and those problems were amplified playing a video while connected to tv with mhl/hdmi. Which of course this bothered me.
It make me think of the build.prop. Then I remembered something.
A change was made to: debug.composition.type...from dyn to cpu or gpu.
if you look a little further down in the build.prop list you will find an entry for "dev.pm.dyn_samplingrate" with value set to "1"
So, when the debug.composition.type was "dyn" it had a sampling rate. But when the debug.composition.type is changed to "cpu" or "gpu" it isn't assigned a sampling rate.
Needless to say I decided to give them a sampling rate. I added and used both "dev.pm.cpu_samplingrate" and "dev.pm.gpu_samplingrate" with values of "1" and "2" for each.
Results. Video playback is stutter free on device and when plugged into tv thru mhl/hdmi the stutter and flicker where completely gone. Also, I swear the graphic speed is lightning fast and apps open faster. I really do believe it has improved the over all graphics speed on the device. Test for yourself and see what you think.
My best result were
debug.composition.type=gpu
debug.egl.hw=1
debug.mdpcomp.maxlayer=0
debug.sf.hw=1
add
"dev.pm.gpu_samplingrate=1"
Edit: forgot to mention. I am running R4INS AOKP Sept 26Th build with stock kernel. No performance changes. No ability to disable dithering.
davietr said:
Hello,
I have done some testing that I think you might find some of my results interesting.
I applied your build.prop setting and they did get rid of the home screen and gallery flicker problems for me. But, I was still seeing stuttering while playing videos and those problems were amplified playing a video while connected to tv with mhl/hdmi. Which of course this bothered me.
It make me think of the build.prop. Then I remembered something.
A change was made to: debug.composition.type...from dyn to cpu or gpu.
if you look a little further down in the build.prop list you will find an entry for "dev.pm.dyn_samplingrate" with value set to "1"
So, when the debug.composition.type was "dyn" it had a sampling rate. But when the debug.composition.type is changed to "cpu" or "gpu" it isn't assigned a sampling rate.
Needless to say I decided to give them a sampling rate. I added and used both "dev.pm.cpu_samplingrate" and "dev.pm.gpu_samplingrate" with values of "1" and "2" for each.
Results. Video playback is stutter free on device and when plugged into tv thru mhl/hdmi the stutter and flicker where completely gone. Also, I swear the graphic speed is lightning fast and apps open faster. I really do believe it has improved the over all graphics speed on the device. Test for yourself and see what you think.
My best result were
debug.composition.type=gpu
debug.egl.hw=1
debug.mdpcomp.maxlayer=0
debug.sf.hw=1
add
"dev.pm.gpu_samplingrate=1"
Edit: forgot to mention. I am running R4INS AOKP Sept 26Th build with stock kernel. No performance changes. No ability to disable dithering.
Click to expand...
Click to collapse
Hey Thanks a lot for the info! I add that on!
Worked like a champ on ParanoidAndroid 2.+ with the InstigaterX 6.3.6 Kernel.
Is it possible to make this into a flashable zip please!
Sent from my SGH-T989 using xda premium
This is great, thanks!
LoopDoGG79 said:
Is it possible to make this into a flashable zip please!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Hey, I was thinking about doing this, but I only have one phone and i dont want to change ANYTHING!!! right now because it's perfect for me. However, the problem with flashing a build.prop is that the build.prop for AOKP, Paranoid Android, and CM10 are all different based on who built it. This means I would have to make a flashable build.prop for all three ROMs. In addition, build.prop also includes information from build number to build date, to what ringtones you are using. So instead of risking errors, I decided that it was best to edit it through the app.
If you have any ideas or brainstorm, definitely message me! :good::good::good:
Hey man thank you so much, the flickering was getting so annoying. I read somewhere that they were not getting SOD or RR with this kernel but when it started flickering I was disoriented but not anymore, thanks to you.
I have T-Mo SGS2 using CM10 Erickwill's rom 10/04 with instigatorx Kernel.
Thanks! Quick 5 seconds to fix!
Sent from my SAMSUNG-SGH-T989 using xda premium
rcanela1 said:
Hey man thank you so much, the flickering was getting so annoying. I read somewhere that they were not getting SOD or RR with this kernel but when it started flickering I was disoriented but not anymore, thanks to you.
I have T-Mo SGS2 using CM10 Erickwill's rom 10/04 with instigatorx Kernel.
Click to expand...
Click to collapse
This is great information that it works on T-Mobile GS2!
I should've known to just check the build.prop, but props to you for figuring out what works... pun intended
If i remember correctly Topprospect the official CM10 maintainer mentioned that this is NOT a fix.....its just the same as disabling HW overlays in the settings.
Sent from my SGH-I727 using xda app-developers app
Related
Hello All,
I am not de developer of this app, but I find it very usefull and wanted to share it. Its called SpareParts and people that have had previous android phones are probably familiar with it.
However, I never found it in any Xperia X10 rom, and everytime I tried to install one from the internet, it just wouldn't work, or didn't include some of the most interesting settings of this app.
Basically SpareParts is a system tweaker, and lets you change a variety of settings which makes it a very handy tool.
I recently found one which included Compcache and CPU settings that worked fine on my X10.
For those who don't know, enabling compcache allows android to compress RAM and results in overall better performance.
It also has working CPU settings (As you may know, most CPU control apps available are unreliable with the X10).
In my case, I used to have ramdom reboot problems , specially when I was heavy using the phone (ie, playing asphalt and streaming music at the same time) and after enabling compache with this app the issue went away.
Also, it allows you to lower the CPU speed without affecting the phone performance too much, so it definitively helps to save a lot of battery.
Anyone willing in to give it a try, here is the link, i suggest setting Swapines to 15 after enabling compache:
http://dl.dropbox.com/u/7864538/SpareParts-4.apk
The phone seems to be more smooth, but may be a placebo effect.
Please give it a try and share your results.
BTW I am using CM 6.1.1 ROM Tweaked and with extras with custom Sysctl settings posted in this thread:
http://forum.xda-developers.com/showthread.php?t=929448
PS.
You may also want to try changing the animation speed to fast (under original spareparts settings). The phone will feel a lot faster
(if you fin this post helpful please don't forget to click the thanks button)
Hmmm interesting, but I can't seem to use it to turn off some of the status bar stuff.
Running FreeX10 with .54 bb
cordam said:
Hmmm interesting, but I can't seem to use it to turn off some of the status bar stuff.
Running FreeX10 with .54 bb
Click to expand...
Click to collapse
Some of the settings will not work. Maybe a dev can mod the app and just leave the working settings. This version of the app was modded for another device.
I'm on wolfbreak's cm v 4.4 and this definitely made the phone.snappier...
I had to uninstall the original spare parts before installing this one or the compcache setting wouldn't stay after a reboot.
Thanks for this!
would not be fully functional since we are not allowed custom kernals
Sweet!
Thank you! This does have a lot more capabilities than the regular spare parts!!! Will tweek it and give feed back!!!
Best regards,
Chris
fiscidtox said:
I'm on wolfbreak's cm v 4.4 and this definitely made the phone.snappier...
I had to uninstall the original spare parts before installing this one or the compcache setting wouldn't stay after a reboot.
Thanks for this!
Click to expand...
Click to collapse
I'm happy that its working for you. don't forget to click the thanks button .
aR_ChRiS said:
would not be fully functional since we are not allowed custom kernals
Click to expand...
Click to collapse
I see you are using 2.1 ROM. I am not sure if it will work in 2.1. I only tested it in 2.2. However, some of the settings are specific for the device this app was originally made for so they won't work for us (ie the status bar tweaks).
cordam said:
Hmmm interesting, but I can't seem to use it to turn off some of the status bar stuff.
Running FreeX10 with .54 bb
Click to expand...
Click to collapse
If you want to change the status bar options you can use CM settings.
Hey, I just installed this version of spare parts and now my phone doesnt go to sleep when I press the power button. I have reverted back to original compache settings and default 60 swapines, rebooted and uninstalled. Please help
Aphex33 said:
Hey, I just installed this version of spare parts and now my phone doesnt go to sleep when I press the power button. I have reverted back to original compache settings and default 60 swapines, rebooted and uninstalled. Please help
Click to expand...
Click to collapse
Nevermind, issue resolved.
Defintion swapines please?
Aphex33 said:
Defintion swapines please?
Click to expand...
Click to collapse
You can find a good one in wikipedia.
Sent from my X10i using XDA App
Do i have to manually install this? Because it didnt work the regular way ;o
Sent from my X10i using XDA Premium App
Which ROM are you running?
shahkam said:
Do i have to manually install this? Because it didnt work the regular way ;o
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
Portland ed from x10 brick
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. The tab will not show up if your kernel does not have these features. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the voltage adjustment that the kernel you are using has either the HAVS or SVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
maybe is good thing to post which kernel for desire s can use this.many users have no idea what kernel supports HAVS or SVS voltage adjustment..its just few of them actualy so u can maybe check and let us know.
Tiamat 1.0.4 does. I don't see any other recent ones listed on the forum here. If you give me a link to other kernels I'll check for you. No stock kernel does (this includes the default cm7 kernel).
check virtuous rom
kernel is unity v2 ...i think.
Adidas108 said:
check virtuous rom
kernel is unity v2 ...i think.
Click to expand...
Click to collapse
It appears that that kernel does not support the interface. If you're willing to test for me, I can pull the source for that kernel, implement the interface and submit a patch to the developer for inclusion. Just let me know if you would be willing to test for me.
EDIT: I got bored, so here:
http://chad0989.dyndns.org/mirror/unitykernel_sysfs.zip
Let me know if it works, make sure you have another kernel downloaded that you can flash in the event that this one doesn't boot.
tried the kernel. works a treat. thanks!
Sent from my HTC Desire S using XDA Premium App
lowered all the voltages twice. tried three times and it crashed. stable on lowering twice. haven't experimented with each of them individually though
Sent from my HTC Desire S using XDA Premium App
dan-fish said:
lowered all the voltages twice. tried three times and it crashed. stable on lowering twice. haven't experimented with each of them individually though
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
It takes a lot of trial and error to get the best voltage table. It would be great if when you get a pretty good one, you could post it here so that others may use it as a starting point.
mind making the tiamat kernal works too?
tcchuin said:
mind making the tiamat kernal works too?
Click to expand...
Click to collapse
Tiamat 1.0.4 should work with it already.
IncrediControl v1.3
Major changes include:
Ad Free has now been turned into a key that removes the ads from the free version. This allows donors who have downloaded the ad free version from the site to update through the market.
HAVS voltage checking. Minimum voltages can no longer be set higher than maximum voltages.
Boot voltages are now stored in the application’s data directory. Boot settings will now persist if you update your ROM or restore the application and data from a backup.
si, is this a replacement for SetCPU? What other features does it have?
shrome99 said:
si, is this a replacement for SetCPU? What other features does it have?
Click to expand...
Click to collapse
It's not a replacement for set cpu at the moment. But in the future I'm adding CPU speed and governor control. As well as the ability to fine tune each governor.
Sent from my ADR6300 using XDA App
Can someone post a screenshot of their HTC Incredible voltage table?
Also, does this app obsolete the USB fast charge boot script? (http://www.incredikernel.com/wp-con...-monitor/download.php?id=enablefastcharge.zip) i.e. Should I delete that script after installing this app and enabling the USB check box in the general tab?
2 more: What does audio boost do? Why are the "enable on boot" checkboxes reset to unchecked each time the app is opened?
slapmeaty said:
Can someone post a screenshot of their HTC Incredible voltage table?
Also, does this app obsolete the USB fast charge boot script? (http://www.incredikernel.com/wp-con...-monitor/download.php?id=enablefastcharge.zip) i.e. Should I delete that script after installing this app and enabling the USB check box in the general tab?
Click to expand...
Click to collapse
Might be better off posting in the incredible thread next time, so we can keep this one desire discussion. But yes, you no longer need that script and are safe to delete it.
Audio boost is louder in call volume.
The check boxes uncheck themselves as a fail safe for users. I know a lot of users will leave it checked and then adjust voltages too low and end up in boot loops. This way if someone is playing with voltages, they aren't set on boot unless they explicitly click the set on boot box and click apply. If you have previously set on boot voltages, those will remain until you check the box again and click apply, then the previously set on boot voltages will be overwritten with the new ones. In the general tab, the box unchecks itself also just to be consistent with the behavior in the voltage adjustment tab.
Thx. (Apologies for wrong forum - tapatalk ui hides a lot of info)
Sent from my ADR6300 using Tapatalk
IncrediControl v1.4:
This is mostly a bug fix release but I have also added:
Automatic detection of the minimum and maximum voltages supported by your kernel
Unless any more bugs arise, the next release will have some new goodies to play with...
http://www.incredikernel.com or from the market.
very interesting thing.
Does some made any test how much it affect battery life, is it worth of playing ?
Ok so i installed this but i can only see the SVS tab. No general tab. Why is that?
Oh nvm finally understood the first post.
If you are running Absolution 3, please do not flash any themes or batteries until an update for the theme and battery is released. The framework has changed and you will bootloop if you do.
If any of you want to talk to the team, we are using an app called Palringo. Just add theandroidcollective as a group. We look forward to hearing from you.
Thank you for trying Absolution. If you have any questions, concerns, suggestions, complaints, etc. please post them here and not in the Development thread. One of the team members will be glad to help you.
We only have two rules. Please do a simple search for your question in the FAQ section below or in this thread before posting your question. Chances are good, the question has already been asked and answered. Also, when you ask a question, please make sure you are as specific as possible so we can pinpoint the problem. We thank you ahead of time for your cooperation.
You may find Absolution at: http://forum.xda-developers.com/showthread.php?t=1304056
Please make sure you read the third post in this thread. Thank you.
If you are running Absolution 3, please do not flash any themes or batteries until an update for the theme and battery is released. The framework has changed and you will bootloop if you do.
*Absolution 3.3 Important Information*​
What is what in AbsolutionTools you ask?
1. Custom OC Profiles:
Sloth - Sleep = conservative 192/345 + Wake = interactive 192/883
flappjaxxx - Sleep = conservative 192/345 + Wake = ondemandX 192/1113
rasroy - Sleep = conservative 192/345 + Wake = ondemandX 192/1344
Nun - Sleep = conservative 268/345 + Wake = ondemand 268/1190
Lone Star - Sleep = conservative 192/192 + Wake = interactive 268/1267
Dumbass - Sleep = conservative 192/345 + Wake = lagfree 192/1420
2. GPS Configs are by crypted and they are all version 2.2 except for Worldwide 1.3 which may be better for some than 2.2 that is why I included it. Make sure to be patient if coming from a clean install when trying to get your first lock. It may take quite some time as it downloads assistance data. I don't think I need to say this but you should not be in a house or a building trying to get a lock as this will severely degrade signal.
3. At the moment 1:30pm EST when you Update AbsolutionTools it will reset any custom OC/UV custom profiles. I will push out a fix for this today some time. But if your profile gets nuked just set it again. Takes a whole 2 seconds. I did this on purpose for a reason. To ready people's devices for the profiles in Tools 5.0 that may not have had andrev_oc installed.
4. If you are using OC/UV Beater Please uninstall it as it will conflict with the current settings you are using if you use custom OC profiles. I will be posting a fix for this later today too.
5. Undervolting is seriously not recommended on this version of Absolution. Your battery life will be as good as it is going to get. Default frequencies are lower than stock CM7 kernel out of the box. If you insist on using undervolting use the included Absolution Undervolt because so far it is the only amount of undervolting that is fairly stable.
6. Ad Blocking Apps such as Ad-Away are no longer needed as AbsolutionTools takes care of this now and it uses the lists as Ad-Away.
7. If you do the One Touch Google Apps Installer from tools YOU MUST Reboot after install or you will in fact get Force Closes. I included the most standard Google Apps to get most users up and running but not all of them. After using the installer Reboot, Open Market and Search Google and it will show you which ones are now installed and which ones aren't.
8. If you are having Compatibility issues with apps in the Market after changing screen resolution in Tools, Go to Homescreen> Settings> Applications> Manage Applications then Find Market and Clear Data then reboot and you should be good to go.
PLEASE READ THIS:
Before you make any changes on your phone, make sure you know what you are doing first. That means, read first, read some more, and continue reading until you are comfortable with making whatever change you want. To not do so is only asking for trouble. With that, The Collective is not responsible for any damage you may cause your phone. If you destroy your phone, brick it or do anything that causes it not to work properly, it is your own doing.
If you are running Absolution 3, please do not flash any themes or batteries until an update for the theme and battery is released. The framework has changed and you will bootloop if you do.
FAQ
1) If you find that your voicemail number is not set or incorrect, please see the following: http://bridog.net/cellular/voicemail-access-numbers/
2) If you find the Market doesn't work correctly after flashing, including FCs and downloading issues, do a restart.
3) If Gmail doesn't sync, go to Settings, Accounts & sync, tap on your account, turn off Sync Gmail then turn it back on.
4) Front Facing Camera hack tells video chat apps that your device is equipped with a front facing camera, then uses the camera on the back. Grab a mirror and enjoy!
5) To set device phone number, go to Settings>Call Settings>Additional Settings>My Phone Number
6) If you have issues using Flash, try this: Using ES File Explorer or the like, navigate to /data/data/com.android.browser/flash player and long press the item scroll down and remove permissions
Try embedded video again.
Question....:-D
I got your 10 char right here
So far so good will setcpu interfere with the oc/uv beater?
passtheknowledge said:
So far so good will setcpu interfere with the oc/uv beater?
Click to expand...
Click to collapse
I'm not 100%sure but I think yes. I'm using the oc /uv beater and having great success. Even uv to -100! Oc to 1.4
Sent from my Inspire 4G using Tapatalk
passtheknowledge said:
So far so good will setcpu interfere with the oc/uv beater?
Click to expand...
Click to collapse
You need to pick one app to mess with oc/uv. If not, the two will compete with each other which will only cause potential problems.
Thanks for the info only reason i ask is because i don't see oc/uv beater having an option to set a profile for screen off (like setcpu).
Maybe its there if not any help?
passtheknowledge said:
Thanks for the info only reason i ask is because i don't see oc/uv beater having an option to set a profile for screen off (like setcpu).
Maybe its there if not any help?
Click to expand...
Click to collapse
It does not have a screen off profile, but I think you will find that the kernel does a great job. If you use setcpu, just don't use OC/UVBeater. I perfer OC/UVBeater because it allows for undervolting from the app. Really convenient...
is there a way to turn off the animations that occur when going through the menu/settings?
---------- Post added at 12:52 PM ---------- Previous post was at 12:45 PM ----------
roderjay said:
is there a way to turn off the animations that occur when going through the menu/settings?
Click to expand...
Click to collapse
nm, just found it.
passtheknowledge said:
Thanks for the info only reason i ask is because i don't see oc/uv beater having an option to set a profile for screen off (like setcpu).
Maybe its there if not any help?
Click to expand...
Click to collapse
You don't really need a screen-off profile to save battery, (if that's why you're using it in the first place, I should say), so just having an option for a single profile state is really all you need. With your screen off, your phone should be spending a good amount of time in "Deep Sleep" mode, (grab the "CPU Spy" app from the Market which will show you how much time your phone is spending in each clock cycle available for your governor). The Devs (especially these guys ) have customized these ROMs to run extremely efficiently while sipping the battery, thus a single profile fits the bill nicely.
roderjay said:
is there a way to turn off the animations that occur when going through the menu/settings?
---------- Post added at 12:52 PM ---------- Previous post was at 12:45 PM ----------
nm, just found it.
Click to expand...
Click to collapse
Feel free to share the answer to your own questions here when you figure something out yourself... You never know when it might help another user! Welcome!
rasroygbiv said:
Feel free to share the answer to your own questions here when you figure something out yourself... You never know when it might help another user! Welcome!
Click to expand...
Click to collapse
+1 on that. Sharing is caring and knowledge is power...ok back to beer time.
I got your 10 char right here
Themes
Thinking on switching to this rom, but I would like to know if there is anyway to change the themes. Do the phoenix theme work?
Otreblada said:
Thinking on switching to this rom, but I would like to know if there is anyway to change the themes. Do the phoenix theme work?
Click to expand...
Click to collapse
Theme Chooser themes are always an option. DO NOT use a theme that was made for a different ROM, or we are not resposible. LOL. But keep an eye out, this team is known for some great theming work. Lots of extras coming in the update later tonight!
7 minutes to answer. Whao! Have not seen a support like this since Symonc was running the MIUI forum. Thanks
Otreblada said:
7 minutes to answer. Whao! Have not seen a support like this since Symonc was running the MIUI forum. Thanks
Click to expand...
Click to collapse
We are here to help. Plus that's the advantage of having a ROM that is supported by a team like ours. However, keep in mind we won't always be able to answer in 7 minutes or so, but we will certainly do the best we can. Thanks for trying out Absolution!!
gio22 said:
We are here to help. Plus that's the advantage of having a ROM that is supported by a team like ours. However, keep in mind we won't always be able to answer in 7 minutes or so, but we will certainly do the best we can. Thanks for trying out Absolution!!
Click to expand...
Click to collapse
+1!! We here at the collective will do everything we can to provide the quickest and best answers that we can!
I got your 10 char right here
Otreblada said:
7 minutes to answer. Whao! Have not seen a support like this since Symonc was running the MIUI forum. Thanks
Click to expand...
Click to collapse
We try our very best. Thanks and welcome!
Sent from my Inspire 4G
hi
as you know cm10&10.1 has a bad bug which cause fps lock.. after turning the phone on, it's really smooth as butter..!
but after locking and unlocking the screen, All animations loss their smoothness.. (you must be strict to notice that..!)
i found a way to solve it..it was solved in peach beta kernel for cm10.1.. (but unfortunately not in new vibra version)
here is beta version
it's weird but i don't know why i've problem with sd card in this kernel.. sometimes i must remount sd card to use camera
and gallery..
and unfortunately i couldn't finde any kernel for cm10 which doesn't have fps problem..
is there any way to fix this bug?
EDIT:
i found 2 kernels for cm10 & cm10.1.. they can solve fps problem instead of loosing vibration..!
it seems dear Devs don't have enough time to spend on it and make a kernel which solves that bug and has vibration
Cm10 kernel
Cm10.1 kernel
I have no FPS bug here - using CM10 nightly, and iodak kernel - I modded the crap outta the firmware itself - I removed Android's own graphic CPU rendering driver from egl folder and modified the egl.cfg file, finally added the GPU acceleration lines in build.prop. The only time it gets slow is because of two things; not so great CPU scheduling and RAM being run down (that I wish O3D have 1 GB RAM - both GPU and CPU eat lot more memory than what LG would like to think....)
First make a backup copy of your firmware and user data before trying the following;
1. Go to /system/lib/egl and remove libGLES_android.so and edit egl.cfg file and remove the line "0 0 android" and then save it - change permission to read-only - rw- r- r- or r- r- r-
2. And then go to /system/ then edit build.prop and add few lines; "debug.sf.hw=1", "video.accelerate.hw=1" and "debug.performance.tuning=1" and save then fix permission. Reboot. If it bootloops, go to CWM recovery and clear both cache and dalvik cache, then reboot.
Sent from my LG-P920 using XDA
Dr. Mario said:
I have no FPS bug here - using CM10 nightly, and iodak kernel - I modded the crap outta the firmware itself - I removed Android's own graphic CPU rendering driver from egl folder and modified the egl.cfg file, finally added the GPU acceleration lines in build.prop. The only time it gets slow is because of two things; not so great CPU scheduling and RAM being run down (that I wish O3D have 1 GB RAM - both GPU and CPU eat lot more memory than what LG would like to think....)
First make a backup copy of your firmware and user data before trying the following;
1. Go to /system/lib/egl and remove libGLES_android.so and edit egl.cfg file and remove the line "0 0 android" and then save it - change permission to read-only - rw- r- r- or r- r- r-
2. And then go to /system/ then edit build.prop and add few lines; "debug.sf.hw=1", "video.accelerate.hw=1" and "debug.performance.tuning=1" and save then fix permission. Reboot. If it bootloops, go to CWM recovery and clear both cache and dalvik cache, then reboot.
Sent from my LG-P920 using XDA
Click to expand...
Click to collapse
Nope your method doesn't work. It only enables GPU rendering in 2d apps. If you run a benchmark test, you can see that it is still locked at 45.95 fps
Sent from my 3D phone.
It works for both 2D and 3D. That's what GPU acceleration is for. -____- Look around in build.prop and other tweaks carefully. Also, try disable VSync in trickmod app. Mine's pretty smooth with the method I posted.
Sent from my LG-P920 using XDA
Dr. Mario said:
It works for both 2D and 3D. That's what GPU acceleration is for. -____- Look around in build.prop and other tweaks carefully. Also, try disable VSync in trickmod app. Mine's pretty smooth with the method I posted.
Sent from my LG-P920 using XDA
Click to expand...
Click to collapse
yeah but have you checked with benchmark 3d tests? You are maybe experiencing placebo
Sent from my 3D phone.
It doesn't matter - benchmark's useless. What's going on with the original setting is that GUI was rendered by CPU in the first place. Thus you are experiencing GUI lag. Simple as that.
P. S. Look around XDA for tutorial and some proofs why benchmark apps are useless. I know I am not experiencing placebo effect and am not on any of drugs - it have been fast for me unless I load some compute-intensive apps.
Sent from my LG-P920 using XDA
Dr. Mario said:
It doesn't matter - benchmark's useless. What's going on with the original setting is that GUI was rendered by CPU in the first place. Thus you are experiencing GUI lag. Simple as that.
Sent from my LG-P920 using XDA
Click to expand...
Click to collapse
I don't think you know what the problem is. Its not lag from the CPU that is our problem. It is that after you lock the screen and unlock it again the FPS (frames per second) gets stuck at 45.95. That means it can't go higher than that. Doesn't matter if the GPU is rendering. On other ROMs the fps shoots up to 95
Sent from my 3D phone.
I am done here. Research. Read and you will find your answers.
Also, look in logcat and save the log, you will help the developers find the source of bug.
Sent from my LG-P920 using XDA
Dr. Mario said:
I have no FPS bug here - using CM10 nightly, and iodak kernel - I modded the crap outta the firmware itself - I removed Android's own graphic CPU rendering driver from egl folder and modified the egl.cfg file, finally added the GPU acceleration lines in build.prop. The only time it gets slow is because of two things; not so great CPU scheduling and RAM being run down (that I wish O3D have 1 GB RAM - both GPU and CPU eat lot more memory than what LG would like to think....)
First make a backup copy of your firmware and user data before trying the following;
1. Go to /system/lib/egl and remove libGLES_android.so and edit egl.cfg file and remove the line "0 0 android" and then save it - change permission to read-only - rw- r- r- or r- r- r-
2. And then go to /system/ then edit build.prop and add few lines; "debug.sf.hw=1", "video.accelerate.hw=1" and "debug.performance.tuning=1" and save then fix permission. Reboot. If it bootloops, go to CWM recovery and clear both cache and dalvik cache, then reboot.
Sent from my LG-P920 using XDA
Click to expand...
Click to collapse
thanks for your help but unfortunately it didn't help me
it's pretty smooth but not as first boot.. i can notice difference before and after unlocking the screen..
Hm. I didn't see too much difference. What lock method did you use - slider or face lock and importantly what firmware did you use - CM10 or 10.1?
I was in bad mood, but okay now though.
Sent from my LG-P920 using XDA
---------- Post added at 05:29 AM ---------- Previous post was at 05:15 AM ----------
Few more questions though; Regarding FPS lock, when it occurs, did it locks "semipermanently" or just spontaneously when it occurs?
To answer some irrevelant question (or revelant ones depending on the point of view), I am running CM10 Nightly - March 18, 2013 straight from cyanogenmod.org so I am not sure if FPS bug is fixed in my package or not. I may have to get better logcat which records a bit longer because some bugs are pretty sneaky.
Sent from my LG-P920 using XDA
Here you can see what I mean. You see the fps count in the lower right corner? It cant go higher than that throughout the test
Edit: lower LEFT. Hehe
Sent from my 3D phone.
Alright, I will install shader-heavy app (just so I can exercise the GPU), and view the live Logcat (via Android Commander).
EDIT: I downloaded standard edition of Quadrant - lemme tell you, I did acquire better result, the highest was 70 fps and I might have lost track of hack I did to make it scream. Now I will need to find a way to make it very unhappy so I can reproduce the similar result BUT at least one OpenCL object, DNA rendering did similar thing, pegged at 49 - 50 fps while it obviously should go over that (SGX540 have four superscalar shaders inside).
Will post Quadrant result in a bit - XDA app's uncooperative.
Sent from my LG-P920 using XDA
You can compare your Quadrant result with mine. And please tell me your CPU governor and IO manager as well as type of screen lock so I can try reproduce the issues.
Sent from my LG-P920 using XDA
lzzar, what benchmark did you use? I would like to impose similar conditions so I can trace it to a package and then find out why.
Sent from my LG-P920 using XDA
well.. luckily i tried some kernels and at last one of them solved the fps problem completely..!
it's one of Pesach85's kernels.. (i don't know it was which one..) if someone needs it, i can upload it..
Good. :thumbup:
Sent from my LG-P920 using XDA
Dr. Mario said:
lzzar, what benchmark did you use? I would like to impose similar conditions so I can trace it to a package and then find out why.
Sent from my LG-P920 using XDA
Click to expand...
Click to collapse
Antutu.
Sent from my 3D phone.
I see - will try this even though Dark Fear found the workaround already.
Sent from my LG-P920 using XDA
Dark Fear said:
well.. luckily i tried some kernels and at last one of them solved the fps problem completely..!
it's one of Pesach85's kernels.. (i don't know it was which one..) if someone needs it, i can upload it..
Click to expand...
Click to collapse
can you upload it ? I really need it , but can I use it to boot to secondary rom ? as I installed my cm10.1 as secondary rom
Dark Fear said:
well.. luckily i tried some kernels and at last one of them solved the fps problem completely..!
it's one of Pesach85's kernels.. (i don't know it was which one..) if someone needs it, i can upload it..
Click to expand...
Click to collapse
Which kernel was it? :what: you started this thread to fix the issue then you solve it and leave everyone hanging.
Sent from my LG-P920 using xda app-developers app
Some of you may not notice, but I'm sure there are a few that do. Touch screen responsiveness on custom ROMs or GSI's for Mata is working, but is definitely not as fluid as stock.
Easiest way to tell is just typing on the keyboard and taking note of the shot delay in between touches. For me, I type fast, and this causes spelling mistakes often, because the touch screen (on a ROM or GSI.) doesn't register as it does on stock.
Next is mobile gaming. Touch seems to be a total hit and miss here, and sometimes won't work at all unless one finger is already on the screen. That's not a big deal, because a simple reboot fixes this temporarily. This was fixed a while ago here, if I recall correctly:
https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/198809
Overall I am hoping to find a fix for this touch responsiveness issue. It effects a ton of aspects of this phone and prevents me from staying on ROMs, and resorting to restoring backups to use my phone properly again.
I've tried messing with the build.prop, switching kernels, checked out various forums and attempted things I probably shouldn't have tweaked with, but still have had no luck figuring this out on ROMs or GSI's. Yet on Stock everything functions properly, and touch is no issue.
Can anyone shed any light on this at all? (To clarify there are 2 issues here: general delay in touch, and touch screen not working after a while on games.)
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
lovelock8353 said:
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
Click to expand...
Click to collapse
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
MoistPicklez said:
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
Click to expand...
Click to collapse
Yes,I rooted it. I just checked idc folder of my stock room restore, there are no more but 1 less idc file in the stock rom. I copied the entire idc folder to main storage, restored the gsi room and replaced it. I don't think it makes obvious change,at least did not make the touch screen as good as the stock.
But I did flash elemental-x kernel after flashing gsi. It might have make it better? Maybe I just got used to the sensitivity of gsi but you may try to flash the kernel and replace the folder, see if any changes are noticed.
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
lovelock8353 said:
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
Click to expand...
Click to collapse
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
hx3 said:
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
Click to expand...
Click to collapse
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
lovelock8353 said:
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
Click to expand...
Click to collapse
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Thanks for the input, pretty sure I have already tried the Oct 27th Havoc OS with Neutrino and still had those touch issues with games, but I will give it another shot in case, did you by chance modify a few things with EX Kernel Manager?
hx3 said:
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
Click to expand...
Click to collapse
The status bar is also thin pixelexperience if you care. Aside from the touch screen latency, I haven't noticed any other issue on this rom, so I recommend you give it a try.
Tried Havoc OS paired with Neutrino, and tweaked around with EX Kernel Manager last night for a while, but still had issues with touch on games and keyboard. Literally everything I have tried on custom installations has not helped improve touch responsiveness.
Come on, surely some random dev still lurks these forums who also notices these delays in touch. Would love to help solve this if I knew exactly where to start, and am willing to test or tweak to get this resolved.
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Grip rejection and touch sensitivity aren't available in GSI's unfortunately, but even some ROMs that do include those settings still have delayed touches, and games eventually lose touch until you reboot on occasion.
Compared to stock, the only ROM that had touch working perfectly (like stock) was Kuran's AICP O. I suspect this has something to do with his kernel, but I am just speculating, I can't be sure on that one.
Then even on a GSI with a stock kernel I still get touch issues, so I have a feeling it has something to do either something in /system but then again, I'm still guessing.
But I appreciate the reply thank you for chiming in on this. ?
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
MoistPicklez said:
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
Click to expand...
Click to collapse
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
rignfool said:
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
Click to expand...
Click to collapse
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
MoistPicklez said:
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
Click to expand...
Click to collapse
Sure...
But why for you no have magisk?
rignfool said:
Sure...
But why for you no have magisk?
Click to expand...
Click to collapse
Edit: I think I may have gotten it figured, and at least narrowed down the issue. I Installed Havoc OS 10-27 again with Dec-patched-boot.img, then Neutrino Hercules over that, on both slots, changed CPU to performance and enabled touchboost, then added these lines to my build.prop and rebooted:
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.6
So far so good, touchscreen jank is gone, scrolling isn't bad at all, and best of all games seem way more fluid. Will continue to test it out.
Edit 2: So far so good games haven't lost touch, not even once, games are still fluid and there are literally no touch delays when gaming or typing. So either the kernel (with performance mode and touch boost on) or the entries I added to the build.prop have fixed this finally. Or both. So freakin' happy.