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

Root CM 10.1 Nightlies Discussion

zacanger said:
20130613 Nightly resulted in a blank (black) screen on boot for me; waited a while, no change. Restoring a NANDroid now.

Just a warning.
Click to expand...

sosaudio1 said:
Confirmed same here twice
Click to expand...

scottfan81 said:
Same here
Click to expand...

aaronp121 said:
20130614 Nightly resulted in a blank (black) screen on boot AGAIN!
Click to expand...

Folks. If you're downloading a rom off of get.cm (ie. builds directly from CM) they aren't checking this forum thread for issues. You *MUST* report the issues on jira for anything to be done about it. If the bug isn't reported to JIRA, it doesn't exist. Bottom line.


I don't want to sound harsh or anything, but...
If you don't know how to do this, or can't do this... It's probably not a good ideal to crack-flash nightlies since their only purpose in life is alpha/beta-testing and checking to see if something breaks the code from compiling. From nightly to nightly there's absolutely no guarantee that everything will work and often it's likely that it won't as changes to the core code doesn't always mesh with every device.



Directions for using JIRA

How to take a logcat


It's great to warn people that a nightly will break something... But the "me too" replies aren't really helpful.

Also, if you check bbqdroid, you can see a sort of changelog to even know if it's worth flashing one nightly over the other.
 
Yoinx said:
Folks. If you're downloading a rom off of get.cm (ie. builds directly from CM) they aren't checking this forum thread for issues. You *MUST* report the issues on jira for anything to be done about it. If the bug isn't reported to JIRA, it doesn't exist. Bottom line.


I don't want to sound harsh or anything, but...
If you don't know how to do this, or can't do this... It's probably not a good ideal to crack-flash nightlies since their only purpose in life is alpha/beta-testing and checking to see if something breaks the code from compiling. From nightly to nightly there's absolutely no guarantee that everything will work and often it's likely that it won't as changes to the core code doesn't always mesh with every device.



Directions for using JIRA

How to take a logcat


It's great to warn people that a nightly will break something... But the "me too" replies aren't really helpful.

Also, if you check bbqdroid, you can see a sort of changelog to even know if it's worth flashing one nightly over the other.
Click to expand...

