yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] stylon:
Hmm... I switched to 1.0.31, but same problem there, it simply doesn't find my Kindle Fire on USB. I do see it via 'lsusb' with 'Bus 003 Device 039: ID 1949:0005 Lab126' and I've also the 0x1949 in my ~/.android/adb_usb.ini, which didn't change and that had always worked. I also can't find an USB debugging option in the Android settings, so I assume it's on and adb is running on this ROM, right? I can switch back and forth to other ROMs and it works there without a problem, so it's not that my USB went bogus all of a sudden ;)

The apps I got working in the mean time. Just looked like I needed a full wipe and reinstalled them all again. There's some weird auto-arranging of icons especially those that are on the quickstart bar. I'm not sure anyone else noticed that? No matter how I arrange them they're all piling up on the left-most position after changing any of the icons on the home screen.

Once I've fixed the adb issue, I'll most likely stick with this ROM for what I would like to try as it promises some support from the CM community and I managed the build process now. I hope at some point Hashcode will accept patches from me as I'm also planning to look into the microphone and the distorted bootanim issues some time soon (did already some backlight fixes and rewrote the ambient light sensor driver).

Best,

STYLON
[Kindle Fire Android Development] wws12:
If you could fix the microphone that would be epic! Also, the debugging menu can be accessed by tapping the build number in "About tablet" 10 times. The adb option is in that menu. :)
[Kindle Fire Android Development] stylon:
That did the trick, thanks a lot! I must admit that I had read about the 10x tapping somewhere before, but never had to use it on any ROM and therefore forgot about it... ;).

About the microphone: I had looked into it before already on the AOSP ROM with a self-compiled 3.0.50 kernel and the recording mechanics of the driver worked, but it looked like that probing for the microphone didn't enable it (actually turned it on, then tried to detect again, failed, finally turned it off). I had added additional debugging output to the kernel to see what's going on there. The code I was analysing had been touched by Hashcode and it looked reasonably ok (checked against the tlv320aic3110 datasheet). I've a few more things to try out and let you know once I make progress.

Despite the basic driver stuff do we know that everything on top the kernel driver is already ok in order to connect to Google for speech recognition?

Best,

STYLON
[Kindle Fire Android Development] prokennexusa:
OFFICIAL CM10.1 + 3.0.50 Kernel for Kindle Fire [CM NIGHTLIES]

Just wanted to Thank you for an outstanding product we install this ROM weekly on customer's tablets. When they ask to donate we direct them to your User ID. Thank you Hascode for all you do here in XDA.
[Kindle Fire Android Development] wws12:
As far as I know, yes the driver is OK. You would have to confirm with Hashcode though. All I know is when I try to tap the microphone in Google Now, it opens the voice search "card" and freezes. The home button allows me to exit it and return to the home screen. I have this headset.

http://www.amazon.com/gp/product/B004PYEEZO/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
[Kindle Fire Android Development] stylon:
Mic works on this ROM!!!

I just retried to capture audio from mic on this ROM and first shot, first try, direct hit.... it works! It's still not routed correctly for Google Voice Search, but I was able to record audio with the tinycap tool that Hash added to the CM ROM. I just posted here in the mic dev section:

http://xdaforums.com/showthread.php?p=40674802#post40674802

Best,

STYLON
[Kindle Fire Android Development] wws12:
The latest CM10 nightly build?
[Kindle Fire Android Development] tmlhodge:
Whats going on with the boot animation?
[Kindle Fire Android Development] :
This is a known issue. Matter of fact, it is such a known issue that if you bothered to search for 30 seconds to 1 minute, you would undoubtebly have found your answer. I am not trying to be a prick, so please don't take it that way, but come on man...
[Kindle Fire Android Development] stylon:
I didn't try the latest nightly, as I did build a ROM on my own from Hashcode's CM source. That was on April, 8th, so, my configuration is closest to that. However, I assume the audio driver in the kernel did not change since then, so I'm sure the latest nightly should work, too.

Best,

STYLON
[Kindle Fire Android Development] jgreene1014:
New To The Kindle

