Related
Okay, let's try not to get this thread cluttered up with off-topic speculation like the last one. Starting with what we know already:
There is a ~30 frames per second cap on 2D and 3D rendering. This can be established both visually (play Doodle Jump) and through a benchmark.
If you boot a Nexus One 2.2 ROM, the animation seems to run at 60FPS for a while. This, however, is not totally certain.
This seems to be a software cap, not a hard cap. However, an HTC product representative says otherwise. Jury's still out, apparently.
There is speculation that the cap might be due to the HDMI out on the graphics chip.
Kernel source is being released "soon".
There is touch sensing lag, but this seems to be unrelated.
This issue affects all EVO hardware builds and all EVO ROMs currently.
HTC claims that the cap is by design to improve battery life.
If there is anything else that you have to add that has reasonable evidence backing it up, please do.
EDITED BY TOASTCFH:
Issue of 30fps has been resolved on the devices with Epson pannels through the work done on the kernel reverse engineered kernel source provided in the thread below. for more information and source code for the fix/fixes. also a update.zip can be found on the OP for Fresh 0.3 containing a boot.img containing the kernel compiled with the fps fix.
{KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}
enjoy
END OF EDIT
Correct me if I'm wrong but while running fps2d, aren't there slight flashes where the fps jumps over 30? That in and of itself should prove that the cap isn't hardware based.
Krandor311 said:
Correct me if I'm wrong but while running fps2d, aren't there slight flashes where the fps jumps over 30? That in and of itself should prove that the cap isn't hardware based.
Click to expand...
Click to collapse
Very true! I'm not versed very well in the actual mechanics of the hardware, but that does sound like a good sign.
well, a good idea to see if it's a hardware cap or whether it's with the kernel is to try using toast's ported incredible kernel? since the incredible doesn't have the 30fps issue, and assuming it's software(kernel) based, then we shoudln't have that problem.
someone willing to try? sorry, i can't do this on my evo at the moment
I would try if I had the kernel made for me in zip format to flash. Since I have one of the I/O devices I would be able to try but I dont know how to make the kernel to flash.
This thread is gonna get merged...
timgt said:
I would try if I had the kernel made for me in zip format to flash. Since I have one of the I/O devices I would be able to try but I dont know how to make the kernel to flash.
Click to expand...
Click to collapse
Try one of the overclock builds. They are using toast's source. I want to think this has been tried before.
EDIT:
Seems it was tried on these builds:
RvU Rom: On android central
AOSP Rom: Avalaunch's AOSP Rom
FroYo Rom : Avalaunch's FroYo Rom
http://forum.xda-developers.com/showpost.php?p=6769032&postcount=88
Vinny75 said:
Try one of the overclock builds. They are using toast's source. I want to think this has been tried before.
Click to expand...
Click to collapse
I'm pretty sure it has and still has the same issues the board files for the evo are in there though not the incredibles
I don't think it is firmware. The RUU for the EVO and Incredible both contain the same tp_amtel224_16ab.img which may be the firmware for the Amtel 224 touchscreen controller. (http://forum.xda-developers.com/showthread.php?t=704640)
From ffolkes
i've been working on this all day. literally. about 9 hours straight.
this is what i've found. changing the mddi clk_rate to anything but 384000000 results in it getting set to 117965000 according to dmesg. now 384/20 = 19.2 which is precisely the frequency of TCXO. seems a bit odd. it's also exactly half of the other clock defined, GLOBAL_PLL at 768mhz. PLL1 (core) is also 768. another clock is defined, AXI at 128mhz, that acronym is mentioned in the video/gpu drivers. not sure if that's related to that clock, or just some video thing i'm not familiar with and completely unrelated.
changing PMDH_CLK (in devices.c) to OFF | MINMAX or just MINMAX *AND* changing the mddi freq to anything higher than 384000000 results in dmesg saying mddi was set to 235930000 (instead of 117965000) but i still get the same 30fps id get if it was at 384000000. so when you think about it, this means mddi can't be capping it, otherwise i'd see a difference between 235930000 and 384000000. but they're exactly the same fps. it HAS to be happening elsewhere.
i've also found removing the adreno200 drivers from /system/lib/egl results in a silky smooth sprint boot animation, the gui flickers crazily, but fps2d still shows 29. perhaps this is what people were seeing with the froyo boot animation looking smooth.
you know, this 29fps thing is very specific...ntsc is 29.97fps. coincidence? i really don't think so. fps2d always averages out to 29, not 30.
i also tried removing all the hdmi code in the board files, that didn't change anything.
i find it very unlikely this is hardware limited though. the gpu is on die with the cpu, so unless htc had qualcomm make them a custom chip, it's all software controlled. there's nothing to suggest the gpu has its own crystal on the pcb. i mean, if we can completely control the cpu frequency via software, the same stands to reason with the gpu.
if it was something hdmi hardware related, it should be able to be disabled in the kernel and the evo wouldn't even know it was there, just like with the sensors that don't work.
it appears the evo uses a SIL9022A for hdmi, which makes no mention of requiring any change to the lcd frame rate. (http://www.siliconimage.com/products...t.aspx?pid=150)
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showpost.php?p=6854074&postcount=664
I did a little experiment to see if the restriction was in user-space or the kernel:
- First I set up my machine like I described in the "Getting a wider set of development tools on the phone" thread
- Then I wrote a little program (attached) that suspends the phone compositing manager and wrote to the frame buffer device directly.
The conclusion: Even when writing straight to /dev/graphics/fb0, talking straight to the kernel, there's a 30fps limit.
halfline said:
I did a little experiment to see if the restriction was in user-space or the kernel:
- First I set up my machine like I described in the "Getting a wider set of development tools on the phone" thread
- Then I wrote a little program (attached) that suspends the phone compositing manager and wrote to the frame buffer device directly.
The conclusion: Even when writing straight to /dev/graphics/fb0, talking straight to the kernel, there's a 30fps limit.
Click to expand...
Click to collapse
So does this hint that it's a board driver issue and not a hardware issue? Is the fps being sent to fb0 already at 30fps? Sorry, just trying to understand. Been working on this issue for days too.
AssassinsLament said:
So does this hint that it's a board driver issue and not a hardware issue? Is the fps being sent to fb0 already at 30fps? Sorry, just trying to understand. Been working on this issue for days too.
Click to expand...
Click to collapse
I think it would be very strange if it were a hardware issue, but this test unfortunately doesn't help answer that question.
As far as I can tell, the way drawing works on the phone is... Every app communicates with this "system_server" compositor process. That compositor is what sends the drawing to the framebuffer device. The individual apps use shared memory to share what they want drawn with the compositor.
The question I was trying to answer was. Is the system_server compositor limiting the framerate, or is it the kernel? My program takes the compositor out of the picture, and just does some very fast drawing straight to the framebuffer device as quickly as possible. It measures the framerate at which the drawing is getting processed by the kernel. If I let it run for a while the output is like:
30 frames in last second, 29.7 average fps, total time 102 seconds
which leads me to believe it's definitely not the compositor (or say userspace libraries) imposing the 30fps framerate.
halfline said:
I think it would be very strange if it were a hardware issue, but this test unfortunately doesn't help answer that question.
As far as I can tell, the way drawing works on the phone is... Every app communicates with this "system_server" compositor process. That compositor is what sends the drawing to the framebuffer device. The individual apps use shared memory to share what they want drawn with the compositor.
The question I was trying to answer was. Is the system_server compositor limiting the framerate, or is it the kernel? My program takes the compositor out of the picture, and just does some very fast drawing straight to the framebuffer device as quickly as possible. It measures the framerate at which the drawing is getting processed by the kernel. If I let it run for a while the output is like:
30 frames in last second, 29.7 average fps, total time 102 seconds
which leads me to believe it's definitely not the compositor (or say userspace libraries) imposing the 30fps framerate.
Click to expand...
Click to collapse
Ok, thanks. Here is what I've tried so far:
I've taken the full stock HTC Incredible source (similar device), and just put in 9 board supersonic files into it, changed the makefile to compile those supersonic specific files and the kernel boots and everything is fine, but its still capped at 30fps. The HTC Incredible does not have the 30fps issue, so it's 1) code that I can't find in those 9 board supersonic files, or 2) Hardware capped.
That's my best thoughts for now on it
I think it has to do with the htc lock screen. The lockscreen is difficult to remove in custom roms (i haven't seen anybody do it yet) and when you run fps2d with the screen off you get 60 fps (or like 57)
Hey... you guys do know that720p LCD HDTVs display at 30Hz right? Newer ones do 240 and whatnot, but if you have an LCD monitor that's high def (like our evos), play with the refresh rate... just saying
Tilde88 said:
Hey... you guys do know that720p LCD HDTVs display at 30Hz right? Newer ones do 240 and whatnot, but if you have an LCD monitor that's high def (like our evos), play with the refresh rate... just saying
Click to expand...
Click to collapse
I don't think any one here knows that. At least anyone that has done their homework.
-Roger
hibby50 said:
when you run fps2d with the screen off you get 60 fps (or like 57)
Click to expand...
Click to collapse
If that is true, wouldn't this be evidence that it is not hardware capped?
roghaj said:
I don't think any one here knows that. At least anyone that has done their homework.
-Roger
Click to expand...
Click to collapse
I don't know what thats supposed to mean so ill ignore it...
How about trying the straight to kernel test on avalaunchs' froyo v8 with the OC revision flashed? seems like something different... custom kernel, overclocked, and the cameras not working could be a plus for the benchmark... hopefully hdmi is dead too....
Does anyone know if the hd2 has this issue doesn't it have the exact same screen and alot of the same hardware as the evo just different OS
Hi guys,
I had made an camera.apk modded Beta version based on DDKP2..And i dont hav i9003 device presently..,so i need a skilled testers to find out any bugs that could arise..
This camera.apk modded version is totally checked, compiled by me and i found that i9003 could capable of recording HD videos at higher quality than stock camera.apk..Before it is opened for all i need testers ...
Here is the info what the modded version can do I9003:
1.Increased 720p HD videos Running @13mbps/30fps ( STOCK ) to 720p @20mbps/30fps (MOD)
2.Increased Audio bitrate to 192kbps/44.1Khz (MOD) quality Instead of 64kbps/16khz (STOCK)
3.Allowing camera.apk to use at any battery life
A lil problem..will upload soon once it is finally tested by me....
reserved..
reserved....
for implementation of camera hack u can reffer here
http://forum.xda-developers.com/showthread.php?t=1453547
he has successfully allowed power button as camera button for both still snaps and video recording ! he also allowed using camera while on a call and <15% battery
Hi,
i have a question:
increasing audio quality doesn't make that distortions in loud environment disappear, right?
This is most important for me...
I have observed that whenever we record videos in low light then vdo quality is not upyo the mark. It looks little bit blackish vdo. But in mid range or higher range nokia phone's vdo quality is much...much better. Can't we do anything about this???
Can i9003 record video at 1080p(full hd)?
vishal24387 said:
I have observed that whenever we record videos in low light then vdo quality is not upyo the mark. It looks little bit blackish vdo. But in mid range or higher range nokia phone's vdo quality is much...much better. Can't we do anything about this???
Click to expand...
Click to collapse
yes i agree with vishal here ! and i have observed one thing ! i found my very old froyo 640x480 res video recorded in a club ! and the amazing part is that the video doesnt hav the locked fps recording rate which the new firmwares have ! so because its not locked at 30 fps it allows more light to be recorded and u can visibly c much more !! its jst odd that gingerbread did this ! even on kpe it used to work fine ! but now if i flash kpe it still doesnt work that way ! how on earth is this possible ?
rascal0pl said:
Hi,
i have a question:
increasing audio quality doesn't make that distortions in loud environment disappear, right?
This is most important for me...
Click to expand...
Click to collapse
yes and the treble noise will be high(fixing it)
shriomman said:
for implementation of camera hack u can reffer here
http://forum.xda-developers.com/showthread.php?t=1453547
he has successfully allowed power button as camera button for both still snaps and video recording ! he also allowed using camera while on a call and <15% battery
Click to expand...
Click to collapse
thank u friend..first i will make this mod as stable
vishal24387 said:
I have observed that whenever we record videos in low light then vdo quality is not upyo the mark. It looks little bit blackish vdo. But in mid range or higher range nokia phone's vdo quality is much...much better. Can't we do anything about this???
Click to expand...
Click to collapse
As i9003 doesnt hav flash light ,the quality may be poor in low light environment...trying to find solution
mrphumin said:
Can i9003 record video at 1080p(full hd)?
Click to expand...
Click to collapse
Not sure may be HW problem may arise..If possible i will try that
@sharp87- heres sum info on WHY its too dark compared to other cams ! the i9003 video cam after KPE has framed a LIMIT to minimum 30 fps for video recording video ! earlier it used to b dynamic from 15 fps-30 fps ! i will upload a link of a video i had taken earlier in lower resolution and u can EASILY make out the difference of the frame rate during playback ! uploading now ! will edit this post with that recording
edit- old froyo video - 640-480 http://www.mediafire.com/?sxcjy8chro486rc
edit2- JUST recorded sample 640-480 http://www.mediafire.com/?f5fs2p2zr5efq6n
edit3- image of the recorded scene WITHOUT night mode (auto mode) http://www.mediafire.com/?d6xj48dhrorzjr0
hopefully this will prove my point on what i'm trying to say !
sharp87 said:
As i9003 doesnt hav flash light ,the quality may be poor in low light environment...trying to find solution
Click to expand...
Click to collapse
as shriomman points out the issue in GB is due to fix frame rate whereas froyo had variable frame rate which would change to less FPS/sec in low light, this would cause blur but will still get you clear image whee as GB gives priority to FPS thus performs very poor in low light.
GB is nothing but a higher version of crap coding from samsung developers.
sgsI9003 said:
as shriomman points out the issue in GB is due to fix frame rate whereas froyo had variable frame rate which would change to less FPS/sec in low light, this would cause blur but will still get you clear image whee as GB gives priority to FPS thus performs very poor in low light.
GB is nothing but a higher version of crap coding from samsung developers.
Click to expand...
Click to collapse
exactly !! the thing is .. how do we get the original thing back ?
shriomman said:
exactly !! the thing is .. how do we get the original thing back ?
Click to expand...
Click to collapse
@shriomman if you have the froyo camera.apk with you then upload it here let me try
send from gt-i9003 using android keyboard
sirilpta said:
@shriomman if you have the froyo camera.apk with you then upload it here let me try
send from gt-i9003 using android keyboard
Click to expand...
Click to collapse
m not on froyo anymore ! i hardly think its related to the apk cus when i switched to kb3 alst week i had the same problem :\
shriomman said:
m not on froyo anymore ! i hardly think its related to the apk cus when i switched to kb3 alst week i had the same problem :\
Click to expand...
Click to collapse
can you collect it from anywhere so that its smali files value can be applied to gb file and can see the difference
sirilpta said:
can you collect it from anywhere so that its smali files value can be applied to gb file and can see the difference
Click to expand...
Click to collapse
u can post in darkgen page ! that firmware is based on kb3 ie froyo !
larga el archivo que lo prubo papá. que linda son estas noticias.
estaria bueno que largen tv-out
Hi guys. I just bought a pre owned huawei honor 6. It runs smoothly until I try playing Heroes Evolved Mobile. The fps usally drops and the game becomes laggy. This game runs smoothly on my samsung j7 which has lower specs than huawei honor 6. Any help or suggestion on how to fix this? Thanks
This must be the GPU's fault.
Sent from my Honor 8 using XDA Labs
Fps,
Yah. Is there anyway so i can improve its performance?
attackontits said:
Yah. Is there anyway so i can improve its performance?
Click to expand...
Click to collapse
Try reducing the graphics of the game if the setting is present.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Try reducing the graphics of the game if the setting is present.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I already set the graphics to low and resolution to low. Still the same.
attackontits said:
I already set the graphics to low and resolution to low. Still the same.
Click to expand...
Click to collapse
Then we can't do anything about it anymore. Unfortunately.
Try to reduce screen resolution ,it will let the game run
I do not guarantee that this works, but it has helped me in similar situations; enable developer settings if not enabled already and check "Force GPU Rendering". As I said, it might help, but also make it worse.
Parrakas said:
I do not guarantee that this works, but it has helped me in similar situations; enable developer settings if not enabled already and check "Force GPU Rendering". As I said, it might help, but also make it worse.
Click to expand...
Click to collapse
GPU rendering leads to lags
gopinaidu77 said:
GPU rendering leads to lags
Click to expand...
Click to collapse
(I'm not a pro at this stuff) but it still might give some boost in some apps right? Or make them lag even more, but the pooint was, if it helps with the fps lag, keep it enabled while you play & after you stop playing, disable it.
And there is a thread about this (https://forum.xda-developers.com/note-4/general/force-gpu-rendering-impact-performance-t3047664).
Parrakas said:
(I'm not a pro at this stuff) but it still might give some boost in some apps right? Or make them lag even more, but the pooint was, if it helps with the fps lag, keep it enabled while you play & after you stop playing, disable it.
And there is a thread about this (https://forum.xda-developers.com/note-4/general/force-gpu-rendering-impact-performance-t3047664).
Click to expand...
Click to collapse
Yes I agree with this.
Are there anyone able to mod the camera libs for RN5? Shutter limit is 1/2s on RN5 whereas its 16s on Mi Max 3 which uses same sensors.
Explore The Universe said:
Are there anyone able to mod the camera libs for RN5? Shutter limit is 1/2s on RN5 whereas its 16s on Mi Max 3 which uses same sensors.
Click to expand...
Click to collapse
+1 on redmi y2 it is 32 secs and also includes manual focus options
+1
+1
+1
+1
Can't any senior member with coding experience work on this ? I would have done it myself if I had any Android coding experience
haigal said:
Can't any senior member with coding experience work on this ? I would have done it myself if I had any Android coding experience
Click to expand...
Click to collapse
I also want to know how to modify this, I know some coding experience
+1
yes Shutter limit low
Really sad to see a camera oriented phone without long exposure photography . If only someone would come forward to mod the camera libs
+1
+1, everyone with a RN5 should be interested on this
+1
can we stop with +1, if you don't have anything meaningful to contribute, it's better to not spam the thread
SpyKnife said:
can we stop with +1, if you don't have anything meaningful to contribute, it's better to not spam the thread
Click to expand...
Click to collapse
+1
SpyKnife said:
can we stop with +1, if you don't have anything meaningful to contribute, it's better to not spam the thread
Click to expand...
Click to collapse
This's XDA now....lol!!
I tried modify to 32s, but no effects. Set to 8s and capture will show camera error, and other time, more than 1/2s, no effects. I also found 1/4s is the most brightness, even more than 1/2s.
Actually maximum right now is 1/4 , the 1/2 shown in most apps is more like 1/6 since it is darker than 1/4. Did you try to increase by lib editing?
haigal said:
Actually maximum right now is 1/4 , the 1/2 shown in most apps is more like 1/6 since it is darker than 1/4. Did you try to increase by lib editing?
Click to expand...
Click to collapse
Well, I increased the time to 135s, but output a black photo
Any idea how is possible to use 960 fps slow motion without applying it only in the last part of the video?
yes you can change it when you play the video
You cant in 960 :/
cycloholic said:
You cant in 960 :/
Click to expand...
Click to collapse
Have you found a way to modify the recording length and the slow motion part?
Chapi Chap said:
Have you found a way to modify the recording length and the slow motion part?
Click to expand...
Click to collapse
Fixed time for 960 fps. 120 or 240 fps no limit time.
lemach said:
Fixed time for 960 fps. 120 or 240 fps no limit time.
Click to expand...
Click to collapse
Are these considered as slow motion?
960 would be ****ing great, but the way it works is useless for me at least :/
cycloholic said:
960 would be ****ing great, but the way it works is useless for me at least :/
Click to expand...
Click to collapse
So how exactly are you using the slower frame rates as slow motion?
Chapi Chap said:
Are these considered as slow motion?
Click to expand...
Click to collapse
i really think they are. I recommend you 240 fps.
lemach said:
i really think they are. I recommend you 240 fps.
Click to expand...
Click to collapse
Tried that, actually this is exactly the functionality I was looking for.
thank you very much!
Hope Xiaomi will add the same functionality for 960FPS, that would be amazing.
The reason for the 960FPS being time fixed, is due to the CPU/GPU are only interpolating the frames, so the camera sensor really isn't bringing in a full 960FPS...
I believe it was something around 300FPS or so, or it could be the 240FPS just with the frames separated and interpolated to 960FPS.