yashsingh1/xdaforums huggingface dataset:
[LG Optimus Black] knzo:
edit:

Good effort. So, the quadrant is simulating the moderate-heavy usage.

Not sure if that works, like I said before, it's not only the lock on max frequency that matters but also the scaling.

Even then, I'm disappointed to know the difference is only 3 joules. That's it? One more reason to drop UV. Negligible effects.

The thing is that

our CPU is already undervolted with smartreflex

, that's the whole point of it. So, why tamper even more with it? My position in this is clear, I'll allow UV support for next versions but it won't be enabled by default nor will I recommend it.
[LG Optimus Black] Huexxx:
To support OC is linked to support UV... The difference in consumption is really negligible, but goes into the good direction.

Maybe the UV isn't the real concern... the real concern is the fact that nowadays (with Froyo) calibrated voltages are fixed to the stock frequencies, so incrementing the max frequency while voltage is automatically mantained by smartreflex is the same that make certain UV, isn't it?

Then, the goal IMHO for gingerbread is to get the optimal voltages to arbitrary frequencies. Let's see how Class 3 perform.

To finish, I've detected that sometimes one or two of the voltages aren't well calibrated at startup, and with auv the four voltajes are well calibrated. This simply is a result of two additional recalibrations made by my script. It's possible to do this without UV, but in my personal case I prefer to UV.

Regards!
[LG Optimus Black] redy2006:
Wait, your max freq was 900 MHz and not 1.1 GHz?

Hmm, perhaps I can't do such like that (light usage) because I need to be connected to the internet..
[LG Optimus Black] Huexxx:
Believe me when I say that for light use 900 or 1100 is the same because the most part of the time the phone is at min freq with InteractiveX.

With 2g and allways connected it seems to perform well too, another history is with wifi conected, or 3g.

Of course, the most energy demanding device is the screen... with big difference. Then, people who have the screen on a lot will drain the battery very fast.
[LG Optimus Black] Huexxx:
I've updated first post with new mod version 1.3.

Now you can set the UV depth. This allows to try a more agressive UV or set it to 0 and simply ensure you get the minimum recommended voltage without UV avoiding lazy calibrating OBs.

Regards.
[LG Optimus Black] redy2006:
Then we moved here.. :)

okay, running again your script:

$ export PATH=/data/local/bin:$PATH
$ su
# uv
Current frequency values: 1100 800 500 300
Current nominal values: 52 41 31 20
Current calibrated values: 52 40 32 20
Recalibrating...
Current calibrated values: 52 42 32 22
Calibrating optimized values...
New calibrated values: 52 42 31 19
Try to recalibrate? [y/n]: n
# cat /data/nova/auto/auvlog
Current frequency values: 1100 800 500 300
Current calibrated values: 52 42 32 21
Current recalibrated values: 52 42 32 22
Auto UV Depth: 1
New calibrated values: 52 41 31 20
#

And it seems difference than my first result:

Current frequency values: 1100 800 500 300
Current calibrated values: 53 43 32 23
Current recalibrated values: 53 43 32 23
Auto UV Depth: 1
New calibrated values: 53 42 31 22

My I ask how it happen? I just running once the 'uv' script.. while aprold tried it several times and get the same result..
[LG Optimus Black] Huexxx:
Well...

- UV script (not AUV) is intended to simply run UV once but goes independent of AUV. UV applies allways a depth of 1. And you are not just running UV once. If auvlog exists is because you have auvlog enabled.

- Looking at your first output, you try to UV once with AUV activated, then you are trying to UV two times, one at startup and once later.

- Looking the results of auvlog (that logs what happens at startup) your initial calibrated values are 52 42 32 21, your recalibrated values are 52 42 32 22, and then auv script has pushed the min values minus one (except for max freq becuase is greater than 1GHz) 52 41 31 20 and the final result are 52 41 31 20. Fine!

- Then, after boot, you have tried to run UV once but the values already lowered by auv. Already calibrated values are 52 41 31 20 (the same values obtained at boot looking at auvlog). After a recalibration the values are worse 52 42 32 22. UV takes the minimum values from both calibrations and decrements them one unit except for max freq in order to push it: 52 40 30 19. The result is 52 42 31 19, and show that at this moment smartreflex only gets the intended value for 1st and 4th freqs, but fails at intermediate freqs getting only 42(40) and 31(30). To recalibrate is not foolproofs and sometimes fail, is allways better to try it al boot, then better play with auv.

