Related
Hello, I have always been a spectator on XDA Forums. Today I have something to share with you guys.
FOLLOW THESE STEPS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG WITH YOUR PHONE.
I have found a solution to make them work for Android. Your android device must be rooted. Once you are rooted follow these steps :
1. Update your Snapchat to the latest version and open it once before moving forward.
2. Download CheatDroid from PlayStore. (It might also ask you to download BusyBox)
3. Disable WIFI/Data. (You must not be connected to the internet).
4. Open CheatDroid and browse to Snapchat.
5. Open the 3rd File named "...snapchat.android_preferences.xml"
6. Scroll down and search for "...vice_whitelisted_for_lenses_on_backend"
7. Change its Boolean from "false" to "true"
8. Exit CheatDroid & open Snapchat (Without the internet connection)
9. Start the selfie camera on Snapchat. Press & hold your face on the screen. At this point you are allowed to use the selfie lenses.
10. Once you have clicked a snap / video, you can enable your WIFI/Data and share it with your friends.
PS : However, I have noticed when you restart the App, the Boolean value switches back to "false" and you will have to redo the procedure. I will find a fix for this soon, let me know if the above procedure works for you. It works on my Samsung Galaxy S3. Also, the recording feature does not work for Android version less than 5.0.
Feel free to add in your suggestions/comments.
Thanks :> But its nice t find solution for restoring this setting
Working on it
I was just doing the same trick. I believe we need to change the device ID which is one line above to a device that is whitelisted and allows lenses.
any progress with this?
Hey! I'm currently trying to find an app that enables me to take screenshots without using the physical buttons on my phone, and I've run into a somewhat strange issue: third-party screenshot apps create images showing nonsense or things that happened in recovery mode.
Sorry for the wall of text below.
Phone details
I'm using a Nexus 5 running stock ROM Android 4.4.4. For recovery I'm using TWRP and for kernel I'm using Linaro by LaboDJ. The phone is rooted and also has Xposed Framework installed. Screenshots on this device are, as you probably know, normally taken by holding down the Volume Down and Start buttons simultaneously, but issues with the Start Button is making me seek an on-screen-based approach instead.
Issue
So far I've tried several different apps which can take screenshots by pressing overlay icons, shaking the phone, and so on. None of the screenshots come out as wanted, however. Depending on the app, screenshot files may fail to be generated, be pitch black, or feature something entirely different than the actual screen. The last type is made using root-requiring apps that scan for different methods to make screenshots (Screenshot Easy, Screenshot Ultimate).
The screenshots created by root-using apps (all images provided below are from Screenshot Easy) initially looked like this or this (depending on selected method, image). For testing I used /system/app mover to turn Screenshot Easy into a system app. This changed what it was able to make into this and this, revealing that the app provides screenshots of things I did in recovery mode. The coloration makes it even stranger (this is what the color scheme of TWRP looks like). In addition, the app retained the ability to make such screenshots even after being turned back into a non-system app or being reinstalled. There has been some days since I made these images, and right now the app can only create this. I'm having a hard time determining what affects output.
I would expect this app to work on a Nexus 5 for different reasons. Firstly, the majority of Google Play reviews for Screenshot Easy on this phone model are positive. Secondly, my phone is able to make screen recordings (SCR Screen Recorder) and take button-screenshots systemwide (DisableFlagSecure). I should also add that while I want to avoid using the physical buttons, they do create regular screenshots if I use them.
What I've tried so far
Fixes I've tried include changing Screenshot Easy settings, reinstalling the app, restoring the stock kernel, disabling various Xposed modules that may or may not be involved, starting the phone in Safe Mode to disable potentially interfering apps (Screenshot Easy was still usable due to being converted to a system app), deleting the TWRP backup on the phone, using an older version of Screenshot Easy from an APK-hosting website, wiping app cache, and wiping dalvik cache. I also tried changing resolution or DPI values (using SecondScreen or changing build.prop values), but this either turns the screenshots black (resolution change) or has no effect (DPI change).
Frankly I cannot make heads or tails out of this issue. If anyone could make any suggestions of what to try next or perhaps diagnose what is going on I would be very grateful!
TL;DR: third-party apps used for taking screenshots behave stangely and don't work no matter what I try. What to do?
Update
Update: it's been about 6 months since my above post, and for shiz and giggles I decided to yet again try downloading a screenshot app to see if I still get strange results. Went for Screenshot Easy (non-pro version) and granted it root permission, and to my surprise it works as it should, creating proper screenshot files.
It is difficult for me to tell if the reason Screenshot Easy now works is caused by some change in my phone, or in the app. However, while Screenshot Easy has received at least three updates since my previous attempt (I reckon the previous version I tried was 1.6.2, and now I'm using 2.9.6), Screenshot Ultimate has not received any updates and still gives me black (or gray), nonsense, or no images.
Edit: Testing suggests the reason is app change; the APKpure copy of v1.6.2 does not work (same issues described above) while v2.1.6, v2.8.2, and the already tested v2.9.6 does. What exactly has changed within the app is still hard to say. A difference is that v.1.6.2 with root permission but without being a system app has two faulty "Method 7" and "Method 8" methods for taking screenshots (image - this somehow differs from my previous experience) while the three working versions have a functional "Root 10" method (image).
According to the app update history (logged by App Annie (direct link, requires login)), the update info for v1.6.2 was simply:
Screen Record (Android 5.0+: Video & Audio)
Improved layout
Improved screenshots
Fixed bugs
Hey guys!
First, my apologies if I am in the wrong section posting. I was not sure where to post. Please move my thread if needed. Thanks!
Second, would someone recommend and/or suggest Android 9 over Android 10 or Android 10 over Android 9? For myself, I really do not like Android 10. When I am referring to Android 10 and I am referring to the original in September and the two updates in September where that last update has a C3 in part of the name, as well as the October Android 10 update. I just do not like any of the updates. Would I be better off going back to Android 9? It is not an issue because I can flash the factory images via ADB when the phone is powered on than Fastboot once the phone is in the flashing mode
Can you explain why you do not like the update?
I personally don't find that there is a lot of difference between 9 and 10, but offcourse 10 has the latest security updates, which might be a reason for you to stay with 10.
Personally I think the biggest noticeable difference between 9 and 10 is the gesture based navigation. However you can turn the Android 9 style navigation back on if you so desire (Settings/System/Gestures/2-button navigation) or even the older 3 button navigation.
Other changes - like dark mode - are also optional. I see little reason to stay on Android 9. Especially since it is not being updated with security updates.
It would be nice if we could continue to use a preferred version but that comes with considerable security risks. If your dislike is purely asthetics, you can try other launchers.
For the sake of security I'll stick with Q10 for now. I have yet to succeed with a direct OTA update even under full stock. If the pending November OTA updates without needing to sideload, I might then install Magisk.
Cool I w up - Micr
alliance1975 said:
For the sake of security I'll stick with Q10 for now. I have yet to succeed with a direct OTA update even under full stock. If the pending November OTA updates without needing to sideload, I might then install Magisk.
Click to expand...
Click to collapse
The majority of pushback comes from people USED to Android 9/Pie. I get it; I really do - when folks get comfortable, change scares the bejeebers outta them. Because I never ran Pie before the Pixel 3a came along (and Android 10 was halfway through its beta when the 3a arrived) I was able to go from 8/Oreo to 10 pretty much directly with only one migration issue; the gesture support. Simply not using them (even with Gboard) was an option, however - and one I adopted.
Launchers - Pixel Launcher was one I was already familiar with (from my Android 6 and 7 days); returning to it was therefore rather a relief.
The even bigger surprise is that I'm not rooted - or using a non-stock recovery; the first time I've done that on a smartphone (or any Android device since Android 5). TWRP was a certain install on a smartphone (as certain as doing tax returns every year); now - I could, in fact, care less. I follow TWRP development (and Magisk development as well); however, it's more a case of looking for a reason to install either - so far, nothing in Android 10 has given me a reason to move away from dead-stock. (Basically, it's a NEW sort of comfort - dead stock - for the first time in my Android phone history - IS actually good enough to run un-stepped-on.)
Dark mode requires neither; it's an option in Settings. Same with VoLTE/VoWiFi. Basically, so much for Magisk.
The thing is, you have to be comfortable with dead-stock; being as this is, after all, a developer/tweaker-targeting community, how many folks are actually comfortable running dead-stock?
If you CAN get comfortable running dead-stock, Android 10 on your 3a or 3a XL (or any Pixel, for that matter) makes a ton of sense.
Follow up - Due to Microsoft Launcher changing it's code base, I installed the beta on my Pixel 3a, replacing Pixel Launched as default. Due to new features, Pixel Launcher is in trouble! It is not the support for Dark Mode, third party launchers either have or are adding it. It is being able to use apps as plug ins; two I use now are Word (expected) and Google Calendar (unexpected). How many third party launchers let you use a system app - even Calendar - as a plug in directly. While Outlook for Android does, it is still nice to have Launcher do so as well. This very post is another example - I have added the XDA app as a plug in. Depending on how often you use an app, using it as a plug in May be faster than as a shortcut.
Im a new pixel user, i come from Nokia 7 plus (Android 9 - android one program, almost the same as pixel) and simply cant go back to 9...
Im glad my nokia also updated to 10 today , i really like the gestures. And i have been on 9 for 1 1/2 year now...
Nova launcher, gestures work fine on android 10, dark mode is not everywhere but its coming....
PGHammer said:
The majority of pushback comes from people USED to Android 9/Pie. I get it; I really do - when folks get comfortable, change scares the bejeebers outta them. Because I never ran Pie before the Pixel 3a came along (and Android 10 was halfway through its beta when the 3a arrived) I was able to go from 8/Oreo to 10 pretty much directly with only one migration issue; the gesture support. Simply not using them (even with Gboard) was an option, however - and one I adopted.
Launchers - Pixel Launcher was one I was already familiar with (from my Android 6 and 7 days); returning to it was therefore rather a relief.
The even bigger surprise is that I'm not rooted - or using a non-stock recovery; the first time I've done that on a smartphone (or any Android device since Android 5). TWRP was a certain install on a smartphone (as certain as doing tax returns every year); now - I could, in fact, care less. I follow TWRP development (and Magisk development as well); however, it's more a case of looking for a reason to install either - so far, nothing in Android 10 has given me a reason to move away from dead-stock. (Basically, it's a NEW sort of comfort - dead stock - for the first time in my Android phone history - IS actually good enough to run un-stepped-on.)
Dark mode requires neither; it's an option in Settings. Same with VoLTE/VoWiFi. Basically, so much for Magisk.
The thing is, you have to be comfortable with dead-stock; being as this is, after all, a developer/tweaker-targeting community, how many folks are actually comfortable running dead-stock?
If you CAN get comfortable running dead-stock, Android 10 on your 3a or 3a XL (or any Pixel, for that matter) makes a ton of sense.
Click to expand...
Click to collapse
I don't know that I had to, but I sideloaded the December update. However, the January update downloaded and installed w/o problem. I have had time to get used to full Q10 stock and it does many nice things. I don't think I'll do root until major changes happen.
NOTICE: I am not responsible for any damage to your device.
So, as a game developer, I often record any gaming sessions for later use (reviews,research,etc), and so losing the ability to capture internal audio was quite an inconvenience. Well, I came across an article about Android Q reintroducing the ability to do so, and I was thrilled, however my daily driver is the only phone I have running Q and I tend to keep my gaming/modding/dev related activities for older phones that would typically collect dust. After a bit of research, tinkering, and frustration, I finally found a way to gain this ability on my S7 running Nougat. However, being rooted, I'm uncertain whether that is the only reason I am able to capture internal audio, as installation didn't take anything root-related, as far as I can tell.
So, with that said, here are the steps I took to accomplish this task, all I ask is any feedback on results, if you were stock/rooted, Nougat/Oreo/Pie/Etc, and if it did or did not work.
Step 1: Install the Samsung_Record_Screen.apk
Step 2: Nougat/Oreo Users install Oreo_QS_Toggle.apk
Pie Users install Pie_QS_Toggle.apk
Step 3: Reboot
Check notification Quick Tiles to see if 'Record Screen' QT was added, remember to swipe left to check second 'page'. If not shown, continue to Step 4.
Step 4: Pull down notifications and tap the 3-dot button next to the cog and choose Button Order. Move the Record Screen QT button from the bottom to wherever you would like it, and be sure to press done in order for it to save.
Step 5: Test and Enjoy
Apps are stock, pulled from the Galaxy/Play Store and untouched, but feel free to decompile and/or scan them yourself. I'm hoping this works for everyone, root and unrooted, regardless of Android version, but that may be a bit too optimistic. Good luck and please remember to report your results, I will happily help where possible.
https://forum.xda-developers.com/galaxy-s8/themes/samsung-screen-recorder-one-ui-t4006455
Zendesk2 said:
https://forum.xda-developers.com/galaxy-s8/themes/samsung-screen-recorder-one-ui-t4006455
Click to expand...
Click to collapse
Ah, didn't see that as it's for Exynos, anyhow, these are the updated versions, Samsung_Record_Screen.apk was recompiled specifically for OneUI 2.1.
Regardless, as long as it works for everyone, I'm happy.
Hi fellas,
I recently bought a Xiaomi Redmi Note 9S, and aside from the fact that it's still running Android 10 over MIUI 12.0.3.0 (Global / EU since I'm in France) when everybody else and their cousin seems to have switched to Android 11 already, everything's peachy with the phone.
My question is borne more out of curiosity than necessity: How better would my photos be if I installed Gcam (Google Camera), rather than keep on using OpenCamera or the Xiaomi app the phone ships with? Would I really see an improvement in the way the Gcam software treats images?
If you think I'd get to gain from the install, then a second question comes to mind: How to install the config file that comes with most of the builds I've found here and there? Last time I installed Gcam on the phone, the config file came separately, and however hard I tried to follow instructions, I never managed to load the config file, so I ditched the app altogether. Patient, I am not for that kind of thing, I'll confess.
So, what gives?
UglyStuff said:
Hi fellas,
I recently bought a Xiaomi Redmi Note 9S, and aside from the fact that it's still running Android 10 over MIUI 12.0.3.0 (Global / EU since I'm in France) when everybody else and their cousin seems to have switched to Android 11 already, everything's peachy with the phone.
My question is borne more out of curiosity than necessity: How better would my photos be if I installed Gcam (Google Camera), rather than keep on using OpenCamera or the Xiaomi app the phone ships with? Would I really see an improvement in the way the Gcam software treats images?
If you think I'd get to gain from the install, then a second question comes to mind: How to install the config file that comes with most of the builds I've found here and there? Last time I installed Gcam on the phone, the config file came separately, and however hard I tried to follow instructions, I never managed to load the config file, so I ditched the app altogether. Patient, I am not for that kind of thing, I'll confess.
So, what gives?
Click to expand...
Click to collapse
gcam use some algorithm to enhance photos to high dynamic range (HDR). you may get better image if you use proper gcam made for your phone.
secondly, config file can be loaded in settings of most gcam. you can use youtube or any tutorial to see how to load configs.
Thanks for your reply, Bhanu. It was my understanding that what Gcam does, mostly, is to apply some sort of software "magic" to what the sensors record, and in this respect, the 48MP main sensor on the Note 9S isn't too shabby, so I'd really like to give it a try, but as I said in my OP, every time I did what was advised in the tutorials I read, i.e. press somewhere in the camera interface (left of the capture button), I always got the same "no config file to load" message, although I had a config file waiting to be installed, one that I had downloaded along with the Gcam .apk file, so I was wondering if there were APKs that already contained said config file, and if so, where can I find them?
For example, this article points at two different builds based on Gcam 8, but it doesn't mention where to find the config file that goes with either one of them.
hi, i like the way you replied,
about gcam i have found v7.4 its recommended to use v7 because they are relatively stable.
link:- http://www.mediafire.com/file/n6zvk...wFjJ1hSydvsFIulyLOShEyHF73I-Hcbch7knXmuWUwVis
just open app and go to settings and developer settings and disable use google photo to use it.
or simply install google photos to make this version work.