• 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]

SUroot said:
I did but only because I was moving a large app from sd that took me below the limit. My limit is actually 37MB. This is because the limit is 10%.

I can turn the alert off from 10% to 2% (easy in terminal( but that doesn't help apps. It should help message (sms and email) that would also get blocked at that threshold
Click to expand...

I guess that makes very much sense given the Linux roots of Android. ext-X filesystems always by default reserve a % of storagespace for admin purposes, among other things so some userapp can't block necessary admin access & management of the drive. But 10% seems like a really high default. Guess it could make sense given the disproportionately small default data-size of a Desire, but figuring out how to change this % to a lower value system wide would be interesting.

Traditionally on Linux the space reserving is done during formating of the partition.
"mke2fs -m 5" e.g. would give (the default of) 5% reserved space for admin use when partitioning a drive.
 
Hi,

I have orded mugen 3200 mah extended battery for desire. And will be getting in 1 week. I 'm currently running this rom with kernal that came with it. Do i need to flash any kernal patch to make the mugen battery work as it should or will it work fine with the current kernal?

thanks
 
SUroot said:
Yes. You can change the threshold for the warning in terminal:

Code: 
sqlite3 /data/data/com.android.providers.settings/database/settings.db

insert into secure (name, value) VALUES('sys_storage_threshold_percentage','2');
Will give you a 2% warning. It will only affect messages however. App moves / installs are still blocked at 10%
Click to expand...


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!
 

Attachments

The battery may not be much better.
Click to expand...

Do you mean it's not worth it? I have read reviews across many driod forums. Mugen extended batteries have more positive reviews.

I had already tried the Battery calibrator app. It was working fine on my previous stock n other custom roms i had flashed. But it doesn't work on your rom (No values shown). Maybe because of incompatible kernal?

But the htc official trick works :

Charging the phone switched on for 8 hrs or more
Switch Off charge it for 1 hr
Switch on n leave it for 2 minutes
Switch off n charge it for 1 hr

This trick improved the battery by 50% +++. Tried it on my old stock battery and the new stock battery i recently bought.

I 'm getting 1 day with new stock battery with moderate usage. Maybe just finished 2 recharging cycles. Read that it will improve after 5th recharge cycle ...

Old stock battery - 12hrs+. It was giving 3hrs+. Before trying the above charging cycle trick ...

Now i have ordered 3200 mah mugen. I have 3 batteries now. :)
 
Kernel is compatible and works fine with Nexus One Battery Calibrator. I use it.

The "Official" HTC method was withdrawn and they no longer recommend that method as it is harmful to batteries.
 
I will try it again. But i believe that the battery calib is only helpful to stop shutdowns @ 15% &\or above. Does it really improve the battery life?

What's your opinion about mugen batteries?
 
I have never tried one, but have read about them. I'm really talking about the 1600mAh not the 3200, so I am wrong, it will probably give you much more life.

There was the whole battery boss thing about claimed capacities not being met and the 1600 mAh batteries from 3rd parties being often worse than OEM batteries of smaller capacity.

Google "Battery boss false capacity claims"

Battery calibration uses the mV to determine the ACTUAL shutdown of the battery and the ACTUAL full charge capacity. So its as useful as any other method, if not more. Nothing you do with an OEM battery will be increasing capacity. It will only be helping it on the way to reaching its full potential.
 
Got some pretty surreal battery life in the last 24Hours. Was having a look at Teppics 2.3 ROM then got bored and restored my nandroid of DGB. Now for about the first half an hour of usage (me actually using the phone rather than it being just turned on) the battery didn't drop a single % (it started on 100%). It then dropped a lot slower than normal and I realised something was going on. The phone has lasted 23Hours with just about 3 hours screen on time which is vastly better than what I normally get. About 13-15hours with 2hours screen on time. The phone got to about 33% this afternoon and then died which I was expecting seeing as I'd had a much longer time on. I'll attach a few screenshots with battery graph etc. As you can see just at the end of the graph the sudden drop where it dies. Any idea how this has happened?

screenshot-1335018516464.png

screenshot-1335018581657.png

screenshot-1335018201011.png

screenshot-1335018251431.png
 
SmasherDK said:
It actually have the "n". I have just activated it, by pushing a file.
And I changed my router from g/n mixed to just n. And it's working :D

xda-developers - View Single Post - [KERNEL] data streaming/VOIP in standby, wifi module for HTC's OTA 2.6.35.10 kernel
Click to expand...

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!
 
SUroot said:
It's also in system/lib/modules/drivers/net/wireless. Both need to be the same
Click to expand...

Is that mean I should change the "bcm4329.ko" into the following 2 folders?

- \system\lib\modules\bcm4329.ko
- \system\lib\modules\2.6.35.13-dGB-2.1-EViollet-GB-HAVS-AXI-128-CFS\kernel\drivers\net\wireless\bcm4329\bcm4329.ko

I did, but still showing ERROR, strange!

or i should create these non-existing folders to place the file
- \system\lib\modules\drivers\net\wireless\bcm4329.ko
 
To be honest its part of the kernel so surprised it works at all. All I can say is that file is in two locations and must match
 
Hey Dan.
Sort of related, and it probably belongs in the root Ascend forums, but if you opt for the Ascend like you're planning, will you be developing a diminutive ics ROM?

Hope the Ascend is easy to root, and your answer is yes. I love this ROM on old faithful.

Andy
 
I'm not sure. The Diminutive was mainly an answer to the small memory space. Also the Ascend D looks like it will be almost pure so not much would be needed.

However, that said things like reboot power menu and notification widgets if not present may need to be added.

I'll probably root and be content for a month or two, but I will likely get to the point quite early on where I want to compile something.

Problem is, I'm not sure how to be the first developer on the scene. I'm not that sure how to go about getting component drivers working in android yet.

But we'll see. I'm certainly not going to the device without the intention of doing something at least.
 
I have a unique problem. When on calls the screen goes off & won't wake even I press the wake button and\or power button. I have to take the battery out and reset to bring back the screen. It only happens when i'm on calls. Evn after the call ends the screen stays off. I have no other problems with the phone. I didn't do any major changes in the settings since the day i flashed dgb rom.

What could be problem?
 
akhilesh rao said:
I have a unique problem. When on calls the screen goes off & won't wake even I press the wake button and\or power button. I have to take the battery out and reset to bring back the screen. It only happens when i'm on calls. Evn after the call ends the screen stays off. I have no other problems with the phone. I didn't do any major changes in the settings since the day i flashed dgb rom.

What could be problem?
Click to expand...

Set screen time out to 30.

Can you test, put desire on flat surface. Make call, still on surfaced. Does screen go off instantly? Does it go off at 30 seconds? If the latter, does it come back on?
 
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 ...
 
You must log in or register to reply here.
Back
Top Bottom