Related
For some reason on any ROM (I'm on RR right now I tried OOS and other versions of RR) my WiFi turns itself off when the screen is off. And ONLY whatsapp doesn't receive or send messages like it supposed to. I tried some other modem/firmwares to fix this but none seemed to work (I'm on 3.2.7 now I tried 4.0.0, 4.0.2, Open beta 11, 10 ,9) I also tried other kernels (I'm on Boeffla now I tried Elemental X and default kernel which came with Resurrection Remix).
No matter what I did (at least as I know) nothing changed so far. In every (if not every most of them) ROM, kernel and modem/firmware same thing happened. WiFi turns off itself when the screen is off and WhatsApp doesn't work like it supposed to..
And yes I clean flashed these ROMs I tried using different IPs and DNS I also tried to reset wireless settings and I also checked the setting to turn WiFi off when screen is off.
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
Hi guys,
I updated my op3 to latest beta 28 but I got random reboots when I'm not using it;
in fact, usually it reboots when charging or when it's in standby, and other moments like that.. I really don't know why!
I checked the MD5 of the zip, I flashed with the latest bluspark 8.54 and I did a full wipe;
I also reflashed with a dirty flash the ROM(and other ROMs based on Oxy).
Nothing changed.. it appears 2-3 times per day.
Anyone of you got the same error? which could be a solution?
I had exactly the same problem, but flash rom via adb fixed that.
not experiencing any.. stock non rooted...
Kshysiek said:
I had exactly the same problem, but flash rom via adb fixed that.
Click to expand...
Click to collapse
Sounds interesting.. will try! Thx in advance
Morning! You're not the onlyone having troubles with OB28, I'm facing similar issues aswell. Decided to wipe all and perform another clean install (not via adb as suggested above) yesterday afternoon and no issues so far. Will keep you updated
Running ExperienceOS by Jamal btw, which is based on stock OB28
I have had this as well. Just keeps rebooting randomly.
Dirty flashing the rom ob28 helps and keeps it stable. But then it reappears after some time randomly. It could be after a few hours or a day or two as well. Yesterday it just started rebooting while it was lying on the desk.
I suspect it could be because of a custom kernel. I have moved from custom to stock (rooted) for now. Lets see
Having same with ob28 also with 5.0. Sometimes it starts rebooting when charging, sometimes while just laying on the desk. 2 times I had it rebooted to recovery. I have even missed an alarm. I found a phone rebooted to recovery in the morning.
Yesterday clean installed 5.0. Rebooted 10 minutes ago. Dirty flashed ob28, retooting also.
Sent from my ONEPLUS A3003 using Tapatalk
In another thread, someone suggested rooting with SuperSU instead of Magisk. Tried that and now stable of over 2 days. You might give it a try
It has something to do with magisk or bluspark twrp in combination with something. Tried installing Supersu. Rebooting stopped, but dm-verity message appeared when booting. Decided to format everything. Flashed original recovery, but it could not decrypt file system. Tapped on forgot my password and it wiped everything. Sideloaded OOS 5.0, rebooted, then flashed twrp via fastboot. Flashed magisk 14.5. Stable for 2 days.
Sent from my ONEPLUS A3003 using Tapatalk
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
creezalird said:
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
Click to expand...
Click to collapse
Same behaviour here on OxygenOS 5.0 with Magisk 14.5 and Boeffla kernel. I usually wipe cache and dalvik in TWRP 3.2 and then it's fine for a couple of hours (or days, if I'm lucky).
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
basvanasperdt said:
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
Click to expand...
Click to collapse
Same here
Been in SuperSU for 3 days. No issues so far
Op3 ob28
I had random reboots on Freedom OS 3.1 after about two weeks of use with stock kernel and Magisk 14 (no issues before that). Flashed Blu Spark 207, didn't help. Flashed FOS 3.2: neither. Somebody suggested aggressive dose to be the culprit. It wasn't as I didn't had it enabled for starters. I Flashed official OB28 + magisk and stock kernel... And after one day, reboot. Flashed Blu Spark 208, reboot. But after a couple more reboots last week, they seem to have gone by themselves:
$ uptime
02:00:49 up 4 days, 6:48, load average: 2.98, 2.01, 2.24
*I had not tried using super su instead.
What can we do to debug this issue? Seems like everybody is trying to guess in the dark...
---------- Post added at 09:31 AM ---------- Previous post was at 09:10 AM ----------
If I may suggest, there seems to be a sort of "environmental" origin for this... I've noticed some "correlated incidence of reboots" between unrelated devices, regardless of specific OB variant (OB, FOS, EOS), kernel (stock, Blu), and root method, based on number of complaints and reports of generically unsuccessful attempts to solve the issue in the respective ROM threads, and here too.
Besides, I've not been able to identify any usage related trigger: this has happened to me while phone is idle, while browsing this thread, while driving thru unknown and dangerous streets guided by Waze, while commuting on the subway and only listening music...
Some more rigurous analysis of the prevalence of these reboots as a function of time might prove useful...
Also, there seems to be a growing incidence between users. There seems to be also a "incubation time" for most of us (but not for everybody). Are we sure we are not talking about some disease?
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
simpele said:
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Click to expand...
Click to collapse
strange1712 said:
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Click to expand...
Click to collapse
abhibnl said:
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
Click to expand...
Click to collapse
Kshysiek said:
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
Click to expand...
Click to collapse
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
candiesdoodle said:
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
Click to expand...
Click to collapse
With magisk 14.0 and later magisk 14.5. Now I'm testing without root at all, as it seems to be magisk related, it is also reported on the magisk thread.
Hi guys. My device is op3 bought from india. I was having this problem of Severe random restart and sleep of death after a few days updating to oreo. I have tried all kind of room oos 5 , z unleashed, rr 6 rom, Omni rom from Oreo builds. They all made problem. I reverted back to oos 4.5 I was still facing same problem but less severe. Tried vortex carbide, aospa, Los but same problem but only sometimes. I tried hard brick recovery by msmdownloadtool but no result.
Then I installed multirom 33 from xda and oos 4.5 and sultan xda LOS 14.1 together. Suddenly I was facing no problem in sultan xda Los. So I just wiped everything and now using sultan xda as primary room without uninstalling multirom and multirom twrp. Now for two days it's running fine.
I was thinking that this is hardware issue, but now it seems that it's software issue.
But I am not a Dev so can someone tell me in software side what are things cannot be solved by msmdownloadtool?? I want to use oos but I am stuck with sultan xda los14.1
I never have any crash in recovery or boot. Everything happens after I start the OS and start installing apps.
I'm absolutely losing my mind please help
A little story time, skip to the end for my question;
So, how to start - One day I unlocked my bootloader, went for some android 11 rom and all was fine. Then android 12 was released and I downloaded the crdroid 12 rom, where I was experiencing some battery drain issues. So I downloaded pixel experience rom. The Bluetooth died because of this rom's cursed source code. I flashed the latest miui fastboot rom and the Bluetooth issue still persisted (remember this for later - not all the drivers flash with the Rom). I fixed the Bluetooth issue by switching several miui roms, also made a guide if you're interested. That fixed the Bluetooth issue and I went for pixel plus ui rom. It was a bit laggy, so I switched to the shiny new Evolution X rom. It was amazing, so much stuff co customize, etc. Well, i experienced another battery drain issues, so I just went for the stock miui with magisk pixelify module. Im pretty fine with this rom, and I thought the problems are gone, because it stock and everything should be fine. Well no. The battery drain issue persists. I was wondering what even is happening, so I opened battery settings. That said that the top apps wasting my battery is screen, Google services and android system. I downloaded a CPU usage stats app, which showed me that the cpu usage is at 99% (I think it's correct as the phone is overheating). The app with most cpu usage was using only 1%. I don't know if this is a firmware bug or whatever, but I think some rom broke it and the latest stock miui didn't overwrite that driver, as written above with the Bluetooth issue.
So, how can I make my phone be as it was released from xiaomi with all the drivers to actually use the hardware correctly?
Thanks in advance for any replies, I'm seriously going to throw my phone out of the window
Also the way how I install the stock Rom is by downloading the latest fastboot rom, extracting it and executing ./flash_all.sh file.
SOLVED! My problem was because of my credit card. I have my cc in the phone case. The cpu was going insane because it was constantly detecting the card and loading info from it. Literally turning off NFC fixed this whole issue. Bruh.