Database Users

Lets get Organized ** Post only flashable Roms****

Maybe a good idea maybe not but since google code was abolished i can't find a thing. Here is a link to an all in one flashable installation of cupcake everything is working gps, market, sms calls etc. I found that the touchscreen may not work on first install just soft reset device and all will work on next reboot. Please follow suit for whatever releases you have thanks. I take no credit in any of the work in the rom biuld we know who these acknowledgements go to.
cupcake 1.5 google-ion 9-12-09
http://www.mediafire.com/?0zniavwqg2m
All files included in zip including voguimg needed to flash nothing else needed just unzip to storage card and enjoy!!!
I will add more links in this post as people add them!!!!

mush2699 said:
Maybe a good idea maybe not but since google code was abolished i can't find a thing. Here is a link to an all in one flashable installation of cupcake everything is working gps, market, sms calls etc. I found that the touchscreen may not work on first install just soft reset device and all will work on next reboot. Please follow suit for whatever releases you have thanks. I take no credit in any of the work in the rom biuld we know who these acknowledgements go to.
cupcake 1.5 google-ion 9-12-09
http://www.mediafire.com/?2ygqzmzjzoe
All files included in zip including voguimg needed to flash nothing else needed just unzip to storage card and enjoy!!!
Click to expand...
Click to collapse
is this just standard cupcake? is it themed?

standard with a blank data file

sorry if this sounds dumb, but i have been away from XDA for quite a few months now.
so you are talking about a very flashable android ROM for the vogue? meaning kiss bye bye winmo? everything works? even MMS and camera?

MMS depends on your carrier i have sprint and i can receive via picture mail(web view) but i cannot send. Everything else works YES kiss winmo goodbye i have

I followed the guide to fix my gps In windows mobile but for some reason, it still doesn't work. Would the GPS work if I flashed android instead of running it off windows mobile?

kiwilime said:
I followed the guide to fix my gps In windows mobile but for some reason, it still doesn't work. Would the GPS work if I flashed android instead of running it off windows mobile?
Click to expand...
Click to collapse
short answer, no it needs to work in win mo first. back to the drawing board. first you need to unlock your phone with an unlocker, then you need to flash an official rom preferrably from your carrier that is GPS enabled, then you can run android and use GPS on it. many tuts around. if you did all of this already, you didn't do it right. also, some programs in win mo require GPS to be primed before working. make sure to use something like google maps to test in win mo.

I'm curious. What's so great about Android on the phone?
I'm using Windows Mobile 6.1 and the phone seems to run fine.
Are there clear cut advantages or is it just "something different"?

jimt007 said:
I'm curious. What's so great about Android on the phone?
I'm using Windows Mobile 6.1 and the phone seems to run fine.
Are there clear cut advantages or is it just "something different"?
Click to expand...
Click to collapse
to me the interface is superior, the apps, but mostly it's just something cool.
functionality wise I think you can achieve the same thing on Windows mobile with the right apps. Just the cool stuff like oooooo are not there on Winmo

jimt007 said:
I'm curious. What's so great about Android on the phone?
I'm using Windows Mobile 6.1 and the phone seems to run fine.
Are there clear cut advantages or is it just "something different"?
Click to expand...
Click to collapse
Run Android from your sd card via haret. Then you can have winmo and android.

im having issues, I have the original 512mb card in the phone formatted twice with fat32 partition. Copied the 6 files from your zip file and flashed the nbh file via the windows ruu flasher all was good. Boots with the linux penguin but I get to the state where it says losetup: /dev/block/loop0: No Such file or directory Failed
Failed to mount data fs on SD Card.
/bin/sh1 can't access ttyl job control turned off.
Then it just sits there.
Help, I'm playing around with this on my partially broken vogue (have my good one running winmo) so I can fool around with it but I've tried everything I could.
Thanks

Have try it on my Kaiser... I know for sure it will not work.. and indeed... loop between reset and the HTC logo

is this different than the one dzo made?

my mistake i made the zip file really quick last night i will redo it. Apparent i didnt rename datablank.img to data.img i will fix and reupload but all you have to do is make sure the file is data.img
The link in the first post has been updated to reflect this change. My apologies.

