yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Segnale007:
Can anyone help me to get ad-hoc network to be seen?

Hello folks. I assume everyone here already knows that ICS doesn't see ad-hoc wifi networks since the IBSS modulation is not enabled in wpa_supplicant.

However looking for a possible way to get around to this, I came across to this thread which led me to this other one where a guy called @wendal put some effort to compile wpa_supplicant with the IBSS modulation included.

Unfortunately though, even though the wpa_supplicant with IBSS modulation compiled is the exact version of wpa_supplicant v0.6.10 used by this ICS rom and it run just fine, it seems that this specific version does't have the right driver to work with the kindle-fire wireless interface.

Correct me if I am wrong.

I/ActivityManager( 1400): No longer want com.android.vending (pid 2307): hidden #16
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1400): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
D/CommandListener( 1296): Setting iface cfg
D/CommandListener( 1296): Trying to bring down tiwlan0
D/CommandListener( 1296): broadcast flag ignored
D/CommandListener( 1296): multicast flag ignored
D/NetworkManagementService( 1400): rsp <213 f0:a2:25:77:b3:22 0.0.0.0 0 [down broadcast multicast]>
D/NetworkManagementService( 1400): flags <[down broadcast multicast]>
E/wpa_supplicant( 2457): Unsupported driver 'tiwlan0'.
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiHW ( 1400): Supplicant not running, cannot connect
E/WifiStateMachine( 1400): Failed to setup control channel, restart supplicant

I know it might not be a priority right now, but I am wondering if anyone here could give a look at the ICS wpa_supplicant tool and patch it to include the IBSS modulation, so that our kindle-fire will be able to see and connect to ad-hoc networks. Most of us here own an android phone which most likely uses ad-hoc tethering, and it would really be a plus one to be able to share our mobile connection with our kindle-fire.

Unfortunately I don't have a linux machine with an android environment set up ready, and I have never really mess with compiling anything for android, so I am not sure how far I would get with this. Though I am willing to betatest if anyone have a spare time to dedicate into this.

Thanks once again and I truly appreciate your work guys :)
[Kindle Fire Android Development] thelonewizard:
I read through the thread and couldn't find it mentioned, but I could be wrong. Either way, I have tried a few different video streaming sites like youtube, and all of them like, fast-forwarded through the video. Also, none of them had sound. I don't know if this was known or not, but I thought I would bring it up.
[Kindle Fire Android Development] revxx14:
Pretty sure this is a known issue.
[Kindle Fire Android Development] DeerSteak:
I learned something new today, thanks! :D
[Kindle Fire Android Development] palmheel:
I figure it out, I used the the option on TWRP to mount and unmount and it worked. Thanks.
[Kindle Fire Android Development] DeerSteak:
That's what I had to do, too. I tried using the app included in the ROM and it says I have no USB connection. Left everything as it was and booted into TWRP and it mounted fine. Something strange, but it might just be me.
[Kindle Fire Android Development] big gulps huh?:
Seriously? Please read the opening post ALL the way through and you wouldn't have to ask that question.....
[Kindle Fire Android Development] shobon:
Ten characters
[Kindle Fire Android Development] michaelkourlas:
An excellent point.

---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------

I have compiled a list of current issues with the Kindle Fire pre-alpha ICS ROM:

- Video: no sound, very choppy (seems to fast forward)

- Sound: flaky, only works once in a while

- Bluetooth: not working

- Orientation change: when going from portrait to landscape and vice-versa, brief graphics problem

- CPU: seems to stay fixed at 1Ghz when WiFi is turned on

Also, when Google Apps are installed:

- Talk: crashes

