yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Gotcha. I also have a pretty huge inbox (2000+). What happens is I open messaging, loads everything without names, keeps on loading, screen goes back to home. I open it again and it's fine. If i keep it under 1000 then it loads with no problems.

Just added the widget, set it up and restarted. Nothing bad happened. I think you are right, it could be a kernel thing as I have not seen any issue with it.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
compcache

Anyone else besides me trying to get compcache enabled? So far I can load all modules and have ramzswap0 created. The problem I am facing right now is initialization, I get a weird init: not a typewriter error. I have tried everything that I can think of hoping I can get that initialized without messing with the kernel (that I can't flash) If anyone else knows how to fix this, we'd all appreciate some info though I am almost absolutely sure compcache is something we'll enable for a while then go back to no compcache :) we just want to know we can enable it.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Somebody knows the name that an app for lockscreen that have 9 points and you can to make a "geometrical figure" to unlock the display.

I don't remember the name, but i see in some froyo distro.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
bro, I don´t know a thing about enabling compcache (that´s why I asked you, lol) but I´ll test things for you if you want me to, as I´m sure we all want you to stay away from things that might mess up your kernel, because since you cannot flash it back it´d be a "show stopper" for the evolution of this build, so I´m open for testing, just let me know what is there to be tested. (I´m a noob, so be very explicit when/if you need me to do something.)

PS: I agree with you on the whole "compcache is something we'll enable for a while then go back to no compcache" but I too, want to know if it is possible just for the sake of knowing. :D
[Tilt, TyTN II, MDA Vario III Android Development] elander:
thank you for such a detailed explanation, I feel I can drop TI school now,lol, no seriously now I understand why compcache used to make multitasking feel better while making the phone look like it had too many apps open even when it wasn't like that , (in cyanogenmod 6) and also now I understand why it was so damn unstable sometimes, well I think I would like to see it enabled just to get to know how does it perform in donut (as there's a lot more free memory) but I don't think it is really needed, so feel free to send me the command list (although I'll probably have to google it all just to understand them,lol) I'd be happy to contribute, as I feel I owe the community a lot, and to be honest I think you have done a terrific job on this build, I even went back to froyo just to make sure I wasn't missing anything and I came back a couple of hours later as I simply could not stand the performance lost compared to this build (sometimes I get up to 55 free memory!!!!) thanks again pal, terrific job, so far this one is a keeper on my kaiser!!.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Kallt_kaffe worked on a compcache.sh script to a point where it works pretty well. It is included in dzo's Fresh Froyo. I use a slight edit that enables usage of swap (partition 4 of SD card) for things that don't compress.

I don't know for sure, but from what I've read, the older ramzswap had an issue where it wouldn't free pages when applications exit. I think the newer one we use, at least with 2.6.32 kernel, has the problem fixed, so compcache works better over the long run. I use it all the time.

If you are interested, this update (for 2.6.32 kernel) has the modules and compcache.sh that I use. I keep this around and install it always after installing a new android. This should work with Donut, but I have never tried: I use Froyo exclusively these days.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
lol I wouldnt drop of school if I were you :) yeah, a lot of people complain about how some things don't behave the way they want but if we try to understand the very basic principle behind it then it will be a lot easier to see why some things may help or not, or if we need them at all.

Thanks for your comments, I really appreciate that a lot. What device were you using for cyanogenmod 6? I've always been curious about those releases but sounded to me like they were for a completely different device, the Dream if I recall correctly bu there is a big chance I am wrong.

I'll pm you what I have attempted with compcache and how I've done it. You might also wanna try the update we were provided last night :)
[Tilt, TyTN II, MDA Vario III Android Development] elander:
I was using my kaiser, there´s a build posted here.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Hey there! thanks a lot for your help and for the attachment. Unfortunately I am stuck with kernel 2.6.25, however I downloaded the attach and updated cause I thought I would try anyways.

The script did not work and doing it manually produced the same error and what happens is when I issue andy insmod or modprobe it complains about any .ko being an unknown symbol. I am convinced this has more to do with the kernel that I am using than anything else as I tried the compiling the official compcache and rzscontrol, the ones in cyanogenmod builds and some other files that I found compiled from another user here.

I will work with Elander on this if he's willing to update to a newer kernel and we'll see how it goes. Do you know (this might sound crazy) of a way to modify a kernel that has been flashed already without flashing it again? Thanks again for your help.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
I have latest kernel 10-12-10 installed (6.32), so I guess that´s the one needed, am I wrong?
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
For the files attached, yes, that would be correct. Script is under /system/bin
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
There's a way to Deodex a Deodexed build?

