yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Not seeing any noticable changes in the CPU, though OSMonitor still reports 0 CPU Scaling occuring. (reading files in /sys/devices/system/cpu/cpufreq) But we are making progress if the cpufreq module is in place and running. :D

We probably won't see anything until the necessary parameters are put in place, but IMO I would create a symbolic link with the CPU Max setting with the actual cpu scale set by the kernel, that way we can still overclock the cpu without the scaling overwriting it and reverting back to default 400MHz.

I would help but I have no idea how to setup a git. :(
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
There are a few posts on xda to download the kernel source from git.

If you need, PM me or Clemsyn. He's been quite helpful to me :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
My /sys/devices/system/cpu/cpufreq folder is still empty. Maybe we need to put some files in there? Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Clemsyn, would it be a abuse to ask you to paste your .config ?

Update:Nevermind that, remembered /proc/config.gz.

Now, i've.. stumbed in this:

-CONFIG_MSM_CPU_FREQ=y
-CONFIG_MSM_CPU_FREQ_ONDEMAND=y
# CONFIG_MSM_CPU_FREQ_SCREEN is not set
-CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=384000
-CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=245760

From here:

http://android.git.kernel.org/?p=ke...ff;h=4f4cc8dd32ca49f99e6dbf1157fe6ed83afed768

The max and the min is not present on our code...
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Yep that's what we need, but we also need to build the CPUFREQ module for our kernel as well. I found several sites that have the source code needed to build the module, though you can run a search for "CPUFREQ LINUX", and come up with the results.

*EDIT* Either daedric or clemysm PM me the information I need to get on the git as well. :)
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Clemsyn, i can't compile the kernel (and even if i could, i do not know how to make it into a nbh). But if you can, would you kindly enable ALL under the CPUFreq ?

[*] CPU Frequency scaling
│ │[*] Enable CPUfreq debugging
│ │<*> CPU frequency translation statistics (NEW)
│ │[*] CPU frequency translation statistics details
│ │ Default CPUFreq governor (ondemand) --->
│ │-*- 'performance' governor
│ │<*> 'powersave' governor
│ │<*> 'userspace' governor for userspace frequency scaling
│ │-*- 'ondemand' cpufreq policy governor
│ │<*> 'conservative' cpufreq governor
│ │<*> 'msm7k' cpufreq governor
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
So the kernel had it the whole time just wasn't enabled? O.o
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
K, will do when I get home. Btw, I don't remember seeing that msm7k on my kernel. Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
The kernel as cpufreq since its first version. 2.6.0000000000000000

It doesn't really matter to enable it, if the kernel cpu code is not compatible with cpufreq.

You can run the kernel 2.6 on a original pentium, but even if you enable cpufreq, you won't get frequency scaling. I belive... we lack support :( but we might steal it from android.git.kernel.org :D

I meant support, not on the cpu, but on the code :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm pretty sure our devices support scaling. Granted its a different OS but WinMo scales the processor fine.

I think all we need to do is build the cpufreq module and then modprobe it into the kernel then activate the necessary features that are present in the stock android kernel. :-)
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Please confirm information, when you get home.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Here it is daedric..I don't have the msm7x cpu governor though. BTW, this kernel is experimental and still recommend kernel on post 173.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
I have no clue... can you RE-download from the git ? to a different dir ?

i've followed you're instructions as per PM to the letter, and downloaded from the SF.net git...

I have no clue.

i'll give you what i have:

The msm7k governor is based on the conservative governor
with some hacks specific to the msm7k.
Symbol: CPU_FREQ_DEFAULT_GOV_MSM7K [=y]
Prompt: msm7k
Defined at drivers/cpufreq/Kconfig:105
Depends on: <choice>
Location:
-> CPU Frequency scaling
-> CPU Frequency scaling (CPU_FREQ [=y])
-> Default CPUFreq governor (<choice> [=y])
Selects: CPU_FREQ_GOV_MSM7K && CPU_FREQ_GOV_PERFORMANCE

file:

kernel/drivers/cpufreq/cpufreq_msm7k.c

Hint:

/* drivers/cpufreq/cpufreq_msm7k.c
*
* based on:
* drivers/cpufreq/cpufreq_conservative.c
*
* Copyright (C) 2001 Russell King
* (C) 2003 Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>.
* Jun Nakajima <jun.nakajima@intel.com>
* (C) 2004 Alexander Clouter <alex-kernel@digriz.org.uk>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
*/

And... at the end:

MODULE_AUTHOR ("Alexander Clouter <alex-kernel@digriz.org.uk>");
MODULE_DESCRIPTION ("'cpufreq_conservative' - A dynamic cpufreq governor for "
"Low Latency Frequency Transition capable processors "
"optimised for use in a battery environment");
MODULE_LICENSE ("GPL");

