![]() |
2012-09-14
, 19:15
|
|
Posts: 1,390 |
Thanked: 710 times |
Joined on May 2012
@ Beirut, Lebanon
|
#2
|
I will vote AMD for president next time if I'm having any shares during next meeting.
![]() |
2012-09-14
, 19:20
|
|
Posts: 1,359 |
Thanked: 1,292 times |
Joined on Oct 2011
@ Tartus.Syria
|
#3
|
![]() |
2012-09-14
, 19:39
|
Posts: 64 |
Thanked: 42 times |
Joined on Jun 2009
|
#5
|
![]() |
2012-09-14
, 19:42
|
|
Posts: 1,390 |
Thanked: 710 times |
Joined on May 2012
@ Beirut, Lebanon
|
#6
|
If you don't want to do a reflash, consider forcing a re-install of the original Nokia packages ("apt-get --reinstall install ..." -- of course this can be problematic when packages were incepted and have a higher security priority than the ones supplied by Nokia; in that situation, you can probably still download them by using -d and then re-incepting them).
Using this technique, I've managed to fix an N900 repeatedly that was otherwise hopelessly screwed up; just make sure root access via ssh is always one of the first things you enable on the phone. With the right configuration, you can sometimes even fix the phone when the UI is completely broken (this doesn't apply as much to the N9 of course, due to MALF).
As for which packages need to be re-installed -- I have never been systematic enough to create a specific list, but usually found the culprits by re-installing packages that seemed UI-related. You can also often find out all related package names with a search query like "apt-cache showpkg <package-name>".
The downside of this procedure is that all customizations are lost (but then again, that is often the cause of your problems to begin with).
I will vote AMD for president next time if I'm having any shares during next meeting.
![]() |
2012-09-14
, 19:52
|
|
Posts: 1,390 |
Thanked: 710 times |
Joined on May 2012
@ Beirut, Lebanon
|
#7
|
1- Please learn what a full stop is
2- Dont double post like that, pretty sure some meego guys will help without the need to ask twice
Good luck
./sifo
I will vote AMD for president next time if I'm having any shares during next meeting.
![]() |
2012-09-14
, 19:54
|
Posts: 64 |
Thanked: 42 times |
Joined on Jun 2009
|
#8
|
I do not understand one word.. Well.. I just wanna know is this a software or hardware issue? Will a reflash fix it or lead to further problems?
![]() |
2012-09-14
, 20:00
|
|
Posts: 1,390 |
Thanked: 710 times |
Joined on May 2012
@ Beirut, Lebanon
|
#9
|
That's not an easy assessment to make (unless someone has dealt with specifically this situation before) -- but more often than not, I've found such cases to be software-related.
To get more detailed information on the battery, charge level, etc. you can always run "lshal | grep batt" from the command line. Look at the battery.reporting.current line, plug the phone in for 30 minutes (using a known, working, dumb charger -- i.e. don't rely on USB, etc.), then run the command again and see if it has changed. If it shows a value up to the maximum (shown on battery.reporting.design line) and it changes in that 30 minute interval, chances are, it's software-related.
Note, to enable command line input, the easiest way is to enable developer mode.
I will vote AMD for president next time if I'm having any shares during next meeting.
![]() |
2012-09-14
, 20:20
|
|
Posts: 1,390 |
Thanked: 710 times |
Joined on May 2012
@ Beirut, Lebanon
|
#10
|
I will vote AMD for president next time if I'm having any shares during next meeting.
Twitter: @ahmadmdaher
Do good for a human being and like my art page!
Last edited by AMD; 2012-09-18 at 13:52.