[Q] New type of Boot logo hang issue topic

I am getting a hang on the bootlogo
This happened after installing the OTA for 44S. if I boot reboot the phone 20 or 30 times I can get past it.
TWRP works fine. if you pay close attention when booting into recovery you see the 1+ logo, and just before TWRP loads the screen goes slightly brighter.
When booting into system, you usually see the 1+ logo, and then the screen goes slightly dimmer. Just after this the logo should change into the rotating animation.. This is where my phone hangs. Just after it goes dimmer but before the logo starts to animate.

Now here is the weird part. I've done all the tricks, returning to stock 44s deleting all the partitions and re creating them, deleting cache, dalvik, flashing a persist.img or manually creating that partition, etc etc. after many days of crying and swearing I flashed stock 38R. it boots 100% of the time. I flashed Calkulins 44S rom, back to hanging on boot. I then restored ONLY the boot partition from 38R, and my phone boots 100%
I can't stay on 38R boot/kernel as I have the jumpy touch screen and a few other bugs which 44S fixes.

Does anyone have any ideas?
In a nutshell, 44S boot hangs 95% of the time.
38R boot image works all the time for booting (but I need the bug fixes from 44S)

(working kernel: 3.4.0-cyanogenmod-g33fa374 build04@cyanogenmod #1 mon Oct 6 11:03:38 PDT 2014)

repo sync hang fix topic

I wonder if you are using VMWare to run Linux. I experienced the same problem as you until I've found what was causing it: the tcp window size on our side being set to 0 (full). I am running Ubuntu 10.04 on VMWare on Windows 7 64-bit as host. To fix it just make sure you give plenty of RAM to Ubuntu on VMWare to discard any memory issues. I had mine set to 512MB and increase it to 1.5M for better performance. Then the most important setting (and the one that did the trick actually): make sure you set the network adapter on VMWare to bridged mode. If using NAT for example, the NAT service will choke and mess the window size for you.

Cause: The TCP window size of a client tells the server the number of bytes it is willing to receive at one time from the server; this is the client's receive window. When the window is set to 0 it means that the client won't be able to receive any more data until it process whatever data is still pending in its internal buffers. This is normal TCP stuff. The size effect of a window set to 0 on a client is that a TCP connection will still be alive for some time until the server decides he has waiting enough and kill the connection. This is what was causing my repo sync to hang with no errors.