yashsingh1/xdaforums huggingface dataset:
[Desire General] jklondon:
This is crazy but my phone randomly seems to turn itself off (battery OK) and I have to take the battery out to get it back again. Anyone else had this issue? Thanks
[Desire General] DaddyCee:
sounds like a dodgy unit, get it swapped out by your service company or supplier.
[Touch Pro2, Tilt 2 Android Development] garage_man:
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.
[Touch Pro2, Tilt 2 Android Development] MooGoo:
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.
[Touch Pro2, Tilt 2 Android Development] garage_man:
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.
[Touch Pro2, Tilt 2 Android Development] DaveTheTytnIIGuy:
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).
[Touch Pro2, Tilt 2 Android Development] [ACL]:
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.
[Touch Pro2, Tilt 2 Android Development] MooGoo:
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?
[Touch Pro2, Tilt 2 Android Development] Tilde88:
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?
[Touch Pro2, Tilt 2 Android Development] electrikjesus:
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
[Touch Pro2, Tilt 2 Android Development] leepriestenator:
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.
[Touch Pro2, Tilt 2 Android Development] garage_man:
I meant to get hardware acceleration working. How far has this come along since i posted this??
[Touch Pro2, Tilt 2 Android Development] mcdull:
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.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
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 [D: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.
[Touch Pro2, Tilt 2 Android Development] garage_man:
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.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
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
[Touch Pro2, Tilt 2 Android Development] Star-Lite:
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.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
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.
[Touch Pro2, Tilt 2 Android Development] BinaryDroid:
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.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
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.
[Touch Pro2, Tilt 2 Android Development] NewbTrader:
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..
[Touch Pro2, Tilt 2 Android Development] [ACL]:
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
[Touch Pro2, Tilt 2 Android Development] BinaryDroid:
And so it Begins...will find out soon enough if the testpoints for JTAG are the same as the 7200/7500

Got my heatplate warming up now along with my IR rework station and will report back with the JTAG locations as long as the locations work. if not at least we know exactly were each testpoint leads.
[Touch Pro2, Tilt 2 Android Development] matthewpapa:
wow man. thats hardcore

ive done debug **** with smd stuff before, but never on something like this...
[Touch Pro2, Tilt 2 Android Development] veeeee:
Good luck to ya!
[Touch Pro2, Tilt 2 Android Development] BinaryDroid:
Good news! I got all the JTAG testpoints found, the pinout is idententical to the G1, the only difference I could tell was the size of the balls themselves, the 7200 from the G1 was I beleive .04mm and this was .005, slightly larger but the layout and pinout matched EXACTLY. I was able locate and floow many of the other traces to their correct function(usb, serial, camera interface) so at least we know we can use the available datasheet for reference if needed.

Once I get out of work i'm going to mod a data port on the side of the phone to connect the segger too without having to work on it while its apart like the G1, even better that the battery door will cover what i add(20pin IDC header very fine pitch)

Once I verify the connection with my J-link and QMAT i'll post up the pinouts in case any one else with a JTAG adaptor can trace the code. hopefully I can at least see were the buggy drivers fail when they do.
[Touch Pro2, Tilt 2 Android Development] rr5678:
Good work. Now the driver can be debugged

Now I forget what's possible with a JTAG connection.

err....never mind that. Just looked it up :p
[Touch Pro2, Tilt 2 Android Development] [ACL]:
The drivers themselves may not be failing. Right now the kernel isnt 100% so we are missing a lot of stuff that may need to be implemented. I think its more important to know what wince does to activate an manage each piece of hardware. For example we still have no clue what the wince kernel does to really activate the gpu. Id love to find out ..

then maybe tackle SOUND !!!
[Touch Pro2, Tilt 2 Android Development] Reefermattness:
You guys i'm loving this thread, and I linked it from my web page. :) Maybe its the pic of the naked rhodium guts that did it for me, I'm not sure. Keep up the work guys. Im excited to see the progress!

EDIT: BinaryDroid can you fix a G1 I bricked? LOL
[Touch Pro2, Tilt 2 Android Development] sovereignty:
OMFG!!! This is a freakin' awesome thread! thanks, Reefer for pointing it out in ur thread

that picture got me excited in places u don't want to know. i'm more of a hardware guy. i wish i had some of the equipment binarydroid has and maybe i could help... :(
[Touch Pro2, Tilt 2 Android Development] demandarin:
Completely Amazed. Yall Are The Real Deal/Mcoy ;-) The workstation pic is Crazzzy! The Real Live Matrix
[Touch Pro2, Tilt 2 Android Development] nc88keyz:
I say damn....I say goddam.....damn son.....way to go.

break that biotch open and spill all her secrets she hides so well.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
lol.. calm down fellas. we havent written one single line of code yet with the new findings.
[Touch Pro2, Tilt 2 Android Development] nc88keyz:
after getting us hooked on the free drug....most of us have gone to AA now and then you throw this bit of good news for us. Yes we are calm but we need the fix now again....

Its really a great thing and sounds very positive from what i read in the last 3 pages.

All joking aside everything is very much appreciated...I went and looked at the evo yesterday ...Its gorgeous....in fact we can even get a free incredible but probally will hold for the shadow or equal on vzw now. Size is everything :)
[Touch Pro2, Tilt 2 Android Development] BinaryDroid:
Ended up having to work on Sunday to get some extra cash, working off of less than an hour sleep right now lol but only 5 hours today. every time I post a picture I get the awesome responses about my workstation, whats even worse is you guys have not seen HALF of my bench hehe. I do tech work during the day but have my own repair business I run out the basement after work so I have the equipment to repair and replace any part on any board except for POP chips. taking ALOT of pictures as I usually do with all my projects, i'm sure they will interested someone.

