Related
I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/
Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.
Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!
woohoo custom ROMs already. Guess I'll be getting myself the phone after all.
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.
That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.
psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.
they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?
Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..
I've seen a lot of new member here. I hope this thread might help them decide what ROM are best for them and reduce the number of question. however, I won't mention any rom in this forum to keep this thread from my subjective point of view. you should see the development section by yourself to find your best suited rom for you.
OK. lets get straight to the topic. this is some things that you should consider when you choose a custom rom. I'll divide the guide into three main parts two make everything is easy to understand. the parts are performance, style, and additional consideration.
##PERFORMANCE##
Click to expand...
Click to collapse
1. debloatware
debloatware is a process to remove considered useless apk from the system. every rom has different degree of debloatware. a hight degree debloatware means you'll have only use a little of ram space for system app. however we'll lost some of sync function like kies synchronization if we remove all bloatware from the system. make sure that you still have all the app you need from stock rom in your custom rom.
2. deodexed vs odexed
Most of custom rom available is deodexed rom while our stock rom is half deodexed rom. I'll try to explain it in most simple way. First of all, we should understand that mostly every app in android consist of three part, *apk files, *dex/odex files, and lib files.
ODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in same folder with the apk files (/system/app). the positive side, it is tend to more stable and consume less internal memory and a execute faster. it is also faster since the system doesn't have to build dalvik cache at boot process. the negative side, it makes the app uncostumizable (cannot apply custom themes) and need more space in system partition.
DEODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in /data/dalvik-cache. the positive side, the app can be themed (full customizable) and consume less system partition. we could put more app in /system/app in deodexed rom. the negative side, it consume a lot of internal memory. the system also might a little bit slower since the system need to build a lot of dalvik-cache when the phone start.
3. custom kernel
a custom kernel could give you a huge boost of performance. for the most basic one, you should choose a kernel with init.d support. we'll need it to run a lot of performance tweaks. if you're seeing a custom kernel, you should look into these point:
- custom governoor
custom governoor will give you a lot of option to set your device performance. you can set the performance as hight as possible or save your battery as long as possible by set the correct governoor.
- custom scheduler
its almost same with custom governoor. however it manage I/O on your device. it won't give you a huge boost on performance but you should consider it as your main consideration.
- droidwall support
- a2sd and swap support
- additional feature
- bug and rom compatibility
not all custom rom compatible with all custom kernel. make sure that your custom kernel is compatible with your rom.
4. performance tweak availabilty
for a basic consideration, make sure that your rom have a performance tweak. otherwise, you'll got only a themed rom with stock performance. if you're a performance person, make sure your rom is have these tweak.
- memory management optimization
- hsdpa optimization
- kernel and I/O optimization
- gps optimization
- internet speed optimization
these tweaks are could be found at build.prop, init.d, sysctl.conf, and gps.conf.
5. additional tweaks
there are also some additional tweak you should consider if you want to install a rom. the commonly used are:
- bravia engine
- sound enhancement
6. performance app
some ROMs offer performance tweak app like ROM manager inside it. you should consider these app if you're a performance person
##STYLE##
Click to expand...
Click to collapse
1. theme
this is a very subjective topic. you should choose a rom with a topic suit with your style.
2. degree of customization
every rom has certain degree of customization. if you're a themed person, you should consider these point for your rom.
- EDT tweak for statbar customization
- ROM'S lab
- customizer app
- theme availability
3. ROM special app
some of ROM have special app for their rom. they're specially developed for only certain roms and comes with special names and various function. these app will give you a huge power for style and performance customization.
##ADDITIONAL CONSIDERATION##
Click to expand...
Click to collapse
1. update availability
some ROMs are good but they're left undeveloped. you won't get an update for your rom. you should choose a rom with a continous update from the dev to ensure you get the best rom for you.
2. dev support
not all ROM maker are really a dev. some of them just a wannabe dev with a theme modified rom skill. you can't expect them to solve the bug in their rom. you should choose with a good reputation and high skill.
3. rom size
this is not a huge issue. if you have a slow internet connection, a smaller rom is better for you. smaller rom also means a big degree of bloatware. the system will be lighter than the other rom.
4. rom base
some of rom are using old firmware (--KL) while some other are using newer firmware(--LB or newer). you should aware of these stuff since not theme and mod available in our forum are compatible with all firmware. new firmware will give you more stability but in most case you can't have custom bootanimation.
5. multilanguage
this is not a huge issue but you should consider it as well. not all rom support japanese, chinese, arabic, spain and latin fonts.
DISCLAIMER: REMEMBER THAT YOU'LL NEVER GET ALL IN ONE PACKET ROM. ALL ROMS HAVE THEIR STRENGTH POINT. YOU CAN'T EXPECT ANY DEV TO MAKE "A PERFECT" ROM FOR EVERYONE. IF YOU DON'T SATISFY WITH YOUR ROM REMEMBER THAT YOU CAN ALWAYS CUSTOMIZE YOUR ROM BY YOURSELF.
Reserved for dunno
just in case
This thread really help me to create my own custom rom with world best future ......... many many thanks for the great thread .....
Sent from my GT-S6102 using Tapatalk 2
If i use to create odexed rom is it support all tweaks ..
And if i costmize only systemui /firmwork * (deodexed)
With odexed rom its support or not...
Sent from my GT-S6102 using Tapatalk 2
if you want a customizable theme you can make your systemUI.apk as a deodexed apk. if your apk have classes.dex inside it you'll need to delete systemUI.odex from your system.
Can i add a link to this in FAQ bro?
This is basic but very useful for newbies
yes sure...
which rom in your openion is preferrable
which hit high ends
explodeaamir said:
which rom in your openion is preferrable
which hit high ends
Click to expand...
Click to collapse
wat r ur expectations from a rom?
explodeaamir said:
which rom in your openion is preferrable
which hit high ends
Click to expand...
Click to collapse
that is an unending debate, anyway for me
stability - stock ROM
I already have all my tweaks needed for my rom. If anyone asked "what rom do you like?" I'll answered "just a stock rom but with a better graphic and sound driver". however, I'm afraid we've to build it from source to get it
More questions
Great explanations bro, specially for nobs like me
My questions are:
1- How can I know if the ROM totally support Arabic-Language?
I live in Saudi Arabia and My SGY comes with XXLC1 stock ROM.
2- Is there any other stocks than XXLC1 ROMs I can use and still support Arabic and Modem-settings in my region?
I notes that most if not all custom ROMs based on Different stocks than mine.
I know, it sounds like I answered my first question in the second one, but still I need more clarifications.
3- Now I'm using REMIX ROM with [email protected] Kernel, based-band S5360XXLC1. Still, I can't have full Arabic interfaces and
my browsers cant read Arabic too. I wounder why?
Sorry for the very nob questions and Thank you very much.
In this thread there will be mods which are confirmed to work and/or to increase the device performance I will list the following things:
Current Roms which are in development
System Kernels
Custom Scripts
Preformance tweaks
Firstly before any of these Roms, modifications you will need a rooted device. This means that you will need to unlock the bootloader via HTC-DEV.com I will explain how to do this on post number two.
Before you do any of this I am not responsible for any damages, data loss or anything of that nature by doing these mods, if you choose to do them you are at your own risk, if you follow the steps properly you should be fine
Okay now the word of warning is out of the way lets get started...
Roms
The current roms which are practically finished, and are adding little tweaks every release are considered the most stable at the moment and this roms are...
The Nameless Rom by einstein.frat is based on the stock rom or RUU if you like, but with added speed and features such as 3D rosie:
NAMELESS ROM THREAD
The second Rom is also based one the standard sense rom, just with many less applications and with being de-odexed, and is built by mmmcfc:
SLIM SENSE
In this next section there will be work in progress roms, but bear in mind that these roms are not intended for daily use, as of yet, so be warned!
Unofficial CyanogenMod 9 for HTC Desire C, this rom is built by the developer Munjeni, most features are working such as phoning sms but WIFI and some other connectivity and sound hardware don't appear to work properly:
Unofficial Cyanogenmod 9
Kernels
This section will explain how to flash a kernel and which ones to use, you have to be aware that certain kernels will not allow WIFI or other features to work as it has to be hard-coded into the system. Firstly Before you install any Kernels you need to know how to install them properly so the things you will need are:
HTC Sync Manger
HTC Drivers for fastboot
Android sdk
This thread is still being worked on!
Reserved
Reserved for some more info
ORIGINAL CREDIT TO BALDWINGUY77 OVER ON ROOTZWIKI. CHECK OUT THE ORIGINALi: http://rootzwiki.com/topic/36706-ro...a-like-stock-android-442-kot49h/#entry1031982
I'm only port to maguro.
Is a port from original rom no have base maguro only changes for use GSM networks
This ROM is Android Kitkat 4.4.2, build KOT49H. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.2, build KOT49H
Source (AOSP) built kernel (boot.img)
(De)Odexed
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Believe it or not, December is still a month!
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Installation Instructions (VERY IMPORTANT - Note: I use recovery-clockwork-touch-6.0.4.3-maguro)
ROM
pbls said:
By the way TWRP works with this rom.
Click to expand...
Click to collapse
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's Superuser Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. Flash the ROM
OPTIONALS:
11. Root: If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
12. Mod's: If you like any mod you can install zip now
13. Change kernel: U can change aosp stock kernel. Tiny Kernel, Fancy Kernel, Dirty V, Franco Kernel, Mpokang kernel.
14. Reboot your phone, and enjoy!
Toro XDA Thread: http://forum.xda-developers.com/showthread.php?t=2508073
CHANGELOG:
1/12/2014
First Release port on base aospa beta3
1/20/2014
Port 1:1 toro build
Fix panorama preview
2/04/2014
Fix root troubles
DOWNLOADS:
LAST VERSIÓN:
ROM 02/04/14
Mega
Link 1 Google Drive
Link 2 Google Drive
OLD VERSIONS :
ROM 1/20/14
Mega
ROM 1/12/14
Google Drive
Mega
MODS:
Universal Mod's:
AOSP BROWSER: Change Chrome for STOCK browser.
AOSP Mms.apk: Install on system aosp mesaje apk
DPS Manager: Add Cyanongen DPS Manager.
MOD's to 012014:
Return to Stock:
BACK TO STOCK Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Return to ShinyROM Kernel: Returns to Original Shiny Kernel
Tweaks & Look:
36 DPI Nav Bar: Reduces Nav Bar to 36 dpi
Battery Percent Grey
More mod in this url: http://shinyrom.goofball.org/?dir=012014/toro/Mods/inmanster
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
[ Attachment removed - new version up in Official thread ! ]
This is something what I wanted. Love stock(ish) ROMs.
Sent from my Galaxy Nexus using Tapatalk
Drive disabled here, please upload to Dropbox (direct link support) or any other mirror Thanks.
Could someone upload to XDA or Mega?
That's what we have been waiting for! Although Google left us, I wanted our device to be up to date with "stock" ROM. Thanks!
Sent from my Galaxy Nexus using Tapatalk
can someone re-upload somewhere? too many users downloaded from google drive and we're out
If you like, I will upload to my server. Gimme a short feedback.
Best regards, PlusOne.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
can i install the rom by twrp or cwm is obligatory?
I can't download becouse there are too many users trying to get it... please upload on other server
Sorry, you can not view or download this file at this time.
There are too many users who visualized or downloaded this file recently. Try again later access. If the file you are trying to access is particularly large or is being shared by many people, you may tarry up to 24 hours to view or download. If after 24 hours you still can not access the file, please contact your domain administrator.
So did anyone actually manage to download and flash this yet? I'm without Wi-Fi for a couple of days.
osm0sis said:
So did anyone actually manage to download and flash this yet? I'm without Wi-Fi for a couple of days.
Click to expand...
Click to collapse
Not so far... Tried a few minutes ago. Still nothing.
I guess those who ended download tickes flew away :laugh:
It would be great if someone could upload it to Mega.. Thanks!!
(Tried to add it to my Drive too but it keeps giving me problems...)
New link to mega in second post :good:
I liked the ROM, simple and quick. Thank you.
Fantastic job....
Inviato dal mio Nexus 5
Shiny rom,blazzing fast,going to test battery for a few days and post feedback.Thank you sir.By the way TWRP works with this rom.
Finally ROM based on stock without modifications. Will try this
Anyone tried this ROM with mpokang kernel?
@Sesme
osm0sis said:
Amazing! Been hoping someone would do this for awhile! Really looking forward to trying it out!
It mentions SystemUI and framework-res mods over stock; what are they, like completing the white KitKat look? (I hope so!)
Click to expand...
Click to collapse
This ROM is ONLY for SM-T560NU, NOT SM-T560. I CANNOT and WILL NOT make a SM-T560/SM-T561 build as they are different CPU/SoCs.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom. If you are new to flashing custom roms, do NOT attempt this. If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. camera
9. selinux enforcing
10. DRM L3
11. deep sleep
What doesn't work/What isn't tested
1. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread.
2. full disk encryption has been deprecated in Android 13 (LineageOS 20).
Source Code
The build instructions, source code and manifest are listed in post #2 FAQ #1. The kernel source code is at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
Thanks
1. LineageOS team for source code.
2. LineageOS-UL team for merging, maintaining the legacy patches needed for old devices into one common reposistory so everyone can benefit.
https://github.com/orgs/LineageOS-UL/people
3. pre ALPHA testers @RDS5 and @Sigster for willing to test pre ALPHA builds and leaving feedback.
FAQ - I spent hundreds of hours building this rom. If you think it's unreasonable to read this FAQ, then don't use this rom. Thank you.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-20.0
https://github.com/retiredtab/android_device_samsung_gtelwifiue/tree/lineage-20
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-20
The vendor tree files are at
https://github.com/retiredtab/vendor_samsung_gtelwifiue/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-20
The manifest.xml (or roomservice.xml) and build instructions for 20 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/msm8916
Q2. Is this ALPHA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid Jan 2023 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 20 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps. You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-T560NU/TWRP/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. I don't have the time to help newbies, so please do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Do I need to erase everything and format my data?
A10. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q11. What gapps should I use?
A11. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
Q12. I'm having problems with gapps, can you answer why it's not working?
A12. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Q13. Why isn't my post answered or ignored?
A13. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q14. What speed up/optimization tips do you suggest?
A14.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q15. Does this rom support Magisk for root?
A15. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q16. Will this rom ever become official?
A16. Starting with 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q17. What is the difference between this rom and others?
A17. This rom tries to be pure LineageOS with little to no modifications.
Q18. Will there be any major 20 code modifications in the future?
A18. I don't anticipate any major modifications. There may be some small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 20 is working.
Q19. Why did you fork the device and vendor trees for 20?
A19. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T357W, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not.
I have completely decommonized and rearranged the 20 msm8916-common tree so it's easier for me to maintain and build.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q22. I don't like the taskbar, how do I turn it off?
A22. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q23. Will this run on the SM-T560 or SM-T561?
A23. No, the SM-T560 and SM-T561 use a different CPU/SoC. The SM-T560NU rom will NOT work on SM T560/SM-T561. I CANNOT and WILL NOT build SM-T560 and SM-T561.
Q24. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A24. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-T560NU/20/
Release notes
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
June 23, 2023
1. Initial 20 ALPHA public release.
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"
Reserved.