I am currently running CM11 and dealing with a lot of the problems that cm10 had. So tried CM12. Basically dead in the water. Never got past registration.
Very sluggish and the keyboard keeps disappearing. The installation of CM11 went pretty smoothly following the install instructions. Not so with CM12.
Maybe there is something I am missing. The instructions say that repartitioning is not necessary !?!??!
Anyway followed the instructions to the letter. Got the suggested recovery and flashed it just like on cm11. The correct gapps to use is always a crap shoot so I tried several. I even installed without gapps still had problems.
So any help here would be appreciated.
thanks
I have been testing CM12 for a few weeks and have a few of the same problems. It seemed like at first it was pretty snappy, but now it's sluggish, keyboard disappears constantly, and my biggest pet peeve is that quite a few of my apps are now unavailable for this device. They worked before, so it's a bug in CM or one of the newer Android versions. I'm just going back to an older ROM for now.
Hi cosmic_kid
I'm asking these same questions in the cm12 QA and dev pages and not getting anywhere. They all tell me to go read some more or stop being rude !?!??!?!
I am currently running cm11 and only have the usual problems just like cm10 had. i.e. battery, black out, losing wallpaper.
So I thought cm12 should be a piece of cake !!! NOT SO !!
There must be something different with the install that is screwing something up.
I tried the recommended eng recovery and the latest TWRP and CWM. Same results. After gapps is installed things go to heck.
I did try running cm12 before installing gapps and it ran smooth. After gapps sluggish and never got past registration. Keyboard never came up !?!?!?
I don't know what to do so I will download the latest nightly and try again.
I Feel Your Pain!
Guys, I know exactly how you feel. I merged the partitions according to the other posts, formatted cache and userdata to f2fs and tried all the nightlies that came out, but keyboard problems, superuser problems and setup crashes just made it impossible to get anything going on my trusty 8gb Nook (BNTV250A). The closest I got to getting anywhere with CM 12 on it was when I updated the CM 12 March 26th nightly on CM 11-M12 and added pa_gapps-modular-nano-5.0.1-20150315-signed. Play store worked, I was able to get into developer options and enable root access and it looked hopeful, but alas it was so slow and lagging that I have given up for now. I used repart.img to go back to stock, (touch pad didn't work on stock since I had upgraded to 10 touch!) booted off SD and installed CMW recovery to restore my CM 11 -M12 configuration. I'm staying in touch through all the threads and hopefully we will one day have a smooth CM12 on our beloved Nooks!
CM12 is now working very smoothly on my 16gb nook. I didn't have to repartition anything. I just about got rid of my 16gb nook because it's older and slower than the newer 8gb nook. Glad I didn't.
So until there is a "how to" thread on how to get it to work on the 8gb nooks I will be using the older one.
The devs said that they didn't have a 8gb model to test their nightlys on. I'm wondering if they test them at all ???
What did you do to get it to run smoothly? I have the 16GB and it slows down all the time with CM12. I read gapps causes a lot of head-aches so I've been tempted to run without it and just side-load all my apps... :/
cosmic_kid said:
What did you do to get it to run smoothly? I have the 16GB and it slows down all the time with CM12. I read gapps causes a lot of head-aches so I've been tempted to run without it and just side-load all my apps... :/
Click to expand...
Click to collapse
pico gapps and Demetris' 16GB CM12 with the Tricker Mod stuff = faster than they day I bought it.
Now I just need 8GB working the same, since I have two of those!
Related
I have a Motorola Atrix on Bell (Canada), and for the past few months it's been running perfectly on a ICS version of Paranoid Android with no issues. I recieved a 32gb SD card for xmas, and I was reinstalling the ROM to move it to internal storage so that I can use my SD Card for music. I decided that since I was reinstalling the ROM I may as well get a new one, so I got the Paranoid Android JB ROM. I installed it to internal storage, with the tweaked body option, and it worked fine. Then I used the option chooser and installed some gapps like the play store, maps, youtube, as well as nova launcher and adobe flash, then rebooted. I first noticed that the wi-fi isn't working. It gets stuck at 'turning on wifi'. Also, none of the gapps were installed, just the launcher. The main issue, is that every couple minutes the phone will shut off. It also takes much longer than usual at the M screen (30-60 sec). It seems to turn off whenever I press the power button to wake it, whenever I plug in or unplug the device, and occasionally just randomly when the device is in use.
The phone is semi-operational right now besides having no Play store and the very frequent shut offs. Any help would be appreciated. I've tried a few different JB ROMs and they all have the shutting off issue, but Paranoid Android seems to be the only one with the Options chooser not working correctly.
Flashed back to the CM7 ROM Neutrino 2.9 . Works perfectly. Still though, is there any reason the JB Roms won't work for me? I know I've tried one in the past and it worked fine, but didn't want to keep is since is was still in Alpha at the time.
bjgrenke said:
Flashed back to the CM7 ROM Neutrino 2.9 . Works perfectly. Still though, is there any reason the JB Roms won't work for me? I know I've tried one in the past and it worked fine, but didn't want to keep is since is was still in Alpha at the time.
Click to expand...
Click to collapse
All ICS/JB ROMs are in early beta still. They're stable, just lacking hardware acceleration.
Did you do proper wipes and format /system partition before installing? Did you re-downloading the ROM and installing again? Did you try CM10 build from EPinter's? Sounds like your using Aroma installer, try flashing normal zip files for gapps, never had issues.
A lot of people are running CM10 as daily without issues, so retrace your steps to see if you overlooked anything.
エイトリックス から 送ります
Hi, I just recently came back to this forum, pleased to find that we now have CM10 working on Amaze ! (Thank you sportsstar!)
However I did have a couple issues when installing, and seeing as how a lot of people in the CM10 thread asked to redirect questions here, I figured I make a thread.
My problem is that it seems as though no matter what I install, there is always a problem. As far as I know, I am using the basic ICS-Ruby kernel that was dumped 6+ months ago. I installed the CM10 rom using 4EXT, with no issues.
However when I installed the Gapps (gapps-jb-20130301-signed) I constantly had the Android keyboard force close on me. So instead I tried to install the JB-4.2-Gapps-signed. With these, the Android keyboard would not force close but the Google Now search app would force close everytime.
I've also tried installing the DARK GLASS 0.6 ROM by jose, but then the wifi would not turn on. (When I would try to turn it on, it would just hang saying "Turning on Wifi").
It is probably worth mentioning that I did do a full wipe everytime I installed the CM10 rom. I was sure to be very thorough. When I installed DARK GLASS 0.6 ROM, again, I did a full format of partiitions, and a wipe. Still the issues above arise.
Can someone maybe help me out as to what I'm doing wrong? Thanks!
------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: I just looked at my phone info, and apparently the kernel I'm using is 3.0.53-gd28c6eb. Is this okay or do I need to flash a new kernel ?
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
My CM 10.2.1 has become increasingly temperamental until finally it always boots to a black screen (just backlight) unless I restore the last backup from my CWM SD card. I'm guessing the boot image has frayed a little around the edges and since I didn't keep a "brand new" backup from the original flashing, the only backups I have are probably a little wonky.
So it's been a little over a year since my original installation following digixmax's excellent directions. I've been thinking of just starting fresh with 10.2.1 and rebuilding my apps so here's a couple of questions:
1. Do I have to go all the way back to Stock 1.43 to follow these same directions? I had my NT repartitioned at B&N before I flashed CM, if that makes any difference.
2. Do I need to root before I flash CM (been too long and I just don't recall)?
3. After a fresh CM flash, would it be wise to use my last backup and Advanced restore so I can skip boot and (maybe) system--or should I just man-up and rebuild my apps from scratch?
OR....since I'm going to go through all of this, should I just flash CM 11 or 12 and get a newer system in the bargain? Reading about updating from CM 10.x to CM 11 has me a little spooked because I haven't been able to track down a definitive statement on whether the partitions have been combined or what that might mean for me.
Does anyone have a favorite 11.x or 12.x build? It looks like the M4 nightly for CM 11 was pretty well-behaved, but there are just so many choices.... I've been more or less happy with 10.2.1 (except for the now almost constant boot issue and lockscreen non-function), but I also know that app updates will eventually pass me by if I stay on 10.2.1.
I'd appreciate any help
Been using 12 for the past few months, no issues.
Sent from my Sensation using XDA Free mobile app
WnG88 said:
Been using 12 for the past few months, no issues.
Sent from my Sensation using XDA Free mobile app
Click to expand...
Click to collapse
Is there a particular set of instructions you followed?
Sent from my Nook Tablet CM 10.21
nmyshkin said:
My CM 10.2.1 has become increasingly temperamental until finally it always boots to a black screen (just backlight) unless I restore the last backup from my CWM SD card. I'm guessing the boot image has frayed a little around the edges and since I didn't keep a "brand new" backup from the original flashing, the only backups I have are probably a little wonky.
So it's been a little over a year since my original installation following digixmax's excellent directions. I've been thinking of just starting fresh with 10.2.1 and rebuilding my apps so here's a couple of questions:
1. Do I have to go all the way back to Stock 1.43 to follow these same directions? I had my NT repartitioned at B&N before I flashed CM, if that makes any difference.
2. Do I need to root before I flash CM (been too long and I just don't recall)?
3. After a fresh CM flash, would it be wise to use my last backup and Advanced restore so I can skip boot and (maybe) system--or should I just man-up and rebuild my apps from scratch?
OR....since I'm going to go through all of this, should I just flash CM 11 or 12 and get a newer system in the bargain? Reading about updating from CM 10.x to CM 11 has me a little spooked because I haven't been able to track down a definitive statement on whether the partitions have been combined or what that might mean for me.
Does anyone have a favorite 11.x or 12.x build? It looks like the M4 nightly for CM 11 was pretty well-behaved, but there are just so many choices.... I've been more or less happy with 10.2.1 (except for the now almost constant boot issue and lockscreen non-function), but I also know that app updates will eventually pass me by if I stay on 10.2.1.
I'd appreciate any help
Click to expand...
Click to collapse
The "boot to black screen" is a known bug in CM10.x (you find some brief discussions of this issue in the old CM10.x development thread.
You don't need to go back to stock to upgrade from CM10 to CM11 or CM12. The general process for performing the upgrade is outlined at http://forum.xda-developers.com/showthread.php?t=2670589. (For CM12.x, you'll need to locate a compatible recovery (to use in step 1(a)) which is typically referenced/linked in the first post of the corresponding CM12.x development thread).
If you're considering CM11 builds, I'd suggest you select a build that is sufficiently recent to have incorporated fixes for the Stage Fright security vulnerability (see http://www.cyanogenmod.org/blog/more-stagefright).
digixmax said:
The "boot to black screen" is a known bug in CM10.x (you find some brief discussions of this issue in the old CM10.x development thread.
You don't need to go back to stock to upgrade from CM10 to CM11 or CM12. The general process for performing the upgrade is outlined at http://forum.xda-developers.com/showthread.php?t=2670589. (For CM12.x, you'll need to locate a compatible recovery (to use in step 1(a)) which is typically referenced/linked in the first post of the corresponding CM12.x development thread).
If you're considering CM11 builds, I'd suggest you select a build that is sufficiently recent to have incorporated fixes for the Stage Fright security vulnerability (see http://www.cyanogenmod.org/blog/more-stagefright).
Click to expand...
Click to collapse
Thanks! I've been following a couple of related threads for awhile now. The most recent post in the thread following this one finally gave me the push and info I need. Just need to pick up another microSD card tomorrow
nmyshkin said:
...
The most recent post in the thread following this one finally gave me the push and info I need. Just need to pick up another microSD card tomorrow
Click to expand...
Click to collapse
Unless you plan on using the uSD card also to backup your current ROM and setup for ease in rolling back (which is a good idea), you don't need an external uSD card to upgrade from CM10 to CM11/12.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2