Develop Bugs

[G800F/M/Y][ROM][7.1][NDE63P] CyanogenMod 14.1 for G800F/M/Y [Test 07/11/2016][eol]

CyanogenMod is discontinued.
This ROM is continued as a LineageOS ROM.
Check the G800F LineageOS ROM for more info.
This is a CyanogenMod 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Working features
HW accelerated GUI
Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Sound
SMS
Initiate and receive calls (the first ingoing call seems to have no sound)
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Fingerprint scanner
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
CM 14.1 ROM for G800F/M/Y (Android File Host)
Google Apps (contains Google Play, ...) for Android 7.1. The following is recommended:
Open GApps Project, Platform:ARM, Android:7.1, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM ROM zip-package
Install the GApps zip-package
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
07/11/2016:
* Initial test build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz, Psyafter, spookcity138 and ayke for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][7.1][NDE63P] CyanogenMod 14.1 for G800F/M/Y [Test 07/11/2016][eol], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, CTXz, spookcity138, psyafter, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-07
Last Updated 2017-02-01

Reserved
This is just a test build. CM 14.1 is not released yet and still instable. There are lots of known issues.
Here a short list of known problems:
First incoming call has no sound
Camera app crashes when you try to switch between camera and video recording mode (in this case: restart the app and recording will work)
Messages with "Browser crashed" will occur from time to time
The default browser does not always display all the text that was typed into a text field.

This was an awesome ROM but now I propose LineageOS 14.1

It works perfect (at least until now) for me ? great job
I hope @ayke brings OTA updates here to make everything easier
Enviado desde mi SM-G800F mediante Tapatalk

This rom is really great! Smooth and without big issues. Everything works as you said and here are some screenshots of Antutu if someone need them. Thanks devs!

What's the problem with first income call? The first one is the only one with no sound?

Great job Henny

@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate

CostasGr said:
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
Click to expand...
Click to collapse
what about battery drain?

sgilyin said:
what about battery drain?
Click to expand...
Click to collapse
seems normal so far

is this normal?
CostasGr said:
seems normal so far
Click to expand...
Click to collapse

With my usage yes.
The only problem is robotic voice

Hey !
Thanks for your amazing job (all of you), I don't have any browser crashes since I use chrome and I remove the stock browser, I also don't have any crash with my camera. I use Google Camera for that. Here is a list of bugs I've noticed:
- Chrome (stable) has crashed the first time I've opened it (only one time, that's why I did say that I don't have any browser crashes)
- Sometimes, something like "MTP Host" crashes..
- In Allo, while sending a message, there's a little sound, that's not a bug since it's in the app... But that sound is garbled (I don't know if that word is correct, I've used Google Translate for it)
I guess that's all..
Also, I don't have robotic voice... Good bye ! And thanks again
EDIT: About the "MTP Host" app.. it's the download app :/

