yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] madadody16:
Arabic Patch

thank you for replay sir, But no still not fixed, because whenever i try to install it my device hangs and i have to re flash it again.

So can it be included with the next update please?

Because in the new update i can see Arabic in system language but still litters not connected, i love this rom really, its the best rom i had until now, its just missing this part only, so i think its easy for you to fix that with the mew update please.

Big thank For you all.
[Streak 5 Android Development] _n0p_:
Arabic support patch.

madadody16, you could at least do the search :)

--

Source:

http://xdaforums.com/showthread.php?t=1410460

http://blog.devasque.com/how-to-apply-patch/

--

Patch:

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

--

Works, tested. Unsure of other effects.

--

Seems like GPS really stopped working.

If you wish this issue resolved, try to contact developer of patch and try to figure out what change may cause it.
[Streak 5 Android Development] Dude_Virus:
Sergei : i dont feel like being away from DSC.... but the only issue is that it gives the edge issur and wifi issue... I had flashed DSC back in between and had again the wifi freeze issues and the edge switching issues. Longhorn doesnt have those but the perf is slow, the lag etc just takes off the mood.....

For the wifi etc can we have the files and driver etc from longhorn put in to DSC....??
[Streak 5 Android Development] _n0p_:
WiFi/3G interchanging issue is fixed in 1.3 and Connection fixer helps with freezes. More 366 BB makes Wifi work even better in terms of stability.

--

And wifi driver in Longhorn IS from DSC (uses kernel and driver i published for CM7) :)
[Streak 5 Android Development] abauer:
Longhorn is totally a placebo Rom , this is my personal experience, I have tried it too.
[Streak 5 Android Development] jitin02:
N0p sir

I am not able send SMS . In morning I sent one SMS to my mom and till now it's not sent just showing sending........
[Streak 5 Android Development] _n0p_:
I'm absolutely sure it's not an issue with rom.

Check your short message center number, etc.
[Streak 5 Android Development] Strephon Alkhalikoi:
Curious choice of words. Placebo ROM?

Regardless, I tried CM7, running the test 4 kernel while DSC was having its problems with WiFi. There were a few niceties in Cyanogenmod ROMs I had forgotten about, such as the theming engine and the notification toggles. I kept it, not because of those things but simply the fact it runs a later version of Gingerbread than DSC.
[Streak 5 Android Development] abauer:
And which are the good things about being the latest version? as far as I know DSC runs all the 2.3.7 appks that are supposed to be on 2.3.7 only.
[Streak 5 Android Development] Strephon Alkhalikoi:
You didn't answer my question. What do you mean by "placebo ROM"?

As to what's better, that's a matter of opinion. Backporting 2.3.7 fixes and changes to 2.3.3 does make the DSC ROM better, but it's not the same as having 2.3.7 itself. DSC is a fantastic ROM and there's a lot of hard work that has been put into it, but remaining based on a stock ROM I no longer find to be palatable. In simpler language, my preference has changed, and my preference is to be as up to date with my Streak's firmware as possible, without attempting to be on the bleeding edge, which the ICS ROMs currently are.
[Streak 5 Android Development] abauer:
what's better is never a matter of opinion, but touchable facts, as for the ICS, since I can't develop myself, am on the waiting position, until the camera driver problem is solved, and the goods from DSC to be ported to ICS, as for placebo, Google it.
[Streak 5 Android Development] _n0p_:
Guys, I think ROM is a metter of personal preference, that's it.

I'm not a graphician, so most work was put into kernel and i'm very satisfied with result.

All known Gingerbread customs use Phoenix kernel.

Just remember touch screen freeze after call and power button issues, for example.

And i'm not backporting 2.3.7.

Only Dalvik VM is reused, and it's more of "oh, it might work better".

Other changes are almost done from scratch, changing smali code and writing extension scripts. And to make it less personal, all coded options are available to end-user.

Regarding other staff. Keep in mind, that framework resides on mostly closed-source HAL and, most important, framework changes done by Dell are not present on open-source builds, so - audio driver problems, no dock, no hdmi.

And our point is to keep ROM stable, fast and functional.

Have a nice weekend,

Sergei
[Streak 5 Android Development] Strephon Alkhalikoi:
@abauer: "What's better is never a matter of opinion, but touchable facts."

There is a difference between having an opinion and having an informed opinion. I do agree that all opinions should be informed opinions, meaning they should have facts to back them up. However, your characterization of the CM7-based ROMs as "placebo ROMs" I find to be...lacking in that department. You haven't presented any facts to back up your claim. You've said that you have tried them, but have you really used them?

