yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
The unmodified version in the MT3G froyo OTA update.. but if you don't know what you are doing .. thus need more help then the obvious answer than I just gave... why not use the 1.33.0013d that everyone else is using.. and where the modifications will help fix the phone if you mess up big time.

Regardless.. if you want MT3G only binaries search the sapphire section of XDA.. this topic is intended for the dream.
[G1 Android Development] VetalR:
I know what I am doing, I just couldn't find the 0013 file. the 0013d does not let me install apps on the internal storage because it thinks that the TM3G is a Dream with 12 mb. But thanks for the answer.
[G1 Android Development] ezterry:
To others that may be reading (particularly those less convinced they "know what they are doing") a reminder that on a sapphire phone; the MTD partitions and ram available in both 1.33.0013 and 1.33.0013d are identical.. 90MB system 60MB cache; 14MB extra ram as compared to my latest ebi0/ebi1 kernels on 32b devices.

This means any lack of space is likely CustomMTD, or actual lack of space available or a bug [and or flawed decision] in the particular rom not related to the the SPL. As 1000s of users are using 1.33.0013d daily on the 32b sapphire phones without any incident; I continue to recommend strongly against flashing back to 1.33.0013 once 1.33.0013d is installed; as almost all problems will be related to other factors.

What 1.33.0013d gives sapphire users is

1) fastboot erase that is sometimes handy if something goes wrong

2) able to flash an NBH file from any region (aka hard SPL functionality) without the use of a goldcard

Dream users get an additional feature in that the partitions sizes are changed to allow for 91MB system and 27MB cache; but this only applies to the HTC Dream.
[G1 Android Development] freez76:
Worse battery life ever!!!!

OK, so I finally flashed my G1 back to CM6.1 after a few months of COS-DS. My reason for switching back to CM was that my phone was super laggy and in CM5.0.8 it was never that bad, however my battery life in COS-DS was incredible!

Unfortunately since I flashed "update-cm-6.1.0-DS-2708port_S.zip" i get barely half a day with almost no use. One more thing I should note is that I'm also running DarkTremor's apps2sd. I have tried what some people have suggested and flashed "ezBiffTestKernel20110222-2708_S.zip" but was getting lots of issues including broken wifi usage so used my nandroid backup and went back.

I am digging around on XDA and profusely scratching my head on this one. If anyone has some insight or ideas I would greatly appreciate it. Here is my phone setup..

T-Mobile G1

DREAM PVT 32B SHIP S-ON

HBOOT-1.33.0013d (DREA10000)

CPLD-4

RADIO-2.22.27.08

HELP!!!! Thanks in advance!
[G1 Android Development] Litesorrows:
Anything CM based I'd use Juice Defender. I wouldn't use CM6 with the 2708 sucks *personal view*. Id go to FroyobyLazlo if you want Speed, Battery Life, and Froyo. It's using a Hacked Kernel so it randomly reboot's at times. But its worth the speed. COS-DS is the best GingerRom out right now too.
[G1 Android Development] R3N0V4D0:
FroyobyLazlo is CM based
[G1 Android Development] freez76:
Speed and usability have not been the issue....only the battery life. If I'm using a better suited kernel shouldn't that have fixed the problem or can it? I have had this phone since '09 and replaced the battery once inbetween, but have never seen consumption this bad! I am ok with trying FroyobyLazlo, but would really like to know what's wrong here first and try to fix it.

Anymore ideas are very welcome!

Thanks
[G1 Android Development] cj chitwood:
I hate to jinx it but I've had very decent use of AndDiSa's ADS Magpie dated 14 August. It's not the fastest I've seen my phone, but it's nearly the fastest I've seen it specifically on gingerbread and I've only had one or two random reboots since I've been using it. In COS-DS, one version would be stable and the next would be quicksand, and by the time it started fouling up I'd have forgotten which version I was on before (and I do multiple NAND backups so it's more trouble than it's worth to figure it out by NAND restoring). Not knocking COS, it's a decent ROM, but one version to the next I often wouldn't know what to expect from it performance wise.

ADS also isn't the best battery life I've seen, but the best battery life I have seen has been on FroYo and Gingerbread ROMs, and what I'm getting out of ADS is NOT bad at all (unless, of course, I leave 3G on, GPS on, auto sync on, wifi on, etc. etc. etc. instead of turning off those things I don't need).

