Rom Android 2017

UPDATE: Galaxy Note official ICS ZSLPF and XXLPY confirmed unsafe

some N7000XXLPY users reported phone bricked issues with this official ICS rom released by Samsung in Germany recently when they were trying to do a wipe or reformat, with cwm or stock recovery

actually this is an old issue that happened to some other devices like Samsung Epic 4G Touch SPH-D710, as well as all leaked ICS based firmwares for Galaxy Note including the international version GT-N7000, US AT&T SGH-I717 and GT-I9220 in China


DISCLAIMER
- this is just a message to inform ppl about possible threats and dangers
- this is only intended for raising your awareness
- this is not aims at scaring you or anyone in any way
- all i want is to express my own opinions
- this is not intended to say nor to find out who is liable or who is to be blamed
- any suggestion provided is for reference only
- phone bricking is not a must
- it does not mean you will brick your phone eventually or certainly
- it does not mean using XXLPY or cwm will brick your phone for sure
- you are not forced to do anything or not to do anything
- you should decide what you should do and should not do
- you are responsibile for what you are going to do
- no one can assure you anything, not excluding me
- i have flashed several leaked roms before a lot of times and currently with XXLPY on my phone at the time i am writing this


NOTICE
- it is up to you whether to ignore this post or not
- it is up to you whether to continue reading this post or not
- you are welcome to leave comments should you have any disagreement or question, but no flaming or bashing please





THE ISSUE


couple of days ago i found chainfire, an experienced developer, issued a warning message in his post:

WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !

Deleting large files while fully booted may also cause problems with your flash memory.

at that time, there was one brick incident reported only with the XXLPY, but countless with leaked ICS roms including my SGN bricked weeks ago. and then, even upgrading via the OTA or FOTA (Firmware Over-the-Air) reported bricks. it is believed that there are bugs in the kernel, rom or the recovery, that can cause damages to the eMMC (Embedded MultiMedia Card) on the phones and make your phone unbootable


The eMMC is composed of the MMC (Multi Media card) interface, the flash memory, and the flash memory controller

eMMC is a standard for embedded memory devices that contain not only a data storage element (such as NAND flash memory), but also a controller for the storage element integrated on the same silicon die.

source: samsung.com


so far there is no evidence if this could be due to cwm or the stock rom, and the actual problem areas are yet to determine at the moment, but what we learnt is that problems can occur likely when the following actions is performed:
- doing a wipe in the *recovery mode
- formatting the partition(s) in the *recovery
- rom flashing in the *recovery mode that involve disk wiping or formatting
- resetting the phone by performing a factory data reset in the settings application

*including cwm recovery by chainfire, XXLPY stock recovery and leaked ICS roms recovery


some argued that wipe is safe and does no harm. but i found after reading the source codes, the wipe will in turn calls for a disk format (format_volume function). simply speaking, a disk wipe means disk formatting


however, the bricks and damages are not happening each time you do a wipe or disk format on your phone. no one knows when it will happen and no one knows if it will happen. personally, i flashed my phone for over a hundred of times with the leaked ICS roms without any problem, but finally i got my phone bricked (not relating to XXLPY). that is to say, may be you are lucky that you don have any problem so far, and may be i was lucky for flashing so many times without any problem, but you will never know what will happen next time and you wont realized you are one of the victums until your phone bricked


after reading the message from chainfire, i started to think this can be a diaster since the cwm is so popular that a lot of ppl are using it and now the developer had issued this warning. so, possibily this will affect a lot of users.

yes, i knew that the number of bricked phone was so tiny, and i understand rom flashing does involve risks, but i opted to post in a forum talking about this aimed at alerting users about this possible threat. i also suggested ppl to stay away from the affected roms until the problem is solved, or stick to their Android 2.3.6 Gingerbread rom for now. as a responsible forum member and developer, i believe this is not a bad thing especially for normal or non-experienced users by informing them about this. it was not for my own good but for the benefits of others and there is no gain for me at all


