yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 9 Accessories] ac289:
Am i right in thinking that all quick/turbo/fast charging is done at 9 volts.

The 2 pin charger that came with my Mi9 is rated at 12v 1.5A and 5v 2A.

So is it 10W or 18W rated?
[Xiaomi Mi 9 Accessories] bioly87:
Max output is 12V * 1.5A = 18W
[Google Pixel 2 XL Questions & Answers] jonnyguitar:
Hi folks something very odd happened yesterday and I'd love your views please.

I have a Pixel 2 XL that recently stopped charging overnight and turned itself off. It was plugged into non official fast charger from Amazon I'll call "charger 1". I turned it back on and it still refused to charge.

I then tried another charger (charger 2) and it also didn't charge. I then even plugged it into a laptop and Windows said there was a power surge and wasn't going to charge it.

I had also noticed an electrical smell and the phone getting hot when it was plugged in and not charging.

I am going to return it to Google but as I need a phone for my business I went out and bought a brand new Pixel 3a XL.

Now here is the strange thing. The official charger that came with my Pixel 3a XL charges my old Pixel 2 XL and also now the two chargers I used yesterday (charger 1 and 2) don't charge either phone...

It seems a remarkable coincidence both chargers 1 and 2 broke at the same time. Could my Pixel 2 XL somehow be responsible for breaking chargers? If so, then why didn't it break the charger that came with my Pixel 3a XL?

Now I don't think I can return the Pixel 2 XL to Google.

Any help appreciated! Thanks
[Google Pixel 2 XL Questions & Answers] CyberpodS2:
If the charge port on the phone had a short in it, then yes you can possibly be trashing chargers.
[Samsung Galaxy S8 Guides, News, & Discussion] thinkwise98:
I just saw this forum and I wish someone can help me, My S8+ can't read any sim card I put. I dont know what's the problem.

http://prntscr.com/oegut2
[Google Pixel 2 XL Questions & Answers] Subhojit:
So my device is hard bricked and have tried everything advised here and on other forums.

Device doesn't get detected by any systems, it doesn't even detect otg usb devices on twrp and so on.

I have the internal storage fully wiped now.

Phone only goes to bootloader and twrp.

How do I unroot/lock the bootloader?

Does Google India care if device is rooted/bootloader unlocked?

Kindly advise.
[Google Pixel 2 XL Questions & Answers] siggey:
If you have bootloader and recovery you can restore your phone. Google don't care about root or nothing, just send the phone to them.
[Google Pixel 2 XL Questions & Answers] TechNash:
I don't know about Google India, but I used to run a repair shop and some people brought in hard bricks.

Google always accepted them, didn't care. They usually just sent a new device
[Google Pixel 2 XL Questions & Answers] Subhojit:
Google has outsourced their service and the guy made a fuss over unrooted state.
[Google Pixel 2 XL Questions & Answers] 666syco:
I had same issue none of my PC would see the phone I used a tool that I used to unlock my OnePlus 6T to fix it. It's call (tool all in one) it works with a bunch of different phone just boot to fastboot and plug in. in the program menu select pixel 2 xl and flash stock rom. That's what I did and the phone booted and stayed bootloader unlocked.
[Google Pixel 2 XL Questions & Answers] Subhojit:
I've tried that too. Even that tool wouldn't detect the phone.
[Google Pixel 2 XL Questions & Answers] 666syco:
it didn't detect it on mine either I manually selected pixel 2 XL and then flash stock image and then I selected the file and hit start it just pushed it through.
[Google Pixel 2 XL Questions & Answers] Edmontonchef:
Not sure if this has been tried. In twrp when you want to mount a type c thumb drive at first it doesn't show up. Pres back and mount again and it appears. You can flash an ota and be back to a working phone

If it doesn't detect the otg then your port is damaged.
[Omni Q&A] ischninet:
Formatting sd-card as "internal storage" not possible on Moto Z

- formatting as external storage works

- when formatting it as internal storage, it aborts, after this, you cannot open the "storage app" anymore. On the sd card, there is now a 16 MB and a 119,07 GB partition (see attached image)

- after removing the sd card "storage app can be used again (does not quit anymore when try to open)

- after removing the2 partitions on the sd card, it can be used again in the phose but ONLY AS EXTERNAL storage.

-as soon you try to format it as "internal storage, the same procedure happens again

- I have 3 Moto Z. It happens with all of them

