Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. NOT MINE anymore. Thanks Frederic Van Assche
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Development Section
Im currently really busy with school, so most of the work will be done on the weekends.
Current development status, and todo list.
1) The lockscreen size mod works fine. Few small code cleanup things and stuff needed.
2) The visible dot toggle has a setting and works perfect. The checkbox sometimes doesn't display right so you may have to click it twice to turn it on/off (not sure whats wrong, low priority).
3) Custom lockscreen message works great. Sometimes you have to enable+disable it for it to update (work on auto do/fix). And I haven't added it to the PIN lock and stuff (have to check). In the end I would like the enable/disable and message to be on a different settings screen (like on Honeycomb).
4) And the carrier name thing is now obsolete. Thanks to the patch by Frederic Van Assche, shown to me by one_love_420.
Ohh. And if any of you have any suggestions on things to add or change, i'm happy to listen and try.
Beta Testing.
Current Bugs
Code:
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
Notes
These builds are buggy. Use at your own risk.
If you cannot unlock your phone, you can fail 5 times and then log in with your google account.
Downloads
http://androtransfer.com/development/smasher816/cm7 beta/
For a better way to do the custom carrier text and to have it in the settings as an option check this over at the gerrit. I have used since he posted it for review and it works great.
http://review.cyanogenmod.com/#change,7314
And
http://review.cyanogenmod.com/#change,7313
Sent from my PG06100 using Tapatalk
Thanks man.
I'm assuming I would run the patch command (git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git format-patch -1 --stdout FETCH_HEAD)
Edit: that seemed to do nothing but output the changes.
I did the checkout one ("git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git checkout FETCH_HEAD") and now it says
Code:
~/android/system/packages/apps/CMParts$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts refs/changes/13/7313/3 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts
* branch refs/changes/13/7313/3 -> FETCH_HEAD
Note: checking out 'FETCH_HEAD'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 5ed9b01... Custom carrier label (2/2)
Sorry, i'm still pretty new at git. What do I do now?
I'm new to the git and I do it probably the more difficult way but it gets the job done. What I do is download each change one by one, use "meld" to compare my java/xml files and add the new edits in. Like I said the more difficult way to do it.
Sent from my PG06100 using Tapatalk
Smasher816 said:
Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. No setting yet.
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Developer Help Needed Section.
1) For the carrier name replacement I edited
Code:
String plmn = "<WHATEVER>"; //ss.getOperatorAlphaLong();
(line 587) in GsmServiceStateTracker.java. I would like to find a way to add this as a setting to CMParts but haven't looked around enough to figure out how yet. If any of you could hint me in the right way or something that would make my life easier.
2) SOLVED
Click to expand...
Click to collapse
how do we change our pattern size???
maxib123 said:
how do we change our pattern size???
Click to expand...
Click to collapse
If you read, he's developing it. Hence, you can't get it as of this moment.
sixstringsg said:
If you read, he's developing it. Hence, you can't get it as of this moment.
Click to expand...
Click to collapse
sorry, it wasnt that clear first time i read it
If you want a tester btw, you know where to find me
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
have you tried chmod 777? if im on the right page, that should work. if not i have no idea mate, sorry
Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
e2fsck -A /dev/sda2
Try that
I ended up getting my read only changes and putting them on my actual computer,
then re doing my VM and melding my changes back in.
I got a backup, and a build made.
However settings crashes (doesn't look like my edits). I will attempt to fix it. Worst comes to worse go back to the good build and merge piece by piece.
Edit: The last two weeks and weekends have been super busy, barely able to turn on my PC. Anyways I got a 4 day weekend coming up, I should hopefully have everything worked out then.
any progress yet?
maxib123 said:
any progress yet?
Click to expand...
Click to collapse
He's got most of the work done, he just needs to get it all merged and get it all up on github. He got distracted by a fun new build system for our kernel.
Edit: Disregard the old information. I now have some freetime over this weekend, the last two weeks have been crazy busy. I am slowly putting my tweaks into the latest nightly and making sure everything is working (vm redo). Anyways the newest build works! - You go to settings -> location and security -> Change Screen Lock -> Confirm saved pattern -> Choose unlock type (pattern) -> Choose pattern size (3-5) -> Draw new pattern (x2).
Where in the settings should the custom lockscreen message be? CMParts -> Lockscreen -> Widget Options -> Custom Message, or Security -> Owner Info (like honeycomb), or somewhere else?
i prefer
CMParts -> Lockscreen -> Widget Options -> Custom Message
Click to expand...
Click to collapse
what i like best about this project is
a) i`ve always wanted a 5*5 unlock pattern
b) you`re working this into the Cyanogenmod Project
Thanks.
Heres a little development update. Im working on getting the 5x5 lockscreen perfect before adding back in the lockscreen message and stuff. The actual 5x5 works fine, all my problems come from the dynamically changing size. Im trying to fix these two important bugs I have found. Hopefully I can get it solved, if not I might upload my work and see if you guys can help me out
Code:
#BUGS#
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
If your willing to put up with these bugs check the OP.
Is there anyway to add this on to a current build of cyanogen nightly rather than flashing an older one?
Sent from my Nexus One using XDA App
Ummmmm. I edited frameworks/base and packages/apps/Settings
So So replace the Settings.apk and framework folder or something.
This is something,I don't mind testing out. hopefully it'll work on cm7.1
From my fist to your face, enjoy.
any idea why this is happening?
eg i can click on the "cancel" but the install" word/icon there is no response.
i did change the ui, but again changed back to default but still the same
Disable halo
its a security feature, google does not allow overlays to run over that button - they could generate virtual clicks and install malware. pa's got a temporary "fix" against that, pac should either use it or instruct their users whats up with the button, since dragging halo over the red x for a sec is a possible solution, too.
Im on stock rooted Android 5.0. Is there an easy way for me to enable translucent decor for the status and nav bar?
jtseidner said:
Im on stock rooted Android 5.0. Is there an easy way for me to enable translucent decor for the status and nav bar?
Click to expand...
Click to collapse
Sorry for not having an answer. But just to double check: I'm on rooted stock (factory image by google), too. Do you also have neither a translucent statusbar nor a coloured statusbar? E.g. my statusbar stays black while having gmail open, although it supposed to be red.
j0hnnie said:
Sorry for not having an answer. But just to double check: I'm on rooted stock (factory image by google), too. Do you also have neither a translucent statusbar nor a coloured statusbar? E.g. my statusbar stays black while having gmail open, although it supposed to be red.
Click to expand...
Click to collapse
Correct, mine is working the same way...
I think the only option is to decompile /system/framework/framework-res.apk and change the appropriate lines in config.xml. If my copy of apktool didn't keep choking on framework-res.apk I would've tried (and probably failed) already.
EDIT: apktool did not decompile framework-res.apk. Until there's a working version I don't think it's going to change unless Lollipop's built from source.
Waiting for this fix too
Waiting for this too. I had translucent bars thanks to gravitybox before, they caused no smoothness issues. I dunno why google insists in keeping them disabled and make our tablet look 2012....
Like i understand there are three separated (and maybe independent) things:
1) translucent status bar (in launcher)
2) translucent navigation bar
3) colored status bar (in app)
On the first AOSP build i had 1+2. Now on factory image none is activated. Does anyone have more detailed information about how they correlate? And why the built from source version is not compatible with the factory image? Aren't there binary files generated on built which can be exchanged?
I decomplicated framework-res.apk but couldn't find config.xml
I made the change in ./frameworks/base/core/res/res/values/config.xml, built from source, and it didn't work. Then I discovered that I need to change it in ./device/samsung/manta/overlay/frameworks/base/core/res/res/values/config.xml. Gonna try building from source again and see if I can get a working framework-res.apk out of the build.
Aside: man, the update package did NOT like being dirty flashed on top of what I already had installed.
EDIT: No luck. Clean flashed the OTA package that I built, and there was no translucence to be seen. If anyone has any ideas on what I might be missing I am all ears, so to speak.
Thanks for trying! I wish I knew more to be of help..
No need to wait for me anymore. Here's one with translucent decor:
http://forum.xda-developers.com/showthread.php?t=1998585
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!