[UP 23-09-10] htc-vogue branch 2.6.25 release files - Touch CDMA Android Development

In the androidupdate there are the kernel's modules.
I release only the vogue but you can change device/panel ecc with nbheditor
Remember to install androidupdate for wlan and other parts
Main features
No yaffs2 tragedy and no data loss on nand
Working camera
UP 23-09
n2rjt mod battery for polaris and kaiser (updated)
UP 19-09
Fixed power collapse (new)
using n2rjt mod battery for polaris and kaiser
Make a full charge circle to get good results
TODO
Fix battery
Fix sdhc support
Modules unchange
Download file from here

What is the general difference between this branch and the one that everyone downloads from dzo's site?

Has kalt a similar site for actual downloads like dzo?
Is this nbh restricted to a build like latest fresh froyo/incubus? For what is the update? Could you explain it a bit more detailed?
Thank you for this post ;D

This is the old branch so it's more stable
dzo stopped develop it on 2010-07-25 (and started with 2.6.32)
the updates are:
-> k_k: tether
-> k_k: battery for polaris/kaiser
-> l1q1d: support for lzma initrd
changelog here

l1q1d said:
This is the old branch so it's more stable
dzo stopped develop it on 2010-07-25 (and started with 2.6.32)
the updates are:
-> k_k: tether
-> k_k: battery for polaris/kaiser
-> l1q1d: support for lzma initrd
changelog here
Click to expand...
Click to collapse
Noob question, actually i really wanna ask this since the new initrd released.
What is the difference between the previous initrd and the new one ?
Thanks

support for relocate_apps fixed by k_k
parted inserted by me

could you plz be so kind to timestamp your releases, as it makes things way easier! is this the same kernel you've posted friday in polaris-forum?
just noticed some complete hangups with that one... but didnt loose any data and feels quite good on pola! thought it could be a sdcard-thing, but swithing back to old one didnt solve that... thx anyways, much better (for now!) than the new tree.

alexinc said:
could you plz be so kind to timestamp your releases, as it makes things way easier! is this the same kernel you've posted friday in polaris-forum?
just noticed some complete hangups with that one... but didnt loose any data and feels quite good on pola! thought it could be a sdcard-thing, but swithing back to old one didnt solve that... thx anyways, much better (for now!) than the new tree.
Click to expand...
Click to collapse
+1 to everything you mention here!

The complete hung up is due to battery level:
th battery sensor goes down and android shutdown the system (no data loss).
After one or two complete charging and discharging that problem disappears for me.

Eyecandy lover - Splash screen ?
Suggestion, could this new initrd and/or kernel will support for splash screen or graphical GRUB ? or maybe the new one will support it ? I hope you can develope on this thing, just to make our device more beautyfull.

androidupdate...
Sorry for the very basic question but how to install the androidupdate?

Use atools or boot menu

Battery
Hi,
I used the previous version of the kernel. I experienced that the standby time increased from 1 day to 2 days
I'm curios about the new release ... now flashing ...
Thanks

is there a chance to get the cam working for the pola (100)??
or is the kernel section wrong for this issue (as it already worked some time ago...)?

Use atools and change device. I release only vogue but it works with all devices.

Stable, but battery still on 52%
Hi,
I trying this release for a day (with latest Froyo RLS15) and it is very stable on my Pola100 BUT, the battery percent stops at 52% and it isn't reduced for half day ago. I try to restart the phone, but nothing changes, the battery percent still in 52%. I'm curious when the phone power down

i'll release soon a new version with latest battery update (i'm testing it on 2.6.32)

l1q1d said:
i'll release soon a new version with latest battery update (i'm testing it on 2.6.32)
Click to expand...
Click to collapse
Thank you again for all the hard work.
The latest kernel VOGUIMG-320-FROYO19-09-10.NBH looks like giving my vogue an extra battery life.
After flashing and update .tar file, i think the batterystats.bin file should be deleted, otherwise the battery level will jump over again.
Hope that help someone who want to apply this update.
Btw, in the other thread, someone post about filesystem comparison, nilfs. Is it better than we use now? willing to try that as an experiment ?

The real problem isn't the fs but the nand driver that is buggy.
i did somr test with jffs2 but nand driver isn't complete so we can't format with it

More stable than 2.6.32)
Thanks! I've been running this since yesterday and it's proven much more stable than Dzo's 2.6.32 kernel that I'd been running. I'd had problems with that one going to sleep and not waking. This one doesn't have that problem
Anyone know what I'm giving up by moving back off the 2.6.32 kernel?

Related

[Q] Best Android distribution for Kaiser

