Camera and Mi Fit App won't work - Galaxy S II Q&A, Help & Troubleshooting

I have two Galaxy S2's; an everyday one and a spare. Both were stock ROMs and generally do everything I want a phone to do.
Recently, however, I needed to install an app (Mi Fit) that needs Android 4.4 upwards so I tried installing a new ROM on my spare S2. I should say that this was an unused, out of the box phone and everything worked fine with the stock ROM.
Initially, I tried to install a custom 7.1 ROM and it worked fine except that Mi Fit crashed every time I tried to pair the Mi Band. Also, TomTom would not work and several other apps failed to work. So, I tried another 7.1 ROM and then several 6 ROMs all to no avail. I had several boot loop issues during this and an "almost bricked" phone that would only go into Download mode but got over all of them. I then tried several 4.4 ROM's but Mi Fit crashes still when trying to pair the band. Also, the camera crashes when trying to load and all other camera apps that I have tried crash as well. One camera app says that the external SD card is not allowing third-party apps to access it. However, I have tried a couple of patches to cure this and they say the card is fine.
I have successfully loaded custom ROM's on other devices and think I (more or less) know what I am doing but am really stuck on this one.
Any help gratefully accepted.

Coaster750 said:
I have two Galaxy S2's; an everyday one and a spare. Both were stock ROMs and generally do everything I want a phone to do.
Recently, however, I needed to install an app (Mi Fit) that needs Android 4.4 upwards so I tried installing a new ROM on my spare S2. I should say that this was an unused, out of the box phone and everything worked fine with the stock ROM.
Initially, I tried to install a custom 7.1 ROM and it worked fine except that Mi Fit crashed every time I tried to pair the Mi Band. Also, TomTom would not work and several other apps failed to work. So, I tried another 7.1 ROM and then several 6 ROMs all to no avail. I had several boot loop issues during this and an "almost bricked" phone that would only go into Download mode but got over all of them. I then tried several 4.4 ROM's but Mi Fit crashes still when trying to pair the band. Also, the camera crashes when trying to load and all other camera apps that I have tried crash as well. One camera app says that the external SD card is not allowing third-party apps to access it. However, I have tried a couple of patches to cure this and they say the card is fine.
I have successfully loaded custom ROM's on other devices and think I (more or less) know what I am doing but am really stuck on this one.
Any help gratefully accepted.
Click to expand...
Click to collapse
This should be posted in Q&A and troubleshooting but no one seems to care about this.
Anyway, I got mi fit working fine until now. Last time i used mifit on los14.1 where quite long ago but i remember that it still work. I'm on 8.1.0 now amd mi fit still working fine

Disappointed no-one came to my aid but just to let you know I fixed the problem(s).

Coaster750 said:
Disappointed no-one came to my aid but just to let you know I fixed the problem(s).
Click to expand...
Click to collapse
It's not ideal you were not offered any assistance but sometimes the issue is too niche or obscure for anyone to have any advice.
What I think would be nice is instead of just saying "I fixed the problem", you detail exactly HOW you fixed it so in future someone with a similar issue searching for help can benefit from your success. What do you think?

As you say, very niche problem so I didn't elaborate. All I did was went back to basics, read the "Android Hacker's Toolkit" book from Jason Tyler and worked through everything until the problem went away. Oh, and reading loads of stuff on here and elsewhere. Not all of it is true (shock horror) but all is now well - and I am not 100% sure what the problem was so won't add to the pool of less than accurate information caught in the web.

Related

[HELP]-Rooted Atrix, Radio/WiFi/BlueTooth Error/Problems

Of course I searched around the forums for a fix but I could find a direct post with a fix. I rooted my phone a year ago ish and installed different roms. Recently added the beta CM 10/10.1. Everything worked find for about a month. Then for some reason the wifi stopped working. Got an error and then the phone crashes/reboots sometimes locks up. Tried recovery into other roms and still nothing. I read its a possible hardware fail but that cant be the reason. Every once in a great while the Wifi will work for about a minute then error out.
Does anyone have a fix that worked for them that had same symptoms? Or know of a working fix?
Thanks.
Applying pressure to various points with various objects seems to have helped some. Other than that, it definitely sounds like the well-known hardware failure. Just because wifi works now and then doesn't mean it's not it.

