yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sergtot:
Wow! Thank you! Will write here :) Can you plus make a new build with OMS support?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] artha9:
what camera works ?, and I deleted it .. apk?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Try Open Camera.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] bobcat131:
KFHDX

Anything going on for Android 8 rom/twrp for the HDX?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
I hope not lineage 15 isn't stable enough as daily driver at the moment. I think in 2018 or Christmas it would be a nice present :cowboy:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stangri:
I can totally relate to staying on an older codebase for the sake of Xposed! Having said that, the pre-November 9th builds work, so I personally see no reason to investigate the issue of the older (13) CM. Especially if there's a way to turn off nightly builds generation and just have November 8th build as the last one available for CM13.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Quick summary of CM 13.0 issues (Thor):

- unresolved CM regression for SIMless devices (details)

- unreliable Bluetooth (headsets, keyboards)

- occasional WiFi disconnects related to dual band APs

- camera support (minor)

- spontaneous reboot if phone dialer inadvertently accessed

Immediately depreciating CM 13.0 (eventually 12.1) seems reasonable given limited support resources. Would rather see efforts coalesce around CM 14.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Thank you for the great summary. Can you point me to 1 of the apps which trigger the endless SIM requests? I'd like to fix that issue as well as screencast support (sharing the screen of the device on Chromecast -- normal Chromecast use is working already).

On my Thor device BT, Wifi and camera support issues have been resolved, tho future public testing may reveal tweaks are needed.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
THOR NEW BUILD UPDATE: 2016-12-16

Download Section

CHANGE LOG:

[BLUETOOTH] Updated bluetooth vendor library to latest CAF branch for Marshmallow (previously KitKat) -- seems to fix many pairing issues, though this needs testing.

[SCREENCAST] Updated audio policy to support Screencast (from Settings -> Display -> Cast). NOTE: A warning box is displayed on Thor saying size is not optimized. Still debugging that.

[SELinux] Turned on Enforcing mode again

(All local changes have been pushed back into CM codebase)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Hmm.. After some more playtesting, it looks like bluetooth might need some more debugging.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] MahmudS:
For me, the biggest issue in CM13 for Thor and Apollo is SIM-cart support, mobile Internet 3G/4G and GPS
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
OK if ggow will post the latest version for Apollo I can help you with some tests for Apollo.

Cm14. 1 for me is more stable

Have a working Camera and WiFi.

I don't need xposed with the newest version

Let me know if you need the tests.

BTW I have some feature request. Are u able to enable double touch to wake? -> you will find the kernel commits by sony or lg https://github.com/DooMLoRD/android_kernel_sony_apq8064/commits/master_kk-4.4.2 thats compatible kitkat

https://github.com/flar2/ElementalX-N5

I saw all Qualcomm devices are able to.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'll post a new version for apollo this evening after some testing.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Requires kernel support; will be curious how deep [MENTION=4243514]Hashcode[/MENTION] and [MENTION=5749760]ggow[/MENTION] are going with the latest efforts to keep this JellyBean/KitKat era device relevant into 2017 and beyond. Who would have thunk Android 6/7 would ever come to HDX. Thanks guys for all your efforts. :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
you are right dude, massive upgrade for this device. i hope this two guys get enough time to develop.

the device is fast and snappy i love the new feeling... android 7 is so fluent.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
The primary culprit was a proprietary messaging/calling app (here) for Verizon Wireless customers which is one of the major cell/mobile carriers in the U.S. However, I believe the same behaviors occurred when Hangouts is designated as primary for SMS (info). Many also require Google Voice integration which gets ugly for testing unless that is your default config.

Great to hear BT, WiFi, camera and other annoyances have been addressed in test builds of CM 13! I stepped away a couple months ago so didn't see those.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] preisl:
Hi,

to follow up on that topic. I have now installed CM-14.1, copied the attached gapps config file to /sdcard/Open-GApps/.gapps-config and installed the stock version of gapps - it worked flawlessly, there are about 220MB of free disk space after installation. After installation there's a log file in the very same folder (/sdcard/Open-Gapps/open_gapps_log.txt) showing exactly what has been installed and what has been skipped.

Btw. installing / upgrading open-gapps is easy with the Open GApps app ( https://play.google.com/store/apps/details?id=org.opengapps.app ).

Cheers,

Martin
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up for Apollo

- Dated 16 December 2016

- See OP for changes
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
I should clarify that I meant CM 14.1 had the bulk of the work done to fix up wifi, BT and camera. I didn't have the time to work out some of the kinks in CM 13.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Yes it is! Especially if twrp is the installed recovery and root permissions are granted to the Open GAaps app for auto install. Even on finicky devices with a different/locked/stock recovery the app offers speedy identification and download of the latest GAaps builds which can the be flashed with another tool like FlashFire. Thanks for sharing!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
Looks like we can go official

If you need latest working cm13 for Apollo I can share my upload for all at cm13
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Someone else beat you to it. Apollo and Thor. :)

