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

I mean the downloading. With a 3MB cache you cannot download apps over 3MB. There are ways around this but not sure they are implemented as standard in CM or not.
 
flashed the rom yesterday and thought i found exactly what i'd been looking for. loved it until realised 3g isnt working. restarted the phone and phone app stoped working too!!!
help plz
new to rooting and custom roms, please help.
 
The ROM is very compact, and doesn't include the database of APN settings, needed for mobile data. So you have to set these by hand, or back up from previous ROM using an apn backup app then restore.

I'm sure there is discussion of this earlier in the thread - I'm using an app rather than browser so not so easy for me to search and link.
 
You could try installing tweakker from the play store. It should be able to set your APN correctly. You can then uninstall it to free up the space.

Aggi

Sent from my HTC Desire using Tapatalk 2 Beta-5
 
hi all and a very good evening to you.

I've had my Desire for ages (year and a half) and pretty recently took a big step (for a phone / linux noob) and rooted.

It didn't go smoothly but I got there in the end with stacks of help from a dude on the Revolutionary IRC (many thanks Dan0man, couldn't have done it without your intervention, just in case you are conceivably reading this thread).

I moved from the HTC 'official' gingerbread release:

BRAVO PVT3 SHIP S-ON
HBOOT-1.02.0001
MICROP-051d
TOUCH PANEL-SYMW0101
RADIO-5.17.05.23
Jul 22 2011, 16:19:16


via Revolutionary to:


BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYMW0101
RADIO-5.17.05.23
Aug 10 2012, 17:52:18

So... I've done heaps of reading, including all 33 pages of this thread and think I've got an idea of what's going on.

I am aware that this ROM is bare-bones, so have tried to prepare myself for a non-SENSE, minimalist experience :)

However, I'd be very grateful for any tips / headsups, people could offer me.

I'm afraid this post is a bit stream of consciousness, so might not be too coherent... but what launcher, if any, does dGB use?

Also, I read, on this page and elsewhere about the size of cache and it impacting on the installation of large apps, games, etc. Is there some trickery, which dGB uses to circumvent this issue?

What about recovery? I've got whichever version of CWM that came with Revolutionary 4.0.1.4 but I think I read SURoot talking about another, which was "infinitely better" (found it: "4EXT" post 1315 and below)

Talking of recovery, should I use recovery (e.g. CWM) to format system, cache & data? I'm pretty sure Rastaman advocates Fastboot (but perhaps he just can't function without the monochrome of a command prompt :p ) - I downloaded Fastboot Commander in preparation...

Ah... also... I checked the MD5 for the 65MB HBOOT file but couldn't see the MD5 for the ROM, so haven't been able to validate that. Am I being blind?

Kernels: I believe one is packaged with the ROM. Presumably this is the recommended one? What would I be getting with the others ones? I think there are 4 on the dGB google sites page...

I also thought, as I've seen it recommended, to maybe do a half-way house and just install the ROM (without adjusting the HBOOT)? Any reason why not? I believe I can install the HBOOT later anyway (to fix the partitions)...

Oh yes... backing up. I did a nandroid backup after S-OFF and have literally just run as full a backup as possible using MyBackupPro (as that's the app I have). Is there a significant need to use Titanium? I was tempted to do a fresh install of all my apps anyway, to compliment my sparkly new ROM, so don't have a huge need to recover my existing apps from backup. I also don't know what crap may have been saved during the backup process...

Can't think of much else. Apologies if I've been too verbose.


All the best,

Gary
 
hi all and a very good evening to you.

I've had my Desire for ages (year and a half) and pretty recently took a big step (for a phone / linux noob) and rooted.

It didn't go smoothly but I got there in the end with stacks of help from a dude on the Revolutionary IRC (many thanks Dan0man, couldn't have done it without your intervention, just in case you are conceivably reading this thread).

I moved from the HTC 'official' gingerbread release:

BRAVO PVT3 SHIP S-ON
HBOOT-1.02.0001
MICROP-051d
TOUCH PANEL-SYMW0101
RADIO-5.17.05.23
Jul 22 2011, 16:19:16


via Revolutionary to:


BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYMW0101
RADIO-5.17.05.23
Aug 10 2012, 17:52:18

