yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] lordmorphous:
@_n0p_

When I get a couple days of no work and no family commitments, I plan on trying my hand at adding a reboot option to the power menu. Would you be interested in that for implementation in a future release?

@Itrifonov

Your English is better than a lot of us "native speakers"...lol

---------- Post added at 04:00 AM ---------- Previous post was at 03:54 AM ----------

I've been using your dhd.ko since shortly after you posted it. Unfortunately, right after that I had to leave for work and home is where I experience the problem. I 'think' I received some notifications while on WiFi, but was busy with other things at the time and am not sure. I don't really care if I can ping my phone when it is asleep, it was the only test I could think of short of sending myself emails or Google Voice texts. Hopefully by Friday I can really test it out. In the meantime though, I have gotten my 3gMicrocell from AT&T working good and get a strong data connection to it when I'm at home. So worst case scenario, I can just set WiFi to turn off with screen off and everything will still work. I would just rather use WiFi if I could.
[Streak 5 Android Development] _n0p_:
lordmorphous, that would be great!
[Streak 5 Android Development] ltrifonov:
Unfortunately, cifs.ko crashes my streak...

it will take more time :(

tun.ko is working fine,

slow-work.ko also loaded fine (it is still useless)

but both cifs.ko, and older smbfs.ko need deeper investigation

EDIT:

if we know the kernel builder it will be easier, I am not sure if this ".config" is actual one (/proc/config.gz), or if kernel sources are same as mine? (mines are from dell opensource 4.05)
[Streak 5 Android Development] _n0p_:
I'm 99% sure, that 406 kernel is the same 405 with further port bugfixes.
[Streak 5 Android Development] _n0p_:
Well, it can make you concider buying another Dell product :)
[Streak 5 Android Development] Vennesch:
Basebands and EXT4

Hi two questions

- Is it wise to do the flashable format to EXT4 (I recall it was on the first page a few months ago, some people reported that it works faster...)?

- After flashing 407, DSC 1.0 and 1.6 again, which baseband should I use (which is better)? The one that is included or 369?

Thanks in advance
[Streak 5 Android Development] _n0p_:
I definitely don't recommend changing FS type.

--

As for BB - choose yourself. I'm happy with 369 (but same was with 366).

407 has overloaded volume levels and newer RPC API, but I think we won't get a new 4xx BB ever.
[Streak 5 Android Development] Dude_Virus:
Flashing the new kernel seems to giving some issues when it comes to network switching. Until i flashed the kernel switching from wifi to mobile data and vice versa was smooth and instant however after flashing the kernel when i tried to switch from wifi to mobile data the edge took ages to come up and when it came it was having no data ( white icons ) . I had to do an airplane mode 2 to 3 times to get that working. i tried this multiple times but the same result. To test it I flashed the 1.7 diff 5 again and the issue was resolved in that. So i again flashed the boot.img kernel via terminal emulator and the problem came back regarding network switching.
[Streak 5 Android Development] Rocker19943:
N0p, could you please disable the sound of camera while focusing the image...
[Streak 5 Android Development] Dude_Virus:
Sergei

There is still an issue with the dialer, between frequent calls its a big delay...i called my bro but as there was some network issue i had to try again so the second time when i pressed the green call button from the call log it didnt start dailing the number immediately. it stayed on the call log screen and i was able to tap on the dial pad or the contacts tab or the favourites tab on the top but when i tried to tap again on the green call button nothing happenned. finally after 20 sec it started to dial again. This issue is there since the 1.4. How can this be resolved as earlier this was never a problem. I am not using any such extra apps or background services that the dialer is having memory issues.
[Streak 5 Android Development] nadastry:
is it possible to install the phoenix kernel in the latest Longhorn?
[Streak 5 Android Development] _n0p_:
Well, again, i think that's a memory issue.

