yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
Ahh it freezes :(

First I had 1.70.19.09 radio, it freezed with white screen then I changed to 1.65.21.18 and it freezed again but with black screen :)

I use gmail sync, google contact sync, corporate sync and i always install iGo. No more application installed and i don't put widgets on screen anymore...

What is the problem?

Can I view some kind of kernel messages after freeze? dmesg, syslog, etc

Edit:

Freezing usually happens when I try to wake up my phone from sleep. Not always, but as time goes the chance grows.

I forgot to mention that I have 3 bad blocks on NAND. Could it be the problem?
[Tilt, TyTN II, MDA Vario III Android Development] SpeedySurfer:
Are you using the right screen type?

This kernal still does have some issues with locking up, Krazy-Killa's kernal mostly fixed that.

I wish I knew what I was doing when it comes to kernals and I'd look at merging them.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
It does ? I haven't had a lockup in ages. Yet i don't have my network connection active...

Also, KERNEL.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
Yes I have the correct panel type. Now it's running for 8 hours, i've put back fresh froyo and updated all fixes (compcache fix, ril update). Still on 1.65.21.18 radio.

Probably daedric is right. My network connection is always active. The corporate account and gmail are always listening for new mails.

I could live without gmail but corporate sync is a must because it's a good old corporate phone :)
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I just changed my radio to 1.65.21.18 in hopes of correcting the GPS issue with no luck, but it seems stability has increased as a side-effect.

Aside from the occasional lock-up of an app or a "fail to wake" issue (sleep of death), I have had 0 problems. if not for the predescribed issues, my phone will have been error-free for over 2 weeks.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
I agree. I haven't got any problem just this sleep of death and it's absolutely random. How can I debug this somehow? (kernel messages, logs)

I would happily find the source of the error if i know where to search.
[Tilt, TyTN II, MDA Vario III Android Development] ttqminh1710:
can share me the polaris kernel plz

thank so much
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Use atools to configure this kernel for Polaris or Vogue. Polaris has same nand size as kaiser so just change the type and tailor the other settings to your wishes.
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
21 Days, no reflashing, rebooted once or twice, my only problem is that my kaiser unfortunatly suffers from the busted 3G chip syndrome, so it battles to get running until i switch to 2G only and then its smooth sailing. With the kernel and Scoots Cyanogen mod 7.1.0 RLS3, everything has been smooth sailing. No data corruption on nand, no lockups of the system, no not waking up from suspend mode. Best of all is the battery life, with moderate use it lasts the day, when i just leave it, like i have for the past 2 days, 2h 18 mins on battery. Got the same battery life using winmo. Thanks a bunch for this!!
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
I wish I had a phone that lasts for 21 days... Please write me a step by step tutorial on how you achieved this! My Kaiser can't keep up after 20 hours.

Which radio do you have?

What updates did you apply?

Are you using account sync? Corporate sync, gmail sync?

Did you apply RIL update?

Is Scoot Cyanogenmod 7 RLS3 laggy? On my phone it's way slower than Fat Free Froyo or Not So Super Froyo or Fresh Froyo...

Does RLS3 respond fast to incoming calls? I have only got response after 4 rings, with the froyo releases it is 2 rings.

Thanks :)
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
I simply flashed this kernel, applied the updates, followed by Cyanogenmod 7 RLS3. The radio version is 1.70.19.09. I disabled vibrate on ring which i saw in another post delays the ringtone. Response to calls seem to be fast enough, using roguetools i overclocked to 40mhz. Basically only use gmail sync, no corporate sync. The other change i made was to install Go laucher and only have one panel instead of the default 5. It also has a built in task killer which i find helps quite a bit since memory resident apps do use batter power and memory even when not in use. Hope this helps, been working very well for me.

Just to add, using an iReader in day mode i get about 4.5 hours of continuous use. Basically i never expected too much from android on kaiser since it was never intended to run on it. I have to say i am pleasantly surprised at what the devs here have achieved
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
The Kaiser processor can scale up to 530 on most specimens. You should try it.

Same here! :D

Android manages it's own memory. It's pointless to start closing programs, as Android will launch them again and that yes, wastes battery. Also, many programs can running in background spending almost no processor/battery. In general, it's advisable NOT to close programs in the background. Use a swap partition, with a fast SD card, you'll have better results.