unexpectedly i saw some ppl flaming and said something not very nicely,

"even a 5-10% bricks is not an issue"
"you are scaring ppl with no evidence"
"i flashed more than 20 times with no problems and i am not scared"
"it is an official rom so it is totally safe"
"you are not a developer and you know nothing about development"

in less than an hour, i realized i was wrong. i was wrong for "no gain for me" but in fact i benefited from learning some english words and phrases which i will never have a chance to learn in my life from books, ever....

to be honest, i don mind these bashings since i believed i was doing the right thing. as i said,

what we know is the number of ppl suffered
what we will know is the number of ppl who suffered avoidable issues after reading this post
but what we dono is how many phones we saved

interestingly, someone then replied, "0 (zero saved)"


anyway, up to now there are more than 10 known soft bricks or hard bricks incidents, involving previous cm builds based on leaked ICS roms and the LPY rom. i can see some of the guys who disagreed with me before had reported phone bricks also


continue to Galaxy Note ICS XXLPY phone bricks - advice

UPDATE: Galaxy Note official ICS ZSLPF and XXLPY confirmed unsafe

not all phone bricks are irrecoverable. it depends what you have done before and what can be done next



A BIT OF ADVICE


there are two kind of phone bricks: soft bricks and hard bricks. in fact, soft bricks are relative easy and possible to recover but hard bricks are not recoverable even with JTAG recovery

soft bricks:
- you can still see the phone boots up with the Samsung Galaxy Note GT-N7000 logo
- the phone enters a boot loop, ie keeps rebooting after booted up
- you are able to enter the recovery mode by pressing and holding the volume up button, home button, and the power button
- you are able to enter the download mode by pressing and holding the volume down button, home button, and the power button
- you are able to enter the download mode with a usb jig
- your phone boots but with lots of FCs

hard bricks:
- you are unable to enter the recovery mode by pressing the keys
- you are unable to enter the download mode by pressing the keys
- you are unable to enter the download mode with a usb jig
- you only see a blank, black screen
- the phone does not response at all after power up and just like running out of battery, but you can feel it is warm somewhere near the camera at the back


do's and don'ts:
as time goes by, there are more and more victums. as to play safe, especially for normal users and those without warranty, it is suggested that:
- do not upgrade to ICS XXLPY yet
- do not flash any affected roms
- do not flash roms in the recovery, neither cwm nor stock XXLPY
- do not wipe or format disks in the recovery
- do not run factory reset in settings on your phone with leaked ICS or LPY based roms
- stick with a safe rom for now (at the moment, all Android 2.3.6 Gingerbread roms are REGARDED as safe)
- go back to one of the roms that confirmed safe if possible, but IF AND ONLY IF you know what you are doing and what you need to do


important:
if you want to go back to gb or other safe roms (no guarantee and do it at your own risks):
- use pc odin to flash a safe rom only
- not until a safe rom is flashed, do not use the recovery or factory reset
- no need to care about the yellow triangle thing, it is easy to get rid of it
- in case the phone FCs (force closes), don worry, they can be fixed
- you should bear in mind that rom flashing is dangerous itself


nevertheless, developers are trying to find out the root causes. so in the meantime, be patient and wait for a solution or newer and safer roms


finally, i want to end this with one more advice: do not have the wrong impression of offical roms or products are 100% safe and harmless. this is not the case in our real world. otherwise, there wont be any windows sp1/sp2... sp5, osx 10.0/10.3... 10.7, ios 4.0/4.0.1... 4.2, android 2.2.1/2.3.6... 4.0.3/4.0.4, linux kernel 2.6.27.62/2.3.35.13.. 3.2.17. there wont be any recall of defective cars, contaminated medicine and the like. you may argue that why ppl still using them? simple enough, just because we don have better alternatives but have to rely on them for now, at least


good luck to you all


back to Galaxy Note ICS XXLPY phone bricks - issues

UPDATE2: Galaxy Note Sony Bravia Engine ICS mod available