- I have 3 sd cargs (Samsung EVO128, Samsung EVO64, Sandisk Extreme plus, it happens with all of them

- Under Lineage 16 all this is fine on all 3 phones with all 3 sd cards

- so, it is definitely a bug with the Omnirom image for the Moto Z
[Omni Q&A] deminex:
same here

with Motorola G4 plus: sdcard (128GB) has to be formated as FAT32, using original extFAT results in format request from OMNIrom, which crashes, leaving the SDcard unusable in the phone. Same when trying to use it as internal storage, formatting crashes.
[Huawei Nova 2 Plus  Themes, Apps, and Mods] Zaid0925:
Can anyone look for google camera for huawei nova 2 plus
[Xiaomi Mi A2 / 6X Questions & Answers] n0b0dy666:
It sure can
[Xiaomi Mi A2 / 6X Questions & Answers] sz.hatef:
Even if it has been damaged you can replace it so easily:

Search on AliExpress: Xiaomi Mi A2 USB Charger Port
[Nexus 4 Android Development] roland3939:
*** Disclaimer ***

This is provided free of charge and does not come with a warranty.
If your device fails to comply with your standards of what you consider functioning, I am not liable.
You do so at your own risk and take the responsibility upon yourself.

Introduction

Downloads:

XDA:DevDB Information

[UNOFFICIAL][LOS-15.1] [MAKO], ROM for the Google Nexus 4

Contributors

roland3939

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.4.x

Based On: LineageOS-15.1

Version Information

Status: Stable

Stable Release Date: 2019-07-13

Current Stable Version: lineage-15.1-20211018-UNOFFICIAL-mako-signed

second source for download: androidfilehost.com

Created 2019-07-13

Last Updated 2021-10-20
[Nexus 4 Android Development] roland3939:
reserved
[Nexus 4 Android Development] Crongar:
Thank you very much for this ROM.

How long do you plan to support updating this ROM? As fas as I understand, OTA updates will be disabled when switching?!
[Nexus 4 Android Development] roland3939:
my goal is to keep this ROM updated until EOL of LOS-15.1 or EOL of my MAKO-device (depending on which one will come earlier :)

This ROM (and its updates) cannot be installed using the LOS-15.1 system's updater app ( I didn't modify the URL defined by the updater_server_url resource )

you have to do these few steps manually:

Flashing Instruction when switching from OFFICIAL ROM LOS-15.1

1. Backup all your data before you start ( I never needed my backups, all went smooth :)

1 a. download ROM ( zip-file) to the device or do adb push ROM ( zip-file) (which ever is more convenient to you)

2. Migrate keys by script. ( to be done only once before flashing very first time this ROM )

3. Boot to TWRP recovery

3 a. Flash the this ROM ( latest build)

4. Reboot to System

have fun
[Nexus 4 Android Development] rdorsch:
Hi, did you do anything special for this build or did you just follow the build instructions https://wiki.lineageos.org/devices/mako/build
[Nexus 4 Android Development] roland3939:
Nothing special, only true LOS 15.1 repository. Build is signed and keys for migration are provided. Thus seamless switch by dirty flashing from official LOS 15.1 is easy and smooth.
[Nexus 4 Android Development] rdorsch:
Interesting, my build compiled, but did not boot :-/

Do you know https://xdaforums.com/showpost.php?p=79938551&postcount=346

?

Seems to be a similar effort (or is this yours?).
[Nexus 4 Android Development] roland3939:
what's wrong with your build? did you do any debugging already ?

No, that's in No case my build. For differences, as i know so far, please see my post

https://xdaforums.com/showpost.php?p=79957738&postcount=348
[Nexus 4 Android Development] next4:
Thx for the instructions! But how do I technically do step "2. Migrate keys by script" ?

I managed to install LOS one year ago on my nexus4 but have no glue how to run a script on my mobile device.

Sorry for asking stupid questions !?!
[Nexus 4 Android Development] roland3939:
step "2. Migrate keys by script" is explained here ( to be found in the ROM's download folder):

Using script migration.txt

for any further questions, please ask
[Nexus 4 Android Development] next4:
thx again for sharing, maintaining and providing the data and your knowledge. :good:

at the moment i am doing the backup. afterwards i will follow the txt for migrating the script.

as far as i can tell, you provided the unofficial ROM and uploaded it to google drive but where will the unofficial updates be found in the future?

---------- Post added at 12:46 PM ---------- Previous post was at 12:21 PM ----------

:victory:

everything went smooth. security updates 5.july 2019 !THXroland3939!
[Nexus 4 Android Development] roland3939:
thanks for your feedback

I'm going to share next updates of this ROM ( incl. security patches August 2019) using the same google drive folder.

hold on! :)
[Nexus 4 Android Development] roland3939:
New build with august security paches uploaded:

lineage-15.1-20190810-UNOFFICIAL-mako-signed
[Nexus 4 Android Development] next4:
Bist super. Merci!

Frank aka Next4
[Nexus 4 Android Development] roland3939:
lineage-15.1-20190906-UNOFFICIAL-mako-signed

New build with september security paches uploaded:

lineage-15.1-20190906-UNOFFICIAL-mako-signed
[Nexus 4 Android Development] thacoon:
Hi,

first I want to thank you for providing this. You saved my phone :o because my self build let me stuck at the Google screen.

I followed the instructions from the official guide for mako. The first time the command source build/envsetup.sh && breakfast mako did not succeed as expected. I then connected my phone to my pc that had the latest official LineageOS build installed, it was already a few weeks old as it was already no longer official maintained. I rerun the command and it finished successful and proceeded with the guide. However, when sideloading my self built image I got stuck at the Google screen.

Do you have any idea what may have gone wrong?

How have you extracted the proprietary blobs? Is it enough to run source build/envsetup.sh && breakfast mako or do I need to extract the propriety blobs in an extra step as the command finishes successful when the phone is connected.
[Nexus 4 Android Development] roland3939:
hi,

proprietary blobs are extracted by running the extract-files.sh script while Nexus 4 device is connected to your computer with ADB and root enabled:

./extract-files.sh

did this step succeed without errors ?

check if all files listed in "~/android/lineage/device/lge/mako/proprietary-blobs.txt" are to be found in sub-folders of "~/android/lineage/vendor/lge/mako/proprietary/vendor/"
[Nexus 4 Android Development] thacoon:
There were not files, I now run

./extract-files.sh

and it extracted the files. I wonder why

source build/envsetup.sh && breakfast mako

succeeded as soon as my phone was connected although there were no vendor files. That's why I assumed that it run

./extract-files.sh

automatically. However, if I have some time I'll redo the build and check if it now works.

Thanks for helping :good:
[Nexus 4 Android Development] nyrel:
1st time flashing

My nexus 4 device isn't working anymore. I can't get to settings and it keeps popping up an error of 'Google play store service has stopped working" in unending loop. I tried to do a factory reset but it says, "no command" or something like that. Well all that doesn't matter. Wondering if you could point me to instruction for flashing this for the 1st time? Can I still follow the ones from the old lineage website or go the current site and just follow some from another phone?

Just found this, can I use these instructions for this package ? lineageosroms.com/nexus-4-mako/

Thanks in advance for the help,
[Nexus 4 Android Development] roland3939:
hi,

for first time (clean !) flashing this rom lineage-15.1-20190906-UNOFFICIAL-mako-signed,

the instructions you mentioned are fully OK

or follow these instructions https://wiki.lineageos.org/devices/mako/install, whichever is more convenient to you

note: you don't have to migrate keys by script ( as you already did a full wipe of data, cache and system partitions )
[Nexus 4 Android Development] nyrel:
Will do this as soon as I get home. Thanks for the reply :).
[Nexus 4 Android Development] roland3939:
New build with October security patches uploaded:

lineage-15.1-20191012-UNOFFICIAL-mako-signed
[Nexus 4 Android Development] nehc_rm:
I am running on Lineage 16.0 unofficial. It's not giving me a lot of battery life. I was wondering if it is possible to flash this rom on a device which has a system partition resized.

https://xdaforums.com/nexus-4/development/rom-lineageos-15-1-t3758779
[Nexus 4 Android Development] ze7zez:
If you read more, you would know more.

This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20191109-UNOFFICIAL-mako-signed

included:

November security patches

Update default webview to 78.0.3904.96
[Nexus 4 Android Development] PsK2010:
Hi,

I come from an unofficial LineageGO 16 (link).

At first attemp my device was bootlooping (not much surprise here, I didn't realized the flashing process didn't wipe the data partition).

So I tried a full wipe of all partitions and followed the instruction from the Using script migration.txt.

