• GAPPS for all ROMs

    4.3/4.4 xda-developer

    • Google Stock (~272MB)
    • FULL (~217MB)
    • MINI (~128MB)
    • MICRO (~82MB)
  • Galaxy S2 Reference

    Mode

    • Enter recovery mode: UP + HOME + POWER
    • Enter Download Mode: DOWN + HOME + POWER

    Root

    There are 2 way to root:

    • via odin: ลง CF-Root-SGS2xxx.zip ที่ช่อง PDA ลง ClockWorkMod Recovery ก่อน แล้วค่อยไปจัดการ update ใน recovery โดยใช้ odin ก็คือ ลง file GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar ที่ช่อง PDA แล้วก็ค่อย reboot เข้า recovery แล้วจัดการที่เหลือ
    • via ROM ก็ถ้าลง ClockWorkMod แล้วก็ทำอะไรได้ในนั้น ถ้าลงผ่าน odin ก็ลงช่อง PDA เหมือนเดิม ใส่มันทั้ง ROM เข้าไป

    Download

    • Stock ROM: หาได้จาก sammobile ตามปกติ
    • Files ที่เกี่ยวข้องจากด้านบนหาได้ที่นี่ via Copy
  • Jekyll it is

    The change arrived. 10ninox blog turned into pretty minimal web pages. It was a bit harder on user’s side since there was nothing such as tag link, month page, search, and so on, but posts remained the same: URL, content.

    10ninox’s blog started by using WordPress, but over the past years, I haven’t been actively blogging and I did a lot more on coding side. Consequently, I figured out that I should have just turned the blog into an easier and cheaper process on my part. Nowadays, I prefered doing anything in text file; working in terminal; pushing stuffs from there to logging in to WordPress–previewing and publishing from there. Jekyll was one of the obvious choices. Why I picked Jekyll over anything? I didn’t know if there was anything better. I tried to find Jekyll alternative in Python, but no success. Jekyll was okay with markdown and I was comfortable with it. Since I didn’t code in Ruby, I was seemingly blind to configure in any way, but basic. Hopefully, one day, I would get around to work on that, but so far, this worked with only nginx and cheap VM and I couldn’t be happier.

    Thanks to Jekyll, Disqus, git, and nginx to make this possible.

  • Weird day - Spammers request to remove the links!? WTH?

    Unmaintained WordPress tends to get tons of spam comments regardless of how you do it. However, today, it’s a weird day.

    I got a request from one of spammers that the links they put on my mom’s blog was hurting them. So I checked that out. I didn’t even remember the password since it wasn’t maintained and my mom apparently hasn’t blogged for many years already.

    This is what I’ve found. The same IP addresses have spammed not only to this web site, but another as well. I suspected this firm did hire spammers for SEO or whatever, but now it’s damage control phase, huh? I have no clue what they are trying to do here since comment section on my mom’s blog isn’t even reachable. I migrated to Disqus years ago.

    The question was why the heck would I care? It sounds to me like he wants me to clean up his shit he dumped on my porch. If anyone has this sorta experience, please enlighten me.

  • psql could not connect to server

    There are a few problems when you think of Homebrew on OSX. This is a problem that has nothing to do with Brew at all.

    psql: could not connect to server: No such file or directory
    Is the server running locally and accepting
    connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
    

    When you find this error message while getting back from system crash, freeze, or any unexpected shutdown, it only means that there is a dirty PID file pointing out the somewhere empty. Basically every daemons will create .pid to store process number, socket and such, so when need, it will be able to do it right and delete right after shutting down the daemons. However, when unexpected shutdown occurs, no time for cleaning up .pid file, that’s where problems start. Everyone will think that the daemon is running (its .pid file exists) and asking for something, surely that .pid file can only lead to false route.

    Solution:

    you do clean up for system. In this case, Brew’s PostgreSQL .pid file is at /usr/local/var/postgres/postmaster.pid

    $ sudo rm /usr/local/var/postgres/postmaster.pid
    

    Then you can start your postgres again. It’s the same with every other daemons; you just need to find its PID file.