yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Guitarman:
Get out the multi-meter and check exact output of the power supply. We had a PC acting up and it came down to 2 possible problems: motherboard or power supply. I was tempted to purchase a new power supply but glad I didn't because it was putting out the correct voltage. I don't know if this helps you with your particular situation but someone might find it helpful.

If you know the board is getting correct voltage you can look else where for the issue. It possibly could save you from purchasing a new motherboard. YouTube has a plethora of tutorial videos on checking them :)
[Kindle Fire Android Development] pfederighi:
So far I've got 5.05V and 12.08V. It's extremely steady.

Update:

I think the issue may not be the motherboard or the power supply but rather a bad audio cable. That is, I think it may be short circuiting inside the cable, causing too much current to go through the audio port, thus causing the board to reboot. Since I've removed it, I've had little to no problems. I still haven't tried reconnecting my DVD drive, though. I'll try that later. So, if nothing else, it's progress.

And... A very joyous Christmas to you all.

well... so much for the audio cable theory. I'm back to bad board as the top culprit. Maybe someday I can do some development again.
[Kindle Fire Android Development] dokie80:
merry xmas too.... :D
[Kindle Fire Android Development] Guitarman:
Thanks for your perseverance with this device. :)
[Kindle Fire Android Development] dokie80:
soooooooooooo.. how are you guys!!!!

happy new year!!!!

anyway, since lovejoy777 (got amazon fire), and pfederighi stop dev-ing coz of his PC problem.. does it mean the original fire is unkindled? :D

i'm back to pfederighi's otterx-cm11.. seems to be more stable than 10.2 one.. plus I still get better battery life on that.. probably will stick with it until the hardware give up..

I want to thank all devs that already support much for this device.. make this "cheap" tablet, worth more than all my other gadget.

after trying out almost every rom available, I recommend this two roms:

- OTTER : jandycane, my first custom rom on KF1.. I probably will switch back to this later, battery life is decent as far as i remember, used this for my kids to watch movie before she gets my wife's ipad

- OTTERX : pfederighi'c cm11, best battery

- OTTERX : lovejoy's slimkat, best performance
[Kindle Fire Android Development] mclad:
We care! Keep building speedy long-battery life KK roms for our otterX's... LP & MM are too laggy, but my two otterX's do good service, one stuck to the fridge door providing photoframe/shopping list/recipes/weather and the other with line-out going to my PA system and running plex & other audio apps (and being a dumb digital photo frame other times)
[Kindle Fire Android Development] pfederighi:
A happy new year to all. So far I'm enjoying being employed again, though it does mean less time spent trying to develop stuff. Oh, well.

Who likes good news? Everyone? Then: Good news, everyone. I think I'm back. I don't want to say definitively, because I'm still not 100% sure, but so far so good. On a whim I installed my old motherboard that I had never gotten around to taking to the electronics recyclers. I thought perhaps it had never been bad at all, rather it didn't like working with my old failing power supply (the one that went blew up). To my surprise, it worked fine and has been working fine for several days now. In fact, I've managed to get CM-9 built, albeit in a virtual machine running an older copy of Ubuntu. However, that alone makes me think that everything is good. I still don't know for certain that my new motherboard is bad since I forgot to uninstall my firewire card to see if that fixed things. Maybe someday I'll get around to testing that setup, but probably not since things are working well and my old board has builtin firewire.

Anyway, I'm now trying to convert CM-9 to OtterX. The device tree is very different compared to CM-10/11/12. Though by going through it I've found some command line options that may be applicable to the newer versions that might free up some RAM, probably at the cost of video performance. I hope to have something to report soon.

[MENTION=994299]dokie80[/MENTION] The 10.2 build is unstable? Hmm... What are you running? Is it GApps? With the exception of web browsers, which may have more to do with JellyBean's release of webkit than anything else (though this reminds me I meant to try ripping the webkit tree from CM-11 and placing it in CM-10), I've found it to be quite stable. In fact, I liked it so much more than CM-11, I never intended to go back.
[Kindle Fire Android Development] dokie80:
not that unstable..... but sometimes it's stuck on boot animation... two times, it shutdown itself because of low battery, so I charge it and go to sleep... the next night I look at it, it stuck on bootloader, with no menu show up, can't boot it up to system.,

I actually think it's over :D, but after try many thing (trying fastboot command to flash bootloader etc, entering recovery, etc), I realize that the problem actually the battery is empty.. apparently when I first plug it to charge, it's stuck on bootloader, and probably freeze, and not charging... the second time it happen again, I already know what to do :D

