Database Develop

[ROM][5.x] SlimLP

SlimLP
[#LOLLI]
[#ESPRESSONAME]
​
[#WHATSSLIM]
[#WARRANTY]
Download:
[#DLGITHUBIO]
[#INFOSLIM]
Disclaimer: SlimRoms are not responsible for any damages to your device.
[#DONATETOME]
XDA:DevDB Information
[unified] SlimLP, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi, SlimRoms
Source Code: https://github.com/SlimRoms/kernel_samsung_espresso10
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-12-10
Last Updated 2017-04-30

Reserved
Screenshots attached

Kudos and thanks to all the special Devs let the tablet have new life. [emoji106] [emoji106] [emoji106]
GT- N7100 with Dr.Ketan Hindocha Rom Android 4.4.2

That's great, nice move thank You @Android-Andi :good:

Great!! Thanks dude!!

Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.

Android-Andi said:
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
Tomorrow morning!

Thank you for making this possible!
All the best for you

Working well for me on my p3110 - brilliant job, well done and many thanks
Sent from my BN NookHD+ using XDA Free mobile app

Android-Andi said:
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
@Android-Andi I will try now your work ... Feedback in an hour. (I hope it boot ☺)
EDIT:
It boot. I'm writing from tab2 P3100 with slimlp 0.8.
First boot take some time and the boot animation is not fluid.
I now try to install SuperSU and restart the system.
After I try adb shell (from terminal?)

@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?

Android-Andi said:
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
Should i do this also on P3110?

Android-Andi said:
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Click to expand...
Click to collapse
@Android-Andi, can i use my terminal in my iMac with the same command you give us? in this case, my tab should be in download mode, right?

SlimShady's said:
Should i do this also on P3110?
Click to expand...
Click to collapse
You can test from time from time if you get an output for "avc:", it will show if there are some denial because of selinux. If i get the output i am able to add a policy to fix it. Hope we can switch to enforced soon
Send from OnePlus One using Tapatalk

MARKBOARD NETSET said:
@Android-Andi, can i use my terminal in my iMac with the same command you give us? in this case, my tab should be in download mode, right?
Click to expand...
Click to collapse
No, device need to boot android.
http://m.youtube.com/watch?v=TMcMVDUbpis
Send from OnePlus One using Tapatalk

Android-Andi said:
You can test from time from time if you get an output for "avc:", it will show if there are some denial because of selinux. If i get the output i am able to add a policy to fix it. Hope we can switch to enforced soon
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
My brain stopped working at "if you get an" xD
Edit: Oh, okay I got it. Will do this tomorrow

Android-Andi said:
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Click to expand...
Click to collapse
@android-Andy Tanks YOU a lot!! Sorry I can only help you as a tester.
3G not working. (See picture) I can receive SMS but can't send.
Problem with root binaries. SuperSU installed give me some minutes.
After I will try your commands. Have you some tests for me?

Android-Andi said:
@philidor thanks a lot
Edit:
mobile data works?
Click to expand...
Click to collapse
yes:highfive::good:

jak978 said:
yes:highfive::good:
Click to expand...
Click to collapse
No mobile data don't work for me. I can receive SMS and have my normal signal bars
This is your grep command @Android-Andi
[email protected]:/ $ su -c dmesg | grep 'avc: '
[ 4.256500] C0 [ init] avc: granted { set } for property=net.rmnet0.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.256958] C0 [ init] avc: granted { set } for property=net.rmnet0.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.257263] C0 [ init] avc: granted { set } for property=net.rmnet0.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.258392] C0 [ init] avc: granted { set } for property=net.rmnet1.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.258728] C0 [ init] avc: granted { set } for property=net.rmnet1.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.259002] C0 [ init] avc: granted { set } for property=net.rmnet1.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260101] C0 [ init] avc: granted { set } for property=net.rmnet2.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260437] C0 [ init] avc: granted { set } for property=net.rmnet2.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260742] C0 [ init] avc: granted { set } for property=net.rmnet2.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 5.750274] C1 [ init] avc: denied { set } for property=supolicy.loaded scontext=u:r:sysinit:s0 tcontext=ubject_r:default_prop:s0 tclass=property_service
[email protected]:/ $

