yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] jokersax11:
all of this would apply to ram only. swap and compcache could use the same idea to dynamically allocate swap but that is still a cache for programs. sorry if its confusing. simple way to explain. i want all the ram i can get but still use everything the phone has properly, like games and the camera.
[G1 Android Development] Dyonas:
Gotcha and understood. I see so many people say RAM and memory when they're referring to storage space sometimes that I want to scream but extra RAM on the G1 would be more than welcome. Hopefully others with the brains to make it happen can do it :D
[G1 Android Development] jokersax11:
actually anyone with a basic knowledge can help. mostly there are a couple things to developing a good idea.

first the concept.

then ideas on how to do it.

next a map or guide to what does what.

coding different parts

putting them together

debug and test

even if all you do is photoshop the ui or provide ideas it helps. once some different people get aboard this should be working sooner than you think.
[G1 Android Development] IConrad01:
Of the three options listed, the kernel script (via ksplice) seems like it would be the shortest route to functionality, but frankly it also seems a bit... well, hackish -- when compared to the virtual device allocation scheme. It would take a hefty re-write of the kernel, I suspect, to accomplish; but being able to resize various devices on the fly would be a good thing. Shrinking CompCache based on real RAM usage for example would probably speed up the phone under light loads.

Just thinking in text here.
[G1 Android Development] jokersax11:
personal i think its going to start simple(script or root app) and go straight to gpu shared on or off. choose and reboot. however i do not want to stop there like winmo did. someone could create a short kernel patch that checks for a service or script and gets value or defaults to standard method. then we would have to come up with how to manage the switch(realtime vs. reboot) ideally we would remap the memory from scratch and rebuild the memory management services to dynamically allocate the ram for all devices(128+ ram) as needed. we have a start, we know where and how to turn the gpu1 shared on or off. now lets make it more than a hack and work on how to make our phones better. btw this is not a waste of time. this extends to other phones and the future way to set up our phones from default.
[G1 Android Development] Geniusdog254:
The only problem with this is when the ram is divided, everything in it is cleared, thats why it is set at boot in the kernel. Think of it like repartitioning your SD. Now it would probably be possible have everything mapped to ONE big RAM table & then build something similar to a scheduler like BFS for RAM that would allocate it as necessary. This is messy though.

Just my $.02
[G1 Android Development] jokersax11:
well yes but it is possible to create shared memory through c++ http://www.go4expert.com/forums/showthread.php?t=8461

however i think the vm heaps has either a 6 or 16mb limit. anyways the service would basically do a memory patch over the kernel in realtime(like overclock) telling the gpu the memory is there all the time. meanwhile it allocates dynamic shared memory from the application memory for the gpu to read and write. meanwhile an app tied to a script would set the parameters and settings.
[G1 Android Development] IConrad01:
Okay -- I know ksplice works with perl; and I know that we can run perl scripts using the ASE .apk.

So... it seems to me that it /should/ be possible to use a patch that reverts the patched kernel back to the previous state, and a patch that switches the original state to the GPU1=0 MB state. From there, we could set up two scripts; one for GPU1-off and one for GPU0-on. Each would simply be an invocation of ksplice to input the specific patch (which would have to be stored on the sd card. [it would be safer if in the ext partition]).

We'd have to set up a secondary RAM device, rather than just adding it to the standard RAM pool... something like establishing it as a /dev/block/shm.

The point of all the above is that when you click on the GPU1-off script, it "reclaims" that RAM and gives you a device that's standard RAM. When you click on the GPU1-on script, it disables that device (forcing the reload of all programs using that RAM) and re-enables the GPU1 device.

Even better yet, the Android Scripting Environment program, much like GScript, supports desktop icons.

So -- very initially speaking, assuming we can get ksplice working on Android (which just requires a static binary, IIRC), we can get a simple pair of icons; one of which frees up the GPU1's RAM; and the other of which re-enables the GPU1.

Since the only times it's going to be "called up" are when a game is actively being played, or something similar, this should be a mostly-satisfactory route to begin with, before we can get into the whole scheduled/scaled script running as a daemon in the background.

Once we get /there/, then we can start looking at true virtual device allocations and shared memory and the like.

