yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] LouZiffer:
Nope. Just got a booting and fully functional kernel this morning after several hours of trying the more conventional methods. I haven't finished running it through its paces yet but everything seems to be working fine (including new wifi/wimax modules).

Oh... and that reminds me: Like many other recent HTC phones, the wimax/wifi modules are not in initrd. You can pack them in there if you have room, but be sure to back up/remove the original ones in /system/lib/modules. (Either way, you'll need to replace those.)

EDIT: Just saw your edit. Yes, HTC's default kingdom_defconfig has the wifi and wimax modules compiled separately. Everything else is integrated.
[Android Software/Hacking General [Developers Only]] HampTheToker:
A custom kernel?!?!?!?

Could you tell us what tweaks will be included in the final release? I'm so looking forward to flashing the Designs first custom kernel.
[Android Software/Hacking General [Developers Only]] ss2man44:
Don't get too excited. I have zero experience with ARM/Android development and I have a ways to go before I feel comfortable "releasing" anything. That doesn't meant I can't help someone else in the process, though.
[Android Software/Hacking General [Developers Only]] HampTheToker:
Lol was talking to Lou.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
If someone would have asked about the kernel, I could have told you the info instead of having to figure it out on your own. As I built kernels the day or day after source was dropped.

That flag how ever I never had to use, May be your toolchain as I use the aosp stuff and built via all different versions with out issue.

Just do the following should get you going building one.

1) Download the source code from htc dev

2) Extract the source code to the directory you please

3) Cd the directory containing source code

4) Then in terminal run the following commands

make kingdom_defconfig

enter

Then

make -j5 ARCH=arm CROSS_COMPILE=/home/username/android/4.4.4/bin/arm-none-eabi-

Changing the after = to where your toolchain is and the version you want to use. As I said I compiled with aosp's I believe it is 4.4.3 or 4.3.0 something like that. I will have to look when I get time to confirm it.

You will then get a zimage, wifi module and wimax module in the places listened in terminal. Should take about 10mins or less to build I would say. Then you should only need the zimage and the stock wifi one work, if I recall. How ever if you get a error then you need the wifi module with the permissions set right. Wimax I can't comment on as I don't have a need for it.

Then anykernel will not work correctly as far as my testing went. How ever skuddy on my team verified this worked http://xdaforums.com/showpost.php?p=18416359&postcount=2 with the stock kernel I built.

Then if anyone wants the stock kernel I built like 3 nights ago I can give it to you but won't have the wimax stuff, as I didn't pack it into the zip. As for overclocking that was what I started on and haven't finished. Was shooting for 1.9ghz how ever.

O and since it is quicker to copy and paste the commands. The commands above are thanks to adrynalyne from the thunderbolt. Though the one was changed to point to the right config.

Edit: I also might want to mention I have been setting on my own roms, just havn't had time to patch some files. Then really even work on it to be honest.

Edit: 2 Take that back if I am getting what skuddy is telling me anykernel will work, though is bit weird how it is done. There will be several option in my tool along with kernel flashing when I finish it up. Then I can confirm the different ways.
[Android Software/Hacking General [Developers Only]] LouZiffer:
Thanks, 2Fast. The more eyes on this the better! I like figuring these things out on my own, and it's great to see when folks can reach the same place using different methods.

This GitHub Repository contains all of the source and tools I used outside of the base development environment.

The kernel source is just what comes from HTC. The external directory contains the codesourcery toolchain I used as well as the abootimg utility. The build.sh script will prep the build environment and build a stock kernel using the toolchain contained in external.

Unless you use the exact kernel version string that HTC uses, you will need to replace the kernel modules for wimax and wifi. I tend to append my own version string to keep things separate and test what has been compiled. Some folks choose not to, and that's fine.

The extra aflag I used is due to using the codesourcery toolchain. It requires that specific support be turned on for the dedicated floating point unit in our processor.

