Build.Prop and Camera Issues - X Style (Pure) Q&A, Help & Troubleshooting

I've tried searching here and google in general to no avail. I have a XT1575 w/ marshmallow. I have been able to get the systemless root to work just fine for me. I've been trying to get tethering to work (I had it work fine before on a Nexus 5 and on Lollipop w/ root and xposed/moto tether) but I just can't seem to get everything to work right together. I have been able to get tethering to work by editing my build.prop file by adding net.tethering.noprovisioning=true however when I do that my camera no longer works. I've tried it in multiple apps, I've even tried taking screenshots. For some reason once I edit build.prop I just lose the ability to take pictures of any sort and it's beginning to frustrate me quite a bit. Any ideas as to why editing build.prop stops my cameras from working? Your help is appreciate.

Related

Force Close on every app

Every time I try to use the keyboard it force closes the running app.
For example I open gmail, I click on reply and it force closes. (because it automatically wants to pop up the keyboard) same goes for chatting in Trillian and every other app that uses the keyboard.
By default I use Swiftkey X Tablet, I turned that off and it still forced closed, I uninstalled every keyboard (except the default Samsung one) with no luck or whatsoever.
I tried googling but I couldn't find anything related, is there a quick fix or am I bound to flash a new ROM on it?
I am using stock ROM on the GT-P3110 with the android version 4.0.3.
Cheers.
Ditched stock for CM9, everything works again.
I still wonder where the problem was though.
The keyboard closing everything problem happened to me when the clipboard became corrupt. I have a post elsewhere on this board that describes how I fixed it. Search is down or I'd find it and link to it. The basic idea is to nuke the contents of /data/clipboard. You lose your "pinned" clipboard items but you can then get things to quit closing.
I am thinking about going to CM9 but wonder if you lose anything other than the dumb Sammy apps? For example, the IR blaster (which I don't really use anyway) or anything like that.
Update: Ok Google knows all: http://forum.xda-developers.com/showthread.php?t=1655619
Brilliant, if it happens again I will use that. Still an annoying bug.
Also would you need root to nuke the contents of that directory?
I have the European version of the Tab 2 7" so I don't have an IR blaster, but I suppose you could just extract the .apk (it could be included in the ROM I have no idea.)
Everything feels a lot smoother on CM9 to be honest.
Thanks for your help!
I don't know, but I bet you need root. Then again, the clipboard must be writable so maybe not. I had thought I would not root this device right away but 5 minutes after I booted it, I realized I needed root for Titanium Backup and that was that.
I recall copying a 5k line javascript. Odd bug. Though I suppose going into Recovery mode and then wipe data would also do the trick if you indeed do need root access.

is there any way to increase the scroll rate on the stock rom?

I'm back using the stock rom from cm10 so I can use the Samsung dock. I'm so used to the faster scroll rate on jellybean roms is there any way my scroll/fling rate can be increased? I looked through the build prop but didn't see anything I could edit though I may have missed it.
You on the right track. You should be able to increase the fling/scroll rate. Also the windowsmngr one. If you not seeing those in JB build.prop, then you can always add those lines in there. Refer to the various build.prop mod threads for exact lines you should add..
demandarin said:
You on the right track. You should be able to increase the fling/scroll rate. Also the windowsmngr one. If you not seeing those in JB build.prop, then you can always add those lines in there. Refer to the various build.prop mod threads for exact lines you should add..
Click to expand...
Click to collapse
That's my problem I can't find anything in the stock build prop relating to fling/scroll. I'm just not real comfortable and have never added lines
There's an app called rom toolbox in playstore. They have a free version and a paid one. I believe its made by an xda member or its praised by xda. One feature of it is that it allows you to "Properly" add a line to build.prop. without having to worry about formatting and stuff. Plus it automatically makes a backup of your original build.proof in case something goes wrong or you need to revert back to it. I used it on my transformer prime and works very well. Even if you don't want to add a line, it'll allow you to edit/increase values of existing lines in your build.prop. I think you need to be rooted. Can't remember. But I do remember that this tool worked perfectly for me. Alot of times using other methods of editing build.prop is risky. Formatting can mess up which will cause you issues on booting up.
Check it out. Its free. As always, read up and research on it before committing to edit. Wouldn't want you to Bork device. Which many have blindly editing build.prop. plus, depending on what you change in there, there's the likelyhood of not being able to install OTA updates.

Amiduos and root

For those who are looking for a good emulator for their PC and genymotion/andy doesn't quite cut it for you, check out Amiduos from http://amiduos.com/ I am working on some tutorials on how to root/debloat/xposed the emulator, I have them posted up on my blog: http://talesfromtheandroid.blogspot.com/2015/09/amiduos.html I am almost finished with the 2.0 part, but it is not hard to manually root.
Happy rooting!
Amazing! Great job, and thanks a lot for this. I was using bluestacks, but ya, that's a piece of crap compared to this. Amiduos is a lot faster. Everything went well following the instructions on your blog for the 2.0 version. I only have one problem, and I know that it's because snapchat is the most piece of crap app ever created in the existence of mankind. Seriously, I have never seen a more problematic app across so many devices. Anyway, ya, it crashes on Amiduos 2.0 .. It seems like it does the exact same thing as what happens on my old-school Galaxy Tab 10.1 WiFi (GT-P7510). You can install it and open it to the login/signup screen just fine, but once you login and it attempts to go the main snapchat UI (where it shows the camera open), it crashes to home screen. I can understand it happening on the Tab 10.1 because it's such an old tablet with old architecture, and I've actually confirmed that it is just the Tab's capabilities itself because I've confirmed with a few other users with the exact same Tab that they have the same issue with snapchat, but you would think it would work fine with Amiduos. This doesn't happen on bluestacks, but my issues with bluestacks were a whole other deal. First off, it's slow compared to Amiduos, but aside from that, I was able to root and get Xposed installed on the latest version. Snapchat actually opens and runs fine on it, but when attempting to use snapprefs (xposed module), it basically doesn't work. It's strange because it was actually working on the first try on the 0.8.11.3116 version of Bluestacks, but snapchat had an issue where if I logged out and then tried logging back in, it gave me some BS login error, and I had to essentially just create a new account. I ended up screwing a few things up in my attempt to solve the issue by clearing data and cache on a number of apps including the xposed framework, and ya, I basically had to reinstall bluestacks, root, install xposed, etc. At that point it wasn't working anymore lol. Snapchat will just crash when attempting to share a photo into snapprefs (that's how you get a photo from gallery into the snapchat editing UI), or it would just show a black screen in the snapchat UI. I'm not sure if I want to try genymotion/andy for my snapchat/snapprefs needs. I might just have to use my old-school jailbroken iPhone 4 to run a tweak that basically does the same thing as snapprefs. The only reason I liked snapprefs better (when it was working on bluestacks) is because it didn't affect the quality of videos that I shared from gallery to send through snapchat. Phantom for snapchat (jailbroken iPhone tweak) seems to do that. Would you happen to know what the issue might be, and how to get snapchat working on Amiduos?
AmiDuos 2.0 Root Solved !
Previous Post:
http://forum.xda-developers.com/showpost.php?p=66391966&postcount=32

