I was on my way out to go rock climbing with my wife when a US census taker was making the rounds at our condo complex, he was using one of the HTC/Harris Census handhelds.
{
"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"
}
The ONLY visible difference was that the Harris logo was on the top left and the HTC logo was on the top right of the case. The HTC Melbourne is named for the Harris' hometown of Melbourne, FL.
No, it does not have a keyboard like reported in other stories.
I did not find out what carrier network the device was on, so no idea was type radio is being used. Or even if the radio was enabled for voice/data or data only.
It looks a lot more rugged than ANY regular HTC device.
http://blog.htc-unlocks.com/2008/11/29/htc-melbourne-htc-converse/
And contrary to Olipro's blog... The Census subcontractor DID NOT act like a "census nazi", he was quite pleasant actually. He did not ask to take fingerprint scans or for any personal data at all, right now the device appears to be strictly to accurately map street address data to GPS coordinates.
I have a friend who is starting with the Census Bureau in the next week or so, I am going to try to get a better look at one the devices.
Here is Service manual for this rare device
http://rapidshare.com/files/209478659/HTC_Melboume__SM_A03.pdf
Here is what I have found out:
The contractors receive 2 days of inside training and then a day of field training. The rank and file have to turn the device in to their team leaders at the end of the day. Team Leaders and QC are allowed to take their devices home. Part of the training does involve the data transfer, either OTA or via the RJ-11 modem.
The device boots to the mapping software, so they end user does not see the underlying WinMo OS. The devices are activesync capable and any work done happens at the regional office the device is assigned to. My contact did not see what was done prior to servicing the device but I suspect that the device was put into bootloader mode and reflashed. They were able to confirm that the device was connected to a Windows PC and that there was some type of remote diagnostic software used prior to the re-flash. Sorry, my contact is not a tech person so some of the specifics are lost on them.
The users are required to sign several NDA's prior to the device being issued to them. The serial # and asset id # are mapped to that user for Inventory control. The fingerprint scanner is used for user login only "at this time"...
The first phase of the contract runs until June of this year, so I will have quite a few chances to actually get my hands on one. If I do, I'll try to dump the ROM to SD Card using BuzzLightyears Grab-It. But I am going to wait on that until the end of the Phase 1 contract.
Screen to small for me and no physical keyboard
Thanks anyway for sharing
RiverRat812 said:
I'll try to dump the ROM to SD Card using BuzzLightyears Grab-It. But I am going to wait on that until the end of the Phase 1 contract.
Click to expand...
Click to collapse
I work for the census and your comments trouble me. You would do well to abandon this idea. You know better than to tamper with our machines. Need I mention the oath you took, or the prison sentences listed in your manual?
Someone from the census bureau came to my house and immediately I was intrigued by this device. I didnt ask to see it, but tried very hard to get a better look at it. I could swear it had the verizon logo on the front of it instead of the logo pictured, but they look so similar I could be mistaken. Although useless to anyone who does not work there it would have been neat to play with.
Related
Hey all!
Ok so i have rooted the rogers dream to i could tether the phone to my PC. now i have done this i cant see to tether, i have tried 2 different apps (code.google.com/p/android-wifi-tether/ and tetherWifi)
I dont seem to get an error message from the first tether program but the second seems to say "error: su: access granted"
Is there some way that maybe the app has not been given super user access?
Thanks!
Any help would be amazing
I am pretty sure to tether you have to call into Rogers and get tetheing activated first. I know for the iphone you have to do this. It should be the same deal with the Dream.
phantom1260 said:
I am pretty sure to tether you have to call into Rogers and get tetheing activated first. I know for the iphone you have to do this. It should be the same deal with the Dream.
Click to expand...
Click to collapse
WHAT?????? Are you serious, thats the worst advice ever. You don't call them up to have it activated. I'm sure Rogers is like T-mobile and frown upon tethering cause it hogs up bandwidth.
Yea and while your at it tell them you rooted your phone. Tethering involves 0 help from your carrier, all your doing is sharing the connection from your phone so if it's not working something isn't setup right.
Also since bad advice is being given out. Go ahead and flash the new spl with the old radio. I heard that turns your phone into something cool.
Ya i know it sounds wierd but i guess there allowing it to sell larger data plans or soemthing.
I double checked on the Rogers site it says you have to have a minimum 1GB data plan to do tethering.
Thats why i thought you have to call in because the iphone prompted me to call in when i was trying to do it with a 512 MB data plan.
Scroll down to the bottom and you will find the tethering FAQ this page is for the iphone but i'm sure same rules apply to the Dream
http://www.rogers.com/web/content/wireless-products/iphone_faqs
{
"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"
}
@Phantom - Dude really just STFU.
@tiptop33 - Make sure you are rooted and that you have USB Debugging turned on. Without USB Debugging the SU app will sometimes timeout.
Fingerlickin said:
@Phantom - Dude really just STFU.
@tiptop33 - Make sure you are rooted and that you have USB Debugging turned on. Without USB Debugging the SU app will sometimes timeout.
Click to expand...
Click to collapse
LOL... Do we need to throw up a pic..... ok you made me with that comment.
Whose doing our Wreckin Crew graphic?
Well first off.. rogers in there plan you can tether why the hell would i call them and ask for it??
but yeah i think i found the problem i needs some program that allows and disallows apps access but dont know what its call!
But yeah thanks for the help eh!
Checked for an update and got this. It is about 21MB.
{
"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"
}
Most of us have it already
wseyller said:
Most of us have it already
Click to expand...
Click to collapse
I just saw this now so I'm updating it now. How come my phone didn't automatically tell me about the update? I would think it would tell me as my other phones have in the past. I'm crossing my fingers this update helps my wifi issues.
RobinsonR810 said:
I just saw this now so I'm updating it now. How come my phone didn't automatically tell me about the update? I would think it would tell me as my other phones have in the past. I'm crossing my fingers this update helps my wifi issues.
Click to expand...
Click to collapse
My IMS wasn't registered and this fixed it. Thats why I took it.
civiksi said:
My IMS wasn't registered and this fixed it. Thats why I took it.
Click to expand...
Click to collapse
I took tbe update and my IMS is still unregisterd. What does that mean? How can i fix it?
djbling said:
I took the update and my IMS is still unregistered. What does that mean? How can i fix it?
Click to expand...
Click to collapse
IMS = IP Multimedia Subsystem
IP = Internet Protocol
SIP = Session Initiation Protocol
With setting off, SMS is sent/received over 1x circuit switched connection
With setting on SMS is supposedly sent/received over a SIP session over IP (e.g. LTE)
I got this from another thread. Did you try rebooting it again? When its registered I definitely sent and received texts much faster
civiksi said:
IMS = IP Multimedia Subsystem
IP = Internet Protocol
SIP = Session Initiation Protocol
With setting off, SMS is sent/received over 1x circuit switched connection
With setting on SMS is supposedly sent/received over a SIP session over IP (e.g. LTE)
I got this from another thread. Did you try rebooting it again? When its registered I definitely sent and received texts much faster
Click to expand...
Click to collapse
Thanks, I've rebooted still un-regested. I"ll try a factory reset later
RobinsonR810 said:
I just saw this now so I'm updating it now. How come my phone didn't automatically tell me about the update? I would think it would tell me as my other phones have in the past. I'm crossing my fingers this update helps my wifi issues.
Click to expand...
Click to collapse
This update was the Day One update that should have been installed the day you purchased the phone. It is sort of like a last minute final version of the software that should have been on the phone before you got it. Never did find out any information about what it covered.
Ally Android said:
This update was the Day One update that should have been installed the day you purchased the phone. It is sort of like a last minute final version of the software that should have been on the phone before you got it. Never did find out any information about what it covered.
Click to expand...
Click to collapse
I'm still on 21.21.12 and I never updated, my phones seems to be running fine..
Sent from my XT1254
Never updated here either
Found out that you must register the IMS on your My Verizon page. It's under features(no extra charge):laugh: For some reason you can't do it on your phone, you must do it from a computer. After registering I got the "Voice HD" or "VoLTE" updatehttp://cdn3.xda-developers.com/images/smilies/laugh.gif
Ally Android said:
This update was the Day One update that should have been installed the day you purchased the phone. It is sort of like a last minute final version of the software that should have been on the phone before you got it. Never did find out any information about what it covered.
Click to expand...
Click to collapse
It added VoLTE.
meskes said:
It added VoLTE.
Click to expand...
Click to collapse
The VoLTE patch was not the day one patch. There have been three OTAs for the Turbo so far.
21.21.15 was a last minute bug fixer.
We think the Lollipop output. Do not like
Hello everyone, hope I will get at least some answer to my issues that I am having with my Lumia 1520, otherwise, I will just throw it away and get back to Android (which I would really like to avoid).
Anyway, a while ago, as in about a year, I have jumped on Fast ring on my Lumia 1520, Wind Black edition (not network locked).
As time passed by, it was ok experience. Yes, WP had issues, and what not, but overall everything worked ok. I got my phone Dev unlocked while it was still on 8.1 but never fiddled with any interops, hacks or anything like that.
So, somewhere after they have removed Astoria subsystem, I started to experience some game breaking issues. Namely, computer doesn't detect my Nokia at all anymore. Mind you that it is not cable issue, it is not port issue, and since a friend of mine also on 1520 experienced the same issue (also on Fast ring), as well as few people online that I saw, I highly doubt it is hardware issue. As said, in one Astoria included build, I had no issues connecting phone to computer, pushing Android apps, removing them etc. Then on, I think that it was next build when Astoria was removed, but I cannot say for sure since it was long ago, and at the same time I though it was a bug in Preview version (which you can expect considering its developers build), and as said, friend also had the same issue.
So basically, when I connect my Lumia to computer(tried on few different computers, havent tried on Linux since I don't have one and heard that its not working on virtual machines), I can hear audible ping from the computer that something is attached, as well when I restart it (Vol Down+Power) I hear audible that something is removed. Phone charges fine via wall charger, as well as with USB, with notification that "Phone is charging slowly" with USB to PC cable...
However, during both cases, I don't see anything pops up in Device manager, nor gets removed after removing Lumia. Obviously, I cannot roll back to 8.1 since Recovery tool doesn't detect it either. I recall that at one point, I have tried following. Attach phone, run recovery, restart it and press Vol Down so that Exclamation mark pops in and during that time recovery detected the phone and started downloading some image. That is how I figured out which my product code is 059V743 RM-937 IT Wind Black. Figured, well, if I get pissed too much, now I know how to get recovery to detect my phone. Except with the latest build (10586.164) it no longer works. Apart from that, phone works just fine.
I have noticed when I have removed Nokia Recovery tool (had both since both were on Windows site to download), once phone was detected as Nokia Boot Mgr or something like that since I didn't paid attention and it installed the files rather quickly...
So, any info on what to try, or where to look (I did searched but nothing that I have googled worked), is much appreciated. As said, tried on different computers, different cables, some also have the same issue, so please skip those advices since I have already tried it. Phone didn't dropped single time, didn't jerk the cables and anything similar, so I doubt it is HW issue anyway.
Thanks and sorry for the long post
I will use this post to politely bump this, since I think this is the first time that I saw 0 reply threads here on XDA
Anyway, after messing around with Vol Down+Power, then Vol Up, firing Nokia recovery tool as well as Windows Device Recovery Tool (yeah I am that desperate now), WDRT detected the phone but with no info on either OS or Firmware on my Lumia. Can someone verify for me please that offered avail image on the server match my Lumia 1520 Wind Black?
{
"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"
}
Thanks
Download the firmware files from here:
http://www.lumiafirmware.com/guid/059V743
Create a folder RM-937 under C:\ProgramData\Microsoft\Packages\Products\ and unzip/move all the firmware files to it. You should be able to flash using WDRT. If that doesn't work then try flashing with Nokia Product Support Tool for Store.
pankaj981 said:
Download the firmware files from here:
http://www.lumiafirmware.com/guid/059V743
Create a folder RM-937 under C:\ProgramData\Microsoft\Packages\Products\ and unzip/move all the firmware files to it. You should be able to flash using WDRT. If that doesn't work then try flashing with Nokia Product Support Tool for Store.
Click to expand...
Click to collapse
Thanks for response Pankaj, I did downloaded that files, but had no idea where to put them. Will wait for this "final" release to be pushed, to see if anything will happen, and then give it a go and let you know.
Again, thanks for the suggestion, since I am kinda desperate, since, closest Nokia Care (I don't want to go to local services since they will come with some stupid idea that board is fried or something like that) is in like Hungary or something, which is little too far for me
Cheers
Edit: Managed to revert back to 8.1 using the guide I have posted here
http://forum.xda-developers.com/windows-phone-8/help/guide-how-to-downgrade-corrupted-wp10-t3339465
Hi all - I've searched everywhere but cannot find an answer, would be grateful for any suggestions.
I have a New Zealand Note 9 from 2degrees and since getting it a few weeks ago have been getting a strange sound notification which is somehow related to wifi. It occurs when I come home and when out and about and seems to be due to something like the presence of open wifi connections or maybe something to do with wifi calling. Its an odd sound as well, 4-5 robotic notes and its not one of the notification sounds that you can choose from.
Things I've tried from looking at multiple forums:
NFC and bluetooth off
Accessibility notification off
Reset all notifications settings
The main solution seems I've seen is to turn off the setting "notify me when wifi is available or connected" in the wifi advanced settings, but I do not have this option.
{
"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"
}
Any suggestions would be much appreciated!
Cheers SH
https://forum.xda-developers.com/galaxy-note-9/help/damn-network-notifications-t3844569
Sent from my SM-N960U1 using Tapatalk
Thanks, but saw that post and already tried everything in it. Cheers SH
shshsh_nz said:
Thanks, but saw that post and already tried everything in it. Cheers SH
Click to expand...
Click to collapse
If you go to Apps then click the three dots at the top right hand corner and show system apps. The select "android system". There is plenty of network notification options there to try.
Sent from my SM-N960U1 using Tapatalk
Two things you can do
1. if rooted you can use an xposed module to disable notifications for that
2. other way is you can use app quarantine pro or greenify or some other app to freeze "settings" which blocks the wifi popup, although I'm not sure if that works for your android version but it does work for mine which is kitkat and s5... still might work on new devices
Thanks Limey - had already done that.
Great suggestions zxzxzx......will try those apps and if not successful will root. Was on the fence about rooting but it looks like this may work and the phone is driving me mad.
Also, Pie update is due any day in New Zealand, maybe that will fix it.
Cheers SH
Hi all
Thanks again for the suggestions. It's driving me mad and I may well sell the phone and take a hit.
One more clue...it seems to happen a minute or so after I use the phone, turn it off and then start walking around. Don't think it is location services as does it with location off. And don't think it is when it finds open wifi networks as it happens when in the middle of nowhere and no wifi nearby. Happens nearly every time I go from home office to lounge. Happens with BT, NFC, data roaming all off.
Factory reset did not help, happened straight away, even with no new apps installed.
Could it be related to wifi calling somehow? I need this feature though as have little cell coverage at home. No options to change any wifi calling settings though, other than on and off.
Cheers SH
shshsh_nz said:
Hi all
Thanks again for the suggestions. It's driving me mad and I may well sell the phone and take a hit.
One more clue...it seems to happen a minute or so after I use the phone, turn it off and then start walking around. Don't think it is location services as does it with location off. And don't think it is when it finds open wifi networks as it happens when in the middle of nowhere and no wifi nearby. Happens nearly every time I go from home office to lounge. Happens with BT, NFC, data roaming all off.
Factory reset did not help, happened straight away, even with no new apps installed.
Could it be related to wifi calling somehow? I need this feature though as have little cell coverage at home. No options to change any wifi calling settings though, other than on and off.
Cheers SH
Click to expand...
Click to collapse
Turn wifi off , that'll stop it. Lol
Sent from my SM-N960U1 using Tapatalk
During the last daylight savings time update, my 2020 Subaru Legacy got messed up and jumped a GPS Epoch, the car now thinks its the year 2040.
This throws a Communication Error 8 whenever I try to use Android Auto, manually setting the time does not work.
Reading Subaru forums, it seems that only replacing the cars central computing unit can reset this time, but that theres a several month delay getting the parts due to chip shortages. But with Covid ending I got a lot of driving to do this summer.
I have a Pixel 2XL thats rooted with Magisk and was wondering if there was any way to bypass this error and get AA working?
{
"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"
}
dehelfix said:
During the last daylight savings time update, my 2020 Subaru Legacy got messed up and jumped a GPS Epoch, the car now thinks its the year 2040.
This throws a Communication Error 8 whenever I try to use Android Auto, manually setting the time does not work.
Reading Subaru forums, it seems that only replacing the cars central computing unit can reset this time, but that theres a several month delay getting the parts due to chip shortages. But with Covid ending I got a lot of driving to do this summer.
I have a Pixel 2XL thats rooted with Magisk and was wondering if there was any way to bypass this error and get AA working?
View attachment 5284337
Click to expand...
Click to collapse
What does the vehicle dealer suggest.
marchnz said:
What does the vehicle dealer suggest.
Click to expand...
Click to collapse
Swap the central computer is the only fix they know, when they get the part, which might be months. According to others its happened to, that fixed the issue, but at least one person had it come back later...so clearly an issue in their software. But not very optimistic i'll get it fixed anytime this summer...so thought there might be something i could do to trick it into thinking its the right time set via a magisk module or root app or something.
Have they tried to re-flash your Subie?
Here are my technician notes from the dealership:
per techline- this is a known issue, engineers are working on software update to correct concern but not available yet with no known timeframe for availability. for customer satisfaction ordered new cockpit control unit to correct issue. techline states- replacement CCU will correct concern, but does not know how long until concern returns, may not return. also stated, android auto compares time stamps from cellphone network to time stamps with gps network from car, if finds correlation issue will not pair phone. CCU on order/will call customer when it arrives
Got a replacement CCU, Android Auto working again.