Hello all,
I'd like to ask which is the best distribution of Android for Kaiser - I mean everything working fine and so on.
I have HardSPL 3.29 and Radio 1.70.19.09 .. I tried one distro (Froyo 2.2 - Incubus26Jc's Super FroYo RLS14 All Languages) but when I started it.. it runs some time then the screen goes dark like sleep.. but when I press the power the screen image is broken... like white lines on the screen.. (this happens on both Incubus Super FroYo and Myn's Donut) ... I don't know is there some additional software that should be installed...
I use starting with HaReT via SD card...
I appreciate any help... Thanks in advance!
Best Regards,
Dimitar Dimitrov
The screen problem is wrong panel type, edit the default.txt in andboot folder, change the panel type, (board-htckaiser.panel_type=X), it can be either 1,2 or 3, if the display looks fine apart from sleep issues when you press power key, chances are you have a panel type 3, panel types 2 and 3 display the same, but have sleep issues if you choose the wrong one.
As for the best build? That is something you have to find out for yourself, not being funny, just that everyone has a different idea of 'best'
Thanks a lot!
Okay about the distribution... As I am new to Android at all... Can you please tell me your opinion about which distribution is working on kaiser (probably one you have tested and you are happy with it)
Thanks once again!
Kind regards!
Depends on what you want.
If you want speed, go with Myn's Warm Donut.
If you want to more apps, and less speed, go with Eclair.
If you want the latest apps and even less speed, try Froyo.
Thank you I'll try which one is working well on my kaiser and i'll choose one.. sorry for stupid questions anyway just i think it is better to ask someone who passed by those kinds of issues
MykoB said:
Okay about the distribution... As I am new to Android at all... Can you please tell me your opinion about which distribution is working on kaiser (probably one you have tested and you are happy with it)
Click to expand...
Click to collapse
I think I have tried all of them, and only 1 is working fine and fast for me: dzo's froyo (currently 26-08-2010). http://forum.xda-developers.com/showthread.php?t=715402 (get it here: http://sourceforge.net/projects/androidhtc/files/ ) (the latest builds include all of the fixes, you don't need to patch anything after installing).
I am running it with haret on the SDcard. It's so fast and smooth I don't even feel the need to flash it to the nand (which would work even faster).
The eclair builds, (polymod 2.1d, etc...) even with compcache enabled they are too slow. Cyanogenmod is also extremely slow, and it was also freezing while the phone was sleeping). And the Donut builds are lacking features.
On my kaiser the dzo froyo build is at least as fast as the fastest donut builds I have used, and it's rock stable. Far better than the eclair and other froyo builds like cyanogenmod.
PS: do not use any "unodexed" or "deodexed" builds. They are slower.
nemuro said:
Depends on what you want.
If you want speed, go with Myn's Warm Donut.
If you want to more apps, and less speed, go with Eclair.
If you want the latest apps and even less speed, try Froyo.
Click to expand...
Click to collapse
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Myn's RLS5 is the best for my kaiser.
And what about battery life?, Cyanogen literaly drain power in a few hours, froyo from dzo is better, but still is a problem for these builds.
Any recommendation?, the old Donut build battery lafe is the best (at least for me) but after several days the phone signal drops to zero, and i cant recover it !!
Please, your comments, thanks in advance!
yap i have same problem with phone signal. i wonder why...
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
zenity said:
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
Click to expand...
Click to collapse
I will try this, is terrific news !! at leas for me, haha.
Thank you !!
Regards
BigMango said:
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Click to expand...
Click to collapse
I downloaded the latest system-WHATEVER for dzo's froyo...on my hd2 you unzip a zip...extract Android dir to SD card and run haret to start android....where exactly is haret and the other things to actually boot the system? It's not in the .tgz's being posted in that sourceforge dir.
zenity said:
Had this problem with a number of builds, turns out that using the 1.71 radio was the problem, reflashing 1.65 radio cured my 'No Signal' problems, sometimes latest is not always best
Click to expand...
Click to collapse
good new, but unfortunatly is not the only problem...did you solved battery draind issue? if yes let me know pls
BigMango said:
If you want the latest apps and the best speed and the best stability, try dzo's froyo.
On my kaiser this build feels like it came flashed originally instead of windows mobile. In comparison, the other builds felt like "hacks": slow and/or buggy.
Click to expand...
Click to collapse
This has been my experience too. I tried several of each of the donut/eclair/froyo builds but the lastest kernel along with dzo's fresh froyo have made a world of difference. Way faster than even the donut builds that had previously been the faster of all of them.
famewolf said:
I downloaded the latest system-WHATEVER for dzo's froyo...on my hd2 you unzip a zip...extract Android dir to SD card and run haret to start android....where exactly is haret and the other things to actually boot the system? It's not in the .tgz's being posted in that sourceforge dir.
Click to expand...
Click to collapse
HaRET is a separate tool, you can get it here.
2011 Builds
Hi
I see that no new builds are posted and for all the latest downloads are from 2010.
I tried using aTools and also downloaded new Froyo from SourceForge.net, but no luck - Android hangs. What other files should be updated to for all to work?
I understand, that aTools ia a mgnificent tool, and everybody can "cook" his own version at home, but it is not totally clear regarding what should be used as basefiles, or if you download a distribution (like i did system-froyo-all-odex-29-08-11_19-patched.tgz) will it properly work, or what should be done to work.
Any advices?
I just erased my CyonogenMod because was a bit slow and as i read, DZO froyo should do it.
Creating the defaul.txt is not a problem. My concern is the zimage, the initrd and the androidinstall to work together properly.
Cheers
---------- Post added at 04:25 PM ---------- Previous post was at 03:31 PM ----------
OK? solved: i had to swith aTools to use a Stable branch and downloaded another initrd. Now all went smooth, and i have latest android on my Kaiser - working fast.
No FileManager, but WiFi works, so as Market, so just download
As a last step, i created with atools an androidupdate file to change my keyboard settings.
That's it.
Astro was not showing up in Market so i went here and downloaded the apps / widgets as a standalone update: forum.smartphonejunkie.com/windows-mobile-apps/202417-dzos-fresh-froyo-2-2-odexed-vanilla-rls6-7-2-10-a.html
I have a single problem now: market does not show all the apps. I search for something, gives me 411 results, but shows only 2 apps. Why is that?
How can market be fixed?
7th September 2010, 01:58 AM
Click to expand...
Click to collapse
This thread is a YEAR old. Of course there are newer roms after that date
I know there are newer roms, but had not been posted. But no problem, i found what i wanted, and i installed Android. Fixed market also.
I have another problem, and maybe i can reformulate the topic's title:
Which Android build is best for Kaiser's battery life?
I mean, the newest froyo drained my battery in one night. Windows Mobile last 3-4 days - depending on the use.
Tough question?

