I have been using CloudyG2 2.2 for over a year with no problems. Unfortunately, I filled up my list of Bluetooth devices (thanks La Guardia) which exposes a KitKat bug where Bluetooth connections are then dropped frequently. I reflashed Cloudy G2.2 again to fix this and went along my way. Unfortunately, I just noticed that when I create a wifi hotspot and connect to it, the other device (usually a Chromebook, though I've tried a few things), can connect to the access point but has no internet connection. Pinging Google does not have a response.
Using SQLite Editor, I have set the following:
settings.db -> global -> tether_dun_required = 0
settings.db -> settings -> tether_entitlement_check_state = 0
I feel like this has probably been beaten to death, but the forum search for this specific forum isn't working. Those above settings seem to have worked across the board on other phones, and if memory serves I used to have to set the tether_dun_required record before I reflashed. Is it possible AT&T has recently changed something on their side? Is there anything else I can check to debug this? I am on AT&T and my plan includes tethering.
Phone model: LG-D800
Android version: 4.4.2
Kernel version: 3.4.102
Build number: KOT49I
Software version: CloudyG2 2.2
Related
Hi Everybody,
I have an anoying problem: I can't get wifi tethering to work. Read millions of posts on XDA but still no results. I love android on my freaky winmo!
This is my status:
Running XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
Settings -> Wireless -> Wifi -> switch on = OK
Settings -> Wireless -> Tethering -> Wifi Hotspot -> switch on = NOK.
It simply says 'error' and it also switches my Wifi off. After this switching on Wifi also fails and giving me the same message: error.
(PS all the menu's are in my native language and I just translated them directly to english. Haven't figured out yet how to switch everything to english)
I tried different kernels (and modules). The last one I tried:
zImage-2.6.27.46-01250-g8f8207c
modules-2.6.27.46-01250-g8f8207c.tar.gz
Remember I read something about wifi and Radio ROM on the phone, but I have not HardSPL-ed it yet. Is there a minimum Radio version required?
Anyway, Hope somebody can help me a bit. I am desperate .
Kind regards,
Mo
Hi,
since a week or so my u8800 suffers from a huge battery drain.
Today i just got 10hours out of it and almost did nothing. (4min. phone call/ 10messages/ max. 10min surfing)
The last 10% of battery was gone in 30 seconds.
It all started last week when my phone was on stock 2.2. Then i updated to the latest stock 2.3.5, but still the same problem.
Model number : u8800
Android version : 2.3.5
base band version : 404020
Kernel version : 2.6.35.7-perf [email protected]#1
Build number : U8800V100R001C00B528G001
I also wanted to calibrate the battery, but i can't root the phone. Tried every program out there
Anyone got the same problem or has a solution ?
Hello Kawadude,
I use superoneklick and it works fine to root the device. Hier ist the how to, what you must do before use superonklick:
- Dial * # * # 2846579 # * # *
- Go to projectmenu, background settings, log settings, log switch and set Log on
- Reboot phone
- Set USB debugging on
- Run superonklick http://depositfiles.com/files/n0dcxce3t or http://shortfuse.org/
Hope it helps
Already tried that without a result.
I also tried DooMLoRD v4, Unlock Root and One-click Root.
Since i installed the official 2.3.5 i can't root my device annymore. On stock 2.2 this wasn't a problem.
Hello, do you keep wi fi enabled at all times? i noticed my battery drains increased greatly when i leave my wifi on 24/7
No, wifi is only enabled when I'm at home.
A couple of weeks ago the battery life was just fine. (With the same usage)
Kawadude said:
No, wifi is only enabled when I'm at home.
A couple of weeks ago the battery life was just fine. (With the same usage)
Click to expand...
Click to collapse
Close any application in your pc that might try to connect with an android device (like huawei's or Asus PC Sync, etc). Those applications use the adb driver and block superoneclick. Check if windows recognize your device and install it properly. Hum... That's all I can think of... ;-)
Igory0k said:
1.Settings-> Applications -> Developer Tools-on
2.Unknown sources -> Settings-> Applications -> Unknown sources-on.
3.Fast boot -> Settings-> Applications-off
4.Dial: *#*#2846579#*#*
5. Go to projectmenu > background settings > log settings > log switch > set Log on
6.log setting-dump & log-on
7.Reboot Phone
Download B528_ROOT
8. Run B528_root.bat
9. Your phone should now be Rooted.
10. You can now go back *#*#2846579#*#* and turn logging off if you want.
Click to expand...
Click to collapse
Try this. I did hear that this last release from huawei (B528) couldn't be/was really hard to get rooted. I haven't tried this, just found it. Credit to @Igory0k.
MtG92 said:
Try this. I did hear that this last release from huawei (B528) couldn't be/was really hard to get rooted. I haven't tried this, just found it. Credit to @Igory0k.
Click to expand...
Click to collapse
Didn't work for me.
The phone rebooted and freezed at the huawei logo.
The only thing i didn't find is step 6: "6.log setting-dump & log-on"
Kawadude said:
Didn't work for me.
The phone rebooted and freezed at the huawei logo.
The only thing i didn't find is step 6: "6.log setting-dump & log-on"
Click to expand...
Click to collapse
You have to do it, rooting apps need that option
And launcher apps etc. don't install them, your battery won't drain Uninstall unnecessary apps too
Moved To Q&A
Please post all questions in the Q&A section
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
sylvisj said:
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
Click to expand...
Click to collapse
Have you tried removing the .cid.info file ?
Using a terminal app type the following:
Code:
su
rm /data/.cid.info
On some ROM's have have to do this after every time I have rebooted the phone, not quite sure why but it works for me.
TrallaP said:
Have you tried removing the .cid.info file ?
Using a terminal app type the following:
Code:
su
rm /data/.cid.info
On some ROM's have have to do this after every time I have rebooted the phone, not quite sure why but it works for me.
Click to expand...
Click to collapse
Hello,
Thanks for the suggestion. I fired up Terminal Emulator, su'd, and it doesn't look like there is a .cid.info in /data/. There is a .psm.info, though, and .npswifi_stream - I don't know if they're related at all.
sylvisj said:
Hello,
Thanks for the suggestion. I fired up Terminal Emulator, su'd, and it doesn't look like there is a .cid.info in /data/. There is a .psm.info, though, and .npswifi_stream - I don't know if they're related at all.
Click to expand...
Click to collapse
Here's the 'ls -a' output for /data:
Code:
[email protected]:/data # ls -a
.container_1
.container_2
.container_3
.layout_version
.mtp_stream
.npswifi_stream
.pcsync_stream
.psm.info
.socket_stream
.ssh
anr
app
app-asec
app-lib
app-private
audio
backup
bcmnfc
bluetooth
cam_socket0
cam_socket1
container
dalvik-cache
data
dontpanic
drm
fota
hostapd
local
log
lost+found
media
misc
nfc
property
qcks
radio
resource-cache
security
shared
ssh
system
time
tombstones
user
wiper
wpstiles
Bump.
I have the same problem......
ninne1 said:
I have the same problem......
Click to expand...
Click to collapse
Bump again.
i think it's missing IMEI and EFS. Try this http://forum.xda-developers.com/showthread.php?t=1264021
r47z said:
i think it's missing IMEI and EFS. Try this http://forum.xda-developers.com/showthread.php?t=1264021
Click to expand...
Click to collapse
I dunno about EFS, but I know the IMEI is already correct - *#06* is showing the same IMEI as the label on the back of my phone.
My phone is work well after flashing CM, but no WIFI.
No /data/.cid.info file!
*#06# - show IMEI.
Did we ever get to the bottom of this?
Im having exactly the same problem, so bump. Its been like that for 6 months, my workaround so far was getting a bigger data subscribtion since 4g is working fine
sylvisj said:
Hello,
To start off, I have a USCellular S4 w/ CM10.1, currently the 7/9 nightly. I am running baseband version R970VXUAMDL and have not modified the kernel.
I am unable to enable WiFi at all on CM10.1 and haven't been able to since initially flashing CM10.1.
Under the Settings menu, I am unable to enable WiFi - it's greyed out.
Under the WiFi menu, I can enable the toggle but it does nothing.
Under the Advanced menu, MAC address shows 'unavailable' and the Wi-Fi region code is set to 'Europe' and will not remember changes.
Click to expand...
Click to collapse
Hi sylvis,
I realize that this is an old post. However. perhaps this thread will help someone else:
I flashed a Samsung Galaxy S4 (T-mobile SGH-M919) to CyanogenMod (CM11) this weekend. It worked ok for a couple days. The owner then said that they can't get any WI-FI. I found your post here and read with optimism that I might be able to fix this problem. Our problem was exactly "word for word" the same problem as you described in your original post. (Well almost exactly; we couldn't get "USA" to stick as the region code)
Before flashing the phone, I did install Philz ClockworkMod and did do a backup of the OEM ROM before flashing to CM11. That said, I found that I did not have to go down the road of restoring a missing IMEI file (as other threaders here describe). Here's what worked for me:
I dialed *#06# on the phone to see if there was an IMEI number present, and there was. I wrote down that number. So I decide to see if that number matched the printed number on the phone, that we can find under the battery.
Before I do a power off of the phone, I recall that I had turned OFF both Bluetooth and Mobile Networks. WI-FI was still turned ON, but in it's non-functional "greyed out" state like you and I both experienced.
Now I power off the phone, take off the back cover, and take out the battery to have a look at the printed IMEI number. Yes, it does march the number that I saw via *#06#.
I had to get up to do something, then returned a couple minutes later. I popped in the battery and restarted the phone. To my utter surprise, WI-FI was back up! In "Advanced" I now see the MAC address and the region is locked on USA
I turn on Mobile Networks, and WI-FI's still working. Being the fool that I am, I have to test this further. So I power off the phone again and just let it sit there for a couple minutes. I power back on and there is still JOY. Problem resolved and happy customer.
In closing: I don't think that the removal and reinsertion of the battery was the total solution, because the owner had already tried that. However, the owner did not let the phone sit with the battery removed for very long. They just popped it out, waited a couple seconds, then popped it back in. I think the total solution was having WI-FI enabled, Bluetooth and Mobile disabled, then doing a power off, with an extended wait time before reinserting the battery.
Hope that helps.
Regards,
Brcobrem
This is stackexchange issue I raised on this issue :
<a href="http://android.stackexchange.com/questions/171241/wifi-hotspot-timeout-setting-gone-in-nougat-7-0-7-1-but-timeout-has-not">
Wifi HotSpot timeout setting gone in Nougat 7.0 , 7.1, but timeout has not</a>; .
(answered only by myself).
I have observed, on receipt of my new AGM A8 QualComm 410 MSM8916 Android 7.0 phone , that the Wifi-HotSpot keeps timing out
after 2-5 mins . I am trying to connect my Linux 4.10 x86_64 host, using its iwlwifi driver, and wpa_supplicant + ISC dhclient, and it
does connect fine, for 2-3 minutes, but then the android phone (default DHCP router) stops responding to ping requests, and the
link is dead , until I bring the device down on the linux host & kill & respawn wpa_supplicant & dhclient . The script I use to do this
is attached. One weird thing is that even though the Android device stops responding to pings, it may still be passing pings through
to the WAN internet , so my script has to trying pinging an actual internet address like www.kernel.org (one of the few public IP
addresses left that respond to ICMP).
This is really nasty of Android Nougat, especially as the previous Android version I used on my old phone (4.2.2)
had a Wifi-HotSpot Timeout Options Settings dialog , which let you specify inactivity timeouts .
So I had to develop this complicated workaround where my 'network' init.d script does
PID_FILE=/run/wlan_ping_monitor.pid daemon /etc/init.d/wlan_ping_monitor.sh
which keeps the link alive.
I really need to root this phone, so I can install my own /etc/hosts file / ISC BIND9, fix this issue in /etc/default.hostapd.conf settings,
and maybe try to fix hostapd , & be able to view logs .
Any advice on how to create a custom recovery for this phone ? latest TWRP & CyanogenModROMs do not support it.
It looks similar to the WileyFox Swift , for which there is a lineageos 14.1 build . Should I try this ?
I am focusing on trying to build android & android_bootable_recovery and android_rooting_tools gitweb gits, & then build AOSP
& TWRP & a recovery ROM - any advice gratefully received.
This is linux kernel bug : https://bugzilla.kernel.org/show_bug.cgi?id=194931
and stackexchange issue: http://android.stackexchange.com/qu...ng-gone-in-nougat-7-0-7-1-but-timeout-has-not
The kernel could be responding better to the empty data frame sent by Nougat hostapd on ap_max_inactivity=300 timeout.
Also wpa_supplicant should be detecting the link has gone dead & re-initializing .
Hi guys,
the trouble began when switching my AP from 2.4 GHz wifi to 5 GHz.
After some time in which everything worked well, it would just suddenly bloody stop working.
It started like this: random disconnect from the wifi, reconnect and then just stopped working (no ssids visible).
Normally I could restart and the problem was gone, but now it is persistent even throughout reboots and I therefore have to use the mobile network (which is really expensive where I live).
I'm using Lineage OS 16, but the problem was also there when I used previous releases iirc which is why I changed the phone for some time.
What I tried:
* flash different firmware versions
* upgrade /system LOS
* restart
* set interface down/up
* delete entry for my SSID and create it again
Right now nothing works.
Maybe someone has knowledge about the internals of the wifi on this SoC.
How is the general design?
E.g. I saw that the kernel loads some files (wcnss.mdt, wcnss.bXX) that are inside the NON-HLOS.bin disk image.
I assume that the trustzone does something with it?
Very weird architecture to get wifi going and debug it.
What are things that I can try?
Does the driver / firmware / android store data that might lead to a different state after reboot and this behavior being persistent?
Who else had this kind of problem?
I also opened an issue at the LineageOS bugtracker where I pasted some excerpts of dmesg / logcat and bit more details https: //gitlab.com/ LineageOS/issues/android/issues/1323 (not allowed to post URLs).
Right now I'm not sure what it is, could be firmware (and therefore not LOS related, which right now I think is more likely) or e.g. kernel or who knows, maybe even hardware?
Thanks!