yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Thanks for the tip scoot, and I actually didn't know that, so that'll come in handy! :)

I'll be making a branch called htc-2.6.32-experimental.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Good stuff, there is a branch called scoot-experimental which I am using to slowly get an updated kernel to 2.6.37 spec, but it's pretty slow!

The guidance i gave you before will only create a local branch, to upload it to git just do this once you have the branch setup locally:

git push origin htc-2.6.32-experimental

Hope it helps :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Thanks for that... Spent about an hour trying to get it to push before I had to leave for work, lol!

I've got my branch pushed to git with my changes, so I'll be working on it seperately from the stable branch.
[Tilt, TyTN II, MDA Vario III Android Development] dany547:
when the RLS 6 will be uploaded ? :D
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Once I start working on the kernel, which will hopefully be this Sunday. I'm aiming for RLS6 to be a stable CPUFreq release. I have alot of splicing to do in the coding to try and seperate some key code from the ARM11 code that controls clock speeds, as we don't want to decrease the clock of certain devices like SMCC, Video, and NAND chip clock speeds. We just want those devices to sleep not decrease their clocks, as it will cause catastrophic issues with the phone (unexplained slow speeds, crashes, and other numerous issues)

I've got alot of work ahead of me, but my ultimate goal is to make it stable for all.
[Tilt, TyTN II, MDA Vario III Android Development] GoldKaiser:
@Krazy-Killa

Does its own ECC .....

Does this means that are no data corruption on NAND ?

Sry for bad English.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
YAFFS doing it's own ECC checking doesn't fix data corruption, only tries to delay it. Data corruption is caused by buggy NAND drivers which requires us to fix, but every developer who's tried ends up with a half-bricked or fully bricked device. I was one of the unfortunates with a half-bricked device, lol.
[Tilt, TyTN II, MDA Vario III Android Development] GoldKaiser:
So we need some testing devices

@ebay some used availible in my country ...for 40-60 € per device

We should open a new dev team for that and collect some donations for test devices ?

Im not very familiar with lowlevel programming ,but i can learn (im 20 years old :-) )

sorry my english is very bad due to im not using the language all the time ,but i will keep on learning ^^

PS : I can provide webspace
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
web space is avaible on source forge ( with codes and files)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm currently working on budgeting some spare cash to buy some damaged Kaisers off of Ebay for testing, and hopefully work on the NAND driver some more. In the mean time, I haven't had much time to work on the Kernel this week, but hopefully this weekend I'll have some updates.

And as far as Webspace is concerned, l1q1d is correct. Sourceforge is fine for me for the time being, and if I really need my own site, I can create my own server within minutes using a spare laptop I have laying around, so I have no problem with webspace. :)

Thanks for the offer though.
[Tilt, TyTN II, MDA Vario III Android Development] crzyruski:
Please accept my small donation, maybe it will help you in the long run.

I have yet to test your code on my AT&T Tilt, I will follow up with the results in due time.

Keep up the struggle of old device :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Thank you for the generous donation crzyruski, very much appreciated.

I've made some small progress with the Kernel. Isolated the issue to the cpu code for the kernel, so I'm setting my sights there now.

I'm also in the process of building a websie for my kernel. Got the server online and now slowly working on the site which is coming along nicely.

I know I haven't updated as much as I used too, but I'm hoping that will change in the coming weeks.

Again thank you for your donation, and thank you everyone for your constant support!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Did some minor work on the Kernel over the course of several days, and i'm going to be testing a new build I have made over the weekend to test stability and CPUFreq, sleeping capabilities.

If all goes well, I'll be releasing 5.9.2.2, which has a fix in the CPUFreq/CPU coding, that corrects the App Sleeps protocol of phone sleeping.

So far initial testing over the course of 2hrs with a battery levels of 25-30%, the phone is sleeping, and waking up correctly with Apps Sleep. CPUFreqing looks like it's working correctly, though the cpufreq folder inside the kernel is still not writeable inside Android, but I feel I can get that corrected with a update to Scoot's Froyo CyanogenMod 6.1.2 build. :)
[Tilt, TyTN II, MDA Vario III Android Development] Neo2SHYAlien:
Nice work dude. I thing Scoot's Froyo CyanogenMod 6.1.2 is the most perfect build and if will work with him will be very cool. Again nice work man.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Just a tidbit of information regarding stability.

I've been running my original RLS5.7 build which has 0 CPUFreq capabilities, and only the power management fixes for about 2 months now, with no issues in corruption or slow downs.

I've been running /system on my damaged NAND (107MB available on system), and a 128MB partition on my SD Card for /data using EXT4. I get an average battery life of about 16hrs per day with occasional use, and a 1hr of total phone call usage a day to my wife, and the time it's unplugged is from 6am to all the way to 11pm at night, and my phone charge is about 20% when I plug it in.

