yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Carld256:
Already done, setting it to 710400 doesn't work either. I even turned it down to 600000 to see if maybe it kicked in there, but it didn't. I've been running at 729 for a couple weeks without any problems with the older kernel, so I'm assuming my hardware can handle it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, this kernel might not support CPU scaling.. I haven't had time to confirm yet, work's been nutso today!

Edit - Confirmed, and added this as a caveat. No OC for now folks!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Same way in which GBX0A is "better" than FRX06 - It is a more recent codebase that offers improved features, but unfortunately requires some things to be rewritten and cleaned up, causing regressions in functionality until the new codebase matures.

The new codebase can't mature without testing.

Obviously this isn't mature enough to be a "daily use" kernel, but without testing it will never be mature enough, and the .27 tree is getting very fragile and difficult to maintain.

I think users here need to think more about the concept of parallel development. They don't seem to understand that there can be "newer" .27-based releases and .39-based releases going on at the same time.

An analogy might be - .27 is a really nice house that is mostly complete and with occasional renovations being made, built on landfill that is slowly subsiding - it seems great to the owner/user but it's going to fall apart at some point due to a poor foundation

.39 is a house that is still under heavy construction but built on solid bedrock
[Touch Pro2, Tilt 2 Android Development] prexzone:
thanks that makes sense. i wish it worked for me so i can see wat the differences are. but GBX0A is "better" than FRX06? hmm thats one i didnt know. i tried GBX0A before FRX06 it didnt work for me n y is it most of the updates that come out only support FRX06. thats wat i noticed plus i hear ppl say a lot that FRX06 is more stable. So how is it better?
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
deleted double post
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
If you prefer a fast phone, is gbx0a better, but not if you need bluetooth.
[Touch Pro2, Tilt 2 Android Development] prexzone:
That doesn't explain nothing. I saw someone say on the gingerbread thread that its not all that fast. Sometimes fast n sometimes slow
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Can we please stick to the topic at hand? Thanks.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I would be surprised if someone here posting something to the topic, but

I fear, that this thread is dead, after you have scared away all the testers.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WTF are you talking about? Be gone troll!
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Maybe my google translator has not found the right words.

I meant only that it seems that you're not very nice.

Perhaps it is sometimes better not to answer stupid questions.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's nice. Please, if you don't have anything to post that is relevant to the topic, don't post. It's pointless, and wastes everyone's time.

Back to .39, WisTilt2 has sorted out the issues with the autobuild so it should be functional again - but still no history yet, one thing at a time ;).
[Touch Pro2, Tilt 2 Android Development] mbellot:
Unfortunately stupid questions will just get asked again if they are simply ignored.

As someone here said, this forum is based on written messages. In order to propagate the information it also requires reading, something many seem to forget (or can't be bothered) to do before asking.

@argh - Sorry for the OT.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Gingerbread is fundamentally newer than Froyo and contains a lot of improvements. It is a significantly improved foundation. However, the xdandroid port of Gingerbread to our devices is not yet complete - so to a user it appears "worse" even though it has a significantly better foundation. However, it IS the future once its maturity level increases.

Same for .27 vs .39 - .39 is a vast improvement in terms of its foundation, however it still needs a lot of porting work for our specific devices.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I am eager to understand the project a little better, but I'm starting from scratch. I looked at a beginner's guide over on ppcgeeks, and have read this thread with interest, but I'm not sure I understand which components serve what purpose -- specifically, which component is actually android itself.

Is zImage just a linux kernel and there are separate froyo files elsewhere (in rootfs perhaps?) that tap into it, or are the zimage files I end up downloading a particular configuration of the kernel that includes all the basic Froyo elements in addition to a kernel of linux used by many other distros? Also, what caused developers to choose the older kernel originally, and what has changed recently to make .39 viable?

Thanks for any clarity anyone can provide. :)
[Touch Pro2, Tilt 2 Android Development] Starfox:
Are there any plans to merge the NAND kernel with .37? I know there are a lot of changes in the NAND kernel that cannot be merged - doing it at this time might be the easiest way to sync it both.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I assume you mean .39. But yea, I've already suggested to ACL that he try to merge his work into the .39 tree so we can have one kernel for haret & NAND. .39 is already running clocks from .27 NAND, so hopefully ACL will be able to get something workin.

