yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 5s Questions & Answers] thecresta:
Same here, ordered my Grey 4/128 on Friday, marked as shipped on Monday morning but status is still "Packed for picking up".

It's not the sellers fault, it's the busiest time of the year and I'm sure it's crazy over there. Would be good to receive it before Christmas but I'm prepared for it to arrive before new year (15 working days).

Service from the seller (Top One) has been very good so far.

Looks like I may have to spend quality time with my family over Christmas, rather than playing with my new phone all day. Booo! :)
[Xiaomi Mi 5s Questions & Answers] marcel112:
i like it more then stock one, also because i have to use an extra plug to use in europe.

With the blitzwolf i charge from 30 -> 100 within 20 minutes :p;)

So you can decide yourself
[Xiaomi Mi 5s Questions & Answers] BPSoft:
Same here, ordered Mi5s grey 4/128 at 6, Shipment information received by DHL since Friday, December 09. This is waiting for pickup.

It's sellers fault also, in China they use DHL HK because it's much more cheaper to export from there.

For that they don't request DHL for pickup, they have agents reponsable to deliver the packages at Hong Kong DHL offices.

This freight forwarder agent, could be a person or a company, there are thousands individuals and companies in china just doing that, and the quality of service varies from none to high quality.

So, i'm not saying christmas have not something to do with delays, but until the package is with DHL, i could only blame Top One for it's decisions.

The truth is, i've probably choosed the best and more expensive distribuitor in the world, and i'm totaly dependent of a mediocre man in the middle at a christmas attack. LOL :D
[Xiaomi Mi 5s Questions & Answers] Carlosbgx:
I havent tried it and couldnt really help u with ur exact question. Anyways, Aukey seems like a good brand for qc3.0 (according to what ive heard) plus well pricing and amazon i believe
[Xiaomi Mi 5s Questions & Answers] thecresta:
For people waiting for Christmas delivery via European Union Express (myself included) - in addition to delays at HK there have been flight delays and cancellations at London airports due to heavy fog over the last two days, so you may have to wait a little longer.
[Xiaomi Mi 5s Questions & Answers] qverkk:
Guys, my phone is in my country and i saw something like "customs status updated" is that any bad news? Am i going to pay tax? Or idk how to check if i got any tax on The phone
[Xiaomi Mi 5s Questions & Answers] patoberli:
It anyway has to go through customs, the question is now if they will add oder check it for free. This is something you will see once you pick up the phone, or up to two weeks later (depends on the country). I received a bill from DHL around 2 weeks after the delivery, but I also don't live in an EU country.
[Xiaomi Mi 5s Questions & Answers] BPSoft:
Yes, that "customs status updated" is normal with or without customs duty involved.
[Xiaomi Mi 5s Questions & Answers] qverkk:
Alright, got my phone today :D will test it in 3 days. Only 100 pln tax tho, it's like 20 something Euro so it's all fine :D
[Xiaomi Mi 5s Questions & Answers] BPSoft:
That is something that i will not accept if it happens to me.

Here if customs duty is applicable, DHL charge around 50eur for his clearance service plus my country duty for electronic devices.

Do you check if DHL consider you live in a remote area?

You could check here: http://raslist.dhl.com/jsp/first.jsp

I thing 20eur is DHL aditional cost to deliver at remote area.
[Xiaomi Mi 5s Questions & Answers] qverkk:
I didn't check it but it says this: "The location you have selected is not a remote area or is not a valid selection."
[Xiaomi Mi 5s Questions & Answers] BPSoft:
Thank you for replying :)

What the receipt says you've been charged for?
[Xiaomi Mi 5s Questions & Answers] qverkk:
I'll check that within 2 or 3 days bud :D but for sure i'll let you know. I did order it to my origin home, not to the flat i rent for studies atm :D cause i didn't know if it will come on christmas holidays or not, so i wanted to be safe and get it :D
[Xiaomi Mi 5s Questions & Answers] qverkk:
It did say that DHL paid my tax and I have to pay it to them. Plus the screen protector is a bit small that I got within it damn
[Xiaomi Mi 5s Questions & Answers] hafatih27:
I'm wondering why do you guys even need to buy a dedicated QC3.0 charger since my standard charger reads "5V~2.5A/9V~2A/12V~1.5A"? Doesn't that pretty much equal to 18W which is offered by QC3.0? ?
[Xiaomi Mi 5s Questions & Answers] patoberli:
I am not fully sure, but I think a QC charger has some special chip inside which allows the phone to tell him to deliver more power.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Disclaimer