mush2699 said:
Apparent i didnt rename datablank.img to data.img
Click to expand...
Click to collapse
If that is only the difference then we can rename it itself if you already have the files.
Question: Can you also replace the system.sqsh with a build you like?
(When you know for sure it is working.. beside if GPS/Bluetooth is working.)
And in the ROM there is: zimage, initrd and haret.exe?
the flash will not work on a Kaiser have try the new ZIP file.

I flashed this rom and it was very nice, but when i tried to sync my google account, it force closed and my contacts never synced. Is there a fix to this?

Can someone also make a Flashable rom for KAISER ... thanks..

ludester said:
im having issues, I have the original 512mb card in the phone formatted twice with fat32 partition. Copied the 6 files from your zip file and flashed the nbh file via the windows ruu flasher all was good. Boots with the linux penguin but I get to the state where it says losetup: /dev/block/loop0: No Such file or directory Failed
Failed to mount data fs on SD Card.
/bin/sh1 can't access ttyl job control turned off.
Then it just sits there.
Help, I'm playing around with this on my partially broken vogue (have my good one running winmo) so I can fool around with it but I've tried everything I could.
Thanks
Click to expand...
Click to collapse
Try scanning the card for errors. Aslo note that the data file needs to be named data.img. Between those 2 ideas you problem should be solved.

Roms
Here is a whole bunch of them
not sure which ones work perfectly, i know a couple of them work for me.
go ahead and try em out.
i take no credit for these roms
http://www.mediafire.com/?sharekey=aa29b5ef55091cf1c79b87b207592a1cda1aeb409e8c06c379b5ba589d1986ba

Even running natively instead of haret i have noticed battery life really sucks and i'm just talking about standby mode. Using the same programs on android as winmo i get about a third of the battery life. Can anyone recommend any battery saving tip. GPS is on only when needed and data is always on. I will not turn data off as it is always on in winmo and i have no issues with winmo.

Don't do it: Reduce LCD Density Setting in Build.Prop For Higher Res Look

hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx

futureshock said:
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
Click to expand...
Click to collapse
The quickest way would be to load up another clean version changing the original to froyo boot it up & go to astro copy the build from system to SD or to the froyo version & restart then delete new version and paste the build into the original froyo & reboot

so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet

Next time, try backing up the android folder on ur SD card before changing anything.. that way a quick format and a trip to ur computer will get ur phone working again..
Sent from my HTC HD2 using XDA App

futureshock said:
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Click to expand...
Click to collapse
Can you share this file here? i got the same problem that many applications can't work with full screen, and i didn't backup this file...
thx~

Sorry for my Englisch.
Problems with the screen in fullscreen games.It is easy to change it.
Open the file with a text editor Build.Prop and edit the line of "ro.sf.lcd_density = 220" to "ro.sf.lcd_density = 240"

Followed the instructions and did this mod.
I sorta of like it. Didn't encounter any problems at all. It's hard to tell the difference. Some apps will support it, Sense UI does not.
The bigger question is. Does this impact battery life. I am still testing this..so right now that's debatable.

I set dpi to 192 and love it. Most apps show more info on screen, a few games are not clever enough.
After using WinMo for 2 years, I'm used to high precision "touching" :-D
A tip: download Spare Parts and use it to turn off compatibility mode.

i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2

vua777 said:
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
Click to expand...
Click to collapse
Not exactly.
The app works but doesn't really make any difference to build.prop file nor does reboot the device.
Your can manually make the changes.
I set it to 200 and I use adw launcher to make usage of the extra space.

Black screen from changing build.prop
So i really wish I found this thread before i tried to change anything. So i also have the black screen when loading android after changing build.prop file, I did copy the file before I changed it. Now i just dont know how to get into the system folder to change it back because when i load android its all black. Can anybody help me here?

Market won't stop force closing! - PLEASE HELP!

Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!

maybe you should try an other android rom ?

The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
SMS92 said:
Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!
Click to expand...
Click to collapse

yz.hd said:
maybe you should try an other android rom ?
Click to expand...
Click to collapse
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
Click to expand...
Click to collapse
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!

SMS92 said:
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!
Click to expand...
Click to collapse
This should help cos if u do it this way u actually not installing/reinstalling the app. u actually repleace the sys market.app for the original one from the ROM. So there is no way it will not work again if it was working before after u flashed the ROM.
I'm pretty sure it will do the trick, but also I may be wrong .
I had some issue on my ROM with cam.app and this proced. helped me.

Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom

FIXED! [Edit: not]
Here's what I did.
Downloaded THIS
Extract it to C:\Droid
Boot into Win Mobile and move your data.img in \Android\ into the \Droid\ folder on your PC.
Start > Run > CMD
type "cd c:\droid" (without quotes) to get into the directory you've created.
Type "e2fsck -f data.img" (without quotes) and say 'y' (yes) to all the errors you encounter. There will be dozens. When done you'll be notified the modified data.img has been saved.
Copy the newly modified data.img from \Droid\ to \Android\ on your device.
Boot into Android - things might be a bit slower/laggy at first.
All should be well!
Edit: This fix seems to have really slowed my phone down. It takes at least 2x as long to run stable on boot (i.e. stop lagging, load all background apps etc). I've imported my previous data.img over and will be trying the fix by Dom (above).
Edit2: And I'm now getting com.android.media force closes with the modded data.img! Music app won't work. Jesus!

ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Thanks for that Dom, I'll keep that in mind for next time! Great tip!

ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?

Same here ...?
SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
Sent from my HD2 Jaws-MIUI

Did fix_permissions via the app ROM Manager and the Market force close still remains

How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.

SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
rikardo1979 said:
Same here ...?
Sent from my HD2 Jaws-MIUI
Click to expand...
Click to collapse
Hmm, it seems that this script isn't inluded in your roms. But for you SMS92 it seems that it is another problem anyway.
If you wanna try sth. else see this:
http://all-google-android.com/google-android-forums/t-mobile-g1-modders/fix-permissions/
This is an "improved" fix permission tutorial which goes further than the command I posted above...quote from the link above: "fix_permissions is only intended for correcting ownership issues. It does not modify permissions, as is being requested."
In this post is a downloadlink for the advanced script so it doesnt matter if its already included in the rom...
@ricardo: see here if you still wanna try it: http://modmymobile.com/forums/567-motorola-backflip-general/556261-fix_permissions-script.html
Greetz Dom

johncmolyneux said:
How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.
Click to expand...
Click to collapse
It's a no-go I'm afraid.
So far the only thing that's worked is running the repairs on my 2gb data.img using e2fsck on my PC, but this in turn created a load more problems (com.process.media started force closing and the rom seemed to be much slower)
Will try some more suggestions tonight.

if your running gingerbread make sure the app is installed on the phone not the sd

I'm also suffering from this issue it started for me when an automatic update downloaded (which I didn't install) I will see if any of the above fixes work for me & if not I will start with a fresh copy of the ROM. Have to admit I have barely used winmo since I started using this build!

I have the same problem using froyo 2.2

I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App

robdee102 said:
I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Any chance you could walk me through the steps you took for a fresh install? I am at my wits end with the FCs and a mount/partition error. Here is my setup:
HTC Hd2 Leo
HTC Desire
Android 2.2.1
Mod darkstone SuperRAM FroYo v1.5
Build FRG8
I am up for a new ROM or whatever to get my phone back in order. Thanks so much!

BOYPPC-SHIFTPDA v.37 Market Force Closes
BOYPPC-SHIFTPDA v.37 Market Force Closes
Please Help my Market is constantly force closing on me the error is:
Sorry!
The application Market
(process com.android.vending)
has stopped unexpectedly.
Please try again.
then it has a force close button.
I would really like to install some apps with the market but
every time I try and use the market I get this error,
I am running the BOYPPC-SHIFTPDA v.37 ROM
Please Help Me

GPS Solution revisited Sense gingerbread.

A lot of users seem to be downgrading to froyo to get a proper GPS signal.
If this is the case then its unlikely to be hardware related ( press down on cover around flash to ensure good contact).
If you have tried various fixes in Gingerbread sense and still cannot get a decent GPS performance then try this file. gps.goldfish.so.
Unzip and with something like root explorer copy to: system/lib/hw (leave other file gps.spade intact) on your rooted phone.
Click on read write button and on permissions change to match other files,
usually tick all 3 boxes for read and user for write (cmhod 644) ticking all boxes (chmod 777) should work too. Or you can push file with adb (dont forget chmod). Either way. reboot and try, I got a stronger signal and GPS is working good in cloudy weather too.
Also worth trying in conjuction with this is clearing the efs data I used second method ( make a backup) before giving up.
http://forum.xda-developers.com/showthread.php?p=12764930#post12764930
The file is from cyanogen CM7 nightly 80. So thanks to Cyanogen team and Kali for hosting CM7 nightly thread.Neadless to say not required if using CM7.
Good luck