Bugs
Hi there, thanks for your work on the rom really enjoying it and love Android 7.
Throughout my use I have discovered a bug with YouTube (not sure if it's the app or rom, but reporting anyway as did not happen on Mm) where changing into 720p causes the app to zoom into the upper left corner of the video. It can be remedied buy only using 360p but is rather annoying.
Again thanks for the work on the rom and all the best in the future. ?

Anyone have the link for xposed framework of this version?

Thomzey said:
Hi there, thanks for your work on the rom really enjoying it and love Android 7.
Throughout my use I have discovered a bug with YouTube (not sure if it's the app or rom, but reporting anyway as did not happen on Mm) where changing into 720p causes the app to zoom into the upper left corner of the video. It can be remedied buy only using 360p but is rather annoying.
Again thanks for the work on the rom and all the best in the future. ?
Click to expand...
Click to collapse
I also experienced that with some internet players when watching HD content..
Enviado desde mi SM-G800F mediante Tapatalk

CostasGr said:
@hennymcc
Robotic voice again ��
Everything else works fine
===========================
Guys I've been testing the Rom for a few hours, and it's preety awesome.
The only bad thing is the robotic voice. @spookcity138
As i remember you fixed this last time
Do your stuff mate
Click to expand...
Click to collapse
Well,as of now my sim card is not detected on CM14 for some strange reason. I seem to be alone in that. The robotic voice,if I remember correctly is linked to using the LP libs. Maybe someday we'll see official MM for the g800f. [emoji3]
Sent from my SM-G800F using Tapatalk

spookcity138 said:
Well,as of now my sim card is not detected on CM14 for some strange reason. I seem to be alone in that. The robotic voice,if I remember correctly is linked to using the LP libs. Maybe someday we'll see official MM for the g800f. [emoji3]
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
You had changed the device tree as I remember and you fixed it last time ( I might be wrong I have no idea about developing) anyhow any help would be awesome because I need my phone for my work so I cant have that robotic voice... Thank you

Great job guys :good:
What are the chances like to get a first update soon? Or better said, moving to beta status?
I think the user respondings are quit positiv so far.
Greetings
Sunn76

Sunn76 said:
Great job guys :good:
What are the chances like to get a first update soon? Or better said, moving to beta status?
I think the user respondings are quit positiv so far.
Greetings
Sunn76
Click to expand...
Click to collapse
Most oft the current issues are Cm related so the CM-Team needs to update their sources time by time
Sent from my SM-G800F using XDA-Developers mobile app

[ROMs] Nougat ROMs for Redmi Pro

Hello everybody!
This thread will be dedicated to Android N developement. Since now the ROMs are not ported (we have a device tree to compile from source) we can get any Android N ROM working but with the same bugs.
From now on i will be working on fixing the bugs of the device tree/vendor tree and any help with it would be apreciated.
I will share my device tree so that people can help with it:
Device tree: https://github.com/end222/lineage_device_omega
Vendor tree:https://github.com/end222/lineage_vendor_omega
Want to help?
In the device tree in github I have opened some issues where I try to put as much relevant information as I can about the state of each bug and the errors I am getting. Please give it a look to see if someone can help
Bugs:
Working:
It boots up
Speaker sometimes
Network
Wifi
Bluetooth
FM Radio
Chargin while being off
Flashlight
Rear camera without focus
Mobile data
Sound
Not working:
Calls
Camera focus and front camera
Headphones
IR
Fingerprint sensor
It shows corrupted SD at boot but SD works good
Download links:
LineageOS: https://www.androidfilehost.com/?fid=817550096634793903
Old ones (To be updated):
AICP: https://www.androidfilehost.com/?fid=745425885120743786
Resurrection Remix: https://www.androidfilehost.com/?fid=817550096634781602
Dirty Unicorns: https://www.androidfilehost.com/?fid=817550096634782672
If you want to give a try to another AOSP like ROM just tell me and I can make a build
If you try the ROM and find any bug please tell me and I will add it to the bugs section in order to work on it and also to give other a clearer information about the ROM.
Do you like my work?
Offer me a beer here:
https://www.paypal.me/OrdunaLagarma

You forgot to add fingerprint sensor.

kristi6.9 said:
You forgot to add fingerprint sensor.
Click to expand...
Click to collapse
That's right

I recommend you to atach the sources below the rom and use devdb not just a regular thread

kristi6.9 said:
I recommend you to atach the sources below the rom and use devdb not just a regular thread
Click to expand...
Click to collapse
In the end I didn't use the device tree I had done. CM sources were giving me warnings about framework, something related to non-existent images for the resolution of the Redmi Pro (CM had already closed when I downloaded them).
Then I took the ROM compiled by andrianom for the RN4 and resized the system dat by hand. Then I modifyed the kernel to get it working on the RM Pro.
So in the end this is a port from the RN4, it is not compiled from source. However I will try to compile Lineage from source as it is almost the same and the device tree I had made should work with some modifications

OK
end222 said:
In the end I didn't use the device tree I had done. CM sources were giving me warnings about framework, something related to non-existent images for the resolution of the Redmi Pro (CM had already closed when I downloaded them).
Then I took the ROM compiled by andrianom for the RN4 and resized the system dat by hand. Then I modifyed the kernel to get it working on the RM Pro.
So in the end this is a port from the RN4, it is not compiled from source. However I will try to compile Lineage from source as it is almost the same and the device tree I had made should work with some modifications
Click to expand...
Click to collapse

If someone could fix fingerprint sensor and headphones, I'm sold

misterright1 said:
If someone could fix fingerprint sensor and headphones, I'm sold
Click to expand...
Click to collapse
I know there are many bugs but at least headphones are working

end222 said:
I know there are many bugs but at least headphones are working
Click to expand...
Click to collapse
HHahahah thats an advantage according to other roms.?????

when can you make this rom stable bro?not eta just asking

pou_gh2 said:
when can you make this rom stable bro?not eta just asking
Click to expand...
Click to collapse
I won't answer that question [emoji14]
I am still really new in the world of developing ROMs as Redmi Pro is the first device that I have used for developing. Then if I knew how to solve all the bugs maybe I could tell you more or less how long it could take.
However, the only thing I know is that I have to modify the vendor tree by mixing it with the vendor tree of other devices. So I cannot tell how long it can take and if I will be able to do it

pou_gh2 said:
when can you make this rom stable bro?not eta just asking
Click to expand...
Click to collapse
don't be a prick dude

Recommended resources
Hi end222 , I just got this phone. Love the specs / screen / performance. The only thing i hate is the OS. I had been using Nougat on a flashed Samsung S4. Just cant bear the older version of Android now, especially the notifications.
I am not new to the world of development but haven't developed ROMs before. Are there any recommended resources you have where I can learn the basics and add on to the work you have done so far. I would love to to be able to create version which can be used daily.

turbochild said:
Hi end222 , I just got this phone. Love the specs / screen / performance. The only thing i hate is the OS. I had been using Nougat on a flashed Samsung S4. Just cant bear the older version of Android now, especially the notifications.
I am not new to the world of development but haven't developed ROMs before. Are there any recommended resources you have where I can learn the basics and add on to the work you have done so far. I would love to to be able to create version which can be used daily.
Click to expand...
Click to collapse
I would really love to see more people working for this phone.
What I recommend you is to read some of the MTK porting guides that can be found on the internet, for example, on xda.
The most important thing you have to learn from those guides is how to port the boot.img.
Do not try to port the whooe ROM using those methods because I tried and they result in most of cases in bootloop. So to port to Redmi Pro you have to:
- From RN4 just by porting the boot.img (and resizing the system image in Nougat) is enough to get it booting.
- From Apollo Lite you will have to copy also hwcomposer from the stock ROM, located in lib/hw and lib64/hw. Also do not forget to port also the boot.img
If you find any problem or have any doubt do not hesitate to send me a message and I will do my best to help
Enviado desde mi Redmi Pro mediante Tapatalk

Thanks end222 for your work keep it up man
Sent from my Redmi Pro using Tapatalk

Lately, I have been always checking all the threads created expecting for any stable update to flash redmi pro but it seems everyone gave up from porting... Is there anyway to port an existing nougat ROM from other xiaomi model and getting stable ? At least the phone and the headset part... I am tired of MIUI ROM specially the weekly version...
Besides that I would to thank to all the people that had helped with this project without them I probably had sold my redmi pro already >.>

rijrg4 said:
Lately, I have been always checking all the threads created expecting for any stable update to flash redmi pro but it seems everyone gave up from porting... Is there anyway to port an existing nougat ROM from other xiaomi model and getting stable ? At least the phone and the headset part... I am tired of MIUI ROM specially the weekly version...
Besides that I would to thank to all the people that had helped with this project without them I probably had sold my redmi pro already >.>
Click to expand...
Click to collapse
The closest phone to the RM Pro is the Redmi Note 4 and this is the best I have been able to do by porting from that device. The main problem is that the phone isn't working in the RN4 either.
Whenever I have more free time I will keep trying things. It should be possible to get at least a good working non MIUI ROM based on Android 6. However it would be much harder to get Android 7 stable

I want to try this ROM, can i downgrade to 6.0 based miui rom safely after I try this ROM? ini

doripto. said:
I want to try this ROM, can i downgrade to 6.0 based miui rom safely after I try this ROM? ini
Click to expand...
Click to collapse
Yes, you should be able to flash MIUI with TWRP after using this ROM. I would also recommend you to do a backup of MIUI before flashing it and then you can come back to MIUI without losing any apps

I tried this rom last night and its great to experience CM again, btw when im insert my sd card it says that my sd card is corrupted but its not corrupted and working fine when I tried it with my sisters MiMax...

Upgrade from AEX 4.6 to RR 6.0 (kinda lost) ?

Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,

Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP

sixth.pr1m3 said:
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
Click to expand...
Click to collapse
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
EDIT: Alright, I installed "Arnova's Pixel2Mod v6" and I now have a working camera. Do not mind my question. I also noticed that you posted the link (on another thread) where I found the Camera mod, so thanks again for your help!

Sinero said:
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
Click to expand...
Click to collapse
Using GCam? HDR option should be working, try the recommended one's from here: https://www.celsoazevedo.com/files/android/google-camera/
Slow motion is not working. If you have dark video issue, use OnePlus 5T Cam.

Thanks again for that link, seems like I edited my last post while you answered !
Here is a little feedback after ten days of usage :
My camera started acting up : usually when going through the camera's gallery the application will crash. I will try another Gcam.
I also noticed that my calls are not working. I can dial someone but when they pick up the call we cannot hear each-other. Does anyone have experienced this kind of situation ?
Everything else is working smoothly, better than under AEX 4.6, sadly with those two main problems I may have to try something else.

Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
For offline charging flash at beast kernal

[REQUEST][ROM][A520f/A720f][OFFICIAL] Resurrection Remix 6.0

please release [ROM][A720f/A520f] [OFFICIAL] Resurrection Remix 6.0
Everyone like this please say!

I'm trying to build one for a5, but may be unsuccessful.
Wish me luck!

Plz post new RR 6 thread for A520F.....now running 5.8.5

@matkali https://www.androidfilehost.com/?fid=1322778262904014011
Here you go.

Thanks
sheepkill15 said:
@matkali https://www.androidfilehost.com/?fid=1322778262904014011
Here you go.
Click to expand...
Click to collapse
thanks for it
if you can port this for a720f

@sheepkill15 I have a question mate. Is there anything specific regarding the installaton process of your ROM? I installed your RR-O-v6.1.0-20180907 and 8.1 GApps mini but I've been sitting on a bootanimation for over 20 minutes now. Thanks for your effort and sharing the ROM with us.

SoloMid Hazard said:
@sheepkill15 I have a question mate. Is there anything specific regarding the installaton process of your ROM? I installed your RR-O-v6.1.0-20180907 and 8.1 GApps mini but I've been sitting on a bootanimation for over 20 minutes now. Thanks for your effort and sharing the ROM with us.
Click to expand...
Click to collapse
There's nothing special to be done, but yes, sometimes it's stuck in bootloop. What I usually do is:
Hard reset, wipe everything except microsd, delete the zip from sd card, copy it again and install again.
Idk why it needs sometimes to be flashed again, but that way it will boot for sure. A normal first boot with this rom should be around 7 minutes

sheepkill15 said:
There's nothing special to be done, but yes, sometimes it's stuck in bootloop. What I usually do is:
Hard reset, wipe everything except microsd, delete the zip from sd card, copy it again and install again.
Idk why it needs sometimes to be flashed again, but that way it will boot for sure. A normal first boot with this rom should be around 7 minutes
Click to expand...
Click to collapse
I got it to work, and it is great. I just have one more question. Do you have any recommendations on which gcam version to use? Thank you once again.

SoloMid Hazard said:
I got it to work, and it is great. I just have one more question. Do you have any recommendations on which gcam version to use? Thank you once again.
Click to expand...
Click to collapse
I don't know which version is good, I don't use it

watched reddish purple balls for about 20 minutes... did the 2nd round and after maybe 90 seconds I am checking it out. Thanks!

+1 ThX

while flashing on SM-A520S 90% flashing bar showing then this error come
Eror 1001 cant mount system
sorry for bad english
try many times also format every thing but still got this error

question
is there any bugs in this rom ? is it stable and support the Dual sim configuration means both sim card can be detected ? cuz am using HadesRom v4.5 it's cool! but i get fed up from the TOUCHWIZ and i want the original google roms give my A5 2017 the full power of CPU and GPU ! more faster and more powerful but with the original looks heavy sometimes after maybe a month of using !
thnx if you reply bro

Chiha ALi said:
is there any bugs in this rom ? is it stable and support the Dual sim configuration means both sim card can be detected ? cuz am using HadesRom v4.5 it's cool! but i get fed up from the TOUCHWIZ and i want the original google roms give my A5 2017 the full power of CPU and GPU ! more faster and more powerful but with the original looks heavy sometimes after maybe a month of using !
thnx if you reply bro
Click to expand...
Click to collapse
In the current build, the biggest problem is that the buttons dont light up, but I fixed that in the meantime, just haven't uploaded it yet. The other noticeable issue is that the battery life is not perfect. I'm working on it too. The radio isn't working yet, but you don't use it, there's nothing more.
I don't know about dual sim, since I have the normal one.

Does anybody else face a problem of a laggy front camera using apps like snapchat/messenger/instagram?

Thank you very much for this rom bro
problems are :
The Rom :
- Didn't detect my saved contacts on both sim cards.
- Didn't have the same quality of image but it's not bad.
- The calculator app still more than 1 min to open ( something weird)!
- Battery usage looks perfect !
- The configurations in settings gives a lot of helpful things such as the customization of the notification panel and the power menu !
.
so what i did now is that i rooted with magisk and i installed ( Root explorer R ) pro version and installed ( System apps uninstall ).
i deleted ( Calculator,Camera,browser,messaging,music player,gallery.....etc) then i installed an Alternative for them. so now i have my customized RR V6.2.0
it's awesome with root. But for who installed this rom you can go to settings and find the display PPI ( you will find it about 400ppi ) i changed it up to 424ppi( the original A5 2017 ppi ) and now works perfectly .

Feedback RR-O-v6.2.0-20180925-a5y17lte-Unofficial
sheepkill15 said:
I don't know which version is good, I don't use it
Click to expand...
Click to collapse
Friend I've been with your rom for a few days and it's the BEST ROM OF EVERYTHING! I say this in a matter of customization and having a purest experience that samsung ...
I have an A520F (two-chip model) and both are OK.
The problem is that it has some really annoying bugs as a problem to play media (especially songs that get squeaked and at first I was worried if my headphones had damaged), also has bugs in the camera that seem to limit their quality a lot, bugs in the interface in general that make the device reboot out of nowhere (it happened to me 1 or 2 times during the time I am with the rom on the device [4 days]), bugs on the physical buttons as previously said, among others ... These were the most important bugs I had with rom.
I have some suggestions for interesting implementations to make in the rom like stereo audio (it has this function in Hades), just leave the pixel launcher more notifications optimization on the always on display and one good thing I believe developers should do is provide a form of install a separate galaxy s9 camera package that is present in rom Hades for all roms.
You are doing a good job and good luck for more projects in the future. I'll probably record a YouTube video about your future rom and give you the credits.

[ROM][GSI] Official Android Q

BETA Version
Ready to try?
I start....
https://developer.android.com/preview/gsi-release-notes

Is very difficult to make it stable....
Wifi connection and screen lock password issue,
second reboot impossible....
But nice to see this evolution.
Stay tuned, work on it....

Booted googles Android Q gsi. Everything works fine, mobile data, calls, Bluetooth etc. Only secured WiFi is messed up can't connect. Reboot bootloop issue is fixed by deleting vendor/app/
Steps I did was,
-have a fresh install of miui 10.3 (from xiaomi.eu) on to system
-flash Q gsi to system partition on twrp
-after gsi flash, reboot twrp then mount vendor and through twrps file manager locate vendor/app and delete it.
-reboot
And done bootloop after restart issue should be home.
Things I found are sounds are very static and distorted I got it fixed my flashing viper4android and you'll need root for that. Use magisk 19. Also I'm using global version. I'm sure chinese version will be fine but again I'm not sure

romen288 said:
Booted googles Android Q gsi. Everything works fine, mobile data, calls, Bluetooth etc. Only secured WiFi is messed up can't connect. Reboot bootloop issue is fixed by deleting vendor/app/
Steps I did was,
-have a fresh install of miui 10.3 (from xiaomi.eu) on to system
-flash Q gsi to system partition on twrp
-after gsi flash, reboot twrp then mount vendor and through twrps file manager locate vendor/app and delete it.
-reboot
And done bootloop after restart issue should be home.
Things I found are sounds are very static and distorted I got it fixed my flashing viper4android and you'll need root for that. Use magisk 19. Also I'm using global version. I'm sure chinese version will be fine but again I'm not sure
Click to expand...
Click to collapse
You sticking with it?

i found a big issue : wifi doesnt work for me.....

rafik25 said:
i found a big issue : wifi doesnt work for me.....
Click to expand...
Click to collapse
Flash the andro kernel

Mackay53 said:
Flash the andro kernel
Click to expand...
Click to collapse
Sorry i tried several times but no changes with andro kernel

Looks like incall voice is buggy too. I can't hear the person on the other end. And system notification sounds are still distorted like staticky.

Hope Q beta 3 will be available for Mix 3 )
Great. Only for mi9 and Mi Mix 3 5 f***** G

wyciunia said:
Hope Q beta 3 will be available for Mix 3 )
Great. Only for mi9 and Mi Mix 3 5 f***** G
Click to expand...
Click to collapse
Lets hope someone ports it over to the normal Mix 3 variant.

