yashsingh1/xdaforums huggingface dataset:
[HTC ChaCha] adlx.xda:
I haven't tried the "Integrate Dalvik cache system elements into ROM" in TB, but I guess it's not done though symlinks. I'd say it's like odexing the apk.

Edit:

I could build the rom odexed (like CM9), which should give some more space on /data (less dalvik-cache). First builds I did, wer odexed, but they wouldn't fix in the /system part. So as a fast measure I rebuilt it deodexed, which is slimest, so it would fit in /system.

I guess I could build it odexed, and remove not oftenly used components (as you guys have shown earlier). So it would be "CM10-lite odexed".

Unfortunately, right now I can't build anything anymore as I have no machine to build on :(.
[HTC ChaCha] atrix4g18:
Here is the ROM without LATINIME.apk and a few others. It won't require any apps to be deleted. GAPPS can be flashed right after.

INSTALLATION:

1. Reboot Into CWM Recovery

2. Wipe DATA, wipe CACHE

3. Flash ROM .zip file (CM10-20121023-CHACHA-LITE-atrix4g18.zip)

4. Flash GAPPS .zip file (gapps-jb-20120726-lite-rebased.zip)

5. DONE!

ROM: http://www.mediafire.com/?4004juylnpfvu11

GAPPS: http://www.mediafire.com/?7m6zv8nc2gdynp8
[HTC ChaCha] adlx.xda:
Please don't post mods of my rom in this thread, which is for development & improvement of the CM10 post. It will mess the thread with the feedback from users who downloaded it.
[HTC ChaCha] Nicois:
Hmm, I think there's something more basic I have wrong with my script. I simply get the CWM "installation failed" message whether I leave the META-INF as-is (with signature checking disabled) or I delete all the files in that area. I did also try using a couple of different java apps to sign the zip file (using test keys) but that failed in the same way. I will reduce the amount my script is doing until I get it working, which will help isolate the problem. e.g. I don't know if I need to remove the entries from the MD5sum file if I've deleted the files.
[HTC ChaCha] atrix4g18:
Why not quickly fix the ROM then? I appreciate your work, but getting more people on this ROM to test it and help improve it is a good idea. Simplifying the installation would be smart.
[HTC ChaCha] mobilepgk:
Have patience atrix4g18...! This is what adlx said earlier, which probably you missed to note...

>>Unfortunately, right now I can't build anything anymore as I have no machine to build on .
[HTC ChaCha] Alex C.:
Because for example some of us might need the stuff you removed. LatinIME.apk represents the stock keyboard, which for example, I need. Basically I can't see any other alternative now other than the ROM odexed to increase free space and removing some of the apps people in general would not use.
[HTC ChaCha] adlx.xda:
In META-INF there is also the updater-binary and update-script (or very similar naming). You can't remove that. CWM "only" unpacks and launch that.
[HTC ChaCha] Nicois:
Thanks for the help.

It turns out that the problem was simply ubuntu's zip is not compatible with cwm for some reason. I have modified my script slightly to use 7zip, and pasted the script here.

As people have pointed out, everyone wants to maximise free memory, but they also need/want different apps, and have different perspectives on what should be in /system. Hopefully this script will let each of us make a few edits to this script, and then use it to excise the unrequired bits of the system before flashing. I'm just too lazy to keep deleting apps every time I flash. For example, if you run the script as it is, it will install, but you will have no launcher at all. Most people will probably want to keep the trebuchet laucher apk.
[HTC ChaCha] ethancottier:
Thank you! Perfect daily driver for me now! :D lgCamera also works fine for taking pictures and videos :) and the wireless tether "fix" for CM9 also works on here, and the google now for cm9 also works. Just clear enough system space and remove the current google now first :)
[HTC ChaCha] atrix4g18:
Right you are. Just updated the thread with my build to tell people about that. I'm glad the development is going well so far.
[HTC ChaCha] kronflux:
I'm not entirely sure what the LatinIME is for. is it just an on-screen keyboard? or does it actually have something to do with keymapping or similar?

either way - rather than deleting it, I've found a thread in which a guy compiled the APK with specific language versions.

here's the thread:

http://xdaforums.com/showthread.php?t=1864193
[HTC ChaCha] Alex C.:
http://developer.android.com/guide/topics/text/creating-input-method.html
[HTC ChaCha] mobilepgk:
well, I have removed LatinIME.apk and have been facing NO issues over last couple of days. I use US EN lang by the way. Also have NOT tried to use speech input (like in google now etc).

by the way, on different subject, I see that my clock reminder audio is not working, I just get vibration mode. I hope it is not related to my experiment of moving all /system/media/audio to sdcard. Even though my notifications and call ringer works.

Can someone please test the clock ringer for me please? Thanks.
[HTC ChaCha] kronflux:
I'm not entirely sure what the LatinIME is for. is it just an on-screen keyboard? or does it actually have something to do with keymapping or similar?

either way - rather than deleting it, I've found a thread in which a guy compiled the APK with specific language versions.

here's the thread:

http://xdaforums.com/showthread.php?t=1864193

*****

Also, I noticed today kind of a major bug we have. When using the phone, the proximity sensor doesn't seem to work - so when you put the phone to your ear to talk, it presses numbers. Makes it very hard to use -as a phone- :p
[HTC ChaCha] skezza:
Has anyone done a video demonstrating CM10 on the ChaCha?
[HTC ChaCha] adlx.xda:
OK, that shouldn't be to dificult to fix, lol, I already faced and fixed the issue in CM7 and 9

Sent from my Galaxy Nexus
[HTC ChaCha] kronflux:
any chance you can poke at the rotation issue with the dialer as well while you're at it? so it's in landscape during a call, rather than portrait?

I dunno how hard of an issue it is to fix, but you also fixed it in CM9, so I'm hopeful that it's nice and easy xD
[HTC ChaCha] atrix4g18:
No. There's not much to see. It works as well as CM9 really. Sometimes feels smoother to me. Why don't you make a backup and try it out?
[HTC ChaCha] adlx.xda:
Sure, just did actually ;)
[HTC ChaCha] atrix4g18:
How often are you thinking of releasing new builds? Obviously you make changes over time and it's not worth a new build for every change, but what were you thinking? Have you thought of making Zips that can be flashed over the ROM to include the changes and fixes you make?
[HTC ChaCha] kronflux:
Each build is technically flashable over the current rom, and will update most things - there can be issues with things that were broken, when they suddenly work properly. One of the more common things people forget to do upon flashing an update rom over their old one is to clear their cache, and dalvik cache. Still, that doesn't always fix everything, so it is -best- during rom development to fully wipe the device each time you flash an update.

But once we are at a 'stable' level, you shouldn't see any issues in flashing updates over the current rom.

For a long time during CM9 Development I only ever flashed zips over my current rom - it wasn't until the camera got fixed that I encountered a situation where it didn't fix it for me simply by updating, at this point I had to completely wipe the device to get it to work.

So you can try just flashing the updates, and if you encounter issues -then- do a wipe and flash. if you dont encounter issues, great!
[HTC ChaCha] atrix4g18:
Sorry I must have said that wrong. I know what you're saying already. What I'm saying is maybe the dev could release zips to flash over the ROM to get fixes out quicker. Back on the Atrix 4g forums when Jelly Bean first came out I remember downloading it right away and shortly after the dev released a 12mb zip that fixed a bug. Do you know what I'm saying? Instead of waiting to fix a bunch of bugs and releasing a full new build of the rom the dev could just release small zips that fixs bugs. It is not worth rebuilding the rom just to fix the phone call bug where the screen doesn't turn off while calling, however if a zip can be put together and released that replaces files, adds files or removes files. This could easily be released and it would be worth making. After enough bugs have been fixed a new rom can be built and released.

Of course, what you say does apply; some bugs may not be able to be fixed simply by flashing a zip over, however I think most bugs will be able to be fixed like this and it would benefit everyone.
[HTC ChaCha] kronflux:
Ah. now I understand better.

I imagine this is possible, but I also imagine it would get a little disorganized without an actual website or release system in place where we could get these fixes in proper order, and remove fixes that no longer apply.

For the very same reason Adlx doesn't allow people to link to their own builds of his rom within this thread, I imagine it would apply the very same to small fixes.

