Hello,
First, I want to say that I hope this is in the right subforum. Otherwise, please, move this thread.
So I have a big issue with using Cyanogenmod 12 and 13 on two totally different devices; the international version of Samsung's Galaxy S4, and the OnePlus One. Installing either version of Cyanogenmod works perfect, but as soon as OpenGApps is flashed (Tried nano, pico...) and Android is loaded up, it gets stuck in an infinite stream of crash messages, telling me that "Unfortunately, the process com.google.process.gapps has stopped."
I have found a fix. BUT this only works on CM13. If you click-spam your way through the first time launcher, then navigate to Settings and find System Restore and perform said operation, then the crashes with magically go away and the phone will run without any problems at all. This is good enough for my OnePlus One.
However: There is no stable build of CM13 for the Galaxy S4 international, in the latest Nightly-build I tried for it, call audio was not working at all.
Does anyone know why this is happening, and how do I go about fixing this, other than the solution I found above?
Help is much appreciated!
I really suspect it being an OpenGApps issue. Though I do not understand why as the same build/phone has worked fine with it before.
Are there any reliable alternatives?
Related
i have galaxy s it's work normally and it's have cm 10
but today when i turn on give me this note
(Unfortunately, the process com.google.process.gapps has stopped)
another note after i make it's ok
(Unfortunately, setup Wizard has stopped)
and i press ok again
give me firs one and still like that give me this two note again again again ...........
because that i can't work in my tell phone
i try install cm10 again and gapps but nothing
and wipe data/factory reset
but it's not work
i need to fix it today i can't live without my phone
CM10 is still in nightlies right?
meaning that they are a bit unstable and not really that useful as a daily ROM if you don't like the kind of surprises you have described.
find another ROM or revert to a stable build of CM10
Hi!
I'm new on XDA, so I'm sorry if the thread is placed in wrong subforum - if it is, I'm asking mod to move it in more proper place.
I bought Lenovo Lemon 3 - it was advertised as Vibe K5 Plus, but apparently the seller wasn't that reliable as I thought. As far as I know, the differences beetwen these models are little or none, but I have pretty big problems with the phone.
First of all it has some preinstalled software, which isn't in Play Store and some of them I can't even find in the net. The apps I would like to get rid off are KingRoot, MaxxAudio and SecurityIT. I successfully managed to disable MiBrowser - with help of KingRoot tool Purify actually. I tried to disable SecurityIT also, but if I do that I can't enter Settings->Apps. When I try the com.android.settings is stopped and it's not working till i enable SecurityIT again.
Second of all is that process com.android.phone is stopping randomly. Sometimes I click "ok" and I it starts working again. But sometimes it keeps crashing until I restart the phone. Since it's a dual sim phone and I'm using only one sim I thought that maybe this is causing a problem, but inserting second card wouldn't work, so currently I have no idea what is causing the problem. I tried cleaning cache and appdata with no effect. If the process is crashing and somebody will call - the phone restarts itself when I try to answer.
Thirdly it's hot. Even if I'm not doing anything and all apps are off and Im charging the phone it sometimes says that it can't be charged because of too high temperature on battery. Sometimes it works fine, but sometimes it's too hot too touch and I don't know why.
Oh, and one more thing. Something is installing random software. It looks like every time I open Chrome something is opening new tab and redirecting to PlayStore. I am trying to close these tabs while they're loading, but sometimes it loads too fast. Every morning I uninstall some new app, which is apparently installed by night. And those apps aren't added to my Play Store Account. I have disabled unknown sources, but I can see that phone is checking for updates around 2 a.m - so maybe those apps are from there - but I can't see any possibility to disable auto-updates. I have disabled auto updates in Play Store and I have "Lenovo Enhanced Experience" unchecked. Most of apps I installed from Play Store are games I had on the previous phone so I am sure they're not dangerous. Any ideas to prevent the installation of this unwanted software will be appreciated.
Since I used KingRoot to disable MiBrowser I apparently rooted it, but I was reading that this works only with KingRoot installed and with internet connection. And it's sending some data to China, which is not nice. RootChecker says it's rooted.
Lenovo Launcher it's not great either, I downloaded Lollipop Launcher from store and it works fine, but I had to block Lenovo Launcher from autostart, because it was very irritating and was enabling few times.
I am living in Europe so I was thinking is it possible to put on this phone Lenovo Vibe K5 Plus Stock ROM? Or is it this "trashy" like the one I have? I really like specs of the phone and I don't wanna return it, but I don't like the software behavior. Can you tell me what I can do to improve this? I don't care about warranty and I would like to have pure, non trashy Lollipop, so if it is possible somehow I would be glad for any help.
Thank you in advance for any help!
Lenovo Lemon 3 K32C36 > Cyanogenmod 14 - 7.1.1: SUCCESS
Hi
Did not know where to post this, I was not allowed to post in developer forums:
For those unlucky enough to have bought a Lenovo Lemon 3, I offer hope. My daugther's 'Lemon' now runs cyanogenmod 14 near flawlessly.
Here's what finally did it.
1st you have to unlock the bootloader. I found this page, google translated it,
http://4pda.ru/forum/lofiversion/index.php?t717648-420.html
and near the bottom is this link to a 'one-click bootloader unlocker'
http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=56376
[All this is similar to the Lenovo unbricking described here:
https://forum.xda-developers.com/k5-plus/how-to/unbrick-vibe-k5-plus-qfil-qpst-method-t3467830
but a lot of that is not what you need now.]
You have to install and run QPST from this on a Windows machine, and the Lenovo and Qualcomm USB drivers and the Visual C thing too to set it up.
I fiddled for a while but eventually got QFIL to recognize the Lemon. Keep in mind Win is pickier about USB cables than Linux.
Following instructions carefully, that one click then worked!
I moved back to Linux and adb and did the second part (pasting instructions from the Win .bat file into a root terminal). Sure enough, when I booted into recovery I had TWRP! But it showed no files on the Lemon and said there was no OS there! Nevertheless I was able to boot back into the awful K32C36 system with no problem.
So I went back to adb and did it again, but this time from the info and links on this page - but I did not at that time see the need to root.
https://forum.xda-developers.com/k5-plus/development/recovery-twrp-3-0-2-0-lenovo-vibe-k5-t3391100
Beyond all expectation TWRP then booted and all was visible.
I then picked this ROM page because someone had wrote that they had it working on K32C36
https://forum.xda-developers.com/k5-plus/development/unofficial-cm14-lenovo-k5-k5-plus-t3478288
to get this
http://moto.shreps.fr/Lenovo Vibe K...cm-14.x/cm-14.1-20161213-UNOFFICIAL-A6020.zip
Then onto SD card with it and pico 7.1.1 gapps
Install with TWRP (after backing up lame old ROM and wiping system, data, cache, as advised).
Long wait during 1st new system boot (I thought it was defeat) -- but comes the little blue man bringing very good Nougat.
Hope someone gets helped here .
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Hi all!
I have already commented on a opened thread about this problem but, as it was a similar, not exactly the same problem, I decided to make a new one, and delete the comment. I tried to install AOKP osprey nougat on my Moto G 2015. It installed with no problem at all, I installed it with Magisk and OpenGapps micro. But, as soon as the phone turned on and I started to go through google registration stuff, I started get a "advanced settings has stopped" with a close button. It was happening forever. I could fast click close and do one click on the phone but the error message was popping up every second. It was unusable, forcing me to not use aokp custom rom. I'm waiting for a new release. U guys do an awesome job and I would love to be able to use it on my phone...
Ty.
:crying:
Hello again guys! A new aokp Osprey version has been released in 05/23. I tried it in my Moto G 2015 that was running LineageOs with no problems. Just like the older ones it installed fine with gapps. But the further problems that I had with the older versions happened again. In the first boot, after installation, the popup error, that I talked about in the previous post appeared, but, this time I managed to get rid of it by just closing it some times (approx. 20x), so then I could login to my google account. In this first boot the phone was working fine, I installed some apps, changed some configs, and it seemed to be working ok. I decided to reboot my phone for testing purposes and here is where stuff broke again. The same error popup that I talked about, but now even with me closing it for at least a hundred times the popup was showing everytime. So, saddly, I just had to return to LineageOS.
That's it, bugs are still happening... But keep up with ur good work and, hopefully we will have some amazing Osprey ROM in te future.
Same bugs...
New ROM (aokp_osprey_nougat_nightly_2019-06-06_ota.zip), same bugs...
I'm giving up on AOKP for now...
Long story short, obtained said device from somewhere and decided to experiment on it, and to survey the modding scene a bit while at it. Yeesh. What happened after that, in summary:
Found XDA. Then found after_silence's roms. Downloaded them.
In the process, I learned how to setup adb and how to make Windows recognize this outdated device's drivers. Now I can do these with my eyes closed.
Flashed TWRP 2.3.2.3. Installed as's first mod with gapps package. But something was wrong, google apps showed only stupid ad-like results after every search. Wiped it and continued searching for other mods. Stumbled upon this. Downloaded the latest one. Flashed it. When I tried to install the gapps package there, twrp said not enough storage to install gapps package. I learned how to use gapps-config file. To no avail. Experimented with each one, including the aokp ones. They were stable, but main menu was like 5 fps. And most of the time, google play stopped. Clock stopped. Trebuchet stopped. Even if nothing stopped, something stopped, sooner or later.
At last, I installed these: cm11 20140419 and gapps lp 20141109. Google continued to show stupid results. Uninstalled google play updates, restarted, it updated itself. Now, all seems stable enough, only with the never before seen, ridiculously stupid glitch of all:
The device restarts if it goes to sleep. Yeah, the screen dims, dims... and restart. Pressing power button once directly reboots the device. There's no sleep - either the screen stays on until the battery drains, or restarts.
At this point I can gladly get on my knees to beg someone for a solution, or for someone to please tell me, "here, these are the latest and HASSLE-FREE android 5.x rom and suitable gapps package".
Please.
VerpinZal said:
At last, I installed these: cm11 20140419 and gapps lp 20141109. Google continued to show stupid results. Uninstalled google play updates, restarted, it updated itself. Now, all seems stable enough, only with the never before seen, ridiculously stupid glitch of all:
The device restarts if it goes to sleep. Yeah, the screen dims, dims... and restart. Pressing power button once directly reboots the device. There's no sleep - either the screen stays on until the battery drains, or restarts.
Click to expand...
Click to collapse
Hi @VerpinZal,
I installed that CM11 version as well, but without gapps (using F-Droid instead).
Cannot reproduce the restart instead of sleep. Screen dims, turns off ... and turns on again w/o any restart.
Cheers!
Edit:
After factory reset @ cwm recovery I was able to flash CM12.1 w/o any issues as well.
Instead of gapps I installed f-droid and aurora store.
A Logitech diNovo Mini helps me to overcome the broken touch function. It connects automatically to the Mediapad via BT after booting up.