Related
Hello, the forum! This is my first post, and I'm making it out of desperation. I have a time-sensitive problem, having just bought an O2 Xda IIs in Jakarta; if I need to complain to the shop that sold it to me, I'll have to do so very soon....
It's just that I'm confused over why the box and manual should read 96 MB ROM, when my "Device Information" screen tells me I've got a Flash Size of 32 MB. Please excuse my ignorance, but I'm completely new to this - it's my first ever PDA Phone.
I see that Blue Angel is also said to have 96 MB ROM here:
Code:
http://en.wikipedia.org/wiki/O2_xda
[edited for correction]
My specs are shown here. Please help me understand what the problem is. Thanks so much!
sub_rosa25
HardWare:
CPU : Intel(R) PXA263
Speed : 400 Mhz
RAM Size : 128 MB
Flash Size : 32 MB
Flash Chip : 28F128K3
Data Bus : 32 bits
Storage : 43.26 MB
LCD : 240X320 TFT
Colors : 65536
rom is 96 mb, you forget the extrom which is part of the rom and takes about 16 mb
simple math: extrom + flash + storage = rom
storage should be 48 mb but after installing the crap from extrom the rest is 43 in your case
Thank you for the quick and easy answer. It wasn't adding up for me because I didn't realize that extrom was included in the 96 MB ROM quoted. Cheers!
There is very little technical information on PIT files , so this thread is an attempt to find out some real details about PIT files, and perhaps eventually be able to create our own PIT files (by modifying Samsung ones, probably).
First, what we think we know PIT files do:
- PIT files only affect the 'STL' devices. That is, it affects the OneNAND and not the MoviNAND.
- PIT files appear to control the sizing (and maybe number) of STL devices that appear in Linux.
- PIT files appear to be used by Odin to map filenames inside .tar archives to STL partitions.
STL files are quite small, at under 2KB in size. Most of the file is made up of 0s. I have tried to compare the differences between the 512 513 and 803 PIT files we have available.
All the PIT files start with 76 98 34 12 0D - probably a signature to show it is a PIT file.
[Unimportant]
The 803 PIT file then has 00s all the way to the next common point. The 512 and 513 both have common data till the next common point - but this can't be too important as the 803 just has 00s.
The next common bit seems to read the following:
"oft IBL+PBL Server\90\To boot.bin inn; C:\Program Files\ESTsof
This probably indicates something to Odin. Strange that it has C:\Program Files\ - build path for the PIT file?
Next we have some 0s with common 1s inside them, followed by the word PIT, then more 0s, and then ries.pit. All common from here on with the words 'EFS' and 'efs.rfs'. Probably telling odin to map the efs.rfs file to the 'EFS' token. Tokens probably defined either in the kernel, or in the closed source STL library. More of the same of this, with 'SBL' 'sbl.bin', 'SBL2' 'sbl.bin' -- Both SBL and SBL2 map to the same sbl.bin file?
'PARAM' to 'param.lfs'
'KERNEL' to 'zImage'
'RECOVERY' to 'zImage' (this one is interesting - could we have seperate zImage and recovery? Could save some RAM here!)
[/Unimportant]
And now we'r onto the actual changes between the PIT files. 'FACTORYFS' maps to 'factoryfs.rfs'. However, before the FACTORYFS token, there are some bytes that likely control the partition sizes.
FACTORYFS
803 : A2 04 : 41476
512 : 7A 04 : 31236
513 : CA 04 : 51716
DBDATA
803 : F0 01 : 61441
512 : 18 02 : 6146
513 : C8 01 : 51201
CACHE
803 : 8C
512 : 8C
513 : 8C
MODEM
803 : 32
512 : 32
513 : 32
So there we have it. The only real changes between the PIT files are some seemingly garbage header information in 512/513 that is missing from 803, and FACTORYFS and DBDATA have different numbers -- probably sizes.
So assuming FACTORYFS maps onto /system, we can see that the only differences in the PIT files is moving space back and forwards between /dbdata and /system. The numbers themselves don't mean anything to me - can anybody work it out?
The numbers are little-endian, so you need to read them backwards per bytes. So instead of A12 it's actually 120A, etc. If you do so, you can see that the difference between 803 and 512 are actually minor, 40 "units" are shifted between probably DBDATA and SYSTEM.
Btw: doesn't the heimdal project klnow something about the pit files?
Nice, that gives us
FACTORYFS
803 : 04 A2 : 1186
512 : 04 7A : 1146
513 : 04 CA : 1226
DBDATA
803 : 01 F0 : 496
512 : 02 18 : 536
513 : 01 C8 : 456
1186+496=1682
1146+536=1682
1226+456=1682
So we have a match.
Now to work out why the fat.format can work with 536, but not with 496
EDIT: Also, need to determine why some roms require certain PIT files. Only possibility I can see is that junk in the header - could be some type of allow list for firmwares. The 803 PIT should therefore work on all firmwares, since it just has 00s. Maybe.
In 803.pit (compared to the .512 one) the system partition size has been increased by 10MB, while DBDATA partition size has been decreased the same amount (10MB).
PS: Dump the BML2 partition. The dump contains current partition mapping.
Hope this helps
RyanZA said:
Nice, that gives us
FACTORYFS
803 : 04 A2 : 1186
512 : 04 7A : 1146
513 : 04 CA : 1226
DBDATA
803 : 01 F0 : 496
512 : 02 18 : 536
513 : 01 C8 : 456
1186+496=1682
1146+536=1682
1226+456=1682
So we have a match.
Now to work out why the fat.format can work with 536, but not with 496
EDIT: Also, need to determine why some roms require certain PIT files. Only possibility I can see is that junk in the header - could be some type of allow list for firmwares. The 803 PIT should therefore work on all firmwares, since it just has 00s. Maybe.
Click to expand...
Click to collapse
I think the main cause is that some firmwares simply don't fit in the space reserved for them. Some of the m have larger system, some of them have larger dbdata partitions. Only a guess though, I think I start flashing pit files just for fun...
RazvanG said:
In 803.pit (compared to the .512 one) the system partition size has been increased by 10MB, while DBDATA partition size has been decreased the same amount (10MB).
Hope this helps
Click to expand...
Click to collapse
10MB = 40 units... That would give us 1 unit = 256kbyte. Nice.
So this means:
BOOT (bml01) = 01 = 1 = 0.25 MB (bootloader)
PIT (bml02) = 01 = 1 = 0,25 MB (the partition table)
EFS (bml03) = 28 = 40 = 10 MB (imei data and such)
SBL (bml04) = 05 = 5 = 1,25 MB (secondary bootloader)
SBL2 (bml05) = 05 = 5 = 1,25 MB (secondary bootloader backup)
PARAM (bml06) = 14 = 20 = 5 MB (the images shown when something is wrong)
KERNEL (bml07) = 1E = 30 = 7,5 MB (kernel image)
RECOVERY (bml08) = 1E = 30 = 7,5 MB (kernel image backup)
FACTORYFS (bml09) = 47A = 1146 = 286,5 MB (/system)
DBDATA (bml10) = 218 = 536 = 134 MB (/dbdata)
CACHE (bml11) = 8C = 140 = 35 MB (/cache)
MODEM (bml12) = 32 = 50 = 12,5 MB (software for wireless)
total: 501 MB
sztupy said:
I think the main cause is that some firmwares simply don't fit in the space reserved for them. Some of the m have larger system, some of them have larger dbdata partitions. Only a guess though, I think I start flashing pit files just for fun...
Click to expand...
Click to collapse
Not sure how true this can be -- Take 512 vs 513 for example. Newer Eclair roms stopped working on 513, and required 512. However, 513 has a smaller dbdata and larger system than 512. Since we know that a clean rom when flashed has a /dbdata of around 2mb, or 1% or so of available space, it can't be space related.
Must be more to than simple space allocations.
EDIT: And 501MB means we have space left over. Where is it hiding?
RyanZA said:
Not sure how true this can be -- Take 512 vs 513 for example. Newer Eclair roms stopped working on 513, and required 512. However, 513 has a smaller dbdata and larger system than 512. Since we know that a clean rom when flashed has a /dbdata of around 2mb, or 1% or so of available space, it can't be space related.
Must be more to than simple space allocations.
EDIT: And 501MB means we have space left over. Where is it hiding?
Click to expand...
Click to collapse
Yes, but the flashed dbdata.rfs was probably actually a large partition, that didn't fit into the allocated space.
Yes, the missing 11MB is strange, unless there is a 1MB "safety" gap between two partition (12 partitions = 11 gaps), or some other data.
EDIT: No, dumped BML0, it's only 501MB in length. The missing part might still be some space needed for the BML and STL to work.
Hi. I'm sorry for hijacking this thread but I need professional help from some geniuses (genii) and apparently you guys are firmware gurus.
Once you guys figure out how PIT files work, can you please help me figure out how to force flash Korean firmware onto an international phone without bricking it? The reason why I would like to do this, is because the Korean version has some really nice features for example native call recording (3rd party call recorders have bad quality). I made a thread for it here
Thanks a lot, köszönöm szépen!
Galaxy S I9000 PIT structure:
512.pit
PBL: 256KB (Primitive Bootloader)
PIT: 256KB
EFS: 10240KB (Non Volatile Memory)
SBL(1): 1280KB (Primary)
SBL(2): 1280KB (Backup)
PARAM: 5120KB
KERNEL(1): 7680KB (Primary)
KERNEL(2): 7680KB (Backup)
FACTORYFS: 293376KB
DBDATAFS: 137216KB
CACHE: 35840KB
MODEM: 12800KB
Total: 513024KB
513.pit
PBL: 256KB
PIT: 256KB
EFS: 10240KB
SBL(1): 1280KB
SBL(2): 1280KB
PARAM: 5120KB
KERNEL(1): 7680KB
KERNEL(2): 7680KB
FACTORYFS: 313856KB
DBDATAFS: 116736KB
CACHE: 35840KB
MODEM: 12800KB
Total: 513024KB
803.pit
PBL: 256KB
PIT: 256KB
EFS: 10240KB
SBL(1): 1280KB
SBL(2): 1280KB
PARAM: 5120KB
KERNEL(1): 7680KB
KERNEL(2): 7680KB
FACTORYFS: 303616KB
DBDATAFS: 126976KB
CACHE: 35840KB
MODEM: 12800KB
Total: 513024KB
In case there is backup blocks (e.g SBL and Kernel, Odin flashes them both while executing the flashing process).
dillovic said:
Hi. I'm sorry for hijacking this thread but I need professional help from some geniuses (genii) and apparently you guys are firmware gurus.
Once you guys figure out how PIT files work, can you please help me figure out how to force flash Korean firmware onto an international phone without bricking it? The reason why I would like to do this, is because the Korean version has some really nice features for example native call recording (3rd party call recorders have bad quality). I made a thread for it here
Thanks a lot, köszönöm szépen!
Click to expand...
Click to collapse
Galaxy S M110S is completely different hardware.
All other I9000 variants use Infineon X-Gold 616 baseband (Modem), while M110S uses Qualcomm baseband chip.
Made a try modifying the PIT file, to add more space to /dbdata and take away space from /system. I added around 25MB extra space to /dbdata.
Wasn't that hard actually, and I didn't encounter many problems (except the fact that the values are for the bare bml device, from which the stl has an extra 4-10% overhead so instead of the originally planed 35MB I could only spare 25).
If anyone's interested I can upload the modified pit and rom files.
Some remarks / questions:
- If we use the bare BML device instead of the STL I know we lose wear leveling (at least according to the rfs docs from samsung), but can't we use yaffs or similar on those devices? Or what if we (can we?) use cramfs for the /system on the BML, to gain even more space we could use for the /dbdata partition?
- The overhead the STL has seems a bit random to me. /system and /dbdata has a 4% overhead, while /cache a 10% one.
I'd be careful about resizing the partitions manually. Samsung should have aligned the partitions for best performance.
I'm not sure if its a placebo, but PIT 512 seems faster to me than PIT 803.
hardcore said:
I'd be careful about resizing the partitions manually. Samsung should have aligned the partitions for best performance.
I'm not sure if its a placebo, but PIT 512 seems faster to me than PIT 803.
Click to expand...
Click to collapse
Aligning should not be terribly hard -- we already specify using 256kb pieces instead of raw bytes. The alignment therefore is somewhere between 256kb and 4mb. If we align for 4mb, we align for everything smaller too. So as long as the numbers used are cleanly divisible by 4*4=16, it will be correctly aligned.
Flashing a PIT file with repartition checked seems to (according to docs) reset the wear leveling (the current record of what was written where, I guess), so you should not tick repartition if you are flashing many times in a row. (Many times is probably some very big number.)
I can't see why we couldn't use YAFFS or similar filesystem. Might work really well. I've got no experience setting up YAFFS though, and I don't believe it is trivial.
RyanZA said:
Aligning should not be terribly hard -- we already specify using 256kb pieces instead of raw bytes. The alignment therefore is somewhere between 256kb and 4mb. If we align for 4mb, we align for everything smaller too. So as long as the numbers used are cleanly divisible by 4*4=16, it will be correctly aligned.
Flashing a PIT file with repartition checked seems to (according to docs) reset the wear leveling (the current record of what was written where, I guess), so you should not tick repartition if you are flashing many times in a row. (Many times is probably some very big number.)
I can't see why we couldn't use YAFFS or similar filesystem. Might work really well. I've got no experience setting up YAFFS though, and I don't believe it is trivial.
Click to expand...
Click to collapse
I wonder if it is possible to make very small /system partition, and move it to mmcblk0 - since it is read only, performance will be ok. And make large dbdata partition, and keep /data/data there. That may be the ultimate lag fix
Sent from my GT-I9000 using XDA App
vitalij said:
I wonder if it is possible to make very small /system partition, and move it to mmcblk0 - since it is read only, performance will be ok. And make large dbdata partition, and keep /data/data there. That may be the ultimate lag fix
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
It is possible, but how would you flash a firmware then?
We are quickly approaching the 'throw it all away, and start from scratch with our own tools and bootloader.
RyanZA said:
It is possible, but how would you flash a firmware then?
We are quickly approaching the 'throw it all away, and start from scratch with our own tools and bootloader.
Click to expand...
Click to collapse
So are u guys planning to release the new galaxy s series phone??
You should rename it to galaxy-xda
So, from the info you have gathered, is there any point in using a PIT file when repartition is not checked?
huxflux2003 said:
So, from the info you have gathered, is there any point in using a PIT file when repartition is not checked?
Click to expand...
Click to collapse
I don't really see much point, but than again PIT file will tell odin (if your flashing pda) explicitly where the kernel should be flashed.
Also, I noticed that kernel partition is only 7.5-6 mb. Doest it mean that we cant use larger kernels (cos I think voodoo might me larger - hence the screen tear on boot).
Hello users,
How do i turbo boost my Android OS on my HOX?
When i rooted it it feels very fast, but when i restored all my apps it was noticeable slower than before.
How can i make it a lot faster and closer to the 'fasteness' of a fresh installed os without losing many apps?
maybe there is a list of apps that are very CPU and RAM intensive?
Here is the list of all my 3 party apps that i have installed:
Code:
cm.aptoide.pt
com.QuiteHypnotic.SilentTime
com.Tim.Koers.Silence (App i made my self)
com.Tim.Koers.beatbooster (App i made my self)
com.Tim.Koers.minitoolbox (App i made my self)
com.Tim.Koers.notebook (App i made my self)
com.Tim.Koers.wifiinfo (App i made my self)
com.beepbeepgo.pilot
com.brother.mfc.brprint
com.chrome.beta
com.cleanmaster.mguard
com.creativemobile.DragRacing
com.desaxedstudios.bassbooster
com.dotsandlines.carbon
com.ea.bf3bl.bv
com.fingersoft.hillclimb
com.gameinsight.airport
com.gameinsight.mycountry
com.gameinsight.mycountry2020
com.gau.go.launcherex.gowidget.taskmanagerex
com.google.android.apps.authenticator2
com.google.zxing.client.android
com.instagram.android
com.integer3d.dirtroadtrucker
com.jrummy.apps.memory.manager
com.jrummy.busybox.installer
com.keramidas.TitaniumBackup
com.macropinch.pearl
com.metago.astro
com.mobage.ww.a560.tinytower_android
com.mobage.ww.a987.PocketPlanes_Android
com.mxtech.ffmpeg.v7_vfpv3d16
com.mxtech.videoplayer.ad
com.news.rssfeedreader
com.nianticproject.ingress
com.nxp.taginfolite
com.path
com.paypal.android.p2pmobile
com.reader.androidworldtab
com.rerware.android.MyBackup
com.rockolabs.adbkonnect
com.rootuninstaller.free
com.sgiggle.production
com.skype.raider
com.snapchat.android
com.socialquantum.acityint
com.sparklingsociety.cityislandairport
com.tapatalk.tapatalk4
com.ttxapps.dropsync
com.utorrent.client
com.viber.voip
com.whatsapp
com.xuecs.ContactHelper
com.yandex.store
deezer.android.app
evz.android.wifi_credentials_recovery
me.youichi.realtimelogcat.ad
net.roamler
nl.sanomamedia.android.nu
nl.schoolmaster.meta
org.exobel.routerkeygen
org.projectvoodoo.otarootkeeper
robj.floating.notifications
Active services (couldn't show the 3 party active packages/services if somebody knows how to do that please comment!):
Code:
Found 80 services:
0 sip: [android.net.sip.ISipService]
1 htctelephony: [com.android.internal.telephony.IHtcTelephony]
2 phone: [com.android.internal.telephony.ITelephony]
3 htctelephonyinternal: [com.android.internal.telephony.IHtcTelephonyInternal]
4 iphonesubinfo: [com.android.internal.telephony.IPhoneSubInfo]
5 simphonebook: [com.android.internal.telephony.IIccPhoneBook]
6 isms: [com.android.internal.telephony.ISms]
7 nfc: [android.nfc.INfcAdapter]
8 wireless_display: [com.htc.service.IWirelessDisplayService]
9 commontime_management: []
10 userbehavior: [com.htc.utils.ulog.IUserBehaviorLoggingService]
11 samplingprofiler: []
12 diskstats: []
13 appwidget: [com.android.internal.appwidget.IAppWidgetService]
14 backup: [android.app.backup.IBackupManager]
15 uimode: [android.app.IUiModeManager]
16 serial: [android.hardware.ISerialManager]
17 usb: [android.hardware.usb.IUsbManager]
18 audio: [android.media.IAudioService]
19 wallpaper: [android.app.IWallpaperManager]
20 dropbox: [com.android.internal.os.IDropBoxManagerService]
21 search: [android.app.ISearchManager]
22 country_detector: [android.location.ICountryDetector]
23 location: [android.location.ILocationManager]
24 SUPL_SERVICE: []
25 devicestoragemonitor: []
26 display: [android.os.IDisplayService]
27 notification: [android.app.INotificationManager]
28 updatelock: [android.os.IUpdateLock]
29 throttle: [android.net.IThrottleManager]
30 servicediscovery: [android.net.nsd.INsdManager]
31 connectivity: [android.net.IConnectivityManager]
32 usbnet: [com.htc.net.usbnet.IUsbnetController]
33 wifi: [android.net.wifi.IWifiManager]
34 wifip2p: [android.net.wifi.p2p.IWifiP2pManager]
35 netpolicy: [android.net.INetworkPolicyManager]
36 netstats: [android.net.INetworkStatsService]
37 textservices: [com.android.internal.textservice.ITextServicesManager]
38 network_management: [android.os.INetworkManagementService]
39 clipboard: [android.content.IClipboard]
40 statusbar: [com.android.internal.statusbar.IStatusBarService]
41 device_policy: [android.app.admin.IDevicePolicyManager]
42 lock_settings: [com.android.internal.widget.ILockSettings]
43 mount: [IMountService]
44 gesture: [com.htc.service.IGestureService]
45 accessibility: [android.view.accessibility.IAccessibilityManager]
46 input_method: [com.android.internal.view.IInputMethodManager]
47 bluetooth_a2dp: [android.bluetooth.IBluetoothA2dp]
48 bluetooth: [android.bluetooth.IBluetooth]
49 input: [android.hardware.input.IInputManager]
50 window: [android.view.IWindowManager]
51 alarm: [android.app.IAlarmManager]
52 htchardware: [android.os.IHtcHardwareService]
53 vibrator: [android.os.IVibratorService]
54 battery: []
55 hardware: [android.os.IHardwareService]
56 content: [android.content.IContentService]
57 account: [android.accounts.IAccountManager]
58 permission: [android.os.IPermissionController]
59 cpuinfo: []
60 dbinfo: []
61 gfxinfo: []
62 meminfo: []
63 activity: [android.app.IActivityManager]
64 package: [android.content.pm.IPackageManager]
65 scheduling_policy: [android.os.ISchedulingPolicyService]
66 telephony.registry: [com.android.internal.telephony.ITelephonyRegistry]
67 htcdeviceinfo: [android.app.IHtcDeviceInfoManager]
68 HtcAppUsageStatsService: [com.android.internal.app.IHtcAppUsageStatsService]
69 usagestats: [com.android.internal.app.IUsageStats]
70 batteryinfo: [com.android.internal.app.IBatteryStats]
71 power: [android.os.IPowerManager]
72 entropy: []
73 sensorservice: [android.gui.SensorServer]
74 media.audio_policy: [android.media.IAudioPolicyService]
75 media.camera: [android.hardware.ICameraService]
76 SurfaceFlinger: [android.ui.ISurfaceComposer]
77 media.player: [android.media.IMediaPlayerService]
78 media.audio_flinger: [android.media.IAudioFlinger]
79 drm.drmManager: [drm.IDrmManagerService]
If somebody has recommendations about apps and how to make them consume less CPU and RAM, feel free to post. and you'll help me and a lot more people!
Thanks,
Tim
Use the TURBO BOOST MOD from Android Development section.
Sent from my HTC One X using Tapatalk 4 Beta
Is that a custom ROM or do you need to flash anything? I'd like to have my system as original as posible.
But i'll take a look!
Thanks
EDIT: Does it really works that well?
tim687 said:
Hello users,
How do i turbo boost my Android OS on my HOX?
When i rooted it it feels very fast, but when i restored all my apps it was noticeable slower than before.
How can i make it a lot faster and closer to the 'fasteness' of a fresh installed os without losing many apps?
maybe there is a list of apps that are very CPU and RAM intensive?
Here is the list of all my 3 party apps that i have installed:
Tim
Click to expand...
Click to collapse
tim687 said:
Is that a custom ROM or do you need to flash anything? I'd like to have my system as original as posible.
But i'll take a look!
Thanks
EDIT: Does it really works that well?
Click to expand...
Click to collapse
Turbo boost is not a custom rom. It works as an 'add-on' to your existing rom and does not change anything on the ui of the phone. If you didn't know it was installed you would not know it was there, except the phone maybe more responsive. Basically it uses the spare cache, data and system memory as the swap file instead of the SD card. This (in theory) improves the read/write time for the swap file as phone memory is much faster.
To install it just down load the zip file and flash it from recovery. During the setup you select how much memory you want to use (it gives a recommendation though) and thats it.
http://forum.xda-developers.com/showthread.php?t=2145133
Hi, my Wave 3 closes when I do random stuff, for example watching a video, sending messages, etc. and when I open it battery level is low. But when It's on charge it dosen't restarts. Anyone have any idea why is this happening? I use S4 style TurkoCWF rom. Thanks.
Phenomen.B said:
Hi, my Wave 3 closes when I do random stuff, for example watching a video, sending messages, etc. and when I open it battery level is low. But when It's on charge it dosen't restarts. Anyone have any idea why is this happening? I use S4 style TurkoCWF rom. Thanks.
Click to expand...
Click to collapse
i have the same problem
*#33284*#
Set Debug Level to:
High
Now Chance Blue Screen gives more info...
1 way is RDX Tool...
Or take picture with Cam...
or Copy and Paste...
Best Regards
---------- Post added at 03:31 PM ---------- Previous post was at 02:44 PM ----------
what blue screen? I dont get no blue screen, only keeps restarting till i put it on charge. Thanks
Click to expand...
Click to collapse
No idea, you enter this Code into your S8600?
Code:
*#33284*#
Yes or no?
RDX Tool is this...
http://forum.xda-developers.com/showpost.php?p=39658811&postcount=23
Sorry, my fault. Forgotten to insert Link.
If S8600 is in Debug Level High... Then Power down for instance should show you Blue Screen...
Now you know what Blue Screen means...
If "luck", this could help by some kind of Errors... to create Messages from handset...
Example... forgotten why or when, but it was my S8600...
Code:
Type : Unofficial Version
Number : 1096
Builder : superuser
Host : S1-AGENT05
Date : 2011/10/26
Time : 17:26:52
Size : 55050240 bytes
CheckSum : 0x0d3edb3f
View :
S/W version:S8600+XX+KJC
Modem:KYRZ213006_05A
SHP:VPP R5 2.1.1
Build Host:S1-AGENT05
BuildAt:2011/10/26 17:26:52
App Debug Level : 0
Data Abort!Page Translation Fa
ult for (0x743f5abc) Read Acce
ss Detection
<Callstack information>
PC = 00EB9E14 _printf_str
LR = 00EBA779 _printf_cs_commo
n
<Mocha Task Callstack>
_printf_cs_common
__printf
_printf_char_common
_printf_fp_hex_real
__MemPartitionGetNextUserAlloc
Ptr
_snprintf
0x002C7972+Dolfin.so
0x00256F6C+Dolfin.so
0x002C7972+Dolfin.so
0x00256F6C+Dolfin.so
OemBmShutdown
BootDestroy
Best Regards
It only shows "Upload data to PC" and that's all. And yes, I used the code u gaved me. Thanks
When I use camera flash it crashes all the times...
Phenomen.B said:
It only shows "Upload data to PC" and that's all. And yes, I used the code u gaved me. Thanks
When I use camera flash it crashes all the times...
Click to expand...
Click to collapse
yep. that happend to me to..
when want to use flash, just it restarts..
Upload data to PC
Click to expand...
Click to collapse
Simple start Tool RDX from here...
http://forum.xda-developers.com/showpost.php?p=39658811&postcount=23
It autodetect Wave...
But if RDX nothing detect in Upload data to PC...
RDX find something and shows something like on Screenshot?
Best Regards
Here:
Code:
Type : Unofficial Version
Number : 1117
Builder : dpi
Host : DELL44
Date : 2013/01/14
Time : 16:54:24
Size : 55050240 bytes
CheckSum : 0x0d284432
View :
S/W version:S8600+FR+MA2
Modem:KYRZ213006_05A
SHP:VPP R5 2.1.1
Build Host:DELL44
BuildAt:2013/01/14 16:54:24
App Debug Level : 0
Data Abort!Page Translation Fa
ult for (0x74543390) Read Acce
ss Detection
<Callstack information>
PC = 00EBAD60 _printf_str
LR = 00EBB6C5 _printf_cs_commo
n
<Mocha Task Callstack>
_printf_cs_common
__printf
_printf_char_common
_printf_fp_hex_real
__MemPartitionGetNextUserAlloc
Ptr
_snprintf
OemBmShutdown
BootDestroy
_WmCallEHFunction
__WmEventHandlerProc
__WmProcessEventInternal
rex_task_free
OemOsLeaveCriticalSection
OsLeaveCriticalSection
WmProcessEvent
OemOsLeaveCriticalSection
OsLeaveCriticalSection
OemOsReleaseMutex
WmExitEventHandler
__BootTimerCallback
__WmProcessTimerEvent
__WmProcessEventInternal
OsReceiveMessageInternal
__WmReceiveEventInternal
WmMainLoop
MochaTask
rex_thread_init
__thread_stub
Pager Stat: Total Page(4864),
Total RAM page(3584), Total Di
sk Page(1280). One Page Size(6
5536)B
Pager Stat: Used RAM page(coun
t :1295, 5180 KB), Used Disk P
age(count :0, 0KB)
Pager Stat: Free Page(count :3
569, 228416 KB)
< Heap 0 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 266,338,304 (Bytes)
MemPrintStat: Allocated size
= 50,159,616 (Bytes)
MemPrintStat: Available size
= 195,092,480 (Bytes)
MemPrintStat: Peak allocated s
ize = 77,725,696 (Bytes)
__MemPoolPrtAllocInfo: freeMax
Size = 195092480
__MemPoolPrtAllocInfo : Huge A
llocated Chunks more then (163
8400)Bytes
"RsrcBitmap.c":line(105) allo
cated (2070016) Bytes
"RsrcBitmap.c":line(105) allo
cated (2070016) Bytes
"..\..\..\..\ShpBrowser\Dolfi
n\Platform\Abstract\BAL\Src\Co
mmon\SFBalFontTTF.cpp":line(19
7) allocated (3505536) Bytes
__MemPoolPrtAllocInfo : Please
Check above chunks
< Kernel Heap(cache+no cache)
of Information Print Start >
MemPrintStat: Total heap size
= 83,886,080 (Bytes)
MemPrintStat: Allocated size
= 9,928,704 (Bytes) (11%)
MemPrintStat: Available size
= 43,016,192 (Bytes)
MemPrintStat: Peak allocated s
ize = 14,360,576 (Bytes) (17%)
MemPrintStat: Fragmentation le
vel = 18 (%)
< Kernel Heap(cache+no cache)
of Information Print Start >
MemPrintStat: Total heap size
= 83,886,080 (Bytes)
MemPrintStat: Allocated size
= 21,078,016 (Bytes) (25%)
MemPrintStat: Available size
= 43,016,192 (Bytes)
MemPrintStat: Peak allocated s
ize = 25,591,808 (Bytes) (30%)
MemPrintStat: Fragmentation le
vel = 18 (%)
< Kernel Heap 3 of Information
Print Start > (0)
MemPrintStat: Total heap size
= 10,354,688 (Bytes)
MemPrintStat: Allocated size
= 3,722,072 (Bytes) (35%)
MemPrintStat: Free size = 6,6
32,616 (Bytes) (64%)
MemPrintStat: Peak allocated s
ize = 4,619,988 (Bytes) (44%)
MemPrintStat: Fragmentation le
vel = 0 (%)
< Heap 4 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 134,217,728 (Bytes)
MemPrintStat: Allocated size
= 15,826,944 (Bytes)
MemPrintStat: Available size
= 117,112,832 (Bytes)
MemPrintStat: Peak allocated s
ize = 15,826,944 (Bytes)
< Heap 6 of Process(0) Informa
tion Print Start >
MemPrintStat: Total heap size
= 125,829,120 (Bytes)
MemPrintStat: Allocated size
= 8,290,304 (Bytes)
MemPrintStat: Available size
= 117,317,632 (Bytes)
MemPrintStat: Peak allocated s
ize = 8,290,304 (Bytes)
Thanks for your time
Code:
Type : Unofficial Version
Number : 1117
Builder : dpi
Host : DELL44
Date : 2013/01/14
Time : 16:54:24
Size : 55050240 bytes
CheckSum : 0x0d284432
View :
S/W version:[B]S8600+FR+MA2[/B]
Modem:KYRZ213006_05A
SHP:VPP R5 2.1.1
Build Host:DELL44
BuildAt:2013/01/14 16:54:24
@Galaxy3HELL
You use also same Firmware?
S8600+FR+MA2
I use S4 style TurkoCWF rom.
Click to expand...
Click to collapse
The custom Version?
@Phenomen.B
We should short wait for answer from Galaxy3HELL...
If both used same Firmware, then maybe Firmware issue...
Solution 1. in theory.
If your Firmware long runs without Errors... then flash again.
So you have clean Version...
Like "Format C:"...
Bad is, you have to Backup before... as you loose all your SMS, Pics etc.
Test 1.1 would be Stockfirmware... unmodified...
XXKJC for instance...
Clean Fullfimware... with Bootfiles...
So it could be easier to find out if Hardware damage... or really only Software issue...
Best Regards
I flashed again but problems are the same.
And I have no full official firmware...
S8600XXKJC_OXA.rar
Try Google...
Maybe you can download from here:
http://uploaded.net/file/qfls8t4d
Not tested by me... I mean exact this Link.
Here you can see, what files inside... + folder Bootfiles...
http://chomikuj.pl/krzak208/Samsung+Wawe3+(S8600)/XXKJC
Best Regards
Yes, i was using Turko FRMA2, but because of problem i flashed full firmware XXKJC and problem still active :victory:
okidoki...
XXKJC is not "latest"...
It is older...
Only good thing about XXKJC is, it is Full with all files + Boot...
Nearly all other available Firmware are only Update... without FFS and full SHP...
So update from XXKJC to XXLD1...
Maybe then more luck...
Best Regards
link for that software?
To find XXLD1 for S8600, please use Google...
Samfirmware/Sammobile...
But when It's on charge it dosen't restarts.
Click to expand...
Click to collapse
Same for you Galaxy3HELL
If USB or Charger attached?
Maybe this means some problems with Power... no constant Energy...
Remove battery... check contacts etc...
Is S8600 flying from... Any kind of scratches...
Check Label for Waterdamage...
Best Regards
adfree said:
If USB or Charger attached?
Click to expand...
Click to collapse
Same with both, it dosen't matter if USB or charger, it will not restart if one of those 2 is attached.
Hmm...
Phenomen.B said:
Same with both, it dosen't matter if USB or charger, it will not restart if one of those 2 is attached.
Click to expand...
Click to collapse
Then, I think that might be a battery problem, bro.
[ JUST A WHIRL : Try cleaning the contacts with a dry cloth, just as a last try. If possible, if anyone else you know has a wave 3, try checking it with his/her wave's battery. ]
TheBasterd said:
Then, I think that might be a battery problem, bro.
[ JUST A WHIRL : Try cleaning the contacts with a dry cloth, just as a last try. If possible, if anyone else you know has a wave 3, try checking it with his/her wave's battery. ]
Click to expand...
Click to collapse
Yup, it's a battery problem. Tommorow i'll go and buy new one. Thanks all for ur help.
Phenomen.B said:
Yup, it's a battery problem. Tommorow i'll go and buy new one. Thanks all for ur help.
Click to expand...
Click to collapse
@Phenomen.B please post you result with new battery. If it solve the problem, i will buy one to :good: Waiting for you answer :laugh:
did you buy new battery and did it solve you problem? :fingers-crossed:
yes it is battery problem :laugh:
i sold phone for 40$, and guy which buy it changed battery and said that it is working fine now
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