yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] Filz0r:
It's not surnia I'm talking, but the squid thread, he posted about that release on this thread, a bit of confusion by me too :p
[E 2015 Original Android Development] grofweg:
Xt1524 here and same issue on the sensors. Returned to the 0716 version.

AFAIK its surnia only by zip name.
[E 2015 Original Android Development] starkly_raving:
Has anyone looked into the provisioning/ network registration for the CDMA variants? [MENTION=5337314]CodyF86[/MENTION] hasn't responded so he must be busy so maybe [MENTION=4400604]Meticulus[/MENTION] could help us?
[E 2015 Original Android Development] Fedray:
Someone having this problem too?
[E 2015 Original Android Development] Humoxxx:
Does this ROM works for xt1527?
[E 2015 Original Android Development] grofweg:
Yes, well ... that's a difficult question if you don't read the first post ;)
[E 2015 Original Android Development] Humoxxx:
Oh im sorry! Missreaded
[E 2015 Original Android Development] grofweg:
;)

Just enjoy the ROM. I have problems with the latest build and sensors. The 0716 version is just fine.
[E 2015 Original Android Development] Humoxxx:
Yes, i have that bug too. CM12.1 08/08/2015 with squid kernel.

The rest is ok, i cant believe how smooth and stable this build is. Im amazed!

Sorry for my bad english :p

Thanks!
[E 2015 Original Android Development] Coodarah:
[MENTION=3445372]scritch007[/MENTION] - New Stagefright exploit - Thanks for taking care.

http://blog.exodusintel.com/2015/08/13/stagefright-mission-accomplished/

https://code.google.com/p/google-security-research/issues/detail?id=502
[E 2015 Original Android Development] matteo 06:
cm 12.1 build 14/08 wi-fi don't works
[E 2015 Original Android Development] jhona1234:
Can you help me to port the miui 6 or 7 from redmi 2 for xt1514?
[E 2015 Original Android Development] Hirsch2k:
I´m also having a few issues with the latest 0731 build:

- Sensors not working (I think this was mentioned)

- CPU hotplug not working, all 4 cores running all the time

- min CPU Freq. was at 800 MHz per Default (I don´t know if due to input boost or not).

- CPU-Z is reporting V7L Kernel, shouldn´t this be V8 since our CPU is? Does this mean we are running 32 Bit Android?

Especially the hotplug bug really drains the battery.
[E 2015 Original Android Development] squid2:
[MENTION=3445372]scritch007[/MENTION] you've been keeping busy lol

http://www.xda-developers.com/xda-external-link/rom-cyanogenmod-for-moto-g-3rd-gen/

---------- Post added at 01:06 PM ---------- Previous post was at 01:01 PM ----------

Sensors are an SELinux issue that scritch007 has been fixing. The default min CPU frequency and lack of hotplug are the same as stock, they are not bugs. Software for surnia is 32 bit instead of 64 since the limited RAM hampers performance on 64 bit.
[E 2015 Original Android Development] scritch007:
Sometime they do not read the inside of the posts and do not grant the credits to the correct person. And sometime they just read it too fast and grant it to the wrong person :).

Great work [MENTION=6485916]squid2[/MENTION]
[E 2015 Original Android Development] harshwardhan ghundare:
Does anyone have all in one tool for flashing twrp,root and for rom? Give me the download link thnks
[E 2015 Original Android Development] scritch007:
cm-12.1-20150817-UNOFFICIAL-surnia-38.zip

Fixed sensors.

CM 12.1 updates (This has the stagefright fixes)

Good news Next build will have fully working led notifications.
[E 2015 Original Android Development] pda1ey:
Great news about including the stagefright fix.

The moto e 2nd Gen doesn't have an led notification? At least my surnia UK model doesn't...
[E 2015 Original Android Development] scritch007:
Well it will, tomorrow.
[E 2015 Original Android Development] starkly_raving:
Any commits/fixes for CDMA? (Telephony provisioning)
[E 2015 Original Android Development] grofweg:
Dirty flashed 0817 but no wifi. Tried also with wiping dalvic cache and system, but unfortunately still no wifi on my XT1524.

