Develop Bugs

CM7 Market problems since last week

Hey people,
I'm currently located in China and I've got serious problems with the Market lately.
I'm using and been using CM7 on my Moto Defy for months (almost since CM7-Jordan beginning) and I've never had such Market problems before.
So I'm wondering if
1) other users from China can tell me if things are the same (or fine) for them?;
2) anyone have hint/suggestion on how to fix this after reading what I did/observed here?:
First, I'll say again that I've never had problems with Market before; none getting it installed (through gapps zip) on CM7 when updating/reflashing ROM or Nand backups/ none with downloading or upgrading apps with the Market app.
But all in a sudden last week, I noticed that the Market was not reacting quickly. I was testing 111004-1128 nightly (which has a newer Superuser file included) then after SU updated itself automatically [coincidence???], all things broke loose, Market would not connect and give me errors. SU would also alway stay in the "Not Installed" List of my Market apps (even after reboots and logins).
I've then tried to install the Superuser Market update fixer app (big mistake I think now) but that just made things worst. In an effort to get the Market going again, I did clean it's cache and eventually it's data which basically resetted all my listed apps in the Market.
Following all that, I did numerous fresh installs [maybe 10 at this point]: RSDL Froyo flashing and CM7 and gapps installs [with and without restoring old working CWM backups] and with countless install combinations of older CM7 builds and gapps versions.
On August's gapps, Market always gives me the "No connection Retry" even if I can get connected to Google services since my wifi indicator turns blue or green (depending on theme/CM7 build used) and Talk and Gmail logs in fine.
On June's gapps,login seems fine: I can browse apps but as soon as I try downloading something, I get stuck at Downloading 0%... and it seems to put the servicee in some sort of bootloop since and other apps icons do not display until I get "Download failed to install - Try again" and click OK. Market will also FC as soon as I select anything from the "Just in" sections.
I've tried clearing Market's cache many times, started Talk, signed out and back in, let my wifi on all night to leave Market to update. I've even created a new gmail account and tried it on yet another fresh install with June gapps; nothing works and this drive me nutts!!
I can go on my desktop, use a VPN service to log in to my Market account and install something from there; it will be pushed on my phone alsmost right away. But again I can't install anything from the phone no matter what.
That would be fine with me, but that means that for any special apps that otherwise would require me to use Market Enabler, I will not be able to do it from the desktop either.
It's not a question of having DroidWall or anything else I've installed blocking something out; like I wrote; I've tried many clean installs without restoring or installing anything...: same.
So, has The Great Firewall" finally caught up to Android Market and stopping use of any Vending.apk from withtin China? Are they recent changes from Google? Or am I having other Market setup/install problems here? What's your take on this?
Thanks for reading and thanks for any help in advance.
Cheers.
And PLEASE do not "full quote" this long post (sorry for that btw) .

Market has been blocked by GFW. I can't access it either unless using VPN.

[] AL [] said:
So, has The Great Firewall" finally caught up to Android Market and stopping use of any Vending.apk from withtin China? .
Click to expand...
Click to collapse
This sounds not so far fetched..
I live in the US, and I see the same type of behavior at my college.
I can get to the app, but when downloading it sits there for a century.
the idea of censorship isn't something I would blame, nor shrug.
Her are a few things I should try...
Use a spare gmail account to test with, and see if you can reproduce the same results...
Try and use that same vpn, configured through your phone this time, and disable any apn/data settings other than wifi... Now try.
Edit:
P.s. What ROM are you using? The cm team has a stable out now.. Guide that a shot...

