Related
Anybody have this working on their phone yet?
tested on my i9020a and doesnt work either for me anyone?
Seems to work fine on mine.
slobba said:
Seems to work fine on mine.
Click to expand...
Click to collapse
thats odd i tested it using the free version and the BLN test didnt even work. Tried calling a few times and missing the call as well as texting my phone and leaving the message unread and still nothing. Wonder if this is the case with only the rogers/fido/telus/bell i9020as as some of us had to root via the i9023 CWM recovery.
Yeh, I got caught with the problems of flashing the i9020 CWM instead of the i9023 version but the BLN is working for me both with the free non-blinking test and pro blinking test.
The NSCollab ROM I'm using includes the latest Netarchy 1.3.0.3 CFS kernel. Maybe that's the reason it's working for me??
really thats interesting, the kernel i tested one was the 1.3.0.3 netarchy kernel i guess i'll have to test it using the paid version and see wat happens
edit: tested using the paid version and it seems like its the i9023 root method thats screwing things up a little.
imisky said:
really thats interesting, the kernel i tested one was the 1.3.0.3 netarchy kernel i guess i'll have to test it using the paid version and see wat happens
edit: tested using the paid version and it seems like its the i9023 root method thats screwing things up a little.
Click to expand...
Click to collapse
That's what I was kinda wondering about the i9023 recovery, I guess that is what is doing it. I have the paid version of BLN as well, and it didn't make any difference.
did a bit more testing and it seems that BLN does work, but only for SMS and not for missed called even with the LED notification on for missed called.
Took mine back to 2.3.3 stock, installed Netarchy latest 1.3.0.3 kernel and now I'm getting the same behaviour: BLN test doesn't work, LED notification on missed calls not working but LED notification on new email is working.
Might try flashing the NSCollab ROM again to see what happens.
Tried running fix permissions on the stock ROM but this didn't seem to fix BLN notifications.
Reflashed NSCollab ROM. Tested BLN and initially still not working but after a reboot it's all working properly again.
so it might just be a stock rom + BLN kernel issue has any of the kernel devs looked into this?
I tried it out a few hours ago on my 9020a with CM7 and the Trinity UV kernel and so far BLN free version works great, not that I have much use for it, never used it on my Galaxy s but will see.
I too am having issues with it working on calls. emails/txts it works without fail.
EDIT:seems i found the issue. its the good old BFS choose a kernel that doesn't use it and it works fine. Seems bfs doesnt really like the 9020a's.
themapleboy said:
I too am having issues with it working on calls. emails/txts it works without fail.
EDIT:seems i found the issue. its the good old BFS choose a kernel that doesn't use it and it works fine. Seems bfs doesnt really like the 9020a's.
Click to expand...
Click to collapse
im using it with netarchy 1.3.0.3 CFS so im not sure if the BFS is the sole cause of this
Hi,
I'm just wondering if anyone got BLN working on the Jame Bond kernel ?
I've read in that thread that it supports Voodoo and BLN and I'm using the Sabai dee kernel but BLN doesn't seem to work for me ?
To be honest, I'm not too sure how to run the test. I click on it and it says press the power button to test it, which I do, but then my screen just turns off and nothing happens....am I doing something wrong ?
I also brought the pro version, and tried calling myself and sending myself an email and nothing happened.
Any suggestions ?
Cheers in advance
I'm running SupeAosp 6.2 Rom and BLN works perfectly for with, this includes missed calls and notifications. The Kernel that I'm using is 2.6.35.12-SuperAosp-S-1400. Apparently the next upgrade is going to be compiled with the UV which I am planning to test out as soon as its released. Furthermore as a bandage solution people can use NoLED without any mods at all, I found the app quite useful as I was not experienced enough to recompile with BLN included.
I forgot to mention, I am using an i9020A.
Chibsz said:
Hi,
I'm just wondering if anyone got BLN working on the Jame Bond kernel ?
I've read in that thread that it supports Voodoo and BLN and I'm using the Sabai dee kernel but BLN doesn't seem to work for me ?
To be honest, I'm not too sure how to run the test. I click on it and it says press the power button to test it, which I do, but then my screen just turns off and nothing happens....am I doing something wrong ?
I also brought the pro version, and tried calling myself and sending myself an email and nothing happened.
Any suggestions ?
Cheers in advance
Click to expand...
Click to collapse
first of all make sure all your settings are correct in the bln app...
bln works for the 9020a, but I forget if the missed call works or not...everything else seems to. with that being said, the issues with stock and the missed call not working will be sorted shortly...when the 9023 gets working...its not the 9023 recovery causing the problem
I know this isn't where i should post this but my Post Count is to low to post in the development forum. I installed RC 0.4 of CM 7 with a full wipe from .3 and up until last night everything was working fine (except the 4g/3g hand-off). Last night out of the blue it started random rebooting/boot looping. I plugged it in and went to bed. When i woke up it was on and some of my launcher settings were reset but other than that it was ok. Then today I have been experiencing more random reboots. Anyone else with this issue?
Can't post in the dev area yet either
I've had CM7 RC4 on for 3 days now and I haven't experienced any reboots yet but I'm not in a 4G area. Did you mess with the overclocking settings? Try to drop it down to 1GHz and see if that helps. Are you on the stock radio? I have mine on stock radio and it seems to work well.
I didn't overclock it any. I did use setcpu to check to make sure that that it was limiting itself to 1Gh thought, but i didn't touch anything else. My radio is the stock MR1 radio 1.16.00.0402w_1. I switched kernels to KangBang's most recent version for now, the random reboots became to much to handle.
You need go back older radio 223r, I have no problem with CM7 RC0.4 and none reboots. The CM7 author stated says use 223r radio.
slayher said:
I highly recommend The stock radio images. All the testing up to this point is based on 1.16.00.0223r Baseband
Click to expand...
Click to collapse
JBass said:
I didn't overclock it any. I did use setcpu to check to make sure that that it was limiting itself to 1Gh thought, but i didn't touch anything else. My radio is the stock MR1 radio 1.16.00.0402w_1. I switched kernels to KangBang's most recent version for now, the random reboots became to much to handle.
Click to expand...
Click to collapse
I read in the forum that you need to be 402w or before.
here: http://forum.xda-developers.com/showpost.php?p=14692504&postcount=5024
Keep in mind that the stock setting for the new release is 1.8GHz in the performance settings. I heard this stock setting was causing some problems for some.
JBass, you gave me link is not CM7 author.
You need read again - http://forum.xda-developers.com/showpost.php?p=13179476&postcount=1
I know that it wasn't from the dev but I guess I'm naive for believing the internet
Now its supported,
cant post link but on rootzwiki the post has been updated.
Hi, im new here and couldnt find any similar threads so posted this one.
I just updated my p920 with stock optus v20b firmware.
When i go into the battery usage page, the time on battery keeps restarting every couple of minutes.
eg. it would keep counting from "1s on battery" to "1m 7s on battery" then go back to "1s on battery".
This will also reset all the percentages used by apps. some times it even shows display using 230% when the time resets to 1s.
Has anyone had this problem??
any help would be appreciated. thanks
Yeah, that's a known problem on the stock GB ROMs. I have that too.
oh, so its a known problem. has there been any fixes for it yet?
Nope. Pretty much all GB roms (Except CM7 Ones i think) have some sort of broken battery stats
Yeah, CM7 works fine because it's not based on the original LG ROM. All other ROMs "inherit" that problem from the stock ROM.
Hi,
I am running CM9.1 on my Nexus S and off late I have noticed my device turning off suddenly. Whenever this happens battery is low but not low enough. i have seen this happening even when battery was 17-18%.
Has anyone else faced this ? Is this hardware problem or CM9.1 on Nexus S issue ?
Try something newer... Cm10 or anything... If more shut offs... Its probably hardware related
best use rasbeanjelly or metal dragon overlord rom...those are rock stable and really smooth ...
try the marmite kernel or airkernel r2 stable....
If you upgrade to cm10, make sure to use a cm kernel, since cm10 and aosp now require different kernels.
Sent from my ns4g using Tapatalk 2
Hi everybody.
I have recently flashed EaglesBlood AOSP 4.0.4 ROM with harsh kernel 3.0.44 to my P999 just for testing how does ICS work on the device.
Overall it's nice. Animations are smooth, device got it's second breathe and I appreciate all the work that dev's done
However I've got an issue with Wi-Fi: when I turn it on list of available routers can be seen. After I select mine, entered the password and clicked on connect I'm getting "not in range".
To be honest, I have a suspicion that this is a hardware issue, not software.
Is there any way to determine it using ADB, Eclipse, LogCat? Can I have kernel's dmesg output?
PS cannot post to development forum
---------------------------------------------------------------
browsing the internets i've found an app called lumberjack, which allows you to monitor almost all log files.
for more accurate output i've turned airplane mode on and cleaned all logs. after, i turned wifi on.
in the logcat (radio) tab nothing interesting for me. it says that wifi change status handled etc. nothing interesting in the logcat (events) tab also.
in the logcat tab i can see
Code:
W/wpa_supplicant
wlan0: Failed to initiate AP scan
nothing about wifi in dmesg also.
last_kmsg is empty. in loaded modules i can see this:
Code:
wireless 203871 0 - Live 0xbf000000
i've tried to google the error (failed to initiate AP scan), but every link is about *nix systems, nothing about android.
i can assure you that there are multiple wifi access points in the range of device.
on the previous ROM, CM7, i've got an issue with wifi. sometimes, when i tried to turn wifi on, all i was getting is a message "Error" under the checkbox.
I'm a heavy user of both eaglesblood and cm7. I have never experienced any of the issues you are describing here regarding to wifi. My guess is that your hunch is correct....its possibly a hardware issue. The only thing I can really recommend is to switch kernels. I highly recommend Trinity's ics Max 1500 kernel. I've tried hash's kernels with eaglesblood and other ics roms and they make my phone too unstable.
Sent from my LG-P999 using xda premium
Try the hard reset by holding vol+ and power until device reboots.
The noob says:
In the absence of a valid argument, 2+1=3 may be used to explain why the g2x did not get the ICS update!
mansa_noob said:
Try the hard reset by holding vol+ and power until device reboots.
The noob says:
In the absence of a valid argument, 2+1=3 may be used to explain why the g2x did not get the ICS update!
Click to expand...
Click to collapse
no result.
Pain-N-Panic said:
I'm a heavy user of both eaglesblood and cm7. I have never experienced any of the issues you are describing here regarding to wifi. My guess is that your hunch is correct....its possibly a hardware issue. The only thing I can really recommend is to switch kernels. I highly recommend Trinity's ics Max 1500 kernel. I've tried hash's kernels with eaglesblood and other ics roms and they make my phone too unstable.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
it seems that i cannot find trinity's ics kernel for p999. i've looking for it http://www.derkernel.com/index.html. there was no p999 at all. further search through google pointed me at kernels for p999, but for gb, not ics.
i'm confused
________________
seems that i found it: http://forum.xda-developers.com/showthread.php?t=1078049. installed the XLP kernel. as far as i can guess, XLP version and the T version are same kernel, except that T is overclocked.
anyways, i have flashed the trinity kernel, and after that i had broken radio. wifi was in same state.
for now i just flashed to my backup, cm7, where i have working wifi (sometimes )
i am still wondering is there anyway to confirm or reject the hardware problem?
http://forum.xda-developers.com/showthread.php?p=23386864 (here's the thread)
And here's the kernel.
Woops...looks like you already found it lol. Yup, the XLP is basically just a non-oc version that maxes out around 1015 I believe. I prefer kernels that are OC'able so I can run them at higher MHZs but lower voltages. Good luck on diagnosing your issue man.