• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[ROM] aospCMod | AOSP 2.3.4 / CM7 (Gingerbread) [05/23/11]

Thanks, that actually works pretty well and has support for Korean!

Now for my ultimate troll question: How do I get Sense UI back onto the phone with the AOSP 9.9.2 rom?
 
Those are both not Sense Rom, they are senseless, if you want a sense Rom you can try Liquidsense 2.1, now if you are looking for sense like apps there are many out there, you can use Launcherpro for a launcher, you can also use Fancy Widget for a weather clock identical to the sense clock, anything else you need let us know

FYI I would also post at the XDA GB forum about your Korean support I am sure they should be supporting it, it is the same Dev.

screen



infinite012 said:
Thanks, that actually works pretty well and has support for Korean!

Now for my ultimate troll question: How do I get Sense UI back onto the phone with the AOSP 9.9.2 rom?
Click to expand...
 
hakujin said:
I'm already starting to 2nd guess my stance on firerat. I'm just getting tired of always having to copy stuff over to /system or move to SD. Problem w/ moving to /system is everytime there's an update, updates won't write to /system even if i mount it as r/w prior to. this is frustrating because then I have to do the same monotonous step over.

I just don't want any problems w/ it (and there have been people with serious problems). There are always different size settings posted, then the complication of market abnormalities (told resolved with latest), and again, when i reflash a ROM I have to reflash it all over right? I guess I'm partly a stalwart as well because I always go into this stuff 110% so I feel a lot of reading time coming on...

If I flast it on now top of (5/17) 2.3.4, will I have to wipe /system & /data? Any latest and greatest pointers and tips would be appreciated. Right now I'm below 30MB on /data and it pisses me off. davlik cache should go on somewhere, preferably to /system. that seems a given w/ the constraints of the partitions + how/where stuff is installed. Wonder why Goog doesn't see this as a better fit.:confused:
Click to expand...


I was in the same boat, then got tired of the low memory, so I just did a little research and tried it out and now I have double internal memory!

Yes, I did a full wipe for the initial mod, but after that all you have to do is make sure you flash the firat boot file every time you change something in the system or flash something from recovery. Here's the way I did it...

- create the txt file with your system and cache values. A safe starting point would be 100 18. That's what I'm using right now. I started using 85 18 but had troubles adding other mods because the system was set too low.

From recovery...

- nandroid backup.

- full wipe (data, cache, partitions, etc.)

- flash the firat recovery file (1.5.8).

- it will prompt you to partition data, cache, and system but not boot. I made the mistake of partitioning the boot the first go round and the mod didn't work, so don't partition the boot.

- flash your ROM and Gapps (if needed).

- flash the firat boot file (once again, you do this every time you change something in the system or when you flash through recovery).

- reboot and check your storage.

Whenever you want to change your system and cache values for larger or smaller ROMs, just go make the changes in the txt file, boot into recovery, nandroid, full wipe, flash the firat recovery file, partition all except boot, restore your nandroid, flash firat boot, reboot and all should be well. This goes for flashing themes and such as well. Any time you want to check and see just how much memory you're using just go into Terminal Emulator and type...

df -h

... and press enter.

I would definitely read through the firat thread a little, but it's really not that complicated once you get it right. I hope this helps. PM me if you need anything else ;)
 
I spent an afternoon and evening screwing with Firerat and could not get a stable install. I was using my last Nandroid to restore.
The next day I decided to try it on the latest AOSP Rom clean. That worked fine, then using TI Backup I reinstalled all the apps that Google didn't automatically install for me. The worst thing I had to do was re-log-on to some of my apps for name and pwd. But now it works great and my Hero seems faster than ever, since all the apps are on the phone and none on the SD card (I was even using a class 10 card). So my advice is get comfortable with Firerat and then just start fresh with a new ROM and avoid old Nandroids. Now how this will work when I switch to a Sense ROM for PRL updates and go back to my Firerat Nandroid....well we'll have to wait for that story. Specs:
RA 1.7 DarchDroid
Firerat MTD 120 18
AOSP 2.3.4 (5/23)
Firerat 1.58
Previous free memory (with many apps on the SD card) = 35 meg
After Firerat = (no apps on the SD card) = 128 meg
The only thing that didn't take so far is the circle battery update that I found -- but I never tested it natively.
 
I used the Modified Amon RA (RA 1.7 DarchDroid) listed in my note above with success too. However I used ADB for the reboot, which I really recommend anyway for swapping and trying out different recoveries until you find the one you like. I like Amon RA for the nice menu's and checks before you do something. Also it lets me boot Sense ROMS like the earlier CWM to update PRL.
 
Do you know how to make the Market work, or how to install the img. file?

I tried following this instructions:

Here is the s0be's fix

1. adb shell <---- what's this?
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download

Then the market should download

and

Hey, I got sick of applying the Market Fix every time so I made this batch file.

Save it in your adb folder then run with aospMF <---- what's this?

Download

But I don't know how to use that... =/,
 
Lozer_Kid said:
Do you know how to make the Market work, or how to install the img. file?

I tried following this instructions:

Here is the s0be's fix

1. adb shell <---- what's this?
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download

Then the market should download

and

Hey, I got sick of applying the Market Fix every time so I made this batch file.

Save it in your adb folder then run with aospMF <---- what's this?

Download

But I don't know how to use that... =/,
Click to expand...
If haven't gotten adb running yet (there's a few tutorials out there, i can post a link to one later when I'm at a computer if someone doesn't beat me to it), then I think youshould be able to run those commands from a terminal emulator.

Start at step 2, in the native terminal emulator
 
Lozer_Kid said:
Do you know how to make the Market work, or how to install the img. file?

I tried following this instructions:

Here is the s0be's fix

1. adb shell <---- what's this?
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download

