yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] troyekto:
Same problem here.

[MENTION=4173406]Kayant[/MENTION] links to daily builds on first post are missing.
[Moto G 4G Android Development] schrickz:
why don't you switched to cm 14.1, I guess that cm14 was skipped.

if the link missing, maybe it will be showing up on experimental build on cm downloads site soon, hopefully.
[Moto G 4G Android Development] Kayant:
Fixed was a formatting issue from editing from Tapatalk.

For parsing stuff try some things here - http://www.technicalnotes.org/fix-parse-error-in-android-there-is-a-problem-parsing-the-package/

Otherwise grab a logcat I read that would tell exactly what is wrong.
[Moto G 4G Android Development] mrLoma:
For who's interested;

Google camera works in cm14.1

GoogleCamera_4.1.006.126161292-41003493

Although sometimes when you switch between photos and videos the camera is strangely rotated 90° and stretched, but it's fixed by switching back and forth.

The newer one crashes on starting off the app after setting your permissions

4.2.022.135443920-41011413
[Moto G 4G Android Development] sevenrock:
Hi,

I am testing cm14.1 using this local manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project name="CyanogenMod/android_device_motorola_peregrine" path="device/motorola/peregrine" remote="github" revision="cm-14.1"/>
<project name="CyanogenMod/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-14.1"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1"/>
<project name="CyanogenMod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-14.1"/>
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-14.1"/>
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1"/>

</manifest>

and these patches:

python vendor/cm/build/tools/repopick.py \
167370 167456 167464 167473 167474 167484 167486 167490 167621 167634 167654 168364 168923 168929 168946 168947 168948 169214 169255
python vendor/cm/build/tools/repopick.py -t moto8226-sdcardfs

When using the app aarddict it fails to scan the sdcard for wikipedia files:

11-06 15:20:14.069 3742 3742 D itkach.aard2.SlobDescriptorList: beginUpdate
11-06 15:20:14.069 3742 3742 D itkach.aard2.SlobDescriptorList: endUpdate, changed? false
11-06 15:20:14.082 3827 3827 W Thread-9: type=1400 audit(0.0:38): avc: denied { read } for uid=10091 name="/" dev="rootfs" ino=1 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
11-06 15:20:14.084 3742 3827 D DictionaryFinder: starting dictionary discovery
11-06 15:20:14.084 3742 3827 D DictionaryFinder: Scanning /
11-06 15:20:14.089 3742 3827 D DictionaryFinder: dictionary discovery took 5
11-06 15:20:14.128 3742 3742 D itkach.aard2.SlobDescriptorList: beginUpdate
11-06 15:20:14.128 3742 3742 D itkach.aard2.SlobDescriptorList: endUpdate, changed? false

with a selinux-related error. How to fix it?

EDIT: Aarddict explicitly scans "/":

https://github.com/itkach/aard2-android/blob/master/src/itkach/aard2/DictionaryFinder.java#L39

RIght now I am trying to revert the rootfs-related changes in https://github.com/CyanogenMod/andr...40c4#diff-24173c425f4e76c041dede0c6e5fe8aaL75
[Moto G 4G Android Development] pofadda:
Most efficient set of GApps to install for this ROM?

I have been installing CM13 snapshot and nightlies for a few iterations and working out what subset of GApps Aroma will fill /system most usefully has always been hit-and-miss. What frustrates is that, in spite of 'optimising' the apks so that the chosen subset's sizes will just fit /system as per the numbers in the log.txts, the next iteration usually fails again until I shrink the subset a lot more. Yet cleverer people seem to get the directory jam-packed and slack free. What am I missing, please?

Repartition the phone? My knowledge of partitioning is limited to Windows fdisk and to gparted and space in the device seems pretty tightly packed so I suspect it would be a pretty pointless 'robbing-Peter-to-pay-Paul' situation anyway.

.

It did occur to me that this is probably a pointless exercise and I should leave /system unoptimised on the grounds that the updates will come thick and fast shortly thereafter and fill up the userspace anyway. Is this glum space-waste inevitable? There is little enough free space on my Peregrine as it is.

What is the wisest course, please?
[Moto G 4G Android Development] tpa-moto:
I think you should fix the app rather than change some SELinux policy. This behavior is wanted, the app shouldn't read "/". Why would an app such as that one need to read "/" anyway? If it's looking for some user created file, it can just use things such as getExternalStorageDirectory() or look into some standard paths. There's no need to scan the entire device.