After a full wipe, running the migration script and flashing the latest image (lineage-15.1-20191109-UNOFFICIAL-mako-signed.zip), everything was working fine.
[Nexus 4 Android Development] nehc_rm:
Thank you for your feedback! I did flash this firmware without any issue, coming from unofficial lineage 16.0.
[Nexus 4 Android Development] roland3939:
Hi,

you didn't have to necessarily migrate keys by script (as you already did a full wipe of data, cache and system partitions)

By running the migration script once before updating from an OFFICIAL MAKO LINEAGE-15.1, (without wipe of /data partition) all Apps and App-Data are preserved ( including calling history, SMS, . ..)

Coming from ANY OTHER MAKO LINEAGE based rom, first time clean! flashing is indispensable for this rom.
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20191211-UNOFFICIAL-mako-signed

included:

December security patches

Update default webview to 78.0.3904.108
[Nexus 4 Android Development] next4:
update went smooth again. No issues, thanks to roland3939 for providing and the work!!
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200113-UNOFFICIAL-mako-signed

included:

January security patches

Update default WebView to 79.0.3945.116
[Nexus 4 Android Development] joelcool69:
Hi @ roland3939. First of all thanks for share this work for our great N4! It's possible to undervolt this kernel / ROM? How can i do it? The custom kernels around doesn't support LOS 15.1 - 16 :(
[Nexus 4 Android Development] roland3939:
hi joelcool69,

thanks for your feedback. Primary goal for this ROM was up-to-date AOSP security in conjunction with reliability (no freezes, no unexpected reboots) for N4 everyday usage.

This in mind, OC/UV have not been my target here. Kernel source for this ROM is unchanged ( Linux version 3.4.113-lineageos-gf8d7bda4a1f --> https://github.com/LineageOS/android_kernel_lge_mako.git)
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200207-UNOFFICIAL-mako-signed

included:

February security patches

Update default WebView to 80.0.3987.87
[Nexus 4 Android Development] D4V|D:
Hi Roland,

thank you so much for publishing the newest releases! I just switched from my built in Android 5.1 to your build and it works like a charm! It runs for about a week now and works super stable and fast, feels like completely new phone. :)

I managed to make it work with microG with signature spoofing over Xposed + unofficial microG installer from this forum. Do you know if this stuff still should work after flashing a update?
[Nexus 4 Android Development] roland3939:
hi D4|V,

as this ROM is GAPPS-free and you did signature spoofing by Xposed module ( RAM patched to support signature spoofing), your chances are very good that after flashing an update your stuff will work fine again.
[Nexus 4 Android Development] D4V|D:
hi roland,

thank you, I gave it a try. If anyone should be interested: it all seems to work quite well :). All I had to do afterwards was to reinstall the Xposed framework, which worked pretty straight-forward through the Xposed app. :good:
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200307-UNOFFICIAL-mako-signed

included:

March security patches ("O_asb_2020-03")

Update default WebView to 80.0.3987.132

added a second source for downloading: androidfilehost.com
[Nexus 4 Android Development] Jogtx16v:
Rom work great. But I have a little issue. I experiment the issue on my 2 mako phone.

Many time the lcd won't wake up. Notification led still work. But black screen. I have to hold power button to reboot the phone. Thank for your help
[Nexus 4 Android Development] nefescalanadam:
do u have any easy way flash migrate key to official lineage?
[Nexus 4 Android Development] roland3939:
hi Jogtx16v,

are you able to provide log-files ( e.g. : /proc/last_kmsg ; logcat files) by adb debugging when LCD won't wake up ? This log information should be taken before executing a hard power cycle (such as holding the power button or powering off)
[Nexus 4 Android Development] roland3939:
hi nefescalanadam,

if I understand you correctly, you're asking how to migrate keys back from this ROM build to an official LOS 15.1 build:

for answer please see text file "Using script migration.txt" from downloads section in #1
[Nexus 4 Android Development] D4V|D:
This could be a Hardware related problem too. I'm using my 3rd Nexus 4 and with the two ones before I had trouble with the power switch as well (They were not running Lineage OS)
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200411-UNOFFICIAL-mako-signed

included:

April security patches (including "CVE-2020-8597_lineage-15.1")

Update default WebView to 81.0.4044.96

second source for downloading: androidfilehost.com
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200507-UNOFFICIAL-mako-signed

included:

May security patches (including "O_asb_2020-05")

Update default WebView to 81.0.4044.117

