OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

Profile
Personal Photo
Options
Options
Personal Statement
ali1234 doesn't have a personal statement currently.
Personal Info
ali1234
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
Interests
No Information
Statistics
Joined: 16-May 18
Profile Views: 376*
Last Seen: 12th June 2019 - 06:17 PM
Local Time: Oct 14 2019, 12:43 AM
19 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Private
* Profile views updated each hour

ali1234

Members


Topics
Posts
Comments
Friends
My Content
5 Jun 2019
Today I was looking at my Gemini and I noticed that the battery has swollen to the point where the back cover is bulging out and it won't close properly because the keyboard can't move down. It closes if I take the back cover off. The battery has also become partially unstuck due to now being round instead of flat.

Attached Image

Attached Image
7 Jun 2018
    The Gemini kernel release from Planet has no git history. I spent the past week writing some software to correct this problem.

    The result is a repository where unmodified files are linked back to their original upstream history. This covers about 90% of the files in the repository.

    The process is mostly automated and was done like this:
    1. Export the Planet kernel source to a tarball, extract it, and remove the nested directory.
    2. Clone upstream repositories: linux-stable, linux-stable-rc, linux-next, linux-next-history, android-common, android-mediatek.
    3. Run 'gitxref <path/to/upstream/repo> <path/to/tarball/directory>' It does the following:
      1. For every file in the tarball, find a list of upstream commits containing that exact file.
      2. For all the found commits, count how many tarball files they exactly match.
      3. Print out the commit with the most matching files.
      4. For every remaining commit, count how many matching files they have, excluding the files that match the already printed commit.
      5. Repeat until there are no matched files left.
    4. Check out the upstream commit that has the most files in common with the tarball.
    5. Copy the tarball over it.
    6. Make a temporary commit of the resulting work dir, including new files: 'git add *; git commit -a'
    7. Get the sha1 of the tree of the commit you just made: 'git cat-file -p HEAD'
    8. Manually create a merge commit listing every matching upstream commit as a parent, and referring to the tree of the temporary commit: 'git commit-tree -p <parent sha1> -p <parent sha1> ... <tree sha1>'
    The result is this: https://github.com/ali1234/linux-gemini/tre...d075f04d4f7065a

    This should be considered a proof of concept. There may be errors in the merge. There may also be more upstream repositories which would be candidates for merging in order to produce a smaller diff. There may even be a better approach to the whole thing. Suggestions are welcome, here or in github issues.
    23 May 2018
    The Gemini keyboard seems to not have any diodes to prevent ghosting. For example with UK keymap if you press any three of the keys E, R, O, 0, then the fourth key will also be triggered. This can be confirmed to be a hardware bug by running "adb getevent /dev/input/event2" and holding down E, R, and O.

    https://deskthority.net/wiki/Rollover,_blocking_and_ghosting provides an explanation of why ghosting happens.

    There are many combinations of keys which do this. The most annoying is probably SHIFT, 9, 0, C, which is easily triggered if you try to type "()" because you are writing code...
    19 May 2018
    Hello,

    I made an Android app to display unique LED patterns when you receive an incoming call. The patterns are generated by turning the phone number into an integer, and then lighting up the LEDs according to the low 15 bits (approx 5 digits). This means each number should display a fairly unique pattern.

    Google Play: https://play.google.com/store/apps/details?...z.al.aledxander

    The source code is here: https://github.com/ali1234/ALEDxander

    Github release page (APK): Releases

    Shall I try to upload this to the Google app store?
    Last Visitors


    17 May 2018 - 5:13

    Comments
    Other users have left no comments for ali1234.

    Friends
    There are no friends to display.
    RSS Lo-Fi Version Time is now: 13th October 2019 - 03:43 PM