yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rotohammer:
Another consideration is that if you just leave your apps running all the time, and just switch between them, you eliminate the startup delay and also the need for a large page pool. In this scenario, less page pool and more system RAM would be better. I run BatteryStatus which has a %CPU load and battery drain ma/mw indicator, so I know that my running apps aren't consuming extra power.

I realize everyone is looking for the Holy Grail(tm), but other usage strategies/patterns may provide the best perf/power.

Somewhat related, I turned on HSDPA, and noticed I'm getting a H indicator just about all the time now. I manually hit send/receive to check email this morning and at first glance I thought it wasn't working because I didn't see the status bar indicate logging in/receiving headers/etc. So I did it again and was surprised that it did check for mail, but very very fast. I'm anticipating this may increase my battery life, since it doesn't need to keep the connection live for as long while grabbing mail every 15 minutes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm just wondering who holds the trademark on that... Is it Galahad, Percival, Arthur, or Jesus himself? :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MickyMax:
Someone can post smaller page pool values and benchmark results ? (more ram, better battery life)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
0 pagepool means it acts like WM2003. Programs are always is copied into ram and runs from there (no XIP) with no limit on total RAM usage. When RAM is used up, it then walks its tracking and deletes stuff out of RAM, so massive lag. It works exactly like the pagefle.sys in Windows except it's not paging out. Pagepool is used to cache programs loaded from ROM so you don't get the slight hit waiting for it to be recopied in again on the next run.

edit: misremembered the MSDN blog about battery life:

The increased battery life of WM5+ over WM2003 is because most software isn't running out of ram.

I think the best way to tune pagepool is to total your usual clutch of programs and their ram usage (do not add system/XIP progarms). If you sit on the Today screen with no plugins, then a 2MB pagepool would work because almost everything is running out of XIP. Add in some other programs that are not .NETCF, and 6MB or 12MB pagepool make a lot of sense.

18MB if you got some .NETCF programs since they're FAT, and you're done. Remember, pagepool is about reducing program load time. It doesn't make programs, nor the OS run faster.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MickyMax:
Can you post the value for a 6MB pagepool size please ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rotohammer:
I don't believe this to be correct. Dynamic RAM refresh is not typically under the OS's control, its done by hardware. For example, the Infineon HYB18L256160BF-7.5 spec sheet says "Auto refresh and self refresh modes" and "Power consumption in self refresh mode is drastically reduced by an On-Chip Temperature Sensor (OCTS); it can further be reduced by using the programmable Partial Array Self Refresh (PASR)."

I don't have the specs for the Samsung RAM/ROM module, but Id expect it to be similar.

I agree, running a CPU benchmark to test the page pool is an invalid test.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
You're right, thanks. I misremembered the MSDN blog.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm not an expert either... but as far as I know it works like this:

1) ROM takes the same to power regardless of how much you have... so 16MB ROM chip should take about as much to power as a 256MB one.

2) RAM takes more per MB. So a 128MB chip takes apporox 2x more power than 1 64MB chip. In addition it doesn't matter if there is anything in that RAM chip or not, if the bank is powered on it will consume memory. So the only was to save memory is to not just not keep anything in the RAM bank, but to actively power it off when not in use.

If you have 1 bank of a 128MB chip I don't think you are using more power whether you have something loaded into that RAM or don't. As long as it is powered it will consume the same amount.

Now granted, if you have something loaded into RAM it is probably accessing other hardware like CPU, screen, etc... so RUNNING applications will take up more battery life than not. However it isn't consuming additional battery for the RAM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Nu... your comments lead me to believe that you think the device is using eXecute In Place. I'm not sure if you read my NOR/NAND thread, but at this point I don't believe the Kaiser is using NOR RAM. This means that there is nothing that is XIPing directly off the ROM. The contents of the XIP are preloaded into RAM to act as a "XIP cache" if you will.

Again, this all comes back to the use of NAND vs NOR. I can't find any documentation which states what type of ROM is actually being used on the Kaiser, but we shouldn't assume that it is NOR (and thus we can truly XIP from ROM) unless we have proof of that.

