[ROM][JB][02/28/2019] aospSX 1.0.9

Search This thread

DJ Scooby Doo

Senior Member
Apr 13, 2012
785
146
New York City
lockergnome.net
ytu6a4yr.jpg


I took all of your advice and I'm trying out other browsers. I like Maxthon and Dolphin. :)

Sent from my brain using Tapatalk 4
 

unqualified

Senior Member
Nov 14, 2013
141
60
Denver
This ROM is great, I'm having only one issue after using for a few weeks - every few days, after sitting asleep in my pocket for a while I'll take it out to find it stuck in a boot animation and a fairly hot battery. I would read through the last_kmsg, but this ROM/kernel doesn't appear to have one? Is there another way to enable last_kmsg?

Sent from my MyTouch 4G using xda app-developers app
 
  • Like
Reactions: GronHog

Steppnasty

Senior Member
Oct 11, 2012
77
99
Washington D.C.
This ROM is great, I'm having only one issue after using for a few weeks - every few days, after sitting asleep in my pocket for a while I'll take it out to find it stuck in a boot animation and a fairly hot battery. I would read through the last_kmsg, but this ROM/kernel doesn't appear to have one? Is there another way to enable last_kmsg?

Sent from my MyTouch 4G using xda app-developers app
This doesn't sound like a kernel issue for the most part. I don't believe you would see a boot animation on a kernel panic. If you are able to grab a logcat through adb, it should point you towards the cause of the bootloop. While I don't know the cause of the initial crash, I will say that after a crash it is always best to do a manual restart of the phone. This is true with any Android rom.

Unfortunately if this issue is a bug in my code then a fix will not be included in my final ICS build which will be released either today or tomorrow.
 

unqualified

Senior Member
Nov 14, 2013
141
60
Denver
This doesn't sound like a kernel issue for the most part. I don't believe you would see a boot animation on a kernel panic. If you are able to grab a logcat through adb, it should point you towards the cause of the bootloop. While I don't know the cause of the initial crash, I will say that after a crash it is always best to do a manual restart of the phone. This is true with any Android rom.

Unfortunately if this issue is a bug in my code then a fix will not be included in my final ICS build which will be released either today or tomorrow.

