yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] surfwaimea:
SMS received time

Seems that the old problem that for SMS it's showed sent time instead of received time hase been resolved for Galaxy S.

How could we get it in CM6.1 for Dream and Magic?
[G1 Android Development] plumppp:
Weak excuse!!! Sounds to me like they're just GIVING UP on us!!!

If it can be done, DO IT!!!

Thanks to ez terry firerat and others, Gingerbread. Will. Happen!!! :D

Technically it has already happen!!! and its Only Gonna Get Better!!!

I don't know about YOU! but my G1 hasn't reached its limit!!! :D
[G1 Android Development] Firerat:
all I've done is add a Magpie into ezterry's build

Ezyterry has done all the hardwork

And yes, gb is running just fine on my G1
[G1 Android Development] ad505:
SWEET! I got a g2 and am not looking back (c:

Sent from my rooted HTC Vision running cm6.1.1
[G1 Android Development] _zygo_:
Then I say you should knock yourself out and start developing! Good luck with that.

Really, is it any surprise that support is being dropped? Fewer and fewer of the devices are in operation. I don't mean to denigrate the G1. I am not saying it is an outdated device or not worthy of continued development. But, at some point, there comes a time when the user base falls below a threshold not worth supporting. If I owned a G1, I would have been looking to upgrade the device. My original MyTouch 3G looks and operates like new (I run CM 4.2.15.1,) and I am perfectly happy with the device. It still makes and receives calls and texts perfectly, runs Touchdown and Google Voice just fine, and I can still use Maps just like I could a year ago. Anything beyond the basics for devices that are now a year and a half and over two years old is gravy. Yeah, it would be cool if flashing CM could magically turn your phone into a Nexus, but it doesn't work that way. Enjoy what you have for now until you buy a new, supported device.

I don't think Steve reads these forums anymore, but if he does, I'd like him to know that I appreciate the ROMs and support since rooting and flashing his ROM in August 2009. My wife says jacking around with the phone has kept me off the streets and out of trouble (haha.) So rather than whine and complain and demand action, show some appreciation and gratitude for the great products and service you have been provided for free while the device was supported.
[G1 Android Development] ad505:
I just wanted to thank everybody, again, for all the help I have always received on these forums. All you guys rock! Anyone update to a new device yet?

Sent from my rooted HTC Vision running cm6.1.1
[G1 Android Development] cmcmyers:
I actually own a HD2 running Android, I got the G1 as a gift for my GF and with this Rom she's loving it... Thank You!!
[G1 Android Development] cinek1987cinek:
I use 6.1.0 stable + boot-cm_2635.10_ds_32a-oc-uv-xtra-ram-fp-122010. Great combination :-)

Thanks !!!!! :-)

// tapnięto przy pomocy HtcMagic_CM6.1.0_TapatalkPRO.
[G1 Android Development] my_former_self:
Agreed. On everything. It is so nice to hear the friendly echo of logic once in a great while rather than the resounding clang of answer-less complaining.

Cyanogen and team have done tons for us and even if he chooses to cease work on G1's & MT3G's right now, we still currently have 3 different stable ROMS to choose from; 1.6+, 2.1 & 2.2 - aka - CM4.2.15.1, CM5.0.8 & CM6.1.0, respectively.

Like _zygo_ said, "Enjoy what you have for now until you buy a new, supported device", start developing your own ROM or just stuff it because you're getting some pretty awesome stuff from Cyanogen...FOR FREE. I just cannot believe how ungrateful people are.

+1 to you, _zygo_. You're awesome, man.
[G1 Android Development] hrk:
Not to piss off anyone, but I'd like to point out that I haven't heard any echo of logic here, from both parties.

I have heard the ungrateful rant of a very poor (as in spirit, not money) person, and the fallacy of "I-am-oh-so-logic" of unknowingly-consumistic-driven people.

I am very grateful to Cyanogen & Team for all the work they've done, I would never, ever, complain to them if they dropped support for my G1 -which they did due to reasonable, understandable lack of interest- and moved on with more pleasant stuff.

I don't think, however, that two years is a reasonable age for a phone to die. My previous mobiles lasted way longer, and died of... "key broke", "battery worn out" and not "you should feel obsolete, and guilty, so buy a new phone from us". I have had a Pentium 200 MMX serve as my home server up to last year (1995-2010), when I replaced it because of.... it was noisy and my brother-in-law was tossing away a new (silent) computer.

I do not want to tell you you're wrong in following consumism but... what does it have to do with the BBQ of CyanogenMod-6.1 "they said it couldn't be done"? I don't want to hear it as much I don't want to hear ungrateful and silly comments about how Cyanogen & Team should spend their time. Can we drop both, please?
[G1 Android Development] tnpapadakos:
i went through a similar dilemma when everyone moved from win98se to xp (tongue in cheek)

its called end of life and product life cycle management

if your dream/sapphire is running well on the last rc or nightly and you're happy with it, just keep using it (seriously, i am with device #1, check my sig)

if you want a new OS like gingerbread and 3 or 4 times the RAM and a cpu that can clock at 1.8 Ghz move to a newer device (device #2)

although i cant imagine why we would want that...
[G1 Android Development] Firerat:
Ezterry has started something great on xda

a source repo for gingerbread dream/sapphire

its very much a 'support yourself' affair

but if you are smart and post logcats, then some attention may be paid to it

within that thread are my Magpie builds, basically they are Ezterry's builds with CM5 like a2sdext ( Magpie ) added in.

some very kewl features with these builds

Ezterry has recently added AutoKernel to the build system ( far superior to the script based AutoKernel I cobbled together )

this means that one zip supports three different kernel types

ebi0 ( standard 32b )

ebi1 ( 32a and Rogers )

2708 ( 32b with the extra 15mb ram )

the correct kernel is installed automatically

GPS is working

gapps and su working ( see bypass's posts in the thread )

internet calling ( see call settings in settings )

gmail has a bug, where you can't read 'long' emails , but the basic email app works fine

other stuff I can't remember

in general the ROM works very well,

it doesn't have all the extra features people have come to expect from a CM, the main reason ( and I have to agree here ) is that ezterry wants a clean base, and some of the extras impinge on performance without any real gain.

if you look at ezterry's issues list on github you will see that he has indicated that he wants to shift the current build system towards one more akin to CM's , so that it can at some point be integrated with CM7

Find

ezterry's builds in post 2

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

The current Magpie can be found here

http://xdaforums.com/showthread.php?p=10678784#post10678784

it is based on Ezterry's 2011-01-17 code

Magpie zips can be found here

http://www.mediafire.com/?0uefg5g8kyeja

regards gapps, look in that thread

I'll look at putting up some gapps zips

personally I like the minimum on system, getting most from Market

so I'll do SuperTiny, Tiny and Full Fat ( might skip the full fat , and just package extra bloat to flash over a SuperTiny )

some of the gapps that are being linked in that thread are not great, they include hdmi which is just a waste of space for us

so what are you waiting for?

nand backup and get flashing

and if you have 15-20 gb free on a Linux box, repo sync , and push some kewl changes to github ;)
[G1 Android Development] my_former_self:
Yawn. :rolleyes: Justin Timblerlake wrote a song for you.

Well said. It's not like we don't have a plethora of ROMS to choose from, like you said (RC, Nightly, Stable, etc).

Awesome! Love that dude.
[G1 Android Development] almostthere:
Not for the beginners who are not willing to search and google around I assure you
[G1 Android Development] King Royalty:
I have HSPL10.95.3000

Will I be able to flash this ROM?
[G1 Android Development] Firerat:
yes,

but it won't work

system is too small

kernel won't boot

solutions

you could use customMTD to get round that

compile yourown kernel and make the zImage smaller, i.e. have more modules

but, tbh you should seek out Ezterry's 2708 thread,
[G1 Android Development] s14evil:
This rom is killing my battery. I get about 4 hours of not using time. Have to keep using taskkiller. It keeps running things I'm not using.....
[G1 Android Development] almostthere:
It's not a ROM issue. It's how you config and what widgets you're running. Mine previously on the latest build lasts me 11 hours a day with data on
[G1 Android Development] s14evil:
So I should have no widges on my home screen, and how did you config yours. I would love at less 8 hours a day.
[G1 Android Development] almostthere:
Previously had about 8 widgets running (clockr, date, tweeter, news, calendar, setCPU, battery and power control) and yet had at least 10 hours 3g enabled but about one hour fb surfing and web browsing. Why not try my_former_self's guide linked in my sig to boost up? Besides that do a battery stats wipe. How to is also in the guide.

Hope that helps
[G1 Android Development] my_former_self:
Guide update!

Updated the guide. Mostly just a few minor revisions to SetCPU settings, a comment on how to easily enable swap (if you want to) and the inclusion of the swap script in the package (which the guide links to).

Unfortunately, MediaFire's free account only allows so many updates of links (to maintain the same link). So, irritably, the link to my guide has changed. You can find the updated link in my signature. Sorry to everyone who links to it in there's; you'll have to change it until I find a different hosting provider (or I just create a new user account on MediaFire...heh heh).
[G1 Android Development] Firerat:
mediafire lets you maintain one folder 'shortcut'

so link the folder and have as many revisions as you like ;)

