[ROM][24 Feb] IceCreamSandwich Development/Discussion Thread
- Thread starter bl1nkk
- Start date
Well it's in the spreadsheet on the front page, so yes, someone else noticed it and reported it correctly. 
And yes, I agree, it's a bit of a pain, but I am getting used to it. if I briefly touch and hold on an app but let up before ICS registers a long-press, that seems to be sufficient. What's odd is that the keyboard seems to work fine and never seems to ignore presses for me, so I wonder if it's more of a Trebuchet issue than it is a driver thing.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
http://hotfile.com/dl/142975317/d99e3ef/gapps_ics_4.0.3_v10.zip.html
And yes, I agree, it's a bit of a pain, but I am getting used to it. if I briefly touch and hold on an app but let up before ICS registers a long-press, that seems to be sufficient. What's odd is that the keyboard seems to work fine and never seems to ignore presses for me, so I wonder if it's more of a Trebuchet issue than it is a driver thing.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
Since Megaupload was seized by the government today and the names are similar I wonder if that's not why. Total speculation on my part. Anyway I mirrored on Hotfile here:
http://hotfile.com/dl/142975317/d99e3ef/gapps_ics_4.0.3_v10.zip.html
Are you saying that stock 6.2.1 to 6.2.2 fixed the touch issue? Like it didn't work on 6.2.1 but works better in 6.2.2?
I need version numbers. I never deal with stock software so I had not known that some touch issues had been rectified
Sent from my Galaxy Nexus using XDA App
I need version numbers. I never deal with stock software so I had not known that some touch issues had been rectified
Sent from my Galaxy Nexus using XDA App
Last edited:
Well it's in the spreadsheet on the front page, so yes, someone else noticed it and reported it correctly.
And yes, I agree, it's a bit of a pain, but I am getting used to it. if I briefly touch and hold on an app but let up before ICS registers a long-press, that seems to be sufficient. What's odd is that the keyboard seems to work fine and never seems to ignore presses for me, so I wonder if it's more of a Trebuchet issue than it is a driver thing.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
Since Megaupload was seized by the government today and the names are similar I wonder if that's not why. Total speculation on my part. Anyway I mirrored on Hotfile here:
http://hotfile.com/dl/142975317/d99e3ef/gapps_ics_4.0.3_v10.zip.html
Thank you!! I was just about to ask for a mirror myself...I was able to DL new rom update but couldn't DL the Gapps...and since I'm a rom flashing whore it was bugging the crap outta me lol!!
Anyways Thanks again
I meant wifi i use barnacle it seems to be the best so far. Wifi tether for root doesnt work so well i vary phones so itcould be a defy mt4 or g2.
Sent from my Kindle Fire using xda premium
Sent from my Kindle Fire using xda premium
Well it's in the spreadsheet on the front page, so yes, someone else noticed it and reported it correctly.
And yes, I agree, it's a bit of a pain, but I am getting used to it. if I briefly touch and hold on an app but let up before ICS registers a long-press, that seems to be sufficient. What's odd is that the keyboard seems to work fine and never seems to ignore presses for me, so I wonder if it's more of a Trebuchet issue than it is a driver thing.
I think you may be right I just checked and im not seeing it nearly as much in apex as I did in treb.
So you're saying 6.2 was crap, and 6.2.1 fixed it? I need to know the before and after versions
So you're saying 6.2 was crap, and 6.2.1 fixed it? I need to know the before and after versions
yeah thats the basic thought lol
I know this is a little off of a question. but is there a way yet to get the kindle fire back to stock and remove the recovery?
Sent from my Amazon Kindle Fire using XDA Premium App
Sent from my Amazon Kindle Fire using XDA Premium App
Yes, you are clearly off topic. Your question has no place here. But a quick search found this thread.
http://xdaforums.com/showthread.php?t=1399072
does anybody have a link for me for 6.2? can everybody check their download history and give me the address for where they originally downloaded 6.2 if they installed it manually? looking for 6.2 not 6.2.1 or 6.2.2 for clarification
cheers
cheers
does anybody have a link for me for 6.2? can everybody check their download history and give me the address for where they originally downloaded 6.2 if they installed it manually? looking for 6.2 not 6.2.1 or 6.2.2 for clarification
cheers
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.2_D01E_3003020.bin
TY! Will check the differences between this and 6.2.1 which is said to be the incremental where this touch screen bug has supposedly been fixed
Rats. I was digging it up on google and found it. But I got beat to the punch
Used search terms "kindle update 6.2 -6.2.2 -6.2.1 download".
Used search terms "kindle update 6.2 -6.2.2 -6.2.1 download".
Fwiw I think 6.2.1 and 6.2.2 feel the same. Never used anything older...my Kfire came with 6.1 but I upgraded immediately. I know only by reading that there were touch issues before, though.
Sent from my Amazon Kindle Fire using xda premium
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
243IceCreamSandwich Development/Discussion Thread
Hello everyone! This thread is dedicated to Hashcode's and JackpotClavin's work.
This is an Android 4.0.3 ROM not meant for daily use! It is based on CyanogenMod 9.
I will not post any instructions how to flash this to your kindle until it is considered to be ready for daily use. If you know how, feel free to do it.
If you want to join us on IRC:
irc.freenode.net #kindlefire-dev
revxx14 created a Google Spreadsheet to collect known bugs. You can find it right here.
Please take a look at it before reporting any bugs!
A rough list what does not work:
- Hardware Video Decoding
- Light sensor
ROM:
2012-02-24 cm9-02-24.zip
ff4e0ea9c27d28b18226e230e2bf2994 by sitic
Changelog:
+init.d support
+fix default.prop
+Test: Apps use now xlarge layout instead of large
More information here
Google Apps:
gapps-ics-20120224-signed.zip
11b5763810edb732379d39b6df9ccbcf
None needed.
The devs do all of this for free, remember that. Buy them a drink! ♥36Here is a new build:
cm9-02-24.zip
ff4e0ea9c27d28b18226e230e2bf2994
Changelog:
+init.d support
+fix default.prop
+Test: Apps use now xlarge layout instead of large
Remarks:
* I'm not sure if init.d is working as it should, to my impression it's executing too early. I've tried to set it such that it executes init.d when the sdcard is ready but convinced that that worked. Could someone test it properly for me?
* I'm breaking with Google's guideline for display sizes here, if you look at that graphic
you'll note that the Fire is on the edge between the large and xlarge layout for apps. However from the code you see that it is using large layout for apps as it has less then 720 Pixel on the short side. In this build it force apps to go with xlarge layouts, i did that to test if apps looks better and use tablet features. Comments on this are welcome, in particular if there are apps which work significant better with this release. However with next build i think i'll go back to the stock large layout.
This build does not include the new boot animation, as that one is not in the cm sources yet. if you really want it, someone used the image from the youtube video to get the boot animation, follow the instructions on this thread. For the battery percentage display: that are changes from cm, i think they'll make a setting for this soon.
I was working on otg (usb host mode) support, the kernel loads it now, but it fails at loading USB 2.0/1.1 drivers (working on this, it's not included in this build).35here's the .zip with working video. I've also implemented XDA user Chiggins' better volume slider which is much better than my uglier icon
everybody give Chiggins a big thanks! he's the reason we can have nice things
i also cherry-picked a change that hasn't been officially approved that cleans up and fixes some of the touch input code which fixes a lot of the touch events not doing anything. i saw a difference with touch input, hopefully you guys will too
md5sum: 43879eaacc0104af2f935c366cbc0244
http://www.mediafire.com/?y8eocgddv569mdc
this wipes your /system and /cache so you'll have to reflash gapps which can be done consecutively. HD videos do not play with the youtube app, if you come across an hd video that you'd like to watch, just hit the little HD button and it will drop down to normal resolution and will begin playing after that. the little HD button i'm talking about is here
enjoy folks. i think that's it for the major bugs and missing functionality since we've upgraded to ics, now on to the tinier ones31Sound = Working!! Update probably tonight for everybody! Sorry I had been away for quite some time; I had a string of family emergencies and the death of a loved one earlier this week Now just video and we should be set!30
It sounds like you need a little insight. Let's see if I can bring you some.
ICS (or Android 4.0.3) is based on the Linux 3.0.x kernel. This kernel (opposed to the previous 2.6.x) has a few new bells and whistles which makes some parts of ICS (HW acceleration for example) dependent on the 3.0.x kernel.
The KF is OMAP based (Texas Instrument platform) and has yet to receive the 3.0.x kernel from Amazon. Without the 3.0.x kernel, we have to back-port (i.e reconstruct the new bells and whistles) to the 2.6.x kernel. This is very tedious and time-consuming.
Today, there are basically two paths on this;
- Back-port everything necessary to the 2.6.x kernel. This is what Hashcode set up to do initially.
- Get the 3.0.x kernel booting. TI has a working 3.0.x kernel on their OMAP devices named Blaze. The KF has the Otter board in it. Thus, to get it booting we have to customize the config to match the Otter board and be able to debug why our current one isn't.
Right now, most of the work is poured into getting the new 3.0.x working. Unfortunately, the USB interface is initialized quite late in the kernel boot, which makes it really difficult to debug (we're basically blind). That's why I started a thread in finding the UART pins on the KF, to be able to debug properly.
I hope this gave you some well needed information. And hopefully I didn't just encourage you to keep whining.
Ps. I bet pressing the Donate-button will speed things up a little
Code:While(whine==true) do repost this.post end
