[ROM] Atrix-MROM-ICS [CM9] build:20121114

[WuchuHurD]

At first its a little laggy and reboots some but after constant use it doesn't hang up as much and reboots are now very rare. Overall the feel is pretty smooth and quick and the only glaring issue is the battery drain.

Also it seemed to sort of fix a keyboard issue that I have, in that my keyboard fully functional in landscape mode. This is an entirely isolated incident as this problem arose a few weeks ago and haven't really been able to solve it.

 

[rancur3p1c]

Now of only someone could leak us a more stable version of the ICS kernel, we'd be merrily on our way...

 

[DomeATRIX]

I just installed the ROM. I chose the RamFix 1100 by luck and it booted well and its working. That means that thats my tegrapart right? If I would have chosen d00 iy wouldnt work right?
Thanks in advance.

 

[Zeljko1234]

I just installed the ROM. I chose the RamFix 1100 by luck and it booted well and its working. That means that thats my tegrapart right? If I would have chosen d00 iy wouldnt work right?
Thanks in advance.

Obviously you should play the lottery

 

[Bert.C]

I just installed the ROM. I chose the RamFix 1100 by luck and it booted well and its working. That means that thats my tegrapart right? If I would have chosen d00 iy wouldnt work right?
Thanks in advance.

I think itd work anyway, but you would only have about half of your available ram if it was wrong. So it would lag like hell.

Sent from my MB860 using xda app-developers app

 

[Cris123]

Tried last night with D00 RAM fix.

Was looking good and running very nicely until I hit the power button. The screen would tear on the lock screen. Battery pulled and rebooted, all was well until I hit the screen timed out and tore again on wake up.

Great work and I'm really looking forward to trying with a revised kernel. :good:

 

[kennethpenn]

Please stay on topic and relevant to the discussion at hand. If your post doesn't contribute anything, then it shouldn't be submitted.

 

[Alcapone263]

Take the above post as an example of a post that doesn't contribute anything :banghead:

at the risk of being off topic myself, KP is a moderator for our forums. he was kindly asking people to stay on topic in this thread, and you immediately posted after him a non-related post.

granted, i myself am disobeying him by pointing out your mistake, but i feel as if you should know to respect the moderators a little more, they dedicate quite a bit of their time into reading reports, and keeping the forums from becoming any worse than they are already.

(Kenneth, please delete this post the next time you go through and clean this thread up)

 

[jersonf]

Got a first random reboot this morning whilst making a call......to my supervisor as to why I'm running late

Was running catlog with errors only filters at the time.

Can't attach logcat zip at the moment, but if anybody wants it... it available.

Edit: used d00 ramfix fix, thanks for the 855mb

100r radio and the usual battery drain etc.


Sent from my MB860 using xda premium

 

[EkzoMan]

Here's my list of bugs after 3 days of use ROM.
1. Battery life is about 6 hours of normal use.
2. GPS can't find any stellite.
3. Wi-Fi disconnect every 30-40 minutes of regular use.
4. Rington cough first 2-3 seconds after device wake up.
5. Screen wake up in 2-4 seconds after recieve incoming call.
6. Screen doesn't wake up on incoming SMS/MMS.
7. Permanent disconnect from mobile internet until reboot.
8. No flash light in cam app.
9. Alarm doesn't play sound.
10. Not sure if this ROM problem or only mine, but my hands free button doesn't work (I've try 2 different sets).
11. There are random reboots on Google Navigation app startup

 

[eddhard]

I fixed GPS by down loading GPS status app. Data was fixed my manually editing my provider setting.

I've had no reboots. Screen wake up some times slow but in general I'm finding it all good.

Sent from my MB860 using XDA Premium HD app

 

[EkzoMan]

I fixed GPS by down loading GPS status app. Data was fixed my manually editing my provider setting.

I've had no reboots. Screen wake up some times slow but in general I'm finding it all good.

Sent from my MB860 using XDA Premium HD app

Ok, I'll try to reinstall ROM and apply all fixes. After that post replay.

 

[mmontuori]

Got a first random reboot this morning whilst making a call......to my supervisor as to why I'm running late

Was running catlog with errors only filters at the time.

Can't attach logcat zip at the moment, but if anybody wants it... it available.

Edit: used d00 ramfix fix, thanks for the 855mb

100r radio and the usual battery drain etc.


Sent from my MB860 using xda premium

If you could provide the logcat containing the crash, it would be great...

Sent from my MB860 using xda app-developers app

 

[scanuto]

Was the kernel built from source or you just pull it off from the leak?

 

[extreme70]

Was the kernel built from source or you just pull it off from the leak?

Leak

If you could provide the logcat containing the crash, it would be great...

Sent from my MB860 using xda app-developers app

