I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.

Originally Posted by dewhashish

I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel

EDIT: i meant leaks, stupid typo

They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.

So Hashcode will have two builds.

1) - works on phones running the current stock GB kernel.

2) - works on phones running the leaked ICS kernel.

There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.

So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.

I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.

I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.

So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.

(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).

I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.

Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.

Sent from my XT894 using xda premium

Originally Posted by Rick#2

I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.

Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.

Sent from my XT894 using xda premium

Originally Posted by Rick#2

...

I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...

This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.

Sent from my Amazon Kindle Fire using Tapatalk 2

Originally Posted by Hashcode

This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.

Sent from my Amazon Kindle Fire using Tapatalk 2

If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire

Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?

Originally Posted by podspi

If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire

Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?

Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)

If that fails, Ill just use hard keys for D4's Safestrap temporarily.

Sent from my DROID4 using Tapatalk 2

..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)

I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/show....php?t=1688610

BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.

You will use the "System" backup to restore back to stock .206 to update later.

I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.