Just wondering if anyone else has been having problems with anything USB related using pixel experience with extras (Don't remember the exact name). And if so how you fixed it. I have tried a lot of different cables and I also know they both work on other phones and other ROMs. This isn't the first time I've had this problem, as I tried pixel experience a while back with the same result.
Edit:
I'm guessing it's a problem with software because when I look at ampere immediately after the measuring is done it's quite high but immediately drops to like 100-200.
I sometimes have a problem with fast charging on a Chinese charger
wiktor83lp said:
I sometimes have a problem with fast charging on a Chinese charger
Click to expand...
Click to collapse
Hmmm, I checked now and sadly doesn't work with laptop, desktop or other wall plugs.
KlasySkvirel said:
Just wondering if anyone else has been having problems with anything USB related using pixel experience with extras (Don't remember the exact name). And if so how you fixed it. I have tried a lot of different cables and I also know they both work on other phones and other ROMs. This isn't the first time I've had this problem, as I tried pixel experience a while back with the same result.
Edit:
I'm guessing it's a problem with software because when I look at ampere immediately after the measuring is done it's quite high but immediately drops to like 100-200.
Click to expand...
Click to collapse
Noticed this issue earlier this year when I flashed my first aosp rom. It's not just a PE/PE+ exclusive issue, it happens on all aosp roms based on xiao trees. The only cable that recognizes quick charging for me is the stock cable that came with the device. I asked about this issue in telegram way back but wasn't answered, unfortunately.
iOrpheus06 said:
Noticed this issue earlier this year when I flashed my first aosp rom. It's not just a PE/PE+ exclusive issue, it happens on all aosp roms based on xiao trees. The only cable that recognizes quick charging for me is the stock cable that came with the device. I asked about this issue in telegram way back but wasn't answered, unfortunately.
Click to expand...
Click to collapse
Hmm, that's kind of sad, means I'll probably need to go back. Even though PE has been really nice now, with the official version. Also doesn't seem like many others have the issue considering there is almost no information about it, so probably no fix.
Related
First of all, apologies if this question was already asked, I did not find anything...
Whilst trying out and comparing several ICS ROMs, I always encountered a problem:
Regardless of which ICS ROM or which kernel I run, when the phone is plugged into my computer, the touchscreen does weird things. It seems as if one touched the screen on several spots simultaniously, which is quite annoying, especially when typing...
On some ROMs/kernels, this problem seems to be less apparent, but it is always there.
Currently I am running ICS333 with mnics-LR kernel (23.05) but as I already mentioned, it does not really matter.
Can anyone confirm this problem and - more importantly - is there any way to fix this?
Was it working when u were in GB? Once i also had the same problem when in gb
Sent from my SGH-T679 using XDA
madushan92 said:
Was it working when u were in GB? Once i also had the same problem when in gb
Click to expand...
Click to collapse
Nothing alike on Gingerbread... Could it be connected to heat? My phone gets rather hot while charging and tethering at the same time...
bopsch said:
First of all, apologies if this question was already asked, I did not find anything...
Whilst trying out and comparing several ICS ROMs, I always encountered a problem:
Regardless of which ICS ROM or which kernel I run, when the phone is plugged into my computer, the touchscreen does weird things. It seems as if one touched the screen on several spots simultaniously, which is quite annoying, especially when typing...
On some ROMs/kernels, this problem seems to be less apparent, but it is always there.
Currently I am running ICS333 with mnics-LR kernel (23.05) but as I already mentioned, it does not really matter.
Can anyone confirm this problem and - more importantly - is there any way to fix this?
Click to expand...
Click to collapse
Usually those kind of problems are connected with bad quality DC power from USB. Bad filtration. Please connect your device to some other PC/laptop and check is it the same. If it is not then your computer is fault. To make sure connect your charger and check is it ok. Stock charger. If it weird too your mobile is damaged.
Of course this may be only one of reasons.
There is some problems with touchscreen when plugged.try calibrate your accelerometer.sometimes it helps sometimes it don't or try touchscreen booster from play store
I once had this problem. Then I changed a cable and it was fixed.
thank you all for your suggestions I'll try them when I get the chance...
for now I'll stick with ICS333 and semaphore kernel, it seems that with this combination, the problem is minimised to "nearly non-existent"
Hello everybody, I am kind of new to rooting still. I have tried many AOSP ROMs and so far I like the Resurrection ROM. the only flaw I am having of the ROM is that it doesn't have fast charge. I really do like fast-charging because I can use my phone on the go and turn it off at night. is there any possible way to get fast-charging enabled on my current ROM? I tried finding on settings and I couldn't find a waybto enable it. please help!
anything?
htav94 said:
Hello everybody, I am kind of new to rooting still. I have tried many AOSP ROMs and so far I like the Resurrection ROM. the only flaw I am having of the ROM is that it doesn't have fast charge. I really do like fast-charging because I can use my phone on the go and turn it off at night. is there any possible way to get fast-charging enabled on my current ROM? I tried finding on settings and I couldn't find a waybto enable it. please help!
Click to expand...
Click to collapse
I think the last time I asked about this issue i was on a AOSP ROM (Cyanogen) and someone told me fast charging is just embedded. So, it won't say in your notification bar, but it's fast charging as long as youre using the correct adapter.
Are you charging time slow, or feel slower than it was before?
it takes 6 hours to go to 100
Aosp roms suck on the note 4. Buggy as hell and problems never seemed to be fixed. I'd say just stick with tekhd's roms. I use tekxodus. Note 4 is getting old now anyway allot of developers moved on to new devices
Sent from my SM-N910T3 using Tapatalk
i have a display issue with my note 8 (N950f), the screen gets greenish and messes up the colors making it very unpleasant to look at (started happening right after september 2020 update) i could fix it by pressing the power button, taping the screen to turn on always on display but then it would switch back to that annoying green display after seconds or minutes (weirdly enough the Always On Display is always good and never shows any green), so i tried to fix it by : Factory reseting, clearing cache, flashing stock os, custom roms pie, 10, 11, nothing worked until i tried flashing a custom kernel (Phantom Kernel for Pie) on a stock os. that fixes the green screen issue temporarily (2 to 3 weeks) i mean it's still there but it gets green very rarely, until it starts to gradually get worse overtime. And also im not the only one! i found another user @B3anbeanbean who has the EXACT problem and he fixes it like i do with the phantom kernel. This can't be a coincidence.
If you have a fast, stable platform that fulfills its mission, leave it be.
My 10+ is still running very well on Pie and will be for the life of the device.
If Samsung doesn't break it, Gookill Android surely will. What applies to MS XPx64, W7 applies more so now with Android.
For all those "upgrades" what did you gain?
Rather than enjoying the device how much time did you lose? Which bring me back to my original statement.
Play games and don't let the game play you.
blackhawk said:
If you have a fast, stable platform that fulfills its mission, leave it be.
My 10+ is still running very well on Pie and will be for the life of the device.
If Samsung doesn't break it, Gookill Android surely will. What applies to MS XPx64, W7 applies more so now with Android.
For all those "upgrades" what did you gain?
Rather than enjoying the device how much time did you lose? Which bring me back to my original statement.
Play games and don't let the game play you.
Click to expand...
Click to collapse
mate, i would've never touched the phone, i love pie and i dont mind using it, the problem occurred on itself on stock os i hadn't touched anything. i did those "upgrades" in hopes of fixing the display.
omae_wa said:
mate, i would've never touched the phone, i love pie and i dont mind using it, the problem occurred on itself on stock os i hadn't touched anything. i did those "upgrades" in hopes of fixing the display.
Click to expand...
Click to collapse
If it running right when first purchased it's likely hardware if a factory reset wouldn't resolve it.
When you start changing firmware rather than find the root cause you throw more variables into the mix. Making it more difficult.
blackhawk said:
If it running right when first purchased it's likely hardware if a factory reset wouldn't resolve it.
When you start changing firmware rather than find the root cause you throw more variables into the mix. Making it more difficult.
Click to expand...
Click to collapse
if it's an hardware problem then why would flashing a different KERNEL fix it? there's no way this can be an hardware issue. please read what i said and dont throw useless opinions if you can't explain them or fix them.
omae_wa said:
if it's an hardware problem then why would flashing a different KERNEL fix it? there's no way this can be an hardware issue. please read what i said and dont throw useless opinions if you can't explain them or fix them.
Click to expand...
Click to collapse
Ever wonder what happens when one or a couple dozen of the billions of transistors in the processor fails?
Firmware doesn't just of a sudden fail, hardware does.
Firmware can get corrupted. Did you ever reflash the original stock firmware version back onto it?
You know verify the firmware load was intact?
You probably lost some digital pathways and/or memory cells in the CPU or another chipset.
The current firmware for whatever reason(s) doesn't use them.
Major carriers like AT&T, Verizon etc are partnered with Samsung and actively dictate what software and firmware goes in those phones to Samsung.
What could go wrong?
I personally never update, rooted and up... well (actually downdates) turned off for all its days.
although to answer the question directly, in my opinion yes spammy ruins stuff for more sales (aka rips off it's customers) then inturn they eventually never want to see a spammed cell again. so realistically they loose money, not a smart choice obviously, but when blinded by greed all kinds stuff will happen.
Was about to put it as a [Question] but decided to place it as possible troubleshoot and experience for anyone with same problem.
Damn, was not expecting this and out of the blue.
I used my mi11ultra normally today, on Xiaomi.eu 12.5.11.0.
I order from Uber, while i waited, was playing asphalt 9. Then poof, lost my wifi connection. Could use mobile data.
At 30% battery remaining.
Couldn't connect to wifi and decided to reboot my phone.
For a few tries turning on wifi reboots my phone after freezing for a few seconds.
Sometimes it doesnt even turn on(no blue icon)
Turn off phone and let the heat dissipate. it's not hot today, and im using FHD res at 120hz, also haven't been playing for a long time, maybe 30minutes.
Tried restart i wiped daivilk and art cache on twrp.
Tried updating just now to 12.5.12.0 , nothing.
Tried Reset Wifi, bluetooth and mobile, nothing.
It lets me, sometimes, enable wifi, search for networks, connect and the wifi shuts down after about 5 seconds.
Right now as i was writing this and decide charged the phone so i could factory wipe. Im at 60% battery and the issue is gone for now.
I posting BOLD on battery comment because i found it that that was the issue oddly enough.
I'm charging the phone till 100% and will let you know if it happens again. "i hope i don't jinx it."
My greatest fear is that i would have to send it to repairs which takes time.
I Jinxed it . Going to Factory reset.
Watched abit of Netflix and then suddenly it freezed the phone and rebooted automatically.
EDIT: It's a faulty wifi module... Have to send it for repairs
xwonic said:
I Jinxed it . Going to Factory reset.
Watched abit of Netflix and then suddenly it freezed the phone and rebooted automatically.
EDIT: It's a faulty wifi module... Have to send it for repairs
Click to expand...
Click to collapse
Was it a Chinese version or global originally?
Chinese
speedtripler said:
Was it a Chinese version or global originally?
Click to expand...
Click to collapse
Chinese version. I even flashed original stock Chinese rom 12.5.12.0 and locked bootloader and it freezes and reboots itself when using wifi or bluetooth.
xwonic said:
Chinese
Chinese version. I even flashed original stock Chinese rom 12.5.12.0 and locked bootloader and it freezes and reboots itself when using wifi or bluetooth.
Click to expand...
Click to collapse
Sounds like it might be a hardware issue if it persists across all ROMs
Do you have a warranty to get a free fix ?
speedtripler said:
Sounds like it might be a hardware issue if it persists across all ROMs
Do you have a warranty to get a free fix ?
Click to expand...
Click to collapse
It had warranty, yes, and it was the Wifi module but ultimately i decided to get a refund.
Curiously i read it's a Mi 11 Series issue, if you decide to search in google "mi 11 wifi issue".
So i have to say farewell to Mi 11 Ultra Community.
My decision was done with several annoyances from Xiaomi and not for the hardware itself, all the crazy features and camera are badass.
Lack of optimization,
Missing gestures navigation with different launchers(which other manufactures already fixed long time ago in android 11...)
Generic updates(same changelog for all devices) and lack of transparency.
I still advise my friends and family to get a Xiaomi device for what they get for the price and i keep getting impressed by the hardware in these devices.
Also love the ecosystem and new features being added every MIUI version.
I got a POCO M3 with Android 10 Xiaomi.eu, that works gesture navigation and doesn't need third party apps.
I think it all comes down to software, because in the hardware department there isn't any complain from me.
I might even get a Poco X3 Pro for 170€ for a secondary device and install some AOSP rom there.
This decision might change in the future since Xiaomi said they are implementing a team dedicated for software issues, but not to this device.
Until then goodbye
Just my opinion,
seems like all hardware issues are happening to people who flashed non stock rom's.
Fingerprints before, and now wifi and Bluetooth.
Glad I am with global version and stock rom (tried .eu for a while and found it garbage). fingers crossed to stay happy
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(