Related
Just wondering if anyone has considered trying to get this epic game going on the kaiser with D3D working. I've seen quake and doom in action and thought maybe since quake is pretty much the same engine...
I'm still new on this htc stuff, just lost a palm centro to a cracked screen and man, I'm glad I did. This thing is amazing once you flash it a couple times....
But yeah, I'd like to see that happen and possibly get some multi player action. But at this point i'm just dreaming. If someone is working on this and needs a tester im down for it!
p.s. searched for half life on the forums and got nothing so i decided to post
It seems valve never made a ppc version of their games like id did for theirs..and I don't think they ever released source code for half-life..in order to be ported to ARM. Hopefully a Tegra device can get developers to port more modern x86 games..battlefield 1942 on a ppc would be nice
Here's something you might like:
http://rapidshare.com/files/196752750/qhl.rar
It's a modified version of quake for mobile with half-life textures and maps etc
Hello guys,
I've recently purchased some games directly from the gameloft shop, only to find they run execrably slow.
This got me very annoyed so i naturally tried other games, for testing's sake, with the same results.
Now i've tried this with different ROMs, NRG's latest WM6.5 as well as Natf's 6.1.
And yes, i did apply the Ace game fix on WM6.5
What i really want to know is, am i the only one that encounters these problems? Is there a fix for this?
Built in games like Teeter work flawlessly but any other java or cab game is
It seems just wrong that on my previous Sony Ericsson phones mostly any game would run so fluent, and on my Touch Pro with ram, 500+ CPU and so on it runs like crap, mind the expression.
It sounds like you, don't know how the problem could persist over multiple roms though...
It is strange indeed, not to mention annoying.
I have heard that there are driver packs.
So far i've found a version of the ATI driver linked by a member, the same on i'm attaching in this post, for veridicity's sake.
Could anyone please direct me to any other recommended drivers for my Raph?
Thanks in advance.
I think it has to do with the GPU. The games may not take advantage of it, and rely on the CPU. I also downloaded a game from ATT "Peggle" which I really like, but runs at 20fps or less, very annoying also. I have not found a fix yet, and I'm not sure there will ever be. I've tried the game on a TP2 and same thing.
I'm just waiting for the HD2 to come to the US, and I doubt I will have any problems with the game on that device
Well, guess i can let this die, i've read around and noticed it's a general issue, due to the Qualcomm chip and stuff.
Decided to sell away this piece of junk. GG HTC for awesome support! :|
Since many people asked what I was doing these days:
The Nook Color running a healthy mix of Android 3.1 Honeycomb from the Xoom and Android 3.1 from Google's SDK.
As can be seen towards the end the Launcher application suffers from some drawing issues. The same issues can be observed in Google's SDK 3.1 emulator. The emulator and the nook both are doing software UI rendering instead of the new in 3.0 hardware accelerated UI rendering. Sadly the PowerVR SGX530 drivers that are (publicly) available right now are lacking some features to activate the hardware UI rendering on the nook. (like support for EGL_SWAP_BEHAVIOUR = EGL_BUFFER_PRESERVED
and the GL_OES_EGL_image_external extension). I started patching around those issues, which is hard without the access to the Android source, and can confirm that the nook's hardware is more than capable of running 3.0/3.1 hardware accelerated even though the source might need some patches if we don't get updated drivers for the SGX530.
So the status right now is: software UI with redraw issues or hardware UI with a working home screen but tons of more issues in other applications.
Other than that sound, wifi and opengl works. (no DSP/video decoding so far)
So who's up for solving the redrawing issues?
Possible solutions are:
getting our hands on a newer SGX530 driver than 1.1.16.4061
unpacking, patching and repacking Launcher2
?
waiting until Google releases the 3.1 AOSP source
-Rafael Brune
It sucks but I feel our best bet is just to wait for source. There are a lot of honeycomb tablets slated for release over the next few months, I think once it becomes more widely available we'll see source.
Since we dont know when will be... all the time, effort, and trouble to get it fully working witout source - will be in vain once the source drop happens.
So unless the people involved don't care, cm7 is more than enough for now. We are lucky to even have that, my phone doesn't even have cm7 working for it.
My .2 anyways
Sent from my SCH-I500 using XDA App
The problem is, Google has stated they won't be releasing Honeycomb source until it's integrated with the phone branch. I personally doubt that we see real source until Ice Cream is out.
honeycomb source will never be released, google said so, we'll get Ice Cream Sandwich source which will be awesome on our nook's i'm sure
ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts
@deeper-blue
good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here
Any hope for USB host support with the port or once again not till source
Sent from my Vision using XDA Premium App
deeper-blue said:
Since many people asked what I was doing these days:
http://www.youtube.com/watch?v=RJ_k4kdsaMk
So who's up for solving the redrawing issues?
Possible solutions are:
getting our hands on a newer SGX530 driver than 1.1.16.4061
unpacking, patching and repacking Launcher2
?
waiting until Google releases the 3.1 AOSP source
-Rafael Brune
Click to expand...
Click to collapse
hey THANKS for posting up what you've done and this very cool video... that was just awesome to see how far someone has gotten to get 3.1 running WELL on the nook.
mad props.
Nice work rafael!
Sent from my NookColor using Tapatalk
can't really help you out, but I'd just like to cheer you on
+1 !
Keep up with the excelent work !!!
botossi said:
+1 !
Keep up with the excelent work !!!
Click to expand...
Click to collapse
luigi90210 said:
ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts
@deeper-blue
good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here
Click to expand...
Click to collapse
Completely agree, there are a couple of interesting apps in the market that take advantage of HC and would be great in the Nook.
If you ask me waiting for AOSP don't look as such a good idea, since it's release is not so sure.
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
arrjaytea said:
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
Click to expand...
Click to collapse
He is running 3.1, which he has been working on and has yet to release because of the bugs he demonstrates in the video.
Great work DB, really excited to see the progress on this. I'm just wondering - would it be feasible to run this with ADW or similar as a holdover until the Launcher2 rendering issues are resolved?
Sounds like patching the launcher will be the easiest route. This is why I love you DB ahhaha, your work is amazing.
Hi deeper-blue,
If you want, I can offer you my help. I would be able to try to patch launcher2. I've been able to work out a few stuff in launcher2 when I was doing test builds of HC 3.0 and 3.1.
I'm trying to look if I can find some drivers for the PowerVR SGX530, but I unfortunately can't help by making 3.1 available on AOSP.
Is there a pointer to instructions on how to cook from SDK ? Have been looking around and have not found anything useful.
Wanted to take a crack at the graphics driver portion.
Very nice work deeper-blue.
Don't let the lazy people uninspire your work. If the Android and Open-source community in geral would wait for corporations solutions linux would never have been created. This is the open-source spirit, guys. If you come here to say that open-source hackers should wait, you're on the wrong place doing the wrong stuff.
Back to honeycomb, even before this 3.1 news I was noticing that one of the main limitations we have on honeycomb is the laucher. I suggest that while we can't hack it (but we will keep trying), we use honeycomb with another launcher just for the sake of using the great tablet oriented apps we can't have on cm7.
About the source code, for me Google made clear that they weren't releasing it for a while. So, I think this is more motivation to make a honeycomb daily driver.
Keep up the great work, Good luck everyone and all hail to this awesome community.
--
Marlon Moura
Keep at it man, we appreciate the work.
Unfortunately I lack the technical expertise to help keep this moving forward; however, I think an earlier poster was dead in his argument that waiting for source code is defeatist mentality for the open source "hacking" gurus out there.
I imagine that Deeper-blue could turn this into a truly polished machine....if he had the time to devote endless amounts of hours to this, but who does and that's why he's seeking assistance from other willing and capable hands.
If anything I hope others who are capable find some inspiration in the challenge and ultimately crack this one into something special.
Thanks in advance to Deeper - blue and other who continue to provide users with a cost effective tablet experience.
-Rt
Hi guys,
I just decided to install Honeycomb on my Nook's emmc, but I haven't played with it, other than the fact that the Market's fails whenever I try to install any app?? Any way to get around that? Any link to the newest HC release?
Also I was wondering if the newly released HC 3.2 (On Huawei Tab) may be of any help to the community, being that it is supposedly optimized for 7" tablets.
Thanks guys for you responses, Also a shout-out to Deeper-blue, Divine_madcat and all the devs who are making these ROMS available.
s9pa said:
Hi guys,
I just decided to install Honeycomb on my Nook's emmc, but I haven't played with it, other than the fact that the Market's fails whenever I try to install any app?? Any way to get around that? Any link to the newest HC release?
Also I was wondering if the newly released HC 3.2 (On Huawei Tab) may be of any help to the community, being that it is supposedly optimized for 7" tablets.
Thanks guys for you responses, Also a shout-out to Deeper-blue, Divine_madcat and all the devs who are making these ROMS available.
Click to expand...
Click to collapse
In terms of hardware compatibility, i do not see 3.2 being much help. While the Hauwei tablet is not a Tegra 2 cpu, it is still not the same CPU family as ours, making it still such that we could not port it.
The SDK might be more useful, but i am not too optimistic about that either.
One thing it would fix, is having to use 120 DPI on our nooks. Since that build would be compiled for screens like ours, a more natural setting of 160 DPI should be feasible.
That is a bummer :-( I was hoping that the HC on Huawei was going to be helpful. Well, what is the best HC (less buggy) that is currently available for Nook Color. Any link to the download would be appreciated.
Thanks
First I want to say, I normally don't post until I am pretty familiar with a device, but I have searched enough and played enough, that I hope my questions or posts don't sound stupid.
That said. I have modified many devices, none so much as my phone, and recently decided to say goodbye to stock(or at least keep it hidden on a sd card if I need it) nook.. I have tried every rom I can, and am now trying nightlies of cm7..
But what is the best setup to have the most market showing, and the most compatibility when you do download apps or apks? I know lcd density is a big factor of what will show up in the market, and the settings in build.prop can keep apps like netflix or tegra games from working(which I have fixed), or.. I am sure there is much more. But there is no updated faq thread that points everyone from asking the same questions, or getting the most up to date information
So the questions:
What are all the changes that you can make to ensure you have access on market and/or can run the most apps?
I am willing to do just about anything to my devices, but I would like to learn specifically for the nook what I can change to get the most out of it. Specifically anything that will make it possible to run tablet applications on it.
Flash MIUI. IMHO, your Nook is now perfect. Then fix Netflix.
LOL. Been to miui, done that. IMO if app developers were less afraid of negative feedback, and willing to beta test with a wider audience, or at least provide a downloadable apk.. this problem wouldn't exist.
Till then(sorry, I don't like MIUI), I guess I am lost.
ikingblack said:
Flash MIUI. IMHO, your Nook is now perfect. Then fix Netflix.
Click to expand...
Click to collapse
If by perfect you mean a large phone then yes flash MIUI and use their 240 lcd density
OP:
Most so called tablet applications are Honeycomb only at this point. You shouldn't need to adjust anything to get Market access. If there is anything that folks are doing to get past Market filters then they should tell me.
You no longer have to edit your build.prop for Netflix if your using a release from the last month
Sent from my LG Optimus V using Tapatalk
http://tablified.com/
I came across that today.
I think the difficulty of answering your question stems from the fact that there are so many different variables involved. What works for someone may not work for others based on the ROM, ROM version, other apps, settings, other fixes they have in place, etc. When I first flashed CM7 and then nightlies, I was under the impression that there would be one general answer to getting the Market fixed so I could download/install any apps and run them. Sadly, it doesn't seem to be so and what you do to fix one app or the Market on your device may be a different process than on someone else's device.
hartlogan said:
I think the difficulty of answering your question stems from the fact that there are so many different variables involved. What works for someone may not work for others based on the ROM, ROM version, other apps, settings, other fixes they have in place, etc. When I first flashed CM7 and then nightlies, I was under the impression that there would be one general answer to getting the Market fixed so I could download/install any apps and run them. Sadly, it doesn't seem to be so and what you do to fix one app or the Market on your device may be a different process than on someone else's device.
Click to expand...
Click to collapse
It is kinda sad, but this only seems to be true about the nook color from what I have seen. There IS a fair amount of development going on, but it seems to be almost totally into cm7. Other android devices I have done a fair amount of playing with, unless a problem is hardware based, or someone did something to their OS or an app they have.. everyone is having the same exact experience.. so I guess I expected similar here, but maybe there is just less development.
I guess I was looking for devs to point out the different things they manipulate, why, and what kind of results they get. For instance, supposedly I should see netflix in the market, but I don't. Not with cm7.0.3 or rc1 or any nightly I have flashed, even though there are plenty of posts that say I should.
I have netflix, and it works, but I am wondering what variables go into manipulating these things. Another example is Order and Chaos 1.0.2, a game that only works on a small list of devices, and just updated.. I tried changing multiple things, multiple ways, and everytime it would fail to boot. Turns out changing just these:
ro.product.model=SCH-I500
ro.product.brand=verizon
ro.product.name=SCH-I500
ro.product.device=SCH-I500
ro.product.board=aries
Made the game work again. Fingerprints, what os we are using, and so many other things just kept it from booting.. but the device doesn't seem to see anything differently in market than before.
Anyways, if anyone can contribute some ideas to this thread, what can be manipulated, why, and what to expect, I would appreciate it, even just for the learning experience.
Netflix only shows up in the market for the 16 or so "official" phones. The rest of us have to sideload the .apk.
---
- Sent from my LG Optimus V using Tapatalk
koopakid08 said:
Netflix only shows up in the market for the 16 or so "official" phones. The rest of us have to sideload the .apk.
---
- Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
I found multiple threads(not on xda, maybe that's the problem) that say on the latest cm7 it is supposed to show up..
I have been trying to do research on what I can change in the build.prop to make apps LIKE netflix show up, but what I really want is to be able to download a paid app called order and chaos. I was able to get the app itself to think it was a supported device, but no matter what changes I make, it won't let me download it in the market.
This is not the only thing I want, but this is what I want most of all. If I hadn't broken my samsung vibrant, I could load the apk from it and have a valid licensed game, but unless it is linked to the nook I won't be able to make in app purchases(like buying game time).
This matters because my replacement vibrant is coming in tomorrow, but I am going to sell it asap..