Guest gold-concert Posted March 4, 2012 Report Posted March 4, 2012 (edited) Guys! You are just great! It's unbelievable, but ICS is available on our device!! Most would even be there is support for GSM, so you can use as a phone! Good luck and thank you for your work!! Edited March 4, 2012 by gold-concert
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 (edited) After my traditional manipulations like with other msm7225 cm9 roms: - move apps to sd-ext; - mount sd-ext on boot and symlink apps in sd-ext; - enable swap on boot; I also took kernel/ramdisk from my original port. I can successfully load our compiled cm9 into user interface. Issues: - damaged graphics on boot animation. (ICS has own graphics interfaces). With original rom I did not even include our hardware graphics driver. So probably should do the same. - touchscreen exhibit strange behavior. Seems touching is off and that rediculous blue circle. But good thing it is a very well known problem on msm7225 ports. (I spent entire Friday reading their forums :) Anyway, great progress. Edited March 4, 2012 by pier11
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 - touchscreen exhibit strange behavior. Seems touching is off and that rediculous blue circle. But good thing it is a very well known problem on msm7225 ports. (I spent entire Friday reading their forums :) Fixed touchscreen by adding /system/usr/idc/* configs from my original port.
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 Other issues discovered: - brightness does not work. Display is dim. (was OK in original rom) - no sound (was OK in original rom) - on-screen keyboard is off screen a bit. (was OK in original rom) UI looks a bit more responsive to me. Maybe our hardware graphics driver still adding a bit. (Fps2D doesn't back this version) Also Gallery worked for images!
Guest dtox125 Posted March 4, 2012 Report Posted March 4, 2012 (edited) Fixed touchscreen by adding /system/usr/idc/* configs from my original port. i think you should add this in pulses device tree to fix the touchscreen.if you havent done it yet. Edited March 4, 2012 by dtox125
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 i think you should add this in pulses device tree to fix the touchscreen.if you havent done it yet. this is what I did essentially, this is how it's got fixed.
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 (edited) as for graphics: looks hardware acceleration can be switched in /system/lib/egl/egl.cfg file. If do u8150 style, which doesn't have physical GPU, (0 1 android; 0 0 qcom): - good boot animation, - Gallery doesn't work properly. Black placeholders in place of thumbnails. (Actually if try to slide them by finger, thumbnail images got revealed. But then disappear again.) - UI feels less responsive. If do our style (0 0 android; 0 1 qcom): - broken boot animation. (I tried even version with proper mdpi 320*480 resolution; also tried cm7 animation). /system/bin/bootanimation could not be replaced from cm7. EDIT: removing booanimation.zip does not help either. Got broken "ANDROID" default animation instead. - Gallery works fine for images; - UI feels a bit more responsive. Edited March 4, 2012 by pier11
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 rotation did not work with normal .32 kernel w/o hacks. working again if replace gsensor->sensors in AkmSensor.cpp in our libsensors.
Guest pier11 Posted March 4, 2012 Report Posted March 4, 2012 surprisingly what works is radio, but no mobile data (msm7225 devices also struggled with that). seems USB mass storage does not work (worked in the first rom).
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 if replace keyboard from the first rom - LatinIME.apk, it will start occupy right place on screen. Curious, which setting affected its compilation this way?... Also miss Messaging app. Ideas?
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 if replace keyboard from the first rom - LatinIME.apk, it will start occupy right place on screen. Curious, which setting affected its compilation this way?... Fixed keyboard. This is the solution (by tilal BTW): https://github.com/GalaxyICS/android_device_samsung_gio/commit/606bbc90ba7d5579c0528db217cd24ba195b82ee same override exist in u8150 tree under ldpi/ folder
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 For some reason I can't change system language - only English UK is an option... (Though can add extra language to keyboard...)
Guest gold-concert Posted March 5, 2012 Report Posted March 5, 2012 Pier11, version with a working radio is not ready yet?
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 that version have many other issues, like no sound is a major of them.
Guest gold-concert Posted March 5, 2012 Report Posted March 5, 2012 (edited) It is a pity. Waiting a successful build. Good luck.Thank you for your work! Edited March 5, 2012 by gold-concert
Guest dr.flo Posted March 5, 2012 Report Posted March 5, 2012 that version have many other issues, like no sound is a major of them. (I did not yet have a closer look at the device trees, so what I say may be obvious to you) Doesn't the u8150 ics tree feature sources of a device specific libaudio (overriding common libaudio)? Since u8150 libaudio is somewhat compatible with our hardware, including their libaudio source in our device tree might help getting their audio? In general I wonder, since u8150 device tree has already received a lot of ics specific fixes, would it be easier to take that tree as a base and make u8220 specific adjustments only where needed?
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 (edited) true that u8150 cm9 tree is way more compatible in the moment with our device than our own. the only advantage I see with our build so far is that radio works. But even that are run a top of u8150 ramdisk (never tried us} but u8150 tree is not ideal for us too. It is low resolution device and have received quite some patches in that area. the point is that differences need to be studied. Edited March 5, 2012 by pier11
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 (edited) got sound if replace /system/lib/hw/audio* from the first rom. Changed some other things before as well, but don't think that influenced/influences working sound. so yes, likely we need to use libaudio source from u8150 Hmm... It's no different then us apart from: -LOCAL_MODULE := audio_policy.u8220 +LOCAL_MODULE := audio_policy.u8150 -LOCAL_MODULE := audio.primary.u8220 +LOCAL_MODULE := audio.primary.u8150 but u8150 build has 3 times more /system/lib/hw/audio* libs, strange... EDIT: our build completely misses (and no u8220 equivalents): audio.a2dp.default.so audio_policy.u8150.so audio.primary.u8150.so @dtox125? Edited March 5, 2012 by pier11
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 (edited) hm... figured that audio_policy.u8150.so audio.primary.u8150.so come from prebuild (!) what put it there?.. What's the origin?... Edited March 5, 2012 by pier11
Guest pier11 Posted March 5, 2012 Report Posted March 5, 2012 (edited) interesting info on Wallpaper Scrolling and hardware acceleration ("Now it's really smooth, better than GB" <-- citation ) https://github.com/G...droid/issues/46 EDIT: And this is from tilal's rom for zte blade: "Full HW acceleration makes it faster than Gingerbread" Curious, will we be able to achieve the same at some point in time with our adreno 130?.. Both of the above are msm7227 machines/Adreno 200 ... (we are msm7200a for those who don't know) Edited March 5, 2012 by pier11
Guest didije Posted March 5, 2012 Report Posted March 5, 2012 Hi pier, to be honest I don't understand half of the things you are writing on this forum :) I am not a programer, so I am unable to help you with this rom. I see you struggling 'alone' to make this very demanding mod and I just want to give you some moral support :) Good luck :) Cheers
Guest cyb3rsp4rk Posted March 5, 2012 Report Posted March 5, 2012 I have one problem :s in my phone u8230(A1 TMN) the rom can't load... it keeps loading but nothing happens
Guest jonnybird Posted March 5, 2012 Report Posted March 5, 2012 I have a 8230 and it works fine afther 10 minutes +/- Very nice work
Guest pier11 Posted March 6, 2012 Report Posted March 6, 2012 (edited) while fighting with brightness in the new build figured that the following successfully control it: echo 50 > /sys/class/leds/lcd-backlight/brightness Max value is 255. And the below lights up keypad: echo 255 > /sys/class/leds/button-backlight/brightness0 value turns it back off. Edited March 6, 2012 by pier11
Guest pier11 Posted March 6, 2012 Report Posted March 6, 2012 (edited) bluetooth actually also works on our build. (I'm using ramdisk from my initial rom...) sent test file from laptop... Edited March 6, 2012 by pier11
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now