yashsingh1/xdaforums huggingface dataset:
[Google Pixel Fold] LukeSeesThrough:
Haha fair enough!
[Google Pixel Fold] blackhawk:
Meh, oddball display format. You ever use a square monitor?

Part of the major failures of both Google and especially Samsung was lack of software innovation for the Fold format for years running now. That derailed the rollout splash in a huge way. Empty space is wasted real estate.
[Samsung Galaxy Tab A series Questions & Answers] System23:
Hi,

I have become a new Device in my hands SM-T295 and it was on latest Firmware BKD, so every Option thats in the Forum are not Work every time the same SECURE CHECK FAILED!!!

So i have Test it out 4 Hours and no Luck!!!

The last hope i have is a GSI ROM that i convert in sparse and create a tar.md5 to Flash it in Odin so like my SM-T510!!!

All Fine at this Step but when i would Flash it, Odin make a ERROR unsingned File!!

Now the Question has everyone Knowledge about how to signing the system.img so that Odin it accept?

than i have modifiy a older Firmware system.img.ext4 after i convert it to RAW with HeXEdit and override the Signed entrys with Zeros, works Fine in Flash with Odin!!!

But the Problem is there that the Boot.img not works and Flash the correct Boot.img SECURE CHECK FAILED!!!

So the Ideer Download a GSI thats Compactible with Android 11 Stock Boot and Signing it ,create a tar.md5 and Flash it via Odin, to have a CustomROM on SM-T295!!!

MFG
[Moto G 5G Plus ROMs, Kernels, Recoveries, & Other ] ku47:
Hello everyone,

I have Motorola moto g 5G plus, LineageOS 20 is currently cunning on it and I now like to install LineageOS for microG.

