Every time I start-up my phone (from cold), it goes online.
This is a pain since it connects via 3G and drains my battery unless I remember to disconnect it.
I've looked everywhere to find the app that is causing this behaviour and I've disabled everything I can find to try to prevent it.
Is there any way of checking what is causing this? I'm running Satin and Radio 1.48.
Try using a tweaker (like HTweakC) and disabling AutoAttach. Might work - never tried it, but mine connects too. Not sure what other unintended consequences it will have, but it is reversible. I imagine it may just prompt you before connecting.
Other possibility is active sync?
Not sure.
Go into comm manager and make sure 'Push email' isn't enabled.
One of the first things my phone does after a soft reset is connect to data.
I'm always connected to data, because I use 'Push'
But I also have 3g disabled and only use it when necassary.
I used to use BandSwitch to use GSM only, But Schap has that toggle built in.
There should also be a Band selection available in Phone Options.
If not, there's a reg fix for that.
Don't know if any of what I just posted helps. :-/
Berd
Let's make life less complicated and start a new thread for people to provide feedback on 2.6.39, ... 3.3, 3.4 (NEW) RHODIUM kernels. The source repository is here. Note, older trees are not under active development.
By the way, these kernels are developed jointly with jonpry, WisTilt2, and bzo. In addition a lot of code is shared with people that maintain active msm kernel branches (emwe, acl, Alex). Finally, all Xdandroid Kernel developers have in one way or another contributed code.
1. Feel free to use any of these kernels, however DO NOT submit a post in this thread that amounts to "This feature does not work for me." If you wish to submit a bug report, make sure you are proficient at using ADB, AND have installed GetLogs. In your post you should:
a. Include GetLogs output of the problem (or it didn't happen).
b. Include Rhodium model (100, 210, etc).
c. Try to reproduce the problem on the other kernels.
All other bug reports will likely not receive full attention.
2. These kernels are to be used with GBX0B.
3. These are auto-built at:
Auto Built Service generously provided by WisTilt2
The autobuild is down. Please use these links, they were the final kernel builds that were on the autobuild site.
2.6.39.3
3.0.18
3.3.8
3.4.3
4. What works:
This list should look very similar to the current status of .27 with your device. Meaning, if you have a rhodium on which the camera does not work with .27 (for example), camera will not work with these kernels as well. Please do not report issues that are present on .27+your device.
- Only 3.0 has BT support. Would appreciate some feedback on this. I get the impression that pairing/connecting takes a bit of patience, but I am interested in how this compares to BT in .27. If we get some positive feedback we can enable BT support across all three kernels.
5. How do these three kernels differ: They are maintained by the same group of people, and consequently differ very little. There are slight variations in power management code, but other than that they are hard to distinguish in terms of functionality.
6. Kexec: To hot-swap the kernels (boot with a new kernel without rebooting into WinMo):
a. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
b. Go to the shutdown menu in GB, and select "Kexec".
c. Phone will reboot within Android, using the new kernel.
7. Finally, I don't have too much time to hang around xda, so you shouldn't hope for "next-business day" response policy I am just hoping we can attract the advanced user to these kernels, that can do most of the troubleshooting on their own.
Enjoy, RHOD has to be one of only a handful of android devices that are pairing android with kernels as advanced as these.
This you should note:
I. If you are experiencing problems with turning Wi-Fi on, try the procedure outlined HERE before posting.
II. With regards to usb related functions and 3.4:
This kernel uses ICS style usb drivers and as a consequence, usb notifications in GBX no longer work. To work around this issue we wrote a little app XdaRndisToggler, which should allow you to turn on ADB, as well as USB Tethering (RNDIS).
Using this app is pretty self-explanatory:
0. Plug your phone in (No notification will appear in GBX).
1. Start the app.
2a. To start the ADB service, select "ADB only" and click apply. At this point you can use ADB to connect to the device.
2b. To start USB tethering, select "ADB+Rndis" and click apply. At this point go into Settings->Wireless->Tethering and check the box that says USB Tethering. The blue "USB Tethering" notification should appear in your taskbar and you should be all set to tether.
3. To stop using ADB and/or RNDIS, select "Disable USB" in the app and click Apply.
FOR ADVANCED USERS:
Alternatively, you can use ADB without the use of XdaRndisToggler (app is still needed for tethering), by making the following changes to init.cfg/init.gingerbread.rc (note, you will need to remount / as rw)
Code:
on property:persist.service.adb.enable=1
- start adbd
+ start adbd
+ write /sys/class/android_usb/android0/enable 0
+ write /sys/class/android_usb/android0/idVendor 0x0bb4
+ write /sys/class/android_usb/android0/idProduct 0x0c01
+ write /sys/class/android_usb/android0/functions adb
+ write /sys/class/android_usb/android0/enable 1
on property:persist.service.adb.enable=0
stop adbd
+ write /sys/class/android_usb/android0/enable 0
+ write /sys/class/android_usb/android0/bDeviceClass 0
Above, minus/plus is used to denote delete/add line respectively.
Downloads:
XdaRndisToggler 06/19
Ts-calibration is not working on the 3.0.9 kernel.
I can't see the [+]'s.
I was forced to use my own calibration file.
I am using the temporary 3.0 kernel and till now, I have faced a few problems:
1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.
2) On some random calls, the sound simply gets disappear and doesn't come. Normally this doesn't happen on every call (trust me, I called more than 7-8 phone no. for more than 1 hours today itself) but suddenly, but on one call, the sound just vanished and I couldn't hear anything from the caller on the other side. The problem remained there until I rebooted my phone.
apurohit said:
(I couldn't get the logs using Getlogs, don't know from where to pick it)
Click to expand...
Click to collapse
GetLogs
apurohit said:
1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.
Click to expand...
Click to collapse
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.
Are you using 3.0 for its bluetooth capability - if so, how's that working for you?
detule said:
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.
Are you using 3.0 for its bluetooth capability - if so, how's that working for you?
Click to expand...
Click to collapse
Well, I tried pairing bluetooth with my laptop and a bluetooth headset, it takes forever however my laptop and the headset is always visible in the available device list. I have used .39 (wifi wasn't an issue on it but calls were problem) and .27 (provided with the bundle where voice issue was constant) and then used 3.0 (temporary provided by you), I am facing this problem on all of them. I have RHOD100, CSVs are attached with this post.
Also, I already have getlog installed on this build (it was provided in the Android App folder) but still, I cannot figure-out where exactly it is saving the file. Since you have provided the Getlog thread hence I will read it through and will provide you the same.
Update: Have attached logs taken from Getlogs. Thanks for the guidance.
apurohit said:
Update: Have attached logs taken from Getlogs. Thanks for the guidance.
Click to expand...
Click to collapse
You instincts were right, it is proximity related. In the file you attached if you search for "proximity" you will see a few "proximity 0" and no "proximity 1" -> meaning the proximity sensor is always reporting "user is near" and consequently the screen stays off.
Here is a silly question, do you have a case on your device, one that might be obstructing the sensor?
detule said:
question, do you have a case on your device, one that might be obstructing the sensor?
Click to expand...
Click to collapse
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.
The screen comes back the moment I pull hardware keyboard but goes off if the call is on or I press power button (general practice to turn the screen on) and then it won't come even if I pull the keyboard.
I have one more question which may sound off topic but thought it's good to ask an expert rather suffering forever.
I am wondering which key should I use to disconnect the call since the end key doesn't work in this case and throw me back on the home screen.
apurohit said:
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.
Click to expand...
Click to collapse
Yes, GBX0B is the first time (apart from NAND) that proximity-related functionality has been enabled.
If you are seeing the same problem in WinMo then you may be facing a hardware failure of your proximity sensor. On the other hand it could be that RHOD100 is somehow special, and we don't have the correct gpio setup in the kernel to handle your device. I just heard from a RHOD110 user saying that everything is fine, so I might be leaning towards the former.
Unfortunately I don't know of any quick tweaks to disable the sensor in Android.
detule said:
If you are seeing the same problem in WinMo then you may be facing a hardware failure of your proximity sensor. On the other hand it could be that RHOD100 is somehow special, and we don't have the correct gpio setup in the kernel to handle your device. I just heard from a RHOD110 user saying that everything is fine, so I might be leaning towards the former.
Unfortunately I don't know of any quick tweaks to disable the sensor in Android.
Click to expand...
Click to collapse
I'm definitely leaning towards that myself. If it's busted in WinMo, chances of it working correctly in Android are slim-to-none.
detule said:
Unfortunately I don't know of any quick tweaks to disable the sensor in Android.
Click to expand...
Click to collapse
I understand, though I will wait for a resolution in near future
Still, thanks for sparing your time answering me
For whatever reason, the link to the autobuild is opening like this
http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/
Not sure why (I know how to get to the page, I'm just pointing this out)
JDog2pt0 said:
For whatever reason, the link to the autobuild is opening like this
http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/
Not sure why (I know how to get to the page, I'm just pointing this out)
Click to expand...
Click to collapse
Works fine here... FF9/Chrome16.
JDog2pt0 said:
For whatever reason, the link to the autobuild is opening like this
Click to expand...
Click to collapse
arrrghhh said:
Works fine here... FF9/Chrome16.
Click to expand...
Click to collapse
Thanks for the heads up i fixed it earlier today.
Now to legitimently post something...
3.1 does not funtion well on my RHOD500 GBX0B. Enabling wifi caused a soft reset that never seemed to clear up. 3.0 works alright. I will probably post the logs in a bit as I've switched to 3.0, however it is incredibly easy to replicate.
JDog2pt0 said:
Now to legitimently post something...
3.1 does not funtion well on my RHOD500 GBX0B. Enabling wifi caused a soft reset that never seemed to clear up. 3.0 works alright. I will probably post the logs in a bit as I've switched to 3.0, however it is incredibly easy to replicate.
Click to expand...
Click to collapse
Can't reproduce on RHOD400 with 3.1, wifi functions flawlessly for me. Since 400 and 500 are basically the same device, I would expect the same to be the case on your device as well.
This is where logs would have been useful.
Not sure what a "soft reset that never seemed to clear up" means. Reset to bootanimation? This is usually a user-land miscue.
detule said:
Can't reproduce on RHOD400 with 3.1, wifi functions flawlessly for me. Since 400 and 500 are basically the same device, I would expect the same to be the case on your device as well.
This is where logs would have been useful.
Not sure what a "soft reset that never seemed to clear up" means. Reset to bootanimation? This is usually a user-land miscue.
Click to expand...
Click to collapse
Decided to create a new post rather than edit the previous one. Anyways I'm not familier with "user-land miscue" so you'll have to explain that one to me, and yes it is a reset to boot animation. Upon manually reseting the device nothing on the homescreen loads and under wifi in settings it says "error"
data.txt contains only one intersting line that I could see.
Code:
E/WifiService( 1325): Failed to load Wi-Fi driver.
In logcat.txt the first line related to wifi is
Code:
I/ActivityManager( 1324): Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.WirelessSettings } from pid 1457
It's late and adb shell is giving trouble with the whole cat /proc/kmesg > dmesg.txt. The included terminal emulator crashes whenever I run it, I have little to no cell signal where I now live, and the Market refuses to work over wifi. I'll dig up an apk after I get some sleep.
JDog2pt0 said:
Decided to create a new post rather than edit the previous one. Anyways I'm not familier with "user-land miscue" so you'll have to explain that one to me, and yes it is a reset to boot animation.
Click to expand...
Click to collapse
Critical kernel errors (so called panics) end in a full blown reset to win-mo. When the device resets to bootanimation, this is Android (userland) freaking out for whatever reason.
JDog2pt0 said:
data.txt contains only one intersting line that I could see.
Code:
E/WifiService( 1325): Failed to load Wi-Fi driver.
Click to expand...
Click to collapse
Usually this is indicative of kernel/modules magic mismatch. Have you tried this http://forum.xda-developers.com/showpost.php?p=20887127&postcount=20 ? If that doesn't work, what kind of output do you get if you type
Code:
insmod /lib/modules/bcm4329.ko
JDog2pt0 said:
It's late and adb shell is giving trouble with the whole cat /proc/kmesg > I'll dig up an apk after I get some sleep.
Click to expand...
Click to collapse
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
...I feel like I am repeating myself.
detule said:
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
Use GetLogs.
...I feel like I am repeating myself.
Click to expand...
Click to collapse
You are, rather unecisarily too. How do you think I got data.txt?
Code:
rm -rf /lib/modules
Did not solve the issue. Phone still goes to boot animation. Not sure what to do next, not sure why it's happening considering we basically have the same phone.
This thread is going to be a work in progress, mainly because I'm at work right now and I can't spend the next several hours typing everything out.
I recently purchased a Epic 4G Touch last week and like many people, have been suffering from GPS fix issues. After some playing around today with my phone, I seem to have a possible solution. I'll be working on step-by-step instructions in the future. Do be aware that you WILL need your MSL for this.
For those familiar with QPST, there's a tab in SERVICE PROGRAMMING called gpsOne, which details the different GPS capabilities that are enabled. Since cellphones aren't using true GPS and are using A-GPS, one of the "assisted" capabilities are enabled, but there are additional capabilities that can be enabled. What you want to do is enable everything.
AFLT stands for Advanced Forward Link Trilateration. You can read about it here. You want to enable this along with GPS/AFLT Hybrid.
As far as I can tell, "Autonomous" will let your GPS function like true GPS without needing cell tower data downloaded to your phone. I imagine it'll take several minutes to obtain a lock like this, but I don't see what the harm is in enabling it.
In a rushed ending, I want to reiterate that you WILL need your MSL to do all this. You also need to turn off USB debugging and type in ##8778# and change AP to CP. Set that back to AP after you're done. You also need the debugging drivers installed. I promise I'll edit this post with more detailed instructions in the near future. For the moment, you should be able to follow the instructions in this post to accomplish the same thing.
Also, since doing this to my phone, I get a lock in about 10 to 20 seconds, or less.
BinaryMn said:
This thread is going to be a work in progress, mainly because I'm at work right now and I can't spend the next several hours typing everything out.
I recently purchased a Epic 4G Touch last week and like many people, have been suffering from GPS fix issues. After some playing around today with my phone, I seem to have a possible solution. I'll be working on step-by-step instructions in the future. Do be aware that you WILL need your MSL for this.
For those familiar with QPST, there's a tab in SERVICE PROGRAMMING called gpsOne, which details the different GPS capabilities that are enabled. Since cellphones aren't using true GPS and are using A-GPS, one of the "assisted" capabilities are enabled, but there are additional capabilities that can be enabled. What you want to do is enable everything.
AFLT stands for Advanced Forward Link Trilateration. You can read about it here. You want to enable this along with GPS/AFLT Hybrid.
As far as I can tell, "Autonomous" will let your GPS function like true GPS without needing cell tower data downloaded to your phone. I imagine it'll take several minutes to obtain a lock like this, but I don't see what the harm is in enabling it.
In a rushed ending, I want to reiterate that you WILL need your MSL to do all this. You also need to turn off USB debugging and type in ##8778# and change AP to CP. Set that back to AP after you're done. You also need the debugging drivers installed. I promise I'll edit this post with more detailed instructions in the near future. For the moment, you should be able to follow the instructions in this post to accomplish the same thing.
Also, since doing this to my phone, I get a lock in about 10 to 20 seconds, or less.
Click to expand...
Click to collapse
This doesn't seem to do anything for me, i enabled all the settings in the gpsOne Tab but when i enabled airplane mode the phone does not find any satellites when using GPS Test. i would like to just put it the way it was, what are the default settings for the Epic 4g Touch?
Jointedman said:
This doesn't seem to do anything for me, i enabled all the settings in the gpsOne Tab but when i enabled airplane mode the phone does not find any satellites when using GPS Test. i would like to just put it the way it was, what are the default settings for the Epic 4g Touch?
Click to expand...
Click to collapse
[HOW TO] Enable stand-alone/antonymous GPS on Epic 4G
I find the Epic GPS to work very well generally, especially in custom ROMs like CM7. That said it all falls apart whn trying to use the GPS in airplane mode or when overseas (or other areas with no CDMA cellular coverage). From what I can determine the Epic 4G was not configured properly to use the GPS chip in these circumstances.
To fix this issue you need to change the GPS settings on the actual gpsOne chip. This will allow the phone to get a GPS signal when in airplane mode and/or not within a CDMA service area. The procedure is time consuming and annoying but in may experience, worth it.
DISCLAMER – the below how-to could completely brick your phone. I have NO IDEA what I’m doing.
You will need to download some software to begin:
1. Qualcomm Product Support Tools (QPST) v.2.7.355 (or newer) – I don’t think I can post that link so Google it.
2. Epic 4G Windows USB drivers - http://www.samsung.com/us/support/ow...SPH-D700ZKASPR
3. MSL code – there are a number of ways of obtaining this so I will not duplicate here.
Step 1:
Obtain your MSL. If you can’t get this, you can’t complete this fix
Step 2:
Install the Epic 4G Windows USB drivers. Assuming you are rooted and or otherwise used ODIN you may already have these installed. Installing again will hurt nothing.
Step 3:
NOTE: So far as I can figure your phone needs to be in stock form to continue from this point on. I tried the rest of this while running CM7 – Nightly 13 and it would not work (particular issues seem to be dial codes and USB modem connectivity). Once finished with the fix you can then flash back to whatever ROM you would like. So…ODEN back to stock.
Open in the dialer and enter ##8778#. This will bring up the “PhoneUtil” menu. Set both UART and USB to MODEM and hit the home button.
Step 4:
Install Qualcomm Product Support Tools (QPST)
Step 5:
Insure that USB debugging is off. Connect the Epic 4G to your computer. The computer should make the usual USB connection noises and may begin installing drivers. Let that that finish.
Step 6:
Open QPST Configuration (installed when you installed QPST) and go the Ports tab, add a new port and select your port number. If nothing shows up uncheck the “show serial….blah blah” box and it will show your port number, select it and add it. You will now see your COM port with your phone connected. Close that.
Step 7:
Open client QPST Service Programming, select your active phone (might take a moment to come up), click "Read from phone" (enter MSL) and then scroll over to gpsOne and select all the options on the left hand side:
Assistance-Spherical
Assistance-Cartesian
AFLT
GPS Almanac
GPS Ephemeris
GPS Almanac Correction
Autonomous
GPS/AFLT Hybrid
……then click “Write to Phone.” When that’s done click “connection” and “close” and then close the program.
This may cause your phone to reboot…if not, reboot it.
Step 8:
Open in the dialer and enter ##8778#. This will bring up the “PhoneUtil” menu. Set UART to Modem (USB to PDA) and hit the home button….reboot again.
Step 9:
You should no be able to use the GPS while in airplane mode or (especially) after booting up in an area without CDMA coverage.
TIPS: If you should clear you AGPS settings for some reason (or they expire?) and you want to use the GPS anonymously without a CDMA or WiFi connection, you will need to reboot the phone first (and possibly disable “use wireless networks” in Location Settings until some new AGPS data is obtained). One way to obtain some AGPS data in absence of a CDMA network is to use an app like GPS Test to load some AGPS data back into the phone via WiFi. Also it may be possible to improve this by refining the gpsOne settings…but you would need to figure out what the hell they all mean.
This solution works for me.
Good luck
So I have been noticing a very specific series of steps, that are 100% of the time making me to restart my Mobile Data Connection to make it work again, here's what happens:
Open WhatsApp, make sure that you are on Mobile Data (3G/4G) and working fine.
Send a video (>1MB) to the WhatsApp Status on Mobile Data (3G/4G)
The video will start showing sending, but will take a very long time and fail.
Internet will stop working now, nothing would work.
Then go to *#*#4636#*#* menu and restart the Mobile radio power.
Internet starts working again.
This I have been doing since last one month, and has never failed me even once, the internet works fine before this with 10-20Mbps speed on 3G/4G, but as soon as I start sending a video on WhatsApp status, this happens everytime.
Any idea what's causing the issue and how to debug this?
rootSU said:
So I have been noticing a very specific series of steps, that are 100% of the time making me to restart my Mobile Data Connection to make it work again, here's what happens:
Open WhatsApp, make sure that you are on Mobile Data (3G/4G) and working fine.
Send a video (>1MB) to the WhatsApp Status on Mobile Data (3G/4G)
The video will start showing sending, but will take a very long time and fail.
Internet will stop working now, nothing would work.
Then go to *#*#4636#*#* menu and restart the Mobile radio power.
Internet starts working again.
This I have been doing since last one month, and has never failed me even once, the internet works fine before this with 10-20Mbps speed on 3G/4G, but as soon as I start sending a video on WhatsApp status, this happens everytime.
Any idea what's causing the issue and how to debug this?
Click to expand...
Click to collapse
With a user name of rootSU I would have figured you would have run the basics already but from this thread I guess not. Start with a logcat. That will tell you what is going one. Most likely its whatsapp bogging the connection down so bad that it needs a restart. I cant say for sure as whatsapp is not really used by many people in my country.
zelendel said:
With a user name of rootSU I would have figured you would have run the basics already but from this thread I guess not. Start with a logcat. That will tell you what is going one. Most likely its whatsapp bogging the connection down so bad that it needs a restart. I cant say for sure as whatsapp is not really used by many people in my country.
Click to expand...
Click to collapse
That's the first thing I did, but couldn't make much sense out of it.
I have taken the whole logcat dump again today in a file, but don't know what to look for actually in it.
Can upload the file here, but it contains too much of device information to be uploaded publically.
If you can make anything out of it, can send you the file in PM though.