So... I've done heaps of reading, including all 33 pages of this thread and think I've got an idea of what's going on.

I am aware that this ROM is bare-bones, so have tried to prepare myself for a non-SENSE, minimalist experience :)

However, I'd be very grateful for any tips / headsups, people could offer me.

I'm afraid this post is a bit stream of consciousness, so might not be too coherent... but what launcher, if any, does dGB use?

Also, I read, on this page and elsewhere about the size of cache and it impacting on the installation of large apps, games, etc. Is there some trickery, which dGB uses to circumvent this issue?

What about recovery? I've got whichever version of CWM that came with Revolutionary 4.0.1.4 but I think I read SURoot talking about another, which was "infinitely better" (found it: "4EXT" post 1315 and below)

Talking of recovery, should I use recovery (e.g. CWM) to format system, cache & data? I'm pretty sure Rastaman advocates Fastboot (but perhaps he just can't function without the monochrome of a command prompt :p ) - I downloaded Fastboot Commander in preparation...

Ah... also... I checked the MD5 for the 65MB HBOOT file but couldn't see the MD5 for the ROM, so haven't been able to validate that. Am I being blind?

Kernels: I believe one is packaged with the ROM. Presumably this is the recommended one? What would I be getting with the others ones? I think there are 4 on the dGB google sites page...

I also thought, as I've seen it recommended, to maybe do a half-way house and just install the ROM (without adjusting the HBOOT)? Any reason why not? I believe I can install the HBOOT later anyway (to fix the partitions)...

Oh yes... backing up. I did a nandroid backup after S-OFF and have literally just run as full a backup as possible using MyBackupPro (as that's the app I have). Is there a significant need to use Titanium? I was tempted to do a fresh install of all my apps anyway, to compliment my sparkly new ROM, so don't have a huge need to recover my existing apps from backup. I also don't know what crap may have been saved during the backup process...

Can't think of much else. Apologies if I've been too verbose.


All the best,

Gary

I'll try to address in order. Apologies if I miss anything.

dGB uses by default, Launcher2 (the Standard Launcher from 2.1/2.2/2.3 Vanilla Android) Howeverr I recommend using Go Launcher.

dGB employs an expandable RAM disk to accommodate downloads. This means a virtual disk in RAM is created when a download starts and expands to a size that the app can fit in. Once the app is installed, the RAM disk is destoyed.

Yup, Use of 4EXT is hugely recommended

Rastaman generally uses fastboot to format as he likes to make his instrtuctions universal. AmonRA recovery does not have this option. Formatting with 4EXT would be fine for NAND memory (Not necessarily SD cards though).

Theres no Md5 for the ROM. Hboot flashes, if corrupt will brick your phone so these are provided as a precautionary measure. This isnt the case with ROMs so there just isn't one ;)

All roms are packaged with a kernel. The kernel is the beating heart. Nothing works without it. The packaged one IMHO is the best. The rest are variations (AXI, BFS etc). The packaged one is AXI CFS. Have a read of my kernel info thread (Via my signature) for the differences.

Try the ROM alone without hboot first as its easier to get out of. You mentioned bare-bones non-sense earlier. There are far fewer bones here than any other bare-bones non-sense ROM, so be aware its not to everyones tastes. I do usually recommend people try other AOSP ROMS before this as often "Wheres this function? Wheres that function?" is the same across all AOSP roms. And sometimes not. Its nice though, when people know what an AOSP rom is rather than just thinking I cut stuff out that I didnt :)

You dont NEED titanium. certainly not for this job. Sometimes its nice if you need to restore an entire load of apps and data as the data often doesn't carry over well in MB. But in Ti, that can be a problem too.

With My Backup, be careful not to restore contacts or calendars if these are google though as you'll end up with duplicates.

Hope this helps.
 