UPDATE: Galaxy Note ICS with Sony Bravia Engine soon


Sony Bravia Engine is included in this modded Gallery for SGN, Samsung Galaxy Note N7000. it is based on the deodexed Gingerbread 2.3.6 XXLC1 released recently

in case you are looking for the SGS2's, read this: Galaxy S2 with Sony Bravia Engine for Gingerbread and ICS


by default, the Bravia Engine is set to ON but can be disabled manually (see below)

this is an incomplete but working demo for implementing Sony Bravia Engine in Gallery3D on Samsung Galaxy S2 for Gingerbread and ICS, as well as Galaxy Note. once you have installed it, your existing Gallery3D WILL BE REPLACED by this demo. note that no performance or memory tweaks, stress tests, etc were performed in this demo, and bugs or force closes are expected but not observed so far

please refer to the document below for installation instructions, and how to check if the engine is running or to see the differences. you can turn off the engine for particular files, and to re-generate your wallpaper with the Sony Bravia Engine by following the steps:

click here for installation instructions





if you like this mod, please give it a like or share this post to your friends, etc, or consider a small donations. thank you

feedbacks and questions are welcomed



PLEASE READ THE DISCLAIMER AND WARNING CAREFULLY BEFORE DOWNLOADING OR INSTALLING THE FILE(S)!!



DISCLAIMER

The file attached below is an unfinished demo resulted from a feasibility study for integrating Samsung Gallery3D application and Sony Bravia Engine, and is provided for educational and research purposes only. This demo is solely to describe and explain how to implement the engine with the Samsung Android Gallery application, and is only intended for demonstrating the outputs produced by Samsung Gallery3D application with Sony Bravia Engine on the Android platform. It is, however, in no ways or by no means to be used on a daily basis, nor to be used for any commerical purpose, and it is not supposed to be distributed or published in any kind.

Samsung Gallery3D, Sony Bravia Engine, Android and all other trademarks mentioned belong to their respective owners.



WARNING

The file(s) attached are provided as is and for demo only. You should pay attention to the laws in your country or region, whichever and wherever applicable. You have to make sure you are not offended by downloading, accessing, transmitting, using, or in any other way utilizing any material contained in the file(s). You further understand and acknowledge are legally able to use or access the material(s) according to the laws in your country or region, and agree to waive, and hereby do waive, any legal or equitable rights or remedies you have or may have against me, regarding all matters related to your use of the file(s).

I am NOT RESPONSIBLE for any damages, including bricked phones, partial or total loss of data resulting from the use of the file(s) contained, in all kinds and/or by any means, caused by using or accessing the file(s)/material(s), including problems caused by the file(s) and/or by third parties. You shall be solely responsible for the consequences of using or accessing the material(s) and I will not be held responsible in the event any charges, including but not limited to civil and criminal charges, be brought against any individuals using the material(s) contained in this post and or attachment(s).





By clicking on the link below you agree to all the terms and conditions described above, and fully understand the risks involved for using or accessing any materials found here, and agree to assume and take on all of the risks and responsibilities in any way associated with this yourself.


download (in CWM zip):
link 1 Gallery3DSBEDemo-SGN.zip
link 2 Gallery3DSBEDemo-SGN.zip
md5: AE20FB15BEA4B6451560E8EE41708B18


references:
more Bravia Engine screenshots marked with differences

SGS2 ICS 4.0.3 Sony Bravia Engine demo with wallpaper rendering available

now with wallpaper enhancements - SGS2 wallpaper Sony Bravia Engine demo

UPDATE: Galaxy Note with Sony Bravia Engine Demo


the Gallery Sony Bravia Engine mod for SGN N7000 will be available later tonite HKT. this mod makes it possible to render images with Sony Bravia Engine's implementation, which increases the sharpness, contrast, levels and so forth of the images and produces better outputs

it is based on the newest Android 2.3.6 rom N7000XXLC1, which should be compatible for ex-XXLC1 roms also. and wallpaper rendering is added as well into this mod