Flashed this as soon when saw that P3100 port also ready. Thanks AndroidAndi! U are really really awesome! Straight change the P3113 version to this version. All working even YouTube able to load video.
What work
- Everything
- Video Player works too. No need 3rd party
Not Working
- 3G Maybe? (haven't tried)
- Recent tab, card stack works perfectly in landscape. When change to portrait, it turns to black color. But, not bothering

[ROM][5.1.1][T710][UNOFFICIAL] CyanogenMod 12.1 for Tab S2 8.0 [BETA]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is BETA at the moment​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@moonbutt74
@yeshwanthvshenoy
@gladiac
@RaymanFX
@sub77
@T_I
@hennymcc
@Sarum4n - for Donating XDA add free
Each of them helped me with this project so a big thanks goes to them!
Before you start
THIS ROM IS ONLY FOR THE SM-T710
A T810 port of this rom by @T_I is available here
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : BETA
What is Fixed
Camera
Sound
Wifi
Storage
Headphones
External sdcard
Screen Rotation
Bluetooth shows note 4 instead of tab s2
Resolution
What is not working
Important
MTP
Minor
Microphone
Minor graphical glitches
Lag after trying to send a text via sms app (Just don't do it and disable the app. It will try to reach RIL even tough its wifi only)
Instructions
How to install CM12.1
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 12.1, enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
18/4/2016 - Fixed Camera (Yes I'm still alive)
**********
27/1/2016 - Fixed Headphones not working
**********
30/12/2015 - Fixed External sdcard
**********
28/12/2015 - Fixed Sound
- Removed Calling option from lockscreen
- Added missing OMX formats
- ROM is now BETA
**********
21/12/2015 - Fixed Storage problems
**********
19/12/2015 - ROM is now ALPHA
- Fixed Wifi
**********
15/12/2015 - Fixed Rotation/Orientation
- Lowered to 320 DPI
- Updated Screenshots
**********
12/12/2015 - Fixed Bluetooth showing note 4
- Fixed bad resolution
- Updated Screenshots
**********
11/12/2015 - CM12.1 Booted for the first time
**********
Downloads
Latest CM 12.1 build : Android File Host
All CM 12.1 releases can be found here : Android File Host
Recommended GAPPS Open Gapps
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/Galaxy-Tab-S2
Screenshots
XDA:DevDB Information
CyanogenMod 12.1 for Samsung Galaxy Tab S2 8.0 T710, ROM for the Samsung Galaxy Tab S2
Contributors
CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-12-11
Last Updated 2016-04-18

Q&A
Q : Why does it say Galaxy Tab S2 9.7 on Android File Host if this is for the 8.0 version ?
A : Android File Host doesn't feature the 8.0 version in their devices. Because of that, all is located under a folder called 8.0
Q : Why is everything so small?
A : The DPI rate is 320 which is the same as on the Stock rom. However, Samsung has made everything bigger. Since this is personal preference, you may always higher your DPI to make things bigger or lower your DPI to make things smaller under Settings > Display > DPI
Q : Will you ever work on CM13?
A : Yes, once we feel like CM12 is good enough, we will move to CM13

Reserved 2

New build 12/12/2015
- Fixed Bluetooth bug showing Galaxy note 4 instead of tab s2
- Fixed bad resolution
- Updated Screenshots

Great work!

Can't wait to use this once it reaches a point where it's functional for everyday use! Excellent work so far!

Good job man!!! Will test this as soon as the WiFi works
Sent from my SM-T710 using Tapatalk

good news for all T810 users! @T_I is working on a port of my ROM. It came to the CM setup wizzard however had some problems with the touchscreen. Should hopefully be a easy fix.

So the sensor module just isn't loading.
Code:
I/ ( 3857): System server: starting sensor init.
D/SensorService( 3857): nuSensorService starting...
E/HAL ( 3857): load: module=/system/lib/hw/sensors.exynos5.so
E/SensorService( 3857): couldn't load sensors module (Invalid argument)
I/ ( 3857): System server: sensor init done.
Tried to use the note 4 ones. They did load up successfully but use different drivers.
Ex the gyroscope uses ICM20610 where mine uses LSM6DS3. I really only came this far. My nightmare would be to make my own sensor libs. That would mean that I would have to learn lot's of lot's of coding!

CTXz said:
So the sensor module just isn't loading.
Code:
I/ ( 3857): System server: starting sensor init.
D/SensorService( 3857): nuSensorService starting...
E/HAL ( 3857): load: module=/system/lib/hw/sensors.exynos5.so
E/SensorService( 3857): couldn't load sensors module (Invalid argument)
I/ ( 3857): System server: sensor init done.
Tried to use the note 4 ones. They did load up successfully but use different drivers.
Ex the gyroscope uses ICM20610 where mine uses LSM6DS3. I really only came this far. My nightmare would be to make my own sensor libs. That would mean that I would have to learn lot's of lot's of coding!
Click to expand...
Click to collapse
I really dont know but doea this help:
https://github.com/STMemsLinuxDrivers/lsm6ds3-input
Sent from my SM-G928I using Tapatalk

Beukhof1 said:
I really dont know but doea this help:
https://github.com/STMemsLinuxDrivers/lsm6ds3-input
Sent from my SM-G928I using Tapatalk
Click to expand...
Click to collapse
Sadly those are for the kernel.
However,
I found this open source sensor for the s3 I9300 that uses a , what I believe, older version of the gyro found in our device. I will see what I can decompile/reverse out of the current module for the tab and will compare it with the open source ones for the I9300. This will be hard and I would be very thankfull if you could redict any expierienced dev you know, here

Suprise!
Turns out I was just missing a shared libary. That caused the module not to load. Sooo.... all that s3 sensor work for nothing
Hey.... atleast I learned something.
Also, build will be released in about 1-2h

CTXz said:
Suprise!
Turns out I was just missing a shared libary. That caused the module not to load. Sooo.... all that s3 sensor work for nothing
Hey.... atleast I learned something.
Also, build will be released in about 1-2h
Click to expand...
Click to collapse
Nice! Good job mate!
Did you have time to look at wifi yet? I would love to try it if that works!
Sent from my SM-T710 using Tapatalk

Beukhof1 said:
Nice! Good job mate!
Did you have time to look at wifi yet? I would love to try it if that works!
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
Not yet, but I will take a look at it soon!

New build is out !
**********
15/12/2015 - Fixed Rotation/Orientation
- Lowered to 320 DPI
- Updated Screenshots
**********
Links have been updated!

Ok so to wifi :
I know most of you want as number 1. priority a working WIFI connection, but this doesn't seem to be that easy to fix, at least not for my empty brain. As you've probably already noticed, my debugging skills are still quite bad (Yes I'm still learning... Yes I'm not perfect.... well maybe yes... ok no just kidding). The current issue i'm facing has probably to do something with the api drivers and wpa_supplicant. I've noticed that the KMSG doesn't even show a tiny trace of the cfg80211 driver and the nl80211 driver. If any developer out there knows what to do with the following log output when trying to access the wifi HAL / Enabling WIFI please tell me.
Code:
D/SoftapController( 3507): Softap fwReload - Ok
W/CommandListener( 3507): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 3507): Setting iface cfg
E/WifiStateMachine( 3901): Unable to change interface settings: java.lang.IllegalStateException: command '90 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 90 Failed to set address (No such device)'
E/WifiMonitor( 3901): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
I/wpa_supplicant( 7883): Successfully initialized wpa_supplicant
I/wpa_supplicant( 7883): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 7883): Could not read interface wlan0 flags: No such device
I/wpa_supplicant( 7883): nl80211: Driver does not support authentication/association or connect commands
E/wpa_supplicant( 7883): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 7883): wlan0: Failed to initialize driver interface
E/WifiStateMachine( 3901): Failed to start supplicant!
D/WifiService( 3901): setWifiEnabled: false pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/SoftapController( 3507): Softap fwReload - Ok
W/CommandListener( 3507): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 3507): Setting iface cfg
E/WifiStateMachine( 3901): Unable to change interface settings: java.lang.IllegalStateException: command '93 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 93 Failed to set address (No such device)'
E/WifiMonitor( 3901): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
I/wpa_supplicant( 7915): Successfully initialized wpa_supplicant
I/wpa_supplicant( 7915): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 7915): Could not read interface wlan0 flags: No such device
I/wpa_supplicant( 7915): nl80211: Driver does not support authentication/association or connect commands
E/wpa_supplicant( 7915): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 7915): wlan0: Failed to initialize driver interface
E/WifiStateMachine( 3901): Failed to start supplicant!
D/WifiService( 3901): setWifiEnabled: true pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/WifiController( 3901): WifiController msg { when=0 what=155656 target=com.android.internal.util.StateMachine$SmHandler } deferred for 313ms
D/WifiService( 3901): setWifiEnabled: false pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/WifiController( 3901): DEFERRED_TOGGLE handled
D/WifiService( 3901): setWifiEnabled: true pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/SoftapController( 3507): Softap fwReload - Ok

