yashsingh1/xdaforums huggingface dataset:
[HTC One S] anteevy:
Hi,

I've been using this ROM (candy5-beta.v0.8.2-20141212-OFFICIAL-ville-215.zip, S-ON, 2.15) for the last two weeks and really like it.

I only have one major problem: twice in this time, my phone suddenly rebooted and after the reboot my mobile network didn't work anymore. The only way to fix it is to clear the Dalvik cache, normal reboot or cache clearing does not work. Any idea how I could track why it is rebooting (log files?) or a faster way to get the mobile network back running (rebooting after clearing the Dalvik cache takes 15min or something...)? The first reboot was during browsing through the Play Store and the second one while playing Desert Golfing, so it seems random.

Thanks (and great work)!
[HTC One S] Rapier:
It would be useful to take logcat and last_kmsg for reboots. There is a thread called something like "How to properly report bugs" or something like that on XDA. I'm on mobile now so I can't provide you a link but a quick search on google or on XDA will show you several threads with instructions how to do that.

On the other hand, my guess is that those issues are not Candy 5 specific, they are general LP bugs due to poor memory management in LP. They mostly occur when using memory intensive apps like SwiftKey, Skype or games (as you had too)

I would also suggest you to upgrade to latest Candy (last is RC 0.9, you're 2 builds back) since it has new features and also it's updated to latest Android 5.0.2

Sent from nowhere over the air...
[HTC One S] anteevy:
Thanks for the fast reply. I can live with the reboots, but that the mobile internet (I just saw that I wrote "mobile network", but actually it's only the internet connection) isnt working after the reboot is the really annoying thing. Any ideas on that?
[HTC One S] Rapier:
You should check the APN in this case. I guess you're referring to the mobile data not being able to connect. I am on radio 1.15 (later ones proved to be worse for me) and I have no issues with mobile data.

Sent from nowhere over the air...
[HTC One S] anteevy:
The APN settings seem to be correct. And as I said, after clearing the Dalvik cache the internet works fine again (without changing the settings). The problem also only occurs after the crash/restart, so I guess something gets corrupted during the crashes that is rebuilt after clearing the Dalvik cache.... Manual restarting does not cause this problem.
[HTC One S] Rapier:
Does turning on/off airplane mode solve anything?

Sent from nowhere over the air...
[HTC One S] anteevy:
No, sadly not. Neither does a normal reboot, or deleting and recreating the APN settings.
[HTC One S] tennisparty:
My mobile data also does not work
[HTC One S] Borman2000:
Have the same issue with unavailable cellular network with 0.9.0 build.

Trying both dirty (just clean Dalvik and cache) and clean (after factory reset) flashing.

Went back to 0.8.3

hboot 2.16

radio 1.20
[HTC One S] Rapier:
Which hboot?

Sent from nowhere over the air...
[HTC One S] Borman2000:
Edited my post immediately after posting it but your answer was quicker... :)
[HTC One S] mooch530:
Just installed the 0.9 dark version and I like what you've done! Very good work. Mobile data is still working for me...I'm on hboot 2.15

Sent from my One S
[HTC One S] rc420head:
All thanks for dark goes to [MENTION=5020670]matthew0776[/MENTION] ,glad your enjoying the candy

CandyRoms Maintainer
[HTC One S] mongoosesRawesome:
Having the same issue here. Wondering if you tried any other radio? I'm also on 1.20.
[HTC One S] letsurock:
0.9, my touch LCD buttons won't turn off. Any idea why? And how to turn off? Icecode kernel. 2.15 hboot .
[HTC One S] Rapier:
I don't understand... What LCD buttons? And what do you mean by "turn off"?

Sent from nowhere over the air...
[HTC One S] grorg:
I think it means backlight of hardware buttons.
[HTC One S] Rapier:
But they are turning off....after 5 secs or so. There is BLN (he said he's using IceCode) that makes them blink if a notification come but that's blinking not permanently lit and it does turn of as soon as you check the notification. And that feature can be disabled via kernel tuning apps

Sent from nowhere over the air...
[HTC One S] letsurock:
Capacitive buttons. The illumination doesn't dim or turn off. Whole night it was on. Now, back to LS 27/12 build.

I use on screen touch buttons as my capacitive buttons are dead except the back light. I use Capacitive buttonsto turn off but, when I try to turn off in 0.9 Candy5. Permission denied, both for stock and IceCode kernel.

[IMG="Touch button"]http://www.extremetech.com/wp-content/uploads/2011/10/buttons2.jpg[/IMG]
[HTC One S] Rapier:
RC 0.9 came with Android 5.0.2 and with "enforcing" selinux permissions. You're using a third party app and I don't think it's ROM fault. LP is in early stages of development and thing are changing fast. App developers have to adapt quickly too if they want their apps to be compatible after each build or commit...and that's a hard task and not always possible. It looks to me more a permission rights management issue with the app than a ROM problem. It also could be something related to superuser app. You might try latest superSU if you haven't done that already. You might also wanna try an app that turns selinux from "enforcing" to "permissive"...I guess that's the problem here and why permission is denied for the app

Oh and it doesn't have anything to do with the kernel. Permissions are granted or denied regardless of the kernel used
[HTC One S] letsurock:
Thanks for the explanation. It was helpful.

It did work. After Changing to permissive, I could control the backlights of capacitive buttons.
[HTC One S] Rapier:
I was almost sure that was it. "enforcing" is more restrictive and some apps have problems aquiring root. Glad youve made it, was a pity not to benefit from the new Candy that has lots of changes

Sent from nowhere over the air...
[HTC One S] anteevy:
Now my mobile internet doesn't work anymore even without a crash restart. It just didn't turn on this morning after I had my phone in flight mode for the night... :( Not even clearing Dalvik cache works anymore.
[HTC One S] rc420head:
Hboot? Was it working before?

CandyRoms Maintainer
[HTC One S] anteevy:
I've posted my problem on one of the last few pages:

"I've been using this ROM (candy5-beta.v0.8.2-20141212-OFFICIAL-ville-215.zip, S-ON, 2.15) for the last two weeks and really like it.

I only have one major problem: twice in this time, my phone suddenly rebooted and after the reboot my mobile internet didn't work anymore. The only way to fix it is to clear the Dalvik cache, normal reboot or cache clearing does not work. (...)"

So yes, it was working most of the time and only today it suddenly stopped working, but even without a crash restart... I didn't do/change anything, just went into flight mode over the night (as I've done for the last few weeks without problems):
[HTC One S] urlyisis:
I've had a similar issue after updating to 0.90. I've tried dirty and clean flashing with the same result.

Once the phone boots and starts the setup wizard, it can't setup the cellular service and I am forced to skip it. Going back later, the phone is not recognizing that there is a SIM in the phone.

I have tried dark and normal 0.9.0.... HBOOT 2.16.

The only other thing I am adding is PA-GApps full modular.

* I've noticed that if I try to add the APN settings (which are all blank) I get "Access Point Name settings are not available for this user."

* If I try to go to mobile plan, it says to "Please insert SIM card and restart". I've tried removing and readding. Also, it works fine in 0.83.
[HTC One S] letsurock:
And I noticed it today that with permissive mode, I can focus in CAMERA. :D

Every I see patch coming up for CM for Enforcing..

http://review.cyanogenmod.org/#/c/83105/
[HTC One S] motabass:
Anyone of you ever tried Screen Mirroring? Doesn't work for me. Can't find Device.
[HTC One S] zieglercol:
I do understand this is beta, but still...

I'm getting random reboots, some days it is even more than 5 times, noticed that it is more frequent while charging.

Did not happen on stock ROM.

I'm on 2.15 and radio version 1.30.

Tried also stock kernel, but it did not resolve the issue.

Is this somewhat general you also are experiencing?
[HTC One S] Rapier:
It is a general issue on all LP ROMs related to memory handling. It is very much depending on the phone usage and what memory intensive apps everyone's using. There are also times when apps are getting killed without an apparent reason. This is mostly affecting devices with less than 2 GB RAM as ville. CM team is aware about the issue and there are also some Nexus 5 users reporting abnormal behavior so fortunately Google or CM might find a solution. Till then we have to live with that. That's the reason for which I have a KK nandroid backup at hand

Sent from nowhere over the air...
[HTC One S] zieglercol:
Ok, clear. Must set myself then to patience mode. As I adore the LP, don't want to downgrade :)
[HTC One S] isaakcu:
3g video call when the next
[HTC One S] rc420head:
Google has fixed memory leaks in next android version (5.0.3 or 5.1) but has set no release date yet. http://www.xda-developers.com/android/lollipop-memory-leak-fixed/

CandyRoms Maintainer
[HTC One S] mikronac.ns:
Fix for that doesn't solve app killing, memory leak is solved but app killing isn't.
[HTC One S] Darknites:
Ram filling up because of leak so you end up with apps getting closed.
[HTC One S] mikronac.ns:
That patch is merged to CM but it doesn't solve app killing... Maybe Google rewrited whole module... We will see soon...
[HTC One S] urlyisis:
Any ideas\movement on this issue? I've had to revert back to 0.83. I've also tried other ROM's like CM12 and Liquid Smooth ports which don't have this issue. It seems that it may be permissions related. See my notes below.
[HTC One S] mongoosesRawesome:
Yea happened to me too. Just running 0.83 was my solution.
[HTC One S] urlyisis:
Hopefully, the 0.9.1 release will fix the issue once available for the ville.

I'm currently running the SLIM ROM port version 0.91 without issues, but want to get back to Candy5.
[HTC One S] letsurock:
Candy5 stock. Still going strong.

Note : No calls done, more instant messaging and autosync 24x7. 0.9 dark UI.
[HTC One S] rc420head:
update is out, see op links for download (light and dark ui) and changelog
[HTC One S] letsurock:
Dark UI implemented in Dialer and Contacts?
[HTC One S] urlyisis:
Woot, back on Candy5. Cell service issue gone.
[HTC One S] rc420head:
No not yet

CandyRoms Maintainer
[HTC One S] Zoucz:
Guys, maybe it's a silly question but...

How can I turn on the navigation bar? I only found dimensions settings in the Candy Interface.

I really fell in love with this ROM and with LP in general by the way. Thank's for what you've done so far!
[HTC One S] rc420head:
Since ville has hw keys navigation bar doesn't show, I can make it show in future builds, then if users don't want navigation bar they can set size to Zero to remove it. There's also an app to add them https://play.google.com/store/apps/details?id=com.mrbimc.udn.lite

CandyRoms Maintainer
[HTC One S] Zoucz:
You are really quick! Thanks.

I thoght it was like that. I don't usually use the navigation bar but sometimes the helicoptering is really pi**ing me off so I wanted to try it few times. I was just wondering now because I saw the screenshot with battery usage attached to one of the previous posts. (HERE)

I konw about the app I even tried it once. And since Xposed is not compatible with LP yet, this might be the only way.
[HTC One S] letsurock:
download buildprop editor, and add "qemu.hw.mainkeys=0"
[HTC One S] rc420head:
Lol forgot that trick, thanks

CandyRoms Maintainer
[HTC One S] Zoucz:
Great! I will try it.

Do you use it because of helicoptering? And are you guys even experiencing this issue?
[HTC One S] Darknites:
If I remember right that issue was some how related to radio and there not much you can do about it.
[HTC One S] Rapier:
It was related to the board/internal layout of the components (were causing some interference that made home button act abnormally) and it was solved by HTC in the devices build after August 2012 (or something like that...I don't remember the year exactly anymore). Only old build devices still suffers of this issue and even if there were some tries to solve the issue by software, it was never completely solved. Newer built devices don't have this issue
[X 2014 Q&A, Help & Troubleshooting] diego7308:
hi i have a problem i installed android L in my moto x 2014 1097 , but i want to install also root and i follow a tutorial for kitkat then when mi phone restart gets stuck on the motorola logo showing at the inception of the world appears with pure water and the M in the center of the world, and hence does nothing more, I can not enter recovery mode or mode factory, I hope you can help me greetings

:crying::crying::crying::crying::crying::crying::crying:
[X 2014 Q&A, Help & Troubleshooting] noircl:
can't enter recovery because it won't launch TWRP/Android stock recovery options/Android figure with red exclamation point or it really can't boot in any sort of recovery? Most probably you blew your recovery so you will have to flash it using fastboot and will need a virgin custom rom. Some users have already posted the links and procedures to do it in the forum, so proceed as they say and you'll be fine.
[X 2014 Q&A, Help & Troubleshooting] sebacbr24:
android l en xt1097??

como instalaste android l en un xt1097??instalaste el ota de la version 95 o 92??

por favor deja los enlaces de descarga

MOD EDIT

English translation added

as you installed an android l ?? xt1097 eet you installed the version 95 or 92 ??

please leave the download links
[G 2014 Android Development] Ashesh1708:
This tutorial is for those who can't wait for the official OTA and already unlocked their boot loader. This method actually fakes your firmware and enables support for the OTA as other countries like US has already released the Lollipop update for Moto G. I've updated my Moto G 2nd Gen to lollipop using this method.

Disclaimer

Unlocking boot loader voids your warranty and wipes everything from your internal memory. It's entirely possible to lose your phone by following this procedure. So I will not be held responsible for the possible outcomes.

Pre-requisites

*You must have an unlocked boot loader.

*This method is tried successfully on Moto G variants XT1068 (dual sim) and XT1069. Don’t try this on other variants.

*Backup your important data before proceeding.

*Download and install Motorola USB drivers from Here

Steps

Download the Tool [This is the minimal size] : Direct Download: (Fast!)bit.ly/moto55l OR Here or http://bit.ly/motoL5 oR NEW LINK http://bit.ly/moto5L OR http://bit.ly/MotoLL5

Extract it to a folder

Open Command Prompt by holding shift then right clicking in folder you extracted

Now run

updater.bat

Copy the file

update-nofsg-working.zip

to your internal storage.

Rename the file "CWM_Touch_Titan_V2.img " in the folder (on your PC) to "CWM_Touch_Titan_V2_2.img ".

Again boot your phone in boot loader mode and connect it to the computer. Open command window in the folder and run recovery.bat

In the bootloader menu, choose “Recovery” option. You will now enter into the Philz recovery. If it fails, repeat step 9.

In Philz recovery, choose install zip and select “update_nofsg.zip” file which you have copied in step 7.

Let it flash. It will take around 10 minutes to complete the flashing. After finishing, reboot the system and you’re done!

After installing "update_nofsg.zip" in Recovery there comes up the question if device should be rooted.

Tap on NO, reboot to Android L.

Rooting

Boot takes 10 minutes at least after rooting! (One time)

Make sure you have atleast Booted once in Andoid L

Copy the file

BETA-SuperSU-v2.19.zip

To your internal storage.

Reboot to fastboot then run

root.bat

It will reboot the phone.

Go to bootloader again and select Recovery

Intall

BETA-SuperSU-v2.19.zip

Reboot .. Rooted! (reboot will be ALOT longer than normal) wait at least 11/2 minutes, don’t be fooled by the time, I have been successful since the first attempt, but didn’t wait long enuff for the bootloader warning screen, and thought the device was locked up, and I would reflash KK and start over again, I done this at least five times, trying different procedures, trying to figure it out, but in reality, had it right the very first try..

If you are not rooted then again go to bootloader and run

root.bat

but don't flash SU again

Screenshots

Coming soon!

Confirmed Working Both Sims!

XDA:DevDB Information

MOTO G XT1068 Andoid L [ 5.0 ] updater + Rooter, Tool/Utility for the Moto G 2014

Contributors

Ashesh1708

Version Information

Status: Stable

Current Stable Version: 1

Stable Release Date: 2014-12-07

Created 2014-12-07

Last Updated 2014-12-07
[G 2014 Android Development] k2wl:
two same threads????/ why????
[G 2014 Android Development] raj.parekh07:
Mirror The link please

DB having hiccups
[G 2014 Android Development] Ashesh1708:
Thanks, Links updated!
[G 2014 Android Development] Vappalika:
Phone info

Thanks for the work!

Phone screenshot of information you can give?

Thank you!
[G 2014 Android Development] premaru:
Noobie question:

After following the steps here, do we just update via OTA to Lollipop?

Also, can you confirm both the SIM cards work?
[G 2014 Android Development] Vappalika:
system info

What is the full version System?

Thank you!
[G 2014 Android Development] amritmalviya:
Sorry but i dont understand properly....i have to download any firmware or just i receive it OTA
[G 2014 Android Development] Ashesh1708:
Solution

You have to download my tool as a zip that will contain Android L rom then running the bat files accordingly will automatically install Android L on your XT1068
[G 2014 Android Development] amritmalviya:
But it is just 0kb and also unable to download plz help
[G 2014 Android Development] premaru:
I got through the steps until just before recovery.bat

I cannot get into recovery (Philz)

I get this error:

C:\Users\Windows\Downloads\Moto G Tool>recovery.bat

C:\Users\Windows\Downloads\Moto G Tool>mfastboot.exe flash recovery CWM_Touch_T

itan_V2_2.img

target max-sparse-size: 256MB

error: cannot load 'CWM_Touch_Titan_V2_2.img': No error
[G 2014 Android Development] Ashesh1708:
After you follow these steps you will automatically have AndroidL installed

This happens after you flash `update-nofsg-working.zip` In recovery
[G 2014 Android Development] Vappalika:
No screenshots

Screenshots do not work. :(((
[G 2014 Android Development] amritmalviya:
Can i flash it directly on xt1068 or i have to download another firmware

---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------

Drop box is giving error....
[G 2014 Android Development] premaru:
I cannot get into Philz recovery. Please help.

Also, the device is only showing one SIM now.

Please help me !
[G 2014 Android Development] GuestD0111:
This Android L update is the one ported from XT1064 or the one for XT1068 got from the TWRP backup of general section?

Thanks
[G 2014 Android Development] premaru:
How do I restore it back to stock please???
[G 2014 Android Development] amritmalviya:
Help i am unable to download tool
[G 2014 Android Development] Vappalika:
system versyon?

This version of the system?

[IMG="http://i.imgur.com/Azw0q2m.png"]http://i.imgur.com/Azw0q2m.png[/IMG]
[G 2014 Android Development] premaru:
OP

It would be nicer if you respond to questions, I'm here with a broken phone? :)

One more question:

****

In the bootloader menu, choose “Recovery” option. You will now enter into the Philz recovery. If it fails, repeat step 9.

****

Are you sure it's step 9?
[G 2014 Android Development] /\droid:
Can you select which sim to use when calling out?
[G 2014 Android Development] Ashesh1708:
Link updated!
[G 2014 Android Development] franovantOtto:
Finally Lollipop booted on my XT1069!! Thanks so much!

Just one thing ... step 6 does not work . To make it work you have to rename the file "CWM_Touch_Titan_V2.img " in "CWM_Touch_Titan_V2_2.img ".

Sorry for my bad english
[G 2014 Android Development] Ashesh1708:
I am trying my best . please wait
[G 2014 Android Development] Ashesh1708:
Post updated, do again from step 5
[G 2014 Android Development] Ashesh1708:
fixed

Post updated, redo from step 5
[G 2014 Android Development] bluepower:
First of all, thanks for the work :)

Second, is this Android L update is the one ported from XT1064 or the one for XT1068 got from the TWRP backup of general section.

Thanks
[G 2014 Android Development] Ashesh1708:
Links updated!
[G 2014 Android Development] Ashesh1708:
Ported from xt1064 :)
[G 2014 Android Development] bluepower:
Thanks. I finishing the process on my XT1068 ;)
[G 2014 Android Development] Ashesh1708:
Post updated, please refollow from step 6
[G 2014 Android Development] amritmalviya:
Sorry but why all people here upload files on mega...

I am still unable to download :(

I want lollipop
[G 2014 Android Development] Ashesh1708:
Added mirror link! :)
[G 2014 Android Development] amritmalviya:
Again it 0kb download completed but unable to open :( :( :(
[G 2014 Android Development] ngydna:
bootloop after root =/
[G 2014 Android Development] Masinho:
Bootloop

Me2
[G 2014 Android Development] amritmalviya:
How do u download it?

Moto g2 (xt1068)
[G 2014 Android Development] Ashesh1708:
It also happened to me

Make sure

First you flashed boot then flashed su then again flashed boot
[G 2014 Android Development] ngydna:
i think the problem is that it doesn't flash boot.img so it gives bootloop error
[G 2014 Android Development] Masinho:
i think the same...

give error when trying to install root.bat
[G 2014 Android Development] Ashesh1708:
Added Google drive link! Finally :)
[G 2014 Android Development] /\droid:
When trying to execute root.bat I get the following error on the phone: "Mismatched partition size (boot)"

Any advice?
[G 2014 Android Development] Ashesh1708:
Try http://xdaforums.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1064-restore-t2957167
[G 2014 Android Development] premaru:
Thank you, all done finally. It was the renaming of the recovery file that was causing the issue.

I did see a few crashes but once I did a full reset in lollipop, everything is working fine including 2 SIM's and mobile data etc.
[G 2014 Android Development] Ashesh1708:
Just run root.bat then igore that error message then select recovery from bootloader mode, Be sure that you Rename the file "CWM_Touch_Titan_V2.img " in the folder (on your PC) to "CWM_Touch_Titan_V2_2.img ".
[G 2014 Android Development] Ashesh1708:
Happy to see it Working :)

Don't forget to hit a thanks on http://xdaforums.com/showpost.php?p=57313405&postcount=1
[G 2014 Android Development] premaru:
Done , I have Lollipop now thanks to you :) Also to be fair to the other member, I fixed the issue due to this post and give full credit to him:

http://xdaforums.com/showpost.php?p=57322728&postcount=23

---------- Post added at 06:45 PM ---------- Previous post was at 06:41 PM ----------

Please can someone tell me, how can I flash stock recovery on this and remove Philz recovery?

Also, will I receive future OTA directly from Motorola or do I need to come back to this thread to get updates?
[G 2014 Android Development] Masinho:
mee2
[G 2014 Android Development] nitsos:
root method don't work ....bootloader screen looping !:(
[G 2014 Android Development] /\droid:
I think I got it!

After installing "update_nofsg.zip" in Recovery there comes up the question if device should be rooted.

Tap on no, reboot to Android L and then continue with the regular rooting manual from OT.

Run root.bat ignore the error message and then install "BETA-SuperSU-v2.19.zip"

My device is now running Android L and is rooted!
[G 2014 Android Development] ngydna:
i already ignored the error message twice, it's still stuck in a bootloop after flashing su
[G 2014 Android Development] nitsos:
solved: you have to copy the BETA-SuperSU-v2.19 to internal memory ,not external :)

Works for me
[G 2014 Android Development] Vappalika:
Version?

Hello!

What is the full version System?

Thank you!

This version of the system?