Verstuurd vanaf mijn Transformer TF101 met Tapatalk
[E 2015 Original Android Development] dwane3:
1524,wifi is not working..
[E 2015 Original Android Development] prbassplayer:
He pushed wifi fix to kernel, so I imagine build soon.

Sent from my SlimRoms powered Galaxy Tab Pro 8.4
[E 2015 Original Android Development] dwane3:
build 39,obtaining ip adress,dhcp wifi is not working..?Please fix this.
[E 2015 Original Android Development] matteo 06:
1524,in cm 12.1 build 17/08 wifi works fine
[E 2015 Original Android Development] dwane3:
1524,wifi working,but only static ip mode,dhcp mode is not working..Please fix.
[E 2015 Original Android Development] grofweg:
For me wifi is working on the Surnia39 build! Thx.

- XT1524 -
[E 2015 Original Android Development] starkly_raving:
No WiFi for me on the XT1526 Surnia 39 build... Goes from "obtaining IP address" to "saved" on home or public WiFi. (With the included Kernel and squid's 7b Kernel.)
[E 2015 Original Android Development] EB20XY:
can you please upload a catlog ?
[E 2015 Original Android Development] DroidFreak32:
For me Wi-Fi works like a charm provided the signal is strong enough..only the boot up time has increased slightly. Not a problem tough. Pretty stable considering the Rom is still in alpha stage
[E 2015 Original Android Development] diafero:
WiFi is working here (xt1524). However, I can still crash the entire ROM by doing:

* In the settings, select Buttons - Navigation Ring

* Add "Toggle Torch" to the ring, and save the buttons

* Open the navigation ring and select the torch
[E 2015 Original Android Development] starkly_raving:
There's no led for the torch so that's probably whats causing that.
[E 2015 Original Android Development] diafero:
Sounds plausible :)

But then, the ROM should not offer the torch in the UI.
[E 2015 Original Android Development] Filz0r:
Hello I've just flashed the latest build over the old build from squid with his kernel, I've wiped only cache and davlik, before and after flashing the ROM and the latest squid kernel. And so far the only issue I've had is a random app shutdown every now and then...

Maybe it's because of the dirty flash, but I can't flash the ROM clean because I'd lose some app data that will be wiped away with the clean, will provide an other feedback after a few days.

Thanks a lot for your work so far!
[E 2015 Original Android Development] starkly_raving:
The WiFi issue is with the ROM (for those of us having it). I've found a fix that works perfectly...

Download this zip...

https://drive.google.com/file/d/0B46DbOH2IgChUGN1X1ZyRXczRUk/view?usp=docslist_api

Extract it with an archiving tool/file explorer. Copy the files from the extracted wlan/prima to root/etc/firmware/wlan/prima and set permissions to 0644(rw-r--r--).

Reboot and profit...
[E 2015 Original Android Development] diafero:
That's awesome :D thanks a lot for all your hard work!

Next build would be build 39, right? I still don't have LED notification. But then, I am using squid's kernel, not sure whether it's the ROM or the kernel that makes the LED work.

In case you didn't mean build 39 but build 40, consider me happy and patiently waiting :)

Speaking of which, is there any chance you could include the Qualcomm Baseband diagnosis driver in your kernel? With squid's kernel, SnoopSnitch <https://opensource.srlabs.de/projects/snoopsnitch> is working, but with your kernel, it complains about a lack of drivers.
[E 2015 Original Android Development] Filz0r:
This fixed my WiFi problems, thanks a lot for this fix!
[E 2015 Original Android Development] scritch007:
From which version did you take those files? I tried with my xt1524 and with the codeauroa qualcomm one but it doesn't seems to work. Maybe it will break for other version then yours, but I'll give it a try anyway
[E 2015 Original Android Development] diafero:
Did you recently add these drivers? I re-flashed the device back to your CM with your kernel, and SnoopSnitch still seems to work. I'm not sure whether the app is just confused and didn't notice that the kernel changed under its back, or whether you added the diagnosis driver to your ROM.
[E 2015 Original Android Development] rokban:
hi, just got a new xt1521 ,still not unlocked bootloader as I did not find anything stable for surnia yet, and stock 5.0.2 is doing quite okay so far, is this cm12.1 stable enough for daily use? I mostly need to use 4GLTE (at times hotspot) and decent battery life and Bluetooth(calls,sms etc are working fine I think). kindly advice! thanks in advance..