X2 :D
[Tilt, TyTN II, MDA Vario III Android Development] MTom:
sorry I'm stupid :confused:

this to be

"Use a swap partition"
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
Lol i meant 490mhz* daedric never thought of using a swap partition, definatly going to look into this, thanks.

Even though android does manage memory, its impossible to fix all the memory leaks in an application. I find that some apps stubbornly run as a background service even though its not necessary. But then my preferance for closing apps i am not currently using comes from cooking winmo roms for older devices like the htc wizard, which actually had a almost working android release called "wing linux", too bad the project went dead.
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
I tried using swapper 2 and manually setting up a swap file to have a look, keep getting permission denied when running "swapon /sdcard/swapfile.swp". Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
I did everything that you said. Not good :(:(, it's worse than fresh froyo, random lockups. First after 7 hours, second after 1-2 hours. I don't understand what i'm doing wrong...

I didn't use corporate sync, just gmail as you said. First I didn't apply the kernel update with RLS3 because I think it should work that way. But after the freeze I applied the kernel update and reinstalled android. Nothing changed.

I changed the radio rom to your version before the procedure, installed go launcher on android, and overclocked the cpu to 490mhz.

Everything is the same as yours :(

Can I ask you what you mean at "applied the updates"? There is kernel update, RIL update, compcache fix just what i've found.

It's really frustrating that all of you have a working android and mine freezing all the time. :(

I have knowledge of programming languages and linux. Please show me the first step on how to debug this problem.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Drop that line of thought. WinMO is very diferent in memory menagement than Android.

Also, if a given app insists on having a background service, (Say Locator service for the Google Maps in general), closing it will not only be pointless, as the Service will be restared shortly, but battery inneficient, as it costs much more to have a service starting than having it run in background wasting cycles once in a while.

Let android manage it's ram. You could try a script like V6 Super for a better memory menagement. :)
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
mattempus since i flashed the 1st android rom i have gotten into the habit of applying updates and running fix permissions every time i flash a new rom. Your problem might even be hardware related like my 3G issue where the phone is extremely sluggish after a clean boot until i set 2G Networks only. Other than that I honestly cant tell you what the problem could be. What i didnt mention is that i have sys and data installed on nand and all apps i move to sd card to keep as much freespace as i can on the device itself.

daedric yeah i expected android to be much more memory efficient than WinMo to begin with since its linux. I am going to V6 Super now and have a go.

Its when i see posts in forums like this that makes me happy all over again i didnt get a blackberry when i could have and grabbed the kaiser instead :-D Now if only there was a hermes android rom my trio would be complete lolz
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I don't think there is ever a possibility of running Android on the hermes because of the processor and limited ROM size. Even if you were to get Haret on an sd card, the processor is unsupported.

Now on to my issue...

I think I also may have a bad 3G issue, or maybe an email problem. Long boot times and random sleep of death issues are happening on both phones. I reverted to an old trusted Fuze for now for answering calls and texting but I hate winmo so much that I even tried "e2fsck" commans in busybox on the Kaiser...lol.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
Hi!

Do you use IMAP push? Yesterday I reinstalled Cyanogen mod RLS3, applied the updates and NOT set up any corporate stuff. Before I checked only corporate contact sync as I thought it would be enough but saw that the email app always running.

So with absolute no corporate sync my Kaiser have been running for 27 hours now. It's really strange but i think that is the problem.

I've found this in a WinMo forum:

"The problem is IMAP email push. IF you use IMAP there is a chance you will get SOD once in a while. I changed all my emails to POP3 never had SOD since then."

Could it be that in winmo and android it's causing sleep of death? :S
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I am beginning to wonder the same thing myself. My work email is on an exchange server here at home office and noone could get on since Friday last week outside of the intranet.

Well, since Friday I had been having SOD issues all weekend. When I checked my work email it would never come up, always showing previous emails from the past Thursday. Called IT and found out the server had been locked out so I went ahead and deleted the corporate work account. Voila, no more SOD.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
Me too. Now uptime is 115 hours, unbelievable!

But i wish i could fix this email problem. :)
[Tilt, TyTN II, MDA Vario III Android Development] prash.666:
hey i used the following procedure given in the "xda wik htc kaiser section" TO THE WORD for this very CM7 and this very Kernel..

http ://xdaforums.com/wiki/HTC_Kaiser. com

(please remove the spaces and then go down to the android section once you find the page)

now i have done exactly evrything as told but i get too many "sorry" messages once the android boots after installing.. like around 10 messages all at once

Sorry!

the application ________________ has stopped unpexpectedly.please try again

Force close (option appears)

the kind of applications that appear are :

ADW

maps

android.process.media

market

gmail

email

messaging

EVEN process.system

gapps

com.android

etc etc etc

all with force close options.

the boot up screen shows the Cm7 logo then all this happens

the bar notification shows the battery level and the network and the time

once turning the screen off and then back again it shows the lock screen with CM wallpaper and two unlock options time network etc..

on unlocking the same thing about the sorry messages keep happening..

the lock screen seems perfect.

bar notification can be pulled down aswell

which shows the

bluetoooth

wifi

sound

network symbols

on holding the power button it shows all the required options.

its like android has not been installed properly..i tried doin it again and again..but nothing!with different panel types too..

What seems to have gone wrong??wht should i do???i have tried all the three panel type options..or please help me with the forums as to where to i have to look into..

i have tried getting to this point for 2 months

i am in a way a noob..

please!!your help would be very great.. :'(
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I used a swap partition on SD for a while but found it best to just use compcache and limit what is running. Go light on the widgets.
[Galaxy S II Themes and Apps] aZuZu:
Anyway this is final version of command line samsung stock zImage Splitter

THIS TOOL CAN SPLIT STOCK IMAGES ONLY!

aZuZu Samsung Mobile Stock zImage Splitter, v1.02.3f. Final. (c) aZuZu. 2011.

If this is not usefull please report to mod..
[Galaxy S II Themes and Apps] DooMLoRD:
it is useful!!! thanks for ur work!
[Galaxy S II Themes and Apps] _JKay_:
Thanks! Will test it later today!!
[Galaxy S II Themes and Apps] _JKay_:
dupe post.....
[Galaxy S II Themes and Apps] aZuZu:
i have problems with upload on server but new version can handle tegrak / chainfire..
[Galaxy S II Themes and Apps] sicopat:
Hi, thanks for your job :)

for my information, what is the purpose of a zImage splitter ?
[Galaxy S II Themes and Apps] malavan:
ok what is this thing?
[Galaxy S II Themes and Apps] aussie_boi:
Very helpful for DEVs in breaking ROMs down, kinda like "unzipping".
[Galaxy S II Themes and Apps] sicopat:
Thanks,

working on stock zImage KF2. (just to try it :))

