Develop Bugs

Button press input lag for a few hours a day

Does anyone else get input lag (that lasts for a few minutes to hours) each day?
Every day (most of the time at around the same time) I'll get horrible input lag that will last from a few minutes to hours that will make the button presses on the remote take 3+ seconds just to register and execute on the Fire TV.
I sideloaded an app to check the CPU usage and it doesn't seem like there is any major CPU usage when I'm experiencing input lag.
This is a very annoying problem with my Fire TV and I'm not sure if other people experience the same problem.

If you have root access,you can use Trickster Mod after installing busybox to increase GPU performance by setting the Govern to performance.
This will partially overclock it to always run 400Mhz instead of going down to lower values which causes inconvenient lags.
I managed to get extremely fast performance after enough consecutive hours of on-time.
You could also get Kernel Tuner to make sure all four CPU cores are enabled and at the proper .384-1.7 settings.
My CPU0 was strangely disabled with the maximum clock on zero but I enabled the core by sliding it to 1.7 where it should actually be.
There is some hidden buttons on the main screen for turning CPU1,2,and 3 on/off you can find with the arrow keys.
You can also set your color bit depth to 32bit or 16bit while 24bit is the default for some reason.
Mine runs perfectly fine on 32bit and it appears to look much sharper.
Why is the default set to 24bit when 32bit works fine and looks better?

retroben said:
If you have root access,you can use Trickster Mod after installing busybox to increase GPU performance by setting the Govern to performance.
This will partially overclock it to always run 400Mhz instead of going down to lower values which causes inconvenient lags.
I managed to get extremely fast performance after enough consecutive hours of on-time.
You could also get Kernel Tuner to make sure all four CPU cores are enabled and at the proper .384-1.7 settings.
My CPU0 was strangely disabled with the maximum clock on zero but I enabled the core by sliding it to 1.7 where it should actually be.
There is some hidden buttons on the main screen for turning CPU1,2,and 3 on/off you can find with the arrow keys.
You can also set your color bit depth to 32bit or 16bit while 24bit is the default for some reason.
Mine runs perfectly fine on 32bit and it appears to look much sharper.
Why is the default set to 24bit when 32bit works fine and looks better?
Click to expand...
Click to collapse
Won't this cause the FTV to overheat? I'm thinking about doing this myself, but wouldn't want to cause any premature damage for a slight increase in performance.

The GPU is not far from max when set to normal mode.
It would usually stick around 320Mhz while occasionally going up to 400Mhz.
The heat has not been much different with performance mode keeping the GPU at 400Mhz.
Don't mess with the Quad-Core CPU modification,because that is the main thing that might overheat you.
I keep mine completely on default apart from enabling that one strangely disabled CPU core.
Out of 212F possible degrees,Trickster Mod's Temperature Info reads out 120F right now after quite a few hours of usage while the "battery" says 86F.

retroben said:
The GPU is not far from max when set to normal mode.
It would usually stick around 320Mhz while occasionally going up to 400Mhz.
The heat has not been much different with performance mode keeping the GPU at 400Mhz.
Don't mess with the Quad-Core CPU modification,because that is the main thing that might overheat you.
I keep mine completely on default apart from enabling that one strangely disabled CPU core.
Out of 212F possible degrees,Trickster Mod's Temperature Info reads out 120F right now after quite a few hours of usage while the "battery" says 86F.
Click to expand...
Click to collapse
Ok thanks I'll give it a try.

I also recently acquired two nice apps that use root to customize settings for a major performance boost in general and with "touch" related performance as well.
I have noticed a smoother touch scroll in browsers,faster menus,and app loading speeds.
The two apps are called Performance Booster and Digitizer Booster.
Performance:
https://play.google.com/store/apps/details?id=com.gejos.android.performancebooster
Digitizer Booster (responsive touch):
https://play.google.com/store/apps/details?id=com.gejos.android.digitizerbooster
There is also some donate and pro versions of Performance Booster that allow double boost and triple boost.

retroben said:
If you have root access,you can use Trickster Mod after installing busybox to increase GPU performance by setting the Govern to performance.
This will partially overclock it to always run 400Mhz instead of going down to lower values which causes inconvenient lags.
I managed to get extremely fast performance after enough consecutive hours of on-time.
You could also get Kernel Tuner to make sure all four CPU cores are enabled and at the proper .384-1.7 settings.
My CPU0 was strangely disabled with the maximum clock on zero but I enabled the core by sliding it to 1.7 where it should actually be.
There is some hidden buttons on the main screen for turning CPU1,2,and 3 on/off you can find with the arrow keys.
You can also set your color bit depth to 32bit or 16bit while 24bit is the default for some reason.
Mine runs perfectly fine on 32bit and it appears to look much sharper.
Why is the default set to 24bit when 32bit works fine and looks better?
Click to expand...
Click to collapse
Hey Retroben,
Can you do a posting with all your tips in the forum? your tips have greatly helped me out. Im sure many will greatly appreciate the performance boosts you helped us get.

I got to gather my findings before I can,but I'll see what I can do.
The major speed increase with GPU Govern set to "performance" while 400Mhz is my biggest accomplishment of findings.
I will need to devise a series of steps for each of my findings,so it might take a long while.
The 32bit Color Depth does seem a lot more vibrant and crisper than 24bit.

If anyone is curious, I found out that having a controller plugged in can cause the random input lag.
Someone had mentioned that on another website so I unplugged my xbox controller from the Fire TV and I haven't had any input lag since then.

retroben said:
Performance:
https://play.google.com/store/apps/details?id=com.gejos.android.performancebooster
Digitizer Booster (responsive touch):
https://play.google.com/store/apps/details?id=com.gejos.android.digitizerbooster
There is also some donate and pro versions of Performance Booster that allow double boost and triple boost.
Click to expand...
Click to collapse
I'm curious about what these apps actually do. The dev won't say; it looks like a lot of it build.prop style tweaks but I'm not sure if it's directly editing the file or adding a loadable script someplace.
On the 24 vs 32 bit color: it's not clear to me that for a TV screen, there's an advantage to 32 bit color. There will be a performance improvement in graphics, as the GPU is calculating many fewer bits per pixel.
The 8 bit and 24 bit images in the Wikipedia article are pretty interesting to look at on a display. I'm surpised by how similar they are on my computer display at its normal 32 bit resolution:
8 bit
{
"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"
}
versus 24 bit
An excellent interactive comparison of bit depths is at
http://www.cambridgeincolour.com/tutorials/bit-depth.htm
IF I can extract the tv from the teenager anytime soon, like tomorrow, I'll look at that cambridge image on the set as well. On the computer, at 16 or 32 bit, the difference in appearance of the last two images in it is very subtle.

retroben said:
I got to gather my findings before I can,but I'll see what I can do.
The major speed increase with GPU Govern set to "performance" while 400Mhz is my biggest accomplishment of findings.
I will need to devise a series of steps for each of my findings,so it might take a long while.
The 32bit Color Depth does seem a lot more vibrant and crisper than 24bit.
Click to expand...
Click to collapse
I have all for cores running on Performance max thanks to Kernel Tuner and the GPU on Performance at 400 with Tweak mod and i switched to 32 bit and im running a bit slower now with FF Type Zero in PPSSPP compared to before. I think im going to switch back to 24 bit and hopefully get a bit more speed back.

THAT IS WHAT I SAID NOT TO DO!
The CPU cores all set to that height will majorly overheat your device,and might kill it.
The most you should do is use Kernel Tuner to set the minimal speeds up to something around 50% full.
I reccommend either leaving it at the default or setting it around the 500 range.
Leave the CPU Govern alone,but GPU on performance mode with Trickster Mod is fine.
The Kernel Tuner's 32bit option does not negatively effect the performance enough (if at all),so you can keep it on with no problems.
The framerate of PPSSPP is dependant on what settings are used.
I have almost everything enabled and I get fluid 60fps with DBZ Budokai Shin.
I also get a nearly stutterless fps with SRB2PSP which normally runs abysmal on the actual system.
My PPSSPP settings...
Graphics:Non buffered,frame limit unchecked with 50% alternative speed,all of performance enabled, and the two speedup hacks enabled.
System:Multithreading and I/O disabled with native 330Mhz PSP clock speed on 2000/3000 mode.
A majority of games will have visual issues (Simpsons Game 3D graphics broken [I blame Qualcomm]) while the two I have tested (DBZ Shin and the SRB2PSP homebrew/port) work nearly flawlessly at full rates.
The 50% alternative rate is really helpful for better performance,since the game still goes up to full speed.

