yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] SilntExecutnr:
I've been having an odd issue for a little while. However, it wasn't a problem until just recently. I have an Samsung Galaxy Note 3 (SM-N900A) that is running 5.0 Rooted through SafeStrap (mind you that barely works and if I boot into it I go boot loops now, whole other issue).

One afternoon I tried to take a picture of my daughter using Snap Camera and notice this error across the bottom saying that it cannot access the sd card. Odd, just set it to default storage and forgot about it. Fast forward several weeks and I go to move pictures around in my QuickPic gallery just as I always do. From main storage to SD card. Just got done taking video and pictures of my daughter at the carnival and go to move them to the SD folder reserved for her pictures. The move is near instantaneous and I back out of the QuickPic Camera folder and the folder that I moved it to its thumbnail doesn't update. WTF, click on it and the pictures and videos are not there. Moved on to file recovery app I have and it only finds half of ONE PICTURE.

I am livid.

Spent majority of last night and this morning looking at fixes. Went back to try and re-run SD Card Access fixes from the app store and they said it was already fixed. Edited the platform.xml , no love, entry was already there... no extra spaces or anything. FX File explorer when clicking on Media Card and going to delete/move something tells me that the action failed. Choosing the top right menu and hitting Enable Write Access takes me to the Storage Selection screen, choose SD Card, hit "Select "SD Card"" (Root directory), and it tells me that "the selected location is different than the location of this storage. Go and select the root blah blah."

Now if I go and restart the phone it works as intended for about the first maybe two minutes. Moving files/taking pics etc. After that for some reason it throws out the same errors.
[General Questions and Answers] ruleh:
Try looking into the dmesg log when the error happens maybe it can give some information about it.

Also try accessing your sdcard from a differernt path such as /mnt/media_rw/sdcard1 or similar.
[General Questions and Answers] ruleh:
Read only file system while it clearly shouldn't be.

I would take a look at how the filesystem is mounted.

Open up a terminal and run

mount

and post the output here.

Also run

dmesg

in the same terminal and post that output here as well.
[General Questions and Answers] ruleh:
The mounts seem alright, at least the ones concerning the sdcard.

As for dmesg, it seems running dmesg >

/data/local/dmesg.txt

should work and create a file under /data/local/ with the output.

Also did you try to navigate to /mnt/media_rw/sdcard1/ yet?
[General Questions and Answers] SilntExecutnr:
/mnt/media_rw/extSdCard is access denied unless I use the root access shortcut. Which then I do have control until it auto revokes my privileges from the built in root module.

EDIT: While I was there with root I deleted a file in the download directory and moved a couple things and restarted... The items are still in their original places and the deleted item is back and functional... wtf?

Here is the dmesg.
[8125, K-JAM, P4300, MDA Vario ROM Development] shreker:
what program do you use to stream videos or play them??????i want to use a different vidoe player to see which one is better??????
[Samsung Galaxy S7 Edge Questions and Answers] thegame261:
Do you have auto on or not?

Do you find auto is better for battery life?
[Galaxy Note II Q&A, Help & Troubleshooting] replytoalok:
I am recently facing a problem of touch buttons in my note 2. They stop working frequently from time to time and then start to work when i turn off my phone nd then restart it.

I am on dn4 v2.1

Is their some fix for it.

Please help.
[X Style (Pure) Q&A, Help & Troubleshooting] brusslesprouts:
Hi i recently dropped my x pure and broke the screen. I ordered a replacement screen and should have it here in a few days. I also have been having issues with my headphone jack cutting out music after doing some research it seems its a common problem with Motorola phones. While replacing the screen i was thinking about replacing the headphone jack as well but cant find any parts for the x pure only for older Motorola phones as well as the nexus 6 like this one. Would any of those headphone jack work in my phone? After watching some tear down videos the headphone jack looks identical to each other and wondering if anybody has done this before or if that would even solve the problem.
[X Style (Pure) Q&A, Help & Troubleshooting] guru_shastri:
i'm actually looking for such a part myself. did you try the one in the link? did you find anything else?

thanks
[X Style (Pure) Q&A, Help & Troubleshooting] bv90andy:
I actually bought a whole mid frame with headphone jack off aliexpress. Just search for mid frame moto x style. It's 10 pounds. It didn't last long though, 1 month in and the same thing happens.
[General Questions and Answers] bajlek:
Hi, my phone is hard bricked. I dont know why but phone is completly dead. It douesnt react on power button or vol + - and power buton etc. Only if I connect it into the PC I will get QHSUSB_BULK driver installing and after that care suite emergency connectivity is installed. Can you help me with unbricking? I have another one running OK. I have bricked by flashing I think.

