Open GoogleCodeExporter opened 8 years ago
+1 this is a good idea (but when asking a password, it should be like you're
putting password when in XMB Menu)
Original comment by Johnjohn...@gmail.com
on 17 Jun 2011 at 10:37
yes this would be a nice feature
Original comment by omnic...@gmail.com
on 18 Jun 2011 at 2:38
You have plugins that allow you to do this.
Not all the people are willing to slow their boot with a password.
Original comment by chlorhyd...@gmail.com
on 18 Jun 2011 at 10:43
neur0ner just released a password locker for 6.39! That's exactly what I'm
looking for, asking password when start up and in xmb!It would be a great
addition if this feature is added to 6.20 and 6.35 PRO CFW.
Original comment by Johnjohn...@gmail.com
on 18 Jun 2011 at 4:59
[deleted comment]
I like the idea of putting in the password from the XMB and I know that not
everyone would want the password that's why I was thinking it would be an
option in the menu just like CPU speed or which ISO driver you were using.
Maybe put it in the recovery menu under advanced options or something like that
to further bury it from unknowing people who don't need to be messing with your
psp or maybe name it something other then "Enable Password" or the like, make
it sound technical... something like "Log Background Processes" (of course you
would explain that it is the password option in the readme). It wouldn't be
forced, but it would be a nice option for those who want it.
Original comment by raptor1...@hotmail.com
on 18 Jun 2011 at 8:40
This enhancement may be done in the future.
Original comment by devnonam...@gmail.com
on 14 Jun 2012 at 9:00
Or what ya could do is integrate the XMB Control (FreeCore) v1.5.5 and fix the
Password Lock for only start-up not every time you enter xmb Like Total Noob
did in 6.20 Tn-D or Tn-E That was the best in his CFW. This should be the first
thing in the list to do many people would love this.
Original comment by why.je...@gmail.com
on 19 Sep 2012 at 5:05
Original comment by piotrekhenry
on 23 Jan 2015 at 4:44
Original issue reported on code.google.com by
raptor1...@hotmail.com
on 17 Jun 2011 at 7:31