yashsingh1/xdaforums huggingface dataset:
[Redmi Note 10 Pro] KTr1sk:
I don't know exactly but as far as I could see Evolution X has miui camera?

Evolution X - Browse /sweet at SourceForge.net

Pixel UI, Customization & More. We Are Evolution X!

sourceforge.net
[Moto G5 Plus Questions & Answers] richard.sincak:
Hello,

I have my moto g5 plus for 6 years and I decided to change battery (old one was almost dead)

so I get new one and I did everything according to iFixit, but after 5 hours on charger I noticed that white led is blinking and phone wont start. It shows only flash symbol (when trying to charge) for one second, then turn of and on again to that flash sign,

I can get to bootloader and it says that battery is OK (charging) but if I unplug it from charger, phone turns off immediately.

is that sign that new battery is dead? or did I forgot to calibrate it or something (hopefuly)?
[Moto G5 Plus Questions & Answers] blackhawk:
Dead battery sounds like. Carefully inspect its cable and pins for damage.
[Moto G5 Plus Questions & Answers] richard.sincak:
I opened my phone and noticed that I accidentally cut the red cable on the battery. With some unbending and duct tape, it's working like new, hopefully for longer than a week :D
[Moto G5 Plus Questions & Answers] blackhawk:
Yay! Repair it properly...
[Samsung Galaxy S22 Ultra] vegetaleb:
I actually have the S22U 256/12 and was planning to get a S23U 256/12 BUT Samsung decided that if you want 12gb RAM you have to get the 512gb only which will be way too expensive (for me)

I wonder if 8gb RAM is acceptable on a sammy phone and its heavy OneUI or even with RAM Plus the lags are definitely there?
[Samsung Galaxy S22 Ultra] blackhawk:
Bigger is always better, but 8gb will run it well to a point. 12gb means it won't get bogged down and helps future proof it.

Without expandable storage even 500gb isn't that much memory and less is unacceptable.

Samsung hasn't done much to justify upgrading to the S23U. SOT still sucks too.

The S23U is more of the same high dollar hypeware that Samsung been peddling for the last 3 years. The last time Samsung slammed real meat down on the table was with the N10+.

Which is why I'm still happily running my 1.5tb dual drive N10+. Samsung is now just the another iPhone wannabe with an spen. That's what I think...
[Samsung Galaxy S22 Ultra] Village_Idiot:
I don't think it will be a huge issue. The S22+ and S22 are 8GB, and based on using my wife's S22+ 8/256) and my daughter's S22 (8/256) I didn't see any performance issues. Nor have they complained.

I know it is not exactly an apples to apples comparison, but that is the closest that I can think of.

Based on the forums here and other places, it was the 8/128 S22 series devices that had poor performance issues; with Exynos devices tending to have more problems than the Snap Dragon devices.

The 8/256 Snap Dragon S22 series devices tended to perform better.

If you are not in a hurry, wait a few months after the S23 Ultras are released and jump on the discounts that are sure to come and then see if you can afford the 12/512 S23 Ultra. Your S22 Ultra should still fetch a decent trade-in price.
[Samsung Galaxy S22 Ultra] vegetaleb:
What about Ram Plus?

Is it as good as real Ram or it will slow down the UI?
[Samsung Galaxy S22 Ultra] blackhawk:
It's a lot slower as it has less bandwidth of physical ram.

The N10+ vs S22U loading test vid* is interesting especially the last 2-3 minutes. Why does the N10+ rip it to shreds? The N10+ even had faster boot up times. At least part of the reason is the S22U is the 8gb ram model. Wonder how the 12gb S22U would do?

Since Android 10 Google Android has gone off the rails with CPU cycle sucking scoped storage.

This 3+yo N10+/Pie in hand gets twice the SOT with a battery that 700mAh smaller than the S22U. Even my new N10+/Q which is the 256gb variant rather the 500gb has 12gb of ram. With a 1tb SD card it has more storage capacity than current Samsung flagship.

Pretty sad how bad Samsung sucks now.

*There's another speed vid with the N9 vs N10+ vs S22U. The N9 get sliced to pieces by the N10+, the delays on the N9 are sometimes in the seconds.
[Samsung Galaxy S22 Ultra] Village_Idiot:
I have RAM Plus enabled on my phone (it is set to 2GB) and I haven't noticed an increase in performance. After disabling it, there was a noticeable, but not huge, increase in performance. It seemed a little snappier. I have no way to objectively test the difference in performance though.

There are a couple things you need to consider when using it:

a) You are robbing Peter to pay Paul. That 2, 4, 6, or 8GB of "extra" RAM is coming out of internal storage. For a 512GB or 1TB device, probably not a big difference. However, it can make a bigger difference on a 128GB or 256GB device.

b) The non-volatile storage that internal memory uses is a lot slower that the volatile storage that is used for RAM. That can cause performance issues. Those issues can be exacerbated by poorly written apps or apps not optimized for RAM Plus.
[Samsung Galaxy S22 Ultra] draskome:
I would say that 8GB vs 12GB should be considered by observing how the phone will be used most of the time.

In normal circumstances there is no noticeable difference in usage, because there is no need to utilize more than 5-6 GB or RAM for smooth operation of the device. In some scenarios, like playing RAM demanding games, difference could be spotted maybe.

As someone said above, this should be looked like a future - proof feature, nothing else.
[Samsung Galaxy S22 Ultra] blackhawk:
I never regretted having too much ram, only too little. That extra 6gb of ram is dirt cheap for greedy Samsung to throw in.

12gb means many apps can stay loaded. If you multitask it's relevant.

View attachment 5816299

Typical ram usage profile with a light load on the N10+. More ram probably means faster bootups. There are no advantages to having less ram other than cost; the newer ram is very efficient.

Samsung is no longer power user friendly. No good reasons to give Samsung your hard earned money for rehashed "new" flagships with inferior design/functionality/usability. That's what I think... Samsung is a dead end.
[Samsung Galaxy S21 Questions] gaara22:
Can someone help me out with this one. A coworker of mine saw a deal on ebay for this S21 and bought it. The seller claimed it was unlocked and there shouldn't be any problems. Lo and below, when he got the phone, it was locked and giving error codes when trying to permanently unlock it.

We decided to check with T-Mobile on Facebook and they said that the imei is not in their system so they cannot unlock it. Anyone know of another alternative method or so to get this phone unlocked?
[Samsung Galaxy S7 Questions and Answers] huggybear404:
Looking for firmware for SM-G930FD , in about says : Android 8 BUILD NR: R16NWG930FXXDBETC6

that work in norway , got phone used in china and suspect they use other frequencies and need reflash firmware to work.

mostly getting silence when trying call people and also they hear nothing.

must it be same version or should I get latest version ?
[Samsung Galaxy S7 Questions and Answers] alecxs:
https://samfw.com/firmware/SM-G930F/TEN

https://xdaforums.com/t/patched-odin-3-13-1.3762572
[General Questions and Answers] Mase_Mase:
I've tried the method described here but with no luck:

http://xdaforums.com/showthread.php?t=364978

Step One Uninstall your TCPMP and Flashbundle player. Yes you have to install TCPMP and Flashbundle all over. I read you had to do this or else it wont work properly.

Step Two Install TCPMP (a media player that is used to play many files.For example youtube videos ). When you install it chose to install it to your SD card.

Step Three Copy the NEW Flashbundle cab (the one I provided) to the program folder that was created for TCPMP on your SD card

Step Four Once you copied the Flashbundle Cab to the TCPMP folder run the Flashbundle Cab from there and chose to install it to the SD card instead of local memory.

Step FiveSoft Reset

Has anyone here tried to get TCPMP and FVB working with the Epix? I would've liked to post this in the Epix discussion, but I could not find the Epix on the front page.
[Chromebooks] Cut_Right_Sharpening:
I have no idea what happened. Logged completely off the Ghromebook and back on and now the Heroic Launcher is in a LINUX APPS FOLDER and it ran and I was able to log into Gog and Epic.

I just purchased an Acer Chromebook Vero 514 - CBV514-1H-55VP

Activated linux.

I downloaded heroic_2.5.2_amd64.deb] the Heroic Launcher for game.

Followed the directions to load it.

I have an icon in the tray and when I click it to OPEN, it starts having a rotating circle thing like it is doing something, but even after running all night, nothing has actually happened.

Any help?
[Chromebooks] arsfr:
wrong deb file? maybe amd64 isn't compatible with your chromebook.
[OnePlus Nord N20 5G] Einzelherz:
Today my phone tried to push the Android 12 update on me, which I do not want. What options do I have to stick with 11?
[Realme C21] Ridazemouli:
Thank you very much, XDA
[Realme C21] Timmmmaaahh!:
De rien. But please always include an English translation. Is there a point to this thread? What does the title mean?

┤Edit├┤Thread Closed├┤No response for 24 hours, thread has no technical value (but we do appreciate those kind words :)).├
[Google Home] salilsurendran:
Hello,