The story

1. phone is telling me something about no boot / bootloader / partitions

2. I download "dload" folder with "update.app" to the SD card and start flashing - OK (B189 I think)

3. trying to testing and after that I use wipe/factory reset

4. reboot

5. unplug battery

6. plug battery in

7. next day phone is completly dead

I will apriciate any help. Thank you
[General Questions and Answers] bajlek:
I also try a others battery but there is no charging led light. Phone doesnt react on any button. Can you help me please?
[General Questions and Answers] TechGuyAnthony:
Wow, this is a tough one. I'm pretty good with restoring phones and this has me baffled. I don't understand how you managed to do this. Fill me in on what you were doing at the time you bricked the device.

---------- Post added at 10:41 AM ---------- Previous post was at 09:53 AM ----------

Hold together:*Power Button + Volume Up Button*for several seconds. And tell me if that does anything to the device (must be decently charged to work)
[General Questions and Answers] bajlek:
Nothing. I pplug in into the charger 5V 2.1A for 4 hours, after that try another charger with another USB cable. But there is no notification (LED or information on LCD) about charging. Phone is completly dead. It doesnt react on any button or any combination (try to hold for 1 minute every combination). But if I plug in into the PC that I see care suite emergency connectivity
[General Questions and Answers] TechGuyAnthony:
Ya. I've had a phone like this before. There was nothing I could to revive it. Start considering replacements... [emoji13]
[General Questions and Answers] bajlek:
Thank you for your support. On the second phone which I repair by firmware upgrade is no IMEI in system. How can I recover IMEI on this phone?
[General Questions and Answers] bajlek:
Re-flash by dload and everything is now fine
[General Questions and Answers] puntogiovax:
How do you solved? My phone won't start.
[General Questions and Answers] HackT3k:
msm8210 files needed

I have the same problem...

Does anyone could provide the unbrick files for Y530-U00 to use with QFIL ??

We need

Thank you!
[General Questions and Answers] mrci2010:
Did u find a solution?

---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------

I need some files if someone wants to extract that files for me
[General Questions and Answers] BeChris100:
So that means, that the preloader is bricked. Because if it would react on any button (Volume Up, Volume Down, Power), then it would normally react. For those buttons are being handled by the preloader partition file. If you either flashed the preloader from a wrong ROM (Like I did one time on Wiko Lenny 3), then no button will react. Those buttons are being handled by their ID's (I think, not sure). Preloader handles the Button ID if it is pressed. If yes, preloader will detect the clicked button and handle the action (for example: Clicking the power button when Display is off → Makes the Display to go on).

If the preloader is bricked, then either you need a new phone or reflash the preloader.
[General Questions and Answers] Andys4c:
Huawei Y530 Bricked too

So heres what happened:

Phone didnt boot and showed a recovery, boot image verify failed.

-i copied original firmware for this model (i used right one) to sdcard and updated from it.

When the update was finishing the phone was stuck.

-I tryed to turn on the phone but i cant.

Plugged it into PC, reflashed but still its dead.

Anyone, help please
[General Questions and Answers] Audacious3058:
Please help (sorry for not specifying)
[General Questions and Answers] Smedslund:
Please specify.
[General Questions and Answers] Audacious3058:
View attachment 5993415

I get this error when trying to flash the firmware
[Android Q&A, Help & Troubleshooting] celoxocis:
Hi there,

i was searching the forum and the inet without any luck about information on how to create or generate *.dtsi files which are placed (in my case) in:

android\system\kernel\oppo\msm8939\arch\arm\boot\dts\qcom\15018\

im bringing up a new device the "Oppo R7S" which is a sibling device of the "R7 Plus".

So far i was able to compile and boot CyanogenMod succefully. Everything worked except for the Videorecorder

Here are a few pictures: http://community.oppo.com/en/forum.php?mod=viewthread&tid=45106&extra=&page=2

I have noticed that the display driver that my rom has used in my bring-up was either the one for the 15018/R7Plus or for the 15011/R7.

I can't remember which one. I went back to stock before i wrote it down. However it is not the one which should be used which is 15023.

This is where i noticed i must have missed something. I checked my panel in the stock rom using DevCheck and under Graphics it lists the Panel:

oppo15023samsung s6e3fa3 1080p cmd mode dsi panel

so i checked my stock rom where it gets that info.

On the stock rom i have a file in "system/etc/" it is named

pp_calib_data_oppo15023samsung_s6e3fa3_1080p_cmd_mode_dsi_panel.xml

But this couldn't be it. So i assumed it must be the display driver in the kernel.

I looked into the CyanogenMod sources https://github.com/CyanogenMod/android_kernel_oppo_msm8939/tree/cm-13.0/arch/arm/boot/dts/qcom

and i was right. There was no 15023 display driver.

Long story short. How do I create and generate those dtsi files?

At the moment this is an Unofficial Rom but i plan to make it an Official Rom as soon as all problems have been fixed.

I hope anyone can help me on my porting "adventure" :)

This is my device tree: https://github.com/Celoxocis/android_device_oppo_r7sf
[Android Q&A, Help & Troubleshooting] celoxocis:
OMG, i was looking the other day at oppo-source github but i let myself fool by the "R7plus-5.1-kernel-source" naming and didn't look for the dts folder.

Thanks so much! :)

Could i simply copy the entire 15022 folder into

"cm-13.0\android\system\kernel\oppo\msm8939\arch\arm\boot\dts\qcom"

and compile the CM-rom?

I have a working device-tree and a working cm-rom, except proper display drivers. My guess is, it would include the display driver files in the kernel at my next compile.

Or would i have to edit specific files to make it work?

So far all i did was to simply copy the

cp cyanogenmod_r7plus_defconfig cyanogenmod_r7sf_defconfig which is in
cm-13.0/android/system/kernel/oppo/msm8939/arch/arm64/configs

and edit Android.mk in

cm-13.0/android/system/device/oppo/msm8939-common#

to include "r7sf"

LOCAL_PATH := $(call my-dir)

ifneq ($(filter r7sf f1f r5 r7 r7plus, $(TARGET_DEVICE)),)

One last question. What is the best way to make the Oppo R7Sf Officially supported by CM?

My device tree is already on github. I will soon commit the latest changes to it. I would really love for it to be included in CM Officially. :)
[Android Q&A, Help & Troubleshooting] maniac103:
You'll also need to add a top level dts file and add it to the Makefile. You can use the r5 commit as reference: http://review.cyanogenmod.org/143086

You'll also need to make some small modifications to get a working accelerometer: http://review.cyanogenmod.org/144868

What DTS to you use currently? Normally you should get an error by the bootloader as no DTS for 15022 is currently included.

Let's make it work first :) Once we have it working (by adding the missing kernel bits), we can have ciwrl fork the device tree to CM and include it in nightlies. Please make sure to put up all required changes outside of the device tree to Gerrit.

Gesendet von meinem R7plusf mit Tapatalk
[Android Q&A, Help & Troubleshooting] maniac103:
I'd suggest going a different route: diff e.g. the 15018 DTS between Oppo's release at oppo-source and CM. Then take the 15022 DTS off Oppo's kernel and apply the 15018 diff generated before onto that. You'll see at least the changes for the accelerometer interrupt and for the tfa9890 (the latter had reset pin and regulator definitions in the sound card in Oppo's kernel and has an own instantiation in ours)

The Makefile changes are required, the TS driver likely doesn't need any changes as the 15018 kernel already supports 15022. (BTW, the 15022 TS firmware is named differently from 15018. Make sure you're using the right one.)

You don't need those; those were required for the R5's USB/headset mux. When pointing to the R5 support commit I was mostly referring to the DTS changes, not the (C) code changes.