- At your first result, making the same deduction, is running fine. To say that this time smartreflex has been less optimistic with all voltages except for 3rd value.

Take into account the following: every boot your system will get different voltage values (apart from AUV). AUV will take this values and will try to decrement it (if depth is greater than 0) or will try to set it the lowest recommended possible (if depth is equal to 0).

Have you understand how it works?

Regards!
[LG Optimus Black] redy2006:
Wow, thanks for detailed explanation, great.. ;)

I've used your v1.2 script already with AUV enabled. Today v1.3 released, I upgrade it... after reboot and check /data/nova/auto/auvlog as instructed on your reply on aprold's thread, then I posted the result there.. and later after read your next post, I tried to running 'uv' (not via 'nova') just to look around, then I posted it here..

Question, while I won't reboot it, which values I had now?

The values at auvlog (52 41 31 20) or 'uv' (52 42 31 19).

Or perhaps I should check via /proc/overclock/mpu_opps?

ADDED

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=52 sr_adjust_vsel=51
mpu_opps[3] rate=700000000 opp_id=3 vsel=40 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=31 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=19 sr_adjust_vsel=22

Thanks.
[LG Optimus Black] Huexxx:
The values should be the result of UV script because it had been launched after auv. Then, it should be 52 42 31 19, and them should be the same that mpu_opps output... but they aren't .... :confused:

Seems like your system have recalibrated by itself and the results are worse this time...

Looking at my own config, is not the same case as yours... In my case at mpu_opps I have the same values that inside auvlog, vsel and calibrated.

I will periodically look at mpu_opps to see if it changes.

In your case, maybe you can reboot too and check if the values ​​match. To try 2 unit UV best set depth to 2 and reboot without launch 'uv once' after.

Un saludo.
[LG Optimus Black] redy2006:
OK as your suggestion, UV best set depth to 2 (and without 'uv').

Reboot, waiting ± 15 minutes, and InteractiveX already sets, and here it goes...

# cat /data/nova/auto/auvlog
Current frequency values: 1100 800 500 300
Current calibrated values: 53 43 32 23
Current recalibrated values: 53 43 32 23
Auto UV Depth: 2
New calibrated values: 52 41 30 21

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=52 sr_adjust_vsel=51
mpu_opps[3] rate=700000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=30 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=22

Still worse? :confused:

For additional info: BPO/SBT disabled.
[LG Optimus Black] Huexxx:
Why freqs at auvlog are 1100, 800, 500, 300 while at mpu_opps are 1100, 700, 500 and 300?

Let me take a look at this... do you have setCPU installed?

---------- Post added at 07:52 PM ---------- Previous post was at 07:25 PM ----------

I can't understand why your 2nf frequency has changed... auv allways takes the frequencies inside mpu_opps and set the same freqs...

Please, If you want, you would flash this... Now the output of auvlog is more detailed.

Then, once flashed, reboot, run nova script and set again your OC (simple, preset or custom, is the same), set again UV depth to 2 and check that AUV is enabled on boot.

Then, reboot and just after boot look at /data/nova/auto/auvlog and at /proc/overclock/mpu_opps. Doesn't mind if governor is not set yet, is independent from clocking.

Wait a while and then look again at /proc/overclock/mpu_opps.

Post here all the info and let's see what's happening.

Regards and thanks!
[LG Optimus Black] redy2006:
What?!! Oops, mistaken... No SetCPU, as I just copy paste from reply-posted and change the value, but it seems I'm not reading my 'copy-paste' that those freq are 700 :D:p apologize.. :o but those value are really mine, taken from output cat via terminal...

[DELETED, EDIT POST ENTRY]

With your v1.4

[SIZE="2"]# cat /data/nova/auto/auvlog
Current frequency values: 1100 800 500 300
Current nominal values: 64 52 40 32
Current calibrated values: 53 43 33 23
Current recalibrated values: 53 43 33 23
Auto UV Depth: 2
New frequency values: 1100 800 500 300
New nominal values: 53 41 31 21
New calibrated values: 53 41 31 21

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=51
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=31 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=22[/SIZE]

What about now? :o
[LG Optimus Black] Huexxx:
The frequencies issue was too rare to be true...

Please, make all the changes I've posted before: flash, re-OC, set depth, reboot, take data, wait a while and re-take data.

Regards and thanks!
[LG Optimus Black] redy2006:
Huexxx, I'm already posted above... but your quoted reply was before it..