I'm trying to take more space of storage on my phone.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
You can't deodex a deodexed build, the correct term would be odexing a dedoexed build or deodexing an odexed build. In any case you can check dzo's thread about odex and optimized build (there is a link on post #1). He has a script that you can push into your phone and run it. Once you have run it and if the process is successful your build would be odexed and remember that once you do this, the correct procedure for updating an app would be to remove the app and the odex file, then update, then odex the app again. Don't update anything related to framework if you are experimenting with themes after odexing because your phone won't boot and you will need to reinstall your build :)
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Thanks bro!

I understood.

Have some problem if i use a kernel that have the name of other device like vogue, just like this: voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh? This could brick my phone or i will need to reinstall the android build?
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
You're welcome! :)

When you flash a kernel you must make sure it matches your device. If it doesn't match your device it will have weird issues, for example: choosing the wrong panel type will make your screen look very funny, like a 256 color screen.

You need to use Atools (find a link on post #1 under "Last notes..." or search for it in the forum) and open your kernel, then you have to select:

-Device

-Resolution (the kernel I attach uses 320x428 to match the 143 dpi that this build is set to)

-Version (select Donut for this build)

-Panel type (depends on who made your screen, my personal case is type 1, if the kernel I included looks fine then this is your panel type as well)

-Keymap (what kind of keyboard your device uses)

and include any other settings that you'd like to try. I only included a battery value of (1350) using the "Simple" settings. This seems to work very well for most users.

Then save your file and your kernel is ready to be flashed. Be advised that Froyo kernels break wifi, if this happens to you then you might need to find an update that activates this for you if one is available (I only tested 1 froyo kernel and this happened to me, do not know if this issue has been solved yet).

Edit: You don't need to reinstall after flashing a kernel but it is advisable. What I did was backup /data partition, install, restore /data partition.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Right!

I don't like to make partitions on my SD. I always install Android on NAND.

I was serching around the forum, but don't have answers about somethings.

- Vogue build's only work on vogue (beyond that have other devices on name)?

- I like the menu of froyo, that seem's a 3D menu. But, i don't know if this works with Helix launcher or this is make only for ADW launcher.

- There's a way to get full market place (because some app's don't appear on Donut, just on eclair and froyo, apps like apps2sd)

Will do you make another builds of android, like Eclair?
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
I didn't mean to make any partition. What you do is select the backup /data in your installer menu, that unmounts your partition from NAND and saves it on SD as a file. Then you select install for Android like you always do. When it's done installing select recover /data from your installer menu and it will delete your /data from NAND, read the file on SD and ovewrite your newly installed /data on NAND. This is done so when you reinstall and boot for the first time your phone will be in the same state you left it: settings, apps, sms, etc. Id recommend doing this only for reinstalls of thr same build

Now to answer your questions: Vogue and Kaiser builds are very similar if not the same. I've used Vogue builds on my Kaiser just as many users have Kaiser builds on Vogue. Again, what's important here is your kernel which is setup as explained earlier.

That 3D menu is only for ADW Launcher, which I can upload here or you can get from Market, the 3D effect is onky for the Froyo version though. If you are using a 2+ version you might wanna check HelixLauncher 2 which might have some other effects. I used Helix here cause the current ADW (as of time of writing) is very heavy on battery. Helix is lightweight and a little more responsive (at least to me).

About Market, there are several fixes out for this. I like it this way though as I see only the apps that would run just fine on Donut. Things not made for Donut will not run okay or install at all. If you wanna use Apps2SD get ready for some SD partitioning as you need an EXT3 partition to move your stuff. I don't know if the partition is required but due to the unclean unmount you really wanna have a journal on your partition.

I would love to try and do something with Froyo (Not a fan of Eclair) but I can't reflash my kernel, therefore unable to use a newer or setup for Froyo and thus unable to test if my builds would run at all. When you do this kind of things it's very likely that your phone won't even boot :)

--
[Tilt, TyTN II, MDA Vario III Android Development] Millence:
Today is a very productive day. I have successfully started

compcache

(2.6.25 kernel) and

wifi tether

on my experimental donut ROM.

So it can be done! :)

Because I suffer from chronic lack of free time more detailed explanation you can expect tomorrow.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Holy crap dude! This is one of those wonderful news that put a smile on my face :D I was already giving into the idea that I was not gonna have that with my current kernel. Awesome! I know I have a pending pm for ya but I've been getting carried away by replying on things here that when I realize it's time to go and do something. I'm sending you one right now though.

@elander, I am also sending you the stuff I told you about only because I said so and you might wanna experiment with it, no need to reinvent sweet water though :D we can always wait on Millence's details.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Thank you for support.

I was thinking that, if you want to build froyo, i could test it.

You just need to PM me.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Found a link for a cyanogenmod 6, I had forgotten that is Froyo, thanks though, I was trying to find a Donut :)
[Tilt, TyTN II, MDA Vario III Android Development] elander:
Do not worry friend of mine, it´s ok to get confused from time to time as "xda universe" is just HUGE,lol, anyways as marcelotorres said, if you are willing to work on a froyo build, I would gladly test it for you, that´s the least I could do for you after all the hard work you have put to this (not to mention all the info you have given me). Give it a thought or two, and let us know in case you feel like going for it, who knows, maybe you could get us no believers (and donut lovers) to give froyo a second shot.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
As I was explaining to marcelotorres through pm's my worst fear in this case is the number of changes I generally do for making a build, you know all those trial and error attempts in which I install and it wont even boot, it would mean 20+ hopefully a lot less uploads and downloads for all of you :)