P.S: just noticed that Percy_g2 will be maintaining XT1521 !! (just like XT1022 :D) , so theres nothing to worry !!
[E 2015 Original Android Development] starkly_raving:
XT1526, a XT1524 user has reported success so hopefully this will be a good interim fix until you can bake it in. [emoji106]
[E 2015 Original Android Development] yelupic:
@starkly_raving - The XT1524 users stating a working wlan didn't mention if it's working with DHCP on their device?

@scritch007

I tested it again by using the original files from stock ROM (22.36.1.surnia_retde.retdeall.en.DE retde, Build LXI22.50-24.1) - The result has been the same error pattern ...

I see two things (just thinking loud ... being no expert):

1. /etc/firmware/wlan/prima/WCNSS_wlan_dictionary.dat

is a symlink to (pds)

/persist/WCNSS_wlan_dictionary.dat

(which maybe is device/SKU specific in its content)

2. There is a counterpart (router/AP) used by each of us which may also cause a different behaviour (are all XT1524 users having the issue?)

(Maybe squid's osprey code would be a nice, promising try?)
[E 2015 Original Android Development] starkly_raving:
DHCP is working on XT1526 I can't confirm any other model.
[E 2015 Original Android Development] diafero:
WiFi with DHCP is working fine on my xt1524 with just scritch's ROM, no extra patches or kernels. (Well, I installed X-Posed, but that shouldn't affect this, right?) It has been working since I first tried it (versions 20150716 and 20150817-39). Even eduraom is working, which is often more flaky than "normal" WiFi.

The LED is actually also working now :) (at least in the notifications settings dialogue). It seems that squid's kernel is still lacking some piece(s) for this.

So the only remaining actual issue for me is the one where the device doesn't connect to new WiFi when it is in stand-by, I have to wake it up first for it to notice the new WiFi in range.

EDIT: LED is working also with real notifications, but it seems to ignore the duration/period setting. I set duration to "very long", but it is still flashing as long as it did with "normal". Even a reboot does not help.
[E 2015 Original Android Development] dwane3:
On my 1524,wifi dhcp is not conected,obtained ip adress,all on the 39 version. (zyxel keneetic lite 2 model).
[E 2015 Original Android Development] starkly_raving:
I pulled the wlan files from my stock rooted ROM. You may want to restore your backup and pull your stock files from wlan and give them a try. Until the dev has a permanent unified fix.

---------- Post added at 10:06 AM ---------- Previous post was at 10:02 AM ----------

My only issue now is the 3G and the 000000 unregistered network. Other than that its pretty stable.

Radio Log:

https://drive.google.com/file/d/0B46DbOH2IgChY2loZ2k0S2lQV0k/view?usp=docslist_api
[E 2015 Original Android Development] Filz0r:
Hello I've been trying out the latest builds and so far it is running perfectly for exception of a few minor security bugs like smart lock not always recognizing my location and asking me my PIN when I'm home, and when the screen is locked if I swipe down the notification drawer and click on the AudioFX toggle I unlock my phone without the need of inserting the PIN. And for last I think that the speaker volume on max volume is kinda low compared to the stock ROM, which had an awesome sound quality.

And finaly, this is more of a personal taste and not a bug, I would love to see the stock CM camera app replaced by the stock Motorola camera app, and I can almost bet that a few more would like that.

For now that's it, thanks a lot for developing this ROM and for your hard work!
[E 2015 Original Android Development] dwane3:
scritch007,build cm-12.1-20150822-UNOFFICIAL-surnia-40 is perfect,wifi dhcp is working,but one time is bootloop restart when toggle wifi and low signal strength (drivers?).Thanks.May be squid2 is rebuild your new kernel with last drivers..
[E 2015 Original Android Development] yelupic:
Reporting for Nightly@2015-08-22/40

XT1524 (retde)

Test 1

Sideload-installed dirty over 39, caches wiped

I can confirm the mentioned reboot after toggling the already known wlan ON, static IP

There were 3 reboots in a row

Results test 1:

WLAN: OK - After deleting the known wlan and re-creating it with only the password provided, DHCP is working well

Sensors: OK

Headset/speaker: OK

Test 2

clean installed 40 after a full wipe (sensors firmware left upgraded)

