Database Users

Remove HTCLOCKSCREEN!!!! HOW!

Hey quick question, I really dislike the EVO Sense lockscreen, I'd much rather have the 2.1 lockscreen style, Flan I think. How would I go about removing it?
Thanks!

Turn off Sense and it is gone.

Remove htclockscreen.apk and .odex or rename them and you should get stock while keeping the other sense goodness.

I turned of Sense and it stayed the original Sense lockscreen.

After you turned off Sense, it should have asked you what home screen you wanted...Sense or Launcher. I just tried it on my phone and it worked fine.

meatgel said:
I turned of Sense and it stayed the original Sense lockscreen.
Click to expand...
Click to collapse
Same problem, the sense lock stayed with a disable. I want to keep sense but I dislike the Locker, I tried using terminal with the Unrevoked root and I can't seem to access the APN? It says access denied or something.

Downloaded RootExplorer and mounted Read and Write operations and changed the name of the two files, Rebooting now. Lets see if that worked.

That didn't work, the file comes right back when I reboot.

I would like to now how to do this too. I am using ADW launcher and the Sense lock screen is still there.

Try no lock in the Market. Also lets you use the volume rocker to come out of standby.

Ranger093 said:
That didn't work, the file comes right back when I reboot.
Click to expand...
Click to collapse
We don't have /system rw in android yet. That is why its not working.
You have to boot to recovery (nandroid screen), mount, and change through adb.

jmxp69 said:
Try no lock in the Market. Also lets you use the volume rocker to come out of standby.
Click to expand...
Click to collapse
Thank you! Just what I was looking for although it would also be nice to be able to double tap one of the for cap buttons to wake up the Evo.
EDIT: Oh it seemed just about perfect and then I figured out that it also turns off the screen lock for incoming calls which is no good for me.

removing htclockscreen.apk and odex does bring up the android lockscreen however, the graphics are off, just like the hero was.

Well damn I've tried 3 different computers and I cannot get ADB to detect my phone correctly so that I can work around and delete the stuff. Is there a guide I can follow exactly to the tee for the Evo 4g

I saw a app on the market to remove the sense screen. Can't remember what its called tho.
-------------------------------------
Sent via the XDA Tapatalk App

i use myLock (free) to kill the Sense unlock and LockPicker (free) to bypass the password if you setup an exchange account

Ranger093 said:
Well damn I've tried 3 different computers and I cannot get ADB to detect my phone correctly so that I can work around and delete the stuff. Is there a guide I can follow exactly to the tee for the Evo 4g
Click to expand...
Click to collapse
sounds like you haven't enabled USB debugging in settings->applications on the evo.

ffolkes said:
sounds like you haven't enabled USB debugging in settings->applications on the evo.
Click to expand...
Click to collapse
I have though, the drivers I try to use will not install when I go to device manager, and I've tried stopping windows from installing automaticly to use the drivers from the SDK.

Lockbot Pro. Best app there is. Built in editor to make your own or browse the gallery and download.
I just made an X10 Themed lockscreen. I'm happy.

What is the Code I need to put in? I'm on the green nandroid screen

(Question) How to delete original lockscreen?

I just tried the latest version of Lockbot.
Again, they did not solved for us the issue about double lockscreen.
Your original lockscreen will appear first. than theirs....so...annoying as hell
I recently rooted my x10 and with titanium backup I deleted moxier and some foreign keyboards. But I can't find where they placed the original lockscreen program.
I think when you delete it from the system and install Lockbot the problem will be solved? Or is this a wrong way of thinking from me?
Does anyone knows where in the device they hide the lockscreen programm?
Cheers,
Arnold

I don't know of a way to delete it, there is an app in the market called no lock or something similar?!
Sent from my X10i using XDA App

It is CRAZY that you can't have just the "secure" lock, but have to do the "simple" lock THEN the "secure lock". Turning off the "secure" lock is no good, I want that protection!
Does anyone know if this has been sorted in future Android versions? Or is it just for the x10? I'm a relative newbie to all this.

there is a pay app called "goto". you can check "replace the original screenlock" to remove it. unfortunately, the built-in screenlock comes back from time to time.
Sent from my X10i using XDA App