I want to send an email using a voice command from google home . For eg. I say 'Hey Google, Add a task buy gift' and I want to send an email to mytasklist@tasks.com with ' buy gift'.

I searched everywhere on the web for this but what I find no longer matches with what I find on the google home app or IFTTT. Most of the pages that suggest IFTTT point to Google Assistant and this is no longer available on IFTTT app but I find 'Google Assistant V2' Some of the pages suggest using Routines on Google Home but there is no Routine to send email on Google Home app. anyway to get this done?
[Google Pixel 7 Pro] UltimateGamer83:
Magisk seems to be the only way to root it for now even with OEM unlock function on with bootloader. I'm on android 13 and Pixel 7 Pro. Root methods like Kingroot seems to fail and be stuck at 1 %. But Magisk works fine.
[Google Pixel 7 Pro] JohnTheFarm3r:
Year 2015 is asking for their Kingroot back. lol

Rooting nowadays literally can't be easier. Install the magisk app, extract the init_boot.img from the ROM you wanna use/flash, patch init_boot.img inside the magisk app and flash that img in fastboot.
[Google Pixel 7 Pro] wilberfan:
Take a look at PixelFlasher.
[Google Pixel 7 Pro] phyberlamer:
why would u want to use a one click root on a pixel pointless. pixelflasher is where its at.
[Google Pixel 7 Pro] otonieru:
Well for me, if any, it's not about one click root.

What i really long for is bootloader unlock & root without the need of PC. Lol,

just like in time when you can jailbreak iphone directly from browser. So easy that someone prank the apple stores, jailbreaking the whole display unit.
[Google Pixel 7 Pro] hp420:
someone obviously missed the entire DECADE we didn't need a cable to do anything unless it involved terminal commands.
[Google Pixel 7 Pro] Not_Purgatory:
Because Kingroot was possible to use back then thanks to security holes in the system, which have been patched and locked down.
[Google Pixel 7 Pro] schmeggy929:
Your statement makes absolutely no sense. We didn't need a cable unless it involved terminal commands? That would be every single time this decade and the last. He was stating with Pixel Flasher it couldn't be any easier.
[Google Pixel 7 Pro] hp420:
first off, do your homework.

second, we literally regressed in flashing. we used to have clockwork, cm recovery, twrp, etc...a million tetherless solutions. for a whole decade. i never needed a desktop computer to flash a phone until recently. but yeah.... pixel flasher is great 🙄.....at sucking.

i want my Nexus back Google. this Pixel line sucks.
[Google Pixel 7 Pro] HipKat:
Pixelflasher is basically a 1-click method for rooting/updating your phone. It's the easiest thing in the world. For 2-clicks, you can flash a custom ROM.

So sorry that you need a computer to root. It's not 2013 anymore. Manufacturers do everything they can to prevent the very thing you want to do. If it's too much of an issue to do what it takes to Root your phone, then don't root it. My Pixel 6 Pro was never rooted, It worked fine. It did everything I needed it to do.

My Nexus 6 was rooted and customized like a muscle car. It also did everything I needed it to do. (I still have it, right in my desk)

If you have issues with Recovery - and I miss Clockwork Recovery big time (I only used TWRP on one device) see if you can get Joey Krim to come out of retirement and create a recovery for this phone. (I still have his recoveries on my Dev-host, actually).

The point is, things change. We don't have hard-key keyboards anymore. We don't have attached antennas anymore. Technology moves forward, not backwards and if we're going to be rebels and mod our phones, we can only go with what actually works.
[Google Pixel 7 Pro] hp420:
I know all of 2 people who own a desktop or laptop. Two. Like you said yourself....it's not 2013 anymore. 5 years ago I was finally able to ditch a computer, but now I should go spend like $400 so I can flash my phone???? Seriously, listen to this logic.

WE HAVE GONE BACKWARDS FROM NEXUS. PIXELS STINK FOR MODDING.
[Google Pixel 7 Pro] Lughnasadh:
I don't think Google screwed anyone. Google does things with the average user in mind (although that can open up another can of worms 🙃) , not modders. The average user doesn't unlock their bootloader, doesn't root, doesn't mod, etc.. It's not Google's job to make things easier for modders.

Hell, I'm just thankful we can root at all.
[Google Pixel 7 Pro] xunholyx:
Correct. It's Google's job to make Android more secure, not easier to hack. SuperSU doesn't exist anymore so now we need to use a PC.

