yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
* I don't know what "deal sleep" is (ie what your program is looking at) to the best of my knowledge the kernel is sleeping.

* roaming on your carrier may have had a different default but as most things ezgb by default uses that of aosp.. and thus that is what is it.. and quite frankly always has on the dream.
[G1 Android Development] Frodo1910:
Well I used zip themer and i think that flashing theme from recovery is the only one form of getting a change,thank you etzerry :D
[G1 Android Development] kruijs:
Yeah, "data roaming on" also caught me by surprise, taught myself to immediately disable it when testing new builds :)

Regarding "deep sleep", how do you conclude the kernel is sleeping? I used "CPU spy" and "BetterBatteryStats" and concluded that the phone does not reach the "deep sleep" state where the phone cpu is really off.

However, in my (our?) case the phone defaults to screen off, with "CPU Spy" showing it is still actually on, at the minimum CPU frequency, instead of in "deep sleep". (untill I remove the SD card, when it *does* go to deep sleep)

*Update*

Just tested Froyo by Laszlo, updated with your latest Froyo kernel ( 2.6.36, 1.5.2), and also there *no deep sleep!* (until removal of sdcard, which again enables deep sleep, just like in all gingerbread roms)

Laszlo's first post states he's using your kernel 2.6.34.8, so I guess some changes were made between 2.6.34.8 and 2.6.36.152 that might have introduced the "no deep sleep" issue, since it was deep sleeping with sdcard in 2.6.34.8...

Ezterry, would you still be able to track down the changes in your kernel that might have changed sleep behavior / SDcard behavior or is that a lot of work?

Anyway, I'll try to play with some logcat and stuff, see if I can find out some more details. :)

Cheers,

Robbert

P.S. Would love to hear from others out there to confirm this deep sleep/sdcard issue is a *general* issue, before ezterry wastes his time looking for changes in his kernel that may only affect my phone/SDcard...
[G1 Android Development] hrk:
1. He means this: SystemClock.elapsedRealtime() - SystemClock.uptimeMillis()

2. Just FYI: I wiped clean the Dream yesterday and noticed the Roaming ON before putting a SIM card inside. I'm using ADS' build. At the same time, I configured a Motorola Defy w/ CM7.1 and it was OFF by default.
[G1 Android Development] russell.nash:
I cannot confirm that the device deep sleeps without sdcard. I pulled it 15 mins ago and still no deep sleep according to "cpu spy". I have to say that I use the device only as standby mobile and rarely do anything with it. It contains almost no relevant apps besides SetCPU with profiles. It has data network off and uses wlan only when screen is on. And it does not use 3G. So it is really only a dead brick most of the time. Nevertheless most runtime is at 128 MHz (98%, SetCPU enabled).

I looked at the issue only because I have the impression that the battery should last remarkably longer for a device doing nothing.
[G1 Android Development] kruijs:
That's strange!...

For me the "remove SD card to get deep sleep" was really consistent over 3 Gingerbread and one Froyo build (at least as long as latest ezterry kernel was used in Froyo build...)

All was testing directly after flashing (after superwipe v2), all ROMS had wifi off, data off, 2G only, did not even log into google account yet, just installed CPU spy on top of bare ROM. CPU settings as default by ROM.

(just a dumb check, but you did "refresh" the CPU spy after 15 minutes, right?)

If you're interested, you could check BetterBatteryStats to see what is generating the partial/kernel wakelock events keeping the device from sleeping.

Final thing for me will be to check if it's persistent on a couple of other SDcards I have lying around, but I still hope someone else picks up on this, since I'm quite stumped, tried to look at some logcat / dmesg logs, but have to admit I'm completely out of my depth there...

Cheers,

Robbert
[G1 Android Development] clonerep:
My phone randomly turns off and my battery is usually drained, upon restarting. I'm not sure if its the ROM, kernel, CPU/board, or battery. Altough, I've recently had this problem, on a smaller scale, with multiple ROMs and kernels.Any suggestions?

officially, unofficial
[G1 Android Development] homais:
rom has been very stable
[G1 Android Development] coenna:
Hi, when I flashed "gprs_patch_S.zip" I got this text:

"install gprsclass=12?

Faster on many providers

than the default 10

Yes - to update to 12

No - to revert to 10

- yes

- no

E:Missing bitmap progress_empty

(Code -1)

E:Missing bitmap progress_fill

(Code -1)

