Not sure if it is a bug, I tried left -> right, then right -> left without lifting my fingers off throughout, then when you try to unlock using left -> right, nothing happens, does it happen to any of you?
Sorry if this concern has been covered in show-p's previous releases, but I've come from an SGS2 without sweep2wake so have no previous knowledge of this feature.
I was wondering whether it has a material impact on battery life through wakelocks or such (sort of like how BLN on SGS2 did), as it would mean the capacitive buttons are constantly 'on.'
Can anyone who's used a kernel with sweep2wake shed some light on this?
Not sure if it is a bug, I tried left -> right, then right -> left without lifting my fingers off throughout, then when you try to unlock using left -> right, nothing happens, does it happen to any of you?
would like to report a 100% reproduce-able reboot....in lockscreen, if I just pressed Home button few times, the phone will HANG and reboot right away.
I'm on Venusaur Rom 3.0.0 with the "long press Home button" mapped to recent task.
I don't mean to sound rude. But you REALLY don't need to post this everywhere! The devs are aware it's a feature people want, but the reality is that getting things STABLE first is the highest priority.
It's not point getting call recording added if the phone doesn't work properly. Please just be patient and stop spamming every thread with your requests.
M.
--- drivers/media/video/tegra/tegra_dtv.c~ 2012-05-09 15:33:11.131000116 +0300
+++ drivers/media/video/tegra/tegra_dtv.c 2012-05-09 18:18:10.212000301 +0300
@@ -737,7 +737,7 @@
debugfs_remove(dtv_ctx->d);
}
#else
-static int dtv_debugfs_init(struct tegra_dtv_context *dtv_ctx) { return 0 }
+static int dtv_debugfs_init(struct tegra_dtv_context *dtv_ctx) { return 0; }
static void dtv_debugfs_exit(struct tegra_dtv_context *dtv_ctx) {};
#endif
--- drivers/usb/gadget/u_serial.c~ 2012-05-09 15:33:12.366000116 +0300
+++ drivers/usb/gadget/u_serial.c 2012-05-09 18:22:35.281999968 +0300
@@ -1331,7 +1331,7 @@
debugfs_create_file("reset", 0222, dent, ui_dev, &debug_rst_ops);
}
#else
-static void usb_debugfs_init(struct gs_port *ui_dev) {}
+static void usb_debugfs_init(struct gs_port *ui_dev, int port_num) {}
#endif
/**
Does this kernel work with cyanogen Rom?
Sent from my HTC One X using XDA
So far I have been unable to get the 204, 102 and 51 MHz frequencies. Lots of reboots and testing. No problem with deep sleep.
Is it set this way intentionally, or is this a bug?
Does show still have a hox???
Sent from my Nexus 4 using Tapatalk 2
This Kernel is NOT STABLE !
Many Users from Leedroid / JDr0id / Revolution HD ROM's reporting :
1. Unresponsive Power Button
2. Deep Sleep Issues
3. S2W Not Responding Intermittently
4. Battery Drain During Charge
5. Inability to End call
If you have any one of these Issues revert back to stock Kernel or another Kernel, several users recommend :
Francos Kernel R2 - http://xdaforums.com/showthread.php?t=1646883
Eternal Kernel - http://xdaforums.com/showthread.php?t=1640532
Remember to "FASTBOOT ERASE CACHE" from CMD window after flashing new Kernel !
You may Also NOT have any of these issues, for a more stable phone consider another Kernel untill the issues have been solved.
*** Recover from Non-booting Phone ***
This is where your phone has discharged during charging and wont power on when not connect to USB / Wall Charger.
1. Remove Phone from USB / Wall Charger for 1min
2. Insert USB / Wall Charger wait until the Red LED begins to Blink Let it blink for about 1m.
3. Power on normally ( If this fails follow steps 1 & 2 again )
4. Allow the phone to charge to at least 30% ( Then Make a Back Up OPTIONAL )
5. Boot into Fastboot and flash another kernel or if you wish to re-flash Bricked ( NOT RECOMMENDED )
6. FASTBOOT ERASE CACHE
7. Boot up as normal