Thanks.

ADD: re-take data: still the same as above...

[SIZE="2"]# cat /data/nova/auto/auvlog
Current frequency values: 1100 800 500 300
Current nominal values: 64 52 40 32
Current calibrated values: 53 43 33 23
Current recalibrated values: 53 43 33 23
Auto UV Depth: 2
New frequency values: 1100 800 500 300
New nominal values: 53 41 31 21
New calibrated values: 53 41 31 21

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=51
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=31 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=22[/SIZE]

ADD: Reboot again.

[SIZE="2"]# cat /data/nova/auto/auvlog
Current frequency values: 1100 800 500 300
Current nominal values: 64 52 40 32
Current calibrated values: 53 [U]52[/U] 33 23
Current recalibrated values: 53 43 32 23
Auto UV Depth: 2
New frequency values: 1100 800 500 300
New nominal values: 53 41 [U]30[/U] 21
New calibrated values: 53 41 [U]30[/U] 21

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=[U]52[/U]
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=[U]30[/U] sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=22[/SIZE]

changes at UNDERLINED.
[LG Optimus Black] Huexxx:
Well, I hope the new auvlog will be more user-friendly...

Your final values are good, but you are experimenting something abnormal...

The 'New' results at auvlog are the extracted data from mpu_opps just after the last recalibration.

From it we can infer that you are getting as calibrated values the same you are pushing, that's good... and looking into mpu_opps the nominal values (vsel) are correct acording to auvlog (53 41 31 21) but the calibrated ones are different!!!!

There are only two explanations to this issue:

- Your OB makes another recalibration at certain moment after auv script. This option doesn't seem to be a good explanation since my OB have the same ROM and the same script.

- Your mpu_opps is 'lazy' and takes a lot of time in get updated... then the info at auvlog is not updated and later takes the values that we can see at your mpu_opps....

Let me see it...
[LG Optimus Black] redy2006:
Rebooted, then left away to watch Benfica vs MU :p and check it out right now.

[SIZE="2"]# cat /data/nova/auto/auvlog
Current frequency values: 1100 800 500 300
Current nominal values: 64 52 40 32
Current calibrated values: 53 43 33 23
Current recalibrated values: 53 43 33 23
Auto UV Depth: 2
New frequency values: 1100 800 500 300
New nominal values: 53 41 31 21
New calibrated values: 53 41 31 21

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=52
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=31 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=22
[/SIZE]

What's the meaning of 'lazy' mpu_opps?
[LG Optimus Black] Huexxx:
With 'lazy' mpu_opps I mean that the changes aren't inmediatly refreshed on it...

Please, try with this, put it into /system/xbin, overwrite the existing one and set the same permissions that nova 0755 (rwxr-xr-x). Then reboot and wait at least 10 minutes.

After that, paste here auvlog and mpu_opps again.

Let's see what's happening!
[LG Optimus Black] redy2006:
Injecting your script...

# cat /data/nova/auto/auvlog
mpu_opps[4] rate=1100000000 opp_id=4 vsel=64 sr_adjust_vsel=53
mpu_opps[3] rate=800000000 opp_id=3 vsel=52 sr_adjust_vsel=52
mpu_opps[2] rate=500000000 opp_id=2 vsel=40 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=32 sr_adjust_vsel=23

Current frequency values: 1100 800 500 300
Current nominal values: 64 52 40 32
Current calibrated values: 53 52 32 23

mpu_opps[4] rate=1100000000 opp_id=4 vsel=64 sr_adjust_vsel=53
mpu_opps[3] rate=800000000 opp_id=3 vsel=52 sr_adjust_vsel=43
mpu_opps[2] rate=500000000 opp_id=2 vsel=40 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=32 sr_adjust_vsel=23

Current recalibrated values: 53 43 32 23
Auto UV Depth: 2

mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=53
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=41
mpu_opps[2] rate=500000000 opp_id=2 vsel=30 sr_adjust_vsel=30
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=21

New frequency values: 1100 800 500 300
New nominal values: 53 41 30 21
New calibrated values: 53 41 30 21

mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=52
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=30 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=21

mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=52
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=30 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=21

mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=52
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=30 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=21

# cat /proc/overclock/mpu_opps
mpu_opps[4] rate=1100000000 opp_id=4 vsel=53 sr_adjust_vsel=52
mpu_opps[3] rate=800000000 opp_id=3 vsel=41 sr_adjust_vsel=42
mpu_opps[2] rate=500000000 opp_id=2 vsel=30 sr_adjust_vsel=32
mpu_opps[1] rate=300000000 opp_id=1 vsel=21 sr_adjust_vsel=21

