yashsingh1/xdaforums huggingface dataset:
[X Play Original Android Development] squid2:
Ah, I don't think the bootloader needs to match but the fsg likely does. Also be sure to erase modemst1 and modemst2 after reflashing the modem. I haven't looked at which firmware packagers are available, but if the retgb package is available, you can flash that in place of the reteu.

If a lot of people actually want to use their single sim devices as dual sim, then I'll have to look for an alternate approach figuring out which devices are dual and single sim. The usual methods of checking ro.boot.radio and the SKU don't work here because the values are the same for both kinds of XT1562. The only differentiating identifier I spotted was ro.boot.carrier (retgb and reteu are single sim, retasia dual sim). I might implement a mechanism to override the device type for people who want to flash modems from different regions.
[X Play Original Android Development] ephumuris:
Mine has been ENABLED and on automatic since I installed the rom yesterday morning. I still think it's to do with people messing with minimum CPU frequency... And with your other kernel there is a slight undervolt too... So even without changing minimum maybe it's a voltage issue...?

For me that is where the problem lies...

FWIW when I had screen freezes on PACMAN rom I think I may have adjusted minimum frequencies. Never had them otherwise.
[X Play Original Android Development] squid2:
Your first procedure (wipe system, data, dalvik, and cache, then flash ROM) is fine. Which recovery are you using? Sounds like you are using a broken old build. Try the last TWRP build I posted on the TWRP thread.
[X Play Original Android Development] sarxion:
Thank you for the quick reply Squid. Which TWRP thread are you talking about, this one?

http://xdaforums.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
[X Play Original Android Development] lehoule:
Amplify seems to be the problem for me. I got a black screen as soon as I started using amplify.

Maybe I blocked too many wakelocks... I'm testing them one by one.

I'm not the only one : http://xdaforums.com/showpost.php?p=63649788&postcount=51
[X Play Original Android Development] Davirus849:
I just flashed the Nov1 version and everything seems to be working perfectly
[X Play Original Android Development] squid2:
Yes, that thread. Use my latest (r4) build.
[X Play Original Android Development] Davirus849:
I just noticed thatI lost the ability to turn off the screen by double clicking the home button with the Nov1 release.
[X Play Original Android Development] squid2:
I'll look into the issues you mentioned when I get a chance. I don't have any 5 GHz routers to test with at home or at work though, so it may be a while before I get to the WiFi issue. One question: does 5 GHz WiFi work with my "Squid Kernel" on the stock ROM? This would help me identify whether it is a kernel or ROM issue.
[X Play Original Android Development] ephumuris:
OK so I went over 24 hours without a freeze so set out to reproduce one.

I set minimum CPU speed to 533... Didn't get a freeze but I didn't leave it for too long as I was busy texting etc. Before I went to sleep I wanted to cancel changes as I need my alarm. So in No Frills CPU I unticked set on boot and restarted...

Alarm went off OK this morning. Took phone off charge. Went back to it and screen was totally black. .

I'm thinking maybe it hadn't reset the CPU changes properly as this is the only change I had made. Live Display active through my whole testing.
[X Play Original Android Development] jellysheep:
Thanks! I'll try the stock ROM as soon as possible.

Btw, last nicht I got the first Screen of Death. Battery was about 17%, both CPU clusters with 200MHz minimal frequency. LiveDisplay ("night" mode) and Adaptive Brightness were on, Ambient Display was off. This was on the 10e kernel.
[X Play Original Android Development] ephumuris:
Again... Common factors modifying CPU values on stock kernel... Or CPU mods as well as the lower voltage of squid kernel.
[X Play Original Android Development] Lennyz1988:
I never had one single Screen of Death and I always use Livedisplay.
[X Play Original Android Development] eskamhl:
I think there's something weird with the management of this cpu and related governors, as you can see in the flollowing screenshots ( and I can swear it ) I didn't changed the min freq of the BIG cores but in the frequency table it seems to run at 400MHz sometimes ( mainly, but also other frequencies under 960MHz are used ).

