Related
I am aware that this has been asked many many times, but i don't see a thread for this issue. I would like to know what attemps have been made to get some sort of support. I am by no means a developer, but i will try my best to get things running. Would it be something as simple as taking a a file out of a current android phone with the same specs and modding for use with a touch pro.
I'm simply curious if there is a thread or website around that discusses this and other issues in more detail.
I'm no kernel hacker, but I am...curious.
That's what i would like to know. facts about how far the development is. Maybe we could start a thread that has such progress stated. Where only the devs would be able to post, so we can have us a look.
The best you can do is read the IRC logs from #htc-linux. I think I recall reading in the logs that klinux had gotten OpenGL working on the Pro2, even with applications like Neocore (thought they're apparently slow).
You have to be a little bit more clear on what you mean by "open gl working".
I'm the developer who was working on the open gl for the klinux build. Bottom line is that open gl is working, but not with hardware acceleration. We used then nexus one drivers (adreno200) to enable things a live wallpapers. But it's so slow its not even worth it.
Now to get hardware 3d working 100%? a lot more work and testing. lol.
Well is hardware 3d working for any of the current android ports in any capacity?
Also, I'm so used to reading hardware specs in Desktop computer form. But with these phones, the only thing I know about them is the CPU manufacturer, model number, and speed.
Is there a separate chipset that handles audio graphics etc, or is it completely SoC.
I read about recent Android ports on the iPhone, and it seems they already have things like external audio working. Is this because the hardware on the iPhone similar to another HTC Android phone, more so than the hardware in the Rhodium?
awesome thread... actually informative and supportive.
i think what the OP is saying is how can us lowerscale highend users be more involved, perhaps in the debugging, data gathering... we could start a -sub group dedicated to each corresponding issues... bill gates didnt invent windows, him and his crew did. the more the merrier eh?
I have a long running reverse engineering thing going on. I have been looking for more info other than IRC. I would like to put my good skills to work w/out starting from scratch. Any info?
EDIT: I did find this, It has some helpful starting info: http://www.androidonhtc.com/wiki/Get_Involved
This is a great thread! I've been wanting to get in on some of this action. Hopefully this will reduce some of the clutter in Reefer's thread.
I meant to get hardware acceleration working. How far has this come along since i posted this??
Only Diamond / Raphael has hardware 3D enabled so far.
Very limited 3D for "low resolution" could be enabled in blackstone or other devices with workaround but that is somehow meaningless.
phh has tried different combinations of memory allocation but in vain.
so am I... given up at the moment.
mcdull said:
Only Diamond / Raphael has hardware 3D enabled so far.
Very limited 3D for "low resolution" could be enabled in blackstone or other devices with workaround but that is somehow meaningless.
phh has tried different combinations of memory allocation but in vain.
so am I... given up at the moment.
Click to expand...
Click to collapse
Phh recommended to trace down mem locations used by wince and that has been done but it still refuses to fire up once pmem.c is modified.
Recently i got the wince dmesg from my rhod in hopes that a cold boot would show as to how the 3d is being activated but that also showed no results. I get this crap when Manila is launched.
[ManilaToday](34156): ### Launching manila ###
23:20:09 [DISP] DrvEscape::HTC_SET_3D_LAUNCHING_FLAG.
I'm not sure what HTC_SET_3D_LAUNCHING_FLAG is.
The next step would be to make an android app and trace down what the hell the libgles_qcom driver is actually doing to see if it is working properly. If you load up ahi2dati.dll on winmo you can actually use the functions to show crap on the screen so i'm hoping the same can be done on android.
Not sure what else can be done at this stage.
[ACL] said:
Phh recommended to trace down mem locations used by wince and that has been done but it still refuses to fire up once pmem.c is modified.
Recently i got the wince dmesg from my rhod in hopes that a cold boot would show as to how the 3d is being activated but that also showed no results. I get this crap when Manila is launched.
[ManilaToday](34156): ### Launching manila ###
23:20:09 [DISP] DrvEscape::HTC_SET_3D_LAUNCHING_FLAG.
I'm not sure what HTC_SET_3D_LAUNCHING_FLAG is.
The next step would be to make an android app and trace down what the hell the libgles_qcom driver is actually doing to see if it is working properly. If you load up ahi2dati.dll on winmo you can actually use the functions to show crap on the screen so i'm hoping the same can be done on android.
Not sure what else can be done at this stage.
Click to expand...
Click to collapse
Ok, i would love to help out as i have never rly done anything like this b4. What exactly are you doing. How do you get HTC_SET_3D_LAUNCHING_FLAG?
How would i open a .dll, i dont think these can just be opened up to see what they are doing. I am on the dark side of the moon here. I know whats going on, but have no clue what to do to help.
garage_man said:
Ok, i would love to help out as i have never rly done anything like this b4. What exactly are you doing. How do you get HTC_SET_3D_LAUNCHING_FLAG?
How would i open a .dll, i dont think these can just be opened up to see what they are doing. I am on the dark side of the moon here. I know whats going on, but have no clue what to do to help.
Click to expand...
Click to collapse
I actually found HTC_SET_3D_LAUNCHING_FLAG on the wince dmesg. You can do this by doing a pwf dump.txt 0x16a00000 0xFFFF0 in haret. I did it after a cold boot to see if anything is done to the gpu once wince boots.
Loading the dll is easy. just make a simple win32 app and do a loadlibrary. This part works but it's not helping on android. I'm interested to see what mcdull thinks since i think he has ventured a lot into this as well. Right now if we can make a simple app in android to load the libgles_qcom.so directly and trace every step, i think that would be helpful to see where we are failing. I'm close to giving up..lol i already took 2 sick days from work to get to where i am now so i could use some help.
Here is what i got out of the chip in wince.
name: ATI HandHeld Interface
versions: 2.07.05110.34681
Revision: 0
ChipID: 1362104322
revisionid: 0
TotalMemory: 15990784
BusInterfacemode: 2
InternalmemSize: 262144
ExternalMemSize: 0
Surface info: 800x480
surface total bytes 768000
dwFrameBufferPhysical=0x14c00780 m_dwFrameBufferVirtual=0x57e00000 dwFrameBufSize=0xbb800
Most people here could probably not help with the hardcore kernel dev stuff, but I guess if you need memory locations or so (be it for opengl/sound etc) I think there a a LOT of people that are willing to run some apps that dump a txt file with debugging info & mem locations to their SD-card and send you that
I would love to help with developing, even if it means that I have to boot into winmo and android all night long and gather certain information, memory-adresses, try different versions of programs with all kinds of parameters etc.
Star-Lite said:
Most people here could probably not help with the hardcore kernel dev stuff, but I guess if you need memory locations or so (be it for opengl/sound etc) I think there a a LOT of people that are willing to run some apps that dump a txt file with debugging info & mem locations to their SD-card and send you that
I would love to help with developing, even if it means that I have to boot into winmo and android all night long and gather certain information, memory-adresses, try different versions of programs with all kinds of parameters etc.
Click to expand...
Click to collapse
We need more devs in general. I ran a trace on a basic app that runs 3d. So there is still a lot of crap to examine.
I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.
BinaryDroid said:
I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.
Click to expand...
Click to collapse
Sounds crazy.. i love it.
I was messing around today and made a small app to load the libgles_qcom.so directly to see if i can replicate my winmo success. Most of the ahi functions are included in the android driver as well except for AhiDispSurfGet which made it impossible for me to draw anything on screen.
The chip did pump out the same info as i posted before and it matches so thats a step in the right direction. Means we can recognize the chip with no problems and all 15.25 memory is reporting as well. If i had more documentation on those functions exported im sure i can get the chip to try to display something directly.
Interesting bit of info I read and perhaps someone can clarify this here. The Sprint Touch Pro 2 uses the Qualcomm MSM7600 processor. The AT&T Tilt2 (GSM phone) uses the MSM7201A processor. The "A" refers to the smaller 65nm die size (I believe).
From what I've read, some changes occurred on the MSM7200 -> MSM7201 due to patent infringements. The next question is, is the MSM7201A and MSM7600 essentially the same chip, just different hardware for CDMA/GSM?
I guess the "libgles_qcom.so" library is used in many other HTC Android phones, but for some reason it's failing on the touchpro2/tilt2, and we're not sure why (although logically it sounds like the library should work as it's used by other android phones with the same chipset)? I'm no kernel dev (I write .NET/c# apps which are much easier than kernel stuff), but am somewhat familiar w/ linux and perhaps can assist in development..
NewbTrader said:
Interesting bit of info I read and perhaps someone can clarify this here. The Sprint Touch Pro 2 uses the Qualcomm MSM7600 processor. The AT&T Tilt2 (GSM phone) uses the MSM7201A processor. The "A" refers to the smaller 65nm die size (I believe).
From what I've read, some changes occurred on the MSM7200 -> MSM7201 due to patent infringements. The next question is, is the MSM7201A and MSM7600 essentially the same chip, just different hardware for CDMA/GSM?
I guess the "libgles_qcom.so" library is used in many other HTC Android phones, but for some reason it's failing on the touchpro2/tilt2, and we're not sure why (although logically it sounds like the library should work as it's used by other android phones with the same chipset)? I'm no kernel dev (I write .NET/c# apps which are much easier than kernel stuff), but am somewhat familiar w/ linux and perhaps can assist in development..
Click to expand...
Click to collapse
learn haret/haretconsole and take a look a the kernel. good place to start. Feel free to come into the irc board if you have any questions
Here is my freeware game -ads free. Working probably at any resolution, especially tested on my HTC Touch Pro 2 480x800. No big graphics but I think good playability. So download from this thread or game website (search for version 2.5): www.lineapolis.dizzy.pl, play (in game is demonstration and help) and comment it - I wait for your opinion...
------------------------------
2010-08-10: update to 2.5
mrdarek said:
Here is my freeware game -ads free. Working probably at any resolution, especially tested on my HTC Touch Pro 2 480x800. No big graphics but I think good playability. So download from this thread or game website (search for version 2.3): www.lineapolis.dizzy.pl, play (in game is demonstration and help) and comment it - I wait for your opinion...
Click to expand...
Click to collapse
What game is it? How do you play this?
Never heard about such thing
I try explain my game but I'm not native English speaker... Principal game rules are simple. You need draw line by 5 adjacent points. On start it not possible so game rules allow add 1 new point for create line. You have some default set points on start, their number increases with the progress of the game. There is also bonus mode in game - you can store points for future use if you draw line by 5 existing points.
Idea is not new. Before computer times I play this game on boring lessons in school using only paper and pen. But i was not happy - I could not restore my best games, so I create computer version of that game - now I can save games, undo moves, reviews games, found hidden moves e.t.c.
Unique value of that game is that you can play just for fun drawing lines or can play in ambitious style and try get best score.
Peoples don't know my game because is unique in Internet - so many sudokus sokobans and other games for single players but no one has coded my favourite game. So try my game and give me opinion here, might you like it.
Thanks for this, I used to play your java version, but for some reason it stopped working on my hd 2, this works great!
thanks for releasing this as a stand alone cab file
I'm so happy that xda promoting my freeware software At last in win-mo you have nice icon. j2me is not bad language - very strict rules so code are runing fast even on old phones. This is framework version - is fast on fast devices. In j2me I was have trouble programming auto-player, I think you will be like this feature. And in this version at last I got idea how coding bonus mode and doing this!
Whats funny is that I lost my Phone in November, last year, used t oplay your game all teh time. Switched to Android for a while, hated it, came back to WM, flashed an NRG ROM, but was missing your game. Took me a while to find the Java Version, actually found a copy last week, but couldn't get it to work with the Java version I have on this phone. Was quite upset, and just about gave up, until today, that is, when I saw a Tweet about it, on my phone, and imediatly installed it. Still haven't figured out what Bonus mode does, or how it differs from what I am used to. Keep up the good work, and again, I am glad I can play this game again on my HD2. Maybe you can do an animatted GIF to show how this works, I am not getting it from the explination on your web site
The only thing i will say, is that on the HD2, it is a little hard to get the dots sometimes, even after increasing the screen size a bit, so sometimes it takes two or three taps to hit the dot I want. No way around this though, as the HD2 has no stylis. It still works fine, however, and if I am really lazy, I can just cycle through the hints until I find the line I intended, or see another line of interest, that I may have missed.
I will add, you should throw up a donation link, in your sig, or add it to the first post, as some people may want to donate a little token of apreciation...
For those who need an understanding on how to play, I ripped this of your web site:
Maybe you need calibrate screen on HD 2 if you have trouble select point? After adding demonstration game and simple help I think that this gif is no big useful but still OK. Read help and you learn what is bonus mode. Or often use hint and in medium game you can see "can store!" - This is bonus feature. With bonus mode You can get much better score eg my is 135! Or just disable bonus in config and play classic mode like in 2.2 In bonus mode strategy has changed - less thinking how to effectively draw lines - more thinking how get and use precious stored points.
2010-08-08: New 2.4 version released - worth redownload!
Twoja gra podsunela mi pomysl, ze nie widzialem jeszcze gry w popularne KROPKI w ktore namietnie gralismy na kartce w kratke na lekcjach w podstawowce moze cos takiego stworzysz?
I translate it by google translator:
Your game gave me the idea that I have not seen the game in the popular DOT in which we played passionately on a piece of the lessons in class in elementary school: P Maybe this will create?
----------------------------------------------
Hm, what difference beetwen this game and your? Please explain me on mail
PL: A jaka jest różnica? wytłumacz mi na maila, i nie pisz PL na angielskim forum, użyj translatora... L
HELLO Xda !!!
I am a Noob from Germany !!
We all who use Bada Os have a serious Issue with the APPS !! so i want to know whether U guys (the great guys who Ported Android to Bada) can Create an APP for Launching an Android app on BADA powered Devices ! !! (atleast for S8500 and S8530) !!!!!!!!!!!!
PLEASEE GUYSSSS U CAN DO ITTTTTT !!!!!!!!!!!
Try it yourself? You make others happy with that
wilmervanheerde said:
Try it yourself? You make others happy with that
Click to expand...
Click to collapse
yeah ! but I just started with C and C++ !!! so I cant !! only the Experts like XDA can handle this !!
lol why you write random words with capital letters any emulator requires countless hours of developing and does never reach the performance of the original system. and android apps have many rights that bada apps don't have so it would be impossible to run these without adjustments in the app itself. if you need these apps buy android.
shadowkavi said:
HELLO Xda !!!
I am a Noob from Germany !!
We all who use Bada Os have a serious Issue with the APPS !! so i want to know whether U guys (the great guys who Ported Android to Bada) can Create an APP for Launching an Android app on BADA powered Devices ! !! (atleast for S8500 and S8530) !!!!!!!!!!!!
PLEASEE GUYSSSS U CAN DO ITTTTTT !!!!!!!!!!!
Click to expand...
Click to collapse
I don`t think that anybody would develop anything like that but everybody is waiting for Oleg`s release of the Android 2.3.3 for the Samsung Wave, so soon there could be a stable version of Android working on Bada. It works already but with a couple of bugs which make it impossible to use the phone for a long period.
In fact, this could be done with enormous efforts. As on the new BlackBerry PlayBook there will be android application support, it is not impossible from technical point of view. There are two different project for this, one is AlienDalvik (I think this will be on BB PlayBook, but it's just a hunch) and the other is IcedRobot (this one is in the very begining of the project). Google them for more information.
I think the biggest problem for us is the Bada SDK, as it is nowhere near ready to accomplish this big tasks... Of course this is just my 2 cents.
Edit: you can find some information about porting Dalvik here: http://groups.google.com/group/android-platform/msg/a177b156d338c513?
But I'm sure I'll not start it...
OK, just trying to make something else out of the bull**** about how cool would be to have a Dalvik port, can anybody say what API would be missing to have a Dalvik VM as a bada application? I know Dalvik is far more than JDK, but I never seen any deep analysis. Back several years ago I played on some embedded platform to put J2ME there (I do get the difference) and porting KVM to hello world level took me something like a weekend or so. Again, comparing KVM to Dalvik makes no sense but honestly, to say that porting makes no sense, we should at least have an estimate of effort and missing API.
BADA should open up then for its own good
If Samsung ever decides to open up more apis for an android apps emu
it will be best for BADA. Bada doesnt even have PSX, N64 emus like android has.
Im missing out on a lot of exciting apps like the ones mentioned because there is no developer working on these apps for BADA.
If bada ever comes out with an emu for Android Apps then ill be in line
im even willing to pay for it.
As for not performing at native speed thats what they said for the psx and N64 emus on android but look at where they are now.
BADA isnt that different from Android it just needs to open up more APIs to
take up the slack.
Thats all reliant on samsung.
the app could possibly emulate these apis too like calendar etc or what else is missing (dont know what it is). so for calendar just create an empty one...
or (to make the point clear) instead of using camera it could show a picture and the android app would work and just think that camera is not moving
...but i'd really appreciate an n64 emu for bada
If I wasn't precise enough I'll just put that in one question:
What exactly (as specific as possible) is missing in the API?
mijoma said:
If I wasn't precise enough I'll just put that in one question:
What exactly (as specific as possible) is missing in the API?
Click to expand...
Click to collapse
I think you were clear enough, we just doesn't have answer to your question. I barely developed anything with the Bada SDK, just played with the different versions. But I know that there were no sprintf, sscanf, qsort etc. when I tried it. Maybe this is not issue with Dalvik. And I saw that SDL was ported to Bada (even if it's not free and/or publicly available) so big scale ports can be done, but I can't see the developer community which is capable and willing to do it...
anghelyi said:
I think you were clear enough, we just doesn't have answer to your question. I barely developed anything with the Bada SDK, just played with the different versions. But I know that there were no sprintf, sscanf, qsort etc. when I tried it. Maybe this is not issue with Dalvik. And I saw that SDL was ported to Bada (even if it's not free and/or publicly available) so big scale ports can be done, but I can't see the developer community which is capable and willing to do it...
Click to expand...
Click to collapse
I don't think any library functions are to be the problem. Most of them are either easy to replace or source code is publicly available. I rather tend to think what hardware abstraction / OS interface might be missing. It is repeatedly brought up that there is missing API, but noone gives any detail. What I suspect is that missing API is far less important than memory requirements, but it'd be nice if someone actually had a look.
About the community I share the opinion that it'd be difficult to get the right people doing this. There is much discussion on XDA how to bring this forum back to developers, so we can finally see more people working than whining.
There is much discussion on XDA how to bring this forum back to developers, so we can finally see more people working than whining.
Click to expand...
Click to collapse
oh so you think it is so bad to have a lot of testers who are ready to kill their phones to prove that you are working in the right direction???
i noticed the disappearance of the Devs like you, Adfree , larieto(but he is in vacation) , Oleg and others
i still don't get it
Is XDA bad forum for the Devs now???
Best Regards
mijoma said:
I rather tend to think what hardware abstraction / OS interface might be missing.
Click to expand...
Click to collapse
Yep, you can be right. And according to this :
http://justanapplication.wordpress.com/category/dalvik/
"Implementing a large part of what is approximately Java 5 plus a large part of some version of the Android APIs (which version is of course another problem) is not exactly trivial given that many of the Android API methods are actually native methods, or call native methods almost immediately, and they often use Android platform specific features, for example, Skia and Surfaceflinger to name but two. In fact it is quite difficult to see how it can run the majority of Android applications unmodified unless it actually contains what amounts to a largish chunk of, not to put to fine a point on it, Android." (it's about AlienDalvik)
DalvikVM itself is pretty big and it needs a few libs to be able to run .dex files and a lot more to run Android apps. With the bada 2.0 we have approx. 240-250 MB free RAM after boot, if I'm not mistaken. This might be enough for some stripped-down Android libs+dalvik+app as we have around 70 MB for apps when booted into Android... I may try to compille dalvik alone if I had some time...
One more thing: there's a project to port DalvikVM to iOS with some progress: http://code.google.com/p/in-the-box/ so this is definetly not just a dream. In fact they have DalvikVM ported. (video here: http://www.youtube.com/watch?v=fhyd18h_as4&feature=player_embedded)
mylove90 said:
oh so you think it is so bad to have a lot of testers who are ready to kill their phones to prove that you are working in the right direction???
Click to expand...
Click to collapse
I don't feel satisfaction when an unaware 'tester' bricks his phone.
I'd prefer people that would contribute their time and knowledge instead. With large number of people unaware what they're doing and later messing forums with requests/DEMANDS for help we are not getting any further. When I asked for help in relatively simple task of downloading and checking bootloaders with a PC app there was little response.
mylove90 said:
i noticed the disappearance of the Devs like you, Adfree , larieto(but he is in vacation) , Oleg and others
i still don't get it
Is XDA bad forum for the Devs now???
Click to expand...
Click to collapse
Well, apart from me actually working hard in RL for past 3 months, I won't say much about others here at bada forum. Generally, XDA is going through hard times with developers being bashed and flooded with excrements from growing number of people feeling that clicking 'donate' is same as buying someone's time and other groups that think developers simply owe anything to users.
With going further down this path at some point the forum would have to change the name to 'xda-noobs.com' as all the devs would be gone leaving all that whining behind. Fortunately, the mods and admins do care and take actions, so I hope it will stimulate more hard-facts discussions.
anghelyi said:
DalvikVM itself is pretty big and it needs a few libs to be able to run .dex files and a lot more to run Android apps. With the bada 2.0 we have approx. 240-250 MB free RAM after boot, if I'm not mistaken. This might be enough for some stripped-down Android libs+dalvik+app as we have around 70 MB for apps when booted into Android... I may try to compille dalvik alone if I had some time...
)
Click to expand...
Click to collapse
Wait a Minute !!! YOU CAN DO IT ??? Where can I buy the Time for you ?? Man thats an awesome News !!!!!!!!!!! I love to hear that !! !! what about the APIs and the things that other guys are talking about ?? Is it possible to bring it on BADA ??? AleinDalvik??? REPLY MY FRIENDDDDDDDDDDDDDDDDDD !!
Hold your horses as you're simply misinterpreting and clearly should go look up what is Alien Dalvik.
VM is one thing, runtime is the other. While compilation should not take too much time, creating runtime environment won't be that straightforward.
mijoma said:
Hold your horses as you're simply misinterpreting and clearly should go look up what is Alien Dalvik.
VM is one thing, runtime is the other. While compilation should not take too much time, creating runtime environment won't be that straightforward.
Click to expand...
Click to collapse
Yes, indeed! I just wanted to say that I'll check if the core libs could be compiled at all without much modification if I had time. But Dalvik alone is not barely more than having a console based java re...
mijoma said:
Hold your horses as you're simply misinterpreting and clearly should go look up what is Alien Dalvik.
VM is one thing, runtime is the other. While compilation should not take too much time, creating runtime environment won't be that straightforward.
Click to expand...
Click to collapse
let android apps run on non android devices
this is what Alien Dalvik does ,right ??
it runs on N900 !! cant we make it to run on Bada ?? Yes or No ??
shadowkavi said:
let android apps run on non android devices
this is what Alien Dalvik does ,right ??
Click to expand...
Click to collapse
First of all, Alien Dalvik is a commercial PRODUCT, not a general concept. Dalvik as it is does not really require android to run.
shadowkavi said:
cant we make it to run on Bada ?? Yes or No ??
Click to expand...
Click to collapse
When you say 'we' who do you really have in mind? What will be yours input?
If you wish to ask the question in that tone and receive a binary answer, then your answer is No.
Is there any significant difference between going this route and using the emulator?
Will I be able to use all the apps and games I have on my galaxy S and S4 with either or both method?
Anything else I should be aware of I didn't think of to ask?
Thanks
Sigh... questions rightly belong in General, not D&H. Also, this (dual-booting with Android) has been asked, and discussed, a *lot* already.
GoodDayToDie said:
Sigh... questions rightly belong in General, not D&H. Also, this (dual-booting with Android) has been asked, and discussed, a *lot* already.
Click to expand...
Click to collapse
Sorry this appeared to be the spot to ask since it is related to the subject of this section which contains the guide to doing the dual booting. And sorry I did not find the answers to my questions in searching otherwise I wouldn't have needed to post. I don't frequent the forums here enough to have known this topic has been beaten to death. Perhaps if you could please point me to relevant thread(s) that answer these questions or me. Thanks.
StoneRyno said:
Sorry this appeared to be the spot to ask since it is related to the subject of this section which contains the guide to doing the dual booting. And sorry I did not find the answers to my questions in searching otherwise I wouldn't have needed to post. I don't frequent the forums here enough to have known this topic has been beaten to death. Perhaps if you could please point me to relevant thread(s) that answer these questions or me. Thanks.
Click to expand...
Click to collapse
Both of your questions have been answered in the android dual boot thread but I shall answer them again here.
There is a difference between dual boot and emulator. The emulator (I say *the*, there are a few) compatibility is poor at best and performance can only be described as absolutely abysmal.
Dual boot is running natively, it isn't fully hardware accelerated video but the performance of the w700p is so far above that a regular android tablet in the first place that this doesn't matter, its no biggy. But it is running on x86 whereas android is usually for ARM. Drivers for x86 builds are usually poor, although the w700p is pretty well off in that regard (I think bluetooth and GPS are missing, double check the original thread), on the w700p is pretty usable anyway. The google services framework and play store are not open source software though so custom android ROM's (including android-ia) cannot include them, these need sideloading from your device, again check the thread as details for how to do this are in there. After this you can use the play store fine, but some apps will not appear in the store and some may not work at all. Because the device is unrecognised, some apps which are limited to appearing for certain devices (which is one hell of alot) will not appear. Android apps are usually platform independent but some performance critical tasks can be done in a platform dependent way, a few popular 3d games do this, some apps doing this have both ARM and x86 versions of the app but most don't bother because x86 android devices are rare, as such they cannot run.
Also, keep in mind, that just because an app doesn't show up in google play, doesn't mean it will not run on your tablet. If you can't find it in Google play, back it up from your phone (using something like ESFile explorer to backup), transfer to your tablet, and try it. Some still won't function, or only partially function, but lots work fine.
I use Android on my W700, dualbooting, and spend almost no time at all in windows.
SixSixSevenSeven said:
Both of your questions have been answered in the android dual boot thread but I shall answer them again here.
There is a difference between dual boot and emulator. The emulator (I say *the*, there are a few) compatibility is poor at best and performance can only be described as absolutely abysmal.
Dual boot is running natively, it isn't fully hardware accelerated video but the performance of the w700p is so far above that a regular android tablet in the first place that this doesn't matter, its no biggy. But it is running on x86 whereas android is usually for ARM. Drivers for x86 builds are usually poor, although the w700p is pretty well off in that regard (I think bluetooth and GPS are missing, double check the original thread), on the w700p is pretty usable anyway. The google services framework and play store are not open source software though so custom android ROM's (including android-ia) cannot include them, these need sideloading from your device, again check the thread as details for how to do this are in there. After this you can use the play store fine, but some apps will not appear in the store and some may not work at all. Because the device is unrecognised, some apps which are limited to appearing for certain devices (which is one hell of alot) will not appear. Android apps are usually platform independent but some performance critical tasks can be done in a platform dependent way, a few popular 3d games do this, some apps doing this have both ARM and x86 versions of the app but most don't bother because x86 android devices are rare, as such they cannot run.
Click to expand...
Click to collapse
This forum was helpful in getting my HTC One X unlocked, rooted and loaded with CM11, so that is my current set-up.
I managed all that with searching and reading.
I've attemped to find a solution to my currect issue, if I have overlooked the answer and thus created a duplicate thread, please feel free to (kindly) point me in the right direction and close this thread.
CM11 is Android 4.4.4
This is the same Android version as my Samsung Galxy Tab 4.
Having fun with the Jurassic World game on my tab I figured I'd get it on my HTC One X as well, but the store lists my device as incompatible. Downloading and installing the .apk elsewhere results in nothing more than a black screen after launching the game.
I've read somewhere that this is due to opengl not being up to the game on my device.
I've also read that this is dependent on chipsets and the like, which reduces my hopes for being able to upgrade.
Still, I've done stuff now that I never considered possible, and read about stuff here that still far surpasses my understanding. So why not ask:
Is there a way to get my HTC One X up to the task of running this game (and thus other likewise demanding games or apps)?
And if there is, I'd like to rise to the challenge of getting my phone there.