yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] ddaggebi:
Thanks for the ROM. Tried it out.

It's not smooth, stutters more than Pie ROMs. However, given that it's still early stage for 10 ROMs, it's very impressive. No huge bugs. Totally usable performance. Pie ROMs in early stages were way more slower than this.

Keep up the good work! It will be great to see some updates!
[Nexus 4 Android Development] M4CH0:
Hi, body, good job for this, it's very smooth on my nexus4. And I want to know which gapps I can flashed on it? I can't find it. Thanks~
[Nexus 4 Android Development] dahawthorne:
https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm32/

Pico works fine.
[Nexus 4 Android Development] edi194:
Testing, testing, testing...

New build is up!

Changelog:

- updated device tree

- updated source

- changed bootanimation

Nothing pretty big ¯\_(ツ)_/¯

December patch not added... yet.

Known bugs:

- inbuilt screen recording will crash your systemui constantly, don't use it

- too big advanced reboot icon

Download link: https://mirror.codebucket.de/cosp/test/Magma-Moonshine-OFFICIAL-mako-20191213.zip
[Nexus 4 Android Development] dahawthorne:
Thanks for the new version. I like the new Marshmallow(?) boot animation.

A couple of things to report. Each time I've flashed after a total wipe (all partitions) & format.

1) Magisk still doesn't stick. Manual installation of Magisk Manager shows "Magisk not installed" although TWRP shows a successful installation. I mention this only because I don't think it's a Magisk problem, as Magisk works on my Nexus 5 with Android Q.

On my first two attempts I got a bootloop - it showed the SIM PIN screen for a second, and then the boot animation showed. This repeated for about 10 minutes.

On the third attempt I installed only the ROM & OpenGapps Pico (no Magisk), and the bootloop is still happening as I write this.

2) I set a security PIN, which was accepted, but then the security showed the unlock method as "Swipe", and no PIN is required to open the phone. When I try to change it again, it says "Wrong PIN".

I have two Nexus 4s. The other one still has the original Magma on it and it doesn't have the PIN or bootloop problems, though Magisk doesn't work on that device either.

It may be only this specific device. Can anyone confirm that these problems don't happen on their device?
[Nexus 4 Android Development] voron00:
Flashing opengapps will break multiple things in android 10 on 32 bit arm devices at the moment, including security PIN settings.
[Nexus 4 Android Development] dahawthorne:
Thanks, @voron00, but both problems persist.

Full wipe & format, install Magma only, no Gapps or Magisk, boot was fine. I chose Security/PIN, entered the PIN, which was accepted, and pressed the back button. It showed "Swipe". I locked the screen and unlocked it with a simple swipe, no PIN required. I tried changing it again and got "Wrong PIN".

And I'm afraid it's bootlooping again - a second of the SIM PIN screen and then the boot animation.
[Nexus 4 Android Development] edi194:
Looking into this, if I'll fix it I'll push new build today
[Nexus 4 Android Development] dahawthorne:
Thanks, [MENTION=4721415]edi194[/MENTION] - much appreciated.

I thought that reporting this without a log might not be too helpful, so I tried it on my second Nexus 4, which is in perfect condition. I'm afraid that both the PIN & bootlooping are happening on that device as well - just Magma, no Gapps or Magisk.

Thanks for your work on Nexus 4 Android 10.
[Nexus 4 Android Development] edi194:
Update... again

Changelog:

- hopefully fix keyguard (pin/password/pattern is now working, after reboot it takes some time to unlock)

- added (useless for now) MagmaSettings

- removed screenrecorder (not working on mako anyway)

- really small source updates

About Magisk...

To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.

Download link on first post
[Nexus 4 Android Development] dahawthorne:
Wow, you're good... :)

PIN and reboot now work correctly.

Magisk still doesn't work despite claiming to be installed in TWRP. No problem - my Nexus 4s are my emergency phones.

I don't know if it's of any help (or interest :)) but the Android 10 on my Nexus 5, on which Magisk does work, is the work of [MENTION=7268092]z3DD3r[/MENTION] - an experimental Hammerhead LineageOS 17 on the green banner at the top of this link:

https://sourceforge.net/projects/hammerhead-lineageos/files/16.0/
[Nexus 4 Android Development] ze7zez:
Unfortunately, recovery from backup twrp 3.3.1-1 UA does not work for me. The system does not stand up and hangs on flying balls. Adb works. I can do logcat if needed.

