[SHARED][ROM][UNOFFICIAL][Android 11] LineageOS 18.0 [joyeuse/miatol][28/10/20]

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
WIFI doesn't connect anymore with 11/29 build, anyone else?

I am suddenly having Wi-Fi problems too. 11-30-2020 build.

I installed it while working at one location. Yesterday, after two months of out-of-town work, I came back home and I can not get Wi-Fi to work with it here.

SSIDs show up as expected, but I can not connect. Other wireless devices have no issues connecting to the same SSIDs.

While these ROMs from Wight seem great, it is disappointing the developer does not answer any posts made to the discussion thread of the relevant Sourceforge account used for distributing them. Wight also does not seem active here (unless, possibly, posting under a different name).
 

M47Z

Senior Member
Dec 12, 2011
186
65
48
While these ROMs from Wight seem great, it is disappointing the developer does not answer any posts made to the discussion thread of the relevant Sourceforge account used for distributing them.
What you wrote about on sourceforce so far:

You can't add a google account without google apps.
OTG does not work a day after the version where this is fixed was released.
You can't use a gapps removal script to remove the lineage camera.
You fail flashing a random zip you found in the files.

... and now you complain about it here?
 
  • Like
Reactions: zanitos1991

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
Hey @M47Z

What you wrote about on sourceforce so far:

You can't add a google account without google apps.
OTG does not work a day after the version where this is fixed was released.
You can't use a gapps removal script to remove the lineage camera.
You fail flashing a random zip you found in the files.
If you took time to read through my posts completely you would see that the majority of these issues were distinctly reported to have been cleared up (either by my own actions or release of newer WightROMs) in my subsequent posts.

