yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] squid2:
Okay Raghav, I've made a TWRP flashable zip of the old kernel used in the May 16 and May 29 builds.

Could you try the following:

Install the latest June 12 build and verify that the WiFi disconnect on deep sleep issue returns

Flash the follwing kernel on the June 12th build and check if the issue goes away: http://www.mediafire.com/download/vo2p7mcc3g6ugj7/otus_kernel_may14.zip

If you want to be extra sure, try reflashing the full June 12th build (with the June 12th kernel) and verify that the issue returns

Dirty flashing should be fine. I just want to verify that the June 6th kernel changes are the culprit. Since this issue does not happen on my device, it's difficult for me to debug myself.

Is anyone else having this WiFi disconnection on deep sleep issue? Indian users? Non-indian users?
[E 2015 Original Android Development] raghavarora1997:
Flashing that kernel solved that problem, now WiFi won't disconnect on deep sleep.
[E 2015 Original Android Development] squid2:
Alright, I guess that the June 6th kernel changes were causing the issue for you then.

I looked through the changes I made on June 6th and couldn't spot any obvious or even likely culprits. WiFi has been working fine for me, so I'll leave the kernel as is unless others start reporting the same problem. You can always reflash the old kernel I posted after installing new builds.

Others: Please do say so if you are encountering this issue with WiFi disconnecting when the phone goes to sleep.
[E 2015 Original Android Development] squid2:
I made a few changes to audio offload settings in system.prop that seem to have significantly reduced ADSP crash frequency. With these changes, YouTube is now mostly usable (it crashed after around 30 minutes of video playback when I tried). The next build (on Friday or Saturday) will include these changes. Impatient users can modify their build.prop to match the linked commit and reboot.

EDIT: Meh, it still seems a bit flaky, but it does seem to be better than before. There are some other things I'll look into this weekend when I find time.
[E 2015 Original Android Development] aliennastik:
can u plz fix the recent key crashing functions?
[E 2015 Original Android Development] SpiralX15:
I'm not able to install WhatsApp on this. I enter my number and click on OK to verify but nothing happens.
[E 2015 Original Android Development] squid2:
Hmm, I don't use WhatsApp myself. Could you post a logcat of when WhatsApp misbehaves?
[E 2015 Original Android Development] SpiralX15:
The OK Button for verifying the number is the only thing that doesn't work.
[E 2015 Original Android Development] Krizthian:
[MENTION=6485916]squid2[/MENTION]

You tried to use a other camera app for fix the camera issue?, for example: Google Camera, or other.

Greatings.
[E 2015 Original Android Development] squid2:
The camera bug only happens once in a while and reopening the app fixes it, so I haven't bothered trying anything else.
[E 2015 Original Android Development] squid2:
June 18th Release

I've posted a new build I made today. This build mostly fixes the YouTube ADSP crashes. It's not perfect though; I encountered a crash in testing when I pressed the home button while a video was playing. Pausing the video before pressing home seems to work reliably. Based off my observations in testing, I'd also suggest reflashing the latest CM gapps after installing this build.
[E 2015 Original Android Development] SpiralX15:
Have you fixed the recent key?
[E 2015 Original Android Development] aliennastik:
useless rom without recent key fix..
[E 2015 Original Android Development] squid2:
Complaining doesn't help anyone.
[E 2015 Original Android Development] Krizthian:
[MENTION=6485916]squid2[/MENTION]

You think the mistake of playing videos from Youtube can be caused simply by the only speaker?

Edit: Do you tried to use this mixer_paths?

https://github.com/Motorola-Cyanoge...b/cm-12.1/prebuilt/system/etc/mixer_paths.xml

Greetings.
[E 2015 Original Android Development] squid2:
I'm using the mixer_paths.xml from the otus stock ROM. The mixer_paths.xml you linked to is for surnia which uses a completely different chipsets. I don't quite understand what you meant by "caused simply by the only speaker." Could you elaborate?
[E 2015 Original Android Development] squid2:
June 19th Release

I've posted a new build today, with the latest CM updates and Linux 3.4.108 (that was just released today actually). The dowload is up on the first post. The YouTube ADSP crash frequency is now low enough to not be too big of an issue.

With regards to the gapps crashes (and recents key issue etc.) that Indian users are facing, I will take another look at the logs that I've been sent and see if I can do anything. Please try to understand that it is hard for me to debug because I cannot reproduce the issue on my device. If any knowledgeable Indian users with the device can look into the issues, it would be highly appreciated.
[E 2015 Original Android Development] PseudoDev:
This ROM is awesome!!!!

