yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S4 Questions & Answers] howudodat:
rooted tab, Android 9, kernel:4.4.153-WETA-4.0, build BSD1, using total commander, trying to paste a file into private storage of another app. Temporarily I have set permissions to 777 (of parent folder), still get unable to write file. see screenshots for more info
[Samsung Galaxy Tab S4 Questions & Answers] waterdaan:
To find the problem you need the LogCat
[Xiaomi Mi A3 Questions & Answers] ficicaaa:
Hello, how did u menage to activate led notification for missed call or sms?

mine only works with viber...

ty in advance
[Xiaomi Mi A3 Questions & Answers] ficicaaa:
anyone ?
[Xiaomi Mi A3 Questions & Answers] vlk67:
go to "Settings", try to find "Notification", in result it is "Application and Notification->Notification", 3rd row is switch for LED
[Xiaomi Mi A3 Questions & Answers] ficicaaa:
actually, i do not have that option :(
[Xiaomi Mi A3 Questions & Answers] Tathagata Nandi:
Settings>>apps & notifications>>notifications
[Xiaomi Mi A3 Questions & Answers] ficicaaa:
I did that and still no led notification, only on viber it works :|
[Xiaomi Mi A3 Questions & Answers] _mysiak_:
Any update on this? Does it work for everybody/somebody/no one? I tried SMS and Gmail notifications - Ambient display turns on, but LED stays off. It seems that the only time when it's glowing is during charging.
[Xiaomi Mi A3 Questions & Answers] _ehsun:
led notification works for Instagram, WhatsApp, telegram
[Xiaomi Mi A3 Questions & Answers] friendfriend:
Not working for "missed calls".
[Xiaomi Mi A3 Questions & Answers] evanB70:
I'm on global rom v10.3.6

The notification led works perfectly for sms, missed calls etc.

I had to activate it from settings though.
[Xiaomi Mi A3 Questions & Answers] _mysiak_:
Yesterday I noticed the LED, but it was only for gmail. SMS messages still nothing. The phone is on the lastest 100% stock EU ROM. Reading topics on MI forum, more people are having the same issue. If I remember correctly, Mi A1 had initially similar problems, but it got fixed after few updates. I guess it's just Xiaomi thing.. :) When I get another phone for myself, I'll try to check it in more details with root.
[Xiaomi Mi A3 Questions & Answers] HTCDevil:
Same for me
[Xiaomi Mi A3 Questions & Answers] friendfriend:
My version global eu rom is v10.3.8 and LED notifications is blind for missed calles and sms.
[Xiaomi Mi A3 Questions & Answers] chem20:
How to assign a color to each notation?
[Xiaomi Mi A3 Questions & Answers] chem20:
That's too bad
[Xiaomi Mi A3 Questions & Answers] Punshibakhuraijam:
I have a problem, ambient display blink always ,rven blink light us off, how to fix it
[Android Q&A, Help & Troubleshooting] FormelLMS:
Google shows in Android 10 the nightmode, but it's only enabled via a switch.

Is someone able to make an app, that will change it automatically?

So that there is Light theme after sunrise and dark theme after sunset?

I think, this would be great and good looking.
[Tilt, TyTN II, MDA Vario III Themes and Apps] -PiLoT-:
is this the rite version of flash to use coz its not working
[Tilt, TyTN II, MDA Vario III Themes and Apps] -PiLoT-:
i tried 2.1 and it doesnt work so then i instaled the other flash for ppc and ot works but then shutopera down anyone know why
[Tilt, TyTN II, MDA Vario III Themes and Apps] pazookie:
flash doesnt work on 9.5...there was a thread about someone trying to get it to work but there findings (a cab) were never posted..your best bet is skyfire...it loads any flash as long as it isnt in a pop up window..but you have to sign up and wait like 3 or 4 months for the beta lol. Opera 9.5 was designed around flash lite 3 and flash lite 3 isnt supported on windows mobile only symbian
[Tilt, TyTN II, MDA Vario III Themes and Apps] -PiLoT-:
yeah adobe and freestylwm.com says its coming though
[Tilt, TyTN II, MDA Vario III Themes and Apps] GSLEON3:
The browser will be integrating FL3. Then it will work.

FP7 will work, but you need to manually set up the config ini file to use it as a plugin. The reason I never posted it was because it is just too choppy & I knew a few new version would be coming out, not to mention that it's designed to be installed with FL3 plugin, which cannot be found for WM yet.
[Tilt, TyTN II, MDA Vario III Themes and Apps] mquintas:
Gsleon3,

Can you tell us how to manually set up or what lines we need add to the config ini or opera.ini file to use FP7 as a plugin in opera 9.5.

Thanks
[Samsung Galaxy Note 9 Questions & Answers] behler:
I want to take my T-mobile unlocked Note 9 to Cricket. Can I flash the firmware to AT&T before doing so in order to take full advantage of the AT&T bands?
[Samsung Galaxy Note 9 Questions & Answers] Jammol:
Yes you can.
[Samsung Galaxy Note 9 Questions & Answers] Youdoofus:
^^^^^^^^^ this ^^^^^^^^^^^

but so far, everyone has neglected to mention that it required a modified version of Odin to allow for cross carrier firmwares to be flashed. I had to do the same with my S9 when i wanted to flash the U1 (unbranded) firmware on the S9 i got from cricket
[Samsung Galaxy Note 9 Questions & Answers] Jammol:
Correct, but that's typically something the person wanting to do the process of flashing firmware on a $1k phone should research or ask about here on xda. As much as I love helping to provide information, it is best for the user that is wanting to undergo the process better educate themselves on what they are about to tackle.

If it had the likelyhood of causing a brick, I would definitely tell them straight away. But other than that, we all get a nice sense of accomplishment when we do flashing that we weren't too sure about. At least I do.?
[Nexus 7 (2013) Q&A] .kaputnik.:
Updated my Flo to the latest versions of Unlegacy Android, TWRP and Magisk a while ago. Afterwards, it wouldn't charge. The USB settings behaved somewhat flaky too, so decided to go back to the earlier versions. Still wouldn't work. Noticed at that point that it wouldn't charge in TWRP either (it should, right?). Decided to try to flash the latest stock rom to rule out any software problems. Put the Flo in bootloader mode, where Fastboot wouldn't find it, no matter which USB port and cables I tried. Tried to reflash the bootloader instead, should rule out any software related problems too.

I've loaded up USBTreeview on the computer to monitor USB activity, and tried plugging the Flo in different USB modes. Nothing happens at all, the USB port seems completely dead.

Also opened the Flo up, stripped a USB Micro cable, and tested for continuity between the wire ends and points after the connector on the PCB. The connector turned out to be ok.

The strange thing is that it charges just fine if I turn it off completely. Assuming it has something to do with everything that could control the charging circuitry being turned off.

So, anyone got any ideas at all what to try next? I'm out of them myself.
[Nexus 7 (2013) Q&A] k23m:
If you refer to the daughterboard PCB then it is inconclusive. Continuity between the port and the motherboard PCB needs to be verified. The wide, silver cable between the PCBs is often problematic. The connections are....

A - 1 (+5V)

B - 3 (data)

C - 2 (data)

D - 4 (OTG)

E - 5 (GND)​
[Nexus 7 (2013) Q&A] .kaputnik.:
Thanks for the suggestion :)