sandyrokr said:
Lets hope someone ports it over to the normal Mix 3 variant.
Click to expand...
Click to collapse
No need to port as it will be a GSI

Mackay53 said:
No need to port as it will be a GSI
Click to expand...
Click to collapse
Yeah I forgot about that but as this device is not specifically supported for a beta, it might have issues like previous GSI betas.

Mackay53 said:
No need to port as it will be a GSI
Click to expand...
Click to collapse
The official support would be nice. I understand the mi9, but i don't see the point i mix 3 5g. the user base is too low. It went on sale only week ago. 5g is still few years ahead from global adoption. Mix 3 4g would be better choice for beta testing.

wyciunia said:
The official support would be nice. I understand the mi9, but i don't see the point i mix 3 5g. the user base is too low. It went on sale only week ago. 5g is still few years ahead from global adoption. Mix 3 4g would be better choice for beta testing.
Click to expand...
Click to collapse
but still, going for 5g model helps xiaomi show their muscles...

Any one tried beta 3 ?
Tried......but bootloop

rafik25 said:
Any one tried beta 3 ?
Tried......but bootloop
Click to expand...
Click to collapse
Same here, tried to get it to work but constantly bootlooped

Anyone tried the latest beta?

But...by the end of the year Android Q will be officially avaible as OTA update for mi mix 3 and other Xiaomi phones as confirmed by them. So why messing things up with unifficial GSI "just to try" a new release? I'm not blaming anyone who wants to, but it is really necessary? It's so terrible to stay on MIUI rather than stock or so bad to stay on Pie (both stock or custom) rather than on a newer OS version?
Personally i prefer a stable software (or an almost bug free one at least) than an unstable one with possibly many non working/partially working features. What do you think?
P.s before the bull**** storm by someone:
1) Yes, i used custom roms before on other devices, i liked them and they always made my devices better in terms of performances and upgraded them to the latest OS avabile when the official support ended. (Galaxy SII Plus, Galaxy Tab S2, Honor 8)
2) You can do whatever you want with your device, i really couldn't care less, but wer're on a forum, i'm just taking a conversation to hear other opinions about GSI (or other custom roms) for this devices wich i found to be very fast, complete and battery friendly even without them.
3) Thank you

I couldn't care less