Cast(screen mirroring) issue

I love everything about this phone
But, yesterday I tried to screen mirror my phone onto my Samsung smart tv and the cast setting just says no devices found as I open it. It doesn't even search for devices. Just immediately says no devices. It's not a problem with my tv since I've tried it with other phones and it works fine. I've seen online that many previous moto g versions have this problem. I've got the g5plus made in China 3gigs RAm and 32internal
You need to add this in build.prop to make it working (youll need root for this):
persist.debug.wfd.enable=1
Enviado desde mi Moto G (5) Plus mediante Tapatalk
When you in the cast menu click the 3 dot menu in the top right and select wireless display. Your phone should now recognize your TV and you should be able to cast.
I have MoTo G5 Plus, it does cast but after 4 minutes it disconnects, which is so , I still did not find any cure of this problem
enable cast but camera error
Hello,
I did the root with the toolkit (works pefect, thanks). After that the camera works perfect.
And I also changed the build.prop like: persist.debug.wfd.enable=1 (works also perfect). Cast is enabled.
But then I cant start the camera. Always error (restart camera).
I read a lot about the camera issue and I tried different things (reboot, clear cache...). I flashed different stock roms an tried camera mods but its always the same.
When I change the build.prop like before (...enable=0) the camera still dont work.
The only thing that is different between my build.prop and the things I read here is that in my original build.prop was a # before and the number 1 was already there like:
#persist.debug.wfd.enable=1
I delete the # or I edit (persist.debug.wfd.enable=1) at the end of the build. Both things enable the cast (the three dots). But the camera dont work.
(I like the stock rom very much. I tried custom rom but I always came back to stock!)
Maybe someone can help me!?
solved: https://forum.xda-developers.com/g5...-bootloader-potter-version-t3694952?nocache=1
Moto g5s plus screen mirror in issue
I have moto g5s plus. I tried to enable miracasting by root my device using magisk. I find build.prop file, there already persist.debug.wft.enable-1. but still miracasting not shown in cast section. Plz help...

