yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mcclain71:
Out of all the roms that I have tried for my Virgin Mobil Canada, only one would work with the camera. All the others give me the "cannot connect to camera" message. Any ideas why? All the roms I have tried are 4.4.2 based with the same gapps package. I am confused. lol. Thanks!
[Sprint Samsung Galaxy S III] REV3NT3CH:
Are you using the stock aosp camera or the google camera that comes with some certain gapps...google cam can cause this issue
[Sprint Samsung Galaxy S III] mcclain71:
I've tried the stock camera app that comes with the roms, and have even downloaded other camera apps from Google Play...all don't work. Thats the part that I don't get honestly. The only rom that works is LiteRom KK Update 4 (4.4.2 based). Thoughts? Lol
[Sprint Samsung Galaxy S III] REV3NT3CH:
It works for me and I'm on a 4.4.4 ROM I built for s3 (personal build)...what gapps are you flashing...that may be flashing camera stuff not meant for what your trying to do
[Sprint Samsung Galaxy S III] mcclain71:
I originally flashed 4.4.2 gapps, with a 4.4.2 rom. i just flashed a 4.4.4 rom and flashed a 4.4.4 gapps. Still no luck. I even unistalled the torch app (was one of the remedies I searched for) and cleared the camera cache too.

Funny thing is...I thought I was on the XDA site for ATT/Rogers/Bell/Telus, until I just looked a second ago :/ Needless to say, yes...i did flash the correct rom for my phone. Lol
[Sprint Samsung Galaxy S III] REV3NT3CH:
Please give me a link to the gapps you are using....can't help if I don't know what your flashing
[Sprint Samsung Galaxy S III] mcclain71:
Here's the link. Thanks!

http://xdaforums.com/showthread.php?t=2397942
[Sprint Samsung Galaxy S III] REV3NT3CH:
Pa gapps is your issue....it replaces aosp camera with google camera ...banks does the same thing...let me dig u up a proper link
[Sprint Samsung Galaxy S III] mcclain71:
I just flashed the 4.4.4 camera module, and no luck :/ maybe I wasn't meant to have a camera
[Sprint Samsung Galaxy S III] mcclain71:
Thanks...I appreciate it :)
[Sprint Samsung Galaxy S III] REV3NT3CH:
http://goo.im/gapps/gapps-kk-20140606-signed.zip

these ive used for 4.4.4 based roms

http://goo.im/gapps/gapps-kk-20140105-signed.zip

use these for 4.4.2 based
[Sprint Samsung Galaxy S III] mcclain71:
Thanks for the links... but those don't work either. I've tried 10 roms last night with various gaps, and have only one work with the camera. Odd eh?
[Sprint Samsung Galaxy S III] Bart8i:
Have the same problem, without opening back, thinking I bought a developer's version with no camera? Have you looked inside?
[Sprint Samsung Galaxy S III] roirraW "edor" ehT:
Not a bad suggestion, but he said he has used only one ROM where the camera worked.