And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!

CTXz said:
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
Click to expand...
Click to collapse
Thanks a lot for the effort you're putting into this.

New build 19/12/2015
This build is no longer PRE-ALPHA but ALPHA
**********
19/12/2015 - ROM is now ALPHA
- Fixed Wifi
**********

CTXz said:
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
Click to expand...
Click to collapse
Ok, this convinced me, sdcard 4th, wifi 3rd. Build on the T810 stack is running.

[ROM] LineageOS 13.0 builds for the Galaxy Exhibit II 4G

DISCLAIMER
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Unofficial LineageOS 13.0 builds for the SGH-T679, ancora_tmo
This ROM currently has reboot issues. There is a list below that lists what works and what doesn't
What works:
Boots
Bluetooth
System Sounds
SD Card
Sensors like accelerometer, light sensor, etc.
Everything else that should work
What doesn't work:
WiFi
RIL (SIM)
Camera
Media Sounds (I think)
Reboots
Probably some sensors...
Other things I'm forgetting...
The current build that we are testing is available to download from the Downloads section of this thread. You will also need the boot.img downloaded too as it needs to be flashed RIGHT AFTER the ROM to the boot partition. ** NOTE: Before installing this ROM, you need to wipe all partitions in TWRP besides the SD Card, then flash! **
To flash this ROM, you will need cars1189's TWRP OS2SD recovery. It can be downloaded here:
https://www.androidfilehost.com/?fid=95916177934529908
We want your feedback here in the thread! PLEASE post things that are not working in the ROM besides the ones that we currently have listed! **We want help from dev that can get us logs through "adb logcat" to help fix bugs, etc.**
We also have a Telegram group chat setup for you guys to join if you like. The goal there is the same here, test, report, and fix. Logs can be sent to us here as well. You can join here:https://t.me/exhibitdev
XDA:DevDB Information
LineageOS 13.0 for Galaxy Exhibit II 4G, ROM for the Samsung Galaxy Exhibit 4G
Contributors
SJR (Sam), androidlover5842, cars1189
Source Code: http://www.github.com/ancora-tmo
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2017-06-03
Last Updated 2017-06-07

