yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
I was using the release made before making cpufreq one, i installed this new scoot CM7 RLS 2 and after about a half of a day(from yesterday night to today midday) it broke in some way. I can't boot my kaiser, when i turn it on, the bootloader screen goes on, after that the linux booting starts and phone turns of after a second or even less(when booting).

I'll try newest kernel now and post results.

Btw. - will the android installer be updated? Is it possible to add options to install different builds or updates without changing it's names like it is in recovery in spica for example?

EDIT: one persistent question: If i'm using data on sd and system on nand, can I use whole nand for system, not only half of it? How to do it, because i can't see this option in atools.

Thanks everyone for your hard work!

EDIT2: I flashed a newer kernel, i still can't boot my phone!

It is acting weird, f.eg, it flashes sometimes with its lcd when it's plugged in a charger.... If it's a hardware issue i will be pissed off like hell, because it was doing fine.It behaves normal in bootloader mode etc, maybe I'll just try flashing WM...
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Did you make sure your battery has a good charge? One reason Android will half boot and shut off is a dead battery. But yah make sure you are plugged into an external adapter that provides power to the device before flashing the new kernel just to be safe.

Under atools you can adjust the size of your NAND space to use more system or more data by checking "Alter system and data partition", then directly to the right, you can adjust the slider for System/Data Partition. I use 100% of my NAND for system due to a bad NAND chip, and the rest on SD Card for data.

I do not plan to update Scoot's CyanogenMod build as it is out of date. Just download a Build here on the forums, and install the androidupdate file under the Startup Menu by choosing "Install Update", and you'll be good to go.

*EDIT* Sounds like a dead battery. Also if the phone is off and if any Linux Kernel is flashed onto the phone (this includes other kernels as well not just mine), Linux doesn't know how to keep the phone off and charge the phone, so the phone will boot back up without the screen on while it is plugged in and off. So the white screen after it shuts off is just the phone powering back up.

And I would definitely recommend putting it in bootloader mode and letting it sit on the charger as it is very possible the battery is dead. Then after it sits for about an hour, flash WinMo back on to the phone, and check your battery level after you have booted to it.
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
here are the measurements:

1.65.16.25, backlight on minimum

wm 6.1:

idle, radio off - 110mA

standby, radio off - 3mA

idle, radio on - 115mA (ticking +/-3mA)

standby, radio on - 5mA (50mA tick every 5sec)

killa 5.9.1.2, sleep mode - apps sleep:

idle, radio off - 110mA (random jumps to 150mA)

standby, radio off - 3mA (110mA jumps every 20sec, could it be ds2746 probing??)

idle, radio on - 110 (150mA tick every 5sec)

standby, radio on - 5mA (15mA ticking, every 30sec jumps to 120mA and holds for 5sec)

killa 5.7, sleep mode - power collapse:

idle, radio off - 110mA

standby, radio off - 5mA

idle, radio on - 110mA (150mA tick every 10sec)

standby, radio on - 5mA (50mA tick every 10sec)

2.6.32 from git:

idle, radio off - 110mA (random jumps to 150mA)

standby, radio off - 3mA

idle, radio on - 110mA (jumping to 280mA

standby, radio on - 5mA (ticking to 15mA)

the values are all quite close, so i really dont know what's draining the battery so much compared to WM values :confused:
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I see that with the original 2.6.32 kernel, with the radio on, there's a massive spike of 280mA, but with my two kernels (even the one without CPUFreq), it doesn't make that massive jump.

Plus it seems my CPUFreq kernel is about on par with WM 6.1.

Not sure about the 120mA jump every 20seconds, and don't think it's ds2746, as it probes every 5secs. Could either be the mddi (frame buffer) updating itself, or the kernel getting an update on RTC.

Either way, I'm liking the results, especially the 3mA with radio off. :)

Try flashing 1.71.09.01, as I'm using that and it seems to do alot better battery wise, and seems more stable.
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
I tried charging the battery without resuls, I flashed WM6.1 and it looked nice, but it said that the sim card isn't locked. That gave me an idea. I unlocked it and locked one more time, it looked like WM is workng fine, I flashed the newest kernel but changed the /system size to max. I installed CM7 rom but it froze after a while, then I installed an update that came with the kernel(huh, .tgz instead .tar isnt a problem for installer? I hope so). So now I have a loop with untracked PID x 2. I tried reinstalling and wiping /data and it isn't working.

Is it a kernel or build issue? I hope that at least CM6.1 build will work fine.
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
Yeah, i was wondering about that 280mA spike. wierd, could be some process, allthough i tried to kill everything possilbe...
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Try flashing Scoot's Froyo CyanogenMod 6.1.2 build. That to me is pretty stable and pretty quick.

I'm unsure why you're having so many problems, but did you put in 3.34 or 3.56 HardSPL? And what Radio ROM do you have loaded? 1.65.xx.xx is recommended, but I recommend 1.71.xx.xx for my kernel. But in all honesty is based on choice and which radio gives you best service for your area.

Yah I'm not sure either, but for an alpha release this is pretty good progress, and definitely going to iron out as much as possible to get this Kernel as battery efficient as possible
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
it didnt survive to sound the morning alarm :p

So, there is something happening every 30sec when it draws 120mA for 5sec.

During that 5 seconds, i can wake up the phone on any button, which means it goes out from sleep mode to do something...
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'm at my overnight job testing battery life and mine crashed twice while in standby. Granted I'm on 4 hrs and I'm down to 68percent which isn't bad for moderate use.

I'll do some code checking when I get off work and see what's making the phone wake every 30...... It's the background checking! Turn off Background push and see if it stops the 30sec wakeups.
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
Background push? Like disable bacgkround data under accounts settings? Did that, still waking up every 30sec.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Hm, well it was worth a shot, lol. I'll check everything when I get home. Battery s now at 63percent. :D
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
I have a 3.34 hardspl and 1.65.16.25 radio or similar. It looked like it wasn't doing weird things when WM rom was flashed(i didn't test it much anyway), after flashing the kernel it came back. I'll try flashing 1.71* radio, flashing the kernel one more time and installing this CM6.1.2 build. Maybe the problems are caused by setting whole nand for /system? I didn't have too much time yesterday for testing.

Oh, and I think the battery is doing fine. I made a movie that shows what is going on with the phone connected to charger. Maybe I'll upload it so you all will know what's going on.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I installed RLS5.9.1 Thursday night, with a CPU Tuner app, then checked out of the hotel at 7AM Friday. The phone refused to wakeup during breakfast, so I rebooted after playing with buttons for two minutes. After that, I used the phone for normal stuff (mostly email), and the battery does seem to last longer. By late afternoon, just before a six-hour cross country flight, it had 30% remaining. Spare Parts told me it had been running about 30% with screen on maybe 5%. During the flight, I kept it in airplane mode. After four hours, I checked, and it had 20% battery remaining. Spare parts said it was running 10% of the time. After 5-1/2 hours, the phone refused to wake up. Upon reboot, it had 12% battery remaining. One thing I wonder about is that every time I checked with CPU Tuner, history showed that it had been running at high CPU speed 100% of the time. Maybe I haven't configured that app correctly.

Today it again wouldn't wake up. I usually can tell when the kernel has crashed, because the Fn key won't light an LED. So this morning, no LED, no response to any key. The last few lines of /proc/last_kmsg read:

[28614.448425] PM: Syncing filesystems ... done.

[28614.488403] PM: Preparing system for mem sleep

[28614.723693] Freezing user space processes ... (elapsed 0.05 seconds) done.

[28614.800903] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.

[28614.818328] PM: Entering mem sleep

[28614.823638] Suspending console(s) (use no_console_suspend to debug)
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Freezing

