Hello,
I'm looking for a g-sensor disabled kernel.
Kernel developers, please make a gsensor disabled kernel, i don't need it, i don't use it.
It causes screen freezing.
To prove it, you can download this sensors application.
http://www.appbrain.com/app/com.julian.apps.Sensors
Run it and rotate/shake/etc. your HD2 rapidly. Screen will freeze and sensor graph on app will stop.
-----------------------
Edit:
Shadiku has released a g-sensor disabled kernel:
The freeze problem has totally gone, but of course g-sensor does not work.
shadiku said:
Okay, I've been wanting to do this ever since I got my HD2. (which was 8 days ago.)
This is a G-Sensor disabled kernel built on the latest git commit (Sat, 28 Aug 2010 17:37:26)
As far as I can tell there are no freezes and the G-Sensor does not work at all.
http://shadiku.com/65aefbaeb0c858941e63f619034d1d407705c674/build.zip
Replace your zImage with the one in the ZIP file, push WiFi and tunneling modules and Enjoy!
Click to expand...
Click to collapse
xmRipper said:
Hello,
I'm looking for a g-sensor disabled kernel.
Kernel developers, please make a gsensor disabled kernel, i don't need it, i don't use it.
It causes screen freezing.
To prove it, you can download this sensors application.
http://www.appbrain.com/app/com.julian.apps.Sensors
Run it and rotate/shake/etc. your HD2 rapidly. Screen will freeze and sensor graph on app will stop.
Click to expand...
Click to collapse
why not to wish for a fixed kernal istead of removing the option from the device , many of us is using the g sensor
hoss_n2 said:
why not to wish for a fixed kernal istead of removing the option from the device , many of us is using the g sensor
Click to expand...
Click to collapse
I mean it should be disabled until it is fixed -_-'
You can disbale it urself right? Just put auto rotate off.
Disabling auto-rotate won't disable the g-sensor.
It won't solve the screen freeze problem.
I want g-sensor driver totaly disabled.
if it is disabled, no1 can test it so how will the devs know they have got it working?
unless u intend for the devs to keep trying it themselves with no help from fellow hd2 users... :-/
I can reproduce the problem easily just in a second.
This is enough to solve the problem for developers. They couldn't expect any more information from us about this issue.
errm.. so, did u send in a kernel log to the devs?
xmRipper said:
Hello,
I'm looking for a g-sensor disabled kernel.
Kernel developers, please make a gsensor disabled kernel, i don't need it, i don't use it.
Click to expand...
Click to collapse
Very nice attitude...
i don't need it, i don't use it
Click to expand...
Click to collapse
And how should I play "Hyper Jump" or "Fall Down"?
Or how should I play "Teeter"???
Maybe you will build me a box of wood, with holes and a marble (but a steel one, I want the feedback when the marble hits the walls).
And I want several levels, so if you are not able to build that in one box, so you have to make several boxed, one for each level...
xmRipper said:
It causes screen freezing.
To prove it, you can download this sensors application.
http://www.appbrain.com/app/com.julian.apps.Sensors
Run it and rotate/shake/etc. your HD2 rapidly. Screen will freeze and sensor graph on app will stop.
Click to expand...
Click to collapse
You are a little bit out of date, huh?
This is known since a while
xmRipper said:
I can reproduce the problem easily just in a second.
This is enough to solve the problem for developers. They couldn't expect any more information from us about this issue.
Click to expand...
Click to collapse
Hey... Wake up... They do this in their spare time...
You (and I and the rest of us) are not able to give them enaugh help to solve that problem. Or why do you think one of the main problems are not solved?
Yeah... Really nice... And you guys from turkey are wondering why many germans don't like peoples like you?
You're acting like a little child...
I'm waiting for the day one of the main developers say that he won't work further on this project because we are not showing enaugh repect to their efforts.
I am not able to write software in C or C# or whatever they use...
I am only an AutoIt "script kiddie"...
So I have try to solve the problems my way (and it seems to work).
Take a look at the GIT shortlog. The part "htcleo: fixed AC charging problems" is a result of my efforts to fix that problem... I've write an E-Mail to Markinus with my detailed observations and how I fixed it temporarily. And a few minutes later he found a mistake in the source and released his changes...
I don't say "disanle the AC charging" (because it was working via USB)...
Maybe you should work a little bit more on the G-Sensor problem...
Try to disable the G-Sensor in Windows (its possible), play with the polling intervals. Maybe there are also some values in Android to change the polling interval to the G-Sensor and report your results... Maybe its to high or to low and that causes the problems...
I don't know it either... But you won't die on some attempts...
Crusoe86 said:
Very nice attitude...
And how should I play "Hyper Jump" or "Fall Down"?
Or how should I play "Teeter"???
Maybe you will build me a box of wood, with holes and a marble (but a steel one, I want the feedback when the marble hits the walls).
And I want several levels, so if you are not able to build that in one box, so you have to make several boxed, one for each level...
Click to expand...
Click to collapse
You can play by using G-Sensor enabled kernel.
For the people who won't use g-sensor, there should be disabled kernel.
Got it? This is not hard to understand.
Making g-sensor disabled kernel couldn't be too hard for developers.
Crusoe86 said:
You are a little bit out of date, huh?
This is known since a while
Click to expand...
Click to collapse
Open your eyes. I still see some poeple come up with different theories on this issue ...
Crusoe86 said:
Hey... Wake up... They do this in their spare time...
You (and I and the rest of us) are not able to give them enaugh help to solve that problem. Or why do you think one of the main problems are not solved?
Click to expand...
Click to collapse
I know they do this in their spare time, so that I'm not asking for when this problem will be solved, I'm asking for a workaround.
xmRipper said:
You can play by using G-Sensor enabled kernel.
For the people who won't use g-sensor, there should be disabled kernel.
Got it? This is not hard to understand.
Making g-sensor disabled kernel couldn't be too hard for developers.
Click to expand...
Click to collapse
And what is when everybody use a G-Sensor disabled Kernel?
Who will then find out the issue of the freezing digitizer?
xmRipper said:
Open your eyes. I still see some poeple come up with different theories on this issue ...
Click to expand...
Click to collapse
Yeah... And several years before some people claim the earth is flat like a Lahmacun...
The problem is the G-Sensor... Basta... If it's not, then it will be ordered (I love the army )
xmRipper said:
I know they do this in their spare time, so that I'm not asking for when this problem will be solved, I'm asking for a workaround.
Click to expand...
Click to collapse
Workarounds on mass
Hey OP, your point is moot. I use a kernel from michyprima, and have not experienced freezes in a long time. I've disabled autorotation cause I don't like it, yet I play many games (Abduction, NFS Shift, Labyrinth ...) which use it.
The only problem is that the g-sensor can't be calibrated, and is off by 10 degrees or so.
For the record, my base is kwbr 4.1 COM3 WinMo + darkstone's HD2Froyo 2.1. I just copied in the new kernel files (root, zImage and modules).
I also use kernel from michyprima, I disabled autorotate, calibrated in WINMO, but always when I walk, the HD2 just don't react, which is very annoying. It also seems, that the CPU load is very high when this happens - which can lead to poor battery life.
Don't take this as a complain, as I know the developers are doing their best to fix this.
I'm prepared to test a new kernel as soon as it is out..., but in the mean time I would be thankful for a kernel with the disabled G-sensor.
Crusoe86 said:
And what is when everybody use a G-Sensor disabled Kernel?
Who will then find out the issue of the freezing digitizer?
Click to expand...
Click to collapse
You should read previous posts in this topic. I answered same question.
xmRipper said:
I can reproduce the problem easily just in a second.
This is enough to solve the problem for developers. They couldn't expect any more information from us about this issue.
Click to expand...
Click to collapse
--------------------
Crusoe86 said:
Yeah... And several years before some people claim the earth is flat like a Lahmacun...
The problem is the G-Sensor... Basta... If it's not, then it will be ordered (I love the army )
Click to expand...
Click to collapse
Read the two posts above. As I said, Some people still claim different things about this issue.
--------------------
Crusoe86 said:
Workarounds on mass
Click to expand...
Click to collapse
Disabling g-sensor from kernel drivers is exact solution.
xmRipper said:
Disabling g-sensor from kernel drivers is exact solution.
Click to expand...
Click to collapse
Then you should write and compile your own kernel
I would do if I could, that's what I'm asking for from developers on this topic.
look, if the g-sensor is disabled, no one will get to test it, and it will never EVER be fixed because NO ONE will feedback to the devs where, when and how did the freeze occured..
It is g sensor problem for sure ,nothing else ,I have been two weeks testing different procedures and apps and it is for sure the g sensor problem ,I don,t know how it is related to the digitized ,but it is the cause of freezes. By the way disabling auto rotate doesn't disable g sensor ,it only disabled the auto rotate function not the g sensor
Sent from my HTC using XDA App
2.6.32.9-38168-g65aefba-dirty [[email protected]] #3
Link removed due to my inability to keep up with new releases and instability.
I recommend you use some new found workarounds, I prefer.
Code:
su
rm -rf /system/lib/hw/sensors*
Oh god finally somebody has understood me
Thank you very much shadiku, I'm going to try this right now.
Related
was that godawful multitouch bug fixed in 2.3.4?
How many fingers are allowed in 2.3.4 without hacking?
thx
only 2 show up for me
The multitouch bug, wasnt a bug..
It is a code that "detects" rain drops..
The best thing they have to do, is to make a "game mode", that if you activated it, disable this function..
If somebody request this in official moto forums, they may implement it..
Paschalis said:
The multitouch bug, wasnt a bug..
It is a code that "detects" rain drops..
The best thing they have to do, is to make a "game mode", that if you activated it, disable this function..
If somebody request this in official moto forums, they may implement it..
Click to expand...
Click to collapse
This would be the absolute most appropriate thing to do. Throw it in one of the Settings sub-menus for those who wish to disable it. It's a great idea in theory but for gamers it may not be the most suitable route to take.
Great idea.
i have never encountered the multitouch or the fingerprint scanner bugs. then again i dont play games on my atrix
bongd said:
This would be the absolute most appropriate thing to do. Throw it in one of the Settings sub-menus for those who wish to disable it. It's a great idea in theory but for gamers it may not be the most suitable route to take.
Great idea.
Click to expand...
Click to collapse
Thinking of it, on programmers view, its very easy to implement.. Its only one flag..
Why dont somebody suggest this on Motorolla's official forums?
Also, the best would be(and more complicate) to have an algorithm to detect when a game is beeing played(eg mobile app went on full screen), ask the user if he wants to change to "game mode".
slade, its a bug, that appears when you hold your finger in the same position for some seconds(i think > 10 secs)
Did a quick search in the forums, and this seems to be the most recent topic.
I would like to know if there's any progress with this issue.
This "feature" is a pain. I can't play any racing game on my emus.
so how do i stop the bloody google maps running in the background? It keeps popping up again in my end task manager.
I don't want to uninstall it.
irishmoe said:
so how do i stop the bloody google maps running in the background? It keeps popping up again in my end task manager.
I don't want to uninstall it.
Click to expand...
Click to collapse
I keep my GPS turned of when I'm not using it, and Google Maps is never running in the background.
Do you use Google Latitude or have any maps/latitude widgets on screen? those will cause this activity.
Nova5 said:
Do you use Google Latitude or have any maps/latitude widgets on screen? those will cause this activity.
Click to expand...
Click to collapse
Have latitude but never use it and no widgets or the like
kjy2010 said:
I keep my GPS turned of when I'm not using it, and Google Maps is never running in the background.
Click to expand...
Click to collapse
Mine is always off too
irishmoe said:
Mine is always off too
Click to expand...
Click to collapse
No idea then Moe, sorry. It never shows in my running services unless I have my GPS turned on and actually running MAPS.
kjy2010 said:
No idea then Moe, sorry. It never shows in my running services unless I have my GPS turned on and actually running MAPS.
Click to expand...
Click to collapse
Yeah it's a pain in the feckin arse!
irishmoe said:
Yeah it's a pain in the feckin arse!
Click to expand...
Click to collapse
When I cooked my ROM, I took everything out that ran in the background that I never used;
Clearfi, Media Server, etc. but never touched anything related to GPS, or maps, so I have no idea why it wouldn't be running on mine, and running on yours. Which version of HC are you running?
I'm running taboonay and richardtrip's kernel
irishmoe said:
I'm running taboonay and richardtrip's kernel
Click to expand...
Click to collapse
Ahhhhh there's no telling then lol
Send them PMs and see if you can get an answer that way.
so how do i stop the bloody google maps running in the background? It keeps popping up again in my end task manager.<br />
<br />
I don't want to uninstall it.
Click to expand...
Click to collapse
Use system tuner pro and freeze any app.it won't run again until you boil it.
I think that the maps service will run if you have 'shared your location' with the browser or other apps that use maps for location specific information. This can be switched on in Settings -> location and security.
josinpaul said:
Use system tuner pro and freeze any app.it won't run again until you boil it.
Click to expand...
Click to collapse
I'm in Taiwan where google have pulled paid apps so can't get that app here!
irishmoe said:
I'm in Taiwan where google have pulled paid apps so can't get that app here!
Click to expand...
Click to collapse
No, but you can make sure everything related to location in your settings is turned off as stated by someone else?
Check under Settings and disable anything related to location, besides GPS (really not needed to disable, it only runs when an application that use GPS is running) .
See my screen capture.
[
QUOTE=kekinash;18423471]Check under Settings and disable anything related to location, besides GPS (really not needed to disable, it only runs when an application that use GPS is running) .
See my screen capture.[/QUOTE]
Thats what my screen has looked like from day one.
kjy2010 said:
No, but you can make sure everything related to location in your settings is turned off as stated by someone else?
Click to expand...
Click to collapse
Yep I know you suggested it but I had already unchecked everything. Still running though
irishmoe said:
[
QUOTE=kekinash;18423471]Check under Settings and disable anything related to location, besides GPS (really not needed to disable, it only runs when an application that use GPS is running) .
See my screen capture.
Click to expand...
Click to collapse
Thats what my screen has looked like from day one.
Yep I know you suggested it but I had already unchecked everything. Still running though[/QUOTE]
irishmoe said:
I'm running taboonay and richardtrip's kernel
Click to expand...
Click to collapse
My bet is your problem lies in your ROM/Kernel mix, but just a guess then.
kjy2010 said:
Thats what my screen has looked like from day one.
Yep I know you suggested it but I had already unchecked everything. Still running though
Click to expand...
Click to collapse
My bet is your problem lies in your ROM/Kernel mix, but just a guess then.
[/QUOTE]
Possibly, was wondering if anyone else encountered the same problem before i start messing around with changing kernels or roms. Plenty of people using this combination and haven't seen any posts with same problem as me. Thanks for the help anyway. Maybe I'll try a different kernel
irishmoe said:
My bet is your problem lies in your ROM/Kernel mix, but just a guess then.
Click to expand...
Click to collapse
Possibly, was wondering if anyone else encountered the same problem before i start messing around with changing kernels or roms. Plenty of people using this combination and haven't seen any posts with same problem as me. Thanks for the help anyway. Maybe I'll try a different kernel[/QUOTE]
Quick question Moe. Why do you use a custom kernel? Do you overclock?
Just asking, because when I first got my tab I must have flashed every ROM and kernel that was out at the time, and found none with less problems, and more stable than the stock 3.2 kernel.
Nothing more than curiosity.
kjy2010 said:
Possibly, was wondering if anyone else encountered the same problem before i start messing around with changing kernels or roms. Plenty of people using this combination and haven't seen any posts with same problem as me. Thanks for the help anyway. Maybe I'll try a different kernel
Click to expand...
Click to collapse
Quick question Moe. Why do you use a custom kernel? Do you overclock?
Just asking, because when I first got my tab I must have flashed every ROM and kernel that was out at the time, and found none with less problems, and more stable than the stock 3.2 kernel.
Nothing more than curiosity. [/QUOTE]
To be honest I'm just trying stuff out to see what all the fuss is about. Both seem to be highly recommended so when i decided to go custom I just went with those two.
Hello folks,
i just flashed my htc hd2 with this rom made by tytung http://forum.xda-developers.com/showthread.php?t=1930240.
i am a real noob to that matter and it is my first device that i flashed and it took me a hole of information gathering but finally i made it.
it is working really great, but i have one problem: the landscape-modus is not working.
i have activated it, but is isn't working automatically.
did anyone have the same problems?
thank for your help!
It may be something to do with the settings for each individual app, but if you have auto-rotation enabled then I don't see why it shouldn't work. Did it work on WinMo?
Maybe you mean landscape in the launcher? If yes, you need to activate it manually because it comes deactivated by default.
I have activated autorotate in the display-settings and it isn't working. for example, when i'm in the browser and flip my phone...nothing happens and i didn't change anything in the browser settings...
Nigeldg said:
It may be something to do with the settings for each individual app, but if you have auto-rotation enabled then I don't see why it shouldn't work. Did it work on WinMo?
Click to expand...
Click to collapse
It was working with WinMo 6.5 and with WPM 7.8....
maybe your sensor needs calibration...download "SensorDebug" from store...open the app...put your phone on the grund and check pitch and roll values...if the values are zero then you are fine...if not check this out...http://forum.xda-developers.com/showthread.php?t=1653251
eliaskammas said:
maybe your sensor needs calibration...download "SensorDebug" from store...open the app...put your phone on the grund and check pitch and roll values...if the values are zero then you are fine...if not check this out...http://forum.xda-developers.com/showthread.php?t=1653251
Click to expand...
Click to collapse
I installed this app...and it is saying nothing. there are no values. it looks like the sensor isn't working.
are you sure.? can't help you pal..sorry.. :-/
Hi everyone ,
maybe you can help few of us ,
when i use the night clock , the clock is not refreshed,
for exemple when it's 5pm , it's in reality 5:15 pm.
any idea to fix this issue ?
regards !
trombonator said:
Hi everyone ,
maybe you can help few of us ,
when i use the night clock , the clock is not refreshed,
for exemple when it's 5pm , it's in reality 5:15 pm.
any idea to fix this issue ?
regards !
Click to expand...
Click to collapse
have you fixed that?
I have the same problem.
ramoneluis said:
have you fixed that?
I have the same problem.
Click to expand...
Click to collapse
Do you guys use force doze apps or amplify, greenify, powernap etc? It may cause this issue.
Konsstantine34 said:
Do you guys use force doze apps or amplify, greenify, powernap etc? It may cause this issue.
Click to expand...
Click to collapse
No. I dont use that apps. When i change the kernel, its work, but i miss other feautures. ..
I cant find solution for this...
ramoneluis said:
No. I dont use that apps. When i change the kernel, its work, but i miss other feautures. ..
I cant find solution for this...
Click to expand...
Click to collapse
On which rom-kernel it does/not work?
Konsstantine34 said:
On which rom-kernel it does/not work?
Click to expand...
Click to collapse
KHONGLOI Note 7 port.
Everything work perfect, but my clock dont work. Its come always when i lock the phone. Its works for 2,3 minutes and stop.
ramoneluis said:
KHONGLOI Note 7 port.
Everything work perfect, but my clock dont work. Its come always when i lock the phone. Its works for 2,3 minutes and stop.
Click to expand...
Click to collapse
Oh, I thought it's happening on original s6ep roms lol. They arent even int based roms/kernels which come with spesific issues like in-call echo etc(personally tested). Anyway; they are still working on it, hopefully gets fixed.
Konsstantine34 said:
Oh, I thought it's happening on original s6ep roms lol. They arent even int based roms/kernels which come with spesific issues like in-call echo etc(personally tested). Anyway; they are still working on it, hopefully gets fixed.
Click to expand...
Click to collapse
Ok. I will wait for this...
Thanks, man!
By now you may have heard about Axon 7 killing music playing app issue, if you haven't experienced it yourself already. For me I'm having a similar or at least related issue. The phone would kill my game when I turn off and on screen. After some investigation, below is my observation
1. Doesn't happen all the time. After a fresh reboot, no killing for a while... but after some time using the phone, it starts to happen
2. Not app-specific: After playing a game heavily for a while, the killing starts... only for that specific game. If I play a different game, then only that new game gets killed.
This have driven me kinda crazy. A look at adb logs reveals this:
12-22 12:45:34.229 I/ActivityManager( 1752): Killing 23881:jp.co.happyelements.toto/u0a122 (adj 0): excessive high power cost :jp.co.happyelements.toto
What the actual f***??? Why would ZTE kill my "excessive high power cost" process *after* I turn on the screen (and not when I turn off screen, which was 5 seconds earlier)??? Has nobody in ZTE thought about that apps that has "high power cost" may not be actually "excessive" but totally within reasons and fall into the category of normal every day use?
And no amount of changing the native "power saving" options stopped this behavior. Back in the days I remember there was some root/xposed module that would whitelist apps from being killed by the OS but I couldn't remember the name. So now I have to ask help on how to deal with this idiocy.
Edit: My apologies... I just noticed I posted in the wrong section... mods please move the thread to Q&A section if possible. Thanks a lot.
is there seriously no solution?
This is intolerable
Turn off smart power lol. Not rocket science my friends
icenight89 said:
Turn off smart power lol. Not rocket science my friends
Click to expand...
Click to collapse
I did. Didn't help.
If it was that easy, then I wouldne be here asking about it would I?
Yep, have the same problem after trying the same things. Several apps (2 of which I use for monitoring blood sugar levels) will randomly stop updating until either re-launched or the phone is rebooted. I have disabled all power manager options to no avail. Whatever power management system ZTE has implemented, it's FAR too aggressive.
Disclaimer - I haven't pulled logcats, but your description of the problem matches mine exactly. Here's hoping for a fix in Nougat and/or a custom ROM, otherwise I'm moving to a different phone. The A7 has great hardware but the stock software is a bloated mess.
B27 does not have this issue (which is why I downgraded to it). Might be a solution for you until the next upgrade releases.
whoiswes said:
Yep, have the same problem after trying the same things. Several apps (2 of which I use for monitoring blood sugar levels) will randomly stop updating until either re-launched or the phone is rebooted. I have disabled all power manager options to no avail. Whatever power management system ZTE has implemented, it's FAR too aggressive.
Disclaimer - I haven't pulled logcats, but your description of the problem matches mine exactly. Here's hoping for a fix in Nougat and/or a custom ROM, otherwise I'm moving to a different phone. The A7 has great hardware but the stock software is a bloated mess.
Click to expand...
Click to collapse
@whoiswes If you are talking about the xdrip app. I too want this app to work with this phone. I tried CM13 and had the app work for hours then at night it stopped working. I only tried it for one night so didn't try different settings. At least this is a positive sign once CM13 becomes more stable or CM14 is released. I heard the app won't work with B27 either.
Found a solution, though it needs root
Code:
pm disable com.zte.powersavemode
then reboot
This totally disables the power saving menu though
phailyoor said:
Found a solution, though it needs root
then reboot
This totally disables the power saving menu though
Click to expand...
Click to collapse
Can you freeze it with TB?
Actually no that didnt help just made it take longer
I have the same issue, ram management is too aggressive.
phailyoor said:
Found a solution, though it needs root
then reboot
This totally disables the power saving menu though
Click to expand...
Click to collapse
Didn't work
:crying::crying::crying:https://forum.xda-developers.com/axon-7/development/xposed-kill-zte-killer-t3532298
phailyoor said:
:crying::crying::crying:https://forum.xda-developers.com/axon-7/development/xposed-kill-zte-killer-t3532298
Click to expand...
Click to collapse
Did this work?
borijess said:
Did this work?
Click to expand...
Click to collapse
No because it has nothing to do with powermanager.
doyou37 said:
No because it has nothing to do with powermanager.
Click to expand...
Click to collapse
Then why was it posts here?
borijess said:
Then why was it posts here?
Click to expand...
Click to collapse
People are desperate
borijess said:
Did this work?
Click to expand...
Click to collapse
Yes
doyou37 said:
No because it has nothing to do with powermanager.
Click to expand...
Click to collapse
Lol did you even look at it?
doyou37 said:
People are desperate
Click to expand...
Click to collapse
I made this xposed module specifically to fix the problem described in OP. If you have the exact problem, including the logcat message, then the module should fix it.
If you dont have the exact problem, including the logcat mesage, then go ****post in another thread.
My solution is to whitelist all apps in:
settings -> energy management -> app energy management -> option button (upper right) -> app protection list -> option button -> set all to off
But the problem is that this setting resets everytime you install/delete an app
Edit: Ok i just tried out manually setting all apps to "off", now it doesn't reset the apps when installing an app but the new app ist automatically allowed to be cleaned. So you still have to disallow cleaning for each installed app manually.
Just an FYI, I updated to the Cyanogenmod/Lineage 13 Beta by UDev and one of my problem apps has been running for 18 hours without a single hiccup. Trying the second problem app later today. Not a solution for this problem but from my perspective it definitely pinpoints Power Manager as the culprit.
@borijess - yeah, Nightwatch and xDrip are the 2 apps that I've had trouble with, and so far Nightwatch is working great on CM13 (1228 build).