CyanogenMod 11 - OnePlus One Nightlies - Bug Reports & Discussion - ONE General

This thread is aimed at people running nightlies on their oneplus one. I think it is good to have a place where we can write about bugs we see on the nightlies. The developers can check this page now and then to see the common issues being faced. Bugs mentioned here can also be transferred to the JIRA.

The issue with the network icon being transparent in the notification bar is being worked on here http://review.cyanogenmod.org/#/c/72566/.
Therefore the next nightly should fix this.
One other bug I have seen is the colour calibration that is not well calibrated and recalibrating it has no effect on the colour. The only way to correct it is to install a kernel and modify the color gamma settings. I started seeing this issue after installing 20140905 nightly.

Please feel free to use the existing thread for nightlies located here:
[OFFICIAL] CyanogenMod 11 Nightlies for OnePlus One

Related

[INFO/FAQ] Unofficial Cyanogen Mod Nightly (6/6 - I'm taking my ball and going home!)

Well, I did it. Ported my number to T-Mobile. Poorer signal in some places, but I get consistent 4Mbps at my desk at work.
So.... I'm going to pretty much retire from maintaining this OP.
If someone wants to start a new thread with a similar format, go for it. If not I'm willing to come in here and try to do a quick update once in a while. It's not like things are moving as fast as they used to anyway, and the appspot changelog is great for displaying what is going on.
[HIGHLIGHT]Some Goodies:[/HIGHLIGHT]
With HDMI out there are some cool possibilites for the Evo. One of the best examples is in a thread started by Lokifish Mars: Use your Evo as a Desktop PC
There are tons of great theme engine themes. Many on the market and some only available on XDA. But since I'm a self serving biased jerk who unfairly looks out for his friends, I've got to mention the Sculpted theme from Shift. I loved Sculpted on CM6, but the version he created for CM7 is incredible, and all you have to do is grab it from the market, and then choose it in Theme Chooser.
Everyone's favorite something-goat-something-Shift-hater Karadorde dropped a little ray of nightly flashing sunshine in our lives. It's a recovery flashable script similar to Calkin's flash all that just flashes cache and dalvik for those times you've gotta have your nightly fix, but don't feel like setting everything up again. Check out his thread for instructions, and download the script there or here: nightly wipe zip
rstuckmaier has basically been doing my job for me recently, and created a thread just for CM7 fixes, tweaks, and work-arounds.
WiMax support is built into CyanogenMod 7. HDMI mirroring is supported in the kernel, but you will need an app to turn on mirroring. You can grab HDMwIn from the market. After trying it out, please support further TeamWIN projects by buying the donate version.
Quick Links:
Nightlies
Google Apps
Commit Log
DrMacinyasha's Mirror (CM and more)
Changelog App
CM Forums Evo Experimental
rstuckmaier's Tips Thread
TecherrataFiles Twitter - Mirror of releases
[HIGHLIGHT]New since 7.0[/HIGHLIGHT]​See the Official Changelog at this link
7.0.2
Common: Fix issue with missing built-in themes
Common: Update bundled ROM Manager to latest version
Supersonic: Actually fix GPS
Supersonic: Fix proximity and light sensor
7.0.1
Common: Fix fling velocity of status bar and ADW swipe - Sven Dawitz
Common: Fixed webview layout bug (issue 3229) - Zinx
Common: Fix GVoice-opens-twice bug - Zinx
Common: Fix issues on all devices with DNS resolution failure after some time - Zinx, various
Common: RTL improvements - Eran Mizrahi, Eyad Aboulouz
Common: Fix crashes in Arabic locale - Eyad Aboulouz
Common: Add Arabic keylayout - Eyad Aboulouz
Common: Improve ADWLauncher scrolling/zoom performance - Pavel Kucera
Common: Fix excessive memory use when appending to textviews - Cyanogen
Common: New wallpapers from the CM community (CC License, see app for credits)
Common: Option to disable vibration while in-call - Evan Charlton
Common: Add long press option to status bar widgets for settings - Alex Avance
Common: Compact carrier and status bar tweaks - Nihanth Subramanya, rorifree
Sholes: Fix connectivity loss bug - cvpcs
Speedy: Fix keyboard lights - JD Horelick
Glacier: Fix backlights - Zinx
Glacier: fix GPS issues - Zinx/QCom
msm7x30: Fix bugs during video resume - Zinx
qsd8x50: Fix 720p video playback
qsd8x50: Unified 2.6.37 kernel - Cyanogen, toastcfh, slayher
Espresso, Legend: WiFi fix (HTC)
Supersonic: Fix GPS issues (HTC)
##########################################
Please bear in mind this is a nightly build, meant to be a testing ground for developers, and there may even be times the new nightly won't work at all. This is a common way of working in open source software. Most of the problems you are encountering the developers are already aware of. With that said, most of the nightly builds has been very solid and stable for many people here, and several of us that are used to development software are using it as a daily driver. Just realize that is not the intention of nightly builds.
[HIGHLIGHT]CM6 features not available & Bugs[/HIGHLIGHT]​
Camera does not have touch to focus and some other features from CM6
Bluetooth Mouse cursor - BT mouse will connect, but acts more like a trackball. See the Use your Evo as a Desktop PC thread for a patch.
No 720p video recording
GPS often will not lock. Cyanogen said he is working on a fix for a point release. Basically the non-open source HTC drivers were used in CM6, but for CM7 they are using the open source reference drivers from the chip manufacturer. Something is strange or maybe even buggy about the Evo hardware. The good news is there is a workaround that has worked for most people.
Note - this is pasted from rstuckmaier's excellent tips thread
Make a Nandroid of your current CM7 setup.
Boot into recovery and perform a full wipe (or use Calkulin Format ALL zip)
Flash any Sense ROM
Open the Market and download MSL Reader, write down MSL.
Open Dialer/Phone and type ##4772579# (##GPSCLRX#)
When it asks you for a password type in your MSL
Reboot phone
BE OUTSIDE
Turn on GPS and open Maps, allow it to fully lock your location (may take a few minutes, do not just wait for initial lock).
Leave GPS on
Turn off phone, reboot into recovery.
Nandroid restore your CM7 backup
[HIGHLIGHT]Installation Info[/HIGHLIGHT]​
You must be fully rooted (including NAND rooted)
Nightlies are posted at: http://buildbot.teamdouche.net/nightly/supersonic/
After flashing the main part of CM, you will probably want to flash the Google Apps Add-On, which adds the Market and allows you to download things like GMail, Goggles, Voice Search, and Maps. Gapps is available here: http://goo-inside.me/google-apps/
There are now only two versions of GApps, one for Tegra CPUs and one for non. For the Evo you want the standard version without Tegra support
GApps changed for CM7 and only has the basics for market access. When you first log in you will be given a screen of checkboxes to download the apps you want. You can also add them manually later from the market.
DrMacinyasha's goo-inside.me is the official source for GApps, and also mirrors most of the other content:
drmacinyasha said:
Just a heads up, I've been keeping my own mirror of all of the CM stuff for EVO. Useful for those who want the gapps updates but don't have an account on the CM forums, etc., and also has all of the Snap kernel files mirrored:
http://goo-inside.me/google-apps/
http://goo-inside.me/evo/cm6/nightly/
http://goo-inside.me/evo/cm6/rc/
http://goo-inside.me/evo/cm6/stable/
http://goo-inside.me/evo/cm6/snap-kernel/
I update the site whenever I can; it's not yet auto-updating, but I'm looking at a way to fix that.
Click to expand...
Click to collapse
[HIGHLIGHT]What features are included[/HIGHLIGHT]​
Full AOSP
Running 2.6.37 Linux kernel
Android OS 2.3.3 (Gingerbread)
More standard Bluetooth stack. HTC uses a funky proprietary bluetooth implementation. Cyanogen has replaced this with a more common one, so the phone now supports HID (Mice & Keyboards) and the Wiimote app in the store.
Tons of Cyanogen Mod tweaks and tools, including but not limited to:
Updated music app with extra options and lockscreen controls
kernel speed tweaks
Notification Drop down power control
CyanogenMod Settings integrated into settings menu
DSP settings
T-Mobile theme engine
Torch flashlight uses camera flash, includes widget
Additional settings and tweaks for Contacts, Dialer, and MMS (maybe more)
[HIGHLIGHT]FAQ[/HIGHLIGHT]​Q. When the new nightly comes out can I just download and flash over the top of the install?
A. Because these are development nightlies they are not guaranteed to work in this way. In many cases this may work fine, but even if it does it may not implement a new feature or fix. For example the MMS fix would not show up unless you wiped, or deleted a specific directory. However, this usually works ok.
Q. What has changed in the newest nightly build?
A. For me the easiest thing has been to follow the CM Source twitter feed. Pretty much any change that doesn't mention another device specifically will show up on the nightly.
Look here for Cyanogen's changes: http://github.com/cyanogen
and here for CyanogenMod in general: http://github.com/CyanogenMod
Q. Flash isn't working
A. Go to the market, search for "Flash Player" and install.
Q. I don't have a Market icon or any other google apps
A. You didn't flash gapps or flashed the wrong one
Q. Rom Manager won't let me download the nightly
A. Purchase the premium version from the Market
Q. Why is the launcher slow?
A. It isn't really, but the defaults used on ADW make it feel sluggish. Try some of the settings from this post by midri
Q. How can I update PRL?
A. There currently is not a way to do it in Cyanogen Mod. You will need to restore a nandroid backup of a Sense ROM (you did make one, right?), update the PRL, then Nandroid back to CM6.
Q. What times are the nightly builds? And what time in my timezone?
A. To my understanding, the bot begins building at Midnight UTC which is 8:00pm EST. They finish around 30 mins later. You can always check this link and verify that the mod date is the next day (for us in the U.S.) In otherwords, It's currently 10:50pm EST on 7/10 and the mod date on the zip file is 2010-Jul-11 00:35:56 so I know it has been built:
http://mirror.kanged.net/cm/nightly/supersonic/
Q. Rom Manager says there are no updates
A. Since these are nightly builds and not releases, the filename stays the same and Rom Manager knows you have a rom named that already. If you want to assure you have the latest, clear your download cache and re-download.
Q. Can I install the Sense dialer/music player/widgets/etc. ?
A. By default no. Sense widgets only work with the Rosie launcher. Most of the other stuff it tightly bound to the framework, which is why many of the AOSP applications can not be easily installed on a Sense ROM.
Q. Is there any way to run the stock android 2.3 launcher instead of ADW?
A. Search the market for "gingerbread launcher." There are several available for free.
Q. My notification toggles keep disappearing! Where did they go?
A. Often changing themes will cause this. Just grab the Notification Restart app in the market. It basically just kills the notification bar so it resets.​
Please feel free to add any that I missed, but hopefully we don't get repeats of the same answered questions or known bugs. I hope this makes things easier for everyone to know what's going on.
Thanks again for your hard work, Cyanogen, Toast, #teamwin, and all of the CyanogenMod Team!
Thanks for the thread!
sent with evo 4g
HW 0003, and Nova panel.
I'm getting a green bar (graphical glitch) at the top during video playback.
Getting it on videos using the YouTube app, and also on some MP4 movies on my sdcard. Happens no matter what video player I use.
Oddly enough, videos that I had recorded with the Evo camera do not have this.
Is it just me? or anyone else having this issue also?
As far as the Facebook, I cannot add my facebook account. The first time it asked for info and appeared to work, but if I go back into Accounts it's not there and I can't seem to add it.
I downloaded Swype beta from the site and it's working fine for me.
Philosuffer said:
HW 0003, and Nova panel.
I'm getting a green bar (graphical glitch) at the top during video playback.
Getting it on videos using the YouTube app, and also on some MP4 movies on my sdcard. Happens no matter what video player I use.
Oddly enough, videos that I had recorded with the Evo camera do not have this.
Is it just me? or anyone else having this issue also?
Click to expand...
Click to collapse
Yup, same here, 003 with nova and seeing the green bar. But, mine switched between purple and green at first, then switching to just green. But weirdly,I've only seen the bar watching hq videos on youtube. Regular movies don't have that....odd.
Would it not be better to use a bug tracking software, even a free one to keep the info sorted?
also have green bar, hw3, novatek panel. don't have it in videos i've recorded. it may just be a function of the youtube app, nothing to do with cm
Another bug.
When you go to cm settings > input settings> haptic feedback tweaks > change any of the patterns ...cm settings force closes
Sent from my PC36100 using XDA App
Kllian said:
Would it not be better to use a bug tracking software, even a free one to keep the info sorted?
Click to expand...
Click to collapse
lol, they have one at cyanogenmod forum. which is probably where all this should be going anyway
HOWEVER, it isn't for nightly builds. you aren't supposed to be posting bugs there for nightlies
timothydonohue said:
lol, they have one at cyanogenmod forum. which is probably where all this should be going anyway
Click to expand...
Click to collapse
I don't think they do bug tracking for nightly's.
Sent from your moms EVO 4G
When the new nightly comes out can I just download and flash over the top of the install so I dont have to start from scratch tomorrow?
heres a question:
is there anyway to get the htc dialer app back on this rom, or is that part of sense, if so can you please link up a apk?
so does this mean that there will be a new build every night from now on or what.
Fring works on WiFi with no problems but FC's when on 3g.
Turn Exposure to +1 on front camera to make it not so dark.
dkotoric1 said:
so does this mean that there will be a new build every night from now on or what.
Click to expand...
Click to collapse
if i understand it correctly, it will be recompiled every night. however, if no code changes were made during the day, before compile, then the nightly won't be any different than the one before.
Also Exchange support in Froyo does not work reliably. This is not a bug in the mod, but in Froyo itself.
timothydonohue said:
if i understand it correctly, it will be recompiled every night. however, if no code changes were made during the day, before compile, then the nightly won't be any different than the one before.
Click to expand...
Click to collapse
Bingo. Changes may be EVO specific or may be generic to all devices. This is why nightlies are not reliable, they are simply a snapshot of the code at the moment. I read a comment that sounded like one of the changes made for the EVO broke the Droid build. Don't think of these as general use builds like we see from DC, Avalaunch, etc. When there is an RC or final, cyanogen typically will post that here.
needoZ said:
Also Exchange support in Froyo does not work reliably. This is not a bug in the mod, but in Froyo itself.
Click to expand...
Click to collapse
exchange is working perfectly for me?

[Q]how to get GPS working on Americanandroid Mod?

I have the same issue as posted here: http://forum.xda-developers.com/showpost.php?p=13909627&postcount=8352
but I am not allowed to post in that thread due to forum restrictions (new user must have a minimum of 10 posts prior).
Are there any other users of the AmericanAndroid mod (around version 050611) that can't get their GPS to get a fix?
UPDATE:
Nevermind, it's a location based issue (I'm in Europe). Although the changelog of the mod stated earlier:
-made major changes to the gps.conf file to allow for faster gps lock times (fasterfix / any gps fast fix software is now NOT RECOMMENDED) the only gps changes you should be making is the old style where you edit gps.conf and change the "us" entries to your own.. ie "gb" "pl" "ca" etc.
Click to expand...
Click to collapse
the app Fasterfix really did fix the GPS!
The May ACA builds have been problematic since they moved to Android 2.3.4. If you are going to use that build, you really need to track the forum on a daily basis and be prepared to update regularly. The GPS issues have been thoroughly discussed on that forum. The 0519 build seemed stable for the two days that I used it although the battery drain was a little high. I just updated to 0521. I'll see how that works tomorrow.