I only use the ROM, no gapps.

btw btw btw... any of you use KF for streaming movie? I have problem using mx player to play movie.... I think It's cm's issue... because when I try using slimkat (AOSP) to stream using totalcomander + mxplayer, it works, but never works on CM (9, 10, 11)...
[Kindle Fire Android Development] Guitarman:
I'm currently using the 10.2 build and with the exception of the browsers closing, this ROM is stable and fast according to my personal experience. I can't wait for some updated older ROMs and will continue trying them all until this Kindle kicks the bucket. Soon I'll be testing ROMs on the 2015 Fire 7 :)

Is there a particular tweak for 10.2 to minimize the closing of the browsers? Or is there a particular browser that fares better in that department?
[Kindle Fire Android Development] dokie80:
i dont remember having browser issue...

alternative browser:

- lightning browser - download link - fdroid page
[Kindle Fire Android Development] pfederighi:
Hi all. Just an update. I'm making progress converting CM 9 to OtterX. I thought someone might want to know. It'll probably still be a while. I haven't forgotten about modding CM 10.2. I think once I get CM 9 done, I'll return to CM 10.2 and see about getting things like tablet mode to work as well as some other things. Cheers.
[Kindle Fire Android Development] dokie80:
thanks for ur effort. I ve been back and forth to otter jb aosp and ur otterx cm11. since I don't use the tablet a lot, I find that battery consumption is the most important thing for me, and no matter how I tweak other rom, I can't get similar result as ur cm11.

on standby, its almost like it doesn't use any power at all!
[Kindle Fire Android Development] pfederighi:
Thanks. I'm glad to see it still gets use. I wish the battery had been as good for the 10.2 build. Maybe someday we can figure out why.

An update: I finally got my first attempt at cm 9 otterx to build. It doesn't work. In fact, on booting it turns the KF off. Not sure where to proceed from here, but I'll keep at it.

edit: The unscientific me never tested my first cm9 otter build. I thought I'd try it. It exhibits the same behavior as the otterx build. So... back to the beginning. Does anyone here have experience building an ICS ROM?
[Kindle Fire Android Development] dokie80:
i'm guessing appops/privacy guard..

i see privacy guard on cm9 and 10 is different than the one on cm11...
[Kindle Fire Android Development] pfederighi:
I found different device & vendor trees from Hashcode for ICS. Why did I not see them on GitHub before? So far it's compiling as I type. I'll keep you posted.

update: partial success. I finally got a booting CM 9 ROM using the prebuilt kernel in Hashcode's device tree. Wifi doesn't work. Every time I compile the ROM and build the kernel along with it results in a "No Operating System Found" situation with TWRP. It, in fact, doesn't write the ROM to the system partition. I have yet to figure out why.
[Kindle Fire Android Development] dokie80:
the best. period. even on standby for all 8 days, for it to take only 30% battery is amazing.

note. the stat start from 60% because I just flash it that day.
[Kindle Fire Android Development] pfederighi:
CM-9

Finally! I've got an otter build to compile, install, and work. It seems the issue is that CM-9 otter ROMs won't install with TWRP newer than 2.6.3.1. What gives? It's just a zip file. Maybe the TWRP BusyBox needs to be updated.

So, now the battle is to get otterx to build and find some way of installing it. Since there's no otterx/f2fs version of TWRP older than 2.8.2 (or something), I guess I'll have to learn how to build TWRP as well.

I am pleasantly reminded of how much the performance rocks over newer versions of CM.

I'll keep you posted.
[Kindle Fire Android Development] dokie80:
oh, I thought u already know about that.. I always use twrp 2.2.2.1 on otter, since I usually flash jelly bean rom..

good luck..
[Kindle Fire Android Development] bflobills:
What version of cm11 is that you're running?
[Kindle Fire Android Development] dokie80:
see my post here... http://xdaforums.com/showpost.php?p=64730596&postcount=108

or go to pfederighi'c post about the rom. link here: http://xdaforums.com/showthread.php?p=62173645#post62173645