Although, I do have to say that I'm not entirely sure how comfortable I am constantly repatching the kernel. Definitely, we're going to want to recommend that people back up their original, unpatched, boot.img files!
[G1 Android Development] jokersax11:
IConrad01 i added your method to first post as it was a great start to this project. if you want me to rephrase just post what you want and ill change it. the only issue i might see is what geniusdog254 said it might unallocate the wrong thing and create a reboot. but some clever coding should prevent this.
[G1 Android Development] IConrad01:
Nah, that's all good.

There's an easy way to prevent it from becoming a reboot-able issue. Enable the GPU-space device as "swap". This could be done one of two ways; tell the phone that the new 8 MB RAM "device" is to be considered the /first/ swap device to be used, and just leave it "as is". The r/w times would be for true RAM. The other option assumes we have the latest CompCache (0.6+) -- as it allows for multiple instances of CompCache. The theme here should be obvious.

Either way, the result is that only swappable pagefiles would be lost when the device is turned back into GPU memory. No system-vital memory would get tossed. Seems simple enough to accomplish, perhaps. But then again, I Am Not A Programmer.
[G1 Android Development] jokersax11:
ok so what are the alternatives to ksplice for the swap device change. since we could make it swap/compcache anyways is it possible to change on the fly like the way overclocking widget does?
[G1 Android Development] IConrad01:
Since it seems there's little activity in this thread, I thought I'd share:

There is a debian armel package for ksplice.

( http://packages.debian.org/squeeze/ksplice )

This is ARM-compiled. We would simply need to cobble together a script which invokes ksplice properly. I myself know nothing of how this would be done.

Usage example of ksplice here:

http://www.ksplice.com/example-update
[G1 Android Development] Ohsaka:
Looks pretty simple. You just need a working kernel build environment. Anyone got one of those laying around? :) I have wanted to do that for awhile but am too lazy to set up a linux VM, lol.
[G1 Android Development] svxdriver:
Hell yeah!!

Im not much good for this project other then willingness to try betas and give feedback, but I'm excited to see where this goes.. It would be great to reclaim the ram being used from the system when you aren't using anything that needs it and use it for what you are using. Has anyone contacted one of the devs that have been modifying the kernels and ask them if they could try building it with the ksplice functionality?? I would think one of them would be happy to build it so you can start playing with it. Wish I could help more on it, but this is a little above my head, but I will be following this thread and learning what I can as i go.. Good Luck!!
[G1 Android Development] Iman07:
did we give up on this already?
[G1 Android Development] Shatterv2:
Keep this up.
[G1 Android Development] tutech:
Any further progress made on this?
[G1 Android Development] r00ktard:
Or you can just buy one of the newer devices that will be released in the future that has more RAM. lol! that is the solution ... more ram of course.

in the mean time you can get a my touch or droid. the G1 will become obsolete soon.
[G1 Android Development] :
great idea...
[G1 Android Development] Ace42:
Exactly!

Someone with some good-sense :cool:

G1 is already obsolete, ya better start saving up those pennies for the new line of 2.0 devices from htc. I know im gotta get rid of thise ol-Gphone for a fancy looking thing, lets say Legend? Maybe nexus but i like the name legend.:D

G1= Oldskool

Newer= New school/up-to-date
[G1 Android Development] IConrad01:
1) The Magic is basically the same thing as the Dream.

2) Droid... yeah. Because everybody has the spare cash laying around to break their contract every year that comes by.

That's just brilliant.
[G1 Android Development] Ace42:
Droid doesnt have that "Hero" power that im refering to, it only does up to 600Mhz. You need that HTC feel for the phone to be of quality running on the nations fastest network..Sprin..Koff..koff

I dont understand why they cant put more ram, phone parts arent that expensive. I think i-phone cost about 190 or so to make.
[G1 Android Development] jubeh:
Cheaper parts mean higher profits. You just realized all companies are evil. Have a good day.
[G1 Android Development] Hiker.Chan:
Wow, that sounds wonderful.

