I have been using the LG v495 on 5.0.1 with some healthcare related Bluetooth devices without any problems. ATT forced the 6.0 update and it caused the BT devices no to work (or spotty at best) and also have problems paring these devices. Is there a way I can go back to 5.0.1 with these tablets? I still have a few that have not yet updated to 6.0 Possibly a way to back up the 5.0.1 from one tablet and restore it to a 6.0 tablet. Not sure why the 6.0 BT is buggy with BT devices that worked fine on 5.0.1
Any help would be appreciated.
Bump? No one has done this?
I don't have the V495 bit did you try a factory reset (which will wipe everything including all user apps, data and internal storage)?
Factory wipe does not change the firmware..
jaingram said:
Factory wipe does not change the firmware..
Click to expand...
Click to collapse
I know it doesn't change your firmware, I mean did you try one to see if Bluetooth improves?
Yep, several times, unfortunately, it didn't help the pairing issues.
Related
Upgraded my Note 10.1 2014 edition to KitKat 4.4.2 with the download from Sammobile, first with the Colombia then with the Cellular South firmware, all works fine but the tablet turns itself off after a short time of inactivity. The only way to get the tablet to start back up is to press the power button as if it is a normal power up. Is anyone else having this issue? I've checked all of the settings and find no way of solving this. Please advise, thanks.
Morqua said:
Upgraded my Note 10.1 2014 edition to KitKat 4.4.2 with the download from Sammobile, first with the Colombia then with the Cellular South firmware, all works fine but the tablet turns itself off after a short time of inactivity. The only way to get the tablet to start back up is to press the power button as if it is a normal power up. Is anyone else having this issue? I've checked all of the settings and find no way of solving this. Please advise, thanks.
Click to expand...
Click to collapse
Are you using any custom kernels ? if not , then a factory reset would be the best scenario for your problem.
lsherif said:
Are you using any custom kernels ? if not , then a factory reset would be the best scenario for your problem.
Click to expand...
Click to collapse
Not using any custom kernels and have tried to reset to factory settings on both Colombia and Cellular South firmware, nothing seems to work, and the tablets turns itself off if it is not being used. I'm sure this issue was caused by the 4.4.2 upgrade as nothing like this happened before the upgrade. Really don't know what else to do.
Same thing happened to me after I rooted on 4.3 & 4.4.2. I would always have to power it back on. When I unrooted, the problem went away.
Sent from my SM-P600 using xda app-developers app
Thanks for the input Russ, but mine isn't rooted. I guess I will have to hope for a firmware upgrade to come out soon, and see if that will help to fix the issue.
strange, I do exactly the same and have no issue.
USA version flashed, no wipe and all seems to be fine.
Did you try to wipe your tab to see if issue still exist ?
lightman33 said:
strange, I do exactly the same and have no issue.
USA version flashed, no wipe and all seems to be fine.
Did you try to wipe your tab to see if issue still exist ?
Click to expand...
Click to collapse
No wipe, just factory reset, unless they are the same :angel:.
Well this is probably what you don't want to hear but I had a similar problem, my stock 4.3 unit rebooted itself in the middle of a game (of "The Room 2" if that's important), and from that moment on started to do the same thing, I updated to the Colombian 4.4.2 to see if that would fix (including a wipe (not just a factory reset) but that didn't fix it at all, in the end I had to replace it after a short row with the gimp at PC world. Currently running the Cellular South 4.4.2 without any issues so far (bar the missing Volume/Brighness bar I mentioned in another thread).
It had all the hallmarks of a memory fault. Good luck, I hope you can fix it and that it's not hardware.
44566455 fitness
flathunt said:
Well this is probably what you don't want to hear but I had a similar problem, my stock 4.3 unit rebooted itself in the middle of a game (of "The Room 2" if that's important), and from that moment on started to do the same thing, I updated to the Colombian 4.4.2 to see if that would fix (including a wipe (not just a factory reset) but that didn't fix it at all, in the end I had to replace it after a short row with the gimp at PC world. Currently running the Cellular South 4.4.2 without any issues so far (bar the missing Volume/Brighness bar I mentioned in another thread).
It had all the hallmarks of a memory fault. Good luck, I hope you can fix it and that it's not hardware.
Click to expand...
Click to collapse
Yes, this is just weird, as this issue started after 4.4.2. What is weirder is the fact that I tried to root it by following this guide http://forum.xda-developers.com/showthread.php?t=2490805 and after multiple tries, "Rootchecker" still says that my device isn't rooted.
is anyone having the same issue as me,
i came from kitkat and flashed v20h stock rom and supersu as per the instructions, everything works fine except my lg apps such as quickmemo+ and lg remote cannot be downloaded using the update centre,
i managed to find the apk and install, and it just doesn't let me update them either,
anyone had this problem before?
Same Boat.
Any solutions? I have the same problems after flashing to Lollipop also. However, I did make a mistake of wiping "internal storage." This is the glitch after that screwup. I resolved the other issues (no softkeys and no notification bar) by flashing Kitkat THEN LP. This issue remains, so I restored LG apps from Ti backups. but they will NOT download and/or update. They do work.
This all started because my 1st LP flash self destructed. It kinda feels like a permission thing. I am hesitant to do another reset (the right one). But I don't want to go forward until I fix this. I think the reset must do something to the LG App Updates app when you fist boot. I think it must see some stuff from internal storage that I had zapped. Since it was't there and now fails.
I know we can't be only two. problem seems rare though. So far.
I have a Sprint Note 4 and until I rooted it my watch connected fine, worked great, looked great with the Pebble Steel band. Now it fails to connect no matter what I do. I have done everything I know to do as a fairly experienced phone geek. Outside of unrooting and reinstalling the stock ROM I cannot get it to connect.
My question is: Do I now need to root my watch so I it will connect to my phone?
EdHicks said:
I have a Sprint Note 4 and until I rooted it my watch connected fine, worked great, looked great with the Pebble Steel band. Now it fails to connect no matter what I do. I have done everything I know to do as a fairly experienced phone geek. Outside of unrooting and reinstalling the stock ROM I cannot get it to connect.
My question is: Do I now need to root my watch so I it will connect to my phone?
Click to expand...
Click to collapse
I'm using my unrooted Moto360 with my rooted Sprint Galaxy S5 running a custom Tom. No problems connecting.
EdHicks said:
I have a Sprint Note 4 and until I rooted it my watch connected fine, worked great, looked great with the Pebble Steel band. Now it fails to connect no matter what I do. I have done everything I know to do as a fairly experienced phone geek. Outside of unrooting and reinstalling the stock ROM I cannot get it to connect.
My question is: Do I now need to root my watch so I it will connect to my phone?
Click to expand...
Click to collapse
Did you reset the watch and reinstall on android wear on your device?
Ramer said:
I'm using my unrooted Moto360 with my rooted Sprint Galaxy S5 running a custom Tom. No problems connecting.
Click to expand...
Click to collapse
Where did you get a custom Tom? [emoji12]
No problems connecting my stock 360 with my xperia ultra running slimkat
joshm.1219 said:
Did you reset the watch and reinstall on android wear on your device?
Where did you get a custom Tom? [emoji12]
Click to expand...
Click to collapse
Darn auto-correct. lol
joshm.1219 said:
Did you reset the watch and reinstall on android wear on your device?
Where did you get a custom Tom? [emoji12]
Click to expand...
Click to collapse
I reset the watch, reinstalled Android Wear and tried to re-pair, no success. Even Factory reset phone and installed Android wear and then try to re-pair. No success.
The only time I was able to re-pair was by unrooting.
We'll see what happens when I upgrade to 5.0.1. In the process of upgrading, re-rooting, re-installing TWRP and then VisionX Rom.
If I have to I will root the watch. I was just curious if my problems were root related.
EdHicks said:
I reset the watch, reinstalled Android Wear and tried to re-pair, no success. Even Factory reset phone and installed Android wear and then try to re-pair. No success.
The only time I was able to re-pair was by unrooting.
We'll see what happens when I upgrade to 5.0.1. In the process of upgrading, re-rooting, re-installing TWRP and then VisionX Rom.
If I have to I will root the watch. I was just curious if my problems were root related.
Click to expand...
Click to collapse
Could you link me to the root method you used? Root access is simply enabling you control of the /system partition and if done properly shouldn't be affecting anything like your Android Wear connection.
I am using my Moto 360 on rooted Sprint Note 4 without issue. I actually had issues with the watch staying connected until I rooted my Note and flashed a custom rom. Uninstalling Android Wear and Moto Connect then factory resetting the 360 to go through the whole pairing process again resolved all issues I had.
joshm.1219 said:
Could you link me to the root method you used? Root access is simply enabling you control of the /system partition and if done properly shouldn't be affecting anything like your Android Wear connection.
Click to expand...
Click to collapse
The latest CF Auto Root at the time.
My (unrooted) Moto 360 connects just fine with my rooted YotaPhone 2...
I suspect that rooting isn't the culprit, but installing a custom ROM.
Custom ROMs usually involve removing/adding/replacing files, and you can't always be sure that the required files for Android Wear connection are still present in the custom ROM you're using...
Things you might want to try, if not already done, are installing another custom or vanilla ROM,
and/or connecting another Android Wear watch to your phone with the initial custom ROM.
Good luck, anyway! I hope you can find a way out of this situation...
Update
Thanks to everyone for all the help.
Since the Lollipop update all is functioning properly. I'm still curious as to why I rooted the phone and it wouldn't connect just to learn why...
it has always worked fine with my Rooted Nexus 6, glad you where able to get it working again!
Can anyone help with this. I have a sprint note 4 that I rooted and was working great, but wanted the stock 5.0.2 upgrade. Used odin to install stock 4.4.4 and remove root. Worked fine phone took the 5.0.2 upgrade. Rerooted and installed wifi tether router but could not get it to work, found it is not working on 5.0.2, dam. Used odin once again to return to stock 4.4.4, rooted, installed wifi tether, everything works with one problem. When turning the screen on I now have a severe lag between the button push and the screen light up.
I odined back for other issues and still had problems. .even a backup was not working... i wiped everything, all data etc, 2 times then went back to nie....then took the otas back to lollipop. .now everything works fine except i still hate the colors
Sent from my SM-N910P using Tapatalk
Fixed, it was a bad sd card had nothing to do with the dowgrade.
Good to hear you found your problem. However if it's tethering that's keeping you away from Lollipop then you can put that to rest because you can easily enable wifi/usb tethering without the need for a third part app like tether router (which i have payed for as well). If you expect to stay on the factory rom/firmware then Lollipop would be a wise choice due to the new ART (android runtime) and it's overall effeciency compared to KK . It has a lot of benefits and other than the stock colors, there's no reason you shouldn't update to Lollipop. Do a little searching here in the Sprint Note 4 forum and you'll find a few easy ways to enable the built-in tethering.
Thanks for the info, did exactly that, found galaxy tools would provide the tether
Downgrade help
Hey
I need some help downgrading my phone from LP 5.02 OE1 update
I have no service and need to re unlock
What files did you use?
Can you send me a link. Odin fail with everything
badgal said:
Hey
I need some help downgrading my phone from LP 5.02 OE1 update
I have no service and need to re unlock
What files did you use?
Can you send me a link. Odin fail with everything
Click to expand...
Click to collapse
You are SOL for now. Cant downgrade rom OE1, but a new OTA is about to come out, I'd sit tight until then. or...Many people flash Noterized Rom. Try flashing that and continue your troubleshooting.
Stuck
Here is my screen
UPDATE:
I gave up and installed the stock Samsung ROM. For any germans on "open" A3s: The Austrian open version of 7.0 works fine. Not network related or other issues for me.
Hu guys,
I installed TWRP, rooted and tried installing xposed installer from here.
After that I got stuck in bootloop. Tried formatting data and a factory reset various times now, but I always get stuck in bootloop again.
Any idea how I can fix my messing up?
Thanks!
timbohenry said:
UPDATE:
I gave up and installed the stock Samsung ROM. For any germans on "open" A3s: The Austrian open version of 7.0 works fine. Not network related or other issues for me.
Hu guys,
I installed TWRP, rooted and tried installing xposed installer from here.
After that I got stuck in bootloop. Tried formatting data and a factory reset various times now, but I always get stuck in bootloop again.
Any idea how I can fix my messing up?
Thanks!
Click to expand...
Click to collapse
Why do you install an Xposed version for L and M on N?
Anyway, you have to flash stock again since a factory reset does not repair damaged system partitions. I would use SmartSwitch for returning to the latest official firmware.
edisso10018 said:
Why do you install an Xposed version for L and M on N?
Anyway, you have to flash stock again since a factory reset does not repair damaged system partitions. I would use SmartSwitch for returning to the latest official firmware.
Click to expand...
Click to collapse
I only flashed 7 after being stuck in bootloops. Before that I was running 6 and installed Xposed for 6.
Any reason in pareticular for not running Austrian 7 in Germany? Seems to work just fine.
Thanks!
Your post was misleading... And no. If it works use it.