yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Odd, I'm using DroidWall no problem with this kernel & FRX07...

"Unfortunately it is not possible, to enable the firewall."

Can you elaborate on that statement? What happens? Is there an error? Do you have logs from the incident?

DroidWall requires root for obvious reasons, perhaps SU never popped up to request permissions...?
[Touch Pro2, Tilt 2 Android Development] großa:
Nevermind, found it :)

Sometimes there are too many trees in the wood :)
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
After klicking the Droidwall widget, i see a su popup.

An then a popup "Droidwall:Firewall disabled"

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

Now it is running, don´t know why. I have nothing changed. ???
[Touch Pro2, Tilt 2 Android Development] großa:
Sometimes it'll take 2-3 trys to get the permission from SuperUser :)

Tried to insmod ramzswap.ko and xvmalloc.ko. Terminal always says "no such file or directory"?
[Touch Pro2, Tilt 2 Android Development] großa:
Compcache seems to be enabled by default. Here the compcache part from the default froyo.user.conf (which comes with FRX07):

#compcache related parameters

compcache{

compcache_en=1	# enable(1) or disable(0)20 compcache

cc_disksize=100	# Ram swap disksize - any number between 1 to 98 should work; default is 1/4 of the RAM (24)

cc_memlimit=64	# Limit the memory usage for backing swap (cc .5x known issue-defaults to 15% of total RAM)

cc_backingswap_en=0	# enable(1) or disable(0) backing swap

cc_backingswap=/dev/block/mmcblk0p4 # pointing to the backingswap partition device, swap

}
[Touch Pro2, Tilt 2 Android Development] mgross029:
'Kernel files are in /system/lib/modules, but I tried it and it said can't insert blah blah blah invalid module format. Not sure if there was a different context this was meant to be used in though.

Running this latest kernel... So far all running well... Thanks StarFox....
[Touch Pro2, Tilt 2 Android Development] großa:
Yes i tried it with the path you mentioned. Doesn't work. I disabled compcache in froyo.user.conf now. Booting is faster now.

The new kernel is running well. XDAndroid runs much smoother than before. Great work StarFox!!
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Thanks.

Now I have a clean dmesg after disabling compcache.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Problem Report 8/11 Test Kernel

With the 8/11 test kernel... My Rhod500 rebooted last night while charging and then the most recent. I received a call and answered it... It then jumped to my speaker which was really loud then the UI rebooted itself while still maintaining the call... (Very Strange Right) I could not disconnect the call or turn the volume down...

What made it funny was it was my wife and she just kept talking and then got a little annoyed when I asked her to hold on and be quiet... (I was at work)

Of course when I explained what was going on and she got a laugh out of it too... :D Beta Testing is soo much fun! LOL

Edit: Wanted to mention the USB Tethering works quite well for me with Droid Explorer...
[Touch Pro2, Tilt 2 Android Development] mgross029:
Wondering if this could be attributed to my problems too... Is there anyway to clear the old Modules out... I am still noticing 1340 module statements when booting the OS...

Thanks...
[Touch Pro2, Tilt 2 Android Development] großa:
Yes there's one:

# Fix for init module lameness

rm `find /lib/modules/ -type l -print0 | grep -v $(uname -r)`

Try this and put it into your froyo.user.conf (it's from StarFox).
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks großa...

I did run this command and have put in my froyo.user.conf, but I am still seeing references to the 1340 kernel... Any other ideas besides wiping out my data.img? I know that would fix it but as often as we change kernels I was hoping for a better route...
[Touch Pro2, Tilt 2 Android Development] mgross029:
So a uname -r does only show the 2.6.27.46-fox-110811 kernel loaded so I'm guessing the kernel is loading properly, but still haven't figured out why I'm still seeing the other kernel referenced in the boot process...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Open a terminal window, and type:

su

mount -o remount,rw /system

find /lib/modules/ -type l -delete

Then reboot. The modules will be unpacked on next boot.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks Starfox,

That put me in the right direction... I used -type l but it did not delete the kernel files so I changed to -type f and that cleared all of the files from /lib/modules/... Once I rebooted I did see there was no more reference to the 1340 kernel... I think I will build a script so I can do that before installing any new kernels...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, seems init needs a better way of detecting when to replace modules...
[Touch Pro2, Tilt 2 Android Development] mgross029:
So far with the 8/11 Kernel my phone will randomly reboot and drop radio signal... Also since deleting the module files on boot the init still detects that they are there and will skip the install, so this could attribute to the problem.

Any ideas on how to force the install? Thanks...

Edit: I also have a weather clock and the location shows up with a number instead of a city name.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I told you what you need to get the module re-installed on reboot, and is still valid. If you go and running your own commands then you are on your own.

Are you running the kernel with anything in cmdline different from stock? If so take that out and see if you can repro the issues. My kernel should behave very similar to stock without the "additional" cmdline parameters.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] mgross029:
Starfox I followed what you had posted... However, when it came to installing the modules it Skipped them... I tried the modified command after a reboot and it skipped the installation.

