yashsingh1/xdaforums huggingface dataset:
[LG V30 Questions & Answers] Zoki88:
Yes i'm aware for wifi not being consistent and all those factors affecting on wifi, in fact today was suprisingly stable 150-160 speed, but i can still see there's definitely some problem when is showed 433Mbps in settings instead of 866 like was earlier at same distance from router, and on tp site settings too for Tx/Rx rate being weird like said in text and showed on screenshots. In fact only my device from all other devices home have weird proportion to Rx(recieve) be bigger than Tx(transmit) and to showing Rx to be those "max" 433 which is wrong

I'm thinking that maybe having Europe OS in Asian device have to do something with that wifi modem problem, maybe i'm wrong, so not advicing anyone to toggling OTA settings. I'll still wait before i try that complete wiping out phone(not even factory reset), or will let it be, still undecidable for that, but thx for help, any help really appreciated!
[LG V30 Questions & Answers] schwinn8:
Again, those readings are not very important and will vary often. Those are theoretical values based on the connection type. In the end, the actual speed you get is really all that matters. For example, my laptop is showing up in my router at speeds like 706, 702, and then suddenly 585. Sometimes it will show 866/6 as well... so a very asymmetric reading is possible. And I'm sitting about 10-feet with clear LOS to my router.

It's not meaningful to worry about those numbers. Unless you're having an actual speed problem, it's not worth worrying about those. There are way too many things that can affect those values (dynamic frequency changes in the router or the device, interference, power management things, etc... there's a TON going on behind the scenes. Just because your device or router says it's on that number for a moment doesn't mean that it won't ramp up when there is a need to do so (or ramp down when there isn't).

EDIT, there's a nice long explanation about the tech here, if you're interested: https://www.duckware.com/tech/wifi-in-the-us.html
[LG V30 Questions & Answers] Zoki88:
S

Didn't read all from that site, but i saw for MIMO thing, and my phone(snap 835 specs says it) support that 2x2 MIMO with speed up to 866, but looks like you were right, not related to those showed numbers, i was getting good speeds of wifi. I still just now refurbished whole phone as i saw that battery is draining drastically faster after i messed up that wifi showing numbers, now when i put actual h930ds firmware in it(early oreo), and connected to wifi, i checked and saw those 866Mbps, so that thing is fixed, but not just that, i also saw in tethering hotspot that i now have option to choose 5GHz which wasn't there, from where i started all this mess at all. Now planned to put Europe H930 OS latest oreo back again to see if maybe that different OS have to do something with that not showing up 5GHz hotspot option, and on top of everything: to hope that battery was draining faster because of that wifi problem and not because of battery itself, as i have phone now for more than 3 years, which works like 1st day. Will tell results
[LG V30 Questions & Answers] schwinn8:
Excellent, glad you got it figured out and back to working normally! Sorry I couldn't be of more help for actual steps, but you got it done, so great job!
[LG V30 Questions & Answers] Zoki88:
You did help actually, as that site seems one of those rare ones which goes deep in explaining all about those connection stuffs for people like me who don't understand that much about it in details, and with today's standards with phones connections with reality of scores using WiFiAnalyzer and not some marketing bs, even if i didn't read all, i will as saw how well are explained and done tests, and also helped to realise that numbers showings don't seems to be reliable much(when it comes to those numbers from settings unlike on speedtest app). Also i just now refurbished phone again on that latest Europe Oreo OS, and seems like there's no 5GHz option available in hotspot, so to all people wondering about not having 5GHz tethering hotspot on their LG V30, it's because Europe restricted it (H930 Oreo OS, i don't know if that's case with Pie), it gives max wifi 4 n standard(again checked on laptop in properties for connected wifi hotspot from phone), it's same thing for recording fm radio, as on Europe OS there's not available that red button for recording it, while on Asian one there is on bottom right side. I'm thinking if i should use original H930DS Asian OS even if i'm in Europe, but i didn't see any benefits or downfalls when it comes to carriers here(didn't much travel to check for other countries in Europe, talking for my place), as it works for both OS everything, and can still have VoLTE i think? Will everything works fine in any Europe country carriers and stuffs? Or is there maybe bypassing this issue to get 5GHz hotspot on Europe OS by changing wifi settings launcher like appearing recording button on fm radio app is solved like that?
[LG V30 Questions & Answers] schwinn8:
Glad that link helped. Yes, Wifi is rather complicated and the numbers we see on boxes and devices is rarely realistic or even attainable.