[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors

Charging still shot

n00b-xda-disciple's Wicked X Video review

Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
[Sprint Samsung Galaxy S III] Bart8i:
On mine I know the sim card reader is damaged by a bad sim card, perhaps he has damaged his LG between rom changes?
[Sprint Samsung Galaxy S III] Bart8i:
An afterthought, when you clean the kernel prior to writing a new rom, you probably wipe the existing address of the camera as well, so the new rom can't validate the camera, so it does not connect or give it power.
[Sprint Samsung Galaxy S III] Ainz_Ooal_Gown:
Have you tried PA Gapps?
[Sprint Samsung Galaxy S III] mcclain71:
I tried another ROM yesterday...Gummy (build date 6.29) and the camera works. I flashed the micro option from PAGapps and everything works, so I'm leaving it like that. Don't know why I was having so many issues, but Im content now. Thanks!
[Sprint Samsung Galaxy S III] Ainz_Ooal_Gown:
So you did try the PA Gapps or did gummy ROM just happen to be the only ROM that the camera worked for you no matter the Gapps package?
[Sprint Samsung Galaxy S III] mcclain71:
Gummy was the only ROM (out side of the original one I used) that worked with the camera... No matter what gapps package I used. I haven't seen anyone else with this issue on the forums, so I know its just me...but its still weird. Lol
[Sprint Samsung Galaxy S III] Ainz_Ooal_Gown:
Well thanks for sharing now if someone else has this problem......not necessarily that someone else will have this problem they can try gummy ROM and yes it is a weird problem
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
(A) For changing RAMDisk size:

Pl change the registry as follows:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 00 MB RAMDisk

"Size"=dword:00000000

"Address"=dword:98000000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 16 MB RAMDisk

"Size"=dword:00000000

"Address"=dword:97000000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 32 MB RAMDisk

"Size"=dword:02000000

"Address"=dword:96000000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 40 MB RAMDisk

"Size"=dword:02800000

"Address"=dword:95800000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 48 MB RAMDisk

"Size"=dword:03000000

"Address"=dword:95000000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 64 MB RAMDisk

"Size"=dword:04000000

"Address"=dword:94000000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk] --> 80 MB RAMDisk

"Size"=dword:05000000

"Address"=dword:93000000

Open the nk.nba using any hex-editor find the following byte sequence, or

Go To Address

0x004032e8

(0x0040c2e8for WM6 nk.nba),

Goto Address 0x00456250 for WM6.1

Goto Address 0x004562E8 for WM6.1 build 19209

and modify as follows:

FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 08 --> 128MB Program, Memory: RAMDisk= 0MB

FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 06 --> 96 MB program, memory: RAMdisk= 32MB

FF FF FF FF FF FF FF FF FF FF FF FF 00 00 80 05 --> 88 MB program, memory: RAMdisk= 40MB

FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 05 --> 80MB program, memory: RAMdisk= 48MB

FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 04 --> 64 MB program, memory: RAMdisk= 64MB

and the registry to the mentioned values above.

(B) Increasing Paging Pool for Hima WM5

1. Extract NK.nba

> xda2nbftool -x NK.nbf NK.nba 0×20040304

2. Open with a Hex Editor

3. Go To Address 0×00404650

(0x0040d650 for WM6 nk.nba),

Goto Address 0x004575B8 for WM6.1

Goto Address 0x00457650 for WM6.1 build 19209

Change it to look like

64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 50 00 --> 5MB PagePool(Default)

64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 00 01 --> 16MB PagePool

64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 80 01 --> 24MB PagePool

64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 00 02 --> 32MB PagePool

4. Update Image Check Sum

> xda2nbftool -c -u NK.nba

5. Repack as NK.nbf

> xda2nbftool -x NK.nba NK.nbf 0×20040304

6. Put in the same directory as HimaUpgradeUt.exe or HimaUpgradeUt_NoID.exe

7. Flash as you normally do.

With this you can achieve the desired RAMDisk size and pagepool size in any ROM

Hope you find the info useful. Enjoy changing....cheers....

EDIT(7.2.2007): To improve understanding added the info as suggested by @llbasha
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] double_ofour:
CoOL... Let me try..
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] rheza02:
where address of ram disk and program memory...?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] rheza02:
how about 48 page file and 96 mb for program memory ??

how ....?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
@rheza02

You must keep in mind that the total of pagepool+Program memory+RAMDisk must 128MB
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] rheza02:
thank you..

how to know size of page file...?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] panda2020:
Hello! c_shekhar

I still don't get it! I don't understand how to change the registry! I do find the registry file for ramdisk and I did change it according to your instruction. But I still don't understand the above "lines". What does it mean???

Help!!!

Panda2020
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
1. Open nk.nba with hex editor. search for the byte pattern corresponding to RAMDisk and pagepool size. Modify the byte according to your requirement. For example for pagepool look for 64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 and modify the next two bytes. Similarly for RAMDisk size.

