yashsingh1/xdaforums huggingface dataset:
[HTC Excalibur] qaplus:
Dell has this unlocked Pharos GPS smartphone for $199. Pretty good price point for the spec IMHO.

Improvement over Dash: QVGA Touch screen, 1660mAh battery, built-in GPS, 2MB camera, Stereo audio jack (2.5mm though)

Spec:

Operating system:	Windows Mobile 6

Processor:	TI, OMAP 850, 200MHz

Memory:	128MB Flash ROM, 64MB SDRAM

Display:	2.8" TFT LCD with touch panel

Resolution:	320 x 240 QVGA with 65K colors

Phone:

* Unlocked with one SIM card slot

* GSM Quad band 850/900/1800/1900 MHz

* EDGE / GPRS Class 10

* Talk time: up to 4 hours; 200 hours of standby

GPS:	NMEA0183

* Cold start <65 seconds (open sky, typical)

* Warm Start <38 seconds (open sky, typical)

* Hot start <10 second (open sky, typical)

Digital camera/camcorder:

* CMOS, 2.0 mega pixels, auto focus

* Up to 1600 x 1200 resolution

* Continuous shooting with zoom in capability

Antenna:	Embedded (2G, Wi-Fi, Bluetooth, GPS)

Expansion:

* Wi-Fi IEEE 802.11 b/g

* Bluetooth® v2.0 + EDR

* USB 1.1 full speed, mini USB

* Mini SD slot

* Stereo audio jack, 2.5mm

Battery:	1660 mAh Li-Ion, rechargeable/replaceable

Device Dimension:	4.92 in(L) x 2.8 in(W) x 0.61 in(T)

Device Weight:	6.49oz
[HTC Excalibur] stylez:
Specs look ok but it's a Dell... Then it's WM6 and probably very propeitry in ROM, it's down to what you do but defo would not put it as a replacement to the Dash.
[HTC Excalibur] jasonusmaximus:
you can't replace the Dash...so begone with your blasphemous words.

:)
[HTC Excalibur] gixxum:
your dash must have a beer tap, a set of boobs and a lazyboy recliner attached to it or something.....cause mine, just keeps getting older and crappier.
[HTC Excalibur] jasonusmaximus:
lol...in a perfect world my friend, in a perfect world...
[Asus ROG Phone 6 / 6 Pro] nathasnajperowa:
I've ordered one from official Asus site in my country (dimmensity 9000+).

I'm curious if special edition has more quality control in terms of screen, speakers and overall build quality.

Is there any owner of this version?
[Oukitel (All phone models)] Fytdyh:
My guesses are faulty fingerprint sensor and perhaps some apps. Use battery saving mode, disable fingerprint and face id and should solve your problem. And why 1h timeout? It's pointless. If you are watching a movie, the screen won't turn off. Likewise if you are gaming.
[Oukitel (All phone models)] doublehp:
can I disable finger and face without erasing my user data ? I didn't find any disable tick; and not even sure the module would get disabled if I remove all my fingers.

1h has several reasons:

- when I pause youtube, or one video has ended, if I am away the phone used to turn off and lock, and got fedup haing to unlock to be able to play something else.

