yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] _n0p_:
Let's wait for Greg's commits - i think where will be plenty :)

--

Meanwhile, i have an urge to setup a build host.

I've got CentOS buildmachine - is it ok or better use some Debian flavour?
[Streak 5 Android Development] lordmorphous:
Apparently wifi won't work at all with 354 baseband.
[Streak 5 Android Development] _n0p_:
This is starting to get interesting.

I'm using 354 BB right now together with freshest DSC-Team kernel, made by Greg, and, except blinking LEDs, everything works.

--

How could that be?
[Streak 5 Android Development] ltrifonov:
mine is Ubuntu, but CentOS should be OK too!

check the README file in our github, that is how i do this
[Streak 5 Android Development] _n0p_:
And i'm usually not too emotional, but :)

Thank you, Lubo!

Bulding now, say, if i remember correctly, changes to sources (except changing config) will result only in rebulding changed objects, am i right?

--

Sergei
[Streak 5 Android Development] greg9100:
Hello DSC Team!-

I actually haven't committed any changes at all within the 4.05 source itself;

Mainly I have focused on the .config and seeing what the hardware meshes with,

going to take a look at these logs! The wifi issue is mysterious yet
[Streak 5 Android Development] ltrifonov:
when modifying litle things , for exampe in one file, then no problems to rebuild again after change, it rebuilds only modified files.

when changing more things at once, it is safe to do make clean first

but... if compiling passes without errors it will be OK :)

if you want to test, this is my build of

Greg's .config, DSC-Team0.2 but comented out this

# CONFIG_MSM_CPU_FREQ_SET_MIN_MAX is not set

without this, mine streak is not booting

boot.img

dhd.ko
[Streak 5 Android Development] greg9100:
@ltrifonov Testing your posted 0.2, and cloned our repository from Github, excellent!

@all regarding the sleep policies

Gkernels1.4.0.1 was tested in 'when screen turns off', thereby wifi would have only been present in short bursts during testing for me, when set to this I found no issues present.

yet I am moving more away from controlling power modes regarding the wifi module, not receiving enough, during sleep/suspend, as I originally thought.

still looking at these logs!
[Streak 5 Android Development] greg9100:
I've captured a wifi issue with ltrifonov's 0.2, on 'never' policy

but couldn't copy in time to share, yet it did look similar to the logs shared with me, Wifi appears to null out, and there's errors and then some zero mac addresses

@_n0p_ and ltrifonov I will build a 0.2+ with this disabled

adjust priority to speedup resume thread

with our collective source-

then I will test and post for testing purposes only

-Greg

---------- Post added at 12:26 PM ---------- Previous post was at 11:54 AM ----------

I've pulled ltrifonov's .config direct from his 0.2 build

and compiled again without:

adjust priority to speedup resume thread

Still using the codesourcery toolchain, and now our Github source!

for testing here is the link:http://db.tt/qbInqQSg
[Streak 5 Android Development] lordmorphous:
This was a mistake on my part. I flashed the baseband with a batch file I had made a while back. My batch file flashed dsp1 as well. I'm now connected to wifi with 354 amss. I only have a couple hours until I have to leave again, so we'll see how it does during that time.

Got a wifi freeze with the 354 baseband. Here is my logcat dump. Going to flash the right baseband now and DSC-Team0.2++ kernel
[Streak 5 Android Development] lordmorphous:
Got a wifi freeze with this kernel too. Here is my logcat dump.

Wanted to add that I was in the middle of a download when the screen turned off and the wifi froze.
[Streak 5 Android Development] _n0p_:
Guys, I think we should carefully review i2c code.

We with attila.m have tested disabling speedup resume in prop, but that doesn't help him either.

I still see resume error in latest attila.m and lordmorphous logs.

Odd enough, I see the same errors in my own log, but wifi works for me.

Maybe a combination of wake locks and sleep may cause this issue?
[Streak 5 Android Development] greg9100:
Thanks lordmorphous-

Looks like the same type of error; we haven't got it nailed down yet-

