yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] satanix:
Yeah its great to know USB host is supported :) mouse doesn't show cursor tho. It only scrolls through the icons or apps. I think cursor support didn't appear on 2.3 until some other version after 2.3.3. Having said that USB keyboard works fine.

Anyway lets not digress from the main act! Looking forward to flash and test the next version :)

Cheers
[Streak 5 Android Development] _n0p_:
Looks like a framework issue to me. Thank you.

--

Lubo and Greg - won't you mind sharing Codesorcery toolchain you are using?

Can't find direct download, sorry. And build time 4.4.3 on my build host is very bad :(

--

BTW, still running BFS version built by Lubo and no vidmem problem so far :)
[Streak 5 Android Development] satanix:
No dude sorry. I've got no development background. Been an avid fan of android since G1 but have always been testing roms themes apps and other stuff. never coded :)

About the USB drive: I've created directories and push the commands through as per the first article but I don't think USB drive was mounted. The commands that I tried to put in terminal were:

mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system

I've even tried this command that I found on the second article but still no luck...

mount -t vfat /dev/block/sda1 /sdcard/u

If you know what the commands should be I would be more than happy to test it for you.

Btw you should try and get a generic data cable. They're going pretty cheep on ebay.

Cheers
[Streak 5 Android Development] ltrifonov:
(Sourcery G++ Lite 2009q3-67)

check here:

---------- Post added at 03:59 PM ---------- Previous post was at 03:55 PM ----------

@satanix

can you run command dmesg after you insert usb drive,

and show us last few rows from output?
[Streak 5 Android Development] _n0p_:
satanix, i had one, then another one. To be honest, they are ubsolutely ^*&^*& :)

Lubo, thank you!
[Streak 5 Android Development] _n0p_:
Got first vidmem fault. Will check with CFS scheduler.
[Streak 5 Android Development] takodijkman:
Great that development is going on!

Just a question - might have missed it in any previous post - but HDMI is unable to work in combination with Dell Dock?

Edit: wrong question, it is working. Only with OEM apps! Asks whether to use HDMI when opening these apps.
[Streak 5 Android Development] _n0p_:
Could you tell from which version hdmi support is broken?
[Streak 5 Android Development] takodijkman:
Thanks for the quick reply, but disregard my question, it is working!!!

I'm used to my LG, which immediately showed desktop and everything when connecting HDMI...

Dell only shows video and music with OEM apps. Took me 10 minutes to figure that out :o.

My video did crash upon playing, second time went okay.
[Streak 5 Android Development] _n0p_:
Good. It would too bad to find that Dell somehow deleted that from released kernel :)

Actually I planned to take a look at whose proprietary libs to recover development headers, but as I don't have a dock, that might be in very distant future :)

--

@Team. Running CFS with patches - no vidmem error so far. If no other problems will be reported - we are ready to release!

Thank you.

To be honest, I even did not think about upgrading kernel, but Lubo made diffs - and maybe we could together patch 3.x.x kernel?
[Streak 5 Android Development] ltrifonov:
about HDMI - i tested it 2 days ago and still dissapointed - only with stock video player, and no sound...

about kernel, I first tried to patch directly over 2.6.39 but... a lot of concepts are diferent in newer branches, patches has to be applied manualy.

It is possible to extract some driver from newer version, but whole kernel will be huge work...

i am with cfs now, quadrant test give me sometimes 1370 points - top score :) look fast and stable
[Streak 5 Android Development] _n0p_:
I know it would be hard to find and change system calls, but when we finish with current kernel, we might give it a shot :)

--

I'm getting about 1350 normally, I remember getting 1500+ on hacked 406 kernel, but don't care about it, as kernel built on sources gives much more possibilities.

--

Btw, i've swtched to ondemand to give nak patch a stress test :)
[Streak 5 Android Development] attila.m:
feddback on 2.6.35.7 DSC-Team0.2+

hi all

my experiences with kernel 2.6.35.7 DSC-Team0.2+

Wifi - with shorter standby periods it reconnects and switching over to 3G if neccessary but with longer standby periods it is losing connection

Emails - push email does not work it works only if the connection was not lost, i had to manually dowload my mails

i had to reauthenticate on corporate exchange server and pull the security policy

btw is there a way to ungear this policy?it's quite annoying...

Notification bar - i had couple of black screen after initiating messaging, calendar or email from notification bar, responded to back or home buttons only (i use my streak mainly for business purposes)

No other issues, i'm fine with stability and responsiveness

thanks guys

cheers
[Streak 5 Android Development] _n0p_:
Well, that's quite a few! :)

