yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Lite Questions & Answers] aliakhgar:
im close to flash the files but i cant finilize them. i get this error on pmbootstrap install.

any idea?

a@a-virtual-machine:~/Desktop$ pmbootstrap install --android-recovery-zip --recovery-install-partition=data
[23:16:28] *** (1/3) PREPARE NATIVE CHROOT ***
[23:16:30] (native) install cryptsetup util-linux parted
[23:16:31] *** (2/3) CREATE DEVICE ROOTFS ("qemu-amd64") ***
[23:16:31] ERROR: Selected kernel (stable) is not valid for device qemu-amd64. Please run 'pmbootstrap init' to select a valid kernel.
[23:16:31] See also: <https://postmarketos.org/troubleshooting>

Run 'pmbootstrap log' for details.

Before you report this error, ensure that pmbootstrap is up to date.
Find the latest version here: https://gitlab.com/postmarketOS/pmbootstrap/-/tags
Your version: 2.3.1
[Huawei P9 Lite Questions & Answers] can0866:
Hello, first, you need to run this command:

$ pmbootstrap init

Work path: You can leave it as default
Channel: edge
Vendor: huawei

Device codename: venus

Username: choose a username

Provider: just press enter

User interface: you can select phosh, if you encounter any issues, select xfc
For the rest, just press enter.

Then, run the install command:

$ pmbootstrap install --android-recovery-zip --recovery-install-partition=data

After doing this, the necessary steps for flashing via adb can be found here: https://wiki.postmarketos.org/wiki/Installation_from_recovery_mode
[Huawei P9 Lite Questions & Answers] aliakhgar:
thanks. installing it. before flashing, were you able to see os logs to find the issue? or trying a second flash.

btw any options other than open bootloader, root, and unmounting partitions before flash to check?

should i wipe manually before flashing ?
[Huawei P9 Lite Questions & Answers] can0866:
Hello, I believe I've tried flashing more than 20 times using every method, but I couldn't make the boot process successful. I've examined the kernel logs but couldn't find the issue. Maybe it won't be a problem for you; the device I'm using is the NMO-L31, but it has the same features as the P9 Lite, so there shouldn't be a problem, yet there is. I couldn't determine whether the issue is with my device or the files. There's no need to do anything extra before flashing aside from the methods you mentioned; manually deleting didn't change anything in my case, it probably deletes itself during the flashing process.
[Huawei P9 Lite Questions & Answers] piero-e:
hello,

as i can remember, to flash a recovery compatible build targetting the /data partition,

using TWRP, you need to first unmount all existing /partions on the device
[Huawei P9 Lite Questions & Answers] aliakhgar:
i did unmount the partitions. i had a successful flash. but on boot screen im encontring this error.

Error: boot partition not found.

retrying...

this error

Troubleshooting - postmarketOS Wiki

wiki.postmarketos.org
[Huawei P9 Lite Questions & Answers] aliakhgar:
i'd be happy to try out your image.
[Huawei P9 Lite Questions & Answers] aliakhgar:
usb networking is working fine. i managed to log into ssh in my p9 lite using usb networking
[Huawei P9 Lite Questions & Answers] can0866:
Did you manage to solve the problem? What do you mean by USB network, my friend?
[Huawei P9 Lite Questions & Answers] aliakhgar:
i dont know if my/your files were ok but i used this repo files on github. and also as brightness was increasing on boot freeze i had an idea that kernel probably booted just fine.

try this.

USB Network - postmarketOS Wiki

wiki.postmarketos.org

when i connected my phone to my windows it was reconized and i could connect it to my vmware ubuntu and using dhcp commands i gave it an ip and connected with ssh.

this is the repo i used. but remember its still freezed on boot logo.

GitHub - Exiatron00/pmos_venus_sources: pmos_huawei_venus

pmos_huawei_venus. Contribute to Exiatron00/pmos_venus_sources development by creating an account on GitHub.

github.com
[Samsung Galaxy A52s 5G] sanderbos:
On manually installing Google Play System Updates, I encounter problems.

I am on the April Android Security Update and also the April Google Play System Update (and no rooting or custom ROMs).