I'm afraid this post is a bit stream of consciousness, so might not be too coherent... but what launcher, if any, does dGB use?
Launcher2, which is the basic, stock GB launcher. But it's really there just so that you have a launcher when you first install (you will find it very hard to use a phone without a launcher!). Most people then install a launcher of their own choice.
Also, I read, on this page and elsewhere about the size of cache and it impacting on the installation of large apps, games, etc. Is there some trickery, which dGB uses to circumvent this issue?
Yes, there is (a temporary RAM disc IIRC). The cache isn't a problem.
What about recovery? I've got whichever version of CWM that came with Revolutionary 4.0.1.4 but I think I read SURoot talking about another, which was "infinitely better" (found it: "4EXT" post 1315 and below)
The most stable CWM for the Desire is 2.5.0.7. But a lot of us have moved to 4EXT Touch now, and I can strongly recommend it. Being S-Off it's easy for you to change - just install the 4EXT app, and let it flash the recovery. It can read nandroid backups made with CWM too.
Talking of recovery, should I use recovery (e.g. CWM) to format system, cache & data? I'm pretty sure Rastaman advocates Fastboot (but perhaps he just can't function without the monochrome of a command prompt :p ) - I downloaded Fastboot Commander in preparation...
If you need to format those, I'd usually do it from recovery. But I assume you're specifically referring to the recipe for changing hboot, in which case you would be using fastboot commands anyway, and it will be easier that way.

I don't know Fastboot Commander myself - command line for me too ;)
Ah... also... I checked the MD5 for the 65MB HBOOT file but couldn't see the MD5 for the ROM, so haven't been able to validate that. Am I being blind?
Probably not. It's a lot less critical for a ROM than a hboot. Bad ROM download, just download and flash again. Flash a bad hboot and you may lose the ability to flash anything else (i.e. a hard brick). So checking the integrity of the hboot is absolutely essential.
Kernels: I believe one is packaged with the ROM. Presumably this is the recommended one? What would I be getting with the others ones? I think there are 4 on the dGB google sites page...
I'd just stick with the one it comes with. Only think of flashing something else if you have a problem.
I also thought, as I've seen it recommended, to maybe do a half-way house and just install the ROM (without adjusting the HBOOT)? Any reason why not? I believe I can install the HBOOT later anyway (to fix the partitions)...
If you flash the ROM first then (a) you are only changing one thing at a time, rather than 2, and (b) if there is a problem with the ROM and you still have the original hboot you can just restore your nandroid (you did take a nandroid before flashing the ROM!). If you change hboot first you can't restore the nandroid without changing the hboot back, because no other ROM will fit.

So yeah, ROM first, check all OK, then take a new nandroid and change hboot.
Oh yes... backing up. I did a nandroid backup after S-OFF and have literally just run as full a backup as possible using MyBackupPro (as that's the app I have). Is there a significant need to use Titanium? I was tempted to do a fresh install of all my apps anyway, to compliment my sparkly new ROM, so don't have a huge need to recover my existing apps from backup. I also don't know what crap may have been saved during the backup process...
Most of us reckon Ti is a more fully-featured backup app for root users.

One thing that may be worth doing: install an APN backup app and back them up before flashing dGB, as you will need to reinstall your APNs afterwards.
Can't think of much else. Apologies if I've been too verbose.
Believe me, I can out-verbose you! :D :fight:

Edit: on the other hand, that does mean I'm often beaten in replying! ;)
 
I'll try to address in order. Apologies if I miss anything.

dGB uses by default, Launcher2 (the Standard Launcher from 2.1/2.2/2.3 Vanilla Android) Howeverr I recommend using Go Launcher.

dGB employs an expandable RAM disk to accommodate downloads. This means a virtual disk in RAM is created when a download starts and expands to a size that the app can fit in. Once the app is installed, the RAM disk is destoyed.

Yup, Use of 4EXT is hugely recommended

Rastaman generally uses fastboot to format as he likes to make his instrtuctions universal. AmonRA recovery does not have this option. Formatting with 4EXT would be fine for NAND memory (Not necessarily SD cards though).

Theres no Md5 for the ROM. Hboot flashes, if corrupt will brick your phone so these are provided as a precautionary measure. This isnt the case with ROMs so there just isn't one ;)

All roms are packaged with a kernel. The kernel is the beating heart. Nothing works without it. The packaged one IMHO is the best. The rest are variations (AXI, BFS etc). The packaged one is AXI CFS. Have a read of my kernel info thread (Via my signature) for the differences.

Try the ROM alone without hboot first as its easier to get out of. You mentioned bare-bones non-sense earlier. There are far fewer bones here than any other bare-bones non-sense ROM, so be aware its not to everyones tastes. I do usually recommend people try other AOSP ROMS before this as often "Wheres this function? Wheres that function?" is the same across all AOSP roms. And sometimes not. Its nice though, when people know what an AOSP rom is rather than just thinking I cut stuff out that I didnt :)

