Do Aug 26 2010 19:38:31 EDT von Ford II @ UncensoredI have a hard time understanding how llvm could be gcc unless gcc got worse over the years, or they're not taking advantage of all the processor tweaks.
its transpiling C into an intermediate code (well, somehow gcc does that too...) but thats done in a way so it has more information about what a program / object are about to do.
So it can smarter decide when to do loop unroling, inlining and other stuff when creating the actual object.
It also can create much more precise errormessages which show this "awareness" of whats it currently doing than gcc can.
If I was rich enough to afford a phone that did wifi I wouldn't have
to cheap out on my land line service.
wifi has come to even the somewhat low-end phones now. The problem is that you generally can't keep it on all the time because it kills your battery.
oh, the other one I'm seriously considering (same price range, also has wifi, also touch screen) is the nokia 5530 Xpress Music (but it doesn't have GPS, which means that if I ever get a car, I'll have to buy a separate GPS, b/c I'm severely directionally challenged. OTOH, getting a GPS in Israel is a whole weird issue - just b/c your cell phone has one doesn't mean you can safely use it because you might accidentally drive into an unsafe place... so it might not be a relevant consideration, although it's not a relevant problem if, for example, I'm looking for an address in Tel Aviv, Haifa, or Modiin)
wifi has come to even the somewhat low-end phones now. The problem is
that you generally can't keep it on all the time because it kills your
battery.
It does however (as I understand it) use less battery than 3G.
It does however (as I understand it) use less battery than 3G.
TADA! My point exactly, although I think this is a point for a conversation in another room,.
Lunch at my desk today while I attempt to root my G1 and then upgrade it to
Cyanogen. Let's hope I don't brick it.
Ok, I bricked it :(
Hopefully not permanently. I successfully downgraded the phone to 1.0RC29, rooted it, replaced the bootloader with a hackinstallable one, etc.
Then I installed Cyanogen, and it doesn't work. And I accidentally deleted the backup of the original ROM that I was careful to take at the beginning.
Hopefully not permanently. I successfully downgraded the phone to 1.0RC29, rooted it, replaced the bootloader with a hackinstallable one, etc.
Then I installed Cyanogen, and it doesn't work. And I accidentally deleted the backup of the original ROM that I was careful to take at the beginning.
HOLY SHIT IS THIS ROM AWESOME. It's like I've got a brand new phone. It's
so much cooler than the stock firmware. And I even managed to get the proprietary
Google apps restored onto it, so I've got my YouTube and Market and Contacts/Calendar
sync running as well.
The best part of all is the tethering. No more futzing around with adb hacks and weirdo proxies. You just click the icon that says "tether" and an Ethernet-like device appears on your USB port. Ubuntu displayed a message on the screen that says "auto usb0 active" and suddenly my laptop is on the air.
The best part of all is the tethering. No more futzing around with adb hacks and weirdo proxies. You just click the icon that says "tether" and an Ethernet-like device appears on your USB port. Ubuntu displayed a message on the screen that says "auto usb0 active" and suddenly my laptop is on the air.
Wow, it's even better now that I'm within range of a decent 3G tower. A speed
test is showing that I'm getting 1.19 Mbps downstream and 330 Kbps upstream.
Not bad for a tether. Certainly better than the clumsy tethering proxy I had to use before, which had a bad habit of constantly disconnecting and required proxy settings on the computer. This is comparable with low-end DSL.
Not bad for a tether. Certainly better than the clumsy tethering proxy I had to use before, which had a bad habit of constantly disconnecting and required proxy settings on the computer. This is comparable with low-end DSL.
Ok, let me see if I can remember the steps that were required, in case anyone
wants to do this (or if I want to repeat it for my wife's phone)
1. Downgrade to T-Mobile's 1.0 RC29 ROM
2. Root the phone
3. Install a custom bootloader
4. Upgrade the radio
5. Install a custom SPL
6. Install Cyanogenmod
The radio needs to be upgraded because step 1 downgraded it. The custom SPL is required in order for the custom ROM to work, otherwise it hangs on the splash screen.
Oh, and did I mention that the G1's previously disabled multitouch becomes enabled under this build?
1. Downgrade to T-Mobile's 1.0 RC29 ROM
2. Root the phone
3. Install a custom bootloader
4. Upgrade the radio
5. Install a custom SPL
6. Install Cyanogenmod
The radio needs to be upgraded because step 1 downgraded it. The custom SPL is required in order for the custom ROM to work, otherwise it hangs on the splash screen.
Oh, and did I mention that the G1's previously disabled multitouch becomes enabled under this build?
Nice, will have to look into doing that. Are all the details on the cyanogen
site? Links Where do you get the t-mobile rom?
And oh yea, last but not least, did you do all that repartitioning, putting
swap on the SD card and other stuff? I had been told that this stuff won't
work well if you don't.
Cyanogen only says that you need to root your G1 before you can install the
ROM. But if you Google search on how to root a G1, there are guides all over
the place, and they all point to places where you can download the RC29 ROM.
The important step is to get the custom bootloader ("rescue mode image") onto your phone. Not only is it necessary in order to load various ROM's, but it also makes life MUCH easier. You can backup your existing ROM to SD from there, you can install various packages, and some of them even allow you to put the phone into SD-to-USB mode so you can transfer files between the SD card and your computer without having to either boot into a working ROM or take the SD card out and put it in an external reader.
Once you've got a decent rescue mode installed, it's practically impossible to permanently brick your phone. I really trashed mine, and discovered later that I've got a bad USB port on my desktop computer at work (which also explains why the USB sticks that I filled with music at work wouldn't play in my car).
But I was later able to just mount the phone at home and put a good image on.
Definitely go for it, though. I can't say enough good things about this ROM. It's like having this year's model phone.
The important step is to get the custom bootloader ("rescue mode image") onto your phone. Not only is it necessary in order to load various ROM's, but it also makes life MUCH easier. You can backup your existing ROM to SD from there, you can install various packages, and some of them even allow you to put the phone into SD-to-USB mode so you can transfer files between the SD card and your computer without having to either boot into a working ROM or take the SD card out and put it in an external reader.
Once you've got a decent rescue mode installed, it's practically impossible to permanently brick your phone. I really trashed mine, and discovered later that I've got a bad USB port on my desktop computer at work (which also explains why the USB sticks that I filled with music at work wouldn't play in my car).
But I was later able to just mount the phone at home and put a good image on.
Definitely go for it, though. I can't say enough good things about this ROM. It's like having this year's model phone.
Ok, a couple more thoughts on the "recovery image" in case Pulse or anyone
else wants to try this.
The recovery image actually isn't part of the boot loader. It is basically a second operating system loaded on the phone whose only purpose is to manipulate the phone's main operating system image.
Once the phone is rooted you can install any recovery image you want.
The stock recovery image only knows how to do a few basic things, such as "wipe" (erase all user data) and "apply update.zip from SD card" (which the main Android OS can signal to happen at the next boot; that's how the stock upgrades are applied).
There are a couple of excellent community-built recovery images out there.
The one I started with was called "Amon RA-recovery" which adds features such as turning the SD card into a USB target -- this is excellent for being able to transfer Android images over from your computer without actually having to boot into one -- that's great if your last load didn't work and the phone isn't bootable at the moment.
Later I found an even better one. It's called ClockworkMod Recovery [http://www.clockworkmod.com].
It has the USB target, and it has the ability to apply *any* image from SD (so you don't have to rename the one you want to update.zip), and it can manage various things on the SD card. This is the one you want if you want to partition the SD card. Partitioning sets aside part of the SD to be used as an extension of the phone's own flash memory, essentially obliterating what was considered to be the G1's main limitation. You can also build a swap partition, which Android can use the same way any Linux kernel does.
Also, if you have ClockworkMod Recovery, you can use ClockworkMod ROM Manager (included in CyanogenMod) to perform related tasks while Android is running. Much easier to apply updates once they arrive.
Considering that you can always flash a new Android image from the recovery mode, and you can also flash a new recovery mode image (power up by holding home+power to boot in recovery mode; power up by holding camera+power to boot into the ROM monitor, from where you can load a new recovery image) it's actually pretty hard -- maybe even impossible -- to permanently brick your G1 to the point where it can't ever be made to work again. I guess some unskilled people would consider a phone to be bricked if it just doesn't boot and they don't know how to fix it. My phone was failing to boot at one point, but I still got it running again.
It turned out that I wasted *hours* on this project because the USB port on my desktop computer at work was writing corrupted data to the phone! This also explains why I was unable to transfer music to USB drives to play in the car, and why a bunch of other things I've done since getting that computer have failed.
The recovery image actually isn't part of the boot loader. It is basically a second operating system loaded on the phone whose only purpose is to manipulate the phone's main operating system image.
Once the phone is rooted you can install any recovery image you want.
The stock recovery image only knows how to do a few basic things, such as "wipe" (erase all user data) and "apply update.zip from SD card" (which the main Android OS can signal to happen at the next boot; that's how the stock upgrades are applied).
There are a couple of excellent community-built recovery images out there.
The one I started with was called "Amon RA-recovery" which adds features such as turning the SD card into a USB target -- this is excellent for being able to transfer Android images over from your computer without actually having to boot into one -- that's great if your last load didn't work and the phone isn't bootable at the moment.
Later I found an even better one. It's called ClockworkMod Recovery [http://www.clockworkmod.com].
It has the USB target, and it has the ability to apply *any* image from SD (so you don't have to rename the one you want to update.zip), and it can manage various things on the SD card. This is the one you want if you want to partition the SD card. Partitioning sets aside part of the SD to be used as an extension of the phone's own flash memory, essentially obliterating what was considered to be the G1's main limitation. You can also build a swap partition, which Android can use the same way any Linux kernel does.
Also, if you have ClockworkMod Recovery, you can use ClockworkMod ROM Manager (included in CyanogenMod) to perform related tasks while Android is running. Much easier to apply updates once they arrive.
Considering that you can always flash a new Android image from the recovery mode, and you can also flash a new recovery mode image (power up by holding home+power to boot in recovery mode; power up by holding camera+power to boot into the ROM monitor, from where you can load a new recovery image) it's actually pretty hard -- maybe even impossible -- to permanently brick your G1 to the point where it can't ever be made to work again. I guess some unskilled people would consider a phone to be bricked if it just doesn't boot and they don't know how to fix it. My phone was failing to boot at one point, but I still got it running again.
It turned out that I wasted *hours* on this project because the USB port on my desktop computer at work was writing corrupted data to the phone! This also explains why I was unable to transfer music to USB drives to play in the car, and why a bunch of other things I've done since getting that computer have failed.
This whole thread makes me want to buy another phone. My Blackberry 8120 is getting a little worn. The main thing for which I selected it--built-in 802.11--is now a common feature. The field is a little wider now.