[Q] Can't connect to the camera!

Hi everybody,
You may have already seen this title so many times, and I have too when I was looking for an answer to my problem, though no luck in finding one.
I bought a Huawei G510-0100 a couple of days ago and for some reason decided to root it straight away. Before rooting everything worked fine, and I only did it in hopes of getting it a bit faster and getting rid of bloatware.
Anyway, I followed this guide I found to root the Huawei G510-0100 http://forum.xda-developers.com/showthread.php?t=2315932 and it turned out fine, except for the fact that I now cant use the camera anymore.
I have tried
rebooting
taking out the battery for a couple of seconds and restarting,
clearing cache
deleting gallery.apk
flashing a more recent version, 4.2
3rd party apps like camera360 or snapchat
reflashing the firmware provided in the thread I just linked
and nothing works
I dont know if its something incompatible between the firmware and the phone, if I should just look for another ROM, but I havent had much luck finding custom roms or anything since this phone is not that popular.
What should I do?
Thanks in advance
Look this:
http://forum.xda-developers.com/showthread.php?p=43523285

Screen mirroring, Sound no work.......

So, gave the screen mirroring a try today in the car (Appradio) connected to (Microsoft wireless display adaptor) got video, touch even worked, but the sound came out through the phone. Tried for a while, different apps, nothing, still through phone (Sound)
So tried my old lg g3 worked perfect first time, sound and full mirroring worked.
LEads me to believe its the phone.
Now the s6 is rooted, using unikernel atm.
ive tried using different roms, but they are all linked to samsung ones (Other phones you could have completely custom roms, samsung though apparently not) but the roms where the samsung mirroring is not present, theres no mirroring, tried a google search of an apk to add the lollipop native mirroring, couldnt find it.
So yeah, my last resort, help!! Been at this for five hours now and bricked my phone 3 times, someone please help, i just want to achieve mirroring with sound, i know its samsungs tech i should be going to but lets face it, you guys are armore useful than they are, plus the first person to solve it gets a few beers!!!
rgray99c said:
So, gave the screen mirroring a try today in the car (Appradio) connected to (Microsoft wireless display adaptor) got video, touch even worked, but the sound came out through the phone. Tried for a while, different apps, nothing, still through phone (Sound)
So tried my old lg g3 worked perfect first time, sound and full mirroring worked.
LEads me to believe its the phone.
Now the s6 is rooted, using unikernel atm.
ive tried using different roms, but they are all linked to samsung ones (Other phones you could have completely custom roms, samsung though apparently not) but the roms where the samsung mirroring is not present, theres no mirroring, tried a google search of an apk to add the lollipop native mirroring, couldnt find it.
So yeah, my last resort, help!! Been at this for five hours now and bricked my phone 3 times, someone please help, i just want to achieve mirroring with sound, i know its samsungs tech i should be going to but lets face it, you guys are armore useful than they are, plus the first person to solve it gets a few beers!!!
Click to expand...
Click to collapse
You're lucky you're able to mirror even video because when you have a modified kernel, it breaks screen mirroring. Every Samsung i've had I had to stay away from custom kernels because I mirror my screen often enough that i rather stay stock then lose that. Sometimes I could use wanam to fake system status but even then, the mirroring wasnt as smooth as it were on a stock kernel
So if I put the stock kernel back on it then it will work again?? Will I loose root if I do so?
If so is there anyway of keeping root when going back to stock kernel?
rgray99c said:
So if I put the stock kernel back on it then it will work again?? Will I loose root if I do so?
If so is there anyway of keeping root when going back to stock kernel?
Click to expand...
Click to collapse
Kernel and root and 2 different things. One is dependent on the other but the other is not. You can have stock kernel while rooted without a problem. Thats what I do.
You can flash stock kernel in recovery and you will stay rooted.
Well I managed to get screen mirroring to work. Stumbled across a rom called echorom. That appears to work whilst keeping both gear manager and root. So happy days. Figured I'd post the solution as not many do.
http://forum.xda-developers.com/showthread.php?p=62005518

[Q] Issues with Magisk after the US998 conversion (ISSUE RESOLVED, THX)

