yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] greg9100:
Gkernels1.0 to 1.3.3

Enable WiFi control function abstraction

Preallocate memory for WiFi buffers

Enable KSM for page merging

Use kernel mem{cpy,set}() for {copy_to,clear}_user() (EXPERIMENTAL)

kernel switched to low resolution timer

Cross-Compiled using arm-eabi-4.4.3

1.3.3 to 1.4.0.1

Suspend sleep mode (Power collapse suspend)

Control the low power modes of memory

Default Memory Low Power Mode during Idle (Memory in retention)

Default Memory Low Power Mode during Suspend (Memory in deep power down)

Enable standalone power collapse

Android RAM Console Enable error correction

Virtual Contiguous Memory (VCM) Layer

1.4.0.1 to 1.4.3.1

Built with an older toolchain arm-eabi-4.3.1

General filesystem local caching manager

Filesystem caching on files

Wifi-

Common routines for IEEE802.11 drivers

--- Bluetooth subsystem support

L2CAP Extended Features support (EXPERIMENTAL)

networking options-

IP: multicasting[*] IP: ARP daemon support

Qos service changed-

Hierarchical Fair Service Curve (HFSC)

---removed from 1.4.0.1 version---

adjust priority to speedup resume thread

1.5 is the same config, but with QoS removed, and patched source to 2.6.35.14
[Streak 5 Android Development] _n0p_:
Greg, huge thanks (don't know if this the right expession :))

--

New thought. Wifi is actually usb-interfaced dongle. How do you think, will enabling or disabling usb power management help?

--

Sergei
[Streak 5 Android Development] greg9100:
Interesting!

Let's try enabling first, how can I assist?
[Streak 5 Android Development] _n0p_:
Let's build it :)

My build times are bad, would you enable it and publish the kernel, based on experimental14 dsc-team branch? If it won't break wifi, we'll ask lordmorphous to test it, as he suffers from this problem most.

I plan tomorrow to walk through your changes and find sound culprit.
[Streak 5 Android Development] greg9100:
Certainly-

I will post with the change

---------- Post added at 05:53 PM ---------- Previous post was at 04:58 PM ----------

Okay here is the CFS test kernel, with the cover hack modification, now with the USB power management;

Enabled

[*] USB runtime power management (suspend/resume and wakeup)

download link: http://db.tt/OY2NeyB5
[Streak 5 Android Development] lordmorphous:
Very excited to try this out. It will be tomorrow at the earliest as I'm not home and home is the only place i use wifi regularly.
[Streak 5 Android Development] ayturkozmen:
_n0p_

- SE Liveview MN800 Bluetooth wristwatch and SE MW600 Bluetooth headset pairing problems with 0.62b Dell Streak'm . Wants me to constantly re-pairing...

- Olleh 406 rom Nero Sync app installed to 0.62b but did not work with PC synchronization. GKernel 1.5 have installed to 0.62b the Nero Sync app synchronization no problem.

- USB storage does not work. SetCPU tried to use it for 998Mhz.

Vista x64
[Streak 5 Android Development] borijess:
Trying it out for the last two hours.

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] Dude_Virus:
Hi _n0P_ please find attached the logcat.
[Streak 5 Android Development] ltrifonov:
@Team:

[COLOR="Red"][B]addDefaultRoute (IPV6) for WIFI (eth0)[/B][/COLOR], GatewayAddr=192.168.1.1

D/NetworkManagmentService( 155): 200 default route replace succeeded for [eth0 -4]

D/LauncherModel( 244): ----> items cloned, ready to refresh UI

E/NetworkStateTracker( 155): Unable to add default route.

E/NetworkManagmentService( 155): Failed to replace default route com.android.server.NativeDaemonConnectorException: Cmd {route replace def v6 eth0 192.168.1.1} failed with code 501 : {Invalid gateway address}: for iface [eth0]

Do we really need this stupid IPV6 ? as a network administrator i don't find any reason next 3-4 years about end customer devices...

other intersting errors:

I/Zygote ( 105): Accepting command socket connections

I/liblogfilter.so( 155): open logfilter done. mem:0x457e1000, version:e001d001, tagnum:55, writable:0

