yashsingh1/xdaforums huggingface dataset:
[Dell Streak 7] TheManii:
I dont know why your button mapping is weird, did steve change it around from the defaults in the kernel?

I havnt touched the mapping at all in my CWM build as the defaults worked fine:

Volup : Scroll up

Voldown: Scroll down

Power: Select

Back: Back

You might be better off in the long term to fix the mapping then to modify the CWM mapping.

If you wish to make future <ICS Layout> builds flashable with CWM, perhaps now might be a good time to change your branch's name.

Like how the GN has:

Yakju

yakjudv/yakjukr/yakjusc/jakjuux/etc

Takju

to represent different configurations

we should do something like:

streak7 (default for stock 5xx compatable layouts)

streak7dm (the current ICS layout)

streak7ex (default stock + ext4 /data + ext4 /cache)

streak7dmex (ICS layout + ext4 /data + ext4 /cache)

(I dont know if the latter two branches would be used though, depends on if ext4 /data + /cache works)

Since flashing a kernel ment for 1 onto a device partitioned to 2 will make it simply not boot.

The right way to be to rename your entire branch, the fast way would be simply to modify the asserts in the install script.

This would require updating your rec (mainly to update the branch it supports internally, but would ultimately make it easier to prevent users from flashing the wrong one and getting a soft-brick.

Here is the current device tree for building CWM 6.0.0.9 (which I will be releasing soon):

S7+S10-6.0-120720.rar

I put the S10 tree in it too as an example,

to make it compatable with streak7dm you will need to change recovery.fstab to:

/data	auto	/dev/block/platform/sdhci-tegra.3/by-name/UDA

and comment out the /emmc entry, that will tell CWM that the device has /data/media symlinked to /sdcard in normal use and to use "rm -rf" instead of actual formatting to protect /data/media when formatting. It will also keep selecting update zips and nandroiding from /data/media support (which is brand new to 6.0.0.9).

Also: I have no idea why sdcard2 isnt working in streak7dm as it works fine in streak7 (minus the fact the display and unmount button is missing for sdcard2)

Have you tried adding back sdcard_oem and reenabling sdcard_oem in the init script? That was the first thing I did (along with changing the /data mounts)

Edit: I am ready to release ICS B4-mod as soon as someone can send me a copy of the apks for it.

Edit2: i'd also like to point out that we have (had) an irc channel if you wish to comminucate in realtime: #dellstreak on freenode (there's technically #dellstreak7, but it's empty now)

Edit3: If you can confirm that the changes needed to make cwm work on streak7dm works, I can continue support for CWM/streak7dm myself as I'll still be building CWM anyway
[Dell Streak 7] snargledorf:
Can't download the source. Devhost is having database issues it appears :/

Can you elaborate a bit more on the naming schema? What is this for? The kernel?
[Dell Streak 7] TheManii:
Devhost is giving me issues on my end too, having trouble uploading.

It should clear soon enough.

if you installed a streak7dm rom (ICS partitioned rom) onto a streak7 (stock 5xx partitioned device) it would cause it to soft-brick as it would try and mount /sdcard as /data.

At least in theory, if we hypothetically released B4 and my B4-mod as update.zips right now.

Having them named as different branches allows you to use install script asserts to block users from flashing the wrong one.

The branches would be for android/CM9 itself (the right way), as in your build tree for CM9.

The fast way would be to change the asserts in the install script (if you do decide to release anything as an update zip)

The kernel is built seperately, it doesnt care about branches (it's the same kernel anyway), it's android itself.

We should also technically also have branches for the wifi builds, since wifi should have the ril stuff turned off(?).

But that's a step or two ahead.

We can wait until you have a new build that can actually boot first, the changes should be pretty easy to make.

I'd just like to see your opinions first.

(JB should also do the same, but it has to actually boot first too)
[Dell Streak 7] Wetzel402:
Hi TheManii & giveen,

I have a quick question for you guys. I am editing a boot.img to gain root access at boot and init.d support. Would the following work?

on boot
chown root root /
chmod 0755 /

/system/etc/init.d/*

This is in the goldfish.rc file.

Thanks for everything you guys do!
[Dell Streak 7] TheManii:
That's likely a bad idea, what are you trying to do specifically?

Do you want the shell to start in root?

Do you want to be able to write to /system without remounting?

<something else>?
[Dell Streak 7] Wetzel402:
This is for the Acer A200. The stock kernel mounts / as read only so I am trying to get full root access (rwx) at boot. We have a root method for the device but currently flashing a fresh ROM tends to result in lose of root because the kernel will mount as read only every time.

Sorry to side track things.
[Dell Streak 7] TheManii:
I need your init scripts to be sure, but

android_device_dell_streak7 / init.streak7.rc - GIThub

is essentially what controls it.

You can either:

change that to say rw

at the end of that block, remount to rw (i would recommend this)

the exact location depends on your device's init scripts though.

Nothing is (supposed) to go into "/" after boot, it's only populated by init and the contents of the ramdisk itself

chmodding everything to 755 may break the system
[Dell Streak 7] TheManii:
After looking more at the B4 system.img, I found out why:

system.img is slightly damaged.

Error Opening \\.\PhysicalDrive0. Error Code 5
No of disks 0
Partition Table Error on C:/Users/TheManii/Desktop/system.img
Invalid End of sector markerBlock size 1024, inp 2048, inodesize 128
Linux Partition found on disk 1 partition 0
Error reading Inode 0 parent inode 45057.
Error reading Inode 0 parent inode 12289.
Error reading Inode 0 parent inode 11.
Error reading Inode 0 parent inode 45057.
Inode 59397 with file size 0
Error reading Inode 0 parent inode 45057.

is what ext2explore tells me about it.

I was able to mount it under linux, and for the reason android is also able to mount it, but (unless ext2explore is mistaken) the image itself is slightly damaged.
[Dell Streak 7] snargledorf:
K just a little update for everyone.

I'm currently working on downgrading the 1.7ghz overclock back to 1.2ghz which is MUCH SAFER. Also Not sure if CM would allow merge with such a high OC.

Also working on fixing the cpu governors which currently aren't doing their jobs. (Cpu pretty much stays locked at it max clock the whole time which kills the battery and I'm pretty sure it is what is causing random reboots)

Going to start back porting linux kernel 3.0 parts that are needed by ICS (Network stats).

Looking into upgrading the kernel to 3.0 (This is a BIG task, no time soon)

Once I have the 1.7Ghz OC out I may release an alpha of B5 to anyone willing to test it.

This will be far from a final release, and there WILL be bugs, but I feel like it's stable enough that it shouldn't do any harm to someones streak.

Will be back after I finish this OC business.
[Dell Streak 7] brncocorey:
I'd happy to test it for you.
[Dell Streak 7] snargledorf:
Well I was able to drop the oc but now I've got no boot due to audio driver issues.

Very weird since I didn't even touch anything to related to audio.
[Dell Streak 7] giveen:
Its probably because Dell connects a bunch of things.
[Dell Streak 7] TheManii:
Perhaps you should simply set the default cpu clocks/governer to the stock level, and leave whatever OC clocks that work alone?

At least the network stats can be backported to a 2.6 kernel, that's how ICS/S5 got it working. Though there's a lot of stuff to backport if you want everything working on 2.6 huh?

Edit: If you find where the led controls are, could you make it so that the cap key leds can be controlled?

The Phoenix Kernal/S5 maps the button backlights to /sys/class/leds/button-backlight/ so you can turn them off/control them individially.

At least to me, the cap keys became redundant when 5xx came out with the action bar.

The Phoenix kernal maps them individially, and CM7.2 used the middle key as a notification led.
[Dell Streak 7] TheManii:
I just realised that the V also has an atmel mxT224 and it also is 2 point only.

The VP likely has the same controller (as it's more or less identical to the V), and it has at least 4 points (as mandated by MS to be WP7 compatable)

It's too bad they botched up the drivers so much in a way that you can simply use a different mxT244 driver(?)

Edit: what is the camera module in the S7? In the V it's an Omnivision OV8810, and there is a thread on hackporting it from similar devices.

Edit2: never mind, it's an Omnivision OV5642 and OV9665

Edit3: if you do get the FFC (the OV5642?) working, could you share your findings with kibuuka? It's the same FFC module as on the S5.

Edit4: the OV5642 is the rear cam, the OV9665 is the FFC
[Dell Streak 7] giveen:
yeah, I was looking at that earlier. Made sense. I'll take a look after I get wifi up and running on CM10.
[Dell Streak 7] TheManii:
After recharging my VP, it actually supports 4 points, even though the mxT224 says it supports 10(?) touch points.

(They might have not bothered fully enabling what the controller's capable of, and I am making the assumption it's the same controller)

It could be possible that a device has multiple touch controllers, adding up to support the total amount of points.

But I would doubt that the VP has more then 1 controller, that would be overkill.

I'm assume I'm asking old questions, but how much work would it be to seperate out the mangled code and use a 'standard' touch driver and rewrite the batt(?) driver as it's own driver (like it should have been in the first place)

Is the driver in the kernal or in android? As I think(?) that it's in the kernal so we would have it's source with the code dell released(?).

Or is it because that the driver is managled that you can seperate them?

Completly OT: but the VP uses the same OV5642 for it's rear cam that the S7 uses, so at least we'd have a working rear cam if we ever got WP7 :D

I dont know what touch controller it uses though, I can only say so far as it's definitely an atmel, but I cant confirm that it's a mxT224
[Dell Streak 7] giveen:
touch controller is mxt224, but with the luna battery driver placed inside of it.

Currently driver writing is beyond me, but yes, it is in the kernel.
[Dell Streak 7] TheManii:
I'm looking at the OV5642, and the ZTE Skate has both:

An OV5642

A (mostly) working driver for it with source for ICS

Does this help?
[Dell Streak 7] giveen:
I'll give it a try, won't hurt

https://github.com/ColdFusionX/android_device_zte_skate
[Dell Streak 7] TheManii:
According to them, the cam driver is missing panorama mode.

But we currently have nothing, even garbage is better then the current status of not even a blank screen.

Wonder how the FFC plays into this though, I saw in passing that the FFC can link up to the rear cam and share it's DSP (so the FFC doesnt need one).

I dont know how the ZTE skate not having a FFC will affect it, hopefully it wont
[Dell Streak 7] Nocturnal_50:
it is possible that they have a few lines of dependancy code in that driver for the FFC, honestly wouldnt surprise me either, if its easy to change those lines to ones compatible with the FFC of the S7 (if change required) I dont see how this could possibly hurt the device
[Dell Streak 7] TheManii:
It would appear that the OV9665 is also used in other devices, such as the HTC Evo. (not very surprising)

Doing more research on what devices use that and have a working OV9665 ICS level source driver, but the evo seems to only have the rear cam working, which is a OV8810 (which isnt relevent to us).
[Dell Streak 7] Nocturnal_50:
I see you have seen the XDA home page today... you could basically port/carry-over any drivers from any HTC phone that was released last year (and some this year prior to the ONE series being released) that has an ICS ROM (whether official or otherwise) and see how it goes
[Dell Streak 7] TheManii:
It depends on the sensor, there's many different omnivision ones.

The drivers are likely not cross compatable or else they could simply forcehackport them.

The sensors are also different from newer devices, the ones with official ICS drivers use newer sensors anyway.

HTC isnt going to port ICS to any of their older devices (likely), the ones that still use the same module that we want.

Which is ironic, as the V just happens to have the exact same sensor that's on the front page, but noone's bothered porting a kernal for ICS.
[Dell Streak 7] Nocturnal_50:
rummage through evo roms grabbing camera drivers? alternatively decompile an official RUU for ICS and see how that goes
[Dell Streak 7] TheManii:
A cursory check shows that the og evo doesnt have official ICS, the only evo devices that have it are the newer models. And it's likely that the newer ones use newer camera modules.
[Dell Streak 7] Nocturnal_50:
evo 3d? would have to modify the driver to negate the 3d but for the most part it should be relatively the same for 5mp cameras from OV
[Dell Streak 7] TheManii:
I dont need to look past the basic specs, the 3vo uses dual 8mp sensors, and ours is a 5mp one.They're different models and arnt compatable.

Edit: I was thinking of the rear cams, we're talking about the front ones now

Edit2: The 3vo does use a 1.3mp FFC module, but it doesnt seem to be the same as the S7's anyway
[Dell Streak 7] Nocturnal_50:
surely modifying a few flags and changing a few values could result in similar functionality, works with drivers that PC's use for a lot of the hardware by the same OEM why would it not work with the camera drivers for android?
[Dell Streak 7] TheManii:
We dont really know how they work, we dont have the luxery of microsoft demanding device makers make their devices conform to standardized generic drivers (think UAA, sound drivers were a disaster before that)

Qualcomm did do that for adreno though, every adreno is very similar from a driver perspective (according to qualcomm, they release a single ICS package and it works with all currently existing adreno modules)

Cameras are an entirely different story apparently, very few source ports of ICS have fully working cams.

The ones that do either A) just used the stock ICS drivers (assuming they even exist) or B) ported it themselves (which is what the link a few posts back are)

Think ethernet/wifi chips on the PC, they're generally not cross compatable driver wise, but they all interface with windows via NDIS. NDIS itself doesnt change that often (and it's explicitly backward/forward compatable), whereas android's interfaces change enough each major version that it breaks everything but the cpu and basic sensors every time (ie the gpu and camera and a couple other things). Android drivers also not very forwards compatable.

If the modules really are that simple, there's no reason Omnivision wouldnt have created unified drivers.

Since it means that they dont have to write dozens of variations.
[Dell Streak 7] Nocturnal_50:
seems like we have a fairly large job ahead of us with getting the cam and/or 3g/4g working (I would prefer the radios and bluetooth over the camera anyday)... would be awkward but not surprising if dell somehow made their drivers rely on each other rather than having separate drivers that dont conflict
[Dell Streak 7] TheManii:
Radios I cant speak for, as I have a wifi S7 and I dont even have a sim in my S5 now.

BT should (keyword should) be working as it's a part of the wifi module, it should be all or nothing. (though that's not the case sometimes anyway)

The BCM4329 driver source should be available anyway in the CM9 kernal source(?), the B4 kernal is rather old, regardless of wifi drivers.

I mentioned the rear cam drivers because it's available as source, hopefully it works and it's easy to integrate. Even if it doesnt integrated nicely/easily, it's still something

The front cam: if we dont get driver source we're (likely) going to need a shim for the HC drivers or simply not have a working FFC.
[Dell Streak 7] joeclark:
for me also the working 3g/4g radio is more important than the camera. i never use it. i have an 8mp camera on my SII that i really dont have a need for the tablet to have a camera.

actually the radio is the main reason i went back to HC (boss decided to pay for a data sim card)
[Dell Streak 7] snargledorf:
Sorry I haven't posted an update guys. Work and life have been keeping me very busy lately and I haven't had much time to work on the CM9 Streak7 port.

Some good news is I got it booting again, but sound has stopped working and apps that used to work before don't seem to be loading anymore.

Once I have those two issues resolved I am going to get a new alpha out to any testers that want to give it a try on their devices.

One request I have is that if there are any folks out there who have streak7's with a modem who could step forward for testing in the future. Currently no one on the dev team has a 3g streak so it is impossible for use to test to see if it is working. Same goes for gps, without a 3g streak we have no way to know for sure if the gps is working.

There still is a while before we will be moving towards getting the modem working we want to get the basics reliable first wifi, hw/video acceleration, etc. But it would be awesome if there were some ppl out there willing to test for us.

Unfortunately as I stated in the beginning of this post, I have a lot going on in my other life and work right now so development has and will be very slow for the next week or so.

Once things settle down here I should be back on top of things :)

---------- Post added at 12:53 PM ---------- Previous post was at 12:45 PM ----------

Also, I am getting closer to figuring out why the CPU stays at it's maximum freq.

Basically the main system process is getting caught in an endless loop somewhere and is causing its CPU usage to max out.

This is causing the the CPU governor to ramp up to the maximum frequency to try and chew through the work faster but since it's in a loop, it never finishes, causing your battery to drain and making the system unstable.

This is also most likely what is causing the system to randomly reboot every once in a while even when it is just sitting there not doing anything.

I suspect network stats not being implemented in the kernel is one cause, but I still have a bit of diagnosing to truly understand what is causing the system process to loop endlessly.
[Dell Streak 7] BTW lover:
I've just started using this ics Port via the wonderful recovery zip Port by TheManii. I wad really hoping this port could help me with a rather exotic problem: in the official 3.2 rom it is no longer possible to use wifi channel 14 which I was able to activate through advanced settings in the wifi menu in settings. The option was called regulatory domain. Any xhance you can bake this back in either this or the new 4.1 port? I'm stuck with wifi channel 14 because the ap I use is set to it because of too many interferring aps in the area
[Dell Streak 7] TheManii:
Incidentially, I do have a modem (an EM820U to be exact), but I cant use it as the donor mobo is broken and the wifi one doesnt have the ports. (it only has blank pads for the pci-e slot).

I could assist with a 3/4g unit if someone donated just a bare mobo (or a cracked display unit/etc) :D

About wifi: it might simply have been built incorrectly in B4, as it has the freq band selector, and the chip simply doesnt support 5GHz.

Changing ro.wifi.channels to 14 doesnt add the box for channel selection either.
[Dell Streak 7] giveen:
Can you guys run this command for me?

"ls /sys/class/net"

I want to see what the wifi network is being called. Right now, in my build I have "wlan0", and I want to see if its labled something else.

Also any other commands you can think of that will display as much info as possible about the wifi card.
[Dell Streak 7] TheManii:
On ICS-B4 it's

bond0/
dummy0/
gre0/
ip6tnl0/
lo/
sit0/
tunl0/
wlan0/
bonding_masters

Do you need it from stock 5xx, or any of the contents of it?
[Dell Streak 7] giveen:
Nope, just wanted to confirm it is wlan0
[Dell Streak 7] Synman:
I'm watching your repo currently and, like you, if I can find the time can help with the modem as I have one with an active sim.
[Dell Streak 7] Nocturnal_50:
Is access to build.streakdroid.com allowing people to fall under the generalisation of dev'? if it is then you have a dev with a 3g variant
[Dell Streak 7] TheManii:
gps is independant of the modem, unless you mean Agps
[Dell Streak 7] Nocturnal_50:
I wouldnt exactly be able to test the aGPS other than by going to and from work and around the city each day, going out into the country would be a test for it but I am yet to see how that would function as there have been times with stock HC were I have noticed it refers to the tower location rather than my location (possibly due to lack of positioning satellites over some regions of Australia) this was also the case with all HS ROMs I have tested... most of my input on AGPS would be hit and miss
[Dell Streak 7] snargledorf:
I mean gps. Figured its probably better to test when your not inside your house connected to wifi.

---------- Post added at 08:31 AM ---------- Previous post was at 08:28 AM ----------

Sweet. Problem solved lol. Sorry man.
[Dell Streak 7] Nocturnal_50:
outside of a physical building it would implement agps if a cellular data connection is available, unless out of reach of the 3g/4g towers or no sim in the device
[Dell Streak 7] TheManii:
lol maybe that's why. From what i've seen on some days even heavy cloud cover is enough to make the signal too weak to read some times.

Overall it 'seems' to work fine in B4 though (though I am getting instances where I see 2-4 sats but they dont lock
[Dell Streak 7] giveen:
Have you tried my GPS hack to improve the look up of satelities in your area?
[Dell Streak 7] siobhter:
What's that?
[Dell Streak 7] Nocturnal_50:
its what giveen said... use google buddy, it will help you
[Dell Streak 7] TheManii:
1st link on "gps hack android" is fixing the gps on the transformer, rest are old/irrelevent articles, so I have no idea what it is.

What I can see in B4 is that the GPS 'seems' to be much worse then on 514.

Standing in the same location with 514, I get about 5-9 sats locked averaging about ~30 SNR (according to gps test)

On B4 I get about 1-4 sats at the same SNR, but they never lock nor do I ever get more than that.

I've tried using the 'update agps data' on gps test on both roms, but after 10 minutes I still dont get more then 3 sats visible with 0 locks on B4.

Previously though it did take 15 minutes for 514 to figure out where I was on first lock, and it worked afterwards. I'll try that on B4 later, but I need it for a roadtrip tomorrow so I had no choice but to revert to 514 for it (not really surprising though, B4 was never stated to be release quality, I can easily switch back afterwards)

Breakdown:

514:

<gps dorment for a while>: first lock: 15 minutes

second lock: 1 minute

further locks: seconds

B4:

first lock: 10+ minutes

never actually locks any sats
[Dell Streak 7] Nocturnal_50:
any chance on getting a 3g port of stock b4 to test this out with agps? might prove to be more accurate or lock faster
[Dell Streak 7] BTW lover:
Since a few days of use of b4 I'm having serious issues with my streak not waking up from screen off. The device goes dead but seems to be running judging from battery drain. Only a reboot via reset hole brings it back to life. Any ideas?
[Dell Streak 7] Nocturnal_50:
Resort back to honey streak or migrate to Jelly-Streak, next build for jelly will go up this week some time
[Dell Streak 7] BTW lover:
I will, was just wondering why this behaviour started after about a week of use. I tried switching to a different launcher and setting min clock speed higher but my streak still dies randomly every few screen offs. Thanks for the reply anyway