yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile General] shkauf:
On my device all the fields are non empty, I have Touch HD with EnergyROM Titanium 21892 (cooked TBattery 0.60).

Unfortunately I could not find the description of those fields. What is the difference between "MS Percentage" and "PA percentage"? What are "KADC" , "RARC" and "ACR"? Is the battery ID a resistive value that is measured with adequate resolution to provide a unique ID (I would expect the series resistance of the LiIoh battery to be in ohms, not Kohms. Clearly this field is not the calculated series resistance but rather a battery ID)? Does the "Cycle" field count full discharge cycles (since last battery insertion or archived per battery ID?)?

Where can I find the TBattery 0.60 documentation?
[G1 Android Development] SimPRoBer20:
Does anyone know how to emulate a .zip rom file?

im reaally curious to know how to develope my own roms

and MAD props to all our current devs for doing awesome jobs at porting new roms daily. really appreciate that.

IF anyone can help with the above question itd b greatly appreciated!!

ill b sure to contribute to the daily slew of roms as soon as i get this process down pat
[Windows Mobile Apps and Games] mercuryzzz:
Here an Italian Translation for Sense 2.1, that fixes worng and bad translations and sentences too large for landscape mode. Give me some feedbacks! Thanks to all.

Installation: copy file "Traduzioni migliori.cab" in device, go to Explorer on device and run it.

Ecco a voi la mia traduzione italiana per Sense 2.1, che corregge alcune errate e brutte traduzioni e frasi troppo lunghe per la modalità landscape. Fatemi sapere! Grazie a tutti

Per installarla, semplicemente copiate il file "Traduzioni migliori.cab" sul dispositivo e quindi avviatelo dal dispositivo tramite "Esplora file".

​

__________________________
[Windows Mobile Apps and Games] etoy:
thanks a lot! i'll try it right now and leave you a feedback soon :)

--

grazie mille! lo provo subito e ti faccio sapere come va.. :)
[Windows Mobile Apps and Games] etoy:
sembra fatta molto bene,bello anche "registro chiamate" abbreviato a "chiamate". molte frasi obbrobriose sono finalmente corrette,come l'ormai famoso "trasc elem per ridisp" :) man mano che lo uso controllo bene tutto,se c'è qualcosa fuori posto te lo segnalo! gran bel lavoro intanto..
[Windows Mobile Apps and Games] mercuryzzz:
"Registro chiamate" era troppo lungo per la modalità landscape, quindi l'ho dovuto accorciare per forza.

Grazie per il feedback

"Registro chiamate" (Call history) was too large for landscape mode, so I used "Chiamate" (Calls)

Thanks for the feedback
[Windows Mobile Apps and Games] teorouge:
Thanks for the translation, but in "Contatti" tab I have no contacts and I see "Aggiungi ai Preferi"... "ti" is missing! Or did I screw something up? :D
[Windows Mobile Apps and Games] mercuryzzz:
Ho controllato e la scritta è completa, "Aggiungi a Preferiti". Se non hai aggiunto contatti ai Preferiti è normale che tu non veda nessun contatto, ma questo non c'entra niente con questa traduzione

I checked and that is complete, "Aggiungi a Preferiti", no missing. If you didn't add contacts to Favorites, it is normal that you don't see any contacts, but this doesn't depend on the translation
[Windows Mobile Apps and Games] teorouge:
Thanks, I know it isn't translation-dependent: I just installed my latest testROM and of course I had no contacts, just wanted to point that out in case you already have any "Preferiti" set! ;)

Ok then, if you say it's correct, maybe it's due to a different font I use in Sense (Segoe UI, by the way).
[Windows Mobile Apps and Games] etoy:
is that one very different from sense 2.5? i'd like to correct some similar strings there (same translation errors)
[Windows Mobile Apps and Games] mercuryzzz:
I don't know, I never tried translation on Sense 2.5
[HD2 General] Ante78:
I updated yesterday to 1.48.413.3 Swe and installed this morning TCPMP 0.72 this morning, when i did that i noticed that the screen lock disspeared.

I deleted the TCPMP from SD-card but that didn´t help.

Any ideas someone?
[HD2 General] Som30ne:
Happened to me after upgrading rom.

Nothing helped but the simplest thing :

Hold Down the power button,

when the menu appears - select lock device.

Tap the power button again,

slide the slider.