Please, do more reading on your own. This topic has nothing to do whatsoever with this thread. zImage = kernel, hopefully that helps you at least. Enough OT people!!
[Touch Pro2, Tilt 2 Android Development] randomblame:
For those interested a changelog for 2.6.39 is located here:

http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.39

Grep MSM in there and you'll start to get an idea of what kind of improvements have been made to the code, keep in mind the kernel we've been building on for so long is based on 2.6.27 so there are far more fixes and improvements than what that changelog shows alone in the versions between. Simply put this is a much cleaner better base to build on. Now back on topic - I saw a few commits today looks like some work is getting done on wifi my wife wont let me test this on her rhod till wifi is working lol
[Touch Pro2, Tilt 2 Android Development] Starfox:
Android is an OS that (currently) runs on top of Linux kernel. While a normal Linux system (say, Ubuntu) uses GNU to provide OS functionality, Android uses an intrepeter based on Java called Dalvik to provide functions, such as allocating memory, handling input, etc.

Linux is often called GNU/Linux because the Linux the kernel provides functionality that mostly deals with the interface to the hardware or filesystem, hence the need for drivers either compiled into the kernel zImage or as a module. There still needs to be abstract layer to let programs access functions, and newer versions of Android provides updated functionality - some programs needs to be rewritten to work on newer version. On Ubuntu those are provided by the GNU libraries.

Linux on Android is actually a forked version that is based on but is no longer part of the "mainstream" Linux (as maintained by Linus Torvalds and others). This is because Google needed certain functionality within Linux to make Android work, but Linus rejected it because it had issues and wasn't being maintained.

So what you have is:

Linux kernel - maintained by Linus

Linux kernel with Google magic - maintained by AOSP

Android (Dalvik) - maintained by Google

Root fs - What gets mounted as /, contains file for booting

System fs - What's in /system, contains files for the OS

Data fs - User data in /data

-- Starfox
[Touch Pro2, Tilt 2 Android Development] manekineko:
FYI, I tried out ext4 on .39, converting both my system and data files. Ordinary performance wasn't affected, but performance under load seemed quite good. I managed to be downloading 3 files from the market simultaneously together with a Google sync at the same time and the system maintained responsiveness. However, later, when I was installing 3 other files at the same time, the system got bogged down and still got fairly sluggish.

It's no panacea, but I believe it's an improvement.

If anyone has any ideas on objective testing of the improvements, it's simple to recompile the kernel with ext4 support and convert the files to ext4. Or I could just send you the files.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Very interesting - doesn't surprise me, I know market downloads are clearly I/O bound in the filesystem. (A Wireshark cap of market downloads shows it zero-windowing all the time, and running top during a download shows sky-high iowait percentages.)

I'm actually surprised ext2 is THAT bad though, I wonder if we have some other fundamental flaw that interacts badly with ext2.

Edit: As to an example of why .39 is a vastly improved foundation that, once our port of it matures, will be the way to go in the future - look at Manekineko's zoombar kernel. I saw his post on the dev list and that feature would have been next to impossible to implement on the .27 tree.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just curious, did you disable journaling or leave it enabled...?
[Touch Pro2, Tilt 2 Android Development] manekineko:
I left it default, which I believe is enabled. Seems kinda handy given our phones aren't exactly paragons of stability.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, but that's the whole crux of the argument about slaughtering SD cards - the journaling will kill 'em. So in theory, disabling journaling should keep from killing the card, while still reaping the benefits of the new file system.

