yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] lolmensch:
@ezterry

not spl or radio specific but i think it comes mainly from your kernel..

i downloaded "CurrentWidget"

it shows the need of electricity of your phone.

my phone never goes beneath 190mA which means that our phone is not able to stand more than lets say 7 hours in IDLE mode... thats pretty bad.

i looked if there are any background services running with ddms.bat and uninstalled news and weather app and many more which were running in the background.

rom is cm6.1 nightly version 255 (just added your spl in the updater-script) with multilingual gapps from 8th october.

(test3 - your latest ota rom - had even worse batterylife but i didnt test it with currentwidget)

could you work on better battery of your kernel? or are there any other things you could think of?

if it's not the kernel's fault i apologize for wasting your precious time.
[G1 Android Development] Phateless:
I flashed this kernel over my oem 2.2.1 and battery life seemed great! Granted, the phone is no longer my daily driver but I left it on for 24 hours without a problem.

I'm not sure it's the kernel, I think it's something about CM6. I had the same problem.
[G1 Android Development] ezterry:
If you don't want my kernel don't use it.. the cm6.1-rc1 2708 port in the op contains the kernel from cm6.1-rc1 (patched to boot with the extra ram)

If you want to improve battery life (don't we all) either more scientific results from usage or patches are welcome..

I'll tell you all the roms with all the kernels work very well.. idle even with wifi going but not signed into google and sitting home while I'm out. 3-6 day uptime is easy.

Otherwise reports of fast drain match reports of long life.. and my testing also has those mixed results.. people who know about the power management are working on better solutions.. some are waiting to port into my kernel.. if I can make them stable on the older version of linux.
[G1 Android Development] lolmensch:
woot O.o 3-6 days Oo it was really no offense to your work. i really appreciate that. you and firerat are really bringing us forward with our old devices.

just somehow disappointed.

probably my battery is the reason. it has like 1200 charging cycles....(dont blame me for posting about battery issues when using that battery please)

i just thought about kernel because its based on an older pershoot kernel where there are battery issues (although its WAY better than the new kernels of him, regarding batter life)
[G1 Android Development] jpzzle:


LIAR :-) I'm using Super E with the new radio new hboot and of course the ez..kernel, and everything works just fine battery life is even better CAMERA ISN'T BROKEN. So to the guy who asked YES U CAN PRETTY MUCH USE ANY ROM WITH IT.. AND YES YOU CAN USE SUPER E ITS EXCELLEMT :-)
[G1 Android Development] Phateless:
Awesome, thanks for that, I've been wanting to try SuperE for awhile now.
[G1 Android Development] Edubyah:
Can anyone post an example of the port edit?

Could anyone post an example of what files are edited to work with the 2.22.27.xx or 2.22.28.xx radios? Maybe we could edit these and re-zip the update if we knew exactly what to look for.
[G1 Android Development] d12unk13astard:
Ya SuperE has been my default rom for awhile now, never liked froyo. Eclair rom with apps2sd is all i ever needed and everything really does run so much smoother with this eazyramhack :-P Thanks again Terry!!
[G1 Android Development] zzrssh:
This was very helpful with my girlfriend's G1; thanks! The instructions were a bit confusing, but once I re-read it and found the relevant parts, ignoring all the extra stuff, it was a breeze.
[G1 Android Development] Firerat:
boot.img

..........
[G1 Android Development] cctv35:
Kernel 2.6.35.9 – OC-UV-RAM-FP – Dream/Sapphire (32B/A)

Unlimited restart

Some people brush it?
[G1 Android Development] Phateless:
Thank you ezterry!

This kernel has made my phone snappier and more usable than I've ever seen it. If I hadn't already bought the mt4g when I flashed this kernel I may not have bought it at all.

Is there any way to get this up to 710 with the additonal ram or is 614 already pushing the feasible limits of stability?

Again, thank you for helping us get the most out of this completely outdated hardware.
[G1 Android Development] the.igorr:
Is there a safe way to re-flash spl 1.33.0013d + radio 2.22.27.08 again?

I got them installed right now, but I have a huge problem flashing Ezterry's test3 rom - browser keep crashing, Gmail not working etc. I had similiar problems with test2 and I'm staring to think that something went wrong during upgading spl and radio (from 1.33.2005 + 2.22.23.02).
[G1 Android Development] mistis:
can i use the 28.25 radio and the new spl at once, or should i use the 27.08 radio with the new spl and only after that upgrade the radio to 28.25?

