(FIX) How to fix Wifi not automatically coming on a CM7 reboot - Kindle Fire General

So I think i found a fix for the wifi not being turned on when rebooting in CM7. I found the info here: http://forums.androidcentral.com/ba...art-automatically-after-reboot-cm7-0-2-a.html
I found this on another site and did it to my nook with the terminal emulator and it fixed the problem:
Quote:
Open a terminal (either directly on the nook or via "adb shell") and type the following
su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
delete from system where name = 'airplane_mode_on';
.exit
and exit the shell again.
Now the airplane mode should be turned off completely and the wifi should again still be turned on after booting when it was turned on when shutting down.
Now my wifi is on after reboot.
Click to expand...
Click to collapse
I followed these instructions using adb and it worked perfectly. Now when I reboot my CM7 fire, my wifi is turned on! Woot!!

I wonder wat causes the problem, I haven't ever experienced it. Hell, I just flashed the new CM7 update and everything came right back on, wifi with passes entered...

The Anthem said:
I wonder wat causes the problem, I haven't ever experienced it. Hell, I just flashed the new CM7 update and everything came right back on, wifi with passes entered...
Click to expand...
Click to collapse
Airplane Mode causes it... I recommend editing setting.db as follows:
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
UPDATE system set value='0' WHERE name='airplane_mode_on';
UPDATE system set value='cell' WHERE name='airplane_mode_radios';
UPDATE system set value='bluetooth,wifi' WHERE name='airplane_mode_toggleable_radios';
The above can be performed via adb or via terminal mode on the device itself... it sets airplane mode off... and sets cell as the only radio turned off by airplane mode.
The setting of toggleable_radios honestly has not worked... since wifi has always been set there... and while sometimes the wifi radio seems to turn on... it never connected to a network... by having wifi not turned off... it (in theory) should help.

Related

[Q] How to fix Wifi "Turning on" stuck when restoring hasn't helped

