belodion
Member
I've desired W10 on my own 1020, but it's a precious phone on account of its camera, so I've decided that it may be best to leave it on 8.1 where all is good and working.
I've desired W10 on my own 1020, but it's a precious phone on account of its camera, so I've decided that it may be best to leave it on 8.1 where all is good and working.
I updated my L1020 to W10M CreatorsUpdate. I have not Lumia Camera app now.
Anyone know how to install this app?
Also, I am looking for a way to make this (formerly AT&T) phone allow "hotspot mode". (This has never worked with any Win version.)
Try the registry hack from this thread: http://forums.windowscentral.com/cricket/439696-cricket-hotspot-advice-thread.html
3 bugs in CU:
- cannot turn off Bluetooth;
- Maps dont work;
- no Lumia Camera.
My L1020 -- masquerading as a 950 -- just updated to build 15210.00 (from an earlier W10 build) yesterday. Since I am dumbly optimistic by nature, I did let it do so.
I am still testing things out. The good news is that the Skype mic is now working. The bad...
...as expected, Lumia Camera went AWOL. I then reverted the registry to the normal L1020 identity, which in the past led to the eventual recovery of Lumia Camera. This has yet to happen.
Perhaps it will come back with a trick someone knows for Lumia Camera and I don't?
Also, I am looking for a way to make this (formerly AT&T) phone allow "hotspot mode". (This has never worked with any Win version.)
I had this issue too. Then I had to edit registry and change a field that shows the phone`s name as 909. Change it to Lumia 1020. Save and go to Store!
It is strange as Nokia camera app is very old. Started with Nokia Pro Cam then was renamed to Nokia Camera and then Lumia camera. Nokia camera may lack RAW support it your phone can capture the files. It needs Lumia Denim software. Changing the name out the phone in registry, will let you get the latest software with the latest codecs and the most quality out of your camera.Thanks John! I actually got the "Nokia" Camera when I finally decided to do the hard reset. This made me happy enough.
Since I've always wondered if "Lumia" and "Nokia" cameras are really really the same thing, I am planning to take a few pixes as "Nokia" for later comparison. Then, doing what you suggest, I may be able to repeat the same shots under "Lumia".
That said, as far as I remember, their interface and features set is the same.
Interestingly, so far, the "focusing chasing" that I experienced with Lumia Camera under the previous W10 rev. seems to be gone. It focuses like a champ. Don't know if it is:
-- a short-lived thing
-- Nokia Camera
-- or the current Win10 version. (I do hope it is this new W10 version but would not advice to try it yet...I have not fully tested it)
I have always had this issue on 10586.xxx too - the fix for me is to make sure none of the WiFi networks saved on the phone have "connect automatically" ticked, then the hotspot seems to work fine....
I had this issue too. Then I had to edit registry and change a field that shows the phone`s name as 909. Change it to Lumia 1020. Save and go to Store!
Many thanks, anon(10169102). I spent hours trying to enable the hotspot function yesterday. Once I did, the next hobby-frustration was not being able to retain the hotspot if the screen lock returned. Under wall power, this was no issue because I tweaked for a "Never" choice on the lock screen options...a desperate something that I only figured out at 3am this morning.
Up by 9am, I logged in here for other purposes. The, Tah Dahh!!! The accidental discovery of your suggestion was a blessing. I ticked off the "automatic" for each Wi-Fi connection and it worked like charm!!!*
*For others: Only those Wi-fi connections that have been used in the past and have passwords need to be ticked off. You don't need to disable any of the others in the long list of "available" that may show, even if they show "connect automatically" as on. AND, this relates to keeping the hotspot service "alive" even when the lock screen turns the screen off. Tested on L1020 with build 15210 (not all my key issues yet resolved), registry access via Interop Tools RC3.