Help My wifi won't even try to connect. It will turn on and i can see my router but when i click connect nothing happens. It worked when i got the phone, i used toast's root then flashed to OMJ EVO 2.1 Eclair v1.3. Didn't work tried flashing with Supersonic_1.32.651.1 and still nothing. then i tried wiping the data and delvic cache and restore with the original backup i made and i still got nothin any ideas
did you flash the most up to date radio?
I was having this problem too, it may be different. My power control would show with the green bar like it was waiting for IP but would not go the bright green indicating it was connedted. If I did it from wireless and Networks it would show "unable to connect" you can find my solution here: http://forum.xda-developers.com/showthread.php?t=699752
I recommend trying this first:
In connect bot on phone, navigate to with
# cd /data/misc/wifi/
then do
# chmod 777 wpa_suplicant.conf
now try to connect from the Wireless and networks in the settings menu. If you can you probably need to do what I did to set it.
Just one question first though, Did you try rebooting the phone? Simple things some times.
Thank you for the input. i've updated radio to 1.39.00.05.31 still does not work. Then i tried changing permissions on the file you recommended...still no luck.
When i go into wireless & networks Wi-Fi will have a disconnected below it. when i go into wi-fi settings i see my home network with "not in range,remembered" under it. After about 3 secs. it changes to "remembered,secured with wep". i'll select it and push connect and nothing happens, it doesn't even appear to be trying to connect.
i noticed something today. Previously when i tried changing those file permissions i simply did exactly what you had said. Did some looking around and the /data/ folder is empty. I did finf the file in /etc/wifi/ directory.
Decided this should have a thread of its own instead of hiding in another thread.
I originally stumbled onto this thanks to cyryl's post where I found that disabling 3G helped prevent a lot of the Sleep of Deaths (SoDs) I was seeing. (Phone was sleeping with solid green LED, then suddenly switches to orange LED and is totally hung.) That led to the discovery that the Vogue sources (which XDAndroid is derived from) had a bunch of newer fixes to their RIL library that were never pulled into XDAndroid.
I set up a clone of the XDAndroid and Vogue repos and merged them all in here:
http://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/androidhtc1
I also fixed several bugs that weren't fixed in either of the previous source trees as well (mostly memory leaks). The result was working well on my phone, but since then I've gone on to fix additional bugs, making this RIL behave almost identically to the native HTC RIL running on my G1 phone.
I used to get SoDs within about 10 minutes of booting up if I had 3G enabled. Now my phone has lasted 24 hours at a stretch without any crashes. The binary is attached here if anyone else wants to try it out. Instructions courtesy of Entropy512.
Entropy512 said:
To test this fix (should work with any Froyo 2.2.2 based builds):
Unzip the attached zip file
Place libhtcgeneric-ril.so somewhere on your SD card. For organization, I use bindfiles/lib/libhtcgeneric-ril.so
Open conf/froyo.user.conf in your favorite text editor
Within the custom_shells{} section of froyo.user.conf, add:
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
On Gingerbread it would be
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /system/lib/libhtcgeneric-ril.so
Click to expand...
Click to collapse
If you run into problems, get a log taken when the problem occurred and attach it with your post describing the problem!
Problem reports without accompanying logs are useless and a waste of time.
You will always need the output from "logcat -v time -b radio". Sometimes you will also need the output from "logcat -v time" (simultaneous with the first). If you don't know how to obtain these, then please STOP NOW and don't proceed any further with this.
There is an alternate set of files in post #6 for use with a patched rootfs. See that post for the details.
The ril in this post is no longer being updated. Use the alternate ril in post #6 to get the latest bug fixes.
Using CDMA Mode
Documenting this here for my future reference, don't do this unless you're actively involved in helping me debug:
To switch into CDMA mode with your current install
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
update secure set value='4' where name='preferred_network_mode';
.quit
Reboot for it to take effect.
Alternatively you can blow away your data.img and edit /system/build.prop and set ro.telephony.default_network = 4 before booting. (Earlier versions of this post said to use 6 for the mode. That was a mistake, 4 is the correct value.)
The original value was 0, so you can switch back to that if you need to.
You will also need to edit a property file to add your network info anyway. You must add e.g.
Code:
ro.cdma.home.operator.alpha = Sprint
ro.cdma.home.operator.numeric = 310120
Replace "Sprint" and "310120" with the correct name and ID number (MCC/MNC) for your mobile network. If you don't get the operator ID right some features will not work properly (roaming display, international dialing...). The easiest way to do this is just to create a file /data/local.prop and put these settings there. I believe the operator ID for Verizon is 310012 but haven't verified this. A complete list of operator IDs can be found on Wikipedia.
If you run into problems we need "logcat -v time -b radio" starting from as soon as possible in the boot to catch all the gory details. Also a regular "logcat -v time" running at the same time.
In fake GSM mode the phone always used a hardcoded operator ID of 310995, and the APN for that ID was used for mobile data settings. In CDMA mode the phone sees the actual operator ID, so you'll need to add an appropriate APN to match that ID. See http://cleanimport.xda/index.php?threads/1023116/.
Thanks for creating a separate testing thread for this - it needed it, and I was going to suggest it if you hadn't already made this thread .
I have tested this on my CDMA RHOD400.
Seems to work well - unfortunately I'm not a good test case, as I very rarely, if ever, get SoD's.
I do know that 30s sleep issue seems resolved - I made several calls, ran it overnight, and it still sleeps quickly with WisTilt2's test kernel. Now we need him to commit his code, get your code tested a little more and commit yours... Holy cow batman, our port is lookin great!
I use Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Here is my log http://forum.xda-developers.com/showpost.php?p=12403347&postcount=22
Borrow to use once:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
New init version
This is an alternate version of the ril which uses /system/bin/pppd instead of /bin/pppd. In order for it to work, you also must change some files in the rootfs. The new files are attached here in rootnew.zip. Here are the instructions for installing from a root command shell, assuming the zip file is in /sdcard/rootnew.zip:
Code:
# cd /
# mount -o remount,rw /
# rm -rf .git
# mv init.android init.android.BAK
# unzip /sdcard/rootnew.zip
# chmod 755 init.android init.etc/ppp/ip-*-*
# mount -o remount,ro /
Reboot after installing. You only need to do this once on a given rootfs. If you switch to a different rootfs you will need to do it again.
The advantage of using this approach is that the /system/bin/pppd doesn't ever try to write to /etc/ppp (so there is less opportunity for filesystem corruption when things go wrong) and the ril will not interfere with Android VPN use. Also this approach is required for NAND installs. I expect that this approach will be the default in the next FRX/GBX releases, but so far the changes haven't been merged yet.
This ril is no longer functionally the same as the ril in the first post. The code is in the initpppd branch of my git repo.
https://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/initpppd
Update: Everything in my initpppd branch has been merged into the main xdandroid repo. All of my fixes will be in the next official xdandroid builds, there's no longer any need to use my personal repo.
You can safely install the rootnew files regardless of which ril you use. But the ril in this post requires these files; it will not work without them.
Note: the init script in this rootnew archive is a patched version based on the xdandroid git repo. If you're running on F22's rootfs, you don't need this archive. Instead, you can grab F22's rootfs image with my patches already applied.
Also note: the ril attached here is no longer equivalent in functionality to the one in the original post. This ril no longer has fake GSM support; if you're using a CDMA phone see below. This ril also no longer uses any options in the startup.txt file. If you had force_cdma or north_am_dialing in your startup.txt file they are now ignored. If you set your operator name and ID correctly in build.prop then the dialing is automatically handled by Android.
Also this ril supports dynamic mode switching for world phones. If you have a rhod400/rhod500 and use both GSM and CDMA you can switch back and forth on demand. Currently the menu for this is buried inside the *#*#INFO#*#* menu.
[size="+2"]New CDMA support[/size]
This version now switches into CDMA mode automatically; you no longer need to set the default_network property or muck with sqlite3. If you have a rhod400/rhod500 and no SIM card installed, your phone will use CDMA by default. If you have a SIM card installed, it will default to GSM and you'll have to switch to CDMA yourself. If you're using my updated Phone.apk (a new version of that as well, not yet uploaded) then the World Phone menu will be enabled automatically and you can use that to select the mode. Otherwise just use the *#*#INFO#*#* phone menu.
You will still need to set your APN for MMS to work, and you'll probably still need to install an eri.xml file. And you still need to set your operator ID properties.
Note: if you try to switch modes on the current GBX image, the Phone app will crash. It's a bug in Google's code, not the RIL. I've written a fix for this and the fix is in the XDAndroid repos, so it will work fine in the next GBX release. Froyo is fine either way.
muziling said:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
Click to expand...
Click to collapse
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
highlandsun said:
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
Click to expand...
Click to collapse
Okay, so just to clarify, this shouldn't work for CDMA at this point? Arrrghhh is on CDMA, it seemed to work for him?
highlandsun said:
OK. Definitely it will fail with Gingerbread. I'm only testing with Froyo so far.
Click to expand...
Click to collapse
Also, just to clarify, this shouldn't work on Gingerbread at all at this point (and not just setting the network to 6 will fail)? I have it mounted in Gingerbread under the lib/froyo directory, since there is no /lib/gingerbread directory, and everything seems to be normal so far but I'm not sure how to tell if it's actually being used and I haven't called the network 6 command yet.
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6 4).
OK, here's the current status before I leave for the weekend:
Currently the ril code sets a radio status of "SIM not ready" when the radio power is first turned on. The CDMA phone sees this and says "wtf, it's trying to use a GSM SIM card" so it kills itself to start the GSM phone code again.
So we need to be able to obtain the current operating mode in the ril so we can see, if we're trying to startup with network mode 6, it should use some other radio status code instead of the SIM-related codes.
Anyone who wants to dig into it and think about how to do that, please do...
highlandsun said:
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6).
Click to expand...
Click to collapse
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
pdawg17 said:
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
Click to expand...
Click to collapse
It's only working well for GSM. Sounds like you should pass it by for now.
Request - for those of us following your source tree, when you upload a binary can you post which git revision that binary was built from?
Thanks
Started running this last night when you posted it in the other thread. I'm GSM only (Rhod210) so I can't help with CDMA, but I've been the victim of what are probably RIL related bugs. In areas with bad signal and when switching between EDGE/GPRS/UMTS networks I've experienced a bug where the "phone" part of the phone starts going haywire. The first symptom is that the phone no longer responds to incoming calls. From that point on, I can receive one text message after which point I can no longer send or receive text messages nor can I make or receive calls. Switchiung to airplane mode doesn't fix the issue and a reboot is required.
I'm hoping you've accidentally fixed this bug too.
highlandsun said:
It's only working well for GSM. Sounds like you should pass it by for now.
Click to expand...
Click to collapse
Confirmed. Works well on my Tilt2. It seems that data speeds are better as well. Can't say for sure but will keep testing. Great work!!
For the less educated amongst everyone, what chance is there of making a quick kernel zImage for us to try out?
I can't use anything after Feb 28th or I get a home screen lock.
The RIL is not a kernel module (.ko), but a loadable library (.so). This is why you need to use the mount command in froyo.conf.
-- Starfox
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Okay, found the conf file. Making the changes now! Must've been a late night. lol
problem still, logs below
6d5b27e_6.zip is network mode 6 's log, com.android.phone keep FC.
6d5b27e_0.zip is network mode 0 's log, when 3G enable, phone in, who call me will listen hang up audio ,and I can not accept and reject this call in my phone.
Raa_1 said:
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Click to expand...
Click to collapse
That's odd - what build are you running, and how was it installed?
I know the conf file was included with the FRX05 full ZIP bundle (or was it the FRX04 bundle?)
OK, several folks have reported Wi-Fi issues with LK8 so I'm making a thread for that.
Please document your problems here so I can help troubleshoot. Logcats are a BIG help when it comes to this.
Thanks!
I have wifi issue on any lk8 rom. I am fine with ljc to lk8 as long as i stay on ljc based rom. When i flash any lk8 rom I get wifi failed to connect or ocasionally it says connected but no traffic. I have tried dirty install on lk8 rom and clean install of lk8 rom several times same result. I go back to ljc and do the chameleon fix and all good.
cajun9924 said:
I have wifi issue on any lk8 rom. I am fine with ljc to lk8 as long as i stay on ljc based rom. When i flash any lk8 rom I get wifi failed to connect or ocasionally it says connected but no traffic. I have tried dirty install on lk8 rom and clean install of lk8 rom several times same result. I go back to ljc and do the chameleon fix and all good.
Click to expand...
Click to collapse
Can you share your Wi-Fi settings?
Don't need the SSID or PW, need to know what security you're running mainly.
I'm on WPA2-PSK and having no issues on LK8.
Most JB builds seem to have problems with WEP, especially if using a second layer security...
I have tried all the different wifi security settings and also no security still nothing. Spent a whole night trouble shooting wifi. Tried changing ip to static still nothing. At times it will show connected but no internet. No problems at all on ljc rom. Other android phone and notebook connect just fine.
cajun9924 said:
I have tried all the different wifi security settings and also no security still nothing. Spent a whole night trouble shooting wifi. Tried changing ip to static still nothing. At times it will show connected but no internet. No problems at all on ljc rom. Other android phone and notebook connect just fine.
Click to expand...
Click to collapse
What settings do the router have set up? (Or do you not have access to it?)
Perhaps the easier way is to do this in ADB from LJC:
Code:
$ su
# cp /data/misc/wifi/wpa_supplicant.conf /sdcard/
This makes a new file in you USB memory called wpa_supplicant.conf - it's the raw wi-fi settings.
Then copy/paste the contents here removing any SSID or PW.
If you can do for LK8 as well then we can probably see if there's a configuration change there.
If you'd rather you can PM this info to me as well.
Last thing to do would be a logcat.
First, turn off Wi-Fi in LK8 and clear the log:
Code:
$ su
# logcat -c
Then turn on wi-fi, let it fail. Let's dump the log now:
Code:
$ su
# logcat -d > /sdcard/logdump.txt
(Doesn't need to be logdump.txt, can be whatever)
Note: You can skip su step if you keep ADB open, only need to do once.
Then .ZIP and attach or put up on pastebin/dropbox/etc and post or send me a link.
Happy to troubleshoot it as much as possible!
Final possible step - wipe the wi-fi information out.
Turn off wifi first before doing this:
Code:
$ su
# rm /data/misc/wifi/wpa_supplicant.conf
...and see if it will pick up and just let you fill in the missing parts.
Hope this helps!
So... I stared into the abyss, but I came back from the brink - unlocked bootloader, and the modem/calibration stuff got wiped during what should have been a routine TWRP flash from fastboot, and left me with no radios whatsoever. After flashing S048, and applying all the known OTAs up till S251, I got my wifi & bluetooth radios back, but it didn't seem to recognise my SIM (tried both slots).
After trying for almost a week, I also finally got the diagnostics mode going and was able to put a working QCN backup in place (thank you XDA and uploader).
So I flashed the LineageOS 15.1 20180413, and lo and behold, it sees the SIM and asks for a PIN to unlock it. So far, so good. Then (first time) Android says 'switching to mobile data, might take a while' but nothing really happens (I am on wireless; if I turn off wifi that doesn't make any difference though).
Under 'Network', 'Automatically select network' is enabled but 'Network' (right below) is greyed out. When I untick 'Automatically select network', it says 'Error while searching for networks'. When I re-tick it again, it says 'Registered on network', although nothing really happens.
Under SIM cards, it says slot 1 is populated, but says 'Mobile Vikings is disabled' (Mobile Vikings being my provider). The button to enable it is greyed out. Switching to airplane mode doesn't force anything either.
I've had a logcat instance open when toggling 'Automatically select network', but nothing related seems to show up. Any hints on what I could try/check? Or is this a coaster?
I believe that once you erase the modem stuff you'll always have serious problems restoring it. It seems like most people have to send the device in for service.
I've still no solution for an old P2 of mine and in that case I even had a TWRP backup.
Lenovo should really allow for us to flash stock images . An unlocked bootloader with LESS privileges makes no sense.
Wipe everything in twrp & flash twrp full backup which included efs & modem shared on our p2 forum. then flash Fastboot s48 only systemchuncks 0-14, boot & recovery then do 4-5 OTAs updates till latest one s251, you'll get you mobile network & calls back.
@eried1 Yeah looks like it
@amansehdav I have turned the P2 subforum upside down and I already tried this - restore a working S233 TWRP backup, flash S048 through fastboot, and upgrade with the OTAs till S251. No dice. Wifi and Bluetooth came back with that process, but the stock firmware would not see the SIM.