Thank you for answering.
After I installed the latest lockbot version AND RESTARTED my phone it is working well for the first time after 300 versions of Lockbot
BUT, they made it so well you never see the original lockscreen back. You might think " THATS GREAT!"
Yes, but when you put your phone in airplane mode and put it back to normal mode, you won't able to login anymore as you don't see the original lockscreen. So you have to restart your phone before it works again. That might answer my own question....IF you are able to delete the lockscreen from your phone totally I think you are screwed as you need it to login your phone with your password.
So Lockbot improved a lot, and works great as long as you don't put your phone in airplane mode and switch it back to normal mode. That requires a reboot. I tested this new version of Lockbot for a day intensively and further on it works great and I did not see the original lockscreen anymore.
I will test it for another few days and when it is still working fine I will buy it.
Cheers,
Arnold

PollPixx said:
Thank you for answering.
After I installed the latest lockbot version AND RESTARTED my phone it is working well for the first time after 300 versions of Lockbot
BUT, they made it so well you never see the original lockscreen back. You might think " THATS GREAT!"
Yes, but when you put your phone in airplane mode and put it back to normal mode, you won't able to login anymore as you don't see the original lockscreen. So you have to restart your phone before it works again. That might answer my own question....IF you are able to delete the lockscreen from your phone totally I think you are screwed as you need it to login your phone with your password.
So Lockbot improved a lot, and works great as long as you don't put your phone in airplane mode and switch it back to normal mode. That requires a reboot. I tested this new version of Lockbot for a day intensively and further on it works great and I did not see the original lockscreen anymore.
I will test it for another few days and when it is still working fine I will buy it.
Cheers,
Arnold
Click to expand...
Click to collapse
What version is that?

1.15.2 pro version.
Still no problems...
Sent from my rooted x10i using tapatalk. Cheers, Arnold

Hmm, i have buy pro version 1.15.2 and i have still dual lock screen problem

Did you restart?
I just read the only bug is when you hit the menu button when its locked, than the double will appear. I tested that and its true. But after re boot its working great again. Or go to settings in lockbot and uncheck and check again the option to replace original lockscreen
It can t be working for me only I guess, my phone is rooted but I don't think that make a difference...
Sent from my rooted x10i using tapatalk. Cheers, Arnold

now it works, I should just disable "No Lock" apps ...BTW my X10i is also rooted ...

Great, I thought I gave wrong advice...
Sent from my rooted x10i using tapatalk. Cheers, Arnold

Power control widget turned my screen off permanently.

what should i do? haha

clintceastwood said:
what should i do? haha
Click to expand...
Click to collapse
Holy sh##, I wonder if thats what happened to mine then.... I had it for 3 hours, installed extended controls on it, turned the brightness all the way down and it died. Battery pull would get me the samsung screen but it would stop after the galaxy animation. I did a factory reset, still did it.
Is that about the same?
I figured that I just had a bad unit so I took it back to the store.
Edit. Just did a little research and we are not the only two this has happened to...not seeing a fix though...

If you have cwm installed or debug enabled you should just adb to your device and delete the offending widget app.
Sent from my SCH-I500 using XDA App

man, that sucks.

Happened to me too... If only we had the notification brightness slider the vibrant has. I had to take miner back too... Didn't know of cwm and I was smart enough to turn debugging mode off so no adb for me.
Sent from my SCH-I500 using XDA App

wizang said:
If you have cwm installed or debug enabled you should just adb to your device and delete the offending widget app.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It persisted after a factory reset on mine. Offending app was all gone... Will be interesting to see if the op can get his working by doing that. Personally I just thought I had a bad phone.

thanks for the help guys put i adb pulled and it solved my problem ... i was freaking for a second

clintceastwood said:
thanks for the help guys put i adb pulled and it solved my problem ... i was freaking for a second
Click to expand...
Click to collapse
Awesome. Wonder why my factory reset didn't fix mine... Weird.
Bigger question... What do the application developers need to change too keep this from happening?

well the truth in my case is i downloaded a version off mediafire to see if i liked it before i donated and the thing was the version i downloaded had an error that to this day has been corrected. so if i wouldve just been legit from the beginning it wouldnt of happened

