When the phone is finally rooted (it will be rooted!), is it possible to implement hardware acceleration in ROMs for the 3D? How about just the browser?
I am only curious.
I would hope so, it may be as easy as turning it on in the build prop. Even the Optimus S has hardware acceleration via build prop edit. S-off is a MUST!
Related
I am on rooted stock 1.2, netflix app does not properly login or when it does, it plays at like 3x speed, so what can I do to fix this?
You need to update your build.prop file. There are a few other threads on this as I was having the same issue. Sounds like Chipmunks movies...
Here are a few...
http://forum.xda-developers.com/showthread.php?p=14086382
http://forum.xda-developers.com/showthread.php?t=1113348
Hope this helps.
I used the following and it worked...
CM7 nightlys + Android 2.2 ROMs(Stock, Froyo, ect...)
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
Also, I'm not 100% familiar with stock 1.2 and Netflix. I am running CM7 nightlies with Dalingrin's OC.
I finally kinda got netflix to work on my mn'd 1.2, except the lack of video is kind of a bummer. I did the full build prop fix, which got me further than some of the other build fixes. Any thoughts?
n8w said:
I finally kinda got netflix to work on my mn'd 1.2, except the lack of video is kind of a bummer. I did the full build prop fix, which got me further than some of the other build fixes. Any thoughts?
Click to expand...
Click to collapse
I just got mine working, amazingly enough. I had the chipmunk sound issue with no video. Then I updated my build.prop to HTC Vision and it fixed the sound problems, but still had no video.
I found this post: http://forum.xda-developers.com/showthread.php?t=1105681
I left my build.prop as model: HTC Vision and manufacturer: HTC and installed the apk on the first page of the thread, mediaclient-1. It is working great now!
I guess everyone has difference configuration on their Nook Colors. I have rooted stock 1.2. From what I've read it seems to work easier for CM7 users.
My rooted Nook seems to loose the video depending on what day of the week it is. I can get it back by going into Manage Applications and hitting Clear data and/or Clear cache. However, I've yet to loose the video running under CM7 from the SD card.
Running Phiremod 6.2 the market version of Netflix plays flawless, audio & video.A little grainy for first few seconds then picture is great.
Sent from my NookColor using Tapatalk
XerxesMcClain said:
I just got mine working, amazingly enough. I had the chipmunk sound issue with no video. Then I updated my build.prop to HTC Vision and it fixed the sound problems, but still had no video.
I found this post: http://forum.xda-developers.com/showthread.php?t=1105681
I left my build.prop as model: HTC Vision and manufacturer: HTC and installed the apk on the first page of the thread, mediaclient-1. It is working great now!
I guess everyone has difference configuration on their Nook Colors. I have rooted stock 1.2. From what I've read it seems to work easier for CM7 users.
Click to expand...
Click to collapse
I'm also on a rooted NC 1.2 and can't get it to work. I get video but it plays chipmunks. I tried the build.prop change to HTC and HTC vision but no luck. I also tried the media client in the other post but it still doesn't work. *sad*
Hi All,
I've been trying to figure out how to get my CM7 NT to stream Netflix in the HD quality of the stock Nook ROM.
I've tried several edits to the build.prop (ro.product.____ and ro.build.___), to no avail.
Are there any specific lines in the current CM7 Internal build.prop that prevent Netflix from streaming in HD, like how the NT comes originally? Or is it some other issue with the CM7 build? Has anybody on CM7 gotten this to work?
Many thanks in advance.
Unless there's been a development I'm not aware of as of right now, you can't, it has to do with the fact that hardware acceleration isn't fully supported in non Stock ROMs. In addition the stock app is believed to be coded differently for the hardware.
DemonicPhantasm said:
Unless there's been a development I'm not aware of as of right now, you can't, it has to do with the fact that hardware acceleration isn't fully supported in non Stock ROMs. In addition the stock app is believed to be coded differently for the hardware.
Click to expand...
Click to collapse
I wish that part about the stock app was true, but the stock app works identically to the version that you get in the Google Play store. Reinstalling the stock version on CM7 via Titanium Backup gets you the same low-quality video and delayed audio that you'd get on the downloaded app.
But hardware acceleration will be here, it's just taking a little while. We're very fortunate to have Rebellos, a recognized XDA developer, joining the new-kernel project. He says he plans to start contributing to the project in about a week.
Mike_IronFist said:
But hardware acceleration will be here, it's just taking a little while. We're very fortunate to have Rebellos, a recognized XDA developer, joining the new-kernel project. He says he plans to start contributing to the project in about a week.
Click to expand...
Click to collapse
Ah, so it's a hardware acceleration issue then, rather than Netflix<-> build.prop device incompatibility? I thought that was done and fixed in the latest CM7 release?
Also stoked to have Rebellos on board.
i thought cm7 had full HW acceleration- and from using it vs using the rooted nook tablet it DOES play movies Better (i can play/stream a bluray.mp4 file on CM7 Fine, it stutters and hangs using the rooted nook(mx video player streaming over my wireless network for both examples) , it is CM9 that is having problem with the ducati timer conflict with backlight timer....the issue is the hd version of netflix if i remember correctly required the locked bootchain blah blah to get the hd version. not sure if that version will run on cm7 i just installed netflix from googlestore and use that.
chaqfoistylo said:
Ah, so it's a hardware acceleration issue then, rather than Netflix<-> build.prop device incompatibility? I thought that was done and fixed in the latest CM7 release?
Click to expand...
Click to collapse
lenardo said:
i thought cm7 had full HW acceleration- and from using it vs using the rooted nook tablet it DOES play movies Better (i can play/stream a bluray.mp4 file on CM7 Fine, it stutters and hangs using the rooted nook(mx video player streaming over my wireless network for both examples) , it is CM9 that is having problem with the ducati timer conflict with backlight timer....the issue is the hd version of netflix if i remember correctly required the locked bootchain blah blah to get the hd version. not sure if that version will run on cm7 i just installed netflix from googlestore and use that.
Click to expand...
Click to collapse
If that were true, I think we'd already have hardware acceleration in CM9. After all, it would mean that source code for a hardware-accelerated graphics driver on the Nook Tablet was available. The whole reason Rebellos is joining the project is because we lack said source code.
Celtic did fix a video performance bug in CM7, but as far as I know it was mainly related to video playback and decoding, not graphics drivers. I might be wrong about that (I'm not a developer myself, I just follow it closely) but that's what the situation looks like right now.
Like I said, there's no difference between the Google Play downloadable Netflix app and the one that comes with your Nook Tablet. The key difference is the underlying firmware - stock, for some reason, gets HD-quality and synced up sound while CM7 gets low-quality and delayed sound. I've been following this one issue closely since it's my one pet peeve with the custom firmware we've got available. Hopefully, though, the devs will sort it out. They all seem like competent and talented folks.
the problem is 99.9% of the universe apparently for cm9(ICS) uses gptimer 11 for ducati...and the backlight some other timer
the nook tablet -currently- HAS to run the backlight on.....gptimer 11, the devs- i believe- have found a ducati on a different timer and they are working on adapting it to run on the nook tablet, once that is fixed- the cm9 devs will progress faster
Hello,
I've a question concerning the H/W overlay used in Jellybean. I'm using the HTC Sensation and i've to manually disable H/W overlays to be able to play video. As i read on some other forums one of the key features from jellybean is the vSync and Tripple Buffering which made it increadably fast. Now is my question why doesnt this work on the HTC Sensation as i havent encountered this problem on any on the other forums with cm10 build which use the same chipset msm8260. What makes the HTC Sensation so unique that it doesnt work?
Rushed said:
Hello,
I've a question concerning the H/W overlay used in Jellybean. I'm using the HTC Sensation and i've to manually disable H/W overlays to be able to play video. As i read on some other forums one of the key features from jellybean is the vSync and Tripple Buffering which made it increadably fast. Now is my question why doesnt this work on the HTC Sensation as i havent encountered this problem on any on the other forums with cm10 build which use the same chipset msm8260. What makes the HTC Sensation so unique that it doesnt work?
Click to expand...
Click to collapse
After reading your post several times I'm not quite sure what you are asking, it seems like you contradicted yourself.
What I can say though is that on the HTC Desire S running a CM10 based ROM H/W Overlay has to be manually disabled also to play videos and even at that it is not perfect and there are flaws with video playback.
I dont really understand why h/w overlays dont work while on other devices with the same chipset it does work. What can you do/ where should you look to fix this problem?
I am aware that Samsung have yet to release the Exynos drivers, so how well does 1080p video playback and gaming work in 4.1.2/4.2.1 based AOSP/AOKP roms e.g. Resurrection Remix, and is the performance as good as the stock roms? Basically, is HW acceleration available in those roms because i was under the impression that drivers were needed to make use of hardware acceleration. Sorry if this is a simple question.
This has been discussed and asked so many times by now it's not even funny anymore.
Use search next time. And no, HW composer isn't working in AOSP.
Sent from the Matrix
Donnie Sins said:
This has been discussed and asked so many times by now it's not even funny anymore.
Use search next time. And no, HW composer isn't working in AOSP.
Sent from the Matrix
Click to expand...
Click to collapse
I did use the search feature but the most relevant result that i could find was from 2011, so i was wondering if anything had changed since then.
I knew that there are unsolved common problems like No fingerprint navigation or unlock, Builtin video camera dont work.
but what are the specific new issues, like new bugs/unstable/overheating/unworking features for Atrix on CM10?
abbychau said:
I knew that there are unsolved common problems like No fingerprint navigation or unlock, Builtin video camera dont work.
but what are the specific new issues, like new bugs/unstable/overheating/unworking features for Atrix on CM10?
Click to expand...
Click to collapse
Hi.
CM10 with "that kernel" (2.6.39.4) = HWA, camcoder, fingerprint (all working) but the battery duration is very short and some devices overheat and has random reboots.
CM10 with GB Kernel (2.6.32.x) = HWA, camcoder, fingerprint (not working) but battery duration is very nice.
Greetings
Thank you!
I would also like to know if CM9 are having the same problems too, as I know HWA, camcoder and fingerprint are also not working for cm9. Thus it doesn't seem to have 'new' issues for CM10 at all.
And one side question. HWA is invented since Android 3.0 (API level 11), so Can I say even HWA cannot be enabled, the performance is still not worse than that of Android2.3.x version of Atrix due to that issue?
abbychau said:
Thank you!
I would also like to know if CM9 are having the same problems too, as I know HWA, camcoder and fingerprint are also not working for cm9. Thus it doesn't seem to have 'new' issues for CM10 at all.
And one side question. HWA is invented since Android 3.0 (API level 11), so Can I say even HWA cannot be enabled, the performance is still not worse than that of Android2.3.x version of Atrix due to that issue?
Click to expand...
Click to collapse
Overall performance its very similar but not entirely. For example, HD video playback don't work fine than GB because we haven't properly libs to use the gpu decoding power, but the GUI its faster.
Greetings.
P/D: Sorry for my bad english, i'm Argentinian.
Also HDMI audio may not work..