My tilt is freezing on "Press and hold Voume Up or DPAD..." screen after flash rls 5.7 (latest stable from first post).
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
If you're still using your "modified" cache setup for downloading apps, try disabling that and booting up. As l1q1d and now me have stated, it is not safe to do a symlink of a specific directory on NAND as you run the risk of over read/writing that area of the NAND in comparison to the rest of your NAND as it HAS to be evenly read/written at all times, and therefore possibly damaging that section of it permanently or even your entire NAND ROM therefor bricking the phone permanently.

Yah I've noticed that too with CPU Tuner. But for the most part CPU Tuner is reporting inaccurate readings as it has 0 write access to CPUFreq inside Android, but the Kernel has full access.

My phone was also doing this last night. After it would be in standby for about 15-30 minutes, it would freeze. Some cases it would recover, other cases it would just not blink. And in some other cases the right-side LED would blink very fast (indicating a notification). Though it sounds like when it suspends a certain device, that device will (due to a bug somewhere) refuse to allow the phone to re-wake. I'll be looking at the code tomorrow as I'm too tired to do so right now... Been awake for 36hrs now, and can't wait to go to bed tonight.

Overall, in a field test, battery life does seem to be improved, and I'm overly impressed despite the instability.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
The phone not even pass thru "Press and hold volume..." screen and i'm not using this script anymore.

Right now, i'm using original scooters CM 6.1.2 rls 6.
[Tilt, TyTN II, MDA Vario III Android Development] oroo708:
storage NAND

just wanna ask something...

what actually does ur kernel do to NAND storage memory(ROM) when installing android on NAND..does it make any partition that change the format or something..

when I flash back to WM,my ROM memory reduced..

does this happen only to me??need some confirmation...

thanks
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
After normal daily use, overal battery performance is quite good. I don't think it can get much better.

