Greetings,
As the title states, I would greatly appreciate it if one of the more technologically adept folk here would make a mod for a Nexus S running on 4.1.1 so as to wake the phone from sleep using the volume rocker.
This thread has it ready for the GNex and
This thread seems to have accomplished it for the HTC One X and i was hoping someone could build the same for the Nexus S.
My power button is dead so I need an alternative and while there are apps that try and achieve similar results, they dont work nearly as well as this. If you recall this is a popular option in Custom ROMs. I would do so myself, but I lack the technical know-how.
Thanks a lot, appreciate any help.
It probably won't come until we have actual JB source for the NS. It doesn't seem like it would be worth it to implement it on the "hacky" (nothing against the devs they work magic with what they have) JB roms out now only to have to redo it when source comes out.
Related
ok here goes can anyone point me in the direction of an ruu that works after upgrading to the new gingerbread on desire?
ok i'll explain a bit more. Iv'e updated to the newest version of gingerbread on my desire, its the official dev one from htc, my problem is my power button is broke so the rom is virtually useless to me, ive tried volume wake apps but they just dont work consistently, so my only option is to revert back using an ruu, the problem is, there doesnt seem to be one that works . anyone with any answer, even if its just to say there is'nt a way of sorting this, will be greatly appreciated
....................................
you would probably be better off posting in the Desire forums.
One of the things that turned me off and kept me on cm7 was the lack of of capacitive button notification lighting in ICS. Is there a way that this has been resolved on stock without using another CM rom? I am really hesitant to go back to an alpha build because it took me so long to get full functionality from the rom and the phone and work exactly how I wanted it.
Thanks.
Alpha lol!! Flash a kernel with bln....
Sent from my Nexus S using xda app-developers app
CM7 isn't ICS, that's CM9. Also it hasn't been an alpha for at least 2 months, it's in RC1 which is as stable as you're going to get.
Use Airkernel or Martrix Kernel to enable BLN.(You can use NSTOOLS to adjust the settings).
Reread what I wrote. One of the things that turned me off of ICS and kept me on CM7 (I know it's GB) is the lack of notification lit capacitive buttons. I basically want to upgrade to ICS or later (really JB once there is a more functional release) but those lit capacitive buttons are crucial for me as I have the att nexus s that has lcd screen and not the more effecient led screen. So a lot of those led notification apps dont help me. A couple of responses here are helpful. I'm hoping there will be a kernel with bln for stock ota jellybean when that comes out. Will that be easy to attain?
It shouldn't be hard to implement BLN for jb. There are numerous kernels with back light notifications for 4.0.4. Have you even checked the development section?
Sent by pocket technology.
chronophase1 said:
It shouldn't be hard to implement BLN for jb. There are numerous kernels with back light notifications for 4.0.4. Have you even checked the development section?
Sent by pocket technology.
Click to expand...
Click to collapse
I didn't know they were called back light notifications until this post (I had kept searching "capacitive button notification light nexus s" the whole time) , so please bare with me as I'm learning. I appreciate your pointing me in the right direction. It gives me hope that when a very functional release of JB for nexus s is out I will be able to use BLN on it.
Its cool. I didn't mean to come across so harshly. My apologies. Yeah. There's a ton of kernels that support it. Just take your pick
Sent by pocket technology.
Hello everyone,
I just got my TF300T last night and it is a great tablet. Before I do anything (upgrade to Jellybean, etc) I am wondering why it seems there isn't much development for the tablet. I have had a couple android tablets and phones, and have rooted all of them for custom ROMs and such, but it almost seems like that's not really done a whole lot here. I just read one thread where the stock ROM was preferred by a good deal over any other ROM. Is there any reason for this? Any particular reasons I should still root, other than installing custom ROMs and kernels?
Thanks for your input.
dman918 said:
Hello everyone,
I just got my TF300T last night and it is a great tablet. Before I do anything (upgrade to Jellybean, etc) I am wondering why it seems there isn't much development for the tablet. I have had a couple android tablets and phones, and have rooted all of them for custom ROMs and such, but it almost seems like that's not really done a whole lot here. I just read one thread where the stock ROM was preferred by a good deal over any other ROM. Is there any reason for this? Any particular reasons I should still root, other than installing custom ROMs and kernels?
Thanks for your input.
Click to expand...
Click to collapse
Rooting is not required to install a rom, most non stock roms are rooted when you install ( they require you to unlock and void warranty ). If you wish to stay stock and don't see a need for root then don't do it.
If I could begin again I would stay on ICS for a time longer. I think good things for this unit are around the next corner.
Devs are working hard to make this happen. The JB bootloader has caused problems with most roms we are accustomed to. Once on JB you can't go back to ICS ( at this time ).
Good Luck!
Thank you for the response. How would I load TWRP onto the tablet then? I know people are suggesting not to unlock the tablet's bootloader unless I have to, so I'd prefer not to.
I figure if I go to JB, I'd load something like CleanROM as people seem to be quite happy with it.
Any additional information is greatly appreciated.
You need to unlock your tablet if u want to install a Rom and recovery
Oh ok. Gotcha. So then I think I know which guide I have to use. Thank you for your help and clarification.
OK, unlocked and such. Loaded CleanROM. Running well so far, but now I have to research ROMs to see which reigns supreme.
Cleanrom is the best for with unt's kernel
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
dman918 said:
OK, unlocked and such. Loaded CleanROM. Running well so far, but now I have to research ROMs to see which reigns supreme.
Click to expand...
Click to collapse
Since you are now on the JB bootloader here is a thread to watch as there will be a new rom coming, don't hold your breath. The reason for the breath statement is this is a big undertaking. It will allow numerous other roms you don't now see in the dev section. Everything now available on JB is based on the stock kernel, this should overcome that limitation.
AOSP, AOKP, Paranoid Android, and so on
http://forum.xda-developers.com/showthread.php?t=1942369
:good:
stock optimized for combination with keyboard dock
dman918 said:
Hello everyone,
I just got my TF300T last night and it is a great tablet. Before I do anything (upgrade to Jellybean, etc) I am wondering why it seems there isn't much development for the tablet. I have had a couple android tablets and phones, and have rooted all of them for custom ROMs and such, but it almost seems like that's not really done a whole lot here. I just read one thread where the stock ROM was preferred by a good deal over any other ROM. Is there any reason for this? Any particular reasons I should still root, other than installing custom ROMs and kernels?
Thanks for your input.
Click to expand...
Click to collapse
For me personally, I prefer using a stock-based ROM over the AOSP based ROM for day to day use. The reason is really simple, and that is the keyboard dock works much better on the stock based ROM. In CM10, for example, the lock/unlock button on the keyboard doesn't work. Also, closing the tablet and the keyboard does not result in the screen turning off automatically (you have to manually press the power button whenever you want to close the tab-dock). If you forget to do this, the battery takes a hit. As well, the mouse cursor in AOSP ROM is not exactly a "cursor", more like a giant circle (it's the default touch indicator in android). I use the keyboard dock a lot for drafting my college assignments, so stock-based Roms are perfect for me.
sosroz said:
For me personally, I prefer using a stock-based ROM over the AOSP based ROM for day to day use. The reason is really simple, and that is the keyboard dock works much better on the stock based ROM. In CM10, for example, the lock/unlock button on the keyboard doesn't work. Also, closing the tablet and the keyboard does not result in the screen turning off automatically (you have to manually press the power button whenever you want to close the tab-dock). If you forget to do this, the battery takes a hit. As well, the mouse cursor in AOSP ROM is not exactly a "cursor", more like a giant circle (it's the default touch indicator in android). I use the keyboard dock a lot for drafting my college assignments, so stock-based Roms are perfect for me.
Click to expand...
Click to collapse
I've noticed the same thing with the closing the tab-dock issue. When I turn off my screen and close it, the screen turns back on right before the tab touches the dock to close, so I have to turn it off again right before closing it to prevent random stuff from opening up/battery draining.
Other than that, I've had great fun playing with the various ROMs. I ran CM9 for the longest time but I switched recently to the Blackbean ROM. Its based on CM9 so it has all the features I like, but its all black/inverted so its better for battery and a lot easier to read in bed at night.
CleanROM is good, so is HydroROM, but I've found that I really enjoy the speed and efficiency of some of these other custom ROMS.
Hello,
I hope this is in the right area, xda / android newb (switched from iPhone within the past three months WOOHOO :good but here goes...
I have the HTC One X (at&t) and I'm running CM10 nightly 20121216 with rohan kernel b6. Every once in a while I when I unlock my phone the touchscreen is completely unresponsive, meaning the lock slider does not work whatsoever nor does the notification center pulldown. I did my best to research this issue and I'm not sure how to replicate it or if its even relevant to CM10. As in is it just my phone, or is it rom / kernel combo that causes this? The only way to resolve this issue is to power down the phone using vol down + power as the power menu is unresponsive as well. If anyone has any insight and would like to provide a solution OR if this is a completely new bug I would be happy to provide more information.
Oh, and a big shout out to Richard V. for figuring out LED for notifications :laugh::good:
I'm pretty sure this is probably a bug with Sweep2Wake, enabled by rohan's kernel that you have installed. Try reflashing CM10 without any custom kernel and then see if you have the problem.
Under volting has cause that for me several times on cm. Its the death sleep. I stopped using kernel mods altogether because of stability about a month ago. So not sure if that's what is still happening for you. But perhaps give it a shot
Sent from my One X using xda premium
Thanks guys I'll be sure to try that out. I somewhat had a feeling it might have something to do with the kernel.
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app
Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk
The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk
lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:
Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.
just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.