Database Develop

[ROM-AOSP] Unofficial CM10.1 (JB 4.2.2) [08/12 ICON DRAG FIX]

Unofficial CyanogenMod 10.1 for the Kindle Fire HD 8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
AUDIO: DO NOT ENABLE "LOCK SCREEN AUDIO" OR "TOUCH SOUNDS" IN SOUNDS MENU. THIS *CAN* BREAK AUDIO.
CyanogenMod Changelog (DO NOT DOWNLOAD ANY .ZIP FILES -- FOR OFFICIAL DEVICES ONLY)
http://changelog.bbqdroid.org/
Download Information:
[LATEST][08/12] BETA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
Mirror 2: d-h.st/xMG
md5sum: 6a717e9b085909e6407cab486f585b54
[07/26] BETA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130726-UNOFFICIAL-jem.zip
Mirror 2: d-h.st/4Uc
md5sum: 41d6331a9492ddc2dd576c6cad71c8f5
[07/17] ALPHA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130717-UNOFFICIAL-jem.zip
Mirror 2: http://d-h.st/XxG
md5sum: 1a1204e8e74211213fd1414ebca80194
[07/13] ALPHA CM10.1 + 3.0.50+ KERNEL
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130713-UNOFFICIAL-jem.zip
md5sum: 5050e8c31851162a117d87d17a1b6806
Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jem/cm10.1/
Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
CHANGES:
[08/12] Includes a Trebuchet patch to fix the screen flip-flop when trying to drag an icon in landscape (by XDA user Wickets^)
[08/12] Headphone volume raised (set to 114)
[07/26] Fixed occasional drawables issue with background / etc reverting to HDPI graphics
[07/26] More Dalvik VM changes
[07/17] Dolby: [WIP] Initial work for Dolby support in CM10.1 -- Still troubleshooting audio effect pre-gain handling
[07/17] Audio: Fixed MIC initialization -- works perfectly now, everytime.
[07/17] Camera: cleaned up DCC file handling for a bit more "Amazon"-like performance.
[07/13] USB Vendor ID / Product ID's have been reset to match the Amazon OS / TWRP values. Should help keep Windows drivers from going bonkers.
[07/13] Some Audio issues have been resolved. It shouldn't stop when swapping apps, etc. Still low volume currently where Dolby decoder is used.
[07/13] CM refreshed which includes several well-known security exploit patches
[07/13] PVR/SGX driver updated to 1.[email protected] fixing several games and Google Earth
[07/13] Enabled "dirty region" rendering which helps 2d rendering quite a bit.
[07/13] Fixed a Bluetooth issue: stuck in TRANSITION mode till it's enabled/disabled after a reboot. This was causing extra battery drain.
[07/13] Some tweaks to Android vm allocations. Still needs work, but less apps are being killed off on the boot.
[06/04] CM refresh for changes (no device updates)
[05/14] New android OS audio driver. MIC works but may need to be stopped / re-started once (WIP)
[05/11] Camera should be working again
[05/08] Fixed orientation for HDMI output (requires a /data wipe) -- sound is W.I.P.
[05/08] Fixed default landscape orientation (was backwards)
[05/08] Fixed power HAL to retain current max CPU freq (original code by twa_priv, patched by Hashcode)
[05/07] Raised headphone volume by 10%
[04/20] [Thanks to Javabugs] Bluetooth firmware is now renamed correctly so that it loads and should work
[04/05] Basic audio function is now working. This means volume adjustable speaker output and headset output. NO input works yet -- still WIP.
[04/01] Basic camera function now working, tho after video recording is stopped, camera will FC during thumbnail creation. Video is recorded successfully tho. Panorama crashed out entirely still WIP.
[02/25] Updates to CM10.1 (4.2.2_r1)
[02/01] First release
FEATURES:
3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
Audio
Camera
Wifi
Bluetooth
Sensors
HWAcceleration
HD Codecs for YouTubeHD and Netflix
HDMI video out is now correct and work across several resolutions. YMMV
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code:
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem

CURRENT KNOWN ISSUES:
When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
AUDIO: Headset volume still may be lowish. Testing better ways of increasing volume w/o distortion. It's a WIP.
3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
I don't have an LTE version so this is not enabled in current builds.
CURRENT KNOWN APP/GAME ISSUES:
Need For Speed Most Wanted: Crash
EZPDFReader: PDF close = Crash

Hey,
HashCode this is very great job!
Thx

Awesome work, Hash and Verygreen (and whomever else is involved). Much appreciated