Reserved
Changelog
Changelog is a work in progress, it will be appearing soon...

Reserved

Interesting effort.
It seems like there will be two kinds of issues with this effort: hardware support issues and footprint issues (because the device only has 512MB RAM).
Regarding hardware support: Did you start from "scratch" somehow, or from @cars1189's device tree? The git history at least doesn't reflect that. Since cars1189 had most of the hardware working I would have expected someone to start from there.
For the footprint side, although it may be somewhat counter-intuitive I would guess that you might have better luck with LineageOS 14.1 rather than LineageOS 13. Two data points: nexus 7 "grouper" (with 1GB RAM) seems to perform better with Nougat than with Marshmallow... and also, a new device "jelly" is being released via kickstarter with 512MB RAM and Nougat.

aaopt said:
Interesting effort.
It seems like there will be two kinds of issues with this effort: hardware support issues and footprint issues (because the device only has 512MB RAM).
Regarding hardware support: Did you start from "scratch" somehow, or from @cars1189's device tree? The git history at least doesn't reflect that. Since cars1189 had most of the hardware working I would have expected someone to start from there.
For the footprint side, although it may be somewhat counter-intuitive I would guess that you might have better luck with LineageOS 14.1 rather than LineageOS 13. Two data points: nexus 7 "grouper" (with 1GB RAM) seems to perform better with Nougat than with Marshmallow... and also, a new device "jelly" is being released via kickstarter with 512MB RAM and Nougat.
Click to expand...
Click to collapse
Thanks for the reply! We started with a mix of @sirmordred's and @cars1189's trees and kernels respectively. We are reworking the hardware that doesn't work from some scratch and already written stuff to make it work nicely. @cars1189 cm12.1 was like 100% stable but it wasn't even close when we initially went to build it with LOS13. Nougat would be good to try but MM needs a stable base for now if you get what I mean. We are optimizing RAM as much as possible, currently the system reads 423MB. We are planning some more optimization soon but we are working on fixing rebooting, SE Policy, and such. Otherwise the system UI runs pretty quick right now. In general, MM will be more usable than Nougat but I'll talk to AndroidLover, my helper/dev and bug fixer, and we will figure something out!

