Database Users

[Q] Deactivate the Camera

Hi all,
Firstly, apologies if this has been covered before, I have had a search but not been able to find an answer yet.
Is there a way to temporarily disable the camera (photo + video) function of the Wildfire? The reason being that I am going to be temporarily working in an area where cameras are banned. I am trying to find an alternative to having the camera drilled at the security entrance.
Does anyone know if it is possible?
Cheers,

I dont think there is. Besides, its pointless if you look at it. You show the security the disabled camera, enter the premises, and activate it again. Ofcourse, this is if the security believes that the camera is disabled, which they wont.
However, I think you can root the phone, take a nandroid backup, and, enter /system and mess around with the camera files (camera.apk), due to which even if you start the camera app, it wont start. However, the question remains whether the security will accept this or not. (Because even they would know a software hack is undoable)
IMV, it would probably be better to get a cheap phone for work, if only phone calls and SMS'es are your need at work.

3xeno said:
I dont think there is. Besides, its pointless if you look at it. You show the security the disabled camera, enter the premises, and activate it again. Ofcourse, this is if the security believes that the camera is disabled, which they wont.
However, I think you can root the phone, take a nandroid backup, and, enter /system and mess around with the camera files (camera.apk), due to which even if you start the camera app, it wont start. However, the question remains whether the security will accept this or not. (Because even they would know a software hack is undoable)
IMV, it would probably be better to get a cheap phone for work, if only phone calls and SMS'es are your need at work.
Click to expand...
Click to collapse
Thanks for the advice.
Let me add, this isn't the only line of defence in satisfying the security people, but I would rather keep the discussion the the software part rather than the ins and outs of the policy and if it would satisfy. It is antiquated and largely pointless policy for the modern world. If someone wants to use a camera as a tool for espionage, there are much better & subtler things than using a smart-phone camera.
From reading round various internet forums, this question always seems to generate more discussion on the policy than the actual deactivation.

alongwor said:
It is antiquated and largely pointless policy for the modern world. If someone wants to use a camera as a tool for espionage, there are much better & subtler things than using a smart-phone camera.
From reading round various internet forums, this question always seems to generate more discussion on the policy than the actual deactivation.
Click to expand...
Click to collapse
True. Anyhow, not much you can do here, unfortunately. (Both in terms of policy and temp disabling the cam)
Sent from my HTC Wildfire using XDA App

Sort of gutting the phone (dont you will be responsible and will probibly brick the phone) you would be better off getting a cheap dumbphone
Sent from my GT-P1000 using XDA App

Enabling multi-user functionality?

So just got my hands on one of these. One thing I noticed/realized that would be a big deal for my intended usage is being able to enable multi-user functionality so each person that uses it can log in to their own profile.
So far on researching I have seen very little discussion on this matter. At best I see no option in the stock rom and no mentions in third party roms. If this is indeed available in third party roms I would not be averse to giving them a shot. I have also seen build.prop edits to enable that and they seem to be the same edit across devices so I'm assuming it is a standard android thing. I haven't had a chance yet to root my Player but is there a chance adding these build.prop options could also work on the stock rom?
Thoughts? Btw, I have already updated to Marshmallow however I did find a post around here that seems to indicate it is still relatively easy to root so once I get time today I am going to go down that route regardless.

I've seen a workaround that has you side-load gmail apk onto the nexus player, which in turn lets you add an account. Then, there are some apps that check for multiple accounts. Haven't tried yet, I think it might no longer work with YouTube like it used to.
Let's get this escalated to google - star this issue to get it some attention.
https://code.google.com/p/android/issues/detail?id=170121

I would really like some info on this! cr08 if you are going to mention builprop edits please at least consider linking the info you refer to haha thanks!

Feedback request on Nikon software issue (wireless mobile utility)