[BUG Report] GT-I9100 Dialer isnt correctly working / AOSP Camera Bug

Hey,
I didnt know where i should Post my Bug Report so if its the wrong section dont hold back to tell me.
I'm currently using my Galaxy S2 for daily use and after flashing some Kitkat Roms Omni is in my opinion the most stable rom and with Nova + ART a damn fast Rom, so thank you very much for supporting my Device.
I dont know whats happening the last weeks but it all began with an Opendelta Issue, i wiped all Data / Factory Reset via TWRP and flashed the Rom completely new and OpenDelta still didnt work, it just said every day its all up2date. Now after a couple of days it is working again, dont know if it was a Server Issue or something else - at the official Omni Page no one post News so i have always to guess whats happening
Currently i found 2 Bugs, if you want to call someone you open up the Dialer and then the Button for the Numbers but after clicking it, theres nothing(Screenshot is attached). You have to go back and try it again then the Numbers are there. The second Problem is that there is no Zoom in the AOSP Camera App if you record a Video. My currently workaround is the Google Camera App, there all is working fine. Also there are some Issues with Apollo , freezing , doesnt update the Song DB etc. , dont know why its so popular - its horrible. Replaced it also with a 3rd party App - Omich/Rocket Player.
The last Problem is that not everywhere in the Settings the correct language is used, if you need some translation help im sure many users would like to help(including me) but that is in my opinion nothing critical .
...and sorry if my Text was hard to read, its not my native language but im working on it :silly:
Regards
Per the FAQ, this is not the place to put bug reports.
However, I9100 hasn't been maintained in a long time, so filing a bug report will be a waste of time. Support for this device is currently going to be dropped with Android 5.0, and if it receives 4.4 bugfixes, that'll have to come from a new maintainer as none of the former maintainers have time/motivation for the Exynos 4210 devices these days.
Some of the issues you describe with Apollo aren't Apollo issues, but the result of a very deep-down core bug that has a side effect of screwing up storage access. This bug has been known for nearly a year (there's a big thread disucssing it somewhere around here...) and still no one has found a fix for the root cause. In fact, it's one of the #1 reasons the device is getting dropped for L. (It will absolutely not receive nightlies unless someone finds and corrects the root cause.)
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
pfxandroid said:
Hey,
Thank you for your response. :good:
I reported the Bug on jira and there is a workaround for the Dialer Bug: Setting The Animator Scale higher than 0.
The Drivers are the problem right?
Click to expand...
Click to collapse
Well, there are three things you listed:
1) Dialer stuff - probably some sort of odd HDPI issue and/or graphics subsystem stuff. The Exynos4 graphics subsystem is why many developers don't want to ever touch the platform again.
2) Zoom in video - What resolution was Google Camera? Zoom has NEVER been available for 1080p resolutions on the Exynos 4210 family, not even stock firmware will zoom in 1080p
3) The storage issues are a symptom of a deep-down kernel bug that no one has found the root cause of. This is the #1 reason the device is getting dropped for 5.0 - there is no chance even if a new maintainer steps up that nightlies will resume until someone tracks down the root cause of this one. http://forum.xda-developers.com/showthread.php?t=2612329 has more discussion (warning: It's long...)

Updated my findings on "cm for wear"

So when I was looking at my cm repos re-syncing I noticed a line of code that mentioned 5.0.0 support. So I then was like "cool, cm for wear" and I wanted to check on my findings so I waited like 3 hours for the sources to be done syncing I found that I could not build for it. I then went on there github and found little mentions her and there but NO`specific tree for any of these devices. Here is two screen shots I took: https://drive.google.com/open?id=0B...kNiNjBsVDUzbVc3YkQtOGZSMXY2dTBfcFk&authuser=0(The rectangle in red is the only thing you need to see the blue does not matter)
Is anyone here on the cm team?, can you maybe shed some light on this mystery? does anyone know anything? Please tell down below!

What OS to chose?

I like every OS and i dont know what to chose. please answer in a poll what OS are you using or you recomend it
Really they're all equally good apart from CM13 - all the CM13's have a bug that prevents autorotation working.
I saw thaat todays nightly (IF it will appear today) will fix sensors bug. If it will, i will use cm13 because its awesome

Categories

Resources