Beyond that, Wifi also has other issues... it's a nice system when it works, but it has a lot of issues in crowded areas. Here's an older article which talks about why Wifi kinda sucks, in general: https://arstechnica.com/information...hat-a-deep-dive-into-why-wi-fi-kind-of-sucks/

The key message there is that Wifi is shared, so if the router or device sees another device on the same channel, then it may be forced to wait, thereby reducing the bandwidth you'll see. A lot of people don't realize that. Heck, in the older days, wifi would only run as fast as the slowest device... which was even worse!

Again, glad to hear you're working well. Interesting that the 5GHz is not available on the European OS. I don't know enough about that situation, so I won't be able to help there. Generally speaking, I would recommend seeing if you an use the US998 firmware, which is the USA "Global phone" ROM... this works well in the US on any carrier, but may also work well on foreign carriers. I expect hotspot 5GHz would work as well.

I don't know about VOLTE in foreign markets. I know that in some cases that doesn't work in the USA (AT&T is one carrier who is awful about this). In other carriers, you sometimes just need to use their ROM - that's what I did for my Verizon-based carrier (I used VS996 instead of US998). For your case, you may need to ask others or read here to see Europe-specific info. I'd love to see what you find, just for my info... I'm always curious!
[LG V30 Questions & Answers] Zoki88:
Here i am again with update, after restoring everything 3 days ago, i'm very happy about my whole phone, battery is excellent, wifi always being much more speed than i ever had earlier, carrier's 4g mobile data sign was appearing right away instead of waiting 5 sec or so. I'm writing this update to let people know that looks like you need to choose between performance of modem from phone(wifi and carrier network), and having VoLTE, as yesterday i changed carrier package which have VoLTE, and i didn't get it, neither can enable it using this very helpful tutorial, as i'm missing lot of files that Europe OS have: https://xdaforums.com/t/module-v17-x-volte-vowifi-enabler-2018-09-20.3649613/ , i'll maybe try to include those missing system files in my Asian OS even if they belong to Europe OS so to try enable VoLTE that way, if that doesn't work, then i won't have it, as for me is more important wifi speed. Main problem here is to get IMS service be registered with Europe carrier on Asian OS, even if i see that there are indeed ims files available on Asian OS, so that maybe tells something, maybe someone find some workaround.

Edit: there's no way to enable or make work lg ims service on that specific AME OS for some reason, i just now (again) put Europe OS as want to see if i can have VoLTE at all, so don't mind me switching OS 😂, but yes, i tested wifi, it's indeed reduced speed with that OS than original one.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cooleydoo22:
I have extracted pixelos payload. bin image to extract the ram disk and kernel, however in AK I'm getting the error kernel offset (page size is 0) every boot image from firmware I know works perfectly fine get this error it doesn't matter where its a muiu global eu image or pixelos i get the same error , I have used these roms before and the booti.img files to flash through twrp no problem at all doesn't make any logical sense to me
[RED Hydrogen One Questions & Answers] Oswald Boelcke:
@jazz4sale Thread closed as duplicate of

https://xdaforums.com/t/hydrogen-one-password-issue.4420727/

and moved from the development section to Q&A as the thread didn't qualify for the first one. The still open thread has been moved from "GND" to Q&A.

Prior to your next posting, please read the guidances and announcements that are stuck at the top of every forum and review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Realme C2] Syntax.(Y):
Does anyone use dac dongle on realme c2? Someone had realme c15 or something like that, he want to use dac dongle, with positioning

Dac dongle (usb type c) > usb c to usb a > usb a to micro usb

And it doesn't work, just in case i ask for my phone too, there's someone said the OTG in realme phone doesn't support with the dongle dac

