Related
i want to put a 3.2 mega CCD in my imate PDA2K. does any body has any idea about this kind of upgrade
i have no idea how you would do that. but if you manage to put one in. tell us about it!
3 factors
1 legcompatible chip is required and as chip manufactors dont follow some std which leg is power which is data which is address..... not to mention how many legs and even size of chip is used
2 electrical protocol compatible chip is required protocol to even tell the cpu what it is and what services it support
3 driver used for the cam and blocking of the old driver as if the old chip use another driver the rom will not boot so a custom rom with the new driver would have to be cooked
end of the day in most cases more expensive and troublesome then buying a new pda..
The Galaxy S has a touchscreen that supports 10 point multitouch.
But you can only use 5!
For some reason Samsung decided to only enable 5 point multitouch, but the driver still supports 10.
You can increase the points tracked by a simple adjustment in the driver:
in the file: /drivers/input/touchscreen/qt602240.h
change:
Code:
5277: //#define MAX_NUM_FINGER 10 // Maximum possible fingering
5278: #define MAX_USING_FINGER_NUM 5
to
Code:
#define MAX_USING_FINGER_NUM 10
And in the android source at:
Code:
froyo/services/java/com/android/server/InputDevice.java
Set max_pointers to 10.
No, atmel maXtouch doesn't support unlimited touches:
http://www.atmel.com/dyn/resources/prod_documents/9530S.pdf
Why would you use 10 fingers on a 4'' screen?
Imagine, ten fingers on the screen. I think you are simply not able to move around any of the fingers , but still cool that more fingers are supported by this amazing device.
The ATMEL chip in SGS actually supports unlimited multi-touch
Rawat said:
The AMTEL chip in SGS actually supports unlimited multi-touch
Click to expand...
Click to collapse
Nice. If I could just get 13 point multi-touch in a ROM/kernel my dreams would be fulfilled and I could stop flashing and get down to business.
opcow said:
Nice. If I could just get 13 point multi-touch in a ROM/kernel my dreams would be fulfilled and I could stop flashing and get down to business.
Click to expand...
Click to collapse
lol thats really funny as sh1t
LoL Galaxy for aliens users with 18 fingers. Byez
Sent from my GT-I9000 using Tapatalk
I think a few hundred thousand very precise and accurate touch inputs, and we might actually have a fingerprint scanner app that's not a spoof!
Having 10 points of multitouch can get rid of the multitouch gaming bug (that isn't present in CM builds for example), because having controls that freezes up each 10 seconds is really boring for me
we have to, each time that happens, remove our fngers from the screen and put them back on it, really annoying... test it with gangstar, nova, etc and you will quickly understand
10 is the actual max. It says so in the driver and in the datasheet.
Atmel maXtouch supports unlimited* touches.
*up to 10 simultaneous touch points can be tracked.
The_Double said:
10 is the actual max. It says so in the driver and in the datasheet.
Atmel maXtouch supports unlimited* touches.
*up to 10 simultaneous touch points can be tracked.
Click to expand...
Click to collapse
http://www.atmel.com/products/touchscreens/default.asp
Single-Chip Touch Solution for Small Screens
Atmel maXTouch microcontroller family sets the standard in capacitive touchscreen technology for smartphones and small-format devices, providing the industry's highest-performing, lowest-power multi-touch components. maXTouch microcontrollers feature Atmel patented charge transfer technology which enhances the traditional approach to mutual capacitance solutions and combines all aspects of advanced touch sensing onto a single chip:
Unlimited touches
Low power consumption
Fast response — completely redraws screen every 4/1000 of a second (4ms) to eliminate recalibration issues
Click to expand...
Click to collapse
Rawat said:
http://www.atmel.com/products/touchscreens/default.asp
Click to expand...
Click to collapse
I usually find datasheets more reliable than advertisements.
opcow said:
Nice. If I could just get 13 point multi-touch in a ROM/kernel my dreams would be fulfilled and I could stop flashing and get down to business.
Click to expand...
Click to collapse
+1 internets for you sir
well its nice to know ... would be useful on the galaxy pad .. or something bigger ... Like a touch table
edit : my bad .. galaxy tab
This is a nice little mod
Sent from my GT-I9000 using XDA App
Rawat said:
The ATMEL chip in SGS actually supports unlimited multi-touch
Click to expand...
Click to collapse
according to the PDF it only supports 10 concurrent touches in real time.
Can't find the "drivers" folder! Am I doing something wrong?
That data sheet is for mx224, and the one in Galaxy S is mx1224, but it's probably from the same family, and has 10 touch points.
I want 195.2 touch points
I think this is in the sourcecode, right?
It's a .h file (C Programming language) so I can't implement this Mod in my ROM, right?
,im sure i read that there will be multi tasking in the future, now the problem i have is im still looking to get a phone i.e. dvp., but its only got 256mb ram, now is this going to play a big part in which phone to get because of multi tasking.
http://www.phonearena.com/phones/Dell-Venue-Pro_id4595
no it doesn't, 512 of ram.
nrfitchett4 said:
http://www.phonearena.com/phones/Dell-Venue-Pro_id4595
no it doesn't, 512 of ram.
Click to expand...
Click to collapse
That was posted in October, more recent news actually show on the device as having 256MB
Personally, I would get a different device due to this - it may not actually make a difference in terms of multitasking, but we just don't know until multitasking is available to developers.
Thing is, developers are allowed to us 90MB for any single app (or game), but this only applies to devices with 256MB RAM. That means that multitasking has not been taken into consideration at all when writing the marketplace specs as I doubt you'll be able to fit 2 x 90MB apps in memory at once (on a 256MB device the total available amount is something like 220MB - as parts are reserved for GPU etc). That said, there is no rule saying that if a device has 512MB the app can or cannot us 256+90 (ie. 346MB) so...
Of course, most apps do not use 90MB so it's not a huge problem. But given the choice between a Dell or Samsung I'd go for a Samsung any day of the week (which is also what I did).
depending on what you want to do/use cases, if you want multitasking ability, take a look at the nokia n900
cheers
So, the next craftsmen decided to port Android on Samsung Wave. Information about this published administrator Polish-bada-world.pl with nick watero. In his message, stated that he and his friends from Russia and Belarus (!!!) eyeing the possibility of porting Google Android on Samsung Wave and now the project has a code name AndroBada. In fact, it is very difficult to read translated from Polish into english text, but the total amount of information you can understand that in the course of viewing the inside of firmware (including JE7 from the Polish operator Orange), the guys found some security holes. These holes seem to be as allow you to download Android for Samsung Galaxy S without affecting the security of the system itself in any way.
Also known major problems faced by them boys:
1) the problem with memory - the system does not see all 512 MB of memory and it is unknown whether this is due to the fact that memory is somehow divided into sectors or is it 1) the problem with memory - the system does not see all 512 MB of memory and it is unknown whether this is due to the fact that memory is somehow divided into sectors or is it just-ish two "strips" of 256 MB. Moreover, the "RAM"Samsung Wave II differs from the memory of the "first wave" and is likely to Wave II was able to load Android;; Look at the two "strips" of 256 MB. Moreover, "RAM" Samsung Wave II differs from the memory of "first wave" and is likely to Wave II was able to load Android;;
2) Processor - it's not like the CPU Samsung Galaxy S. One gets the feeling that the CPU Samsung Wave does not accept the driver written for the processor Galaxy S. 2) Processor - it's not like the CPU Samsung Galaxy S. One gets the feeling that the CPU Samsung Wave did not find the driver written for the processor Galaxy S.
So far they have showed a vedio on youtube to demonstrating that they mean business .I dont know about you guys but seriously they where able to prove that it is possible in just 5 days or less off hard work
more news about the project soon
ps. praying that they release a stable version (sorry bada i think your days are coming to an end)
so, who are those guys? are they willing to share knowledge?
http://www.youtube.com/watch?v=5UueWOF5Icc
This is the video of androbada....
@MCLP look here about the ram:
http://forum.xda-developers.com/showthread.php?t=899661
If it is easy plz create a english section on the site of androbada...
RAM is the same. Use AT Commands:
AT+HEADERINFOSHOW?
S8500 and S8530 answers with:
KAC007021M...
And this is the "POP" in Samsung CPU...
Major difference is NAND.
S8500 have 2GB moviNand from Samsung (KLM2G1DEDD-A101)
S8530 uses SanDisk... iNand
Best Regards
Guys,
I no where see any kind of message in "http://bada-world.pl/androbada/" about the demo video, even one of the user in that forum claims that it was posted by XDA. am i missing anything?? else google translate not working properly
I knew the Wave had 512mb of RAM, stupid harvy mundane.
Now discussion and news will be publish here: forum.xda-developers.com/showthread.php?t=1006796
Do not write here.
Hurry up. Soon is 1.April.
But we could make also few nice Videos.
What we need:
1.
We need Video capture from real Android handset... or Win Mobile if you wish.
2.
If we have Screencapture Video... then we need to convert into Flash, to prevent...
For example:
http://www.zdnet.de/windows_flash_a...o_swf_converter_download-39002345-88979-1.htm
3.
Now we need bada SDK or we have compiled this Example to replace swf Video.
http://forum.xda-developers.com/showthread.php?t=904555
Now everyone could make their own Android or S60 or WinMobile or...
I could do this example with EF81, SXG75 or some other old handset...
But Resolution is 240 x 320...
I have no handset with 480 x 800 for make such Capture Video.
Sorry, my fault.
Oh, nice. Seems much easier. Found this:
http://www.youtube.com/watch?v=Jb0AzMmQ174&feature=player_embedded#at=357
What is the difference between your Videos and this nice fake?
Btw, thanx to this guy who explained how he locked Fake Video...
adfree said:
Hurry up. Soon is 1.April.
But we could make also few nice Videos.
What we need:
1.
We need Video capture from real Android handset... or Win Mobile if you wish.
2.
If we have Screencapture Video... then we need to convert into Flash, to prevent...
For example:
http://www.zdnet.de/windows_flash_a...o_swf_converter_download-39002345-88979-1.htm
3.
Now we need bada SDK or we have compiled this Example to replace swf Video.
http://forum.xda-developers.com/showthread.php?t=904555
Now everyone could make their own Android or S60 or WinMobile or...
I could do this example with EF81, SXG75 or some other old handset...
But Resolution is 240 x 320...
I have no handset with 480 x 800 for make such Capture Video.
Sorry, my fault.
Oh, nice. Seems much easier. Found this:
http://www.youtube.com/watch?v=Jb0AzMmQ174&feature=player_embedded#at=357
What is the difference between your Videos and this nice fake?
Btw, thanx to this guy who explained how he locked Fake Video...
Click to expand...
Click to collapse
Look at this nice Video:
http://www.youtube.com/watch?v=Jb0AzMmQ174&feature=player_embedded#at=357
Then tell me please, how to be sure that other Videos are not fake?
Best Regards
adfree said:
Look at this nice Video:
http://www.youtube.com/watch?v=Jb0AzMmQ174&feature=player_embedded#at=357
Then tell me please, how to be sure that other Videos are not fake?
Best Regards
Click to expand...
Click to collapse
okay...forget all...oleg started a new thread...please start working with him...i believe you people know better than anyone else...so plz..
http://forum.xda-developers.com/showthread.php?t=1012856
Yes adfree. please spend your energy on this one.
I was glancing at some screenshots of the Galaxy Nexus/GNex/Gex/Whatever, and noticed an issue/feature which is not unique to the Nexus.
The quote RAM figures for the device and the RAM total in the "Running" section of applications never match (in the massive sample of Android handsets I've seen - 3).
HTC Desire: Quoted RAM - 576MB. RAM total in "Running" section - 374MB. 65%
Galaxy S II: 1GB (1024MB). 693MB. 68%.
Galaxy Nexus: 1GB. 631MB (in screenshot I saw). 62%
I'm not actually calling this a problem, I'm just wondering what is the reason for this difference. Is the "Running" apps section simply RAM allocated for apps and the rest of the RAM is for the OS? Are the OEMs lying to us while smoking fat cigars by their swimming pools?
I'm sure there's a very simple reason for this. I just don't know it.
Just like the devices total memory is 16 gb and 13.xx is actually to be played with. These things often get 'rounded up' quite often in the world of cars the manufactor claim a certain horse power and its rounded to nearest 50 or 100. Such is life in this modern age I'm afraid and unless some kind of consume4 rights group tries to do anything about this the current trend of manufactoers and ceo 's bull sh*tting to us is likely to continue.
Of course I'd like to be wrong and say that the other 300+MB are dedicated to the 'system' but I can't promice I'm afraid.
Sent from my X10i using xda premium
I dont think it's that easy in this example though.. when talking about storage size one actual GB is 1024 MB but when it says 16GB on the box the manufacturers and retailers actually mean 16000MB devide this 16000 by 1024 and you get the real useable storage size, 15.625GB in this case. Talking about RAM on the other hand they tend to go by the full size GB when typing it out for you, 1GB is 1024MB of RAM, so.. where does that lost RAM go? I dont know! Someone with deeper knowledge want to explain further?
Sent from my X10i using xda premium
Maybe the 'system' really does use that much then although bear in mind sence and touchwiz are bound to use more. Hopefully on the actual retail release software will be more optimized and we get some ram back.
Sent from my X10i using xda premium
The GPU shares memory and reserves a huge chunk of the ram for itself.
The rest I can't explain correctly (if it's correct at all) but it's reserved for the os and can't be addressed by apps.
These reports only show the part that's addressable by apps.
gokpog said:
The GPU shares memory and reserves a huge chunk of the ram for itself.
The rest I can't explain correctly (if it's correct at all) but it's reserved for the os and can't be addressed by apps.
These reports only show the part that's addressable by apps.
Click to expand...
Click to collapse
So this is to ensure the OS has enough ram and flows nicely and keeping everything lag free and super quick. Good news
Sent from my X10i using xda premium
gokpog said:
The GPU shares memory and reserves a huge chunk of the ram for itself.
The rest I can't explain correctly (if it's correct at all) but it's reserved for the os and can't be addressed by apps.
These reports only show the part that's addressable by apps.
Click to expand...
Click to collapse
Nice one.
As Tjotte said, I know that when it comes to storage, manufacturers normally quote gigabytes as multiples of 1000MB (I call this lying but what the heck). Then you add another small percentage for BIOS and you have a storage device with about 90%+ of what you thought it was going to be.
But around a third off the quoted figure??? That's more likely system allocation rather than a blatant lie.
Which now leads me to think... PC GPUs have their own RAM completely separate to system RAM. Apart from cache, I'm guess the mobile SoC's don't have specific RAM. Hmmmmm..... A quick peak at AnandTech at the Kal-El write-up tells me they don't. Bummer.
I think some of its used for caching as well. If you open task manager in Windows, you'll often see how the available RAM is far less than what would be expected if you take total RAM and subtract the RAM used by currently open apps (both system and user). It could be that some of RAM is essentially pre-fetching or caching apps, both user apps as well as system apps (such as Dialler, Framework components, GoogleSync etc) which notably make launching everything faster. And some of it is definitely used by the GPU as well similar to the integrated graphics on pc's, and this is probably dynamic as well, which can explain why available RAM does fluctuate within the same phone in similar conditions.
Internal storage is the Gb vs GB bit vs byte issue plus partitioning, a free hundred MB as /system, maybe other partitions for other things such as user data etc.
As far as the ram, some for the gpu, the os will use some, some will be used as cache which can be dropped if needed, but in the end the device still has more free ram than some phones have in total.
Sent from my GT-I9100 using xda premium
Disk storage manufacturers calculate in base-10 and memory manufacturers in base-2. If they say a device has 1GB of RAM, it is 1024MB, not 1000MB. Same goes for flash memory. The Nexus has 16GB of flash, 2.5GB appear to be reserved for system.
Anyone who wants to understand the difference between base-10 decimal SI units, JEDEC units for RAM sizes, base-2 binary IEC units, and the confusion 1000 vs. 1024 creates should check out Wikipedia's article on the topic, as it pretty much covers everything... including things like how storage device sizes and network speeds are measured, consumer confusion, and even lawsuits.
http://en.wikipedia.org/wiki/Binary_prefix
phazerorg said:
Anyone who wants to understand the difference between base-10 decimal SI units, JEDEC units for RAM sizes, base-2 binary IEC units, and the confusion 1000 vs. 1024 creates should check out Wikipedia's article on the topic, as it pretty much covers everything... including things like how storage device sizes and network speeds are measured, consumer confusion, and even lawsuits.
http://en.wikipedia.org/wiki/Binary_prefix
Click to expand...
Click to collapse
That's all well and good but it's totally irrelevant when it comes to the 1 GB ram in this phone. It has 1024 MB ram, as stated. However, some of it is reserved for parts of the hardware like the GPU, the radio, video encoding/decoding etc. This is the same for all Android phones. Anyone that wants to see it can check that allocation in the source. Brian Swetland from Google has already described the motivation for this and the specific sizes used for different components for the Nexus One.
blunden said:
That's all well and good but it's totally irrelevant when it comes to the 1 GB ram in this phone. It has 1024 MB ram, as stated. However, some of it is reserved for parts of the hardware like the GPU, the radio, video encoding/decoding etc. This is the same for all Android phones. Anyone that wants to see it can check that allocation in the source. Brian Swetland from Google has already described the motivation for this and the specific sizes used for different components for the Nexus One.
Click to expand...
Click to collapse
Agreed that it is irrelevant and the device definitely has 1024 MB of RAM. I was going a bit off-topic in an attempt to defer any further off-topic comments on that subject by directing people to an alternative source for that information rather than discussing it in this thread, which is about the Galaxy Nexus's RAM.
Your post is probably the most useful and informative so far in this thread. It does have 1024 MB, used for various purposes as needed, and there's really not much else to say.
It is hardware accelerated and to my knowledge the sgx540 doesnt have discrete ram so that factors into the equation. I wouldnt be sjrprised if the os allocated 64-128mb ram for the gpu.
I invented cyberspace. You're trespassing.
RAM Division
1.HW Drivers(screen, gpu, audio, etc)
2.OS Services & Shared Memory
3.Cached Services/processes
4.Active Apps
phazerorg said:
Agreed that it is irrelevant and the device definitely has 1024 MB of RAM. I was going a bit off-topic in an attempt to defer any further off-topic comments on that subject by directing people to an alternative source for that information rather than discussing it in this thread, which is about the Galaxy Nexus's RAM.
Your post is probably the most useful and informative so far in this thread. It does have 1024 MB, used for various purposes as needed, and there's really not much else to say.
Click to expand...
Click to collapse
Oh, I see. Fair enough. Actually I wrote my post based on the assumption that your post was the first post. I later realized that was not the case so I just quoted your post to make it clear which post I was referring to.
-Most of the times a part is reserved for the gpu.
-Android will reserve more ram when there is more ram to optimize performence.
-Abdroid get more and more features wich use more ram.
-Active apps wil be kept in ram when possible.
-Applications get also more complexed.
-Android gets build differently when there are higher hardware standards. Compare for example windows 7 with windows xp. Windows 7 uses a lot more ram because of several cahcing optimizations for example.
Could be buffers too.
e.g if you check free memory on a linux system a large amount is used by buffers but is actually useable if needed.
It's definately not "rounding up" as 30%+ is a long way from the kind of rounding up manufacturers of storage do.
phazerorg said:
Anyone who wants to understand the difference between base-10 decimal SI units, JEDEC units for RAM sizes, base-2 binary IEC units, and the confusion 1000 vs. 1024 creates should check out Wikipedia's article on the topic, as it pretty much covers everything... including things like how storage device sizes and network speeds are measured, consumer confusion, and even lawsuits.
http://en.wikipedia.org/wiki/Binary_prefix
Click to expand...
Click to collapse
This is actually very useful for people that don't understand the differences. And there are many that don't.
They had to cut back on the RAM because they paid too much for Matias, since the boxes were already printed with 1GEEBEE noted, they're now trying to pass it off and hope nobody notices.