http://xdaforums.com/kindle-fire-hd...3-kindle-hdx-2015-11-29-t3259732/post70039742
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stangri:
Brilliant, paired with my JBL Clip+ like the cm13 did and seems to be working better than cm13 so far (experienced occasional hiccups with BT audio during video playback on cm13 with plex client).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] floschl:
I am having problems installing cm-14.1-20161216-UNOFFICIAL-apollo.zip using TWRP 3.0.2.0:

Patching system image unconditionally...

E:unknown command [log]

E:unknown command [log]

Did a full wipe + restart to recovery before.

Anything I did miss? Is there also a new TWRP for apollo (its the 16GB version)?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Ignore the error and proceed as you normally would. Everything should be fine.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Definitely not stable enough, most of the stuff to support our hardware platform is not in place.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] captaindaxter:
I wanted to say thanks,I was able to downgrade root unlock the bootloader flash linageos and flashmy own custom nethunter build! I think I'll write a guide for all of it because it was quite a process. Nap time for me though I've been at it for hours. I'd love to talk with the rombuilder o have some questions about building the kernel. Till tomorrow!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] captaindaxter:
Pictures
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
Latest version is working fine even with arise and magisk

Thanks for keeping the Rom updated
[Kindle Fire HDX 7" & 8.9" Original Android Develop] RolandStoner:
Hello! I was wondering about the kernel source. I'm new to this whole dev process but I'm a pretty quick learner. I'm trying to create a bzImage file for the kernel but keep running errors after I "make" bzImage. Im using the tool chain requested and run makemenu to the nethunter specs. Here is the output after make Arch=arm menuconfig bzImage is ran
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rockyrhino:
Wi-Fi Vuln

LineageOS (cm14.1) was patched on the 16th against the KRACK vulnerabilities.

review.lineageos.org/#/q/topic:krack-n+(status:open+OR+status:merged

I'm not sure if the cm13 branch has been patched or not.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] trantuan1:
camera very dark, how fix?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Typical for this device regardless of custom ROM. Only fix is to return to stock (FireOS) or a KitKat based ROM such as Nexus or CM11.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] trantuan1:
thank you very much
[Kindle Fire HDX 7" & 8.9" Original Android Develop] gatoh:
In CM13 works fine for me, so I think that could be fixed in the future. Try CM13 and test it!

Enviado desde mi Nexus 5X mediante Tapatalk
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jlbrown1:
[MENTION=5749760]ggow[/MENTION],

Any reason you cannot make this an "Official" version?

Thanks!

Jason
[Kindle Fire HDX 7" & 8.9" Original Android Develop] CocoBun:
He's not the one who maintains and determines if it can be, that's Hashcode. Maybe he could contact him about it
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jlbrown1:
[MENTION=4243514]Hashcode[/MENTION],

Any reason your version and [MENTION=5749760]ggow[/MENTION] version cannot be "Official"?

Jason
[Kindle Fire HDX 7" & 8.9" Original Android Develop] matt_heynes:
Hi there,

new Kindle Fire HDX owner here. I hope this doesn't sound too pushy, but I was wondering if we could get an update on the KRACK patches. I was thinking about flashing LOS 14.1 on my device soon, but I would like to wait until an image with these fixes becomes available (in order not to have to reflash in the near future).

Thanks a lot in advance.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
TTBOMK the next upstream (Lineage 14.1) release will have KRACK patches. Supposedly happened Oct 16th (here).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] robnhl:
I've hit some trouble. I have a Thor device, unlocked bootloader, was running a July build of this ROM.

I decided to wipe and flash the newest (14-OCT-2017) version of the ROM and the two microG files from this thread.

Flash seemed to go OK but I don't get past the Lineage boot animation.

Wiped and tried flashing the old July build. Same problem. Stuck on the boot animation.

Any ideas on what I've done wrong or how to resolve?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
May sound like a strange recommendation but has proven effective in the past:

- wipe and flash this basic KitKat based ROM

- if device boots normally return to TWRP, wipe key partitions (system, data, cache, dalvik) and reflash Lineage with a suitable (mini or smaller) Open GApps package