I can't wait to see the nice future of my G1.
[G1 Android Development] iPhone iWing:
ok how bout you all get a new devices while these guys or guy gets the scripts wrote and all summed up, you will all being using them on that pretty new device. ya, you guys should remember that the kernel doesn't completely change just because of hardware. Imagine having a device with 288mb of hardware ram and adding a patch or script to allow even more ram. There you go!! :D
[G1 Android Development] ryanolson7:
everyone talking about just 'buying new devices' are limiting theirselves to deal with restricted ram access.. lets say you get a new device with 300 mb ram, which is a lot but if things are done the same way you'd only get to use like 200mb.. if we can get all this working it'll make our phones faster and more efficient with ram allocation. you may not see a benefit using this on a phone such as the droid but one day it might make a difference even on that phone! we will especially see the difference to the g1 users out there.. lets do this guys!
[Touch HD General] jigners:
I felt the need for this thread as i have posted the solution i found (somebody else may have discovered this) in many of the Leo (Manila 2.5.1919) thread, but some people fail to read and kept asking the same question over and over. Hence in a way i feel i can help the ROM chefs L26HDLEOV2, Dutty LeoR5, Miri R10 etc.,

I use microsoft myphone to back up and restore contacts and calendar entries. the strange thing is, I found this entry while editing a contact

1. in Manila, open a contact

2. click edit contact,

3. scroll down to the very bottom and click "more" (you'll be brought to the windows contact editor)

4. click "Notes" - a strange entry is noted - "<<FDMID>9895967</FMID>" - I simply deleted this, and VOILA! i could add this same contact now to favorites without crashing!

i think i should get a copyright for this discovery!! LOL:D

this might only be applicable to people who are testing Manila 2.5.1919 and using microsoft myphone to backup contacts and calendar entries.:p

found a much quicker way to delete this note string "<<FDMID>9895967</FMID>". log in to microsoft myphone in PC and delete the note string to any contacts which contains this.
[Touch HD General] d.cortez:
this solution was also reported in PhamQuang thread for v 62 or 63 as well.
[Touch HD General] noris08:
i disagree with you - i use L26 V2 rom and i also have that string on my favorite contacts notes and i can add or remove favorites with no problem.

more than that - i did wtaht you suggested. i deleted that string from my favorites notes (on phone and on pc outlook), soft reset the phone, delete a favorite contact, add again, sync and guess what?

the string is back on place:confused:

so it must be something else
[Touch HD General] ardsar:
This string is being added by Manila to allow it to identify favourates and link it to any facebook profiles you have. This string will always be created once added to your favourites.

THis string format could have changed between builds, resulting in some users devices hanging.
[Touch HD General] noris08:
you probably are right, but my point is that, as far as i am concerned, this string doesn't cause the crash

i had a stock rom which originaly created my favorite contacts

since then i flashed several roms and i restored my contacts every time with my pc outlook

i had not one single crash caused by adding favorite contacts no matter waht rom i installed

this is the reason i said "it must be something else";)

my 2c
[Touch HD General] Fallen Spartan:
I've moved this to general discussion forum
[Touch HD General] jigners:
thanks Rick! Good day!
[Touch HD General] jigners:
yes, perhaps this "something else" is unique to my method of backing up contacts. as i mentioned in the first post, i only backup using microsoft myphone.

BTW, there is another quicker way of deleting the note string, to those who use myphone. I logged on to myphone and deleted all the contacts which contain the note string. and now i can sync with myphone and add favorites with no crashing
[Tilt, TyTN II, MDA Vario III General] trav2001:
I have been combing the forums and searching like crazy for a way to get my MMS to work on T-Mobile USA with my ATT Tilt. It has the stock WM 6.1 on it.

Can someone PLEASE help me and NOT refer me back to searching? I'm about ready to get rid of the phone
[Tilt, TyTN II, MDA Vario III General] Ronio777:
Have you tried using the T-mobile configurator?

http://tmobileuspublic.wdsglobal.com/

There was a Cab floating around called tmobyjoe599 that could also set all the data settings. It appears to be here.. http://xdaforums.com/showthread.php?t=395203
[Tilt, TyTN II, MDA Vario III General] ChumleyEX:
or http://xdaforums.com/showthread.php?t=565522
[Tilt, TyTN II, MDA Vario III General] trav2001:
Ya, non of that seems to work. I'm sure that someone out there must have gotten this to work...I've had other phones from other provides and didn't have an issue with MMS...
[Tilt, TyTN II, MDA Vario III General] JimmyMcGee:
Check to see that you have 3G signal. No 3G no MMS. Also, I'm not sure but does the Kaiser3 (TILT) even support the 3G Frequency of T-Mobile?

Also, SINCE you are using a Stock At&t ROM I have a sneaking suspicion that you won't get an At&t Optimized ROM to work on another Network. Maybe you should flash a Custom ROM and see if that helps.
[Tilt, TyTN II, MDA Vario III General] trav2001:
Ya, i've tried that too, and I can't even get the hardSPL to install...SOOOO i think I'm stuck with no MMS : ( I get the big "E" on my screen for the edge network of T-Mobile.

EDIT: Nevermind, I FINALLY got it, with the help of T-Mobile Configuration tool...
[Tilt, TyTN II, MDA Vario III General] ChriL:
moneyies?

do you have to pay for the configuremyphone thing if you have unlimited texting?
[myTouch 3G, Magic Android Development] dills84:
this looks good. anyone try it yet? noticable speed?
[myTouch 3G, Magic Android Development] Mazziota:
Rom doesn't work with sdcard choose or sdcard update

E: No signature (2 files)

E:Verification failed
[myTouch 3G, Magic Android Development] dwang:
how about reading the post. I specifically said this is fastboot only.
[myTouch 3G, Magic Android Development] supa2001:
I got error: remote.
[myTouch 3G, Magic Android Development] DOHCtor:
I'm going to fastboot this later tonight
[myTouch 3G, Magic Android Development] tudor00:
That's great! Please make it flashable and please NEVER add app2sd, we don't need that.

Did you use the last rom provided by HTC?
[myTouch 3G, Magic Android Development] DOHCtor:
agreed. a2sd is pointless for us.
[myTouch 3G, Magic Android Development] supa2001:
How did you guys flash it? It kept giving me the same error.

Do I need engineering SPL?
[myTouch 3G, Magic Android Development] Slotrat:
I love it! :D

Wifi Tethering works with aNetShare (available on market).

Lets just hope someone can fix HTC_IME3 this weekend so we can get it running on Android 1.6. That's the only thing I'm missing now.
[myTouch 3G, Magic Android Development] kchau:
have you considered adding bfs to this?
[myTouch 3G, Magic Android Development] dwang:
Cool thanks, I've updated the OP with that info.
[myTouch 3G, Magic Android Development] dwang:
There are lots of other roms with bfs. I'm going to try to keep bfs out of this one and keep it as close to stock 1.6 as possible.

Its quite fast without it.
[myTouch 3G, Magic Android Development] tudor00:
@dwang: would you be so nice to make it flashable? I am not familiar with fastboot at all. Is it a lot of work for you to make it flashable?
[myTouch 3G, Magic Android Development] spyz88:
Give the guy a break. He's doing this on his spare time for FREE. When he gets around to making it flash-able he will.

God, some people are not appreciative at all..

Fastboot info (post 4):

http://xdaforums.com/showthread.php?t=555724
[myTouch 3G, Magic Android Development] tudor00:
Arrogant bastard, I was being extremely polite when asking, I don't see why I would get such aggressive comment like yours. Go to hell

I am just very admirative of this work and eager to try it. It would have been no worries getting a 'NO' answer.
[myTouch 3G, Magic Android Development] dwang:
I'll try to get a non-fastboot version up over the weekend. This is my first rom so i'm still in the learning process.
[myTouch 3G, Magic Android Development] tudor00:
Thanks so much for the reply. Good luck and thanks for your work.
[myTouch 3G, Magic Android Development] tudor00:
Do I have to hit 'enter' between these two lines in the command prompt?

fastboot flash boot boot.img

fastboot flash system system.img

edit: I get the following after hit 'enter' after the first line

'sending 'boot' <2560 kb>... OKAY

writing 'boot' ... INFOsignature checking....

FAILED <remote: signature verify fail>

What's wrong? Is it because I don't have an engineering SPL?
[myTouch 3G, Magic Android Development] dwang:
yeah you need the engineering spl. I don't think the spl that shipped with the magic will work.
[myTouch 3G, Magic Android Development] wolf5150:
Error: "cannot remove ' *': No such file or directory"

Formatted SD card, 1.5 booted up but would not allow app installations -

