kexec bootloader bypass information thread

[ma5t3rw1tt]

should have cm10 in a day or two now...DancingNexus

----
Is this speculation or do you know for sure?

 

[jstafford1]

I'm guessing 2 weeks

Sent from my DROID3 using Tapatalk 2

 

[Vertigo RT]

I'm guessing 2 weeks

Sent from my DROID3 using Tapatalk 2

Agreed.

 

[ovelayer]

its purely speculation..however if you read through his twitter he allready has it booting on the d3..it just had some problems he had to sort out..knowing that he wants to get a build out to tease us

 

[pondd]

Hash posted this on XDA

Quick status update:
- I have successfully tested video decoding using the new ducati on the Kindle Fire (doesn't have a camera)
- And I'm now working on the new Moto kernel bringing it up-to-date so it can use the same drivers and ducati as the KFire, and once done it will be easier to update straight from TI. The new kernel version is 4AI.1.6 (3.0.31 mainline) for those that are curious.

Reading this thread and thinking about it some more, I will continue to do ICS builds as it's ready for the new codecs w/o any additional changes (once the kernel is done). Be nice to see what's going work and what isn't.

Once ICS is running well, I'll start on JB. Which will need audio changes and a bunch of optimizations.

Thoughts?

 

[cobravnm13]

Post by jonpry on XDA:

"Sound is not going well on the kexec builds. Granted I don't totally understand how it's supposed to work. Whatever it's supposed to be doing it isn't. The only ideas I have are super complicated. At this point I think it's best to have the RAZR kexec port move forward since there is a small chance audio will just work on RAZR and we can look at it to see how stuff is supposed to be happening."

Sent from my 3rd reincarnation of the ever-so-lovable Droid

 

[ovelayer]

From my end, I have a very set focus at the moment.

#1 for me is getting the new kernel merged up to a point where it can use all of the goodies I have for it.

This is a fairly long process starting with a grueling merge of code that I'm on day #4 of. Then, I get to debug the thing for days/weeks until most the kernels are resolved,. This includes turning back on the rpmsg system and debugging memory allocation issues that we had previously.

Only after that, do we finally get to see how effective this new ducati runs on the D3, and if it will work with our camera hardware, etc.

So sound issues aside, I still have several days/weeks before I can see a new bootup of the kernel in what I consider a really usable state.

#2 Once the new kernel is functional, I can choose 1 of 2 paths:
A) I could work on kexec binaries to use the new kernel on the other phones. This would be needed before we could test it on the RAZR and compare audio notes.
B) I could continue to troubleshoot the D3's audio w/o a reference point like the RAZR and see where it goes.

I'm not sure I would call that "back burner"


Sent from my XT894 using Tapatalk 2

if its not one problem its another that's slaps us d3 users

 

[hotpl8]

It did seem too good to be true, this was happening so fast. At least for now it hasn't been deemed impossible. See what the future holds...I did have an itch to flash something new though. This is the longest I've been on a single rom in about a year. Been a month on HGH. Getting bored

Sent from my DROID3 using Tapatalk 2

 

[brad92]

Post by jonpry on XDA:

"Sound is not going well on the kexec builds. Granted I don't totally understand how it's supposed to work. Whatever it's supposed to be doing it isn't. The only ideas I have are super complicated. At this point I think it's best to have the RAZR kexec port move forward since there is a small chance audio will just work on RAZR and we can look at it to see how stuff is supposed to be happening."

Sent from my 3rd reincarnation of the ever-so-lovable Droid

That's exciting for us RAZR users

But disappointing for y'all. Granted, coming from a DX to RAZR, and having had locked bootloaders that everybody said couldn't be bypassed, this concept amazes me

 

[jstafford1]

Dont get down. I think we'll be fine. Theres bound to be issues and building these kernels from the ground up takes time. It'll get worked out....be patient.

Sent from my DROID3 using Tapatalk 2

 

[MikeTheCat]

Dang you moto! It's so stupid how I have bugless CM9 on my OG DROID (Yes, it IS working lol) but the D3 can't have it thanks to the Boot Loader lockdown. Anyway, keep up the good work guys!

I'll be sticking with SteelDroid 5.x. It has sound. lol

~Paw Typed Without Thumbs From My Squeeking Mouse Phone~

 

[cloudstrife05]

Dang you moto! It's so stupid how I have bugless CM9 on my OG DROID (Yes, it IS working lol) but the D3 can't have it thanks to the Boot Loader lockdown. Anyway, keep up the good work guys!

I'll be sticking with SteelDroid 5.x. It has sound. lol

~Paw Typed Without Thumbs From My Squeeking Mouse Phone~

Steel Droid 5.x for the d3 has working call audio?

 

[lotzakritters]

Steel Droid 5.x for the d3 has working call audio?

It works the same as with all the ICS builds for the D3, with the same bugs. So it works sometimes. As for Steel Droid GB, yes it does..

Sent from my DROID3 using Tapatalk 2

 

[cloudstrife05]

It works the same as with all the ICS builds for the D3, with the same bugs. So it works sometimes. As for Steel Droid GB, yes it does..

Sent from my DROID3 using Tapatalk 2

Yeah I stopped using ics roms a while ago because of the audio.

 

[MikeTheCat]

It works the same as with all the ICS builds for the D3, with the same bugs. So it works sometimes. As for Steel Droid GB, yes it does..

Sent from my DROID3 using Tapatalk 2

Works 99% of the time for me. But ICS on my DROID 1 is truly incredible. lol I have no idea how, Though.