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

Search This thread
By:
Advanced…
N

newbieornah

Member
Jan 10, 2018
7
2
Steppnasty said:
1. Do you have s-off?
2. Can you capture a dmesg while the device is booting and attach it?
Click to expand...
Click to collapse

Yes I have s-off with eng hboot

And I'm not at all familiar with capturing logs, after researching on google the best I was able to do is this https://github.com/newbieornah/bootloop-log/blob/master/adb%20shell%20cat%20proc%20last_kmsg.txt
I've tried capturing logs during boot but adb wouldn't recognize my device unless it was in recovery
Sorry if it's not what you asked for but I have little experience past rooting and flashing stuff to this phone
 
  • Like
Reactions: Steppnasty
N

newbieornah

Member
Jan 10, 2018
7
2
Something of note: I was able to get 1.0.8 to boot with kernels from earlier versions of the rom (specifically tested the ones from 1.0.5 and 1.0.4), with a fair share of bugs of course, including the inabilities to adjust screen brightness and turn on WiFi.
So maybe its a kernel issue?
 
S

Steppnasty

Senior Member
Oct 11, 2012
77
99
Washington D.C.
newbieornah said:
Yes I have s-off with eng hboot

And I'm not at all familiar with capturing logs, after researching on google the best I was able to do is this https://github.com/newbieornah/bootloop-log/blob/master/adb%20shell%20cat%20proc%20last_kmsg.txt
I've tried capturing logs during boot but adb wouldn't recognize my device unless it was in recovery
Sorry if it's not what you asked for but I have little experience past rooting and flashing stuff to this phone
Click to expand...
Click to collapse

First, thanks for the feedback. I apologize for the delay as I have not had much time to look into this.