Just wanted to say kudos to the developer this is very nicely done!
[Kindle Fire Android Development] wws12:
So what you are saying is Google Now/Voice search doesn't work yet because its not routed, but other third party apps do?
[Kindle Fire Android Development] stylon:
:D I only used Google Voice Search as example. I think mic audio isn't routed at all to Android apps as we didn't know yet from which audio sub-device to capture. I think it's now only a matter of writing a correct alsa.conf or adding the right pcm capture device to the Android subsystem.

Best,

STYLON
[Kindle Fire Android Development] wws12:
Is that easy to do? Lol
[Kindle Fire Android Development] Hashcode:
Hi Guys,

I posted in the other thread, but thought that here would also be helpful:
[Kindle Fire Android Development] wws12:
We are anxiously awaiting your return to KFire development!
[Kindle Fire Android Development] tobiascuypers:
off topic but 10,000 thanks for Hash!!

On topic: I have stretch homescreens option checked under launcher/homescreen. But it does nothing? Ive been able to live with it, just a little issue?
[Kindle Fire Android Development] Zzim:
Maybe i'm missing something or i'm just new to this but is it possible to switch from the phone UI to the tablet UI? I can't seem to figure out how to do this.
[Kindle Fire Android Development] :
Use TWA_priv rom
[Kindle Fire Android Development] ProfEngr:
Tried to flash this last night coming from NRG's ICS. Did a wipe of system/cache/dalvik (the usual suspects). Some odd things happened on first boot (I'm dual-booted with Modaco as Alt).

1) I had wifi link to my router on the choose language screen. How did that survive a wipe?:confused:

2) There were no soft buttons at the bottom of the screen. I got stuck in the wifi list screen with no way to 'back button' out.

Bad flash or something else? I've restored from nandroid for now.

Edit: one other thing. I'm still on TWRP 2110. Goo Manager says the 2.5 flash was successful, but it never sticks on reboot.
[Kindle Fire Android Development] tobiascuypers:
You should wipe data if coming from ICS. And look on this page for a flashable zip of TWRP 2.5: http://xdaforums.com/showthread.php?t=1592681

Should be in the last few pages from Ichigo
[Kindle Fire Android Development] ProfEngr:
I thought I did wipe /data; maybe I missed it.

I found the flash while waiting for help on #twrp. I haven't had a chance to wrestle it away from my daughter to try again.
[Kindle Fire Android Development] wws12:
Just updated to RC1 and it has run pretty well so far. Will report any bugs I find here.
[Kindle Fire Android Development] mstrpeter:
I love this ROM but Im debating on switching into something else because of the overnight battery drain issue. I've read posts till I'm crosseyed but I can't figure out if this is still an issue or if its just me. I see that deep sleep was supposedly fixed on 12/16 but I have issues and the 1 other KF that I converted is having the same issues. If I let it sit overnight without turning it off I will often come back to a dead kindle... But not always, maybe 75% of the time.

Any thoughts????
[Kindle Fire Android Development] sagnam:
Install Better Battery Stats and find out what app you installed is preventing deep sleep.
[Kindle Fire Android Development] loCe45:
As already suggested, Better battery stats is solution to your problems. You probably have a rouge service/app in background that prevents your kindle to go to deep sleep (wake lock), so be sure to check kernel and partial wakelocks in BBS app.
[Kindle Fire Android Development] rbeavers:
I had battery issues, did a clean install and the battery life is great.
[Kindle Fire Android Development] Peowraaku:
I just switched from an unofficial build to official snapshot. Is it possible to get tablet ui back?
[Kindle Fire Android Development] Pkt_Lnt:
Just a few posts above.

http://xdaforums.com/showpost.php?p=40913825&postcount=2474
[Kindle Fire Android Development] Hashcode:
Newest nightlies will include an all new audio driver in the Android OS. It works, but it's not finished (no MIC support yet).

I'll try and keep this updated as testing continues.
[Kindle Fire Android Development] tobiascuypers:
Jw.. Did [MENTION=4300906]stylon[/MENTION] ever request his change as a merge? Would be nice to have "out of the box" instead of flashing every time? I use his zip from the MIC thread to use my mic.
[Kindle Fire Android Development] Hashcode:
Last I saw, the .zip had mixed reviews.

However, now that I've updated the Audio HAL, (it uses the correct input # for the headset MIC). I just need to re-add the mixer setup to the mixer_paths.xml file and we should be seeing a working MIC.
[Kindle Fire Android Development] tobiascuypers:
Great! And I think some of the mixed reviews were from the voice feedback not working when talking to Google now.

