maemo.org - Talk
Page 7 of 17 « First 56 7 89 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   MeeGo / Harmattan (https://talk.maemo.org/forumdisplay.php?f=45)
-   -   [PLEASE JOIN] Petition for bug fixing for N9 (https://talk.maemo.org/showthread.php?t=89318)

rainisto 2013-03-04 17:29
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by Lucazz990 (Post 1326805)
I think we are ready to go...

Any suggestion/add before trying this? :)
Your only hope to get these fixed is to post the petition to the community and hope that community fixes these... :)

There is _zero_ Harmattan R&D people still in Nokia to fix any bugs (they all have been fired quite a while ago), nobody has even read harmattan bugzilla since january 2012. If there are any subcontactors left, they will only fix critical security releated bugs, like if some easy to use sim unlock exploit get released then there is a small change that it will be looked into. (Although even that might be ignored, since TMO already had a thread of how to bruteforce calculate the sim unlock code, and that hole was just ignored).

rainisto 2013-03-04 18:14
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by veeall (Post 1326826)
Battery drop bug is annoying. Does somebody here knows how to get it back to correct battery readings without a reboot? I had 40% battery which suddenly dropped to 4%, but after reboot i had about 20% still, thus almost half of power gone rebooting a phone. And i needed badly a battery to last.

Yes, Nokia should fix it, regardless their current mobile phone strategy.
Its not a bug but feature, battery drainage is not linear like explained in here http://smackerelofopinion.blogspot.f...-draining.html

There is no way to fix the feature since voltages measured from battery can vary randomly.

Bharateeyudu 2013-03-04 18:26
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by Lucazz990 (Post 1326805)
I think we are ready to go...


Any suggestion/add before trying this? :)
I noticed a minor bug recently in the recent call log. When I open call log the default view ("Recent Calls") shows the information correctly, with recent calls marked as "Today", "Yesterday", "Last Week", and "Older".

However, when I tap the top bar ("Recent Calls") to select a category (Missed, Received or Dialed), and then revert back to "Recent Calls", it messes up the time stamps and doesn't group the call logs correctly.

Pardon me if it doesn't make a lot of sense, but you can try it by following the steps:

1. Open call log through 'Phone' app
2. Notice the time stamps, the dates and the description match (Today, Yesterday, etc.)
3. Tap the top bar that reads "Recent calls" and select any of the options "Missed, Received or Dialed"
4. The time stamps for the filtered list still matches
5. Now tap on the top bar again and select "Recent calls" and you'll notice that the time stamps and descriptions don't match. Today will actually include calls from today, and two past days, similarly yesterday and last week!

Lucazz990 2013-03-04 18:51
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by Bharateeyudu (Post 1326847)
I noticed a minor bug recently in the recent call log. When I open call log the default view ("Recent Calls") shows the information correctly, with recent calls marked as "Today", "Yesterday", "Last Week", and "Older".

However, when I tap the top bar ("Recent Calls") to select a category (Missed, Received or Dialed), and then revert back to "Recent Calls", it messes up the time stamps and doesn't group the call logs correctly.

Pardon me if it doesn't make a lot of sense, but you can try it by following the steps:

1. Open call log through 'Phone' app
2. Notice the time stamps, the dates and the description match (Today, Yesterday, etc.)
3. Tap the top bar that reads "Recent calls" and select any of the options "Missed, Received or Dialed"
4. The time stamps for the filtered list still matches
5. Now tap on the top bar again and select "Recent calls" and you'll notice that the time stamps and descriptions don't match. Today will actually include calls from today, and two past days, similarly yesterday and last week!
I tried but it's all as it should be... :confused:

Bharateeyudu 2013-03-04 19:24
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by Lucazz990 (Post 1326860)
I tried but it's all as it should be... :confused:
That's weird... maybe it's just my N9! :(

tortoisedoc 2013-03-04 19:30
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by veeall (Post 1326826)
Battery drop bug is annoying. Does somebody here knows how to get it back to correct battery readings without a reboot? I had 40% battery which suddenly dropped to 4%, but after reboot i had about 20% still, thus almost half of power gone rebooting a phone. And i needed badly a battery to last.

Yes, Nokia should fix it, regardless their current mobile phone strategy.
For me moving the power saving settings from 20 to 10% does the job - sometime.
It is indeed a weird bug. I wonder if it is in the QT Layer..

EDIT : Sorry, just noticed this now :

Quote:
Originally Posted by rainisto (Post 1326840)
Its not a bug but feature, battery drainage is not linear like explained in here http://smackerelofopinion.blogspot.f...-draining.html

There is no way to fix the feature since voltages measured from battery can vary randomly.
the fact that the battery life is not linear is understandable; but the fact that it drops from barely above power saving to switching completely off without nothing in between goes way bejond that imo..

sony123 2013-03-04 19:36
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by rainisto (Post 1326830)
Your only hope to get these fixed is to post the petition to the community and hope that community fixes these... :)

There is _zero_ Harmattan R&D people still in Nokia to fix any bugs (they all have been fired quite a while ago), nobody has even read harmattan bugzilla since january 2012. If there are any subcontactors left, they will only fix critical security releated bugs, like if some easy to use sim unlock exploit get released then there is a small change that it will be looked into. (Although even that might be ignored, since TMO already had a thread of how to bruteforce calculate the sim unlock code, and that hole was just ignored).
Then why is there twitter update for N950? Seems strange if Nokia isn't planning something (no matter how small it will be).

Or maybe the contractor accidentally released something XD

tortoisedoc 2013-03-04 19:44
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by sony123 (Post 1326876)
Then why is there twitter update for N950? Seems strange if Nokia isn't planning something (no matter how small it will be).

Or maybe the contractor accidentally released something XD
Single App update !== FW update, unfortunately.
Stop dreaming...

Lucazz990 2013-03-04 20:39
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by sony123 (Post 1326876)
Then why is there twitter update for N950? Seems strange if Nokia isn't planning something (no matter how small it will be).

Or maybe the contractor accidentally released something XD
They are updating twitter because of the new API, 1.1, I'm not an expert but afaik without this update the app should stop working properly...

veeall 2013-03-04 21:10
Re: [PETITION TO NOKIA] Bug fixing for N9
 
Quote:
Originally Posted by rainisto (Post 1326840)
Its not a bug but feature, battery drainage is not linear like explained in here http://smackerelofopinion.blogspot.f...-draining.html

There is no way to fix the feature since voltages measured from battery can vary randomly.
Ok, but i just now happened to have a sudden battery drop to 04%, i tried few refreshes from a n9 qtwek refresher, and after doing 'restart bme' battery level jumped back to 15%.

As you know phone switches itself off when on low battery, even if it is just misreported to be low, but rebooting takes another unnecessary toll on power level. Anyway, there's hope i don't need to do full reboot but hopefully restarting bme(for what that stands for?) is enough, as happened just now.


All times are GMT. The time now is 02:06.
Page 7 of 17 « First 56 7 89 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8