[ROM][JB][02/28/2019] aospSX 1.0.9
- Thread starter Steppnasty
- Start date
It's amazing this device still has development.
I wish I still had it just to play with.
Sent from my LG-H901 using Tapatalk
I wish I still had it just to play with.
Sent from my LG-H901 using Tapatalk
Thanks for update.
yours gapps links are dead. I downloaded from other site gapps-jb-20130812-signed.zip.
Just install it. wifi and mobile signal very very low.
Signal strength 2147483647 dBm 255 asu. It must be -60 dBm here where im sitting.
Last edited:
Thanks for the heads up. I will take a look at that.
Also, I uploaded the gapps I've been using to this site and updated the links. I feel like I need to scrub my hard drive everytime I go to Devhost(d-h.st.com) so its probably for the best that I stop using them to host files.
Thanks for keep it up. Is that busybox, Xposed, gravitybox supported I have made little modification with these apps.
Busybox is included. You should be able to install the Xposed framework but I can't vouch for the modules. I know nothing about gravitybox so I can't give you any info on support for it.
So, I take a try to install these.
trackball to awake only work when phone have been charge, otherwise not work
Last edited:
Which version are you running? In version 1.0.6, there is a bug in the power management that was putting the trackball gpio to sleep when it is off-charger but this is fixed in 1.0.7.
I have updated the bug section on the main post with the signal strength issue. I found the problem with and I have it fixed on my test phone so the fix should be in the next version I release.
1- Running 1.0.7. trackball not working for me. (screenshot below)
2- Write access denied at sys/android_touch.
3- I have in previous its working well for me. Would you like to add sweep2wake feature. (screenshot below)
Attachments
Verify that Settings->ASX options->Trackball Wake is checked.
If the box is check and you are still unable to wake with the trackball then:
1. Reboot into recovery
2. Backup
3. Wipe data/factory reset
4. Reboot
Let me know if this works.
Actually do this instead:
1. Reboot into recovery
2. Backup
3. Wipe data/factory reset
4. Re-flash 1.0.7 without flashing GAPPS
5. Reboot
I also flashed this ROM but the trakpad waking isn't working. However this is really a minor thing for a well functioning ROM. I did not expect this phone is still supported by the community. Truly amazing work thank you! Now my MT4G is awaken from a 4 year hibernation and will serve as a smart remote in my living room
.I also flashed this ROM but the trakpad waking isn't working. However this is really a minor thing for a well functioning ROM. I did not expect this phone is still supported by the community. Truly amazing work thank you! Now my MT4G is awaken from a 4 year hibernation and will serve as a smart remote in my living room
Thank you. As long as people are still using this phone, I have a reason to continue working on it.
As for the trackball issue, I cannot replicate this on my phone which leads me to believe there may a difference in hardware or firmware.
What recovery type and version are you using?
Also what is the version of radio that you are using?
Would it be possible to attach a dmesg of the issue?
Thanks
Boot loop when trying to flash
I can't for the life of me get the latest version to install. I've tried doing it through several recoveries and have tried several versions of the rom. The highest I've been able to flash is 1.0.5, and it was buggy as hell. Anything higher and my phone will get stuck in the boot sequence (won't go past the splash screen). I've also tried doing it via OTA update on 1.0.4 (1.0.5 OTA wouldn't work), and it would fail after download. Any suggestions?
I can't for the life of me get the latest version to install. I've tried doing it through several recoveries and have tried several versions of the rom. The highest I've been able to flash is 1.0.5, and it was buggy as hell. Anything higher and my phone will get stuck in the boot sequence (won't go past the splash screen). I've also tried doing it via OTA update on 1.0.4 (1.0.5 OTA wouldn't work), and it would fail after download. Any suggestions?
1. Do you have s-off?
2. Can you capture a dmesg while the device is booting and attach it?
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
28I 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-017Since 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.6Just posted new version (4.2.2). This is still a work in progress so expect a few bugs that I don't know about.51.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.41.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!
New posts
-
-
-
Question Rom recommendation? Please read- Latest: ABuilderProbably?
-