[ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1

[schrickz]

Same problem here.


@Kayant links to daily builds on first post are missing.

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.

Sent from my peregrine using XDA Labs

 

[Kayant]

@Kayant links to daily builds on first post are missing.

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.

Sent from my ONEPLUS A3003 using Tapatalk

 

[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

 

[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

 

[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?

 

[tpa-moto]

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

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.

 

[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

 

[matthias1976]

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

only old backup worked for me.
installing older zip wont work.

I have tested the upgrade and it seems to work fine upgrading from CM13 to CM14.1 with the 4 Nov build.

dirty flash from cm13 is working but dirty flash from cm14.1 not !?

 

[aha360]

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

only old backup worked for me.
installing older zip wont work.

dirty flash from cm13 is working but dirty flash from cm14.1 not !?

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.

 

[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)

 

[schrickz]

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)

better to have a backup.

Sent from my peregrine using XDA Labs

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

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.

had this problem when I got both cm & Google dialer installed, try to disable cm dialer.

Sent from my peregrine using XDA Labs

 

[aha360]

better to have a backup.

Sent from my peregrine using XDA Labs

---------- 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.

Sent from my peregrine using XDA Labs

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.

 

[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...

 

[sebaalbo98]

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...

I was the same with version 04 and did a clean install and fix

 

[matthias1976]

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...

after restore fullbackup still no sim ?
for me it worked with fullbackup

 

[khalmika]

I was the same with version 04 and did a clean install and fix

Thank you!!! I just wiped data-cache and fixed!!

 

[aha360]

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...

I was the same with version 04 and did a clean install and fix

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.

 

[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 . I would guess it may due to some changes not being fully merged in yet.

Sent from my ONEPLUS A3003 using Tapatalk

 

[Pupet_Master]

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 . I would guess it may due to some changes not being fully merged in yet.

Sent from my ONEPLUS A3003 using Tapatalk

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)

 

[Zyquil]

only old backup worked for me.
installing older zip wont work.

dirty flash from cm13 is working but dirty flash from cm14.1 not !?

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.

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.

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

better to have a backup.

Sent from my peregrine using XDA Labs

---------- 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.

Sent from my peregrine using XDA Labs

CM Dialer isnt on the applist of 14.1