I think it has resolved. I wiped dalvik & cache and flashed ICS gapps a few days ago due to an issue I was having with the Android/Google Keyboard (I didn't flash gapps on the initial install, because the rom had several google apps pre-installed and I was having trouble installing the ROM), and haven't had a single crash in the several days since.

This is a fantastic daily driver. Great work!
 

Steppnasty

Senior Member
Oct 11, 2012
77
99
Washington D.C.
I think it has resolved. I wiped dalvik & cache and flashed ICS gapps a few days ago due to an issue I was having with the Android/Google Keyboard (I didn't flash gapps on the initial install, because the rom had several google apps pre-installed and I was having trouble installing the ROM), and haven't had a single crash in the several days since.

This is a fantastic daily driver. Great work!

Awesome and thanks
 
  • Like
Reactions: CalicoJeb

BobZombiE

Member
May 1, 2012
44
15

I guess i will stay at this Rom untill some one release a KK 4.4 with camera & browser.

I was sick & tired of JB Slow and laggy Roms with GSM signal drop!! And KK Roms does not have browser or Camera but they are really fast.
So i decided to use Synthetic aospX , then i saw you updated this just 1 days ago :good:

Really fast Rom , and still did not find any problem, just 1 unwanted reboot in 12 hours of heavy use with lots of applications running in background. And for me that's nothing special.

Thank you
 

estallings15

Senior Member
Apr 22, 2011
6,201
2,547
Did a clean install of the latest build, followed by gapps. Setup continually FC's. Wiped dalvik/cache and rebooted. Same thing. Tried another install with different gapps. Same. Wiped caches again. Same. Reflashed ROM only with intention of downloading the old version of the ROM to install and then dirty flash over. However, on reboot, all was well. I just went into settings and added my gmail.

I'm not sure what happened, but whatever works. Fantastic ROM, BTW. Nice update, OP.

Sent from my MyTouch 4G using Tapatalk
 

GronHog

Senior Member
Jun 25, 2012
133
34
cameron park
Any body else getting random signal drops. Did not get any when using viper touch. If your not getting any drops, what radio you using.

Sent from my MyTouch 4G using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 28
    I am not responsible for anything you do to your device.

    Current Android Version: 4.2.2
    Current Kernel: 2.6.36

    Features

    Project Butter (ION Memory Management, Improved VSYNC & Triple Framebuffer)
    Open source camera daemon

    Downloads
    aospSX:

    ROM: aospSX 1.0.9
    GAPPS: JB 20130812
    Stepp_aospX:
    ROM: code.google.com Final md5sum - 714b512470643e582ea75c08f65b2a40
    GAPPS: ICS 20120317

    Installation
    Make sure you have S-OFF
    I recommend backing up all data
    Wipe data and cache (Recommended but optional if updating from aospX or aospSX)
    Flash ROM
    Reboot

    Notes
    OTA Updating

    As of 2/19/18, OTA is functional. Currently hosting OTA ROM on DropBox. Previously used XDA's devDB for OTA but they removed the ability to link directly to the ROM.
    Tested on CWM recovery. Let me know of any issues.
    If update fails in recovery, download is located in /sdcard/OTA-Updater/download/ folder.

    Issues
    Known Bugs

    none
    Known App Incompatibilities
    none

    Changelog - The short version
    Code:
    [B]1.0.9[/B]
    - Fixed boot crash for Glacier phones with "M4G2DE" model internal flash.
    - Fixed issue where headphones were not recognized.
    - Added hardware key custom rebinding from CM.
    - Allow camera button (long press) to select different camera app.
    - Camera Updates
      - Fixed issue where using the camera button to focus would not turn off LED when button is released.
      - Fixed issue where using the camera button to focus would break the next call to focus.
      - Fixed occasional freeze when taking a picture.
    
    [B]1.0.8[/B]
    - Switched to JB sound package.
    - Fixed bug where incorrect signal strength was being reported.
    - Camera Updates
      - Added Auto-Focus
      - Auto exposure improvements
      - Added WVGA camcorder mode
    
    [B]1.0.7[/B]
    - Added blue notification led
    - Fixed display auto-brightness
    - Fixed physical button lights
    - Fixed issue where SetupWizard would not finish properly
    - Fixed YouTube video playback.
    - Fixed issue where copying to phone with USB Mass Storage would be 3 times slower.
    - Camera Updates
      - Added flash for camera.  This also fixes Torch.
      - Tweaked auto exposure to adjust faster.
    - Kernel Updates
      - Tweaked power management idle and sleep modes.
      - Fixed trackball wake when sleeping.
      - Fixed issue where CPU frequency was stuck at 768Mhz.
      - Fixed issue where user-configured max CPU frequency not being restored at boot.
      - Added overclocking support.
      - Allow CPU frequency to be underclocked at 192Mhz. Originally set at 256Mhz.
    
    [B]1.0.6[/B]
    - Lots of kernel updates:
        - USB driver updated to JB 4.2.2 from CAF
        - Kernel version updated to 2.6.36
        - Clocks, power management, etc updated to 2.6.38/CAF.
    - Improvements made to camera daemon
    - GPS Fixed
    - Added current CPU speed in Performance settings.
    
    [B]1.0.5[/B]
    - Fixed SIM card not being recognized
    - OTA Tweaks
    
    [B]1.0.4[/B]
    [U]Android updates[/U]
    - All but four ICS packages updated to JB MR1
    - OTA Updater fixed
    - Performance settings, Advanced reboot and Kill app back button options re-added from aospX
    - Root access settings added
    - Complete rewrite of mm-open-daemon:
        - Added support for front facing camera
        - Improved auto exposure algorithm
        - Wrote formulas to calculate several VFE settings instead of hard coding them, allowing different camera modes to be utilized
        - Added different modes/resolutions for both camera sensors
        - Various other fixes/improvements
    - Updated to CAF Camera App
    - Adreno Blobs Updated to JB MR1
    - Fixed bug where animations would not render the last frame
    - Fixed audio not recording for camcorder
    
    
    [U]kernel updates[/U]
    - Framebuffer driver updated
    - GPU driver updated
    - New Camera2 driver for MT9V113 (FFC)

    Thanks/Credits
    Synthetic.Nightmare - big thanks for his guidance/support and for providing the base for which I am using for this rom.
    The aospX team
    The CyanogenMod Team
    XDA developers
    Code Aurora Forums
    Other devs still keeping this phone alive
    Anyone else I may have forgotten

    XDA:DevDB Information
    aospSX, ROM for the HTC Glacier: myTouch 4G

    Contributors
    Steppnasty
    Source Code: http://github.com/steppnasty

    ROM OS Version: 4.2.x Jelly Bean
    ROM Kernel: Linux 2.6.x
    Based On: AOSP

    Version Information
    Status:
    Stable
    Current Stable Version: 1.0.9
    Stable Release Date: 2019-02-28

    Created 2014-08-17
    Last Updated 2019-03-01
    7
    Since the last update I have been working on getting the camera operational. I could have taken the easy route and just brought up PMEM just for the camera but that would have been messy and it would make any future updates I do a PITA. So I dove into the code and learned a few things that I thought I would share here since it is difficult to find any documentation online. First of all I originally thought that libcamera was made open source for jellybean. This is actually only partially correct. When I was trying to make the libcamera code work I kept running into issues where it felt like the code was not finished. For instance, libcamera would send an IOCTL to the kernel and expect a response from a second non-existant thread. After writing in a substantial amount of "missing" code into libcamera in an effort to "complete" it, I decided to google one of the IOCTLs that were missing from libcamera. I managed to find something on a chinese website that wasn't much help except for the title of the page which was "mm_qcamera_daemon". After doing some research on this I came to the conclusion that the "missing thread" from libcamera was actually a separate program that communicates with libcamera and the kernel driver. So prior to Jellybean the camera was structured like this:

    Camera App->android frameworks->libcameraservice->camera HAL->libcamera->liboemcamera->kernel driver

    As of Android 4.2.2 it was reworked to look something like this:

    camera App->android frameworks->libcameraservice->camera.msm7x30->libmmcamera_interface->kernel driver
    mm_qcamera_daemon->kernel driver

    Basically the proprietary imaging functions were moved out of the main thread and into a separate executable that runs at boot. There were significant changes made to the kernel drivers that are similar to the changes made to the framebuffer drivers. The camera sensor drivers have had most of their functions moved to a sort of shared sensor driver with the actual sensor drivers mostly holding specific register settings. A lot of the changes were made to tie the camera sensors into Video For Linux 2 (V4L2). Userspace functions in libmmcamera & mm_qcamera_daemon then talk to the camera drivers through V4L2.

    So I managed to write a Jellybean camera sensor driver for the main rear camera that works with this new format. I have also made progress writing a program that will act as the daemon. Currently I have a camera preview on the rear facing camera. I still have clean up to do on my local code before I commit as everything is a mess right now. I am trying to get everything close to the jb_mr1.1-release branch AOSP with as few modifications as possible. If everything goes smoothly I should be able to post the next release in a couple of weeks.
    6
    Just posted new version (4.2.2). This is still a work in progress so expect a few bugs that I don't know about.
    5
    1.0.3 is up. Lots of bug fixes, camera fixes, etc. Let me know if you dirty flash and are unable to find the Camera app. Or any issues that is.
    4
    1.0.2 is up! Lots of updates. Rear camera works. Sort of. Still a work in progress but I figured I would add the theme manager as a distraction. So enjoy!