Why not? It's only a matter of building -eng instead of -userdebug. I somewhat doubt it's using the 15018 DTS. The DTS features the model number (https://github.com/CyanogenMod/andr.../boot/dts/qcom/msm8939-v3.0-mtp-15018.dts#L23) which the bootloader uses to figure out the DTS to use. If the bootloader fell back to use 15018, that would be kinda weird.

Maybe. It's unclear without further debugging. You can look in dmesg whether the kernel drivers found the right camera sensor. What blobs are you using? r7plus' verbatim or did you copy others off the stock ROM?

It's not just the panel being inverted? You can check whether orientation is correct in recovery. If it is, the accelerometer is off and needs further debugging/fixing.

With the old state of timestamps being off the issue was that orientation changes stopped working altogether after some time. It's unrelated to your issues which must be isolated to DTS, as sensor HAL + kernel driver is working just fine on r5, r7 and r7plus.

That's mostly trivial as most of those files are straight copies from the stock ROM, they're just renamed. Only the .eq files need conversion (text -> binary), you can use this tool for doing that.
[Android Q&A, Help & Troubleshooting] celoxocis:
You are right. That is the better route. I will see the changes and be able to apply add/delete the changes onto the 15022 DTS files.

Yes I saw the TS file naming in the source and have included those in my blob list already.

Should i use

"ifeq ($(CONFIG_OPPO_COMMON_SOFT),y)
+dtb-$(CONFIG_ARCH_MSM8916) += msm8939-mtp-15022.dtb

or rather

+dtb-$(CONFIG_ARCH_MSM8916) += msm8939-v3.0-mtp-15022.dtb

as the R7S was later released than the R7 Plus. It should be based of the R7 Plus.

I got curious too. I'm compiling and -eng version, once done I will flash and check the bootlog.

I extracted the dmesg and pasted it into pastebin here: http://pastebin.com/306q3xZS

Im using TWRP which has no rotation. I will flash CM recovery later and check if its correct in the recovery. :)

Thanks! I was looking how i would convert those two files a few weeks ago but didn't find sources.

This is a simple C-file compile?

gcc calc-biquad.c -o calc-biquad

While working on the sources and checking the diff's i discovered this difference between 15018 and 15022 (both oppo source).

Which i think could be the cause of the inverted rotation issue :)

Letf is 15018 and Right is 15022

(see attachment)
[Android Q&A, Help & Troubleshooting] maniac103:
Release date isn't relevant there. Check /sys/devices/soc0/revision - if it says 3.0 adding 3.0 to the DTS name is the right thing to do.

dmesg alone likely isn't sufficient here. From it it looks like the sensors don't come up, though. Not sure what exactly the problem is, but are you sure you have the right blobs? Initializing the camera is mostly done by the blobs. If you say it worked some time ago, please try whether the r5 introduction kernel commit broke anything for you.

Yeah, except you'll need the math library (-lm).

Yes, it could. It's almost as likely that the difference is normal, though, as those properties tell the driver how the sensor is mounted in the device, and the mounting orientation isn't necessarily the same between 15018 and 15022. Worth a try though.
[Android Q&A, Help & Troubleshooting] celoxocis:
Thanks! Checked and its "3.0" i applied 3.0 files.

I just finished adding 15022 files into the kernel and started the compile. I will look into the problem as soon as i finish flashing the new rom.

I found my eeprom file for the camera too. I used to extract all blobs because i did not know which was the correct one.

Yes i agree. I read about it online when i discovered the difference. The sensor is probably mounted differently in the R7S. We will see as soon as the compile is finished and i flashed the rom :)

So far the compile runs through without any complains to my kernel additions. I went with the suggested route. Diff CM-15018<->Oppo-15022 applied those changes to the Oppo-15022 files and got CM-15022.

I did not create a different defconfig for the R7S. I sticked with the settings from R7Plus. Just renamed it for dependency mode.

I noticed something. While i fixed up the TFA9890 files.

where did you get the "left.tfa9890_n1b12.patch" file from? it's not in the R7S nor R7Plus ColorOS stock rom.

i see one patch "TFA9890_N1C3_1_7_1.patch" which is renamed to "left.tfa9890_n1c2.patch"

i can see a second "coldboot.patch" but that looks empty and has not the same content as "left.tfa9890_n1c2.patch"

is it a generic file which is required for TFA9890? if yes. i guess i can simply copy and paste it. as "left.tfa9890_n1c2.patch" is identical in both roms?

for the compile i just copied the R7plus file as i didn't know where it came from. :)
[Android Q&A, Help & Troubleshooting] maniac103:
n1c2/3 and n1b12 are just different revisions of the tfa9890. r7plus stock firmware carried both files IIRC; it should be OK to omit n1b12 if the r7s doesn't have that revision.

Gesendet von meinem R7plusf mit Tapatalk
[Android Q&A, Help & Troubleshooting] celoxocis:
Ok i will just leave that file out of the blob list.

I had time today to flash my new build today and test it, which included the 15022 kernel inclusions and as i hoped all the issues i had, are gone! :)

Thanks alot for your help!

As far as tested:

Both cameras work!

Videocamera works!

All Sensors + GPS, Wifi work too!

Flashlight works.

Rotation issue fixed too! The guess about the sensor mounting was right!