no unconditionally reboot(s)

Results test 2:

WLAN: OK (DHCP and static IP)

Sensors: OK

Headset/speaker: OK

Test 3

Went back to stock, downgraded sensors firmware, full wiped, installed 40

no unconditionally reboot(s)

Results test 3:

WLAN: OK

Edit: Having an active wlan and switching Airplane mode ON (no SIM) while playing a mp3 music file with eleven results in a reboot.

Sensors:

- Orientation: not OK

- Proximity/Gestures: not OK

- Auto Brightness: not OK

Headset/speaker: not OK

Bluetooth: not OK - music stream drops every 4 secs.

___

bottom line:

40 seems to be a lucky number with the DHCP/W-LAN issue.

Installed over (update history 2015-07-16 > 2015-08-17/39 > 2015-08-22/40) also the sensors and the headset work.

Thank you for your time and knowledge @scritch007 & @squid2
[E 2015 Original Android Development] starkly_raving:
Logs for radio, events and main. Hopefully something of value can be found to get the provisioning squared away for the XT1526.

Logs:

https://drive.google.com/file/d/0B46DbOH2IgCheHF1RlpwTi01a1E/view?usp=docslist_api
[E 2015 Original Android Development] rokban:
Well, flashed cm12.1 22/08 ( was on stock) .then flashed squid2 kernel, anyway still proximity sensors are not working , apart from that things are quite decent. Any solution to this issue?
[E 2015 Original Android Development] yelupic:
@rokban

I get working sensors with this sequence:

stock rom (downgraded sensors firmware to original)

1. 2015-07-16 (clean install, upgrading sensors firmware automatically, booting into homescreen)

2. 2015-08-17/39 (dirty install = only cache wipes, booting into homescreen)

3. 2015-08-22/40 (dirty install = only cache wipes, booting into homescreen)

Maybe 2. can be omitted.
[E 2015 Original Android Development] starkly_raving:
This may also help with the "000000" issue...shows unknown after typing getprop to carrier... [MENTION=5337314]CodyF86[/MENTION] had an init script that set up the CDMA variant network and it was a simple fastboot command "fastboot OEM config carrier Sprint" ... Hopefully this will help.

Here's a link to his git and the init for falcon(motog)

https://github.com/codyf86/android_device_motorola_falcon/blob/cm-12.1/init/init_falcon.c
[E 2015 Original Android Development] rokban:
Anyway I hope next build will solve the issue...
[E 2015 Original Android Development] Filz0r:
If you set the SE Linux to permissive sensors will work, and I'm sending this on 39th build along with squid2 kernel, along with a fix found in previous post for the WiFi problems
[E 2015 Original Android Development] PriPhaze:
Hmm?? Im using last build of CM 12.1 with Squid Kernel r7c and everything is working flawlessly. In fact when i first flashed the rom as clean install .. there was a major battery drain, device was getting hot so easily with apps that i know .. are not that hard to run. I will keep testing it but right now im happy that some things i couldnt theme with the past CM Version are now themed without losing the speed of the rom.

Btw im using a XT1527
[E 2015 Original Android Development] rokban:
Well I had frequent reboots with squid r7c somehow, now using r7b since couple of hours or more ,absolutely fine !

---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------

I read somewhere that I'm Google play we don't have selinux changers anymore? So which app to try for that?
[E 2015 Original Android Development] dwane3:
r7b working fine,but LED notifications is not working..
[E 2015 Original Android Development] squid2:
Wifi Driver Reboots

The new WLAN drivers in scritch's August 22 release (Build 40) are the same as those in my r7c kernel and the osprey kernel. I haven't heard of any bootloop issues on osprey, and I haven't encountered any bootloops on Surnia with the driver either. However, some users here are reporting bootloops on Surnia with the new driver, both with my r7c kernel and with scritch's new build that uses the same driver.