I always keep adb on after this lesson...
http://forum.xda-developers.com/showthread.php?t=785603&highlight=horror

clintceastwood said:
well the truth in my case is i downloaded a version off mediafire to see if i liked it before i donated and the thing was the version i downloaded had an error that to this day has been corrected. so if i wouldve just been legit from the beginning it wouldnt of happened
Click to expand...
Click to collapse
Extended trial eh? looked at extended controls change log, none on theirs yet. Guess I'll try power widget instead.

I was a victim of this as well with the extended controls widget. I emailed them and they didn't seem overly concerned, though to be fair there is a language barrier. I would have expected profuse apologies and a refund, at the very least.

I use the one called "Backlight!" but when I installed and saw the default value levels of 0,50,150,255 and saw a zero that instantly threw up a red flag. Before using widget I just edited the custom brightness levels to 34,65,103 which translates to 13%,25%,45%. Are there other devices where you could assign the toggle to a hard button? That's the only way I can see having a 0 default level on a device.
good day.

I submitted a ticket to the extended controls group and they just updated it after fixing the issue... Said it is now fixed and will be in the next release.

this has been posted in the forum, the phone still works, the display is just completely blacked out. 0% apparently meant different for the Samsung Fascinate phones than other Android phones. Power Control widget had updated their log a few days ago saying this was resolved in the last update here:
http://www.appbrain.com/app/power-control-plus-(widget)/com.siriusapplications.eclairwidgets

good thing the brand new version that i tried to pay for still blacked out my screen

Thank God I found this thread! Same here!! Power Strip. Was so depressed when I noticed I couldnt wake my screen back up after boot and locking it! Phew.... AWESOME PHONE!

Yea this happened to me as well and I didn't have de bugging on to use adb. Took it to the store they were like "we have never seem this happen before...sorry sure have this new one!" LoL
Sent from my rooted 1.2 voodoo Fascinate

Mine did it from a Ringer Profile app. I was trying to get my Fascinate to act more like a Blackberry in regards to notifications and such. All seemed well until I re3booted the phone. I went through 2 phones from this. The app did have functions for setting screen brightness for different profiles. Since I got that one solved, the phone's been great!

MikG 3.0 2nd issue - no lockscreen/sd card

Oh no. Here I am posting again within a few days with another issue.
My previous issue can be found here:
http://forum.xda-developers.com/showthread.php?t=1459225
I just turned my phone off to attend a few classes and when I turned it on my lockscreen was invisible (so could not unlock phone) and I saw an error on the top bar saying my memory storage was empty. If I reinsert my sd card the error goes away but lockscreen is still invisible. The phone does nothing. I hate to say it but I'm thinking about switching outta this ROM. It's moving fast when it DOES work so would love some help on this.
Thanks in advance.

This happened to me when flashing, i had to flash, reflash reflash reflash until it finally came up, Maybe try rebooting it a bunch of times?

This happened to me as well when I tried MikG 3.0. You might want to try going into recovery and selecting the mounts and storage option and choose mount emmc. If it gives you an error, then your EMMC is borked and you must flash back to a stock incredible based from (such as TeeRom, Ice Cream Sense, or Stock GB) to format phone storage. You'll lose everything on EMMC but it will fix your issue. I also took out my SD card before choosing to format phone storage just to be safe
Looks like something is causing this issue on Mik3.0 and I unfortunately must advise backing up your emmc before using it.
Sent from my Droid Incredible using the XDA app.

What Mods are the two of you using? Ext4, themes not in the MikG forum? I need to know so I can try to recreate the problem. As I said in another post, this ROM does NOT even touch the emmc partition. Let me know what changes you've made. I can't help you with no information. There's been a hundred downloads and you two are the only ones I see with an emmc issue. Are your phones new, used, eBay? Thanks for the info.
EDIT: Also, what CWM recovery are you using?
Sent from my HTC Droid Incredible