[Q] GPS gingerbread on HD2

Hi guys, bit of a newbie here.
Ive seen on the site abut getting gps to work on this version and followed instructions but nothing seems to work.
It got me thinking... would an external Bluetooth GPS work instead? Just as a bit of a work around?
Many thanks for your help here

johnpodlesak said:
Hi guys, bit of a newbie here.
Ive seen on the site abut getting gps to work on this version and followed instructions but nothing seems to work.
It got me thinking... would an external Bluetooth GPS work instead? Just as a bit of a work around?
Many thanks for your help here
Click to expand...
Click to collapse
Do u mean that u have tried this too. http://forum.xda-developers.com/showthread.php?t=1100114
It work for me and a lot of other people who tried it.

nghockcheng said:
Do u mean that u have tried this too. http://forum.xda-developers.com/showthread.php?t=1100114
It work for me and a lot of other people who tried it.
Click to expand...
Click to collapse
The OP may also want to check the gps.conf file to determine if it is optimized for the region. Check this thread out as well: http://forum.xda-developers.com/showthread.php?t=953630
I am using Tytung's Gingerbread 2.3.5 Nexus HD2 v2.9 build with both the GPS v2.0 and an optimized gps.conf file on my phone. First locks are under 10 seconds and relocks are almost immediate using the built-in Google Navigation on the phone. Without the optimized gps.conf file, first lock was around 20 seconds. Tytung's ROM is set up for the North America. If you are not in North America, then you will need to change the gps.conf file to match your region.

The build-in gps must work, but a bluetooth gps will work to.
Sent from my mercury using XDA App

GPS problem
Hey guys I don't want to open a new thread, so I'll just post here...
I have the same GPS problems as most people here – GPS Status and GPS Essentials are showing no satellites, 0 visible and 0 used for fix.
I’ve left the phone to search for 10min in couple of occasions and nothing.
I think I’ve tried about everything here to fix it (and this is begging to bug me majorly)...
Updated the libraries with v2.0 RPC tytungs update (before that I’ve used the AngleDeath Europe.zip patch)…
Then edited the gps.conf file
first added the eurpe.pool.ntp.org,
then tried following lines
0.europe.pool.ntp.org;
1.europe.pool.ntp.org;
…etc.
Event tried the (my) country specific server address (pulled it of from the NTP POOL PROJECT website)
rs.pool.ntp.org
Installed the xtra.bin injector
Tried it on a perfect summer day and/or night, with 3g and WIFI on… but no results…
I’m running
CyanogenMod-7-NIGHTLY-Desire[TyphooN_V3.5.7-MAGLDR]
Tytungs r11_beta2 kernel (the lock screen lag fix)
CW 3.1.0.0
Radio Leo 2.15.50.14
Any ideas?

hi, this is what ive used but i must be doing something wrong and dont understand what im doing with the files etc
Im using MDJ_GingerBread_HD2_v.1.0_RC4_RAM_MODDED SC Card version
does that make any difference?

Is anyone with this problem using one of the latest roms with agps support? I can lock on in about 20 seconds from a restart. Also is everyone on the latest magldr?

never had any problems using MDJ Gingerbread... no editing or anything else - it works perfect right from the get-go...

t00tall said:
Hey guys I don't want to open a new thread, so I'll just post here...
I have the same GPS problems as most people here – GPS Status and GPS Essentials are showing no satellites, 0 visible and 0 used for fix.
I’ve left the phone to search for 10min in couple of occasions and nothing.
I think I’ve tried about everything here to fix it (and this is begging to bug me majorly)...
Updated the libraries with v2.0 RPC tytungs update (before that I’ve used the AngleDeath Europe.zip patch)…
Then edited the gps.conf file
first added the eurpe.pool.ntp.org,
then tried following lines
0.europe.pool.ntp.org;
1.europe.pool.ntp.org;
…etc.
Event tried the (my) country specific server address (pulled it of from the NTP POOL PROJECT website)
rs.pool.ntp.org
Installed the xtra.bin injector
Tried it on a perfect summer day and/or night, with 3g and WIFI on… but no results…
I’m running
CyanogenMod-7-NIGHTLY-Desire[TyphooN_V3.5.7-MAGLDR]
Tytungs r11_beta2 kernel (the lock screen lag fix)
CW 3.1.0.0
Radio Leo 2.15.50.14
Any ideas?
Click to expand...
Click to collapse
I think the problem is that on your build they recommend using Tytung's NMEA and not the RPC file that you tried. Try loading v2.0 NMEA by Tytung and give it a try. On some of these builds, only one of these files will work. I suspect your build is one that will need only the NMEA file to make the GPS work properly.

