[ROM][OFFICIAL][Lollipop 5.1.1][otus] PAC-ROM LP-MR1 - E 2015 Original Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PAC-ROM is built with our own tweaks and options, including picks and features from the best ROMs out there!
Why choose among ROMs, when you have All-in-One !!
* By flashing this, you automatically void your warranty! *
* If your phone breaks, blows up or runs away from you, do not cry to us! *
* Do not ask for ETAs!! *​
* Download the ROM and GApps *
* Reboot to recovery *
* Wipe data/factory reset *
* Flash the ROM and then GApps *
* Reboot your phone *
* Enjoy *​
* Download the latest version *
* Reboot to recovery *
* Flash the ROM *
* Wipe both dalvik cache and cache *
* Reboot your phone *
* Enjoy the latest version of PAC-ROM *​
* Submit a bug report *
* Submit a patch *​
* None for now *​
* PAC-ROM Downloads *
* PAC-ROM Downloads (Shreps Host - Old Builds)
* GApps *​
* PAC-ROM Team *
* Cyanogen Team *
* AOKP Team *
* DirtyUnicorns *
* SlimRoms *
* Vanir *
* Omnirom *
* Special thanks to all our Build Bot Providers (see Contributors list for all names) *
* PAC Graphix Team - Graphics, logos and images (see Contributors list for all names) *
* And of course, thank you for your love and support! *​
Support us with these banners:
Help with server costs
​
XDA:DevDB Information
[ROM][OFFICIAL][Lollipop 5.1.1][otus] PAC-ROM LP-MR1, ROM for the Moto E 2015
Contributors
Shreps
Source Code: https://github.com/PAC-man/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked BL & TWRP
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-05-30
Last Updated 2015-10-12

---

Reserved

---

It works in xt1511 but sometimes does not detect headphones

---

Gergarciz said:
It works in xt1511 but sometimes does not detect headphones
Click to expand...
Click to collapse
Did you try to reboot the phone? Is it showing any gapps FC issue on reboot?

---

gapps issue
gapps fc issue with xt1506 indian version..recent key not working ..and gps

---

raghavarora1997 said:
Did you try to reboot the phone? Is it showing any gapps FC issue on reboot?
Click to expand...
Click to collapse
No FC issue and it's only when I start the phone with headphones connected

---

Gergarciz said:
No FC issue and it's only when I start the phone with headphones connected
Click to expand...
Click to collapse
The headphones not being detected when booting with them plugged in is a known issue. I haven't actually tried to fix it since it's very minor and trivial to work around (unplug and plug back in when rebooting with headphones plugged in). The issue might also be present in the stock ROM, but I'm not sure.

---

squid2 said:
The headphones not being detected when booting with them plugged in is a known issue. I haven't actually tried to fix it since it's very minor and trivial to work around (unplug and plug back in when rebooting with headphones plugged in). The issue might also be present in the stock ROM, but I'm not sure.
Click to expand...
Click to collapse
can u plz fix google play service fc and recent key function in indian version...thanks in advance

---

Hi,
A new build is online with :
- Device tree & Kernel updated with @squid2 commits
- PAC Repo updates

---

gapps fc issue with xt1056 indian version....

---

aliennastik said:
gapps fc issue with xt1056 indian version....
Click to expand...
Click to collapse
Are you aware that this kind of reply is useless ?
First I don't have the device variant you have, so can't reproduce/test.
Plus do you have a logcat ? a kmsg ?
What build are you using ?
Is this bug exists/is solved on the CM 12.1 build of @squid2 ?

---

Shreps said:
Are you aware that this kind of reply is useless ?
First I don't have the device variant you have, so can't reproduce/test.
Plus do you have a logcat ? a kmsg ?
What build are you using ?
Is this bug exists/is solved on the CM 12.1 build of @squid2 ?
Click to expand...
Click to collapse
Device Variant Moto E2 3g otus (Retail EU)
this variant is supposed to be the one indians are using.
and this Gapps FC issue and recents key not functional issue is experienced even on cm12.1 rom.
I just dont get what's the problem. When i flashed a different variant, the issues vanished but i lost my signal(Obviously).
What to do???
The logcat seems to be completely normal.

---

@Shreps I've been hearing of this issue for a while from users of the Indian variant of the (dual sim) XT1506. They've been saying that google play services has been crashing and the recents button not doing anything beyond running the vibrator motor. They say that it only happens after the second reboot (everything works fine on the first boot after installing the ROM).
The issue is unique to the XT1506, and possibly specific to the Indian variant of the XT1506. North and South American users have not reported any issues and say that it works fine. I have not encountered any such issues myself, since I have an XT1505 model.
I have looked at the logs several users have submitted from my CyanogenMod ROM. The logs are quite perplexing. The gapps crashes happen deep inside proprietary play services code and give a most cryptic error message at the root of the crash: "Must set times" Searching the internet has not yielded any other devices reporting a crash with a similar backtrace. The logs for the recents button are also perplexing. Many uses had submitted logcats of the recents button not working, and I was unable to spot anything that appeared relevant. I then asked users (like @Barunes) to try capturing just the new logcat entries that appear when the recents button is pressed. The log entries of just pressing the recents button on an Indian device with broken recents were exactly the same as pressing the recents button on my device that works properly.
This has been a tough issue to debug for me, since it can't be reproduced without an Indian device, and the logs have not been very helpful. One user @Manish_Sky says that he was able to fix the crashes by modifying his hosts file, but others have not had success with his method.
I'm hoping a knowledgeable user with an Indian device will be able to debug this. I suppose one can create a CM build with debug prints inserted in the recents button code, or possibly hook a debugger up to SystemUI. Maybe that will lead to something useful. I must admit that I am a low level systems and embedded software person, and know very little about what goes on in Android Java-land.
@Barunes You said "When i flashed a different variant, the issues vanished but i lost my signal(Obviously)."
I'm curious, what did you flash? Did you flash the XT1505 modem on your XT1506? If flashing an XT1505 modem on an XT1506 fixes the recents key, we have a very bizarre issue on our hands. Maybe I need to use different RIL blobs on the Indian model?

