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
according to certain websites, the kin ui was made in silverlight. whether this is true or not i dont know. however i just wanted to say that i will be working on a new kin design interface and will be possibly making a website for it if it works okay. all support is appreciated.
Yes, everything points to the Kin menu being Silverlight-based, however, the IEmobile 6 browser on the Kin does not support Silverlight.
possible solution
hmm... maybe i could make the ui in silverlight, save it as a file, and redo the programming in some like visual c++ or visual c#. we need to find out how microsoft did it and retrace their steps our way.
The biggest complication is just that we don't have access to the Kin OS files. If we did, then it would be almost easy to modify what's already there.
I'll try anyway
im gonna see if i can break in...im good at that so this may not be that difficult.
Good luck with that. Seriously, lol.
........... Guys, guys. This stuff is a lot harder than it looks, take it from someone whos worked on this for a long time. ITS TOUGH! We have none of the neccesary codes and system access for a clean succesful break in. Just slow down a little ok.
Good luck to anybody who tries to crack this phone but I would like to mention the fact that if you can jailbreak a itouch does not mean that you can hack into this phone.
BitPim alternatives
Anybody know any good alternatives to BitPim? I need something like it that is centered around the file system. I may have just figured out how to hack this phone, but I need something better than BitPim for it to work.
X-15D9W8491 said:
Anybody know any good alternatives to BitPim? I need something like it that is centered around the file system. I may have just figured out how to hack this phone, but I need something better than BitPim for it to work.
Click to expand...
Click to collapse
I would suggest that you make a thread about your question so people can see your question
Sent from my ADR6300 using XDA Premium App
The Issue
X-15D9W8491 said:
Anybody know any good alternatives to BitPim? I need something like it that is centered around the file system. I may have just figured out how to hack this phone, but I need something better than BitPim for it to work.
Click to expand...
Click to collapse
I believe this is at the core of the issue. There is nothing that can access the "file system" other than what media we store. If there was anything better it would already be hacked. I believe we are going in circles here. If we can get into the "file system" it's hacked.
This is what I know accesses the phone so far(none are hacks):
* Zune software
* Qualcomms QPST(scary)
* KinO(johnkussack's closest to a hack)
* BitPim
Are there anymore to add to the list?
gerrypw said:
I believe this is at the core of the issue. There is nothing that can access the "file system" other than what media we store. If there was anything better it would already be hacked. I believe we are going in circles here. If we can get into the "file system" it's hacked.
This is what I know accesses the phone so far(none are hacks):
* Zune software
* Qualcomms QPST(scary)
* KinO(johnkussack's closest to a hack)
* BitPim
Are there anymore to add to the list?
Click to expand...
Click to collapse
If you're on a Mac, MarkSpace has a Kin sync program. It's basically like Zune software excluding DRM content, but also has a pretty simple browser program to access the folders (not the root folder, where the contact XML file would be found).
There are other MTP explorers out there, that will actually show you the content of the phone. However, in my testing, none of them will allow you to read or write content.
Basically, if the phone is in MTP (default) mode, you only have access to the media, and not to the OS space on it. We'd need a driver to use one of the other USB modes.
ok
ill make a new thread...
Hello poeple of the internet, my name is Alex and I just bought an Samsung Galaxy Tab 3 10.1.I was so happy when I bought it but now I`am a bit upset, because I can't run on this device ''cool'' games like Batman, Real Racing 3, Asphalt ( any version), Need for Speed Most Wanted, and other stuff like this. I am able to install the app, but when I'm openning it it says (name app) has stopped. What would be the reason ? and in NFS MW It is a huge lag, in the home screen, after touching the screen , It simply crashes somehow. The sound is broken , and I can`t even go to settings or back to the Samsung Home Screen, only by holding the ON button at the top of the device.
Please tell me why It this happening to me? And how can I fix this!
P.S : the device has only 3 days.
Hi !
I think this may have something to do with the 'special' specs of our device
It has an x86 CPU (similar to the ones used in PCs) and a PowerVr SGX 544MP2 GPU and that may present a problem to some of the games as out tab is somewhat different
I'm not very sure of anything that i've said above (it is what I think is wrong) and therefore if someone smarter than me comments please follow their advice
I believe there MIGHT be a fix for this in the development section. Please browse that and if you find the fix congrats
Cheers
P.S. This might help
http://forum.xda-developers.com/showpost.php?p=45532966&postcount=4
Nitro_123 said:
Hi !
I think this may have something to do with the 'special' specs of our device
It has an x86 CPU (similar to the ones used in PCs) and a PowerVr SGX 544MP2 GPU and that may present a problem to some of the games as out tab is somewhat different
I'm not very sure of anything that i've said above (it is what I think is wrong) and therefore if someone smarter than me comments please follow their advice
I believe there MIGHT be a fix for this in the development section. Please browse that and if you find the fix congrats
Cheers
P.S. This might help
http://forum.xda-developers.com/showpost.php?p=45532966&postcount=4
Click to expand...
Click to collapse
I'll Shed a little more little on this l As @Nitro_123 said the "special" specs are to "blame" well kinda of.
Apps especially games usually contain native code which is basically code the talk directly to the processor, Intel and Arm processors talk a different language so normally any app you pulled of a phone for example wouldn't run, however intel created a translator library called libhoudini which does the magic, hence houdini I suppose.
Right now the best source of information for libhoudini is the android-x86 google group, do a search for libhoudini and see whats in there, I would assume the Android-IA official sight might have a FAQ about it but i've not checked.
Basically there plenty of things to try and tweak if things don't quite work right
I am looking for a software that can fool my accelerometer to make it things I walk 10 000 steps. I know I can build a small contraption to do it mechanically, but I am looking for a software way to Do it., directly on the android or via my computer with adb
Itadiki said:
I am looking for a software that can fool my accelerometer to make it things I walk 10 000 steps. I know I can build a small contraption to do it mechanically, but I am looking for a software way to Do it., directly on the android or via my computer with adb
Click to expand...
Click to collapse
This seems like a similar question on XDA but nobody ever helped to answer it, so I feel for you on this question.
Mock accelerometer/sensor
Digging deeper into the recent articles on the problem set, this article implies that it can't be done except in an emulator.
Setting Accelerometer Data for the Android Emulator
Digging into much older references,
How to send fake Accelerometer values to an app on a real device?
That article says "Sensor Simulator" will do what you want, but I have no experience with that app, but at least the reference says it works on the device and in an emulator.
But there was some question on whether it works on a real device versus just on an emulated device.
Is it possible to simulate accelerometer motion on a real (not emulated) device?
Thanks a lot for your reply