2. change the registry in the folder \OEM\ROM_Himalaya_v1.50. It should be probably 0ffd60e6-162d-4643-850c-58fcc4e34579.rgu in your folder too. And cook.
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] dotfred:
Right, I will try to explain.

When you cook your Rom, you decide what will be the size of the RamDisk and the size of the page pool.

So first of all, you adapt the rgu file of the ramdisk to have the size you want for ramdisk then you go in the ROM directory where the nk.nba file is. You open it with an hex editor and you modify it in order to define the size of the page pool you desire. Then you cook your rom in order to have your final nk.nbf.

In my nk.nba RamDisk pattern is located at address : 0x004032e8

Hope it's clear

Cheers,

.Fred
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] bluecream4:
I do appriciate your efford for everybody ;) :)))

Thank you
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Cryingman:
How about for 20M Pagepool and 44 ramdisk?

Please tell me what hex number and registry volume?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] panda2020:
Thanks a lot! I already did it! But how can I know the cooked rom have such page pool size? Since the ramdisk size is shown (I cooked 32MB page pool and 32MB ramdisk)???

Panda2020
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
You are always welcome..
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] patbisch:
So if I want a 32 MB pagepool and no ramdisk, I must have 96 MB for program but I modify .nba file : FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 06 for program memory and 64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 00 02 for pagepool size and when I go to settings, system and memory in my device it show only 64 MB for program, what do I wrong ?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
Have you carried out corresponding modifications for RAMDisk=0 ???
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] patbisch:
I restart from nothing with rom kitchen and it's ok now but I don't no what's the problem !

Thanks.
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Gufer:
Ramdisk

Changing only registry doesn't change size of ramdisk ?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
You are right. For changing the size of the RAMDisk you have to change registry as well the hex editting the nk.nba .
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
1. Look for FF FF FF FF FF FF FF FF FF FF FF FF 00 00 and then make next two bytes as 00 08 to make it look like FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 08 .

2. No registry values to be placed for the RAMDisk.

3. Remove the folder ROM_Himalaya_v1.50_3.00a.40 from the OEM (if you are cooking the ROM yourself) which contains ramdisk.dll and the relevent registries.

4. look for 64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 and make next two byte as 00 02 to achieve the 32MB PagePool.

And voila you shouls achieve the desired... ANy prob you may get back to me..
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] your1337l33ch3r:
master im cooking your rom kitchen but the only problem i have is to locate the address of these FF FF FF FF FF FF FF FF FF FF FF FF 00 00?... i have a hard time searching for it... thank you so much for your HELP and REPLY... youre truly a MASTER...
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] dotfred:
As I mentioned earlier, look at this address : 0x004032e8

Cheers,

.Fred
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
As .fred has mentioned you may find it that way. But it is very simple to use search function by giving an ASCII string or byte sequence if you are using a hex editor. This search feature is part of that. Which hex editor are you using?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] your1337l33ch3r:
@master shekar

sorry for the inconvinience but i still couldnt see that values... im using master shekars rom kitchen... and advanced hex editor...

@dotfred

thanks for replying but i still couldnt see that values maybe because im using master shekars rom kitchen...

sorry
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] dotfred:
Are you sure you try to edit the nk.nba and not the nk.nbf?

c_shekhar and I are using the same nk.nba, so you definitely have to find this sequence in the hex editor.