TimelesslyPrecise said:
…
Her are a few things I should try...
Click to expand...
Click to collapse
My OP was a long one, but I think that i did mention somewhere that I've tried a new gmail account with same result.
My vpn use encryption and will not work on defy ;(
Strangely, from all my recent tries at getting gapps to work properly, it seems that I can only use 2G data to do the first account setup. And that seems to 'work' only with June gapps package.
Recent update (on RC1.5):
I've also managed to get my installed apps listed again by playing around with 2G data and installing and uninstalling a standalone 3.1.3 Vending apk as update and undo it.
I was able to download 2 or 3 apps (out of 50 trials) also by fiddling w data enable/disable.
But again, never before, in 4-5 months using CM7, I had to turn on data past the initial Google setup and I've never had any download issues either....
So i don't think that it's related to TGFW and will keep digging...
On 7.1 now but no change..as
I did flash june gapps w 7.1 but never got any setup to do since no factory reset. Will try a clean install tomorrow or the day after...
Thanks for your reply.

OK I finally got it to work after all.
I just tried to fix the fix the problems caused by the new Superuser update after trying a recent nightly in just the worst possible way over and over.
So what you have to remember is:
1- to NOT signin to your Google account using data and do it over wifi. So select "Skip" on the screen showing "Create an account", "Sign in" or "Skip" and go ahead with other settings: your baseband, wifi and especially turning off "Data enabled".
2- always use the latest gapps version, not the June one like I tried many times
3- Install gapps along with a fresh CM7 zip install; not a nand restoration.
4- after reboot (if needed by Defy Baseband Switcher) just press the Market icon and set up your account then
So wipe data, cache and Dalvik and install CM7 zip (RC1.5 is a good one to start with) and and latest gapps zip and follow the above.
Sorry for this useless thread and for me trying to get this working like a chicken without a head
So @ TimelesslyPrecise: if your downloads do not start, it might as well be because you did setup your account over data the first time.
So just start from scratch again:
- backup your apps [with TB, the newest (and free) Astro file manager or other];
- do a fresh CM7 install (no need to reflash Froyo) but do as above;
- restore your apps;
- then just click on the Market icon and sign in.
Don't worry if at first your apps are not listed under "My apps"; they will eventually come back with usage.
@xcjiang: yeah I knew that, but that doesn't mean that the Market app on the phone doesn't work.
Sorry again about that.
Cheers.

Didn't worked for me...
Instead I found cause and solution elsewhere http://forum.xda-developers.com/showthread.php?t=1295222
To cut the story short, problem is in way that Market don't get DNS right.
Solution is to install app that will change DNS for every wifi connection DNS to OpenDNS (my choice) or GoogleDNS. I'm using DNS Changer.
Now enjoy superfast Market

M8 Marshmellow updated - some issues.

I flashed the Wolla v2.5 MRA58K.H6 with TWRP and had some questions/issues. The camera kept on force closing, even though on other apps it worked just fine. I occasionally have a "android system has stopped working" warning as well. Also, I was expecting the full wipe to wipe all the internal storage as well, but I don't believe it did?
Wanting to install the newest ROM but wondering if there is a way to easily back up all apps and such - it took a long time to get it up and running at this level and don't want to go through it again. Thoughts?

Try using Titanium Backup to back up your apps and data. Personally, I use a combination of SMS Super Backup for my SMS/Call logs and Titanium for my apps.
I'm using Wolla v3.5 GPE right now and everything is great except for some strange reboot/bootloop every time I open up Snapchat. Uninstalling the app seemed to have solved the issue, but I still want to be able to use it... It's probably to do with the new camera API.

I'll give that a try. What's the difference between 2.5 & 3.5?

Updated to 3.5 and wiped it all.
Everything is working well except the system will not let me install chrome, why I do not know. I've tried downloading from the app store, both normal and beta, and every time it force closes. I've tried having it install from on my computer through google play and it force closes. I've downloaded the apk and allowed install from unfamiliar sources and it will get to the install page, and say app not installed. What gives?
Also, it seems all of my internal folders have been wiped clean - this means when I open the M8's internal storage on my computer, there are no folders; no download, no dcim, nothing. Any advice on what's happening here?

Solved both issues using [this solution](http://forum.xda-developers.com/showthread.php?t=2684384). Internal memory was set to read only.

Snapchat gives "login temporarily failed" error with CM ROM

Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!

saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.

NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!

I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.

This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk

Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app

[HELP THREAD] cm-14.1 on LG-G3 (Model: D8555)

I decided to update my phone from CM13 to CM14.1 the other day without having read anything about CM14 and not realising how new it was (yes I know, stupid thing to do!).
So after the update I've had nothing but problems with google services not working properly, so I uninstalled google services from the apps menu within the phone, downloaded the Android 7.1, ARM, Stock version of GAPPS from opengapps.org and booted my phone into TWRP and flashed the newest version of gapps.
This fixed the issue with google services not responding, however now none of my apps work.
Anytime I try to load an app such as facebook, email, browser. My phone will freeze for several minutes and then the app will just tell me its stopped responding.
Does anybody have any advice on what to do? (I dont care if the result is that I have to wipe the phone and lose everything on it, just want my phone to work again!)
Edit: an additional piece of info, any time I try to do something that requires root access (for example moving an app to my SD card) my phone will tell me that I don't have root access, even though I must because I'm using cyanogenmod...

Rhaom said:
I decided to update my phone from CM13 to CM14.1 the other day without having read anything about CM14 and not realising how new it was (yes I know, stupid thing to do!).
So after the update I've had nothing but problems with google services not working properly, so I uninstalled google services from the apps menu within the phone, downloaded the Android 7.1, ARM, Stock version of GAPPS from opengapps.org and booted my phone into TWRP and flashed the newest version of gapps.
This fixed the issue with google services not responding, however now none of my apps work.
Anytime I try to load an app such as facebook, email, browser. My phone will freeze for several minutes and then the app will just tell me its stopped responding.
Does anybody have any advice on what to do? (I dont care if the result is that I have to wipe the phone and lose everything on it, just want my phone to work again!)
Edit: an additional piece of info, any time I try to do something that requires root access (for example moving an app to my SD card) my phone will tell me that I don't have root access, even though I must because I'm using cyanogenmod...
Click to expand...
Click to collapse
Try doing a clean flash of the rom along with the respective gapps package. You have to flash the rom and gapps together. And for the root issue, you have to first turn ON root from the developer options in settings.

Sreerag ag said:
Try doing a clean flash of the rom along with the respective gapps package. You have to flash the rom and gapps together. And for the root issue, you have to first turn ON root from the developer options in settings.
Click to expand...
Click to collapse
Scrap this, solved the additional problem I was having.
Thank you for your assistance, all is working well now

Hi guys, is there a way to change the carrier name? The correct name for my carrier is "telecom Italia spa", not "... Italiz spa". Thanks in advance.

Problems after first update of LineageOs 17.1 install

First update since installing Lineageos on Lenovo P2.
The navigation bar along the bottom disappeared. Couldn't be swiped up - had been fixed previously.
Then found other things as well. Fingerprint sensor not working. Pixel launcher failing. Had been using Nova launcher and foolishly removed it thinking I'd reinstall to see if it restored the nav bar. But now stuck with a failing launcher and can't start anything - including Play to reinstall Nova. Just says 'Pixel Launcher keeps stopping, App info, Close App.' Cleared cache from App info as that was all I could do but no difference.
I haven't read it anywhere but are updates cumulative? Ie, can I skip one if I miss it and get all updates rolled up into the next one. I hope so because that's what I did. Jumped from something like 9th August to 30th.
Any ideas?

Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.

alirazaagha said:
Current update always include codes from previous builds so you can skip nightlies in between. There are few solutions for your problem. I'm telling you two:
1. Install a third party launcher apk through system settings
2. Reboot into TWRP, wipe system only and install latest update package with nano gApps and it should work.
Click to expand...
Click to collapse
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.

bind00 said:
Thanks so much for your help. In fact, while trying your first suggestion I somehow got into Google Play through APK install settings from where I was able to reinstall Nova Launcher. So now I have a partly useable phone again but still with the problems that followed the update in my OP (navigation bar gone, fingerprint sensor stopped working plus the failing launcher - those are just the things I found without looking).
It's disappointing that the update failed though, not least as staying updated was a major reason for moving to Lineage. Any ideas why this might be?
Maybe I should try the second suggestion and reinstall the update by sideloading as described here. So do I use the same file that I use to install LineageOS in the first place from here https://download.lineageos.org/kuntao? It's not stated in the document. And will this wipe the phone clean again?
Finally would I have to re-sideload a GApps package at the same time and should it be Nano GApps as suggested? Originally I installed Open GApps as suggested in the upgrade instructions.
Click to expand...
Click to collapse
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.

alirazaagha said:
The Pixel launcher in Android 10 force closes if it is not chosen as "Recents provider". Therefore, navigation bar also stops working. Hence, we need Quickswitch app to choose Pixel or any other launcher such as Lawnchair for giving them the mentioned right and that works without any hiccups.
You should install the latest update after wiping system only. You don't need to wipe everything, just wipe system partition.
Nano GApps are taken from Open Gapps website. I've suggested nano GApps because it doesnt include Pixel Launcher hence, stock ROM launcher will flawlessly work. However, if you want to use Pixel Launcher then install Magisk from recovery and Quickswitch module within Magisk. Then open Quickswitch app from launcher and click Pixel Launcher. Quickswitch app will process for a few moments and will restart your phone. Now, choose Pixel launcher as default from settings if it is not used as default and Done.
Click to expand...
Click to collapse
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.

bind00 said:
Many thanks again for your detailed help. Much appreciated.
Went for standard Open GApps just because that's what I had before and had hoped to get it all back as it was. (I've no particular preference for Pixel only that was all that was available to me after updating through updater. ) I've got the update loaded now, sideloaded with adb and TWRP. Unfortunately I seem to have accidentally factory reset from TWRP (thought I was just swiping to unlock and only noticed too late. Doh.)
TBH, this has been a whole lot of hassle for an update. After hours to get this far now have to set phone up from scratch yet again. And crucially, I still don't know why updater failed. Going to be very nervous about running update in future and staying updated was the main point of moving to Lineage in the first place.
But thanks for help again.
Click to expand...
Click to collapse
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.

alirazaagha said:
No problem bro. Next time, when you update, follow these things:
1. Keep ROM, Magisk and GApps in a single folder.
2. When updating ROM, just install the ROM and restart.
Click to expand...
Click to collapse
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers

bind00 said:
Thanks again. That's good information. So you recommend not using the Updater but adb sideloading instead?
OK, and I just read this at stackexchange "You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so)." So if GApps is in the same folder it finds it automatically I guess.
I'd better clue myself up on Magisk now and a decent backup system.
cheers
Click to expand...
Click to collapse
Built in update works as required but if it messes with system partition then you better download update and install it through recovery.
GApps can be restored after update but the point is that you don't need it. System update only replaces the older system files with new ones without touching gApps files. Whereas, Magisk is automatically installed after update if it's in the same folder.