also

tinyurl has a handy feature, link a mediafire folder with a memorable name ;)
[G1 Android Development] my_former_self:
Hmm. Good point. Hold on...done! OK, folks, link in my my sig changed, but for the last time, thanks to Firerat.

Thanks, rat. As always, you're the man.
[G1 Android Development] mackdaddy187:
Is there another download link? cyanogen links for Dream are down.
[G1 Android Development] Phateless:
They're not still up the Cyanogen wiki?
[G1 Android Development] mackdaddy187:
Nope, it goes to an error page.
[G1 Android Development] IKoRuPT:
You can download my_former_self's Super Pack (click the Ultimate Setup Guide in his signature), which includes the file along with others you might find useful.
[G1 Android Development] delyorik:
Alright, so maybe I'm missing something here. I recently updated the radio/kernel on my phone to what's in my signature. I could swear I remember booting into recovery afterwards. Now I can't (any recovery, not just RA - I flashed Clockwork as well, no go). Is 0013d the issue? I've got plenty of backups in case I "need" to start over with .nbh, but I'm kinda (obviously) not looking forward to the downtime, heh. Tips?
[G1 Android Development] G1sanju:
Its a known issue, flashing recovery from CM5 and CM6 doesn't work most of the time. 0013d does not have a flashing capability so you can't use fastboot also. You can check the thread for 2708 radio and 0013d SPL, there are instruction to recover from this situation.

It is as easy as flashing an NBH from the fastboot and flash recovery, radio and SPL from fastboot. restore your latest working backup and you should be ready to go....
[G1 Android Development] ezterry:
cm is booting? you have a HTC 32b Magic? and recovery is failing with 1.33.0013d+2.22.28.25?

If these are true it be nice to know what version of recovery you flashed.. but lets just do it manually in case

1) get Ra-Recovery recovery-RA-sapphire-v1.7.0G.img

2) place on the root of your SD card

3) via adb shell:

erase_image recovery
flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img

if you get an error try running the flash_image command again.

Once done power off, then boot into recovery holding home.
[G1 Android Development] Phateless:
If you're not comfortable (or not set up) with adb you can also run these commands via Terminal Emulator on the phone itself. Just SU first.
[G1 Android Development] delyorik:
You guys are up early, heh. I appreciate all three of your replies. Since I'm not a big fan of multiple posts, I'll just cut/paste replies and stuff.

>>Its a known issue, flashing recovery from CM5 and CM6 doesn't work most of the time. -- G1sanju

Before the radio/spl change, I was already running CM 6.0Stable. It was just a radio/spl change from 1.33.2005/2.22.19.26I.

>>cm is booting? you have a HTC 32b Magic? and recovery is failing with 1.33.0013d+2.22.28.25? -- ezterry

Yup, yup, and yup.

>>If these are true it be nice to know what version of recovery you flashed.. but lets just do it manually in case -- ezterry

Followed those instructs and got the same results as I have before: RA tries to come up, but all it does is show Build : RA-sapphire-v1.7.0G on the bottom of the screen, and nothing else. RA 1.7.0G is the one I've used since it came out - only reason I flashed Clockwork was I read another thread saying that it might be possible to reflash RA using Clock and get it to work. No dice. It's puzzling. After the recovery freeze, I do a battery pull and then reboot.

Something of note: each time the phone boots (from power down, bootloader, or failed recovery attempt), the phone goes to the green mytouch screen, blacks out, reboots to the green screen, then boots as normal. Kinda weird, so a sign that something's borked somewhere (heh). What's nutty is that the phone works perfectly fine (internet, games, market, phone calls, texts, email, etc.), so I'm almost tempted to just leave well enough alone - almost. ;)

The only thing I haven't yet done is a complete fastboot wipe (that'll be my last option since I have viable backups and whatnot) and just start over again. No big deal in the end, but obviously it'd be cool to avoid, heh.

>>If you're not comfortable (or not set up) with adb you can also run these commands via Terminal Emulator on the phone itself. Just SU first. -- Phateless

Nah, I'm cool with ADB. I'm just puzzled as to why recovery is freezing when it tries to load, heh.
[G1 Android Development] Firerat:
my guess is you flashed recovery with rom manager

just flash it with fastboot
[G1 Android Development] Phateless:
I thought 0013 and 0013d SPLs are perfected and won't allow a fastboot flash?
[G1 Android Development] Firerat:
true,,

I had the guy who bricked still in my head :)

but still, the solution is fastboot ( after reverting with nbh )

but if there is a working rom, then via adb shell

stop zygote
flash_image recovery /sdcard/recovery.img
reboot

this works because Android is not running, so you have plenty of memory

there is a script on cm forums which will do all that for you

target was people who can't use adb shell
[G1 Android Development] Phateless:
Agreed. Does the stock SPL allow fastboot flashing? So nbh back to stock, flash an engineering SPL, then fastboot flash the recovery, restore your nandroid and go on with your life?

Are there any engineering SPLs compatible with the new radio/kernels?
[G1 Android Development] my_former_self:
If you're "cool with ADB," and you can get into your ROM, like you said, then just do what rat said; flash via ADB. Way easier and FAR less time consuming than NBH-ing it just to get "fastboot flash recovery" back.

As to why recovery is freezing, I'd almost be certain it's because you flashed from CM5 or CM6. Like it was said, it's a known memory issue. Most likely, the recovery image got garbled during the flash. It happens. You're not the first.

So, ADB that bad boy and you should be fine. Let us know how it goes.
[G1 Android Development] delyorik:
Nah, still freezes. Even tried flashing my original 1.5.2 from my first rooting, but it still froze. I'm prolly gonna have to nbh. In the meanwhile, the phone still works as previously mentioned, so I still get to text/call/play Scrabble/etc., heh! Battery life sucks (my original reason for wanting to go to recovery last night/this morning was to wipe battery stats!), but as long as I'm mindful of what I'm doing, it'll be fine 'til I get a full day at home to play with it.

Cheers, guys. I'll let you know what gives afterwards. And thanks.
[G1 Android Development] Firerat:
su
rm /data/system/batterystats.bin

tbh, it won't actually do anything for battery life, but ^^ look it is easy
[G1 Android Development] delyorik:
Thanks Firerat, heh. Think I'll prolly just do the whole phone over after work on sunday.

Cheers fellas.
[G1 Android Development] hrk:
3D not working?

I updated the Nexus Revamped Live Wallpaper and it's not working anymore. The author moved the code to OpenGL-ES and I am wondering if it's a problem with the code, my phone capabilities or my setup.

~ # ls -lha /dev/graphics/fb0 /dev/msm_hw3d*
crw-rw---- 1 root graphics 29, 0 Feb 4 20:19 /dev/graphics/fb0
crw-rw-rw- 1 root root 252, 1 Feb 4 20:19 /dev/msm_hw3dc
crw-rw---- 1 system graphics 252, 0 Feb 4 20:19 /dev/msm_hw3dm

I remember there was some talk about changing 3d permissions, but I can't find anything on the latest firerat script, so I don't know what to check. Can you give me some pointers? Are the above permissions correct?
[G1 Android Development] Phateless:
Do live wallpapers even run half-decently on a G1? On my mt3g I OC'd to 614 and turned off everything I could think of to try to make the thing run faster.
[G1 Android Development] hrk:
It depends on the wallpaper, the previous version of Nexus Revamped worked fine.
[G1 Android Development] _zygo_:
Here is what I do...I just shut my eyes as tight as I can get them for about 30 seconds, then open them and look at my phone's wallpaper real quick. It looks "live" for about 10 seconds. Cooool.
[G1 Android Development] my_former_self:
I spin around in the middle of the room for 30 seconds, then I sit down, turn on my phone. REALLY makes a difference in the movement of the wallpaper, I can't emphasize enough. :D
[G1 Android Development] hrk:
LOL, you're so funny I may try to do it when I'm bored.

BTW, it's working now, it was a bug in the code.
[G1 Android Development] my_former_self:
New goodies!

Been doing a lot of flashing between CM4, CM5 & CM6 lately for various reasons. They've all been "from scratch" setups, even though I have Nandroids. I've been trying to find the "perfect" setup; speed vs usability. Needless-to-say, the hunt is still on :D

I'm settling back down on CM6 right now and have been working with it a bit today and tonight. Along the way, I got really tired of uninstalling "needless" apps every time I did a "from scratch" install (which is purposeful). So, my weariness bore fruit that might help others out (at least on CM6.1).

Whipped up a little program to automate what I call the "de-clutter" process; getting rid of unneeded apps. It's basically a quicker way to get rid of "junk" like Live Wallpaper support, the OI File Manager, Genie Widget, etc. Basically, stuff that takes up space and background resources.

