Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 1 hr ago -
Maemo repository (3)
to Community by torsen - 1 day, 17 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 15 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 21 hrs ago - more...
 |
|
2011-05-06
, 14:36
|
|
Posts: 968 |
Thanked: 663 times |
Joined on Jun 2010
@ Australia (Melbourne/vic) / Lebanon (Zgharta/north)
|
#402
|
Originally Posted by vi_
yes i know i have bad langiage in my post, but it was never refered to you, i didn't call you anything, and i wasn't trolling in my posts before, maybe the last one was, and i should get out ride my quadbike too, its sunny over here too .
This is feedback.
This is feedback.
This is feedback.
This is a$s.
The approximate value of the feedback could possibly be calculated as such:
Code:feedback=((information*understanding)/grasp of english^-1)
You are right zdanee, I have descended into bait-trolling, I think I shall just have to stop wasting time on this forum and go outside and ride my bike for a change. Hey there is sunny out here!... ... ...
__________________
rolling down the street, smoking ENDO, sipping on gin and juice
laid back, with my mind on my money and my money on my mind .
rolling down the street, smoking ENDO, sipping on gin and juice
laid back, with my mind on my money and my money on my mind .
|
|
2011-05-06
, 14:54
|
|
Posts: 27 |
Thanked: 10 times |
Joined on Mar 2010
|
#403
|
Well...for me after updating to v47 and rebooting phone wont start anymore. First I thought I just was careless and battery finshed but when looking indicator light when charging it's just yellow, not blinking with yellow color.
When I try to start phone Nokia logo appears and indicator light is white so at this point everything seems to be ok - but stucks there...
Can not flash either.Computer (Windows7 & Windows XP) does not recognize USB device anymore. So when I try to flash flasher stops in quite beginning erroring "Suitable USB device not found, waiting"..
When I try to start phone Nokia logo appears and indicator light is white so at this point everything seems to be ok - but stucks there...
Can not flash either.Computer (Windows7 & Windows XP) does not recognize USB device anymore. So when I try to flash flasher stops in quite beginning erroring "Suitable USB device not found, waiting"..
|
|
2011-05-06
, 15:12
|
|
Posts: 237 |
Thanked: 274 times |
Joined on Jul 2010
|
#404
|
Originally Posted by Salatheel
your battery seems to be empty in a way the phone doesn't start..
Well...for me after updating to v47 and rebooting phone wont start anymore. First I thought I just was careless and battery finshed but when looking indicator light when charging it's just yellow, not blinking with yellow color.
When I try to start phone Nokia logo appears and indicator light is white so at this point everything seems to be ok - but stucks there...
Can not flash either.Computer (Windows7 & Windows XP) does not recognize USB device anymore. So when I try to flash flasher stops in quite beginning erroring "Suitable USB device not found, waiting"..
the n900 does boot into charging mode inorder for the battery to charge (blinking yello/orange led) ,
if the battery is quite empty , the charging is managed by the hardware battery chip , in that charging mode , you can't start the phone and the led will have a solid yellow color .
connect your phone to your pc / charger and leave it connected for half an hour and let it charge .
 |
|
2011-05-06
, 16:07
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#405
|
For what it's worth, I've been getting constant lockup/reboots while using this kernel that I have been unable to isolate as to the reason.
Not present on v46, BFS or other releases.
Not present on v46, BFS or other releases.
|
|
2011-05-06
, 16:14
|
|
Posts: 27 |
Thanked: 10 times |
Joined on Mar 2010
|
#406
|
Originally Posted by ivyking
There is also weird appearance; when charging, yellow light's "blinking frequency" is about 1 or 2 minutes...I'll let my phone stay in charger nigth over and try to do something again...
your battery seems to be empty in a way the phone doesn't start..
the n900 does boot into charging mode inorder for the battery to charge (blinking yello/orange led) ,
if the battery is quite empty , the charging is managed by the hardware battery chip , in that charging mode , you can't start the phone and the led will have a solid yellow color .
connect your phone to your pc / charger and leave it connected for half an hour and let it charge .
 |