I can't say it's for everybody but I do think everybody looking to try G1 ROMs should look at ADS for at least a while.

Oh, and unlike on COS, Google Maps and GPS actually work together. On COS, Maps would die every time if GPS was enabled. Overall the ROM is quite stable for me.
[G1 Android Development] ezterry:
Just FYI for anyone wishing to experiment:

My latest build of the ezGingerbread kernel is out: ezgb2636 v1.5.1:

http://xdaforums.com/showpost.php?p=14768272&postcount=2427

It has two builds: 1) for gingerbread based roms and is the ones built into the ezGingerbread series.

The second is a froyo compatible build, its been an option for the froyo ota based roms for a while, but with version v1.5.1f I've also have had success with froyo based roms.

So if you are still using my biff testing series 20110222 (2.6.34.8) or the older 20101106 (2.6.34.7) kernels and wish to try something new the 2.6.36.4-s3 kernel may prove a useful update.
[G1 Android Development] cj chitwood:
Oh, and maybe add some punctuation... would be easier to read quickly...
[G1 Android Development] roccoadam32:
Posted the log because the kernel is reventing the phone from sleeping..can see in spare parts running 100% after my screen was off for 2 minutes had to flash back to the power save kernel
[G1 Android Development] ezterry:
No more than expected from the "its not working" post made shortly after an announcement with incomplete information.

If you run dmesg (note not logcat) after waking the device, or look at the battetry drain over time, its obvious the kernel is sleeping.

I can see now there is a cosmetic bug, that causes the system to not be able to read the time spent sleeping however. In tern this makes the battery history appear as if the phone was "running" 100% of the time. Gingerbread seems to be doing a better job since the new battery graph shows the kernel sleeping.
[G1 Android Development] roccoadam32:
I was only trying to point out what I saw if you say the phone is sleeping fine but u guys always come across angry when people who don't know as much about android as you do are trying to help
[G1 Android Development] TBBle:
Just trying to clarify something, I'm using CustomMTD, so I understand that I can't use the radio update zip files to switch radios between the two radio images supported for this kernel. But does that also prevent me directly flashing the radio using fastboot?

I'm just not clear on how these things interact, and I don't understand _why_ CustomMTD prevents using the radio update zip, so I can't make any connections as to whether or not fastboot flashing the radio is equally prevented.

To be clear, I'm already running 2.22.27.08 with the 2708+ kernel and hboot 1.33.0013d. So I'd just be switching radios underneath, not applying any other changes.
[G1 Android Development] ldrifta:
im not 100% sure but i would just remove the mtd partition... its easy... you can put it back on after... either way im almost sure you need to re-flash rom because of radio change..
[G1 Android Development] AndDiSa:
You should not flash radio/spl with custom mtd because your caching size is reduced and this may cause problems, i.e. bad flashes.

That you cannot flash radio using fastboot is a different thing: normally this is the preferred method, but you are on 1.33.0013d, which is a perfected spl and this one has only a restricted set of fastboot commands enabled.
[G1 Android Development] bandido73:
Quick question...will this work with clockworkmod recovery? If so which version?

thank you very much in advance, and keep up the good work. :)
[G1 Android Development] ezterry:
The dream version if you have a dream.. the mt3g version if you have a 32b sapphire device.