Btw, Thanks in advance
[Tilt, TyTN II, MDA Vario III General] loly2002:
Dear all,

thank you so much for your previous help i really appreciate it

i have a new problem now :( (sorry for that)

the problem is that i upgraded my tytn II (KAIS100) only back camera,

to Rom: 3.28.405.0 WWE and Hard SPL-3.29

Radio: 1.65.17.56

Protocol version: 25.83.40.02H

and now when i make a video call i see only the other person and my picture is just blank and the back camera is not working

and i have a friend of mine have the same phone and same ROM and he can make video calls and the other person can see him by the back camera

so any help or suggestions i will be very thankfull :)
[Tilt, TyTN II, MDA Vario III General] whitehooptie:
Change the radio.....
[Tilt, TyTN II, MDA Vario III General] loly2002:
can you tell me the best radio

and is there any risk to lose data or anything on the phone after changing?
[Tilt, TyTN II, MDA Vario III General] whitehooptie:
Well, you're about to get lit up in this place. Do a search for "The Ultimate Radio Thread". It is somewhere in the ROM section of Kaiser. There has quite a few radios for download. The best one is personal preference. Some will work for you, some won't. Depends on the ROM you're running. Just search, search, search!

And no, no danger. Only bad things, if they are incompatible, no sound, no camera, stuff like that.
[Tilt, TyTN II, MDA Vario III General] loly2002:
Dear all,

thank you so much for your previous help i really appreciate it

i have a new problem now (sorry for that)

the problem is that i upgraded my tytn II (KAIS100) only back camera,

to Rom: 3.28.405.0 WWE and Hard SPL-3.29

Radio: 1.65.17.56

Protocol version: 25.83.40.02H

and now when i make a video call i see only the other person and my picture is just blank and the back camera is not working

and i have a friend of mine have the same phone and same ROM and he can make video calls and the other person can see him by the back camera

so any help or suggestions i will be very thankful
[Tilt, TyTN II, MDA Vario III General] JimmyMcGee:
Yes, Follow whitehoopti's advise.

My advise, do not ever post your question more than once. Four threads across the Kaiser Forums! That's a no-no. This is your only warning on this. :)

Also, Search for the answer before creating a new thread.

Thread Closed. Please read the Kaiser Section Announcement Guidelines and the Forum Rules.
[Google Pixel 6 Pro] AwkwardUberHero:
Hi all,

My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.

I've contacted T-Mobile. They've given the green light on their end to unlock.

When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."

TMobile is saying there is nothing they can do, and google is telling me the same thing as well.

Any ideas? Just looking to get this device back to Android 12.
[Google Pixel 6 Pro] Alekos:
What device unlock app?

What happens when you:

Connect to wifi.

Enable OEM Unlocking in developer options.

Download latest platform-tools

Run the fastboot command: fastboot flashing unlock
[Google Pixel 6 Pro] LLStarks:
A second hand work phone Pixel 6 Pro that's already on 13. That phone has seen some **** in a very short time.

T-Mobile pushes the unlock to you. If you downloaded the app from the Play store, it's the wrong one. Using the sim unlock one in T-Mobile sim settings also doesn't seem to work.
[Google Pixel 6 Pro] AwkwardUberHero:
It's connected to WiFi, but the oem unlocking item is greyed out.

I haven't tested running the command in fastboot yet. Was worried what would happen.
[Google Pixel 6 Pro] AwkwardUberHero:
They asked me to download the device unlock app from the app store. I did, and used it.

They said that they have approved the unlock on their end.

I'm quite confused. This is my first carrier locked pixel.
[Google Pixel 6 Pro] Morgrain:
If you get a second hand phone from work that has experimental beta software installed from a previous owner, which is clearly a massive issue for a work phone in several regards (security just one) why don't you just give it back and demand a new one? Not sure how your company acts, but mine would instantly seize that phone, there is not knowing what might have been installed on it, it might even be a non-genuine A13 build. It's simply a risk most companies would never take, at least if they have some credibility.

