Jump to content

Dazzozo

Members
  • Content Count

    3,220
  • Joined

  • Last visited

Community Reputation

3,318 Excellent

2 Followers

About Dazzozo

  • Rank
    Hardcore
  • Birthday April 24

Contact Methods

  • Website URL
    http://dazzozo.com/

Profile Information

  • Location
    York, UK
  • Your Current Device(s)
    Crescent, G300, Y300, Nexus 5

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Okay but whatever, like, this is a pointless conversation. CEASE
  2. Who's a kid? :blink: I've been here for nearly 3 years. :p
  3. wow, that seemed really aggressive :blink: There's nothing wrong with being helped and you've certainly been asking for a lot of help in IRC, and you're all using forks of my work anyway. I did a ton of stuff before you even showed up, but it's okay to forget that right?
  4. It doesn't need F2FS, EXT4 works just fine, but everything else is pretty much correct. I don't think anyone is going to bother with display-legacy going forward. I'd be lying if I said I hadn't prepared the CAF stuff locally on KitKat a few weeks before L released. Put it this way: this is the only Android version that I can remember where the hardware buttons needed fixing. I was waking the device up by rebooting it over ADB for my first build.
  5. yep, it's one of the worst yet, completely turned a bunch of things on their head
  6. It's buggy for everyone, it's broken for you. :p
  7. Sorry guys! Been busy with my first term at uni, but I think you all deserve this.
  8. I don't really know why people insist on treating this ROM like I intend it to be a final and polished product. They're nightlies, no one said they were stable, the whole purpose of them is to shout at me when the build breaks so I can fix it. It often seems like having forum threads for them is beneficial to no one. Use whatever ROM you want, but at the end of the day you're using something I had a part in creating because a lot of them incorporate my work. ...anyway, sorry there hasn't been anything happening in the last few days, too much real life. :P
  9. Harassing Qualcomm isn't productive and there's a huge lack of understanding in that thread. They dropped the platform for a legitimate reason. This is just adding to the noise they have to sort through. There is a way forward, but it's a lot of work and I don't think I'm prepared to commit all that time on my own.
  10. I'll definitely look in to it, I can't say much more than that. Has it always been broken?
  11. That doesn't refer to *me*, it refers to the guy who authored it. A bunch of people are quitting CM recently. https://github.com/CyanogenMod/android_vendor_cm/commit/36cd9f57542ea3b3d00110d98b3b7fa3d974143e
  12. Hello, its been a long time. :o Hopefully you won't throw stones at me. :( I guess I should start at the beginning: I'm sorry for disappearing in the way that I did, it probably led to a bunch of complaints and drama but I have no idea. I had a bit of a crisis and just had to get out of everything, so I didn't really enjoy it either. :P The changes to the Jenkins/GetCM URLs I see being discussed are really just cosmetic - "thebronasium.com" refers to something that's long since dead and not relevant to what it was actually hosting in the last year or so. I don't think I broke any update flow in that change, GetCM will continue to serve on the old URL, and I have the domain for at least a year before a decision needs to be made on whether I drop it - hopefully long after anyone is using a build with the old URL baked in to the CMUpdater app. Speaking of GetCM, I'm going to have to clean out a bunch of old builds sometime soon, because 4*200MB every day adds up, and it was a pain when I moved server in May. Going forward, I don't really know what the plan is. Since January I've been maintaining the builds and nothing more. I have no idea if any bugs have popped up since then that need addressing. Looking further forward than that, L is obviously no more than a few months off from release and you can have a decent idea of the shape that it's taking if you know where to look. I have a feeling our "lazy" strategy with the kernel probably won't suffice for much longer (we're basically using a kernel that targets Android 4.1 on 4.4) and given that it's a major release, it might be the death of a few chipsets and I imagine more people than usual will probably not bother with it. Other than that, I'm going to pick up a few other projects unrelated to Android, as I really ought/want/need to. I want to learn something and break things again. :D
×

Important Information

By using this site, you agree to our Terms of Use.