[ROM][official] HTC OneX CyanogenMod 10.1 (4.2) release

[Thömy]

KitKat won't be the way for me for a long time it seems I just downgraded from the 10.2 stable because of bluetooth, wifi and dosbox issues... Any ETA on addressing the first two in CM11?

Can you be more specific please? Enabling BT is fixed but there are issues with headsets. What's the problem with WiFi? Low signal and no WiFi Direct?

 

[morningstar.fallen]

Can you be more specific please? Enabling BT is fixed but there are issues with headsets. What's the problem with WiFi? Low signal and no WiFi Direct?

Well BT just wouldn't turn on. Then all of a sudden, when coming out of the flight mode or after restart it turns itself on. But if I turn it off again, it won't come back on.

And wifi takes forever to connect and the signal reception isn't great either.

I wish I could give you some log readings but what's done is done and I am already back to 10.1.3.

Everything works now and the only minor issue is the app drawer sometimes crashing.

 

[Thömy]

Well BT just wouldn't turn on. Then all of a sudden, when coming out of the flight mode or after restart it turns itself on. But if I turn it off again, it won't come back on.

Hm, I thought that is fixed. Haven't seen any reports during the last week. Did you try the most recent nightly or the M4 release?

And wifi takes forever to connect and the signal reception isn't great either.

So you are positive the signal is weaker and it doesn't just show less bars? But more or less a known problem.

 

[morningstar.fallen]

Hm, I thought that is fixed. Haven't seen any reports during the last week. Did you try the most recent nightly or the M4 release?

I have only been using 10.2.1 stable so far. Did not try the CM11 yet because I was a bit worried about the whole "not working" section It might as well be that the BT issue was fixed in later releases and I just didn't know about it. What finally made me to downgrade, was the fact that my paid DosBox turbo app kept crashing (but that's probably nothing to do with you guys).

I used to be more adventurous back in the day, flashing new roms weekly and daily, but now I am just looking for stability.

So you are positive the signal is weaker and it doesn't just show less bars? But more or less a known problem.

It is possible that it was showing less bars rather than the reception being actually weak. My main worry though, was the fact that it always took a rather long time to connect, comparing to 10.1.x builds.

 

[Thömy]

I have only been using 10.2.1 stable so far. Did not try the CM11 yet because I was a bit worried about the whole "not working" section

That explains it. I haven't fixed it CM 10.2. Backporting the the fix will be easy but useless because there are no automated builds anymore. Also the "not working" section is actually smaller than the CM 11 one. The only think (that I can think of right now) that works in CM 10.2 but not CM 11 is WiFi Direct.

What finally made me to downgrade, was the fact that my paid DosBox turbo app kept crashing (but that's probably nothing to do with you guys).

Try to get a log of the crash next time please. But it can indeed be a DosBox problem

I used to be more adventurous back in the day, flashing new roms weekly and daily, but now I am just looking for stability.

I understand you. Unfortunately I'm not able (read: I don't want) to support more than one release and also CyanogenMod only allows automated builds for one version.

It is possible that it was showing less bars rather than the reception being actually weak. My main worry though, was the fact that it always took a rather long time to connect, comparing to 10.1.x builds.

Long as in several seconds or long as in minutes? I don't experience such a thing if the signal strong enough. If it's not then Android might decide it's better to use mobile data instead. Anyway the "weak WiFi signal" issue is something that's been around for a long time. It's something I want to fix or at least understand. But I don't know where to start and it requires hopping between Sense/CM10.1/CM11 ROMs which is a bit tedious without a second device. Combined with the fact that some devices actually have WiFi antenna issues makes this even harder.


I would love to know from more users why they still use CM 10.1 or CM 10.2 and if there is anything I can do. But I doubt many of them check XDA anymore if they are satisfied.

 

[morningstar.fallen]

Try to get a log of the crash next time please. But it can indeed be a DosBox problem.

Will do!