As for standby. It drops 10% every 3 hours. Allthough it never reached low battery notification. It usually hangs (buttons not responding, can't wake up, qwerty backlight is active), or drops dead during 5 or more hours of standby.

Take a note that often flashing/reinstalling on NAND wil create bad sectors through time.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'll agree with you on the NAND bad sectors, but also the more times you flash your NAND the more "clutter" gets on it, and the less space you get until you have to "low-level format" the NAND, which comes the risk of permanently bricking it due to it wiping everything.

Yah, I think I've just about improved battery life to the point that it will last quite a long time now (possibly to where it needs to be for Android). Now I just gotta stabilize it so we can at least keep it in standby for as long as we want without it hanging, lol.

I'll see if I can push my changes to git now, as I did a stash of my changes before pulling updates from git. So now I have the updated yaffs. :)
[Tilt, TyTN II, MDA Vario III Android Development] Tamarinde:
Just wondering if your new kernel is going to be safe to use on nand, your previous one seems to have killed a few blocks for some people.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Yes, my Kernel is safe to use for NAND users as any other Kernel. The driver is exactly the same as all the other Kernels out there, because I reverted after I damaged half my NAND in under 10 seconds. lol
[Tilt, TyTN II, MDA Vario III Android Development] Tamarinde:
I am impressed by the developments you have been making so far and I cant wait for a stable release.

I was actually thinking of just switching to a native android phone so its more stable(and more memory).
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'll continue development until I make it as stable as possible. Right now I believe I managed to commit all my changes to git but so far I haven't seen it update on the site.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
If you had committed correctly it would update immediately, maybe you did not do git push after committing?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I just tried but I get an error saying the remote end hung up unexpectedly. O.o
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
You have to have the git checked out with ssh protocol, not git protocol.

I don't remember for sure, but something like the kernel/.git/config file should maybe be:

[remote "origin"]

fetch = +refs/heads/*:refs/remotes/origin/*

pushurl = ssh://krazy-killa@androidhtc.git.sourceforge.net/gitroot/androidhtc/kernel.git

url = git://androidhtc.git.sourceforge.net/gitroot/androidhtc/kernel.git
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Ok, I should have this taken care of either this evening or tomorrow.

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I have successfully commited my changes to git. Though I think I accidently did a merge of the same file, lol.

All my changes are now on git, so if anyone wants to take a look feel free. :D
[Tilt, TyTN II, MDA Vario III Android Development] TuoNonno:
Very impressive work, even if I've switched to another phone I continue to follow you and your thread because when it will be stable I'll switch back to our beloved kaiser :)
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
I still have lot of problems with my android on kaiser. When starting there are a lot of lines with "PM". Animations are smooth but apps are starting veery slowly, some of them can't even start(osmonitor). I don't know if that is a hardware issue, phone is still going mad when I'm trying to charge it without turning it on, it flashes white on lcd and the charging led goes off(? turns off) permamently.

I use chinese flex cable, original one broke some time ago. Maybe something is not connected properly? It was fine for some time.

I'm using 5.9.1.2 kernel, I don't know git's adress, because i can't find it on androidonhtc git.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
The PM: messages are normal. They're just diagnostic messages indicating that the specific components are now powersave enabled and should go to sleep when the phone does. :) They will be turned off in my next release however, as I've done what I needed. :)

Yes, and again that's not specific to my kernel, all our kernels do that as it's an issue with the kernel not being able to recognize that the phone is off when it's plugged in and needing a charge. When that happens the phone turns on without initializing the video drivers correctly.

Not sure why apps are loading slowly but then again it's based on your SDCard class (if you installed on SD Card), or if you have CompCache enabled. I highly recommend enabling CompCache after installing a build (if it supports it), as it provides extra memory for the phone to store apps in memory. :)

I have been unable to load OSMonitor as well, don't think it's specific with my Kernel or not, but I haven't really tested OSMonitor as much as I want as I found CPU tuner to be alittle better, despite it not reading CPUFreq correctly.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
OSMonitor works for me, your RLS5.9.1.2 with Fresh Froyo. What doesn't work with your kernel is USB tethering. I think somebody else broke that a few months ago. The kernel I have used a lot recently, made by Clemsyn in January, does USB tethering just fine. I've been meaning to look into that, but my day job keeps me busy recently.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Hm, I'll se if I can get ahold of clem and send me his changes so I can get it into git. :-)

Plus I'll be working on the kernel this afternoon to attempt at fixing the sleep crashing bug. Plus work on any requests and other bugs (Usb tethering for example). :-)
[Tilt, TyTN II, MDA Vario III Android Development] msichal:
I think my kaiser with the newest kernel is useless because of very short battery life... Should't the cpufreq be the thing that incereases the battery life? :)

Where can I find last release without cpufreq and with better battery life?

EDIT: I think I have RLS 5.7 somewhere on HDD.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
RLS5.7 is my best battery life while in standby release. The download for it is in my original post (Latest Kernel, or HAReT Files) are RLS5.7 :)
[Tilt, TyTN II, MDA Vario III Android Development] SpeedySurfer:
Something I've noticed is that it never seems to lock up when on the charger or plugged into a PC. Maybe it's just me?
[Tilt, TyTN II, MDA Vario III Android Development] lorenzoparis:
Hi !

which androidinstall.tgz do u suggest with ur kernel ? :-)

thx for ur job and help
[Tilt, TyTN II, MDA Vario III Android Development] V3rt!g(o):
It never sleeps while plugged in.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
If you want stability then go with Latest Kernel file. If you'd like to test CPUFreq ten download RLS5.9 files.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Still freezing...

Rls 5.7 is still freezing on "Press and Hold Volume..." screen. :(
[Tilt, TyTN II, MDA Vario III Android Development] Rondador:
RLS5.9.1.2 does not work for me, it reachs the boot animation, but there stops. If i connect to the phone via adb and execute top, all processes doing nothing(0% of CPU) except top. I attach the dmesg log.txt
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Make sure you're not using Scoot's 7.0.2 RLS2, as it causes issues. Go back to his 6.1.2 Froyo build, and you should be fine. :)
[Tilt, TyTN II, MDA Vario III Android Development] Rondador:
I reinstalled and working at the moment, except the touchscreen, please could you remove the line:

gpio_func(85,0,1,1);

In arch/arm/mach-msm/board-htckaiser.c

¿Or give me a way to compile the kernel?

¿How can i monitor the Freq changes?. In /proc/cpuinfo there is always the same BOGOMIPS.

¿Can i use RogueTools with this kernel?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Sorry for the lack of updates, and don't think that I'm letting this Kernel die ;). I have just been extremely busy this week with working 2 jobs, 7 days a week, and also caring for my wife who is on bed-rest until the end of her pregnancy (which is Oct). I am taking notes on all posts in this thread since my latest kernel, and will make adjustments to the kernel as necessary, but there will be delays as I have only 4-6hours of me time a week right now.

@Rondador,

I will look at what that gpio_func is tied too, but as far as I can see, no one else has had issues with the touchscreen. What type of phone do you have (Kaiser/Tilt, Polaris, Vogue), and what kind of setup do you have (HAReT, or NAND?)

Thanks :)
[Tilt, TyTN II, MDA Vario III Android Development] Rondador:
Mine is a Spanish TyTNII, KAIS130, with KAIS160 battery. I dont know what that gpio_func does, but i started trying android with haret and kernel 2.6.25, working TS,then 2.6.25 on NAN with working TS, but after a concrete commit the TS died; i reverted to the problematic commit and found that removing that line the TS works again, that line cause problems for my TyTNII on all kernels since that commit. Now i have system on NAND and data on SD partition.

I have C knowledge and luckily some more time than you :p , but i dont have the deep kernel knowledge to make changes to the kernel.

I have noticed that with the "normal" kernel, the battery meter works + or - well, but yours indicate always a 99%.

Thanks for your effort
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Hello Krazy, just wanted to let you know I have commited a change to git which I'd like you to try if you get a chnace, the ext4 driver should now also deal with ext2 and ext3 so they all fit in the kernel but I don't personally use it so it would be good to know if it works! I have reverted some of the changes you commited for now because my phone wouldn't wake from sleep when I compiled and tested it before reverting. I will check over the changes and put them back in soon :) Hope you don't mind, I promise i'll get most of it re-commited, just need to find what was causing the problem, may be to do with v-sync.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
The phone doesn't wake from sleep because of a bug in the Suspend code. Power collapse just puts the core components into extreme low power saving, while "Apps Sleep" puts the phone to sleep like a laptop goes into standby. Once I get time, I've got a hunch I want to try to see if I can get Power COllapse working again with my clock changes. :)

Though it could very well be since there's a bug in the NAND, if you have CompCache enabled, and the phone goes to sleep, the stuff stored on the NAND that is "possibly" corrupted is then stored in RAM causing the phone to crash while it sleeps.

*EDIT* I'll be storing a backup of my changes so I can go back without having to re-write them.
[Tilt, TyTN II, MDA Vario III Android Development] leona:
Hi Krazy, please pass on our best wishes to your wife, this must be quite a stressful time for you both, and hoping that everything works out for you guys, she is your priority, so don't worry if this stuff gets put on the back burner for now, sure others can pick it up. keep well, be strong for her.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Good idea :) Another thing that might keep the main branch more bug free is to create an experimental branch for yourself. What i do is copy my kernel directory to a new folder and rename it experimental or something like that. Then do:

git branch krazy-experimental

git checkout krazy-experimental

You'll now have 2 directories, one following the main branch and one following your own experimental branch. If you want to commit experimental stuff just do it in the experimental folder and commit to your own branch. If you think the changes are stable enough to go in the main branch just go back to the directory following the main branch and do:

git merge krazy-experimental

which will update the main branch with the changes you have made to your own branch. You can also do it the other way round if you want to merge changes from the main branch to your own using:

git merge htc-vogue-2.6.32

Sorry if you already know all that :)

Hope everything is ok with you and your wife, sounds like you're going to be in demand for a while. All the best with it all though, it'll be worth it in the end!