Has anyone obtained a working system from recovery?
[Nexus 4 Android Development] dahawthorne:
When I read your post my first thought was that "hangs on flying balls" must be a traditional Polish way of saying "Not very stable". But then I got what you meant... :)

I can confirm that recovering an image doesn't seem to work, which rather defeats the purpose of a recovery. I've never seen a TWRP recovery failure before. I did a backup with 3.3.1-1 UA, wiped everything except Internal Storage, and recovered the image, but it "hung on flying balls" :).

I flashed standard TWRP 3.3.1 Mako, but that's the same - although it did complain about vendor & EFS partitions not being found. When I get more time I'll reinstall Magma and try the same backup, wipe & recovery with standard TWRP.

Update: No, standard TWRP doesn't work either. Full wipe & format, flash Magma & OpenGapps only, took TWRP backup, system rebooted ok, back to TWRP, recovered this new backup apparently ok, but it's been on the flying dots boot screen for 10 minutes now.
[Nexus 4 Android Development] nitin.chobhe:
Try the commits on Nov 19, 2019 here: https://github.com/Colt-Enigma/platform_system_extras/commits/c10

Nitin
[Nexus 4 Android Development] voron00:
FYI recorder is also fixed in latest sources.
[Nexus 4 Android Development] edi194:
Yeah, I saw some information about it but on Magma it was working on every other device, just not on mako. I need to look into it, thanks for information
[Nexus 4 Android Development] ARDV:
how can i use GO apps in this release instead of standard apps?
[Nexus 4 Android Development] nitin.chobhe:
Remove the ones that you don't want and get them from the play store.

Nitin
[Nexus 4 Android Development] ARDV:
i tried installing this gapps package:

https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm32/

and i receive: incompatible android rom detected: this gapps pkg is for android 10 only, please download the correct version for your rom 7.1.2 sd 25

error code 20
[Nexus 4 Android Development] dahawthorne:
Try again. I've had this message a few times and the second attempt has always worked. It looks as if there's a temporary glitch with TWRP which mysteriously fixes itself.
[Nexus 4 Android Development] ARDV:
the rom did not even run, it stucks in the google colors moving

i came from carbon rom with android 9
[Nexus 4 Android Development] dahawthorne:
Have you repartitioned to increase the system space, and also wiped and formatted everything?
[Nexus 4 Android Development] ARDV:
yes, i did the repartition long ago before flashing Carbon Rom, i'm now using a modified TWRP to deal with the new partitions table. and i Also formatted system and cache and dalvik and data. I tried reflashing but the rom still doesn't boot.

edit: i've updated the TWRP and the Gapps are now installed, but the rom still cant boot.
[Nexus 4 Android Development] edi194:
Tried flashing without gapps?
[Nexus 4 Android Development] dahawthorne:
I thought of that too, but I've flashed Android 10 Gapps 32 many times over the past couple of weeks without any failures. As said above, the only problem that I have is Magisk not sticking. Gapps are fine and with the new Magma version of a few days ago both my Nexus 4s boot fine.

Ah, one thought. ARDV, are you using the most recent Magma? The previous version did bootloop.
[Nexus 4 Android Development] ARDV:
yes, i've tried many times without gapps.

yes, i'm using Magma-Moonshine-OFFICIAL-mako-20191214

I've also tried this ROM:[ROM] LineageGO 16 - Android Go experience with Lineage [mako]

and i got the same problem, the phone stucks in the boot animation, and after few minutes the phone takes me to the TWRP

i dont have to flash any kernel?

i’m using: twrp-3.3.1-1_UA-mako.img

edit: when i went back to Carbon rom the phone booted again, but i still want to use this rom.

i hope that you can help
[Nexus 4 Android Development] voron00:
Maybe try with official TWRP
[Nexus 4 Android Development] dahawthorne:
My last attempt. There is no TWRP option to format system/cache/Dalvik, though the wipe function does it automatically. There is a specific "format data" where you have to type "yes" to format data. Did you do this?