When I first installed the 1 november build I had many SOD, I tried v10e kernel but with the same result. Then I used v10d for some time with no issues, but now that I want to reproduce the wake up problem I'm not able to do that even with the same v10e kernel used before. Maybe it could be related to some applications that keep the cpu somehow busy with the screen off in addition to the bad management of the cores :confused:
[X Play Original Android Development] ephumuris:
Good to have confirmation but pretty sure by now Live Display is not a contributing factor.
[X Play Original Android Development] squid2:
Yeah, I tried LiveDisplay and running down my battery last night (still on now) and still haven't had any SoD isssues. [MENTION=1399438]ephumuris[/MENTION] while reduced voltages are plausible, it doesn't explain why it happens on the stock CM kernel and doesn't happen on the Squid r10d kernel. I chose very conservative levels for the UV to ensure stability on all devices. Overall, I'm still not sure what's happening. Reducing CPU frequencies and interactions with the power HAL could be a factor.

Someone had submitted a pstore log a couple days ago that showed an intersting phenomenon of DRAM persistence and degradation. Based on the level of corruption (I've done research on memory persistence at work), that indicated that the CPU was dead for around 15-60 seconds before it was rebooted. Anyway, the logs were too difficult to interpret due to the corruption. If anyone else encounters a SoD issue, try force rebooting the device right away, then capture a /sys/fs/pstore log once it boots up.

One other thing you could try is removing the PowerHAL and seeing if that changes the behaviour. Try mounting /system as RW, and remove /system/lib/hw/power.default.so. Then reboot, and see if the SoD behaviour changes.
[X Play Original Android Development] ephumuris:
I wish I remembered to grab a log this morning after it froze. I'll maybe try again and grab the log just to have another one to reference against the one you have.

I agree if there are no voltage changes between D and E kernel of yours I'm probably off the mark with voltages but I'm not versed in dram persistence and degradation and I'm not fully aware of the commit changes between those two versions either.

Has ANYONE using the r10d kernel had the freezes?
[X Play Original Android Development] droider007:
Using r10d......none for me
[X Play Original Android Development] ephumuris:
Have you made any changes to stock CPU settings? As in lowered minimum CPU frequency? Or just flashed r10d and using it as is?
[X Play Original Android Development] jhaedee:
I'm using 24th October build with Squid Kernel r10d.

I've flashed moto camera and updated it and had no issues apart from it was occasionally slow to capture so i switched to the HTC Camera mentioned in a previous post and it's working fantastically.

I have been using this build since around the 24th and have had no crashes, force closes or anything else other than the occasional process freezing but it's not regular enough for me to care. I have connected to the 5ghz network at home for around a week now with no issues at all and 2.4ghz networks work just as well.

I have used live display for days at a time and had it turned off for days at a time and had no issues related to this.

Short of installing xposed the only modifications i have made are customizing the status bar icons, installing a theme, installing the 4g/Lte logo switcher and an root hiding app for my banking app. Other than that i haven't modified any CPU stuff.

Just wanted to thank Squid again for all his hard work. I was getting a bit down about the fact the Moto X Play seemed to be a bit clunky and that i'd missed my window to return it to amazon but your cyanogenmod rom and kernel has really brought it to life AND it's allowed me to get rid of the eyeball searing whiteness of Lollipop. I seriously can't thank you enough!!! :D
[X Play Original Android Development] polobunny:
Soft-reboot while playing MKX. Here's contents of /sys/fs/pstore (ramoops) + other logs I gathered.
[X Play Original Android Development] ephumuris:
Just realised my phone isn't connecting to works WiFi and that is indeed 5ghz too... I'll try squid kernel perhaps and test.

Works on the latest Squid Kernel so not sure what has changed on latest CM build...
[X Play Original Android Development] Davirus849:
I'm experiencing this strange camera crash that only happens when I enable the HDR function, this crash happened with Google Camera, Motorola Camera and Open Camera.

Here is the logcat

https://www.dropbox.com/s/r9qan7azvmqdxuw/Log_2015-11-06_15-10-43.txt?dl=0

As extra note, I enable the camera using the twist gesture, it seems there is less chance the camera crashes if I open it manually instead of using the gesture.

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] meisanerd:
I just tested my local 5GHz connection on the stock rom. I used both the stock kernel and squid kernel, and both of them worked just fine for me. I haven't yet tried with CM though, to see if it is a ROM issue.
[X Play Original Android Development] Davirus849:
Answering to my own problem, seems that switch from 21mp photos to 8mp fix the crash.

