Develop Bugs

[Q] Need help with CM problems.

I'm currently using their stable build from November 2012 CM10, which I've tried upgrading to there latest stable a few times every now and then, and every time I attempt to upgrade it states it was aborted about 2 seconds in. Is there something special I'm suppose to do to upgrade to 10.1-10.2? Also I attempted using CM installation program and it kept me on the same version, and now I'm getting a "Unforunately, Android keyboard (AOSP) has stopped working." error, which I figured was from gapps. Can anyone please point me in the right direction of what I'm suppose to do about this.

epykun said:
I'm currently using their stable build from November 2012 CM10, which I've tried upgrading to there latest stable a few times every now and then, and every time I attempt to upgrade it states it was aborted about 2 seconds in. Is there something special I'm suppose to do to upgrade to 10.1-10.2? Also I attempted using CM installation program and it kept me on the same version, and now I'm getting a "Unforunately, Android keyboard (AOSP) has stopped working." error, which I figured was from gapps. Can anyone please point me in the right direction of what I'm suppose to do about this.
Click to expand...
Click to collapse
Are you dirty flashing from 10.1 to 10.2 or clean flashing? If you're dirty flashing chances are that's what's causing the problem. From what I remember about upgrading from 10.1 to 10.2 was that a clean flash was necessary to having a bug free experience. My suggestion is backup your apps via Titanium Backup and factory reset on 10.2.

It wouldn't be advised for you to flash CM 10.1 to CM 10.2. Strictly because these are two different Android versions. First of all you will want to download the following links below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Note: This is strictly for the SGH-i747 and not the SGH-i747M variant)
CM-10.2.0-d2att.zip
Clockwork-6.0.4.3-d2att.img
CM10.2 4.3.X GApps
After you have downloaded the above files, you'll want to flash the Clockwork with Odin. If you are unsure on how to do this, please proceed to this tutorial. After you have flashed the last CWM, you will want to transfer the CM-10.2 image and the GApps to your root of the device. Then go into your custom recovery. Now wipe your data and dalvik cache. Then flash/install the CM10.2 zip file and then GApps. Now restart your device and you'll be on 4.3
If you are using TWRP, you'll need to find the appropriate version for that.

[Q] Play Store error on CM11

