naasking

This is an odd issue, I can't get Cloud Sync to connect to an Office 365 Business Basic or Business OneDrive account. I can connect to the Sharepoint account no problem, but not OneDrive. The Microsoft sign in page just says it can't find the account, but I can login directly using a web browser or using the OneDrive app on Windows.

I'm currently running DSM 7.2.1-69057 Update 5. Anyone know what the issue might be?

https://preview.redd.it/cvwx1tyfs20f1.png?width=573&format=png&auto=webp&s=fce14d630732ae1ce6efa2e662bdf6d779f97650

I posted about this on the xpenology forums but thought I'd try here as well. I installed DSM 7.1 on my AMD system using rr-24.5.1 and everything worked great. Kudos to all involved, it was a lot smoother than previous attempts! I have 6 SATA drives plugged into the motherboard, and another 4 connected via a PCI card.

When I ssh into the machine, all 10 drives are visible under /dev/sdX, but only 6 of the drives are visible in the DSM storage manager. I assume it's the 6 drives plugged into the mobo, and the 4 drives connected to the PCI card are not showing up for some reason.

How can I

Model is a UN46ES6100F. See the coloured lines and dimming in the picture below. When the TV starts, the Samsung logo displays without lines at full brightness across the whole screen, but then the lines kick and half the screen dims when it's fully on. That suggests to me that it's either the digitizer or the logic board, is that correct?

​

https://preview.redd.it/2bfteeqaocsa1.jpg?width=4000&format=pjpg&auto=webp&v=enabled&s=afebcfba8507a9ef598ccfcd2c0770b6a6e76f01

I know a bunch of people have had issues with this update. For the most part it's been fine for me except for these two things that have been bugging the hell out of me:

• This nagging pop-up when roaming comes up every single time I unlock my phone, and sometimes even while I'm using it, typing in messages, browsing on WiFi, and more. I can't find any way to turn it off and I'm starting to wish bodily harm on whoever wrote this code. It popped up twice while typing this post while I'm sitting next to my router with a strong WiFi signal.
• Bluetooth has become very unreliable. My handsfree works to listen to music, but not if I call out with my VoIP app (mic

I have a working Hitachi LE39H217 that just started showing some intermittent backlight issues, as show in this image:

https://imgur.com/a/2x3TSVH

It's only edge lit from the bottom, but the dark spots come and go, and sometimes show up in different areas, ie. sometimes on the right side, or the middle, etc. I disassembled and tested each LED on the strip and they all work. A couple looked a little dimmer at the same voltage, but not dark like in the image.

Some of the pins on the LED ribbon cables that power the LED strip were folded over, so I thought maybe they were getting only intermittent power, but fixing that didn't resolve the issue.

Is this maybe

Trying to figure out whether the issue with this Samsung UN40D6000 is worth fixing. Whole screen has some intermittent flickering and the top few inches have persistent snow/flickering as shown in this video:

https://youtu.be/sDuMyzn1JNs

Same issue on all HDMI inputs. Is this a main board issue or the LCD control board? If the former might not be worth replacing, but maybe the latter would be.

I'm troubleshooting a laptop with a power button on it, which immediately shuts off after showing the ASUS logo but before the BIOS/UEFI becomes available. However, it boots successfully if I pull the keyboard connector from the motherboard immediately after powering it on. Steps:

1. Plug in laptop keyboard connector to laptop motherboard.
2. Press power button on laptop keyboard.
3. Pull laptop keyboard connector from motherboard before ASUS logo shows up to boot successfully (I have ~2 seconds). If I don't do this step, or I do it too slowly, the laptop immediately shuts off.

When I pull the motherboard connector, I can boot into the BIOS/UEFI or Windows

I recently had cause to install a custom ROM on my old Nexus 5 and ran into the proximity sensor issue that has plagued many users.

If you have TWRP installed, then the instructions provided in that post become considerably simpler, no need to mess with root:

1. Boot into TWRP.
2. Click Mount and check "System" and "persist".
3. Go back to the main screen.
4. Click "Advanced", then "File Manager".
5. Delete folder /data/system/sensors
6. Delete folder /data/misc/sensors
7. Delete file /persist/sensors/sns.reg

Now when you reboot the proximity sensor should work!