Database Info

Locked droid

Not sure if this is the place to get an answer, but I have a big problem. HelixLauncher has locked my Droid Getting a pop-up message: "Helixlauncher has stopped unexpectedly, please try again" with a small command window that says "Force Close". Touching Force Close just brings back the message again and no other commands are possible. Tried removing battery, but same issue repeats. Phone is currently unusable until I find a solution. Please help.

You could use adb to remove helixlauncher. That is, if you didn't remove the stock launcher.
adb remount
adb shell
rm /system/app/ whatever the name of the helix launcher app is
Click to expand...
Click to collapse

sounds like someone should have nanded ..... if whats posted above doesn't work, re-flash your rom.....take it as a lesson, nanding is your best friend

Your, ah, Droid? Not that I think you should be stoned and chased out for posting about something non-N1, but...
That aside, were you using just plain HelixLauncher or HelixLauncher2? The latter was developed for the N1 and, as I understand, doesn't play nice with Droids.

N1 in same trouble
Although tech savvy, still new to Android & N1.
Thought I needed HelixLauncher and installed it on to my N1 w/ 2.1 u1. Was working ok, but I decided to drop screen size to 1.
It's also possible, but unsure about this, that I tried installing HL2.
In short ended up with unending prompt and the same issues as listed in original post.
Looking into resetting, using pwr+vol.dwn. Is that what was meant by re-flashing, or that's something harsher? Couldn't find what 'nanding' means.
Also, the N1 is not rooted, whatever that means again.
Ended up eventually resetting phone to factory values. Reconfiguring phone now..

Actually, if you're fast enough you can stop this fc loop.
You need to get to Settings | Applications | Manage Applications and then clear the defaults for HelixLauncher so that you can select the regular launcher.
But how with constant fc? I did it this way:
When HL fc's it will briefly throw you out to the last screen you had active before it tries to reload (you only get half a second or so). The time that you do get should be enough to enter one or so commands... so after fc #1, press close then quickly hit the menu button and 'Settings', HL will launch again and fc again, after pressing close you should see the settings page, hit Applications, HL will launch again and fc, press close and hit Manage Applications... etc, etc.
Painful but perhaps better than a rebuild if you have no other way.
YMMV

Yeah, I tried, but wasn't fast enough. It's like the wild wild west.. the slowest gun lost.
It seems either Android or the launcher should offer a more graceful bailout in scenarios like this. Seems like a serious bug to me. And I've written a few of those myself..

EkoTonic said:
Yeah, I tried, but wasn't fast enough. It's like the wild wild west.. the slowest gun lost.
It seems either Android or the launcher should offer a more graceful bailout in scenarios like this. Seems like a serious bug to me. And I've written a few of those myself..
Click to expand...
Click to collapse
lol, yeah, the gun slinging took me a bit of time!
And the problem is a recognised one BUT the instructions are clear... wipe the data before reverting from Helix to stock and when upgrading roms... the dev has tried to put failsafes in but short of deleting the data there are few options...
But, since the warning is in place, I don't think we can call it a bug, rather an understood limitation... painful nevertheless.
PS - if you've got Set CPU installed you could try and get to that and set your speeds a low as possible, this will give you more time... still requires the gun though.

Did you install it as a system app? Launcher2.apk ?

The suckiest option is to always do a factory reset, as long as you didn't flash the helix launcher. This will delete the Helix Rom, but it will also delete everything from your phone. Proceed with caution!

britoso said:
Did you install it as a system app? Launcher2.apk ?
Click to expand...
Click to collapse
Installed from app store. Went searching for Helix and got 2 versions. Installed 1st and was trying to figure out how much I liked it. Noticed it made things faster, so I was loving that. But then decided to see if settings->scrn size option allowed me to jam more apps on the front page. So, I was playing with that, I believe {set it to 1?}.
As I would be hitting the Home page, it kept asking me how I wanted to complete that action, Default or Helix? So, I made Helix the default action. Then at one point, I was unable to return to the Home page.
Misery followed..
Now, I see from djmcnz's posting that there is supposed to be some sort of warning somewhere, but none on the App store intro of the app.
In either case, imho, it's not ok for an app to risk this kind of loss of functionality, not to mention data.
FYI, I have not left any of the negative comments that show in the app store. I understand the developers behind this app are proud of their work and rightly so. I however will not risk it again. It's not that important to me to be bleeding edge.

EkoTonic said:
Now, I see from djmcnz's posting that there is supposed to be some sort of warning somewhere, but none on the App store intro of the app.
Click to expand...
Click to collapse
Yes, sorry I was referring to notices in this forum.