E/SurfaceFlinger( 155): [B][COLOR="Red"]Couldn't open /sys/power/wait_for_fb_sleep[/COLOR][/B] or /sys/power/wait_for_fb_wake

D/PrintK ( 155): <6>msm_kgsl: initialized dev=0 mmu=on per_process_pagetable=off

E/libEGL ( 155): eglSetSwapRectangleANDROID:1848 error 3008 (EGL_BAD_DISPLAY)

E/PrintK ( 1): <3>init: starting 'bootanim'

this is framebuffer early suspend, in our .config is not set, but something may look for this...

# CONFIG_FB_EARLYSUSPEND is not set
[Streak 5 Android Development] _n0p_:
Let's

ayturkozmen, aknowledged.

Sorry, i don't have a bluetooth set.

Answer may be in /etc/bluetooth/autopairing.conf

Nero sync - need to do checks.

--

Battery. Let's start.

STD Battery

W/PrintK ( 1): [BAT](31~39= 98 00 44 30 00 05 00 00 03) (22 0A 00)

Mugen

W/PrintK ( 1): [BAT](31~39= 00 00 05 30 C0 00 02 00 00) (22 0A 00)

Some value of above should be to battery type detector.

I need more logs of different batteries.

It's full of...

[b]//n0p - looks like we should go off at 4%. But battery/amss starting to decide it at 20%. Dunno, the simplest way that comes to mind -
detect Mugen.
On detection:
Get voltage. This formula:
(Voltage - 3200) / 16 should return correct percent for Mugen
gag_data[GAG_VOLT] = gag_reg_00_15[0x08] + (gag_reg_00_15[0x09]<<8);
[/b]
if(gag_data[GAG_SOC] < 20)
{
if(qb_data.low_bat_power_off)
qb_data.bat_capacity = (gag_data[GAG_SOC] < 4)? gag_data[GAG_SOC] : 4;
else
qb_data.bat_capacity = gag_data[GAG_SOC];
}
else
{
[b]//n0p - looks like this code tries to straighten charge curve on high charge values.[/b]
if(gag_data[GAG_SOC] >= 90)
qb_data.bat_capacity = gag_data[GAG_SOC] + 4;
else if(gag_data[GAG_SOC] <= 89 && gag_data[GAG_SOC] >= 86)
{
int soc_89_5, soc_88_5, soc_87_5, soc_86_5;
if(gag_data[GAG_SOC] == 89)
{
soc_89_5 = gag_data[GAG_FCC]*885/1000;
if(gag_data[GAG_RM] > soc_89_5)
qb_data.bat_capacity = 93;
else
qb_data.bat_capacity = 92;
}
else if(gag_data[GAG_SOC] == 88)
{
soc_88_5 = gag_data[GAG_FCC]*875/1000;
if(gag_data[GAG_RM] > soc_88_5)
qb_data.bat_capacity = 91;
else
qb_data.bat_capacity = 90;
}
else if(gag_data[GAG_SOC] == 87)
{
soc_87_5 = gag_data[GAG_FCC]*865/1000;
if(gag_data[GAG_RM] > soc_87_5)
qb_data.bat_capacity = 89;
else
qb_data.bat_capacity = 88;
}
else if(gag_data[GAG_SOC] == 86)
{
soc_86_5 = gag_data[GAG_FCC]*855/1000;
if(gag_data[GAG_RM] > soc_86_5)
qb_data.bat_capacity = 87;
else
qb_data.bat_capacity = 86;
}
else
{
qb_data.bat_capacity = gag_data[GAG_SOC];
}
}
else
qb_data.bat_capacity = gag_data[GAG_SOC];
if(qb_data.bat_capacity > 100)
qb_data.bat_capacity = 100;
}
[Streak 5 Android Development] _n0p_:
Lubo, i confirm your IPv6 point.

I remember that FB suspend is supported by driver.

--

One of config options/hacks gives jittering sound. Going to do check now.
[Streak 5 Android Development] roy8846:
When to do it??

I have a different battery

(this one)

http://www.ebay.co.uk/itm/130514397987?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
[Streak 5 Android Development] _n0p_:
Do a

adb logcat | find "[BAT]"

But after a fresh start of the system.
[Streak 5 Android Development] roy8846:
http://imageshack.us/photo/my-images/269/62787847.png/