EDIT: By the way, (looking at the util you're using) I've worked some with joeykrim in the past. He's a good guy and the SDX folks deserve plenty of respect. :)
[Android Software/Hacking General [Developers Only]] ss2man44:
I assumed you were talking to me because Lou has only implied that he is playing around with the source, not developing a custom kernel.

EDIT: As for ways to flash the kernel, can't I test with "fastboot boot [image]" for now?
[Android Software/Hacking General [Developers Only]] LouZiffer:
My main interest is personal, and to help the community along by sharing whatever is learned along the way. In doing that I'll happily share whatever kernel I'm running. Right now I'm at recompiled stock until comfortable that the result is stable.

Overall the Kingdom platform already has plenty going for it even at stock. I expected HTC to recycle a lot from the EVO Shift, but have been pleasantly surprised. This platform uses the EXT4 filesystem natively, and their kernel configuration is pretty darn good as far as a safe, fast configuration. They've even done a bit of tweaking to take advantage of new processor features.

I'm using fastboot boot [image] for testing before doing an actual flash, yeah. If it doesn't boot it'll still need a battery pull, but the original boot is still there.
[Android Software/Hacking General [Developers Only]] ss2man44:
How hard do you guys think it would be to merge existing changes from the CyanogenMod 7x30 repo into the Kingdom-specific kernel source?
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Not catching on what you are saying? The root tool was just a add on to my s-off tool for the merge. Along with flashing cwm and several other things. It originally started out as commands and moved to scripts. The tool I have been working on for two days, has the same features as some others. How ever is everything I have done combined, so I can update it all at once. So really I have no clue as to what you are refering to :confused:

O should have answered this first as for that one toolchain, I can't think of the name or where it is from. I never once have had good luck with it period. So that probably explains it.

Then for people that want to play here is 200 to 150mv undervolt kernel. http://dl.dropbox.com/u/24065431/StockClockUndervolt.zip Uses the same voltages pretty much as my merge kernel so it should be stable. Confirmed by skuddy from my team to be working. You are on your own to flash it though with the supplied info. As I really don't have time to put a guide up.

If you need the wimax modules let me know.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
I don't mean to double post, how ever I think it is cleaner to answer this question. Where I am not sure on the repo but we use the same acpu table as the 7x30's. If you are looking for overclocking it will be up later.
[Android Software/Hacking General [Developers Only]] ss2man44:
I used "fastboot boot zImage" and it's frozen at the HTC boot splash. Is there any way to debug this? Or was I supposed to give it a boot.img?

When I try to unpack the stock boot.img that a CWM backup gave me, it tells me:

$ abootimg -x boot.img
boot.img: no Android Magic Value
boot.img: not a valid Android Boot Image.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
I will be honest with you, When I made the oc kernels a few days ago. Since I am use to having s-off I kept getting issues no matter what I tried. I haven't even tried since then but built and sent them to skuddy to mess with. Mainly due to he seems to never be busy.

Wish I could help more than that, but I told him to post in here to help you guys out. If he doesn't I will see if I can mess with it tonight.
[Android Software/Hacking General [Developers Only]] skuddy:
your doing it wrong.....

take the recovery.img out of 2fasts ph44img for cwm. put it in root of C:\

then in cmd cd to your android sdk folder

for instance mine would be c:\androidsdk\tools <--- this is where my fastboot lives.

then type fastboot boot c:\recovery.img

from there it will boot into cwm, which then magically allows you to flash a custom kernel zip
[Android Software/Hacking General [Developers Only]] ss2man44:
I'm talking about flashing my own compiled kernel, and I managed to do so by creating my own boot.img turns out the "stock" one I had was corrupt.
[Android Software/Hacking General [Developers Only]] LouZiffer:
Edit the img file and strip all of the characters before ANDROID!. Then save it. It'll unpack fine afterward (and will still work on the phone).

I was saying I'm glad to see some of joeykrim's stuff in use (the flashboot tool skuddy was trying). Nothing else meant by that.

....

As far as integrating CM kernel code into HTC's, I don't think it'd be worth it to try and merge everything beyond tweaking. All of the "kernel debug" statements you find sprinkled throughout are parts of CarrierIQ. There's lots of effort put in already into removing CIQ from devices, but I still think it's better to take the CM code and bring anything necessary to support the Kingdom platform forward into it instead.
[Android Software/Hacking General [Developers Only]] skuddy:
i retract my statement. you said it works. my bad
[Android Software/Hacking General [Developers Only]] 2fast4u88:
O the link I posted, I didn't even look at it but was sharing it. As for the app I guess you are talking about. Skuddy never used it and neither have I. How ever now I get it.

As for Ciq it is in everything. Though last I looked the cm kernel is old, where you will have to merge stuff into it any way. Personally I wouldn't base off it.
[Android Software/Hacking General [Developers Only]] ss2man44:
Aaaand success. Using code from CM's 7x30 kernel, I've managed to overclock the device to 1.4GHz.
[Android Software/Hacking General [Developers Only]] skuddy:
push it farther. 2fast squeezed 1.8ghz out of the merge.
[Android Software/Hacking General [Developers Only]] ss2man44:
Oh believe me, I plan to. I just wanted to see if I could do it. This is the first time I've ever touched the source of anything Android or even kernel (module) related.
[Android Software/Hacking General [Developers Only]] LouZiffer:
Nice proof of concept! If you want something to aim for or beyond: As far as I know the stable limit for Snapdragon so far has been 1.9GHz, which has been seen on the EVO Shift. That speed was stable for some, but not all. 1.8GHz, which 2Fast hit, seemed to be the highest common denominator.

It'd be really nice to see ours hit a new high mark. (Maybe wishful thinking.)
[Android Software/Hacking General [Developers Only]] ss2man44:
I've loaded the wifi and wimax modules but it refuses to pick up any cell signal now. There doesn't seem to be an error but bars no longer appear.

EDIT: Here's a screenshot of both the overclock and the lack of bars.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
The merge will run above 1.8 ghz, as mine does 1.8 fine with only a slight voltage boost. Just never pushed it higher. I ported the merge oc to the design and skuddy says it shows the clocks and works. How ever I can't confirm as the junk doesn't want to take. Keeps booting on the stock kernel, about to slap it into the boot.img and flash it with my rom.

How ever if someone wants to play with it I can upload it.

Edit: Do you have the bottom of the phone of by chance in the screenshot? Probably stupid but just thinking as it connects the antenna I believe.
[Android Software/Hacking General [Developers Only]] ss2man44:
D'oh! Now I feel really stupid. I had the back off to pull the battery when my first fastboot attempt failed. Thanks for that bit of info.

I'm just curious to see what you changed to OC. Can you upload your acpuclock-7x30.c?
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Um I would but something isn't right, oc and bench sucks. So trying to figure it out while figuring out why I can't seem to get a kernel to stick. If/when I get it fully working I will post it/pm it. O that is funny by the way :) How ever don't feel bad I did the same thing awhile back. Cept I kept trying to figure it out and realized the bottom was off.
[Android Software/Hacking General [Developers Only]] ss2man44:
Well, if you want, I can post a diff of the changes I made if it would help you.