Checked the connections as per above, had continuity between all testpoints. The silvery FFC and its connectors seems to be fine.

Also pulled and reseated the FFC in both ends, just in case temporary contact was made somewhere when I removed and flipped the motherboard over to access the test points. No change though, the USB port is still dead :(

Edit: you don't happen to know what the 4 pin surface mount IC on the data traces close to the USB connector is? Two diodes integrated on an IC perhaps?
[Nexus 7 (2013) Q&A] k23m:
I checked N7's USB port....

Unit off, charger disconnected, ohmmeter measures:

GND-5V: 8kohm

GND-D1: 3Mohm

GND-D2: 3Mohm

D1-D2: 8Mohm

(meter polarity makes no difference)

Unit on, Android running, voltmeter measures:

GND-5V: 0V

GND-D1: 0V

GND-D2: 0V​

Can you please verify the above?

You did test a few USB modes, but there is one, very low-level from the SoC itself, you have not tried:

- turn it off and disconnect USB

- press both vol buttons and...

- plug in to a PC

Now your PC should register a new USB\VID_05C6&PID_9008 device [in QHSUSB_DLOAD mode]

Yes, the IC is an ESD suppressor. It may even absorb the hit from a faulty charger and protect the tablet from destruction by excessive power supply...

:highfive:
[Nexus 7 (2013) Q&A] k23m:
Your ohmmeter is different but we should see comparable results from the more consistent diode-test:

Unit off, charger disconnected, diode-test measures:

GND-5V: 2.6V; 0.5V reverse

GND-D1: 1.2V; 0.7V reverse

GND-D2: 1.2V; 0.7V reverse

D1-D2: 1.5V; 1.5V reverse

GND-ID: 0.8V; 0.8V reverse​

As for the differences in Android, it seems that your micro cable is from an OTG adaptor and has pins 4 and 5 shorted, hence you get this 5V out and also active data. Please disconnect it and check the ID pin on diode-test.

Let's see the hardware logs. Please 'install' the attached file in TWRP within 3 minutes from initial reboot. Then find 'logs.tgz' in the root of internal storage and attach it here or upload somewhere and post a link.

This case is very interesting indeed, cheers! :good:
[Nexus 7 (2013) Q&A] .kaputnik.:
Ah, good idea :)