- Camera: crashes (shouldn't really even be included)

- Setup: offers to use network-provided time, but there's no mobile network chip
[Kindle Fire Android Development] revxx14:
That MAC address fix did nothing for the CPU issue for me. Still stuck at 1008. I know it's not the point, but it was mentioned that it might fix it too.

To the post before this:

Yes, the camera and phone stuff should all be removed (if it's not too difficult, otherwise it doesn't really matter). One of the things that I find pretty funny is that I can crash the OS from the lock screen, by trying to unlock to the camera. Also, I've noticed the rotation thing too. It looks like it flips the image the opposite direction, and stretches it out, but just for a second.

EDIT: So it looks like no matter what, the CPU is stuck at 1008 for me, even if wifi is turned off.
[Kindle Fire Android Development] MMDominator88:
Still @ 1008? clear cache and dalvik, etc

Specific post: http://xdaforums.com/showpost.php?p=20794074&postcount=26

Thread: http://xdaforums.com/showthread.php?t=1406845
[Kindle Fire Android Development] jutley:
Would this help in any way

http://www.engadget.com/2011/12/29/cyanogenmod-compiler-project-allows-android-tweakers-to-easily-m/
[Kindle Fire Android Development] paraniodandroid:
While playing around with the ROM I've noticed that I can only charge the device up to 51%. Looking at the battery status it switches between charging and discharging when it reaches this point indicating that it might be full already.
[Kindle Fire Android Development] bl1nkk:
No. That's what everyone does already.
[Kindle Fire Android Development] jutley:
Ic icecream
[Kindle Fire Android Development] revxx14:
So, I know this is a forked version of this ROM, but this guy says he's got audio working...Is there any chance we can use his fix?

http://xdaforums.com/showthread.php?t=1379208
[Kindle Fire Android Development] FroyoShark:
This should be included in the ROM.
[Kindle Fire Android Development] revxx14:
Tried clearing cache and Dalvik, did nothing. What all is safe to wipe in TWRP?
[Kindle Fire Android Development] Myzur:
I am getting the message "Unfortunately, the process com.android.phone has stopped" when running ICS. I installed "tryforsdcard.zip" from TWRP.

Any suggestions?

EDIT: I did a factory reset wipe in TWRP and that fixed the problem. Hello, ICS!
[Kindle Fire Android Development] revxx14:
Google Music always crashes too. Might be related to the audio issue, but I'm not sure.

Where can I go to learn more about porting stuff? I'd love to be more help with stuff like this, but I only have a bit of experience developing software, and none for Android, so all I can do right now is bug check.
[Kindle Fire Android Development] cccodyyyy:
Here's some screenshots for those who are curious, feel free to add them to the OP.

Lockscreen: http://i.imgur.com/MYUzn.jpg

ICS web browser: http://i.imgur.com/jbNcF.png

New settings UI: http://i.imgur.com/Gzvkf.png

Amazon Kindle Fire on 4.0.3: http://i.imgur.com/Gs6Vn.png

New notification window: http://i.imgur.com/mchLq.png

Youtube: http://i.imgur.com/FbmVP.png
[Kindle Fire Android Development] CodenameDeadpool:
This. It's one of the only things stopping me from using it as a daily ROM, that and XDA premium won't install on it for me, but it will install on the MIUI ICS ROM.
[Kindle Fire Android Development] rukin5197:
First off, I ould recommend posting this in the cm9 building forum, as all of them have their environments set up.

Secondly, I can easily tether my mobile connection from my phone to kindle fire using the built in cm7 wifi tether and/or wireless tether for root users from the market. Of course, I have no knowledge of ad-hoc and quite frankly never heard of it
[Kindle Fire Android Development] CodenameDeadpool:
I use an ad hoc program called Connectify, it lets me use my PC as a wifi hot spot. My PC gets internet via a dsl modem but I have a card with a wifi antenna in my PC that puts out the wifi signal. Sadly I can't connect at home with these CM9/ICS ROMS
[Kindle Fire Android Development] Segnale007:
Unfortunately the rom I use on my x8 has a know bug regarding the built-in wireless tether, which yes uses "infrastructure" and will work with pretty much anything, if u have the luck to have a phone/rom that works with it..
[Kindle Fire Android Development] jdommer:
I'm glad I posted, rather than continuing to bang my head against finding the setting. :) I was just looking for something that seemed a small enough problem to get started looking at.

16 is probably perfect. I just pulled 12 out of the air.
[Kindle Fire Android Development] Jessical:
...If it's a driver thing, how am I having the same USB issue under OS X Lion?
[Kindle Fire Android Development] a2296455:
This is looking better and better, with video fixed, do you think we can get on the Cyanogen repo and have CM9 officially for this device? It looks like progress is going swell we can be released officially with CM9! So excited!
[Kindle Fire Android Development] Jaimemex:
Netflix?

Is there a way to get Netflix working on the ROM yet?
[Kindle Fire Android Development] isaiahhhhh:
I don't mean to be insulting, however these posts are extremely relevant to this thread as it directly involves the future of CM9 for the Kindle Fire. Secondly, Ad hoc is a wireless mode through which wireless devices may communicate with one another. Tethering in the way you cite through the market app directly involves the creation of an ad hoc network via your phone. I'm not sure why your able to tether, it's possible that your tether app of choice has something special about it in this instance or the build of CM7 you're using supports ad hoc tethering. Either way, congrats on the working tether.

---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------

I can't speak for the developer, but as of last night I was unable to use Netflix on the build released on the 2nd of February as well as the latest one released on the 5th.
[Kindle Fire Android Development] rukin5197:
Constant FC's on YouTube now... I feel like I'm the only one getting these random errors. Going t reflash gapps
[Kindle Fire Android Development] jearl75:
Where have all the kittens gone?
[Kindle Fire Android Development] CodenameDeadpool:
I've been suggesting integration of adhoc to cm9 for a couple of days. I have been ignored.
[Kindle Fire Android Development] isaiahhhhh:
From what I understand isn't it a bug issue where it just hasn't been discovered how to integrate it yet?
[Kindle Fire Android Development] CodenameDeadpool:
I don't know much more about it except that it's a hindrance. Lol. Couldn't they get an idea from CM7's code? AdHoc works fine on it.
[Kindle Fire Android Development] lovejoy777:
Where have all the kittens gone?

the puppies went ages ago don't tell me the kittens have all gone now too.

what ever will he take next.
[Kindle Fire Android Development] foxdog66:
This is cm9 but not official. They took cm's source and made it work on the fire and a few mods here and there. This usually leads to official support from the cm team.

Cm7 officially supports adhoc and would probably be your best bet. Even tho the fire isn't officially supported by the cm team, adhoc does work on the cm7 port. Hopefully the cm team will be adding adhoc support to cm9 in the future in which case someone will most likely make it work on the cm9 for the fire (very likely to happen)
[Kindle Fire Android Development] CodenameDeadpool:
I use Whistlestop's CM7 ROM as my daily ROM. I use wifi via adhoc everyday. I'm just wondering why no one on here has tried to do so as of yet? Seems like a biggie to me.
[Kindle Fire Android Development] rukin5197:
Hopefully the people who keep asking ;)
[Kindle Fire Android Development] revxx14:
Apparently MIUI is working on the KF now, and they don't mention HW decoding NOT working, so I think it might work. Not 100% sure, but can someone take a look...?