Samsung Gallery3D Original	Samsung Gallery3D with Sony Bravia Engine

more screenshots will be added later


note that this is not the one which regarded as fake and was shipped with almost every roms before in the SGS2 and other forums. for those who in doubt or want to know how and why my mod works but not others that simply tell u to edit the prop files, read my post about this issue below and u will have a totally different conclusion:
is Sony Bravia Engine really working with SGS2 and other Android devices?


for reference, please refer to my previous posts below about the Sony Bravia Engine Gallery3D demo for SGS2:
SGS2 Gallery3D with Sony Bravia Engine previews
SGS2 wallpaper Sony Bravia Engine demo
SGS2 ICS 4.0.3 Sony Bravia Engine demo
more Bravia Engine screenshots marked with differences

the Gingerbread rom XXLC1 launched in Europe and is available for download

product code: GT-N7000ZBADBT
pda: XXLC1
csc: OXALC1
modem: XXLB2
date: 2 Mar 2012

some updates:
Kies air
Kobo
S memo
Zinio


download link found on the internet (PS this will wipe your data):
link 1

UPDATE4: Sony Bravia Engine for Samsung Galaxy S3 coming soon

UPDATE3: more Bravia Engine screenshots marked with differences

UPDATE2: SGS2 ICS 4.0.3 Sony Bravia Engine demo with wallpaper rendering available

UPDATE: now with wallpaper enhancements - SGS2 wallpaper Sony Bravia Engine demo


this is an incomplete but working demo for implementing Sony Bravia Engine in Gallery3D on Samsung Galaxy S2/Samsung Galaxy Note for Android 2.3.6 Gingerbread/Android 4.0.3 Ice-Cream Sandwich. once you have installed it, your existing Gallery3D WILL BE REPLACED by this demo. note that no performance or memory tweaks, stress tests, etc were performed in this demo, and bugs or force closes are expected but not observed so far

EDIT: the current version is incompatible with I9000 yet


i considered it a success based on the following facts and results:
- the library needed by the Sony Bravia Engine for converting images was loaded and being used by the gallery app
- the gallery app warned against missing libraries if they could not be accessed
- the be_photo file did played a role and the outputs were back to nornal (without the Bravia engine) if it was not accesssible
- the images were processed/converted by the engine during the image creation
- the outputs produced (screenshots captured) by the Samsung Gallery3D were identical to those produced by Sony Gallery installed on my device in terms of file sizes, checksums, etc
- the outputs produced by the Samsung Gallery3D alone without the Bravia engine were different in terms of file sizes, checksums, etc


i cannot, however, assure it is 100% ported for the reason that i do not own a SE device. but even i do, the outputs cannot be compared directly due to different resolutions, color engine, brightness used, etc




PLEASE READ THIS POST CAREFULLY BEFORE DOWNLOADING OR INSTALLING THIS DEMO!!





system requirements:
- gingerbread/ice-cream sandwich
- rooted
- CWM recovery
- built and tested on:
Samsung Galaxy S2 GT-I9100- 2.3.6 - I9100XWKK5
Samsung Galaxy S2 GT-I9100 - 4.0.3 - I9100XXLP6
Samsung Galaxy Note GT-N7000 - 2.3.6 - N7000XXLC1
Samsung Galaxy Note GT-N7000 - 4.0.3 - I9220ZCLP6


files to be copied to your phone:
- /system/app/Gallery3D.apk
- /system/etc/be_photo
- /system/lib/libbmpcnv.so
- /system/lib/libiwi.so
- /system/lib/libiwiOmx.so
- /system/lib/libiwiOmxUtil.so


installation:
backup your files first!!!
then, either:
1/. with CWM
- put the zip file in your sdcard
- reboot into recovery mode
- choose the zip file and select update
- reboot your phone

or:
2/. with File Manager/Explorer/shell
- extract the zip file
- copy the system folder extracted from the zip to your /system (rw permission is required)