The only other things I've added were the offset because I am running the newer version of Haret... Since when I first tried your kernel that was what I needed to do, along with a few others.

I know these are all test kernels and every Rhod version may handle them differetly...

It may be best if I just delete or rename my data.img to see if that resolves these problems since I have been trying the stock kernels and test kernels. Thanks for your advise...
[Touch Pro2, Tilt 2 Android Development] domoarigato:
questioni... in this kernel does green LED = sleep and orange = function?

cause mine doesnt stay green. maybe after the initial boot but it stays orange the rest of the time.

anybody know what the cause of this is? i havent installed any other programs other than facebook and google maps.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Did you disable GPS? Or maybe Facebook is constantly connected/syncing.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Updated to include the proposed led patch. If it breaks, then someone else is responsible. Otherwise, you are still responsible for your device.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, pass that buck on...

thx for the patch integration :p.
[Touch Pro2, Tilt 2 Android Development] Starfox:
The required changes to support ext4 /data has been pushed by the rootfs autobuild. Couple of things to note:

1) You must use a rootfs dated 8/16 or later for the proper support

2) You must use my kernel, as it is the only one with the required support compiled.

3) You must have the cmdline option "ext4dev" inside your startup.txt. Otherwise it will still continue on using ext2 data.img.

4) Using ext4 will create a brand new file called data.ext4. This is intentional, as I did not want to have the same file (data.img) with different format to confuse the matter further. This also means that none of your existing app/setting will be preserved. Be sure to back up your data & app with something like Titanium Backup, and have at least 500MB free on your SD card so that the system can create a new store.

While it is still possible to corrupt your data.ext4, it should be reselient against unexpected shutoff/battery pull/etc. If there is a demand for it, I'll consider putting up a close-to-mainline kernel separate with ext4 support+few minor updates included that supports all devices.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fortunz:
Starfox and Detule rule! Donation sent to starfox, anyone know where to donate to detule? I looked at his profiles here and at ppcgeeks and didn't see any links.

http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-August/000371.html

At first I wasn't sure what to make of that (where to add what), but I figured I take a guess at it and echoed the options to the listed location in the custom section of my user.conf. In the unlikely event anyone else here is as clueless as I was, I'm including the line to enable notifications and get rid of the sleep debug:

echo 0 > /sys/module/microp_klt/parameters/debug_mask

The led will flash orange while a call is incoming. If you miss the call and the phone turns off, solid green shows until you clear the notification. The tape I had over my led is gone, yay! :D Also, LEDs hack works for me to turn it off completely if for some reason you don't even want notifications or charge indication.

It's probably a good idea to boot the kernel with no switches right off the bat to ensure your device sleeps well before turning the debug off.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The only remaining issue is blinking... currently the LEDs stay solid until the state is cleared (charging, email, low battery, etc).

But definitely some nice work done by all. emwe, alex, Detule, and Starfox. Kudos, users will now love you for a short period of time :p.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I can't speak for anyone else, but I plan on loving the devs for a moderate amount of time following this improvement. ;)
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks for the appreciation -> my few lines of code certainly do not call for it, but if you feel so inclined please donate to the xdandroid project.

The above code will stop sending sleep notifications to the LED and start receiving notifications from android. Seeing how you will likely have a (lack of) sleep triggered LED (amber) ON while echo-ing the above command, I think it is a good idea to follow up the above command with

echo "0" > /sys/class/leds/amber/brightness

echo "0" > /sys/class/leds/green/brightness

This will ensure that the LED is reset in the off position before starting with the new regime.

Finally, before automating the process please make sure you are comfortable with your phone in the sense that you can anticipate its sleep behavior without being able to see the LED notification. One should _at_the_very_least be always aware when GPS is turned on.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I've put in another donation to xdandroid with a hat tip to you. You've helped make my experience a little better, and I appreciate it, even if the code was short.

Thanks! Will do. Just out of curiosity, are the quotes important? Did I get lucky writing it without them, or are they optional? When I was scoping out other user.conf lines, it seemed like there were only quotes around alphanumeric strings. If numbers alone were being written, no quotes. Just trying to pick up what I can, figure out what's what.