PS: I think the commit you are looking for is cbf7ba18db3c607834d3f8d0745dae99f3e2a4ec in system/coresepolicy, but I could be wrong.
[Moto G 4G Android Development] Zyquil:
Welp. I got hit by the no sim problem and com.android.phone crashing by build 11-06 coming from build 11-04. Restoring did me no dice either as well as reinserting the sim card. Cba doing a clean wipe until in a few hours

If anyone has a solution without clean installing I'd gladly appreciate it :)
[Moto G 4G Android Development] matthias1976:
only old backup worked for me.

installing older zip wont work.

dirty flash from cm13 is working but dirty flash from cm14.1 not !?
[Moto G 4G Android Development] aha360:
Well, after doing a factory reset and installing the 20161106 UNOFFICIAL NIGHTLY ZIP, whilst the installation was successful, I now get app crashes (force close) on the stock/AOSP/Google Dialer and whenever I tried to place a phone call through the stock dialer or a third-party dialer app like ASUS Contacts/Dialer, the app does not present to you the in-call screen with options to end the call and so on, and therefore, I feel that any ZIP/ROM after 20161103 is deemed buggy.

Here's a logcat file for those who want to try and figure out what the problem is.
[Moto G 4G Android Development] khalmika:
Well, i'm going to upgrade from cm14 to 14.1... I read something about an upgrade that allow us to flash it without wiping data?

Can i do that? Or should I do it old school style? (Backup all with titanium, wipe, flash and restore) :)
[Moto G 4G Android Development] schrickz:
better to have a backup.

---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------

had this problem when I got both cm & Google dialer installed, try to disable cm dialer.
[Moto G 4G Android Development] aha360:
Problem is that even with the stock dialer disabled, I still have problems with calling people and receiving calls as there is no in-call UI/display whatsoever. I even tried to have just the AOSP dialer installed but that problem still exists.

Therefore, I reverted to the 20161103 install that I had backed up on my phone.
[Moto G 4G Android Development] khalmika:
i have a problem.. I actually dirty flashed 14.1 (2016/11/06) over 14.0 (2016/10/27) - I have a full backup of this last one - and SIM is not detected (and process com.android.phone FC)... what should I do? I'm about to wipe all data and try this out...
[Moto G 4G Android Development] sebaalbo98:
I was the same with version 04 and did a clean install and fix
[Moto G 4G Android Development] matthias1976:
after restore fullbackup still no sim ?

for me it worked with fullbackup
[Moto G 4G Android Development] khalmika:
Thank you!!! I just wiped data-cache and fixed!!
[Moto G 4G Android Development] aha360:
Don't bother - you'll end up not being able to call people and receive calls, even if you try your hardest to implement Android Custom ROM Safe Practices.