But there are still 2 Google Play System Updates waiting, one of 9.9MB and one of about 700KB that comes after that.

But after installating the 9.9MB patch, my phone will spontaneously reboot within one minute of starting the phone.

Not every time, I have sometimes rebooted my phone succesfully after installing the patch, and installed the second patch. But always after a couple of phone reboots, my phone will suddenly reboot after restarting the phone.

And when that happens (and only then), the 9.9MB patch is waiting for me again, so apparently it is rolled back when that happens.

I have found at least four forum threads online in different languages of people having the same problem, but I actually thought it would have more coverage.

(I have submitted a bug report with Samsung, previously they were quick to respond when I filed a bug report, but not this time)
[Samsung Galaxy A52s 5G] wiresquire:
I have noticed exactly the same issue. I haven't noticed the 700KB update. When I apply the 9.9MB April update, and reboot, the phone restarts itself before I can do anything else.

Sitting on the March Google Play System update, the phone seems to be working OK otherwise.
[Samsung Galaxy A52s 5G] sanderbos:
The May system update (so not the google play system update) appears to have fixed this issue. I am now fully up to date with patches for both system update (May) en google play system update (April), and could manually reboot 5 times without issue.
[Tilt, TyTN II, MDA Vario III General] wisniak:
Hi,

I currently use AS 4.5 to sync my Exchange data to my Tilt.

I sync the Calendar etc every morning before I leave for work.

However, the calendar is frequently updated during the day, and I want to ne able to sync to my work PC as well during the day.

Due to a variety of reasons (not technical), I'm not able to use push mail or to sync via a third party tool eg Google.

