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

Gazza!

I really enjoy reading your posts. You really do outverbose Hadron by far :what: which I wasn't sure anyone could do :D

But it is very well written, and well structured, something not everyone seems to care about (Hadron is one of the most notable exceptions to this statement).

Regarding keyboard, I highly recommend SwiftKey X which is available in Play. I am also running a beta SwiftKey 3 right now, but I actually prefer the X. It has excellent predictions (if you allow it to learn from your texts), and good customization options.

Sms backup and restore is my choice, hands down, along with the same guys apps for backing up APNs and call logs.
 
My god. You really have beaten hadron, lol
I definitely +1 for SwiftKey and SMS backup and the apn, never had any problems with any of them.
Glad your enjoying dgb, IMHO the best rom I've tried!
I've never used MBP, but i can vouch for titanium,
I'm sure you have many many more hours to play before its just how you want!
And then after a few weeks you will start again! :D
And by the way those battery stats are better than any ive had! I'm lucky if I manage 3 hrs screen on before it dies.
 
I use the HTC keyboard. Beats them all hands down for me. Will be taking it to my next device too.

Only upto android 2.2 did battery stats (stupidly) reset at reboot. Now, they reset after being on charge for a while, like it always should have done. That's much more meaningful
 
Hi all

Thank you all for the charitable (and helpful) replies :)

Was slightly concerned about my waffle being too waffly... but I appear to have got away with it (this time).

Am gonna try the HTC IME mod (ta Hadron).

However, am naturally also tempted by Swift Key, as discerning users have recommended it. ;)

Lockscreeens, etc

I'm definitely not clear on them. To my mind, there are 2 'layers' of lockscreen (or at least there were on my old ROM):

* A lock screen which you slide or rotate to unlock.
* A 2nd lock screen that requires a PIN, pattern or password to unlock.