I think we will give a test for fresh kernel tomorrow, maybe, just maybe nak patch will make things better.

Have you given a try to TouchDown? I was using it till I switch to gmail completely, and was very satisfied with it. And you may ask your mail admin to relax policies for road warriors as well :)

I do experience black screen sometimes, actually that doesn't bother that much. It's a video driver fault, and can be completely fixed with disabling screen animations, but I just too love smooth gpu animations :)

--

Sergei
[Streak 5 Android Development] attila.m:
i had the push mail issue with gmail as well

but thanks, i'll give TDown a try

the annoying thing is that if i wanted to change the lockscreen with WidgetLocker for instance, i had to unlock the screen twice
[Streak 5 Android Development] _n0p_:
I might be wrong, but I previously though that push works only on ActiveSync connections, and Gmail does a timed sync...

I will try WidgetLocker.
[Streak 5 Android Development] satanix:
here are the lines that i think you may be interested in.

Cheers
[Streak 5 Android Development] borijess:
Battery drain is a lot higher with latest kernal.

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] _n0p_:
I'm going to be away from PC today :(

Lubo, would you be so kind to prepare and publish two flashable zips with .14 CFS-NAK-DJT kernels built with Codesourcery and 4.4.3 GCC for tests?

--

Sergei
[Streak 5 Android Development] smnc:
Holy Crap guys!

I don't check in for a few weeks and just look at what you've accomplished!

Between moving/renovations and my own Android project (for the Moto Spice family of phones) I haven't had the time to devote to DSC that I'd like.

Keep up the excellent work, and hopefully I'll have time to contribute something usefull in the near future!
[Streak 5 Android Development] ilian:
Thanks for the quick repaly. I've done what you said but again I have the 405 BB:) As long as I don't have any problem is it necessary to have the 406 BB?

Любо разбирам какво трябва да направя но резултата си е все същия. Не знам дали има някъкяв смисъл да сменям на 406 изобщо:) Благодаря
[Streak 5 Android Development] _n0p_:
smnc, there's a working rogers tethering solution by truefat in this thread. :) If you confirm, then one line from wishlist is done.

--

405 should be fine, but anyway - give flashme pack one more try, please. I personally never flashed 405 bb, but I think community would be grateful for 100% working solution.

What will be a 100% fix - is a restoring device with qdl, but it rquires a bit advanced skills.
[Streak 5 Android Development] ltrifonov:
Sergei, my day is full with meetings, now have 30 free minutes, will try to prepare both zips now
[Streak 5 Android Development] ilian:
I did again the flashme pack and same result - 405 BB :o Let me describe what I have done. Maybe I made some mistakes.

First nandroid backup, then flash the 406 recovery, then update.pkg 406, (I got them from the first page) flash recoverSM, and nandroid restore.

If you can give me some link for what I have to do with the QDL I can give it a try.
[Streak 5 Android Development] jenjenX:
I spent a lot of time getting the 406 bb on this ROM so maybe I can help.

Try factory restore, get in to fastboot, run flashme to flash the correct mbn files, now let the phone boot up.

Now check the BB, if it's okay now flash your required ROM as usual.
[Streak 5 Android Development] ltrifonov:
As Sergei requested, here 2 flashable zips, based on Greg Gkernel zip structure

WARNING !!! USE AT OWN RISK!!!

codesourcery

gcc443
[Streak 5 Android Development] borijess:
Are these different from this kernal posted yesterday?

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] borijess:
What's the differences between those two kernals?

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] _n0p_:
They are build with different toolchains, might give different results on battery/performance.

This kernels built with cfs, not bfs scheduler, so battery should behave exact as 0.62b version.

--

Lubo, thank you!
[Streak 5 Android Development] borijess:
So both of these kernals are different than the 1 I posted the pic of?

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] _n0p_:
Yes, they should.
[Streak 5 Android Development] borijess:
Are these kernals based on Gkernal 1.5?

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] Dude_Virus:
DSC TEAM

THE BEST CUSTOM ROM I HAVE COME ACROSS...

I simply love the ROM . Love the responsiveness and the simple yet superb theme and the wallpaper WOW...have been on it since the past 3 days and no SOD , no random reboot , no headphone or charger unplugging freeze issue. Infact I am have set the proc to be overclocked both min and max with performance governor and still no issues.

One things that i noticed which happened twice.

On pressing the button for the screen to go off it comes right back on ... again i press the button and the display is back on.. i had to do the process 5 times for the screen to finally stay off. ( this happened twice )