It looks that auvlog had more detailed...
[LG Optimus Black] Huexxx:
Well, like I suspected, your mpu_opps is 'lazy' showing the new calibrated voltages...

Let me explain myself:

- The new script shows the values and mpu_opps in order to detect if there are problems extracting the parameters. Everything is fine, discarded issue.

- Looking at auvlog...

-- first values and after recalibrating ones are running fine. In this particular case, look at first values of 2th freq calibrated voltage: 52, same value that vsel... this voltage is bad calibrated at boot by itself... or maybe it will be good calibrated but after a while.

-- once injected the new values (after Auto UV Depth: 2), look at mpu_opps... vsel values and calibrated ones are the same... this is normal with my OB, but in your case seems that the values are not updated yet... the following mpu_opps is launched after 60 seconds, and this new values remain unchanged in the following mpu_opps... these are the REAL values applied to your system...

In order to definitely check the behaviour and modify the script to run flawlessly, try with this... like before, inject it, change permissions and reboot...

Thanks and so sorry for the tests!

---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------

Another thing...

Once downloaded new auv, injected and running, please repeat the process two times and paste both results.

You have to wait at least 2 minutes before see inside auvlog. No need to post mpu_opps, it's already inside auvlog.

Regards!
[LG Optimus Black] Huexxx:
Ok!

- In the first run:

-- At boot, 2nd voltage seems too high, and doesn't seem to change.

-- At recalibration, 3rd voltage becomes stable after 5s, and 2nd voltage becomes stable after 10s ... that's what I mean with lazy...

-- At new value pushing, 4th value becomes stable after 5s, and 3rd value becomes stable after 10s.

-- With your 2 unit depth, you finally get 52, 42, 32, 22 when at boot the values were 53, 52, 33, 23. Apart from 2nd value that seems to be misscalibrated at boot, you only archieve a unitary decrement at all voltages.

- At second run, the things change!

-- At boot, all voltages seems well calibrated.

-- At recalibration, all the voltages seems well calibrated from the begining.

-- At new value pushing, all the voltages become stable after 5s.

-- With your 2 unit depth again, this time you finally get 52, 42, 32, 22 again, when at boot the values were 53, 43, 33, 23. Again you only archieve a unitary decrement at all voltages.

I'll recommend to set only a unitary depth.

What you gain from using my script? To avoid a 2nd freq excesive voltage (frist run), and a slightly decrement on voltage applied. Is not a exagerated advantage, but if everything run fine... Why not apply it and avoid miscalibrated voltages?

With all this info I'm goint to reprogram v1.4. I'm goint to introduce adaptative waitings in order to wait to a stablished values before continue...

Regards and thanks!
[LG Optimus Black] Huexxx:
I've updated the first post with new 1.4 version.

Thanks redy2006!
[LG Optimus Black] redy2006:
Okay, another test-drive with your official v1.4 script..

Reboot recovery, flashing, and reboot again...........

Then I change UV depth = 2, although it said that Recomended value: 1

Reboot again, and waiting again for ± 5 minutes, and here's the result...

Fri Sep 16 19:01:47 WIT 2011

Frequency values at boot: 1100 800 500 300
Nominal values at boot: 64 52 40 32
Calibrated values al boot: 53 43 40 23
Current recalibrated values: 53 43 32 23
Auto UV Depth: 2
New nominal values: 53 41 30 21
New calibrated values: 52 42 32 22

So now, what does between UV depth = 2 or 1 (your recommended value)?

Thanks.
[LG Optimus Black] Huexxx:
Well, this seems to be running well right now!

Let's analyze the data.

- Looking at calibrated values at boot, the 3rd voltage seems to be so high. If not running my script, maybe this value will remain up with the consecuent extra battery waste.

- Looking at Current Recalibrated Values, 3rd value seems to be well calibrated.

- New nominal values are minimal less 2 (your depth) except for 1st freq ('cause is greater than 1GHz).

- Looking at New Calibrated values, it looks like your OB can't drop the values 2 units... pushing 53 41 30 21 you actually get 52 42 32 22. Why mantain depth to 2 if your OB can't decremet 2 units? Maybe is better to stuck at depth=1.

Conclusion: With my script, you have reduced 1st, 2nd and 4th values in one unit while 3rd stucks at the same value. Also you get 3rd value well calibrated... it seems to stuck at 40...

Regards and thank for your help!
[LG Optimus Black] redy2006:
Last test-drive

Okay this will be my last test-drive :)