Doesn't match... must be a hack of some sort... problem is, WHERE THE HELL DID I GET THIS ???
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I have this too, though I'm still making heads or tails of all this, plus trying to figure out how to compile, luckally my laptop is already configured for compiling as I have to compile my wireless adapter drivers everytime I update my linux kernel. :(
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I'm still quite happy with the kernel in post #63. It has never yet crashed for me. If I pull the battery or open the SIM card door, it recovers without loss.

If I shut down "cleanly", it does have some corruption, usually in Dalvik cache.

It is definitely more stable than anything I build myself from the git repo.

Perhaps I am using an older toolchain? I use the one that comes with the Fresh Froyo repo, in android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
is there any change on the kernel to commit to the git?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I've been trying to build my own kernel lately, and so far all I get are crashes during boot. Don't even get the press center to open menu part. :(
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Do you have latest bootenv and tinboot?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Um, as those don't ring a bell, it'll be safe to say that I don't. :P

I mean it compiles without a problem, just when I try to use the zImage for HaRET it crashes before the press center for menu.

Also out of curiousity, how do you build a kernel for NAND flash?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Oh you are using haret. Maybe the log file will give a clue. Or maybe you need an updated initrd.lzma from bootenv.

In same sourceforge place as the kernel you can find tinboot and bootenv. Bootenv has the initrd, tinboot builds an nbh file from the parts.
[Tilt, TyTN II, MDA Vario III Android Development] 79bass:
New Nand Driver

Hi,

It was a while I wasn't updating my Kaiser... I never had time, but I was waiting the next data corruption event to erasing everything and setting up the new initrd, and new juicy stuffs.

Ok, downloaded new kernel (29-11 and other from forum) and new atools.

First big problem, I can't set up the right panel anymore. Use to have panel 1, but now ot the setting are not applied anymore or something wrong with the kernel. nor panel 1, 2 or 3 are right, nor "Auto" option is working.

Then can't install system on NAND anymore, (device is not existing). So it is not a matter of unapplied update (I can't with no nand partitions), I guess it's a kernel problem.

