Related
Hi. I'm using CM12.1 with my quark (xt1254). Using a clean install method if I flash cm with a current gapps build (tried 1/29/16 & 1/30/16) the play store will not download apps over approx 25 MB. Play store downloads the app to 99%, restarts the download, then fails with error 963. Small apps are unaffected. Using the exact same method, but with an open gapps from 12/08/15
https://www.dropbox.com/s/e7a48os7ucj014p/open_gapps-arm-5.1-stock-20151208.zip?dl=0
, works perfectly fine. Just thought I'd see if anyone had any thoughts as to what's up. Ideas, contents, suggestions appreciated.
sd card
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
kikkie said:
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
Click to expand...
Click to collapse
I think the issue is related to the way CM12 chooses the default install location for you. The newer gapps builds may have triggered something, but I believe the root of it to be the default installation location. Please see this post for a possible permanent solution.
http://forum.xda-developers.com/showpost.php?p=65139180&postcount=6
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
elderlypunk said:
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
Click to expand...
Click to collapse
No joy after changing the default location? Which way did you use to change the location? Did it give you any messages? it shouldn't have, if it worked, it should just have returned a prompt.
Just to be on the safe side, I would load the gapps file that you mentioned was working in the past, and change the default location before trying any of the apps. If you already have it all loaded up, then yes, I'd also recommend you clear the cache and data from the playstore and playservices apps.
Don't know if you're using opengapps, but I took a look at their most recent builds and noticed that the file size changed slightly after 01/20/2016, so your reasoning has merit.
If you happen to be using TWRP, you could also try changing the location from recovery. Advanced -> Terminal Command -> Select and then enter the command. I really hope this helps.
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
elderlypunk said:
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
Click to expand...
Click to collapse
Ugh. I was able to recreate the behavior you're experiencing on a 2012 Nexus 7 - the only device I have access to with no SD card slot. I used the last two nightlies of CM12 and opengapps from two days ago, and also the one I mentioned from 1/20. Always had the behavior when downloading large apps, and as you say, apps not from the playstore. And yes, same behavior whether I used nano, pico, et. al.
The behavior disappears once I flash the latest nightly with the gapps from 1/20 AND change the default location. I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Gster09 said:
I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Click to expand...
Click to collapse
No worries! Since I found a working older gapps I'm inclined to let this go for now.
Which older version did you install? I'm running into this issue.
See link in op.
Hello,
I have same 963 error issue on my both cm 12.1 devices : Galaxy Nexus and Nexus 7 (2012).
I tried on my Galaxy to "pm set-install-location 1" but it don't solved the issue.
(delete the play store app cache and data don't work)
Can you provide me the link to this Gapps, it is not working anymore
ancelin said:
Hello,
Can you provide me the link to this Gapps, it is not working anymore
Click to expand...
Click to collapse
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue.
Click to expand...
Click to collapse
Did s/he mention when it will be fixed?
If you're looking for a version of Open GApps that doesn't have the double download fail with error 963. Then you should install Open GApps 2016.01.05. Don't install the 2015.12.08 version if you're using CyanogenMod! You'll end up breaking WebView on your rom if you do. You can find an Older Version option on the Open GApps Web Site and get the version I mention from there.
As others may have mentioned you can temporarily dismount your SD Card as a work around to this issue, but I preferred to downgrade rather than having to do that every time I used the Google Play Store.
As I understand the issue it's not a bug with Open GApps itself but a bug with the Google Play Store, apparently but I haven't confirmed any version of Google Play above 6.0.5 can have this issue.
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
Click to expand...
Click to collapse
This fixed the issue for me, and I was able to install the 2 problematic apps. Strangely, I had no trouble installing some other apps, namely made by my operator (MEO music and MEO drive), which leads me to think it might be related to locale.
However, now I can't search the play store, as it force closes when tapping the search box :/
Best thread ever.
Finally it works.
Thanks everyone
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.
Unable to login google account in device setup
i was using global beta ROM 9.1.24 and then flashed EU 9.2.15 but faced an annoying problem after boot, i completed terms and agreement at copy data page no matter what i do it wont take me to next screen weather i select copy from cloud or don't copy maximum it will do is it takes me to a blank screen with only back key and battery icon visible please help me out with it. i have done clean flash
You can always add Google account later by skipping at phone setup
As for your blank screen problem, I had almost similar problem but it was with stable ROM
What I did was select wipe cache/davlik/data/system
This erased installed os and then I flashed ROM & solved the problem, try it.. Internal storage will not be affected..
Don't forget to also flash the force encryption zip after the rom
I faced this issue too. So I installed previus version then login and dirty flashed 9.2.15 eu.
There's 9.2.15eu v2 link. I quess it's fixed version.
sorry for bad english
Martensite said:
I faced this issue too. So I installed previus version then login and dirty flashed 9.2.15 eu.
There's 9.2.15eu v2 link. I quess it's fixed version.
sorry for bad english
Click to expand...
Click to collapse
Can u share the link, cant find it on official eu page
vergilrahul said:
Unable to login google account in device setup
i was using global beta ROM 9.1.24 and then flashed EU 9.2.15 but faced an annoying problem after boot, i completed terms and agreement at copy data page no matter what i do it wont take me to next screen weather i select copy from cloud or don't copy maximum it will do is it takes me to a blank screen with only back key and battery icon visible please help me out with it. i have done clean flash
Click to expand...
Click to collapse
It's due to older version of android webview, just download latest android webview from apk mirror and then install it. Had the same issue even on latest version, issue fixed after installing latest webview.
stonedead said:
It's due to older version of android webview, just download latest android webview from apk mirror and then install it. Had the same issue even on latest version, issue fixed after installing latest webview.
Click to expand...
Click to collapse
thanks man worked for me
stonedead said:
It's due to older version of android webview, just download latest android webview from apk mirror and then install it. Had the same issue even on latest version, issue fixed after installing latest webview.
Click to expand...
Click to collapse
created an account just to say THANK YOU, my issue was whenever i attempted to add a google account it goes black screen, I did what you suggested and installed the latest webview from apkmirror and IT WORKED!!
I can add google accounts again
this was ongoing issue with miui eu roms. The same happend to me (unable to continue adding google account/black screen) in at least 2 versions I have tried. Thanks for the feedback everyone.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Magisk (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and Magisk
Information
This is native tablet port with normal keyboard, animations and other stuff.
My port based on:
framework and apps: T510XXU1ASCE and T515XXU1ASCK (new Tab A 10.1 SM-T510\515) Android 9.0 with 2019-03-01 security patch
libs and etc: A600NKSU1ZSB6 (SM-M105F) Android 9.0 with 2019-02-01 security patch
kernel: based on M105FDDU1ASB2 (SM-M105F) Android 9.0 3.18.91
Additional
1. Added OC for CPU (1690MHz - Kernel Adiutor, EX Kernel Manager) and GPU (default 1001, in OC 1146MHz - EX Kernel Manager)
2. Added themes from A600N
3. new wlan driver driver 4.0.10.206A_20181017 (from A600FNXXU3BSC5)
Links
LTE version:
1. 20190523: https://drive.google.com/file/d/1tK1F92bTWaaOBqUbkyVL8j3Sw50B0kre/view?usp=sharing
WiFi version:
1. 20190523: https://drive.google.com/file/d/1v2OM_IL8SCq5rLxOG1Vy21syd2KTq-Zd/view?usp=sharing
Magisk
Before run Magisk installer in TWRP - you need run small script - https://drive.google.com/file/d/1ZnnKHtDAl0ioHjQXiNO6wErZN8odsO0P/view?usp=sharing
It's simply unmount /cache partition and then mount it as /vendor. After run the script, you can install Magisk. If Magisk Manager does not appear in the list of apps - extract magisk.apk from Magisk installer and manually install it.
Sources
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Thanks
Thanks to Samsung
good morning Valera! I've been waiting for this a lot, since Samsung Pie is very good rom, I've already downloaded and flashed it. I just had time to try the basics and everything seems to work and the Ui is nice. Then I will make a good revision. Thank you very much for your great works!
@Valera1978 First of all, thanks for the great Pie port. Tab feels brand new, smooth. One thing I have found is the Themes/Wallpapers don't work. It will download wallpapers but when you go to apply, all you see is a black square, and nothing is applied. If it is an animated one for lock screen, it fc's the systemui when you try. Not a big deal as I can always apply wallpapers from my own collection. This is only issue so far and I have a feeling there won't be many more if any. Thanks for your works!!!
great job from shortcomings is at present a problem with the keyboard
I like this rom, it seems clean and pretty and I would like to be able to install magisk but I do not understand how to do it, could you explain it ?. Thank you
Bootloop
I tried this on my T580 coming from RR latest Pie ROM. Backed up ROM, factory reset wipe and installed just the wifi port. Wiped dalvic and rebooted. Bootloops at first Samsung screen. What did I do wrong?
edit: Never mind. Used Advanced Wipe for everything but Internal and SD. Booting now.
Great rom. Thanks for your effort.
Looks good thank you.
Are there other people who get a failed when they try to sign in the Samsung account?
In the pie_t510_t580_port there are the follwing settings that don't work or crashes, or don't belong in the wifi version and if it's possible should be removed.
T-roaming
Service provider
Mobile networks
Also in the About tablet there is some LTE version information
There is also the mobile hotspot settign in the connections
Cellphone signal icon in the at the top next to the wifi signal
These are for when you have the LTE version
Great work man!!! Thanks for your work!!
Anyone managed to download other languages keyboards in samsung keyboard because swiftkey lags
chris333333 said:
Anyone managed to download other languages keyboards in samsung keyboard because swiftkey lags
Click to expand...
Click to collapse
When I try to download other languages I get the message download failed. Probably a bug.
I hope you can port this rom for P585Y. Thank you
Tung Lam said:
I hope you can port this rom for P585Y. Thank you
Click to expand...
Click to collapse
I imagine that if you were to give the dev a P585, he might have a reason to port and a device to test it on. Otherwise, he has neither. I've seen this request many times, where someone with a different device, asks a dev to support theirs, and it never succeeds.
My personal hotspot isn't working after my first reboot... though I've uninstalled every 3rd party app.
Edit: It comes after installing Magisk.
EDIT 2: I've tried to reboot without installing any apps twice, and the problem appears, I only need hotspot for hosting an offline game with friends, like Bombsquad.
Is it debloated?
jurgenmmehja said:
Is it debloated?
Click to expand...
Click to collapse
Sort of...
This ROM needs more focus though, it's faster than the stock Oreo, but has weird bugs...
To solve that keyboard bug switch to the phone interface through build.prop editor,
Edit the line: ro.build.characteristics=tablet to phone instead of tablet.
Then add the languages you want then revert back the changes after finishing.
About that hotspot bug, I don't know, but can't we just use the stock kernel and wifi instead? What's the use of the new one?
About the Secure Folder, there's a way to set it up by modifying the kernel, and we never had it on our own device, we only got it on S7.
But there's a small question... do we have a chance to get a Samsung 64-bit ROM on our device? Because the Play Store will shut down on 32-bit devices in August 2021, though this device is 64-bit.
Is it really much faster than stock 8.1? None of the roms I've tried so far have been, the ui lags and battery takes a hit I assume as it's running harder to keep up
Bingley said:
Is it really much faster than stock 8.1? None of the roms I've tried so far have been, the ui lags and battery takes a hit I assume as it's running harder to keep up
Click to expand...
Click to collapse
That's because it's overclocked, and it generally feels way smoother like the stock Nougat ROM, there are some annoying bugs though, some camera apps can't access the camera, and the Hotspot doesn't work after installing some apps and rebooting, looks like it's not Magisk to blame, that doesn't happen in the stock though.
So I'm waiting until the OP replies or gives us an update hopefully.
I've tried the hotspot in the A600N port and it works properly! Why not here in this port? I think due to the presence of numerous Korean carrier options and maybe the Wi-Fi Sharing, when it's enabled, the hotspot doesn't work, even if disabled and rebooted. So you should remove these options, I guess?
I use SwiftKey beta as a side keyboard, testing the puppets, they are working in the stock ROM, but in both Pie ports, though I've allowed camera permission, the app can't load puppets, and that is not just present in SwiftKey, it is present also in some apps, it may be a missing Pie support, hopefully.
And thankfully, there are no camera modes, just front and back camera,
When I switch modes in this port, it force closes immediately,
and the Photo editor works properly in the A600N port, but not in this port, when I switch the filter it gives me a black screen instead
The only thing that annoys me is that the tablet interface of the A600N is not as great as this port, landscape mode is better here, because this port has tablet framework.
So, I wish this port gets more attention than it deserves, thank you Valera1978 for your great contributions! Hope you focus on this port, well more than you do with LineageOS!
Work on P580 ??
few bugs for me after crDroidAndroid-10.0-20200311-vince-v6.4
hi all,,
so after crDroidAndroid-10.0-20200311-vince-v6.4 which is still working great, all updates even last one Update - 15/07/2020 few bugs started to happen.
worst of all is that after flashing with any new crDroidAndroid-10.0 updates NanoDroid-microG was uninstalled after flash so i reinstall last version and this were it all started to crash. i try to open whatsapp telegram swiftkey uber and they all crash a soon as they open. of course they were working well before i reinstall NanoDroid-microG. i checked all permissions when open NanoDroid-microG.
i noticed that if stop the wifi then none of the apps mentioned crash but the don't update because no wifi...
is this build implement spoofing signature or is it something else?
also there was no gps signal but i think the last version 15/07/2020 fixed that problem.
also since the crDroidAndroid-10.0-20200311-vince-v6.4 i can not export manually my contact into vcf file, nothing happens.
hope you can help or fix this i would hate to change rom it is really the best one!
cheers