Issues:
The CWM recovery is based off of the Feiyu 0930 Kernel. It should not break touch screens.No freaking way!!
Couldn't thank you enough!
A few questions, though.
Is the provided CWM safe for use on the fire i.e does it use one of the newer Feiyu Kernels?
Also, is this ROM based of the older source code which does not have the required fixes for the touch screen?
because he's too busy coding i guess? Also, I already asked if it was a problem, and he said it's ok.Why did you make this post and not Christian Troy?
@Geodex, I intend to keep updating the board, however I'd be more than happy to have CT start one himself.@novadaemon if you are going to be updating first post when CT releases new updates/patches I don't have a problem with you starting this thread.
If not let me know I will close this and CT starts one he can update himself as the forum is running an old version of IPBoard hence no way we can give CT permissions to edit first post when he wants.
Will be hard for any mod to dig through all CT's posts in here once this thread goes mental like all the others.
Cheers.
The difference is in the screen used. Two different companies screens were used. Early models are QM and newer models are TM.What is the defference between Fire TM and QM?
Sorry if answerd before.
Hmmm it's not the same as how it was on ICS/Flambe, but it's close enough. I prefer the Circle + Percentage anyway. Thanks!it's there in the setting. you just have to enable it in status bar setting.
It's not a ROM issue. It's a hardware issue.Is high-pitched mosquito noise still a bug in these CM ROMS ??
Can handle the popping but that damn mozzy is getting an extreme pain!!
There isnt supposed to be one. You are supposed to extract uImage_recovery to your SD card.im new to modding the flame so bear with me, ive downloaded the CWM5.5.0.4 file and there is no .zip inside the .rar so what do i extract and where?
I reread the instructions and realized how it could be confusing. I've modified the instructions to make it more clear. I apologize for the confusion.thanks done the CM10 update, ill let you guys know how i fair! awesome timing considering my micro sd card only arrived this morning off amazon and have been using the stock firmwire from ainol for the past 3 days
Are you using the 10-18-2012 rom and Compatibility 1.0.1? And did you make sure to use the proper file for QM or TM?got an issue with my sd card, it doesnt get recognised by the flame anymore, its the same card i used to get CM10 flashed on to my device, if i plug in my tablet to the desktop and turn on mass storage then the sd card files are visible but the tablet just wont interact with it so install any .apk's for example, appinstallers say i have no sd card mounted
That is terrible to hear.I think I have fried the "touch" part in my touch screen.
When i was updating to CM10 I saw that there wasn't the zip for the "compatibility" (damn it). Then (my mistake) i have rebooted, it was too late when i thought that CM10 without the compatibility zip will do harm to my fire.
I have managed to reinstall another firmware, but, well, my touchscreen doesn't work. I just want to know if it's too late and i can throw my fire in the bin or if there is some kind of update that can make my touchscreen alive again :-(
remove the factory update file and redo it manually.Gets to about 25% then freeze. :/
Factory update aml file
ulmage-recovery
And fire 0930 qm zip on sd card
added. It was 3:13am here when you posted it. sorry about the delay.add this one to the op, from now on they will be harmless if you forget to flash the compatibility zip since there's no boot.img flashing in the rom .zip
@ludwig
in recovery? try formatting media partition using stock recovery or flashing this file
What is the full filename of the ROM you are flashing? is it the repack or the normal version?why is that I can't flash it on my FIRE .. TM VERSION..when i try to flash the rom it says
.......even place the CWM TM v5.5.0.4 extracted file on the right place.
I will check on it, but if you could take a screenshot or a picture of the screen when that happens, that would be great.There's another bug I found during watching youtube and dailymotion within default browser and chrome.
1. In default browser, the video is played somekind bigger or not scaled in the player while watching youtube or dailymotion in lansdscape mode. But if I rotate in portrait mode the video is still played in landscape mode although the browser is rotating according to portrait mode.
2. In chrome browser, there's no video playback.It is blank or pitch black although the playback time is running.
Not sure if this happens on the previous builds but on Flambe it was working good. Nova could you support my findings.
Thanks.