[ROM] WildVogue- Sense Froyo Edition

This is Froyo Sense coming to Vogue...
Calling does not work!!
The latest kernel 240x320 works the best.
It runs about as fast as Super Hero with no Overclocking when WildVogue is oc'ed to 520 mhz with Rogue tools
It runs from a system.img but i am working to strip it down to NAND
Data should be put on NAND
I have no clue if this will work on Polaris or Kaiser(It'd be helpful if someone could try...)
here are some preliminary screenshots(attached).
This preliminary(Beta) build:
Thanks vellowax for all the help
Thanks Thoughtlesskyle for your kind suggestions
And the whole community for all the previous work that helped me get here.
Its a port from WildPuzzle v8 for Wildfire
the androidinstall.tar is here
I'm looking for help learning and developing it but I'm coming along
This is a Beta I have no responsibility whatsoever if you brick your phone
If you have any suggestions please reply in this thread
Lovely!
jholtom said:
This is Froyo Sense coming to Vogue...
Calling does not work!!
...
I'm looking for help learning and developing it but I'm coming along
This is a Beta I have no responsibility whatsoever if you brick your phone
If you have any suggestions please reply in this thread
Click to expand...
Click to collapse
I will try this when calling works but keep your progress--make it mature!
Your download link doesn't work
I figured it out, but you might want to edit it and correct it.
I'll do some testing with this as I have a spare phone that's not activated.
jholtom said:
I have no clue if this will work on Polaris or Kaiser(It'd be helpful if someone could try...)
Click to expand...
Click to collapse
Excellent Jholtom, I've linked this thread in Kaiser forums, If noone will be brave enough to try it out I will test it in the afternoon. Great job!
link is doesnt work if i download this ill try yhe kaiser but icant download this link
The link is fixed now
can not install kaiser because low memory on nand
What Kernel are you using for this jholtom ?
I tried using the 11/29/10 2.6.32 kernel and was getting an error message.
I'll try again with the 10/29/10 2.6.32 kernel
Will give this a try.
I have it installed on the kaiser. It took a little work but its on. It will only work in 320x240 and with at least 200 mb for sys and then use an ext2.img for data. One problem I am having though is that all the HTC setup apps fc. I am going to try just removing them and see how that works. I used an old october kernel as I tried to update to the 11/29 one and was getting a module error and did try the android update and it didnt solve it so I rolled back.
trashed my super froyo so i guess ill give this a try........
great jobs,i'll give it a try
I managed to actually get into the rom finally. I took a setupwizard from a froyo rom and used it. I had to really fight with it though. The wizard ran poorly, and the date and time settings at the end kept fc'ing looping it back to the beginning of the wizard until finally it went into the rom. Going to test it now. I do not believe its a phone issue but a build issue as of right now. If you could remove the date and time settings it is referring to then I think it might be a bit better.
To run on the kaiser so far i've had to:
Set resolution to 320x240, Change partition to be 200 MB on SYS and rest on DATA via ext2.img . Afterwards I took a setupwizard.apk from a froyo rom and then renamed and replaced the HTCSetupWizard.apk the rom included as that was contributing to FC's.
On the kaiser wifi and the radio are not working. Both get an error when attempting to be used. I am going to try bringing in a etc folder from a working froyo rom and see if that solves the issue.
Lastly there is a power issue on the kaiser. It seems to keep thinking its almost near dead while on usb even though in the kernel it shows the proper power levels.
OK...
Tried this on my Vogue
the 10-31-10 2.6.25 NBH kernel will work.
BUT!!!
Do NOT try this on a class 2 card - OMFG... WAY too slow
Class 4 or class 6 at least...
Hopefully you can fit it in NAND soon?
aceoyame said:
I managed to actually get into the rom finally. I took a setupwizard from a froyo rom and used it. I had to really fight with it though. The wizard ran poorly, and the date and time settings at the end kept fc'ing looping it back to the beginning of the wizard until finally it went into the rom. Going to test it now. I do not believe its a phone issue but a build issue as of right now. If you could remove the date and time settings it is referring to then I think it might be a bit better.
To run on the kaiser so far i've had to:
Set resolution to 320x240, Change partition to be 200 MB on SYS and rest on DATA via ext2.img . Afterwards I took a setupwizard.apk from a froyo rom and then renamed and replaced the HTCSetupWizard.apk the rom included as that was contributing to FC's.
On the kaiser wifi and the radio are not working. Both get an error when attempting to be used. I am going to try bringing in a etc folder from a working froyo rom and see if that solves the issue.
Lastly there is a power issue on the kaiser. It seems to keep thinking its almost near dead while on usb even though in the kernel it shows the proper power levels.
Click to expand...
Click to collapse
@aceoyame
you are on a kaiser right?
Everything works fine on my vogue running 240x320 2.6.32-froyo-09/10/21 kernel
I get through the setup wizard fine and it runs pretty darn fast for sense when overclocked to 545 with Rogue tools
Wifi and radio have not been repaired yet from froyo i'm working on
Remember this is a Beta build
Does_It_Matter said:
OK...
Tried this on my Vogue
the 10-31-10 2.6.25 NBH kernel will work.
BUT!!!
Do NOT try this on a class 2 card - OMFG... WAY too slow
Class 4 or class 6 at least...
Hopefully you can fit it in NAND soon?
Click to expand...
Click to collapse
@Does_it_Matter
What device are you on?
I would try the 240x320 2.6.32 froyo 09/10/21 kernel for vogue(if thats what you have)
I dont know for kaiser of polaris
The build itself is a decent speed but the problem is, your not able to clock up with rogue tools until after you have everything set up. So default were at 400 mhz which is dirt slow. As for the kernel, I don't believe thats going to make a difference here. I did try to merge the etc folder with fresh froyo's and it made no difference. I thought maybe the missing wifi levels folder and a couple other things would help.
That means our problem is deeper somewhere else for those. Also, I would include rogue tools in the build itself to save some hassle downloading it at slow speeds.
fyi, i'm a kaiser developer. I know I never post on the vogue or polaris forums.
jholtom said:
@aceoyame
you are on a kaiser right?
Everything works fine on my vogue running 240x320 2.6.32-froyo-09/10/21 kernel
I get through the setup wizard fine and it runs pretty darn fast for sense when overclocked to 545 with Rogue tools
Wifi and radio have not been repaired yet from froyo i'm working on
Remember this is a Beta build
Click to expand...
Click to collapse
I am using L1qu1ds .32 kernel dated from 10/29/2010. It isn't a kernel issue that I am having but like I said, rogue tools cannot clock up the build until after installation.
aceoyame said:
I am using L1qu1ds .32 kernel dated from 10/29/2010. It isn't a kernel issue that I am having but like I said, rogue tools cannot clock up the build until after installation.
Click to expand...
Click to collapse
> /sys/module/clock_7x00/parameters/ahb_div
echo 500 > /sys/module/clock_7x00/parameters/a11
add that to the top of the userinit.sh to have it overclocked to 500mhz from the getgo. It will be overclocked throughout the boot process.
Thanks mssmison for the info.
incubus26jc said:
> /sys/module/clock_7x00/parameters/ahb_div
echo 500 > /sys/module/clock_7x00/parameters/a11
add that to the top of the userinit.sh to have it overclocked to 500mhz from the getgo. It will be overclocked throughout the boot process.
Thanks mssmison for the info.
Click to expand...
Click to collapse
Thats not the same as overclocking through atools right? I know that through a tools the kaiser gets unstable as all hell. For some reason it doesnt with rogue tools.

[Q] x1 nand successed,need more

I've been successed in x1 nand by flowing Alex&caliban2's instruction,and bring it to my country as the first one,thx to xda.
Now could anyone tell me how can i use "ast-alex-linux-xperia-android-2.6.35.tar.gz" which download from "gitorious.org/~ast/linux-on-qualcomm-s-msm/alex-linux-xperia"
your question leaves two reasons why you're asking this:
a) you want to learn how to develop kernel.
b) you think you're missing out on latest kernel and want to use it on your phone. or "bring it to your country".
well, if it really were a) you wouldn't be asking this in here, but would've found the answer how to compile kernel elsewhere. so let's go with b):
you're not missing out on anything. suspend-bug is still unfixed, flashing android to nand is nice, but even less usable than haret-version. alex was stuck on this, he went back a step and is rewriting lots of kernel-stuff.
quote from irc-chat today:
[22:22] <helicopter88> Alex[sp3dev]: will you continue to work on .35 or since now only 3.1?
[22:23] <Alex[sp3dev]> helicopter88: depends on whether i'll fix wifi on 35 or not. i plan to release a test build without wifi since many people use 3g instead
Click to expand...
Click to collapse
thx a lot! i see
I find good karnel is to be 2.6.27.46 its 890 kb big, you can find it in sensdroid v5 android from jertan93, and in hendroid android..
very good battery consumpiton last two days, charging is also working but not always so that is the issue, and some keyboard freezing sometimes...
Maybe is better kernel out there but i did find where...
nope, no better kernel. you're using ygge-kernel, btw. (zimage is part of kernel too)
there's midnight's kernel on neopeek, based on .27 from xdandroid, adjusted to x1. faster, no bug with hw-keys, charging works in theory.
but:
batt-meter is broken, it always shows 100%. so you never know how much juice is left. and it doesn't shut down the sys when batt gets critical. it runs till it's completely depleted. (=deep discharge = bad thing for the battery)
so you have to choose between the devil and the deep blue sea.
caliban2 said:
nope, no better kernel. you're using ygge-kernel, btw. (zimage is part of kernel too)
there's midnight's kernel on neopeek, based on .27 from xdandroid, adjusted to x1. faster, no bug with hw-keys, charging works in theory.
but:
batt-meter is broken, it always shows 100%. so you never know how much juice is left. and it doesn't shut down the sys when batt gets critical. it runs till it's completely depleted. (=deep discharge = bad thing for the battery)
so you have to choose between the devil and the deep blue sea.
Click to expand...
Click to collapse
Is this kernel "htc-msm-linux @ 20111001_013904" you are talking about?
I download that form neopeek.com but i don't have a link.
That kernel is 2.1 mb big, I just rename it and replace my ygge-kernel with this, i'm now using it for 15 hours.
I found that charging is working only when you leave phone alone, my battery menagment is working it it is not showing 100% all the time.
I charge my phone over night was shown 41 % on evening and 100 % in morning, now is on 82 %.
I also found that my benchamrk result is slightly less than whit 890 kb kernel (ygge) 560 points copared to 490 points whit this in quadrant standard.
Is there a way for fully market working?
Now I get only few app to be able to download couse others are "uncompatible with device"
huh?!
nah, that's original xdandroid-build. ("glemsom") midnight is based on it.
so you're saying they fixed batt-meter?! Oo this would be the best news ever.
i'm gonna test this right now, we'll have a serious talk if it doesn't work!
and yes, kernel being ~2mb is normal, it consists of zimage and modules.tar.gz. (i'm getting a slight feeling you didn't understand this, and just replaced the modules. "main-part" of kernel is in zImage. but let's see...)
yes i didn't replace zimage file i keep old one... but it is working i just rename the image to original.
here is download link of that file
http://xdandroid.com/wiki/Main_Page
and here is jerrytan93 talking about new kernal that is the most stable...
http://forum.xda-developers.com/showthread.php?t=1288765&page=3
post number #29 to #31
well i didn't find zimage of that kernel i'm still new in that
alright, time for serious talk...
of course batt-meter doesn't work. would've been a surprise. by not replacing zImage you kept ygge's kernel, just replacing the modules. (question is if the new modules even got unpacked to system)
thank you, i know where to download glemsom-autobuilds. ^^ but i prefer this link...
so remember, always replace both files! zImage is the more important one.
dunno why you shouldn't find it, it's called zImage_xxx_something_xxx. just rename it to zImage.
problem with most "cooks" here releasing roms is that they never tell which kernel they're uploading with their builds. just useless blabla like "the most stable, the best...!!!"
so here's an easy guideline:
- battery shows correct percentage, charging is buggy, hw-keys stop working -> ygge-kernel (march 2011)
- battery always shows 100% -> xdandroid-build ("glemsom") or a kernel based on it (midnight)
in theory, charging works on glemsom, bug with hw-keys is fixed
the reason why you get higher scores with ygge is because it has gpu overclocked (ygge-turbo < ygge-monster), glemsom doesn't. midnight's kernel has gpu overclocked too, it's faster.
agreeing with you apsolutley 100%
They only upload new build but newer talking about the kernels, few kernels didn't work for me because they are highly overclocked so didn't boot at all, i lost so many time studing for reason but i figured later it is from kernel...
Well keeping than my 11 march kernel 890kb it is working fine but have some bugs that i can handle with...
Thank you about sharing your knowledge and links nobody is talking about kernels and threads and posts are so messy with kernel information...
I have now two androids on 2 separete sd cards on
1. is hendroid here is my comparison with samsung galaxy 3.
http://www.youtube.com/watch?v=xU0dM168DDE
2. is sensdroid v5 which is better it looks good and it stable enough for daily use without need for windows mobile.
Did you try arcdroid v2?
On each android build my market is not working as i should, do you know reason for that and is there a fix?
I download stock gapps with everybuild.
good. but listen, you're mixing things up again.
- i wrote gpu-overclock, as in graphics (not cpu). this has nothing to do with what you set in startup (=cpu-speed), gpu-clock is fixed.
- keep zImage as well, it's the most important part! (kernel-files always have 2.x mb in total)
nope, tried almost none of these roms. if i'm not running nand for fun, i'm running neofroyo.
not interested in themed roms which are based on neofroyo anyway. the android-part in my sig is there for a reason.
I am a newer about this, waiting for a stable nand andriod system.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
There are so much I can't understand , Admire you so much!
Here is quote from jerrytan93 how to roll back Market to 3.13 version and stop future updates. This is major problem on all android version so i found it to be useful:
"Apps not compatible is because of the lastest version of Market, Market had updated automatically from 3.1.3 (originally in GAPPS package) to 3.1.5 version which was unstable now. I found some a solution for you all:
Use Terminal Emulator (if you don't have it, download in Market),type the following command:
su *PRESS ENTER TO GAIN SUPERUSER PERMISSION*
pm disable com.android.vending.updater *PRESS ENTER AGAIN*
This will disable the Market Updater from updating the Market.
After that, go to Settings > Applications > Manage Applications > Market > 'Uninstall updates' and then 'Clear data'
Your market will roll back to previous version. "
@caliban2 thanks, i messed some things when extracting the glemson kernel, the same problem for me battery is 100 % all the time.
Notify me when there would be best kernel out.
I don't use the market at all....can download apps from many other webs,try to use ucweb.apk which can download from www.uc.cn
haa~~~new nand android can be tested now,for i can't post in XPERIA X1 Android Development,i just say thx to Alex here!!!

[NAND][pre-ALPHA] Kovsky ICS 4.0.3 testbuild0

Based heavily on TeamICS' work on HeroC, here is some very early initial work on ICS for the HTC Kovsky, AKA Sony Xperia X1. Built from AOSP source, with source available.
This is NOT for the faint of heart, and as far as I know nearly everything is broken right now. Instructions for building are coming soon - meanwhile, source is available at https://github.com/Zorlin with bits from https://github.com/CyanogenMod and https://github.com/TeamICS
Credits:
- TeamICS for all their ridiculously awesome work on Hero/HeroC
- CyanogenMod team, on which some TeamICS work is based.
- IceDroidV2 for the installer and current (slightly modded) kernel/boot.img - see IceDroidV2 thread for appropriate credits and source.
Currently working:
- Boots!
Currently not working:
- Everything else
- ADB
Notes:
boot.img is made from applying the ICS porting guide to IceDroidV2's boot.img
Currently there's a "hack" to attempt to get adb working - I threw in a copy of busybox as /system/bin/sh. Need to work out a better way, since it really didn't work...
I've got a bunch of ideas, but it's late, so... here:
DOWNLOAD:
testbuild0 - "The Magic ZIP File"
I can't believe it. OMG !!
BUT
Is it really ICS or just some skin for android 2.3 ?
X1 long live
Garena said:
I can't believe it. OMG !!
BUT
Is it really ICS or just some skin for android 2.3 ?
Click to expand...
Click to collapse
It's really ICS, which is why so little works. Gingerbread kernel for now, though.
woooaaaahhhh.....i love u full to all developers x1 the brilliant smart man ....kovsky never die !!!!
Do you really think you have enough background knowledge to get this off the ground? Or is it more of a "lets see what I can do" thing?
wallaceff said:
Do you really think you have enough background knowledge to get this off the ground? Or is it more of a "lets see what I can do" thing?
Click to expand...
Click to collapse
Yes and no. I think I can bring it to the same state as HeroC, maybe sans camera, and port hardware acceleration if/when they get it working. Kernel isn't my forte, though. At the moment adb is a major and confusing stumbling block... I'm missing something stupidly simple.
can we install it or it's not ready yet
I installed it that we install IceDroid v2 but nothing happened
It was stuck in android boot
mahmoodifar said:
can we install it or it's not ready yet
I installed it that we install IceDroid v2 but nothing happened
It was stuck in android boot
Click to expand...
Click to collapse
You install IceDroid V2 first and then overwrite it... but no, at the moment this is just for developers and tinkerers.
oh damn how nice would that be!!!!
go ahead zorlin an thx a lot for your work
Hi Zorlin how is going ur work ?
Slow... lots of real-life stuff going on. I'll probably publish build instructions on the weekend so others can start contributing.
Haven't forgotten you guys though.
Hello. Any progress or updates of Your work?
Oh my god..
I hope this really happen....
I will do wait your work!
revol5 said:
I hope this really happen....
I will do wait your work!
Click to expand...
Click to collapse
I will try to make something based on @Zorlin sources from #1 post. At all, probably He have own things to do so that is why He not respond.
fergy said:
I will try to make something based on @Zorlin sources from #1 post. At all, probably He have own things to do so that is why He not respond.
Click to expand...
Click to collapse
Your signature shows that you have a own kernel for NAND for X1?
What is working etc? maybe you could share it, when it has benefits to the current published ones
EDIT: maybe you could join zargloub and midnight for kernel dev?
neoofoox said:
Your signature shows that you have a own kernel for NAND for X1?
What is working etc? maybe you could share it, when it has benefits to the current published ones
EDIT: maybe you could join zargloub and midnight for kernel dev?
Click to expand...
Click to collapse
Hello @neoofoox.
Working everything except camera, fm radio and bluetooth (atm working on kernel to see where is problem).
Charging/discharging (at last I think it is ok as phone discharge within 20 hours->3.5 yrs old battery<- using push, wifi, bluetooth and location with 10-15 minutes of talking)
Also, phone wake asap You press power, ok or lock button (also with double security using pattern after normal unlocking)
I also don't think that this is right thread for something other than ICS work conversation.
When I got all things working proper, be sure that will make an new thread with image and patches to kernel.
BR,
Ramon
EDIT: Yeah, I will be happy to talk with @zargloub and @midnight regarding kernel.
EDIT2: Regarding sharing, I use only main system of Cyanogen but My own kernel, so as I say, until kernel completely work, I will not share it because of lot's of questions what users cannot fix until I fix holes inside kernel.
@fergy Last question ot jooc Does your phone reboots if you miss a call?
Sorry guys, I might be retiring my Kovsky... I'll publish build instructions and sources etc either way. If you don't hear back from me, assume I retired it
I'm getting fairly hopeful that you'll get decent ICS on the Kovsky soon though.
EDIT: Yup, it's official. I turned in my Xperia X1 in exchange for a free, off-contract Samsung Focus S (which I'm reselling) through the recent Microsoft promotion. I'll still have it for a week - I'm going to try and get ICS on it before then, but I don't really know what chances are like.
After that, I'll turn this over to someone else who can hopefully carry it through.
fergy said:
Hello @neoofoox.
Working everything except camera, fm radio and bluetooth (atm working on kernel to see where is problem).
Charging/discharging (at last I think it is ok as phone discharge within 20 hours->3.5 yrs old battery<- using push, wifi, bluetooth and location with 10-15 minutes of talking)
Also, phone wake asap You press power, ok or lock button (also with double security using pattern after normal unlocking)
I also don't think that this is right thread for something other than ICS work conversation.
When I got all things working proper, be sure that will make an new thread with image and patches to kernel.
BR,
Ramon
EDIT: Yeah, I will be happy to talk with @zargloub and @midnight regarding kernel.
EDIT2: Regarding sharing, I use only main system of Cyanogen but My own kernel, so as I say, until kernel completely work, I will not share it because of lot's of questions what users cannot fix until I fix holes inside kernel.
Click to expand...
Click to collapse
With these things working it is working perfectly, who need wifi if you can use mobile Data to access Internet and who needs bluetooth if you can send files via Email or connect your Phone via headphone port to your soundsystem etc..
I would test that if it becaume available and will report every bug etc. You could choose some people for testing which know something about that / for reporting bugs. So you can fix them and make the kernel 'perfect'.
Zargloub stopped developing and he has his files on gitorious so you could merge the kernels, here is working bluetooth and wifi (but it shows bad signal strenge)
Are you on github or gitorious so other devs can see what you are doing and maybe can help or people see what you are working on now.
I would love to test it, because for me it is allready perfect I hope we read something from you soon. You are our last hope
EDIT: sp3dev was also working on kernel you can get the sources here and here
EDIT2: I asked sp3dev if he would help, but he cannot for 2 reasons, first he has currently no time, the second reason is that he don't want to work on project which are close-source. Maybe you should think about releasing that before it is completely finished or make it open-source. Your device is old and that slow down the process a lot.

Unofficial build of CyanogenMod 11.0 for GT-I9506

Hi,
since the official maintainer "solk2" for the GT-I9506 moved on to CM12 before providing a final build incorporating his latest fixes I decided to make my own builds.
According to my personal experience the battery life has vastly improved. In particular the power consumption while the display is off has decreased substantially. Solk2 has apparently fixed some issues with the kernel so the battery issues are gone. So for everyone not yet willing to transition to CM12 (in my case inter alia due to the currently unstable state and the lack of a stable Xposed framework in Android 5) this might be a good alternative.
I will gladly share my unofficial ROMs, however I would need someone to host the files in order to do that. If anyone would be so kind as to host ROMs please let me know.
If any relevant code changes to CM11 will appear I will most certainly compile a new version.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from Cyanogenmod, solk2 and others. So every credit goes to them.
I will not and cannot make any changes to the code. The only thing I can do and will do is build a ROM thereof in case some interesting fixes etc. appear. However, since CM11 is becoming outdated there will most probably not be a lot of changes to come.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like the original ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (with Samsung firmware of 4.4.2 nordic countries) and runs without obvious issues. Your mileage may vary.
Here is the current version, including the CM-11.0 code base up to http://review.cyanogenmod.org/#/c/97688/ :
https://www.mediafire.com/folder/j0jynk3en95j5n1,soag9jcmrcajdhq/shared
* Note *
At least some of the issues with solk2's latest official builds were apparently caused by preceding changes to the kernel code. My builds use the latest code base of February 16 incorporating solk2's latest fixes (see https://github.com/CyanogenMod/android_kernel_samsung_ks01lte/commits/cm-11.0).
Unless solk2 will make further changes to the kernel (which I doubt as he has turned his attention to CM-12) the changes in my builds are only related to merged changes in the official Cyanogenmod code for CM-11.0 (see http://review.cyanogenmod.org/#/q/status:merged+branch:+cm-11.0). In other words the kernel will remain the same, even if the build date thereof may change.
Thank You. Perfect rom. in 2015-05-20 mms is working by default I have not find any bugs.
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
ilfavi said:
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
Click to expand...
Click to collapse
You do not need flash any stock. Just flash TWRP, make full wipe and flash this rom + gapps
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
ilfavi said:
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
Click to expand...
Click to collapse
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
And thanks for your work !
3lambda said:
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
Click to expand...
Click to collapse
I suppose so... Since it does use the official CM sources, just go ahead and try it.
Thanks for the reply
Do you have some knowledge on building stuff ? (via linux command, problem etc)
What should happen if I update via OTA as it ask me to do?
edit: I realized that the updates suggested are cm12 so can be ignored
I had one strange bug in this rom (maybe reason was in gapps): Go to SMS app, push new and write name in address line from above: phone getting list of contacts to chise. You choisew one and see wrong number (without region code) in address line.
If you push on contacts button and choise contacts here everything will be ok.
NeuDLi said:
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
Click to expand...
Click to collapse
Do you know to make compatible with this ROM, the Arter97 kernel?
Alexyerga said:
Do you know to make compatible with this ROM, the Arter97 kernel?
Click to expand...
Click to collapse
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
NeuDLi said:
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
Click to expand...
Click to collapse
Because the Solk2 kernel causes random reboots sometimes
Alexyerga said:
Because the Solk2 kernel causes random reboots sometimes
Click to expand...
Click to collapse
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
NeuDLi said:
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
Click to expand...
Click to collapse
Last time ago arter's kernel was compatible but he removed the support because he didn't have time to maintain two kernels.
Thanks anyway NeuDLi, i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Alexyerga said:
i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Click to expand...
Click to collapse
Well, another problem... I'm not sure if it is a bug in settings.apk or only in connection with our device. However, when you check the option is always ON, and upon leaving the settings.apk it will always return to being ON. So at least I can say that turning if OFF cannot have had an effect because it was never turned OFF.
However, I will try with KSM disabled now. For the time being you can manually disable it and lock this state (well at least until next reboot) by doing the following in an adb session or the terminal:
echo 0 > /sys/kernel/mm/ksm/run
chmod 444 /sys/kernel/mm/ksm/run
Another way would be to recompile the kernel with the option disabled. It would be far better to fix the issue in settings.apk. However, to file a bug report one would have to check if the behaviour is the same in the official nightlies... I read that someone reported this as a bug for the Oneplus One, but it was never resolved.
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
iBuu said:
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
Click to expand...
Click to collapse
Although I cannot often enough remind everyone that I did not provide or change any code but just build it that's still not too bad for the first build of a guy not that much into coding .
After a weekend with not much use but some hours of listening to audio books I was left with 21% charge after more than 3 days (see attached screenshot). That's just awesome! So I believe it can safely be said that any power consumption bug was resolved by solk2's latest patches to the kernel.
Also I believe that turning off kernel samepage merging might have helped additionally, so I encourage everyone to try it as well (see above post for manual way to turn it off as bug in settings.apk won't let you otherwise). In my opinion this option should default to off as it is said to be potentially unstable and the I9506 surely has enough RAM not to need it. So I prefer to lessen CPU load for longer battery life in exchange for potentially increased RAM occupation.

Categories

Resources