On my old ROM, I could control when the PIN driven one became active - as far as I know a slide lockscreen is active as soon as the screen is inactive (but perhaps that was configurable too and I just had it coming on straight away... just can't remember).

Anyway, on dGB, I presumed the configuration in "lockscreens" \ "delay and timeout" would define the behaviour of the lockscreens.

This also has to work in tandem with whatever display timeout settings have been configured (mine's set to 1 minute).

So... this is what I've set up to test the functionality:

Under "Location & Security" - I had removed my PIN security, setting "change screen unlock" to "none" (so I could be methodical & monitor the behaviour of one thing at a time). HOWEVER, since this greyed out my slide lock options in "Lockscreen" \ "delay and timeout" (somewhat unexpected, given I'd changed security lock, rather than slide lock), I reinstated PIN security.

So:

"Location & Security" \ "change screen unlock" = PIN

"Lockscreen" \ "style options" \ "lockscreen style" = "rotary"

"Lockscreen" \ "style options" \ "Incoming call style" = "sliding tab"

[I've also made the custom app starter active but am not expecting that to affect matters (I thought I'd have the camera easily accessible).]

Btw, could someone explain the difference between the "security lock" and "slide lock"? They sound self explanatory but I'm not clear why the slide lock becomes greyed out when I've not had PIN lock set...

Anyway, I've got the following going on in "delay and timeout":

security lock screen timeout delay & screen turned off delay are both set to 10 mins.

AND

slide lock delay is enabled.

slide lock screen timeout delay and screen turned off delay are both 1 min.

I'd have expected this to mean the slide lock becomes active after 1 min of the screen going off and the PIN 9 mins after that (so you're not having to input your PIN, every time the screen's off).

However, this is simply not the case. If I turn the display off and then on again, both screenlock and PINlock are both active. I've even tried rebooting the phone after configuring the locks, to no avail. I've also tried reversing the timeouts i.e. that which was 1m is now 10m and vice versa. No impact.

I expect I'm just misunderstanding something but it's not what I was expecting to happen (and software should do what I tell it to do, not what it wants to do
fight.gif
) lol grrr


G
 
PS I just reflected on what was happening and it's almost as if my config is not being saved. Obviously other settings are taking hold (e.g. which type of screen lock I have, etc) but I just wondered if permissions could conceivably be blocking the writing of the screen lock delay config?

Sorry if this is dumb or configs aren't affected by file permissions. I'm not getting any error messages btw.
 
As I understand things, once you have activated screen lock security (such as PIN code) all other unlock options you've made are irrelevant, as the only thing happening is the PIN unlock.
 
hi all

Another noob question :o

Having used quickpic for a gallery app & to apply wallpaper (I'm pretty sure Rastaman recommended it), how do I restore the original wallpaper of the ROM?

I think it was simply black, so of course I could make a .jpg of the correct dimensions...

I've done some fiddling and established there's a wallpaper file that gets overwritten (in /data/data/com.android.settings/files/)... but having deleted that file (as a test to see if it forces the use of the 'default' image I was after), somehow the ROM has found another image to use, that's not located there - I've no idea where the image has come from (it's a lush lake with hills on the the horizon) but it's definitely not from my SDcard!



Cheers,

G
 
The problem is there is no image, so once you've gone from no image to image, that's it

well believe it or not I have a fix, which I've confirmed and reproduced.

I found an .xml file in /data/system (wallpaper_info.xml).

I initially tried to find the object named in it and failed, so just wondered what would happen if I commented the code line out.

I saved the file, rebooted the phone and lo and behold... my black default backdrop had returned.

I checked the file out again and found that it had been converted to a .bak (although the xml comment tags had been removed). A fresh file had been generated in its place.

The critical code that affects the wallpaper is the following:

component="android/com.android.internal.service.wallpaper.ImageWallpaper"

If this is deleted then one's wallpaper disappears on reboot (although the image still exists).

The 'clean' code of the new wallpaper_info.xml should read:

<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<wp width="960" height="800" name="" />

The 'dirty' code is:

<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<wp width="960" height="800" name="" component="android/com.android.internal.service.wallpaper.ImageWallpaper" />

I believe the component statement is introduced as soon as wallpaper is introduced, so deleting it returns things to their pre-wallpaper state.

Hope this helps people.


G

PS don't know if this is visible to others but for some reason I've got a space appearing in "ImageWallpaper". It's not there when editing but there after posting. This should not be the case! I've confirmed it's happening in FF, Chrome & IE9 (bizarre).
 
I've made a patcher to run dGB in desire cdma (bravoc). I tested for a while, the results are:

- voice and text message - ok
- evdo - ok
- keyboard - ok
- keypad lights - ok
- camera - working but landscape becoming portrait
- gps - not tested
- wireless - error (i test the dGB kernel with CM7 nightly, its working fine)
- auto rotation - error

I think the problem is in framework-res.apk. I don't know how to modify this stuff. If you want to try it, you can download the patcher from here.
Included in the patcher are kernel, modules, binary for bravoc. I took framework-res.apk from latest dGB. I also modify build.prop to work with bravoc.

Here the about screen.
2012-05-14%2014.23.04_resize.png
 
I've made a patcher to run dGB in desire cdma (bravoc). I tested for a while, the results are:

- voice and text message - ok
- evdo - ok
- keyboard - ok
- keypad lights - ok
- camera - working but landscape becoming portrait
- gps - not tested
- wireless - error (i test the dGB kernel with CM7 nightly, its working fine)
- auto rotation - error

I think the problem is in framework-res.apk. I don't know how to modify this stuff. If you want to try it, you can download the patcher from here.
Included in the patcher are kernel, modules, binary for bravoc. I took framework-res.apk from latest dGB. I also modify build.prop to work with bravoc.

Here the about screen.
2012-05-14%2014.23.04_resize.png

With your new cdma kernel, ensure both /system/lib/modules/bcm4329.ko AND /system/lib/modules/2.6.35.13-dGB-2.1-EViollet-GB-HAVS-AXI-128-CFS/kernel/drivers/net/wireless/Bcm4329/bcm4329.ko are the exact same file. Both need to be updated for wireless to work
 
With your new cdma kernel, ensure both /system/lib/modules/bcm4329.ko AND /system/lib/modules/2.6.35.13-dGB-2.1-EViollet-GB-HAVS-AXI-128-CFS/kernel/drivers/net/wireless/Bcm4329/bcm4329.ko are the exact same file. Both need to be updated for wireless to work

the path is correct. i flash dGB kernel into CM7 nigthly and the wireless module is working fine.
/system/lib/modules/bcm4329.ko is only symbolic link created by script 'mksymlinks.sh' in eviollet's kernel. i will check the updater-script.

dGB-modules.png
 
Actually symlink stopped working when I embedded the kernel in this Rom so I had to duplicate the file.

Edit

That said, it doesn't mean it will work if you do it but you have to at least test it because that was the only way embedding it would work
 
Any tips on improving sound / music quality on the HTC Desire?

I keep getting vexed listening to "Echoes, Silence..." (foo fighters) cos it makes my (relatively) expensive earbuds sound shite, yet playback through my PC sounds much better. Unfortunately, my PC lacks the portability of my Desire ;)

I'm using the stock music player.

Is it just a limitation of the Desire soundchip or what?


Cheers,

G
 
I use sennheiser ear buds with poweramp. Great sound quality. If you don't buy poweramp, you can't argue that you like sound ;)

Get the trial
 
I use sennheiser ear buds with poweramp. Great sound quality. If you don't buy poweramp, you can't argue that you like sound ;)

Get the trial

Thanks mate.

Does it really make that much difference? I don't really understand how software can 'influence' hardware output so significantly. I appreciate / vaguely understand about codecs and what they do but beyond that, unless PowerAmp uses custom (and awesome) codecs, I don't get how said app improves on one's sound experience.

Btw, if I need to use an equaliser, then there's a problem with the sound source in the first place (at least that's my belief - I like good, neutral sound).