- my phone stores many documentations I need to read in various situations (technical specs of engines in the field, or components I am soldering, which may require me to put gloves (for dirt reason, or chemically agressive products. I don't buy IP68 phones for the fun of carrying a hammer in my pocket))

- I may read web pages that take several minutes to read (I use very small font), or need to re-read some paragraphs.

So my customers wouldn't agree with juging pointless the way I configure my phone.

I can't see how a hardware part could produce such a regular fault, every exactly 600s; it's already very hard to design a hardware component that specific, I would be curious to understand how this precision could be done by the hasard of some fault.
[Android Head-Units] sebekkg:
Hi everyone,

I have bought android head unit for audi a4 b8. It is snapdragon 662 unit with 6GB/128GB.

It has KSW android 11 but the work with CAN BUS is useless, well not entirely buttons do work, but unit doesen't know if light are turned off or on, how much diesel is in it, but what is most frustrating is unit doesn't know if car is in reverse to turn on reverse camera over can bus. Now it only works over reverse light in forced mode.

Does anyone has some newer and better mcu file than this one. Guys at bimmerpost forum told me that only with newer mcu i might have a chance to have camera working properly . With this forced mode it takes 3-4seconds to engage in reverse camera mode, and 3-4 seconds to come back, so in tight turns when there camera should be faster is useless. Thanks in advance.

View attachment 5756957

View attachment 5756955
[Samsung Galaxy S10e Questions & Answers] adrianuuii:
I buy s10e, After several tests, after weeks of use, I found a horrible defect, front camera (4k 60fps) (1080p 60fps) no focus, I've done everything until I got in with the sansumg technicians and they didn't even know what it could be and the whole method to solve it was not completed, only option would be to test android 10. (risky) HELPPPPP?????

everything else on the phone is fine!!!!
[Samsung Galaxy S22] xda-eh:
Which phone gets more hot or warm when it shouldn't, the S22 or S21 Fan Edition?
[Samsung Galaxy S22] xda-eh:
@blackhawk ?
[Samsung Galaxy S22] blackhawk:
Probably the one with the larger capacity battery runs the warmest🤣 Samsung started dropping balls with the N20U. The S22 may be the biggest power hog of the bunch though with not much performance to show for it. This 3yo N10+ in my hand is only milliseconds slower then the S22U in most operations and uses half the power. The break point is the N9 which is noticeably slower (sometimes seconds slower) in all operations especially gaming.

That said all Samsung's should be optimized for best performance. If it's running warm at idle it needs to be toned down as it's burning up the SOT and battery, literally.
[Samsung Galaxy S22] xda-eh:
So the phone's with larger batteries get warmer than the ones with the smaller batteries? It's it the other way around?

Based on what you're saying the S21 FE gets warm than the S22 since the former is bigger than the latter.

How?
[Samsung Galaxy S22] blackhawk:
No, it's which one burns the most current. Unless there's a high ambient temperatures and/or a heavy workload the phone shouldn't get warm. It certainly shouldn't get warm at idle or when using the browser for surfing.

To optimize find the power hogs and address each one on a case by case basis. Battery optimization, adaptive battery ie global power management never worked right; turn it off and get to the root causes. No social media apps on the phone, they are security risks and power hogs. Cloud storage is a power hog (are you missing the 1tb V30 rated SD card yet?), Google backup Transport as well. Playstore and Google play Services I temporarily disable unless needed. Location as well. All Google, Samsung, app and carrier feedback, don't need it.

If you can see the apps data usage real time it can help point out some of the power hogs.

I use a package disabler to block about 70 packages including Android updates. You can use adb edits to do this but it's more awkward.

Don't go too nuts and leave the small Samsung system apps alone. Target bloatware that's useless to you, remember it may have dependencies that you use. Best to understand what an app or service does before you disable it. Names can be deceiving. If you screw up any manner of missing features can appear and be hard to track down. Learn as you go; don't use someone else's list as your tastes are likely different. Some of the bloatware is useful and uses little or no resource when idle. Target the hogs, disable only if need be. Some can be checked in their app setting by disabling background battery and/or data usage (this doesn't invoke global power management).
[Samsung Galaxy S22] xda-eh:
So bottom line, does the S22 or S21 FE become hotter?
[Samsung Galaxy S22] xda-eh:
Anyone?
[P3600 General] clinton:
I do not want the screen to wake from standby when my phone recieves a new SMS. I tried the reg edit below with no success on my 3600 running WM6.

Location in Registry : HK_LOCAL_MACHINE\Drivers\BuiltIn\RIL

Select "New" D_Word and you will be asked to enter the details :

Top portion just enter : DisableSMSWakeUpEvent

and bottom portion just enter the value : 1

Can anyone suggest another method?

Thanks.
[P3600 General] YACO:
Same Issue... looking for an answer now.

-YACO
[3D Printers] bderijke1156:
Hello i was wondering if it will be safe to 3d print in my room. I will be getting an ender 3 v2 and only printing PLA. It will be sitting next to a window if I need to open it. Is it safe to print in my room like this or is it unsafe and this could be putting me at risk for health problems. or i could possibly get an enclosure if that is better

Thanks
[3D Printers] buenso80:
@bderijke1156​

For me, the only gain of an enclosure, would be to avoid draft . this is , off course if you still plan on sticking to pla tpu and petg.

With Abs - I would consider an enclosure for the smell and maybe health issues, in the long run.

But I understand your worries, as both pla, petg and tpu could be dangerous

If you live in a city, breathing in general can be fatal ;-)

It very much depends much on how much you´re planning on printing. If it´s 24/7 and you never leave your room , then I would consider an enclosure by all means.

You should do , what makes your mind safe..
[3D Printers] adiboak:
If you are concerned about your health, you may consider getting an enclosure for your printer. An enclosure will help trap any fumes or particles emitted from the printer.
[3D Printers] lilyoffical31:
When carried out correctly and in well-ventilated spaces, 3D printing is generally regarded as safe.
[3D Printers] appaalpine:
To add onto the enclosure item...you can add filter the air inside the enclosure which will help as well.
[3D Printers] strongst:
Printing PLA or even PETG is harmless, I've printed a lot of them inside and there is no smell or other harmful particles in the air.
[3D Printers] aidansw:
I can't find anything specifically for the v2, but I know for the Ender 3 v1 the bowden tube could degrade and release fumes- so it might be worth replacing that. Also, while its true that PLA and PETG it seems like is safe, some filaments might have additives/dyes that might not be. (That's why I always cringe when people say PLA is food safe then use dyed PLA for food stuff)
[3D Printers] Santana1997:
Make sure your area has good ventilation. Other than that, I think you should be good.
[Device Repair] mberndt:
Hi,

I recently noticed that the USB port on my Redmi 9 seems to be broken. I can still charge the battery just fine, but no data transfer of any kind seems to work.

Thinking that there might be something wrong with the USB port, I replaced the little board that it sits on, but unfortunately that didn't fix the issue. Does anybody have an idea what the issue might be and how to diagnose the problem?
[Google Pixel 7 Pro] lunacies:
I don't know if this is the right place to ask or if it already has been or not, but is there any possible way to get 32 bit apps to run in some type of compatibility mode or something like that? For the most part the majority of my old apps came over from my old phone, however there are some apps I have and used regularly which are not compatable with this phone and I am not sure if the developers are still active or not. I'm assuming the answer is no, or would require root if it were possible and rooting is out of the question for me because I have Verizon. I am expecting to be SOL but figured it was worth asking about here.
[Google Pixel 7 Pro] danw_oz:
This question has been asked and discussed in length, try search
[Google Pixel 7 Pro] schmeggy929:
I will not be rude and the short answer is no. Apps on the play store had roughly 2 years to switch 64 bit. For s**ts and giggles I did try to do a search with zero results.
[Google Pixel 7 Pro] iRhyiku:
If the devs are still active and they havn't updated to 64bit by now then they are a lost cause.
[Google Pixel 7 Pro] jdoe6783:
No Google's heads up to devs gave them ample amounts of time to switch all their apps from 32bit over to 64bit. Tough shiz if the devs didn't take the arning seriously and switched their apps over whenthey had the cance to do so. I'm genuinely curious of 32bit compatibility is a concern and/or a necessity for you why you would buy a smartphone that doesn't support it? I really don't see how that makes much sense when you could have chose from a lot of other new flagships with 32bit support in tact.
[Google Pixel 7 Pro] Guyinlaca:
Get a Galaxy S22 Ultra, Motorola Edge 30 Ultra or OnePlus 10 Pro. It's likely next year's flagships of any brand will be 64 bit only, so the forced shift is coming.
[Google Pixel 7 Pro] lunacies:
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.

I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there would be a way around it but obviously not.
[Google Pixel 7 Pro] nickelnine:
This might be of some help to run 32 bit apps you want:

GitHub - ThomasKing2014/Pixel7_32bit_helper

Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] Ultraman666:
Interesting I will have to check this out
[Google Pixel 7 Pro] VergeDX:
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (

I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo.
[Google Pixel 7 Pro] cultofluna:
Remove "stock' magisk

Install the patched magisk apk

Patch the stock init boot with the patched magisk apk

Flash the new patched init boot
[Google Pixel 7 Pro] bhammler:
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
[Google Pixel 7 Pro] jdoe6783:
That's what I meant by and or sorry if me misinterpreting what you meant
[Google Pixel 7 Pro] Namelesswonder:
I've compiled Magisk with the supplied patch from the repo and it isn't working for me. I've verified that the init does include the changes to override ro.zygote, however none of the Zygote processes start as the adb server never starts up, and well it doesn't boot.

Tested with the modified Magisk APK from the repo, same deal.

Strange that a clean install is necessary.
[Google Pixel 7 Pro] bhammler:
don't bother with a clean install, after I've installed some Mgaisk modules, I had a bootloop ;-)
[Google Pixel 7 Pro] lunacies:
It's nice to see there may be an option and I hope it works for everyone else. I am stuck with a Verizon phone so rooting is out of the question for me and I figured something like this would require root but hopefully other people are successful in getting it to work.
[Google Pixel 7 Pro] Gerr1:
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
[Google Pixel 7 Pro] hahimot483:
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?

Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper

Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] Namelesswonder:
No as I discuss here.

Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
[Google Pixel 7 Pro] Gerr1:
Yes it works now with the new magisk Manager APK.
[Google Pixel 7 Pro] Namelesswonder:
Still unable to get it to boot, even after completely clearing out all Magisk data in /data/adb. I'm on QPR1 Beta 3.1 like @bhammler. Whereas they couldn't boot after enabling Zygisk, I can't boot at all with it. Only difference between us is they wiped and I didn't.