Unit off, charger disconnected, diode-test measures:

GND-5V: 2.3V; 0.5V reverse

GND-D1: 0.9V: 0.6V reverse

GND-D2: 0.9V; 0.6V reverse

D1-D2: 1.3V; 1.3V reverse

GND-ID: 0.8V; 0.7V reverse.

Did all measurements both with and without the cable, just to see if the cable introduced any effects. The results were identical.

A little lower across the block, but generally much more consistent with your readouts :)

Well, if it was from an OTG cable, the GND-ID resistance would have been somewhere close to 0 ohm rather than the 209 kOhm I got yesterday :) Re-measured GND-ID just in case, without the cable, directly on the connector pins. Still 209 kOhm.

If you'd like, I could double check by measuring the 5VDC-GND voltage with the device powered again, directly on the connector pins, without the cable. Would rather not though, it's far too easy to slip with the probes and short something out.

Ran the system log collector twice. Booted to TWRP and ran the collector as quickly as I could, booted the system and downloaded/deleted the logs from the device, rebooted to TWRP again, and let it sit for 2 mins before running it a second time, to really give everything time to initialize properly.

Had to zip the logs, the forum wouldn't let me attach .tgz files. Hope you can find anything out. Had a look in the logs myself, and quickly established that this is way over my head, you really need to know what to look for for those to be of any use :)
[Nexus 7 (2013) Q&A] k23m:
So, if not the cable, then we have an internal issue - your N7 is stuck in OTG mode. This mode is ignored by the low-level QHSUSB_DLOAD and only then PC can detect it or CHARGE IT when off! (except for modified Android kernels which enable charging in OTG mode)

No doubt about it, compare the logs....

your dmesg
<7>[ 2.876586] id_pin_irq_work_function: gpio_get_value(APQ_OTG_ID_PIN) = 0
<6>[ 2.876586] id_pin_irq_work_function: APQ_OTG_ID_PIN is low : Host mode

dmesg in normal mode
<7>[ 2.077331] id_pin_irq_work_function: gpio_get_value(APQ_OTG_ID_PIN) = 1

Final check - unit on, Android running, USB disconnected (non-OTG mode):

USB pins 5-4, voltmeter measures... GND-ID: 1.8V​

If you measure below 1.8V, it is confirmed, and we will search for a remedy next... :fingers-crossed:
[Nexus 7 (2013) Q&A] .kaputnik.:
Confirmed, the GND-ID voltage with Android running and USB disconnected is only 347 mV.

Powered the device off again, and did some resistance measurements while at it. As mentioned before, the GND-ID resistance is 209 kOhm (or 0.8V with diode test). Disconnected the silvery FFC in the USB daughterboard end, GND-ID resistance jumped to > 40 MOhm. Reconnected the FFC and disconnected it in the motherboard end instead, still > 40 MOhm. That should rule out any issues with the FFC and USB daughterboard at least. Diode test with the FFC disconnected gives, 3.07V, max probing voltage of my multimeter (getting the same reading with probes in the air).

Did a quick checkup of the motherboard with a strong flashlight and a loupe. Nothing obvious visible to the eye, like burned components/PCB, signs of water ingress, [conductive] debris, etc. Leaving the motherboard removed by the way, in case there's something specific you want me to check.

If you feel like opening your N7 again, as a reference, what is your GND-ID resistance reading (powered off, USB disconnected) ?

From your second post in the thread, it looks like you have access to schematics etc. Googled around some, but could only find this kind of documentation for the 2012 model. You don't happen to have a link? Would probably be incredibly helpful with pin designation tables for the FFC connectors, etc, if available :)