When you get the new mixer setup will Google now work correctly?
[Kindle Fire Android Development] stylon:
I also had mixed results with the fix proposed in the mic thread, but no time to investigate further. If you've re-worked the HAL already it's best to wait for that. I'm happy to continue testing when you're done with it as I've a few other things on my plate currently.

Best,

STYLON
[Kindle Fire Android Development] Hashcode:
Best thing about the new kernel audio driver in 3.4 is that each device (speakers, headset and MIC) can be activated independently. Where currently the kernel controls main power switches for the speakers/headset/MIC together (based on headset pin insertion) and it seems like you get output OR input but not both. So any sound at all will stop input and immediately swap to output.
[Kindle Fire Android Development] goldflame09:
to me, and im no expert, it seems like the way that the current drivers are set up, that it is only able to handle one device at a time.

question though. if you get no sound out of the earbuds and they happen to have a mic, will the mic work for a little?
[Kindle Fire Android Development] wws12:
How its coming with the MIC hash?
[Kindle Fire Android Development] mstrpeter:
I finally got the battery to act up and this is what I see... I can't see the partial wake stats from the previous boot, unless there's something I don't understand about better battery stats. I don't know what to do with this information, so I was hoping someone could offer some insight :)

Thanks in advance. I don't think its a harware issue because the other kindle fire I installed cm on is reporting the same basic issue, although I've not run better battery stats on it yet
[Kindle Fire Android Development] Hashcode:
More changes in the next nightly (or actually I may have missed the timing on today's.. so tomorrows nightly)

I went ahead and wrote a sensor HAL (Hardware Abstraction Layer) for the Kindle Fire / Fire 2 to replace the Amazon binary "sensors.otter.so" that is currently being used. This goes hand in hand w/ the bma250 accelerometer driver update for our 3.0 kernel (I developed the update in the 3.4 kernel and backported it into our current kernel).

What does this do for us? Nothing. Really.

The sensor HAL is a wrapper which reads the input events from sensors like accelerometers, gyroscopes and other "chatty" sensors. They get buffered by the HAL so that the OS can pick several events up at once and handle them appropriately.

What this REALLY does is gets rid of a binary file dependency. We've been using the Gingerbread sensor HAL from day 1. And it'll be nice to have a spot to add the light sensor events when I get more time.

In the world of Android, source is king because it allows us to upgrade over time, where proprietary blobs eventually cause a huge amount of problems ...

Enjoy.
[Kindle Fire Android Development] Hashcode:
I'm knee deep in dev for about 6 devices at the moment. I'm going to lie low and let the community troubleshoot this. If it looks like no one can help point you in the right direction, I'll jump in later.
[Kindle Fire Android Development] VaksenDK:
Fair enough, if you ask me. You have already done such a huge amount of work for the KF and performed so many miracles, that I think you should be granted a little breather. :)
[Kindle Fire Android Development] Krunk_Kracker:
This rom is great, except for the sleep of death that hit's it almost nightly. Has anyone figured out a way to prevent it from having a sleep of death? It's on RC1.
[Kindle Fire Android Development] mstrpeter:
No worries at all, I'm working around it... usually leave it plugged in while i'm at work and then use it in the evenings, so it's not a huge functionality issue, I, along with everyone one else am hugely appreciative of all the work you and the community does... I can't understand how you find the time to do any of it honestly.

sounds like you're describing the same thing as me :)
[Kindle Fire Android Development] Hashcode:
So, I actually JUST had the sleep of death happen to me. And was able to get a kmsg log after long pressing the power button, and then VERY quickly hitting it again to reboot (more than a few 1/10ths of a second and memory will be cleared).

Scanning back through my log, I see all sorts of possible suspend/resume issues which clearly could be the culprit:

[ 2246.649139] pm_op(): i2c_device_pm_suspend+0x0/0x7c returns -121

[ 2246.649169] PM: Device 4-0048 failed to suspend: error -121

[ 2254.350250] hub 1-0:1.0: activate --> -22

[ 2262.286926] pm_op(): platform_pm_suspend+0x0/0x64 returns -16