I have, and the only issue I've encountered since switching may have to do with my SetCPU profile settings for sleep. I've had two occasions where, when the Streak is asleep and a call comes in, the lockscreen appears instead of the phone dialer and the touchscreen becomes non-responsive. I have to abort the call using power and call the person back in those cases. Using CM7 settings I can work around the issue, but I choose to deal with it instead.

@_n0p_: I agree that the choice of ROM is a matter of personal preference, and I didn't need to go into explicit detail about it. It was enough that I felt it necessary to switch. I made it a point not to disparage the DSC ROM, because despite switching I still would go back to it if I had no other options available. The few things that the CM7 ROM is missing (dock, HDMI) are non-issues to me simply because I don't have a dock and don't output video to my television. The only real audio quirk is the volume being set to maximum for incoming calls, and there are ways around that as well.

I apologize for using the term "backporting" in referring to the work you are doing and have done on DSC. I had thought that some things other than the dalvik cache were worked into 2.3.3. Would it be safe to say that through the use of code changes and scripts you have incorporated many of the bug fixes changes that 2.3.4 - 2.3.7 have made such as improvements to the camera, battery life, and video chat support?
[Streak 5 Android Development] abauer:
I am not gonna feed you in here anymore, PM only.
[Streak 5 Android Development] Strephon Alkhalikoi:
I never got an answer to my initial question from you to begin with so why would I waste my time PMing you regarding an opinion you cannot back up with facts?
[Streak 5 Android Development] Lucifer4obg:
_n0p_ my friend it was nice jurney ...

I'm about to switch phones and I wanted to thank you. I'm using the DSC for I don't remember how long and it was wonderful. I came here when the support for ginferstreak was droped and this was amaising ride. Thank you.

If I ever can help, don't hasitate to contact me.
[Streak 5 Android Development] jitin02:
U must be a lawyer
[Streak 5 Android Development] _n0p_:
Have fun!

I think placebo in this case means "contains no system changes that could make anything better".
[Streak 5 Android Development] Strephon Alkhalikoi:
@_n0p_: Comments like "placebo ROM" shouldn't be made unless the person making them is prepared to explain themselves. By making such a comment, he directly or indirectly insulted everyone on this forum not using DSC, in effect questioning their choices. While I understand the sentiment given the high quality of the DSC ROM, it is no one's place to question the choices of another, regardless of what we may think.

@jitin02: I'm no lawyer, but do editing for a role playing game company. I spent a long time on a forum where this type of comment was common, and learned that attacking the argument is more effective than attacking the person making it.
[Streak 5 Android Development] _n0p_:
Oh I see. So instead of making your own point, you started trolling. Good enough.
[Streak 5 Android Development] Mazensahlieh:
The plus point for 2.3.7 for me was the themes and working GPS with Arabic weather the rom supports Arabic natively (CM) or by patching (MIUI). Other than that DSC is waaay better..having nop for sure.
[Streak 5 Android Development] mokokawi:
ive been using DSC Rom for awhile now....im on .72 with a baseband of 406.....runs great.if i want to install 1.3 pre 3.....is my bb ok...or do i have to put 366 on...ide like to jhst leave 406....and wait till a good ics rom is avaible....i tried the ics out now....and it ran....even though slowly.....but i need data and wifi tether,so waiting for that......i like my current DSC just fine,but i do like the new ics themes in thenewest build
[Streak 5 Android Development] deysmacro:
if nothing wrong and all working... maybe you dont need to do anything... that what i would say...

we all change bb to 366 because we had problem with current bb... so.. if your current working like it should ... again... dont do anything.. :)
[Streak 5 Android Development] _n0p_:
Back on subject. I investigated autobrightness a bit further.

It actually contains six different tables.

What would you guys say about alternate, lower level autobrightness?

For example, i'd love to have lower level at about 15, so night reading would be comfortable.

As this change will be in kernel, it will affect all Phoenix kernel releases for good.

--

366 has lower amplification levels for voice, so if you lowered them with DSC Gain, you might want to increase them back.
[Streak 5 Android Development] deysmacro:
autobrightness level? that would be good in my opinion... :good:
[Streak 5 Android Development] TiGuy82:
Why not? ;) Go for it!
[Streak 5 Android Development] salvator83:
I'm agree on this. Yes, _n0p_ , go for it..:good:..
[Streak 5 Android Development] _n0p_:
I'm currently reading datasheet for our display, kindly provided by hPa.

It appears we have quite a complex piece of hardware here.

Autobrightness is fully hardware controlled, but levels/hysteresis can be set manually.
[Streak 5 Android Development] deysmacro:
dont it pretty much the same like in cm7? something could be use as reference there..
[Streak 5 Android Development] _n0p_:
I'm not sure if i've got you right.

