Related
Q:What is BlendMIUI Speed-Porting Software For XPERIA 2011
Ans:This is a short program trying to help you guys to build your own BlendMIUI rom for Xperia 2011 devices in just few minutes.
Q:How to use it?
Unlock Bootloader first!
1.Download BMSPS(BlendMIUI Speed-Porting Software) then unpack it to anywhere you like(Windows environment).Btw,you should install JAVA SE JRE first or it won't works because it needs JAVA environment to sign the rom.You can goto oracle.com/java to download the latest Java SE JRE.
2.Download latest MIUI rom for Desire HD from miui.us(or anywhere you want).
3.Rename the rom you just downloaded as MIUI.zip then put it into /MIUI_DHD_ROM directory.(Do not rename it as MIUI.zip.zip!)
4.Run BMSPS_luancher.exe to start.
5.Do as follows then it will automatically create update.zip under the BMSPS directory.
Then you have two choices:
=>Help youself:
6.Put the update.zip rom to your SD-card.
7.Flash BlendMIUI kernel(I have put it into \BlendMIUI-kernel directory) or DooMKernel for MIUI.
8.Use CWM-recovery to flash the update.zip rom.
=>Use Auto-Flash Function
You don't need to do anything on your phone,it will help you to do all works automatically and boot into the new system!
Features:
1.Support Devices: Xperia Arc,Xperia Arc S,Xperia NEO,Xperia NEO V,Xperia Ray,Xperia Play.
2.Latest CM7.2.0 rebuilted sources as base.
3.Automatically port MIUI for your device then create unpdate.zip and sign the rom to let you flash it into your device directly.
4.Your choice Function (addons)
5.Fully working Auto-Flash Function
P.S: CM7 sources and kernel for XPERIA RAY are come from bheremans.
Changelog for Version 02:
1.Add moded Packageinstall to let you chose where you would like to install your apps including SD-card.
2.Fixed function to remind you to install java-jre if update.zip is not created.
3.Small changes.
Changelog for Version 03:
1.Fixed PackageInstaller and Torch FC problem when using the ROM from www.miui.com as base.
2.Automatically recognize MIUI version (Depends on the MIUI rom you use) and change Build version for porting rom.
3.Add "Your Choice" function to help you customize your own BlendMIUI rom(BlendUI,DSPManager,Tweaks,Audios from SE).
4.[For DEVs] Whole-New Source code:More easy to read,more easy to add new language(I mean the BMSPS itself) and new functions.
Changelog for Version 04:
1.Disable echoing information for better display.
2.Fixes and improve performance of BMSPS.
3.Add "Auto-Flash" function to help you flash BlendMIUI automatically
Changelog for Version 04.3:
1.Add Xperia Ray ST18i support(All sources for Xperia Ray are come from bheremans).
2.Fixed Auto-Flash function.
3.Fixed ADB Detective bug which cause the software stuck at entering into Auto-Flash function when you input "yes".
Changelog for Version 04.7:
1.Add Xperia Neo V support.
2.Fully working Auto-Flash function (You don't need to do anything on your phone now until it boots into the new system.BMSPS will help you to do everything automatically.)
3.Some small changes
Changelog for Version 05.0:
1.Add Xperia Play R800i support.
2.Add confirm function to avoid error selection.
WARNING:
1.This is not an update-package and you'd better delete all old files if you have installed early version of BMSPS.
2.Make sure you have unlocked bootloader before using this tool.
3.Baseband 56 is highly recommanded(based on .42 official firmware).
Download links:
BMSPS V05.0: http://www.mediafire.com/?4c5rkkcns4abf3k
Latest Source Code @ github.com/JasonStein
[Credit]
Bheremans,Eamars,FXP,DooMloRd,enzo...
Please report bugs with screenshots!
No way! That was fast thank you so much!
Sent from my R800i using xda premium
Gah! R800x cheated out again!
Sent from my R800x
Feel a little left out in the cold for the r800x :-(
sent from my s.e.x play u jelly?
MAster224 said:
Feel a little left out in the cold for the r800x :-(
sent from my s.e.x play u jelly?
Click to expand...
Click to collapse
also works on r800x , I'm sure but may have bugs since r800x is an CDMA phone.
My friend told me it works fine on Xperia Play and AutoFlash function works correctly.
What should you do before using this tool to port and flash MIUI rom:
1.Install fastboot driver.
2.Flash .42 official firmware(if you are already on baseband 56 you don't need to flash it again)
3.Turn on your phone and connect it to your PC using usb cable with USB-Storage Mode closed.
Then:
Use BMSPS to port MIUI rom from miui.us and use Auto-Flash function to let software help you flash the kernel and rom automatically.
(You'd better chose wipe data and cache when BMSPS ask you or it may not boot correctly)
something is wrong with mediafire...
EDIT: Problem is gone. Maybe just some server issues.
What works/doesn't work
Sent from my R800i using XDA App
Touchpads work?
Sent from my R800i using Tapatalk
can someone try it? what goes wrong it's all automatic.
Then post what works and what does not work
i will test it but my play is in service :'(
i'm going to test it now.
can someone make a list with what i must to test?
sorry for my bad English
This did not work for me, the tool just crashs, but i think it is a promblem of my pc. I have the Beta Build wich JasonStein created and there are the only real bugs bluetooth and touchpads. It should be very similar with this.
IE-coRe said:
This did not work for me, the tool just crashs, but i think it is a promblem of my pc. I have the Beta Build wich JasonStein created and there are the only real bugs bluetooth and touchpads. It should be very similar with this.
Click to expand...
Click to collapse
Looks like I will stick with stock.
The only reason I won't use a custom Rom is because most of them have reported issues with the touchscreens.
Sent from my R800i using Tapatalk
@KeiranFTW: The Touchscreen issues ppl talk about aren't noticeable at all.
It's just like 2-3 pixles that don't register (from all angles, as far as i know)..
Though i wonder why it's not fixed, yet. :O
HearthC0re said:
@KeiranFTW: The Touchscreen issues ppl talk about aren't noticeable at all.
It's just like 2-3 pixles that don't register (from all angles, as far as i know)..
Though i wonder why it's not fixed, yet. :O
Click to expand...
Click to collapse
Was on my phone when I posted that so it autocorrected "touchpads" to "touchscreen" LoL.
Didn't know there was any touchscreen issues but without the touchpad some games I find hard to play.
Just installed on my r800i. Wifi, Camera, Flash and buttons work fine. Bluetooth does not start. I have not tested touchpads yet.
Ciao
Andrea
Hi all,
Please someone can help me how i can add a language pack to BMSPS_LANGUAGE folder????
and where i can find him??
thanks in advance
Main things to test:
1. WIFI
2. Bluetooth
3. Camera
4. Touchpads
5. Data
Dont forget to test Camera in Barcode Scanners
wifi data camera torch working
touchpads and bluetooth not.
The kernel from DooMLoRD is from the fxp 045 (or something) that doesn't have bluetooth and touchpads.
If DooMLoRD have time he will change it and maybe it is working than
Ultimate Notification LED fix for Xperia (ICS 4.0.4, 4.1.B.0.431)
Introduction
One of the most annoying bugs in the everyday use of Sony's official ICS firmware version 4.1.B.0.431 (and later) is that the notification LED only works for missed calls, and it doesn't notify anything else anymore.
Ironically, the previous beta firmware ICS 4.0.3 v4.1.A.0.562 showed a specular bug: the notification LED didn't notify missed calls, but it was working for everything else (SMS, Email, ..).
The "Ultimate Notification LED fix"
I've got around fixing this bug by reversing and doing a minor change in a 4.1.B.0.431 framework file (services.odex).
The patched file has the notification LED working for everything as it was in GB firmware: the LED now blinks for missed calls, sms, emails, and any other application showing LED notifications (eg: K9-mail, Whatsapp..).
Update: This patch now works on all Xperia devices with 4.1.B.0.431 firmware, and it has been tested initially tested on a Xperia Mini Pro sk17i.
Disclaimer
These files come with no warranty, express or implied.
By downloading and using files linked in this page you express your understanding that you use those files at your sole risk.
No one can be held responsible for any damage directly on indirectly related to files linked in this page.
If you flash something to your phone you must remember that there's always a minimal chance that something goes wrong: you know it, I can't be held responsible if your phone gets wrecked, if your working LED flashes during a work meeting and you get fired, or anything else.
Downloads and Install Instructions
To install this fix you have to be in a stock ICS 4.0.4 firmware v4.1.B.0.431, with root and ClockWorkMod (CWM) recovery installed.
To install the fix simply download the right package for you, and:
make sure your phone is charged! It's always safer when you need to flash something.
put the downloaded ZIP it in the root of your SD Card
reboot into CWM recovery
Do a Nandroid backup using CWM ("backup and restore" => "backup"): you shouldn't end in a bootloop if you download and apply the proper file, but it is a good practice to a CWM backup before applying mods and patches, so you can easily restore it and go back if anything goes wrong!
did I mention to do a Nandroid backup?
choose "Install ZIP from sdcard" => "Choose zip from sdcard"
browse to the ZIP in your SD Card
choose apply and reboot device.
enjoy a properly working led
The right package to download for you depends on your current system framework files status.
Use the following list and infos to find the proper download for you:
If you have an Xperia device on stock ICS 4.0.4 v4.1.B.0.431, and never applied other LED patches: install Busybox if you don't have it already, and download the following universal patch Ultimate_4.1.B.0.431_Notification_LED_FIX_UNIVERSAL_stock_rom_by_zxp.zip (originally attached to post #37).
Note: Busybox must be installed on your device before installing this package, or it will not work. The patch scripts expects Busybox to be installed into /system/bin.
If you never applied any patch and don't know what to download, this is the file you want!
Why: it is smaller, and only replaces the services.odex file with the patched one, that's all you need; the services.odex is automagically generated in your device, that's why Busybox is used, and this is what makes this package "universal".
If you your device currently has arcatarc's fix applyed: download Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip
Why: if you used on arcatarc fix, this package will restore 4.0.B.0.431 framework files along with the patched services.odex, because arcatarc's fix installed the old 4.1.A.0.562 framework files and this change needs to be reverted.
If you are using a stock deodexed ICS 4.0.4 v4.1.B.0.431 firmware: download Ultimate_4.1.B.0.431_Notification_LED_FIX_FOR_DEodexd_roms_by_zxp.zip
Why: it will replace the services.jar with the patched classes.dex inside.
This works for all Xperia Devices, including but not limited to the Xperia Mini Pro sk17i/a.
If you are using the new firmware v4.1.B.0.587: you are lucky, I have also released the Ultimate LED FIX for the new firmware 4.1.B.0.587. You can download it from the new version thread.
If you are using an even newer firmware: you have to wait for Sony to release this firmware for my sk17i, so that I can port the patch over the new version, or wait for someone to port it.
Background info, closing notes and thanks
As already specified this patch is based off stock 4.1.B.0.431 framework: I simply deodexed with baksmali, manually edited one .smali file to change the offending code that prevented the LED to work properly, and packed everything back.
I hope to find time to post very soon a Tutorial on how to apply the fix yourself, for educational purposes and to help less experienced people to port it over the .587 version.
Experienced users should be able to compare the stock 431 baksmali-ed services.odex and the patched one to find the small change, and port it over .587 without the need of my forthcoming guide.
Thanks to _mysiak_, he posted the Xperia Arc S stock framework files that I used to understand what path I had to follow to make "universal" patch.
Thanks to arcatarc, he posted the old 4.1.A.0.562 services.odex in his "partial fix" thread (I say "partial" because it simply used .562 framework files which showed a specular bug, as explained in the introduction), I have compared that version to the new one to quickly spot which file needed to be patched.
If you happen to port this patch to a newer firmware please post a link to your thread, so that I can add it in this post to inform users with such firmware that a patch exists for them.
If you want to inform other users of this patch please link back to this thread and don't simply re-upload/re-post a package. A link to this thread is the only way to be sure that users chose the proper package and can be updated if there is the need for a new/updated patch.
Bugs & Known Issues
This patch is now used by thousand of users without any reported issue or strange behavior.
If you install this patch and you end in a boot loop it means you have applied the wrong package. Please re-read the download info & instructions, and apply the proper zip. Period.
If you find any real problem please post it, and I'll update this section.
Changelog
2012.09.05 (current): Released the new Universal patch for stock/odex devices. The new Universal patch for stock/odexed fw now works on all Xperia devices, not only on the Xperia Mini Pro sk17i. This replaces the old first package, which has been deleted from this thread. (See posts #32 and #37 if you are curious on how/why it works).
Now all packages work an all Xperia devices.
2012.09.04: Updated infos for those having bootloop on stock/odex devices different from the Xperia Mini Pro with the first (small) package, while researching for a solution. (See posts #11 and #12 for reference).
2012.09.03: Initial release.
Additional Notes for those coming from arcatarc's fix
If you have used arcatarc "partial" fix you may have noticed that it had 2 major user visible problems:
the LED notification for missed calls was not working
it showed a single white blink when some notifications appeared in the statusbar: eg the Xperia Keyboard "choose input method" notification caused a white LED blink each time it appeared.
This patch doesn't have those problem, everything (seems!) to work as it should!
LED fix for deodexed roms works perfect , however the first one didn't work for me.... thanks man...!!!
Bootloop on mini, stock ICS 4.0.4 v4.1.B.0.431...
Stuck at XPERIA boot logo on Arc S, stock ICS 4.0.4 v4.1.B.0.431..
Thanks for your feedback, I'll try to help you solve the bootloops if I can.
Bear in mind that if you flash the package for the stock firmware you need to have all of the framework files untouched. If you have previously used other patches/fixes that modified some file inside /system/framework you can get a bootloop, and I can only help if you have modified files because you applied arcatarc fix before.
Adee.roy said:
LED fix for deodexed roms works perfect , however the first one didn't work for me.... thanks man...!!!
Click to expand...
Click to collapse
I'm using "the first one" (if you meant Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp.zip) on my own sk17i and it works!
If you tried to flash the "first one" in a deodexed rom I believe it's normal you've got a bootloop. If it was a stock (odexed) rom please tell me what do you mean by "didn't work"? You had a bootloop or your LED didn't act properly?
Did you install in a stock, unmodified, sony .431 firmware on your sk17? Was it another mobile?
AleksandarST15 said:
Bootloop on mini, stock ICS 4.0.4 v4.1.B.0.431...
Click to expand...
Click to collapse
What package did you install? You were on stock ICS with or without arcatarc fix?
_mysiak_ said:
Stuck at XPERIA boot logo on Arc S, stock ICS 4.0.4 v4.1.B.0.431..
Click to expand...
Click to collapse
What package did you install? You were on stock ICS with or without arcatarc fix?
works perfect on sk17i
thanks
@others
make sure you download the correct version. you need to check first wether your services is odexed or not and apply to appropriate patch.
zxp said:
What package did you install? You were on stock ICS with or without arcatarc fix?
Click to expand...
Click to collapse
I used Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp.z ip on my stock ICS without any modifications...
work like a charm! Thank you very much :good:
used @ sk17i stocked ics ROM
Works perfect on SK17a Xperia Mini Pro Stock ICS 4.0.0 v4.1.B.0.431 ROM & Mesa 1.7 Kernel. Thanks
I was on Arc S stock ICS, with "small" Arcatarc's fix (only services.odex replaced) and this fix put me into bootloop -> Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp.zip.
Now I tried Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip and phone booted fine. LED notification seems to be working fine as well. I compared all jar/odex files between stock Arc S ROM and from your fix and their content is different (though size is exactly the same).
AleksandarST15 said:
I used Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp.z ip on my stock ICS without any modifications...
Click to expand...
Click to collapse
So far the only confirmed installs are coming from sk17 users.
Maybe the other devices have some different framework file? If one of the $BASECLASSPATH files is different in other mobile phones this can't work. Well, actually it means that the patch can't be universal, and must be customized for each mobile.
AleksandarST15 if you did a nandroid backup so you can easily revert, can you please make 2 tests?
Here are the tests:
flash again the same zip, and try to clear dalvik cache & cache before reboot. You should get the bootloop again, but it is worth trying
flash the second file (Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip) and reboot. This comes with all required framework libs, coming from the sk17i. Does it works?
If the first one works the patch can be universal.
If the second one works, the patch can't be universal. You can still flash that file that comes with all framework files, but if your mobile phone has different framework files it is not the definitive solution to overwrite them with those coming from another mobile phone.
_mysiak_ said:
I was on Arc S stock ICS, with "small" Arcatarc's fix (only services.odex replaced) and this fix put me into bootloop -> Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp.zip.
Now I tried Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip and phone booted fine. LED notification seems to be working fine as well. I compared all jar/odex files between stock Arc S ROM and from your fix and their content is different (though size is exactly the same).
Click to expand...
Click to collapse
Thanks for your report _mysiak_! I was writing a reply and I didn't see it.
This seems to confirm point 2 of my last post, that is framework files differ a bit from mobile to mobile. That's why you get the booloop by flashing only the services.odex: all framework jar/odex files must be consistent.
It would help to know if they only differ in their signature (maybe because it is device-specific) or in the rest of the contents (the dex contents). Has anyone links to documentation (official/unofficial) that clears this point? Or dumps of stock framework libs for another device (not a sk17)?
If the content (and not only the header) is different would mean that anyone not having a sk17 can flash Ultimate_4.1.B.0.431_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip to quickly have working LED notifications, but this can have side effects because their framework files contain some different code...in this case the better option would be to have a owner of each device to port the patch to its device and post back.
i cant believe its finally working again! good job zxp.
st15i, real ics lite r3, deodexed.
Untot said:
i cant believe its finally working again! good job zxp.
st15i, real ics lite r3, deodexed.
Click to expand...
Click to collapse
It's the same I thought. Finally this stupid LED working again!
Thanks for your feedback, this confirms that the deodexed version is device-independant (the dependency on the other framework files comes on the odexing phase obviously).
I've updated the first posts with updates from user feedback.
zxp said:
It's the same I thought. Finally this stupid LED working again!
Thanks for your feedback, this confirms that the deodexed version is device-independant (the dependency on the other framework files comes on the odexing phase obviously).
I've updated the first posts with updates from user feedback.
Click to expand...
Click to collapse
Well thanks a lot for ur work...the deodexed version worked for me in mu custom build xperia pureness rom...good
Sent from my SK17i using XDA Premium HD app
Can work in 587?
Sent from my WT19i using Tapatalk 2
botski said:
Can work in 587?
It works on my custom rom:smultronic v.2(587)
Rage kernel 3.2
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
REPORT!
I'm using Ultimate_4.1.B.0.431_Notification_LED_FIX_FOR_DEod exd_roms_by_zxp.zip for coconut on Real ICS 5.2
LED Notif is working (but no missed call)
botski said:
Can work in 587?
Sent from my WT19i using Tapatalk 2
Click to expand...
Click to collapse
You shouldn't use it on 587, it would be safer to wait for someone to port it to .587, or wait my port (if Sony releases .587 for sk17i).
pucank said:
It works on my custom rom:smultronic v.2(587)
Rage kernel 3.2
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
I guess you flashed the deodexed package? The odexed had less chances to work..
I'm still surprised. Sony didn't change anyting in service.jar in .587?
Dimasdanz said:
REPORT!
I'm using Ultimate_4.1.B.0.431_Notification_LED_FIX_FOR_DEod exd_roms_by_zxp.zip for coconut on Real ICS 5.2
LED Notif is working (but no missed call)
Click to expand...
Click to collapse
As far as I know Real ICS contains many tweaks and customizations, maybe they changed other framework files that break the patch.
Did you try to wipe dalvik cache? I didn't need it on the stock (odexed) rom, I don't know if it may be necessary for deodexed roms.
zxp said:
You shouldn't use it on 587, it would be safer to wait for someone to port it to .587, or wait my port (if Sony releases .587 for sk17i).
I guess you flashed the deodexed package? The odexed had less chances to work..
I'm still surprised. Sony didn't change anyting in service.jar in .587?
As far as I know Real ICS contains many tweaks and customizations, maybe they changed other framework files that break the patch.
Did you try to wipe dalvik cache? I didn't need it on the stock (odexed) rom, I don't know if it may be necessary for deodexed roms.
Click to expand...
Click to collapse
Well, it's better than before /LED is not working at all/ after apply this patch, LED works. I don't mind about that missed called thing
Ultimate Notification LED fix for Xperia (ICS 4.0.4, 4.1.B.0.587)
Introduction
One of the most annoying bugs in the everyday use of Sony's official ICS firmware version 4.1.B.0.431 (and later, including v4.1.B.0.587) is that the notification LED only works for missed calls, and it doesn't notify anything else anymore.
Ironically, the previous beta firmware ICS 4.0.3 v4.1.A.0.562 showed a specular bug: the notification LED didn't notify missed calls, but it was working for everything else (SMS, Email, ..).
The "Ultimate Notification LED fix"
I've got around fixing this bug by reversing and doing a minor change in a 4.1.B.0.587 framework file (services.[o]dex).
The patched file has the notification LED working for everything as it was in GB firmware: the LED now blinks for missed calls, sms, emails, and any other application showing LED notifications (eg: K9-mail, Whatsapp..).
This patch works on all Xperia devices with 4.1.B.0.587 firmware, and it has been tested initially tested on a Xperia Mini Pro sk17i.
Disclaimer
These files come with no warranty, express or implied.
By downloading and using files linked in this page you express your understanding that you use those files at your sole risk.
No one can be held responsible for any damage directly on indirectly related to files linked in this page.
If you flash something to your phone you must remember that there's always a minimal chance that something goes wrong: you know it, I can't be held responsible if your phone gets wrecked, if your working LED flashes during a work meeting and you get fired, or anything else.
Downloads and Install Instructions
To install this fix you have to be in a stock ICS 4.0.4 firmware v4.1.B.0.587, with root and ClockWorkMod (CWM) recovery installed.
To install the fix simply download the right package for you, and:
make sure your phone is charged! It's always safer when you need to flash something.
put the downloaded ZIP it in the root of your SD Card
reboot into CWM recovery
Do a Nandroid backup using CWM ("backup and restore" => "backup"): you shouldn't end in a bootloop if you download and apply the proper file, but it is a good practice to a CWM backup before applying mods and patches, so you can easily restore it and go back if anything goes wrong!
did I mention to do a Nandroid backup?
choose "Install ZIP from sdcard" => "Choose zip from sdcard"
browse to the ZIP in your SD Card
choose apply and reboot device.
enjoy a properly working led
The right package to download for you depends on your current system framework files status.
Use the following list and infos to find the proper download for you:
If you have an Xperia device on stock ICS 4.0.4 v4.1.B.0.587, and never applied other LED patches: install Busybox if you don't have it already, and download the following universal patch Ultimate_4.1.B.0.587_Notification_LED_FIX_UNIVERSAL_stock_rom_by_zxp.zip.
Note: Busybox must be installed on your device before installing this package, or it will not work. The patch scripts expects Busybox to be installed into /system/bin or /system/xbin.
If you never applied any patch and don't know what to download, this is the file you want!
Why: it is smaller, and only replaces the services.odex file with the patched one, that's all you need; the services.odex is automagically generated in your device, that's why Busybox is used, and this is what makes this package "universal".
If you your device currently has arcatarc's fix applyed: download Ultimate_4.1.B.0.587_Notification_LED_FIX_by_zxp_FOR_arcatarc_fix_users.zip
Why: if you used on arcatarc fix, this package will restore 4.0.B.0.587 framework files along with the patched services.odex, because arcatarc's fix installed the old 4.1.A.0.562 framework files and this change needs to be reverted.
If you are using a stock deodexed ICS 4.0.4 v4.1.B.0.587 firmware: download Ultimate_4.1.B.0.587_Notification_LED_FIX_FOR_DEodexd_roms_by_zxp.zip
Why: it will replace the services.jar with the patched classes.dex inside.
This works for all Xperia Devices, including but not limited to the Xperia Mini Pro sk17i/a.
If you are using the old firmware v4.1.B.0.431: you are lucky, I originally released the Ultimate LED FIX for firmware 4.1.B.0.431, you can download it from the old version thread.
If you are using a newer firmware: you have to wait for Sony to release this firmware for my sk17i, so that I can port the patch over the new version, or wait for someone to port it.
Background info, closing notes and thanks
As already specified this patch is based off stock 4.1.B.0.587 framework: I simply deodexed with baksmali, manually edited one .smali file to change the offending code that prevented the LED to work properly, and packed everything back.
I hope to find time to post very soon a Tutorial on how to apply the fix yourself, for educational purposes and to help less experienced people to port it over newer versions.
Experienced users should be able to compare the stock 587 baksmali-ed services.odex and the patched one to find the small change, and port it over new versions without the need of my forthcoming guide.
If you happen to port this patch to a newer firmware please post a link to your thread, so that I can add it in this post to inform users with such firmware that a patch exists for them.
If you want to inform other users of this patch please link back to this thread and don't simply re-upload/re-post a package. A link to this thread is the only way to be sure that users chose the proper package and can be updated if there is the need for a new/updated patch.
Bugs & Known Issues
This patch is now used by thousand of users without any reported issue or strange behavior.
If you install this patch and you end in a boot loop it means you have applied the wrong package. Please re-read the download info & instructions, and apply the proper zip. Period.
If you find any real problem please post it, and I'll update this section.
Changelog
2012.10.04 (current): applied my fix to the new firmware version 4.1.B.0.587, and released specific packages for this firmware version. The universal package now supports busybox both in xbin and sbin.
Additional Notes for those coming from arcatarc's fix
If you have used arcatarc "partial" fix you may have noticed that it had 2 major user visible problems:
the LED notification for missed calls was not working
it showed a single white blink when some notifications appeared in the statusbar: eg the Xperia Keyboard "choose input method" notification caused a white LED blink each time it appeared.
This patch doesn't have those problem, everything (seems!) to work as it should!
was waiting for [.587] Awesum
Bad thing is, that this led fix works only with stock sms app. I use other sms client, and with this, led don´t blink.
happyBOY78 said:
Bad thing is, that this led fix works only with stock sms app. I use other sms client, and with this, led don´t blink.
Click to expand...
Click to collapse
Maybe the problem lies in the alternative sms client? This fix is proven to work with email, gmail, sms, whatsapp, missed call... not only stock sms!
PS: at least this was true for .431, I appreciate feedback on the fix on this new .587 firmware because something may have changed.
zxp said:
Maybe the problem lies in the alternative sms client? This fix is proven to work with email, gmail, sms, whatsapp, missed call... not only stock sms!
Click to expand...
Click to collapse
Will this work with XS app port?
If so can I use in my rom?
Developing an ICS rom
Allen Hu said:
Will this work with XS app port?
If so can I use in my rom?
Developing an ICS rom
Click to expand...
Click to collapse
I'm sorry I don't know what is the XS app port are you speaking of.
Generally speaking it will work for you if your custom ROM uses a stock, unmodified, services.jar/[o]dex. Else you'll lose functionality or customizations.
zxp said:
I'm sorry I don't know what is the XS app port are you speaking of.
Generally speaking it will work for you if your custom ROM uses a stock, unmodified, services.jar/[o]dex. Else you'll lose functionality or customizations.
Click to expand...
Click to collapse
I mean the apps from Xperia S resized....
And is it ok if I added the v6 supercharger in services.jar ?
i have .431 patch on .587 already. which package should i use?
happyBOY78 said:
Bad thing is, that this led fix works only with stock sms app. I use other sms client, and with this, led don´t blink.
Click to expand...
Click to collapse
For me it works fine with non-stock sms app (GO SMS pro). Missed calls, etc works too zxp - Thx for the fix!
tested working on my stock 4.1.B.0.587 ST15i
Allen Hu said:
I mean the apps from Xperia S resized....
And is it ok if I added the v6 supercharger in services.jar ?
Click to expand...
Click to collapse
Xperia S apps, should work fine just like any other app with this patch I think.
I never used v6 supercharger, but as far as I can understand from a quick look it dynamically patches a given services.jar rather than simply replacing it (which is what my patch does).
So if you have v6 supercharer patch my patched service.jar/[o]dex you should have it both supercharged and with the working LED.
spyblaster91 said:
i have .431 patch on .587 already. which package should i use?
Click to expand...
Click to collapse
If you applied my .431 patch on .587 you can simply use the same type you already used. Eg: if you used the "universal" one, you can use the "universal" one again, it will override the previous one.
Which one should i apply...im using markphyton rom .587 doomkernel
Sent from my R800i using xda app-developers app
Im using the fix for .431 and works great on my .587, whats new in this one? should i change my mod?
Seems to work fine in my xperia Arc LTi15.
Thanks!
thank you so much man, finally my ARC S notif LED its work like a charm :fingers-crossed: ....
Do you know if this patch works for the Real ICS r6 rom (based on 4.1.B.0.587)?
Which package should I use in case it works?
Thanks a lot in advance!
Deshabilitado said:
Im using the fix for .431 and works great on my .587, whats new in this one? should i change my mod?
Click to expand...
Click to collapse
Yes you should use this new version on a .587 based ROM, because if you use the fixed .431 file you are actually missing some fixes/changes that sony did in input method handling and other misc code, that you will restore by applying the new .587 patch.
evo10 said:
Which one should i apply...im using markphyton rom .587 doomkernel
Click to expand...
Click to collapse
ecejmpe said:
Do you know if this patch works for the Real ICS r6 rom (based on 4.1.B.0.587)?
Which package should I use in case it works?
Click to expand...
Click to collapse
If those roms are deodexed you should use the third package (Ultimate_4.1.B.0.587_Notification_LED_FIX_FOR_DEodexd_roms_by_zxp.zip) else you have to use the first (Ultimate_4.1.B.0.587_Notification_LED_FIX_UNIVERSAL_stock_rom_by_zxp.zip): either way you must be sure that your ROM has a unmodified services.jar(/odex) or you'll loose some customization.
Im using .587. Which one i need to download?
Sent from my WT19i using Tapatalk 2
Is there a way to install it without a root or unlocked bootloader?
Thanks
botski said:
Im using .587. Which one i need to download?
Sent from my WT19i using Tapatalk 2
Click to expand...
Click to collapse
Please read the Downloads and Install Instructions section in the first post, it contains a detailed answer to your question.
Hello everyone,
There have been some time that new ICS firmware for Neo L is posted, and over time i manage to get a collection of patches that enable Xperia Play's touchpads.
Thread that i found it can be found here http://forum.xda-developers.com/showthread.php?t=2189311 and here http://forum.xda-developers.com/showthread.php?t=2176936
Since no one posted it as flashable zip, i guess i could do it.
https://docs.google.com/file/d/0B8eMrl6yvYKyQXl2ZVdCWVJTcWM/edit?usp=sharing
I had to make compatible with Lupus ICS/GB V4 Kernel (system less then 280MB), so that means i had taken some apps from /system/app to /data/app (on the bright side, apps in data can all be deleted, for debloating purposes)
It should be compatible with other ICS stock kernels, but i didn't test it
Screenshots are here http://forum.xda-developers.com/showpost.php?p=38841129&postcount=57
Credits for touchpad fix goes to Markpython for editing framework.res and framework.jar
I must say big THANKS to Wedges,Doomlord and CosmicDan's for their work on our's Play's kernel :good:
And ofcorse thank to other developers and chefs here on XDA forum for their work :victory:
Update1:
-Thanks @smokerman, for making a video of this ROM. http://www.youtube.com/watch?v=Mjnw55pfX18
-This ROM is compatible with Lupus ICS/GB kernel V5, now it have 30MB of free space in system partition
Bakisha said:
Hello everyone,
There have been some time that new ICS firmware for Neo L is posted, and over time i manage to get a collection of patches that enable Xperia Play's touchpads.
Thread that i found it can be found here http://forum.xda-developers.com/showthread.php?t=2189311 and here http://forum.xda-developers.com/showthread.php?t=2176936
Since no one posted it as flashable zip, i guess i could do it.
https://docs.google.com/file/d/0B8eMrl6yvYKyQXl2ZVdCWVJTcWM/edit?usp=sharing
I had to make compatible with Lupus ICS/GB V4 Kernel (system less then 280MB), so that means i had taken some apps from /system/app to /data/app (on the bright side, apps in data can all be deleted, for debloating purposes)
It should be compatible with other ICS stock kernels, but i didn't test it
Screenshots are here http://forum.xda-developers.com/showpost.php?p=38841129&postcount=57
Credits for touchpad fix goes to Markpython for editing framework.res and framework.jar
I must say big THANKS to Wedges,Doomlord and CosmicDan's for their work on our's Play's kernel :good:
And ofcorse thank to other developers and chefs here on XDA forum for their work :victory:
Click to expand...
Click to collapse
What is the performance of this ICS Rom?
Whether in games & applications usuaro interface?
has some kind of mistake, or is completely stable?? the touchpad 100% functional for games, as in gingerbread ..?
I am very curious .. I think I'll give it a try ...
yekasangredevago said:
What is the performance of this ICS Rom?
Whether in games & applications usuaro interface?
has some kind of mistake, or is completely stable?? the touchpad 100% functional for games, as in gingerbread ..?
I am very curious .. I think I'll give it a try ...
Click to expand...
Click to collapse
Touchpads are compatible as any other ICS ROM, but i don't think it's perfect as in gingerbread.
Antutu score is around 4500 to 5500OC.
All phone functions works (GSM at leats). I mean, it don't have much features like other ROMS, but what it have, it works 100%
So far i didn't find any bugs (if there are any, it is most likely due my attempts to make a ROM out of Firmware files :laugh: )
As i see it, it is good ROM base-starter. To be modified, when deodexed... (this one is still odexed)
FInally as u promise a stock ics wthout fancy heavy apps.
Downloading now, let's see...
Edit: 2 things:
-why the quick google search bar doesn't do anything if i click on it?
-The system apps in /data/apps maked kinda messed up settings, but u could erase some usless stuff (like Wisipilot or Mc Afee) , like the guy before me wrote: "To be modified, when deodexed... (this one is still odexed)"
Dany XP said:
FInally as u promise a stock ics wthout fancy heavy apps.
Downloading now, let's see...
Edit: 2 things:
-why the quick google search bar doesn't do anything if i click on it?
-The system apps in /data/apps maked kinda messed up settings, but u could erase some usless stuff (like Wisipilot or Mc Afee) , like the guy before me wrote: "To be modified, when deodexed... (this one is still odexed)"
Click to expand...
Click to collapse
-google search is moved to data/app, maybe that's why it's not working
-Apps can be deleted from zip file before flashing (open with winrar/winzip and delete apk that you don't like/use , or later after flashing from launcher or PC (i use android commander for mass install/uninstall > http://androidcommander.com/
Bakisha said:
-google search is moved to data/app, maybe that's why it's not working
-Apps can be deleted from zip file before flashing (open with winrar/winzip and delete apk that you don't like/use , or later after flashing from launcher or PC (i use android commander for mass install/uninstall > http://androidcommander.com/
Click to expand...
Click to collapse
(google search is fine now, dont know why dont earlier)
Of course i know , but my point is that it would be nice having all those apps in system/app like in original rom. And in the same time u can erase some useless stuff (McAfee, etc etc)
Dany XP said:
(google search is fine now, dont know why dont earlier)
Of course i know , but my point is that it would be nice having all those apps in system/app like in original rom. And in the same time u can erase some useless stuff (McAfee, etc etc)
Click to expand...
Click to collapse
I know what you mean, but as i said, the point of this "ROM" is to be as close as flashing FTF. I don't consider this as "my" ROM, it is for everyone else to download/look/edit/compare and this thread can be used for discution about mods that can be done with this rom...
My idea was to have stock ICS from Neo L that work on Play (with touchpads)
And i had problems with system size (system+vendor partition on FTF is much larger, around 340MB, and it hardly be squeezed to 280MB, to be compatible With Lupus ICS/GB V4)
I did some changes based on this for my personal use, and i'll upload that version tommorow as "my" ROM tommorow (upload speed sux for me)
Ps: as i said before, stock ROMs are always bloated
Bakisha said:
I know what you mean, but as i said, the point of this "ROM" is to be as close as flashing FTF. I don't consider this as "my" ROM, it is for everyone else to download/look/edit/compare and this thread can be used for discution about mods that can be done with this rom...
My idea was to have stock ICS from Neo L that work on Play (with touchpads)
And i had problems with system size (system+vendor partition on FTF is much larger, around 340MB, and it hardly be squeezed to 280MB, to be compatible With Lupus ICS/GB V4)
I did some changes based on this for my personal use, and i'll upload that version tommorow as "my" ROM tommorow (upload speed sux for me)
Ps: as i said before, stock ROMs are always bloated
Click to expand...
Click to collapse
OK i understand your point of view.
Anyway, i reboot just to be sure and...well there's definitely something wrong with wi-fi. It's incredibly slow.
Dany XP said:
OK i understand your point of view.
Anyway, i reboot just to be sure and...well there's definitely something wrong with wi-fi. It's incredibly slow.
Click to expand...
Click to collapse
Well, i never had problem with wifi... Are you sure your neighbours are not stealing your wifi connection?
JK. Maybe it updating something in background...
Sent from my R800i using xda app-developers app
Bakisha said:
Well, i never had problem with wifi... Are you sure your neighbours are not stealing your wifi connection?
JK. Maybe it updating something in background...
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Maybe I spoke too soon, wait. Maybe it is me after all.
By the way, thank u. I always wanted a simple "original" stock ics for our Xperia Play. Why no one never ever did it?
Sent from my R800i using xda app-developers app
Dany XP said:
Maybe I spoke too soon, wait. Maybe it is me after all.
By the way, thank u. I always wanted a simple "original" stock ics for our Xperia Play. Why no one never ever did it?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
You are welcome.
Well, it's in XDA member's nature, we always want more
But afraid to ask for ETA
Sent from my R800i using xda app-developers app
So everything works here?
I basically just use my phone for N64oid, gameboid, Real Racing 3 and a lot of music and social networks (Instagram, Twitter, Face). So I don't care too much about touchpads unless I install a game like Fifa12 or Dead Trigger. But the problem I always have with all the ICS I've tested is that games like Real Racing 3 always closes (because of RAM).
Found a bug, the same on True Ancestor so i'm just gonna link it: http://forum.xda-developers.com/showpost.php?p=40423492&postcount=118
Yeah, everything should work, only bug so far is double-tab opening when startint browser from bookmark shorctcut (as DanyXP said). Maybe it's firmware fault, i'll check afternoon on flashed FTF.
As for free RAM, you can use 480p version of kernel, it gives 30MB extra free RAM, at cost of lower resolution at video recording (i personaly can't see the difference, and for me, 720p version recording is look like upscale of 480p recording)
I don't have real racing 3, and most RAM intensive game that i played was SIMS freeplay
Sent from my R800i using xda app-developers app
Guess what, i just checked on a Xperia Mini Pro with stock official ICS, no root, nothing modified and...the bug browser is here as well!
This Xperia Mini Pro has 4.1.B.0.587 but Hybrid Rom use the same build and has no bugs. How is that?
Dany XP said:
Guess what, i just checked on a Xperia Mini Pro with stock official ICS, no root, nothing modified and...the bug browser is here as well!
This Xperia Mini Pro has 4.1.B.0.587 but Hybrid Rom use the same build and has no bugs. How is that?
Click to expand...
Click to collapse
Thanks for info, it means it's firmware's bug. And i notice it's not just shortcut, it open two tabs from every aplication that have links who open browser (Timescape and XDA, for example).
Ps: Well, Krisdee is great dev, i'm sure he fix that bug.
Sent from my R800i using xda app-developers app
Bakisha said:
Thanks for info, it means it's firmware's bug. And i notice it's not just shortcut, it open two tabs from every aplication that have links who open browser (Timescape and XDA, for example).
Ps: Well, Krisdee is great dev, i'm sure he fix that bug.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Yeah, Krisdee somehow fixed it but HOW?!?!
Originally Posted by Dany XP View Post
That's the only bug I found until now. So right now is not backing up settings, passwords, bookmarks, etc, to my Google account.
Click to expand...
Click to collapse
Originally Posted by krisdee View Post
1. Uncheck the backup option in backup & reset options.
2. Exit and reboot into CWM
3. Fix permissions (advanced option) and reboot.
4. Install Terminal Emulator and type the following:
HTML Code:
su (press enter)
bmgr transport com.google.android.backup/.BackupTransportService (press enter)
(exit terminal)
5. Go back to settings, under backup & reset options and check the box for backup, and select your account.
6. Take care
Click to expand...
Click to collapse
Maybe he fix it like this
Megacubo said:
Maybe he fix it like this
Click to expand...
Click to collapse
I have no idea why it's working in Krisdee's ROM and why it's not working in SE official firmware...
But it's just small bug. Not so important IMHO
This don't help?
http://forum.xda-developers.com/showpost.php?p=38877687&postcount=111
Hi,
You may be aware of recent news about 2 different security vulnerabilities that allow replacing code on a signed APK while maintaining the original signature.
Master Key (Bug 8219321)
An issue related with duplicate entries on the ZIP / APK files.
It was patched by Google back in February 2013 and shared with OEMs, and some of the newer devices might have already received the fix in a recent stock update.
Bug 9695860
This also originates in the ZIP file parsing routines, and was disclosed just a few days ago immediately after the previous one was made public. The correction has already been applied by Google to the code,
Checking if you're affected - if youre running any ICS ROM on your Xperia 2011 you are
You can use 3rd party apps to test your system, such as:
- SRT AppScanner
- Bluebox Security Scanner
On Android 4.3 both of these bugs should be fixed, as well as on the latest CM's.
While technically different, both of these vulnerabilities permit that legitimate APKs can be manipulated to replace the original code with arbitrary one without breaking the signature. This allows someone to take an update from a well known publisher (e.g. Google Maps), change the APK, and a device receiving it will happily apply the update as if it was indeed from that publisher. Depending on the apps being updated in this way, priviledge escalation can be achieved.
Google has already mentioned that all apps published on the Play Store are checked for this kind of manipulation, but those of us installing APKs from other sources aren't safe.
Installation steps
1. Reboot to CWM
2. Flash the file
3. Wipe dalvik cache
4. Reboot to system - you're safe
Warning & Recomnendation
- This is a HUGE Issue. If you are installing apks outside from gplay often, its highly recomnend to apply this patch no matter what ICS based ROM you are running - Flash ROM, and immediately after flashing the ROM also flash the patch, than reboot.
Download
Grab it from here.
Changelog
1.0 - Initial version
Devs
Please implement this into your ROM! PM me for details.
Thanks to saurik!
If you appreciated this fix, consider donating with Paypal.
Thanks!
Placeholder
Umm I still dont get it :-/
What is this and what does it do
Edit
So basically it prevents edited apps from installing over the other?
Sent from my LT18i
Sahaab said:
Umm I still dont get it :-/
What is this and what does it do
Edit
So basically it prevents edited apps from installing over the other?
Sent from my LT18i
Click to expand...
Click to collapse
Search
http://www.saurik.com/id/17
jader13254 said:
Search
http://www.saurik.com/id/17
Click to expand...
Click to collapse
Thnx bro forgot about that
Sent from my LT18i
Sahaab said:
Thnx bro forgot about that
Sent from my LT18i
Click to expand...
Click to collapse
No problem, do you understand it now?
jader13254 said:
No problem, do you understand it now?
Click to expand...
Click to collapse
I am just about to after I eat
Wanted to thank u first
May I just ask one thing?
Isnt this sony's problem and not ours?
Sent from my LT18i
Sahaab said:
I am just about to after I eat
Wanted to thank u first
May I just ask one thing?
Isnt this sony's problem and not ours?
Sent from my LT18i
Click to expand...
Click to collapse
Its our AND sony's problem.
Ok, heres what the issue is:
- when you install an app, outside of gplay, a hacker can keep the original signature (and we will think its for example our nice google maps update), and the system will ask us to replace the original app. But the hacker modified the code, and it can acess to all things google maps does - internet, contacts, basically everything, and can send the information to servers, with your number, email etc. Also, it can send sms to premium numbers etc
jader13254 said:
Its our AND sony's problem.
Ok, heres what the issue is:
- when you install an app, outside of gplay, a hacker can keep the original signature (and we will think its for example our nice google maps update), and the system will ask us to replace the original app. But the hacker modified the code, and it can acess to all things google maps does - internet, contacts, basically everything, and can send the information to servers, with your number, email etc. Also, it can send sms to premium numbers etc
Click to expand...
Click to collapse
Oh so this will basically avoid that
Thnx bro
May I inplement it in my rom?
Sent from my LT18i
Flashed it and wiped dalvik cache. SRT App Scanner now says I'm safe. Thanks!
By the way, will this fix work on Jelly Bean?
LT18i
UHD 4.0 & UHD mod 4.8
Lupus kernel v16
pkazemi said:
Flashed it and wiped dalvik cache. SRT App Scanner now says I'm safe. Thanks!
By the way, will this fix work on Jelly Bean?
LT18i
UHD 4.0 & UHD mod 4.8
Lupus kernel v16
Click to expand...
Click to collapse
Doesn't work on JB, but CM includes it by default (cm 10.1)
deleted
eventhough I still have no idea how urgent it is, I just flash it anyway LOL
Here is my screenshot before and after flashing this fix using app srtscanner
alfstep said:
eventhough I still have no idea how urgent it is, I just flash it anyway LOL
Here is my screenshot before and after flashing this fix using app srtscanner
Click to expand...
Click to collapse
That means it works - fine
On UHD 3.0.2 bluebox security said not patched and srt app scanner is said that too ?
LT18i
Locked BL
tryed to flash 2x time but still not working..
Off course i wiped davilk cache...
I have replaced it manually but still not working !! (
Any solution ?
It works
Sent from my LT18i
deleted
Waiting for odexed version of this.
Work good with Ray.
One less fix run via xposed, thanks.
Jader , I would like to implement this in my next update..
Sent from my Xperia Neo V using xda premium