http://www.theverge.com/2012/2/8/2785559/miui-android-4-0-kindle-fire-custom-rom-alpha

EDIT: Ah, looks like it doesn't work according to this thread: http://forums.miui.us/showthread.php?15369-ROM-ALPHA-MIUI-us-4-0-3-2-2-3-Ice-Cream-Sandwiched!
[Kindle Fire Android Development] Jaimemex:
U again...lol
[Kindle Fire Android Development] Hashcode:
if you're having usb issues can you try my flash .zip in my kernel thread? its for CM9.
[Kindle Fire Android Development] Segnale007:
Its not a bug. Google didn't integrate the IBSS modulation in wpa_supplicant in ICS, which is needed to see and connect to ad-hoc networks.

To make a long story short, wpa_supplicant needs to be patched and recompiled in order to integrate the IBSS modulation and work with ad-hoc networks.
[Kindle Fire Android Development] CodenameDeadpool:
Pain in the ass? No?
[Kindle Fire Android Development] Segnale007:
For me, yes. I will set up a Linux machine with a Android compiling environment tomorrow and read as much as I can about how to patch the current wpa_supplicant used by this rom, and figure out why the already patched same version of wpa_supplicant didn't work on the kindle-fire, though it was clearly something related with the kindle-fire wireless card not being recognized by the patched wpa_supplicant . At this point I don't know whether each device has its own wpa_supplicant that works with its own driver or what.

I'm hoping someone with a little bit more of knowledge will come up with some clarification.
[Kindle Fire Android Development] CodenameDeadpool:
You...are awesome