|
2011-05-06
, 17:55
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#407
|
I would like to point that from my experience, Titan's undervolting profiles were really BAD and maybe this is source of all reboot problems people are reporting here.
Yea, i was also using "ideal" profile for long time without problems - at least that was what i thought. Then, after few months i started to encounter VERY strange problems with more and more applications - to make long story short, i was impossible to explain what was really happening, restoring backups helped for some time, then weirdness occur again. Also, i started to encounter strange reboots.
At the beginning i blamed applications and tweaks installed last, but hours of testing get me nothing and problems were all together unreproduceable. So i started to wonder if undervolting may occur files/filesystem corruption - especially that, after few of the strange reboots, maemo did automatic fsck (i enabled that option in one of kernel-power setting files - to do fsck when "needed", whatever it means).
I tried lover undevolting (higher voltage),and in next few months problems tend to occur less, but still appeared after some time. So i looked at titan's setting - they we're strange, to say at lwast. Check for yourself - how voltage rise with higher frequency - many times it seems unbalanced. I did my own profile, completely from scratch, based on standard Nokia settings + ideal titan's setting (Something between stock settings and "ideal" settings, to get voltage on 500 mhz and voltage on 900 mhz - ie. min and max voltage for me. then, voltage progress between min and max was adjusted by me, cause titan's setting were trash in my opinion).
From that time, i don't have ANY problems of this kind for many months, no single strange reboot or corrupted file. No single need for backup restore. I was even able to apply good tweaks, that before i blamed of system instability.
Sorry for that long post, but i think that many people here can encounter the same. I don't have hard proof, so this post scientific value may be close to 0 - as i said, problems we're not reproduceable - but, titan's undervolting profiles are quite popular here, and i think that this may be cause of many false problems reports in many part of forum, unrelated to on-topic subjects. Keep in mind that after preparing my own undervolting settings (my N900 is still undervolted, but not so high) i got no problems and my N900 is set to 500 mhz min - 900 mhz max all the time. also i did NOT feel any noticeable higher battery drain due to higher voltage.
Also, to make things clear - i really appreciate titan's hard work on kernel-powers - even that he dropped it without any notice - but i think that undervolting settings were undertested, and becomes too popular, especially "ideal".
Filesystem corruption due to undervolting is *****y thing to detect and even harder to reproduce. Maybe we should suggest, that any problems, before reporting, should be reproduced not only without overclocking, but also without undervolting? And, what is also very important, on filesystem backup that was NOT "poisoned" by undervolting?
Last edited by Estel; 2011-05-06 at 18:04.
Yea, i was also using "ideal" profile for long time without problems - at least that was what i thought. Then, after few months i started to encounter VERY strange problems with more and more applications - to make long story short, i was impossible to explain what was really happening, restoring backups helped for some time, then weirdness occur again. Also, i started to encounter strange reboots.
At the beginning i blamed applications and tweaks installed last, but hours of testing get me nothing and problems were all together unreproduceable. So i started to wonder if undervolting may occur files/filesystem corruption - especially that, after few of the strange reboots, maemo did automatic fsck (i enabled that option in one of kernel-power setting files - to do fsck when "needed", whatever it means).
I tried lover undevolting (higher voltage),and in next few months problems tend to occur less, but still appeared after some time. So i looked at titan's setting - they we're strange, to say at lwast. Check for yourself - how voltage rise with higher frequency - many times it seems unbalanced. I did my own profile, completely from scratch, based on standard Nokia settings + ideal titan's setting (Something between stock settings and "ideal" settings, to get voltage on 500 mhz and voltage on 900 mhz - ie. min and max voltage for me. then, voltage progress between min and max was adjusted by me, cause titan's setting were trash in my opinion).
From that time, i don't have ANY problems of this kind for many months, no single strange reboot or corrupted file. No single need for backup restore. I was even able to apply good tweaks, that before i blamed of system instability.
Sorry for that long post, but i think that many people here can encounter the same. I don't have hard proof, so this post scientific value may be close to 0 - as i said, problems we're not reproduceable - but, titan's undervolting profiles are quite popular here, and i think that this may be cause of many false problems reports in many part of forum, unrelated to on-topic subjects. Keep in mind that after preparing my own undervolting settings (my N900 is still undervolted, but not so high) i got no problems and my N900 is set to 500 mhz min - 900 mhz max all the time. also i did NOT feel any noticeable higher battery drain due to higher voltage.
Also, to make things clear - i really appreciate titan's hard work on kernel-powers - even that he dropped it without any notice - but i think that undervolting settings were undertested, and becomes too popular, especially "ideal".
Filesystem corruption due to undervolting is *****y thing to detect and even harder to reproduce. Maybe we should suggest, that any problems, before reporting, should be reproduced not only without overclocking, but also without undervolting? And, what is also very important, on filesystem backup that was NOT "poisoned" by undervolting?
Last edited by Estel; 2011-05-06 at 18:04.
|
|
2011-05-06
, 18:25
|
|
Posts: 805 |
Thanked: 1,605 times |
Joined on Feb 2010
@ Gdynia, Poland
|
#408
|
Originally Posted by Estel
Could you upload yout profile file or send it to me via PM (I'm curious what you did there and am eager to test). What about battery life? How often do you need to charge?
I tried lover undevolting (higher voltage),and in next few months problems tend to occur less, but still appeared after some time. So i looked at titan's setting - they we're strange, to say at lwast. Check for yourself - how voltage rise with higher frequency - many times it seems unbalanced. I did my own profile, completely from scratch, based on standard Nokia settings + ideal titan's setting (Something between stock settings and "ideal" settings, to get voltage on 500 mhz and voltage on 900 mhz - ie. min and max voltage for me. then, voltage progress between min and max was adjusted by me, cause titan's setting were trash in my opinion).
|
|
2011-05-06
, 18:36
|
|
Posts: 112 |
Thanked: 92 times |
Joined on Nov 2010
|
#409
|
i too use my own voltage settings coz i find lv/ul/xlv voltages are a little too much on the lower side to my liking, phone might turn on and run but it might do incorrect calculations due to too low voltage but the end users wont notice it most of the time, the same reason we run prime95 for hours to check oc stability/calulation accuracy on desktops to ensure rock solid stability.
nkirk
nkirk
|
|
2011-05-06
, 22:46
|
|
Posts: 345 |
Thanked: 117 times |
Joined on Jan 2010
@ uk
|
#410
|
Originally Posted by kyllerbuzcut
seems to be back to normal now. Perhaps some teething problem with new kernel and media tracker or something, but system seems to have settled now and looks all ok on omap1.
dont kbow if this is a definite problem yet BUT booted into omap1 'normal' mode last night and left it to charge overnight for work in the mornniing. Same as usual. This morning the battery widget, battery graph and battery icon all seemed to harmonise too. Connected to internet to play an internet radio station. Wouldn't play. This happend sometimes and is a bugger. Restart usually fixes. Upon restart into omap1 again things were really unresponsive. widgets weren't staying where they should be, Weird stuff going on. Still working but being funny with me.. So, another restart into omap1. left for a minute before turniing on again. Same thing. Beginning to get late for work I rebooted into v47 and everything works ok. Still at work at the moment and working fine. Don't want to test omap1 incase it's still funny and restarting can wipe 1/4 of your battery sometimes. Will test when I get home. Could have been a temporary fit.
Has anyone else had any similar experiences? Also battery widget is off again on v47 today. Real battery level seems about normal I would say. I have cssu.
 |
| Tags |
| battery-status, bq27x00_battery, kernel, kernel-power, misiak4king, noobs-cant-read, pali4president, patches, readdirections, revolverspinyou |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 11:11.
- faster, snappier response
- battery life is worse (powertop reveals not much)
- 4 random reboots while browsing
- music library got corrupted ? trying to fix that now