This is getting really interesting now by the way :D

Edit: Judging by the log, it looks like the the OTG mode is controlled by a GPIO "pin" being pulled high or low. Guessing the circuitry leading up to the GPIO interface is quite simple. If the problem is something with the circuitry, rather than with the GPIO interface itself, I'm no stranger to desoldering components, cutting traces, etc and completely disable OTG mode. I'm never gonna use it. The N7 is just a "secondary device" nowadays, mostly used for watching movies, HMI for the ODB interface in the car, and cyberloafing on the toilet :D

Edit 2: Took a second closer look at the motherboard, and this time I found something when focusing on the components! What looks like an inductor to me, at the power supply management chip, is busted. Even found the chipped off fragment in the case. See attached photos.

Could definitely explain why that GPIO pin isn't high enough. Doubting I've caused that when removing the mobo, been very careful with it.
[Nexus 7 (2013) Q&A] k23m:
OK, the daughterboard is not faulty. I measure 300kohm GND-ID resistance. No worries about the ferrite bit from the inductor.

I don't have the schematics and they would not help much in this multi-layer, compact PCB, BGA design. It seems that there is a conductive leak from the pin to GND caused by corrosion, or internal IC voltage pull-up resistor failure. So, let's try a simple mod to correct this situation. Please solder a 100kohm resistor between +5V and the ID - the area around USB port is most convenient for it. If the resistor is not enough to increase ID to 1.8V, then try 10k next. If still not enough, use 1k, but not any lower values.

Should this mod be unsuccessful, you can always use Timur's kernel which enables charging in OTG mode. :victory:

:highfive:
[Nexus 7 (2013) Q&A] .kaputnik.:
Got no means of measuring inductance, but a resistance comparison to the other inductors in the same area, which looks identical, suggests the coil is ok at least. Assuming those are only for filtering out high frequency ripple, shouldn't matter if the inductance is a little bit off. So, no worries :)

Will try the mod once I'm a little less shaky, was out for a few beers yesterday night :D Had the same general idea yesterday, but waited in case you had a more elegant solution :)

Really hoping it'll work, would be nice to have fastboot access etc.

Edit: you don't happen to have a suggestion of a point to tap 5VDC from, that's powered when the device is not in OTG mode, btw? Hard for me to find one with a device stuck in OTG :)
[Nexus 7 (2013) Q&A] k23m:
Sure, I propose either the 4V or precise 3.0V. This ~4V comes almost directly from unregulated battery (via a MOSFET only) and needs to be handled carefully. If you prefer a safer option, but hard to reach tap, go for the 3.0V. Also, the shielded area of ELAN IC, the touch control chip, could be explored for more regulated voltage options. Personally I'd use 4V as it is right next to the ID test point near USB port.

:fingers-crossed:
[Nexus 7 (2013) Q&A] .kaputnik.:
So, tested with a 100 kOhm between the 4V point and ID yesterday morning, but it wasn't enough. The ID-GND voltage landed lower than I expected. Had some social stuff going on for the rest of the day, and also today, so had to put it aside until now.

Decided to do it experimentally instead, so soldered a couple of salvaged DIP socket pins to wire pieces, connected them to the 4V and ID test points, and started working through my resistor assortment downwards. At 8k2 charging started to work. The ID-GND voltage was still far from 1.8V though, more like 1.2V or something like that, but hell, it worked, was happy enough with that :D

Soldered in a 6k7 resistor to have some margin, and put the device back together again. Now it's happily charging. Will try fastboot mode etc later on, but I believe we can assume the mission is accomplished :D

I'm extremely impressed by your incredible patience and pedagogic, thorough way of putting things, leaving nothing out! If you ever get any technical problems with your > 30000 ton merchant ship, I'll gladly help you in return; that's my field of expertise, and probably the only place where I possibly could measure up to your help with this :D

Once again, thanks a lot!

Edit: a couple of pics from the modding, if you're interested:
[Nexus 7 (2013) Q&A] k23m:
Great news! Every fixed Nexus 7'13 makes me very happy :victory:

I wish we had its service manual with complete schematic diagrams and could diagnose more problems with better efficiency. It is a 6 year old tech and I hope that the schematics will eventually leak out on the internet.

Note to future readers - the 4V track goes right down to USB port area and if you scratch the paint, you could solder a small SMD resistor there without any wires. Thanks to kaputnik's experiments we now know it should be around 6.7k-4.7k.

