[ROM][UNOFFICIAL][8.1] LineageOS 15.1 for Amazon Fire HD8 7/6th gen (douglas/giza)

Search This thread
By:
Advanced…
F

Finnzz

Senior Member
Sep 26, 2017
183
110
@Rortiz2
I'm enjoying LineageOS 15.1 so far (Douglas). I see that deep sleep is a known issue. Is there a way to manually force a deep sleep? And do you think the deep sleep problem is something that could be fixed in the near term, or is it more a long term, to probably can't be fixed sort of issue?
 
S

ShapeShifter499

Senior Member
Sep 13, 2009
474
160
I'm using a Amazon Fire HD 8 2016 "Giza" model and it works great for the most part but I'm experiencing an issue with one of my two "Giza" tablets. It doesn't seem to want to properly shutdown and I don't know why, it'll just abruptly power off when the battery is low enough. Does anyone here have ideas what might be happening?
 
R

Rortiz2

Senior Member
Mar 1, 2018
2,417
1,796
Barcelona
Crim Soukyuu said:
For me it also happens with one access point - I randomly see the Wi-Fi icon going hollow - not connected to any AP. That is with me not moving... I think there were reports about that before?
Click to expand...
Click to collapse
Yes, there were similar reports here, but I thought they were already resolved (with the wi-fi HAL update). Since the patch I sent to anujdatar didn't work as expected, I guess I'll have to debug this issue as well. If any of you experience the same problem again, please try to get a kernel log and log.
 
R

Rortiz2

Senior Member
Mar 1, 2018
2,417
1,796
Barcelona
Finnzz said:
@Rortiz2
I'm enjoying LineageOS 15.1 so far (Douglas). I see that deep sleep is a known issue. Is there a way to manually force a deep sleep? And do you think the deep sleep problem is something that could be fixed in the near term, or is it more a long term, to probably can't be fixed sort of issue?
Click to expand...
Click to collapse
Unfortunately, I'm still not sure of what's causing deep sleep to not work at all (even though I tried to debug it a lot of times). So yeah, I can't give you an exact date (or estimated) of when I'll fix that issue.
 
  • Like
Reactions: Finnzz
R

Rortiz2

Senior Member
Mar 1, 2018
2,417
1,796
Barcelona
ShapeShifter499 said:
I'm using a Amazon Fire HD 8 2016 "Giza" model and it works great for the most part but I'm experiencing an issue with one of my two "Giza" tablets. It doesn't seem to want to properly shutdown and I don't know why, it'll just abruptly power off when the battery is low enough. Does anyone here have ideas what might be happening?
Click to expand...
Click to collapse
I have read that in one of your gizas you had to disconnect the battery to be able to unlock it. By any chance, the tablet that gives you problems is that one? If so, I guess you should check the battery connector.
 
R

Rortiz2

