Microsoft has a diagnostic tool DevHealth.exe (sorry, I cannot publish it).
Here is the output on BA:
Code:
<Perf Gates>
<Gate Name=Memory>73351168</Gate>
<Gate Name=Storage>53208064</Gate>
</Perf Gates>
Bootup Time Markers (Milliseconds):
Calupd: Exiting = 54682
Initialized appt ssupdate = 54667
Initialized msgcount ssupdate = 54340
SSUpdate: Thread now in message loop = 54209
Calupd: Starting = 53221
SSUpdate: Shell Ready = 53089
System Memory Report
====================
Page Size: 4096
| Pages | Size (bytes) | Size (MB) | Address
Total Storage (Flash) | 15436 | 63228928 | 60.30 | n/a
Available Storage | 12990 | 53208064 | 50.74 | n/a
Used Storage | 2446 | 10020864 | 9.56 | n/a
Physical RAM (sources breakdown) | 24080 | 98631680 | 94.06 | n/a
Main Memory | 24080 | 98631680 | 94.06 | 0x901f0000 - 0x95ffffff
Physical RAM (consumers breakdown) | 24080 | 98631680 | 94.06 | n/a
Kernel Prealloc. | 139 | 569344 | 0.54 | 0x901f0000 - 0x9027afff
Paging Pool | 514 | 2105344 | 2.01 | 0x9027b000 - 0x9047cfff
Kernel RAM Map | 1 | 4096 | 0.00 | 0x9047d000 - 0x9047dfff
Watson Size | 75 | 307200 | 0.29 | 0x95fb5000 - 0x95ffffff
Overhead | 6 | 24576 | 0.02 | n/a
Object Store | 8 | 32768 | 0.03 | n/a
Program Memory | 23337 | 95588352 | 91.16 | n/a
AVAILABLE PROGRAM MEMORY | 17860 | 73154560 | 69.77 | n/a
USED PROGRAM MEMORY | 5477 | 22433792 | 21.39 | n/a
Kernel Objects | 406 | 1662976 | 1.59 | n/a
Misc | 138 | 565248 | 0.54 | n/a
Programs | 4933 | 20205568 | 19.27 | n/a
(S) Stack | 405 | 1658880 | 1.58 | n/a
(H) Heap | 2149 | 8802304 | 8.39 | n/a
(E) EXE Data | 109 | 446464 | 0.43 | n/a
(D) DLL Data | 699 | 2863104 | 2.73 | n/a
(c) Code RAM | 631 | 2584576 | 2.46 | n/a
Process | 208 | 851968 | 0.81 | n/a
Module | 423 | 1732608 | 1.65 | n/a
(r) Read only RAM | 153 | 626688 | 0.60 | n/a
Process | 60 | 245760 | 0.23 | n/a
Module | 47 | 192512 | 0.18 | n/a
Map/Shared | 46 | 188416 | 0.18 | n/a
(W) Read/Write RAM | 787 | 3223552 | 3.07 | n/a
Process | 429 | 1757184 | 1.68 | n/a
Module | 0 | 0 | 0.00 | n/a
Map/Shared | 358 | 1466368 | 1.40 | n/a
Look at the "Paging Pool" line, it is only 2.01 Mb. On HTC Universal it is 4.8 Mb, on one of the DELLs it is 8 mb.
The large the paging pool is, the more code pages can present in RAM simultaneously -> the less loads from slow ROM -> the faster the device is.
BA has 128 Mb RAM, so we can increase it safely to 8Mb (larger value would not give noticeable improvements).
One note - I don't know the addresses to patch in ROM, so someone should find how to increase pool size.
The true GURU is back!
its really Nice to see u again mamaich!... hopes u can help us here in BA...
Another step forward .. thanks to all of you guys.
mamaich
Were you able to get your hands on nkDebugX (available as a powertoy)?
ok
how to increase pool size ? :evil: :twisted:
MDAIIIUser said:
Were you able to get your hands on nkDebugX (available as a powertoy)?
Click to expand...
Click to collapse
I never heard about this tool.
Regarding paging pool size:
Code:
0000437056: 28 A0 1F 80 FF FF FF FF │ FF FF FF FF 9B 4F FF FF (а А ЫO
0000437066: 64 B0 00 00 64 00 00 00 │ 08 DF 1F 80 00 00 20 00 d░ d ▀ А
0000437076: 00 00 00 00 C4 6B 1D 80 │ 50 C0 1D 80 9C F0 1C 80 ─k АP└ АЬЁ А
At address 0437072 of NK.NBA you see 00 00 20 00. Try to increase the value to 00 00 80 00 (it would increase pool to 8 mb). If this works - you'll see the noticeable speedup during boot process, and the RAM amount displayed in "memory" CPL applet would decrease by 6 Mb.
You may play with higher/lower values, 8 Mb should be enough in most cases. But BA has lots of RAM, so you may try 16Mb.
But the device may fail to boot. In this case connect KITL and tell me the error message, it is possible that some other addresses should be also changed (or maybe I've found an invalid address, I was looking in Universal's ROM).
I edited nk.nba as you advised and flashed my BA with edited Helmi 1.3.1 ROM.
Super fast!!!!!
It works!!!!!!
Thanks GURU mamaich!!!!
And RAM is reduced 6 MB as you mentioned.
From 91.16 to 85.14 MB.
Image attached
mamaich said:
MDAIIIUser said:
Were you able to get your hands on nkDebugX (available as a powertoy)?
Click to expand...
Click to collapse
I never heard about this tool.
Regarding paging pool size:
Code:
0000437056: 28 A0 1F 80 FF FF FF FF │ FF FF FF FF 9B 4F FF FF (а А ЫO
0000437066: 64 B0 00 00 64 00 00 00 │ 08 DF 1F 80 00 00 20 00 d░ d ▀ А
0000437076: 00 00 00 00 C4 6B 1D 80 │ 50 C0 1D 80 9C F0 1C 80 ─k АP└ АЬЁ А
At address 0437072 of NK.NBA you see 00 00 20 00. Try to increase the value to 00 00 80 00 (it would increase pool to 8 mb). If this works - you'll see the noticeable speedup during boot process, and the RAM amount displayed in "memory" CPL applet would decrease by 6 Mb.
You may play with higher/lower values, 8 Mb should be enough in most cases. But BA has lots of RAM, so you may try 16Mb.
But the device may fail to boot. In this case connect KITL and tell me the error message, it is possible that some other addresses should be also changed (or maybe I've found an invalid address, I was looking in Universal's ROM).
Click to expand...
Click to collapse
Mamaich... U're still the best in everything!!! its work like a charm...thanks Mamaich..
In my rom, its make faster just like wm2003... :wink:
helmi_c said:
Mamaich... U're still the best in everything!!! its work like a charm...thanks Mamaich..
In my rom, its make faster just like wm2003... :wink:
Click to expand...
Click to collapse
Hey Helmi
I agree with you.
Mamaich is GURU.
And you too.
Thanks all.
Hope you will release a new ROM with this patch soon.
:wink:
Future WM5 releases -
Is it safe to say future releases will include this larger pooling system for BA?
btw 9-14 is my bday...hrmm I wish for a better BA globally! :twisted:
mamaich said:
At address 0437072 of NK.NBA you see 00 00 20 00. Try to increase the value to 00 00 80 00 (it would increase pool to 8 mb). If this works - you'll see the noticeable speedup during boot process, and the RAM amount displayed in "memory" CPL applet would decrease by 6 Mb.
You may play with higher/lower values, 8 Mb should be enough in most cases. But BA has lots of RAM, so you may try 16Mb.
But the device may fail to boot. In this case connect KITL and tell me the error message, it is possible that some other addresses should be also changed (or maybe I've found an invalid address, I was looking in Universal's ROM).
Click to expand...
Click to collapse
Thanks Mamaich, My Rom is very fast
helmi_c said:
mamaich said:
MDAIIIUser said:
Were you able to get your hands on nkDebugX (available as a powertoy)?
Click to expand...
Click to collapse
I never heard about this tool.
Regarding paging pool size:
Code:
0000437056: 28 A0 1F 80 FF FF FF FF │ FF FF FF FF 9B 4F FF FF (а А ЫO
0000437066: 64 B0 00 00 64 00 00 00 │ 08 DF 1F 80 00 00 20 00 d░ d ▀ А
0000437076: 00 00 00 00 C4 6B 1D 80 │ 50 C0 1D 80 9C F0 1C 80 ─k АP└ АЬЁ А
At address 0437072 of NK.NBA you see 00 00 20 00. Try to increase the value to 00 00 80 00 (it would increase pool to 8 mb). If this works - you'll see the noticeable speedup during boot process, and the RAM amount displayed in "memory" CPL applet would decrease by 6 Mb.
You may play with higher/lower values, 8 Mb should be enough in most cases. But BA has lots of RAM, so you may try 16Mb.
But the device may fail to boot. In this case connect KITL and tell me the error message, it is possible that some other addresses should be also changed (or maybe I've found an invalid address, I was looking in Universal's ROM).
Click to expand...
Click to collapse
Mamaich... U're still the best in everything!!! its work like a charm...thanks Mamaich..
In my rom, its make faster just like wm2003... :wink:
Click to expand...
Click to collapse
What tool/editor you used to edit the rom?
Thanks!
mamaich said:
At address 0437072 of NK.NBA you see 00 00 20 00. Try to increase the value to 00 00 80 00 (it would increase pool to 8 mb)
...................................
You may play with higher/lower values, 8 Mb should be enough in most cases. But BA has lots of RAM, so you may try 16Mb.
Click to expand...
Click to collapse
Mamaich,
How to edit to 16 MB.
I will try to do.
Since it's hexadecimal, it sounds logical to me that you would replace the "8" (or "2") by "F" which is the equalent of 16 in hex.
Or is this too simple?
GerardNL said:
Since it's hexadecimal, it sounds logical to me that you would replace the "8" (or "2") by "F" which is the equalent of 16 in hex.
Or is this too simple?
Click to expand...
Click to collapse
0xF is 15 and not 16
you should change 00 00 20 00 to 00 00 00 01
These are hexadecimal values with the reverse order of bytes: 0x200000 (2097152) in the first case and 0x1000000 (16777216) in the second.
I don't think that there would be noticeable improvement when changing 8 to 16 Mb.
Thz all
i test it very fast this first time to fast like this thz somuch
mamaich said:
you should change 00 00 20 00 to 00 00 00 01
These are hexadecimal values with the reverse order of bytes: 0x200000 (2097152) in the first case and 0x1000000 (16777216) in the second.
I don't think that there would be noticeable improvement when changing 8 to 16 Mb.
Click to expand...
Click to collapse
Thankssssss mamaich.
Will have a try when have time.
But now it is very fast with 8 MB.
So impressive. :wink:
Is there a cab file patch that can acomplish this miracle or can it only be done by creating a new ROM? I have yet to try creating a ROM as I am too chicken to try..... :-( (afraid of winding up with an expensive paperweight)
motisu said:
Is there a cab file patch that can acomplish this miracle or can it only be done by creating a new ROM? I have yet to try creating a ROM as I am too chicken to try..... :-( (afraid of winding up with an expensive paperweight)
Click to expand...
Click to collapse
This cannot be done via CAB.
Related
Barebone 2.6
Barebone 2.6 released, released on Jun 24
Barebone 2.5 released, released on Jun 20
Barebone 2.4 released, released on Jun 11
Barebone 2.3 released, released on Jun 6
Barebone 2.2 released, released on Apr 7
Barebone 2.1 released, released on Apr 1
Barebone 2.0 released, released on Mar 28
Barebone 1.5 released, released on Jan 30
Barebone 1.4 released, released on Jan 27
Barebone 1.3 released, released on Jan 26
Barebone 1.2 released
seperation of slim and barebone edition (both reached version 1.1)
first release, released on Jan 19
The idea of this roms is to provide a very small and leightweight rom with maximum stability and performance. The device has great hardware, but the built-in software doesn't use this hardware properly, so its up to you to install the right software from other software houses.
The rom is not protected, you are invited to take it as a base for your own roms/experiments. Modifying it using the kitchen is quite easy.
General
Instructions how to flash a rom can be found here, there or in the wiki
ROM is user customizable (more information)
ROM is compressed using 7-Zip
I'm not responsible for any harm
This ROM is not protected in any way. You are invited to use it as a base for own ROMs (or experiments)
Windows Mobile 6.1 Professional, CE OS 5.2.21051, Build 21051.1.6.4
Based on Blackstone official release 1.59.709.0
~370 MB of free storage memory
~150 MB of free program memory
dynamic pagepool
The idea of this barebone rom is to provide a very small and leightweight rom with maximum stability and performance. Therefore most oem applications are removed, whereas libraries still remain in order to make the device running properly.
The following has been removed
AdobePDF
Album
AudioBooster
AudioManager
AutoVolumeControl
AutoUpdate (doesn't work anyway)
WorldCard Mobile
Catalog
CommManager
ConnectionSetup (including DB)
CyberonVoiceSpeedDial
EnlargeStartMenu
FullScreenPlayer
GoogleMap
HTCAnimation
HTCMessage
IME (including ezInput)
IPSECVPN
JbedJava
JetCetPrint
LargeTitleBar
Managed Programs
Manila
MP3Trimmer
NewMailAccount
OneNote
Opera
OutlookEnhancement
PictureEnhancement
RemoteDesktopMobile
RSSHub
SampleMusic
SamplePictures
SocialNetworkEngine
SQM (replaced through dummy)
StreamingMedia
StreamingSrcFilter
TaskManager (the HTC one)
Teeter
Transcriber
USBToPCPopUp
VoiceRecorder
VolumeControl
WelcomeCenter
WindowsLive
YouTube
Zip
Some unneeded files
Unnedded themes
Changes made
Updated .NET Compact Framework to version 3.5
Updated SqlCeMobile to version 3.5
Registry and file system has been cleaned up, removing any not needed HTC keys/values
replaced theme because of color issues (see here)
User customizable (see here)
Added NeoS2007 graphic pack (see here)
Performance tweaks (mainly enabling/increasing all kinds of caches)
Increased wireless speed (see here)
SD TuneUp (see here)
Screen rotation from screen menue enabled
Security warning (for non-certified software) disabled
Disabled error reporting
Disabled feedback (+menue removed)
Today items are activated by default
Native Windows Mobile Incall Recording enabled
SIM contacts aren't shown by default
Following tweaks & fixes have been included
SMS Timezone fix
Patched payload
Updated some graphic drivers
Known bugs/issues
none
Donation
Creating and supporting this ROM is kind of time-intensive. If you appreciate my work consider a donation
Thanks!
Thanks to all of those who give me something back and motivate me for the further development!
chris5304, 10 Euro
bigdog, 5 Euro
makkad, 10 Euro
kalhimeo, 15 Euro
Download
Version 2.6: HTTP, 54762807 bytes, MD5: 2e608d6e272cb6353be0a78b2c68d3d3
Version 2.5: HTTP, 54766593 bytes, MD5: 792835a7cd73a7623240f8a8919c6554
Version 2.4: HTTP, 54728605 bytes, MD5: d9cc18bd31e4f642de4a56156641e9e7
Version 2.3: HTTP, 54868958 bytes, MD5: f33431c3d7557e1f27080fa667924fc5
Version 2.2: HTTP, 54093692 bytes, MD5: 1bd6b88f5859181ed61771aab9fdb190
Version 2.1: HTTP
Version 2.0: HTTP
Version 1.5: HTTP
Version 1.4: HTTP
Version 1.3: HTTP
Version 1.2: HTTP
Slim Version 1.1: HTTP
Version 1.1: HTTP
Version 1.0: HTTP
Check out my other ROMs
Geranium, Windows Mobile 6.5
Thanks to all the people making rom cooking in this way possible!
Changelog
Version 2.6
Fixed issue with customer feedback (won't popup anymore)
Fixed graphic issues (tearing) within some applications
Replaced some graphic drivers in order to get better performance
Version 2.5
Added NeoS2007's driver package
Fixed version display
Increased performance
Version 2.4
Removed Catalog
Removed Managed Programs
Replaced some graphic drivers
Changed default font size
Version 2.3
New base ROM: 1.59.709
Updated XIP & OS version to 21051
Added GraphPack
Removed application you may want to install
Here is a list of removed applications you may want to install. Just download the cab and install it as usually. The cabs were created from the OEM packages, so should be just the same.
AdobePDF
Album (HTC)
AudioBooster
World Card Mobile
CommManager
connectionsetup HTC
ConnectionSetupDB
CyberonVoiceSpeedDial
IME Engine Western
IME EzInput Western
JetCet Print
TaskManager
Teeter
USBToPCPopUp
YouTube
ZIP (HTC)
Opera9
If you wish to have a cab for your favorite application just tell me about it
Benchmark results
SPB Benchmark
Write 1 MB file: 523.200000
Read 1 MB file: 35.100000
Copy 1 MB file: 596.600000
Write 10 KB x 100 files: 4080.900000
Read 10 KB x 100 files: 208.600000
Copy 10 KB x 100 files: 2657.200000
Directory list of 2000 files: 1206.300000
Internal database read: 764.800000
Graphics test: DDB BitBlt: 3.930000
Graphics test: DIB BitBlt: 30.645000
Graphics test: GAPI BitBlt: 5.875000
Compress 1 MB file using ZIP: 2755.900000
Decompress 1024x768 JPEG file: 413.400000
Arkaball frames per second: 8.801500
CPU test: Whetstone MFLOPS: 3569.000000
CPU test: Whetstone MOPS: 1000.700000
CPU test: Whetstone MWIPS: 7167.800000
Copy 1 MB using memcpy: 8.430000
Test OpenGL
alpha texture: 38348 kPixel/s
torus one light: 7270 kPixel/s
color blending: 38439 kPixel/s
sub texture: 10774 kPixel/s
Here you can read more about it.
Overview of packages
OEM
Code:
OEM Version List
Folder: C:\BlackStoneKitchen\OEM\
App. Name Version
--------------------------------------------------------------------------------
AdvancedNetwork 1_0_9_0
App_Service_dll 1_62_0_0
Arcsoft_MMS 5_0_43_98R6
AutoRun 4_31_6_2
AutoShortcut 1_1_2_0
BluetoothSetting 2_11_0_0
BootLauncher 1_0_35330_2
BTBPP 1_6_8_0
BTSAP 3_2_0_R2
ButtonSetting 3_16_0_0
CAMERA 6_6_32687_8
CheckAutoRun 2_18_0_0
CleanGPSData 1_1_0_0
ClearStorage 1_38_0_0
ConcurrenceMgr 1_2_18192826_0002
DataDisconnect 1_13_0_0
DeviceInfo 1_27_0_0
DRMMiddleware 1_0_080630_0
DShow 2_00_081210_0
FMRadio 1_6_18191820_2
GSensorCalibrator 1_1_18191827_2
HTCApplication 1_9_0_1
HTCGesture 1_0_30346_2
HTCSettings 1_3_8_1
HTCUtil 3_22_0_0
InvokeSIMMgr_dll 1_11_0_1
LockStreamDRM 1_1_080625_O9_08
LongPressEndKey 1_2_37378_3
mHubVO 1_65_081121_X0
Mute 1_1_2_0
MyCPL 3_13_0_6
PhoneCanvas 3_50_33398_1
PhoneSetting 6_23_0_3
PKG 1_1_0_0
Power 2_18_0_0
PowerOffWarning 1_15_0_0
QuickGPS 1_00_18202228_01
RandomAccess 4_1_18222125_0
Redial 1_2_0_0
RingtonePlugin 1_00_080624_2
SensorSDK 3_3_18192831_1
SIM_MGR_exe 6_57_0_0
SIMLock_exe 4_24_0_0
stk_service_dll 4_84_0_0
stk_uippc_exe 4_62_0_0
StorageLow 1_0_0_2
TouchFlo 3_0_32567_2
USBtoPC 1_24_0_1
USSD_Service 4_30_0_0
VersionInfo 1_0_18182525_0
VideoTelephony 2_0_33916_0
WiFiSettings 1_2_1_0
WLANSettings 2_4_3_0
--------------------------------------------------------------------------------
Generated with OEM Version Checker by Vic, 2008
SYS
Code:
SYSversion 1.2 by MrVanx - 2008
--------------------------
SYS Directory Found
---------------------------
No DSM Found! | .ROM
No DSM Found! | .VM
5.2.21041 aku 1600 | AdobeFlash
5.2.21041 aku 1600 | AdobeFlash_LANG_0409
5.2.21051 aku 1604 | BaseApps
5.2.21051 aku 1604 | BaseAppsFiles
5.2.21041 aku 1600 | Base_DPI_192
5.2.21041 aku 1600 | base_dpi_192_resh_480_resv_800
5.2.21046 aku 1603 | Base_Lang_0409
5.2.21041 aku 1600 | Base_Lang_0409_DPI_192
5.2.21041 aku 1600 | Base_Lang_0409_DPI_192_RESH_480_RESV_800
5.2.21041 aku 1600 | Bluetooth
5.2.21041 aku 1600 | Bluetooth_Lang_0409
5.2.21051 aku 1604 | BROWSING
5.2.21051 aku 1604 | BROWSINGCORE
5.2.21041 aku 1600 | browsingie
5.2.21041 aku 1600 | browsingie_LANG_0409
5.2.21041 aku 1600 | Browsing_DPI_192
5.2.21041 aku 1600 | Browsing_Lang_0409
5.2.21051 aku 1604 | BTDUN
5.2.21041 aku 1600 | Bth_A2DP
5.2.21041 aku 1600 | Bth_A2DP_Lang_0409
5.2.21041 aku 1600 | Bth_HID
5.2.21041 aku 1600 | Bth_HID_Lang_0409
0.0.0 aku 0 | ChangeTextSize
5.2.21041 aku 1600 | CommonNonEA
0.0.0 aku 0 | DisableErrorReporting
0.0.0 aku 0 | DisableFeedback
0.0.0 aku 0 | DisableSecurityWarning
5.2.21041 aku 1600 | DRM
0.0.0 aku 0 | EnableInCallRecording
0.0.0 aku 0 | EnableRotationFromScreenMenue
0.0.0 aku 0 | EnableWLANGMode
5.2.21041 aku 1600 | Enterprise
5.2.21041 aku 1600 | Enterprise_DPI_192
5.2.21041 aku 1600 | Enterprise_Lang_0409
5.2.21041 aku 1600 | Enterprise_Lang_0409_DPI_192
5.2.21041 aku 1600 | Entertainment
5.2.21041 aku 1600 | Entertainment_DPI_192
5.2.21041 aku 1600 | Entertainment_Lang_0409
5.2.21041 aku 1600 | Entertainment_Lang_0409_DPI_192
5.2.21041 aku 1600 | FWUPDATE
5.2.21041 aku 1600 | Fwupdate_Lang_0409
5.2.21041 aku 1600 | GPSID
0.0.0 aku 0 | Grahpic_Driver_Pack
5.2.21041 aku 1600 | INTERNETSHARING
5.2.21051 aku 1604 | MediaOS
5.2.21051 aku 1604 | MediaOSFiles
5.2.21041 aku 1600 | MediaOS_dpi_192_resh_480_resv_800
5.2.21041 aku 1600 | MediaOS_Lang_0409
0.0.0 aku 0 | Metadata
0.0.0 aku 0 | NetCF
0.0.0 aku 0 | no2chem_dummycustsat
5.2.21042 aku 1601 | Office
5.2.21041 aku 1600 | Office_DPI_192
5.2.21041 aku 1600 | Office_Lang_0409
5.2.21041 aku 1600 | Office_Lang_0409_DPI_192
5.2.21051 aku 1604 | OS
5.2.21051 aku 1604 | OSFiles
0.0.0 aku 0 | Performance
5.2.21051 aku 1604 | Phone
5.2.21051 aku 1604 | PhoneRedist
5.2.21041 aku 1600 | PhoneRedist_DPI_192
5.2.21041 aku 1600 | PhoneRedist_Lang_0409
5.2.21041 aku 1600 | PhoneRedist_Lang_0409_DPI_192
5.2.21041 aku 1600 | Phone_DPI_192
5.2.21041 aku 1600 | Phone_dpi_192_resh_480_resv_800
5.2.21041 aku 1600 | Phone_Lang_0409
5.2.21041 aku 1600 | Phone_Lang_0409_DPI_192
5.2.21041 aku 1600 | ppgprov
5.2.21051 aku 1604 | Redist
5.2.21041 aku 1600 | Redist_DPI_192
5.2.21041 aku 1600 | Redist_dpi_192_resh_480_resv_800
5.2.21041 aku 1600 | Redist_Lang_0409
5.2.21041 aku 1600 | Redist_Lang_0409_DPI_192
5.2.21051 aku 1604 | RUNTIMES
0.0.0 aku 0 | SDTuneUP
5.2.21051 aku 1604 | Shell
5.2.21041 aku 1600 | SIM_TKit
5.2.21051 aku 1604 | SMIME
0.0.0 aku 0 | SmsTimezoneFix
5.2.21041 aku 1600 | SMS_Providers
5.2.21041 aku 1600 | SQLCE
0.0.0 aku 0 | SqlCeMobile
0.0.0 aku 0 | SqlCeMobile_Lang_0409
0.0.0 aku 0 | WakeUpOnNewSMS
5.2.21041 aku 1600 | WWAN
Build version has been patched at some stage
Good, exactly, what I was looking for. 6.1 free of bloatware.
congrats on the ROM man
Finally congratulations!
nice thanks
but what i really wanna see is a wm6.1 rom free of all the htc gubbings, especially TF3D, dont use it anyway prefferring spb stuff
so if anyone wishes to accomadate? (i cant work the kitchen stuff at all being geekless )
cool man thanks,
i love the idea of this,
thanks
Thanks for all the congratulations, hopefully its usefull for one of you .
Beautiful!! D/L right now.
After some restructure I now come up with two branches. The slim and the barebone one. It should be quite clear (after reading the descriptions above ) what you are confronted with.
Any suggestions, comments or something like that?
hi,
thank you for your work. it is lightest rom in the forum.
just a quick question: what version of .net framework is included (default one 2) or 3.5 ?
thank you
many thanks, just what im looking for. will try it out on the weekend when im not pda dependant!
John, thank you very much for this ROM. It is exactly what a lot of people were looking for. Thank you.
miri said:
just a quick question: what version of .net framework is included (default one 2) or 3.5 ?
Click to expand...
Click to collapse
I decided to stay at version 2.0. Although the 3.5 version is running fine (in most cases), there might be software not running as it is still a beta and therefore not built for roms granting maximum stability.
Installing the framework isn't a problem at all, you can also use netcfcfg in order to switch between those versions (in general and for a single application only).
Barebone 1.2 has been released!
Congratulations for Barebone 1.2. It is exactly what I was looking for.
I use SPB mobile shell instead manilla
Sehr schön!
Wenns das Ganze jetzt noch als deutsches ROM gibt, wäre es supi!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The two last champions goes face to face in the first game of the regular season!
Which team will you pick?
Offensive Comparison
Total Yards Per Game
NO: 372.5
GB: 358.1
Passing Yards Per Game
NO: 277.6
GB: 257.8
Rush Yards Per Game
NO: 94.9
GB: 100.4
Points Per Game
NO: 24.0
GB: 24.2
Third Down Conversion %
NO: 48.8
GB: 41.5
Time of Possession
NO: 1925.0
GB: 1921.0
Defensive Comparison
Total Yards Per Game Allowed
NO: 306.2
GB: 309.1
Passing Yards Per Game Allowed
NO: 193.9
GB: 194.2
Rush Yards Per Game Allowed
NO: 112.3
GB: 114.9
Points Per Game Allowed
NO: 19.2
GB: 15.0
Third Down Conversion % Allowed
NO: 34.5
GB: 36.2
Team Leaders:
2010 record: 11-5 (Second in NFC South)
Passing | Cmp | Att | Yds | TDs
#9 Drew Brees | 448 Cmp | 658 Att | 4620 Yds | 33 TDs
#10 Chase Daniel | 2 Cmp | 3 Att | 16 Yds | 0 TDs
Rushing | Car | Yds | Avg | TDs
#29 Chris Ivory | 137 Car | 716 Yds | 5.2 Avg | 5 TDs
#21 Pierre Thomas | 83 Car | 269 Yds | 3.2 Avg | 2 TDs
Receiving | Rec | Yds | Avg | TDs
#12 Marques Colston | 84 Rec | 1023 Yds | 12.2 Avg | 7 TDs
#16 Lance Moore | 66 Rec | 763 Yds | 11.6 Avg | 8 TDs
2010 record: 10-6 (Second in NFC North)
Passing | Cmp | Att | Yds | TDs
#12 Aaron Rodgers | 312 Cmp | 475 Att | 3922 Yds | 28 TDs
#10 Matt Flynn | 40 Cmp | 66 Att | 433 Yds | 3 TDs
Rushing | Car | Yds | Avg | TDs
#** Brandon Jackson | 190 Car | 703 Yds | 3.7 Avg | 3 TDs
#12 Aaron Rodgers | 64 Car | 356 Yds | 5.6 Avg | 4 TDs
Receiving | Rec | Yds | Avg | TDs
#85 Greg Jennings | 76 Rec | 1265 Yds | 16.6 Avg | 12 TDs
#89 James Jones | 50 Rec | 679 Yds | 13.6 Avg | 5 TDs
I managed to edit the file /system/url/keychars/omap-keypad.kcm.bin, which is the hardware keyboard layout file with HxD (hex editor).
This post helped me a lot to do this:
http://forum.xda-developers.com/showthread.php?t=945921
I mapped the keys to type the following:
Normal | Shift | Alt | Shift+Alt
a | A | ä | €
o | O | ö | )
u | U | ü | *
8 | 8 | Ä | 8
9 | 9 | Ö | 9
0 | 0 | Ü | 0
You can download the bin file, replace it in /system/url/keychars/ an set the same permissions like the old file had.
Good luck, have fun.
Note that on the screenshot, a "." is missing after the "ä", I added this in the file but didn't update the screenshot.
I have told the OP that this topic may stay in Development.
how did you manage to edit it? I would like to do the same in order to be able to write czech characters...
http://www.pcguide.com/res/tablesASCII-c.html might come in handy, along with a hex editor like HxD.
Thanks Jewremy, forgot to mention that I used HxD ))
1.) do I need to have root to do this?
2.) What are the first two positions for in the bin file? For examle:
You say it works like this:
Normal | Shift | Alt | Shift+Alt
a | A | ä | €
...in the bin file the corresponding row looks like this (I added one more dot after the first ¬):
A.¬.a.A.ä.¬
...so there is six positions instead of four - what is the use of the first two?
This helped me a lot to do it. Added it to my first post.
http://forum.xda-developers.com/showthread.php?t=945921
Rotkaeqpchen said:
This helped me a lot to do it. Added it to my first post.
http://forum.xda-developers.com/showthread.php?t=945921
Click to expand...
Click to collapse
Could you do a stock one, but edit the ok button to be a smiley key???
I don't know if that works, first I don't see the OK key, second I don't think that you can bind 2 characters to one key. Please anyone help him!
Im going to get to the point.
Hey Miroslav or anyone with experience with filesystems please take a look!
=========================================================
Code:
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | mtd | 0 | 0 | 0 | u |
| system | /dev/block/mtdblock4 |[COLOR="Red"][B] yaffs2 [/B][/COLOR]| 153600 | 137928 | 1 | f |
| data | /dev/block/mtdblock6 | [COLOR="Red"][B]yaffs2 [/B][/COLOR]| 239104 | 105300 | 1 | f |
| boot | /dev/block/mtdblock0 | mtd | 5120 | 5120 | 0 | i |
| recovery | /dev/block/mtdblock2 | mtd | 5120 | 5120 | 0 | i |
| cache | /dev/block/mtdblock1 | yaffs2 | 65536 | 31184 | 1 | f |
| sdcard | /dev/block/mmcblk0p1 | vfat | 0 | 0 | 1 | n |
| | | | 0 | 0 | 0 | n |
| andsec | /sdcard | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk0p2 | ext4 | 0 | 0 | 1 | f |
| | /dev/block/mtdblock10 | mtd | 474880 | 474880 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
As the above shows our phones system and data partitions uses the yaffs2 filesystem but is there a way to convert this to ext4? Many phones has done this "conversion" and there is said to be noticeable improvements. Eg. Galaxy Ace
Here is a short explanation of it
Most Android devices currently use YAFFS, a lightweight filesystem that is optimized for flash storage . The problem with YAFFS is that it is single-threaded and according to Google developer Ted Tso, it would likely “have been a bottleneck on dual-core systems.” EXT4 a much superior file system was used in the latest Google Nexus S. Tim Bray of Android Developers Blog has said starting with Nexus S and Gingerbread O/S , this change has bring a big boost in input and output file operations, and explains some of the amazing speed improvements seen on the Nexus S.
Click to expand...
Click to collapse
Quoted from http://leemn.wordpress.com/2011/01/...stem-to-ext4-and-upgrade-to-modaco-rom-beta1/
=========================================================
Ok here is a example!
(These file are from http://forum.xda-developers.com/showthread.php?t=1593925) A Galaxy Ace Rom
✔ Filesystem Are In EXT4 Format [ Best System Performance ]
In the update.zip of the Rom there is this file
mkfs.ext4
According to to the updater-script which controls what the recovery does when it flashes a rom, it does this to the above file
Code:
package_extract_file("mkfs.ext4", "/tmp/mkfs.ext4");
and later
Code:
set_perm(0, 0, 0755, "/tmp/mkfs.ext4");
=========================================================
If any of this makes sense to you please comment down below. Maybe we can port this to our phones
Is this do sth else with file or its just set perms?
Also can u provide links to roms with ext4 converted from yaffs as u say?
Sent from my LG-GT540 using xda premium
All phone with 512ROM chip have Yaffs filesystem. Phones with more than 512mb have EXT2/4
I can make little script for recovery and it format Yaffs to EXT4, but in real testing its no differences in performance. But I am not sure will be it stable or no. For me its not good idea.
Script will be look like that:
unmount("/system");
unmount("/data");
unmount("/cache");
format("ext4", ""MTD", "/dev/block/mtdblock4");
format("ext4", ""MTD", "/dev/block/mtdblock6");
format("ext4", ""MTD", "/dev/block/mtdblock1");
Its up to you the ace got 256 mb ram if im not wrong
With EXT4, there is no real performance increase.
The only thing you're notice is;
faster boot times
shorter launcher redraw time
No lag what so ever when internal storage runs low
Disadvantages;
File system needs to be converted back to yaffs2 before flashing a rom via recovery. If not, phone will get stuck on LG splash screen.
Hmm ok and what phone are you using now? The
"Both Galaxies are protected by CORNING® GORILLA® GLASS "
got me interested
bs828 said:
Hmm ok and what phone are you using now? The
"Both Galaxies are protected by CORNING® GORILLA® GLASS "
got me interested
Click to expand...
Click to collapse
What phone I use doesn't matter
Just popping back randomly coz I am bored.
bs828 said:
Its up to you the ace got 256 mb ram if im not wrong
Click to expand...
Click to collapse
I am talking about ROM-memory-chip, not RAM. We have 256mb RAM and 512mb internal memory.
P.S. ACE have 392mb - RAM
oops miss read
miroslav_mm said:
I am talking about ROM-memory-chip, not RAM. We have 256mb RAM and 512mb internal memory.
P.S. ACE have 392mb - RAM
Click to expand...
Click to collapse
*Ace has 278MB of RAM
Yaffs is there for a reason. I don't know much about performance, single- or multithreaded, but yaffs takes care of flash wear while ext will happily write to the same blocks over and over again, shortening whole flash's life.
MrAndroid12 said:
*Ace has 278MB of RAM
Click to expand...
Click to collapse
No! 278 its available RAM. Like 180mb on IceCreamSwift. Memory chip on ACE - 392mb!
I am not sure but this looks promising.
My friend have galaxy ace with that Rom and benchmark is high. and I have optimus one
anyway,
I believe we need to just edit and write
/system ext4 system
/cache ext4 cache
/data ext4 userdata
instead of
/system yaffs2 system
/cache yaffs2 cache
/data yaffs2 userdata
to recovery.fstab of device sources and Let it compile Rom and Recovery and flashing it will be the
Result.
miroslav_mm said:
No! 278 its available RAM. Like 180mb on IceCreamSwift. Memory chip on ACE - 392mb!
Click to expand...
Click to collapse
Yep.
hmskrecik said:
Yaffs is there for a reason. I don't know much about performance, single- or multithreaded, but yaffs takes care of flash wear while ext will happily write to the same blocks over and over again, shortening whole flash's life.
Click to expand...
Click to collapse
It would take more than a devices useful cycle before the chip wares out completely.
I don't think anyone would use the same smartphone smartphone for 10 years+
hmskrecik said:
Yaffs is there for a reason. I don't know much about performance, single- or multithreaded, but yaffs takes care of flash wear while ext will happily write to the same blocks over and over again, shortening whole flash's life.
Click to expand...
Click to collapse
you don't need to care about this because modern flash memories always have wear levelling technique to prevent early wear out. and even withtout this technique it will took years to completely make the flash unwritable. there's a special version of ext4 which does not have journals to reduce flash wear
People who've received their Note 8s, could you check if you have UFS 2.1 or 2.0 storage? This was more of a lottery with S8 and S8 plus. See discussion here: https://forum.xda-developers.com/galaxy-s8/how-to/ufs-2-0-2-1-identify-flash-chip-s8-t3601656
Basically, you need to run
Code:
cat /proc/scsi/scsi
in Terminal app and report what you see? The post above explains how to interpret it as 2.1 or 2.0. Also please include your country and model number (US snapgdragon, etc.)
Looks like mine has 2.1 ... (KLUCG4J1ED-B0C1) is what it shows . I have a Verizon Black model
I have 2.1 (KLUCG4J1ED-B0C1) also. T-Mobile black
mehdi_s82 said:
People who've received their Note 8s, could you check if you have UFS 2.1 or 2.0 storage? This was more of a lottery with S8 and S8 plus. See discussion here: https://forum.xda-developers.com/galaxy-s8/how-to/ufs-2-0-2-1-identify-flash-chip-s8-t3601656
Basically, you need to run
Code:
cat /proc/scsi/scsi
in Terminal app and report what you see? The post above explains how to interpret it as 2.1 or 2.0. Also please include your country and model number (US snapgdragon, etc.)
Click to expand...
Click to collapse
I have the 2.1 UFS chip
Edit: US - TMOBILE - BLACK
razor237 said:
Looks like mine has 2.1 ... (KLUCG4J1ED-B0C1) is what it shows . I have a Verizon Black model
Click to expand...
Click to collapse
VZW Black and not surprisingly same storage model. Glad to have UFS 2.1
This model is def UFS 2.1 - http://www.samsung.com/semiconductor/products/flash-storage/ufs/KLUCG4J1ED-B0C1?ia=2413
AT&T Black model.
It has UFS 2.1 as well.
TMobile, black, 2.1 here. Perhaps there's no lottery this time?
Sprint - Black - UFS 2.1 (KLUCG4J1ED-B0C1)
Kil4Thril said:
TMobile, black, 2.1 here. Perhaps there's no lottery this time?
Click to expand...
Click to collapse
Yea looks like its all 2.1 for note. But I wonder why they don't brag about it in their spec sheet
Deleted - Duplicate post
Sprint black ....
With the S8/+, all S8+ and Exynos S8's have 2.1.
jmshene said:
Sprint - Black - UFS 2.1 (KLUCG4J1ED-B0C1)
Click to expand...
Click to collapse
Same here.
UFS 2.1 speed test
Speed test for those of you that are interested. Note 8 with this memory: http://www.samsung.com/semiconductor/products/flash-storage/ufs/KLUCG4J1ED-B0C1?ia=2413
Read: 547MB/s, Write 215MB/s
This is a readout from unlocked version of the Note8 unbranded carrier free.
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 49488
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Well-known LUN ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 00 Lun: 49456
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Well-known LUN ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 00 Lun: 49476
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Well-known LUN ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Direct-Access ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 00 Lun: 01
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Direct-Access ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 00 Lun: 02
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Direct-Access ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 00 Lun: 03
Vendor: SAMSUNG Model: KLUCG4J1ED-B0C1 Rev: 0003
Type: Direct-Access ANSI SC
afkguy said:
Speed test for those of you that are interested. Note 8 with this memory: http://www.samsung.com/semiconductor/products/flash-storage/ufs/KLUCG4J1ED-B0C1?ia=2413
Read: 547MB/s, Write 215MB/s
Click to expand...
Click to collapse
Impressive!
N950U1 unlocked NA Snapdragon variant, UFS 2.1 confirmed!
Maybe it isn't NVFS, but it sure helps the Note 8 feel wicked fast after three years on the Note 4.