yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] stephj:
Yes, .NET programs get complied down to CIL, previously MSIL, a stack based, machine independant byte-code or P-Code.

All of this stuff is defined, search the net for "Partition III CIL" for a bit of light bedtime reading.

Use Red Gate's .NET Reflector, to open your HelloWord.exe program, and it will show you the IL code, as well as higher level code, VB C# Delphi etc.
[Touch Pro, Fuze General] xgm541:
I am currently following a few websites to keep my news upto date with my ATT fuze. I have tried just about every single possible solution to get my GPS to work. Disabled aGPS, tried GPSTest, flashed various ROMs, tried various GPS programs, change poll interval to 500 ms, etc, etc.

I have owned this phone for 4 months now and I have yet to get a satellite lock to work. The closest I ever got was GPTtest running showing 6-7 different satellites in view, trying to connect to about 3 of them. I left that running for nearly 2 hours, and no luck. Whats the deal?

Please do not tell me to use the search function because I have searched XDA as well as google, and they all end up in the same place of speculation on why the GPS might not be working, but none of the said methods actually make it work.
[Touch Pro, Fuze General] xhypnotik:
It works man. I ran 6.5 beta with Google Maps installed. Took me to a location I've never been to and back.
[Touch Pro, Fuze General] arvin2212:
xgm541, before using AGPS, do you have the right gprs settings for your phone? Have you confirmed that your gprs works?

Anyway, for the gps, read up on my thread about me finding an alternative way to get a better fix.

HERE:

http://xdaforums.com/showthread.php?p=3514443#post3514443

Also, make sure you flash your radio if possible. Read up on the radio thread and i am sure other ATT users have posted the performance of GPS based on the Radio.

I am not an ATT user, as i am from Malaysia. So i am unable to help you on the AGPS part.
[Touch Pro, Fuze General] LBCta:
I second arvin's suggestion on flashing a radio. If you're in the US, I highly recommend 1.12.25.19, I have AGPS and GPS logging disabled, use GPS Test and always get a cold fix in less than a minute outdoors.
[Touch Pro, Fuze General] st3v3:
yeah ive got no issues with it, used it last weekend in the car and worked perfectly.
[Touch Pro, Fuze General] doctajay:
GPS definitely works. Flash the latest leaked AT&T rom, and just try it out. Don't flash cooked ROMs but the stock leaked ROM. If GPS doesn't work in that ROM then something is wrong with your particular phone. I'm in California and I get locks in under 7 seconds, and I'm using wm 6.5
[Touch Pro, Fuze General] freekquency:
GPS is about all that im unhappy with, on my fuze.

It does work, i placed a 3 stage multicache using only my fuze with googlemaps/GCz last week and everyone whos found the cache say my coords. were almost dead on. (coords were an average of around 20 readings at each site)

My trick (doesnt work fast but it works) is to turn on gmaps let it sit there for

1 min while it gets a lock, then switch to my gps (geocache) program and i have nps. I cannot get any other programs to lock or hold the gps without first running the googlemaps program. And everyonce inwhile as soon as i turn it on ill lock up 10 birds. Doesnt make much sense, and i too have played with all i could find (agps,baud,comport, windows settings etc)

good luck
[Touch Pro, Fuze General] NLS:
GPS works good enough.

I definitely suggest radio 1.11 or later.

Of course best to get the whole 5.05 ROM.
[Touch Pro, Fuze General] cremainsc:
Work great! To nearly perfect location!

I'm using the ATT test ROM and google maps with street view.
[Touch Pro, Fuze General] Sleuth255:
Works better than any phone I've ever owned when the test ROM or a derivative is running the show. Matching radio must be used. I've tested the Ralphael 1.12.25.19 (shipped with test ROM) and the Blackstone 1.13.25.24 so far.
[Touch Pro, Fuze General] freekquency:
Messed around a bit more and got instant 10 sats after changing to

baud rate of 9600 on com4... i guess the windows management of the gps is most of the problem (?).
[Touch Pro, Fuze General] Kepela523:
I had the same exact problem as you. I couldn't get a lock no matter what I tried, I was thinking of going back to the Kaiser. I then decided to change my radio from the .32 to the 1.12, left GPS Test running for about 30 minutes, still no lock.

I was standing on the balcony of my apartment....

Then..... when I got into my car I tried again and I got a lock in under 30 seconds..