[ 2262.286987] PM: Device alarm failed to suspend: error -16

And then this particularly nasty log item:

[ 2492.920349] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00

^^ That one is NEVER ever good.

So I'm going to research of these and compare to my latest commits.

For reference:

1. I2C 4-0048 == TMP105 temperature sensor

2. Device alarm is normally an Android OS issue where something is setting the alarm over and over
[Kindle Fire Android Development] tobiascuypers:
I remember getting an error like that a while back for a completely unrelated device.

Just a guess here, do you think this one is because of a memory issue? No specific kind, just a general memory problem?

I have never had a SOD while running Official or the cherry pick rom, and I always free up ram, and have next to nothing on internal storage.
[Kindle Fire Android Development] mstrpeter:
very interesting...

what really struck me as odd... mechanically didn't understand, is that it appears to flash drain the battery...
[Kindle Fire Android Development] Krunk_Kracker:
Yep, I would have it charge over night, and if it would SoD, it would have at most 10%

Since it's my fiancee device, I put her on a modded stock room until this gets figured out.

Sent from my RAZR MAXX
[Kindle Fire Android Development] Hyperiunn:
Came to the forums and found this ROM listing that there's a new audio driver and I instantly thought, great someone finally figured out the fix for jelly beans audio lag - awesome. Unfortunately, it seems it's still not being fixed and I'm going to assume that instead mic capabilities have taken a priority over such a HUGE issue. I just don't understad how that gets a priority first over the fact that this lag not only breaks the ROM but just causes unneeded frustration as well. I can't even imagine how annoying it'll be when using a mic as well. If that doesn't we'll that's good, but what if you're using a headset and would like to listen back?

You would think that one of the most annoying problems would be fixed by now rather than being overlooked and wholly not talked about. Or when it is, it's 'oh we know it's a long running issue, there's nothing we can do'. I mean come on, every time I play audio on my device in jellybean I get a 5 sec period of lag EVERY time. I can't play Pandora or a lot of different music apps because the audio driver shuts off while it's buffering the next song so I get a constant loud POP in between songs. Try using noozoxide and you'll understand my frustration. I only use headphones with this devices so it's a bit maddening.

If you look at gederom it works with no lag, so what's the big deal here? And yes, I understand it's running ice cream sandwhich, but really? Could so much of changed between the kernel from then and now that it causes this ROM breaking issue? And yes it's broken for me and anyone else that uses headphones. I dunno I've been waiting half a year for at least something, and it's still rarely being talked about or I'd assume being worked on. And no, I don't have time to learn how to figure all of this out on my own time, I'd probably be better off getting a nexus or something similiar with that time lost. Although one thing I'd love to see is a fully functioning kernel because this one other than that issue is pretty great. And you know, I really love this little tablet, it gets the job done mainly for everything I need... except for sound.

Is the problem really this elusive though? I'm really curious about that.
[Kindle Fire Android Development] rbeavers:
If honey catches audio, your post gets you what?
[Kindle Fire Android Development] ghost_og:
It's not that you don't have a legitimate issue, but there are more tactful ways to bring it up that don't involve you coming off as demanding and entitled (Sorry, but you do). I'm sure that wasn't your intent, but when you say things like "I've been waitng" and "I don't have time to learn" it conveys a lack consideration for those who do such wonderful things for our KF's.

This is a development forum. Posting logs along with a description of the problem you're having goes a long way in helping devs squash bugs. Seeing as how you don't have the technical know how to figure it out on your own, questioning the prioritization of those who do is not constructive or helpful. Hashcode doesn't strike me as the type of person to just ignore stuff or overlook it, but I'm sure certain items can get lost in the shuffle when working on multiple devices. This is why providing quality feedback (i.e. logs) is so critical; trying to recreate the exact issue someone is describing can be just as time consuming as it is to fix it. So in the future, please do your best to help them help you.
[Kindle Fire Android Development] goldflame09:
bud, first of all you post is very demanding indeed and you dont need to be letting out all your rage. there is a nice way to ask about this, which you did NOT do. thanks for your consideration.

second. i personally can use apollo with headphones and i get NONE of the problems that you are describing. i wont say that no one among us hast has these problems, but that was just rude.