[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired [B]because the alarm app failed[/B].
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]

Rules

- Please search the thread before asking questions

- Please try to stay on topic, I know it's not always possible

Reporting Bugs

- Please report bugs here

- Report only one issue per bug report

- When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...

- Explain the issue as clearly as possible

- Explain the steps required to reproduce the issue if necessary.

Prerequisites for Installation

- Must have an unlocked bootloader

- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo).

Project Status

BETA TESTING -- QUALITY IS GETTING BETTER BUT TAKE A LOOK AT THE FUNCTIONALITY GRID IN POST #2

KNOWN ISSUES

- Thor/Apollo: Some apps may rotate to landscape the wrong way leaving the screen upside down. Many times you can re-rotate the device to fix.

- Thor/Apollo: Sometimes after an extended period of time Wifi will stop working. Toggling airplaine mode fixes it.

- Thor/Apollo: Bluetooth pairing issues - bluetooth function is still WIP.

Fresh Installation

- Backup your existing ROM first

- Wipe the /data partition (but you can keep the media storage)

- Flash the ROM File

- Flash Open Gapps: use an ARM 7.1 version smaller than the "full" size to make sure it fits

- Reboot

- Enjoy!

LineageOS Developer Builds / Downloads

LineageOS Builds for Thor

LineageOS Builds for Apollo

Gapps

- Open Gapps (use a size smaller than "Full" to make sure it fits)

NOTE: Here's what I do to solve the "Play Games" side load issue... Anytime I update my GApps zip file:

- I download the "full" and "mini" versions of GApps

- Extract the "GApps/playgames-arm.tar.lz" file from the "full" file and add it to the "GApps" folder of the "mini" file.

- Open the installer.sh script in the "mini" file and move the "playgames" line from the full_gapps_list= section into the mini_gapps_list= section

- I use this modified "mini" .zip when flashing CM-14.1 ROMs so that my Play Games install always works.

Source Code (branch: cm-14.1)

- Kernel Source

- Common Device Tree

- Thor Device Tree

- Apollo Device Tree

Credits

- LineageOS Team

- Cyanogenmod Team

- CodeAurora

- ggow

- Cpasjuste

- dpeddi

XDA:DevDB Information

LineageOS for Kindle HDX 3rd Gen, ROM for the Amazon Kindle Fire HDX 7" & 8.9"

Contributors

Hashcode, ggow

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

Based On: LineageOS

Version Information

Status: Beta

Beta Release Date: 2016-12-16

Created 2016-12-11

Last Updated 2020-07-05
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Reserved

SEE ATTACHED ROM FEATURE STATUS GRID

CHANGE LOG

20161208: Initial build released

20161214:

[CM Base] merge changes for Android-7.1.1_r4

[CM Base] merge changes for Android-7.1.1_r6

[KERNEL] Updated for 38 CVEs

[TEMP] Turned off SElinux Enforcing due to Android-7.1.1 changes

[SELINUX] Initial fixes for Android-7.1.1 merge

[CAMERA] Fixed camera snapshot bug by enabling libs with text relocations (KitKat libs have them)

[BUTTONS] Fixed overlay to remove hard key settings for buttons that don't exist

20161215:

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

20161216: Nightlies for CM 14.1 started