I've browsed a little in the forum but haven't found a solution if not downgrade :( kernel.

I'm not an expert on mobile device.. I can't have the device ID of my hardware (something like lspci doesn't exist?).

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] mr_ppp:
I've found myself if you have the simple battery option ticked it ignores panel type no matter what you do, it took me ages to realise this, changed it to advanced and entered my battery mah and now it works, might be the same problem? Never had a problem installing on NAND though!
[Tilt, TyTN II, MDA Vario III Android Development] 79bass:
Whaaa, that was quick...

The battery option fixed the problem.

I was using atools from git.

I used the simple setting because once upon a time was a fair way to adjust the battery but now this option should be fixed or removed... In fact it screw everything with new kernel in my device.

thanks for the tips

Best regards

Francesco
[Tilt, TyTN II, MDA Vario III Android Development] vinny13:
Can someone convert this to a Vogue kernel for me? Atools won't work... Can't get edited kernels to properly install to the nand for unknown reasons...
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
I cant do the conversion in Hex Editor since those two are totally different (POLARIS and KAISER's worked for me by just changing the POLA100 with KAIS**** in the 3rd line). I'm really sorry of not being any help :/ (I feel it since I'm looking for the right support and trying to figure out stuff all on myself)

Atools isnt working for me too (python installer is deep-sh** with AMD's processors), and no one out there is really into making nbh's for us.

This is punch line for me. Ofcourse I fall in the stupid category coz I cant run Atools good as you "CLEVER: people do.

The only hex edited version I was able to do on myself was a random shot to DZO's repository with some hex editing and Fat Free Froyo (the only wifi working combo). Rest all tests with about dozen kernels and half dozen distros out of eclairs and froyos FAILED. (Wifi failed to start).

My Device is KAIS130 HTC TyTn II, Panel Type 1. Now I will be trying Donuts soon when I'm piled up of pathetic WM bugs.

kthxbai
[Tilt, TyTN II, MDA Vario III Android Development] peter s:
recommended toolchain

@l1qu1d:

could you please share the git for your htc-vogue 2.6.25 modifications (source) and the toolchain you used for your releases? (forget the latter if it was arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu)

@all

am i the only one with 2.6.25 and sd-card mounted twice (once on /sdcard by /init (initrd) and once on /mnt/sdcard by /system/sysinit.rc (or vold respectively)?

thanks!

peter
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
The /sdcard is a symlink to /mnt/sdcard. You can not mount a single device more than once. But you can create "shortcuts" to the mounting directory.

Though I wouldn't mind giving the 2.6.25 kernel a looking at, as I really like the stability.
[Tilt, TyTN II, MDA Vario III Android Development] peter s:
right but wrong :)

/sdcard is created on boot by /init from initrd. /system/sysinit.rc creates /mnt and /mnt/sdcard and attempts to ln -s /mnt/sdcard /sdcard - but fails, since it is already there and in use as a mount point for /dev/mmcblk0p1

the reason why dual mount is possible: there is a second logical device (/dev/block/vold:bla) using the same physical device...

i would like to fix the init script in initrd, hence my questions above.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I have no problems with accessing the sdcard however, but I see what you mean.

My phiosophy on stuff like this is... If it ain't broken don't fix it.

What are you trying to do? I mean the sdcard mounting works fine.

Technically you can just modify the sysinit.rc file of the build you're using to do a symlink instead of mounting sincethe kernel already did it, so this is not a kernel related problem but a specific build problem.
[Tilt, TyTN II, MDA Vario III Android Development] peter s:
not quite, since the vold mount from /system/sysinit.rc is hotplug-compatible while the mount from the initrd init script is not.

plus, /sdcard is only there for backward compatibility - /mnt/sdcard seems to be the preferred mountpoint. there is even some attempted setprop-magic in the sysinit.rc to let vold know the card is mounted already. i assume this fails because of the different mountpoints (or possibly due to the different device names). i would like to experiment with this and other init related stuff.

precisely it is neither the one, nor the other. to me it seems this is a missing (small) update/fix in initrd or its init script respectively. therefore it should be relevant for all android builds at least from froyo onward.

apart from all this, i consider it bad to have one physical medium mounted twice.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
I've been gone for awhile. I was wondering if there were any kernels I should be looking out for in here or if clemsyn's changes were finally commited to git.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Nope, no new kernels since your last post. Not sure about it being committed to git though. :(
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
i didn't use a complete toolchain but only the android ndk (from android developer google site).

For the 2.6.25 sources look in the git (my sig)
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Been quiet on the kernel front lately hasn't it! I've got 2 exams in the next couple of days but once they're done i'm hoping i can finish up a few of the things i started before christmas which were all kernel related, so fingers crossed they don't dump a load more work on me for a bit :)
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I really like the post 63 kernel, which is git sources 2.6.32 branch but with CONFIG_YAFFS_DISABLE_BLOCK_REFRESHING=y. So i have been silent lately.

I have gotten tired of the keyboard backlight being not quite right, though, so I think I'll commit a change. What I'm running now ignores the light sensor completely. I'd like to be able to turn on the backlight by covering up the sensor, though. Also, arrow keys dont affect the light but the keys surrounding the dpad do. So more work needs to be done there.
[Tilt, TyTN II, MDA Vario III Android Development] papatel:
I've tried about 10 different .32 kernels for my tilt running froyo builds and the only one that does not corrupt my data or crash repeatedly on a NAND install is the one on post 63. Top of tree corrupts my data within a few reboots and I get crashes frequently.

This is also my favorite kernel so far :)
[Tilt, TyTN II, MDA Vario III Android Development] X46X:
Hi,

I mean, latest .25 kernel download with a-tools yesterday DRAIN BATTERY very quickly..
[Tilt, TyTN II, MDA Vario III Android Development] Neo2SHYAlien:
Huh for me latest 25 save battery too much :)
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Would anyone object to post 63's configuration getting checked in to git? I think that makes sense until somebody has a kernel that works better.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
PLEASE DO! I hate having 6-8 hours battery
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
i release on 16 a new kernel with the dzo changes, i'm still waiting for the 63 changes.
[Tilt, TyTN II, MDA Vario III Android Development] X46X:
Please, how I do Backup and Restore? :o
[Tilt, TyTN II, MDA Vario III Android Development] seancojr:
You boot into the menu where you would normally install and select "Backup Data" then repeat the process again but this time choose "Restore Data" as the option.
[Tilt, TyTN II, MDA Vario III Android Development] X46X:
If you mean Back up my data in Settings/Privacy I mark it. But I dont see Restore my data. I see Automatic restore (this is not marked) and Factory data reset..

EDIT: Oh sorry, I'm stupid. You mean boot menu, of course. Thank you!
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Battery temperature now available

Thanks to V3rt!g(o) we have a conversion of aux0 to temperature.

It may be crude, and require calibration, but it seems close at least.

I just committed the change to board-kaiser-battery.c
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I'm back! Didn't realize our device was pushed back to legacy now :) Anyways, I got a G tab and was quite busy updating the kernel and playing with the device. I have to say, it's a pretty impressive tablet. I just built a kernel for my wet Kaiser that is still chugging along. Here are the changes I made.

1. Loosen up some Yaffs setting to improve speed

2. Decreased kernel log buffer size to 32

3. Enabled Block layer SG support to v4

4. Enabled Block layer data integrity support

5. Enabled CONFIG_UACCESS_WITH_MEMCPY

6. Enabled Installation of FIQ hander

Please give me input on how it goes. Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
I will be testing it later today. Thank you for the work clemsyn! If it goes well can you hand me the code you used that way it can be committed to git?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I'll try to incorporate this module to our Kaiser...Any advice will be greatly appreciated. n2jrt, would this have any issues if I mix this in with your battery module?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Will do :) OK, I added the module above by editing proc_comm.c, then adding proc_comm.h. Then edited the makefile and I was to build the kernel with that support. Not sure if it's placebo but the screen looks better (most likely placebo). Will continue testing before I release it.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Sweet deal, if it all works out, I'd be interested in testing it. I'm currently using 2.6.25 l1q1d's kernel at the moment, for the sake of stability, until a kernel comes out with improved power management, which from the sounds of it, you may have it. :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Will release it in a few hours. It really looks like the screen is more vibrant.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Great, and when you release it I'll make sure that the code gets committed to GIT so we can have your additions and our battery life lol
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Looking forward to it! :)

I've been completely unsuccessful in compiling my own kernel, so I'm looking forward to this.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Here it is...Please let me know if you screen is better or if it is just a placebo on my part :) BTW, looks like battery gauge was pretty accurate, died a few minutes after 0% and didn't even edit it with atools. This is type 2 screen and type 1 keyboard so edit it accordingly. I also found a newer module so I'll try this module too.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
No issues, please do what you can to improve our great old phones! It's not MY battery module, it is OURS. Just be sure to pull down the latest code so we dont lose the new temperature sensing feature. Thank you so much for your work. Please commit and push changes to git, or send them to someone who can.