I haven't seen any proof/anything to backup the claim that journaling does in fact kill SD's, other than I know the way journaling works, and it's not really compatible with how SD cards work.
[Touch Pro2, Tilt 2 Android Development] prexzone:
Arrrgghhhh or how ever u spell ur name if u don't like a question just ignore it. U don't knw it all. Just cos u good in these sort of things don't mean u on top of the world. This is the internet ppl gonna write watever they like. When I made a complain about the 39 kernel did u help me? No. Stop being hard it doesn't help only makes ppl distant away from u
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What the hell are you talking about?

Unless you have something to add that pertains to the thread topic, then don't post. Seriously, I'm getting sick and tired of these OT posts that not only have nothing to do with the topic, but also have nothing to do with the forum section. PM me if you seriously have personal demons with me, I'll gladly delete your messages. Much better option than posting this drivel in a thread.
[Touch Pro2, Tilt 2 Android Development] DmK75:
I tried this kernel on my Topaz.

It's booted and works but backlight always minimal and screen only landscape, battery is wrong etc. ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol... I did say it's RHOD only, I'm assuming you read that part :p. emwe has TOPA up on .35 fairly well AFAIK, I'll ping him.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Didn't we have this convo in another thread, where you claimed it was a dumb idea? Do you even know how SD card works? That most "on-board" flash on newer phones use eMMC, which from a OS standpoint acts just like a SD/MMC card, and I know that there isn't a big issue using jornaling you make out to be.

http://www.bunniestudios.com/blog/?p=918

Did you know most memory card don't even test all the cells coming out of the line? It's cheaper to toss in a controller to do that block management (he quotes $.19 for cost of testing each cell for 30sec.) Most card typically reserve 5-10% of the cells for wear leveling and bad block management, hence the varying size of usable space (I've seen anywhere from 3.6~3.8GB on a 4G card). I guess he doesn't know his stuff when he talks about using ext3 and not having to worry about block management.

The use of journal and the flash wear was probably warranted when using small (~256MB) cards and the likelyhood of over-wearing the same blocks. I'd rather have journaling enabled and live with a card that's going to last half as long than to deal with a corrupted data.img which seems to happen at least once a month from using XDAndroid.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well here's were we differ. I wouldn't want to trash an SD card's life for the sake of a corrupt data.img - even if it was once a month, which certainly is not the number of times my data.img goes corrupt - I'm testing so many things, that's usually the only reason I create one. I am pretty much always able to revert to my old data.img.

Either way, hyc has a patch to fix the umount issue on shutdown, but AFAIK you must have dedicated partitions.

I would also want to make people aware, if it did cut a card's life in half I'd sure like to know that's what I'm in for.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I'm not even talking about shutdown, I've had corruption happen because the phone shut off from running out of battery. Next boot, everything was FC and the only thing I could was to nuke the image. Unexplained freeze, battery popping out, running out of juice, these are things that a journaled FS can be resilient against corrupted FS.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] manekineko:
Well if the powers that be agree to switch to ext4 in XDAndroid when .39 matures, then we could have the best of both worlds.

It'd be really simple to edit the init to read a startup.txt option to go with or without journaling.

Then we could post it as an option, maybe default no journaling, but if you want to have a more resilient Android system at the expense of increased card wear, add JOURNALING=ON to your startup or something like that.
[Touch Pro2, Tilt 2 Android Development] BoominSVX:
So I was just messing around with this again, and I know CDMA was a grey area, but just for S's and G's I redid the FRX06 download, updated the user config, changed my startup.txt, re-downloaded the f22 rootfs, and also the newest ril2. After sending it all over to the card, I have 3G at boot. FWIW, I also changed the ril located in the rootfs to the ril2 just to be sure it was there, and on unblank, I get a nice T CDMA 64 at the top of my screen. This is the current kernel from the autobuild of .39. labeled Sat Jun 11 22:13:01 PDT. Phone is still about the same speed as .27, but working finally.

Edit: Speed just became much improved. LauncherPro FTW. Also, wifi is trying, but stuck at obtaining ip address and I cant hang up a call, but I think thats my fault for using end as home.