aaopt said:
Interesting effort.
It seems like there will be two kinds of issues with this effort: hardware support issues and footprint issues (because the device only has 512MB RAM).
Regarding hardware support: Did you start from "scratch" somehow, or from @cars1189's device tree? The git history at least doesn't reflect that. Since cars1189 had most of the hardware working I would have expected someone to start from there.
For the footprint side, although it may be somewhat counter-intuitive I would guess that you might have better luck with LineageOS 14.1 rather than LineageOS 13. Two data points: nexus 7 "grouper" (with 1GB RAM) seems to perform better with Nougat than with Marshmallow... and also, a new device "jelly" is being released via kickstarter with 512MB RAM and Nougat.
Click to expand...
Click to collapse
SJR (Sam) said:
Thanks for the reply! We started with a mix of @sirmondred's and @cars1189's trees and kernels respectively. We are reworking the hardware that doesn't work from some scratch and already written stuff to make it work nicely. @cars1189 cm12.1 was like 100% stable but it wasn't even close when we initially went to build it with LOS13. Nougat would be good to try but MM needs a stable base for now if you get what I mean. We are optimizing RAM as much as possible, currently the system reads 423MB. We are planning some more optimization soon but we are working on fixing rebooting, SE Policy, and such. Otherwise the system UI runs pretty quick right now. In general, MM will be more usable than Nougat but I'll talk to AndroidLover, my helper/dev and bug fixer, and we will figure something out!
Click to expand...
Click to collapse
Nice to see someone still working on this. Theres definitely many things that need fixing if someone is to update for newer android versions. Last i left off the sensors where being moved open source and while they work on older versions even 5.1.1 had issues with some of them. If anyone wants help or for me to try a build(if you have a bootable base) id be more then happy to help test, I just dont have much time for development. Good Luck!

cars1189 said:
Nice to see someone still working on this. Theres definitely many things that need fixing if someone is to update for newer android versions. Last i left off the sensors where being moved open source and while they work on older versions even 5.1.1 had issues with some of them. If anyone wants help or for me to try a build(if you have a bootable base) id be more then happy to help test, I just dont have much time for development. Good Luck!
Click to expand...
Click to collapse
It would be great to help us out! There is a test build that boots but has some rebooting issues. In the Downloads section of this thread. So yeah, we need a hand with testing and stuf!
Thanks!
Sam

