Related
Is flash 10.1 beta hardware accelerated? Video isn't 100% smooth, I read on engadget froyo walkthrough that hardware acceleration wasn't enable yet on their beta, but is the public beta HW accelerate enabled?
Yeah, it's not what I was expecting. Here's hoping (for Adobe's sake) that it's not hardware accelerated yet. Is there any GPU resource monitor available? Would that necessarily show you if it's accelerated?
Sites which haven't been optimized for mobile flash don't perform flawlessly but those that have been (Miniclip.com etc) work extremely well. It feels as if you're playing games locally installed
theres not any hardware acceleration to be done on the nexus. flash just uses the cpu like normal flash, hardware acceleration refers to using a gpu (something the n1 is missing)
iammuze said:
theres not any hardware acceleration to be done on the nexus. flash just uses the cpu like normal flash, hardware acceleration refers to using a gpu (something the n1 is missing)
Click to expand...
Click to collapse
I love when people think they know what they're talking about.
Vash63 said:
I love when people think they know what they're talking about.
Click to expand...
Click to collapse
X2. Wow. Just wow.
URPREY said:
X2. Wow. Just wow.
Click to expand...
Click to collapse
+1.. that's why the ndk shouldn't have released - java uses the cpu lol
Porn on my nexus runs smooth! Large flash files aren't the quickest, but remember, this is BETA!
its still in beta, so we will see i guess. regardless its a step forward.
I think the answer is "sort of."
From the Android Flash readme:
Flash on Android supports software decoding for all the same H.264 profiles as Flash on the desktop, and uses the hardware decoder for videos using H.264 Baseline Profile and Level <= 3.2.
There are also a lot of Known issues in rendering in the readme file. My own subjective test was running Bejewled Blitz in Facebook. It ran a little better (smoother) on my nexus than with my acer aspire netbook with a 1.2 GHZ atom. This was much better than I was expecting given that it's still beta.
i find that as long as I have atleast 220mb of ram free, bangbus runs just find. the video is smooth, the audio is too but its a little out of sync at times. I once caught my browser using up 105mb of ram and the phone was running at 104 degrees too. Im running pershoots oc kernel, and it helped smooth out the flash a bit.
Just wondering if anyone else has watched many movies with NF ? I'm using the most recent version, but running off SD card.
Seems quite a bit slower than running under B&N stock 2.1
What SD card, and also what specifications are you using?
nootered said:
What SD card, and also what specifications are you using?
Click to expand...
Click to collapse
I checked, and it is only a 4 GB Class 2 card (Sandisk). I suppose that could be having a significant impact ?
I'm not running an OC kernel either yet.
Is it possible to get at the internal memory when running NF off the SD card ?
I have had very good results using QQPlayer on my OC'd NookColor at firmwares 1.0.1 and 1.1. I've yet to try out Froyo due to it's lack of video/audio playback.
With the overclock, all formats worked smoothly, but without, there was a bit of a stutter with some of them.
edit: I use a 16GB Class 2 uSD
synnth said:
I have had very good results using QQPlayer on my OC'd NookColor at firmwares 1.0.1 and 1.1. I've yet to try out Froyo due to it's lack of video/audio playback.
With the overclock, all formats worked smoothly, but without, there was a bit of a stutter with some of them.
edit: I use a 16GB Class 2 uSD
Click to expand...
Click to collapse
Why is video poor on Froyo, is it due to lack of video support or the fact that its on SD or both?
Anyone know if it will be possible to get the video hardware support on Froyo?
Regards,
Mike
Yeah all this love for the Nook and while its still early in it's life... running froyo from internal at the moment leaves me YouTube less... :/
panamamike said:
Why is video poor on Froyo, is it due to lack of video support or the fact that its on SD or both?
Anyone know if it will be possible to get the video hardware support on Froyo?
Regards,
Mike
Click to expand...
Click to collapse
Obviously, no-one. No sound from CyanogenMod guys that hardware based video decoding AND rendering is enabled in their customized Android 2.3 (I suspect they customize stuff mostly for fast/smooth GUI and/or better 3D. When the same shaders of SGX530 refuse to act as video deinterlacing renderers in their build, they could say that they wash their hands and move on. Sure, that's what TI has stuck with their Zoom2 platform. Or Motorola with the following Droid X/2 phones. Remember, there's no hardware decoders support in Android if it's not for m4v. They have that principle, you know. Rockchip/Snapdragon don't
Mr. Deeper-blue of recent "Honeycomb on NC" fame has GUI hardware acceleration working. It's not video, and very far from getting hardware overlays (=zooming in/out HD video at will, and following the device's orientation, full augmented reality support, full HD video phone, etc.,. etc.) But we are all ears. Pity the A3.0 is more of a pure concept now, having nothing to do with a practical implementation on a 3-year old SoC OMAP3621 Google decided it doesn't like a base demo A3.0 machine.
In any case, for good video on a single-core ARM (plus GPU, plus DSP though) look for the work on Android 3.x, plus VOME engine donated by VisualOn for the AOSP 2.3 project.
However, if nothing of above helps much, get yourself dual-core TI OMAP4430 RIM PlayBook based on QNX and forget everything about those silly green dudes (for awhile though....too many Android hackers put Android on their Pandaboards somewhere back in summer 2010)
Consider it a rant, if you will. But it also a "bow" of sorts to Mr Deeper-blue who probably never bothered to look into "limitations" of either OMAP3621, or Android 3.0. He just did unthinkable. Now I won't be suprised to see Android 3.0 on my Pandigital Novel one of those days, lol.
-----------------------------------
fineoils.blogspot.com
aludal said:
Obviously, no-one. No sound from CyanogenMod guys that hardware based video decoding AND rendering is enabled in their customized Android 2.3 (I suspect they customize stuff mostly for fast/smooth GUI and/or better 3D. When the same shaders of SGX530 refuse to act as video deinterlacing renderers in their build, they could say that they wash their hands and move on. Sure, that's what TI has stuck with their Zoom2 platform. ...
Mr. Deeper-blue of recent "Honeycomb on NC" fame has GUI hardware acceleration working. It's not video, and very far from getting hardware overlays (=zooming in/out HD video at will, and following the device's orientation, full augmented reality support, full HD video phone, etc.,. etc.) But we are all ears. Pity the A3.0 is more of a pure concept now, having nothing to do with a practical implementation on a 3-year old SoC OMAP3621 Google decided it doesn't like a base demo A3.0 machine....
-----------------------------------
fineoils.blogspot.com
Click to expand...
Click to collapse
This is pretty much what I was wondering about, will OMAP3621 see any support or potentially get proper drivers adapted to work with the various hacks.
Maybe if B&N comes out with their version of Froyo they may include what's needed to get the DSP support driver/interface...
Mike
overclocking will definitly speed things up
Hey guys, appreciate the work you guys have done here. Am running stock rom on my galaxy mini, still new to android after ages spent as a wm6.5 lurky hence taking my time before trying to go gingerbread. I have tried mx player, mobo player, qq player rockplayer yet I still can't get •Mkv clips to play well. Video is always choppy though sound is fine, in wm apps had the option to reduce quality unlike in android. Any ideas on how I could improve playback?
yes, the only solution for your problem is buying an upgrade phone.
The Adreno 200 GPU and the 600MHZ CPU is not up to the task of playing any file with higher resolution than 480p. Maybe some MPEG4 files, but H.264 not possible.
MX Player is one of the best players in terms of hw acceleration. If this can't handle well, you are out of luck.
icsterm said:
yes, the only solution for your problem is buying an upgrade phone.
The Adreno 200 GPU and the 600MHZ CPU is not up to the task of playing any file with higher resolution than 480p. Maybe some MPEG4 files, but H.264 not possible.
MX Player is one of the best players in terms of hw acceleration. If this can't handle well, you are out of luck.
Click to expand...
Click to collapse
agreed +1
Try QQ player it also gives nice playback...
icsterm said:
yes, the only solution for your problem is buying an upgrade phone.
The Adreno 200 GPU and the 600MHZ CPU is not up to the task of playing any file with higher resolution than 480p. Maybe some MPEG4 files, but H.264 not possible.
MX Player is one of the best players in terms of hw acceleration. If this can't handle well, you are out of luck.
Click to expand...
Click to collapse
Hmmm bummer, guess I'll start eyeing the galaxy S soon, this happens to be my first crack at android already am suffering from the smartphone upgrade fever! That voice in my head that keeps telling me to upgrade just won't let up! With that said the galaxy mini is still quite cool, for a starter.
Well then whats the max recommended benchmark video resolution I should try to play? I remember having issues with an .mkv 480p big bang episode. whats the highest resolution any of you have played with reasonable results?
You can install tweaked chainfire drivers along with overclocked kernel to see if its working
i think if you oc it will work much more smoother
What is the resolution of the videos ur trying to play?
Convert them 240x320 and try.
This works best for me..though I don't remember how well.mkv plays but I tried various formats in this res a long time back and they all seemed to play well.
Try on both mobo and Qq...
Hmm I'll give Mx a try.
---edit----
Damn this thread is months old!
Haha dont worry about it being a month old, we still read it. Converting videos sounds tideous
Sent from my GT-S5570 using XDA App
kwoski said:
Haha dont worry about it being a month old, we still read it. Converting videos sounds tideous
Sent from my GT-S5570 using XDA App
Click to expand...
Click to collapse
ya but that is the best way to get most of the hdvideos to work, afaik.
i use total video converter.
cannot expect a 720 or a 1080p to play on mini without down converting it
btw ya i've had a lil trouble with .mkv, i prefer avi.
.avi always delivers in my mini, its my preferred format, had a chance to fiddle with a pals galaxy s and galaxy s2 and damn I was so freaking blown out of the water! Right now am thinking upgrade, just as soon as I rob a bank to afford one! just rooted galaxy mini, was considering overclock options but am not sure that would do much improvements. Oh and what about CHAINFIRE3D? Do you guys think it can enable smoother mkv play on mx video player or does it only work for games?
Sent from my GT-S5570 using XDA App
I think Cf3d works only with games.
Sent from my GT-S5570 using Tapatalk
Is that an expert opinion or an educated guess?
Sent from my GT-S5570 using XDA App
I'm not sure abt cf3d cuz it has lots of options..and if u use it properly(knowing what does wat),it mite have some effect.
head over to that thread.
I actually have chainfire installed, just freaked out by the warning it gave just before I install the openGL driver so am still growing a pair before activating it . Read the forum and pretty much still I can't tell heads or tails about what it really does. And also from the looks of things it seems to be complimented better by overclocking abilities on your phone. I have been using stock froyo for a while and now am feeling ready to graduate to the big boys league, just can't decide yet between going for a stock gingerbread rom or cyanogen rom. As time goes am sure more solutions will come out to tackle this problem coz .mkv is a pretty important format these days especially in phones coz of its small storage size requirements, wish android and samsung had taken more time to make it more compatible with their hardware and software respectively
Sent from my GT-S5570 using XDA App
Does any dev know if it is possible on Gingerbread to use this "technology" to create "buttersmooth" refresh rates using vsync and videobuffer?
Thank
This is what i know accurate as per my HW knowledge multiplied by driver programing experiences.
Phones' LCD hw as per resolution doesnt support Vertical Sync more than 65Hz. Although LG has used 75Hz to all LG devices. Increasing Vertical Sync only gives high benchmarks by false 2D/3D results. Increasing HW Vertical Sync HZ rather than supported by phone actually worsens performance, needless to mention in longer run it damages LCD controllers. Phone LCD supports max 65HZ refresh rate thats what called VSync(Virtical Sync).
FramBuffer refresh rate is another story. We can setup kernel kill fd signal(SIG KILL) to specific ms to refresh forcefully kill and restart framebuffer artificially but that will gives blinking display. I am already done with FB refresh rate
Sent from my LG-P990 using Tapatalk 2
But spica surely it works in a similar way to PCs? I.e the Vsync is only set to the max possible frame render of the display, e.g. a 60HZ monitor will sync at 60FPS where Vsync will kick in if enabled... you can also do this for any refresh rate like the newer 120hz monitors.
Wouldnt it simply require changing the variables to acknowledge this extra hz in our displays?.
Just curious, probably wrong but it would be nice if it were true as it would be even easier .
Project butter also uses both the CPU and the GPU to render frames. Its switches between the 2 and one can "prepare" while the other one is still being used to render
Sent from my LG-P990 using xda app-developers app
Chris4evernoob said:
Project butter also uses both the CPU and the GPU to render frames. Its switches between the 2 and one can "prepare" while the other one is still being used to render
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Hmm I dont know much about this project.
Wider LCDs for CPU as per the resolution, can support hight refresh rate but our phone LCD cant:/ it works(increasing vsync and it doesnt damage to LCD controllers in short run) but it will cheat benchmark(as softwares detects wrong info and muliplication) but in realtime performance will be worsened. And its not good for LCD controller HW. We will find every phone with 65hz max except LG. As because phone's LCD controller HW can draw only max 65 HZ sync. Increasing it will draw more frames but it wont be used by HW resulting in wasted frames. FrameBuffer refresh is completely different thing unrealated to vsync. If I can find more detailed refrence link about it than I will post the link when i get PC access soon
This project might be using combination of FB and vSync, not only vsync.
Can anybody rdirect me towards link of this project?
Sent from my LG-P990 using Tapatalk 2
I previously had phone Samsung Galaxy Spica((I-5700).
I began Horse Power Kernel Development 1st with these kernel. Reffer this link:
http://forum.samdroid.net/f53/development-kernel-horse-power-4973/
Click on Previous Changelogs History spoiler.
You can see in older changes i have increased Vertical Sync rate to 80Hz. But believe me it gives only massiv e 2d/3d score. But the performance of games were worsenedd incl. Of UI smoothness. I did revert it in newer version.
Yes its just matter of changing values in kernel display driver
I dont anything about butter project, can anubody provide me link of it?
Sent from my LG-P990 using Tapatalk 2
http://www.google.com/search?hl=en&...3.0.0.0.8612.2.0.0.2.2.0.0.0..0.0...0.0...1ac.
Don't know what you are looking for Spica?
And another link with some info.
http://www.androidpolice.com/2012/0...e-responsive-apps-that-anticipate-your-touch/
Thank you for providing links.
Edit: oh sorry w/o reading it I completely misunderstood before. Its different
Sent from my LG-P990 using Tapatalk 2
Okay I read overly not in deep. Its not related to kernel-HW's refresh rate that I was discussing, hence its safe. Okay its related to android framework I guess, not read in deep. Not related with Kernel and kernel needs no changes. Its google's work I guess
It seems good. I will look more deeply tomorrow as soon as I get PC access
Sent from my LG-P990 using Tapatalk 2
IF this would ever be ported to Gingerbread for our phone, it would only be found on CM7 ROMs, not on Stock ROMs.
Android has kinda bad design concerning the scrolling stuff in its framework which causes it to never be as smooth as other Smartphone OS like iOS or WP are or will be.
This base design can't be change easily anymore, in order to NOT break the (available) Android apps.
It's also clear that even though Google can't change the whole base, they will put efforts in creating and finding workarounds for providing a smoother UI anyway.
This and faster hardware will make Android smoother every year.
They have already proven with both ICS and Jelly Bean that they are able to improve the smoothness. But the changes they had to perform for this surely (without knowing further details) affect big parts of the Android Framework.
This means in order to get a smoother scrolling experience on Gingerbread, ROM DEVs would need to backport features and changes of the new OS revisions to GB framework. And I'm sure this is way too much work (for our crappy little phone ).
Also it can only be done if the whole framework source is available, so no smoother scrolling for STOCK. And there is nothing kernel DEVs could do in this case by their own (besides the things they are doing already), unfortunately.
But you guys could ask Temasek to backport smoother scrolling to his CM7 ROM *jokingly - won't be that easy*
Answering to the OP, it's quite impossible... We need to backport lots of changes in GB framework (for example hw acceleration) and to do a lot of work that it doesn't worth it. And the only rom that would support these changes is cm7, and it isn't so stable.
If you like project butter, get a galaxy nexus. We have doubts to get ics update on our 2x...
markop90 said:
Answering to the OP, it's quite impossible... We need to backport lots of changes in GB framework (for example hw acceleration) and to do a lot of work that it doesn't worth it. And the only rom that would support these changes is cm7, and it isn't so stable.
Click to expand...
Click to collapse
Yeah that's exactly what I wrote - just in short But I wouldn't call CM7 unstable.
markop90 said:
Answering to the OP, it's quite impossible... We need to backport lots of changes in GB framework (for example hw acceleration) and to do a lot of work that it doesn't worth it. And the only rom that would support these changes is cm7, and it isn't so stable.
If you like project butter, get a galaxy nexus. We have doubts to get ics update on our 2x...
Click to expand...
Click to collapse
Cm7 is one of the most stable roms on our phone...
Sent from my LG-P990 using xda app-developers app
Stefan Gündhör said:
IF this would ever be ported to Gingerbread for our phone, it would only be found on CM7 ROMs, not on Stock ROMs.
Android has kinda bad design concerning the scrolling stuff in its framework which causes it to never be as smooth as other Smartphone OS like iOS or WP are or will be.
Click to expand...
Click to collapse
Actually scrolling in Android is very well implemented. The reason for the lag is twofold:
1) Android started as keyboard driven OS (a better blackberry), with no touch interface in mind, so the UI thread is of normal priority. That means that touch events don't have a higher priority than any other process that runs on your phone at the same time, thus any animation or transition can be interrupted (in cpu cycles) by another process. Say for example that you are scrolling a long list. Every other process that does something at the same time (updating your widgets, checking your email etc) will get equal time with the cpu as the scrolling animation. That means allot of interrupts during that animation that cause frames to drop and thus lag to occur. It also means that the ui thread must wait for it's time whenever there is a touch event (user interaction through the touchscreen) to respond. Changing the UI thread priority would solve most ui problems with android but it would also indeed break compatibility with older apps.
2) The other problem is that most devs do a very poor implementation of lists. Android lists are actually very efficient but badly documented, and many developers implement them in ways that are sub-optimal. In order to save memory, the list only uses as many views (items) as fit the screen, and when the user scrolls it simply recycles them by changing their content. That means that the objects displayed in the list are cleared from the memory as soon as they leave the screen. So every time you return to the place where those objects where, an interrupt followed by IO with the filesystem takes place (the worst kind of interrupt). That's not such a big problem when the only thing you want to display is text, but what if you use bigger stuff like bitmaps? Then you get allot of lag. To avoid that you have to keep the list objects in memory. If you have too many such objects and want to avoid filling all the heap you can create a cashe with a limited size, or simply load object to the list only after scrolling has stopped (look to the cm9 music player cover art for one such example). Anyway, to make a long story short you can implement very complex and content heavy lists that run like butter on a arm6 600mhz gingerbread phone, but you can also make those same lists lag on OneX with the wrong implementation.
And btw, project butter DOES use the kernel, it makes use of a custom governor that immediately rumps up the cpu freq to the max whenever there is a touch event.
Stefan Gündhör said:
Yeah that's exactly what I wrote - just in short But I wouldn't call CM7 unstable.
Click to expand...
Click to collapse
I didn't say that cm7 is unstable, but it still has some freezes and random reboots... For example, yesterday I flashed cm7 again, after 2h of runtime I opened the browser and the phone froze and restarted himself... It is sufficiently stable, but I cannot use it as daily rom... And it is also battery hungry...
Ricardo has done a really great job on this phone, but cm7 isn't a rom for my business.. I prefer max stability, so I had to flash a 2.2 rom... GB memory leak is very annoying..
Supupa said:
Cm7 is one of the most stable roms on our phone...
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
"one of the most stable"? Maybe you just haven't tried a good stock based rom... I used cm7 for 7 months and i had a lot of problem...that's because of the closed Tegra2 sources...
markop90 said:
"one of the most stable"? Maybe you just haven't tried a good stock based rom... I used cm7 for 7 months and i had a lot of problem...that's because of the closed Tegra2 sources...
Click to expand...
Click to collapse
What do the closed sources have to do with cm7? It's GB as well and they are fully compatible.
I used CM7 for over half a year, never had any real problems.
ICS and GB are very diferent in the way they interact with the hardware.
Butter smoth stuf on GB is not possible.
This is what Ricardo Cerqueira answered about this:
"Project Butter is mostly about synchronizing gfx composition with the display's actual refresh rate... and Gingerbread didn't have a hardware compositor at all."
Hi
I updated to to 4.0.3 from Gingerbread. I was initially very happy as it felt like a brand new phone.
But now I am facing 2 problems:
1. Video files are really really choppy and it goes out of sync and eventually hangs the phone.... I am using BS Video Player app for videos. In Gingerbread I was able to play even HD (720p) movies quite easily but now much smaller videos are not playing properly. I have tried other (including the default one) players also
Have you guys faced similar problem? Is there solution you could suggest?
2. Camera won’t start sometime. Sometimes it starts and then it works fine.
Is there any solution for this?
I can kind of answer your first question, for some reason some video codec supports are dropped when going to ICS+ (I had a 720p recording of a science experiment that played wonderfully on GB, but couldn't even play on ICS and above). So your solution is third-party video players (I personally like DicePlayer, but all work well).
As for the camera, that's probably a bug in the rom you're using.
Sent from my GT-P7510 using Tapatalk HD
I am using a 3rd party player (BS Player) only, Earlier it played everything fine. Now it's really choppy and tries SW mode after struggling in hardware mode for sometime, then it hangs.... And with default it's always saying that the video can't be played after few minutes.
Soryuu said:
I can kind of answer your first question, for some reason some video codec supports are dropped when going to ICS+ (I had a 720p recording of a science experiment that played wonderfully on GB, but couldn't even play on ICS and above). So your solution is third-party video players (I personally like DicePlayer, but all work well).
As for the camera, that's probably a bug in the rom you're using.
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
saiko7 said:
I updated to to 4.0.3 from Gingerbread. In Gingerbread I was able to play even HD (720p) movies quite easily but now much smaller videos are not playing properly.
Click to expand...
Click to collapse
Some ROMs/kernels use bigger part of the RAM for the apps, on costs of the video recording. As you didn't provide info about which rom and kernel do you use, it would be best to check the source threads of their developers and read what other people write about it
saiko7 said:
But now I am facing 2 problems:
Click to expand...
Click to collapse
That should be a Kernel issue... Some Kernels use some of the available for use with apps removing some useability from the camera. You should check if your free Ram is bigger than 370 Mb. Usually most Kernels with bigger free memory has that problem...
Thanks guys for replying
I am using ICS_4.0.3_MR1-RC4.2_I9000 from here :
http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
3L4CK_5C0RP10N said:
Usually most Kernels with bigger free memory has that problem...
Click to expand...
Click to collapse
How can bigger free memory create problem? or did you mean the other way around?
Is there any lightweight and fully functional that you guys can suggest for my good old GalaxyS i9000?
saiko7 said:
How can bigger free memory create problem? or did you mean the other way around?
Click to expand...
Click to collapse
Usually developers add some more free memory for general use, removing some from other parts of the Kernel used for example by the camera.
But if you only installed that Rom, usually the Stock Kernels don't have that problem. But depends on what Kernel that Rom uses... I don't know.
Is there any lightweight and fully functional that you guys can suggest for GalaxyS i9000?
saiko7 said:
Is there any lightweight and fully functional that you guys can suggest for Galaxy S i9000?
Click to expand...
Click to collapse
I have a Galaxy S+ (GT-i9001) and I use the K^Kernel that has great performance and awesome battery life. But for i9000 I don't know, sorry...
For i9001 there are 3 versions of this Kernel: 360 Mb; 370 Mb & 390 Mb of free memory.
In the 390 Mb version, 720p Video doesn't work also...