(P.S. There's a "Thanks" button at the bottom of each post. I encourage you to use it. It costs you nothing, but I at least value it.)
[Nexus 4 Android Development] Cice96:
Try mounting system in recovery before flashing gapps.
[Nexus 4 Android Development] ARDV:
it is not necessary that i use the modified one?

in the modified TWRP thread they say: "it is build with support of new partitions layout and sizes", so i understand that i cant use the official ne while i"m using new partitions, is it right?

in my TWRP i find optionss to format system/cache/Dalvik.

the problem now is not in gapps, even without gapps the phone doesnt boot with this rom.
[Nexus 4 Android Development] dahawthorne:
"Normal" TWRP works fine to flash the ROM. Neither TWRP version restores a backup - see the thread above.
[Nexus 4 Android Development] ARDV:
which thread?

here:

https://xdaforums.com/nexus-4/orig-development/repartition-nexus-4-repartition-t3844383

they have mentioned:

# You should use ONLY recovery from this thread since other don't support all benefits of this mod.

[MENTION=5424240]Clamor[/MENTION]
[Nexus 4 Android Development] dahawthorne:
I don't think I can help you.

You have not answered my question about using "yes" to format data.

I was referring to this thread - the comments above.

I have used both the UA & standard TWRP versions to install the ROM & Gapps successfully. A dozen times. On two different Nexus 4s. Both versions are fine to install the ROM; they are fine to back up; they do not recover the backup, so the backup is (at the moment) pointless.

I get no impression that you are properly reading or understanding or appreciative of my efforts to help you.
[Nexus 4 Android Development] ARDV:
"You have not answered my question about using "yes" to format data."

i"m sorry, i forget to answer. yes i did it and it doesnt help.

i will try official TWRP and tell you.

i really appreciate your help. Thank you.

edit: I've re-flashed the ROM with official TWRP and i get the same result, it stuck in booting animation.
[Nexus 4 Android Development] sule_krug:
I've tried it yesterday and I had problems with gapps ,I couldn't install anything from the play store(tried multiple gapps ) ...ROM itself is running but it will need more work ...thanks for your work

---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------

On my first boot it did get stuck on Google logo so I restarted it and it booted fine
[Nexus 4 Android Development] danyjad:
Waiting on gapps to finish installing here. Android 10 on a Nexus 4, what a time to be alive!
[Nexus 4 Android Development] welshgeekygurl:
Migrating from CarbonROM. Today successfully installed Android 10 this beautiful phone. Able to use it without Google Apps.

Later flashed gapps from cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm32/. Unfortunately now phone stuck on boot animation(Marshmellow like welcome screen animation). It is been 10 minutes now. What is the ideal time it take to boot?

Am I doing anything wrong?
[Nexus 4 Android Development] dahawthorne:
I remember reading a long time ago that it's best to flash the ROM & Gapps before rebooting. You could try flashing the ROM again and then Gapps, then reboot and cross your fingers... :)
[Nexus 4 Android Development] seven7xiaoyang:
i can't downlond rom from the link,can you upload this to google drive?
[Nexus 4 Android Development] matusala:
WOW. Thank you very much. This works amazingly well. I also have nexus 5 and i have pixel experience 9 on nexus 5. It lags so much. On startup nexus 5 is unusable for about 2-3 minutes. This works right away and is VERY smooth. GREAT work!
[Nexus 4 Android Development] DaShanMan:
I can't seem to download the ROM from the Server either... I've tried:

-Different Browsers, different computers, all without success :(

I'm really bummed because I prepped my N4 by turning it into a brick for quite a while adjusting the partitions.

I'm fairly certain it's now ready & capable to flash but now...

I can't download the damn Rom.

Would you please consider uploading it to another location?
[Nexus 4 Android Development] ze7zez:
Perhaps the file hosting has not been paid for at the moment, because the main page https://www.codebucket.de/ is working properly.

Wait for OP to release the ROM version that can be restored from TWRP backup.
[Nexus 4 Android Development] DaShanMan:
Thanks, I had actually tried just going to the server earlier but didn't get a response. And you are correct that: https://www.codebucket.de/ is currently UP... however I still cannot seem to download the ROM.

Patience is hard to practice when all prepped & ready to go.

I forgot to add... I'm already running Android 10 on my Nexus 7 Tablet which runs much better than pie ever did.

With the Nexus 4 being almost identical spec-wise...

And with a Lower Resolution Display, theoretically the Nexus 4 should run quite well on Android 10.

Mind you somehow I missed noticing how this ROM version could-not be restored via TWRP.

Thanks.
[Nexus 4 Android Development] matusala:
Download link is fixed now, you can download it.
[Nexus 4 Android Development] DaShanMan:
OMG!!! I have this Android 10 installed and running (really well [so far]) on my 2012 vintage Nexus 4. Wow! Simply Amazing. Thank you Ever So Much.

Even loaded the Google Playstore but to be honest...

I noticed the F-Droid application was pre-installed & kinda like this direction.

The thought could be... A LOT of the modern Google services (especially when running in the background) will likely prove to be too much for this vintage device.

My Thoughts... Avoid the heavy ones, such as maybe Google search.

Perhaps try using the Google Go instead & Loading Lighter Apps whenever possible.... ???

So far I've allowed... the Google Text-to-Speech & Sounds Upgrades + Via Browser

Gonna Keep this thing Lean & Mean ... LOL

Thanks again,

I'm still in shock this is even possible.

I'm gonna try & back it up... & then I'll try Magisk with the end goal being Root.

EDIT: So far... No luck getting Magisk 20.2 working. Hmmmmmm....

EDIT my EDIT... I've tried Installing it via TWRP3.1.1 recovery, & also via adb sideload "magisk.zip"

Even followed up flashes with using the dtb_fix.zip file (as found in the crDroid forum for the Nexus 6 aka Shamu)

Still... No Luck.
[Nexus 4 Android Development] lokenk:
https://sourceforge.net/projects/opengapps/files/arm/beta/

PİCO GAPPS OK
[Nexus 4 Android Development] sbhajband:
Network problem

I have installed it successfully and enjoys it . but one problem is occurred I am from India and here no 4g connectivity for nexus 4. In this ROM you added 4g network connectivity. Because of this my mobile has no proper network 3g or 2g.

Please provide me any Radio modem .zip for only 3g or 2g network .

Carbon ROM 9.0 is working great with 3g and 2g.

Sorry for my bad English!!
[Nexus 4 Android Development] sbhajband:
Here is a screenshot with carbon ROM 9.0 pie with 3g full network
[Nexus 4 Android Development] ze7zez:
Is Nexus 4 for India different from Nexus 4 for Europe?

Just after installing and enabling the internet, I have H+.

The choice of preferred LTE is not the same as getting it on Nexus 4.

Change in 3G network settings, then you'll have 3G.
[Nexus 4 Android Development] sbhajband:
You are a developer Please provide me any Radio modem .zip for only 3g or 2g network . in your ROM 2G network not working. H+ has only half signal.
[Nexus 4 Android Development] Holzhacker:
Does this ROM also replace the radio firmware to enable LTE? With the latest stock radio firmware LTE can't work.
[Nexus 4 Android Development] voron00:
No, but overlay for hiding LTE from options no longer works in Q, LTE option will just do nothing, not sure why people got so confused because of this.
[Nexus 4 Android Development] ALEXIS_0071:
waiting for android 10 (funny)
[Nexus 4 Android Development] edi194:
Update!

Download

Changelog:

- January 2020 security patch

- Included ThemePicker

- Included Updater

- Small improvements
[Nexus 4 Android Development] HJCK:
magisk:)
[Nexus 4 Android Development] sbhajband:
Without magisk :crying:
[Nexus 4 Android Development] edi194:
February update

- merged February patch

- added statusbar icon tuner

- added statusbar network traffic

- added themepicker in launcher

- restored messaging app

- fixed NFC settings page lag

- other bug fixes

You need to apply update manually, OTA is not working right now.

Download | Telegram community
[Nexus 4 Android Development] 7wells:
@edi194

Thank you so much for your great achievement! :good:

I am going to flash, but before I realise that there are problems with Magisk (not sticking). Or what exactly are the problems?

I found a note by @topjohnwu in his Magisk thread:

I do not have enough knowledge to judge whether his note applies here but would just like to make you and others aware of it. Does this maybe help?

PS:

I did an advanced wipe (checked all boxes) and did also a format => yes.

Flashing Android Q, Open GApps nano, and Magisk 20.3 (stable) worked flawlessly (my /system partition was large enough).

After flashing Magisk, I did a wipe dalvik/cache.

The Nexus 4 booted into the new system within less than 2 minutes - very fast for the first time, as far as I can tell from other custom ROM experiments. ;)