Display driver is the correct one!

I have yet to grab a boot log. "adb logcat" before and while booting the device should be enough to catch everything. right?

The only thing left to do is to filter out the proper camera blobs.

Im using JackPotClavin's Android-Blob-Utility for that.

Can i leave out the blobs for Camera, Camera autofocus, Camera chromatix which are referenced in "lib64/" ?

I have seen that the R7Plus nor the R7f use these blobs in the proprietary-files.txt.

I will try to commit all changes to github on the next weekend. Once i finish updating the blobs list with the proper camera blobs. :)
[Android Q&A, Help & Troubleshooting] maniac103:
That's one option, another one would be strace'ing the camera daemon (in adb shell):

su
setprop ctl.stop qcamerasvr
strace -f -eopenat /system/bin/mm-qcamera-daemon

That'll tell you what blobs it tries to open.

Yeah, you can, the media stack is 32 bit only.
[Android Q&A, Help & Troubleshooting] celoxocis:
I finished the blob list but there is something i have been trying to fix for days and i can't really figure out whats the cause.

It is Wifi:

In Oppo Stock ColorOS everything is fine and stable. Wifi just works out of the box. It keeps switching between 2.4Ghz and 5Ghz depending where im in the house. (Signal strength)

I have a AVM Fritzbox 7490 with the latest firmware and all features. Dual band etc.

In CyanogenMod i keep having "drop outs". The Wifi is just dropping out. Like i have it turned off.

When i force it to use only 2.4Ghz band in wifi advanced options, it never happens. I believe it happens when it should automatically switch between 2.4Ghz and 5Ghz.

In my device tree im already using the "WCNSS_qcom_wlan_nv_15022.bin" as my "WCNSS_qcom_wlan_nv.bin"

I have already checked following files and made a diff for what the cause could be:

p2p_supplicant_overlay.conf = same as stock

WCNSS_qcom_cfg.ini = same as stock

wpa_supplicant.conf = wifi-direct settings disabled. we don't need that.

wpa_supplicant_overlay.conf = same as stock

It seems like i can fix the issue when enabling "Always allow Wi-Fi Roam Scans" and "Use legacy DHCP client" in Developer Options.

But here is the problem as soon as i reboot the device those settings are unchecked.

How can i make it permanent? Is there a way to make it permanent in the device tree? to compile the ROM using those settings as default?

I can even replicate the problem by turning off those two settings and walking around the house.

Any idea? :)

Update:

After hours of testing. With and without the above options.

Forced 5Ghz wifi is not stable at all. I tried all combinations getting 5Ghz to work, with no luck.

Forced 2.4Ghz works fine with and without above options. So my conclusion. It is definitly something wrong with how prima handles the 5Ghz.

In stock both work fine.
[Xperia Z5 Premium Q&A, Help & Troubleshooting] thedan55:
Hey guys

My brother bought an x5 premium but it's locked to EE. The first time he contacted EE they said it'll take 3 weeks, it didn't happen so he's contacted them another 3 or 4 times and they've not done anything. Now they're saying that Sony haven't released the code...... That doesn't sound right to me.

Has Anyone successfully unlocked their z5 premium?

Thanks
[Xperia Z5 Premium Q&A, Help & Troubleshooting] guhvanoh:
If you're in the U.K., Carphone Warehouse is where you get unlocked fones from. All the time.
[Xperia Z5 Premium Q&A, Help & Troubleshooting] thedan55:
You mean get them unlocked, or just get unlocked phones?
[Xperia Z5 Premium Q&A, Help & Troubleshooting] guhvanoh:
Carphone Warehouse only sell unlocked fones. So save yourself the hassle and get your fone there.
[Xperia Z5 Premium Q&A, Help & Troubleshooting] thedan55:
Right, but mind you, that's not what this thread is asking..... But thanks for the tip!
[Xperia Z5 Premium Q&A, Help & Troubleshooting] raven213:
i thought the phone was unlocked already?? when i bought mines it came unlocked
[Xperia Z5 Premium Q&A, Help & Troubleshooting] thedan55:
Hi mate, thanks for the reply. This phone is locked to EE and I'm having issues unlocking it, as I said in the op
[Xperia Z5 Premium Q&A, Help & Troubleshooting] raven213:
Only way i can think of is to buy an unlock code for it
[Xperia Z5 Premium Q&A, Help & Troubleshooting] thedan55:
Any recommendations of where? Someone trustworthy