My advice: hold off until there's further updates with that problem fixed, though what you ultimately do after reading this is up to you - don't say I didn't warn you.
[Moto G 4G Android Development] Kayant:
Nah sure what's going on there will sim card stuff. As my phone doesn't have a working sim ATM j don't notice it :p. I would guess it may due to some changes not being fully merged in yet.
[Moto G 4G Android Development] Pupet_Master:
Hey Kayant, great choice of new phone btw, will you dev to the OnePlus 3 too? (as i'm about to buy one too, 399 dollars is a bargain)
[Moto G 4G Android Development] Zyquil:
Yep I tried a backup too bad I only had system backed up. Nasty habit of leaving out data when just dirty flashing. I'll make data backups via twrp next time.

Anything related to the sim will crash as far as I could tell. I ended up clean installing 14.1 11-03

CM Dialer isnt on the applist of 14.1 :confused:
[Moto G 4G Android Development] aha360:
The stock/AOSP dialer on the Moto G LTE for some reason is now updatable/linked to the Google Contacts/Dialer apps that are available on the Google Play Store, so no matter what you do, you are effectively screwed for now if you use any ZIP/ROM after 20161103 (correct as of the time of writing).
[Moto G 4G Android Development] schrickz:
checking on the change logs, a lot of stuff regarding phone being added, better wait for tomorrow build.
[Moto G 4G Android Development] Zyquil:
Yeah good thing I kept a copy of 20161103 14.1

Gonna have to wait for future builds and feedback before moving on:good:
[Moto G 4G Android Development] mrLoma:
Where can we find those change logs?
[Moto G 4G Android Development] schrickz:
check it on the 1st post.
[Moto G 4G Android Development] Tenchu:
cm14.1 Dialer

Hi for all..

I'd installed version 20161103 and in version 20161105 i'd to make full wipe (like others said) to make everthing works. After that, SIM and other things are ok, even dialer.

Sorry for my english.
[Moto G 4G Android Development] Kayant:
Just so you know "Official" nightly builds are a go and I would expect the first one will be up tomorrow.

Also it seems like the phone stuff in limbo have been merged in so if possible could someone test upgrading to the build without full wipe(Ofc make sure to have your backup in hand!) as I don't have a second working sim to use for me Moto G because Oneplus 3 using nano sim.

I wouldn't be as there is more than enough experience people supporting it atm :p. Although when I learn more about development I will likely make my "custom" rom with features I want and maybe share it.

Indeed it is which is why I went for it when I have enough Uni money now :D. As long as it doesn't get damaged or lost this will be my new device for a long time i think.
[Moto G 4G Android Development] khalmika:
wait what? You mean that if i flash any zip after 1103 i'll have issues?

i've flashed 1106 and everything is ok :D (well i had to wipe all data)
[Moto G 4G Android Development] aha360:
Based on MY EXPERIENCE, yes, as when I tried to make calls either via the AOSP/stock/Google Dialer or via any third-party dialer, I don't get an in-call/call-handling UI presented to me at all, and when I receive calls, I also fail to get the in-call/call-handling UI presented to me so I do not even get a chance to put down/cancel the phone call without having to reboot my phone, so therefore, for that reason, I advise against upgrading to ANY post-20161103 CM14.1 ROM in the meantime (2016-11-08) until this is fixed.
[Moto G 4G Android Development] IronTechmonkey:
Wahoo, and there we are within the first 18 devices addedd to the official CM14.1 build list. https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets Thanks to you, and [MENTION=5075128]LuK1337[/MENTION] et all for getting Peregrine in there so early.
[Moto G 4G Android Development] schrickz:
awesome ..
[Moto G 4G Android Development] Fedray:
CM13 Peregrine changelog is no longer available, now we have this https://www.cmxlog.com/14.1/peregrine/ :D
[Moto G 4G Android Development] schrickz:
can't wait for testing the 1st Nightly, the same feeling when I tested 1st Kit-kat build for Nexus S.
[Moto G 4G Android Development] taconi dantas:
http://www.cyanogenmod.org/blog/cm14-is-landing
[Moto G 4G Android Development] gaston2150:
I finally test this ROM tonight.

I have some issue.

First, I can't get a root accès properly. I checked root access in developper option and installed superSU with binaries.

But, I can't modify /system/etc/hosts with a terminal or with Adaway

How did you get a functional access root ?

I restored sucessfully my SMS, but I get notifications when i restart the phone.

thanks for your help
[Moto G 4G Android Development] Pupet_Master:
I know the feeling, for that money where i live i would get an LG G3, but the OnePlus 3 is just amazing for the price and the possibilities to mod.

I hope to see this ROM of yours to become a reality some day ;)
[Moto G 4G Android Development] Fedray:
You don't need to install any SuperSU, only enable it in developer options.
[Moto G 4G Android Development] schrickz:
which version of AdAway you have ?

try v.3.2, set the host target from AdAway preference to system/etc/host

if you using v.3.1.2, you need to flash the AdAway systemless.zip after flashing SuperSu SR3.zip.
[Moto G 4G Android Development] gaston2150:
Thanks

I uninstalled superSU and effectively, it works fine without it.

I installed adaway 3.1.2 with systemless.ZIP.

In the thread, it noticed 3.2 must not be installed with systemless.zip. so how to pass 3.1.2 to 3.2?

Also, thanks for this ROM, it very powerfull !

Envoyé de mon XT1039 en utilisant Tapatalk
[Moto G 4G Android Development] pjconoso:
CM14.1 nightly is live. I want to hug the devs!

https://www.cmxlog.com/14.1/peregrine
[Moto G 4G Android Development] Wyneg:
Official nightly can be flashed over unofficial builds???

Thanks!
[Moto G 4G Android Development] fygonzalo:
Hello guys, anyone can install gapps using the cyanogenmod recovery? It gives me an error: "E:Failed to find META-INF/com/android/metadata" in update package...

I will go back to TWRP but I am not sure why the official cyanogenmod recovery doesn't work..
[Moto G 4G Android Development] panagiotis15:
Its possible but to have better results i recomend to make a clean flash install.I am making my tests upon to my device as well!
[Moto G 4G Android Development] Wyneg:
I flashed over and SIM card isn't recognized, xD