And the new ROM is really smooth! :)
[Nexus 4 Android Development] ze7zez:
You can always check if WebView from the Bromite project works:

arm_SystemWebView.apk
[Nexus 4 Android Development] 7wells:
The flashing of Magisk did not show any errors, but Magisk is not installed, tells me Magisk Manager 7.5.0 (265).

Now I am not sure whether to ask further questions (e.g. how to log) here in this thread, in an open Magisk thread, or in both. :o

PS: The problem/question and a possible solution has already been given there:

PS [MENTION=4721415]edi194[/MENTION]

The system bootloops after Magisk installation and uninstalling it again - see Magisk thread over there. I do not know if this has to do with Android 10/Q or with Magisk, or a combination of both, but there cannot be other root causes, as I did a (very) clean ROM installation (formatting & wiping all partitions before). Well, with the exception of Open GApps (nano) maybe? This is no criticism in any direction. I justed wanted to share this with you/everybody. :)
[Nexus 4 Android Development] 7wells:
@edi194

Flashing Magisk 19.1, 19.2, or 19.3 all lead to bootloops (after first flashing back the original bootloader from the Android 10/Q ROM). I assume the same will happen with the Magisk 20.x versions, but have not yet had the time to test these as well. Since I do not know how to collect and post logs, my feedback is certainly of very little/no value, and I am sorry about this. Maybe somebody else has some further ideas how to get Magisk working on this very nice ROM?
[Nexus 4 Android Development] Didgeridoohan:
With A-only Android 10 setups (2SI, two stage init), like we have here, any Magisk release before v20 won't work. Which is why you're getting a bootloop on those versions. Magisk v20+ is necessary.