I think logcat will not help us with random reboots. I analyzed ~15 logcats recorded just before reboot (my atrix "likes" every "that" stuff) and there's nothing interesting, only normal system and apps activity and

E/NetlinkEvent(  173): NetlinkEvent::FindParam(): Parameter 'MDM_SHUTDOWN' not found
D/HWC_HDMI_MOT(  174): wait_for_extdisp_service: try to connect to ExtDisp service IPC
E/HWC_HDMI_MOT(  174): connectToExtDispIpc: Client Failed, No IPC Server

repeating all the time. So many times that logcat from night (30 minutes of usage, ~8 hours of sleeping and 5min usage, all the time plugged into charger) has more than 150k (!) lines. Weird.

Another think I noticed is

D/AudioHardwareMot(  177): AudioStreamOutMot::standby called for 0x7e4738
[COLOR="Red"]D/AudioHardwareMot(  177): Changed Min CPU Frequency to 300000 KHz[/COLOR]
E/AudioHardwareMot(  177): Error:Cannot change smp affinity for irq 124 [COLOR="Red"](Permission denied)[/COLOR]
D/AudioHardwareMot(  177): Output 0x7e4738 standby complete

Is audio affecting CPU minimal frequency?

 

[mmontuori]

Leak



I think logcat will not help us with random reboots. I analyzed ~15 logcats recorded just before reboot (my atrix "likes" every "that" stuff) and there's nothing interesting, only normal system and apps activity and

E/NetlinkEvent(  173): NetlinkEvent::FindParam(): Parameter 'MDM_SHUTDOWN' not found
D/HWC_HDMI_MOT(  174): wait_for_extdisp_service: try to connect to ExtDisp service IPC
E/HWC_HDMI_MOT(  174): connectToExtDispIpc: Client Failed, No IPC Server

repeating all the time. So many times that logcat from night (30 minutes of usage, ~8 hours of sleeping and 5min usage, all the time plugged into charger) has more than 150k (!) lines. Weird.

Another think I noticed is

D/AudioHardwareMot(  177): AudioStreamOutMot::standby called for 0x7e4738
[COLOR="Red"]D/AudioHardwareMot(  177): Changed Min CPU Frequency to 300000 KHz[/COLOR]
E/AudioHardwareMot(  177): Error:Cannot change smp affinity for irq 124 [COLOR="Red"](Permission denied)[/COLOR]
D/AudioHardwareMot(  177): Output 0x7e4738 standby complete

Is audio affecting CPU minimal frequency?

The following errors have been fixed and checked in MROM github, waiting for next build:

E/NetlinkEvent(  173): NetlinkEvent::FindParam(): Parameter 'MDM_SHUTDOWN' not found
D/HWC_HDMI_MOT(  174): wait_for_extdisp_service: try to connect to ExtDisp service IPC
E/HWC_HDMI_MOT(  174): connectToExtDispIpc: Client Failed, No IPC Server

The following item is displayed by /system/lib/hw/audio.primary.tegra.so:

D/AudioHardwareMot(  177): AudioStreamOutMot::standby called for 0x7e4738
[COLOR="Red"]D/AudioHardwareMot(  177): Changed Min CPU Frequency to 300000 KHz[/COLOR]
E/AudioHardwareMot(  177): Error:Cannot change smp affinity for irq 124 [COLOR="Red"](Permission denied)[/COLOR]
D/AudioHardwareMot(  177): Output 0x7e4738 standby complete

I need some testing on this one, this particular library appears to be a debug library, need some of you to run the following commands:

# mount -o rw,remount /system
# mv /system/lib/hw/audio.primary.tegra.so /system/lib/hw/audio.primary.tegra.so.old
# sync; sync; sync; reboot

I will try this later too...

 

[petersonldp]

We will have news soon? How can I contribute to help in bug sensor during call?

 

[chonkit]

hi guys..can you guys get to use google maps even google location service under location service settings there are checked? it show please enable a my location source in system settings..i am sorry if this question asked before

Sent from my A500 using xda app-developers app

 

[extreme70]

# mount -o rw,remount /system
# mv /system/lib/hw/audio.primary.tegra.so /system/lib/hw/audio.primary.tegra.so.old
# sync; sync; sync; reboot

Now cpu easily gets down to 216MHz but no sound at all.

 

[Manzing]

We will have news soon? How can I contribute to help in bug sensor during call?

Maybe you can try these build.prop tweaks ? They're used in someone's CM10.

# Disable blackscreen issue after a call
# Sensor FDP
ro.lge.proximity.delay=25
mot.proximity.delay=0
mot.proximity.distance=25

#Disable black incoming call screen
ro.telephony.call_ring.delay=200
ro.mot.eri.losalret.delay=0