When I installed LineageOS 20, I followed LineageOS wiki page (https://wiki.lineageos.org/devices/nairo/install/variant1) and needed following 3 files.

- recovery.img

- copy-partitions-(xxxxxxxx)-signed.zip

- lineage-20.0-(xxxxxxxx)-nightly-nairo-signed.zip

On LineageOS for microG download page for this model (https://download.lineage.microg.org/nairo/)

There are 3 files

- lineage-20.0-(xxxxxxxx)-microG-nairo-boot.img

- lineage-20.0-(xxxxxxxx)-microG-nairo-recovery.img

- lineage-20.0-(xxxxxxxx)-microG-nairo.zip

I'm a bit confused and just wondering if anyone can clarify how I use boot.img file and also if I need to use copy-partitions.zip file from LineageOS?

Thank you in advance.
[Moto G 5G Plus ROMs, Kernels, Recoveries, & Other ] khusika:
Hi @ku47

LineageOS for microG is an unofficial fork of LineageOS which mean you can follow installation instruction trough their main page instead of from Official LineageOS wiki page.

For your information, make sure that lineage-20.0-(xxxxxxxx)-nightly-nairo-signed.zip contains boot.img. The recovery.img is usually used by OTA updater, you can install it if you want to do update with OTA updater.
[Moto G 5G Plus ROMs, Kernels, Recoveries, & Other ] ku47:
Hi @khusika

Thank you so much for you reply. I totally misunderstood at the start. It worked well this time.
[Galaxy Tab S2 Android Development] thefanum:
Release notes

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

June 23, 2023

1. Initial 20 ALPHA public release.

2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"

3. If you are coming from stock rom or an older LineageOS version (example, 18.1), you MUST format your data in TWRP. Remember to backup your data and verify that restore data works before upgrading to 20.
[Galaxy Tab S2 Android Development] thefanum:
ZRAM EDITION RELEASE NOTES:

After extensive testing and benchmarking, the ZRAM version seems to offer everything the original does, but with better multitasking capabilities and it launches at least one application that has a 4gb RAM minimum requirement, that won't even open on the original release (this tablet has 3gb RAM).

I'm going to recommend people try the ZRAM version by default, moving forward. Until something comes up to change my mind, this seems like an upgrade across the board.
[Galaxy Tab S2 Android Development] GmanGrout:
Thanks for the rom works perfectly apart from Bluetooth any ideas? Followed all the steps...
[Galaxy Tab S2 Android Development] thefanum:
Interesting, let me test on my devices and I'll report back
[Galaxy Tab S2 Android Development] GmanGrout:
Thanks! I tried with and without gapps.

Also tried los 17.1 and the Bluetooth was working.
[Galaxy Tab S2 Android Development] prkfsz:
Firstly, a huge thank you to the developer! This was really good news that this little device will get extended life. :)

The rom itself looks nice and fluent. I did however come accross several problems:

- i flashed the image file of the right version of the TWRP from within older version of the TWRP. While flashing rom, i got error 7. Then I flashed the TWRP (tar) from Odin and the install of the rom was a success. I know it may very well be the case of a bad download, but I am writing this in case someone else encounters this one.

- i can't get gesture navigation to work properly, despite trying several times. Only the swipe upwards (access open apps) is working.

- i can't get a GPS lock. Am using OSMAnd software. Tried the GPS test app but it can't find anything.
[Galaxy Tab S2 Android Development] thefanum:
Thank you! And thank you for the feedback. The good news is I can confirm gesture navigation does work, I've tested it on both of my tablets on this ROM, and I've been using them on one of them since the beginning, with zero issues.

I can also confirm that gps can work, as it's working on one of my tablets, and I'll double check on the other.

Do me a favor and try the following, let me know if it fixes these issues:

1. Back up apps and data

2. Boot into TWRP, advanced wipe (make sure files are not on internal), format data, advanced wipe, wipe everything except SD and USB.

3. Flash ROM, Flash Gapps (if needed), flash magisk (if you want it). Make sure to flash them all without rebooting or rebooting recovery (this fixed the gapps permission issue for me).

Please report back the following:

A. If gapps /play store all work out of the box (without having to adjust the permissions manually)

B. If gestures now work

C. If GPS now works. If not, check that your maps app have location permissions, and if not enable them and test again.

I've also found the source of the Bluetooth issue (actually retiredtab did, so all credit goes to him for that one), and I'm going to try and build a new version with the Bluetooth fix and new security patches. But it would be nice to know if these need to be address before hand. Please and thank you.
[Galaxy Tab S2 Android Development] thefanum:
I have confirmed this bug, and I should have it fixed by the next release.

Thanks for bringing it to my attention. I never use Bluetooth with this tablet.
[Galaxy Tab S2 Android Development] GmanGrout:
Thanks very much mate for keeping this great tablet alive 🙏 look forward to the update to address the Bluetooth issue 👏👏👏
[Galaxy Tab S2 Android Development] friedsonjm:
Up and running like a charm! Thanks!
[Galaxy Tab S2 Android Development] finalista:
I reinstalled stock to update the FW to the latest version. then followed the instructions given. everything is working as expected and out of the box ( gestures, gps, gapps ) besides bluetooth ( will be fixed in the next release ). @thefanum well done! thank you very much for bringing los 20 to this "old" tablet - very appreciated! unfortunately all new android tablets have displays with at least 10" - I'm really missing something like the ipad mini for android :(
[Galaxy Tab S2 Android Development] BhNeP:
This ROM is as smooth as butter on my T713. And way gentler on my battery than the latest LOS 17.1 builds. Gesture navigation is also working.

Thanks so much for sharing such a mature alpha!
[Galaxy Tab S2 Android Development] thefanum:
Well that's fantastic news! One thing I've learned over the years of running LOS, and Cyanogen before that, is that if a ROM works for everyone except you, flashing the newest stock rom, and starting from scratch is usually the solution.

And thank you for the time you put into troubleshooting this, and reporting back with detailed feedback. It makes my job SOOOO much easier.

As for the actual bugs, I'm hoping to have some time this weekend to fix the Bluetooth bug, and update to the newest security patches.

I've also decided against automating my builds, as I was previously thinking about doing (and may have mentioned). After a good discussion with u/retiredtab , he's explained to me that it's just not worth the trade off. The convenience is nice to have, but when things randomly break on the user, it means a less reliable OS. And I've decided to follow his advice, do updated builds manually when I have the time (and when there's a reason, security updates, bugs to fix, etc). So I just wanted to fill you guys in on the change of plans, and the logic behind it. When in doubt, I defer to the experts. And in this case, that's retiredtab.

That being said, assuming I have the time (and I probably will *figures crossed*), I'm aiming to update the security patches quarterly, so we should have an update every 3 months or so. And I'll address any bugs we find along the way in those updates (unless there is a major bug, I'll try to address those faster). And with the 4 releases a year, we will have the added benefit that they will be thoroughly tested, and hopefully, fully functional.

So I do apologize for getting people's hopes up about the automated builds, but I do think the end result will be a higher quality user experience, which is as secure as you can expect of a device of this age.

And while automated builds are off the agenda, I will still look into seeing if I can get OTA updates functional, without the LineageOS infrastructure. It would be nice to be able to get those quarterly updates via the settings app. No idea if I'll be successful, but that is on my to-do list currently.

And I totally agree. I've bought 5-6 different tablets, all different models, since this one was discontinued. And in trying to find anything that comes close to this quality, in this form factor, I've determined they just don't exist. And haven't for years. Which is a shame. But it's also what motivated me to get better at programming, so that I could help bring my favorite tablet back to life. So at least there's silver lining lol.

And again, a huge thanks to Retiredtab, the entire LineageOS team, the LineageOS UL team, and all the Android devs. I truly could not have done this without them.
[Galaxy Tab S2 Android Development] thefanum:
That's great to hear! And you're very welcome. I was wondering if it was a fluke that my battery life had improved dramatically, coming from the unofficial 17.1 build also. I also think I might have slightly better battery than even the official LOS 16 builds, although that might be anecdotal, as I haven't done any actual diagnostics.

Either way, I'm glad everyone else is getting that extra juice too! Lord knows we can use every drop, with batteries of this age lol
[Galaxy Tab S2 Android Development] retiredtab:
Getting better battery life in my LineageOS 18.1 T813 and LineageOS 20 T813 (and thus LineageOS 20 T713) is by no accident.

Builds that are automated and don't have someone checking the rom for functionality or crashing processes in the logs are going to have worse battery life. The crashing processes prevent proper suspend/deep sleep which leads to poor battery life or dead devices in the morning because it crashed overnight.

In developing LineageOS 20 msm8916 from Dec 2022 to June 2023, 3 out of the 6 monthly security patches or changes in LineageOS/AOSP broke the functionality of msm8916 devices. If my builds were automated and blindly uploaded without me checking them, 3 out of those 6 builds wouldn't be working properly.
[Galaxy Tab S2 Android Development] starvays:
After seeing the positive comments, I've also decided to give this ROM a try. I'll be installing it on my stock 713. I'll see you after using it for a few days.
[Galaxy Tab S2 Android Development] finalista:
@thefanum could you give us a short update about your timeline for the bluetooth bugfix? thx
[Galaxy Tab S2 Android Development] ronnz98:
Great work guys! Are there build instructions for T713 also available?
[Touch Diamond, MDA Compact IV ROM Development] marius81:
I've made a back-up with Sprite Backup on Vic's 3.0 LT ROM. After that I flashed my Diamond with Dutty's 3.6 ROM and restored the old back-up made earlier with Sprite Backup. After soft reset my phone stops at first image (where it shows the radio version, the ROM version...)

Please!, can anyone help?
[Touch Diamond, MDA Compact IV ROM Development] cyron_at:
Do a hard-reset & don't restore the system settings any more!
[Touch Diamond, MDA Compact IV ROM Development] adwinp:
@Marius: Use PPC PIMBackup instead of Sprite. I guess the most important are messages and address book?
[Touch Diamond, MDA Compact IV ROM Development] duttythroy:
As users says please restore only pim information using pimbackup, not recommended to back up system files

Thread closed
[Android Software/Hacking General [Developers Only]] Littlenine:
Guys as you see, a us devices has been unlocked bootloader,which were using v3 keys and certs. If somebody have solution or V3 keys , certs like ATCMD , plz contact me Thanks

Mt tg is @Littleninelst :) good luck to u guys

View attachment 5946201View attachment 5946203
[Windows 11] abhinavsatheesh:
I am running the latest Windows 11 Stable Build 22621.1928

Some features like new Taskbar overflow is still not coming for me. But the new search button has come up. What's the reason?View attachment 5946209View attachment 5946207
[Windows 11] khusika:
Taskbar overflow will automatically transition into this new overflow state when it has hit its maximum capacity and looks like you still has lot of spaces. Look at my taskbar below (22621.1928)

View attachment 5946253
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] unluckysnapdragoncollecto:
Please i've been looking for a long time for a AOSP Google Pixel rom if anyone has a link to one please let me know
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] Manmeet_2008:
Bro you can look for these roms in the phone's custom roms section of xda. If it is not found try contacting any developer to make it available. Currently there are no pixel rom and LOS for this device and I dont think anyone would spend their time on this device as it is too outdated.