The fact that available memory (even on devices set with a 0 pagepool) is well below the 128MB chip that is in there is one piece of evidence I offer that we are using NAND RAM and thus loading the contents of XIP (low level device drivers) into RAM during boot.

Apart from that I agree with your assessment of how the PP works.

If you have any evidence to the contrary of what I am stating, please advise as I don't claim to be an expert.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Excellent point. I'm thinking that boot-up is one of the only tests to show a difference.

Reason being is that if I have 3 or 4 apps I typically keep open that consume less than available RAM (almost a given), then it doesn't matter how large my PP is as my apps are already loaded into RAM and should switch between each other as quickly as possible (as the RAM allows).

Maybe a speed increase will be seen switching between "built-in" apps like phone, settings, today screen, etc.

It is also possible that if you close your 3-4 custom apps, and then reopen them they may open quicker since part of their code pages are still in the PP.

Remember items in the PP won't run/switch faster than items not in the PP because the PP is just RAM, and EVERYTHING that is running runs in RAM (unless you have NOR ROM). People however are seeing differences in speeds and I can only attribute these to more code pages that are frequently used being able to stay in the PP.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
The best test of PP settings is boot time. The next best is utilizing built-in apps that reference a large number of individual files. For example, Your Mail Inbox & contacts. Also the settings pages & navigation between them.

For this it's recommended that you time these apps, From Button Push/Launch to the time they become fuly functioning.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
Now after all the tests we have gone through, The Mystry of this value 03 15 A0 03 00 10 8E 05 03 00 00 0A (kaiser Default) remains unsolved !!!

This value is not 12mb pp,so what is it then?

I changed the default value "03 15 A0 03 00 10 8E 05 03 00 00 0A" to "0C 16 A0 E3 00 10 8E E5 03 00 00 EA" which is also suppose to be 12mb pp and got the following results :

Total Memory : 101.32mb

In Use : 32.32mb

Free : 69.00mb

I also didn't feel any change in the speed between 12mb and 16 mb pp.

so if 0C 16 A0 E3 00 10 8E E5 03 00 00 EA is 12mb pp,then what is 03 15 A0 03 00 10 8E 05 03 00 00 0A ???

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dluisao:
ok very good
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
I'm only remarking, as I understand it, everything from the xip, as seen in the Part01.raw ROM dumps, is intended to run from any available NOR ram to XIP. The fact the Part01.raw dump is 5MB strongly suggests this, but as to how HTC actually implemented it on the Kaiser is up in the air.

Since, the OS kernel and many core subsystems exist in this 5MB section and the OS doesn't change (much), it's difficult to disbelieve that HTC wouldn't at least try to implement some XIP nvram in order to save battery.

But yes, this is all beside the topic which is what is a good size to set the pagepool to. There maybe a high and a low value thresholds that are getting set to the same so it doesn't change (much as how you should set your swap file size in 2000/XP to anyways).

I don't understand why such large pagepools are necessary on an embedded OS that seems to be designed to run within 32MB of ram, and even more so when compared to the PalmOS world where everything had been XIP since the beginning, iirc. Hell, since this is all flash and ram, we don't even have to deal with spindle latencies stretching into seconds vs nanoseconds.

I attribute a lot of the lag I've experienced to any app using .NETCF/Java because both are JIT compiled, bad database caching (Contacts app), and such. If I can get a 50K C++ app up and running in 1.5 vs 10 seconds for a .NETCF app, hmm..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
So actualy you advice to reduce the Kaiser default 12mb pagepool to 5mb.

It's worth a try :)

Thank you!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I think this would seriously hinder the Kaiser's Performance.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
Thanks AllTheWay

Reflashing the radio solved the Random Freeze problem.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
No. I think 12MB to 18MB should be BillGatesTM Good Enough. :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I'm glad it's working for you now :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
I agree with you and most likely 16mb pp is the optimum pp.

BTW, I tried the 5mb pp and it was very slow.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shafez:
Has anyone try the 18mb pp yet?

I just tried it and it is alot faster than the 16mb pp.

please give it a go and feel the diffference.