slacka-vt said:
Awesome work, Hash and Verygreen (and whomever else is involved). Much appreciated
There's CM10 Development for the KFHD 7" here:
From past experiences, the Dev's do not like having requests for a different device in their threads (or any requests for that matter ). Just sayin' . . .
Click to expand...
Click to collapse
Yes i know, and i allready know that HashCode have not time to do something for the 7" and i have updated my post so you can also do it

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
Hashcode said:
Unofficial CyanogenMod 10.1 for the Kindle Fire HD 8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
Download Information:
[02/01] ALPHA CM10.1 + 3.0.50+ KERNEL
Download the ROM
md5sum: 36a6ec8df79b6dedbe56692ee2f07391
Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)
Older builds are found here (under my "Jem" folder on goo.im):
http://goo.im/devs/Hashcode/jem/cm10.1/
PLEASE BE SURE TO WIPE DATA/CACHE WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
CHANGES:
[02/01] First release
CURRENT KNOWN ISSUES:
AUDIO DOES NOT WORK. I'm still troubleshooting and working on a custom audio HAL (if needed)
I need to tweak the build.prop settings so that more apps are compatible.
Camera crashes at the moment
Bluetooth function turns on, but is largely untested.
Haven't touched HDMI yet
I don't have an LTE version so this is untested. Tho much of the RIL files are in place as well as APNs.
FEATURES:
[02/01] 3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
[02/01] PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
[02/01] Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
[02/01] Wifi
[02/01] Bluetooth pairing (no audio)
[02/01] Sensors
[02/01] HWAcceleration
[02/01] HD Codecs for YouTubeHD and Netflix
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code:
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem
Click to expand...
Click to collapse
How we can port this rom to the kindle fire hd 7". I love your work, you are a great developer
Sent From My Super Modded KFHD

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
Thanks for the hard work, downloading now!

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
ChrisFa5 said:
Thanks for the hard work, downloading now!
Click to expand...
Click to collapse
Great, let me now how both the bootloader (from the other thread) and ROM installation goes.
Sent from my DROID RAZR HD using Tapatalk 2

Thank you!
Now to get a fastboot cable.
If anyone installed it please give us your impressions.

kls2k said:
Thank you!
Now to get a fastboot cable.
If anyone installed it please give us your impressions.
Click to expand...
Click to collapse
You can definitely do the install w/o a fastboot cable, but you do need to have a working fastboot driver on your machine. The KFHD's stock bootloader will check for fastboot commands for a short period of time during the boot.
There are other methods as well to get the partitions setup for this, however, in the case of disaster having a working fastboot setup will be required to restore.

Hashcode said:
You can definitely do the install w/o a fastboot cable, but you do need to have a working fastboot driver on your machine. The KFHD's stock bootloader will check for fastboot commands for a short period of time during the boot.
There are other methods as well to get the partitions setup for this, however, in the case of disaster having a working fastboot setup will be required to restore.
Click to expand...
Click to collapse
Hashcode,
Does a factory/fastboot cable work on the 8.9? Some say to buy it, and others say that it only works for the Kindle fire 2 and 7" and that there is no need for it. If it is needed, is there a specific cable that you recommend? Thanks

vaggolena said:
Hashcode,
Does a factory/fastboot cable work on the 8.9? Some say to buy it, and others say that it only works for the Kindle fire 2 and 7" and that there is no need for it. If it is needed, is there a specific cable that you recommend? Thanks
Click to expand...
Click to collapse
I do all my work without a fastboot cable but I have my fastboot driver configured correctly so that the KFHD8 is recognized as a fastboot device during the bootup.
So, while I have tested fastboot on almost every other device that I own, I've never needed to use it on the KFHD8.
EDIT: I just did a quick functional test and my Motorola OEM factory cable did *NOT* place me in fastboot mode. So I think getting a fastboot cable may be a waste of time for the HD 8.9. Rather that users download the Android SDK and make sure it's setup correctly for fastboot. Updating my OP's.

Hashcode said:
I do all my work without a fastboot cable but I have my fastboot driver configured correctly so that the KFHD8 is recognized as a fastboot device during the bootup.
So, while I have tested fastboot on almost every other device that I own, I've never needed to use it on the KFHD8.
EDIT: I just did a quick functional test and my Motorola OEM factory cable did *NOT* place me in fastboot mode. So I think getting a fastboot cable may be a waste of time for the HD 8.9. Rather that users download the Android SDK and make sure it's setup correctly for fastboot. Updating my OP's.
Click to expand...
Click to collapse
Thank you!!

Hashcode, I'm getting a black screen after installing the rom + gapps. Any help?