There's some optional stuff in there, too, to give you the opportunity to get rid of the default browser, music app, messaging app, etc, if you are using 3rd party apps for those purposes already. And I included the option to replace the 3D Gallery with the 2D and a Camera fix to make sure the preview panel defaults to the 2D Gallery (always been a popular one). None of this last stuff is done without you telling it to, though. You can opt out of that stuff.

It's a pretty self explanatory program. Very very basic, but it gets the job done. Just follow the link in my sig. I added it to the MFS CM6.1 DS ULTIMATE Setup Stuff link; it's my "dumping ground" for helpful CM6.1 stuff I've done. Just unzip the file ("MFS CM6.1 DE-CLUTTER-ER v2.2.zip") and read the README (duh). Hope it helps someone out! ;)
[G1 Android Development] Phateless:
I can only imagine how CM4 runs with ezterry's 614 kernel and the extra 14mb of ram. :D

Why don't you just open the zip files and remove the apps before flashing?
[G1 Android Development] my_former_self:
1. CM4 blazes w/terry's kernel. Alas, it has no BT Voice Dialing support. Kind of defeats the purpose of a "hands free" BT setup in the car :( Ugh. If only that worked. I have no idea why Google waited until 2.2 to get their acts together and finally make a true hands free BT Voice Dialer. Unfortunately, they also coded it to Froyo. :mad:

2. I use Amon Ra's recovery, which won't flash unsigned zips. Yes, I know I can sign them with a few programs, but I'm an IT guy and I like writing stuff. :D Anyways, this gives people the opportunity to do change some other stuff without fussing too much. We were all newbs once, I'm trying not to forget them.
[G1 Android Development] Phateless:
Yeah I hear you. To be honest I'd be perfectly content to run Donut my whole life if only I could add speech to text in any field. The voice actions in general are just super cool.

I think I'm genuinely bummed that I never tried out CM4 when I had my mt3g. Sometimes I think about getting another one just to play with. The one ROM I truly regret that I never tried out was Dwang's Donut. I have a feeling that would have been THE ROM for me.

Ahh, definitely appreciate the support of the noobies, as I'm not far beyond that stage myself. :) I wish I could go back to Ra recovery, but Clockwork has been fine so far on the MT4G, with the exception of the charging bug which nobody has figured out yet.
[G1 Android Development] my_former_self:
I'd totally run CM4 as a daily driver...if it weren't for the (lack of) voice actions. Heck, replace Launcher.apk with the ADWLauncher EX apk in /system/app and it's like a whole new phone. Kinda crazy how you can take a 3rd party replacement launcher, download it from the Market, then rename it and bam; new system launcher. But the lack of voice, I just can't do sadly.

I started out on CM4 with my MT3G and my wife's G1. I remember when it was experimental and in its 4.1 stages where it ended up with four 9's, I think, by the end :D Before 4.2 rolled out, it was at 4.1.9999. Every 9 I saw added was like a Christmas gift :D Ah, the good ol' days...

We're all newbies in one area of Android or another. Hopefully Clockwork's bug gets figured out. Good recovery, none-the-less. A bit too much for legacy hardware, though. I'm holding out and waiting for the Nexus S's to come down in price a little. Sooooo pretty....:)
[G1 Android Development] Phateless:
Yeah it's wild how much new life these devs have breathed into that ancient device.

Wow, I got into rooting right as CM5.0.7 came out. The first time I booted Eclair onto the MT3G I was like a kid in a candy store with all the new features and settings. It was like getting a whole new phone and I was hooked.

Totally true about newbie-ness. I'm just now starting to get comfortable with adb and fastboot. It's making me want to take computer science classes and try to learn how to do some dev'ing of my own.

Why do you want a Nexus S over a MT4G? I can tell you from the experience of modding my gf's Captivate that I am VERY disappointed with Samsung and their Android efforts. That phone had so much potential but it's let the enthusiasts down in so many ways. GPS issues, NFS file system, ODIN and Kies, etc... It doesn't even have an SPL, if I understand correctly. So no fastboot.

I dunno, my experience with the whole thing makes me really glad I chose an HTC and passed on the Vibrant.

EDIT - Besides, the MT4G has more RAM than the Nexus S and the NS has no external SD slot, no HSPA+, and there's one other thing I'm forgetting that surprised me. I'll think of it later, I'm sure.

EDIT 2 - I've seen MT4Gs on CL in my area for $250. That's pretty damn good for how much phone it is.