Is it possible to do the reverse process (on windows :)) ?

I believe it's a bit more complicated (or impossible ?)

Noob question : Why decompiling a kernel when sources are free ?
[Galaxy S II Themes and Apps] cruzzmz:
i tried it but after extracting using the tool i only get empty folders ... am i doing it wrongly?
[Galaxy S II Themes and Apps] sicopat:
For the moment, it's working on stock zImage only
[Galaxy S II Themes and Apps] aZuZu:
ok. folks! new version is up.. still in alpha but now supports all three formats

stock, tegrak, and chainfire are now supported.

WARNING: i have issuses with cygwin so there is special exe file run_cpio.exe in application folder which you can run manualy to unpack chainfire ramdisk.

enjoy!
[Galaxy S II Themes and Apps] cruzzmz:
i am trying to extract the stock XXKF2 kernel

this is what i did

1. extract the .tar file

2. extract ur tool

3. copy the zImage to to ur tool folder

4. use cmd and use

asmzis zImage

all the zImage is extracted but inside all the folders are empty

:(
[Galaxy S II Themes and Apps] aZuZu:
by agrument is see you are using old version...

today i have upload new version. which can handle all three formats..

for now it is using additional argument..

so to unpack stock zImage command goes

asmzis zImage stock

so to unpack chainfire zImage command goes

asmzis zImage chainfire

so to unpack tegrak zImage command goes

asmzis zImage tegrak

old version could unpack only stock.

p.s next version will be back to old asmzip zimage becouse i will add detection for types..

plus fix for zimages w/o ramdisk.
[Galaxy S II Themes and Apps] Chainfire:
Not to complain, but what could possibly be the use of dumping my kernels, aside from ripping my hard work off ? I mean, they are just the stock kernels + my modifications.
[Galaxy S II Themes and Apps] cruzzmz:
got error when extracting the ram disk ... 7z exe come out with error

i extract only stock zImage
[Galaxy S II Themes and Apps] aZuZu:
i downloaded stock XXKF2 kernel what ever from here.. http://xdaforums.com/showthread.php?t=1101671

also fixed error in 7z call procedure and reupload all now should be ok ...
[Galaxy S II Themes and Apps] aZuZu:
Well if they are stock kernels and somebody wanted to test cf-root with for example tegrak kernel? Shouldn't that be allowed to him / her? If not say a word and i will remove application from server. Sorry if i offended you in any way. I just thought that this appliction could be usefull.
[Galaxy S II Themes and Apps] aZuZu:
damn server.. now patched version should be uploaded...
[Galaxy S II Themes and Apps] sicopat:
Thanks, will wait for the recompiling solution :)
[Galaxy S II Themes and Apps] cruzzmz:
i tried the new ver .... all files extracted but is the system folder suppose to be empty?
[Galaxy S II Themes and Apps] Chainfire:
Exactly why should this be allowed ? Other "devs" in the past have completely ripped off my work this way - that's why I no longer allow re-use of any of my stuff without express permission. This stuff easily allows for a simple re-branding of my CF-Root kernels, something I have spent over a year on to perfect, and is supported across various devices. That being said, simply injecting parts of CF-Root initramfs into Tegrak will likely end up with many features not working ;)