cheers
[G1 Android Development] tnpapadakos:
either way is fine
[G1 Android Development] d12unk13astard:
Heres some pics of my increased memory after the ezterry hack, this has made my phone so much more faster and responsive.

before i installed loads of apps/games..

...and after i installed over 100+ apps/games to phone, still smoking fast and craploads of memory left.
[G1 Android Development] mistis:
dont know about 27.08 but with 28.25 everything went smooooth ;)

thanks a lot :)
[G1 Android Development] revolnia:
security is ON

Hello guys...

I flashed this new radio/spl/kernel and flashed DroidEris 2.1 sense ROM.

I just realised when I entered fastboot mode:

DREAM PVT 32B SHIP S-ON

Is it normal to have the security ON?

would I still be able to run this below command? Because I want to flash the new ROM update:

fastboot erase system -w
fastboot erase boot

Thanks!
[G1 Android Development] breezy169:
im currently running the MT3G . but i havent done the whole fastboot thing yet so is there any other way to flash the hboot & radio? and is it safe to do this to my MT3G ? bc i heard this is great only the g1's?
[G1 Android Development] djmeistro:
do the radio and the updates effect wifi at all?
[G1 Android Development] Trek55:
not at all buddy...
[G1 Android Development] Firerat:
go to the OP and read from

the stuff you want is in the box under

but tbh, I doubt your problems are radio/spl related
[G1 Android Development] djmeistro:
Thanks buddy!
[G1 Android Development] Edubyah:
New RADIO

I have the myTouch3g 1.2/Fender and as most people know I am already stuck with the 1.33.0013 SPL. After speaking with Terry I upgraded radio from 2.22.23.xx to 2.22.28.25 instead of the 2.22.27.08. I then restored my nandroid of a custom build (maybe hodge podge would describe it better) 1/3 Froyo for Trout 1/3 RA's FroyoMod and the remaining 1/3 I like to call Gumbo (if you contributed something to the community I got a piece of it) it has worked nicely so far other than problems I had pre-radio change (themed mrkt. F/C after appinstall and always updates to /data/app/) I felt it was noticeably faster at certain tasks especially phone.apk sooo quick to call and answer. (again maybe coincidence but still best it has ever ran) My dilemma now though is: I'm a themer and this T-Mo OTA mix (see hodge podge) is not text color change friendly so I want to get back to a CM derivative , maybe Biffmod again or the nightlies. But when I flashed nightly 257 then Terry's 251-cm-2708port_s.zip it made it all the way without bootloop then when the hard keys lit-up right before ithe animation stops and lockscreen pops up it just stays like that - hard keys backlight on bootanimation perfect frame-rate and never goes to lockscreen in the O.S. Do I need to downgrade to 2708 radio or is the 2825 supported also?

PS-Can I edit the update-script to make it boot with 2825 radio?
[G1 Android Development] ezterry:
You are forgetting agin that the 2708 ports have the new kernels for extra memory on the 32b devices.. you have a 32a device and the correct memory map is in the standard ebi0 kernel (the one shipped in the actual cm6.1rc1 not my "port" of it)

Yes many have proven the new radios work on the fender, but there is no new kernel for the fender. Only the original mt3g 32b and g1/dreams are able to use the new kernel.
[G1 Android Development] Edubyah:
What should I do? CM6 nightly 257 wouldn't boot are 2825 and 2708 acceptable radios for CM roms? Therefore not requiring any "port".
[G1 Android Development] Firerat:
why is it not booting,

where is your logcat?

did you flash a compatible kernel?
[G1 Android Development] G1ForFun:
I just want to be sure....does the newest radio (2.22.28.25) also apply in these steps? Or do I specifically need to roll back to the previous radio (2.22.27.08) in order to flash the eng spl again?

If you just temporarily need an engineering SPL (and recovery is working):

(and have SPL 1.33.0013 + radio 2.22.27.08):

1) Nanroid backup

2) Flash (via recovery) ENG SPL 1.33.2005 **

3) do what you need to in the engineering SPL

4) reflash 1.33.0013d as above (install, reboot bootloader, fastboot erase)

5) restore nandroid
[G1 Android Development] G1ForFun:
You need to flash a compatible kernel...like this one.

For example this is the Nightly 251 kernel by Ezterry.

ez-nightly251-cm-2708port_S.zip

(md5: 2d43c64343d4d5de6a2a9fecbc263d24)

You would flash the CM6 257 nightly and then flash the gapps of your choice and then flash this kernel that I am linking you too.
[G1 Android Development] Edubyah:
Logcat...