If all goes well you can retry MicroG and/or Magisk. Don't forget to take a nandroid (full backup) in TWRP first for quick recovery should something go wrong. Also make sure your TWRP installation is up to date.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] robnhl:
Thanks. Was just heading back here to report that doing a system wipe resolved the issue. I should have thought of that straight away. Thanks for the response, though.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] waleedmalik:
TWRP fast boot waiting for device after unlocking bootloader from nexus hdx

My device is HDX7 Thor i have flashed aboot and vuln cubed twrp, then unlock.bat file, the usual.

I have unlocked bootloader on hdx nexus rom after rooting using kingroot.

I need to install lineage OS but I first need twrp recovery

after executing fastboot flash recovery twrp.img command it is showing waiting for device

what should i do now please help

I have changed usb ports

i have disabled driver signature in window 10 recovery

please help all drivers are installed

on device it says [fastboot] Ready.

is my device useless now please help.

I have already outdone my self and I am about to panic. :eek::confused::(:crying:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Hi Guys,

I put a few patches up on review which should fix the camera for most users (tested on Thor currently): https://review.lineageos.org/#/q/st...on_hdx-common+branch:cm-14.1+topic:camera-fix

I had miss-applied some camera CVEs back in 2016 which started causing camera issues (super dark, etc). This patchset reverts a few and re-applies them correctly.

I'm waiting till someone w/ Apollo device can test as well before merging to our kernel.

Re: why this isn't an official LineageOS device.. that's a good question. I guess I need to probably setup the wiki pages and make it official.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] 苏苏伍滋:
Thank God for the maintenance of the hdx7 ROM Hope you can make oreo God
[Kindle Fire HDX 7" & 8.9" Original Android Develop] waleedmalik:
THanKS all!

I did it on my own and I learned alot I am very happy.......:laugh::D:good::good::good::cool:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Went ahead and merged the camera changes into the LineageOS cm-14.1 kernel branch:

https://github.com/LineageOS/android_kernel_amazon_hdx-common/commits/cm-14.1

So hopefully the next build will include that.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] arshileus:
Hi guys,

I am new one here. I have got fire hdx 8.9 3rd edition and want to install android 7.

Can you give me full guideline how to do this.

P.S Will Camera work with this ROM?

P.S.S How i know tablet has 2500x1600 screen resolution, but i see that it doesn't use. Why this happens?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
All 3rd gen HDX devices use full screen resolution whether that be 1920x1200 (7" Thor) or 2500x1600 (8.9" Apollo).

Rooting FireOS and unlocking the bootloader are prerequisites to installing a custom ROM (there are a few exceptions). Look for recent threads with title keywords 'unlocking bootloader...' for an overview. You will likely face several frustrating challenges; be prepared for a lengthy process and a few setbacks. Reading up in advance will give you a leg up.

I have a 'to do' to clean up and consolidate several threads on this topic. For now you'll need to wade through the muck. Ask questions as they arise.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
Hash your alive

Good to see you back...

If I got an account I will do the wiki etc.

Hope to see hdx official again.

Br
[Kindle Fire HDX 7" & 8.9" Original Android Develop] 苏苏伍滋:
I met the problem that I couldn't install the application. What's the solution?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] CocoBun:
What are you asking? I would say buy an iPhone, but they suck. If pc is master race for gaming then for mobile it's Android phones (preferably Samsung or Huawei)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] 苏苏伍滋:
Sorry, I'm a Chinese. I don't know how to translate English, but it seems that there is something wrong with it
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Albert Poon:
Write in Chinese then. I can read.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] maiksfirehdx:
Hello,

I had exactly the same problem. I could solve it by installing ADB driver manually via device manager. There was yellow exclamation mark at Android device. I choosed manually ADB Composite and after that fastboot was able to transfer twrp.

Hth

Maik

Gesendet von meinem KFHDX mit Tapatalk

---------- Post added at 05:20 PM ---------- Previous post was at 05:12 PM ----------

Hello Hashcode,

first I want to thank you for that awesome work. [emoji3]

And I have a question regarding wifi. After some idle time connection to my AP gets lost, switching to airplane does not help. I need to open wifi config and reconnect to the AP. Disconnect also happens during regular usage such as playing games or surfing.

Are there any plans to fix this in near future and what can I provide for analysis?

Best regards and thank you in advance

Maik

Gesendet von meinem KFHDX mit Tapatalk
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
[MENTION=5749760]ggow[/MENTION] - of possible interest for future builds: https://lineage.microg.org
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steffen19:
Hi Hashcode,

I'd like to test your camera fixes on a thor device. Is a new flash image planned for the near future?

Best,

Steffen
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up

- Dated 19 November 2017

- LineageOS upstream

- November security patches