Longhorn is CM7. There's a thread for CM/MIUI Phoenix kernel releases.
[Streak 5 Android Development] nadastry:
Sorry :(

Havent seen that.

I posted my question there...:crying:
[Streak 5 Android Development] Dude_Virus:
Sergei but if it was a memory issue then everything else also should have got affected, y is it that only the phone app and that too between dialing calls is the problem. And this issue is not just happenning on my streak, my managers streak which i updated to 1.4 also has the same problem. Two phones having the same memory problem isnt that unlikely. Moreover if there was a memory problem then the other tabs on the top like the dialer , call log , contacts , favourites should also be non accessible. everything works except for the dialing part. Once i press the green telephone icon to start the dialing process there is a huge delay before the actual dialing starts. I today checked by using a stopwatch.. it took 22 seconds from the moment i pressed the call button until the screen which shows that it is dialing the number came up. But during those 22 seconds i was able to navigate everything else. I have tested this with UV - on / UV - off . conservative governor / performance governor . I have tried this with almost everything frozen with titanium backup so that there are no background services running. I checked with system panel light and free memory showed me 182 mb and still that issue occurred.

BTW that wifi problem for which i emailed you the logs was resolved by flashing the diff 5 twice. After that the wifi was stable with the following settings 5 sec timeout and wifi pm - off/off . 14 hours being on wifi there was no freeze and the device went into a deep sleep, out of those 14 hours it was in deep sleep for 9 hours so its good. For me the following wifi PM settings cause issues FAST / MAX, OFF / MAX and MAX / MAX .

Just one issue and that is i have to open dsconfig everytime i turn on the wifi to re set the values as even with connection fixer as normal when wifi is turned on it seems it doesnt take the 5 sec timeout because even after 3 hours with the phone being off the deep sleep was none. But when i went ahead and opened ds config and re clicked the set now button and saved everything went back to normal as i tested by keeping the phone unused for 1 hours and deep sleep showed me 52 min. Can something be done for this ?
[Streak 5 Android Development] rydroid:
OK every time I use volume keys the phone resets. Reflash. Factory wipe nothing stops it for long.
[Streak 5 Android Development] Dude_Virus:
Noticed another issue, when a call comes in the gprs disconnects but after the call finishes and the gprs connects back everything else works but the google talk or gmail as gtalk states that network is current unavailable. However at that point I am able to browse and use other messengers etc. Even after waiting for a couple of min it still says the same and the E icon is white. I have to do an airplane mode to get that resolved. And this happens everytime the call comes and gprs disconnects. Any ideas as to how to fix.

Also when i reached home and tried to switch on the wifi it just didnt want to switch on. Tried airplane mode but no go and with the wifi refusing to switch on even the mobile data didnt have any data connectivity and this all led to a fast battery drain making the phone hot. Finally had to reboot to get the wifi working
[Streak 5 Android Development] _n0p_:
Give me output of

su

getprop ro.build.DSC_CONFIG_VBEEP

Phone:

Let's check it this way:

comment

renice

command (with # symbol) in init.streak.post_boot.sh and dsc.samrt_reassoc.sh

Wifi timeout:

After boot -

output of

cat /sys/module/dhd/parameters/dhd_watchdog_ms

and

getprop ro.build.DSC_CONFIG_WIFITIMEOUT

GPRS always disconnects on call, though i think it should be possible (provider dependent) to keep it.

--

Regarding all other stuff:

Give output of

ps | grep -c app

It's number of running apps.

(i have 29 running apps right now), 83MB free, 32MB Dalvik heap.

--

Reverting kernel values, so conservative behaves the old way:

echo 70 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold

echo 30 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold

echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_down_factor

echo 128000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo 20 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step

echo 128000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/ramp_freq

--

Camera focus beep - there's a call to tone generator in AutoFocusCallback. Can be disabled by altering code.
[Streak 5 Android Development] _n0p_:
DSC v1.7

DSC v1.7

--

Cumulative, flash over any 1.x version.

--

Kernel, framework hacks, updated DSConfig.

Volume Beep and vibration configurable (affects Volume panel when setting volume with keys).

Scheduler (on ext SD) configurable. Can be set on the fly with DSConfig. Use BFQ for streaming media (hunderteins find).

Same for CPU kick.

Better portrait mode (hard to describe, now you just have to enter Settings, fo example, to fix it in portrait). More, this can be set on the fly now.

Conservative governor hacks - higher sampling ratio, introduced ramp_freq (jump to 576000 by default to reduce lag, took the idea from SmartassV2), retuned parameters.

WiFi driver watchdog configuration to replace hPa's patch. Note - if you set this value and then lowering it - reset the WiFi (off/on) so the setting will take effect faster as it's polled on watchdog timer. Needs Connection fixer set to normal. 5 sec timeout should solve most of WiFi freeze problems.

Removed hPa's driver from DSConfig.

WiFi driver Power Management configuration. Needs Connection fixer set to normal.

Logic of calling hidkbd changed to increase stability.

SmartassV2 governor added to kernel (576000/245760). Work unstable for me.

UV for 128000 is set to 925mV.

--

http://n0p.8bit.fm/streak/updDSCv1.7.zip

mirror@khoacoi:

http://www.littlemaruko.com/Nopteam/updDSCv1.7.zip

--

PDroid patch for this release:

http://n0p.8bit.fm/streak/PDroid-v1.31-updDSCv1.7.zip

mirror@khoacoi:

http://www.littlemaruko.com/Nopteam/PDroid-v1.31-updDSCv1.7.zip

For faster flashing flash PDroid right after update, so Dalvik cache will be rebuilt only once.

(To revert simply flash updDSCv1.7.zip again).

--

Have fun,

Sergei
[Streak 5 Android Development] jamo59:
jamo59

Hello there!

I would like to ask if the internal 2GB card is bad and should be replaced if the format for format and in what program?

This error message is written to the phone: This power in cache: recovery / log No space left on device!

: Sírás:
[Streak 5 Android Development] _n0p_:
It's not bad it seems.

While in recovery, connect Streak to PC

Issue

adb shell

You'll get to device shell.

Issue

rm -r /cache/*

This should clean /cache partition
[Streak 5 Android Development] Crinos512:
_n0p_, I am having a crash on the latest 1.7 update... specifically when trying the Flashlight function of the QuickPanel. This results in the entire notification bar disappearing for a short time.

I also have the 'Notification Toggle' App installed and the Flashlight function uses the LED as expected.
[Streak 5 Android Development] _n0p_:
Are you using Pdroid patch?

Would you provide your log after SystemUI crash?
[Streak 5 Android Development] Crinos512:
yes, and yes...

View attachment flashlight.txt.zip
[Streak 5 Android Development] _n0p_:
Crinos512, strange:

10-29 11:59:10.088 I/dalvikvm( 1493): threadid=4: reacting to signal 3
10-29 11:59:10.088 I/dalvikvm( 1493): DALVIK THREADS:
10-29 11:59:10.088 I/dalvikvm( 1493): (mutexes: tll=0 tsl=0 tscl=0 ghl=0 hwl=0 hwll=0)
10-29 11:59:10.088 I/dalvikvm( 1493): "main" prio=5 tid=1 NATIVE
10-29 11:59:10.088 I/dalvikvm( 1493): | group="main" sCount=1 dsCount=0 obj=0x4001f198 self=0xce48
10-29 11:59:10.088 I/dalvikvm( 1493): | sysTid=1493 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=-1345006496
10-29 11:59:10.088 I/dalvikvm( 1493): at android.hardware.Camera.stopPreview(Native Method)
10-29 11:59:10.088 I/dalvikvm( 1493): at com.lidroid.util.LedController.off(LedController.java:35)

10-29 11:59:10.088 E/ActivityManager( 1411): ANR in com.android.systemui
10-29 11:59:10.088 E/ActivityManager( 1411): Reason: Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x40000004 (has extras) }

I wonder if this because camera is held open by something.
[Streak 5 Android Development] Crinos512:
hmm... is it possible that the QuickPanel app is getting in it's own way (possibly hanging on a perceived double tap)
[Streak 5 Android Development] _n0p_:
Unlikely. Looks like camera doesn't respond in some requred timing.
[Streak 5 Android Development] Dude_Virus:
I did not get this part where you have mentioned comment renice etc.

---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------

As far as GPRS is concerned I am aware that it gets disconnected when there is a phone call. The issue which I was pointing at was that once the call is finished the GPRS should connect back, instead it doesnt connect back and shows white icons and no data connectivity. I have to constantly try airplane mode sometimes even upto 4 times to get it back working or have to end up rebooting the device. I can relate to this because even today when i tried switching to mobile data from wifi it never switched to mobile data. White E icon no data connectivity, airplane mode didnt wanna work and even checking the box to enable airplane mode never enabled airplane mode and the option grayed out. I had to then reboot the phone for the mobile data to work properly.

I ran the ps | grep -c app in terminal and it returned with a value of 31. Checked the system panel light and the free memory is 85M but if I go to settings -- application -- running services ... the free memory there shows 150 MB.
[Streak 5 Android Development] jamo59:
jamo59

Thank you for your answer!

But unfortunately I can not do this because I bit the computer. I'm trying to ask for help.

(Or if you did, that in Private describes exactly what to do, then maybe we could!)
[Streak 5 Android Development] _n0p_:
jamo59, isn't there a menu in recovery for clean/wipe cache or format cache partition (not data, only cache) ?
[Streak 5 Android Development] jamo59:
Hello!

The fast boot and recovery work.

I manage to do that to my 407.pkg is only 4x what I started with no error message normally been installed! After he returned to 3.2.8. 1.7 DSC and the recovery are now working properly! Now everything is ok!

3.2.8 The recovery in vain I started deleting the cache was not willing to move on after the dell logo! (Deleting the cache on the computer I could not do it!)

Fearing I describe is probably a software update caused the problem because it would not install the update and it wrote that there is not enough space on the card and delete program! This is not true because there was plenty of space. Then he started to turn off by itself, and even restarted my phone factory reset is done automatically. And then I just got the Dell logo.

Köszönöm a segitséget!: Good:
[Streak 5 Android Development] Dude_Virus:
Sergei earlier when i used to charge the phone with it being off, I used to get a battery icon. However now since I have flashed the 366 BB it doesnt show me that icon anymore. I just noticed it as the phone ran out of juice so i connected it to the charger but the battery icon never displayed on the screen. Just the 3 lights lit up and then they too vanished. What needs to be done to fix that.

Also the screen calibration screen is different than earlier. I have tried flashing the 406 BB but still the same. Any ideas..??

Remembered one more thing that I got an error while flashing the 406 BB using your flashme tool and I had to flash it manually.

DSC ROM Quick flash tool by n0p and streakOwner.

--

Welcome!

This script will update AMSS and DSP to version 406,

and flash StreakMod Recovery.

--

Do following steps:

Power-off Streak

Connect it to PC

Start it.

After DELL logo appears, press and hold Camera button.

Wait until "Waiting for SD detect..." message dissapears.

Select FASTBOOT.

--

When you see FASTBOOT_MODE message, simply

Press any key to continue . . .

Flashing AMSS...

sending 'amss' (15780 KB)... FAILED (data transfer failure (Too many links)

)

finished. total time: 0.032s

Flashing DSP...

< waiting for device >
[Streak 5 Android Development] _n0p_:
Kartikaye, I think some area in nand is corrupted.

Have you used QDLtool or similar?

I used QDL after some tests on AMSS :) and must say I like some aspects of older fw (other than bb/dsp, sure). For example, i'm entering and navigatin recovery without any button trouble.

I'd suggest running your one with QDL (streakflash).
[Streak 5 Android Development] Dude_Virus:
I have used streakflash last when i had an issue with my ext sd card not getting detected. At that as I was trying a couple of things the phone did not somewhat want to boot after I had installed clockworkmod. So i read about streakflash, it had got me back to a point where I was able to atleast get to the recovery and i then had my ext sd card detected. So i flashed DSC back again.

One thing though when I had to do this process of QDL i did not find sufficient documentation and had issues doing it for example it not working with some version. Then driver issues and it not completely flashing the stock rom. Do you have any documentation on it.

Although manually flashing the BB using the commands work.
[Streak 5 Android Development] _n0p_:
StreakFlash doesn't flash the system partition and it's good because it leaves ROM unaffected.

It just reverts all low level fw to 305 version.

So after StreakFlash you simply have to update bb/dsp.
[Streak 5 Android Development] chriscullen42:
Some issues with 1.7

Well I took the plunge a few weeks back and installed DSC 1.5 over my SoftBank 369 ROM. All was fine, except I get a WiFi freeze (the only cure I found was to reboot) from time to time but other than that it is fast, smooth and stable.

I decided to put 1.7 on as this seems to have addressed the WiFi issue - but alas, I found my device became less stable, with several random reboots occurring since. I tried enabling the UV option, which seemed to make no difference to the reboots, so in the end I have Nandroid restored back to 1.5.

If it will help I am happy to put 1.7 back on and send any logs over to help pin down the issue - mind you, someone will need to hold my hand as I have not done that kind of thing before :)

Please do not read this as a negative post, I am absolutely blown away with DSC, it is a huge improvement over any stock ROM and the WiFi issue is not a big deal. It never ceases to amaze me how well these roms work when you consider this is a product of very few people's efforts fitted in around their busy lives - so a huge thanks to them all and especially _n0p_

BTW: To install 1.7 I did a Dalvik cache wipe, cache wipe then installed 1.7 then another Dalvik and Cache wipe then a fix permissions.
[Streak 5 Android Development] _n0p_:
chriscullen42, i like reports :)

Say, are those reboots in some way reproducable?

Settings that may affect stability:

CPU kick when on (should make system respond faster, should not have negative effect, but..)

Connection fixer when Aggressive (may behave incorrectly, but Normal should work fine.)

UV (System may freeze or reboot with UV enabled)

SmartassV2 set as CPU governor.

Reniced Phone process (renice can be commented out in /etc/init.streak.post_boot.sh and /etc/dsc.smart_reassoc.sh)

I agree that i took a bit more experimental path since latest releases, but it's how it keeps me interested :)

I test my work on my device, and as we know so far, every Streak is somewhat different from others, so what works for me may bring instability for others.
[Streak 5 Android Development] chriscullen42:
As far as reproducing the fault, it takes a while. I noticed when playing an audiobook via audible the reboot happens about 30 mins in. I left the streak alone last night and it did not reboot for over 8 hours, then half an hour into playing the audibook this morning it rebooted again. I have never changed the DSConfig settings, apart from enabling UV - which made no difference. All the other settings were CPU Kick off, WiFi Fixed Normal. I did not look to see what governor I had in place - sorry :(

Maybe I'll keep an eye on this forum and see how things progress - if you can hint that changes may help me - I'll roll it back on and let you know how it goes. Once again, thanks for all you hard work.
[Streak 5 Android Development] _n0p_:
Do i get it right that reboot happens on using WiFi for a long (over 30 min) period of time?
[Streak 5 Android Development] chriscullen42:
I don't think it's to do with WiFi - the time it rebooted I was using Audible whilst driving, so I had no active WiFi connection and Audible works from a local cache - so makes no use of any network connection. I had no other apps actively using WiFi or any connection at both times.

A further bit of information. After the phone rebooted when I was driving home, I left it alone for the remainder of the journey which was about 25 mins. As i was getting out of the car, the phone rebooted again. At this point, a WiFi signal would just have come into its range, as when I park the car my home WiFi becomes available. I then only used the phone occasionally to view emails, but did not use it for playing any music/podcasts/audiobooks etc. During this time I did download emails and podcasts. In the evening I then played a podcast for about 10 mins before unplugging the headphones and then going to sleep. In the morning the phone was fine and had not rebooted as the podcast player was still open when I unlocked. I then drove to work and started playing the audiobook, after about 30 mins the phone then rebooted.

I am not aware of any WiFi hotspots anywhere along my route to work and I have not noticed any appearing on the phone in the past, however that is not to say some are present or not.

I hope this helps!
[Streak 5 Android Development] _n0p_:
It sure does.

If you'll feel like testing 1.7 again - would you do the following:

Disable WiFi manually before driving.

Even more help would be from issuing in terminal emulator:

su

logcat -v time -n 3 -r 100 -f /sdcard/dsc.txt

Leave terminal emulator running.

This will log everything on SD with names dsc.txt and dsc.txt.1, dsc.txt.2, dsc.txt.3

If random reboot happens - zip this files from SD and send me.

This would really help with problem investigation.
[Streak 5 Android Development] nadastry:
One problem with DSC 1.7 pre:

Sometimes the S5 does not go to deep sleep (CPU Spy).

It shows ~ 4h 128 MHz and ~ 4h deep sleep (for instance).

The other states are not needed often (minutes).

The thing is: I am used to switch WLAN on/off when needed/ not needed - and it was definitly off that time.

How do I find out what prohobits the deep sleep?
[Streak 5 Android Development] _n0p_:
Check (and reduce) WiFi timeout in DSConfig.
[Streak 5 Android Development] chriscullen42:
Ok, I'll use my restored S5 with 1.5 for today - just to make sure it's nothing to do with Audible (as I have not used it much until the other day), then if it is ok, I'll put 1.7 back on the device and follow your instructions above and let you know how I get on. Thanks for all you help!
[Streak 5 Android Development] charlie_brown_:
hi nop!

after i flashed 1.7diff2 some weeks ago, my s5 is stable and i haven't reboot or wifi problem, only problem is battery drenage.

now do you suggest me to upgrade to this stable 1.7 or i can attend to major new upgrade?

and if i upgrade to 1.7 must i wipe all my data again?

many many thanks for your works!

n