A request...Can the kernel be coded to detect and report battery power other than the stock battery. I have a mugen 4800 and it never reported correctly on the stock and neither has it reported correctly on this ROM too...Mugen says that there is an internal setting.

What happens is that the battery reports draining properly like a stock battery does and then goes down and gets stuck at 1% until the entire charge is finished .

LOVE the work U guys are doing.. simply awesome and amazing.
[Streak 5 Android Development] ltrifonov:
they are based on DSC-Team sources from here

Greg will say if Gkernel is using same, or different sources.

.config file is based on Greg's .config as He is part of DSC-Team.
[Streak 5 Android Development] borijess:
OK thanks sorry for asking so many questions.

Sent from the SuperStreak! ;-)
[Streak 5 Android Development] ltrifonov:
I think you have to install some kind of battery calibrator, they are free on market. Then charge your new battery to 100 % and run calibrator. This will clear battery history and will re-calibrate your battery.
[Streak 5 Android Development] _n0p_:
Dude_Virus, thank you.

Download and install one of kernels, published by ltrifonov few posts earlier, one of new patches adresses the screenoff issue you've mentioned.
[Streak 5 Android Development] ahmed45:
_n0p_ thanks bro great rom! found no bugs or any lag great for gaming everything works properly like it should. i was on dj steves 2.4.4 before this someone mentioned your rom great work keep it up. just would like to know if you can help me with ro.media.enc.hprof.vid.bps where to place it in the build.props
[Streak 5 Android Development] Dude_Virus:
Tried it all still doesnt work...the battery reporting just doesnt detect the battery with the entire 4800 capacity... I know for sure its not an issue with the battery because the same battery shows proper charge on android 1.6.. froyo onwards this is an issue... the battery runs down till 1% and if i reset the battery by removing it the % goes to 70%... when i spoke to Mugen they said its something to do with the kernel forcing the device to only detect the stock 1500 mah battery... I asked them for a fix and they said there development team doesnt work on kernel so it was just a fullstop for me.

I have noticed onething. it has something to do with the airplane mode...if the battery reached 1% and i continuosuly use the phone it wud be stuck on 1% unless i take the battery out and put it back in. However if I put the phone on airplane mode when the battery reaches 1% and leave it for like 15 to 20 min.. the battery % again reports 70% to 80 % which is the actual charge left

---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------

Thanks buddy will try those kernels and check and update if I have any issues.

Great Job guys.
[Streak 5 Android Development] roy8846:
Love this Rom :D

Been playing DiRT3 all day on it (see my thread in the apps section)

@nop

Can you maybe take a look at power rom lite and see what fixes white camera screen using chainfire??

Would love to be able to use it :D
[Streak 5 Android Development] _n0p_:
ahmed45, what does that value mean? Anyway, /system/build.prop is the place. Thank you for feedback!

--

Roy, debug.composition.type=mdp :)
[Streak 5 Android Development] _n0p_:
Thank you!

Shipped :)

--

v0.51b - with help of streakOwner kernel is now undervolted. Used his recommended settings in build.prop
[Streak 5 Android Development] streakOwner:
You did a excellent job with the undervolting, thank you mate, now this ROM can do everything as before but using less battery, perfect for daily use.

Now due to the changes in the build.prop and the new way the dalvik cache is build now it is a must to clean dalvik cache before rebooting , right after the zip flash of the cumulative update , and I would advise it as a standard procedure after flashing updates in general to clean partition cache, fix permissions and clean dalvik cache before rebooting.
[Streak 5 Android Development] dsteinberg:
Aha My bb is 514 havent changed it since gs 2.4, is it advised to go through the whole update.pkg with the olleh rom?
[Streak 5 Android Development] _n0p_:
Though TheManii warns about brick problem, i didn't see any reported real life problems.

So yes - flash 406 first. You can do nandroid backup first and restore it right after installing 406 ROM to avoid data loss (that's what i did).

Flashing full 406 ROM will at least settle all low-level system firmware, including BB.

--

My extensive investigation also shows that SD2.4 (before kernel change) is actually some mysterious never seen 405 Olleh ROM, so no worries :)

Only thing that could break your device on low level - is DT.mbn. And since it's never used after installing StreakMod, i think it's safe.

Actually, stock rom flashes DT, then DT makes upgrade. There's no way it could start by itself.

--

Only fun thing i've found on 406 ROM - after installing and BOOTING it can show fullscreen red banner "Visit KT forums" or such. I've almost produced some building material (it was late) :)
[Streak 5 Android Development] dsteinberg:
Ok will follow steps diligently and post later when in back in business. ;)