May be the kernel is actually missing some networking configurations?

We need a brain storm perhaps, I'm thinking _n0p_ was on the right track with his suggestions

I've still been waiting for my device to have the error as well, I haven't yet since the flash around noon est here, phone been in sleep for at least one hour, usually enough time for the issue to surface

-Greg
[Streak 5 Android Development] greg9100:
What if we are using the wrong driver for wireless?

Could it actually be bcm4329? I will give this an attempt tomorrow
[Streak 5 Android Development] mokokawi:
I like the rom a lot....but I would like to change my lcd density....I used to use an app to change it to 240,on froyo rom....but it wont work on this.....anyway I can change it to this dpi

also...I want anothe dialer theme....and for it to work in the 240dpi setting

sent from my Pimped out Dell Streak
[Streak 5 Android Development] roy8846:
Dpi changer works fine.

Search market its free
[Streak 5 Android Development] borijess:
I know that wifi is the bigger issue here but has anyone been able to solve the proximity sensor during phone calls? Which causes the touch screen to freeze. I use the power button to end call but gets frustrating when on an automated phone call and need to access the dialpad to push number 1. This is an issue that plagues all gingerbread roms.

Sent from the SuperStreak!
[Streak 5 Android Development] mokokawi:
my wifi is working good....get calls good too..and I havent even flashed the amss...and dsp files yet

sent from my Pimped out Dell Streak
[Streak 5 Android Development] mokokawi:
thanks

sent from my Pimped out Dell Streak
[Streak 5 Android Development] _n0p_:
I've got a solution for blocked on-screen keys after or in call.

--

This happens only when you change phone orientation with proximity sensor on (near the ear is the most frequent case). I plan to take a look at correction of libsensors behaviour, but meanwhile you can use this, a bit inconvinient solution:

Determine what orientation you use most - landscape or portrait. If you make calls frequently, you might choose portrait.

Download and install portrait mod (link available in first post)

Install SmartRotator from market. It will lock all apps to default orientation.

In SmartRotator settings, tap on apps you need to be auto-rotated and select "turn on"

Don't choose Phone for obvious reason.

Now you can forget about blocked keys, as Phone app will stay on your preffered orientation.

--

btw, as we are a community, everyone is free to share his solutions. I promise to keep track and publish links to them on first page.

Only thing - be very descriptive, so anyone would understand them correctly.

Things that are obvious to you might not be that for others.
[Streak 5 Android Development] borijess:
Thank u I did not know this. nOp by the way u r awesome!

Sent from the SuperStreak!
[Streak 5 Android Development] _n0p_:
Thank you! :)

I personally think that everyone, taking part in this project - either developing or testing, is awesome :)
[Streak 5 Android Development] DashingGentleman:
Just wanted to report back. Since version 0.6 I'm no longer experiencing any random reboots. Everything seems fine (but I haven't been using the phone very heavily). No SOD with min freq 245 and conservative.

The WiFi still seems to drop out every now ad again but that may have to do with my anoying wifi setup at work (a multi-AP WPA2 enterprise setup - Android really doesn't like it).

I installed the latest GKernel and I cannot overclock using SetCPU. I thought OC was a feature of these kernels?
[Streak 5 Android Development] _n0p_:
Greg has stated that Gkernels (as standalone project) won't be overclocked.

Now we're together working on 405 kernel sources (DSC-Team kernel project).

--

Meanwhile you could use patched Gkernels 1.4.0.1 (link available in first post).

(any other substitution for word "meanwhile"? I seem to overuse it :) )

--

As promised - modded ramdisk i'm using on our releases attached (renamed to zip, forum engine don't like .gz)

Changes from official ramdisk -

Reworked memory management.

Enabled debug.
[Streak 5 Android Development] ltrifonov:
"Unable to increase ACPU vdd (-5)"

this message is appearing in your logcat, this also appears in logcats from attila.m

This may be something with CPU voltage, in my logcat i never find such messages, and my wifi is extremly stable...

@lordmorphous: can you change your CPU settings this way:

min clock freq: 384

max clock freq: 998 (mine is 1.152)

governor: performance
[Streak 5 Android Development] _n0p_:
ltrifonov, i think it may be the issue with bus itself.

Now looking at i2c-msm.c

--

And it's full of hacks for our device :)

--

@DSC Team:

Quallcom recommends setting VDD in steps of not more than 25. Maybe we should try including all freq steps in kernel, so it may comply with this recommendation?

--

btw, i need a bit on info - ondemand jumps min-max or goes fast through all frequency steps?
[Streak 5 Android Development] ltrifonov:
there is a free program in market - quick cpu info pro

it shows in real-time cpu speed in notification tray, and you can watch how cpu is switching up-down at all possible freqs.

hmmm... it seems that my kernel keeps only max cpu... (aha, this is due to governor - when conservative cpu freq is changing all the time, when performance - keep on max)

But i still have excellent battery time ;)
[Streak 5 Android Development] _n0p_:
You got me a bit wrong.

I meant - how ondemand governor actually behaves?
[Streak 5 Android Development] TheManii:
From my experience, it uses the highest and lower half freqs,

example for [256, 384, 512, 688, 896, 998, 1024] (I'm making up half the numbers)

It would be:

256: 50%

384: 10%

512: 10%

688: 2%

896: 0.01%

998: 0.02%

1024: 27.97%

This is more or less true for both ondemand and smartass, it'll rapidly jump between 1024 and 512 then idle at 256/384. It rarely ever uses the freqs between around the top half and the topmost one.

If it's 1152 replace then 1024 would be rarely used and so on
[Streak 5 Android Development] ltrifonov:
I did some tests, most of time when "ondemand" it was min or max, but few times for very short it was 384 and 998, so it is jumping all
[Streak 5 Android Development] _n0p_:
That's good. I think we should build and test kernel with big freq table, with vdd step no more then 25.
[Streak 5 Android Development] ltrifonov:
now my table is:

struct clkctl_acpu_speed acpu_freq_tbl_998[] = {
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 0, 0, 14000, 0, 0, 1000},
{ 0, 128000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000},
{ 1, 245760, ACPU_PLL_0, 4, 0, 0, 0, 29000, 0, 0, 1000},
/* Update AXI_S and PLL0_S macros if above row numbers change. */
{ 1, 384000, ACPU_PLL_3, 0, 0, 0, 0, 58000, 1, 0xA, 1000},
{ 0, 422400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xB, 1000},
{ 0, 460800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xC, 1000},
{ 0, 499200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xD, 1050},
{ 0, 537600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xE, 1050},
{ 1, 576000, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xF, 1050},
{ 0, 614400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x10, 1075},
{ 0, 652800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x11, 1100},
{ 0, 691200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x12, 1125},
{ 0, 729600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x13, 1150},
{ 1, 768000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x14, 1150},
{ 0, 806400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x15, 1175},
{ 0, 844800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x16, 1225},
{ 0, 883200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x17, 1250},
{ 1, 998400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x18, 1300},
{ 1, 1075200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x19, 1300},
{ 1, 1152000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1A, 1400},
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0},
};

1000 to 1400 ...

1000 245760

1025 384000

1050 422400

1075 460800

1100 499200

1125 537600

1150 576000

1175 614400

1200 652800

1225 691200

1250 729600

1275 768000

1300 806400

1325 844800

1350 883200

1375 998400

1400 1075200

1400 1152000 - here is repeat

maybe that way?

or we can start from 128 and then all freq will be with own vdd
[Streak 5 Android Development] _n0p_:
I think this should do the trick, at least for testing purposes :)

We might come up with undervolted values later.

--

I've tried some i2c bus hacks, so far no good, if i'll have any success, i'll post them ASAP.
[Streak 5 Android Development] ltrifonov:
build complete ;)

<6>[ 0.233428] Max ACPU freq from efuse data is 1152000 KHz
<6>[ 0.234252] ACPU running at 768000 KHz
<6>[ 0.234283] [COLOR="Red"]19 scaling frequencies supported[/COLOR].