20161230: First Thor build of LineageOS (was CyanogenMod's -- now forked for community development)

SElinux back to Permissive mode -- let's see if this makes functions like bluetooth and camera better
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Future work task list:

- [Apollo] Debug rotation / wifi issues that certain users are experiencing

- Pull in more Google kernel/common changes for better compatibility

- [IN PROGRESS] Orientation and gryo sensor changes to correct odd rotation selections by apps

- Full device encryption support (requires working amazon keystore HAL)

- Audio FAST mode during low power can cause audio skipping (headphone use case w/ screen off)

- More bluetooth stack testing (may need to compile static version of BlueZ to run some tests)

- Look into changes for allowing Viper4Android integration w/o needing SU or breaking SELinux

- Re-enable thermal protection for the audio HAL. NOTE: when setting prop persist.speaker.prot.enable=true it kills all sound. Needs debugging.

- Research adding kernel commits to support double touch to wake support

- [FIXED 2016-12-22] Add volume button configuration settings back into CM

- Possibly write a bootloader firmware ID script which can be run to determine user's bootloader version

- Look into audio HAL changes which would increase volume while keeping clarity (similar to Viper4Android)

- Continue work on camera HAL from source [LONG TERM PROJECT]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NeverSmile:
OFMG. It's possible. Thank you so much. [emoji106]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
First thing to testing is WIFI. I made some changes to the WIFI configuration which differs from CM-13.0.

So if you've previously experienced difficulty in this area and are willing to help test, please let me know what your experience is like.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NeverSmile:
when i complete install and use Super Su v2.78 via flash. Wifi cannot turn on.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] tvd0405:
WiFi seems to work fine for me. I did not flash any root. I am using the default one that comes with CM

---------- Post added at 03:00 AM ---------- Previous post was at 02:41 AM ----------

Camera does not work (fc)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
I had a string of annoying issues with SuperSU v2.78 including reoccurring loss of root on CM 12.1. Drove me half nuts! Downgrading to v2.76 (terminal build by ChainFire) solved all problems. I realize 2.76 doesn't directly support Android 7 but v2.78 seems to have bigger issues. Might stick with integrated CM 14.1 privacy/root manager for now.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Agreed. Specifically: I have not tested external root at all.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
I tested Thor front cam with "YouCam Perfect" found here:

https://play.google.com/store/apps/details?id=com.cyberlink.youperfect

Can you check that as well?

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] tvd0405:
I got "camera error" with this app when trying to take a picture.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
Hmm. Sounds like I may need to do some debugging. Thank you for testing.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Grtschnk:
I can confirm the problem the camera. Tried a few different apps. Some are able to show the preview but none can actually take/save a picture. (Still more useful than FireOS..)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Apollo version

Yes, we will need to release the new recovery. The TWRP version that I released (3.0.2-0) had issues that have since been fixed in the omnirom_bootable_recovery tree.

---------- Post added at 10:54 ---------- Previous post was at 10:36 ----------

I have built the Apollo version, will post it if all is good later this evening.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] GameExpertNetwork:
WOOOO!

EDIT: when will the recovery be released?

---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------

@ggow, when will the new recovery be released? And should it be flashed before or after cm-14.1?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'll build TWRP for Apollo and check it. I'm guessing [MENTION=4243514]Hashcode[/MENTION] will release it for Thor.

You should use the new recovery ASAP so flash and use on the next ROM upgrade.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] GameExpertNetwork:
Crap... so I have to wait?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
No you can flash it now, with the existing Thor recovery. When the new TWRP is released upgrade when it suits you.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] GameExpertNetwork:
Ok, thanks!

---------- Post added at 02:57 PM ---------- Previous post was at 02:52 PM ----------

also, may I suggest providing md5 files?

---------- Post added at 02:58 PM ---------- Previous post was at 02:57 PM ----------

Errr.... Problems with installing cm 14.1 on thor w/ TWRP:

E1001: Failed to update system image.

E:unknown command [log]

E:unknown command [log]

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

oops, the error was my fault, forgot to restart recovery after wiping data

---------- Post added at 03:21 PM ---------- Previous post was at 03:00 PM ----------

boot animation seems to be taking a long time

---------- Post added at 03:40 PM ---------- Previous post was at 03:21 PM ----------