I believe you can still flash Magisk in TWRP by renaming the .apk to .zip to gain root, but unfortunately there's no TWRP versions for Android 13 yet.
[Google Pixel 7 Pro] hp420:
Nexus was specifically made as a reference Android device. Google ripped that away from us for a phone made for "the average user" in Pixel. My sentiment stands. We got shafted HARD! I love my p7. But I wanted a Nexus. It's really disappointing to see Google abandon us so much! We had it MADE with TWRP. We would have been better served with the Play suite of phones if they wanted user friendly...but they killed that too!!! Google kills EVERYTHING we love.
[Google Pixel 7 Pro] EtherealRemnant:
Someone doesn't seem to understand that the only reason those tools worked was because they relied on an OS that was full of security holes. Google just plugged those holes. It may be more inconvenient now than it used to be but it's much more secure for everyone.
[Google Pixel 7 Pro] hp420:
someone doesn't seem to understand not everyone cares about security over functionality. idk about you, but i've never had a single issue. not one. ever. going all the way back to 2009 with my first android. and if my count is correct i've had around 3 phones that were unrooted, and those were only because of encrypted bootloaders.

the only time any of my info ends up in the wrong hands is because of server security. has nothing to do with my phone. this is a linux device. NOTHING happens without permission anyway.
[Google Pixel 7 Pro] EtherealRemnant:
Your disinterest in security doesn't mean that 99%+ should have to suffer with an insecure OS just so that you're not inconvenienced when trying to mod your device.
[Google Pixel 7 Pro] otonieru:
well maybe what i really want to see from a phone is : "iknowwhatamdoing" mode,

something like 'csrutil disable' or secureboot disable in mac/PC

and that toogle should be available from the device itself. Not by connecting to other device.

let the one that need full security to be on stock mode

and let anyone who know what they are doing, bypass any security mean.
[Google Pixel 7 Pro] EtherealRemnant:
Giving the ability to bypass security just gives shady characters a shiny red target to figure out how to exploit. It would make no sense to allow this directly on the device.
[Google Pixel 7 Pro] HipKat:
No, they didn't because they never intended to have their phones rooted. If you want to break the rules, then pay the price.

Teenagers don't have computers anymore. Gaming alone is a multi-billion-dollar-a-year industry: Graphic Design/Web design, accounting, media servers, work force servers - all on computers or laptops.
[Google Pixel 7 Pro] HipKat:
Maybe an iPhone would be good for you.....
[Google Pixel 7 Pro] otonieru:
Well, you still need a valid credential to toggle it, which for me, sufficient by any mean.

but then, it's an empty dream. After all, too many smartphone users who simply visit, click and download something malicious at first chance, so it's very normal for google and other oem to enforce their security measure.
[Google Pixel 7 Pro] hp420:
except i literally do none of that. the only computer i've touched in over 6 years is the one at work. and it's not that uncommon, you just live in a tech geek bubble. desktops and laptops are completely unnecessary for like 80% of the population if they have a smartphone.

also, if google was so against rooting and modding in the first place, how come apps like superSU, twrp installer and cm recovery, cm downloader, and a whole plethora of one click apps were NEVER removed or blocked from the play store? google is also EXTREMELY WELL KNOWN for using XDA members' code for features, mods, etc in android, chrome, chrome os, etc.

also....root is root....twrp is NOT root. google RIPPED all custom recovery away from us. they blatantly allow flashing. they still allow pixel flasher to work. your argument is like swiss cheese dude.
[Google Pixel 7 Pro] hp420:
this is EXACTLY my point. if you allow access, you deserve what comes. plain and simple. it's not my fault enough people don't have the common sense to not just randomly click things. So we should all be punished by dealing with a dumbed down phone when those people were NEVER supposed to be the target customer in the first place?

screw this back and forth crap...bring nexus back. if you like pixel, great....why can't we still have nexus though?
[Google Pixel 7 Pro] otonieru:
The thing is, those people are exactly the target for most OEM. Lol. Where the smartphone and marketing gimmick will outsmart the user/potential buyer.
[Google Pixel 7 Pro] hp420:
that's where the oem steps in. this is supposed to be a reference device....or was supposed to replace that without losing its functionality, at least
[Google Pixel 7 Pro] HipKat:
Oh, YOU don't have a computer so no one does.

SuperSU - is a root checker.

There is no TWRP installer. There is the TWRP App, but you have to have TWRP for it to work and custom recoveries are not rooting. They MAY allow you to root your phone but in themselves, they're just a custom recovery.

There is no CM Downloader

