Related
LED Hacks is an app in the market free and it disables the bottom softkey lights so even in the darkest room you can't see that annoying light leakage..
Also will disable charging LED!
I don't care! I didn't know
I'd use this because I don't need then to be lit up, but also because since 2.2, they always come on.
If only LED hacks was actually in the market. :|
CarbonFiberSkins.tk
Yeah, I'd love such an application. Unfortunately I also cannot find it in the market.
Try one word ledshack
Its still in my market.
Ah, that shows it fine. Now I just have to find a good guide to rooting 2.2.
Edit: Typo, still getting used to swype.
Sent from my PC36100 using XDA App
But then you can't see your bottom keys, so doesn't that pretty much defeat the purpose?
Idk bout you guys but I've been playing with this phone for months now and I know exactly where all four soft buttons are without having to see them...I used to put a case on to cover the light leakage but not anymore....
It'd be nice if maybe someone can figure how dim permantly on boot
I haven't noticed any leakage at all.maybe I just haven't paid attention?
Sent from my %phone% using Tapatalk
One of the Lucky ones!
No leakage that i know. Or noticed. Was txting in complete dark for 2 hrs last night... ill pay closer attention tonight
sent from my Evo
Is there another way of doing this without root?
Not that I know of...the app needs to make admin changes (root)
jewelbaluyut said:
Is there another way of doing this without root?
Click to expand...
Click to collapse
Download terminal emulator and run these commands:
Code:
echo 0 > /sys/class/leds/button-backlight/brightness
That'll keep the capacitive keys backlight turned off 'til the next time you wake your phone from sleep with the power button.
Why Yoga tablet 2 screen looks so blurred and sharpened at the same time
Have you been wondering why your screen on the 10" Yoga tablet 2 with KitKat doesn't look really crisp even with some obvious sharpening applied? Here is why!
Lenovo screwed up twice!
1. Blur filter is applied. (KitKat ONLY) The BIOS/bootloader defines wrong display resolution. The Intel graphics driver (i915) gets confused and switches on panel fitting which includes a blur filter (fuzzy filter). Normally this is used if the display resolution is different from the frame buffer resolution to scale the image. Here the device just scales 1:1 and applies the filter. Luckily the driver is open source and it turns out there is a way to overwrite this feature No longer true for Lollipop. Thanks Lenovo
2. Sharpen filter is applied. (KitKat and Lollipop) The panel is not programmed correctly. When disabling the CABC feature (/sys/lcd_panel/cabc_onoff) the sharpening effect is gone. But CABC should have nothing to do with sharpen. Unfortunately the specs of the display (AUO B101UAN01.E) are not public so I cannot verify if the correct MIPI DSI commands are sent to the panel.
So our display is softened then sharpened again! What a waste!
Both workarounds are only temporary. After each screen off/screen on sequence the old values are restored by the system. So we need an app which sets the values after the screen is switched on. Or a new kernel. Or Lenovo cares to fix it in a future release
Fix (Root partially required)
I wrote an app which can disable CABC / sharpness filter (requires ROOT) and can disable the blur filter (KitKat, no root required) . Of course I am not held responsible if you brick or burn your tablet. I tested this on my 1050F with rooted firmware S000143_150105.
1. Copy app to device and install
2. Start app and select your setting
3. The settings may apply only after switching screen off and on again.
Source on Github:
http://github.com/Matshias/yoga2sharpness
Bugs / issues
- may not work directly after reboot, only after screen on/off
- fullscreen video may switch on CABC/sharpness filter again
Any suggestions? I'd be really happy if you could test and report
Cheers!
Matt
Update Jan 21
make more reliable and add complete source
Update Jan 26
Reliable implementation as app which automates this process.
Update Jan 30
new version 1.1 (please uninstall old version!):
- add option to start at boot and enable/disable applying the settings at screen on for manual operation
- add little delay after screen on for more reliable operation
- app should be harder to kill by the system
Update Feb 2
new version 1.1.1:
- Fix occasional reboot issue when using the setting on display on. Turns out Android sends screen on broadcasts sometimes even if the display is off. This causes a crash if the filter settings are applied.
Update Feb 11
new version 1.1.2 (please uninstall old version):
- hopefully ultimately fix reboot issues by using different method to start on boot
Update Apr 30
tested with new firmware S000198_150422. Same as before. Lenovo has not fixed the issue, but the app works like before
Update June 3
New version 1.1.3:
- fix full screen video playback re-enabling CABC/sharpness filter. As for CABC itself root is required.
Update June 17
Update for Lollipop version 1.2.0:
- blur filter disable no longer needed
- sharpness filter is still present. If root becomes available for Lollipop this should work there too
Update June 19
Fix for rooted Lollipop - version 1.2.1:
- the mechanism for sharpness filter disable from 1.2.0 didn't work, probably due to SE Linux restrictions
Matshias, you are a legend!
I bought a Yoga 2 10" a couple of weeks ago and the odd blurred and sharpened effect ruins what is otherwise a great little tablet. I'd always suspected it was some kind of odd scaling issue, but I haven't had time or sufficient Android knowledge (or root access on my device) to properly investigate it, beyond making up some test images with alternate 1 pixel wide black/white lines - which were rendering as grey on the Yoga 2.
I had a support ticket raised with Lenovo about the issue, so I've referred them to this post and one on the Lenovo Community forums.
Thanks for your hard work, hopefully Lenovo will implement the fix in a software update soon!
Cheers,
Richard
Thank you!
matshias: Thank you.
The blur filter disable makes a HUGE difference. I really appreciate you taking the time to post your results, hopefully Lenovo will take note and implement a permanent fix.
workes
Hi!
I have just started using your app with the latest firmware on a 1050L.
0) Unrooted device
1) installed your app and applied the non-root part of the fix - worked after screen on/off
2) rooted device with temporary cwm solution from this parent thread (- which worked as well)
3) applied the root-required part of the fix from your app - works as well
Thank you for this!
Great great great! Like the others here I was looking for a solution to this Problem since I bought the tablet.
I am really satisfied with your APP, now everything is way sharper.
BUT: When I test the screens resolution with a screen test APP, only the horizontal ( long sides) resolution seems to be right now. The vertical resolution (short sides) is still just grey, when testing single pixel lines.
Do you have the same Problem, what could cause this?
fanatictentacle said:
Great great great! Like the others here I was looking for a solution to this Problem since I bought the tablet.
I am really satisfied with your APP, now everything is way sharper.
BUT: When I test the screens resolution with a screen test APP, only the horizontal ( long sides) resolution seems to be right now. The vertical resolution (short sides) is still just grey, when testing single pixel lines.
Do you have the same Problem, what could cause this?
Click to expand...
Click to collapse
I see the same if the sharpness filter/CABC is still switched on. If you have root then try disabling the sharpness filter as well and then the screen test look fine. Obviously the sharpness filter in the panel is not uniform in all directions and seems to prefer horizontal resolution (in landscape mode).
Thanks again for the advice!
I just had to enable root, really cant look at that horrid screen anymore! But now it really looks as sharp as an 240ppi Display should look like!
problem
After installing the app I have problems.
In 10 minutes my tablet rebooted 3 times . Android not asked to reboot.
It was crash of sistem. My system is rooted.
After uninstalling I had no problems.
Regurds
Yosef said:
After installing the app I have problems.
In 10 minutes my tablet rebooted 3 times . Android not asked to reboot.
It was crash of sistem. My system is rooted.
After uninstalling I had no problems.
Regurds
Click to expand...
Click to collapse
Did you use the start on boot feature? This might cause it. I uploaded new version 1.1.2 which should fix that problem. Let me know if it works for you.
this is a fantastic fix, one that Lenovo should have implemented themselves
actually when i just got the tablet over christmas, it was running older firmware in which the blur filter was actually not enabled. yes i now realize the text was "over sharp" but it was clear, and what i expected for the price (i.e. not double the price for a galaxy tab S) but i was fine with the sharpness, it looked good, and the tablet otherwise suits my needs perfectly, and gotta love that built in stand. i didn't even know what people meant about the image quality, considering the mid-range target audience of the tablet.
anyway, i recently got the OTA firmware update to the current S000143_150105 and that's when it messed everything up. it enabled the blur filter, and it looked HORRIBLE. i tried to accept it because at 1 ft from the tablet, the text actually looked all right, perhaps even a slight improvement because it was slightly softer. but the blur filter is applied to EVERYTHING, so all the images and everything on the screen was blurred....it was like looking at an HD monitor with a state of the art GeForce video card but using the standard windows video drivers...everything stretched and totally blurry.
this is a great fix, i don't have my tablet rooted and don't want to take the potential battery hit to disable the sharpening filter (since i think it looks good just with the blur filter disabled). it might be in my head though, but i feel like the system is a little more sluggish...maybe due to the update, maybe because of this (great) app...i wish lenovo would fix this, seems easy enough. sours me to an otherwise great tablet for the price.
speaking of battery, i noticed in the last day after installing the fix that my tablet powered off sometime during the day, and when i restarted, the battery had drained about 30%. and it continued to drain faster than before. i previously got well over 10 hours of usage time playing movies and web browsing, in addition to up to several days of standby....today i had to charge it within 24 hours and only got about 7 hours use time and 13 hours standby...any chance it's related to the fix, or has anyone experienced it after the firmware update?
@digitalatlas: Thanks for testing the app.
Regarding your observations, I don't think sluggishness can be attributed to the app. After all it doesn't do much. Only when the screen is switched on or you manually start the app it changes the kernel setting. So it really shouldn't have any impact on performance.
The battery life should also not be affected by the app itself. It does not have any background tasks other than the kernel setting mentioned above and it shouldn't wake up the device as well. Although I saw occasionally that my app gets informed that the screen was switched on even though the screen was not switched on. That caused some reboot issues. But that was fixed with version 1.1.1 and 1.1.2 and I didn't see a reboot since I use 1.1.2. Also there are reports of hangs/reboots by other users unrelated to my app. Anyways it might be the case that changing the kernel setting has some other effect on the hardware, kernel and battery life. According to Intel documentation the filter is not meant to be switched on or off while the display is active. However, it is the only time it is possible to change it in our system. So to be sure we have to test and disable/uninstall the app and see if the battery life improves.
Hopefully Lenovo fixes this with an upcoming update!
Thanks!
Just got this tablet in the mail today and was disappointed by its display. So grateful for your fix, its like night and day with the blur gone. Guess I have a good reason to root now to get rid of the sharpness too. Mind me asking what method you used to root for this firmware?
Falv said:
Just got this tablet in the mail today and was disappointed by its display. So grateful for your fix, its like night and day with the blur gone. Guess I have a good reason to root now to get rid of the sharpness too. Mind me asking what method you used to root for this firmware?
Click to expand...
Click to collapse
I used the temporary CWM method [GUIDE] CWM & Root Lenovo Yoga 2 (8/10/13)
It is easy enough and works fine, but keep in mind that there might be issues with OTAs.
I'll keep track of the battery over the next little while, hopefully it was just an aberration that first charge. I'm getting better results with this second charge since the update and your fix.
Could you or someone post a picture shoeing the effect of turning the sharpening filter off? Might help some of us decide it rooting is in fact worthwhile. Thanks!
digitalatlas said:
I'll keep track of the battery over the next little while, hopefully it was just an aberration that first charge. I'm getting better results with this second charge since the update and your fix.
Could you or someone post a picture shoeing the effect of turning the sharpening filter off? Might help some of us decide it rooting is in fact worthwhile. Thanks!
Click to expand...
Click to collapse
I tried taking pictures but it doesn't really show the effect. Instead I made two screenshots and recreated the filter with GIMP. It should be very close to what the panel does.
Does anybody have any info from Lenovo? I think that this is preposterous! How can someone do that and have it go through testing? Unless there were no tests at all.
Buying Lenovo was a mistake.
v1.2 tested on my new 1050F. Awesome. I was disapointed by the screen but now it's perfect. Thank you so much to have done this patch!
+1
AMAZING PICTURE QUALITY!!.
Without blur picture is good, but witchout blur and sharpness image quality is FU…NG AWSOME!!
THANKS!!!!!
saupiquet said:
v1.2 tested on my new 1050F. Awesome. I was disapointed by the screen but now it's perfect. Thank you so much to have done this patch!
Click to expand...
Click to collapse
+1
Great app, thank you
Are you all running this with rooted devices? Mine is not yet rooted but notice a big difference with this app. How much better is it if I was to root the device? Thank you so much for this fix. I recieved my tablet today and was very disappointed with the display.
Does anybody know of a method or app to add always on display? I tried an app from the app store and it worked well but killed my battery. Probably because it disabled doze and kept the phone awake... Anybody have any input on this?
That function doesn't work exactly perfectly on the Axon but I am using ACdisplay with some success. The always on thing isn't going to be exactly what you'd see on a Motorola device though. If you want the wave to wake feature as good as it gets, try ambient display through xposed but it's still iffy and ACdisplay has much better notification layouts imo.
This is one of the things that really bugged me about this phone at first, especially with the tiny, barely visible LED notification light. Not good synergy.
Always on Amoled Beta
https://play.google.com/store/apps/details?id=com.tomer.alwayson
howdid said:
Always on Amoled Beta
https://play.google.com/store/apps/details?id=com.tomer.alwayson
Click to expand...
Click to collapse
I tried that one actually. I liked the idea but the power consumption was pretty crazy. Had to uninstall. Maybe others will have better luck.
What you need is a way to allow the CPU to go into deep sleep without turning the display off. I believe this is hardware dependant, though.
All recent moto phone have their own low-power CPUs specifically for ambient display and voice commands without requiring the CPU to wake.
Oneplus devices support gestures while the device is in deep sleep, but this is a hardware feature built into the panel, which is why these gestures are not customizable.
The problem with both of these is that they're hardware-specific, so unless ZTE has made provisions for always on displays, active display, off screen gestures, etc, theres going to be a pretty significant hit to battery when using apps that do these things.
xxBrun0xx said:
What you need is a way to allow the CPU to go into deep sleep without turning the display off. I believe this is hardware dependant, though.
All recent moto phone have their own low-power CPUs specifically for ambient display and voice commands without requiring the CPU to wake.
Oneplus devices support gestures while the device is in deep sleep, but this is a hardware feature built into the panel, which is why these gestures are not customizable.
The problem with both of these is that they're hardware-specific, so unless ZTE has made provisions for always on displays, active display, off screen gestures, etc, theres going to be a pretty significant hit to battery when using apps that do these things.
Click to expand...
Click to collapse
You can read on Qualcomms homepage about the 820 that it supports always on low power mode ....it is something the CPU can do ....look at Samsung's s7s they have the same CPU
howdid said:
You can read on Qualcomms homepage about the 820 that it supports always on low power mode ....it is something the CPU can do ....look at Samsung's s7s they have the same CPU
Click to expand...
Click to collapse
Sweet. I doubt the always on app uses whatever process the s7/g5 use to do this, is this something kernel related?
Thanks for the input everybody. If the Snapdragon 820 can support low power use like some of you suggested we may see this feature in cyanogenmod? (hopefully ZTE actually helps...) otherwise custom roms built on ZTE's base maybe. Although I doubt ZTE will add the feature to the rom in future updates.
xgerryx said:
That function doesn't work exactly perfectly on the Axon but I am using ACdisplay with some success. The always on thing isn't going to be exactly what you'd see on a Motorola device though. If you want the wave to wake feature as good as it gets, try ambient display through xposed but it's still iffy and ACdisplay has much better notification layouts imo.
This is one of the things that really bugged me about this phone at first, especially with the tiny, barely visible LED notification light. Not good synergy.
Click to expand...
Click to collapse
I've seen this app before. Might try it out.
Yes, glance plus
https://play.google.com/store/apps/details?id=com.thsoft.glance
It's awesome, plus your phone thinks it's on the lock screen. So you can shake whenever glance is active to turn on your flashlight.
Double tap to wake works WAY better.
Is also compatible with fingerprint unlock.
I use this on my Axon, haven't noticed any battery drain
MrWilsonxD said:
Yes, glance plus
https://play.google.com/store/apps/details?id=com.thsoft.glance
It's awesome, plus your phone thinks it's on the lock screen. So you can shake whenever glance is active to turn on your flashlight.
Double tap to wake works WAY better.
Is also compatible with fingerprint unlock.
I use this on my Axon, haven't noticed any battery drain
Click to expand...
Click to collapse
I can't figure out how to get the fingerprint working!
When it's on, you can't unlock with fingerprint, you have to wait until the screen is fully black
amus76 said:
I can't figure out how to get the fingerprint working!
When it's on, you can't unlock with fingerprint, you have to wait until the screen is fully black
Click to expand...
Click to collapse
Have you enabled these settings?
MrWilsonxD said:
Have you enabled these settings?
Click to expand...
Click to collapse
Yes and I havec to double tap ton open, the fingerprint is not working when glance is on screen
amus76 said:
Yes and I havec to double tap ton open, the fingerprint is not working when glance is on screen
Click to expand...
Click to collapse
That's strange! I haven't had that issue.. It just immediately unlocks for me.
I would try uninstalling, rebooting, reinstalling? + maybe another reboot? (I'm no tech expert.. But I'll reboot a phone till magic happens lol)
MrWilsonxD said:
That's strange! I haven't had that issue.. It just immediately unlocks for me.
I would try uninstalling, rebooting, reinstalling? + maybe another reboot? (I'm no tech expert.. But I'll reboot a phone till magic happens lol)
Click to expand...
Click to collapse
Still got the problem
amus76 said:
Still got the problem
Click to expand...
Click to collapse
Have you activated it as a device administrator?
MrWilsonxD said:
Have you activated it as a device administrator?
Click to expand...
Click to collapse
Yes, all autorisation
Maybe i'm expecting too much from this app, i want to unlock with the fingerprint directly when you get a notification instead of double tap and I don't think any app at the moment manage to do it
Thanks for the help
amus76 said:
Yes, all autorisation
Maybe i'm expecting too much from this app, i want to unlock with the fingerprint directly when you get a notification instead of double tap and I don't think any app at the moment manage to do it
Thanks for the help
Click to expand...
Click to collapse
That's strange.. As I'm able to do exactly that.. Sorry man.
I am using this app. The clock goes away after showing for a few seconds. It seems to happen intermittently.
MrWilsonxD said:
That's strange! I haven't had that issue.. It just immediately unlocks for me.
I would try uninstalling, rebooting, reinstalling? + maybe another reboot? (I'm no tech expert.. But I'll reboot a phone till magic happens lol)
Click to expand...
Click to collapse
My fingerprint was working. Now its doing the same as yours. Its not working not double tap unlocks phone now.
I have what I needed, thanks!
Hi, I'm wondering if someone with a Le Pro3, either the CN or US model (or both) could please provide me with the output for dmesg and logcat.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure, please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell df -P > df-P.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, for some root-required tidbits (these commands could actually be dangerous!!! they will be running as root, please be very careful, you've been warned): You have two ways you can do this:
Run "adb root" to put adb in an automatic root mode (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Please check the files to verify that the contents are not an error. The other method, if switching adb to root mode doesn't work, would be to:
Run "adb shell"
Run "su" to put your shell into root mode, NOTE: BE VERY CAREFUL HERE (this requires that you have root and allow adb commands to be run as root)
Run "adb shell ls -la /dev/block/bootdevice/by-name" and then copy/paste the output into a file named "by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num" and then copy/paste the output into a file named "by-num.txt"
Finally, if you are simply not able to achieve root on your device (either in general, or just for ADB), both of these tasks SHOULD be possible when you're booted into the TWRP recovery. If you don't have TWRP installed, then don't worry about it. I'm just assuming you do.
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
secXces_debaki said:
I can do that when I'm out from work in around 6 hours. For what exactly u need it? Just curious.
Click to expand...
Click to collapse
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
dr4stic said:
My own curiosity... Maybe put some of the info in Christmas cards, you know how it goes.
Click to expand...
Click to collapse
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
secXces_debaki said:
If my girl let me work on my phone I will send u a pm.
Was yesterday on the phone trying to build a rom, but always loose my baseband.. Lol. So she's a bit angry that I am to much on the phone ^^
I do my best sir.
Click to expand...
Click to collapse
Well, don't get yourself into any trouble. I'm not in the business of ending relationships None of the commands modify anything, they just read information and dump it into a file. Other than rebooting, your device won't need to go offline. Also, if you HAVE modified your device in terms of ROM or whatever, please include a list of your mods or whatever in the message you send me with the text files zip.
PS> I've visited your area, or at least the one listed with your profile on XDA. It's a beautiful place. If I could get a visa worked out, it's on my list of places in europe I'd love to move to, possibly in retirement
U are planing to get one x720/7?
There are some way beautiful places around in Germany.
Can u maybe help me with my meta-inf?
secXces_debaki said:
U are planing to get one x720/7?
Click to expand...
Click to collapse
I'm giving it some very serious thought. I'm in the US and the x727 will be on sale on wednesday at US$300, which is very compelling for a device with an msm8996pro, even if the camera is average at best, the screen is less than impressive, and it's missing a headphone jack. My G2 is starting to act up and I need something cheap for the short term.
In any case, I'm doing my research now. I've downloaded the ROMs for 17s (both the stock CN version and the modified IT version). The kernel sources are released for x727, and I imagine the x720 kernel can likely be built from the same sources, in fact I wouldn't be surprised if everything about the kernel was the same. So I wanna see if I can get a kernel and rom building. I may attempt a TWRP build first, since I'd want that anyway, and it's simple enough to boot from fastboot and see if things work. But, I need help understanding the system. And that's where the information gathering in this post comes in.
secXces_debaki said:
Can u maybe help me with my meta-inf?
Click to expand...
Click to collapse
I have no idea what you're referring to with the meta-inf.
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
secXces_debaki said:
U got a pm. Hope its good, logcat and logcat-radio was used after i write my pin. Or i need to make it earlier?
Click to expand...
Click to collapse
I would really like the logcat and logcat-radio to be running from the moment just after the hardware logos on the screen start showing up, once EUI starts to boot. The logcat is circular and has a limited buffer. Once it reaches the end of it's buffer, it starts overwriting itself, therefore it only keeps a certain amount of the logs in memory before they're gone. Your logcats were therefore incomplete. In more basic terms, I don't see where the system started booting up, that part of the log had already been overwritten when you took the log.
I also sent you a response requesting additional information, and for you to re-run one of the other commands that also errored out.
I do appreciate the help, I really do, thank you
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
secXces_debaki said:
I guess my meta-inf breaked the baseband, is it even possible?, anywhere else then this my rom based on 17s booted and worked. That's why I asked, I don't have any knowledge for the meta-inf. That's to complicated for me.
When u own a x727 are u maybe able to help me? ^^
Click to expand...
Click to collapse
Yeah, that doesn't help at all. Meta-inf to me is a file included in a flashable zip. It isn't even a main file, and it isn't even particularly important. It certainly wouldn't damage the baseband. The baseband, otherwise known as the modem or radio, controls your phone. It's like the brain stem, it controls the most basic automatic responses. Generally if your radio was broken, your phone would be hard bricked, there would almost certainly be no recovering from that.
Did you flash a modified radio/firmware to your device?
secXces_debaki said:
My personal thoughts about that device.. Are atm really good. The screen is for a fullhd device really good, better then my op3 or Xiaomi mi5/MI max. Also the glass feel much better in typing then any device i had since my Note 3 (nearly owned every Android device who was In any way popular)
The camera is good enough for fast pictures, but that's all, there are way better cameras outside.
The sot is for me atm way to low, if I would use it the whole day I would get around 10h sot or even more, but this device have with the .17 software a big battery drain. With 6h sot on 1 day I loose in deepsleep between 15-25%. The device isn't awake, also there is no wakelock or anything. Strange behavior.
The sound is awesome, u will love it. If u don't need much bass through the loudspeaker.
Finished my short OT ^^
Click to expand...
Click to collapse
Heh, thanks
That actually lines up similarly to other things I've head about the device. Your assessment of the screen seems more positive than some, but then that sorta thing is a bit of personal preference. Frankly I don't game (much) to the point where I want a QHD or 4K display, and I don't intend to do VR. The reason I wanted a msm8996 is for the other advanced capabilities. The thing I'm looking forward to most is getting WiFi Calling working for T-Mobile, my reception isn't always great and that would be fantastic for me
As for the sound, I learned a long time ago to accept disappointment there. And I'm OK with that. I really wanted a headphone jack. Adapters tend to be bulky and/or break, and I don't like to be restricted to a single pair of headphones just because they have the right connector. You also can't easily share headphones with a CDLA connection. I have heard that the speaker output is nice, and I'm looking forward to that.
Mostly I'm excited that the kernel is not much modified from the CAF sources. Once I've verified that whatever it is I'm working on will actually boot, I will be able to upgrade to a newer revision of the kernel (with security fixes) and possibly even jump to the UM branch for the kernel, which is unifying for the Nougat release. I'm using the op3 as a template for my cm device and at the moment just gathering information. I don't even know if I'll buy the device yet or even make a rom. But it's what I'm looking into. This is a side project for me, and I desperately need to find a job, that takes priority.
secXces_debaki said:
Kk I try to be as fast as possible to do the logcats at the moment my pc recognize my phone.
Click to expand...
Click to collapse
I don't know how fast the phone boots, but usually I have the command already typed into the window, then I reboot and as soon as the first logo appears on the screen I hit enter. The command may not see the device immediately, and it'll say "awaiting device" and that's fine, it'll start logging as soon as the device appears. Then do CTRL+C 30 seconds after all the final connections to the cellular network are done
Managed to fix my standby drain..
U got a pm with the last logs. Hope it's good
After returning and exchanging my bricked **Android 11 model while trying to impossibly downgrade to Android 10 to root, I got my hands on a pre-Android 11** unit and was able to successfully root it. My only gripe with it right now is that running apps in landscape mode seems to cause a soft reboot, especially on launch. A characteristic of this is how it happens when the app has barely even filled the screen entirely by the boarder before the ONN logo reappears. Wanted to create a batch script to give me a somewhat decent live logcat output of what's going on, but didn't have the time. Youtube Vanced playback on both Music and Youtube cause a soft reboot on BOTH display orientations. Media playback is OK, SoundCloud only.
TL;DR: Tablet is trigger happy with soft reboots in apps oriented in landscape, making portrait mode the only viable display orientation on my tablet. Oversized smartphone, anyone?
.
Run the following command "adb logcat -v threadtime >logcat.txt" and reproduce the issue
Kenora_I said:
Run the following command "adb logcat -v threadtime >logcat.txt" and reproduce the issue
Click to expand...
Click to collapse
Ran the command and took a long look at the logcat. LSPosed and EdXposed seemed to be likely candidates for causing the problem when hooking onto apps, but disabling them resulted in the same behavior. After flashing the stock boot image + vbmeta, it appeared that Magisk itself was causing the issue. I'm going to look into it further from here.
Looked into it further. Safetynet appears to have a link to these problems.
Fresh logcat after reproducing bug
https://files.catbox.moe/7emoe6.txt
Logcat 2 [note that for reproducing this bug, I am reorienting the screen to landscape before opening FX File. This may or may not be reflected in both logs, assuming there may be some losses for whatever reason]
https://files.catbox.moe/bala2v.txt
.