WARNING !!! experimental

boot.img

dhd.ko

But as I don't experiencing these wifi problems, i will not catch the diference...

CPU table:

struct clkctl_acpu_speed acpu_freq_tbl_998[] = {
{ 0, 19200, ACPU_PLL_TCXO, 0, 0, 0, 0, 14000, 0, 0, 1000},
{ 1, 128000, ACPU_PLL_1, 1, 5, 0, 0, 14000, 2, 0, 1000},
{ 1, 245760, ACPU_PLL_0, 4, 0, 0, 0, 29000, 0, 0, 1025},
/* Update AXI_S and PLL0_S macros if above row numbers change. */
{ 1, 384000, ACPU_PLL_3, 0, 0, 0, 0, 58000, 1, 0xA, 1050},
{ 1, 422400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xB, 1075},
{ 1, 460800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xC, 1100},
{ 1, 499200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xD, 1125},
{ 1, 537600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xE, 1150},
{ 1, 576000, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0xF, 1175},
{ 1, 614400, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x10, 1200},
{ 1, 652800, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x11, 1225},
{ 1, 691200, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x12, 1250},
{ 1, 729600, ACPU_PLL_3, 0, 0, 0, 0, 117000, 1, 0x13, 1275},
{ 1, 768000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x14, 1300},
{ 1, 806400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x15, 1325},
{ 1, 844800, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x16, 1350},
{ 1, 883200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x17, 1375},
{ 1, 998400, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x18, 1400},
{ 1, 1075200, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x19, 1400},
{ 1, 1152000, ACPU_PLL_3, 0, 0, 0, 0, 128000, 1, 0x1A, 1400},
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0},
};
[Streak 5 Android Development] _n0p_:
Maybe too early, but i've got no VDD errors so far in this kernel!
[Streak 5 Android Development] ltrifonov:
this is my 5th kernel for today, will leave it for the night ...

at least now we have extra fine cpu tuning :)

EDIT: kernel is still based on Greg's 0.2 with all him tweaks
[Streak 5 Android Development] _n0p_:
Lubo, i'd like to clarify - which config should I use when building kernel with my test hacks?

I'm starting to loose tracks, sorry.
[Streak 5 Android Development] greg9100:
ltrifonov-

Thanks! currently testing this build;

Earlier my en-devour with the other wifi driver bcm4329 failed, thought it was worth a try

---------- Post added at 11:49 AM ---------- Previous post was at 11:14 AM ----------

Thanks _n0p_ !

ramdisk acquired
[Streak 5 Android Development] ltrifonov:
Sorry, updated .config in github. this is copy of Greg 0.2 with added CIFS
[Streak 5 Android Development] mokokawi:
I like what youll are doing with the feq/cpu tuning.....great work

sent from my Pimped out Dell Streak
[Streak 5 Android Development] attila.m:
wifi seems resolving

@ltrifonov

i flashed the boot.img and copied the dhd.ko you posted earlier

and wifi seems remaining connected

i'm gonna pm my logcat to you and n0p

@n0p

i restored the original build.prop as well

cheers
[Streak 5 Android Development] borijess:
This did not work for me. Got excited for a while there but began to do the same thing again while on the phone. :'(

Sent from the SuperStreak!
[Streak 5 Android Development] truefat:
Mine freezes regardless of orientation. If I cover the sensor for more than 2 seconds the keys freeze. If I cover it less that 2 seconds it doesn't freeze or unfreezes if it was frozen prior.
[Streak 5 Android Development] _n0p_:
borijess, my apologies.

I'm using this solution for two weeks - and it works for me.

I'll try to find different one.
[Streak 5 Android Development] borijess:
Thanks

Sent from the SuperStreak!
[Streak 5 Android Development] _n0p_:
Would you run a simple check? If you operator has help line with automated voice menu - i'd like you to call it, when place your palm near screen/speaker. Screen will block. Hold it for 3-5 secs. Put palm away. Will your buttons be blocked?
[Streak 5 Android Development] borijess:
I tried it and it still works. It seems to be more of an intermittent problem now. With u r fix it works when it wants to.