Not to insult your intelligence by any means. BUT, are you outside in the open?? Because once you have set those settings that everyone here has asked you to do. It should work.

Here is what I did.

Change the stock radio. I believe this to be the main culprit. 1.12 works good. then set your standard GPS settings to Baud 96**** and to COM 4. Run GPS test in the open, outside.

It should work. I sometimes mess around with the AGPS settings. I mainly leave it off because I honestly have no idea what it is.

I get a lock in under 1 - 2 minutes every time. However, I am having a problem with the speed of the GPS. I use TomTom 6 and sometimes my triangle cursor wiggles oscillating from left to right. I don't know why. and also sometimes it is delayed.

I have yet to find a fix for this, I would be glad if someone can please help. I'm not sure if this is a video problem or a GPS problem.
[Touch Pro, Fuze General] cparkhorn:
Worked Both Ways

I've had my Fuze since just before ATT released them, and the GPS worked fine for me, once I could get a signal, obviously a big issue. I followed all of the GPSidfix cab etc and they helped, had to load GPS Test to prime, once it got a full lock and said running I could use Google, TomTom 6 or Livesearch and get instant locks.

I don't flash ROMs, but finally broke down and put the ATT Leaked Rom on my Fuze, and bammmmmm. GPS is almost instant in every single one of those applications, we're talking 2 or 3 seconds when I'm outside. I get locks in my house when I'm by the windows as well.

I haven't driven today, so I can't speak to lag etc or other issues, but once I knew the lag it never bothered me that much. Overall, the new ATT Leaked ROM has been awesome for GPS.
[Touch Pro, Fuze General] freekquency:
i never changed my radio, am using the stock radio on a fuze bought 1 1/2 months ago, i disabled agps and am using com4 baud 9600 super fast gps now.
[Touch Pro, Fuze General] LT2009:
GPS Position Lag w/ internal (built-in) GPS receiver

I can second or third... that.

Firstly, I don't mean to invalidate any previous comments, posts or fixes, or insult anyone's intelligence. I just merely report my VERY UNSCIENTIFIC findings.

I've had my ATT Fuze (HTC Touch Pro) for about 3 months now, and I've tested various GPS apps in the quest of finding out whether the hardware is the one to blame for the GPS POSITION LAG. I'd like to share my personal findings so that it may help others.

The ONLY GPS application that I can say that come very close to NOT having GPS POSITION LAG is Mobile Navigator 7.3.1 (build 137). On top of that, this version of Mobile Navigator is the only one so far to be ALMOST right on when the destination is reached. Other applications that I've tried always show the destination is 2 or 3 houses down the street.

The following applications I've tested all have position lag: one previous version of MN7, IGo8, TomTom 7, iGuidance, Garmin XT, and NDrive.

Did I use the registry tweak as suggested in previous post and did it resolve the lag?

Yes, I did try the tweak. But personally, I don't think it solved the problem.

Did I change to different ROM or Radio?

No. Everything on the phone is stock ATT Fuze.

So, is the hardware or HTC the one to blame for the lag?

Sorry! YOU have to come to the conclusion on this one.
[Touch Pro, Fuze General] apl:
I have a related problem, with the GPS device freezing (?) at high speed. I drove recently in Germany, and up to 120km/h my navigator (HTC-TP + Destinator 7) worked fine. When I drove faster it just stopped tracking, and resumed when I slowed down below 120km/h resumed.

Anyone experienced that or has an idea how to fix it?
[Touch Pro, Fuze General] pyraxiate:
TomTom7 also isnt working perfectly for me. It seems to be about 3-5 seconds too slow. It shows me at the street after I have already passed it. I made the registry setting changes that were posted earlier and will test the lag this afternoon ( it may be the Polling Interval being set to 1000 vs 100 i hope. I will report back to say if it has helped :)
[XPERIA X1 General] chongbh:
Guys,

Anyone tried the above found in the Rom Development Section of this forum?

How is the feedback and is it worthwhile to use this ROM instead of the default WM6.1 R2AA?
[XPERIA X1 General] khalilsemaan:
awesome

i am trying it now and its just great!

coul be a little slow in some places but i have never had to soft reset for any reason i didnt invoke ;). its surprisingly stable and compatible with everything. i was even able to sync with activesync and also my emails even though ppl complained about these 2 issues.

