Database Info

[Q] [solved] switched to (official) CM11 nighly, WLAN isn't really working

Hi there,
I have a little bit trouble to follow all infos in CM11 Experimental in "Galaxy S Relay 4G Android Development".
Maybe someone is gracious and help me out.
I was running CM10.2 (20131128) with CWM 6.0.3.5.
So I downloaded cm-11-20131208-NIGHTLY-apexqtmo.zip from cyanogenmod; installed the actual apexq_recovery-10.2.img, which I installed over Heimdall (Debian).
After that I booted the phone into CWM 6.0.3.7; wiped /cache; installed cm-11-20131208-NIGHTLY-apexqtmo.zip; installed gapps-kk-20131119.zip; rebooted to recovery and rebooted the phone. (like Nocturin nearly did it)
After that the phone did 2-3 reboots by its own and then everything was up. First impression of my GoLauncher was that some widgets have problems to load - I don't see that as a problem.
My biggest problem for now is that WLAN isn't working anymore. The button is kind of greyed out and not really working.
Maybe I jumped a little bit too high and dirty from my CM10.2 to CM11.
Android Version: 4.4.1
Baseband-Version: T699UVBMC5
Kernel-Version: 3.4.71-cyanogenmod-...
CPU: ARMv7 Processor rev 4 (v7l)
CyanogenMod version: 11-20131208-NIGHTLY-apexqtmo
So what did I missed to do? I appreciate any help to get my WIFI back to work.
Thanks in advance
EDIT: I tried the cm-11-20131203-EXPERIMENTAL-mmmmm....chocolate_selinuxon-apexqtmo-45.zip now.
Android version changed to 4.4 but Wifi is working again!
I don't know what are the differences between the releases from the CM11-Experimental thread and the official nighlies.
And there are some little things which are noticeable in my normal use and still not fixed but at this stage of an kitkat release I have to bow myself to the developers Great work guys!
I'm not sure if it's clever to switch from this version to the upcoming nighly 20131210.... maybe I give it a try - and fail?!
I'm still interested in an aswer of my question about missing something with that wifi problem under the nighly version (20131208).

[Q] Verizon S3 locks up every reboot on rooted 4.1.2 > 4.3

I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!

Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.

[Q] Cannot connect to camera for d2lte

I have 2 of the same phones (i747M with twrp 2.7.1 for d2att installed)
On one, everything worked flawlessly (the older one)
On the other, I had to talk to a developer of twrp to get twrp working...
Now I just realized that the camera app isn't working. It works fine when I restore to the touchwiz stock rom.
I tried wiping my entire device before installing the new stable build 6 rom for d2lte. I also tried flashing the weekly roms for that device on both phones
the result is the same: camera works fine on the older phone while on the newer one, it doesn't
Someone suggested that this might be a hardware issue.. Basically, the TWRP guys fixed my other problem by pulling the latest cyanogenmod build and compiling a recovery. -So I'm wondering if something can be done to make my camera work again on my new phone...
(Before all of this, I of course tried rebooting, closing other apps, clearing data, etc...)
Update: I tried flashing the latest cyanogenmod nightly (June 30) and the camera app worked, but I prefer slimrom
Another update: all the bug report shows when I reproduce the error is
Device: Slim-d2lte-4.4.4.build.6-OFFICIAL-5242
Kernel: 3.4.95-cyanogenmod-gd56ed95 [email protected] #1

[Q] Random Force reboots

Hey guys, I'm a pretty heavy tinkerer and I know that comes with some risk. But before I completely wipe and reflash everything I wanted to see if someone could help diagnose my problem.
I have a Nexus 5 and have been running MultiRom for a while. I currently have Paranoid Android and Android L dual booting. I was on the newest version of PA (4.6 BETA 1) but I just flashed back to a past backup so now I am on PA 4.4 (I think). I have been having random reboots for about a day and now I can't even get my phone to stay on longer than a few minutes. I just installed Xposed and a few Modules so I assumed those were giving me the trouble, but I uninstalled Xposed when I started having problems and that didn't help. Even my backed up ROM and my Android L won't work without rebooting. This leads me to believe its something deeper down than my ROM.
Before I clean off and reflash, is there any way I can diagnose or fix this issue?
Thanks a ton.

Phone intermittently Restarting, reverts to optomising apps weekly.

Device: SM-G920I
ROM name: Xtrestolite 3.2
ROM version and base: G20IDVU3EPC3
Build number: XtreStoLite Deo Mod v.3.2. DPD8
kernel version and its settings: Stock Kernel
Rooted
Problem:
Every now and then, my phone will just become non responsive and automatically restart on its' own. I have had this problem quite a lot on different versions of this ROM. I do not have Xposed installed as this would cause my device to constantly overheat and make the restarts worse. The restarts are intermittent and i have no way to diagnose the reason. At least once a week, it will restart and then the optimising screen apps come up (as if I had just flashed something). I do have lucky installed, but the problems occured before this. The restarst are more noticable when I use the app headspace, it's a meditation app so I will know that the phone restarts because the audio cuts out. Any help would be appreciated.