yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
New release! 🥳

.. in progress (keep an eye on my TG Automation channel)

As mentioned I do not provide changelogs besides from my TG Automation channel anymore but this one is important so I drop a note here, too.

first of all I've changed the versioning back to /e/ standards. I've used "v1-0" in the past as I thought that will happen soon (lol) and as its used by them as the most recent branch names (e.g. v1-q). To get a better understanding of which exact version you get (and be able to identify the matching official /e/ changelogs) I will use what they use (atm of writing: v0.16). Due to this versioning change the newest update will not popup as an OTA so you have to boot to TWRP and flash it manually.

second: I have changed the signing keys (actually one of my build scripts deleted them by accident). Because of the version scheme change this does not matter at all for you as OTA does not work anyways.

the next & last major one: I have enabled UNOFFICIAL builds again. The reason is I am planning OFFICIAL builds. I personally like to have F-Droid, Aurora and so on already included in the ROM so I will continue doing CUSTOM builds including OTA support as well. The major diff is that some apps will be included in the ROM and "Apps" will be removed. Other then that will be identical. Until we reach the OFFICIAL state I will provide CUSTOM + UNOFFICIAL builds.

This build contains a ton of fixes & enhancements made by @aoleary so I hope I didn't broke anything while merging his changes ;)

oh ya and some little changes from my site regarding charging led (led blinks green when charging and goes solid green when fully charged) :D and some other tweaks here & there

Installation instructions:

follow the FAQ to do at least a regular clean flash correctly. If you encounter any issues do a full clean flash.
[G4 Android Development] breversa:
These are AWESOME news !!! :D

But I thought going official was out of the question. Has anything happened regarding this, and if so, what ? Care to share your thoughts ? ;)
[G4 Android Development] steadfasterX:
yes it was but now it will be possible ;) its in progress already (but depend on them atm). and no there is no ETA ;)
[G4 Android Development] breversa:
I'm not the kind to ask for ETAs anyway. ;-)

I clean flashed your latest custom on my unlocked h815 and everything is fine, though it felt a bit slow at first.

By the way, will @aoleary 's fixes be backported to LineageOS or even AOSP (if that makes sense to begin with) ?
[G4 Android Development] steadfasterX:
LOS yes that will come next
[G4 Android Development] nubla:
It's fantastic to see so much development effort for such an old but still wonderful device. Thank you all! Can't wait to try it out.
[G4 Android Development] breversa:
Alright, I've found a bug in 0.16-p-20210419-CUSTOM-h815 (clean flash) : the led blinks green (I guess ?) when the phone is charging, even when the battery led toggle is off.
[G4 Android Development] steadfasterX:
oh man I wasnt even aware of that setting.. that explains a lot..
[G4 Android Development] breversa:
Yeah, and it's tedious to find too !

It's in Settings > Notifications > Battery light(/led/whatever)
[G4 Android Development] nicolaslienart:
Hi, thanks for supporting our beloved G4!

I am a bit lost, I am running v29A at the moment and I'd like to move back to v20p in order to switch to your custom /e/ ROM. The flashable file seems to be what I need but the link is broken, can you provide a new one please?

Thanks heaps
[G4 Android Development] nubla:
Updated to TWRP 3.5.2_9-PREVIEW-270_g4 and e-0.16-p-20210419-CUSTOM-h812_usu. At first I was confused by the appearance of the /e/ "Apps" store, but realized I had unwittingly installed the UNOFFICIAL version. Nope, I prefer the custom build without "Apps"! Thanks steadfasterX for making a build pretty much exactly to my liking.

Some issues/questions:

- The default Bromite browser was not able to load any webpage, with message "ERR_NAME_NOT_RESOLVED", suggesting to check internet connection and secure DNS configuration. Other apps and Fennec connected without issues. I had to look in Bromite's Settings -> Privacy and security -> Use secure DNS -> and select a provider, since it was set to Custom with a blank provider URL/IP.

- I noticed new apps DNS66 and Omega Launcher which I did not install myself. What's the reason for additions? Btw, I use Lawnchair launcher. For DNS, I know the built-in settings are very limited.. maybe that's why?

