PDA

View Full Version : True 4>7 network & battery bars!



Pages : 1 [2]

spark001uk
06-03-2004, 11:52 PM
@ Belabs:

Two questions:
Firstly, i know it appears to work (i'm trying it now), but is it ok to put table 1 values into table 4, shouldn't it have its own values ?

Secondly, why is this problem only occuring with the battery bars and not with the net strength bars also ?

thx
Mark.

belabs
08-03-2004, 08:04 PM
"is it ok to put table 1 values into table 4, shouldn't it have its own values ?"

yes it should have... if you want an accurate meter display.
copying from the other 7 steps table is just used for testing

anyway... i modified yak's script
try this and see if Ur bars will still skip
good luck!

spark001uk
08-03-2004, 09:53 PM
Tried it. Works, but it says it cant find tables 4,5,6, but it finds table 7.

Also just out of interest, how come when only 3 tables are altered we get the 5 > 1 problem, yet if 4 tables are altered it works fine ? Why don't all 7 tables need to be done ??

belabs
08-03-2004, 10:17 PM
Tried it. Works, but it says it cant find tables 4,5,6, but it finds table 7.


its normal...

observe Ur phone and see if the 7 bars works fine....

spark001uk
08-03-2004, 10:31 PM
Ye works ok, after it changes tabs 1,2,3,7. But then again, it worked with the previous procedure of changing 1,2,3, and 4 (using tab 1 vals in tab 4). I watched it all the way from full to dead, and didn't notice anything abnormal !
And just to make things even more confusing for me, 3310 script changes tables 1,2,3,4 and 5. Yet still doesnt work properly !! <tears a bit more hair out> :-x

NokDoc
08-03-2004, 11:07 PM
Mr. Spark001,

The 7-6-5-1 is a problem due to the battery type, my 3310 has it too with the NiMh battery.

However with the same phone and flash, it does quite ok with my 8210 LiIon battery.

Btw, Mr. Belabs, nice job.

NokDoc

spark001uk
08-03-2004, 11:23 PM
So wot has belabs' alteration done then ? <confused> :)

NokDoc
08-03-2004, 11:51 PM
Hi,

Well, as far as I understood, he noticed a thing that was missed in the original gsc script by Mr. Yak.

NokDoc

spark001uk
09-03-2004, 12:22 AM
Yes i understand, but dint u say it was a battery problem not a script problem ? PS i have same phones and batts as u, but still get the problem. :-?

Also i can't understand why 5210/8210 has 4 tables, and 3310 has 5 ?

kraze1984
09-03-2004, 11:26 PM
Do u have a NiMH or a LiIon battery?
I'll check your solution and maybe try to modify yak's gsc. Maybe there's some wrong mask in it...

So many maybe's :)

At first glance it seems that yak's patch replaces all the battery conversion tables in 3310. :( I checked it two times...

spark001uk
10-03-2004, 02:47 AM
Kraze,
With u there mate, but could u help us lesser intellects understand it a bit better ? What is contained in each table, a formula for something ? Ive looked at the appropriate sections in hex, and i see in 3310 there are five lines of these tables. And only four lines in 8210/5210 ? Why is this ? Would just like to know in more detail so as i can get a better understanding of how it works?
thanks mate
Mark

kraze1984
11-03-2004, 12:55 AM
Did you read this threed since the beginning?
It's all already explained... At least for me it is clear.
The conversion stirngs (BarConversionTable)we are talking about, are the voltage values at which a bar, showing battery status is disappearing from the screen.
If we take a 3210 flash (modified) with this string:
0B1B 0AB7 0A53 09EF 098B 0927 0927 0927
0B1Bh=2843 at this value disappears the top bar (7th)
0AB7 at this value disappears the 6th bar
0A53 at this value disappears the 5th bar
09EF at this value disappears the 4th bar
098B at this value disappears the 3th bar
0927 at this value disappears the 2nd bar
0927,0927,0927 - the first bar cannot disappear, and there are 2 values in reserve

see example here:
http://nokiafree.org/forums/attachment.php?attachmentid=10081


Why there are different quantity of those strings?
IMHO, they are for batteries with which the fone can work, or batteries that were released by NOKIA at the moment of appearence of the fone on the market.

Hope, its clear now

kraze1984
11-03-2004, 01:00 AM
btw, tried my mate's li-ion 3.7 V battery from DCT-4 Nokia fone on a 3310 and it worked :) And the 7bars were showing correctly :)

spark001uk
11-03-2004, 03:00 AM
Yes mate, thanks for that, very informative. i didn't realise each string was for a different battery type. So surely with 3310 bars going 5 -> 1 there must be some incorrect values ? Or is there another reason for this ?
thanks
mark

tangcla
15-03-2004, 07:23 AM
NokDoc, link not working... :(

Does anyone else have it that can host it? :)

tangcla
15-03-2004, 07:52 AM
Nevermind about above post, found the script :D

Next question is, what are the threshholds for each of the seven bars of reception? Seems like at 84dBm, it is still on 4 bars (out of 7). Only when you get insanely good reception, ie. standing right next to the base station with -30dBm will it get to full reception as such :p

NokDoc
15-03-2004, 11:28 PM
Nevermind about above post, found the script :D

Next question is, what are the threshholds for each of the seven bars of reception? Seems like at 84dBm, it is still on 4 bars (out of 7). Only when you get insanely good reception, ie. standing right next to the base station with -30dBm will it get to full reception as such :p

Hi,

In the manual files:

9C A2 A7 AC 00 00 00 00 > 9C A2 A8 AE B4 BA C0 00

100-9C= -100dB org min
100-AC= -84dB org max
100-C0= -64dB new max

NokDoc

tangcla
16-03-2004, 12:27 AM
Hi,

In the manual files:

9C A2 A7 AC 00 00 00 00 > 9C A2 A8 AE B4 BA C0 00

100-9C= -100dB org min
100-AC= -84dB org max
100-C0= -64dB new max

NokDoc
Hi NokDoc,
I don't know how the g3n0lite scripts work :D what do I do with that? :lol:

kraze1984
17-03-2004, 07:15 PM
i don't know wether it works only for my fone (3310 v6.07) but it seemz that i've solved the 7>6>5>1 bug.

After each voltage string i.e.:
0F0E 0EE3 0EB8 0E8D 0E62 0E37 0E37 0E37
there are four bytes. after some strings they are 0000 (1st, 2nd, 4th), after some they are 6400 (3rd, 5th).
64h = 100 (100% ?).
I changed all the 0000 to 6400, and now, even after 2nd recharge it seems to work. at least i've seen 7,6,5,4,3,1 bars.

P.S.
>EDIT The max voltage i observed on a standart NiMH batt was 4500 mV

yak
17-03-2004, 08:30 PM
Hi there!

As you all can see, I haven't worked too much on my patches recently (including true7bars). This is the case beacause I'm experiencing some big changes in my life (moving to another country, learning new language :)). But in free time I work on my new Nokia reversing project - NokiX. Everything I can say now is that I'm trying to replace G3n0lite with this program. It will be a so-called "script based firmware modder for Nokia DCT-3 phones". All patches will be implemented by external scripts. The script language will be based on REXX language so it will be much more powerfull than GSC. Currently the program is quite ready but I still have to write the scripts.