This is clearly not your problem to deal with. It's noble that you invest so much of your "free" time for this, but it's a waste of time imho. It's not your job to make that phone work properly. If it's not in a working, proper state at the moment of delivery from employer to employee, you need to demand a working model.
[Google Pixel 6 Pro] Alekos:
If it's greyed out, the Bootloader is still locked. You'll need to contact them (either through your work or TForce) in order for them to unlock it. But corporate devices (from T-mobile) might have different policies on unlocking. Best to contact your IT Dept.

But as the @Morgrain has suggested, this phone should have been wiped and factory reset by your employer to a proper working state. It wasn't. That's concerning. Many of us have worked for companies who are, shall we say, less than competent, at IT. But it's 2022 - there's no excuse.
[Google Pixel 6 Pro] AwkwardUberHero:
I was going to give it one last shot before trading it back in. TMobile said that they have set it to be unlocked on their end, and that factory resetting it and checking it again to see if the bootloader is allowed to be unlocked might be a solution.

I've flashed roms, rooted and such for many years, but I've never had one like this. If TMobile did flip the switch in their end for the permission to unlock the bootloader, then it should show this, even in a developer preview software build, right?

I doubt that factory resetting this and trying it again will do any good, but I guess it's worth a shot.
[Google Pixel 6 Pro] LLStarks:
Don't use the play store app. It doesn't work. The phone has a built in app. It doesn't work either.

The unlock doesn't need to be approved. It has to be pushed to your phone. Your phone will alert you that it's unlocked without doing anything. T-Mobile cannot be the one telling you it's unlocked. After that, you reboot and bootloader unlock should no longer be grayed out

You got a bad rep who doesn't know what they are doing.

Your IT also had no business giving you a phone this compromised.
[Google Pixel 6 Pro] roirraW "edor" ehT:
To be clear - T-Mobile wouldn't unlock your bootloader or be able to toggle the OEM unlocking themselves, they would only make your phone carrier unlocked. It just so happens that on T-Mobile devices (and maybe some others but definitely not Verizon), that carrier-unlocking a phone permanently usually also makes it so that you can toggle OEM unlocking. It's also possible that corporate management of your phone prevents it from ever having the OEM Unlock toggle be ungrayed, but on the other hand, I would think they would have it locked down to where someone can't opt the phone into a Beta program, and it's also strange that T-Mobile would do, or attempt to do anything regarding the phone since you don't own it or pay for the phone service.

As several have said, it's not your phone, it's not your responsibility, I wouldn't even think your work would want you to be messing with it even though you're capable.

I would also add that unless your work has the capability to make their phones have OEM Unlocking ungrayed out, and re-grayed out at will, they'd never be able to fix the Android 13 DP/Beta situation themselves - they would have to go to T-Mobile et cetera, although after they fix it, I would expect them to want to toggle it back and make it so that no one else can toggle it again. I guess your work just doesn't manage their associate's phones very closely.
[Google Pixel 6 Pro] AwkwardUberHero:
So, they approved the carrier unlock.

The app does that part. I've done that a few times. But, the oem unlock is still greyed out.
[Google Pixel 6 Pro] 96carboard:
Yes and no. Not everybody works for high security big bank or government. Depends on the employer and depends on the job for the employer.

One piece of good news is that it is VERY unlikely that its a non-original A13. After all, its locked still. That means that the build had to be signed by the appropriate keys in order to install.
[Google Pixel 6 Pro] AwkwardUberHero:
So, TMobile said for me to down load the device unlock app. I did that, and ran it. It told me it was carrier unlocked.

The OEM unlocking portion is greyed out in develope options though still, and saying to connect to the internet or contact my carrier. Which confuses me. If it's sim unlocked, then I should be able to unlock the bootloader, right?
[Google Pixel 6 Pro] roirraW "edor" ehT:
As I said, your work may have more control over your phone since it's their phone, not yours. They may have something in place that keeps OEM Unlocking disabled, no matter what. I'm just speculating, I don't know if that's the case. I really couldn't guess any further why it's still grayed out for you. I wouldn't even bother spending any further effort on it. If it happened to me, I would tell work about it and let them deal with it.
[Google Pixel 6 Pro] LLStarks:
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.