My info:
- Bought brand new 1.5 years ago
- CWM 5.0.2.0
- Hboot 0.92
- Nothing additional was flashed, not even tiny's kernel
- Wiped Data/Factory Reset, boot and system from CWM before flashing
- Restored apps with data from Titanium
- Set up Google and Facebook accounts
- Installed and applied Slate.apk
- Applied the following tweaks:
Font: Roboto
Autobrightness: Lowest
Boot Animation: HTC Stock
Down Animation: ATTEMPTED to switch to HTC Stock, however it was hanging on the download so I hit home to get out of the screen.
Status Bar Transparency: Switched to transparent, switched back
Rosie Drawer Scrolling: Disabled
Quick Settings: Disabled various quicksettings (4G, ADB Wireless, Silent, Vibrate)
Animation speed: Switched from Normal to slow on both transition and window
- Edited build.prop ro.fingerprint to reflect GB instead of Froyo so I don't get the OTA nag
- Set up everything all nice and stuff
I may have missed something, but that's pretty much what I did.

Div033 said:
My info:
- Bought brand new 1.5 years ago
- CWM 5.0.2.0
- Hboot 0.92
- Nothing additional was flashed, not even tiny's kernel
- Wiped Data/Factory Reset, boot and system from CWM before flashing
- Restored apps with data from Titanium
- Set up Google and Facebook accounts
- Installed and applied Slate.apk
- Applied the following tweaks:
Font: Roboto
Autobrightness: Lowest
Boot Animation: HTC Stock
Down Animation: ATTEMPTED to switch to HTC Stock, however it was hanging on the download so I hit home to get out of the screen.
Status Bar Transparency: Switched to transparent, switched back
Rosie Drawer Scrolling: Disabled
Quick Settings: Disabled various quicksettings (4G, ADB Wireless, Silent, Vibrate)
Animation speed: Switched from Normal to slow on both transition and window
- Edited build.prop ro.fingerprint to reflect GB instead of Froyo so I don't get the OTA nag
- Set up everything all nice and stuff
I may have missed something, but that's pretty much what I did.
Click to expand...
Click to collapse
Only thing I see I don't like and don't recommend is TB with data. I have never had ANY luck keeping things stable doing that. Not saying that's it, just pointing it out. Still not seeing anything. Sorry. Just not sure how the ROM can do this. I asked Aamikam, the dev for the EVO version of this for his thoughts. He's not sure how this is even possible since the ROM doesn't touch emmc. Not sure.
Sent from my HTC Droid Incredible

countryfolk07 said:
Only thing I see I don't like and don't recommend is TB with data. I have never had ANY luck keeping things stable doing that. Not saying that's it, just pointing it out. Still not seeing anything. Sorry. Just not sure how the ROM can do this. I asked Aamikam, the dev for the EVO version of this for his thoughts. He's not sure how this is even possible since the ROM doesn't touch emmc. Not sure.
Sent from my HTC Droid Incredible
Click to expand...
Click to collapse
There are four reported cases of this issue on these forums so far; the OP of this thread, two more in the rom thread and myself. Still not as widespread as it could be, but it must be a rom issue. I've been restoring apps with APP data (never system data) through titanium in every rom flash and never have any issues, so I do not believe that is it. However I am not ruling it out. I forgot to mention I have an AMOLED screen if that makes any difference.

Div033 said:
There are four reported cases of this issue on these forums so far; the OP of this thread, two more in the rom thread and myself. Still not as widespread as it could be, but it must be a rom issue. I've been restoring apps with APP data (never system data) through titanium in every rom flash and never have any issues, so I do not believe that is it. However I am not ruling it out. I forgot to mention I have an AMOLED screen if that makes any difference.
Click to expand...
Click to collapse
I also have AMOLED. What I'm not understanding is that I have flashed the exact .zip the reported cases have flashed. I've not seen the issue. Very frustrating, this is my favorite ROM and just wanted to be able to share with others, because this has always been a favorite.
Sent from my HTC Droid Incredible

Those having various issues, there is an updated build.prop on the mikmik site. Try it please.
Sent from my HTC Droid Incredible

