Has anyone successfully opened up the tytn rom for modifying? Is it possible to change the cache size the way the BA has been done. I would like to see the ability to change the default cache to 16MB or even 32MB for performance boost.
axiom said:
Has anyone successfully opened up the tytn rom for modifying?
Click to expand...
Click to collapse
We are trying hard, see other posts in this forums and read the wiki...
axiom said:
Is it possible to change the cache size the way the BA has been done. I would like to see the ability to change the default cache to 16MB or even 32MB for performance boost.
Click to expand...
Click to collapse
BlueAngel has 128Mb of ram which can be used as paging pool and ramdisk... that's why after modifiying the pool size you end up with less ram (77 visible MB in helmi 1.3.2 with 16Mb pool for example).
TyTN has only 64Mb of RAM, if you take 16Mb for paging pool and 32Mb for ramdisk you'll end up with a device with 16Mb of ram... which would make it quite unusable
At the moment we don't have the tools nor the knowledge to make something like what mamaich has done with blueangel in the Hermes... but it's just a matter of time
I see. But I find the ram disk useless at anything over 12 Megs, so there would be enough room left over for additional Ram. But then that's just a personal preference.
I mean, the overall cache might not need to be 16MB, 8MB might do what 16MB does on the BA. I guess we really won't know until someone cracks it open.
In any case, I would be willing to give up ram disk for increased performance.
interesting ... shouldn't the TyTN perform much better as other devices? (pointing to the CPU ... where are the 400 MhZ?) but i agree ... get lost of some MB for performance increase ... i am with you
Someone should PM mamaich to ask for his kind support in this matter
I will ask him about this and get back with his answer.
Here is mamaich's response to this.
It is possible to adjust pool size on any WM5 device, but I don't know is it possible to flash a patched ROM to TyTn. And typically the OEM made tests to adjust pool size for max speed.
The method of looking for addresses is similar to method I've described in Universal topic
Click to expand...
Click to collapse
Well does anyone have any insights to this? Are we able to flash a patched ROM on the TyTn yet?
axiom said:
Are we able to flash a patched ROM on the TyTn yet?
Click to expand...
Click to collapse
We are close to but not able yet, see method two here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
If anyone can help on this is very welcome!!!
Related
Can anyone tell me how the size of the page pool affects
1. Stability
2. Speed
3. Available memory after a soft reset.
With my limited info, I believe it to be the case that with a *higher* page pool, you get more OS stability, more speed, but less available memory for other apps to run. Would that be correct?
it depends
some ppl like Big PP
some ppl do not
Huh? I'm not asking what people like. I just want to know what effect a larger or a smaller page pool has on those 3 things. So, no one knows?
Well i am back at WM5 now. Made a 2MB pagepool rom.
Stable
Fast
Free memory after boot : 36MB
imparator said:
Well i am back at WM5 now. Made a 2MB pagepool rom.
Stable
Fast
Free memory after boot : 36MB
Click to expand...
Click to collapse
WOoowwWw thats what i call free ram!
cand you do that on touchv3?
Or you can give us a guide how to do it??
imparator said:
Well i am back at WM5 now. Made a 2MB pagepool rom.
Stable
Fast
Free memory after boot : 36MB
Click to expand...
Click to collapse
So, you claim that a very low p.p. will increase both stability and speed? Why do we have larger p.p.'s then?
no,large page pool,more speed,small page pool ... guess what ) and dude,wm5 sux...
zeroed said:
no,large page pool,more speed,small page pool ... guess what ) and dude,wm5 sux...
Click to expand...
Click to collapse
Please explain why WM5 sux
in my opinion a big page pool is not really faster.
ok, some apps start faster but the free ram is too low.
with lots of free program memory you can keep running all your important apps and you don't have to close and start them every time.
so with always opened apps your daily usage of your ppc should be much more fluider than with a big page pool and only 1x mb free program memory.
i hope i could explain it with my sucking english
You do make a point, but most people prefer to close their apps all the time.
Its like with windows desktops, some people have 50 windows open in their taskbar and some only 2 or 3.
If you are one of the people that like opened apps your right, I like fresh app starts so I prefer a nice 8mb pool size
Kaoh said:
You do make a point, but most people prefer to close their apps all the time.
Its like with windows desktops, some people have 50 windows open in their taskbar and some only 2 or 3.
If you are one of the people that like opened apps your right, I like fresh app starts so I prefer a nice 8mb pool size
Click to expand...
Click to collapse
hehe, i have two LCDs connected to my pc, so that everything fits onto the screen. so i am a 50 windows guy
for more details i refer all of u to this post
http://forum.xda-developers.com/showthread.php?t=321912
Hi Folks looking forward to the New Elite ROMs that will be coming out soon.
Just wondering if anyone can tell me a method for changing te pagepool.
It was quite easy to do on the Universal either by editing the ROM or doing it dynamically.
With 0 pagepool the Uni was more responsive even though it was at the expnse of RAM (I had the 128MB upgrade so it didn't really matter)
Any info would be great. A step by step guide would be even better
From the Diamond discussion on this nothing has been sorted yet, I'm guessing the two processes will be similar, given the similarities in the devices
Dave
Developers please help. It seems that our Nexus Ones are restricted to only 180 MB RAM as their is a bug in the kernel. Can anyone make or compile a RAMhack that can open up the extra 100-150 MB RAM. The below is an excerpt from another thread under the Nexus One - Nexus One forum here in XDA. Im wondering how much faster this thing will fly. It seems a MEMhack such as the one they used to free the 10MB for the dream might be the same approach. Apparently Google will patch this but there is no ETA on the next update.
A "memhack" kernel update in the next Nexus One OTA should give us an additional 100-150MB RAM. Who wants to try to compile a kernel that does this now?
reserved for space
flak0 said:
Developers please help. It seems that our Nexus Ones are restricted to only 180 MB RAM as their is a bug in the kernel. Can anyone make or compile a RAMhack that can open up the extra 100-150 MB RAM. The below is an excerpt from another thread under the Nexus One - Nexus One forum here in XDA. Im wondering how much faster this thing will fly. It seems a MEMhack such as the one they used to free the 10MB for the dream might be the same approach. Apparently Google will patch this but there is no ETA on the next update.
A "memhack" kernel update in the next Nexus One OTA should give us an additional 100-150MB RAM. Who wants to try to compile a kernel that does this now?
Click to expand...
Click to collapse
it's really only a matter of time on this ... once the 2.6.3x kernel is perfected for the mahimahi HW ... we'll get it. Think tank not really necessary ... as it's in the works.
~enom~
Ummmm. I thought that was the goal here:
http://forum.xda-developers.com/showthread.php?t=616383
Doubt we need the 2nd thread.
That is correct that is the goal however, until the .32 kernel is perfected is there a way to hack the current Kernel like it was done for the Dream to get the extra memory back. I am just making a suggestion. I know the only issue with the .32 kernel is the proximity sensor fails from what I have read. Can this be confirmed?
All sensors work fine with 2.6.32. Google put the sensor code in git a few days ago. I am having issues with the camera, but another person in the kernel thread said he got it working, but I can't confirm it yet.
As for the memory hack, I do not know how to do it, but the memory map and allocation are in <kernel dir>/arch/arm/mach-msm and the two files are line 959 in board-mahimahi.c and board-mahimahi.h has the memory map table breakdown.
Edit: I just got the camera working
Wont enabling that ram for program use affect the GPU(Like on the G1)?
~~Tito~~ said:
Wont enabling that ram for program use affect the GPU(Like on the G1)?
Click to expand...
Click to collapse
No, there is ram that isn't even allocated in the nexus unlike the G1. You would just move everything around and nothing would be adversely affected (in theory).
staulkor said:
No, there is ram that isn't even allocated in the nexus unlike the G1. You would just move everything around and nothing would be adversely affected (in theory).
Click to expand...
Click to collapse
Thats a bug google said would be fixed and more ram would be avail for the Nexus.
According to swetland, the only way is via the .32 kernel due to the problems caused by the 1:1 requirement. Otherwise it sounds like things go bad very quickly.
swetland said:
Roughly 220MB is available to userspace in the shipping build (ERD79).
Quite a lot of memory is dedicated to the radio firmware (41MB), dsp firmware (32MB), display surfaces (32MB), gpu (3MB), camera (8MB), a/v buffers (41MB), and dsp buffers. Much of this needs to be set aside for these specific tasks due to hardware requirements of very large physically contiguous buffers which can be difficult or impossible to obtain after boot once the physical memory space gets fragmented.
The big limitation though is that the Linux kernel needs to do a 1:1 physical:virtual map of general purpose memory used by the kernel and userspace (which excludes the special purpose stuff described above). This eats into the available kernel virtual address space, which is also needed for cross process shared memory used by the binder, etc. Run out of virtual memory and things get unhappy.
In 2.6.32, HIGHMEM support for ARM will allow us to avoid this requirement for a 1:1 mapping which will allow us to increase memory available to userspace without running the system out of virtual memory adddress space.
Click to expand...
Click to collapse
bofslime said:
According to swetland, the only way is via the .32 kernel due to the problems caused by the 1:1 requirement. Otherwise it sounds like things go bad very quickly.
Click to expand...
Click to collapse
Thanks for the details. I wasn't aware of what was causing the problem before reading this. This makes a lot of sense.
It puzzles me that my TG01 boasts a healthy sounding 256MB of RAM, but often all that is available when all apps are terminated is no more than 80MB free. Having a look at the background processes, these seem to account for about 40MB which would suggest there should be about 200MB free at worst! What is all the "spare" memory preoccupied with? Is there a utility that will give a breakdown of how the RAM is allocated?
Why is this a problem? Because, more often than not, I get an error using Internet Explorer that there isn't quite enough memory to run Adobe Flash.
dont use IE lol ... IE memory managment is one of the things they fixed in 6.5.3 ... when i had 4 tabs open in opera and had 35mb free , i started to panic too , but then i opened 14 tabs and i still had 20mb+ free , so its all good , its quite dynamic
A program call CleanRam will help you get more Ram spaces.
Go here for more info
http://www.htcaddicts.com/?id=110
Ram Problem
yeah i agree with you! on the htc touch hd, it had 288 mb of ram, and after a clean soft reset and touchflo 3d running, it had 199mb of ram left.
on our TG01 it has 256mb ram, an after i installed touchflo 3d 2.5, i have 58mb of ram after soft reset. there Is so little to use.
This makes no sense
There has to be something we are missing. how do we free up more of this memory? What is it being saved for that we cannot even seeit?
Guys wait for clean roms.
I am sure our chefts will cook us some awesome roms soon.
BTW I am anew proud owner of TG01 (no voice calling quality problem.)
Currently with rogers canada
even with the ability of flashing clean roms, there still seems to be big problemss with ram. perhaps toshiba sold their devices with false specs?
its fine aslong as u avoid the sense roms
and be sure to softreset every few days
souljaboy said:
its fine aslong as u avoid the sense roms
and be sure to softreset every few days
Click to expand...
Click to collapse
good point but sense has good eye-candy
what is the ram on a clean 6.5 rom with titanium?
olyloh6696 said:
good point but sense has good eye-candy
what is the ram on a clean 6.5 rom with titanium?
Click to expand...
Click to collapse
Memory:
Storage: In Use – 38 MB Free – 224 MB
Programe: In Use – 118 MB Free – 87 MB
Per my 6.5 'clean' ROM - link in signature below....
Hi all. Today i have disassemled my Diamond2 (I have looking for reason why it have 288mb of RAM)
And found interesting thing:
Diamond2 have only 1module of memory, it's Samsung (I have recorded markers on the chip but have lost the papper.. ****)
i have COMPLETELY disassemled the phone, i found only ONE module of ram (For example my previous phone had two pieces)
So i think HTC did this:
They merged nonvolatile slow 1024mb module for:
1)512mb for internal storage
2)288mb for RAM
3)Anoter 224mb has been hidden
Its explains how HTC got 288mb for RAM, also explains why Diamond2 3(!)times slower than SE X1 in memory bandwith benchmark (nonvolatile memory not so fast as traditional RAM module).
So i think its possible to get more RAM by editing rom's memory mapping. Actually i can't do it by myself, but is there someone who can do it? I can test "New gen roms" in my spare time
P.S. Eventually we can just pump some MB from Storage (Are you need so much?) to RAM (You definitely need it, especially when use rom with Manila2.5)
P.P.S. Why i think its 1024mb module? Because i never ever seen memory chips like 768mb
good idea.
sadly that I don't know any thing about technics.
looking forward that some guys will make it.
BUMP.
I would love to see this come about!
The module is:
SAMSUNG 967 KBY00N00HM-A448 GML215A7.
Checked with google, didnt find how large it are, but its really nonvolatile memory, also very cheap
Interesting
+1
I always wondered about this. Would be nice if someone could pull this off. Mine starts up with only about 70mb free (uggggh) and slowly but surely goes down to around 58 where it finally seems to stable out at.
Interressed too !
that's quite some smarts digging this up!
will keep checking here for the holy grail of more memory...
I only wish that its possible to do it.
we all are much interessted , but search the developer... i dont know it if works, I mean the topaz is already 1year old , i can't believe that nobody have try this already...
but i hope =D
maybe a radio update will do the trick, like it did on the HD2
Possible beginning of a solution
If it is a 1024MB chip then maybe they simply laser cut a connection somewhere giving access to the rest of the available memory.... Like AMD did on the old Athlon chips to lock the multiplier.
If this is the case then all that's needed is a graphite pencil and the location of the cut connection and we're in business!
except that AMD CPU was on a large peace of PCB, and the connection was easily in sight, while here we're talking about a possible 65 nm technology memory chip completely encapsulated. good luck using a pencil on that. sorry I'm such a show stopper, but it's gotta be somewhere else.
This is a memory module, not an old athlon CPU
Have found a little guide from Loox device:
1) Patch nk.exe ("ulRAMEnd" must read value from ROMHDR, not an constant)
2) Patch nk.exe (Dont let "IPM-functions" in nk.exe rewrite registers in memory controller and activte additional RAM partitions.
3) Change "ulRAMEnd" in ROMHDR, XIP partitions.
4) Edit "OEMAddressTable" in nk.exe.
Just realized, we can try to change "MainMemoryEndAddress" in nk.exe (S000 file). It works for Kaiser/Polaris/Niki, gains 16mb of RAM
This is Great!!! If there is a possible way to do this then our TD2's will run much better and faster
and then if only we can overclock damn processor...
Have checked situation about HD2 hidden ram and found that it actually same with D2 - HD2 also have only one memory module, it doesnt have real RAM memory too.
So it was possible to resize RAM partition by flashing new rom and radio(?).
So i 100% sure it can be done on topaz.
(By the way i think Diamond, TP and Rhodium affected too cause they all got very slow RAM with strange size)
I dont have PC so i cant do it by myself
So our hope is cookers only, or someone like Olinex
P.S. Can someone send me nk.exe from HD2 original and new (With unlocked RAM) roms?
Interesting find! I'm following this with excitement hopefully someone can do something about this... but then thinking about it isn't some of this extra RAM saved for hard resetting by the bootloader?? Getting rid of this will stop that or am I confusing this with the ROM space?
Tim4 said:
Have checked situation about HD2 hidden ram and found that it actually same with D2 - HD2 also have only one memory module, it doesnt have real RAM memory too.
So it was possible to resize RAM partition by flashing new rom and radio(?).
So i 100% sure it can be done on topaz.
(By the way i think Diamond, TP and Rhodium affected too cause they all got very slow RAM with strange size)
I dont have PC so i cant do it by myself
So our hope is cookers only, or someone like Olinex
P.S. Can someone send me nk.exe from HD2 original and new (With unlocked RAM) roms?
Click to expand...
Click to collapse
You should also post this in the HD2 ROM Development thread, hopefully someone will send you the files.
Also, this thread is getting more and more interesting! I hope you can come up with something!
Best regards
it isn't some of this extra RAM saved for hard resetting by the bootloader?? Getting rid of this will stop that or am I confusing this with the ROM space?
Click to expand...
Click to collapse
Nope, hard-reset will just delete all files on main storage that doesnt have "ROM" marker. Its the only thing it does and doesnt requires extra ram. (I think so, may be i wrong )