Database Users

[Q] IWConfig and IWList usage to manipulate txpower

Currently looking at iwconfig, somehow the txpower is set to 32dbm (1492mW). Iwlist eth0 txpower lists available txpower levels below such a number. 0dbm and 25dbm (255mW). I'm guessing this 32dbm is nowhere near correct. How can we manipulate txpower? Its nice to have these commands working now! BTW the formula for dBm is P =30+10log(W). In this case, W=1.492, so dBm is actually 31.74. Not that it matters, I think that's way out of spec.

Blades said:
Currently looking at iwconfig, somehow the txpower is set to 32dbm (1492mW). Iwlist eth0 txpower lists available txpower levels below such a number. 0dbm and 25dbm (255mW). I'm guessing this 32dbm is nowhere near correct. How can we manipulate txpower? Its nice to have these commands working now! BTW the formula for dBm is P =30+10log(W). In this case, W=1.492, so dBm is actually 31.74. Not that it matters, I think that's way out of spec.
Click to expand...
Click to collapse
I don't think that may be accurate. I compiled iwlist and when I look for channels it gives a bunch of channel 0's, with very odd values, many far from the 2.4ghz range. I may have renamed the wrong wireless(number).h to wireless.h before compiling. I'm curious if you have this problem as well? How did you compile iwlist?

GPS Fix for Aussie Vibrant Owners (will work for other regions)

Hey all.
Just another GPS fix that seems to work really well. Being in Australia with a Vibrant, I have had allot of trouble with GSM Bands and GPS. Allot of the GPS fixes I tried did not work.
After some playing around, I came up with this. I now find 11 satellites within 5 seconds, and lock on to them within 5 seconds, compared to before, which was 1-4 satellites in 5 minutes.
The setting below are aimed for Australians, though can be changed to suit any region. Ru, USA, etc.
Please note this requires a tiny bit of adb work. So make sure to have the sdk-tools. You need to be rooted.
The process:
Open up notepad and copy the following lines.
NTP_SERVER=au.pool.ntp.org
XTRA_SERVER_1=1.au.pool.ntp.org
XTRA_SERVER_2=2.au.pool.ntp.org
XTRA_SERVER_3=3.au.pool.ntp.org
SUPL_HOST=supl.google.com
SUPL_PORT=7276
Save this file as gps.conf (take note on the filename, and make sure its not gps.conf.txt)
Place this file on the root of your sdcard.
Open a CMD Prompt and change to the sdk-tools. Then type
adb shell
su
cat /sdcard/gps.conf > /system/etc/gps.conf
reboot
After the reboot, goto phone dialer and use one of the two numbers below.
For Eclair 2.1 Users - *#*#1472365#*#*
For Froyo 2.2 Users - *#*#3214789650#*#*
In Application settings, change Operation Mode from Standalone to MS Based.
In SUPL/CP Settings, change the server & port to supl.google.com and port 7276.
Reboot again.
After the reboot head back to the GPS menu via the above dialer codes.
Press Delete GPS Data, then press Get Position Test. Go outside and place the phone down, and let it sit for about 3-5 minutes. It should have found at least 10 satellites.
After that, exit the GPS menu, and everything should be done. Test by using the app GPS Test.
For use in other regions head over to http://www.pool.ntp.org/ and find your zone information, or a simple Google of pool.ntp "your region" should give you the direct link.
Cheers
Dave

Interesting.
Checked my phone and it's about 9 seconds off.
Found this app which looks like it could be helpful.
http://www.appbrain.com/app/clocksync/ru.org.amip.ClockSync
Thanks for finding this issue.
Edit: Did a bit more research and now I'm skeptical that what you found is significant regarding GPS performance. Here are some forum posts discussing phone time and GPS time:
http://code.google.com/p/android/issues/detail?id=5485
I'm not doubting that you saw a difference, however, you also changed some settings other than just the time sync server. We've seen many reports over the last months by users who changed something that appeared to make a big improvement in GPS lock time or accuracy only to see the differences disappear within a few days. I'll be interested to see if your observed improvement persists. It would also be interesting to know if you set all your GPS settings back to default whether the time sync server change makes any difference.

Have you tried this:
http://forum.xda-developers.com/showthread.php?t=878970
It is the top sticky in the General section for a reason.

[app] HsdpaKeepalive v0.1

Have made a app that keeps your hsdpa alive while u tether on your phone.
Target ip is hardcoded(google dns)
You have possibility to change packet size and ping delay that suits your needs.
Remember to make a excemption on juice defender for this program, if u want to use ping while screen off ability.
Originaly i made this app for my personal needs since i didnt find similar one from market, any feedback on bugs or features is very much appreciated.
edit: Upcoming features which i plan to add: 1. Wifi detection, stops pinging when u have wifi on. 2. Automatic packet/delay calculation for hsdpa to keep on.
hsdpa keepalive v0.1

