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

Maritus1

Senior Member
Dec 14, 2013
253
104
0
I'm getting a "no mirrors found" on androidfilehost download link. Anyone else?
No, I've tested it, AFH has found four mirrors.

If I want to dirty flash the updated builds, do I have to reflash gapps? I know I shouldn't dirty flash, but I like to test it and if I run into issues I'm gonna clean flash anyway.
Thanks
 
Last edited:

asusgarb

Senior Member
Jul 4, 2010
1,775
344
0
I've just read OP and I have a question. Why shouldn't we flash SuperSu? It should offer better root experience... or is it incompatible with nougat?

Inviato dal mio SM-N9005 utilizzando Tapatalk
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,211
3,345
253
Beijing
@davidmueller13
I'm trying my hands at building TWRP today. I'm referring to the official guide here and using the limited manifest here (also mentioned in the guide) to save space, since I don't build Omni.
Repo sync completed successfully. Then under the build directory, I cloned the tree you linked me to a while ago:
Code:
git clone https://github.com/davidmueller13/device_lt03lte_nougat.git device/samsung/lt03lte
And I did the envsetup and it did say "including device/samsung/lt03lte/vendorsetup.sh", so I assume I synced that part correctly too.
But then in the lunch menu there's no device-specific entry other than "cm_lt03lte-userdebug", and when I pick it it just errors out saying there's no config makefile.
Are the steps I followed outdated or something else I missed?
 
Last edited:

davidmueller13

Senior Member
May 13, 2014
177
940
93
davidmueller.xyz
And I did the envsetup and it did say "including device/samsung/lt03lte/vendorsetup.sh", so I assume I synced that part correctly too.
But then in the lunch menu there's no device-specific entry other than "cm_lt03lte-userdebug", and when I pick it it just errors out saying there's no config makefile.
Do you maybe use one of the CM branches instead of of the omni branch?
 

AndyYan

Recognized Contributor
Jan 30, 2012
4,211
3,345
253
Beijing
Ah crap, just found out I wrote the wrong link in the initial post. But I did clone the tree/omni one... I'll double-check that later.

EDIT: Apparently I'm bad at git usage. Manually set the fetched branch and it seems to lunch just fine, will see how the build goes.

Sent from Google Nexus 6P @ CM13

---------- Post added at 08:37 PM ---------- Previous post was at 07:46 PM ----------

Still hitting a ton of roadblocks. I had to add a lot of extra repos to quiet the errors thrown by lunch, yet it now reports "WARNING: detected conflict in revisions for repository android_device_samsung_msm8974-common" which I don't know how to solve. On top of that, every time I lunch it attempts to revert my roomservice.xml to default.
Here's my current roomservice.xml - basically adding necessary repos from your collection:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
  <remove-project name="lj50036/android_device_qcom_common" />
  <project path="device/samsung/lt03lte" name="davidmueller13/device_lt03lte_nougat" remote="github" revision="omni" />
  <project path="device/samsung/msm8974-common" name="davidmueller13/android_device_samsung_msm8974-common" remote="github" revision="cm-12.1" />
  <project path="kernel/samsung/lt03lte" name="davidmueller13/kernel_samsung_lt03lte_nougat2" remote="github" revision="master" />
  <project path="device/qcom/common" name="davidmueller13/android_device_qcom_common" remote="github" revision="cm-12.1" />
  <project path="device/samsung/qcom-common" name="davidmueller13/android_device_samsung_qcom-common" remote="github" revision="cm-12.1" />
  <project name="android_hardware_broadcom_wlan" path="hardware/broadcom/wlan" remote="omnirom" revision="android-6.0" />
  <project name="android_external_stlport" path="external/stlport" remote="omnirom" revision="android-6.0" />
  <project name="android_hardware_sony_boringssl-compat" path="hardware/sony/boringssl-compat" remote="omnirom" revision="android-6.0" />
</manifest>
 
Last edited:

AndyYan

Recognized Contributor
Jan 30, 2012
4,211
3,345
253
Beijing
You should not use device_qcom_common, device_samsung_qcom-common and device_samsung_msm8974-common from my github, because I forked them 2 years ago (they are outdated).
You can just the ones you find in omniROM github.
No dice, still saying conflicting revisions. Is that because both your and Omni's qcom-common repo don't have an "android-6.0" branch? I had to use "android-5.1" instead so as to make it sync properly.
 

sgs9

Senior Member
Nov 10, 2010
747
184
73
Essen
garudalinux.org
Very good work, thx to @davidmueller13 :)
Some question.
In TWRP 3.0.2 my restore (backup 5.1.1) stop on modem installation.

Wireless work everytime but notification say no Internet connection for device, with PC I have.
In Titanium Backup, long press menu button for Menu I got split screen with last recent apps.
No change modus between 2.4 and 5 GHz .
Settings now only white page.
Something went wrong :mad:

For people like me ;) , put ROM and Gapps on ext. SD before wipe Internal Storage :D

Sorry about my English.
 
Last edited:

vpboi

Member
May 20, 2012
15
4
0
Perth
First off all let me thank you @davidmueller13 for delivering an excellent ROM.
I have been using this ROM for the last couple of months or so I really appreciate the amount of work you have put in and the progress you've made with so far with it.

My only gripe is with the latest release with the shift to you made for the long press menu key from triggering the Multi Window view to showing the app 'Menu'.
I know some people have requested this (or similar) behaviour, but I for one loved the ability to bring up the 'Multi Window' view.
I think it is a very useful feature to be able to interact with multiple applications at the same time with a long press.
Would you please reconsider bringing back the 'long press' behaviour ( to show Multi Window) in your future releases or let us know how to manually revert the behaviour back to what it was in your past releases.

Once again, Thank you for all your hard work on this ROM. It really does help give a new life to my Note 10.1, Cheers :)
 
Last edited:
  • Like
Reactions: DA6030

vpboi

Member
May 20, 2012
15
4
0
Perth
Although not all button settings are working, you can set longpress home button for split screen.
Thanks for your reply.
Well what do you know It does work; I tried the button settings previously but gave up when the options for menu key wasn't working.
I was actually hoping for a workaround like editing one of the key-layout files but I guess this will do for now. Thank you !
Oh and would you kindly post if any such workarounds (as mentioned above) is applicable here.
I would much prefer the menu key long press to function as the split screen trigger rather than the home key.
 

b2ron

Member
May 2, 2011
7
0
0
not work microphone in Skype
on my tablet, I changed in /system/etc/audio_policy.conf
-global_configuration {
- attached_output_devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER

+global_configuration {
+ attached_output_devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE
- devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
+ devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
 
Last edited: