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

Root Brightness M6 and Monster 5

DaemeonZane

Member
I've currently got m6 installed, and had Monster 5, both with the OC kernel version. The crappy part is my brightness has been maxed out, and can't get half the brightness I got on stock. Any ideas as to what I can do? I've tried theme and ron changes, LCD changes, turning off auto brightness, etcetera, to no avail. What gives?
 
I've currently got m6 installed, and had Monster 5, both with the OC kernel version. The crappy part is my brightness has been maxed out, and can't get half the brightness I got on stock. Any ideas as to what I can do? I've tried theme and ron changes, LCD changes, turning off auto brightness, etcetera, to no avail. What gives?

If you've tried wiping and re-flashing roms and you still have that problem it might be a problem with your phone. When did this first happen?
 
When I flashed my first Monster Rom, 4. It didn't have problems in stock configuration, or with Admiral Beast, but all other roms present this issue. It sucks because I really like Monster, Lunar-Gen, and M6, and thought perhaps it was an issue with the roms... I can confirm again that stock, brightness is fine, but modded, it isn't working near as well.
 
When I flashed my first Monster Rom, 4. It didn't have problems in stock configuration, or with Admiral Beast, but all other roms present this issue. It sucks because I really like Monster, Lunar-Gen, and M6, and thought perhaps it was an issue with the roms... I can confirm again that stock, brightness is fine, but modded, it isn't working near as well.


It must be reqs kernel.
 
I know that I recently saw something on doing a custom OC kernel here... being a dev, Boraichee, how hard is the process? And do you recommend flashing lazy kernel instead of OC?


Building a kernel is not a simple task. As far as recommending the oc kernel or not, I think it depends on your phone. Have you tryed it?
 
Yeah, I'm running it now, and have the thing maxed 900/900, and other than brightness issues, the thing is smooth, especially with M6. Beautiful piece of work, that... I wonder... is there a specific build.prop setting or something that could counteract the kernel value for brightness threshold?
 
Screen filter on the market, try it out

I have... nothing changes it. Refunded around twenty bucks on paid apps pretending to brighten beyond the norm.... to no avail. Apparently, someone screwed up on stock kernel mods and the like, as apparently the ambient light filter on the top left facing is what is causing the issue, not brightness itself. If I can figure out how to reset the ODIN counter, I'll get it replaced... I wonder if perhaps that isn't due to all the flashing I've done. :banghead:
 
I've now identified that the issue is persistent across all ROMs, stock and otherwise, stock kernels and OC'd. But here's the kicker: On the starting Samsung logo, prior to the SCH-R720 logo, brightness is still as bright as it was on day one, but from the SCH-R720 logo on forward, brightness blows so hard, it could be a class 5 Tornado....:mad: Fact of the matter is, I have a phone that works perfectly sitting next to a phone that doesn't, and with no way to rule out a hardware failure due to modded kernels and ROM's, there's one thing left to try, and I don't know how. Is there any way at all I can take the other phone, dump everything, and get it over to my phone, maybe with adb?
 
It's a hardware issue with your phone, I've flashed a ton of roms and stuck with Monster as my daily driver, have not experienced any brightness issues...
 
I've now identified that the issue is persistent across all ROMs, stock and otherwise, stock kernels and OC'd. But here's the kicker: On the starting Samsung logo, prior to the SCH-R720 logo, brightness is still as bright as it was on day one, but from the SCH-R720 logo on forward, brightness blows so hard, it could be a class 5 Tornado....:mad: Fact of the matter is, I have a phone that works perfectly sitting next to a phone that doesn't, and with no way to rule out a hardware failure due to modded kernels and ROM's, there's one thing left to try, and I don't know how. Is there any way at all I can take the other phone, dump everything, and get it over to my phone, maybe with adb?

qpst can make a backup of your phone. then just restore the backup to your new phone. all with qpst. nothing else.
 
Issue solved, with an upgrade to 2.3.6 and a re-flash of the stock kernel through CWM. Apparently my phone and Req's kernel don't jive well... Still, I will be doing a qpst backup as advised. Thank you all for the help.
 
Back
Top Bottom