[CLOSED][ROM][6.x] LineageOS 13.0

Status
Not open for further replies.
Search This thread

Android-Andi

Inactive Recognized Contributor
Mar 3, 2013
10,856
29,295
andi34.github.io
LineageOS 13.0
[#MARSH]
[#ESPRESSONAME]

[#WHATSLOS]

[#KANGERS]

[#WARRANTY]

[#INFOLOS]

[#DSOURCELOS]

Downloads:
Please use latest espresso-common TWRP to flash this rom, you can find it here.
(Other recoveries might work, but maybe cause issues - don't report flashing or Gapps issues if you use a different recovery!)


Official:
espresso3g (boots on P3100 & P5100)
espressowifi (boots on P3110, P3113, P5110 & P5113)

Unofficial (for testing):
[#DLGITHUBIO]

Extras:
su (arm)
su removal (arm)

Support development
[#DONATETOME]

XDA:DevDB Information
[unified] LineageOS 13.0, ROM for the Samsung Galaxy Tab 2

Contributors
Android-Andi, Ziyan
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x

Version Information
Status: Testing

Created 2016-01-29
Last Updated 2017-05-14
 

Android-Andi

Inactive Recognized Contributor
Mar 3, 2013
10,856
29,295
andi34.github.io
Reserved

In case someone likes to compile on his own:

You need to setup Linux first, good tutorial here:
Ubuntu / Xubuntu:
- https://nathanpfry.com/how-to-prepare-ubuntu-14-04-lts-trusty-tahr-to-compile-android-roms/
- https://nathanpfry.com/how-to-setup-ubuntu-15-04-vivid-vervet-to-compile-android-roms/
- https://nathanpfry.com/how-to-set-up-ubuntu-15-10-wily-werewolf-to-compile-android-roms/
- https://nathanpfry.com/how-to-setup-ubuntu-16-04-lts-xenial-xerus-to-compile-android-roms/

Arch based Linux ready to go:
- BBQLinux by @codeworkx http://bbqlinux.org/

Once you have synced CM source run the following in terminal:
Code:
mkdir -p .repo/local_manifests
nano .repo/local_manifests/local_manifest.xml
Add the following to your local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_device_samsung_espressowifi" path="device/samsung/espressowifi" remote="github" revision="cm-13.0" />
  <project name="CyanogenMod/android_device_samsung_espresso3g" path="device/samsung/espresso3g" remote="github" revision="cm-13.0" />
  <project name="CyanogenMod/android_kernel_samsung_espresso10" path="kernel/samsung/espresso10" remote="github" revision="cm-13.0" />
  <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-13.0" />
  <project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-13.0" />
  <project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0" />
  <project name="TheMuppets/proprietary_vendor_ti" path="vendor/ti" remote="github" revision="master" />
</manifest>
Save the file.
Back in terminal:
Code:
repo sync
. build/envsetup.sh
breakfast espressowifi
make bacon
(you can replace espressowifi with espresso3g if you like to build for p3100/p5100)
 
Last edited:

Gabrius99

Senior Member
Keyboard will FC if you flash Gapps.
In this case you need to flash https://www.androidfilehost.com/?fid=24391638059058223 by @Deltadroid directly after gapps.
- should be fixed on next build i hope.

Hi Andi, i'm using this since yesterday and it's pretty stable, i haven't any crash or so, but i'm having a strange issue with sdcard.
It get mounted and I can see it in the native file manager from which I can read and write, but other app can't read it, for example Music doesn't find any song. Going to mnt/media_rw/(sdcard-name) i can see the SDcard but if I try to open a song or an APK it gives me "I/O error". What could be?

(log attached if could help)
 

Attachments

  • log.zip
    121.5 KB · Views: 1,043

Android-Andi

Inactive Recognized Contributor
Mar 3, 2013
10,856
29,295
andi34.github.io
Adaptive storage works??
Haven't added the fstab changes for it. Its on the todo list too. Think sometimes tomorrow i am able to upload a new build, else on monday.


There's a lot of really big work going on ATM:
- common TWRP for all Tab2 variants (P31XX and P51XX will share same recovery).
Only bad side will be, that older builds won't be flashable without manually editing the updater-script inside the rom.zip (all my builds from today and newer will be able to use it) - but older recoveries still can be used.

After that sometimes later (currently testing):
- P3100 and P5100 will share same build
- P311X and P511X will share same build
This reduces build time by 50% and makes maintaining easier again.

Gesendet von meinem LG-H815 mit Tapatalk
 

MJ523

Senior Member
Jan 18, 2015
52
13
@Android-Andi anyway you can help build a rom for the Tab 4 SM-T230NU? sorry I have a tab 2 and now a tab 4 so its weird that tab 2 has a rom and tab 4 does not. any help would be appreciated. Thanks for your work!
 

anonymous8

Senior Member
Jan 6, 2014
144
40
Earlier I was waiting desperately to see MM on my tab but now I m unable to decide which one to flash
#floodofMM #yolo

Sent from my GT-P3100 using Tapatalk
 

anonymous8

Senior Member
Jan 6, 2014
144
40
Am flashing each and everyone to test they build for us so we test for them or u stick to any one and report back
I appreciate you bro
My sixth sense has seen the bright future of marshmallow on our tab #lol
So now I'm downloading Open gapps aroma 6.0.
Report soon

Sent from my GT-P3100 using Tapatalk
 
Last edited:
  • Like
Reactions: bkrishna963

TabTapper

Senior Member
Jun 9, 2015
362
109
Is 3G and Cellular working?

Hi,
Andi thanks for CM13. Can anybody tell about 3G and cellular working for P3100? as i am using for my business work.
Thanks in advance
 

Zte blade l

Senior Member
Mar 6, 2015
148
80
Chennai
Any app don't recognize SD card.I can read the SD card in settings but I can't even download anything in SD card. Even UC browser doesn't recognise SD card.
Any fix....pls
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 204
    LineageOS 13.0
    [#MARSH]
    [#ESPRESSONAME]

    [#WHATSLOS]

    [#KANGERS]

    [#WARRANTY]

    [#INFOLOS]

    [#DSOURCELOS]

    Downloads:
    Please use latest espresso-common TWRP to flash this rom, you can find it here.
    (Other recoveries might work, but maybe cause issues - don't report flashing or Gapps issues if you use a different recovery!)


    Official:
    espresso3g (boots on P3100 & P5100)
    espressowifi (boots on P3110, P3113, P5110 & P5113)

    Unofficial (for testing):
    [#DLGITHUBIO]

    Extras:
    su (arm)
    su removal (arm)

    Support development
    [#DONATETOME]

    XDA:DevDB Information
    [unified] LineageOS 13.0, ROM for the Samsung Galaxy Tab 2

    Contributors
    Android-Andi, Ziyan
    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.0.x

    Version Information
    Status: Testing

    Created 2016-01-29
    Last Updated 2017-05-14
    35
    Reserved

    In case someone likes to compile on his own:

    You need to setup Linux first, good tutorial here:
    Ubuntu / Xubuntu:
    - https://nathanpfry.com/how-to-prepare-ubuntu-14-04-lts-trusty-tahr-to-compile-android-roms/
    - https://nathanpfry.com/how-to-setup-ubuntu-15-04-vivid-vervet-to-compile-android-roms/
    - https://nathanpfry.com/how-to-set-up-ubuntu-15-10-wily-werewolf-to-compile-android-roms/
    - https://nathanpfry.com/how-to-setup-ubuntu-16-04-lts-xenial-xerus-to-compile-android-roms/

    Arch based Linux ready to go:
    - BBQLinux by @codeworkx http://bbqlinux.org/

    Once you have synced CM source run the following in terminal:
    Code:
    mkdir -p .repo/local_manifests
    nano .repo/local_manifests/local_manifest.xml
    Add the following to your local_manifest.xml:
    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
      <project name="CyanogenMod/android_device_samsung_espressowifi" path="device/samsung/espressowifi" remote="github" revision="cm-13.0" />
      <project name="CyanogenMod/android_device_samsung_espresso3g" path="device/samsung/espresso3g" remote="github" revision="cm-13.0" />
      <project name="CyanogenMod/android_kernel_samsung_espresso10" path="kernel/samsung/espresso10" remote="github" revision="cm-13.0" />
      <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-13.0" />
      <project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-13.0" />
      <project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0" />
      <project name="TheMuppets/proprietary_vendor_ti" path="vendor/ti" remote="github" revision="master" />
    </manifest>
    Save the file.
    Back in terminal:
    Code:
    repo sync
    . build/envsetup.sh
    breakfast espressowifi
    make bacon
    (you can replace espressowifi with espresso3g if you like to build for p3100/p5100)
    30
    Adaptive storage works??
    Haven't added the fstab changes for it. Its on the todo list too. Think sometimes tomorrow i am able to upload a new build, else on monday.


    There's a lot of really big work going on ATM:
    - common TWRP for all Tab2 variants (P31XX and P51XX will share same recovery).
    Only bad side will be, that older builds won't be flashable without manually editing the updater-script inside the rom.zip (all my builds from today and newer will be able to use it) - but older recoveries still can be used.

    After that sometimes later (currently testing):
    - P3100 and P5100 will share same build
    - P311X and P511X will share same build
    This reduces build time by 50% and makes maintaining easier again.

    Gesendet von meinem LG-H815 mit Tapatalk
    30
    LineageOS testbuilds up:
    - Clean flash required
    - some parts arent rebranded yet to LineageOS (e.g. SetupWizard)

    Should we rename this thread and update it or generate a new thread?
    29
    • Many thanks to @Ziyan for the new kernel! He did the main part of it! (We worked together on it for almost 9 months now - where is the time?!)

    Time really flies! All those weekends spent with this kernel, fixing the mess created by Samsung, figuring their changes out... countless hours, which will probably never pay off. Nonetheless, it was a great experience :)

    What to expect after this milestone? Well, our kernel is now a proper bringup based on TI's latest 3.0 branch. Part of the reason I decided to go on this unbelievably time-consuming route was to ease the bringup of new kernels in the future; I think my latest experiment pretty much sums up the success here - look at the attached picture :)