[ROM][SM-P605][7.1.2] Unofficial LineageOS/CyanogenMod 14.1 for lt03lte (13.09.2020)

rp518dan

Member
Dec 30, 2011
23
3
0
Philadelphia
I like having SU enabled by default.

It was interesting that I had to figure out how to turn on root by reading the OP.
It works well for me to not have to download an additional file.

New Build

Changelog:
-Synced sources
-Bluetooth disabled per default
-unknown sources enabled per default

Download

Also a little poll: It's planned that Lineage won't be prerooted anymyore and the SU stuff will become an extra addon (i.a. for problems with app which are using Safetynet).

Should i stick to this or should i enable SU per default (like now)?

Please vote here: http://www.strawpoll.me/11998987
 

DA6030

Senior Member
Oct 3, 2007
285
130
63
HDMI output

Out of curiosity, has anyone tried HDMI output via an MHL adapter?
I just tried with a SlimPort adapter, which did not work, although I frankly don't know if the hardware supports either.
For those unfamiliar, there are two incompatible standards for outputting HDMI video over microUSB (SlimPort and MHL), each of which usually requires a dedicated chip on the board.
 

Tilagoon

Senior Member
Jan 20, 2012
1,095
521
133
Montpellier
Out of curiosity, has anyone tried HDMI output via an MHL adapter?
I just tried with a SlimPort adapter, which did not work, although I frankly don't know if the hardware supports either.
For those unfamiliar, there are two incompatible standards for outputting HDMI video over microUSB (SlimPort and MHL), each of which usually requires a dedicated chip on the board.
Hi,
I have successfully connected my SM-P605 with my TV using an MHL to HDMI adapter cable
As far as I remember there are two different types of MHL to HDMI cables depending upon the model of the smartphone.
I bought this one on Amazon.
Below a picture of the wrapping of this cable.
I am not using the CM 7.1.1 ROM for time being but a custom ROM 5.1.1 (I don't know if it matters)

 

Attachments

  • Like
Reactions: DA6030

DA6030

Senior Member
Oct 3, 2007
285
130
63
Below a picture of the wrapping of this cable.
I am not using the CM 7.1.1 ROM for time being but a custom ROM 5.1.1 (I don't know if it matters)
Awesome, thank you! You also answered the question I meant to ask, which is about this ROM in particular being compatible. Is the 5.1.1 ROM you used when testing the MHL cable a CM-based ROM, or is it TouchWiz-based?
 

Cilenco

Senior Member
Jan 2, 2013
87
75
38
Can someone please tell me about the battery life with this ROM?
I'm on Lollipop atm and the battery life is awesome (3-4 days of two hours video streaming)

On other Nougat ROMs there is a bug with videos (zooms into the top left corner after some time). Is this fixed in this ROM?
 

DA6030

Senior Member
Oct 3, 2007
285
130
63
Can someone please tell me about the battery life with this ROM?
On other Nougat ROMs there is a bug with videos (zooms into the top left corner after some time). Is this fixed in this ROM?
I use mine principally for ~2 hours/day of video streaming, although I charge it every night, and I'd estimate it never falls below 70%.
I've never heard of, nor experienced, any video bugs with this ROM.
 

Ben81

Senior Member
May 16, 2010
112
40
48
Pontefract, West Yorkshire
Out of curiosity, has anyone tried HDMI output via an MHL adapter?
I just tried with a SlimPort adapter, which did not work, although I frankly don't know if the hardware supports either.
For those unfamiliar, there are two incompatible standards for outputting HDMI video over microUSB (SlimPort and MHL), each of which usually requires a dedicated chip on the board.
MHL cable works fine for me. I'm still on the CM version of this ROM from December. Can't see any reason it wouldn't work on the most recent.
 
  • Like
Reactions: DA6030

niceguy0815

Senior Member
Oct 4, 2011
104
16
0
Hi,
I flashed this Rom on my Galaxy Tab and after a short first view i must say...
"It runs super fast for my feling :)" Thanks for that amazing rom.
But i have now a little qoestion / Problem .. But I also think its not a ROM problem :)..
After installing superuser and titanium backup I start TB the first time and go to settings and give TB via "documet Root" the Path to my TB Backup direktory on my external SD Card.
After setting the Path to the backup location TB restarts automaticly (Its normal)..
But after the restart I got The spinner for (I think in english) "reading app data"..
And this Message stays ther for ever.

Than I hav testet to copy with root explorer my TB Backup folder to internal storage, change the Path in TB Settings and test again.
But the same "reading app data..." massege stays for ever.
Now I hav renamed the TB Backup folder on Ext Storage via root explorer and ceated a new emty TB Backup folder and changed settings to this emty folder in TB.
Now Titanium Backup starts but without old backup files!!

So it seams TB cant read it???
can it be a Android 7 Restrictions or som rights problem???
Befor that rom I had an custom Samsung Rom Android 5.1 (I think) on the tablat.
And there the TB Folder on SD has worked correktly becaus I hav made a backup om my apps before flashing this Rom.

Dose anybody else having this problem or an Idear for me how I can fix this?
 
Last edited:

Tilagoon

Senior Member
Jan 20, 2012
1,095
521
133
Montpellier
Hi,
With root explorer copy the contents of the old TB directory to the new one created !
But why did you install Superuser ??
The normal way of rooting this ROM is to go to developer options and activate the root.
Superuser is not needed !!
 

niceguy0815

Senior Member
Oct 4, 2011
104
16
0
Hi,
With root explorer copy the contents of the old TB directory to the new one created !
But why did you install Superuser ??
The normal way of rooting this ROM is to go to developer options and activate the root.
Superuser is not needed !!
Hi Thanks for replay :)
yes i have testet this 20 minuts aggo :)
But same result "reading app data"...

And with super User you are right thats the way i do that to :)
Sorry for miss understanding :)

Now I start with a emty folder again and test to make a new app backup in TB on this rom and than close TB and see if it has with newly createt files the same problem on start.
If not i will check in Root explorer the diffrents from old and new created files. If it has on??? :)
Backup ist started in this moment and semse to worke to SD Card so far...
 

hizzy06

Member
Sep 12, 2015
47
6
0
Hi i always get lag on my lockscreen on this rom. Its only at lockscreen. Once i get past that, everything works smooth and well. Any help? :)
 

Franky_12

Member
Dec 3, 2012
6
2
0
Hi i always get lag on my lockscreen on this rom. Its only at lockscreen. Once i get past that, everything works smooth and well. Any help? :)
Yes, I can confirm that - in a way.
The lag went away as I removed a custom background for the lockscreen.
I used "google backgrounds" from the playstore to only install a background for the launcher and not for the lockscreen.
 
  • Like
Reactions: DA6030

niceguy0815

Senior Member
Oct 4, 2011
104
16
0
Hi,
I got my TB Backup Pronblem fixed.
It was one damaged File in Backup folder. After moving 2Houers files around I had found it :).. 1 of 1125 Files :)...
Now Tb works fine again...
 
  • Like
Reactions: DA6030

hizzy06

Member
Sep 12, 2015
47
6
0
Yes, I can confirm that - in a way.
The lag went away as I removed a custom background for the lockscreen.
I used "google backgrounds" from the playstore to only install a background for the launcher and not for the lockscreen.
Alright thanks man! Shall try that later :)
 
Jun 2, 2015
38
11
0
Petah Tikva
Hello. I have a problem with restoring backup with TWRP (3.0.2.0).

I have made a complete backup using TWRP. Everything works fine, except for the data partition. When I restore the backup of the data partition I have no errors in TWRP, but after booting i keep getting messages that com.android.phone has crashed, capacitive buttons are being highlighted although I set them to be off all the time, and I cannot enter system settings! When I tap on the gear, the Settings screen appears, but it is totally blank, no options to choose, searching yields no effect.

I tried fixing permissions with apps you can find in Google Store, with no luck. Repairing the partition with TWRP did not help either.

Any ideas?
 
Jun 2, 2015
38
11
0
Petah Tikva
Hello. I have a problem with restoring backup with TWRP (3.0.2.0).

I have made a complete backup using TWRP. Everything works fine, except for the data partition. When I restore the backup of the data partition I have no errors in TWRP, but after booting i keep getting messages that com.android.phone has crashed, capacitive buttons are being highlighted although I set them to be off all the time, and I cannot enter system settings! When I tap on the gear, the Settings screen appears, but it is totally blank, no options to choose, searching yields no effect.

I tried fixing permissions with apps you can find in Google Store, with no luck. Repairing the partition with TWRP did not help either.

Any ideas?
OK, it has everything to do with permissions. When i change every item on the data partition to rwxrwxrwx i can access Settings and everything works. Until reboot. The questions are:
1. How can I change the permissions permanently, so that they would stay even after reboot?
2. Is there a way to know which permissions to set on which file/directory, because setting rwxrwxrwx on everything seems to compromise security.

I don't know whether this bug is TWRP or ROM related.
 

Franky_12

Member
Dec 3, 2012
6
2
0
OK, it has everything to do with permissions. When i change every item on the data partition to rwxrwxrwx i can access Settings and everything works. Until reboot. The questions are:
1. How can I change the permissions permanently, so that they would stay even after reboot?
2. Is there a way to know which permissions to set on which file/directory, because setting rwxrwxrwx on everything seems to compromise security.

I don't know whether this bug is TWRP or ROM related.
Did you wipe your data partition before restoring it?
So as you own a complete backup I would even consider a complete wipe before restoring the backup.