de-crapify the doubleshot!

I have rooted my phone, MT4GS, and discovered the /system/app with all the things that are installed and some that are not installed on the phone. These include all the CRAP that I will never use. (teleNAV, friend feed, Zino reader, etc.) I have copied off the contents VIA SD and removed about 33MB if files. Most were pretty obvious. I will include a list. I have made the assumption that if I remove select apps and reset (to factory) my phone, the removed apps will not be installed thus de-crapifying my phone. I would like to know from those more knowledgeable on Android that myself if I am correct. Here is a list of files I have selected for removal. As far as I can tell there is nothing too important, just all the apps I don't use and don't want.
Any thoughts or suggestions would be greatly appreciated. Thanks.
(can provide the rest of the list if needed, i.e. those to be kept)
Bejeweled2_trust5.apk
com.htc.FriendStream3DWidget.apk
com.htc.FriendStream3DWidget.odex
com.htc.TrendsWidget.apk
com.htc.TrendsWidget.odex
com.htc.Twitter3DWidget.apk
com.htc.Twitter3DWidget.odex
com.mobitv.client.tmobiletvhd.apk
desktopPointer-signed-v6.apk
Flickr.apk
Flickr.odex
FriendStream.apk
FriendStream.odex
HtcTwitter.apk
HtcTwitter.odex
Jazz.apk
MobileBackup.apk
MyAccount.apk
MyReportAgent.apk
MyReportAgent.odex
netflix-17-release-android-marketplace-upgrade.apk
qik.apk
slackerradio.apk
TmobileAndroidDeviceCarbon-c42-n123.apk
TMOUS_Navigator.apk
ZinioReader.v2.03.3312.Regular.apk
ZinioSettingsProvider.v2.03.3198.TMobile.Smartphone.apk

If you factory reset using the pdimg59.zip then they'll all be put back on.
Sent from my MT4GS running Bulletproof

Where is that file? I did a search and didn't find anything....

There was also an excellent write-up done in the apps section. It's no longer updated and is kind of buried on page 3 but it's still a great place to start.
http://forum.xda-developers.com/showthread.php?t=1222672

Thanks for the help. I used the bloater apk from the thread. The only thing it would not let me uninstall was Netflix. It's funny also that the MP3 and video trim programs don't show up to be installed, the mysketch, and a few other apk files that are in the app folder.

I will be taking over bloater within the next few days.
Expect it to be updated to include a lot more.
I depreciated the thread siani_8 linked to because of the sticky I have in the developers section.
The sticky hasn't been updated in a while because:
1 - what's there is solid, and useful.
2 - no one else has posted app descriptions.
If other people are willing to post descriptions of what the apps actually do in the thread, i'll update that into the actual reference posts.
I figure that i've set the stage for the rest of the info to be put in, and i've done that much so far. If the community is interested in having descriptions posted, then the community at large will provide them.
The app reference is what inspired Romanbb to write that awesome Bloater app, and what we've all learned since then means more to be added. Bloater is very high on my project list, and it will be included in the new version of Bulletproof just like the last.
Also, that thread that got depreciated is from way back when - right after we first got S-OFF and were able to start deleting useless garbage we were all sick of being stuck with.
Definitely read through it if you are working on this from the ground up, because you'll see how we started to learn what we know today. It's a great exercise, and you'll learn a lot about your phone approaching it by playing along instead of just skipping to the end result.
Any questions feel free to ask, we're all here to help.

I need to add your thread in the compendium too. Its a good write up blue, I can't believe I missed it.
sent from my Agent Orange MT4G Slide using xda premium

I still can't find anything on this pdimg59.zip. Can anyone shed some light on it?

I think what you're referring to is the Stock ROM.
Easy answer:
Think of it like a failsafe for your device. If there is a file by that name on the sdcard, the phone will try to flash it on boot.
It's a more in depth answer then that from a technical perspective, but for just a quick "what is this?" that'll suffice. Someone with more time on their hands will probably come through here to expand on that if you're still curious.

To really decrapify your phone, just delete Rosie and HTCSense from /system/app. Just install another launcher app first.

Blue6IX said:
I think what you're referring to is the Stock ROM.
Easy answer:
Think of it like a failsafe for your device. If there is a file by that name on the sdcard, the phone will try to flash it on boot.
It's a more in depth answer then that from a technical perspective, but for just a quick "what is this?" that'll suffice. Someone with more time on their hands will probably come through here to expand on that if you're still curious.
Click to expand...
Click to collapse
sent from my Agent Orange MT4G Slide using xda premium