EDIT: I will anyway. It's rather brief. The things beyond modifying the clock tables, I saw in the CM repo and pretty much just copied and pasted.

$ diff acpuclock-7x30.c acpuclock-7x30_old.c
99,100c99
< { 4, 1401600 },
< { 5, CPUFREQ_TABLE_END },
---
> { 4, CPUFREQ_TABLE_END },
123d121
< { 1401600, PLL_2, 3, 0, 192000000, 1250, VDD_RAW(1250) },
215,218d212
<
< /* Program PLL2 L val for overclocked speeds. */
< if(s->src == PLL_2) {
< writel(s->acpu_clk_khz/19200, PLL2_L_VAL_ADDR);
< }
529,532c523,524
< // Force the stock clock by default, otherwise it will not boot.
< speed = &acpu_freq_tbl[8];
< cpu_freq = &freq_table[3];
< //speed = &acpu_freq_tbl[ARRAY_SIZE(acpu_freq_tbl)-2];
< //cpu_freq = &freq_table[ARRAY_SIZE(freq_table)-2];
---
> speed = &acpu_freq_tbl[ARRAY_SIZE(acpu_freq_tbl)-2];
> cpu_freq = &freq_table[ARRAY_SIZE(freq_table)-2];

EDIT2: This bug is also present on the Design/Hero S when using anything that replaces the lockscreen. Any ideas on how to fix it?
[Android Software/Hacking General [Developers Only]] 2fast4u88:
What are you by perhaps benching at 1.4ghz in quad?
[Android Software/Hacking General [Developers Only]] ss2man44:
991 @ 1.2GHz

1147 @ 1.4GHz
[Android Software/Hacking General [Developers Only]] ss2man44:
But Quad scores include the GPU as well. Maybe the source HTC gives us has a lower GPU clock by default?

EDIT: If I remove this from acpuclk_set_src(), the benches become acceptable again:

if(s->src == PLL_2) {
writel(s->acpu_clk_khz/19200, PLL2_L_VAL_ADDR);
}

