Closed
Bug 1144637
Opened 9 years ago
Closed 9 years ago
[Shinano][Aries] Invalid WiFi MAC address
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
2.2 S8 (20mar)
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
Maybe the root cause of bug 1144623. STR: 0. Get a Z3/Z3 Compact device, look at MAC address in Settings, WiFi 1. Get another Z3/Z3 Compact device, look at MAC address in Settings, WiFi Expected: Different MAC address Actual: Same MAC: 02:90:4c:c5:12:38
Assignee | ||
Comment 1•9 years ago
|
||
So that's default MAC address. Looks like we lack pushing the /system/bin/taimport blob.
Assignee | ||
Comment 2•9 years ago
|
||
Pushing /system/bin/taimport gets me a better MAC address, but now my device is always "offline" in adb :(
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #2) > Pushing /system/bin/taimport gets me a better MAC address, but now my device > is always "offline" in adb :( And that's solved by ro.adb.secure=0 in default.prop
Assignee | ||
Comment 4•9 years ago
|
||
Not sure why this slipped through, I was convinced we already had this blob in place. We also need ro.adb.secure=0 otherwise adb is constantly 'offline'.
Attachment #8579351 -
Flags: review?(mwu)
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(wcosta)
Flags: needinfo?(drs)
Comment 5•9 years ago
|
||
Isn't ro.adb.secure something that's set depending on your build type? Not too comfortable overriding that property..
Assignee | ||
Comment 6•9 years ago
|
||
Not that I know off, it's used to control the adb authentication stuff as far as I could find.
Comment 7•9 years ago
|
||
Comment on attachment 8579351 [details] [review] Shinano common PR Alright then. Thought I think we should get support for secure mode at some point. ADB locking itself out when the lock screen comes up is insane.
Attachment #8579351 -
Flags: review?(mwu) → review+
Assignee | ||
Comment 8•9 years ago
|
||
From https://www.codeaurora.org/cgit/quic/la/platform/system/core/tree/adb/adb.c?h=kk_3.5_rb4.1#n1287 : > property_get("ro.adb.secure", value, "0"); > auth_enabled = !strcmp(value, "1"); > if (auth_enabled) > adb_auth_init(); I think it's pretty clear :)
Assignee | ||
Comment 9•9 years ago
|
||
(In reply to Michael Wu [:mwu] from comment #7) > Comment on attachment 8579351 [details] [review] > Shinano common PR > > Alright then. > > Thought I think we should get support for secure mode at some point. ADB > locking itself out when the lock screen comes up is insane. I remember seeing a bug for this, but I'm unable to find it :(
Assignee | ||
Comment 10•9 years ago
|
||
https://github.com/mozilla-b2g/device-shinano-common/commit/2edf7771f1b5e5cf39ea1d24d821b246a050c0aa
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Flags: needinfo?(drs)
Updated•9 years ago
|
Whiteboard: [systemsfe]
Target Milestone: --- → 2.2 S8 (20mar)
You need to log in
before you can comment on or make changes to this bug.
Description
•