yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
I'm quite sure USB drains vanished in my 2636 kernel tree.. and mobile data was not patched.. (now if I didn't gain a camera bug I could release a kernel)

Most of the drain be gone from what I can tell is:

https://github.com/ezterry/kernel-biff-testing/commit/fc5d7c2d1e3c4053f1bd1eb94c63344bffdd2891 + https://github.com/ezterry/kernel-biff-testing/commit/b95d121976171f36f74c1d0cb9d4bdbce0b1ffde

And and with the long lasting green screen gone:

Green screen (sapphire): https://github.com/ezterry/kernel-biff-testing/commit/16ec75063ffb10704a6efc10fa31ffd71aafc533

The potential of the kernel seems good assuming I can force camera to behave.

(I am having some issues with crashed camera battery drain.. if you are using the phone after a camera freeze)
[G1 Android Development] MattDrumz:
Thanks for your answer. I think I'll just stay on my current radio then. I'm not really having terrible battery life anyway. As long as my phone lasts throughout the day, I'm happy. I was just thinking about switching to the older one because some people said it was easier on the battery.

Thanks for all your work!
[G1 Android Development] farmatito:
Hi,

also remember to disable CONFIG_MSM_SERIAL in your configs and only let CONFIG_MSM_SERIAL_HS enabled.
[G1 Android Development] ezterry:
I'm still not sold on what result I ought to expect from that.. and I might need serial in debugging yet.

For that matter I'm not sold on why the adb change works (even if at least I can test its working) because the old version was in 2.6.34.y and didn't have the problem you fixed.
[G1 Android Development] farmatito:
May be an interaction with some other code of the android gadget or the msm72k_udc, otoh the last official code

from htc for the sapphire has the old code (and also the 2.6.35 htc code for vivo).

I don't think you will need MSM_SERIAL for a release

build, in a test or debug kernel I can understand it:

board-trout.c

#if defined(CONFIG_MSM_SERIAL_DEBUGGER)
if (!opt_disable_uart3)
msm_serial_debug_init(MSM_UART3_PHYS, INT_UART3,
&msm_device_uart3.dev, 1,
MSM_GPIO_TO_INT(86));
#endif

/* gpio_configure(108, IRQF_TRIGGER_LOW); */

/* put the AF VCM in powerdown mode to avoid noise */
gpio_set_value(TROUT_GPIO_VCM_PWDN, 1);
mdelay(100);

if (system_rev < 5) {
trout_x_axis.info.gpio = trout_4_x_axis_gpios;
trout_y_axis.info.gpio = trout_4_y_axis_gpios;
}

#ifdef CONFIG_SERIAL_MSM_HS
msm_device_uart_dm1.dev.platform_data = &msm_uart_dm1_pdata;
#endif

and

MACHINE_START(TROUT, "trout")
/* Maintainer: Brian Swetland <swetland@google.com> */
#ifdef CONFIG_MSM_DEBUG_UART
.phys_io = MSM_DEBUG_UART_PHYS,
.io_pg_offst = ((MSM_DEBUG_UART_BASE) >> 18) & 0xfffc,
#endif

board-sapphire.c

#if defined(CONFIG_MSM_SERIAL_DEBUGGER)
if (!opt_disable_uart3)
msm_serial_debug_init(MSM_UART3_PHYS, INT_UART3,
&msm_device_uart3.dev, 1,
MSM_GPIO_TO_INT(86));
#endif

/* gpio_configure(108, IRQF_TRIGGER_LOW); */

and

#ifdef CONFIG_MSM_DEBUG_UART
.phys_io = MSM_DEBUG_UART_PHYS,
.io_pg_offst = ((MSM_DEBUG_UART_BASE) >> 18) & 0xfffc,
#endif

devices_htc.c

#if 0
static struct platform_device *msm_serial_devices[] __initdata = {
&msm_device_uart1,
&msm_device_uart2,
&msm_device_uart3,
#ifdef CONFIG_SERIAL_MSM_HS
&msm_device_uart_dm1,
&msm_device_uart_dm2,
#endif
};

