NOTE: the log below pertains to KB5...I haven't had time yet to look into KB6.
http://www.samfirmware.com/WEBPROTECT-p1010.htm
ro.build.display.id=FROYO.XWKB5
ro.build.version.sdk=8
ro.build.version.release=2.2.1
ro.build.date=Thu Feb 17 19:34:43 KST 2011
I'm going to unpack the various RFS archives, to see what's new. I've got a GT-P1000 Galaxy Tab (wifi+3G), so I'm not going to flash with Heimdall (let alone Odin ).
I made backups for factoryfs.rfs / dbdata.rfs etc. using the usual bit-by-bit "dd" -based method, and I've got a trusty TitaniumBackup archive ready, just in case
I notice that TV-out seems to be gone, and FM radio appears to be available. Hardware DSP support seems more present too. (read content logs below for more information)
TAR contents:
Code:
p1wifi_20110128_r10_00.pit (4 KB) (see PIT-info dumped below)
GT-P1010-CSC-SERKB3/
cache.rfs (10.9 MB) (see content listing below)
movinand.mst (51MB) (can be extracted with [URL="http://movitool.ntd.homelinux.org/trac/movitool/"]MoviTool[/URL], based on [URL="http://forum.xda-developers.com/showpost.php?p=9481702&postcount=30"]Volker1's method[/URL])
P1010XWKB5-REV03-ALL-low-CL913814/
boot.bin (256 KB)
cache.rfs (672 KB)
normalboot.img (4.3 MB)
param.lfs (612 KB)
recovery.img (4.3 MB)
Sbl.bin (1.2 MB)
system.rfs (331 MB)
userdata.rfs (1.2 MB)
Output from Volker1's PIT-info utility:
Code:
Contents of PIT file: p1wifi_20110128_r10_00.pit
---------------------------------------------------------------------------
file magic = 0x12349876 (expected value)
Unknown data: 0 0 0 0 0
Number of partitions = 13 (usual value)
Partition #1
Usual content: boot.bin, the primary boot loader (low-level hardware initialization)
partition entry type: 0 0 (normal partition)
ID = 0; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [IBL+PBL.........................]
file name = [boot.bin........................................................]
Partition #2
Usual content: partition information table (PIT)
partition entry type: 0 0 (normal partition)
ID = 0x1; flags = 0; unknown: 0
size = 1 blocks of 256 * 512 bytes = 131072 B = 128 kB = 0 MB
unknown string: [........]
partition name = [PIT.............................]
file name = [p1wifi.pit......................................................]
Partition #3
Usual content: efs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x14; flags = 0x2 (rfs file system); unknown: 0
size = 40 blocks of 256 * 512 bytes = 5242880 B = 5120 kB = 5 MB
unknown string: [........]
partition name = [EFS.............................]
file name = [efs.rfs.........................................................]
Partition #4
Usual content: Sbl.bin, the secondary boot loader (loads linux kernel)
partition entry type: 0 0 (normal partition)
ID = 0x3; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL.............................]
file name = [sbl.bin.........................................................]
Partition #5
Usual content: backup of secondary boot loader
partition entry type: 0 0 (normal partition)
ID = 0x4; flags = 0; unknown: 0
size = 5 blocks of 256 * 512 bytes = 655360 B = 640 kB = 0 MB
unknown string: [........]
partition name = [SBL2............................]
file name = [sbl.bin.........................................................]
Partition #6
Usual content: param.lfs /mnt/.lfs j4fs
partition entry type: 0 0 (normal partition)
ID = 0x15; flags = 0x2 (rfs file system); unknown: 0
size = 20 blocks of 256 * 512 bytes = 2621440 B = 2560 kB = 2 MB
unknown string: [........]
partition name = [PARAM...........................]
file name = [param.lfs.......................................................]
Partition #7
Usual content: zImage, the linux kernel
partition entry type: 0 0 (normal partition)
ID = 0x5; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [NORMALBOOT......................]
file name = [normalboot.img..................................................]
Partition #8
Usual content: recovery.bin, the backup copy of zImage/initramfs
partition entry type: 0 0 (normal partition)
ID = 0x8; flags = 0; unknown: 0
size = 30 blocks of 256 * 512 bytes = 3932160 B = 3840 kB = 3 MB
unknown string: [........]
partition name = [RECOVERY........................]
file name = [recovery.img....................................................]
Partition #9
Usual content: factoryfs.rfs
partition entry type: 0 0 (normal partition)
ID = 0x16; flags = 0x2 (rfs file system); unknown: 0
size = 1430 blocks of 256 * 512 bytes = 187432960 B = 183040 kB = 178 MB
unknown string: [........]
partition name = [SYSTEM..........................]
file name = [system.rfs......................................................]
Partition #10
Usual content: dbdata.rfs
partition entry type: 0 0 (normal partition)
ID = 0x17; flags = 0x2 (rfs file system); unknown: 0
size = 302 blocks of 256 * 512 bytes = 39583744 B = 38656 kB = 37 MB
unknown string: [........]
partition name = [USERDATA........................]
file name = [userdata.rfs....................................................]
Partition #11
Usual content: cache.rfs
partition entry type: 0 0 (normal partition)
ID = 0x18; flags = 0x2 (rfs file system); unknown: 0
size = 140 blocks of 256 * 512 bytes = 18350080 B = 17920 kB = 17 MB
unknown string: [........]
partition name = [CACHE...........................]
file name = [cache.rfs.......................................................]
Partition #12
Usual content: modem.bin
partition entry type: 0 2 (unknown value)
ID = 0x3; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [HIDDEN.D........................]
file name = [hidden.rfs.t....................................................]
Partition #13
Usual content: Unknown
partition entry type: 0 2 (unknown value)
ID = 0; flags = 0x1; unknown: 0
size = 0 blocks of 0 * 512 bytes = 0 B = 0 kB = 0 MB
unknown string: [........]
partition name = [MOVINAND........................]
file name = [movinand.mst....................................................]
The usual CSC cache.rfs content:
Code:
/dbdata/svox/de-DE_gl0_sg.bin
/dbdata/svox/de-DE_ta.bin
/dbdata/svox/en-GB_kh0_sg.bin
/dbdata/svox/en-GB_ta.bin
/dbdata/svox/en-US_lh0_sg.bin
/dbdata/svox/en-US_ta.bin
/dbdata/svox/es-ES_ta.bin
/dbdata/svox/es-ES_zl0_sg.bin
/dbdata/svox/fr-FR_nk0_sg.bin
/dbdata/svox/fr-FR_ta.bin
/dbdata/svox/it-IT_cm0_sg.bin
/dbdata/svox/it-IT_ta.bin
/system/csc/feature.xml
/system/csc/contents.db
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/customer.xml
/system/app/MusicODC.apk
/system/T9DB/qwerty_fi.kdb
/system/T9DB/phonepad_cs.kdb
/system/T9DB/qwerty_da.kdb
/system/T9DB/Samsung_400_PLlsUN_xt9.ldb
/system/T9DB/phonepad_lt.kdb
/system/T9DB/Samsung_400_TRlsUN_xt9.ldb
/system/T9DB/Samsung_400_DEusUN_xt9.ldb
/system/T9DB/Samsung_400_ETlsUN_xt9.ldb
/system/T9DB/Samsung_400_ENubUN_xt9.ldb
/system/T9DB/Samsung_400_SVusUN_xt9.ldb
/system/T9DB/qwerty_sv.kdb
/system/T9DB/Samsung_400_DAlsUN.ldb
/system/T9DB/phonepad_uk.kdb
/system/T9DB/phonepad_it.kdb
/system/T9DB/phonepad_el.kdb
/system/T9DB/qwerty_hu.kdb
/system/T9DB/qwerty_es.kdb
/system/T9DB/Samsung_400_UKlsUN_xt9.ldb
/system/T9DB/qwerty_fr.kdb
/system/T9DB/qwerty_et.kdb
/system/T9DB/Samsung_400_SKlsUN_xt9.ldb
/system/T9DB/phonepad_no.kdb
/system/T9DB/qwerty_nl.kdb
/system/T9DB/qwerty_lt.kdb
/system/T9DB/Samsung_400_LVlsUN_xt9.ldb
/system/T9DB/Samsung_400_ITlsUN_xt9.ldb
/system/T9DB/Samsung_400_PTlsUN_xt9.ldb
/system/T9DB/phonepad_da.kdb
/system/T9DB/Samsung_400_HUlsUN_xt9.ldb
/system/T9DB/Samsung_400_ELlsUN_xt9.ldb
/system/T9DB/phonepad_et.kdb
/system/T9DB/Samsung_400_KKlsUN_xt9.ldb
/system/T9DB/phonepad_es.kdb
/system/T9DB/qwerty_sk.kdb
/system/T9DB/phonepad_nl.kdb
/system/T9DB/qwerty_pt.kdb
/system/T9DB/Samsung_400_ESlsUN_xt9.ldb
/system/T9DB/Samsung_400_CSlsUN_xt9.ldb
/system/T9DB/phonepad_ru.kdb
/system/T9DB/phonepad_tr.kdb
/system/T9DB/qwerty_tr.kdb
/system/T9DB/phonepad_de.kdb
/system/T9DB/Samsung_400_FIlsUN_xt9.ldb
/system/T9DB/phonepad_ko.kdb
/system/T9DB/phonepad_fr.kdb
/system/T9DB/phonepad_fi.kdb
/system/T9DB/qwerty_ru.kdb
/system/T9DB/phonepad_en.kdb
/system/T9DB/qwerty_en.kdb
/system/T9DB/qwerty_cs.kdb
/system/T9DB/qwerty_el.kdb
/system/T9DB/Samsung_400_NOlsUN.ldb
/system/T9DB/Samsung_400_RUlsUN_xt9.ldb
/system/T9DB/qwerty_kk.kdb
/system/T9DB/qwerty_no.kdb
/system/T9DB/qwerty_uk.kdb
/system/T9DB/phonepad_lv.kdb
/system/T9DB/phonepad_pl.kdb
/system/T9DB/Samsung_400_NLlsUN_xt9.ldb
/system/T9DB/phonepad_sv.kdb
/system/T9DB/phonepad_sk.kdb
/system/T9DB/Samsung_400_LTlsUN_xt9.ldb
/system/T9DB/qwerty_pl.kdb
/system/T9DB/qwerty_de.kdb
/system/T9DB/Samsung_400_FRlsUN_xt9s.ldb
/system/T9DB/qwerty_ko.kdb
/system/T9DB/qwerty_lv.kdb
/system/T9DB/phonepad_pt.kdb
/system/T9DB/qwerty_it.kdb
/system/T9DB/phonepad_hu.kdb
/system/CSCFiles.txt
/system/SW_Configuration.xml
Changes in /system/app/ :
Removed DailyBriefing, Ebook, Mms, MobileTrackerEngineTwo, MobileTrackerUI, OtaProvisioningService, SamsungWidget_WeatherClock, SoundRecorder, signin, syncmldm, wipereceiver, wssomacp
Added PhoneCrashNotifier, PopupuiReceiverf, qik, qikhelp, skype
Changes in /system/bin/ :
Too many to list, but here are some notable ones:
Removed BCM4329B1_002.002.023.0534.0590.hcd (the driver for the multi-function Broadcom BCM-4329 chipset, also removed in /etc/wifi/ etc.), akmd2 (the multi-sensor driver, now split into several sub-daemons: geomagnetic, gyroscope, temperature, light, orientation, pressure, proximity, etc.)
Notable changes in /system/etc/ :
Added audio/codec/FMRadioEar.ini, audio/codec/FMRadioSpk.ini, and FM-radio stuff in /etc/firmware/ and /lib/libfmradio_jni.so (the Texas Intruments BRF6350 chip supports FM radio...but I don't think that /system/app/ contains an FM tuner application).
Notable addition: /lib/dsp/ + /lib/libOMX*.so + /lib/libVendor_ti_OMX*.so + lib/libaomx_*.so (Texas Intruments OMX/DSP, hardware encoding/decoding of 720p AMR, WB-AMR, AAC, h264, WMA, WMV, MP3, MPEG4, Flac, AC3, S263, etc.)
Code:
720p_h264vdec_sn.dll64P
720p_mp4vdec_sn.dll64P
720p_mp4venc_sn.dll64P
baseimage.dof
baseimage.map
chromasuppress.l64p
conversions.dll64P
dctn_dyn.dll64P
ddspbase_tiomap3430.dof64P
dfgm.dll64P
dynbase_tiomap3430.dof64P
eenf_ti.l64P
h264vdec_sn.dll64P
h264venc_sn.dll64P
ipp_sn.dll64P
jpegdec_sn.dll64P
jpegenc_sn.dll64P
m4venc_sn.dll64P
monitor_tiomap3430.dof64P
mp3dec_sn.dll64P
mp4v720parcdec_sn.dll64P
mp4varcdec_sn.dll64P
mp4vdec_sn.dll64P
mpeg4aacdec_sn.dll64P
mpeg4aacenc_sn.dll64P
mpeg4aridec_sn.dll64P
nbamrdec_sn.dll64P
nbamrenc_sn.dll64P
postprocessor_dualout.dll64P
qosdyn_3430.dll64P
ringio.dll64P
star.l64P
usn.dll64P
vpp_sn.dll64P
wbamrdec_sn.dll64P
wbamrenc_sn.dll64P
wmadec_sn.dll64P
wmv9dec_sn.dll64P
yuvconvert.l64p
Wifi access point doesn't seem very well protected (/etc/wifi/softap/hostapd.conf):
SSID = AndroidAP (not broadcast)
IP = 192.168.43.1
PASS = "password" (WPA)
By the way, the Wifi interface is different than on the fully-featured Tab: tiwlan0 (the access point is tiap0)
Nice let us know what's new and how you make out
This is great news and I am looking forward to your project, thanks!!!
Heads-up: original post updated with PIT partition structure and TAR contents.
Original post updated with further information (FM radio, DSP, etc.). None of this is authoritative, obviously. I am just making plain observations. I haven't even seen the manufacturer's specifications yet for this device.
Splice/combine the ROM with a P1000 ROM?
Cool. Does this mean that your aim to splice/combine the ROM with a P1000 ROM to create a custom Android 2.2.1 ROM WITH 3G capabilities, that is compatible with P1000?
And in that case, it sure would be nice to keep most of what has been removed from /system/* in the P1010 ROM, of course.
Very interesting, thanks for posting the analysis.
I wonder whether GL drivers are any newer than from P1000 ROMs.
And GPS daemon?
Also, interesting about these split sensor drivers.
edit
hmm, interesting, the GL drivers are for SGX530 not 540 like in normal tab.
And the CPU in 1010 is OMAP3 not Hummingbird.
KB6 now online @ Samfirmware.
I'm too busy to look into it though.
Hi,
I just got the Wifi version. How can I check the ROM version?
does the P1010 still have a gps radio?
jackfrostn said:
does the P1010 still have a gps radio?
Click to expand...
Click to collapse
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
could someone try getting the skype and qik files working
any update on the ROMs progress?
bthoven said:
Yes. Only differences between 3g and wifi model:
- no 3G radio
- less powerful CPU/GPU on wifi model (thus can't play HD/Full HD video)
- and off course, wifi model is cheaper
Click to expand...
Click to collapse
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
himmelhauk said:
Actually it CAN play HD video. It can record 720p movies so it would only make sense it'd be able to play them. I watch 720p episodes of Breaking Bad on mine.
Sent from my GT-P1010 using XDA Premium App
Click to expand...
Click to collapse
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
bthoven said:
Yes, it can play 720p lower bitrate whilst the 3G version can play higher bit rate, and also 1080p.
Click to expand...
Click to collapse
Actually it is worth making a correction here as well, it plays 1080 just fine as well, at least for me.
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
chrisliphart said:
Out of curiousity, where did you see that the wifi has a different CPU/GPU than the GSM/CDMA versions? I'm not finding that info anywhere.
Click to expand...
Click to collapse
In all the TI OMAP libraries and kernel in the ROM?
skype for p1010 wifi
Skype will work with regular rom.i used it all day today
Yes, it does have gps radio on there. Well mine does anyway (in the uk)
Ok...by request, here's a pretty simple boot animation porting/converting tutorial.
IF THE BOOT ANIMATION YOU'RE TRYING TO PORT IS FOR SMALLER SCREENS:
First off...if the frames are too small, it will look crappy and stretched. That being said, try to find something that is remotely close to the 480 X 800 screen size...or resize each individual frame. If the frame size is somewhat close to 480 X 800, then all you have to do is change how the boot animation is being read in the desc.txt file.
- Unzip the boot animation you're trying to convert
- Open the file named "desc.txt" in notepad
- Change the screen size to your desired size
EXAMPLE: If the desc script looks like this...
Code:
[B][COLOR="Red"]400 700[/COLOR][/B] 30
p 1 0 part0
p 0 0 part1
...then change it to this...
Code:
[B][COLOR="Red"]480 800[/COLOR][/B] 30
p 1 0 part0
p 0 0 part1
- Click save (do not change file name)
- Now zip up frame folders and desc.txt file
- Make sure you use "store" compression method
- Now double click on zip and delete the file named "Thumbs.db" from all of the frame folders
OPTIONAL: I like to convert the frames to a format with a smaller file size. If the boot animation consists of more than 150 frames, and are in .PNG format, chances are your boot animation is going to be more than 5-6mb. If you've resized the .PNG frames to a bigger size...then you'll end up with a 15-20mb boot animation. If this is the case, just convert them to .JPG format.
IF THE BOOT ANIMATION YOU'RE TRYING TO PORT IS FOR BIGGER SCREENS:
You can just alter the desc script if you want, but if the frame size is alot bigger (tablet sized), then you'll need to do the following:
- Unzip the boot animation you're trying to convert
- Re-size all frames in all frame folders to desired size (TIP: "PIXresizer" will resize multiple files)
- If making a portrait boot animation, you have to rotate all the frames
- Open the file named "desc.txt" in notepad
- Change the screen size to your desired size
EXAMPLE: If the desc script looks like this...
Code:
[B][COLOR="Red"]500 1200[/COLOR][/B] 30
p 1 0 part0
p 0 0 part1
...then change it to this...
Code:
[B][COLOR="Red"]480 800[/COLOR][/B] 30
p 1 0 part0
p 0 0 part1
- Now zip up frame folders and desc.txt file
- Make sure you use "store" compression method
- Now double click on on zip and delete the file named "Thumbs.db" from all of the frame folders
TO SPEED UP/SLOW DOWN FRAMERATE (animation play speed)
If your boot animation seems to be playing too fast or too slow, then do the following:
- Unzip the boot animation
- Open the file named "desc.txt" in notepad
- Now, change the framerate
EXAMPLE: Change the two digit number after the frame size to desired framerate...
Code:
480 800 [B][COLOR="Red"]30[/COLOR][/B]
p 1 0 part0
p 0 0 part1
That's it! Enjoy
Thank you for posting this!
elephant007 said:
Thank you for posting this!
Click to expand...
Click to collapse
Np
10char
I have a feeling I know the answer to this, but any chance you know how to convert to the qmg format fir stock ROM?
jedwardmiller said:
I have a feeling I know the answer to this, but any chance you know how to convert to the qmg format fir stock ROM?
Click to expand...
Click to collapse
Not possible at this time.
Never mind, I decided to start a new thread with my question...
http://forum.xda-developers.com/showthread.php?p=19484808
BUMPED!!!!
...so that we can start seeing more boot animations in this mug.
Hello there,
Could anyone smarter than me please tell me what is causing this boot animation not to play?
Here are the image specifics:
Size in pixels: 360 x 640
Print size: 95.26 x 169.36
Resolution: 95.9866 x 95.9866 ppi
Color space: RGB
File size: 157.5kb
File type: PNG
Number of layers: 1
Number of pixels: 230400
Total number of frames: 101
The compression of the zip is set to 'store'
The permissions are set to 0644
I'm using the international model (d855) with no carrier bootanimation.
Bootanimation is in /system/media where the old one was.
The total size of the zip is 14436 KB
The desc.txt file looks as follows
Code:
1440 2560 24
p 1 0 part0
p 0 0 part1
If I have that right the first part plays once with no pause and the second part is in a continuous loop with no pause.
The framerate is set to 24 to match the framerate of the video I pulled the frames from.
What is happening:
After the splash screen I just get a black screen until the device has booted. No animation.
Any help would be very appreciated.
Bump. Still haven't found where I'm going wrong.
While I look around for my mess up , I have reduced the animation size by 63% by optimizing the frames.
If it's any incentive for you guys to help, it's a popular anime boot animation
Resolved:
Setting a defined number of loops for the last part of the animation fixed it.
Hello,
who has some more Information about the Bootanimations?
Maybe we can create a WIKI Thread for it: http://forum.xda-developers.com/wiki/Hui_Fei_Type
Malaysk has here a thread about BOOTANIMATIONS.
http://forum.xda-developers.com/showpost.php?p=62776842&postcount=18539
But maybe anybody want to create a bootanimation, what a important for that?
Maybe we can bring here some information togehter.
Then i start to edit this first thread to bring all information together.
Questions:
- Which pixelsize can the animation have for a: 1024 x 600 or 800 x 480 ?
- Which files are possible JPG GIF PNG ?
- How many pictures can the animation have?
- Is this the structur for the animation? What are important for that? What are the "Parts" mean?
FOLDER: bootanimation_dancing_droids
------- FOLDER: part0
-------------- d001.jpg
-------------- d002.jpg
-------------- d003.jpg
........
------- FOLDER: part1
-------------- e001.jpg
-------------- e002.jpg
-------------- e003.jpg
........
------- FILE: desc.txt
- What are inside the desc.txt file? What does it mean?
800 480 20
p 1 0 part0
p 0 0 part1
- How must the filename for the animation are?
- This are a part from the Installation instruction from Malaysk. How can i give this right to the zip (Which Programm???, which menue?)?
5. Next, copy bootanimation_dancing_droids.zip file below the animation to a folder \ system \ mtc \ and give rights 644 (ie rw-r-r)
More questions or answers please here in that thread.
Many, many Informations and Tools for the Bootanimations:
http://forum.xda-developers.com/showthread.php?t=2756198
Hi,
I am having an issue with Android system taking almost all memory after a few days uptime.
As a result application are closed when going to the background due to the lack of memory, all the phone slows down (reboot screen take 10s to load !).
Rebooting fixes the issue.
I am in v9.0.0.127
First two screenshots are before reboot.
3rd one after reboot which shows normal Android system memory usage.
Is anyone else having the same issues?
Currently the AL00 is on .137 and don't have that issue. Are you one the international model of the Mate x?
Yes international version.
Happened again today, a single app can be open, chrome complains about lack of memory..
Android os, native, does that mean the os itself is leaking memory or could that be an app ?
Could you post me what your Android os memory usage is ? Including the native, kernel and cache part ?
I have been playing with adb, I have found out that 'lost memory' is increasing which seems to indicate some kind of memory leak.
I will need to wait a few more days for the leakage to become bigger to make sure.
Unfortunately it seems I cannot access the ION debugging without root
https://stackoverflow.com/questions/28057989/how-do-you-enable-ion-debugging-in-android-kernel
There is indeed a memory leak within [email protected]
meminfo shows that the PSS for this process keeps increasing :
Code:
Total PSS by process:
1,032,307K: [email protected] (pid 638)
[...]
Total PSS by OOM adjustment:
1,499,208K: Native
1,032,307K: [email protected] (pid 638)
73,370K: [email protected] (pid 639)
[...]
Total PSS by category:
1,157,620K: EGL mtrack
755,914K: Native
332,849K: Dalvik
HWEVR:/storage/emulated/0/memleak $ dumpsys meminfo 638
Applications Memory Usage (in Kilobytes):
Uptime: 93341265 Realtime: 314343135
Pss Private Private SwapPss Heap Heap Heap
Total Dirty Clean Dirty Size Alloc Free
------ ------ ------ ------ ------ ------ ------
Native Heap 176 176 0 40 0 0 0
Dalvik Heap 0 0 0 0 0 0 0
Stack 16 16 0 20
Other dev 10 4 4 0
.so mmap 172 112 36 1120
Other mmap 2 0 0 56
EGL mtrack 1 030 180 1 030 180 0 0
Unknown 72 72 0 444
TOTAL 1032308 1030560 40 1680 0 0 0
In /proc/meminfo, we can see that the memory used by the ION memory allocator keeps on growing :
Code:
IonTotalCache: 29696 kB
IonTotalUsed: 1 374 764 kB
The leak is fixed in .184 on evr l29