Senior Member
Mar 1, 2018
2,417
1,796
Barcelona
OS9er said:
Hello everyone, new forum user here. Recently installed this build of Lineage on my Douglas, and just grabbed the latest update. All the major features are working fine. Only problem I have is the SD-card inaccessibility bug (device sees the SD card is inserted, but can't read any of the files on it). I'd love to see a patch for that, if possible. Otherwise, it's working much better than FireOS ever did. :)
Click to expand...
Click to collapse
Could be because I disabled sdcardFS. What's the format of the SDCard?
 
R

Rortiz2

Senior Member
Mar 1, 2018
2,417
1,796
Barcelona
Finnzz said:
@Rortiz2 This may be an unpopular opinion, but I hate the default typing sounds on LineageOS. I'm not sure if it's kosher to replace them in the distribution image? If so here is a copy of the iOS typing sounds:
bit.ly

iOS 10 Keyboard Sounds.zip | by JT1510365 for Generic Device/Other

bit.ly bit.ly

They just need to be placed in /system/media/audio/ui
Click to expand...
Click to collapse
I would prefer to keep the LineageOS sources as stock as possible. You might hate the default sounds, but other people might like them. So yeah I think it's best to just leave them as is and let users change them afterwards if they don't like the defaults (like you did). As a side note, since these will be overwritten every time you update the ROM, I would recommend you to create a ZIP that replaces the sounds (so you can just flash it after every update) or set up some kind of addon.d script.​
 
  • Like
Reactions: Finnzz
S

ShapeShifter499

Senior Member
Sep 13, 2009
474
160
Rortiz2 said:
I have read that in one of your gizas you had to disconnect the battery to be able to unlock it. By any chance, the tablet that gives you problems is that one? If so, I guess you should check the battery connector.
Click to expand...
Click to collapse

Turns out it was a bad battery. I got a hold of a fresh new battery through a seller on Amazon and replaced the one in the problem tablet. The same tablet now properly shuts down on low power. It lasts longer too it seems. All is well there now.

I do see a different issue, when using the YouTube app sometimes it will get stuck on screen when it attempts to go to floating video mode, picture in picture. It will stop responding to touches and I find I have to use the part of the screen not taken up to navigate to settings and force close the app.
 
D

Drachna

Member
Sep 7, 2021
11
2
I'm downloading the latest version now. I have to say that I've become very impressed with this ROM over the last few months or so. It works like a charm (except with some select browsers), especially offline, where it's almost as snappy as my phone.

Just a note on video playback: 720p or less works although the device has issues with [email protected], 1080p or higher is extremely choppy.
 
K

kirik_party

New member
Jan 16, 2022
3
0
Hi, @Rortiz2, I'm having trouble in waking up screen of my Douglas, once it turns off. Have to press the power button 5-10 times to wake up the display. Then too, its mostly a hit and miss. Have to mostly poweroff the tab and turn it on to access it.

I had flashed latest (Jan 2) build on it. Earlier was using 12.1, which worked flawlessly.
 
R

Rortiz2

Senior Member
Mar 1, 2018
2,417
1,796
Barcelona
kirik_party said:
Hi, @Rortiz2, I'm having trouble in waking up screen of my Douglas, once it turns off. Have to press the power button 5-10 times to wake up the display. Then too, its mostly a hit and miss. Have to mostly poweroff the tab and turn it on to access it.

I had flashed latest (Jan 2) build on it. Earlier was using 12.1, which worked flawlessly.
Click to expand...
Click to collapse
Try to grab logs while you reproduce the issue (include kernel logs as well, so I can check the kpd status).
 
You must log in or register to reply here.

Similar threads

D
Rapid Temporary Root for HD 8 & HD 10
Replies
1K
Views
384K
L
likwidchz
K
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2017 (douglas)
Replies
752
Views
207K
D
DutyThree
X
Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root
Replies
1K
Views
313K
R
Rortiz2
K
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)
Replies
2K
Views
343K
L
likwidchz
R
[ROM][unlocked][douglas] Lineage-12.1 [5 SEP 2020]
Replies
599
Views
125K
koop1955
koop1955

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 17
    R
    Rortiz2
    Quick update; I'll probably release the latest version of 15.1 soon with some fixes and I'll continue working on 18.1 as I already started making the trees.​
    View
    1
    C
    CheapoTab
    Thank you @Rortiz2 for still taking the time to release OS for this old little tablet. It is actually all I need for airplane trips for work and, well, I'm a little too cheap to buy something else for using a few times a year.

    At this point, I'm good with TWRP and have your latest Lineage 15.1 installed. The only thing holding me back from not reinstalling FireOS is apparently SafetyNet - can't install Disney+ or Netflix for media. Any suggestions on getting around SN?

    And if you need a tester, I'll happily install 18.1 as soon as you release.
    View
    1
    R
    Rortiz2
    anujdatar said:
    Hey, not sure what happened, but I turned my Douglas on after a few days and it was stuck in a boot loop or something. It got stuck on the LineageOS boot animation for a while and then rebooted to TWRP automatically. This happened every time.

    1. I tried to clear cache, but it said
    Code: 
    Failed to mount '/cache' (No such device)
    2. Then i tried re-flash this rom zip, that I already had on the internal storage and it said "Failed to mount (No such device)" for `/cache`, `/system` and `/data`.

    Now I seem to have lost everything that was on the internal storage, and it cannot mount anything. It won't connect to my computer either. It says "No media storage found. Make sure device is unlocked and MTP is enabled." It seems like the data partition does not have any file system format. And am unable to create one either. It says
    Code: 
    failed to mount and unable to recreate `/data/media`

    I would try to flash the old Fire OS image, but can't seem to mount the internal storage on to my Linux pc. Any ideas?

    Edit: I also tried the repair file system, but it gives me the same "Failed to mount" error. And I found an old TWRP backup that i've been trying to copy onto the tablet using adb, but it keeps rebooting after like 20%. Maybe the internal storage is dead?

    Edit2: Okay, so I successfully copied the backup to the mounted SD card. But it during restore using twrp, it says This /data backup was made with ext4, so i need to change it back to ext4 to ensure it boots. But it won't let me change file system using twrp

    Code: 
    Formatting Data using mke2fs
