Develop Bugs

[COMPLETED] New more stable ril

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?)

[MOD] LoSD - LoS Repair Daemon v1.3.1 [Updated 2012-08-08]

NOTE:
If you came here looking to fix recent problems with LoS in recent builds of Jelly Bean, be aware that this utility has not been tested with JB or ICS at this time. I figured LoS was a solved problem, so retired the project. I'm looking into it again, and may have something out later depending on how much has changed in the OS updates.
Introduction
Has your phone ever had a circle with a line through it instead of signal bars? Has your phone ever shown signal bars, but all calls and texts fail until you reboot? Well, those situations are called Loss of Service, or LoS, and while we can't actually stop them from happening yet, those situations can be detected and repaired. The Loss of Service Daemon (LoSD) does that, so you don't have to!
It does this by:
Restarting problematic radio daemons when detected.
Rebooting when all attempts to fix have failed.
In addition, it can create a log dump of various system logs for debugging purposes.
Requirements
Phone must be rooted.
An init.d compatible kernel.
Busybox must be installed.
Many ROMs and custom kernels do this automatically, but check the feature of your basic tool-chain before installing.
Installation
All files are located in my github projuct, if you'd like to get a closer look at how all LoSD works. But what you really want to to know:
Download LoSD
This will be a file you can flash using ClockWorkMod. Simply copy it to your internal or external SD card, reboot into recovery, and flash. The next reboot will be running LoSD.
NOTE : Installing LoSD will automatically remove -viperboy-'s LoSChecker, as they should not both run at the same time.
Download LoSD Uninstall
The above package will fully remove all traces of LoSD from your phone. Flash if you're having problems or no longer need/want LoSD.
WARNING! Do not wipe anything before or after install of this utility! It is not a ROM. You will be left with an unbootable system.
Usage
If you installed the flashable zip, your phone will automatically launch the LoS daemon at every boot.
Or you can call it manually to obtain debugging logs!
Code:
LoSD dump
When called with the 'dump' command, LoSD will dump all debugging logs and exit, creating a timestamped directory in LOGPATH (/data/local/LoSD by default), as well as a tar archive named logs.tar.gz. This lets you capture situations where LoSD did not detect a LoS, and send the logs for analysis.
Frequently Asked Questions
These are taken from the README file that gets installed with LoSD. There's more dev-related info in that file, so give it a look!
Q: Will this restart the radio or the phone if I lose 4G?
No. 4G is actually a separate radio from the CDMA radio used for texts and phone calls. This script ignores the 4G radio entirely and can not trigger no matter what happens to the 4G radio.
Q: Will this restart the radio or the phone if I'm using WiFi?
No. Turning on WiFi *will* disable your 3G data, but will leave the CDMA radio in an available state so you can still receive phone calls and texts. The LoS daemon knows the difference, so feel free to use your WiFi as you please. LoSD may restart your radio while you're on WiFi, but only because your CDMA radio stopped responding and you wouldn't have received any texts or phone calls if it didn't try and fix the radio.
Q: Where do I find the logs?
Logs produced when the radio is restarted, or the phone is rebooted, are stored by default in /data/local/LoSD in a directory time and date stamped for when the fix was attempted, or a reboot was triggered.
Q: Help! My log directory is getting huge!
By default, LoSD will not dump system logs when it repairs a LoS. But you may have enabled it on your own if you modified the configuration file. If you're in a spotty coverage area, the log directory may start to fill with several timestamped log dumps, each of which are around 5MB. If you'd like to stop this, please ensure your LoSD.ini configuration file does not contain the following line:
Code:
DUMPLOGS=1
Such a line will enable log dumping, which again, is disabled by default!
Q: I think I have LoS the daemon didn't detect. How do I get logs?
Very easily! LoSD has a built-in logging command! Just type this into a terminal, or an 'adb shell':
Code:
su
LoSD dump
This will create a timestamped directory just like LoSD had detected it. In addition, a file named logs.tar.gz will be dropped in your LOGPATH directory (that's /data/local/LoSD by default) you can send to us. We recommend putting it in dropbox, or some other binary-file hosting site.
Credits
Many thanks to -viperboy- for the original concept of checking for LoS with a script.
HaiKaiDo gave us the idea of restarting the radio daemon before rebooting.
If I'm forgetting anyone, please PM me!

Configuration
There are several settings you can apply to the LoS daemon while it's working. These settings should be placed in a file named LoSD.ini in the /data/local/LoSD directory of your phone. If you change any settings, you must either restart the daemon, or reboot your phone.
Currently recognized settings:
DEBUG
Many log entries are only informative in nature and can be very noisy. If you are having trouble and want to see LoSD activity reported in the system logs and LoSD.log, set this to 1. Default is 0.
DUMPLOGS
Whether or not logs should be dumped during a LoS repair or system reboot. Should be 0 for false, or 1 for true. Default is curently 0.
LOGPATH
Full path to where logs should be dumped. This is also where LoSD keeps its own LoSD.log file. Default is /data/local/LoSD because the daemon knows that directory exists. Feel free to place it somewhere on your SD card. If this directory does not exist, LoSD will attempt to create it for you. Please make sure the path is writable!
RESTARTS
How may times should the daemon attempt to restart the radio before giving up and initiating a system reboot. Default is 2. This setting was primarily defined because ghost LoS can sometimes degrade into full LoS, and subsequent radio restarts may be necessary to regain service.
RESTART_LIMIT
How many successful radio restarts before LoSD considers the phone state tainted? Too many RILD restarts may damage other services, or cause other unknown side effects. After this limit is reached, further LoS events will not result in an RILD restart, but a full reboot. Default is 3.
SLEEP
How long to wait between radio checks, in seconds. Default is two minutes.
Example:
Code:
LOGPATH=/sdcard/los
RESTART_LIMIT=1
Again, if these settings are changed, you must either restart the LoS daemon, or restart the phone. To restart the daemon, execute the following in an ADB shell or terminal:
Code:
su
killall LoSD
nohup LoSD &
The 'nohup' is there to prevent the command from attaching to your TTY, so you can disconnect without your session hanging. Feel free to omit this if you were just going to close your TTY.

Change Log
Version 1.3.1
Added third Airplane mode check for ICS firmwares.
Third firmware check also works on phones with disabled logcat.
Version 1.3.0
Improved CDMA connection FAILED detection.
Added second Airplane mode check for EL13, EL26, EL29 firmwares.
Version 1.2.0
Added debug log level.
Moved several informative messages to debugging only.
Debugging is now disabled by default.
Tweaked RILJ error detection for RIL_REQUEST_CDMA_GET_SYSTEMPROPERTIES.
Can now ignore false positive ghost LoS caused by phone calls.
Phone call and Airplane mode now checked before anything else.
CONNECTING status no longer skips LoS check.
Added ghost LoS check for CDMA 'Unknown data error' messages.
Version 1.0.0
Log dumping is now disabled by default.
Now uses 'setprop ctl.stop/ctl.start' to try restarting RILD nicely.
Does a quick check to prevent multiple running copies.
Added a radio restart limit to avoid glitchy post-fix systems.
Clear radio log in case of false positive ghost LoS.
Version 0.9.0
Added non-LoS check for transient CONNECTING status.
Now check for ghost LoS *after* standard LoS.
Calling LoSD with 'dump' now dumps and tarballs all debugging logs.
Version 0.8.1
Fixed bug in grabbing bugreport dump.
Now removes -viperboy-'s LoSChecker on install.
Removed LoSD logcat dump in favor of persistent LoSD.log.
Version 0.8.0
Now maintains a separate log for tracking all LoS events.
Added DEBUG configuration setting.
Version 0.7.1
Fixed typo in AirplaneMode check. Should no longer reboot in airplane mode.
Version 0.7.0
Fixed bug in radio log dump.
Now tries multiple times to restart RILD before reboot.
Added DUMPLOG as boolean to disable / enable log dumps
Added RESTARTS as number of RILD restart attempts before reboot.
SLEEP, LOGPATH, DUMPLOG, and RESTARTS are now user configurable.
Now searches for /data/local/LoSD/LoSD.ini for config settings.
Version 0.6.0
Initial public release

Good deal, the more people working on this the better and I know viperboy had a lot of work going. I'll give your version a go today.
Sent from my SPH-D710 using xda premium

Just_s said:
Good deal, the more people working on this the better and I know viperboy had a lot of work going. I'll give your version a go today.
Click to expand...
Click to collapse
Haha. Thanks. The way I see it, Viper has his hands full with way more important projects right now. With his ROM, the EK02 pull, the ICS work... why should he have to worry about this too? He was going to rewrite his script anyway, so I just took the opportunity to do it while he was distracted being useful.
While I was at it, I just... added a few things. That's all.

installing now.. thanks for this, and thanks viper

How about an option that appends to a file a date and time that the los happened instead of the full log? How about a notification after it fixed a los? The viper script made the phone appear like I never have los. Good but I still would like to know how often it happens.

gedster314 said:
How about an option that appends to a file a date and time that the los happened instead of the full log? How about a notification after it fixed a los? The viper script made the phone appear like I never have los. Good but I still would like to know how often it happens.
Click to expand...
Click to collapse
I can do the feature to keep a running tally of LoS, but so far as I can tell, there's no way to send notices from the command line. If there is, I can't find it. Sorry.
Sent from my SPH-D710 using xda premium

Question... Do I need to be uninstalling this script everytime I update, or just flash over the old? -Grand
Sent from my SPH-D710 using XDA App

grandmastem said:
Question... Do I need to be uninstalling this script everytime I update, or just flash over the old? -Grand
Click to expand...
Click to collapse
Just flash it over the old one. I've made the install smart enough to install over previous versions of LoSD. If you're running -viperboy-'s LoSChecker, you should run his uninstall first, though.
Also:
Edited OP to reflect new 0.8.0 version. Added a setting to suppress the Info-level log messages. Now it also keeps a LoSD.log in the LOGPATH directory so you can keep a log of its activity between reboots without having the log dumping enabled.
I also updated the Configuration and Change Log sections.

After u install it wat u do to run it or do it run on its own
Sent from my SPH-D710 using xda premium

pats4life100 said:
After u install it wat u do to run it or do it run on its own
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It runs on its own.
Is this JarJar Binks?
Sent from my SPH-D710 using xda premium

Just_s said:
It runs on its own.
Is this JarJar Binks?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1 sir.....+1.......
Also thanks for the shoutout trifthen! Nice work

Giving this a go. I'll report in with anything that seems odd. I definitely get LoS on occasion, and the girlfriend doesn't approve haha.

trifthen said:
I can do the feature to keep a running tally of LoS, but so far as I can tell, there's no way to send notices from the command line. If there is, I can't find it. Sorry.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Trifthen, I'm glad you took this over cause I had alot of other stuff going on. If I see any enhancments, I will send them your way. Also, you have my permission to include the line in your updater-script to remove my LoSChecker because I don't want it to affect users who use yours and don't uninstall mine. Just add this into your updater-script:
Code:
delete("/system/bin/LoSChecker");
And you can also add a line to remove my logs as well if you want. The files might be taking up a good bit of space...
Code:
delete_recursive("/data/local/LoS");
Those should be right, I'm at work so I'm typing from memory
For counting when LoS happens, you could just write a timestamp or something else into a file (>> adds into a file, > overwrites any data in a file) and then just do a wc on it (-l option reads lines, I think) which would give you the number of times that you had LoS from reading the amount of lines in the file. Just a thought.

Yay no more this ****
Sent from my SPH-D710 using xda premium

-viperboy- said:
Trifthen, I'm glad you took this over cause I had alot of other stuff going on. If I see any enhancments, I will send them your way. Also, you have my permission to include the line in your updater-script to remove my LoSChecker because I don't want it to affect users who use yours and don't uninstall mine. Just add this into your updater-script:
Code:
delete("/system/bin/LoSChecker");
Code:
delete_recursive("/data/local/LoS");
Click to expand...
Click to collapse
Thanks man. I'll do that. I'll be waiting in anticipation for those enhancements. I actually just got a reboot following a ghost LoS where I couldn't send any texts. It couldn't restart the radio, and boom. The best enhancement we could get is to have no need for this utility. Heh.
... and then just do a wc on it (-l option reads lines, I think) which would give you the number of times that you had LoS from reading the amount of lines in the file. Just a thought.
Click to expand...
Click to collapse
Yep. The new /data/local/LoSD/LoSD.log is basically everything it sends to the system log, so it's like a mirror that persists after reboots, unlike the system logs. In addition, you can turn off those pesky "Radio appears normal - no LoS." information messages by setting DEBUG=0 in the config file.
I just found a cut-n-paste bug in the line that dumps the bugreport, so I may just add the lines that remove LoSChecker along with that fix.
Thanks again, Viper!

Is anyone else running a hacked PRL and running into issues like I am?
EDIT: Rebooted manually, held up at splash screen, weird series of beeps and now back up....running Blazer v.12 on EG31.

DizDroid said:
Is anyone else running a hacked PRL and running into issues like I am?
Click to expand...
Click to collapse
Well, if your hacked PRL is the 000000 one that puts you permanently on Verizon, that might be an issue. I noticed the phone killed my radio about 6 times today around the same 20-minute period while I was right on the edge of Sprint service and kept roaming on and off. I was standing in line for lunch in a building that's not nearly as tall or as deep as where I work, yet it was driving my radio nuts. LoSD's ghost LoS checks triggered multiple times, so I have plenty of logs to work with now so I can revise the check to be a little less overzealous.
I can't say for sure, but forcing yourself to roam may have a similar effect. Take it with a grain of salt.

trifthen said:
Well, if your hacked PRL is the 000000 one that puts you permanently on Verizon, that might be an issue. I noticed the phone killed my radio about 6 times today around the same 20-minute period while I was right on the edge of Sprint service and kept roaming on and off. I was standing in line for lunch in a building that's not nearly as tall or as deep as where I work, yet it was driving my radio nuts. LoSD's ghost LoS checks triggered multiple times, so I have plenty of logs to work with now so I can revise the check to be a little less overzealous.
I can't say for sure, but forcing yourself to roam may have a similar effect. Take it with a grain of salt.
Click to expand...
Click to collapse
Thanks for the reply, keep up the great work. If I wasn't trying so hard to get out of my Sprint contract I'd ditch the .000000000000000000000000000 in a heartbeat.

[Q] Help ? Xperia ARC+DarkKernel+LX : Wifi almost working, only sees the gateway

Hi,
This is my first post, on this great forum, so I'm posting as a "noob"...
So my problem :
- I installed the LegacyXperia 20130908 CM10.1 release. It was working almost OK
- But because of the high wifi drain, I gave the lated DarkKernel a try (http://forum.xda-developers.com/showthread.php?t=2451839)
It seems to perform very good BUT I just noticed something really weird : I have access to the internet through my wifi LAN, I can ping my gateway BUT nothing else works on the local LAN :
ping fails :
[email protected]:/ $ ping -c 1 192.168.1.13
PING 192.168.1.13 (192.168.1.13) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=1 Destination Host Unreachable
The arp table seems incomplete :
1|[email protected]:/ $ arp -a
d810.home (192.168.1.13) at <incomplete> on wlan0
livebox.home (192.168.1.1) at 00:1f:95:26:25:4d [ether] on wlan0
The routes seem ok, the ip neighbours are not :
[email protected]:/ $ ip route show
default via 192.168.1.1 dev wlan0
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.10
192.168.1.1 dev wlan0 scope link
[email protected]:/ $ ip neighbor show
192.168.1.13 dev wlan0 FAILED
192.168.1.1 dev wlan0 lladdr 00:1f:95:26:25:4d STALE
AH, on more weird thing, the kernel arp table has lots of zeroes for the unreachable devices MAC adresses (yes, I have 192.168.1.13 and 1.15 are up and running) :
[email protected]:/ $ cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.1 0x1 0x2 00:1f:95:26:25:4d * wlan0
192.168.1.15 0x1 0x0 00:00:00:00:00:00 * wlan0
And I can't seem to be able to communicate with the local LAN only with the android phone...
I have static IPs in my DSL router, I can't set the arp tables manually.
I *think* this was all working with the default ROM kernel, but before I attempt to revert back to that kernel to check (I backed up the modules, but yet another noob thing, I'm not sure putting back the tar into /lib/modules will be enough...) :
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Since it's my first post (only 9 remaining now !), I can't post in dev section...
Thanks && regards

Did you flash the DarkModules?

Hi,
Yes i did flash them in cwm...

fschaer said:
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Click to expand...
Click to collapse
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155

Someguyfromhell said:
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155
Click to expand...
Click to collapse
Hi,
Thanks for the reminder.
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
and it appeared after i flashed this new kernel which seems better for the battery.
I think this is a kernel/wifi modules issue, not a rom one.
Or a noob error, but then i hope some of you can help me understand my error
As i said, wifi is somehow working since i'm replying just now using it...
It's just that apart from the dhcp/gateway, my device seems unable to learn any mac address with this kernel.
I haven't tried a tcpdump for now, and i wanted to test ipv6 but my 'great' dsl/wifi box does not support v6 - yes, that still exists...
Regards

fschaer said:
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
Click to expand...
Click to collapse
He is also developing the kernel together with his team, which is given within the .zip file.

Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers

fschaer said:
Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers
Click to expand...
Click to collapse
Which DNS server are you using? Did you change anything else by WiFi?
The captcha is only for limited amount of posts, then it will disappear.

I did not change any dns setting, but i saw local names in the terminal, so i must be using my dhcp/box dns.
You remind me i unchecked the wifi optomizations with the new kernel: i read this was causing arp issues on nexus devices...
Lets try to re-enable that... appart from this, i changed nothing after i flashed this kernel.
Except I tried 1.8ghz (it worked well), but this disappeared sincei restored the official rom krtnel
Thats really all i changed since i tried the new kernel yesterday evening

Can you believe this...
- Restoring the wifi optimisations did not help
- rebooting the DSL box helped. For 5 minutes.
I was able to ping a computer on the network, but not to go to the dsl box webserver. and I lost internet.
- subsequent dsl box reboots did not solve anything : no internet, no webserver, no connexion even on the wired PCs , powerd them on or off, nothing.
- *unplugging* everything + dsl box reboot => did restore internet+wifi on the arc
- replugging the PCs did not break
- and I can now see/ping the LAN with the arc s
Only remains, now, the dlink switch I have downtstairs that is the only stuff that remained plugged all time (theres a device on it, but it's off)..... It must have switched to a "netkill" state somehow. Funny, isn't it ?
let's now start wireshark, reinstall the new kernel, and see if there is any difference... and lastly reboot/replug the dlink switch
the come back for the (arp) ping of death ?
Regards

Last experiments:
- fired wireshark, to capture any network suspicious paquets
- reflashed the new kernel+modules
- retried ping / local LAN
Still working.
I rebooted my last network device (dlink switch), repluggued it : everything is still working.
conclusion : I don't understand :laugh:
Cheers

[Q] Another 4.3 Wifi Tether TrevE problem thread

I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.

Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.

Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.

atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.

bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??

Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.

I'm running synergy 4.3 rom and native hotspot works no problem. .

I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.

[Q] Wifi Not Working On Cyanogenmod 11 - T989

I was able to install CM11. Flashed cm11 on 12/7 and everything has been working great. I was able to update everything. On next morning, wifi signal was there but no access to internet. Wifi is on but it picks up no wifi signals. If I turn on/ off wifi doesn't find anything else. And receive WPS has failed error... if I click in refresh.
I have already daily upgrade nightly builds to up to date build (20131217), but success. same issue. Any idea?
If I do a full wipe and then restore a backup it work for a day, then stops again.

I have the same problem. I dropped the phone on the wooden floor, and thought the wifi just broke, but now I'm confident it's because of bugs in cm11
Considering returning to cm10.3
LE:
Installed BeanStalk with no data/cache wipe and WiFi is still not working.

gust989 said:
I was able to install CM11. Flashed cm11 on 12/7 and everything has been working great. I was able to update everything. On next morning, wifi signal was there but no access to internet. Wifi is on but it picks up no wifi signals. If I turn on/ off wifi doesn't find anything else. And receive WPS has failed error... if I click in refresh.
I have already daily upgrade nightly builds to up to date build (20131217), but success. same issue. Any idea?
If I do a full wipe and then restore a backup it work for a day, then stops again.
Click to expand...
Click to collapse
I updated mine to 1/14/2014 CM11 Nightly and still no Wifi. Anyone have the same experience?

I had the same problem. You can try wiping all data, reinstalling ROM and gapps. Everything but the camcorder works!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

it solved !!!! ...
Hi to all
I had this problem and i could fix it.
afret install CM 11, go to this address : settings/wi-fi/advanced/wi-fi region code
and change it to fix. for me it works on Europe.
I hope it be useful.
If it works for you, give me Thanks ...

Will try as we speak. Thanks for sharing.
---------- Post added at 08:55 PM ---------- Previous post was at 08:13 PM ----------
I just upgraded to cm 11 build .17 and Wifi just doesnt turn on.
It says turning on... and just hangs.
I've set region to Europe to no avail..

I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 0. Reboot and then you should have wifi working again.

value
adrscu said:
I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 0. Reboot and then you should have wifi working again.
Click to expand...
Click to collapse
Thanks, that worked great. but the setting reverted back to "1" on its own , i changed it back to "0" working again but any idea how to keep it from reverting back?
The value only reverted the one time, hasn't been an issue again.

Samsung Galaxy S Advance - Cyanogenmod 11 wifi connection problem
adrscu said:
I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 0. Reboot and then you should have wifi working again.
Click to expand...
Click to collapse
Downloaded SQlite debugger. Cannot find Setting Storage. Please help.

adrscu said:
I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 1. Reboot and then you should have wifi working again.
Click to expand...
Click to collapse
This totally worked for me. But it stops, and the problem is back again. Checking the settings.db shows it has returned to 0. (wtf!)
Not sure what to do at this point. It's nice to know it's not hardware.

thanks!
i had the same problem. this guide solved my problem. thanks.

Fixed my network problem by removing ad-hoc network
Hey,
I had a problem when I tried to connect to an ad-hoc network I'd setup. The network settings screen would freeze up on me and then..... nothing. I checked the database settings by adb'ing onto my phone (a rooted oppo find 5 by the way). I checked the values of the settings database as described by others. That didn't work so then went to the file containing connection details of known wifi networks
Code:
sudo ./adb shell
[email protected]:/ $ su
1|[email protected]:/ # cd /data/misc/
[email protected]:/data/misc/wifi # ll
First I start a shell on my phone (sudo ./adb shell), then I change from a regular user into the superuser (su) then I go to the directory containing the wifi connection info.
There I opened the file wpa_supplicant.conf and removed the ad-hoc connection that caused my problems. I've also read about people simply removing the file. Downside of that is that you will loose your painstakingly acquired history of known passwords (but I guess in the end that is still better then not having a wifi connection at all....)
Hope this helps somebody
Cheers!

Hi
I have installed cyanogenmod 12 beta 10 on my galaxy s2 i9100
there is no country code option in wifi advance setting.
how can I get my wifi worked?

Rydermuff said:
Thanks, that worked great. but the setting reverted back to "1" on its own , i changed it back to "0" working again but any idea how to keep it from reverting back?
The value only reverted the one time, hasn't been an issue again.
Click to expand...
Click to collapse
May I ask for a absolute path of "settngs.db" file, please? By the way, have you fixed the issue with reverting?
Thank you.

SAHRSOFT said:
Hi to all
I had this problem and i could fix it.
afret install CM 11, go to this address : settings/wi-fi/advanced/wi-fi region code
and change it to fix. for me it works on Europe.
I hope it be useful.
If it works for you, give me Thanks ...
Click to expand...
Click to collapse
Hi Sahrsoft, where are these options on CM 12 (lollipop)? Thanks!!

Hi guys,
Just wanted to tell you that setting wifi_display_on to 0 didn't work for me. Full reset did the trick on my GS4 GT-i9505

adrscu said:
I found a solution. Download SQlite debugger from Play Store. Open the app, then open Setting Storage, then setttings.db, then Global, then scroll down to wifi_display_on and edit the value, change it to 0. Reboot and then you should have wifi working again.
Click to expand...
Click to collapse
Thanks so much dude! I was so close to resetting my phone and this worked perfectly! To those of you who got lost on this I'll try to describe it better... Download SQlite debugger from Play Store or on your PC then transfer the apk to your phone and install Open the app, then press 'App' and scroll down to 'Setting Storage', then 'setttings.db', then 'global', then 'name', now scroll down to 'wifi_display_on' and edit the value to 0, make sure you commit this change by pressing the arrow icon in the top right and accepting. Now reboot and turn on your WIFI!

SAHRSOFT said:
Hi to all
I had this problem and i could fix it.
afret install CM 11, go to this address : settings/wi-fi/advanced/wi-fi region code
and change it to fix. for me it works on Europe.
I hope it be useful.
If it works for you, give me Thanks ...
Click to expand...
Click to collapse
thank you !