What does that do, anyway?

EDIT2: got a score of 1973 @ 1.4GHz

EDIT3: I see, that code modifies the multiplier of PLL2 to reach the desired core clock. But why does setting that multiplier reduce performance so much? In fact, I just got 2036 @ 1.2GHz, so I know the overclock doesn't do anything at all without changing the multiplier.

And now I realize that change near the bottom simply forces it to keep 806.4MHz as the base clock when determining the device's default PLL2 L value.

EDIT4: I think I see the problem. One second...

EDIT5 (world record?): Okay! It looks like the crystal in the PLL2 of 8x55 is actually running at half the frequency, so the above code should be changed to this:

if(s->src == PLL_2) {
writel((s->acpu_clk_khz/19200)*2, PLL2_L_VAL_ADDR);
}

I know this because the default value associated with this 1.2Ghz device is defined as "#define PLL2_1200_MHZ	125" at the top instead of ~40-70 like the rest. I've already made the change and flashed and benchmarks look good again.

1580 @ 1.2GHz

2082 @ 1.4GHz

In fact, it might even be safe to change it to

if(s->src == PLL_2) {
writel(s->acpu_clk_khz/9600, PLL2_L_VAL_ADDR);
}

which would lead to even more resolution in the frequency steps (multiples of 9600).

Here's my current clock.

And here's the resulting Quad score. ;)

Now I've used "flashboot flash boot boot.img" and it boots perfectly fine, I think I'll call it a night. Thanks for all the help, guys.

EDIT: Came back to say that 1.9GHz at 1.5v is a teeny bit unstable with random occasional reboots. I think the voltage could use some tweaking.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Nice :D I had to go to bed due to classes. How ever I should have mentioned to look at the thunderbolt overclock, as it should be the same process as the chipset is the same. Or is listed as being the same any way, I haven't really looked into it.

Edit: Nvm the thunderbolt would have used the 1024 pll2.
[Android Software/Hacking General [Developers Only]] ss2man44:
The next step would be to tweak the governors, right? Ondemand is a bit finicky. Also, I'd still like to know how EVO 3D kernel devs fixed that touchscreen bug.
[Android Software/Hacking General [Developers Only]] ss2man44:
2fast, is it okay if I use your clock tables in my public github repo? I'll give credit in both the commit and in a comment.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Fine with me, I've been busy with classes so haven't had time to even work on the kernel since the other night.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Can we have the ruu.exe? As I can get the rom.zip myself and upload it. As the above zip file is corrupted.
[Android Software/Hacking General [Developers Only]] amoser871:
good work guys if yall have anything you need tested i am always willing to help not much of a devolper but a great test dumby.
[Android Software/Hacking General [Developers Only]] Skitzi:
I have been able to flash that ph44img.zip via bootloader successfully a number of times.

You need to re-lock the bootloader for it to work. If you try and flash the indiviual img fles with an unlocked bootloader it will let you flash boot and recovery, but the system.img fails with an error about size. I assume thats why flashing the eniter zip via fastboot fails.

But ya, relock and it works, have done that a number of times.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Try to edit it, for example the .txt and the zip is corrupt.

Edit: Mine isn't relocked, how ever it loads the zip and is all via bootloader. Tried 3 different times and had skuddy confirm the zip is corrupt.
[Android Software/Hacking General [Developers Only]] 2fast4u88:
Will someone flash this and let me know how it works? http://dl.dropbox.com/u/24065431/Merge-2fast4u88-stock7.zip Oc is still on the flakey side, or at least still acts like it to me. I did have the cpu clocks limited on boot for 1.2ghz how ever I took it off on this build to test something. Where it will boot at 1.8ghz. How ever I would recommend for the best battery life to set it to 1.4ghz as it uses stock volts for now.

Also ignore the file name as I just flopped it into the merge one. How ever the partition mount points are correct. I also did not put the wimax stuff in it though the stock ones should work fine.

As of right now the kernel has the following done. Uv from 1.2ghz down, Oc to 1.8ghz, Turned Powersave and Conservative on, Read ahead fixes, Lowered emmc voltage and lowered wifi voltage. As for governors I will try to add them later today/tomorrow.