For me it's not a huge problem, it seem it's a problem with CM in general, no a bug for this specific rom.

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] squid2:
Thanks for the proper log. I've never encountered it myself and couldn't reproduce it, but I'll keep an eye out for it in case it ever happens on my device or for others.

The relevant portion of the log is:

11-06 15:10:12.882 354 29664 E QCamera2HWI: static void qcamera::QCamera2HardwareInterface::preview_stream_cb_routine(mm_camera_super_buf_t*, qcamera::QCameraStream*, void*): preview is not running, no need to process
11-06 15:10:18.232 29002 29713 E mm-camera: mct_bus_sof_thread_run: SOF freeze; Sending error message
11-06 15:10:18.232 29002 29713 E mm-camera: mct_bus_sof_thread_run: Force tombstone for debugging purposes.
11-06 15:10:18.232 29002 29713 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 29713 (mct_bus_thread)
11-06 15:10:18.373 348 348 I DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-06 15:10:18.373 348 348 I DEBUG : Build fingerprint: 'motorola/lux_retca/lux:5.1.1/LPD23.118-10/19:user/release-keys'
11-06 15:10:18.373 348 348 I DEBUG : Revision: '33472'
11-06 15:10:18.373 348 348 I DEBUG : ABI: 'arm'
11-06 15:10:18.381 348 348 I DEBUG : pid: 29002, tid: 29713, name: mct_bus_thread >>> /system/bin/mm-qcamera-daemon <<<
11-06 15:10:18.382 348 348 E DEBUG : AM write failure (32 / Broken pipe)
11-06 15:10:18.382 348 348 I DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-06 15:10:18.424 348 348 I DEBUG : r0 00000000 r1 00007411 r2 00000006 r3 00000000
11-06 15:10:18.425 348 348 I DEBUG : r4 a4e42dd8 r5 00000006 r6 00000000 r7 0000010c
11-06 15:10:18.425 348 348 I DEBUG : r8 000f4240 r9 a4e42d80 sl b7268f54 fp b6dddb8a
11-06 15:10:18.425 348 348 I DEBUG : ip 00007411 sp a4e42d20 lr b6f66d2d pc b6f8c93c cpsr 60000010
11-06 15:10:18.425 348 348 I DEBUG :
11-06 15:10:18.425 348 348 I DEBUG : backtrace:
11-06 15:10:18.425 348 348 I DEBUG : #00 pc 0003993c /system/lib/libc.so (tgkill+12)
11-06 15:10:18.426 348 348 I DEBUG : #01 pc 00013d29 /system/lib/libc.so (pthread_kill+52)
11-06 15:10:18.426 348 348 I DEBUG : #02 pc 00014a8b /system/lib/libc.so (raise+10)
11-06 15:10:18.426 348 348 I DEBUG : #03 pc 000110d5 /system/lib/libc.so (__libc_android_abort+36)
11-06 15:10:18.426 348 348 I DEBUG : #04 pc 0000f66c /system/lib/libc.so (abort+4)
11-06 15:10:18.426 348 348 I DEBUG : #05 pc 00002d99 /system/vendor/lib/liboemcamera.so
11-06 15:10:18.426 348 348 I DEBUG : #06 pc 00013513 /system/lib/libc.so (__pthread_start(void*)+30)
11-06 15:10:18.426 348 348 I DEBUG : #07 pc 0001143f /system/lib/libc.so (__start_thread+6)
[X Play Original Android Development] sarxion:
Where did you get the Motorola Camera app? I've been looking for it to no avail. Only info I've found is that apparently you need to flash it instead of installing it as an apk. Also, I haven't encountered that HDR camera crash, albeit taking HDR pictures in the Google Camera app does take a rather long time (2 secs average). Other than that, no issues of any kind
[X Play Original Android Development] Lennyz1988:
Is it not connecting or does it not see the wifi network at all?
[X Play Original Android Development] ephumuris:
Hi.

