Related
Q&A for [ROM][CM12][5.0][Lollerpop][KANG] Grouper nightly kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM12][5.0][Lollerpop][KANG] Grouper nightly kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will not flash
I keep trying to flash this rom and all I get in TWRP is Error executing updater binary. I was able to flash other 5.0 AOSP roms but I am having trouble with this one.
BSZAospLP v1.1 flashed fine as well as an older build of your rom. The last 2 builds will not flash at all. Same error. TWRP and MultiROM are updated to current versions.
My rom shows a camera installed when I go to manage apps, but it doesn't show in the app drawer and I can't access it. Stock launcher no hidden apps or anything
dcwiker05 said:
My rom shows a camera installed when I go to manage apps, but it doesn't show in the app drawer and I can't access it. Stock launcher no hidden apps or anything
Click to expand...
Click to collapse
For me this issue existed already on KitKat. I think the camera app is kinda hidden because the N7 camera isn't designed to take pictures. But some launchers allow you to create an activity shortcut to the respective activity of the camera app to launch it. This works fine for me with action launcher.
First off, I do know that this is a work in progress, and so far, it has been an excellent release. But, I want to know if anyone else is noticing the following issue below or if it could just be my device.
Has anyone noticed if their keyboard response is slow within games, such as Game of War? I'm noticing severe lagging in the keyboard when I'm attempting to chat, send email or do searches. Anything that requires keyboard entry is slow.
I've noticed this as well in other games. I also am running CM12 on my Droid RAZR HD (XT926) and keyboard response is fine. It only seems to be with this build on my Nexus 7 (2012) WiFi, so I can't tell if it's just because Grouper Nexus 7 is just not up to the task of running this, or if it's just the ROM is still early.
I've tried both the stock keyboard that comes in CM12 as well as my default that I use, Swiftkey. Again, on my phone (XT926), Swiftkey works great in the games.
Outside of games on my Nexus, the keyboards work fine. It's only within games that I see the severe lagging. And by severe lagging, I mean that I will select into the input box to start typing and then the keyboard may not show up for 15 seconds. One time, it took over 30 seconds. And then, once the input box has focus, typing on the keyboard appears to do nothing and then maybe another 15 to 30 seconds later, it starts to show up, one type at a time, with seconds of lag between types. Sometimes, it eventually clears up for a bit, but if I start to type longer, it can then start to lag again like before.
Just curious if anyone else has noticed this. I've done a clean wipe. I'm running 11/28 build with f2fs on the data partition, and I'm running it with the MKernel-a72 kernel.
Thanks!
UPDATE:
Okay, downloaded the 12/01 image and the keyboard issues appear to have been taken care of.
for me too the 20141205 build is not booting
it is checked. I am trying
pie control
How far are we from setting pie control, either slim pie or paranoid pie. In a lolipop release? This is the most important feature for me.
jasius said:
How far are we from setting pie control, either slim pie or paranoid pie. In a lolipop release? This is the most important feature for me.
Click to expand...
Click to collapse
I think CM discarded Pie control, they didn't include it in CM11. I put my hopes in SlimLP, since Slimkat had a decent Pie implementation.
Problems
Hi,
thanks for the ROM. I have a few questions, problems for which I would like to ask for help:
data and cache partitions are mounted without the discard options. Is this normal? Can this be added?
GPS is not working: E. g. the GPS status app (or Google Maps) does not see a single satellite.
I cannot copy files from the Windows Explorer or by adb push to the (emulated) sdcard/internal memory: error message of adb: failed to copy 'xxx' to '/storage/emulated/0/xxx': Read-only file system
Thank you for your help
Ok answering myself: With the latest build (141222) (part ?) of the GPS problem and the copy problem have gone:
The GPS status app can now find the satellites. Also in one map app (OruxMaps) the location is shown. Unfortunately, it still does not work with google maps.
For whatever reason it is now possible to copy files and directories with the Windows Explorer to the "internal memory". But not with adb push?!?
jmozmoz said:
Hi,
thanks for the ROM. I have a few questions, problems for which I would like to ask for help:
data and cache partitions are mounted without the discard options. Is this normal? Can this be added?
GPS is not working: E. g. the GPS status app (or Google Maps) does not see a single satellite.
I cannot copy files from the Windows Explorer or by adb push to the (emulated) sdcard/internal memory: error message of adb: failed to copy 'xxx' to '/storage/emulated/0/xxx': Read-only file system
Thank you for your help
Click to expand...
Click to collapse
Is mtp not working on the latest build as of yesterday?
It's not showing up under Device Manager at all so I can't browse for drivers. I've tried disabling and reenabling debugging but I get nothing. When I go to Storage and try to select USB Computer Connection, I get no options or drop down.
It does charge however.
Black screen upon boot
I just flashed the latest nightly after converting it to F2FS using the Windows tool. I also did a full wipe and manually checked to make sure system, data and cache were in f2fs. The ROM boots and 'optimises' apps just fine but then I just get a backlit black screen, only the power button works.
What might be my mistake?
[Solution HERE: disable AFWall+-2.0-alpha2]
Hey there,
I installed the optimized CM12.1 20150602 with Xposed and Xprivacy and now I got a connectivity problem:
When I come back from flight mode or enter a known wifi, wlan0 connects to my local wifi but Internet still gets routed through mobile data (LTE).
ping rounter not possible
Wifi icon has a "!"
netcfg shows:
Code:
rmnet_usb0 UP 10.175.104.107/29 0x00000041
wlan0 UP 192.168.2.126/24 0x00001043
on turning off mobile data, wifi data starts working and keeps working when I turn mobile data back on
I tried with a clean system: no problem, added Xposed/Xprivacy: no problem. So I guess one of my apps with root access must have caused that bug.
Possible candidates: AFWall, AdAway, droid VNC, OpenVPN, OS Monitor, SSHDroid, Tasker, TB.
Anyone knows how to fix this? I guess it must be a problem of how and what gets prioritized.
The setup took me quite some time and it would be great if I could fix this without starting from scratch. Plus I'd like to know the source of the problem.
Log attached.
I run none of the apps you mention and have the same issue and it happens on all wireless networks. I know of two workarounds, if they can be called that.
First is to cycle WiFi from within settings. When I do that it normally works right for a few days after.
Second is to power cycle my wireless router. That normally only works for a day or so as well.
I personally feel this is a flaw in CM as I have also seen the exact same issue on CM and any ROM built from it.
FIX
I found a fix for my problem by trial and error:
First I dirtyflashed the system again which didn't help, so I thought the problem must be in /data... thats where wpa_supplicant.conf is located so I had a look at it and strangest thing was:
The priority numbers for high eventhough it had only three entries. I changed them to 1/2/3 and rebooted. After that automatic connection to wifi worked again. BUT:
I rechecked the
Code:
/data/misc/wifi/wpa_supplicant.conf
again and the priority was back to the old state: 41/47/38 - in this order for the only three networks.
So the fix for me was: Change priority and save. Reboot afterwards.
Can someone elaborate on how this could fix the problem?
Oh and I must revoke my solution. Didn't work on the other network. :/
OK next trial and fail: deleting wpa_supplicant so it gets renewed. No difference.
Maybe I just try to install a fresh install and just restore /data.
I tried deleting the whole /data/misc/wifi folder. Didnt fix it!
And now I even installed from scratch and restored /data only from backup. Didn't help either!
What do I have to remove to fix this???
Rule number 1 of the Optimized ROM: do not use Xposed if you want support. So, uninstall Xposed, make a logcat of your issue if uninstalling Xposed doesn't fix it, then send that to AntaresOne.
He doesn't read the threads in Q&A, and wouldn't reply to this one anyway because of Xposed.
Strephon Alkhalikoi said:
Rule number 1 of the Optimized ROM: do not use Xposed if you want support. So, uninstall Xposed, make a logcat of your issue if uninstalling Xposed doesn't fix it, then send that to AntaresOne.
He doesn't read the threads in Q&A, and wouldn't reply to this one anyway because of Xposed.
Click to expand...
Click to collapse
Yes, thank you, I know that.
I didn't report a bug, I'm just trying to understand the problem, so I won't run into it again.
I tried tried a clean system and a clean system with Xposed and Xprivacy installed and did not have that problem, so I ruled that out.
Lucky for me: I did mention that in my OP.
My point is that you're presenting your information to the wrong audience. You need to post the logcat, without Xposed, on the Optimized CM12.1 thread, if you haven't already done so. That way the people who can actually do something about it can attempt to fix it.
I do apologize however for not reading the thread properly. It was late at night for me and I was half asleep. *sigh*
SOLUTION
So I hope it is fixed now.
My last resort was to flash a new modem/non-hlos.
I was on a 4.4.2 modems (DTM-I9505XXUGNG8_I9505DTMGNG3_I9505XXUGNG8_HOME.tar) before and updated to the latest modems for T-Mobile Germany: DTM-I9505XXUHOD5_I9505DTMHOD1_I9505XXUHOD5_HOME.tar.
This seemed to have solved my Wifi problem.
Step-by-step (no data loss but still: make a backup):
Check which is the latest ROM for your country/carrier on sammobile.com
Download ROM on sammobile.com or samsung-updates.com (no account necessary).
Extract ZIP > rename extracted *.tar.md5 to *.tar > extract modem and non-hlos file from *.tar with WinRAR or the likes.
Shutdown mobile and start into Download mode (Vol-Down)
Run Odin, disable Auto-restart and flash modem and reboot back into Download mode (I did that twice because people were hinting that but I doubt it's necessary).
Flash non-hlos in case you have a S4-LTE version.
Reboot and test.
/edit: didn't fix it.
Solved this time?
I think I finally found the problem: AFWall v2.0-alpha2 seems to cause the connectivity problem.
As soon as I deactivate the Firewall connection won't have any problems. I can't believe I needed so much time to find the bad boy.
Guess I didn't want to reduce security on my system, so I tried to avoid disabling/deleting my firewall.
Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images
Oooh... now I can test this to see if it fixes my G+ compatibility issue
The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you
meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.
irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211
#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.
This will work on a Nexus 9 or it only works in pc's?
when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy
Waiting for rooted system.img for Phoenix OS 2.1.0
SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy
MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?
Guys, when to expect a rooted image for V 2.1.0 x86
thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?
Hi fellow OnePlus 2 users,
I've got a problem with my phone and I'm not finding the solution on myself so I hope you can help me.
Since I upgraded for LineageOS 15.1 to 16 I have some problems with my bluetooth connections. Some devices that previously worked (BMW car audio, Windows 10 PC) are now refusing to connect while other devices (plaintronic headset) are still working.
What I already tried:
- remove the pairing from both devices and pair again - That doesn't work. I can't get them to pair again. When I try to pair my phone with the BMW I get the message that the pin wasn't correct. But neither the phone nor the BMW did show any pin.
- Clear Cache of Bluetooth App
- Reset of network settings
- Factory Reset
Nothing helped. When I checked the Bluetooth settings I noticed that the phone says the MAC is 00:00:00:00:00:00.
Hopefully you have an idea. Thank you very much.
With best regards
Markus
Just a small update.
I did a downgrade to LineageOS 15.1 and a factory reset. After that Bluetooth worked as expected. It's also showing the correct MAC Address. I then tried to upgrade again. The result is the same. Bluetooth isn't working right and the MAC is shown as 00:00:00:00:00:00.
Same problem here!
Hi,
after flashing the NoGravity Kernel the problem was partly resolved. I could connect to all Bluetooth device again. But my Mac Adress is like 00:00:00:**.**.**. It changes every reboot I need to pair every device after every reboot again.
As I posted in another thread, I'm having the same issue. Coming from an extremely ancient Marshmallow AOSPA build, I Advance Wiped all partitions except Internal Storage, flashed OOS 3.6.1 firmware, installed one ROM (HavocOS, AOSP-based), got the 00:00:00:00:00:00 MAC issue, advance wiped everything again, installed a different ROM (Liquid Remix, LineageOS-based with NoGravity-based kernel), got the 00:00:00:**:**:** issue.
If I restore my NAND backup of Marshmallow, I see my correct Bluetooth MAC even with the 3.6.1 baseband, so I know the firmware update didn't break it. But damned if I can figure out how what steps I need to do to make the correct MAC show up in Pie.
I managed to fix this almost by accident while screwing around trying to figure out what was broken. Literally all that needed to be done was
Code:
/vendor/bin/btnvtool -O
(capital oh, not zero) as root and reboot. Running this command generates the /persist/bluetooth/.bt_nv.bin file, presumably with corrected permissions, since that file already existed on my device with the correct MAC address before I ran the command. Running the command again now spits out an error saying that the file already exists. The one command run fixed the MAC, and it's subsequently survived multiple reboots.
What's even more interesting is that /vendor/bin/init.program_bdaddr.sh already calls this command. I can only theorize that when the init script is being run, it lacks some necessary SELINUX privilege to properly create the file.
In any case, please try running this command and let me know if it works for anyone else.
@ dion_starfire
You are my personal hero. Your solution fixed my MAC address.
I have the same issue! How do you do that? Where do you change the code
No code change, just load up a terminal like Termux, "su" to become root, and run the command. Then run "exit" twice to close the terminal.
dion_starfire said:
No code change, just load up a terminal like Termux, "su" to become root, and run the command. Then run "exit" twice to close the terminal.
Click to expand...
Click to collapse
Running the command broke my wi-fi mac , now is 02:00:00:00:00:00. ? Before had One problem, now have two
It worked flawlessly for me, thank you both very much!
You have to report the issue to LineageOS GitLab issues. Apparently dozens of users are having the bluetooth issue with latest version LineageOS 16.0 but now with older versions.
dion_starfire said:
No code change, just load up a terminal like Termux, "su" to become root, and run the command. Then run "exit" twice to close the terminal.
Click to expand...
Click to collapse
come faccio a diventare root? su not found
Hi anyway you could tell how to do this on my Android phone. I've got the termux app but can't seem to get to the right place to add /vendor/bin/btnvtool-O
Cheers
Got it sorted downgraded to lineage 15.1 then flashed lineage 16.0 build 190801 and gapps micro for same and everything is working again. Camera is working and Bluetooth is working so far.
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
AFAIK these roms cover other Moto G3 versions but investigate more for yourself.
Always keep Nandroid backups using TWRP of your running Rom. I keep copies of my latest Android 10 Chli360/Lineage running Roms on my Phone's portable SD card in the phone and also on my Laptop.
https://twrp.me
Warning!
I've never bothered with any Android 8 Oreo roms on my G3 2015 Osprey. I went straight to Android 9(PIE).
https://chil360.github.io
I've tried most and now I'm only interested in the Lineage versions and the Havoc versions of Android 10 as these keep the Hardware FM radio that I like to use.
Havoc version,
Havoc-OS-v3.3-20200306-osprey-Unofficial.zip
Working fine and
Lineage,
ineage-17.1-20200308-UNOFFICIAL-osprey.zip
Working fine.
Note: If I recall correctly Chil360 Havoc Android 10 Rom does not need Gapps installing. If Lineage does I use Arm_10_Pico,
Note:
When setting up the phone I never let the phone install backups automatically I have my apps backed up on my SD card and re-install them from there. Google photos will not not clone-Install and a few others so I just re-download those.
Contacts:
Although Google backs up contacts lists to be safe I keep an,"Old School" backup using the Contact's apps Import/Export option and save them to a .vcf file. This will look like contacts.vcf or 000001.vcf on the phone wherever you have chosen to save it. This can be imported into any contacts app,Even on APPLE phones!
I send a copy of this .vcf file to myself attached to an Email. This means I can download my contacts to any phone anywhere in the World if I ever need to.
Note:
I never encrypt my phones so cannot answer any questions on this subject.
If you want to,"Root" the phone then install the .zip version of Magisk from your phone's Internal Memory and keep it on your phone's Internal memory. You install the .zip using TWRP's install option and always take it's advice on clearing Dalvik Cache and Cache.
Then once the phone is booted update both it and it's manager via an Internet connection.
Note: Some,"Pay/Money" apps will detect that you are running a non-stock rom. You can hide these apps using,"Magisk Hide" and in some cases you need to Hide the app AND then use Magisk option to rename itself. You can call it anything you like but keep it simple like Osprey.
HTH
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Chil360 has updated the April 2020 Havoc 3.4 and it now installs on the Above phone. I am testing it as I post.
Havoc-OS-v3.4-20200417-osprey-Unofficial.zip. Does not require Gapps installing.
BTW I do like the AOSP_Pizza Android 9 rom for Chil360 as well(Still has FM RAdio).
https://www.androidfilehost.com/?fid=4349826312261742008
I go back to it sometimes as it has some features others don't have like showing local temp on the Lockscreen and also allows me to install a Custom boot animation logo. I like the old,"Stitch" Moto Logo
The Android 10 roms won't let me change the animated loading logos(They will let me change the static boot logo) or I need to find versions that will work with Android 10
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Just thought I'd update.
Started to install Chil's latest Paranoid Android and it installed fine but stopped as I realized it doesn't have as many tweaks as Havoc 3.4.
Things I like about Havoc 3 series.
I can have,
Date and time in the notification bar.
Battery percentage next to Battery icon and time left when Notification bar is swiped down.
Easy to swap software buttons(I'm right handed so like my Back button on the right).
It still lets me use my old version of Holo Launcher.
You can assign functions to the Software buttons like Long press to Lockscreen. Can't seem to get Long press to enable the Flashlight tho
Advanced Restart on Power button.
Loads more tweaks to explore.
One thing I would like but I'm not sure if the Motos are capable but I have a cheap China phone that lets me double tap the screen to wake it up and I don't mean just at the Top of the phone I mean anywhere on the screen.
I can't see myself using any other version except as stated AOSP Pizza for a bit of a change now and then
PS
Continued thanks to CHIL his work is much appreciated keeping these Classic little phones going
Latest Chil360 roms are out. I'm running Havoc(May Security updated) but FM radio not working
Has anybody else had issues with the FM radio not working after upgrading to v3.5-20200508 version of Havoc Android 10 for Moto G3 2015? I found after upgrading to this version, the FM radio would no longer work, it would just freeze. Downgrading to v3.4-20200417, it would work perfectly again. Upgrading again to v3.5-20200508, it no longer would work. Has anything been changed that would cause this? Other than this issue, I believe that the ROM is excellent.
Gord
Glad you found this. Checking the FM radio is usually one of the first things I do but didn't this time
Yes you are right it's not working for me as well in Havoc 3.5.
Gone back to 3.4 with no problems :good:
Gordster
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Gordster said:
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Click to expand...
Click to collapse
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
R1ffR4ff said:
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
Click to expand...
Click to collapse
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
stukdev said:
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
Click to expand...
Click to collapse
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
R1ffR4ff said:
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
Click to expand...
Click to collapse
Maybe its an hardware fault, but with the Moto App i haven't any problem
stukdev said:
Maybe its an hardware fault, but with the Moto App i haven't any problem
Click to expand...
Click to collapse
See previous reply and also I don't know if you know the,"Soft Reset" trick on Moto phones that can clear some problems.
Press and hold the Power button in for around 10/15 seconds until the phone restarts. This emulates taking the Battery out and can clear clogged RAM of old data that can prevent correct operation
I've been running the latest May AOSP PIZZA
AOSiP-9.0-Pizza-osprey-20200517.zip
Since yesterday and all seems fine so far. Only thing missing is the local Temp on the lock screen unless I'm missing a setting. This was the same with the last version
Not a deal breaker
Installed Chil360's latest AOSP_QUICHE Android 10 June updates(Clean install).
AOSiP-10-Quiche-osprey-20200605.zip
All working well including FM Radio. Updated TWRP using the APP to 3.3.1 as the TWRP clock and date went funky but may not be related.
Phone is still rooted with Magisk and Root removed before installing clean and then re-rooted and Magisk updated.
Nice editing option to move Software buttons around in the AOSP roms. When texting I have a habit of hitting the Home button making my SMS app disappear. I've moved my Home button a little off-centre more to the right(I'm right handed) and this has cured that
Update. The Rom is working well but it's doesn't feel as slick as the AOSP_PIZZA version(May version) so I've gone back to that for now just out of personal preference.
So presently my faves are Havoc 3.4 and Havoc 3.6(Android 10) 2020 and AOSP_PIZZA Android 9 May 2020 version(Moto Stitch Boot animation).
Again my ongoing thanks for CHIL360's work in keeping these great little phones updated
Latest Android 10 Havoc 3.6 released by Chil360 with June 2020 updates,
https://chil360.github.io/ten.html
Gapps included.
Installed and all working e.g Text/Calls/GPS/FM Radio/ WiFi/WiFi Hotspot/Camera/Bluetooth etc.
Very fast booting and really slick
One possible glitch is the Stock Camera has the option to Save to SD but it doesn't seem to work. As I rarely use the Stock Camera preferring the much better,"Open Camera" from the Playstore this is not an issue for me
PS
Because of the dedication of the Android Developers on here we have an old 2015 Phone/s with more up-to-date software than many brand new phones
Chil360 has released a first and new Rom to his collection. Android 10 PixelExperience Plus 10.0,
https://chil360.github.io
If you like Google I think you will like this
I wonder if he might be looking to work on the new Android 11 if it can be used on the Moto G3
Then install Gapps if required.
Then do another Factory reset for good measure.
If ever there's a problem when first setting up after the first boot-up has loaded just press and hold the Power Button in for around 10/15 seconds and the phone will reboot(Soft Reset) which emulates taking the Battery out. [/B]
Chil360 has released a new Rom,
potato_osprey-10-20200619-croquette.v3.2.0+15.Community.zip
Unfortunately I cannot test it as it boot-loops.
Tried all my tricks but no good
Gone back to Havoc 3.6
Latest POSP Croquette v3.2.0-hotfix+16 loads but no FM radio so no good to me
Back to Havoc 3.6(Android 10)/ AOSP_PIZZA Android 9 May version
July 2020 Havoc 3.7 released by Chil360.
Installed clean and running well
The Havoc 3.7 July 2020 release by Chil360 IMO is the best and most stable custom rom I've tested for Moto g3 2015 (osprey) and is highly customizable. I especially like the "smart battery charger" feature which allows the charger to be set at a maximum percentage in my case 92%. I have not found any other custom rom with this feature. This will help prolong the battery life by not charging it to 100% every time. The July 2020 release installed fine and is running with no apparent problems. I tried the latest "official" lineageos version July 3 2020 but had problems with random spontaneous reboots.