806979 - Some info fields (like wifi hotspot) do not show any information after updating; this does not happen on devices that have just been re-imaged or reset

Status: RESOLVED DUPLICATE of bug 813764

(Firefox OS Graveyard :: Gaia::Settings, defect, P3)

Description

[Armen [:armenzg]]

The first time I tried to enable the wifi hotspot I started tapping on the name, password and security expecting them to do something.
I thought something was broken.

After a while I realized that the hotspot was working even if those fields showed nothing interesting. This realization came when I tapped on the "HotSpot Settings" button.

It would be nice to make use of the 3 mentioned fields or remove them completely.

This was confusing to me and I bet will be for others.

Comment 1

[KM Lee [:rexboy] (inactivate after Sep. 22)]

I have made a patch that fine-tuned the style on these fields, including not to change background color when tapping, and remove the separating line between these fields, to decrease misleading.  Will this solve the problem?  Completely remove the fields may be somewhat inconvenience because we still need to confirm the Hotspot name.

Comment 2

[Armen [:armenzg]]

The fields were not showing *any* text.

The same happens when you tap on "Settings" -> "Device information" on the first 3 fields (Model, OS Version, Last updated). When you tap on "More information" the fields Platform version, Build Identifier and Update channel are also empty.

Could you also fix these extra 6 fields as well? Perhaps we can adjust the title of this bug to be more accurate?

Comment 3

[KM Lee [:rexboy] (inactivate after Sep. 22)]

These fields do have information shown on my Unagi phone except for the update date.  What's the platform used here?
Tested on Unagi with
Gaia: 16fda9  (Nov.4)
Gecko: 1aacbf (central, Nov.4) / dea182 (aurora, Oct.29)

Comment 4

[Robert Kaiser]

(In reply to KM Lee [:rexboy] from comment #3)
> These fields do have information shown on my Unagi phone except for the
> update date.

Is that on a freshly flashed image or have you applied an update at least once? IIRC, this always worked for me on otoro on a freshly flashed image and broke with the first applied update.

Comment 5

[Armen [:armenzg]]

I've reset my phone yesterday and the fields now show information:
Name: FirefoxHostSpot
Password: whatever
Security: open
###########################
Model: nice
OS Version: 1.0.0

Comment 6

[KM Lee [:rexboy] (inactivate after Sep. 22)]

I tried again on 11/11 (nightly channel), updating to the latest one (11/14) and these fields works good for me except that "Last Updated" field doesn't show up (this is bug 809974).  I'll try do some more updating for a few days. if this won't happened again, maybe we can close this bug after 809974 get fixed?

Comment 7

[Robert Kaiser]

Yes, I also saw this start to work some time IIRC last week, only the "Last Updated" field remains blank now.

Comment 8

[Armen [:armenzg]]

I'm on 11-06 stable channel and all of the fields are blank for me.

Comment 9

[KM Lee [:rexboy] (inactivate after Sep. 22)]

I've tried serveral cases like:
1. Flash 11-06 stable image into unagi 
2. Flash 10-17 stable image and upgrade to 11-14
3. delete IndexDB and reboot
but can't reproduce this problem.  The only way I found to blank out these field is just delete /data/local/indexedDB/chrome, then kill & reopen settings app, and these fields god blank out.  But this is not what a user will do, and in this case it will get fixed once reboot. so I can't conclude the root cause are the same.  Is there any reliable way that could make this happen?

Comment 10

[Armen [:armenzg]]

I'm on 11-14 and the fields are not blank anymore.

Nevertheless, I have found another bug.

If you change the name, password or security of your hospot the fields will always be:
"FirefoxHotSpot", "1234567890" and "open".

On another note, it doesn't matter if I setup the connection to be WPA2 it will *always* connect as if I had no password. I can nevertheless change the SSID.

Comment 11

[KM Lee [:rexboy] (inactivate after Sep. 22)]

Thank you for reporting!

For the latter one, is it the same one as bug 806758 and bug 813764?  Since it's working in progress, let's close this bug and if the setting fields disappears again , we can reopen it.