https://www.dropbox.com/s/2rboeewsg79ypan/MotoCamera442.zip?dl=0
[X Play Original Android Development] jellysheep:
Finding the network and authenticating works, but obtaining an IP address sometimes takes many seconds or does not work at all. When it tries the 2,4GHz band of the same router, obtaining an IP address always works instantly.
[X Play Original Android Development] ephumuris:
Doesn't obtain IP.
[X Play Original Android Development] squid2:
If you aren't running already, try flashing my "Squid Kernel" and see if it makes a difference. Most likely it's the revert I reverted to fix the WiFi keep awake issue in my office that's causing your trouble. I use different drivers in the two kernels to try to give options to people facing different kinds of issues.
[X Play Original Android Development] squid2:
November 7 Build

I've posted a new build with some minor changes. Apart from updates to CyanogenMod itself, I also included newer Adreno drivers from the Yu Yureka that seem to make the UI slightly smoother and slightly improve graphics benchmark results too.

EDIT: I might have uploaded the wrong build where autofocus is broken. If you encounter broken autofocus, flash my "Squid Kernel" to fix it.
[X Play Original Android Development] ephumuris:
You must have missed it i posted already mate flashed squid kernel. WiFi works on 5ghz with squid not with stock cm kernel.
[X Play Original Android Development] manan001:
Does this fix camera hdr freeze?
[X Play Original Android Development] Zobat:
I can confirm
[X Play Original Android Development] squid2:
Sorry, I hadn't read your earlier post properly. The behaviour makes sense then, the WiFi driver I'm bundling with the CM kernel solves the keep awake issue on some networks but breaks connecting to others. I'm providing both options so people can use the one that suits their needs.
[X Play Original Android Development] ephumuris:
Thanks I'll just stick to squid kernel for now as its working fine and CM rom is the best :)
[X Play Original Android Development] m2kk:
In the latest build torch causes a soft reboot.

D/CMActions-ChopChopSensor( 7092): chop chop triggered

E/AndroidRuntime( 6319): *** FATAL EXCEPTION IN SYSTEM PROCESS: TorchService

E/AndroidRuntime( 6319): java.lang.NumberFormatException: Invalid int: "null"

E/AndroidRuntime( 6319):	at java.lang.Integer.invalidInt(Integer.java:138)

E/AndroidRuntime( 6319):	at java.lang.Integer.parseInt(Integer.java:358)

E/AndroidRuntime( 6319):	at java.lang.Integer.parseInt(Integer.java:334)

E/AndroidRuntime( 6319):	at java.lang.Integer.valueOf(Integer.java:525)

E/AndroidRuntime( 6319):	at com.android.server.TorchService.startDevice(TorchService.java:326)

E/AndroidRuntime( 6319):	at com.android.server.TorchService.updateFlashlight(TorchService.java:386)

E/AndroidRuntime( 6319):	at com.android.server.TorchService.access$700(TorchService.java:59)

E/AndroidRuntime( 6319):	at com.android.server.TorchService$3.run(TorchService.java:455)