second source for downloading: androidfilehost.com
[Nexus 4 Android Development] next4:
I still enjoy my nexus4 with continued updates. Thx again Roland it´s p:highfive:retty cool you are running this thread and providing updates for my beloved phone =)

At the moment my friends Galaxy S4 recieved 17.1 Android 10... Good day. Best wishes!
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200607-UNOFFICIAL-mako-signed

included:

June security patches (including "O_asb_2020-06")

Update default Chromium WebView to 81.0.4044.138

second source for downloading: androidfilehost.com
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200709-UNOFFICIAL-mako-signed

included:

July security patches (including "O_asb_2020-07")

second source for downloading: androidfilehost.com
[Nexus 4 Android Development] roland3939:
New build uploaded

lineage-15.1-20200810-UNOFFICIAL-mako-signed

included:

August security patches (including "O_asb_2020-08")

second source for downloading: androidfilehost.com
[Nexus 4 Android Development] TigTex:
I've just installed this on my nexus because I needed it to temporary replace a failed phone. Some information is missing on the first post so I'll post it here.

Just like official lineageOS, there are no gapps included. So remember to install them from opengapps. Select ARM cpu and android 8.1. Choose the smaller pack.

There is not enough space to run this ROM and pico gapps (the smaller pack). So you need to change the system and cache partitions size. To do that, check lineageOS 16/17 posts on this forum. There is a flashable zip.

Stock TWRP will give an error when you flash this rom. You need a modded TWRP that it's not easy to find. Check here Also, it's possible that this twrp version will fail to reboot the system. Mine did.

After flashing the ROM and before flashing gapps, you need to resize the partition size and you use twrp for that: Just go to wipe, select system and "change or repair file system". There's an option to repartition. Make sure that the partition size is above 1200mb. Remember to format "cache" partition.

First boot will take 5 minutes. Be patient.

Good luck and have fun!
[Nexus 4 Android Development] roland3939:
hi TigTex

[MENTION=4978916]TigTex[/MENTION] can you please give a bit more justification for your remarks on installing gapps on this ROM.

There was no need to resize any partition when installing pico gapps (open_gapps-arm-8.1-pico-20180510.zip)!

Further more, Stock TWRP 3.2.1-0 ( and newer TWRP versions) are working fine when flashing this ROM!
[Nexus 4 Android Development] Waldold:
Seems all running well after yesterdays update of outdated official LOS. (y)

But it was a little complicated quest to install working ADB for running script of migration keys, it may be a problem for beginners.
[Nexus 4 Android Development] roland3939:
New build uploaded 20200826

lineage-15.1-20200826-UNOFFICIAL-mako-signed

second source for downloading: androidfilehost.com

Change-log: ipv4: Pass struct flowi4 directly to rt_fill_info

this fixes: Latest Firefox (Version 79.0.5, Version 80.0.1-beta2 and some other apps) causing soft reboot after launching.

credit goes to [MENTION=11050113]Waldold[/MENTION]
[Nexus 4 Android Development] roland3939:
hi TigTex,

size of GoogleTTS has increased by approx. 60% during last 2 years. So, one option is to reduce the size of opengapps pico by configuration.

Please see also here: https://xdaforums.com/showpost.php?p=76444485&postcount=2

BTW: official TWRP 3.4.0 has some issues with rebooting.
[Nexus 4 Android Development] Waldold:
Yes, it reboots again and again back to recovery menu even if you choose "shut down" the device.
[Nexus 4 Android Development] aarem:
One option may be to include microg and ditch google to the extent practical.
[Nexus 4 Android Development] 7wells:
I nevertheless recommend using the latest twrp-3.4.0-0-mako. If one wants to shutdown, simply keep pressing the power button until the Nexus 4 powers off. And if one wants to boot into the system, power the device off like this and then on again. This TWRP problem seems rather a problem of missing convenience, and eventually this will be fixed, too.

[MENTION=7193478]roland3939[/MENTION]

Thank you very much for offering LOS 15.1 builds for the Nexus 4 and for the hint & link about excluding Google TTS. :good: I confirm that thus, flashing OpenGApps pico works without problems.

I flashed your latest LOS 15.1 build (26 Aug 2020) on a formatted & completely wiped Nexus 4, i.e. no previous official build on the phone. How does your guide & script for migration of release-keys apply in my case? How can I sign your latest LOS 15.1 build with keys to become official? :confused: Thanks for your advise.

Do you plan further updates of LOS 15.1? (e.g. with the September 2020 security patches)