Almost bug free!

Gapps work for me....although I'm Indian

Recents screen works too

ROM is pretty stable.

Great Work!

What I did was wiped cache, dalvik cache, system and data. And then go to install, choose the cm and then choose "select another zip" and then chose the Gapps.

Then swipe to install. Maybe we have to make sure that both are queued with cm first and then gapps next. Maybe its possible that Indian users are flashing separately which is causing the problem
[E 2015 Original Android Development] aliennastik:
which version of gapps u install??

x86 or arm??
[E 2015 Original Android Development] PseudoDev:
arm ofcourse
[E 2015 Original Android Development] aliennastik:
gapps downloaded from first page???

or can u provide the link?

---------- Post added at 04:17 PM ---------- Previous post was at 03:43 PM ----------

recent key is not working....google play service fc error still there but play store working fine...
[E 2015 Original Android Development] PseudoDev:
Trust me.

Go to the recovery, wipe the dalvik cache, System, Data and cahce.

then go to install and do everthing exactly the way i have mentioned. DO NOT FLASH THE ZIPS SEPARATELY.

DO THEM ON QUEUE, FIRST THE ROM AND THEN THE GAPPS 5.1.

Sould work.

It worked for me.

DONT FORGET TO PRESS THE THANKS BUTTON!!!!
[E 2015 Original Android Development] Ravx:
No it doesnt i have tried this process many times. Though the version of gapps may have solved your problem. Can you tell which gapps version you installed. Post a link if possible
[E 2015 Original Android Development] PseudoDev:
I tried the arm version.

If that doesn't do, try 5.0 Gapps
[E 2015 Original Android Development] aliennastik:
paste the link of gapps u r using..
[E 2015 Original Android Development] PseudoDev:
. https://github.com/cgapps/vendor_google/raw/builds/arm/gapps-5.1-2015-06-02-15-19.zip

And yes, do login in the welcome screen. Don't skip that part for logging on later.
[E 2015 Original Android Development] PseudoDev:
I will try debugging the ROM.

Don't pressurize [MENTION=6485916]squid2[/MENTION] as he has done a lot for us already by porting the ROM for us fixing most of the bugs.

We didn't even have CM12.1

So i'm gonna go forward and try, although i cannot guarantee a 100% success rate.

But my exams are going on so i can start only after 2nd of july.

Thanks!
[E 2015 Original Android Development] SpiralX15:
I'm starting to get a clear idea that the gapps version might be affecting the working of recent key. I flashed without gapps and no error yet.

Sent from my Moto E2 XT1506.
[E 2015 Original Android Development] raghavarora1997:
I don't think that GApps is affecting the recent key issue, because I've flashed CM without GApps, and I'm still getting recent key issue on second reboot.
[E 2015 Original Android Development] squid2:
Interesting. Could you post a logcat of the recents key crashes with no gapps installed? I don't need a full logcat of everything, I just want to see the log messages that show up when you press the recents button and encounter a crash.

Also, has anyone tried the [MENTION=4493088]Shreps[/MENTION] PACman ROM for otus? Do the recents key crashes happen there too or only on CyanogenMod?
[E 2015 Original Android Development] raghavarora1997:
I've tried Pac-Rom also it's also showing the recent key error.
[E 2015 Original Android Development] squid2:
Okay, so it appears to be something very specific to this device. Could you post a logcat of the recents key crashing (showing just what happens when you press the recents button and not stuff that happens earlier). I have a few logs that users shared on older builds that show everything from bootup, but they are huge and I haven't been able to narrow down the crash. I want to isolate the issue causing the recents crash in the logs.
[E 2015 Original Android Development] raghavarora1997:
logcat

here's the logcat with just the recent key issue. I hope this helps you.
[E 2015 Original Android Development] squid2:
Thanks for the log. I see a ton of different things going on in there, such as LuckyPatcher crashing repeatedly and Amazon-related app crashes. The phone keeps a farirly large buffer of logged data that it spews in entirety when you do "adb logcat".. As a result, even though you ran logcat for only a short period, there are nearly 5000 lines of log entries, most of then probably unrelated to the recents key. I can guess that the relevant content is towards the end of the logs but since it's not hard to find out, I'd rather know exactly which log entries pop up when you press the recents key.