I recall that during my Dell Axim days, I had a hell of a time synching between my home and work computers (many times I'd get duplicated calendars, etc).

I'd appreciate your recommendations regarding appropriate syc apps that would replace AS and would allow me to sync from my 2 PCs (both are WinXp), and I always sync with my Exchange account that contains all my data (calendar, emails from all my accounts, etc) as a single source (ie I don;t have 2 separate Echange accounts, which should simplify things).

I'm aware of Missing Sync and Chapura Pocket Mirror Professional.

Can anyone here recommend either one, or another app?

Thank you.
[Google Pixel 7] eksitus:
Hello!

I recently bought a Pixel 7 from a carrier (Visible, a sub-brand of Verizon), risking being locked with stock OS for a hefty discount.

Surprisingly, I managed to successfully turn on the OEM unlock.

Now with the OEM unlocked, how can I make sure the device will not lock itself, for example after another factory reset?

I want to fully update it and use it with stock Android to test it for a week (to see what I'll be missing if anything) and switch to GrapheneOS.

Would that require somehow reflashing the bootloader?

I just want to make sure any Visible / Verizon modifications (underneath the android) are no longer in place and I'm not risking being OEM locked for good.

(Basically make it as close to ones bought from Google store as possible).

I'd appreciate any advice or guides hot to properly sanitize the phone, or what should be my next steps,

Thanks!

=====================================

Visible specific info [skip reading if does not apply to you]:

Unlocking was supposed to be possible only after 60 days of using the device in the network (I wonder if that would work with no issues, I'm sure their customer service would not be very helpful), so IMMEDIATELY after I got the device:

- I turned it on and followed the most offline setup possible (no SIM, no WiFi, no password setup)

- I opened settings (OEM was greyed out)

- Restored phone to factory settings

- Plugged in T-mobile SIM (disabled mobile data beforehand)

- Turned phone on and followed offline setup

- OEM still greyed out

- Connected to WiFi

- I was able to OEM unlock

Probably most steps are unnecessary and what is the most likely is that Visible forgot to lock the device, but I did not want to miss any chances, doing what I could to bypass the OEM lock.

Hope this info helps someone in similar situation, but remember your phone might come locked and you might need to deal with not very useful Visible customer service after 60 days.
[Google Pixel 7] bobby janow:
@eksitus Why not just unlock it now? It'll still be stock with some minor issues regarding security stuff but if you're going to load Graphene anyway what the heck. Once you have the OEM switch active and toggled to allow unlock it will not revert back. So whatever you decide to do will have no effect on the ability to unlock. As for the steps you took the only one needed was to connect to Wifi (the internet) in order to make the switch active.
[Google Pixel 7] eksitus:
Thank you for the reply!

I already toggled the OEM unlock switch, but I am still paranoid that once I'll insert the Visible SIM card and update the stock system, at some point they will be able to lock the OEM / ability to use other carriers for 60 days.

I've heard that carriers have ability to lock the phone with their SIM card (but feel free to educate me on that).

So is there a chance they would proceed with the lock when they detect Pixel connected to their service?

Is there any way to prevent it (by modifing the currently unlocked system)?

Do you know if Graphene prevents carriers from locking the device, or if by reflashing the phone with stock Google Android would deprave them from this ability?
[Google Pixel 7] bobby janow:
I guess they can do whatever they like but I've never heard of a carrier changing the OEM toggle to inactive once it's active and flipped. The way I read it is once you connect to the internet it queries the carrier with your IMEI and that will determine if the switch is active or not. I'm not sure anyone knows for sure but that's pretty much the common thought. But back to my original question, why not unlock now that you can? It won't hurt that much, perhaps a banking program or two might give you trouble but you probably don't use those if you're concerned about privacy and using Graphene.
[Google Pixel 7] manjaroid:
Enabling OEM unlock allows bootloader unlocking, necessary for flashing firmware. (In the case of Graphene it's recommended the bootloader is re-locked once installed.) Unlocking from the carrier is a different matter but it's usually the first step in making the OEM unlock switch selectable on a carrier's phone. Since you were able to easily toggle the switch I wonder if your Pixel was carrier locked to begin with. It definitely doesn't sound like a typical Verizon phone.

As a point of reference, mine is unlocked and was purchased from Google. But based on the IMEI Google Store's RMA process identified it as a Fi phone. Meaning Fi is the same as unlocked, or vice versa. Maybe your situation is like that and you're free and clear of the carrier to do what you want. You won't know for sure until you try unlocking the bootloader with the Visible SIM installed.
[Google Pixel 7] eksitus:
Thanks a lot for the reply!

I'll for sure install the Graphene in a week or two, but first I wanted to test the original system beforehand to see what features I miss and what features I gain (out of curiosity). For example I wanted to test whether the camera (app) quality is similar, or does the battery drain slower/faster.

I did not know I can look up the status! Would this mean my phone is analogous to Google Store version and I don't have to worry about Visible interacting with it in any way?

View attachment 5900273
[Google Pixel 7] bobby janow:
Where did you get the device? It looks like it was Fi which would mean no one can lock it.
[Google Pixel 7] eksitus:
Bought it from the Visible store, as they offered a massive discount ($600 -> $400) for certain users who needed to upgrade the phone to use their new network (which was a lie, but the discount was too good to pass).
[Google Pixel 7] manjaroid:
I think you have the unlocked variant like mine but if you customize I don't know what you can expect with Visible's SIM on Verizon's network.
[Google Pixel 7] bobby janow:
It will mean nothing. I have an unlocked Google device and I put the Verizon sim in at the start of setup. OEM unlock will always be active no matter what I do or which carrier I ever decide to go with.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Deleted member 10744851:
About LineageOS

LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.

LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

FULL CREDIT GOES TO @K9100ii AND @html6405 FOR THEIR SOURCE CODE.

NOTE:

This is the first time I'm building a ROM. Similarly to lallolu's LineageOS 18.1 it was intended for personal use, but I decided to share it since it was stable.

What's working:

RIL (Calls, SMS, Data)

Wi-Fi

Bluetooth

NFC

Camera

Video Recording

Video Playback

Audio

Sensors

Flash

GPS

Vibration

WiFi Hotspot

SeLinux enforcing

What's not working:

VoLTE (won't fix)

You tell me

Flashing Instructions:

Copy Lineage zip to phone.

(Optional) Copy OpenGapps to the phone.

Boot to TWRP

Go to Wipe -> Advanced wipe -> select Dalvik, Cache, System, Data and Internal Storage

Go back to Wipe -> Format data -> yes

Tap Install -> Select LineageOS zip (and optionally, gapps)

Swipe to flash

Reboot system now

First boot might take a while

Downloads:

Latest: [REMOVED]

Previous: [REMOVED]

Recovery: TWRP (If 3.7.0 doesn't work, use 3.6.2!)

(Optional):

OpenGapps 12.1

Sources:

https://github.com/LineageOS

https://github.com/Radplay/android_device_samsung_s5neolte

https://github.com/Radplay/android_device_samsung_universal7580-common

https://github.com/TALUAtGitHub/android_kernel_samsung_universal7580

XDADevDB Information

[ROM][UNOFFICIAL][s5neolte][SM-G903F][12.1] LineageOS 19.1, ROM for the Samsung Galaxy S5 Neo

Credits:

LineageOS-UL

TALUAtXDA

html6405

ROM OS Version: Android 12L

ROM Kernel: Linux 3.10.x

Based On: LineageOS

Version Information

Status: Testing

Created 2023-04-29

Last Updated 2023-05-09
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Deleted member 10744851:
Changelog:

09.05.2023:

- May security patch

- Updated LineageOS sources

- Switched to Jemalloc for better performance

29.04.2023:

- Initial release
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Deleted member 10744851:
Reserved
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] vlad3647:
So far so good,thanks
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ziolko00:
good job
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Neoony:
Any chance of upgrading from 18.1 without losing data?

Migration patch? (I do have the one from 17.1 to 18.1, not sure if the same one would work)
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Deleted member 10744851:
Assuming you got 18.1 from here, it should be as simple as flashing 19.1 (and gapps) in TWRP. I tried it myself and it worked fine, but you should take a backup just in case.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Neoony:
Yep, flashing 19.1 and gapps

Checked if it boots, booted

Flash magisk

Everything works

Big change in UI :D

Thanks for the ROM!
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Neoony:
Not 100% sure yet, but it seems that I am also not losing 5Ghz wifi after the phone is idle (then I would have to go airplane mode for few seconds and back to connect again / or sometimes disabling and enabling wifi would work)

I had that problem with all previous Lineage versions for this phone

https://xdaforums.com/t/rom-unofficial-s5neolte-sm-g903f-10-0-lineageos-17-1.4082017/post-83974647

Didnt happen yet, I hope it stays

Was quite annoying with no good way to only stop this phone from using 5Ghz (without completely disabling 5Ghz on router)

I will keep an eye on it
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] blob101:
Well done Radplay. I was hoping that someone was going to have a go at porting 19.1 and this first build looks great.

If you are open to suggestions, the recording and in call mic volume seems a bit lower than the stock rom. I also couldn't get the in call speaker phone mic to pick my voice up normally.

Thank you for making this ROM available!
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] przemo_one:
Does WiFi tethering work over 5Ghz?

:edit

it should, don't know for sure because i'm testing previous version 18.1 and it does
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ccomoo:
Thank you for the ROM. During calls, I have an issue where the sound button doesn't work, and the person I'm calling can hear themselves slightly, like an echo."
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ziolko00:
W rzeczywistości przycisk głośności nie działa
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Neoony:
Volume buttons work fine for me

I guess it must be hardware?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Neoony:
Also, pretty sure this is fixed, never happened since 19.1

Well done, Thanks!
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ziolko00:
for me, visually too, and in fact they do not quieten down
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] ccomoo:
For me, the volume button doesn't work only during phone calls
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Beta123MAX:
Thanks for publishing your work!

I've got a little suggestion. As far as I've noticed, mount zram with discard flag commit is missing:

universal7580: mount zram with discard flag · LineageOS/android_device_samsung_universal7580-common@1a97047

Change-Id: Id89a8c27749f6caca31a524504d68bf0f80cb98a

github.com
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Deleted member 10744851:
I'll look into it. ZRAM is set up differently in the tree I forked than it is on the official LineageOS one, if it performs better than the current setup I'll ship it in the June build.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] 0157horst:
i'am from germany i need volte am i right?;)
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] :
If your carrier discontinued 3G then yes.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] 0157horst:
ok that is not good cause the whole country got no more 3g ...