The "post 63" kernel has been very popular.

Are the changes represented by that kernel committed to git? Was it just a config change, or were source changes also involved?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
RE: 63, they were just changes in the config.

Anyways, I've been looking more closely in the kernel folder and found another module (proc_comm.h) being used by vogue_smd in a different folder...not sure how it is going with the new module being introduced....
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Backing up data now, then flashing new kernel..

Will post results by tonight! :)

EDIT: Ok I'm not sure what you did, or how you did it, or possibly this module fixed it, but my camera now works with 2.6.32 kernel!!! Took a picture, phone didn't crash, and still going. Now my phone did run out of memory, and had to reload the launcher but other than that, it WORKED!!!! O.O I will edit this post again tonight when I do my daily use of it, and report what I find. Also don't really notice anything different with the screen, it could be crisper but then it could be my imagination trying to convince me of something. Will report tonight on my findings!
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Glad we finally got your camera working. I still think the screen is more vibrant everytime I look at it but your right, could just be my imagination :) More input about the kernel is appreciated. I just have a feeling that a reset is better than turning off the Kaiser since there are 2 modules (haven't turned off my phone or reset it coz I'm testing on how long it goes). Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I haven't noticed a change in battery consumption (seems the same too me), which makes me believe this module merely activates the secondary CPU used for phone calls and radio, and I've noticed a performance gain which could support this theory of mine. Alot of apps load alot faster than normal, menu response is quicker, no haptic feedback input when I tap the screen, but I haven't fully tested this part yet, lock screen haptic feedback works however.

All my apps were corrupted, at least in the data partition when I restored my backup, so I'm in the process of reinstalling everything at the moment. Apparently the 2.6.25 kernel doesn't even recognize corruption, which could be why it seems more stable, but with that kernel everything did seem to slow down after awhile, which could be corruption anyhow. But after the firmware update, every app in /data was completely corrupted, had to uninstall then reinstall the apps to restore functionality. Lost my sync with Google as well, but most settings remained (wifi settings, bluetooth, screen brightness). Though my ringtones got completely messed up. When I received a text message earlier, it started playing a phone ringtone sound, so it kept looping until I checked it (people at the grocery store were looking at me funny, cause I was looking at my phone weird going 'wtf is this' lol!)

CPUFreq still doesn't seem to be activated, but at the moment not worried about it as I'm testing stability now more than anything.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
If so then that would explain the performance gap between my build overclocked @ 572 mhz vs the dream. I am going to flash it here in a minute or so.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Yah the Kaiser has 2 CPUs built into it's circuitry. One that controls the Operating System, graphics, etc. The other controls the phone's radio, and if any phone applications in the OS. Windows Mobile makes full use of this feature, that's why it's phone app runs so fast, it's on a completely different pipeline than the OS itself.

Now if the secondary CPU is not active, then everything in theory will default to the primary MSM7200 CPU, which is being loaded enough as it is. The Secondary CPU runs at 272MHz, which is more than enough to run the radio. But again, I haven't received any phone calls lately to confirm this, but my wife should be calling me on her lunch break in the next several hours, so I'll report then if the phone app responds faster to incoming phone calls.
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
Still havent been able to test. The kernel has the new menu which wants the mounting to be configured by atools and im having a hell of a time getting sys on nand and data on img working.