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
These threads are coming along nicely, love it, absolutely love it. Great work.
sent from my incarcerated Incredible 2
I'd have to agree with my bud above me here. Good job on organization!!
Sent from my Incredible 2 using XDA Premium App.
I'm really not trying to be a ****, but aren't nightly's specifically for soak testing new releases and squashing bugs. I had a d1 and used cm7, but not the nightly's. I always thought they were for testing. But apparently not. So, could someone explain their purpose to me? I'm honestly curious.
Sent from my Incredible 2 with Xda app
devator22 said:
I'm really not trying to be a ****, but aren't nightly's specifically for soak testing new releases and squashing bugs. I had a d1 and used cm7, but not the nightly's. I always thought they were for testing. But apparently not. So, could someone explain their purpose to me? I'm honestly curious.
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
The purpose is to enjoy the progress. They don't want bug reports because we are all aware of the fact that there are bugs, that's the nature of the beast. Today's build will have different bugs than tomorrow's, if we posted every lit bug that we experience then, well there would be no time to build, the team would just read bug reports all day. Over the course of time the team fixes bugs that recur and when enough things have been worked out they release an RC.
So....enjoy!
Thunderbolt!
So we don't have nightlies yet, and this thread is in anticipation of the merge?
devator22 said:
I'm really not trying to be a ****, but aren't nightly's specifically for soak testing new releases and squashing bugs. I had a d1 and used cm7, but not the nightly's. I always thought they were for testing. But apparently not. So, could someone explain their purpose to me? I'm honestly curious.
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
They are nightly build tests - nothing more. It tests the current state of the code repository, to make sure the build isn't broken. Users wanted to see them, so we share them.
xgunther said:
So we don't have nightlies yet, and this thread is in anticipation of the merge?
Click to expand...
Click to collapse
No. Merge was done a few days ago. Nightly build started last night.
attn1 said:
No. Merge was done a few days ago. Nightly build started last night.
Click to expand...
Click to collapse
So will they be posted here, or?
EDIT: disregard.
Sent from my Incredible 2 using Tapatalk
Is cmsrc twitter not being updated? 0 nightly already great. Only issue I have seem is in call volume is quite low
Sent from my Incredible 2 using Tapatalk
I didn't know we had a nightly build section or I would of been posting here.
I am currently running full-3 and I have been having issues with using the phone overseas. I am in japan on softbank and it is not picking up any signal.
The signal is wcdma and on the stock rom I could set it to that and get phone/sms but no data. I added the correct apn (after trying to get it to work properly) and I am still not getting anywhere.
Another thing I am worried about is the whole activate your phone part. When I flash it, it always has the activate screen and no matter what it will not activate so I don't know if that has anything to do with it. I hope not since I am not in the states so I can't just hop on the network and do it.
I'm on build 3 and my compass flips north and south in the maps application anyone else having this? I know it was in the stock rom but its fixed in the gb leak.
Sent from my Incredible 2 using Tapatalk
cheifkeiff said:
I'm on build 3 and my compass flips north and south in the maps application anyone else having this? I know it was in the stock rom but its fixed in the gb leak.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
I can confirm this.
Sent from my Incredible 2 using Tapatalk
Anyone else having any of the following issues?
- Home button does nothing at all (even holding it down)
- Volume buttons wake device (even though the setting for this is disabled in CM Settings)
- Cannot seem to enable the standard lockscreen at all (even when I enable a password or pattern lock - it just wakes up at the home screen or wherever I left off)
I'm running nightly #3, but I also had these issues with the beta.
xgunther said:
I can confirm this.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
I too have the reversed compass on maps. Strangely, the compass app on market seems to be correct.
megarek said:
I too have the reversed compass on maps. Strangely, the compass app on market seems to be correct.
Click to expand...
Click to collapse
Yep same thing happened to me on the stock rom and this one, compass app shows direction fine though. Also gps seems to lock quickly just the compass is just not showing the correct direction.
cheifkeiff said:
Yep same thing happened to me on the stock rom and this one, compass app shows direction fine though. Also gps seems to lock quickly just the compass is just not showing the correct direction.
Click to expand...
Click to collapse
Yep, known issue on stock rom: http://community.vzw.com/t5/DROID-I...-Maps-Google-Sky-and-Google-Earth/td-p/530726
I hope this can be fixed in CM7.
mturco said:
Anyone else having any of the following issues?
- Home button does nothing at all (even holding it down)
- Volume buttons wake device (even though the setting for this is disabled in CM Settings)
- Cannot seem to enable the standard lockscreen at all (even when I enable a password or pattern lock - it just wakes up at the home screen or wherever I left off)
I'm running nightly #3, but I also had these issues with the beta.
Click to expand...
Click to collapse
Sounds like a bad wipe. Wipe wipe wipe data/cache/dalvik-cache, then try again.
xgunther said:
Sounds like a bad wipe. Wipe wipe wipe data/cache/dalvik-cache, then try again.
Click to expand...
Click to collapse
Hmm well that sucks to do all of it over again. But I guess it's worth it. I'll try it and report back.
Sent from my Incredible 2 using XDA App
Never done nightlys...do I need to do a wipe before I flash these? Or can I install over the cm7 I currently have?
sent from my incredibly awesome incredible 2 with cm7
EI22 rotation lag!!!!i am noticing a lag rotating my phone when it come to me turning my phone from horizontal to straight up...i have done the horizontal calibration but still there is a lag...my question is ....is there a lag fix for this and yes i am running EI22 with the EI22 modem?
galaxyd700 said:
i am noticing a lag rotating my phone when it come to me turning my phone from horizontal to straight up...i have done the horizontal calibration but still there is a lag...my question is ....is there a lag fix for this and yes i am running EI22 with the EI22 modem?
Click to expand...
Click to collapse
First, can you make your title more clearer...Like EI22 rotation lag?
And second, try the calibration again. I haven't seen mention of this yet, but if more users show up with it then I am sure someone will make a lag fix on it.
Well I'll throw my vote in on this... I have lag and hor. cal. doesn't do it.
galaxyd700 said:
EI22 rotation lag!!!!i am noticing a lag rotating my phone when it come to me turning my phone from horizontal to straight up...i have done the horizontal calibration but still there is a lag...my question is ....is there a lag fix for this and yes i am running EI22 with the EI22 modem?
Click to expand...
Click to collapse
Have you tried doing the horizontal calibration with the screen upside down? That used to fix my rotation lags on froyo. Something about using it with the screen facing up always made it lag instead of fixing it.. If that don't work u might have to try using terminal emulator and see if that helps.
Sent from my SPH-D700 using XDA App
See Gingerbread Horizontal Calibration and these posts: my calibration question and jbadboy2007's response and jt1134's rebuttal.
The short story is that there is no known calibration method for GB, whether on a stock-based ROM or AOSP, such as CM7.
* Note: jt1134 is one of the CM7 devs, therefore I feel pretty confident he knows what he's talking about. I'm pretty sure jbadboy2007 is experienced as well.
Did you experience lag on froyo at all or is this a new thing?
Sent from my SPH-D700 using XDA App
Librizzi said:
Did you experience lag on froyo at all or is this a new thing?
Click to expand...
Click to collapse
I don't know if you're addressing the OP or me (probably OP), but I'll go ahead and tell ya I had rotation lag with a couple of different Froyo ROM flashes.
using the /system/bin/sensorcalibutil_yamaha I was always able to minimize the lag, though if I had a number of different home screens filled with apps it would still lag a bit more than a virgin ROM flash (not unexpected).
The "new thing" is that now there is no known fix for rotation lag*, which sucks.
* At least with CM7. The sensorcalibutil_yamaha fix may still work with stock-based ROMs in GB, I've just never tried any GB except for CM7.
AmericanJedi001 said:
I don't know if you're addressing the OP or me (probably OP), but I'll go ahead and tell ya I had rotation lag with a couple of different Froyo ROM flashes.
using the /system/bin/sensorcalibutil_yamaha I was always able to minimize the lag, though if I had a number of different home screens filled with apps it would still lag a bit more than a virgin ROM flash (not unexpected).
The "new thing" is that now there is no known fix for rotation lag*, which sucks.
* At least with CM7. The sensorcalibutil_yamaha fix may still work with stock-based ROMs in GB, I've just never tried any GB except for CM7.
Click to expand...
Click to collapse
I tried the /system/bin/sensorcalibutil_yamaha cmd with terminal emulator. Says the cmd is not found :-(
Bringing this thread back I guess, instead of making a new one. I'm having a big issue with 2-3 second rotation lag. Tried the upside down horizontal calibration and no go. Just throwing my hat in the ring in hopes that someone will find a fix.
There was a thread opened for the issue.
Refer to the link below.
Hope it helps!
http://forum.xda-developers.com/showthread.php?t=1347012
Alias8818 said:
There was a thread opened for the issue.
Refer to the link below.
Hope it helps!
http://forum.xda-developers.com/showthread.php?t=1347012
Click to expand...
Click to collapse
That's for cm7.
Sent from my Samsung Legen-wait for it-dary! 4g
ac16313 said:
That's for cm7.
Sent from my Samsung Legen-wait for it-dary! 4g
Click to expand...
Click to collapse
From the original thread:
* For other GB ROMs the fix should be basically the same, though I would recommend using the framework.jar from that specific ROM. (Maybe other, more experienced devs would like to shed some light on this topic? Would this framework.jar or flashable .zip be safe to try with other GB ROMs?)
So it may be usable...
Bumping this. Rotation lag is the most annoying issue with GB thus far
adamdelozier said:
From the original thread:
* For other GB ROMs the fix should be basically the same, though I would recommend using the framework.jar from that specific ROM. (Maybe other, more experienced devs would like to shed some light on this topic? Would this framework.jar or flashable .zip be safe to try with other GB ROMs?)
So it may be usable...
Click to expand...
Click to collapse
It might work it will break some things though, and he said the fix should be the same, meaning what he did should be the same to fix lag on other ROMs. Which it is.
Sent from my Samsung Legen-wait for it-dary! 4g
Holding phone upsidedown on a flat surface and calibrating fixed my issue completely.
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Holding phone upsidedown on a flat surface and calibrating fixed my issue completely.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Did not work for me...
Bumping this again. Praying that someone can make a fix for this issue. It is plaguing my experience. Otherwise it is outstanding. I repeatedly tried the upside down calibration and it has not worked.
The framework.jar from my rom has the fix. Take that file and then calibrate on a flat surface.
Sent from my SPH-D700 using Tapatalk
That's weird, I'm actually on your V4 ROM now. I could possibly reflash. Or I guess I could just drop that file over the old one, that's prob easier. Or maybe time to upgrade to V5 huh. Thanks for the response.
---------- Post added at 11:12 PM ---------- Previous post was at 10:43 PM ----------
Ok so, wow. I dropped the same framework.jar I already had over the old one, and the calibration tool in settings> display works. Very weird. But someone should mark this as solved in case it needs to be done separate from flashing a ROM.
marcusant said:
The framework.jar from my rom has the fix. Take that file and then calibrate on a flat surface.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Flashed ICS v5 and my rotation lag issue is gone Yay!
So I saw through Reddit that they were releasing this for like 70 devices. Anyone try it? How similar is it to the various KANG builds we have for our device?
I'm downloading now, so ill post my thoughts.
Sent from my Incredible 2 using XDA
so far it seems to be very similar to the Kangs. It does feel a teeny bit more responsive than those others.
The low volume on call bug is still present, but flashing aeroeven's .8 kernel fixes this just as it does in the KANG builds.
I didn't experience the multi touch issue that seems to be plaguing some users, but for what it's worth i didn't experience it on the KANG builds either.
The keyboard didn't stick for me while typing at all. i spent about 5 minutes typing random words into an email and it didn't stick once.
Edit: when logging into I heart radio the keyboard was sticky as hell.
one thing i've noticed is that once the market finally switches to google play, the label says Market, but it has the play icon.
excuse a newb
So I downloaded and installed 7.2 but when I try to add a new account to sync, it says it cant connect to the server. Ideas?
Also, what is this flashing kernel to get rid of low in-call volume?
Thanks!
deerhunter1911a1 said:
So I downloaded and installed 7.2 but when I try to add a new account to sync, it says it cant connect to the server. Ideas?
Also, what is this flashing kernel to get rid of low in-call volume?
Thanks!
Click to expand...
Click to collapse
I haven't experianced the server issue. maybe it was a bad flash, make sure you wipe data before hand.
aeroeven's .8 kernel over at rootzwiki
thenaut said:
I haven't experianced the server issue. maybe it was a bad flash, make sure you wipe data before hand.
aeroeven's .8 kernel over at rootzwiki
Click to expand...
Click to collapse
thats what i thought too, but i did a nandroid backup, factory data reset, then installed zip from sd...i had a few bad downloads that didnt work, but this is the second time it did work and second time no server...
ill look for that kernel! Thanks!
deerhunter1911a1 said:
thats what i thought too, but i did a nandroid backup, factory data reset, then installed zip from sd...i had a few bad downloads that didnt work, but this is the second time it did work and second time no server...
ill look for that kernel! Thanks!
Click to expand...
Click to collapse
Check the md5 sum as well.
Sent from my ADR6350 using XDA
thenaut said:
I haven't experianced the server issue. maybe it was a bad flash, make sure you wipe data before hand.
aeroeven's .8 kernel over at rootzwiki
Click to expand...
Click to collapse
Should we use the CFS or BFS kernel?
dimitri407 said:
Should we use the CFS or BFS kernel?
Click to expand...
Click to collapse
I'm using the .8 bfs at this time with good results, but you can use the cfs as well. Either will work, just different schedulers.
and....im a moron and just never flashed google apps. rom works perfectly.
I personally like kangs release better than this. I use swiftly x for my keyboard, and many times it lags when I type. Opera Web browser doesn't work for me, which is the browser I prefer. Long wait time switching between wifi and 3G. These are the issues I am having. Yes I wiped everything coming from kangs build before flashing this. I tried "fix permissions " and even uninstalled and reinstalled the apps that were misbehaving, but nothing has fixed these problems.
Sent from my DINC2
I tried the official build but it wasn't surprising to me that the most of the same issues that plague all cm7 builds for this phone are still present and the custom kernels don't really help to fix the problems. Im just going to stick with sense some more until cm works some of them out.
Sent from my ADR6350 using Tapatalk
What do you feel is missing?
Sent from my ADR6350 using Tapatalk
A fix for the use of wireless tether v2.0.7. The overall feel of cm just isn't there. Its not quite as smooth as I remember and I really hate that when I listen to music and try to do other things it causes the music to lag for a second. The call volume was still very low which I figured would be something they would address but they didnt. Wireless tether app not working is pretty much a deal breaker for me though. I have to use my phone for my home internet and the hotspot just isn't a very reliable connection most of the time and its very annoying to get disconnected and have to reconnect constantly.
Sent from my ADR6350 using Tapatalk
I found RC1 to be more stable than the last stable 7.1.0.1 release. Everything works for me including wireless tether, and I have not had any stability issues. The compass issue is also gone, which is a welcome change for me. (Trying to navigate Boston on St. Patty's after a few green beers via a compass that always points the wrong direction was not particularly easy.)
The only thing I have noticed is that the FM Radio will force close periodically if a notification noise chimes while I am listening, but it did that on 7.1.0.1, too. However, on 7.1.0.1, it would require a reboot rather than simply reopening the app. All in all, I'm pretty stoked. I am looking forward to stable and CM9 (hopefully) down the road.
General_Tso said:
I found RC1 to be more stable than the last stable 7.1.0.1 release. Everything works for me including wireless tether, and I have not had any stability issues. The compass issue is also gone, which is a welcome change for me. (Trying to navigate Boston on St. Patty's after a few green beers via a compass that always points the wrong direction was not particularly easy.)
The only thing I have noticed is that the FM Radio will force close periodically if a notification noise chimes while I am listening, but it did that on 7.1.0.1, too. However, on 7.1.0.1, it would require a reboot rather than simply reopening the app. All in all, I'm pretty stoked. I am looking forward to stable and CM9 (hopefully) down the road.
Click to expand...
Click to collapse
So the wireless tether app v2.0.7 works for you. Since I've had this phone every kang I've tried hasn't worked and the official still doesn't work so how did you fix it?
Sent from my ADR6350 using Tapatalk
thenaut said:
I haven't experianced the server issue. maybe it was a bad flash, make sure you wipe data before hand.
aeroeven's .8 kernel over at rootzwiki
Click to expand...
Click to collapse
I have been in search of a good kernal, but aeroevan's link on rootzwiki aren't working. I was running Skyraider Zeus but just switched to CM7.1.0.1 and was going to try the Tiamat kernal, but just saw that 7.2 was up. Any thoughts on whether I should switch to 7.2 and where I can get the aeroevan kernal if the link isn't working?
brymaster5000 said:
I have been in search of a good kernal, but aeroevan's link on rootzwiki aren't working. I was running Skyraider Zeus but just switched to CM7.1.0.1 and was going to try the Tiamat kernal, but just saw that 7.2 was up. Any thoughts on whether I should switch to 7.2 and where I can get the aeroevan kernal if the link isn't working?
Click to expand...
Click to collapse
Shoot me a pm and I can share a link with you from my box account to both the bfs and cfs versions.
Sent from my ADR6350 using Tapatalk
General_Tso said:
I found RC1 to be more stable than the last stable 7.1.0.1 release. Everything works for me including wireless tether, and I have not had any stability issues. The compass issue is also gone, which is a welcome change for me. (Trying to navigate Boston on St. Patty's after a few green beers via a compass that always points the wrong direction was not particularly easy.)
The only thing I have noticed is that the FM Radio will force close periodically if a notification noise chimes while I am listening, but it did that on 7.1.0.1, too. However, on 7.1.0.1, it would require a reboot rather than simply reopening the app. All in all, I'm pretty stoked. I am looking forward to stable and CM9 (hopefully) down the road.
Click to expand...
Click to collapse
You better belive we will have a stable version. HTC has announced that we will get ics. And cm is still being developed for our phone despite the fact that they will have to redo a lot when the right drivers are released. Looking forward to it. Hopefully the camera won't suck.
Sent from my ADR6350 using XDA
I'm not doubting we will have a working version I just don't see the really awesome versions until we get an official release or a leak. I'm going to hold out on an ics until something official comes out.
Sent from my ADR6350 using Tapatalk
disconnecktie said:
So the wireless tether app v2.0.7 works for you. Since I've had this phone every kang I've tried hasn't worked and the official still doesn't work so how did you fix it?
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
I am using the factory tethering option at Settings -> Wireless & networks -> Tethering & portable hotspot. I have had good luck with that. Is there a reason you are going with this particular app rather than the "stock" option?
joefrog1996 said:
You better belive we will have a stable version. HTC has announced that we will get ics. And cm is still being developed for our phone despite the fact that they will have to redo a lot when the right drivers are released. Looking forward to it. Hopefully the camera won't suck.
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
I have read HTC's announcement. I say "hope," because I am going from Cyanogen's "Will [insert device] get CyanogenMod 9?" flow chart (see Ricard Cerqueira's Google+ page). Even with the release of ICS, there is still only a 75% chance. The only devices that are certain at this point are those that already have CM9 nightlies. Given HTC's slowness releasing kernels, etc. and my general cynical disposition, I'll believe it when I see nightlies released for the Incredible 2.
Someone please please PLEASE tell me if there is a way to tell the captive touchkeys to stay on when the screen backlight is on. I may be in the minority but I can't stand the lights going out while I'm using the phone. Sounds simple but I REALLY hate them going off. There wasnt an issue with the unofficial CM10 alpha 5(?). At one time I had a rom that allowed me to set a timeout in seconds OR to match the backlight. That would be perfect in my mind. It would be great if the keyboard backlights were on any time the keyboard is open (IMO). If I'm in the minority then someone please tell me where I can set it at the OS level for just me. If I can't find a solution then I will have to go back to alpha 5 and stay there.
I have googled everything I can think of. I keep getting pages about a "great" new beature of CM9 that allows you to disable the backlight altogether. Great for some maybe but not me. I bring that up to say that I have tried to find the answer on my own first.
Is your capacitive lights feature unchecked in the advanced settings? I think the majority of people who have used samsung phones don't need the lights, so that's why this feature has been implemated.
Sent from my SPH-D700 using xda app-developers app
It is unchecked. I have no problem with the ability to disable but would love to have the option to have them stay on (JB Default) when the screen is on. I don't like having to guess where the buttons are when it's dark out. It's petty I know but it really does bother me enough to not use the rom If I can't change it.
Please post questions in Q&A
Thread moved
Thanks
FNM
FWIW - I'd like to see this as an option, too. It's an annoyance, but not a show stopper. I'm actually getting pretty good at guessing where the capacitive keys actually are, but sometimes get ticked at fumbling for them.
Al
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
arschend said:
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
Click to expand...
Click to collapse
This functionality would have to be added to the CM framework. The framework is what controls the 6 second timeout and a configurable timeout setting has not been coded. Anyone is free to work that out and submit it to the CM gerrit system
Sent from my SPH-D700 using xda app-developers app
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
reiter01 said:
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
I finally got brave
bbelos said:
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
Click to expand...
Click to collapse
A year has passed. Updates have come and gone. I even switched to another phone and back to the Epic4G. Same thing bugged me as always. I took the leap and set up a virtual machine so I could compile CM 10.1. I did a test compile and came out fine. I then made the changes you mentioned (that made more sense once I got used to the built process) and it WORKED!
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Thank you so much (a year late).
reiter01 said:
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Click to expand...
Click to collapse
I've had my Epic for a week, running CM 10.1, and this bugs the snot out of me too. Any chance you could PM me a link to your build? :laugh:
Sure
I'll try to figure out where to upload it. Keep in mind I know nothing about coding for Android. It's simply CM 10.1 (newest) for EpicMTD with 2 numbers changed and then compiled. I do like that the ability to control the brightness of the buttons still works. I don't like them super bright but I do want them always on.
Download
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
reiter01 said:
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
Click to expand...
Click to collapse
Understood, and thank you good sir. :highfive:
UPDATE: Loaded, booted, and is running without a hitch. You have solved my one major gripe with CM on my Epic. Thankyouthankyouthankyouthankyou!
Glad I could help someone else. CM10.1 is so near perfect in every way, it was frustrating to have such an annoying "flaw". In the older version of CM they didn't have the ability to adjust the brightness of the buttons so I can understand some people wanting them off or fast timeout. If I ever have some spare time I will try to add this as a feature to the menu but I doubt it will ever happen.
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
reiter01 said:
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
Click to expand...
Click to collapse
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Patch
bbelos said:
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Click to expand...
Click to collapse
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
reiter01 said:
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
Click to expand...
Click to collapse
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Awesome
bbelos said:
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I installed your cm11 but havent gone through and tweaked it out. Looks like that might do the trick. I have found a couple bugs (to be expected).
1. If on a call and hit home, there is no way to get back to hang up. Have to power off.
2. While on home screen. Hitting the "menu" button at the bottom and choosing "settings" brings up the launcher3 settings. Used to be the android settings...maybe it's a change. Not a deal breaker but I prefer the old way.
Thank you for all your work. I wish there was some way I could help you out.
Hi Devs
I'm from Mumbai India and i'm using galaxy nexus gsm.
It is an awesome phone but lately i'm having problem
My phone screen flashs and blackouts out of nowhere While operating my nexus and than i have to reboot it.
This has been happening from the time when i tried few custom roms (xylon, miui, overdrive, pa, minco v6 and madoco) back to back couple of weeks back. I don't know what is the cause of it and why is it happening.
So guys i need little help here.. Plzz help me fix it.
Right now I'm using baked 7 rom and gapp 4.2.1 12/12/2012.
Thank you in advance
I believe this is referred to as a Screen of death, or sod. Search the forum, and you may find some answers. Ive heard this is common on 4.2.1, but have yet to deal with it myself. Actually, though, ive had some close calls where the power button will not wake the phone, and i believe ive also seen where the actual issue is waking the phone from sleep..
Actually, I've just noticed that you're using the old gapps as well. The baked downloads page has the new gapps, and perhaps that may help you.
THANK YOU
bodh said:
I believe this is referred to as a Screen of death, or sod. Search the forum, and you may find some answers. Ive heard this is common on 4.2.1, but have yet to deal with it myself. Actually, though, ive had some close calls where the power button will not wake the phone, and i believe ive also seen where the actual issue is waking the phone from sleep..
Actually, I've just noticed that you're using the old gapps as well. The baked downloads page has the new gapps, and perhaps that may help you.
Click to expand...
Click to collapse
thanks alot,..
Have you tweaked the kernel options, messed with thecpu clock? Maybe try bringing all of that back to stock.
hi,
you guys may find reading this helpfull (it's dev's only, but reading it doesn't do any harm): http://forum.xda-developers.com/showthread.php?t=2080690
cheers
YES may be
jackbane said:
Have you tweaked the kernel options, messed with thecpu clock? Maybe try bringing all of that back to stock.
Click to expand...
Click to collapse
i had tweaked the kernal options once long back,.. it twisted kernel i guess