if you want to get a nexus, go for it. there is NO ONE here to stop you from doing so. the LEAST that you could have done, is to appreciate all the time and effort that it takes to do such a thing such as this.

if this gives you no trouble on ICS, stay on it. no one here is forcing you to use JB.

no as for solving you problem, i personally think that kernel logs (dmesg) might be better than just logcats. please provide more information that just getting mad and demanding that this needs to be fixed. nothing here NEEDS to be done. this entire website is based off of people WANTING to do these things. they can stop anytime they want to.

P.S. just and fyi for the next time you post. try to do it in a nicer way and also, maybe search before posting

also a note to everyone else, lets not start a fight on this thread. not worth it
[Kindle Fire Android Development] Hyperiunn:
I aplologize if I sounded demanding yet, I'm very passionate about this and possibly passionate enough to setup an environment myself to debug this.

Honestly, I just wanted to create a dialogue about this rather than the usual reaponse which usually is 'this has been talked about use the search function'. This is a development forum and yes I'm familiar with Android in many respects and I really am curious what the issue is with this problem which has caused it to be curtailed for so long. When I said, I didn't have the time to learn everything it really meant dissecting everything that hashcode has done and figuring out what needs to happen to fix this. I may or may not take this challenge up, but I was hoping during the last year and a half my frustration with only using headphones with this device would of subsided eventually. If I had decided to stay quiet as I have, someone else would've taken my place and done so. Who knows maybe they would've had tact as well. ;)

Let me finish this by saying that I respect the work that hashcode has done so far with the Kindle Fire and that again I was only trying to get the gears grinding around this issue. I'd love to hear a technical response as well, as that is what this forum is for correct?
[Kindle Fire Android Development] goldflame09:
apology accepted by me at least.

the best thing at this point you could do it to probably look through system logs and kernel logs to see if you can find anything out of the ordinary. also keep in mind that hashcode is working on a 3.4 kernel. this may or may not resolve your issue when it is fixed and ready for daily use
[Kindle Fire Android Development] Hyperiunn:
As far as I know from what dmesg has told me from the terminal prompt, a codec 'mutes' itself whenever there is no sound and 'unmutes' itself when there is. Maybe it's a simple as having the codec always being 'unmuted' and always ready for sound to be outputted? That's all I've looked into thus far, but I highly doubt it'd be that easy.

That's probably way off base though since Android probably uses many codecs for different apps I'd assume.
[Kindle Fire Android Development] goldflame09:
the only problem that i can see from doing that is that the speakers would be on all the time causing battery life to drain.

since i dont have the problem, when i have time, ill look and see what my dmesg says
[Kindle Fire Android Development] Hyperiunn:
Makes sense, I hadn't thought of that. I'll look further into this but it could be that the audio driver had to be recreated for jellybean and if that's it, this could be quite a challenging task. I think a first place to look would be to find out what ice cream sandwhich does differently and how it handles sound events whenever you're plugged in as opposed to jellybean. Anyways I'll leave it at that for now, hopefully hashcode has time to look at this.
[Kindle Fire Android Development] Hashcode:
I understand your frustration. However, I don't use headphones on the KFire, so I don't see this bug in action. And while this does get mentioned every now and then, it hasn't come up lately and probably fell off my "todo" list.

The issue: there is a timing bug where the headset isn't powered on and/or routing to the speakers hasn't been shut off correctly. This came about when I tried to migrate in some of the audio changes from the 3.0 Kindle Fire 2 kernel that Amazon released. I was hoping to fix the MIC. As it turns out, the new driver is very different from our driver provided by Texas Instruments. I ended up breaking more than I fixed.

I took the time to locate my changes in the sound driver:

https://github.com/KFire-Android/ke...ec7c1bbf543c3bc84aa6c97f49b6354added347#sound

I'll see if I can revert that change and restore normal headset operation.
[Kindle Fire Android Development] Hashcode:
I tested this build w/ 2 of my sound changes reverted out and it seemed to play normally. Can you test it as well?

http://goo.im/devs/Hashcode/otter/cm10.1/cm-10.1-20130524-UNOFFICIAL-otter.zip

Make sure to flash gapps again:

http://goo.im/gapps/gapps-jb-20130301-signed.zip

If this is a good fix for the audio issues via headset then I'll push it into the nightlies.