Best thing abt 6.5 is its user friendlyness (honeycomb) and that its way more finger friendly than 6.1 (kinetic ihphone like scrolling EVERYWHERE - even in programs,,,, and larger better looking buttons also EVERYWHERE!!)

be sure to flash hardspl first and enjoy this great ROM!!
[XPERIA X1 General] chongbh:
Oh, thanks for your feedback.

It seems great too and I am tempted to give it a try though.
[XPERIA X1 General] chongbh:
If I want to flash back the stock ROM, does that mean that I need to download the stock ROM image from the HardSPL thread and do the same image updating.

After it has been updated then update the ROM via SEUS to the latest R2AA ROM?
[XPERIA X1 General] theredundant:
Hey fellow Singaporean :P

I'm using the itje's 6.5 Rom. I love it. Prefer Titanium than the TouchFlo. Though I wished WinMo would've put an options on how to view the menu. I prefer normal grid alignments than the honeycomb. But all in all, love the rom.
[XPERIA X1 General] chongbh:
Hi, you are a Singaporean too. :D

Thanks for your feedback.

I am doing the ROM update now so that thread do not have the titanium, right?
[XPERIA X1 General] theredundant:
It has what it states in his thread just like in his screenshots.
[XPERIA X1 General] chongbh:
Thanks. I forget how to install the theme?

And which folder I have to put in so that the WM6.5 able to read the background pictures?
[XPERIA X1 General] randolph2000:
just installed it few hours ago.. the today screen is somewhat laggy.. applications are somewhat hard to reach. wm 6.5 dont have weather and programs tab for commonly used apps.. having problems with active sync (email)

my rating would be 6.5/10
[XPERIA X1 General] theredundant:
I just have mine put in "My Pictures" or something and it'd auto detect. I just changed my wallpaper though.
[XPERIA X1 General] chongbh:
Oh, what wallpapers you using cos I want to change the default wallpaper too, thanks.

I have seen someone posted a thread here on Xperia wallpaper but when I put into the phone, it is not able to detect either a theme file or a picture file, not sure any step I have missed?
[XPERIA X1 General] chongbh:
I found out that there is the battery indicator bug as it is not updating the status from the battery so decided to go back to original R2AA ROM first.
[XPERIA X1 General] akp99:
Why do we need a separate thread to discuss this? I've suggested a potential fix for the battery bug in the official thread...
[XPERIA X1 General] chongbh:
Sorry for the duplicate thread as I am trying to gather some response and help from those who have installed the same ROM.

I have reply you back for the location of the battery indicator fix?
[XPERIA X1 General] stormlv:
Ahh I had it but I kinda hated it...

Its laggy everywhere and I really really hope that Microsoft won't release the OS as it is.

I'm changing back to nX1i 1.04...
[G1 Android Development] macpod:
Hey folks. I put some instructions up that state how to make a G1 Serial to USB adapter. This could be handy for kernel hackers and could be modified too for other purposes which I plan to explore... :D

http://www.instructables.com/id/Android_G1_Serial_Cable/

Enjoy, and please leave comments on the instructables website if you see something wrong or confusing!
[G1 Android Development] damnoregonian:
CMOS vs TTL levels can mean the difference between a functional device and a dead UART.

anyone know if it's actually 5v tolerant or does in fact require CMOS voltage level?
[G1 Android Development] macpod:
I can tell you the G1's pins output 2.8v. I think I would stick close to that. The only reason I used the 3.3v cable is because I have seen pictures of a cable an actual android dev has allegedly used 3.3v levels.

Did you find the instructions confusing since I claimed CMOS-TTL? I actually switched it to just say 2.8v levels now to be safe. I guess saying TTL was a bad word choice since it can go up to 5v although I do specify you need a 2.8 or 3.3v serial to usb adapter in the required materials section.
[G1 Android Development] lbcoder:
Nice.

Next step is to disconnect the console and allow control of rs232 devices from the phone.
[G1 Android Development] macpod:
Working on it ;) You need to disable H2W and PIQ AFIK.
[G1 Android Development] damnoregonian:
ya it was the TTL that made me second guess.

I have several TTL level uarts that will smoke CMOS level inputs. I wasn't about to try one of them unless you had said you did with no problems.

2.8 is odd, but i imagine it's still some form of low voltage MOS and can handle 3.3v without problems.
[G1 Android Development] axou:
Thanks for the great tutorial !

