Related
One man has successfully integrated WM6 modules into XIP of hx4700. The result: working WM5 with WM6 modules from "msxipkernel" package (taken from Universal)
Maybe his method can help us to port WM6 on Himalaya?
(Original thread: http://4pda.ru/forum/index.php?showtopic=44886)
Here is what he did (translate from russian):
1. Take "xipport". Modified one is attached.
2. dump xip & build maps for hx4700. Save "map.txt"
3. dump xip & build maps from wm6 xip (HTC Universal or any other device)
4. Just copy all modules and those ".txt" files from msxipkernel (wm6) except "cachefilt", "encfilt", "filesys".
5. "realloc P" & write maps (it works for hx4700). If not enough mem for realloc - then increase "physlast" in "romhdr.txt"
6. In new "map.txt" addresses of regions in section "first Dll... last Dll" for 4 files in "oemxipkernel" must stay unchanged, for example:
---
01fe1000 - 01fe2000 L00001000 actual of region_1 Fsdspy.dll
01fe2000 - 01fef000 L0000d000 actual of region_1 msflash.dll
01fef000 - 01ff0000 L00001000 actual of region_2 cecompr.dll
01ff0000 - 01ff1000 L00001000 actual of region_1 ceddk.dll
---
If they are not then fix in corresponding "imageinfo.txt" value of o32[1(2)].o32_realaddr
7. Repeat the same for all files in "msxipkernel". We need that "actual of region_1" correspond with "map.txt" (wm6). For files "pm.dll" and "regenum.dll" will be "!!!!!!!!!!!!!" symbols.
8. Edit "o32[1].o32_realaddr" for "pm.dll" and "regenum.dll" to make there regions exactly concur with regions of excepted "cachefilt", "encfilt". Such a replacement. After all this section must be:
---
01fa01fe - 01fa01fe L00000000 Start: first DLL address
01fa01fe - 01fe1000 L00040e02 NUL
01fe1000 - 01fe2000 L00001000 actual of region_1 Fsdspy.dll
01fe2000 - 01fef000 L0000d000 actual of region_1 msflash.dll
01fef000 - 01ff0000 L00001000 actual of region_2 cecompr.dll
01ff0000 - 01ff1000 L00001000 actual of region_1 ceddk.dll
01ff1000 - 01ff2000 L00001000 actual of region_1 mspart.dll
01ff2000 - 01ff3000 L00001000 actual of region_1 imgfs.dll
01ff3000 - 01ff4000 L00001000 actual of region_1 fsreplxfilt.dll
01ff4000 - 01ff5000 L00001000 actual of region_1 fsdmgr.dll
01ff5000 - 01ff6000 L00001000 actual of region_1 fatutil.dll
01ff6000 - 01ff7000 L00001000 actual of region_1 fatfsd.dll
01ff7000 - 01ff8000 L00001000 actual of region_1 regenum.dll
01ff8000 - 01ff9000 L00001000 actual of region_1 diskcache.dll
01ff9000 - 01ffa000 L00001000 actual of region_1 devmgr.dll
01ffa000 - 01ffc000 L00002000 actual of region_1 crypt32.dll
01ffc000 - 01ffd000 L00001000 actual of region_1 coredll.dll
01ffd000 - 01ffe000 L00001000 actual of region_1 certmod.dll
01ffe000 - 01fff000 L00001000 actual of region_1 pm.dll
01fff000 - 02000000 L00001000 actual of region_1 busenum.dll
02000000 - 02000000 L00000000 End: last DLL address
---
9. Look into "map.txt" (Universal) to find where was the first region of "regenum"
---
01fef000 - 01ff0000 L00001000 actual of region_1 regenum.dll
---
If it was "0x1FEF000", and we changed it to "01ff7000". So we have to patch file. Edit "S000" of "regenum.dll" and fix all dword-aligned values that looks like: XX XF FE 01 to XX X7 FF 01 (so we see them in "winhex"). It can be automated with a simple script
10. Do the same for "S000" in "pm.dll"
11. Set in all "imageinfo.txt" cvalue of "e32_subsysminor" to 1.
12. Write new placement of "ROMHDR" into "S000" of "nk.exe"
13. Make ROM, flash and Try!
hx4700 wm6
hx4700 wm6, frankinstein style. interesting development anyone upto trying it?
hey Avis. He did not mention in his steps when to introduce cachefilt, etc.
could you possibly ask him to post the original XIP.bin and the WM6 XIP.bin; so, we could study further. (sorry, I don't speak Russian)
This is promising...
Jiggs
Oh, I get it. He didn't include cachefilt and stuff because he's still using WM5 system files...
step 12 is vague. write new placement of "ROMHDR" into S000 of "NK.EXE" BUT I couldn't locate any instance of the address of ROMHDR in S000!
hx4700 wm6
jiggs, sounds like you got skillz. can anyone help develop this solution? need to get more people aware of this..
jiggs said:
step 12 is vague. write new placement of "ROMHDR" into S000 of "NK.EXE" BUT I couldn't locate any instance of the address of ROMHDR in S000!
Click to expand...
Click to collapse
okay I got it. there is rom_00 hdr in map.txt those addresses are the ones I can locate in S000 nk.exe. However, I have flashed my deviced three (3) times already, but it won't boot nor even show the boot screen.
What is not clear to me is step 6. what is my reference map.txt: hima? or uni?
lyger said:
jiggs, sounds like you got skillz. can anyone help develop this solution? need to get more people aware of this..
Click to expand...
Click to collapse
tell bepe and tofclock, they're more experienced in porting...
did you use a hx4700 or a different device? Shame it didn't start-up.. anyone provide any insight on how this works?
Avis,
Could you please request for sample xip.bin's so we can study further?
Thanks in advance.
Jiggs
This method will not work in our Himalaya because we need nk.exe that is compatible with the new CORE. Unfortunately, our very old nk.exe is not compatible with WM6 CORE.
I realize this is about the Himalaya,
But does this mean we might have a working WM6 for the hx4700?
There are like thousands of people waiting on that. we've even signed petitions to try and get hp to do it :/
well if anyone needs help in porting wm6 to a wm5 device that has no wm6 kernel, i can try and help.
i've already contributed to some such projects which have been successful.
i suspect that you and Avis are the only ones working on it
http://forum.xda-developers.com/showthread.php?t=293352&page=3
Rudegar said:
i suspect that you and Avis are the only ones working on it
http://forum.xda-developers.com/showthread.php?t=293352&page=3
Click to expand...
Click to collapse
i was on holiday....how is the hx4700 port right now?
edit: ok i checked it out
For ATOM EXEC Only!
UPDATED DECEMBER 19, 2007
NEVER ATTEMPT TO UPDATE YOUR DEVICE USING SD CARD FLASHING!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROM: WM6.0 20071216A3WWE
DOWNLOAD 6MB PP (51.95 program memory) : rapidshare|mediafire
ROM: WM6.1 B19209 AKU 1.0.2 20080417A5WWE
DOWNLOAD 6MB PP (51.95 program memory) : see my signature
NOTE: IF YOU DON'T WANT TO DOWNLOAD AGAIN, YOU CAN CHANGE THE PAGEPOOL YOURSELF. INSTRUCTIONS HERE
BUG FIXES: OS 5.2.1938 (Build 18508.0.7b.0)
Features: WM6 Clean Edition
Camera Working Back.
Headset Working Back.
NETCF 3.5
New Device Software Update Utility - now you can choose what you want to update!! on this case mostly you only need either OS Only or OS + Extended ROM.
XIP Core Upgrade
Memory Boost Up to 20480 bytes.
Speed Improvement!!
Built-in SRS WOW HD
Built-in Power Management
Windows Live 10.6.33.0600
Extended ROM:
1. Fann Capture Screen Utility
2. Helmi Touch Dialer 2G
Bugs: A2DP is not 100% compatible. (some device working, some not)
Steps:
1. Uncompress the 7z file into C:\Windows\Temp
2. Verify the files, should be 6 files
3. Execute Device Software Update Utility.exe
4. Follow the rest steps.
Please charge your device after upgrade to 100% full before you comment the drain batteries on your device!!.
This UNOFFICIAL ROM is still under development and you can't expect support from it. If you can't afford to have a buggy phone, this is not for you. By flashing this TEST ROM, it means you are willing to take the risks, solve any bugs encountered yourself and report problems to this forum.
Like I had mentioned before in one of the ATOM thread, ATOM EXEC device can boost more memory. In order to do that we need to re adjust the memory address on nk.exe and giisr.dll like below (of course need to change S00x)
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80562000 L00000000 ------ start of RAM free space
80562000 - 84000000 L03a9e000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
For ATOM EXEC WM6 Cooker, you may used my XIP as a reference. you may take nk.exe and giisr.dll and port into your own XIP (increase about 500 KB)
For ATOM WM6 Cooker, you also will still able to gain more memory (about 20480 byte) by using my giisr.dll
please note: don't forget credit to me when you used my nk.exe and giisr.dll
so never less, I saw quite many people know how to cook WM6 on ATOM device, well I'm happy to see that. keep working boys!!
reserved for 3rd party standard applications
Hi mate, very nice, cant wait to try it out!
homer285 said:
Hi mate, very nice, cant wait to try it out!
Click to expand...
Click to collapse
it's up now
you can update into your own xip
sad to hear that until now you wasn't able to fix the A2DP...
vickoy said:
sad to hear that until now you wasn't able to fix the A2DP...
Click to expand...
Click to collapse
I'm afraid so, till someone build/crack the new A2DP WM6 driver for ATOM/EXEC Device.
vickoy said:
sad to hear that until now you wasn't able to fix the A2DP...
Click to expand...
Click to collapse
I think someone is working on this, out of interest what's your headset brand and model #, thanks.
Woa... Nice Updated, bro! Very interesting. Will try, now!
i think the links are backwards i.e the 8mb pagepool link directs to the 6mb pagepool download and vice versa
homer285 said:
I think someone is working on this, out of interest what's your headset brand and model #, thanks.
Click to expand...
Click to collapse
I am currently using sony ericsson HBH-DS220. So far, I can still use the current driver with my headset, I just need to do some trick... like for example if I need to used it to listen to music I just need to turn it off, run iplay and then turn it back on... quite irritating but no choice.
btw, having a value of 0 in A2DP settings of JointStereo is a lot more better and giving true stereo compare to value of 1, that was being suggested from the other thread.
yung_vu said:
i think the links are backwards i.e the 8mb pagepool link directs to the 6mb pagepool download and vice versa
Click to expand...
Click to collapse
yeah right! I just downloaded the 8MB pagepool but I've got here 6MB...LoL
chartreux said:
Like I had mentioned before in one of the ATOM thread, ATOM EXEC device can boost more memory. In order to do that we need to re adjust the memory address on nk.exe and giisr.dll like below (of course need to change S00x)
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80562000 L00000000 ------ start of RAM free space
80562000 - 84000000 L03a9e000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
For ATOM EXEC WM6 Cooker, you may used my XIP as a reference. you may take nk.exe and giisr.dll and port into your own XIP (increase about 500 KB)
For ATOM WM6 Cooker, you also will still able to gain more memory (about 20480 byte) by using my giisr.dll
please note: don't forget credit to me when you used my nk.exe and giisr.dll
so never less, I saw quite many people know how to cook WM6 on ATOM device, well I'm happy to see that. keep working boys!!
Click to expand...
Click to collapse
Thank you so much, downloading.......................
But it's better if you tell us how to do that ourself.
I replace my giisrd.dll by yours to my Atom, but nothing happens. what's the matter ? Do I need to change the nk.exe too ?
medkid said:
I replace my giisrd.dll by yours to my Atom, but nothing happens. what's the matter ? Do I need to change the nk.exe too ?
Click to expand...
Click to collapse
use xipport and click write map button.
chartreux said:
use xipport and click write map button.
Click to expand...
Click to collapse
I do write map but see that nothing changes
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80567000 L00005000 NUL
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
medkid said:
I do write map but see that nothing changes
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80567000 L00005000 NUL
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
Click to expand...
Click to collapse
your original XIP
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80566000 L00005000 NUL
80566000 - 80567000 L00001000 initialized data of region_1 giisr.dll
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
and now after copy my giisr.dll, your giisr.dll address already re-adjust to 80561000 from 80566000. (save 20480 bytes)
the next step you will need to adjust start of RAM free space to 80562000 (inside ROMHDR.txt)
chartreux said:
your original XIP
Code:
04000000 - 80500000 L7c500000 NUL
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80566000 L00005000 NUL
80566000 - 80567000 L00001000 initialized data of region_1 giisr.dll
80567000 - 80567000 L00000000 ------ start of RAM free space
80567000 - 84000000 L03a99000 NUL
84000000 - 84000000 L00000000 End: end of RAM
84000000 - 9ac00000 L16c00000 NUL
and now after copy my giisr.dll, your giisr.dll address already re-adjust to 80561000 from 80566000. (save 20480 bytes)
the next step you will need to adjust start of RAM free space to 80562000 (inside ROMHDR.txt)
Click to expand...
Click to collapse
Thanks for enlightening me.
I do it and now flashing my Atom again
after flashed:it seems that I don't see any difference, although MAP.txt has changed:
80500000 - 80500000 L00000000 Start: start of RAM
80500000 - 80506000 L00006000 uninitialized data of region_2 nk.exe
80506000 - 80561000 L0005b000 initialized data of region_3 nk.exe
80561000 - 80562000 L00001000 initialized data of region_1 giisr.dll
80562000 - 80562000 L00000000 ------ start of RAM free space
80562000 - 84000000 L03a9e000 NUL
and the ROMHDR.txt:
Code:
dllfirst: D=01F901FD
dlllast: 02000000
physfirst: P=9AC00000
physlast: 9AFE2990
nummods: (00000018)
ulRAMStart: R=80500000
ulRAMFree: 80562000
ulRAMEnd: 84000000
ulCopyEntries: (00000002)
ulCopyOffset: P+00117FDC
ulProfileLen: 00000000
ulProfileOffset: 00000000
numfiles: (00000008)
ulKernelFlags: 00000002
ulFSRamPercent: 00000004
ulDrivglobStart: 00000000
ulDrivglobLen: 00000000
usCPUType: 000001C2
usMiscFlags: 00000002
pExtensions: P+0000271C
ulTrackingStart: 00000000
ulTrackingLen: 00000000
84000000 - 84000000 L00000000 End: end of RAM
downloading the 6mb pagepool and gonna try it a bit.
thnx for ur hard work chartreaux
hey man
Thanks!!!!BUT
why my camara doestn't work after the updated
nb: try it at your own risk,.
Okay, here i'll describe how to port XIP and SYS folder to build your fresh new ROM,.
- for a newbie, why do we need to port this? "its necessary to make a new OS and build"
ex: CE OS 5.2.2000 Build 20000.1.0.0
Then lets start working out,.
What do you need?
Atom WM6 Kitchen (see the usage and how to use HERE)
Hypercore Kitchen (see the usage and how to use HERE)
M'reloc (see the usage and how to use HERE)
Already have it all?
continue this step by step then,.
You have to extract the XIP from the source that usually came from OS.nb file (downloaded ROM that have a newer OS and build), here is the step by step,.
nb: The safest way, is to change the coredll.dll only, if you wish to change all of it, its up to you,.
1. Extract XIP.BIN from the source, by using XIP_Extract found in hypercore\tools\convert\XIP_extract,.
Code:
RomMaster.exe OS.nb. -w 5 -b 0x00310000 -x -o xip.bin
---------> There, you'll see a "command program", run it, then write like above,.
2. Run "XIPPort" then select "dump xip.bin", there, you'll have a new folder named "OUT" that contains with 2 folders inside, "FILES" and "MODULES",.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------> What's inside the FILES folder? it is the XIP that needed for building imgfs, to create diskimage_Ver.nb0, and make your device booting,.
---------> What's inside the MODULES folder? it is the module, that your device performance and works, depend on, so becareful okay,.
3. Open M'reloc, choose module coredll.dll inside "MODULES" folder,.
---------> there, you have to change the V and D base, become atom V and D base (For Atom, V=03F4E000 , D=01FFC000)
---------> and, you have to change the V and D base, in the imageinfo.txt (inside the modules folder)
4. Copy coredll.dll and coredll.dll.txt and do the next step,.
Then, its time for you to change your diskimage_Ver.nb0 XIP, here's the step by step,.
1. Extract XIP.BIN from your diskimage_Ver.nb0, by run program "romtoolz" inside the TOOLS folder (Atom WM6 Kitchen),.
---------> Choose the source (diskimage_Ver.nb0),.
---------> Then choose where do you wan the xip.bin to be extracted,.
2. Run XIPPort (you could find it in the same folder), then select "Dump Xip.bin" , you'll see new folder created, named "OUT" that contains with 2 folders inside ("FILES" and "MODULES")
------------------- its just like step number 2 above ----------------
3. Copy the file that have been M'reloced (coredll.dll and coredll.dll.txt) into MODULES folder, then, select "Realloc P" then, select "Write Maps",.
---------> Open MAP Physical.txt, try to find, is there any "!!!!", if you have it, try to check, have you m'reloc the module correctly? and try to select "Realloc P" then "Write Maps" again,.
4. Select "build xip_out.bin" , you will have a new files named "xip.out.bin",.
------------------- Screenshot above (right) ----------------
5. Select "write xip_out.bin to:" then write like this,.
------------------- Screenshot above (right) ----------------
---------> 0018000C ----------> This is the default xip address for XDA ATOM
---------> diskimage_Ver.nb0 --> Means that the xip.out.bin will be written to the file named diskimage_Ver.nb0
nb: All this stuff must be located in one folder (diskimage, xipport, etc) or it wont work,.
----- finally, now you have a new OS ready to update your device ROM,. -----
GOOD LUCK,.
Happy ROM Cooking to all of you,.
- Kumara -
reserved,.
reserved too,.
Garmin said:
---------> 0018000C ----------> This is the default xip address for XDA ATOM
Click to expand...
Click to collapse
It's the same thing for Kaiser ?
Thanks Garmin , another STICKY! ,waiting for you to complete this btw i need the link to build 2000 too , PM me hehe
Many thx for this, looking forward to read the complete version Please upload the necessary apps or link to where to find aswell
regards
yass
MickyMax said:
It's the same thing for Kaiser ?
Click to expand...
Click to collapse
no no no no,.
its not the same,.
try to ask someone expeienced on it, try to ask the addres of OS.nb for kaiser,. is not that actually,.
but, the procedure was just same,.
thanks,.
Garmin said:
no no no no,.
its not the same,.
try to ask someone expeienced on it, try to ask the addres of OS.nb for kaiser,. is not that actually,.
but, the procedure was just same,.
thanks,.
Click to expand...
Click to collapse
Thank you
It's so nice to see this.
May I ask how to deal with in cooking the xip part of Atom XDA LIFE?
Thanks!
Thank you for the nice screenshots
Any one got a link to Jiggs's kitchen ?
Garmin, can you please upload Jigg's Kitchen?
regards
yass
lnks said:
It's so nice to see this.
May I ask how to deal with in cooking the xip part of Atom XDA LIFE?
Thanks!
Click to expand...
Click to collapse
I have posted this in the Atom Wiki: Disassembly of Other Device ROMs
http://wiki.xda-developers.com/index.php?pagename=Other_Device_ROM
BUT, as far as assembly is concerned, you have to ask an Atom Life user because there have been reports that assembly doesn't quite work.
JIGGS KITCHEN???
How many time i have reviewed that jiggs never release a kitchen in a public,.
be patient please,.
i'll upload it,.
thanks,.
ThanX bud , can you come on yahoo?
tjlabais said:
BUT, as far as assembly is concerned, you have to ask an Atom Life user because there have been reports that assembly doesn't quite work.
Click to expand...
Click to collapse
Oh no, it semms to work.
See the attached pictures. Both pictures are from Atom Life. The 1908 is from ferryboat's chinese ROM. The 1978 is the XIP from an other build by ferryboat, cooked in the original WWE build but with 4 MB PP.
scorpio16v said:
Oh no, it semms to work.
See the attached pictures. Both pictures are from Atom Life. The 1908 is from ferryboat's chinese ROM. The 1978 is the XIP from an other build by ferryboat, cooked in the original WWE build but with 4 MB PP.
Click to expand...
Click to collapse
Great job scorpio,.
New map for atom exec
Hi, bro... as we know on both atom/ exec rom we used some module from original wm5. like cecompr.dll
and i have using cecompr.dll from original wm6 hermes to my rom N-Touch. See my new map
Code:
00000000 - 01f901fd L01f901fd NUL
01f901fd - 01f901fd L00000000 Start: first DLL address
01f901fd - 01fd1000 L00040e03 NUL
01fd1000 - 01fd2000 L00001000 initialized data of region_1 ceddk.dll
01fd2000 - 01fe1000 L0000f000 initialized data of region_1 TrueFFS.dll
01fe1000 - 01fe2000 L00001000 initialized data of region_1 cecompr.dll
01fe2000 - 01fef000 L0000d000 initialized data of region_1 stratad_intel_l.dll
01fef000 - 01ff0000 L00001000 initialized data of region_1 regenum.dll
01ff0000 - 01ff1000 L00001000 initialized data of region_1 pm.dll
01ff1000 - 01ff2000 L00001000 initialized data of region_1 mspart.dll
01ff2000 - 01ff3000 L00001000 initialized data of region_1 imgfs.dll
01ff3000 - 01ff4000 L00001000 initialized data of region_1 fsreplxfilt.dll
01ff4000 - 01ff5000 L00001000 initialized data of region_1 fsdmgr.dll
01ff5000 - 01ff6000 L00001000 initialized data of region_1 fatutil.dll
01ff6000 - 01ff7000 L00001000 initialized data of region_1 fatfsd.dll
01ff7000 - 01ff8000 L00001000 initialized data of region_1 encfilt.dll
01ff8000 - 01ff9000 L00001000 initialized data of region_1 diskcache.dll
01ff9000 - 01ffa000 L00001000 initialized data of region_1 devmgr.dll
01ffa000 - 01ffc000 L00002000 initialized data of region_1 crypt32.dll
01ffc000 - 01ffd000 L00001000 initialized data of region_1 coredll.dll
01ffd000 - 01ffe000 L00001000 initialized data of region_1 certmod.dll
01ffe000 - 01fff000 L00001000 initialized data of region_1 cachefilt.dll
01fff000 - 02000000 L00001000 initialized data of region_1 busenum.dll
02000000 - 02000000 L00000000 End: last DLL address
02000000 - 03df2000 L01df2000 NUL
03df2000 - 03df8000 L00006000 Virtual base address of ceddk.dll
03df8000 - 03e44000 L0004c000 Virtual base address of TrueFFS.dll
03e44000 - 03e5a000 L00016000 Virtual base address of stratad_intel_l.dll
03e5a000 - 03e5e000 L00004000 Virtual base address of cecompr.dll
03e5e000 - 03e62000 L00004000 Virtual base address of regenum.dll
03e62000 - 03e71000 L0000f000 Virtual base address of pm.dll
03e71000 - 03e79000 L00008000 Virtual base address of mspart.dll
03e79000 - 03e83000 L0000a000 Virtual base address of imgfs.dll
03e83000 - 03e8d000 L0000a000 Virtual base address of fsreplxfilt.dll
03e8d000 - 03ea2000 L00015000 Virtual base address of fsdmgr.dll
03ea2000 - 03eab000 L00009000 Virtual base address of fatutil.dll
03eab000 - 03ebe000 L00013000 Virtual base address of fatfsd.dll
03ebe000 - 03eca000 L0000c000 Virtual base address of encfilt.dll
03eca000 - 03ed0000 L00006000 Virtual base address of diskcache.dll
03ed0000 - 03edc000 L0000c000 Virtual base address of devmgr.dll
03edc000 - 03f4e000 L00072000 Virtual base address of crypt32.dll
03f4e000 - 03fe4000 L00096000 Virtual base address of coredll.dll
03fe4000 - 03ff0000 L0000c000 Virtual base address of certmod.dll
03ff0000 - 03ffa000 L0000a000 Virtual base address of cachefilt.dll
03ffa000 - 04000000 L00006000 Virtual base address of busenum.dll
04000000 - 80580000 L7c580000 NUL
good point indeed since our ATOM imgfs only use XPR compression and no need to hanle LZX Decompress method, can save 8192 bytes for imgfs modules.
File struct error,
I try to "rommaster.exe os.nb ... from Hermes
but it have an error
[Error] File struct error, xip end offset is 0x7c90ee19, but file length
is 0x043aa800.
Please someone help
When manually porting a XIP, is it safe to change the VM location without changing the physical location of a module? Also, if the answer is yes, is it safe (maybe recommended) to remove the NULs and reallocate the module's to fill the NUL's?
a) yes
b) its safe but unnecessary. if you collapse the modules between physlast and ramfree (and then move up ramfree) that space will be allocated to free ram. however it has no other effect on performance.
the nul space between physfirst and physlast is only to fill out the block size and cant be collapsed.
Ok, thanks. Porting makes a lot more sense now. Now, on to b.) I was just referring to the NUL spaces between modules, I don't think I'm ready for the freeing RAM part yet. But let me ask you this, I ported a Titan from device xip 20931 and Donor of 21232. Can you look at my MAP.txt and tell me if it looks good to you? (I went ahead and removed the NUL's just in case, I thought they might have been bad). I know this is in the Rapheal thread, but apparently, I was porting my Touch Pro's without issue (except for the NUL's that I thought might need to go) because they weren't getting overlaps.
I really appreciate your feedback.
View attachment MAP.zip
in what address spaces are you collapsing nul ?
there are no overlaps in your map
Yeah, there aren't any more. I re allocated to fill in the NUL's between modules in both the virtual and physical. I also had to make enough space (0xc000) for imgfs.dll since I couldn't even get XIPport to make a map.txt with it in there originally due to either the physical or virtual overlaps from that module. It caused XIPPortto error out. I removed the imgfs.dll from the folder, ran realloc P and finally got my map.txt. Then, I "Jimmy'd" it in there manually by using some of the NUL spaces and reallocating other modules.
For reference, here are the NUL's I am referring to. This is part of the map.txt from a Vogue Donor 21501 and a Herman 20771 test xip I made:
02000000 - 03db2000 L01db2000 NUL
03db2000 - 03dbb000 L00009000 Virtual base address of wce_rex.DLL
03dbb000 - 03dc2000 L00007000 Virtual base address of smem.dll
03dc2000 - 03dc9000 L00007000 Virtual base address of relfsd.dll
03dc9000 - 03dce000 L00005000 Virtual base address of MMMAP.dll
03dce000 - 03dd5000 L00007000 Virtual base address of htcfsfilter.DLL
03dd5000 - 03dda000 L00005000 Virtual base address of GxDMA.dll
03dda000 - 03df9000 L0001f000 Virtual base address of FLASHDRV.DLL
03df9000 - 03e49000 L00050000 Virtual base address of DDI.dll
03e49000 - 03e4f000 L00006000 Virtual base address of ceddk.dll
03e4f000 - 03e53000 L00004000 Virtual base address of cecompr.dll
03e53000 - 03e57000 L00004000 Virtual base address of regenum.dll
03e57000 - 03e66000 L0000f000 Virtual base address of pm.dll
03e66000 - 03e6e000 L00008000 Virtual base address of mspart.dll
03e6e000 - 03e7e000 L00010000 NUL
03e7e000 - 03e8a000 L0000c000 Virtual base address of imgfs.dll
03e8a000 - 03e94000 L0000a000 Virtual base address of fsreplxfilt.dll
03e94000 - 03eaa000 L00016000 Virtual base address of fsdmgr.dll
03eaa000 - 03eb3000 L00009000 Virtual base address of fatutil.dll
03eb3000 - 03ec6000 L00013000 Virtual base address of fatfsd.dll
03ec6000 - 03ecc000 L00006000 Virtual base address of diskcache.dll
03ecc000 - 03ed8000 L0000c000 Virtual base address of devmgr.dll
03ed8000 - 03f4a000 L00072000 Virtual base address of crypt32.dll
03f4a000 - 03fe1000 L00097000 Virtual base address of coredll.dll
03fe1000 - 03fef000 L0000e000 Virtual base address of certmod.dll
03fef000 - 03ffa000 L0000b000 Virtual base address of cachefilt.dll
03ffa000 - 04000000 L00006000 Virtual base address of busenum.dll
04000000 - 80000000 L7c000000 NUL
There is a 64KB dead space there (red). Do I gain anything by bothering to reallocate all the modules above the NUL at 03e7e000 up (or down the list) another 0x10000, thereby pushing that 64KB dead space into the top NUL (blue) ?
Same goes for physical.
Update:
Actually, after doing some further reading, I would only gain 24KB of space by collapsing the NUL between physlast and RAM free. It currently is at 802da000 - 802e0000 with a length of L00006000 on the Titan port I made.
What is it?
A pure(-ish) build of AOSP (code-frozen 4.1.2_r1/jb-mr0-release, a.k.a JZO54K) for the Xperia Play. It's as pure as can be, there are some fixes from CM10 (thanks J), SlimRom and myself needed to get everything working. But the framework and apps are 99% 90% AOSP, with changes specific to solving known Jellybean issues on our device. There are however some more extras, such as Google Apps preinstalled and maybe some other slight changes.
What's the point?
Designed for developers/chefs and testers, this has three major goals:
Provide a good base to port other Jellybean ROM's to (in particular, my Turbo UI ROM)
A good comparison with other JB ROM's to see what is and isn't broken (great for the second or third multiboot slot). E.g. if something crashes in Slimbean or PAC, try in this. Because it is "feature frozen" whereas CM10 and other JB ROM's keep adding new things that may break something (you know, it happens).
Forward-port ICS/GB code to get more things working - like native xLoud and better Touchpad support.
This ROM is feature frozen. I will not add Notification Toggles. I will not add a Reboot option to power menu. I will not add *anything* unless it will benefit other JB ROM's/Developers or Turbo UI. Please don't request new fancy features that other JB ROM's already have - this is not the point of this ROM. Many of my developments have already made their way into wedgess PAC, cj360's SlimBean and/or FXP's CyanogenMod. Jellyzeus is a platform for my own research and improvements and I only released it for educational, development and comparison purposes.
If you want a more serious and useful ROM that is directly based on this, check out my MIUI based PatchROM build - Turbo UI.
Status?
Green: Complete
Brown: Has issues or untested
Red: Broken or not finished yet
Calls, texts, 3G for GSM (have not done heavy testing, needs more)
Multiboot-aware
All sensors (including proximity)
CDMA addon (beta, needs logcats if any problems)
Camera (Legacy) (Thanks to Wedgess) (No Panorama)
Browser and Web rendering
Sound with with decent stock-like headphone volume
xLOUD enabled (uses ICS Audio blobs from stock/prebuilt) (hack)
Google Apps included
Wifi
GPS / Location services
Touchpads (Lag reduced but not eliminated)
Bluetooth
Native Wifi Tether
Google Now Voice Search/Recognition
Video Recording (480p only - don't ask about 720p, not possible)
?
Bugs/Important Info?
On a fresh install, all the tones are set to silent. Ringtone, Notification Tone and Alarm tone must be manually set. I have no idea what is causing this. Fixed.
Sources?
All of my source changes can, as always, be found on my GitHub (see my signature). Additionally, here are the details of my repo's - they are all original AOSP from 4.1.2_r1 tag, with the exception of these mentioned repo's - mostly for compatibility with QCOM hardware, as well as additional fixes and improvement's I've made. There are also various small patches to make to get it to build. Instructions for building from my sources can be found in post #2.
Source repo/patch details:
Code:
cosmicdan:
bootable/recovery/ (forked from cyanogenmod)
device/semc/msm7x30-common/ (forked from garwedgess)
frameworks/av/ (forked from AOSP)
frameworks/base/ (forked from AOSP) (jellyzeus branch)
frameworks/native/ (forked from AOSP)
hardware/libhardware/ (forked from slimroms, jb branch)
hardware/libhardware_legacy/ (forked from slimroms, jb branch)
libcore (forked from AOSP)
system/core/ (forked from AOSP) (jellyzeus branch)
vendor/semc/ (forked from garwedgess)
cyanogenmod:
build/
external/busybox/
external/bluetooth/bluez/
external/yaffs2/
external/zlib/
hardware/broadcom/wlan/
hardware/ril/
hardware/sony/DASH/
packages/apps/Gallery2/
packages/apps/LegacyCamera/
vendor/cm/
system/bluetooth/
system/netd/
system/vold/
garwedgess:
device/semc/msm7x30-common/
device/semc/zeus/
device/semc/zeus-common/
SlimRoms (branch):
external/chromium/ (jellybean)
external/webcore/ (jellybean)
hardware/msm7k/ (jb)
hardware/qcom/audio/ (jb)
hardware/qcom/gps/ (jb)
hardware/qcom/media/ (jb)
hardware/qcom/display/ (jellybean)
This patch for Guava incompatibility with OpenJDK -
https://github.com/CyanogenMod/android_external_guava/commit/c8b97210aa31c9b80b5fd136d8617ebe4e731e09
Use prebuilt kernel to save time and fix build complaining from missing kernel sources -
Open /device/semc/zeus/BoardConfig.mk and remove the comment (#) symbol from TARGET_PREBUILT_KERNEL
Open vendor/cm/config/common.mk and comment out the three lines for Terminal, like so:
[code]#PRODUCT_COPY_FILES += \
#vendor/cm/proprietary/Term.apk:system/app/Term.apk \
#vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm4.so:system/lib/libjackpal-androidterm4.so
[/code]
Credits?
CosmicDan, Kamarush and Irii for Turbo JB Kernel
Cyanogenmod and Jerpelea (FreeXperia)
Wedgess, cj360, paxChristos, KeiranFTW, Nickholtus, SuperVenom and Farenheith
Fellow members of MIUI Australia - LennyKano, FusionJack and Dekky
Special thanks to Amarullz (creator of Aroma Installer) and the XDA community
Download and Instructions?
Flash Turbo JB kernel (recommended) and be sure to follow the instructions there. This ROM is multiboot-aware already, so feel free to install the ZIP from Slot 2 or 3.
Install the ROM normally (in any slot you like if using multiboot)
Download latest ROM: zeus_aosp_412_r5.zip @ Mediafire
Download CDMA addon: zeus_aosp_412_cdma_r3.zip @ Mediafire (install after main ROM)
Changelog?
Code:
r5
--
- Overhaul Telephony, Webkit, Bluetooth and Net framework
- Additional property support from CyanogenMod (performance related)
- Reverted Camera changes in r4
- More things I can't remember. It's all on GitHub.
r4
--
- Fixed Camera recording (480p only, 720p permanently removed due to bugs)
- Fixed native App2SD
- Numerous fixes/optimizations to Telephony and Media framework
- Reverted ICS audio blobs
r3
--
- New - hold volume buttons to skip music tracks
- Fixed various Google App issues (e.g. Calendar sync, Location services)
- Reduced touchpad lag by about half (best I can do until we learn more...)
- Fixed touchpad recognition (Farenheith's Touchpad Fix v1.1)
- Fixed default tones being silent (Random fix)
- Fixed Wifi signal indicator on statusbar (Framework issue)
- Fixed GPS (was it ever broken? Google Maps and GPS Status lock fine)
- Fixed Bluetooth (Update sources for BCM interface from CM10)
- Patched services to not force minfree or adj values
- Basic tweaks added to init.d, same used in MIUI Australia (minfree/adj/kernel tuning)
- Updated Google Now to latest version (no longer crashes on voice input but simply fails)
r2
--
- Additional video and audio native decoding support, thanks to CAF (such as H.263, WMV, MP3, etc)
- Fixed root (replaced with Chainfire's SuperSU v0.99)
- Fixed Proximity Sensor
- Fixed rotation (accelerometer/orientation)
- Fixed compass
- Fixed ALS (automatic brightness)
- Fixed Browser (replaced webKit core with prebuilt from SlimBean port, thanks cj360!)
- Disable some debugging parameters to improve performance
- Native Sony sound blobs and full xLoud support enabled
- Replaced AOSP Keyboard with Nexus 4.2 version (smaller APK)
- Removed unused content accidently included from CM10
- Removed Google Calendar and returned original (more compatible with widgets, can get Google Calendar from Play Store anyway)
r1
--
- Initial release
Screenshots?
No. It looks like AOSP (like CM10 but with much less features). If you only want to see what this ROM looks like, please move along it's for dev's and research purposes after all.
This post is reserved for build instructions.
Really looking forward for this! First!
Sent from my R800i using xda app-developers app
---------- Post added at 05:15 AM ---------- Previous post was at 04:28 AM ----------
I don't really have any ideas on the kernel panic, but I'll keep thinking.
Sent from my R800i using xda app-developers app
I figured it out, same problem as the webcore glitches. QCOM tile renderer is not fully ported yet. WOOO one-man think tank!
CosmicDan said:
I figured it out, same problem as the webcore glitches. QCOM tile renderer is not fully ported yet. WOOO one-man think tank!
Click to expand...
Click to collapse
+ A Half Wit
Sent from my R800i using xda app-developers app
You're only a halfwit when you complain or flame the dev's
The camera works fine. The automatic rotation doesn't work.
Binary_File said:
The camera works fine. The automatic rotation doesn't work.
Click to expand...
Click to collapse
Erm... Camera doesn't work. Automatic rotation is a minor framework issue, not a priority right now. Main things are camera and web browser (which are graphics related).
CosmicDan said:
This post is for detailed status and (when available) source-code links and summaries of changes.
kmsg dump of the kernel panic when trying to start legacy camera:
Code:
Switching from ACPU rate 768000 KHz -> 1024000 KHz
Enabling PLL 2
Disabling PLL 1
ACPU speed change complete
msm_enqueue: queue event new max is 1
msm_enqueue: queue control new max is 1
msm_pp_release: pp not in progress for 0
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = 81180000
[00000000] *pgd=01376031, *pte=00000000, *ppte=00000000
Internal error: Oops: 80000007 [#1] PREEMPT
last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
Modules linked in:
CPU: 0 Tainted: G W (2.6.32.9-KRsH-irii #1)
PC is at 0x0
LR is at msm_ioctl_config+0x10d8/0x12b4
pc : [<00000000>] lr : [<803e5198>] psr: 60000013
sp : 8c135e68 ip : 00000014 fp : 8c135edc
r10: 2c72490c r9 : 8c134000 r8 : 8003712c
r7 : 40046d1b r6 : 2c72490c r5 : 2c72490c r4 : 80e6d0d8
r3 : 00000000 r2 : 0000002b r1 : 00000000 r0 : 8c135e84
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c57c7d Table: 01380059 DAC: 00000015
LR: 0x803e5118:
5118 fffffe00 e1a0200d e3c23d7f e3c3303f e24b0070 e5933008 e2952004 30d22003
5138 33a03000 e3530000 1a000005 e1a01005 e3a02004 ebfaf31b e3500000 0a000008
5158 ea000001 e3a01004 ebfafc46 e51f0064 e3002854 e51f1074 e51f3068 eb06ce30
5178 ea00003e e5943000 e51b1070 e5932080 e59330c4 e592205c e5920000 e12fff33
5198 eafffc1e e51f00a0 e5947000 e3500010 9a000004 e3a010d0 ebf5798b e2506000
51b8 1a000001 ea000002 e1a06000 e3a03001 e5863030 e1a0c00d e3cc3d7f e3c3303f
51d8 e286003c e5933008 e2952004 30d22003 33a03000 e3530000 1a000005 e1a01005
51f8 e3a02004 ebfaf2ef e2504000 0a000017 ea000001 e3a01004 ebfafc1a e51f0114
SP: 0x8c135de8:
5de8 00000000 80d9c000 800d8624 80114318 80c0ca40 00000000 ffffffff 8c135e54
5e08 2c72490c 40046d1b 8c135edc 8c135e20 80036bb0 80036308 8c135e84 00000000
5e28 0000002b 00000000 80e6d0d8 2c72490c 2c72490c 40046d1b 8003712c 8c134000
5e48 2c72490c 8c135edc 00000014 8c135e68 803e5198 00000000 60000013 ffffffff
5e68 8c135ecc 8c135e78 801303fc 8012d1bc 00000032 00000000 00000000 0000002b
5e88 2c57000c 2c724900 000004cc 81180b10 00000133 00000000 00000000 8c130128
5ea8 00000200 8c156420 8c135ecc 8c029a00 803e40c0 2c72490c 40046d1b 8003712c
5ec8 8c134000 2c72490c 8c135efc 8c135ee0 80157698 803e40cc 2c72490c 8c029a00
FP: 0x8c135e5c:
5e5c 00000000 60000013 ffffffff 8c135ecc 8c135e78 801303fc 8012d1bc 00000032
5e7c 00000000 00000000 0000002b 2c57000c 2c724900 000004cc 81180b10 00000133
5e9c 00000000 00000000 8c130128 00000200 8c156420 8c135ecc 8c029a00 803e40c0
5ebc 2c72490c 40046d1b 8003712c 8c134000 2c72490c 8c135efc 8c135ee0 80157698
5edc 803e40cc 2c72490c 8c029a00 40046d1b 0000001b 8c135f7c 8c135f00 80158160
5efc 80157668 80036340 8003eb18 80e2b6c0 00000002 8017a404 801482c4 cf397500
5f1c 00000020 00000000 00000000 00000003 2c7245b0 ceaa1b00 2c7245b0 00000003
5f3c 00000000 8c135f6c 8c135f50 ceaa1b00 00000002 0000001b 2c72490c 8c029a00
R0: 0x8c135e04:
5e04 8c135e54 2c72490c 40046d1b 8c135edc 8c135e20 80036bb0 80036308 8c135e84
5e24 00000000 0000002b 00000000 80e6d0d8 2c72490c 2c72490c 40046d1b 8003712c
5e44 8c134000 2c72490c 8c135edc 00000014 8c135e68 803e5198 00000000 60000013
5e64 ffffffff 8c135ecc 8c135e78 801303fc 8012d1bc 00000032 00000000 00000000
5e84 0000002b 2c57000c 2c724900 000004cc 81180b10 00000133 00000000 00000000
5ea4 8c130128 00000200 8c156420 8c135ecc 8c029a00 803e40c0 2c72490c 40046d1b
5ec4 8003712c 8c134000 2c72490c 8c135efc 8c135ee0 80157698 803e40cc 2c72490c
5ee4 8c029a00 40046d1b 0000001b 8c135f7c 8c135f00 80158160 80157668 80036340
R4: 0x80e6d058:
d058 80e6d054 00000000 00000000 8080e260 00000000 00000002 00000001 00000000
d078 805d9458 80e2b7a4 80e2b7a4 0ee00001 00000001 00000001 80e6d0d8 00000000
d098 00000000 80e6d09c 80e6d09c 00000000 00000000 8080e260 00000000 00000001
d0b8 00000001 00000000 805d94c0 80e6d0c4 80e6d0c4 0ee00002 00000001 00000000
d0d8 cb099500 00000000 80e6d0e0 80e6d0e0 80e6d0e8 80e6d0e8 00000001 00000000
d0f8 80719017 80e6d0fc 80e6d0fc 80e6d104 80e6d104 00000000 00000000 80728fea
d118 00000000 80e6d11c 80e6d11c 80e6d124 80e6d124 00000000 00000000 80728ff0
d138 00000000 80e6d13c 80e6d13c 80e6d144 80e6d144 00000000 00000000 80728ff5
R8: 0x800370ac:
70ac e24fef6d 3798f107 e28d1008 e3a08000 e357080f e2270000 2a0011ff ea02873c
70cc e1a02007 e28d1008 e3a00000 eb000925 e28fe014 e1a07000 e28d1008 e3570e17
70ec 3891000f 3798f107 eaffffef e5ad0008 e1a02007 e1a0100d e3a00001 eb000919
710c eaffff90 e320f000 e320f000 e320f000 e320f000 807e8a98 8080bf00 800377a8
712c 800ceacc 800bf904 80037714 80148fcc 80149048 801482f0 80146848 800d8dc0
714c 80148340 801560cc 80155e88 80037724 80147c5c 800d8dc0 80155cec 80147f4c
716c 800eb148 800d8dc0 800d8dc0 801488f4 800cb73c 80164720 800d8dc0 800eb230
718c 800eb644 800d8dc0 800c70b4 800d8dc0 800d8dc0 800cfc0c 800d8dc0 800d8dc0
R9: 0x8c133f80:
3f80 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3fa0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3fc0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
3fe0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
4000 00000000 00000002 00000000 8c156420 807fdff8 00000000 00000017 8119faa0
4020 8119faa0 8c134000 8c1565cc 811fa1c0 00000000 8c156420 8c135e6c 8c135e20
4040 8059e334 00000000 00000000 00000000 00000000 00000000 01010000 00000000
4060 2c724f00 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Process Binder_1 (pid: 1156, stack limit = 0x8c1342f0)
Stack: (0x8c135e68 to 0x8c136000)
5e60: 8c135ecc 8c135e78 801303fc 8012d1bc 00000032 00000000
5e80: 00000000 0000002b 2c57000c 2c724900 000004cc 81180b10 00000133 00000000
5ea0: 00000000 8c130128 00000200 8c156420 8c135ecc 8c029a00 803e40c0 2c72490c
5ec0: 40046d1b 8003712c 8c134000 2c72490c 8c135efc 8c135ee0 80157698 803e40cc
5ee0: 2c72490c 8c029a00 40046d1b 0000001b 8c135f7c 8c135f00 80158160 80157668
5f00: 80036340 8003eb18 80e2b6c0 00000002 8017a404 801482c4 cf397500 00000020
5f20: 00000000 00000000 00000003 2c7245b0 ceaa1b00 2c7245b0 00000003 00000000
5f40: 8c135f6c 8c135f50 ceaa1b00 00000002 0000001b 2c72490c 8c029a00 40046d1b
5f60: 0000001b 8003712c 8c134000 00000000 8c135fa4 8c135f80 801581f8 80157c28
5f80: 00000001 00000001 2c5762d8 2c569740 2c724934 00000036 00000000 8c135fa8
5fa0: 80036f00 801581c0 2c5762d8 2c569740 0000001b 40046d1b 2c72490c 2c7248fc
5fc0: 2c5762d8 2c569740 2c724934 00000036 2c574dd8 000e1000 0006ae00 000002f8
5fe0: 2c53930c 2c7248e0 2ab49cfd 2ab2ebd4 00000010 0000001b ff706766 ff746a6a
Code: bad PC value
[audio_out.c:audio_dsp_event] PCMDMAMISSED 32
Nnvh vdnnbolllicb.o vk
---[ end trace 1b75b31a2719ed1e ]---
Kernel panijbimvhyc - not syncing: Fatal exception
[<8003d83c>] (unwind_backtrace+0x0/0xd8) from [<80598164>] (dump_stack+0x20/0x24)
[<80598164>] (dump_stack+0x20/0x24) from [<80598978>] (panic+0x6c/0x130)
[<80598978>] (panic+0x6c/0x130) from [<8003b5c4>] (die+0x17c/0x1a8)
[<8003b5c4>] (die+0x17c/0x1a8) from [<805981cc>] (__do_kernel_fault.part.2+0x64/0x74)
[<805981cc>] (__do_kernel_fault.part.2+0x64/0x74) from [<8003ecf8>] (do_page_fault+0x1ec/0x204)
[<8003ecf8>] (do_page_fault+0x1ec/0x204) from [<80036340>] (do_PrefetchAbort+0x44/0xa8)
[<80036340>] (do_PrefetchAbort+0x44/0xa8) from [<80036bb0>] (__pabt_svc+0x50/0xa0)
Exception stack(0x8c135e20 to 0x8c135e68)
5e20: 8c135e84 00000000 0000002b 00000000 80e6d0d8 2c72490c 2c72490c 40046d1b
5e40: 8003712c 8c134000 2c72490c 8c135edc 00000014 8c135e68 803e5198 00000000
5e60: 60000013 ffffffff
[<80036bb0>] (__pabt_svc+0xiy. Mkz50/0xa0) fro . [<803e5198>] (msm_ioctl_config+0x10d8/0x12b4)
[<803e5198>must (msm_ioctl_config+0x10d8/0x12b4) from [<80157698>] (vfs_ioctl+0x3c/0x9c)
Mk
[<80157x cg:banghead: mixvkok698>]
(vfs_ioctl+0x3c/0x9c) from [<80158160>]r (do_vfs_ioctl+0x54oftu 4/0x598)
? Ggbf yourself g6c6uukt:rolleyes:lmng
[<80158160>] (do_vfsvkrjvj_ioctl+0x544/0x598) from [<8y01581f8>]y (sys_ioctl+0x44/0x70)
[<801581f8>] (sys_ioctl+0x44/0x70) from [<80036f00>] (ret_fast_syscall+0x0/0x2c)
:
&@[email protected]:*Binder_1*
Gvnm .:df
Rebooteing in 1 seconds..
smd_close(RPCCALL)mm l nuik
:what::thumbdown:
I think the interesting part is this:
Code:
Code: bad PC value
[audio_out.c:audio_dsp_evju:jnj çgigyaent] PCMDMAMISSED 32
d .mzk
Y
I've done some research and apparently this is some kind of deadlock, but from what i do nott know.
Click to expand...
Click to collapse
Sent from my FIH-FB0 using xda premium
I found the problem, both camera and browser should be fixed this weekend. Was not using latest fixed QCOM hardware sources for display (specifically, TileRendering support).
Proximity mught be in the libs.
/system/lib/libssensorservice.so
Or something like that. Maybe..
Sent from my Xperia Play using xda app-developers app
JunDavis said:
Proximity mught be in the libs.
/system/lib/libssensorservice.so
Or something like that. Maybe..
Sent from my Xperia Play using xda app-developers app
Click to expand...
Click to collapse
Well yeah, and the sensor hardware static object. Finding the actual code and getting the ICS sensor framework working in JB is no as simple as copy/paste though.
On a lighter note, I've already implemented the groundwork for using Sony stock ICS audio libs. Which means that getting full xLoud support (actually reliably unlike Turbo UI and, in future, with a toggle) should be relatively easy. Yay!
CosmicDan said:
Well yeah, and the sensor hardware static object. Finding the actual code and getting the ICS sensor framework working in JB is no as simple as copy/paste though.
On a lighter note, I've already implemented the groundwork for using Sony stock ICS audio libs. Which means that getting full xLoud support (actually reliably unlike Turbo UI and, in future, with a toggle) should be relatively easy. Yay!
Click to expand...
Click to collapse
Yea :/, I knew you can't just copy and paste. I just posted that because I thought it was somewhat relevant.
Also, yay! xLoud
Sent from my Xperia Play using xda app-developers app
Besides, why do we need proximity sensor anyway? It only goes up to 1 cm.
Guess it would be nice to have every tiny thing working though.
Sent from my Xperia Play using xda app-developers app
JunDavis said:
Besides, why do we need proximity sensor anyway? It only goes up to 1 cm.
Guess it would be nice to have every tiny thing working though.
Sent from my Xperia Play using xda app-developers app
Click to expand...
Click to collapse
Because it's annoying that your face can touch buttons when you're in a call lol.
CosmicDan said:
Because it's annoying that your face can touch buttons when you're in a call lol.
Click to expand...
Click to collapse
Never had that problem o.o lol
Sent from my Xperia Play using xda app-developers app
CosmicDan said:
Because it's annoying that your face can touch buttons when you're in a call lol.
Click to expand...
Click to collapse
Yeah lol
Sent from my R800i using Tapatalk 2
And also battery. If you're in a long call you want to save as much battery as possible, and the screen is the biggest offender of battery use. I know you can always press power button to turn screen on/off, but that's quite annoying when you want to (e.g) quickly check how long the call has gone for.
CosmicDan said:
And also battery. If you're in a long call you want to save as much battery as possible, and the screen is the biggest offender of battery use. I know you can always press power button to turn screen on/off, but that's quite annoying when you want to (e.g) quickly check how long the call has gone for.
Click to expand...
Click to collapse
Agreed, I already had to upgrade my battery a while back :/
Sent from my Xperia Play using xda app-developers app
Make sure you keep your old one for whenever you do flashing or logcat and other USB stuff. Constantly plugging/unplugging USB tends to wear-out a battery quicker that usual. And as usual, only charge when essential _don't top it up every night if not needed). But sometimes that's not realistic, so use "Fast Discharge" app on Play Store to help quickly drain battery fully, then recharge to max over night (from flat). That will help recondition the battery.
But yeah, my "dev battery" barely lasts two hours lol. That's the original one from my old X10.