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!

[KERNEL] Kernel (deprimed_test) - Break It If You Can

With the my new build wifi gets stuck at Obtaining IP Address with the newest deprimed. My guess is something in 2.3.4 broke it. I haven't tested with stock kernel and won't be able to tell tomorrow.
 
Would you mind interpreting it for me, as I would like to instated what out is and does.
Thanks


walkin the walk while tappin the talk
danceswithbongs

I assume you are asking what ipv6 is/does. I am far from an expert on this subject, but I'll give you the short version. Typical IP addresses are 256 bits, which are usually shorthanded to 4 decimal numbers known as octets. For example, 192.168.1.1. Each device on the internet must have a public IP address. Your computer in your house may or may not have a public IP address. Mine do not, because they sit behind my wifi router, so my router has a public IP, but my PC's have private IP's. Anyway the internet ran out of public IP addresses, so they went to ipv6, which has a larger number of bits, and therefore more available addresses.

This is the part where I speculate, because I don't know a whole lot, but I would assume phones get public IP's when they are connected via 3G. I would further suspect that those IP's are ipv6 addresses. Whereas when connected via wifi, they may or may not be public IP's, and may or may not be ipv6 addresses, they may be ipv4 addresses.

So given the above asssumptions, if you have an app that defaults to ipv6 but gets an ipv4 address via wifi, I assume there could be issues, but this is where I need an expert to weigh in.
 
Thanks GBOGH
If it is all correct very helpful.
Somewhat correct still quite helpful.
Completely wrong I end up losing a ton on the video daily double on jeopardy, Trebek mock me, I go into a tailspin and end up only finding some salvation and comfort in the fact that at least I'm not Donald Trump.
Cuz then, I'd really hate myself.

I now see where I started getting the wrong impression regarding compression in my initial expression. The different bit rates made me think it was the same, but due to compression at it's own discretion.
Allow me this confession: The error most likely is because I was first reading something about ipv6, whilst watching C-SPAN with the House in session each side refusing any concession on their interpretation of the freedom of expression.

Oops, I apologize for that major digression.

walkin the walk while tappin the talk
danceswithbongs
 
same issue...android system gives wait or FC. ...using winner 57
standard VSEL 250 -900MHz latest deprimed. Only started after kernel install. really notice when installing apps.

An oddity, since flashing the kernel I am seeing the "Android OS" as using the majority of the resources, not the display like normal. Is that unusual? Not noticing significant battery drain yet compared with normal, just found it odd.
 
same issue...android system gives wait or FC. ...using winner 57
standard VSEL 250 -900MHz latest deprimed. Only started after kernel install. really notice when installing apps.

An oddity, since flashing the kernel I am seeing the "Android OS" as using the majority of the resources, not the display like normal. Is that unusual? Not noticing significant battery drain yet compared with normal, just found it odd.

This is on official CM
 
same issue...android system gives wait or FC. ...using winner 57
standard VSEL 250 -900MHz latest deprimed. Only started after kernel install. really notice when installing apps.

An oddity, since flashing the kernel I am seeing the "Android OS" as using the majority of the resources, not the display like normal. Is that unusual? Not noticing significant battery drain yet compared with normal, just found it odd.

This is on official CM

crazy battery life...DAMN:icon_eek:
 
Prime, Running your newest deprimed with LGBv1.7. Really smooth.
Question: What does the bumblebee governor do? Sry if I missed it in the forum. Just wondering which I should use, and at what speeds?
Thanks for the great work. I am using liquids build in setting for governs, no scripts.
 
same issue...android system gives wait or FC. ...using winner 57
standard VSEL 250 -900MHz latest deprimed. Only started after kernel install. really notice when installing apps.

An oddity, since flashing the kernel I am seeing the "Android OS" as using the majority of the resources, not the display like normal. Is that unusual? Not noticing significant battery drain yet compared with normal, just found it odd.

This is on official CM

Prime,

No clue why "Android OS" is using so much with official cm 7.0.2 here when using your kernel, but it was. Just refreshed(complete wipe) and reinstalled cm 7.0.2 and will try your kernel again in a bit. What were your settings for that device clock speed/governer? Would love to have that life. Was it in use at all or just sitting?
 
same issue...android system gives wait or FC. ...using winner 57
standard VSEL 250 -900MHz latest deprimed. Only started after kernel install. really notice when installing apps.

This is on official CM

Prime,

No clue why "Android OS" is using so much with official cm 7.0.2 here when using your kernel, but it was. Just refreshed(complete wipe) and reinstalled cm 7.0.2 and will try your kernel again in a bit. What were your settings for that device clock speed/governer? Would love to have that life. Was it in use at all or just sitting?

The screen on time was 2 hours, I run the device with bumblebee @ 900mhz most of the time over wifi usually. Wifi calling (and receiving) always enabled, sync off (still receive push email)... that's about it really. I run twicca as my twitter application (sync every hour), no facebook or any other social networking sites. I use boat browser, dolphin mini, and dolphin hd for browsing sessions. I use SystemPanel, watchdog, and OS Monitor for monitoring (not all together). I use SpeedView Pro(GPS speedometer) every morning/afternoon for 2 hours combined time to aid in broken speedometer issue in borrowed vehicle. I don't use 3G much because of signal issues in immediate area.
 
same issue...android system gives wait or FC. ...using winner 57
standard VSEL 250 -900MHz latest deprimed. Only started after kernel install. really notice when installing apps.

This is on official CM

Prime,

No clue why "Android OS" is using so much with official cm 7.0.2 here when using your kernel, but it was. Just refreshed(complete wipe) and reinstalled cm 7.0.2 and will try your kernel again in a bit. What were your settings for that device clock speed/governer? Would love to have that life. Was it in use at all or just sitting?

The android os rise is because of BFS, it is giving the OS priority therefore causing higher CPU usage. See in my image, android os is near the top also, we will just have to monitor it and see if the positive outweigh the negative.

I am seeing no issues, but each device is different.
 
I'm not seeing the high OS battery usage. Overall battery life seems great. Wifi is my only issue 57 with latest deprimed. Reports #1

Sent from my Droid using DroidForums
 
So Prime, on your device running cm getting those crazy battery stats, are you using swap/compcache/both? Trying to figure out the battery impact. Thinking cm 7.0.2 needs at least compcache, but not sure.

Installed your kernel again and this time, so far at least it all seems pretty normal. Maybe the fresh install of cm 7.0.2 was needed.
 
@Prime, I follow you on twitter as Gil_Smash and I tweeted about the increased performance and testing for batt life and after I said that everything was going good, I got my slots all set up with milestone overclock and then today when I started using my phone I started getting worse and worse performance till it was almost impossible to use. I'm running SS5.2 right now and I tried changing around settings such as JIT and compache settings but nothing made any difference. It got so bad that I had to switch back to chevys kernels. Any reasons you can think of for that happening. Could my voltage be too low? I was getting good battery life but nothing crazy so it wasn't worth it to me. I haven't had much good luck performance wise with your kernel even though I've heard such good things about it and I feel like either my phone just doesn't like it or I'm doing something wrong.

Sent from my Droid using DroidForums
 
Back
Top