I certainly agree about running it with the debug intact first. I only ever tried GPS once, even in winmo. Perhaps that's why I've never had a sleep issue.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Quotes are there for safety. It's not required for argument without spaces or chars that need escaping.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Grabbed the latest kernel and rootfs, changed startup.txt, removed old data.img and rebooted. Took a while, seemed almost to keep looping on the flying androids boot screen but it finally finished, got a FC for android.phone, continued setting stuff up after it settled down. Loaded titanium backup pro, phone hung after installed, then rebooted to android, locked up as soon as boot was done and then immediately rebooted to winmo. I'm assuming I won't be able to get logs since it rebooted to winmo, but anything you would like me to check or look at?
[Touch Pro2, Tilt 2 Android Development] baikal2:
Feedback on LED patch

I have gotten the test kernel and included the 3( 2 resetting the LEDs to 0 and the line disabling the debug) lines in my conf file.

The amber light stays on after booting up. If I have a missed call , the green light turns on. The green light in this case overrides the orange. Once I clear the notification , there are no lights turned on.

I can also make the orange light go away ,if I plug and unplug the charger. I have verified to check that there is no activity going on by removing the lines from my conf and the LED stays on in green. Am I overlooking something obvious here.

The new kernel seems snappier too. Thanks to all the devs to make this happen.
[Touch Pro2, Tilt 2 Android Development] Starfox:
There should not be an issue with ext4 by itself, since I've been testing it on my phone for the past few days. I'd say it's a transient error since you started having FC on first boot which shouldn't happen. See if it still happens after nuking data.ext4, and if it does we can try to figure out if it's the kernel (should not be the rootfs, all it does it change where /data is).

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
After changing to the new rootfs, my german keyboard is broken.

Can you please change the german microp-keypad-files with the new files?

http://xdaforums.com/showpost.php?p=16335114&postcount=37
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks for catching this -> it will be fixed in the next patch hopefully today or tomorrow.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Just tried again, same thing "The process com.android.phone has stopped unexpectedly. Please try again. I even re d/l'd the kernel to make sure it was just a bad dl. Any other advice or tests you want me to run? Also, can you increase the size of a ext4 like we can the ext2 data.img's standardly created?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The process for increasing the size should be the same.

As for that FC message, does it go away eventually? I get those sometimes on boot, but they go away after a couple. I think the system is just choking as it starts up.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I'm in the process of rolling out a "vanilla" kernel without all the testing fluff. I think that ext4 is a lot more sensitive to anything OC'ed, at least that's what I'm seeing from the logs. When the vanilla+ kernel is released, I'd like for you to try it on there to make sure none of the testing stuff is interfering.

Also as arrrghhh said, changing the size is simply a matter of editing /init. If you don't want to do that, then run the commands:

dd if=/dev/zero of=/sdcard/data.new bs=1M count=[size]

mke2fs -t ext4 -E test_fs -O ^huge_file -F /sdcard/data.new

gzip /sdcard/data.new

mv /sdcard/data.new.gz /sdcard/data.gz

On next boot, it will replace your existing data.ext4 with the blank one you created. Of course, this assumes you have enough space for both your current and the temp one you are creating, at least until the next boot.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
If I hit FC it will go away :D. I'll try setting the beotch up again and see what happens. A little off topic, but this morning was in winmo because I was expecting a call and didn't want to chance missing it, and low and behold... freaking phone never rang on my end and went to VM. I'm wondering if Sprint's having issues and we're thinking it's the port.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
For you, that might very well be the case. Have you done a PRL update with Sprint lately? Or bugged them on the topic? You're already running 2.37 for your radio, right?

Assuming you've got the updated radio, then I would look at PRL. If that's all good, and calls are going straight to VM in WinMo... then yea, it's not the port, it's your service :p. This would also explain why you're the only one who's really experiencing the bug in this manner.

I think all the other bugs people were experiencing was resolved with the radio firmware update. I know I haven't been dropping calls or losing service at all anymore.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Yeah I'm on 2.37, I believe I'm on the latest PRL but I'll updated just for haha's and see what happens. Sounds crazy but I was glad to see it happen in winmo too which showed it's not the port.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm kinda glad too... as much as we hate WinMo, it at least allows us to rule out issues with our port :p.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Please check dmesg for any sort of weird message about sdcard/etc. after you boot up. Also, if you don't mind, please try the same thing without ext4dev in the cmdline, to create a fresh ext2 data.img. Thanks.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks StarFox...

Great work... Kernel ran nicely on my Rhod500... Tested out the LEDs and they worked for a little while but then after a reboot they just stayed amber. Went back into my .conf and commented out the echo commands which makes it nice to be able to switch back and forth... After I did that phone operated as it did prior so no biggie... It was kind of wierd but I was almost missing my green led... Almost like and assurance that my phone was sound asleep... LOL! :D

Detule & emwe: Nice job on the LEDs btw...