Some standard things are already made (kill_mcu_chek, kill_flashcheck_faid, 5e0_table support, menustructure support). Additional there is a script to increase the number of templates in 3310 (so you can use them as notes).

I see that you've made some researches on making true 7 bars. I will try to implement new findings in script for NokiX.

There will be no more GSC scripts made by me.

kraze1984
18-03-2004, 01:14 PM
Interesting... As g3gg0 no more continues g3n0lite...
It's a good continuation!

will this program support .gsc patches?
will you import the functions already available with g3n0lite?

Crux
18-03-2004, 04:03 PM
cool :)

very cool indeed :)

hud_nash
18-03-2004, 08:48 PM
wow,

cant wait to see your work sir

spark001uk
19-03-2004, 12:23 AM
i don't know wether it works only for my fone (3310 v6.07) but it seemz that i've solved the 7>6>5>1 bug.

After each voltage string i.e.:
0F0E 0EE3 0EB8 0E8D 0E62 0E37 0E37 0E37
there are four bytes. after some strings they are 0000 (1st, 2nd, 4th), after some they are 6400 (3rd, 5th).
64h = 100 (100% ?).
I changed all the 0000 to 6400, and now, even after 2nd recharge it seems to work. at least i've seen 7,6,5,4,3,1 bars.

P.S.
The max voltage i observed on a standart NiMH batt was 4494 mV

I tried this on mine, also 6.07. Unfortunately result was no different. :sad:

kraze1984
19-03-2004, 06:40 PM
did you change the 0000 after each voltage table? After the first especially.
And what battery type do you have?
Mine is BMC-3.

I can't promise nothing, but i'll try to change the .gsc to make it automatic.

grreetz

yak
22-03-2004, 12:25 AM
@ kraze1984

No, it won't support gsc scripts (there are not so many of them so they can be rewritten - it's easier then adding gsc support :)).

There will be no built-in patches - everything will be implemented through scripts. I have just downloaded g3n0lite 2.0 sources and I plan to rewrite most of its built-in patches (Fade LEDs, Rhytmic backlight, Slideshows and others) to NokiX scripts. I also plan to make them more friendly, for example you will be able to give some kind of 'slideshow descripting file' during patching so there will be no need to use other tools to edit the slide. And everything with just one click :)).

