hey ATnTdude, did you end up fixing your error? i get the same boot error when flashing, so i just ended up nandroid'ing back to frf50.
i was going to try flashing the stock one and rooting it.
[LINKS] Nexus One FRF72
- Thread starter deanrparry
- Start date
hey ATnTdude, did you end up fixing your error? i get the same boot error when flashing, so i just ended up nandroid'ing back to frf50.
i was going to try flashing the stock one and rooting it.
In fact a couple more of us already questioned it. You just didn't notice our posts.
Had 40ish mb in FRF50 and 40ish in FRF72.
Unstable FRF72
I am experiencing instability
with FRF72, I didn't had any problem with FRF50, Even one time my phone hangs and I forced to restart it, but everything back to normal after that. I think it should be some compatibility problem between the app I have and FRF72 specially Launcher Pro. Anybody else had any problem like that? (By the way, this is my first post on xda-developers, I am checking this forum for years now, but recently I bought a N1 and decided to participate a little in this forum )
I am experiencing instability
with FRF72, I didn't had any problem with FRF50, Even one time my phone hangs and I forced to restart it, but everything back to normal after that. I think it should be some compatibility problem between the app I have and FRF72 specially Launcher Pro. Anybody else had any problem like that? (By the way, this is my first post on xda-developers, I am checking this forum for years now, but recently I bought a N1 and decided to participate a little in this forum )I haven't seen it mentioned, but the issue with Google Voice needing to be tapped twice or crashing after opening is fixed with 72.
I thought about going to stock, updating, then rerooting, then I thought "screw it" and decided to wait for the next update.
What's changed in the alarm clock notification? I've a few issues with the current implementation in 2.1.the alarmclock notification has a new interface!!!!!
My edge has been acting up since 2 days ago, cant switch to it manually anymore, that was with FRF50, its still happening now with FRF72.
Try selecting your network operator again, this worked for me.
Not sure if this has something to do with FRF72 or what. But it seems that since the update I will get occasional delays in the Swype keyboard. I'll be swyping along and suddenly it will hang, I'll keep swyping words and after a second or two it will catch up and display the words I swyped. Could be a problem in the newest Swype beta too.
Thank you, I actually did see one response a few pages back but I considered 1 relatively equal to 0. Anyway glad to know there are multiple others. I realized the second article mentioning the mem boost was reporting on phandeoid which reported the boost so I guess its just a reporting mistake...no biggie I just didn't want to be left out
Thank you, I actually did see one response a few pages back but I considered 1 relatively equal to 0. Anyway glad to know there are multiple others. I realized the second article mentioning the mem boost was reporting on phandeoid which reported the boost so I guess its just a reporting mistake...no biggie I just didn't want to be left out
I repeat
FRF50 I had 28meg internal showing in SD and phone storage, now have 54meg.
After a few days, it's gone down to 42meg, but there is absolutely an increase.
Am I the only one having location detection issues after reboot?
It's easily reproducible: location detection via 3G doesn't work after reboot with wi-fi and gps off. So far I've seen only one other report of a similar problem. This may be not just in FRF72, but in FRF50 as well.
@ilanad
The reason your internal memory has dropped is due to the browser cached files go to settings,applications,manage applications,all applications,scroll down to browser,tap it,clear cache.hope this helps
The reason your internal memory has dropped is due to the browser cached files go to settings,applications,manage applications,all applications,scroll down to browser,tap it,clear cache.hope this helps
Anyone else having issues with tethering?
frf50 worked great with wpa2 encryption, but I can't connect with it enabled now. Open works fine still.
....
edit:
Scratch that - turns out it was client based not phone that was the problem.
frf50 worked great with wpa2 encryption, but I can't connect with it enabled now. Open works fine still.
....
edit:
Scratch that - turns out it was client based not phone that was the problem.
Last edited:
F
flybyme
Guest
Dial *#*#4636#*#*
Phone Information
Scroll down and make sure its on WCDMA Preferred.
Similar threads