I really really do hate asking for help and 99.63757% of the time I can fix things myself doing the necessary research into the problem(s) and potential solutions, but so far this one has me stumped and I'm too frustrated with it to just keep starting over so I'm asking for assistance from anyone that might be able to help, so here goes...
OK, so I picked up two H931 V30's the other day for $100 (for both, actually), one is slightly damaged (glass damage just under the Menu/Recents button area) but it's 100% functional, the second one is pristine. I did the conversion to the US998 without any issues on the undamaged one since the damaged one is for my Wife and she has no need for root/custom ROMs/massive amounts of tinkering like I've been doing for 20+ years or so. Unlocked the bootloader without issues too.
So, I get everything done according to the WTF guide (very nicely done piece of work, seriously) and it's up and running without issues. But then I decide to check and see if Magisk has an update so, I scroll over, find the Magisk icon, tap it, and I get that damned message I always get about updating to the latest version, either choose "NO THANKS" or "YES" and that's when the problems start. This is Magisk 18.0 by the way, and I've attempted this with 18.1 as well, and even the latest 19.1 and it still happens like this regardless:
The phone then suddenly turns into molasses in winter as far as operational speed goes. It chokes, then it dies, then the Home screen resets exceedingly slowly as if it suddenly went from the powerhouse phone it is to 1 frame per second or something in functionality.
The phone heats up like crazy, then I eventually am forced to hold Volume Down + Power and force it to reboot, and it does reboot and gets right back into the OS like nothing happened and everything works as normal.
But I cannot get Magisk to do anything at all, the app itself apparently never loads, doesn't function, I can't update it or get it to run in any way at all. Everything else works, including apps requesting root which is given by Magisk as it should. I know that with the unlocked bootloader Netflix won't install by default, and I know Magisk is installed and functional because Netflix shows up in the Play Store and I was able to install it and watch a video and the Magisk Manager icon is clearly right there on my device.
I've done this like 7 times now and I'm not going to do it again for the moment, I'm gonna end up corrupting something from all the flashing I think and then doing it again, then again, etc.
On my V20 I had this issue in the past (not recently) where when I attempted to execute the Magisk Manager app it constantly asked me that question when it starts up and regardless of "NO THANKS" or "YES" or even if it's updated to the latest version it always asks me that damned question and I've never been able to get it to stop. But with the V20 the app does load and I'm able to access features of the Magisk Manager.
On this V30, I can't do anything at all and I always have to reboot the phone hard and I'm kinda sick of doing that. So I started over again an hour ago, everything is working fine for the 8th time except probably Magisk. I haven't touched the icon but it's installed, root is working fine, but I really do want to understand WHY this crap keeps happening and WHY I can't get Magisk Manager to run properly without crapping out the phone.
If anyone can help or offer some suggestions I'm all eyes (given this is a text-based communication medium, obviously).
Thanks, and have fun, always...
bb
Haha I love that you got the mint one and gave your wife the dinky cracked one.
Well the damage is inconsequential, and she's been using a Stylo 2 Plus that has glass damage in almost exactly the same place, go figure. I'm tougher on devices than she'll ever be but I do the tinkering around with stuff, not her.
br0adband said:
I really really do hate asking for help and 99.63757% of the time I can fix things myself doing the necessary research into the problem(s) and potential solutions, but so far this one has me stumped and I'm too frustrated with it to just keep starting over so I'm asking for assistance from anyone that might be able to help, so here goes...
OK, so I picked up two H931 V30's the other day for $100 (for both, actually), one is slightly damaged (glass damage just under the Menu/Recents button area) but it's 100% functional, the second one is pristine. I did the conversion to the US998 without any issues on the undamaged one since the damaged one is for my Wife and she has no need for root/custom ROMs/massive amounts of tinkering like I've been doing for 20+ years or so. Unlocked the bootloader without issues too.
So, I get everything done according to the WTF guide (very nicely done piece of work, seriously) and it's up and running without issues. But then I decide to check and see if Magisk has an update so, I scroll over, find the Magisk icon, tap it, and I get that damned message I always get about updating to the latest version, either choose "NO THANKS" or "YES" and that's when the problems start. This is Magisk 18.0 by the way, and I've attempted this with 18.1 as well, and even the latest 19.1 and it still happens like this regardless:
The phone then suddenly turns into molasses in winter as far as operational speed goes. It chokes, then it dies, then the Home screen resets exceedingly slowly as if it suddenly went from the powerhouse phone it is to 1 frame per second or something in functionality.
The phone heats up like crazy, then I eventually am forced to hold Volume Down + Power and force it to reboot, and it does reboot and gets right back into the OS like nothing happened and everything works as normal.
But I cannot get Magisk to do anything at all, the app itself apparently never loads, doesn't function, I can't update it or get it to run in any way at all. Everything else works, including apps requesting root which is given by Magisk as it should. I know that with the unlocked bootloader Netflix won't install by default, and I know Magisk is installed and functional because Netflix shows up in the Play Store and I was able to install it and watch a video and the Magisk Manager icon is clearly right there on my device.
I've done this like 7 times now and I'm not going to do it again for the moment, I'm gonna end up corrupting something from all the flashing I think and then doing it again, then again, etc.
On my V20 I had this issue in the past (not recently) where when I attempted to execute the Magisk Manager app it constantly asked me that question when it starts up and regardless of "NO THANKS" or "YES" or even if it's updated to the latest version it always asks me that damned question and I've never been able to get it to stop. But with the V20 the app does load and I'm able to access features of the Magisk Manager.
On this V30, I can't do anything at all and I always have to reboot the phone hard and I'm kinda sick of doing that. So I started over again an hour ago, everything is working fine for the 8th time except probably Magisk. I haven't touched the icon but it's installed, root is working fine, but I really do want to understand WHY this crap keeps happening and WHY I can't get Magisk Manager to run properly without crapping out the phone.
If anyone can help or offer some suggestions I'm all eyes (given this is a text-based communication medium, obviously).
Thanks, and have fun, always...
bb
Click to expand...
Click to collapse
Are you thinking the problem is with Magisk manager or with Magisk itself?
Sent from my LG-US998 using Tapatalk
br0adband said:
So, I get everything done according to the WTF guide (very nicely done piece of work, seriously) and it's up and running without issues.
Click to expand...
Click to collapse
You're welcome.
br0adband said:
But then I decide to check and see if Magisk has an update so, I scroll over, find the Magisk icon, tap it, and I get that damned message I always get about updating to the latest version, either choose "NO THANKS" or "YES" and that's when the problems start. This is Magisk 18.0 by the way, and I've attempted this with 18.1 as well, and even the latest 19.1 and it still happens like this regardless:
Click to expand...
Click to collapse
When we first started rooting the V30 (first with the official LG bootloader unlock codes for the few that were eligible) over a year ago, we had Magisk 16.0, 16.1, then Magisk 17.1. (I think 17.0 was just very unstable if I remember correctly.) As each became more stable we upgraded to newer versions, but some in between were never used. For the longest time, I delayed recommending 18.0 until it was proven.
18.0 upgraded to 18.1 easily, but Magisk Manager keeps nagging me to update to newer version. Clicking on Magisk Manager keeps prompting me to install newer version (for 19.x) but it never successfully installs. I know I will have to flash the uninstaller in TWRP and then download 19.1 and reinstall in TWRP. I hesitate doing that because it was a major pain last time to re-choose all the apps I want root or want to hide.
One time while doing it it I ended up with TWO Magisk Manager apps in my App drawer. I had to uninstall Magisk again (in TWRP) and reinstall yet again.
All that to say this.... Have you tried flashing uninstaller for Magisk in TWRP, then reinstalling 18.1 or 19.1 or whichever one you want?
Here's the uninstaller...
https://github.com/topjohnwu/Magisk/releases/tag/v19.1
I'll give that a shot I suppose, can't really hurt much if it fails - and yes I'll do a TWRP backup first.
It's just odd because the root aspects are OK as stated, everything gets root that requires it (I only have a few apps like the root add-on for fx File Explorer, LTE Discovery to get some additional data, Titanium Backup which I don't even really use that much but paid for years ago, etc). I reached a point in the past where I was like "What do I really need to do all this crap for anymore, stock ROMs are actually quite nice and stable, that's more important over the long run that tinkering constantly..."
Been tinkering on consumer electronics since the 1970s when I was a wee tiny kid, just getting sick of it nowadays and want the devices to just work well. Sure I can eek out a bit more in terms of performance if I put in hours of tweaking and configuration but honestly, it works just fine as it is on the stock ROM and I'm OK with that so far.
I'll see about uninstalling Magisk and installing 18.1, see what happens when I do actually attempt to run the Manager and then if that fails uninstall it and give 19.1 a shot and report back.
EDIT:
OK, for whatever reason when I uninstalled 18 and then flashed 18.1 I got no dice, no idea why so I then rebooted to recovery again, removed 18.1, then flashed 19.1, got back into the OS, installed the latest Manager again and poof, voila, now it works.
Bleh, I tell ya, sometimes... 3rd time's the charm, or the 4th, or the 10th, or something.
Thanks for the responses, this one is now done.
FWIW, I upgraded 18.1 to 19.1 on my phone (VS996) a while ago and it's been working fine... just to provide a datapoint. Aside, this also allowed GPay to work properly as well.

