yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] victory144:
Strip line back!.

Apparently the strip line is back, after some days using kernel #12.

anyone else?..
[Kindle Fire Android Development] BluPix:
Sometimes sound is muted without any cause. I must go to settings, change volume and then it's unmuted. In application Magic Piano this mute is really often.
[Kindle Fire Android Development] ProfEngr:
I think this a known issue. Remember it being brought up a few pages back.
[Kindle Fire Android Development] BluPix:
But now we have application Magic Piano where this bug is really often (at least once per "Fur Elise"), so developers can test it on this application.
[Kindle Fire Android Development] ProfEngr:
Ah. n/m then.

Sent from my TBolt with the XDA App using 1 opposable thumb
[Kindle Fire Android Development] spraveen:
In adobe reader as well it is seen when it is zoomed.
[Kindle Fire Android Development] southbird:
You're clearly not talking about the same thing because he was referring to an audio bug, not a visual one. What do you see when zooming in Adobe Reader?
[Kindle Fire Android Development] lovejoy777:
building cm9 from source (trying)

sorry to bother you all.

(slightly off topic).

I'm trying to build my first rom from source.

i followed a guide and managed to build cm9 for my gnex.

i now have tried to do the same for my kindle, but am having problems.

my local manifest is as follows:

<manifest><!-- local projects --><project path="device/amazon/otter" name="KFire-Android/device-amazon-otter" remote="github" revision="ics"/><project path="kernel/amazon/otter" name="KFire-Android/kernel_omap" remote="github" revision="4AI.5"/><project path="vendor/amazon/otter" name="KFire-Android/android_vendor_amazon_otter" remote="github" revision="ics"/></manifest>

im stuck at this as brunch otter returns this:

steve@lovejoyub:~/CM9$ brunch otter
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/otter/cm.mk]]: "device/*/otter/cm.mk" does not exist. Stop.
Device otter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for otter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/otter/cm.mk]]: "device/*/otter/cm.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_otter'
** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'
steve@lovejoyub:~/CM9$

any pointers anyone

have I got the right local_manifest?

thanks in advance

steve
[Kindle Fire Android Development] twa_priv:
Might be a stupid question ... but did you do a repo sync after putting the local_manifest.xml in .repo?
[Kindle Fire Android Development] lovejoy777:
yes did repo sync and all went well.

then cd into my work folder ie. CM9.

then ran ./get-prebuilts

after this i ran the terminal as my 1st post.

if i issue brunch and not otter_brunch i get a list of devices (no otter there)

should i start from the begining?

Edit:

ok i think i found it.

in my working folder i have "local_manifest" inside this is the the otter manifest.

but i also have "local_manifest" in repo and this has the samsung manifest inside.

(can i just change this inside repo manifest to the otter one then do repo sync again?

I did make clobber before starting with kindle.

when i do afresh what do i need to do to start from a blank slate?

and is there a way to just update the repo and not redownload everything again?
[Kindle Fire Android Development] twa_priv:
Does your device/amazon/otter directory exist? If not then something went wrong with the sync.
[Kindle Fire Android Development] lovejoy777:
no. redoing sync now.

sorry for the noobishness.

do i have to start with a new working directory or can i issue make clobber to clear it

thanks again

steve
[Kindle Fire Android Development] sthomas38:
I'm personnaly trying to build on an external hard drive since my internal is near full, but as of now it's not a real success :D.

fatal: unable to start /media/Stockage/source/.repo/repo/main.py
fatal: [Errno 13] Permission denied

If think there's something wrong in my fstab as Google told me :p.

I'll take another look at it in two weeks, now I'm leaving to England for the holidays :D.
[Kindle Fire Android Development] southbird:
External drives are typically factory-formatted to FAT32 or NTFS to be Windows compatible. This however is NOT Unix-permission compatible. If you are running it as an ext2/3/4 drive, it's some other permission problem.
[Kindle Fire Android Development] sthomas38:
Right, it's an NTFS formated one. Thanks for the quick answer :).
[Kindle Fire Android Development] lovejoy777:
I'm going to do a little more reading.

thanks for your help twa_priv:-)