Long as in several seconds or long as in minutes? I don't experience such a thing if the signal strong enough. If it's not then Android might decide it's better to use mobile data instead. Anyway the "weak WiFi signal" issue is something that's been around for a long time. It's something I want to fix or at least understand. But I don't know where to start and it requires hopping between Sense/CM10.1/CM11 ROMs which is a bit tedious without a second device. Combined with the fact that some devices actually have WiFi antenna issues makes this even harder.

In my case there is a difference of let's say 10 to 15 seconds of connecting to a known network with 10.1.x and close to, or sometimes over 1 minute with 10.2.x

I would love to know from more users why they still use CM 10.1 or CM 10.2 and if there is anything I can do. But I doubt many of them check XDA anymore if they are satisfied.

I suppose there are lots of people like myself who like CM so much and don't have the time or will (or both) to experiment anymore. I don't come here nearly as often as I used to (partially because of the quality of your software and partially because of being generally a busy person). But perhaps when the stable of CM11 is released I'll give it a shot.

Thanks a lot for your help!

 

[vedko]

I would love to know from more users why they still use CM 10.1 or CM 10.2 and if there is anything I can do. But I doubt many of them check XDA anymore if they are satisfied.

I passed my HOX over to my brother and a few weeks ago I upgraded it to 10.2.1. He's not a "flasher" and needs stability (and lives a few hundreds km away so I cannot run over to fix it if something breaks). But yes, there are still people using older versions and they're satisfied with them!

Having said that I need to add: Thömy, thanks a LOT for the effort you put into the development for HOX! Without any exaggeration you kept this great device alive.

