yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Honestly, I'm surprised that it worked without first flashing the T290XXU3CUG4 OEM base first, since that was the transition to the Android 11.0 kernel. In the past, that's been an issue.

I've got three Galaxy Tab A7's (SM-T500s) now, and so that's the next big project. I've been putting it off because this is the first release that's been using dynamic partitioning, which is going to be a major hassle. Fortunately, it's going to be raining in Seattle for the entire 4-day holiday weekend, so I'll have lots of time indoors to focus on my hobbies.

Last week I also got an insane deal on a Galaxy Tab S7 FE (SM-T733), so that's been added to my list for TWRP and Nexus Stock supported devices.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gigahurts:
Well, the rain in a part of life up there, cool you can focus on development whilst indoors.

Awesome news about the s7 fe, unfortunately the soc is a bit different than the s7 and s7+, but I've already got twrp and a of debloated custom ROM installed that I've been working on for them.

I buy broken tabs (frp, broken screens, no charging, etc) and fix them. That's how I've acquired so many, discount in bulk. Lol. Not sure how the dirty flash worked either, - it didn't going from stock a9 to your a10 ROM, I think Odin takes over and pretty much overwrites every partition, and for whatever reason it worked going from a10 to a11 (I'm kinda lazy is the only reason I didn't format data. I'm downloading your t510 new ROM now and will flash shortly, let you know how it goes. I have 4 t290s all with broken screens, but all function perfectly. I ordered replacement screens, just waiting for them to arrive.

Thanks again brother. (Edited to take some ill advised, thanksgiving day, too much alcohol and inebriated based comments out, for the sake of the moderator"s awesome supervision and general protection of this thread, owned by an even more awesome developer - I went into a little bit too much detail about things which should not be discussed here and which google, in their infinite wisdom, probably wouldn't appreciate. - which I blame partially on a combination of ftryptophan and pomegranate cider).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gigahurts:
Just a quick reply. Safetynet attestation passes now, just checked 30 seconds ago. Weird, I'll check the t510 again and update shortly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Gent':
hi there, thanks for the rom. How can i flash the .tar.md5 file, should i use odin or can i flash it through twrp. Btw i'm coming from stock android 11. Thanks in advance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
Thanks, AFH worked slow but well .. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
Odin
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] XRaiderV18:
so...this is a stock android os experience for the sm-t290? is it still being actively developed?

kind of not thrilled with samsung's take on android 11(the performance just goes down hill the more days elapse since its last reboot)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
New build posted which works around the hang during offline charging by simply booting normally. This is often a desirable behavior for automotive configs, and it's by design on iOS. (Note that I've hit the 2GB file size limit on the .zip update file, and so you may have trouble installing it in TWRP.)

Downloads:

Nexus_Stock_CR_T290XXU3CUG4-20220220.tar.md5 (Odin tarball)

Nexus_Stock_CR_T290XXU3CUG4-20220220.zip (TWRP update)

Change Log:

20220220:

Boots normally for offline (cold) charging

System partition based on CAOS 11.0 v315 (January 2022 Security Update)

Updated TWRP recovery to v3.6.0_11-1 (20220220).

Updated Google apps from latest OpenGapps Stock variant (20220215) w/ rollback for WebView
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyPhreak:
So I dusted off my SM-T290 that was previously running stock T290XXU3CUG4, powered it on, and it proceeded to auto-update to T290XXU3CUK4.

The Instructions in your OP still say "Ensure matching OEM build (e.g. T290XXU3CUG4) is installed"...

Will I have any problems by laying down your latest "TWRP v3.6.0_11-1 (20220220)" and latest Nexus_Stock_CR_T290XXU3CUG4-20220220.zip on top of this? Or should I use Odin to flash back to the previous stock ROM first?