The best thing to do is be patient. This is currently not recommended for daily use anyway, just mostly for testing, as it's alpha and experimental.

Personally I'd rather see a bunch of stuff get fixed in one release, rather than having to flash many little updates anyway.
[HTC ChaCha] atrix4g18:
Yeah, that's true. Honestly I'm using this as my daily though. It works well enough.
[HTC ChaCha] Alex C.:
In terms of flashable zips it really depends. You might have a patch that fixes something but breaks something else. Usually I would go for a full build with wipe data/cache beforehand. It has been noticed that flashing another rom on top of the current one already causes a lot mishap.
[HTC ChaCha] adlx.xda:
atrix4g18, I was thinking, instead of publishing a mod of a specific version (in time) of the CM10 I published, which will force you to publish again a Lite version each time I will publish myself a new build, maybe you could prepare only 1 zip (not 2) that would do the following:

- 1) Remove unecesarry stuff from whatever CM10 build I will publish

- 2) Add Google Apps "lite"

The way I see it, it will be better for everyone:

- because you won't need to update your "rom lite" zip each time,

- people will always be able to download and use my latest published rom (and also I'll keep my download count)

- it will be easier for users, becasue they will only have to flash my rom, then afterward flash your "liten+gapps" zip, to get a fully usable system with latest CM10 build + Gapps Lite

If you do that I believe this will be real added value for the users to my work, and I'll publish a link to your thread from here (in OP or OP+1).

Maybe you could also **** in your zip the lgCamera app, and why not the stuff for Google Now, and Wifi Tethering by EthanCottier (with credits).

I think it would be great. What do you guys think?
[HTC ChaCha] Nicois:
Hey, I'm no expert but if the APKs are ODEXed, the davlik cache files for these apps will be tiny, won't they? So we can load up /system with a bunch of APKs and not eat away at our very limited /data partition.

I know that ODEXed APKs are very system (hardware and OS/library) dependant, but that isn't a problem. We all have the same firmware and we are distributing the APKs along with the rest of the CM10 OS.

Or am I missing something obvious?
[HTC ChaCha] adlx.xda:
Right, dalvik-cache for those will be small or even non-existent, but it will grow size in /system (which is the reason why I made the first build deodexed).

I'll be able to make it odexed, but the tradeoff will be I'll need to remove stuff from the build. I'll check back in the thread for your experiences about what you have removed.
[HTC ChaCha] mobilepgk:
I am not expert either, hence I missed this 3rd option of odexing. adlx and alex had been quick enough to realize that "odexing" is one of practically favored option to go further, and I guess adlx is working on it already! thanks.
[HTC ChaCha] adlx.xda:
OTAs

Regarding publishing incremental updates, it's a possibility. It's actually easier for users, sure. From the dev PoV it depends. Depending of the stuff involved in the incremental update, it can be more or less easy to prepare the update script in the zip. Also the side effect could be variable, and then it would be a mess to help users with issues (as for each incremental update the upgrade path and possible ending version installed in the users phones multiply).
[HTC ChaCha] adlx.xda:
The good thing is there's not much of work on for that ;), it's a matter of a choice, decide if you want to build odexed, or not (deodexed).
[HTC ChaCha] Alex C.:
@adlx.xda - As far as I can see, currently we have a lot of apps that we can dispose without affecting the general usability/usage of the ROM. I would do a compare with the CM9 apk's and see the diff on first install.

Mod-Edit: Cleaned quote of deleted post

jotha - forum moderator
[HTC ChaCha] mobilepgk:
yes, I liked idea of keeping ROM available only at one place. This way work is not duplicated which will clearly avoid any confusion on people's part.

In addition this way it clearly brings out each ones expertise clearly, thus helping to have clear ownership defined. This is way to go and improve synergy.

btw, in some other cases of ROM being updated/modified (say adding kitchen stuff etc), then it ofcourse makes sense to duplicate ROM in other thread, but not in this case of just trimming. Hence atrix4g18 may focus on his expertise ie. zip involving triming and installing gapps light.

Thanks all for great work so far. CM10 is really worth to work together and make it better.
[HTC ChaCha] unreal64:
May I ask you if the front camera also work with this app?? Thank you! ;)
[HTC ChaCha] kronflux:
Personally I like the way things are done now. I don't really think smaller updates are better, and I also don't like the idea of being forced into having certain apps or having certain apps removed.