Lots of issues with LG V600TM

Hi guys.
I'm quite new here so forgive me if I put the post in the wrong place.
Let me try to describe my issues with my phone.
A couple months ago I got a new LG V60 from my wife (brand new but without warranty).
The first problem I noticed after a few days was that the fingerprint scanner wasn't working properly. I mean everyone can unlock my phone after a few tries placing finger on the scanner at an angle.
When I try to unlock the phone by fingerprint it takes ages (it's very difficult to unlock the phone for the first time). I was trying remove saved fingerprint and create a new one but the problems is still there.
Another problem is with losing signal from satellites when using navigation. I was trying Google maps, Sygic and TomTom and it's look like the Google works best but there is still problem with signal, quite often I get information about 'searching position'.
Next one is that the phone is freeze sometimes and I have to restart it to work properly. It's happening around once a week.
I was trying hard reset but it didn't fix it, then I downloaded the original firmware with android 10. I don't know if it helped because I got lots of updates and it ended up on the Android 12 again. At the beginning of use after this operation the phone was working better but after a couple of weeks the same problems came back.
I'd like to add if I want to do a back up I get information like this "the required google certificate has been deleted". On Android 10 this information wasn't appearing.
Do you have guys any idea what's wrong with this phone?
Thank you in advance.
emillo83 said:
Hi guys.
I'm quite new here so forgive me if I put the post in the wrong place.
Let me try to describe my issues with my phone.
A couple months ago I got a new LG V60 from my wife (brand new but without warranty).
The first problem I noticed after a few days was that the fingerprint scanner wasn't working properly. I mean everyone can unlock my phone after a few tries placing finger on the scanner at an angle.
When I try to unlock the phone by fingerprint it takes ages (it's very difficult to unlock the phone for the first time). I was trying remove saved fingerprint and create a new one but the problems is still there.
Another problem is with losing signal from satellites when using navigation. I was trying Google maps, Sygic and TomTom and it's look like the Google works best but there is still problem with signal, quite often I get information about 'searching position'.
Next one is that the phone is freeze sometimes and I have to restart it to work properly. It's happening around once a week.
I was trying hard reset but it didn't fix it, then I downloaded the original firmware with android 10. I don't know if it helped because I got lots of updates and it ended up on the Android 12 again. At the beginning of use after this operation the phone was working better but after a couple of weeks the same problems came back.
I'd like to add if I want to do a back up I get information like this "the required google certificate has been deleted". On Android 10 this information wasn't appearing.
Do you have guys any idea what's wrong with this phone?
Thank you in advance.
Click to expand...
Click to collapse
I also have the v600TM on Android 10. I have had no problems with the fingerprint except after the first time I unlocked the bootloader (see 1st post for the fix). I did not allow an update to Android 11 or 12. Maybe you should try the fingerprint on A10 for awhile before moving to 12.
Hopefully you don't have one of those Chinese refurbs pretending to be new!
AnnexedOne said:
I also have the v600TM on Android 10. I have had no problems with the fingerprint except after the first time I unlocked the bootloader (see 1st post for the fix). I did not allow an update to Android 11 or 12. Maybe you should try the fingerprint on A10 for awhile before moving to 12.
Hopefully you don't have one of those Chinese refurbs pretending to be new!
Click to expand...
Click to collapse
Hi
Thank you for the reply.
Maybe you right and I should try to use the phone on android 10 and see if it's works properly. I'll see what happens.
Do you know when android 13 will be available for V60?
As a owner of the V30, V40 I'm really disappointed of the V60 now.
emillo83 said:
Hi
Thank you for the reply.
Maybe you right and I should try to use the phone on android 10 and see if it's works properly. I'll see what happens.
Do you know when android 13 will be available for V60?
As a owner of the V30, V40 I'm really disappointed of the V60 now.
Click to expand...
Click to collapse
Hi,
You're welcome. When you are new to a forum or group, its like you are invisible.
My current main phone is the V30. The V60 has been more difficult than past phones to configure the way I want. When I installed TWRP a few months ago it was a DISASTER! Installing MicroG (to replace google play services) has also not worked out well. I have limited funds and I am beginning to wonder if the V60 was a good choice.
There is already an Android 13 beta for some versions of the V60.
The thing with V60 is that it is newer than V30. So a lot of fixes are not fully cooked. With LG gone from the scene, there is no incentive for developers to pursue it with any dedication. I don't know if TWRP will be fully built for this phone.
Audio_Lover said:
The thing with V60 is that it is newer than V30. So a lot of fixes are not fully cooked.
Click to expand...
Click to collapse
I do remember how slow the V30 was in the beginning. Now the V30 has a bunch of ROMs and an OFFICIAL LineageOS! I hope the V60 goes the same way. I doubt it, though.
Audio_Lover said:
I don't know if TWRP will be fully built for this phone.
Click to expand...
Click to collapse
I forgot to mention that I posted a possibly newer (than 3.6.0-11) version of TWRP for the V60:
TWRP 3.6.0-11
Here a updated recovery. All credit goes to @UnlockLG https://drive.google.com/file/d/1P-wc8aJ6zVDC1xiKfdTKfzGoh2kQHIPp/view?usp=sharing
forum.xda-developers.com
Hi guys
It's me again with another problem
As for the above problems that I wrote about, I decided not to do anything about it for now and patiently wait for the android 13 update and see what happens.
How happy I was when two days ago I received the opportunity to download the update.
The joy did not last long, as it turned out that I'm unable to download the update.
Previously, I got information like 'The phone is being use and update will be downloaded later' (or something similar). Now the update downloads for a while and pops up 'Installation problem' and cannot be downloaded (always in the same time). I restarted the phone, deleted apps, changed from WiFi to mobile data and still the same.
Do you have guys any ideas what can I do with it?
As far as I know the phone is from US (T-mobile) and I live in the UK.
Thank you in advance for your help
emillo83 said:
Hi guys
It's me again with another problem
As for the above problems that I wrote about, I decided not to do anything about it for now and patiently wait for the android 13 update and see what happens.
How happy I was when two days ago I received the opportunity to download the update.
The joy did not last long, as it turned out that I'm unable to download the update.
Previously, I got information like 'The phone is being use and update will be downloaded later' (or something similar). Now the update downloads for a while and pops up 'Installation problem' and cannot be downloaded (always in the same time). I restarted the phone, deleted apps, changed from WiFi to mobile data and still the same.
Do you have guys any ideas what can I do with it?
As far as I know the phone is from US (T-mobile) and I live in the UK.
Thank you in advance for your help
Click to expand...
Click to collapse
If you unlocked the bootloader, I hear that updates don't work.
AnnexedOne said:
If you unlocked the bootloader, I here that updates don't work.
Click to expand...
Click to collapse
Thank you for the reply.
How to check if the bootloader is unlocked?
As I said before I haven't done anything yet with the phone as I was waiting for the update but I'd like to check it, maybe the bootloader was already unlocked
emillo83 said:
How to check if the bootloader is unlocked?
Click to expand...
Click to collapse
When the phone is starting up (after being off or rebooting) it will say something like: This phone cannot be checked for corruption. Lock the bootloader.
If the bootloader is locked I suggest you backup before doing a factory reset.

Categories

Resources