Do we know if there were any significant bootloader changes between these two stock ROM versions? The BL_ filenames are definitely different, and HxD definitely shows many diffs (though I have no idea what I'm looking at here...).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Gent':
Links not working.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I'd guess that your odds are good, but beyond that I really can't say because I haven't tried it. I did put in a request for the kernel source for T290XXU3CUK4 last week, and hopefully we'll have that soon so that TWRP and Nexus can be updated for the latest OEM firmware.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
It just worked for me from Incognito Mode, so everyone should have access. OneDrive just requires that you have an account. For anonymous downloads, try the Android File Host archive.

Note: This is the time of year when my Microsoft Alumni Membership renews, and so my OneDrive reverts to the free version for a day before the new product key takes effect. That would have been March 2nd.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyPhreak:
I'm pretty sure I unlocked the bootloader on this tablet correctly several minutes ago. However with this latest version K4 of the stock ROM I was

not

seeing messages during regular boot that the tablet is unlocked. I did confirm in Developer options that OEM unlocking said "Bootloader already unlocked", and when booting into download mode it said "OEM LOCK: OFF (U)".

So I decided to try and flash your slightly older version G4 Nexus ROM on top of this newer K4 stock but unfortunately it FAILed at writing the system.img:

Spoiler content hidden.

At that point I long-pressed the power button to turn it off, then powered it back up and got the message "An error occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Any long-press on the power button after that would immediately return to the same screen...

@MossyTC hinted in a post in his Unlock/TWRP/Odin HowTo/Root guide to long-press power and then immediately press volume up+down and insert the USB cable, which took me back to regular download mode.

At that point it made more sense to revert to the previous stock version G4 that your current Nexus released is based on. That flash via Odin (all four files, including BL_) went off without a hitch. Post-flash reboots still showed no indication that the bootloader is unlocked, but Developer options still showed "Bootloader already unlocked", and download mode still said "OEM LOCK: OFF (U)".

So at this point the tablet should have been ready to flash your latest Nexus ROM, right? But the flash FAILed in the same place:

Spoiler content hidden.

On this latest fail there was a red error message printed on the tablet screen, right below "download mode!! ":

SW REV CHECK FAIL : [system]Fused 3 > Binary 0

Maybe this error message was also printed when I attempted to flash your Nexus G4 on top of stock K4 but I just didn't notice it...

Any idea what's going on here?

(Edited for some minor terminology cleanup)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Sounds like you triggered Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyPhreak:
Hopefully that will still work if I disable all the auto-update features first? But I'm guessing not...

At this point I've already flashed back to stock K4 (again, no errors) but yeah I guess I should go ahead and bite the bullet and let Samsung and Google have their way with auto-updates on this poor tablet. Otherwise when you release a K4-based Nexus ROM it will probably fail again?

BTW thanks for all your effort on this. Looks like you did a great job, if only Samsung will step out of the way!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yeah, do a search on ValultKeeper and you'll find several of my rants about how insidious it is, basically creating a hidden bootloader state that appears unlocked but actually isn't. You don't need to log into Samsung or Google to disable it after setup, but you do need Internet access so that it can connect to Samsung's backend service after you enable Developer Options.

Alternatively, you can just get really good at catching the reboot after an OEM firmware flash to return to Download Mode and then flash the custom ROM, skipping the OEM setup entirely. That's what I've learned to do.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyPhreak:
Thanks, I figured that avoiding logins to Google and Samsung would still let Samsung access their backdoor(s). Should be even easier for everyone to do that, now that Samsung's source code has been leaked. Yikes!

I'll try your hint about immediately returning to download mode when you release a K4-based ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UPSGuy:
I just wanted to take a moment to point something out that I wish I had known before I spent lots of time on trial and error & research.

If you're running this rom and want root, you don't need to mess with magisk or install supersu. Simply go to Settings->Phh Treble Settings->Misc features and select the checkbox next to SuperUser. Exit settings & reboot. Install a root checker and you'll see that you now have root.

P.S. If you like the usual Samsung navigation button layout (not the default on this rom) you can do that on this same page. Select the check box next to Navigation Bar Inverse then reboot.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Roarmaster:
[Deleted]; wrong forum
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kylethedarkn:
I'm getting a software rev check fail when trying to flash the custom tarball in odin. Any idea how to fix this?

Got it installed, but I'm having a problem with storage. It says I only have 8gb of storage...Does anybody know how to fix that or tell it to install to ext sd card?
[Touch Cruise General] mastra:
I have a Storage card (SanDisk Micro SDHC, 8 gb) in my HTC P3650 (Polaris) with WM6.

Since yesterday I can't access a few photo files. They are corrupted.

I tried to delete them, but it wasn't possible. I even couldn't delete anything.

So I tried 'format'. Even this formating couldn't delete any file.

It is also not possible to save files on storage card.

how can I reset or delete or format the storage card?
[Touch Cruise General] oTToToTenTanz:
Solution

Hey,

once got the same problem.

I used software to format the card.

http://www.zdnet.de/hilfsprogramme_fuer_pocket_pc_flash_format_download-39002345-9971-1.htm

The program should be fine, the limited shareware edition is enough to clear the card once.

Have fun dude,

Kon
[Android Stick & Console RockChip based Computers] ashdjto:
Hi all

I have hk1 max box CPU 3318

Everything is well bit launcher seems write protect ..when i try to add icone to the quick bar nothing happen

Someone have this launcher apk?
[Huawei Developers] Mayism:
After an app of the open testing version is released, some users feed back that they cannot find the app on HUAWEI AppGallery. We find that this problem can be solved with the following solution:

1. Go to the Version information page in AppGallery Connect, click View details to check whether the user has accepted your invitation. Only users who have accepted the invitation can find the app. If the status of a user is Unsent or Invited, you can send an invitation to the user again.

2. Make sure that your test is still within the validity period. Otherwise, your app will be removed from sale.

3. Then, make sure you have selected the right data storage location. For example, if you want to invite users in Germany, select the Germany site. If you don’t know the exact site where the test user resides, or you want to invite users from all over the world, select All. You are advised to select All. If you select the wrong storage location, you have to recreate the user list and release your open testing app version again.

4. Finally, make sure the user in question has signed in to AppGallery using the account you invited, and that their location is included in your app release countries or regions. A user can find your app only when all preceding conditions are met.

5. Suggest that the user use a GMS-based or HMS-based device to search for your app in case that your app may be filtered out for other devices.

For more details, please check:

https://developer.huawei.com/consum...lery-connect-Guides/agc-betatest-introduction
[Huawei Developers] justnewsp:
That is of big help
[Huawei Developers] Mayism:
Thank you for your like.
[Huawei Developers] Freemind R:
As a developer, you'll know that people these days have all sorts of apps to make their lives more convenient. But with so much competition, how do you make your utility apps indispensable to users?

With HUAWEI Push Kit, you can maintain closer ties with your users by pushing them information that matters to them. This boosts awareness of, and engagement with, your apps.

Push messages are useful in all kinds of situations, including:

Browser: Recommend news stories to users so they can keep up with current events.

Weather: Send users daily messages about weather, and warn them if sudden and extreme weather conditions are expected.

Game accelerator: Recommend new games and send users game-related benefits.

Input method: Recommend the latest themes and functions of an app.

HUAWEI Push Kit provides you with everything you need to make sure your messages reach your target audience.

High Delivery Rate

Generally, news-related messages are pushed to a large number of users. As Push Kit is a system-level channel, you can use it to send tens of millions of messages every second, and tens of billions of messages every day. By establishing a stable and system-level persistent connection, Push Kit uses the Push Service app, which is preset on users' devices, to display messages in the notification panels of the devices, even if your app isn't running in the background. This means that 99% of your messages will reach their target devices within 10 minutes.

Audience Segmentation

With Push Kit, you can classify target audiences using tags. For example, if you have a weather app, you can send alerts about extreme weather to devices based on specific attributes, such as the user's region.

Scheduled Messaging

Sending messages at the wrong time can affect open rates and even annoy users. With Push Kit's scheduled messaging function, you can set the time you want to push in advance. This enables you to flexibly arrange your work and choose the most suitable time for your audience. For example, players don't want to be disturbed in the middle of a game, so when you're pushing messages using game accelerator, you can select a more appropriate time, such as during meals or before they go to sleep.

Easy Integration

Integrating Push Kit is really straightforward. Huawei provides a tool for you to integrate Push Kit into your app within half a day, and provides sample code for you to reuse in your app server. If you run into any problems, we have dedicated technical support who can help you with the integration process.

Click>>Find out more on our official website

Click>>Access guide

Click>>Technical support

We hope you enjoy using Push Kit!
[Huawei Developers] Rebis:
Very useful.
[Huawei Developers] John Wo:
:geek:
[Huawei Developers] John Wo:
Thanks for sharing
[Huawei Mate 30 Pro Guides, News, & Discussion] LPools:
Do you think Biden might lift the ban on Huawei and Huawei might push out GMS?

I got used to not having GMS but I think it would be nice to have it. I got 10.1.0.268 but can't installed GMS.

Thanks
[Huawei Mate 30 Pro Guides, News, & Discussion] KrewsialNL:
Don't count on it.
[Huawei Developers] Mayism:
After an open testing app version is released, some test users may fail to receive the invitation link. I used to encounter this situation. After communication with Huawei technical support, they suggested a solution to this problem:

1. First of all, make sure your app has been approved for release. Generally, you will receive an email notification once your app is approved. You can also sign in to AppGallery Connect and check app status yourself.

2. On the Version information page, click View details and check whether the user who has reported that they have not received any invitation is in the Invited state. If so, the system has sent the invitation link.

3. If the status of all users is Unsent, the possible cause is that the app has been released but the open test start time has not arrived yet. You can change the test start time to launch the test in advance.

Note that to invite additional test users, you need to click Invite to send them an invitation manually.

4. For a user in the Invited state, you can click Invite again to re-send an invitation.

5. If your test user still cannot receive the invitation, instruct the user to check their junk folder and subscription folder in case the notification is intercepted.

For more details, please check:

https://developer.huawei.com/consum...lery-connect-Guides/agc-betatest-introduction
[Upgrading, Modifying and Unlocking] anabouha:
hi guys,

i need change language for i780 - french language.

any link for download.?:)