retroben said:
THAT IS WHAT I SAID NOT TO DO!
The CPU cores all set to that height will majorly overheat your device,and might kill it.
The most you should do is use Kernel Tuner to set the minimal speeds up to something around 50% full.
I reccommend either leaving it at the default or setting it around the 500 range.
Leave the CPU Govern alone,but GPU on performance mode with Trickster Mod is fine.
The Kernel Tuner's 32bit option does not negatively effect the performance enough (if at all),so you can keep it on with no problems.
The framerate of PPSSPP is dependant on what settings are used.
I have almost everything enabled and I get fluid 60fps with DBZ Budokai Shin.
I also get a nearly stutterless fps with SRB2PSP which normally runs abysmal on the actual system.
My PPSSPP settings...
Graphics:Non buffered,frame limit unchecked with 50% alternative speed,all of performance enabled, and the two speedup hacks enabled.
System:Multithreading and I/O disabled with native 330Mhz PSP clock speed on 2000/3000 mode.
A majority of games will have visual issues (Simpsons Game 3D graphics broken [I blame Qualcomm]) while the two I have tested (DBZ Shin and the SRB2PSP homebrew/port) work nearly flawlessly at full rates.
The 50% alternative rate is really helpful for better performance,since the game still goes up to full speed.
Click to expand...
Click to collapse
Yeah i just did performance govern for a temp performance test, i get the same speeds on ondemand just fine. but i'll try turning off multithreading and I/O and test it again with the other tweaks you said for PPSSPP.

For what its worth, I noticed the lag immediately following updating to the latest fw. On the original fw the ftv felt so fast and snappy and now is feelz slow and laggy.

It must be related to new bloatware like the kiddy mode and music management.
If you press alt+tab on a keyboard to view recent apps,the media options like apps games videos and photos will be listed,which means they run every time you pass the related options.
Root users need not worry,because rbox will have the homescreen options mod for removing the options soon.
I want to wittle it down to search,home,and settings so I can access things much faster.

Mod Boost+ to enforce 720p resolution?

Currently we can force games to run at 1080p resolution which improves performance and battery life. But displaying 1080p image on 1440p screen is not ideal as the scaling will be "lossy", instead, if we could have the option to make games run at 720p, the pixel scaling ratio will be exactly 4:1, having an even bigger gain in performance.
Is it possible to mod Boost+ app so that we could run apps at 720p resolution?

one thing that u can do is this here!
See this
BTW: i think it makes no sense...only for Games in low Energy and Performance boost

you can connect htc to the pc and use the wm size 1080x1920 add shell, which will make it run full system and full hd, boost + will automatically reduce the game resolution to 720p and then go back to the adb shell and type wm size delete, the htc back to 2k but the game is still 720p.

Switching Display Res from WQHD - FHD

Hey guys,
So just wondering has anyone noticed and pros / cons when switching the display resolution from WQHD ( 2560 x 1440) to HHD (1920 x 1080)?
Ive switched to it back and forth several times, and so far I really cant see any difference. The screen quality / crispness seems to be the same. Also I noticed that when i have FHD selected the device obviously seems to run a little faster / snappier.
Incase you don't know what I'm referring to its in Settings>Display>Screen Resolution.

Hmm the only place I can change that is by turning on a power saving mode, I don't see any screen resolution in the settings otherwise (on Canadian N930W8).

stevierayvaughan said:
Hmm the only place I can change that is by turning on a power saving mode, I don't see any screen resolution in the settings otherwise (on Canadian N930W8).
Click to expand...
Click to collapse
Thats strange I have it as a stock option in settings...