Just try using gsi if you want pixelos otherwise several options of other roms are available . GOOD LUCK 👍👍
[Samsung Galaxy J7 (2016 Exynos 7870) ROMs, Kernels] takaki44:
Search for rom here https://t.me/s/Exynos7870Updates?before=1672
[Sony Xperia 5 III] cyn330:
so i have the a103so which mean this the softbank version, unfortunately the softbank phone version only gets 1 os update so it stuck at android 12, so the question is can i flash my phone with global firmware? is it possible even with locked bootloader? because i really want to try out the android 13 since what i saw from the review its got lot of improvement for the phone. might someone answer my curiousity about it, thanks guys
[Touch Pro, Fuze Accessories] nucentury08:
Hey Guys Don't worry I Spoke to a Rep at Expansys About the Rubber Battery Covers They Are getting them Very Soon By jan 9 Htc pulled them Back from Expansys So Expansys is A Great Site to get them And the only Site As Well So guys pre order Them Asap Then they Will Ship to you by Jan 10 or 11th ......:D
[Touch Pro, Fuze Accessories] bpm2000:
here is his email:

Really awesome to hear that orders made 12/11 went out, and my order, placed on 12/7 has yet to ship.
[Touch Pro, Fuze Accessories] bfspider:
Here's an email that I got this morning. I ordered mine when the origional thread with the photos started.