I'll try clean install!!!

Thanks!
[Moto G 4G Android Development] aha360:
Yeah, flashing OFFICIAL builds on top of UNOFFICIAL builds will result in com.android.phone crashing, with the end result being that the SIM(s) will not initialise, so therefore, a factory reset is needed.

In other news: the in-call/call-handling UI works - it turns out that I needed to CHOOSE THE DEFAULT PHONE APP BEFORE I PLACE A PHONE CALL.

Talk about silly.
[Moto G 4G Android Development] Fedray:
Any major bugs? Is stable enough for daily driver? I'm at cm13 atm

Enviado desde mi XT1040 mediante Tapatalk
[Moto G 4G Android Development] troyekto:
It's says that sim card is locked, but outgoing calls are working for me. I can't test incoming calls at the moment.
[Moto G 4G Android Development] fygonzalo:
It is for me, I didn't found any bug.
[Moto G 4G Android Development] B160AVE:
Stable here so far.
[Moto G 4G Android Development] Tenchu:
Flash over unofficial

Hi all!

For me, flashing over unofficial version (20161105) work's, included phone.

Only bug i'd saw is the battery icon that not all changes.

In time, congratulations devs for great job.
[Moto G 4G Android Development] matthias1976:
i bet dirty flash over 04.11.16 build and newer work.

coming from 03.11.16 and older will give no sim error
[Moto G 4G Android Development] l0rand:
Will I need to wipe the data or system is enough coming from 20161103?

[MENTION=507649]devs[/MENTION]: Thank you for your efforts bringing 7.1 to our devices :)
[Moto G 4G Android Development] IronTechmonkey:
If you are not specifically testing to see if a dirty flash works then clean flashing is recommended for ROM testing, especially at this early phase just after a significant transition.
[Moto G 4G Android Development] l0rand:
Will I need to wipe everything then? Or wiping system should be enough?
[Moto G 4G Android Development] Wyneg:
Clean install worked ;)

Thanks!
[Moto G 4G Android Development] CraschTD:
After few days on 14.1 I see that it's enough for daily use.

I did a clean install.

Anyway I got some reboots (say 1 per day).

Battery consumption is worse than CM13.

Sometimes when I turn on the screen the phone vibrates and the camera opens.
[Moto G 4G Android Development] l0rand:
Doesn't that happen when you push power twice? You can turn that off in Settings. Look for Jump to Camera.
[Moto G 4G Android Development] CraschTD:
You're right!!!! Evidently my cover (sometimes) keeps the power button pushed. Without the cover the behavior is consistent!

Thanks a lot
[Moto G 4G Android Development] Fedray:
So battery life is worse? Thats bad :( we need cm14.1 custom kernel asap! Im gonna try the rom today and then write my review.

Enviado desde mi XT1040 mediante Tapatalk
[Moto G 4G Android Development] l0rand:
http://xdaforums.com/showthread.php?t=3295505 This one works with 14.1.
[Moto G 4G Android Development] IronTechmonkey:
Clean flashing, almost by definition, includes a full wipe/factory reset. Also, I have seen one unique recommendation for flashing ROMs on Peregrine devices which I've not seen recommended for other CM devices*. I dont say this in a lecturing or nasty way but anyone flashing these ROMS should have good general knowledge about the differences between clean and dirty flash, and there are some good and easily found CM and XDA resources in that regard. Here is what I call a very clean flash which includes some steps that are not necessary but do eliminate uncertainly later if bugs are encountered. This flash workflow is focused on minimizing avoidable extraneous factors when testing the ROM rather than just updating my device or trying to save time.

Preparation:

- Back up your app data.

- Create a nandroid backup

Flash:

- Boot to recovery

- Wipe Dalvik and System caches. *Peregrine specific note referred to above: For some devices and ROMS it is also suggested that you also wipe data at this point. Such was recommendation for Peregrine CM12.1 and tweaked stock ROM but I'm not sure if wiping data is also recommended for Peregrine CM14.1.

- Flash ROM and Gappps one after the other in the same TWRP recovery session (missing step added**).

- Wipe Dalvik and System caches again (missing step added**)

- Reboot to system.

- In some cases it is recommended that you not skip the first run configuration steps. I usually skip them although we are now required to connect to a network at some time during first boot (missing step added**).

- Allow phone to settle for a few minutes

- Reboot.

- Proceed to do local configuration while looking out for bugs before things get complicated by the addition of apps.

- Install your apps.

[MENTION=7115570]l0rand[/MENTION]

[EDIT]** Added steps that were lost during my sloppy cutting/pasting earlier....and they are important steps as well, like the defining aspect of clean flashing I mention earlier. Mea culpa, and Physician heal thyself! Apologies for any confusion but what is listed now is a proper (but certainly not the only proper) workflow.
[Moto G 4G Android Development] Tenchu:
Perfectly instructions to clean flash

Amazing IronTechmonkey! Thank's for that great instructions.
[Moto G 4G Android Development] l0rand:
Did anyone experienced problems when moving applications to the internal storage? If I try to move them from the sd card I get "not enough disk space" message, but if I remove the sd card and install from playstore, then it installs fine.
[Moto G 4G Android Development] IronTechmonkey:
When you say internal storage are you referring to internal SD or external SD being used as internal storage (adoptable storage)?

NM did some research and figured it must be internal/private storage.
[Moto G 4G Android Development] CraschTD:
I didn't trust the SD adoption mechanism (I didn't understand it very well), I would like to keep a partition not managed by the system but it seems not possible.

