Laying on the couch trying to ignore a massive headache while seeing how I can fix the keyboard. Devs get sick too, but this one is too determined to get this working to let sickness get in the way. Sometimes.
[ROM][WIP] United ICS
- Thread starter tvall
- Start date
here's a slimmed latinime.apk that shouldn't be cut off. English only to save space too. A whole ~10mb smaller http://db.tt/rLliMcbr
J
jianC
Guest
DJBhardwaj
Inactive Recognized Contributor
Uh. The two MediaFire links for the CustomMTD zips are broken, giving me a big useless red button that says "Authorize Download".
Last edited:
4.0.4 actually. Latest cm9 code
It's mediafire. And mediafire is having issues today. I'll upload somewhere else later.
DJBhardwaj
Inactive Recognized Contributor
DJBhardwaj
Inactive Recognized Contributor
Rapidshare, MediaFire, I can't tell the difference when I'm half-asleep. >~>
I'll check back and download those two things tomorrow, then. [lumbers over to bed]
I am 99% sure its an issue with the overlay files. I'm using modified cm7 files that I change as needed. All cm9 ports I've looked at had an xml about size that cm7 doesn't have
Last edited:
All the APK's can be slimmed if you remove all other translations and resolutions 
or at least just resolutions.
or at least just resolutions.
All the APK's can be slimmed if you remove all other translations and resolutions
Yeah. Other resolutions is probably a good idea to strip out. I'll work on that tomorrow. In addition to the audio issue. Have you found anything that would help with that?
Take these 3 files from EZGB/CM or any working rom:
AudioPara_TMUS_DREA.csv.gz
AudioPara_TMUS_SAPP.csv.gz
AudioPara_VODA_SAPP.csv.gz
They're located in /system/etc/.audio (it's a hidden folder).
Copy the whole folder in /system/etc/.audio in your rom.
Add this to the end of your updater-script:
Code:
if file_getprop("/tmp/nfo.prop","sysboard") == "trout"
then
ui_print("system/etc/.audio/AudioPara_TMUS_DREA.csv.gz");
run_program("/sbin/sh","-c",
concat("busybox gzip -dc ",
"/system/etc/.audio/AudioPara_TMUS_DREA.csv.gz > ",
"/system/etc/AudioPara4.csv"));
else
if file_getprop("/tmp/nfo.prop","smisize") == "64"
then
ui_print("system/etc/.audio/AudioPara_TMUS_SAPP.csv.gz");
run_program("/sbin/sh","-c",
concat("busybox gzip -dc ",
"/system/etc/.audio/AudioPara_TMUS_SAPP.csv.gz > ",
"/system/etc/AudioPara4.csv"));
else
ui_print("system/etc/.audio/AudioPara_VODA_SAPP.csv.gz");
run_program("/sbin/sh","-c",
concat("busybox gzip -dc ",
"/system/etc/.audio/AudioPara_VODA_SAPP.csv.gz > ",
"/system/etc/AudioPara4.csv"));
endif;
endif;
run_program("/sbin/sh","-c","sleep 2; sync");
set_perm(0, 0, 0644, "/system/etc/AudioPara4.csv");Test it and see if that works.
Oh, I completely forgot about that. When I built I just touched AudioPara4.csv to make it build. Was going to replace it when I actually got it working but completely forgot. Thanks! Ill try tomorrow
Sent from my VM670 using Tapatalk 2
Btw, don't forget to delete the AudioPara.csv that's already in /system/etc
I'm going to just adb push the right one to test if it works. If it does ill figure out how to add it to the source and rebuild. Might as well add autokernel in at the same time (alpha2). Then I just want to strip down the rom and call it stable (alpha3). Getting hw acceleration and camera working is required for me to call it beta or rc
Sent from my VM670 using Tapatalk 2
Ellen is working on a cm7 theme so she doesn't want me messing with her phone today. I'll add audio and kernel stuff to the source and build today, but I can't test till tomorrow. Do you guys want me to release the untested build that might fix it and fixes stuff I needed to do anyway, or do you want me to test first?
Sent from my VM670 using Tapatalk 2
Sent from my VM670 using Tapatalk 2
J
jianC
Guest
I'd be more than happy to test
Sent from my HTC Aria A6380 using XDA
Could you install the rom then push a good AudioPara4.csv to see if it fixes audio?
Sent from my VM670 using Tapatalk 2
Hi guys,
kudos for making cm9 work! However, can someone please post a video to provide other a look at the performance of the rom? If you could include it in the OP that would be perfekt
Regards
kudos for making cm9 work! However, can someone please post a video to provide other a look at the performance of the rom? If you could include it in the OP that would be perfekt
Regards
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
22This is ice cream sandwich for the Dream/Sapphire. Yes, you read that right. Android 4.0, Ice Cream Sandwich. We currently have cm9 and AOKP mostly working. AOSP is next
What works:
It boots
Touchscreen
Wifi
Mobile data
Audio
sdcard
Bluetooth (maybe. It turns on. I don't have devices to test with)
What doesn't:
Camera
Hardware acceleration
probably everything else, tell us
info:
Android 4.0.4
latest cm9 source as of 09 Aug 2013
Latest aokp code as of 6 of June 2012
Downloads:
Cm9:
Alpha3 - https://dl.dropboxusercontent.com/u/19978192/cm-9-20130802-UNOFFICIAL-dream_sapphire.zip
Alpha2.2 - http://dl.dropbox.com/u/19978192/android/update-cm-9.0.0-RC0-dream_sapphire-alpha2.2.zip
Alpha2 - http://db.tt/ejZqOHDX
alpha1.1 - http://uniteddev.com/wordpress/file...0-RC0-dream_sapphire-UNOFFICIAL- alpha1.1.zip
alpha1 - http://uniteddev.com/wordpress/file....0.0-RC0-dream_sapphire-UNOFFICIAL-alpha1.zip
alpha0 - http://uniteddev.com/wordpress/files/update-cm-9.0.0-RC0-dream_sapphire-UNOFFICIAL-signed.zip
Aokp:
Alpha2 - http://db.tt/p2lQtue2
Alpha1 - skipped
Alpha0 - http://db.tt/jErGK56g
kernel -
ezterry's kernel + ics patches and some performance tweaks (enabled 710mhz overclock and other things) http://www.mediafire.com/?py8asp6ab109dyl
ezterry's ezgb 1.5.2 http://sandbox.devnull.name/android/ezgb-kernel/ezgb-2636-v1.5.2_S.zip
cmtd files
http://www.mediafire.com/?amh4qn763gi339r
http://www.mediafire.com/?vw51n1ctl8j1p4t
http://uniteddev.com/wordpress/files/roms/cm9/mtdpartmap.txt
Note: the rom zips are not signed. Flash with clockworkmod, or sign yourself. Once this becomes more usable, I will start signing them.
very slim gapps http://www.mediafire.com/?o94hh30vh0q1oy7 (there are here for testing purposes. contains copyrighted google code that I am not really allowed to distribute. use at your own risk!)
possible fix for camera:
http://www.mediafire.com/?smfhlv2xon1e45z
flashing instructions:
you need to use custom mtd. I used 140 for /system and 20 for /cache (rom currently requires a /cache partitoin. will be fixed in a later update)
1. download all needed files and place them on your sdcard. mtdpartmap.txt needs to be at the root of it
2. flash recovery patch.
3. wipe system, data, and cache
4. reboot into recovery.
5. flash rom and kernel
6. Flash gapps if desired
7. flash boot patch
8. reboot into rom
9. wait.
10. enjoy the awesome
To use data, you need to put in your apn settings. Google to find these.
Thanks to:
Google - android
CyanogenMod team - the awesome rom
Aokp team - aokp
Ezterry and AndDiSa - kernel for ics
Infinimint and the united dev team - hosting and support
My girlfriend - for loving me even though I worked almost all day on this.8Pictures (screenshots later)
Sorry for the blurry pics. Used my other phone running cm9 with a partially working cam
Roadmap:
Slim down (in progress)
Mess with hw acceleration and camera (maybe never) - this will be alpha3/beta1 if it happens
Port AOSP
Changelog:
Alpha2.2: update to latest code. good cm9 release.
Alpha2.1: not released
Alpha2: fixed audio
Alpha1.1: small fixes (keyboard, other stuff) cm9 only bugfix release
Alpha1: fixed wifi, sdcard, and home button (skiped in aokp)
Alpha0: initial public release.
If you want to build yourself (please do, we need more people fixing stuff), the repo init command will look like this:
Code:$ repo init -u https://github.com/UnitedDev/android.git -b ics
Note: rules on using this rom for other projects
Most of android is under the apache2 license. just don't violate that and we're good.
more specific rules: source is on my github, do whatever you want within the terms of the licences. make your own rom, use it to port other devices, release a rom that is exactly the same with a new name and a shiny theme, I don't care as long as you are building from source.
If you use prebuilt anything from releases of this rom, please be nice and send me a pm asking for permission. this is supposed to be an open community, but i hate seeing 20+ cm7 roms with nothing different except name and bundled apps. If you don't ask, and you havent made something different enough from this rom to be worth having its own thread, it may or may not get reported.4Interesting.
Seems to me from reading a bunch of comments in this thread, that there is a severe limitation on this system image as a result of limited internal storage space.
I took a quick peek at the image, and the first thing that strikes me very clearly is that this image is NOT ODEX'ed.
There is a lot of confusion regarding the use of ODEX files in a system image. There is, in fact, no downside to their use, EXCEPT that it will prevent you from modification of contents of /system/framework/, which virtually nobody does anyway, so it is irrelevant.
Basically, when you have a system image that has NOT been ODEX'ed, you end up effectively with multiple copies of 'classes.dex' for each application.
In a non-ODEX'ed system image, all of the archives in /system/app/ and /system/framework/ contain a file 'classes.dex', which is basically the java code for those archives. Upon first boot, the classes.dex file is extracted, optimized, and stored in /data/dalvik-cache, so you effectively have TWO COPIES. One in the application archive, one in /data/dalvik-cache/.
When you ODEX a system image, you perform this optimization IN ADVANCE, and store the ODEX file right beside the application archive. NOT ONLY THAT, but you also DELETE the classes.dex file from the archive, since it is then redundant.
So the effect of ODEX'ing a system image, is that the system partition will be marginally bigger, the data partition will be DRASTICALLY smaller, and firstboot will be FAR FAR faster (since it won't be running dexopt to generate dalvik-cache).