Working android build.

Hi all. Your android solution may be here. I have installed most of the recent android builds available. The below build from konstakang has worked and for me has a good functionality and minimal crashes so far.
http://konstakang.com/devices/rpi3/CM14.1/
I have tried the more recent Oreo 15.1 build but this one has a better display performance. There is a bug with not being able to change the wallpaper but will check with konstakang how to get working.
I tried the build before looking into over clocking but a revisit greatly improved performance and less lag by editing config.txt. Accessed config.txt from a root search via Nautilus after flashing the downloaded image via etcher. Only added
force_turbo=1 #Voids Warranty!
boot_delay=1 #helps to avoid sdcard corruption when force_turbo is enabled.
I didn’t go any further with over clocking as this seems to make the difference. Not seen the CPU temp more than 70c yet. Check out the below link.
https://haydenjames.io/raspberry-pi-3-overclock/
Finally to get things up and running no need for the play store at all so I wouldn’t even bother. It only causes major crashes and Aptoide is sufficient. I have root access from the settings menu and have downloaded quick root reboot. Chrome and Showbox along with mx player. All working. CPUx gives stats such as core temp. Will be able to get terminal access also from app download. The media apps do seem to shutdown occasionally but i hope a wifi dongle upgrade add-on will sort this out.
http://en.aptoide.com
Hope this helps someone and let me know if have the same or different luck. Big up to the developers and website authors!
I tried the 8-10-17 build, and I could any apps I installed would crash immediately. I could not get the resolution to fit my TV screen either after changing resolutions in the boot config. Have you ran into any issues like this?
I had problems with older builds from the same source and others. Even paid for one from Exton but he's a rip off merchant. Try this one that I had in the op.
http://konstakang.com/devices/rpi3/CM14.1/
Read the FAQ about root access and download quick reboot from Aptoide.
As I said it works reasonably well. Try the over clocking and apps from Aptoide. Also reboot a couple times I've read makes a difference with things crashing. If you find an app continuously crashes then uninstall and try different one.
My TV displays fine. 49inch 4k. I guess if yours doesn't from first boot then could Google for the correct config.txt script. This newer build seems to detect the TV resolution but don't quote me on that.
I wouldn't go for the newer konstakang Oreo build as was laggy but of course give it a go if you like. Konstakang builds seem to be the best on the net so far and I've tried loads since the new year. See what the next one is like as well as he's pretty up on current development.
is this a stretch img?
Not sure what you mean by stretch?
I'm guessing this is also for the RPi 3B+?
This was done on the pi3b. I don't know if it's works on the newest model.
Stops bootlogo n shuts down
First boots situation
Flashed with etcher

Categories

Resources