- Latest camera patches included in kernel
[Kindle Fire HDX 7" & 8.9" Original Android Develop] 苏苏伍滋:
Thanks for the maintenance, I have already brushed the latest version, the camera can display the picture but take photos
[Kindle Fire HDX 7" & 8.9" Original Android Develop] steffen19:
Feedback on 19th Nov. Flash image

Hi ggow,

thank you for the new flash image with hashcodes new camera patches.

[MENTION=4243514]Hashcode[/MENTION]:

I noticed the same behaviour as written in the post from 1:14pm today.

The standard camera app can display a live image (there's no darkness problem anymore), but it is not possible to take a snapshot. I assume that it is due to some SELinux issues.

Whenever I try to take a picture, the app displays an error message, which says that an unspecified error has occured and it is closed after pressing 'OK'.

I'd like to test taking camera pictures with SELinux = permissive, but I don't know how to change the SELinux state.

Perhaps someone can help with a hint.

Audio output with the standard music app also seems to have a small problem. The widget works, but when the main app window is open I get error messages saying 'the audio file can not be played'. It seems that the widget and the main app window are fighting over the access rights.

Best,

Steffen
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stauraum:
boot-loop

Hello,

On friday i select 'encrypt this device' in the settings. Now the kindle hangs in a boot-loop. Today i wiped the complete device and reflashed it. But the boot-loop still appears. now since 2 or 3 hours.

whats wrong and how can i fix this?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
- boot into TWRP

- perform a full wipe of *all* partitions including internal storage

- reboot into recovery (this step is important)

- tether device and download appropriate zips (ROM, GAaps, etc)

- flash ROM

You may have to update TWRP if using a build prior to 3.1.x.x. AIR only newer versions are able to deal with encrypted partitions.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] TacoLoco:
Great ROM, makes Fire HDX a really cool device! Are there any plans to port Oreo to this lovely device? :cool:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stauraum:
hmm ...

this doesnt work for me. Updated twrp to 3.1.1-1, wiped the whole System, rebooted and flashed Lineage, Gapps and SuperSu. But the boot-loop still appears. :(

Edit: with lineageOS 13. its working now. Thanks. (y)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Appreciate the update. You could try returning to Lineage 14.1 or try a different Nougat based ROM. I have been pumping AospExtended (AEX) of late for it's speed, stability and feature set. I'm a longtime CM/Lineage user but AEX provides the best experience on an Android device I have had to date. All the goodness of pure AOSP with a nice set of optional extensions.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jlbrown1:
[MENTION=5749760]ggow[/MENTION],

Any update on Bluetooth? I have tried many different methods, including the ones in this thread, to no avail. The tablet sees the headphones, it just will not pair.

Are there log files somewhere that I could post that would help?

Thanks!

J
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
FWIW - I have had no problems pairing a small collection of BT test devices (keyboard, mouse, earbuds, speaker, receiver) on AEX for Thor. Rather surprising as BT connectivity issues have dogged virtually all custom ROMs for HDX devices from Android 5.1 forward. Maybe just got lucky with my portfolio. That said, it's nice not having to switch to my phone to stream music to the home audio setup, etc.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stauraum:
I've tested now Lineage 14, AOSP and Slim. All are 7.1-roms. All not working. Reflashed Lineage 13 and now the tablet is working again.

Can the be a problem with the bootloader after selecting "encrypt this device"?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You could try reflashing the vulnerable bootloader but I doubt that will help. In all likelihood one of numerous (over a dozen) 'hidden' partitions was touched by the encryption attempt. At present there is not a comprehensive catalog of contents and, more importantly, a means for restoring back to 'stock'.

[MENTION=5828306]draxie[/MENTION] - thoughts?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Locked bootloader?

Given that hashes and signatures are checked before loading

each new stage in the boot process, the bootloader must be

good, if the device is able to boot at all. On the other hand,

based on what works and what doesn't, I'd say the bootloader

is likely locked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] stauraum:
Yesterday i've re-unlocked the bootloader. Every output says success. But i'm unable to boot any 7.x Android. hmm ... freaky ...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
I'm sticking with this at least conceptually. Nougat encryption is implemented differently than Android 4.4-6.x and remains a work-in-progress. The link below offers a laymen's perspective on some of the issues and hints at the problem you are currently experiencing. Me thinks the keys (or at least a flag) are resident in an area of permanent storage that remains untouched by standard partition wipes. Android 7.x based ROMs notice that and balk during boot while 6.x and lower ROMs are clueless to the previous device state. Good luck.

https://blog.cryptographyengineering.com/2016/11/24/android-n-encryption/