Hi all xda folks
I am starting this thread because I thing there is no proper solution to long gps fix time problem. I want to share my observation with a hope of helping solve this little prob. In most other ways our android port is solid and in my opinion comparable with most native android devices.
Now to avoid people saying that I just didn't search the forum I'm aware of partial solutions like :
1) Using Gps status app to download A-Gps data
2) Using WM QuickGps to download gps data using WM
3) Switching to proper gps region using gps.conf
...
Now I would like to sugest (from my point of view of humble user;-) )possible solutions for the devs but don't get me wrong I don't mean it to offense anyone.
I'm not a dev just trying to help.
1) Write something what does exactly that thing what QuickGPS does just to do it from Android environment
//Cause right after QuickGPS download fix times are minimal
//This would be enough fix for me ;-)
2) Find out what is wrong with current gps drver or any a-gps or any things helping to get faster fixes
To the second point a have an observation I wanted to share. When using GPS Test app to get fix on HD2 you don't see the signal strength bars before you get fixed. But as I saw on Desire the bars show up immediately and just change color when you get to the fix. But its just a hint. I don't know if it does mean anything.
Desire screen !!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is quite everything I wanted to say please don't stone me I mean no offense to anyone
in my experience its build specific.
every desire build I've used (currently m-deejay's revolution) has the gps issue.
Cyanogen Builds do not (currently using michyprima's Everyday Builds).
songokussm said:
in my experience its build specific.
every desire build I've used (currently m-deejay's revolution) has the gps issue.
Cyanogen Builds do not (currently using michyprima's Everyday Builds).
Click to expand...
Click to collapse
pretty much
Cyanogen builds can have the issue too, I've had major problems on shubcraft and very slow locking on hyperdroid.
The main problem is that Android can't write data to the gps chip yet, which is necessary to be able to use the 'a' from aGPS. (That's exactly what QuickGPS does, and because it's written to the gps chip, Android can access it but not update it.)
So unless someone manages to give Android write access, I don't think there's a whole lot we can do, except for the known gps.conf and libgps tricks.
StephanV said:
Cyanogen builds can have the issue too, I've had major problems on shubcraft and very slow locking on hyperdroid.
The main problem is that Android can't write data to the gps chip yet, which is necessary to be able to use the 'a' from aGPS. (That's exactly what QuickGPS does, and because it's written to the gps chip, Android can access it but not update it.)
So unless someone manages to give Android write access, I don't think there's a whole lot we can do, except for the known gps.conf and libgps tricks.
Click to expand...
Click to collapse
And that would easily explain why it works in WinMo...but does not clearly explain why some users have quick lock in Android (I am not one..mine takes 3-5 minutes sometimes).
Jon
JonSolo said:
And that would easily explain why it works in WinMo...but does not clearly explain why some users have quick lock in Android (I am not one..mine takes 3-5 minutes sometimes).
Jon
Click to expand...
Click to collapse
I'm not too sure either, but I think it may be because of QuickGPS too. I noticed there's an option to enable gps data download whenever activesync is enabled. Most people boot bank into WinMo for installing a new build, kernel or whatever, and would that way actually run QuickGPS at least once every week. But I'm by no means an expert, this is just what seems to me a plausible explanation.
I thought quickgps "just" go to internet, and download the satellites positions into a text file? If you don't do that on wm the first gps lock is slow, the second on a same period is quick because the phone now knows where they are. Too bad android can't so that for now, maybe with gingerbread...
So please can someone of you who say that its build specific post the build and kernel with which it is working you get fix in less then lets say 15 secs?
Thanx
Sichroteph said:
I thought quickgps "just" go to internet, and download the satellites positions into a text file? If you don't do that on wm the first gps lock is slow, the second on a same period is quick because the phone now knows where they are. Too bad android can't so that for now, maybe with gingerbread...
Click to expand...
Click to collapse
First part is true, problem is that WinMo can store these files on the gps chip, Android can't. Android can only read data from this chip, hence QuickGPS being a valid fix.
Android can of course do this, we just can't on our HD2, so gingerbread ain't gonna fix any of that.
Waterskier33 said:
So please can someone of you who say that its build specific post the build and kernel with which it is working you get fix in less then lets say 15 secs?
Thanx
Click to expand...
Click to collapse
I believe I've had it fixed in shubcraft 2.0, JDMS 1.6 did a pretty good job too. Might've been total coincidence though, I'm still not sure if any of this is build related.
Today I asked on #htc-linux and it seem that devs don't see the problem I spoke with markinus and he told me that he has fix in about 4 sec. So maybe it is not kernel problem.
I still have huge problems with GPS. Doesn't matter what ROM or radio I use it doesn't lock, or lock after 1-5 min. Outside or inside doesn't change anything. It's not a problem with week signal, my friend with HTC wildfire get it within seconds sitting next to me. I use kwbr rom with 2.15 radio.
StephanV said:
Cyanogen builds can have the issue too, I've had major problems on shubcraft and very slow locking on hyperdroid.
The main problem is that Android can't write data to the gps chip yet, which is necessary to be able to use the 'a' from aGPS. (That's exactly what QuickGPS does, and because it's written to the gps chip, Android can access it but not update it.)
So unless someone manages to give Android write access, I don't think there's a whole lot we can do, except for the known gps.conf and libgps tricks.
Click to expand...
Click to collapse
I find this pretty strange.
With quickgps you have to download the data, you really see a progress when downloading, and the file goes to the windows directoy. xtra.bin is the filename.
If you remove that file and reboot the phone you have to wait a long time to get a gps fix again.
In Android you have no clue if it downloads it, and where does it go? Try to do a search on that file. I got 0 results so I actually wonder where it is and even if it works?
Related
I'm running WM6 w/spb mobile shell and trying to use SPB Backup, but for the last two days i've been seeing a log message about someting called the "NK.EXE" process blocking a read on "windows/compimeh.0409.dat"
Any help appreciated.
Thanks.
Darkeyce said:
I'm running WM6 w/spb mobile shell and trying to use SPB Backup, but for the last two days i've been seeing a log message about someting called the "NK.EXE" process blocking a read on "windows/compimeh.0409.dat"
Any help appreciated.
Thanks.
Click to expand...
Click to collapse
NK.EXE is a required kernel system process.
Mike
Ah...thanks...I wonder if i can exclude that...
???
I too am having the same problem. Can this be fixed? Am I missing something? Am I always going to have this problem now that I am running WMBE 1.2? Is it a big deal? Is there a way to fix it? I would like SPB Backup to work without any problems.
Many thanks for the answers to my questions.
Thanks
Marc
It's no big deal.
compimeh.0409.dat is data only meant to be written/read by the operating system
mikechannon said:
NK.EXE is a required kernel system process.
Mike
Click to expand...
Click to collapse
actually... it's THE kernel
Olipro said:
actually... it's THE kernel
Click to expand...
Click to collapse
Stripping the peach:
the skin is not the kernel, neither is the fruity juicy flesh. Most people would call the stone the kernel, but is it? No, inside the stone is a nut. Is that the kernel? or is that tiny little baby plant inside the nut the actual kernel?...
Maggy said:
Stripping the peach:
the skin is not the kernel, neither is the fruity juicy flesh. Most people would call the stone the kernel, but is it? No, inside the stone is a nut. Is that the kernel? or is that tiny little baby plant inside the nut the actual kernel?...
Click to expand...
Click to collapse
I am pink therefore I'm spam.
But seriously when you find the value of X you will have the answer to your kernel conundrum:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's all very simple really
Mike
Maggy said:
Stripping the peach:
the skin is not the kernel, neither is the fruity juicy flesh. Most people would call the stone the kernel, but is it? No, inside the stone is a nut. Is that the kernel? or is that tiny little baby plant inside the nut the actual kernel?...
Click to expand...
Click to collapse
nk.exe is the kernel, period.
Okay, okay, I'll take your word for it ;-)
Back to serious: Do you know if NK.EXE is very different for different devices and if it changed a lot over the years?
Maggy said:
Okay, okay, I'll take your word for it ;-)
Back to serious: Do you know if NK.EXE is very different for different devices and if it changed a lot over the years?
Click to expand...
Click to collapse
yes...
every CE version since CE 1.0 has seen changes in the kernel... sometimes very big changes...
and yes it is device specific because the hardware abstraction layer (which is called OAL in our case) is linked into the same exe as the kernel, i.e. NK.exe.
this will change in CE6 (no, WM6 is not CE6!!).
....why did you ask about this ?
Because I own a Himalaya and a Backpack (CF slot, extra battery and VGA/composit output for Hima). Lots of Hima users who upgraded to WM5 or WM6 have their Backpacks laying in a drawer unused because there are no working drivers. I guess I found out why they refuse to work, the cause is IMHO in NK.EXE. I'm trying to gather courage to dive deep into disassembling it...
Maggy said:
Because I own a Himalaya and a Backpack (CF slot, extra battery and VGA/composit output for Hima). Lots of Hima users who upgraded to WM5 or WM6 have their Backpacks laying in a drawer unused because there are no working drivers. I guess I found out why they refuse to work, the cause is IMHO in NK.EXE. I'm trying to gather courage to dive deep into disassembling it...
Click to expand...
Click to collapse
sorry for slow reply.
if you need help with kernel disassembly let me know
also, do you know asm? that'll be needed a lot. and reading the C sources as well.
i've had some fun before with nk.exe..
but why do you think the cause for your problem is nk.exe?
can you tell me more details?
Thanks for the kind offer. I've done some x86 ASM programming in the late 80's, early 90's, so no, I'm not an experienced XScale ASM programmer and much less capable of of porting bits and pieces of drivers and kernel from WM2003 to WM6. But I'm willing to learn and there are many backpack owners who currently can't use it for anything else than for VGA/composit output.
BTW I've read lots of C sources over the years, some I do understand at first sight, some I'm totally unable to read. But how is C related to this problem?
All that's known about Himalaya ASIC5 as far as I can find it:
http://wiki.xda-developers.com/index.php?pagename=HimalayaASIC5
This chip handles PCMCIA so it's very likely that it's responsible for R/W access to CF card, right?
http://wiki.xda-developers.com/index.php?pagename=HimalayaGPIO
As you can see GPIO2 Backpack IRQ hooks into nk.exe, that is the Himalaya WM2003 any version official releases... There are several other known details about Backpack in these pages http://wiki.xda-developers.com/index.php?pagename=HimalayaHardware but the amount of information does not yet make me happy.
There has been a leaked out WM5 Hima beta that has never been officially released, but some, very rare, ppl on buzzdev reported having Backpack battery and/or CF working using that ROM...
if you want to understand the kernel disassembly, you must understand C too, because using the C sources for the kernel (the shared source in platform builder) will make it *lots* easier.
i don't think you can port the driver without rewriting it in C/C++, so that's another reason why that'd be a requirement.
unless the modification that is needed is simple in asm...
but even to find what the problem is, is not a trivial task at all.
BTW what is your guess about how nk.exe is related to the problem? i'm curious.
do you have this beta wm5 where this backpack thing works? that would make this task quite a lot easier.
cmonex said:
if you want to understand the kernel disassembly, you must understand C too, because using the C sources for the kernel (the shared source in platform builder) will make it *lots* easier.
Click to expand...
Click to collapse
Are the kernel C sources public? Or is there a way to decompile them?? That would indeed make things easier.
BTW what is your guess about how nk.exe is related to the problem? i'm curious.
Click to expand...
Click to collapse
IMHO,MVVHO it seems clear to me from the GPIO table
do you have this beta wm5 where this backpack thing works? that would make this task quite a lot easier.
Click to expand...
Click to collapse
It did not work for all, most tried and failed, some where lucky. Himalaya's can be nasty critters. I have here two "identical" Hima's, both type PH10B, both same ROM, same bootloader, same radio, same RAM configuration. I bought both with broken screen, bought 2 screens with identical part # from same seller, but one is much darker than the other. No problem, I use mine (the darker one) always at 40% backlight and it's still comfortable reading. But strange.
Even stranger, I tried to install the same bunch of software on both, even in the same order. Some programs that ran smootly on A crashed B vice versa...
I think HTC was still trying to find out how to separate the experimental department from the construction line in those days...
Back to your question, it was a very early unstable beta, I tried it, went back to WM2003, deleted that beta :-( I could not foresee that it could play such a crucial role later in history.
Shortly afterwards Microsoft started law suit threats against the founders of xda-dev and buzznet, all these early ROMs were taken off ftp sites. I PMmed some of the members who tried it, especially those who reported working Backpacks... no chance...
as i said: shared sources from platform builder. most of the kernel source is available in there. let me know if you can't find PB 5.0. i have the download links for the eval version and the eval license key.
decompiling, dream on..
could you please go into details on the GPIO? this would make matters much more clear.
i hope you can find that rom somehow. that would make this case less hopeless.
Is it correct modify NK to extend its memory from 84 to 100mb as we are dealing with the Kernel?
I tried by altering the following hex address in S000 but it didn't work
From 9FE530559FE5A13EA0E38224A0E3
To 9FE530559FE5A13EA0E38324A0E3
I can't boot anymore. Always stuck on 2nd splash. But if I removed it, it boots fine but keeping 84mb program memory instead 102.
Any idea folks?
Thanks
cmonex said:
nk.exe is the kernel, period.
Click to expand...
Click to collapse
Ok...Im new to XDA and have always come here when I've needed help. However, after looking around I cannot find an answer to my current problem. I have a T-mobile wing with a 6gb storage card. I have all of my software, movies, pictures, ie cache, and pictures installed to my storage card. My problem is that my main system storage seems to be decreasing by the day. I am down to 3.5mb and have no clue as to what is consuming the space. I have run scans for large files and have even run sktools to make sure that im clearing out everything. Has anyone else experienced this problem? Any help would be greatly appreciated.
Danny
Already tried a soft-reset?
It usually clears it up and otherwise check if you have set your storage card as storage for your mail attachements.
Yep...I've done all of that and nothing. Im really running out of options and dont want to do a hard reset to have to re-configure everything how I have it now. urggg
Try using this.
I'd also suggest using PocketMechanic or MemMaid ... and I'm sure SkTools will do it too to clear out all the crap that you can.
With PocketMechanic, you can "relocate" installations from the main device to the storage card, and that may help you as well.
I had the same problem. Then I stuck Open Touch 2.6 on it, and all of a sudden it ran way better. I was really apprehensive about doing it at first too since I was happy with my settings. But really, it's worth just taking the plunge. I went from 5mb to what, over 30mb free and it seems like I have the exact same setup (in fact, MORE programs) and they are on the device and not the card, too.
The standard ROM just really whacks your phone.
The Stock Rom sucks ass. I use TouchIT 4.4 and I'm extremely happy with it.
Thanks for all the info. After looking at some of the threads on the two roms recommended im seriously considering doing so. 3 quick questions....1. Can I revert back to the original rom if needed? If so, how. 2. Is there a feature that my phone has now that these roms do not have? 3. Will flashing the phone with one of these roms void the warantee on my phone? Thanks again!
1. Can I revert back to the original rom if needed? If so, how.
Yes, by running the Stock T-MOBILE RUU
2. Is there a feature that my phone has now that these roms do not have?
Any of the Tmobile crap ... myfaves, hotspot logins ...etc... but you can install most of those with a cab.
3. Will flashing the phone with one of these roms void the warantee on my phone?
Yes. Theoretically. But again, if you ever need to send it in, you can install the Stock Tmobile RUU and hopefully you won't have any problems.
Yeah....better off. I dont need the extra T-mobile crap any ways. Which rom is best? I looked at the one you have and that one seemed better.
btw....what exactly does the page pool hack do?
Different people on here will reccommend different Roms.
ITJE has been around making Herald/Wing ROMs the longest and he's the Godfather of the Herald/Wing Rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
roman2113 said:
btw....what exactly does the page pool hack do?
Click to expand...
Click to collapse
This should help you out:
pof said:
What is the Page Pool?
Quoting mamaich:
The large the paging pool is, the more code pages can present in RAM simultaneously -> the less loads from slow ROM -> the faster the device is.
Quoting Mike Calligaro from Windows Mobile Team Blog:
In general terms, there are a number RAM uses that aren't reported in the Memory CPL.
For instance, an OEM might set aside a fair amount of RAM to allow the camera to write directly into it without using the CPU (a DMA buffer). Typically the way they do that is to tell the system there is less than the available RAM and then use the RAM the system doesn't know about.
Another example is something called the "page pool." This is similar to the "page file" on a desktop system, and is heavilly used on NAND systems. The page pool isn't something a user can configure, so there's not much point in showing it in the Memory CPL.
Code that can't be shut down or paged out, especially drivers, isn't shown on that Memory CPL either. There's no reason to show you the RAM the display driver is using, because you can't do anything about it.
Applications use RAM in two ways. There is code that runs, and there is data that is created while it is running. On a NOR device, the code can run directly from the ROM and not be loaded into RAM first. This process is called XIP (eXecute In Place). NAND devices can't XIP, so their code is loaded into RAM and executed from there. If you don't have a Page Pool, this code is loaded into normal RAM. The Page Pool is a mechanism to limit how much code is loaded into normal RAM. With a Page Pool, we can unload code that hasn't been used in a while and reload it later if we need to. We can't do that without a Page Pool.
More information:
http://forum.xda-developers.com/showthread.php?t=276630
http://blogs.msdn.com/windowsmobile/archive/2005/11/17/494177.aspx
http://blogs.msdn.com/windowsmobile/archive/2005/08/19/453784.aspx
Click to expand...
Click to collapse
Bro...thanks so much! You have been extremely helpful in answering all of my questions. I think I will be trying out the Touch-It rom this weekend. Hopefully this fixes my original problem.
No probs. Anything else, let us know and we'll be glad to help you out.
duprade said:
Different people on here will reccommend different Roms.
ITJE has been around making Herald/Wing ROMs the longest and he's the Godfather of the Herald/Wing Rom.
Click to expand...
Click to collapse
lmao, funny
For those who don't know.. WiFi tethering works flawless now..
Download: http://www.multiupload.com/8HAAG90SA1 ( Htc evo framework blah blah blah)
Also download: http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_2-pre14.apk (Latest WiFi tethering app)
Now youre ready:
1. Download those files.
2. Connect you're phone- and mount your SDcard to your PC.
3. Copy fw_bcm4329.bin to your SDcard, Make a folder on your SDcard called Android.Tether.
4. Paste fw_bcm4329.bin Into Android.tether on your SDcard.
5. Uninstall older versions of WiFi tether on you phone.
6. Install the lastest version of WiFi tether. (NOT MARKET VERSION)
WiFi tethering works flawless now, without the need to set static ip and ping'ing.
Encryption works too
damn, i searched this forum to make sure no other threads about the same, but i only searched this forum and not apps & themes.. sorry for multi thread
this works with 2.1...? root/non-rooted device?
needs rooting, nevermind ;D
Excellent, thanks for posting this!
Didn't know it had been resolved
StrongOneX said:
damn, i searched this forum to make sure no other threads about the same, but i only searched this forum and not apps & themes.. sorry for multi thread
Click to expand...
Click to collapse
No problem, I orginally posted my thread in development, but my thread got moved to themes and apps. I guess it fits better in that section.
http://forum.xda-developers.com/showthread.php?t=697168
Huh?
Stil no response as to which version this works for (2.1/2.2), also, I'm running MCR which comes with Wifi Tether, is this problem existent in that or not?
alias_neo said:
Stil no response as to which version this works for (2.1/2.2).
Click to expand...
Click to collapse
People have reported in that it works on both Eclair and Froyo (at least DeFrost 0.6). Anyway we got an working in-built wifi tether on Froyo now.
alias_neo said:
also, I'm running MCR which comes with Wifi Tether, is this problem existent in that or not?
Click to expand...
Click to collapse
Wifi Tether on MCR doesn't work out-of-box, at least according to mine tests.
Edit: Corrected a quite obvious spelling error.
So why does MCR include it if it doesn't work?
alias_neo said:
So why does MCR include it if it doesn't work?
Click to expand...
Click to collapse
Ask Paul
I was also kind of "fuzzed" by that when I tried wifi tether on MCR, also that it doesn't work is a fairly known problem.
Sweet! It works now
Hmm... maybe not! An iPhone do see the AP but a Desire and a HD2 cannot
It works fully 100%, it's been confirmed numerous times. So problem is on your side, bud
What do you mean Desire can't see it? You have two Desires laying side by side?
Thx so much for this reminder.
vanja said:
It works fully 100%, it's been confirmed numerous times. So problem is on your side, bud
What do you mean Desire can't see it? You have two Desires laying side by side?
Click to expand...
Click to collapse
Yeah, I am at work with my colleagues around me (iPhone, iPhone, Desire and HD2) and the iPhones can see the wireless network and connect to it, whereas the Desire and HD2 cannot even pick it up.
If some phones can see it and others can't what do you think the issue is?
I know that the desire cannot see ad-hoc networks which this method is based on, explains the Desire but I dunno about the HD2.
Froyo's wifi tethering works in master mode though which is lovely and will work on all wifi devices.
I have a question : what type of wifi network is wifi-tether ? adhoc or infrastructure ? Does the phone act as an access point ?
Actually, it is not working a perfectly as it could. My laptop computer sees it as an "unsecured" network although WEP 128bits is enabled and password set. (and it's not a bug from the computer, there are other WEP secured networks available in the area which windows see as "WEP")
Read my post above, it's ad-hoc. WEP seems to work perfectly here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it's optional man, if you don't want it you don't choose it...and there is a way to make it work for someone who wants it badly.
anyway, i just tried the new version and it works great, absolutely awsome on my desire with MCR3.1
oh ok, so that's why. must be some kind of admin restriction on my corporate laptop. my bad.
Poodlemastah said:
Read my post above, it's ad-hoc. WEP seems to work perfectly here.
Click to expand...
Click to collapse
lol, nice AP name at the top of the list
Btw - I can confirm this works fine on MCR r3.1.
Encryption/no encryption and the speed is great.
Did anybody tried the new htc sync 3.0 with htc hero on android 2.1? They say on htc official site that it's working on htc devices with android 2.1 but on web it's said that this update is just for htc wildfire. I cannot download it for a trial for the moment.
I think I got the answer and I will wait. By the way, HTC sync really sucks!
rapsass said:
I think I got the answer and I will wait. By the way, HTC sync really sucks!
Click to expand...
Click to collapse
Don't use it then! oh and it's just for the htc wildfire for now.
It should work for Hero too. Just not on Vanilla builds obviously
Alternative link:
http://www.multiupload.com/U0ZVKIZIR6
btdag said:
It should work for Hero too. Just not on Vanilla builds obviously
Click to expand...
Click to collapse
It works for the HTC Hero, just tested it.
http://www.multiupload.com/IQIPL4FATM (3.0.5387)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
very itunesque
That looks so much better than the old sync. Did you delete Sync 2 before installing? Did you have any problems or was it nice and easy? Are you on a stock ROM?
Duh ..... just looked at your sig - please ignore last question
peterc10 said:
That looks so much better than the old sync. Did you delete Sync 2 before installing? Did you have any problems or was it nice and easy? Are you on a stock ROM?
Duh ..... just looked at your sig - please ignore last question
Click to expand...
Click to collapse
I wasn't using any sync before hand but it's always wise to uninstall anything you have application wise before installing the new versions.
andrewb84uk said:
I wasn't using any sync before hand but it's always wise to uninstall anything you have application wise before installing the new versions.
Click to expand...
Click to collapse
Not true - if the application is written correctly it shouldn't matter whether you have an old version installed. It is incredibly rare than a new version of software will break older ones unless they explicitly state that it will (i.e. there has been a major code/structure change).
It is not a Microsoft update, so it won't break older code.
btdag said:
Not true - if the application is written correctly it shouldn't matter whether you have an old version installed. It is incredibly rare than a new version of software will break older ones unless they explicitly state that it will (i.e. there has been a major code/structure change).
Click to expand...
Click to collapse
It's not true. Well on forums I see people doing 'upgrades' to applications and I see people face problems all the time doing it this method.
Theres plenty apps there has been issues with including java/vmware/flash beta ...... et al.
andrewb84uk said:
It's not true. Well on forums I see people doing 'upgrades' to applications and I see people face problems all the time doing it this method.
Theres plenty apps there has been issues with including java/vmware/flash beta ...... et al.
Click to expand...
Click to collapse
When you consider how many of millions of people update their software like this and out of that you might get a few thousand with problems you're still talking a very minor amount. There is no need to uninstall every app you want to update. This would take ages. I don't care if you want to do it for every app you update but don't recommend this to others as its just going to put people updating software when they should be.
And i've never had a problem updating java, vmware or flash (even using the beta versions) from older versions to newer ones. Java used to leave behind the old ones but it never negatively affected a system (aside from filling up the hard drive). VMWare is worthless anyway (get VirtualBox - support the open source community). Flash is made by Adobe - of course its going to have issues - they make software for Mac's then break the software and release it for PC. Having said this I very rarely have an issue with software updates unless it is explicitly stated on their website that it requires you to uninstall before updating.
hi
I just installed the ver 3 but my hero is not connecting to my pc
any luck or other way to do it
i have performed the follwoing steps
1 installed htc sync 3 over 2.0.33 i had both the sync on my pc but ver 3 was not working, so i unstalled 2.0.33, tried again
no luck
2 then i unistalled ver 3 as well restarted my pc installed sync 3 again no luck
any idea how do we can get this to work
by the way on my hero just upgraded to villainRom ver 12
please advise
Dont hurry!
Hey guys,
The HTC Sync DOES and DO work with HTC Hero.
I did uninstall the previous version and drivers and installed the new one. Yes it does tell you that its not recognized and the HTC Sync is not found on your computer when the phone trying to search for it. But I left it connected to go and search on Google to find out why, Guess what .. It run by itself telling me that I have Hero phone and what I should call it!!
Now I am syncing my stuff and its just working fine, just leave it for 2-3 minutes and it show up by itself
sbsxaid said:
Hey guys,
The HTC Sync DOES and DO work with HTC Hero.
I did uninstall the previous version and drivers and installed the new one. Yes it does tell you that its not recognized and the HTC Sync is not found on your computer when the phone trying to search for it. But I left it connected to go and search on Google to find out why, Guess what .. It run by itself telling me that I have Hero phone and what I should call it!!
Now I am syncing my stuff and its just working fine, just leave it for 2-3 minutes and it show up by itself
Click to expand...
Click to collapse
Thats probably because its installing drivers and detecting the correct phone et al. Glad it works.
Oh, forgot to mention..... when u plug in your usb select sync from the menu...
Sent from my HTC Hero using XDA App
Greetings folks,
I am able to pick up mu phone ok but failes to see the sd card,
See the attached image for more info,
Rebooted phone and computer and also removed and replaced sd card.
Any one got any thing to help with this ?
Ps i am using SenseHero B5.1
Steven_belfast said:
Greetings folks,
I am able to pick up mu phone ok but failes to see the sd card,
See the attached image for more info,
Rebooted phone and computer and also removed and replaced sd card.
Any one got any thing to help with this ?
Ps i am using SenseHero B5.1
Click to expand...
Click to collapse
It might not work with that ROM, try asking someone to try it who is using that ROM to see if they get the same effect.
andrewb84uk said:
It might not work with that ROM, try asking someone to try it who is using that ROM to see if they get the same effect.
Click to expand...
Click to collapse
Yeah thought this so going to try the orange 2.1 rru,
Will report back later tonight.
I've tested it with VR12, it doesn't work. Tried it with 2.1 RUU and it worked.
I'm getting the error: 800705B4 when trying to update my phone.
So I found a solution on Microsoft's website.
However, the instructions say turn the phone off, which is fine.
Then turn it on, which is fine. But then hold the camera button immediately after turning it on to put it into update mode and this should appear on the phone's screen:
http://i51.tinypic.com/2euibkj.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I hold the camera button (the call button), nothing happens and it just boots as normal.
Help please?
You can not update your phone as it is not a Native Windows Phone device
Regards
I see. So none of us HTC HD2 WP7 users will be able to update unless we flash a new rom or something?
ive been trying to find out exactly what is happening, i suspect its driver related, or at least partially driver related. ive been trying to find out exactly what is happening and why it doesnt work, but i cant find out exactly what driver is installed when a HD7 goes in to update mode,
ive asked on the HD7 forum but no one seems capable of telling me what VID and PID is associated with the device when it goes in to update mode.
dazza9075 said:
ive been trying to find out exactly what is happening, i suspect its driver related, or at least partially driver related. ive been trying to find out exactly what is happening and why it doesnt work, but i cant find out exactly what driver is installed when a HD7 goes in to update mode,
ive asked on the HD7 forum but no one seems capable of telling me what VID and PID is associated with the device when it goes in to update mode.
Click to expand...
Click to collapse
Let me know if you find a solution.
And out of interest, does everyone get this problem when trying to update?
Because I haven't seen any threads similar to this one on xda, and I would've thought at least one person would have tried to update and reported their error by now?
I do. I also can't enter in update mode with my HD2. Absolutely the same situation as you ...
ive given up, i dont have the money to get an HD7 and the hassle of trying to get someone else to do things to their HD7s is too much, im still very much of the opinion that at the very moment updating fails, Windows desktop identifies the device as a LEO device, its not a coincidence, it might not be the whole story but im sure its a big part of it.
to be honest, i really cant be bothered updating the ROM or reflashing as we will need to do, im going to wait until we have some worthwhile updates, ideally even some kind of back up program so i wouldnt need to do it again, in the mean time it works just perfect the now so im not to fussed.
Awesome_Space said:
I do. I also can't enter in update mode with my HD2. Absolutely the same situation as you ...
Click to expand...
Click to collapse
Look people..YOU CANNOT UPDATE THE HD2 WP7 ROM USING ZUNE NOR ANY OTHER TOOL CURRENTLY OUT THERE!!!!
WPSupportTool does NOT work on the HD2. Chevron7 Updater (in my case and I haven't heard anyone else having success) does not work neither!!!!
As for not flashing any new updates to WP7, to each is own, but how much stuff have you got loaded on your phone that you wouldn't want to re-flash with WP7 releases?
I personally can have all my contacts, calendar entries, most of my marketplace and sideloaded apps, and 6 email accounts loaded on to my phone after a flash inside 45 minutes. And it wouldn't take long to put customer ringtones and alerts, and any music/video on there through Zune. It's not as though we have anything to flash again anytime soon. Release 7008 is it until the NoDo release is put out by DFT. Who knows when that is coming, although I've heard gossip it's supposed to be in the next couple of weeks.
Chill mate, think he gets the picture already, we know it doesn't work, I would like to find out why it doesn't, its nit a matter of being impossible, its a matter of finding out why! As for reflashing, I have several apps that are essential, they do not support skydrive so any reflash will mean me losing the data, although in saying that, with everything being sandboxes it might be possible to manually locate and copy it....hmmm there's an idea =). Next project set!
of course, little bit later, we can hack more easily then now. but when i connect the phone to pc. it identifies hd7.
kasapoglu said:
of course, little bit later, we can hack more easily then now. but when i connect the phone to pc. it identifies hd7.
Click to expand...
Click to collapse
yes it will until you put it in to update mode where by its identified as a LEO, the phone wont update unless in update mode
dazza9075 said:
we know it doesn't work, I would like to find out why it doesn't, its nit a matter of being impossible, its a matter of finding out why!
Click to expand...
Click to collapse
Yep, pretty much this.
I want to find out why it doesn't work, and if there's a solution.
Osca said:
Yep, pretty much this.
I want to find out why it doesn't work, and if there's a solution.
Click to expand...
Click to collapse
If there was a solution, I think the XDA cooks would have found it by now. Demanding aren't we. WP7 was never supposed to be run on the HD2. The entire OS and UI was built around hardware criteria driven by Microsoft to the phone manufacturers.
Error Code
I also get an error code : 80180048 when I try to update my hd2 win7 with zune. Has anybody also received this message and has it been fixed by anyone yet? Will we be updating any time soon without re-flashing?
80's Pecho said:
I also get an error code : 80180048 when I try to update my hd2 win7 with zune. Has anybody also received this message and has it been fixed by anyone yet? Will we be updating any time soon without re-flashing?
Click to expand...
Click to collapse
Are you serious dude?
hjhjhj said:
If there was a solution, I think the XDA cooks would have found it by now. Demanding aren't we. WP7 was never supposed to be run on the HD2. The entire OS and UI was built around hardware criteria driven by Microsoft to the phone manufacturers.
Click to expand...
Click to collapse
So we souldnt even bother to try and work stuff out because "someone else" will fix it?
There is a patch available for a Samsung phone for this very error.
Perhaps it holds the key to solving this issue on HD2?
http://forum.xda-developers.com/showthread.php?p=12640984
ozzy lion said:
There is a patch available for a Samsung phone for this very error.
Perhaps it holds the key to solving this issue on HD2?
http://forum.xda-developers.com/showthread.php?p=12640984
Click to expand...
Click to collapse
Tried this, The phone is not recognized by Windows Phone Support Tool .
Regards
Just bumping this thread to check if a fix is available yet; does a fix exist yet?
nope there isnt im afraid