[CM7] Nightlys - No Bug Reports, No Other threads, No Official support - HTC Incredible S

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: link​Changelog: @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

Related

[Q] Where is RC1-7.0.0-11.02.18 CM7 for Milestone?

I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF

[Q][ICS 4.0.4 / MTD] AOKP for P1000/L/N - Camera App

Hello!
I have been using the ICS 4.0.4 [MTD] AOKP for P1000 ROM for sometime now and am on the latest build B#36 (as on 17/05). The Camera App with that build is not stable and does crash randomly. This is mentioned in the Bugs List. However, in the following post --
http://forum.xda-developers.com/showpost.php?p=25102133&postcount=876
I have installed the 'CameraUpdates.zip' and have not faced any issues with the Camera App after that. Further, the GUI is also different from the Camera App present in the B#36.
My question is why not update or include the Camera App listed in the link above with the next build of this ROM?
(Unfortunately, I cant post in the Dev Thread due to the number of posts.. Could someone look into this and pass it on to the Dev Thread -- http://forum.xda-developers.com/showthread.php?t=1523174)
Thanks.
Yes I mentioned that and Stimpz0r will fix it in the next build, it was included in the previous build. Thanks
Sent from my GT-P1000 using XDA
Couple things:
I would've posted this in the dev thread, but, you know the rules about new accounts :/
Just one day since coming from build 35 to 37, have noticed significant power drain, still quantifying it, will keep my eye on it, but initially lost 30% over the course of 5 hours in idle mode, constant drain, 3g off, wifi off when screen not active, BT off, GPS off.
Also, the whole app rotation on home screen thing comes up when trying to move/delete/uninstall, even with allow 180° rotation turned on. After activating rotation, one has to restart before it takes affect.
More importantly, the main camera still acts up quite a bit for me. Quite a few fc's, which is to be expected, i guess. Strangely if i turn off the shutter sound in settings, it crashes, every time. Like, always and without fail. Panorama and video, front camera all working well, just the main camera. Tested with stock camera, instagram, vignette, and procapture, same effect, fc's with shutter sound off. I did a factory reset/wipe and went through settings systematically, so I'm reasonably sure this is the problem. Wonder if anyone else has encountered this, or has a work around. I hate that shutter noise.
Don't know if it's intentional but when i try to turn off menu button in top right corner through menu location in rom control settings, the button isn't removed, and the nav bar back/home/recents/menu buttons become larger and more spaced out instead. Not a problem, just weird. Resetting nav bar options and rebooting reverts it back to smaller keys again.
Finally i just want to give some recognition to devs like stimpz0r, humberos, cdesai, dizgustipated, alroger, chainfire, and sbrady, who seem to consistently add to and improve these builds tirelessly, as well as take the time to answer questions and field comments from noobs and more experienced members alike with a degree of patience and humour. And of course thanks to all the aokp and cyanogenmod mates, my sgt works so far better than when i bought it. The teamwork and support is amazing to see. It's impressive, what all of you guys have been able to do. I thought we were all well and truly screwed by Samsung, i couldn't believe it when they left all of us early adopters out in the cold, but you have really come through for all of us. This is a seriously nice piece of work.
FF
Sent from my GT-P1000 using XDA
By batt hasn't been great, but yesterday I downloaded Battery Calibrator by Damo Software and did calibration according to its instruction and seems to improve.
Shutter sound is a known bug, I thunk mentioned in the known bugs, did you read it?
Sent from my GT-P1000 using XDA
Now that you mention the camera thing, yeah. But I'm a johnny come lately to aokp. It takes a serious time investment to read through all the posts with the issues scattered throughout, it's easy to miss one. And while there is a lot of info in the op and changelog posts, particularly about mtd/non-mtd (which is great) these common problems seem to be under-addressed, so i thought to just gather them together here for someone to find. I know it must be a pain to update the changelog posts thoroughly after every new build.
Cheers
ff
Sent from my GT-P1000 using XDA
p1000
Sir, can you please help me how i do upgrading my tab p1000 to ics 4.0
the existing ver 2.3.3 , and i hope if i get for ics or any upgrading ver above 2.3.3
[email protected]
if you have time
subroma said:
Sir, can you please help me how i do upgrading my tab p1000 to ics 4.0
the existing ver 2.3.3 , and i hope if i get for ics or any upgrading ver above 2.3.3
[email protected]
if you have time
Click to expand...
Click to collapse
Assuming yours is GT-P1000
Read this
http://forum.xda-developers.com/showthread.php?p=27500461
Sent from my GT-P1000 using xda app-developers app
If it might help you
go to this forum http://forum.xda-developers.com/showthread.php?p=23097605

Anyone downloaded and used cm-10.1.0-RC5-quincytmo.zip yet?

Curious about experiences. Right now I'm on the M3 Experimental.
It's really stable.. By far the most stable cm10.1 build I've ever used. Only thing Is the instagram videos come out fuzzed out and you can't see anything. That Sux
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Only one bluescreen in 24 hours so far. Using its boot image in the newest Slimbean, hope it continues to hold up.
I was just coming to post this exact same question. I had to go back to M3 because there were too many bugs in the subsequent nightlies.
But I think i'll try RC-5 and see what it's about.
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
jdekoven said:
I did flash it. Since that time I've had some issued with bluetooth where I've had to reboot the phone to get it to work. Also some "blue screen" and random reboots. Someone suggested I should probably reflash and clear everything (data, cashe, dalvik etc...)
Click to expand...
Click to collapse
The bluetooth issue seems inherent in any of the 4.2.2 roms. I've done clean installs , wiped with Darkside, etc. It doesn't really seem to matter.
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Installed 10.1.0 using the updater and had lots of problems. Audio bad, Bluetooth not working. Installed clean with a factory reset and it is very stable. Only issue is still some camera apps (Google drive scan, latest evernote) require setting Disable HW Overlays. But other than that, seems good
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
Lots of random reboots followed by a blue screen, I have noticed that it happens a lot during or after viewing a video and certain games, it even has happened while texting. No where near stable, battery life is horrible and like I said the reboots are random but often.
I'm using the CM 10.1 stable release as the boot image for PAC-Man rom. So far, no blue screens, reboots or anything. I've messed around with it, adding the Google edition camera and other goodies I found in i717 forum. Flashed in the S-4 launcher and everything is still holding together. Battery life is okay, considering I'm using livewall paper and wifi also. 60% remaining after four hours.
I'll give it a few days to settle in.
10.1.0 (4.2.2), good so far
jdekoven said:
I noticed today there was a new release on 6.24.13 under "stable" cm-10.1.0-quincytmo.zip . Could someone explain to me the difference between this and the "release candidate" cm-10.1.0-RC5-quincytmo.zip which was released on 6.16.13? It would seem the former would be the more updated because of the later release date? I already have the RC5 flashed on running. Some issues here and there so just curious.
Thanks,
John
Click to expand...
Click to collapse
I've been running the 'stable' version for a couple days and only one b.s.o.d. Runs smooth and battery is about the same at RC5. Camera is good as well. Don't use Blu-tooth so can't testify for that. I reboot every morning and that seems to make a world of difference.
Wish stock JB would come to us.
Anyone know how to get stock screen resolution back?
20130804-Nightly stable
Hey all, just thought that since I complained about how buggy the nigthlies were, I should come back and say that I am now on the 20130804 and it is very stable. I have been using it since Monday and i've only have one reboot. I initially had some screen flickering when I had a solid green background (from an MIUI theme), but I switched to another wallpaper and don't have that problem anymore.
Just FYI.

[Q] Audio stops working from time to time

Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore

[Q&A] [ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies (tenderloin)

[Q&A] [ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies (tenderloin)
Q&A for [ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies (tenderloin)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies (tenderloin). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
The 20150112 version has brought full Youtube functionality for me (can't say anything about Netflix, since I don't have an account). Great job!
Correction: YouTube only works up to 360p, anything higher than that will still fail.
I'm noticing a strange issue. I use an app that downloads movie. At seemingly random intervals while downloading, the wifi will tank completely. When opening settings-wifi, no wifi points are found and/or listed. Toggling does not help. So far, only a reboot gets it back. I have only had this occur while making a lengthy download. Small downloads, basic browsing (chrome, facebook..etc) have not as of yet been impacted. The timing is random, so i'll do what I can to get a logcat. Until then, has anyone else had this occur?
Superuser
Got it to work with - UPDATE-SuperSU-v2.40.zip - installed in TWRP.
spc2000 said:
Got it to work with - UPDATE-SuperSU-v2.40.zip - installed in TWRP.
Click to expand...
Click to collapse
It has root built-in. It's off by default now in CM, but you can turn it on in developer options.
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
rebel1699 said:
I'm noticing a strange issue. I use an app that downloads movie. At seemingly random intervals while downloading, the wifi will tank completely. When opening settings-wifi, no wifi points are found and/or listed. Toggling does not help. So far, only a reboot gets it back. I have only had this occur while making a lengthy download. Small downloads, basic browsing (chrome, facebook..etc) have not as of yet been impacted. The timing is random, so i'll do what I can to get a logcat. Until then, has anyone else had this occur?
Click to expand...
Click to collapse
I haven't noticed that. Does toggling airplane mode work? That works on my phone when the WiFi toggle won't.
Sent from my SGH-I337 using XDA Free mobile app
Hearthstone using Evervolv 5 runs fine but this ROM won't handle a match without freezing mid-game, which is surprising considering how responsive everything else is.
How long to boot CM12 on Touchpad?
I saw a post that said "a LOOOOONG time". Can anyone provide me with an estimare as to how long I should wait before I consider the device hung, please? It's been almost half an hour. Thanx.
01/15 Build
Everything works fine. I can even see AC bandwidth and was able to connect. The only main issue that still not fixed is that it does not recognize all BT devices. It is also slow first time with most of the applications.
rebel1699 said:
I'm noticing a strange issue. I use an app that downloads movie. At seemingly random intervals while downloading, the wifi will tank completely. When opening settings-wifi, no wifi points are found and/or listed. Toggling does not help. So far, only a reboot gets it back. I have only had this occur while making a lengthy download. Small downloads, basic browsing (chrome, facebook..etc) have not as of yet been impacted. The timing is random, so i'll do what I can to get a logcat. Until then, has anyone else had this occur?
Click to expand...
Click to collapse
Dremnblest said:
I saw a post that said "a LOOOOONG time". Can anyone provide me with an estimare as to how long I should wait before I consider the device hung, please? It's been almost half an hour. Thanx.
Click to expand...
Click to collapse
Upto an hour depending how big your gapps package is or in my case 3 hours as I was also reinstalling 60 apps.
But you should be able follow the progress by connecting to play store and your apps to see what is being downloaded /installed.
[ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies
How can i instal the new Lollipop 5.0.1 in my HP Touchpad. I downloaded al the pa.gapps.pico, FLITMAN, and Cyano 12. This is what i did.
I use the TPtool, complete data reset, and transfer the 3 files but i get an error message. How can i rezise the partition or how is the way to do it?
Do i need to add those 3 files in the Tpinstall folder and do a TWR recovery or wipe the data and install the OS with the new cyano 12?
Thank you
touchpad 4g
I have a Touchpad 4G model. Does this build work fine on it? I don't care about 4g data connections.. just wifi is good enough for me.
... considering that ART cache is way bigger than Dalvik cache (way bigger), and that our old TPs have very low eMMC performance, both sequential and random (iops), could it be that ART on the TP is/feels slower than Dalvik ?
daedric said:
... considering that ART cache is way bigger than Dalvik cache (way bigger), and that our old TPs have very low eMMC performance, both sequential and random (iops), could it be that ART on the TP is/feels slower than Dalvik ?
Click to expand...
Click to collapse
That may limit the benefits a bit but I still found ART on 4.4 quite a bit more responsive, and now 5.02 is just super smooth.
---------- Post added at 10:59 AM ---------- Previous post was at 10:47 AM ----------
Just wanted to say thanks, this rom gives the HPTP new life, if this had existed three months ago I wouldn't have bothered updating to a tab pro, and I have a feeling the tab pro and it's idiotic hardware navigation buttons is going to be gathering dust now.
My TP must not like LP then. First of all, games are slower here and there. Just a minor framerate drop, nonexistent on KK (Example, Motoheroz)
Then, the common stall, like TP is waiting....
At least for me, KK is still faster, and it's not placebo. It's the difference between a pleasant experience or a unpleasant one
First of all thanks for the great post.
I successfully installed the latest rom 31-01 but after a while it freezes and needs a factory reset.
Hello Team,
I have all over all a little bit a different feeling. Is it possible, that the kernel is the problem of buggy stuff? Why:
- I tried the cm11 with kernel 3.4, it was really instable.
- I tried cm12 with kernel 3.4. The same issues.
- On cm11 I go back to kernel 3.0 and cm11 by milaq, working quiet ok.
- The same with cm12. Milaq's Version is based on kernel 3.0 and it is running.
Can it be that the kernel 3.4 does not run on all HPTP?
Sent from my A0001 using XDA Free mobile app
launcher3 is always crashing...
i tried to create a logcat hope may be helpful...View attachment 3148279
View attachment 3148280
View attachment 3148281
With the 0207 build, it's not exactly crashing, but it is very choppy compared to the pre-0122 builds. Also, the graphic glitches in the lock screen and on Youtube in fullscreen mode are still there.
Hi, im using the lastest build, its working great, very stable. However, im facing a problem that is the time for charging battery is really long. It did not happen when I used the CM11 (4.4.4) build. The fact that I do not use the original charger. How can I fix this problem? Thank you.

Categories

Resources