E/AndroidRuntime( 6319):	at android.os.Handler.handleCallback(Handler.java:739)

E/AndroidRuntime( 6319):	at android.os.Handler.dispatchMessage(Handler.java:95)

E/AndroidRuntime( 6319):	at android.os.Looper.loop(Looper.java:135)

E/AndroidRuntime( 6319):	at android.os.HandlerThread.run(HandlerThread.java:61)

W/DropBoxManagerService( 6319): Dropping: system_server_crash (837 > 0 bytes)

I/Process ( 6319): Sending signal. PID: 6319 SIG: 9

W/Sensors ( 7854): sensorservice died [0xb8429298]

W/Sensors ( 7092): sensorservice died [0xb83ebd80]

W/AudioFlinger( 6088): power manager service died !!!

W/AudioFlinger( 6088): power manager service died !!!
[X Play Original Android Development] squid2:
Are you using the stock kernel provided with the last build? I had accidentally uploaded the wrong build with a broken kernel, but the rest of the ROM is OK. Flash my "Squid Kernel" in the interim till I upload a new build with a proper kernel.
[X Play Original Android Development] m2kk:
I've been using the provided kernel with the CM builds. Although I used your squid kernel with stock.

Flashed 10e ontop of CM now and the torch works fine... I would say right away that the experience overall is much better. With the stock kernel the Nov 7 build felt quite sluggish.
[X Play Original Android Development] Davirus849:
Try opening the camera using the twist gesture, open it like 3 or 5 times, take 3 HDR photos each time, check if it crash.

Also, try it using the default 21mb photo size.

Enviado desde mi XT1563 mediante Tapatalk
[X Play Original Android Development] Zobat:
http://xdaforums.com/android/apps-games/app-motorola-camera-5-0-7-1-material-t3007246
[X Play Original Android Development] Davirus849:
Yup, there is where I got it.

Also this is the error I get after using the HDR mode
[X Play Original Android Development] Zobat:
Did you upgrade it in the market? I don't have this problem.
[X Play Original Android Development] Davirus849:
Yes, I got the Google Camera directly from the Google Play Store.

Even the Motorola Camera was downloaded from the store.

I did a factory restore from the Recovery and still experiencing those errors.

I may note that im using the build in kernel and that I only have this problem with 21mb photos, when I downgrade to 8 or lower, it works fine.
[X Play Original Android Development] Zobat:
Delete google camera, delete moto camera, reboot recovery, flash moto camera zip, clear cash, reboot, update moto camera, my 2 cents
[X Play Original Android Development] squid2:
I just tried taking 15 HDR photos following your described procedure (twist to launch camera, take 3 pictures, turn off) repeated 5 times. I didn't encounter any such crashes, but I'm running my "Squid Kernel". I suspect there might be a bug with the default CM kernel that I've been using for previous builds. Today, I rebased the CM kernel off a newer Motorola release for the Moto Maxx 2. I'll be releasing a new build with my new stock CM kernel tonight, and hopefully it will be more stable.
[X Play Original Android Development] Davirus849:
Just flashed your latest CM version and your latest Kernel, and the problem seems to be gone.
[X Play Original Android Development] Lennyz1988:
[MENTION=6485916]squid2[/MENTION] Do you think you will tackle the speakerphone bug in the future?
[X Play Original Android Development] droider007:
lets see if new kernel improves UI performance :fingers-crossed:

moto maxx 2 UI has zero stutters in videos and reviews......also any news on adding hotplugs and governers in your squid kernel?
[X Play Original Android Development] ephumuris:
He has posted in kernel thread that he will be going back to adding features now for his kernel. Good news all around.
[X Play Original Android Development] Zobat:
In his kernel this problem is fixed
[X Play Original Android Development] shanthasorooban:
What's the difference between Maax 2 and MXP? Both looks similar to me.
[X Play Original Android Development] squid2:
November 9 Release