The thing is, people who know how to work with this stuff are already perfectly able to extract and repack. This just provides a shortcut for a lot of noobs who have no idea what they are doing, will be doing blatant rip-offs, and release a lot of half-working kernels. This tool allows beginners to skip the part where they actually learn how this stuff works, which is pretty important, really. Those who've had to learn everything properly will have a lot more respect for other people's work than those who can rip with the push of a button.

I have my own toolchain that allows extraction and repacking of pretty much any Samsung-style kernel, which also runs on Windows (so yes, it is perfectly possible to do) for over a year now. The above is exactly the reason I have never released any of it publicly (though several have asked).

I am not "offended", nor am I going to tell you to remove it. However, as you may have understood from what I wrote above, it does not exactly make me a happy person.
[Galaxy S II Themes and Apps] aZuZu:
Ok! Tool is removed from server! Sorry, ppl! But Chainfire has good point! Sorry Chainfire!

MOD PLEASE CLOSE THIS AND THREAD ON samsung i9000 thread. Thanks!
[Galaxy S II Themes and Apps] ratcom:
put like that you do have a point ;) especially when it can be targeted at a particular persons work instead of "stock". That said, with it say .... only able to handle "stock kernels" this would be be a very handy tool to have.

edit - well done Chumby_666 I think you have made to right choice in this case however what about a version that can handle "stock" versions only?
[Galaxy S II Themes and Apps] aZuZu:
MOD DON'T CLOSE THREAD...

Baby we are back in buissnies... will repost.. for stock ones..
[Galaxy S II Themes and Apps] aZuZu:
ok. reuploaded stock zimage splitter.

fixed:

a) it doesn't use 7z no more.

b) detection of stock / custom zimage / image wo ramdisk.. so it gives nice message :D
[Galaxy S II Themes and Apps] docn:
gread idea! looking forward to test the cmdl.

you'll get a Ozuljkso from me
[Galaxy S II Themes and Apps] aZuZu:
no thanks!

i would rather Karlovacko beer :D Ozujsko beer is too sweet on this hot day :D
[Galaxy S II Themes and Apps] sicopat:
Thanks, it seems to work well.

But why a Windows tool to extract zImage if we can't use windows to rebuil/ compil zImage ?

Can you build a tool to re compil zImage with windows please ?

thanks
[Galaxy S II Themes and Apps] aZuZu:
like i said i dont' have samsung so this was like first step to learn about zImage stuff, but je there is plan to make like splitter / joiner thing..
[Galaxy S II Themes and Apps] sicopat:
That would be the first windows tool.

