Related
Dear internet community,
i would like to adress my problems concerning the installation of Xposed and GravityBox on my Fairphone. You must know that this is my very first smartphone and i dont really know how to use them yet. But i know that i would like to be able to change my Locksreen wallpaper, whích is the only intention for me to try to install Xposed in the first place.
So lets get to the nuts and bolts:
Firstly i tried to "unroot" my phone (of which i dont have any clue what that might mean), but the program i used (universal unroot) gave me this message upon trying: "please allow root access now. If you cant allow root access your device is most likely not rooted". At this point i dont know if i am able to allow root acess to that program, which ist rediculous in itself since this program should allow me to do that in the first place. I checked in the settings but couldnt find anything that looked like root access.
The next step was to install Xposed (version 2.6.1 and then 2.7 both with the same result). After the installation and the reboot, Xposed states unter the "Framework" category that: "the latest version of Xposed is currently not active (my app manager tells me it is). Did you install the framework and reboot?". Again i did the reboot and i installed it. If try to go further into the Framework menu and press the "install/update"-button it tells me: "failed to get root access. make sure your device is rooted properly and you have not blocked shell commands".
My question now is: do you have a solution for my problem? I would be very thankfull and appreciative if you would offer me a solution, since my intentional desire of changing the Lockscreen Wallpaper is such a small thing that it is quite hillaours as to how much effort has to be put in to change this small detail. Please dear community, help me out!
With kind regards
Alex
Hi Alex,
AdmirAlex said:
Firstly i tried to "unroot" my phone (of which i dont have any clue what that might mean), but the program i used (universal unroot) gave me this message upon trying: "please allow root access now. If you cant allow root access your device is most likely not rooted". At this point i dont know if i am able to allow root acess to that program, which ist rediculous in itself since this program should allow me to do that in the first place. I checked in the settings but couldnt find anything that looked like root access.
Click to expand...
Click to collapse
First of all: I see no point in "unrooting" my device. Since you said, you don't have any clue what that might mean, maybe this helps.
The term "root" is comparable to the "admin rights" on your computer. Some people do not need those rights. But If you don't need it just don't use it. If you "unroot" your device, what you do is, you throw away those admin rights. I don't see why you want to do this. The only reason which comes to my mind, is if you want your manufacture to repair your phone using your warranty. They basically don't like it if your phone is rooted, and say it violates the warranty conditions. But then again: fairphone comes pre-rooted, so having root does not void the warranty of your fairphone.
Usually if a program wants to have those root(/admin) rights, a screen pops up where you have to confirm that the app might use those rights.
If you want to know for what root rights can be good for, just google "rooting android" or something like that to read up on that topic.
AdmirAlex said:
The next step was to install Xposed (version 2.6.1 and then 2.7 both with the same result). After the installation and the reboot, Xposed states unter the "Framework" category that: "the latest version of Xposed is currently not active (my app manager tells me it is). Did you install the framework and reboot?". Again i did the reboot and i installed it. If try to go further into the Framework menu and press the "install/update"-button it tells me: "failed to get root access. make sure your device is rooted properly and you have not blocked shell commands".
Click to expand...
Click to collapse
Seems like you are actually unrooted. To use xposed and all its cool modules you need to have root rights. Unrooting your phone to use xposed is just contra productive. Maybe install SuperSU to re-gain root rights. But maybe you need to re-flash your OS.
AdmirAlex said:
My question now is: do you have a solution for my problem? I would be very thankfull and appreciative if you would offer me a solution, since my intentional desire of changing the Lockscreen Wallpaper is such a small thing that it is quite hillaours as to how much effort has to be put in to change this small detail. Please dear community, help me out!
Click to expand...
Click to collapse
Wait, what? Did I understand correctly, that you unrooted your phone to use an app that requires root so that you can change your lockscreen background?
Dude, you can do this in the settings without any root/unroot/xposed stuff.
As you said it is just a small detail, and such a standard feature, so it would be CRAZY if you need to go through such a hassle.
Just go into settings and somewhere in the display or lockscreen settings you can choose a background (you might need to disable the mood background for this). I do not have my fairphone anymore, so I cannot tell you where exactly that option is. Maybe someone else can point to the the exact location of that setting.
Hyst said:
...Maybe someone else can point to the the exact location of that setting.
Click to expand...
Click to collapse
I can't find any option for a different lockscreen image on my FP - only normal background image (wich is then also used for lockscreen, if I have mood background disabled). So I would also suggest GravityBox, which seems to be a too complex topic for your first smartphone ever...
dirtycutmaster said:
I can't find any option for a different lockscreen image on my FP - only normal background image (wich is then also used for lockscreen, if I have mood background disabled). So I would also suggest GravityBox, which seems to be a too complex topic for your first smartphone ever...
Click to expand...
Click to collapse
I know that this option is there. I had a custom lockscreen background (without using some xposed module like gravitybox). I will check with a friend who has a Fairphone, and tell you where the setting is.
I am sorry. Apparently I was mistaken. Changing the lockscreen background to a different wallpaper than the homescreen background seems not to be possible. You can just choose between mood background or not. I thought I had two different backgrounds while I had my Fairphone, but seems like I was wrong. sorry
Why is this not implemented? What I know for sure is that is a feature in CM and and Samsungs stock android version. I do not know about AOSP android.
Thanks for your feedback, Hyst!
I second your question about the missing implementation, but that's quite in a row with some other phone's stock features I am missing on the FP - e.g. a more solid gps, special character search in contacts and some other things other phones can do. Then I remember, Fairphone is still quite new on the market and neither has the experience nor the financial background to act like e.g. Samsung would do. And taken that into account, I'm sure they will grow with the requirements...
Hyst said:
Hi Alex,
First of all: I see no point in "unrooting" my device. Since you said, you don't have any clue what that might mean, maybe this helps.
The term "root" is comparable to the "admin rights" on your computer. Some people do not need those rights. But If you don't need it just don't use it. If you "unroot" your device, what you do is, you throw away those admin rights. I don't see why you want to do this. The only reason which comes to my mind, is if you want your manufacture to repair your phone using your warranty. They basically don't like it if your phone is rooted, and say it violates the warranty conditions. But then again: fairphone comes pre-rooted, so having root does not void the warranty of your fairphone.
Click to expand...
Click to collapse
Yeah i know now why the Phone needs to be rooted in order to work in a way i would like it to.
Seems like you are actually unrooted. To use xposed and all its cool modules you need to have root rights. Unrooting your phone to use xposed is just contra productive. Maybe install SuperSU to re-gain root rights. But maybe you need to re-flash your OS.
Click to expand...
Click to collapse
So atm the only viable solution that i could find is to reflash the Android of my phone. I tried to but the installation progress aborts itself so i am not able to reflash atm. The Fairphone support team got a mail from me, so lets wait and see.
Wait, what? Did I understand correctly, that you unrooted your phone to use an app that requires root so that you can change your lockscreen background?
Dude, you can do this in the settings without any root/unroot/xposed stuff.
As you said it is just a small detail, and such a standard feature, so it would be CRAZY if you need to go through such a hassle.
Click to expand...
Click to collapse
Now in a later post of yours you said that it is not possible. But i qould like to go into why i unrooted my phone. I was watching a Video from this site and misunderstood what has been said. I unrooted my phone, thinking that this would be necessary to make Xposed work. By that time i didnt really know how all of this works. I know its a rookie mistake and a "stupid" one, but i learned something and i am okay with it.
The next task now is to reflash my phone. Maybe you guys have an idea as to why it wont work: I followed the instructions on the Fairphone website and it still aborts during installation.
Edit: I am not allowed to linkt external websites, so i cant give you the video and fairphone installation guide links.
Greetings
Alex
Hope I didn't get it completely wrong but just wanna throw in another idea: why don't you reset your phone to factory settings? Reflashing it sounds like a lot of work for a beginner like you.. (Didn't do it either)
Since the phone is/was rooted from release on, resetting it should do the charme, imo. If you don't have a lot of files to lose I'd try that.
PS: really funny how complicated it got for you since your main intention was to change the lockscreen wallpaper )
PPS: follow this http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone from the 4th point on
arghwhymustiregister said:
Hope I didn't get it completely wrong but just wanna throw in another idea: why don't you reset your phone to factory settings? Reflashing it sounds like a lot of work for a beginner like you.. (Didn't do it either)
Since the phone is/was rooted from release on, resetting it should do the charme, imo. If you don't have a lot of files to lose I'd try that.
Click to expand...
Click to collapse
Yeah, i tred that a couple of times, but it wouldnt remove the unroot
PPS: follow this http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone from the 4th point on
Click to expand...
Click to collapse
Thanks for the link, i will try that in the meantime
PS: That, unfortunately, didnt do the trick
Edit2:
Since the Fairphone support hasn't replied yet, i tried another solution, but i need to ask you guys for help. I was following the instructions in the Fairphone wiki under the "How to restore Fairphone if you totally bricked it" topic. All the necessary files and programes are downloaded. Now when i choose the scatter file of the fairphone binarys the program gives me this message: "Error initialising scatter file failed. Please check the name of scatter file which you load is legal". if i press the download button the program gives me this message: "Download list is empty, please select a scatter file before executing"
I really dont get this. The fairphone binarys are supposed to work with this program, yet they are not. Can anyone help? Is there something really pbvious i have overlooked?
Greetz
Alex
Bump --> Please help me to figure out the SP Flash tool. To see the details check the post above
Thank you sooo much
AdmirAlex said:
Please help me to figure out the SP Flash tool.
Click to expand...
Click to collapse
I don't think you need to go through that mouch trouble as you're still able to use your phone (if I understood that correctly).
How about re-installing the Fairphone software from recovery? There's a nice guide on how to do that at:
fairphone.zendesk.com/hc/en-us/articles/202478028-Manually-install-Fairphone-OS-software-update-version-Cherry-1-6
Afterwards the superuser binaries should be back and you will have root access again.
haffenloher said:
I don't think you need to go through that mouch trouble as you're still able to use your phone (if I understood that correctly).
How about re-installing the Fairphone software from recovery? There's a nice guide on how to do that at:
fairphone.zendesk.com/hc/en-us/articles/202478028-Manually-install-Fairphone-OS-software-update-version-Cherry-1-6
Afterwards the superuser binaries should be back and you will have root access again.
Click to expand...
Click to collapse
Thanks for the hint, but that exact process does not work, since the update aborts itself giving an error message but not specifiying on which error exactly cause it to abort... I am frustrated at this point.
Greetings
Alex
AdmirAlex said:
Thanks for the hint, but that exact process does not work, since the update aborts itself giving an error message but not specifiying on which error exactly cause it to abort... I am frustrated at this point.
Click to expand...
Click to collapse
Which Fairphone model do you have? If it's the old one (from last year's batch), did you already use the repartitioning tool to "unify" your internal storage? Which update did you try to apply (exact filename)?
haffenloher said:
Which Fairphone model do you have? If it's the old one (from last year's batch), did you already use the repartitioning tool to "unify" your internal storage? Which update did you try to apply (exact filename)?
Click to expand...
Click to collapse
Its the second Batch phone, so the FP1U. I tried it with almost any OS given on the homepage. Those are the ones i tried:
OTA_AOSP-4.2.2_2014-08-05.zip
Fairphone_FP1_OS_v1_6_OTA_2014-07-31.zip
Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip
Fairphone_FP1_OS_1G13G_v1_6_OTA_2014-07-31.zip
The Fairphone updater tells me that my phone is running the "Chenpi" version 1.5 which i cannot find on the hompage (thats strange isnt't it?)
What else could be done here?
Greetings and thank you very much for your ideas so far!
Alex
AdmirAlex said:
Fairphone_FP1_OS_v1_6_OTA_2014-07-31.zip
Click to expand...
Click to collapse
Applying that one from recovery clearly should have worked. I've even used it myself with my (already repartitioned) first batch phone.
If you want to be sure the .zip file you downloaded is not corrupted, compute its MD5 checksum. If you're under Windows, use a tool like heise.de/download/md5summer.html
Under Linux, just use md5sum <filename>
The checksum should match the one found on Fairphone's software update page: 664ca09368a4c922a12dc2526afe092b
AdmirAlex said:
The Fairphone updater tells me that my phone is running the "Chenpi" version 1.5 which i cannot find on the hompage (thats strange isnt't it?)
Click to expand...
Click to collapse
1.5 is the version your phone was shipped with, I think. As they issued the update to 1.6 just a few days after the new phones started shipping, I guess they thought putting only the new image up on their website was enough.
haffenloher said:
Applying that one from recovery clearly should have worked. I've even used it myself with my (already repartitioned) first batch phone.
Click to expand...
Click to collapse
The awesome support Team worked something out and my phone is finally rerooted! Now, i have installed Xposed, rebooted it, installed Gravitybox, rebooted it and both programs are working fine. After some fiddling around it finally has worked!! For most of you it might seem to be a small thing and really not that important, but for me it is. Honestly the only two things i really use to personalize the phone is the Wallpaper / Lockscreen and the WakeupCall ringtone.
Thank you so much for all of your support and patience!
Greetings
Alex
Hey all, so I'm new to posting, and sorry if this isn't done correctly somehow.
So I just flashed blisspop 3.4 onto my LG G3 D850. Everything went smoothly for the most part, I had a few GAPP issues, but I worked it out. Once I got everything up and running, I clicked on a folder, and noticed a lock Icon. Curious to see what it did, I pushed it, and made a pattern lock, assuming that it locked the folder. I had no intentions of keeping it locked, I was just trying out the feature. Anyway, after entering in the pattern, the folder simply disappears. Along with the apps in it. Now this is a problem because my play store app is in that folder, along with a few others that I use pretty frequently. I've fooled with it for a few hours, and I have no idea what has happened, or why. The apps that were in the folder don't show up in the Apps section in the settings, or in the app drawer. The only ways I have found that allows me to access them are if I use a the pie wheel on he phone, or if I use a different profile. If I use the pie wheel to try to access the playstore, it says check connection and won't load. BUT, if I go into the other profile, it works fine (yes, the connection is the exact same). I really want to be able to resolve this, any help would be greatly appreciated
TboneThomas said:
Hey all, so I'm new to posting, and sorry if this isn't done correctly somehow.
So I just flashed blisspop 3.4 onto my LG G3 D850. Everything went smoothly for the most part, I had a few GAPP issues, but I worked it out. Once I got everything up and running, I clicked on a folder, and noticed a lock Icon. Curious to see what it did, I pushed it, and made a pattern lock, assuming that it locked the folder. I had no intentions of keeping it locked, I was just trying out the feature. Anyway, after entering in the pattern, the folder simply disappears. Along with the apps in it. Now this is a problem because my play store app is in that folder, along with a few others that I use pretty frequently. I've fooled with it for a few hours, and I have no idea what has happened, or why. The apps that were in the folder don't show up in the Apps section in the settings, or in the app drawer. The only ways I have found that allows me to access them are if I use a the pie wheel on he phone, or if I use a different profile. If I use the pie wheel to try to access the playstore, it says check connection and won't load. BUT, if I go into the other profile, it works fine (yes, the connection is the exact same). I really want to be able to resolve this, any help would be greatly appreciated
Click to expand...
Click to collapse
I would just reinstall the Gapps.zip in recovery.
The best place to get answers for this issue is likely the blisspop 3.4 thread.
[OFFICIAL][5.1.1_r3] BlissPop v3.4 [D855/0/2][ls990][vs985] 05/27
[FAQ][HELP THREAD] LG G3 | Ask any question | FAQ in first post [Noob Friendly] by DelBoy
[INDEX] LG G3 - ROMs, Kernels, MODs, Recoveries, Themes [30 May 2015] by benkxda
I will request that this thread be moved to G3 Q&A, Help & Troubleshooting
Installation Instructions:
https://wiki.cyanogenmod.org/w/Install_CM_for_ls970
Click to expand...
Click to collapse
Changelog:
20160814:
Updated using branch cm-12.120160127:
Updated to CM-12.1 using codebase cm-12.1-YOG7D
Updated libs from mako, which fixes GPS, Encryption, & some dirty log messages.
Click to expand...
Click to collapse
Special Thanks:
Looking at the commit log, I've got to say thank you to Shelnutt2 and Ricardo Cerqueira. Seth, for his work on porting this device & permission to post this build, and Richardo for maintaining the gproj kernel.
Click to expand...
Click to collapse
I've been using this with Ting. Seems more stable than the CM-11 build that I was using. Mms & cell data are the two things that do not work out of the gate for me. Wondering how this shapes up with Sprint. I vaguely remember cell data working, but I don't think the default mms app did. However, I was able to use a third party mms app for pictures.
If this works well for people I'll see what I can do about getting my changes pulled upstream.
XDA:DevDB Information
UNOFFICIAL CM12.1 for LS970, ROM for the Sprint LG Optimus G
Contributors
fuzzy7k, Shelnutt2, Ricardo Cerqueira
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-01-28
Last Updated 2016-08-17
What gapps version to use?
Thanks for providing this! I've installed it, to replace my cm-12-20151108-NIGHTLY-ls970.zip ROM. But I haven't been able to find a gapps download that will work with this (all Google services keep crashing) or fail to installed (Status 6). Any help will be appreciated.
Thanks!
gapps version
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate." Have you run into this issue? Any known fixes?
For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate."
Click to expand...
Click to collapse
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
geodosch said:
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
Click to expand...
Click to collapse
Yeah I just went through unrooting and going to stock (where it worked fine) and now tried again to install without luck. I don't understand this problem or what could possibly be the issue at this point.
Edit: I have noticed that I'm not seeing my 5 GHz network although it was available in stock.
Profile switcher
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
geodosch said:
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
Click to expand...
Click to collapse
Hey geodosch, same experience here with pop up errors with one difference, I was not able to get into Play Store... I only have four com.google.* green droid icons, and after clicking them I get 'App isn't installed'. Which gapps did you install, any other tips?
Many thanks!
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
A couple of issues
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
curiousGeorge said:
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
Click to expand...
Click to collapse
Did you click the "Downloads" tab near the top of this topic? (Between "Discussion" and "Reviews") There should be a link there to "cm-12.1-20160127-UNOFFICIAL-ls970.zip", dated 2016-01-28.
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
geodosch said:
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
Click to expand...
Click to collapse
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Ah, looks like I was right. It's the silly SELinux thing. The trick is to go here http://forum.xda-developers.com/showthread.php?t=2524485 and set the phone to permissive. Which you can totally do because you can go into the build info and click build number until you get "developer mode" enabled and enable root access in apps. Then everything works perfectly, even from a seemingly glitched install, regardless of GApps version. Pretty nice eh?
I'm gonna let everything update and then try reenabling SELinux, for kicks.
[edit]Ah, rebooting screws everything up again until the SELinux changer finally loads and changes things to permissive. So it doesn't exactly stick at boot. Still looking for a permanent fix...
curiousGeorge said:
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Click to expand...
Click to collapse
I'm running ClockworkMod 6.0.4.7. It's been a while since I originally installed the CM ROM, but I know I didn't have any luck with TWRP, though I can't say for certain that it was at fault... it may have been due to some other issue which I later fixed, and switching to CWM may have been incidental.
I've found that using the official CM recovery fixed my gapps woes.
On another note, GPS isn't working for me.
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
geodosch said:
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
Click to expand...
Click to collapse
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
geodosch said:
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Click to expand...
Click to collapse
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
geodosch said:
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
Click to expand...
Click to collapse
It's there, under "Power menu". Just search for power.
Nicene Nerd said:
On another note, GPS isn't working for me.
Click to expand...
Click to collapse
I read somewhere that you may need to get a lock in a ZVC build before flashing. Try that. It sounded like hog wash to me, and didn't work when I tried it. But, after updating the libs, all was fine. So, maybe both conditions must be met. On a positive note, I rarely have GPS enabled, but when I flip the switch, it comes on. So, it's not like you need to leave it on across reboots.
fuzzy7k said:
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
Click to expand...
Click to collapse
fuzzy7k said:
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
Click to expand...
Click to collapse
Glad to see you taking I look here. I really don't want to replace my Optimus G, since all phones now seem to be either low-end performance or over-sized. So I'm glad I can still keep mine going with these builds.
fuzzy7k said:
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
Click to expand...
Click to collapse
I hadn't tried adb before rebooting (Murphy's Law: whenever it happened I was often doing some time-constrained task, so I just rebooted as quickly as I could.) But the next time it happens I'll connect and check the logs. It's interesting that you mention multiple profiles, because it seems to have happened several times in my car, and I have profiles set-up to switch when the car bluetooth connects/disconnects.
If you're going to be poking around in the code, another issue that I've been having is the default app for the browser no longer seems to work consistently. I know this worked on an older CM12 build, and think it used to work on this one. But when something launches a browser I'm very often prompted for which one (Chrome or Browser.)
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
fuzzy7k said:
It's there, under "Power menu". Just search for power.
Click to expand...
Click to collapse
In the power menu, I see an option to switch users (which is disabled, since I don't have multiple users set-up), but I don't see an option for Profiles.
As we all know by now, the new update(INT.10.5.11/EU.10.5.10) changed how the photochrom work
now, it's working with the main sensor, and act like a filter, it's working only outdoor, with a minor effect
The new photochrom is like 10% of what it used to be.
I'm trying to re-enable the full Photochrom experience
For now, I've had tried these three ways to re-enable it, and NONE of if work
I tried to replace the OnePlusCamera.apk to the older version, doesn't work
I tried to replace these following files from vendor to the older version
Code:
Code:
/vendor/lib/camera/*
/vendor/lib/hw/camera.qcom.so
/vendor/lib64/camera/*
/vendor/lib64/hw/camera.qcom.so
but still, doesn't work.
And I can also confirm, the "fake device model" method doesn't work either.
(for IN2020 Chinese model, it fake the device model to other region, so it won't block the photochrom filter, work at EU.10.5.9/INT.10.5.10 for IN2020)
I can't seems to figure out what is changed between this & last update, that changed the photochrom behavior
If anyone can get it woking again, please let me know
BTW, the whole privacy concern is just nonsense, IT CAN'T SEE THROUGH CLOUTHES
Otherwise, you'll be naked every time you see a security cam, coz those things got IR too
OnePlus shouldn't disable/crippled a camera sensor on our phone, just for their own PR
UPDATE
The latest workaround is to use the FactoryMode app to "Test" the camera
First method is to unlock the FactoryMode
Follow this thread: [GUIDE] Unlock Factory Mode *root*
Then you can launch the camera test/camera preview in FactoryMode
Another way is to directly launch the CameraManualTest with adb command/local shell
Code:
For shell(require root):
su
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
For adb(require PC):
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
For wireless adb(require wireless adb debugging to be enabled):
[URL="https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md"]https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md[/URL]
These are still just workaround with FactoryMode, hope to see the original build-in camera method soon
Hoping for good solution for this problem, as it was cool feature I didn't have time to play with. Wouldnt have upgraded if I knew beforehand that this was the case.
Not only did the camera app update from 4.0.267 to 4.0.279, but the com.oneplus.camera.pictureprocessing updated from 4.0.79 to 4.0.81. I backed up both of these apps before updating using Apk Generator (play.google[dot]com/store/apps/details?id=com.aksapps.apkgenerator) but I'm not rooted so I can't replace system apps. You can try it and let me know though. Be sure to backup your apps in case it doesn't work.
drive.google[dot]com/folderview?id=18D_XwiiTJxfuhaV3TqJ5N4cDyYg_2gkE
There's a couple other camera related stuff I backed up but it doesn't look like changes were made to those. Links are censored with [dot] to get around the 10 post restriction.
I'm still on 10.5.9 EU.
Let me know if you need anything from mine..
I'm not rooted as yet so it can't be pulled without root I can't help as yet.
GiveMeAnthony said:
Not only did the camera app update from 4.0.267 to 4.0.279, but the com.oneplus.camera.pictureprocessing updated from 4.0.79 to 4.0.81. I backed up both of these apps before updating using Apk Generator (play.google[dot]com/store/apps/details?id=com.aksapps.apkgenerator) but I'm not rooted so I can't replace system apps. You can try it and let me know though. Be sure to backup your apps in case it doesn't work.
drive.google[dot]com/folderview?id=18D_XwiiTJxfuhaV3TqJ5N4cDyYg_2gkE
There's a couple other camera related stuff I backed up but it doesn't look like changes were made to those. Links are censored with [dot] to get around the 10 post restriction.
Click to expand...
Click to collapse
Tried this method, didn't work either
GiveMeAnthony said:
Not only did the camera app update from 4.0.267 to 4.0.279, but the com.oneplus.camera.pictureprocessing updated from 4.0.79 to 4.0.81. I backed up both of these apps before updating using Apk Generator (play.google[dot]com/store/apps/details?id=com.aksapps.apkgenerator) but I'm not rooted so I can't replace system apps. You can try it and let me know though. Be sure to backup your apps in case it doesn't work.
drive.google[dot]com/folderview?id=18D_XwiiTJxfuhaV3TqJ5N4cDyYg_2gkE
There's a couple other camera related stuff I backed up but it doesn't look like changes were made to those. Links are censored with [dot] to get around the 10 post restriction.
Click to expand...
Click to collapse
Still, won't work
Why are they making this so hard to do?
I tried to replace anything seems remotely relate to camera in /vendor/lib and /vendor/lib64
nothing work, I think the change might not in /vendor?
By doing the file compare, i see these OnePlus service has been updated through this update, is it possible they restrict the camera with those service?
Code:
/system/priv-app/oneplus-framework-res
/system/priv-app/OPCoreService
I tried to replace them with older file, but system will be shutdown after boot
Anyone got any more ideas?
Cattell said:
I tried to replace anything seems remotely relate to camera in /vendor/lib and /vendor/lib64
nothing work, I think the change might not in /vendor?
By doing the file compare, i see these OnePlus service has been updated through this update, is it possible they restrict the camera with those service?
Code:
/system/priv-app/oneplus-framework-res
/system/priv-app/OPCoreService
I tried to replace them with older file, but system will be shutdown after boot
Anyone got any more ideas?
Click to expand...
Click to collapse
How about trying to connect only Photochrom camera with an test/debug app?
ster88 said:
How about trying to connect only Photochrom camera with an test/debug app?
Click to expand...
Click to collapse
You gave me an idea. Tested with factory mode and camera tab then forth camera preview. Interesting, can still see the preview with it seeing through thin plastics even indoors. So, whatever they did with this update can probably be circumvented, just not sure how hard it would be. If you want to check it out, enable factory mode app then go to camera tab and do forth camera preview. Included screenshots of where to go and it still working.
jeffsga88 said:
You gave me an idea. Tested with factory mode and camera tab then forth camera preview. Interesting, can still see the preview with it seeing through thin plastics even indoors. So, whatever they did with this update can probably be circumvented, just not sure how hard it would be. If you want to check it out, enable factory mode app then go to camera tab and do forth camera preview. Included screenshots of where to go and it still working.
Click to expand...
Click to collapse
Wow it worked
Oneplus 8 Pro IN2023 10.5.10IN11BA
https://drive.google.com/file/d/1D5YRdOBKInFYQ2ns9r-eoefprCiUASj7/view
https://drive.google.com/file/d/1D9v40zFyMbiKLPFPLw36XzNUHCpK7gwE/view
https://drive.google.com/file/d/1D4JEyb-kJTCfzxiN0lYPhvvDcr2zX8Qr/view
https://drive.google.com/file/d/1D1FDJIRc_CmmIfh5P8IU3afeVkQfbCVS/view
Edit :
If you go to camera test in factory mode app, then you can take a picture with photochrom mode.
https://drive.google.com/file/d/1DNLkrOU8w-LI8TH4oZ8h6xOkeCd_Md1Q/view?usp=sharing
https://drive.google.com/file/d/1DKUJj2Xy4bKrJSot7CHtP3UYpV4LqIMg/view?usp=sharing
ster88 said:
Wow it worked
Oneplus 8 Pro IN2023 10.5.10IN11BA
https://drive.google.com/file/d/1D5YRdOBKInFYQ2ns9r-eoefprCiUASj7/view
https://drive.google.com/file/d/1D9v40zFyMbiKLPFPLw36XzNUHCpK7gwE/view
https://drive.google.com/file/d/1D4JEyb-kJTCfzxiN0lYPhvvDcr2zX8Qr/view
https://drive.google.com/file/d/1D1FDJIRc_CmmIfh5P8IU3afeVkQfbCVS/view
Edit :
If you go to camera test in factory mode app, then you can take a picture with photochrom mode.
https://drive.google.com/file/d/1DNLkrOU8w-LI8TH4oZ8h6xOkeCd_Md1Q/view?usp=sharing
https://drive.google.com/file/d/1DKUJj2Xy4bKrJSot7CHtP3UYpV4LqIMg/view?usp=sharing
Click to expand...
Click to collapse
Nice find. I knew someone would take a better look at all the options in that menu. At least there is a way to still use the photochrome mode now.
how to open the factory mode plz i dial *#808# and nothing happens it just clears everything on my dialer how to open factory mode on in2020 plus i m using one plus dialer
babsvsphudi said:
how to open the factory mode plz i dial *#808# and nothing happens it just clears everything on my dialer how to open factory mode on in2020 plus i m using one plus dialer
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlock-factory-mode-root-t4118527
How to enable factory mode, *#808# doesn't work I am not rooted.
Good work guys
Considering how difficult they tried to make it, I believe the best long term solution would be to have a specific app used just for this feature (mimicking this factory mode)
Else they would mess it up with more updates
i just rolled back my software version, so i have the function again
I'm on 10.5.11. but factory mode camera did not pick x-ray vision as mentioned. I tried several remotes and stuff. Any reason for that?
snovharry said:
I'm on 10.5.11. but factory mode camera did not pick x-ray vision as mentioned. I tried several remotes and stuff. Any reason for that?
Click to expand...
Click to collapse
It's not x ray vision. It's an IR camera and can only see through very thin plastics without IR shielding. It works on Amazon remotes and Vizio remotes that I've tried.
I found a way to launch the color filter camera without being root and without using MMI dial codes to access factory mode.
It is a bit impractical right now because I couldn't make it work on a terminal emulator app yet, but it works through the adb shell just fine.
Just run this from the adb shell:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It will launch the manual camera test from the FactoryMode app right away.
Press the bottom right icon to switch the camera until you get to the IR camera.
I'm running on the 10.5.10.IN11BA build.
Shure. Naming it "x-ray" is only a metaphor for the effect.
Hi all..
I have been using LinageOS for quite a while now, I love it and applaud those that have worked so hard to make such a wonderful OS.
But the main reason for using it is so I can avoid google. I have just installed Linage-18.1-20211113-nightly-beryllium-signed (I did not use the GAPPS package) and when I checked the installed apps/system, there is 2 google assistant apps.
I also rooted my mobile before installing Linage using magisk-v23-0 and disable-force-encryption=-treble, this was done through TWRP 3.3.0.0 beryllium. I mention these in case there is a possibility of these google apps coming from there, but have searched on the net and can find no evidence of this..
Anyone know anything about this? If Linage is now including google apps I am going to have to find another OS, and I really do not want to..!
Cant seem to get these google assistant apps off my phone (POCO f1). Tried every wipe I could do in TWRP, tried a port of CalyxOS, nothing will shift them.. Even when I 'force halt' they just switch themselves on again in a few minutes..
Going to try going back through the LinageOS versions and see if there is one that doesnt have them.
Nobody have an idea of how to get rid of these?
It's definitely weird, very weird (and hard to believe, if I may say so).
Using LOS ever since and never ever had such thing happening. Sometimes even putting gapps on it to try something with GSF...
Did you do a proper re-install from the scratch, just like by the book?
https://wiki.lineageos.org/devices/beryllium/install
Other than that, perhaps try asking in
https://forum.xda-developers.com/t/rom-official-lineageos-18-1-weeklies-for-xiaomi-poco-f1.4188235/
Hi SigmundDroid (cool handle)
Have now tried E Foundation too, every wipe I could do in TRWP, nothing will shift them, they activate a few minutes after I 'force stop' them..
Am now trying to find a way of doing a full format of the partitions as these files are like viruses..
E Foundation forum folk are also a bit startled by this, think they would like to know how to remove the files as part of the install procedure, me too..!!
Just found this;
https://pastebin.com/bf9Hh4RH
3rd and 4th line down.
When I look at the google assistant apps, the first one shows at the bottom of the screen under ‘advanced’;
Version 11
com.android.hotwordenrollment.okgoogle
The second one shows;
Version 11
com.android.hotwordenrollment.xgoogle
Not 100% sure how to use those lines, but they look to be adb commands… Any idea anyone?
Similar thread from 2017: https://forum.xda-developers.com/t/google-assistant-on-lineage-os.3566187/
Of possible relevance is that it's what does the transfer of accounts and settings from your old phone in newer Android versions. I don't plan on using Google Assistant generally, but it was very handy that the Lineage setup hooked into it for transferring accounts and stuff from my "old" phone.
Ah, the plot thickens..
I do get that some folk are ok with google, but not me.. Would still very much like to get rid of them. Also, those that are making google-free roms would no doubt want them gone too, can hardly be google-free with those hiding deep in the moby..
Did you clear the system partition? Some ROM install packages run an addon.d script to retain Gapps and other stuff. Of course LineageOS does not contain any Google stuff, only AOSP. So there is just another logical explanation for this. If you want to be sure, look in the LineageOS image yourself.
Apologies.. Looks like I had not made it clear, I do not now think Linage, or Calyx or E-foundation have google assistant in them.. They seem to be remnants on the phone, probably from the original rom.
But they will not easily be removed and so remain regardless of which custom rom subsequently ends up on the phone.
Am hoping someone way smarter than me can work out how to get rid of them, also hoping it will help others achieve the same..
fastesteddy13 said:
Just found this;
https://pastebin.com/bf9Hh4RH
Click to expand...
Click to collapse
Hmm, there is not much of an explanation what it does - looks like uninstalling a lot of bloatware.
Quigley said:
logical explanation for this
Click to expand...
Click to collapse
I concur with @Quigley and we shall find it.
fastesteddy13 said:
Tried every wipe I could do in TWRP
Click to expand...
Click to collapse
Which ones? (you can do screenshots in TWRP with power + vol down)
I guess we can assume you did the mandatory
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process
Click to expand...
Click to collapse
Plus what @Quigley said:
Quigley said:
Did you clear the system partition?
Click to expand...
Click to collapse
Did you?
https://www.addictivetips.com/mobil...plained-boot-system-recovery-data-cache-misc/
PS:
fastesteddy13 said:
SigmundDroid (cool handle)
Click to expand...
Click to collapse
Zank you! I zink your teflon is in love wiz your moza
fastesteddy13 said:
Apologies.. Looks like I had not made it clear, I do not now think Linage, or Calyx or E-foundation have google assistant in them.. They seem to be remnants on the phone, probably from the original rom.
But they will not easily be removed and so remain regardless of which custom rom subsequently ends up on the phone.
Am hoping someone way smarter than me can work out how to get rid of them, also hoping it will help others achieve the same..
Click to expand...
Click to collapse
One other thing: it can also be the product partition. Gapps are normally included in the product image in the original firmware. Did you wipe that one as well?
Its still in LOS 19.1 , despite years of complaints. Starting to look like they keep it in there on purpose, no option to uninstall, disable is greyed out..... SKETCH!
Same for Lineage 20 on my OnePlus 7T Pro. "google free" system ...
Is there an explanation somewhere why the apps are permanently and indelibly integrated? Why is there almost nothing about this on the net?
The .apks are 100% in the lineage images. You can verifiy this by yourself, if you want.
They are located in the product.img under priv-app.
EDIT:
deGoogle LineageOS 20.0 (tested on Oneplus 8T 'kebab' kb2003) - Luc
How to get rid of G-Services from your Android phone running LineageOS completly.
lucdev.net
Well ...
I used now App Manager (F_droid) and uninstall it.