Hi, I've had my G1 Android for 5 days now and still had no updates.
I'm reading all over the internet about security flaws in the
operating system and I'm worried about this!!
When are we going to get updates in the UK?
I'm Running on TC5-RC7 at the moment. Is this the latest version in
the UK?
Is it safe to do my internet banking on my G1 with all this talk of
Trojans & Key Logging?
We released an update to US devices yesterday, and expect the UK
update to follow shortly. The vulnerabilities of the G1 OS revolve
around visiting an infected site. As with all internet activity, you
should be careful to visit known good sites (for instance, your
internet banking website should be fine) and always make sure you're
on a real website before entering any sensitive info.
> Hi, I've had my G1 Android for 5 days now and still had no updates.
> I'm reading all over the internet about security flaws in the
> operating system and I'm worried about this!!
> When are we going to get updates in the UK?
> I'm Running on TC5-RC7 at the moment. Is this the latest version in
> the UK?
> Is it safe to do my internet banking on my G1 with all this talk of
> Trojans & Key Logging?
Out of curiosity, what are the differences between the US and UK
builds?
Thanks,
Tony.
On Nov 4, 9:24 pm, Robin from the Mobile Team wrote:
> Hi DB,
> We released an update to US devices yesterday, and expect the UK
> update to follow shortly. The vulnerabilities of the G1 OS revolve
> around visiting an infected site. As with all internet activity, you
> should be careful to visit known good sites (for instance, your
> internet banking website should be fine) and always make sure you're
> on a real website before entering any sensitive info.
Could you give us a date when the OTA update in the UK should be sent
by, I have been pestering T-Mobile now for three days enquirying about
the build version and the discrepancies between the US and UK build
numbers, and they seem as in the dark as the rest of us.
If possible could you also post a breakdown of the items fixed in each
build so that we don't have to go by the here say posted on various
forums.
On a slightly different subject could you give us an idea as to when
the following items are going to be fixed.
1. IM access to Windows Live Messenger, AIM, IRC etal, as these were
advertised as features of the Android phone.
2. Issues using email client to connect to the various major email
services (an issue posted on various forums), such as Windows Live,
Yahoo, Comcast and T-Mobile.
> Out of curiosity, what are the differences between the US and UK
> builds?
As Rileyp1 says, the UK IM client seems limited to Google Talk. It
offers you a choice of one when you start it (bad UI design!), i.e.
just your Google Talk account. Also, voice dial is missing. I was
looking forward to using that, and hope it appears in an update. Some
files related to voice dial seem to be present (in an "en-us"
directory), but no app. Street View *is* present, but the data isn't
published for the UK yet. You can still try out Compass Mode by
browsing to a US city, or the Tour de France route, or several other
places. That's all I've found so far.
> As Rileyp1 says, the UK IM client seems limited to Google Talk. It
> offers you a choice of one when you start it (bad UI design!), i.e.
> just your Google Talk account. Also, voice dial is missing. I was
> looking forward to using that, and hope it appears in an update. Some
> files related to voice dial seem to be present (in an "en-us"
> directory), but no app. Street View *is* present, but the data isn't
> published for the UK yet. You can still try out Compass Mode by
> browsing to a US city, or the Tour de France route, or several other
> places. That's all I've found so far.
Thanks cmb. As far as I'm aware the us IM apps all work via SMS, which
would explain their absence (despite being in t-mobile's marketing).
The lack of voice dial is a pain, and something I'd assume will be put
back in the image sooner rather than later. My chief concern is that
the UK spec handset I have in front of me is displaying a number of
bugs that were present in the original US build (mainly, really bad
battery life(in the region of 5-6 hours life with light usage, in an
area with strong 3g coverage) and that the 'chin' of the device seems
to heat up when ever the handset is under any kind of load).
Given T-mobile's history of b*ggering around with their phones
software (and stripping some useful stuff/cramming in awful stuff like
their "web 'n' walk" app) I'd rather be building my own updates, but
for now an OTA update that'll at least bring the UK version somewhere
near to the US version would be nice.
I have contacted T-Mobile in the UK a number of times since getting my
G1 and their response is that OTA updates are pushed out by Google and
not controlled by T-Mobile.
This does prompt one important question and that is if the update is
'pushed' how does Google know the addresses of the phones that require
the update? Is there a lack of information coming from T-Mobile UK as
to phones sold and live on their network? Or is 'push' a euphemism for
'pull' in the same way that Microsoft Update works.
It would appear that for peripheral Google items such as the gPhone
(sorry Android) they do not provide a direct method of support, like
an email address, relying instead on forums such as this to field any
questions that users may have. This I believe is a very short sighted
approach as complaints will and are being aired in a very public way
and may result in what looks as through it could be the most important
development in mobile communication going the way of Betamax and the
HDDVD.
Other items that the US users have received in recent updates include,
MS Word and PDF viewers, which again would be wonderful items to show
off the phone with, if only we had then in the UK.
Noted on the T-Mobile forum that OTA (over the air) updates ARE sent
over the mobile phone network, as if they were coming from a Google
server via the internet these would be called OTI (over the internet)
updates. This brings me back to the essence of my original question
which is WHO is responsible for sending out OTA updates, Google or T-
Mobile.
I suspect I will be spending more wasted time on the phone to T-Mobile
UK trying to get OTA Updates sent to my phone.
Ok, I have dug around alot and think I now understand how the OTA
update procedure works, below is the process as I understand it;
1. Once the Google Android team have produced an update that has been
tested and is ready for deployment they place it on a web server
called android.clients.google.com/updates. The file itself is a zip
file containing an update script and files.
2. The G1 phones requiring the update are sent a SMS text message
notifying the update process on the phone that an update is available,
and probably includes the name of the update file itself. The user
does not see this SMS text message as the phone intercepts it and
removes it from the received SMS message folder.
3. The phone then downloads the update over the internet and stores it
in a temporary location on the phone.
4. The user will then get a message informing them that an update is
available and giving them the opportunity to install the update at
that time.
5. The phone goes into an update state, during which time the
operating system is updated, before the phone then reboots.
6. Once the reboot is complete the phone will be at the new updated
build version.
I summise that the process of sending the SMS text messages is in the
control of T-Mobile and runs on receipt of a message from the Google
build system, which means that the reason that some users (mainly in
the UK) have not received any updates are one of the following;
1. The Google Android team are ignoring the UK market at present (Very
bad descission as the number of mobile phones per head of population
is the highest in the world).
2. The Google Android team can't get the fixes applied to the US
version of Android to work in the UK version (oops).
3. The Google Android team aren't sending T-Mobile UK a signal
informing them that an update is available (would have thought that
they would have noticed this by now).
4. T-Mobile UK have not got the mechanism setup to send out bulk SMS
text messages to their G1 users (probably had other things on their
minds at the time, whats for lunch for example).
5. T-Mobile UK have chosen not to switch on the Update system for the
UK (Just wait for the headlines in the papers about a flaky operating
system).
What ever is the case, I would suggest that rather than posting a
reply on one of the numerous user forums telling UK users that they
must be cautious about use of the Internet via the phone (i.e. on your
head be it), the same urgency that was shown by their sister company T-
Mobile US should instead happen.
Please, Please, Please do not kill this wonderful phone while it's
still in it's infancy.
I have a G1 and love it but cant help but feel let down by google and
t-mobile as i have a UK model and we are still waiting for our
update(s) I feel we should be told a time frame. Do you think that
its acceptable for us to wait an undisclosed amount of time for this
to take place.
please could you be more forthcoming with info.
thanks
On 4 Nov, 21:24, Robin from the Mobile Team wrote:
> We released an update to US devices yesterday, and expect the UK
> update to follow shortly. The vulnerabilities of the G1 OS revolve
> around visiting an infected site. As with all internet activity, you
> should be careful to visit known good sites (for instance, your
> internet banking website should be fine) and always make sure you're
> on a real website before entering any sensitive info.
> Cheers,
> Robin
> On Nov 4, 9:24 am, dombud wrote:
> > Hi, I've had my G1 Android for 5 days now and still had no updates.
> > I'm reading all over the internet about security flaws in the
> > operating system and I'm worried about this!!
> > When are we going to get updates in the UK?
> > I'm Running on TC5-RC7 at the moment. Is this the latest version in
> > the UK?
> > Is it safe to do my internet banking on my G1 with all this talk of
> > Trojans & Key Logging?
Well, after a slight moment of madness and a bit of a tinkering
session, I've not got the US build running happily on my UK handset
(and it's also just updated it's self to RC30).
I can report that nothing appears to be broken, and that the battery
life is much improved so far. Of course, this means that the google
will sort out the UK builds now :D
> Well, after a slight moment of madness and a bit of a tinkering
> session, I've not got the US build running happily on my UK handset
> (and it's also just updated it's self to RC30).
> I can report that nothing appears to be broken, and that the battery
> life is much improved so far. Of course, this means that the google
> will sort out the UK builds now :D
Hi there,
So you're running RC30, the US build and it's still working? Anything
different at all, such as key mapping?
I've not found anything show stopping - Web 'n' Walk is gone, but i've
gained the voice dialer (which works ok, despite apparently being
geared towards American accents. It's not something I'd ordinarily
use), the Amazon MP3 app (which I haven't used to purchase anything
yet, but you can stream samples) and not present in the apps menu, but
visible under the apps management tool, The US T-Mobile 'My Faves'
app. Calls are fine, as is data, battery life seems to be about 15-20%
better (but i'll report back when it's had some heavy use) and the
handset doesn't get as warm on the 'chin' during use. Key mapping is
all fine.
To give you a brief overview of how I bodged this into place, There's
a guide over on the xda-developers site. Basically, I reflashed the
device's recovery partition with a version that'd accept self signed
updates. I then unpacked the rc29 update, and removed the version
check that stops the tc4 build being applied over the uk's tc5 before
re-signing it and applying it via the sdcard update method. There is a
(re)build of the tc4-rc30 build that applies the newer battery life
fix, (as well as the slightly iffy output of stdin to a su shell
session) but retains telnetd (and includes busybox!), so you can
continue to (ab)use root access on the handset. Sadly, I missed this
in the excitement of actually getting a device update this morning. :(
> > Well, after a slight moment of madness and a bit of a tinkering
> > session, I've not got the US build running happily on my UK handset
> > (and it's also just updated it's self to RC30).
> > I can report that nothing appears to be broken, and that the battery
> > life is much improved so far. Of course, this means that the google
> > will sort out the UK builds now :D
> Hi there,
> So you're running RC30, the US build and it's still working? Anything
> different at all, such as key mapping?
> I've not found anything show stopping - Web 'n' Walk is gone, but i've
> gained the voice dialer (which works ok, despite apparently being
> geared towards American accents. It's not something I'd ordinarily
> use), the Amazon MP3 app (which I haven't used to purchase anything
> yet, but you can stream samples) and not present in the apps menu, but
> visible under the apps management tool, The US T-Mobile 'My Faves'
> app. Calls are fine, as is data, battery life seems to be about 15-20%
> better (but i'll report back when it's had some heavy use) and the
> handset doesn't get as warm on the 'chin' during use. Key mapping is
> all fine.
> To give you a brief overview of how I bodged this into place, There's
> a guide over on the xda-developers site. Basically, I reflashed the
> device's recovery partition with a version that'd accept self signed
> updates. I then unpacked the rc29 update, and removed the version
> check that stops the tc4 build being applied over the uk's tc5 before
> re-signing it and applying it via the sdcard update method. There is a
> (re)build of the tc4-rc30 build that applies the newer battery life
> fix, (as well as the slightly iffy output of stdin to a su shell
> session) but retains telnetd (and includes busybox!), so you can
> continue to (ab)use root access on the handset. Sadly, I missed this
> in the excitement of actually getting a device update this morning. :(
> On Nov 9, 5:30 pm, supersoulfusion wrote:
> > On Nov 9, 2:59 pm, Orlovsky wrote:
> > > Well, after a slight moment of madness and a bit of a tinkering
> > > session, I've not got the US build running happily on my UK handset
> > > (and it's also just updated it's self to RC30).
> > > I can report that nothing appears to be broken, and that the battery
> > > life is much improved so far. Of course, this means that the google
> > > will sort out the UK builds now :D
> > Hi there,
> > So you're running RC30, the US build and it's still working? Anything
> > different at all, such as key mapping?
There's no guide shoehorning the US software onto a UK G1, but
basically:
Follow the guide in the first post here: http://forum.xda-developers.com/showthread.php?t=443041 Then, pull down the rc29 zip file (link in the second post here:
http://forum.xda-developers.com/showthread.php?t=441282)
unzip it, edit "directory_you_unzipped_to/META-INF/com/google/android/
update-script" to remove the 1st line (it starts "assert
getprop("ro.build.fingerprint") ==" and repeats for a couple of
different builds)
Then, zip and re-sign using the test keys that came with the first
link, copy it to the sd card (as update.zip) and update via the
recovery tool.
There's also a patched version of rc30 on the same forum, that will
keep root access for you.
I would like to point out that I did this via Linux (so if you're
running Windows, I encourage you to get an ubuntu VM running), and
while I'm happy to help if you want to give things a go, I am _NOT_
(and I cannot stress this enough!) responsible if you manage to
destroy your handset.
And yes, my device picked up the us rc30 update on it's own. My
handset won't get UK updates, as it's now reporting a different build
(tc4-rc30), and as I missed the patched rc30 update, will only accept
an update signed with Google's key, so I can't hack the update-script
(until someone smarter than me figures out how to get root access
under rc30) If you think you might at some point want to switch back
to the UK updates, you'll want the patched version of rc-30.
And google, if you get upset about this post, feel free to nuke it :)
but you might want to be a bit more forth coming with the UK
updates :D
> hi orlovsky
> is there any chance of you posting up the link to the guide over at
> xda-developers site. i cant seem to find it.
> cheers m8
> this could be just the ticket. will doing this mean you will have to
> use the U.S updates from now on??
> On 10 Nov, 00:01, Orlovsky wrote:
> > I've not found anything show stopping - Web 'n' Walk is gone, but i've
> > gained the voice dialer (which works ok, despite apparently being
> > geared towards American accents. It's not something I'd ordinarily
> > use), the Amazon MP3 app (which I haven't used to purchase anything
> > yet, but you can stream samples) and not present in the apps menu, but
> > visible under the apps management tool, The US T-Mobile 'My Faves'
> > app. Calls are fine, as is data, battery life seems to be about 15-20%
> > better (but i'll report back when it's had some heavy use) and the
> > handset doesn't get as warm on the 'chin' during use. Key mapping is
> > all fine.
> > To give you a brief overview of how I bodged this into place, There's
> > a guide over on the xda-developers site. Basically, I reflashed the
> > device's recovery partition with a version that'd accept self signed
> > updates. I then unpacked the rc29 update, and removed the version
> > check that stops the tc4 build being applied over the uk's tc5 before
> > re-signing it and applying it via the sdcard update method. There is a
> > (re)build of the tc4-rc30 build that applies the newer battery life
> > fix, (as well as the slightly iffy output of stdin to a su shell
> > session) but retains telnetd (and includes busybox!), so you can
> > continue to (ab)use root access on the handset. Sadly, I missed this
> > in the excitement of actually getting a device update this morning. :(
> > On Nov 9, 5:30 pm, supersoulfusion wrote:
> > > On Nov 9, 2:59 pm, Orlovsky wrote:
> > > > Well, after a slight moment of madness and a bit of a tinkering
> > > > session, I've not got the US build running happily on my UK handset
> > > > (and it's also just updated it's self to RC30).
> > > > I can report that nothing appears to be broken, and that the battery
> > > > life is much improved so far. Of course, this means that the google
> > > > will sort out the UK builds now :D
> > > Hi there,
> > > So you're running RC30, the US build and it's still working? Anything
> > > different at all, such as key mapping?
> There's no guide shoehorning the US software onto a UK G1, but
> basically:
> Follow the guide in the first post here:http://forum.xda-developers.com/showthread.php?t=443041 > Then, pull down the rc29 zip file (link in the second post here:http://forum.xda-developers.com/showthread.php?t=441282)
> unzip it, edit "directory_you_unzipped_to/META-INF/com/google/android/
> update-script" to remove the 1st line (it starts "assert
> getprop("ro.build.fingerprint") ==" and repeats for a couple of
> different builds)
> Then, zip and re-sign using the test keys that came with the first
> link, copy it to the sd card (as update.zip) and update via the
> recovery tool.
> There's also a patched version of rc30 on the same forum, that will
> keep root access for you.
> I would like to point out that I did this via Linux (so if you're
> running Windows, I encourage you to get an ubuntu VM running), and
> while I'm happy to help if you want to give things a go, I am _NOT_
> (and I cannot stress this enough!) responsible if you manage to
> destroy your handset.
> And yes, my device picked up the us rc30 update on it's own. My
> handset won't get UK updates, as it's now reporting a different build
> (tc4-rc30), and as I missed the patched rc30 update, will only accept
> an update signed with Google's key, so I can't hack the update-script
> (until someone smarter than me figures out how to get root access
> under rc30) If you think you might at some point want to switch back
> to the UK updates, you'll want the patched version of rc-30.
> And google, if you get upset about this post, feel free to nuke it :)
> but you might want to be a bit more forth coming with the UK
> updates :D
> On Nov 10, 12:01 pm, eLv./.G1 wrote:
> > hi orlovsky
> > is there any chance of you posting up the link to the guide over at
> > xda-developers site. i cant seem to find it.
> > cheers m8
> > this could be just the ticket. will doing this mean you will have to
> > use the U.S updates from now on??
> > On 10 Nov, 00:01, Orlovsky wrote:
> > > I've not found anything show stopping - Web 'n' Walk is gone, but i've
> > > gained the voice dialer (which works ok, despite apparently being
> > > geared towards American accents. It's not something I'd ordinarily
> > > use), the Amazon MP3 app (which I haven't used to purchase anything
> > > yet, but you can stream samples) and not present in the apps menu, but
> > > visible under the apps management tool, The US T-Mobile 'My Faves'
> > > app. Calls are fine, as is data, battery life seems to be about 15-20%
> > > better (but i'll report back when it's had some heavy use) and the
> > > handset doesn't get as warm on the 'chin' during use. Key mapping is
> > > all fine.
> > > To give you a brief overview of how I bodged this into place, There's
> > > a guide over on the xda-developers site. Basically, I reflashed the
> > > device's recovery partition with a version that'd accept self signed
> > > updates. I then unpacked the rc29 update, and removed the version
> > > check that stops the tc4 build being applied over the uk's tc5 before
> > > re-signing it and applying it via the sdcard update method. There is a
> > > (re)build of the tc4-rc30 build that applies the newer battery life
> > > fix, (as well as the slightly iffy output of stdin to a su shell
> > > session) but retains telnetd (and includes busybox!), so you can
> > > continue to (ab)use root access on the handset. Sadly, I missed this
> > > in the excitement of actually getting a device update this morning. :(
> > > On Nov 9, 5:30 pm, supersoulfusion wrote:
> > > > On Nov 9, 2:59 pm, Orlovsky wrote:
> > > > > Well, after a slight moment of madness and a bit of a tinkering
> > > > > session, I've not got the US build running happily on my UK handset
> > > > > (and it's also just updated it's self to RC30).
> > > > > I can report that nothing appears to be broken, and that the battery
> > > > > life is much improved so far. Of course, this means that the google
> > > > > will sort out the UK builds now :D
> > > > Hi there,
> > > > So you're running RC30, the US build and it's still working? Anything
> > > > different at all, such as key mapping?
Orlovsky im sorry but im as green as they come with linux and while i
want to gie this ago im not sure where to start(sorry) i have download
the rc 29 update and the recovery zip file from first link. im just
getting ubuntu VM to run on xp. how do i put recovery image at /system/
recovery.img. if it sounds like to much work helpin i'll understand.
but if this works at least this would be a sweet guide for U.K users
to try.
You'll need root access to your phone, so you might want to check out
the guide on the xda forum regarding that too. Once you have root
access you'll be able to telnet (or connect via ADB as root) and
you'll then be able to run through the other steps.
I would suggest that if you're even remotely unsure about what you're
doing, that you hold off. the learning curve might be a little steep,
and I'd hate for you to brick your phone while you're learning
linux :)
On Nov 10, 3:52 pm, eLv./.G1 wrote:
> Orlovsky im sorry but im as green as they come with linux and while i
> want to gie this ago im not sure where to start(sorry) i have download
> the rc 29 update and the recovery zip file from first link. im just
> getting ubuntu VM to run on xp. how do i put recovery image at /system/
> recovery.img. if it sounds like to much work helpin i'll understand.
> but if this works at least this would be a sweet guide for U.K users
> to try.
> You'll need root access to your phone, so you might want to check out
> the guide on the xda forum regarding that too. Once you have root
> access you'll be able to telnet (or connect via ADB as root) and
> you'll then be able to run through the other steps.
> I would suggest that if you're even remotely unsure about what you're
> doing, that you hold off. the learning curve might be a little steep,
> and I'd hate for you to brick your phone while you're learning
> linux :)
> On Nov 10, 3:52 pm, eLv./.G1 wrote:> Orlovsky im sorry but im as green as they come with linux and while i
> > want to gie this ago im not sure where to start(sorry) i have download
> > the rc 29 update and the recovery zip file from first link. im just
> > getting ubuntu VM to run on xp. how do i put recovery image at /system/
> > recovery.img. if it sounds like to much work helpin i'll understand.
> > but if this works at least this would be a sweet guide for U.K users
> > to try.
> ive got root i just wondered what u used to edit script file
> On 10 Nov, 16:10, Orlovsky wrote:
> > No problems :)
> > You'll need root access to your phone, so you might want to check out
> > the guide on the xda forum regarding that too. Once you have root
> > access you'll be able to telnet (or connect via ADB as root) and
> > you'll then be able to run through the other steps.
> > I would suggest that if you're even remotely unsure about what you're
> > doing, that you hold off. the learning curve might be a little steep,
> > and I'd hate for you to brick your phone while you're learning
> > linux :)
> > On Nov 10, 3:52 pm, eLv./.G1 wrote:> Orlovsky im sorry but im as green as they come with linux and while i
> > > want to gie this ago im not sure where to start(sorry) i have download
> > > the rc 29 update and the recovery zip file from first link. im just
> > > getting ubuntu VM to run on xp. how do i put recovery image at /system/
> > > recovery.img. if it sounds like to much work helpin i'll understand.
> > > but if this works at least this would be a sweet guide for U.K users
> > > to try.
I'm impressed with all the good discussion over the weekend & I'd like
to address some of the questions:
- Yes a patch is still coming out, & will be pushed by Google as soon
as we can. We don't promise specific dates & times because anything
can happen at the last minute, and there's little worse than dashed
hopes.
We're working hard to get the UK patch out; the delay is not an
attempt to show favoritism or to ignore our friends across the pond! I
hear it's coming Very Soon.
- You'll notice that we use Groups for all of our products, not just
"peripherals". We're monitoring them closely & think it's fine to air
things publicly where everyone can weigh in, no matter if the comments
are positive or negative. The London Sales & Engineering Office won't
be able to assist you with these G1 questions; you can continue
posting questions here or sending them to T-Mobile.
Part of the joy of the open platform is that everyone has access to
the code, so Google doesn't become a bottleneck in the process. To be
clear, the only portion of the phone that Google is fully supporting
is the Android Market (which has it's own Help Forum & Help Center).
-Orlovsky - no need to remove your post, though I will mention that
this isn't the recommended way to get updates :)
> Aha! I used vi. You could do it under windows, but windows has a habit
> of changing the line terminators. :)
> On Nov 10, 5:06 pm, eLv./.G1 wrote:
> > ive got root i just wondered what u used to edit script file
> > On 10 Nov, 16:10, Orlovsky wrote:
> > > No problems :)
> > > You'll need root access to your phone, so you might want to check out
> > > the guide on the xda forum regarding that too. Once you have root
> > > access you'll be able to telnet (or connect via ADB as root) and
> > > you'll then be able to run through the other steps.
> > > I would suggest that if you're even remotely unsure about what you're
> > > doing, that you hold off. the learning curve might be a little steep,
> > > and I'd hate for you to brick your phone while you're learning
> > > linux :)
> > > On Nov 10, 3:52 pm, eLv./.G1 wrote:> Orlovsky im sorry but im as green as they come with linux and while i
> > > > want to gie this ago im not sure where to start(sorry) i have download
> > > > the rc 29 update and the recovery zip file from first link. im just
> > > > getting ubuntu VM to run on xp. how do i put recovery image at /system/
> > > > recovery.img. if it sounds like to much work helpin i'll understand.
> > > > but if this works at least this would be a sweet guide for U.K users
> > > > to try.
But of course! It's nice to see that Google are accommodating towards
users hacking T-mobile's handset ;) I know you can't elaborate on a
potential release for the latest UK build, but could you explain the
difference between the US and UK builds? (assuming there's no politics
behind the differences ;) )
Oh, and elv, how did you get on? I hope you took the self signed
route, so we can probably get you back onto the UK build when it
arrives?
Cheers,
Orlovsky.
On Nov 10, 10:03 pm, Robin from the Mobile Team wrote:
> -Orlovsky - no need to remove your post, though I will mention that
> this isn't the recommended way to get updates :)
It's good to know that the update is coming very soon, even though the
us users have got three updates up to now...
To be honest, I do feel a bit let down by Google on this issue, esp
after having to wait under no confirmed release date while our friends
are getting updates after updates...
Even the M$ wont release its updates in this way.
On Nov 10, 10:03 pm, Robin from the Mobile Team wrote:
> I'm impressed with all the good discussion over the weekend & I'd like
> to address some of the questions:
> - Yes a patch is still coming out, & will be pushed by Google as soon
> as we can. We don't promise specific dates & times because anything
> can happen at the last minute, and there's little worse than dashed
> hopes.
> We're working hard to get theUKpatch out; the delay is not an
> attempt to show favoritism or to ignore our friends across the pond! I
> hear it's coming Very Soon.
> - You'll notice that we use Groups for all of our products, not just
> "peripherals". We're monitoring them closely & think it's fine to air
> things publicly where everyone can weigh in, no matter if the comments
> are positive or negative. The London Sales & Engineering Office won't
> be able to assist you with these G1 questions; you can continue
> posting questions here or sending them to T-Mobile.
> Part of the joy of the open platform is that everyone has access to
> the code, so Google doesn't become a bottleneck in the process. To be
> clear, the only portion of the phone that Google is fully supporting
> is the Android Market (which has it's own Help Forum & Help Center).
> -Orlovsky - no need to remove your post, though I will mention that
> this isn't the recommended way to get updates :)
> Cheers,
> Robin
> On Nov 10, 9:09 am, Orlovsky wrote:
> > Aha! I used vi. You could do it under windows, but windows has a habit
> > of changing the line terminators. :)
> > On Nov 10, 5:06 pm, eLv./.G1 wrote:
> > > ive got root i just wondered what u used to edit script file
> > > On 10 Nov, 16:10, Orlovsky wrote:
> > > > No problems :)
> > > > You'll need root access to your phone, so you might want to check out
> > > > the guide on the xda forum regarding that too. Once you have root
> > > > access you'll be able to telnet (or connect via ADB as root) and
> > > > you'll then be able to run through the other steps.
> > > > I would suggest that if you're even remotely unsure about what you're
> > > > doing, that you hold off. the learning curve might be a little steep,
> > > > and I'd hate for you to brick your phone while you're learning
> > > > linux :)
> > > > On Nov 10, 3:52 pm, eLv./.G1 wrote:> Orlovsky im sorry but im as green as they come with linux and while i
> > > > > want to gie this ago im not sure where to start(sorry) i have download
> > > > > the rc 29updateand the recovery zip file from first link. im just
> > > > > getting ubuntu VM to run on xp. how do i put recovery image at /system/
> > > > > recovery.img. if it sounds like to much work helpin i'll understand.
> > > > > but if this works at least this would be a sweet guide forU.Kusers
> > > > > to try.
|