Done.
Failed to mount '/data' (No such device)
Unable to recreate /data/media folder
Updating partition details...
Failed to mount '/system' (No such device)
Failed to mount '/cache' (No such device)
Failed to mount '/data' (No such device)
...done
    Click to expand...
    Click to collapse
    Run the following commands with ADB on TWRP and PM me the results.
    Code: 
    adb shell cat /sys/class/block/mmcblk0/device/cid
adb shell cat /sys/class/block/mmcblk0/device/csd
adb shell mount -t debugfs none /sys/kernel/debug
adb shell cat /sys/kernel/debug/mmc0/mmc0:0001/ext_csd
    View
  • 24
    R
    Rortiz2
    1607247455067-png.5435845

    LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
    ​
    Instructions:
    • Reboot to recovery mode
    • Wipe data, system (/system_root) and cache
    • Flash the ROM and the Gapps
    • Reboot and enjoy!
    Downloads:
    Reporting Bugs:
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    Known issues:
    • Deep sleep (Doze)
    • Hardware decoding (OMX)
    • Camera (both photos/videos) isn't working on giza
    • Can't connect to hidden SSIDs
    Notes:
    • SELinux is in Permissive mode
    • The ROM only supports both douglas (Fire HD8 2017) and giza (Fire HD8 2016)
    How do i...
    • Unlock and install TWRP?
      • Follow the instructions of the unlock thread (douglas | giza)
    • Go back to the original/stock ROM?
      • Download the stock update.bin (douglas | giza) and flash it using TWRP
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code: 
    What is your--
LineageOS version:
LineageOS Download url:
Gapps version:

Did you--
wipe:
restore with titanium backup:
reboot after having the issue:

Are you using--
a task killer:
a non-stock kernel:
other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    Contributors
    R0rt1z2, FreakyyLike (for the douglas donation)
    Source Code: https://github.com/mt8163-dev
    Kernel source: https://github.com/mt8695/android_kernel_amazon_mt8695
    View
    17
    R
    Rortiz2
    Quick update; I'll probably release the latest version of 15.1 soon with some fixes and I'll continue working on 18.1 as I already started making the trees.​
    View
    13
    R
    Rortiz2
    New build is up.

    2021-10-31 [douglas] [giza]
    • Resolved missing {drm,omx} symbols ({TimedEventQueue,EVP}).
    • Added MicroG support (Signature Spoofing).
    • Added exFAT support (included new kernel driver).
    • Fixed audio stream (amazon proprietary libraries).
    • Added GPU Extension Device ("GED") support.
    • Updated the security patch to October 2021.
    PS: Happy Halloween!
    View
    11
    R
    Rortiz2
    Good news to everyone. I partially fixed HW decoding (and this includes Video Recording) ;)

    EDIT: It fully works now
    View
    10
    R
    Rortiz2
    New build is up.

    2021-09-16 [douglas] [giza]

    • Fixed camera.
    • Fixed internal storage (OBB) issues.
    NOTE: Video recording isn't working at all, it crashes with the stock camera app but it works with some third-party apps (such as Telegram).
    NOTE: Let me know if obb issues are fully gone (I basically reverted the sdcardfs squash update). Try to clean flash the ROM as well before reporting if the bug it's still present.
    View

New posts