Hash any progress on bricked kindle or have you binned it. mines in storage (maybe longterm:-(.)
[Kindle Fire Android Development] miro101:
i'm on gede rom with latest kernel and the striping/light artifacts are back,

somebody else haviing this issue ?
[Kindle Fire Android Development] :
Great job on kernel hash seriously since this my kindle has turned into an everyday use device. I am curious though as to why USB fast charge has not yet been implemented? I still use a DINC and Chad's/tinys kernel has it and honestly that's my number one reason besides many others to use their kernels over others. The kindle takes forever to charge and was just wondering if the community could come together to make this happen. I'd happily donate or test or provide any knowledge and working hours to make it so. Thank you for your time.

Martin
[Kindle Fire Android Development] southbird:
I don't think a lot of others here use Gede. I guess first try flashing Hash's latest kernel in the OP.

If that makes no difference, wipe everything except SD card, go back to CM9 using this: http://rombot.droidhive.com/ROMs/otter/cm9/cm9-kfire-3.0-hashcode-05-26.zip ... and then flash Hash's latest kernel in the OP. If your issues go away, you know that Gede is including a somehow incompatible kernel. Which is what I'd strongly believe is the case since the "striping" issues have been gone for most of us for at least a month now.

It's up to Hash, but primary Hash is not too interested in "nice to haves." It's more about getting core Kindle Fire functionality to work first. That means don't expect things like this until after the charger driver and USB transfer speed has been fixed.
[Kindle Fire Android Development] Hashcode:
I just wanted to do a quick update:

Got my new device yesterday, and immediately put twrp, fff 1.4a and ICS on it.

Should be good to pick up where I left off w/ the kernel now.

Hope to have a new version in a few days.
[Kindle Fire Android Development] e495957:
Hashcode this is great news! I'm so glad.

What do you think the chances are of going on CM's official site, github and nightly release schedule at www.get.cm? You think it will be soon? I'm already using this as my daily driver...
[Kindle Fire Android Development] sthomas38:
CM team is quite strict about official support. I think our CM is too buggy for the moment :).

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] Thief777:
I would also like to see him in the CM project, it has all the chances. It is easier, no need to mess around with the phone part of the device.

I also use on a daily basis, but the problem with charging (...
[Kindle Fire Android Development] webdroidmt:
Sorry Trojan, I have to disagree with you on that. :laugh: I also have a Touchpad running CM9 nightlies and the CM team has made great strides with it. They managed to get HWA working quite well with the "old" 2.6 kernel for Netflix, Youtube HD etc. and just recently got our mic working. Having that kind of a team effort working on your device is awesome. However, the TP's CM9 is still basically beta and has it's share of bugs/quirks similar to those with the KF.

Since I have both devices and love 'em both, I can be objective and IMO, the KF in it's current state does just as well, if not better than the TP in general functionality on CM9/ICS. Hashcode's work on the 3.0 kernel and FFF1.4a has been outstanding and he got HWA working far sooner than I ever thought possible for this device.

I believe a lot of getting official CM9 support comes down to circumstance. One important circumstance being, which CM team dev(s) owns or takes an interest in the KF. So, if the TP can have official CM support, why not the KF?

The End :D:

Mike T
[Kindle Fire Android Development] lovejoy777:
hash glad to hear you got your new one

what chip?

has your source got the volume slider in?

thanks again

steve
[Kindle Fire Android Development] dnd61:
Hopefully the charger driver is working fine :good:
[Kindle Fire Android Development] sthomas38:
You're right, but I think the Touchpad is a special case. You know, HP themselves really "engaged" (omg my English stops here :D) some CM devs to get Android working on this device, unlike all other devices :).

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] veeman:
*bribed

Sent from a thingymajig that sends things.
[Kindle Fire Android Development] intersectRaven:
For WiFi modules, ics-mr1. For firmware ics-mr0. :)
[Kindle Fire Android Development] Hashcode:
iR: Posting your patch to the kernel repo for now so that we can test other parts of the kernel.

Thanks :)
[Kindle Fire Android Development] Hashcode:
Also for troubleshooting of the modules use this patch:

diff --git a/mac80211/compat/drivers/net/wireless/wl12xx/main.c b/mac80211/compat/drivers/net/wireless/wl12xx/main.c
index 0dfd493..39a709f 100644
--- a/mac80211/compat/drivers/net/wireless/wl12xx/main.c
+++ b/mac80211/compat/drivers/net/wireless/wl12xx/main.c
@@ -1086,12 +1086,12 @@ static int wl12xx_fetch_firmware(struct wl1271 *wl, bool plt)
fw_name = WL1271_FW_NAME;
}