You are a gentleman and a scholar. Thank you very very much. I don't know much about it, but if I can be of any help, please let me know. I hit the "Thanks" button but I've already given out 8 today so I will get you tomorrow, if it means anything.
[Kindle Fire Android Development] Segnale007:
Please don't thank me as I'm really not sure what I will be able to achieve and I don't want to disappoint anyone. I am not trying to collect any thanks but I'm rather trying to get some help as my knowledge are kinda limited at this point.
[Kindle Fire Android Development] CodenameDeadpool:
I'm just thanking you for listening and trying
[Kindle Fire Android Development] dnd61:
It works very smooth. May better than CM9
[Kindle Fire Android Development] Hashcode:
its clocked to 1.3ghz from what i read
[Kindle Fire Android Development] dnd61:
yeah, and hopefully video will work soon.
[Kindle Fire Android Development] CodenameDeadpool:
I tried it out earlier and don't mind it. Stock System UI kept crashing. I installed ADW Launcher EX and it worked flawlessly(not to mention looked better). Regular ADW crashes every time you try to open it. Overall looking pretty damn decent.
[Kindle Fire Android Development] thornd7:
I'm all for anything that works better! :)
[Kindle Fire Android Development] jfb9301:
Hashcode, that's an improvement for me. It gets me ADB on 02_05. I get the ADB notification, but not the USB notification. Windows drivers have zero errors now, but without the usb notification, I cannot test USB.
[Kindle Fire Android Development] dnd61:
It is just an Alpha, there are many things to do, but it's look nice and i belive it will be perfect
[Kindle Fire Android Development] Hashcode:
So wierd. I wonder if there's a USB notification setting somewhere. I get both adb and USB on mine.
[Kindle Fire Android Development] Segnale007:
@HashCode is kindly taking time patching and compiling the right wpa_supplicant binary that works with the kindle-fire. He will update it on his thread as soon as he gets it to work.

So keep an eye on his thread for further updates .

Bis ups @HashCode
[Kindle Fire Android Development] Fireblend:
So, I'm feeling a little overwhelmed by the latest releases; could someone help me out here? I'm still running VideoTouch1-29.zip, and although I have no complaints at all regarding that release (other than the occasional crash/freeze on some apps), I'd like to have a concrete list of what improvements have been added since on later builds:

USBWOOT.zip adds "USB Mounting", but then the latest one (cm9-02-05.zip) adds "USB partial fix", what's the deal with that? Is VideoTouch1-29.zip the latest ROM with the custom lockscreen (meaning the later ones go back to having a camera icon)? Or have any of the latest ones incorporated it yet? How about the build just posted over at Hashcode's kernel thread? Have there been any regressions worth mentioning since VideoTouch1-29.zip?

I'd say an update is urgently needed on the OP so that:

1. New users flash only one ROM, so that when reporting bugs/requests and the like we're all on the same page.

2. It's easy to determine where development is at.

I get that many of these are "quick builds" meant mostly to get USB working, but the amount of builds is confusing and is making development seem fractured.

Finally, is the bug list still being updated? Which of these builds is it keeping track of exactly?

As a side note, why not do some light overclocking similarly to the MIUI ROM? I'd be happy to have a faster KF :)
[Kindle Fire Android Development] hachiueno:
I was thinking the same thing as Fireblend. It's very confusing to see that USB mounting was fixed in one release, then a later release achieves only 'partial six'. Makes you wonder if USB mounting actually works or not in the previous release.