thanks tom
[Upgrading, Modifying and Unlocking] spinghead:
lang.

me 2 guys.. i need the eng. ver. thanks in advance
[Upgrading, Modifying and Unlocking] anabouha:
http://xdaforums.com/showthread.php?t=392959
[Huawei Developers] John Wo:
Overview

We've grown accustomed to the hassle of connecting our devices to the Wi-Fi networks in new locations, which can be an annoyance at best, and a major frustration at worst. But perhaps more importantly, this process also comes with the risk of password leakage. Wouldn't it be nice if there was a way to connect our devices to Wi-Fi networks on an automatic basis, rather than having to manually enter the password each time?

HUAWEI Nearby Service offers a Wi-Fi sharing feature, which once integrated, equips your app to connect users on a wide range of smart devices to the Wi-Fi networks that they encounter.

Wi-FiShareDemo

Here, we've used Wi-FiShareDemo as an example, which has integrated the Wi-Fi sharing function in Nearby Service. Now, we'll show you the core code for the app, and how the app can be run.

Preparing Tools

One Huawei phone (The phone for sharing Wi-Fi must be a Huawei phone, and be connected to Wi-Fi.)

One Android device (The device to be connected to Wi-Fi must run Android 5.0 or later and have HMS Core installed, and can be a phone or a TV box.)

