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

Root [ROM][AOSP]dGB v01_28_2012| 2.3.5| 375MB /data| 60MB /system |Mult-lang |Unlock |Reboot[28 Jan]

akhilesh rao said:
On flat surface track ball works fine. On palm sometimes it doesn't. Screen stays off evn i press Track ball or power button or track ball + power button combo.

Yes screen goes off instantly when i press the call button. If i use track ball it stays on for 30s n goes off again.

Is it possible to map the screen wakeup key from track ball to any other hardware key. I nvr used search hard key. If i could map the screen wakeup option to that key. I think that would fix my problem ...
Click to expand...

Sorry, to confirm, flat surface, make call, no touch, screen instantly off?
 
OK, I had been trying the MIUI rom, but was really unimpressed with the battery life, so thought I'd give this one a look!!

I've flashed it, but there isn't many apps on it... I've seen the page that says I have to drop them into 'places'... but I can't find these places to drop them!!!

For some reason, Titanium backup won't let me access my previous back ups on the SD card!!!

All i'm after with a new Rom, with good battery life and decent features!

What can anyone recommend - or how do I install these on this?
 
Titanium backup won't let me access my previous backups!

So I cannot restore anything from before!
 
Yes you said. Not a Rom issue so can't help there. Maybe re install titanium? Check your sd card?

I'm asking what apps are you talking about 'dropping places"
 
Ok.

The apks, put them on your sd card and browse there with a file manager. When you press the apk, it should give you an option to install it or to open it with package installer

/system is within the Rom, once installed, not on sd card, if that's what you thought.

However you can actually put Ringtones etc in folders called Ringtones, notifications, alarms and they will appear in the menus. UI sounds will need to be in /system though. Root explorer or es with root exploring capability required.

Font? Unless you read a lot of Chinese, Japanese stuff, you could probably do with out
 
Thanks SU.

I've ran quick system info and there is no a2SD on there (but there should be...), but I have tried running the Darktremor Apps2SD script, but the phone just hangs on the HTC startup screen!

Cause of this, I can move my apps to SD so have the old memory issues!

Any ideas?
 
dGB isn't an A2SD+ ROM - you need to install a new HBOOT or repartition the MTD to get the benefits of it. It is only 60MB so your system partition can be reduced from 250MB to 60 - that freed-up memory can be used for Apps. You can also use standard Android A2SD (i.e. move the bits of the app the app-designer has designated as moveable).

This repartitioning is not trivial, do a lot of reading before you attempt it.
 
Griff_LI said:
dGB isn't an A2SD+ ROM - you need to install a new HBOOT or repartition the MTD to get the benefits of it. It is only 60MB so your system partition can be reduced from 250MB to 60 - that freed-up memory can be used for Apps. You can also use standard Android A2SD (i.e. move the bits of the app the app-designer has designated as moveable).

This repartitioning is not trivial, do a lot of reading before you attempt it.
Click to expand...


That would explain it then... :)

Would I use GParted to reduce the system partition?
 
Dibs said:
That would explain it then... :)

Would I use GParted to reduce the system partition?
Click to expand...

No this is nothing to do with sd card partitioning, more advanced modifications are required. Suggest you read this then read it again for good measure so you understand what's involved - will benefit you in long run. While you're there no harm reading (or re-reading) all the faqs and relevant guides on the ATR sticky ;)
 
After having my unbranded Desire for nearly 2 years i thought it was time to root, S-OFF and install a custom ROM.

Can't believe i didnt do this before!!

So I now have dGB but want to maximise my app space.

So is it just a case of putting on the 60 or 65 dGB HBOOT using fastboot to resize the partitions?

SURoot-awesome tiny ROM by the way, cheers
 
Yes, it is just a matter of changing hboot. But do read the procedure and follow all steps. See the root memory faq or alpharev website for the method.
 
all done, very simple when i got the right syntax (kept typing recovery instead of hboot LOL)

loads of room for apps now, the one thing that has been annoying me for the last 12 months!!
 
pkrboo said:
After having my unbranded Desire for nearly 2 years i thought it was time to root, S-OFF and install a custom ROM.

Can't believe i didnt do this before!!
Click to expand...

But dGB wasn't released that long ago. :D

