hi there
s.memo keeps Crashing I am on a stock Rom
2.6.35.7-N7000XXKJ4-CL641703
[email protected] #2
I bought it from amazon.de, i am in UK
basically if i try to launch s memo directly via shortcut on home screen (finger or stylus) i get
A blank screen for a few seconds or so then i
Get a force close dialog saying s memo has stopped
Working (process com.sec.android.widgetapp.diotek.smemo) has stopped unexpectedly....
I can create an s memo widget on the home screen
And if i tap on this it launches what i assume is s memo and i can draw etc and save etc, this then turns the widget into mini version of whatever i drew/wrote but if i tap on the saved widget i get the force close dialog, i am able to click the widget "+" icon on the newly saved widget and i can work on a new s memo doc, but after saving.... Force close etc.
I have completely wiped phone factory reset etc and nothing installed no joy. Any help would be much appreciated. Could not find any info googling relevant terms.
Thanks
s memo crashing
Try this to solve the problem:
1. Find /data/system/packages.xml with Root Explorer.
2. Make a backup of packages.xml right away in the same folder in case we mess anything up any need to restore it later
3. Copy packages.xml onto the root of your internal or external storage
4. Plug your device into your computer and copy packages.xml from the root of your storage over to your computer
5. Open the packages.xml on your computer with your editor of choice - I use Wordpad
6. Search for the string. The lines should look something like this:
<package name="com.sec.android.widgetapp.diotek.smemo" codePath="/system/app/SMemo.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.diotek.smemo/lib" flags="1" ft="135586718b0" it="133696737a0" ut="135586718b0" version="1" userId="10044">
7. then, you need to put/add this: enabled="1" at the last line before the ">" sign. The lines should look something like this:
<package name="com.sec.android.widgetapp.diotek.smemo" codePath="/system/app/SMemo.apk" nativeLibraryPath="/data/data/com.sec.android.widgetapp.diotek.smemo/lib" flags="1" ft="135586718b0" it="133696737a0" ut="135586718b0" version="1" userId="10044" enabled="1">
Do this work?I have not rooted my phone but will do it just to solve this problem!
no that doesnt work
man I hope someone find a fix for this!!
I updated my firmware to the latest open Europe one and the problem stop! So the best to solve this problem is to.flash a new firmware!
Pure vida guys!
Sent from my GT-N7000 using xda premium
Hey guys,
There have been a ton of people asking how to activate onscreen buttons and disable the capacitive buttons since CM12 builds have started rolling out. Obviously, at some point, these features will be rolled into the ROM, but until then, I figured it would be a good idea to simply present a step-by-step thread on the issue. There have been answers all over the place button nothing dedicated and centralized, so I figured I would help some guys out.
Things needed:
CM12 Build on any variety (currently K900 and bpear have "nightlies" available in development. Check em out.
Root access. Just flash SuperSU 2.16 (http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip) if you don't have it. Root is necessary.
Zip to turn of the backlights: http://www.mediafire.com/download/p385se5ia28cqab/noSoftkeyBacklight.zip (thanks @Moody for this)
1.) Activate On-Screen buttons
- Use a program such as BuildProp Editor (look it up on the Play Store) to create a new build.prop entry. Call it qemu.hw.mainkeys, and set it's value to 0. If you are doing this manually, just add the line "qemu.hw.mainkeys=0"
- Reboot.
2.) Deactivate Capacitive buttons
- Download Root Explorer or some other program that allows editing of system level files.
- Mount your system as R/W. In root explorer at least, when you get into the system, there is a button up top to do so.
- Navigate to /system/usr/keylayout. Open Generic.kl in with a text editor.
- Comment out the follow lines by inserting a pound sign (#) in front of the line:
key 158 BACK
key 172 HOME
key 139 MENU
After this, they will read:
# key 158 BACK
# key 172 HOME
# key 139 MENU
Therse are numerically ordered, shouldn't be hard to find within the document.
- Remount your system as R/O.
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Anyone know how to enable hardware home long press to get to Google now?
TjPhysicist said:
Anyone know how to enable hardware home long press to get to Google now?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures&hl=en
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Hi there, first of all, thanks. I am having a problem where after I disabled the capacitive buttons (Step 2) the power and volume buttons are not working. Thanks in advance.
You know how to enable menu key also?
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Yes any chance of getting home button long press as search? Default is the menu button doing this.
Its not working bro
Tried and followed your steps , disabling capacitive keys works but enabling on screen keys not working even after changing build.prop , also i read in some post that enabling on screen key mod will not work in cm roms is that true can any one confirm me?
i am using following rom its CM12
http://forum.xda-developers.com/oneplus-one/development/devrom-cm12-scheduled-builds-t2938372
its very stable didnt experience any glitch till now , multi user and guest account works , all the other features are working too, try it out friends.
Pure awesomeness, many thanks for this guide. I'm back to my comfort zone, onscreen for me is just more intuitive.?
BTW, how to bring back the capacitive lights? I tried to remove the script at /etc/init.d and it only bootloops after reboot.
Edit: Nvm, found it, re-flashing the ROM brings back all to the default behavior including the capacitive backlights.
kmakiki said:
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Click to expand...
Click to collapse
For some reason this step isn't working for me. I tried wiping cache/dalvik and it didn't fix anything
Can anyone give a screenshot of the on-screen buttons?
Is this possible to do in hydrogen OS? I love that rom, but i switch back since there is no option to turn off hardwer keys and enable software key in system?
Sent from my A0001 using Tapatalk
How to add volume button onscreen by editing buid.prop
hey Everyone,
I tried to enable the on screen softkeys by editing the build.prop file to add the following line:
qemu.hw.mainkeys=0
This was suggested in many forums and found to be working, but not on the galaxy s4 i guess. When i reboot my phone after adding this line, the systemUI crashes and the phone is totally unusable.
Have anyone tried to do this, or have you ditched the HW keys and enabled the integrated on-screen softkeys on GS4?
Please let me know how...
Thanks!
Hello K3 Note users!
So, about 5 months ago I discovered that my back and menu keys were not working. I tried rebooting the device, pulling the battery out, changing the ROM and I even opened the phone up, to see, if every wire was connected properly....but the problem wasn't to be found. I also tried to get some support from the Lenovo's website, but I ended up getting none.
Eventually I found a workaround, that does not fix the problem itself, but it makes the phone usable again.
The solution is easy and it has already been written before:
1) Flash a custom ROM.
2) Make sure that you have ROOT.
3) Download a file manager, that can make use of the root rights.
4) Go to /system/build.prop
5) Add the line: "qemu.hw.mainkeys=0" to the very end of the file.
6) Reboot and voila!
However, I found that some apps refused to work with the nav bar and some vital content of those apps got hidden by the buttons.
I managed to found a fix for this problem. It can be solved with a wonderful Xposed module titled "Hideable Nav Bar".
The plugin will create a little down arrow on the left of the nav bar. This will let you to hide the bar whenever you want/need to. When the bar is hidden, then bringing it back is as easy as swiping up a bit from the bottom of the screen.
(I won't give you the steps on how to install Xposed, because it has already been described in the general thread.)
Anyway if you have installed Xposed, then you want to go to "Download" and search for this module. After that you should install the module, activate it and then reboot your phone. :good:
I hope this post was helpful to some K3 Note users and if it did help you, then don't forget to press the "Thanks" button too!
Redmi Note 2, Android 5.0.2, MIUI 9.6
Need to enable original soft keys. I`ve managed to edit build.prop (qemu.hw.mainkeys=0) from TWRP terminal and sed command. Keys showed BUT don`t response.
I`ve noticed a new menu option in Settings (can`t be not quite accurate, coz I have a translation enabled) - System and Device -> Advanced -> Buttons and gestures -> Screen buttons -> Change buttons positions. And if I change positions, it changed. But buttons are stil not responding.
Are there any MORE options in build.prop, that blocks it?
UPD:
[How To] Disable Capacitative Keys and Enable Soft Keys
Just in case anyone might find this useful, I've put together the instructions I found whilst trying to do this. Finally I can take photos without accidentally bringing up the Menu or closing the Camera App! First time I've ever posted here, so be kind! This works in CM11 M6 on Samsung Galaxy...
forums.androidcentral.com
I`ve found some article, that point to /system/usr/keylayout/ directory and need to comment key 139 and key 158. But there were no such filename from article. So I`ve just tried to edit Generic.kl and It doesn`t work.