This is why I have not released a newer version of my kernel is because of the failure of my previous RLS5.9.1.2, which is not stable at all, and battery life is suffering drastically.

My next release, I can confirm will be significantly more stable than RLS5.9.1.2, and significantly better at battery life. I am in the process of testing this new release which so far I have had 1 crash while sleeping. Battery life has improved while phone is on, and battery life has improved while it is sleeping. So far the crash that happened was caused by a failed attempt at the driver to wake to report a new email. This has not occured since, but I am testing to reproduce the error to further isolate and elimanate it.

Obviously phone battery life is still a factor while using the phone. I had a one hour phone call with my family this morning, and battery life is weaker while on the phone with this release. I am attempting to use CPUTuner to tune the cpufreq to a lower frequency while the phone radio is in use, but I have run into a snag where the cpufreq variable files are not writable inside Android. This is obviously a build issue, and I'm looking at ways to allow our builds to write to the kernel files at will. :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
RLS5.9.2.2 is coming along nicely. Currently only crashed once in the last 6hrs, battery life is pretty good, especially for moderate use.

Will report more tonight.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Are you using the experimental RIL, or the traditional one?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I believe I'm using the traditional one, but in all honesty I'm not terribly sure. I've been modifying the original 2.6.32-9 Kernel before scoot seperated into a new branch to build his.

It's now 8pm, and my battery is at about 15%, still only one crash since 5am this morning, and about occasional use (turning on checking email every hour, made 2 phone calls, played with DROID sounds, heh.) Phone Standby occurs on the spot with no delay, and comes out of sleep without any delay. Phone's been running only 11% of this current charge, and screen has been on 6.8% of the time, phone calls only 0.3% of the time.

CPUFreq is working in the Kernel, but is not in Android itself. So Android is still reporting inaccurate readings (running at 384MHz constantly, and not transitioning speeds). This is a build issue that I'm unsure how to fix.

Any Android Builders interested in helping me work on getting CPUFreq built inside Android?​
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
What does it take to integrate cpufreq into the build?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
That part I'm not sure of. I'm still trying to figure out why Android cannot read the control files in the kernel.

My first guess is permissions, but I I've tried everything. Currently what needs to be done is that scaling_min_freq, scaling_max_freq need to have their ownerships switched from root root (user:group) to root:system, so that Android can access and modify those two files at will. From what I understand system is UID 1000, if "system" doesn't work.

Also when the OS is built, can you control what users are created at build time?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Update on the Kernel Testing.

Kernel is far more stable than my previous release, and Apps Sleep works beautifully. When no tasks are pending (background data, market downloading, email checking, etc), the phone will instantly go to sleep 99% of the time. The 1% of the time the phone usually crashes on sleep.

Will continue to test and hopefully have a release this weekend. :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
RLS 5.9.2.2 Released​

Includes much needed fixes to Power Management and stability. Also increased clock speed to 528MHz, which is the normal clock rate for the MSM-7201 processor.

Two versions have been released. One with a Boot Logo, and one without it (showing the ever so familar console screen). The Boot Logo version does not have access to the Boot Menu mainly because the FrameBuffer Console is disabled for the BootLogo to work. I have made Boot Scripts for most used types of installs (updates, system updates, full installs, formats, etc)

Please let me know how this performs.

NOTE: Android still does not recognize CPUFreq, but it is installed inside the Kernel and working. :)
[Tilt, TyTN II, MDA Vario III Android Development] cn2661:
hi Krazy-Killa mate,

thanks for your hard work, have been waiting for the new kernel for so long=]

Have downloaded it for further testing, so far it works fine, obviosly smoother than before

However I have a question concerning about the update file attached with NBH

actually what updates does it bring?

Im using Not So Super Froyo ROM, so far it works fine with the new kernel, Except when I apply the update file, then it fails to boot and Freezes on the X logo boot screen, some seconds after the key button led lights up.

whenever I recover from the backup file prepared before (which means to disapply the update file), it works without problem. Just wonder whats going on.

Anyway, thanks again for all your great job.
[Tilt, TyTN II, MDA Vario III Android Development] dany547:
nice man :d if you want i will meke u a nicer boot logo
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm actually re-working the bootimage so that way it's more flush with the background. If you can make one that has a similar layout and color scheme, I can take a look. Just make sure it's 8-bit, 240x320 and in PNG format. :)
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
I am testing your kernel too along with the RIL update...

First attempt was not good, killed my phone within 15 minutes after installing apps and updates and setting home to be forced in memory. Perhaps that just overloaded the CPU...

At this moment second install of my NSFF seems to be working nicely, I am going to make a full day travel so I'll report later...