note. both are otterX ROM
[Kindle Fire Android Development] pfederighi:
Hey all. Well, I've got CM9 OtterX to boot. That is, it boots and I can access it via adb. I suppose if I can figure out the init scripts, it might make it all the way to graphical. I suppose it's progress, right? I'll keep you posted.
[Kindle Fire Android Development] dokie80:
take ur time. not going anywhere. :D
[Kindle Fire Android Development] pfederighi:
So I've given up on the CM-9 OtterX project for a while. I thought I would see about improving the CM-10.2 build, which, in turn, helped me to figure out a major problem with CM-9 and why I couldn't get it to boot to GUI. Perhaps I'll resume sometime. Anyway, I present CM-10.2 SGT7 OtterX compiled with JustArchi's flags, Linaro Toolchain (the first time it's ever worked for me), and Sabermod Toolchain. Enjoy. https://drive.google.com/open?id=0B7BjC3Ky49TVd0VIX1lKOWh6dHM

The good:

* Decently fast without overclocking

* Tablet mode works great

* Jelly Bean 4.3 is still widely supported

The bad:

* Reboot to recovery from the advanced reboot menu doesn't work. Don't use it. It will sit with a "Rebooting" window forever.

* Gesture (swipe) typing doesn't work with the AOSP keyboard.

* The stock browser is horrible and will likely crash

* Battery life isn't so great

* Probably more...

Untested:

* Gapps. Try at your own risk. Let us know how they work and what Gapps package you use.

Suggestions:

* Lightning Browser

* Naked Browser

* Deadline or SIO I/O scheduler
[Kindle Fire Android Development] Samuelgames:
Has anyone been able to get evdev touch input working over X11? I have a nearly fully working port (With all components but touch working) of Ubuntu but X crashes with a segfault whenever I touch the screen
[Kindle Fire Android Development] pfederighi:
Is that plain Ubuntu or Ubuntu Touch? If it's Ubuntu Touch, is it Hashcode's preview release or something newer? Can you check the kernel log (dmesg or /proc/kmsg) or the X log (/var/log/Xorg.0.log) and see if there's any clue as to why it's crashing?
[Kindle Fire Android Development] t3chwizard:
This is likely so CPU intensive it will be horribly slow lol
[Kindle Fire Android Development] pfederighi:
So, yeah, there's more...

* I recently reinstalled "The Silent Age" because I really like it and I figured I should finish it some day. The sound is horrible and about 80% of the graphics aren't rendered.

* It appears that any browser that uses WebView its web rendering engine will likely crash for no particular reason. Sadly the WebView engine is very different in KK and newer versions, so there's no backporting it. Google has also abandoned JB and will not even fix the security issues in the existing WebView engine.

My only thoughts on these are possibly too much optimization and/or the SGT7 frameworks/base/ tree is messing things up. I'm leaning towards the first option and will be compiling an unoptimized version as a comparison.

update:

So I left the compiler flags the same as stock CM with the exception of leaving out debugging symbols, that is '-g', since if one isn't running a program in a debugger, it just adds bloat. Sound is now normal. Many background graphics still aren't rendered in The Silent Age - I assume other apps are affected as well. The speed is still decent. I will try changing toolchains and see if that helps.

update:

The graphics issue may just be that one app. Or maybe it doesn't like JB. I'll upload an update that at least will have better sound.
[Kindle Fire Android Development] pfederighi:
Here it is: https://drive.google.com/open?id=0B7BjC3Ky49TVd0VIX1lKOWh6dHM
[Kindle Fire Android Development] chykal:
Thanks pfederighi. Running well and sounds good.
[Kindle Fire Android Development] Samuelgames:
Perfomance is actually pretty damn good on my experience, what bottlenecks the Otter is Android, there is nothing that is CPU intensive on an idle or common use case since hardware is initialized properly
[Kindle Fire Android Development] chykal:
This is very interesting. How is it going? Do you plan to share it once touch is working?
[Kindle Fire Android Development] pfederighi:
Hello all.

I have long had the thought that f2fs has been a hindrance to the smooth functioning of the KF ever since it was introduced as the new standard for OtterX. My thought for this was based on the fact that I tried f2fs on my phone and it performed worse and that the KF also performed worse with OtterX/f2fs. So, I wondered what would happen if I switched to OtterX/ext4. This is the result. Overall, I'm happy with it.

Pros:

* Smooth

* OpenGapps work well. Other gapps probably work well, too.

* ART works well

Cons:

* As always, possibly over optimized. That is, some apps just don't want to work (It might be a hardware limitation, as well).

* Battery life isn't that great. I don't know why. It has the same kernel that I used for the ROM with better battery life.

* Installing even the barest of gapps will eat up memory and CPU time.

Suggested settings:

CPU governor: interactive

I/O scheduler: deadline

Allow purging of assets: yes

Kernel Samepage Merging: if you need/want the potential extra memory, sure

16 bit transparency: yes

To install:

1. Format your /data partition to ext4 with TWRP.

If you have an older OtterX TWRP that doesn't support changing the file system then:

1a. Boot to recovery

1b. Connect to the KF with adb: adb shell

1c. Unmount your data partition: umount /data

1d. Format your data partition:

without journal (because it's faster and it's not really needed): mke2fs -T ext4 -O ^has_journal /dev/block/mmcblk0p12

or with journal (because you're paranoid ): mke2fs -T ext4 /dev/block/mmcblk0p12

1e. Reboot to recovery with TWRP

2. Copy the ROM to the KF: adb push cm-11-20160831-UNOFFICIAL-otterx.zip /data/

3. Install ROM with TWRP

4. Reboot and enjoy

https://drive.google.com/file/d/0B7BjC3Ky49TVemVyVzJ6ckZLcUU/view?usp=sharing

Here's a question: Does anyone know what the mystery kernel command line option 'newbootargs' does? The ROM doesn't work without this magical argument. I think Hashcode added it for use with OtterX, but I can't find any source that actually uses it or a definition if it's an alias for something else.
[Kindle Fire Android Development] dokie80:
huh! happy to see there still someone developing here :D

I just recently fix my KF charging port, cost me around 9-10 USD... I know... Its too much, considering the new kindle is only around 50 USD (but no kindle sold here officially, while unofficially is much more expensive)... anyway... can you please try if youtube kids works on that rom?

I currently using Jandycane ROM on otter.. last I tried, YT Kids doesnt work on otterX cm11, so I revert back...

many thanks for still developing for this device :)
[Kindle Fire Android Development] sd_shadow:
maybe [MENTION=4243514]Hashcode[/MENTION] would even like to reply
[Kindle Fire Android Development] pfederighi:
Hello all.

So, I recently installed the tried and true Netflix 3.0.0 apk, and it doesn't work. I tried other versions, and they don't work. I tried building an unoptimized CM11 and it doesn't work. I downloaded the latest official OtterX build from CM, and Netflix still doesn't work. The Netflix help center basically says to clear the cache and or install the latest version of the app, neither of which solve the issue. I haven't yet tried earlier versions of CM or other KK ROMs.

Is anyone else experiencing this? Have you found a solution? Thanks.

Other news: coming soon: an updated CM11 that (I'm pretty sure) doesn't have the annoying WiFi issue of dumping errors to logcat every 2 seconds. I don't think it'll be any different in terms of functionality, but it might be ever so slightly faster.
[Kindle Fire Android Development] dokie80:
I don't use Netflix, but i think it's the same reason why I can't stream movie from NAS (DLNA) using mx Player. It work on slimkat though.

I'm still on jandycane rom now, the kids only use it to play YT Kids.

Oh... And hello to you too.. :laugh:
[Kindle Fire Android Development] pfederighi:
Is anyone good at diagnosing wifi issues on the KF? I thought it'd be cool to have an AOKP KK build. So I did one. It's smooth like butter, but wifi doesn't work, and I can't figure out why. The kernel modules load, but any attempt to run wpa_supplicant dumps errors on logcat, none of which are helpful, mostly that the device is not ready. I couldn't decipher anything from dmesg either. So, if you have any ideas, I'd appreciate them. I can send/post dmesg & logcat if needed.
[Kindle Fire Android Development] daniel_303303:
I experience a situation that sometimes the kindle goes to sleep and cannot wake, the battery is drained rapidly in that case. It is experienced in many ROMS, is this my device issue? Anyone experience that or have any idea about how to tackle?
[Kindle Fire Android Development] dokie80:
some rom (mostly KK rom), has a deep sleep issue, caused battery drained. u can try using doze app on lolipop rom, or use similar apps to prevent apps to wake the device, or u can use JB rom, that's known not to have that issue...

for KK rom try pfederighi's cm11 rom (otterx rom) that has a fix for that issue... combined with appops (prevent apps to wake up / disable stay awake and wake ups)...

good luck
[Kindle Fire Android Development] daniel_303303:
The device is actually crushed during sleeping and cannot turn on by tapping the power button. I have to force close the device by long pressing the power button and reboot.
[Kindle Fire Android Development] dokie80:
you should let us know what rom you have, and how often u face this problem...

if you already use the rom for a long time and recently have this problem, probably better to do factory reset than trying other new rom you never try...

there are several reason why the kindle crashed when sleeping.... some app using cpu too much to do something, cpu freq too low... or you u can also try other cpu governor... sorry no direct solution :D
[Kindle Fire Android Development] pfederighi:
AOKP KitKat

Hello all.

The hope of fixing the wpa_supplicant bug that dumps messages to logcat was a pipe dream. I thought I had it fixed, but I didn't. Oh, well, I provide a hack in this latest build.

Features:

Smooth

Art works well

Navbar is on the side in landscape

Error messages from wpa_supplicant commented out

CRT electron beam screen off doesn't rotate the screen grab 90 degrees

Lower minimum brightness

No sleep of death so far

Issues:

Sound isn't always good. I've noticed this in The Room 3 and The End of the World. I suspect it might have something to do with low RAM. Most apps I've tried seem fine, though.

Getting wifi to work for the first time is annoying. Keep trying it. Sometimes it helps to connect to an open connection first.

Wallpaper Cropper service crashes. I don't care, it generally annoyed me anyway. It does prevent Launcher3 from changing the wallpaper, so I replaced Launcher3 with Holo Launcher, which I like more anyway.

Other:

I added some free apps that I think are useful.

This is for an ext4 data partition. Does anyone want f2fs?

I suggest leaving the "wake on charge" option on. I have not experienced an SOD so far, but in the past, sometimes that was the only way to get my KF to wake up.

Raccoon - APK downloader from Onyxbits http://www.onyxbits.de/raccoon

Avoid Amazon Underground. You will likely regret it if you install it.

Thanks: [MENTION=4410674]lovejoy777[/MENTION] Steve, from your help in my attempt to build SlimKat, I got this to work and I understand Android ROM building a little better

Download:

https://drive.google.com/file/d/0B7BjC3Ky49TVRVhiT1F3ZjRfNTQ/view?usp=sharing
[Kindle Fire Android Development] pfederighi:
AOKP KitKat Sound Problems

The sound problem that affects some apps, I believe is an issue with the Unity engine. It affects many a device and ROM. I have yet to find a solution. The only solutions I've found involve changing the app source and recompiling it. I doubt developers would willing to do that. (There is one possible end-user solution, but it doesn't apply in our case) If I manage to find an end-user solution, or even a ROM modification solution, I'll post something here.

If you know of or find a solution, please share it.

Cheers
[Kindle Fire Android Development] King_root:
Guys how did you build lollipop and marshmallow for this device when cm11 was the last official update? Even I want to start building now.
[Kindle Fire Android Development] sd_shadow:
There are many threads about building roms on XDA, and most roms are unoffical before they are official
[Kindle Fire Android Development] King_root:
But there aren't really updated ones like for marshmallow and nougat? Do you know any updated ones?
[Kindle Fire Android Development] pfederighi:
Are you wanting to build LP, MM, or N for the Fire? Those versions of Android don't work so well with so little RAM. They use large amounts more RAM than KK, JB, or ICS. So, in order to get them to work, and have any RAM left over for apps, most of the RAM is compressed, which means lots of compressing and decompressing which leads to a less than stellar user experience. KK also uses compressed RAM in order to get it to run on 512 MB devices, but the effects are far less noticeable. Basically, I've really tried to use things newer than KK, and no matter how optimized I could make them, my user experience sucked, so I've given up on them. I've also given up on gapps on the Fire since even when they aren't being actively used by an app, they eat up RAM and CPU time.

Note: This is not meant to disrespect those who use LP, MM, N, and/or gapps on the Fire.

If you're wanting to build it just for the experience, I would start with Cyanogenmod which is now LineageOS (CM is still available on GitHub). It's well supported on most everything including, though not officially, the Fire. Hopefully the instructions will be reposted on the new web site. Basic instructions for LP (This is from memory. Please forgive me if I forgot something or if the order is incorrect.):

mkdir cm

cd cm

repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1

repo sync

source build/envsetup.sh

cd vendor/cm

./vendorsetup.sh

cd ../..

breakfast otterx

cd device/amazon/otterx

./extract-files.sh (Take a look at the script. This is mostly to copy the proprietary files from an existing CM install connected via adb and create some makefiles. You can also download the files from https://github.com/TheMuppets/proprietary_vendor_amazon and run the setup-makefiles scripts manually)

cd ../../..

brunch otterx

I hope this helps.