- Noticed the new feature of the green LED blinking during charging... but why? Is there any override for this? There is already a Battery Light configurable option in Settings -> Notifications -> Battery light, which I had configured for low, charging, and full states. The new feature forces itself on top of those, so that there are multiple simultaneous charging indications now, unless I turn of my customized ones and stick to the new default.
[G4 Android Development] breversa:
I didn't realise that Omega Launcher was now included, but I wholeheartedly support this move, as I don't like Bliss Launcher. (y)

Also, Lawnchair (2) is no longer maintained, while Omega is still being developped. :)

That's a bug. It's been reported already, both here, and in the LineageOS 16 thread.

From what I can gather, the led blinks green (I guess) whatever the led toggle position :

If the toggle is off, you'll see blinking.

If it's on, the led will stay on (actually, it'll blink over/under a fixed colour).

There's currently no way to keep the led off (AFAIK) while charging. Good luck trying to sleep in the same room as a charging phone. :cry:
[G4 Android Development] nubla:
I guess I'm a bit resistant to sudden changes. I'll have to try out Omega and see how it compares to Lawnchair. I know the latter is no longer supported, but I stuck with it because I liked it best and didn't have issues with it. I had tried a whole pile of launchers when I first started using /e/ because Bliss is just... well let's leave the adjectives alone. haha

Aha, so that's what you meant! I was confused because this was even mentioned as a feature in the "release notes" post.

The blinking really bugs me. I use it only for notifications that demand attention so that they get taken care of and the blinking can stop...

In any case, as long as the user has an option to override the defaults, that's what matters. Glad to know it'll be addressed.

Also, is there a way to disable the screen turning on with a "New Notification" message? That's redundant when there is a notification sound and notification LED...
[G4 Android Development] nicolaslienart:
I switched to /e/ CUSTOM on my unlocked H815 yesterday and can share my experience:

Coming from v29A H-ROM that I've been running for 4 years without lags, but I now want to keep moving away from proprietary stuff.

I did a clean and full install and flashed 20p bootloader and modem, rebooted and flashed /e/

However I didn't have access to internal storage somehow, /sdcard directory just contained a .TWRP directory and was read-only. I can't tell what went wrong during installation (when I checked this directory through TWRP file explorer it was exactly the same).

So I restored my NANDroid backup and installed /e/ without full format and it works like a charm now!

Thanks heaps to the maintainer steadfasterX for supporting our G4 with this wonderful ROM, I can now stand free against GAFAM. It also saves us from renewing our device, the planet thanks you too 🌿

Donation made to help you maintain your leech server, hope it helps.

EDIT

I just noticed that power button double press to open camera is a bit too sensible and triggers accidentally (the option is called Jump to camera in the settings)

The Long press for torch setting doesn't work for me too

EDIT 26/04

Double-tap works for me but it's sometimes slow (few seconds before the screen turns on) and capricious (Tap to wake), I can't tell if it''s my device as I didn't use this feature back when I was on LG ROM. It also wakes-up accidentally even if the option Prevent accidental wake-up is activated.
[G4 Android Development] nubla:
Yes, I've noticed these issues too. For the camera shortcut, I find pressing the power button slightly towards the bottom of the phone helps avoid this, but it still happens to me pretty often.

I'm having a strange issue where FairEmail's new email LED notification turns from the default yellow color to red after a few minutes. Waking the screen returns it to yellow, and again after a delay it turns red. I wonder if it could be related to the charging LED patch to the ROM, or if it's a bug in the FairEmail app, or something else. The blinking red LED made me think my phone battery was low. Also I don't see any way to change FairEmail's notification LED color in the android settings.

Also, is the screen waking up to display "New Notification" a new "feature" of android? And can it be disabled?
[G4 Android Development] steadfasterX:
Omega is the most popular fork of Lawnchair. I like Lawnchair too so i switched to Omega. Good news are that Lawnchair dev has slowly started again and so Omega will be replaced one day. Yea the bliss launcher ... I don't like apple style nowhere.. Besides the functionality is very limited...

Dns66 is a rootless adblocker! It use vpn techniques while actually not using a vpn. I prefer adaway but trying dns66 as an alternative without root.

Your bromite issue might be solved with an update.

Led has been answered by others already and is going to be fixed.
[G4 Android Development] levider:
Did you try blokada?
[G4 Android Development] nubla:
That is good news about Lawnchair slowly getting revived!

The trouble with those "vpn techniques" is that it interferes with using an actual vpn since only one such app can be used at a time.