Then again, so does Apple and Intune not being thorough enough.
[Google Pixel 6 Pro] AwkwardUberHero:
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?

Last attempt before I give up on it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I know with regards to non-phone Google things at the very large corporation I'm at - where we've used Google for everything (except for phones) for a decade - that some things that are under the control of our internal Google Admins in our IT department slip through and then later get corrected.

As regards to phones, I don't have a corporate phone, but they used to supply some Samsung models for a brief period where they experimented with allowing both iPhone and Android devices, but they stopped probably because it was just more work for them to manage both iPhone and Android devices. I can't speak as to whether they had the capability to keep people from unlocking their bootloader or keep folks from opting in to DPs/Betas, but that was also ~6 years ago.

If you can't toggle the OEM Unlocking (it's still grayed out), then you can't unlock the bootloader.
[Google Pixel 6 Pro] NippleSauce:
I mean, this kinda depends on whom you work for. Some companies that give out work phones choose Android as they can customize the build and can view the phone's usage. I can't remember if it was the FBI or the police somewhere who mentioned doing this exact thing in order to visibly track what is being done on these phones. So if your company is knowledgeable (which I suppose is a rarity nowadays, haha) and deals with some information that must be kept secure, then I would just confront someone in the IT department and ask them what the deal is "as the phone isn't running a stable and secure version of Android". Because if it's customized for phone usage tracking, then doing what you are doing could get you into some trouble.

Not worth taking such risks with something that isn't yours. Where I work in IT, people always mess with (and too frequently break) devices that they are borrowing - and then complain about having to pay $250 for cracking the display or destroying the case of a laptop that they are simply

borrowing

.

It seems that nobody reads the contracts that they are signing or has enough common sense to not destroy something that isn't theirs.
[Google Pixel 6 Pro] Alekos:
To be fair, I would do anything and everything to unlock the device because I like messing with technology (even if it comes from work).

The Toggle is greyed out right - but is it on or off - because when the device is unlocked, the toggle will be greyed out (but toggled to the on position). When you boot into fastboot, does it say device state locked?

Do a factory reset in recovery mode and check again.
[Google Pixel 6 Pro] AwkwardUberHero:
It's greyed out and off.

I haven't checked it in fastboot yet.
[Google Pixel 6 Pro] Alekos:
it varies by company. The companies I worked for, they didn't require employees to pay for broken devices unless it was a blatant disregard of policy (and even then, I've never seen an employee pay for a broken device).

But the terms vary. Larger companies have the ability to go through a lot of phones and have decent contracts with carriers regarding warranty and insurance.
[Google Pixel 6 Pro] Alekos:
ok, if it's toggled off then the unlock still hasn't been processed on the phone. Sounds like the MDM rules are blocking it from being unlocked.

Do you have an MDM running on the phone, like Lookout or Duo? That could be preventing it from being unlocked. Have you tried wiping the phone in recovery mode? Are you in contact with TForce (they usually offer better support than regular customer service)?
[Google Pixel 6 Pro] XRaiderV18:
may I suggest, as a layman here, that you reach out to your company's IT, explain whats wrong and what you're looking to do? either they'll help you out, do it for you or tell you very firmly 'dont do that'. but you've nothing to lose by asking.
[Google Pixel 6 Pro] opz187:
This seems obvious but you've already factory reset from recovery since receiving the unlock?
[OnePlus 8 Questions & Answers] KLit75:
I noticed the OXYGEN UPDATER APP now has Android 12 available to install but it hasn't quite made it to the official update in the settings. Just wondering if anyone has tried this update and whether you experienced or heard of any bugs?

I have no reason to think there is but Ive literally heard nothing good, bad or neutral. It's like no one owns this phone anymore. An update like this used to be noteworthy. That said, if anyone reads this and you have info, please share. Thanks
[OnePlus 8 Questions & Answers] uacyber:
I have updated my device today and one thing I have noticed the most is that volume levels after the update are much lower than they were. I cannot use normally my earphones indoors and cannot image how bad it will perform outdoors.

Would be grateful if someone knows how to fix such problem.