- wl1271_debug(DEBUG_BOOT, "booting firmware %s", fw_name);
+ pr_info("booting firmware %s\n", fw_name);

ret = request_firmware(&fw, fw_name, wl1271_wl_to_dev(wl));

if (ret < 0) {
- wl1271_error("could not get firmware: %d", ret);
+ wl1271_error("could not get firmware(%s): %d", fw_name, ret);
return ret;
}
[Kindle Fire Android Development] death2all110:
got them to build. must of been something in my kernel source.
[Kindle Fire Android Development] Hashcode:
I've just compiled the p-ics-mr1-release branch of hardware/ti/wlan which uses the firmware from device/ti/proprietary-open branch ics-mr1

All of which is the latest available source.

Waiting for the new ROM to build, and then I'll update the device/amazon/otter git with all of the prebuilt modules / firmware and the kernel w/ the backlight hardcoded to max.
[Kindle Fire Android Development] intersectRaven:
Tried those branches and my WiFi still won't connect. It just stays at the

ADDRCONF(NETDEV_UP): wlan0: link is not ready

output. :(
[Kindle Fire Android Development] Hashcode:
Do you have a kmsg handy?
[Kindle Fire Android Development] intersectRaven:
Ignore that...I saw a WiFi commit you entered 2 days ago and resynced my kernel source with yours. Works now so I can move on to other things. Thanks! :)\

*Btw, here's a patch for the alternate display panel Kindle Fire I debugged a while ago:

http://pastebin.com/X55qR6VS

I think we should restore all the previous initialization styles in there since it seems possible that Amazon may have used more than 1 panel manufacturer. :)
[Kindle Fire Android Development] mlpmail:
Seeing as how now have working wifi can you post a new compiled img that I can use?

Thanks
[Kindle Fire Android Development] intersectRaven:
That's tricky seeing as you also need to have new firmware images. Let's just wait for hashcode to release a new one with the necessary changes so you can get everything working nicely. :)

*on the other hand, I think he hasn't included the display changes for your model...hmm...I'll see what I can do... :)
[Kindle Fire Android Development] Hashcode:
I can't believe I removed this code from the panel driver. I was debugging some things and left this part out.

Adding back the entire check from the stock ROM.
[Kindle Fire Android Development] intersectRaven:
Upload just finished...same location as before. Notify me if WiFi doesn't work. I'm still not sure if it'll replace the files you see. :D

*Here's the MD5 sum of the file since it's a bit bigger than I'm comfortable with. :)

85cc3312bb85db0ca3877f9f7a4338dd
[Kindle Fire Android Development] Hashcode:
Test Build #2 can be found here: http://bit.ly/HN8e4B

Of course I'll update the OP but here's a quick summary of changes:

1. Removed the custom SystemUI changes to CM9. It's completely stock. This should eliminate any sync issues that people were having using the local_manifest.xml file for building the new ROM. If you are building the new ROM on your own, please double check here:

https://github.com/KFire-Android/android_local_manifest/blob/ics-test/local_manifest.xml

And make sure your local_manifest.xml file is up-to-date. (It should only have 1 project now). In short: no easy access brightness / sound bars. We'll re-add that mod back into the ROM when we get farther along.

2. Hardcoded the backlight brightness to max setting. Nothing will change it. The screen does power off on suspend or when you press the power button. And then comes back when you press power button. We'll keep working on the adjustable backlight issue. But for now this allows more people to test the kernel / ROM build. (thanks intersectRaven)

3. Re-added the multi-panel support during initialization. This was removed early on for testing and I never put it back. This change should also allow more people to test the ROM / kernel. (thanks intersectRaven)

4. Updated PVR binaries to 1.8@869593 and moved the kernel modules into the ramdisk so that they load on init.

5. Updated the wifi modules / firmware to mac80211 driver to version R5.00.14

6. Changed the bootanimation to a 960x540 sized version but it's facing the right way.
[Kindle Fire Android Development] mlpmail:
Thanks

I installed the zip over hashcodes original rom using twrp and now I have a working display that surfs the web.
[Kindle Fire Android Development] 50CalPotato:
Hashcode and insectRaven: you two are beautiful sons of *****es.