Try Ultra Edit ( http://www.ultraedit.com ), load the nk.nba file, then type CTRL+G, this will show you a popup window where you have to enter the line where you want to go, just type the address mentioned in my previous post and you will find the values you're looking for!

Cheers,

.Fred
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] your1337l33ch3r:
master dotfred... yup... im editing nk.nba... im using ultraedit also... but it still the same... i cant look for it... i attached the file so you can see my problem... thank you so much master dotfred
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
In the screenshot which you have attached with your post I can very well see the byte sequence starting at the address 4032e8 and ending at 4032f7. As I can see in the screenshot, you have already changed the bytes for 0 RAMDisk and 128MB program memory. Go ahead...
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] your1337l33ch3r:
thanks master shekar... but i have a problem... whenever i resize my pagepool to 32mb it only gives me 81mb program memory?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Gufer:
Change yourself pagepool and ramdisk

So , after all these changes I have to coock new rom ? I found on buzzdev download section rom called unbranded with no other stuff ( I don't need it ) . Only need 64 MB ramdisk for GPS navigation software maps .
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Marx2:
you have 128MB of RAM in Himalaya. Usually it was diveded into 64MB RAM and 64MB Ramdisc. If you want bigger page pool, you must sacriface some RAM for it. So sum of them must give you 128MB of RAM

Shekhar in his ROM kitchen did it like this: 64RAM+40Ramdisc+24PagePool

After those changes you of course must burn new ROM
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] shaju:
Hi Shekhar,

Where should I change bites in Hexedit, If I want to have the 32MB ram, 32MB Pagepool? After Changing these Value in NK.nba which extracted from NK.nbf, I have chaged

FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 04 --> 64 MB program,memory: RAMdisk= 64MB:- for 32MB RAM disk

and

64 00 00 00 D8 FF 21 80 01 00 00 00 00 00 00 02 --> 32MB PagePool,

should I do following steps

4. Update Image Check Sum

xda2nbftool -c -u NK.nba

5. Repack as NK.nbf

xda2nbftool -x NK.nba NK.nbf 0×20040304

6. Put in the same directory as HimaUpgradeUt.exe or HimaUpgradeUt_NoID.exe

or

I have to cook as you mentioned above

2. change the registry in the folder \OEM\ROM_Himalaya_v1.50. It should be probably 0ffd60e6-162d-4643-850c-58fcc4e34579.rgu in your folder too. And cook.

???

Is it possible to see simcontacts in Contacts like Buzz AKU23? Where I can find Radio 1.19?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
By changing the pagepool size and the RAMDisk to your choice why dont you cook your own ROM it is very very simple. I have posted both my ROM Kitchens on the ftp in himalaya section and the concerned thread are :--

http://xdaforums.com/showpost.php?p=1044950&postcount=98

http://xdaforums.com/showpost.php?p=1024505&postcount=25

You can also visit buzzdev.cnet for more knowledge on ROM cooking.
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] bryanbelt:
Alright, c_shekhar. . .I am TRULY at a loss for what to say. I have tried several different ROMS, yours included, and no matter which I install, the page pool continues to come out at 16 MB. . .I tried editing the ROMs myself, but I gave up, realizing that you and others had already done the work for me. . .why is it that no matter WHICH ROM I use, it is always the same result?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] bryanbelt:
I'm pulling out what little hair I have left. . .HELP!!!

Seriously. . .I have hard-reset, re-flashed, deleted what was in the RAMDISK. . .NOTHING is working. . .
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Marx2:
how do you check how big page pool size is? There is only one method to check it:

page_pool_size = 128 - (RAM + Ramdisc).

I suspect you read some value from system info and treat it incorrectly as page pool size.
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] bryanbelt:
Am I correct that "page pool" and "storage" are the same thing? If not, please educate me. . .Perhaps I'm not explaining my dilemna correctly. There are a lot of things I'd like to install on my Himalaya. . .the problem is, even when I install them in the RAMDISC, my "Storage" space keeps decreasing. . .help. . .please?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
Too many queries bro...

First one first...

You can do both ways. If you choose procedure -1 (i.e unpack the already cooked NK.bnf) then for achieving the desired RAMDisk you have to change the registry after flashing the ROM. So every time you hard-reset your device you have to re-enter the necessary registry values. Whereas if you choose procedure-2 you have the ROM of your choice and taste which is fully ready to face any kind of reset..