And btw.: yes, my new S4 is a great device, but every time I get (now my brother's) HOX into hands, I cannot avoid the sentiment, in still emotionally attached

Sent from my GT-I9505 using XDA Premium 4 mobile app

 

[3raser]

But yes, there are still people using older versions and they're satisfied with them!

I use CM10.1 because it is the most stable version. The list of known issues and problems posted for both 10.2 and 11 is holding me back to upgrade. Which is really bad in my opinion because 10.2 is out for a long time. I guess the HOX doesn't have the developer support it needs any more. People are switching devices too fast. I guess the best device upgrade would be a Nexus. It has great support and there only a few models instead of HTC who releases a new model every month.

 

[Thömy]

I use CM10.1 because it is the most stable version. The list of known issues and problems posted for both 10.2 and 11 is holding me back to upgrade. Which is really bad in my opinion because 10.2 is out for a long time. I guess the HOX doesn't have the developer support it needs any more. People are switching devices too fast. I guess the best device upgrade would be a Nexus. It has great support and there only a few models instead of HTC who releases a new model every month.

It looks like CM 10.1 was indeed a release with very few issues. Developer support is unfortunately very lacking . I simply don't have the time to work on all the reported issues. Often I don't have the necessary equipment (like docking stations) to reproduce the issue. But I slowly iron out issues that have accumulated after the CM 10.1 release. Some of which I'm also to blame .

 

[drivenby]

I use CM10.1 because it is the most stable version. The list of known issues and problems posted for both 10.2 and 11 is holding me back to upgrade. Which is really bad in my opinion because 10.2 is out for a long time. I guess the HOX doesn't have the developer support it needs any more. People are switching devices too fast. I guess the best device upgrade would be a Nexus. It has great support and there only a few models instead of HTC who releases a new model every month.

I disagree tbqh

Cm10.2 and to a lesser degree cm11 are both very stable.

The problem is if you only check out nightlies you are bound to run into some bugs.



Sent from my One X using Tapatalk

 

[vedko]

I use CM10.1 because it is the most stable version. The list of known issues and problems posted for both 10.2 and 11 is holding me back to upgrade. Which is really bad in my opinion because 10.2 is out for a long time. I guess the HOX doesn't have the developer support it needs any more. People are switching devices too fast. I guess the best device upgrade would be a Nexus. It has great support and there only a few models instead of HTC who releases a new model every month.

The problem is also the Tegra chip inside - this proved a dead-end road and there is close to none development for the platform, and it seems NVidia ditched it as well. Therefore, the contribution of Thömy and tbalden to HOX is simply priceless.

 

[Mr Fett]

Hey there,

Sorry for resurrecting an old thread but I'm just writing a blog entry about this exact problem with Android's roaming. Thousands of people complaining about it for years and yet still no fix.

You mentioned a manual fix for this - is there any chance you could break it down a little for the more technically challenged amongst us? I'm assuming it can't be done on a non-rooted device?

Thanks!

Bob

 

[vedko]

Hey there,

Sorry for resurrecting an old thread but I'm just writing a blog entry about this exact problem with Android's roaming. Thousands of people complaining about it for years and yet still no fix.

You mentioned a manual fix for this - is there any chance you could break it down a little for the more technically challenged amongst us? I'm assuming it can't be done on a non-rooted device?

Thanks!

Bob

What exactly do you mean with "roaming issue"?
Anyway, as for your second question: CM ROMs come rooted by default, so almost all "manual fixes" mean actually editing of system (text) files. And for that root is required.

PS Not sure how many people are still monitoring this thread. Everybody moved to CM11 or went for a new phone.

 

[paulow1978]

Cannot get the changes to stick

I am having exactly the same problem. One of our staff bought android scanners for our warehouse and they re not roaming properly even with the wireless roaming fix app as it crashes.

thought I would pursue this avenue. I have managed to configure the file and saved it then changed the permissions to read only. But on reboot of the device, it does not connect to the wireless automatically and asks for a password again. On entering the password it wipes out whatever is in my wpa_supplicant file.

I have double checked the syntax etc. I may have to try upgrading the device to lollipop though will probably brick it!!!

Ok just a new post here because the old one is getting quite long..

I think I may have cracked it. There is another file /data/misc/wifi/wpa_supplicant.conf.

When I add the bgscan line into there it parses the line upon starting wpa_supplicant because it throws an error when starting complaining this is not a global variable. So I added it manually to the network specific configuration area like so:

ctrl_interface=wlan0
driver_param=use_multi_chan_concurrent=1 use_p2p_group_interface=1
update_config=1
device_name=endeavoru
manufacturer=HTC
model_name=HTC One X
model_number=HTC One X
serial_number=SH34BW101272
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
disassoc_low_ack=1
p2p_go_max_inactivity=60
p2p_go_ht40=1
p2p_multi_chan=1
concurrent_sched_scan=1
autoscan=periodic:30

network={
	ssid="Mobile-Wireless"
	psk="<VERYSECRETPASSWORD"
	key_mgmt=WPA-PSK
	priority=2
	bgscan="simple:20:-30:20"
}

Bottom line under network configuration bgscan="simple:20:-30:20". Beware this is a very bad setting because it implies now:

Do background scans when the signal gets lower than -30db (so almost continuously, this was on purpose for my testing)
Then rescan every 20 seconds, and I believe the second 20 value is the scan interval when the signal is good.

Despite being a bad value'd test setup.

IT WORKSSS!!!

I can see it re scanning every 20 seconds and considering the roaming candidates. WHOOHOO.

I'm not sure how to put a line in that file from source because it's maintained on the fly I guess because the network is added to it when you connect to it and provide the key. So someone has to make a change in the code that appends lines in that file upon connecting to an unknown network and saving it in there.

In case anyone goes working on this; a sensible config like would be:

bgscan="simple:30:-65:300"

So don't bgscan unless the signal gets worse than -65db and then once every 30 seconds.
When the signal is good do it every 300 seconds.

:victory::victory::victory::victory::victory:

So now all we need is a developer who can change whatever code that generates that /data/misc/wifi/wpa_supplicant.conf to include an extra line per network that gets added. That should resolve the issue. Again, I have no dev skills so I'm kindly asking someone to have a look at this.

So until this gets merged we actually have a manual fix.. ADB pull the file, put the line in the network section. Push it back and fix the permissions and ownership. Then reboot or wpa_cli reconfigure.

Re-testing now on the stock CM10.2 20131002 nightly to see if it works without the CONFIG_BGSCAN=y

 

[IllUMINATUz]

nice work mate keeping the development alive..
I've moved on to One +, but HTC is still alive with my mom playing youtube videos only..
I'm not active as before, but I'm following.
Thank you