Fireblend, it's possible to overclock the Fire to 1,2 GHz. Read more about intersectRaven's kernel here :)
[Kindle Fire Android Development] Fireblend:
Oh, I know that :) thanks anyway. What I mean is including overclocking as a feature on the actual ROM (since a build also includes a kernel, no?) as the current build for MIUI 4.0 does (See hashcode's post here), and thus getting a build that doesn't need much tinkering with.

That'd also get us all on the same page and avoid issues/bugs popping up due to people that don't necessarily want to dabble much with development and yet want to stay as active bug reporters playing with different kernels - and thus causing more potential mismatching or inaccurate reports.

Either way, what I ultimately want to suggest after all is getting a "unified" ROM built asap; because the fractured efforts seem to be hurting development and bug reporting.
[Kindle Fire Android Development] That Baker Guy:
+1

also iv been using the cm 9-02-02 rom its gettin terruble battery life now. which rom has the best battery life? im about to flash intersectravens kernel see if that helps, also it rarely goes into deep sleep using cpu spy.
[Kindle Fire Android Development] Firehwk:
I hate having to post this a second time, but has anyone else tried connecting to a microsoft exchange server for email/calendar/contacts? I've been getting a "Can't connect to server." message on both the 2/2 and the 2/5 cm9 builds. The server name, domain/username, and password are all correct (taken directly from my d2g on cm7 and stock kindle fire, and if I enter them incorrectly, I get a "Couldn't open connection to server." or "Username or password incorrect." message).
[Kindle Fire Android Development] jfb9301:
I tried Hashcodes build (located in other thread). Same results as I posted here, ADB, no USB. Plus a few other bugs noted in his kernel thread.

I tried a wipe install of CM9-02-05 and get same results.

Device manager is finally recognizing my KF on these latest builds, but I don't get the usb notification on the KF, so I cannot test to see if USB is working.
[Kindle Fire Android Development] Segnale007:
Its probably a problem with your machine. I have been using HashCode latest build since it came out this morning and I am mounting and unmounting the usb storage just fine in OSX and Linux.

If I was you I'd uninstall the device in device manager and do the driver installation once again.
[Kindle Fire Android Development] jfb9301:
done.... repeatedly, no change, and I've tried this on 2 different machines.
[Kindle Fire Android Development] matchstick13:
I have HashCode's kernel with the 02-05 CM9 build, and my computer recognizes my KF as "Amazon Kindle USB device", but wont let me mount the SD or ADB. I uninstalled it and plugged my KF back in, and it installed as the same thing.
[Kindle Fire Android Development] jfb9301:
I had symptoms similar until I got latest Kindle Fire Utility (0.93) and did the driver install. After that I had ADB but not USB (using hashcodes latest kernel). Without Hashcodes latest, I didn't have ADB or USB.
[Kindle Fire Android Development] JackpotClavin:
And this is with a data wipe? No restoration of anything?
[Kindle Fire Android Development] chazs:
look for touchdown apk, is much better
[Kindle Fire Android Development] jfb9301:
Full Wipe of everything but SDcard

Install CM9-02-05

Install Hashcodes 02-08 Kernel

Install Gapps

Latest drivers from KFU 0.93

symptoms (updated)

No USB Notification

yes ADB Notification

Windows Device manager recognizes Portable Device/D: which is the Kindle

Windows Device manager does not recogognize any Android ADB interface

using >adb shell results in device not found

Windows7 32bit
[Kindle Fire Android Development] matchstick13:
Nandroid

Factory Rest

Wipe Cache/D-cache

Flash 02-05

Flash gapps

Ran for a day

Flash HashCode's Kernal

Oh yea, running Windows 7 64-bit
[Kindle Fire Android Development] Jessical:
Which models of Macs is everybody here using? I just remembered something changed the USB ports with the MacBook Pro unibody models/update to OS X...

I can debug under OS X Lion, but I can't mount/option doesn't show up using Hashcode's kernel.
[Kindle Fire Android Development] marty331:
We are all using the Linux model.

CM7 Infuse - XDA Premium
[Kindle Fire Android Development] nind:
Hey,

i finally compiled a latest version with all fixes since 02-05. The USB mount/app on sd/sdcard remount issues should be fixed now (big thanks to Hashcode and sduvick). The new touch slop setting (better recognition drag <-> long press) from Hashcode is included. I compiled it for stock kernel and latest kernel from Hashcode:

cm9-02-09_stock.zip

c44059eea4cfd5f106d79c635ce9e219 cm9-02-09_stock.zip

cm9-02-09_hashcode.zip

9f06a70faa92f94b0d1fb558fa544853 cm9-02-09_hashcode.zip
[Kindle Fire Android Development] namurt:
i'm currently running 02-05 with IR's kernel.

is a full wipe necessary before flashing 02-09?

HUGE THANKS to nind, btw! :)
[Kindle Fire Android Development] nind:
No, a wipe should not be needed (no guarantees).
[Kindle Fire Android Development] namurt:
i'll give it a go with just a cache/dalvik wipe. and i'll be sure to do a full wipe (if i encounter any issues) before making any "hey, this is broken!" posts.

thanks again, nind. you are a beast!
[Kindle Fire Android Development] matchstick13:
Just FYI, nind's build fixed the SD mount problem for me, but not ADB. Its working on his end, but not mine. It may just be my computer/drivers, but if anyone else has problems there might be something wrong in the ROM.

As always, thanks to the devs for all the hard work!
[Kindle Fire Android Development] csholmq:
ADB works for me. (Using Mac, OS X Lion).
[Kindle Fire Android Development] jwilliamf:
Same here!!, Can't get adb to work. I have an asus transformer, and adb work like a champ, but not KF. I have tried every single guide i have found and every single tip, but no luck. Oh, well!

As long as i can mount sd, everything is fine and dandy.

Thanks nind!!

Update: I be damm! Just fix my adb problemo!!

You might need this: driver and place it in the ".android" directory.