same here... wiped, factory reset, then installed cm10.1, then wiped and factory reset, then gapps. After blue Kindle screen just a black screen, nothing happens. installed again, cm10.1, then gapps, no wipe/reset. black screen. Got an Fire 8.9 32GB.

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
are both of you using 32gb devices?
has anyone had a successfully installed this?
Sent from my DROID RAZR HD using Tapatalk 2

Just tried your build on my 16GB wifi model but got a black screen on boot (right after the blue KF logo). Happens no matter gapps installed and wiped or not.
I have a recently synced copy of your git repo and I could build myself and run the rom properly though.

Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
siruba said:
Just tried your build on my 16GB wifi model but got a black screen on boot (right after the blue KF logo). Happens no matter gapps installed and wiped or not.
I have a recently synced copy of your git repo and I could build myself and run the rom properly though.
Click to expand...
Click to collapse
Can you get a copy of /proc/last_kmsg from the black screen boot and send it to my email? Dont pastebin as there is serial #, etc information that shouldnt be shared. hashcode0f at gmail.com
I will also wipe and flash this build again. could have been a bad build somehow.
Sent from my DROID RAZR HD using Tapatalk 2

I am afraid I couldn't. After the black screen I had to hold the power button to forcefully turn the tablet off and on again - it seemed that the kmsg didn't persist through that to recovery.

Hashcode
first of all, Thank you very much for developing this roms. I bought KD HD 8.9 16Gb when you were developing cm10.1 :laugh:
I read your post (bootloader and this rom) and follow steps. and succeed to enter twrp recovery. (+ blue amazon logo)
but after i installed this rom and gapps, logo appeared and black screen ...
I can enter twrp recover (by power + volume button) but i can't connect kindle 8.9 to pc (windows7 can't recognize KD driver )
so I can't move the file or enter the fastboot .. ( I ordered a factory cable.)
If you know to connect kindle to pc at black screen or at the twrp recovery mode ( I tried to mount use mode of twrp recovery but it was no useful)
tell me something please.