I've been thinking, at the very least I know for a fact that Froyo boots with my current kernel cause I installed it by mistake but I get a lot of force closes and no bluetooth or wifi. This I believe were caused by a) an old kernel and b) a kernel setup for Donut. I could give it a shot, if I can make it at least run just fine using my kernel it should work a lot better for all of you with an appropriate kernel, we'd only need to test wifi and bluetooth, which if I am not mistaken already work in Super Froyo.

If I do attempt something like this I would like to do it after the resizing and compcache things we had planned. I also thought of even going back a little and attempt having a runnable sense UI since it is as far as I know, very slow on Tatoo. You know, just trying to come up with something to do :) I'll let you know if I dare to mess with Froyo. Thanks a lot for your support.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
Ok, we won't try to rush you into froyo, besides I really like the idea of improving donut as much as we can since it is the fastest and more stable version of android avaliable to the kaiser, so it is wise to stay on it and improve as much as it can be improved. again if you need help testing on the resizing process (or any others), count on me. thanks again pal.

PS: I thought you had forgotten about resizing to qvga since you are stuck to a different resolution, but I'm glad to see you still have that in mind, mean while if anybody else is willing to run 240*320 on this build I recommend setting your DPI (using rogue tools) to 114 as (almost) everything fits just right and looks really "hi res" as a matter of fact the only thing I have seen so far that doesn't fit the screen is the "repeat" button on the default music player, so to me it is perfect as I don't really need/use it.
[Tilt, TyTN II, MDA Vario III Android Development] shefsalad7:
Thanks for all the hard work and TLC you have been putting into this build and this thread. It is greatly appreciated. I have been surfing around for a year now for a fast stable build for my Kaiser Tilt and so far this one is the best. I have yet to find a Froyo build that isn't too slow. The closest I found was dzo's Fresh Froyo. I have RLs3 installed on nand and all is running great after a couple days. I have noticed only a couple of little bugs:

I am also using 240*320 with 120dpi and everything looks great, except gmail. The inbox font is way too big. The message itself looks fine once it has been clicked, but the inbox listing doesn't look right.

Messaging always closes automatically (no FC message though) a second or two after pulling it up.

XDA app does the same thing, not sure if that has anything to do with this rls or not. Are you experiencing any of these minor issues.

I really like Helix launcher, thanks for including that instead of ADW.

You guys are great! Thanks a lot.
[Tilt, TyTN II, MDA Vario III Android Development] illegal2008:
BT no sound

BT audio gives me no sound with different kernels

nand
[Tilt, TyTN II, MDA Vario III Android Development] Millence:
comcache and wifi-tether on donut

Try putting this lines in sysinit.rs

Afaik compcache is running like a service.

This lines are from VaniljEclair.

# Compcache
service compcache_on /system/bin/logwrapper /system/bin/sh /system/bin/compcache.sh start
disabled
oneshot

service compcache_off /system/bin/logwrapper /system/bin/sh /system/bin/compcache.sh stop
disabled
oneshot

on property:persist.service.compcache=1
start compcache_on

on property:persist.service.compcache=0
start compcache_off