Ty for your work
[Streak 5 Android Development] dsteinberg:
Umhh i thought i could easily find and download 406 olleh rom and recovery to start but all the places i tried have removed it.....

edit: never mind googled Streak_406_19940_14.pkg and donwloading now from a chinese download site 115.com.
[Streak 5 Android Development] big:
I last update v0.51b, fast and stable, but can't running market?
[Streak 5 Android Development] dsteinberg:
hello, im now on 0.51b. just a quick update on my first findings:

went into init.streak.post_boot.sh to change governor and i find the governor already set to "ondemand". good.

reading streakowner suggestion he has cpu max frequency set to

max frequency 998400

default now i have 1075200. will keep this as it is unless having other problems i will report. im now goinf to modify build.prop as suggested.

thankyou for your great work.

ps. anyone wishes to upgrade to this baby wonder i followed n0p well done guide on

http://xdaforums.com/showpost.php?p=18656924&postcount=2.

To find the 406 olleh rom just google Streak_406_19940_14.pkg there are few chinese sites hosting the download.

edit: bb still GAUSB1A140514 even after flash of update.pkg 406 olleh, any thoughts??
[Streak 5 Android Development] _n0p_:
dsteinberg, are you sure it's not 40614?

Very strange issue...

--

big, can you provide more info on your market problem?
[Streak 5 Android Development] dsteinberg:
Checked again its 40514
[Streak 5 Android Development] big:
My device shows information: sever error!, and i'm try fix here:

www.xdaforums.com/showthread.php?t=1231358

...

(Using Root Explorer;

Download apk to sdcard

mount /system rw

browse to /system/app

remove MarketUpdater.apk

remove Vending.apk

browse back to sdcard and copy the Vending.apk to /data/local/tmp

copy the Vending.apk from /data/local/tmp to /system/app

using permissions action, set permissions on Vending.apk [Owner: Read Write. Group: Read. Others: Read]

using set owner action, set owner to 0 - root, group to 0 - root.

Close and reboot.)

...

but is now it's always FC.

---------- Post added at 10:21 AM ---------- Previous post was at 10:01 AM ----------

I'm had fix ok, market running :)

- Using Titanium freeze update market

- Into settings/applications/all/market> clear cache, clear data and unistall update, restart market> OK

V0.51b than v0.5b 1,5 time :)
[Streak 5 Android Development] _n0p_:
dsteinberg, on your SD card in the LOST.DIR folder you can find some files with numeric names. Find file about 160MB in size and upload it somethere. I'd like to take a look (it's the decrypted 406 update.zip).

--

big, glad you was able to solve it yourself :)

But anyway, will anyone confirm market problem - i so far didn't encounter any.
[Streak 5 Android Development] dsteinberg:
Hello, i found quite a few files into the .lost.dir folder, most of them are over 180 mb except 1 is 154 mb. if thats the file you need heres the link

http://dl.dropbox.com/u/26325204/3565

ty
[Streak 5 Android Development] smnc:
Here is my long promised logcat of the Jorte crash. I never seem to have time when I'm at ky PC, so I grabbed "Save Logcat" from the market.

Here are the main and event logcats

http://db.tt/QoaPbCau

http://db.tt/4XaOEC1j

Also, would a radio logcat from when my streak is booted with the rogers sim help with tracking the bastard down and killing it?

No market problems here and everything is super stable on .51b so far :-)
[Streak 5 Android Development] _n0p_:
Jorte tries to establish parntership with Google, then commits suicide:

Gonna think about it.

And yes, radio log would help.

Maybe recreating your google accounts would help?

It works fine with my both accounts, so maybe Google somehow don't allow Jorte to access your account data?

