Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Guys any help
KartmanCV said:
Guys any help
Click to expand...
Click to collapse
Use some other rom... Recommended crdroid latest build... Use picogapps... And try again...
The issue could be rom related and even after trying new rom the problem still persists then it could be a baseband issue...
Try the recommended rom first with complete full wipe .. Good luck
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
nicky.phoenicks said:
Hi,
Were you able to fix this?
I'm facing the same issue. Tried several basebands and ROMS. Also, flashed stock rom through QFIL/QPST, but the issue is still there.
Thanks,
Click to expand...
Click to collapse
Were you able to fix it??? How did you resolve? After three years, I faced this issue all of a sudden after I changed my phone's battery, and tried everything with software but no fix. Any possibility that it is a hardware issue? How can it be deeply inspected to find the real cause of this problem?
KartmanCV said:
Hello folks!
I recently found a strange bug on my Zuk Z2(Plus).
I was running it in AICP 20170901 build along with Orbot App. I had a situation when the phone started heating up and the battery drain became faster. As I was travelling and wanted to save the last ounce of juice, I deleted Orbot, to cool down the phone as it was continuously running in the background. My phone got switched off later, but once I was able to charge it, I tried connecting it to my home Wifi network. It just kept showing "Connecting" and later "Saved", but never connected. After repeated attempts to connect, it shows "Saved". Frustrated with this, I did a clean wipe and installed a previous backup of AICP 20170901 build which I saved a few days prior to this. But to my surprise, I was again unable to connect. It kept doing the same thing.
So, I did a clean wipe and did a fresh install of AICP 20170901 build and again, the same thing kept repeating. So, I installed the stock rom to check if it might work on that, but to my luck it didn't. So, I switched back to my earlier backup of AICP, and installed Dark Moon Kernel 004.1, But again no luck.
Between multiple ROM switches, it sometimes connects to the network and doesn't connect to the internet and then gets automatically disconnected.
Is there some fix to this. I think Orbot messed up something, and I am unfortunately not that tech savvy to find out what it did. Orbot is meant to replicate Onion Router, but landed me in a soup
Please advice.
Click to expand...
Click to collapse
Is there any fix found for this? or is it forever? Need help, need to give this phone to someone but can't fix this issue. Please help through any ways.
You may try resetting the carrier and wifi network. This may help.
You may try resetting the carrier and wifi network. This may help.
Related
Hi there,
Just wanted your point of view regarding something really strange that happened to me yesterday.
(btw, I looked it up all over the forum + google but still unabale to find a proper answer)
So basically, I droped down my phone, which crashed on the floor but nothing really serious. Ever since, every time I try and turn on the wifi, it says "Error".
I've tried rebooting it several times and still get the issue.
Do you guys think the wifi chip could have been broken? Is there any report log I could find using terminal or root explorer?
Phone specs:
Virtuous Unity v1.29.0
Android 2.3.3
Phone rooted
Bluetooth does turn on
Thanks in advance for your help
Try flashing a different rom, back up your current one first, and check out if the wifi is working without restoring any apps.
Did you ever fix this? I did the exact same thing, dropped onto hard tile. Wifi error and couldn't read data partition.
Randomly after a day or 2 it fixed itself and was fine for 2 weeks.
BUT...just happened again today. I wiped caches, reflashed ARHD, fixed all permissions. Data partition became readable again (not sure which of those fixed that) but i still get "Wifi Error" when turning wifi on.
Any help/suggestions much appreciated.
I currently have Jandycane 1.3 flashed and I'm having some really weird issues. Every time I turn Wifi on and it detects my network, my router starts to act up causing it to forcefully reset itself, affecting every device connected to it. I didn't have this issue with Jandycane 1.1 ( I did not flash 1.2 ). I'm not sure if this is an issue with the ROM itself or an issue with the updates Hashcode made, as he's been tweaking with the wifi. I did in fact wipe everything before flashing.
Please excuse me if I have overlooked this being answered before, but as I was trying to search for a solution I was constantly greeted with an error about the board having high traffic.
-
It appears now that if I flash back to 1.0 or 1.1, I have this problem as well. I did not have this problem prior to flashing 1.3, and I have wiped everything (cache, dalvik, factory reset, system and SD card)
And just to note, I realize that not everyone is having this issue but myself and some others are.
-
After a few reboots I managed to get Wifi working again on 1.0, but still cannot get it working on any others.
-
Flashed 1.3 over 1.0 making sure to only wipe the two caches and kept wifi on. Upon booting, Wifi now works without a problem. Still not sure what the problem was/is but at least it's resolved for now.
narume said:
I currently have Jandycane 1.3 flashed and I'm having some really weird issues. Every time I turn Wifi on and it detects my network, my router starts to act up causing it to forcefully reset itself, affecting every device connected to it. I didn't have this issue with Jandycane 1.1 ( I did not flash 1.2 ). I'm not sure if this is an issue with the ROM itself or an issue with the updates Hashcode made, as he's been tweaking with the wifi. I did in fact wipe everything before flashing.
Please excuse me if I have overlooked this being answered before, but as I was trying to search for a solution I was constantly greeted with an error about the board having high traffic.
Click to expand...
Click to collapse
Im using 1.3 and it works fine. Try to reflash it
Sent from my Amazon Kindle Fire using XDA Premium HD app
I tried that, thinking it might have been a bad flash but the problem still persists. I also downloaded the ROM again to make sure it wasn't a bad download, but after flashing it, the same problem occurs.
I cannot connect to my router with any of the jelly bean builds it perpetually attempts to connect always saving then going right back to acquiring ip address
After downloading Hashcode's ROM, I can say in good faith that the problem persists in the newer update that Hashcode has done while he was fixing the wifi issues. I did not have this problem on either ROM prior to the recent update, but now Wifi does not work at all and when it is scanning for networks, the second it picks up mine it sends some kind of signal to my router and forces it to constantly reset itself.
narume said:
After downloading Hashcode's ROM, I can say in good faith that the problem persists in the newer update that Hashcode has done while he was fixing the wifi issues. I did not have this problem on either ROM prior to the recent update, but now Wifi does not work at all and when it is scanning for networks, the second it picks up mine it sends some kind of signal to my router and forces it to constantly reset itself.
Click to expand...
Click to collapse
Yeah try any of lithiums builds before the hw codecs were added they connect fine just no hw codecs when he did a sync with the WiFi revision that's what borked it for me and yes my router did crap out on me once as well on the present builds literally shut off then on again or reset of some nature??
My router logs state disconnected reason: deauthenticated
Thepooch said:
Yeah try any of lithiums builds before the hw codecs were added they connect fine just no hw codecs when he did a sync with the WiFi revision that's what borked it for me and yes my router did crap out on me once as well on the present builds literally shut off then on again or reset of some nature??
My router logs state disconnected reason: deauthenticated
Click to expand...
Click to collapse
I finally got one to connect the new one by twa_priv with the Sgt7 enhancements also I did opt out of googles backup service for my tablet in account setup because I noticed that after I was on the net on my WiFi tether it greyed my signal out and I had no net so I reflashed after a full wipe minus the SD card and opted out of Google service and all my connections are good including my home router for me this is a breakthrough the only jelly bean that connects to my home network
I'll give his a go. I didn't flash it as I was worried it would suffer from the same problem as the others recently have started doing, I also noticed a few complaints about the UI force closing. Guess it's really the only JB solution for now until this issue is resolved. I have a Dalvik log in case Hashcode wants to take a peek.
narume said:
I'll give his a go. I didn't flash it as I was worried it would suffer from the same problem as the others recently have started doing, I also noticed a few complaints about the UI force closing. Guess it's really the only JB solution for now until this issue is resolved. I have a Dalvik log in case Hashcode wants to take a peek.
Click to expand...
Click to collapse
The thing I experienced with fc`s of the ui is trying to change it to tablet mode personally I can live with it in phone orientation I just like to test everything all jb ROMs have bugs but no WiFi is a deal breaker for me
Appears I'm having this problem now with every JB rom. 1.0 and 1.1 worked fine prior to flashing 1.3, but now every JB rom I flash, including 1.0 and 1.1 have this problem. I've no clue what is going on.
-
Got it working on 1.0 after a few reboots, but cannot get it working on the others.
-
Flashed 1.3 over 1.0 making sure to only wipe the two caches and kept wifi on. Upon booting, Wifi now works without a problem. Still not sure what the problem was/is but at least it's resolved for now.
WiFi problems here appeared over time
narume said:
I currently have Jandycane 1.3 flashed and I'm having some really weird issues.
Click to expand...
Click to collapse
For me it worked great last night; then when I got home I could not even enable WiFi. On a lark I reflashed 1.3 [with only cache wipe, not /data], and the WiFi started working again, and still is, now.
Even with it working, I'm seeing many wpa_supplicant errors, including:
D/wpa_supplicant( 561): nl80211: survey data missing!
I/wpa_supplicant( 561): wpa_driver_nl80211_driver_cmd: Unsupported command SETSUSPENDMODE 1
Any ideas?
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.
I was connected to my wifi, left my phone alone for a few hours, and when I came back (yesterday), i saw the wifi not connected. I go to try and reconnect it, and it says wifi turning on, and nothing else happens, it is stuck there. I can not get it to connect to my wifi. Any idea what could cause this? what can I do?
Gsm galaxy nexus, paranoid android 3.99 android 4.3.
mobile data, calls, text, etc all work great, only problem is wifi seems to be stuck. I tried rebooting, but still nothing.
Any ideas, and thanks for your help.
Been reading other threads. Going to make a nandroid backup and factory reset this baby see if that works. I will let you know. If not I will try another room or go back to stock. If anyone has any other ideas highly appreciated.
Sent from my Galaxy Nexus using Tapatalk 4
malystxy said:
Been reading other threads. Going to make a nandroid backup and factory reset this baby see if that works. I will let you know. If not I will try another room or go back to stock. If anyone has any other ideas highly appreciated.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Factory reset, nothing, restore previous nandroid from 6 months ago, noothing. Still stuck at turning on wifi, but nothing more than that happens. Would screen shots help I can post them. Last resort going to go back to pure stock see if that fixes it.
If not I am guessing hardware problem? anyone have somthing similiar happen, and what did you get to work if anything to fix it? or is my wifi module fried? Thanks any who have input.
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
malystxy said:
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
Click to expand...
Click to collapse
Could indeed be your wifi antenna. Had a similar experience with a T-Mo MyTouch3G a while back. Same symptoms.
Are you clearing all caches, factory resetting, and wiping the system partition from recovery?
Last case, you should restore to absolutely stock, relocking your bootloader and everything.
iLeopard said:
Could indeed be your wifi antenna. Had a similar experience with a T-Mo MyTouch3G a while back. Same symptoms.
Are you clearing all caches, factory resetting, and wiping the system partition from recovery?
Last case, you should restore to absolutely stock, relocking your bootloader and everything.
Click to expand...
Click to collapse
Awesome, thanks for responding, was beginning to wonder if anyone was reading it
What I tried so far (each time wiping dalvic cache, cache, and doing full factory reset from both within android and cwm):
Factory reset on paranoid android 3.99 android 4.3 = nothing
Install cyanogemod 4.3 = nothing
Restore my nandroid backup of bixie deodexed stock rom (which i used before going to paranoid) = nothing
try other version of android from 4.1, 4.2, etc. on varion roms = nothing
restore to google stock (as far stock as possible minus locking bootloader, means yes, stock recovery and everything), 4.1, 4.2, 4.3 = nothing.
ran out of ideas, learned alot though, and got more flashing experience than I care. Did learn how to adb backup, more about android backups, etc though. Some good has come out of it, but my original problem of wifi was and is still not resolved.
Unless there are other ideas, I am pretty convinced the wifi antenna/module died (and a google search confirms others have had something similiar happen, they had to replace the pcb to fix it, which is costly where i live, Argentina). So may just use it sans wifi until I get a new phone, thing has a couple years anyway and nexus 5 is about to be announced.
But I am open to any and all suggestions least I still have hpsda+ speeds 70% of the time.
malystxy said:
OK, update, nothing I did work, android 4.1, 4.0, 4.2, 4.3, factory, stock, custom, cyanogemod, paranoid, nothign solves it.
I suspect my wifi module dyed out. anyone else have something similiar happen?
Click to expand...
Click to collapse
initialize, discoverPeers, connect : working
file trasnfer : not working
i guess, wlan driver of kernel space is missing. ex) nl80211.c & wl_cfg80211.c
my phone is android 4.1, 4.2 in AOSP.
i nothing solves it, too :crying:
somebody Help~~
This thread is over a year old, but I'm having the same problems lately. The device was reluctant to auto-connect to known wifi networks, which I attributed to the current and latest CM11 snapshot. Then, a few weeks ago, the phone became unstable, with random reboots 3 or 4 times a day. Clearing cache and Dalvik cache didn't help. I didn't want to do a full-wipe, with CM 12 on the horizon. About 2 days ago all wifi reception stopped. I could activate wifi in the software, but the device wouldn't receive any signal at all (checked with Wifi Analyzer). So I was afraid that the wifi died out permanently. This morning, in a last attempt I switched off the phone and took out the battery for a couple of minutes. On restart I was surprised to see that wifi found a known network and received an ip-address. However, an internet connection never established and the menu reported a bad reception. I then de-activated and re-activated wifi, but that didn't bring me any further. I guess I'll wait for the first CM12 nigthlies to find out if miracles still exist.
Hi, I have the latest CM12 installed in my tablet, but I have a lot of issues, especially when installing multiple apps or if I try to change the Launcher. It gets into boot loop and there is nothing one can do but re-flash the rom, which is pretty annoying. It has happened to me already 3 times in a short while and I am thinking of flashing LineageOS. However, I hear it is still very buggy, especially the issues with wifi. So I would like to ask which is the least buggy Rom for 7.0 v410 or if there is a way to avoid CM12 from getting the problem with boot loop.
Boot loop has been caused when trying to change Launcher (because trebuchet regularly crashes), when installing x-plore file manager and in a clean flash when I attempted to install multiple apps at the same time. In all cases it got stack in boot loop, or would start only to restart after a while, endlessly.
Finally, I opted for LineageOS 14.1.
I had the 11-11 Nightly for some time and seemed fine. Today I updated to 25-11 Nightly. It feels maybe slightly laggy, but still checking it.
I have also installed "Best WiFi Keeper" app from play store and it generally keeps me connected. However, if connection is lost (e.g at restart or if I get out of range), I have to reconnect manually. I tried few apps for reconnecting but nothing worked. It appears that although the WiFi network is seen, the tablet cannot really re-establish the connection automatically.
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Tesla works great for me. I'm running a lollipop version that's still on androidfilehost; I'm not sure if GZR ever got updated beyond 5.1 for V410.
I've had CM 14.1 (long enough ago it was still CM and not LOS) on the tablet, and it felt like it would get laggy. That could just be from junk my kid installs though, but I don't seem to have that problem with Tesla.
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
kingzones said:
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
Click to expand...
Click to collapse
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
jason2678 said:
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
Click to expand...
Click to collapse
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
xdause said:
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
Click to expand...
Click to collapse
I'm on Tesla, but it has the same base as Tipsy. I don't have data on the tablet so it isn't a 100% conclusive test, but it doesn't seem to work. The switch for USB tethering never turns on. Wifi turns on but never connects properly. My laptop does briefly show connection then disconnects with both USB and wifi tethering. It could be because there is no data connection on my tablet, but looking through dmesg on the laptop gives me the impression that something on the tablet isn't working right.
kingzones said:
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Click to expand...
Click to collapse
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
nicospanas said:
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
Click to expand...
Click to collapse
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
KLit75 said:
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
Click to expand...
Click to collapse
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
nicospanas said:
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
Click to expand...
Click to collapse
Thanks. That's more or less what I thought. From what I'm hearing there are some bugs in the roms that no doubt aren't being maintained at this late stage so I think I'll stick with stock (would be nice to have a custom recovery though.)
Not that it matters (a year later) but lots of people root with Kingroot when there isn't another option and there's several ways to remove all the bits left behind and switch it to supersu.
Thanks again!
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
kingzones said:
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
Click to expand...
Click to collapse
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
nicospanas said:
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
Click to expand...
Click to collapse
That would be great.. I shall try.. if successful, I shall post results.
I have a uk410, the US Cellular variant of the v410. I tried the CM12.1 "stable" release cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-v410.zip found here (archive.org/download/cmarchive_snapshots), along with Open GApps nano for 5.1 (opengapps.org/?api=5.1), and quickly got the infinite rebooting issue.
I then switched to the Telsa ROM mentioned earlier in this thread (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip) found at androidfilehost.com/?fid=24052804347807214, again with Open GApps nano for 5.1 (build open_gapps-arm-5.1-nano-20180922.zip), and have been running it with no issues for two days. My wifi is connected, and stays connected (tested two different routers), Play Store and apps have been working fine, and no crashes so far.
I'm using TWRP 3.1 (twrp-3.1.0-0-v410.img).
Thanks for mentioning Tesla, @jason2678 !
So like all of you I was looking for a rom to install on this v410 7" tablet, and it looks like I should just give up or stick with 4.4.2 stock if I want to go through the rooting process.
Basically all the development roms end with the same problems, wifi dropping, hostspot not working, no ir blaster, volume problems, bluetooth errors, and several hundred posts about lolipop memory leaks crippling the tablet because of only 1gb mem.
So, I am asking all of you, is there any real reason to root it, besides going back to stock 4.4.2?
And lastly, is the stock 4.4.2 kdz image that is floating around a test version, and if so is there an actual official kdz image somewhere that isn't a test image?
Thanks...
CrDroid by far in my opinion. Lineage based, 7.1.2.
Also, e/ os has been unofficially released. No Google anything...an entirely new Google list operating system by lineage. It's lightning fast and runs magisk perfectly. It's basically like nothing you've ever seen before and if you look under LG g pad 7.0 on Android file host, go to the second page and click on the last user who goes by the name anonymous and you'll find the ROM there. I had no idea what it was until my g pad boot it up and I saw the e logo. I pretty much **** myself in excitement