Hey all,
As I don't develop CyanogenMod or work for their team, I didn't think it'd be right to make a post in the Development sub-forum. Anyway, I came across a post over on Android Police stating that CM 13 Nightlies are now availble for 'manta'. I've downloaded the latest Nightlie and flashed it on my Nexus 10 along with the lastest Gapps, and everything works great. You can find the Nightlies here. All credit goes to the CyanogenMod team for keeping our Nexus 10 alive!
In my case the gapps are too big (even micro and nano) while pico gets successfully flashed but then Google Play Services crash all the time.
Did you flash the very first nightly from Jan 9?
I have the same issues: nano gapps too large for system, can't install this way... any solutions?
Edit: pico gapps work, no issues so far
I can't even install the pico gapps. Which package did you use OP?
Edit: Tried again with a full wipe and it worked using the pico-apps. Have had no crashes of any Google services so far. I used the latest CM nightly to flash.
rxzlmn said:
I can't even install the pico gapps. Which package did you use OP?
Edit: Tried again with a full wipe and it worked using the pico-apps. Have had no crashes of any Google services so far. I used the latest CM nightly to flash.
Click to expand...
Click to collapse
Did it fail with the nightly from Jan 9 but then succeeded witht he nightly from today (Jan 10)?
Dimitris CH said:
Did it fail with the nightly from Jan 9 but then succeeded witht he nightly from today (Jan 10)?
Click to expand...
Click to collapse
I used the newer one both times. Only difference was full wipe.
I'm having zero luck on getting Google Play Services installed. Tried the nano, now the Pico. Same as above users, the install will go just fine but will give me crashes every second on screen.
I read here and there that this crash on CM13 (other devices) can also be caused by a) Privacy Guard settings for Google Play services, or b) allowing Google Play Services to access "Phone" and "Contacts" or something to that effect.
Still playing around trying to get this to install.......
Edit: Did a full wipe of everything, including System/Data, and it all works now. I'm all setup! I'm getting an error on Google "Now on Tap", saying "The app has stopped" everytime I try to use it. I remember seeing the fix somewhere about something in Accessibility settings. But I'm having no luck remembering what it was or finding the fix again.
DTB
Google play services were not working for me at first either. I decided to try and sideload the latest Google Play Services apk to see if would fix the problem. Thankfully, it did fix it. You can find the apk file here.
Install Opengapps nano or pico http://opengapps.org/ and full wipe before install.
http://review.cyanogenmod.org/#/c/127116/
Anyone tried enabling f2fs?
Good news, finally got "Now on Tap" working.
I went to settings. I searched for "Assist", and selected "Assist and Voice Input".
(I honestly can't find in the settings where it is, I can only find it by searching within settings.)
The "Assist App" was set to "Google App". I selected "None", then went back and set it to "Google App" again...and all was good!
So, looks like I am finally up and running. Another note; the Marshmallow apps restore didn't seem to restore for me. I even used my phone to setup my account, all was linked fine. It got my identity and set it, but did not restore any apps. Not a huge deal.
DTB
viruszzz said:
Install Opengapps nano or pico http://opengapps.org/ and full wipe before install.
Click to expand...
Click to collapse
I guess you did not read the part where we said that this is exactly what we did.
1GB RAM
I succesfully installed CM13 with Opengapps pico and its running very smooth so far. But in settings it's showing me that I only have 1GB of RAM instead of 2GB. Did anyone else notice this?
Edit: 1,1GB to be exact. Very strange.
Edit 2: I read in another thread that about 900MB is reserved for the GPU so that's probably why it is showing just 1,1GB for the system.
Hei, ref doing a full wipe, is that before doing the pico gapps install, and exactly what is meant by full wipe? Thanks
Cintra2 said:
Hei, ref doing a full wipe, is that before doing the pico gapps install, and exactly what is meant by full wipe? Thanks
Click to expand...
Click to collapse
Yes before installing Pico. I did a wipe after too, just to be sure. A full wipe means cache and system/data. If you have TWRP a normal wipe includes all of this.
MisterT200 said:
Yes before installing Pico. I did a wipe after too, just to be sure. A full wipe means cache and system/data. If you have TWRP a normal wipe includes all of this.
Click to expand...
Click to collapse
Many thanks for your quick reply, now I'll give it another go
Mvh
PS That did the job All working very well now!
Does CM13 support loop device?
I need to run linux chroot (via linux deploy); that requires that the ROM supports loop device. Request to those who have successfully install CM13 on N10: Could you install the free app "loop device checker" and check to see if loop device is supported?
THANKS!
ps. This app is free and useful but it has annoying loud music; mute the speaker first
After installing CM13, my Nexus10's rotation doesn't work.
When I used stock lollipop, rotation worked perfectly.
Even if I update to the newest version, it's the same here. (cm-13.0-20160129-NIGHTLY-manta)
Does anyone have the same problem?
Cintra2 said:
Many thanks for your quick reply, now I'll give it another go
Mvh
PS That did the job All working very well now!
Click to expand...
Click to collapse
Hey, down the page, you should be able to fit bigger packages than pico on there.
http://forum.xda-developers.com/nexus-10/development/rom-aicp-11-manta-t3280678/page18#post65047967
Youtube 1440p videos
For some reasons with the 02/09/2016 release I'm able to run YouTube video at 1440p, but after updating to newer releases it isn't the case anymore, instead I have the same problem as with Google's official releases the videos run for 1s then stops while the audio still runs normally.
Related
Did I break my Tablet...?
I am a big PACman fan and have been using the rom on every one of my devices. I am also not new to rooting and flashing procedures and have done them on different devices many times including updating hundreds of times. PACman was quiet for a while but has started up again since August, so I was really looking forward to that until I had following problem:
1. Installed the newest rom with a factory reset beforehand.
2. Setup the device as usual.
3. Opened gmail --> Stuck on "Getting your messages"
4. Tried calendar, contacts and google music without success, as they display neither my music, contacts nor my calendars.
5. Drive and Maps are working though...
I have now done the following:
- Reverted all the way back to stock 4.1, rooted and upgraded to 4.4.2 stock.
- Flashed boot.img from PAC rom and installed it with gapps. Everything went perfectly.
- Added my google account during the setup process, opened gmail --> stuck on "getting your messages"
- Added a second google account, which is also not syncing.
Before this I already tried using different gapps (PA, CM, Banks), doing a playstore and play services reset. I am really not new to this and this is the 5th device I own that I rooted and installed custom roms on. My phone has PAC and is working flawlessly. I'm really lost here and would appreciate any ideas or help.
Rom versions I tried: nightly from 12th, 18th and 323rd with clearing cache and dalvik after install.
Gapps: Banks, CM and PA gapps 11th, 18th
When installing AOSB project, everything works flawlessly!
Something I am missing here? Please help!! This is getting so frustrating...
PS: Here are three screenshots of how it looks like (weird is that there are no timestamps in the sync tab)
http://imgur.com/sAEqmCE,UxNjuNa,zJ83DiT
moesus said:
Gapps: Banks, CM and PA gapps 11th, 18th
When installing AOSB project, everything works flawlessly!
Click to expand...
Click to collapse
the problem is in P.A.C ROM builds or in Gapps.
Rootk1t said:
the problem is in P.A.C ROM builds or in Gapps.
Click to expand...
Click to collapse
PAC rom can't be the problem, as all other users report no errors. I have tried different Gapps (always checked MD5 sums...) and this issue doesn't resolve. I am looking for any new ideas on the issue.
Personally I cannot explain the issue myself
So if anyone has an idea, please help!
Search for another boot.IMG, there have been issues with the cm boot and wifi modules, maybe the same with the PAC boot.IMG low/ connectivity would explain the lack of sync time stamps
Sent from my omni_pollux using XDA Free mobile app
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
Hello,
after flashing the new CM13 snapshot cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-i9300 I keep receiving the following error over and over again:
"[CRASH] com.google.android.gms threw java.lang.securityException
java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.
at android.os.Parcel.readException(Parcel.java:1620)
at android.os.Parcel.readException(Parcel.java:1573)
at android.location.ILocationManager$Stub$Proxy.addGpsStatusListener(ILocationManager.java:741)
at android.location.LocationManager.addGpsStatusListener(LocationManager.java:1537)
at aepg.acom.google.android.gms:1045)
at aelu.bcom.google.android.gms:7362)
at aelu.handleMessagecom.google.android.gms:262)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.os.HandlerThread.run(HandlerThread.java:61)"
Most of the apps doesn't work either. Most of the Gapps don't work, too, reffering to this error.
I granted the permission for Location but this does't help either.
I don't know what to do. Help would be much appriciated!
Thanks.
Mike
Same problem here....
I tried a clean flash and also tried to install gapps directly after installing cm13. But no success. I keep getting this error message...
I have the same problem with S4.
flash newest/oldest gapps ?
exe98123q said:
flash newest/oldest gapps ?
Click to expand...
Click to collapse
directly downloaded from open gapps:
open_gapps-arm-6.0-nano-20160821
try old or dont use, you can download apk from mirrors (google is yours uncle )
the newest have some bug or high demand on resurences imo
edit.
try pico only, you no need nothing else
exe98123q said:
try old or dont use, you can download apk from mirrors (google is yours uncle )
the newest have some bug or high demand on resurences imo
edit.
try pico only, you no need nothing else
Click to expand...
Click to collapse
Tried pico - same problem.
Tried whiping cash, fresh install CM13, fresh install GApps - same problem.
I did however find apk mirrors, but installing them didn't work ("Parsingfehler")...? How do I install the APK other then uploading it to the phone? Did I choose the wrong apk? Which one do I use for my S3 i9300? I tried this one:
http://www.apkmirror.com/apk/google...es-9-4-52-438-127739847-android-apk-download/
Does this problem maybe have anything to do with this patch?!
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
Sorry, but I'm not an expert so I'd need support what to do with it.
Please help. I'm starting to get sick of this problem and thinking about switching back to CM11 if this is even possible (tried to do so once after CM13 - phone went to bootloop) ...
Thanks.
that apk you can install normal, only gaps
exe98123q said:
that apk you can install normal, only gaps
Click to expand...
Click to collapse
???
i mean cant, gapps include files .jar, not only gsm core
Does anyone have a solution for the problem? Still not working. As soon as I start any gapp the message appears again.
Please help.
Thanks
Meanwhyle I managed to solve the problem. This gapps seem to work fine in combination with the CM13 snapshot:
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
1) whype system partition & cash
2) flash room (I used cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-i9300.zip (296.87 MB)
3) install gapps (see above)
4) reboot
At first it seemed to cause further FC, but somehow they disappeared (maybe after updating the apps) and now everything works fine (except GPS location in Google Maps, but this is my least problem).
I also foudn another provider of gapps, but didn't test it.
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Apps
I had the same problem I gave up in the end and I downloaded aptoide has the same apps that you get from the play store
http://forum.xda-developers.com/showthread.php?t=3276606
Try this.
Sent from my GT-I9300 using XDA-Developers mobile app
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
Updated on July 3, 2018:
(reason in post #636)
MicroG in post #396, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
Open GApps in post #416, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible. It also performs a one time nice Google setup of the unit, beginning with language, account, and so on.
Note to all using this firmware for the first time: since it is differently partitioned from what you had before, you must also perform a wipe all in recovery, ideally just before the first startup (to avoid wasting time), or at any time now.
WARNING: MicroG Core and LP don't work well: contacts are not seen from apps like Hangouts, Google/Voice Search, while True Contacts needs local loading of profile & contacts - from vcards on the internal SD. Therefore I strongly recommend the Open GApps version!
Note also that with the MicroG version, the gms core app must be configured, and Hangouts' service called NetworkConnectionCheckingService must be disabled, for Hangouts to work:
Code:
pm disable com.google.android.talk/com.google.android.apps.hangouts.service.NetworkConnectionCheckingService
TomTom GO storage support is explained in post #45.
TT GO spoofing is in post #392.
Poweramp's early start&restart is also supported by default.
Phone calls via a BT connected phone could be dialed by (always) selecting the MTC Service(aka Headunit), as the preferred dialer.
MTC Sound direct sound control is readily supported, if the associated hardware mod is also done.
Automatic screen brightness control based on location&time is also implemented by default.
Blank logo kernels are in post #600 (get them while they last).
Developer Mode in post #332.
Firmware is also rooted and xposed.
To those who make outlandish claims about this firmware: they are either trolls or firmware is not for them. However firmware supports all rk3188 MTCB or MTCC units. Make your own judgement, and don't get scared away.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
===
Here's another one: in principle, unless an unlikely bug is reported, I don't reply in this thread to users who are not listed as saying thank you to this post.
===
Mod Edit :- Content Removed
Thanks @dsa8310 .. your rooms are great .. I installed microg rom yesterday . Works great . Will try the new one soon. The only question I have is the performance of both roms similar coz I have 1GB Ram
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396.
Open GApps in post #416.
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Hi @dsa8310, is it possible to find what version of your firmware that I have installed in my radio. I think I updated yesterday, but not sure if it the recent one that you posted yesterday.
Maybe a tall tell signature or something to look for.
Again, thanks for your work on the firmware. And I hope this section works out for you.
Wayne
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
As usualI I ll be putting the ROMs on the fileserver for everyone.
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
dsa8310 said:
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
Click to expand...
Click to collapse
I have the 6/28 one.. MicroG I guess. Getting Gapps..
Thanks bud.
Like to donate as well..
EagleSoldier said:
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
Click to expand...
Click to collapse
I now use the (pico) Open GApps enabled version. I like it because I don't have to configure things and it is 100% Google compatible. I dislike it because of Google ads' undisturbed presence, unlike the MicroG version that avoids them, partially, at least for my set of apps.
There might be observable differences in their footprint size (necessary RAM) and load of system (background tasks). I can't say for sure, since I have a 2GB RAM (upgraded) unit. Furthermore, I run the same set of apps most of time: Poweramp and TomTom GO which have the same heavy requirements (TT mainly).
Perhaps 1GB units should use MicroG while 2GB ones could afford the Open GApps version.
A technical comparison between versions could be done, in a terminal (termux), with commands like "free -m" (free memory) and "uptime" (busybox uptime) (for load average); "busybox ps", too, if implemented.
But, ultimately, it's a matter of feeling: if you feel that one version is more responsive, feel free to use it.
(switching back and forth is facilitated by the same partitioning, though going through a wipe all in recovery seems necessary)
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
ankerede said:
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
Click to expand...
Click to collapse
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
dsa8310 said:
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
Click to expand...
Click to collapse
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
ankerede said:
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
Click to expand...
Click to collapse
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396, and here:
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
Open GApps in post #416, and here:
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
elyl said:
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
Click to expand...
Click to collapse
No, they are not.
It's possible, but then uninstall by hand three apps: com.google.android.gsf, org.microg.gms.droidguard, FakeGapps1.1, and then reboot.
Hi dsa,
i'm on your latest microg version of your firmware with the playstore. But when i open the playstore and try to connect i get this error: [RH-01]
any idea?
problem iam facing now i cant play music while using google maps, any help?
dsa8310 said:
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
Click to expand...
Click to collapse
I give it a + for GApps. Still works nice with Google Play and able to use what you paid for with no issues.
Finally got more play time with the latest and I like it.. Using 1G, no upgrade memory at all..
Still need to add a few more apps.. but good to go..
Thanks @dsa8310
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
dsa8310 said:
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
Click to expand...
Click to collapse
Exactly what I did. A setup that I have never seen before had to be done. Great Job.
It's Open GApps' merit, not mine. Once the setup is done, everything else falls into place.
After Flashing Rom, On first boot There was no option shown for Copy Data.. There was only an option related to crDroid cloud. After Rom boot there was also no option device set-up just like miui rom or aosp rom. Now everything working perfect and smooth in this ROM. But Now I need to my all messages which I had taken backup on my google drive.
Please help if any working method is exist to resolve my problem.
I think you installed the basic version of nikGapps. Try with a larger one, like the omni, in order to have Google/Pixel Setup Wizard.
This way the setup should ask you to restore a google backup.
lucamacc said:
I think you installed the basic version of nikGapps. Try with a larger one, like the omni, in order to have Google/Pixel Setup Wizard.
This way the setup should ask you to restore a google backup.
Click to expand...
Click to collapse
Still did not work for me
StephenVannevel said:
Still did not work for me
Click to expand...
Click to collapse
I faced the same problems when flashing NikGapps myself. Although there is a download page listing all that goes into a package, there is hardly enough description. I'm sharing the solution I found here.
I tried installing the omni and the full version of NikGapps. Both packages included the 'Google setup wizard' but the wizard only gets triggered into action when it either recognizes a new account being added or at first boot after a factory reset. I didn't take any chances and factory reset the phone since it had nothing on it yet.
Other apps that I wish I had installed before were Android Auto, Google assistant and their dependencies. You can't flash them later (they give an error) and they don't work properly if they're installed from the play store.