Flashed 1.6 and all is well, thanks for everything dave
[myTouch 3G, Magic Android Development] jtc442:
home screens

newbie, sorry, but sort of confused i guess. with this rom, it said something about 5 screens. i guess i was thinking 5 home screens. how do i get more than the 3 screens that are there? someone please help. if this is in the wrong place, i apologize now, but didnt know where to post it, since this is the rom i just installed.
[myTouch 3G, Magic Android Development] dwang:
what are you talking about? There are 5 home screens.
[myTouch 3G, Magic Android Development] dwang:
v1.6 is out

v1.6 http://drop.io/p1knm9f

* Fix a2sd issues for real this time.
[myTouch 3G, Magic Android Development] dwang:
there is nothing in userinit.sh. You put whatever you want.
[myTouch 3G, Magic Android Development] jtc442:
im only getting 3??? am i doing something wrong?
[myTouch 3G, Magic Android Development] dwang:
You tell me..
[myTouch 3G, Magic Android Development] jtc442:
home screens

i dont know, thats why im asking. like i said, im new to this, i wiped, and installed the rom, but only 3 screens? i apologize if im offending you or something, but im just asking. ive never messed with android until about a week ago, just asking for some help.
[myTouch 3G, Magic Android Development] dwang:
There's a Q & A section for asking for help. This board is intended for people with a certain amount of knowledge. When I put out my ROM, I'm assuming people already have some basic knowledge of rooting and installing custom roms.

Seems like you are still running your original ROM, since I'm 100% certain that my rom has 5 home screens.

Were you able to successfully root your phone? Have you installed other custom ROMs before?

Please do some reading before asking questions.
[myTouch 3G, Magic Android Development] jtc442:
yes, my phone is rooted, and tethered, used unlockr. have installed several custom roms before. had a different rom installed, the first one that was out when donut was first released, then i got on tonight, was reading about how fast yours is, which i give you that, it is very fast, compared to what i did have, i just dont have the 5 home screens. i love this rom, just wondering if maybe it is a phone setting or something.
[myTouch 3G, Magic Android Development] dwang:
It comes with 5 screens by default. Are you sure you are running my rom?

Go to settings -> about phone and see that the kernel version says

"dwang@dwang-laptop"

If you are running my ROM, I would then try a wipe.

Are you sure you don't have another "home" application running, like Open Home, dxtop, ahome, etc?
[myTouch 3G, Magic Android Development] kchau:
when layar3d comes out, will the memhack not allow it to work?
[myTouch 3G, Magic Android Development] jtc442:
installed the 1.6, 5 screens now for some reason. dont know what happened with the 1.5??
[myTouch 3G, Magic Android Development] dwang:
I saw your edit. If you read my previous posts, you can see that I'm an extremely helpful person.

However, if somebody comes out and says such and such doesn't work and doesn't give any other information besides that, how am I able to help?
[myTouch 3G, Magic Android Development] jtc442:
thats why i said i am new, and i installed your rom, but i was only getting 3 screens. i didnt really know what else to put?? i just know the rom installed, but only 3 screens. i have no clue why? but i saw you released 1.6, didnt think it would help, but wiped and installed it anyways, and it worked. i guess a miscommunication or something. i wasnt trying to be a jerk, but the way you came off to me at first hit me wrong i guess, since i was only asking why only 3. anyways, i love this rom, its working awesome now, very fast!! was getting tired of my phone laggin with everything. dont have that prob now!!
[myTouch 3G, Magic Android Development] dwang:
Ok.. I'm happy you are enjoying my ROM.
[myTouch 3G, Magic Android Development] jtc442:
once again, i apologize for my (edited post)!! just think what you were saying and what i was saying all came out the wrong way or something and we misunderstood! thank you for your work!! its great!!
[myTouch 3G, Magic Android Development] supa2001:
Thanks for making this! Love it.

1.5 is faster than 1.4!

Not gonna install 1.6 since I don't use a2sd.
[myTouch 3G, Magic Android Development] jtc442:
update

i just figured out what it was, for whatever reason. when i clicked on the link for the 1.5 download, it has the launcher.apk file there also. i installed the rom, then after that, i installed the launcher. that is what caused me to only have the 3 screens. not sure what the launcher was for, so i thought i needed to install it, since it was there.