int __init msm_add_serial_devices(unsigned num)
{
if (num > MSM_SERIAL_NUM)
return -EINVAL;

return platform_device_register(msm_serial_devices[num]);
}
#endif

so unless you enable CONFIG_MSM_DEBUG_UART and

CONFIG_MSM_SERIAL_DEBUGGER i think CONFIG_MSM_SERIAL will only sit there and wake your

device with an

<6>[15203.628173] Wakeup IRQ 109 pending, suspend aborted
<6>[15203.629180] PM: early resume of devices complete after 0.243 msecs

preventing it to sleep correctly.
[G1 Android Development] ezterry:
IF I see evidence of such sleep problems on the 2636 kernel and related drain (and I might) yes I will want it to go away and may remove the component.

The Serial driver is just that the driver to the serial port (its hidden in the extended pins of the ext USB port)

To some its useful (besides JTAG robotics projects seem to be the largest user of the interface..as the dream makes a useful onboard computer to control the device.. or provide wireless communication back to a computer+human)

And its worth keeping about even if just for those uses.. of course any such robotics use will be fine loading a kernel module..
[G1 Android Development] mimox:
Can clockwork recovery be used instead of amon_ra in the original instructions on page 1?
[G1 Android Development] azrash:
not sure, but you can always try, refer this, it might help

http://xdaforums.com/showthread.php?p=13148255#post13148255

1. flash engineering spl or orange.nbh to get engineering spl

2. reboot bootloader

3. flash clockworkmod,

4. radio

5. spl

dont forget to a fastboot erase system -w and fastboot erase boot

if clockworkmod doesnt work, flash orange.nbh again, and repeat instruction in OP.

but i am not sure though, never tried it, but in theory it should work
[G1 Android Development] dhyqa:
Help me please

I want to flash this to my phone but when I want to to do that it keep saying error

Eventhough I already placed the file to the same folder with fastboot and I already checked my typing if by mistake I type it wrong

What should I do?

Sorry for my bad english
[G1 Android Development] johnson8cyl:
What error?

Sent from transparent xda app by theimpaler747
[G1 Android Development] dhyqa:
It keeps saying 'error cannot load' everytime I try to flash it