Android Studio (3.X or later)

Creating an app

Import the source code to Android Studio.

Register as a Huawei developer.

Create an app in Huawei AppGallery. For details, please refer to HUAWEI Developers-App Development. Note that you will need to download the agconnect-services.json file, generate the signing certificate, and save both to the app directory.

Run the app in Android Studio and install it on the test devices.

Procedures

After configuring the code and completing the installation, perform the following steps.

1.Start Wi-FiShareDemo on B, and tap Connect Wi-Fi.

2.Start Wi-FiShareDemo on A, and tap Share Wi-Fi.

3.On A, select the phone that will share Wi-Fi, make sure that the verification codes on both phones are the same, and tap ALLOW.

4.On B, tap ALLOW in the dialog box that is displayed to authorize the Wi-Fi connection.

Core Code

You can view the source code of the app in GitHub. In this app, the WifiShareHelper.java class is encapsulated based on the Nearby Service APIs. Only the APIs requestWiFiConfig and shareWiFiConfig for WifiShareHelper.java are used to connect to and share Wi-Fi.

requestWiFiConfig

// The device request to connect WiFipublic void requestWiFiConfig() { Log.d(TAG, "requestWiFiConfig"); mWifiShareEngine.startWifiShare(mWifiShareCallback, WifiSharePolicy.POLICY_SET) .addOnFailureListener(e -> Log.e(TAG, Objects.requireNonNull(e.getMessage())));}

