Related
THE orignal is here...i just share
http://forum.xda-developers.com/showthread.php?t=1517415
THANX
I am not the developer
Unofficial VLC for Android - Beta build
* not supported by the VLC team *
if u like my post OR HELP plz Press Thanx button...
Doesn't work for me
Our processor is not supported.
Hey guys, I'm working on building AOKP for the Otter/Kindle Fire
She Boots! I'm posting here to get some input from my
Make a backup in TWRP/CWM and wipe everything and flash.
SEE POST 2 FOR CHANGE LOG AND GAPPS
DEMO
Please press thanks
DL HERE: aokp_otter_beta2.zip
Razorback Build 1: [NOT SURE IF THIS BOOTS]
DL HERE: aokp_otter_razorback-b1.zip
If you're feeling generous..buy me a beer Click the 'Donate' button under my name
MD5 Sums
6fb42387b83012a808d04d77748c2aa9 aokp_otter_alpha1.zip
76398973c90790ecefe1b3c692b61918 aokp_otter_alpha2.zip
257b229ebfcdf2fcc9318973c9268b43 aokp_otter_alpha3.zip
d74b7cf7a931cbe15add0ea04817f99d aokp_otter_beta1.zip
c50c8d496ab04743008461526ecbf44c aokp_otter_razorback-b1.zip
3b3fbba31b14a13e8cb94396bd85f66a aokp_otter_beta2.zip
Change Log:
Alpha 1:
+ Initial Release
Doesn't Work:
+ Standard Wallpapers (Live Wallpapers Work)...-Looking for help with this...
+ Touch Screen seems to lack some Sensitivity? -Help with this too
+ Wifi!? -Turns on but seems to hang on 'Obtaining IP Address' -Help here too..
+ HWA
..You know the usual Kindle Fire ICS stuff.
Alpha 2
+ Touchscreen is working normally.
+ Wifi is fixed (Thanks to a tip from Hashcode)
Doesn't Work
+ Standard Wallpapers (Live Wallpapers Work)...-Looking for help with this...
+ HWA
..You know the usual Kindle Fire ICS stuff.
Alpha 3
+ Based upon AOKP Build 30
+ Gtalk should now be working. Get your gApps HERE
+ Minor tweaks to the quick toggles.
Doesn't Work
+ Standard Wallpapers (Live Wallpapers Work)...-Looking for help with this...
+ HWA
..You know the usual Kindle Fire ICS stuff.
Beta 1
+ Based upon AOKP Build 32
+ Gtalk should be working. Get your gApps HERE
+ Minor tweaks/enhancements
Doesn't Work
+ Standard Wallpapers (Live Wallpapers Work)...-Looking for help with this...
+ HWA
..You know the usual Kindle Fire ICS stuff.
Razorback Build 1
+ Based upon AOKP Build 32
+ Gtalk should be working. Get your gApps HERE
+ Hashcode's #3 3.0 kernel plus a minor tweak here and there.
Doesn't Work
SEE THIS POST: http://forum.xda-developers.com/showpost.php?p=24665564&postcount=2
..You know the usual Kindle Fire ICS stuff.
Beta 2
+ Based upon AOKP Build 34
+ Gtalk should be working. Get your gApps HERE
+ Minor adjustments
Doesn't Work
+ Standard Wallpapers (Live Wallpapers Work)...-
+ HWA
..You know the usual Kindle Fire ICS stuff.
kernel 3.0?
no. 2.6.35.7+
http://forum.xda-developers.com/showthread.php?t=1489213
3.0 kernel required for this rom...
If you want to boot it, you need to port the drivers to an older version of kernel 2.6.25.7 for example.
How did you get it to build? I tried porting it about a week ago, but kept getting xlint errors everywhere. I gave up after whitehawkx said he'd quit with it.
animefun135 said:
http://forum.xda-developers.com/showthread.php?t=1489213
3.0 kernel required for this rom...
If you want to boot it, you need to port the drivers to an older version of kernel 2.6.25.7 for example.
Click to expand...
Click to collapse
That post is for the GalaxyS I9000....i don't see anything specific stating it requires a 3.0 kernel....please explain.
death2all110 said:
Hey guys, I'm working on building AOKP for the Otter/Kindle Fire
Right now, it does not boot. It will flash in recovery okay, but it just wont boot, Doesn't look to be kernel related... I'm posting here to get some input from my FELLOW DEVELOPERS ONLY. NOT FOR MASS CONSUMPTION!
ONLY COMMENT/CHIME IN IF YOU HAVE SOMETHING USEFUL....
Please...none of the 'it wont boot wtf!?' posts or ....'is hwa working'....or...'OMGZ CANT WAIT!!!!!!111!!!1!' type of posts...please.
Anyway, if you decide to help, make a backup in twrp and wipe everything and flash.
I have a couple logcats here:
http://pastebin.com/EdWB8qDP
http://pastebin.com/QJYYdgdv
DL HERE: aokp_otter-ota-eng.zip
Click to expand...
Click to collapse
Looks to me like surfaceflinger is not initializing because it doesnt get the correct wake_fb signals from the kernel. So yeah... a new kernel is needed. Or try dropping in a CM9 surfaceflinger...
NRGZ28 said:
Looks to me like surfaceflinger is not initializing because it doesnt get the correct wake_fb signals from the kernel. So yeah... a new kernel is needed. Or try dropping in a CM9 surfaceflinger...
Click to expand...
Click to collapse
Thanks for the tip! I'm looking into surfaceflinger now. At first I didnt catch that till you pointed it out. Glad to have another set of eyes looking at this.
death2all110 said:
Thanks for the tip! I'm looking into surfaceflinger now. At first I didnt catch that till you pointed it out. Glad to have another set of eyes looking at this.
Click to expand...
Click to collapse
Please let us know what you find as the solution. I'm working on another Kindle port as well and having an issue with surfaceflinger too.
Sent from my DROIDX using Tapatalk
Krunk_Kracker said:
Please let us know what you find as the solution. I'm working on another Kindle port as well and having an issue with surfaceflinger too.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
NRGZ28 said:
Looks to me like surfaceflinger is not initializing because it doesnt get the correct wake_fb signals from the kernel. So yeah... a new kernel is needed. Or try dropping in a CM9 surfaceflinger...
Click to expand...
Click to collapse
Tried dropping in CM9 surfaceflinger from the KF cm9 source... no go....
Code:
...
I/SurfaceFlinger( 1305): SurfaceFlinger is starting
I/SurfaceFlinger( 1305): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/SurfaceFlinger( 1305): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake
...
Full logcat here: http://pastebin.com/CHnTMZDS
Just delete hwcomposer.omap4.so and it will boot
Sent from my Galaxy Nexus using XDA
Lemme guess...thats what controls HWA?
SHE BOOTS!
Ill upload a build in a bit.
Well it'll boot. Hashcode has a working hwcomposer for the fire on one of our cm9 repositories. It boots fine without the hwcomposer.omap4 library and isn't noticeable with or without it
Sent from my Galaxy Nexus using XDA
Any way to keep it from being built?
Edit:
Code:
rename Android.mk in the '<source>hardware/ti/omap4xxx/hwc' directory.
Rename the file under hardware/ti/omap4xxx/hwc/android.mk to android.disable and it won't be built
Sent from my Galaxy Nexus using XDA
Ill have a build ready later this evening!
death2all110 said:
Ill have a build ready later this evening!
Click to expand...
Click to collapse
Can't wait to give it a try!!
+1
thanks
Edit:
are you building now
Yes. But I'm leaving it go. I'm spending time with my girlfriend, and family so I'm barely keeping an eye on it, im running it on -j2 just so its not taking all my server's resources...
Edit:
laptop went into standby....closed the ssh connection had to restart compiling. using screen now. so i can safely detach
I found this patchd version of google chrome over on the arc forum, it does install and sign me in but doesn't display web pages for me, the non patched version from the market will not run at all for me and i know is due to no hardware acceleration yet on ics builds for defy, but maybe a dev here can work with this version, maybe not but thought I'd post anyway,
I did not patch this and do not know who did but here is the post i got it from http://forum.xda-developers.com/showthread.php?p=22910621 ,
Download here
http://www.mediafire.com/?4df8r5djnahde60
Sent from my MB525 using xda premium
We'd still need HWA, wich we can't implement on gingerbread so all you can do is wait for CM9 to have it
CM7 + CM9 double boot
HWA will soon be implemented in Defy/Defy+ CM9 ...
lutch83 said:
HWA will soon be implemented in Defy/Defy+ CM9 ...
Click to expand...
Click to collapse
Where from you know that? Is it certain information or you just assuming?
Could someone competent introduce me to the HWA problem on AOSP ICS? Is there a need for new drivers for each GPU model or CM team is prepairing universal solution for this? I'm not very into Android architecture, maybe someone who is can answer?
adiq_ambro said:
Where from you know that? Is it certain information or you just assuming?
Could someone competent introduce me to the HWA problem on AOSP ICS? Is there a need for new drivers for each GPU model or CM team is prepairing universal solution for this? I'm not very into Android architecture, maybe someone who is can answer?
Click to expand...
Click to collapse
Eppy and quarx are working on hardware acceleration for CM9 at the moment. They have got HDA working partially (3D accel.) But 2D acceleration is not yet working. And it's 2D acceleration that is needed in order for chrome to work.
It may be a driver matter, i don't know, but i'd make an intelligent guess on it
CM7 + CM9 double boot
Hi!
It has come to my attention that videos played in this ROM (VGA+) are getting less stuttter / lag. Even without the modified libraries.
As I have checked the date when the libraries (OMX) were created, it was way back 2008.
if I applied the updated libs of the Adreno 200 for ICS ARMv6, the lag is getting obvious, its like there is a sudden freeze in frames.
I don't know for now what's going on here (libstagefright, OpenMAX, and the Adreno 200 drivers) in the cm9.1 alpha 9 rom itself.
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
maybe there is a way on putting JDroid's and Gangster41's modified files here, but for now, I don't know what files to put and what's not, coz I'm no good at modifying the libraries. (No knowledge about linux / android programming)
Everytime I put the modified OMX libs, video acceleration gets worse.
Even the Adreno 200 Lib updates for ICS! :/
hope this info somehow helps the issue on the HW acceleration for ARMv6.
I hope the solution will be found soon, so we will have a fully functional cm9!
Where did you find adreno200 libs for armv6 ics?
thepastormarty said:
Hi!
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
Click to expand...
Click to collapse
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't understood something.
EdikNeznanov said:
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't undertood something.
Click to expand...
Click to collapse
yeah you're right. Thanks anyway. I'll try to look deeper into the files then.
polfrank said:
Where did you find adreno200 libs for armv6 ics?
Click to expand...
Click to collapse
sorry for not replying.
somewhere in the xda afaik.
I have attached the necessary files for the ICS. (The adreno 200 drivers, dont forget to delete the libGLES_android.so.. they said, deleting that file will increase performace, as it now relies on hardware, and the OMX libraries done by gangster41)
As far from what I have read from the android devs on ics armv6, video recording was somehow possible, but in h263, ammb (vid/audio) format.
see here (http://forum.xda-developers.com/showthread.php?t=1860561&page=5)
Hello! Has there been any progress concerning this matter? I tried modifying things some time ago but I failed..
As I saw, thehacka1 has released a rom(icysnap) with better video playback(i hope it s not my idea).
Furthermore I thought that the owl project team could give a little help here, although they re focused on cm10.1 doing a good job...
Are there any chances of improvement or should I abandon hope...? :/
I copied system/lib folder from MIUI v4 by Henry_01 (which has working video playback) into SlimSandwich and video was working correctly. I just thought I should share. So, we have working video playback on ics!
trying put the latest nightly cm-11-20140308-SNAPSHOT-M4-otter.zip got fail in TWRP Recovery 2.6.3.1:, when trying dirty flash from cm-11-20140117-UNOFFICIAL-jem.zip reason not understanding cant i dirty flash ? how would i update to this rom snapshot-m4 ? im not sure but im on hd 8.9 it is Amazon Kindle Fire (1st gen) correct?
this forum rocks thanks for the help
Wrong device, simple as that. 'otter' is the first-gen Kindle (the blocky, low-res ones). The HD models are the second gen, HDX are third gen. Do not attempt to flash anything that doesn't have the 'jem' identifier in its name.
If you're desperate to get the latest nightly build I suppose it should be possible to extract the necessary binary blobs from Hashcode's build and recompile and link the latest CM from the source. Personally I'm just waiting until someone who knows a lot more about it thinks the changes have made it worth building an update.
charlesky said:
Wrong device, simple as that. 'otter' is the first-gen Kindle (the blocky, low-res ones). The HD models are the second gen, HDX are third gen. Do not attempt to flash anything that doesn't have the 'jem' identifier in its name.
If you're desperate to get the latest nightly build I suppose it should be possible to extract the necessary binary blobs from Hashcode's build and recompile and link the latest CM from the source. Personally I'm just waiting until someone who knows a lot more about it thinks the changes have made it worth building an update.
Click to expand...
Click to collapse
ok thanks silly me ill stay put for now ill also wait thanks just thought by updating to M4 fix sum bugs
update latest one from hash ROM-AOSP] Unofficial CM11.0 KFire HD 8.9 (KK 4.4_r1.2) [03/15 MMC LAGFIX]
thanks closed