Sorry to bother you, but could you just run logcat with the output sent to your screen (just run adb logcat without piping output), and then copy paste the few new lines that show up on your terminal when you press the recents key and encounter a crash? It should just be a small amount of data (under 50 lines probably). For example, when I press the recents key on my (working) device, I get around 10 new lines of log entries showing up. Thanks for your help.
[E 2015 Original Android Development] raghavarora1997:
here are those lines that i got in logcat after pressing recent key.

E/AudioTrack( 751): AudioTrack::set : Exit

D/audio_hw_primary( 272): start_output_stream: enter: stream(0xb77a4a38)usecase(1: low-latency-playback) devices(0x2)

D/audio_hw_primary( 272): start_output_stream: enter: usecase(1: low-latency-playback) devices(0x2)

D/audio_hw_primary( 272): select_devices: out_snd_device(2: speaker) in_snd_device(0: )

W/msm8974_platform( 272): Codec backend bitwidth 16, samplerate 48000

D/hardware_info( 272): hw_info_append_hw_type : device_name = speaker

I/msm8974_platform( 272): platform_send_audio_calibration: sending audio calibration for snd_device(2) acdb_id(14)

D/audio_hw_primary( 272): select_devices: done

D/audio_hw_primary( 272): out_standby: enter: stream (0xb77a4a38) usecase(1: low-latency-playback)
[E 2015 Original Android Development] squid2:
Okay, I get the exact same log entries when I press the recents key. They dont indicate any crash. Did you encounter a crash when you pressed the recent button and the log showed the entries you pasted here?
[E 2015 Original Android Development] raghavarora1997:
Its not actually a crash, but on pressing recent key, nothing shows up, can't get the apps running in background, just the phone vibrates a little nothing else
[E 2015 Original Android Development] squid2:
Oh, I see. I did not know the nature of the bug. I thought SystemUI was crashing when you pressed the recents key or something like that. This certainly is a peculiar issue.
[E 2015 Original Android Development] squid2:
June 27 Release

I've posted a new build with the latest CyanogenMod updates. The download link is up on the first post.

Unfortunately, I haven't yet figured out what is causing the recents key to not work after the second reboot after installing this ROM on Indian phones. It works fine on XT1505 and XT1511 models, so I can't reproduce the issue, making it difficult to debug. The nature of the bug is quite strange, happening only on Indian devices and not leaving any messages in logcat when pressing recents. I will keep trying to track it down. In the interim, I'd suggest that Indian users avoid rebooting after installing the ROM and booting it the first time. I've also heard from users here that the recents key starts working again if you leave the phone alone for a few hours.
[E 2015 Original Android Development] Chiveta:
[MENTION=6485916]squid2[/MENTION] I have a moto e 2015 (4G) and when installing the pacman also failed me, the key home and recents, and I had to enter the recovery. formatting system, and install the rom again and solved ... hope it is resolved ..
[E 2015 Original Android Development] Ravx:
This is not the rom for 4g version. It's only for 3g. The 4g version is in another thread.
[E 2015 Original Android Development] PseudoDev:
Indeed strange. It doesnt seem to work in the "Retail EU" variant of the stock rom which is supposed to be the one the indians use.

I flashed another version, a Brazilian version, although my phone's network stopped working, the Gapps issue and the recents screen issue got fixed. Is there a way to get the network back?

This is a strang issue indeed. :rolleyes::rolleyes::eek::eek::eek:
[E 2015 Original Android Development] Chiveta:
-(Wipe) Advacend Wipe

-Select System (Swipe to Wipe)

-Install zip rom, (Again)

(it worked on my 4G version, try the 3G version! (I had the same problems.) And I resolved the problem)
[E 2015 Original Android Development] squid2:
July 1st Release

I've posted a new build with the latest CyanogenMod changes and updated f2fs drivers. Unfortunately, I noticed in my testing that YouTube has become very crashy again. I then found that the last (June 27) build also had YouTube ADSP crash issues. Reverting to the June 19th build fixed the YouTube crashes for me. Thus, for any user who wants YouTube to work properly, I suggest sticking to the old June 19th build for now.

In other news, some discussion with [MENTION=6101402]Barunes[/MENTION] has led me to believe that the gapps and recents key issues on the Indian model may be related to the modem software. He said that the gapps crashes and recents key issues went away when he tried running CyanogenMod after flashing XT1505 firmware on his device. Obviously the cellular modem didn't work when he did that, but it is an interesting finding.
[E 2015 Original Android Development] Shreps:
Hi there, for the gapps/recent key issue, if it's really modem related, an update of prop blobs (vendor) may do the trick !