The device should show the slider now on every wakeup (as it was in the original state).

(If this does not work -

try the registry tweak -

Go to HKCU\ControlPanel\Keybd and change DeviceLockWhenSuspend to 0
[HD2 General] Ante78:
It worked, thanx
[General Questions and Answers] ink718:
Can someone please post the "soft reset" application that NRG is using in his roms...
[General Questions and Answers] aseem123:
here ya go!
[XPERIA X1 Q&A, Help & Troubleshooting] royalbloodvi:
I once saw a thread here, and I think it used the windows mobile slide to answer and slide to ignore.

The answer slider was green

The ignore slider was red, and u slide it horizontally.

If anyone knows anything about this, please let me know.

I find X2 dialer way too laggy (I am using stock X2), and hard to find contacts. Even the the default WM skin is faster and better.

Anyway, it was a cab file that enabled that skin, and it also changed the keypad a bit better than WM dialer.

Thanks!
[XPERIA X1 Q&A, Help & Troubleshooting] jackleung:
It's not from WM built-in but HTC. Search for blackstone, Topaz, or Rhodium dialer.
[XPERIA X1 Q&A, Help & Troubleshooting] royalbloodvi:
I just heard from someone that WM 6.5 has slide to answer, but hwo do I activate it?
[XPERIA X1 Q&A, Help & Troubleshooting] hofo_mofo:
To be honest, you cannot go wrong with this one

http://xdaforums.com/showthread.php?t=442154&highlight=dialer

I know you said there is a function in WM 6.5 which has the same thing...but I think this one is the best

The only thing I would love to see changed (and I know exists just can't find it), is the HTC dialer but when during a call has two buttons; a big button for key pad and a big button for end call...but still it's all good and am happy with this one
[Touch CDMA Android Development] jnadke:
I created a new thread for this because the old one was for development, and there's no more development :D :D

I finally decoded all the information GPS is providing, and updated the drivers to provide full GPS support.

Rootfs link below for those running from SD or NAND

This thread is for people who want the latest and greatest! As ROM builders integrate these libraries into their ROMs, you shouldn't have to come back here. GPS 5.0 is likely to stay, as I don't foresee any bugs.

Check out the old thread as well. Shidell put some work into an ADB how-to:

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

Rootfs with libgps5.0already pushed in (fixed some file permissions in this version and verified libgps is in there):

http://dl.dropbox.com/u/58383/rootfs-libgps5.0.zip

NBH (thanks jamezelle!):

http://5d698f86.linkbucks.com/

zImage and libgps.so attached! Rootfs above!

INSTRUCTIONS (SD): Replace your zImage and rootfs.img with the ones provided and reboot! (Put them in the android directory).

INSTRUCTIONS (NAND): Flash the new NBH. Then either flash the new rootfs.img, or adb push the library to your /lib/donut, /lib/eclair, and /lib directories.

Bugs remaining (I don't feel like hunting them down):

* Satellite reporting is finicky (this is an issue with the gps messages themselves). Satellites disappear and come back randomly. Only way to fix this is put in a state machine that combines satellite messages over multiple seconds. Also you'd need to prune satellites that are old. I implemented one, but had crashing issues so I ditched it.

* [Fixed] After booting, the first time you try to use GPS with Google Maps/Nav, it will fail. Exit out and re-enter and it will always work from then onward.

Changes:

-2.2: Fixed 'no position in maps/nav on first try after reboot'

-5.0: Fixed issue with negative altitudes, also rebaselined versioning to match versioning inside the software

For maximum compatibility, make sure you're running a 3.42.50 radio (CDMA):

http://forum.ppcgeeks.com/showpost.php?p=389964&postcount=8

Radio-only nbh that won't mess up your NAND.

Most newer NoMoRootfs (andboot) builds should already have this cooked in!

Kaiser zImage:

http://dl.dropbox.com/u/58383/kaiser_zImage.zip

(also any of dzo's newer zImages work)
[Touch CDMA Android Development] tatnai:
i was using the previous zimage from 1/23/10 with rootfs 1/26/10 through sd card ext2. worked great. before that, I used the 1.4 version (the one before 1.5) without any problem (pushing the libgps.so).

however, with the 2.1 zimage and rootfs, the sattelite does not appear at all, after entering and exiting maps/gpstest numerous times and rebooting. any clue? going to try a few things (maybe will try pushing the libgps instead, or the old zimage) to see if I can sort it out.
[Touch CDMA Android Development] jnadke:
You can try this one that uses a constant accuracy like the old ones to see if that fixes it. You'll have to push it.

The new lib uses 64-bit location values, which are much more accurate than the other things (this isn't causing your issue). The new one also uses different accuracy reporting, which android may not like.

Others: The above files definitely work, please don't use the attached.

Edit: Looks like I wasn't actually pushing libgps.so into rootfs! Don't use the below, it fakes the accuracy.
[Touch CDMA Android Development] jnadke:
[Removed file]

I may have figured out what's causing the "no position lock on first try after reboot" problem. I put a fix together, it worked, but crashed the phone. I'll debug it later.

Tatnai's problem may be related. I'm assuming AGPS isn't working on his phone and that's causing the issue.
[Touch CDMA Android Development] JacenSolo2001:
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
[Touch CDMA Android Development] jnadke:
Yup, just put it in the android directory.
[Touch CDMA Android Development] JacenSolo2001:
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
[Touch CDMA Android Development] jnadke:
Whoops, I think my script was never actually pushing libgps to rootfs. I just looked and the timestamp is old. It may have been storing it in data.img. This means you're probably actually using the old libgps + new kernel = does not work.

I'm removing it for now. Either:

1) Go back to an old zImage/rootfs (I'll post a new one later)

2) Push it into android using shiddell's instructions: http://xdaforums.com/showthread.php?t=616436

I'd appricate it if you'd do #2, so I can get testers to work out bugs (there shouldn't be any). However, I'll be putting out a libgps-2.2 later that fixes the "failed first lock on fresh reboot" bug, so I understand if you'll want until then for a new rootfs.
[Touch CDMA Android Development] JacenSolo2001:
I may try the push tonight when i get in from work.

LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot :)

Thanks again for all you're doing !
[Touch CDMA Android Development] jnadke:
If you have ASTRO in your app tray, can you go to /lib and click-hold the libgps file. Hit details. What timestamp is it?
[Touch CDMA Android Development] JacenSolo2001:
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
[Touch CDMA Android Development] jnadke:
I'm talking about when android is booted (not /lib on the sdcard). It mounts the rootfs.img as a file system.

If you don't have a /lib directory, then it has to go in /system/lib

LD_LIBRARY_PATH usually only looks in /lib, then /system/lib

So it's possible I was pushing it into rootfs.img properly, and the modified timestamps aren't being updated.
[Touch CDMA Android Development] JacenSolo2001:
Jan 26 2010
[Touch CDMA Android Development] jnadke:
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.

Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.

I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
[Touch CDMA Android Development] jamezelle:
im going to make nbh's for the NAND flashers which files should i use

EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
[Touch CDMA Android Development] jnadke:
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.

The zImage-2.1 should be final.

I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.

Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported. I did come out with a zImage-2.2 that checks if accuracy isn't 0 before sending a message to libgps, but this triggered random reboots (looks like it doesn't like this). Right now it just checks if a gpstime is being reported (which isn't right because it should report that even if no position lock is present).

I'm not sure what the proper method for Android GPS is to gracefully indicate GPS is lost, but the libgps-2.2 version on my phone seems to work with zImage-2.1.
[Touch CDMA Android Development] jamezelle:
here you go ppl use the rootfs in the first post!!! this contains all 3 resolutions for vogue only right now

NAND NBH FILES 2.1 "240 428 and 480"

btw jnadke im not getting a lock with this in 2.1(2.1 eclair btw) not sure if it is compatible

EDIT: pulled up maps and it rebooted phone ill try again

EDIT2: 10 min not one sat, so i backed out fof GPS Test and it rebooted phone

EDIT3: ok so im an idiot and didnt use your rootfs and pushed the lib to /lib and my init points to /system/lib lol so i fixed it all is well ;) it works just fine
[Touch CDMA Android Development] dmulligan:
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
[Touch CDMA Android Development] jamezelle:
use the rootfs in the first post and the nbh's in my post on this page

i can confirm a lock
[Touch CDMA Android Development] dmulligan:
jnadke removed that file this morning.
[Touch CDMA Android Development] roberto188:
Kaiser Lockup

Poly, I too am having GPS lockups. Google Nav will work for about 2 minutes then just freeze. I'm running Zenulator's Iondonut. What are you running on your Kaiser? The screen shot looks nice! I recently tried the eclair builds for kaiser, but they are in Beta and are far too slow for day to day use.
[Touch CDMA Android Development] cb2002:
Kaiser GPS lockup

First a big thank to jnadke and all devs to the wonderful development and community spirit here.

I'd like to add one more data point to the Kaiser GPS lockup. I experience this fairly regularly on my ATT Tilt/Kaiser. Currently I'm running the latest Myn's warm donut in NAND with the 2/20 NBH from sourceforge.net/projects/androidhtc/files

Unfortunately every lock up is a hard lock up which require a battery pull reboot. Is there any log file to look at after reboot to figure out what happened? I can pull the log file if there is one and post it here after reboot.

Interestingly, I can't use ADB neither for some reason with this install since ADB does not detect the device although Windows did and had Android driver installed.

If you any help testing or debugging, just let me know... I can install test build with more debug log that survive a reboot if needed to reproduce the problem.

Thanks
[Touch CDMA Android Development] jnadke:
Thanks for the feedback.

Does the lockup happen randomly? Or after the same amount of time every time?
[Touch CDMA Android Development] cb2002:
For me, the first few times after a new install the GPS seems to work fine, take it for short trip back and forth to work (about 10 minutes, local road, low speed). One pattern I do notice often is that it tends to lose the GPS lock before locking up, i.e. Navigation would go from a 3D to a 2D and display "Searching for GPS.." then the phone locks up completely.

This seems to happen fairly more often when I'm driving on the highway, but not sure if that is because the higher speed or longer trip distance.

If you can compile a RIL with GSM cell tower patch that'd be great too, at least it would approximately knows the location.

Thanks jnadke
[Touch CDMA Android Development] cb2002:
Yesterday I installed the latest dzo NBH for Kaiser 03/13 and decided to give GPS a try again to see if anything changed. I drived over to a friend's house, about a 10 minutes drive total.

During the trip I had to enter a short tunnel. After 10-15 seconds into the tunnel, the phone lost GPS signal and lock up completely. It did not go into a 2D view with "Searching for GPS..." at all. Another battery pull reset.

Any thought on this?
[Touch CDMA Android Development] jnadke:
Next time this happens, after you reboot, get a dump of /proc/last_kmsg

i.e. Go to Terminal or BetterTerminal and do:

cat /proc/last_kmsg > /sdcard/errmsg

And then post the errmsg file here.

I want to know what's causing the lockups. A kernel panic should trigger an automatic reboot, but the kaiser might not support reboot (I don't know).

I did have a similar issue the other day. I was exiting GPS and the phone rebooted. I got some logs I'm checking out.
[Touch CDMA Android Development] dzo:
The kernel is set up so that it never reboots (shutdown when charging reboots but that's the only time I think), a reboot generally means that the ARM9 has crashed or is confused about something. On boot, it prints the last ARM9 error and the time it happened after the line that says "Modem Status:".

(I don't know if this works on kaiser) but it may not be a very helpful message.

In recent kernels I've disabled printing all the rpc call data so you might have to enable that again to find out what's really happening.

Good luck.
[Touch CDMA Android Development] jnadke:
It looks like a race condition, or a resource lock issue.

Looks like the thread was trying to read data while GPS was being shutdown.

I'll probably have to fix it up, though I've been meaning to rewrite the GPS driver to use blocking, rather than polling.

I attached my kmsg log. Let me know what you think.
[Touch CDMA Android Development] dzo:
I think I see the problem, the A9 sends rpcs to the A11 and until we started using the GPS they all fit into a single message so I just wrote some simple code to grab the message, (do_read_data in vogue_rpc.c). GPS messages are often quite long so I changed the code to to read them but it assumes that the rest of the message arrives immediately after the first part. I thought the A9 would do some locking so this couldn't be a problem but it seems like it is. The solution is to maintain a list of partial messages (using the MID, the message ID) and pass them on when the last part has arrived. The original google code did this but it used some extra encapsulation to route all the messages through 1 smd channel and so needed rewriting.

Does this make sense?
[Touch CDMA Android Development] jnadke:
Yeah, makes sense. Explains why the crashing is more or less random. Basically a race condition.
[Touch CDMA Android Development] zc2:
kmsg dump after GPS crash

here is my last_kmsg, after GPS has crashed
[Touch CDMA Android Development] dzo:
I'll make a start at fixing this if I have some time today, unless you want to?
[Touch CDMA Android Development] jnadke:
I won't have time until Saturday, but I can pick up where you left off.
[Touch CDMA Android Development] dzo:
I think I got it working, hard to test, but it puts the gps messages together fine and should be better. See my latest commit, I've also put a kernel and NBHs on my site.
[Touch CDMA Android Development] cb2002:
I'd love to take this for a test drive but unfortunately I'm on the Kaiser :(
[Touch CDMA Android Development] zc2:
Sorry, it did not help. My phone froze instantly as soon the Google maps tried to access the GPS.
[Touch CDMA Android Development] dzo:
The change is only for Vogue, Kaiser and Polaris use a different mechanism for getting gps data.
[Touch CDMA Android Development] conanford:
Ha, I have precisely the same problem with v5 (haven't tried any other versions), running myn's v4 warm donut & the 03-17-2010 nbh. HTC Vogue with Bell 3.42.50 radio and in Canada, it works very well on the way to work (with an occasional blue-circle growing to ~15 ft when between between two transport trucks at a light), but on the way home, it behaves exactly as you said. Incidentally, I drive generally NW to SE to work, and SE to NW home. Maybe there's a bug related to the time of day or direction?
[Touch CDMA Android Development] jnadke:
Thought I'd document this here:

Dzo found a bug in the linux kernel (zImage/NBH) side of the GPS driver.

Upgrade to the 4/6 kernel or later for the fix.

This bug may have been related to all the dropout symptoms you have been seeing. It would really only make the GPS more unreliable the 2nd time you use Google Maps without rebooting.
[Touch CDMA Android Development] tatnai:
have been running the latest kernel since it was released i still have the g p s drop out issues however i'm wondering if it is more a google navigation problem rather than a gps problem as copilot functions without any problems for me.

Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
[Touch CDMA Android Development] jnadke:
Looks like its crashing sometime during gps_enable. There should be one more set of messages for more commands its sending.

I don't have a Kaiser, so that makes the problem extremely hard to solve. Further, most of the stuff reverse engineered was done long ago, by people not still around.

Whatever is happening, either the phone doesn't like the current commands we're giving it, or some race-condition is happening (more likely).

The most I can do is make sure no other code is trying to ask for data before gps_enable is called.

I think the problem might lie in the fact that ioctls are non-blocking. It looks like the user-space driver is calling the GPS_ENABLE routine, then continuing for asking for data.

Looks like there's a race condition here (in ioctl handler):

475 if (!state->state) {
476 state->state = GPS_STATE_ON;
477 gps_enable();
478 }

476 and 477 should be swapped. Similarly, 482 and 483 (the gps_disable) lines should be swapped too.

Looks like this is crashing it (from gps_nmea_thread):

405 if (state->state == GPS_STATE_ON)
406 gps_tickle();

GPS tickle looks to be sending more commands over the AMSS, it might be doing this before gps_enable has finished.

Additionally, I don't know what trying to read from the SMD7 NMEA channel does before the device is operational. The entire gps_nmea_thread should be protected by a:

while (state->state != GPS_STATE_ON)
[Touch CDMA Android Development] kallt_kaffe:
I have a Kaiser and I have a virtual Ubuntu machine setup for compiling kernels but I do not fully understand what to do with the information above.

But if I'm told what changes I should make to board-kaiser-gps.c then I'll be happy to try it out. I'm experiencing the GPS freezing often enough to have given up using the GPS in Android but I'd love to see it fixed.
[Touch CDMA Android Development] jnadke:
The simple fix is to:

In file arch/arm/mach-msm/board-kaiser-gps.c:

Swap lines 476 and 477. Similarly, 482 and 483 should be swapped as well. These are race condition lines. The action (gps_enable) needs to be done before it's marked as completed (GPS_STATE_ON).

This should eliminate the freezing issue, unless it is something else. Start with that.

File with line numbers is here, for reference:

http://git.linuxtogo.org/?p=groups/...64129e9e692a6537eb4c6;hb=refs/heads/htc-vogue

Ironically, the gps_enable printks are actually causing this. printk's slow down kernel code considerably, enough that they can cover up or cause bugs. In this case, the printk is slowing down the gps_enable code and exacerbating the race condition.

Keep the printks though, they are not the culprit.