I know this is probably slightly beyond the scope of this forum, but I was hoping to get some feedback from some experts on what I am being spoon fed by Nikon support.
I have a Note 4 but I had this same issue with an HTC One M7, M8 and LG G3.
In a nutshell, my Nikon camera has a wireless adapter that allows you to transfer pictures from the camera to an Android or iOS device. You need to install the Nikon Wireless Mobile Utility software on the device in order to enable this. When I transfer a picture using any of the above Android phones and try to attach it to a text message, I get unsupported media type. The details on the picture shows that it has an image type of JEPG, not JPEG. Again, this on any of the Android phones that I've had. I attached a picture of an LG G3 screen showing the wrong image type and I sent this to Nikon.
Now, if you open the picture in an editor, crop it (or make some other change), and then save it, it's fine. The image type is now JPEG and can be attached to an MMS message.
I contacted Nikon support and they are telling me it's a Samsung issue. Before I go back to them, can someone give me their 2 cents on what they are feeding me because it makes zero sense? I refuse to give up on this. Thanks! - Kevin
========================================
Hi Mr. Moore,
Thank you for contacting Nikon. I did have this case reviewed by my supervisor, and this is a Samsung issue. You would need to contact them for further assistance on this matter.
Best Regards,
Christine C.
========================================
Dang it, it's not a Samsung issue. I've had the same problem when I had my HTC One M7 and M8. To prove it, I just loaded up the WMU software on my wife's LG G3 phone and it has the exact same problem. It is a Nikon software problem! Please tell them not to pass the buck. See attached picture that I took of the LG phone displaying the details of a picture that I transferred using the WMU. It still shows the file type to be JEPG! Thank you.
=======================================
Hi Mr. Moore,
The devices this issue is occurring on are Android phones which is ran by Samsung. Android devices have been documented to read Nikon files as JEPG instead of JPEG. When this issue occurs, we recommend customers to contact Samsumg and they may be able to provide assistance with correcting this issue.
Best Regards,
Christine C.

moorek said:
I know this is probably slightly beyond the scope of this forum, but I was hoping to get some feedback from some experts on what I am being spoon fed by Nikon support.
I have a Note 4 but I had this same issue with an HTC One M7, M8 and LG G3.
In a nutshell, my Nikon camera has a wireless adapter that allows you to transfer pictures from the camera to an Android or iOS device. You need to install the Nikon Wireless Mobile Utility software on the device in order to enable this. When I transfer a picture using any of the above Android phones and try to attach it to a text message, I get unsupported media type. The details on the picture shows that it has an image type of JEPG, not JPEG. Again, this on any of the Android phones that I've had. I attached a picture of an LG G3 screen showing the wrong image type and I sent this to Nikon.
Now, if you open the picture in an editor, crop it (or make some other change), and then save it, it's fine. The image type is now JPEG and can be attached to an MMS message.
I contacted Nikon support and they are telling me it's a Samsung issue. Before I go back to them, can someone give me their 2 cents on what they are feeding me because it makes zero sense? I refuse to give up on this. Thanks! - Kevin
========================================
Hi Mr. Moore,
Thank you for contacting Nikon. I did have this case reviewed by my supervisor, and this is a Samsung issue. You would need to contact them for further assistance on this matter.
Best Regards,
Christine C.
========================================
Dang it, it's not a Samsung issue. I've had the same problem when I had my HTC One M7 and M8. To prove it, I just loaded up the WMU software on my wife's LG G3 phone and it has the exact same problem. It is a Nikon software problem! Please tell them not to pass the buck. See attached picture that I took of the LG phone displaying the details of a picture that I transferred using the WMU. It still shows the file type to be JEPG! Thank you.
=======================================
Hi Mr. Moore,
The devices this issue is occurring on are Android phones which is ran by Samsung. Android devices have been documented to read Nikon files as JEPG instead of JPEG. When this issue occurs, we recommend customers to contact Samsumg and they may be able to provide assistance with correcting this issue.
Best Regards,
Christine C.
Click to expand...
Click to collapse
Well if you got a display and the ability to check the image on the camera then see what type it shows there before transferring and also when you do so next time do it both to a pc and a phone and see if its the same result.
It could just be a buggy protocol being used by Nikon but I don't think instead I would use the word that I know its a bug from Nikon's side since its the same outcome on all device manufactures which kinda confirms Nikon's android app or the protocol or the software in the camera is buggy.
Customer services are mostly dumb as a door and don't know anything apart from the details they have on a manual on there computer screens.
Have you looked for a firmware update to your camera as there tech team might have had others reporting this and thereby fixed it?

Thanks for the reply. If I transfer a picture from the camera to Windows (via sd card) and then copy the picture to my Android phone (using ES File Explorer), it works just fine. I can bring it into the SMS app with no problem. I checked for a firmware update on the camera (D3300) and there is none. I may load up the software onto one of my kid's iPhones and see if it does the same thing. If so, I'm sure support will tell me that Samsung make iPhones also.
I replied to the CSR and asked he to escalate it as she didn't know what she was talking about, in a polite way. For now, I'll keep on transferring, crop, save, and then send.

There is an app that fixes this issue, https://play.google.com/store/apps/details?id=au.id.thomnet.jpgjpg

Kospet Prime 2 on Android 10 - Root?