What should I do then? :(

Sorry for my bad english
[G1 Android Development] johnson8cyl:
Did u type in fastboot devices and get a serial number on the last line letting u know your in the right dir in the cmd prompt and it recognizes your phone? U did extract the zip file and put the individual files it the tools folder not the whole zip file right?

Sent from transparent xda app by theimpaler747
[G1 Android Development] dhyqa:
Yes

I do that at first to make sure my phone already connected to fastboot mode and it connected and I already extract the file and put it in the tools directory too but it still didn't work :(

Sorry for my bad english
[G1 Android Development] johnson8cyl:
What exactly did u type?

Sent from transparent xda app by theimpaler747
[G1 Android Development] dhyqa:
At first I try to flas recovery by typing this

fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img

And it saying error cannot load

I try it again and again but it still didn't work

And then I try to flash radio and I type

fastboot flash radio radio-2.22.27.8.img

And it also saying error cannot load :(

What should I do?

Sorry for my bad english
[G1 Android Development] azrash:
what is your current spl and radio? it should be stated at the phone's screen when you on it in fastboot mode.
[G1 Android Development] dhyqa:
This is the info I get when I enter fastboot

DREAM PVT 32B ENG S-OFF

HBOOT-1.33.2005 (DREA10000)

CPLD-4

RADIO-2.22.19.26I

Apr 20 2009,15:30:43

I hope that will help :(

Sorry for my bad english
[G1 Android Development] johnson8cyl:
U should be ready to go with no problems. I don't get it. Is there a file in your tools folder something like win.dll?

Sent from transparent xda app by theimpaler747
[G1 Android Development] hrk:
Are you really sure that you're running fastboot FROM the tools directory?

Where did you open the command prompt?

Why don't you provide the complete error message you get, by doing a complete copy/paste from the computer?

Are you so determined to hurt us by providing the same uncomplete informations? :(
[G1 Android Development] dhyqa:
yes

there's a file in the directory named 'AdbWinApi.dll'

is there something wrong with that? :(

i'm so sorry if what i do make you troubled :(

yes

i'm sure i'm runnig fastboot from tools directory

this is what i type and what i get when i want to flash that

C:\Documents and Setings\Lenovo>android\tools\fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
error: cannot load 'recovery-RA-dream-v1.7.0-cyan.img'

and then i try to flash the radio hopefully it will work but it's the same like the recovery

i get it like this

C:\Documents and Setings\Lenovo>android\tools\fastboot flash radio radio-2.22.27.08.img
error: cannot load 'radio-2.22.27.08.img'

and that's what i get :(

what should i do then?

sorry for my bad english
[G1 Android Development] Effdee:
try this

C:\Documents and Setings\Lenovo>android\tools\fastboot flash radio android\tools\radio-2.22.27.08.img

if that doesn't work

then move radio-2.22.27.08.img to C:\

and

C:\Documents and Setings\Lenovo>android\tools\fastboot flash radio C:\radio-2.22.27.08.img

or

cd android\tools

so you see

C:\Documents and Setings\Lenovo\android\tools>

and then

fastboot flash radio radio-2.22.27.08.img

all very simple
[G1 Android Development] hrk:
This is why I asked for more informations. You are NOT RUNNING FASTBOOT FROM TOOLS DIRECTORY :).

You are running fastboot from "Lenovo" directory. Change the commands the way Effdee suggested and the problem will go away.
[G1 Android Development] dhyqa:
it work!

so that's why i can do that

thank you for everyone who help me

and sorry if i trouble you so much :o

sorry for my bad english
[G1 Android Development] netw3rkd:
How do I get back to having s=off? I'm thinking I could install vold on cm 6.1. I don't notice the extra ram really and want full root.
[G1 Android Development] ezterry:
But what are you trying to do that you don't have "full root".

I think this idea that s=off is root is an indication you need to either a. Stay where you are or b. return to stock and don't re root until you read more.

Hint vold has nothing to do with s=on/s=off
[G1 Android Development] netw3rkd:
i realize that vold doesn't depend on s=on or off. i have a few apps namely root tools that needs s=on to run. I enjoy messing around with things because I can do so. I'll find what files I need to reflash, just figured you might be able to help. s=off isn't root, it just allows you to have r/w to the nand that the system is stored on. Again, I don't want to stay where I am. What is best for you or other's isn't best for me. thanks for your opinion anyways.
[G1 Android Development] azrash:
What exactly are you trying to do on your g1? you want to backup/restore apps using root tools? :)
[G1 Android Development] ezterry:
I think you are mistaking the Dream/Sapphire for a later more locked down device..

The only thing missing is fastboot access

You have full read-write access to system, recovery, boot, userdata, cache, misc, and if you pull some strings even hboot its self.

This means with 1.33.0013d you will have no problem formatting, and restoring images form recovery, and mounting and modifying in recovery.

this include using unyaffs to restore *.img of yaffs images, or flash_image for non filesystem partitions.

And again I recommend either unrooting or staying where you are until you read.. the OP post is a good place to start since you have not read all of it.. or at least comprehended what you read.

(And my real opinion is this: If you have an operation that really needs S=On you ought to be able to make it S=On with the information in the OP.. and return when/if the operation is done)
[G1 Android Development] azrash:
well said, he is using aria too, that might explain the confusion as well:p
[G1 Android Development] ThauExodus:
Splash Screen Question...

Hi,

I want to install a new splash screen.

I know that i must downgrade and after the flash of the splash upgrade again.

To downgrade.. which spl and radio should I use or can keep my radio-2.22.27.08?
[G1 Android Development] johnson8cyl:
Keep your radio. Just go back to engineering spl.

sent from my transparent xda app by the impaler747
[G1 Android Development] ThauExodus:
Which spl is the engineering spl?
[G1 Android Development] johnson8cyl:
I believe 2005 eng. spl is posted in the op

sent from my transparent xda app by the impaler747
[G1 Android Development] _DX_:
Ok guys, apparently I messed something up and I don't know what...

I followed the steps in the first post and everything went ok. I could flash everything without problems (I didn't flash the recovery since I was already on 1.7.0), only after the whole process I couldn't enter my recovery anymore.

So I did what was in the post and flashed the .NBH file, and started over. Again I flashed all the files, this time I flashed the recovery too. Everything went fine again, no errors. But again, no recovery. The third time, after flashing the .NBH again, I only flashed the recovery to see if it wasn't a bad combination with the SPL/radio. Still no recovery... I don't mind flashing everything again, but I'm starting to think that this is not going to work.

I followed the first post to the letter, and I checked every file for matching MD5-sums. So I have no clue what I'm missing here... :confused:

Any help is appreciated!

EDIT: Nevermind, I was impatient and flashed again - this time it worked... :eek::confused::D
[G1 Android Development] jonnyj771:
i guess i am gonna sort of play noob here...i am running yoshi 1.1 but still running 0013 hboot. i am thinking of going to .0013d, however, a little confused...i am assuming i will have to reflash the rom when i flash the update. or will i be able to flash the update without having to change anything? phone is already rooted (obviously) and running rather well, im hoping not to change anything. just wondering if changing to the .0013d will require me to reflash everything?
[G1 Android Development] jdb78:
Read the OP carefully and you'll know that you can restore a nandroid backup after updating the combo. You will need a kernel that supports the additional RAM though. So make sure your ROM supports 2708+ or at least is capable of running a kernel that does. Check the latest pershot kernels for instance - or ask Yoshi.

If you can confirm that your ROM is able to use the 2708+, just nandroid, follow the instructions in the OP, nandroid restore and you'd be ready to go.
[G1 Android Development] jonnyj771:
I know that i can use the hboot and radio with the kernel/Rom i have currently...i was also looking at the 28.25 Radio and not sure but does that radio .zip file have the new hboot 0013d with it? i already downloaded both...but don't want to flash the hboot if the radio already has it in the file. I am still running S-ON so i cannot access fastboot at this time however, i am rooted via fast boot.

One last question. I am running clockworks recovery...I have taken a backup through recovery, but do i need to switch to amon-ra to do this?
[G1 Android Development] jdb78:
Let me quote the OP for you:

The radio does not include the SPL nor does the SPL include the radio...

Regarding to the hboot I found:

AFAIK Clockwork will work o.k. but I am not 100% sure so maybe someone else can confirm. Again: read the OP carefully, everything you need you can find in there.
[G1 Android Development] jonnyj771:
finally got it done

booted into clockworks recovery...flashed the 2.22.28 .zip...my phone rebooted itself and i didn't lose any work.

went back to recovery...flashed hboot .0013d and it rebooted...didn't lose anything there either.

It was rather fast to flash the hboot to the phone...thought at first it was going to kick back since i have S-ON still...but it took the update...will see how this pans out.

Thanks ezterry for your work. will be recommending you to those who need it.
[G1 Android Development] ellisbodds:
Okay, so I've just tried to flash the 2.22.28.25 radio using fastboot, but I get an error message.

I try typing:

(after having cd'd to the tools directory where fastboot.exe is stored)

but all I get is:

And now I don't know what to do :(

It worked fine when I tried flashing the recovery image in the same way. :cool:

Currently on the 2.22.19.26i radio and hboot 1.33.2005.

EDIT: Flashed 2.22.27.08 instead, worked fine.

Then used the update.zip method to get to 2.22.25.28 :)
[G1 Android Development] deuse:
Hi all

I hope someone can give me a bit of advice on doing this as I have not messed with my G1 for ages(been out of the loop)

I have Dream PVT 32B ENG S-OFF

HBOOT 1.33.2005

CPLD-4

Radio 2.22.23.02

Am I right doing it this way. Put the hboot-1.33.0013d.img and the radio-2.22.27.08.img in the SDK tools folder

Then go into fastboot..using Commande Prompt on my pc I type

fastboot flash radio radio-2.22.27.08.img

fastboot flash hboot hboot-1.33.0013d.img

fastboot reboot-bootloader

then

fastboot erase system -w

fastboot erase boot

I already have recovery-RA-dream-v1.7.0 so I think I don't need to do that again?

Then flash a rom...and taht's it?

Sorry for being a dumb ass guys..but my brain ant what it used to be :)

thank you for your time.
[G1 Android Development] ldrifta:
I have a method to install via recovery Here me and Habitat22 put together! it's pretty simple if you follow the directions..
[G1 Android Development] deuse:
Thank you Sir..going off to read now :)

So it's Step 3. Upgrading to 2.22.28.25/1.33.0013d I need to follow?
[G1 Android Development] azrash:
that is correct. fastboot method is much2 safer than other methods. if you can do it in fastboot, then why not. goodluck
[G1 Android Development] deuse:
I done it the fastboot way and all went well phhh :D

Thanks for your help guys and thanks to teh OP.
[G1 Android Development] autojack:
I performed this complete hack on my Dream back in November, and put the 2.22.27.08 radio on it at the time. The additional memory has really made the phone much more pleasant to use, but it does have a tendency to hard-reset now, which it never did before. I was wondering if maybe I should upgrade to the 2.22.28.25 radio and see if it's more stable.

1. Can anyone comment on that?

2. If it's recommended, can anyone tell me what I need to do to upgrade, since I already have the 1.33.0013d hboot, 2708 kernel, etc? I'm running Cyanogenmod 6.1.0.

Thanks!
[G1 Android Development] ezterry:
A1: Some people will say otherwise (usually with incomplete information) but yes it is recommended to update to the newer radio as the new one was part of a security update to the MT3G in TMO-US and subsequently the only one of the new radios distributed world wide.

A2: nandroid backup and flash the zip in the op section about switching between the radios (== Switching between Radios 2.22.27.08 and 2.22.28.25 ==)

The nandroid will hopefully not be needed.. but people have had issues with data when making the switch. Also sometimes the clock in your phone gets confused on the switch that may confuse some roms until corrected.
[G1 Android Development] deuse:
@ezterry

I followed the op and all went well a few weeks ago. I have just checked what memory I have free

and it says (using free in console) Total 97004..Used 10412..Free 87472(as I had a few problems)

How do I get the total 112700? or am I doing it wrong from console?
[G1 Android Development] AndDiSa:
In recovery or on a booted ROM?

If it's in recovery, that's normal, if it's on a running system, you probably don't have an appropriate kernel, because the additional memory you will get only with an adapted 2708+ kernel.
[G1 Android Development] deuse:
Thanks for the info ;) I am flashing a rom now so I will look after.

All ok...thks for the help man :)
[G1 Android Development] cj chitwood:
THANK YOU for "flash nbh" being operative! I haven't rebooted to system or recovery yet (restoring files to my SD ATM) but I thought I was bricked until I reread that section! PITA losing all my stuff doing the round trip flash-all nbh, but at the same time its far better than throwing the phone away or buying JTAG equipment.

