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

Status
Not open for further replies.
Search This thread

john99ap

Senior Member
Sep 17, 2016
237
109
I installed v13 version. It is work well, but i do not couldonˋt install my downloaded apk file (for example: zemana antivirus, eWeather hd e.t.c.). I install form play store, without any problem.

If you mean the greyed out "Install" button, just press the square button to go to recents, select another app and then return to the previous by pressing square again. Now you should be able to press the "Install" button.
 
  • Like
Reactions: nguhanhson

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
Just tried

Just tried this ROM and ..... I am left speechless. It virtually granted my old Galaxy Tab 2 new life. I have used Dhollmen 4.4.4, it was nice ROM, but I got used to my new Xperia X Compact phone and my tablet was used just a deco for a shelf :) This ROM is awesome, and most importantly very fast and responsive. Thank you very much @android andi
 

Android-Andi

Inactive Recognized Contributor
Mar 3, 2013
10,854
29,272
andi34.github.io
Uff, I guess it is a very difficult task without having done it before and with the risk of loss my tablet forever. Thanks for your help, anyway.
It is not, but i have a good day today... attached a kernel which skips the intelligent board detection and force uses p3110 driver and configs.
You simply need to flash that directly after flashing the rom, kernel should work on all 5.x, 6.x and 7.x roms.

I have not tested, but you might be able to update your recovery too:
Use a device specific TWRP and flash a common TWRP (my unofficial "espresso-common" or official "espressowifi"), (DON'T REBOOT)
once that's done flash the AnyKernel with RECOVERY prefix.
Now reboot your recovery.
If you have luck, you might have a working common TWRP now - in bad case you need to flash using Odin a working one again ;)
 

Attachments

  • AnyKernel-2017-10-28-11-55-ONLY-P3110.zip
    5.5 MB · Views: 21
  • AnyKernel-2017-10-28-11-55-ONLY-P3110-RECOVERY.zip
    5.5 MB · Views: 31
Last edited:

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
[IRRELEVANT] Fingerprint sensor & Camera

Fingerprint sensor is a bit laggy and moody. Sometimes it works, sometimes not. Waiting a bit helps...

From camera quality I can't do any conclusion until I can myself compare pictures from Stock, but what is a bit disturbing is that Camera Button is not starting Camera when phone is locked and in Camera app the Volume Up/Down buttons are not making Zoom or anything useful, they just work as Trigger :)


Wrong forum
 
Last edited:

mvn_

Member
Oct 28, 2017
18
2
It is not, but i have a good day today... attached a kernel which skips the intelligent board detection and force uses p3110 driver and configs.
You simply need to flash that directly after flashing the rom, kernel should work on all 5.x, 6.x and 7.x roms.

I have not tested, but you might be able to update your recovery too:
Use a device specific TWRP and flash a common TWRP (my unofficial "espresso-common" or official "espressowifi"), (DON'T REBOOT)
once that's done flash the AnyKernel with RECOVERY prefix.
Now reboot your recovery.
If you have luck, you might have a working common TWRP now - in bad case you need to flash using Odin a working one again ;)

Hello Andi, thank you for doing what you do.
I have the same problem as this user, only that I'm using a P3100. Would this kernel work on my device? I don't mind losing the 3G part, because my tablet is broken and it doens't recognize SIM cards.
 

g4rr4f0n3

Member
Oct 25, 2017
7
0
It is not, but i have a good day today... attached a kernel which skips the intelligent board detection and force uses p3110 driver and configs.
You simply need to flash that directly after flashing the rom, kernel should work on all 5.x, 6.x and 7.x roms.

I have not tested, but you might be able to update your recovery too:
Use a device specific TWRP and flash a common TWRP (my unofficial "espresso-common" or official "espressowifi"), (DON'T REBOOT)
once that's done flash the AnyKernel with RECOVERY prefix.
Now reboot your recovery.
If you have luck, you might have a working common TWRP now - in bad case you need to flash using Odin a working one again ;)

Thanks very much for your help. I don't know how to thank you. I'll try them as soon as I can.
 

g4rr4f0n3

Member
Oct 25, 2017
7
0
Thanks very much for your help. I don't know how to thank you. I'll try them as soon as I can.

I have just installed the ROM, without problems. Thank you so much!!

The recovery was wrong. I think the problem is that the AnyKernel zip file with RECOVERY prefix is exactly the same as the one without the prefix. Isn´t it? Could you check that it is correct?When I try to install it in TWRP, I have an error. Thanks again.
 

smart-t78

Senior Member
Jun 24, 2014
1,241
1,368
www.androidfilehost.com
I have just installed the ROM, without problems. Thank you so much!!

The recovery was wrong. I think the problem is that the AnyKernel zip file with RECOVERY prefix is exactly the same as the one without the prefix. Isn´t it? Could you check that it is correct?When I try to install it in TWRP, I have an error. Thanks again.
which error do you have??
are you using the latest common twrp??
if you have a problem with twrp, please post the issue in twrp thread.
 
Last edited:

Android-Andi

Inactive Recognized Contributor
Mar 3, 2013
10,854
29,272
andi34.github.io
I have just installed the ROM, without problems. Thank you so much!!

The recovery was wrong. I think the problem is that the AnyKernel zip file with RECOVERY prefix is exactly the same as the one without the prefix. Isn´t it? Could you check that it is correct?When I try to install it in TWRP, I have an error. Thanks again.

Good it worked, we can continue taking about it in my anykernel thread. Both zips are same same besides that the RECOVERY one should address the recovery.img instead boot.img.

Please post the recovery.log in my anykernel thread after trying to flash it (adb pull /tmp/recovery.log)
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 203
    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 :)