Hi, I've flashed my US Le 1 Pro first with Beta Hydri v4 but because I had the malware stock US rom it came with the phone. In the stock rom Hifi and that changing display didn't worked but i didn´t really care but everything else did , like gyroscope and compass (and very well) but since i've flashed to Beta Hydri v4 with full wipe, some axis are inverted, I think X in accelerometer is outputing negative values instead of positive.
I've trying flash other roms (like cuocu92 14s and the original stock I had from my backup) but didn´t worked. I'm so sad because I've just bought 2 days ago the bobovr z4 so i could use it for vr.... :'(
Can someone help me?
I noticed this problem when I tried to use Google Camera for (360° spherical panoramas) very frustrating.
At this moment one solution is use other phone to VR.
simondd said:
At this moment one solution is use other phone to VR.
Click to expand...
Click to collapse
It works with original rom but you have to wipe everything except your sdcard.
At least for me now working perfectly.
I am having the same issue. My phone is rooted. I am surprised there are no apps or anything that can invert the VR for us.
CM 12.1
dreamwalkerfx said:
I am having the same issue. My phone is rooted. I am surprised there are no apps or anything that can invert the VR for us.
CM 12.1
Click to expand...
Click to collapse
Thanks to @BetaHydri, he fixed this issue in the CM12.1 V4.2
Additional Infos about how to fix
Thanks very much for the quick reply!
I flashed to 4.2b using TWRP and then installed the gapps, I really did not want to format my device.
4.2b fixed my GPS issue thank God, but the VR is still inverted.
Went into TWRP file manager using recovery, and tried to move the new .conf file from the 4.2b zip to the /sensors/etc folder.
This didn't seem to help at all. There is still nothing in the /persist folder.
Any ideas would be appreciated.
Cheers
dreamwalkerfx said:
Thanks very much for the quick reply!
I flashed to 4.2b using TWRP and then installed the gapps, I really did not want to format my device.
4.2b fixed my GPS issue thank God, but the VR is still inverted.
Went into TWRP file manager using recovery, and tried to move the new .conf file from the 4.2b zip to the /sensors/etc folder.
This didn't seem to help at all. There is still nothing in the /persist folder.
Any ideas would be appreciated.
Cheers
Click to expand...
Click to collapse
First time I flashed the V4.2, I came from the Stock Rom, it didn't fix the Gyro problem, but as I remember you should delete/rename these files first (sensor_def_qcomdev.conf - sensors_settings - sns.reg) then in TWRP do a factory rest and wipe Dalvik + Cache.
Reflash the Rom again.
Thanks for the quick response.
Unfortunately with the lack of time I can't look at factory reset... it would take me forever to re-load all apps, docs, pictures, etc.
I am wondering if there's a manual way to do this through TWRP -- ie. copying the correct sensor files into their respective folders, clearing cache, and seeing if that works.. right now my /persist folder is empty
If anybody has a chance that has a working gyro, I'd love a copy of their sensors folders both in persist and system.
dreamwalkerfx said:
Thanks for the quick response.
Unfortunately with the lack of time I can't look at factory reset... it would take me forever to re-load all apps, docs, pictures, etc.
I am wondering if there's a manual way to do this through TWRP -- ie. copying the correct sensor files into their respective folders, clearing cache, and seeing if that works.. right now my /persist folder is empty
If anybody has a chance that has a working gyro, I'd love a copy of their sensors folders both in persist and system.
Click to expand...
Click to collapse
The factory reset doesn't wipe your internal storage, only the apps installed and settings will be restored to default.
Anyways, if tomorrow I get free time I will upload the files needed for you.
Does your GPs lock on OK?
May need to reflash, no idea what I did wrong but the GPS does not work. Bounces around the map every few minutes.
I can confirm, I reflashed today -exactly- as instructed on the instructions in the 4.2b thread, re-installed all apps, etc etc.. an hour process at least..
The gyroscope is still inverted,
After dalvik + cache cleanup in TWRP and after boot you should have in /persist/sensors folder three files:
1. error_log
2. sensors_settings
3. sns.reg (this has now all new settings in an encrypred format from the sensor_def_qcomdev.conf file)
And on /system/etc/sensors only that above mentioned clear text sensor_def_qcomdev.conf file.
Click to expand...
Click to collapse
and there is still -nothing- in the /persist folder...
I have the one file in /system/etc/sensors, but I don't have it in /persist.
I'm ready to throw this phone out the window
---------- Post added at 06:22 PM ---------- Previous post was at 05:36 PM ----------
My bad, there are the 3 files in the persist folder (had to activate root explorer in ES).
No idea why it's not working.
For the GPS, I have no idea because I don't use it at all. Go to CM 12.1 BetaHydri thread
I attached a Zip file contain all files with their respective directories as shown below.
Code:
system/etc/sensors/sensor_def_qcomdev.conf
etc/sensors/sensor_def_qcomdev.conf
persist/sensors/error_log
persist/sensors/sensors_settings
persist/sensors/sns.reg
Good luck.
nsmsdz, you are the man.
After replacing all the files/overwriting, and a reboot, it works fantastic.
May the Android Gods be with you always.
help
Hello.
I lama, I need help. He tried more ROM, still the same problem. I do not know if this one problem, I do not know how to delete and replace files. The phone ROOT files, but I can not see. Thank you very much for your help.
Sorry for the English, translated into translator.
Newbie can not embed the video, this is the only way
video:
youtu.be/YDJmj_dM8CY
Related
Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.
Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.
I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.
4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium
No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.
Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?
I fixed this deleting the "pictures" folder with RootExplorer.
jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .
My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!
Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.
Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0
/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk
The gallery detects no images and the music player finds no music. I have many folders full of images and "music" folder filled with music. ES file manager can detect and view/play image-/music files.
I recently installed the latets version CM9 and I have never had this issue before. Third party music apps are also unabe to detect music. Factory reset does not help. Deleting cache and data in settings does not help. There is no issue with .nomedia files.
Don't know what to do really. Any answer is greatly appreciated.
re-flash the rom
Charl96 said:
The gallery detects no images and the music player finds no music. I have many folders full of images and "music" folder filled with music. ES file manager can detect and view/play image-/music files.
I recently installed the latets version CM9 and I have never had this issue before. Third party music apps are also unabe to detect music. Factory reset does not help. Deleting cache and data in settings does not help. There is no issue with .nomedia files.
Don't know what to do really. Any answer is greatly appreciated.
Click to expand...
Click to collapse
Its very obvious!
If reflashing doesnt work, try putting all the music files in the root of the sd card and not in folders as you did now!
gire.prasad said:
Its very obvious!
If reflashing doesnt work, try putting all the music files in the root of the sd card and not in folders as you did now!
Click to expand...
Click to collapse
Horrible option. Makes the whole "hierarchical filesystem"-thing pointless, and the SD-Card looking extremely confused (I like having a /sdcard/music/ folder, and even more folders in that. And camera also saves pictures to subfolders of /sdcard/.). There has to be another way. On my GNex CM9 doesn't have this problem, so it isn't ROM-related, and Gingerbread isn't making this trouble, too. Just as a start to exclude options on the "why".
(But, yes, I've tried that with one file, and it works. For people interested in shabby workaround and not in real fix it'll probably do the trick. (Except for (camera) pictures. Camera saves in /sdcard/DCIM/blabla. No way to change that.))
abnah said:
Horrible option. Makes the whole "hierarchical filesystem"-thing pointless, and the SD-Card looking extremely confused (I like having a /sdcard/music/ folder, and even more folders in that. And camera also saves pictures to subfolders of /sdcard/.). There has to be another way. On my GNex CM9 doesn't have this problem, so it isn't ROM-related, and Gingerbread isn't making this trouble, too. Just as a start to exclude options on the "why".
(But, yes, I've tried that with one file, and it works. For people interested in shabby workaround and not in real fix it'll probably do the trick. (Except for (camera) pictures. Camera saves in /sdcard/DCIM/blabla. No way to change that.))
Click to expand...
Click to collapse
I'm gonna try putting 1 mp3 file on root and delete any .nomedia file too see if it works, if not I'll reflash.
Same with gallery, it can't hurt..
By the way I noticed the gallery shows pictures taken after I deleted the ROM but if I place old photos in that same folder they don't show up...
Thanks for all the answers
PS. I did full wipe before installing the ROM and will wipe everything again..
dammit I ****ed up, did wipe and didn't root again so when I flashed the ROM it didn't boot. Flashing 2.3.4 Stock FTF file now. Thanks anyway.
Just FYI: Putting files to the root of /sdcard is not a longterm solution, after reboot they don't show up again. Niether clearing Media Storage's data nor wiping cache nor dalvik cache, nor fixing permissions works as a solution. That is really f*cked up.
Edit: No changes in ongoing nightlies on that. Hopefully: Yet. But I wouldn't bet on it.
SOLVED!
This is not a ROM problem! It could happen to anyone using ROM Manager!
How-to fix:
1. Download and install the latest ROM Manager APK from their website.
2. Delete the .nomedia file in /sdcard/android/data/ (ROM Manager 5.0.1.3 put a bad one there, the new version will be good).
3. Clear the data for Media Storage in Settings > Apps.
4. Reboot.
5. Wait. Re-indexing can need a while.
Credits go to the guys from the awesome Galaxy Nexus forum. Especially to Dragn4rce for creating this thread and kyokeun1234 for pointing out aboves easier solution.
abnah said:
This is not a ROM problem! It could happen to anyone using ROM Manager!
How-to fix:
1. Download and install the latest ROM Manager APK from their website.
2. Delete the .nomedia file in /sdcard/android/data/ (ROM Manager 5.0.1.3 put a bad one there, the new version will be good).
3. Clear the data for Media Storage in Settings > Apps.
4. Reboot.
5. Wait. Re-indexing can need a while.
Credits go to the guys from the awesome Galaxy Nexus forum. Especially to Dragn4rce for creating this thread and kyokeun1234 for pointing out aboves easier solution.
Click to expand...
Click to collapse
Thank you tremedously, and your credits!
*Pressing Thanks* Cheers!
YES!
abnah said:
This is not a ROM problem! It could happen to anyone using ROM Manager!
How-to fix:
1. Download and install the latest ROM Manager APK from their website.
2. Delete the .nomedia file in /sdcard/android/data/ (ROM Manager 5.0.1.3 put a bad one there, the new version will be good).
3. Clear the data for Media Storage in Settings > Apps.
4. Reboot.
5. Wait. Re-indexing can need a while.
Credits go to the guys from the awesome Galaxy Nexus forum. Especially to Dragn4rce for creating this thread and kyokeun1234 for pointing out aboves easier solution.
Click to expand...
Click to collapse
Thanks a lot, this was really helpful for me!
Lt15i
lavenderdl said:
Lt15i
Click to expand...
Click to collapse
Was this a question? If yes: Yes, the solution is exactly the same across devices.
SystemUI keeps crashing when it tries to restart, making my phone completely unusable. I'm not able to flash another ROM at the moment so what I'd like to try is deleting the app data for SystemUI (wiping cache and dalvik didn't work). I have Team Win Recovery so I'm able to access the filesystem to delete files.
Can anyone suggest which file(s) I should look for?
restore a backup
beekay201 said:
restore a backup
Click to expand...
Click to collapse
I want to keep my most recent files. I took some photos today and they didn't get a chance to instant upload. I can wait a few days until I get to a computer I can use ADB on to push a ROM.
Sounds like you don't need a working device.
a maguro wrote this.
Use adb to remove /data/data/com.android.systemui/ folder
Hey guys! Big news!
I've fixed the problem, well.. sort of.
I will edit the post If I had something else to test.
1. Uninstalled Android System Webview and installed the one that is present in the Play Store (I can't select it for Webview Implementation though)
2. Launched YouTube app and showed a green screen no matter what the quality is.
3. Tried Chrome and the video works well without any freezes.
Hello to members here.
Would be really grateful for any help with info' regarding my Galaxy Grand Dous GT-19082 running on 4.1.2. I like the phone a lot, and don't like the fact I accidentally deleted the wall paper picker and also the program monitor from the system with root delete app. So I can not use live wall paper now, or the program monitor
As said before, phone rooted, think using/has CWM. Apart from that it's standard.I didn't back up my phone with Titanium back up etc unfortunately. I have tried to see which ROM I am using, but can't find out, even under settings/about device. It must be a stock ROM I guess, as I only rooted it, didn't change ROM.
I have spent/wasted a day and a half so far trying to find info' on the web looking how I can re install these to the phone. Potentially frustrating. I have looked for the apk files but could not locate.
I am fairly basic with my knowledge on this techie stuff, so if anyone can explain as simply as possible and step by step. I would be most thankful. If I could pay somebody to do it, then I would probably be keen, just want my phone as it was again...
Thanks again, and respect in advance for any helps/info' and advise.
Sincere regards, Alex
Recklessly deleting a few, seemingly unimportant system files could have as destructive consequence as having to reflash your whole firmware via Odin. That means you have to backup all your apps and datas. What firmware version are you on currently? Maybe some guys here can help extracting the files from the firmware package you mentioned, or else you might have to download the whole firmware (mind you, it's huge) and flash it via Odin.
Hey Naufalhadyan, Thanks for the reply. Yes, was reckless and kind'a stupid deleting the files.
My firmware is I believe 4.1.2 Jelly Bean
mr_b_alex said:
Hello to members here.
Would be really grateful for any help with info' regarding my Galaxy Grand Dous GT-19082 running on 4.1.2. I like the phone a lot, and don't like the fact I accidentally deleted the wall paper picker and also the program monitor from the system with root delete app. So I can not use live wall paper now, or the program monitor
As said before, phone rooted, think using/has CWM. Apart from that it's standard.I didn't back up my phone with Titanium back up etc unfortunately. I have tried to see which ROM I am using, but can't find out, even under settings/about device. It must be a stock ROM I guess, as I only rooted it, didn't change ROM.
I have spent/wasted a day and a half so far trying to find info' on the web looking how I can re install these to the phone. Potentially frustrating. I have looked for the apk files but could not locate.
I am fairly basic with my knowledge on this techie stuff, so if anyone can explain as simply as possible and step by step. I would be most thankful. If I could pay somebody to do it, then I would probably be keen, just want my phone as it was again...
Thanks again, and respect in advance for any helps/info' and advise.
Sincere regards, Alex
Click to expand...
Click to collapse
1. Boot into recovery, Volume UP + Home + Power
2. Select Install zip and choose this zip file - View attachment apps-update.zip
3. Let it install
4. Go back, select Wipe Cache
5. Go to advanced, select Wipe Dalvik-cache
Alternatively, extract the zip, mount your /system and copy the apks included and set their permissions to rw-r--r--
I couldn't find an exact apk that says Program Provider, so I'm included both possible ones.
Apks included:
- ApplicationsProvider
- SecLiveWallpapersPicker
- SecWallpaperChooser
- TaskProvider
All above apps are extracted from 4.1.2 XXAMF7 firmware directly.
The zip file will copy and replace the above system apps. Clearing cache and dalvik-cache will let your phone upgrade apps but no data will be lost, without it you might get Force Closes.
NOTE: Please make sure you back up your data before-hand, just in case
Hi Iceyhotguy,
Much thanks to you for the zip link and what seems like straight forward instructions.
I have spent a while trying to add the zip. When I go into recovery mode, it says it can not mound sd card. I have even payed for the premium version of CWM now, thinking I could add the zip this way, which I think I can, but again in recovery mode, it can not mount the sd card, which is where the file is download to. (I think)
Have downloaded the file straight to the phone aswell, but no luck yet.
I guess I have to install manually some how, you said ''Alternatively, extract the zip, mount your /system and copy the apks included and set their permissions to rw-r--r--'' . If you could be so kind to talk me through in baby steps (as I don't really understand this way) how I can do it this way, seeing the recovery mode way is not working for some reason.
Close,but not quite there yet.
Really hoping to fix my mistakes of accidentally deleting file soon, guess it's a good lesson, and I am learning more about this kind of thing, so not all bad.
Hope to hear back from you, and/or other members soon.
Thankyou,
Alex
Spent ages trying to fix my phone, and research online how I ''copy the apks included and set their permissions to rw-r--r--'' can't do it, getting frustrating..
Also I read online that using CWM as a recovery is not needed on a stock ROM and the error message in recovery 'can't not mount sd card'' can happen with stock rom and CWM....
Would really appreciate some help to fix this. Thanks:good:
Managed to try change permission with a root explorer program, though it says some files do not allow permission change, so seems I can not so this either
mr_b_alex said:
Spent ages trying to fix my phone, and research online how I ''copy the apks included and set their permissions to rw-r--r--'' can't do it, getting frustrating..
Also I read online that using CWM as a recovery is not needed on a stock ROM and the error message in recovery 'can't not mount sd card'' can happen with stock rom and CWM....
Would really appreciate some help to fix this. Thanks:good:
Click to expand...
Click to collapse
Reflash the CWM for 4.1.2 with Odin from here - http://forum.xda-developers.com/showpost.php?p=42349036&postcount=1
That'll fix the sdcard issue. If it doesn't try putting the zip file in internal memory.
I explained how to copy bootanimation file here in steps and paste it back in /system/media with setting permissions : http://forum.xda-developers.com/showpost.php?p=46010766&postcount=2
The same principle will apply when copying apks from the above zip file, take all 4 apks, and paste them in /system/app folder then follow my post above to set permission.
iceyhotguy said:
Reflash the CWM for 4.1.2 with Odin from here - http://forum.xda-developers.com/showpost.php?p=42349036&postcount=1
That'll fix the sdcard issue. If it doesn't try putting the zip file in internal memory.
I explained how to copy bootanimation file here in steps and paste it back in /system/media with setting permissions : http://forum.xda-developers.com/showpost.php?p=46010766&postcount=2
The same principle will apply when copying apks from the above zip file, take all 4 apks, and paste them in /system/app folder then follow my post above to set permission.
Click to expand...
Click to collapse
Thanks for the info' s. Have tried, done what was well explained, but still no luck..
Think I try to reflash the stock rom via odin, if you have any links /info' on this, that would be great, thanks
iceyhotguy said:
1. Boot into recovery, Volume UP + Home + Power
2. Select Install zip and choose this zip file - View attachment 2581684
3. Let it install
4. Go back, select Wipe Cache
5. Go to advanced, select Wipe Dalvik-cache
Alternatively, extract the zip, mount your /system and copy the apks included and set their permissions to rw-r--r--
I couldn't find an exact apk that says Program Provider, so I'm included both possible ones.
Apks included:
- ApplicationsProvider
- SecLiveWallpapersPicker
- SecWallpaperChooser
- TaskProvider
All above apps are extracted from 4.1.2 XXAMF7 firmware directly.
The zip file will copy and replace the above system apps. Clearing cache and dalvik-cache will let your phone upgrade apps but no data will be lost, without it you might get Force Closes.
NOTE: Please make sure you back up your data before-hand, just in case
Click to expand...
Click to collapse
Thanks a ton man, this worked for me and now I re-installed Live Wallpaper APK. Could not install via any root perm enabled file manager. Sumit pointed me here, thanks to him too.
Has anybody encountered the camera app not saving pictures? The camera app opens up and takes pictures fine but when you open the image from the gallery app, it's just a solid dark green color. I searched the OP3 threads but I have found nothing conclusive. Storage is also wonky since sometimes I can't access files I have placed in the internal storage (rom folder for flashing disappears but takes up space). I have encountered this problem in 6.0.1 to 7.1.1. I have tried adb format userdata and wiping storage and flashing the correct TWRP and firmware images. If any of you has encountered this problem and has solved it, please do comment and help me. Thanks!
vinax89 said:
Has anybody encountered the camera app not saving pictures? The camera app opens up and takes pictures fine but when you open the image from the gallery app, it's just a solid dark green color. I searched the OP3 threads but I have found nothing conclusive. Storage is also wonky since sometimes I can't access files I have placed in the internal storage (rom folder for flashing disappears but takes up space). I have encountered this problem in 6.0.1 to 7.1.1. I have tried adb format userdata and wiping storage and flashing the correct TWRP and firmware images. If any of you has encountered this problem and has solved it, please do comment and help me. Thanks!
Click to expand...
Click to collapse
seems to me like its a hardware fault here, its your nand storage which looks like its about to give up on you, better claim warranty while its still valid.
vinax89 said:
Has anybody encountered the camera app not saving pictures? The camera app opens up and takes pictures fine but when you open the image from the gallery app, it's just a solid dark green color. I searched the OP3 threads but I have found nothing conclusive. Storage is also wonky since sometimes I can't access files I have placed in the internal storage (rom folder for flashing disappears but takes up space). I have encountered this problem in 6.0.1 to 7.1.1. I have tried adb format userdata and wiping storage and flashing the correct TWRP and firmware images. If any of you has encountered this problem and has solved it, please do comment and help me. Thanks!
Click to expand...
Click to collapse
Did you make any edits to your buildprop?
Hw4ng3r said:
Did you make any edits to your buildprop?
Click to expand...
Click to collapse
Nope, buildprop is stock/unchanged. I have a guess that this is a storage permission problem.
vinax89 said:
Nope, buildprop is stock/unchanged. I have a guess that this is a storage permission problem.
Click to expand...
Click to collapse
i was having the same problem here. it hapened to me when i went to 7.0 on freedom os. it has nothing to do with the storage that guy was talking about.
i just reinstalled the os and wiped and it was gonne like that
It happened to me after disabling an app, unfortunately don't know exactly which one. I suggest factory reset.
I'm having the exact same issue.
I've re-flashed OOS 4.0.2 twice, re-formatting the system via stock recovery in between. tried with and without root, also removed data for the camera app.
Strangely it works just fine with an app like Open Camera (although the quality is miserable) - have you tried that?
edit: I also assume a permission issue but struggling to find out how that seems to work in Nougat...
Cheers
Stock build.prop
can anyone upload the stock build.prop file for oxygen os 4.0.2 one plus 3
shubhambankar96 said:
can anyone upload the stock build.prop file for oxygen os 4.0.2 one plus 3
Click to expand...
Click to collapse
Is this what you want? Delete ".txt" from the name of the attached file.
Try changing build.prop permissions to rw-r-r. That worked for me with a similar problem.
It only happens if u have edited Ur build prop or something did it. make sure the build prop is stock and dpi change is also issue (via build prop not from settings )