Not to mention you completely contradict yourself by claiming custom recoveries are available on the Play Store, then in the next sentence complain because Custom Recoveries aren't available. BTW, every Custom Recovery was developed by a third-party, unpaid developer. Complain to THEM if you're not happy. Google never created a custom recovery and yeah, Cyanogen back in the day did a lot of development that was incorporated into future versions of Android. That's why Cyanogen left Amateur development for a paid position.

Google supported that back then by releasing source code and Kernel source code, which made it easier for amateur Devs to find exploits and to modify the OS. Hence the term, Android Open Source Project. I think it was with Android 5.0 that they went closed source on the Kernels

It was Devs on sites like XDA and SDX-Developers who first introduced ARM and EXT4 to Android, for example.

Also,

IDC is now forecasting PC shipments to be around 320 million PCs that could be sold in 2022.

Will There Be A Downturn In The PC Market In 2022-2023? - Forbes

Secondly, this isn't the complaint department. Maybe you should have done actual research before you bought a phone that doesn't live up to your expectations.
[Google Pixel 7 Pro] xunholyx:
You do realize that even if they still made Nexus devices you'd still need a PC, correct? It isn't the model of phone preventing it, it the newer Android versions. Plus there is no TWRP for Android 13 (and mostly 12), so rooting through that will only happen on Android 11 or earlier.

The Pixel line is really not that far off from the Nexus line. Google makes it easy to unlock your bootloader unlike other OEMs. It's just that a new method of root needed to be implemented. Chainfire stopped with his SuperSU project because the old exploits were patched for security reasons.

It seems your biggest beef is you don't have a PC. It's not Google's fault that you don't want to get one. Buy a cheap Chromebook (you can get one for $300 or less), put it into developer mode, and install the Linux version of the Android SDK's platform tools.
[Google Pixel 7 Pro] HipKat:
I still have my Nexus 6, rooted and flashed with some ROM, I can't remember which one, if you wanna buy it.....
[Google Pixel 7 Pro] EtherealRemnant:
And this is exactly why they have found ways to block things being done on the device. I remember how easy it used to be. If I had ever lost a phone back then though? We didn't even have filesystem encryption in the early Android days so if someone got my rooted device, they would have had access to every part of my life and the TWRP installed on my phone would have allowed them to make an exact clone without my knowledge. In retrospect, I was living way too dangerously back then...
[Google Pixel 7 Pro] xunholyx:
For reference on my comments about TWRP not working on Android 12/13, please see this recent post from one of the developers of that.

https://xdaforums.com/t/recovery-teamwin-recovery-project-redfin-official.4240711/post-88037631
[Google Pixel 7 Pro] gitrazorhub:
Not for the Pixel 5. I have been unable to get Magisk to work since I left Android 11. I just left 12 for 13 and I still can't get Magisk to work after sideloading the patched boot image.
[Google Pixel 7 Pro] i42o:
Fastboot boot patchedboot.img >> go into magisk > direct install. >> Reboot.

There might be a new set of commands for cheetah... But that's always been the command that I use to root my pixels.
[Google Pixel 7 Pro] Beefheart:
You talk about how things were different a decade back for rooting and modding phones.

PIxelflasher is as close to a one click solution as you will get, it covers all you need. To say it sucks is ridiculous. Besides, I don't even see the big deal about needing to use a computer anyway.
[Google Pixel 7 Pro] Lughnasadh:
You can't fastboot boot on this device since it uses init_boot.img for patching, not boot.img. Need to flash it.
[Google Pixel 7 Pro] Lughnasadh:
You don't sideload the patched image, you flash it in fastboot.
[Google Pixel 7 Pro] phyberlamer:
no joke. That's the first. Id rather ditch phone than a pc.

Get a laptop pretty sure find some locally at pawnshop or fb marketplace for good prices.
[Google Pixel 7 Pro] nooted1:
Others have previously spoken similar sentiment, but it is important to realize that "one-click" root solutions only existed because of flagrant security vulnerabilities that could have just as easily been taken advantage of by nation-state hackers to screw you over.

Raspberry Pi can do most of what is needed in order to root most modern devices, maybe with the exception of Samsung devices where Odin is needed. Even then, Heimdall does work it's just not as simple.
[Google Pixel 7 Pro] gitrazorhub:
When the phone reboots after installing the patched boot.img Magisk has no option for Direct Install. Same results for me on Android 12 and 13.
[Google Pixel 7 Pro] xunholyx:
Patch the init_boot.img on the Pixel 7 series, not the boot.img
[Google Pixel 7 Pro] gitrazorhub:
You are correct. Poor word choice on my part. After flashing the patched boot.img Magisk does not show option for Direct Install. Same results for me on both LineageOS 19/20 (Android 12 and 13).