Also, just a quick suggestion - maybe gTalk interferes? (it's only a not-based-on-anything thought).

[ 11-02 02:22:10.359 153:0xbb I/ActivityManager ]

Displayed jp.co.johospace.jorte/.MainActivity: +12s695ms

[ 11-02 02:22:11.109 270:0x186 I/GTalkService ]

connectionEstablished

[ 11-02 02:22:11.119 270:0x186 I/GTalkService ]

[GTalkConnection.20] connectionEstablished: release wakelock

[ 11-02 02:22:11.119 270:0x186 I/GTalkService ]

[GTalkConnection.20] releaseAsyncWakeLock: clear timer: WakeLock{405a07a0 held=false, refCount=0}

[ 11-02 02:22:11.129 270:0x186 I/GTalkService ]

[GTalkConnection.20] (WORKER THREAD) update account status

[ 11-02 02:22:11.179 270:0x186 I/GTalkService ]

[GTalkConnection.20] (WORKER THREAD) update account status - done, took 53 ms

[ 11-02 02:22:21.929 153:0x179 W/PrintK ]

Binder Thread #(377) sends sig=9 to id.partnersetup(1260)

[ 11-02 02:22:22.119 1651:0x673 W/dalvikvm ]

threadid=1: thread exiting with uncaught exception (group=0x40015608)

[ 11-02 02:22:24.590 840:0x348 I/WidgetUpdateService ]

onCreate

[ 11-02 02:22:24.590 840:0x348 I/WidgetUpdateService ]

onStart 1

[ 11-02 02:22:24.610 840:0x348 I/WidgetUpdateService ]

onDestroy

[ 11-02 02:22:27.800 1651:0x673 W/PrintK ]

johospace.jorte(1651) sends sig=9 to johospace.jorte(1651)
[Streak 5 Android Development] smnc:
Well, Jorte works fine on my Iconia with the same Google account, but I have several accounts, so I can try messing around.

Going to sleep for a few hours, then attack it.

Sent from Vera, my Iconia A500; All dressed up going places!
[Streak 5 Android Development] takodijkman:
Great ROM!

Want to flash, but - stupid as I look now :( - I can't find any 406 recovery image?

The .pkg file was no problem, but the corresponding recovery is not that easy to find!

Maybe someone can point a link?

Really would want (and recommend, if worth any) to use the 406 recovery image, because of all the weird stories with a super-bricked device!
[Streak 5 Android Development] _n0p_:
takodijkman, i've used this one. Haven't made any harm to my device.

--

And can you provide links to that stories?
[Streak 5 Android Development] takodijkman:
Thanks a million!!!

e.g. here on our forum: http://xdaforums.com/showthread.php?p=18826340#post18826340

Everywhere you see 406 Olleh in the same sentence with super-brick or low-level brick.

The truth is that those are mainly assumptions and I don't believe it really. I have also read that there are no real clues. Nevertheless, made me a bit more cautious with this type of ROM :).
[Streak 5 Android Development] _n0p_:
I promise to tell everyone if i receive at least one brick report from trusted source.

--

I've updated first post with links to 406 ROM, but will remove them on legal notice, as i'm quite sure that it's actually a closed beta-test ROM.

--

New quick solution:

If you can't end conversation or press buttons in dialer - it's because you've changed phone orientation with proximity sensor on. Fastest way to "fix" - waive your palm over speaker (where proximity sensor is located) and buttons will be unlocked.

--

smnc, another entry:

[ 11-02 02:25:41.509 153:0x179 I/am_crash ]

[1686,jp.co.johospace.jorte,48708,java.lang.ArrayIndexOutOfBoundsException,NULL,MonthlyDraw.java,861]

Well, is there any chance that Jorte cannot parse/process some entry?
[Streak 5 Android Development] greg9100:
Thanks for the test kernels, testing;
[Streak 5 Android Development] _n0p_:
http://xdaforums.com/wiki/Dell_Streak_5/Flashing_Guide

Look for StreakFlash tool.

Very detailed article here (i've used it, with ,ahem, not too successfull amss hack attempt :) ):

http://forums.whirlpool.net.au/archive/1557150

--

Hi Greg!

Any new ideas? Do you find new kernels suitable for our next release?

--

Dude_Virus, can you ask Mugen what exact part of kernel we should take a look at?

--

Sergei
[Streak 5 Android Development] greg9100:
@Sergei and Team-

Only ideas from me currently-

What if we tried different allocators:

SLUB

or

SLQB patch

I have experimented with SLUB in the early stages with Gkernels project, it seemed promising,

I've also thought about a BFQ patch;

Meanwhile testing Lubo's 4.4.3 build, next the codesourcery
[Streak 5 Android Development] _n0p_:
For me this says that I should pay a visit to Wikipedia :) To have a look at whose "We need your money" banners, of course :)

--

I actually thought about - is swap support really needed? Dalvik manages mem itself, and this might save precious kernel mem timings. Disregard this, if it's already disabled, i'm from Streak, and cannot check right now.
[Streak 5 Android Development] greg9100:
Sergei, We do have swap support in the configs-

I would be one for disabling the support for it
[Streak 5 Android Development] lordmorphous:
Just wanted to say that I got a random reboot with the gc443 kernel. I was in my car at the time and didn't really have a way to pull a logcat for the team. I wasn't using my phone at the time, it was just sitting in the seat next to me when I noticed the Dell logo come up. I have since flashed the codesourcery version. So far so good on it.