is there no chance for fix volte?
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] :
Nope. As of right now it's not possible to get VoLTE working on a custom rom on any Samsung device.
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Shisco:
I'm facing a problem with non-functioning GPS. Originally I used the phone without MicroG, nothing changed after installing it. Location is still dead as a dodo :/
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] :
Can't reproduce. Location/GPS works fine on my s5neolte (LineageOS 19.1 + OpenGapps 12.1).
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] Neoony:
Does anyone else have random crashes and/or slowdowns?

I mean, I have not reset data for a very very long time, over multiple LineageOS versions.

( I just have so many things set up, would be pain to start new, some auth apps I could only transfer to new phone with QR, not possible after data wipe, but now they added account sync, eventually I will have to do some reset xD )

So I am always assuming it might be that I have collected a lot of mess and should reset data.

However I have never had crashes on previous LineageOS versions, only slow downs and terrible battery. [or very rare crashes] (also every other restart basically drops the battery down 10-20%)

e.g. yesterday the phone just decided to keep restarting every few minutes after every reboot, while using poweramp and headphones. Pulling battery didnt change much. But then later, not trying to listen to music, its suddenly fine.

Also the slowdowns I have seem to be fine after flashing and wiping cache and dalvik, they get worse after a while until I would wipe cache and dalvik again, and then fine for a while. (not sure what could this mean)