[IMG="yep it works"]https://aww.moe/x84x02.png[/IMG]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Grtschnk:
I had the same error as you, but the ROM seems to work fine. Could you elaborate on this restart issue? (Never heard about this before) Not sure now if I should reflash or just leave it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] MahmudS:
Wi-Fi speed falling down to zero after few minutes when screen is turn off, it's global issue, or I need to change some settings? TWRP 3.0.3-1, CM14.1 for Thor from 20 Dec.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] preisl:
I have the same issue with wifi... my AP is off during night time and the HDX (Thor) never connects automatically in the morning. I wanted to work around that by using Automate, so I created a flow to connect, but it simply doesn't connect. Thanks for the hint with wifi manager, but it also doesn't connect (automatically). So the only working method for me is to connect manuallly -which works via default Android settings and with Wifi Manager :)

Cheers,

Martin
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Interesting. My secure AP is up 24x7 (except for the rare power outage and a weekly automated reboot) so I don't have much experience with that scenario. Have you tried assigning a static IP either on the AP or device? Possible DHCP is getting in the way (albeit unlikely).

BTW - if you like WiFi Manager a new build can be found here: http://www.aqua-mail.com/forum/index.php?topic=4823.0
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Zathor:
Apollo, TWRP 3.0.3.0 (same with 3.0.2.0), cm-14.1-20161219-NIGHTLY-apollo

I have to manually update to new nightlies as the CMUpdater cannot restart automatically into recovery mode. Also I cannot reset to factory defaults. Is that an issue of my device only or a common one?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
You need to install cyanogen recovery if you want that functionality.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
...and ask yourself if you really want/need that capability at present given the state of the ROM (early maturity) and recent experience with CM 13 nightlies.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DHD:
I can not install Aroma Package (downloaded from opengapps.org). It's automatic reboot while installing the pakage then boot to OS.

Same on hashcode's build (downloaded from first page) and cm-14.1-20161219-NIGHTLY-thor.zip from download.cyanogenmod.org.

TWRP 3.0.3-1 from http://xdaforums.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547

P.s clean flash, storage almost empty.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
CM recovery needs some work I think so that devices w/o a misc partition can work. Not recommended at this time.

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hashcode:
I haven't tested Aroma on HDX devices. I'll try and keep this on my TODO list, but I'm curious what the use case is for Aroma?

- Hash
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DHD:
Thank you for feedback!

I have a issues: I can not log in Google Apps (Maps, Google App...) which installed from Play store => I tried flash them by Open Gapps (mini) => Almost app running smothly but can not get Google Now feature running => trying install Aroma package.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Zathor:
Thank you very much for your replies (also to Davey + ggow).

I do have an Nexus 7 (flo) with CM 14.1 and TWRP recovery. On that device I can restore the factory defaults and flash new roms from within the CM updater. Maybe this device has the misc partition.

As I was curious I tried to flash the recent CM recovery but this does not work ("fail: size too large"). It was worth a try at least, I am back to TWRP 3.0.3.1 and manually flashing the new ROMs.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] GT725:
Good morning, I need your help please.

Have the Fire HDX 7 "(Thor)

TWRP 3.0.3-1 is Installed and Operated

There is no OS installed (Full Wipe)

I now install CM 14.1 Starts the device only up to the gray Kindelfire logo. I wait 10 minutes brings me there not further.

I run a full wipe out and install CM13 (07112016) on Fire HDX 7 "It works.

What am I doing wrong that does not work on my HDX 7 "?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NextDroid:
Verify the integrity of the CM 14.1 .zip archive. That's what I would do first. Also, this happened to me a couple times with this exact ROM because it didn't download correctly the first time.

Tapatalk を使用して私の Kindle Fire HDX から送信
[Kindle Fire HDX 7" & 8.9" Original Android Develop] GT725:
Cm-14.1-20161222-NIGHTLY-thor.zip Downloaded

Sha1 and is correct

ZIP file checked for errors, not found

CM14 installed hanging at the gray logo
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NextDroid:
I can't think of anything else... We need the pros to answer this one... Perhaps I'll learn something new too.

You have the latest build of TWRP, performed a clean flash...

Maybe stay on CM13 for now? I don't know what else to tell you, sorry...