settings:
- NO EXTRA setting is required
- NO NEED to edit any prop file


turning on the Sony Bravia Engine:
- NO NEED to do anything, the engine will be turned on by default


tunning off the Sony Braiva Engine:
- you can only turn it off TEMPORARILY (*see below)


uninstalling the demo:
- the simpliest way is to overwrite the Gallery3D.apk with your previous version
- remove the files listed above if you want a complete uninstall but not a must


how to check the Sony Bravia Engine is loaded and running:
- create a new folder in your external sd card is suggested, eg /mnt/sdcard/external_sd/sbetest/, then copy an image file of your choice in that folder
- within that newly created folder, make a new copy of the image file you just copied there, and rename it by adding a tag 'BE-OFF' to the filename without quotes. now you will have two identical images here and read like eg, myimage1.jpg + myimage1BE-OFF.jpg, myimage2.jpg + myBE-OFFimage2.jpg, etc. the engine will ignore all files with the BE-OFF tag so a normal output will be produced instead
- if you created the new folder in your external sd card, go to Settings > Storage, and select Unmount SD card, followed by selecting Mount SD card again as to force a media rescan
- if you created the new folder elsewhere but not in your external sd card, perform a media scan either by running a third party app like 'Rescan Media', which can be found on the market
- start Gallery SBEDemo and you should see the new folder and files just created
- then,

1/. for normal users
- browser the two images and you should see the differences in sharpness, color, etc. if you do, then the Sony Bravia Engine should be running properly
- do a screen capture for the two images and save them. compare the two file sizes and they should be differ (beware of the zoom in/out buttons, etc and make sure they look identical when capturing the screenshots)

2/. for advanced users
I - by checking the pids
- get the pid of the gallery (media) by:
a) pidof com.cooliris.media
or,
b) ps | grep media | grep -v grep
- get the pid that is using the lib file /system/lib/libbmpcnv.so after clicking an image in the gallery by:
fuser /system/lib/libbmpcnv.so
- the pid returned from fuser should be equal to the pid of the gallery
II - by checking the file size and checksum of the files
- perform screen captures for both images
- compare the checksums and they should differ
III - by comparing the output produced by SonyEricsson's Gallery
- install SonyEricsson's Gallery and make sure it runs properly with the bravia engine
- perform screen captures for the images in both Gallery SBEDemo and SonyEricsson's Gallery
- compare the checksums and they should be identical
IV - by reading log file
- read the log by logcat and you should read messages like 'BE-OFF' tag or '### entering be 111' with tag MediaItemTexture


in order to prove it further, you can:
- click on an image without BE-OFF tag, press the home button and switch to another app or home, rename the /etc/be_photo, then press the home button to switch back to gallery again to see the differences, and a log will be printed and read like the following:
01-04 22:43:56.194: ERROR/BitmapConverterNative(1382): Failed to LoadParameters, Missing Parameter files ==========
- kill the gallery app and rename the /system/lib/libbmpcnv.so, start gallery again and click on an image, you will get a force close because the required library file libbmpcnv.so has been removed/renamed, and you will find a log message like:
01-04 22:48:34.964: WARN/dalvikvm(5192): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/sonyericsson/swiqi/BitmapConverter;
01-04 22:48:34.964: WARN/dalvikvm(5192): threadid=15: thread exiting with uncaught exception (group=0x4001e578)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192): FATAL EXCEPTION: TextureLoad
01-04 22:48:34.969: ERROR/AndroidRuntime(5192): java.lang.ExceptionInInitializerError
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.cooliris.media.MediaItemTexture.transformWithIQI(MediaItemTexture.java:394)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.cooliris.media.MediaItemTexture.load(MediaItemTexture.java:166)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.cooliris.media.RenderView.loadTextureAsync(RenderView.java:313)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.cooliris.media.RenderView.access$900(RenderView.java:53)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.cooliris.media.RenderView$TextureLoadThread.load(RenderView.java:1280)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.cooliris.media.RenderView$TextureLoadThread.run(RenderView.java:1264)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load bmpcnv: findLibrary returned null
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at java.lang.Runtime.loadLibrary(Runtime.java:429)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at java.lang.System.loadLibrary(System.java:554)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     at com.sonyericsson.swiqi.BitmapConverter.<clinit>(BitmapConverter.java:30)
01-04 22:48:34.969: ERROR/AndroidRuntime(5192):     ... 6 more
01-04 22:48:34.969: WARN/ActivityManager(812):   Force finishing activity com.cooliris.media/.Gallery




