• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP] CyanogenMod 7 | Android 2.3.5 | Last Version: CM7-Triumph-09182011 (discontinued)

Audio is not working? Do you mean music? Or like talking on the phone?

Audio not working generally means no sound period. With things like this, if you can get the audio drivers working for one thing, it works for all things. It's most likely a driver issue ticker's trying to resolve, and so that affects all audio on the system.

Think about if someone said the audio on a laptop wasn't working. Same principle.
 
Audio not working generally means no sound period. With things like this, if you can get the audio drivers working for one thing, it works for all things. It's most likely a driver issue ticker's trying to resolve, and so that affects all audio on the system.

Think about if someone said the audio on a laptop wasn't working. Same principle.

OH I was confused because he said it was able to get and make calls, but I guess no calls were actually made.

Thanks!
 
I just decided to register to say thanks to tickerguy and Isaac. I find myself checking on this thread multiple times daily to see the latest news, progress and problems regarding getting CM7 functional on the Triumph. Please continue the frequent updates, I love watching you guys figure things out and eventually getting them working. You two are doing some amazing things and I'm beyond eager to see a stable release.
 
im screwed. i got clockwork mod so i could flash this ROM. so i flashed it. when i went to reboot, it just stays stuck on the M logo. i cant even get into clockwork now. what do i do!?
 
im screwed. i got clockwork mod so i could flash this ROM. so i flashed it. when i went to reboot, it just stays stuck on the M logo. i cant even get into clockwork now. what do i do!?

Pull out the battery to turn the phone off. Then, power the phone on while holding the volume buttons to get back into clockwork mod- you can then restore your backup
 
Pull out the battery to turn the phone off. Then, power the phone on while holding the volume buttons to get back into clockwork mod- you can then restore your backup

i tried that already. it wont go into clockwork now.

Edit: its been sitting here on the motorola logo for about 15 to 20 minutes now. no CM7 dude scrolling across the screen. just in logo loop.
 
hold vol down and power and connect it to the computer and try to reinstall clockworkmod 4.0.0.9 from the first post. that should hopefully work.
 
Yeah there's no audio at all - I've been spending my time getting the phone interface working. You can "make" and "receive" calls but you can't talk since there's no audio.... that, of course, is now the priority as soon as I clean up the code changes that got me to data success - there are a few things to remove (that weren't necessary) and a couple of things to case for only the Triumph and otherwise reorganize, then it's on to the next challenge.

I write on the markets (Market-Ticker - MarketTicker Forums) and trade for a living so during the week there won't be nearly as much time put in on this as there was this weekend - it may be a few days before anything else of substance happens on my part. Of course Isaac is likely making progress too.
 
Ticker, Isaac
1de6294ef0eac5f1dcd78371fdd95f1f.jpg
 
Incidentally the audio problem is likely fixable with a kernel swap. That may be my first attempt there, as poking around in the device folder doesn't disclose anything obvious that's broken.

I don't know why Isaac decided on the kernel he used and I've emailed him but he hasn't gotten back to me... Before I dive into the audio code I want to understand where things are. If you want to play high-wire act you might try flashing one of the kernels that are here in this forum on top of the load I sent up last night - beware that doing that might blow you up entirely - no promises on this as I haven't tried it yet and odds of me having a lot of time to work on this during the week are not high.
 
Incidentally the audio problem is likely fixable with a kernel swap. That may be my first attempt there, as poking around in the device folder doesn't disclose anything obvious that's broken.

I don't know why Isaac decided on the kernel he used and I've emailed him but he hasn't gotten back to me... Before I dive into the audio code I want to understand where things are. If you want to play high-wire act you might try flashing one of the kernels that are here in this forum on top of the load I sent up last night - beware that doing that might blow you up entirely - no promises on this as I haven't tried it yet and odds of me having a lot of time to work on this during the week are not high.

Tried flashing the umph kernel last night with cm7. Got stuck at motorola logo.
 
NEW PROBLEM! when I'm not usein the phone an it stays locked. When I go to unlock it. It'll stay black n wont go back on till I do a battery pull.
 
This thread is starting to get... ugly. First off it's a CM7 thread,for the devs to post updates and the such,CM7 is in "ALPHA PREVIEW" far from a stable solid build.

so if you are flashing this build it's at your own RISK if you brick your chit,people that are flashing this build should only be flashing for "preview" purposes only!

i see a lot of people flashing then asking "why is it doing this?" why is it doing that?" which takes away very appreciated time from the devs to have to back track.. and answer questions that can easily be answered if you just read the whole thread.

it was stressed by the devs to only flash these "previews" if you KNOW what you are doing,so if you have flashed and a problem occurred you should KNOW how to back out.. repair and be back to where you were.

so please for the sake of everyone waiting patiently,keep the thread on course and beneficial to the devs work,and please don't flash if you don't fully understand what you are doing,you'll have a bricked phone before CM7 is even finished... and we wouldn't wan that... now would we.

so sit back... grab some snacks... and read the thread... and let these l337 devs get back to work...(this post is not intended for testers,as testers you know what your doing and understand all risks)

thanks -BG
 
At present bug reports aren't going to get any attention at all, since the present situation doesn't even have BASIC functionality (specifically, audio!)

I KNOW the rest of the code is unstable - in fact, I can crash it pretty much "on command" right now, but I made that build available for those who wanted to play, fully aware of the risks and the fact that it's really more of a curiosity piece at present than anything else.

Once we have a kernel that actually supports the drivers in the system (and at present I don't know anything - literally - about what Issac did there) I can move further forward (he may be doing so himself, and I wouldn't be surprised at all if he is - but remember, he's a college student and should be putting his FIRST block of attention there.)
 
Back
Top Bottom