yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] paxChristos:
Thread Reopened. Keep it on topic.

Pax

FSM Amazon Kindle Fire
[Kindle Fire Android Development] BrooksBlood:
Just had a bug with the power off feature. It rebooted the kindle altogether. I'm at dinner so Ill post a log later so you can scan through it
[Kindle Fire Android Development] yangtsesu:
NO usb mass storage when I plug my kindle fire to my archlinux.

adb works well.
[Kindle Fire Android Development] piotr.pot:
TO ENABLE MASS STORAGE GO TO:

"Settings -> Storage" and then click on the 3 dot "menu" icon in the upper right.

Choose the only option "USB computer connection"

Checkmark "Mass Storage"
[Kindle Fire Android Development] gruuvin:
There has been a bit of wondering if it would be possible at the kernel level to fix an issue that has stood in the way for some apps to access the mic input. One speculation is that full duplex audio is not enabled with the stock kindle kernel/audio driver. This was speculated because of possible evidence that only applications that would not simultaneously stream audio output will enable audio input stream (mic). Voice recorder and Grooveshark accept an input stream while Skype, Groove IP w/Google Voice do not.

Here is a thread discussing it a bit: http://xdaforums.com/showthread.php?t=1652311

Groove IP with Google Voice and synced Google Contacts makes for a really nice "phone" on the Kindle Fire. With a mic/headphone combo plugged in, you can call up anybody in your contact list, and you can hear them, but sadly they can not hear you :( Man it would be awesome if this could be fixed in the kernel!!

I did a quick search on audio full-duplex support for android and found a TI-Android-ICS-PortingGuide wiki (http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide) that mentioned in the "Audio" section support for simultaneous playback and record (full-duplex mode) for an AM335xevm that uses AIC31 audio codec. I believe our kindles use the AIC3110 audio chip, so maybe this is good news.

http://processors.wiki.ti.com/index.php/UserGuideAudioDriver_PSP_04.02.00.07

http://processors.wiki.ti.com/index.php/AM335x_Audio_Driver%27s_Guide
[Kindle Fire Android Development] Hashcode:
Thank you! I'll bookmark this post and read through the info as soon as the charger driver is in better shape. This is next on "the list"(tm).
[Kindle Fire Android Development] AluminumHaste:
The 3 dot icon is not there but thanks for trying anyways.
[Kindle Fire Android Development] Techlyfe:
I believe the three dots will only be there if there is a valid usb connection, that happened with my wifes kindle when she was at work complaining about not being able to hook it to her pc. She swore the three dots were not there. And then she realized, the kindle wasn't even hooked up to the pc, it was connected to the OEM charger... Check the Cable, then, check the drivers.
[Kindle Fire Android Development] lovejoy777:
the three dots were not on any aokp rom when I last tried them, only cm9 roms seem to have the dots.
[Kindle Fire Android Development] sthomas38:
I've built a fully vanilla kang today including the latest source changes. If Hash allows me to, I can post it here :).
[Kindle Fire Android Development] southbird:
Wouldn't put it -HERE- since this is the dev thead for the KERNEL ... would it make more sense to have a Kang / 3.0 thread? At the very least, probably the user alternate thread.
[Kindle Fire Android Development] sthomas38:
Yes you're right but this is also a ROM thread :D...

But okay, I'll create a thread.
[Kindle Fire Android Development] BrooksBlood:
Actually its the kernel development thread. Read the title.
[Kindle Fire Android Development] AluminumHaste:
Nope still not there, tried on 2 kindles. However, both these kindles are running ReloadedROM latest + 3.0 kernel 10a
[Kindle Fire Android Development] YaKillaCJ:
Thanx Hashcode. Kernel is great. Few more things left will makes our device a example of what Ice Cream Sandwhich should be. After the charging issue. I believe tackling the audio is kool.

Not that its my place but I request that the audio driver itself gets fixed b4 the Voip. I mean as U described yourself, the audio drivers are janky. DSP manager doesnt work and thats my only pet peave messing with my ICS experience.
[Kindle Fire Android Development] AlexDeGruven:
The dots are the menu trigger. This is not kernel level stuff, so any behavior like this on a ROM other than that posted in this thread is irrelevant .

If the menus are not available, take it up with the appropriate ROM thread.
[Kindle Fire Android Development] AluminumHaste:
Strange, the discussion had led me to believe that USB connectivity wasn't working because of this kernel, not because of the rom, but I see what you are saying, the 3 dots should be there because that's part of the ROM.
[Kindle Fire Android Development] kernelsandirs:
Battery Life - Governors?

So what is the best governor to use to get good battery life, I seem to get fairly less battery life once I flipped the switch and moved to to the AOKP with kernel 3.0 #10a.

Battery life is not horrific or anything but just wondering how others are best managing their battery, with governors etc?

I am at 1008Mhz and "On Demand"
[Kindle Fire Android Development] Nightly Suicide:
ONDEMAND

Min 300 MHz

Max 1200 MHz

I have pretty good battery life. Even the deep sleep does well. I use Apex Lanucher so I don't really need a high min.
[Kindle Fire Android Development] koroshbhasabrain:
Random Bug Rant....

Hey guys! Hash, with your newest ROM and kernel, I noticed these bugs (these are probably known by now...

1: Random reboot (obviously)

2: Sometimes everything goes extremely jerky and nothing responds

3: The "Battery" tab in the settings shows 'Charging' when it's plugged in, but the battery icon shows nothing (also well known)

I'm happy to lend a hand in any way, just tell me what I should do.

PS: I might sound like a total noob, but what do the governor settings mean and do in the overclock tab? Thanks!!
[Kindle Fire Android Development] Nightly Suicide:
1 & 2 has never happen to me with gedeROM. 3 is fine, just minor GUI stuff...
[Kindle Fire Android Development] phufford:
I've had no reboots ever. I've run into particular programs that are jerky and slow, but usually it's because they're misbehaving (Facebook, looking at you). The battery thing is well known and top of the fixes list.
[Kindle Fire Android Development] ammubarak:
I have been using the latest Hahcode's CM9 four the last ten days with no random reboot or a lack of response due to either kernel or ROM.

To optimize the autonomy of the battery, I have changed the screen brightness to approximately 33% and configured the CPU performance to 800 MHz and 1008 MHz on demand.
[Kindle Fire Android Development] lovejoy777:
no reboots or lag here either. did you do a clean install or did you restore old data etc?

iv'e been running hashes full setup for a couple of weeks and it has been silky smooth.:-)

edit. if im not mistaken, lowering the screen brightness doesn't help battery as the back light is on or off, i think the back light is dimmed by a layer, not by dropping the brightness of the back light. (in other words altering the brightness still means that the back light is on full).

if this info is incorrect please post amendments.

thanks

steve
[Kindle Fire Android Development] Dasanko:
Since nobody answered this, have a read here, as they are well explained: http://xdaforums.com/showpost.php?p=24006181&postcount=3
[Kindle Fire Android Development] Entropy512:
Same here. No reboots.

I use conservative along with a screen-off profile in SetCPU. I forget what frequency limit I set on my Fire - 600 I think? (600 min when screen is on, max when screen off.)
[Kindle Fire Android Development] kernelsandirs:
I am pretty sure it actually adjusts the backlight brightness, a layer would really mess up contrast.

If you install "Screen Filter" from the play store you will see what using a layer for dimming looks like, it's pretty bad.

Lowering brightness should help with battery.
[Kindle Fire Android Development] lovejoy777:
thanks for the clarification i think i remember now, it was mentioned when the screen brightness was at full in early release of hashes kernel and people (myself included) were using the screen filter app. sorry for posting incorrect advice and thanks again for putting me right.

Steve
[Kindle Fire Android Development] BrooksBlood:
Actually had a random boot up in the middle of my final for Stochiometry class lol luckily my professor has a kindle as well with this rom installed so he knew what I was talking about when I told him I swear it turned on by itself :-P He said if I didn't have this rom on here he would've had to invalidate my final for cheating but he understands because his kindle does the same thing with this rom. I'll do some investigating once I get home.
[Kindle Fire Android Development] :
Wow you are so lucky lol
[Kindle Fire Android Development] btonetbone:
Pfft. "Stochiemtry" isn't even a real word. Nice try!
[Kindle Fire Android Development] Dasanko:
He wrote "Stochiometry", not "Stochiemtry", and that was a typo. He meant Stoichiometry: http://en.wikipedia.org/wiki/Stoichiometry
[Kindle Fire Android Development] duke69111:
Rebooting

I was not getting the rebooting before I updated.

I updated the AOKP Build 36 rom by 0xD34D a couple of days ago that I think includes the kernel version #10. When I install it this way, I get the reboots after powering down.

If I install just the kernel version #10 on top of the same rom and then wipe dalvic cache, i no longer get the reboots after powering down.

I included a copy of the logcat from right after the restart from the AOKP Build 36 rom by 0xD34D that included the kernel in the update.
[Kindle Fire Android Development] ratchetandclankf:
I have noticed the following that might be helpful. The OS does detect charging. There must be a problem reporting it to anything beyond the settings app. Could our problem be the ROM and not the kernel? I am running the latest version, btw. Love it.
[Kindle Fire Android Development] veeman:
It's "Stoichiometry" and it's used in Chemistry to predict reactions between different compounds.

---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------

Your signature is super creepy. It's telling me my IP address and ISP and OS and Browser. :/

---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------

Why did you have your Kindle with you while you were taking a final?
[Kindle Fire Android Development] shahabk818:
I want to install this Rom on someone's kindle, I just wanted to know when does the charging detector issue will be fixed? I mean I'm ok with current charging but it's hard for her.

how long you think it takes?:confused:
[Kindle Fire Android Development] duke69111:
Check the first post, its noted along with some suggestions for best charging your kindle.
[Kindle Fire Android Development] BrooksBlood:
I had it so I could use it to read after. Had it sitting on the table and BAM! The boot animation came up haha. And yes it is Stoichiometry :-) I did a typo. Next final is mechanical engineering (going for my masters in this, trying to become an internal combustion engineer hints why I'm taking stoichiometry- a class covering the combination of compounds and how to determine there reactants) :-P don't think I'll be bringing the kindle to this one! Anyways sorry for the off topic posts, back to development.
[Kindle Fire Android Development] southbird:
General rule is you don't ever ask for ETAs here. It gets done when the purely volunteer developer finds enough spare time in their presumably busy lives to do it. Stay tuned to the thread and whenever that kernel version/date upticks, see what's happened. If you got the feature you wanted, horray. You can try donating to Hashcode to see if it'll grease the gears, but that's about it. (You should do that anyway!)
[Kindle Fire Android Development] Alessioromatm:
probably your kernel is the cause of auto startup on KF,both turning off by menù and turning off by holding down the button,sometimes the tablet is turn on by itself
[Kindle Fire Android Development] ratchetandclankf:
What I mean is Systemui doesn't display it. Settings does. I already have acknowledged that charging does work.
[Kindle Fire Android Development] thedeveloper1:
It shows on here
[Kindle Fire Android Development] Hashcode:
Hi Guys,

I know I've been a bit quiet lately, and I wanted to talk about what I'm working on with some of the latest kernel commits:

- I probably have the random reboot fixed; I'll do a new kernel patch soon (tm).

- Had a request to add utf8 (international) support for filesystem (filenames etc) so you can see the nls_utf8 module was added for those that need it.

- I've been trying to work out VPN support as well. And so far only L2TP seems to be working. PPTP is being resistant via the Android interface.

- Continuing work on charger which is not committed into the main kernel source.
[Kindle Fire Android Development] AluminumHaste:
That's good to hear thanks for the update
[Kindle Fire Android Development] shahabk818:
the biggest problem I have with this kernel is battery life, I take the kindle to work or college won't work more than 3 hours. lose more than %25 overnight I had almost 10 hours with stock and even more with cm7

what causes that? is this from kernel?
[Kindle Fire Android Development] intersectRaven:
Yeah, that has no video yet...just for isolating the problem. Seems your Fire has an LG panel...interesting...I'll fix something in a bit. :)

*btw, hashcode, I still can't get WiFi to work...I used the ics-mr1 branch in both wifi and proprietary and uploaded all wl127x firmwares...is there anything I'm missing?

**New kernel uploaded with your display vendor. Hopefully you'll get a video flicker. :p
[Kindle Fire Android Development] Hashcode:
Im going to try a build with the backlight hard coded and see if thats a better test ROM.
[Kindle Fire Android Development] intersectRaven:
If you want, here's my patch:

http://pastebin.com/U4eU1Dzm

I really need help getting WiFi up so I can test full time. It's really bothersome. :)

*Btw, a good side-effect of the patch is it doesn't flicker anymore during off and on transitions. Bad side-effect is brightness adjustment won't work EVER with that in. :p

**mlpmail: new kernel same location if you haven't read my previous post. ;)
[Kindle Fire Android Development] mlpmail:
That change gives me video. so apparently there 2 panels in kindles can someone fix the kernel to support both?
[Kindle Fire Android Development] intersectRaven:
I think there's already a plan for that. Part of the necessary change is already there just commented in hashcode's kernel. :)
[Kindle Fire Android Development] death2all110:
Well I made a couple changes to the kernel for my personal testing and so the provided ones no longer work. my KLIB and KLIB_BUILD are both set to the kernel dir which for me is ~/android/development/threepointoh i used the tilde here for shortening, i use the full /home/myusernamehere/... in the actual paths. is this not correct?
[Kindle Fire Android Development] intersectRaven:
It should be fine. You just set those two variables to where your kernel was compiled and just do a make ARCH=arm CROSS_COMPILE=<compiler path> and it should go fine. My only problem was getting the firmware to load which I'm still waiting for hashcode to reply to. Did you modify the pm_runtime in your modifications? This would be the only thing I would know of that could prevent your compilation from finishing. :confused:
[Kindle Fire Android Development] death2all110:
nope. i didnt
[Kindle Fire Android Development] intersectRaven:
That's odd...you are issuing the make command in the mac80211/compat directory aren't you? :confused:
[Kindle Fire Android Development] death2all110:
still does it. this is exactly what i did:

blake@darkxshadows:~/android/development/wlan/mac80211/compat$ export ARCH=arm
blake@darkxshadows:~/android/development/wlan/mac80211/compat$ export CROSS_COMPILE=arm-none-linux-gnueabi-
blake@darkxshadows:~/android/development/wlan/mac80211/compat$ export PATH=$PATH:/home/blake/arm-2010q1/bin/
blake@darkxshadows:~/android/development/wlan/mac80211/compat$ export KLIB=/home/blake/android/development/3.0kernel/
blake@darkxshadows:~/android/development/wlan/mac80211/compat$ export KLIB_BUILD=/home/blake/android/development/3.0kernel/
blake@darkxshadows:~/android/development/wlan/mac80211/compat$ make clean
blake@darkxshadows:~/android/development/wlan/mac80211/compat$ make

And the results:

blake@darkxshadows:~/android/development/wlan/mac80211/compat$ make
./scripts/gen-compat-autoconf.sh config.mk > include/linux/compat_autoconf.h
make -C /home/blake/android/development/3.0kernel/ M=/home/blake/android/development/wlan/mac80211/compat modules
make[1]: Entering directory `/home/blake/android/development/3.0kernel'
....
/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless/wl12xx/sdio.c: In function 'wl1271_sdio_power_on':
/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless/wl12xx/sdio.c:181: error: implicit declaration of function 'pm_runtime_enabled'
/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless/wl12xx/sdio.c: In function 'wl1271_resume':
/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless/wl12xx/sdio.c:384: warning: unused variable 'wl'
make[4]: *** [/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless/wl12xx/sdio.o] Error 1
make[3]: *** [/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless/wl12xx] Error 2
make[2]: *** [/home/blake/android/development/wlan/mac80211/compat/drivers/net/wireless] Error 2
make[1]: *** [_module_/home/blake/android/development/wlan/mac80211/compat] Error 2
make[1]: Leaving directory `/home/blake/android/development/3.0kernel'
make: *** [modules] Error 2
[Kindle Fire Android Development] intersectRaven:
Can you give me the outputs of these commands from your KERNEL directory:

grep pm_runtime_enabled include -r

grep PM_RUNTIME .config
[Kindle Fire Android Development] death2all110:
here you are:

blake@darkxshadows:~/android/development/3.0kernel$ grep pm_runtime_enable include -r
include/linux/pm_runtime.h:extern void pm_runtime_enable(struct device *dev);
include/linux/pm_runtime.h:static inline void pm_runtime_enable(struct device *dev) {}
blake@darkxshadows:~/android/development/3.0kernel$ grep PM_RUNTIME .config
CONFIG_PM_RUNTIME=y
blake@darkxshadows:~/android/development/3.0kernel$
[Kindle Fire Android Development] intersectRaven:
Hmmm...last question...did you build the kernel with the otter_android_defconfig? It may be that a configuration there was necessary for the WiFi build. :confused:
[Kindle Fire Android Development] death2all110:
yes i did, i just changed the version name in that. surely that shouldn't have any effect?
[Kindle Fire Android Development] Hashcode:
iR- for the wifi module build, I double checked my branches for compiling the wifi modules and I was mistaken:

For hardware/ti/wlan use branch: ics-mr1 and follow the posted directions

The firmware in the build came from device/ti/proprietary branch: ics-mr0 under wl12xx/wlan/* these are the files that end up in the build under /system/etc/firmware/ti-connectivity
[Kindle Fire Android Development] Hashcode:
FYI: changing the version name will break all of the prebuilt modules in the ROM.
[Kindle Fire Android Development] death2all110:
Well I decided to clone his source again. Just in case..
[Kindle Fire Android Development] Hashcode:
To make sure TI didn't update something which is breaking the wifi modules, I'm going to recompile then against the latest sources and firmware. I'll post an update here in a bit as to which branches, etc.
[Kindle Fire Android Development] death2all110:
Alright. Thanks. So for the wifi modules which should I be using? ics-mr1 or ics-mr0?
[Kindle Fire Android Development] intersectRaven:
Thanks for that. I can't imagine having to switch my Fire to different kernels every now and then. ;) Anyways, I'll be helping in debugging this thing and solving anything. Btw, if you need the patch for the alternate display panel thing, I can post is as a diff again at pastebin. :)
[Kindle Fire Android Development] jmcoffey:
Choose a differenet cpu governor.
[Kindle Fire Android Development] shahabk818:
it's set on interactive, with one should choose?
[Kindle Fire Android Development] Techrecycler:
Use badass battery monitor in market to rule out any persistent apps first. Then try other governers & clock settings.
[Kindle Fire Android Development] nandroltom:
Can anybody report NOT losing 20% battery overnight with this Kernel? Otherwise I would file this as a bug.
[Kindle Fire Android Development] sthomas38:
Yes me, my battery is fine.

Envoyé depuis mon Amazon Kindle Fire avec Tapatalk
[Kindle Fire Android Development] jmcoffey:
On Demand gives better life for me. Or power saver.
[Kindle Fire Android Development] shahabk818:
its on ondemand, so there are tons of battery saver apps on google play

which ones better in your experience?
[Kindle Fire Android Development] Hashcode:
05-26: KERNEL.ZIP #11 IS NOW READY HERE (FLASH IN RECOVERY): http://bit.ly/KTAgj1

md5sum ba1e0ca296645b631954167b74c07bd5

FULL STOCK CM9 ROM AVAILABLE HERE: http://bit.ly/L3LCgP

md5sum 8b3251b824535f2199eb02adc005b94d

- RANDOM REBOOT FIXED. Needs confirmation and testing.

- PowerVR/SGX update: SGX Driver (1.8@869593) with CPCAM support

- Added nls-utf8.ko (external module) for international filesystem support

- Added a bunch of modules for VPN/PPTP/L2TP support (needs testing)

- USB mode changes/cleanup: Mass Storage / ADB

TROUBLESHOOTING FOR USB not being recognized in Windows 7 (while the Kindle is *NOT* plugged into computer):

- Open Device Manager

- Right-click your computer name and select "Show Hidden Devices"

- The top device group should be: Android device(or phone): under it "Android ADB Composite device"

- Right-click on that and select uninstall

- Now plug the Kindle back into the computer and let driver re-install
[Kindle Fire Android Development] jmcoffey:
I use battery saver pro. It gives me about three more hours than without.
[Kindle Fire Android Development] shahabk818:
installed.

I think hash will increase the battery life in further releases
[Kindle Fire Android Development] Thepooch:
Disregard
[Kindle Fire Android Development] afu1979:
PPTP VPN

I tried the new kernel and tested my PPTP connection to work. It is still unsuccessful and here is the log output.

I/keystore( 125): uid: 1000 action: i -> 1 state: 1 -> 1 retry: 4
I/Vpn ( 171): Switched from [Legacy VPN] to [Legacy VPN]
V/LegacyVpnRunner( 171): Waiting
V/LegacyVpnRunner( 171): Executing
D/mtpd ( 7228): Waiting for control socket
D/mtpd ( 7228): Received 20 arguments
I/mtpd ( 7228): Using protocol pptp
I/mtpd ( 7228): Connecting to *********.*** port 1723 via wlan0
I/mtpd ( 7228): Connection established (socket = 11)
D/mtpd ( 7228): Sending SCCRQ
D/mtpd ( 7228): Received SCCRP -> Sending OCRQ (local = 38913)
I/mtpd ( 7228): Tunnel established
D/mtpd ( 7228): Received OCRQ (remote = 59167)
I/mtpd ( 7228): Session established
I/mtpd ( 7228): Creating PPPoX socket
F/mtpd ( 7228): Socket() Protocol not supported
D/dalvikvm( 4107): GC_CONCURRENT freed 331K, 8% free 7370K/8007K, paused 2ms+3ms

I/LegacyVpnRunner( 171): Aborting
I/LegacyVpnRunner( 171): java.lang.IllegalStateException: mtpd is dead
I/LegacyVpnRunner( 171): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.execute(Vpn.java:569)
I/LegacyVpnRunner( 171): at com.android.server.connectivity.Vpn$LegacyVpn
Runner.run(Vpn.java:447)
D/dalvikvm( 449): GC_CONCURRENT freed 430K, 10% free 6986K/7687K, paused 3ms+2m
[Kindle Fire Android Development] Hashcode:
Yes, the pptp stuff isnt quite working yet. Can you test L2tp or openvpn?
[Kindle Fire Android Development] powerpoint45:
Good job hash.I just flashed your updated boot loader and kernel. Things seem to be smoother and their is no more shutdown issues.