You dont NEED titanium. certainly not for this job. Sometimes its nice if you need to restore an entire load of apps and data as the data often doesn't carry over well in MB. But in Ti, that can be a problem too.

With My Backup, be careful not to restore contacts or calendars if these are google though as you'll end up with duplicates.

Hope this helps.

That's awesome SURoot... and such a quick reply too. Ty :)

Regarding changing Recovery software, I presumably would use Fastboot. However, for my test purposes, can I stick with CWM to install your ROM (just to keep things simple)?


You will need to atleast make a note of you APN details or use APN Back up as there are no APNs included in this ROM.
Thanks Nicka. Great tip. Reassuringly (for me) I made both a manual note of my APNs (cos for some reason they differ just slightly to O2's online ones).

Also, MyBackupPro now supports APN backup (however I've found supporting and working are 2 different things with MBP... annoyingly).

I've actually done some manual backing up too (copying APKs, etc, across), so should be able to install anything not picked up by MBP.


@Hadron.

Top reply mate and ty too for your insights :)

Launcher2, which is the basic, stock GB launcher. But it's really there just so that you have a launcher when you first install (you will find it very hard to use a phone without a launcher!). Most people then install a launcher of their own choice.
Unless this is departing from the thread too much, what launcher do you use?

The most stable CWM for the Desire is 2.5.0.7. But a lot of us have moved to 4EXT Touch now, and I can strongly recommend it. Being S-Off it's easy for you to change - just install the 4EXT app, and let it flash the recovery. It can read nandroid backups made with CWM too.
I think I'll stick with CWM (falling in line with your comment about 1 change at a time) but when you say install... actually, don't worry. Just did the easy (and non-lazy) thing and googled 4EXT installation. Simple when it's an APK. I did just wonder whether it might be a .zip that I had to run from recovery..

I don't know Fastboot Commander myself - command line for me too ;)
Can't remember where I found out about this - probably in a fastboot FAQ... but I found a recommendation for it. It's a command line interface for Fastboot anyway. So if you don't use it, what do you use instead?

So yeah, ROM first, check all OK, then take a new nandroid and change hboot.
In regard to reversing HBOOT (if for some bizarre reason I needed to leave dGB), I guess I could run Revolutionary again?


Cheers,

Gaz
 
To change hboot back you just do what you did to install the dGB one. Download the one you need from alpharev.nl and fastboot flash it.

I just use fastboot command line (i.e. the fastboot executable). I have heard of Fastboot Commander, just never used it (or Android Flasher, or any of these things).

And launchers, I also use Go at the moment (though I dislike the "more convenient" way of adding stuff to the home screens they introduced in the last update, so am using the previous version).
 
[looks sheepishly at his feet]

I decided to use Fastboot (so I could get used to it). I successfully used the erase command to wipe system, cache & userdata.

The problem I now have is how to actually install dGB.

I can use fastboot to do the boot.img but as the other items in the .zip are "system", "data" and "META-INF" (and all are folders), I've concluded I can't use Fastboot to apply them.

Should I put the dGB.zip over to my sdcard (e.g. using adb - again, just for the practice) and run the .zip from recovery?



Cheers,

G
 
Yes, you flash ROMs from recovery, not via fastboot.

Copy to sd, then in recovery select the install zip from SD option. You've already wiped everything, so no need to worry about that. I assume you have a nandroid, 'cos it's too late now if not ;). You can also mount the sd over usb when in recovery mode.

Do read the faqs linked from the All Things Root Guide sticky - I'm sure there must be a description of flashing a ROM in there.
 
Yes, you flash ROMs from recovery, not via fastboot.

Copy to sd, then in recovery select the install zip from SD option. You've already wiped everything, so no need to worry about that. I assume you have a nandroid, 'cos it's too late now if not ;). You can also mount the sd over usb when in recovery mode.

Do read the faqs linked from the All Things Root Guide sticky - I'm sure there must be a description of flashing a ROM in there.

ta mate and thanks for humouring me :)

