Develop Bugs

Google+ Incompatible [Solved]

It seems that Google believes my rooted, stock Galaxy Nexus is incompatible with Google+. The only things I've done to the phone are to root it and install a custom recovery. I haven't changed the build.prop or the DPI settings. Any thoughts on how I can resolve this issue? I've also force stopped, and cleared data for: Google Play Services, Google Framework and Google Play Store, followed by a reboot.
http://i.imgur.com/ouRiZKv.png

It happens to me too in a nexus 4 and a nexus 10, both rooted

VivaErBetis said:
It happens to me too in a nexus 4 and a nexus 10, both rooted
Click to expand...
Click to collapse
Well, I tried temp unrooting, and clearing the market. Didn't help though. Not that I think it has any relation, but are you running a stock recovery?

Hrm, I think they have it broken on the Market:
REQUIRES ANDROID:
2.2 - 2.3.7

randalla0622 said:
Well, I tried temp unrooting, and clearing the market. Didn't help though. Not that I think it has any relation, but are you running a stock recovery?
Click to expand...
Click to collapse
No, I'm running TWRP in both devices.
But this may be related with something I realized few weeks ago:
http://forum.xda-developers.com/showthread.php?p=40611435
Maybe my devices had a wrong version to upgrade......
---------- Post added at 08:54 PM ---------- Previous post was at 08:43 PM ----------
Oh Well, as you said it seems that is broken for ics & jb...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

http://www.androidpolice.com/2013/0...oid-2-2-2-3-7-but-google-is-working-on-a-fix/

freezer2000 said:
http://www.androidpolice.com/2013/0...oid-2-2-2-3-7-but-google-is-working-on-a-fix/
Click to expand...
Click to collapse
Thank you. This kinda **** only happens to google

Thanks for the followups! I see that it's resolved in the store now.

[Q] S Pen Writing Recognition

Hello, I have rooted and have TWRP recovery, running DEATHSTALKER rom, I have noticed that the hand writing recognition software is not working, I have tried some options like changing the date to SEPT. 28 and it worked, but there is no update on the playstore to fix the problem I am having, has anyone else had this problem running a custom rom? Samsung N900T 32gb T-Mobile

Yea I had the problem for a few days and then couple days ago inwoke up and there was an ota from Samsung on the playstire that fixed my keyboard. Works like a dream now. Its there you just gotta find it. Ill look later and see if I could find it for ya
N3 anticipating Tweaked perfection
---------- Post added at 08:10 PM ---------- Previous post was at 07:14 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
N3 anticipating Tweaked perfection

I found it on the play store but their is no option for update. It has been almost a week now and i still have no writing recognition

I can get you the apk if you want to try to install that?
Sent from my SM-N900T using xda app-developers app

I got the update alsp
Sent from my SM-N900T

nismopower93 said:
I found it on the play store but their is no option for update. It has been almost a week now and i still have no writing recognition
Click to expand...
Click to collapse
What does it say?
Sent from my SM-N900T

For those of you having problems (and are on DarthStalker version 3), check out post #1019 on his thread. All PROPS go to the OP laroi07, of course, and sorry i don't know how to post links or if i'm even allowed to.
http://forum.xda-developers.com/showthread.php?p=46896199#post46896199

[APK] Google Now Launcher Lollipop version

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys..after flash of factory image, in your N4 you will find "old" home launcher.
If you want "official" Lollipop, Nexus 6-9 launcher, just download and install this:
DOWNLOAD
Enjoy

Or you can download it from Play Store

Latest version here: http://www.apkmirror.com/apk/google-inc/google-now-launcher/

Mashed_Potatoes said:
Or you can download it from Play Store
Click to expand...
Click to collapse
Most people don't receive update..Google Now Launcher is blocked at version 1.1.0.1167994 of 1 August 2014..
fr3quency said:
Latest version here: http://www.apkmirror.com/apk/google-inc/google-now-launcher/
Click to expand...
Click to collapse
Same versione that I posted

autoradio78 said:
Most people don't receive update..Google Now Launcher is blocked at version 1.1.0.1167994 of 1 August 2014..
Same versione that I posted
Click to expand...
Click to collapse
I have the August 1st version on my phone and it works properly and gives me the lollipop one, I think the only advantage of the new one is new wallpapers but the new wallpapers are also in the factory image, just tied to the default launcher instead. I might be wrong though.

autoradio78 said:
Most people don't receive update..Google Now Launcher is blocked at version 1.1.0.1167994 of 1 August 2014..
Same versione that I posted
Click to expand...
Click to collapse
Nah, apkmirror has version 1.1.1.1516623. Yours is 1.1.1.1499

fr3quency said:
Nah, apkmirror has version 1.1.1.1516623. Yours is 1.1.1.1499
Click to expand...
Click to collapse
You're right ..lI have seen under ...link changed at first post

Thanks for the updated apk.
In both the play store version and in this one, I get blurry icons (I mean they seem low res) and I don't know why. Am I the only one?

Samsung Galaxy S3 I747M - best and simplest rooting method?

Phone was locked to Virgin network and below is "about device" screenshot.
Please help, I've tried towelroot but no success. Thank you in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

grga said:
Phone was locked to Virgin network and below is "about device" screenshot.
Please help, I've tried towelroot but no success. Thank you in advance.
Click to expand...
Click to collapse
Probably the simplest way is to install a custom recovery with Odin and then flash the SuperSu.apk with that recovery.
TWRP for the i747M; use this file -- twrp-2.8.7.0-d2can.img.tar 8.5M
Stable SuperSu the recovery flashable download is near the bottom of the OP

Flash TWRP with Odin, Use TWRP to flash SuperSU ZIP (not APK like above).

If twrp fails to mount system and or won't wipe (bootloop) then you may want to use a different recovery.
Every post seems to recommend twrp but it didn't work right on two d2att devices. I'm not super genious but I been having root on every device I have since about 2011. Its not a user error.
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
I'm using philztouch. Ported by RoryB. It works excellent with both devices. Just my two cents.

I did it with Odin. It works OK now.

Question LE11.2.7.7 BA finally available

The full OTA is also available in Oxygen Updater
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Finally, i was waiting for this version!

Same here was looking for it... glad to see!

Just got it this morning.
And holy crap this website now has more ads on mobile than the Sunday newspaper.

Hmm, my device is now failing safetynet, didn't have any of this before with previous updates.
Anyone seeing the same?

plz delete

No issue with safetynet if this what you mean @emontes

Fre$h said:
No issue with safetynet if this what you mean @emontes
Click to expand...
Click to collapse
It is, yes. I have no idea why , though,it was fine on the previous version.

emontes said:
It is, yes. I have no idea why , though,it was fine on the previous version.
Click to expand...
Click to collapse
Did you try to simply disable any Magisk module then reboot just to the if the culprit isn't there ? Is Magisk Hide engaged ?
You can also try to fasboot boot the correct boot.img that is already patched too and see how the assertion react

Anyone notice any sound issues since the update when watching videos or listening to music? I have to crank the volume way up and there doesn't appear to be any bass.

Did you try to simply disable any Magisk module then reboot just to the if the culprit isn't there ? Is Magisk Hide engaged ?
You can also try to fasboot boot the correct boot.img that is already patched too and see how the assertion react
Click to expand...
Click to collapse
Didn't even think of that,been using edxposed for a while and didn't have any issues until now. Found some other people complaining and saying lsposed did the trick and that was it. Thanks!