The bromite connection issue was solved once I went into settings and selected a secure DNS provider. The problem was just that the setting was blank by default.

Is it possible to have the navigation buttons auto-hide in bromite to gain more viewing space? I did not find such a setting and now it is always displayed.

Could the LED issue cause problems with other apps? FairEmail's notification changing colors from yellow to red to yellow is really bizarre. EDIT: It's not just FairEmail. I changed Signal's notification LED to white to make changes easier to spot, and after some time, it turns pink. If the screen is touched it returns to white. It seems something is adding red to the notification LED after some time. Does this make any sense in the context of the LED patch issue?
[G4 Android Development] steadfasterX:
Yes when using dns66 you can't use a regular vpn at the same time. I just disable dns66 then as it makes no sense to me using an adblocker within my vpn but if you need that there are better solutions using root.

All led issues you may encounter atm are related to the led charging change - as long as it happens when a charger is connected.
[G4 Android Development] nubla:
This is without the charger connected.
[G4 Android Development] nicolaslienart:
Hi :)

AOSP Android Keyboard is showing emojis with their skin color substitutes which makes the list very long to scroll and it's actually unusable for me (see scrollbar size 😅)

I don't know if it's the intended behavior but maybe it's a bug on my device. Is anyone experiencing the same behavior?
[G4 Android Development] breversa:
https://leech.binbash.rocks:8008/e-os/pie/h815/e-0.17-p-20210607-CUSTOM-h815.zip fixed that bug ! Thank you @steadfasterX ! I can finally sleep in the same room as a charging phone ! ^^
[G4 Android Development] nubla:
Can confirm, v0.17 solves notification LED issues introduced in v0.16. Both with charging, and the bizarre color change of app notification lights getting red added to them.

Also, funny to learn of updates via this forum even before the phone notifies of available updates. Update procedure went smoothly.
[G4 Android Development] nicolaslienart:
Hi :)

Thanks for fixing charging LED, it's so much better to have the control now!

I am experiencing a dark mode bug with Contact app, it's really hard to read text because it is also dark instead of light. It's fine in light mode.

See screenshot below.

EDIT 06/29

Same issue with Music
[G4 Android Development] breversa:
Same for me, also in french FWIW.
[G4 Android Development] MorganXYZ:
I assume my bootloader stack is on the lastest MM version for my model (h815) as I recently installed lineage-16.0-20210608-UNOFFICIAL-h815.zip but if it wasn't how would I know and would I flash this:

h815_20p_bootloader_20p_modem_TWRP-flashable.zip

?
[G4 Android Development] MorganXYZ:
Also, in the instructions for LOS you suggest both LOS su and Magisk if I want root:

But for /e/ you only suggest Magisk:

Why?

Is there any way to root without your warning at FAQ#1?
[G4 Android Development] steadfasterX:
That depends on if you have an official unlocked device or not (i.e. UsU). When you have an official unlocked device then yes this bootloader zip is correct.

The problem is "assuming" is not enough to be sure. flashing a ROM will not touch the bootloader. If you are not sure then I can just strongly recommend flashing the bootloader zip - thats the easiest way to be sure. The other way would mean to use SALT, extract the 20p kdz, making a SALT backup, verifying md5sums of all bootloader files. so in sum.. flashing the zip is easier for the most ppl.

LOS su is deprecated and is for LOS (so not for /e/ - even when based on LOS)

Magisk is the state of the art root method anyways.

You (i.e. the user) can do a LOT of things wrong when using Magisk though. I talk mainly about installing (bad) Magisk modules here. Other then that Magisk is the only reliable way to go if you need root.

There are lot of other stuff which might can happen and how should I guarantee your reported issue is a ROM issue or not? So no, the warning in FAQ 1 is something you cannot avoid when using Magisk sorry.

btw: that does not mean that you are not allowed to ask things etc. it means that we might get to the point that you have to un-root to narrow down an issue (never happened in the past but..)
[G4 Android Development] MorganXYZ:
Thanks @steadfasterX for the detailed responses - this /e/ project is very interesting, both generally and your custom implementation and reasons why.

Oh! There sooo many problems with assuming!!! (But, less if you tell everyone.)

However, I had the same back up as I had for the LOS flash so I could only do so much damage and I definitively did an official unlock many years ago, so all is well.