Mod Edit: It is best to not to post names, phone numbers, & email addresses from a personal email onto a tech forum. Please be more considerate in the future.
[Touch Pro, Fuze Accessories] HalcYoN-Fuze:
It will be nice to get one of these from anyone but Expansys.
[Touch Pro, Fuze Accessories] bigriggy63:
Can you please send me a private email with Josh's contact info? I had the same problem with my order, as it came up with the "non-discounted" price when I received my confirmation email.

Thanks in advance!
[FYT Android Head Units] nkl347:
Hi, there. I recently installed an unbranded FYT system on my 2010 G37X with Bose and Navigation. I encountered two issues and how someone could help.

1. When any sound is active (FM, music app, car play, etc.), there will be a white noise coming from the speakers. The noise disappears when the head unit is muted. So instead of a grounding issue, I guess it's the AMP or DSP issue of the head unit. The most likely reason is the AMP in the head unit and the AMP of my car (which comes with Bose speakers) are both working. Because when I change the sound level, it's normal sound when 1/100 and very loud when 5/100. I tried to disable the headunit AMP from [setting->device->sound->AMP ON/OFF]. But there's no difference. I guess it just didn't disable it. Is there a way to force disable AMP?

2. My A/C is not working properly. The system always thinks the temperature is 100F/40C and the tuning range of the AC is 86-115F/30-45C, which clearly isn't normal.

Videos attached, please help!o_O
[FYT Android Head Units] j0hn83:
That does not disable the head unit "amp" but it disables power to the AMP wire, which can be used to power your external AMP.

There is no head unit amp that can be disabled.

I'm using my cars OEM AMP without issues as are many others, including many users with BOSE amps.

It's all to do with how the audio is wired at the rear of the head unit but I'm no expert in that so can't help.
[FYT Android Head Units] louforgiveno:
I believe on my unit Amp on/off controls the cooling fan behavior on/off.

To OP, might not help, but have you checked under Settings-Sound Mix and adjusted the levels there? MIGHT help with white noise issue. Also now that i re-read your post, it sounds like you might have speaker level signal being injected into factory amplifier.....you should have line level being injected? Are you using the rca plugs from head unit to factory amp?
[FYT Android Head Units] nkl347:
Thank you very much! I think you are right. It's very likely that I'm sending the speaker-level signal to the factory amplifier. Is there a solution to this? Based on my understanding, both the 16-pin power cable and the 20-pin RCA outputs sound. So the 16-pin power cable is speaker-level, and the 20-pin RCA is line-level?

As I do more experiments today, it seems that my RCA port is connected but not working. I unplugged the RCA port from the head unit, and the sound remained the same. My CAN bus connection is tricky. As attached in the figures
[FYT Android Head Units] nkl347:
Thank you so much. Sorry, I don't know much about how AMP works, but that's probably what louforgiveno said: speaker-level signals are sent to pre-amplifiers.