Refeer you read my mind about debugging Wince. thats what i plan to do first soon as I get the connection made, I'll try halting the core at specific times and dump the registers values then step through line by line to understand it more. i'm going to be working on this non stop during the day until I get some useful data, can you give me some specific things to look out for? pretty confident I should have it ready to debug tonight. You think I should HALT right after clicking on Haret then debug from their and then step through and see how everything gets setup in memory....then reboot and compare to a wince load? you got any place I can upload memory dumps and trace logs so others can check it out also? i'm not gonna focus on the sound right now since I read we may not have the drivers for android......just drivers in general to compare from android and CE.

I remember someone mentioned we have drivers for the sound but only initialization...is that correct? if theirs any information you guys who are working on the drivers can tell me like actual process name, memory locations I can start at, things like that it would be a TREMENDOUS help. or maybe just link me to the most recent kernel/driver source code and i'll have a look.

One more thing, can someone point me to a stripped out bare bones WINCE ROM? I am running a stock rom now but will do the custom rom while i'm at work here. all it needs to have is a phone and file explorer along with whatever wince needs to run. it'll make my work faster if i have less code to trace through.
[Touch Pro2, Tilt 2 Android Development] Taurmindo:
Energy Android Super Lite ROM perhaps? it's from january but it'll probably work. a stripped rom with only drivers to boot android, so it sounds right at least.. :)
[Touch Pro2, Tilt 2 Android Development] Reefermattness:
Thats the link I was going to give him, but if you actually click on it, there are no files to download. I believe NRG took them down as nobody was using them. There is one on PPCG but it is a CDMA ROM.
[Touch Pro2, Tilt 2 Android Development] Taurmindo:
oh ok, then i'd guess reaching him on twitter would be the best choice. if that rom still exists somewhere, that is.
[Touch Pro2, Tilt 2 Android Development] nevergonnauseth:
what about caulkins stripped roms? i can't post a link but its on ppc under touch pro 2>android development
[Touch Pro2, Tilt 2 Android Development] Xodium:
If he took them down because he was running out of webspace, or he needed a place to host them, I'd be willing to put them up on my webspace. I got an epic load of it with unlimited bandwidth.

(Assuming NRG is okay with it, that is)
[Touch Pro2, Tilt 2 Android Development] [ACL]:
If you have time to jump on the #htc-linux channel on the freenode irc network tomorrow that would be awesome. I usually get in 10am EST and phh as well as other kernel devs might be there as well, but we can definitely work around your schedule. Some of those guys have been working on sound for a long time so they can answer all your questions. I believe there are differences between some rhodium versions so which version are you working on?

The gsm rhodiums are similar to the topaz. This is the topaz memory map

http://www.htc-linux.org/wiki/index.php?title=TopazMemoryMap

Most importantly it looks like we need to trace adsp memory phys=0xAC000000, size=13MB

The CDMA rhodium is somewhat different. I have some addresses recorded but not on me at the moment.

The latest community kernel accessible here

http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm

If there is anything else you need, feel free to PM me.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
BinaryDroid, Can you verify if the Rhod has the same pinouts as the Topaz. I ran into this old post and wanted to see how they compare.

http://xdaforums.com/showthread.php?t=669871

Also i want to see if i can get the wiki updated with any information we find.
[Touch Pro2, Tilt 2 Android Development] BinaryDroid:
I cant verify the Topaz but if they have the same datasheet then and it was traced the same way it should be correct for that model, its nothing at all like the tp2 though as far as the locations and layout.

nothing useful to update so far, i got the connection made but i forgot to trace the mode control pins and the watchdog my segger is not able to halt the core, it does get recognized though so thats a good thing. wont have time until this weekend to retry. i am also going to trace the other set of pins thats are just above the JTAG testpoints but have a nornal 10x2 pinout. it seems like it may lead to the radio though. might as well trace everything we may need in the future for unbrick purposes.
[Touch Pro2, Tilt 2 Android Development] Horace:
Any updates?
[Touch Pro2, Tilt 2 Android Development] mrgodai:
this is probably a dumb question from a noob, but IF we can get hardware Opengl working on droid based on jtag/hardware debugging, is it possible to do the same for WM?
[Touch Pro2, Tilt 2 Android Development] q426669:
I'm pretty sure that Hardware OpenGL is working in WM already...the drivers might suck, and your movie playback might lag, but AFAIK it does technically work.