I've compiled a kernel with CONFIG_TROUT_H2W, CONFIG_MSM_FIQ_SUPPORT and CONFIG_MSM_SERIAL_DEBUGGER unset

I understand that the UART port appears as /dev/ttyMSM2, however I can't measure anything on the TX pin when sending data from the Dream, i.e :

echo "Hello" > /dev/ttyMSM2

Have you succeeded in transmitting data in any direction ?
[G1 Android Development] macpod:
What are you using to measure? A multimeter isn't going to work.. you would need a scope.. or serial device of compatible voltage levels able to run at the g1's baud rate.

I didn't have a build env setup on my computer and I only got everything setup/compiled last night because of the cupcake merge into master (I might post instructions on how to build everything before the march 18th merge if there is interest).. so I haven't had a chance to disable the debug console/etc and test yet. I plan to work on that tonight and tommorow.

Some interesting things I have found sofar and questions if you guys happen to be researching this stuff:

-Booted normally you get a "debug>" prompt. ps works.. but I haven't researched what other commands are possible. What have you guys found?

-With the phone powered off, if you plug the serial cable in and read it, it tells you the charging mode and some other characteristics/etc.

-The engineering spl has a serial console you can send commands to. I haven't research what commands are possible yet.. again, what have you folks found?

edit: I bet if you attached a piezoelectric speaker between the tx and gnd pins.. then piped /dev/urandom to /dev/ttyMSM2, you could test that way too.. but that's unconfirmed.
[G1 Android Development] axou:
Thanks for your answer, I was measuring with a scope.

I'll try again with a default msm_defconfig'd kernel and see if I get a console.

Looking forward to hearing of your tests !
[G1 Android Development] viperbjk:
Not only the engineering spl has that. You can use either usb or serial to talk to the interface. What is more interesting : Serial lets you talk to the radio directly (oemsbl) and outputs debug info. Access to all commands is only given using engineering spl and security unlocked device. The commands however are already in the wiki.

Totally confirmed. Sounds just like a good old modem :)

Cya,

Viper BJK
[G1 Android Development] macpod:
Ok, taxes put me on hold.. but I'm back and have it working. Here is the config file I used to compile the kernel.

Speed is set to 9600 8N1, the G1 serial device is /dev/ttyMSM2. If you were curious, /dev/ttyMSM0 is bluetooth related.

I'll post up instructions later on how to compile and install it as well as a boot.img for convenience if folks are interested.
[G1 Android Development] gourneau:
Great, thanks a lot for all your contributions! I am looking forward to your instructions.
[G1 Android Development] viroos:
Hi all xda users :-),

Thank you for your work macpod.

I am looking forward to your instructions also.

TIA

regards,

Maciej
[G1 Android Development] hoepfel:
I would love to get a boot.img as well, I'm not very skilled with all that and only want the serial console to interface the G1 with my Arduino.
[G1 Android Development] cyanogen:
Just ordered the parts for this. Thanks.
[G1 Android Development] hoepfel:
Okay, I got it working! Instructions are for Ubuntu only, sorry. I believe you need a rooted phone with engineering (or hardspl or comparable fastboot-enabled) bootloader and macpods serial to usb cable (or something comparable).

1) Compile Android source with Dream-specifics as described by this. You probably only need prebuilt and kernel, but I'm not very familiar with git and just got everything.

2) cd into the kernel directory, copy macpods serial9600config from above as .config there

3) "make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi- oldconfig" I don't remember if this asks for anything at all, if it does, go with the suggested answers

4) "make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-" - You now have a kernel image for Android 1.0 (I think), but for me it works with JFv1.51 as well

5) You can now compile fastboot in $ANDROIDSOURCE/system/core/fastboot or grab the precompiled binary from http://android-dls.com/files/linux/fastboot

6) Hook up your phone, power off, start with camera+power. Press back when the skating androids appear to switch to fastboot mode.

6) Do ./fastboot boot $ANDROIDSOURCE/kernel/arch/arm/boot/zImage and wait. This takes a moment, then it should start.

You know should have /dev/ttyMSM2 which you can echo into (echo "hello world" > /dev/ttyMSM2) or listen to (cat /dev/ttyMSM2). For instance, I'm building an Android app that passes GPS coordinates over the console to an ArduPilot board and will provide telemetry to a ground station. Testing it with "Serial port terminal" from the Ubuntu repository works as well (remember to choose 9600 bauds and the right port).