This build introduces a new, completely redone default kernel for this ROM. It should be more stable than the previous one. It's based of the recent kernel release for the Moto Maxx 2. Here is a link to the new branch: https://github.com/sultanqasim/android_kernel_motorola_msm8916/tree/lux

[MENTION=1772208]Lennyz1988[/MENTION] The speakerphone seemed okay to me when I last tried it (no echo), but I may have been running a different kernel. Let me know if your echo problem persists on this new build. If it still misbehaves for you, I'll dig into it further, though digging into the Audio HAL will be a time consuming undertaking.
[X Play Original Android Development] squid2:
Cyanogen Recovery

Last night, something strange happened to my device and it would refuse to load TWRP. It would reach TWRP splash screen and then get stuck. While stuck, the CPU would be churning away as TWRP tries to allocate more and more memory, eventually getting killed by the kernel's OOM killer, and then retrying. I'm not sure what happened, but neither erasing ans reinstalling TWRP, not removing the /sdcard/TWRP folder, would make it work. Older versions were broken too. I don't know why this was happening, but I was stuck.

To overcome this roadblock, this morning I flashed the Cyanogen recovery (generated for free by the CM build process). It's very limited in functionality (being a decendant of CWM), but at least it's working. In case any of you ever get stuck in this situation, here is a build of Cyanogen recovery that you can flash: http://www.mediafire.com/download/155qon4vjhakk79/lux-cm-recovery.img

I still recommend TWRP for normal use since it has far more features and is easier to use. However, in case of emergencies, here is a simpler alternative you can fall back upon.
[X Play Original Android Development] rober788:
maybe i didn`t saw in earlyer messeges, but i want to ask if CM has support for dual sim (i have XT1562, bought from europe and using asia DS firmware).

Maybe is possible to add a flashable zip to add dual sim.
[X Play Original Android Development] droider007:
cm supports dual sim...
[X Play Original Android Development] squid2:
CM supports dual SIM. However, if you have a European single SIM that you converted to dual SIM with Asia firmware, this ROM will try to configure your device as single SIM unless you force it to dual SIM by editing the build.prop. See the single to dual SIM conversion thread for more details.
[X Play Original Android Development] rober788:
thanks, founded the link and i will share it if anyone is interested. ( http://xdaforums.com/showpost.php?p=63385239&postcount=6 )

Just to be sure what i have to do ... download the CM rom, open zip and modify build.prop adding text in that link.
[X Play Original Android Development] Lennyz1988:
I'll try to test it in my next calls. If the same problems still occurs, will it help to provide a logcat?
[X Play Original Android Development] LuizHenrique91:
I tested a voice call on speakerphone today and it worked as expected.
[X Play Original Android Development] pyr0sphere:
Clean flashed the Nov 9 release with built in kernel. Seems pretty smooth so far. Was coming from the Oct 1 release
[X Play Original Android Development] polobunny:
Very smooth, great job. You know I was telling you about reboots? I could never find out why they happened. Lately it was mostly app crashes whether on stock cm kernel or squid kernel. So far so good though! ☺
[X Play Original Android Development] LuizHenrique91:
The November 7 build is very smooth with the squid kernel. I will flash the Nov 9 soon, but I can see the need, because everything is working fine.
[X Play Original Android Development] Berlino:
Just clean flashed Nov 9th release and can't obtain an IP-address on 2,4/5GHz with baked-in cm stock kernel.
[X Play Original Android Development] Zobat:
Correct. Flash squids latest kernel to fix this issue
[X Play Original Android Development] Berlino:
[MENTION=3353780]Zobat[/MENTION]

I know that flashing squid kernel solves the issue, just wanted to mention the problem with stock kernel. :)

Edit: Flashing squid on top of latest release 9th doesn't help...the phone gets stuck in a bootloop (has to be the new cm stock kernel) - see my post in squid-kernel-thread: http://xdaforums.com/showpost.php?p=63753791&postcount=252