You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer the questions about build version and network, will save
developers a lot of time !
What steps will reproduce the problem?
1. Installed Chrome to Phone on Samsung Galaxy 4s Android 4.4.4
2. Select the account to use (only my gmail account is displayed)
3. Tap to select gmail account.
4. Tap Next
5. Phone displays error message "Unfortunately, Chrome to Phone has stopped."
What is the expected output? What do you see instead?
I expect Chrome to Phone to register with my gmail account and start working.
Instead, registration stops at the error message.
What version of the android, in Settings -> About phone -> Build number (
ex. FRFxx ) ? If less than FRF50 - see the FAQ.
Android 4.4.4
Model SGH-M919
Build No. KYU84P.M919UVUFNK2
Kernel version 3.4.0-2437203
dpi@SWDD6020 #1
Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?
It happens both on WiFi and T-Mobile's mobile network.
Can you open "Gmail" application ? Do you see new messages without hitting
'refresh' ?
Gmail opens flawlessly, and displays a current list of emails to my Gmail
account.
Can you open "Talk" application ? Do you see incoming chats ?
I do not have a "Talk" application.
Please provide any additional information below.
I have unloaded and re-loaded both Chrome and Chrome-to-Phone. Chrome to Phone
worked until I brough my phone to Samsung to fix an error in which the S4 would
complete calls but neither I nor the other party can hear each other. Samsung
re-flashed my phone. Since then, I have not been able to register Chrome to
Phone.
Original issue reported on code.google.com by [email protected] on 22 Mar 2015 at 5:32
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 22 Mar 2015 at 5:32The text was updated successfully, but these errors were encountered: