Reply
Thread Tools
Posts: 455 | Thanked: 278 times | Joined on Dec 2009 @ Oregon, USA
#51
Originally Posted by devu View Post
Have you seen this?

I know many ppl jumping string to TALK.

My 2 cents?



YES!

Maybe I'm mistaken, but how can something which has never had a release date be 'late'??
 

The Following 6 Users Say Thank You to craftyguy For This Useful Post:
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#52
Originally Posted by craftyguy View Post
Maybe I'm mistaken, but how can something which has never had a release date be 'late'??
VERY good point !!!
 
HellFlyer's Avatar
Posts: 1,148 | Thanked: 613 times | Joined on Mar 2010 @ Toronto
#53
Originally Posted by chemist View Post
To pick up on Texrats advice...

Please be aware of that HK version is some kind of different to the global version so there maybe other things they have to look at for the global one.

Asking again and again for explanations wont help as you wont get much more than already released.

Nokia has a demand of working PRs so it might take some time to fullfill this. As already mentioned in the email, there are some bugs not easy to track down. I am currently investigating in hildon-home hickups which take about 2-5 days to occure so to determine which of the 3rd party programs is causing it takes weeks of testing already. He wrote about longterm issues and maybe they got a way to get something like home mess up in a shorter time but still it will take weeks to test and fix.

If you like to have your phone broken or bricked because of a leaked PR's RC this is ok with me. Maybe there is no closed community test for PR1.2 as Nokia does not want to take the risk yet. Have you thought of that they may bricked devices while testing and decided to not release yet?

Please chill out on the PR1.2 topic. We all have to wait! Posting off-topic and Nokia requests all over the place doesn't help any one but keeps the moderators busy.
I had some issues with hildon-home ( freezeing and nonresponsive UI) caused by facebook widget , did you look at that?
__________________
The quieter you become the more you are able to hear


"I'm a N900 user, can I haz Flash 10 plz?!11!?" © Jaffa


Elopocalypse started on 11.02.2011
 
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#54
Originally Posted by HellFlyer View Post
I had some issues with hildon-home ( freezeing and nonresponsive UI) caused by facebook widget , did you look at that?
I am not sure who that is directed at but as i dont use facebook i cannot comment, as for the difference between the leaked and awaited fw's i am sure it will be a huge difference but if the leaked one is anything to go by then all i can say is WHEN the official one does come it will be something like hello world i am the N900 ha ha.
 
felbutss's Avatar
Posts: 579 | Thanked: 286 times | Joined on Oct 2009 @ Australia
#55
same i dont use facebook widget. now i understand why this is taking so long. this is a huge issue that any widget can cause. hope they change something to avoid this again.

lol and this is just 1 bug.
 
Posts: 119 | Thanked: 57 times | Joined on Dec 2009 @ Rotterdam, port to Europe !
#56
Originally Posted by rpgAmazon View Post
First: there is a work arround, so NO BRICK
Second: same downgrading from PR1.1.1, so OFFICIAL RELEASES BRICK THE PHONE?
You must read the thread.
1. You admit there can be a brick, but there is a work around...
2. The downgrading to the official FW 1.1. causes the brick, see my point 1.
 
felbutss's Avatar
Posts: 579 | Thanked: 286 times | Joined on Oct 2009 @ Australia
#57
u cant brick a n900 99%. that 1% i dont even know how it would be possible


brick=Never being able to restore the phone

its more like temporarily disabled till a restore

Last edited by felbutss; 2010-05-08 at 18:12.
 

The Following User Says Thank You to felbutss For This Useful Post:
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#58
Originally Posted by eerde View Post
1. You admit there can be a brick, but there is a work around...
2. The downgrading to the official FW 1.1. causes the brick, see my point 1.
I will jump in here and try to explain something ok , the brick situation would only have happened if someone did not follow proper procedere on flashing and as for downgrading i am not entirely sure it is possible to completely downgrade so there might lye the problem but as stated there IS a workaround which does prove its not the leaked fw.
Please dont listen or take ion everything you read from other forums because this forum IS the forum for N900 users and here is where you will get correct info.
For your info i did flash the erlier released fw and back to the leaked fw for no other reason than to see if it was possible or not and i did not have a single problem.
 
NvyUs's Avatar
Posts: 1,885 | Thanked: 2,008 times | Joined on Aug 2009 @ OVI MAPS
#59
downgrading from PR 1.2 leak to 1.1.1 is no more dangerous than downgrading from PR 1.1.1 to PR 1.0
this is all a non argument really if people would be truthful.

however i do not recommend people touch leaked firmware, but if you do whatever happens or does not happen its all of your own doing and you will get little sympathy

Last edited by NvyUs; 2010-05-08 at 18:18.
 
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#60
Originally Posted by NvyUs View Post
downgrading from PR 1.2 leak to 1.1.1 is no more dangerous than downgrading from PR 1.1.1 to PR 1.0
this is all a non argument really if people would be truthful.

however i do not recommend people touching leak firmware but if you do whatever happens or does not happen its all your own doing
Once again this is right and yes i agree on the advice recommending not to touch leaked anything because 9 times out of 10 it has problems BUT this time i was one of the first 5 or 6 that did flash and YES we did take a hell of a chance that luckily paid off as their did not seem to be any fatal effects.
But that advice NOT to recommend i agree with .
 
Reply

Tags
black hole, vortex of dumb

Thread Tools

 
Forum Jump


All times are GMT. The time now is 10:38.