Thanks to to macpod for his excellent work and help with building the cable, Google for providing such a kick-ass (somewhat) open phone and all the kernel hackers and rooters for their work.

I just wrote this from the top of my head, just post if you have trouble getting this to work.

edit: I attached my kernel image, which should allow you to skip steps 1 - 4 if you're so inclined.
[G1 Android Development] rigamrts:
do you guys think this will help all the bricked devices? just a question i don't have a bricked device to test but would be nice if did
[G1 Android Development] linkmaster_6:
So let me get this straight? The cable allows direct access to the motherboard and all the hard were in it? Sorry i am a complete noob
[G1 Android Development] hoepfel:
Well, I don't know nothing about bricked devices, but if you can still get them into fastboot mode, you can flash every partition on the phone, so you should be able to resurrect it.

The cable normally allows you access to a debug console (you see kernel outputs while booting, then get a console). I don't know what that is for (maybe USB debugging for developing apps, dunno. I read somewhere that you can directly access the GSM chip, issue AT commands and the like). You'd need to look into that. And with a custom kernel you get a regular serial console trough that extended USB port on your phone, just like telnet'ing into your phone or whatever. Normal unix stuff. And this console can be accessed from Android apps as well.
[G1 Android Development] aggtrfrad:
do we know what config options/boot options should be used, so we can receive the kernel output while it loads from serial?
[G1 Android Development] spiritplumber:
It seems to work for me but it turns off wifi and the sd card. Is this intended behavior?
[G1 Android Development] hoepfel:
I guess it's got something to do with the Kernel being for Android 1.0 and your OS likely being Cupcake... One probably could compile a current kernel instead, but I couldn't be bothered so far. And yes, I do get the same behavior.
[G1 Android Development] virdi:
First, thanks to macpod for starting the fire...

Second, I am also interested in G1-Arduino interface... keep us posted here...
[G1 Android Development] virdi:
@cyanogen: I am so happy to see you getting into this... I am an Arduino developer and can some real great things once we get the Arduino-Android interface working...
[G1 Android Development] hoepfel:
I did get Arduino to G1 working. There are instructions in this thread, what else do you need to know?
[G1 Android Development] virdi:
Android-Arduino interfacing

I read your instructions (The "it" in "Okay, I got it working" made me miss it). Thanks for sharing! I have couple of questions as I have never compiled Android from source. All of this may not make complete sense as I am still trying to understand...

1. Are we recompiling just the kernel or something else too? If yes, does it mean this can't be done on custom ROMs? (Cyanogen, JACHero, JF).

2. Once we recompile the kernel or fastboot, how can we transfer/flash the binaries to the phone?

3. Is it possible to know exactly what OPTIONS were changed/added in the attached config file (which I suppose is used by the compiler to specify options while compiling the new kernel). I guess we can request custom ROM hackers to include those changes in their respective ROM kernels.

Thanks in advance!
[G1 Android Development] hoepfel:
1. Are we recompiling just the kernel or something else too? If yes, does it mean this can't be done on custom ROMs? (Cyanogen, JACHero, JF).

-- Well, I compiled a complete Android 1.0 source because it seemed easier, but I'm only using the kernel. The kernel, even though it's old by now, still works with JF v1.51, so I'm assuming other builds should be fine as well. But note that some features (wifi, sdcard, netfilter...) may not work because we're using macpods kernel config file.

2. Once we recompile the kernel or fastboot, how can we transfer/flash the binaries to the phone?

-- I do fastboot via ./fastboot boot [androidsource]/kernel/arch/arm/boot/zImage jfboot.img-ramdisk.gz , but am not sure if it's even required to give JFs ramdisk image as parameter (it's optional). This boots the phone once with the different kernel and doesn't flash anything. To make changes permanent, you would need to look things up.

3. Is it possible to know exactly what OPTIONS were changed/added in the attached config file (which I suppose is used by the compiler to specify options while compiling the new kernel). I guess we can request custom ROM hackers to include those changes in their respective ROM kernels.

-- Very true. There should be the used kernel config in /proc/config.gz (or similar, this is what I remember from the top of my head) on your custom ROM. And you can diff that against other configs. But I guess the smartest thing to do would be diff'ing macpods kernel config against a stock 1.0 kernel config to collect the necessary flags, then add those to a current kernel's config file.

I'm in a little rush right now and can't look up the details, but keep the questions coming, I'm really glad to help!