---

Thanks for the update status @squid2
About the recent key error, I think it's Kernel related. The hardware even is not catched or something like that.
Which means you will never see something in logcat, but only in kmsg.
Good luck with this guys :x

---

squid2 said:
@Shreps I've been hearing of this issue for a while from users of the Indian variant of the (dual sim) XT1506. They've been saying that google play services has been crashing and the recents button not doing anything beyond running the vibrator motor. They say that it only happens after the second reboot (everything works fine on the first boot after installing the ROM).
The issue is unique to the XT1506, and possibly specific to the Indian variant of the XT1506. North and South American users have not reported any issues and say that it works fine. I have not encountered any such issues myself, since I have an XT1505 model.
I have looked at the logs several users have submitted from my CyanogenMod ROM. The logs are quite perplexing. The gapps crashes happen deep inside proprietary play services code and give a most cryptic error message at the root of the crash: "Must set times" Searching the internet has not yielded any other devices reporting a crash with a similar backtrace. The logs for the recents button are also perplexing. Many uses had submitted logcats of the recents button not working, and I was unable to spot anything that appeared relevant. I then asked users (like @Barunes) to try capturing just the new logcat entries that appear when the recents button is pressed. The log entries of just pressing the recents button on an Indian device with broken recents were exactly the same as pressing the recents button on my device that works properly.
This has been a tough issue to debug for me, since it can't be reproduced without an Indian device, and the logs have not been very helpful. One user @Manish_Sky says that he was able to fix the crashes by modifying his hosts file, but others have not had success with his method.
I'm hoping a knowledgeable user with an Indian device will be able to debug this. I suppose one can create a CM build with debug prints inserted in the recents button code, or possibly hook a debugger up to SystemUI. Maybe that will lead to something useful. I must admit that I am a low level systems and embedded software person, and know very little about what goes on in Android Java-land.
@Barunes You said "When i flashed a different variant, the issues vanished but i lost my signal(Obviously)."
I'm curious, what did you flash? Did you flash the XT1505 modem on your XT1506? If flashing an XT1505 modem on an XT1506 fixes the recents key, we have a very bizarre issue on our hands. Maybe I need to use different RIL blobs on the Indian model?
Click to expand...
Click to collapse
The one i flashed was named something like this (OTUS_RETUGLB_5.0.2_LXC22.99-12_cid9_subsidy-DEFAULT_CFC.xml)
the one we use is (OTUS_RETEU_5.0.2_LXC22.99-12_cid9_subsidy-DEFAULT_CFC.xml).
I tried modding the system UI like a million times but with no sucess.
What to do?
What about the Gapps issue?
What do i do about that?

---

Barunes said:
The one i flashed was named something like this (OTUS_RETUGLB_5.0.2_LXC22.99-12_cid9_subsidy-DEFAULT_CFC.xml)
the one we use is (OTUS_RETEU_5.0.2_LXC22.99-12_cid9_subsidy-DEFAULT_CFC.xml).
I tried modding the system UI like a million times but with no sucess.
What to do?
What about the Gapps issue?
What do i do about that?
Click to expand...
Click to collapse
The RETUGLB variant is the XT1505 (that I have). Did you flash NON-HLOS.bin from XT1505? Did you flash CyanogenMod after flashing the XT1505 stock firmware?
Also, just in case this has something to do with the kernel as Shreps suggested, could you try taking a dmesg before and after pressing the recents key when it is broken and posting it?

---

squid2 said:
The RETUGLB variant is the XT1505 (that I have). Did you flash NON-HLOS.bin from XT1505? Did you flash CyanogenMod after flashing the XT1505 stock firmware?
Also, just in case this has something to do with the kernel as Shreps suggested, could you try taking a dmesg before and after pressing the recents key when it is broken and posting it?
Click to expand...
Click to collapse
Just a min......stay tuned
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
squid2 said:
The RETUGLB variant is the XT1505 (that I have). Did you flash NON-HLOS.bin from XT1505? Did you flash CyanogenMod after flashing the XT1505 stock firmware?
Also, just in case this has something to do with the kernel as Shreps suggested, could you try taking a dmesg before and after pressing the recents key when it is broken and posting it?
Click to expand...
Click to collapse
It says acess denied.
IDK why.
I have root acess enabled

---

Barunes said:
Just a min......stay tuned
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
It says acess denied.
IDK why.
I have root acess enabled
Click to expand...
Click to collapse
Try running "su" and then "dmesg".

---

squid2 said:
Try running "su" and then "dmesg".
Click to expand...
Click to collapse
Genius!!!

---

Barunes said:
Genius!!!
Click to expand...
Click to collapse
After pressing....