Cyanogenmod 13?????? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Will cyanogenmod 13 come to the kindle fire hd 7 (Tate)?

Yep, @BuQQzz and I (mostly him, haha) are working on porting CM13 to this device, as well as the 8.9" (jem). I'm not exactly sure when a usable build will be uploaded, but it should be in the not-so-distant future.

I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?
Two, what steps can I take to make sure I am running the best I can for the best results?
The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.
If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.

Jaybone073 said:
I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?
Two, what steps can I take to make sure I am running the best I can for the best results?
The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.
If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.
Click to expand...
Click to collapse
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.
2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.
You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.

monster1612 said:
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.
2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.
You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.
Click to expand...
Click to collapse
I stand corrected. There is no external slot. I was mistaking the back logo panel as a possible external storage cover. My son has had the device for quite some time and he asked dad (me) to give it the "works". The device was running atrocious and much slower than it does now. I've had it for about 2 months and after installing the 2nd bootloader, rooting, twrp recovery..... You get the idea, I had it very stable and clean. It's been running quite well on 12.1 and I am pleased to see development still happening for such an older device.
As far as apps go, I have only installed what he likes. A few games (about 4) and a couple of social ones like Instagram and facebook for him. The real slowdown was actually with Facebook continually not updating and having errors. A recent reboot has fixed that. It also appears that the occasional reboot is actually helping the rom settle in.
I had previously tried the CyanDelta Updater on the play store and it didn't work well. I will now give CM Downloader a try to see of that keeps me from having to reflash the GApps and other apk that seem to force close that I had previously mentioned.
Thanks for the quick response and advice.

Jaybone073 said:
I stand corrected. There is no external slot. I was mistaking the back logo panel as a possible external storage cover. My son has had the device for quite some time and he asked dad (me) to give it the "works". The device was running atrocious and much slower than it does now. I've had it for about 2 months and after installing the 2nd bootloader, rooting, twrp recovery..... You get the idea, I had it very stable and clean. It's been running quite well on 12.1 and I am pleased to see development still happening for such an older device.
As far as apps go, I have only installed what he likes. A few games (about 4) and a couple of social ones like Instagram and facebook for him. The real slowdown was actually with Facebook continually not updating and having errors. A recent reboot has fixed that. It also appears that the occasional reboot is actually helping the rom settle in.
I had previously tried the CyanDelta Updater on the play store and it didn't work well. I will now give CM Downloader a try to see of that keeps me from having to reflash the GApps and other apk that seem to force close that I had previously mentioned.
Thanks for the quick response and advice.
Click to expand...
Click to collapse
If you go into the CM Downloader app settings, you should be able to add in the zips (maximum of 6) you want flashed after a ROM update. Once that's complete, all you need to do is download an update and initialize the install process from within the app, and it'll handle flashing the zips. From personal experience on CM nightlies for jem (the 8.9" version), I tend to see stability break down after about 24 hours of device uptime without a reboot, so reboots do help significantly.

Any progress so far?

Pix12 said:
Any progress so far?
Click to expand...
Click to collapse
Currently, the generated zips take longer than cm12.1 to flash (but they still flash successfully). As for a functional ROM, that hasn't happened yet - it refuses to boot after about 5 seconds. last_kmsg says it's an SELinux issue.

Related

[ROM][NANDROID-BACKUP] minusculeShield 1.0

minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)
This is great. Will give this a shot today or tomorrow. Thanks!
themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.
I still get notification prompts for ota.
themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way

[ROM/A1/Recovery][Wifi+3G+TMobile][4.4.4/2.8][Oct 27]Omni Based Rom and TWRP

