You can just replace the Keys, all Keys are Stickers
Uploaded with ImageShack.us
The device must not be opened !!!
Then copy these files to system/usr/keylayout/
http://www.share-online.biz/dl/18IWSTKMY76
I guess I should port the keyboard layout changer from MS1 to CM10.
Just saw this thread today:
Awsome! Now the Q is really complete!!
Stupid question of the day :
Which program do you recommend to copy the files into /system/usr/ ? Androxplorer obviously can't do it, i need a program with Root access, right ?
EDIT : Used Rootexplorer, and this worked. However, i still don't get the German keyboard layout ? How do i activate this ?
after overwriting the files you have to reboot your device.
I use ES Explorer for stuff like that.
Sent from my XT897 using XDA Premium 4 mobile app
gehstock said:
You can just replace the Keys, all Keys are Stickers
Click to expand...
Click to collapse
damn, how nice. but i really miss the ö, ä, ü and ß key on the photonq, because i mostly write in austrian dialect, which has much umlauts.
(jetzt seh ich grade, du heißt gehstock. wie gehts dir ohne umlaute?)
with well modified keyfiles you can access Umlaute by double pressing the Vokal. ß by double pressing s ;p
very handy
Sent from my XT897 using XDA Premium 4 mobile app
Afaik only on Skrilaz_CZ builds with multipress feature.
Not CM default feature.
Correct me if I'm wrong.
could be right. I've never used a non skrillax build
Sent from my XT897 using XDA Premium 4 mobile app
Sorry guys, i tried several times but i can't get this to work. The reason is simply that all file managers i have tried so far, Rootexplorer and ES Explorer, fail when trying to overwrite the existing system/usr/keylayout/ folder, although both have perfect root access (i have SU Superuser for this).
What can i do to get this working ? Are there different levels of root access ?
you have to get write access to the system folder by remounting it
su mount -o remount,rw /system
for es explorer open the left sided menu.
Werkzeuge
click on Root Explorer
R/W einbinden
choose r/w twice.
now you should be able to overwrite files
Sent from my XT897 using XDA Premium 4 mobile app
comstyle said:
for es explorer open the left sided menu.
Werkzeuge
click on Root Explorer
R/W einbinden
choose r/w twice.
now you should be able to overwrite files
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much, that did the trick ! I have been to the 'tools' section (=Werkzeuge) of ES Explorer before already, but didn't realize that there are additional functions when clicking on the switches. Allowing R/W for system and root did it, i have QWERTZ finally !
EDIT : I don't know what happened, but for a while the second phone i did the update with did not react to the keyboard any longer at all, and also the power button could not be used to interrupt the screensaver. I tried various actions, also changing the permissions for the new 'keylayout' folder (i renamed the old one to 'keylayout_backup') from the GZ archive file to 'rwx' for all groups, not only 'root', and all of a sudden - after some reboots - everything was fine again. Keyboard worked again, and phone will react to power button. Don't know exactly what i did to get this working, but thank god it does ....
EDIT #2 : This is strange, although i do have QWERTZ working now on all three XT897 phones, on one of them the power button is not working anymore since i changed the keylayout folder. The button itself is working, i can power on the phone fine if it shut down, but as soon as ANDROID has started it won't allow me to lock and unlock the screen with the power button, i have to use the keyboard for that. The phone can be used this way, but this is quite annoying as it makes one handed use almost impossible ? BTW, the other two phones are on 4.1.2, this one is still 4.0.4, will that explain the difference ?
Is there any possible explanation to this behaviour ? Maybe a wrong/outdated file in the new /system/usr/keylayout folder ?
it's possible the key isn't defined inside the file. never had this problem with my files but I used them with jb stock and cm10.2.
you probably should check your files again and/or just update to cm10.2.
Sent from my XT897 using XDA Premium 4 mobile app
comstyle said:
it's possible the key isn't defined inside the file. never had this problem with my files but I used them with jb stock and cm10.2.
you probably should check your files again and/or just update to cm10.2.
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
But i was using exactly the same files in all three phones, the original files from Gehstock from his original link, and they worked for the two phones with 4.1.2, only on mine with 4.0.4 they don't work for the power button ? I had this strange effect that in one of the two 4.1.2 phones the keyboard would not work at all, including power button, immediately after overwriting the old files, but after fiddling around with read/write permissions it worked all of a sudden, and including power button.
Now i have QWERTZ on all three phones, but on mine with 4.0.4 the power button will only work if i want to switch on the phone, as soon as ANDROID is running the power button doesn't react anymore, meaning i have to use TWRP to shut it down again and can't switch to flight mode at all. Any idea what could be causing the problems ? Which of the files in the keylayout folder will describe the power button, maybe i should make a reload of this file ?
EDIT :
Here a list of the files in my original /system/usr/keylayouts folder on Android 4.0.4 :
AVRCP.kl
cyttsp-i2c.kl
Generic.kl
keypad_8960.kl
msm8960-snd-card_Button_Jack.kl
qwerty.kl
usb_keyboard_102_en_us.kl
Vendor_05ac_Product_0239.kl
Vendor_22b8_Product_093d.kl
Vendor_22b8_Product_0938.kl
Vendor_045e_Product_028e.kl
Vendor_046d_Product_c216.kl
Vendor_046d_Product_c294.kl
Vendor_046d_Product_c299.kl
Vendor_046d_Product_c532.kl
Vendor_054c_Product_0268.kl
In the new layout folder from Gehstock there are a number of additional files, especially
atmel_mxt_ts.kl
Button_Jack.kl
gpio-keys.kl
philips_remote_ir.kl
samsung_remote_ir.kl
ue_rf4ce_remote.kl
while some others are missing, like msm8960-snd-card_Button_Jack.kl and usb_keyboard_102_en_us.kl .
Is the problem with my power button maybe resulting from any of the missing files, or the additional files which can't be read in 4.0.4 ?
EDIT 2 : I solved the problem. Deleted the folder from Gehstock, brought my original folder back and only replaced the file 'keypad_8960.kl' with the one from Gehstock. Now i have QWERTZ and my power button is working again.
Can anybody explain to me why we are told to replace the complete folder, if all we need for QWERTZ is the one file ? I only found this out when reading this thread here (German ) :
http://www.android-hilfe.de/motorol...difizierte-belegung-des-hardwarekeyboard.html
When reading this thread it became clear to me that all we need to replace is 'keypad_8960.kl' to get QWERTZ.
So, has anyone an idea how we can get double or longpress on a,o and u to get ä, ö and ü ? At the moment, ihave to close the phone too type the letters with the software keyboard. Plus, i have a major problem, when i type ****+, it doesnt type a semicolon but a <, same with shift+. No double point or however the two dot thing is called, but a >
Any idea how to fix those issues?
I suppose you are not using cm11? (umlaut = sym + vowel) just select the right layout. (the second "Asanti QWERTY" is qwertz)
when using cm10 or stock rom (rooted) you could insert a modded layout file for double pressing
comstyle said:
I suppose you are not using cm11? (umlaut = sym + vowel) just select the right layout. (the second "Asanti QWERTY" is qwertz)
when using cm10 or stock rom (rooted) you could insert a modded layout file for double pressing
Click to expand...
Click to collapse
i cant get cm11 to run on my photon q... dunno why, but no rom boots, so i have to stick with aokp , since its the only rom working.
so.... you could just add a modded layout file into the right folder to get double pressing!?!
did you try that?
comstyle said:
so.... you could just add a modded layout file into the right folder to get double pressing!?!
did you try that?
Click to expand...
Click to collapse
no, which files exactly are the ones qwertz (not qwerty, i replaced y/z) with äöü?
[off topic] btw, is there anything special i have to keep in mind for installing custom roms on my photon q (with gsm sim mod)? i have twrp and aokp running, but only aokp and colorOS are installing, everything else fails while installing.
Related
Hi guys,
Have you used two finger rotation in google maps on SGS SL earlier? Its a simple but quite handy feature for them who use Google maps as regular navigation system. It is possible by just transferring the attached file into the System/etc/permissions folder. Just download the attached zip file and extract it. You will find android.hardware.touchscreen.multitouch.distinct.xml file, put it on sdcard, copy it using root explorer to System/etc/permissions folder. reboot the device. Now go to google map and see if you can rotate the map using two fingers. This feature works only on Google maps above version 5, so please update to latest Google maps. if you have older version this feature will not work.
Not to mention you need root permission and the system should be mounted as RW as you are pasting file in subdirectory of system.
Just press thanks button If you like my Post.
Hry trip my phone has maps 4.5 preinstalled and i cant seem to update it.maps dont show up on my market either.is it ok if i download 5.0from an external source and then use it?
Sent from my GT-I9003 using XDA App
Yes you can. But before installing the downloaded version you will have to clear the data for google map. Then push the apk file to system/app or replace it using root explorer.
Sent from my GT-I9003 using XDA Premium App
Cant i just clear the data and install the new apk????
Sent from my GT-I9003 using XDA App
rdr_m said:
cant i just clear the data and install the new apk????
Sent from my gt-i9003 using xda app
Click to expand...
Click to collapse
may work, just try it and let us know.
trip007in said:
Hi guys,
Have you used two finger rotation in google maps on SGS SL earlier? Its a simple but quite handy feature for them who use Google maps as regular navigation system. It is possible by just transferring the attached file into the System/etc/permissions folder. Just download the attached zip file and extract it. You will find android.hardware.touchscreen.multitouch.distinct.xml file, put it on sdcard, copy it using root explorer to System/etc/permissions folder. reboot the device. Now go to google map and see if you can rotate the map using two fingers. This feature works only on Google maps above version 5, so please update to latest Google maps. if you have older version this feature will not work.
Not to mention you need root permission and the system should be mounted as RW as you are pasting file in subdirectory of system.
Just press thanks button If you like my Post.
Click to expand...
Click to collapse
hi trip007in!
It looks great! Thanks for all the great work you guys are doing!!
One question, does this change the finger gesture used for rotation (like in i9000), or just enables it?
I mean because my i9003 already has rotation enabled by default in maps, but the gesture is different, for some reason it is two horizontal fingers which I find less intuitive.
@hyperion: It enables a gesture to rotate the map around another axis. You probably mean rotation around an axis, which is "lying in the ground" horizontally - this still works afterwards. But now you can also rotate around an axis, which "poked into the ground" vertically (meaning that the top of your phone is not north anoymore).
EDIT: For the case that the above statement doesn't make it clear: I installed the fix on my phone, and it works perfectly. Nice feature.
hyperion86 said:
hi trip007in!
It looks great! Thanks for all the great work you guys are doing!!
One question, does this change the finger gesture used for rotation (like in i9000), or just enables it?
I mean because my i9003 already has rotation enabled by default in maps, but the gesture is different, for some reason it is two horizontal fingers which I find less intuitive.
Click to expand...
Click to collapse
It does not affect the other functionalities/ gestures. Just adds two finger rotation in googleMaps. This gesture helps the user to correct the direction of the map and the arrow to align towards in the desired direction for eg: It helps to align the map and the point of the arrow (your position) in the direction you are moving. Just try it. If you do not want you can always remove this .xml file without affecting anything.
Thanks, I'll definitely try it
Just works..
Thanks trip! I pressed the thanks button too btw..
I think this would be a very useful feature. Recently I used the maps on a trip and I had to rotate the phone to make it point in the direction I was moving which was inconvenient.
I have ES File explorer but this is not allowing me to copy the file from external SD card to System/etc/permissions. I also noticed that there is already a file there with same name and I tried to rename it but that was also denied. Any advices?
Mount file system as rw on top by toggle button on root explorer.
Sent from my GT-I9003 using XDA Premium App
trip007in said:
Mount file system as rw on top by toggle button on root explorer.
Click to expand...
Click to collapse
I have not purchased root explorer. Any free alternative?
jesrani said:
I have not purchased root explorer. Any free alternative?
Click to expand...
Click to collapse
Use Super Manager.
Sent from my GT-I9003 using XDA Premium App
spacebar2011 said:
Use Super Manager.
Click to expand...
Click to collapse
Thanks, it worked. This is a really useful feature.
Ya, I was using it earlier on my spica so was missing it. So posted it for benefit of everybody.
Sent from my GT-I9003 using XDA Premium App
thanks, it worked like a charm.
Not working on my device having map 5 and follow as told carrot xml file to system/etc folder
I badly want this. This is very cool.
Sent from my GT-I9003 using Tapatalk
@ manrock111: You have to copy it to system/etc/permissions (not system/etc) and reboot for it to work.
XDA_Bam said:
@ manrock111: You have to copy it to system/etc/permissions (not system/etc) and reboot for it to work.
Click to expand...
Click to collapse
thanks bro now working flawlessly.
Sent from my GT-I9003 using Tapatalk
hello all,
first of all THANK YOU very much for this ROM - really appreciate it!!!
second of all:
I currently have a stock rom on my device - rooted.
As I understand I need to replace the stock recovery with that of krylon360(http://forum.xda-developers.com/show....php?t=1099374) and then follow the steps listed in the first post??
is the link in my post is the link to the final version of cwm for our devices??
Thank you very much for the help and sorry for the noobenst this is my first rom change
alon2 said:
hello all,
first of all THANK YOU very much for this ROM - really appreciate it!!!
second of all:
I currently have a stock rom on my device - rooted.
As I understand I need to replace the stock recovery with that of krylon360(http://forum.xda-developers.com/show....php?t=1099374) and then follow the steps listed in the first post??
is the link in my post is the link to the final version of cwm for our devices??
Thank you very much for the help and sorry for the noobenst this is my first rom change
Click to expand...
Click to collapse
your link wont load, just make sure you go to the thread that says CWM FINAL by krylon 360 and follow the steps and you will be fine
dsexton702 said:
your link wont load, just make sure you go to the thread that says CWM FINAL by krylon 360 and follow the steps and you will be fine
Click to expand...
Click to collapse
this is the link(as I see it in my broser)
what are the steps after I replaced the recovery?
is it as simple as following the steps in this thread?cause I saw people had problems...
Thank you very much for the help again
Just go to cyclopscomputers.com/gs4g
Sent from my SGH-T959V using XDA App
Use root explorer to copy/replace recovery.bin put update.zip on root of sd card, reboot into recovery.
Sent from my SGH-T959V using XDA Premium App
This is what I did and worked perfectly. But I allready had KD1 which I recomend you get. Download the recovery and update.zip and put both of them on the root of your sd card. Then get root explorer from the market. Open root explorer and go down to sdcard. In the sd card you are gonna find the recovery file you placed in there. Your long press it and its gomma say copy. Copy that and press back button and then your at the main page of root explorer again. Its gonna say paste and cancle at.the bottom but dont press anything yet. You go all the way down to system and go into it and then into /bin. In /bin your gonna press the mount r~w button at the top right which allows you to paste the file. You press paste at bottom left and its gonna ask if you want to overwrite say yes.(if it didnt ask you overwrite that either means the file you downloaded was renamed.or there was a (2) or (3) on it if you downloaded various times. Just take the ending out so its.just.recovery)
Now back out to homescreen of your phone.and if you have kd1 you can get into recovery from quickboot if not then turn off your phone and hold powerbutton and both volume keys while the phones turning on normally it will go to a bluish screen with an android.(recovery) here you click reinstall packages and your done
Sent from my SGH-T959V using XDA Premium App
sorry i have to do this... but i'm pretty sure theres more than enuff info to figure it out... noob or noobiest... didnt have to start a random thread
Moved to general.
rickyy00 said:
This is what I did and worked perfectly. But I allready had KD1 which I recomend you get. Download the recovery and update.zip and put both of them on the root of your sd card. Then get root explorer from the market. Open root explorer and go down to sdcard. In the sd card you are gonna find the recovery file you placed in there. Your long press it and its gomma say copy. Copy that and press back button and then your at the main page of root explorer again. Its gonna say paste and cancle at.the bottom but dont press anything yet. You go all the way down to system and go into it and then into /bin. In /bin your gonna press the mount r~w button at the top right which allows you to paste the file. You press paste at bottom left and its gonna ask if you want to overwrite say yes.(if it didnt ask you overwrite that either means the file you downloaded was renamed.or there was a (2) or (3) on it if you downloaded various times. Just take the ending out so its.just.recovery)
Now back out to homescreen of your phone.and if you have kd1 you can get into recovery from quickboot if not then turn off your phone and hold powerbutton and both volume keys while the phones turning on normally it will go to a bluish screen with an android.(recovery) here you click reinstall packages and your done
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thank you very much for the detailed explanation.
I'll try that tomorrow at work cause at home I can't get windows 7 to recognize my device
To be honest u don't need a pc and can do the whole thing from your phone with the right apps and it works flawlessly haveing roottookit and supermanger also helpful in the process
Sent from my SGH-T959V
rose2jam said:
To be honest u don't need a pc and can do the whole thing from your phone with the right apps and it works flawlessly haveing roottookit and supermanger also helpful in the process
Sent from my SGH-T959V
Click to expand...
Click to collapse
how can I do it without a PC?
downloading now supermanger , didnt find roottookit
not working...
So I did as you said(didn't use my PC by downloading stright to the phone and using root explorer)
boot into recovery using quick boot app(exclamation mark screen with little green robot)
pressed the reinstall packages
it says:
-- Applying Multi CSC
-- Installing Multi CSC
-- Install from sdcard..(in yellow)
Finding update package(in yellow)
E:Can't mount /dev/block/mmcblk0p1(in red)
(No such file or directory)(in red)
E:Can't mount SDCARD:update.zip(in red)
Installation aborted(in red)
did I do something wrong?
alon2 said:
So I did as you said(didn't use my PC by downloading stright to the phone and using root explorer)
boot into recovery using quick boot app(exclamation mark screen with little green robot)
pressed the reinstall packages
it says:
-- Install from sdcard..(in yellow)
Finding update package(in yellow)
E:Can't mount /dev/block/mmcblk0p1(in red)
(No such file or directory)(in red)
E:Can't mount SDCARD:update.zip(in red)
Installation aborted(in red)
did I do something wrong?
Click to expand...
Click to collapse
Did you move the the update.zip to the correct directory?
yep moved it to /sdcard
Sent from my SGH-T959V using XDA App
Did u add the recovery file from downloaded to system .bin folder
Sent from my SGH-T959V
rose2jam said:
Did u add the recovery file from downloaded to system .bin folder
Sent from my SGH-T959V
Click to expand...
Click to collapse
yes I did just like the tutorial said to(overwrite the original)
/dev/block/mmcblk0p1 - really doesn't exist
E:Can't mount /dev/block/mmcblk0p1(in red)
(No such file or directory)(in red)
Click to expand...
Click to collapse
I really don't have that directory - should I have it?
issue solved by formatting the SDcard
so I formatted mt sdcard and the managed to get into CWM.
I hava another question:
now every time I want to go into CWM I should do the same procedure?
I mean put the update.zip in the root of the sdcard->go to recovery->reinstall apps?
Alon
That's what I do leaving the update there... btw its root toolbox helps geting into recovery without the three button push also with getting rid of bloat
Sent from my SGH-T959V
going to flash...few more questions
rose2jam said:
That's what I do leaving the update there... btw its root toolbox helps geting into recovery without the three button push also with getting rid of bloat
Sent from my SGH-T959V
Click to expand...
Click to collapse
Now that I have cwm I want to replace the kernel.
I want to take Bali v2.1 extended battery from whisky -
my questions are:
1) which kernel should I take:regular\UV(what's the difference anyway)
2) what about all my apps+data/contacts/sms...? will it erase them?what backup should I do?
Hi all - Is there a way to flip the volume keys? I use my tab 7.7 in landscape 100% of the time and would rather the key nearest the power button be Volume Down and the other key be Volume Up.
I've tried both the normal version of ButtonRemapper & the Galaxy Tab version of ButtonRemapper but neither seem to work for me.
Any suggestions?
*****EDIT******
I figured out that all i needed to do was to manually edit the keylayout files in /system/usr/keylayout
I wasn't sure which file to edit so i just edited any of them that referenced Volume.
I used ES Explorer in root mode to modify the files, rebooted and now the keys are flipped
*****EDIT*****
Solved!
I googled and figured out the solution - i have modified the first post with the info.
Confirm only need to modify the Generic.kl file.
Sent from my GT-P6800 using xda app-developers app
ZhenMing said:
Confirm only need to modify the Generic.kl file.
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
Ah thanks for the info that'll make life easier for anyone else wanting to do the same
Hi,
I'm pretty sure this problem could be common to all rooted devices, so I'm posting it in the general Q&A.
Basically, I would like to experiment with some build.prop tweaks I found around other XDA topics. I'm sure all of you know about the general tweaking of the said file, so I won't get into too much detail about it.
However, the changes just don't stick. They reset to default every time I reboot, as if the build.prop file never changed. So, how do I make them stick?
Phone details:
Phone: Xperia X8
ROM: FroyoPro v2.5
Kernel: Stock (can't unlock the bootloader, unfortunately)
Are you saving before exiting?
XperienceD said:
Are you saving before exiting?
Click to expand...
Click to collapse
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
xWhiskey said:
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
Click to expand...
Click to collapse
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
sircrisp said:
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
Click to expand...
Click to collapse
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
xWhiskey said:
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
Click to expand...
Click to collapse
I'm here to wake this thread up, because I'm having this same issue and I can't seem to find any duplicate build.prop file...
Anyone having a good suggestion for me please give it, all assistance is welcome.
Android version 4.4.4
Galaxy Note Edge
Sent from my SM-N915P using Tapatalk 2
me too have the same problem , please some dev or expert help with these problem
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Are you setting the file permissions correctly as rw-r--r-- ??
[/COLOR]
flexton said:
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
samsungrockz said:
Are you setting the file permissions correctly as rw-r--r-- ??
Click to expand...
Click to collapse
thank u for answering but sorry guys to say this , it's not the way of editing it , or the permission , when i make changes they are saved correctly and the device apply the changes in the start of the first boot after these changes are made , but during the boot (after applying the changes) the device restore the stock build.prop , so when the device finishes boot up the changes are applyed but the build.prop (i cheked it) is back to stock , this mean another boot & the changes are gone , :crying: :crying: no matter how many times or changes u do they are applyed only for the first boot after they are made
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Kico.MMK said:
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Click to expand...
Click to collapse
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the advice , actually i did that but you know there is always something to be fixed :silly:
I have the same issue with my Vodafone Smart Ultra 6. I have root and system has read write access according to ES File Explorer. But any app that has root privileges, writes just fine without errors. However, if I close the app and load it again, or reboot, any changes are lost. So if I remove a system app using a root uninstaller it will say the app has been uninstalled. But it's still there. Drives me insane.
Exactly the same on the Smart Ultra 6.
Was hard enough to get it rooted but seems any changes to the system partition/file system just don't stick. Short of putting a custom rom on it I'm stuck for ideas.
I'd love to know what causes this behaviour.
Any updates here? I just started running into this after updating to the 7.1.1 January factory image on my 5x. The weird thing is when i reboot in TWRP it all looks fine but when I look at my system directory from Android the boot-from-recovery.p is still there and my build.prop changes aren't...push TWRP again, boot to recovery read build.prop and it's my edited version. wtf?
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
I have the same problem: after reboot all the changes are gone....
ashd63 said:
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
Click to expand...
Click to collapse
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
ullie4404 said:
I have the same problem: after reboot all the changes are gone....
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
Click to expand...
Click to collapse
Did you ever find the solution to this? I'm having the same problem..all changes reset with every reboot and the file's permission is like -rw-----
I want to make Swype my default keyboard. I have have CyanogenMod's flasable zip and Swype's working apk. I want to replace default keyboard in the zip with Swype. is it possible to do it?
please help
Long pressing on any text field will open a menu..click input method, select keyboard of your choice
gaurav.mishra280295 said:
I want to make Swype my default keyboard. I have have CyanogenMod's flasable zip and Swype's working apk. I want to replace default keyboard in the zip with Swype. is it possible to do it?
please help
Click to expand...
Click to collapse
Ur question isn't clear dude.. if u just want 2 use it as ur default keyboard,do as my friend said.but if u want to delete default keyboard, delete d keyboard apk from system/app using root explorer
Press thnx button if it was helpful(plz)
Sent from my GT-S5670 using XDA
"if u just want 2 use it as ur default keyboard,do as my friend said"
Long pressing to change the keyboard does not make the keyboard the default. Upon reboot, your stock keyboard is used or none if you have removed it. I have to change to Swype upon every boot. Very annoying. There must be a way around this. Does anyone know?
thejayjetson said:
"if u just want 2 use it as ur default keyboard,do as my friend said"
Long pressing to change the keyboard does not make the keyboard the default. Upon reboot, your stock keyboard is used or none if you have removed it. I have to change to Swype upon every boot. Very annoying. There must be a way around this. Does anyone know?
Click to expand...
Click to collapse
I'd love to hear the answer to this as well. Prior to last release of Android, Swype said that it was an Android problem and the next release would fix it. They stated on the user comments section that "we can't help sloppy Android code and it's not our fault". The problem was neither - it still comes up with the standard keyboard as default upon reboot every time
gaurav.mishra280295 said:
I want to make Swype my default keyboard. I have have CyanogenMod's flasable zip and Swype's working apk. I want to replace default keyboard in the zip with Swype. is it possible to do it?
please help
Click to expand...
Click to collapse
Try SwiftKey.
The issue happens with all paid keyboard.
Someone says it's an os fault..someone a Play store fault..someone a bad app coding fault.
The fact is that no one had made a fix.
It's there a way to fix this without touching the alt keyboard (I mean without moving it or installing it manually so to avoid any strange future updates failure) that can prevent the default stock keyboard to stick back as default at each reboot??
I mean..if I back up the stock android keyboard and then uninstall it with Titanium Backup..could it fix?
Sent from my Samsung Galaxy S3 GT-i9300 using TapaTalk2
PIRATA! said:
The issue happens with all paid keyboard.
Someone says it's an os fault..someone a Play store fault..someone a bad app coding fault.
The fact is that no one had made a fix.
It's there a way to fix this without touching the alt keyboard (I mean without moving it or installing it manually so to avoid any strange future updates failure) that can prevent the default stock keyboard to stick back as default at each reboot??
I mean..if I back up the stock android keyboard and then uninstall it with Titanium Backup..could it fix?
Sent from my Samsung Galaxy S3 GT-i9300 using TapaTalk2
Click to expand...
Click to collapse
This issue happens with (almost) all paid keyboards, as the only available keyboards at boot are the stock and free ones, given paid apps are stored in a protected storage area that is unavailable at boot time, at least until the Google Play service is actually started.
That's why (for instance) SwiftKey Free or Smart Keyboard Free are indeed kept as default keyboards after a reboot, but their corresponding paid apps will not and hence the 1st available free/stock keyboard will be selected.
The solution (developers?) could be the paid keyboard being the same free app, working with a "license" paid app. This way, the keyboard would be available at boot time and could be enabled as default, while keeping paid/premium features.
I'm afraid this is an OS restriction (bug maybe?) not yet addressed but with a helper app. The best ones so far imho (just workarounds anyway, as they still require user intervention):
Keyboard Picker
Keyboard Swap
I managed to get it working on 2.3.7 & 2.3.8 successfully but the gesture feature doesn't work(coz it asks for license):sly:. Does anyone know where the Swype licence gets stored(somewhere in /system partition)??
swype somehow checks your build.prop file and based on that check, Swype will work or not.
steps you have to do first:
http://forum.xda-developers.com/showthread.php?t=959192
First you will need to extract the needed files from a stock ROM. If you are still running the stock software, you can use a file explorer app to make a copy onto your SD card. Just copy and paste. You can also pull the files from the stock image or from the Iced glacier ROM. Pulling from Iced Glacier is the easiest method. Just unzip the ROM file and find the needed files.
There are two files, both in the system partition. The first is "Swype.apk" and is in /system/app folder. The second is "libSwypeCore.so" and is in /system/lib/ folder.
Edit: 7/25/11
It seems you must also conciser the source ROM and destination ROM when obtaining the files. Swype does a device/licence check when running, and if it fails the check then Swype will not work. The build.prop lists "t-mobile/htc/ect" as product.brand and Swype seems to check this before running. So use a version of Swype from a ROM with the same build.prop or edit the build.prop manually.
Now to install Swype:
There are two ways to do this, ADB or root explorer. (or other file manager with RW)
Any extra info to help explain what is going on for any new guys will be in green text.
For ADB:
First put the files you extracted into the tools folder of the android SDK, then open an ADB shell to your phone. When that is done, use the following commands. (each line is a separate command)
Remember Linux commands are case sensitive.
First is to mount /system as RW. (this allows you to save files to /system)
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Then you need to push (save a copy) the files to the correct locations.
Code:
adb push Swype.apk /system/app/Swype.apk
adb push libSwypeCore.so /system/lib/libSwypeCore.so
It may give the files the wrong permissions. (how much access to the system they have) Just to be safe we need to give the files the right permissions.
Code:
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.so
sync
reboot
Your phone will reboot and then you are done.
For Root Explorer:
Extract a copy of the needed files and put them on the SD card.
Then open root explorer and open the "sdcard" folder.
Next find "Swype.apk" and long press it and select "copy" (or if you have already completed this step once, copy "libSwypeCore.so")
Use the back button to go back to the root of the folder tree (up top where it shows your current location, it will show "/" this is where you started from when opening the app)
Locate and open the "system" folder.
You then need to tap the button up top marked "Mount R/W" (this will allow you to make changes and copy the files to the right locations) (this step should not be needed if you have already done so before)
Next open the "app" folder. (or if you are moving "libSwypeCore.so" open the "lib" folder)
Hit the "paste" button to copy the file.
Next long press the file you just copied "Swype.apk" and select "permissions" (or "libSwypeCore.so" as appropriate)
You will see a bunch of check boxes. The will be labeled "read" "write" "execute" across the top and "user" "group" "others" down the left side.
For "user" select the "read" and "write" boxes
For "group" and "others" select the "read" box only. Then select "OK"
When done with the first file, repeat the above steps again with the second file. Observe any changes to the steps that are in orange text.
Next open up a "terminal emulator" app and then run the following commands.
Code:
su
sync
reboot
Your phone will reboot and then you are done.
Hope this helps someone.
Click to expand...
Click to collapse
however, this has not helped my with my Galaxy Ace with custom rom. I guess the build.prop files do not match.
You can try with your Fit however. You need to have the swype.apk and the libswypecore.so files from your Original rom.