Oh the 4-10 ROM I was unable to get the display going no matter how hard I tried. I guess that means that I've got a LG panelled Kindle Fire.

After flashing what you just put up, it's working beautifully!

Phenomenal work guys, just phenomenal.
[Kindle Fire Android Development] Hashcode:
It's really 100x better to test with the temp. backlight and panel fixes.
[Kindle Fire Android Development] 50CalPotato:
My problem is that I haven't a clue as to doing anything other than getting into TWRP and flashing a ROM!

So far, everything is going extremely smoothly. I am also not affected by the WiFi bug; it's working perfectly after resuming from sleep.
[Kindle Fire Android Development] Hashcode:
I'd say load Chrome up or whatever else you plan on using normally. And report back w/ bugs.

It's about time I jumped back onto the last few errors getting the Ducati / hw codecs working.
[Kindle Fire Android Development] TexasRules777:
I'm using fff 1.3 and CWM and I just can't get this to load. I've factory reset,wipe cache,dalvik, install zip then gapps...just the fff screen then just a black screen. Even let it sit for 5 mins...? Will installing TWRP help this issue?

Ooops I meant to post in the general section...sorry
[Kindle Fire Android Development] Hashcode:
I believe there is a current issue with CWM. TWRP will probably make it work. Let me know if you try it; how it goes.
[Kindle Fire Android Development] webdroidmt:
Hmm, maybe some HP folks might have wanted this but overall, HP was uncooperative in providing many drivers. In particular, the original wifi drivers were finally provided about a month or so ago. What actually helped the early development of the Touchpad was a leaked android binary image.

But, this is a dev thread for the KF 3.0 kernel, so that's the end of my discussion of the TP. I still believe that the KF dev has come far enough to be considered for the CM "official" tag. Currently, Hashcode's builds are "Unofficial" CM9, hopefully we'll see "Official" in the not too distant future. :fingers-crossed:

My primary reason for wanting this to happen is obvious, more people involved that are capable of making fixes and improvements. Thanks.

Mike T
[Kindle Fire Android Development] twa_priv:
Hey Hash,

Not sure if and when you are planning to do your next full ROM build - but I wanted to let you know that I just cleaned up my frameworks/base repo and basically started over merging in the KF changes. There was some cleanup necessary because CM added notification drawer powerwidget configuration options.

The state of the ics-otter branch now is CM as of today + the following KF changes: volume slider in notification drawer, removed airplane mode from power menu, toggle status bar from power menu.
[Kindle Fire Android Development] Hashcode:
twa_priv: I think it would benefit many devs if we had a frameworks/base kept up-to-date in our repo. Would you mind taking care of that? I can add you to the KFire-Android git members with permissions on a frameworks/base fork.

The key would be to keep it stock CM except for those few UI changes.

Also.. next kernel will have new PVR/SGX update in it:

http://www.omapzoom.org/?p=device/ti/proprietary-open.git;a=commit;h=a5203bf442f19e3ad4e3f52aefc536e97dfb7183

Note:

0d7410c PVR-UM/KM: Support Jellybean build

f269b1f PVR-UM: Make pvrsrvinit wrapper compatible with Jellybean

Yummy.
[Kindle Fire Android Development] lovejoy777:
maybe found a little bug with the new merge?

if you set back button long press to kill app. then inside any directory/app the back button always returns you to the home screen.

(it could be my build as it's one of my 1st's).

thankyou guys it's all coming together :-)

cheers steve

sent from my new non bricked kindle:-)
[Kindle Fire Android Development] twa_priv:
I can't see that any of my changes have an effect on the back button - but you never know. The only way to be soure would be to test this on a real vanilla build (using CM frameworks/base) and see if the behaviour is the same.

---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------

I can do that. And I'm not planning to make any other modifications anyway. Are you fine with leaving my toggle statusbar mod in - otherwise I can take it out/revert it?
[Kindle Fire Android Development] lovejoy777:
just done a fresh install and it was one of my mods. lol

all working super smooth.

for what its worth my new build scored 6144 on benchmark (performance setting)

what does true vanilla mean?
[Kindle Fire Android Development] powerpoint45:
I noticed that your rom links are down but I saw some unofficial ones here:

http://rombot.droidhive.com/ROMs/otter/cm9/