choice: yesno loaded!!

gprs settings?"

Is that supposed to show up? If so then consider adding info on that to the guide in the first thread post. I picked "yes" - hope that was the right choice!
[G1 Android Development] Valwit:
seems to be quite ok. for sure way better then cm 6.1 i had before. :)
[G1 Android Development] GuyInDogSuit:
Any good flashable themes that could work with this? I used to use LunarUI but that requires the T-Mobile Theme Manager/Chooser. Unless ezTerry can put those in his ROM....?
[G1 Android Development] chakar.dee:
Why don't you make your own theme with UOT theme kitchen on http://uot.dakra.lt ?
[G1 Android Development] GuyInDogSuit:
I've tried. I can't make anything as cool as LunarUI though.
[G1 Android Development] greeneyes2910:
Bugs

Hi Terry,

I´m a little bit confused... I´have to say that is almost stabelst rom i´ve tried but it´s so far the only once, where i can´t install every app , I want to... For Example Whatsapp Messenger ~ i´ve tried many versions but every one couldn´t install... I´ve tried Andisa Romversion, too... There It installs, but there fore other apps, won´t install... Have you got an idea, why this happens`?
[G1 Android Development] ezterry:
50% of the time I see these reports it works for me.. the other 50% are market restrictions... or real can't be fixed incompatibilities.

All I can say is fix permissions, clear dalvik cache, if market is blocking it try to install via the website to see why market thinks the phone is not compatible, if it just errored out restart and try again, and look at your logcat for more information on any errors.

My experience is I have much more problem running apps (that no longer work on our old phone with limited ram) than installing them.. but it could also be silly things such as your market version, (The one with the rom is ok, and the newest one Google sent me has been maybe a bit slow but I've not had a problem.. no promises if you are somehow stuck inbetween) it can also be a problem if you did not wipe when coming from another rom, or restored too much system data with titanium.

Also check your free space and default install locations/ apps2ext settings
[G1 Android Development] greeneyes2910:
Oh, I forgot to explain, that the bug already exist by installing via adb or even with root explorer (i have many apps located on sdcard) ... whatsapp is only an exampel ~ there are some more apps, with same bug... They already could installed on some other 2.3.7 roms , e.g cyanogenmod... But nevertheless, your work on this rom is more than perfect so far :)
[G1 Android Development] ezterry:
Did you remember to enable non market sources? Other comments about how to solve it yourself apply 2x for those not using market however.

No problems for me intalling things with the included File Manager, sometimes issues with adb but that is usually a faulty USB wire I have around.. (and more rarely memory over-utalization if the phone is still loading things after boot.)

(I am assuming properly signed applications and they are not from say another rom needing system user access.. Whats app messenger installed cleanly for my from market.. there is not much else I can test for all I know you found a bug or bad assumption in root explorer)
[G1 Android Development] GuyInDogSuit:
The only thing I miss in this ROM is the CM7 settings (volume attenuation, "always play over speaker" hacks, etc) and the Theme Manager. Other than that, this is one helluva solid ROM!
[G1 Android Development] #2!:
Is it possible to get wifi calling to work on this rom? It works perfectly on Froyo by Laszlo with the update provided in this thread:1224658. But I would like to be able to use it with this rom.
[G1 Android Development] ezterry:
The built in SIP voip calling has been working in this rom for only about 12 months.

Both on wifi and if your 3g network is fast enough.
[G1 Android Development] #2!:
The reason I use wifi calling is because I live in a semi-dead zone and usually can't send texts or call without it turned on. Or it tries and error's out. I'm not trying to make and receive free phone calls, just need to be able to use my phone # from home.

I appreciate the reply's!
[G1 Android Development] OpenMinded:
Whatever i do, i cannot get gapps installed?

They just do not show up?!

Any help?

I did a full wipe
[G1 Android Development] GuyInDogSuit:
Make sure you're using the latest Gapps for your Android version. I assume you're on this ROM, correct? I'm using this Gapps and it works just fine for me.

---------- Post added at 06:49 PM ---------- Previous post was at 06:42 PM ----------

How do you get texts over WiFi? If my data network is disabled or unable to connect for any reason, my texts don't send even on a WiFi connection.

As far as internet calling, I've never had luck getting it to work. You could try Google Voice, which allows texting and voice calls, but not MMS (that's what email is for). Skype apparently works well, too, though I think they charge, even for domestic calls.
[G1 Android Development] ezterry:
Wipe , install rom, install g-apps as per OP

(This will work unless you did not fully wipe a prvious install, or have a very odd cMTD set.)
[G1 Android Development] DelBoy:
Are CM settings included in this rom(tweaking settings)?
[G1 Android Development] AndDiSa:
No, you will have almost only AOSP ... plus some minor merges / kangs from CM.
[G1 Android Development] cmoi_ca:
Thank you ezterry for your awesome rom, however I'm experiencing with the 1.0 release some random reboots(5 times a day), I've installed a fresh copy and the problem didn't go. I have mytouch 3G and that problem never been so frequent with previous releases.
[G1 Android Development] GuyInDogSuit:
Any apps you installed recently that might have caused it? I'm running this ROM and it's been working just fine for me. Only issue I have is occasionally the status bar disappears (crashes?).
[G1 Android Development] #2!:
If you have the Tmobile wifi calling app installed and working you can send and receive just like it would on a cell network connection. When wifi calling is enabled and connects to the Tmobile server it will automatically turn off the cell radio and also turn it back on as soon as the connection is lost. You must have a valid sim and it does use plan minutes.
[G1 Android Development] ezterry:
Well you can try the same steps as the froyo roms (the files being replaced are the propritary ones from HTC.. and have not changed between froyo and gingerbread.

I can't exactly test this however not being on t-mobile, and more interested in my VoIP working (not free but much cheaper than rogers international long distance) if I care at all.. So best is to do your own experimentations and accept the risks it may not work
[G1 Android Development] cmoi_ca:
thanks, I'll check my recent installed apps :) . About the status bar, if you're using zeam launcher, there's a shortcut that can be defined in preferences to hide and show the status bar, it could be the answer :)
[G1 Android Development] GuyInDogSuit:
Nope, I'm using ADW.
[G1 Android Development] cmoi_ca:
Turned out the overclocking did that, just decreased the frequency and all fine again :)
[G1 Android Development] ruben_b:
Just trying to install this ROM on my wifes old 32b Sapphire with Radio-2.22.28.25 and SPL 1.33.0013

It's already rooted and CWM is installed using ROM Manager.

When I'm trying to install it using ROM Manager, it reboots and is stuck on the screen with the exclamation mark. I'm then pressing Home+Power and it moves on, but doesn't install.

When I rename it to "Update.zip" and try to install it directly via the revovery, it doesn't work to (signature error).

I'm used to flashing ROMs using my Desire or GNex, but the Magic gives me a really hard time...

Any hints on what I'm doing wrong?
[G1 Android Development] GuyInDogSuit:
The download may be corrupt. Try downloading again. Also make sure you wipe beforehand.
[G1 Android Development] tvall:
Clockworkmod doesn't seem to be installed. Try flashing again
[G1 Android Development] ruben_b:
I've checked the md5sum of the ROM, so the file should be OK, but will download it again.

CWM is installed, but only an old version without the option to choose a zip file. It only has the option to use the update.zip.

Haven't found a current version of CWM for the Magic.

Edit:

The CWM is really missing. Thought the installation worked and it's an old version, but it's the stock one.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[G1 Android Development] GuyInDogSuit:
The latest version for the Magic is 2.5.0.7. Just flash it again in ROM Manager.
[G1 Android Development] vuvantuan59:
You can work Language

Vietnamese ! Thanks ....rom run verry fast !

Sent from my Gingerbread on Dream
[G1 Android Development] frankdrey:
I've seen the yesno binary in two updater zips so far

the gprs update thing and sense lx recovery...

I've been told its by you ezterry

Can I use it?

If yes, where would you like credit?
[G1 Android Development] BitPlacebo:
Issues Installing

I'd like advice on why I can't seem to flash the recommended radio/SPL? Is there something else I need to do?

I'm having an issue flashing my G1 Dream to the required starting point radio-2.22.27.08.img/hboot-1_33_2003.img.

I flashed it to CM4 awhile ago (see radio and SPL info below). I can't seem to flash any of the newer ROMs like EZGingerbread using the Installation Guide.

I was recently able to flash the recovery-RA-dream-v1.7.0-cyan.img using a different custom recovery (JF I think) console previously installed when I did the CM4. I am trying to fastboot flash the radio and hboot images but I'm getting an "FAILED (remote: partition does not exist)".

I also tried flashing these images using the recovery console, but got "can't find radio partition".

My partitions:

1 start:32.3KB end:15.0GB Size:15.0GB type:primary fat32

2 start:15.0GB end:16.1GB Size:1069MB type:primary ext2

Here is additional phone information:

G1 D32 GB Data:

DREA100PVT 32GB

HSPL 10.95.3000

CPLD-4

Radio 2.22.19.26I

Any ideas?

Thanks.
[G1 Android Development] frankdrey:
Yes. I think first you need an spl that actually supports flashing those.

Install danger spl

Google for "g1 dangerspl cyanogenmod wiki"
[G1 Android Development] frankdrey:
Huh never mind dont.

I'm not thinking straight
[G1 Android Development] BitPlacebo:
Awww. I got excited when you told me to flash DangerSPL. But it sounds like you changed your mind.

I keep finding contradictory info and nothing definite on this issue.

I went to this thread:http://forum.cyanogenmod.com/topic/278-installation-support-line-cyanogenmod-for-dreammagic/

which then lead me to this thread on Flashing AnySPL (NoneDanger):

http://xdaforums.com/showthread.php?t=692614

He says not to use flash_image in the console, but that is what I used to flash the new recovery. It seems to work fine.
[G1 Android Development] frankdrey:
Well I thought that your spl that you had right now didn't support fastboot flashing. But someone pmed me that its otherwise and that dangerspl will brick you. So I got worried and said never mind. But then I noticed that you do have a dangerspl compatible radio. So if you make sure you have the right radio you should be good. Not sure if dangerspl will fix your problems

I always go from stock rc29 > cm6 setup (dangerspl) > 2708 kernel

Works fine. I've flashed my g1 so much already:P

Ehhh but still...be careful...read carefully
[G1 Android Development] hrk:
Bold is mine. Don't take it bad but... W(here)TF did you get that "required starting point"? Not here.

Follow ezTerry's post with the right RADIO and HBOOT/SPL and you'll avoid harming your phone. If you can't get your numbers straight, don't even try or you'll brick your phone.

Once you have the right combo of RADIO and HBOOT you can safely follow the first post in this very topic and enjoy some ezGingerbread!

Sorry if I sounded rude.
[G1 Android Development] Firerat:
post the logcat, so I can look at it

( pastebin pls )

once you have done init and repo sync

AndroSrc=$(pwd)
# dalvikvm stuff
cd dalvik
git remote add -t Magpie -f Magie git://github.com/Firerat/GB_dalvik.git
git checkout Magpie/Magpie
git merge m/gingerbread
cd $AndroSrc

# frameworks
cd framework/base
git remote add -t gingerbread -f Magpie git://github.com/Firerat/GB-framework_base.git
git checkout Magpie/gingerbread
git merge gh/gingerbread
cd $AndroSrc

# apps settings
cd packages/apps/Settings
git remote add -t Magpie -f Magpie git://github.com/Firerat/GB_packages_apps_Settings.git
git checkout Magpie/Magpie
git merge m/gingerbread
cd $AndroSrc

# device setup
cd device/htc/dream-sapphire
git remote add -t gingerbread -f Magpie git://github.com/Firerat/GB-device_htc_dream-sapphire.git
git checkout Magpie/gingerbread
git merge gh/gingerbread
cd $AndroSrc

# system code # no longer required, use the repo's branch
# but you may like to watch it on github, just in case I add something fun
[STRIKE]cd system/core
git remote add -t Magpie -f Magpie git://github.com/Firerat/GB_system_core.git
git merge m/gingerbread[/STRIKE]

cd $AndroSrc
echo "TINY_TOOLBOX := true" >> buildspec.mk

if you repo sync you will leave those branches, repeat but no need to re add branches

AndroSrc=$(pwd)
# dalvikvm stuff
cd dalvik
git checkout Magpie/Magpie
git merge m/gingerbread
cd $AndroSrc

# frameworks
cd framework/base
git checkout Magpie/gingerbread
git merge gh/gingerbread
cd $AndroSrc

# apps settings
cd packages/apps/Settings
git checkout Magpie/Magpie
git merge m/gingerbread
cd $AndroSrc

# device setup
cd device/htc/dream-sapphire
git checkout Magpie/gingerbread
git merge gh/gingerbread
cd $AndroSrc

[STRIKE]# system core
cd system/core
git merge m/gingerbread[/STRIKE]

cd $AndroSrc

you could amend the default.xml, but the above is a bit more flexible, as it reduces the chances of conflicts should the 'official' repo change

e.g. My branches get folked and become part of the repo

should that happen you just need to skip the relevant section and just track the main repo's branch

I can cherry pick from the main repo, and the main repo can cherry pick mine

NOTE:

the above does not include AutoKernel

or the backuptool I kanged from CM
[G1 Android Development] flyers00:
I downloaded and flashed magpie-gb on my g1 and its been working out great so far. My gmail has been working and the only thing missing is gps. Hopefully you guys will sort it and get it working. Great job ezterry,firerat and all others involved
[G1 Android Development] Firerat:
gmail is working?

does it not fall over when you read an email, after 5-10 seconds?
[G1 Android Development] flyers00:
I stand corrected,gmail is failing after reading the 2nd or 3rd email. Sorry for the false hope that it was working correctly.
[G1 Android Development] jsp254:
your links are broken. please update them
[G1 Android Development] Kefir.net:
Running good on my Magic 32A!

The only problem is freezing and slow animations. It's because graphics HW acceleration doesn't work?..
[G1 Android Development] claude96:
Thank you ezterry for your reply,as for the kernel I tried ( pershoot 2635.10_ds_32a-oc-uv-xtra-ram-fp-122010 ), for the rest of the steps I did all that with all your 3 alphas, it worked with the first one but not the others !

btw I flash nd reboot superwipe 2 times b4 flashing,so I'll try again nd provide a log if possible,thanks again.
[G1 Android Development] jsp254:
I saw somewhere the someone had ported the GB gapps over to the eris. I think it was dated 20110107. Had mdpi in the title. Would this take a lot of work to port it over to d/s? Would it have to be modified at all since it's mdpi?

I downloaded it but I'm hesitant to try flashing it.
[G1 Android Development] lele5800:
please tell me how to run the last release on my magic 32A ...

i have:

flashed the rom dated 01/07/2011 then flashed the pershoot kernel (that works good on the first release)

and restart the phone..

it show me the boot animation and the phisical key light On , but it stay on boot animation, i think forever, i wait 25 minutes...please help me, thanks!

and sorry for my bad english.. :D
[G1 Android Development] ezterry:
It was in the post with the link:

If you are still lost please wait for a sightly supported beta build we are still on alpha nighties here.

I won't trust any gapps myself until I validate/create a package .. but try it and let us know if its worth anything.. others in this thread also have gapp packages floating around.
[G1 Android Development] nomadman:
nothing nandroid cant fix. do u have a link?

this be it: http://xdaforums.com/showthread.php?t=864403

edit/

i had to manually push all the /system contents of the archive. i did exclude some large apks like maps due to low space. but the gut of gapps isnt giving me any problems so far. oh, btw, i get a fc with browser. no a problem to fix..
[G1 Android Development] AndDiSa:
I flashed GB-magpie yesterday ... for an alpha version it's running very well. Almost all of my "old" apps from the /sd-ext partition were installed automatically. Congratulations!

Beside the problems already posted here (slow 3D, Gmail-looping, GPS not working), I noticed, that e2fsck is not included within the ROM. It's not a big thing, but this may lead to the situation that /sd-ext is not mounted on startup (which happened to me due to a unclean unmount). I pushed e2fsck and some libs manually using the version from CM6.1 and afterwards it was working without problems.
[G1 Android Development] dillalade:
Sometimes best to read the entire thread regardless - keep your own understanding up to speed ;)

Post 42 regarding browser fix

Post 1002 on this thread (which was posted in this current thread by someone)

http://xdaforums.com/showpost.php?p=9288746&postcount=1002

[2nd code to be run in Terminal - locks my ADW firmly in memory, no lag in Home retrieval.]

Enjoy

(If the Post 1002 link doesnt appear/broken, then I'm not certain whats going on, Im simply copying/pasting the link into this text box.)
[G1 Android Development] Firerat:
it is probably because system wasn't clean

for some reason format system is not working,

I worked around that in the Magpie build by added a rm /system/* to the backuptool.sh

this has made my lazy :(

but like Ezterry says, a superwipe should fix it on a stock build

Edit:

thinking about it, my hack will not work if you are not flashing it over a previous GB build, as the backup function doesn't run if its not Android 2.3.1

( didn't want to backup/restore incompatible gapps )