I'm REALLY happy things are finally coming together.
[Touch Pro2, Tilt 2 Android Development] fortunz:
Just installed it and I'm very happy with the results. On my .27 kernel (20110506_232639), my favorite Chinese dictionary, recently released in beta on Android, would crash before opening. The same beta opens fast and runs smooth on the 20110611 of .39 and I finally get to try out live OCR. :D Very exciting. Thanks to all involved.

RHOD500, booted into airplane mode initially. 3g and voice connect well enough once I enable them, noticed extra sluggishness until I turned off 3g only. While trying to receive a call (placed by me from my GV web dialer) touchscreen didn't recognize input while I tried to refuse the call, had to hang up from the website. On a second try, phone locked up during the ring and I reset it. I assume the above is related to the documented CDMA issues. Will try more later.

I think I might make a batch file or a mortscript for transitions between .27 and .39. Because I really am that lazy.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for the feedback guys. I haven't been around much to test .39 (my laptop died finally...) for the powers at be, but they got wifi workin for GSM devices last I was on IRC - CDMA seemed to have some separate wpa_supplicant issue - I still need to catchup on the logs.

I'm just curious, why? The initrd offset shouldn't be an issue, and neither should the different haret. Basically you should be able to boot a .27 kernel on the .39 setup, just the other way around doesn't work (can't boot a .39 kernel on a .27 setup ;))
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Also the newest autobuild has ADB over usb support built-in. I've had success on linux, JonPry said it should work on Windows, but my mac doesn't like it.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I wasn't sure about startup.txt's affect before, so thanks, saved me a little wasted effort. My script is hardly necessary, but now not only can I trigger the kernel switch from a lnk on my homescreen, but I can also tell at a glance on the homescreen which kernel is active (when I toggle the kernels I also toggle haret's icon between 2 customs I made for easy ID). I'll probably only use .39 when I'm playing with Pleco's live OCR (see earlier post), but I plan to use that fairly regularly.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
He makes one comment about using ext3 instead of JFFS2. He probably slipped up when saying ext3 instead of 2 or 4. He makes NO mention of journaling on his blog, and he was not speaking about journaling but about flash-aware vs. non-flash-aware filesystems in general. Yes, journaling won't put a major stress on a single point of the card, but it will STILL significantly increase the amount of data written to a card. It WILL wear out the SD faster (however, not by "burning a hole" to a single location), and it WILL decrease write performance, the latter being why no phone manufacturer I know of uses a journaling filesystem. Nearly all Android phones use ext2 or ext4. Given how ****-tacular our filesystem write performance is, we don't need to make it even worse with jouranling.

More importantly - do you see any phone manufacturers using ext3? Have you thought there might be a reason WHY none are?
[Touch Pro2, Tilt 2 Android Development] MDGeist:
been testing the 12/06 .39 kernel for the last days. looks nice enough for me, haven't had any fc's, failed wakes or data connectivity issues. clockdrift issue seems to have improved, too. with the old .27 kernel i had about 2-3 minutes drift a day, now it's about 0,2 secs :)

only problem i encountered was a freeze + reboot when i was travelling by train, phone kept switching from gprs to edge to 3g and ultimately just rebooted...

no problems in daily use though, icq/msn/gtalk, some browsing, some gmail... got about 2 days of battery life on this run ^^

using Froyo B v006 with CWM on a Rhod100
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'd recommend the new RIL, but based on that awful build you're running it won't be possible to integrate it :p.
[Touch Pro2, Tilt 2 Android Development] randomblame:
aww arrgh don't bash cm it works great on ... other devices... :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm not bashing CyanogenMod if that's what you think. I'm bashing that awful build he's using, tiad8 trash.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
froyob isnt tiad's its nekarbay from neopeek
[Touch Pro2, Tilt 2 Android Development] bijan588:
There are two froyo blues...

One by neopeek and one from tiad.

Tiad is just a gammic, half of what he says are lies. All he does is take stuff from other people and bakes it into one and calls it his release. Just like how he claims he compiled this "new" kernal that has the same md5 hash as wistilts. Basicly he is a lair, and what he does improve on he wont share... He was even distributing warez with his builds. If you want support for that garbage go to his site and ask.

Sent from my DROID X2
[Touch Pro2, Tilt 2 Android Development] muziling:
With kernel-pack-htc-msm-2.6.39.1-gaf8d799-dirty-20110616_213601.zip

Make a call, all UI buttons is not press-able, (BT, add calling, mute, speaker, keypad,...)
[Touch Pro2, Tilt 2 Android Development] milda25:
Yes, I have same issue on rhod100.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Known issue with the zoombar enhancements. I forgot to add it to the list on the first page tho, I'll do that now.

I thought that commit was pulled, but that might've just been locally from WisTilt2's tree to narrow down if that was indeed the issue. It is the issue, but if the commit is still present in the autobuild, that is why you folks are experiencing this bug.

Edit - just talked to jonpry, he's going to pull the zoombar commit. Newest kernel from .39 will have this feature removed, until this bug is fixed.
[Touch Pro2, Tilt 2 Android Development] muziling:
adb works now ,no need to adb connect 192.168.20.1 before.
[Touch Pro2, Tilt 2 Android Development] detule:
nilfs2 binaries

For future reference
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Updated the second&third post - adb does indeed now work, although there's no indication on the phone that it is...
[Touch Pro2, Tilt 2 Android Development] Starfox:
dmesg dump from latest autobuild on Sprint RHOD. It turns on Wifi on and detects SSID but gets mangled packet. Oh and the mystery of froyo.user.conf, file created is FSCK*.REC, the rest is left as an exercise.

http://db.tt/MmIWSnd

-- Starfox
[Touch Pro2, Tilt 2 Android Development] muziling:
kernel-pack-htc-msm-2.6.39.1-g67a27c5-dirty-20110618_191202.zip

when charge with pc, phone call in, no ringtone, otherwise, it has.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Bluetooth log for jonpry.

http://db.tt/wgn7RWG

Running patchram under .27 w/-dr (debug/reset)

http://db.tt/F6esiWB

It's failing this test from bluedroid, I think kernel interface may have changed? Hardware seems fine.

// Try for 10 seconds, this can only succeed once hciattach has sent the
// firmware and then turned on hci device via HCIUARTSETPROTO ioctl
for (attempt = 1000; attempt > 0; attempt--) {
hci_sock = create_hci_sock();
if (hci_sock < 0) goto out;

if (!ioctl(hci_sock, HCIDEVUP, HCI_DEV_ID)) {
break;
}
close(hci_sock);
usleep(10000); // 10 ms retry delay

-- Starfox
[Touch Pro2, Tilt 2 Android Development] milda25:
kernel-pack-htc-msm-2.6.39.1-g8b00dce-dirty-20110619_212201.zip

With this build of kernel: kernel-pack-htc-msm-2.6.39.1-g8b00dce-dirty-20110619_212201.zip there is no sound (in call, no mic, no beep volume up/down).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, the newest acoustic code has been committed to .39. Sorry I haven't been able to keep up with development, been very busy at work + my laptop died so I've been 'away'...

So if you folks want to run .39, you'll need a system image with the new acoustic code.

Edit - I just updated the first post, here's hoping someone reads it.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
With the new acoustic code I was hoping BT would still work but it doesn't (I was using the 4/19 kernel with all the fixes before)...any idea if it is just a matter of removing certain fixes, etc to get it working or is it going to require a different method?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I saw some discussion on .39 & BT. Seems like it's not ready yet.

The audio routing is just that, improved audio routing. BT is separate, and only related in the sense of audio routing to the headset. So they are tied to eachother, but BT itself is its own beast. I haven't tested this yet myself.
[Touch Pro2, Tilt 2 Android Development] shatred:
How about camera support for rhod-100's with an UAO panel?

still kinda anoying to reboot back into winmo each time i want to make an picture :O

are there any devs. currently working on this issue?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for the off-topic... Might want to ask in viruscrazy's thread, he's the gentleman who did all the original cam work. He's going to be your best resource.
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
Is wifi still broken in latest release?