For example: the google apps lite that has been linked to recently still has a couple things that can be removed.

The current LatinIME has all languages. Which is good for rom release, but not good for space.

It sucks not having a user friendly copy of the rom, that does everything for you - but at the same time, each user's needs are different.

I say for now, we should stick to releases the way they are, and come up with our own ways on saving space, or deciding whether or not to install gapps.

Maybe once we get a little closer to a stable release would be a good time to decide what way it should be released, and what apps should be included or removed.

That's just my opinion.

PS: could someone check in a web browser if they can enter numbers in login forms and such?

Mine's function button isn't working in the browser for some reason, and I want to pinpoint

whether it's the custom LatinIME I'm using, or if it's an actual bug with the web browser.

EDIT: also, noticed in the Terminal Emulator, "FN" + "H" (ie: "_" [underscore]) doesn't work. it puts a space rather than an underscore. In fact, it won't even accept a pasted underscore. It treats it as a space. I even tried running a command with an underscore in it's initial command preference, and it still treated it like a space. so confused!
[HTC ChaCha] ethancottier:
I've removed LatinIME but it was like that anyway. You just need to hold down FN and press a number/symbol key :) instead of pressing FN once, then pressing the number/symbol key. Same goes with shift+capital letters :)

---------- Post added at 07:39 PM ---------- Previous post was at 07:39 PM ----------

It doesn't no... blame HTC!!
[HTC ChaCha] Nicois:
I don't see the downside of odexing. I have 70+mb of /data used by dalvik-cache, and if a lot of that won't be needed with odexed packages, it's worth it.

If anyone really wants a deodexed build and it's just a compile-time option, you could just make both and let people choose.

I'm also looking at how hard it would be to odex non-system APKs, to further reduce the wasted space in dalvik-cache.
[HTC ChaCha] empy16:
Most of the camera apps in Google Play work with this rom.

P.S. I think this should be in the screenshots, just so everyone would know. (With Low-ish screen brightness)
[HTC ChaCha] atrix4g18:
http://xdaforums.com/showthread.php?p=33345746#post33345746
[HTC ChaCha] atrix4g18:
****THIS IS A FLASHABLE ZIP WHICH WILL DO THE FOLLOWING****

- REMOVE SOME APPS IN /SYSTEM/APP/ TO FREE UP SPACE

- INSTALL GAPPS

- INSTALL A WORKING TETHERING APP

INSTALLATION:

*FLASH OVER ANY CM10 ROM*

- Reboot Into CWM Recovery

- Flash "NEW-CM10-mod-1.1-GAPPS-ATRIX4G18-20121027.zip" (Link below)

- Reboot

DOWNLOAD: http://www.mediafire.com/?pv7ec5101yeaqvs
[HTC ChaCha] lucasarran:
EDIT: I will repost in the other thread
[HTC ChaCha] adlx.xda:
Removed by me
[HTC ChaCha] adlx.xda:
LInked in the OP+1 so people can get to it easily.
[HTC ChaCha] atrix4g18:
Thanks. The latest version in that thread has the tethering app built in. I got it from the Play Store set the settings correctly and then backed it up and built the zip to include it. So now it trims the rom, installs GAPPS and installs a functional tethering app.
[HTC ChaCha] Nicois:
Is it true that if you're including the odex file, you can remove the classes.dex from the APK/JARs? If so, from what I've read the oxexed versions would take about the same amount of space as the original, so there's no tradeoff in terms of space.

I'm only going on what I've read; I don't have any hands-on experience either odexing or deodexing.
[HTC ChaCha] Nicois:
OK, I just executed this script (with the bootloader lines updated) and my system went from 52mb /system free and 25mb /data free to 12mb /system and 89mb /data.

Of course the exact effect of this script depends on your setup (e.g. which gapps you have installed) but I'm very happy with the outcome. I haven't fully exercised my phone since, but it certainly boots up and appears to work exactly as it did before.

The bootloader bit of the odex script looks like this:

BOOTCLASSPATH=/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
cd /system/framework
for filename in core.jar core-junit.jar bouncycastle.jar ext.jar framework.jar framework2.jar android.policy.jar services.jar apache-xml.jar

Just read the instructions properly in the linked thread (e.g. mount /system and /data from CWM, and make sure adb is working) before you run the script.
[HTC ChaCha] Hongrois123:
Power Widget Brightness Control

Anyone tried to touch the brightness control icon on the power widget? Its wild :)... screen never comes back, only full wipe, reflash helps

Please @Alex C. and @adlx.xda try, curious what happens...

thanks in adv
[HTC ChaCha] ethancottier:
What's weirder is that I don't have a power widget lol. I know that I did.. but it's somehow disappeared :S
[HTC ChaCha] Nicois:
I have experiencing a few lock screen issues.

Until earlier today, the lock screen worked properly, letting me swipe to unlock.

I changed a setting for the lock screen, moving the clock to the other side of the screen, and now the thing you're supposed to swipe is located off the screen to the right, meaning I can't swipe to unlock!

Luckily, a second (IMO) bug let me work around the above issue: the notification bar is still visible and active, so I was able to drag it open, select an unread email, and it opened the gmail app. When I left it, I was back at the home screen, having bypassed the screen unlock.

There's something else I'll share: sometimes, when the screen is reactivated, the colo(u)rs are not right. It's like the green (or maybe blue) pixels aren't working at full strength - everything has a strange tint, and the screen is a bit grainy - not lower resolution, but less clear. Sorry I can't be more precise. If it's important, I can try to take a photo next time it happens.

Lastly, the GPS isn't getting a complete lock for some reason. I've used the GPS status app to reset the GPS, but that hasn't helped. Perhaps I just need to leave it outside for longer to get an initial lock, but it's certainly slower than it used to be.

I really love CM10 though. I use my headset with calls to avoid accidently muting or hanging up on the callers, and don't mind the occassional issues with wifi. It's so much smoother and now I know how to odex the system apps I have plenty of free space.

Keep up the good work!!!
[HTC ChaCha] ethancottier:
That's not a bug, it's a feature :) very handy one too!

I've had that too, also on CM9, just a quick screen off-screen on fixes it :)
[HTC ChaCha] adlx.xda:
cm-10-20121029-EXPERIMENTAL-chacha-ADLX-ALPHA0.zip

I'm uploading a new build right now. I haven't been able to test it, so I don't even know if it will flash and boot and work correctly. Beware.

I made it to test some scripts to reduce the size of the rom, removing some stuff. Maybe I removed too much, or I could remove more. It will be a question of adjusting ;).

Also the build is odexed now. LatinIME is now ~10 MB.

Link: REMOVED.

File size should be 123 MB, and md5 should be 1099fcb076e254295c831d09239cd698 .

If not, be patient, the build is probably still uploading!

EDIT: Link removed, there something wrong with the build, it wouldn't boot. I have to see why... :(
[HTC ChaCha] kronflux:
I was wondering why it wouldn't download xD

thanks for the update!

Hope you get it figured out soon! Good luck!
[HTC ChaCha] adlx.xda:
I believe I've just found the issue with the bootloop. Will probably upload a new build tomorrow.

EDIT: just a preview (no GApps installed)

Filesystem Size Used Free
/system 260M 237M 22M
/data 150M 10M [B]139M[/B]
/cache 35M 2M 32M
[HTC ChaCha] adlx.xda:
Uploading fixed (hopefully) build right now. Check the md5.

55eee2af338862dc36f9e7b871ca6fad cm-10-20121029-EXPERIMENTAL-chacha-ADLX-ALPHA0.zip
[HTC ChaCha] kronflux:
Flashing now! will post any bugs I find tomorrow after work :)
[HTC ChaCha] Nicois:
I flashed it an hour or so ago, and it seems to work well, except for an error popup saying gallery stopped working. I hadn't seen any such error with the earlier build.

Now I understand odexing a bit more, it's so frustrating to see so much wasted space in /data. I might try deleting the classes.dex from the /data/app apks too. Sure it means I can't safely just blow away the dalvik-cache, but it's a small price to pay.