SJR (Sam) said:
It would be great to help us out! There is a test build that boots but has some rebooting issues. In the Downloads section of this thread. So yeah, we need a hand with testing and stuf!
Thanks!
Sam
Click to expand...
Click to collapse
Below is what i found of things that need to be addressed. I however am no able to get it to boot it just keep restarting at the boot animation. Seems like theres still alot to be done.
Code:
#1 ZN7android11MediaPlayer13setDataSourceEPKcPKNS_11KeyedVectorINS_7String8ES4_EE
add /system/lib/libseccameraadaptor.so|libshim_native.so
maybe more after you add this?
Lot of selinux issues id recomment trying with permisive
06-06 09:42:57.670 1 1 I init : type=1400 audit(0.0:3): avc: denied { mounton } for path="/sys/kernel/debug" dev="debugfs" ino=1 scontext=u:r:init:s0 tcontext=u:object_r:debugfs:s0 tclass=dir permissive=1
06-06 09:42:58.270 1 1 I init : type=1400 audit(0.0:4): avc: denied { setattr } for name="mmcblk0p14" dev="tmpfs" ino=4049 scontext=u:r:init:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:5): avc: denied { read } for name="mmcblk0p15" dev="tmpfs" ino=4052 scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:6): avc: denied { open } for name="mmcblk0p15" dev="tmpfs" ino=4052 scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:7): avc: denied { write } for name="mmcblk0p15" dev="tmpfs" ino=4052 scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:8): avc: denied { ioctl } for path="/dev/block/mmcblk0p15" dev="tmpfs" ino=4052 ioctlcmd=127c scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.600 126 126 I multipdp: type=1400 audit(0.0:9): avc: denied { read write } for name="dpram1" dev="tmpfs" ino=3807 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:42:58.600 126 126 I multipdp: type=1400 audit(0.0:10): avc: denied { open } for name="dpram1" dev="tmpfs" ino=3807 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:42:59.991 1 1 I init : type=1400 audit(0.0:11): avc: denied { getattr } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.011 175 175 I init : type=1400 audit(0.0:12): avc: denied { execute } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.011 175 175 I init : type=1400 audit(0.0:13): avc: denied { read open } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.011 175 175 I init : type=1400 audit(0.0:14): avc: denied { execute_no_trans } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.141 179 179 I init : type=1400 audit(0.0:15): avc: denied { execute_no_trans } for path="/system/bin/get_macaddrs" dev="mmcblk0p17" ino=354 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
06-06 09:43:00.381 183 183 I expr : type=1400 audit(0.0:16): avc: denied { write } for path="pipe:[4523]" dev="pipefs" ino=4523 scontext=u:r:toolbox:s0 tcontext=u:r:init:s0 tclass=fifo_file permissive=1
06-06 09:43:01.052 160 160 I surfaceflinger: type=1400 audit(0.0:18): avc: denied { read write } for name="kgsl-2d0" dev="tmpfs" ino=4104 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:43:01.052 160 160 I : type=1400 audit(0.0:19): avc: denied { open } for name="kgsl-2d0" dev="tmpfs" ino=4104 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:43:04.876 1 1 I init : type=1400 audit(0.0:25): avc: denied { getattr } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:04.886 249 249 I init : type=1400 audit(0.0:26): avc: denied { execute } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:04.896 249 249 I init : type=1400 audit(0.0:27): avc: denied { read open } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:04.896 249 249 I init : type=1400 audit(0.0:28): avc: denied { execute_no_trans } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:05.046 168 168 I mediaserver: type=1400 audit(0.0:29): avc: denied { execmod } for path="/system/lib/libaudioalsa.so" dev="mmcblk0p17" ino=1204 scontext=u:r:mediaserver:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
[ 10.267028] type=1400 audit(1496742028.465:23): avc: denied { read write } for pid=160 comm="surfaceflinger" name="msm_rotator" dev="tmpfs" ino=3978 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:audio_device:s0 tclass=chr_file permissive=1
[ 10.338684] type=1400 audit(1496742028.465:24): avc: denied { open } for pid=160 comm="surfaceflinger" name="msm_rotator" dev="tmpfs" ino=3978 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:audio_device:s0 tclass=chr_file permissive=1
Service sdcard needs a SELinux domain defined
LineageOS Version: '13.0-20170526-UNOFFICIAL-ancora_tmo'

cars1189 said:
Below is what i found of things that need to be addressed. I however am no able to get it to boot it just keep restarting at the boot animation. Seems like theres still alot to be done.
Click to expand...
Click to collapse
Oh, sorry! I should include a built boot.img from our cm12 kernel(yours that got androidlover to get it to boot it for now.) THE boot.img is now available in the downloads section. Also if logcat can be posted a zip file or text file, that would be great, or we will find another way to share them.
Sam

Hey all, I added a link to the first post. It includes out new Telegram groupchat link to talk about the phone, etc. in there. Go join it if you like!

We are planning to push out a new build in a day or so that will be much better. Stay posted!! Write us any questions and I will read them!

I'm building tonight, will have a build up tomorrow morning POST around 10ish if it works without build errors. Any of you guys have questions about the ROM, etc. ?

New build is available for download in the threads download section. I'll update the changelog soon. Let me know what works/doesn't work in the new build!
*EDIT* The build I uploaded DOES NOT BOOT! I will reupload tomorrow with a working one. Sorry!

Currently having trouble with libs and things, we are playing around with things to get stuff working, anyone have suggestions?

Hey all, been busy but I want to get back to this phone this week with 13.0 if it's possible for me, anyone want to help me? That would be awesome!
Sam

Hey man, I would love to help, I am not a developer or anything but I can try the builds if you wish. Tried the one in the downloads section but didn't read that it didn't boot so if you have one that I could try I can get back to you and report everything.

