[ROM] [NIghtlies] Disarmed Toaster [CM10/PA/AOKP] - 0.2.0 (Unofficial)

Search This thread

agrabren

Inactive Recognized Developer
Mar 28, 2011
1,451
9,516
Weld County, CO
Family and friend this weekend, keeping me away from coding. But this week, I'll be getting extra time to dev, so starting Tuesday, things should make great progress.

Yesterday, I tried calling my wife, totally forgetting that phone is broken. Doh!

Sent from my Nexus 7 using xda premium
 

KaRLiKCZ

Senior Member
Feb 16, 2012
91
12
Plzen
I tried version 0.1.1 yesterday and Mobile data were not working. Strange was that charging wasn't working and showing all time 66 percent.
I was booted in second slot of Boot manager. My operator is Vodafone CZ.

Sent from my Evo 3D GSM.
 
P

phantom5

Guest
Boot Manager messes up charging and 3g.

Sent from my Nexus 7 using xda premium

the Multiboot thing? it messes upp even more. I had problems with kernel , wifi and bootloops when i used it ( other roms) it sucks that google only allows 15 minutes to get your money back when you bought something :(
now i have a useless app for €5 on my account...
 

testman86

Senior Member
Mar 23, 2012
351
112
the Multiboot thing? it messes upp even more. I had problems with kernel , wifi and bootloops when i used it ( other roms) it sucks that google only allows 15 minutes to get your money back when you bought something :(
now i have a useless app for €5 on my account...

I do it in a different way. What I do is switch off the device, boot in Recovery.

Then make a nandroidbackup of the current rom. Wipe evrything (wipe data/factory reset and wipe cache + dalvik) and flash the nandroidbackup of an other rom and use it.

Then, if you want to use the first rom again, reboot in recovery, make a nandroidbackup of the current rom, wipe everything and flash the nandroidbackup of the rom you want to use.

Its "hard" work, but then you have multiboot and everytime a clean system. With that way i use 2 roms in parallel and boot which i want to use.

I use 4EXT Recovery Touch v1.0.0.5 RC5

I hope this may help you :)
 
Last edited:

XzinteR

Senior Member
Aug 19, 2011
207
46
the Multiboot thing? it messes upp even more. I had problems with kernel , wifi and bootloops when i used it ( other roms) it sucks that google only allows 15 minutes to get your money back when you bought something :(
now i have a useless app for €5 on my account...

Main reason I occasionally pirate apps. I keep it for < day to try it out. After that I either buy it or uninstall it. It's my way of getting around the stupidly short return window

Sent from my Amazon Kindle Fire using xda premium
 

metamasterplay

Senior Member
Mar 20, 2011
351
120
Casablanca
the Multiboot thing? it messes upp even more. I had problems with kernel , wifi and bootloops when i used it ( other roms) it sucks that google only allows 15 minutes to get your money back when you bought something :(
now i have a useless app for €5 on my account...
What sucks is that you can't even resell it. Glorious were the days when I could freely exchange my Playstation CDs.
 

IxBUSTERxI

Senior Member
Jun 19, 2012
269
62
Berlin
Main reason I occasionally pirate apps. I keep it for < day to try it out. After that I either buy it or uninstall it. It's my way of getting around the stupidly short return window

Sent from my Amazon Kindle Fire using xda premium

+1
But with the bootmanager it is unnecessary, cause there is a free version, which is totally enough to have 2 systems neighboring each other.

I also use this ROM in dual boot, and for me 3G and wifi work flawlessly. I didn't try charging, but I will report back.

I installed it like this:

Nand of current ROM
Full wipe
Flash cm10 and gapps
Boot phone and set it up
Nand cm10
Restore first ROM
Execute bootmanager and restore nand of cm10.
:D

Sent from my ICS-powered HTC EVO 3D using xda premium


EDIT:
Charging really is screwed with dual boot and the battery always shows 66%...
 
Last edited:

al3xxx92

Member
Sep 4, 2008
9
1
A bug that I noticed : in videos playing fullscreen either YouTube or gallery, image is weird b&w with greenish tint and artefacts. Screenshots of it are normal, as well as vids playing in portrait. Also YouTube videos stop playing about halfway.
Stereo BT playback works for me. Hardware buttons' light works when using manual screen backlight.
 
Last edited:
  • Like
Reactions: Grea09

Grea09

Senior Member
Sep 12, 2007
99
11
Lyon
Done some test,

Whats broken :
  • Calls In/Out (can't hear and other people don't hear)
  • Video codecs : Youtube display weirdly (seem like a resolved bug from CM9)
  • 3D driver are buggy (Chrome bug)
  • MHL : works but orientation is in landscape while the screen display it in portrait. The image is correctly mirror but the screen display a LOT of glitches that makes it unusable (attachement) . Probably linked to 3D driver and codec.
  • And as said : 3D panel (driver is here though), camera, FM Radio
  • Internet sharing via USB or wifi

What's works :
  • Wifi
  • Data (bug the same way as before for me, like connection doesn't work and need a reinitialisation each time)
  • Mic and Google Now (some minor gliches)
  • Butter interface (smooth)
  • GPS
  • USB Mass Storage
  • etc

Don't need to update first page as it seems like you find it easy to resolve those bugs.
Agrabren enjoy your rest ;)
 

Attachments

  • Screenshot_2012-08-13-16-32-48.jpg
    Screenshot_2012-08-13-16-32-48.jpg
    98.7 KB · Views: 349
  • Screenshot_2012-08-13-16-33-01.jpg
    Screenshot_2012-08-13-16-33-01.jpg
    74.4 KB · Views: 345
Last edited:

agrabren

Inactive Recognized Developer
Mar 28, 2011
1,451
9,516
Weld County, CO
Done some test,

Whats broken :
  • Calls In/Out (can't hear and other people don't hear)
  • Video codecs : Youtube display weirdly (seem like a resolved bug from CM9)
  • 3D driver are buggy (Chrome bug)
  • MHL : works but orientation is in landscape while the screen display it in portrait. The image is correctly mirror but the screen display a LOT of glitches that makes it unusable (attachement) . Probably linked to 3D driver and codec.
  • And as said : 3D panel (driver is here though), camera, FM Radio
  • Internet sharing via USB or wifi

What's works :
  • Wifi
  • Data (bug the same way as before for me, like connection doesn't work and need a reinitialisation each time)
  • Mic and Google Now (some minor gliches)
  • Butter interface (smooth)
  • GPS
  • USB Mass Storage
  • etc

Don't need to update first page as it seems like you find it easy to resolve those bugs.
Agrabren enjoy your rest ;)

Thanks! That's great feedback, with clear details and even pictures which tell me which component is broken (the video decoder is having "issues", which is what that pseudo-static is). From the details and the images, I'm able to narrow down problems much quicker and provide fixes faster. Right now, I'm focused on the phone call aspect, because a phone without a working phone is... well... useless. At least to me. :)

But I've just done some code cleanup, so I should be able to rebase soon, too. But I'll hold off on rebase till things are stable. Last time I did a rebase, I lost all graphics out, and had to go fix all the QCOM display logic. :-/

This week, I'm also bringing up my auto-resolver. Its a machine configured to do all my "official" builds, as well as sync down all the latest changes from CM (and probably PA as a branch version), and make sure they all build. If they do, it'll auto-integrate and fire off a fresh build. If not, I'll get a message telling me I need to get integrations unblocked.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 215
    CyanogenMod 10 - Disarmed Toaster - Rearmed

    Current version: 0.2.9


    elW6.png


    This is an un-official ROM, and not directly supported by the CyanogenMod team.

    Background Information:
    While working on Devil Toast, it occurred to me that I enjoyed having "names" for the different ROMs, instead of just calling them "CM9", "CM10", etc... But then, what was I going to call Jelly Bean? And while I greatly appreciate all the help ToastCFH has given me in the Android community, it didn't make sense to continue naming my ROMs after him. Then it struck me, "Disarmed Toaster". The name originally came from Microsoft (I'm sure they're thrilled to have named an Android ROM) and their absolutely insane "Random Naming" scheme in the XBOX 360. My wife couldn't think up a nickname (if any of you can't guess what my nick is, you have a *serious* issue with pattern recognition) so the XBOX 360 suggested some for her. The one that caught her attention was "Disarmed Toaster". What exactly is an armed toaster? Do we need to start warning people of the dangers of armed toasters? Are they rising up against us? So after some mild chuckles, she selected it as her name. No, she doesn't play online. No, neither of us have a Gold account. We play "Ticket To Ride" on it, that's about it. So when I got Jelly Bean to boot for the first time and actually function, the first change I made was to name it "Disarmed Toaster", after the woman who really is the most important person in my life. When it became evident that I took Devil Toast as far as it was going to go without some serious code writing (for this unfamiliar, this is the act of writing source code. I don't do any smali hacking or binary swapping from other developers to make these ROMs), I decided it was time to cut over to Jelly Bean. So here it is, a pre-Alpha Jelly Bean ROM, named "Disarmed Toaster"

    Code:
    #include 
    /*
     * Your warranty is now likely void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * spontaneous combustion, your wife/girlfriend wanting
     * to have my babies, or any other host of cosmic penalties
     * which may befall you, your family, or your phone.
     *
     */

    What works:
    • Phone
    • Wifi
    • Camera
    • USB Mass Storage
    • Bluetooth
    • GPS
    • Car Dock
    • Google Now
    • Mutli-touch

    What doesn't work:
    • Anryl Kernel is missing (you can select it, but the actual boot image is missing from the package)
    • PDroid app is missing (you can download it from XDA). Framework is still properly installed.
    • Vanilla Kernel may or may not actually boot. It didn't boot for me, but mileage may vary?
    • Vanilla Kernel missing multi-touch patch
    • Random data drops
    • 3D
    • HDMI output

    Downloads:
    ROM: http://goo.im/devs/agrabren/cm10/shooteru
    Mirror: http://dl.nemec.co/agrabren/cm10

    GAPPS: http://goo.im/gapps/gapps-jb-20120726-signed.zip

    Kernel: Vanilla Kernel
    Toolchain: GCC ARM version 4.6
    Source: https://github.com/agrabren/android_kernel_htc_shooter.git

    Kernel: CoolExe ShooterU Kernel
    Toolchain: Linaro
    Source: git://github.com/Coolexe/shooteru-ics-crc-3.0.16-e733189.git

    Kernel Flashing:
    This ROM uses extra information contained in the boot.img file which standard mkbootimg doesn't understand and discards. To change the kernel, please download the unpackbootimg and mkbookimg tools located on goo.im next to the ROM itself. These are linux-only tools for the moment, but should unblock people from creating boot.img files which are compatible with Disarmed Toaster.

    Special Thanks:
    First, and most importantly, my wife Courtney, who this build is named after
    CoolExe and MikeC84 for offering me the ability to prepackage their kernels in the installer
    ToastCFH, who helped me learn both Linux and Android, as well as contributed largely to all HTC product development in CM
    Anryl, who has helped me along in the GSM community
    Binux-Project, for the amazing 3D Boot Animation
    TeamWin, cause I still love those guys
    DigitalHigh, who got me back into this stuff
    And HTC, makers of a great phone that failed only because of marketing and software...

    Version History
    0.2.0
    • Camera fixes
    • Bluetooth
    • AOKP added to ROM
    • Kernels included in AROMA Installer
    0.1.6
    • Fixes in build process, switch to Anryl and MAC Kernels
    0.1.5
    • Internal bugfixes, integration of latest codebases
    0.1.4
    • Fixed WiFi
    • Fixed Phone Audio
    0.1.3
    • Fixed Google Now
    • Broke Phone Audio (See a recurring trend?)
    • Broke WiFi
    • Fixed multi-touch
    0.1.2
    • Fixed issue with phone audio
    • Verified USB Mass Storage and GPS
    • Broke Google Now / mic
    0.1.1
    • Fixed mic issue when not in phone call
    • Fixed headset issue
    0.1
    • Pre-alpha builds
    106
    Bugfixes completed for next release
    • No video from YouTube or Gallery
    • PDroid 2.0 and V6 Supercharger patches for all three ROMs

    Bugs blocking next minor release

    Bugs blocking next major release
    • AOKP bootloops
    • Tile Rendering has corruption (visible in YouTube video playback)

    Planned Development: This list is subject to change
    0.4:
    • WiFi Tethering
    0.5:
    • 3D Camera and Gallery
    0.6:
    • YouTube 3D
    0.7
    • Battery Improvements
    75
    I'm actually working on the 3D camera at the moment. :) Why? Because I miss the 3D part of the EVO 3D. I'm not nearly as focused on my own "ROM" at the moment as I am creating the patches required to get all ROMs supported. I will, obviously, end up uploading my own ROMs for people to try and play with. But first, I want to get this feature working. :)

    It's a bit harder, Qualcomm took down some of the source code we used in the past. Good thing I'm stubborn. ;)
    72
    Flash a sense Rom and see if that makes a difference. If it's Sprint (CDMA), update your PRL and profile while you're there.

    New development well be on 4.2.1, since that's the code I'm now most familiar with. I thought I knew android before I started on Thor. I was wrong. But I'm coming back with new abilities and more understanding. I program Java now too! So no part of the system is off limits to me!

    Sent from my Nexus 7 using xda premium
    70
    Yes, still working on it. Work is, of course, still very hectic at the moment. But I'm also trying to get 4.2.2 fully building and functional. That's not a small task (sadly) but I'll get it working. Once we have something stable, I can put some nice touches on things like the LEDs. And I'm still in the process of learning more and more about the internals of Android and its architecture. That experience is invaluable for adding features like 3D support. So don't take my lack of updates as nothing happening, it's just nothing to release yet.