Please correct me if I'm wrong :)
[Touch Pro2, Tilt 2 Android Development] WoZZeR999:
Yup, GLES 1.0 (and maybe 1.1, not sure) work on WinMo. Gles 2.0 isn't the only thing that won't work for RHOD (don't have the hardware to support it)
[Touch Pro2, Tilt 2 Android Development] hackbenjamin:
soooo

i guess u gave up?
[Touch Pro2, Tilt 2 Android Development] [ACL]:
If you are referring to the original question about open GL, no we didnt give up. I'm still working on it. I can only put about an hour a day or so, but there has been progress.

If you are wondering about the Jtag .. well then i have no idea :-(
[Touch Pro2, Tilt 2 Android Development] kosmarnik:
Awsome stuff, BinaryDroid, that's how its done :D

A newb question, Raphael and Rhodium should have the same chipset/cpu, right?

On paper they seem very similar, so I'm a tad confused as to what they changed to complicate this stuff so much, seeing as Rap port got most everything working including sound and 3d.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
you cant ask these noob questions man.. at least mention you did a quick search so we can at least think you tried to research. You are gonna get torn apart over here if you keep this up.. i think we made the last guy cry .. lol

bottom line is that they arent the same.. dont believe me ? look at the kernel code and you will see :-)

The good news is that we are making slow progress. Learning other way to get around the barrier we have in front of us.
[Touch Pro2, Tilt 2 Android Development] kosmarnik:
You're right. I shouldn't have asked that :D I did look at the wiki before posting though.

I just wanted to say thanks to BinaryDroid...and got carried away :p

Why shouldn't I believe you? Actually, I knew that they weren't the same or it would have been done already, seeing the proficiency of people involved.

I was actually interested in the differences, but should have searched for it :/

Great stuff! Keep it up.

I'd love to help, but I can only hack Perl and do web-dev PHP :(
[Touch Pro2, Tilt 2 Android Development] dmitrik:
anybody have work dump for JTAG?
[General Questions and Answers] _AI_:
Will there ever be any Maemo-based smartphone-MID that will be available for verizon? I have recently become interested in the Nokia N900 and its awesome capabilities. If it were just a linux-based MID then I would get it, however the fact that it will be a phone AND Maemo computer (it basically is a computer) has caught my interest. I've seen the LinuxJournal's review of it and I've been looking at what you can do with it ever since. At the moment i have a Droid on Verizon and am not destined to switch plans nor carriers at the moment, but I would LOVE it if the N900 were made available for Verizon.
[General Questions and Answers] _AI_:
as i said this would rock.....

Sent from my Droid using the XDA mobile application powered by Tapatalk
[HD2 General] HENNESSY.1122:
can someone please help me with the configurations to setup vpn on my hd2...i've looked all over the web and have found no success...
[Nexus One Themes and Apps] sirjoeyg:
Hey guys,

Was looking to see if its possible to place the "Phone" bar at the bottom of the HTC Sense Desire and place it on the Nexus One, WITHOUT having to change the whole UI or rooting my phone???
[Nexus One Themes and Apps] evilkorn:
Unless there is something like that as a home replacement in the market, no.
[Nexus One Themes and Apps] sirjoeyg:
Thanks boss. Any suggestions on what to look it under?
[Nexus One Themes and Apps] bewA:
as far as i'm aware its not possible as its part of SenseUI.

You could try HelixLauncher which allows you to drop icons next to the app drawer like iphone.
[Nexus One Themes and Apps] sirjoeyg:
Thanks bewA. Tried it, its cool but hate that it kills the 3d effect when scrolling my apps on N1.
[Nexus One Themes and Apps] wicked_beav:
Thats why you use HelixLauncher2 buddy and you still have your pretty 3D scrolling
[Nexus One Themes and Apps] sirjoeyg:
You da man. Thanks!
[Nexus One Themes and Apps] kitsunisan:
No, there was a replacement launcher you could use, it had the curved desire bar with phone on one side and browser on the other, but I can't remember who did it. It's somewhere in this forum though.
[Nexus One Themes and Apps] sirjoeyg:
Thanks Kitsunisan. Sounds interesting. If you remember or come across it please let me know.
[Nexus One Themes and Apps] grainysand:
Flash Desire ROM? Heh. I know there's a SweeterHome 2 theme that does it, though.
[Nexus One Themes and Apps] sassyness77:
Well

Okay i know we cant just pull parts of the sense rom onto a stock vanilla rom.

But do you guys believe that it would be worth sacrificing hours and hours of work to finally unlock this possibility? I believe so. I mean adroid is here to stay and if we could somehow create a hybrid stock vanilla rom it would be unreal!!

What do you guys think?
[Nexus One Themes and Apps] x986123:
Kind of impossible. You need the Sense UI framework, which is deep in the ROM, and porting it to Stock is really pointless, because it would turn out to be the Desire ROM after porting it.