Cheers :highfive:
[ONE Q&A, Help & Troubleshooting] rshoreview:
Please help!!

I have messed up my oneplus one bacon

I was using lineageos 16 and all was fine. For some dumb reason like getting 'Screen mirroring' feature, I decided to go back to lineageos 15.1. Somewhere in the instructions I [mis]read, a clean wipe is recommended to go back to previous release.

I wiped all my partitions from twrp. That's why, my system partition is gone.

I tried a bunch of things after searching on these forums for similar symptoms, but no luck as of yet.

I tried to flash the stock recovery and stock ROM

Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted

Now, my phone's state -- I have Cyanogen recovery

ADB devices does not work.

> adb reboot bootloader

adb server is out of date. killing...

* daemon started successfully *

error: device not found

Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.

>fastboot oem unlock

OKAY [ 0.009s]

Finished. Total time: 0.019s

It simple reboots to the recovery without unlocking

>fastboot oem device-info

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

(bootloader) console_enabled: 0

(bootloader) exec_console_unconsole: 0

OKAY [ 0.021s]

Finished. Total time: 0.028s

I tried sideload to upload files like stock ROM, I get verification errors.

I was hoping this thread would help me. But not sure how to apply this fix

I am unable to flash or boot as I get the following error

> fastboot flash recovery recovery.img

target reported max download size of 1073741824 bytes

sending 'recovery' (9968 KB)...

OKAY [ 0.317s]

writing 'recovery'...

FAILED (remote: Device not unlocked cannot flash or erase)

>fastboot boot recovery.img

downloading 'boot.img'...

OKAY [ 0.318s]

booting...

FAILED (remote: Device not unlocked cannot boot)

finished. total time: 0.339s

Please help!!!
[Google Pixel 3 XL Questions & Answers] Ariel_PR:
Delete this
[Google Pixel 3 XL Questions & Answers] i42o:
no.
[Magisk] nift4:
I use multiple apps systemized via Magisk, for example microG, and all apps loose their data (granted permissions, app data etc) after a reboot. I created a test module with a test priv-app and it looses also all data in reboot. What's happening here? It's very annoying.
[Magisk] nift4:
Found a workaround: Install the apps as user app before installing it as system app.
[Magisk] kurtn:
You and Vieu Van published a microG installer magisk module. I'm ready to test, but I can't find a channel for giving feedback. I see no issue in module's github either. (https://github.com/Magisk-Modules-Repo/microg_installer) What is your prefered way of communication?
[Magisk] razr96:
Do you use EdXposed? I have the same issue and that module being enabled seems to be the cause.
[Magisk] nift4:
GitHub issues :)

EDIT: I added them
[Magisk] nift4:
Yes
[Magisk] kurtn:
Welcome back! And the magisk module re-appeared. Have you tested with lineageOS 17 ?
[Magisk] nift4:
Yes, I use it as daily driver. I now maintain it, Hieu Van has no time for that anymore.
[Magisk] kurtn:
Have you seen this?

https://github.com/microg/IchnaeaNlpBackend/issues/50#issuecomment-572662514
[Magisk] nift4:
Now yes :) I have to note that I switched back to original GMS until auth is fixed - I simply need my paid apps.:angel:
[Magisk] kurtn:
After fix "auth", what is your plan to get paid apps running?
[Magisk] nift4:
The problem is that Play Store does not get really logged in and so it can't verify licences.
[Magisk] kurtn:
So you install a playstore app. How about the patched one from nanodroid?
[Magisk] nift4:
I use that.
[General Questions and Answers] AStrutter:
I don't know to much about this kind of things, but I think I bricked my phone. So basically I had an old Samsung Galaxy Y Duos (GT-S6102) laying around I decided to try installing a custom ROM to it. The problem is that I think a flashed the wrong version of CWM and now the phone is stuck at the first boot screen. I'm still able to go back in recovery and when I do that, it says at the bottom that there was an error mounting /system. I tried multiple times wiping the data and the cache, but I had no luck. This is not a great problem because it was just an old phone, but it would be great if it was still fixable. Do you have any suggestions?
[Samsung Galaxy Watch] EagleOne22:
Hi there,

for some activities (i.e., strolling) the watch alerts me about the start of automatic detection of the activity itself, showing on the watch screen some infos like number of steps and others.

After a while, this "page" is discarded and only a symbol of the activity itself is shown on the watch. Is there any way to keep that menu on or to make it pop up on user demand?

Thank you in advance.