The EXT4 works great... I don't OC so just stock speed and I did notice a little more snappiness in the system...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Update with some more patch from your friendly kernel guru Detule. This one does require some userland update, but you will get more blinkenlights goodness (and yes, it even blinks). You need an updated liblights from http://db.tt/ZUjymT9. The file should be bind-mounted on startup in your froyo.user.conf, ie: mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] baikal2:
Starfox,

Do we still need to retain the 3 echo lines in the user.conf file along with the lib mount.

TIA
[Touch Pro2, Tilt 2 Android Development] Starfox:
Yes, the 3 lines are required, two to reset the LED and one to change the behavior. Please note that the final patch that would be included may have different kernel interfaces name, if/when the patch gets accepted I will update the kernel to match what has been committed.

Please make sure to provide feedback either here or on the IRC channel concerning the led patch. Thanks.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] baikal2:
Feedback

Starfox,

Not sure what the expected behavior of the patch is There are no lights in android (not even during booting). A missed text/call gives me a solid green.

Again not sure when the blinking lights kick in. This patch is an improvement over the previous one in that the persistent amber is gone .

Once again thanks for the patch
[Touch Pro2, Tilt 2 Android Development] detule:
Can you verify that you have mounted the lights library correctly (ls -al /system/lib/hw/ and read off the date)?
[Touch Pro2, Tilt 2 Android Development] baikal2:
good point. Will get back to you.
[Touch Pro2, Tilt 2 Android Development] baikal2:
The date is july 27th. I might not have mounted the lib correctly. Could you please check if the mount statement which Starfox has listed ,is complete.

Should the line read

mount --bind /sdcard/lights.msm7k.so /system/lib/hw/.

instead of

mount --bind /sdcard/lights.msm7k.so /system/lib/hw.
[Touch Pro2, Tilt 2 Android Development] detule:
It should be

mount --bind "path to downloaded lights.msm7k.so" /system/lib/hw/lights.msm7k.so

In my case, the "new" library is placed at the root of my sdcard so the command is

mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so

When you've successfully loaded the library, the date should read August 16.
[Touch Pro2, Tilt 2 Android Development] baikal2:
Thanks detule. The mount worked. Date showed up as Aug 16th.

Missed call throws a blinking green. Connecting the phone to a charger throws a solid amber.

thx
[Touch Pro2, Tilt 2 Android Development] Starfox:
Sorry, that was my fault. My mind was side-tracked. Thanks for catching that.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks Detule, emwe and StarFox... I've been running stable since last night... Charging shows Amber, when fully charged went green... Missed call, email or notification / blinking green...

When using GPS mapping I've always had to reboot the UI (using Blade Buddy) to clear whatever is running (still have not been able to figure this one out)... Light stays off... Seems to work much better than other previous patch!

Nice work!

Edit: This one caught me... Did not rename the lights_msm7k_so file at first... I kept noticing during boot that it was stating it could not find the file/directory, so I started looking into the problem and renamed the file... Just a gotcha for me and not sure if others may run into similar issue

Also, I notice a few errors on boot which reported when trying to load the modules... I'll see if I can capture a screen shot or logs... Thanks again everyone...
[Touch Pro2, Tilt 2 Android Development] mgross029:
Posting a couple getlogs files for review...

I actually had a SOD... Not sure what caused it but I had to reset to get any response back from my Rhod500...

First log was taken before SOD and second after...
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
With kernel 8/16, my phone is rebooting to winmo after 5 minutes. (still ext2, sorry, no logs)
[Touch Pro2, Tilt 2 Android Development] detule:
Stating the obvious here but somehow your sensor blew up -> this was/should not be affected by the LED patch. If this happens again make sure you grab a logcat -v time, as well as dmesg.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks detule... I will do that...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Please open a terminal window, and these command exactly:

su

find /data/system/dropbox/ -mtime 0 -name "SYSTEM_LAST*" -exec cp {} /tmp \;

tar cvf /sdcard/$(date +%F).tar tmp/*.gz

rm /tmp/*.gz

You should find a file called /sdcard/2011-08-17.tar (or today's date) that you can post somewhere. These contain copies of your last dmesg for any boot in the past 24hrs.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Starfox, wasn't having luck with the ext4 data so went back to the ext2. If you want me to try diff things I'll be glad to, but not gonna be around a ton the next few days. I will say though that all the kernels are working great, stable, blinking lights, etc. Sorry for my noobness, but how are we supposed to enter the comments into out conf file for the blinking lights? I've entered the echo commands but they don't seem to have taken until I manually enter them in a terminal session, but then they work wonderfully.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Worked just fine in my froyo.user.conf. Hop on if you want me to guide ya...

But it's really like any of the other commands that go in user.conf. Just make sure they're each on their own line, and in the custom commands section.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Thanks, I didn´t know that.

My logfile is attached.