What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[ROM] [SELFKANG ICS AOSP ROM] CM9/ICS for Droid 4 -- [BETA 03/05/2012]

I posted an overclocking method for this ICS build in the droid 4 general discussions I am currently overclocked to 1430 MHz an running stable an lightning fast

Sent from my XT894 using DroidForums
Ur battery life isn't that much different is it?
What abt battery temp? Do u have occasions when its hot hot?
 
With WiFi, each device and operating system handle security on the router differently. CM7 & CM9 while similar in that they're basic builds of android, are still very different.

The command lines for when and how a security key is sent to the router are handled in a different manner. They're also recognized by the router differently when they respond.

In this example, this is CM9 base code, wifi set for enterprise security:


public class EnterpriseField {
private String varName;
private String value;

private EnterpriseField(String varName) {
this.varName = varName;
this.value = null;
}

public void setValue(String value) {
this.value = value;
}

public String varName() {
return varName;
}

public String value() {
return value;
}
}

/** {@hide} */
public EnterpriseField eap = new EnterpriseField("eap");
/** {@hide} */
public EnterpriseField phase2 = new EnterpriseField("phase2");
/** {@hide} */
public EnterpriseField identity = new EnterpriseField("identity");
/** {@hide} */
public EnterpriseField anonymous_identity = new EnterpriseField("anonymous_identity");
/** {@hide} */
public EnterpriseField password = new EnterpriseField("password");
/** {@hide} */
public EnterpriseField client_cert = new EnterpriseField("client_cert");
/** {@hide} */
public EnterpriseField private_key = new EnterpriseField("private_key");
/** {@hide} */
public EnterpriseField ca_cert = new EnterpriseField("ca_cert");

/** {@hide} */
public EnterpriseField[] enterpriseFields = {
eap, phase2, identity, anonymous_identity, password, client_cert,
private_key, ca_cert };



As you can see there are a bunch of commands that need to happen on the OS side before a sync can happen with your wifi router. Any variation here, can cause the enterprise security to boot the command back that there's a verification issue, like you're seeing.

The CM7 build, actually uses a completely different set of command structures than CM9, as in the way it processes each separate type of security (WEP, WPA, WPA2...etc).

So CM7 is going to act different than CM9, and vice versa.

Same with your router, in that with CM7, it could have been identifying your device as a standard wifi device, like another computer. When CM9 comes in, if the router is not updated with the best firmware, it may not recognize the new OS that your phone has. It also may be looking for a different log sequence from the phone in WEP or WPA or WPA2 securities. Hence the suggestion of messing with the router to see if a different security setting might work better than the other.

It also could be that because the first failed attempt by CM9 didn't verify correctly, the router could be blocking access entirely, because it thinks it's an intruder trying to take command of the router, and has blocked your phones IP or MAC address from connecting. I've seen this on some high end enterprise type routers in the past. They're security measures, that allow the router to automatically protect against bandwidth pirates, just looking to use your internet.

In order to truly figure out what's going on with all of this, you need to have admin privileges on the router, to access the logs of what is occurring when you're trying to connect to the router. Once you have the logs, you can then identify if the security type is the issue, or the MAC filter is the issue, or some other setting that may be causing your problem.

Or if the phone in general is just not catching at the correct time.

Without having those logs, there's not much anyone can tell you here on getting it fixed, unless there's a new update where the WiFi commands are changed, but those haven't been touched in 21 days according to Github. So I don't think you're going to get an update on wifi connectivity through the nightlies at this point, because it's not a main issue.

More pressing is solving the data switching from 4G to 3G & on reboot, and then the video codecs & bluetooth audio issues.

Those are more relevant to making this a truly daily driver for most users.

I hope this helps.
D*mn u are IT savy there pimp....:biggrin:.....well thanks for responded..i went on his laptop and went to search for programs and typed in belkin and belkin monitor popped up...I clicked it and nothing happened..like a dead window..but i was trying to search for those logs to see what's up...I'll just wait til he gets back an see what it is instead of annoying yal lol..but thanks. We should figure it out with this post u posted.
 
And if your friend doesn't know much about routers or IT, ask him to make a second network with WPA2 or WEP (Both work fine from my experience), password protect it and just hide the SSID. And if he is paranoid, he can also block all MAC addresses with the exception of yours. All of which is simple and can be done with a little bit of reading through the routers settings.
Ok thanks I didn't even think of that!
 