and, that's all. feedbacks and questions are welcomed



PLEASE READ THE DISCLAIMER AND WARNING CAREFULLY BEFORE DOWNLOADING OR INSTALLING THE FILE(S)!!



DISCLAIMER

The file attached below is an unfinished demo resulted from a feasibility study for integrating Samsung Gallery3D application and Sony Bravia Engine, and is provided for educational and research purposes only. This demo is solely to describe and explain how to implement the engine with the Samsung Android Gallery application, and is only intended for demonstrating the outputs produced by Samsung Gallery3D application with Sony Bravia Engine on the Android platform. It is, however, in no ways or by no means to be used on a daily basis, nor to be used for any commerical purpose, and it is not supposed to be distributed or published in any kind.

Samsung Gallery3D, Sony Bravia Engine, Android and all other trademarks mentioned belong to their respective owners.



WARNING

The file(s) attached are provided as is and for demo only. You should pay attention to the laws in your country or region, whichever and wherever applicable. You have to make sure you are not offended by downloading, accessing, transmitting, using, or in any other way utilizing any material contained in the file(s). You further understand and acknowledge are legally able to use or access the material(s) according to the laws in your country or region, and agree to waive, and hereby do waive, any legal or equitable rights or remedies you have or may have against me, regarding all matters related to your use of the file(s).

I am NOT RESPONSIBLE for any damages, including bricked phones, partial or total loss of data resulting from the use of the file(s) contained, in all kinds and/or by any means, caused by using or accessing the file(s)/material(s), including problems caused by the file(s) and/or by third parties. You shall be solely responsible for the consequences of using or accessing the material(s) and I will not be held responsible in the event any charges, including but not limited to civil and criminal charges, be brought against any individuals using the material(s) contained in this post and or attachment(s).





By clicking on the link below you agree to all the terms and conditions described above, and fully understand the risks involved for using or accessing any materials found here, and agree to assume and take on all of the risks and responsibilities in any way associated with this yourself.



download link: Gallery3DSBEDemo (in CWM zip)

UPDATE3: more Bravia Engine screenshots marked with differences

UPDATE2: more screenshots here SGS2 Gallery3D with Sony Bravia Engine previews

UPDATE3: SGS2 Gallery Sony Bravia Engine demo

UPDATE: it now works with stock gallery IT WORKS!! Sony Bravia Engine and Samsung Galaxy S2 with stock Gallery3D



hi all,

after i mistakenly reported the Sony Bravia Engine worked with SGS2 before, i decided to test if the Bravia Engine can be used on Galaxy S2 myself from the beginning

after spending a whole day in dealing with the files and dependencies, i think i have found something finally and yielded the following results :

1 - the Gallery3D (SemcGallery3D.apk) from X10 works together with the stock one




2 - the library file libswiqibmpcnv.so is loaded after the SE Gallary is launced, and fuser shows the libswiqibmpcnv.so is being used by the SE Gallary




3 - the be_photo is loaded by the libswiqibmpcnv.so when a photo is selected in the SE Gallery. and if it is removed, libswiqibmpcnv.so reports an error




and finally, the outputs for two HD images found on the internet from stock Samsung Gallery3D.apk and SonyEricsson SemcGallery3D.apk with be_photo loaded, taken by screen capture

Samsung Gallery3D	SonyEricsson Gallery3D
click here to view the original file
click here to view the original file

to be continued ... :D