Regards
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
I agree that 18mb is very fast. Dutty's Hybrid from April 1 has a 18mb pp. I have tried 32, 24, 18, 16, 15 and I must say that either 18 or 16 is going to be your best bet.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
Thanks for making the 16MB pp available off your site. Saves me the trouble of getting dragged into a patching project. :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Tayton:
Another way to adjust the page pool.

I tried as a test to take a cooked windows.nb file and using the hex editor search for the hex strings A0 03 00 10 8E 05 03 00 00 0A. I found them twice in the file and made the adjustment to the previous two bytes on the two sets (10 16 from 03 15 for a 16mb page pool).

Checking the memory status it seemed to work this way. Also as a check I dumped the rom and reconstructed it with the kitchen. I then opened the nk.exe file and checked. Its value had been changed to the appropriate string.

I also noted that if I use that windows.nb file when building future versions of my rom it retains the 16mb (10 16 values) settings.

Can anyone verify this? It seems one step easier than the original method.

Also if anyone else has already posted this finding, congrats and sorry for the potential repost.

PS. I also tried changing the bites directly in a .nbh file and it seemed to work the same, I havent tried repeating this step to verify though.

Has anyone else done it this way? (Do all of you do it this way and I'm just behind?)

This would mean one can change the pagepool in a cooked rom file without having to extract it first.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Wow. I don't think I noticed that or maybe I am blind to. Now all we need is for somebody to change the Page Pool.exe to really change the page pool. By your theory you can easily do this also with a hex editor and the .nbh file without having to create a .nb file from it.

Now lets see if you can change the page pool on the AT&T 3.51 ROM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Tayton:
Well if i had to muster a guess.

For my test I was using my Rogers 1.83 rom.

I took a look at alex's recent 3.51 rom att rom as a lark.

Though the strings that dutty mentioned could not be found. I searched for some hex values that preceded it. I found to patterns that may work though I may be wrong but i dont think so.

search for the pattern, you will find it twice in the rom the same as the other pattern for the 1.83 rom.

03 E5 A0 03 00 E0 84 05 03 00 00

This co-incides to the other pattern.

I found this btw by searching for this hex string which is consistently before both patterns.

**** (Edit: i had the 8th byte incorrectly listed as 8a instead of 83 for those that test the string try again)

To test this try searching for this pattern on a rom where you know the True Page Pool has been changed. This string will be found twice and the True Page Pool string pattern that Dutty listed should start 3 bytes past it.

E1 02 38 83 E1 01 3C 83 E1 80 00

On the original roms the bytes to change were defaulted as 03 15. This one seems to be 03 E5.

So perhaps changing to two sets to.

10 E6 (the first two bytes) may yield a 16 meg page pool. I will try it later.

Note: This is a guess but the patterns seem to hold true. I will try it will alexs new clean rom to test.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Hi there,

If I understand right, this is the offset for the pagepool in the new AT&T build (CE version: 3.51.502.0)?

03 E5 A0 03 00 E0 84 05 03 00 00

Thank you :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Tayton:
Test pattern verified! Note that the method below is the way I found it to work.

Here are the following steps that should work on most roms. I am going to word it so possibly someone with program skills could make a page pool changer.

This was tested on Alex's 3.51 rom ultraclean .nbh file using a basic hex editor.

1) Searched for the first instance of the following hex string: E1 02 38 83 E1 01 3C 83 E1 80 00 (Only use this string for the first match!)

2) 3 bytes farther I found this hex string of 11 bytes: 03 E5 A0 03 00 E0 84 05 03 00 00

** (above string changes depending on what rom version you use and if its been cooked or not. In the case of the unchanged att rom I found E1 02 38 83 E1 01 3C 83 E1 80 00 ?? ?? 03 E5 A0 03 00 E0 84 05 03 00 00)

3) I copied that string 03 E5 A0 03 00 E0 84 05 03 00 00 into keyboard buffer for next search then set the second byte E5 to E6.

(Basically I added 1 to the value which maybe sets the pagepool to manual? This was based on Dutty changing his second byte from 15 to 16.

4) I changed the first byte 03 to 10 so the new string would read 10 E6 A0 03 00 E0 84 05 03 00 00

5) I searched for 03 E5 A0 03 00 E0 84 05 03 00 00 again and changed it to 10 E6 A0 03 00 E0 84 05 03 00 00 (basically repeating steps 3 and 4)