My battery cant really last 1 day. (there was never any difference when I bought new one on some older Lineage OS)

I dont really expect some kind of fix, I should just reset data and see what that changes.

(I think a lot of it is probably because of the mess on my phone, I dont have a lot of apps right now, but did a lot of stuff on the phone in the past)

But just want to ask, how is the performance and battery and crashes to anyone else on lineage-19.1-20230509-UNOFFICIAL-s5neolte ?

Note: lineage-19.1-20230509-UNOFFICIAL-s5neolte is better than the previous one, on the previous one I had many more issues with a lot worse slowdowns.

EDIT: Really not sure what happened, I basically get almost nonstop crashes now, reflashing LineageOS+gapps not helping. Weird, didnt change anything

Plug it in to charge it, works fine, unplug it and unlock phone, crash..keep it plugged, works fine

Didnt have this few days ago

EDIT2: Data reset not helping either, as soon as I unplug the phone, it crashes, plug it in, it stops crashing. Flashed previous build, same.

I guess something else is wrong here ( Maybe its time for a new phone anyways xD )

In recovery everything is fine though

EDIT3: I also get random reboots on my april backup from 18.1, a bit less. somehow I can get the phone up while its charging, but barely, so maybe battery had enough...unplug, crash (percentage shows fine though)

Phone was really hot at some of the slowdowns/freezes I had recently, maybe that hit the battery

Getting that new phone, I wanted to do that for a while anyways :D (especially if I had to start with wipe anyways)

It was an honor S5 Neo! 🤜🤛

And thanks for anyone supporting with LineageOS/custom ROMs
[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] K9100ii:
I'm fairly disappointed with my work is being used in its entirety here and credit isn't being very prominently displayed. I only found out rather recently.

This is entirely the work I did initially for personal use, with some admittedly random meaningless changes on top.

I was myself planning to start maintaining unofficial 19.1 builds for this phone, but unfortunately, my phone's display stopped working and so I could never go through with such plans. Only usable with scrcpy and ADB enabled on boot for now. I'm going to get a new display soon.

Anyway, here's two bugs the overly simple "What's not working" section doesn't have, and I found myself through extensive testing:

If you enable airplane mode after having it disabled, the cellular modem will not actually be disabled. In the SIM status info in settings, it won't say "Radio off" in whichever section.

This means that the modem would still be active, and draining the battery.

If rebooting with airplane mode enabled, the modem does seem to stay disabled.

I couldn't figure out any fix or workaround for this.

The headphone jack has some distortion (with some audio content) at maximum volume.

I know a workaround for this, but am reluctant to share it.

Not sure if I'll be motivated to publicly maintain any further when I do get a new display. Hmm.

In any case, you're all welcome, I suppose....