Then the market should download

and

Hey, I got sick of applying the Market Fix every time so I made this batch file.

Save it in your adb folder then run with aospMF <---- what's this?

Download

But I don't know how to use that... =/,
Click to expand...
adb (Android Debug Bridge) allows you to run a terminal/command-line program from your computer, but the commands are sent/run on your phone. it's a more convenient way of getting powerful linux command-line tools on your phone. but there are terminal emulators that run on your phone. so try running the commands on your terminal emulator (like i suggested in my post above)

but here's the process for adb installation the finally got the drivers to work for me, for some reason i was having driver trouble following the steps from the google developer sites.
How To: Set Up ADB/USB Drivers for Android Devices | TheUnlockr

here's some more info on adb:
Android Debug Bridge | Android Developers
and
What Is ADB And How To Install It With Android SDK
 
Can someone tell me again the easiest way to get Sprint VVM to work on the latest ASOP Rom? I someone has the backup file or the backup apk could you send it to me, and I can restore in on my ROM? Would that work? Or do I have to create the backup myself?

Thanks!

Note. I have not installed the latest AOSP rom, but I plan to wipe all and flash tonight. Just want to be prepared.
 
mrtimo said:
Can someone tell me again the easiest way to get Sprint VVM to work on the latest ASOP Rom? I someone has the backup file or the backup apk could you send it to me, and I can restore in on my ROM? Would that work? Or do I have to create the backup myself?

Thanks!

Note. I have not installed the latest AOSP rom, but I plan to wipe all and flash tonight. Just want to be prepared.
Click to expand...

From what I've read I'm pretty sure there is no way to get visual voicemail to work. I just installed it and it didn't work for me.

Everyone uses Google voice or youmail. And sprint is soon going to integrate everyone to Google voice and do away with visual voicemail.
 
I suppose I exaggerated a little because I don't use them either. I just go old fashion and call my voicemail. But I know those are the to closest replacements.
 
Youmail worked fine for me with AOSP, but I have gone over to Google Voice since the Sprint integration. GV will also transcribe your voicemail for free.
 
yeah, I like google voice, the biggest pain is when you click to call someone back from google voice it automatically calls from google voice number... actually wait, no... just checked this is not the case. This is the case on google.com/voice

But, very very often when I am listening to a voice message it "pauses" and I have to click play again. Perhaps the message did not download all the way? a bit annoying.
 
Yes that happens to most of us also, but it is a minor glitch, it could be because it did not fully download yet, but it takes a sec to hit it again, but I was also a large Youmail fan and I also use GV now. I find it very convenient.

As for you calls you have the option for it to make all calls through GV, or calls that you want, or only international calls, so you can set it up the way you want.


mrtimo said:
yeah, I like google voice, the biggest pain is when you click to call someone back from google voice it automatically calls from google voice number... actually wait, no... just checked this is not the case. This is the case on google.com/voice

But, very very often when I am listening to a voice message it "pauses" and I have to click play again. Perhaps the message did not download all the way? a bit annoying.
Click to expand...
 
someone said that you could make a backup of vvm on an older ROM and than restore it once you had AOSP installed... this does not work anymore?
 
You can try, simply make a Nandroid and let us know, so far there has not been great success.


mrtimo said:
someone said that you could make a backup of vvm on an older ROM and than restore it once you had AOSP installed... this does not work anymore?
Click to expand...
 
For those using Firerat, what is your mtd setup? I used 110 5, but have seen people use larger caches and wasn't sure what that range was or benefits.

Also, does this ROM have quickoffice? Presently using a 'Deck'GB build over at XDA, but a bit annoyed that I don't have a working Quickoffice.

Thanks for keeping this thread going over here, super useful.
 
neely615 said:
For those using Firerat, what is your mtd setup? I used 110 5, but have seen people use larger caches and wasn't sure what that range was or benefits.

Also, does this ROM have quickoffice? Presently using a 'Deck'GB build over at XDA, but a bit annoyed that I don't have a working Quickoffice.

Thanks for keeping this thread going over here, super useful.
Click to expand...

I don't use firerat's but I have read that you need a cache between 15-20 for the market to work without applying sobe's fix. If you already do the fix each time then its not a big deal for you. But the market won't download if you cache is set lower than 15. Most recommend 18 as a safe setting. Hope that helps.
 
You could go as low a as 80 18 if you would like. 80 just doesn't leave much room for flashing other mods. That's why I use 100.
 
oOMavrikOo said:
I would definitely read through the firat thread a little, but it's really not that complicated once you get it right. I hope this helps. PM me if you need anything else ;)
Click to expand...
Thank you, I appreciate your effort and yes it doesn't seem that difficult.

I keep going back and forth though... as the low /data space serves as a reminder to tidy up and remove apps I don't really use anyway, so it has a bit of a positive benefit for me. On the other had, the cluster f--k of deciding what does on /system (only to be duplicated on /data when updated from the market), and what to move to SD gets a tad monotonous.

That said, I have one question. What do you mean by changing system requires reflash. You mean, if I say... copy/move/delete anything from /system/apps (as one example), I must reflash fire rat?

Also what do 80 and 18 individually represent... MB size of two partitions but which ones? And If I use 100 or 120 for the 1st, where is that space subtracting from?

Edit: I now glean the 2nd is CACHE partition? Is this partition viewable from Root Explorer? It helps to see it visually to put it in perspective. What size is it, by default? Lastly, still not certain what latter number is, but I'm guessing /data since that's really where we need space. 30MB borrowed from /system and it'd be perfect quite frankly.

I may end up doing this if I update ROM, but can't seem myself doing it otherwise. My eyes are on the anticipation of SGS2 at this point, even though my upgrade won't be until Dec! :D
 
You must log in or register to reply here.
Back
Top Bottom