thats on 0.61b (standard kernal)
[Streak 5 Android Development] _n0p_:
Looks like your battery is std for system.
[Streak 5 Android Development] Dude_Virus:
Ok installed the cfs test kernel .....wifi looks good...as of now....let me uninstall wifi reassociate and then check
[Streak 5 Android Development] roy8846:
strange , I have wiped stats different ways , let it drop from full charge to zero etc..

It stays on 1% for around 20 mins+ (depends on what I'm doing)
[Streak 5 Android Development] _n0p_:
20 min on 1% is ok. Have the same on std batt. It's like an internal protection for system.
[Streak 5 Android Development] roy8846:
So its not 1800 :(

Oh well it was cheap...
[Streak 5 Android Development] Dude_Virus:
Roy thats because ura too is an extended batt with 300mah extra than the stock so as dell doesnt report even a single mah above 1500 thts why the phone works even after reaching at 1%

For me when it reaches 1% and stays there the phone works for 20+ hours
[Streak 5 Android Development] Dude_Virus:
Roy its nothing to do with the battery...try this when it reaches 2% or even 1% just turn off ur device and then reseat the battery and you will notice the charge left to go up from 1%

If i reseat my battery when it reaches 1% the charge left shows as 70% and it again then runs down to 1% and if i again reseat the battery the charge left is 40%
[Streak 5 Android Development] greg9100:
@Team and community

With the latest test kernel,

feedback regarding the wifi freeze problem happening more often?

It seems to happen much more frequently in my device and environment;

There are more options to explore kernel .config-wise on Sergei's line of thinking:

In the USB section of drivers

< > USB Wireless Device Management support

< > Enable Wireless USB extensions (EXPERIMENTAL)

I could enable the USB Wireless Device Management support, and post?

---

Also I could disable IPV6, and post that as well;
[Streak 5 Android Development] borijess:
Using new kernal and I still get the wifi freezes.

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] _n0p_:
Most probably WiFi USB suspend simply has no effect, sorry.

Will study sources more.
[Streak 5 Android Development] Dude_Virus:
Well thts strange with this new kernel i am not facing any issues.....infact with the other kernel when the signal bars and the wifi symbol used to gray out i used to loose connectivity but on this one inspite of them getting grayed out wifi data transfer was still there.
[Streak 5 Android Development] _n0p_:
Well, i'm starting to think that there's actually a soul inside every Streak :)

Got no logical explanation for that. except you have a bigger battery...
[Streak 5 Android Development] Dude_Virus:
Even i am thinking the same tht every device is reacting differently to the same kernel.....as i remember with 1 kernel you has posted that maps are causing battery drain so best option is to freeze it however for me on tht kernel maps never caused a battery drain... neither did ever i found the time drift even without clocksync installed...yes only on boot it used to go off but back to normal withon seconds....

However onething i have noticed on this kernel tht even if i am stagnant at 1 place the wifi signal strength is fluctuating drastically...i checked tht by being 2 feet from my router and in wifi analyzet it was constantly goin up and down which is strange
[Streak 5 Android Development] greg9100:
@ Team-

I did not notice this in the logs before; is this the wifi dongle?

W/PrintK ( 161): WLAN init: bt pulse done ***************
D/PrintK ( 15): <6>mmc1: card 0001 removed
W/PrintK ( 15): [MMC]> host name mmc1, q_wlan_flag: 0
W/PrintK ( 161):
W/PrintK ( 161): Dongle Host Driver, version 4.217.63.0
W/PrintK ( 161):
W/PrintK ( 161): Dongle Host Driver, version 4.217.63.0
W/PrintK ( 161): BootLog, -dhd_module_init, ret=0
[Streak 5 Android Development] _n0p_:
@Team. I'm definitely doing something wrong here.

Here's a built kernel (.config inside installation archive)

- scsi drivers removed

+ enabled all codepages

+ hopefully all Greg's and Lubo's changes

- timer back to highres

+ increased upper freq limit (added to table)

- size opt removed