Alright the last conversation with Terry cleared this up for me. I apologize for the time it took but your time was not wasted as now I know.....and understand fully! I flashed the newest nightly on my Fender myTouch3g with the 2.22.28.25 radio and nothing else!!!!! No port no kernel this is where I was confused as I did not realize the same ROMs I have been using boot just fine with all 3 of the 2.22.xx.xx radios no port needed for myTouch 3g 1.2. Port only needed when using 1.33.0013d spl on Dream to get the extra RAM. So all the Magic 1.2/Fender owners only benefit from new radio no extra RAM just updated radio. Now for another question can I use the modified SPL on Magic1.2 with the known benefits and no disadvantages?

PS-Firerat requested my logcat for my problem-There is no problem it was in my head...hence the absence of my logcat..LMAO..at myself before you do.

ATTENTION MAGIC 1.2 OWNERS

After testing and pestering the experts the only thing you need to do is update RADIO to 2.22.27.08 or 2.22.28.25 this is all! No port files to flash and no 2708 port ROMs are needed the same ROMs and kernels you have always used will work.
[G1 Android Development] Phateless:
I never got as high as 63 mb of free ram. I wonder if I'm actually getting the ram I'm supposed to be...
[G1 Android Development] Firerat:
thats not ram, its space on /data

they have chosen to slow their phone down by putting dex on sd-ext
[G1 Android Development] Phateless:
Shown in Task Killer? I tried the "mem" command on Terminal but with my font large enough that I can read it the formatting is so messed up I can't tell what I'm looking at.
[G1 Android Development] Firerat:
yes..

what do you want, and what are you going to do with it?

if you want 100% free ram, turn your phone off
[G1 Android Development] XxKOLOHExX:
LMFAO! nice one haha :P
[G1 Android Development] sparksco:
I have dalvik-cache on ext and my phone isn't slow. My linpack is 3.7 at 528mhz max
[G1 Android Development] Firerat:
lol

benchmarks
[G1 Android Development] sparksco:
Well my phone's not slow, and I have about 10 widgets on my home screen. I have no lag at all.

Edit: see for yourself. Keep in mind he has windows animations and transitions on very slow for demonstration purposes:

http://www.youtube.com/watch?v=UA5n5C8TUUo
[G1 Android Development] G1ForFun:
God you make yourself look even worse when you make posts like this. At least know what you are talking about before cooking up roms.

And all he said is that your phone will be

slower

when you bind the dalvik cache to ext....
[G1 Android Development] arefin:
Suggestions please, battery panics with wifi turned on

hahahahhahahahaaa....

period....

can someone put some light on this:

the battery goes down so fast when wifi is turned on that I can actually see it going down, say 1% in every 10 secs. This is certainly not normal, I have used the same ROM (biff2.1) before having this 14MB hack installed. What is happening?

any suggestions are welcome, my guess is the new Radio (I'm using 2.22.27.08 radio) could be killing the battery when wifi is turned on. I dont have data plan so cant check whether it causes the same on data.

Thanks in advance
[G1 Android Development] Firerat:
lmfao

it looked slow to me

"that was my silent video, hope you guys enjoyed it"

hehe

anyway, the point of that video was ?
[G1 Android Development] sparksco:
And all I'm saying is I didn't notice my phone getting slower, period
[G1 Android Development] Firerat:
turn the battery % thing off, its always stressed people out

if it needs to keep updating the % , its doing stuff

doing stuff = using battery

because you see it tick down it further compounds it, normally you don't 'see' it tick down so you don't get stressed
[G1 Android Development] Phateless:
lol, aren't we clever.

Use Pandora and Navi simultaneously.
[G1 Android Development] xaueious:
Why do I see rom cooks arguing with devs in this thread lol...
[G1 Android Development] breezy169:
hey guys, every time i tried to flash the recovery (the first step) it keeps saying error cant load recovery

anyone know how i can solve thiis ?
[G1 Android Development] Firerat:
Nope, its just most people are dumb

try using Auto Memory manager and set secondary server to the same as Foreground app

use

menu--> running processes --> Group by oom

to get a better idea of what is running, and what slot they in

the higher you set that slot, the more likely it will be killed
[G1 Android Development] Edubyah:
I don't know but I kinda like it! FUNNY SH#T HERE.....AND I THOUGHT THIS WAS DEVELOPMENT...LMAO..HAHA
[G1 Android Development] sparksco:
I guess you didn't read the part where I said the animations and transitions were set on very slow for the video. The point is it's not slow on anything else with the rom, so that's the point...
[G1 Android Development] punshkin:
i am not that much into all this spl and kernel stuff so i have some questins

1)this gives my G1 extra Ram/memory so i can have more applications at the same time running right?