I was "downgrade" the overclock, I use stock freq...

Fri Sep 16 20:32:57 WIT 2011

Frequency values at boot: 1000 800 600 300
Nominal values at boot: 60 52 44 32
Calibrated values al boot: 53 43 33 23
Current recalibrated values: 53 43 33 23
Auto UV Depth: 2
New nominal values: 51 41 31 21
New calibrated values: 51 42 32 22

Well it seems I still have same final value.. :eek:

Okay then, it's enough for now, I'll just stick with it.. and waiting for the next Gingerbread :D

Question, does Gingerbread OB (cm7/miui/or else) had it's own calibrated voltage? or perhaps you would still maintain such as this script to calibrate?

Thanks.
[LG Optimus Black] Huexxx:
As i said before don't know where, calibrated voltages are linked by default to stock freqs whatever freqs we set. Good result. In my case with 900, 700, 500, 300 all goes smooth IMHO.

Let's see how performs Smart

Reflex Class 3, hopefully there will be no need to tweak any... or maybe will be.

:)
[LG Optimus Black] Diabu:
How i enter in the recovery if my phone don't boot at the start? :(
[LG Optimus Black] Huexxx:
Why don't boot? At which point stucks at boot?

Maybe you need to reflash nova.

Try to enter recovery pushing several times a hardware button just after power on. I'd goes bad, reflash with kdzu.
[LG Optimus Black] Huexxx:
I've just remembered your case... you should access recovery repeatedly pushing a hardware key.
[LG Optimus Black] naeem86:
can i use this mod on nova v6.1?xD sorry for noob question!:$
[LG Optimus Black] Huexxx:
I don't know and I'm not going to think if is completely possible without problems... If I were you I don't do that!

Update to v8 if you want to try my stuff.

Sorry and regards!
[LG Optimus Black] wiqi546:
Mr. Huexxx i wana ask you a quick question.

I saw your battery stats (5days+) and i must say em totally surprised by them :D . Because mine last less than a day :( . I am thinking about flashing your script. Right now i am on Nova V8 (or whatever is the latest one). Plz tell me how much was your brightness when u got that 5days of battery backup.

Regards! and thanks. :)

PS: Yes i am on a 2G only network and mobile data is always turned off. Sometimes i turn on wifi. I have read this complete thread and found a reference to setCPU. Yes i have installed it (but haven't changed anything, i sometimes use it for monitoring 'time in state'). Should i uninstall it or...?
[LG Optimus Black] Huexxx:
Hi!

The mention to setCPU wa trying to find where was a specific problem... you can have setCPU installed but IMHO is useless because you can set everything within nova script.

I had brightness in auto for the battery marathon.

Right now I'm trying with 2G, data allways on and moderate use, and it seems to last about 4 days.

Regards!
[LG Optimus Black] sonic997:
Hi, Huexxx, are u still there?

I am a newbie and jsut flashed with the nova v8, do you mean that flashing with the Huexxx v8 can help with the battery?

OC for changing the CPU speed will burn the motherboard?

Thanks
[LG Optimus Black] Huexxx:
You can install my stuff in order to modify the stock 'nova' script.

With this, you gain the possibility to activate the auv feature to try to safely lower the voltage applied to the CPU.

In my case, I use 900, 700, 500 and 300 freqs instead 1000, 800, 500 and 300, so I'm doing UC (underclocking) and that won't harm your device.

If your are planing to OverClock (I think isn't necessary), stucking fax freq at 1100 I think that you aren't going to burn your motherboard ejeje

Regards.
[LG Optimus Black] sonic997:
when i update the quasar v8 source .zip, it says

Finding update

Opening update

Installing update

Installation aborted

what's going on?

Do I need to reflash nova? I dont want to start from zero again.

Thanks
[LG Optimus Black] Huexxx:
You DON'T have to install quasar kernel... it already is inside Nova v8.

It seems to fail at install... Does your OB run well? Then you don't have to do anything.

Regards.
[LG Optimus Black] sonic997:
i use 8 hours standby for 2G network to estimate the overall battery life.

It is estimated that the battery can last for 40 hours for 2G network without any other usage like calls, SMS, etc.

I think it is not normal and I think it is a must to flash the files...

what should i do?