Sound OK, but SoD might be back (i think it's timer related)

Also, dhd.ko size is big(?) - i'm sure i've enabled wifi abstraction.

--

Lubo and Greg, i need you to review config options, a bit tired with slow compiling.

--

http://www.littlemaruko.com/Nopteam/DSC_Team4.zip

--

Sorry for been abrupt, quite tired today. At least sound issue is done for.

--

Roy, i'd like you to give a test for this kernel. Testing myself too.

--

Sergei
[Streak 5 Android Development] dsteinberg:
Hello I have reverted back to 0.51b to be able to check the cracking audio coming from certain games. And the proof is that with 0.51 up to pre 0.6 the audio is working as it should. to further confirm I have also flashed Greg's kernel over 0.51 and the cracking audio comes back. N0p, can the kernel be the issue with bad audio reported by others?

Ops,...was so excited to tell the news I missed your post ....sorry

Edit2: I am 99 sure the sod is timing related

Sent from my Dell Streak
[Streak 5 Android Development] _n0p_:
If we'll be able to undestand the real problem with rtc,...
[Streak 5 Android Development] lordmorphous:
I would like to report that so far wifi is working great for me with last night's kernel.
[Streak 5 Android Development] lanhaj:
lordmorphous

Can you give me the link to the kernel you are referring to? I am having wifi issues.

Thanks
[Streak 5 Android Development] _n0p_:
Great!

Greg, I think we should publish tomorrow our collaborative kernel with all gained so far options, but with hires timer for a wider test. If you'll publish cumulative config, i'd be grateful, and will try to push new freq table and config into experimental14.

Still, I cannot get why dhd.ko in my build is that size... Size optimization shouldn't have THAT effect.

Remembering tinkering with compilers long time ago, I can say that sometimes size opt outperforms speed opt (sic!), but only if looping blocks of code fit in 32K . Arm processors have low cache mem, dunno how much Snapdragon has.

--

Sergei
[Streak 5 Android Development] greg9100:
Here are two config files:

The config for last night's kernel-

Config-A,

[*] USB runtime power management (suspend/resume and wakeup)

-------

Today's kernel I tested privately

Config-B,

Disabled IPV6

[*] USB runtime power management (suspend/resume and wakeup)

[*] OTG Support

<*> Enable Wireless USB extensions (EXPERIMENTAL)

<*> USB Wireless Device Management support

These configs do not have the timer change in either, back to the high resolution timer,

they do have the optimize for size as well;
[Streak 5 Android Development] _n0p_:
I'd just like to add that two lately published kernels - by Greg and me have NAK patch.

To you this might mean that it's safe to use ondemand governor now, as main device freeze problem is eliminated with this patch.

--

I think we are very close to give .14 main kernel status, anyone willing to help - please test latest published kernel

http://xdaforums.com/showpost.php?p=20259943&postcount=1162

(it has USB power management and all available fs codepages, to make otg guys happy)

So we could take a rest a bit and revert to framework hacking :)

I also plan to publish special hacked kernel to test on 4800 battery. If any detection method will be found, it will go in main release.

--

Sergei
[Streak 5 Android Development] lordmorphous:
Sure...this one:

http://xdaforums.com/showpost.php?p=20238443&postcount=1137

Let us know if it works for you too!
[Streak 5 Android Development] _n0p_:
Last request for today: everyone, having 4500 mugen battery, we need your log output

http://xdaforums.com/showpost.php?p=20252846&postcount=1146
[Streak 5 Android Development] ayturkozmen:
_n0p_

// Do NOT change this file format without updating the parsing logic in

// BluetoothService.java

// This file contains information to prevent auto pairing with Bluetooth devices.

// Blacklisting by vendor prefix address:

// The following companies are included in the list below:

// ALPS (lexus), Murata (Prius 2007, Nokia 616), TEMIC SDS (Porsche, Audi),

// Parrot, Zhongshan General K-mate Electronics, Great Well

// Electronics, Flaircomm Electronics, Jatty Electronics, Delphi,

// Clarion, Novero, Denso (Lexus, Toyota), Johnson Controls (Acura),

// Continental Automotive, Harman/Becker, Panasonic/Kyushu Ten,

// BMW (Motorola PCS), Visteon

AddressBlacklist=00:02:C7,00:16:FE,00:19:C1,00:1B:FB,00:1E:3D,00:21:4F,00:23:06,00:24:33,00:A0:79,00:0E:6D,00:13:E0,00:21:E8,00:60:57,00:0E:9F,00:12:1C,00:18:91,00:18:96,00:13:04,00:16:FD,00:22:A0,00:0B:4C,00:60:6F,00:23:3D,00:C0:59,00:0A:30,00:1E:AE,00:1C:D7,00:80:F0,00:12:8A,00:09:93