Are you on the QPR1 builds or just the stable builds?

Because I'm thinking that it doesn't work fully on QPR1 which means next month it's not going to work.
[Google Pixel 7 Pro] dary1zhu:
If you didn't restore your apps using Google Backup, it would cause issues. Just do a clean flash of qpr1 3.1 and flash the patched init boot immediately, after that when boot into system, don't let magisk install apk by itself, instead install the patched apk from 32bit helper. It will work. I don't know if I say it clearly, but in my case you must do it before restoring any apps (clean system).
[Google Pixel 7 Pro] Gerr1:
Absolutely right, cancel the Setup and flash the init Boot img, than restore
[Google Pixel 7 Pro] Namelesswonder:
Why would not restoring apps from Google Backup have any change? It is irrelevant.

I didn't want to wipe my device, but since I wanted to at least test how robust the solution was I decided to go ahead with wiping as it appears to be necessary on QPR1 and I can corroborate what @bhammler has said: enabling Zygisk on the patched Magisk causes the boot to hang on QPR1.

It causes several services to fail to start and Magisk will continually restart the zygote process.

This same issue doesn't occur on the stable November update, however next month QPR1 leaves beta and will become the December update, so Zygisk won't work unless things get updated.

I have also tested further and found that rebasing and applying the patch to Magisk 25205 (or some commit between 25200 and 25205) also causes Zygisk to halt the boot process on both the November update and QPR1.