I'd forgotten about that FAQ. Have bookmarked about a million root things but not that (and why can I not find a facepalm smilie when I need one?).

Oddly enough I've checked the sticky and can't see anything to talk you through flashing a ROM - I'd presume that there are normally installation instructions for each individual ROM, rather than a generic statement.

Anyhoooo... yep I did do a nandroid before going crazy with fastboot. Will now endeavour to get to grips with adb, then flash via CWM.

Thanks again for the help. Next time we speak, I'll hopefully have some good news


Cheers man

G
 
ha. Magpie!

might have to take my pretty thing to bed with me... just to protect it and stare at it :)

love the way you get the tv turning off effect, when you turn the display off (ahhhhhh... pretty)

Houston, we have wireless and market access.

did make one booboo though - remembered to back up lots of apks, notification samples, etc, but didn't take my default music player :(

ty SUroot for this.


G
 
hi all

Am still playing with dGB but the magpie thrill has lessened a bit, since I had to 'dirty' the home screen with shortcuts. It almost feels wrong to put anything on it!

Have had a few probs post-installation but have conquered most I think. The biggest issue was HTC Sync not working (I sync with Outlook on my home PC) but I've managed to virtually substitute it with MyPhoneExplorer, although there are issues with that too (sadly). A magnificent program otherwise, especially considering it's freeware.

Anyway, currently, I need to sort out the default compact QWERTY keyboard cos I keep mis-hitting keys (inaccurate typing / little keys, rather than sausage fingers ;) ) and the spellcheck is pants.

I am a bit biased though cos I actually really like the HTC keyboard I previously had. I guess I'll get used to a different kb, in time...

Any suggestions?

I've done some research and have heard good things about:

- swype
- slide IT (trial)
- smart keyboard (trial)
- HTC IME mod

The only problem with the HTC IME mod is that the filehost for the links on SUroot's Useful downloads page (http://androidforums.com/desire-all-things-root/334444-index-useful-downloads-root-users-updated-22nd-july-2011-a.html) has been down for a while, so I can't grab it.