// Blacklisting by Exact Name:

ExactNameBlacklist=Motorola IHF1000,i.TechBlueBAND,X5 Stereo v1.3,KML_CAN

// Blacklisting by Partial Name (if name starts with)

PartialNameBlacklist=BMW,Audi,Parrot

// Blacklisting by addition of the address during usage
[Streak 5 Android Development] lordmorphous:
Disregard my last. Had a wifi freeze...:-(
[Streak 5 Android Development] _n0p_:
Bad result is also valuable.

Will look more into wifi chip code.
[Streak 5 Android Development] Dude_Virus:
_n0p_ ok found an issue with cfs test kernel .... its not letting me charge the battery completely as its constantly giving an error message battery is taking too long to charge charging disabled...I have to then unplug the charger and start again...as the mugen needs 5 to 6 hours to charge completely..

now thts something i have noticed for the first time on tht cfs test kernel.... i have now downloaded the dscteam4 kernel and will give it a test as to how it goes
[Streak 5 Android Development] dsteinberg:
Installed, im just in the initial testing so just a few remarks: audio seems fixed but max volume sounds lower than before, i had phone in standby while charging all night @ max 1267.2 set with antutu then unplugged and phone rebooted itself. have now set to 1190 , testing, keep you posted.

Many thanks for your commitment in what seems now to be the only real deal with gingerbread on streak.

keep it up

ty
[Streak 5 Android Development] _n0p_:
And I had a SoD this morning. Just as expected :)

I will publish modded Olleh 406 kernel as 0.63 update, until we sort out the timer issue.
[Streak 5 Android Development] _n0p_:
v0.63b

Hard decision.

--

v0.63b

--

http://www.littlemaruko.com/Nopteam/updDSCv0.63b.zip

--

Cumulative. This means it contains all changes from prev. releases:

Flashplayer removed from system.

New DalvikVM.

Bootanimation.

--New--

Back to hacked Olleh 406 kernel. But with new frequency range 128Mhz-1267Mhz (by default set to safe range 245-1075)

--

hosts reverted to default. Remember, that using AdBlock may break some flash video site do to adblock detection.
​

With best regards,

DSC Team.

--

PS. This absolutely doesn't mean we stopped working on kernel! :)
[Streak 5 Android Development] lordmorphous:
Installing now, will report later. I'm giving GXKernel 1.0 a try with it.
[Streak 5 Android Development] borijess:
Just installed love the continuous effort to try to perfect this rom. Awesome job guys!

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] dsnreddy:
seems like a bit faster and snappier--but cpu is not going below 245 Mhz in idle condition
[Streak 5 Android Development] streakOwner:
The 406 ROM IS SAFE

The 406 ROM IS safe and the problem was not ın the rom ıtself or any low level baseband at all , but ınstead was a typo ın the ınstall.bat fıle whıch make automated ınstallatıons of the baseband fıles , namely the amss.mdb and the dsp1.mdb , somethıng lıke the maxıcets MIDFLASHERLITE or Multırecoveryflasher from UKSheep. So everythıng ıs SAFE ıf you dont use the automatıc ınstaller on that fıle , _n0p_ wıll soon provıde a updated versıon of the ınstaller for less advanced users havıng trouble flashıng the baseband fıles.

Lınk of the 406 pkg

http://www.multiupload.com/75ZNXCB370

Lınk of the Offıcıal 406 ROM

http://www.multiupload.com/L5VWGSX6EB

Enjoy the SAFE and the most stable custom ROM uptodate.
[Streak 5 Android Development] dsteinberg:
hello, and thankyou for your update. i am now runnning dsc 0.51b, flashed the zip 0.50b then the update 0.51b AFTER having copied over the update.pkg (406 olleh) on my SD fastboot flashed recovery.img (compatible with 14 ) and flashed the update.

all went fine, i then flashed the portrait.zip file from themanii and my streak boots up fine.

only strange The BB version shows GAUSB1A140514-US.

