Related
Hi everyone,
I've just bought a Nexus S in france, and the european version is the i9023 one; with a S-LCD screen (among very little other things that I'm not aware of). It seems that the BLN mod kernel is not available for the i9023, so I'm here to ask xda devs if they could port the BLN modification to the i9023 kernel...
that would be really nice, and I'm ok to pay a few bucks via paypal to the person that would make it ;-)
I hope my request will be heard...
Thanks !
yep you are right, the i9023 isn't supported (yet ) but morfic and nedlar are working on this issue
I am also waiting
if SuperAOSP ROM works for you then it is build in
even for a i9023 kernel ?
Well, i could git it a try then...
the i9023 has other driver, so i don't think that it will work
For now, only the i9020 is supported...
eiabea said:
I am also waiting
Click to expand...
Click to collapse
Me too! Any word from the developers?
Need BLN tooo
any hope for i9023 user??
Some news for i9023?
would be awesome to get BLN working. I bought BLN Control Pro to support Neldar and the development. Maybe it helps.
I have been having a poke around my i9023 Nexus S today. The bad news is it seems that there is no Cypress touchkey chip, which is where the guts of the i9020 BLN kernel mod is done. Instead the keys are handled as an extension of the main touchscreen. I guess this is the main difference between the i9020 and the i9023. Maybe it is due to the SC-LCD rather than AMOLED?
From observation however I would say the button backlight is definitely still interdependently controllable, so I think a BLN for i9023 could still well be possible even without the Cypress chip.
Well! Pays to read the git commit log.
arch/arm/mach-s5pv210/herring-touchkey-led.c is where it's at for i9023 devices. Seems ALL FOUR button backlights are independently controllable, merely by toggling some GPIO lines.
I'll have a further hack at this tomorrow but it looks quite promising.
OK, I have a working (if a little hacky) patch for BLN support on i9023 Nexus S devices.
Unfortunately for some bizarre reason the android market won't let me buy the "Pro" BLN app so I have not tested blinking, but as the interface is basically identical I presume it will work.
https://github.com/neldar/kernel-2.6.35-nexusS-bln/pull/1
Hopefully the original devs can take it up and get it into Netarchy's kernel or something.
Wow, good job. Is there a way to test it? If yes, how?
Nedlar managed to mend to BNL on the I9023 ?
It'll be possible or not ?
Because a lot of people are some dreams ^^ !
But the hardware's Nexus I9023 isn't like the hardware's I9020, so... a big difficulty !
Yes, possible and working now for me.
I will try get a build into an update.zip if people are keen to try it.
Well I'd like to try, so if you can make an update.zip, so that'd be nice.
thanks
OK, here is a update.zip build for testing thanks to Koush's AnyKernel. You need to flash this from recovery.
dl.dropbox.com/u/197956/sdf3df-bln-signed.zip
MD5SUM
e4ce23ba4366e0a77df4adbb45b6387e sdf3df-bln-signed.zip
Built from github.com/akent/linux_samsung/tree/1a1db08b19ffb7a196ab993cf00e8c55ac0859c7
It is the latest unmodified upstream Samsung kernel plus the BLN mod for both i9023 and original Nexus S devices (although I have only tested i9023).
Also includes and installs the modified liblights binary you need to make the BLN app work.
The blinking feature may or may not work, as I said, I haven't been able to test it. I cannot really see how the mechanism is supposed to work, perhaps there is some magic in the BLN Pro app. Without blinking, the biggest problem is that it can be difficult to see the backlight notifications in bright light conditions.
Please do a nandroid backup before installing, I take no responsibility if you lose data and you don't have a backup.
I've tested this on the CM7 nightly and ClockworkModRecovery v3.0.2.5, your mileage may vary.
Happy to hear how it goes for people.
(Sorry for the non-hyperlinked links, the XDA forum software won't let me post links yet.)
thanks mate!! am very happy to see progress of this issue!!
hopefully the other kernels catches wind of this!!
As I was working on trying to port CM6/CM7, I realized that it is much more time effective for me to port the tweaks involved with CM6/7, rather than trying to actually port the whole thing. So with that in mind, what tweaks/aspects of CM6/7 do people like/would like to see on our phone?
Bear in mind that because CM7 is GingerBread, so although I will try my best, I can't promise that features from CM7 are portable. CM6 features should be portable, but I *promise* nothing, and will try my best otherwise.
Currently working on
An extra menu in settings to control all this crap
REQUESTS
:LED Settings that are actually helpful/useful (pending)
:Camera on Low Bat (pending)
:Customizable Power Notification (pending)
Requests that probably aren't going to happen
CM7 (until a GB source release from Samsung for our phone or a very generous donation that gives me a reason to spend a month porting a kernel)
CM7 Theme Support (built on the GB API, all themes are Gingerbread minimum API anyways).
Click to expand...
Click to collapse
i think the lockscreen gestures would be awesome
theme support would be cool ( dont know if thats possible)
led settings would be nice
I mentioned this to you before, but I thought i'd post here and see if anyone else responds: how about an optional flashable tweak, if possible, for those who want to be able to use their camera on low battery and don't want their screen dimmed and keyboard blacked out. (I know you can brighten the screen on low batt., but you have to do it every time after waking the phone from sleep). I believe on CM7 the phone simply functions normally until the battery dies.
I'll definitely look at the battery tweaks as that should be fairly easy to find, as for the theme manager, the issue is that its built from the GB API, as are all the themes. So even if the theme manager were ported, none of the themes would install as they would require a higher OS version
Customizable notification power control bar. What we have is decent enough. But I always liked that about CM series, being able to customize.
Touchwiz power control is good enough so no need to put this as a high-demand feature.
Are you still working on porting CM? I'd rather wait for CM than just flash tweaks every now and then.
I agree instead of porting u should at least try port cm6 which is froyo that would be awesome till we get a gingerbread kernel leak which krylon is looking into
Sent From My Rooted Sidekick 4g XDA Premium App
Porting CM6 will take me at least another month. That's what I was working on the past 2 weeks, but its all the same problem. CM6 and CM7 both require a ported kernel (2.6.35), which is very tedious and frustrating given the parts that were added to our phone.
Yea I saw that when I was looking into it I'm trying to get in contact with a samsung team on xda see if the help us out to get this ported
Sent From My Rooted Sidekick 4g XDA Premium App
What I'm saying with this thread is, we can essentially build CM6 on our phones, without the official title and all the extra work in porting a kernel, if we just build the parts in that make CM6 different from stock.
So that's my goal, to add enough parts to this that it will be similar to CM6 in functionality.
That's a great idea I just don't know what we can use lol
Sent From My Rooted Sidekick 4g XDA Premium App
The way I see it, although I love CM and would love to see it on this phone just as much as the next guy, I don't see a whole ton of stuff that's in CM that's not in our stuff already. So if I can focus on the things that people actually use from CM, I can build things that people want in CM, rather than trying to build CM.
sduvick said:
The way I see it, although I love CM and would love to see it on this phone just as much as the next guy, I don't see a whole ton of stuff that's in CM that's not in our stuff already. So if I can focus on the things that people actually use from CM, I can build things that people want in CM, rather than trying to build CM.
Click to expand...
Click to collapse
Makes sense, considering you're the only one working on it, that I've heard. If it takes time to port a whole thing over, why not cut time down and just port that parts you love about CM.
Honestly, with the work you and ayoteddy have been doing for our phones, Cyanogen isn't a big deal to me. I mean, this may be off-topic, but the only things I do want are to completely eliminate that keyboard lag and to keep the keyboard backlight lit whenever open. Other than that, you guys have tweaked and optimized the phone so much already.
I haven't seen any keyboard lag, where do you see this? I'll look at the keyboard backlight thing shortly, currently working on an extra menu in settings to control all the tweaks I'm adding.
I'll also add a requests list to the OP shortly. EDIT: added.
When typing quickly some inputs may skip. I read the Samsung Epic had the same problem. That phone had a fix for the keyboard lag.
badboi_zero said:
When typing quickly some inputs may skip. I read the Samsung Epic had the same problem. That phone had a fix for the keyboard lag.
Click to expand...
Click to collapse
Ahhh! So it happens to others too. i thought i just was messing up..i was like..i never messed up before. yess, this happens to me too and it sucks. makes uo type ike tis. (missing letters, but not that frequent)
Yeah. Just like that. It's worse when you're typing on an app that uses more resources, like typing on a web browser on an html page. Or when the facebook app is refreshing the feed while you type a status.
I contacted the developer who made the keyboard patch for the Epic(he really fixed the problem up good on that device!). he made a similar patch for us, for the Sidekick, I've just been too half-assed about learning how to apply the patch to our kernel, lol.
you guys can read what he wrote and find the patch he made us here, at the end of the thread:
http://forum.xda-developers.com/showthread.php?t=975611
apparently, our phone shouldn't suffer nearly as bad as the Epic, but he still made us a patch to make our keypad timer delay configurable by the user!
Edit: for some reason, the letter that skips the most on my phone is the "y", haha.
I don't know much about CM, but I'd really love the option to use landscape software keyboards. I am astonished that DSamsung actually chose to BLOCK THE FEATURE, een if we PAY to download a non stock keyboard.
The keyboard fix for the epic won't work for the Sidekick, because the change that was made to fix the epic issue was already there from Samsung
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.
I have stock Froyo ROM.
With stock kernel, the light sensor works fine. I can use the built-in auto-brightness (settings/display/brightness / auto), and I can use my own Tasker auto-brightness routine, and I can see the tasker variable %LIGHT change with ambient light level (albeit in discrete steps).
I installed 3 different custom Kernel’s:
Defuse 1.4
Infusion 1.8
Infusion 2.0
With each of these, light sensor doesn’t seem to work. Built-in auto-brightnes doesn’t work. My tasker auto-brightness doesn’t work. Tasker %LIGHT value reads 100 lumens no matter whether you are in a dark closet or bright sunlight.
Just to make sure it wasn’t my phone, I disabled voodoo lagfix and went back to stock kernel again (from a backup I had made). Light sensor works fine once again. It’s definitely something about those kernels.
.
Question 1 - Does anyone else remember seeing this?
(I’m kind of surprised that searching didn’t show this in the general, q&a or developer forums....how could I be the only one to notice????).
Question 2 - By any chance, are any patch or fixes known?
(I doubt it, but just figure I’d ask)
By the way, this is by no means a complaint. I am very happy with the performance of those kernels and plan on keeping them as long as I’m in stock Froyo (which might be quite awhile). I can see the improvement in response time in menus, in swiping home screens (and in Quadrant fwiw). I tested all the other features I can think of and everything else works flawlessly (except possibly some extra flashing from BNL feature on Infusion 2.0, already well discussed in developer’s thread). I am very, VERY grateful to the developers that gave us these kernels last year and continue to work on great new things to share with us.
Probably just some wrong code that needs fixed... and it wont be fixed either, all have moved on bigtime lol. It would also seem useless to go back and change it...
Sent from my SGH-I997 using xda app-developers app
Ryanscool said:
Probably just some wrong code that needs fixed... and it wont be fixed either, all have moved on bigtime lol. It would also seem useless to go back and change it...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It certainly wouldn't be useless to me. I got 5 Infuse phones for my five immediate family members, and I am sort of the go-to guy within the family for questions. For one thing I might do better helping them if I stick with Froyo (although I haven't quite made up my mind on that... might try for some stable GB either stock or AEON on my phone only) . For another thing, they are not interested in changing things they have figured out, so if I can give them custom kernel with their Froyo, it would make their phones faster wthout forcing them onto a new OS.
But since I don't have any ability to develop a fix myself and as you mentioned, those who do have long since moved on to bigger/better and newer things. So useless or not is probably an irrelevant point... it ain't gonna happen.
It's also weird that the same problem happened on all those different kernels from different developers. Makes me wonder if somehow I'm missing something and doing something wrong on my end, although I don't know what that could be. Oh well.
Thanks for responding.
I recently acquired an sgs4g and previously owned a Vibrant. I understand that the sgs4g is specifc on roms, but can't seem to find one that is 100% working. Can someone explain to me what the common issues are and the history/likelyhood of them being fixed?
I understand the following may or not may not work:
GPS (used to this being wonky, assume there are workarounds and it can be made to work)
Notification Lights (just got mine back with Paranoid, really would miss them)
Video Recorder (I am ok with this as a causality, I never use it)
HotSpot (I love this when traveling, it's part of the core functionality of the phone for me. I could get by with a straight tether though).
I ran Paranoid Android on my Vibrant and loved it. It was the reason I chose to stick with my Galaxy and not upgrade to the newest model.
Thanks
JB is still in alpha stages, especially if you care about stability and location services.
ICS is mostly working. You will probably need to patch your build.prop for GPS unless you decide to use Ultragen.
GB is fully working.
GPS - Problematic as listed above. Not working on JB, works on ICS with build.prop line added, works on GB.
Notification Lights - Phone doesn't have a notification LED. Sorry.
Video Recorder - Not working on JB, works on ICS/GB.
HotSpot - Not working on JB, works on ICS/GB. May work on JB with third party apps like Barnacle.
The JB bugs above are likely to get fixed if we don't annoy the developers too much and provide useful logs when requested. Other bugs may or may not get fixed depending on how annoying the people requesting them happen to be and whether or not the developers want it themselves.
If your goal is just 100% stability, go with Barebones GB. It's a very nice debloated stock and about as stable as you can get.
Theraze said:
JB is still in alpha stages, especially if you care about stability and location services.
ICS is mostly working. You will probably need to patch your build.prop for GPS unless you decide to use Ultragen.
GB is fully working.
GPS - Problematic as listed above. Not working on JB, works on ICS with build.prop line added, works on GB.
Notification Lights - Phone doesn't have a notification LED. Sorry.
Video Recorder - Not working on JB, works on ICS/GB.
HotSpot - Not working on JB, works on ICS/GB. May work on JB with third party apps like Barnacle.
The JB bugs above are likely to get fixed if we don't annoy the developers too much and provide useful logs when requested. Other bugs may or may not get fixed depending on how annoying the people requesting them happen to be and whether or not the developers want it themselves.
If your goal is just 100% stability, go with Barebones GB. It's a very nice debloated stock and about as stable as you can get.
Click to expand...
Click to collapse
I am currently just updating the phone with Kies to GB. I may try the debloated Gb first and maybe ICS after. I ran ICS on my Vibrant, it was great. I have a feeling a lot of the things I liked were aesthetic choices and could be duplicated on GB. (Ex: Home screen, newest gmail widget) provided they are supported in GB.
" Notification Lights - Phone doesn't have a notification LED. Sorry."
Er, I meant the keys at the bottom, they light up on missed calls etc.
Thank you for the input, that's exactly what I needed. Any suggestions on GB and ICS roms (names)? I know it's kind of up to the user ultimately and expect opinions to vary.
Thanks
Ah! What you need then is the BLN Control app for BackLight Notifications from the Play Store. And either ICS or GB and a kernel that supports it... most do, just avoid the Proton ICS kernel, as Beastmode doesn't like BLN. Proton may eventually get it, but if that's something on your "want. want. want." list, may as go with a kernel that supports it now.
Alternatively, the NoLED app will give you an on-screen notification that's configurable and works without any kernel modification needed.
GB Roms to try: Barebones. Valhalla. Valhalla Black.
Barebones is very similar to stock. Minimal skinning, everything just works, and it's a slim/sleek ROM as well. The one I generally suggest for people starting out.
Valhalla is the beautifully tweaked ROM that many GB people still love as their daily driver. It's farther off of stock, but does work very well.
Valhalla Black is a further-tweaked Valhalla. Some parts may be more difficult to see, but in general if you like the look, it's great.
For ICS: AOKP, Slim, HebMIUI, Fah-Q CM9.
AOKP is my general fav ICS ROM. It's highly configurable, and I love the laziness of weather on my security screen without needing an additional lock screen.
SlimICS is a slightly-more configurable CyanogenMod that takes less space. What's not to love?
HebMIUI is great if you're a fan of MIUI ROMs. Since it's MIUI, not CM based, you'll need to do a full wipe between installing it and any of the other 3 I suggested, but it's one of the most updated ROMs for our phone.
Fah-Q CM9 is good if you're a fan of straight CyanogenMod, put out by this month's current active development team. The caveat here is that since it uses the Protean kernel (and HebMIUI might as well), there's no BLN control.
Personally, my daily driver with GB wandered between Barebones and Valhalla Black. For ICS, it always came back to AOKP. Right now, I've been running PACman JB for the last week or so as it implements portions of Paranoid Android/AOKP/CyanogenMod, but the lack of GPS in JB continually brings the ICS AOKP siren song back to my ears.We'll see where I fall back, but...
I do hate bln but the reason I disabled bln was because when I fixed the lights issues for the capacitive keys I eliminated any bln crap lol I might work on putting it back this week but not sure for now it doesn't work but then again the kernel fixes deep sleep and battery life so...
Sent from my Galaxy Nexus using xda premium
I recommed you to Heimdall one click and then put Barebone ROM. It will already give you a debloated rooted stock.
Leave Kies aside, waste of time.
So I finally rooted this phone, and I have ODIN and I also have this HEIMDALL along with an abundant amount of other files Ive been suggested to download yet I cant seem to change the rom still. I am on 2.2.1 any ideas suggestions or guidance would be helpful.
Odin and heimdall drivers may clash. I would uninstall all drivers (&kies) and stick with the heimdall if you're already having issues. Link in post above yours is good place to start.
Pc or Mac?
Find lumin30 or bhuvden one click guides. Follow and you shouldn't have any trouble.
Thanks for all the advice. It's exactly what I was looking for.
I am going to go with AOKP for now. I have been using GB with the heimdall kernel and it's the little things I miss, (like the ICS dialer, lock screen and status bar). I have tried to use alternatives like hololock etc and it just doesn't feel the same.
Cheers! Thanks for being a great community.
Ultragen is my fav ICS rom
Sent from my SGH-T959V using xda app-developers app
atlantiatech said:
Thanks for all the advice. It's exactly what I was looking for.
I am going to go with AOKP for now. I have been using GB with the heimdall kernel and it's the little things I miss, (like the ICS dialer, lock screen and status bar). I have tried to use alternatives like hololock etc and it just doesn't feel the same.
Cheers! Thanks for being a great community.
Click to expand...
Click to collapse
I have been running AOKP on both my SGS4G as well as my wife's for 3 weeks now, and my phone is the most stable it has ever been. Very snappy and not a single crash. I did, as the poster references above, tweak my GPS file in my build.prop (it has been working great, much better than stock) and I would also recommend updating the modem on your phone to the LB6 padded modem. If you want an easy way to tweak your GPS, as well as install the AMR-WB codec for HD Voice, install Pimp my Rom from the Play Store. My wife likes it, and she is the first to complain about a slow phone or constant reboots. Was like getting a brand new phone. Team Acid did a bang up job. Great work.