Related
This thread is meant for (technical) discussion of OT-995, notably ICS-based (e.g. CM9 and AOKP) OS and kernel development.
Any non-technical questions/discussion belong in the general OT-995 thread.
Status quo
There's an ongoing effort bring CM9 and AOKP to the OT-995. Although neither is anywhere near complete, basic functionality (graphics/audio/gsm (non-data)/wifi/sensors) is present.
Both iuss and fonix232 currently maintain Android repositories related to OT-995. A common kernel is maintained by iuss, based on the 2.6.35.11 release by Alcatel.
Updates will likely be posted in this thread, but this topic start may not be fully up-to-date.
Source repositories
kernel: https://github.com/ius/tct_cocktail_kernel
android/bootable/recovery: https://github.com/ius/android_bootable_recovery
android/device/tct/cocktail: https://github.com/ius/android_device_tct_cocktail
(on top of the CM 'ics' branch)
android/device/alcatel/cocktail: https://github.com/fonix232/android_device_alcatel_cocktail
android/vendor/alcatel/cocktail: https://github.com/fonix232/android_vendor_alcatel_cocktail
Flashable releases
fonix232 has provided flashable builds of CM9 and AOKP: http://goo.im/devs/fonix232/OT995/ICS
(Be aware that these might not always be up to date with the repositories listed above)
Other bits of interest
iuss' slightly outdated README for his repositories.
fonix232 said:
Possibly, couldn't really boot yours though :\
Also, some more info about liblights. The tempfix works (keyboard lights up with screen), but apparently when the keyboard file is set in liblights, it won't call the keyboard function. If I set it to e.g. the notification LED, it is called, but bails out with error 13 (no access to notification LED control).
Click to expand...
Click to collapse
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
iuss said:
I just found some spare minutes and had a look at it as well (had to run & was working on writing the topic start for this thread, so I didn't get to posting about it).
It suddenly struck me that there's both a buttons and keyboard light; our virtual keys are buttons, I suppose keyboard is reserved for the backlight of a hardware keyboard.
Alcatel/TCT labeled the buttons backlight 'keyboard-backlight' in kernel, which it isn't.. I've fixed this; now the backlight works as expected. The notification light doesn't work with the CAF/AOSP liblights (different device paths), for now the stock (binary) liblights should work - it probably requires a chmod of the sysfs files in init.rc.
Click to expand...
Click to collapse
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens. I've logged it, every device open, every call of write_int, every device light setting, everything, and keyboard only showed up when:
a, Not the proper keyboard brightness path was given (in my case, it was the notification LED)
b, Moved the keyboard control to the lcd-backlight controller function - as it is currently.
And apparently yes, I've forgot to chown the whole LED folder's content to system
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
handy tool for making logs...
This app runs the following commands:
dmesg
logcat -v time -d
logcat -v time -b radio -d
getprop
uname -a
ps
Click to expand...
Click to collapse
Download : dl.dropbox.com/u/2889810/apps/getlogs_v1.1.apk
Thread : http://forum.xda-developers.com/showthread.php?t=1123129
I do it by hand, but thanks ;D
maby its a good thing to copy the apk to system/app
there will be a lot of people installing the build and then complain here that some stuff dont work (also bugs u didnt even realize they where there cuz u cannot test alone)
and when u ask them for logs some of them dont even know how to do it..
fonix232 said:
That makes sense - however, if you check my files, I've clearly made it so even if it there's a keyboard or buttons device, both calls the keyboard code - what never happens.
Click to expand...
Click to collapse
If I interpreted things right, you mean neither was ever called? If you had wired buttons-to-keyboard it should've worked, the reason why set_keyboard_light was never called is because TCT hacked the Java framework (by making the turn-on-screen-backlight-and-buttons event turn on the keyboard light as well).
Also, our biggest problem is: this LED acts like as a battery/attention/notification LED, while keeping the modes of a trackball - slow pulse, fast pulse, constant on, constant off, and breathe. What would be the best way to approach?
Click to expand...
Click to collapse
The monkey approach - I checked out the code for Nexus; it doesn't provide a battery light at all (which is probably only useful if you have a green/red led); attention and notification are routed to the same led.
The stock liblights seems to work quite well, e.g. notification (sms/mail) causes a blink, attention (USB inserted) a constant light.
Let's just copy stock liblights for now, we can rewrite/reverse it later.
(Just a sidenote: setting the notification LED's brightness to 0 will lead to the crash and reboot of the phone)
Click to expand...
Click to collapse
Good catch. Fixed in my kernel tree (no-op instead of a null fptr call)
iuss, I understand your concerns, and most probably will stick to it, but I've already began writing liblights Actually, it's like, around the fifth revision, fifth try, and still no worky. Just finished up my test-package (ultimate AOKP-CM9 with GApps installer, will post it separately), will test that and check back.
EDIT:
Tried your new kernel, but somehow, wifi fails to connect. DHCP timeouts, etcetera.
Works fine here (and I didn't touch anything related). For reference, a built zImage.
iuss said:
Works fine here (and I didn't touch anything related). For reference, a built zImage.
Click to expand...
Click to collapse
Egh, turns out it was my fault, something frikked up with my installer. Still working on the small quirks tho
Also an idea about BT - why not use the same module that the Galaxy Tab P4 series used? They are all BCM4330, so theoretically it should work!
question is it possible to make 3 point multitouch? (or more?)
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
iuss said:
The controller appears to be able to detect > 2 fingers, but doesn't return data for more than two.
In other news, I pushed a fix to make the ts driver once again support 2 fingers.
Click to expand...
Click to collapse
The 5306 can detect up to 5 distinct touches, but apparently either the chip was locked down to two (or via baseband, and might be unlocked in ICS), or just the communication signal is processed in a wrong way.
But nice addition with the multitouch support!
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
fonix232 said:
EDIT:
First drawback of the stock liblights: the buttons light won't come alive after unlocking the screen, but needs to set the brightness manually. Does not occur if brightness is set to auto.
Click to expand...
Click to collapse
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
iuss said:
Odd. Works just fine for me. I don't see how it's related to brightness either.. (what brightness? screen? I didn't touch it, nor have I any auto-brightness-control related overlay, if that's relevant).
Click to expand...
Click to collapse
I don't see either, but when brightness is on manual, I have to modify the value for the keyboard lights to show up.
Performance issue
I know, my question is maybe premature.
But what about the performance. Do you feel it could be faster than the stock rom?
Maybe some quadrant test would give us some idea?
it feels amazing
I think I might know a way to have 5-point touch, but it won't be easy...
Looking at the source code of the ft5306, you can see that in the firmware upgrade part, it points to a header file: FTS0094P430_CockTail_V1d_20111123_app.h
This header is nothing else, but an actual FT5306 firmware file, dissected into bytes. Basically, they took the hexa code of a binary firmware, and pasted it into a text file byte by byte! Sounds stupid, but actually a good way to integrate a firmware into the kernel.
However, the function can be overwritten so instead it reads bytes from an actual binary firmware file, located on the filesystem. Doing that, plus acquiring a 800*480 FT5306 firmware image (so far I've only found an 1024*600 one) would result in unlocking the whole capacity of the panel!
Also gave a try at the camera HAL. I can't make it work sadly :\
What happens if you write bogus firmware to ft5306, though? :x
The panel will most probably won't work, although the firmwares are pretty similar in all the ft5x06 series.
Aaaalthough, if you reflash a proper firmware, it should work again
Hi there,
I just received my new Mi MIX 2S (actually, I got it 360 hours ago, if you know what I mean...) and I'm very satisfied with this toy
I'm on the last MIUI 10 Global Beta (8.7.5) since this afternoon, with SuperSU v2.82-SR5 and of course, with an unlocked bootloader.
However, I noticed a "strange" glitch/issue when I quick touching/typing.
It's seems that the screen not considering the different touch but acts like it does "two in one" touch.
I made a small video to illustrate the issue :
https://youtu.be/NdW8Zeo1MLQ
Does anyone has this too ?
Do you think it's an hardware or a software issue (like calibrate or touch-delay update) ?
Thanks
lafritte57 said:
Hi there,
I just received my new Mi MIX 2S (actually, I got it 360 hours ago, if you know what I mean...) and I'm very satisfied with this toy
I'm on the last MIUI 10 Global Beta (8.7.5) since this afternoon, with SuperSU v2.82-SR5 and of course, with an unlocked bootloader.
However, I noticed a "strange" glitch/issue when I quick touching/typing.
It's seems that the screen not considering the different touch but acts like it does "two in one" touch.
I made a small video to illustrate the issue :
https://youtu.be/NdW8Zeo1MLQ
Does anyone has this too ?
Do you think it's an hardware or a software issue (like calibrate or touch-delay update) ?
Thanks
Click to expand...
Click to collapse
Hardware issue, I have the same issue.
https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/miui-im-swiping-t3803874
Damn... I bought mine on Joybuy, I'll try to deal with them about the warranty because I guess I can't contact Xiaomi directly.
The XDA Gesture workaround seems to be a good temporary way but, I really don't want to stay on a defective device...
I already did this with my Oneplus One (as a early buyer, I got a similar issue) and it was worst with time, I regret to had never return them
lafritte57 said:
Damn... I bought mine on Joybuy, I'll try to deal with them about the warranty because I guess I can't contact Xiaomi directly.
The XDA Gesture workaround seems to be a good temporary way but, I really don't want to stay on a defective device...
I already did this with my Oneplus One (as a early buyer, I got a similar issue) and it was worst with time, I regret to had never return them
Click to expand...
Click to collapse
Bought mine on Aliexpress, no way I'll get a warranty without me paying $30 of shipping and lose a month without the phone.
I tried the XDA gesture thing, but you can't really get the same gestures as on MIUI (alsway have to make the gestures from the bottom of the phone it seems). So for now I'm just using it with this "bug", with the keyboard closing from time to time when I type.
Probably gonna get a Mi Max 3 to replace it anyway sooner or later.
I just made the thest you did with a drawing app and I got the same results when I multi touched the screen very quickly. I hadn't noticed this earlier because it didn't cause any problem for my daily use. Specifically, in which context did you notice that issue?
hayatesan said:
Bought mine on Aliexpress, no way I'll get a warranty without me paying $30 of shipping and lose a month without the phone.
I tried the XDA gesture thing, but you can't really get the same gestures as on MIUI (alsway have to make the gestures from the bottom of the phone it seems). So for now I'm just using it with this "bug", with the keyboard closing from time to time when I type.
Probably gonna get a Mi Max 3 to replace it anyway sooner or later.
Click to expand...
Click to collapse
I guess JoyBuy has the same warranty policy, which means cost return and more than a month without phone...
I haven't tried the XDA Gesture workaround yet, but I'm not too happy about losing the MIUI gesture
Hope that's JoyBuy will be understanding...
rodaven said:
I just made the thest you did with a drawing app and I got the same results when I multi touched the screen very quickly. I hadn't noticed this earlier because it didn't cause any problem for my daily use. Specifically, in which context did you notice that issue?
Click to expand...
Click to collapse
Thanks for your test and your answer.
In my case, it's very annoying when I (fast) typing a message, it causes a "fake" swipe and recude the keyboard or go back to home screen. I'll try to make a better screencast to show you in-use case.
lafritte57 said:
I guess JoyBuy has the same warranty policy, which means cost return and more than a month without phone...
I haven't tried the XDA Gesture workaround yet, but I'm not too happy about losing the MIUI gesture
Hope that's JoyBuy will be understanding...
Thanks for your test and your answer.
In my case, it's very annoying when I (fast) typing a message, it causes a "fake" swipe and recude the keyboard or go back to home screen. I'll try to make a better screencast to show you in-use case.
Click to expand...
Click to collapse
Fine, I'll tell you my experience. I use to had the same problem, it's only noticeable using the keyboard and specially when you tap the letters located near the edge of the screen, specially like the Q and P. I'm almost completely sure that the problem is related to gestures, because the system thinks you're swiping, in my case I got some lag too in addition to the false back gesture. What I did to fix this is use the keyboard (Google keyboard) in one hand mode (long press the "," and this option will pop up next to the emoticon) and moving it to the center and the problem is gone. It's actually more comfortable this way because the space bar moves up and it's more accessible. You can play then with the keyboard size if you think it's too small. There are two others threads talking about the same problem and I recommended this solution in both, and it seems to work for others too. Try it and tell us.
https://forum.xda-developers.com/showpost.php?p=76789600&postcount=13
I have this issue too, are you sure it's a hardware problem and it does not affect everybody?
Thank you.
stark0 said:
I have this issue too, are you sure it's a hardware problem and it does not affect everybody?
Thank you.
Click to expand...
Click to collapse
Hi,
Actually, I think it's more an OS issue than an hardware one.
After some tries and research, I noticed that these "screen glitches" are bad interpretations of fast multitouching, translate into swipe/gesture.
These swipe/gesture come with the gesture navigation mode, included in full-screen desplay (and which allow to hide the bottom navigation bar).
If you re-enable the "classic" display, with the bottom bar, the issue doesn't seem to exist. So, I guess for MIUI, some fast-typing/touching are interpreted as gestures (swipe down-to-up = home, left-to-right = previous...)
In the same registry, I noticed that, if you use a scrollable widget (Google Agenda in planning display) and if you scroll down on it (in order to see the bottom lines for example), MIUI interpret it as a down-to-up gesture (and so, go back to home, or search).
So, I really hope that in a future update, the sensibility of these gestures could be decreased/improved...
For now, you could :
Enable the one-hand mode ok Google Keyboard as proposed by @rodaven (but personnaly, I dislike the fact to have a small keyboard with a lot of lost space around it...)
Disable the full sceen display mode (and so, say goodbye to the gestures feature)
Stay on full screen mode and gestures, get upset when you write a message and pray for un update
lafritte57 said:
Hi,
Actually, I think it's more an OS issue than an hardware one.
After some tries and research, I noticed that these "screen glitches" are bad interpretations of fast multitouching, translate into swipe/gesture.
These swipe/gesture come with the gesture navigation mode, included in full-screen desplay (and which allow to hide the bottom navigation bar).
If you re-enable the "classic" display, with the bottom bar, the issue doesn't seem to exist. So, I guess for MIUI, some fast-typing/touching are interpreted as gestures (swipe down-to-up = home, left-to-right = previous...)
In the same registry, I noticed that, if you use a scrollable widget (Google Agenda in planning display) and if you scroll down on it (in order to see the bottom lines for example), MIUI interpret it as a down-to-up gesture (and so, go back to home, or search).
So, I really hope that in a future update, the sensibility of these gestures could be decreased/improved...
For now, you could :
Enable the one-hand mode ok Google Keyboard as proposed by @rodaven (but personnaly, I dislike the fact to have a small keyboard with a lot of lost space around it...)
Disable the full sceen display mode (and so, say goodbye to the gestures feature)
Stay on full screen mode and gestures, get upset when you write a message and pray for un update
Click to expand...
Click to collapse
Thank you so much!
I have the gestures disabled because of that but it still happens in the keyboard (I don't like the one-hand mode). So, we need to wait hoping it'll be solved.
stark0 said:
Thank you so much!
I have the gestures disabled because of that but it still happens in the keyboard (I don't like the one-hand mode). So, we need to wait hoping it'll be solved.
Click to expand...
Click to collapse
I just found that this issue was submit on MIUI website in January : http://en.miui.com/thread-1539964-1-1.html
lafritte57 said:
I just found that this issue was submit on MIUI website in January : http://en.miui.com/thread-1539964-1-1.html
Click to expand...
Click to collapse
But that's different from the multitouch issue that is in the main post (https://www.youtube.com/watch?v=NdW8Zeo1MLQ&feature=youtu.be), isn't it?
stark0 said:
But that's different from the multitouch issue that is in the main post (https://www.youtube.com/watch?v=NdW8Zeo1MLQ&feature=youtu.be), isn't it?
Click to expand...
Click to collapse
In my opinion, it's the same issue.
Due to the full screen/gesture feature, fast multitouches are interpreted as a gesture.
On my video, you could see it.
On the issue from MIUI website, users asked that swipe/gesture are disable over keyboard when it's on-screen.
I think it should be a solution to combine gesture navigation and fast multitouch/type.
Personnaly, I disable full screen/gesture navigation (for now, sadly) and the issue desappear, that's why I'm pretty sure it's a software issue (which concern very model with this feature).
I changed my screen
Actually i cracked my screen and replaced new lcd from aliexpress claimed original. I checked it is JDI. But the touch issues still persist. I think its xiaomi driver.. or i dont know.. i really regret having this phone
lafritte57 said:
In my opinion, it's the same issue.
Due to the full screen/gesture feature, fast multitouches are interpreted as a gesture.
On my video, you could see it.
On the issue from MIUI website, users asked that swipe/gesture are disable over keyboard when it's on-screen.
I think it should be a solution to combine gesture navigation and fast multitouch/type.
Personnaly, I disable full screen/gesture navigation (for now, sadly) and the issue desappear, that's why I'm pretty sure it's a software issue (which concern very model with this feature).
Click to expand...
Click to collapse
I tested more, disabling fulls creen gestures and the problem persist. There is a video with the keyboard trying to type "alguna", sometimes it makes a gesture "left to right":
https://www.youtube.com/watch?v=N8EgUfaN5C0
It's very disapointing, I had touch screen problems with my oneplus one and now with the mix 2s.
I've noticed the touchscreen is a little bit slow/lazy when I activate navigation gestures.
The lazy response area is only on the bottom-left of the display, and it concerns only the "A" letter of my qwerty keyboard (a very small area).
This lazy response of the touchscreen is on all other apps, not only in the keyboard, and it concerns only that small area.
If I use navigation buttons, the problem disappear.
I don't know if this issue was present also in previous OS version because I've tried using navigation gestures today
I've the Nex S 8/256GB, PD1805_A_1.17.10
Anyone noticed this?
Exactly the same here...
Sorry for this (maybe too) late answer: Have exactly the same issue. I'm used to write really fast on my phone, but since having the Vivo Nex, I'm slowed down extreamly because of this. Also for me just the "A" letter is the problem. Doesn't matter which keyboard or size (tried several), it's always laggy...
I really hoped this would be a thing of the past after the newest "Funtouch-update" from some days ago, as they've been writing about "better touchscreen accuracy" in the changelog... But nobchanges at all concerning this point...
Did anyone already found a solution against this, without having to turn on those ugly navigation buttons on the bottom of the screen? I really like the three swiping gestures.
Same on my side
Seems as my previous post has been deleted / went lost...
I've exactly the same problem here with the "A" key of the keyboard being really slow on my Vivo Nex S (256GB, global version). Hoped this problem would fade away after the newest "Funtouch" update 3 days ago, because they wanted to have solved exactly this problem, what Vivo told us in the changelog...
But all kept the same. Tried already three different keyboards with different settings, no success. Does someone has a solution for this?
But I really DON'T like having the navigation buttons visible, so this is no option for me. I definitely want to use the original slide actions for the three buttons below the screen...
To be honest: I'm using the Nova Launcher over the Funtouch System (the Funtouch launcher is absolutely useless). Could this have an influence?
This happends to me too.It seems there s area down to the bottom of screen is not sensitive enough.
I have vivo 1805 which is Taiwan version, not sure if this model same as the global version. And I also try to flash the chinese version ROM but failed cause of the signature difference. The update progress in Taiwan is not as fast as chinese. Hope VIVO in Taiwan could release the fix soon.
guagin said:
This happends to me too.It seems there s area down to the bottom of screen is not sensitive enough.
Click to expand...
Click to collapse
Well, not sure if this is the same issue on my device, as the sensitivity seems to be ok on mine, but I have to push the "a" button much longer (not stronger) than all others. So just a laggy key... And REALLY annoying!
But "good" to hear that others seem to have comparable problems. If there just finally would be a fix for this on the Vivo phones...?
Hey guys. I have been facing the same issue and started experimenting with navigation replacements. So as you guys realize, sensitivity is just fine when using the nav buttons but there are a lot of keyboard mistypes when using Vivo's own navigation gestures.
Therefore, after expermintation, I can confirm that the app called "Fluid Navigation" is an awesome replacement for the navigtion gestures. XDA Navigation gestures is slightly incompatible with the Nex. But Fluid Navigation works perfect.
So all you need to do is follow these steps
1, Switch to Nav buttons
2, Install the app
3, Grant accessibility permission
4, Grant Write Secure Settings through ADB. The app gives instructions for this
5, Hide the nav bar through the app
6, Customize the gestures in the app. It even allows quick settings swipe up.
Hope this helps. Enjoy guys. You will definitely feel the difference
manu_up said:
Hey guys. I have been facing the same issue and started experimenting with navigation replacements. So as you guys realize, sensitivity is just fine when using the nav buttons but there are a lot of keyboard mistypes when using Vivo's own navigation gestures.
Therefore, after expermintation, I can confirm that the app called "Fluid Navigation" is an awesome replacement for the navigtion gestures. XDA Navigation gestures is slightly incompatible with the Nex. But Fluid Navigation works perfect.
So all you need to do is follow these steps
1, Switch to Nav buttons
2, Install the app
3, Grant accessibility permission
4, Grant Write Secure Settings through ADB. The app gives instructions for this
5, Hide the nav bar through the app
6, Customize the gestures in the app. It even allows quick settings swipe up.
Hope this helps. Enjoy guys. You will definitely feel the difference
Click to expand...
Click to collapse
Thank you for this awesome information, now i have no lag anymore and i can write fast!
Happy to have helped
My 1st smartphone was a Palm Pre Plus (webOS), I got an Android next but Went back to WebOS with an HP Veer. ... Really liked how they implemented gestures properly a DECADE before anyone else. Was using Moto phones for nearly 8 years, really loved the Active Display & Moto Actions (camera flip & chop chop flashlight).
With my Moto Z2 Force dying and Moto basically making garbage or something ridiculously overpriced *cough*RAZR*cough* ... had to look elsewhere.
Got a Pixel 5 a few days ago. I hadn't experienced Android 9 or 10, so 11 is a bit step up from Oreo.
Always on display is pretty cool, not as good as Active Display, but better than the old Ambient Display.
Double tap power button to launch camera will work, although not as cool as flipping (I know 3rd party apps exist to mimic gestures, but I'm trying to keep phone as clean as possible for endurance)
Fluid Navigation Gestures can mimic proper Navigation - I'm sorry but the built in Pixel Navigation needs a lot of work. The Swipe up and hold for recent apps is very frustrating to use.
(Here is a solution to removing the 3 button Nav bar on Android 11 with terminal: https://www.reddit.com/r/Android/comments/irs1eb/hiding_the_3_dot_navigation_bar_on_android_11_root/)
(For reference, I disabled the left swipe bar. Kept the right swipe as a back button [the one idea I like of Google's], Right Swipe bottom edge -> Recent apps; Left Swipe bottom edge -> Back; Swipe up bottom edge -> Home [Just as it was on WebOS and Moto One Touch Nav]
Various Apps allow for "chop chop" for flashlight. Still testing which one is the best solution.
And Many thanks to @Tulsadiver For his work on the ancient 3Minit app to work with Pixel 5 /4a etc. https://forum.xda-developers.com/pixel-5/themes/3minit-battery-3minit-clock-t4177835 He also has a flashable Magisk module to remove Nav bar https://forum.xda-developers.com/pixel-5/themes/clock-mods-remove-navbar-mod-t4177829
With those mods, Battery can be changed to similar to Gravitybox Ring battery style and clock can be moved to center or right (the left clock is very annoying).
Just sharing a few things I've come across many different places. Some of this really just writing here for myself for memory and sharing if it'll be helpful for anyone else.
Cheers!
I bought a cheap Moto G7 Power and realized how much I deeply missed some of Moto's little tweaks. Chop and twist are big ones that I miss constantly. Still trying to get an app that implements it half as well. I'd really, really love if we could get a ring battery indicator around the hole punch to reclaim lost space and move the clock. Another killer feature that the Moto had me convinced was just another part of Android was scrolling screenshots. Deeply disappointed when I went to use it on the Pixel with a newer OS and it was missing.
Why are you finding the swipe up hard to use?
Sent from my Pixel 5 using Tapatalk
somnambulantdead said:
I bought a cheap Moto G7 Power and realized how much I deeply missed some of Moto's little tweaks. Chop and twist are big ones that I miss constantly. Still trying to get an app that implements it half as well. I'd really, really love if we could get a ring battery indicator around the hole punch to reclaim lost space and move the clock. Another killer feature that the Moto had me convinced was just another part of Android was scrolling screenshots. Deeply disappointed when I went to use it on the Pixel with a newer OS and it was missing.
Click to expand...
Click to collapse
Yeah I hear ya. The Active Display / Moto Display was great too. At least on the Moto X / X2, after that it wasnt as good but still better than what any other manufacturer has developed.
I've seen the app "energy ring" which does this, but the dev hasn't added support for Pixel 5 yet (it's been added for Pixel 4a, so I'm hoping support will come soon).
With Magisk and tweaks by Tulsadiver, the clock can be moved to the right, it looks much better.
Davey Dual Sim said:
Why are you finding the swipe up hard to use?
Sent from my Pixel 5 using Tapatalk
Click to expand...
Click to collapse
The swipe up is fine, it's the swipe up + HOLD that bothers me. doesn't feel fluid or natural. One motion should control one action only.
roweboat56 said:
The swipe up is fine, it's the swipe up + HOLD that bothers me. doesn't feel fluid or natural. One motion should control one action only.
Click to expand...
Click to collapse
Interesting, I'm finding it one movement , move up from bottom, then the hold is less than s second
Sent from my Pixel 5 using Tapatalk
roweboat56 said:
The swipe up is fine, it's the swipe up + HOLD that bothers me. doesn't feel fluid or natural. One motion should control one action only.
Click to expand...
Click to collapse
If you swipe up from the bottom about ½cm you don't need to do the hold action. It automatically loads the recent apps screen for me. Any higher and it'll take you back to the home screen without holding.
I just use Button Mapper to turn my volume button into a flashlight toggle when the screen is off. Much faster and works more often than the chop gesture. You can customize other stuff too wtih it. A nice all-in-one app.
Hi people, am currently waiting for bootloader unlock, am trying to sort things out and see how am gonna use my new rooted phone Xiaomi Redmi Note 9 Pro (got it as gift), well phone is great, but am coming from old era where rounded corners and notch was not a thing, i still prefeer screens with rectangle shape, and am willing to sacriface lower portion of screen up to ending of rounded corner and same above till the camera module, so i can have nice rectangular screen
Now my question is how to?
How to change screen size? (how to measure where to start and end)
If by software rounded corners still exist how to remove them?
Am planing to flash xiaomi.eu rom (am considering Ressurection Remix) and magisk root.
Thank you great people and community.
It's simple, and can be done without rooting, connect with ADB.
So your device has 1080x2400 resolution, you'll have to lower numbers from the height (2400) in order to get a rectangular display.
Play with numbers till you get it right, commands to use:
adb shell
wm size 1080x2200
Mohamedkam000 said:
It's simple, and can be done without rooting, connect with ADB.
So your device has 1080x2400 resolution, you'll have to lower numbers from the height (2400) in order to get a rectangular display.
Play with numbers till you get it right, commands to use:
adb shell
wm size 1080x2200
Click to expand...
Click to collapse
Thank you very much, i will check it out once i got bootloader unlock since am waiting 168h on Xiaomi devices, i will not fiddle with anything so i dont mess something up
And about software rounding, since when in settings i choose option to hide notch and move status bar down, it hides a notch and its completley disabled part of screen, but it still gets a rounded corners by software, i will try this with option dont hide anything maybe then under hardware display is rectangular, but you never know i will let you know , but if it is software how can i find it on my device, since i googled and found something for Pixel devices, and its all diffrent, thank you alot.
And what about DPI , or resolution after that change, should i keep everything as it is
essen33 said:
Thank you very much, i will check it out once i got bootloader unlock since am waiting 168h on Xiaomi devices, i will not fiddle with anything so i dont mess something up
And about software rounding, since when in settings i choose option to hide notch and move status bar down, it hides a notch and its completley disabled part of screen, but it still gets a rounded corners by software, i will try this with option dont hide anything maybe then under hardware display is rectangular, but you never know i will let you know , but if it is software how can i find it on my device, since i googled and found something for Pixel devices, and its all diffrent, thank you alot.
And what about DPI , or resolution after that change, should i keep everything as it is
Click to expand...
Click to collapse
Hiding notch ain't that effective, and you lose some of your screen doing so.
Your screen is a rounded AMOLED, that's hardware, it also has software roundness in order to be compatible with your screen. It's not that hard to disable roundness, for hardware, you can overcome it by "wm size", and you can change DPI by: "wm density xxx" to your desired value.
The software overcoming needs APK editing, so you need a PC/Laptop. You need to edit framework-res.apk (and maybe SystemUI.apk). There's an app that allows you to edit framework-res.apk values directly, you may want to check it:
Privset.
Mohamedkam000 said:
Hiding notch ain't that effective, and you lose some of your screen doing so.
Your screen is a rounded AMOLED, that's hardware, it also has software roundness in order to be compatible with your screen. It's not that hard to disable roundness, for hardware, you can overcome it by "wm size", and you can change DPI by: "wm density xxx" to your desired value.
The software overcoming needs APK editing, so you need a PC/Laptop. You need to edit framework-res.apk (and maybe SystemUI.apk). There's an app that allows you to edit framework-res.apk values directly, you may want to check it:
Privset.
Click to expand...
Click to collapse
Thank you, its actually LCD, on Redmi note 9 pro, Thank you for commands above, when i screenshot something it appears rectangle, so in theory it should work and rounded edges should not be there
Well for that APK stuff, does installing custom ROM help in that? I was thinking about RR rom,
Also, i dont mind losing screen size, and for me hiding notch is a must doing it this way, personally i hate it, i hate rounded edges, i just hate it my heart hurts when i see it, i got this phone as gift so i need to appreciate it i cant sell/replace it that way its kinda disrespectful
essen33 said:
Thank you, its actually LCD, on Redmi note 9 pro, Thank you for commands above, when i screenshot something it appears rectangle, so in theory it should work and rounded edges should not be there
Well for that APK stuff, does installing custom ROM help in that? I was thinking about RR rom,
Also, i dont mind losing screen size, and for me hiding notch is a must doing it this way, personally i hate it, i hate rounded edges, i just hate it my heart hurts when i see it, i got this phone as gift so i need to appreciate it i cant sell/replace it that way its kinda disrespectful
Click to expand...
Click to collapse
Oh sorry, I assumed it being a budget killer to offer an AMOLED display similar to RN10.
Well .. having LCD makes it a bit different, as the parts you cut off from your display will keep lightening up, that's how LCD displays work.
Honestly, you'll hate it more, it'll be like watching a long video on YouTube without fullscreen mode.
Strange tradition you've got right there, here, we're more understanding, if someone gifted you a phone, it won't matter if you sold it or replaced it, what matters is the feelings you've grown out of his gift.
About the APK stuff, it can be done on any ROM, but it's more stable on AOSP-based ROMs like RR, Havoc, PE, ...
An easy way to achieve your goal would be to use adb wm size, and reduce height. (There's another thing to do, adjust the new touch positions; cause your phone will keep using old positions, so if you're using gestures, it won't work that simple, till you recalculate it. (Easy to solve).
Mohamedkam000 said:
Oh sorry, I assumed it being a budget killer to offer an AMOLED display similar to RN10.
Well .. having LCD makes it a bit different, as the parts you cut off from your display will keep lightening up, that's how LCD displays work.
Honestly, you'll hate it more, it'll be like watching a long video on YouTube without fullscreen mode.
Strange tradition you've got right there, here, we're more understanding, if someone gifted you a phone, it won't matter if you sold it or replaced it, what matters is the feelings you've grown out of his gift.
About the APK stuff, it can be done on any ROM, but it's more stable on AOSP-based ROMs like RR, Havoc, PE, ...
An easy way to achieve your goal would be to use adb wm size, and reduce height. (There's another thing to do, adjust the new touch positions; cause your phone will keep using old positions, so if you're using gestures, it won't work that simple, till you recalculate it. (Easy to solve).
Click to expand...
Click to collapse
Well its a family gift so if i sell it it would be toxic "you didnt like my gift" , iam about to flash RR, so i will look into that, i dont mind having background light on unused part of screen, well how if you dont mind, your tips on recalculating touch positions, i found some googling around, what you recommend, thanks alot
essen33 said:
Well its a family gift so if i sell it it would be toxic "you didnt like my gift" , iam about to flash RR, so i will look into that, i dont mind having background light on unused part of screen, well how if you dont mind, your tips on recalculating touch positions, i found some googling around, what you recommend, thanks alot
Click to expand...
Click to collapse
Okay, so a year ago, I had Galaxy S7 that got some water issues, so the bottom part of screen wasn't working, and I was using on-screen navigation bar, so I used ADB wm commands to make the phone usable until it dries up.
What I did was, reducing screen height up to the usable part. Then, I used: adb wm overscan command.
This command tells the system where is the screen end, whether at top, bottom, right, or left. So if your bottom screen is reduced by 2 cm, you'll have to tell your system about that, so that it don't assume it's still at the actual hardware values.
The command uses numbered values separated by commas like this (original values):
wm overscan 0,0,0,0
The numbers are organised LEFT,TOP,RIGHT,BOTTOM
You can use minus too, I honestly don't remember which numbers were suitable for my case, you'll have to check it on your own (won't take over 10 minutes). Only change TOP & BOTTOM values.
Who knows, maybe you won't need to do this anymore, perhaps Android 11's AI does that automatically whenever changing screen resolution.
Mohamedkam000 said:
Okay, so a year ago, I had Galaxy S7 that got some water issues, so the bottom part of screen wasn't working, and I was using on-screen navigation bar, so I used ADB wm commands to make the phone usable until it dries up.
What I did was, reducing screen height up to the usable part. Then, I used: adb wm overscan command.
This command tells the system where is the screen end, whether at top, bottom, right, or left. So if your bottom screen is reduced by 2 cm, you'll have to tell your system about that, so that it don't assume it's still at the actual hardware values.
The command uses numbered values separated by commas like this (original values):
wm overscan 0,0,0,0
The numbers are organised LEFT,TOP,RIGHT,BOTTOM
You can use minus too, I honestly don't remember which numbers were suitable for my case, you'll have to check it on your own (won't take over 10 minutes). Only change TOP & BOTTOM values.
Who knows, maybe you won't need to do this anymore, perhaps Android 11's AI does that automatically whenever changing screen resolution.
Click to expand...
Click to collapse
Thanks alot i managed to set it up, very helpfull
essen33 said:
Thanks alot i managed to set it up, very helpfull
Click to expand...
Click to collapse
Glad I could help.
Hello, I have a problem and a question with him. When I install a custom rom and lower the resolution, despite using the notch bar killer, a notch remains that got bigger and I can't delete them, also when I put the dark mode it becomes white