Please point me in the right direction if this is not the correct sub for this.
The following repeatably shows in Logcat -
Failed to find provider info for com.facebook.katana.provider.AttributionIdProvider
I'm trying to determine why there is any indication of Facebook in the log. I do not currently have nor have I ever installed Facebook on this device.
Running PureNexus 7.1.1 build.
Apparently Instagram was making the call. Please delete.
Related
Hi everyone,
I''m facing a problem with my app. I alwys tested it with Android 4.1.2 on my galaxy note and it work perfectly, but since some days I updated my phone to android 4.3 and the application stopped to work: it works but it seems there is a problem with database. the view is blank and it seems that the db is empty.
I think theo problem is due to path and multi-users (available since Android 4.2, doesn't work also on Galaxy S4 of my friend with 4.2.2).
I tried to find a solution but doesn't found anything.
Even on the debug I haven't useful log. the only error I receive is the following:
API call with unopened database connection pointer
I think is due to a permission of the access the the right path, but it's very strange.
My phone is not rooted.
thank you for the help.
Maybe share the source code, where you open the db file?
shows us your source code
This is for: Samsung GT-I9300 (Android 4.1.2 Phone)
Context: We are mobile development consultants and one of a beta versions of the an app we did for client is crashing on client's devices. (It was delivered through Testflightapp but since the app immediately crashes before the testflight session begins, we don't see any debug logs or crash log via testflight)
We want our client to send us the logcat contents so we asked him to:
1) Turn on the Developer Options from Settings/About Phone/ and Touch 7 times on the "Build Number".
2) In Developer Options you will see "Take bug Report". Touch it and Touch Report and it will take some time to prepare the email. When the preparation is complete you will see a notification which will ask you to Share the Report.
He replied:
Looking in developer options and I don't see anything called "take bug report
We then actually checked the user manual of Samsung GT-i9300 Galaxy and it does not have the 'take bug report' feature.
Question: How can we access the logcat contents from the client's device without resorting to integrating a logging framework in the app ?
Dump state error log or adb
Hi Guys,
Has anyone tried the encryption feature found in Security settings? I'm using a recent nightly CM11 from Quarx/Blechd0se (Thanks, brilliant work!) quite stably for days now, but fail to make the encrypt phone function work...
When fully charged and USB powered, which are requirements, the successive encrypt phone buttons end up on a green android picture. This screen misses text and a progress bar which should normally appear on top of the screen, as seen on some screenshots. Even left for several hours, nothing progresses and a simple press on back button cancels action immediately which proves nothing has been encrypted in the meanwhile.
Took a Catlog and the only interesting message is the following:
Code:
01-02 01:34:23.732 E/Cryptfs ( 1197): Cannot get size of block device
In case it helps, find attached the output of mount command : View attachment mnt.txt
Could you have a look / help me out? (add to bug list if it applies)
In fact, for me, this function needs to be activated for connecting to my professional mails ...
Thanks in advance! :good:
Cheers
Further tested...
Hello all,
Just some more info... I flashed back to Quarx' CM9 and quickly tested once more the encryption and face the same problem but I didn't catlog, neither checked the mounts... Then I flashed Epsylon3's CM9 and quickly checked with the same result too...
But then I checked at catlog and now I get another type of error... Which is interesting and maybe promising as I already read some posts about this message...
Code:
04-14 21:11:13.101 E/Cryptfs ( 2219): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Problem seems to be more general than only Quarx/Blechd0se's CM11 but a friend uses a CM9 flavor on a Samsung Galaxy S and has encrypted the phone successfully...
All in all it's linked with the filesystem (block device or not), how it is formated (yaffs/ext3/ext4) and mounted (mount/mount_all)...
Some interesting reading on jira.cyanogenmod.org/browse/CYAN-87 (not linked, I don't have 10 posts yet)...
Hope to find, test and come back with some more info soon...:fingers-crossed:
Cheers!
Hi all,
The title says it all.
Whenever I try to enable a vpn based application I get an error. I've read somewhere that there's an app VpnDialogs.apk to enable it so I tried following the installation guide for an old version, but it wasn't meant to be for the S5 nor Marshmallow.
The error message in the attached pic.
Does someone know a fix for that?
Hi All
To begin with let me Thank All of You :highfive: who opted to participate in the Beta Testing Program for OOS/H2OS
(CBG / OBG / MPG / OTA) and help us Test the Beta's to make it better and better with every release. We are trying to introduce new features, eliminate the bugs and optimize the software for a better user experience, making OOS/H2OS the Best Optimized OEM Rom :fingers-crossed:
To do this we need regular feedback and bug reports/logs from our users to diagnose the issues and rectify them.
I see that although users are able to reproduce various issue, however very few know how to take logs and report. Thus to make it simpler, let me introduce you to the OnePlus Logkit which is a built in feature to capture logs and does not require root access or any special permissions. If you follow the below you can easily take logs and submit for further testing and it does not matter if you are rooted or a stock user.
Before we begin:
* Please make a clean flash to check weather the issue still persists before taking the log, most of the times a clean flash will solve your issue so we would appreciate if you do a clean flash before reporting any issue.
* We would appreciate logs without any mods like Magisk/Magisk Modules, Custom Kernels/AKT or any other Visual or SystemUI Mods
* This method should work on all OOS/H2OS Versions Beta's | Stable
* Use the Feedback app to submit the logs or upload and share the link with me so i can forward them to the ROM Team :fingers-crossed:
Follow the below steps to take logs on OOS/H2OS Beta or Stable using Oneplus Logkit:
1. Input *#800# from dialing interface to enter "oneplus logkit", delete history log :good:
2. Click "advanced", choose "save log type", select all these options (Kernel, Main, System, Radio, Event, Tcpdump), then click OK :good:
3. Click "save log", when it informs you whether to reboot, please reboot if the issue reoccurs easily, otherwise, click “cancel” :good:
4. Click "get QXDM Log, choose “modem-common”, roll down, click "open device log" :good:
5. Make the issue reproduce and take a screenshot to record the time :good:
6. Wait for few minutes (better above 10 minutes), click “save log” again to stop it, enter QXDM Log and choose “close device log” :good:
7. Enter file manager, choose storage, find the oem_log file, zip it and send it to us along with the screenshots :fingers-crossed:
As mentioned above use the Feedback app to submit the logs or upload and share the link with me so i can forward them to the ROM Team :fingers-crossed:
We will try out best to work on your logs and appreciate proper feedback.
Many Thanks for your love and support for OOS/H2OS
PS: Screenshots attached on the post below.
Screenshots
Screenshots Attached
Thanks bro,
Hope a longer support for the OP3/OP3T!
Telegram group created for early access to the latest