As for the 'wifi-tether' things are a bit more complicated. I will try to correct the original application until Monday in order to work, without having to run the script.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Yeah, a change in kernel can make a huge difference. With the one I packed I get bluetooth phone and audio, and both work well in my phone, I've listened to music through it and held long conversations on the phone through bluetooth.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
speaking of kernel, warbyte how's ypur battery life with the kernel you are using? how old is your battery? is it a standar 1350mah? because no matter how many tricks I try with my two months old battery I can't make it to the end of the day without using data conection as aI dont have a data plan and also very very very light use. :( (This is build independient as I have tried most builds with the same result).
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Hi guys!

I have bought a new battery for my Kaiser today.

Curiously, it made my Kaiser soft reset....and i need to reinstall Android again...

Strange...
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
I can assure you this build can go on my phone for exactly 10 hours, locked on 2G, auto sync in background, slight email checking, slight facebook status updates, 1 hour OsmAnd activity (as my speedometer in my car is broken), and no calls leaving my battery at a lil more than 70% I think I made that observation (to you if I remember correctly when published RLS02). I have two batteries. My original one, 1350, which lasts when fully charged 5 minutes if you call :) and half a day if you dont call at all and this other new battery, also stock 1350, which is the one I am currently using and it is exactly 1 month and a half old.

What kills my battery, from 100% to around 20% in exactly 8 hours overnight without a plugged in charger is a twitter app that I use, but it checks for new twits every 5 minutes so I understand why. All this is with that same kernel.

Have you checked to see whether it might be some battery miscalibration? One time during my tests I remember having the meter stuck at 100% and when checking with dmesg in terminal you could see all crazy things when charging, like an odd number of units more than 5000, then less than 2000, reached over 7000, and it also gave me really weird negative currents. When this happened I would get a fully (100/100) charged battery and it would discharge in 5 minutes, charged in 5 minutes and if it went in dmesg with a value lower than a 30/100 the phone would just turn off so something was terribly wrong.

When that weird issue happened I took my battery out for 10 mins, tried turning it on so all current was discharged (I think) then I put my battery in, hard reset to clear the kernel, fresh installation, and left it charge overnight. Next day everything was alright and the battery had correct readings. It had nothing to do with the release because I didnt change anything in the package after that. With a default installation I dont think there is much eating the battery, I also keep GPS active (in settings) all the time, along with cell based location.

During that frustrating time with RLS02 I noticed a little bit of correlation between installing with a fully charged battery as opposed to using an almost dead battery. This correlation might be quite biased but I am convinced a fully battery gave me less force closes on reboot and def. a lot less calibration problems, it always started full at 3200 units.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
That is very weird. When I bought mine, plugged that in and when booted the meter indicated 100%, then slowly discharged, that is the only difference I noticed, while my original battery would jump from 100% to 15%, really damaged battery.

Don't worry, it must have been a coincidence between /data corruption while rebooting and putting in your new battery. Try the /data backup, you wont regret it and will make your life a lot easier :) I always keep a backup on SD, and an androidinstall.tar as this is still my everyday phone and I wouldnt like to find out through half of the day that I need to go back home to get a working phone again.

Edit: I'm looking at your sig and it says you got SPL 3.340000? If you are messing with Android :) and if you can still install winmo, find a thread about Hard SPL, and get that done immediately. Accidentally having a stock SPL is what left me locked on this kernel without being able to flash anything. Hard SPL 3.29 is adviced by a lot of people and myself.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
No problem my friend, i learn a trick...

I have put Astro on xScope download folder...and if i have to reinstall Donut, i just need to open xScope and enter in download folder...then i (re)install Astro and all of my apps, that i put on Apk's folder... ;)

I'm testing my newer battery,and it is very good... ;) my old battery was damaged.

I'm using spl 3.34.0000 and radio 1.71, and when i want to install some WinMo build, i flashe my phone with a stock rom (wm 6.1..in my native language...portuguese)...and when it install and boot, i make a hard reset, then i flash to radio 1.71 and spl 3.34...and then install the build that i want.

;)

PS: My stock SPL is another, that i don't remember now, but isn't 3.34.0000

For now, i'm waiting for the release 4, with compcache :D
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Sounds great, just trying to make sure less people make the same mistakes I did in the past :)

I still need to test Millenece's compcache lines. I am using my phone to connect to the internet right now so I'll have to wait till I am done around here and other things so I can try it.
[Tilt, TyTN II, MDA Vario III Android Development] shefsalad7:
I am running rls 3 on nand using Kaiser Tilt. How can I tell which SPL I am using?
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
I think that you only can see what is your spl when you're using WinMo.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Remember man,

i'm your alfa-beta-tester... :D

Since yesterday i'm working in my own Android build.

I was working in Froyo, but i'm thinking to develop for Eclair or Donut.

In your point of view what version is less difficult to work?

Since i have installed your builds, i have learned a lot of things! Now i know new things, and have my questions and doubts answered.

Thanks again for all your support and for all people that improve my knowledge about Android.

In a few days, i want to release my own build, but i want your opinion before officially release this. :D
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Warbyte,

How do you edit your camera driver?

It can be inserted to a froyo or eclair build?