Advice: should i start all over again using the link provided by n0p or streakowner and download the 406 update, the 406recovery then factory reset then the 50b, then wipe dalvik and cache then 51b and that should fix and i should have the 406 BB?

ty
[Streak 5 Android Development] _n0p_:
dsteinberg, i think it would be sufficient to flash BB and DSP using

This package (just prepared and tested).

Extract it somewhere and run flash (flash.cmd)

--

Reorganized first post. I'm not good at it...

--

Quick update to v0.52b - possibly-not-working-at-all SoD workaround.
[Streak 5 Android Development] uglyrooster:
Same issue here:

- Complete install from 406 via fastboot: GAUSB1A140514-EU

- Additional install via package: GAUSB1A140514-EU
[Streak 5 Android Development] streakOwner:
ı have flashed these fıles

http://www.multiupload.com/YZJ9VXRMYU

http://www.multiupload.com/G30B90JNS1

wıth these result
[Streak 5 Android Development] uglyrooster:
Files are identical with n0p...
[Streak 5 Android Development] _n0p_:
Guys, that's a really strange issue.

I don't have a PC right now at least to do a simple "fc /b " check.

To start: dsteinberg and uglyrooster - you have flashed 405 baseband before, am I right?
[Streak 5 Android Development] uglyrooster:
Solution was possible with zip-file update to 406.

Sounds strange but was the last and only step that finally worked.

Btw: SOD solution with screen on in 0.52 works fine so far.

Thanks for that great ROM!
[Streak 5 Android Development] dsteinberg:
Hello can you outline in detail the steps you took to successfully have the 406 bb please
[Streak 5 Android Development] smnc:
Looks you were right _n0op_.

The problem is Jorte having a fit with that specific calendar.

Martin

Sent like a Streak of Light from SpideyStreak using Tapatalk
[Streak 5 Android Development] uglyrooster:
@dsteinberg:

Solution is easyier than everything else. Load this file from streakOwner:

http://www.multiupload.com/75ZNXCB370

Go into streakmod and make an update via update.zip, but choose the zip-file above.

At least you have to delete dalvik cache and cache, even a factory reset was not necessary coming from _n0p_'s ROM (I tested both ways).

You are not rooted afterwards and some settings are overwritten but even a restore afterwards from nandroid worked fine.

For sure a factory reset and building up from scratch will be the perfect way...
[Streak 5 Android Development] idkidk:
Hi _n0p_,

I have maxicetdroid 1.2 and streakmod recovery installed, can i flash directly the whole rom via streakmod (and do a factory reset) or i must restock the streak?

Tia

Idk
[Streak 5 Android Development] _n0p_:
Simplest way - simply flash full DSC ROM 0.5b over, than flash 0.52b (most current update).

Do a factory reset right after.

Keep in mind, that you should move apps to internal memory before flashing.

If you want really fresh install -

http://xdaforums.com/showpost.php?p=18656924&postcount=2
[Streak 5 Android Development] uglyrooster:
@idkidk:

I switched several times from maxicetdroid to _n0p_, no problems with deleting dalvik cache and cache.

As mentioned before: A factory reset is always recommended!
[Streak 5 Android Development] idkidk:
THANKS!
[Streak 5 Android Development] idkidk:
THANKS! I'll try

Bye

Idk
[Streak 5 Android Development] _n0p_:
smnc, that what logs are for :)

Glad to hear.

--

New wway's GingerTrue theme (v1.1) is available in new "themes" section.
[Streak 5 Android Development] takodijkman:
Me posting the above post, makes me obliged to tell my experiences with your ROM installed now.

Ready???

It's simply awesome :p!!!

Love this one, really stable, fast, snappy.

Spent a lot of time and attention to the installation, to make that absolutely clean. Maybe a good thing to share for everyone having problems.

* factory reset

* reboot and fastboot; flash amss, dsp1 and recovery for 406

* reboot and update to 406 with recovery

* reboot and fastboot; flash StreakMod recovery

* reboot and go into SM, update with DSC's zip

* reboot and factory reset

* reboot and go into SM, update with DSC's update zip

* wipe Dalvik, cache and fix permissions

* reboot and factory reset

-> you're off to a great experience!

Don't forget to calibrate the battery (app from market, or use 'clean battery stats' in SM)