Hello xda,
Just two days ago out of the blue while transitioning from home to the train with the Tegra on off (I remember turning it off during charging before I left) as I sat down on the train I found it turned on (unusual) I didn't think much of it but since then I later noticed that my Wifi was stuck on the "Turning Wifi on" message and that the app wouldnt allow me to click the cog in the top left to return to the settings page (moreover when I click the open programs buttons it just disappears..strange) the only reason my attention was brought to this was because my Bluetooth gave me an error saying it couldnt share bluetooth anymore.
At the time I thought a simple restart would fix it but nope it didn't. My tegra is rooted but I have had no problems until now!
Since then I have done
Factory data reset
Cleared memory cache
Factory restored using the advent factory 4.3 image http www adventcomputers co uk / product-download-select/296 (sorry first posts and I don't seem to be allowed to post links).
Right now I find myself stuck at the "Welcome" screen as after I select a language and press next the wifi tries to turn on and I cannot skip this.
Any suggestions on what I should/could try please? Is it a hardware problem like it happened with the Samsung Galaxy?
Thank you
Does anyone have a suggestion?
I am trying to compress the latest stock rom (Roms Stock 4.4.2 from rootjunkysdl) into a system.img in ext4 format so as to then place it in the automatic Vega-tegra recovery tool found at: www adventcomputers co uk / product-download-select/296
At the moment I am stuck at the fompressing a folder directory into an ext4 file .img format.
Anyone have any ideas?
The reason I am trying the above is because upon resetting it with the above mentioned recovery tool, the WiFi is still on "turning on" however with it resetting it to version 4.3 means I cannot find a way to bypass the welcome screens as it won't allow me past until I manage to connect it to the internet.
Please, any help at this point would be very much appreciated
Fiztban said:
Does anyone have a suggestion?
I am trying to compress the latest stock rom (Roms Stock 4.4.2 from rootjunkysdl) into a system.img in ext4 format so as to then place it in the automatic Vega-tegra recovery tool found at: www adventcomputers co uk / product-download-select/296
At the moment I am stuck at the fompressing a folder directory into an ext4 file .img format.
Anyone have any ideas?
The reason I am trying the above is because upon resetting it with the above mentioned recovery tool, the WiFi is still on "turning on" however with it resetting it to version 4.3 means I cannot find a way to bypass the welcome screens as it won't allow me past until I manage to connect it to the internet.
Please, any help at this point would be very much appreciated
Click to expand...
Click to collapse
Try some USB 3g/4g Dongle and insert it into micro USB , then you can connect to internet via 3g/4g and see if you can get past welcome screen.
...
I had similar problem "wifi just showing turning on forever" with a phone. But that had happened because I had accidently deleted the "insmod" binary from "/system/bin/" folder ( actually replaced it with the one that came with "precompiled busybox-1.21.1-armv7" from busybox.net.) So at that time my phone was not able to load the "Wifi module some .ko extension file") See if you are also having this problem.
asratxda said:
Try some USB 3g/4g Dongle and insert it into micro USB , then you can connect to internet via 3g/4g and see if you can get past welcome screen.
...
I had similar problem "wifi just showing turning on forever" with a phone. But that had happened because I had accidently deleted the "insmod" binary from "/system/bin/" folder ( actually replaced it with the one that came with "precompiled busybox-1.21.1-armv7" from busybox.net.) So at that time my phone was not able to load the "Wifi module some .ko extension file") See if you are also having this problem.
Click to expand...
Click to collapse
Thank you for your reply, my tegra is not set up for 3/4G as far as I know, wouldnt connecting a dongle require some app installation?
wifi stuck at "turning on" for months
Hi
My tablet turned off and on then would not connect to wifi it gets stuck at turning on amd i cannot press any buttons to turn it on.
I have reset. Put in airplane mode and finally factory reset so now it asks to connect at Welcome page but still shows turning on.
I have not rooted or am not technically savvy i just know the basics but i do not know what to do and cannot use my tablet at all!!
Please help!!
aimeymarie said:
Hi
My tablet turned off and on then would not connect to wifi it gets stuck at turning on amd i cannot press any buttons to turn it on.
I have reset. Put in airplane mode and finally factory reset so now it asks to connect at Welcome page but still shows turning on.
I have not rooted or am not technically savvy i just know the basics but i do not know what to do and cannot use my tablet at all!!
Please help!!
Click to expand...
Click to collapse
You are having one of the symptoms of a bad OTA update/Flash/etc.
I described my problem in detail here: http://forum.xda-developers.com/nvidia-tegra-note-7/help/help-tablet-stuck-fastboot-t2967999
Today I plan to work on it, I'll let you know if I get it going again with Wireless and what I had to do.

HTC Desire S Wifi problem

I need some help with my WiFi connection problems
HTC Desire S, S-ON, SuperSU, 4EXT Touch recovery.
i was on stock rom 2.3.5 until recently and it was working fine almost all the time.
flashed CM11 Android 4.4 based rom
after that cannot connect to Wifi - open or secured both
as soon as i touch the "Connect" option, the shown WiFi signal strength does down and it does not connect.
have tried deleting the Wifi settings folder inside data - using terminal
# rm -rf /data/misc/wifi && reboot
also tried the FXR wifi fixer app, but no luck.
any suggestions ?
in my stock rom, i used to get to enter the credential storage password to connect to secured Wifi - but no such option is shown here.
thinking this might be a rom problem, flashed a 4.2 based one, but still cannot connect.
even tried booting in safe mode, but same result.
say i am right next to the router and my phone can see the signal at full strength -
as soon as i touch the connect button, the signal goes way down, it does not connect, then the signal goes up to full again.
thanks a lot for any suggestions.

APN settings are not available for this user

