Database Users

R2BA020 review

No matter how much SE can piss me off, I have to say they did a good job with the last update R2BA020 .
I did fully charge my battery, did not use any task killer or such only kept adw launcher. With a normal use the battery last me a little over 48 hours I was at 10% when i devided to recharge it again.
-Around 2 hours of video
-4 hours of reading with Aldiko
-1 hours of internet
-Around 50 txt msg
-20 call 5-15 min each
-3 Pictures
-4 Hour of music while reading
-Email and weather widget run to update every hour
-Fancy widget running
-Bluetooth on all the time
-Gps and wifi was off all the time
Bottom line it’s impressive, now I really can enjoy my device without carrying a charger and searching for an outlet all the time .

I completely agree, the 020 firmware is fantastic. My usage differs slightly but even using Bluetooth to listen to Spotify all day didn't drain my battery. Neither did using my phone as a wireless 3G modem with Wifi tethering.

Well, yes, nice improvements but the WIFI is still using a lot of juice

wifi is confirmed using alot.

the phonebook is now kind of stupid...
when you click a person's name, their contact shows up, and when you tap their phone #...instead of calling that person directly it would bring you to the dialer screen with the # entered in and you need to press "call" to call the person...
i mean..if im in someones contact page and i tap their #..im pretty sure i want or need to call them....i really dont understand the point of bringing the dialer screen up again..pretty stupid on SE's part in my opinion

Well a quicker step would be to long hold their name and call them
Sent from my X10i using XDA App

Well, I've rooted my device yesterday, started using it massively around 3 or 4 am to reconfigure everything and now its battery is at 8%:
throughout all the process wifi was used for internet (when needed, of course), 3g/gps/bluetooth turned off.
* Installed a lot of apps, some using barcode scanner, some using appbrain.
* Synced with google
* Restored a backup
* Reconfigured a lot of apps
* around 6 sms
* tweeted 2 or 3 times
* 5 to 10 calls 10m~ each
* listened to music through the day (around 2 hours of music, simple last fm scrobbler was used to cache the data, didn't scrobbled yet)
* read a pdf book around 1 hour
* some random usage through the day, like checking online stuff.
* Since I go to work using the subway, the signal reception is quite poor, so the phone prolly was searching for signal during the day.
Even wifi draining a lot of battery, the phone battery was quite good for everything that I've done today.
Apart from the battery the whole system feels better, all the UI customizations done by SE are faster (timescape, mediascape, dialer and so on).
I can say, like all of you, SE did a good job on this update. I can't wait for the Q3 2.1 release. Seriously, I want 720p video recording so much

Greetings guys,
Whats the difference R2BA020 and B2FA020.
Thanks for your kind reply.
Vatis

has anyone noticed any difference in call quality - in call volume especially
this was the thing i looked forward to getting the most out of this upgrade but no much difference i notice, still can't hear very well in any outside environment
i hope this issue becomes resolved...

I usually use headphones while outdoors, so I can't help here. Indoors it's been quite good, at least for me.

dpk0875 said:
has anyone noticed any difference in call quality - in call volume especially
this was the thing i looked forward to getting the most out of this upgrade but no much difference i notice, still can't hear very well in any outside environment
i hope this issue becomes resolved...
Click to expand...
Click to collapse
I was on fw 16 and it was a litter bit low but still fine, didn't notice any difference between 16 and 20 tho.

never heard of B2FA020 - Think it might have been a typo on someone's part?

Screen off while in call.
Not to start a new thread, I'll pin my question to this one. I've updated to R2BA020 (O2 Irl branded) and noticed that whenever in call the screen is not turning off, as it used to before. Did anyone else experienced this problem?
Regards, masterofp.

check your screen time out settings in the settings/ display/ screen timeout section.. it may be that it's reverted to a longer timeout period or to not time out at all.

im_iceman said:
check your screen time out settings in the settings/ display/ screen timeout section.. it may be that it's reverted to a longer timeout period or to not time out at all.
Click to expand...
Click to collapse
Nope, still @ 15 seconds...

Though overall battery usage seems to be better with R2BA020 (Rogers), I've run into an odd issue:
When tethering via PdaNet, my battery drains at an alarming rate. It dropped 20% in the past hour. This wasn't the case before I upgraded (was using stock Rogers firmware before) - it would drain, but much more slowly, going from 100% to maybe 55% over the course of the 8 hours I was at work tethered. It's almost as if it's not charging at all via USB (or is charging much more slowly than before).
I checked, and the phone does register as charging while tethered. So I'm not sure what exactly the issue is. Nothing else has changed.
-edit-
Turned off PdaNet during a meeting I had today just to make sure my X10 is charging properly via USB, and sure enough it is (gained 12% charge over the hour).

after updating into R2BA020, my sim tool kit and play now were gone. Now, I want them back (especially STK). Does anyone know how to do it? My X10 is not rooted yet.

I'm pretty happy with the new Facebook app. It got rid of the "Camera" icon on the mainscreen and replaced it with "Inbox", which makes so much more sense.
My ringtones got reset, and I noticed that Astro File Manager lost a few file associations. I'm prompted for all sorts of default apps etc now, but it's just a minor annoyance.
I did the update through the Sony Ericsson PC Software. The first boot after update took a very long time on the Rogers splash screen. I was afraid the device was bricked for a couple of minutes. I guess it was just the first boot, and the Xperia was restoring all my user data.

Does anyone have comparison between R2BA020 and R2BA023? appreciate if it includes benchmarking between them.

masterofp said:
Not to start a new thread, I'll pin my question to this one. I've updated to R2BA020 (O2 Irl branded) and noticed that whenever in call the screen is not turning off, as it used to before. Did anyone else experienced this problem?
Regards, masterofp.
Click to expand...
Click to collapse
yes, Am also facing the same problem

Does yours AUTO UPDATE of TIME & DATE

Mine seem to do this everytime I reboot. As well as media scanner. What is all this??

I don't know but I am getting
the time auto update thing about every five minutes while I am watching Avatar. Pretty annoying.

Yeah, it does it on boot, but never after that.

Mine has only started the auto-update of time and date thing since applying the GPS 'fix'. It has slowed my boot time from mere seconds to ~1min, accompanied by low FPS (~1-5 max) until the tests are all complete.

Jon C said:
Mine has only started the auto-update of time and date thing since applying the GPS 'fix'. It has slowed my boot time from mere seconds to ~1min, accompanied by low FPS (~1-5 max) until the tests are all complete.
Click to expand...
Click to collapse
mine does what you describe, the whole process do take about a min now from power on to usable state. But the thing is, It was doing this way before the GPS Fix. Im not exactly sure but it might have to do with the amount of programs installed in our phone.

My phone's been doing the choppy thing since I added 10gb of music and all my standard apps. It's because it has to register so much data, not because the GPS is pinging a different server. That's like filling up your car's gas tank, getting a flat and blaming the flat on bad gas.

Wrong thread sorry...moderators please delete my post...thanks

GPS Time

I was messing around with the GPS on both my G1 and my Vibrant and noticed the GPS time was different on the phones. My G1 displayed the correct time, but the Vibrant was off by a few hours. Any thoughts/insight?
Edit:
A few posts down this guy posted a video, and you can see the time is different from his cliq as well.
http://forum.xda-developers.com/showthread.php?t=736325

I see it as well. I believe that the software isn't adjusting the time zone properly. GPS uses GMT, I suspect that the GPS driver is using a hard coded time offset rather than the calculated one from your current location.

ttabbal said:
I see it as well. I believe that the software isn't adjusting the time zone properly. GPS uses GMT, I suspect that the GPS driver is using a hard coded time offset rather than the calculated one from your current location.
Click to expand...
Click to collapse
agreed. this would throw off location calculation if im not mistaken.

flip clock an hour ahead [SOLVED]

my flip clock on the new mdeejay froyo HD build is an hour ahead of the time on the top right.
it flips to an hour ahead, never seen this before.
any ideas?
(pic attached)

I have the same, in WinMo Goatrip ROM as well as when running Mattc's 1.8...I travel a lot and somehow the HD2 is not recognising The Daylight Saving Time in Europe but setting the time I.e. in Dubai to 3 hours ahead though it is only 2 hours.
The little clock top corner displays the correct time according to the applicable time zone...strange...
Sent from my HTC Desire using Tapatalk

if you hit "automatic time" in the time/date settings this seems to fix it

[Q] Clock goes back when Battery removed?

I recently noticed that when I remover the battery for more than a minute, the clock (after starting up) would be late. The more I leave the battery out, the more the battery will be late. I recently tried several Android NAND roms & WP7. I have returned back to WM.
I don't remeber noticing this before, I have Hard-Reset the phone, re-flashed, HSPL, Task29, and still the same.
Is it my HD2 only? a Hardware problem (covered by warranty)? Or is it something normal?
Thanks for any feedback.

The internal battery on the board of your HD2 has run dry. You can send it back to HTC to get it repaired...but really all it does is run the internal clock, so it's not a huge deal if you can stand resetting the clock when restart your phone.

I was suspecting this, as I faced it with my Tornado. But I didn't read about any user with an HD2 who complained about it.
Any idea where I can buy one to try to replace myself?

omar302 said:
I was suspecting this, as I faced it with my Tornado. But I didn't read about any user with an HD2 who complained about it.
Any idea where I can buy one to try to replace myself?
Click to expand...
Click to collapse
It's not possible to replace it, unless you buy a new phone, because it's not really a battery, it's more like a small chip and its fix integrated on the motherboard. There's no way to change it without buying a new motherboard. I would say, this problem is not big enough to pay so much for it. And maybe you could think about it, if it's necessary to remove the battery. Unless you want to replace the SIM Card you don't have to. SD-Card Slot is not under the battery and for rebooting you have a reset button, and if you have to flash your phone, you have to set up everything so it's not a problem to also set up your time ^.^
Best regards

Is it something that should be covered under warranty?
I baught my HD2 from Clove.co.uk from 1 year back & at the time, warranty used to be 2 years from purchase.
Also, if it is a problem of the Inernal Battery, wouldn't the time reset to ROM date & time? My problem is that the time actualy goes back.
For example, it is 9:15pm & I remove the battery for 1 minute, the phone starts & time is 9:11pm. The more the battery is out, the more the time will be back.

Yeah I have this problem too! *feels less alone*
I noticed this problem after the first time I ran an Android build from SD, but that was probably coincidence...
I'm not really into sending it to warranty, my HD2 works great and sometimes they come from warranty worse than they go...

DeadVirus said:
I noticed this problem after the first time I ran an Android build from SD, but that was probably coincidence...
Click to expand...
Click to collapse
Now that you mentioned it, I did notice this problem after one of the Android builds from SD. Don't remeber which.

omar302 said:
Now that you mentioned it, I did notice this problem after one of the Android builds from SD. Don't remeber which.
Click to expand...
Click to collapse
I'm starting to think that it is related... Another guy complains about something similar after using Android SD...

Yes... Normally it should reset it.
But if you say it's only one year old, there's another hardware problem because such a battery has a lifetime from approximately 2 years.
Maybe - or better they must - will change it under the warranty conditions.
And I don't think that it has something to do with AD SD builds. I also used them for a long time and never encountered something like this.

Hello there.
I have the same problem with my HD2, which runs on a cooked ROM.
What I have noticed is that it actually goes back to the date and time of it's last boot (in fact the time and date SET after the last boot, since it changes and I have to reset it every time, by syncing or manually), regardless of the way the reboot was done. It is a little strange I guess...
Just thought to add this little piece of information.
Oh, and my phone is also quite "young", I have it for less than a year (don't remember the exact date of purchase).

Interesting. I was about to post a similar issue.
I had been using (SD) Android for about 3 weeks continuously. Had a crash and rebooted. I have some problems in Android now following this (corrupt Data.img I think) so booted back into WinMO and found the date was now 2nd Feb 2010 and some random time!
Reset the time and restarted and for some reason it refuses to recognise we are in BST (and I can't see how to change it to GMT +BST)
Same date/time showed when I booted into Android (doesn't seem to be getting the correct details from Network?)
Slightly better after a few reboots so that now everytime I reboot with a battery pull it is setting an older time (but correct date).

I have the same issue using WP7. The time changes backk like 6 hours or so to a completely random time.
And the annoying thing is that the phone seems to think its the right time, and theres no way to 'force' and automatic time update on its self, so i have to disable automatic update and enter the correct time manually!

That's the thing that gets me most - you can move between time zones and the phone gets the local time from the Network operator, but will not "check" if it is wrong by so much....

It must be the internal battery thingumijiggy.
Just confirmed that it only happens after a battery pull.

as long as no one has posted a theory yet, i'm gonna give it a shot!
i think the phone might have TWO regions of memory for storing the current date/time:
1. a "volatile" one (good as long as battery is present)
2. and another "non-volatile" one (survives between battery pulls)
my theory is, WM6.5 ROMs have something hidden in them that allows the date/time to be (periodically?) written to the non-volatile region in case the battery is pulled, following which the system might need to recall the last reliable date/time, as opposed to resetting to an arbitrary default date/time.
the volatile region is good as long as the battery isn't removed. the volatile region is initialized by the non-volatile region and is subsequently kept updated by the RTC (real time clock) chip, whether or not an OS is running (like android or WM or WP7).
but perhaps the little piece of logic that updates the non-volatile region is somehow absent in our android builds?

I have the same problem, and i just use clocksync a free app from market. The app sync the time every time you reboot your phone.
Sent from my Nexus One using XDA App

Dmxnet said:
I have the same problem, and i just use clocksync a free app from market. The app sync the time every time you reboot your phone.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I also use clocksync in android. But it doesn't solve the problem... :S