[ROM][4.4.4][Unofficial] Beanstalk - Togari_GPe[2014-07-27] - Sony Xperia Z Ultra

Unofficial build of Beanstalk Kitkat 4.4.4 for the Togari_GPe
[#BeanstalkHead]
Sources:
This ROM is built from source using
Scott's git
CM's git
My changes to CM's tree etc
CM's kernel with changes for ZU with DT2W
[#BeanstalkFeatures]
Install:
[#Install]
Not Working:
Recovery, you may need to flash a CM11 kernel from Carbon or CM to get recovery back
"fastboot flash boot boot.img"
Working:
Looks like most everything works well except some camera glitches
Camera fix / workaround "Another Camera Fix (It's really a workaround) to try > Post #23"
Download:
Build 2: BeanStalk-4.4.4010-20140808-togari_gpe.zip
Build 1: BeanStalk-4.4.4010-20140729-togari_gpe.zip
Credits:
Scott of Beanstalk Team for the ROM
CM (Kali et al) For the device tree
krabappel and [vertigo] and many others
XDA:DevDB Information
Unofficial Beanstalk for Togari_GPe, ROM for the Sony Xperia Z Ultra
Contributors
blueether, scotthartbti, [vertigo], CM, AOSP
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Togari with Unlocked Bootloader
Based On: CM et al.
Version Information
Status: Testing
Created 2014-07-29
Last Updated 2014-08-08

---

Looks good. Can't wait to test drive another ROM for the gpe.
Sent from my Gpe Z Ultra using XDA Free mobile app

---

I'm trying this right now. Everything seems to work correctly except for booting into recovery. Whenever I try to boot into recovery after flashing this rom I end up with a black screen. It doesn't matter if I try to enter recover at boot using the volume keys or if I try to do it from to reboot menu when shutting the phone down.
I'm going to have to flash another kernel to get the recovery back.

---

fzurita said:
I'm trying this right now. Everything seems to work correctly except for booting into recovery. Whenever I try to boot into recovery after flashing this rom I end up with a black screen. It doesn't matter if I try to enter recover at boot using the volume keys or if I try to do it from to reboot menu when shutting the phone down.
I'm going to have to flash another kernel to get the recovery back.
Click to expand...
Click to collapse
Just extract the one from Carbon and flash with fastboot or flashtool. Sorry about that

---

blueether said:
Just extract the one from Carbon and flash with fastboot or flashtool. Sorry about that
Click to expand...
Click to collapse
I'm starting I think the problem is in my end. I flashed the carbon kernel and I still cant get into recovery.
Oddly enough, I seem to have no problem getting into recovery using doomlords advanced stock kernel.
How do I get into recovery using your kernels @blueether?
Also, is there any way to disable dt2w? It seems to have a pretty good battery drain.

---

fzurita said:
I'm starting I think the problem is in my end. I flashed the carbon kernel and I still cant get into recovery.
Oddly enough, I seem to have no problem getting into recovery using doomlords advanced stock kernel.
How do I get into recovery using your kernels @blueether?
Also, is there any way to disable dt2w? It seems to have a pretty good battery drain.
Click to expand...
Click to collapse
You should get into recovery just like doomlord's, press vol up when the LED comes on just after boot starts.
I'm sorry that I cant test these builds out at the moment
You are the first to complain about battery drain with dt2w. It should't have a wake lock and will allow the phone to go into deepsleep, but to disable do this from a terminal:
Disable DT2W:
In terminal write: su -c "echo 0 > /sys/android_dt2w/dt2w_active"
After reboot DT2W will be activated again. If you want to make it disabled by default add the above init.d script!
Click to expand...
Click to collapse

---

Hmmmm, I can't seem to get dt2w disabled. The directory /sys/android_dt2w doesn't seem to exist.. The mkdir command in the sys directory doesn't seem to work either.
Also, I installed doomlords kernel with dual recovery again just to make sure, and recovery works just fine in that kernel with the volume keys. @blueether are there any logs I can grab to help debug the issue? If it helps, the screen seems to get stuck in the sony logo with the led showing green whenever I attempt to boot recovery from your kernel

---

fzurita said:
Hmmmm, I can't seem to get dt2w disabled. The directory /sys/android_dt2w doesn't seem to exist.. The mkdir command in the sys directory doesn't seem to work either.
Also, I installed doomlords kernel with dual recovery again just to make sure, and recovery works just fine in that kernel with the volume keys. @blueether are there any logs I can grab to help debug the issue? If it helps, the screen seems to get stuck in the sony logo with the led showing green whenever I attempt to boot recovery from your kernel
Click to expand...
Click to collapse
I remember now... I removed some of the code as the original writer packed a sad and threw their toys out of the pram (I still think that if they use GPL code the have to live by the GPL).
If you think that dt2w is causing battery drain then all I can suggest is to flash the boot.img from the latest ZU gpe CM11 builds. If I did a kernel without dt2w it would just be the same as the CM one.

---

blueether said:
I remember now... I removed some of the code as the original writer packed a sad and threw their toys out of the pram (I still think that if they use GPL code the have to live by the GPL).
If you think that dt2w is causing battery drain then all I can suggest is to flash the boot.img from the latest ZU gpe CM11 builds. If I did a kernel without dt2w it would just be the same as the CM one.
Click to expand...
Click to collapse
Ok... I flashed cm stock kernel and recovery doesn't work there either. I'm thinking that the issue is that I flashed TWRP into the FOTAKernel partition. Is TWRP for xperia z ultra compatible with the gpe edition of the device?

---

fzurita said:
Ok... I flashed cm stock kernel and recovery doesn't work there either. I'm thinking that the issue is that I flashed TWRP into the FOTAKernel partition. Is TWRP for xperia z ultra compatible with the gpe edition of the device?
Click to expand...
Click to collapse
yeah I don't know what effect that will have, I think I remember @DooMLoRD saying that it wont flash a recovery to FOTA?

---

Download:
Build 2: BeanStalk-4.4.4010-20140808-togari_gpe.zip
Wedding anniversary edition

---

On your latest build successful I flashing pimped via flashtool but still can't boot into recovery. When first book image comes up and first led flashes I press volume up and stays on logo. But I am able to boot back into ROM no issues

---

diamantericos said:
On your latest build successful I flashing pimped via flashtool but still can't boot into recovery. When first book image comes up and first led flashes I press volume up and stays on logo. But I am able to boot back into ROM no issues
Click to expand...
Click to collapse
does this use the default dpi from the stock rom or does it have the 320 dpi? also what is teh actual default dpi? 400
?

---

runsoverfrogs said:
does this use the default dpi from the stock rom or does it have the 320 dpi? also what is teh actual default dpi? 400
?
Click to expand...
Click to collapse
this is using 320 (native dpi) the GPe uses 400 for some strange reason

---

blueether said:
this is using 320 (native dpi) the GPe uses 400 for some strange reason
Click to expand...
Click to collapse
just a request, do you guys know if 320 dpi, fifa game works? thats what i dont like about my GPE, the fifa game isnt' compatible for some reason. maybe its the dpi setting?

---

runsoverfrogs said:
just a request, do you guys know if 320 dpi, fifa game works? thats what i dont like about my GPE, the fifa game isnt' compatible for some reason. maybe its the dpi setting?
Click to expand...
Click to collapse
This one? Or another?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

blueether said:
This one? Or another?
Click to expand...
Click to collapse
oh wow! so it is the dpi that's making it incompatible with my stock gpe! okay looks like im flashing this rom.. thanks for your help!

---

runsoverfrogs said:
oh wow! so it is the dpi that's making it incompatible with my stock gpe! okay looks like im flashing this rom.. thanks for your help!
Click to expand...
Click to collapse
that Screen Shot was in the GPe Carbon not Beanstalk, but should be the same.
Or just root and edit the build.prop and change the lcd to 320 dpi

---

blueether said:
that Screen Shot was in the GPe Carbon not Beanstalk, but should be the same.
Or just root and edit the build.prop and change the lcd to 320 dpi
Click to expand...
Click to collapse
ohh that would be easier, let me try that.