To simplify, CM is just an AOSP extension (mostly framework), so i don't get what it has to do with autobrightness :)
[Streak 5 Android Development] deysmacro:
i see.. so 2.3.3 and 2.3.7 is not that related.... :angel:
[Streak 5 Android Development] _n0p_:
Let's just say that Dell patch enables autobrightness functionality on stock ROMs.

It has nothing to do with Android version.

You can take a look in DSC 1.3 /system/etc/dsc.enable_lightsensor.sh and /system/etc/dsc.disable_lightsensor.sh to see how it can be done via scripts.

--

First check for brightness:

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

Lowered two first levels, unsure if it has effect.
[Streak 5 Android Development] abauer:
I tried the zip , but truly can't see any difference, it has to be measured maybe with some other smartphone the lux being emitted by the LCD, with naked eye, really I can't tell.
[Streak 5 Android Development] _n0p_:
Thank you. What I personally experienced - somehow slower reaction for changing ambient lighting.

Ok, gotta read further.
[Streak 5 Android Development] _n0p_:
Well, further tests - on Google Plus video chat initial brightness actually drops alot :)

So it's just to find the actual table, used in UI mode.
[Streak 5 Android Development] abauer:
how do you measure brightness ?
[Streak 5 Android Development] _n0p_:
Without tools, initiate simple videochat in Google+.

You'll see very dimmed screen.

--

Still up to me to find out how the whole thing works.

We have different modes and tables:

MSG2("(5400=%02X 5600=%02X) Backlight Mode = %s",reg5400,reg5600,
mode==1? "NORMAL":
mode==2? "LABC":
mode==4? "CABC_UI":
mode==5? "CABC_STILL":
mode==6? "CABC_MOVING":
mode==7? "LABC_CABC_UI":
mode==8? "LABC_CABC_STILL":
mode==9? "LABC_CABC_MOVING":"INVALID"

Backlight values are initiated by stage value of 1, using this tables (0-5): (57xxxxxx is the backlight level setup for our matrix)

{ 0x57000000,0x57010034,0x57040000,0x57050090,
0x57080000,0x570900E0,0x570C0001,0x570D0070,
0x57100003,0x571100FF,0x57020000,0x5703002A,
0x57060000,0x57070083,0x570A0000,0x570B00D6,
0x570E0001,0x570F0030,0x57120003,0x571300FF,
0xFFFFFFFF },

{ 0x57000000,0x5701004A,0x57040000,0x5705009A,
0x57080000,0x570900FC,0x570C0001,0x570D009A,
0x57100003,0x571100FF,0x57020000,0x5703003A,
0x57060000,0x5707008A,0x570A0000,0x570B00E3,
0x570E0001,0x570F0055,0x57120003,0x571300FF,
0xFFFFFFFF },

{ 0x57000000,0x57010060,0x57040000,0x570500AB,
0x57080001,0x57090020,0x570C0001,0x570D00D5,
0x57100003,0x571100FF,0x57020000,0x57030042,
0x57060000,0x57070095,0x570A0000,0x570B00F8,
0x570E0001,0x570F0080,0x57120003,0x571300FF,
0xFFFFFFFF },

{ 0x57000000,0x57010060,0x57040000,0x570500BC,
0x57080001,0x57090042,0x570C0002,0x570D000A,
0x57100003,0x571100FF,0x57020000,0x57030045,
0x57060000,0x570700A0,0x570A0001,0x570B0020,
0x570E0001,0x570F0092,0x57120003,0x571300FF,
0xFFFFFFFF },

{ 0x57000000,0x5701006A,0x57040000,0x570500D2,
0x57080001,0x57090058,0x570C0002,0x570D0045,
0x57100003,0x571100FF,0x57020000,0x57030045,
0x57060000,0x570700A9,0x570A0001,0x570B002C,
0x570E0001,0x570F00C3,0x57120003,0x571300FF,
0xFFFFFFFF },

{ 0x57000000,0x5701006A,0x57040000,0x570500E2,
0x57080001,0x57090075,0x570C0002,0x570D004A,
0x57100003,0x571100FF,0x57020000,0x57030045,
0x57060000,0x570700B6,0x570A0001,0x570B004B,
0x570E0001,0x570F00E6,0x57120003,0x571300FF,
0xFFFFFFFF }
};
[Streak 5 Android Development] abauer:
I am using "Holo locker" as lockscreen , but after reboot I don't see it directly upfront, is any way that I would be presented directly with that locker after rebooting ? it is much cooler than the default one.
[Streak 5 Android Development] jitin02:
kindof done with DSC

