Database Develop

[Q] Spontaneous restarting on particular WPA Enterprise network

Hi,
I've been having a problem where my phone is restarting itself intermittently while I use the wireless network at my school (Purdue). I've tried both WPA and WPA2 (the school provides networks for both) and seen problems with both. The networks are the "enterprise 802.1x" version which requests a username and password to connect. I sometimes have to try a few times to get it to connect to WiFi (it sometimes takes a minute or two after I first turn on "Wi-Fi". Then, every few hours, the phone reboots itself: I'm in the middle of doing something (can be anything) or the phone is idle in my pocket and then the AT&T boot screen appears. I assume that there is some sort of kernel panic or something else that causes the hardware to reset itself.
I'm fairly sure that this issue only happens in a specific building on campus, so perhaps there is a misconfigured access point here. Even so, this is still a bad problem and could have security implications (perhaps a malformed packet is causing some buffer to overflow).
My phone is a non-rooted, stock AT&T Captivate with the JH7 firmware
I've tried talking to Samsung, but they want me to send the phone to them so that they can "repair it". I've swapped out the phone at the store where I got it for a new unit and the new unit (with new battery) also has this same problem.
The 802.11g at my house works flawlessly.
Ideas?
Assuming that this is a kernel-panic issue, how would I extract a stacktrace or other debug information? Do kernel panics cause the phone to restart itself? Have the 802.11 drivers been updated in newer kernels (what's the chance that a custom firmware based Froyo would solve this issue?)
(disclosure: This question was posted on samsungcaptivateforum last month without any
productive responses. I'm a new user here, so I cannot link to that post yet....)

pigrew said:
Hi,
I've been having a problem...
Click to expand...
Click to collapse
Thats weird because my phone has no problems like that and I have connected to many WPA networks. I don't know the source of the problem but my suggestion would be try a custom rom before sending to samsung because it can't hurt. If it doesn't work for you then just restore to stock and send it to them. (kernel suggestion: latest speedmod kernel. works flawlessly.)

Do you use "enterprise"/RADIUS/802.1x authentication? (This (roughly) means that you need to enter a username and password in order to connect to your network).
I was trying to wait until AT&T releases 2.2, but I'm getting impatient on that front. I'll try to look for the speedmod kernel, perhaps. My office is in an electronics lab, so I wonder if something is spewing out RF interference in here.
-Nathan
joeshmoe08 said:
Thats weird because my phone has no problems like that and I have connected to many WPA networks. I don't know the source of the problem but my suggestion would be try a custom rom before sending to samsung because it can't hurt. If it doesn't work for you then just restore to stock and send it to them. (kernel suggestion: latest speedmod kernel. works flawlessly.)
Click to expand...
Click to collapse

I just flashed my with the Cognition 3.02 firmware and the issue is still present. My hunch is that it is a wifi firmware or driver bug. I doubt that these things are changed in the various kernel builds.... Maybe the official Froyo release will fix it, but at this point I doubt that it will.
Someone in my building suggested that the issues may be caused by us having two separate networks on different sides of the building that have the same ESSID.

[Q] after update to 2.3.6,wifi can not connect

My WiFi connection has always been reliable and robust before the update to 2.3.6,but now it works wrong,the wifi is scanning repeatedly.When I try to connect my wireless,the connection button is disable.
Anyone else seeing this? Would you give me a suggestion?
Thank you!

I've had the same problem since 2.3.6 was pushed to my Nexus One. There seems to be some people with this and other serious issues, but there doesn't appear to be any acknowledgement of the problems from Google. I have read some posts by people who use their phones for their business and such, and the issues with 2.3.6 are causing them to lose time and money. I don't know why they released this, they obviously didn't test it very well.

911 and e911 explained

Personal background: Associate degree in Laser Electro Optics. 12 years research and development semiconductor manufacturing, 15 years as an EMT, last 10 years as a 911 telecommunicator for Austin-Travis County Emergency Medical Services. 6 of those years as a Training Officer.
The reason for my (cough) resume is so everyone understands I have the technical background and experience to explain the differences between e911 and 911.
Public Safety Answering Point: the local organization tasked with answering emergency request phone calls and dispatching appropriate emergency resources. PSAP's are broken into two types, primary and secondary. The primary PSAP is typically the local police department for city's and the local sheriff's department for unincorporated areas. Some colleges have their own police department and may have their own PSAP. So realistically a person can connect to a different 911 call center depending upon their location within a small geographic area.
Large urban areas typically have secondary PSAP's. The secondary PSAP usually consists of public safety departments not related to law enforcement such as fire and/or emergency medical services (ambulance services) specially trained to send request specific resources dependent upon the emergency. In Austin and Travis County we run 120 thousand EMS 911 calls per year. The police department takes about 2000 911 calls per day.
911: a simple to remember phone number nation wide allowing everyone access to emergency services. No location information is transmitted or received. The PSAP is responsible for determining location by interrogation of the caller. This can a problem if the caller is altered or otherwise unable to give accurate information.
e911: Enhanced 911 was created to ensure location information was transmitted to the 911 call center regardless of the callers ability to give this information. The phone companies are responsible for ensuring this information is available and transmitted to the PSAP. Conventional e911 is effective for landline phones. Cell phones present a completely different problem.
Cell phones are required to meet two different location technology standards.
Phase 1 wireless data: as cell phone use skyrocketed in the nineties, legislation was passed requiring provider's to transmit location data based on the cell phone tower that the cell phone was connected to. While this is helpful, it is problematic due to the sheer size of the area that had to be searched if the caller was unable to give their location.
Phase 2 wireless data: legislation now requires GPS location data be provided by the cell phone company. This location information can be transmitted via the gps chip from the cell phone or via radio location triangulation using the cell towers in the immediate area of the caller.
So in a nut shell, my test of neobuddy's ICS indicated that 911 worked for a sim loaded phone. I did not test the phone with the sim pulled. I also did NOT verify that GPS data was being received by the PSAP.
If 911 works with your phone it should work in any area. I was connecting with two different PSAP's as I live right between two different area's and sometimes connect to one or the other.
Hope this clears some of the confusion. A good explanation is located at en.wikipedia.org/wiki/Enhanced_9-1-1.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Later tators
Sent from my Touchpad using xda premium

thanks a lot. i can confirm cm7.1 has 911 issue.
Sent from my SGH-T959 using XDA Premium App

Developers should also note that as technology continues to advance, video conferencing and text message 911 activation requirements will also be legislated in.
I firmly believe that Google should begin requiring manufacturers make their modem software and audio software open source. Manufacturers should also be required to provide detailed explanations of how the relevant library's interface with the operating system, modems and audio system when activating an emergency call. This is Androids achilles heel. All it will take is one national media event to slam the door on open source operating systems for cell phones. I love the freedom Android provides and the exceptional programing skilss of our developers.

Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Sent from a cell tower to the XDA server to you.

Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Click to expand...
Click to collapse
correct as none had the source code....but for 2.3 onwards rom.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Click to expand...
Click to collapse
made my day.....thanks a lot....will be keeping a close eye on this thread...

My understanding is the issue is only without a sim right?

The 911 issue is with SIM, i don't know about without and im not planning on finding out.

HaloMediaz said:
My understanding is the issue is only without a sim right?
Click to expand...
Click to collapse
It has to do with emergency mode (no dim) and when no compatible roaming network is around (no service) .
Sent from my HTC Sensation 4G

hmmm I havent called 911 in YEARS but it still feels nice to have the ability and this was a nice explantion thank you

MIUI 360 in Asheville NC works fine but not in other areas?

Hopefully they can test the cm9 test ports that are out now.
Sent from my SGH-T959 using xda premium

http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.

Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Can we get independent confirmation of this? (not that I don't believe you)
Sent from my SGH-T959 using xda premium

Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.

You typed all that from your touch pad? props
Sent from my SGH-T959 using XDA App

Genesis3 said:
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
Click to expand...
Click to collapse
No, I get that. Just wanted to make sure he verified was all..

Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Don't know who you are or where you came from but, you sir may have saved CM development for the vibrant community. Here's hoping and you're the man!!!
Sent from my SGH-T959

Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
I just downloaded your kang and running great so far, Thanks for you work !!
Question, is this 911 fix kernel dependent ? ie will it break if I flash another cm7 kernel ?
Thanks again for your hard work !!!

will replacing the kernel break both 911 and gps fixes?

I didn't save anything.
Here's the bottom line, if you're interested in it.
In the original Vibrant device directory there was a set of sources for libaudio -- one of the shared libraries that Android depends on to talk to the audio hardware in the phone. There was no documentation as to where this source came from, but I know where it didn't come from -- it didn't come from a public Gingerbread source for the Vibrant, because there isn't one.
It turns out the library this source builds does not work correctly but exactly why I'm not certain of. One of the problems with debugging this is that I have to have someone else test for me, which means I can't do the sort of testing I like to when I'm tracing things like this (a highly-iterative process that requires that I actually be staring at the debugging screen while doing the deeds that cause the bad behavior) since I can't call 911 myself.. Had the provenance of this code been documented originally (or lack thereof) I would have investigated this possible connection, as I knew the problem lay in the audio connectivity due to myriad kernel and application traces a couple of months ago. I didn't chase that library down and attempt to graft in other related versions because I assumed that the CM people knew what they were doing building that library from source rather than using a cribbed copy from, for example, Froyo or a different gingerbread build off a similar device.
Picking up a different shared library does work. Exactly what the provenance of that library is (e.g. was it grabbed from a binary, was it built from DIFFERENT source, where did it come from?) is also unknown.
Now that I have a working shared library on this device and a non-working one I'm going to compare traces. Maybe I'll get lucky and find the changes necessary in the source that's in the build tree and be able to fix that, at which point I'll know what I've got rather than having a "magic" library from God-knows-where.
Now here's the part that annoys me -- I was all over some of the CM guys about audio problems with other Samsung devices and tried to get access to the "not yet finished" repos because I expected that if I could run down the same sort of problem with ordinary calls in one of the OTHER Samsungs it was rather more likely than not that the same fix would be pertinent in some way on the Vibrant -- simply because manufacturers tend to use the same chipsets and bits, along with APIs, between different devices (it makes it easier for their coders and maintainers to do their jobs.) In addition when I started working one this one of the other protagonists didn't give me jack and crap about the provenance of anything in the device tree and, again, there's no docs embedded in the tree either. You can find the flamewar and slander aimed at me here if you'd like. It turns out I was on the right path; the problem this library allegedly fixed was having to hit <MUTE> twice to turn off and on the audio path. Sound familiar? Well, the pointer to the file that I found and integrated was from a bug logged against the I-9000, a similar phone to the Vibrant, and that library version works. What's changed in it? There's no set of commits logged against the ZIP file provided in that patch; is it a binary lift from a different build (e.g. some factory build) or did someone fix the source?
Who the hell knows because again, it's not documented in the bugtracker. Until I know where it came from and, if there's source, I have access to it, I won't support it. I don't play the "hide the sausage" game when it comes to alleged community coding projects.
I ran into something similar with the Triumph in that there was a different set of parameters coming up from the hardware when a wired headset was plugged in. That was easy to run down because I could do it and see what was going on; it was a literal couple of line change in the code once I found it. There are a couple of places in the libaudio source that might be the cause of this now that I have a reason to look in there, but without being able to easily reproduce the condition that creates the failure (e.g. call 911) it's a guess.
The ICS builds out at present have a different copy of the same compiled library and it also works. I bet that one works too on CM7 as it's fairly close to the metal and thus the API's probably the same (or close) on the Android side but I haven't tried it yet. I've got little reason to since I now have a libaudio.so that's functional on CM7 in any event.
While I've been working on the 911 issue (for a couple months on and off) I also traced down some actual working (properly) GPS libraries that handle the AGPS assist data in the correct way, something that other sets of them do not, and added those too. I also made a few other changes. The battery life is reported to be rather impressive, and the near-instant GPS locks most-definitely are. I can't speak much to the battery life view of the world as of yet but I will be looking at that; that's an area I know quite a bit about (getting these devices to properly go into deep sleep as they should) and the source tree I'm working with does have kernel source.
Any sideloaded kernel that leaves libaudio.so alone (check the zip file to make sure that /system/lib/libaudio.so is NOT present) should be ok, but no promises. Before you go screwing with kernels make sure you want to --you might break GPS performance as a number of the kernels have various attempts to get the GPS to work right and load various libraries along with the kernel itself with varying degrees of success.
I'd be willing to maintain this port but there are two conditions -- first, I expect apologies from the CM people who attacked me, in public, and second, I expect a formal commitment that there will be no more hiding of information. "I don't know" is an acceptable answer provided you run down the person who does -- someone does know because someone DID either import or code the material in question; silence and lack of documenting where things came from and how they came to be is not acceptable. When things go into the codebase through review they damn well ought to be documented. I played "talking to the brick wall" with the Triumph and now the Vibrant and I won't do it if I'm taking on responsibility for maintaining something.
If CM wants me involved in this that's the deal. If not I'll consider setting up a parallel build and set of repos for the bits that have to be changed from the base CM7 Gingerbread branch as I did for the Triumph if there are people interested in it, but my time is not unlimited and in all honesty my taste for working with the CM people and the CM code in general has been seriously damaged, never mind that what I have here seems to work just fine. As such the benefits of continued efforts are likely to be relatively small. If I decide against a continuing effort I will take the build environment that produced that I have now and attempt to set up a manifest so it can be cloned by anyone else who cares to do so, which should take care of others being able to build and run the KANGs from source if they wish. The latter may take a while as I need to find a day when I'm not busy and can put that together (again, lack of documentation doesn't help) and then pull a clean test from a zero base and make sure it builds and runs.
The Vibrant is no longer my daily device but I do still own one, and given its relatively modest resale value I'll probably keep it as a spare device -- it's a very credible phone and with working GPS code it actually locks faster and better than my Hercules does. It's biggest shortcoming is that it's relatively RAM-starved compared to more-modern devices.
Fancy that.

[Q&A] CyanogenMod 12 - Lollipop - Pre-Nightly Shakeout

Q&A for CyanogenMod 12 - Lollipop - Pre-Nightly Shakeout
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CyanogenMod 12 - Lollipop - Pre-Nightly Shakeout. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

CM12 dead space on launcher screen
Installed this shakeout looks great!
I have unusable screen real estate on the left and right sidesnof the launcher is this normal?

Resolution and DPI changes in lollipop
With root enabled you can use ResUI from the themes and apps section and DPI changer from the play store. You have to have root enabled for the changes to take effect I believe.

If u make ur grid size custom and scroll down so its the largest, a 9x8 I believe, it uses most of it

ROM Pershoot TF701T 20150227 testing results
so, since I have less than 10 posts, this will automatically be put in the wrong Q&A section. Anyway, I'm running Pershoot's new TF701T Rom 20150227 and want to give some feedback since I also ran the prior version. If an OP would kindly take this restriction off so I can actually post in the correct thread...
This version is much more responsive than the 20150205 Rom. I am using this Rom with Google Keyboard to type this voice message! Everything seems to run very smooth YouTube is good. WiFi is quick, internet and embedded videos are great! Google Apps work fine. Almost 24 hours now and no slow down, battery use is normal and it barely uses any power during sleep.
The only thing I see missing is screen mirroring. Until that is implemented, it can't be a daily user for me. I have not tested GPS yet, & I wonder about the Nvidia specific drivers for the Tegra 4. I do not play games much and have not had a chance to test that either. All in all, it seems like a very stable base!

Miracast & Screen casting
Any idea when screen casting will be implemented? I have been playing with the latest build and all seems great! The settings menu is quite confusing and took forever to find the keyboard settings... I also find it difficult to find other settings that are common in prior Android versions. Is there anyway to keep the KitKat version of settings? ?

getting there... CM 12 testing
okay, so I'm using the current cm 12 20150309. I actually get to enable miracast and see receiving devices but I cannot connect to them. I have tried with a LC Smart TV and a Roku streaming stick which neither will connect. Also, the stock 442 version will only connect to the lc tv and not the streaming stick... the Roku is still in beta just to let you know.
this is also getting posted in the wrong thread again! hopefully the OP will recognize this and I don't think that is even recognizing that this is the third posting of mine! My posts are not getting counted...

i've enabled wifi display and protected buffers support for it (also enabled in the CM11 build); ensure its checked (in casting; wireless display). i have no way to test. you'd need to post logs and i'll see what i can do, or submit a patch which sorts it out to gerrit, against the known working device.

more testing... 20150311
Once again I am using the latest cm build with Google keyboard to voice type this message. this build is definitely quick and responsive and miracast or screencasting is almost functional. I have tried about a hundred combinations of settings on both receiving devices and this tablet without success. Also I noticed that I cannot connect to an external Bluetooth speaker without the launcher crashing when trying to use the volume keys. The Bluetooth speaker will connect but there is no sound and it crashes the launcher. Seems to me as a buffering or memory allocation issue since both devices want to connect but cannot finalize the handshake.
Let me know what the easiest way to pull log files off of this tablet is and I will see what I can help with... ???

Take note of the 'Known Issues' (on DB), and you will see the workaround for the Bluetooth issue (un-select Phone Audio on the device's BT settings).
Pull a logcat while trying to connect to a known working Miracast device and post it.
Thx.

10-4...
pershoot said:
Take note of the 'Known Issues' (on DB), and you will see the workaround for the Bluetooth issue (un-select Phone Audio on the device's BT settings).
Pull a logcat while trying to connect to a known working Miracast device and post it.
Thx.
Click to expand...
Click to collapse
will do, I'll see what I can get you tomorrow for some fresh logs... ?

Howdy strangers...!
So, I am just playing around with Pershoot's new cm 12 OS and I am wondering why hundreds of people view this thread and nobody contributes! There must be many more people out there that can provide debugging and log information than just me! Let's all work together and get this done ASAP! Don't be intimidated to contribute to this thread! We need all the input everybody has on everything!?

K94U said:
So, I am just playing around with Pershoot's new cm 12 OS and I am wondering why hundreds of people view this thread and nobody contributes! There must be many more people out there that can provide debugging and log information than just me! Let's all work together and get this done ASAP! Don't be intimidated to contribute to this thread! We need all the input everybody has on everything!?
Click to expand...
Click to collapse
Havent miracast or something like this. BT speaker is working here. Atm i havent any problem with this build (except ui battery symbol of dock isnt visible)
Gesendet von meinem LG-D855 mit Tapatalk

20150313 miracast log
Here is the log file... Tried to connect miracast to the LG TV 3 times in different ways. Also, the stock browser has no upload options for attaching documents to XDA posts. I got my Bluetooth speaker working... Thanks!!!
I do not know why this log file ended up having such a long name but it is the original file.

20150313 miracast log for Roku
Here is the log file for trying to connect miracast to the Roku streaming stick. I tried 3 times and it tries to connect then the roku immediately goes back to the home screen. Thanks!

more casting info
I have a verizon wireless galaxy s4 that connects to both the LG TV and the Roku streaming stick just fine running the latest stock 442. The latest stock version 11. 4.1. 29 for this tablet will only connect to the LG TV after numerous tries but not the Roku. ?

I haven't looked at your log as of yet. but please only post the one from the device that is known working against stock.
Please also post a log from stock of it working.
Thx.

Just noticed this week while I was away that when a USB is plugged into the dock everything works however there is no notification that it is plugged in and there is no way to eject it. Also if you close the dock while it is plugged in and then open it it tells you that it was not safely removed. I am not sure if that is stock behavior or not and it is not really an issue if I could eject it properly.

Turn off MTP and you should get eject options in storage.

pershoot said:
Turn off MTP and you should get eject options in storage.
Click to expand...
Click to collapse
pick up 3/15 and you'll get the extended options for USB in storage.

Problem with smart view after oreo update

I doubt many have this problem as most people using smart view have a wifi connection they use to connect their devices to. My display adapter is one that doesn't connect to a network but instead basically creates it's on wifi connection that my phone connects to using WiFi direct. Before the Oreo update it worked flawlessly and still does on my S7 Edge.
Now when I try to connect to it on my Note 8 it's tries to connect and in some instances connects, but then almost immediately disconnects there after. I contacted samsung support and had them remote into it to see if they could get it to work. They told me it was a bug and that they would forward it to the development team, and that a fix should come soon for the bug. Well it's now going on three weeks since then and there has yet to be a update out fixing the issue. I emailed Samsung support reminding them of the issue and they said there was no reported problems related to smart view and that the next update should fix a lot of the bugs that came with the first update.
My hope with this post is that others might have the same issue or a work around, and if not, that maybe Samsung will eventually see it and find a fix for it. My S7 doesn't perform as well as my Note 8 so I'm hoping a solution comes soon.

You are not the only one, but i have another kind of problem with smart view...