Edit: There is also scheduler tweaks done. You can also flash it as is if you fastboot cwm. Otherwise you can install it one of the other ways provided. Also if you try to do it via fastboot cwm, make sure you are on a rom with a edited boot.img or use a edited one. As in my task to figure out what was going on with the kernel not taking was using the stock boot.img.
[Android Software/Hacking General [Developers Only]] Skitzi:
don't know what to tell you. I can flash it and edit it. I can also toss it in the kitchen and extract boot and system.img.

Here is the text for the android-info.txt file:

"modelid: PH4410000

cidnum: UTSI_001

mainver: 1.26.573.7

hbootpreupdate:12

DelCache:1

"

I can post the copy I have
[Android Software/Hacking General [Developers Only]] skuddy:
would you be so kind, i would love a working copy.
[Android Software/Hacking General [Developers Only]] Mangani001:
8 hrs and all is well... no bugs.. running it at 1.8ghz on the skitzipak beta-1 rom...
[Android Software/Hacking General [Developers Only]] 2fast4u88:
I never said the system image is corrupt, as I can unpack it as well. Here is the deal I have downloaded it 6 times where neither has been fine. Put the zip on the card renamed. Boot to h-boot and it starts to load the image, once bar gets to full and back to h-boot it goes. At first I though it may be due to the ota changing the misc image. Where I then tried to edit the .txt when I found out it was corrupt. According to when I try to save the change to the zip, the h-boot is corrupted.

Though if you have the same one downloaded and it some how isn't corrupted. If you will upload it so I can see if it is as well. That would be great.

Nice, for you is benchmarks still on the low side by chance? For example myself and skuddy get increases till 1.5-1.6 ghz. Then after that it falls flat off in quadrant (Yes I know not the best benchmark, how ever not what I am checking), though linpacks scores actually increase for every clock. Then due to the voltage needed to run 1.8 or higher I doubt I put those clocks in unless people want them. Though curious how is your battery life on 1.8?
[Android Software/Hacking General [Developers Only]] OctoberNexus:
ICS Roms would be nice. Just sayin

sent from my HTC Kingdom
[Android Software/Hacking General [Developers Only]] Skitzi:
Here you go: PH44IMG.zip - 376.6 MB

I know I have said it before but tossing it out again for people have missed it.

You have to reloack your bootloader for this file to flash correctly via the bootloader. If you try with an unlocked bootloader it will scan the zip but then not actually flash it. This is due to the system.img. To test you can also try flashing the individual .img files via fast boot. When you try and flash the system.img while your bootloader is loecked it gives you an error about the image being too large. Lock your bootloader and try again and it will work. I spent a week going round and round till I relocked and everything worked.

unlocking is the same process as before i you relock your bootloader (there was one time it would not let me use the same unlock.bin so I had to go generate a new one).

Hope this helps
[Android Software/Hacking General [Developers Only]] qdcti:
Skitzi，I cant open vaelek.com/index.php/topic/2483-skitzipak-for-heros-on-us-celular/#entry39387, it say:[#10340] You do not have permission to view this topic.

why? I want use the rom,thanks
[Android Software/Hacking General [Developers Only]] Mangani001:
3901 on antutu up from 2880.... My sdcard sucks... 70 on the linpack and no noticeable drop off in battery life at 1804Mhz....3600 @ 1.6...
[Android Software/Hacking General [Developers Only]] amoser871:
so i flashed this just fine but its just the stock rom i mean yea it got me backm to stock but know i have to reroot boo lol oh well
[Android Software/Hacking General [Developers Only]] Skitzi:
Yep, those are the stock images for the Hero S.

---------- Post added at 08:56 PM ---------- Previous post was at 08:52 PM ----------

Yaaaa, The post is hidden for the moment. Long story short is I posted the wrong zip, and deleted the wrong folder on my computer. I deleted my good base,built from the bad base, and posted the bad build. My bad and sorry all.

I have it rebuilt and working better than ever, just working on adding a few more features before I re-release.
[Android Software/Hacking General [Developers Only]] amoser871:
skitzi you rock man i cant wait to try the rom out good luck and hope to see it up soon
[Android Software/Hacking General [Developers Only]] nfinitefx45:
OTA from the Sprint Design 1.19.651.1

Hello everyone I am a dev from the Evo Shift and have ported the Design to the Shift but would like if someone could post either the OTA 1.19.651.1 zip or a system dump from a phone updated to 1.19.651.1.

Any help on this would be greatly appreciated. you can hit me up by pm or just post it and let me know the link.

Thanks Erik