jbdan
Extreme Android User
No luck JB
Are you granting it access like it does the first time you sign in to chrome to phone? Ya know, when it takes you to that webpage?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[Verizon] [ROM][4.0.4] AOKP ICS B40/M6/Mods (7/8)
- Thread starter jbdan
- Start date
-
- Tags
- galaxy nexus
Are you granting it access like it does the first time you sign in to chrome to phone? Ya know, when it takes you to that webpage?
jbdan
Extreme Android User
andoird213
Android Expert
Patriot, I just joined the ranks of the rooted and ROMmed
I flashed AOKP and went through the sign-up process in the Chrome-to-Phone app. As soon as it finished, I sent myself something and it showed right up.
There HAS to be a reason why your Nexus isn't receiving the links...
Was there any particular order that you signed in and connected?
From the phone or from the computer? On the computer I've tried disconnecting and then reconnecting and when I reconnect in opens up an AUTH tab which it authorizes automatically (since I'm already signed in to Google) and then the tab shuts down and it sees my devices. It sends it to my Prime, but my Prime doesn't receive it, and it won't even send it to my phone, it says it is unable to. On the devices themselves, I've tried signing out, signing back in, enabling/disabling sync in both Chrome and the Accounts section in Settings, and I've tried manually syncing (sync now). All with no luck.
Welcome to Rootdom!
Yes indeed! Always great to see some new faces! (or avatars...
)
No, I sent Chrome to Phone from the laptop, didn't get it, opened up the app on the Nexus and configured it. And BOOM! It showed up.
The only thing I can suggest is uninstalling Chrome to Phone, reboot, re-install it from Play, and reconfigure it. That should eliminate whatever's hanging it up
AndroiDad75
Android Enthusiast
Patriot,
I have had this happen from time to time. The way I have fixed it, has been to go into apps, on the gnex, and clear data and force stop the Chrome to Phone app. Then when I re-launch the app, I have to go in and re-sign in. You still won't see anything that you have been trying to send prior to doing this, but now if you send something it should/will work - at least it does for me.
This has happened to me a few different times, and each time I have been able to fix it by the above method. Hopefully that helps, and you haven't tried that already. The big thing, the first time I did it, was realizing that I wasn't going to get anything that was sent prior to doing the clear data/force stop. I figured it would be in the history, but it isn't. You have to resend it once you clear/force stop.
VoidedSaint
Resident Ninja
i cant believe they are still down...
jbdan
Extreme Android User
andoird213
Android Expert
That did it! Thanks!
jmar
Nexican
VoidedSaint
Resident Ninja
^^ dont even know how to begin reading that 
^^ dont even know how to begin reading that
Thanks for saying what I was thinking, Saint!
I'm a geek, I'll admit it: but that web page goes to a level of geekiness that I don't even come CLOSE to. No offense, Jmar, but I can't make ones or zeroes of anything on that page...
jbdan
Extreme Android User
^^ dont even know how to begin reading that
It's simple when you know what to look for.
Next question: can I flash this over b37 without a wipe? I assume I can...
EDIT: Is there a changelog anywhere online yet? My searches are fruitless...
EDIT: Is there a changelog anywhere online yet? My searches are fruitless...
andoird213
Android Expert
B38 rocks
andoird213
Android Expert
The only issue I've found so far is that lockscreen images pixelate
jmar
Nexican
I wouldn't considering the big change to swipeable nav bar Widgets. You can, if you want.
Change log won't hit until the builds are posted on AOKP's official page. Technically, b38 isn't official right now, though available for download on goo. I usually wait until roman drops into the AOKP thread on RootzWiki to say it is official. He tweets it as well I believe. And if you check out the AOKP thread on RootzWiki there is a link to an email list for when builds and milestones drop unofficially and officially.
jmar
Link to post described above about email list: http://rootzwiki.com/index.php?/topic/19302-AOKP-|-toro-|-May-24-|-build-37-|-4.0.4#entry719000
andoird213
Android Expert
I dirty flashed and like I said, the lockscreen images pixelating is the only issue I see. Though I don't think it's an issue with how I flashed since the image sizes were shrunken again (those of you on AOKP a while know that they've changed the sizes many times). I bet something like "made lockscreen images smaller" will be in the changelog
Okay jmar, save me again here... I haven't been a consummate ROMmer since my OG Droid days and Build 37 was my first ROM on Nexus.
What exactly is "dirty wiping"?
No toilet jokes from the peanut gallery, please
VoidedSaint
Resident Ninja
better boot animation finally lol
jmar
Nexican
Okay jmar, save me again here... I haven't been a consummate ROMmer since my OG Droid days and Build 37 was my first ROM on Nexus.
What exactly is "dirty wiping"?
No toilet jokes from the peanut gallery, please
It is when you wipe cache and dalvik cache as well as system data. System data is under mounts/storage and dalvik in advanced.
Then,
Flash ROM, GApps and anything else.
Good luck sir!
jmar