At least there's something wrong, as I do more experiments, the RCA port is not functioning at all. The system picks sounds from other sources, likely to be the 16-pin power port.
[FYT Android Head Units] louforgiveno:
I think those rca's are for video input.

My unit has a cable with 4 rca's labelled FR, FL, RR, RL and are red and black, or white...can't recall.

I see in the pic your unit has the optical output option....my guess is that is why it doesn't have the rca option...

So you might need to try to find an optical decoder (assuming your factory amp doesn't have an optical interface), or replace the factory amp with an aftermarket with optical interface.

This is what I'm guessing, maybe someone with similar model can chime in.
[FYT Android Head Units] nkl347:
It did come with an RCA cable set that is interchangeable with the one I showed in the red circle, but my car harness cannot be connected to these ports. The seller said either one of the two should work, so I used the plug-and-play one. But now I'm confused. I need to ask the seller again.
[FYT Android Head Units] j0hn83:
If it is an FYT unit and has a 20 pin connector on the rear then the pins are identical on almost all units, whether they have optical or not.

This includes RCA audio output

Pins A17-20 are a bit different on the newer YL850 units.

Whether the seller shipped the right 20 pin adapter with the correct rca's on the correct pins is another matter.
[FYT Android Head Units] nkl347:
I think I started to figure things out. I will do some self-wiring and should be able to resolve the issue. One last thing I noticed is that the 20pin connectors only have two RCA out channels (RL) for [A4 and A6]. I assume the FR and RR just come from one same port; and RL RR come from another port?

my RCA cable only has two output ports, my plan is to buy splitters to make them 4.
[FYT Android Head Units] louforgiveno:
Doesn't seem right, but give it a try....an rca is only gonna have a + & - signal, not front and rear.... doesn't compute to me, but I'd have to be in front of unit and car to say for sure
[FYT Android Head Units] j0hn83:
That's how it should be.

My 20 pin cable only has 2 RCA outputs which is what I use to output audio to my car. It goes from the RCA to a canbus box which converts it to an spdif signal then on to my OEM amp.

I have full control of each speaker (fl/fr/rl/rr) with fade and balance working.
[FYT Android Head Units] nkl347:
Some updates, the audio issue has been addressed by adding a 4 Channel Hi to Low Converter. Thanks, @j0hn83 and @louforgiveno !

The HVAC issue remains.
[FYT Android Head Units] louforgiveno:
Glad to hear.....i don't have ac unit option so probably can't help with that.....if i come across something I'll @ you

Hopefully the right person will read your post and have some ideas....
[Samsung Galaxy S22 Ultra] Nesqu1k2010:
I was able to make and use bad spin . It work but what is next , who can help root?

Or oem unlock , I understand ot is not free but uf Nyone can recommend someone will be good . Thx
[Google Pixel 5a] raccoondad:
Hello, I restarted my Pixel 5a to charge it (it was low on battery). It powered on once I plugged it in (like normal), however instead of the yellow screen I am used to (I run GrapheneOS) I received a pretty scary red arrow telling me 'Failed to load/verify boot images'!

On screen I can see NOS-Production: Error, boot-slot: B, and the reason for failure being it could not load or verify boot image.

OEM unlocking is enabled, at least I never disabled it. So I attempted to use fastboot to unlock the bootloader. However that only got me 'Error getting device locked state Not Ready'

All options like recovery mode or rescue mode fail as well! I checked the variables in fastboot and it seems unlocked is set to "error"!

Anyways, is there any way to fix such a thing? Is this common in Pixel 5a and is it known to happen in other google devices if so? Could a repair store maybe help?

Its currently bricked, so any help is very appreciated
[Google Pixel 5a] V0latyle:
The only way to fix this is to have the phone repaired. The shop will most likely replace the main board so your dats will be gone unfortunately.
[Google Pixel 5a] BrewNinja:
I just had the same thing happen, but Im on stock pixel android. If you find a fix, please respond back!
[Google Pixel 5a] gsmshakin:
I have the same problem. Don't fix the device status: error. Enter the Reason it failed to load/verify boot images on Google Pixel 5a 5g phone. Try to factory images flashing Fastboot mode FAILED (remote: Error getting device locked state Not Ready).View attachment 6064253
[Google Pixel 5a] taxap:
The same problem happened to my phone pixel 3

Are there any solutions?
[Google Pixel 5a] gsmshakin:
I have no solution, bro. Very bad problem