[Q] HTC Keyboard on CM7

Simple enough. After a long time of searching here and elsewhere, I have found no way to install the official HTC_IME keyboard on a ROM that doesn't already have it. Any attempts to do so just cause a Force Close upon trying to interact with it in any way.
And do not bother saying "just try _____ instead". If I wanted to try a different keyboard, I wouldn't be posting this thread.
I have a logcat that says "Unable to instantiate activity ComponentInfo", which I read is a problem with activities not being defined in AndroidManifest.xml. But unfortunately, the AndroidManifest.xml that comes with HTC_IME is junk. Trying to open it in any program either shows you what looks like non-western encoding, or it won't open it at all.
If anybody has any insight, that would be delightful. Either something I could try to make it work, or providing the logcat that shows all the errors that popped up, or something. Anything to finally get the Sense 3.5/3.6 HTC_IME working on our phones.

If nobody has any idea about this, does anybody at least know how I might go about figuring out any aspects of this problem besides the shot-in-the-dark Googling I've been doing trying to figure this out?
Just in case, I have attached the aLogcat file that I saved, filtered by the app to just show errors (which in this case, is only the errors generated by trying to access the keyboard via the Settings menu). If desired, I can generate and attach one for when you try to actually activate the keyboard via the Input Method operation.

I took the HTC IME apk from the HD revolution rom (system/apps) and pushed it onto my sensation's Virtuous Inquisition and I got it working except for the swype part.

I tried that. But unfortunately, CM7 is definitely missing libraries and/or other files needed by the apk file. Virtuous would be likely to have them because it's built from a Sense ROM, as opposed to CM7 most definitely *not* being built from anything but pure Android.
Someone had thought they found all the files needed to use the keyboard, but trying that did nothing for me, which means either more files are needed, or maybe something has to be done with the very messy and nearly uneditable AndroidManifest.xml file. But it seems that nobody on the forums has any idea. I had rather hoped that a developer might at least know, but of course I appreciate any input.

Would this work?

I'm not sure, but I'm certainly going to download it and give it a shot. Whether it works or not, thanks for the heads up. You've reminded me that I should also look around the forums of other qHD HTC phones in case somebody has figured something out in one of those.
Edit: Bah, of course the download link doesn't work. Every time I try, ESET kicks in and complains. Even when I shut it off. And once I finally got ESET to shut up, IE just refused to download the file anyway.

nvm i signed up for swype beta lol.

[Research] Stock Samsung Apps Catalog & Documentation