Hi n0p,

The rom is starting to act weird.

the wifi can be turned on, try'd wifi fixer on and wifi fixer off. bt no success.

everytym i reboot it gives me screen to add my gmail account, everytym i have to add it again and again.

Cant use video camera, as soon as hit record it say insert Sdcard. [my sdcard is empty, formatted it already bt still say insert sdcrd]

cant take pic as its the same it force closes evry now or then

:mad::mad::mad::mad:

help me solve this , as i dont want move to other rom/or stock, there is no better rom than dsc but it makin me mad
[Streak 5 Android Development] _n0p_:
WidgetLocker works fine. It's up to app dev to make it work normally.

Disable UV/Overclock first.

Next, check your SD card and connectors on Streak.
[Streak 5 Android Development] jitin02:
I don't use over clock. I am always on 998

And reg SD card. Except camera all other apps read it
[Streak 5 Android Development] _n0p_:
Give me the error log, so i could determine where problem is.
[Streak 5 Android Development] abauer:
Thank you n0p , widgetlocker lockscreen is much better and even customizable, very pragmatic indeed.
[Streak 5 Android Development] ogel2:
well, after almost 2 weeks trying this 1.3 i decided to go back to 1.2. seems more stable and faster in my streak. goodwork anyway n0p :good:

thx
[Streak 5 Android Development] abauer:
dalvik.vm.startheapsize=40m

dalvik.vm.heapsize=48m

I was in same situation as you, until I changed this lines on /system/build.prop
[Streak 5 Android Development] _n0p_:
I guess i should extend DSConfig :)

For me, increasing Dalvik heap actually makes Streak respond faster to task switching.

--

Updated DSConfig:

Configurable Dalvik VM heap.

http://n0p.8bit.fm/streak/updDSCv1.3-DSConfig.zip

Mirror @ khoacoi:

http://www.littlemaruko.com/Nopteam/updDSCv1.3-DSConfig.zip
[Streak 5 Android Development] uluvali:
n0p,

What settings are you using for your start heap/heap?
[Streak 5 Android Development] _n0p_:
Currently testing 40\80. So far so good. :)
[Streak 5 Android Development] p_razzi:
Defaults seem to be 64/96. Would you suggest 40/80 is a better setting?

If you're going to update DSConfig again, could you add a switch to keep capacitive lights on?

Thanks,

J.
[Streak 5 Android Development] _n0p_:
Sorry, got out my head, will fix.

Stiill think 64/96 is good for me, but if you have alot of background apps... I'd count 5-6 mb per one background app.
[Streak 5 Android Development] ogel2:
tried that already. but that didn't improve my streak performance. :(

nice..!! :good:
[Streak 5 Android Development] _n0p_:
Looks like dalvik.vm.startheapsize actually has no effect. I will remove this option in future releases.
[Streak 5 Android Development] abauer:
I have trouble pairing with iPhone devices but not any problem at all with android ones, is there any way to solve this ?

thank you
[Streak 5 Android Development] jitin02:
IPhone always sucks in pairing
[Streak 5 Android Development] abauer:
so not any kind of walk around either ?
[Streak 5 Android Development] jitin02:
If u r jailbroken on iPhone then try finding tweaks from cydia for this
[Streak 5 Android Development] _n0p_:
Got no iPhone to test, sorry.

--

Further testing Dalvik memory - looks like 24m is enough for all apps i use (16m makes Dolphin crash from time to time)
[Streak 5 Android Development] deysmacro:
i think gb standard is 32 :)
[Streak 5 Android Development] _2bad4u_:
I try to pair my streak with a friends ipad3 and i always get error. I'm runnin miui.
[Streak 5 Android Development] deysmacro:
please take note that ipad / iphone is really selective when trying to pair with other phone... not just android phone only... apple have made the device to behave that way by default...
[Streak 5 Android Development] _2bad4u_:
Yes i know, just like blackberry.
[Streak 5 Android Development] _n0p_:
Nope, just 16m.
[Streak 5 Android Development] besony:
Go launcher n Go Dialer and 90~MB free ram always!

Guys,

I have been using Go Launcher Ex and Go Dialer for quite some time now.

But- I see- after like a month of usage of ROM - there is way too much lag while going to Launcher (home) or the Dialer itself - for example - after a call or after exiting any application.

I am using 1.3 DSC rom since quite some time ( after I shifted from CM 7.2 - couple of months back ).

I see the snappy-ness of the ROM decreases a lot after like 2-3 weeks of clean install.

I don't install tonnes of apps now - I have like 20-25 apps tops. ( most of them to the SD card as well )