2) where does it take this from?

3)it is so complicated. are there chances the next cyanogenmod will install this automaticly if i flash the rom-zip?
[G1 Android Development] LexS007:
It's for T-Mobile Dream or for Rogers Dream?
[G1 Android Development] nlysurferdude03:
ok so i have been trying this with the latest nightly on my mt3g and cant seem to get it for the life of me. i got the same error then saw your post of needing the customMTD so tried that and im still getting the same damn error and can't seem to flash a rom =( i dont know what else to do at this point. any help would be appreciated. :confused::confused:
[G1 Android Development] Abhi_UK:
1)So this is the new radio that will give us better recpetion and also the hboot that will give us more ram?

2)Also will roms flash normally or do we need firerat mtd?
[G1 Android Development] Firerat:
the reason people are talking about customMTD is that I included a workaround for SPLs which are not in the ROMs assert checks

in the mtdpartmap.txt file include the line

spl 1.33.2005

this will append the recovery's kernel command line with

androidboot.bootloader=1.33.2005

which is enough to trick the assert checks into thinking you have 1.33.2005

alternatively edit the rom's updater.script, and add your running SPL version , or just remove the assert checks

e.g. add

getprop("ro.bootloader") == "1.33.0013d" ||

or delete

assert(getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire");
assert(getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.2003AF" ||
getprop("ro.bootloader") == "1.33.0004" ||
getprop("ro.bootloader") == "1.33.2004" ||
getprop("ro.bootloader") == "1.33.3004" ||
getprop("ro.bootloader") == "1.33.0005" ||
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.3005" ||
getprop("ro.bootloader") == "1.33.0006" ||
getprop("ro.bootloader") == "1.33.2006" ||
getprop("ro.bootloader") == "1.33.3006" ||
getprop("ro.bootloader") == "1.33.0007" ||
getprop("ro.bootloader") == "1.33.2007" ||
getprop("ro.bootloader") == "1.33.3007" ||
getprop("ro.bootloader") == "1.33.0008" ||
getprop("ro.bootloader") == "1.33.2008" ||
getprop("ro.bootloader") == "1.33.3008" ||
getprop("ro.bootloader") == "1.33.0009" ||
getprop("ro.bootloader") == "1.33.2009" ||
getprop("ro.bootloader") == "1.33.0010" ||
getprop("ro.bootloader") == "1.33.2010" ||
getprop("ro.bootloader") == "1.33.0011" ||
getprop("ro.bootloader") == "1.33.2011" ||
getprop("ro.bootloader") == "1.33.3011" ||
getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013");

faking SPL with customMTD is just far more convenient
[G1 Android Development] Abhi_UK:
My last question is that because we have to use this kernel, we can't use psfreedom can we?
[G1 Android Development] nlysurferdude03:
thank you very much for that explanation, I've made the adjustment of adding the spl 1.33.2005 line to my txt file, yet im still receiving the same error ending with:

E:Error in /sdcard/cm_dream_sappire_full-235.zip

(status 7)

Installation aborted.

any suggestions would be greatly appreciated because im just sittin here in recovery.
[G1 Android Development] ezterry:
Yes.. they are the same phone (and op instructions is the method to safety switch rado+spl without bricking regardless of the currently running version)

but if you are with rogers with a rogers phone, rogers will probably cut your data on the assumption that you no longer have their e911 update
[G1 Android Development] Firerat:
did you flash recovery patcher and reboot?

you need to do that so the fake spl gets added to recovery's kernel cmdline

no need to do the erase or formats ( unless you changed the sizes while adding the spl line )

Edit:

Oh, if you only using custom MTD to fake the SPL ( not resize ) then enter your current sizes for system and cache

e.g. Stock G1 with Danger SPL is

mtd 90 30
[G1 Android Development] sisterchick:
From OP: !!!! WARNING !!!!

The following is *ONLY* to be used on HTC Dreams (so if you don't have a pyhsical keyboard on your phone do not install the Radio/SPL as indicated on this thread)

Did you try to install the radio/spl from the OP or did you use the OTA for the MT3G?
[G1 Android Development] ezterry:
More tech info:

http://code.google.com/p/cyanogenmo...Model Network Owner Summary Stars Priority#c3

You will need to install the new radio+spl yourself.. I will not be surprised to see cm have an official port patched for the kernel.
[G1 Android Development] nlysurferdude03:
hahaha yah i saw that warning. i started this whole thing out from XXkoloheXX's post on page 4 for mt3g users. i then went on to about 3 or 4 different pages throughout the whole process downloading probably about 8-10 files. just for kicks i tried to flash tom's xtra that was just released and somehow that installed, along with the kernel from page 4, and the tiny gapps i have. right now im on the hboot-1.33.0013d.img and the 2.22.27.08 radio.

but heeding that warning now...should i continue with the flash of the FR-boot file and reboot??? lol i feel so frustrated that its taken me since 11pm to get this far and i couldn't even tell you what i did to get the xtra version to flash, but im happy about it lol.
[G1 Android Development] Abhi_UK:
Whats the recommended custom mtd partition sizes and also can we use this with psfreedom ?
[G1 Android Development] ezterry:
But XXkoloheXX installed the MT3G ota to install the radio + 1.33.0013 official spl.. not the one hacked for the dream.

The kernel works on both dream+sapphire but this is how to install on the dream

Well if you have a MT3G with 1.33.0013d .. I cannot tell you how to continue unless you tell me the non customMTD partition sizes

From adb shell while recovery is running without the patch:

Will tell me the needed info

Otherwise it's up to you if recovery booted you can use custom mtd..

CustomMTD: The same as if you where not using the new spl?

"90 2" unless otherwise stated by your rom. If you want to match 1.33.0013d as it behaves on the dream use "91 27"

Psfreedom existing kernel will probably bootloop the same as cm6 ebi0 kernels do on this radio
[G1 Android Development] nlysurferdude03:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.8M 0 47.8M 0% /dev
/dev/block/mtdblock4 2.0M 1.1M 884.0K 57% /cache
/dev/block/mmcblk0p1 3.2G 247.6M 2.9G 8% /sdcard
/dev/block/mtdblock5 373.8M 1.1M 372.6M 0% /data
/dev/block/mtdblock3 90.0M 85.8M 4.2M 95% /system
/dev/block/mmcblk0p2 457.0M 8.0M 424.5M 2% /sd-ext

i believe that tells me that the customMTD is in effect which is set to 90 2. damn it all...:eek::(
[G1 Android Development] Firerat:
soooo frustrating

CustomMTD has nothing to do with this !!!

partition sizes are dependent on the ROM you are using

the only reason it has been mentioned here is because customMTD has a handy trick in it so you don't have to edit the updater-script to get a ROM to flash

I think I will put together a quick patch, which is independent of CustomMTD just to save us some noobfusion
[G1 Android Development] ezterry:
Yes that looks like "90 2" I ask about the unmodified partition map because I truly don't know what it will be on the MT3G

I modified the partition table data structure to "91 27" from a stock dream configuration.. but I know when the SPL runs on a Sapphire board it also modifies this partition table.. I don't know what the result is or if the result is stable (thus I recommended not using 1.33.0013d on the sapphire.)

The reason for the modification is 1.33.0013 is a perfected SPL; 1.33.0013d is a bit less perfect (as mentioned in the op): Because running customMTD without fastboot erase is annoying; and without ~90MB system most recent roms won't install. (So its very hard for me to support 1.33.0013 without the modifications on the Dream)

1.33.0013d however on a dream has a 91MB system ready for nearly all current roms; and fastboot erase works simplifying CustomMTD even if other fastboot commands are still missing [if they existed I'd have enabled them].
[G1 Android Development] nlysurferdude03:
ok so now with that being said, should i go back here to the first line and install that spl and continue to the ota froyo and market fix? i can't seem to get that root method to work though as i have already tried a few times this morning. by the way, thank you so much for taking the time out to explain all this to me. ive been a long time reader and hardly post but now this just kicked my a$$ and ripped me a new one. thanks again, i really appreciate it.
[G1 Android Development] tnpapadakos:
somebody make an all-in-one.zip that flashes proper spl/new radio/recovery/cm6.1rc for the Magic:D

now that would be exciting
[G1 Android Development] ezterry:
ANd probably significantly increase the brick count.
[G1 Android Development] sparksco:
There's no arguing, I'm just pointing out that dalvik-cache on sd-ext doesn't make my phone slow
[G1 Android Development] Phateless:
Lol, so true!

Thanks for the tip, will definitely check that out. I always assumed that running both those apps together would push everything else out of memory.
[G1 Android Development] AndDiSa:
... but slower then having dalvik-cache on internal nand. Access time to sd-card is slower than access time to internal nand, this has an impact on speed. Even if phone speed is always something relative.

Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
[G1 Android Development] Firerat:
it will,

I'm assuming Pandora runs as a service, else I would have told you point blank that you can't run both at the same time