Sent from the SuperStreak!
[Streak 5 Android Development] _n0p_:
Thank you. I was absolutely sure that it related to autorotate (bug in framework/lib), but now it seems like pure driver issue.
[Streak 5 Android Development] Masterzer0:
This morning, my Streak just got reboot while I'm reading unread msg from whatsapp.

It starts with blinking button and after that it went reboot.

I am using 0.61b with Gkernel 1.4.0.

Still try to reproduce the problem but nothing until now..
[Streak 5 Android Development] borijess:
I have never had a random reboot with this rom.

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] _n0p_:
Look like hw fault.

Could you take a look at your /firstboot/poweroff.log for any unusual events?
[Streak 5 Android Development] Masterzer0:
I already check the poweroff.log but it doesn't record the random reboot this morning.
[Streak 5 Android Development] _n0p_:
Blinking buttons indicate hw fault interrupt. And it works on low level firmware (there's lot of them(firmwares) actually).

It's most probably not related to undervoltage - my tests shows that on very low voltage only the video part goes off, Streak works and blinks buttons.

Any chance it was overheated a bit at that moment?

Any additional info on circumstances would be really appreciated.
[Streak 5 Android Development] _n0p_:
food for mind

@DSC-Team!

#ifdef CONFIG_QSD_SVS

#define TPS65023_MAX_DCDC1	1600

#else

#define TPS65023_MAX_DCDC1	CONFIG_QSD_PMIC_DEFAULT_DCDC1

#endif

static int qsd8x50_tps65023_set_dcdc1(int mVolts)

{

int rc = 0;

#ifdef CONFIG_QSD_SVS

rc = tps65023_set_dcdc1_level(mVolts);

/* By default the TPS65023 will be initialized to 1.225V.

* So we can safely switch to any frequency within this

* voltage even if the device is not probed/ready.

*/

if (rc == -ENODEV && mVolts <= CONFIG_QSD_PMIC_DEFAULT_DCDC1)

rc = 0;

#else

/* Disallow frequencies not supported in the default PMIC

* output voltage.

*/

if (mVolts > CONFIG_QSD_PMIC_DEFAULT_DCDC1)

rc = -EFAULT;

#endif

return rc;

}

static struct msm_acpu_clock_platform_data qsd8x50_clock_data = {

.acpu_switch_time_us = 20,

.max_speed_delta_khz = 256000,

.vdd_switch_time_us = 62,

.max_vdd = TPS65023_MAX_DCDC1,

.acpu_set_vdd = qsd8x50_tps65023_set_dcdc1,

};
[Streak 5 Android Development] ltrifonov:
our curent .config (still greg's 0.2) in github reads:

CONFIG_QSD_SVS=y

CONFIG_QSD_PMIC_DEFAULT_DCDC1=1200

but these may be conflicting with the logic:

#ifdef CONFIG_QSD_SVS yes we have it!

#define TPS65023_MAX_DCDC1 1600

#else

#define TPS65023_MAX_DCDC1 CONFIG_QSD_PMIC_DEFAULT_DCDC1 this is skipped

#endif

So, CONFIG_QSD_PMIC_DEFAULT_DCDC1=1200 probably is skipped and we are

working with 1600 as default ?!

EDIT: anyone tried boot.img from yesterday with big freq table?

i have early response from attila.m, but what about battery life? mine looks like drain faster
[Streak 5 Android Development] _n0p_:
Even more, TPS65023 itself checks the voltage :)

Well, as voltage AGAIN is set via i2c bus, my guess could be right.

either i2c has bugs, or its driver.

Just look how many hacks board-qsd8x50_austin.c

contains vs any official sources.
[Streak 5 Android Development] _n0p_:
It shoud :) - at least voltage supplied is higher. And i'm using it.

