Hey,
Some of the wm2005 devices show a "loader screen" when you hardreset the device. One of my custom cabs I placed in the extrom, needs you to tap "accept" before it will isntall. The problem is that the "loader screen" is in the way, thus the install just hangs.
Ne ideas on how to get past this??
if it show the dialog and just not response to tabs
moving the focused the actionbutton to the button like "yes" or what even
and pressing the center of the actionbutton works like click
the only problem is: The screen that you should click "accept"
on doesn't show, it is behind the "loader" screen.
Aaargh! :x
In my rom there is a config.txt file that has commands that are run by the AutoRun.exe file.
the first line displays the splash screen:
SHOW:\Extended_ROM\Verizon_Logo2.bmp
the second line Disables the Touch Pad (TP)
EXEC:\Extended_ROM\TPDisable.exe
Then alot of cabs are loaded
The last two lines Enable the Touch Pad and do a soft reset.
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset
If yours is simular, just modify it to not show the splash screen, and make sure the touch pad is enabled when you load your cab.
I have a apache from verizon.
Hope this helps.
Hi all.
Suddenly, the "Space Key" does not appear in Full Qwerty Keyboard.
Now ".com" & "/" appear instead of "Space Key".
(plz see the attached file)
I want to change from ".com" & "/" to "Space Key",, how ever i don't know the way.
Could u give the solution?
i had exact same problem. apparently you have to do a registry change to fix it. HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
Your variable might not be 1 but when my screen was as yours it was a 2. Laater it switched on its own to a 9 so dont lose this registry change because your probably going to have to do it again. I noticed when i added new contact or something to that effect it changed the variable
Thank you very much for your solution!
My "CurrentET9Style" is 6.
After revise from 6 to 0, Back to normal keyboard.
Thank you !!!
mjcole2003 said:
i had exact same problem. apparently you have to do a registry change to fix it. HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
Your variable might not be 1 but when my screen was as yours it was a 2. Laater it switched on its own to a 9 so dont lose this registry change because your probably going to have to do it again. I noticed when i added new contact or something to that effect it changed the variable
Click to expand...
Click to collapse
Did you install the tweak cab from ppgeeks? if so, that is your issue. It was in the 1st post
thanks ,i think i get it.
supdawg said:
Did you install the tweak cab from ppgeeks? if so, that is your issue. It was in the 1st post
Click to expand...
Click to collapse
who's first post? I did install the tweak cab from ppcgeeks and would like to read that 1st post. If i uninstall the tweak will it fix the reacurring problem or do i have to hard reset? Thanks
when i changed to "autocomplete" I had the same problem with the space key being gone until i put the registry back the way it was...Tj
Keep CurrentET9Style = 0 ??
Changed HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
This works temporarily, but when I click on the time in a calendar entry, it switches to numbers, and does not switch back unless I re-edit the registry. Is there any way to keep the setting from changing at all? I want it to stay at CurrentET9Style = 0.
Anybody?
Hi everyone. Okay, first let me just say that the "FixStuckTP2Keyboard.cab" is fine and it does work. But it reverts your keyboard back to the "eT9" and you probably did a registry hack to change it from that in the first place (changed it to "COMP") am I right? Not to knock that cab, like I said it works just fine but I did NOT want to "install" a cab file everytime this happened (after it would change it back to "eT9" I would have to go back into the registry and change it to "COMP" again.)
Let me tell you HOW this is happening in the first place, it has something to do with Opera. You can test this very easily. First get your keyboard working properly, then open Opera. Type something in the address bar or just tap the address bar and BAM! Your keyboard is stuck in that mode. Now I don't know why this happens, that mode is getting stuck in memory for some strange reason and it will NOT let go.
I'm assuming this is ONLY happening to those of us who have used the registry (or a program or cab) to change the keyboard to "COMP" instead of "eT9" since changing it back to "eT9" solves the problem.
There are three solutions:
1.) ONLY use the slide-out keyboard when using Opera.
2.) Use the FixStuckTP2Keyboard.cab
3.) Use the MortScripts I created.
Use "KB-OFF (eT9).mscr" to force the "eT9" info into the registry. Then use "KB-ON (COMP).mscr" to enter the "COMP" info back into the registry, then do a soft reset.
You can rename these files if you like.
Yeah I know it sucks to have to do a reset just to get the use of your spacebar back just because you used the virtual keyboard when using Opera but hey, what are you gonna do?
UPDATE: Just noticed that "sometimes" my scripts don't work if you click on them one after another (again for some strange reason). If this happens to you just click on "KB-OFF" soft reboot then click on KB-ON" & reboot. Weird I know.
I've been running on m1ndh4x8r's Sense 3.5 ROM for a while and the only issue I have is not being able to disable the CRT on/off animation.
Settings> no animations don't seem to disable it even after a reboot. Also installed Spareparts and setting the animation speed to fast doesn't seem to do the trick either.
So is there any way I can get rid of it? If I had to decompile and edit services.jar, how do I go about that? Thanks in advance.
Bump. Sorry
Alright, seemed to have figured it out myself. Had edited the PowerManagerService.smali and the PowerManagerService$BrightnessState.smali (services.jar) to remove bits of the CRT animation.
Well, I've attached the services.jar file if anyone requires it. It does have CRT off, NOT on. And the animation switches off when settings are set to 'no animation'.
PS. I'd advice backing up your current services.jar to avoid any issues. The file has been edited from m1ndh4x8r's v4.7 sense 3.5. And I apologize if there is an easier alternative around, couldn't find it when I searched.
Edit: Just to avoid confusion: This flashable Zip file allows you to have CRT off animation when switching the screen off/ locking AND disables the CRT on animation when unlocking. Also, setting it to 'no animations' will remove the CRT effect altogether unlike some ROMs where the effect sticks regardless.
Hi guys,anyone can help me?
I would like to hide or erase the "Drag to Unlock" text under the lockbar.
If you have some suggestions please write here,thanks
P.S. I don't wanna use another lockscreen like widget locker etc.
robsup79 said:
Hi guys,anyone can help me?
I would like to hide or erase the "Drag to Unlock" text under the lockbar.
If you have some suggestions please write here,thanks
P.S. I don't wanna use another lockscreen like widget locker etc.
Click to expand...
Click to collapse
Download the HiSuite from Huawei website. Inside the program is a tool for customising the UI, Connect your P6 with the computer and the program. start the UI customisation tool. Load the theme you wish to modify. Change what you want, then save it as another theme, load it back to your phone and apply the modified theme. That should do the trick. I did look into the tool, its good, though I didnt making a new one yet. But others have used it before for the intended purpose.
Hi, yes i tried with that method but there isn't a voice or a png to erase the "drag to unlock" text...
You can just rename the file as zip file and browse for the unlock text. I remember while browsing the contents of the ios7 theme that i did come across the unlock text file as an image file. But i dont remember where it was located.
Have you tried playing with the xml file? I think this line refers to the text 'Drag to unlock' that you want to remove.Notice its start at x=0 and width is 720 which is the screen width, position at y=1100 which is the text y position and align center. If you wish to test whether its the correct one or not, just change the align parameter.
<text x="0" y="1100" w="720" h="80" align="center" size="18" color="#FFFFFFFF" src="system.unlocktip"/>
While the lines after that containing y="1105" refers to the animated arrows if you wish to remove that as well.
The xml file is at Taste/unlock/layout-hdpi/layout_taste.xml
Yes i did;this is the unlock .txt but i don't see the "drag to unlock" voice to erase....
Dammit i'm going crazy to know how to do!!
EDIT:I see now your post,Zemega,so do you think I should delete that string?
Indeed that is the case. In fact I like your idea very much that I went ahead and test it for myself. You can see the screenshot in the attached. Of course I remove the arrow as well. If you dont want to remove the arrow just remove that one string from before. Another suggestion is to increase the arrow count, but you have to to time it right. Attached are screenshot of my lock screeen and the edited file.
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
I couldn't fix the "Pixel is starting..." issue. Factory Flashing (after removing -w) QQ1A.191205.008 resulted resulted in being stuck at the "G" screen. I flashed the QQ1A.200105.002 factory image (again with -w removed) and was left in the same "Pixel is starting..." state.
Here is where things get interesting:
Over adb I launched the Settings app:
Code:
adb shell am start -a android.settings.SETTINGS
Next, I went into "Security," which prompted for my PIN, and then removed the screen lock. After doing this, I was able to get into /sdcard in the ADB shell, something that was not possible before.
Back in the settings app, I enabled USB File Transfer and copied all my files & photos off. I was also able to launch apps from within the apps list in Settings. This let me export settings/data from other apps that allowed it. :good:
So it seems that entering your PIN in the Settings app also unlocks the phone!
Thanks for describing this and how you ended up resolving it. I am seeing the same "Pixel is starting". Flashing the (March 2020) factory image didn't fix mine either.
I was able to get into Settings by pulling down the notification shade while the "Pixel is starting" message shows. I removed my fingerprints and PIN.
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
I've tried this:
Settings-->Apps & notifications-->App info--> {select any app and tried clicking on icon at top of screen} Nothing. Poked around a bit and tried various things but couldn't figure out how to launch an app from here. Thanks in advance.
docdl said:
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
Click to expand...
Click to collapse
There should be a "Open" shortcut just below the app icon to the left of "Uninstall" (or "Disable" if it is a built-in app).
_Ra1n_ said:
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
Click to expand...
Click to collapse
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described. I'm also stock, rooted with Magisk, on the January update. I just found that I can get into adb, but I'm a loss of what do to from here. I can't believe toggling a system UI tuner setting could cause a catastrophic crash. How did you end up solving this? Were you able to flash the full factory image while preserving your data? I honestly have no idea what do to at the moment. I'm gonna have to use an older device and research this more after work.
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Ditamae said:
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described.
Click to expand...
Click to collapse
Interesting! Exact same order of events.
Ditamae said:
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Click to expand...
Click to collapse
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
_Ra1n_ said:
Interesting! Exact same order of events.
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
Click to expand...
Click to collapse
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
I did utilize the system UI tuner to disable my alarm icon from showing in the status bar, so I'm hoping I can perhaps find the file associated with the plugin specifically and rename that. Hmm. Only this is systemless... Might not be possible. This is my first rooted device without full read/write capabilities. Not sure how I feel about systemless.
Otherwise, other than time, the only bummer to all this is that I think I'm going to lose the Magisk module YouTube Vanced, as it's not longer supported.
Anyway, thanks very much for your help so far.
Ditamae said:
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
Click to expand...
Click to collapse
If your luck is as good as mine, you should be able to just plug in the device and enable file transfer (Settings > Connected Devices > USB > "Use USB For ... File Transfer."
Note that, as explained above, I had to remove my security PIN in settings before that worked, though.
_Ra1n_ said:
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
I was able to backup my data, and use Solid Explorer with root to search through system files. But, I don't see that directory. I see: data/data/com.android.systemui but no systemui.tuner. Any other idea where those systemui tuner files might be lurking? I'm an RN with a kindergartener home from school, and as much as I love tinkering with Android, now is not a good time.
_Ra1n_ said:
Interesting! Exact same order of events.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Ditamae said:
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Click to expand...
Click to collapse
Sorry for the slow reply. Unfortunately I'm mostly out of ideas.
I'd ask in the general Android Help subforum: https://forum.xda-developers.com/android/help
You'll likely get more eyes on the question (where does SystemUI Tuner store it's settings & how to reset them) and hopefully someone with better knowledge on Android settings/preferences can provide some incite.
Homeboy76 said:
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Click to expand...
Click to collapse
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
_Ra1n_ said:
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
Click to expand...
Click to collapse
@Ditamae Rain is correct. I have edited my post.