This additionally means that currently v25.2 is the latest version of Magisk that can be used, once a new version like v25.3 is released the patch will need to be updated to work around this. If not then you will have to run without Zygisk.

You don't need to go through the setup or abort it, you can just run fastboot --skip-reboot -w update image.zip to disable the automatic reboot, wipe the device, and restore it to stock firmware. After that it is just selecting to reboot back into the bootloader and flashing init_boot.
[Google Pixel 7 Pro] dary1zhu:
I got zygisk enabled, and rebooted many times as I'm using substratum themes, no bootloop so far. Instagram mod installed successfully, which clearly indicates that the modded init boot is working.
[Google Pixel 7 Pro] Namelesswonder:
What version of QPR1 are you running?
[Google Pixel 7 Pro] dary1zhu:
the latest, beta 3.1
[Google Pixel 7 Pro] Namelesswonder:
Can you show a screeenshot of the home page in the Magisk app?
[Google Pixel 7 Pro] Namelesswonder:
That's strange because I literally can not get it to work with Zygisk. I've spent the last 9 hours trying every combination and it refuses to work. Either from completely skipping setup to immediately enable Zygisk to restoring in the setup, installing and running a 32-bit app, installing a Zygisk module, then enabling Zygisk. It all ends the same.

I don't know the exact process you followed, but it shouldn't be any other different than:

Flashing wipe QPR1

Flashing patched init_boot

Booting and going through setup

Installing patched Magisk APK