Hope it helps giving idears ?

Envoyé de mon A1-840FHD en utilisant Tapatalk
[E 2015 Original Android Development] PseudoDev:
I didn't really find any problem in the dmesg.

Flashing NON-HLOS.Didn't help.

Should I try building cyanogen mod via source?

But thats gonna take up GBs of data and i dont really have a fast internet connection.

I even encountered a strange problem yesterday.

My battery got low so i activated the battery saver, the phone got crazy!

The windows closed automatically, Random apps opened up, Navigation bar stopped working

It automatically opened google, and started typin random letters itself.

I think we seriously need to build a custom kernel and incorporate the drivers propely.

Unfortunately, i couldnt take a logcat or dmesg.
[E 2015 Original Android Development] squid2:
Hmm, I wonder what you did when you when you had gotten rid of recents key issues after flashing the RETUGLB firmware and then flashing CyanogenMod afterwards. Maybe you didn't encounter crashes because you didn't reboot? Or did you actually reboot CM one or more times and still didn't encounter recents key issues? Sorry to bother you, but could you try reproducing what you did with flashing the RETUGLB firmware and then flashing CyanogenMod. I want to know if that actually did anything to stop the gapps crashes on CM, or if it was just a fluke.

With regards to the kernel, all the drivers are already in there and it is already built from source.
[E 2015 Original Android Development] PseudoDev:
I flashed the entire variant and got no issues even when I booted many times!

No issues. Simple.

That's all.

P.S : I even flashed the ROM manytimes .

Maybe there is some way of getting network enabled in the RETGLB variant?
[E 2015 Original Android Development] squid2:
Okay, so if I understand correctly:

- flashing the entire RETUGLB firmware and then flashing CM and TWRP made CM work reliably every time, but the modem didn't work (since it was incompatible)

- flashing just the XT1505 RETUGLB modem on XT1506 didn't fix anything, but it broke the modem (as expected)

Based on the above observations, it appears the modem is not the culprit, but something else in the stock firmware package is. Could you try flashing the full XT1505 RETUGLB firmware package, then flashing just NON-HLOS.bin (modem) from the XT1506 to fix the modem?
[E 2015 Original Android Development] PseudoDev:
Umm.....

The modem isn't broken...
[E 2015 Original Android Development] squid2:
Heh, so flashing the XT1505 modem didn't break it? That is strange. Are you sure you flashed the XT1505 modem?
[E 2015 Original Android Development] PseudoDev:
I flashed RETUGLB variant's NON-HLOS.

I dont know if its of xt1505.

Shall I send you the NON-HLOS file?
[E 2015 Original Android Development] squid2:
The RETUGLB variant is the XT1505. Maybe the modem firmware is interchangeable between XT1505 and XT1506. I'm now trying to think of why flashing the full XT1505 broke your modem, but flashing just the XT1505 modem software didn't break it.

What I think I know:

- The XT1505 stock ROM would cause the modem to not work on the XT1506 because it lacks dual sim support

- The full XT1505 stock firmware package consists of the system image, boot image, stock recovery image, bootloader image (contains multiple bootloaders and trust zone), and modem software

- Your test is suggesting that the modem software from the XT1505 works fine on XT1506

- installing TWRP and CyanogenMod after installing the stock XT1505 image will replace the system, boot, and recovery images

- You said that installing CyanogenMod after installing XT1505 firmware led to the modem still being broken, but it fixed the recents key issues

That only leaves the bootloader from XT1505 as the thing that fixed the recents key and broke the modem. It doesn't make much sense to me, but who knows?
[E 2015 Original Android Development] PseudoDev:
Bootloader and network???

Doesn't make sense to me.

If the modems are interchangeable, then why did my network cut off when I flashed xt1505 variant?
[E 2015 Original Android Development] squid2:
I don't know. That is why I am confused as to what is going on,
[E 2015 Original Android Development] squid2:
YouTube ADSP Issues

I tried to do some bisecting and testing to narrow down the cause of ADSP crashes returning. After a few hours of bisecting, building, and testing, I then found that I was unable to reproduce the ADSP crashes. Now YouTube works reliably for me on the latest July 1st build. I don't know why it was having issues when I tried last time. Maybe it was just a fluke.