I use - advance task manager - which shows me - after a day of use - I am always at 90ish MB free like all the time !

It comes down to 30-odd mb free at times.

Also- done battery wipes and calibration -

But- with APN ( 2G ) on all times, and about 60-70 mins of calls daily, and major use of Watsapp - My battery drains at >15% per hour!

Is everybody getting similar perfomance / battery life ? ( +/- depending on the usage? )

I think (particularly) my Streak is gonna die without a warning! :crying:

____

I am also trying to apply fixes that n0p and other guys release.

Dalvik set at 40/48 then 64/96 and all possible combinations -

( but - that looks like placebo too! :/ )

____

Any help or pointers?

( I was confused - what thread to put this in - but since I am following this thread- thought of getting inputs from here only )

Thanks a ton for the wonderful work people!

especially n0p

Cheers!

Sony.
[Streak 5 Android Development] _n0p_:
I think it's ok for stock battery.

And of course it wears out with time.

--

Also - productivity depends from number of background apps.

Check with autostarts, a lot of apps like to launch on connectivity change, etc.
[Streak 5 Android Development] besony:
Comments on free ram / launcher / dialer ?

Any comments on free Ram? being so low ( or this is common with you too? )

Any better launcher + dialer combo ?

Also - any particular apps you are talking about?

@Maps- I take care to Force-stop it every time I open it.

Any other apps you are hinting at?

I just want lightweight + fast !

Looks wise - my requirements are very minimal now!

Thanks,

Sony.

P.S. Just forgot - Sometimes - I go into some app ( gmail, browser, whatsapp..) - and I have to come out and go in again !

first time opening an app - the touch may or may not work !

( and ^ that is random occurence ).

But- definitely happens after I wake the device after more than an 30 minutes or 1 hour.
[Streak 5 Android Development] _n0p_:
Free ram doesn't mean much for Android.

Check with System Panel or similar - how many apps have you got in background/running/etc? Do you see there something you don't want or even have no idea why it's there?
[Streak 5 Android Development] abauer:
having free memory is android doesn't make much sense tha way android claims the memory stack . it seems it is just a matter of what kind of app we use mostly, dolphin is a memory hog, so those that use dolphin should use high number on the heapsize, or games too, I mean big games.

good that n0p is finally throwing himself into DSC-ics arena, thank you n0p.
[Streak 5 Android Development] deysmacro:
you might want to try to wipe cache and wipe dalvik cache by the way...
[Streak 5 Android Development] bluhound:
Recently I've been getting Wifi errors again. The wifi icon shows green then later it becomes white. Disabling Wifi then re-enabling it works but it will randomly stop working again. I'm using DSC 1.3 with 366BB.

The odd thing is that even after I tried resetting everything back to factory default, clear dalvik, cache, data etc and tried using it without installing any extra apps... the problem is still there.

Out of curiosity, I tried Longhorn 2.9.1. Same problem. Anyway, I did a logcat when the error happened.

_n0p_, I removed the logcat attachment and PM'ed you instead.
[Streak 5 Android Development] abauer:
@n0p , could you please compile a kernel that ignores the baseband for the ICS, dunno what kind of effect the old bb might have on the ICS builds, hope better, please look a bit into the camera lib for ICS as the development is totally stuck over there, without much progress seen for over a month already.
[Streak 5 Android Development] deysmacro:
i use 366bb and it is working great.. just the led panels keep blinking every few minutes .. lol.. :D
[Streak 5 Android Development] _n0p_:
Guys, i'm trying to resolve camera issue (our libcamera is linked to libui functions that are not present in ICS, and you know that Qualcomm don't release much. Dell could request drivers as vendor, bu we can't) and absolutely not sure if i succeed (will most probably fail). Streak is almost useless for me without camera, so don't expect anything.
[Streak 5 Android Development] abauer:
so if it is a matter of writing the drivers , it is impossible, since none did it before for the streak , so those skills are vastly lacking in the community, but trying other libs, form devices with same hardware as ours , or even there it is just easy to say but not easy to do ?

do you intend to ask Qualcomm for the ICS drivers, in case they don't have such , even they might be willing to give is also an opportunity.

The gingerbread DSC lacks really nothing now, so please keep an eye on the ICS development.

thank you
[Streak 5 Android Development] _n0p_:
I can't do much alone.

We have two cameras:

ov5642 (main)

ov7690 (vga)

--

Closest possible (at least what i've found) is ZTE Blade that has ov5642 and ov5640(?) and it's libcamera has support for ICS.
[Streak 5 Android Development] deysmacro:
i dont care much for front camera if the main is working... also front camera is low quality.. so it is not a big deal unless it is main camera :o