yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] hal_9000:
Ok, I'm bored of waiting for the Market update, so I'll install it manually. But I'm still wondering how is supposed that Google was rolling out this update. Anybody using CM6.1 has received this update automatically somehow? :confused:
[G1 Android Development] my_former_self:
Haven't received it yet. Although, I've already got the apk downloaded. Got some time tonight, so I'll probably install it rather than wait. I mean, heck, that's what we've got rooted phones for, right? Gettin' crap before we're supposed to :D
[G1 Android Development] _zygo_:
You aren't going to believe what I have done. I actually find that CM's 4.2.15.1 with that boot image hack runs very well on my phone, so that is what I am using. I have a 16MB swap with 10 swappiness, which seems fine for what I do.

I've tried that TMUS OTA FROYO POS, twice, and I liked CM's 6.1, but there is something about that new radio that causes my phone to reboot about eight times until it gets a good T-Mo signal. Since I live out on the very edge of service, I think that's the problem and this can be like a ten-minute process. There is nothing particularly compelling about Froyo for me. I have been using the old Donut ROM for a week now and I can't think of a thing I am missing from Froyo. Even the latest Maps update and Market update are on my phone, and I didn't get the Market update using stock, OTA.

So my swap and swappiness may not translate to Froyo, but it works great in Donut. I have been testing with 0 swappiness, though, which I never thought to do until I read a post about something else and the guy mentioned 0 swappiness. The jury is still out on that, but so far so good.
[G1 Android Development] cybernetus:
I install Magpie on my phone and I have some problems when I reboot this.

When I install any aplication on the sd-ext and reboot my phone, the phone enter on the first screen and reboot.

The system reboot five or six times.

When I reboot again, the system reboot five or six times, or more ...

Is anyone have this problem ? I see this problem when I apply the Hotfix 002.
[G1 Android Development] my_former_self:
Nah, I do believe it. In fact, I was just thinking the other day about how much I loved 4.2.15.1 (as long a name as it is!). Don't get me wrong, I think Cy & team did a heck of a job on 6.1, but I do remember 4.2.15.1 being blazing fast.

I (or my wife) don't get reboots, but like you said, you live on the edge of service. So, I'm sure the extras of Froyo don't help when an already maxed out phone is looking for a signal.

I might nandroid backup my 6.1 and rock me out some 4.2.15.1 (w/radio enabled kernel) for old time's sake. Never know, maybe I'll stick with it. I've even still got a v1.2 of ADWLauncher's system apk lying around for donut, too.
[G1 Android Development] my_former_self:
Did you make sure to download the DS version of MagPie?

Did you also make sure to apply the Hotfix002 AFTER flashing MagPie?

Did you make sure that it was the Hotfix for MDPI and not HDPI?

Did you wipe the Dalvik-Cache or run a fix_permissions?
[G1 Android Development] my_former_self:
Guide Update!

Updated the guide again. I did a little reading on SetCPU and how Android handles it as a process. Apparently, profiles help to register it as a background process and prevent Android from killing it. At least in theory :rolleyes: So...

Changelog:

Small revisions to the SetCPU settings.

Profiles are now recommended to be enabled to prevent Android from killing SetCPU's process.

Profiles should be:

Battery <101%, 160Mhz Min/595(576)Mhz Max, onDemand, priority 100

Screen Off, 160Mhz Min/352Mhz Max, onDemand, priority 100

That's it! As always, the most updated version of the guide is in my sig.
[G1 Android Development] my_former_self:
Update on that: FC's out the butt. I've tried manually installing, using Root Explorer, ADB, removing the original, clearing the cache, clearing the data, flashing the most updated gapps (which somehow killed off my Gmail app, go figure), etc. Best I can get is in and seeing it, but after about 5 seconds, I just get an FC and I'm out. Oh, well.
[G1 Android Development] ZilverZurfarn:
Installed the new Market using simple ADB push replacing old Vending.apk with the new, and while it works, it FC's after a finished install (the installation as such works), and then some time after, FCs keeps popping up. Works, but limps along, it seems.

<edit>...and now it refuses to start up at all.</edit>
[G1 Android Development] delyorik:
Just tossed the 2.2.7 onto my original myTouch. Looks great! I'm curious to see how it handles Google updates as well as normal app updates.

Cheers.
[G1 Android Development] hal_9000:
I installed the file "Vending-2.2.7-testkeys-signed.zip" from recovery mode and it's working fine for me.