Completing Magisk setup

Enabling Zygisk

If there are any deviations you took then let me know.
[Google Pixel 7 Pro] Ultraman666:
So if you already have magisk 25.2 installed and want to use the modded version to allow 32 bit app installs. Do you have to remove the current magisk and all modules then install the modded version or can you just install the modded version over the original with the modules still installed?
[Google Pixel 7 Pro] cultofluna:
On the second step the init boot has to be patched with the new magisk apk( the patched one)
[Google Pixel 7 Pro] Namelesswonder:
I said patched init_boot, in the same post I said I installed and ran 32-bit apps, my previous post has me discussing disassembling the init and compiling Magisk with the zygote patch.
[Google Pixel 7 Pro] J0nhy:
Is there a tut or something for this? I see people talking bout installing custom magisk apk but in that link there's no apk or anything to download can someone take me to the right direction? Thanks
[Google Pixel 7 Pro] J0nhy:
Which patch magisk? I can't find a download link in that link
[Google Pixel 7 Pro] Gerr1:
In GitHub search for the Button Go to file
[Google Pixel 7 Pro] kemikalman:
Hello have you solved your issue? I'm also stuck whenever I enable zygisk and reboot it stucks in G logo and loading. thank you.
[Google Pixel 7 Pro] zebulon17:
I don't understand.

I have insalled Magisk-v25.2_patched.apk on a wiped pixel 7 pro and i can instal 32bit apk. But how i can enable without bootloop zygisk?

What is the magisk_v243.apk available in the package folder on github?
[Google Pixel 7 Pro] mad4some:
Question: I restored apps from my old device to my P7Pro using Swift backup. Most work fine but a few will not even start at all, just a blink and they're done. After some reading people are saying that the 32 bit apps are blocked from being installed (from the play store) in the first place, so did I get around that block by using Swift and they will no longer open because they are 32 bit?.....or could it be compatibility issues with 13? A couple of them are often updated apps that a lot of people use ( Blink camera app, Sam's Club ) that I would've thought would be up to current standards. :unsure:
[Google Pixel 7 Pro] nomfway:
I am on stable build (TD1A.221105.001) and used the magisk-v25.2-patched.apk from the repo, patched the init_boot.img and reboot. However, it was casuing my Pixel 7 Pro bootloop as well. In fact the G logo loads for 0.5 seconds and it's completely gone, then it tries to boot up again. And I have no way to stop this because it went away very fast that preventing me from booting into safe mode!

Edit: I was using stock stable magisk before this and it was the same version number (25200), so not sure what happened to the patched magisk.apk
[Google Pixel 7 Pro] Gerr1:
You can boot always in safe mode, nothing to do with the bootlogo just press volume down before the logo appears.
[Google Pixel 7 Pro] nomfway:
In fact, that's what I did. And by "it went away very fast" means that the phone is in constant bootloop and pressing the buttons for safe mode obviously doing nothing, because the bootlopp happens before the phone managed to process the button combination. I hope this makes it clearer.

Edit: Also, volume down+start button boots into fastboot mode, that the only way I could escape bootloop by flashing back the stock init_boot.img

Edit 2: "Press your phone's power button. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode" -from Google Support

In my case the animation started and immediately ended due to bootloop, so I don't think "nothing to do with the bootlogo just press volume down before the logo appears." is a correct statement.
[Google Pixel 7 Pro] Gerr1:
From recovery you can shutdown the phone, have you tried to shut down, power on and immediately push vol up and vol down instead of just normal vol down? And hold power button of course.
[Google Pixel 7 Pro] nomfway:
Gave another try, this time I went to recovery mode as advised. Shut down phone > power on > press the key combinations again, couldn't get into safe mode, I could only access fastboot mode somehow. (And it was still stcuk in bootloop)
[Google Pixel 7 Pro] nomfway:
BTW, I noticed part of the screen flickers whenever the boot animation is force killed, looks like the patched init_boot.img was corrupted in some ways. @Namelesswonder Have you encountered similar stuff?
[Google Pixel 7 Pro] nomfway:
3rd attempt: used magisk_v243.apk provided in the repo

Same result, constant bootloop unless flash back to stock .img. Same fate as Nameleswonder to be honest.