Signal Switch For Better Data $peed$ AT&T G3 d850

Ok people, after scrolling from forum to forum looking for a way to edit my build.prop for better data performance I've come to a couple of conclusions........The main one is that the majority of people end up bricking their phones. Either from being noobs or even a developer simply forgetting to change permissions. The other is that pretty much ALL of the lines people say to edit or even add just simply do not work. I'm posting a method I found in a forum,I can't remember which one but it's the one I use and have found to be the most helpful in getting a better signal.
You must be rooted!!!
First download an app from the play store called #SHORTCUT MASTER#
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
This app let's you access the G3's hidden hidden menu. You can scroll into numerous hidden folders and files. Some I wouldn't mess with!!! Open the app and go to the settings within the app. Click on "Secret Code Explorer". Scroll down until you see this folder below..........
""""33233323 com.lge.hiddenmenu .ErrFatalErrFatalBroadcastReciever""""" CLICK ON THIS!!!!
Scroll down until you pass a couple "Rat_Selection" folders. I believe you want the third but incase I have placed some screenshots below to help out. Rat_Selection let's you instantly switch from 2G, 3G, 4G, LTE depending on your coverage area. Not sure about which coverage area you are in? Here's another useful app that allows you to check ALL CARRIERS COVERAGE AND ALL NETWORK SPEEDS to help you get some Info about what speed you should switch to if any.
Download "Open Signal" from the play store.
https://play.google.com/store/apps/details?id=com.staircase3.opensignal
Again check the screenshots if you don't believe me. This app is extremely useful!!! Ok so go ahead and finaggle with these two apps and see if it helps any of you and post some feedback. Good or Bad. Last but not least if you just want to edit your build.prop for whatever reasons here are a few lines I have added to mine just to see if they would help and as of right now I'm not sure if they helped but adding these lines did not brick my phone. Changed permissions rebooted and everything seems fine. As I said I'm not sure if they work but obviously doesn't hurt anything. As of now
ro.ril.gprsclass=34 ---- gprs (edge) speed settings
ro.ril.hsdpa.category=28 ---- HSPA+ Download speed settings by category. Cat 28 is the highest
ro.ril.hsupa.category=7 ---- HSPA+ Upload speed settings by category. Cat 9 is highest, 7 seems to work just fine tho
ro.ril.hsxpa=5 ---- setting to enable hspa+ for the upload and download
#Better signal.
persist.cust.tel.eons=1
PS........
I know I said that changing or adding certain lines don't seem to work but I think "hypothetically" that if you switch to say,3G that maybe adding these lines could help with the DN and UP SPEEDS?? Not sure but just saying
FYI I'm not taking credit for anything just sharing what I've learned. These are not my own edits but found on different forums. If this is a repeat post just go ahead and delete. If this helps anyone please hit the thanks button, if not then please feel free to leave constructive criticism or just plain out bash me......

huge amount of AudioFlinger messages in logcat

I'm a new user, not allowed to post in development forum. So forgive me for posting here. This is in response to the "[ROM][AOSP][hermes] Delirium Sense7 thread. This ROM produces 80KB in logcat every second, which is the repetition of the same message:
Code:
D/AudioALSACaptureDataProviderNormal( 263): readThread, latency_in_us,0.000119,0.000299,0.001681
D/AudioFlinger_Threads( 263): need 54274 frames in to produce 18091 out given in/out ratio of 3
D/AudioFlinger_Threads( 263): not enough to resample: have 1025 frames in but need 54274 in to produce 18091 out given in/out ratio of 3
D/AudioFlinger_Threads( 263): now need 1024 frames in to produce 341 out given out/in ratio of 0.3333
D/AudioFlinger_Threads( 263): success 2: have 1025 frames in and need 1024 in to produce 341 out given in/out ratio of 3
V/AudioTrackShared( 263): mAvailToClient=0 stepCount=341 minimum=342
D/AudioFlinger_Threads( 263): need 53251 frames in to produce 17750 out given in/out ratio of 3
D/AudioFlinger_Threads( 263): not enough to resample: have 2 frames in but need 53251 in to produce 17750 out given in/out ratio of 3
The messages hint a problem in audio re-sampling, but since the mobile phone produces this messages without any audio sounded, it's either misbehaving or a secret recorder has been running. Anyway, is this an ignorable problem? Perhaps the ROM set debug level too high (I'm new to android dev). I currently filter out these messages in order to work on my other projects.

Eventually I am switching away because of the following bugs.
- usually my SPI client (nonoh) produce noise while dialing
- Google Map freezes, mostly when I am on the move (GPS location change)
- Tethering doesn't work - the other wifi clients connects, gets IP address but can't surf.
Hope the next ROM to try is better.

FWIW, this is due to "Google Now" detection being set to "From any screen". Turn that off, and these will go away (but if it's only when charging and screen on, it might not be that big of a deal).