Anyway... I hope this will not be the case with this kernel, but sometimes I have strange issue that noone was reporting ever... writing on the HW keyboard pushed the "chose special character for this letter" dialog and all the keys become blocked and even trying to write on the SW keyboard was always putting last letter written on the HW keyboard over and over... hope it will not happend with this one, but I'll let you know :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
It's possible the CPU was operating at it's peak 528MHz the entire time. Android likes to play tricks on the CPUFreq module at first load. Once everything up, and you reboot again, it should be good. :)

I'm testing right now with Thoughtlesskyle's Not So Super Froyo RLS18. Barely managed to install onto my NAND chip, lol. But so far so good. Froyo is running smoothly, and quickly. CPU Tuner is also reporting no errors in CPUFreq, so it has write access to the CPUFReq parameters, but CPUFreq still reports itself that the CPU cannot set it's speed, even though the MSM CPUFreq hack is changing the clock speed normally.

I am also running radio 1.65.18.21.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I also have had terrible results. I install everything on NAND, and whenever it crashes I am in the habit of restoring data from backup. After your explanation, I see that maybe I was hurting myself. I'll brave a reboot without a restore, and see if that makes things more stable.

The symptom I see is weird. Usually, my backed up data partition works fine for all my email accounts. After installing your kernel, and probably by coincidence, my exchange email stopped working: the account totally went away. I re-enter the credentials, and the phone syncs with email, but then like ten minutes later it's dead. No blinky lights, no keyboard lights, no light from the screen. I was away from a computer with adb all day, so I didn't capture a dmesg log.

I bet there was something about being pegged at high frequency, combined with the heavy utilization of a fresh email sync. I'll try again tomorrow with a reboot after the email restoration.

The other way I was crashing things today was by enabling compcache. That didn't kill it immediately, but again after like ten minutes after compcache really kicks in. But I haven't checked to see if you supplied the compcache modules that I use, so that might be it.

I have been using the new RIL with your kernel and my own personal fresh build of Fresh Froyo. (No, guys, nothing has changed in Fresh Froyo in months. I just like to build it weekly for myself.) Other than the crashes, very nice, snappy, with good phone performance.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I understand the crashing is pretty frustrating. With my own testing I've noticed a decline in the amount of crashing on my phone. Also, as I mentioned, I installed a Froyo build but it takes up 100% of my half-damaged NAND. So the phone immediately crashes after it's booted, and I get massive corruption in my /system partition. After installing /system on either a img file or the partition on the SDCard, my crashing literally stopped. Phone became incredibly stable, and speed was still pretty snappy.

With the Eclair build I didn't have this issue, but I had the issue of the occasional lockup every couple of hours or so, depending on the situation. With each crash, I haven't had the need to restore. Though mainly it could be because my data is on my SD Card, but my NAND is used by system at the time.

The root cause is up in the air at this point. It's either the power management, or the NAND driver. I really don't know. It could also be the new RIL, I mean there are so many variables for the instability differences on each phone.

As far as the massive drain in the battery, it could very well be the phone operating at 528MHz during sync because Android needs 100% cpu utilization (no idea why), during the entire time. Once syncing has stopped, and the occasional small syncs occur, everything seems normal. You could try using CPU Tuner (yes I know it doesn't report correct frequencies), and adjust the maximum freq of the processor to check battery life. With Froyo builds, CPU Tuner should have full rights to the CPUFreq parameters.
[Tilt, TyTN II, MDA Vario III Android Development] dany547:
i will come back to you in a few days with a bootimage :D,because now i'm a little busy
[Tilt, TyTN II, MDA Vario III Android Development] drfno1:
Been using 5.9.2.2 for 2.5 days now with a mod of Not So Super Froyo RLS18. Had 4 lockups 2 were black screen, 1 a white screen in the morning on first use, and 1 where it locked up and was displaying the home screen. Each time a battery pull and restart brought the phone up with no corruption or data loss.

An observation on the battery status. I noticed that it seemed to drain fast BUT when I restarted after a battery pull I was seeing that if the battery status was say 34% after the reboot it said it was 62%. Don't know if this means anything but it always reads more after pull and restart.

KK, I may have a kais100 motherboard that won't charge but the nand is good and the data connection works. PM me if you are interested.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'll have to agree with you. I have had 5 lockups today, all on black screen. Battery was at 34% as of 4pm this afternoon, and it was on since 630am this morning. I think it's mainly due to the constant lockups that are draining the battery faster, because during the boot, the phone switches to normal 384MHz, then once CPUFreq kicks in, it switches to 528MHz, and holds during the boot, then once everything's loaded, and phone begins to idle down, it drops to 123MHz.

I'm currently testing several iteration of ROMs, too see what the results are. I've used VanijEclair, Scoot's 6.1.2. RLS6, and now I'm trying Scoot's 7.0.2 RLS2. Attempting to confirm if the crashes are similar in nature across the board, or if it's based on the CPU load when the phone sleeps. After about 2 days of testing with this build, I'll switch to Myn's Donut build (with some modifications to sysinit and build.prop)

I've also made some changes to which I/O Scheduler the phone will use. I tried CFQ this morning, but it caused alot of lockups, and poor performance. Now I'm trying Deadline, and using 7.0.2 RLS2, and it's pretty snappy, compared to before where it was pretty sluggish.

Is it just the motherboard, not the full phone? What I'm looking for is a full phone that is in reasonable working order (nand has to be 100% though), that can be tortured. But let me know if you do have the motherboard, I might be interested. :)
[Tilt, TyTN II, MDA Vario III Android Development] drfno1:
I tried Scoot's 7.0.2 RLS2 and all the phone calls I received never rang just showed up as missed calls and voice mails other than that it worked great.

I'll know more the condition of the phone next week, I do know the mb works.
[Tilt, TyTN II, MDA Vario III Android Development] zxxxy:
Wow Krazy Killa! A Very ice kernel so far! Still has some minuses with waking up... for me sometimes pone shows "no service" when service is aviabile, Free RAM is very random with auto killer: from 20Mb to 60Mb (wonder why) .. With this kernel and darkprince's "myFroyo" (which i've modded a bit) i can watch youtube and play angrybirds!!! Very good job! Keep up the good job, please, and if You can, please try enabling autifocus =D
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
OK, my report after few days running Sys-NAND/data-SD...