The new Kospet Prime 2 has a fairly impressive set of hardware and is one of the first smartwatches to run Android 10.
Since they don't seem to be open to discussing possible root solutions at a smart watch forum I'm on, I'm asking for any possible help and solutions here. It is an MTK based device with the Octacore Helio P22 MT6762, a Sony 13MP camera, 4GB / 64GB, enough cellular bands to work with most any service in nearly all locations, GPS, bluetooth, Wifi, Google Services and most of the usual amenities.
I understand Android 10 creates difficulties in gaining root but I've heard Magisk may give some amount of root privilege but so far I haven't been able to install it on this device. While I've got a lot of devices rooted this is the first one I own on Android 10. Any thoughts, info or help much appreciated.

Just to add some info I simply get 'Installation failed' when Magisk v8.0.2(307) tries to install beta 21.000.
Magisk log file:
- Device platform: arm64-v8a
!Process error
!Installation failed
Developer options are enabled, OEM bootloader unlocked in developer options, USB debuggin On.

Really? ?
After everything I explained....
Here you are...

pablo11 said:
Really? ?
After everything I explained....
Here you are...
Click to expand...
Click to collapse
Sorry pablo but if you see my message on the watch forum you will see I like the challenge of the Impossible. What is true today can change tomorrow as many here have shown that formerly un-rootable phones got rooted.
And as I mentioned there Apple and nearly everyone said you can’t bypass the iCloud lock. I worked on an iCloud locked iPhone for 5 years on and off spending hundreds of hours on it when everyone said it was impossible to bypass it (except for the phony youtubers just wanting clicks and web sites selling bogus claims to unlock for big $$). After 5 years I finally hit on a method to bypass the iCloud lock. Not one of those phony pay services either. Not the half baked DNS barely working method which created a virtual web based iPhone. My own method. iPhone is fully functional now. This was not a stolen phone. I bought it at the time from a guy who admitted it was iCloud locked and I confirmed it was purchased from a guy who forgot to unlock it and forgot his iCloud password. Unfortunatley at that time I believed all the BS on the Internet that it was easy to unlock. I tried every method from about everyone who claimed they had an unlock method. None worked. It was the challenge of the impossible that kept me working on it. A couple times I was very close to taking it out to a shooting range to put a bullet through it. :laugh: I guess I have an issue with anyone saying I can't do something. I'm not sure my method would
work on all iPhones or all versions but it worked on mine.

Root has been achieved! Thanks to user 'noidremained' and luisreche on the watch forum for letting me know about this. And big thanks and kudos to topjohnwu for achieving this difficult root on Android 10 with Magisk using the 'canary' channel. Still investigating what we can do with this root - may just allow you to snoop around as I believe the system partition cannot be modified further but will update with any news on that.

And thanks to pablo11 and user 'none' on the watch forum we now have TWRP for the Kospet Prime 2 and much thanks for his help and tips. Info here: Root & TWRP for the Kospet Prime 2

Sorry to hijack your thread but was hoping to get your advice. I have a Prime 2 that I've tried to put into developer mode (tap on the Build number and all that). It says it's now in developer mode but there's no developer settings menu item. Just wondering if you experienced the same or if they've updated the build to hide dev options? I'm on D09_KOSPET_PRIME2_V1.5_20201210. Many thanks.

chrisduke said:
Sorry to hijack your thread but was hoping to get your advice. I have a Prime 2 that I've tried to put into developer mode (tap on the Build number and all that). It says it's now in developer mode but there's no developer settings menu item. Just wondering if you experienced the same or if they've updated the build to hide dev options? I'm on D09_KOSPET_PRIME2_V1.5_20201210. Many thanks.
Click to expand...
Click to collapse
After some more digging I found the Developer menu in Settings > System

HELO TO EVERY BODY
I WANT TO CHANGE IMEI TO ACCESS NETWORK BECAUSE I LIVE IN IR.I
ANY BODY DO THIS?

droidzer1 said:
The new Kospet Prime 2 has a fairly impressive set of hardware and is one of the first smartwatches to run Android 10.
Since they don't seem to be open to discussing possible root solutions at a smart watch forum I'm on, I'm asking for any possible help and solutions here. It is an MTK based device with the Octacore Helio P22 MT6762, a Sony 13MP camera, 4GB / 64GB, enough cellular bands to work with most any service in nearly all locations, GPS, bluetooth, Wifi, Google Services and most of the usual amenities.
I understand Android 10 creates difficulties in gaining root but I've heard Magisk may give some amount of root privilege but so far I haven't been able to install it on this device. While I've got a lot of devices rooted this is the first one I own on Android 10. Any thoughts, info or help much appreciated.
Click to expand...
Click to collapse
Kospet watches are not CDMA so Verizon is incompatible. Sprint only offers data plans, no talk or text. Watch can not make bluetooth calls. It's a sha.e, it's a beautiful watch.