countryfolk07 said:
I also have AMOLED. What I'm not understanding is that I have flashed the exact .zip the reported cases have flashed. I've not seen the issue. Very frustrating, this is my favorite ROM and just wanted to be able to share with others, because this has always been a favorite.
Sent from my HTC Droid Incredible
Click to expand...
Click to collapse
Good ol' software.
I'll try and troubleshoot it tomorrow perhaps. I love this rom as well and if I can get MMS over Wifi working like you say you have then it'll be a daily driver for sure.
What we know:
- Issue happens after a reboot
- EMMC is repartitioned as something completely different/is corrupted, making the volume unreadable.
- Upon boot, apps and whatnot seem to start up but no lock screen is present. The entire device does not respond to touches, including the capacitive buttons and hardware buttons excluding the power button (holding it does nothing though) to turn the screen off and on. Perhaps its having trouble loading Rosie.apk?
Also, I remember I did freeze some HTC stuff I don't use, but I don't recall freezing anything out of the ordinary. When I go back to troubleshoot I'll redo everything step by step, rebooting after each change.
Sent from my Droid Incredible using the XDA app.

Ok guys. I'be figured out what happened, just have to fix it. There is no emmc on the EVO. I have to trick our phone into seeing it. Talking to Newt to figure this out. Thanks for your patience.
Sent from my HTC Droid Incredible

countryfolk07 said:
Ok guys. I'be figured out what happened, just have to fix it. There is no emmc on the EVO. I have to trick our phone into seeing it. Talking to Newt to figure this out. Thanks for your patience.
Sent from my HTC Droid Incredible
Click to expand...
Click to collapse
This is great news! Keep us posted

I've been having the same issues mentioned, I took me 3 flashes to get the lockscreen to work and occasionally when I do reboots it won't show up and I'll have to do a battery pull. I also get the sd notifications sometimes, the sd card still works but the notification stays there. Another problem I've been having is that annoying system update from verizon, it keeps popping up and I don't know how to get rid of it. Any ideas?

Stratman14 said:
I've been having the same issues mentioned, I took me 3 flashes to get the lockscreen to work and occasionally when I do reboots it won't show up and I'll have to do a battery pull. I also get the sd notifications sometimes, the sd card still works but the notification stays there. Another problem I've been having is that annoying system update from verizon, it keeps popping up and I don't know how to get rid of it. Any ideas?
Click to expand...
Click to collapse
Build prop update at the mikmik will help with the update nag. Also, I finally got the SD/emmc , and lockscreen issue, all at the same time after doing a font. For two weeks I had no issues, until I decided to change fonts in tweaks. Anyone having these issues after changing fonts? Just trying to troubleshoot some more.
Sent from my ADR6300

countryfolk07 said:
Build prop update at the mikmik will help with the update nag. Also, I finally got the SD/emmc , and lockscreen issue, all at the same time after doing a font. For two weeks I had no issues, until I decided to change fonts in tweaks. Anyone having these issues after changing fonts? Just trying to troubleshoot some more.
Sent from my ADR6300
Click to expand...
Click to collapse
I switched to Roboto font during my run, but I did a bunch of other tweaks previously mentioned before rebooting so I couldn't single it out for sure. Sure does seem like the culprit now though!
Sent from my Droid Incredible using the XDA app.

Div033 said:
I switched to Roboto font during my run, but I did a bunch of other tweaks previously mentioned before rebooting so I couldn't single it out for sure. Sure does seem like the culprit now though!
Sent from my Droid Incredible using the XDA app.
Click to expand...
Click to collapse
Yes it does.!!!!!! Maybe were on to something. Everyone else with the lockscreen/emmc issue, please, please, please, let me know if you switched fonts. Thank you.
Sent from my ADR6300

I have the issues and I did not switch fonts...

Stratman14 said:
I have the issues and I did not switch fonts...
Click to expand...
Click to collapse
Aghhhhhh!!!!!! Your emmc was wiped out? Or just lockscreen issue?
Sent from my ADR6300

I haven't had the lockscreen issue in a while but I keep getting a notification that won't go away saying "Phone storage is empty or has unsupported files". And how do you push build.prop with root explorer?

Stratman14 said:
I haven't had the lockscreen issue in a while but I keep getting a notification that won't go away saying "Phone storage is empty or has unsupported files". And how do you push build.prop with root explorer?
Click to expand...
Click to collapse
Download the file to your SD card. Make a backup of your current build.prop. Call it build.prop.old. Copy the downloaded build.prop and paste to /system directory. Then change permissions to rw-r--r-- . Do all of this before a reboot. To change permissions, make sure system is r/w enabled, then long press file and select permissions.
Sent from my ADR6300

