Related
i'm using Galaxy SII i9100 Orange, and when i try to update my phone to Android 4.0.3 i dont have lockscreen. everytime i press power button it come to Home screen .
i've using both Cook rom ICS and stock rom ICS : XXLPQ stock official rom Android 4.0.3 but nothing change.
not only me , my friend have the same problem. i change in settings -> Security -> ScreenLock and chose whatever you want (pin,pattern,facedetection,slide) but nothing happen.
any idea to fix this thanks a lot.
ps: sr for my bad English
kenjilolip0p said:
i'm using Galaxy SII i9100 Orange, and when i try to update my phone to Android 4.0.3 i dont have lockscreen. everytime i press power button it come to Home screen .
i've using both Cook rom ICS and stock rom ICS : XXLPQ stock official rom Android 4.0.3 but nothing change.
not only me , my friend have the same problem. any idea to fix this thanks a lot. i want to try face unlock on android 4.0.3 T.T
ps: sr for my bad English
Click to expand...
Click to collapse
OMG WHAT ARE YOU GUYS !!! oneday you all "noobs" gona post here " why we dont have credits to make calls" WTF !!
Go to settings -> Security -> ScreenLock and chose whatever you want (pin,pattern,facedetection,slide)
lummujaj said:
OMG WHAT ARE YOU GUYS !!! oneday you all "noobs" gona post here " why we dont have credits to make calls" WTF !!
Go to settings -> Security -> ScreenLock and chose whatever you want (pin,pattern,facedetection,slide)
Click to expand...
Click to collapse
sr. but u dont understand . i change everything but still dont have lockscreen =.= i'm not that stupid
kenjilolip0p said:
sr. but u dont understand . i change everything but still dont have lockscreen =.= i'm not that stupid
Click to expand...
Click to collapse
back to 2.3.5 and w8 for the official ICS , they said xxlpq is official but it has many bugs ! stay on 2.3.5 and search over market ,there are many facedectection lock programs !
lummujaj said:
back to 2.3.5 and w8 for the official ICS , they said xxlpq is official but it has many bugs ! stay on 2.3.5 and search over market ,there are many facedectection lock programs !
Click to expand...
Click to collapse
i came back 2 GB and still waiting. dont no what happen with my phone
lummujaj said:
OMG WHAT ARE YOU GUYS !!! oneday you all "noobs" gona post here " why we dont have credits to make calls" WTF !!
Go to settings -> Security -> ScreenLock and chose whatever you want (pin,pattern,facedetection,slide)
Click to expand...
Click to collapse
lummujaj
Posts: 71
Join Date: Jun 2011
Bwahahahahaha
no one have problem like me
try factory reset phone
i also get same problem no lock screen and airplane mode , handser directly shutdown when ever i press poer button, no flight mode and no other option comes
http://forum.xda-developers.com/showthread.php?p=22669088#post22669088
The first thing I would try would be doing a full wipe. I suppose you just flashed it on top of GB.
madddi2011 said:
The first thing I would try would be doing a full wipe. I suppose you just flashed it on top of GB.
Click to expand...
Click to collapse
I did the same thing (flashed XXLPQ on top of GB), and I'm having the same problem. No lock screen/phone isn't going into sleep mode. Long-pressing the power button gives no options but simply turns off the phone. So I've decided to do a full wipe, but at the risk of sounding like a total noob, what do I need to do exactly? I've already gone through CWM Recovery mode, wiped all the data and user cache. Also did a factory reset. That brought the phone back to default settings, but yet still on ICS, with still the same problems. I reflashed ICS and still no good. Obviously I'm doing something wrong, but what do I do? I'm thinking I'm meant to revert back to GB, or maybe even back to the original stock build (though I didn't backup the ROM). But I'm also wondering how that would work without causing problems, since I'd be flashing an old GB build on top of ICS.
In short: I'm a noob and I don't know what to do. Please help!
Edit: I never lost the "NO" keystr file in my efs/imei folder.
Edit 2: FIXED! Both lock screen and power button options are back.
Despite having retained the keystr file, it was actually necessary to fix it up... Here's how I did it (make sure your device is rooted):
Download "Android Terminal Emulator" from the Play Store. Just open it and type in this code:
su
echo -n ON > /efs/imei/keystr
sync
reboot
Click to expand...
Click to collapse
And that's it.
I have since turned off my phone and turned it back on and it is still working fine, so you shouldn't have any problems retaining the file upon reboots. I hope this solves your problem.
Tizza said:
I did the same thing (flashed XXLPQ on top of GB), and I'm having the same problem. No lock screen/phone isn't going into sleep mode. Long-pressing the power button gives no options but simply turns off the phone. So I've decided to do a full wipe, but at the risk of sounding like a total noob, what do I need to do exactly? I've already gone through CWM Recovery mode, wiped all the data and user cache. Also did a factory reset. That brought the phone back to default settings, but yet still on ICS, with still the same problems. I reflashed ICS and still no good. Obviously I'm doing something wrong, but what do I do? I'm thinking I'm meant to revert back to GB, or maybe even back to the original stock build (though I didn't backup the ROM). But I'm also wondering how that would work without causing problems, since I'd be flashing an old GB build on top of ICS.
In short: I'm a noob and I don't know what to do. Please help!
Edit: I never lost the "NO" keystr file in my efs/imei folder.
Edit 2: FIXED! Both lock screen and power button options are back.
Despite having retained the keystr file, it was actually necessary to fix it up... Here's how I did it (make sure your device is rooted):
Download "Android Terminal Emulator" from the Play Store. Just open it and type in this code:
And that's it.
I have since turned off my phone and turned it back on and it is still working fine, so you shouldn't have any problems retaining the file upon reboots. I hope this solves your problem.
Click to expand...
Click to collapse
zia my phone dont have keystr , so i make 1 and type On . so it working ^^ now i have my lockscreen and power button work.
so same problem but we have different bug :|
1. dont have keystr
2. have keystr but have to use Terminal Emulator to fix it
I couldn't find anyone facing this problem but here it goes
I just flash stock official XWLP7 firmware with CSC JVLPB build: 03/04/2012
and the problem is that whenever i press the power button to lock my phone, it just turns off the screen, and whenever i press it back it just turns it on without going through anylockscreen even if i put a PIN or a PATTERN
Can this be solved??
Think i'V seen this before.....
Sure it is not a custom ROM?
Dial wipe code, or flash again.
Sent from my GT-I9100 using Tapatalk 2
yes it's not a custom rom, and I already did a wipe and flashed again, but still same
I had the same problem and i flashed again. Its the better way to solve it
Check if you have /efs/imei/keystr with "ON" inside it, if you don't, create it.
Have you looked under settings -> security to check the automatically lock setting?
oinkylicious said:
Check if you have /efs/imei/keystr with "ON" inside it, if you don't, create it.
Click to expand...
Click to collapse
You're the man!!! It just worked wonderfully thank you!!
i am having a problem with my samsung galaxy s2, the power menu doesnt come up when i press the shut down button but it switches off straight away, and the lock screen doesnt work, non of them does. i would be so grate full for who ever can find me a solution
Backup data and factory reset first .
jje
i would have said the same as jje said..
It happens exactly the same
my sgs2 doesn´t block the screen and when I hold the power button it turns off directly, I just Installed ICS and does not work either unlock pattern or pin just turn off the screen and when i push the home button or the porwer button just turn on, does not show any unlock screen, i´ve already done the factory reset and wiped cache and still the same, it´s the same problem i hope that anyone can help us please, thanks
i tried everything but it still doesn't want to work --.
i flashed the gingerbread rom it works perfectaly but slow as hell. even though i admit ics is a great rom to have, but why cant someone find a solution to this stupid problem
socialspider11 said:
i tried everything but it still doesn't want to work --.
i flashed the gingerbread rom it works perfectaly but slow as hell. even though i admit ics is a great rom to have, but why cant someone find a solution to this stupid problem
Click to expand...
Click to collapse
Sounds like a bug. Try flashing DXLP9.
socialspider11 said:
i am having a problem with my samsung galaxy s2, the power menu doesnt come up when i press the shut down button but it switches off straight away, and the lock screen doesnt work, non of them does. i would be so grate full for who ever can find me a solution
Click to expand...
Click to collapse
You're missing your /efs/imei/keystr file. Do a google search for "/efs/imei/keystr fix". You'll need root to apply the fix.
i360* said:
Sounds like a bug. Try flashing DXLP9.
Click to expand...
Click to collapse
This MIGHT work instead of what I suggested above, but I didn't think firmware flashes included or built/rebuilt the keystr file. I could be wrong though.
same problem..fixed after rooting
same problem here...just upgraded from 2.3.5 to Android ICS I9100XWLP7 and facing the exact issue of no screen lock and no power button menu....
Update:
Rooted phone using http://forum.xda-developers.com/showthread.php?t=1501719
and
fixed issue using http://forum.xda-developers.com/showthread.php?p=26542830#post26542830
darengive said:
same problem here...just upgraded from 2.3.5 to Android ICS I9100XWLP7 and facing the exact issue of no screen lock and no power button menu....
Click to expand...
Click to collapse
Dude. Look one post up.
thanks
ctomgee said:
Dude. Look one post up.
Click to expand...
Click to collapse
thanks, wanted to share info...
I had the same problem last week, this thread solved it for me, follow it from the 7th post to the end: http://forum.xda-developers.com/showthread.php?t=1547449&page=2
Thank You, it works a treat.
solved .. atlast
ried everything, then I found a s2 with working power menu and everything .. noted its firmware .. searched on net (link given below) and flashed everything in package .. everything is running as it should .. Sharing it coz I didnt find proper solution for me anywhere .
http://www.trickytweaks.com/i9100xxlsj-4-1-2-galaxy-s2-i9100-jelly-bean-update-tutorial.html
Root your device then open root folder with x-plore app after that go to following directory
efc>imei
Creata a file
Keystr
Openfile as text and write "ON"
Save the file
Tap and hold the file a menu will pop up click on permission
First deselect all boxes and click ok
Again go to permission and select all boxes under read write column click ok
Go to settings>lock screen
Re-enable Lock instantly with power button option.
---------- Post added at 03:17 AM ---------- Previous post was at 02:53 AM ----------
Root your device then open root folder with x - plore app after that go to following directory
efc / imei
Creata a file Keystr
Openfile as text and write " ON " Save the file
Tap and hold the file a menu will pop up click on permission
First deselect all boxes and click ok
Again go to permission and select all boxes under read write column click ok
Go to settings > lock screen
Re - enable Lock instantly with power button option
:good:
---------- Post added at 03:25 AM ---------- Previous post was at 03:17 AM ----------
Root your device then open root folder with x - plore app after that go to following directory
efc / imei
Create a file named "Keystr"
Openfile as text and write " ON " Save the file
Tap and hold the file a menu will pop up click on permission
First deselect all boxes and click ok
Again go to permission and select all boxes under read write column and click ok
Go to settings > lock screen
Re - enable Lock instantly with power button option.
:good:
Hi
I have a 4.0.3 france firmware installed samsung I9100G.But lately the no lockscreen problem (holding the power button will not bring the options and just shuts the phone off),ringtone and a few other problems started to annoy me really bad.
I'm thinking to install the 4.0.4 german firmware from samfirmware but how stable is it? is there any problem with the 4.0.4 or anything special i should know about it?
i have reflashed the 4.0.3 but those problems didnt go away.
thanks for any helps.
Go back to GB.For me that is more stable than ICS or JB.
Sent from my GT-I9100 using xda premium
If the firmware is official, it should be stable. So, your choice: or GB, or ICS.
burning_afd said:
Hi
I have a 4.0.3 france firmware installed samsung I9100G.But lately the no lockscreen problem (holding the power button will not bring the options and just shuts the phone off),ringtone and a few other problems started to annoy me really bad.
I'm thinking to install the 4.0.4 german firmware from samfirmware but how stable is it? is there any problem with the 4.0.4 or anything special i should know about it?
i have reflashed the 4.0.3 but those problems didnt go away.
thanks for any helps.
Click to expand...
Click to collapse
May be I can help you fix all your 4.0.3 problems instead of messing with your phone.
Post all the problems you are facing, and we'll get started
Swyped from my Galaxy SII
Jokesy said:
May be I can help you fix all your 4.0.3 problems instead of messing with your phone.
Post all the problems you are facing, and we'll get started
Swyped from my Galaxy SII
Click to expand...
Click to collapse
updated to 4.0.4 but nothing changed.
ok here are the problems:
- The power button options are not showing up. if i hold the power button it just closes the phone directly.
- The screen lock doesnt work. Wont lock the screen with any option there.
- The sim lock doesnt work. If i put the sim lock on (put a lock on the sim) the phone starts normally but wont let me call or text. So i have to disable the lock on the sim to make it work normal.
Now these are the problems i have seen so far. When i got the phone it was GB and there was absolutely no prob until updating to ICS. So whats the suggestion, should i give a try on custom firmware ICS or go back to official GB? if you say custom firmware then which one?
burning_afd said:
updated to 4.0.4 but nothing changed.
ok here are the problems:
- The power button options are not showing up. if i hold the power button it just closes the phone directly.
- The screen lock doesnt work. Wont lock the screen with any option there.
- The sim lock doesnt work. If i put the sim lock on (put a lock on the sim) the phone starts normally but wont let me call or text. So i have to disable the lock on the sim to make it work normal.
Now these are the problems i have seen so far. When i got the phone it was GB and there was absolutely no prob until updating to ICS. So whats the suggestion, should i give a try on custom firmware ICS or go back to official GB? if you say custom firmware then which one?
Click to expand...
Click to collapse
It's always recommended to perform a factory reset after upgrading your phone software
Swyped from my Galaxy SII
For me the samsung stock roms are like windows o/s.
GB=xp
Ics=vista
Jb=w7
A crude comparison......but vista was a pile of crap.....
Sent from my GT-I9100 using xda premium
burning_afd said:
updated to 4.0.4 but nothing changed.
ok here are the problems:
- The power button options are not showing up. if i hold the power button it just closes the phone directly.
- The screen lock doesnt work. Wont lock the screen with any option there.
- The sim lock doesnt work. If i put the sim lock on (put a lock on the sim) the phone starts normally but wont let me call or text. So i have to disable the lock on the sim to make it work normal.
Now these are the problems i have seen so far. When i got the phone it was GB and there was absolutely no prob until updating to ICS. So whats the suggestion, should i give a try on custom firmware ICS or go back to official GB? if you say custom firmware then which one?
Click to expand...
Click to collapse
1. If your phone is not rooted, root.
2. Create file /efs/imei/keystr, containing the word ON.
3. Make sure the file has rw-r--r--, or 644 permissions.
4. ...
5. Profit!
ctomgee said:
1. If your phone is not rooted, root.
2. Create file /efs/imei/keystr, containing the word ON.
3. Make sure the file has rw-r--r--, or 644 permissions.
4. ...
5. Profit!
Click to expand...
Click to collapse
ok thank you very much bro. that did it
i first rooted the phone from here: http://forum.xda-developers.com/showthread.php?t=1679778 with the option 2.
then used this little guide:
- Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
Go to home, force close your terminal app, shut your screen off, and when your turn it back on your lock screen should? be there.
Obviously you must be rooted the "su" command
And for Signal Problem Simply do not put any pin on your sim ,,,
I have been using epinter's CM10.1 for Atrix 4g and following the Atrix 4g CM10.1 developer discussions. I am trying to get the camera flash to work. krystianp posted that one should extract from CM9, the files tcmd and tcmdhelp and put in /system/bin. But I cannot find a CM9 for the Atrix 4g (olympus) that has these files. Does anyone know where to find them? (Would have posted to the CM10.1 thread but don't have permission to do so.)
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Thanks
andresrivas said:
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
rhcohen said:
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
Click to expand...
Click to collapse
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
reply
Feche said:
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
Click to expand...
Click to collapse
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
rhcohen said:
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
Click to expand...
Click to collapse
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
reply
Feche said:
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
Click to expand...
Click to collapse
For what it is worth, I just installed the 12/31 kernel and the flash with stock camera app now DOES work for me*, and the timing even seems to be OK. So someone ought to be interested in understanding the difference between your configuration and mine. (If anyone is actually following this, my sequence, executed over the past week or so, was a wipe/clean install of epinter's 12/11 CM10.1 rom, followed by his latest gapps, followed by a second flash of the 12/11 rom. Then this morning putting the tcmd and tcmdhelp files in /system/bin, with appropriate permisssions; and then finally flashing krystianp's 12/31 kernel.) Too soon to comment on battery life.
I think this kernel is supposed to be logging network disconnects (which I also seem to experience, about one a day, requires reboot to reconnect). Do you know where we find the resultant logs, and how (lacking permissions to post at the developers' site) we are supposed to deliver them to krystianp? I notice that, in response to a submitted log file, krystianp made a post about restarting the radio from a terminal, which didn't actually achieve a re-connection for the one person who tried it.
* small update: the flash works with stock app, but only if I do a spot ("touch") focus first. Small price to pay!
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks --- so I found the relevant krystianp post on the logs:
http://forum.xda-developers.com/showthread.php?p=48954198&highlight=dmesg#post48954198
Specifically,
"To get kernel log just do (as root):
dmesg>/sdcard/kernel.log
And for radio log do:
logcat -b radio >/sdcard/radio.log
(Logcat works continuously so you might have to use ctrl+c to cancel it) "
Question is, what do I do with these logs? I could attach them to a reply at the developer forum if I had permission to reply....
Presumably I don't want to keep running this kernel with debugging turned on forever.
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks, I will wait a couple of days so there is some accumulated info in the logs and do that. So far, no drops and one spontaneous reboot.
reply, to forward to krystianp
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
rhcohen said:
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
Click to expand...
Click to collapse
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
You should have mention him by @krystianp . Not sure it will work from the phone
Hit the damn thanks button instead!
Enviado desde mi MB860
RE turning radio off and on
overboard1978 said:
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
Click to expand...
Click to collapse
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
further update
rhcohen said:
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
Click to expand...
Click to collapse
----------
OK I have a further update. Using the testing tab from the dialer gives me the option of turning the radio off; when I click it nothing changes -- in particular no option to turn the radio on.
When I try krystianp's echo "shutdown" and echo "powerup" commands, I get a system prompt back but no indication that anything has changed with the radio (though maybe it would be reflected in the radio logs). In any event, certainly no connection to the network.
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
rhcohen said:
----------
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
Click to expand...
Click to collapse
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
reply; and what is "uv"?
PolesApart said:
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
Click to expand...
Click to collapse
-------------
Thanks. Sending the logs may no longer be relevant; @krystianp posted a new kernel a day and a half ago. I flashed it yesterday, and so far, no radio drops. If I get any I will post another message with logs and also send a message to krystianp.
I notice in describing the new kernel he says he made changes to radio and UV. Can someone tell me what is UV? I tried a search in the 10.1 developer forum and a more general google search but find nothing useful (I suspect this use of "UV" does not mean "ultra-violet".)
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
reply
PolesApart said:
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
Click to expand...
Click to collapse
I saw today's post but didn't interpret it the same way. He had already said that this kernel, along with the one from 12/31, were for people with the disconnect errors (which I was getting), but when he posted the Jan 5 kernel he indicated there were changes to radio and UV; I thought today's notice was just reaffirming the purpose of both the 12/31 and 1/5 kernels.
The 12/31 kernel clearly did more than just turn on logging however, as it seems to have fixed the camera flash for many (including me).
And the 1/5 kernel seems to be working more stably for me -- 1 1/2 days now without a radio drop. Maybe just luck.