Personally, I like the T9 keypad (I've always used that in portrait, so moving to compact QWERTY is 'an experience'). Landscape kbs are surprisingly ok, as the buttons are bigger and I find the word suggestion and correction better... but I just like holding my phone in portrait when doing texts... and T9 predictive texting is still the biz, as far as I'm concerned.

[6 hours have passed seen I typed the above]

I've been experimenting with Go Keyboard, which seems pretty good, although I think I might have found a bug in it - either that or I simply don't understand some of the typing logic. For some reason, if you choose a symbol (via SYM), after having typed a word, the symbol gets inserted infront of said word i.e. keystroke sequence seems to be ignored, which makes it a real challenge to put punctuation after a word. I've found a way round this but it just seems illogical. Also, having come from the HTC sense keyboard, it's maddening that the SHIFT/CAPS key is where the DEL key used to be. You have noooooooooo idea how many times I've just selected initials instead of deleting a character lol. Autospacing seems to act weirdly too... and don't even get me started on the ENTER key - it simply doesn't seem to apply the ENTER action on the highlighted word (it always takes the first in the word list, which is normally a set of numbers).

Anyway... I digress from the general pleasure I've been having using the new ROM. I actually genuinely like the minimalist interface (hence my initial comment about spoiling it / cluttering it up with shortcuts). On some superficial levels, it's just like a different theme but it just feels 'nice'. I've only been doing basic things with it - making phonecalls, texts, a bit of browsing. I've configured the music player but haven't actually used it yet.

I've found 3 or 4 things that I don't understand though - I don't know whether they are to do with the ROM, the OS or me:

* when you autorotate to landscape in calendar, the event title disappears. It reappears in portrait.

* battery stats were appearing to reset themselves on reboot (but that's stopped now).

* I simply can't get the lockscreen settings / timeouts to behave as anticipated. I'm using them in conjunction with PIN lock. Basically, the lock screen and PIN lock kick in virtually immediately the displays times out or is turned off. In some respects, this is very secure but not as I was anticipating it functioning.

As a separate issue, initially, I was concerned a bit about battery consumption but know my battery isn't perfect (since I can't get it to a changing point where it gets to 0 mA, which I understand means the battery's knackered... although the phone does decide the battery's at full capacity, so it can't be too cr@p). Also, my phone consistently burns juice with the display on, even when the display is relatively low.

I think I've noticed some ROM efficiencies though! I reckon the CPU throttles down? I concluded that because I could see the mA consumption fluctuating / generally dropping more during inactivity / lower usage levels than it did on the stock 2.3.3 ROM. Here are some quick stats, if people are interested:

* I'm down to 49% and the phone's been on for 9hr 2m 18s
* Display - 77% - time on 3h 54m 40s
* Go keyboard - 6% - CPU tot 19m 24s; CPU for 9m 32s
* Cell standby - 5% - time on 9h 2m 18s
* WiFi - 4% - running for 4h 50m 42s; CPU tot 7s
* Phone idle - 3% - 5h 7m 37s
* Market - 3% - CPU tot 7m 18s; CPU for 7m 15s; Awake 1s
* Android OS - 2% - CPU tot 3m 50s

Reflecting on the above, I'm pleased with the display stats. However, Brightness is on minimum and I'd not be able to get away with that outside. :( I've been doing a fair amount of playing with the keyboard and been using Market reasonably too (to browse for keyboards / reading app reviews, etc) and WiFi's been on all the time.

Equally well, I don't reckon I've been hammering the phone. I made a few phonecalls earlier, etc, but fully charged phone afterwards + haven't been doing anything taxing like watching movies, YouTube, etc.

I'm still pretty pleased though. I like the fact I want to experiment with my handset again, rather than just use it. No force-closes either. A few occasions I've had blank screens and dialogues popping up asking whether I want to wait or force-close. I've realised / presumed apps are busy doing things though, so have had patience. For example, when I was first browsing a conversation thread on my restored SMS, I had a blank screen for a while + the aforementioned dialogue but chose wait then just used the back key. When I went back in again, the thread was visible.

All in all, I'm really enjoying dGB, so ty once again SUroot for the huge amount of work you must have invested in developing the ROM :) :) :)

I might even do the HBOOT soon, to get the full data partition. I'm just thinking I might flash back my old nandroid, so I can recover my user dictionary, which MyBackupPro appeared not to restore properly (or backup in the first place).

Lol... that brings me onto the performance (or lack of it) of MBP - it decided it wanted to restore something like 3500 APNs, when I only had 2 on my old ROM. This was another situation where I got a black screen and an eventual force-close or wait dialogue, when I wanted to review the restored APNs... only to find there were only around 8 in there. The SMS restore took ages too, although all the data seemed to come back, although there was some kind of sorting order issue in the SMS client, which eventually resulted in me exporting all the SMS from MyPhoneExplorer (which had imported them perfectly, implying all the data was sound, along with the date/time stamps), converting them, deleting the store from the phone client, then reimporting via an app called SMS backup and restore, which seemed to get the time-stamps correct on the conversation threads.

I must admit I've found MBP to be fine with restoring SMS previously (on my Sense ROM), along with call-logs, etc... but I'm not going to bother trying the saved apps & data - I think clean app installs from Market for my lovely new ROM :)

I also might experiment with Titanium...

Anyhow, it's 5am and time for bed. I hope the dGB community are all keeping well. Take it easy all.


G
 
OK, you may have out-verbosed me this time! :)

Just a couple of comments:

* I have copies of the HTC IME. I'll let you know how to get them via PM. I've never used Go Keyboard, so can't comment on that (I'm currently using SwiftKey 3 beta).

* Even on minimum brightness, 4 hours screen on and 51% battery used is remarkably good!

* Re lockscreens, there are 2 settings in Lockscreen settings -> Delay and timeout. I have mine set to enable the security lock immediately if I turn the screen off, but after a short delay if it times out. I just checked with PIN (I normally use pattern) and it works fine for me.
 
Back
Top Bottom