Summarized Standard Disclaimer: use at your own risk. I use it at mine.
*Full wipe recommended if coming from another kitkat rom*
MAKE SURE TO HAVE A BROWSER APK. THERE IS NO MORE STOCK BROWSER. For firefox see below.
My personal build "Diamond Rom 4.4" is based on omnirom with the following additions:
CM Calculator (the newly redone one they're proud of)
CM File Manager
CM Wallpapers
Bash shell
Nano text editor
Powertop
Koush's full featured open source superuser (and it's INTEGRATED into settings :cyclops: )
Carbon rom blue balls wallpaper
Cyanogenmod port of 2 column settings adapted to Omni rom.
Omni floating window
I've added a few of my personal touches which include
Batter circle color changing: green 100%-51% yellow 50%-16% red 15%-0% This was my favorite I9000M framework-res mod that I've missed since switching to CM7.2 way back.
Killed lock screen music full screen (personal privacy thing when riding public transportation)
Disable android external storage management: messes with ext4 formatted hard drives or multi partitioned hard drives. Use the unix style mount command
Disable hardware keyboard on boot: disabled but not removed. You'll have to manually turn it on
Removed camera sounds
Disable SELinux at the kernel level. It's even disabled on my laptop/desktop at the kernel because it seems like it's more trouble than it's worth.
Put the dalvik cache in the cache partition. Don't waste the data partition for it. :cyclops:
And of course, comes bundled with my A1 kernel :cyclops:
Every thing I've tested: camera, youtube hd, sound, gps, usb otg(use manual mount command) etc work.
*Instructions*
First time flashing omni:
-Read second post FAQ and other important information.
-Flash TWRP (you can flash twrp over cwm from cwm if you're in that situation)
-Reboot into new recovery
-Make recovery backup (optional)
-Run Titanium Backup (highly recommended)
-Full wipe
-Format system partition
-Install ROM
-Install gapps
-Reboot :cyclops:
Subsequent flashes:
-Install ROM
Downloads
Mediafire Wifi download folder with md5sum file
Mediafire 3G download folder with md5sum file
Mediafire TMobile download folder with md5sum file
*Authorization to download is just a captcha. Simply enter the text in the picture or name the item being advertised in the picture.* Mediafire sure beats sh***y sites like uploaded.net or rapidgator
A1 Kernel (as its own download)
V1.9.2: Security fix made aware by cyanogenmod, specifically this. The commit message on my github has a copy and paste mistake. It should list both of those security flaws as patched instead of the same one twice. Oops :cyclops: Security fix comes with ALL roms June 28 and onwards.
3G/Wifi 6ff199d6c9037d222a70ec0c561c8028
TMobile a675fd353ad3ad7dbf8e6bf2109fa360
TWRP Recovery
2.7.1.0 Wifi 6c995325e749e7561893e398847b09a0
2.7.1.0 3G 8fa04be69d0faf3d9a134e829ddff680
2.7.1.0 Wifi July 8 a8d12c13aac7430a319369069d814e72
2.7.1.0 3G July 8 dc1c50622c29c621f29b95f4c53734ea
2.7.1.0 Wifi August 11 b2c21e8fd58dc38a9c8b7669031b84b1
2.7.1.0 3G August 11 9f48defe78391e63a9053cbd281f738f
2.7.1.0 TMobile August 11 87fb29c803a2e3a56d98a1475c5fce8f
2.8.0.0 Wifi cfdac70d0ccac34cf220887eab72f8b0
2.8.0.0 3G d7918eb397f54c484e04a6d5cb07945c
2.8.0.0 TMobile aaf7c6d2455ca32178ec846f5186c774
Newer versions of firefox explicitly disable flash on tegra2. Use my firefox mod which is just normal firefox with a hacked tegra2 blacklisting mechanism. Don't use the old firefox apk. It has unpatched security holes.
Changelog: omnirom gerrit
Sources: https://github.com/AAccount?tab=repositories Has my device trees as well as all the omni repos I forked with my additions.
Credits:
Kasper_h: helping to make 4.4 possible
pershoot: original device tree from CM10.1
Omni team: providing great starter rom and keeping it TF101 compatible
fred6681: original gapps package. I just removed the 4.4.2 check
Cyanogenmod team: rom extras like calculator, superuser, to fill in Omni's missing holes and 2 panel settings template.
XDA:DevDB Information
Omnirom+ 4.4 for Galaxy Tab 10.1, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Stable
Created 2014-10-12
Last Updated 2014-10-11
Known Issues:
Wifi signal indicator and speed indicator don't show up
No list of 3G APN. Write down your settings first
Bluetooth audio issues
Recovery adb doesn't start automatically. In recovery, go to Advanced --> ADB Sideload and start it. You can then cancel it if you don't want to use that. It just starts the recovery adb and will continue to run until you reboot. fixed thanks to twa_priv
Use another recovery for TMobile. Apparently the twrps I make can't boot on TMobile hardware even though it boots on my Wifi only.
FAQ
How do I get multi window: Settings-->(second) More --> App circle bar (check box) && --> Included apps (choose what you want available in multi window)
Yes you can flash TWRP over CWM
Random flickering: Try Settings-->Developer options -->Disable HW Overlays.
Can't install a very large quantity of apps: fix
Can't mount ext4 media: kill the e2fsck process assuming you safely removed the media before sticking into the tablet.
(Below this is optional)
(Android device manager does have legitimate uses. However, please read and consider the following paranoid but realistic fantasy:)
Completely disable android device manager: By only going to Settings->Security->Device administrators and un checking "Android Device Manager" this doesn't completely remove the ability for google to send in commands to your device. Go to the google play store through a web browser, choose android device manager, and try "ringing" your device. To my horror, my tablet started to ring as if it got a phone call. I don't find it acceptable that gapps gives google a way to setup a remote command and control operation. In any other operating system this is considered a back door or virus.
To close this back door install Xprivacy. Enable system apps to be modified. Look for the entry (should be highlghted in red to indicate a system app) "Google Account Manager, Google Backup Transport... (lots of items here) ...Google Services Framework". Check mark Notifications and open its menu. Check mark the items in red. These are cloud to device (c2d) permissions which do exactly what you think. While not necessary, disable identification too for good measure. This disabled the ring feature on my tablet which means android device manager should no longer be able to send in commands. I don't have the guts to try the device wipe feature but it should work too. Do not disable location otherwise google maps won't be able to find you which means no gps car navigation.
See this post about building from source. I use a different, simpler trick for prebuilt chromium binaries. Fear not, they are source built but only when there are real source changes. They're just recycled in between to save 90mins/build of time.
Downloading now!! Thanks for your work!!
Enviado desde mi GT-I9195 mediante Tapatalk
Another 4.4.3 for the tab?
Thank you very much!
Hi AAccount,
thanks for your 4.4.3 ROM, sounds promising ... however, what about the graphical glitches on that vesion? I always went back to ROM version CM10.2/SGT7 as this seems to be the latest one without those glitches (last version I tried was Nameless ROM version 4.4.2 where they were still visible ... and annoying).
Thanks in advance,
mistersixt.
Great job!! Runs fast without bugs and glitches, only youtube HD...
The best kitkat rom!! Thanks !
Enviado desde mi GT-P7510 mediante Tapatalk
Best kitkat rom. I have some glitches. It is not as smooth as cm10.2 so i am going back to cm10.2.
What graphical glitches do you mean? I think ever since omni fixed the screenshot way back most graphical bugs have been ironed out. By youtube hd do you mean it doesn't play or can be laggy? If you mean laggy I read on wikipedia the GPU video decoding on the tegra2 sucks. That's a hardware problem.
3G build and new recovery coming later today. I cheated the chrome renderer build process by copying all the freshly done ones from the wifi only output folder.
My github is now fully up to date with all the appropriate omni repos forked with my personal touches whether it be the audio blob fixes or little things I like.
Sent from my GT-P7510
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
AAccount said:
What graphical glitches do you mean?
Click to expand...
Click to collapse
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
lancem71 said:
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I added instructions. There's no really preferred gapps package. I just like that one because it's the smallest one that gets the job done. There are some gapps packages that are bigger than the rom which I consider bloated.
mistersixt said:
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
Click to expand...
Click to collapse
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Great room, thanks! Everything working OK during the first hour of use
Sent from my GT-P7500 using XDA Free mobile app
Thanks for posting this! Great ROM. Only problem I'm having is the APN settings are blank for my 3G tablet (P7500). I input them manually and everything works, but normally they are preset.
AAccount said:
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Click to expand...
Click to collapse
Many thanks for this!
"Disable HW overlays"- for some reason this setting does not stick between reboots (not your ROM problem- it happens in all devices that I've ever seen). Is there a way to apply it automatically during or after boot? Such as in a script, or init settings etc?
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
jaibar said:
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
Click to expand...
Click to collapse
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
AAccount said:
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
Click to expand...
Click to collapse
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
jaibar said:
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Same around 2xx mb. I'm fine with it, since the 400mb in /cache is wasted anyway.
Sent from my GT-P7500 using Tapatalk
223MB here
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Sendt fra min GT-I9305 med Tapatalk
thra1982 said:
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Click to expand...
Click to collapse
Every time somebody asks about Netflix... I fell I'm missing something big...

[Q] New to Droid

I just got my Droid 4 off of Ebay, and I'm going back to Android after 5 long years of Windows Phone. Rooted and installed the latest version of Safestrap that lets us used the (now)unused partitions. Seeing the lack of ROM diversities, My question is: Which ROM should I install? xD
All the Marshmallow ones and the Lollipop one I tried where really slow after installing just a few apps. So I went back to 4.1.2. There is a KitKat one that I'd like to try but the links are dead. I also found a thread suggesting to modify the booting of Cyanogen 12 with apparently good results, but I didn't look too much into how to do that.
Tbh I'd love something like SFOS but it looks like it's being worked on right now. So it might be a while till it's ready for daily usage, if it's ever brought to that point. :/
peter768 said:
I just got my Droid 4 off of Ebay, and I'm going back to Android after 5 long years of Windows Phone. Rooted and installed the latest version of Safestrap that lets us used the (now)unused partitions. Seeing the lack of ROM diversities, My question is: Which ROM should I install? xD
All the Marshmallow ones and the Lollipop one I tried where really slow after installing just a few apps. So I went back to 4.1.2. There is a KitKat one that I'd like to try but the links are dead. I also found a thread suggesting to modify the booting of Cyanogen 12 with apparently good results, but I didn't look too much into how to do that.
Tbh I'd love something like SFOS but it looks like it's being worked on right now. So it might be a while till it's ready for daily usage, if it's ever brought to that point. :/
Click to expand...
Click to collapse
Hello,
I'm using stock one JB 4.1.2, heavy debloated and overclocked. You can add some functionality from other roms by instaling xposed.
I recommend the latest Lineage 13.0 ROM. This is my daily driver and it's amazing.
I also have Mentors' debloated Stock ROM for dualboot, in case I ever need it. The biggest contra of the Stock ROM is the extremely bad GPU performance. It can't even display Snapchat because there are graphical errors everywhere. It also stutters while scrolling in a lot of apps.
These problems are all gone with CM13. I played through Red Dwarf on it and the game worked smooth as butter, with some nice, detailed graphics. Get an overclocked kernel from the forums here, while you're at it.
You should also never use the Stock ROM as the main system, because it lacks years of updates and has severe security holes in it.
schmatzler said:
I recommend the latest Lineage 13.0 ROM. This is my daily driver and it's amazing.
I also have Mentors' debloated Stock ROM for dualboot, in case I ever need it. The biggest contra of the Stock ROM is the extremely bad GPU performance. It can't even display Snapchat because there are graphical errors everywhere. It also stutters while scrolling in a lot of apps.
These problems are all gone with CM13. I played through Red Dwarf on it and the game worked smooth as butter, with some nice, detailed graphics. Get an overclocked kernel from the forums here, while you're at it.
You should also never use the Stock ROM as the main system, because it lacks years of updates and has severe security holes in it.
Click to expand...
Click to collapse
I tried Lineage with an overclocked kernel yesterdat but it was still quite laggy. I also couldn't install the google apps due to insufficient space. Did you do anything else? Also I'm on cdma so I stayed away from Mentor's ROMs.
Instead of the original GAPPS, I'm using:
- XPosed
- the FakeGapps module for XPosed
- the MicroG Play Services from here
- and the Google Play Store. Got the APK from apkmirror, installed it, copied the files from /data/app/com.android.vending to /system/priv-app/com.android.vending and chmodded the files to 644 and directories to 755 (this has to be done, otherwise the Play Store cannot login).
This is a bit of work, but it runs much faster and doesn't drain my battery as fast as the original GAPPS do. The last step isn't even required, you can use FakeStore or BlankStore instead and just get all your applications from apkmirror if you want it.
Bonus feature: You can now use Google Maps with the Apple NLP backend.
schmatzler said:
Instead of the original GAPPS, I'm using:
- XPosed
- the FakeGapps module for XPosed
- the MicroG Play Services from here
- and the Google Play Store. Got the APK from apkmirror, installed it, copied the files from /data/app/com.android.vending to /system/priv-app/com.android.vending and chmodded the files to 644 and directories to 755 (this has to be done, otherwise the Play Store cannot login).
This is a bit of work, but it runs much faster and doesn't drain my battery as fast as the original GAPPS do. The last step isn't even required, you can use FakeStore or BlankStore instead and just get all your applications from apkmirror if you want it.
Bonus feature: You can now use Google Maps with the Apple NLP backend.
Click to expand...
Click to collapse
I tried to follow this, but Google Play Store crashes. When I run the app, the Google Account is created, but thats it, I cannot run Play Store. Do you have any advice?
It still works fine for me with the same instructions posted above.
Maybe you have a different version of the PlayStore? Mine is from here and doesn't crash:
http://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-7-8-32-release/
You may have to kill the app after the first login and open it again so you can accept the EULA, though. Otherwise you'll get a connection error.
(Useful: 5 second back button killing in the developer options.)
If it still doesn't work:
- Open up the microG Settings and check if signature spoofing is indeed enabled
- Open up Xposed and check if the FakeGapps module is activated. If it isn't, activate it and reboot.
---
A completely different, even more lightweight method to get PlayStore and microG working:
1. Flash the latest LOS13 ROM.
2. Enable ADB debugging on the device and connect it via USB to your PC.
3. Install adb and python on your PC and run the Tingle application (cmd.exe: "python main.py")
This will patch the installed ROM on the fly and replace a system file. It enables signature spoofing, which means fake Google Play Services will run WITHOUT XPosed. No XPosed means even more free resources on the device.
The rest of the instructions is unchanged:
4. Get the MicroG Play Services from here
5. Get the Google Play Store from apkmirror, install it, copy the files from /data/app/com.android.vending to /system/priv-app/com.android.vending and chmod the files to 644 and directories to 755 (this has to be done, otherwise the Play Store cannot login).
This method is a lot more extensive, especially on Windows systems where you'll have to install ADB and make it visible in the system path. You'll also have to install python manually. A pain. Much easier on a Linux system.
But it's the only method to make it work on LOS14 at the moment, because there is no XPosed for Android 7 out yet AND the only method for people who don't want to use XPosed.
Just FYI, maybe this helps someone.
peter768 said:
There is a KitKat one that I'd like to try but the links are dead.
Click to expand...
Click to collapse
You can get CM11 and other CyanogenMods for Droid 4 here - http://web.archive.org/web/20161226224516/http://download.cyanogenmod.org/?device=maserati.
peter768 said:
Tbh I'd love something like SFOS but it looks like it's being worked on right now. So it might be a while till it's ready for daily usage, if it's ever brought to that point. :/
Click to expand...
Click to collapse
You can get Sailfish OS for Motorola Droid 4 here - https://talk.maemo.org/showthread.php?t=99031.
It's not 100% stable but worth trying out (though not as daily driver for me).
Of course using Safestrap you can have more than one ROM installed on the device so you can follow the development of each ROM/OS you are interested in.
For example I have CM11 as my daily driver, stock ROM in case of problems (didn't have to start it until now) and Sailfish OS to look on its development.
schmatzler said:
You may have to kill the app after the first login and open it again so you can accept the EULA, though. Otherwise you'll get a connection error.
(Useful: 5 second back button killing in the developer options.)
.
Click to expand...
Click to collapse
Many thanks, this was the issue. Works perfectly also with newer play store version.
After some frustration with LOS13 (Bluetooth not working, laggy performance) I'm using now Mokee ROM (with FakeGapps for Xposed). Workes nicely, especially I appreciate the Aegis app for controlling app behaviour (autorun, wakelocks, background services, hibernate, broadcasts). Restarting the phone every 2nd day prevents performance lags which build up slowly.

[ROM][Pie] Unofficial LineageOS 16.0

This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. Installing google apps requires some apps to move to data partition because of limited system size. See install description for more info.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-The camera preview image sometimes shakes at random
Download
https://mega.nz/#F!5fBWlIAQ!Jlq9Bj789iJ0iIIptK00tg
Update
If you already run an earlier version of this rom, just boot to twrp and install the latest flashable zip file
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz link is in section download)
5. If you want to install opengapps or need system partition space for other things. Install the move_to_data.zip file from the attachments. This will move the Webview and the LatinIME app to data partition.
6. Choose one of the following options:
-either install google apps (download form https://opengapps.org/. Choose x86 9.0 nano or pico)
-or install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360) this is lighter in ram and cpu usage but you will get problems with google chrome and other apps
7. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
8. Reboot the phone. First reboot will take some time
Changelog
Code:
20191018:
fixed problem with sms receiving
20191012:
mobile network connection works now after boot
Fixed problems with network switching
Show taps option is working now
intel art extension enabled
Call recording enabled
text relocation warnings disbaled
(untested) encryption. Needs special configuration (see below)
20190819:
SELinux is now enforcing
Notification access feature enabled
solved crashes with houdini emulated apps
20190713:
usb configuration works properly
battery light works now
July security patches
20190704:
first stable release of this rom
DATA Encryption
If you want to enable data encryption this would break the pds partition backup. To prevent this, the cache partition can be used as backup location:
-edit /system/bin/pdsbackup.sh
-change PDS_FILE=/data/misc/pds/pdsdata.img to PDS_FILE=/cache/misc/pds/pdsdata.img
-resize data partition in TWRP:
Code:
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk0p17
resize2fs /dev/block/mmcblk0p17 1367079
-reboot the phone
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-08-19
Created 2019-07-04
Last Updated 2019-08-19
This if I did not expect it, I'll try to see how it goes. Thank you.
Download links and install description are up now. Download from mega.nz because xda download section is broken at the moment. I'm waiting for your test reports
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
BTW, performance is really great, seems to be almost same as Lineage 11.
dumkm said:
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
Click to expand...
Click to collapse
I also noticed that. Will see how this can be fixed. It is just a problem with the option dialog. Usb connection works fine. As a workaround you can set a default USB configuration in developer options
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I have not tested storage encryption yet. Will have a look at it later
dumkm said:
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
Click to expand...
Click to collapse
I think lineage trust doesn't differentiate between permissive and disabled. Selinux support is planned for future releases
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
dumkm said:
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
Click to expand...
Click to collapse
Notification Led should work. Can be configured under settings->apps and notifications->notifications->notification light. I don't know what happened with the battery light. It will hopefully come back if I upgrade the driver to hidl.
Google Chrome is a known problem with MicroG. It requires official gapps. I will check if some of the unprivileged lineage apps can be moved to data partition to make place for google apps
Newbie question
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
dumkm said:
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
Click to expand...
Click to collapse
That's good. Than we can make a flashable zip to automatically move and symlink them to data partition.
I will provide a new build till end of the week with improved usb and notification LED implementation. I already got it working in my local setup
flameseewa said:
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Click to expand...
Click to collapse
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
julianwi said:
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
Click to expand...
Click to collapse
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
TWRP error 70
julianwi said:
This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. I don't know how smooth it runs with official gapps.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-Mobile cell connection doesn't connect after boot. You have to turn airplane mode on and off to let it work.
-selinux is set to permissive for now (reduced security)
Please report more bugs if you test this rom
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz https://mega.nz/#!ICwXRC6D!VZqe3o5zeWbmMiZvka_BtUTW5T_V7_OdMS57Oe9CbMk)
5. Choose one of the following options:
-either install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360)
-or install google apps (download form https://opengapps.org/. Choose x86 9.0 pico)
6. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
7. Reboot the phone. First reboot will take some time
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-07-04
Created 2019-07-04
Last Updated 2019-07-05
Click to expand...
Click to collapse
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Kazvko said:
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Click to expand...
Click to collapse
Yes, system partition size is limited on this phone. To install GApps some files need to be moved to data partition.
I created a flashable zip to automate this process. Take a look at the modified install description in the first post
New build is up now.
flameseewa said:
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
Click to expand...
Click to collapse
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
julianwi said:
New build is up now.
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
Click to expand...
Click to collapse
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
dumkm said:
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
Click to expand...
Click to collapse
I know, haven't looked at the storage encryption for now. It will maybe be in the next update next month
flameseewa said:
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
Click to expand...
Click to collapse
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
julianwi said:
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
Click to expand...
Click to collapse
That's an old guide, will everything still work?
flameseewa said:
That's an old guide, will everything still work?
Click to expand...
Click to collapse
Yes, it should still work the same. If some links are outdated you can google them yourself
Thank you for bringing my old RAZR i back to life! I really appreciate the time and effort you spent for this obselete phone. Looking forward for more updates and for a bug free ROM. Using it now
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I'm not sure if I misunderstood but when you said "it required deleting....." and "reducing partition size of data", did you mean you can get WiFi to work if you do those things? I'm no expert at these but I can atleast apply the "fix" (if it really is) given that you guide me, if it's okay with you. Thanks!

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for SM-T813 - June 9, 2023

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.
This is ONLY for the T813. I do not have and will NOT build T713, T719 and T819. See post #2, FAQ 20. Any questions asking to build these will be ignored.
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. selinux enforcing
9. deep sleep
10 DRM level 3 (SD definition)
Known issues/What doesn't work/what's not tested
NOTE: If any following features are important to you, don't use this rom as I will not be fixing them because I
i. don't use/need that feature
ii. already tried fixing it and couldn't succeed and won't spend anymore time on it.
1. Stock camera doesn't work at all (reason i and ii). Opencamera version 1.51.1 works for taking pictures and videos BUT with a 10 to 15 second delay when switching between functions.
I have not tested any video conferencing apps so they may or may not work. If they don't work, revert back to old rom as I will not be spending anytime trying to fix/troubleshoot.
2. fingerprint (reason i). I never use it and I see it doesn't even load correctly in the logs.
3. ARM64 gapps (reason i). 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 ARM64 gapps.
There are various gapps projects (at least 5 in 2023). 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/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, I have opened a new thread at
https://forum.xda-developers.com/t/...o-use-discussion-for-18-1-rom-sm-t813.4540423
so you may discuss gapps. I will NOT be participating in that thread as I do NOT use gapps.
4. disk encryption (reason i). Never tested.
5. If you restart the device with the purpose to reboot it and the usb cable is plugged in, the device will not reboot and stay in charging mode. Simply unplug the usb cable, wait 15 seconds and restart the device.
Source code
All the source code including the kernel is provided in post #2 FAQ1.
Thanks
1. LineageOS team for source code.
The rest in alphabetical order.
2. @Deltadroid for updating the msm8976 kernel for branches 14.1 and 16.0 with bug and security fixes. I'm using his 16.0 branch.
3. @lifehackerhansol for suggesting that I kang the pm-* proprietary blobs from another rom and making suggestions for possible fixes to the camera.
4. Team Infusion Developers github.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/syphyr/android_kernel_samsung_msm8976/tree/lineage-16.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8976-common
https://github.com/retiredtab/android_device_samsung_gts210vewifi
The vendor tree files are at
https://github.com/retiredtab/proprietary_vendor_samsung_msm8976
The manifest.xml (or roomservice.xml) and build instructions for 18.1 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
Q2. Is this BETA 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 Oct 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 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. 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.6.2_9-0. Do not use any other version for these reasons.
https://forum.xda-developers.com/t/...or-sm-t810-jan-11-2023.4430349/#post-86745013
https://dl.twrp.me/gts210vewifi/
I will not answer questions if you don't use this exact TWRP version.
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. In addition, I don't run Windows OS at all.
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. Will you build 19.1 and higher for this device?
A10. Any questions on higher Android versions will be completely ignored. I do this in my free/spare time and will not be subject to any ETAs or demands. If you want a higher version, the source code is freely available as per FAQ #1 and you can build it yourself.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.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.
You MUST FORMAT DATA in TWRP so backup your files first to some external storage (external microsd or PC).
NOTE: After you do the above, first boot (without gapps, magisk, etc) will take about 90 seconds. It may pop with a message saying "System UI isn't responding". Hit close app and then reboot the tablet again.
Q12. What gapps should I use?
A12. 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 ARM64 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.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system".
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. 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.
Questions about gapps, for your courtesy, should be asked in the thread below.
https://forum.xda-developers.com/t/...-use-discussion-for-18-1-rom-sm-t813.4540423/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q15. What speed up/optimization tips do you suggest?
A15.
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. Use a web browser like Brave that has built in adblock and privacy features.
4. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
5. Look for apps that are open source, ad free and lightweight.
Q16. Does this rom support Magisk for root?
A16. I don't use Magisk. Magisk is always being updated to fool Google's certification process which may or may not work.
Q17. Will this rom ever become official?
A17. Never. I don't want the responsibilities that come with being an official maintainer.
Q18. What is the difference between this rom and others?
A18. This rom tries to be pure LineageOS with little to no modifications.
Q19. Will there be any major 18.1 code modifications in the future?
A19. 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 completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working.
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. To be clear, I will NOT build T713, T719 and T819.
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. Does this rom support OTA updates?
A22. No and I have no plans to add that functionality.
Q23. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A23. You can download it from
https://sourceforge.net/projects/retiredtab/files/SM-T813/18.1/
Release Notes
I have personally tested all the functionality as to what works as per post #1 before uploading the build. 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. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since May 5th patches (about 5,600 files had to be recompiled).
May 7, 2023 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since Apr 5th patches (about 6,600 files had to be recompiled).
Apr 15, 2023 release notes
1. Incorporates Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since Mar 5th patches (about 4,500 files had to be recompiled).
3. Updated aptX code so that it works and stops crashing (broken in 17.1) as per https://github.com/retiredtab/propr...mmit/3f6bd0d979ae25e3ba23e2c214fa7207c81f6b32
March 17, 2023 release notes
1. Incorporates Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since Feb 5th patches (about 24,000 files had to be recompiled).
3. Added overlay to control capactive key light buttons to enable/disable or change duration as per
https://github.com/retiredtab/andro...mmit/5a2649a040adfb879fd03076f97dd5321c5e27e6
Feb 13, 2023 release notes
1. Incorporates Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since Jan 5th patches (about 13,000 files had to be recompiled).
3. Updated DRM code so that Disney+ works. See
https://github.com/retiredtab/andro...mmit/6c41d16cf1a8b2e8c436b3bef922a47e606381ee
https://github.com/retiredtab/propr...mmit/fed0f34d48330908165f78051066127b0e1870d8
Jan 7, 2023 release notes
1. Initial release of 18.1
2. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
3. If you are upgrading from a custom rom, stock or any older versions of LineageOS (like 14.1, 16.0 or 17.1) YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA in TWRP. You cannot dirty flash at all. Backup your data first.
Reserved #4
I have personally tested all the functionality as to what works as per post #1 before uploading the build. 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. This is known has a clean install. Backup your data before a clean install.
18.1 has been my daily driver since Oct 2022.
Jan 7, 2023 release notes
1. YOU MUST read posts 1-4 if you haven't already.
2. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
3. If you are upgrading from a custom rom, stock or any older versions of LineageOS (like 14.1, 16.0 or 17.1) YOU MUST wipe dalvik/cache, cache, system, data and internal storage partitions in TWRP and FORMAT DATA in TWRP. You cannot dirty flash at all. Backup your data first.
Thanks for all your efforts. I never thought anything above Android 10 would see the light of days on the T813 model, since it was highly neglected here in my opinion. I will definitly try it out
THANK YOU "RETIREDTAB" this is awesome!
I will try it out on my T813 and report back here if there are any problems, Thanks a lot for this rom!!!
@retiredtab, many, many thanks for this rom. Have done a full clean install, the backup of the previous 17.1 took longer. So far everything I need to use is working perfectly. I mainly read the news, pick up emails and buy too much stuff from amazon.
went with the opengapps pico set, and all my google stuff is working, and it restored my apps from the previous backup. Did have some odd issues giving permissions to to the various google apps but once that was sorted it ran.
keep up the good work, and will keep testing
Further update after a weekend of use, the screen off battery drain seems to be minimal(may be Greenify helping) but appears to be better than I had on the previous 17.1 rom. No other issues found as yet.
will the camera issue be adressed or it will stay like that?
Ferchurito said:
will the camera issue be adressed or it will stay like that?
Click to expand...
Click to collapse
I'd say its unlikely to change, far as I know its never been fixed in the previous 17.1 rom either. As retiredtab mentions in point 1, camera use is not a big need or he has alrady tried to fix it and not been able to.
I did everything wrong with a working result:
-My Starting point: LineageOS 17.1 (ripee) installed
- Backup of User Data @ Android System (copy to MicroSD)
- Updated the TWRP version to the recommended in TWRP (coming from ripee version for 17.1)
- Boot to System to ensure it's still working
- Backup everything in TWRP
In one batch without booting in between:
- I dirty flashed "lineageOS 18.1" over "lineageOS 17.1 (from ripee)"
- Flashed the Arm64 version for Android 11 of "mindTheGapps" over existing "OpenGapps (for Android 10)"
- Flashed Magisk *.zip
- Deleted Cache and Dalvik
Boot to system and it's working perfectly so far
FYI.: Camera App "ProcamX" is working as well.
FYI.: Especially for lineageOS 17.1 users: I can confirm GPS is working (GPS Test Plus)
For sure I wouldn't recommend this procedure and maybe I will do a clean install later to gain smoothness and to make it stable in general but so far it's super nice, no bootloop, random restarts (BUT it's based on a few hour usage only) or whatever and a big thank you to ritiredtab
I have Magisk and safetynet pass flashed. I can download Netflix from Playstore but it doesn't play any content. It seems that Widevine / DRM is not part of the ROM at all as the App "DRM Info" doesn't show any Widevine information. In consequence Netflix doesn't play and stuck in "loading". Anyway it seems to enable some old DRM blobs can fix the issue like at least for L3 which is SD playback. Something like here needs to be added I think....:
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/339185
Didn't dig deeper into the topic so far. Just want to share the info.
Renzke said:
It seems that Widevine / DRM is not part of the ROM at all as the App "DRM Info" doesn't show any Widevine information.
Click to expand...
Click to collapse
As I listed in post #1, DRM L3 works as I check/test/verify ALL my public xda builds for the functionality in post #1 before uploading.
Here's the results of checking DRM with 4 different programs. Devcheck by flar2 is what I use to check all my ROMS for a variety of values and widevine DRM L3 (along with clearkey) is clearly shown. Device Info HW and DRM Check also show widevine properly.
DRM Info by Android Fung is the only one that cannot show the widevine information which may be due to a bug in this program or it's poorly written and being denied by selinux enforcing.
DevCheck and Device Info HW are both ad free while DRM Check and DRM Info are infested with ads. The latter 2 are programs I will never use again.
In addition, DRM Info by Android Fung shows this in the logcat
Code:
GooglePlayServicesUtil: com.androidfung.drminfo requires the Google Play Store, but it is missing.
As I mentioned several times, I do NOT and will NOT install any gapps.
Your link to gerrit regarding DRM is already in my code (done a bit differently, but works as clearly shown by Devcheck).
https://github.com/retiredtab/propr...mmit/92ecf0f7615a291281e4b39da6be956e92e66d82
https://github.com/retiredtab/andro...mmit/5a91ac3d5d14510b335f8d6ec650b254edcdb2dc
@retiredtab Thanks for the detailed reply. You are right. I See Widevine L3 in other Apps as well. Shame on me '-'. Even Netflix itself gives this Info... Anyway... Playback is not starting while preview videos are working. Tried already a couple of versions without success and checked the permissions. As I'm customized with Magisk the rootcause could be on my side for sure. Prime Video is working by the way. Would be nice to know if a clean install has the same behaviour.
Renzke said:
@retiredtab I See Widevine L3 in other Apps as well.
Click to expand...
Click to collapse
There's a reason why I always recommend clean installs. When you don't do it, it leads to unexplained problems. If Prime is working, that suggests DRM L3 is working.
If a clean install doesn't work with Netflix, then see FAQ 9 and send me the logs (zipped). There's no guarantee that it will show anything wrong or if I can fix it. I don't have/use Netflix or any other $treaming service.
Having said that, I do build other roms like the T810 (S2 2015 exynos model) and others have commented that they do not need Magisk hide, root, etc to get Netflix shown in the playstore because my T810, like this T813, is selinux enforcing. They report that the T810 shows up as "device is certified".
Again, since I don't use gapps, I cannot confirm if "device is certified" is true for T813, but if it is, then Netflix should show up without Magisk/hide, root, etc. If it does show up, it's a bonus. If the T813 shows up as "device not certified", I have no plans to fix this as I don't use gapps.
@retiredtab I'm not sure if I will do a clean install as the system is working quite well expect Netflix and at the end of the day it's not super important for me. In case I do a clean install I will provide a log and be thankfull for the offer to fix things
The chances to have an indication is maybe low in the logs as Netflix loops in the loading screen without an error at all. Anyway I don't want to waste your time with this topic currently as I cleary didn't follow your instructions by doing a dirty flash and so on. And again... Super nice to have this rom which gives my tablet a 2nd life. Thanks a lot.
Renzke said:
@retiredtab I'm not sure if I will do a clean install as the system is working quite well expect Netflix and at the end of the day it's not super important for me. In case I do a clean install I will provide a log and be thankfull for the offer to fix things
The chances to have an indication is maybe low in the logs as Netflix loops in the loading screen without an error at all. Anyway I don't want to waste your time with this topic currently as I cleary didn't follow your instructions by doing a dirty flash and so on. And again... Super nice to have this rom which gives my tablet a 2nd life. Thanks a lot.
Click to expand...
Click to collapse
I don't really care about using Netflix on this device, but figured I'd let you know that I'm having the same issues after a clean flash. Will try and grab a log later.
I have this strange problem
I have two tablets SM-T813 and SM-T819.
I installed Lineage os 18.1 on SM-T813 and SM-T819 (I modified the installer). On the T813 it booted without any problems. On the T819, on the other hand, it stands in bootloop. I went into recovery and there were no files in INTERNAL STORAGE, it was empty. To T819 I need to install some file or something so that it can start reading Memory and come out of bootloop?
K-BOX2022 said:
On the T819, on the other hand, it stands in bootloop.
Click to expand...
Click to collapse
As I mentioned in the FAQ, there's nothing I can do without the T819 physically in my hands. If the T813 worked on T819, then it's a bonus. If not, it was worth a try.

Categories

Resources