Based off these results, I'd recommend using the latest builds again. However, if you do encounter frequent ADSP crashes while playing YouTube videos, try going back to the June 19th build.
[E 2015 Original Android Development] squid2:
July 3 Release

I've posted a new build that sets a few extra RIL configuration parameters suggested by [MENTION=6327301]raghavarora1997[/MENTION] for the XT1506. I've heard from some Indian users that the radio behaved a bit oddly at times; maybe these settings will fix something. Indian users in particular should try this build and report back if any changes in radio behaviour are noticeable. Maybe it might even have an impact on the recents key issue - it is such a weird bug that who knows what could be the culprit.
[E 2015 Original Android Development] raghavarora1997:
recents key issue is not fixed, however RIL became more reliable. Earlier on going in basement signal goes off and wont come back even when i come out. i had to deactivate and then reactivate the sim to get the network, now its not happening.
[E 2015 Original Android Development] Ravx:
Is the play services force close still happening? I mainly face two problems,i can live with recent key issue but i cannot sign into google plus .it becomes unusable amd i spends atleast 4 hours a day on it. Therefore this rom becomes unusable for me in current state. The other problem i face sometimes is that whatsapp stops responding when i verify my no. The rest is ok i guess and yes youtube also force closes every time.
[E 2015 Original Android Development] raghavarora1997:
I'm not using Gapps so I don't know anything about the play services FC, but whatsapp works fine for me, and on soft reboot the recent key doesn't break.
[E 2015 Original Android Development] aliennastik:
google play service fc in latest build also...can not sign in with google account...play store and other play services dependent products are not working...rom is still not usable...stick to stock version...neways thanks for squid2 for his efforts...
[E 2015 Original Android Development] Ravx:
For me everything else other than google plus and youtube is working. I can login into google. Play store also works perfectly.

---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------

Than what are you using to download apps?
[E 2015 Original Android Development] raghavarora1997:
Almighty Google.
[E 2015 Original Android Development] aliennastik:
blackmart and mobogenie but ryt now back to stock
[E 2015 Original Android Development] Carlos Arriaga:
good job. I'll be testing.
[E 2015 Original Android Development] Carlos Arriaga:
[MENTION=6485916]squid2[/MENTION] link is not workin july 3.
[E 2015 Original Android Development] magdeoz:
This working perfectly.
[E 2015 Original Android Development] Carlos Arriaga:
[MENTION=6485916]squid2[/MENTION]

great work. but the volume too low, relative to the stock ROM. sound notifications, is just, presendible by low volume. I will wait for future update. : D
[E 2015 Original Android Development] aliennastik:
guys recent key and gapps fc solved.....yeyeyeye
[E 2015 Original Android Development] squid2:
July 14 Release

I've posted a new build with the latest CyanogenMod updates. I haven't had time to track down and fix the root cause of the Indian time zone issues, but you can still use the workaround of changing the time zone to something west of GMT.

In case you are curious, I did a bit of experimenting with the time zone bug on the weekend. Installing a working TimeService.apk didn't fix anything, and neither did replacing time_daemon and libtime_genoff.so with known good binaries from other devices. The issue is thus probably not in one of these three binary blobs. I'll do some more investigation when I find time.
[E 2015 Original Android Development] Krizthian:
[MENTION=6485916]squid2[/MENTION]

In my crDroid build Youtube works perfectly:

http://xdaforums.com/moto-e-2015/orig-development/rom-crdroid-moto-e-2015-3gotus-awesome-t3152505

EDIT: I just suffered a crash on Youtube, this had not happened, but according comets error in the post this happens sometimes ...

Greatings.
[E 2015 Original Android Development] squid2:
Yeah, it happens once in a while. I don't know exactly what the cause is. It may well be a bug in the ADSP firmware that custom ROMs trigger but the stock ROM works around. I've fiddled with various settings and included various kernel patches that have reduced the crash frequency, but it still does happen sometimes.
[E 2015 Original Android Development] squid2:
July 16 Release

I've posted a new build that adds radio configuration for US market XT1511 models. Mobile data will now hopefully work on these devices.
[E 2015 Original Android Development] Ravx:
I am having problem with the YouTube app.

When I try to change video quality. The phone hangs and reboots. Also when you dismiss any video while its playing in small floating window. It hangs and the phone reboots.

Is there any workarround for this.