I did the same as the LOS install with the addonsu from LOS - that seems to have worked as it did for LOS, but I take on board that it's depreciated and Magisk is preferred - I assume (Oh no, not again!) I flash with addonsu-remove-16.0-arm64-signed.zip I can then move to Magisk? (Actually, I'm not really assuming, I'm asking if I would be correct to assume if I did. :)) I just found this: LineageOS is dropping its own superuser, which seems to explain what's going on.

I've discovered that although microG self-check reports signature spoofing to be working, the Signature Spoofing Checker app reports it not to be working and there's no control switch under Dev ops - is that as it should be and because of the use of 'Restricted patches'?

Many thanks, M
[G4 Android Development] steadfasterX:
Yes using the removal zip will allow you to flash magisk.

Good point about the restricted microG . I had completely forgotten about that. As written in the OP i provide only builds in restricted mode.. The setting in Developer options was written by me when i had integrated the microG Patches into LOS and as mentioned in the LOS thread you won't find them here or there anymore.

I think I will switch my custom build to full Spoofing support any time soon.
[G4 Android Development] MorganXYZ:
With switches - it's always nice to have switches to toggle :)

And, should I be troubling you with bugs with microG? Or should I go upstream - calendar and contacts feeds don't seem to work? Also, Maps doesn't seem to work where it used to work on LOS - it seems to pick up the accounts from microG and then detect that there's not enough GPS whereas on LOS it just didn't seem to realise and ran without an accounts?
[G4 Android Development] steadfasterX:
nope. that was the part where I said it is too much work maintaining that (as it is my own code and none where others contribute).
[G4 Android Development] MorganXYZ:
I can get by without switches to toggle; I'll just have to find something else to fiddle with :rolleyes:
[Android Head-Units] tin2001:
99% of my driving, I know where I'm going and I only need music and GPS speed info displayed on my head unit. On longer trips, even if I know where I'm going, I'll use Google Maps to help me keep track of how the journey is progressing, but I don't really need the entire full screen map.

What I'd like to do is have a launcher screen that has all this shown, all the time, so I rarely need to open an app. The last part of the puzzle is the next turn navigation information... So far I've discovered Google Maps and Waze don't offer widgets for this, but haven't looked at any other navigation apps.

I've also tried several car-specific launchers and found FCC Car Launcher can kind of do it (if you give it your own Google Maps API key), but this launcher runs very slowly on my cheap unit.

Does anyone know of any way I can do this?
[OnePlus 7 Questions & Answers] jeticson:
Hey Folks,

Can any one help me figure out How to enable AptX Codecs on my OnePlus 7 (GM1900 running OOS 10.3.3.GM57AA)?

I tried many times in Developer settings, but they get reverted the next moment always. Any workaround???

I bought a pair of Earbuds but cannot enjoy this feature. Any help is appreciated. Thanks in advance.
[OnePlus 7 Questions & Answers] Prinçe çharming ap:
They are auto tuned if your hardwares(earbuds) are not supporting AptX codec then it always uses default codec you can't do anything about it...

At least not in Oxygen Os
[OnePlus 7 Questions & Answers] jeticson:
Soundpeats Trueair earbuds are equipped with QCC3020 which is capable of AptX codecs. It must be a bug in OOS. I tried to force use AptX codecs in Developer settings but only to fail.