sunmartin said:
HELO TO EVERY BODY
I WANT TO CHANGE IMEI TO ACCESS NETWORK BECAUSE I LIVE IN IR.I
ANY BODY DO THIS?
Click to expand...
Click to collapse
Not info info. KOSPET will change IMEI but you have to know the frequency network. If you have verizon...its not compatible.

The problem still persists

Hello there... My question might require rooting? Below is a link to what's going on from my channel..

friends already managed to root for the latest version (July/2021)?

I am thinking of rooting my Oneplus 8 Pro but... call recorder? infrared camera?

I am thinking of rooting my Oneplus 8 Pro but I would like to know if there is currently a ROM that allows me to:
have automatic call recording (maybe even with google dialer or third-party programs)
have the possibility to exploit the "infrared camera" at 100%
have the latest version of android (11) and related security patches
it's possible?
Thanks.

You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...

emirefek said:
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
Click to expand...
Click to collapse
Thank you very much for the reply.
I have the latest version of android 11 released not even a month ago (updated to the latest security patches).
With this version do you think I can unlock registration via ADB with the command you gave me?
As for the infrared camera, using that ADB command would I be able to use it through the official oneplus "camera" app?
I also wouldn't want to root for any problems with banking apps and the like, so if I could fix that it would be better.
Thank you again.

emirefek said:
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
Click to expand...
Click to collapse
I tried with the two ADB controls for recording and the camera.
The first one enables me the recording menu in the options, but in fact, despite having enabled the automatic recording, it does not record anything, the option appears on the dialer screen.
I think it is blocked for my country (Italy), is there any way to unblock it?
I was able to record the call. Stupidly I hadn't set the oneplus dialer as the default one. Now I wonder if there is a way to record calls with google too?
As for the room, on the other hand, even when photochromic is selected, it simply tells me that I have to be outdoors and in more illuminated environments.
I managed to enable the camera too: D
My only doubt now is if it is possible to make call recording work with the google dialer or, with the google dialer + external programs (like CubeACR).

ChIP_83 said:
I tried with the two ADB controls for recording and the camera.
The first one enables me the recording menu in the options, but in fact, despite having enabled the automatic recording, it does not record anything, the option appears on the dialer screen.
I think it is blocked for my country (Italy), is there any way to unblock it?
I was able to record the call. Stupidly I hadn't set the oneplus dialer as the default one. Now I wonder if there is a way to record calls with google too?
As for the room, on the other hand, even when photochromic is selected, it simply tells me that I have to be outdoors and in more illuminated environments.
I managed to enable the camera too: D
My only doubt now is if it is possible to make call recording work with the google dialer or, with the google dialer + external programs (like CubeACR).
Click to expand...
Click to collapse
You need to do your research yourself about Recording in Google's dialer. I'm not using it actively. I hope you'll find a way. And quick tip. After opening IR camera with ADB try to lock camera app from recently apps menu. With that you can use after a while without re-running command. And don't forget to share HowYouDid after figuring out recording at Google's Dialer. Have a great day!

You can enable Call Recording with ADB you don't need root for that.
Click to expand...
Click to collapse
You can't use call recorder on Android 11 in certain countries - Poland for example. I will try to go back to Android 10 ( Oxygen ).

Only way to get infrared is to roll back to 10.5.9 I think it is, I'm in the UK so that was the last one to work for me.
In regards to the camera on 11 it's quite simple but not the same..
Just obtain factory mode via the above method or several others, then you have two options.
Either use *#808# then go to the camera test page and use the 4th camera, then take screen recordings or screen shots (that's what I use) as it's the quickest way Vs the command to open it each time
Or
Download the app from the play store for the photchrom camera and use that which gives an interface for the same thing but has more options, simply cycle the camera using the flip button (bottom right)
OnePlus 8 Pro Photochrom[ROOT] - Apps on Google Play
OnePlus 8 Pro Photochrom Camera for ROOTED devices & OxygenOS 10.5.11 or 11
play.google.com
Call recording I have this by default.
If you're in a region like Australia then it may be blocked, AFAIK most places allow it.

emirefek said:
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
Click to expand...
Click to collapse
VERY USEFUL.
Do you know where we could find more "tricks" like those??? They're great!

Donno if anyone chimed in bit I'm using mobile banking with zero issues rooted. If done right it all works proper. The main reasons for me to root are to force chat heads. (Exposed) change the dpi (much more real state ) gravity box(volume skip screen off with no issues ran through exposed) along with a few other things inside gv.
Button mapper for screen on volume skips (usually cannot get it to work right for screen off long press skipping but this with gravity box is a seamless long press setup) titanium backup to freeze a few things.
There's an app for root that allows you to basically shut all sensors and everything per app. Xprivacy or some thing other)
I can't not lol