shareWiFiConfig

// The device to share wifipublic void shareWiFiConfig() { Log.d(TAG, "Start to share WiFi"); mWifiShareEngine.startWifiShare(mWifiShareCallback, WifiSharePolicy.POLICY_SHARE) .addOnFailureListener(e -> Log.e(TAG, Objects.requireNonNull(e.getMessage()))); showListView(); setListViewListenerMode();}

Learn More

For more details, please visit HUAWEI Developers.

For further instructions, please refer to Development Guides.

To join the developer discussion, please visit Reddit.

To download the demo and sample code, please go to GitHub.

To resolve integration issues, please go to Stack Overflow.
[Huawei Developers] John Wo:
1. Introduction to Wi-Fi Sharing

We've grown accustomed to having to spend time connecting our devices to Wi-Fi networks in new locations. Requesting and entering a Wi-Fi password can often be a hassle, and sometimes it can prove to be a major frustration. But perhaps more importantly, this process also comes with password leakage risks. HUAWEI Nearby Service offers a Wi-Fi sharing feature. When this feature is integrated, your app will be equipped to help users connect a wide range of smart devices to the Wi-Fi networks they encounter.

2. Wi-Fi Sharing Principles and Highlights

2.1 Principles

As shown in the figure above, users can use Bluetooth to enable their phones to discover devices, such as other phones, smart TVs, TV boxes, or smart speakers. Then they can simply select a device, after which Nearby Service will automatically configure the Wi-Fi settings and connect the device to the Wi-Fi network.

2.2 Hassle-Free Wi-Fi Connections

With the Wi-Fi sharing feature, users can connect their devices to Wi-Fi without needing to request and enter a Wi-Fi password, manually turn on the Wi-Fi switch for the device to be connected, or spend time determining a suitable Wi-Fi network, greatly enhancing the user experience across the board.

2.3 Effective Safeguards for User's Wi-Fi Information

1. Only the currently connected Wi-Fi network on the user's device can be shared. Wi-Fi networks that are saved on the device but not connected cannot be shared, ensuring that they are not affected.

2. Wi-Fi passwords are not disclosed, preventing password leakage.

3. HMS Core encrypts Wi-Fi passwords before transmission, preventing them from being eavesdropped.

4. HMS Core automatically configures the Wi-Fi on the device to be connected. The SSID and Wi-Fi passwords are not provided externally.

5. Only nearby devices (for example, devices within 10 meters) are eligible to share Wi-Fi.

6. A verification mechanism is provided for users to reject applications from untrusted devices.

3. Integration of Wi-Fi Sharing

3.1 Integration Process

1. Enable Wi-Fi sharing.

a. Call WifiSharePolicy to set or share Wi-Fi as required.

b. Register WifiShareCallback to process callback events.

c. Call the startWifiShare() API to enable Wi-Fi sharing.

2. Share Wi-Fi.

Call the shareWifiConfig() API to share Wi-Fi with the remote endpoint.

3. Disable Wi-Fi sharing.

Call the stopWifiShare() API to disable Wi-Fi sharing on the local endpoint.

3.2 Integration Restrictions

1. Devices whose Wi-Fi is to be shared must be Huawei phones that run EMUI 4 or later and have HMS Core installed.

2. Devices to be connected to Wi-Fi must run Android 5.0 or later and have HMS Core installed.

3. The Wi-Fi to be connected should be encrypted in WPA2-PSK mode.

4. Learn More

For more information, please visit HUAWEI Developers-Nearby Service.

For detailed instructions, please visit Development Guide.

To download the demo and sample code, please visit Github.