B
I have the same problem. Thanks for pointing out the fix, it worked fine for me. I did notice that right before the reboot, ROM Control popped a message on the status bar, but it went by too quick to read.
Otherwise, this is a really nice ROM. I do notice a little lag with screen touches, but it's an minor inconvenience for me more than a major issue.
Great job overall.
That is an interesting question. Post 3 in the thread provides the info.
There have been atleast 2, possibly 3, versions of the zip package. These are the 2 I know.
aokp_otter_build-33_0xD34D.zip
aokp_otter_build-33r2_0xD34D.zip
33 has kernel #6
33v2 has kernel #7
As much as I respect Hashcode for getting 3.0 working, his packaging of the boot.img leaves a bit to be desired. The img for 6 and 7 both say they were built on Feb 28th 2008 lol. The only way to tell the difference is via file size. Heaven forbid he makes a change where there is no change in size.
Works pretty good touch sensitivity needs a little amping battery consumption is high Google earth stops unexpectedly some small buggy things but nothing major. Its really sweet to have HWA on ICS finally netfilx and in browser flash seem to work well for the most part. All in all no doubt this is some fine work thanks
I tried wiping dalvik and cache ..even uninstalling and re installing amazon mp3 and each time i press the icon..boom,reboot. (sorry hit the wrong quote..it's for the guy who fixed his amazon mp3 problem)
Last edited:
I've got no adb connection as well.
Compairing this with an the build 32 rom, I noticed that in build 33 I see both the "USB debugging" and the "USB Storage" icons in the notification bar. I'm not able to kill the "USB Storage" from the UI. It always comes back as long as the usb-cable is connected.
When I look at the uevents with udevadm monitor, I get the following
Build 32, working adb:
Build 33, non working adb:
Any chance to kill that "USB Storage" connection in this build?
Ufff, I've had issues before on a Win 7 64 bit machine - haven't tried ADB with this particular ROM yet - and for a time now I've been using wireless ADB only . Never fails to work. Otherwise, you might want to reinstall USB drivers, etc., and it might work.*
Check to see if the drivers are installed. I've since switched to a different rom, but IIRC the device id has changed with this rom. Not sure why or how that's even possible, but check your device ID in Device Manager to make sure its not different.
I had to add
to [Google.NTamd64] and [Google.NTx86] in android_winusb.inf before it would recognize the drivers, but after that it worked.
I had to add
Code:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_021&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01to [Google.NTamd64] and [Google.NTx86] in android_winusb.inf before it would recognize the drivers, but after that it worked.
I really like the polished feel in this rom, but the touch slop makes it hard to use regularly. and rom control crashed randomly pretty often now.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
The problem is with USB somehow, ive used ADB before with kindle and use with Samsung Galaxy 5.
I can access adb using Wifi adb
I can access adb using Wifi adb
So what are you doing when ROM Control crashes? A little more info can help to track down possible problems. Just saying it crashes is not a big help without knowing what is going on at the time and the steps required to reproduce it.
I'm actively working on this ROM so the more info that you guys can provide me when you have issues, the better chance I have at tracking down the cause and fixing it.
It doesn't matter if you can access it using another device or if you've accessed it before. If the device isn't showing up in ADB then you either have debugging disabled, or the driver isn't installed. Since you have wireless ADB setup I'm guessing its the latter.
Even if you've installed the driver, if the device ID has changed Windows won't recognize it as a Kindle Fire. On mine it showed up as "Amazon" instead of "kindle" with a device ID of VID_1949&PID_0001 when it should have been VID_1949&PID_0006.
When you plug the device in Windows will scan android_winusb.inf for that ID and if it doesn't match then it won't use the driver. No driver, no ADB.
Android uses separate drivers for ADB and Mass Storage. You can have mass storage without ADB. If ADB is installed it will show up like this:
Check to see if there are any unrecognised devices.
What app are people using to take screenshots on this rom?
I haven't gotten any to work yet, and we don't have the hardware to do it native.
Sent from my Amazon Kindle Fire using Tapatalk 2
I haven't gotten any to work yet, and we don't have the hardware to do it native.
Sent from my Amazon Kindle Fire using Tapatalk 2
TWRP is different. When I was having trouble I could still access adb from recovery. But if the device isn't even showing up looks like you have the opposite of the trouble I'm having. I have ADB but no mass storage on CM9, but mass storage works in TWRP
Try plugging it in and using DDMS (android-sdk\tools\ddms.bat). Just select your device and press ctrl-s.
I would, but adb isn't working for me right now.
Sent from my AOKP Amazon Kindle Fire using Tapatalk 2
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
63
I present to you AOKP for the Kindle Fire
Milestone 6
Let me start off by giving thanks to some people that have made this possible.
Team Kang:
Roman
Whitehawkx
Zaphod-Beeble
Jonathon Grigg
ProTekk
Khas Mek
sethyx
And a big thanks to Hashcode who has made a 3.0 kernel for this great piece of hardware!
Major changes since Milestone 5
- Removed FB sync
- Added ability to hide sender and/or message body in notifications (Mms)
- Added CM9 T-Mobile theme manager
- Added Sense 4 style Task switcher (you have the option of choosing from stock/web os/sense 4 now)
- Added ability to play boot sound (disabled by default) -- read instructions in ROM Control >
- General > Boot sound
- added delayed ring feature to Phone
- added Emoji to Mms (enable in Mms settings)
- added AOKP wallpapers app
- added USB tether toggle,
- added AOKP clock widgets
- added notification counters
- new boot animation
- added nav bar widgets (must add nav bar widgets button/long press button in nav bar settings and add some widgets to play with!)
- added AOKP stats (www.stats.aokp.co) -- you can opt out
- added bluewall firewall - RC > General UI > Less Notification Sounds -- limits the number of notification sounds an app can play per X seconds, so like 1 GTalk ping/30s, but notifications will still be coming in
- improved weather code
- added "copy to clipboard" option in "Share" dialogs throughout Android
- added hardware info in about screen
- added new music layout to lockscreen (you can choose between old and new)
- added nfc toggle
- added nfc polling settings (Settings > More > NFC polling mode)
- made lockscreen weather prettier
- fixed DRM issues
So what makes this build different from the stock (no longer supported) ROM? Well here's a list of features I've added:
System UI
- Added volume slider w/mute to the status bar settings panel for quick access to system volume level
- Added a screenshot button, which can be enabled in ROM Control, to allow quick access taking a screenshot of current screen.
Trebuchet
- Added an easy access settings button at top right of home screen
- Added dual docks - now you can use up some of that empty space by placing apps and shortcuts into these two docks for quick access to these apps on any home screen
ROM Control
- Added screenshot button which can be added to the navbar buttons
- Added settings for changing location of the volume slider in the stats bar settings panel
At this time I have not found any issues with the ROM. If you find a problem/issue/bug please let me know what it is and how to re-create the problem. Working with the source is far easier than the work I have done with MIUI so I have much more control over the issues.
files
AOKP for Kindle Fire - Milestone 6
gapps11
I'm all for working with others. The problem I have had is that I see people putting out these ROMs but not really fixing issues or making it functional for the hardware it is running on. That was my motivation for building AOKP myself and share it with others.
I see people doing this sort of thing where they port a rom or get something working on another device and leave it at that (not saying that's the case for the other AOKP roms). I understand that is a logical first step, but I like to code and if I can fix problems and add useful functionality I will do so.10I'm back!!!
Since AOKP have decided to no longer support our device, I decided to get back in action with my customized version. So I present to you Milestone 6 with my usual changes. Once they release Milestone 6 to the masses I'll update the OP with the latest change log. In the meantime, enjoy this new release!
L!TH!UM aka |0xD34D|8
To clarify, AOKP merged the old 2.6 kernel based device tree into their sources. It has not been maintained or updated since then. I'm sure you could actually make their M5 build work by flashing back to a 2.6 kernel and then applying the official AOKP build. But there also might be bugs, etc.
A few more bugfixes and I will get the new device tree merged into AOKP for "official" support of the 3.0 kernel based build. At which point we would be able to grab official builds such as this and go crazy flashing.
Sent from my XT894 using XDA7
Official support for the 3.0 kernel version of the Kindle Fire won't happen until the new kernel is in a more final state.
In the meantime, the community is going to rely on devs to produce up-to-date builds using the latest sources.
Just tossing that out there for what its worth.
Sent from my XT894 using XDA
New posts
-
[App][Beta] Stinger News - News and RSS feeds your way. [FREE] [NO ADS]
- Latest: Stephen.k.spear
-
-
Does usb otg not work on all custom roms or works on some?
- Latest: myanonymousaccountname
