Thread Deleted

CyanogenMod 7.2.0 (Android 2.3.7)(2012.05.26)

OP laidaxin

7th March 2012, 01:58 AM   |  #21  
rignfool's Avatar
Senior Member
Thanks Meter: 615
 
2,102 posts
Join Date:Joined: Dec 2010
Anyone else have problems with the screen coming back on when you take it down from your ear?

I think the proximity sensor isn't waking the screen up?

Sent from my Filpside using Tapatalk
8th March 2012, 05:27 AM   |  #22  
rignfool's Avatar
Senior Member
Thanks Meter: 615
 
2,102 posts
Join Date:Joined: Dec 2010
Ok... to you guys with more experience than me....

I was reading my build.prop file and noticed that umts(3G) requires a libril-moto-umts-1.so

Wondering if maybe we have a ****ty copy of it in our /system/lib/ directory and that's what is causing the reboots?

So maybe if we pull the one out of the defy tree we can fix it that way?

If not... anyone know where I could find instructions on how to fix it?

Ditto on the sensors since they still ain't working 100%

Sent from my Filpside using Tapatalk
Last edited by rignfool; 8th March 2012 at 05:32 AM.
9th March 2012, 10:28 AM   |  #23  
bakageta's Avatar
Senior Member
Thanks Meter: 85
 
231 posts
Join Date:Joined: Jan 2010
More
So, I realized that the bootmenu and cwm recovery using in this CM7 build were newer than the one in the other thread, I extracted them and replaced my recovery with this one and was able to nandroid restore, so I wiped and installed CM7.

My initial thoughts:
Haptic feedback settings for hardware buttons don't take effect until after a reboot. I initially thought they were broken altogether, but rebooting put them to the values I had set. Stock levels are entirely too low, IMO, it's really not noticeable.

I'm having problems with Better Terminal Emulator Pro and the hardware keyboard. In text messaging and such, the function key layer works as expected, but in BTEP function does nothing, making it impossible to get to several key characters. In the stock rom, there were no problems with BTEP, and I've tried both a fresh reinstall from the market as well as restoring my previous working copy from Titanium Backup.

On the first couple of boots, the wifi hotspot ongoing status wouldn't go away, then it randomly stopped showing up... *shrugs*

The rotation sensor seems overly sensitive, it will flip the screen at the strangest moments on me.

Was the stock CM7 code changed for the lockscreen? I seem to recall the option to unlock on trackball in CM7 on my dream, but that's been replaced by unlock with menu here. Any chance to get both included? I dislike using the capacitive keys for unlocking, having the hardward button to unlock has always been my preference.

I have yet to test GPS, something I use regularly, but navigation didn't immediately crash, so that's a good sign. I didn't want to take a trip outside to see if it'd sync up, but I'll report back on that after my next trip out.
Last edited by bakageta; 9th March 2012 at 10:31 AM.
9th March 2012, 11:17 PM   |  #24  
rignfool's Avatar
Senior Member
Thanks Meter: 615
 
2,102 posts
Join Date:Joined: Dec 2010
I have issues with GPS... it doesn't fix fast enough to be able to use navigation...

However... I installed a stable release on my buddy's atrix and the results are the same as on my flipside...

I assumed it was a cyanogenmod issue... and if you tell me it worked fine on your dream... then I will assume its a cyanogen+motorola issue

Sent from my Filpside using Tapatalk
10th March 2012, 12:07 AM   |  #25  
Member
Flag Gem
Thanks Meter: 15
 
51 posts
Join Date:Joined: Feb 2011
Donate to Me
Question
Has anyone heard from laidaxin on the estimated arrival of the next release? I've been sitting here chewing my nails down to the nub wondering what's going on... just curious about an update on progress
10th March 2012, 01:59 AM   |  #26  
bakageta's Avatar
Senior Member
Thanks Meter: 85
 
231 posts
Join Date:Joined: Jan 2010
More
Other than the dream being too slow of a phone, navigation worked properly, the gps signal sync'd up pretty reasonably and such. CM7 on my friend's Nexus had no navigation issues either, so it's not a CM-specific bug.
10th March 2012, 03:38 AM   |  #27  
rignfool's Avatar
Senior Member
Thanks Meter: 615
 
2,102 posts
Join Date:Joined: Dec 2010
As far as I can tell... via PM... he's almost given up... he was talking about uploading his source so others could help...

I'm not sure if he's stumped or what... I'm waiting to see it... though I don't know how much help I'll be

And... don't forget... the first rule of CM... don't ask for ETAs
Sent from my Filpside using Tapatalk
10th March 2012, 02:13 PM   |  #28  
Member
Flag Gem
Thanks Meter: 15
 
51 posts
Join Date:Joined: Feb 2011
Donate to Me
Wasn't asking for an eta lol just the progress
10th March 2012, 03:35 PM   |  #29  
bakageta's Avatar
Senior Member
Thanks Meter: 85
 
231 posts
Join Date:Joined: Jan 2010
More
Source code would be wonderful, porting CM isn't a small task and I'm sure that other members of the community would be able to contribute as well, especially now that it's down to just little fixes.
10th March 2012, 05:31 PM   |  #30  
rignfool's Avatar
Senior Member
Thanks Meter: 615
 
2,102 posts
Join Date:Joined: Dec 2010
PM sent to laidaxin and WinSuk

Sent from my Filpside using Tapatalk

Subscribe to Thread

Tags
cyanogen, rom
Previous Thread Next Thread
Thread Tools
Display Modes