Hey guys,
New to this forum, and trying to obey the rules, but if I'm not.. please feel free to kindly slap me in the right direction!
I just installed CM11 on my Ouya using the [ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies thread as a guide.
After getting everything up and running successfully on my Mac (it was a bit harder than doing it with my Nexus 5 for some reason!) I am now all up and running. Seems to work great with a keyboard and mouse.
I have noticed that I am having some problems though with the install - mainly using the Play Store. The play store loads correctly, but I get the following error-
Error while retreiving information from server. RPC:S-7:AEC-0
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've Googled around about this and found lots of posts to do with old phones. However, all the fixes I have tried have not worked. I even erased and re-flashed CM11 to my Ouya and the same issue occurred.
I have tried:
Force-Stopping the Google Play Store, Google Play Services and Google Services Frameworks.
Clearing the app data and caches for the above
Rebooted to recovery CMW and cleaned cache and Dalvik
If anyone has any ideas, please feel free to point me in the right direction.
**UPDATE**
I just reset everything again and installed the latest CM11 nightly on my Ouya, downloaded the latest Google Play Store APK from the web using the browser and upon signing in got a slightly different error:
App could not be downloaded due to an error. (941)
Click to expand...
Click to collapse
Googling this shows... the same kind of ways to fix it (deleting cache etc) but sadly this just doesn't work for me

Are you flashing gapps after the ROM?

TwitchyEye said:
Are you flashing gapps after the ROM?
Click to expand...
Click to collapse
As far as I know, I did yea... Please tell me its something that simple!

Well it could be the gapps package, the OUYA has a pretty small system partition so only the banks minimal or pa micro gapps will fit. Also it could be crappy WiFi which is really common, these things really suck when it comes to WiFi. I have to tether mine from my phone.

Issues after updating to Android 11

I'm really considering going back to Android 10.
I'm not sure if the issue is Android 11 related . Root related , or magisk module related.
Occasionally when I try to wake up the phone all I get is a black screen , which requires a restart by holding down the power button.
Another issue I have come across is random freezes when using apps such as Google news and Amazon. When the phone freezes , I attempt to restart the phone. I press the power button, menu comes up I attempt to restart it . Get haptic feedback for the for the button press but nothing happens.
I'm on the latest canary build of magisk and all modules updated.
Has anyone has similar issues on android 11?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 3a XL

Nope haven't had any issues with Android 11 besides the Android 11 new feature media controls not always dismissing after I remove a media app from recents requiring the app to be force closed
I am not rooted and don't have a custom kernel installed.
So probably root related honestly try disabling magisk then reinstalling the stock boot img using adb

Thank you for the reply, I'll definitely give that a try
Sent from my Pixel 3a XL

ACHILLES R32 said:
Thank you for the reply, I'll definitely give that a try
Click to expand...
Click to collapse
I had issues like yours as well... Actually tried other roms but ended back on stock 11 with fx kernel. Not sure if it was the update I received to magisk or just the super clean install but this go around those issues so far have not returned.

adm1jtg said:
I had issues like yours as well... Actually tried other roms but ended back on stock 11 with fx kernel. Not sure if it was the update I received to magisk or just the super clean install but this go around those issues so far have not returned.
Click to expand...
Click to collapse
Thank you, hopefully I have the same luck as you with a fresh install of Android 11. I did a Android 11 image flash without a data wipe. Seems like it was a mistake lol
Update: if anyone has the same issue ,magisk systemless host module seems to be the issue . There is a github ticket open for the issue.
https://github.com/topjohnwu/Magisk/issues/3171
Sent from my Pixel 3a XL

Could anyone please test an app on G930F?

Hi,
I downloaded and installed an app on my Galaxy S7 G930F with customm ROM Resourrection Remix 7.0.2 and also on my Galaxy S20 with stock ROM. While it works with the stock ROM, it does not with the custom ROM.
This post suggests that the custom ROM is the problem. However, I am in contact with the app's support team and they ask, if I can test it on another device with this custom ROM. I cannot, because the S7 is my only device with Resourrection Remix.
Issue: I can install the app but after showing the start screen for a minute, it crashes.
Could anyone please install the following Roborock app (in Play Store simple search "roborock") and try to run it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Many thanks
Philipp

I tested it, it's not working too on with my Samsung S7 with Pixel Rom

hamzaharoon1314 said:
I tested it, it's not working too on with my Samsung S7 with Pixel Rom
Click to expand...
Click to collapse
Thanks!
I am still in contact with the support team, but they try to stall me...
I will let you know, if I find a solution.

Flippowitsch said:
Hi,
I downloaded and installed an app on my Galaxy S7 G930F with customm ROM Resourrection Remix 7.0.2 and also on my Galaxy S20 with stock ROM. While it works with the stock ROM, it does not with the custom ROM.
This post suggests that the custom ROM is the problem. However, I am in contact with the app's support team and they ask, if I can test it on another device with this custom ROM. I cannot, because the S7 is my only device with Resourrection Remix.
Issue: I can install the app but after showing the start screen for a minute, it crashes.
Could anyone please install the following Roborock app (in Play Store simple search "roborock") and try to run it?
View attachment 5628533
Many thanks
Philipp
Click to expand...
Click to collapse
Hey, in this case an logcat would be great. Start catlog and then open the app if its crashing stop the log. Save the log and send it to the ROM developers

master373 said:
Hey, in this case an catlog would be great.
Click to expand...
Click to collapse
When I created this thread, I tried to create a catlog, because I thought, it could help. Unfortunately, I did not find out, how to do so. Is there a catlog beginner's guide?

Flippowitsch said:
When I created this thread, I tried to create a catlog, because I thought, it could help. Unfortunately, I did not find out, how to do so. Is there a catlog beginner's guide?
Click to expand...
Click to collapse
There are several apps for that or you can do it with adb.

Question Installing OOS13 Open Beta 2

I'm having trouble following the official instructions for installing the open beta for OOS13 onto me LE2125. I downloaded the apk through the link in the instructions, but curiously it had a .zip extension after the .apk extension. I tried deleting the zip extension, and installing the file as I would any other apk, but the app did not match the description in the instructions. First, it was called "MyApplication2," and second, the interface was different. There's no gear icon in the upper right, just a single button:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I tap the button, and select the installation file, the app immediately crashes. Clearly I'm doing something wrong, but I'm not sure what, and from past experience I thought XDA would be more helpful than OP tech support. Any suggestions?

I can't be certain about this process becuase I don't have OOS on my phone, but the installation instruction you linked talks about a ZIP file, rather than an APK:
Download the latest ROM upgrade zip package from the specified server.
Click to expand...
Click to collapse
In step 4 it tells you how to handle/what to do with it.

Normally, I have updated through the Oxygen Updater app and not how the official instructions tell you to. Seems to be a lot easier and they have easy to follow instructions for updating locally, as well as their own version of that- using official update files, of course.

kodayoda713 said:
Normally, I have updated through the Oxygen Updater app and not how the official instructions tell you to. Seems to be a lot easier and they have easy to follow instructions for updating locally, as well as their own version of that- using official update files, of course.
Click to expand...
Click to collapse
Thank you, Oxygen Updater is working better than the official APK.

I would also like to know since it's a beta if there would be a different procedure with updating. I'm rooted on open beta 1 and I can simply install ob2 with oxygen updater or system update then just flash magisk modified boot, correct?

Arcide said:
I would also like to know since it's a beta if there would be a different procedure with updating. I'm rooted on open beta 1 and I can simply install ob2 with oxygen updater or system update then just flash magisk modified boot, correct?
Click to expand...
Click to collapse
That's the problem, I had to unroot, then it started working.

mustangtim49 said:
That's the problem, I had to unroot, then it started working.
Click to expand...
Click to collapse
Unroot before updating?