New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 674984 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Device issues on build68-b1

Project Member Reported by mikec...@chromium.org, Dec 16 2016

Issue description

The device attached to this machine appears to have a popup saying...

"Android System. There's an internal problem with your device. Contact your manufacturer for details"

If someone could take a look at this device it would be great. The device might need a new Android build? It is the only device with N AOSP, so that might have something to do with the problem.

This is link to bot having issues.
https://uberchromegw.corp.google.com/i/chromium.android/builders/Android%20WebView%20N%20%28dbg%29
 
screen.png
477 KB View Download

Comment 1 by pschm...@google.com, Dec 16 2016

Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)
Online it seems to say that the issue is caused by having different /vendor/build.prop and /system/build.prop. It appears this is the case......



chrome-bot@build68-b1:(Linux 14.04):/b/c/b/Android_WebView_N__dbg_/src$ third_party/android_tools/sdk/platform-tools/adb shell cat /vendor/build.prop

ro.vendor.build.fingerprint=google/bullhead/bullhead:7.0/N5D91L/3425233:user/release-keys
.
.



chrome-bot@build68-b1:(Linux 14.04):/b/c/b/Android_WebView_N__dbg_/src$ third_party/android_tools/sdk/platform-tools/adb shell cat /system/build.prop

ro.build.fingerprint=Android/aosp_bullhead/bullhead:7.1.1/NYC/3518060:userdebug/test-keys
.
.


Not really sure of fix though. Do you guys have any idea what to do?

Comment 3 by pschm...@google.com, Dec 16 2016

That popup is not there anymore.

It's currently running Android/aosp_bullhead/bullhead:7.1.1/NYC/3518060:userdebug/test-keys

What do you want me to flash it to?

Comment 4 by pschm...@google.com, Dec 16 2016

Re: #2  I've seen this before when a device is updated rather than flashed from scratch.

Anyway let me know what version if N you want installed.
Any N AOSP build. It has to be AOSP or our tests wont work. Im not sure where people get AOSP builds to be honest, so hoping you know. Thanks a ton for the help :D
Also, the popup disappeared because I clicked it through "adb shell input tap". Im guessing it will reappear on reboot? 

Comment 7 by pschm...@google.com, Dec 16 2016

flashed it with the latest 7.1.1 aosp build.

bullhead:/ $ cat /system/build.prop |grep ro.build.fingerprint
ro.build.fingerprint=Android/aosp_bullhead/bullhead:7.1.1/NMF26V/3562348:userdebug/test-keys

bullhead:/ $ cat /vendor/build.prop |grep ro.vendor.build.fingerprint
ro.vendor.build.fingerprint=Android/aosp_bullhead/bullhead:7.1.1/NMF26V/3562348:userdebug/test-keys
Status: Fixed (was: Assigned)
Awesome. Thanks for the incredibly quick help. Bot is now running as expected.

Sign in to add a comment