No corruption in NAND, because there is only System partition...

Data on SD are still using Ext2 and seems to be pretty stable...

Phone freezes every and each time trying to sleep, sometimes even when starting some app, like Trillian... I have to press reset and then power button to make it boot again... So it makes my phone totally unusable :( Damn phone does not run even about an hour without freezes...

So... what do you need to find out what is happening to me? Any log or something like that? I do not have any other issues, just those freezes that are making me crazy :(
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
After some changes to how I use my phone, I've managed to bring down the amount of crashes to about 2 a day. I'm still using VanijEclair build, with some slight modifications to it's userinit.sh and build.prop.

As far as EXT2 being used, that is too be expected because I did not include the EXT4 Formatter in my init scripts. It formats the partition as EXT2 but mounts it as an EXT4 partition on startup. Android is correctly detecting EXT4, but Linux will detect it as EXT2 as it is formatted using an EXT2 formatter. I will be modifying my init script to be compatible with l1q1d's atools, so you can go between EXT4 or EXT2. :)

Trillian crashes my phone if I leave it loaded when it sleeps. Hell, having any apps loaded in background causes the phone to crash on sleep.

This weekend I'm going to try and use Power Collapse as a sleep option too test what happens, but I'm pretty confident that the same results as before will happen.

I'm starting to think it's an issue with the phone's CPU usage spiking just before the phone sleeps, or spiking when it wakes, which could blow up the timer for the Apps Sleep protocol.

I will do more testing this weekend.
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
OK, let me know if I can help in any way, cause I am really enthusiastic about your work, but not skilled kernel dev... ;)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I will be posting some modified changes that need to be made the sysinit.sh file in all the froyo and some eclair builds involving CPUFreq permission modifications.

They are not needed with my kernel as the kernel sets the permissions on boot. Also, I will be working on a possible fix to why the phone crashes on sleep. So far everytime it crashes is when the LED is used for notifications while sleeping. I will attempt to disable the sleep LED, as I can confirm, verify, and with absolute certainty the phone will sleep 100% of the time when the power button is pressed. Only time it does not is during sync, music playback, etc.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
I can add a button to atools if it's a simple modification

:-)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I believe it's an easy fix. There's an LED function imbedded in the sleep function that causes the left LED to blink every 4-5seconds. Some applications use that LED (Trillian), and since my sleep mode is highly sensitive to how the phone is being used when it wakes and sleeps, this could very well fix the issue that's been plagueing this Kernel since the implementation of CPUFreq.

I'll report this weekend of my results, and if it's an easy fix, I'll see if I can configure the code to adhere to the kernel's current boot variables. :)
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
Would that mean, that setting trillian to use different LED would help or is the issue independent on which one is used and phone will crash on trying to fire any of them?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
How is this work going? Have you made any more improvements? I think the last beta was a good step forward in performance and battery life, but it suffers from the general instability that we have had. I think that recently we've all been using Scoot's kernel with the separate cache, since it seems to be a huge improvement in stability. I'm hoping that you can combine his changes (mostly initrd I believe) with yours and keep developing a cpufreq solution.