Hey guys, as part of my current work on producing a nice modified version of the "stock" firmware for the T-Mobile variant of the GT PLus, the SGH-T869, I have taken the approach of producing what I hope is decent documentation of my entire build process. Part of that has been cataloging all apps included with the "stock" ROM. I've got a very good start in finding at least a cursory explanation of what each app does and what effect removing the app has on the device.
I've been able to remove an alarming number of apps with no apparent ill effects, so at this point I'm turning to you, the XDA community, for assistance in figuring out what the remaining items do.
I have a publicly-viewable Google Docs spreadsheet here.
This spreadsheet is basically a list of every APK present in /system/app on the SGH-T869_TMB_T869UVLG7_T869TMBLG7 firmware, which appears to be the most recent ICS firmware for the USA T-Mobile version. I have backed up all files to an account I set up on Android File Host, and begun the process of linking them into the spreadsheet for easier reference.
As of now the following items are basically a mystery:
-ClipboardSaveService.apk
-CSC.apk
-DSMForwarding.apk
-DSMLawmo.apk
-FTC.apk
-FTM.apk
-FTS.apk
-Keychain.apk
-MobileTrackerEngineTwo.apk
-OmaCP.apk
-OmaDrmPopup.apk
-PanningTryActually.apk
-PCWClientS.apk
-Personalization.apk
-Phone_Util.apk
-PopupuiReceiver.apk
-PRUI.apk
-SecOmaDownloadProvider.apk
-etc
The intent with this document is to serve as a reference for people working with the "stock" Samsung firmware.
If you have any info you'd like to contribute, post to this thread or PM me
Also, I'll need "alpha" testers of my ROM in probably a week.
My initial release is planned to be simply a fully "optimized" copy of the stock ROM, with about 400MB of stock bloat removed, all remaining system apps deodexed and zipaligned, su and SuperSu, and probably some minor aesthetic mods added (1% battery and a themed notification bar).
The primary goal is to produce a nice stock-based ROM for the T869 (which doesn't have a lot of ROM options at present) and also to give the community a nicely documented guide on what I did, which may prove helpful to other would-be ROM makers.

a lot of these are 0MB or 0kb in size, or very small... eg.100kb or so.
You could always decompile these apks, would help you figure it out.
CSC.apk is Customer Service Configuration, or Country Code eg. KOR, XME, EUR
MobileTrackerEngineTwo is reponsible for tracking the device.. Samsung Dive, etc.. I believe.
Panningtryactually.apk involves tilting the device to scroll, etc. this .apk is just for thatwith pop up messages, etc.
Personalization.apk is directly related to CSC. This is the apk that will let you change your CSC I believe.
clipboard save service is obvious, I would keep that.
The others Im sure we could figure out.
I disabled a lot of stock apks and removed readers hub, and my device is pretty fluid as it is.

Awesome, thank you for the information!
I was planning on adding a column for file size into the spreadsheet next, so that bit should become obvious.
I'm pretty sure the ClipboardSaverService is actually a supplemental thing that allows you to "save" clipboard items so you can have multiple items in a stack, because the stock Android clipboard functionality has been working perfectly fine on its own with ClipboardSaver removed.
The more I get to know how the Samsung stuff is built, the less impressed I am by it. Almost all of the "new" stuff they add to their ROMs seems like solutions to problems that don't actually exist. The tilt-to-scroll thing was cool for about an hour, until I tried to use the tab on a bus and kept accidentally triggering it.
So far, with all the stuff uninstalled, I am getting really good battery life from my tab.I'm at 77% after 13 hours of discharging. Now, that's light internet use for a few hours and then sleeping for like 5 hours, but still. It's basically just as good as anything I was seeing from CM10. Work was crazy yesterday cuz we had some people missing, but today should be much less busy so I'll have time to chug away on the spreadsheet some more.
Anyone have any solid idea what Keychain.apk actually does? The name would imply that its some sort of secure storage manager that holds user credentials, like Keychain in Ubuntu and Mac OS X. However, I'm not entirely sure what that would mean in the context of Android. Maybe to manage passwords saved in the browser? I'm gonna have to probe a bit more to find out what it does, probably.

Scratch that theory about the ClipboardSaverService. That special GUI is only present on the stock "Internet" browser, and is present & working even with ClipboardSaverService removed.
Got a few bits of helpful info over here http://www4.gsmspain.com/foros/attachment.php?postid=12686608

there was a few good lists here on xda... also if you have time, learn to decompile these have a peek at some images and .xmls, you should be able to figure them out.
cheers.

FWIW, whenever I see FTM, I think Factory Test Mode.

I ended up "re-stocking" my GT-P7510. which apparently shares roughly 95% of the same APKs.
I have also finally found some actual negative consequences from removing "all" the Samsung stuff, attempting a download in my stock browser currently causes the app to crash.
This should help determine what at least one of the "mystery" APKs actually does

I don t know what the above mentioned "mysterious" apks are, but what I know is that I removed all of them already a while ago, and my p6210 works like a charm. But it s a wifi only model, for 3g models apks that are phone related shouldn t be removed, for obvious reasons...

[HOWTO] Show lockscreen before launcher after reboot.

Hi,
Since android started to use keyguard as separate package, one bug always disturbed me: When device boots, it shows the launcher with home screen and then in couple of seconds the lockscreen.
To my surprise, when i start to work with Note 4 ROM I've discovered the absence of such bug! Lockscreen shown first after animated boot logo.
So, here is the fix.
You need to decompile Keyguard.apk by Apktool and then in AndroidManifest.xml replace:
Code:
<application android:label="@string/app_name" android:largeHeap="true" android:persistent="true" android:process="com.android.[B][COLOR=Red]systemui[/COLOR][/B]" android:supportsRtl="true">
to (note the red part)
Code:
<application android:label="@string/app_name" android:largeHeap="true" android:persistent="true" android:process="com.android.[B][COLOR=Red]keyguard[/COLOR][/B]" android:supportsRtl="true">
Then compile Keyguard.apk and push it to device (/system/priv-app).
From now, keyguard will have its own process and won't affect SystemUI even if FC (the same SystemUI won't crash Keyguard if FC).
Probably, this bug belongs to Samsung. I think most pre-Note4 devices with KitKat are affected and can be fixed as shown above. The line can look a little different, but you should find the first red part and replace by second red part without touching anything not red.
Devs can freely use this fix without permission. Just give a proper credit.