pkrboo said:
So I now have dGB but want to maximise my app space.

So is it just a case of putting on the 60 or 65 dGB HBOOT using fastboot to resize the partitions?

SURoot-awesome tiny ROM by the way, cheers
Click to expand...

The 65MB hboot let's you put the DroidSansFallback.ttf and some audio effects file. If you don't plan on using those, you can have +5MB for apps with the 60MB. :D
 
Actually you can symlink the font anyway.

Put font.ttf (font.ttf for simplicity here) in /data/local/fonts for example

So then, in terminal:

ln -s /data/local/fonts/font.ttf /system/fonts/font.ttf

That creates a shortcut where the font should be to where it actually is.
 
declan1 said:
So happy to know that finally have a solution for the Wifi-N mode.

I did tried to unzip & put the "bcm4329.ko" into "'system/lib/modules/", set the permission into "rr-r-r". However, after restarting my Desire, I only get "ERROR" when I enable the Wifi.

I also tried changing the "bcm4329.ko" file in ROM file (dGB_01_28_2012_eng.zip) on computer and then flash it into my Desire, but I get the same error.

I know some of you here do install the N-fix successfully, may I know the correct method for installing this N-mode fix?

Thanks so much!
Click to expand...

In general on Linux, for a module to work it NEEDS to be compiled for that specific kernel. This is deliberate, as changes in the kernel might potentially make different versions incompatible, so due to "better safe than sorry" mentality mismatching module/kernel-versions refuse to load. There are some exceptions, but in most cases you can assume you can not just pick a module.ko intended for one kernel and run it on another.

suroot said:
It's also in system/lib/modules/drivers/net/wireless. Both need to be the same
Click to expand...

Is it actually there twice or just symlinked?
 
SUroot said:
Alright, dGB users ONLY - I have located the hardcoded limit of 10% and removed it completely.

Here you can see me at 1.54MB space remaining. With the 2% warning limit mentioned earlier:

screenshot-1334962137830.png


So I have setup my Ubuntu 12.04 Beta 2 as a build environment and copied my repo backup back to the machine. Although I wont be compiling full ROM releases for dGB, I though since dGB is all about NAND space, learning the limit is % based called for adjustment.

So, I have recompiled the DefaultContainerService.apk from the dGB source (Cannot say for sure but would expect this to be incompatible with other ROMs). All you need to do is to delete the existing /system/app/DefaultContainerService.apk using root explorer (or alternative) and replace it with the attached version...

(Edit > And reboot)

This Removes the hard Limit so you have to manage this yourself. What would happen if the NAND fills whilst installing / Moving an app could be bad. Your Risk!
Click to expand...

Ah, really great. :)

However, I wonder if it wouldn't be a good idea to leave in at least 1-2% reserved space? I've used 0% on desktops, but only for partitions with mp3, h264 & similar files, not more vital partitions. For sure 0% on the desire would cause risk of dataloss (eg, incoming SMS/MMS doesn't fit?) and in worst case it might be problematic also to recover from a "full disk" issue without a PC with devtools installed nearby.

Eg a 1,5% reserved storage space and a warning if free space drops lower than 1%, could really be a good compromise between maximizing storage space but still leaving some margin.
 
It's there twice. Originally it was symlinked but it stopped working like that.

In regards to % the syntax was something like 0,1. For 10% I couldn't ascertain the correct syntax for 2% which would have been preferable.
 
hi SUroot, i want to know about your minimum size for cache partition.
in my calculation your rom seting are 60MB system and 375MB data, so the cache is only 2MB (desire only have 437MB usable space). is it correct?
i try 3MB cache with CM7 and i always unable to authenticate with google account or download from google play store. right now i'm using 5MB cache.
could you share your trick to use small cache partition? ;)
 
The hboots all have 5MB cache. I'm using 65 system, 5 cache giving 368 /data.

You can squeeze a couple of extra MB with a custom mtd. If I recall correctly SUroot found 3MB cache to be the smallest that works, which is where the number in the thread title comes from.
 
I only mean with this ROM. I cannot remember how CM7 gets around the small cache partition, even if it does by default at all.
 
You must log in or register to reply here.
Back
Top Bottom