So I have a question. The hardware of the One S supports BT4.0 w/BLE. In the world pre-4.4 (or was it 4.3) each manufacturer had there own implementation of BLE(if you can't use an "always syncing" fitbit on a device this is likely the reason), Google consolidated it to a standard api (or at least this is what I've been reading), What does that mean for the One S on CM11, do I still support BLE? Which one, the google version or the pre-google version?
This question is speculative, all the "facts" I've listed above maybe wrong... I'm just laying out what I think I know.
My understanding is that they replaced the bluetooth stack in JB (4.2?) which broke a bunch of stuff including BLE. 4.3 mostly fixed it and brought BLE back. I believe we are using the straight AOSP bluetooth stack which should have working BLE...maybe go to a store and try out your device before buying?
EDIT...this article seems to match my recollection
I actually haven't had one in a week or more...
Was running very smoothly yesterday evening. After a night of charging, BSODs all the way...
Although, I nailed it down. It's all about the lockscreen:
1. Wake-up on portrait > fine
2. Wake-up on landscape > BSOD
3. Wake-up on portrait + rotate > Freeze
I could reproduce that consistently in a dozen of experiment this morning.
Maybe I should have started by this: all the BSOD / freeze occurs on wake-up / Lock screen rotation... Never during normal usage.
Have to go back to 19/01. :crying:
@intervigil: is it known bug or something ?
EDIT: I uninstall Apex Launcher just in case, but issue still here.
Me either, with Nova or GEL. Does it do it with no lockscreen or with the swipe lockscreen?
With no Lockscreen, it's all fine, rock-stable !
If I put any lockscreen, it fails, following exactly what I mentionned earlier.
EDIT: and by the way, it just doesn't happen on 19/01. So I'd say it's more a ROM problem... but that's strange that I'd be the only one affect ?
Yeah...it's just you then I guess you could pull a log while this is occurring and maybe Intervigil can give you a better idea what's going on.
So, as a workaround I built myself a kernel with accessory detection disabled. I can boot the zImage just fine, but i can't flash it with fastboot flash zimage (permission denied)
I also tried to build a boot.img, using the current nightly as a base for unmkbootimg and mkbootimg
mkbootimg --kernel arc/arm/boot/zImage --ramdisk initramfs.cpio.gz --base 0x80400000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom' -o new_boot.img
unfortunately, this just leads to a boot loop any advice?
unfortunately I don't have much time currently, so i'm still using the old kernel myself. Is there any reason you upgraded the kernel as well? Because otherwise you can simply flash the old kernel over the new CM build. It should work just fine.I really liked that kernel as it didn't crash apps in foreground (e.g. Ingress) every time the phone was plugged into or removed from car dock. I'm now back to stock kernel due to flashing a recent nightly and I miss that very much. Any chance to get this issue solved? @eabinsan @intervigil
unfortunately I don't have much time currently, so i'm still using the old kernel myself. Is there any reason you upgraded the kernel as well? Because otherwise you can simply flash the old kernel over the new CM build. It should work just fine.
Not sure I said that exactly, but I think that support for our device is definitely a low priority since our maintainer was hired by CM and likely spends most of his time on tasks that bring in revenue. As it stands now, it doesn't seem we will ever get a stable release, so will be stuck here in xda purgatory complaining back and forth about the same things until we can afford to get a pure AOSP device and give up the crack flashing life.