3. It is possible to see the sim contacts in my ROM too for that you have to simply change few registry value which I can tell after you finish your ROM flashing.

4. Radio 1.19 you can find on this forum as well as buzzdev.net.

I hope I have answered all and nothing is left...cheers....
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
You are badly confused Bro! And you have unnecessarily strained yourself as well as your device by resorting to avoidable multiple flashes.

The Storage is different from pagepool. The Storage is abt 16MB and can be extended to 30MB by sacrificing the ExtROM. Whereas the pagepool is something which you can not see. You can only come to know of it by way of simply arithmatic calculations as explained my @marx2 above. I hope I am clear now.....
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] shaju:
I have successfully flashed my i-mate by changing value in NK.nba into 32MB pagepool & 0MB RAMdisk according to your intructions; step1. Then after flashing I have modified in the Regedit to get 32MB RAMDisk. It shows 93.22MB RAM & 31.96 RAMDisk, may I right?

After all these I'm interested about Contacts which show Sim-contacts, can u help me?

Thnx to your advice, waiting for .........
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
It is absolutely perfect...Congats mate...

regarding show sim contacts try these registry:

[HKEY_CURRENT_USER\ControlPanel\Phone]

"ShowSIM"=dword:1

Enjoy...
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] bryanbelt:
Okay...much clearer to me now...how do I sacrifice the ext rom...? If you could kinda' walk me through the process, I would very much appreciate it...Thank you in advance, c_shekhar...I sincerely appreciate all you do!
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
Thanks very much for the nice words dear. Run hima_doc_tool to merge the ExtRom into your storage...See here-->

Enjoy....
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Gufer:
Change page pool

It's working :) .

I remove at ocassion some software ( scenario , speed dialing and other ) Now my hima is working faster i think :) .But i did something stupid .... remove TCPMP :( and cant find OEM package with it .

Anyway it's good idea to test the changes .
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Marx2:
OEM packages are here (TCPMP too)

http://wiki.xda-developers.com/index.php?pagename=OEM packages
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
Good show...congrats..
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] ione:
Would you teach me how to increase the size of pagepool? I want it with 64M

or if it is prosible? Thanks
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
All the information is available on post #1 of this thread. What other way do you want me to teach???
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] OnceHeaven:
Hi guys, im using R 1.60c.00WWE, Radio 1.18.00, Ram size 128Mb. but den my storage has only 14.54mb which really is considered very very low, whereas program, i have a total of 120.32mb. can i get some advise on how to have bigger storage?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] c_shekhar:
Use hima_DOC_tool1.0 for merging the ExtROM into storage. You shall have 30MB storage after that. And mind you that there shall be no ExtROM in your device...try..
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] abc138:
Hi c_shekhar, tks for your great job!

Sorry for my stupid question:

How or where can i get the "nk.nba" file instead of "nk.nbf" which is in your ROM?

Thank u in advance!
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] TofClock:
Wow ....

This is with a old tool called xda2nbftool.exe

and in a dos prompt :

xda2nbftool.exe -x nk.nbf nk.nba 0x20040304

But ... i think , there is not a file called READ_ME_FIRST.txt with the rom .?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] abc138:
got it.

thank u sir!
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] solomhamada:
can any one who succesfully completed these steps CLEARLY illustrate them?

sincerly,

Adam
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] The_hesham:
I traied several times but no luck

As per the first post:

1- It is easy to get the .rgu file and modify the figures for Ramdisk

2- Suddenly C-shakhar jumbed to that we have to change some figures

FF FF FF FF FF ........

to the required programe size, where no body mention

3- to change the pagepool I did it by the programe name XVI32.exe, I changed as mentionned

but the result came 32pp & 32RD & 45 programes availabe !!!

What did I miss?

I think the main reason is that I didn't change this FF FF FF ........

Can some one give us a clear explanation.