I don't know if this is actually the new version that Google was talking about, since is supposed that the new Market has filter options for age (all, pre-teen, teen and adult) but I cannot find any way to configure that preference on mine. :confused:
[G1 Android Development] cybernetus:
I will reinstall the ROM on friday.

The only thing I don't do is run the fix_permissions.

Thanks for your answer.
[G1 Android Development] almostthere:
You should try the flash from recovery method instead. The file is somewhere in the android app forum. Works fine for me with no FC or crashes so far (Told you 2.2.6 sucked)

EDIT: Found it http://xdaforums.com/showpost.php?p=9898638&postcount=19

BTW, just to be safe, clear the cache and data of Market's app before you do this
[G1 Android Development] ZilverZurfarn:
Flashing Vending-2.2.7-testkeys-signed.zip from recovery does nothing beside replacing old Vending.apk with the new one, so extracting Vending.apk from the zip and pushing it over should produce the same result. Possibly a reboot (which I didn't do) after pushing it over would have made some difference, but now I'm back with "old" Vending.apk that I backed up before updating. Yes, the new Market looked cooler, but I'm all for function over looks. New Market is twice as big as old, and if all I get is nice graphics, I'm gonna stick with the old one.
[G1 Android Development] hal_9000:
Not only nicer graphics. As I said before the new Market is supposed to offer age filtering and some other hardware filtering, like DPI filtering. That's why I'm in doubt about if that 2.2.7 is actually the new Market that Google announced they will be rolling out these days, as I cannot find the setting for the users configure their age preference.

EDIT: This is what they say on a email sent to developers:
[G1 Android Development] the00guy:
I aplogize for sounding like a douche the other day, I was highly aggravated after getting lost because the google maps on my 6.1 install would continously FC. I didn't mean to offend CM, Team Douche, or the community here.
[G1 Android Development] loukvlav:
Hello, I think there is a mistake in your guide regarding setCPU. You set all profiles with a priority 100%. This way the "Screen off" profile never gets activated because "Baterry < 101%" is always active. Check it yourself.

run /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq while the screen is active and you will get "576" then turn screen off and you will also get the same, instead of the max limit under "Screen Off" profile!

I think you should give the "Screen Off" profile a priority of 100% and the rest a lower priority. This way the max limit is decreased to the specified one.
[G1 Android Development] almostthere:
Maybe this doesn't sound much of a big deal but the new market functionality wise has improved. One major cause to embrace it is downloads are paused instead of hung if lets say an incoming interrupts HSDPA links. The other is increase in download cap to 50mb.

Something to consider instead of summarizing based on the ey candy alone
[G1 Android Development] my_former_self:
Good luck. Maybe something just went "wonky," you know. It happens.

Thanks, I'll try that one. I tried a flash from a gapps package that contained the 2.2.7 (due to your comments about 2.2.6), but it still didn't work. I'm going to try your link there. Crossing my fingers!

P.S. - And the cache and data clear is dually noted. I was doing those before "just to be safe" as well :D

Apology accepted, as far as I'm concerned. The current update to Maps works far better than the previous one, btw. Maybe you nabbed a gapps with a cr*ppy Maps version (there are soooooo many gapps to choose from, it gets a little out of control). Anyways, thanks for being cool and I totally understand the aggravation now. +1 for your post.

You are absolutely right. It was actually a typo mistake as, looking back at it, I think I just copy and pasted the first line to the second and changed the profile name, then frequency and forgot to drop 100 down to 99. You and I think alike; I had originally run a cat /sys/.../scaling_max_freq some time ago to determine the profiles and if they were working.

You sneaky little bugger, you! :D Thanks for catching that. Guide's been updated with the fixed priorities. +1 for your post.
[G1 Android Development] my_former_self:
Guide Update (Minor)

Guide update. Minor typo fix.

Changelog:

Small revisions to the SetCPU settings.

Profiles are now recommended to be enabled to prevent Android from killing SetCPU's process.

Profiles should be:

Battery <101%, 160Mhz Min/595(576)Mhz Max, onDemand, priority 99

Screen Off, 160Mhz Min/352Mhz Max, onDemand, priority 100

Special thanks to loukvlav for catching that.

Updated version of the guide is always in my sig.
[G1 Android Development] almostthere:
Lemme know how it went as maybe I can from there recall if I missed out any steps
[G1 Android Development] my_former_self:
Got it flashed and even got into the Market to do an update on an app, but it froze up on me multiple times. Although, I suspect it may have to do with the kernel I was running at the time; Pershoot's 2.6.35.10. I got freeze ups other times, as well, unrelated to the Market. We're talking total freeze ups; pull the battery kind.

I had previously been running EZTerry's (which is based on Pershoot's 2.6.34.7, I think). Not sure why I switched to Pershoot's newest. Bored, perhaps. Not sure if that was the actual cause, but I'm back on EZTerry's and haven't gotten a freeze up yet. Key word, though, is "yet." :D For all I know, it could have been some app update or something else. But my bet is on that particular kernel version. Not Pershoot's, in general, but just the .10 version.

Anyways, I'm going to give it another run now that I'm back on EZTerry's. Probably do it tomorrow when I get home from work. Got a little time then. The Market sure did look purdy when I briefly had it up and running, though :D
[G1 Android Development] almostthere:
Good to hear at least you somehow got it working and pinpointed the exact cause though. +1 for your info
[G1 Android Development] dnd02220:
any mirror sites? can't see the download link.....
[G1 Android Development] Firerat:
rom manager, or CM Forums
[G1 Android Development] cybernetus:
Hey, thanks,

I flash the ROM again today, and I don't have problems.

The fix_permissions solve the reboot problem :-)

:) Happy New Year for all :)
[G1 Android Development] highlandsun:
wifi tether is not working for me any more. Using Pershoot 2708 kernel with latest radio (and 0013d SPL). Am I missing an update for the tether app or something?
[G1 Android Development] tnpapadakos:
same here, but this is the newest one

here is their project page

works on mine, doesnt force close
[G1 Android Development] francians:
hi, just a question.. is fm radio working? I have a tattoo and I'm trying to find a solution for this issue. I know g1 has the same brf6350 chipset, but orginal firmware isn't useful. plz send me a pm :)
[G1 Android Development] androbit:
Emergency call

I have HTC Dream with CyanogenMod-6.1.0-DS Rom. All right, but if I call my carrier support call center TIM 119, i get an answer from local police station :confused: . I think my phone does an emergency call when i call 119 (my Telecom carrier support number). I solve that trouble putting a +1 after 119 :o .

I read somewhere I'd modify /system/etc/ecclist_for_mcc.conf file, but i don't know what I have to modify in that file to solve that problem. Perhaps have I to delete 911 numbers and add a line like: 222 112, where 222 is Italy MCC and 112 emergency call number?
[G1 Android Development] cybernetus:
I have this doubt too ... is anyone solve this question ?
[G1 Android Development] delyorik:
So for a while, I was having problems moving from 6.1 RC1 to 6.1 Stable, no matter what kinds of wipes I tried. Flashing 6.0 Stable, then flashing 6.1 Stable over again solved that one.

Yay me, or something like that.

I'll have to play with radio/spl some other time, but for now, I'm content.
[G1 Android Development] my_former_self:
I'd say "yes" to the SPL+Radio upgrade. I was a little unsure about it at first, too. Like you said, "...a little skittish about messing with a 'good thing.'"

But I went ahead and did and I'm happy I did. Reception is a little better, IMO, and I get HSDPA quite a bit now. Plus, the extra RAM doesn't hurt, either (provided you flash a kernel that can utilize it). ESPECIALLY on my wife's G1 (I have a MT3G).

Sounds scary at first, but if you do it in the right order and just pay attention, it's a pretty quick process. As always, Nandroid backup first!
[G1 Android Development] delyorik:
Oh, I've had your CM6 setup guide and zip file sitting on my desktop for a bit now, reading, re-reading, even had tried doing that with my 6.1RC->6.1S flashing, but now that I've actually got stable working, I may do the backup/reflashitall thing when I get another day off. Meanwhile, I'm loving just 6.1S with my current setup, so I'm really curious to see what my MT3G does with a radio/spl update.

If I do, it'll definitely be while using your guide, which I appreciate your having compiled.