My main audio experience is via Sennheiser headphones (open-backed). My surround sound speakers packed up literally years ago and I use these headphones all the time. Although they were designed for PC use, the sound quality genuinely seems great to me, particularly considering they were only
 
Well given that all the sound processing is done via software, is it hard to believe? This is digital audio processing via digital equipment so yeah, the player makes a huge difference. Ever compared windows media player quality to Winamp? Same thing. Just try it. The equaliser is great too
 
It will work. The battery may not be much better.

Just download the Nexus one battery calibrator from market.

Then follow:

Advanced Battery Calibration (tested and verified on Oxygen + bravoGSM (Page 1) / Tutorials, Guides and FAQs / Oxygen Forum

Just a heads up. I have performed this calibration many times. And every single time it has worked.... until the next charge cycle.
The calibration works, it'll discharge back to 0, but next time I charge up, it'll discharge to 13 then turn off. Then I have to do all over again. Tried various times on various ROMS, with the same results on all. Interestingly, I started off with phone turning off at 18. But the first 5 times I tried, the phone would turn off before telling me to plug in. Each time it did this, the next time I gave it a try, it would power off 1% lower. So I went from switch off at 18 to 17, 16, then 15, 14, and finally 13%.

Also, what do you use to move to SD? Simple2ext? The built in move to SD? I can't get close to 115 apps. Not by a long shot. Always run out of space before that.
 
Also, what do you use to move to SD? Simple2ext? The built in move to SD? I can't get close to 115 apps. Not by a long shot. Always run out of space before that.

Nothing, this is the dGB port SUroot did. As the title says it's only 60MB in size which means we get back 190MB of system partition (although you have to re-partition which is non-trivial). I currently have around 75 apps installed and 163MB free (yes, more space free than a Desire with no apps on it). You don't have to worry about A2SD+, the built-in still works.
 
Thanks mate.

Does it really make that much difference? I don't really understand how software can 'influence' hardware output so significantly. I appreciate / vaguely understand about codecs and what they do but beyond that, unless PowerAmp uses custom (and awesome) codecs, I don't get how said app improves on one's sound experience.

Btw, if I need to use an equaliser, then there's a problem with the sound source in the first place (at least that's my belief - I like good, neutral sound).

My main audio experience is via Sennheiser headphones (open-backed). My surround sound speakers packed up literally years ago and I use these headphones all the time. Although they were designed for PC use, the sound quality genuinely seems great to me, particularly considering they were only
 
Nothing, this is the dGB port SUroot did. As the title says it's only 60MB in size which means we get back 190MB of system partition (although you have to re-partition which is non-trivial). I currently have around 75 apps installed and 163MB free (yes, more space free than a Desire with no apps on it). You don't have to worry about A2SD+, the built-in still works.

I get that. But peeps are talking about moving to and from SD. As I am guessing the ROM doesn't do this "automagically", they must be moving things over manually. Just wanted to know what they were moving with.
 
hi dan,

your pm is full.

i recompile the dGB kernel without loadable module and wireless lan embedded into kernel image. i also put bcm4329.ko into /system/lib/modules and the path you mention before. i removed mksymlink.sh from updater-script.
flash the rom and then flash the patcher.

the results are:
- voice call ok
- text message ok
- mms not tested (my service provider didn't provide mms)
- gps ok (lock 12 satelites outdoor with 4m accuracy)
- camera ok (i'm using camera.apk from cm7 nightly)
- evdo/cdma1x ok
- wireless not ok (i'm using dgb and manu kernel)
- blank wallpaper
- auto-rotation not ok
- auto-brightnes not ok
- roaming indicator is always on (even when i choose home only and turn off data roaming)

i also capture the logcat.txt, do you want to see?
logcat.txt

thanks.
 
Back
Top Bottom