Link to buds features here: https://www.soundpeatsaudio.com/en/true-wireless-earbuds-trueair.html
[OnePlus 7 Questions & Answers] Prinçe çharming ap:
Maybe you are right
[OnePlus 7 Questions & Answers] Danaosthedemon:
have you tried the magisk modules to enable aptx and other codecs?
[OnePlus 7 Questions & Answers] Prinçe çharming ap:
for me only AAC codec worked because my earbuds only supports AAC codec you can see in the screenshot my earbuds is AAC enabled,check yours also if it is AptX enabled after connecting to phone or not. i thought that you want to switch to AptX codec to remove latency issues...or may be i am wrong ?
[OnePlus 7 Questions & Answers] jeticson:
Am not rooted.:(
[OnePlus 7 Questions & Answers] jeticson:
I do not get this extra option in ear buds settings.

But I got the AptX enable menu when I connected the same buds with a Oppo Reno device. So it's a Op7 device OS issue. I have taken the issue up to the OOS Team in OP forums. They have taken logcats and said they are working on this issue. Hope to get it solved.
[G4 Q&A, Help & Troubleshooting] Zaidmughal:
I have LG G4 H812 I unlocked it using UsU. I installed PixelExperience ROM and it worked fine for months, but recently WiFi started misbehaving, I tap on the icon in quick settings to turn it on but it just keeps on blinking, and then does not turn on. I go to WiFi settings to turn it on and it does not turn on, after several attempts it turns on but does not scan WiFi networks, I tried resetting the device, Wiped Cache, Data, System, Delvik Cache, Performed Clean Install of latest ROM. I read somewhere to smack the phone to see if the WiFi works by smacking (pointing a hardware issue) but that does not work too. I cannot afford a new phone and this phone is useless without the WiFi. And Yes, it gets hot a lot. Please Help:(:(:(
[G4 Q&A, Help & Troubleshooting] Feduz:
Same issue.. MAC Address of WIFI is 02:00:00:00:00:00
[G4 Q&A, Help & Troubleshooting] Zaidmughal:
MAC address us normal in my phone.
[OnePlus Nord Accessories] Hastaloego:
s.t.
[OnePlus Nord Accessories] karimski75:
Nillkin superfrosted shield case
[OnePlus Nord Accessories] Lazy Rich:
Where is that?
[OnePlus Nord Accessories] karimski75:
AliExpress
[OnePlus Nord Accessories] netokee:
One of the best case I have

View attachment 5250605
[Windows Mobile Development and Hacking General] wwejason:
Is there a copy of Yahoo Go that works for WinMo 6 that might possibly work with the 800w?
[Windows Mobile Development and Hacking General] kenny782:
did you ever find it?
[Android Head-Units] muish002:
Hello All,

I might ask something stupid now, but I know from the past people generally are very helpful here.

I concider myself handy enough with androif (phones!) but since I had someone building in a android head unit,..

The first one had all kinf of bugs, but atleast I could use a launcher i liked myself,.

But, due all the bugs they replaced it. looking good, but...they, to start with, blocked the launcher. or well. I can install it. I can set in settings the standard launcher, but somehow it always comes back in the main layout. "BC LAUNCHER"I think it is.

The controls mainly go trough a partly transparant circle on your screen, giving a home button, page back etc.

When I use the launcher, somehow I miss, for instance, a go back button somewhere. So have to use that little circle again, And you guess it; returning me to the main layout.

So..was thinking; I install an other rom. But! This android unit also operates my standard car functions, such as satnav, some settings of thecar etc.

So,. basically, they fitted the android in between the Mercedes system. Really not what I want (if android fails, all fails!) but only thing I can do about it is have all removed. And I really use it a lot.

I believe the system runs on android 9.

So. If I would find a Rom;

I looked into the info of the system, but at MCU I find some custom MB line. Not what I would exopect.

I realise my info I am giving is quite limited, but rather hear where to find the correct info then drop all kind of non relevant data here.

How large would be the risk that the communication with the car goes wrong? Or is this a seperate part?

I hope I make sense!
[Android Head-Units] muish002:
I managed to figure out the specs, see pics.

But now what? Suuplier claims its for sure Android 9,that all works as supposed (can't even control Spotify with the car buttons), and that e. G the laucher are 'experiments that he doesn't support.'

Supplier has zero knowledge of android.
[Android Head-Units] muish002:
(sorry, my phone didn't allow me to add the pics, the xda app is waster)
[Android Head-Units] KostasDan:
Sorry for kicking this older post but i have the same problem... I am desperately searching for options with my new android based head unit mine is a MT8988 with android 10 installed in a W204 MOPF MB.

These are the specs...

View attachment 5226079
[Android Head-Units] muish002:
You bought, just like I did, a fake unit. Run an app that will tell you the REAL specs.. You'll probably find its android 7 or 8.

You probably still have a little box with these systen? That's old anyway. All modern (android 10)systems have only a screen where all is in.

I took mine out, sold it, and bought a real android 10 unit, that allows me to do anything. It works like a charm!
[Android Head-Units] KostasDan:
Can you recommend me a app that could tell me the real specs??
[Android Head-Units] muish002:
Sure, try devcheck
[Android Head-Units] KostasDan:
Either good or bad these are my specs according to devcheckView attachment 5227023View attachment 5227025View attachment 5227027View attachment 5227029
[Android Head-Units] muish002:
I miss operating system?
[Android Head-Units] KostasDan:
View attachment 5227437