(Even some of the newer roms in rom manager know to install the 2708 kernel.. otherwise both pershoot's and my own 2708 kernels are on rom manger, just download one before installing the rom so its on your sdcard)
[G1 Android Development] bandido73:
Can you please take a look at my sig and give me some info on what to do next to get this going? a problem im having is i got CWM recovery installed, i tried flashing Ramon RA Recovery 1.7.0 (which is 1 of the requirements)through fastboot and Rom Manager it says installed but when i go to reboot into recovery it stays on the G1 screen and wont boot till i do a battery pull.i let it boot all the way and reflash CWM RECOVERY in Rom Manager and will boot fine into Recovery.I would really appreciate any info on this and get this resolved.
[G1 Android Development] pkilla:
Can I do this hack with these stats

Dream pvt 32b s off

1.33.2005

2.22.23.03 and how and what do I need
[G1 Android Development] AndDiSa:
I posted my answer already here
[G1 Android Development] Ace42:
Terry I have upgraded to the -.28 radio thru recovery, but would like to revert to the older one 2.22.23.02, because that one works with the donut ROM I was planning on using. And I still have the danger SPL, didn't get around to flashing the new one.
[G1 Android Development] ezterry:
Really why people who still insist on donut don't use the oldbuilds kernel is beyond me... really the onlything broken is compcache and ipv6.. and both of those can be fixed by putting the modules where init scripts expect them.

At least that was the only issue I saw with CM4

Anyway I think the post about 1.33.2003 as mentioned in the stock SPL section of the OP includes info about stock spls. 0.95.*, and eng spls 1.33.2003 and 1.33.2005 as well as 2.22.23.02.
[G1 Android Development] Ace42:
I haven't used the phone since last year+, so I haven't kept up with its developments. I want to keep it on enom's donut rom permanently. I'm selling my main phone, so I have to use my G1 till my upgrade comes around or I get a new phone. I saw this post and thought it would make the phone much better to cope with.

Edit: Nvm, I'll just un-root and start over...
[G1 Android Development] Gordon01:
I have been stuck with fastboot.

Does this actions erase data partition? Is there any way to save data partition?
[G1 Android Development] cj chitwood:
I believe it does erase Data. However, if it does, I myself know of no way (save for JTAG) to save it. Maybe someone else knows more, but when I was googling for ways to salvage partitions (assuming a functional fastboot) I found none.
[G1 Android Development] Gordon01:
So... only way to save data is JTAG?
[G1 Android Development] ezterry:
Nandroid is how you backup data, if you didn't run nandroid before whatever made you be stuck at fastboot you most likely already lost the data.
[G1 Android Development] tufoz:
hi Guys,

i'm freezed in the fastboot mode.. i can't enter in recovery...or power on the phone..

32b

hboot 1330013d

radio 2222708

what can i do?
[G1 Android Development] AndDiSa:
The solution is already posted in the OP, look for *== Important Information about 1.33.0013d ==*
[G1 Android Development] cybernetus:
Well, I read the forum and I see this address to download the new kernel of ezterry

http://xdaforums.com/showpost.php?p=14768272&postcount=2427

Well, I flashed this on my phone today and I will test this.

I don't see any problems with this kernel now ...
[G1 Android Development] cybernetus:
Well, I return to my old kernel to test the battery life.

When I put the new kernel, my phone drain my battery, and I have some problem with is.

I post some updates here .
[G1 Android Development] ezterry:
If you are switching between very diffrent kernels make sure you wipe battery stats or your battery "drain" will not resemble the actual use of the phone.
[G1 Android Development] cybernetus:
Hey ezterry, I switch to the new kernel again.

My problem is an application bug. The Facebook application drain all my battery on the last 2 days.

I update the application yesterday and my problem, now, isn't exist.

I will test again and post my results here.
[G1 Android Development] phin586:
Thanks for the info. Now to see which runs best with cyanogen 5.0.8 for me. Was using the default biffmod that came with it. I am now using the ezgb kernel. Looking for the best batter + performace.
[G1 Android Development] josh36:
@ezterry - I doff my cap to you, you are a star! Superb work!

I have successfully integrated the new radios, the kernel, the new hboot and Amon_RA (cyan) with the CM7.2 - the latter compiled from source - all this gave my old G1 a new lease of life - I hope your work on G1 will continue!

I was reluctant initially to use anything other than the CM kernel, but I was stuck in a bootloop, so I switched to this kernel and it all worked out!

I also did the GPRS upgrade (although I haven't had the chance to test it yet), but now after all this my IMEI, IMEI SV and baseband values have been wiped out. Could this be as a consequence of doing the GPRS upgrade, the radios or something else? Is there any way I could restore these?

FYI - I have a G1 rooted which had CM6.1 previously, together with the standard (.19i) radio and hboot (.2005).

I have now altered slightly the kernel's .config file (to exclude the bluetooth stuff, among other things) and compiled it successfully - will test it and install it over the xmas period to see how it goes.

@ezterry - is your version of the kernel using the standard netfilter stack or have you made any modifications to it?

I am asking this, because my next step after compiling and installing this kernel is to patch it up to include ipset (will start with v4.5 and if all goes well will then move swiftly to include version 6.9.1 which is the current release and which supports ipv6 very well).

I intend to make extensive use of the firewall and ipset performance is way better than the regular ip/net matching - I know this from experience.

Even though ipset does not become "part of the Linux kernel" until v3.1, I have successfully used it since kernel .35 - without any difficulties - so provided the netfilter stack isn't altered too much I don't envisage too many problems integrating this into the android (or ezterry's) kernel.

I've also looked at the iptables sources used in Android and there are some quite bizarre changes I still can't get my head around yet!

I intend to update iptables to at least version 1.4.10 as well as the wpa_supplicant to (possibly) 0.7.3, so I need fully functional netfilter.

EDIT: I've successfully compiled the kernel from source, no problem, but how do I prepare the update zip file to update it on my phone? I can't simply replace zImage in the original update zip file because all kernel modules seems to have been packed with a separate tool, which I have no idea about!
[G1 Android Development] mahroze:
I know this maybe a noob question but I have

radio: 2.22.19.261

HBOOT: 1.33.2005

I wanted to know that should i just flash as per the instructions or do need to read any other post to flash a different spl and radio combination please advice

no worries got it :)
[G1 Android Development] Scrip:
if you took the time to read the OP you wouldn't be asking
[G1 Android Development] elmanortega:
hey guys amazing work can i get some help with this?

i dont want to brick my device
[G1 Android Development] Scrip:
I pointed you to this thread because it has everything you need

take your time and read it

if you still do not understand the op then you need to pay someone who does

jumping on guide threads and asking for the "makes the idiot look smart" guide is no help to anyone
[G1 Android Development] PJK2011:
*** Delete ***
[G1 Android Development] elmanortega:
yes but i rather have some one with experience to help me out and do it once than bricking my device, can some one just walk me on this??
[G1 Android Development] :
It's all in the OP... I don't see how hard it could be since I was a complete noob when I installed 2708 radio + 1.33.0013d spl on my G1 last year
[G1 Android Development] demkantor:
Besaides, if you want help search the forums, then when all else fails post in the q & a, don't ask for help in the development section, chances are not as likley here
[G1 Android Development] tvall:
Bumping this great piece if info up
[G1 Android Development] Infinimint:
I'm gonna request a sticky :D
[G1 Android Development] TheShortybro:
I have made a way to do this WITH safety 100% working, it may go against every standard you guys have with fastboot but it works. Just lookie here: http://xdaforums.com/showthread.php?t=1630038
[G1 Android Development] ezterry:
Look in the OP the 1.33.0013 to 1.33.0013d that prevents you from flashing it without a valid system.

Everyone (in the past year and a half) that has felt so obligated to write such a guide while grudgingly may add the warning about the 1.x radio, has failed to add logic to look for/verify the 2.22.X radios before allowing the user to flash the hboot.

Mind you its still safer in the long run to know how to use fastboot and less can go wrong if you flash directly to the bootloader ether than to cache, to have the bootloader copy it into place. Thus I will continue to try and discourage the use of recovery where possible for the hboot and radio flashes. This discouragement is why its *not* in the OP and wont be.

But its always "worked" from day one via recovery.. you just need to be very very careful the system is compatible.. and with our knowledge today there is no reason these scripts are not made smart enough to double check.

I don't know if you remember the days of the danger/deathSPL... the problem ultimately was we didn't realize the compatibility problem with the 1.x radio and *most* of the 1.33.* SPLs (1.33.2003 being a rare exception) To make maters worse people for some reason to ensure the install was clean seemed to have a habit of flashing the original android 1.0 nbh file with the original 1.x radio/0.95.* SPL.. and thinking they still had the 2.x radio from before the nbh flash. By forcing you into fastboot we are sure what radio/bootloader you have.. and are sure if it lets you flash it wont become a brick.
[G1 Android Development] Scrip:
should the bold be recovery?
[G1 Android Development] demkantor:
hey scrip nice to see your back, im sure ezterry isnt discouraging flashing from fastboot...
[G1 Android Development] ezterry:
correct.. *cough* what I mean not what I type.... (fixed)
[G1 Android Development] TheShortybro:
Fastboot only works if you have S-Off, wich in this case it has not with the RAM-hack, because it comes from the MT3G stock OS. So fastboot is only useful if you use DangerSPL, because that is to only SPL that is fastboot enabled. It becomes only useful for flashing ONE SPL/HBOOT. So why do people prefer doing this when you can do this between the palms of your hands? Fastboot is not so very useful now isn't it?

But is if both methods work why are we arguing about this? Let the people choose what to decide, it's still their phone and if we give a guide that is 100% legit and works for both they can choose! Don't push people to do the 'reccomended' but explore other options!

AnDiSa, EzTerry and other devs, think about THAT!
[G1 Android Development] chidori602:
Uhh, I'm kind of lost reading all this. Is SPL 1.33.0013 available in this thread? I currently have spl 1.33.2010 and I am trying to go back to the stock spl.
[G1 Android Development] cj chitwood:
There is a link to 1.33.0013d in the first post under a word in large print that is "Files". You'll have to download a zip file that contains this and one other file in it, but it's there.

You say you're trying to go back to the stock SPL though. The stock one is not available here but I'm certain I saw, somewhere in XDA, a link to a page offsite that had several SPLs -- including stock -- listed.

---------- Post added at 01:09 PM ---------- Previous post was at 12:57 PM ----------

I'm out of time for the moment, but I was able to pull this up for you. I went to the forum root, clicked "Android" at the top of the screen, saw a link to the G1 subforum (You can probably get by just clicking the "HTC Dream: G1" link at the top of the page under Portal/Wiki/XDA TV/New Posts/Quick Links/UserCP links).

Then I went to the right hand side of the top of the forum thread list, and clicked "Search this forum". I chose the words "Stock SPL" (but unfortunately that's relatively vague terms -- still, I found the following).

This one shows how to root a stock G1, but more importantly, starts you out from a nonrooted state, using the original DREAIMG.NBH file -- which is one way to unroot if you want to go completely stock.

I didn't see any others, but I only looked at three threads. The thread linked above is the closest to finding stock spl. It's called DREAIMG.NBH, you put it on your SD card root directory, boot the phone to fastboot mode, and it will flash your phone back to unrooted stock (*I BELIEVE... it's been so long, I don't really remember).

Hope this helps.

[EDIT]

I only just now saw you ask a question in the other thread.

WHAT EXACTLY DO YOU WANT TO DO AND ON WHAT HARDWARE?

The G1 (Dream) does not have exactly the same hardware as the G1 (Dream) (not a typo, some were EBI0 some were EBI1 IIRC)

Also, the G1 (Dream) and MyTouch (MyTouch 3G, MT3G 1.1, MT3G 1.2) all had minor differences and you must know exactly which platform you've got so you don't brick it with the wrong SPL.

Are you wanting to go bone stock, unrooted, send-it-back-to-HTC-for-repair? Or, are you just wanting to downgrade for stability in a custom ROM?
[G1 Android Development] demkantor:
I think s/he's got the mt3g, if that's the case it would be best to ask the questions in the mt3g forum. If s/he has the g1, then the .13 spl would not be stock.

Either way I stand by my firsft statement... search button works great
[G1 Android Development] chidori602:
alright so, basically i have 1.33.2010 right now. With this SPL lots of things dont work. I just want to go back to the original. I have the mt3g 1.2 by the way. also i've tried 1.33.0013d and i get a message saying that i need 1.33.0013 as 1.33.0013 is just an update.
[G1 Android Development] cj chitwood:
Then 0013d is not for your phone. 0013 is, possibly. Is the 1.2 the one with the audio jack? I believe that one had a different board from the one without (obviously, to support the jack, but different enough that I'm not sure the same spl will work). I'm officially out of my area of expertise though (some would say I was never in it to begin with :) ).

--

Sent from my Bulletproof HTC Swiss Army Doubleshot with XDA-Dev app
[G1 Android Development] Phateless:
I believe you might be correct, I think the 1.2 is a 32a iirc. Check me on this though, as it's been awhile...
[G1 Android Development] tvall:
On the 1.2 I recommend 1.33.0013d. Everything works as it should. Plus you have a better chance of reviving what would otherwise be a brick.

Ezterry took 1.33.0013 (the stock spl for the 1.2 and what was pushed in the froyo ota) and enabled everything he could and made it more friendly on the htc dream. Works really well
[G1 Android Development] djmeistro:
me too *crosses fingers*
[G1 Android Development] gringo69:
curious....if i remember right....ppl said JIT didnt work right due to lack of RAM on our phones....would this be enough of a bump to get JIT workin right?