From what I see the SD is reformatted and an unknown file system partition is created when you adopt your partition.

So I'm sticking with link2sd.
[Moto G 4G Android Development] IronTechmonkey:
Nor did I trust it from the first moment I saw it and realized how easy it is for users to accidentally wipe their SD cards by playing with adoptable storage without understanding the ramifications. There was also no readily available first party documentation other than a general statement that it's wonderful and will save you space. Sadly it is hard to see this as being accidental. Google and some phone manufactures first tried to take away external SD slots from the hardware but that was not tolerated by the consumer market so now Google is using this feature to achieve a similar effect. It has always been one of Google's desires to leave us only one route to our data - on-line through their on line services which is harder to force on devices that are have external SD card slots or are configured to NOT be on-line all the time.

In any event the value of adoptable storage is exaggerated and there are serious downsides to using it. Here are some articles about adoptable storage.

http://www.androidcentral.com/inside-marshmallow-adoptable-storage

https://www.reddit.com/r/Android/comments/3oz7eu/guidelines_for_marshmallow_users_formatting/

https://www.reddit.com/r/Android/comments/3o6u80/psa_i_formatted_my_sd_card_as_internal_storage/

As to partitioning off a section of the drive so Android wont use it, I've read that this can be doing but dont recall the source or the details... of whether it was done under adoptable or portable storage.
[Moto G 4G Android Development] CraschTD:
I've tried the obvious way with mini tool PW, so I created two partition. Told android to adopt only one partition, but it did reformat all the SD with two partition.

I hope that some day they will leave the dark side and stick with the available space left on sd.

In this case, I'm sure that the implementation of adoptable storage is better than link2sd.
[Moto G 4G Android Development] IronTechmonkey:
For what this is worth, I found the post I had been recollecting. Second half of this post: http://xdaforums.com/showpost.php?p=64466517&postcount=213. Definitely be well backed up if you play with this.
[Moto G 4G Android Development] tutticlandestini:
this can help you? http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
[Moto G 4G Android Development] CraschTD:
Seems promising... I'll try this way ASAP
[Moto G 4G Android Development] tonibm19:
So, I have the first or second unofficial cm14.1 version and I would like to do a clean install and switch to official.

Sure there are no sim problems with clean install?

I also read something about 1 random reboot a doy which doesnt seem to happen to be right now(in unofficial cm14.1), is this true?

I'm using my phone as a daily diver so I'd like the official version to be as stable or more than the unofficial im running now.
[Moto G 4G Android Development] IronTechmonkey:
Thanks for that link. Although the "How to split your card" section is probably what [MENTION=2011434]CraschTD[/MENTION] is looking for, I found this interesting "What really happens is that with Marshmallow you cannot move-to-sd without adopting your SD card as internal. And then the only apps that will move-to-sd (now called Change) are those that could already move-to-sd.". Assuming this will be the same in N7.x/CM14.x, then being forced by Google to use REMOVABLE storage that I own in a way that is not REMOVABLE in a device that I own just to store apps in external SD will keep me on L5.1.1/CM12.1 and start me looking for non-Android options. Arrrggg! I love Android and CM but Google just craps on us through it. Sorry for the OT.