Related
Given the recent explosion of nightly users, there is a need for a place to discuss them, and/or ask if other users are having similar issues as you...this is that place
DO NOT: Post to the bug tracker
DO NOT: Open another thread (Please)
DO NOT: Think of this as official forum support; this thread will be strictly user to user support. Don't expect CM-dev help.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Download: link
Google Apps addon:
Mirror: link
Mirror: linkChangelog: @cmsrc
Ah, and the daily flashing addiction begins again... like smack, but for geeks
Thanks guys! Downloading nightly #0 now
Sorry, I'm noob in CM story, what is nightlies? The intermediate version between stable versions? Why no bug repports? There is official forum where bugs are reported?
200mpx said:
Sorry, I'm noob in CM story, what is nightlies? The intermediate version between stable versions? Why no bug repports? There is official forum where bugs are reported?
Click to expand...
Click to collapse
Nightly builds are published test builds and unsupported. They always have been. They are experimental, volatile and too many issues come and go to be clogging up the bug tracker (intended for releases) with them. These are NOT primarily for users; they are to test the build process and for developers and device maintainers to evaluate. They are shared with users under these conditions, so you can use them or not, but issues with nightly builds are categorically rejected in the bug tracker. Hence; threads like this.
If I'm running the RC0 now, do I just flash it on top or do a clean install? And are the subsequent nightlies flashed on top or clean install every time?
Sent from my Incredible S using XDA App
The nightlies aren't for everyday use, and they can also not work at all (i.e bootloop). If you need to ask questions, chances are you should probably stick with RC0
Like attn said the nightlies are for devs and device maintainers, and more advanced users who are interested in the very, very latest code but they are totally unsupported releases, hence the no bug reports & questions angle. If a particualr nightly gives good performance increase or a new feature that is sought after, you will probably hear about people using a particular nightly n the forums, in which case it tends to be safe to flash it like a normal ROM (yet still totally unsupported)
Cardiiiii said:
If I'm running the RC0 now, do I just flash it on top or do a clean install? And are the subsequent nightlies flashed on top or clean install every time?
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
I thiink this one is safe to flash over RC0.
It should fix the flashlight issue.
attn1 said:
I thiink this one is safe to flash over RC0.
It should fix the flashlight issue.
Click to expand...
Click to collapse
Yes and yes, flashed straight over RC0 and torch works on high brightness without breaking screen backlight
One more small bug in rc0 theusing the defaultv videos app when I play a video the keyboard light turns off..
Sent from my HTC Incredible S using XDA Premium App
Had issue #1 in the nightly #1 (06/24) as well. On Nightly #2 (06/25) and I still have that issue and have noticed another one. Can someone confirm if they have it too?
1) Switching cameras (front to back and vice versa) freezes camera. Camera doesn't work until I reboot. Once rebooted, the camera shows the image from the camera you selected fine. Might be an issue with the code not properly initializing the camera from which data is to be taken or not properly releasing the camera being used first.
2) In the music player, the progress bar seems a bit off.. there is a disconnect. If someone can tell me how to take a good screenshot, I will
A (rather) lame way to show it in ASCII would be..
---------__O-------------
when it should be..
-----------O-------------
Can anyone confirm?
Yeah there is some camera bug in the latest nightly, worked fine the first time after flashing, but black screen and crashing since then.
Sent from my Incredible S using XDA App
Cardiiiii said:
Yeah there is some camera bug in the latest nightly, worked fine the first time after flashing, but black screen and crashing since then.
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
Bizarrely, I can still make the camera work if I launch it using WidgetLocker (my custom lockscreen replacement app) but I suffer the blackout bug if I try and launch it from the drawer or a homescreen shortcut.
FYI, Nightly #3 is out.. time to go grab it!
http://download.cyanogenmod.com/?device=vivo
John Anderton said:
FYI, Nightly #3 is out.. time to go grab it!
http://download.cyanogenmod.com/?device=vivo
Click to expand...
Click to collapse
Seems that I have battery drain with this version. Also my camera started to crash after some time
Sent from my Incredible S using Tapatalk
200mpx said:
Seems that I have battery drain with this version. Also my camera started to crash after some time
Sent from my Incredible S using Tapatalk
Click to expand...
Click to collapse
Nice to know it wasn't just me.
It lasted me 19 hours 50mins from 100% to 48%. 3 hours later, it went to 8% and needed a charge
Flashed RC1. Let's hope it does well Charging up the battery now
Camera works well.. No issues with it so far in a brief test.
Had noticed another issue in Nightly 3. Was playing music and the phone auto switched off for power save. A couple of mins later I hit vol up for vol increase and the player skipped to the next song
Wasn't able to reproduce it since.
John Anderton said:
Nice to know it wasn't just me.
It lasted me 19 hours 50mins from 100% to 48%. 3 hours later, it went to 8% and needed a charge
Flashed RC1. Let's hope it does well Charging up the battery now
Camera works well.. No issues with it so far in a brief test.
Had noticed another issue in Nightly 3. Was playing music and the phone auto switched off for power save. A couple of mins later I hit vol up for vol increase and the player skipped to the next song
Wasn't able to reproduce it since.
Click to expand...
Click to collapse
Haha, I had that strange pattern too, 18h and 55% left, and suddenly it started to discharge like a mofo, on Nightlies 4 now, will report if it's any better.
Flashing Nightlies is such an addiction, and the battery life seems stable and the decrease is steady, no drastic reduction.
Cardiiiii said:
Haha, I had that strange pattern too, 18h and 55% left, and suddenly it started to discharge like a mofo, on Nightlies 4 now, will report if it's any better.
Click to expand...
Click to collapse
Had the same issue with RC1 today Will get Nightly 5 now and check
Could you also play a music track and skip half way and check if the seek bar line is a misaligned? I've had that issue from Nightly 2 as well
John Anderton said:
Could you also play a music track and skip half way and check if the seek bar line is a misaligned? I've had that issue from Nightly 2 as well
Click to expand...
Click to collapse
Was that in the default player? I only ask cause Fede's Ubermusic got a fix in beta to fix this exact problem
l0st.prophet said:
Was that in the default player? I only ask cause Fede's Ubermusic got a fix in beta to fix this exact problem
Click to expand...
Click to collapse
The default player. The one which launches when I click "Music".
I've kinda settled on Nightly 5. 36 hours gone and I'm still at 68% charge Will let the run keep going until I have to charge it again
Ok firstly I'd like to say I just rooted my phone last week, this was my first time doing it. I decided to do it to get rid of various problems (I was led to believe rooting fixes everything). Some of them went away, some of them stayed, and new ones came up with the rooting.
I was coming a stock LG Optimus 2X P990 with Android 2.3.4 (had been updated because the phone was originally older 2.2.2 I think.. I'm not sure), and rooted to Nova HD Rom (ICS 4.0.4) using this thread : http://forum.xda-developers.com/show....php?t=1508492. Oh also, I'm using SPB Shell launcher.
Problem #1 : Signal interuption. This one is probably the worst problem I have. I rely on my phone a lot as I don't have a ground line I need it to catch all my calls. About 2-3times a day I'll check my phone and I'll have no network. Sometimes the signal bars are frozen, they don't flutuate as I move to different areas. Sometimes there's an X on the signal logo. Either way, where I go inside/outside.. my phone can't get network. At first I tried to activate/de-activate 2G, turning on/off airplane mode to somehow reset the damn thing, but it just won't pickup. Then I tried a reboot, after the reboot.. still stuck at no signal. Then I finnally found how to fix it.. a full power OFF, and back ON. That's right each time I peak at my phone and it seems to be doing this, I need to make a complete shut down to wake his ass off.
Problem #2 : Battery drain. Well after days of reading on the subject apparently rooting my G2X was gonna improve it's battery life. Result is : no difference. I've bought a bunch of apps to try and keep track on what's wrong (BetterBatteryStats, Battery Monitor Pro). Just this morning I unplug my fully charged phone at 7:00:AM, and by 1PM (6hours later) it was done. There was about 1½hours of awake time, and about 50mins of screen on (perhaps half of this was using my 3G internet with various apps), no SMS or Calls. Usually if the phone is kept sleeping it can last about 24hours, do you guys think this is normal battery drain?
Problem #3 : Phone Clock off? Last week I was woken up by my alarm in the morning to find out I was about 40minutes late. Only happened once so far. I checked to see if I had set my alarm incorrectly.. nope, then I saw my phone time.. It was was OFF by 40mins... WTF? I went in the options and everything was fine... "Automatic date & Time" checked. I unchecked/checked it, and it didn't fix it, I had to reboot the phone for the time to come back to normal. Now hopefully that was only a one time problem, only now I have to live with the stress every morning my phones time might be wrong and I'll be late for work.
Problem #4 : Seriously where the hell is my FM radio. I use to listen a lot of FM radio before I rooted my phone , this is a feature I enjoyed. After rooting the FM radio application was gone, I said what the hell I'll just get another app from google play. NOPE, not a single FM radio app (that works). I tried a bunch of stuff, read on the forums and searched google for like 3hours and couldn't believe how much work I had put into such a simple thing.. this is so infuriating. The next day I kept looking but was never able to get anything working.. Oh and every where I look people say "lol why use FM radio when you can stream 1gazillion radio with given apps or whatnot". DAMMMMMMNN CAUSE MAYBE I DON'T HAVE INFINITE DATA PLAN? (In fact I have only 500megs/month). Seriously I'm so mad about this.
Problem #5 : Can't copy MKV files?! . I swear to got now that I rooted my phone each time I try to do something, something ****S UP. I just wanted to plug in my phone and copy some episodes of a serie I watch. Each time I tried copying the files : BAM "Windows Explorer has stopped working". So after another 2hours or so of trials and errors I figured the damn thing out . If I try to copy anything, it works. If I try to copy a *.MKV file, explorer crash. A solution I found is renaming my files to *.****YOU and then copy it and rename it back to MKV after it's done copying. Then I wondered, what if I rename a txt file to mkv, will it crash when being copied? Nope won't crash. So it's not just the extension? But why does it work if I remove the mkv extension.. oh good god how the hell am I supposed to understand anything.
Problem #6 : Can't play that MKV file?. Hey I finnally copied my file, the next day at work during my break I open my phone to watch it and.... well I realised there wasn't any video player included in my ROM, so luckly this time I found apps on the market that could play it. I used MX Player. Oh alright time to watch it? NOPE The video is all laggy and skipping frames like hell. Also audio is off and about each 10sec it mutes as if it was re-syncing the sound. Later the next evening I wasted another couple hours figuring this one out. What comes out often : they say use Dice Player instend! LOL Funny! The damn app won't even open my file!.
Playing with my phone I opened an APP I've pushased : System tuner pro. Looking at the CPU stats I noticed the first CPU was at 1.01Ghz, and the second one was at 216mhz? What the hell? I thought isn't that suposed to be 2x1ghz dual core?. So I cranked up the thing up to 1.01Ghz just like the other CPU, opened MX Player and already my video was almost watchable (a definitive improvement). I went back in System tuner pro, and overclocked the damn thing (even tough I had no idea if it was safe to do so) to 1.4ghz on both cores. Another significant improvement, this time when set this way I could watch my video! And the app onlyl reports a 5Celcius increase so I guess it's fine.
My only problem/question about that is why does each time I reboot my phone does the damn thing turns back to 216mhz? In fact why was it set to 216mhz in the first place? Considering all the problems I have and that I reboot my phone about 10times a day, I can't just go in system tuner the re-set my CPU settings each time?
Hopefully you guys can help me.. I'm exhausted I''ve been searching this forum and the web for the last couple days, I have like 1000tabs open in chrome. Btw this forum is a goldmine for information but damn it's a lot of reading.
Thanks in advance for your help
First, I'd like to say that I admire your keenness to detail in writing all of your issues down. Thing is, most of the problems you have are mainly because you flashed a modified ICS ROM. ICS roms by themselves are in beta stage, meaning there are some things that people compromise in flashing them (such as the missing FM radio), and you flashed a modified one, which might be the reason for certain power saving features such as your 2nd core down stepping to 216MHz.
Thing is, most of those were discussed in the NOVA ICS thread.
I would recommend flashing the more stable ROMs. Temasek's CM7, DjangoManouche by Carburano, Nostalgia by Topogigi (Froyo ROM) are the ones that pop-up in mind.
For a panic button, you can do a smartflash and it will restore all partitions to stock LG (wiping all user data of course).
Anyway, read the threads carefully. The opening posts and the last 5 pages at least. In order to get a feel of user experiences with the ROM.
Goodluck and happy flashing!
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
I also noticed that you mentioned you have a G2X? But you also mention having a P990. If you're on a G2X, you have a different forum section my friend. This forum section is specifically for the O2X.
Flashing an O2X ROM on a G2X may result in softbricks.
(Please disregard my advise about ROM choices if you're have an LG P999 G2X, those are all intended for the LG P990 O2X.)
yea my mistake when I typed G2x.. I meant O2X.
Thanks for the advice.
If I change my ROM will it wype all my user data again? (sorry im a newb at this)
The ROM itself might not. But I highly recommend you wipe your device since you're moving from 1 version of android (ICS) to another (Froyo or GB).
I'd recommend you CM7 (not CM9) based ROMs but since you need the FM radio, they have none AFAIK.. but you can try stock based ROMs that are still in active developments by the dev. Usually they worked just fine and will fix most of your problems.. again, don't use CM9 based..
Now for the network that is constantly disconnecting in background, this bug is actually introduced (at least for me) after the GB update (i assumed because of the changes LG has made to the baseband). There's no surefire fix for this problem.. try different combinations of basebands and RILs.. stick to whatever works for you
For battery, if you're in constant mobile network, 24 hours standby time is incredible IMO.. our battery is just too low in capacity to make it last any longer than that.. my only advice is minimize the number of apps in your device, because some of them always stay in RAM doing god knows what..
Good luck
Sent from my Optimus 2X using XDA
Patbach said:
yea my mistake when I typed G2x.. I meant O2X.
Thanks for the advice.
If I change my ROM will it wype all my user data again? (sorry im a newb at this)
Click to expand...
Click to collapse
Yes it will wipe them.. for baseband changes too.. so if you have apps that you'd like to preserve, back them up before flashing anything.. Titanium backup will do the trick, but some instability issues might appear if you choose to just backup and then restore everything up.. so choose all your important apps and leave the rest.. this way if something is wrong with the rom after restore, you can at least pinpoint which app is causing it
Sent from my Optimus 2X using XDA
amateru said:
I'd recommend you CM7 (not CM9) based ROMs but since you need the FM radio, they have none AFAIK.. but you can try stock based ROMs that are still in active developments by the dev. Usually they worked just fine and will fix most of your problems.. again, don't use CM9 based..
Now for the network that is constantly disconnecting in background, this bug is actually introduced (at least for me) after the GB update (i assumed because of the changes LG has made to the baseband). There's no surefire fix for this problem.. try different combinations of basebands and RILs.. stick to whatever works for you
For battery, if you're in constant mobile network, 24 hours standby time is incredible IMO.. our battery is just too low in capacity to make it last any longer than that.. my only advice is minimize the number of apps in your device, because some of them always stay in RAM doing god knows what..
Good luck
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
CM7 has a working FM radio since late last year.
Just an FYI.
----------
Sent from my Optimus 2X
salisbury_steak said:
CM7 has a working FM radio since late last year.
Just an FYI.
Oh great.. that means you wouldn't mind using CM7.. i just don't bother checking for working FM radio app since long ago
why not try Temasek's kang build? I believe it is still the best stability wise..
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
is there ICS Roms which are CM7 Based? I figure might as well have the latest version of android...
Patbach said:
is there ICS Roms which are CM7 Based? I figure might as well have the latest version of android...
Click to expand...
Click to collapse
CM 7 is Gingerbread
CM 9 is ICS
The numbers indicate Android's different iterations, so no, you can't
Sent from my Optimus 2X using XDA
CM 7 is a fantastic phone, but it has 2 big problems:
-huge battery drain, specially when you enable Wifi!
-sporadic BSODs...specially when the phone is on charging...
Sadly i had to remove CM7 because i use a lot Wifi...i flashed Topogigi's nostalgia now..good rom
Inviato dal mio LG-P990 con Tapatalk 2
markop90 said:
CM 7 is a fantastic phone, but it has 2 big problems:
-huge battery drain, specially when you enable Wifi!
-sporadic BSODs...specially when the phone is on charging...
Sadly i had to remove CM7 because i use a lot Wifi...i flashed Topogigi's nostalgia now..good rom
Inviato dal mio LG-P990 con Tapatalk 2
Click to expand...
Click to collapse
Which both are solved to about 95% by using etana kernel.
In short CM7 is the most feature complete ROM without sacrificing performance on our phones.
Skickat från min Optimus 2X via Tapatalk 2
Just to give an update I have changed my ROM to a CM7 based rom like u guys said. Temasek's kang build
Problem 1. Signal interuption : problem is definitly solved.
Problem 2. Battery drain : definite improvement, battery now last at least twice longer
Problem #3 : Phone Clock off? : Didn't get the problem again, so solved.
Problem #4 : Seriously where the hell is my FM radio. : Well I got an FM radio app, but I can't make it work. It doesn't pick up the stations..
Problem #5 : Can't copy MKV files?! : Well this is solved yes and no. If I manage to make my computer detect the damn phone, I can copy whatever I want to. Thing is for some reason I can't seem to be able to plug my phone into Mass Storage mode anymore. It worked a couple of times and all of sudden even tough I didn't change any drivers, my computer just doesn't see the phone anymore. I get a "USB Composite Device" with a yellow "!" mark in my device manager.
I tried a bunch of stuff in the options, rebooting the phone and/or computer, nothing worked. I decided to try reinstalling the rom, and boom right after I pluged it in, the USB Mass storage mode worked. Once again after a couple of times it started doing the same thing (yellow "!" mark in my device manager), and no new drive being detected. This time I'm completly clueless on what's going on, and I have no idea what I can do about it.
I'm currently copying files using Samba Filesharing over Wi-Fi, but sometimes I'd prefer using my USB cable, and I just can't...
New problem!!! : I had my phone at work yesterday and pluged in my headphones to listen to music, start my music and the sound was playing in both my heatphone and phone speakers. I tried unplugging/replugging the headphone, now the sound only worked on the phone speaker. Looked up every phone option possible regarding sound or headphones.. couldn't find nothing. I did a reboot on the device, and bam fixed everything. Couple hours later I re-open my phone for music, same problem occured. Had to reboot the device for the sound to be back in the headphones.
Most problems are fixed, I Guess I'm satisfied, but damn can't everything just work...
JuiceDefender Premium will make it that your device loses 1% every 10 hours if screen is off.
Stock 20Q from LG is free of bugs and full of functions.
Might be a stupid advice,
but you do know that you need your headphones plugged in for FM radio? (they are the actual antenna)
In the settings you can also set your region (e.g. North America or Europe), since the frequencies differ a bit (e.g. Europe uses 0.1MHz 'jumps' and some regions 0.2MHz).
Zorkman said:
Might be a stupid advice,
but you do know that you need your headphones plugged in for FM radio? (they are the actual antenna)
In the settings you can also set your region (e.g. North America or Europe), since the frequencies differ a bit (e.g. Europe uses 0.1MHz 'jumps' and some regions 0.2MHz).
Click to expand...
Click to collapse
yea I know all of that don't worry.
The FM radio app is pretty buggy, today I made it worked. Once the app was started with the station selected, I hit the home button then I pulled down the tray and click on the FM app from there. All of sudden I started hearing sound.. it had worked.
Turns out the app is also the source of what is messing my headphones up. When I close and re-open the app, the sound will come out from the phone speaker, and that messes up every sound from the phone then on.
Patbach said:
yea I know all of that don't worry.
The FM radio app is pretty buggy, today I made it worked. Once the app was started with the station selected, I hit the home button then I pulled down the tray and click on the FM app from there. All of sudden I started hearing sound.. it had worked.
Turns out the app is also the source of what is messing my headphones up. When I close and re-open the app, the sound will come out from the phone speaker, and that messes up every sound from the phone then on.
Click to expand...
Click to collapse
That FM radio thing is a bug that I haven't heard of actually. When you have the opportunity (or maybe on the next build #94, I'd suggest a full wipe then reflash).
Hi community! Thanks to all the developers who make this project fly!!!
I fear I have a resistant Touchpad that does not want to output any audio in Android CM9 or CM10.
It has sound in WebOs so I don't think it is a hardware problem.
I've tried CM9 (123012) and heard some soundtap noise after a reflashed gapps, but then the sound went away, I think
when the wifi started (?).
CM9 was extremely slow and the system would be very laggy and freeze when I tried to change the volume by using
the volume buttons. Many times I'd have to do a power+home button shutdown.
CM10 (121612) on the other hand was very responsive, quick and smooth and there was no lag or freeze on pressing the
volume button- but still no audio.
I used ACMEuninstaller to remove CM9 and used:
ACMEInstaller3, CWM6, moot 0.35 for both installs, flashed cache and dalvik, and fixed permissions.
Is there anything else I can try?
Thanks!
Briefly hold the power button to bring up the menu and make sure it isn't set to mute should be the bottom Line with a line under the speaker on the right .
I brought up the screen, and it shows the speaker icon on the right side with the line under it.
It looks like volume is on and not mute, but still no sound.
Thanks for the suggestion.
Thinking it was something to do with WebOS 3.05, I used the thread in this forum to bring back the Touchpad to WebOS 3.00, and
then 3.04 and still the same issue appears in Android.
I'm now thinking that this 32GB Touchpad may not have the same hardware for the audio codecs to work in android?
(Actually, I'm clueless and just guessing, and, hope I'm wrong.) :fingers-crossed:
Well it was worth a try, it shouldn't be anything to do with webos (I'm on 3.05) . Do the headphones work as it has been suggested that the socket my be causing problems .
Otherwise I'm also clueless .
Good to know that it isn't WebOS 3.05 related.
I tried the headphones and no sound either. So I rebooted with the headphones plugged in and no sound.
One other thing I can't figure out is why would CM10 be more stable than CM9 on this device, when the consensus seems to be
that CM9 is much more stable?
No idea , I'm using Oat's at the moment but also have a backup of jcsullins so that I can test out things on both and have stopped using CM9 completely .
I take that you get no sounds when typing and that the volume cursor moves when you use the rocker switch .
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
Try going to settings > sound > volumes, and see if the settings are correct.
If I think of something else, I'll post it.
I have the exact same problem. Tried all the resolutions mentioned above, no result. Wiped out android and used WebOS doctor for full recovery, then installed the latest nightly (24 Nov 2013) still no sound. Somewhere it was mentioned that it is due to a firmware (A6) problem but I don't know how to downgrade or upgrade the firmware.
Any help is appreciated.
Hp Touchpad on CM9 and CM10
I have also tried for nth times but my touchpad 16GB has no audio output (including 3.5mm jack) on CM9 or CM10......... somebody help
I have the same problem, but can install older CM9 builds and have sound. 6/12/2012 nightly is one that has sound for me.
My problem ended up being the head phone jack. I rapidly inserted/removed the headphones several time and my speakers came back to life.
Still very odd that I had audio in WebOS and older cm9 builds the whole time, but I'll refuse the question that logic and am thankful that I was able to get it working.
north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.
CJMax said:
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.
Click to expand...
Click to collapse
Have you guys considered submitting alogcat to the developers? It might be more productive than just stating that you have a problem. Submitting a logcat might help to get the problem fixed. I remember hearing issues with 64GB Touchpads not playing sound with CM9 Roms. Flashing the audio libs helped a few of those users.
I created a log on pastebin: MyfU2DDU (not allowed to post full urls yet). Who should I send it to? At the beginning of the log, sound was still working, then (I think line ~1280) sound stopped. Afterwards, I'm getting out of memory errors. Running CM10, same problem in CM9 and CM10.1.
Had the same prob and now back on cm-9-20130512 and disabled system sounds. It works now.
As the subject line says, I have tried flashing different builds of CM9, and CM10, AOKP, and the only build that works are the nightlies for CM10.1. What happens is, at some point randomly during use, or more commonly when the screen is off, sound will stop functioning and NO audio will come out of the touchpad. On top of this there is also massive slowdown in every single app. I have tried increasing minimum clock speed, flashing new Kernels, Removing android completely and reinstalling from WebOs, Changing my recovery app, upgrading Moboot, and doing a complete format of system, data, etc before flashing. NOTHING works. Any suggestions?
I'm having the exact same problem. I've tried both CM9 and CM10 along with webos 3.0.0 and 3.0.5. I've also done a full wipe and run webos doctor to start from a completely blank slate. My tablet did suffer from the scratchy sound problem under webos 3.0.5. I haven't tried it yet under 3.0.0.
If I reboot, it works for a little while. I'll get some HW/SW info and post it shortly.
[edit]
The lag only happens when the audio stops working. When audio works, there is no lag and it runs like a dream.
IN WEBOS
Version HP webOS 3.0.0
Product number FB359UA#ABA
Model HSTNH-129C
Android version 4.1.2
Kernel verion 2.6.35 palm tenderloin [email protected] #1 thu apr 18
CPU ARMv7 Processor rev 2 (v7)
Cyanogenmod 10-20130418-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM
Build date Thu Apr 1800 04 59 CDT 2013
Build number cm_tenderloin-userdebug-4.1.2 jzo54k eng.jc.20130418.000410 test-keys
MOBOOT 0.3.5
I used CMinstaller3 todo all my CM installs. I couldn't find CMinstaller2. I don't know if that has any bearing on this issue.
I hope this helps. I love this device but I've been fighting with this for almost a month and i'm running out of ideas.
Thanks!
I've since found CMinstaller2 and loaded CM9. Same issue.
Another update: Some may be aware of the scratchy audio issue on the touchpad in webos. I experienced this yesterday under CM9. Since very few people have this problem, I wonder if it is a hardware related issue and only a few touchpads suffer from this.
augoosto said:
As the subject line says, I have tried flashing different builds of CM9, and CM10, AOKP, and the only build that works are the nightlies for CM10.1. What happens is, at some point randomly during use, or more commonly when the screen is off, sound will stop functioning and NO audio will come out of the touchpad. On top of this there is also massive slowdown in every single app. I have tried increasing minimum clock speed, flashing new Kernels, Removing android completely and reinstalling from WebOs, Changing my recovery app, upgrading Moboot, and doing a complete format of system, data, etc before flashing. NOTHING works. Any suggestions?
Click to expand...
Click to collapse
Try the latest CM9 nightly as mentioned here:
http://forum.xda-developers.com/showpost.php?p=43602041&postcount=2740
Issue
As of today I have discovered that Turning on and connecting to Wi-Fi is the source of the problem. Flashed that new build JC and it worked great until I turned Wi-Fi on, at which point the same issues occurred. Why this happens on all builds except CM 10.1 I am still not sure.
augoosto said:
As of today I have discovered that Turning on and connecting to Wi-Fi is the source of the problem. Flashed that new build JC and it worked great until I turned Wi-Fi on, at which point the same issues occurred. Why this happens on all builds except CM 10.1 I am still not sure.
Click to expand...
Click to collapse
Well, that's certainly strange.
Could you try with latest CM9 again and grab output of 'dmesg' after you turn on wifi and get the failed audio?
jcsullins said:
Well, that's certainly strange.
Could you try with latest CM9 again and grab output of 'dmesg' after you turn on wifi and get the failed audio?
Click to expand...
Click to collapse
Certainly can
Issue
dmesg output attached.
I also have flashed 9-20130714-Nightly and I've noticed an improvement in the audio stoppage. I tried to repeat the problem that augoosto has seen by turning the wifi on and off. I was not able to repeat it. I will keep trying to stimulate the failure. I seem to get a lag only when the audio has stopped, and only when the app/program is calling to make a sound. if I mute the app and not the tablet sound (candy crush is a good one to try this), I get normal non-laggy performance.
Overall things are much better with this build. I probably only have to reboot a few times a day. Previously, I had to reboot every time I wanted to do something that involved sound.
Another thought. There may be some correlation to using the power switch. I just now let it fall asleep on its own, and use the home button to wake it up. I'll do more to see if I can find more correlation.
Thanks!
augoosto,
I don't know much about how sound in Android works, but I took a look at your dmesg output anyway. This line stood out to me:
Code:
[ 162.777248] asoc: can't open platform msm-audio
I would assume that this line occurs sometime after CM boots, because I doubt that your TP is taking almost 3 minutes to boot.
Next time that the audio drops out, try running cat /proc/asound/cards and see if anything is listed. My TP lists a single card called msm-audio in CM 10.1.
Sent from my SAMSUNG-SGH-I747
I'm a newbie to Android on my Touchpad and I am also experiencing this intermittent dropout of the audio. I have not been able to narrow down the loss of audio to running any particular application, or sequence of events. In short, audio will be working fine, then, the next thing I know, silence.
For better or worse, I'm running a jcsullins preview build: 10-20130418-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM . Everything else has been working fine except for this annoying audio problem. BTW, I first noticed the problem shortly after my initial install and tried to view a YouTube video. The video displayed one frame at a time, obviously very sluggish, and no audio. After rebooting, the same YouTube video played fine, and other sounds were working, too. I didn't think anything of it until I noticed the audio disappearing at random times.
If it helps, I've attached my dmesg and logcat listings captured today as soon as I realized that my sound disappeared. The "Out of memory" errors listed in logcat are certainly suspicious, but could just be a symptom rather than the problem.
-Don
sound card still listed
My sound card is still listed after using that cat line, but I am still no closer to fixing this problem, which I am now experiencing in cm 10.1 as well as of the last 10 builds.
Dmesg
jcsullins said:
Well, that's certainly strange.
Could you try with latest CM9 again and grab output of 'dmesg' after you turn on wifi and get the failed audio?
Click to expand...
Click to collapse
See anything out of the ordinary in my dmesg output JC?
Partial fix
I have found what seems to be the cause of the issue. It appears that the issue is caused by bad blocks in the NAND memory of the device. Last night I did a full format, and before re flashing, I partitioned the SD card in CWM, causing the installation to be written to a different section of the devices flash memory. The audio issues almost completely went away in CM9, now I just need to find a way to identify all of the bad blocks and prevent them from being written to. Hope this is helpful to other users suffering this issue.
augoosto said:
I have found what seems to be the cause of the issue. It appears that the issue is caused by bad blocks in the NAND memory of the device. Last night I did a full format, and before re flashing, I partitioned the SD card in CWM, causing the installation to be written to a different section of the devices flash memory. The audio issues almost completely went away in CM9, now I just need to find a way to identify all of the bad blocks and prevent them from being written to. Hope this is helpful to other users suffering this issue.
Click to expand...
Click to collapse
This is great news as mine has become almost unusable. I'm not 100% sure how to partition the SD card in cwm but I'll take a stab at it and let you know if it fixes mine as well.
augoosto said:
My sound card is still listed after using that cat line, but I am still no closer to fixing this problem, which I am now experiencing in cm 10.1 as well as of the last 10 builds.
Click to expand...
Click to collapse
Try doctor yout TP before installing
augoosto said:
I have found what seems to be the cause of the issue. It appears that the issue is caused by bad blocks in the NAND memory of the device. Last night I did a full format, and before re flashing, I partitioned the SD card in CWM, causing the installation to be written to a different section of the devices flash memory. The audio issues almost completely went away in CM9, now I just need to find a way to identify all of the bad blocks and prevent them from being written to. Hope this is helpful to other users suffering this issue.
Click to expand...
Click to collapse
can you please give us the steps for doing this,, by doing this will we loose webos as well ? i have the touch pad with cm9 and have tried different builds but sound has not worked consistenly. in web os it works well.
with these particular touchpads we have, is it better consider some other OS !!
Any progress with this audio issue? It's the only problem I ever have with my touchpad. Incidentally, it never shows up on my daughter's, which has cm7 installed.
Same thing here. Sounds work fine at the beginning, then lose it (after the screen is off for a couple of seconds).
It was working fine at some point using CM9, but since I tried CM10.2, CM11 and now evervolv 4.4.2... I still have that painful issue. Everything else work fine, except audio. It also prevent youtube from playing videos. Videos work fine while the sound is working, but when we lose the sound, youtube videos doesn't play anymore.
I've been crawling the web since last December on this subject, found a couple of thread like this one with the issue but nobody has found how to fix it (or I didn't find it yet!)
If anyone has an idea... please let us know, thanks!
ps.
Here's a dmesg sample output in attachment (and on pastebin.com/FzsXs7fS )
Suspicious lines:
<3>[ 216.450042] APR: Unable to open handle
<3>[ 216.450073] q6asm_audio_client_alloc Registration with APR failed
<3>[ 216.450103] q6asm_audio_client_free: APR Common Port Already Closed
<3>[ 216.450164] asoc: can't open platform msm-dsp-audio.0
I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night
The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.
Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.
goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.
Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.
EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.
Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.
Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?
Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.
I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4