If there is a kernel panic before the USB/adb driver is loaded, you wont be able to pull a dmesg that way. Pulling the /proc/last_kmsg off of the phone may be the only way to get the kernel log. Pulling the battery will wipe or corrupt the last_kmsg so its a little tricky to get it if you have a kernel panic and the phone reboots a few seconds into boot. You can try this trick that works for me.
This assumes the phone does a full reboot (screen goes black then "T-Mobile Mytouch 4G" logo appears) when it crashes:
1. Disconnect phone from computer.
2. Reboot phone.
3. Hold the volume down & power button when the phone powers down for a reboot in order to reboot into recovery without pulling the battery. (This is tricky as you have to hold both buttons before the phone boots again (Mytouch 4g logo) but after phone loses power.
If you see a bootsplash when the phone boots the kernel panic will cause the bootspash to freeze momentarily. After a few moments have passed you should see the bootsplash move a few more frames before the screen goes black. Hold both buttons when the screen goes black.
If you see the Mytouch 4g logo and then the screen goes black and stays that way for several seconds, you may have to hold the phone at an angle to see if the backlight is on and when it turns off. When you see the backlight shut off, hold both buttons.
3rd scenario is the Mytouch 4g logo stays up for a longer than normal amount of time then screen goes black for a second before the system boots again. Hold both buttons when screen goes black.
This can take several attempts to work.
4. Once you are in recovery mode, do this: adb pull /proc/last_kmsg

If you are unable to get this to work, try to get another log the same way you got the last one. Last one was partially corrupted and I wanted to validate one particular section that stood out to me.
Also if you could post a dmesg from the recovery and/or a dmesg from a boot using a 1.0.4 or 1.0.5 kernel.

Lastly, what recovery and version are you using?
 
Zojak

Zojak

Senior Member
Aug 27, 2011
62
14
Dusted off my MT4G and flashed this rom. On 1.0.8 it would show the MyTouch 4G screen, go black then reboot.

1.0.7 and 1.0.6 did the same thing.
1.0.5 download was unavailable.
1.0.4 was able to boot.

My bootloader screen shows
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.09.04.26_M
eMMC-boot
Oct 11 2010, 12:44:14

My recovery is ClockworkMod 5.8.1.0.

Here is last_kmsg from 1.0.4 after rebooting into recovery.
https://pastebin.com/raw/UWnhpVQZ

I haven't been able to boot into recovery after a bootloop on 1.0.8. But I'll continue trying.
 
  • Like
Reactions: Steppnasty
S

Steppnasty

Senior Member
Oct 11, 2012
77
99
Washington D.C.
Zojak said:
Dusted off my MT4G and flashed this rom. On 1.0.8 it would show the MyTouch 4G screen, go black then reboot.

1.0.7 and 1.0.6 did the same thing.
1.0.5 download was unavailable.
1.0.4 was able to boot.

My bootloader screen shows
GLACIER PVT ENG S-OFF
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.09.04.26_M
eMMC-boot
Oct 11 2010, 12:44:14

My recovery is ClockworkMod 5.8.1.0.

Here is last_kmsg from 1.0.4 after rebooting into recovery.
https://pastebin.com/raw/UWnhpVQZ

I haven't been able to boot into recovery after a bootloop on 1.0.8. But I'll continue trying.
Click to expand...
Click to collapse

I have attached a modified kernel. Flash this on top of 1.0.8. Instead of bootlooping when the phone crashes, it should automatically boot you into recovery where you can do an "adb pull /proc/last_kmsg". I have also added some additional debugging logs.
 

Attachments

  • kernel-2.6.36-dbg.zip
    3.5 MB · Views: 4
  • Like
Reactions: Zojak
Zojak

Zojak

Senior Member
Aug 27, 2011
62
14
I must say I love the size of this device. Fits so nicely in my hand.

How do you open the recent apps screen on this rom? The physical buttons don't seem to bring it up.
nm. Hold down home button.
 
Last edited:
Zojak

Zojak

Senior Member
Aug 27, 2011
62
14
I ran into an issue with the phone not recognizing when headphones are plugged in. The back speaker continues to be used. Besides that this rom has been very good. Much more stable than the 3.0/4.0 roms I tried years back.

Also would you know how I can change which camera app launched when the camera button is pressed?
 
Last edited:
S

Steppnasty

Senior Member
Oct 11, 2012
77
99
Washington D.C.
Zojak said:
I ran into an issue with the phone not recognizing when headphones are plugged in. The back speaker continues to be used. Besides that this rom has been very good. Much more stable than the 3.0/4.0 roms I tried years back.

Also would you know how I can change which camera app launched when the camera button is pressed?
Click to expand...
Click to collapse

I don't know of a way to launch a different camera app with the camera button. The camera app has the code that listens for the CAMERA_BUTTON intent and then it launches itself. As for the headset issue, I am working on a fix for that.
 
S

Steppnasty

Senior Member
Oct 11, 2012
77
99
Washington D.C.
Zojak said:
I ran into an issue with the phone not recognizing when headphones are plugged in. The back speaker continues to be used. Besides that this rom has been very good. Much more stable than the 3.0/4.0 roms I tried years back.

Also would you know how I can change which camera app launched when the camera button is pressed?
Click to expand...
Click to collapse

Just an FYI. I was able to come up with a solution for selecting a different camera app with the camera button. I tested this with the Open Camera app. I also have a fix for the headphone issue and I threw in customizable hardware buttons from CM. I am currently trying to fix an issue with using the camera button to focus. If I don't see any other issues after I fix the focus button, I will push out the next release.
 
Zojak

Zojak

Senior Member
Aug 27, 2011
62
14
Steppnasty said:
Just an FYI. I was able to come up with a solution for selecting a different camera app with the camera button. I tested this with the Open Camera app. I also have a fix for the headphone issue and I threw in customizable hardware buttons from CM. I am currently trying to fix an issue with using the camera button to focus. If I don't see any other issues after I fix the focus button, I will push out the next release.
Click to expand...
Click to collapse

Sounds great.
 
You must log in or register to reply here.

Similar threads

febycv
  • Locked
  • Poll
[ROM][ICS][AOSP][Beta] .: :: Creamed Glacier :: :. [UPDATED 03.16.2012]
Replies
4K
Views
689K
febycv
febycv
...Awesome...
[ROM][AROMA][AOKP](11.02.12) Dark JellyBellyG1.1 Tweaked To Perfection!
Replies
3K
Views
521K
DavilaDarkness
DavilaDarkness
blackwing182
  • Locked
[ROM]5-23-2012[DiSCONTINUED]| AOKP-Insomnia Build 37 For MT4G
Replies
2K
Views
370K
GrimReaper24
GrimReaper24
eViL D:
[ROM] Virtuous Fusion MT4G v1.1.8 :: Gingerbread Sense 3.0/3D (6/10/2011)
Replies
5K
Views
555K
Elloco305
Elloco305
0.0
[ROM][JB][CM10][PORT]Jellybean Port from Desire S (12/06/2012)
Replies
978
Views
181K
mymeatb18
mymeatb18

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 28
    S
    Steppnasty
    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
    View
    7
    S
    Steppnasty
    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.
    View
    6
    S
    Steppnasty
    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.
    View
    5
    S
    Steppnasty
    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.
    View
    4
    S
    Steppnasty
    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!
    View

New posts