Any tweak to use full screen for any apps on OnePlus 8 Pro

Hi all! Does anybody know some tweak ui app to force full screen for all apps? Unable to use the whole screen is very annoying. I've turned off status bar due to screen burning after two months, but the upper line is always empty in portrait or landscape mode.
Thanks in advance!
And peace to all.

aae_nsk said:
Hi all! Does anybody know some tweak ui app to force full screen for all apps? Unable to use the whole screen is very annoying. I've turned off status bar due to screen burning after two months, but the upper line is always empty in portrait or landscape mode.
Thanks in advance!
And peace to all.
Click to expand...
Click to collapse
I am researching on this. On A10 you can use the magisk module "none display cutout". After install, in dev settings you have an option to completely ignore the holepunch area and swithching to fullscreen with gmd gestures lite will have truly fullscreen and no icons to burn in. Sadly this is not working on a11. Module will flash, holepunch will be ignored. But fullscreen mode will just turn off holepunch area

Thank you very much!
But I would prefer to not install twrp and not to flash magisk as well due to some reasons.
Just hope if exists some tweak app with adb granted permissions, like those for immerse mode.

Yes, thx,a solution would really be nice. I have been wondering about this.

aae_nsk said:
Thank you very much!
But I would prefer to not install twrp and not to flash magisk as well due to some reasons.
Just hope if exists some tweak app with adb granted permissions, like those for immerse mode.
Click to expand...
Click to collapse
Do not use the below
DO NOT SELECT DOUBLE CUT OUT
DO NOT USE ON BETA

dladz said:
I think you're going to struggle without root, you'd need to change some files in system, without root I don't think you can.
Have you checked on the display cut out in developer options?
Haven't used it but may offer every you want?
Check out the other OnePlus forums, they're longer established and may have mods which can be adjusted for this OS, or possibly it may even work as is..
Hope this helps.
Click to expand...
Click to collapse
Do not chose double cutout. Instant bootloop with no chance of recovery. Don't say i didn't warned you

elmarian756 said:
Do not chose double cutout. Instant bootloop with no chance of recovery. Don't say i didn't warned you
Click to expand...
Click to collapse
Really? I didn't get any of that, tbh though I don't think I actually clicked that one.
Find it hard to believe that OnePlus would leave that in.
Would assume that safe mode would still work.
Are you on stable or beta?

dladz said:
Really? I didn't get any of that, tbh though I don't think I actually clicked that one.
Find it hard to believe that OnePlus would leave that in.
Would assume that safe mode would still work.
Are you on stable or beta?
Click to expand...
Click to collapse
Stable. Mine instantly died after selecting double lol. I was very pissed off but i had a quick backup so didn't took much time messing with it. Ob3 users reported to me in a testing group that innbeta this doesn't happen

elmarian756 said:
Stable. Mine instantly died after selecting double lol. I was very pissed off but i had a quick backup so didn't took much time messing with it. Ob3 users reported to me in a testing group that innbeta this doesn't happen
Click to expand...
Click to collapse
Maybe it's an ob3 issue? Apologies mate, I had no idea.
Updated my original post to avoid it

You can use the adb command to remove magisk modules in case of bootloop caused by this, happened to me on my 8T. Still looking for a working notch killer for a11

samspark said:
You can use the adb command to remove magisk modules in case of bootloop caused by this, happened to me on my 8T. Still looking for a working notch killer for a11
Click to expand...
Click to collapse
could you post this exact command sir? this is one of the biggest things on paranoid about, they're not being a good version of TWRP for 11

There's definitely a lot of dead space up at top reserved for the humongous status bar icons, a good 0.5".
Should have made them smaller and further up the screen. Like others mentioned this task will be probably zero achievable without root etc.

Burt Squirtz said:
could you post this exact command sir? this is one of the biggest things on paranoid about, they're not being a good version of TWRP for 11
Click to expand...
Click to collapse
adb wait-for-device shell magisk --remove-modules
You need to turn your device on after typing that in adb