Related
Anyone know the .apk name of the nexus lock screen in the system/app folder?
Jboxen said:
Anyone know the .apk name of the nexus lock screen in the system/app folder?
Click to expand...
Click to collapse
I dont believe there is a apk for it as if you remove htclockscreen.apk it gives you the n1 lockscreen.
droidkevlar said:
I dont believe there is a apk for it as if you remove htclockscreen.apk it gives you the n1 lockscreen.
Click to expand...
Click to collapse
Right. I did that in evil Eris 2.0 and it has a background picture rather than being transparent. I'm trying to locate the .png it is loading so I cam change it to a transparent one.
Jboxen said:
Right. I did that in evil Eris 2.0 and it has a background picture rather than being transparent. I'm trying to locate the .png it is loading so I cam change it to a transparent one.
Click to expand...
Click to collapse
no one has figured out how to make it transparent again, i read it was being looked into. i prefer the background as it doesnt conflict with my htc clock on the home screen.
droidkevlar said:
I dont believe there is a apk for it as if you remove htclockscreen.apk it gives you the n1 lockscreen.
Click to expand...
Click to collapse
so if i remove the htclockscreen.apk from my eris it will just use the n1 lockscreen?
Macros617 said:
so if i remove the htclockscreen.apk from my eris it will just use the n1 lockscreen?
Click to expand...
Click to collapse
Yes this is true
Jboxen said:
Yes this is true
Click to expand...
Click to collapse
this may be going a bit out of the way but how do i remove it?
Macros617 said:
this may be going a bit out of the way but how do i remove it?
Click to expand...
Click to collapse
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I choose to save it incase I want it for later)
reboot phone and you should see the changes.
(for EE2 users) Just so you know, as of right now, you can not change the image for the Nexus Lockscreen. (I have tried a few times and for whatever reason it will not accept the change, it sends my phone into a loop)
dianeofarcadia said:
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I choose to save it incase I want it for later)
reboot phone and you should see the changes.
(for EE2 users) Just so you know, as of right now, you can not change the image for the Nexus Lockscreen. (I have tried a few times and for whatever reason it will not accept the change, it sends my phone into a loop)
Click to expand...
Click to collapse
before i do this what's ee2 user? I have the eris on 2.1 leak 3
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I cho
Click to expand...
Click to collapse
before i do this what's ee2 user? I have the eris on 2.1 leak 3
Click to expand...
Click to collapse
EE2= evil eris 2, it's a rom for those that are rooted. If you are on the leak, no root, then you can't make this change.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Ah alright thanks though
-------------------------------------
Sent via the XDA Tapatalk App
Has anyone talked to konikub or spencer about it?
-------------------------------------
Sent via the XDA Tapatalk App
dianeofarcadia said:
using root explorer
go into system>app>
long press on HtcLockScreen.apk
choose move and paste on your sdcard or you can choose to delete.
(I choose to save it incase I want it for later)
reboot phone and you should see the changes.
)
Click to expand...
Click to collapse
So if HTClockscreen.apk was deleted... anyway to get it back?
i tried to delete it with root explorer but it is saying it is a read only and i cant delete it...
i tried to delete it with root explorer but it is saying it is a read only and i cant delete it...
Click to expand...
Click to collapse
Make sure you have read/write mode on. You can also remove using adb
Sent from my JACKEDZ v1.1 using Tapatalk
droidkevlar said:
Make sure you have read/write mode on. You can also remove using adb
Sent from my JACKEDZ v1.1 using Tapatalk
Click to expand...
Click to collapse
im not very familiar with android...just bought the phone and just got the root explorer so im not sure how to do the read/write mode on thing
jpen said:
im not very familiar with android...just bought the phone and just got the root explorer so im not sure how to do the read/write mode on thing
Click to expand...
Click to collapse
Using rootexporer, just open the folder you want to remove the apk, at the very top, you will see it says mounted as r/o and then a button that says mount R/W. Hit that button. Now you can remove/edit files in that dir.
Piece of advice. If you are truly interested in learning your phone, look into adb commands. There are a few programs listed on this forum that do it for you or you can learn the commands yourself and just enter them via cmd line.
This will only work if your phone is rooted correct? Won't work on nonrooted or leak v3?
nesgodawg said:
This will only work if your phone is rooted correct? Won't work on nonrooted or leak v3?
Click to expand...
Click to collapse
is he right? cuz im not rooted i just have the official 2.1 and yea im not seeing the mount R/W option..
Yeah, after doing some research it does turn out you have to be rooted. I'm trying to adb my phone now and keep getting blocked out.
You have to root first.
1. Change input method to any other keyboard.
2. In the /system/app folder, delete Swype.apk
3. In the /system/lib folder, delete libSwypeCore.so
4. In the /data/data folder, delete the com.swype.xxx folder
5. In the /data/dalvik-cache folder, delete the [email protected]@swype.... file.
6. REBOOT OR IT WON't INSTALL PROPERLY
7. Install and run the swype beta installer and follow the on-screen instructions. Installer link here http://db.tt/cD8HXlI
You also can rename the files to .xx.bak so you have a backup. This works 100% for me on Com Rom 2 after just installing today so I don't know how this will work on systems that have been used daily for a while.
I take no part if none of this works and permanently deletes swype from your phone. Your own fault.
Credit to google leading to this post by Snow02 on droid x forums
What exactly is it?
Sent from my SCH-I500 using XDA Premium App
A keyboard
Sent from my SCH-I500 using XDA Premium App
Its the newest version of swype. I was running it when I was using JTs CM7 but I thought it was worse then our TW swype.
Sent from my SCH-I500 using Tapatalk
representingcochran said:
Its the newest version of swype. I was running it when I was using JTs CM7 but I thought it was worse then our TW swype.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
How is it worse?
Its not I just swyped this from 3.0 I personally think its better I didn't make a single mistake while writing this when I usually do with older versions.
Sent from my SCH-I500 using Tapatalk
tonu42 said:
Its not I just swyped this from 3.0 I personally think its better I didn't make a single mistake while writing this when I usually do with older versions.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I completely agree with you, its a complete improvement from the last version. The word suggestion window is gone and moved to a frame above the keyboard, word prediction is way more accurate, swyping is more accurate, etc.
I'm a big swype user, so thanks for the instructions...may give this a whirl.
Where can I find the swype beta installer?
Sent from my SCH-I500 using XDA Premium App
http://beta.swype.com
The biggest change (other than tablet support) with Swype 3 isn't even the much improved suggestion window or the faster and more accurate swiping: it's that Swype now does predictive tapping too.
No more need to switch between Swype and the stock keyboard or SwiftKey if you aren't in a swiping mood. That's why their tagline for 3.0 is - and I'm not making this up, just watch their promo videos - "Stroke it AND poke it."
So what color is the new swype?
Edit: My sywpe expired so im being forced to update. Instructions worked perfectly thnx.
Thanks for the instructions. Worked perfectly. Now to get used to the slightly different interface...
Thanks for putting this little tutorial out there cuz after updating to UKB2.1 the swype keyboard stopped working
I admit I might not the most brainy person when it comes to this
Had a heck of a time figuring out how to remove those system files... finally resorted to Root Explorer (paid app) to remove these files (I am sure there was a way to do it without, but I refer you to the above comment)
For some reason the swype beta likes to be authenticated twice...
and after the second authentication process, I made sure to reboot before using the keyboard...
so far it is working and I like the new keyboard... (I had better since it would take me another whole afternoon to figure out how to install the old swype keyboard)
thanks again and keep up the good work
jabberjaw said:
Thanks for putting this little tutorial out there
Click to expand...
Click to collapse
+ 1 - thanks button was hit
jabberjaw said:
Had a heck of a time figuring out how to remove those system files... finally resorted to Root Explorer (paid app) to remove these files (I am sure there was a way to do it without, but I refer you to the above comment)
Click to expand...
Click to collapse
Glad you got it worked out, but wanted to let you know not to feel bad about going to root explorer. You will likely find that you have a lot of uses for it - there is a LOT that goes on round here that having root explorer makes life a lot easier to follow...
Enjoy!
I just updated to 2.1 and my swype crapped out on me too. I've tried everything to get it working, but nothing works.
I've been trying to delete the swype.apk and other files instructed here, but they won't delete. 'don't have permission," "read only" or "Cannot Delete." I'm using Root Explorer too, and trying to switch Mount r/o to r/w, and it won't change! Someone help me! I'm going through Swype withdrawls already!
What program is everyone using to locate and delete files?
BTW, I've switched keyboards before I try to delete, still no luck.
neotrixy,
i remember having similar difficulty
try changing [mount r/o] button before you select the app you want to delete,
couldn't find a another protected system app to delete to try this again, but I was able to switch the mount button back and forth by pressing the grey button at the top of the screen
hope this helps
ps- i did find that someone posted a swype fix in the UKB thread (not sure if it works)... it is way back in the thread... but i had already switched to beta before i found it
No, i think already mentioned, for whatever reason, the button won't change to r/w. It's stuck on r/o. I don't know what the problem is, I've never had a problem like this before.
Thanks for the help though!
Any other ideas?
I think i got it fixed...I downloaded a newer version of Root Explorer, and it let me change the r/w.
Thanks guys!
ok,
It sounds like your Root Explorer program has not been granted superuser permissions yet.
I can't remember when it asked for those permissions, check in your superuser icon to see if Root Explorer is listed in there and has a green circle next to it.
I have been looking in looking around in the Root Explorer menus but don't see anything
I hope it is as easy as clicking the allow button in superuser, if not my other thought would be to uninstall and reinstall Root Explorer to see if it will ask for superuser permissions when you open it up.
good luck
Yes
Thanks for your help. I was so frustrated with Verizon having made that (or so they thought) permanent. That is so stupid they want their people stuck with an old version. Appreciate all your help. God bless in Jesus' Name.
Sorry should have posted here in first place
Hi all
Eventually........have rooted KFHD then got brave and installed Google Market....only issue is that KFHD will not auto rotate and bottom menu bar is missing.
Any help please?
Download LMT https://www.dropbox.com/s/h7xwelcg8uzyaee/LMT_v1.91.apk.... Install.
Open and choose start service. Click the pie tab at the top and configure your pie items. (eg. Pie item 1, set to home. Pie item 2, set to back. Etc)
If you want the stock softkeys/navbar back then do this next:
Download ES File Explorer here https://www.dropbox.com/s/u227um3vt3o2yzx/ES.apk
Install and open. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back.
Sent from my KFHD using xda premium
Visual help.
Sent from my KFHD using xda premium
Krsmqn said:
Download LMT https://www.dropbox.com/s/h7xwelcg8uzyaee/LMT_v1.91.apk.... Install.
Open and choose start service. Click the pie tab at the top and configure your pie items. (eg. Pie item 1, set to home. Pie item 2, set to back. Etc)
If you want the stock softkeys/navbar back then do this next:
Download ES File Explorer here https://www.dropbox.com/s/u227um3vt3o2yzx/ES.apk
Install and open. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back.
Sent from my KFHD using xda premium
Click to expand...
Click to collapse
Thanks for reply Krsmqn.
I have downloaded and installed LMT. Set pies to menu, back etc I already have ES File Explorer installed.
Now i get lost ............. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back...........
Sorry for being thick but can you please explain this part a bit more?
Many thanks
fs1023
found .....Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back...........
It is already set at 0
Krsmqn said:
Visual help.
Sent from my KFHD using xda premium
Click to expand...
Click to collapse
I have gone to Pie and set menu etc but how do i set permissions?
Sure.
I assume that one of the pie keys have been set to the menu option.
Check the pictures below.
The first picture is the settings bar. Choose settings.
Scroll down to "root settings" (see second picture near the bottom)
Open root settings and make sure all are checked, 3rd picture (4 or 5 boxes, depends on version) and grant su permission.
Navigate to the /system/ folder as seen in 4th picture.
click on build.prop and choose ES Note Editor, as seen in 5th picture
Find the code I point out in the 6th picture and carefully change the 1 to a 0 by clicking on the screen. If it already says 0, then we need to get you the softkeys.apk.
lets try this first.
Sent from my KFHD using xda premium
Exuse my ignorance....i get picture 1 but where are the others from? KFHD menu?
fs1023 said:
Exuse my ignorance....i get picture 1 but where are the others from? KFHD menu?
Click to expand...
Click to collapse
The 2nd and 3rd picture are of the settings menu in ES File Explorer. The others are the ES File Explorer interface and the build.prop properties.
I see you found the qemu.hw.mainkeys and have found it set to zero.
Ok. lets try this...
Gimme a second to prepare the files.
Went through your instructions mate and that code IS set to 0
Before we have you download anything, let's make sure you need to.
Open ES File Explorer and navigate to the /system/app/ folder. Look to see if you have "SoftkeyBar.apk" installed.
Yes mate its a square grey box with 'Kindle' written on it.
BTW how do I buy you a beer for your help?
fs1023 said:
Yes mate its a square grey box with 'Kindle' written on it
Click to expand...
Click to collapse
Hmm... I'm puzzled. There's no reason for you to have no softkey bar.
Go back to Build.prop file in /system/
Sometimes there's a second entry of "qemu.hw.mainkeys=1" in there. Look for it.
Could you also let me know what method you used to root?
---------- Post added at 02:35 PM ---------- Previous post was at 02:32 PM ----------
fs1023 said:
BTW how do I buy you a beer for your help?
Click to expand...
Click to collapse
I appreciate it but I quit drinking some time ago. Just knowing that I helped is enough. I've been blessed with outstanding help on these forums before, so I just want to pay it forward.
There is no 'second entry of "qemu.hw.mainkeys=1"
The qemu.hw.mainkeys=1 is qemu.hw.mainkeys=0 on my Kindle is this correct?
I rooted through Kindle firste aide step 21. Admitttidly it took me 4 times. I can/could not do a clean 'unroot' and in one instance it rooted the device again. Do you think i have corrupted files?
fs1023 said:
There is no 'second entry of "qemu.hw.mainkeys=1"
The qemu.hw.mainkeys=1 is qemu.hw.mainkeys=0 on my Kindle is this correct?
I rooted through Kindle firste aide step 21. Admitttidly it took me 4 times. I can/could not do a clean 'unroot' and in one instance it rooted the device again. Do you think i have corrupted files?
Click to expand...
Click to collapse
Yes, qemu.hw.mainkeys= # is the code. 1 or 0 is just the number that identifies the different state. So it's all good.
As far as why your nav bar isn't showing up...... I dunno. You have now passed the realm of which I can be of assistance.
I suggest you post your problem on the Kindle Fire First Aide thread. Be sure to include the information we have already covered to save some time.
I'm sorry I couldn't help you resolve the issue, but Chris (prokennexusa) and those guys on that thread will get you sorted out.
Good luck!
Ok thanks for all you time and help it has been most appreciated and keep up the good work in helping others.
regards
fs1023
Krsmqn said:
Yes, qemu.hw.mainkeys= # is the code. 1 or 0 is just the number that identifies the different state. So it's all good.
As far as why your nav bar isn't showing up...... I dunno. You have now passed the realm of which I can be of assistance.
I suggest you post your problem on the Kindle Fire First Aide thread. Be sure to include the information we have already covered to save some time.
I'm sorry I couldn't help you resolve the issue, but Chris (prokennexusa) and those guys on that thread will get you sorted out.
Good luck!
Click to expand...
Click to collapse
Hi all
Can anyone follow on from Krsmqn and help me with my problem?
Sent from my KFTT using Tapatalk 2
fs1023 said:
Hi all
Can anyone follow on from Krsmqn and help me with my problem?
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
Sent from my KFTT using Tapatalk 2
Krsmqn said:
Download LMT https://www.dropbox.com/s/h7xwelcg8uzyaee/LMT_v1.91.apk.... Install.
Open and choose start service. Click the pie tab at the top and configure your pie items. (eg. Pie item 1, set to home. Pie item 2, set to back. Etc)
If you want the stock softkeys/navbar back then do this next:
Download ES File Explorer here https://www.dropbox.com/s/u227um3vt3o2yzx/ES.apk
Install and open. Open the menu (using one of the LMT pie buttons you created) scroll to the bottom. Choose root settings. Check all (grant su permission)
Navigate to /system/
Open build.prop with es note editor. Find the code "qemu.hw.mainkeys=1" change it to 0. Back to save and reboot. If it is already set at 0, then reply back. "
Sent from my KFHD using xda premium
Click to expand...
Click to collapse
I have always wanted to know how to change the DPI but I didn't want to fiddle around and softbrick I have a factory cable but hate to pull it out, Would you mind taking a screenshot of the line I have to edit for the DPI change?
Sent from my KFTT using xda app-developers app
Open build.prop with ES Note Editor (found in /system/)
Find the code below. Change it, back out without changing anything else. Save. Reboot.
Sent from my KFHD using xda premium
Forgot image. Here it is. Be very careful.
Sent from my KFHD using xda premium
Alright guys,
Pretty much what I'm after is a launcher shortcut which locks our gear.. The reason for this when using custom launchers the home/power button by default does not lock the device anymore.
It seems that particular feature was hardcoded into the TW launcher.
There are various applications available on the playstore, although I haven't found any which work on the gear as they require additional settings to be enabled in a traditional settings dialog.. which obviously we dont have.
If anyone has any ideas please post ! Or even better if you know of a app in mind which works !
Click to expand...
Click to collapse
EDIT:
jrdejavux said:
can you guys please post instructions thank you!
Click to expand...
Click to collapse
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
fOmey said:
Alright guys,
Pretty much what I'm after is a launcher shortcut which locks our gear.. The reason for this when using custom launchers the home/power button by default does not lock the device anymore.
It seems that particular feature was hardcoded into the TW launcher.
There are various applications available on the playstore, although I haven't found any which work on the gear as they require additional settings to be enabled in a traditional settings dialog.. which obviously we dont have.
If anyone has any ideas please post ! Or even better if you know of a app in mind which works !
Click to expand...
Click to collapse
Screen off and Lock
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
put a shortcut to the app and it'll lock your device
i'm now looking for a way to capture the 'home button' to run this app
karoolus said:
Screen off and Lock
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
put a shortcut to the app and it'll lock your device
i'm now looking for a way to capture the 'home button' to run this app
Click to expand...
Click to collapse
I tried this particular application, although it FC's here..
fOmey said:
I tried this particular application, although it FC's here..
Click to expand...
Click to collapse
yeah, you have to enable the device administrator somehow.. on my phone, it works just fine, now to get it to the watch
karoolus said:
yeah, you have to enable the device administrator somehow.. on my phone, it works just fine, now to get it to the watch
Click to expand...
Click to collapse
Yes im aware of that, you obviously didn't read the OP very well.. Thanks anyway..
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Brendo said:
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Click to expand...
Click to collapse
Genius. Worked a charm.. I sussed the keylayouts out previously.. I was looking at Generic.kl..
Modified Key 172 to POWER and it works a charm.
fOmey said:
Genius. Worked a charm.. I sussed the keylayouts out previously.. I was looking at Generic.kl..
Modified Key 172 to POWER and it works a charm.
Click to expand...
Click to collapse
Brendo said:
Can you try editing gpio-keys.kl in /system/usr/keylayout
I think that is the file that tells the os what hardware buttons do
btw this idea got me thinking about enabling mass storage, but I had no luck with the couple of apps I tried. I think kernel needs ums module
Click to expand...
Click to collapse
Awesome tag team. Works great with Nova!
How do you modify the key?
Sent from my SM-N900V using xda app-developers app
bosshogg38 said:
How do you modify the key?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Root file explorer.. Open the file as a text file.
can you guys please post instructions thank you!
jrdejavux said:
can you guys please post instructions thank you!
Click to expand...
Click to collapse
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
fOmey said:
MUST BE ROOTED
1. Push a Root File Manager or adb to your gear.
2. Navigate to "/system/usr/keylayout", Open/pull the "gpio-keys.kl" file.. Confirm any root permission popup's.
3. Modify "Key 172 HOME" to "Key 172 POWER", Using a text editor.
4. Save/Push changes.
5. Restart gear.
I like to use adb to pull the files I want to modify to my desktop, Modify them, Place them on the SDCARD of the gear and then manually place them using a root file browser to their original locations. Also remember to set permissions, Imitate any other permissions in the same directory.
Click to expand...
Click to collapse
Do you happen to have the stock file setup? I think I may have accidentally edited the wrong key, so now i have two lines with "Key 172 POWER".
MaTtKs said:
Do you happen to have the stock file setup? I think I may have accidentally edited the wrong key, so now i have two lines with "Key 172 POWER".
Click to expand...
Click to collapse
I do not, Although this is what it should look like:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
key 172 POWER WAKE
fOmey said:
I do not, Although this is what it should look like:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
key 172 POWER WAKE
Click to expand...
Click to collapse
Awesome. Thanks buddy.
MaTtKs said:
Awesome. Thanks buddy.
Click to expand...
Click to collapse
I can't get this to stick...I make the changes, and save, but when I go back in they are different again.
Using root explorer.
Sent from my SM-N900V using xda app-developers app
Guys,
Good day!
I have a lg l90 410hn and physical buttons stopped working and found a solution to enable the virtual buttons by editing the build.pro the system:
1st You need to have your mobile with root and have the Root Explorer app.
2nd Go to the System folder, hold the build.prop file until the menu appears.
3rd Select open with text editor
4th Go to the last line and write / paste it:
qemu.hw.mainkeys = 0
But when editing the build, the device appears problems:
1- The call does not work
2- the chipcard 1 does not work
3- some system applications are with the android icon and open and close.
Is there any way to edit the build.pro in KDZ file before sending for device?
I'm sorry for bad English!
Hmm, weird... Editing build.prop shouldn't cause such problems. Maybe you've done something wrong while editing it?
You can try other tools after a fresh system install to edit build.prop. I know Kernel Auditor can do it.
Sent from my LG-D410 using XDA Free mobile app
lfom said:
Hmm, weird... Editing build.prop shouldn't cause such problems. Maybe you've done something wrong while editing it?
You can try other tools after a fresh system install to edit build.prop. I know Kernel Auditor can do it.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
I solved my problem in parts using the swapper, but still not what I want. I will monitor the forum to find a solution !!
I used several applications to edit the build. After editing build the device presents problems