yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG V10 Q&A, Help & Troubleshooting] AnonVendetta:
[MENTION=5395086]YrrchSebor[/MENTION]: I just got my unlock about half an hour ago. I didn't call that lady, I just kept calling and asking to speak to supervisors until my request was elevated. Finally, they asked for email and said to wait 3 days. I dont know exactly what happened, but I think they added my IMEI to unlock database. I got the email, ran Unlock app again, worked first time around.
[T-Mobile LG V10 Q&A, Help & Troubleshooting] YrrchSebor:
Glad you finally got it [emoji106]
[T-Mobile Note 7  Questions & Answers] raf1919:
Is there way to remove the search bar in sms messages app? I would like to get my fav contacts back like in S7 or at least just get rid of search bar.
[T-Mobile Note 7  Questions & Answers] suzook:
I hate it too.
[T-Mobile Note 7  Questions & Answers] raf1919:
No fix outside of rooting than I assume.
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
For weeks now my Google App randomly stops responding and forces a Soft reboot.

I have no idea how its triggered. I have a logcat where I think I caught all of the error.

I have no idea how to read it and see whats causing the error!

Logcat:

https://mega.nz/#!7ZRwkIrS!FL1oeP6udLer__2g6TZoOvU1O_oHTKBolJwShypgoB0
[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
Have you flashed any Gapps for your device and ROM? It could be that your current version is not rhe right version for your device/rom.. Try google search gapps for Nexus 6P marshmallow, or whatever rom you're on. Hope that helps

Sent from Sony Xperia Z5 E6653
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
Again this is an error thats been happening for weeks! Prior to that I had 0 problems with the same setup.

I am using OpenGapps Arm64 6.0 just like the Official Cyanogenmod site says. Those are the officially supported gapps!
[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
If im seeing the logcat correcly, you seem to be having SU issues... has your device given you any SuperSU errors/crashes??

If possible,

Boot in to Recovery.

Reflash your Gapps.zip file via recovery

before rebooting out of recovery make sure to clean/wipe cache data and dalvik cache first

then reboot to system.. you may need to download your Apps Again though which shouldnt be a problem..

another way to fix the issue is ONLY able to be done if your device doesnt keep force rebooting your device..

other wise the quickest way would be just to navigate to Settings>Apps>Google Play Store> Clear App Data and Restore App Defaults... Then navigate to Settings>Apps>Google Play Services> Clear App Data and Restore App Defaults, then clear your memory cache..

Then reboot phone and viola.. You should be all good :).
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
Thing is as I mentioned above. Again this is one of the dozens of clean installs ive done! Cyanogenmod has Root built in. Its permanent and a part of the system. This is a problem on clean install you see. There is literally no cache or data to be deleted. Even after I wipe those and I go and set the phone up again it happens again... over and over. I have tried multiple versions etc.

Can you please give me more detailed info from the logcat! This has been really helpful.
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
I dont know if I mentioned this but this is a clean install done a day ago. The gapps package is as new as it can get. Also YES! This started AFTER a Google App update. Before a certain update Nothing like this happened at all!

I have a Nexus 6P which obviously comes with Stock Gapps package. Id flash nothing less than that. I am using a Nexus Phone and as that I love the Google Now Launcher. Sadly because of that I NEED to use the latest Google App to be able to use the phone fully.

As for the missing System files I have no idea how thats happening. Can I just ask you if there is any way to find out if The missing system files messages are caused by GAPPS apps. If so then I think flashing Gapps over Cyanogenmod as system apps when its not stock android and is obviously modified might cause the thing to happen.

I dont know how GAPPS cam ever be corrupt since as I said this has been happening over the past month and ive clean installed it many times with different versions of TWRP, OpenGapps and Cyanogenmod to take the same result. In the Recovery Log file I get no errors so that is strange.

Also god damn /system/priv-app/Velvet/lib/arm64/ is the Google Search app.... I literally think it jus cant use it since its installing things as SYSTEM apps ona System that is not Stock android and thats why this is happening.

Hey I just opened the location in this part of my crash report:

09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B]

I opened the Google search APK file. .... Its not arm64. The folder inside the APK is called arm64-v8a!

Can that cause the problem?
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
[MENTION=7347494]TheTecXpert[/MENTION] Thank you so much! I feel like Im finally getting somewhere wherever that is.

Whatever 09-03 02:07:55.994 16912 16912 W System : ClassLoader referenced unknown path: /system/priv-app/Velvet/lib/arm64[/B] means and from wherever it is its looking in the wrong place! The Google App that came with OpenGapps has arm64-v8a instead of arm64. I checked in the Opengapps archive as well!

Its like that on all my previous backups from months ago as well. It was fine back then so:

Is there ANY way you can tell me what is trying to referenced unknown path: /system/priv-app/Velvet/lib/arm64 ? Is it the Quick Search Box relaunching?
[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
Nah I don't think that would be causing the problem. Because you ARE on an ARM64 chipset.. And i dont even think gapps comes with v7 v8 specifically (not that I have seen)..

Its usually categorised as arm And arm64.. Yeah while looking through the logcat, there are actual system specific files that a missing and also writing to device permissions are being blocked.. I read somewhere that the problem with the 2 most latest gapps packages were causing all sorts of problems with peoples nexus 6p devices.. Thats why initially I thought that your actual rom build or the gapps package itself could have been corrupt.. If you look carefully in your logcat.. You will see letters and then the log event description..

D/debug

E/error

W/warn

I/information

F/fatal

You will notice a bizarre amount of errors, and quiet a few fatals and most of them are android.google. Related, and system related..

Now if you look further in to your logcat.. You will see are very unpleasant error (any several of them) where the system is trying to write data to the disk/filesystem, but it is giving you SU errors and unable to write data to disk as you dont have permission to do so. Meaning somewhere along the line, su issues CAN infact cause reboots since theres no permission to write to the system/disk..

In recovery do you have the system partition mounted as read only Or mounted with read and write enabled?

If the above mount settings doesn't make any difference even with r/w permissions.

Then try the following.

Boot to recovery, uninstall your current superSU version.. or just simply flash/Reflash SuperSU V2.76, update the binaries etc. Hopefuly that will atleast fix the w/r permissions.

The reason why im suggesting to Reflash superSU IS because in your logcat, you are receiving constant sigpipe errors (aka sigfaulting) which is a sign that something is wrong with your root

Sent from Sony Xperia Z5 E6653
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
This is getting more and more complicated becauss sadly I can not. I never flashed SuperSU in the first place. Again its deeply integrated into Cyanogenmod itself. It comes with it on the ROM and its even deep in he settings.
[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
Hey mate.. i have good news for ya.. I just found the factory image for your device which will COMPLETELY set your device back to COMPLETE factory stock.. the zip file has everything necessary to get your device back to working order as if it were straight out of the box..

First Download the file below on your PC.

https://dl.google.com/dl/android/aosp/angler-mtc20f-factory-4355fe06.zip

then..

Open your Adb & fastboot terminal program

Extract the downloaded zip file into it's own directory (by default it will create its own directory and folder structure)..

Next open the extracted folder and (twice) and you will see a bunch of files.. move ALL of the files to the Root directory of ADB and Fastboot Terminal program so that all the files are in the same folder as your terminal program.

Next just drag the "flash-all.bat" file into the terminal window with your mouse and hit enter..

the script should then execute and once it has completed your device will reboot.

I've attached screenshots just for a reference for ya..
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
I forgot to mention a few things. Im not really new to android. I know about the factory images from google. Tried the latest 6.0.1 image from Google a FEW times already as well as the OTA updates from google. I know it will flash everything and erase the partitions. I have even tried erasing the partitions myself and resizing them. It is not the problem. I have even flashed them all individually via fastboot and erased partitions as well that way. Im not new to android. Ive been here for a while now but THIS problem is beyond me.

For a reference of how much my Android knowledge is at this point refer to my guide where me and the TWRP devs found a bug in the latest TWRP version that was bricking the EFS partition of Nexus 6P devices by looking through the kernel logs and helpes people fix it by deleting the corrupt EFS partition via Shell : http://xdaforums.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119

I simply dont want to use stock android. I want my custom rom. I know my way around android a bit but understanding the logcat for some reason is beyond me. I just have no idea about this issue.

As you can see because im not new I have tried everything I know! And YES Stock Android for my device DOES NOT have this issue but its stock android after all. Im trying to fix it on Cyanogenmod.

The thing I forgot to mention was that its not really a clean install. Well it is BUT once I get to the First Time Google Setup I do choose to restore all the apps and homescreen layout from one of my previous Nexus 6Ps. All that does it it restores your homescreen layout and reinstalls all the apps freshly from Google play which is 216 apps so far. All the apps are freshly installed so I dont think it can cause harm.
[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
after you restore your apps.. does your device start to boot loop?
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
No. It does not. After a few min of it working fully fine with all my apps then the problem happens. The Google app stops responding and it causes a reboot. I havent gotten any reboots! Its not on a timer as well. Right now Its been a whole 10 hours with no reboot or crash! It will happen again however. It always does.

Ususally with things like these there is an app that is causing it or 2 apps that dont play well witch each other who cause the problem. Thats why I also posted the logcat. To see if 2 apps didnt play well with each other but since that is not the case its super confusing.
[Nexus 6P Q&A, Help & Troubleshooting] blitzkriegger:
At this point it is highly likely that something amiss happened to your backup of the google app, as the issue only kicks in after you restore it. If you have automatic backup enabled in the past then there's a possibility that onecof the backup points for the app got compromised.

I don't use the backup/restore feature that much, but if i recall correctly during initial set-up you have the option to manually choose which apps to restore correct? If that's the case restore everything except for the google app. If you come from a totally clean install (which includes setting up the phine as new/not restoring app from cloud) I'm fairly certain the reboot issue with the google app won't happen.
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
The backup isnt really a backup. Google simply saves the name of the app and ten cleanly reinstalls them from Google Play. Its not restoring one of my previous apps. Its just installing them straight from Google Play cleanly.

Once Cyanogenmod 14 based on Android 7.0 comes out I plan to do a FULL clean wipe with no restores and set it up as a brand new phone. That seems to be the best option. Till then im just going to live with it. If THEN it causes the same problems with no restored settings or things we will know what the problem is.

Thank you a lot for the help! [MENTION=7347494]TheTecXpert[/MENTION] Is it a problem for me to write here again and reference you if I need more help? After a month of searching and people trying to help and failing you were the only person who was able to read the logcat and provide some insight on what TF has been happening inside! Its gonna be a few weeks/months since Cyanogen takes time.
[Nexus 6P Q&A, Help & Troubleshooting] blitzkriegger:
I did try to read your log as well yesterday out of curiosity but I did not fully understand everything in it :D What I was able to pinpoint was what happened right before your phone did the soft reboot :

09-03 02:05:20.676 947 961 I ActivityManager: Killing 4473:com.google.android.googlequicksearchbox:search/u0a36 (adj 0): bg anr

09-03 02:05:20.717 947 958 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ id=5, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ], android.os.BinderProxy@9a342dd)

09-03 02:05:20.718 947 3522 D WifiService: Client connection lost with reason: 4

09-03 02:05:20.718 947 3523 D ConnectivityService: releasing NetworkRequest NetworkRequest [ id=5, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]

09-03 02:05:20.719 947 3523 E ConnectivityService: RemoteException caught trying to send a callback msg for NetworkRequest [ id=5, legacyType=-1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED] ]

09-03 02:05:20.725 947 4958 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.service.SearchService in 1000ms

09-03 02:05:20.726 947 4958 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.search.core.BroadcastListenerService in 11000ms

09-03 02:05:20.726 947 4958 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.sidekick.main.remoteservice.NowService in 21000ms

09-03 02:05:20.733 16099 16099 E ReflectionService: Message dropped: the service handler is null.

09-03 02:05:20.737 14183 14183 I Finsky : [1] com.google.android.vending.verifier.PackageVerificationReceiver.onReceive(2102): Skipping verification because own installation

09-03 02:05:20.946 947 971 I PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/vmdl962661913.tmp/base.apk pkg=scd.lcex isa=arm64 vmSafeMode=false debuggable=false oatDir = /data/app/vmdl962661913.tmp/oat bootComplete=true

I don't have enough technical knowledge though to know what caused the crash to happen. Just a thought did you make any changes to privacy guard settings related to google play services in the past?
[Nexus 6P Q&A, Help & Troubleshooting] TheTecXpert:
Of course you can mate.. Feel free to call upon me whenever you need to.

Oh by the way, did i mention that this line

09-03 02:05:20.676 947 961 I ActivityManager: Killing 4473:com.google.android.googlequicksearchbox:searc h/u0a36 (adj 0): bg anr <--- bg anr = Background App Not Responding (so your searchbox is crashing).. uninstall it and clear all of the leftover app cache and data.. then reboot the device.. then reinstall your Google Search App from google play store.. don't restore it from a backup..

then take another logcat and see where the NEXT crash starts.. is that making sense ??? its an effective way of narrowing down the root cause of the problem..

try that first, then get back to me with the result..
[Galaxy Note 3 Android Development] bearusa:
And on that note...thread closed, insult my crew you insult me. [MENTION=4207059]sparx
[Galaxy Note 3 Android Development] ant0nius:
My neck beard stroke is strong today. Please respect the work and authority of devs, friends.
[Galaxy Note 3 Android Development] dikkebas:
Nothing much left to say....

Check the link in my signature for some solace
[Galaxy Note 3 Android Development] sawdoctor:
Thread Closed,

Anymore language like this from anyone and action will be taken against their account

Regards

Moderation Team
[MTCB Android Head Units Q&A] vlaine:
My usb ports are dead. Wifi also.

Everything else is working fine so it's not a big problem

The only thing I'm missing is my dashcam.

Is there an app to record using AV Input ?
[Nexus 6P Q&A, Help & Troubleshooting] A380:
Encrypted 6P with Nougat here. A week after flashing the OTA, unlocking the phone with the initial pin code worked fine, but I started having problems unlocking the phone again by swiping. It just wouldn't be swiped out of the way. It became more and more difficult . Had to reboot all the time in order to get access to the phone, through the pin code unlock.

Initially reflashing the OTA and removing 'trusted locations' for smart unlock seemed to do the trick. 10 hours later the phone went into the same problematic lock screen mode again. This time without any trusted locations.

Installed an alternative lock screen to see if that would work. This required disabling the default lock screen...

After the next boot up, the phone says that the password was correct, but 'decryption was unsuccessful" and the data is corrupt. Will need to perform a factory reset.

Does anyone know a way to avoid resetting the phone? Flashing back to the latest Marshmallow did not help.

Thanks so much.
[Nexus 6P Q&A, Help & Troubleshooting] A380:
OK, for anyone else finding themselves in this situation: make sure you get your backups off the phone before it's too late.

After a factory reset to Nougat everything is fine, but all my stuff is gone.
[Android Head-Units] oyedejia:
my head unit is a gs version with rk3066 cpu, with 1024mb ram.its about a year i installed it.recently,in about 3-4 wks ago,I noticed the unit is kind of very slow compare to when it was installed and it also hangs with no response too often.This made me to check the unit settings and i discovered the ram size has reduded from 1024 mb to 512mb.has anyone experience this issue before? and if there is any solution to return it to its original 1024 mb.

Thank You.
[Android Q&A, Help & Troubleshooting] Solidcancer07:
A very warm Hi! to the XDA community :)

My phone, the Sony Xperia E4, does not have a recovery - so I am slowly learning how to develop one. It has an MT6582 chip.

In the process I have obtained the stock boot.img (via boot.sin) from the phone's stock .ftf firmaware file.

I wish to use MTK droid tools to create the recovery, however it first gave me the error that the boot.img file is not split. After some research I came to learn that such boot.img files need to be split into the kernal (Zimage i believe) and ramdisk.

After some further research I came across this seemingly helpful guide and tool on how to split the boot.img file on Windows (unfortunately I do not have Linux at my disposal atm).

Now to my issue: (referring to the aforementioned guide & tool) When running the command

bootimg.exe --unpack-bootimg boot.img

I get this error:

AssertionError: invald bootimg

Which leads me to believe the boot.img file I have extracted may be corrupt or extracted from the wrong .sin file.

If you are still with me, how can i confirm that the boot.img file from the stock rom is indeed "working" and contains ramdisk and kernal?

Some extra information:

This is the guide I used to initially extract the boot.img file from my phones stock firmware. They highlight that boot.img is extracted from the kernal.sin file. My firmware has no such file. Later in the comments it mentions that newer Sony phones have the boot.img file in the appropriately named "boot.sin" file. This is the file i used to extract my boot.img. Thus from here I cannot see why the boot.img file cannot be split.

The full command line and response is:

C:\Users\\Downloads\Cofface>bootimg.exe --unpack-bootimg boot.img
arguments: [bootimg file]
bootimg file: boot.img
output: kernel[.gz] ramdisk[.gz] second[.gz]
Traceback (most recent call last):
File "<string>", line 2213, in <module>
File "<string>", line 1424, in unpack_bootimg
File "<string>", line 151, in parse_bootimg
AssertionError: invald bootimg

Thanks very much in advance! :)
[Android Q&A, Help & Troubleshooting] spencersir2:
Finally have a quick fix for the drain issue, and I am sorry not at a place where I can post pictures, but go to battery optimization and turn of Bluetooth share and whatever app you use with Bluetooth(for me it is Google play) and un-optimize it. I don't think it is a Bluetooth antenna issue it is a doze issue. And after you try it post here and let me know if it is just me or not
[Android Apps and Games] Sahaab:
"OctaBall" On Play Store

PlayStore Link

Ping Pong in an Octagon

Control the paddles to keep the ball within the octagon.

Instructions :

Right side of the screen turns paddles clockwise

Left side of the screen turns paddles anticlockwise

Upper half of the screen turns paddles faster

Lower half of the screen turns paddles slower

Some feedback would be great, thank you very much.

http://imgur.com/JlaawjK

[YOUTUBE]https://www.youtube.com/watch?v=1IJCURNiShM[/YOUTUBE]
[Verizon Note 7  Questions & Answers] badboyg200:
Why does the HD video call not work across carriers??? I don't understand this at all.. there's no need for Google Duo if they can just make the devices talk amongst carriers.. anybody know the specifics behind this?

I.e. I can't use the built in video call to call my gf ATT N7 from my Verizon N7
[Verizon Note 7  Questions & Answers] seh6183:
Well google duo is a google thing and the built in video chat in the dialer is a samsung thing. Even if they were to work across carriers, both phones would have to be newer samsungs. Google duo is for people with any phone manufacturer who want to video chat between each other.
[Sony Cross-Device Development Themes and Apps] Guetto Design:
Hello Friends

again here I bring some of my work

in material design apps camera sony

I hope you like my work ;)

Thank you

​

[/CENTER][/B]

new icons material desing

Latest updates

Screen shots

​

Downloads

Fun AR

Click here To download

Motion Shot

Click here To download

Don't forget to thank me if you like/love my work
[Sony Cross-Device Development Themes and Apps] Cromwellfenix:
Thanks, do you have the apps 4k and timeshift, face in or any other ? Please share
[Sony Cross-Device Development Themes and Apps] maple_mak:
Great icon design! But don't forget to add some shadow to some details because it's Material Design!
[Note 7 Questions & Answers] millicent:
Is it possible on stock device? I have tried all my tricks, no luck so far. Thanks for any idea on how to make it work.
[Note 7 Questions & Answers] Kansatsusha:
adapters or usb drive with the C connection? Also have to be formatted as fat32
[Note 7 Questions & Answers] millicent:
Using the usbc adapter. I have also tried fat32, the otg device is still not detected. I have tried stick mount but that fc instantly when I select mount.
[Note 7 Questions & Answers] rcobourn:
Something wrong with your port? It works fine for me with the included adapter. Suggest you try on a store display model for comparison.
[Note 7 Questions & Answers] Kansatsusha:
How it respond when u put it in?