I would love to post logcats, but my USB ports are wonky. :( hopefully one of those 4 who experienced the blank screen will report it. (I am sticking to RC's)
 
Uzephi said:
I would love to post logcats, but my USB ports are wonky. :( hopefully one of those 4 who experienced the blank screen will report it. (I am sticking to RC's)
Click to expand...

Yeah, I may do it if nobody else will. I just don't run CM... I use PAC and it's a bit of a hassle to do a backup, factory reset, install the rom, restore... just to get a logcat.
 
Yoinx said:
Folks. If you're downloading a rom off of get.cm (ie. builds directly from CM) they aren't checking this forum thread for issues. You *MUST* report the issues on jira for anything to be done about it. If the bug isn't reported to JIRA, it doesn't exist. Bottom line.


I don't want to sound harsh or anything, but...
If you don't know how to do this, or can't do this... It's probably not a good ideal to crack-flash nightlies since their only purpose in life is alpha/beta-testing and checking to see if something breaks the code from compiling. From nightly to nightly there's absolutely no guarantee that everything will work and often it's likely that it won't as changes to the core code doesn't always mesh with every device.



Directions for using JIRA

How to take a logcat


It's great to warn people that a nightly will break something... But the "me too" replies aren't really helpful.

Also, if you check bbqdroid, you can see a sort of changelog to even know if it's worth flashing one nightly over the other.
Click to expand...

Note:

"Bug reports are accepted for Stable and "M" releases only. Nightly builds by nature may contain bugs or have stability issues and therefore bug reports for these builds are not accepted."

Direct quote from link you posted.

I'm now confused. Lol
 
scottfan81 said:
Note:

"Bug reports are accepted for Stable and "M" releases only. Nightly builds by nature may contain bugs or have stability issues and therefore bug reports for these builds are not accepted."

Direct quote from link you posted.

I'm now confused. Lol
Click to expand...

Weird, I could've sworn they accepted them for nightlies for some reason.


Either way, reporting back here that a particular nightly doesn't work makes sense so that people don't flash it. It wont get the bug fixed though, the only way to do that is in the bug tracker. If they don't accept them for nightlies, don't expect the bug to get fixed *shrug*.

The follow up "me too's" aren't really useful. That was the main point.
 
Yeah cm expects device maintainers to be up on the status of their devices. Unfortunately when they are not, this puts users flashing nightly builds in a bad spot.

And to be quite honest neither rmcc nor I run iproj devices as daily drivers. I got a sweet deal on a mint N4 from someone at work a few weeks ago so both my p930 and vs920 sit in a drawer most of the time.

That said I'll try to flash a nightly cm build in the next couple days and work with rmcc to figure out what's wrong.
 
Yoinx said:
Weird, I could've sworn they accepted them for nightlies for some reason.


Either way, reporting back here that a particular nightly doesn't work makes sense so that people don't flash it. It wont get the bug fixed though, the only way to do that is in the bug tracker. If they don't accept them for nightlies, don't expect the bug to get fixed *shrug*.

The follow up "me too's" aren't really useful. That was the main point.
Click to expand...


I wasn't posting for a fix, I was just posting that I was experiencing the same thing. I find relief seeing someone comment that they are having the same problems as me.

That being said I did find your post resourceful for someone interested in reporting a bug.
 
aaronp121 said:
20130614 Nightly resulted in a blank (black) screen on boot AGAIN!
Click to expand...

Yeah.... I think that adding a "same here" doesn't mean that we are trying to add insult to injury... Rather, we all know that sometimes you can have a bad flash or hardware just acts stupid from time to time. This is a forum and one persons experience may not mean that the flash is fouled up, but a couple saying "yeah that's my experience too" helps to warn others before they have to go thru the grief of flash, restore, flash... Or... Even so, could be that this is a known show stopper, and someone knows a fix.

It's all good. We inherit the risk just from rooting our phones. We all should shoulder the responsibility and understanding that flashing a nightly is probably gonna break something.

That's the beauty of doing things for ourselves.

I have no fear that a fix will happen soon. Until then, I will continue to flash nightlies and come back to the last known good one until it's fixed.

No worries!

Rich
 
tdm said:
Yeah cm expects device maintainers to be up on the status of their devices. Unfortunately when they are not, this puts users flashing nightly builds in a bad spot.

And to be quite honest neither rmcc nor I run iproj devices as daily drivers. I got a sweet deal on a mint N4 from someone at work a few weeks ago so both my p930 and vs920 sit in a drawer most of the time.

That said I'll try to flash a nightly cm build in the next couple days and work with rmcc to figure out what's wrong.
Click to expand...

Whatever it is... I'm pretty sure it's this commit to the kernel.

https://github.com/CyanogenMod/lge-kernel-iproj/commit/95d76a44f77a2540f308d8d865758662b5f75eba

I pulled that one into the kernel that I'm messing with, boots to black. Reverted it, boots fine.

Sorry if I can't be much more help.. But at least that limits it to a few lines of code (or just reverting that commit) to fix the issue.
 
beddybeezy said:
Will you post the version of your kernel with the reverted commit?
Click to expand...

any of the ones that I've posted before have it. It's a revert to undo a previous commit. Removing the commit seems to be what causes the problem.

You could also just yank the boot.img out of a CM zip from more than a 4 or so days ago, and flash it manually to get the same effect.
 
Yoinx said:
any of the ones that I've posted before have it. It's a revert to undo a previous commit. Removing the commit seems to be what causes the problem.

You could also just yank the boot.img out of a CM zip from more than a 4 or so days ago, and flash it manually to get the same effect.
Click to expand...

So do you think a manual flash of an updated nightly followed by a flash of the cm tweaked kernel would put it into boot?
 
reeseboy said:
I know they were fixed in RC5, but I haven't tried any of the newer ones yet... might flash one tonight to see.
Click to expand...

I'm running nightly 6/12 and the videos do not always work. From a webpage in chrome if you click on a video in portrait it will not show bu you can hear the audio so it is playing, just not visible, If you turn the phone to landscape you can see the video for split second then it goes scrambled with angled lines. Turning the phone back to portrait you can see the video for a split second then it will disappear. Sometime the screen will scramble completely and your only course is to hold power for 10 seconds to reboot.

I am going to go back to RC5 and do more tests. :)

Loaded RC5 and videos play correctly even when rotating from portrait to landscape, youtube app fc's shortly after opening it and doing nothing. If I select a video or pull down menu I can watch but just sitting it will fc.
 
tdm said:
Didn't get a chance to look at the black screen issue on the latest nightly builds yet but I'll try to do that tomorrow. It's pretty important because it's affecting all nightly builds for all ROMs.
Click to expand...

like I was saying that one revert that rmcc committed is the changer. Without it the kernel still displays fine. With it...black screen. Unfortunately I'm not good enough to understand why.

Sent from my VS920 4G using Tapatalk 2
 
bones420la said:
Is YouTube and video playback working like it should?
Click to expand...

I have issues in the YouTube app where, when a video starts in the small window, the information and all comments below are covered by black then fuzzy lines.... It's almost like the video is smeard and zoomed because if a video opens with black background and blue text that animates off screen, it colors the black frame below. Tried to take a screenshot and it came out fine. Side note.. Paused video to take the screenshot and it cuts off just below shutdown... Had to guess where the button was.

BUT....

Turn the phone from vert to horiz and it's a little slow to respond but it looks like it runs well in the horizontal or wide-screen mode.

Video playback by device seems OK.
 
sosaudio1 said:
I have issues in the YouTube app where, when a video starts in the small window, the information and all comments below are covered by black then fuzzy lines.... It's almost like the video is smeard and zoomed because if a video opens with black background and blue text that animates off screen, it colors the black frame below. Tried to take a screenshot and it came out fine. Side note.. Paused video to take the screenshot and it cuts off just below shutdown... Had to guess where the button was.

BUT....

Turn the phone from vert to horiz and it's a little slow to respond but it looks like it runs well in the horizontal or wide-screen mode.

Video playback by device seems OK.
Click to expand...

Playing videos in YouTube in Firefox is bad too. I keep trying to take a screenshot and can't. The screenshots always turn out OK.

Hang on...got an idea...
 
You must log in or register to reply here.
Back
Top Bottom