OK, hopefully this thread isn't in the wrong place... (If it is, feel free to flame and call me whatever, I'm just trying to get something done and I know all the devs watch this section)
I am in the US, and I am fully aware of the legalities of broadcasting on channels other than 1-11. I have several routers, running dd-wrt firmware, and three of the four are running as repeater bridges. Due to the extremely noisy wireless environment caused by neighboring networks, the only way I can get a clear signal between all of them is by setting the wireless channel to channel 14. Unfortunately, as soon as I do that, my Captivate no longer sees the network. This is exceedingly upsetting when my fiance shows me her iphone... which is still connected to the network!
I know it's not much, but I'm hoping that others will chip in or that some dev will take pity on me, but I've got $10 on a solution, paypal to whoever can make my Captivate connect to my wireless network on channel 14.
In hopes that others contribute as well, I'll make a list with total bounty:
Total: $15 - wifi channels 12, 13, 14 enabled
richhed - $10
ccdoggy - $5
BONUS!!!
Evidently, while we're messing with the wpasupplicant and wireless drivers, others have chimed in with an interest in the 5GHz wifi channels. Hopefully while tweaking the drivers that run the wireless radio to enable channels from other regions, a way to enable the 5GHz frequency will be discovered as well!
TOTAL: $35 - Enable 5GHz frequency wifi channels
ccdoggy - $5
Shammyh - $20 --- THANK YOU
DarkSi08 - $10
I never tested it, but the CyanogenMod 6.1 12-27 nightly definitely allows you to choose the channel (I saw 11-14 if I remember correctly), so if you run that you should be able to have the option to change it.
I know this isn't quite what you're looking for, but it's the only immediate solution that I know of.
root your phone and Install a custom ROM, than you need to choose a working modem.bin (european versions support those extra channels, please go to the modem thread to get more information)
the problem is: to enable 850MHz band on those modems... it is not impossible
good luck
Currently working on this
Code:
static struct ieee80211_channel __wl_2ghz_channels[] = {
CHAN2G(1, 2412, 0),
CHAN2G(2, 2417, 0),
CHAN2G(3, 2422, 0),
CHAN2G(4, 2427, 0),
CHAN2G(5, 2432, 0),
CHAN2G(6, 2437, 0),
CHAN2G(7, 2442, 0),
CHAN2G(8, 2447, 0),
CHAN2G(9, 2452, 0),
CHAN2G(10, 2457, 0),
CHAN2G(11, 2462, 0),
CHAN2G(12, 2467, 0),
CHAN2G(13, 2472, 0),
CHAN2G(14, 2484, 0),
};
static struct ieee80211_channel __wl_5ghz_a_channels[] = {
CHAN5G(34, 0), CHAN5G(36, 0),
CHAN5G(38, 0), CHAN5G(40, 0),
CHAN5G(42, 0), CHAN5G(44, 0),
CHAN5G(46, 0), CHAN5G(48, 0),
CHAN5G(52, 0), CHAN5G(56, 0),
CHAN5G(60, 0), CHAN5G(64, 0),
CHAN5G(100, 0), CHAN5G(104, 0),
CHAN5G(108, 0), CHAN5G(112, 0),
CHAN5G(116, 0), CHAN5G(120, 0),
CHAN5G(124, 0), CHAN5G(128, 0),
CHAN5G(132, 0), CHAN5G(136, 0),
CHAN5G(140, 0), CHAN5G(149, 0),
CHAN5G(153, 0), CHAN5G(157, 0),
CHAN5G(161, 0), CHAN5G(165, 0),
CHAN5G(184, 0), CHAN5G(188, 0),
CHAN5G(192, 0), CHAN5G(196, 0),
CHAN5G(200, 0), CHAN5G(204, 0),
CHAN5G(208, 0), CHAN5G(212, 0),
CHAN5G(216, 0),
};
static struct ieee80211_channel __wl_5ghz_n_channels[] = {
CHAN5G(32, 0), CHAN5G(34, 0),
CHAN5G(36, 0), CHAN5G(38, 0),
CHAN5G(40, 0), CHAN5G(42, 0),
CHAN5G(44, 0), CHAN5G(46, 0),
CHAN5G(48, 0), CHAN5G(50, 0),
CHAN5G(52, 0), CHAN5G(54, 0),
CHAN5G(56, 0), CHAN5G(58, 0),
CHAN5G(60, 0), CHAN5G(62, 0),
CHAN5G(64, 0), CHAN5G(66, 0),
CHAN5G(68, 0), CHAN5G(70, 0),
CHAN5G(72, 0), CHAN5G(74, 0),
CHAN5G(76, 0), CHAN5G(78, 0),
CHAN5G(80, 0), CHAN5G(82, 0),
CHAN5G(84, 0), CHAN5G(86, 0),
CHAN5G(88, 0), CHAN5G(90, 0),
CHAN5G(92, 0), CHAN5G(94, 0),
CHAN5G(96, 0), CHAN5G(98, 0),
CHAN5G(100, 0), CHAN5G(102, 0),
CHAN5G(104, 0), CHAN5G(106, 0),
CHAN5G(108, 0), CHAN5G(110, 0),
CHAN5G(112, 0), CHAN5G(114, 0),
CHAN5G(116, 0), CHAN5G(118, 0),
CHAN5G(120, 0), CHAN5G(122, 0),
CHAN5G(124, 0), CHAN5G(126, 0),
CHAN5G(128, 0), CHAN5G(130, 0),
CHAN5G(132, 0), CHAN5G(134, 0),
CHAN5G(136, 0), CHAN5G(138, 0),
CHAN5G(140, 0), CHAN5G(142, 0),
CHAN5G(144, 0), CHAN5G(145, 0),
CHAN5G(146, 0), CHAN5G(147, 0),
CHAN5G(148, 0), CHAN5G(149, 0),
CHAN5G(150, 0), CHAN5G(151, 0),
CHAN5G(152, 0), CHAN5G(153, 0),
CHAN5G(154, 0), CHAN5G(155, 0),
CHAN5G(156, 0), CHAN5G(157, 0),
CHAN5G(158, 0), CHAN5G(159, 0),
CHAN5G(160, 0), CHAN5G(161, 0),
CHAN5G(162, 0), CHAN5G(163, 0),
CHAN5G(164, 0), CHAN5G(165, 0),
CHAN5G(166, 0), CHAN5G(168, 0),
CHAN5G(170, 0), CHAN5G(172, 0),
CHAN5G(174, 0), CHAN5G(176, 0),
CHAN5G(178, 0), CHAN5G(180, 0),
CHAN5G(182, 0), CHAN5G(184, 0),
CHAN5G(186, 0), CHAN5G(188, 0),
CHAN5G(190, 0), CHAN5G(192, 0),
CHAN5G(194, 0), CHAN5G(196, 0),
CHAN5G(198, 0), CHAN5G(200, 0),
CHAN5G(202, 0), CHAN5G(204, 0),
CHAN5G(206, 0), CHAN5G(208, 0),
CHAN5G(210, 0), CHAN5G(212, 0),
CHAN5G(214, 0), CHAN5G(216, 0),
CHAN5G(218, 0), CHAN5G(220, 0),
CHAN5G(222, 0), CHAN5G(224, 0),
CHAN5G(226, 0), CHAN5G(228, 0),
};
THANK YOU DG! BTW, about to flash Cog3, Love your ROMs!
designgears said:
Currently working on this
Click to expand...
Click to collapse
get the 5 GHz frequency working (somehow?) and I'll be pleased. tired of my dual band router's N not being used.
For the bridges you might seriously consider using a 5 or 10mhz channel.. Dont know the bandwidth requirements but by using a smaller channel that is not one of the primary non overlapping channels you cut noise by almost 50%, thus allowing the bridges to get a clear signal to each other.. however normal 802.11 devices dont support < 20mhz channels, so if the bridges arent using a dedicated bridge link with 1 other ssid for the wireless clients, obviously there will be problems. I think dd-wrt will support the smaller channels (down to 5 mhz i believe) on certain hw configurations. The other option is to use a 5ghz bridge link and 2.4 client ap.
In extremely noisy situations, the only fix is a better antenna. The idea being, more power going out, more power to your devices, and with an antenna the devices signal gets amped back up too.. However the noise will also, but due to proximity the SNR at the AP should be within acceptable parameters for a decent link on 802.11n with a 20mhz channel. Do not use 40mhz channels this will only make it worse. For a good indoor solution in noisy environments (6 or more SSID's with a signal of -75 or better dbm) I'd get a Ubiquity Bullet with a 9-13dbi omni OR 16 dbm sector aimed in the direction that makes sense. This will increase usability enormously.
Wait... Does Dg' post mean the cappy supports 5 ghz wireless N?
Sent from my SGH-I897 using XDA App
No his post means he is working on channels 12-14, where does it ever say he is working on 5 ghz N??
silverslotcar said:
No his post means he is working on channels 12-14, where does it ever say he is working on 5 ghz N??
Click to expand...
Click to collapse
I think he just misunderstood my out of the park request (and the fact that the "code" quoted part of DG's post mentions a 5GHz part). the hardware in our phones doesn't support the 5 GHz frequency for wifi, so (unless the functionality is there and they just don't have it enabled?) that's just a pipedream in my mind that I jokingly requested.
There are 5 ghz channels listed in his post above. i thought that maybe enabling all of the 2.4 channels would also enable 5 ghz channels. I was just asking as from what i can tell from dg's post 5 ghz was listed. Yes i know the hardware needs to support it, it was worth just asking.
Sent from my SGH-I897 using XDA App
Kaik541 said:
I think he just misunderstood my out of the park request (and the fact that the "code" quoted part of DG's post mentions a 5GHz part). the hardware in our phones doesn't support the 5 GHz frequency for wifi, so (unless the functionality is there and they just don't have it enabled?) that's just a pipedream in my mind that I jokingly requested.
Click to expand...
Click to collapse
Exactly. Looking at it more i see that dg's post is just the regulatory domain regulations. 5 ghz is included because its he regulations for the country. My bad.
Sent from my SGH-I897 using XDA App
ccdoggy said:
Wait... Does Dg' post mean the cappy supports 5 ghz wireless N?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Im not 100% sure if it does or not, but the source is there for it. I am pretty sure the same driver is used on the models that do support it. That would be my guess..
But then I found that the Galaxy Tab has dual band support and runs the exact same chip..
Still at a whopping $10! Come on folks, I can't be the only person that needs this functionality? Let's get a few more pledges and make this worth DG's (or another dev's) while!
designgears said:
Im not 100% sure if it does or not, but the source is there for it. I am pretty sure the same driver is used on the models that do support it. That would be my guess..
But then I found that the Galaxy Tab has dual band support and runs the exact same chip..
Click to expand...
Click to collapse
Now, THAT would interest me. 5.0 Ghz just for the ability to do network scans for conflicting networks for that range also.
$5 for upper 2.4 channels
$5 for enabling 5.0 if possible
Isn't there anyone else who can throw some more money in on this and make it worth DG's (or someone else's) time? Anyone who might want to, say, travel to Europe or Japan, and be able to take their phone with them, and connect to these upper channels?
Sent from my SAMSUNG-SGH-I897 running Cognition 3.02, Firebird2 kernel, and i9000UGJK4 modem, using XDA App
I'd put up a solid $20 if someone figures out how to get the Captivate to work w/ 5 GHz 802.11a/n networks.
thekurrgan said:
For the bridges you might seriously consider using a 5 or 10mhz channel.. Dont know the bandwidth requirements but by using a smaller channel that is not one of the primary non overlapping channels you cut noise by almost 50%, thus allowing the bridges to get a clear signal to each other.. however normal 802.11 devices dont support < 20mhz channels, so if the bridges arent using a dedicated bridge link with 1 other ssid for the wireless clients, obviously there will be problems. I think dd-wrt will support the smaller channels (down to 5 mhz i believe) on certain hw configurations. The other option is to use a 5ghz bridge link and 2.4 client ap.
In extremely noisy situations, the only fix is a better antenna. The idea being, more power going out, more power to your devices, and with an antenna the devices signal gets amped back up too.. However the noise will also, but due to proximity the SNR at the AP should be within acceptable parameters for a decent link on 802.11n with a 20mhz channel. Do not use 40mhz channels this will only make it worse. For a good indoor solution in noisy environments (6 or more SSID's with a signal of -75 or better dbm) I'd get a Ubiquity Bullet with a 9-13dbi omni OR 16 dbm sector aimed in the direction that makes sense. This will increase usability enormously.
Click to expand...
Click to collapse
if the signal strength is a big factor then couldnt the op just set the antenna strength higher? i have 2 routers with dd-wrt one set as a repeater and the default antenna power setting is 70-71mw or something, they can both be turned up to 251mw. my entire block and a neighboring one can pickup my wifi if i leave it unsecured with the antenna power at max but i use the default settings, no need to broadcast free internet to 50+ people. i dont do that but my brother did with his router when he lived here, combined with some bigger antennas he used to share his wifi with his friend 3 houses up the road.
Perhaps change the country code in nvram_mfg.txt or nvram_net.txt and see what happens. The files are in /system/etc/wifi/:
Code:
# country code
ccode=EU
Change it to JP, since channel 14 is allowed in Japan.
Dani897 said:
if the signal strength is a big factor then couldnt the op just set the antenna strength higher? i have 2 routers with dd-wrt one set as a repeater and the default antenna power setting is 70-71mw or something, they can both be turned up to 251mw. my entire block and a neighboring one can pickup my wifi if i leave it unsecured with the antenna power at max but i use the default settings, no need to broadcast free internet to 50+ people. i dont do that but my brother did with his router when he lived here, combined with some bigger antennas he used to share his wifi with his friend 3 houses up the road.
Click to expand...
Click to collapse
Well yes, if it were that easy... And if I had about 30 spare WRT54G routers lying around... I appreciate your trying to help, but if you increase the Tx power above around 90mW (on Linksys WRT54G routers) you can plan on replacing it by next week or so. The board and the radio are inside a plastic housing that barely has adequate ventilation slots for the amount of heat produced by the radio at the stock Tx power levels, and I know from experience that just because the firmware allows it doesn't mean that you should do it...
Even if that wasn't the case, OR if I wanted to solder in a case fan on to of the radio chipset, the more you increase Tx Power, the more you increase noise. I once heard the analogy of a noisy wireless network being like a crowded concert hall. If you were sitting next to me in a concert hall, and we were having difficulty hearing one another, I could put my hands to my mouth, cup them around your ear, and scream at the top of my lungs right into your ear, and you would definitely hear me, but it's doubtful you would understand what I said (doubtful you would understand much of anything coming from that direction for the next ten minutes or more, actually). In the same fashion, if there lots of other wireless networks in range, increasing the Power of your network without trying a channel with less noise is actually counter-productive. The more noise, the worse your SNR, and SNR in any connection IS your effective link quality. I have 8, (yes, 8) other networks in range of my primary AP (gateway), all range between channels 1 and 9... There are two other networks on channel 11 in range of my first repeater, and then one more on channel 6 in range of the second repeater. I wish I could solve the signal quality issue as easily as cranking the volume up to the max, but when I increase it even past 84mW my clients in range of the primary AP start getting packet loss and terribly intermittent connectivity loss.
___________________
ppmz said:
Perhaps change the country code in nvram_mfg.txt or nvram_net.txt and see what happens. The files are in /system/etc/wifi/:
Code:
# country code
ccode=EU
Change it to JP, since channel 14 is allowed in Japan.
Click to expand...
Click to collapse
I appreciate you trying to help out, I was thinking along the same lines at first. I have tried editing the settings.db file, changed the wifi_num_allowed_channels to 14 from 11, I edited the build.prop ro.wifi.channels also from 11 to 14, and I changed the ro.product.locale.region from US to JP. I also changed the country code to JP in both of the system/etc/wifi/ files you are referring to, all to no avail... Trust me, if it was something that easy (simple sqlite .db editing with root explorer, move back to /dbdata/ and chown system system, fix permissions... I'd have been posting a fix rather than a bounty. It seems to be deeper-rooted than that... Seems to be related to the now missing wireless regulatory domain setting that was once present in the settings for android devices, but has apparently been removed in (eclair? donut?) and newer OS revisions.
Thank you all for your input, and for your attempts at a solution. I am sure that if we keep at it we'll find the solution, and as of right now the first person who does will be the recipient of a whopping $40!
Sent from my SAMSUNG-SGH-I897 using XDA App
My S4 constantly reboots (every 10 minutes or so) whenever it is connected to a car bluetooth system. It happens with both a Parrot MKi9100 (fitted to a Mazda 6) and a JVC KD-R811 (fitted to a Honda S2000). I'm running Android 4.4.2 (Phoenix ROM v4.4.2). I've tried wiping the cache partition but it didn't help.
Has anyone else had this problem? Any ideas what I can try to fix it?
Seems like a kernel problem but without a logcat it's impossible to tell. Try a different kernel.
Lennyz1988 said:
Seems like a kernel problem but without a logcat it's impossible to tell. Try a different kernel.
Click to expand...
Click to collapse
I've been trying to reproduce it, with the car in the garage, while running aLogrec, but of course it refuses to reboot after 45 minutes.
I've never reflashed a kernel. Any recommendations for something stable? (I don't need bells and whistles/overclocking etc)
Could be the battery.
Bluetooth causes a little extra power usage. If the battery is shot it might not be able to handle the added load of bluetooth draw.
This has been the cause of reboots when using the torch or the camera before.
Of course this might not be the problem at all. But if you have access to a spare battery, its worth a shot to swap them out and see if it makes a difference.
Skipjacks said:
Could be the battery.
Bluetooth causes a little extra power usage. If the battery is shot it might not be able to handle the added load of bluetooth draw.
This has been the cause of reboots when using the torch or the camera before.
Of course this might not be the problem at all. But if you have access to a spare battery, its worth a shot to swap them out and see if it makes a difference.
Click to expand...
Click to collapse
Coincidentally, I was using my spare battery when I was trying (unsuccessfully) to get it to reboot in the garage. In any case I have now just tried again with the "normal" battery, but after an hour it also wouldn't reboot. In any case, the phone is usually (but not always) connected to the cigarette lighter power source in the car. At one point I thought that that might be the problem, but it still reboots frequently when running off battery.
It seems that the problem only arises while the car is moving. I tried turning off wifi while driving (thinking it might be caused by the phone hunting for wifi connections), but it didn't help. Now I'm running out of ideas.
???
The part where it only happens when moving is weird.
How about if the car is parked but you shake the phone?
I could see if there was something loose in the phone that the road vibrations could trigger it. The first thing I'd suspect is a loose battery. Bit shaking it would prove or disprove that theory real quick.
Skipjacks said:
The part where it only happens when moving is weird.
How about if the car is parked but you shake the phone?
I could see if there was something loose in the phone that the road vibrations could trigger it. The first thing I'd suspect is a loose battery. Bit shaking it would prove or disprove that theory real quick.
Click to expand...
Click to collapse
Hmm...interesting theory....so I just reconnected it to the car in the garage and bumped the phone around., including knocking it quite hard on the steering wheel a few times. It didn't bat an eyelid
Hmmmm....that's a tough one.
I am down to demonic possession as the most likely issue.
Did you try contacting an old priest and a young priest?
Seriously I am completely stumped on this one.
(I know most of xda is a younger crowd. This is a joke from the movie The Exorcist that many of you aren't even aware of)
Skipjacks said:
Hmmmm....that's a tough one.
I am down to demonic possession as the most likely issue.
Did you try contacting an old priest and a young priest?
Seriously I am completely stumped on this one.
(I know most of xda is a younger crowd. This is a joke from the movie The Exorcist that many of you aren't even aware of)
Click to expand...
Click to collapse
The more I analyse it the more your demonic possession theory seems to apply, so I'll see whether CheckaTrade can help with an exorcist.
In the meantime I might investigate trying a different kernel, although I have no idea where to start with that yet....
OK so the phone rebooted in the car while I had aLogRec running (within a few minutes of the phone connecting to the car's bluetooth), and I saved the log output (the last part is below). Can anyone see anything here that might give a clue as to what caused the reboot?
Code:
D/TextLayoutCache( 2679): Enable myanmar Zawgyi converter
D/TextLayoutCache( 2679): Enable myanmar Zawgyi converter
D/SSRMv2:Monitor( 905): SIOP:: AP = 520, Prev AP = 520, Duration = 10026, PST = 519
D/SSRMv2:AmoledAdjustTimer( 905): prevTemp = 297, currTemp = 298, prevStep = 4, currStep = 4
I/ActivityManager( 905): Waited long enough for: ServiceRecord{45216848 u0 com.amazon.venezia/com.amazon.mcc.crashreporter.android.CrashReportService}
D/HeadsetPhoneState( 1823): Signal level : previous=4 curr=4
D/STATUSBAR-NetworkController( 1257): onSignalStrengthsChanged signalStrength=SignalStrength: 24 -1 -1 -1 -1 -1 -1 99 2147483647 2147483647 2147483647 -1 2147483647 gsm|lte 0x4 level=4
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
D/EnterpriseDeviceManager( 905): ContainerId: 0
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
D/AlarmManagerService( 905): Kernel timezone updated to 0 minutes west of GMT
I/ServiceManager( 321): Waiting for service AtCmdFwd...
D/STATUSBAR-NetworkController( 1257): onServiceStateChanged voiceState=0 dataState=0
D/STATUSBAR-NetworkController( 1257): onServiceStateChanged mDataNetType=10
D/STATUSBAR-NetworkController( 1257): getUpdateDataNetType() - mDataNetType:10
D/HeadsetPhoneState( 1823): sendDeviceStateChanged. mService=1 mSignal=4 mRoam=0 mBatteryCharge=5
D/HeadsetStateMachine( 1823): Connected process message: 11
D/PopupuiReceiver(15367): onReceive() getAction : android.intent.action.NETWORK_SET_TIMEZONE
D/PopupuiReceiver(15367): NETWORK_SET_TIME prevMCCvalue : -111
D/PopupuiReceiver(15367): gsm.operator.numeric : 234
D/STATUSBAR-NetworkController( 1257): updateDataNetType()
D/STATUSBAR-NetworkController( 1257): Nothing, mRoamingIconId = 0
D/STATUSBAR-NetworkController( 1257): refreshSignalCluster - setNWBoosterIndicators(false)
D/STATUSBAR-NetworkController( 1257): refreshSignalCluster: data=2 bt=false
E/MP-Decision( 2130): num online cores: 2 reqd : 3 available : 4 rq_depth:3.300000 hotplug_avg_load_dw: 108
E/MP-Decision( 2130): UP cpu:1 core_idx:1 Nw:1.900000 Tw:140 rq:3.300000 seq:0.000000
E/MP-Decision( 2130): UP cpu:2 core_idx:2 Nw:2.700000 Tw:90 rq:3.300000 seq:98.000000
D/PopupuiReceiver(15367): MCC init : mccstrcmp
D/STATUSBAR-AirplaneModeQuickSettingButton( 1257): mPhoneStateListener - inAirplaneMode: false
D/STATUSBAR-IconMerger( 1257): checkOverflow(576), More:false, Req:false Child:6
D/WifiController( 905): SET_AP_BOOSTER_FLAG ignored due to state change
D/HeadsetPhoneState( 1823): sendDeviceDataStateChanged
D/HeadsetStateMachine( 1823): Connected process message: 20
D/WifiService( 905): onDataConnectionStateChanged: state -2, networkType - HSPA
D/STATUSBAR-NetworkController( 1257): onDataConnectionStateChanged: state=2 type=10
D/STATUSBAR-NetworkController( 1257): getUpdateDataNetType() - mDataNetType:10
D/STATUSBAR-NetworkController( 1257): updateDataNetType()
D/STATUSBAR-NetworkController( 1257): Nothing, mRoamingIconId = 0
D/MobileDataStateTracker( 905): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
D/PhoneApp( 1503): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
D/FileWriteThread( 1503): FileWriteThread : threadType = 2
D/NotificationMgr( 1503): hideDataDisconnectedRoaming()...
I/BootupListener( 1503): mPendingNetworkManualSelection : false
D/MobileDataStateTracker( 905): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
D/StatusChecker(14637): onReceive : android.intent.action.SERVICE_STATE
D/StatusChecker(14637): Service state changed : 0
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
V/AlarmManager( 905): waitForAlarm result :4
I/wpa_supplicant( 1285): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00 SSID=
V/AlarmManager( 905): waitForAlarm result :4
I/wpa_supplicant( 1285): Scan requested (ret=0) - scan timeout 30 seconds
D/Sensorhubs( 293): readContextData: 1, 1, 7, 0
D/SensorHubManager( 905): onGetSensorHubDataLocked: library = 1, 1, 7, 0
D/CAE ( 905): onGetSensorHubData(SensorHubParserProvider.java:69) - onGetSensorHubData Event [event buffer len :4]
I/CAE ( 905): parse(SensorHubParserProvider.java:142) - buffer size = 4
I/CAE ( 905): parse(SensorHubParserProvider.java:153) - 1, 1, 7, 0,
D/CAE ( 905): display(ContextProvider.java:357) - ================= AUTO_ROTATION =================
I/CAE ( 905): display(ContextProvider.java:373) - Angle=[0]
D/SContextService( 905): updateSContext() : event = Auto Rotation
V/WindowOrientationListener( 905): mSContextAutoRotationListener.onSContextChanged, Rotation: 0
E/MP-Decision( 2130): num online cores: 3 reqd : 2 available : 4 rq_depth:0.600000 hotplug_avg_load_dw: 134
E/MP-Decision( 2130): DOWN cpu:2 core_idx:2 Ns:2.100000 Ts:240 rq:0.600000 seq:243.000000
W/EDMNativeHelper( 268): EDMNativeHelperService is published
W/ActivityManager( 905): destPackageName = null
D/HeadsetPhoneState( 1823): Signal level : previous=4 curr=4
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
D/STATUSBAR-NetworkController( 1257): onSignalStrengthsChanged signalStrength=SignalStrength: 24 -1 -1 -1 -1 -1 -1 99 2147483647 2147483647 2147483647 -1 2147483647 gsm|lte 0x4 level=4
I/ServiceKeeper( 905): In getpackagename pid = 905 uid = 1000 package name = android
W/GAV4 ( 2270): Thread[Thread-130,5,main]: Using destination https://ssl.google-analytics.com
D/PowerManagerService( 905): [api] release WakeLock flags=0x3000000a tag=SuperSU Receiver Wakelock uid=10162 pid=14704 (0x0)
D/PowerManagerService( 905): [api] applyWakeLockFlagsOnReleaseLocked : userActivityNoUpdateLocked is called : SCREEN_BRIGHT_WAKE_LOCK 'SuperSU Receiver Wakelock' ACQUIRE_CAUSES_WAKEUP ON_AFTER_RELEASE (uid=10162, pid=14704, ws=null) (elapsedTime=10001)
I/ServiceKeeper( 905): In getpackag
So it seems that the problem is wifi-related. I've taken a few journeys now with wifi disabled, and have had no reboots in over an hour of driving. I guess the reboots are happening as the phone hunts for new wifi signals?
Can anyone suggest anything I can try to fix this? (different kernel, ...?)