[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...

Cyanogenmod 13??????

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.

[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!

Postmarketos for Amazon Fire 7 HD (2017) (Austin)

Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin
Amazon Fire 7 (2017) postmarketOS Armv7l Mediatek MT8127 Mali-450MP4 600x1024 display 1GB RAM Linux 3.10.54
What seems to work:
Boot Touch screen Battery percentage Usb internet OTG usb Wayland, Mate, Xfce4, Lxde, Sxmo, i3wm
Does NOT work:
Wifi & Bluetooth (no drivers) GPU acceleration (drivers do not work) Audio Sleep and fully turning off the display Screen rotation Wifi adapter does not work even with drivers and kernel support, mobo support issue(?) FDE Cameras You tell me
Special options: *Must be flashed to USERDATA partition as system partition is too small
msm-fb-refresher packaged is added to the depends to make the screen refresh. After flashing the device must be booted into recovery once. From the recovery it is to be powered off and booted and then as normal. This is because the device depends on the AMONET exploit which is applied by twrp after every flash.
Flashing Instructions
This assumes that you already have linux installed and the bootloader on the tablet is unlocked. Don't worry if it looks complicated. If you are unsure of something ask on the postmarketos matrix or leave a comment for help.
Install pmbootstrap as stated in the postmarketos wiki, does not matter which options or device you pick.
Once that is done download and drag the two folders in the git repo into "/home/YOURUSER/.local/var/pmbootstrap/cache_git/pmaports/device/testing/" also displayed as "~/.local/var/pmbootstrap/cache_git/pmaports/device/testing".
Run pmbootstrap init and select amazon as manufacture and austin as the device, mate, lxde, xfde, are confirmed working.
Run pmbootstrap install
Boot into twrp and wipe all partitions including data
Boot into the hacked bootloader from the twrp options
Run pmbootstrap pmbootstrap flasher flash_rootfs --partition userdata (system partion is too small to flash!) and once it is done flashing run pmbootstrap flasher flash_kernel
Unplug the device, wait 10 seconds and then hold the power button. Once it is powered on YOU MUST boot it into twrp at least once as it needs to restore the AMONET exploit, until you do that the device will not boot.
Issues
If something does not work such as the display rotated wrong or device not booting just comment or open an issue, I changed the rotation of the display in the kernel options to horizontal but i did not test the effects as I already have android with books on it.
Reinstall android/lineage
Simple as cake, just boot into twrp wipe all partions(some will fail), you may need to resize and fix until it starts working. You just need the system and data partitions to be reformated to ext4 even if they already are. Then just flash the lineageos zip file and reboot the device normally(amonet is fine)

GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin
Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin - GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon ...
github.com

This looks promising, nice job. I will try installing it on my Austin during the next days.

Rortiz2 said:
This looks promising, nice job. I will try installing it on my Austin during the next days.
Click to expand...
Click to collapse
Good luck. Tell me if the display works if you do install it. Thanks

hexdump0815 cleaned up the config file, use his fork if you are going to install.​

Is it wifi working? It'll awesome

Baonks81 said:
Is it wifi working? It'll awesome
Click to expand...
Click to collapse
Unfortunately the drivers for this SOC are nonexistent so nothing works. WIfi and hdmi adapters don't work, but OTG does. Hexdump made a Debian and Ubuntu image for this tablet, it is great but the tablet is mostly useless without WiFi and GPU support. You can also flash the main image to the userdata partition instead of using an SD Card, but if I remember correctly the rootfs won't auto extend. It would have been great to use this as a linux tablet, however this SOC is uncommon and is not supported by any Linux maintainer. https://github.com/hexdump0815/imagebuilder/releases/tag/211101-02

Fandroid Tech said:
Unfortunately the drivers for this SOC are nonexistent so nothing works. WIfi and hdmi adapters don't work, but OTG does. Hexdump made a Debian and Ubuntu image for this tablet, it is great but the tablet is mostly useless without WiFi and GPU support. You can also flash the main image to the userdata partition instead of using an SD Card, but if I remember correctly the rootfs won't auto extend. It would have been great to use this as a linux tablet, however this SOC is uncommon and is not supported by any Linux maintainer. https://github.com/hexdump0815/imagebuilder/releases/tag/211101-02
Click to expand...
Click to collapse
Thanks for new information. I'll searching around
I think we can find firmware it out on /dev/mmcblk---

Baonks81 said:
Thanks for new information. I'll searching around
I think we can find firmware it out on /dev/mmcblk---
Click to expand...
Click to collapse
I looked at the firmware dump on github, it is all proprietary and seems to be compatible only on android. The closest I got to getting working wifi was moving the original libs and networkmanager bin to linux however it only showed wifi working for a few seconds without detecting anything.

I'm working on this device right now. I just downloaded the repository below, and I will make a pull/merge request upstream soon.
Fandroid Tech said:
GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin
Working ebuild for installing postmarketos on the Amazon Fire 7 HD (2017) codename Austin - GitHub - GjergjiFloychi/amazon-austin-pmaports: Working ebuild for installing postmarketos on the Amazon ...
github.com
Click to expand...
Click to collapse
I have my own fork of the pmaports repository at https://gitlab.com/Worldblender/pmaports, where I will push your files (eventually with my changes) to. Maybe we can work together on getting this tablet supported upstream, if you still want to (anything else that isn't working, like the Wi-Fi/Bluetooth, will have to come later).
UPDATE: Well, I'm going to use https://github.com/hexdump0815/pmaports-amazon for the config now, didn't notice it the first time around. I also noticethat it's possible to get Wi-Fi working with https://github.com/hexdump0815/imagebuilder-firmware/blob/main/tablet_amazon_austin-firmware.tar.gz, that I will try out with my builds soon.
From https://github.com/hexdump0815/imagebuilder/tree/main/systems/tablet_amazon_austin:
wifi seems to work by using the android firmware and tools in a minimal android bionic chroot env
wifi can be stated via /scripts/start-wifi.sh
uncomment the start of this script in /etc/rc.local in case wifi should be enabled by default
wifi support was added in february 2022, so all images from before do not have it yet but it can be added easily afterwards
Click to expand...
Click to collapse

Worldblender said:
I'm working on this device right now. I just downloaded the repository below, and I will make a pull/merge request upstream soon.
I have my own fork of the pmaports repository at https://gitlab.com/Worldblender/pmaports, where I will push your files (eventually with my changes) to. Maybe we can work together on getting this tablet supported upstream, if you still want to (anything else that isn't working, like the Wi-Fi/Bluetooth, will have to come later).
UPDATE: Well, I'm going to use https://github.com/hexdump0815/pmaports-amazon for the config now, didn't notice it the first time around. I also noticethat it's possible to get Wi-Fi working with https://github.com/hexdump0815/imagebuilder-firmware/blob/main/tablet_amazon_austin-firmware.tar.gz, that I will try out with my builds soon.
From https://github.com/hexdump0815/imagebuilder/tree/main/systems/tablet_amazon_austin:
Click to expand...
Click to collapse
You could package the wifi hack into an Alpine Linux for firmware package if you want. Debian 11 runs really well, to bad we can't get everything working.

Fandroid Tech said:
You could package the wifi hack into an Alpine Linux for firmware package if you want. Debian 11 runs really well, to bad we can't get everything working.
Click to expand...
Click to collapse
Will work on that soon. I just got a build to boot today, and basic functionality seems to be working. I'm going to try a different distro for accessing more functionality (likely Ubuntu 20.04 or 22.04) I just opened up a merge request at https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3251 for the progress on upstreaming.

I'm thinking about using the exact same kernel that the LineageOS image uses:
https://github.com/cm14-mt8127/device_amazon_mt8127-common
https://github.com/cm14-mt8127/kernel_amazon_mt8127-common
This kernel has been updated to 3.10.108, and it's the last one for the 3.10 branch. I'm going to try creating a new build using this kernel, and see how it goes.

Worldblender said:
I'm thinking about using the exact same kernel that the LineageOS image uses:
https://github.com/cm14-mt8127/device_amazon_mt8127-common
https://github.com/cm14-mt8127/kernel_amazon_mt8127-common
This kernel has been updated to 3.10.108, and it's the last one for the 3.10 branch. I'm going to try creating a new build using this kernel, and see how it goes.
UPDATE: Three patches would not apply successfully for this kernel:
fix-host-card-inserted.patch
silence-power-logspam.patch
silence-thermal-logspam.patch
After building without these patches, the kernel boots, but it stays stuck without being able to process further, with some kernel messages displayed. I wonder what I should do to get this kernel working, or if this one shouldn't be used.
Click to expand...
Click to collapse
Use any kernel you want. It literally does not matter as it cannot be mainliner in the future anyways. It makes no difference what you use.

Fandroid Tech said:
Use any kernel you want. It literally does not matter as it cannot be mainliner in the future anyways. It makes no difference what you use.
Click to expand...
Click to collapse
Here's my results after building and boot it:
There are some kernel messages that pop up, and the splash screen never appears. It doesn't matter whether there is a microSD card inserted or not; there seems to be too many changes made to it from 3.10.54 to 3.10.108, along with additional changes that are designed more for Android/LineageOS usage. Finding every one of them is too much work for me.
Three patches would not apply successfully for this kernel:
fix-host-card-inserted.patch (will apply successfully once the entry for line 271 is removed)
silence-power-logspam.patch
silence-thermal-logspam.patch
Again, after building without these patches, the kernel boots, but it stays stuck without being able to proceed further, with some kernel messages displayed. I tried building without any of the patches shipped, but the end result is still the same. I need some help as to what what I should do to get this kernel working, or else I will go back to the 3.10.54 kernel that I know is actually booting to the splash screen. Here, I don't care whether I use a mainline kernel here, since I know the SOC is not supported by mainline. I simply care that I can get a newer kernel version working (from 3.10.54 to 3.10.108), unless there's too many changes for me to go through.

Worldblender said:
Here's my results after building and boot it:
There are some kernel messages that pop up, and the splash screen never appears. It doesn't matter whether there is a microSD card inserted or not; there seems to be too many changes made to it from 3.10.54 to 3.10.108, along with additional changes that are designed more for Android/LineageOS usage. Finding every one of them is too much work for me.
Three patches would not apply successfully for this kernel:
fix-host-card-inserted.patch (will apply successfully once the entry for line 271 is removed)
silence-power-logspam.patch
silence-thermal-logspam.patch
Again, after building without these patches, the kernel boots, but it stays stuck without being able to proceed further, with some kernel messages displayed. I tried building without any of the patches shipped, but the end result is still the same. I need some help as to what what I should do to get this kernel working, or else I will go back to the 3.10.54 kernel that I know is actually booting to the splash screen. Here, I don't care whether I use a mainline kernel here, since I know the SOC is not supported by mainline. I simply care that I can get a newer kernel version working (from 3.10.54 to 3.10.108), unless there's too many changes for me to go through.
Click to expand...
Click to collapse
Just use the stock 3.10.54 kernel. Both versions have long since been EOL. It does not matter what is used as functionality will still the same, both now and any future development. I would not bother upgrading the kernel to 3.10.108. Hexdump told me a while back that somebody else maintaining a similar soc on the mainline branch told him that mainlining the device is almost impossible due to some proprietary components by Amazon. I am not entirely sure as to the validity of this claim but I think that it is not worth the effort of upgrading the kernel of this device. Check this page for more info, I found it to be very helpful to my port. https://wiki.postmarketos.org/wiki/Amazon_Fire_7_2015_(amazon-ford)

[waits eagerly nonetheless]
This is a solid old device in a lot of ways. I'd love to see it supported by PMOS.