To access the router, it's done so by like going to a website. If you have access to the physical device, underneath it will have info, unless it's removed of course. It'll have a number like '192. 168.1.1' which gets entered in a Web browser, as tho ur going to a website. Depending on his settings, it might ask for a password to access the routers settings. It may also say that too underneath it Haha. If it doesn't, searching Google for something like 'default router passwords' would help if he didn't change it. From there, it's your choice on if you wanna mess with it. You maybe even be able to back up the routers settings, and screw with it without doing any harm, as long as you re load them. Just don't mess with firmware :P. I'd help more if necessary, but I'm gonna go to sleep
 
Ur battery life isn't that much different is it?
What abt battery temp? Do u have occasions when its hot hot?

The highest temp I have seen when running at 1440 MHz is 38 C an that's with it running all day an night plugged in to a wall

Sent from my XT894 using DroidForums
 
To access the router, it's done so by like going to a website. If you have access to the physical device, underneath it will have info, unless it's removed of course. It'll have a number like '192. 168.1.1' which gets entered in a Web browser, as tho ur going to a website. Depending on his settings, it might ask for a password to access the routers settings. It may also say that too underneath it Haha. If it doesn't, searching Google for something like 'default router passwords' would help if he didn't change it. From there, it's your choice on if you wanna mess with it. You maybe even be able to back up the routers settings, and screw with it without doing any harm, as long as you re load them. Just don't mess with firmware :P. I'd help more if necessary, but I'm gonna go to sleep
No worries mate!....iv always had a knack for fixing things..curiosity gets the best of me
 
I'm on 3/19 And yesterday and this morning I experienced 4G going out. Yesterday it took a little bit of restarting the phone and changing to GSM to fix it. This morning, I tried something else and got it back first try. Which leads me to believe this is the same exact problem that the Droid X and MIUI experienced for a while with the toggle buttons in the notification bar. I have the LTE button in my notification bar and when the 4G goes out, that stays lit up as though it's fully working/enabled. Next time your 4G goes out, make sure that 4G toggle is disabled from the notification bar and then switch it to GSM for a little, then back to LTE/CDMA in the network modes. I really think the MIUI Droid X developer wizard0f0s could help or give you his tips on how to fix it Hashcode.

Also, there is a problem kinda like the 4G problem. I use SwiftKey keyboard and it too randomly stops working. And this little notification in the notification bar that looks like a keyboard pops up when it does.
Edit: Nevermind, it may just be a ICS incompatibility with SwiftKey.
 
Last edited:
I'm on 3/19 And yesterday and this morning I experienced 4G going out. Yesterday it took a little bit of restarting the phone and changing to GSM to fix it. This morning, I tried something else and got it back first try. Which leads me to believe this is the same exact problem that the Droid X and MIUI experienced for a while with the toggle buttons in the notification bar. I have the LTE button in my notification bar and when the 4G goes out, that stays lit up as though it's fully working/enabled. Next time your 4G goes out, make sure that 4G toggle is disabled from the notification bar and then switch it to GSM for a little, then back to LTE/CDMA in the network modes. I really think the MIUI Droid X developer wizard0f0s could help or give you his tips on how to fix it Hashcode.

Also, there is a problem kinda like the 4G problem. I use SwiftKey keyboard and it too randomly stops working. And this little notification in the notification bar that looks like a keyboard pops up when it does.

Click the little keyboard looking icon and choose swype again. That icon is the IME switcher (let's you switch between keyboards)

Sent Via My ICS Flavored DROID4
 
Click the little keyboard looking icon and choose swype again. That icon is the IME switcher (let's you switch between keyboards)

Sent Via My ICS Flavored DROID4

That works each time for you? Doesn't with SwiftKey, I've tried it every time it gets messed up. Maybe it's just a ICS incompatibility with SwiftKey than. Because now that you got me thinking about it, I don't remember the last time it got a update haha. Gonna edit my post saying maybe it's SwiftKey and check to see if maybe there is a ICS beta compatible.
 
Dang..in 6 hours I'm below 67 a good bit..

Are the bottom 3 vsel values stock cuz if not change them to stock cuz that's what killing ur battery cuz any vsel value below 63 will work anything over won't. ur vsel values should be from top to bottom 63 61 53 44 29

Sent from my XT894 using DroidForums
 
Sorry for the confusion, but I was talking abt stock..lol
I'm gonna give it a shot this weekend tho..
But thanks for the advise..I'm anxious to see if I can overclock this bad boy
 
Back
Top