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...
Related
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
theking1st said:
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
Click to expand...
Click to collapse
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
cars1189 said:
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
Click to expand...
Click to collapse
Thank you @cars1189 for your answer. I used the device thread to do it but the problem is, I let it spinning for more than 5 hours. I have flashed many roms in my phone since i had it (more than 10 times or more) and i know that it does not take more than 10 mins max to install. But don't worry after that i went back and restored my previous CM 9 rom and right now i'm on the CM 11 build of 1-29-14 of your CM mass thread. It works fine, not at 100% but it doesn't drain my battery like your CM 10.2 build of 1-11-14 and it is almost stable. I will try tonight to use your ADC kernel with the jfbs CM 11 rom that first didn't work for me because I saw in your thread that this kernel may help it to load and install without the spinning issue. So i will give it a shoot. But anyways thanks for your answer and it means a lot to me really. :good:
GOOD
@cars1189 , I'm actually running the 6-18-14 build of CM11 and as far as it goes, i'm not encountering any major issue at the moment. The theme engine is working fine for me and battery life is great for my usage. I use this build as a daily driver, and it does a great job. Calls, texts, data, wifi, Bluetooth and GPS are all working. I had issues before with the amount of RAM available, but now that it has 375MB of RAM, it is more snappy. Just :good: Thank you for your work on our to make our phone still valuable today!! THANKS MAN!!!!!!
Hello there!
Recently I had some problems with random rebooting my device, so I decided to wipe the entire phone and install new version of CM12.1. I hadn't any problems during that process. I installed my favourite apps and configured my device. Everything worked quite nice and fast. First problem appeared when I did first reboot. Phone just.. gets bootloop. No matter what i'm doing - next reboot is always bootloop. I don't have idea what should I do CM11 starts to annoy me a bit.. I'm using a Huawei Ascend G620s-L01.
Any kind of help would be much appreciated!
Regards, Mat. @edit
Oh.. Same thing happens on CM13..
Anybody has an idea? :/ I realised that the AOSP ROMs based on Lollipop works! But after first reboot SIM stops working.. I'm gonna die..
edit:
ah, I noticed that radio and sim card stopped working on almost every ROM. It works only on some CM roms..
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?
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 .
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .