When I formatted persist partition, the lineageos fingerprint camera can not be used, the install MIUI9 fingerprint, camera repair, but if I install the camera system before and after the original set will mobilize the death card, WeChat will sweep the way stuck in MIUI flyme well what is the reason is the bottom board package...... I didn't use the data format and WQ, is now the biggest problem is the camera fault, why not native, you can help me, sorry my bad English
I'm sorry for you that no one could understand your English to find a fix for you
Related
Hi people!
I´ll like to ask something that has been bothering me; here´s some context:
I have a very very low end android phone (motorola xt303) and it was working the best it could, i was using link2sd normally (with an issue that i will tell you in a moment)... then the power button failed, i took it to waranty and they change the motherboard, basically i have a "new" phone now (On the inside xD)
Here´s the thing when i got my phone back, i rooted it and installed link2sd right away , i formated the 2nd partition of the SD before all of that, but now when i´m trying to link the apps i have a problem: if i just pick Link application it would work but if i choose to also link dalvik caché and libraries it won´t work, it would tell me: "Fail Create_link.blablablablablalbla: I/O error" - Check attached image.
What i´m doing or what i did wrong? before waranty i could link both dalvik and the libraries.
-And the other issue i had before (and now) was that even if linked most of my apps (Had in the internal storage the basics and most used (no more than 40MB) it would took my memory and ended up without space again (i had a bunch of apps tho), but i´ve found on foroums people who have many apps and most of the internal space avaliable.
I will really appreciate any help,.
Pd: if there´s something that you don´t fully understand about my writing i´ll try to explain to you (English is not my native lang)
Pd2: Really googled and searched here before posting but couldn´t really find anything that helps with my problem
No clue?
Tapatalk
Hi everyone !
So I've got a oneplus one (64Go internal memory), that I just upgraded from my custom ROM to marshmallow. I tried the stock one, then a custom cm13 based one from sultanxda, that I used with the private kernel of derromtester, and I had several fun experiences. However there is something that I don't like, whalich is that in this custom ROM raw camera and slow shutter are not permitted due to the oxygenOS library. Meanwhile I arrived to a very nice configuration of my application data and of my parameters. I thought of dirty flashing the stock ROM (it will erase all the way I personalised my home screen, the screen resolution and all that stuff right ? Does titanium backup change anything to it ?).
Anyway I wanted to make a backup in case Ilit didn't go well. However, I couldn't! Whereas I should have had like 14 Go of free memory, I had like 14 only... And it seems like my storage is only 54Go now, and not 64 anymore. The computer sees the same in mtp mode. Where are those 10Go gone ??
Long story short, 10Go of my memory vanished and I have no idea why and where...
Thanks for your answers !
Could it be an unmounted partition ? Which one ?
Hello,
this is my first post.
My D6503's Camera stopped working after I updated to MM, well only after I played around with the permissions for the google services app. My phone was running stock and I didn't think that anything serious would happen.
I denied the google services permission to my camera in order to cut down on its power usage, unfortunately my camera and torch is now unable to open and keeps saying that the camera is unavailable.
I've tried various third party apps, when I launch them they say the camera is in use.
I've also noticed that my battery life has severely decreased as the camera itself is warm and I think it doesn't shut off.
Since then I've reset the permissions, factory reset, wiped the caches (including the dalvik) various times, rooted and installed a recovery and wiped everything, I've flashed every conceivable stock rom and currently I'm running a custom rom for a locked bootloader.
A few things that I've been wondering:
1.) Is it possible to reinstall or flash the hardware drivers specifically for the phone?
2.) Might I be able to fix this problem by unlocking my bootloader and installing a custom kernel and then reverting back to stock and restoring the TA partition?
3.) is it possible to totally wipe the phone's partition and install everything from scratch?
4.) The sony android system used to have a browser app that is now disabled and replaced by chrome, I've noticed that the browser app is actually still available in the software but a setting somewhere is specifically blocking the use for it. Might there be a service setting that I could reset to gain the function of my camera again?
5.) Might my TA partition settings be influencing my camera somehow (maybe after being corrupted) and is there a way that I could change the settings or edit my TA partition?
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.
EDIT
This issue was fixed. The problem is with the persist partition getting corrupted on some devices. The reasons are not clear, but we have strong reasons to believe this is due to TWRP's implementation of leaving logs and cache files on the /persist partition, which is limited in size. The log files often exceed 20MB in size and cause the sensor config and calibration files to become corrupted on that partition.
Steps to get this fixed:
Obtain a working persist.img from someone (it is device specific. You can find the ones for crosshatch and blueline on this thread, but will have to ask someone else for other devices)
Replace your persist partition with the persist.img you obtained. This needs to be done using an advanced command (dd) and you need to be on Android 9 in TWRP (rooted) to do this. Read the thread (around page 19) for more details.
Flash Android 10 (does not need to be a clean install, but clean install is always recommended).
WARNING: replacing your persist partition with someone else's (even the same device) WILL replace your original, unique factory calibration data with someone else's. This includes audio config files, camera calibration files, sensor calibration files. Backup your original /partition image before doing this and only do this if it is absolutely necessary. You have been warned!
No one on this thread assumes responsibility for anything bad happening to your device. It worked for all of us, but is not guaranteed to work for you. Still no news from Google, who are still investigating.
ORIGINAL THREAD
Starting a new thread here from the old one: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-final-version-release-t3963794/page7
What is the problem?
Many users of Pixel 3 XL, Pixel 3, Pixel 2 XL and even the OG Pixel are reporting a major bug after upgrading to Android 10. All the sensors seem to be disabled.
This includes Active Edge, Proximity Sensor, Ambient Light Sensor, Auto-brightness, Accelerometer (Auto-rotation, flip to shhh, double tap to wake and lift to wake). All of these are dead on Android 10.
What we know:
Whether we upgrade directly from Android Pie or do a clean install using the factory images does not seem to matter. The issue only affects a certain set of users and only goes away if we revert to Pie. The phone works perfectly then.
Manually erasing all partitions and installing from the image does not work either.
Installing Android 10 individually on partitions A and B does not help either.
Re-locking the bootloader and returning completely to stock does not work either.
The only thing in common for all of us is that we were all rooted and/ or using a custom kernel in the past. However, some others who had been rooted and using custom kernels/ ROMs report they do not face this issue.
Interestingly, for users on the beta program, they started noticing this issue around Beta 6. Post-that, even if they reverted to an older Beta 3,4 or 5 which did not have this problem, they would face this problem after Beta 6. And this is continues with the public version now.
Some users suspect this could be happening due to "something left-over somewhere hidden on the phone." (not verified, but makes sense, in theory)
Coverage
This issue is widely covered now:
https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/
https://www.androidauthority.com/pixel-sensors-android-10-1026027/
https://9to5google.com/2019/09/05/pixel-active-edge-sensors-android-10/
https://mobilesyrup.com/2019/09/05/pixel-users-experience-dead-sensors-post-android-10-update/
... and many more
Next steps:
If you face this issue, please add your comments and what you have tried here and update the bug on Google's issue tracker that we have filed here:
https://issuetracker.google.com/issues/140476661
There is also a help center article on Google's support forum that you can upvote here: https://support.google.com/pixelphone/thread/13511202?hl=en