6) Saved the changes.

Here were the memory test results:

03 E5 A0 03 00 E0 84 05 03 00 00 yielded 81.30 mb ram (default)

10 E6 A0 03 00 E0 84 05 03 00 00 yielded 81.55 mb ram

11 E6 A0 03 00 E0 84 05 03 00 00 yielded 80.55 mb ram

14 E6 A0 03 00 E0 84 05 03 00 00 yielded 77.54 mb ram

I haven't performed any test benches on the different values. Feel free to test away. Just use the hex editor for now on any cooked .nbh rom or os.nb file. It doesnt really matter when you change it.

Last couple of thoughts:

- The idea worked for Polaris as well.

- If a page pool program is made the following logic should work:

-- Search for the first pattern

-- Move over 3 bytes and copy the next 11 bytes as the next search pattern.

-- Set the first byte to the desired page pool size.

-- The second byte should be set to E6 if previously E5 or 16 if original 15. If a new rom comes out that uses a different value again, perhaps the rule should be only add 1 to the second byte if the first byte is 03 (page pool set to dynamic). What do you guys think?

-- Search the new copied pattern to get to the next set.

-- change the first and second byte again as above.

I have no programming skills so someone else will have to take up the challenge of writing the page pool changing program. I noticed sakajati wrote a basic one from dutty's perhaps he could modify.

Thanks again Dutty on your hard work. Glad I could finally pitch in with this slight discovery.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] amik5:
What changes does this make on the phone? increased preformance?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Tayton:
Changing the page pool value affects the phones performance as noted in the beginning of this thread.

What page pool sizes to use have been covered in the first posts and tests have been performed on different sizes throughout the thread.

Based on what Dutty has found I assume the second byte enables or disables a manually set page pool.

The first byte is the actual page pool size in Hex.

10 = 16 meg page pool.

12 = 18 meg page pool.

18 = 24 meg page pool (again this is covered by Dutty)

The ATT 3.51 rom has a different hex string to search for as noted in my comments above.

As mentioned you can edit your cooked file directly which saves some steps.

If you want to change your ATT 3.51 rom to a 24 meg page pool for example. Do the following.

You can use a hex editor on the ruu_signed.nbh file or the window.nb (or whatever your os.nb file is) directly to change the page pool size.

1) Open up the RUU_Signed.nbh with hex editor.

2) search for A0 03 00 E0 84 05 03 00 00 and move back 2 bytes.

3) The values should 03 E5 if the rom is still set to dynamic.

4) Change E5 TO E6 if not already.

5) change the first byte before the E5 to the desired page pool size (03 is is intial size) to 16. Its in hex.

6) Search again repeating steps 2 to 5.

7) save changes
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Hi Tayton,

This one I find on the AT&T 3.51 build:

A0 03 00 E0 84 05 03 00 00

But moving 3 bites forward or backwards I can't find 03 E5 :confused:

Can you help me please?

Sorry but I'm a complete nOOb in this :D

Thank you!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Tayton:
Hi Laurentius,

I am just not explaining well. I worked out the system that should be universal to both roms. I gave a quick 7 step method for the att 3.51 only rom above to make it easier.

Let me show you how it works on your example.

(Click on it to expand picture, not sure why my attachment is so small)

The string inside the black frame box is the one that is found in most roms including the att 3.51 (E1 02 38 83 E1 01 3C 83 E1 80 00 ). and you can see that 3 bytes over are the values 10 E6. This indicates that the rom is already set to manual pagepool (because of the E6) and is set to 16 meg page pool (

because 10 = 16 meg page pool in hex 1F = 31 in hex, 20 = 32 etc)

Change that 10 value to whatever size you wish. remember its hex so 0E = 14 in decimal.

Note that the string in the black box can only be used to find the initial set. When you search for the second set use the string you highlighted and then change the previous 2 bytes. In your example again it is 10 E6 just left of your black highlight. make your first change then search again for the string you have highlighted (A0 03 00 E0 84 05 03 00 00 ) and two bytes previous will be 10 E6 again. Make same change there and save it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Thank you, very kind of you ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kyphur:
Kyphur's PagePool Patcher

