I installed the OC kernel/fast mode from this thread. http://forum.xda-developers.com/showthread.php?t=1906507&page=7
and it works well, but I have a lot of bleeding and ghosting going on. IE. The outline or parts of images stay after I start zooming/panning, basically doing anything. Is there anyway to get rid of the bleeding?
Fast mode does degrade display quality - it's not that good for reading in fast mode, imo - but is helpful for things that redraw the whole screen.
If you just use the overclock and change the governor to performance, the quality of the display isn't affected and you get a performance benefit. I briefly tried locking the cpu at the higher end of the frequency range, which is noticable but I suspect drains the battery more than needed.
Terminater27 said:
I installed the OC kernel/fast mode from this thread. http://forum.xda-developers.com/showthread.php?t=1906507&page=7
and it works well, but I have a lot of bleeding and ghosting going on. IE. The outline or parts of images stay after I start zooming/panning, basically doing anything. Is there anyway to get rid of the bleeding?
Click to expand...
Click to collapse
Try clearing "dalvik cache".
Have you flashed the latest kernel 166?
http://forum.xda-developers.com/showthread.php?t=1906507&page=5
For viewing images I use "JustPictures!". For PDF's, 'EzPDF' and 'Ebooka'.
The ghosting is hardly noticeable.
Here is compare of fast mode and no refresh on my nook. fast mode has a high loss of contrast and a lot of ghosting.I preffer no refresh. Program is EBookDroid.
Thanks for the suggestions, guys!
I'll try them out and see if they work.
Related
I dont know if i am explaining this right, but it seems that whenever battery status is running, the pixels seem to get very blurry. For example, the signal bars start shivering, the bars become blurry, and random blurry lines show up in random parts of the screen. has this happened to anyone else, and if so have you fixed it?
Thanks in advance,
Anish88
If by that you mean that the screen starts flickering like a very old CRT monitor, then it does happen when the CPU in underclocked. In my wizard, the view becomes unstable below 100MHz, but it might vary from device to device.
First thing you might want to do is to go to batteryStatus options and disable the CPU scaler (dynamic CPU overclocking) and set the CPU speed to stock 195MHz. If after that the screen becomes stable again, it means that it was a problem with underclocking. In that case you'd need to find a minimal speed on which your screen looks fine - just test all the speeds below 195MHz and set the minimal speed not causing screen problems as minimal speed for the CPU scaller (it's in BS options/CPUScaler)
i believe it happens when ever this an overclocked speed. But it also happens occasioinaly at 195 mhz. is there any fix for this?
any ideas?
nobody else has had this problem????
Just a few thoughts about 2.1 vs. 2.2
Am I just smoking crack from all the repetitive flashing every other day, or do some of the mature 2.1 builds out there run smoother and have less battery drain?
I decided to drop back to an older DC 2.1 build and I keep finding myself thinking that even though some things are not as "zippy" overall I am happy with the performance. I also noted there were some odd items only seen on 2.2 roms, no matter what kernel I was on. These little things included the screen appearing to momentarily light up brighter at the bottom of the screen, and an odd bluish hue to white web pages until I would touch the screen. I have not been able to get the full flash working as smooth as on 2.2 , but ill keep messing with it im sure.
Yeah on average the mature 2.1 roms will have better battery life then 2.2 roms, but with a custom 2.2 rom (DC, BS, etc...) my battery is almost as good as my 2.1 was.
The slightly less battery life on 2.2 is well worth the performance. Are you running the newer kernels? (2.6.32 versus 2.6.29). The 32 kernel seemed to have helped a lot in terms of responsiveness
While I might have had slightly longer battery life on 2.1, if I did, it isn't by much.
No way I could go back though, their are just to many things that work so much better on 2.2. Most noticable for me is how fast things open. Allong the same lines, when you open the settings/aplications menu or Titanium backup you don't have to wait two minutes for it to populate. Then their is the flash that actually works correctly on web sites. My phone boots up significantly faster, and just runs smoother. Nope, I couldn't go back.
wfrandy said:
While I might have had slightly longer battery life on 2.1, if I did, it isn't by much.
No way I could go back though, their are just to many things that work so much better on 2.2. Most noticable for me is how fast things open. Allong the same lines, when you open the settings/aplications menu or Titanium backup you don't have to wait two minutes for it to populate. Then their is the flash that actually works correctly on web sites. My phone boots up significantly faster, and just runs smoother. Nope, I couldn't go back.
Click to expand...
Click to collapse
I actually find the new Flash to be annoying... with Flash Lite, you just double-tapped on the video, and it would go to full-screen... now it plays everything on the page, and can go really slow, and then you have to try to zoom in and find the full-screen controls on whatever video you're watching, in order to get it to fill the screen properly... unless there's a trick I don't know about...
ScrapMaker said:
I actually find the new Flash to be annoying... with Flash Lite, you just double-tapped on the video, and it would go to full-screen... now it plays everything on the page, and can go really slow, and then you have to try to zoom in and find the full-screen controls on whatever video you're watching, in order to get it to fill the screen properly... unless there's a trick I don't know about...
Click to expand...
Click to collapse
Long press on the flash video to bring up the full screen control or you can try to tap the full screen button on video players like Youtube. Either way, once you have it full screen, it runs pretty well. Video still lags a bit, but games run way better than they did in flash lite.
i never updated my evo... i'm still on the original release rom with no updates. my phone isn't broken and i have sudo root via unrevoked 1 so nothing pressing me to update to 2.2 just because its available....
superlinkx said:
Long press on the flash video to bring up the full screen control or you can try to tap the full screen button on video players like Youtube. Either way, once you have it full screen, it runs pretty well. Video still lags a bit, but games run way better than they did in flash lite.
Click to expand...
Click to collapse
damn, long-press doesn't work for me... that only worked on Lite
I'm using burnt droid & 4.1.2 kernel. Did the battery memory wipe as well. I get about 32 hours generally after a week of the battery data adjusting to the battery itself. Also, don't have to use task killers anymore.
Hi, I was about to buy the 7.7 at the store quem I saw something wierd. When in stock browser, the whites went blueish, but in others apps it was ok. Is this a normal behavior of the browser or just a fault unit?
Ps: I have postponed the device until someone clarifies this to me. This is the best place to ask. So please masters help me.: )
I believe this is due to a settings in the browser to conserve energy, as white tends to drain more power from the screen.
Click on the top right corner -> Color
You should be able to set the color level for power saving. Try setting it to Default, and see if the problem still exist.
Thanks man, I was really worried about that. I am glad it is just a setting.
Update
Lenovo fixed the issue in the latest update with my initial method which was switching off the CABC in the backlight controller which gives us a brightness boost. So obviously it is not dangerous.
Old Message:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
Instructions:
Use a build.prop editor form the Playstore
Edit the variable "ro.qualcomm.cabl=2" and set it to 0. CAUTION this modifies the system partition. If you want to receive OTAs in the future you will have to flash the system partition with an original image or backup.
Reboot
Technical details:
There are three places where CABC can be switched off:
In the build.prop
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c -> could be dangerous because it increases brightness and the voltages in the backlight controller
matshias said:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
I attached an Automate flow which disables CABC and guess what we get a brightness bump of about 20%. Now the maximum brightness of the display is even a bit brighter than my old Yoga Tab 2 and should be on par with the 3 pro
Make sure that Automate runs on system startup and has root enabled.
Technical details:
There are two places where CABC can be switched off:
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c
It turns out that if you disable the latter CABC is off even without modifying the former. Of course this requires ROOT to change. This could also be done in the kernel, but would need either a recompile or modifying the init.rd
Click to expand...
Click to collapse
Thanks Now only audio sync issues left for me and tablet will be perfect.
Have you compared the battery performance with and without CABC disabled?
Ashili said:
Have you compared the battery performance with and without CABC disabled?
Click to expand...
Click to collapse
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
matshias said:
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
Click to expand...
Click to collapse
Yap, I think so. The battery life is long enough. Thank you.
I would think as long as you manually adjust brightness to match your content, you'd get similar results.
I modified the thread to use a less invasive method. I am having issues with my tablet. I am not sure it was caused by this mod but just to be safe I recommend everyone not to use it any longer.
what kind of problem?
chuwq1038 said:
what kind of problem?
Click to expand...
Click to collapse
Everything works (also the display) but the battery drains and the back of the tablet gets warm even when the tablet is switched off. Could be completely unrelated to the mod, but who knows.
With latest official update I have a battery drain issue too. 15% down overnight...
In this thread I'll write (and add later) all the possible and effective ways to save more battery with this device, which has a pretty disappointing sot and doesn't last all the day. My aim is, though, to try explaining what's going on.
Since this is my very first guide thread expect a lot of changes in a short time.
Missing something? PM me or leave a reply here. You can discuss the various methods here as long as you're posting true tips
Let's start!
Little test
Can I hide text here? Nice
Battery Related Tips
Make sure your battery isn't dying Tip popularity: ultra Works: probably
All those tips won't really help you if your battery is faulty!
If you're like "I used to have 6 hrs SOT but suddenly I get 2 hrs on a 5 total" (extreme case) then you should directly buy a new battery (possibly the s7 Edge one) and replace it with the help of your friends
Click to expand...
Click to collapse
Replace your battery with an s7 Edge one Tip popularity: not so much Works: possibly
Just by installing an original S7 Edge battery you're theoretically improving your device's long lasting capacity by 41% (because their size is 2550mAh vs 3600mAh)
Then you'll need to calibrate it. Please refer to this telegram group if you are in need.
Click to expand...
Click to collapse
Display Related Tips
Decrease Brightness more and more Tip popularity: ultra Works: how not!
You'll understand this more when you'll read the next 2 tips! Decrease your screen's brightness and install an app to go even further. Also, enable auto brightness at minimum. It's ok saving power but it isn't if this means having a black screen
Click to expand...
Click to collapse
Black Themes Tip popularity: high Works: of course
This device features an AMOLED display.
If you didn't know, this technology gives you true black by shutting down the pixels on your screen!
Given this, you're actually saving power when your device is displaying pure black
Click to expand...
Click to collapse
Grayscale Display Tip popularity: medium Works: possibly
By setting your device in grayscale mode you're removing colors (wow) and since our device still features that AMOLED technology you're more likely to save power because of darker colors forcing pixels to be almost black.
Don't think you're really shutting down the RGB leds! In fact you're lighting up them all, but with decreased brightness. This won't work well if you use apps with bright/white themes!
It could also save power because of the less data to process(not confirmed)
Click to expand...
Click to collapse
Disable Always On Display Tip popularity: medium Works: yes Explained by: Nikx97
You can't use AOD for long. That's true and Samsung knew why (other than marketing purposes) when our community asked louly for having it on our device.
Behind that, our display is different from the one mounted on s7.
What's different then?
Our display requires the cpu to be awake everytime, updating the screen or not, because there's no memory this display could use to just keep showing an image. From s7 and later, there's this memory that gets updated by the cpu every minute.
This surely ends up with a huge drain
Click to expand...
Click to collapse
Software Related Tips
Reduce your CPU usage
Enable UPSM if you really need it Tip popularity: medium Works: of course
If your phone isn't rooted (I'd ask why are you even here) it will set up for you a black theme and set your device in grayscale mode, while decreasing brightness and disabling most apps. Then is up to you disabling wifi, bluetooth and setting it in airplane mode. I'd rather shut down my phone directly in this particular case
Click to expand...
Click to collapse
Don't play intensive games Tip popularity: Ultra Works: overkill
If you're not playing games your CPU will be grateful to you and your battery too. There's not much to be explained.
Of course you can still play games. Just try to prefer simple ones instead of PUBG Fortnite Asphalt 9 The Sims Minecraft Gta Online etc
Click to expand...
Click to collapse
Set up your CPU governors Tip popularity: suggested only by developers Works: Overkill if set properly
First of all for this you'll probably need a good kernel. Not necessarily a battery kernel, a fairly customizable one would fit nicely (If you're using an S7 Edge battery and you're on Android 7.0, feel free to try my kernel, ask for LKernel here).
Here are the best settings from what I've tried so far (I'm going to explain also why)
You'll need to set (perhaps with the aid of Kernel Adiutor or MTweaks) POWERSAVE governor for LITTLE and CONSERVATIVE for BIG.
The aim of this is to force LITTLE to work more than BIG, because it uses less power and it is enough for off screen processes and whatsapp, telegram and also some games (such as 1010 or sudoku or 2048). If you want to go further with this configuration limit your frequencies: the lowest you can to 600/800mhz for LITTLE and the lowest to 1800mhz for BIG.
With this configuration, when LITTLE can't handle some tasks BIG comes in rescue and solves the problem.
Lazily but it does his work and, of course, use less power.
It is advisable going further with kernel adiutor's settings to save more battery. I'm probably going to post my settings file later
Click to expand...
Click to collapse
That's all I got time for today, maybe I'll add more in a week
Reserved. Just because I don't want people commenting "first!"