yashsingh1/xdaforums huggingface dataset:
[Streak 5 Android Development] abauer:
@n0p, I am trying to build kernel using toolchain from Linaro 12.08 based on 4.7 which gives yet anotherspeed boost compare to 4.6 it needs some patches thou to make it compile http://xdaforums.com/showthread.php?p=27589313#post27589313 which work ok, am using the master branch from github and as .config the n0p-config file. zImage compiled fine after the patch. But when i install the boot.img on the streak, the screen is somehow rotated, what can be the reason ? Am using the boot.img to exract the ramdisk from the latest version DSC 1.5.

Thank you in advance
[Streak 5 Android Development] _n0p_:
abauer, interesting. I planned to test Linaro toolset myself, eagerly waiting the results.

--

Please check and disable all options in "DSC Team Phoenix options" menu in kernel configuration.
[Streak 5 Android Development] p_razzi:
Any chance we can get 'keep LEDs on' in the next build of DSC Config? ;)
[Streak 5 Android Development] _n0p_:
Yes, but this feature needs to be redone first in nicer way. PowerManager hack comes to mind.
[Streak 5 Android Development] abauer:
Yea did, thank you , I see no substantial difference in performance between 4.6 and 4.7 compiled with the same flags , maybe i am doing something wrong or maybe need to get more deeper into compiling optimizations offered from the linaro with other flags, something i am unwilling to do as to compile only once one kernel after a "make clean" my laptop needs more than one hour, plus my charging cable is ruined now and each time i have to flash something i need to upload it to internet first and then download to sdcard, so the process for me is very slow and too much time demanding.
[Streak 5 Android Development] _n0p_:
abauer, i think Linaro toolchain should by used to compile the whole Android env, not only kernel. This should give better results.
[Streak 5 Android Development] abauer:
n0p, DO agree , but I think , it would be a waste of time trying to build GB instead of a JB at this point. Your GB (DSC) has become boring now, :o, never crashes, no FC, no reboots faster as never before,battery lasts for days now on my setup, I cant even find a small problem now . You have made of GB a total success with your DSC releases.

My sincere congratulations !!!

http://xdaforums.com/showthread.php?t=1762641
[Streak 5 Android Development] deysmacro:
hmmm.. i smell jb invitation :D
[Streak 5 Android Development] nom051205:
That's why I never post in gb thread, for me all this gb roms smooth like butter, yes there are some minor bugs but not even bother me :D

Hey abauer, if you want to try to make jb boot on our device, you can ask help from Preludedrew, as far I know he is the first dev can boot up jb on qsd8k device, then he spread his trick for other dev. Or you can ask texasice or jmz_ software/jmz_taylor and team dirt_mazda. All this dev are very welcome and offering help when I try to port ics in the first time. I learn much from them. Too bad I have no any knowledge how to compile kernel :p

You can find them in #evervolv freenode or tweeter.

Good luck and wish both of you and nop can bring jb to our device.:D
[Streak 5 Android Development] abauer:
As for my experience not all GB released are same. If you look deep enuf you will understand what I mean.

As for JB, I have no access to adb anymore so cant get logs during boot time in a conventional way, so count me out. n0p and hunderteins are our hope.

As for kernel building, setting up the environment is maybe more than half of the work, if you never done before. rest is just trial and error game , and there is really very much info around about kernel building and patching, but n0p with his work has made it unnecessary to intrude and change anything in the kernel, it is just perfect as it is now, unless some porting to the new 3.2 kernel would become a necessity down the road. and also n0p seems to be always around.

EDIT : adb can be run in a wireless mode too, didnt know that before , cool cool , trying now
[Streak 5 Android Development] msprakashmmc:
Yeah :) time to cook JB:D
[Streak 5 Android Development] sinan33:
How about Mike?Does he help us about ICS issues?
[Streak 5 Android Development] _n0p_:
Well, I see signs of my Streak aging:

For example, kernel flashing sometimes stops device boot, unless I fully reformat yaffs.

This actually stops me from experiments, as I have no plans for departing with my Streak.

Sorry if that breaks your hopes though,

Sergei.
[Streak 5 Android Development] uluvali:
Quick question (may be off topic)

My hardware (Home, Back and Options) buttons stopped responding this am. I cleared my zeam quick launch tray and downloaded button saver so that I can navigate. Ive cleaned the partition and cache. Ive reinstalled 1.5 as well. Searched forum for "hardware buttons" with no success. Next step would be to perform a clean reinstall. Has anyone else experienced this? Is this a hardware failure? Is there another diagnostic step?
[Streak 5 Android Development] _n0p_:
uluvali, odd, but working advice:

Try to heat the button panel with finger (friction, like you did in your childhood with thermometer). This worked for me with home button.

Do it for 5 min, then reboot and do calibration. Hope this'lll work.
[Streak 5 Android Development] msprakashmmc:
yeah dude, after many tweets he replied n asked to mail him.. He sent a patch for fixing camera ICS, I posted the patch link in Camera and ICS forum by n0p for testing but nobody tested it yet.:'( Link for that forum here, anybody please test & report back please, then only we can use Mike as he helps now..

xdaforums.com/showthread.php?t=1834458&page=7

---------- Post added at 09:48 PM ---------- Previous post was at 09:41 PM ----------

Mike sent this..

It should fix overlay based proprietary

camera libs coming from gingerbread

and froyo builds.

https://github.com/CyanogenMod/andr...mmit/738b6a8dfdcd7b38c7178f8d70d3d69c33f16551
[Streak 5 Android Development] uluvali:
Amazing! It worked. Stopped working 15 mins later but at least I know what to do to get it back. Was this a permanent fix for you or is this a sign of impeding hardware failure?
[Streak 5 Android Development] deysmacro:
maybe there is outside electro static that making the hardware touch button goes unresponsive... you know.. something that counter the sensitivity of it..
[Streak 5 Android Development] _n0p_:
It's hardware, but still works for me, occasionally stopping at sauna or other places with high humidity :)
[Streak 5 Android Development] uluvali:
Working like a charm now... I'm not going to ask, "How did you know the workaround for a hardware problem?". I'll just say thank you and You are the MAN!
[Streak 5 Android Development] msprakashmmc:
What..? So will you try to fix camera n other problems with Ocs..? or you not Gonna test ICS..?:( Oh man:'( please dont say like this..?!
[Streak 5 Android Development] Dude_Virus:
How does keeping the UV : ON help..?? What differencd does it cause..?? Is it beneficial to turn i on as while testing UV i didnt notice any such change.
[Streak 5 Android Development] deysmacro:
uv means undervoltage .. in theory it should significantly reduced power consumption...
[Streak 5 Android Development] sinan33:
@Sergei

Sergei would you please send me download link for your latest ICS kernel?
[Streak 5 Android Development] _n0p_:
Undervolting makes voltage on CPU a bit lower. I expect 5% (+-, depending on usage scenarios) benefit. On other hand, it can cause device to freeze or reboot (all Streaks are different).

http://xdaforums.com/showpost.php?p=31022862&postcount=506
[Streak 5 Android Development] vankooten:
getting desperate

a few days ago I did a clean install and upgraded to 1.5

this was because of sudden reboots.

yesterday I was in town and took my Dell out.

the wifi icon was still on and didn't switch for the 3g icon.

went to settings to switch the wifi off manually, but it didn't want to switch off.

waited till I was back home to see if it would pick up my router, but no way.

so I rebooted the phone and everything was working again.

immediately made a logfile and mailed it to Sergei.

later that evening I installed titanium pro, and this prog told me that the phones id was changed ??

it left me two choices, keep this one or go back to the old one. did the latest.

this afternoon (I was at work, so far away from home) I saw I had an email notification.

opened the email, but it could not make a connection with the server.

tried some other internet things, but nothing would open.

the 3g icon was there in white.

from the notification bar I could switch data on and off, as well from settings I could switch it off and on, but no connection.

so I rebooted the phone and everything was working again.

what is wrong with my phone (or with me) ??

is it an idea to format the sd-card, put the rom and the recovery and the update 1.5 on it and start all over again?

joop.
[Streak 5 Android Development] Dude_Virus:
Buddy the same happens for me if I have connection fixer switched on in DSCONFIG .... if i keep the connection fixer OFF it switches fine though takes sometime... The normal mode and agressive mode in connection fixer they both give me the same problem. Try the off mode and check it helped me with the problem. Same thing happ in 1.4 also wherein if I kept connection fixer ON even after reaching my.office which is 20 kms away the wifi still showed as connected to my router and signal strength as poor. This also resulted in massive battery drain even causing the phone to heat up.

---------- Post added at 09:52 PM ---------- Previous post was at 09:44 PM ----------

I am testing with UV switched on and i havent got any freezes or reboot but have experienced 2 things.

1. After unlocking the phone a part of the screen towards the.bottom displays as black and after couple of seconds becomes proper.

2. The same issue occurs when i finish a phone call... in which the bottom 1/4 of the screen is black hiding the lock buttons.. so in order to unlock the phone inhave to play blind and move my thumb over the black area so as to unlock the screen.
[Streak 5 Android Development] vankooten:
thank you dude_virus,

the second time the wifi was off and the 3g didn't want to come up.

Switched the wifi-fixer off now.

Curious what this 3g thing can be.
[Streak 5 Android Development] Rocker19943:
n0p, would be like if you could fix led notice buttons light, the middle buttond goes on when i have a missed call, but for other notices like a new mail, only thouse side buttons goes on
[Streak 5 Android Development] Dude_Virus:
Sergei had mentioned earlier in the posts that it depends on what you select , red white or green in the respective app. For me for email the middle light light on where as for the missed call the backbutton is lit. For facebook its the back button whereas for other messengers its the home button. This actually helps identify as to wht kind of notification is it.
[Streak 5 Android Development] TheManii:
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 mtd@system /system
mount yaffs2 mtd@system /system rw remount
mount yaffs2 mtd@userdata /firstboot nosuid nodev
devwait /dev/block/innersd0
exec /system/bin/fdiskcmd cleansd
devwait /dev/block/innersd0p5
devwait /dev/block/innersd0p6
# mount ext4 /dev/block/innersd0p5 /cache noatime nosuid nodev nodiratime errors=continue barrier=0 noauto_da_alloc nobh data=writeback
# mount ext4 /dev/block/innersd0p6 /data noatime nosuid nodev nodiratime errors=continue barrier=0 noauto_da_alloc nobh data=writeback
exec /system/bin/fdiskcmd

Could you elaborate on the reason why the ext4 mounts were commented out?

I know firsthand that the stock kernel doesnt like using ext4, but this isnt the stock kernel.

I had assumed that DSC used ext4.

Also: do you know what devwait is exactly? It obviously mounts innersd0p5/6, but it's "magic"(?) in that it's not an external command(?).

Do you know if we have the source code to it and where it is if that were the case?

I dont expect that if I did

devwait /dev/block/innersd0p7

that it would magically know to mount p7 as /system, devwait only has 1 parameter it would seem.

Finally: do you know if devwait or fdiskcmd includes e2fsck?

as /data is an ext partition, they should have fsck run on each bootup.

I dont know how important it is for an ext3 partition, but it seems that most ramdisks that I run into that mount /data as ext4 also include e2fsck for it.

---------------------------------------------------------------------------------------------------------------------------

Unrelated topics: I'll ask again: would you consider adding in MTP/PTP support? CM9 is capable of using all 3 (depending on kernel support).

streak5sd8 and streak5sd32 are stopgap solutions, the proper way is to use MTP and have massive /data partitions (streak5dm).

Android 4.0+ still supports UMS, but native 4.0+ devices (ie ones that ship with it and arnt simply upgraded to it) that use UMS are in the minority.

DSC isnt 4.0+, but AOSP/ICS and paranoidandroid are downstream of the phoenix kernel.

I'm not keeping up that well, but are your hardware issues NAND based?

If that is the case, streak5sd8 and streak5sd32 based roms do not use the nand at all except for storing/loading boot.img.

The only exception is DSC as it's based on 40x, source based roms are not capable of using /firstboot and you can simply skip mounting it alltogether.

(/system on streak5sd8 and streak5sd32 is stored on innersd0p7)
[Streak 5 Android Development] _n0p_:
mounts commented - it's actually a leftovers from testing hPa's way. And i dislike writeback (stability) option anyway.

I did it different - ext2/3 drivers are disabled in kernel and ext4 used for them instead:

CONFIG_EXT4_USE_FOR_EXT23=y

It's that simple.

--

devwait "should" wait for device to become active BUT actually isn't executed at all. Dunno why it's there.

--

fdiskcmd will reformat internal SD in case of FS failure, so it'd better to disable it on non-std layouts.

--

From what i've read MTP is only a high-level protocol, so i think it's not kernel related - i'm almost sure it's functionality is provided by user-space library.

--

Next, /firstboot (it seems) can be quite easily moved to /data.

--

As for my hardware issues - i think i simply flashed it too much, so i should stop while it works.
[Streak 5 Android Development] TheManii:
I havnt read up on how MTP is implemented, regardless our roms arnt built with it in, userspace or kernel.

I only assume that it requires some kernel side code, as the S7/S10 have MTP but UMS is completely disabled in them.

I did think about simply symlinking /firstboot to data (if that's what you mean), but I have no idea the implecations.

Dell bothered to include it as a seperate partition for a reason, though it could be as a fallback.

I can tell you that if it panics on /data, it will simply mount MTD:userdata as /data.

How does it mount innersd0p5 and 6? is it using devwait or is it hardcoded(?)

I dont know how this would affect the rest of the system, but being able to explicitly state ext3/4 "should" be more "compatable", though it seems that it's fine the way it is.

As the DSC varient kernel does it differently, do you think:

mount ext4 /dev/block/innersd0p7 /system
mount ext4 /dev/block/innersd0p7 /system rw remount

will work?

If it's already mounting p5/6 as ext4, I dont need to change those.
[Streak 5 Android Development] _n0p_:
I suspect partition mounting is done within fdiskcmd.

Anyway, it'd be nice having all mounts in one place (/system, /data, etc.)
[Streak 5 Android Development] TheManii:
At least on stock 407, I believe it is devwait (I'm not certain, but I think I saw a ramdisk with devwait but not fdiskcmd, but I could easily be mistaken)

I think(?) that it waits for it to be ready and then mounts it in a hardcoded manner(?) when it's ready.

Regardless, the other rom's ramdisks I dealt with explicitly declare their mounts, including FS type.

I cant say the cost/benefits of switching back to that from the current situtation, but it would make the ramdisk at least more flexable in it's mounts.

The other roms use something like this:

mount ext4 /dev/block/innersd0p7 /system
mount ext4 /dev/block/innersd0p7 /system rw remount
mount ext4 /dev/block/innersd0p6 /data noatime nosuid nodev nodiratime errors=continue barrier=0 noauto_da_alloc nobh data=writeback
mount ext4 /dev/block/innersd0p5 /cache noatime nosuid nodev nodiratime errors=continue barrier=0 noauto_da_alloc nobh data=writeback

For streak5sd8 and streak5sd32

devwait and fdiskcmd arnt used at all, unfortunately neither is e2fsck.

If you dont like writeback, you can simply remove that entry as I assume it's optional. In fact half those options are redundant, android applies most of them to /system anyway without it being specified.

As the other roms are not 40x based, I simply removed MTD:userdata alltogether and simply leave it unused.

It would certianly make things easier on my end if you avoided using MTD:userdata as that would mean I can simply not mount it for CWM also.

MTD:userdata represents 90% of the issues left in my bugreports for CWM.
[Streak 5 Android Development] _n0p_:
In syslog:

E/PrintK ( 1): <3>init: /init.rc: 75: invalid command 'devwait'
E/PrintK ( 1): <3>init: /init.rc: 75: invalid command 'devwait'
E/PrintK ( 1): <3>init: /init.rc: 75: invalid command 'devwait'

--

innersdp8 is for SD emulation?
[Streak 5 Android Development] TheManii:
Well then if it really is fdiskcmd then it has to be hardcoded(?),

"fdiskcmd cleansd" doesnt specify which goes where exactly.

Yes innersd0p8 is going to (eventually) become

/sdcard + /sdcard2 (Android 4.0+)

/sdcard + /sdcard/external_sd (Android 2.3.x)

Havnt been able to make much progess on dual sd, but it wont change how the install scripts or CWM works.
[Streak 5 Android Development] hunderteins:
fdiskcmd is ugly, but not so ugly to reformat a non-std internal sd. It starts fdisk and finds, that

the innersd is 16 GB large, thinks it is 16 MB large and stopped because that is less than 512 MB. So no need to disable it completely.

It you want to disable repartioneering and format of the innersd, make sure that there is the file /firstboot/format (644) and the directory /firstboot/boot (755) before you start fdiskcmd
[Streak 5 Android Development] abauer:
n0p Can you provide me a kernel image zImage with kgsl enabled plus a boot.img from the attached file , so 2 files.

Thank you in advance.
[Streak 5 Android Development] _n0p_:
I can, but i doubt it'll run - as .zip doesn't preserve rights on files.
[Streak 5 Android Development] abauer:
thats ok I will do the rest , as for now I have not much space left on device to compile from sources, actually I need zImage and ramdisk.cpio.gz

thanks

Already have a half compiled JB from sources but no space on device to compile kernel
[Streak 5 Android Development] _n0p_:
http://n0p.8bit.fm/streak/a_z.zip

zImage - kernel with kgsl/genlock (no screen rotation needed).

ics_ramdisk.gz (ics ramdisk) and ramdisk.gz (your files).

Have fun.
[Streak 5 Android Development] TheManii:
Could you show what mount looks like on 1.5?

Apparently I cant use DSC unmodified anymore as the mounter cant handle extra innerSD partitions.

I'll just recreate the mount script with explicit mounts if I had the mount parameters.
[Streak 5 Android Development] hunderteins:
...
/dev/block/innersd0p5 /cache ext3 rw,nosuid,noatime,nodiratime,commit=99999,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/innersd0p6 /data ext3 rw,nosuid,nodiratime,commit=99999,barrier=1,nodelalloc,data=ordered 0 0
...

# mount -t ext3 -o rw,nosuid,noatime,nodiratime,commit=99999,barrier=1,nodelalloc,data=ordered /dev/block/innersd0p5 /cache
# mount -t ext3 -o rw,nosuid,noatime,nodiratime,commit=99999,barrier=1,nodelalloc,data=ordered /dev/block/innersd0p6 /data

fdiskcmd does more than just mount. It will reformat your innersd and populate the filesystems /firstboot and /data, if they do not suit. Is there /firstboot/fdiskcmd.err from your broken dsc?
[Streak 5 Android Development] TheManii:
It doesnt reformat unconditionally, I've reformatted /firstboot and it didnt touch my innerSD.

If it does reformat, it didnt kick in on my 16gb card.

Thanks those commands are exactly what I needed, I'm just going to bypass fdiskcmd.
[Streak 5 Android Development] hunderteins:
cause your 16 GB card is not legit. look into 'dmesg |grep -i fdisk' fdiskcmd thinks your card ist 16 MB of size and keeps away.

All I'm saying is that fdiskcmd is where the initial layout is born. Really supporting larger internal sd will need to reimplement all functions of fdiskcmd.
[Streak 5 Android Development] TheManii:
It's simply easier to not use it, out of the 4 roms I'm working on, only DSC uses fdiskcmd.

I'm simply going to bypass it for my streak5ex and streak5dm mods.

It's not capable of mounting innersd0p7/8 anyway, so I couldnt use it even if I wanted to.

Edit: actually, in the same vein: DSC is the only rom that even uses /firstboot.

The other roms arent based off of 40x.

I cant tell it to not mount firstboot either.

Edit2: yea it detects it as 15mb, that's pretty dissappointing in how inflexable it is.

Only thing I can say is that it does do e2fsck at least, the other roms manual mount and dont remember to do e2fsck on bootup on /data, but that's about it.
[Streak 5 Android Development] _n0p_:
I remember manics did that already (at least quite similar) without trouble and even published a guide.

Why don't look here:

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

He even backed up all data.
[Streak 5 Android Development] deysmacro:
ah .. that one more related on using otg cable without actually connected to the thumbdrive or something like that .. it uses otg cable to use the extra internal sd partition...
[Streak 5 Android Development] _n0p_:
Absolute nonsence. It just uses a different mount point.
[Streak 5 Android Development] deysmacro:
well.. maybe i was wrong... :eek:
[Streak 5 Android Development] _n0p_:
Guess it'll have to wait until me or hunderteins will change the innerSD :)

--

Attached ramdisk mounts existing partitions without problems (newer ini binary), but for some reason breaks init.d.
[Streak 5 Android Development] hunderteins:
baseband 369

I got the "new" softbank rom from http://xdaforums.com/showthread.php?t=1895331

and installed the amss.mbn on DSC via fastboot.

Only problem is, [gsm.version.baseband] stays at GAUSB1A136612-EU

I put ATI into /dev/smd0 and got Release: GAUSB1A136912-EU. So it's half upgraded?

I even installed dsp1.mbn from 369 but it stayed that way.

I've got the feeling that the amss.mbn is not the firmware part that has to do with libril-qc-1, cause logcat -b radio showed me, BASEBAND_VERSION GAUSB1A136612-EU

So I made a nandroid, flashed the recovery.img and the complete streak_29579_12.pkg,

flashed streakmod recovery and restored the nandroid. So the gsm.version.baseband is now GAUSB1A136912-EU.

Now I've got a pre boot softbank greeting screen. :rolleyes:
[Streak 5 Android Development] _n0p_:
Congrats on new bootloader :)

--

BB sometimes doesn't update it's number for system.

For me (if it's an issue) it's enough to nandroid/FReset/nandroid back (no need to flash full rom).