Question though, Google is failing me on this one: How might one go about making an nbh backup of their phone so that the round-trip flash-all doesn't result in e.g. an Orange flash for a TMO-US device (plus not having to reflash everything)?​
[G1 Android Development] ezterry:
The s=on SPLs can only run signed (by htc) nbh images; Thus we can only use official ones.

The advantage of 1.33.0013d is it enters true fastboot mode (makes running 'fastboot flash nbh *' easier but this is possible on the original 1.33.0013 in RUU mode) and it ignores the CID check/Main Version check making it easier to flash the Orange NBH regardless of your phones original region or previous flashed rom.

This means however we can't create an nbh.. best method:

> fastboot flash nbh <orange.nbh>

> fastboot reboot-bootloader

> fastboot flash recovery <ra or clockowork ebi0 recovery.img>

> fastboot flash radio <2.22.28.25 radio.img>

> fastboot flash hboot <1.33.0013d.img>

> fastboot reboot-bootloader

> fastboot erase system -w

> fastboot erase boot

Then boot into recovery and restore your rom from the recovery backup. (the above actually never boots into the orange rom.. just borrows the radio+spl to re-build the system)

--

As long as you make a backup to your SD this is not that horrible. (Well if you know how to use fastboot)
[G1 Android Development] cj chitwood:
Right, got that...