Edit: but as you've seen there are still issues with compatible versions ("Magisk not installed"). I'm playing around a bit myself with Android 10 on the Mako, so if I can find something I'll let [MENTION=4470081]topjohnwu[/MENTION] know and who knows, maybe there'll be a fix...
[Nexus 4 Android Development] 7wells:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thanks for your hints. As beginner, I am not aware of the "A-only" thing etc., sorry. Should I try the latest canary Magisk versions? I do not know yet how it works, but I could provide logs if this helps. Maybe you or somebody could provide me with a little hint how to accomplish this? Thanks once more.
[Nexus 4 Android Development] Didgeridoohan:
No worries. Basically, A-only (and A/B) refers to a system Google introduced with Oreo where most partitions on your device are duplicated into an A partition and a B partition. It's to make system updates more seamless. There's plenty of info available if you look around the web...

If you want to try using the Canary releases it's just to go ahead like you would with the stable release (either download the Canary Manager and patch a boot image with the Canary release channel selected, or download the Canary release zip and install through TWRP). There's no difference except that the Canary releases often contain experimental fixes and code for testing, which means it can be quite unstable sometimes. It likely won't make much difference though... I'm always using the Canary releases and see the same thing.
[Nexus 4 Android Development] sbhajband:
Magisk works or not???

---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------

Wait.. ing for magisk on Q
[Nexus 4 Android Development] 7wells:
@sbhajband

Not for me, see there (canary channel).

@Didgeridoohan

Thanks once more. I have flashed the latest canary Magisk 20.4 (via offical mako TWRP) but the canary Magisk Manager then tells me that Magisk is not installed. Since this might be too off-topic here, I will address this problem in the Magisk thread over there (canary channel) or over there (official channel).
[Nexus 4 Android Development] woiddale:
Hello,

for me does all three images does not work.

Magma-Moonshine-OFFICIA-mako-20191214.zip => I can not view videos on youtube or so. I see some of the videos in black and white and strangely chopped up.

Magma-Moonshine-OFFICIA-mako-20200126.zip and Magma-Moonshine-OFFICIA-mako-20200203.zip => If I activate the screen lock with a pin, I can no longer unlock my screen with the pin. I also had problems rebooting the Android.

Best regards

Walter
[Nexus 4 Android Development] edi194:
Just fixed pin unlock, it'll be available with March update. About videos, these are working fine for me.
[Nexus 4 Android Development] Nilpy:
Maybe the magisk problem is the same one hitting the unofficial lineage 17.1 build?

https://mobile.twitter.com/topjohnwu/status/1226644269261213696

https://xdaforums.com/nexus-4/development/rom-lineageos-15-1-t3758779/page38

I just wanna install adaway :crying:
[Nexus 4 Android Development] nitin.chobhe:
Great! Can you link me the commits please?

Nitin
[Nexus 4 Android Development] edi194:
Yes, it's same bug, waiting for someone smarter than me to fix it.

Only thing was needed for this bug:

https://github.com/MagmaProject/manifest/commit/500377cd79bc875279d870990438f2af726b9cf3
[Nexus 4 Android Development] nitin.chobhe:
Thanks! Only this commit was needed: https://github.com/LineageOS/androi...mmit/9978131365c0456baf9ff742bd52005718e17034

And it fixed the PIN for me on Carbon ROM too :highfive:

Nitin
[Nexus 4 Android Development] Amrut Parmar:
Custom header support in it??
[Nexus 4 Android Development] saeedgh08:
Thx for your big job for this great rom thx alot