hey everyone,
i have a strange issue and hope that someone can help me.
I use the neopeek Roms a lot and i have tried every single kernel.
But whenever the phone is in sleep mode io dont get any phone calls. the phone wakes up (red led) but thats it.
after i called my phone while it was in sleep mode it wouldnt go back into sleep mode.
i dont have this issue with the system.ext file androids.
over at neopeek.com we couldnt find a solution thats why im posting it over here.
thank you for ure help!
nick
the-nj said:
hey everyone,
i have a strange issue and hope that someone can help me.
I use the neopeek Roms a lot and i have tried every single kernel.
But whenever the phone is in sleep mode io dont get any phone calls. the phone wakes up (red led) but thats it.
after i called my phone while it was in sleep mode it wouldnt go back into sleep mode.
i dont have this issue with the system.ext file androids.
over at neopeek.com we couldnt find a solution thats why im posting it over here.
thank you for ure help!
nick
Click to expand...
Click to collapse
try pm.sleepmode=2 in your startup.txt
Eodun said:
try pm.sleepmode=2 in your startup.txt
Click to expand...
Click to collapse
We should not be using this in the newer kernels. BZO made a commit to the PLL2 code, and you should now either be using =1 or =0. I'd recommend =1 if you're OC'd, =0 if not. But not =2, assuming you're on a newer kernel (within the last 2 months I'd say...)
Also, to the OP - does this happen on FRX04 builds...? You also said you tried "every kernel" - there's some newer ones than autobuild, like 1253 - have you tried that?
hey,
thanks for your fast replies.
i already tried pm.sleep_mode 1 and 2 i have tried with and without oc.
currently im testing the FROYO B. but i have this issue with every build. ive tested every build so far. and i tried every other kernel i could find besides the autobuild. tested the 1253, the other one here at xda and the neopeek kernels.
had no luck with any kernel.
i had the same problem with the screen call ... it did not wake on any call but after i changed sleep mode to 2 it worked perfect
excuse my language
thank's man
hey,
thanks...i dunno why cuz normally pm.sleep_mode=2 shouldnt work but for some reason it does...seems to work...thanks
the-nj said:
hey,
thanks...i dunno why cuz normally pm.sleep_mode=2 shouldnt work but for some reason it does...seems to work...thanks
Click to expand...
Click to collapse
I tried sleep mode 1 and 2, still won't wake up. I also keep trying every new update between the kernel testing and the rootfs.
radcpuman said:
I tried sleep mode 1 and 2, still won't wake up. I also keep trying every new update between the kernel testing and the rootfs.
Click to expand...
Click to collapse
Are you overclocking? Assuming you're using a fairly new kernel, you should either be using 1 or 0 for the sleep_mode setting.
arrrghhh said:
Are you overclocking? Assuming you're using a fairly new kernel, you should either be using 1 or 0 for the sleep_mode setting.
Click to expand...
Click to collapse
No overclock. I have the latest test kernel and even today's rootfs update.
Here is my startup.txt.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2 pm.sleep_mode=0"
boot
I tried sleep_mode=1 earlier. If the LED is flash green, it doesn't wake up. I only started using the test kernels because non test stuff was doing the same thing. Everything else is working great since I turned off the GPS settings.
Would the incoming call issue be something that could be seen in log files by chance?
radcpuman said:
No overclock. I have the latest test kernel and even today's rootfs update.
Here is my startup.txt.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2 pm.sleep_mode=0"
boot
I tried sleep_mode=1 earlier. If the LED is flash green, it doesn't wake up. I only started using the test kernels because non test stuff was doing the same thing. Everything else is working great since I turned off the GPS settings.
Click to expand...
Click to collapse
There's some old deprecated commands in there. I highlighted them in red.
Also, why are you disabling hw3d? In addition, why do you have the north_am_dialing statement in there if it's set to 0? Also, I would definitely switch the sleep mode to 1.
What system image are you using? FRX04? I don't have this issue whatsoever, assuming the phone is doing OK (no SoD condition, no pegging proc, etc) the phone always wakes up for calls...
Have you tried deleting your data.img?
arrrghhh said:
There's some old deprecated commands in there. I highlighted them in red.
Also, why are you disabling hw3d? In addition, why do you have the north_am_dialing statement in there if it's set to 0? Also, I would definitely switch the sleep mode to 1.
What system image are you using? FRX04? I don't have this issue whatsoever, assuming the phone is doing OK (no SoD condition, no pegging proc, etc) the phone always wakes up for calls...
Have you tried deleting your data.img?
Click to expand...
Click to collapse
I'm using FRX04. Most of the setting except for pm.sleep_mode came from the startup utility. I have deleted the data.img once. I've even re-sized it to 769mb.
With the latest kernel image and rootfs I haven't had any issues except the dpad backlight stays on for a long time and incoming call issues. Then after a while will return to normal.
Should I take the hw3d out or set it to 1?
radcpuman said:
I'm using FRX04. Most of the setting except for pm.sleep_mode came from the startup utility. I have deleted the data.img once. I've even re-sized it to 769mb.
With the latest kernel image and rootfs I haven't had any issues except the dpad backlight stays on for a long time and incoming call issues. Then after a while will return to normal.
Should I take the hw3d out or set it to 1?
Click to expand...
Click to collapse
You can either take the hw3d statement out, or set it to one - they both should have the same effect.
There is no 'dpad' on the TP2. Do you mean the 4-button row at the bottom...? If those lights are on at boot, they will stay on in Android, so make sure they do not turn on at boot. Basically get the phone in portrait mode and wait until the button lights go dark.
Please try your data.img again. You can simply rename it, this is just a test - that file gets messed up and causes odd effects, this might be one of those instances.
arrrghhh;11295243
Please try your data.img again. You can simply rename it said:
Thanks for you help arrrghhh!
I renamed the data.img. Started it up, signed in to my google account to sync contacts. Waited for it to go to sleep, then called the phone. The LED went to amber, but didn't wake up and ring. I have the sleep_mode set to 1. I set the 3d setting to 1.
Click to expand...
Click to collapse
Related
Hi Experts,
I am using Sprint Touch Pro2 , model number RHOD400.
I installed the latest build of Froyo which of 2011 Mar 25.
I am running the android from subfolder of my SD card, it boot up and everyting works fine. Pretty fast.
The only serious problem is when the phone goes sleep, it become NO SERVICE.
Can not recieve call, and after awake, it was saying NO SERVICE and the phone service come back after couple
seconds.
I tried to change the pm.sleep_mode to 2,3 or 4, neither works.
here is my startup.txt :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=4
physkeyboard=rhod400 rel_path=androot/FRX06"
boot
===================
BTW, the last build I used was from last year, it doesn't have this issue, and this is the first time I meet this
issue before.
I am not sure if this is a known issue but I can't find any other thread talking about this.
Posted a few days ago in [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes
arrrghhh said:
This is a known issue - for users with RHOD400/500, if you use it as a GSM device, the SIM card will get shut off in sleep. WisTilt2 is tracing thru a huge commit, and trying to fix it. You can use kernel 1253 and the problem will not be present. But obviously you won't get any of the fixes that have happened in newer kernels - the biggest one probably being cam.
Click to expand...
Click to collapse
arrrghhh said:
2. For the losing signal every time the phone turns off, this is a kernel issue. See my previous posts, you need to run kernel 1253 or previous until the issue is fixed (there was a giant clocks commit, and the theory is on the RHOD400/500 in GSM mode, the SD card and SIM card get shut down when the panel is shut down. Obviously shutting down the SIM is unexpected behavior, and devs are working on it. There's already a bug filed on the tracker too, thanks!!!!
Click to expand...
Click to collapse
You've been thanked for saving me the time to explain again .
To the OP, follow those directions, and keep the sleep_mode=1.
i have some problem...
thankss arrrghh..
dewagprs said:
i have some problem...
thankss arrrghh..
Click to expand...
Click to collapse
problem solved , i use kernel 1253. But camera not working
dewagprs said:
problem solved , i use kernel 1253. But camera not working
Click to expand...
Click to collapse
Holy hell, did you not even bother to read what I said about the kernel!?!? Oy.
Try to re-reading my post.
Hi,
I recently updated to the XWKI8 stock firmware and now the screen fails to time out I have tried setting the time out to 15s/30s/1 min but the screen never switches off.
Is this a know issue? Is there any work around? I am getting fantastic battery time gains by upgrading from 2.3.3 but all is lost the moment the screen gets turned on due to an incoming message (when the phone is in my pocket) and then never gets turned off)
--Ashwin
kkashwin said:
Hi,
I recently updated to the XWKI8 stock firmware and now the screen fails to time out I have tried setting the time out to 15s/30s/1 min but the screen never switches off.
Is this a know issue? Is there any work around? I am getting fantastic battery time gains by upgrading from 2.3.3 but all is lost the moment the screen gets turned on due to an incoming message (when the phone is in my pocket) and then never gets turned off)
--Ashwin
Click to expand...
Click to collapse
1) Tried normal reboot since flash?
2) Updated via Kies? So maybe you try to reflash it but then you have to do it via Odin (Kies just see that it's the actually one)
Here the files and instruction: http://forum.xda-developers.com/showthread.php?t=1075278
CHEERS
kkashwin said:
Hi,
I recently updated to the XWKI8 stock firmware and now the screen fails to time out I have tried setting the time out to 15s/30s/1 min but the screen never switches off.
Is this a know issue? Is there any work around? I am getting fantastic battery time gains by upgrading from 2.3.3 but all is lost the moment the screen gets turned on due to an incoming message (when the phone is in my pocket) and then never gets turned off)
--Ashwin
Click to expand...
Click to collapse
Please try the following - if not already done:
1. Wipe cache partition in recovery mode (Volume UP + Home + Power).
2. If you have CWM then also clear Dalvik cache (for Java VM).
If that does not help either, you may have to make a hard reset (*2767*3855#).
As this will wipe internal SD card, be sure to have everything in a backup elsewhere.
EDIT:
Here is another guess to try before.
There are two different places where you can set the screen off time.
The one you found is (I am sure) in Menu => Settings => Display => Screen timeout.
The other one is in Menu => Locations and Security => Timeout.
Maybe there is an other value set on your phone.
Try to change this setting before wiping everything.
Good luck !
Resolved!
A combination of the above two suggestions resolved the problem. Tried setting and unsetting security options and rebooting. It seems to be working now.
Thanks guys!
I'm having problems with my phone, when the screen turns off, it turns on again and I don't know what's happening... I previously changed timeout to 30 min because I was downloading stuff then I change it back to 30 s but now I have this issue. What should I do?
rolo143 said:
I'm having problems with my phone, when the screen turns off, it turns on again and I don't know what's happening... I previously changed timeout to 30 min because I was downloading stuff then I change it back to 30 s but now I have this issue. What should I do?
Click to expand...
Click to collapse
did you overclock your cpu and what rom/kernel are you using?
Raider_ said:
did you overclock your cpu and what rom/kernel are you using?
Click to expand...
Click to collapse
I have cyanogenmod 7.2 installed on my phone. The kernel is the one for this rom, i installed at the same time i installed this rom.
i dont know too much about overclocking but on cyanogenmod settings i selected "smartass". The default mode is "interactive" but i already tried switching between these and it doesn't solve the problem. the max overclock i think is at 1024. That's it
But the screen sometimes flashed and it's a little bit scary at times let me tell you because it is sleep and all of a sudden it turns on the screen, its like is possesed or something. xD
Can someone please help me? I thought the problem was solved but this issue is getting me out of my nerves, after the timeout screen goes off, the screen turns on again by itself for about 3 times. I don't know what to do, but it's draining battery because of this. Please help.
rolo143 said:
Can someone please help me? I thought the problem was solved but this issue is getting me out of my nerves, after the timeout screen goes off, the screen turns on again by itself for about 3 times. I don't know what to do, but it's draining battery because of this. Please help.
Click to expand...
Click to collapse
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
evilbarcode said:
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
Click to expand...
Click to collapse
Where can I change the scheduler option? I already tried wiping the dalvik cache and changing the governor to "ondemand" reboot, but the problem is still there, when the phone goes to sleep, it turns the screen on again about 5 or 6 times then it turns off and after a while it repeats.
evilbarcode said:
Try to set the governor to ondemand and the scheduler to sio or noop set it on boot, then reboot to cwm, clear dalvik cache and reboot system. If that doesnt work. Backup, reflash rom and kernel, then advance restore data only.
Click to expand...
Click to collapse
Raider_ said:
did you overclock your cpu and what rom/kernel are you using?
Click to expand...
Click to collapse
What has scheduler or governor or OC to do with this?
Sent from my Xperia Arc S using xda premium
The thing is I can't solve this problem, do you think if i reflash firmware and kernel it would be ok? But I dont want to lose my apps or data, and if I make a backup before reflashing then i restore it, would the problem come back? Please, I need to put an end to this thing, is driving me crazy!
EDIT: I attached a txt file with my logs. Using "aLogcat" app, I found this:
Maybe it can help..?
Does someone knows what is this about?
W/asset ( 346): deep redirect failure from 0x01030046 => 0x02080019, defStyleAttr=0x01010084, defStyleRes=0x01030022, style=0x7f0d0008
if you see the logcat attached to my previous post, you see it repeats A LOT so I guess the problem is there but I don't know.... My screen is still turning on several times after going to sleep......I noticed a battery drain about 3% - 4% per hour so I don't think it's normal, when I go to sleep I have to have my phone on so the alarm sounds but for example I go sleep at 12:00 am and by the time i wake up 6:00 am in only 6 hours is about 15% or more drain..... I need to solve this problem
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.
New build up
big thx to @sbrissen for his help and many of the device fixes
not working:
Wifi must be turned on, (doesn't need to be connected just has to be on) otherwise you may experience reboots when screen turns off.
gps
cm cam?
Click to expand...
Click to collapse
working:
everything else
Click to expand...
Click to collapse
In any case, please provide logcat and/or last_kmsg if something isn't working as expected.
Disable sim pin lock before flashing! It's known to be broken on other devices and would cause your simcard to be locked permanently (you would need to order a new one).
Rom:
https://mega.co.nz/#!NI11nL6R!FXz41aYVPGXrvpFUoi1_F1d2ecU-3lIGXwTcUGLpqzA
Gapps for 5.0:
https://s.basketbuild.com/gapps
Gapps mirror:
https://mega.co.nz/#!5R0D1B4L!1zP2aiDzlBAQ05I4UkgTNaVVLQME9Yjj1Fl7nwAPzs0
On it. Rough and busy weekend orI'd probably have been done lol
Wow. You're fast ?
[Rom] [alpha] [Unofficial] CyanogenMod 12.0, malir3p2, Build1
Good timing lol. Sat down to repo sync to work on this myself and this popped up lol
Hung at note screen but it's spinning now. I'll let you know and try to pull log if no go
Ok so no adb, just waiting for device. There is no keyboard or it won't pop up. Wifi works but you can't enter password. No baseband but that is due to se DISABLED. On KK, at least for me it HAD to be either enforcing or permissive or I got not baseband. Looks new but long way to go. But booting and it didn't reboot on me. Here's the last kmsg after reboot to recovery
https://www.dropbox.com/s/iog9gq8vc5rovhz/last_kmsg?dl=0
Booted up, going through the setup now.
edit: GPS and WiFi working.
good. for me works too. and no baseband
Running a test build of my kernel with config hack for se permissive with cm12 initramfs just to see what happens. I'll let you know once the build finishes
Boots but black screen with keys that will light. I forgot we had to remove SE from the device, should have known this would do this. Either way, nice job. It's close and like I said I'm almost positive baseband is from se disabled
Boots, but no keyboard to input anything. Tried to install Kii keyboard, but still won't work.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
rob_z11 said:
Boots, but no keyboard to input anything. Tried to install Kii keyboard, but still won't work.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
You need to go into input settings, change keyboard, and enable the "Hardware - Show input method" slider.
Thanks. No baseband mean no network right?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
rob_z11 said:
Thanks. No baseband mean no network right?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Right.
jeeze DT, you're rocking!
I cannot wait to see this on, hopefully, all the note 2 variants, including CDMA!
Booted up no baseband, also power button triggers reboot. Video playback doesn't work...only sound plays
nelly_85 said:
Booted up no baseband, also power button triggers reboot. Video playback doesn't work...only sound plays
Click to expand...
Click to collapse
Work in progress... Lucky to get this far..
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Damn, you're fast man! Can't wait to try this out, but until the baseband works I'm just going to watch with giddy anticipation. Wonder if including a newer modem would help?
nelly_85 said:
Booted up no baseband, also power button triggers reboot. Video playback doesn't work...only sound plays
Click to expand...
Click to collapse
Can you get me a logcat of the crash (trigger the power button while logging) please.
Also please make another logcat while trying to play a video.
JosephT said:
You need to go into input settings, change keyboard, and enable the "Hardware - Show input method" slider.
Click to expand...
Click to collapse
I am glad you finally can post here. [emoji1]
Boot on
Not data baseband Unknown
adb logcat Do I need to extract?
windows8k said:
Boot on
Not data baseband Unknown
adb logcat Do I need to extract?
Click to expand...
Click to collapse
Baseband probably can be fixed next build. Mobile data still would be broken.
More important is the power button crash. I really need a logcat of it.
When I watch a video on YouTube, the video is just black, an logcat spammed with this:
Code:
E/ (13086): egl_android_pixel_format* _egl_android_get_native_buffer_format(android_native_buffer_t*) unsupported native buffer format (0x13)
E/GLConsumer(13086): error creating EGLImage: 0x3003
E/GLConsumer(13086): Failed to create image. size=640x360 st=640 usage=0x2100 fmt=19
W/GLConsumer(13086): [unnamed-13086-0] updateAndRelease: unable to createImage on display=0x1 slot=4
E/ (13086): egl_android_pixel_format* _egl_android_get_native_buffer_format(android_native_buffer_t*) unsupported native buffer format (0x13)
E/GLConsumer(13086): error creating EGLImage: 0x3003
E/GLConsumer(13086): Failed to create image. size=640x360 st=640 usage=0x2100 fmt=19
W/GLConsumer(13086): [unnamed-13086-0] updateAndRelease: unable to createImage on display=0x1 slot=0
E/ (13086): egl_android_pixel_format* _egl_android_get_native_buffer_format(android_native_buffer_t*) unsupported native buffer format (0x13)
E/GLConsumer(13086): error creating EGLImage: 0x3003
E/GLConsumer(13086): Failed to create image. size=640x360 st=640 usage=0x2100 fmt=19
W/GLConsumer(13086): [unnamed-13086-0] updateAndRelease: unable to createImage on display=0x1 slot=6
It didn't crash though, no power button crash either.