Just replace startup.txt and get kernel from http://glemsom.users.anapnea.net/android2/htc-msm-linux/
i use 20101103_215747 it works like a charm
i overclock my blackstone to 710.4Mhz !
with this build y can play angry birds beta also!!
Happy new year!!
http://www.youtube.com/watch?v=b9syPXkRlQ4
video sorry about bad quality
and here y can get it
http://narod.ru/disk/1838366001/Android.zip.html
thanks anyways
but ......
is this android 2.1 iwth htc sense
and has the latest 3d drivers
and the fast kernal??
Hi
dont know really ,im trying to find nice android builds and tested almost every build for last 1 year. And i think this very good and stable. Also 3d works fine.
I put some video then y can see,or just try it
Btw it is klinux build with bugs repairs.
i got this build
its the best with the features (sense) and i only play zenonia 2 and baseball superstars
i overclocked it to 614400 ( i dont want any sudden rebooting)
btw
the cool thing is
i got two android builds which i use
frx03 blazn (11.26 drivers)
Klinux htc sense with bugs fixed
ALL IN ONE SD CARD (2gb)
how cool is that
is there any mirror ? The download doesnt work for me
dragvandil said:
is there any mirror ? The download doesnt work for me
Click to expand...
Click to collapse
here you go
megaupload
http://www.megaupload.com/?d=8JEWPUVU
Hey...
What about the battery life... How often do you have to recharge per day?
Best
Latest was over 24H with playing and testing it, i think it is good. I use in 2g mode and if idont use data it is off, and allso backround data is off. Also i use that build with stopping sense and using Launcher pro. it is faster and dont use battery that much.
Spige said:
Latest was over 24H with playing and testing it, i think it is good. I use in 2g mode and if idont use data it is off, and allso backround data is off. Also i use that build with stopping sense and using Launcher pro. it is faster and dont use battery that much.
Click to expand...
Click to collapse
Ohhhh
i always use sense
hmmm
i am taking it off from now on
Hi
Yes do that, if y dont know how then: go to settings/applications/manage applications wait to computing and then search HTC sense and force to stop then back and then press power button and select launcher pro.
I'm totally noob with installing Android on the Blackstone. How can I install this version?
Just tried this out on my Touch Pro2. Everything bar the Camera and Bluetooth is working perfectly! Nice job!
I can not try this version because, when I start it, it stops and reboots by itself.
Also calibrate the touchscreen is a problem.
I've tried with different versions of Kernel and zImage
HTC Blackstone
startup.txt
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3 acpuclock.oc_freq_khz=650000 htcblackstone-panel.no_bkl_off=1 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
boot
My start up
This is my startup :with overclock settings
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage_20101103_215747
set initrd initrd.gz
set cmdline "acpuclock.oc_freq_khz=720000 lcd.density=210 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-2,-1,3"
boot
Hi thank you
@=Spige
with you startup i've got "waiting for sd card" .....
@gudi
with you startup i've solved ... bu i've got again the problem with the touch calibration ... to solve this problem I used my old file ts-calibration
however, this is very strange
thanks to both
no moon or sun during animatio
when the weater animation is doing its animation it shows a white square an not the moon or sun, is there a fix for that? and why are the live wallpapers not working?
in the glossy theme build they are working, cant we combine sertan things of these both builds?
ok only solution for waiting for sd card in another card, i have that same prob with sandisk sdhc card. Try Kingston card , now i have 2 microsd working.
strange i dont have that problem with this build. But another builds i have that also. Try to download exacly same build in here cause i saw that they are little bit diffrent size. Use Google chrome then y can translate that russian language to your own. Hope this helps y...
Related
Beta testing of a new kernel that allows over clocking up to 660mhz. I have no time to do a lot of testing. So far MCR rom 3.2 is stable and fast with it. So I am calling for testers. The kernels are using ramzswap.
Download
Note: It will not work on 2.x rom as it is a 2.6.27 kernel.
This is great news. I would try it, but I have a CDMA Hero.
I think this also works for 2.1 ROM; I'm using Vanillain 1.0 and I went from 145 CPU benchmark to 154...
how to apply?
and does setcpu support this setting yet?
thanks for the work
1) Download the SetCPU in the link
2) Drag the SetCPU file into your SD card
3) Open and install using any file manager (I use Astro)
4) Download the setcpu.txt file into your SD card (not into a folder)
5) Open SetCPU and press Menu > Device Selection > Scroll all the way down to "Custom Frequency Config" (last on the list)
6) Then set up the frequency as you desire
is this based on teknologist's kernel? this shall be included in MCR once stable enough.
Is root needed?
Yes you need root for this to work, and just on a side notice using the overclock widget seems to work to.
worked on my hero i guess.. but how stupid m i, i tried edit the txt file and push into my nexus and try the settings... damm.. f*ck, it did not work at all... damm...
doesn't do anything for me according to linpack. Same amount of Mflops/s
edit: and screen went black and never got out of it.... :S
660 MHz ?? Bye bye batery...
Myriad Group is developing a new virtual machine for android that increases 3x the speed of the system running aplications, with the same hardware, and a optimized use of the batery and will allow richer grafics... The name of the project is Dalvik turbo and it will be show on the Mobile World Congress of Barcelona...
You can read it here: www(dot)mobileburn.com/news.jsp?Id=8684
I hope we can use it to our Hero's ...
Dalvik Turbo looks extremely promising. If 3x performance can actually be achieved, then we have to ask Google... what were you thinking with Dalvik's original design?
Please, read this:
http://android.modaco.com/index.php?s=&showtopic=302182&view=findpost&p=1185063
What do these numbers mean?
Sergio PC said:
Seems to be working fine, you can tell in various instances such as scrolling in menus etc...
Lox_Dev you the man! thanks.
Click to expand...
Click to collapse
BogoMips is not the clock!
It's the efficiency of running a bootonly calibration loop.
This doesn't mean that Lox_Dev work isn't a great thing, though.
so in a nutshell, whith this mod does hero run faster or not?
ermacwins said:
so in a nutshell, whith this mod does hero run faster or not?
Click to expand...
Click to collapse
I don't think so.
Just because your car shows 200mph in the speedometer doesn't mean it can go that fast.
Really, read here: http://android.modaco.com/index.php?s=&showtopic=302182&view=findpost&p=1185063
Uqbar said:
BogoMips is not the clock!
It's the efficiency of running a bootonly calibration loop.
This doesn't mean that Lox_Dev work isn't a great thing, though.
Click to expand...
Click to collapse
Alright i understand ill edit that post to find some explanations.
Thanks man.
Hello I'm flash that kernel and after reboob i see circle showing droid logo => htc =>droid and that replay again and again some clue ?
After a backup I usually wipe everything out before installing a new rom.
Try this.
Here are the nbh files compiled upto the last change in the Dzo's GIT on the 03-05-10.
15-04-10 Updated - Uploaded new nbh's due to not working with Sense 2.1 build. Thanks kallt_kaffe & toasty_.
22-04-10 Updated - Latest Change from Dzo's git - Fix GPS enable/disable race condition on Kaiser.
26-04-10 Updated - Latest Change from Dzo's git - Add delays to vfe commands
29-04-10 Updated - Latest Change from Dzo's git - Add a delay to the adsp code and change the dsp irq handler.
03-05-10 Updated - Latest Change from Dzo's git - Add adsp delay and irq trigger change for cdma devices only.
PS: You may have to wipe system to get this to work so if your currently happy wait until you update your andriod system.
Here's the ones for the AT&T Tilt.
Updated 03-05-10 - See Post 1
What's the difference between the files in the first post compared to the second post?
Dukenukemx said:
What's the difference between the files in the first post compared to the second post?
Click to expand...
Click to collapse
ATT Tilt Keyboard layout.
tried this with eclair, and it gets stuck on at
Code:
A N D R O I D
xPreSiDenT said:
tried this with eclair, and it gets stuck on at
Code:
A N D R O I D
Click to expand...
Click to collapse
What build of eclair did you use as it sounds like the kernel is booting as it get's to where ANDRIOD is displayed.
I'm been using polymod 2.1g + the upgrade posted in the thread, it's been working ok for me. My knowledge of Andriod and linux is still quite limited, so I'm not sure what else to recommend.
happened to me too... just reinstalled the system with androidinstall.tgz (without wiping data) and all went well
I'm also using 2.1g, but I dont know about the update. Ive installed all the updates (polymod_2.1g-BT_Update.zip and the full market update) posted after 2.1g.. are there any more? I dont know how to update the kernel as is posted on the first page:
UPDATE 19 Mar 2010:
Latest .NBHs and Kernel for Kaiser & Polaris posted to http://ponack.net/poly/BT_Update/ , thanks again to Mr PaveL for building them.
If you're using HaRET, the same zImage now works for Donut AND Eclair. For Eclair you will need to add hw3d.version=1 to the command line in your default.txt . If the previous BT zImage wasn't working for you, this one should. (New Vogue .nbh and the same kernel can be found @ dzo's site.)
Click to expand...
Click to collapse
as far as I know the zImages are for haret users only... am I wrong?
xPreSiDenT said:
I'm also using 2.1g, but I dont know about the update. Ive installed all the updates (polymod_2.1g-BT_Update.zip and the full market update) posted after 2.1g.. are there any more? I dont know how to update the kernel as is posted on the first page:
as far as I know the zImages are for haret users only... am I wrong?
Click to expand...
Click to collapse
ZImages are for Haret you are correct.
PolyMod Update
http://forum.xda-developers.com/showpost.php?p=6105602&postcount=3011
What's the difference between the different Panel types? How do I know which one to use?
OshiHidra said:
What's the difference between the different Panel types? How do I know which one to use?
Click to expand...
Click to collapse
board-htckaiser.panel_type
Panel type used to power the panel off and on (see also vertical line issue)
[edit] Values
* 0 - Don't power off the panel
* 1 - Sony
* 2 - Topoly
* 3 - Topoly
Shamefully copied from here.
I just tried all three and settled on the one I think worked the best.
fultotop said:
ZImages are for Haret you are correct.
PolyMod Update
http://forum.xda-developers.com/showpost.php?p=6105602&postcount=3011
Click to expand...
Click to collapse
thanks alot! Am gonna try it right away. I seriously hope it solves my wifi issue :S
fultotop said:
Here are the nbh files compiled upto the last change in the Dzo's GIT 4 Days ago Fix kaiser usb (same as polaris). These are the first time I've done this, but I've tested them on my Kaiser.
Click to expand...
Click to collapse
Just a heads up. I also make my own NBH's and I noticed today another thing in tinboot.S that aren't up-to-date with the NBH's that DZO compiles.
Use a hexeditor and you will see that the mtdparts parameters are different. I've updated my NBH build (another thread here) and the noticable difference is that the partition sizes are different so that the system partition is larger than before. The data is still the same though.
I'm currently testing the Sense 2.1 build and it requires a larger system, that's why I noticed the difference.
Ok got the same problem with the nbh from DZO and yours. Problem is DZO uses other sizes and adresses for mtd-partitions, so if you are using Data and/or System on Nand, data can' be found.
Code:
DZO's NBH from 8th April:
mtdparts=msm_nand:[email protected](nand)ro,[email protected](root),[email protected](system),[email protected](userdata)
Yours:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
maybe it works if you first flash nbh and then reinstall system and data
EDIT: OK, was allready said - I've been to slow
kallt_kaffe said:
Just a heads up. I also make my own NBH's and I noticed today another thing in tinboot.S that aren't up-to-date with the NBH's that DZO compiles.
Use a hexeditor and you will see that the mtdparts parameters are different. I've updated my NBH build (another thread here) and the noticable difference is that the partition sizes are different so that the system partition is larger than before. The data is still the same though.
I'm currently testing the Sense 2.1 build and it requires a larger system, that's why I noticed the difference.
Click to expand...
Click to collapse
Thanks that would explain why it wouldn't boot without reinstalling the system partition for some people.
toasty_ said:
Ok got the same problem with the nbh from DZO and yours. Problem is DZO uses other sizes and adresses for mtd-partitions, so if you are using Data and/or System on Nand, data can' be found.
Code:
DZO's NBH from 8th April:
mtdparts=msm_nand:[email protected](nand)ro,[email protected](root),[email protected](system),[email protected](userdata)
Yours:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
maybe it works if you first flash nbh and then reinstall system and data
EDIT: OK, was allready said - I've been to slow
Click to expand...
Click to collapse
Thanks you saved me some time, I've updated them see first post.
FYI, all the links in the first two posts are dead.
EDIT: nevermind, evidently I'm having a serious problem with my browser right now. Links are fine.
You say these work with the Sense 2.1 build but that requires HVGA while according to the file names these are QVGA. Are these actually HVGA (480) but just have the wrong names?
Nevermind, tested it out myself and they really are 320 builds. Well, nothing a little hex editing couldn't fix...
OshiHidra said:
What's the difference between the different Panel types? How do I know which one to use?
Click to expand...
Click to collapse
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
byron0318 said:
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
Click to expand...
Click to collapse
Yes. Yes it does.
byron0318 said:
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
Click to expand...
Click to collapse
On your TyTn II perhaps panel 2 or 3 work best, however all 3 panel types are used on most models of kaiser, depending on supply at the time of manufacture, so there is no really easy way to tell which panel type you have, apart from disassembling your kaiser and checking the part numbers on the lcd panel itself.
I have 2 almost identical kaisers (KAIS130) both are identical in every way, apart from the lcd panel, one has type 1, the other type 2.
Pixel errors, colour problems, lines and streaks on the display, are all symptoms of choosing the wrong panel type for your device, and the only thing you can do is use a different nbh, or change panel type in default.txt until you find the correct one.
The last days Froyo rubbed all my nerves. As promised earlier to a few members I decided to update CM5-builds. And here is the first Final release of my Eclair-builds:
VaniljEclair from kalt_kaffe (original thread from HTC Kaiser)
Changelog:
[*]V1.1 is a 1-file-download. The ZIP-Archive contains everything you need!
What's Included:
Latest LauncherPro
Compcache activated
Browser removed and replaced by Dolphin Browser HD
Performance tuning
[*]1-file-download due to FINAL release V1.1 -> read Install Instructions carefully!
To get the full performance out of all my builds you have to open all apps once and then restart your device 1-2x times
Known Bugs:
Camera is broken
If you wake up your device and the screen stays black -> just slide from left to right as you would do when unlocking the phone -> The display will wake up immediately.
Used sources for this Port:
kalt_kaffe's VaniljEclair ROM for HTC Kaiser
XDAndroid: rootfs + kernel (2.6.27)
Credits go to: Cyanogen + Cyanogen-Team, kalt_kaffe, XDAndroid-Project, Balsat and top everyone else whom I have forgot! You may consider a donation to all of 'em!
Download + Installation Instructions (read carefully):
Neopeek's VaniljEclair-Port CyanogenMod 5.0.8
RE-EDIT: This Text is copy&paste for all threads on all compatible devices! Everything works fine for my Diamond. I still have no other device then a Diamond. I am still a one-man-show regarding my Android-Ports. So don't blame me for anything that doesn't work for you on any other device...
thank you very much
Can you post some screens please....
Hi vatoloco,
I couldn't see anything run on my Blackstone,always show black screen.
Thanks for the good work
mike86_tsai said:
Hi vatoloco,
I couldn't see anything run on my Blackstone,always show black screen.
Thanks for the good work
Click to expand...
Click to collapse
me too,it`s always show black screen
try turning off 3d in startup...
vatoloco said:
try turning off 3d in startup...
Click to expand...
Click to collapse
How can i do it? where?
always black screen, what to do?
Finally, I can see the main screen, just follow the below setting
Originally Posted by NemanjaLO View Post
Got it WORKING without force close!!!
Before first boot edit your startup.txt and add this to "set cmdline" "hw3d.force=1" and keep TouchFlo running in WinMo. You also need to disable boot animation in tar.gz package: For this you need linux system, open your archive in linux and find init.eclair.rc file in init.cfg folder and disable this lines:
#service bootanim /system/bin/bootanimation
# user graphics
# group graphics
# disabled
# oneshot
But after boot , I could turn on the wifi,but couldn't get ip.
GPRS ok.
Bluetooth ok,but the voice have a lot of noise,microphone ok.
GPS ok.
speed is good.
Thanks for the good work
you dont have to do that anymore, hw3d is working, but gralloc from the "hw3d thread" has to be replaced to /lib/eclair/hw/ & /system/lib/hw/ and also for me wifi wont work if i use updated kernel. so i extract wlan.ko from the modules and place it to /system/lib/modules/ ...
overall the build seems stable.
# I get 16.5 fps on neocore benchmark. (pretty decent i believe)
#However i am facing issues with wifi not able to get dhcp address (have to set static)
# google talk and gmail app aint working (force close). need to probably replace the apps. (not sure)
thanks neopeek.
vatoloco said:
Camera is broken
Click to expand...
Click to collapse
Means: Not working or really broken???
First post updated with V1.1
Broken means not working!
For those who got this release working .
can you upload the files that you had to modify (startup,tar.gz...) , so it would be a more easier process for non-experienced users to download this release and run it by one button ..
thanks in advance .
Where's the problem, huh? Move to npkinstall-folder. rename diamond.txt to startup.txt there! Start install.exe! After installation move to startups-folder and copy startup.txt from diamond where haret.exe is and simply run haret.exe! That's all! Sometimes I ask myself if someone misses reading my instructions. I think renaming 1 txt-file and copying 1 txt-file should be simple enough!
That's 2 steps!
Neopeek,
For blacstone users, need to replace the gralloc file in your builds to get the hw3d working. which if not done gives black screen and 3d is not enabled.
Neopeek,
For blacstone users, need to replace the gralloc file in your builds to get the hw3d working. which if not done gives black screen and 3d is not enabled.
Click to expand...
Click to collapse
...but boots up for you w/o that gralloc? So kindly link me to that gralloc so I can implement it. But first if it boots up just let me know if everything else works or something Blackstone-specific still needs a fix. Damn it! I have no Blackstone. SO I need you to test and give me hints!
I'm going to format to ext2 partition to try
Many thanks for the chance to get android on my blackstone man
I already downloaded the v1.1,but when I run the installer, the system show it will formate my ext2 partition,and then say cann't open xxxx.tar.gz,when show reboot in 7 seconds.But nothing happen after 7 seconds.
When I reboot manually,I found all of the android I in my card was gone,it empty because the sdcard already be formate during the installer running.I try two times the result is the same.
Fix already,It's my problem, I don't know why between the ext2 and fat32, there is 7.8MB no use, so after I repartition my sdcard, now is ok to install the file.
After waiting over 20 minutes, still black screen.
Neopeek,
For blacstone users, need to replace the gralloc file in your builds to get the hw3d working. which if not done gives black screen and 3d is not enabled.
Click to expand...
Click to collapse
I think I have to include this for you to get it working for you. On the other side you may try to set "hw3d.force=0" in startup.txt. Thanx indeed for testing!
Yes, after replace the gralloc.msm7k.so that from hw3d thread, now it boot ok. after boot the wifi is also no problem to get ip.
I pulled the latest kernel tarball, fixed and tweaked a few things, then compiled it on my Rhodium. Although it works well on my Rhodium, I cannot guarantee that it will work on yours. In addition, it is guaranteed NOT to work on any other since I disabled support for it in .config.
You can install this kernel just like the one you would off the autobuild. The kernel is named -fox-YYDDMM where the date is when I pulled the tarball. While suggestions and feature request are welcome, it takes me ~2.5hr to go through one compile, so don't expect a new build very often.
You need the patched haret.exe as well as an additional line in startup.txt to boot this kernel. Instructions for that can be found at http://forum.xda-developers.com/showpost.php?p=14519408&postcount=1.
Latest (8/20) at http://db.tt/OeRyLYu
Changelog:
8/20 http://db.tt/OeRyLYu
microp: Upstream version of LED patch from Detule. Please note the requirement of updated lights.msm7k.so still applies.
8/16 http://db.tt/3UWBs3y
microp: Updated microp LED patch from Detule, now with more blinkenlights goodness (and yes, it even blinks). In order to use this, however, you need an updated liblights from http://db.tt/ZUjymT9. The file should be bind-mounted on startup in your froyo.user.conf, ie: mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so
8/15
microp: Proposed LED patch from Detule, mailing list has instruction on how to play with the blinkenlights.
.config:
Enabled IP_NF_TARGET_REDIRECT as a module because it's needed for certain app.
Started from clean source to get rid of any residuals.
8/11
Compcache: Included 0.5.4, patched kernel to support the swap notify
clock-wince: Added a debug output that shows freq requested, closest set, and the calc, without needing clock_wince.debug_mask=15.
.config notes:
LZOCOMPRESS/DECOMPRESS is built-in to the kernel. Therefore if you want compcache, you just need to insmod xvmalloc.ko and ramzswap.ko.
8/9
Upstream: htc_headset_microp fix
acpuclock: Changed turbo mode+20mhz only when acpuclock.force_turbo=2 is set. Also, overclock by 20mhz for any bus speed >100MHz.
modules: Use strip --strip-unneeded.
8/6
acpuclock: Change turbo mode t->axiclk_khz from 160000 to 180000. AXI clock control the bus freq, and upping it should make overall performance better.
clock-wince: Add supposed support for 48Mhz SD clock from .35. HOWEVER the kernel claims calc_freq is 61.44Mhz according to clock_wince.debug_mask=15. You also need to add msmsdcc_fmax=48000000 in order to use this clock anyway.
proc_comm_wince: Fix long-standing issue with msm_proc_comm_wince_pending_ints & DEX_INT_VBUS check which clobbered pending_int. You should no longer have a SoD during transition changes to/from suspending while inserting/removing the USB cable.
microp-k*: Got rid of the printk spam of backlight/keyled status changes.
.config changes:
1) Change default I/O scheduler to deadline. Our kernel does not do well with noop.
2) Change default AMSS firmware interface to 6125 which is what I have on my RHOD400. You can check yours (which is in the modem) by running dmesg | grep AMSS.
3) Change kernel default sleep_mode from CONFIG_MSM7X00A_SLEEP_MODE_POWER_COLLAPSE_SUSPEND to POWER_COLLAPSE. This is usually overridden but makes pm.sleep_mode=1 unnecessary.
4) Change CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN from 128MHz to 112Mhz. This meant that the kernel never used the 112MHz clock because it was below the ondemand minimum. No-frills CPU can confirm this.
5) arm6k support enabled. Not sure if it makes a difference but the kernel hasn't complained.
6) Conservative and Powersave governor enabled.
7) CONFIG_INPUT_TABLET disabled, nothing was enabled in there anyway and ours uses TOUCHSCREEN.
8) CONFIG_USB_ANDROID_RNDIS_WCEIS enabled, supposedly makes Windows think it's dealing with a NDIS ICS device.
9) Enabled ext4 and disabled yaffs2. Ted T'so backported fixes for ext4 for .27 release. This contains all the patches available on his ext4 git for the 2.6.27 kernel, but still should be considered EXPERIMENTAL.
GPL availability notice:
kernel source as available from http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commits/htc-msm-2.6.27
compcache module+patch from http://code.google.com/p/compcache/downloads/detail?name=compcache-0.5.4.tar.gz
.config used to compile available from within /proc/config.gz
Minor patches to the kernel source can be made against the git tree upon request. Please PM me if you are in need of that.
-- Starfox
Hmm haret freezes with your kernel on my rhod100_de.
(pm.sleep_mode=1 is deleted in startup.txt / no difference with pm.sleep_mode=1 not deleted)
Put sleep_mode back, and if it still doesn't boot, it's possible that the axi bus is too high. I'm looking to make it a kernel parameter in the next compile.
-- Starfox
So far so good.
Couple of things - first, it seems you didn't strip the modules...? There's no way they should be 7+mb .
Second, of all the things you've put in this kernel, one really stood out to me:
Starfox said:
proc_comm_wince: Fix long-standing issue with msm_proc_comm_wince_pending_ints & DEX_INT_VBUS check which clobbered pending_int. You should no longer have a SoD during transition changes to/from suspending while inserting/removing the USB cable.
Click to expand...
Click to collapse
If that's true ^^ (and works) why not submit a patch to mainline? Or is this your testbed for patch submission?
Good work, I'll see what I can make blow up. Only just booted... doesn't seem faster, but it's still settling methinks.
Please use the posted kernel/modules combo from the OP. I support 2 most recent revisions.
-- Starfox
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
anish88 said:
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
Click to expand...
Click to collapse
What device, build?
Rhod400, frx07
maybe a sample of the startup.txt would be appreciated too
also where am i suppossed to put msmsdcc_fmax=48000000 maybe im putting it in the wrong spot?
Running 8/6 here on rhod400. It seems just a tad bit faster/smoother.
anish88 said:
Rhod400, frx07
maybe a sample of the startup.txt would be appreciated too
also where am i suppossed to put msmsdcc_fmax=48000000 maybe im putting it in the wrong spot?
Click to expand...
Click to collapse
Did you just assume where the msmsdcc command goes? lol.
It goes in the "cmdline" between the quotes - where pm.sleep_mode is, etc. Make sure there's at least one space between each entry.
I'd imagine that's your issue, as I have the same phone/build and it works great for me.
arrrghhh said:
Did you just assume where the msmsdcc command goes? lol.
It goes in the "cmdline" between the quotes - where pm.sleep_mode is, etc. Make sure there's at least one space between each entry.
I'd imagine that's your issue, as I have the same phone/build and it works great for me.
Click to expand...
Click to collapse
odd, still no dice for me? what does your startup look like in general?
anish88 said:
odd, still no dice for me? what does your startup look like in general?
Click to expand...
Click to collapse
Did you rename the kernel? Have you updated the kernel before...?
My startup isn't anything special, just FRX07 with some additions for me (rel_path, OC, msmsdcc, no_partitions...)
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "msmsdcc_fmax=48000000 acpuclock.oc_freq_khz=714000 lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 rel_path=Androids/Stock07 no_partitions"
boot
i didnt have set initrd_offset 0x00a00000. i changed it, booting as we speak.
anish88 said:
i didnt have set initrd_offset 0x00a00000. i changed it, booting as we speak.
Click to expand...
Click to collapse
Shouldn't need it for .27... I forgot to mention that one tho, good catch. That is for .35/.39/3.0... .27 should work without it (and you'll need a new version of HaRET to use .35/.39/3.0 with that initrd_offset...)
anish88 said:
i tried running this. it gets stuck at the HaRET: Booting Linux Dialogue in WinMo. am i suppossed to make any changes to startup.txt because i tried adding msmsdcc_fmax=48000000 to startup.txt and am getting the same response. is there anything I am suppossed to be doing?
Click to expand...
Click to collapse
STOP.
If you are not getting past the boot scroll, then your phone cannot take the changes I made.
Again, let me make this clear. I do not guarantee that your phone will work with this kernel. I also can guarantee you that no mount of fiddling with startup.txt will change the fact that your phone will not boot.
You can try the updated zImage several post past the OP which should allow you to boot. Do not go blindly changing stuff in startup.txt. If you do not know what it does, ASK first.
-- Starfox
Starfox said:
STOP.
If you are not getting past the boot scroll, then your phone cannot take the changes I made.
Click to expand...
Click to collapse
Welcome to the joys of providing patches to the public...
The new zImage doesn't work for me either.
So my phone can't handle your kernel
Perhaps the AMSS firmware or the arm6k?
No Joy with Rhod500
Just tried this on my Rhod500 and I get a couple of Vibs from phone when Haret is launched, but the screen won't even re-paint... Just thought I would let everyone know...
Thanks...
If you need to know the AMSS version, it is shown during the HTC splash screen as [bunch of letters]-6125 or something very similar. From what I see the GSM users are having most of the issues, so it probaby is AMSS related.
-- Starfox
mgross029 said:
Just tried this on my Rhod500 and I get a couple of Vibs from phone when Haret is launched, but the screen won't even re-paint... Just thought I would let everyone know...
Thanks...
Click to expand...
Click to collapse
Ditto to this on a CDMA Rhod400 also. Vibrates on launching Haret, but does not go any further.
This kernel is based upon the current git tree for 2.6.27 with minor tweaks included, such as ext4. This is suitable for all devices and should work as well as the autobuild. Please note this isn't an autobuild, so there might be a slight delay between a commit and an update to this thread. Also I do not intend to deviate much from the autobuild other than the changes mentioned below, so if you really need a feature, please include a compelling reason why it should be done.
You will need a new haret.exe as well as an additional line in startup.txt to boot this kernel. Instructions for that can be found at http://forum.xda-developers.com/showpost.php?p=14519408&postcount=1.
Commit 1348 (8/20): http://db.tt/UnLHCuR
Older version: Commit 1346 (8/16): http://db.tt/RhUlSDd
Changes:
Support for ext4 (You must use a rootfs dated 8/16 or later, and have the option ext4dev in your startup.txt cmdline)
Deadline I/O scheduler as default
Sleepmode 1 set by default (No longer needs pm.sleepmode=1 in your startup.txt cmdline)
Ondemand CPU governor minfreq lowered to 112MHz
Powersave and Conservative CPU governor added
Netfilter Redirect added as module
RNDIS set as default for tethering
Swap notifier patch for compcache included and enabled
Most of these changes are in .config, and can be verified by looking at /proc/config.gz in your running kernel. The swap notifier patch allows compcache to skip certain operations, which should improve performance if you do use ramzswap. Ext4 is still considered experimental in the .27 tree, but has been updated with Ted T'so's backport patches in his ext4 git.
Please again note the following on ext4 support:
1) You must use a rootfs dated 8/16 or later for the proper support
2) You must use my kernel, as it is the only one with the required support compiled.
3) You must have the cmdline option "ext4dev" inside your startup.txt. Otherwise it will still continue on using ext2 data.img.
4) Using ext4 will create a brand new file called data.ext4. This is intentional, as I did not want to have the same file (data.img) with different format to confuse the matter further. This also means that none of your existing app/setting will be preserved. Be sure to back up your data & app with something like Titanium Backup, and have at least 500MB free on your SD card so that the system can create a new store.
GPL availability notice:
kernel source as available from http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commits/htc-msm-2.6.27
compcache module+patch from http://code.google.com/p/compcache/downloads/detail?name=compcache-0.5.4.tar.gz
ti wlan git clone'ed from git://android.git.kernel.org/platform/system/wlan/ti.git
.config used to compile available from within /proc/config.gz
-- Starfox
Just loaded this one up and found something very odd... my ts-calibration was all off... Booted back into WM and deleted and re-calibrated... Still seeing the same issue...
Not sure why a module would do that but just thought I would let you know...
I went back to your 8/15 and 8/16 test kernel and could not even use the slide lock... This one is really wierd... Going to delete my data.ext4 and see if I can resolve that way...
Thanks for all the hard work you've been putting in to come up with these kernels...
Edit: Just saw the update on this page... Thanks...
Sorry about having to pull the file, I've recompiled the whole thing using gcc-4.4 and the touchscreen seems normal again. For those who may have downloaded the first file, please download it again, even if you don't have issues. The correct filesize for the new version is 2460710 bytes.
For the technical-mined out there, the first attempt was compiled using arm-linux-gnueabi-gcc 4.5.2-8 under Ubuntu 11.04 amd64. Certain versions of compiler may introduce bugs where it might over-optimize certain things, and to complicate things, we are trying to make it run under a different architecture. That can introduce unforseen bugs due to endianess, data size differences, etc. that would otherwise not happen. Cross-compiling is a voodoo art at best, and the kernel source tree expands to ~900MB including all the intermediate files produced during the build process.
If you have a Ubuntu 11.04 machine and would like to help me determine if it was actually a cross-compile bug, send me a PM and I'll try to walk you through setting up the build environment and compiling the kernel. Since the bug popped up with the touchscreen, it will be relatively easy to confirm whether the compiler was responsible.
-- Starfox
Hmm - I must be missing something.
It says:
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/loop0 is mounted.
EXT3-fs (loop0): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (loop0): error: couldn't mount because of unsupported optional features (240)
MILFS: Can't find milfs on dev loop0
mount: mounting /dev/block/loop0 on /dev failed: Invalid argument
Failed
Failed to mount /data (/sdcard/)
Anything I'm missing - I've triple checked all the instructions.
* RHOD100 UK
* Running on SD Card with new Haret and amended Startup.txt
What exactly is in your startup.txt cmdline, and which rootfs are you using?
-- Starfox
Right. So, I went back to the Commit 1346 (8/16) and that went away.
Now I'm getting "ignored duplicate definition of service" and the "request_suspend_state" loops... it might be due to the new Class 10 SD that I'm using for this testing - Going to find an old Class 2 and try again.
FYI - the startup.txt command line is
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave pm.sleep_mode=1 hw3d.force=1 acpuclock.oc_freq_khz=716800 ext4dev physkeyboard=rhod100_uk-b4HOME"
rootfs is rootfs-20110816-7e04198.zip
StarFox,
Loading this kernel now to test it out... I've been running your 8/16 test kernel for over two days with only the wifi being a problem. The LEDs have working great!
I'll let you know how this kernel goes... Hopefully better than the Cross-Compiled on I grabbed... LOL
StarFox,
Ran with this kernel through yesterday and into this morning... It all seems stable... However, I did notice longer than normal GPS signal acquisition times. When I was running the 1340 kernel I noticed this too. When I went to your Test 8/16 kernel I was getting a lock much quicker. Going to go back to the 8/16 test kernel to verify this.
Thanks...
bughunt said:
Now I'm getting "ignored duplicate definition of service" and the "request_suspend_state" loops... it might be due to the new Class 10 SD that I'm using for this testing - Going to find an old Class 2 and try again.
FYI - the startup.txt command line is
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave pm.sleep_mode=1 hw3d.force=1 acpuclock.oc_freq_khz=716800 ext4dev physkeyboard=rhod100_uk-b4HOME"
Click to expand...
Click to collapse
Okay, first, you're running a class 10 card with 1-bit and 14Mhz freq. Take these ones out: force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave hw3d.force=1
You can take this one out if running my kernel:
pm.sleep_mode=1
How old is this startup.txt? These are values that have not been used for a while.
-- Starfox
Update to build 1348, the new liblights will require you to have it bindmounted.
I'd appreciate if people would post different machines this has successfully worked on. I know it works on Rhodium, looking for Diamond/Raphael/users. Thanks.
-- Starfox
Starfox said:
Okay, first, you're running a class 10 card with 1-bit and 14Mhz freq. Take these ones out: force_cdma=0 msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave hw3d.force=1
You can take this one out if running my kernel:
pm.sleep_mode=1
How old is this startup.txt? These are values that have not been used for a while.
-- Starfox
Click to expand...
Click to collapse
Right - that's fixed. It now boots up and seems a bit more snappy than before.
do you have to format a partition off of your sd card to ext4 before using this?
AkumaX said:
do you have to format a partition off of your sd card to ext4 before using this?
Click to expand...
Click to collapse
Nope, it will create a data.ext4 file that is the data.img, but in ext4 instead of 2.
My Rhodium is rebooting when I turn on Wifi. Radio is 3.44.25.27 running GBX0A (11.3.2011).
bughunt said:
My Rhodium is rebooting when I turn on Wifi. Radio is 3.44.25.27 running GBX0A (11.3.2011).
Click to expand...
Click to collapse
Rebooting to WinMo?
Have you tried on FRX07?
Which RHOD? I'd guess 100 from your carrier.
Edit - logs would be helpful, if you have any. On a reboot to WinMo, /data/system/dropbox logs are the only option (other than ramconsole)
arrrghhh said:
Nope, it will create a data.ext4 file that is the data.img, but in ext4 instead of 2.
Click to expand...
Click to collapse
cool, i'll try out this testing when i figure out where all my microsd cards went...
Move Panel to PLL2 and add 1056MHz Option. If you don´t know how? then ask me
EDIT: What about editing Neopeeks CWM recovery to change Data.ext4 to a real ext4 partition?
BlackRainX said:
Move Panel to PLL2 and add 1056MHz Option. If you don´t know how? then ask me
EDIT: What about editing Neopeeks CWM recovery to change Data.ext4 to a real ext4 partition?
Click to expand...
Click to collapse
You'll have to explain the panel one to me, but not sure what the 1056MHz option would do for this kernel.
Also, this is xdandroid kernel, not CWM. And data.ext4 is a real ext4 partition. It's only ext4dev because .27 was before ext4 was "official".
-- Starfox
BlackRainX said:
Move Panel to PLL2 and add 1056MHz Option. If you don´t know how? then ask me
EDIT: What about editing Neopeeks CWM recovery to change Data.ext4 to a real ext4 partition?
Click to expand...
Click to collapse
Blackra1n,to have a partition in cwm as ext4 you just need to change a few things in rootfs
Starfox said:
You'll have to explain the panel one to me, but not sure what the 1056MHz option would do for this kernel.
Also, this is xdandroid kernel, not CWM. And data.ext4 is a real ext4 partition. It's only ext4dev because .27 was before ext4 was "official".
-- Starfox
Click to expand...
Click to collapse
Panel if run from pll1 gets weird with gpu overclocked,so Blackra1n moved the panel to pll2,from what user reported the panel works well now and there's more speed,if you need more infos,pm me or blackra1n(I'm on #xdandroid in the afternoons)
More infos here
Please describe how panel gets "weird", because this is the first time I've heard of it. Rhodium by default runs at 960mhz pll from what I've seen. And there seems to be no way to conclusively test what freq a pll runs at - from a quick glance of the thread mentioned I saw some "tests" of factors other than a simple freq change - ie, I saw mention of JIT being enabled for the "overclocked" one, which does not help.
-- Starfox