Sourceforge does not seem to allow editing of the topic subject (i.e. "SOLVED") but I did include updates in my posts where appropriate for both the developers (and end-users') knowledge.

The only reason the gapps removal script no longer removes all desired apps any more is that two apps have (only in recent versions of the ROM) been moved into subfolders at /system_ext/priv-app instead of /system/priv-apps/

.gapps-config clearly points out it won't work in such a fashion.

You have a problem with me pointing any of this out to the developer?!


... and now you complain about it here?
"Complaint"? Seriously?!

I am reporting unexpected or (suddenly) changed or lack-of functionality. If I were able to develop a ROM like this I would love the detailed reports I have given. Without good feedback, software does not progress in a way which helps users and developers can end up flailing about.


Further comment: Wight has provided an incredible service to users of the Xiaomi Redmi Note 9 line. I wish I had the ability to help code this stuff, but failing that, at least I can provide constructive input based on my tested and experienced usage. In this way, hopefully Wight does not have to test every single use case him/her-self.

These WightROMs seem better (and more streamlined!) than the other alternatives for this device, so I would like to help in any way I possibly can!
 
Last edited:

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
Hi @zanitos1991

@fbachofner try unmetered connection or maybe update your firmware, I don't have any problem using joyeuse

Thanks for your ideas!

1. I had already tried using an "unmetered connection." Unfortunately that didn't work. Sorry I didn't mention it.

2. re: firmware -- I assume this would be done with the installation of the most recent stock ROM, right?

Before flashing WightROM's 2020-11-30 version I flashed the V12.0.1.0.QJZEUXM version available here: https://xiaomirom.com/en/rom/redmi-...download-redmi-note-9-pro-stable-fastboot-rom

This seems to be the most recent version available from Xiaomi.


Also, on a (probably) related note, the developer has made available "lineage_miatoll-img-eng.wight554.zip." This seems to have firmware in it, but flashing the zip file with PBRP does not work.

I wonder whether one should extract the included .img files and flash separately, but the developer has not yet responded to my query on Sourceforge.

"Miatoll" is ostensibly the "unified source" for "for all of Xiaomi's Sanapdragon 720G Devices" so I infer I am working with the correct files.
 

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
Hi @heyadmwutanime

On Recovery backup your Data, System and Boot. Then flash latest MIUI and recover your backup. I am not sure if a simple firmware update zip will help on miatol. You can also try though.
Thanks for your ideas!

Before flashing with the 2020-11-30 version of the WightROMs custom rom I had installed the latest EEA version of Xiaomi's ROM: V12.0.1.0.QJZEUXM

Would this be analogous to your suggestion?

Or does the installation of a ROM (an "original" installation as I did -- rather than pulling from a backup) potentially trample on the Xiaomi-provided firmware?
 

heyadmwutanime

Senior Member
May 22, 2020
121
15
18
Before flashing with the 2020-11-30 version of the WightROMs custom rom I had installed the latest EEA version of Xiaomi's ROM: V12.0.1.0.QJZEUXM

Would this be analogous to your suggestion?
I did a clean MIUI V12.0.1.0.QJZMIXM install, then flashed PBRP as recovery, formated data, wiped dalvik/cache, installed Wight's 2020-11-30 version and wifi works fine. I don't know why you got problems. I didn't install any GApps. Maybe you tried to adb uninstall some factory apps of LineageOS?
 

lucasymax

Member
Apr 16, 2019
14
3
3
veracruz
Thanks. Do we also need to flash disable verity zip from https://zackptg5.com/android.php#disverfe ?

@gigahurts
Please rework your manuals. Especially the 2 seperate disable verity instructions and the A-Z instructions are confusing as hell.
I DO NOT UNDERSTAND THE INSTRUCTIONS TO INSTALL LINEAGE FOR THE FIRST TIME (I HAVE PIXEL EXPERIENCE ROM INSTALLED)

I CAN DO FORMAT DATA (IT DOESN'T MATTER LOSING DATA)
OR
I HAVE TO DO WIPE NECESSARILY SO THAT I DO NOT HAVE PROBLEMS WITH THE INSTALLATION

THANKS FOR THE REPLY
 

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
Hi @heyadmwutanime

I did a clean MIUI V12.0.1.0.QJZMIXM install, then flashed PBRP as recovery, formated data, wiped dalvik/cache, installed Wight's 2020-11-30 version and wifi works fine.


So we took the same basic approach. I did not wipe dalvik/cache, which was strongly discouraged in the opening post here.

[ SOLVED? ]

I am happy to report: yesterday I took the phone (which I am not quite using as a "daily driver" because of this unknown) to two different clients and I was able to connect to their Wi-Fi networks without any problem.


I don't know why you got problems.


It looks like our home Wi-Fi suffered a partial failure during my 2-month trip. Old (previously connected) devices can still function with it, but anything new which attempts to connect can not (I just validated this with a different new device this morning).

It is very strange. Presuming one uses the correct credentials, there is nothing in my network setup which would preclude a device from connecting to either my private or guest Wi-Fi networks at the moment. Must be some sort of failure in the router's Wi-Fi chip.

I'll spin up a new access point tomorrow night or next weekend when I get a chance.

Thanks to all of you who gave helpful suggestions!
 

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
Hi @lucasymax

I DO NOT UNDERSTAND THE INSTRUCTIONS TO INSTALL LINEAGE FOR THE FIRST TIME (I HAVE PIXEL EXPERIENCE ROM INSTALLED)
Here's how I did it:
  1. Before flashing WightROM's 2020-11-30 version I flashed the V12.0.1.0.QJZEUXM STOCK version available here: https://xiaomirom.com/en/rom/redmi-...download-redmi-note-9-pro-stable-fastboot-rom
    make certain you do not re-lock the phone's bootloader

  2. Perform absolute minimal configuration and re-enable developer options, including USB debugging
    Step 3 will not likely work without this!

  3. Boot to Fastboot mode (Power + Volume DOWN). Install PBRP (Pitch Black Recovery Project) using Android SDK Platform Tools.
    PBRP for this device is linked in the first post of this thread.

  4. Reboot into Recovery mode (Power + Volume UP). Format data (i.e. with PBRP)

  5. Using PBRP, flash the newest WightROM for this device from a SD-Card or USB OTG.
    The ROM is available at: https://sourceforge.net/projects/wightroms/files/joyeuse/lineage/
    As of this morning, Wight's most current ROM is still " lineage-18.0-20201130-UNOFFICIAL-miatoll.zip "
    This ROM works very well. [ I had a Wi-Fi "scare" a couple days ago, but it turns out one of my access points had failed. ]

  6. If desired, gain root with Magisk
    Magisk is also linked in the first post of this thread

  7. If desired, flash OpenGAPPS or similar.
    [ This is required if you want to install any apps from the Play Store. ]
    This is also very useful to "debloat" LineageOS (using a .gapps-config configuration file).
    [ I personally dislike including any userland apps (other than settings) on an initial device setup as I have a full suite of apps I have curated. I find these work far better for me than the defaults which come with any ROM I have used. ]

Good luck and have fun!
 
Last edited:
  • Like
Reactions: JoshReuben

Apple Pi

Member
Jul 29, 2010
40
1
8
Trying to install my microsd card as internal storage I'm getting this error:

attempt to invoke virtual
method 'java.lang.String
android.os.storage.VolumeInfo.getID()' on a
null object reference

Why can't we get an offical ROM that doesn't lay an egg when you try to DO LITERALLY ANYTHING
 
Last edited:

heyadmwutanime

Senior Member
May 22, 2020
121
15
18
Why can't we get an offical ROM that doesn't lay an egg when you try to DO LITERALLY ANYTHING
You are free to support some developers or code yourself. Also I'd just format it as external memory. What reason is there for internal? Over 128GB used space -> your performance becomes slow af. Just move your heavy files to external memory or cloud.
 

Apple Pi

Member
Jul 29, 2010
40
1
8
It's more that people say things "just work" but then you update the rom, which bricks your install, then you have to reformat everything re-install and then lo-and-behold the storage stops work and randomly hangs for no reason and then the cherry on the cake SMS no longer works. Why can't we just have an minimal ASOP ROM without all the fucking spyware that just works for once it makes no sense to me.
 

Apple Pi

Member
Jul 29, 2010
40
1
8
Miui is not an option because its chuck full for Chinese and google spyware because they refuse to just people use their devices without being monitored and monitized. Also backing up your phone doesn't help when none of the Roms come with functioning tools to do so. And the nextcloud integration on this ROM is broken too.
 

M47Z

Senior Member
Dec 12, 2011
186
65
48
I did not wipe dalvik/cache, which was strongly discouraged in the opening post here.
Is it though? Can't find where this is strongly discouraged. Usually wiping cache/dalvik doesn't hurt. You should always do it when switching rom. I usually also do it after rom updates and as an early troubleshooting step.
 

fbachofner

Member
May 30, 2009
14
6
23
Seaside, CA
Hi @M47Z

Is it though? Can't find where this is strongly discouraged. Usually wiping cache/dalvik doesn't hurt. You should always do it when switching rom. I usually also do it after rom updates and as an early troubleshooting step.
You know, you are right!

@gigahurts actually said:
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
Later on, after discussing installation of NikGAPPS he mentioned wiping cache/dalvik.

I reviewed my installation checklist and did exactly that, except I had installed OpenGAPPS. I did not wipe cache/dalvik before installing the ROM, however.

In either case, this does not seem to be the source of my at-home Wi-Fi issue. I think there is a problem with the access point; "old" (i.e. previously connected) devices work but connecting any new Android devices fails.

Have not yet had a chance to replace.

Thanks for your input.