slbenz said:
I think the problem is that on your build they recommend using Tytung's NMEA and not the RPC file that you tried. Try loading v2.0 NMEA by Tytung and give it a try. On some of these builds, only one of these files will work. I suspect your build is one that will need only the NMEA file to make the GPS work properly.
Click to expand...
Click to collapse
Yeha, I’ve noticed a after my post here that in the “update” list of the TyphooN ROM is stated that the NMEA lib is implemented in it… anyhow, re-loaded the NMEA lib… edited the .conf file again… rebooted… injected the xtra.bin … left the phone outside for like 5min to try to find any satellites… 0 hits :/
Man, this is frustrating… I would hate to have to change or re-flash the rom, I’m quite satisfied with this one… maybe I’ll switch to iOS XD

t00tall said:
Yeha, I’ve noticed a after my post here that in the “update” list of the TyphooN ROM is stated that the NMEA lib is implemented in it… anyhow, re-loaded the NMEA lib… edited the .conf file again… rebooted… injected the xtra.bin … left the phone outside for like 5min to try to find any satellites… 0 hits :/
Man, this is frustrating… I would hate to have to change or re-flash the rom, I’m quite satisfied with this one… maybe I’ll switch to iOS XD
Click to expand...
Click to collapse
With all the changes that you did, you may have no choice but to reflash the ROM again. Then only change the gps.conf files to your region after the reflash if it is not correct for your area. Then hopefully your GPS will be working again. If after all that, and it still doesn't work, you may have to look in the GPS antenna to see if it is working.

slbenz said:
With all the changes that you did, you may have no choice but to reflash the ROM again. Then only change the gps.conf files to your region after the reflash if it is not correct for your area. Then hopefully your GPS will be working again. If after all that, and it still doesn't work, you may have to look in the GPS antenna to see if it is working.
Click to expand...
Click to collapse
I've flashed my phone (yet again) the newest build of the TyphooN ROM... edited the .conf file, AND... nothing :| maybe I wrote the conf file in a wrong way... should it look like this?
i54.tinypic. com/11qgv8h.png (c/p the link for a screenshot of the conf file - I still cant post outside links)
any help would be greatly appreciated!

t00tall said:
I've flashed my phone (yet again) the newest build of the TyphooN ROM... edited the .conf file, AND... nothing :| maybe I wrote the conf file in a wrong way... should it look like this?
i54.tinypic. com/11qgv8h.png (c/p the link for a screenshot of the conf file - I still cant post outside links)
any help would be greatly appreciated!
Click to expand...
Click to collapse
Unfortunately, I can't see the link. Maybe you should try the quick and easy way to change your region by using FasterFix that is free on the Market. At least it will quickly change your first gps.conf file line to the correct region and hopefully get you a gps lock. I suspect that the gps.conf file you are changing may not be correct or possibly the changes you are making are not being taken and the original gps.conf file keeps staying? I don't think it is the build. I've used TyphooN in the past with my custom gps.conf file that I use with no problem.

slbenz said:
Unfortunately, I can't see the link. Maybe you should try the quick and easy way to change your region by using FasterFix that is free on the Market. At least it will quickly change your first gps.conf file line to the correct region and hopefully get you a gps lock. I suspect that the gps.conf file you are changing may not be correct or possibly the changes you are making are not being taken and the original gps.conf file keeps staying? I don't think it is the build. I've used TyphooN in the past with my custom gps.conf file that I use with no problem.
Click to expand...
Click to collapse
Thnx anyway... I think I'm going to flash the win 6.5 back on... to check is my GPS receiver working... maybe it's a hardware fault, I've recently purchased it used, and flashed it to android immediately...