I was considering sticking with an older radio/SPL, but I guess as long as I have a signed NBH lying around (I will, now!) then it really isn't a problem whatever features I lose by having the 0013d.

But thanks for the explanation. Always good to learn something new!
[G1 Android Development] microb0i:
NM
[G1 Android Development] beav_35:
I am trying to get this to work with Super D but I am getting an install unsuccessful error when installing some apps from the market. I found that it is caused by the /cache partition being too full. Its 27mb and there is less than a mb left. Is there a way to move the dalvik-cache to the data partition or what is the proper way to fix this?
[G1 Android Development] ezterry:
Upgrade to gingerbread?

lets see Super D.. on CM4 with apps2sd I used this: http://xdaforums.com/showthread.php?p=6060799#post6060799 (as I recall it also works on super d)

If you don't have apps2sd enabled.. make another init.d script to bind mount dalvik-cache somewhere more useful.

But I've not run pre2.1 for over a year now..
[G1 Android Development] beav_35:
Thanks so much, that script works perfectly!

I was running froyo for a while but while the extra features are nice they don't outweigh the cost in speed for me.
[G1 Android Development] taqri85:
the best thing that can happen to a g1/htc dream. ezterry you are great.
[G1 Android Development] Namit1994:
I remember you said that there was a screen on battery drain in your 0222 kernel. Can you fix that?
[G1 Android Development] ezterry:
the 2.6.34.* kernel lines are end of life and I'm not working on it [Remember my last release was February 22nd].. Also all we can say was it was a very slight bit worse than some other kernels.. particularly if you want the battery to last a long time you must keep the screen and data off.. or very very rarely used regardless of rom/kernel/ect.