Can be found here...

It will patch Roms that match the pattern of the at&t 3.51 Rom for PagePool.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sej0153:
Awesome!

Dutty, I have to say...you freaking rock! I love tweaking my tilt and hacking it in whatever way I can. I am definitely a taker and never contribute to any of these sites just because I figure someone else will anyway. I never thank anyone for their work either because a million people have already done it. Your Hybrid ROM however is so freaking awesome that I cannot help but tell you THANKS! It turns this device into a performance GOD. You are incredible at what you do, man. Thanks again. Keep up the fantastic work, and if you need anything please let me know, bro! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bushu16:
I must say, Dutty u r the ultimate king... I really respect you for your great work and creativity. keep up the good work. What do u do in general... as in for living
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Solarwind:
Hello duttythroy,

Downloading now, will try.

Your efforts much appreciated.

SW ;o)
[Xiaomi Poco F1 Questions & Answers] thegrantonstarcause:
Hi,

Has anyone tried to unlock the bootloader on their new phone? If so, what was the wait time you were given by Xiaomi? Am curious as recent Xiaomi phones have vastly increased waiting times for unlocking but as this phone is a global model and supposedly developer friendly I am hoping to not have to wait weeks when I receive mine.

Also, as an oem unlock does a full reset, is there any good method for performing a nandroid style backup of all apps and associated settings so if I do have to wait, I don't need to set everything up twice?
[Xiaomi Poco F1 Questions & Answers] PrathaM X:
https://en.miui.com/unlock/

not able to apply, after login it just says ERR_TOO_MANY_REDIRECTS :/

were u able to apply ?

edit : installed mi unlock on pc then tried, says 1440 hours wtf
[Xiaomi Poco F1 Questions & Answers] Ruvy:
AFAIK there is no way to take a nandroid backup without rooting your device. Now if you could root your phone without unlocking the bootloader that might just do.

However there are few exceptions like HELIUM you can try.
[Xiaomi Poco F1 Questions & Answers] thegrantonstarcause:
60 days :(

Thanks for checking.
[Xiaomi Poco F1 Questions & Answers] Daruwalla:
WTF, I would be dead by than. I got 30 days. :(

I used a very old Mi ID, should I create a new account and try or will it mess up the time limit more?
[Xiaomi Poco F1 Questions & Answers] PrathaM X:
dont know, there shold be some unofficial method

try posting this in miui forum , maybe will get help there
[Xiaomi Poco F1 Questions & Answers] raj7749:
guys try with new account.. after unlocking use old account
[Xiaomi Poco F1 Questions & Answers] Daruwalla:
Xiaomi changed the bootloader unlock policy. Now, you can unlock the bootloader after 3 days. I just unlocked mine which was showing 720hours.
[Xiaomi Poco F1 Questions & Answers] PrathaM X:
dont know but i tried thrice and i am just stuck on 99%

nothing happens after that
[Xiaomi Poco F1 Questions & Answers] Daruwalla:
What error it shows? Enabled dev option, enable bootloader unlock/usb debugging from developer settings and try?
[Xiaomi Poco F1 Questions & Answers] PrathaM X:
yes enabled both usb debugging in dev option, added miui acc too

still this -_-
[Xiaomi Poco F1 Questions & Answers] Daruwalla:
What this? Atleast tell the error or post screenshot. lol
[Xiaomi Poco F1 Questions & Answers] Skinpipe:
Has the oem unlock switch actually stuck in the correct position, it's a stupid switch that reverts itself, when you leave the screen you gotta click it a few times, sorry if you knew that already
[OnePlus 5 Questions & Answers] Arlenio Paiva:
I'm using the xxxNolimits rom 5.1.3. When I try to do the procedure to update the version of the oxygen I can not. I downloaded the rom from the site of oneplus, 5.1.4, I make the flash in the TWRP blu spark latest version and when I reboot the message "no OS installed"

I do not know what to do, my oneplus only recognizes the custom rom if I try to go back to the stock it does not recognize. It's like I'm not flashing anything. MA does not appear any error during the flashing of the stock rom by twrp

Could someone help me?