I can't debug the issue because I can't reproduce it on my device. Could someone try to capture and post a last_kmsg after a bootloop? I know some less experienced users had difficulty trying to capture one. It's important that you set yourself up correctly to capture one. Before trying to induce a crash (I heard turning wifi on and off does that for affected users), make sure adb is fully configured (enabled, computer authorized). Once you succeed at triggering the crash, the other important thing is to capture a last_kmsg before it reboots again (if your device is boot looping). During the boot process, it takes a moment for the adb daemon to start. You won't be able to connect to adb till the daemon is running. However, you want to capture the log early enough before it crashes and reboots again. So you will have to capture it during just the right period. If you don't have enough experience timing your log captures, you can try just repeatedly calling "adb pull /prod/last_kmsg" during the boot up process until you successfully capture a log. Once it is captured, post the captured last_kmsg on something like pastebin and share a link here.

EDIT: I just realized that last_kmsg is not available on the surnia kernel; it's only set up on otus. I'll look into an alternate debugging method.

EDIT 2: I found that the last_kmsg functionality has been replaced by ramoops in the pstore filesystem on 3.10.x kernels for Android. I'll post instructions on how to capture logs with this newer mechanism once I figure out how to use it myself.
[E 2015 Original Android Development] PriPhaze:
http://xdaforums.com/showthread.php?t=2524485
[E 2015 Original Android Development] rokban:
Well just did what you told ,but still sensors are not working :(
[E 2015 Original Android Development] PriPhaze:
wow ok... ehm after reading your post i decided to turn off wifi and BANNG! Im in an endless bootloop. It just got to the point where it says it is Optimazing 2 Apps ( idk why .. it didnt appear before ) and then reboted and now it doesnt move from boot animation.. Im a noob taking logs! Aww

BTW i think it also happens when you uninstall and app
[E 2015 Original Android Development] yelupic:
DEVICE/ROM

XT1524, Build 40, SELinux: Strict, adb shell/pull gives no root without manual activation via "adb root" on my device

___

PREPARATION

WLAN ON & connected (DHCP)

SIM inserted, Airplane mode OFF

___

IN TERMINAL (@squid2 - there is no file "/prod/last_kmsg" to pull after a bootloop, used /proc/kmsg instead BEFORE bootloop)

adb root

adb shell cat /proc/kmsg

___

ON DEVICE

SWITCHING AIRPLANE MODE ON

___

OUTPUT

<6>[ 341.631979,1] wlan: disconnected

<6>[ 342.173337,1] wlan: unloading driver v3.8.20.23

<3>[ 342.173371,1] wlan: [1116:E :HDD] hdd_wlan_exit: 8021: Unregister IPv6 notifier

<3>[ 342.237372,0] wlan: [1116:E :HDD] hdd_wlan_exit: 8024: Unregister IPv4 notifier

<3>[ 342.829763,0] Fatal error on wcnss!

<3>[ 342.829790,0] wcnss subsystem failure reason: dog.c:1296:Dog bark timeout..

<6>[ 342.829805,0] subsys-restart: subsystem_restart_dev(): Restart sequence requested for wcnss, restart_level = SYSTEM.

<6>[ 342.829889,0] wcnss_notif_cb: wcnss notification event: 8

<6>[ 341.632002,0] wlan(0) 00:00:00:00:00:00 Standalone

<6>[ 342.829900,0] wcnss_pm_qos_add_request: add requestwcnss_pm_qos_update_request: update request 100

<3>[ 342.849114,0] PRONTO_PMU_SPARE 0200002e

<3>[ 342.849131,0] PRONTO_PMU_COM_CPU_CBCR 00000ff1

<3>[ 342.849139,0] PRONTO_PMU_COM_AHB_CBCR 00000ff1

<3>[ 342.849147,0] PRONTO_PMU_CFG 00400011

<3>[ 342.849154,0] PRONTO_PMU_COM_CSR 00000001

<3>[ 342.849161,0] PRONTO_PMU_SOFT_RESET 00000000

<3>[ 342.849169,0] PRONTO_SAW2_SPM_STS 0000301e

<3>[ 342.849176,0] PRONTO_PLL_STATUS 00030001

<3>[ 342.849183,0] PMU_CPU_CMD_RCGR 00000002

<3>[ 342.849191,0] PRONTO_PMU_COM_GDSCR a0222002

<3>[ 342.849200,0] A2XB_CFG_OFFSET 000003fd

<3>[ 342.849207,0] A2XB_INT_SRC_OFFSET 00000000

<3>[ 342.849215,0] A2XB_ERR_INFO_OFFSET 00000000

<3>[ 342.849222,0] CCU_CCPU_INVALID_ADDR 00000000

<3>[ 342.849230,0] CCU_CCPU_LAST_ADDR0 00288f08

<3>[ 342.849237,0] CCU_CCPU_LAST_ADDR1 00288f04

<3>[ 342.849245,0] CCU_CCPU_LAST_ADDR2 00288f00

<3>[ 342.849252,0] CCU_PRONTO_AOWBR_ERR_ADDR_OFFSET 00000000

<3>[ 342.849259,0] CCU_PRONTO_AOWBR_TIMEOUT_REG_OFFSET 00000000

<3>[ 342.849267,0] CCU_PRONTO_AOWBR_ERR_TIMEOUT_OFFSET 00000000

<3>[ 342.849274,0] CCU_PRONTO_A2AB_ERR_ADDR_OFFSET 00000000

<3>[ 342.849282,0] Read data FIFO testbus 01000002

<3>[ 342.849290,0] Command FIFO testbus 00200002

<3>[ 342.849299,0] Write data FIFO testbus 00400002

<3>[ 342.849306,0] AXIM SEL CFG0 testbus 80800000

<3>[ 342.849314,0] AXIM SEL CFG1 testbus 08200000

<3>[ 342.849323,0] CTRL SEL CFG0 testbus 03020000

<3>[ 342.849331,0] CTRL SEL CFG1 testbus 00060000

<3>[ 342.849339,0] PMU_WLAN_AHB_CBCR 80000ff1

___

DEVICE REBOOTING ...
[E 2015 Original Android Development] squid2:
Thanks, it looks like a watchdog is timing out in WCNSS (wlan subsystem). The watchdog trip triggers an IRQ which instructs the kernel to reboot the system.

On my device, it doesn't happen:

<6>[ 1320.257416,3] wlan: disconnected
<6>[ 1320.961008,2] wlan: unloading driver v3.8.20.23
<3>[ 1320.961109,2] wlan: [1690:E :HDD] hdd_wlan_exit: 8021: Unregister IPv6 notifier
<3>[ 1321.016006,2] wlan: [1690:E :HDD] hdd_wlan_exit: 8024: Unregister IPv4 notifier
<6>[ 1320.257443,1] wlan(0) 00:00:00:00:00:00 Standalone
<3>[ 1321.074879,1] wlan: [5366:E :WDA] Update channel list capability Not Supported
<3>[ 1321.138383,0] wlan: [397:E :CTL] WCTS_NotifyCallback: received SMD_EVENT_REOPEN_READY from SMD
<3>[ 1321.202592,0] wlan_logging_thread: Exiting the thread
<6>[ 1321.202615,0] wlan_logging_thread: Terminating
<6>[ 1321.202943,0] wlan_logging_sock_deactivate_svc: Deactivate wlan_logging svc
<6>[ 1321.365815,0] wlan: driver unloaded

Maybe a wlan firmware difference is to blame? I have the Canadian version of the XT1527.
[E 2015 Original Android Development] DroidFreak32:
Same problem here. But have you tried turning Wi-Fi off from inside the Wi-Fi menu in settings app? I can get it to toggle there without any issues! But it does take time to search for the networks.

-xt1521-
[E 2015 Original Android Development] dwane3:
But on the r7b no bootloops,why,drivers?
[E 2015 Original Android Development] squid2:
Yeah, I changed the WiFi driver between r7b and r7c.
[E 2015 Original Android Development] dwane3:
Any variants?May be very old drivers try?
[E 2015 Original Android Development] PeterPan6754:
hello,

i have a problem with the "usb pc connection", i had switch from MTP to PTP now it is fix on PTP and i cant change this option. it jumps back to PTP.

the only way i can change i musst aktivate the adb-debug modus, but when i disable adb-debugging then is the same problem with swithing the usb-connection modus.

has anyone the same problem ?
[E 2015 Original Android Development] JobSup:
Which Gapps are you using? Can we use the arm64 Gapps for 5.1 from opengapps.org?

Tried... TWRP didn't let me flash the arm64 Gapps. The arm opengapps could be flashed but the setup assistant didn't work. Guess I reflash and try different Gapps.
[E 2015 Original Android Development] diafero:
I see there's a version 40 now, is there a changelog for that anywhere?