I can't however recommend the new 2.6.36.* kernels for CM6 based roms as it causes other problems; and while appears to work well with froyo aosp roms, I cannot say if has new bugs over the more tested 20110222 regarding froyo roms.
[G1 Android Development] Namit1994:
Another question since you're like a kernel god, is it possible to take a 32A kernel source and make it compatible with 32B?
[G1 Android Development] dmwase88:
After Bricking my HTC Dream,i have got a 32B Magic

it has the following

sapphire PVT 32 SHIP S=OFF H

HBOOT = 1.33.0014

Radio = 3.22.23.18

Now my question is,can i just upgrade to the 2708 14+MB Hack ..i.e the 2.22.27.08 Radio and HBOOT 1.33.0013d...because i thought 3.X.XX Radio are for 32A magics....Thanks
[G1 Android Development] dmwase88:
After Bricking my HTC Dream,i have got a 32B Magic

it has the following

sapphire PVT 32 SHIP S=OFF H

HBOOT = 1.33.0014

Radio = 3.22.23.18

Now my question is,can i just upgrade to the 2708 14+MB Hack by Ezterry..i.e the 2.22.27.08 Radio and HBOOT 1.33.0013d...because i though 3.X.XX Radio are for 32A magics....Thanks
[G1 Android Development] VetalR:
Stupid question, but where is it?