When I set up my 6P a few hours ago, it asked me for my SIM pin (white symbol) but never actually connected to a network. Taking a look at my APN settings I get this weird message: "Access point settings are not available for this user." So I'm also not able to add a VPN manually.
I searched a lot and found some methods to try. Here's what I already did:
- Force stopped Phone and Messaging Storage
- Cleared Phone and Messaging Storage data
- Deleted /data/data/com.android.providers.telephony/databases
- Factory Reset
- Rolled back to 7.0.0 from 7.1.1 beta
Is there anything else I could try?
Thanks in advance!
i have the same problem
goog luck
I'm not intimately familiar, but I did see a couple of potential solutions:
Step 1 : WiFi turned on, and be in the range of a known WiFi network.
Step 2 : Reboot the phone (may need to reboot several times, if it doesn't work the first time)
Step 3 : When the phone reboots, it should connect to WiFi network.
Step 4 : Go to APN settings and see that you can, now edit APN settings.
Reason : When phone is turned on, if it's not connected to WiFi, it will try and connect to mobile network thus disabling you from editing APN settings. However if you try the above steps, your phone connects to WiFi instead of Mobile-data.
Click to expand...
Click to collapse
My original solution would be to flash the factory image. I've had some wonky behaviour in the past with the root issue being older radio operating on newer firmware. You can grab the latest image 8.1.0 (OPM7.181205.001, Dec 2018) directly from Google. Flashing instructions are at the top of the page, but boil down to:
Ensure you have necessary tools and drivers installed; reboot into bootloader (power on while holding VolDown key)
Run
Code:
fastboot flashing unlock
Unzip factory images, and execute the flash-all script corresponding to your system (.sh from Linux, .bat from Windows).
This will update the bootloader, radio, and firmware.

Dumpsys Working Over ADB But Not Via Terminal Emulator

I just flashed back to the factory image and rooted my device. Prior to wiping the device and flashing back to the factory image I was on a custom ROM. I had a tasker profile setup that would disable deep idle mode and light idle mode during the day and have it activate overnight. It worked really well on the custom ROM, but on the factory image I just get error messages. I have granted tasker root permissions as well and tried in terminal emulator with root permissions but still get error messages. Yet if I try the same command via adb shell over my PC it works perfect. Here is the command I am trying to run, any ideas why it would work on my PC but not on my device with root permissions granted?
dumpsys deviceidle disable (This will disable deep idle mode and light idle mode)
dumpsys deviceidle enable (This will enable deep idle mode and light idle mode)
Any suggestions would be greatly appreciated. Also thanks to @italia0101 for helping me with the commands and tasker profile, it was working great on the custom ROM.
Chochiwpg said:
I just flashed back to the factory image and rooted my device. Prior to wiping the device and flashing back to the factory image I was on a custom ROM. I had a tasker profile setup that would disable deep idle mode and light idle mode during the day and have it activate overnight. It worked really well on the custom ROM, but on the factory image I just get error messages. I have granted tasker root permissions as well and tried in terminal emulator with root permissions but still get error messages. Yet if I try the same command via adb shell over my PC it works perfect. Here is the command I am trying to run, any ideas why it would work on my PC but not on my device with root permissions granted?
dumpsys deviceidle disable (This will disable deep idle mode and light idle mode)
dumpsys deviceidle enable (This will enable deep idle mode and light idle mode)
Any suggestions would be greatly appreciated. Also thanks to @italia0101 for helping me with the commands and tasker profile, it was working great on the custom ROM.
Click to expand...
Click to collapse
Update:
I ended up flashing another custom ROM and now the shell command is working as expected. Not sure why it wasn't on the factoy image but it is now. Peace :good:
Same problem here, really driving me nuts

TB-X704F Factory restore gone wrong

I have used the rescue and smart recovery program to factory restore my TB-X704F but after using it my wifi and bluetooth will not work at all. Showing mac address not available.Any attempt to turn the wifi slider on just results in it turning off again straight away. Any solution to this?
EDIT: Fixed it by manually running all the commands in C:\ProgramData\LMSA\Download\RomFiles\TB_8704F_USR_S001018_1910091527_Q1241_ROW\8953_fastboot_all_images.bat including the ones prefixed by REM

Categories

Resources