big thanks @sorg, finally someone tried to fix this problem that only a few users note.. so now the lockscreen appears immediatly?

rickyy22 said:
so now the lockscreen appears immediatly?
Click to expand...
Click to collapse
As i've wrote above, lockscreen is the first thing u see after animated boot logo.

Will report to you when I get around to Testing this.
I cannot believe so many ROM Devs over look this. This happened to me today after a Dalvik/Cache wipe.
After "Android is Upgrading" message was over, the Phone showed the Launcher/HomeScreen and then the Lock Screen show after 2 seconds.
This is very unprofessional. ROMS with this issue should never be allowed to ship with this "feature". This is akin to your arrive at your house, your front door opens, so everyone can see inside, then quickly closes, and then you have to use your key to get in.
Thanks for your post,
Kind Regards.
sorg said:
As i've wrote above, lockscreen is the first thing u see after animated boot logo.
Click to expand...
Click to collapse

just tested on Keyguard.apk from OEM G900FXXU1ANJ1 build, unfortunately this doesn't work it kills the keyguard completely and causes errors with the fingerprint sensor.

Had trouble even compiling the apk, something about my machine and java not liking each other perhaps. But the rest of my stuff works so...if I'm not sure what's broke.... Then what I thought was done (compiling process froze), looks like it didnt work here either on CM 11, Complete fail to even boot the first time. No message, nothing. Wipe Dalvik, Put backup APK, then Force closes next time around. I may have more than 1 problem though. Whatever this bug is, its a major oversight on the way KitKat works, and it looks unprofessional in the face of competing products. Why do you think they let this Slip?

cstayton said:
just tested on Keyguard.apk from OEM G900FXXU1ANJ1 build, unfortunately this doesn't work it kills the keyguard completely and causes errors with the fingerprint sensor.
Click to expand...
Click to collapse
Since you are "recognized developer", i think you should have more experience to track the problems than just describe what you see. At least you can look into logcat to check what exactly causes the problem. May be old settings (data folder) of keyguard conflicts with new process id.
Generally speaking, my SHV-E330S is the same as your SM-G900F. Even ROMs from G900F with some tweaks can work on my E330S device. Thus, I think this tweak should be compatible. There is a little chance that fingerprint service prevents it from working, but i really doubt.
If you believe you made the change correctly, then make full backup of device (in TWRP or CWM), then do a master reset and check if problem still exists. Sometimes, if i see strange things, i do this way to make sure where the problem comes. And without checking logcat there is a little (if none) chance to understand where is the problem.

sorg said:
Since you are "recognized developer", i think you should have more experience to track the problems than just describe what you see. At least you can look into logcat to check what exactly causes the problem. May be old settings (data folder) of keyguard conflicts with new process id.
Generally speaking, my SHV-E330S is the same as your SM-G900F. Even ROMs from G900F with some tweaks can work on my E330S device. Thus, I think this tweak should be compatible. There is a little chance that fingerprint service prevents it from working, but i really doubt.
If you believe you made the change correctly, then make full backup of device (in TWRP or CWM), then do a master reset and check if problem still exists. Sometimes, if i see strange things, i do this way to make sure where the problem comes. And without checking logcat there is a little (if none) chance to understand where is the problem.
Click to expand...
Click to collapse
OK, first off log cats are eronious and rarely provide accurate reflection of issues that's why using the app log created in /data/log is prefered. Second your assuming I didn't check any logs. Third I did none where created. Fourth I am well aware of processes and how things work I have been a developer by profession for nearly 20 years.
I merely posted as a note that it did not work I did not ask for nor do I need support from you for your mod.
Thanks for your reply. :thumbdown:
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Ok, so aside from the little skirmish, if you fix this problem can you wake up the CM team and let them know about it?
It seems an overall KitKat CM based issue. It is not working in my Galaxy S2 Skyrocket, and not working in my Galaxy S3 D2LTE. I cannot even decompile the apk now, even though I have the proper tools and I can even use zipsigner to sign this thing right on the device if needed. However, I am having Java issues. So if you've got something that works, please post and make it known.
btw, no logs were created in /data
Phone simply stuck on boot is the result. CM Keyguard = Kaput.
cstayton said:
OK, first off log cats are eronious and rarely provide accurate reflection of issues that's why using the app log created in /data/log is prefered. Second your assuming I didn't check any logs. Third I did none where created. Fourth I am well aware of processes and how things work I have been a developer by profession for nearly 20 years.
I merely posted as a note that it did not work I did not ask for nor do I need support from you for your mod.
Thanks for your reply. :thumbdown:
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse

Hello.
My device device boots, it shows the lockscreen, before launcher with home screen.
So this issue has been solved, right ?

sorg said:
Hi,
Since android started to use keyguard as separate package, one bug always disturbed me: When device boots, it shows the launcher with home screen and then in couple of seconds the lockscreen.
To my surprise, when i start to work with Note 4 ROM I've discovered the absence of such bug! Lockscreen shown first after animated boot logo.
So, here is the fix.
You need to decompile Keyguard.apk by Apktool and then in AndroidManifest.xml replace:
Code:
<application android:label="@string/app_name" android:largeHeap="true" android:persistent="true" android:process="com.android.[B][COLOR=Red]systemui[/COLOR][/B]" android:supportsRtl="true">
to (note the red part)
Code:
<application android:label="@string/app_name" android:largeHeap="true" android:persistent="true" android:process="com.android.[B][COLOR=Red]keyguard[/COLOR][/B]" android:supportsRtl="true">
Then compile Keyguard.apk and push it to device (/system/priv-app).
From now, keyguard will have its own process and won't affect SystemUI even if FC (the same SystemUI won't crash Keyguard if FC).
Probably, this bug belongs to Samsung. I think most pre-Note4 devices with KitKat are affected and can be fixed as shown above. The line can look a little different, but you should find the first red part and replace by second red part without touching anything not red.
Devs can freely use this fix without permission. Just give a proper credit.
Click to expand...
Click to collapse
There is no keyguard.apk in lollipop 5.0.1 for e330s !!

Wipe Dalvik, Wipe Cache, Reboot. Then let us know. This happens from JB to KitKat. Not sure about Lollipop.
ionutmaruta said:
Hello.
My device device boots, it shows the lockscreen, before launcher with home screen.
So this issue has been solved, right ?
Click to expand...
Click to collapse

deleted

deleted

This method does not work. The information in OP is completely wrong.

sorg said:
Hi,
Since android started to use keyguard as separate package, one bug always disturbed me: When device boots, it shows the launcher with home screen and then in couple of seconds the lockscreen.
To my surprise, when i start to work with Note 4 ROM I've discovered the absence of such bug! Lockscreen shown first after animated boot logo.
So, here is the fix.
You need to decompile Keyguard.apk by Apktool and then in AndroidManifest.xml replace:
Code:
<application android:label="@string/app_name" android:largeHeap="true" android:persistent="true" android:process="com.android.[B][COLOR=Red]systemui[/COLOR][/B]" android:supportsRtl="true">
to (note the red part)
Code:
<application android:label="@string/app_name" android:largeHeap="true" android:persistent="true" android:process="com.android.[B][COLOR=Red]keyguard[/COLOR][/B]" android:supportsRtl="true">
Then compile Keyguard.apk and push it to device (/system/priv-app).
From now, keyguard will have its own process and won't affect SystemUI even if FC (the same SystemUI won't crash Keyguard if FC).
Probably, this bug belongs to Samsung. I think most pre-Note4 devices with KitKat are affected and can be fixed as shown above. The line can look a little different, but you should find the first red part and replace by second red part without touching anything not red.
Devs can freely use this fix without permission. Just give a proper credit.
Click to expand...
Click to collapse
how to make the galaxy s5 has Keyguard.apk ?

I can see this is bothering a lot of people. I am still working on it. If I have good news I will post it here. The OP of this thread gave VERY little information on what is to be actually done. If I get this figured out, I will post a whole new thread with instructions on how to do it.

ocd_amp said:
I can see this is bothering a lot of people. I am still working on it. If I have good news I will post it here. The OP of this thread gave VERY little information on what is to be actually done. If I get this figured out, I will post a whole new thread with instructions on how to do it.
Click to expand...
Click to collapse
thank waiting

After spending close to 3 hours on this, and meticulously looking at every line, every resource, I think this is a closed source issue. I am coming to a conclusion that Cyanogenmod steals, borrows, hacks, bribes, whatever it takes to get their product out as fast as possible without proper testing. I am willing to bet this issue affects thousands of CM11 users that are out there. Every single person I know on Kitkat with a Samsung phone has this problem. I am sorely disappointed with this and I find it hard to believe that many ROM devs have been quiet about it. For now, there is nothing I can do unless someone with higher knowledge comes in here and guides me so I can fix this problem for everyone.