n0rbi_666
22-03-2004, 02:32 PM
@yak, will NokiX support 3210 ? :)

yak
23-03-2004, 05:15 PM
@ n0rbi

NokiX itself provides only an environment for scripts. The scripts are written in REXX language, NokiX only adds some usefull flash modyfying commands to the REXX language. So itself, NokiX doesn't support any model. The main thing are the scripts. The scripts written based on G3n0lite's patches will mostly work in simillar way as they did in G3n0 - so, still, no fade leds on 3210. But since they are kind of 'open source', maybe someone (me? ;) will fix them in the later time to work with larger family of phones. We'll see...

kraze1984
24-03-2004, 01:12 AM
Pls try this script and test if it corrects the NiMH bug:
Its a 0.8 by belabs modified with 6400's found by me.
(see upper posts).

spark001uk
24-03-2004, 02:35 AM
@kraze

Hi, tried changing to 6400 on each batt string, and also just to be sure i tried it again using the gsc u made, just to make sure. No difference i'm afraid. BMC-3 is my batt.

kraze1984
24-03-2004, 03:11 PM
@kraze

Hi, tried changing to 6400 on each batt string, and also just to be sure i tried it again using the gsc u made, just to make sure. No difference i'm afraid. BMC-3 is my batt.

strange...
I noticed only that the 7th bar in normal mode (no switching to MADos) was visible for 24 hours or so, the 6th bar - for about 6h, 5th - about 6h, 4th - about 2h hours, 3,2 - together about 2 h, 1st- about 1 h.

Maybe you drained the battery too fast and didn't notice ?
Where there any modifications in your flash except the 7bar? Cause i had a lot of them.

grreetz

spark001uk
24-03-2004, 10:46 PM
Ok just modded a plain 6.07 flash with only your gsc. Will post again when i know how it goes. By the way did u realise u have used the gsc designed for phones with two navkeys (8210 etc) ?

kraze1984
24-03-2004, 11:33 PM
Ok just modded a plain 6.07 flash with only your gsc. Will post again when i know how it goes. By the way did u realise u have used the gsc designed for phones with two navkeys (8210 etc) ?

No, i didn't. But the patches are different only in the situation and size of bars. So, if this one works, i could modify also other patches, if not (i hope not!) no need to upload junk to forum....

grrreeetz

kraze1984
28-03-2004, 12:15 AM
Anyone else tested the .gsc, i've posted?

Waiting for constructive replies :)

tangcla
28-03-2004, 01:44 AM
Anyone else tested the .gsc, i've posted?

Waiting for constructive replies :)
Sorry, I'm not too technical here, so I don't know about the programming of the GSC file. All I'm after is a GSC file that has the reception threshholds fixed up (so >-84dBm is 7 bars of battery reception :D) and that the battery bars don't go all funny - I had 0 battery bars in a call, getting 'battery low' messages, and after the call I had 5 bars :)

I'll give you 0.9 GSC a try when I get home :)

tangcla
28-03-2004, 03:31 PM
Anyone else tested the .gsc, i've posted?

Waiting for constructive replies :)
I'm running your GSC script now - ummm, that technical stuff went way over my head, so what's the difference I should be looking out for?

When the battery still has 3.6 volts, it says battery empty, and it still only shows 4/7 reception bars at -84dBm... that's all I'm after ;)

spark001uk
28-03-2004, 06:10 PM
@kraze

tested twice now, with gsc. Doesnt work, still goes from 5 > 1

mark

belabs
30-03-2004, 11:50 AM
@kraze

tested twice now, with gsc. Doesnt work, still goes from 5 > 1

mark
sometimes, things are just different

do some troubleshooting... im also wondering why does the bars still skip even changing all the BarConvTab on 3310, the update i made on the yak's gsc was for the other units, not for 3310. i also dont have a 3310 so here's something you can do for Urself

maybe U should identify first which (or if theres any) of the 5 bar conversion tables in your fls Ur batt is using. (ex. change the values of BarConvTab1 to show only 1 bar even in a full charge batt, 5 bars for the BarConvTab2...etc.)

if u find it
then concentrate on that table, maybe U should first aim to make the 4th, 3rd & 2nd bar to appear, and from that figure out what will U do next.

read infos about the tables from the earlier posts

good luck!

kraze1984
06-04-2004, 02:56 PM
yup, its strange... All those voltage values...
For some phones they give effect, for some - not...

That's why by now flash modifiying is still manual (and brain) work :)

tangcla
06-04-2004, 02:59 PM
Are there any new versions of the script available? :-P

NokDoc
06-04-2004, 06:04 PM
Hi guys,

Brainstorming and suggestions are very good.

It proves U guys are very interested in the background things.

But I'm afraid, this specific battery bug is not that simple to solve.