Tapatalk ã‚’ä½¿ç”¨ã—ã¦ç§ã® Kindle Fire HDX ã‹ã‚‰é€ä¿¡
[Kindle Fire HDX 7" & 8.9" Original Android Develop] GT725:
Here the log files, maybe help?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
hey i cant add it for review at cm so i post it here....

patchset: add smoothness to our device

rootdir/etc/init.target.rc

# Adaptive LMK

write /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk 1

write /sys/module/lowmemorykiller/parameters/vmpressure_file_min 53059

hope somebody can at it at gerrit
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NextDroid:
I have never really analyzed .log files before for any particular reason, so this is a learning opportunity xD

I looked in the dmesg.log for the kernel output, and it looks like the problems start when the second stage of the SELinux initialization starts (8.283966), with invalid keywords and whatnot, and then I start spotting errors seeming to be related to the EXT4 filesystem (9.831130). Maybe these are related to the denial of the write permission (9.536125) a few lines above.

I couldn't find anything of interest in the recovery logfile, though...

Tapatalk ã‚’ä½¿ç”¨ã—ã¦ç§ã® Kindle Fire HDX ã‹ã‚‰é€ä¿¡
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Paladin@1976:
I flashed CM14.1 today and had no problems with flashing. But after first start of CM14.1 I had to take some configuration like language, wifi, google account and more. Is it normal that there are many pages beeing blank and only a skip button appears? I skipped all these pages and finally I got the normal android start screen without errors. Play Store is also working and settings too. I would like to know what configuration I skipped.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Bawdy George:
You rock. Since the bootloader unlock discovery, I have added to my 32GB Thor a cheap used 16GB Thor and should be receiving my cheap used 16GB Apollo any day now. Your unofficial 20161216 CM 14.1 build is the first CM build I've tried since CM 11 that can do Chromecast screen share - albeit with the "not optimized" message, but still.

For Thor, with a clean flash using TWRP 3.0.2.0, I cannot get BT to pair with my TDK A33 speaker, though it does see it. Also the native camera app gives a "can't connect to camera" error. No 3rd party camera apps that I've tried seem to work either. No screen rotation or wifi issues to report here. Haven't tried any of the nightlies, but I'm happy to run through anything that would help as I'll have both a Thor and Apollo (wifi only) at my disposal.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NextDroid:
Welcome, Bawdy!

You can refer to the spreadsheet in the 2nd post of the thread by Hashcode on the status of ROM features here:

http://xdaforums.com/kindle-fire-hd...-14-1-thor-t3517481/post70044211#post70044211

Also, the camera discussion has been going on for a while now in the past few pages. Good to have a tester with both Apollo and Thor available :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Bawdy George:
Forgive my ignorance, but for ROMs with root ability built into the developer options, what's the advantage to using SuperSU? Is it just that it has more granular options, and logging in the paid versions?

---------- Post added at 01:02 AM ---------- Previous post was at 12:51 AM ----------

Thanks. It's the least I can do, as I don't have great coding/scripting chops but am very experienced in troubleshooting. I saw the support matrix, which is why I mentioned the bluetooth and camera issues as they appeared to conflict. I can get the YouCam Perfect app to connect to the Thor camera, but it seems to be calibrated incorrectly in that the light level in the camera image is very faint.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Hi [MENTION=7907328]Bawdy George[/MENTION] - great report (including recent updates)! For awareness the primary HDX developers are spending time with family as 2016 winds down. Don't get discouraged if you don't see immediate feedback; I'm sure both will be back online by early January. Enjoy your newly liberated devices!

---------- Post added at 07:42 PM ---------- Previous post was at 07:35 PM ----------

You summed it up nicely. The integrated root/privacy manager in CM does a decent job and pretty much stays out of the way unless configured otherwise. The exceptional SuperSU goes further as you noted but there is no inherent advantage for routine use unless you want/need some of the embedded functionality. I have SuperSU installed on some devices running CM ROMs, others not. If specific SuperSU capability is not needed having a 3rd party root manager on board represents unnecessary complexity.