I would be really pleased :)
[Galaxy S II Themes and Apps] aZuZu:
so huston we have a problem :D

mr tegrak gave perm for unpacking his zImage but we need to wait that chainfire add registration system to his cf-root becouse they are packed similar and adding some specific file search pattern would be nuts.. becouse it would require unpack zImage find some specific file if it is there remove all...
[Galaxy S II Themes and Apps] aZuZu:
added tegrak support.

no more splitter dev. all focus is now on joiner.

p.s.

reuploaded in 8.25am
[Galaxy S II Themes and Apps] _JKay_:
Heh... Its so easy to unzip Chainfires initramfs... I did that weeks ago on a VirtualBox. Here is a tip.. If you want his kernel to reinstall Superuser.apk etc... just remove the folder '/system/cfroot/' because install.sh checks for a subfolder there.

I think Chainfire should be more open.. release the source code.. let other people learn... like Supercurio does... I mean this is Android! OpenSource!!!

Maybe I should release his initramfs here.... and explain what it does? Who want it? Nah... I better not :)
[Galaxy S II Themes and Apps] ivcarlos:
Closed solutions on opensource systems

I agree!!

Chainfire, closed solutions on opensource system dnt work!!

After two versions of gb 2.3.4 on my sgs using cfr i decided definitively abandon cfr because a lot of problems occurs.. Phone freezes, sleep and dnt awake anymore..

now i try to create my own kernel... stock, rooted and with cwm.

i think after a lot of versions of kernels and phones, Chainfire loosed control and quality. now, none of stock kernels available... so, sorry. i will make my and... enjoy!

:D
[Galaxy S II Themes and Apps] aZuZu:
It is his right to close source :D you don't like it don't use :D or use some hex editor and peel his zImage till you come to initramfs :D

What is the name o right!

It should be called not cf-root but cf-babushka :D ( sarcasm )
[Galaxy S II Themes and Apps] Chainfire:
The first public one, at least, hehe ;)

As I stated before, I'm not disallowing you from releasing this... I just see more downsides than upsides. It does not make me jump with joy. If you end up doing so, I might even release my own tools, as it's all out there anyways.

Good luck :) If you're doing it without actually recompiling the zImage header and footer, I'm wondering how long it will take you to find out what the trick is :)

That's the point, it is easy if you know what you are doing. Which pretty much leads to: people who require this solution for anything else than pure convenience obviously do NOT know what they are doing, in which case they might be better served by reading up first ?

That's just hurdle #1 to get at the initramfs, from there you can learn whatever you want. Most of CF-Root isn't really closed source you know, the initramfs is there for all who know how to get it, so they can learn away. The APKs are indeed closed source, though. As for CWM4 and such, changes to that source are very minor (3 lines? 4 lines?), most of the magic to solve CWM problems happens in initramfs scripts, NOT in CWM itself. (My CWM for SGS1 had some more changes due to RFS).

As I have stated before, my biggest concern is people just taking CF-Root, "rebranding" it, and passing it off as their own work, without any credits or acknowledgements whatsoever. This has happened several times before. To be fair, I do get a lot of donations from my work on CF-Root :)

(As for kernel source code, I don't even have it myself...)

Again, there is preciously little closed source about CF-Root. You just don't know what you are doing. As for your problem with freezes, sleep, wakes, have you ever considered it is something you yourself are responsible for? As aside from you, nobody seems to have these problems, and it does sound suspiciously like a misconfigured governer to me (usually caused by tweaks and CPU control apps).
[Galaxy S II Themes and Apps] aZuZu:
yeah! i'm doing w/o recompiling worst part is done problem is new command line :D

aZuZu - Samsung Mobile zImage ToolKit, v1.02.3a [ Alpha ]. (c) aZuZu. 2011.

usage: asmzitk [-s[project_name] -c[project_name,kernel|project_name,ramdisk] zImage

-s[project_name] zImage

example: -sExample c:\zImage

will make folder in projects called example and store extracted files there.

-c[project_name (kernel), project_name (ramdisk)

example: -cStock,User c:\zImage

will combine kernel from project Stock and ramdisk from project User and save zImage.