And CyanogenTeam (if you're skimming), cheers for all your hard work as well.
[G1 Android Development] Jul10++:
Hey folks...

Which radio is better to run the CM 6.1 stable in the G1: 2.22.19.26I or 2.22.23.02 ?
[G1 Android Development] my_former_self:
Nah, you don't need to reflash everything. Just Nandroid backup, do the SPL+Radio bit, restore your backup and flash the kernel over it. The rest is all just speed tweaks, especially since you're rolling a MT3G (hence, you don't need apps2SD like Magpie and the Hotfix, etc).

I'm actually time travelling right now; flashing CM 4.2.15.1, trying some different kernels, and using adb to replace a few things like the Launcher and such. Not sure if I'm staying with it, but it's fun :D
[G1 Android Development] Firerat:
wrong question ( well options to question )

2.22.27.08 or 2.22.28.25

28.25 is working out fine for me
[G1 Android Development] Jul10++:
Thanks, actually I've CM 6.1 running with ota-radio-2_22_19_26I & Danger SPL in my G1. Can I just install the 2.22.28.25 radio via the recovery mode? or do I need to install a new spl?
[G1 Android Development] Firerat:
http://xdaforums.com/showthread.php?t=831139

Edit

I should point out that you will need a 'special' kernel for these radios.

but support is growing fast, as basically you gain an extra 15mb of RAM , which is significant for a G1

the Kernel Patches have been put in CM6's Kernel, but its not compiled as the 'norm'

your options are to flash the Kernels provided by EzTerry

or compile your own, either from CyanogenMod's github, or another src after patching with EzTerry's patches
[G1 Android Development] gringo69:
does anyone else think a "back" "pause" and "forward" button would be useful for music player icon thing in the drop down notification bar...i hate having to leave an app to change a song or putting the phone to sleep and using the unlock screen buttons to do it. Im on a g1 and it kills some of my apps like opera...plus i thought it would just be a faster way to do it.

I dont have the know how to do it...so im hoping others might want this enough for it to get added in CM or something.
[G1 Android Development] Rrod15:
I had a question I still use my g1 even though I have a g2 but every time I use it the battery will be fully charged but it just randomly turns off on me over and over again does anybody know how to fix that or what the problem might be?
[G1 Android Development] delyorik:
Alright, so I gave it a shot and followed your guide. Kept rebooting back into recovery. That's when I figured I'd skip the magpie and hotfix. That's when it finally booted up straight. I'm not sure what happened with the other stuff, though... I was curious as to how that was going to work with my phone.

Sigh. ;)

Updates later (since I just finished rebooting) on how the phone performs.

Cheers and happy new year.
[G1 Android Development] pl_laszlo:
did anyone had problem like this when tried to compile cm froyo branch?

Checking API: checkapi-last
Checking API: checkapi-current
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Install: out/target/product/dream_sapphire/system/app/AccountAndSyncSettings.apk
Install: out/target/product/dream_sapphire/system/app/AndroidTerm.apk
Install: out/target/product/dream_sapphire/system/app/ApplicationsProvider.apk
target Java: Bluetooth (out/target/common/obj/APPS/Bluetooth_intermediates/classes)
(unknown): error 17: Field org.apache.http.protocol.HTTP.EXPECT_CONTINUE has changed value from "100-Continue" to "100-continue"

******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************

make: *** [out/target/common/obj/PACKAGING/checkapi-last-timestamp] Error 38
make: *** Oczekiwanie na niezakoĹ„czone zadania....
(unknown): error 17: Field org.apache.http.protocol.HTTP.EXPECT_CONTINUE has changed value from "100-Continue" to "100-continue"

******************************
You have tried to change the API from what has been previously approved.

To make these errors go away, you have two choices:
1) You can add "@hide" javadoc comments to the methods, etc. listed in the
errors above.

2) You can update current.xml by executing the following command:
make update-api

To submit the revised current.xml to the main Android repository,
you will need approval.
******************************

make: *** [out/target/common/obj/PACKAGING/checkapi-current-timestamp] Error 38
Note: packages/apps/Bluetooth/src/com/android/bluetooth/opp/BluetoothOppPreference.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

make update-api didn't help :(
[G1 Android Development] bhrich902:
after reading and searching here and at the cyanogen forums, i haven't found what i'm doing wrong here. i have an original tmobile mt3g which i ran the tmobile update, so is now on 2.2.1, tried flashing the rom with clockwork and amon recoveries and both seem to loop at the green mytouch logo. i followed the instructions from here and cyanogen and im sure i did and met the requirements. What would i be missing here?. thanks in advance...

i am rooted (as per unlockr's instructions superoneclick), and had both recoveries.
[G1 Android Development] my_former_self:
If you ran the TMO update, you most likely have a S-ON (Perfected) SPL now. Which means no fastboot flash recovery for you. Hope you had a Nandroid backup. Cuz it's time for SAPPHIRE.NBH, flash recovery...
[G1 Android Development] ezterry:
Why?

The reason it won't boot is the OTA has the new 2708+ radio

Go to my 2708+ radio/kernel thread and look up a 2708 anykernel then:

* Run superwipe (there are other ways but if you don't know them this is easiest)

* flash cm6.1

* flash 2708 anykernel of your choice

* reboot
[G1 Android Development] my_former_self:
I was under the impression that he wiped out his recovery image. I hope I'm wrong. If I am wrong, bhrich, Terry's thread is here. I'd suggest using Terry's kernel, too (I found it to be very stable and reliable).
[G1 Android Development] almostthere:
@my_formere_self: guess what? Botched some battery mod so had to do a complete reinstall and tried this time to go without swap. My g1 behaves much better with no soft resets or the need to reboot. Only 2 days so far so we'll see how it goes
[G1 Android Development] microstart:
Thx a lot!!!!!!!!!!!!!
[G1 Android Development] bhrich902:
Originally Posted by bhrich902 View Post

after reading and searching here and at the cyanogen forums, i haven't found what i'm doing wrong here. i have an original tmobile mt3g which i ran the tmobile update, so is now on 2.2.1, tried flashing the rom with clockwork and amon recoveries and both seem to loop at the green mytouch logo. i followed the instructions from here and cyanogen and im sure i did and met the requirements. What would i be missing here?. thanks in advance...

i am rooted (as per unlockr's instructions superoneclick), and had both recoveries.

Originally Posted by my_former_self View Post

If you ran the TMO update, you most likely have a S-ON (Perfected) SPL now. Which means no fastboot flash recovery for you. Hope you had a Nandroid backup. Cuz it's time for SAPPHIRE.NBH, flash recovery...

Originally Posted by ezterry View Post

Why?

The reason it won't boot is the OTA has the new 2708+ radio

Go to my 2708+ radio/kernel thread and look up a 2708 anykernel then:

* Run superwipe (there are other ways but if you don't know them this is easiest)

* flash cm6.1

* flash 2708 anykernel of your choice

* reboot

I was under the impression that he wiped out his recovery image. I hope I'm wrong. If I am wrong, bhrich, Terry's thread is here. I'd suggest using Terry's kernel, too (I found it to be very stable and reliable).

ezterry, thanks for the info, I will be doing those steps and reporting back.

my_former_self, i didn't wipe the recovery, but it hasn't been the most stable either. I have flashed clockwork and amon through rom manager, but sometimes is there and then sometimes is gone and i have to reflash it, luckily it's been there whenever the phone goes into boot loops and i can restore. I didn't back up the original 1.6 that the phone came with, but i did backup the ota 2.2.1 that i am sitting on right now, so at least i have something to go back to.

This is where I am at the moment:

android 2.2.1

baseband 62.50sj.2017u_2.22.28.25

kernel 2.6.32.9-27237-gbe746fb

frg83d

sapphire pvt 32B ship s-on g

hboot-1.33.0013 (sapp30000)

cpld-10

radio-2.22.28.25

oct 21 2009,22:33:27

again, thanks and i'll report back...
[G1 Android Development] tman3:
Sorry I search this whole thread where can I download this?
[G1 Android Development] Firerat:
its in the OP

edit

and I answered that same question 27 posts ago

http://xdaforums.com/showthread.php?p=10202002#post10202002
[G1 Android Development] MattDrumz:
Just flashed this ROM again, using my_former_self's setup guide. Everything seems to be running pretty well.

If I end up using this ROM again, I will most likely port the themes on my post in the SuperE thread to CM6 (and a few more).
[G1 Android Development] bhrich902:
Back, i followed the instructions here (clean everything, flash mod, gapps, kernel, reboot, go back to fix uid) and everything seems to be working great for now. One quick thing though, if i were to try another rom at some point, would i be needing that +2708 kernel unless it already comes with the rom?.

Thanks for the help you two and cyanogen for the rom 8)...
[G1 Android Development] cybernetus:
I use the my_former_self setup guide too.

This ROM with the xda_terry's kernel is very fast and stable.