Was worth a try, but i still have vdd errors in logs, so we may revert back to our default table and concentrate on i2c analysis - maybe dumb udelays would help?
[Streak 5 Android Development] ltrifonov:
ok, but why I do not have such errors?

how long are you owning your devices? mine is pretty new - about 2-3 weeks.

can it be possible when battery get older, supplied voltage to be wrong?
[Streak 5 Android Development] _n0p_:
Since early spring.

But most probably thats not the case. This may lead only to shorter battery life - and i have errors on external power too.
[Streak 5 Android Development] _n0p_:
Here's for test:

http://n0p.8bit.fm/streak/DSC_Team.zip

In this build:

Our uv/oc table used.

tps driver sets voltage TWICE and prints results to log.

If this will be of ANY help, i'll provide a diff.

--

Sergei
[Streak 5 Android Development] Coxeroni42:
Is this a flashable .zip? Will try to test it from this evening on, don't have my cable at work.

Btw: Dunno if this has already been stated: 0.61b eats battery like a mf when being active. Watching .avis kills it in no time. Apart from that, it is very stable for me. Not a single forced reboot so far with it.
[Streak 5 Android Development] _n0p_:
It's flashable, but it's for testing purposes only.

What kernel are you using now? And i'd convert avi's to mp4 to use hw accel.
[Streak 5 Android Development] ltrifonov:
3 days ago, when first activated CIFS in kernel, I was watching avi movie on air from cifs mounted share, and battery drain was 30% for 1h 30 min . Not so bad :)

btw, @_n0p_ i am unable to access your site n0p.8bit.fm...

maybe some kind of regional IP restrictions.
[Streak 5 Android Development] dsteinberg:
Hello N0p, just a quick report

ive just installed beautiful WWay gingertrue light and the Battery level on standard lockscreen is showing up incorrectly.

tyia

edit: i had the default dsc wallpaper with dark background, i changed wallpaper with a bright background and now its showing up, its the black colour used for the characters thats misleading...

by the way the default DSC wallpaper is amazing but now i cant find it anymore :(
[Streak 5 Android Development] _n0p_:
ltrifonov, as it my work server, i just had to put some limits to number of sessions, sorry. It usually should let you in within 5-15 mins.

If anyone can provide free file hosting - i dislike file sharing engines completely, i'd be grateful.

--

dstenberg - you can open framework-res.apk as zip archive, extract it and take a look at all those .jpegs :) I'll report indicator issue to Pavel.

Actually it's my fav theme and was made as a motivational present to me :)

--

Sergei

Edit. Sorry, looks like provider down.

Will reload to gDocs.
[Streak 5 Android Development] Coxeroni42:
The standard 0.61b thingie, no changes made. Will try to see, if mp4 conversion helps.
[Streak 5 Android Development] _n0p_:
Links updated!

Thank you for notifying me - site will be down till Wednesday.

--

DSC_Team test kernel:

https://docs.google.com/open?id=0B2eKBWR7rH7ENGM2NWYwYmItNWY5YS00NzU4LTkzMDktZmVmNTNlYTdhZGZi
[Streak 5 Android Development] khoacoi:
Hi nop,

Thanks for your great work. I'm very glad to share my hosting with you. Please let me know if you need it.

Regards
[Streak 5 Android Development] lordmorphous:
I don't really know why, but my WiFi has been perfect the last two days. Sunday night, I made a nandroid backup of what I had (0.61b with Itrifonov's first WiFi module edit). I flashed the 406 update.pkg, then streakmod of course, then restore my nandroid backup. I've been very excited tracking the progress the team has been making but have been hesitant to flash any of the test kernels this time since everything is working so well. The only other change I can think of is I installed APN Manager from the market. I was having a problem connecting to some services I have running on a server at home while I was on 3G. I made some edit's to AT&T's APN settings and now those work too. I know APN shouldn't have anything to do with WiFi, I just wanted to share changes I made.
[Streak 5 Android Development] _n0p_:
Would you PM me the details?

I'm going to be quite busy on this weekend, but i'd gladly move to your site on Monday.