Sorry for double posting, was really interested in this and was wondering if you got any news or if you are still working in this, would love a build to play with! hahah ? and thanks to you for this!

Szand said:
Sorry for double posting, was really interested in this and was wondering if you got any news or if you are still working in this, would love a build to play with! hahah ? and thanks to you for this!
Click to expand...
Click to collapse
I really want to get back to this phone, something keeps bringing me back. I'm trying to get a few other devices I have done. For now though, I've been looking at 14.1 as that seems promising. I'll see what I can do any help with development too is much appreciated

SJR (Sam) said:
I really want to get back to this phone, something keeps bringing me back. I'm trying to get a few other devices I have done. For now though, I've been looking at 14.1 as that seems promising. I'll see what I can do any help with development too is much appreciated
Click to expand...
Click to collapse
Thanks man and I would love to help with development but I really don't have any knowledge in it, but I'm looking forward to learning and would if you could tell me where to start. :victory:

Any news?

Grim Fandango Remastered not working with Magisk

Hello everyone,
Grim Fandango Remastered exits immediately when Magisk is installed.
Its working fine with SuperSU.
I am running LineageOS 14.1 on a Xperia Z4 Tablet and tried Magisk 16.0/16.3/16.4.
BTW: Netflix and Prime Video working fine despite CTS Profile failure. Basic integrity check is okay.
Any ideas?
Greetings,
Medizinmann

Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...

Didgeridoohan said:
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Click to expand...
Click to collapse
Here is the logcat.....
Any help appreciated!
Greetings,
Medizinmann

Didgeridoohan said:
Unless you post a logcat from when the app exits, it's gonna be hard to have any ideas...
Click to expand...
Click to collapse
After analyzing the logcat i found the following...
Code:
[ 07-05 20:34:59.404 423: 428 E/Vold ]
ASEC loop device creation failed for /storage/emulated/0/Android/obb/com.doublefine.grimfandangoremastered/main.150.com.doublefine.grimfandangoremastered.obb (Permission denied)
[ 07-05 20:34:59.404 423: 428 W/Vold ]
Returning OperationFailed - no handler for errno 13
[ 07-05 20:34:59.404 1578: 2362 D/VoldConnector ]
RCV <- {400 21 obb operation failed (Permission denied)}
[ 07-05 20:34:59.390 428: 428 W/vold ]
type=1400 audit(0.0:415): avc: denied { getattr } for path="/data/adb/magisk.img" dev="mmcblk0p43" ino=508522 scontext=u:r:vold:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0
The problem seems to be, that the app can’t access their .obb-Files. But why is that?
Greetings,
Medizinmann

Medizinmann said:
The problem seems to be, that the app can’t access their .obb-Files. But why is that?
Click to expand...
Click to collapse
Yes, I saw that as well... And there's been similar reports for other apps.
It's because Magisk is using the loop device, and this seems to conflict with some apps. It's under investigation...

Question ERROR: Reconcile failed: Package com.asus.atd.smmitest has no signatures that match those in shared user android.uid.system; ignoring!]

HI
does anybody know how to get rid of this error:
Code:
1|ASUS_I006D:/sdcard/Download # id
uid=0(root) gid=0(root) groups=0(root) context=u:r:magisk:s0
ASUS_I006D:/sdcard/Download # pm install $PWD/SMMI_TEST.apk
avc: denied { read } for scontext=u:r:system_server:s0 tcontext=u:object_r:fuse:s0 tclass=file permissive=1
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.asus.atd.smmitest has no signatures that match those in shared user android.uid.system; ignoring!]
1|ASUS_I006D:/sdcard/Download #
SMMI_TEST.apk is an app from the original Android for the ASUS Zenfone 8 and I want install it in OmniROM 12 .
regards
Bernd
Update 15.06.2022
Looks like this error can only be fixed by signing the app with the private key used in the running ROM
Update 22.06.2022
The test app works fine on a custom ROM if signed with the private key for that ROM (tested with a self compiled version of OmniROM 12)
Update 25.06.2022
"Resolved" by compiling my own CustomROM -- see How to use the Hardware Test App from ASUS on a Zenfone running a CustomROM
​

from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest

gothta said:
from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest
Click to expand...
Click to collapse
... without that permission the app can be executed but can not do anything anymore