I noticed one quite odd thing:

We patch these 4 or 5 battery value records in the mcu.

Inside my eeprom are also two of these records.

After running a modified 7 bars flash, they are still the old, unpatched info.

When U change besides the mcu patch also these two lines eeprom into Ur new 7 bars style, it looks like it's working.

1D.03D2 Battery#01: (0C1C0D480C94012C012C002D 0F430EB70E690E690E690E690E690E69 00000585)
1D.03F2 Battery#02: (0C1C0DCA0C9E02580258002D 0F110E850E370E370E370E370E370E37 6400053F)

This is data from a 8210-531, with full operational 7 bars mcu patched.

Maybe we should have some closer look at the meaning of them in eeprom?

NokDoc

User32
06-04-2004, 10:30 PM
why are the values stored in eeprom?
eeprom is supposed to keep permanent settings; not values that keep changing.

kraze1984
07-04-2004, 04:49 PM
Hi guys,

Brainstorming and suggestions are very good.

It proves U guys are very interested in the background things.

But I'm afraid, this specific battery bug is not that simple to solve.

I noticed one quite odd thing:

We patch these 4 or 5 battery value records in the mcu.

Inside my eeprom are also two of these records.

After running a modified 7 bars flash, they are still the old, unpatched info.

When U change besides the mcu patch also these two lines eeprom into Ur new 7 bars style, it looks like it's working.

1D.03D2 Battery#01: (0C1C0D480C94012C012C002D 0F430EB70E690E690E690E690E690E69 00000585)
1D.03F2 Battery#02: (0C1C0DCA0C9E02580258002D 0F110E850E370E370E370E370E370E37 6400053F)

This is data from a 8210-531, with full operational 7 bars mcu patched.

Maybe we should have some closer look at the meaning of them in eeprom?

NokDoc

But sometimes it seems that the fone changes itself values in eeprom for battery. its only my opinion.

kraze1984
07-04-2004, 04:54 PM
why are the values stored in eeprom?
eeprom is supposed to keep permanent settings; not values that keep changing.

Those values do not change. They are stable and show when the battery indicator should act. That's why after some wrong unlocking the battery indicator can show bad values.

NokDoc
07-04-2004, 05:52 PM
Hi,

>> eeprom is supposed to keep permanent settings...

No, instead, its the opposite.

A copy of Ur essential ram data is stored into eeprom area, to make it able to keep Ur 'dynamical' values when the phone is set to off, and Ur ram data will get lost.

Ok, I can imagine the problem U have, while the name is too confusing bout this.

Electrical Erasable Programmable Read Only Memory.

So the EEP tell U that actually the ROM name is wrong.

Technically it is harder to write to eeprom as if it was into ram.

But functional this writing happens alot of times, every change U make is stored there.

Eg, Ur netmonitor state, Ur alert time etc...

I hope it's clear?

NokDoc

User32
08-04-2004, 04:23 PM
@NokDoc
>> I hope it's clear?
almost...

@kraze1984
didn't know such result after bad unlocking

set
15-04-2004, 09:18 AM
...so we have to patch eeprom data too... :rolleyes:

NokDoc
15-04-2004, 06:50 PM
...so we have to patch eeprom data too... :rolleyes:

Hi,

I don't think it's the solution, just a quick hack to notice the results.

I should say, we must know more about why those settings aren't updated by the patched mcu functions itself.

But I myself never found the functions that uses that eeprom part of these battery records.

Only the mcu stored parts, which we could edit into a 7 bars script.

NokDoc

set
16-04-2004, 04:49 AM
I'm still using one table value all throughout the min/max current/voltage tables.. havn't notice anything queer so far. Maybe those values are recalculated before they are stored in eeprom...(just a guess)... gez we have to dig deeper... :)

NokDoc
02-09-2004, 04:33 AM
Hi,

News bout those eeprom tables, in case people still work on that:

0C1C0D480C94012C012C002D0F430EB70E690E690E690E690E690E6900000585

The 0585 in the end is a checksum of the 1E bytes before.

NokDoc

tangcla
02-09-2004, 04:42 AM
I'm not geeky enough to understand hex stuff :(
so, how does this affect the scripts? Anyone going to make a new script for g3n0lite? :D

mudy1
29-09-2005, 08:19 PM
dear yak and other members
please i want the true 4>7 ..... for the 6110
i would be gratefull if u provide the instruction on how to make these tricks with my phone
plzz send at : [email protected]
thx alot m8s

tangcla
30-09-2005, 12:03 AM
dear yak and other members
please i want the true 4>7 ..... for the 6110
i would be gratefull if u provide the instruction on how to make these tricks with my phone
plzz send at : [email protected]
thx alot m8s
I'll email it to you now.

mudy1
02-10-2005, 10:11 PM
thx alot buddy
i really appreciate this