I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.

imatts said:
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
Click to expand...
Click to collapse
Ok thanks for the great answer! Guess ill stick to WQHD! Just thought it might offer some benefits.

been testing this and found that it does not get warm when switched down
and to the eye same amazing screen

imatts said:
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
Click to expand...
Click to collapse
phame said:
Ok thanks for the great answer! Guess ill stick to WQHD! Just thought it might offer some benefits.
Click to expand...
Click to collapse
Sorry, but my findings are almost the opposite, I even made a thread in discussion forum to regard the change to FHD to other users.
FOR ME, switching to FHD has improved the responsiveness of the UI (graceui) considerably, and I do not see the "LCD density increase" (btw.: what should that be? i guess DPI?? then switching to FHD would be a DEcrease...)
Also, I'm almost sure that this must lead to battery improvement too. simple because cpu und gpu have less work to do calculating the lesser amount of screen-pixels to draw! This might be slight, but should be there!
The other problems you mention are because you are playing around with density mods, are you using xposed? I use the lower FHD resolution now for a week, and I do not have ANY problem with it!!! And trust me, I use this phone the whole day long and have many programs and communication tools installed.
everything works as it should!

TML1504 said:
Sorry, but my findings are almost the opposite, I even made a thread in discussion forum to regard the change to FHD to other users.
FOR ME, switching to FHD has improved the responsiveness of the UI (graceui) considerably, and I do not see the "LCD density increase" (btw.: what should that be? i guess DPI?? then switching to FHD would be a DEcrease...)
Also, I'm almost sure that this must lead to battery improvement too. simple because cpu und gpu have less work to do calculating the lesser amount of screen-pixels to draw! This might be slight, but should be there!
The other problems you mention are because you are playing around with density mods, are you using xposed? I use the lower FHD resolution now for a week, and I do not have ANY problem with it!!! And trust me, I use this phone the whole day long and have many programs and communication tools installed.
everything works as it should!
Click to expand...
Click to collapse
This was the case both on root/unroot using standard adb shell wm debsity xxx and in-settings res.

how to change output resolution on Pine64 with Remix OS 2.0 to work with NexDock

I received a Nexdock which is basically a display and a bluetooth keybord. The idea is that with Nexdock you can turn your Pine64 computer into a laptop.
More info on NexDock on indiegogo.com
I'm running RemixOS 2.0 on my Pine64 2GB but I can't change the output resolution of the Pine64 to 1366x768.
1366x718 is the native resolution of the Nexdock.
Nexdock works together with Pine64, but all text is hard to read because of the wrong display setting.
When ordering a Nexdock Nexdock claimed compatibility with Pine64...
Any solution or Remix OS update to fix this issue?

I'm on the same boat as you.
Running debian the display is using the right resolution but obviously there's no GPU acceleration and no bluetooth working.
Bluetooth will get a fix in the future probably but I have little hope for GPU on debian. That means no usable Kodi-
At this stage of development Android (and RemixOS) seems to be the better solution for the Pine64.
On PC you can change the vesa mode at boot but I don't know how to do it on Pine.

Ok. I don't have an available SD to burn again RemixOS but could you try this?
in settings> experimental features >enable debug terminal console
press Alt+F1 this will opens the console
type wm size 1366x768 hit enter
press Alt+F7 to exit

Debug window
Unfortunately, that option seems to have been removed for the Pine build. I tried alt+f1 to see if maybe it was enabled by default, but no luck.

Lower screen resolution

Hi
I'm currently using redmi note 8 running a custom rom.
Is there a way to lower the screen resolution from 1080p to 720p?

You can do this with root via terminal apps. Not done this for a while but the command used to be wm size. So you would for example use the command, "wm size 720x1080".

I only find guides for other devices. How to change resolution I know, but I am not sure which settings will work. Usually I just carefully try, but I read that Changing Resolution and Dpi bricked some MIUI 11 Devices, so I am not sure, if I should do it. A bit more performance and battery would be great, but right know no money for a new phone, if somethings going wrong

I use this
https://github.com/Szaki/XiaomiADBFastbootTools