Related
Is there any way to change the grey background colour in the orange m600 phone dialer. Maybe to a lighter colour in the sunlight it is nearly impossible to read the info on it
I don't have your device, but let me guess.
Your phone should be on WM5 and it seems that your phone is in skin mode.
There are.. 3 ways to solve it
(1) Try the default dialer
(2) Use a customized dialer
(3) Edit the skin
- Details -
(1) Disable the Orange skin, by editing the registry, go to
HKEY_LOCAL_MACHINE\Security\Phone\Skin
modify the Enable from "1" to "0"
(2) Go to this thread
http://forum.xda-developers.com/viewtopic.php?t=35326&highlight=
Grab one of the colour that you like and install (can be uninstalled if you don't like it)
(3) There is a file in your windows directory that is used for the skin background (open one by one on your PPC, or better, copy everything from your PPC to your PC), copy that into your PC, modify it, and paste it back.
NOTE: All of the methods stated above require restarting the device.
Just done option 2. Excellent, I can now dial using my fat fingers! 8)
Hi,
I have just tried the default skin rather than the orange one but now i can't get the orange (grey) one back could someone tell me how to get it back. i have tried setting the registry entry to 1 but it resets to 0 on reset.
thanks
Got it back, took about 4 resets - strange!
WM5 has a weird habit of not doing things on the spot. E.g., when you reset the unit just after you change the registry, the new modifications won't be shown. I read somewhere that WM5 has a delayed thing in writing onto registry. So, you should like wait for a while before you resetting your unit.
My screen goes crazy. During a call up to my ear it flips to horizontal, changes out of key pad view and not always to mute/speakerphone... keys view, sometimes to contact info, and can be a nightmare to get back to "end call." I've found times when the caller hung up but the TP2 put them on hold and kept my time going.
Any programs and or reg hacks to:
1) stop the horizontal flip when placed to an ear, and
2) keep it in keypad mode or general call mode?
Real pain when dialing into a system that requires keypad responses. Everytime I put it back to my ear I have to go through a crazy sequence to get back to the key pad.
This is my only complaint wth this phone, it's not easy to use as a phone!
Thanks.
I have the same problem when dialing into VM, or into any call queue. I looked through the registry a bit. Didn't see anything obviously labeled.
yeah me too. Only thing I could find was using Gyrators' exception list to not rotate the phone, but it wasnt 100% reliable. I would *LOVE* to find a way to stay in keypad mode too.
Hi All - I guess I'm just jumping on the bandwagon but I have the same issue and find it annoying. I loaded the 'incall screen tweak' but that didn't work. Any help more seasoned members than I could offer would be greatly appreciated.
Cheers!!!
I had the same issue too, whenever I put my phone up to my ear (left handed) it would go into landscape. The fix is simple but you have to edit a registry setting. I'm going by memory here, so please forgive the vague info
1) make sure to backup your reg info
2) using your favorite reg edit program, goto
HKCU\Software\HTC\HTCSENSOR\GSensor\Whitelist
3) now this is the part I kind of forgot, you need to find a string with the DATA value that includes "phone" or "dailer"
4) delete that string
5)soft reset and give it a try, the phone shouldn't go into landscape whenever you turn it during a call.
AstarteSV said:
I had the same issue too, whenever I put my phone up to my ear (left handed) it would go into landscape. The fix is simple but you have to edit a registry setting. I'm going by memory here, so please forgive the vague info
1) make sure to backup your reg info
2) using your favorite reg edit program, goto
HKCU\Software\HTC\HTCSENSOR\GSensor\Whitelist
3) now this is the part I kind of forgot, you need to find a string with the DATA value that includes "phone" or "dailer"
4) delete that string
5)soft reset and give it a try, the phone shouldn't go into landscape whenever you turn it during a call.
Click to expand...
Click to collapse
OK, I went where you said, but no dialer, and only phone entry is:
Phone/Lock/Compose/Picture
String= Dialog
And deleting this stopped "lefty" in call flipping? Doesn't make sense to me. Doesn't seem to only control dialer or phone.
Please confirm or anyone out there please help. I don't want to delete something don't understand.
Can I simple change Dialog to something like "Zero" or "0"?
MLT2004 said:
OK, I went where you said, but no dialer, and only phone entry is:
Phone/Lock/Compose/Picture
String= Dialog
And deleting this stopped "lefty" in call flipping? Doesn't make sense to me. Doesn't seem to only control dialer or phone.
Please confirm or anyone out there please help. I don't want to delete something don't understand.
Can I simple change Dialog to something like "Zero" or "0"?
Click to expand...
Click to collapse
That's it! forgot what the process name was, but yeah, deleting that stopped the phone from trying to change to landscape during a phone call. Deleting that will tell the G-Sensor not to change the orientation of the phone's screen during a phone call, however it also tells it not to change the orientation during a picture (which wasn't a big deal for me cuz I can change it when I view them in windows). You can always look up the process in google or even the forum search tool if you're still scared.
If anyone else is interested I tried a "partial" delete of the suggestion above. I created a new string leaving out the Phone.
Lock/Compose/Picture
String= Dialog
deleted old string with phone/....
So far no more "lefty" crazy problems, and pictures seem to appear in landscape.
Here's hoping all is OK!
MLT2004 said:
If anyone else is interested I tried a "partial" delete of the suggestion above. I created a new string leaving out the Phone.
Lock/Compose/Picture
String= Dialog
deleted old string with phone/....
So far no more "lefty" crazy problems, and pictures seem to appear in landscape.
Here's hoping all is OK!
Click to expand...
Click to collapse
Awesome, good job!
I installed Gyrator 2. Just create a new event with the phone as the application. Nothing for orientation, nothing on stylus, and rotate screen for actions. Then promote the event to the top. Highlight your new phone event and select orientation, it will have a check mark and a number one next to the event. It hasn't failed on me yet and I use the key pad all day long with my job!
I just upgraded to the Verizon official WinMo 6.5 and the registry hack doesn't seem to work anymore, and I'm having issues getting Gyrator to work, has anyone resolved this issue for WinMo 6.5?
AstarteSV said:
I just upgraded to the Verizon official WinMo 6.5 and the registry hack doesn't seem to work anymore, and I'm having issues getting Gyrator to work, has anyone resolved this issue for WinMo 6.5?
Click to expand...
Click to collapse
I haven't had any of the issues with the 6.5 upgrade that were mentioned with 6.1. Haven't needed to add S2U2 since the screen lock is built in and the phone is much more responsive when placed to the ear and then moved away to access the keypad. It's not perfect but vastly improved over 6.1...
I guess my point is try it the way it is with 6.5 and see if you thinks its better. leave gyrator and reg hacks aside for a few.
I am talking about the setting that is usually found start>settings>all settings>personal>phone>cdma services>location setting. This is a Touch Pro 2 BTW.
I thought it would be under HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PhoneSetting\LocationSetting, but I did some testing and it doesnt seem to save under any of those keys. Here is what I did -
I made note of any reg keys under this branch that looked like they could be the one involved. I changed the setting back and forth from the front end so that it would turn the functionatlity on and off. I made each change tapped ok a couple of times then I rebooted the device. Once it booted up the setting did save in the front end, but the registry keys under that branch never did change their values.
I also did some testing with settings under
HKLM\system\Currentcontrolset\gpsintermediate driver\
and
HKLM\drivers\builtin\gpsdriver\
I changed the value back and forth in the front end but the regsitry keys never did change values. I rebooted in between changes and the front end did retain changes but not key changes were found.
Does anyone know where it is saved at? It seems that Google maps sets this automatically when it installs. I need to see how its done to implement in my software. Any help would be appreciated. Thanks!
bump it up
bump it up
C3C076 or one of you who are more familiar with this than I might be able to answer this...only I can't post in the proper thread due to thread post count....
Couple of things about this mod for the ThL W8. I have it running just fine but have some issues with it.
1. How do I get rid of the circle battery mod and go back to the stock battery icon?
2. How do I change the font on the lockscreen 'clock' app? The bolded hour looks terrible.
3. How do I stop the lockscreen from showing the left side box temporarily? It is showing that you can slide left to install widgets on the lockscreen but I don't like how it unbalances the look of the lockscreen.
4. Version 1.4 changelog mentioned that empty sim card slot notifications would be hidden....I still see a message for sim slot 2 being empty until I click the clear notification button.
5. Now that I think about it, could I just replace the digital clock app in 1.4 gravitymod2 with the stock clock app from android 4.1.2? If so, how?
Link to thread in question:
http://forum.xda-developers.com/showthread.php?t=2249808
1) You have 3 options a) learn to live with it b) decompile SystemUI and edit resource XMLs to hide circle mod and unhide stock battery c) flash different ROM
2) You can replace clock with another clock lock screen widget. There are many of them on play store, e.g. DashClock
3) There's no option for it. It's default Android 4.2 feature. There's an app called "lockscreen policy" which can disable side lock screen pages so it is maybe capable of hiding carousels, but I'm not sure.
4) it's not about disabling notification but hiding second signal icon in status bar
5) see 2)
C3C076 said:
1) You have 3 options a) learn to live with it b) decompile SystemUI and edit resource XMLs to hide circle mod and unhide stock battery c) flash different ROM
2) You can replace clock with another clock lock screen widget. There are many of them on play store, e.g. DashClock
3) There's no option for it. It's default Android 4.2 feature. There's an app called "lockscreen policy" which can disable side lock screen pages so it is maybe capable of hiding carousels, but I'm not sure.
4) it's not about disabling notification but hiding second signal icon in status bar
5) see 2)
Click to expand...
Click to collapse
Thank you for your reply C3C076.
Lockscreen Policy killed 3 birds with one stone! It disables lockscreen widgets, which also gets rid of the 'carousel' or box borders that show then fade for a second on the left side of the screen, and also disables the bold font on the clock hours! Nifty app and does just what I want there. Thanks for that!
6. There is a major bug that I and other uses are running into in the current version of GravityMod2 (1.4). My phone recent list and also text message contacts are getting split up. I send a message or make a call and it goes through fine. Then a return message or call is received and it shows up in my call log or messages as a different contact/person. It shows up received with the country code (+1) in my case and if I go to click on the profile/contact icon next to that number there is a message about an invalid number couldn't save contact. When I place calls by clicking on these received calls, I get a invalid number error message, click ok to dismiss it and then it will go through fine (using gv or not using gv in both cases).
I think that has something to do with the country code being added...I don't really know except it is kinda frustrating. Is there anything you can do to fix in an update to GravityMod2?
Ok Back to the topics above.
4. The missing sim icon is indeed gone (i didn't even really realize it because it never bothered me). The notification, other the other hand, really bugs me. I mean, that TRIANGLE CAUTION EXCLAMATION POINT! just BEGS for my attention and the notification comes up every boot or every airplane mode disable (cell radio on enable). I haven't tried this yet but I thought maybe freezing the specific sim toolkit app using titanium backup might cause this notification to not show up....unless the notification is from the OS itself in which case, any way you can disable that?
1. Thanks for the pointers. That will get me started towards changing the battery icon to suit my preferences.
7. Possible updates for the next version of GM2 to consider:
In version 1.4 of GM2, the file /System/etc/permission/com.android.sip.xml has the feature android.software.sip commented out (as per this topic by gmincca). I checked the other file: android.software.sip.voip.xml and the permission was not commented out. Maybe you missed that first one? Or it doesn't matter? I understand those permissions relate to the built in internet calling capability of this phone. I probably won't use it but I uncommented those two permissions in those files anyway using FX Explorer rooted to save the files after remounting as rw.
Volume levels for the earbuds while playing media (headset, media) were killing me ears! I used engineering mode to adjust the volume levels here under Headset mode, media, to be max of 112 and levels 0-6 to be 40, 64, 80, 96, 102, 108, 255. The last setting is for when plugged into a car speaker or external speaker you can still get max volume and the previous settings allow for actual listening with earbuds at a comfortable level. I do not know if these settings are on a per speaker basis and your mileage may vary with the usefulness of these. I thought it helped out a good bit. I also made some minor adjustments with the sound levels for the speakerphone (loudspeakermode, sph, level 6 to 160) to be able to hear the speakerphone better while on a phone call.
8. You got the auto brightness setting for the dark just right in your latest change. 0% brightness matched autobrightness just perfect! Only minor thing is in full daylight auto brightness was a little bit under 100% so didn't work as I thought. If the auto brightness % for full lux can be adjusted I'd like to know where, or if you could update for the next version of GM2 that would be awesome!
Thanks for all your hard work on this custom ROM for the ThL W8! Kudos/Karma/+1 to you!
6) This is a standard feature/bug of all mtk6589 4.2 roms. I can't do anything about it since we have no sources and messing with anything at java disassembled code level (smali) is a pain in the ass. Easy solution is to keep all your contacts with country code prefix and it'll be OK in case your operator sends the same caller ID for calls and messages. You should keep your contacts with prefix anyway to be able to call while roaming.
4) I might try removing that notification in the future
7) you're right about SIP. I missed that file. If you uncomment it SIP options will appear in Phone settings.
8) I didn't adjust upper levels, just lower ones. It would be helpful to measure light sensor values under different light conditions with some app and adjust levels. So if you like to experiment, any input will be welcome. I can send you current values.
C3C076 said:
6) This is a standard feature/bug of all mtk6589 4.2 roms. I can't do anything about it since we have no sources and messing with anything at java disassembled code level (smali) is a pain in the ass. Easy solution is to keep all your contacts with country code prefix and it'll be OK in case your operator sends the same caller ID for calls and messages. You should keep your contacts with prefix anyway to be able to call while roaming.
4) I might try removing that notification in the future
7) you're right about SIP. I missed that file. If you uncomment it SIP options will appear in Phone settings.
8) I didn't adjust upper levels, just lower ones. It would be helpful to measure light sensor values under different light conditions with some app and adjust levels. So if you like to experiment, any input will be welcome. I can send you current values.
Click to expand...
Click to collapse
6. I can say it is not solely 4.2 roms but also 4.1.2 as well. On the stock rom and on the update line brush package FH4, 4-28-2013 (4.1.2 and 4.2.1 respectively) both of those roms also experienced this issue with the contacts being added country codes on incoming calls/messages.
After I went through my google contacts and used UltraEdit32 (similar to notepad++) with regular expressions to remove parenthesis, spaces, and hyphens (and a bad contact that was gumming up the works), I was able to make calls again without it erroring out with that message. It would still give the error message but then the call would go through. I didn't add the country code at that time but I guess it wouldn't be to difficult to export/download my google contacts again, turn off syncing, fix/add my contacts, then delete the contact stores on my phones and resync with added country codes.
With that said, if I use the dialer to directly dial the number which isn't in my contacts I still get the "Call not sent, no valid number entered" error message. I have found this problem is related to Google Voice and the Dialer (Phone) app. If I turn off using Google Voice to make all calls or to ask every time and set it to do not make any calls, the calls will go through no problem, I need Google Voice though so I guess I'm left wondering if I can use a different dialer...perhaps the stock 4.2.1? I have no idea how to get started changing that though.
My phone's dialer is from GM2 currently: version 4.2.1-eng.zhangshuangshuang.1366707806
Other's who have had my same problems with GV integration had similar issues with Samsung's replacement/custom dialer causing issues. Can I get a stock dialer/phone app somehow?
4. Please! And thank you! Of note: using Titanium Backup to freeze the simtoolkit application didn't do anything. I didn't see stk1 and stk2 like in 4.1.2 and in the 'line brush update official 4.2.1 rom. I only saw the one simtoolkit app and freezing had no effect on the notification). When I long press the notification, and press 'app info' it brings up the phone app. This means the notification is coming from the phone app directly I guess.
8. I'd be interested in what the current levels are for the brightness. I can use GPS status to measure the current lux however it doesn't report the current screen light level brightness setting, just the incoming measured lux from the light sensor.
9. Developer mode is not enabled by default in GM2. I had to google to find my usb debugging setting. (Go to Settings -> About -> Press 7 times on the Build number). Maybe this is an easy toggle to enable this by default for the next build of GravityMod2? I mean we are flashing a custom rom after all Not a big deal really if not.
6) Using alternative dialer from vanilla Android is impossible "thanks" to dual sim extension. The changes in framework and telephony are too vast.
4) it's coming from telephony subsystem in the framework.
8) I'll provide lux/brightness pairs later today (hopefully)
9) My opinion is that it's OK how it is now. Most of the users don't need it. Those who do, already know how enable it or can find out easily.
Here are the brightness levels and corresponding LCD backlight values.
Code:
<integer-array name="config_autoBrightnessLevels">
<item>16</item>
<item>32</item>
<item>50</item>
<item>100</item>
<item>140</item>
<item>180</item>
<item>240</item>
<item>300</item>
<item>600</item>
<item>1000</item>
<item>2000</item>
<item>3000</item>
<item>4000</item>
<item>8000</item>
<item>10000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>20</item>
<item>30</item>
<item>50</item>
<item>60</item>
<item>70</item>
<item>80</item>
<item>90</item>
<item>102</item>
<item>110</item>
<item>120</item>
<item>130</item>
<item>180</item>
<item>200</item>
<item>210</item>
<item>230</item>
<item>255</item>
</integer-array>
C3C076 said:
Here are the brightness levels and corresponding LCD backlight values.
Code:
<integer-array name="config_autoBrightnessLevels">
<item>16</item>
<item>32</item>
<item>50</item>
<item>100</item>
<item>140</item>
<item>180</item>
<item>240</item>
<item>300</item>
<item>600</item>
<item>1000</item>
<item>2000</item>
<item>3000</item>
<item>4000</item>
<item>8000</item>
<item>10000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>20</item>
<item>30</item>
<item>50</item>
<item>60</item>
<item>70</item>
<item>80</item>
<item>90</item>
<item>102</item>
<item>110</item>
<item>120</item>
<item>130</item>
<item>180</item>
<item>200</item>
<item>210</item>
<item>230</item>
<item>255</item>
</integer-array>
Click to expand...
Click to collapse
I did some testing in direct sunlight.
Anything over 8000 lux needs full brightness to be able to see the screen (even when the screen is set to 100% brightness in anything over 8000 lux it is still kinda of hard to see but that's why it needs to be full brightness on auto for 8000+).
In shade, but still bright out, the lux read about 6000 and the auto brightness setting was good.
I in framework-res.apk, changing those last two lux levels I think would help.
<item>6000</item>
<item>8000</item>
...
<item>230</item>
<item>255</item>
I tried decompiling and recompiling framework-res.apk after making the changes but couldn't get it to work. I wasn't sure how to install it. I used apktool and apkmultitool to decompile framework-res.apk and then change /res/values/arrays.xml and saved the files. Then I compiled and also tried signing them to produce the new apk. So far so good.
I then tried installing using apkmultitool install apk and it didn't work. It just said waiting on device. I tried rebooting my phone, tried recovery mode, tried regular just plugged in and turned on mode and nothing. USB debugging is enabled.
I also tried copying the changed apk directly to /system/framework (after first mounting as rw and changing the permissions of the new apk to match the permissions of the current framework-res.apk) using copy and paste on FX "file explorer." It would freeze when I gave it the paste command (yes it had root permissions).
I don't know how to install the changed apk or how to update this to get the new brightness settings. As the copy operation had froze the app, even pressing home did not work so I had to use my nandroid backup to revert phone to a useable state again.
When you compile modified apk in multi tool, say yes when it asks you if it's a system apk. Then say yes to create "keep" folder and delete resources.arsc from it, and then finish compiling process.
C3C076 said:
6) Using alternative dialer from vanilla Android is impossible "thanks" to dual sim extension. The changes in framework and telephony are too vast.
4) it's coming from telephony subsystem in the framework.
8) I'll provide lux/brightness pairs later today (hopefully)
9) My opinion is that it's OK how it is now. Most of the users don't need it. Those who do, already know how enable it or can find out easily.
Click to expand...
Click to collapse
6. Great. Perhaps an alternative dual-sim dialer is available...I didn't check...are the stock 4.2.1 (FH4 4-28-2013 official update) dialer and the Eastcom/GravityMod2 dialers the same? Could that kind of change be made and fix up these crazy errors?
4. Does that mean it is also impossible or just kinda difficult to fix?
9. Agreed and hey, thanks for taking the time to answer all my questions. Hopefully I can help in some way too
I managed to solve 4) already. I mentioned it in GM2 thread.
C3C076 said:
When you compile modified apk in multi tool, say yes when it asks you if it's a system apk. Then say yes to create "keep" folder and delete resources.arsc from it, and then finish compiling process.
Click to expand...
Click to collapse
Apkmultitook didn't prompt me about this, possibly because I chose the decompile system apk option at first. In fact, the compile process finished just fine with no errors. (Hopefully it was a good format for being a system apk but it didn't ask about that so...)
Once I have the compiled apk...I wasn't sure what to do with it. I was able to verify I had changed the xml file by decompiling the new apk but couldn't get it installed on my phone. I was probably doing something wrong. Is copying and pasting correct?
Have you tried wiping dalvik cache?
C3C076 said:
Have you tried wiping dalvik cache?
Click to expand...
Click to collapse
In what order would I do that?
Wipe the dalvik cache from recovery....then what? Try copying and pasting the new apk again? How does wiping the dalvik cache help here?
OK. I wiped the dalvik cache and then rebooted. Tried replacing my current framework-res.apk again with the new one (after setting permssions on the file first) and I still get a freeze at coping files. I might try again later with a different app with root access that can remount the /system as rw. Or maybe look into creating a update.zip and trying from recovery if that is possible.
I typically use "adb push" while in recovery (system partition must be mounted)
Good new everybody.
Looks like I fixed the Caller ID issues. At least for phone calls now.
This means that contacts stored without country code will be matched to caller ID sent by operator containing country code.
Messages seem to be handled differently (damn it) but I will try to look into it, too.
C3C076 said:
Good new everybody.
Looks like I fixed the Caller ID issues. At least for phone calls now.
This means that contacts stored without country code will be matched to caller ID sent by operator containing country code.
Messages seem to be handled differently (damn it) but I will try to look into it, too.
Click to expand...
Click to collapse
Waiting for this update for phone and Messages.
C3C076 said:
I typically use "adb push" while in recovery (system partition must be mounted)
Click to expand...
Click to collapse
Thanks. That was part of the problem.
The other part was since it was a system apk, I signed it thinking that's what it needed but I read a comment that stated that system apks shouldn't be signed. All I had to do was make my changes, compile it, then copy over meta-inf and AndroidManifest.xml from the original to the newly compiled apk. Then, adb push was correct as you stated for system apks.
On a side note I had to manually put in my java jdk path for android's sdk by editing the \adt-bundle-windows-x86_64-20130219\sdk\tools\lib\find-java.bat file with my jdk path....and I had to make sure I had the adb driver installed which was another hiccup. Once all those settled then I could use adb and apkmultitool etc worked fine.
I pushed the changed framework-res.apk to my phone verifying the changes were made and testing the light sensor values with 'GPS Status' which shows the lux...AND IT WORKED!! I can now leave the brightness on Auto and it works just fine
The change made was to framework-res.apk\res\values\arrays.xml
Changed lines 554 and 555 to be 6000 and 8000 respectively instead of 8000 and 10000.
Can you incorporate this change into the next version of GM2 C3C076?
So, new topic:
10. What files in SystemUI.apk or framework-res.apk are for the Cyanogenmod circle battery? I looked all through those two and couldn't find the graphics of the circle battery?
Thanks again!
Great I will include it in today's release.
CM circle battery is not image based. It is a self-drawing ImageView. It's in CircleBattery.smali in statusbar/policy.
It is referenced in layout xmls. The change would be easy. Just remove references from 2 xmls and remove visibility="gone" from standard battery references.
@C3C076, sir could you share how you were able to fix the Caller ID problems of your phone/rom. I currently own a ZTE V987 and have been trying to look for a fix for the same problem. I currently have android 4.1.2 Thanks!
I have a rooted Xperia Z lollipop. I want to disable the User add function as I am giving my kid access to the phone with screen time app. How can I make that disappear?
I have set the user_enable to "0" in the setting database but it doesnt work. Do I need to edit build.prop?
Have a look at this https://www.reddit.com/r/Android/comments/323l36/android_5x_how_to_disable_guest_additional_user/
Make sure you have backup of files you edit, it's very easy to **** up when manually editing files
edit: lol just noticed xda censors swear words, this reminds me that i have seen a setting in maybe gravitybox or some app where u can remove add use or switch guest from notification bar on top, which is probbaly what you want to do, i will check around and see where i found it.
EDIT: Another thing I just tried and it works well
Add the following lines to your build.prop
fw.max_users=1
fw.show_multiuserui=0
Change the max users number to however many users you have on phone now. I did the database change earlier too, and after adding these two lines there's still icon on lock screen to switch users but it doesn't do anything, i got a long loading the first reboot, but that maybe because i am also playing around with xposed modules, just force reset the phone by pressing volup and power for 3 seconds and it should boot. Hope this helps.
I read it. Did as said. Added fw.max_users=1 but did not add fw show... The phone went into boot loop...
Can you share your build.prop? I wonder what I have done wrong.... Duh
Do I need to add "ro.sys." before the fw.max and fw.show?