the lag problems, together with animations, etc, have been fixed for deodexed JVO/JVP/JVQ/JVR browser, credits to brightidea for correcting the problems, and lirik0 for letting us know in I9000 section


read more

i'm too frustrated with samsung's stock browser since JP6, and the deodexed one from JVQ is totally rubbish. it's sooooo lag that i've to wait for 2 seconds after each scroll


so, after studying some great posts in xda, i've modded a deodexed JVQ browser with all the lag things disappeared. now it just perform like what it used to be, u can scroll from the top to the bottom of the page with 1 single scroll. HOWEVER, i cannot say it's 100% bugs-free



so, USE IT AT YOUR OWN RISKS!! and remember to do BACKUP!




installation (for deodexed rom):
simply remove the existing Browser.apk from /system/app, and put this one there

PS you may notice some strange thing when u start this modded browser for the 1st time like a blank page is shown or cant scroll the page. just reload the page or restart the browser will do


NOTICE to all users:
- this is a one-off mod and it is not supposed to have any further modifications/adjustments

NOTICE to modders/developers:
- if u want to keep this alive or help to maintain this mod, etc, feel free to ask for the trick in xda


you can get it here

I9000XXJVP (XEU) 2.3.4 is available now, which is 'supposed' to fix a security hole that allow hackers to compromise and steal personal data including phone book from your device

the long awaited gingerbread sms mod for deodexed I9000XWJVB and I9000XWJVH are out finally. they are not modded by me this time but, instead, by another nice guy called montymintypie in the xda forum, who also fixed the limit of number of msgs per sms and the auto convert to mms problem


more info and download

more info about my froyo version sms sent time fix for I9000XWJS5 and I9000XXJPX/I9000XXJPY

flashed I9000XWJVB a few days ago and just ran a quadrant, cpu scored 5508. what?? 5508?? 4.x times of froyo's?





personally, i treat it as an incorrect result. i always believe it is obtained by misinterpreting the individual results so that the base number is much smaller, and thus produce a larger number and yield a higher marks. i don think my device runs a lot faster than before (talking about the cpu performance), and definitely no chance for a 4.x performance

in my opinion, it becomes meaningless to read or compare the cpu's result calculated by it anymore

it is reported that Gingerbread upgrade has been pulled by Google. the mentioned rom, I9000XXJVK, which was available in UK via Kies, was pulled off

below is an extract from the message posted by an administrator from Vodafone:

Due to an issue with the Gingerbread update for the Samsung Galaxy S, its roll out has been temporarily suspended by Google... we are working with Samsung to reinstate the roll out as soon as possible...




on the other hand however, some people claimed that it was due to a call delay bug on incoming and outgoing calls in 2.3.3


source: www.engadget.com

finally Gingerbread I9000XWJVB, NEE, is available for Samsung Galaxy S I9000, you can download it from the internet or upgrade via Kies
 






build info:
PDA I9000JVB
Phone I9000JVK
CSC I9000JV3
Baseband is I9000XXJVK
Kernel version 2.6.35.7-I9000XWJVB-CL118186
root@DELL102 #2
Build number GINGERBREAD.XWJVB
Firmware Version 2.3.3
File System RFS
Build date is Fri APR 8 16:39:27 KST 2011


source: forum.xda-developers.com

it's rumored that there will be a new member in the Galaxy S product line - the 2011 edition

with Gingerbread pre-installed, it equips with a 1.4GHz processor. the spec is about the same as the Galaxy S, except that HSPA+ 14.4Mbps support is added and the battery is a 1650mAh one. it should be arrived at the end of April and it will cost you around US$850

a new version leaked today together with a new JVK modem. the build date is 20 Mar

noted that the original version comes with a Sbl (secondary boot loader), if u really wanna give it a try, grap one with Sbl removed on the net

a beta 2.3.2 version XWJV1 (I9000XWJV1) is leaked, and reported to be running (most of the cases) except some apps

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJV1
ro.build.version.incremental=XWJV1
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2