Edit:its back up now
[Kindle Fire Android Development] southbird:
Actually rombot is where he keeps them, so they weren't "unofficial" any more than CM9 on a KF is ever unofficial. :P But they were missing from rombot for a bit for some reason.
[Kindle Fire Android Development] Thief777:
How are things going with the problem of charging display, it's so annoying, would solve the problem?
[Kindle Fire Android Development] twa_priv:
Ok, done. The ics branch of KFire-Android/android_frameworks_base now is up-to-date with the latest CM commits + the additional KF changes.

Anyone who want's to use it please add the following to your local_manifest.xml:

<remove-project name="CyanogenMod/android_frameworks_base" />
<project path="frameworks/base" name="KFire-Android/android_frameworks_base" remote="github" revision="ics" />

@Hashcode - I don't know if you want to update the android_local_manifest repo to include this by default - or if you want to leave the choice to the devs.
[Kindle Fire Android Development] vbdss:
http://www.xda-developers.com/android/full-ntfs-readwrite-support-for-android/

Is this of any use for us?
[Kindle Fire Android Development] ProfEngr:
Sure would be nice. NTFS is defacto for partitions >127gb.

Sent from my TBolt with the XDA App using 1 opposable thumb
[Kindle Fire Android Development] Hashcode:
If that's ok, I'd like to use this for the automated nightlies. And I'll include it in the local_manifest.xml.

The biggest issue is that w/o the right UI mods, ROMs for the Kindle Fire can go from great to really cumbersome. So thanks for keeping this up ;P
[Kindle Fire Android Development] southbird:
This article makes such a big hoot about it, but this is pretty much as easy as flipping a switch in the kernel compile. I'm sure once we get far enough that USB OTG becomes a priority we can have all the practical drivers in the world.
[Kindle Fire Android Development] ProfEngr:
Until then, I'll just stick to <128gb partitions on my usb drive. Now to locate a win98se format.com so I can format above 32gb.
[Kindle Fire Android Development] Hashcode:
Added the unofficial NIGHTLY server info in the OP.

Every night, this build is generated automatically from CM sources using the latest kernel.

NIGHTLY DOWNLOADS
[Kindle Fire Android Development] sthomas38:
Thanks Hashcode. Gonna close my thread then! :D

Was a pleasure to help :).

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] miro101:
Wow am I the only one who has the problem of burnt in images on the latest rom? Or am I expecting to much?

This is happening :

When I'm on a bright screen for some time (sodoku free by genia. Com), 8 minutes, and switch to a dark screen, example : Google Chrome with no tabs, I can still see as a ghost image the sodoku grid.

I am to worried about my Kindle s screen?

Ps. I'm on latest rom with everything wiped, except the battery stats
[Kindle Fire Android Development] aaricchavez:
That's been happening to me, but I replaced my LCD with one of of eBay(This didn't happen to me on the OG one), so if you bought your KF used/refurbished it might have a replaced LCD.
[Kindle Fire Android Development] quick_:
I purchased a refurbished Kindle Fire from amazon, and I've also had the ghosting /burnin,

issue on every 3.0 kernel.

Are u saying this is a hardware defect with refurbished devices?

I had always assumed it was a kernel/software issue...
[Kindle Fire Android Development] aaricchavez:
I didn't have the issue until I put the new screen in(At least I don't remember having the issue). The original one was made by LG, I don't remember the brand of the one I put in, but it wasn't LG.

Now, if it was Amazon themselves that refurbished it, it would be an OEM screen meaning that it very well could be a kernel/rom issue.
[Kindle Fire Android Development] quick_:
Interesting thanks. FWIW, I get the ghosting after only a few seconds of stuff displaying on the screen. I can't believe that these (even refurbished screens) are so poor quality that this would even be possible.

That said even the on screen keyboard from typing this message left ghosting and I can watch it slowly fade out, which would seem to be hardware not software but I'm not expert in screen tech lol...

Sorry for off topic.
[Kindle Fire Android Development] andTab:
Bug in 6/28:

Trying to go into settings results in "unfortunately, com.android.settings has stopped"

Also, the icon is off (green android instead of settings icon)
[Kindle Fire Android Development] twa_priv:
Works fine for me. What ROM did you come from? What did you wipe? .....
[Kindle Fire Android Development] jfb9301:
The ghosting is not limited to just refurb screens. I bought NIB in December, and mine ghosts too. I finally switched over to HC from the JC 3.x with 2.x Kernel about 2 days ago.