Database Users

People w/ Froyo(HACK) and bugs

Just curiosity: Are people that are reporting "bugs" (though to me it sounds like apps that need to be updated for full compatibility with Froyo) running the OTA updated 2.2, or manually updated 2.2?
Edit: Changed name to Froyo(HACK) as recommended by someone since no one seems to be running a genuine OTA updated Froyo

Manually-updated using the official signed update from Google, for me. I don't have most of the bugs that have been reported here; the only one I'm currently aware of is that two applications I updated via the market this morning are no longer shown in the "Downloads" list, although they are labeled as "installed" when I search for them in the market. Other than that, no problems here.

crackness said:
Just curiosity: Are people that are reporting "bugs" (though to me it sounds like apps that need to be updated for full compatibility with Froyo) running the OTA updated 2.2, or manually updated 2.2?
Click to expand...
Click to collapse
No one on the entirety of XDA has upgraded via the OTA update. Everyone hacked.
(The OTA was press-only for people who attended Google I/O.)

Paul22000 said:
No one on the entirety of XDA has upgraded via the OTA update. Everyone hacked.
(The OTA was press-only for people who attended Google I/O.)
Click to expand...
Click to collapse
Ahhh.... I thought that was only speculation :/
/trying my hardest not to ***** and moan...

Paul22000 said:
No one on the entirety of XDA has upgraded via the OTA update. Everyone hacked.
(The OTA was press-only for people who attended Google I/O.)
Click to expand...
Click to collapse
Exactly.. About time more people acknowledged this.

logger said:
Exactly.. About time more people acknowledged this.
Click to expand...
Click to collapse
I understand what you're saying.
However Google have released an OTA update to the MEDIA!
They'll grab this with both hands and show how the NEW messiah has fallen over again and how we should have all bought iPhones.....
I do believe this Froyo is HIGHLY unpolished and very dissapointing. It should have been released when it was fully ready.
I'm desperately trying to get back to CM but it seems to have screwed my phone and I'm stuck........

wmm said:
Manually-updated using the official signed update from Google, for me. I don't have most of the bugs that have been reported here; the only one I'm currently aware of is that two applications I updated via the market this morning are no longer shown in the "Downloads" list, although they are labeled as "installed" when I search for them in the market. Other than that, no problems here.
Click to expand...
Click to collapse
The market problem has a fix in this thread:
http://forum.xda-developers.com/showthread.php?p=6572697#post6572697
google needs to provide an official fix for the issue so we don't have to use the hack one

punk4bc said:
The market problem has a fix in this thread...google needs to provide an official fix for the issue so we don't have to use the hack one
Click to expand...
Click to collapse
yoo mean a hack for a hack
I think I'll just wait for the official Google OTA.
Good thing that people around here are chasing up all the last minute bugs for Google though. I am sure they would prefer to see them now rather than after releasing it to the general public.

logger said:
yoo mean a hack for a hack
I think I'll just wait for the official Google OTA.
Good thing that people around here are chasing up all the last minute bugs for Google though. I am sure they would prefer to see them now rather than after releasing it to the general public.
Click to expand...
Click to collapse
good point lol
I'm waiting for the official Google too

Yeah I updated with Paul's version and I would have stayed on froyo but having annoying camera bugs.
I dont think Google meant this as an actual release since you Market isn't allowing protected apps etc with the froyo fingerprint. etc.
So i'm back on Cyan and all is well with the world.
I did however keep the newer radio to test it out.

It would be great if someone around here could change EVERY thread title that mentions this version to FROYOHACK so that once the real official one is released, we dont have to wade through all this pre-release BS. I know it is not possible but just thought.

What were your camera bugs?
I did Paul's too and mine worked 100%. Still have the new radio and according to speed tests it is doing better than the old one

punk4bc said:
What were your camera bugs?
I did Paul's too and mine worked 100%. Still have the new radio and according to speed tests it is doing better than the old one
Click to expand...
Click to collapse
I've posted it in the general forum. QIK app didn't work and if you use the stock camera app and slide to the camcorder then BACK to the camera, N1 would crash.
I posted the logcat and it appears there are some incompatibilities somewhere deep. I tried every kind of wipe and 'band-aid' that I could to get it working and failed miserably.
But I figured since i'm on an AT&T N1 that this release wasn't intended for me and there must be some kind of subtle differences.
*shrug* we'll see.

wmm said:
Manually-updated using the official signed update from Google, for me. I don't have most of the bugs that have been reported here; the only one I'm currently aware of is that two applications I updated via the market this morning are no longer shown in the "Downloads" list, although they are labeled as "installed" when I search for them in the market. Other than that, no problems here.
Click to expand...
Click to collapse
One thing I have learn is a app has a widget and it is moved to the sdcard it will show install but not show. I moved these to the phone and they show now.

logger said:
It would be great if someone around here could change EVERY thread title that mentions this version to FROYOHACK so that once the real official one is released, we dont have to wade through all this pre-release BS. I know it is not possible but just thought.
Click to expand...
Click to collapse
Hey thanks MOD (or whoever did it) for renaming the thread. Excellent Job...

I don't know if it's a bug, but I can't find FM radio anywhere... and I believe it was announced.

logger said:
Hey thanks MOD (or whoever did it) for renaming the thread. Excellent Job...
Click to expand...
Click to collapse
Hah, as OP, I changed it. I didn't realize (though I had read it somewhere else) that the only people who got the OTA update were press/developers who went to I/O.
FOR THOSE JUST READING NOW: According to Paul (and where ever else I read online), anyone else with Froyo updated manually, so take current issues with a grain of salt.
Deusdies said:
I don't know if it's a bug, but I can't find FM radio anywhere... and I believe it was announced.
Click to expand...
Click to collapse
The FM radio stuff was never announced OFFICIALLY. I do remember it being something rumored, but I don't ever remember Google saying it was an addition to Froyo. AND, even if it was announced, read my reiteration above about no normal consumers having the Official OTA update to Froyo.

ibegary said:
I've posted it in the general forum. QIK app didn't work and if you use the stock camera app and slide to the camcorder then BACK to the camera, N1 would crash.
I posted the logcat and it appears there are some incompatibilities somewhere deep. I tried every kind of wipe and 'band-aid' that I could to get it working and failed miserably.
But I figured since i'm on an AT&T N1 that this release wasn't intended for me and there must be some kind of subtle differences.
*shrug* we'll see.
Click to expand...
Click to collapse
I running Froyo on the AT&T Nexus on Telus here in Canada and so far I am having no issues, maybe some app that you installed is causing the crash...weird tho.

crackness said:
Hah, as OP, I changed it. I didn't realize (though I had read it somewhere else) that the only people who got the OTA update were press/developers who went to I/O.
FOR THOSE JUST READING NOW: According to Paul (and where ever else I read online), anyone else with Froyo updated manually, so take current issues with a grain of salt.
Click to expand...
Click to collapse
Sort of ironic now, that people will avoid this thread in favour of ones without HACK in the title, as they will not want to accept that they have a hacked version on their device You cant win I guess.

[REF] Possible GPS Fix Epic 4G System File (experimental)

Anybody try this yet?
http://forum.xda-developers.com/showthread.php?t=759976
If you do report back with your results.

Phaze13 said:
Anybody try this yet?
http://forum.xda-developers.com/showthread.php?t=759976
If you do report back with your results.
Click to expand...
Click to collapse
I have done it on my JH2 rom. Seems to be locking on marginally faster, but I haven't tested it with tracking yet, and probably won't be able to until tonight. The track that I saw using it did look better, but who knows if it will be that way for everybody.

Have you noticed any issues related to the change, ie worse call performance/quality, etc. as reported on some of the other posts regarding this issue and possible fixes?

There is a thread on this allready posted in general.
Is there mod who can merge these two so propel wont have to watch both threads and all reports are in one?
Sent from my SAMSUNG-SGH-I897 using XDA App

jneilliii said:
Have you noticed any issues related to the change, ie worse call performance/quality, etc. as reported on some of the other posts regarding this issue and possible fixes?
Click to expand...
Click to collapse
I haven't seen anything regarding those side effects with GPS fixes. No, I'm not experiencing anything like that. Phone still performs must like it did before.

chvybeatsford said:
There is a thread on this allready posted in general.
Is there mod who can merge these two so propel wont have to watch both threads and all reports are in one?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I would merge the threads but the fixes are not the same. This fix is can be flashed in recovery. I would use this fix if you are running I9000 rom. I read in the original thread that there my be some differences in locations of the files for the captivate and vibrant so the fix may not put every thing in the right location. They are working on versions for captivate and vibrant. I loaded stock I9000 jm5 rom and applied the fix. It helped with accuracy but there is still lag.
Edit: It may be that just the vibrant is different.
Case_ said:
Now this is interesting. Trying to make that revert package for Vibrant...and the ROM is entirely different GPS-wise from I9000 and Captivate ROMs! There's no /system/bin/gpsd folder, there's no /system/etc/jupiter.xml and there's no /system/lib/libgps.so...
I wonder why...
Click to expand...
Click to collapse

This has made GPS on my Captivate seems like it's not even trying to get a lock. :-\

I've got an Epic 4G waiting for me at home today. Any dev requests, just ask!
Sent from my SAMSUNG-SGH-I897 using XDA App

InsaneJester17 said:
This has made GPS on my Captivate seems like it's not even trying to get a lock. :-\
Click to expand...
Click to collapse
That is unfortunate. It seems to be helping me on JH2. I've changed my settings back to Standalone instead of MS based and I'm still locking onto as many satellites as I was before. Still not sure if it is holding a lock, but it is giving me 5 meter accuracy from inside my apartment. I'm hoping that the standalone mode does better at tracking than ms based.

dontshakepandas said:
That is unfortunate. It seems to be helping me on JH2. I've changed my settings back to Standalone instead of MS based and I'm still locking onto as many satellites as I was before. Still not sure if it is holding a lock, but it is giving me 5 meter accuracy from inside my apartment. I'm hoping that the standalone mode does better at tracking than ms based.
Click to expand...
Click to collapse
I guess I should note I'm on JF6 in case it matters.

maybe this is why we still dont have froyo...

First of all, I was going to hang on to my nexus until a hi Res display came along but my wife got a vibrant and I got one free, the point is I've only had it a few weeks and I wasn't following it too closely so I don't even know the original due date for froyo. But this is my 4th android so delays certainly don't surprise me. Anywa, as i understand it the SGS has the same specs as the galaxy tab, and apparently adobe flash is a "disaster" on the tab. http://www.sfgate.com/cgi-bin/artic...e-tab-is-an-embarrassing-disaster-2010-11.DTL
So maybe adobe flash on the vibrant has needed special attention. At this rate however I would expect all able galaxy s owners to just buy the nexus s and simply remove themselves from samsung's incapable firmware update team's psychological abuse
I haven't heard complaints about the unofficial versions but maybe they are having trouble stabilizing flash enough for a stable official version such that we have flash working but other bugs exist, maybe getting those bugs ironed negatively affects flash? Or maybe I'm just trying make myself feel better through poor rationalization...

To Be Honest I've Been Running Froyo For A Little While Now And Flash Works Great For Me...
Granted I'm Not on It 24/7 And I'd Rather Use Mobile Sites Most Of The Time.
But When I Do Use Flash It Works Fine

Erickomen27 said:
To Be Honest I've Been Running Froyo For A Little While Now And Flash Works Great For Me...
Granted I'm Not on It 24/7 And I'd Rather Use Mobile Sites Most Of The Time.
But When I Do Use Flash It Works Fine
Click to expand...
Click to collapse
Same here only I prefer the full sites and flash works great I've been watching movies streamed from the web and after two hours of non stop use still no problem
Still flashing

I had no problems with flash but I did set it to On-Demand because it lags up the scrolling. xvideo flash videos played with no problem.

But other countries have froyo already, we don't have froyo mostly because we have a modified GalaxyS, think about it like this, Nexus One would always get updates first because they were plain vanilla not modified (touchwiz or SenseUI). I hope I make sense.

dmolition said:
But other countries have froyo already, we don't have froyo mostly because we have a modified GalaxyS, think about it like this, Nexus One would always get updates first because they were plain vanilla not modified (touchwiz or SenseUI). I hope I make sense.
Click to expand...
Click to collapse
Yeah I'm definitely reaching, I just start getting antsy when these firmware updates get delayed and we don't hear much from the responsible party/s. I feel like almost every firmware update I've ever received has been delayed, but ive always had HTC phones until now, is Motorola always behind as well?
Also, is froyo actually that late (I mean, I know its devastatingly late seeing as gingerbread will be out before we get it but as far as what vibrant owners were promised....)? What was the original due date?

If flash is always turned it will really have issues, but if your turned it on when you need it, it will work fine like watching videos, you just have to wait for about 10 seconds of loading then it will work fine.

i feel the same as OP =[

Another theory to why Froyo isn't officially out...
... is that they responsible party(s) decided to leak a froyo version first. Than let the developers here at XDA hammer out details, then recover it and put the fixes into their own version to make it better. Maybe that is why leaks comes out to us. So the manufacturers can get free alpha testers and fixes.

I honestly just uninstalled flash. It bogged down my phone too much. As soon as I got rid of it, my browser was back to being speedy.

richiehd said:
I honestly just uninstalled flash. It bogged down my phone too much. As soon as I got rid of it, my browser was back to being speedy.
Click to expand...
Click to collapse
Why not just set flash to "on demand" in your browser? It won't load until you click on the flash content. Most browsers support that.

My phone's better with flash if I'm using the skyfire browser. It much faster than the stock.

You are aware that the Nexus S is also a Samsung phone right?

Yes Flash 10.1 does make the browser laggy and presumably consumes more battery due to being a system hog. I am using Obsidian V2 Froyo ROM. There could be work arounds, but it definitely needs optimization for mobile devices.
Now how does this only affect Galaxy S phones and not any other phone running froyo?

Honestly, I'm gonna be pissed if it turns out they held back 2.2 for ****ing *FLASH*.

swehes said:
... is that they responsible party(s) decided to leak a froyo version first. Than let the developers here at XDA hammer out details, then recover it and put the fixes into their own version to make it better. Maybe that is why leaks comes out to us. So the manufacturers can get free alpha testers and fixes.
Click to expand...
Click to collapse
Not in the slightest, at the most they watch over to listen for bugs. We got JI2 when they had already moved on to JI4/JI5 and then to JI6. Samsung doesn't work off of stuff here, the developers work off of what Samsung gives us.

rakeshchn said:
Yes Flash 10.1 does make the browser laggy and presumably consumes more battery due to being a system hog. I am using Obsidian V2 Froyo ROM. There could be work arounds, but it definitely needs optimization for mobile devices.
Now how does this only affect Galaxy S phones and not any other phone running froyo?
Click to expand...
Click to collapse
Not sure but with apps now poppimg up statimg no support for galaxy s I think I shouls have steered clear of them and their hummingbird...
Sent from my SGH-T959 using XDA App

[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6

Here is a flashable version of the full HTC Eris stock ROM - v 2.41.605.6.
March2011_OTA_ReferenceROM_v1.zip ( 99,606,802 Bytes; MD5: 770786915545a16f564a42e344ce7bb6 )
( 02/15/2012 - Re-hosted download link - thanks to XDA user doogald for providing a home for this ROM )
This is what you would get if you took the HTC 2.1 Leak-V3 PB00IMG.zip (same thing as the "Official 2.1 RUU") ROM, and then upgraded it twice - first with the July 2010 OTA, and then after that with the March 2011 OTA. (Using this ROM flash basically saves you that trouble.)
The ROM itself is completely stock, but unlike the "Flashback21" series of ROMs, this flash does not restore a stock recovery, nor flash any radio firmware - you can use it just like any other ROM.
(It is not meant to used for preparing a phone for resale or return - use the FlashBack21 ROM for that).
AGAIN, please note that this ROM is completely stock - it is not even rooted.
Feel free to use it as the basis for other 2.1 Sense ROMs.
If you want to have a "pure HTC stock ROM", but with the benefits of overclocking and rooting, I suggest you flash the "engtools3.zip" and Conap's "CFSv9" kernel immediately after flashing this. This would get you "stock+root+overclocking" - kind of like the original "PlainJane" ROM, but patched up to the current (3/2011) HTC software release.
One other note. Out of curiosity, I decided to run some benchmarks on a GB ROM vs. this HTC ROM, but using the same kernel (CFSv9), and clocked at a fixed rate (setCPU min = max = 748Mhz). So, I performed the kernel replacement and then ran a couple benchmarks.
This allows a crude comparison of what the improvements in the underlying dalvik engine have been between the Eclair release and the Gingerbread release - it is sort of "apples to apples" because the same kernel, scheduler, applications, and clock rates are used.
The numbers here are not the absolute benchmark values, but rather their RATIO - GB:Eclair. (In the cases where the benchmark value is "lower = better", or elapsed time, the value is inverted so that in all cases, a number greater than 1.0 indicates an improvement in Gingerbread). I used JIT = on, and compcache off for the GB ROM.
Code:
Ratio Benchmark
1.57 Quadrant Full
1.16 Elapsed Time (wall clock time) for Quadrant Full
1.10 setCPU "Long Bench"
0.96 setCPU "Native Bench" **
-.-- Linpack for Android - Skipped (not meaningful - too sensitive to JIT)
** This one should be very close to 1.0, as native code does not depend on the dalvik app engine.
In "real world" terms, Quadrant's raw score probably is not too meaningful - but notice that in elapsed time for the full benchmark, the GB ROM was consistently about 16% faster to completion. That measurement - wall clock time - is a "real world" metric. So, in addition to all the other goodness of Froyo/GB, you do seem to get a decent improvement - 10 to 15% - by switching to GB.
cheers,
bftb0

ah nice work man

Good work! I will definitely use this because I always keep falling back in love with stock HTC Sense xD
Sent from my Eris using XDA Premium App

nice! bftb0 always providing quality work/info for the Eris community! i was actually doing something similar! good to see you providing the Eris users even more choices!
thanks again!

Great work!!! This will definitely come in handy

Very nice!

This is great - thanks!

Thank you bftb0!
This saves a lot of time for all the base work on future updated versions of xtrROM and xtrSENSE! I really appreciate all you do for us in the Eris community.
Cheers
Sent from my Eris using XDA App

I think that the superlatives being tossed around here are causing the eyes of the real devs in this forum to roll backwards in their heads. I hope not!
There's not much skill in putting a stock ROM together - just a bunch of checking to make sure you've got all the symlinks, file modes, and permissions set up correctly. Then, zip it up and sign it!
( I did load it onto my phone and check everything to make sure nothing had gone horrible wrong; I suppose that counts for something - but that's not mad skilz, either. )
bftb0

bftb0 said:
I think that the superlatives being tossed around here are causing the eyes of the real devs in this forum to roll backwards in their heads. I hope not!
There's not much skill in putting a stock ROM together - just a bunch of checking to make sure you've got all the symlinks, file modes, and permissions set up correctly. Then, zip it up and sign it!
( I did load it onto my phone and check everything to make sure nothing had gone horrible wrong; I suppose that counts for something - but that's not mad skilz, either. )
bftb0
Click to expand...
Click to collapse
Oh stop being modest. You rock admit it.
Sent from my Eris using XDA App

So what's different in this new ota?
Sent from my CPCEris using XDA App

CPCookieMan said:
So what's different in this new ota?
Sent from my CPCEris using XDA App
Click to expand...
Click to collapse
Looks like it is mostly bug fixes with some enhancements in the Exchange client, MMS capabilities, and several other things.
Here is what Verizon had to say about it.
I did a "file differences analysis" (see this XDA post) that showed that 101 (out of ~127) different pre-installed apps had (.apk) changes, and 20 different framework libraries (.jar) showed changes too. Whether they were major or minor, I don't really know - just that it was apparent that a lot of stuff got "touched". The "system" image in both releases have a little north of 810 files in them - about 260 of those got changed.
I only had the ROM running for a short period of time (to do testing); the one thing that I noticed is that on my home WiFi (uses WPA), the association process was instantaneous - that was sort of rare for me in the past.

Was the radio changed at all in this update?

endoki said:
Was the radio changed at all in this update?
Click to expand...
Click to collapse
NO.
10char

semmtexx said:
Oh stop being modest. You rock admit it.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Agree

bftb0 said:
I think that the superlatives being tossed around here are causing the eyes of the real devs in this forum to roll backwards in their heads. I hope not!
There's not much skill in putting a stock ROM together - just a bunch of checking to make sure you've got all the symlinks, file modes, and permissions set up correctly. Then, zip it up and sign it!
( I did load it onto my phone and check everything to make sure nothing had gone horrible wrong; I suppose that counts for something - but that's not mad skilz, either. )
bftb0
Click to expand...
Click to collapse
semmtexx said:
Oh stop being modest. You rock admit it.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
zach.xtr said:
Agree
Click to expand...
Click to collapse
bftb0, the amount you help EVERYONE, no matter what ROM they are running or trying to run, is extraordinary. You may feel that you're "just doing your thing", but you deserve the praise that you get.

bftb0 said:
I only had the ROM running for a short period of time (to do testing); the one thing that I noticed is that on my home WiFi (uses WPA), the association process was instantaneous - that was sort of rare for me in the past.
Click to expand...
Click to collapse
I never had problem with WiFi and stock, but I do for sure with CM ROMs running CFS when I turn on WiFi from a widget. However, just to test, I flashed CFS v9 over this last night, turned off WiFi for a while, then turned it back on from the widget, and it also associated right away for me.

I have themed this ROM and am about 80% done with it. Thanks for this runs really well on the stock kernal. I am just wondering how popular 2.1 is now with Froyo and GB out. If there was a base of people that like sense eclair I would consider releasing it once it was finished.

jonathanphx1 said:
I have themed this ROM and am about 80% done with it. Thanks for this runs really well on the stock kernal. I am just wondering how popular 2.1 is now with Froyo and GB out. If there was a base of people that like sense eclair I would consider releasing it once it was finished.
Click to expand...
Click to collapse
I would love a theme with a blue battery and themed dialer! Would it be similar to the "Sensibility for Sense 2.2" theme you were working on?

No offense to anyone, but I would likely only even try the March OTA in the form of an updated ROM from zach.xtr, or if I modified it myself.
Nothing against you, it's just that whenever I want to go back to near stock, xtr's ROMs are just too well established for me to experiment with anything else.

GB Update reviews.

I just want to see how everyone feels about the official update. My niece has my old epic rooted with a ec05 rom. I just want to see if I should get her to update.
So whats your thoughts, first impressions, battery life and all.

cdszoke said:
I just want to see how everyone feels about the official update. My niece has my old epic rooted with a ec05 rom. I just want to see if I should get her to update.
So whats your thoughts, first impressions, battery life and all.
Click to expand...
Click to collapse
Well here's my two cents...gps lock is not fixed...root is currently impossible to retain with the stock kernel. You need some kind of modified kernel to keep root. Keyboard lag is still present unless your rooted and install a fix.
These above listed items do have remedies, however they require a custom rom or multiple patches to fix.
That being said...if you always run stock there are no additional negatives. Gingerbread is much faster,smoother and cleaner imo. Take it from there.
Here's a link to all the advancements thus far: http://forum.xda-developers.com/showthread.php?p=19155759
Sent from my SPH-D700 using Tapatalk

Still waiting on the offical version.
But I have been running swiss cheese samsprint for months with no issues at all. Everything fully functional.

chkchkboom said:
You need some kind of modified kernel to keep root. Keyboard lag is still present unless your rooted and install a fix.
Click to expand...
Click to collapse
I think both of these statements are wrong based on my experience.
I have root and have no modified kernel. I think you can keep root without a fix, what you can't keep is a custom recovery program (like CWM).
I have had no keyboard lag so far. If it is there, it is definitely MUCH better than the previous version.

Milkman00 said:
I think both of these statements are wrong based on my experience.
I have root and have no modified kernel. I think you can keep root without a fix, what you can't keep is a custom recovery program (like CWM).
I have had no keyboard lag so far. If it is there, it is definitely MUCH better than the previous version.
Click to expand...
Click to collapse
Wait what?

The Root said:
Wait what?
Click to expand...
Click to collapse
What was unclear?

Milkman00 said:
I think both of these statements are wrong based on my experience.
I have root and have no modified kernel. I think you can keep root without a fix, what you can't keep is a custom recovery program (like CWM).
I have had no keyboard lag so far. If it is there, it is definitely MUCH better than the previous version.
Click to expand...
Click to collapse
It is not incorrect...just incomplete...I think its foolish to have root without a good means of nandroid backup and custom recovery.
Sent from my SPH-D700 using Tapatalk

chkchkboom said:
It is not incorrect...just incomplete...I think its foolish to have root without a good means of nandroid backup and custom recovery.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I have backup with Mybackup and Titanium, so I am more than happy with my backup options. ROOT itself is very important to me (and a lot of other people), so given the option I would rather have root and no custom recovery program, as opposed to a custom recovery program and no root.
A very important distinction to make.

Milkman00 said:
What was unclear?
Click to expand...
Click to collapse
No, just unnerving that they'd have such a forceful recovery program. Samsung has been sneaking little locks in things lately. Odin can break them but it's frustrating that they've gone down this road.

The Root said:
No, just unnerving that they'd have such a forceful recovery program. Samsung has been sneaking little locks in things lately. Odin can break them but it's frustrating that they've gone down this road.
Click to expand...
Click to collapse
ah gotcha.

there really is no point in staying on froyo ec05 now. the only thing i could think of that would keep me on it would be SRF1.2 but since you didnt mention she had that i would say just update it for her. Things are quicker, snappier. The OS is built to be more stable and just all around better for the phone than the froyo version was.

The Root said:
No, just unnerving that they'd have such a forceful recovery program. Samsung has been sneaking little locks in things lately. Odin can break them but it's frustrating that they've gone down this road.
Click to expand...
Click to collapse
+1.... I didn't want to be the theorist.
Sent from my SPH-D700 using Tapatalk

Keyboard works so damn well!! Seriously its never worked this well for me. I'm running the deodexed build with nubernel so I dunno if there are any key lag hack built in or not.
Cd's or tapes?

My main beef with my phone has been fixed with this update. Music playback was annoying. Didn't matter if it was stock player or PowerAmp, I would get a weird hiccup at about 3 seconds into every song. On top of that, I could hear some electrical crackling when doing certain things while listening to music, especially while using wired tether. Gingerbread has eliminated it and music playback has been flawless for me all day so far. Not even a little click when the screen goes on/off anymore.

No doubt this phone still needs to be rooted with some patches just to make it useable. I'm disappointed samsprint took this long and still left so many of the original issues that shipped with the phone on eclair.
Basically it has the exact same widgets and touchwiz as always but with the underlying os updated to gingerbread.
I was hoping we would get the sgs 2 version of tw with the new widgets, and see the keyboard, and gps working out of the box.
Also the browser is pissing me off. It removed the zoom buttons and double tap isn't zooming in anymore...?
Its not all bad. With the gps fix (flashed in cwm) I'm getting better gps locks than ever before on this phone. Also the system as a whole is a bit faster. Unfortunately you will still make tradeoffs by updating.
Edits:
Tap to zoom works on non-mobile websites in the browser. Using my /data hack I was able to change default text size also.
Notification LED does in fact appear to be fixed...but there is a very long time between blinks (something like 20 seconds), would be much happier with a 2 sec blink. It is so slow, I thought it was not working.

redvexx said:
Still waiting on the offical version.
But I have been running swiss cheese samsprint for months with no issues at all. Everything fully functional.
Click to expand...
Click to collapse
You have to be on EC05 to get the update. It wont work on EE03.
Sent from my Galaxy Tab 10.1

chkchkboom said:
+1.... I didn't want to be the theorist.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not theory. The lock patches on Galaxy Tab are a pain. So happy I got on In Paris so quickly.

|| Acer || said:
You have to be on EC05 to get the update. It wont work on EE03.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
So I wont even get the notification of an update?
I'm not sure If I even want it considering I have been using this ROM with no issues.

redvexx said:
So I wont even get the notification of an update?
I'm not sure If I even want it considering I have been using this ROM with no issues.
Click to expand...
Click to collapse
No u will not get the notification but I would recommend updating to the latest since I can say it will be more stable than one of the oldest gb builds out for this phone
Sent from my Google Nexus S 4G using xda premium

metalblaster said:
there really is no point in staying on froyo ec05 now. the only thing i could think of that would keep me on it would be SRF1.2 but since you didnt mention she had that i would say just update it for her. Things are quicker, snappier. The OS is built to be more stable and just all around better for the phone than the froyo version was.
Click to expand...
Click to collapse
Sorry I forgot to mention I put srf 1.2 on it before I sent her the phone.