yashsingh1/xdaforums huggingface dataset:
[Desire HD Q&A, Help & Troubleshooting] bengylow:
Dear All DESIRE HD user,

Did anyone of you manage to ROOT your DHD ? z4root doesn't work with DHD !!! ....too bad....please let me know.
[Desire HD Q&A, Help & Troubleshooting] CitizenLee:
We're pretty much all rooted here ;)

Have a look at the pinned threads in the development section for guides. You need to use Visionary, not z4root for DHD.
[Desire HD Q&A, Help & Troubleshooting] ghostofcain:
Dear bengylow , have you considered reading the development section?
[Desire HD Q&A, Help & Troubleshooting] bengylow:
I'm having 2.37.767.2. That's why ??

I've use gingerbreak, visionary, superoneclick, android ace, adb.....none working. ....
[Desire HD Q&A, Help & Troubleshooting] ProreX:
Try to take a look at this thread. http://xdaforums.com/showthread.php?t=1152233

Hope it helps.

When I was rooting i did stupid act, I had phone on 1.72 version, and before rooting i decided to use official upgrade to 2.36. That act costed me a lot of time and energy to downgrade but I finally managed it. I also had to use GOLDCARD (and I borrowed SD card from my daughters phone, lucky me to have a daughter who was willing to lend me her card) ;) Long story short, just follow instructions, but before, be sure to understand every step you need to take. It would be a problem that you reach 2/3 of a way and than you find out you don't understand step or two, and your phone is turned on half way to rooting. :D Read instructions few times before start to do things.
[HD7 General] daaango:
So I recently updated the HTC App Notes via the Marketplace and now I can't open it. Whenever I try to, it goes to a black screen, then back to the home screen. I wrote down some pretty important notes in there and would love to either have them back or get the app to start working again without losing any data.

Any suggestions?
[HD7 General] Jim Coleman:
Turn your phone off, then back on again.

And a word of caution - it's generally a bad idea to use apps which store your data only on the phone. Apps like the pre-installed OneNote will sync your notes to the web, so you'll never lose them.
[HD7 General] daaango:
Yeah restarting it was one of the first things I tried, but no luck.

And yeah, I guess you're right I'll take a look at OneNote after I get my data from Notes lol

Anyways, any other suggestions?
[HD7 General] Jim Coleman:
You can try uninstalling the app and re-installing it, but you may well lose your data if you do so.
[HD7 General] daaango:
Losing the data is what I'm afraid of :/
[HD7 General] Jim Coleman:
Why did you start using an app that has no way of backing up?
[HD7 General] daaango:
Dunno, I guess it was pretty and it was an official htc app? Lol it was my first time using windows phone 7 and I guess I just used what I found first time around
[Nexus S Android Development] morfic:
Trinity Max is a Kernel for Nexus S running conservative core voltages at each OC level.

Trinity Vmax only differs in extended voltages at each OC level.

I recommend Max, Vmax is if you want to see if you can squeeze out just that last ounce of clock speed and are comfortable with the higher core coltages.

Perfectly fine to use setcpu including screen off profiles below 800MHz. Thanks to coolbho3k's patch that fixes the policies during suspend/sleep and restores the previous on resume.

This is for.Android 2.3.2.or below.

What you get:

Trinity-Max-CM7-1.1

Trinity-Max-Bionix-1.1

Trinity-Max-StockRom-1.1

Vmax:

Trinity-Vmax-CM7-1.2

Trinity-Vmax-cm7-v1.1

Trinity-Vmax-bionix-v1.1

Stock:

Kernel for Stock Roms

Kernel for cm7

Kernel for Bionix NS

Experimental UV Big Bore kernel available:

Trinity-UV-108BB-Experimental

------------------------------------------------------------------

BT Trouble? Not in this house!

method of assurance: (lost track who said it first, it's in this thread, thanks)

- switch wifi OFF, switch BT OFF

- update kernel

- FIRST: on reboot switch BT ON

- THEN switch WiFi ON
[Nexus S Android Development] RinTinTigger:
Can we get an Update.zip ?

and maybe for MoDaCo?

i know youve been waiting for these questions ^^
[Nexus S Android Development] morfic:
Yes, you can, later.

Copy/paste on modaco? i could. always forget that nice place for some reason.
[Nexus S Android Development] RinTinTigger:
Thanks for creating flash zip later.

And i ment a working kernel for the MoDaCo custom rom r3 ^^
[Nexus S Android Development] morfic:
What does it need in init.rc to work?

If it does nothing special, it would work anyways, and if it does special stuff, link me to the initrd they use and i can build one with that.

I Will push the modified source to github once i am done, then they can take care of that if i don't before then.
[Nexus S Android Development] DebauchedSloth:
Cool!

Any chance you could post your patches?
[Nexus S Android Development] k0mpresd:
here is boot.img. i put the .ko in /system/modules in the ramdisk folder and compiled but still error for wifi. im sure i did it wrong. anyways, its a bootable/flashable img. my phone boots off it. :)

fastboot boot oc.img
[Nexus S Android Development] unremarked:
Also contains the ext4 optimizations? :D /hope

I feel the need, the need for speed!

EDIT: And is this only for the stock kernel, or will it work on CM7?
[Nexus S Android Development] k0mpresd:
yes, has ext4 mod.
[Nexus S Android Development] RinTinTigger:
Not booting on MoDaCo r3 :/
[Nexus S Android Development] mortzz:
So basically just push the .ko and boot the zImage in fastboot?

What is the purpose of the line that's being added to the build.prop?
[Nexus S Android Development] morfic:
That's all it is.

You can run neocore without it and if you don't hit 65fps, it's still needed.

On the vibrant it still limits the results even if kernel is capable of more.

Why 68? It's what quadrant reports for refresh, and no need to go above that.
[Nexus S Android Development] morfic:
Put the module into system/modules/ inside the update.zip's skeleton

copying SYSTEM, I can modify it to do that if needed.

Now I wonder if mkbootimg actually likes me or not. I wasted so much time on mkbootimg in the beginning, I'm simply staying clear of it right now..

haha, now I get it, not a update.zip

you'd have to modify init.rc to copy it over, which I might add to reduce the number of steps needed

Btw, I'll add /data mount options next time, I tried them after I built this.

Quadrant advanced shows a nice difference obviously, I'll include it in the way shown on the ext4 thread.

Torn between tweaking this more and first flashing somb's alpha rom and trying this with it.
[Nexus S Android Development] mortzz:
Mine locks up whenever I run Neocore. I guess my phone isn't stable :(
[Nexus S Android Development] k0mpresd:
success!

here is bootable boot.img that will install correct bcm4329.ko and build.prop.

test:

fastboot boot oc_final.img

or flash:

fastboot flash boot oc_final.img

edit: whoops, typo.
[Nexus S Android Development] morfic:
Neocore was always my problem child with froyo kernel, I was overjoyed running multiple runs without issues.

This is only a first version, we can push voltages later. And make this available for more phones.
[Nexus S Android Development] morfic:
I said I'll push it to github when I'm done. :)

Right now I just need feedback to get a better idea about reliability.
[Nexus S Android Development] mortzz:
Yeah, it locks up in nenamark and playing 3D heavy games too.

Awesome, thanks! I'd be disappointed if my phone couldn't take a mild overclock.
[Nexus S Android Development] k0mpresd:
this should be a one-click install to install your zimage with correct files. :)

download, extract, run overclock.bat. only for windows. :rolleyes:
[Nexus S Android Development] ikon8:
This only for stock rom? CM7?
[Nexus S Android Development] ragiut1:
+1

10char
[Nexus S Android Development] 651stp:
maybe after 1.4 :DDDDDDDDDDDDD
[Nexus S Android Development] PeartFan40:
Unstable?

I've got trinity 1.3 on my NS and it's butter. Have you even flashed it? Or are you assuming it's unstable.
[Nexus S Android Development] unremarked:
@Morfic: Great work, mate. Absolutely flawless on 1.3ghz and I can't wait to try 1.4ghz. Once you've reached that pinnacle, I wonder if you wouldn't mind adding something to the kernel. I'm sure you're familiar with BLN, coming from the Vibrant forums. Folks would love to have that on their Nexus S, and as I understand it, the only thing that's keeping us from being able to use it is the lack of a supporting kernel. :) Hope you'll consider it when/if you can!

BLN link for infos: http://xdaforums.com/showthread.php?t=813389
[Nexus S Android Development] dylchow:
1.3 with ext4 on stock rom freezes at bootlogo

but 1.3 without 3ext4 on stock rom runs very smoothly

thanks morfic :)

EDIT: hmm phone rebooted when running avatar by gameloft for a while, not sure if its the app or the kernel cuz played dungeon defenders without a problem

also just wondering wut profile on set cpu for screen off, cuz had a lil problem with booting the phone back up again with 200/100 on demand...
[Nexus S Android Development] hkoutso:
That would be awesome! Its the only thing I miss from my Nexus One :)

As for morfic's kernel still rock-solid and stable! Been running it for the past 10-12 hours at full capacity (wifi,browsing,emails,youtube,angrybirds).

Battery use seems the same as in stock 2.3.1.

Morfic once again excellent work ;)

PS. Any news on the bluetooth fix ?
[Nexus S Android Development] risegeek:
I hope you guys may be able to shed a little insight for me, I'm pretty new to the Android scene, the Nexus S being my first phone with this great operating system. I have wiped data & flashed the Bionix NS1 ROM, after this I would like to get this kernel running, I have found limited information on this :confused: I reboot into clockwork & then flash the kernel? :confused: I've tried this and as soon as I unlock my phone it will suddenly freeze up and restart, I've tried to wipe data before I install the kernel also, however it produces the same result.

Much appreciated :)
[Nexus S Android Development] golu12:
im on modaco rom, and i was successfully able to do 1.2ghz, so will this 1.3ghz thing also work?
[Nexus S Android Development] deez1234:
I believe it was confirmed working a few pages back.
[Nexus S Android Development] crushsuitandtie:
That screen off problem is because 200 is too low to get the screen on. That's why I requested to get 400mhz back. Having 800 MHz during sleep is a battery drain. 200 seems to be a more useless step than 400 in the case of the nexus.

Anyway raise the Max on the profile and it will wake correctly.
[Nexus S Android Development] avetny:
Latest Galaxy S Overclock to 1.6 GHz (Vibrant) Sees FPS Unlock :)

i hope we gonna get some thing like 2GHz :D
[Nexus S Android Development] AllGamer:
Does Bluetooth works properly now on the OC mod to 1.2?

or it's still under construction?
[Nexus S Android Development] k0mpresd:
i got 3444 on quadrant using 1.3ghz kernel.
[Nexus S Android Development] hoseth0711:
Am i the only one who got serious problems with loading big pages containing flash 10 stuff? I believe the kernel is the sinner. I am using the bionix ROM. My kernel is running at 1000-1300. Can anybody help ? I have deleted the flash apk in system with root explorer and there after installing the flash app again.
[Nexus S Android Development] Doug8796:
morfic.. what part of the code do i need to modify?
[Nexus S Android Development] 651stp:
Actually i have mine set to 200 all the time and i've never run into any screen off problems with any of the kernels that has been released by morfic so far. I dont know if im just lucky or what but it doesnt happen to me, and i cant re-produce it even when i set it to 100.
[Nexus S Android Development] 651stp:
in SetCPU, try to have the lowest at 200. (thats what i keep mine at with no problems) and leave set on bootup unchecked. If you have profiles that are active while the phone is sleeping try to delete those and see if that gets rid of the screen freezing up.
[Nexus S Android Development] MaliceOmega:
dont know if this will help but this is the exact steps i took to get my flash running again.

use root explorer to delete flashplayer.apk

reboot phone

go and install from the market

reboot once more for good measure

and viola mine started working.

im running the rom and kernel seen in my sig for reference. my friend said it didnt work for him using this kernel and cm7 alpha 2
[Nexus S Android Development] morfic:
Shame it doesn't run on cm7, I can see what the Cm7 initrd needs, to avoid building 2 kernels all the time, it works to split the kernel and redo mkbootimg with the cm7 alpha 2 initrd.

I know because I booted cm7a2, it ran almost as quick as Bionix, just a little under. Not sure how valuable it is to compare an alpha rom with a preview of another. But it proofs the switch of units makes it boot on the other rom. Just make sure the modules get put in place too
[Nexus S Android Development] hobbescs:
I was having trouble on 1.2, couldn't get a gps lock. Upgraded to 1.3 and now all is good! Keep up the great work!!
[Nexus S Android Development] morfic:
About flash, just loaded and used http://www.barbie.com if that site works, no further test is necessary.
[Nexus S Android Development] mbh87:
I hope he adds BLN. That would be AWESOME.
[Nexus S Android Development] AllGamer:
LOL :p nice test site

you'r right, that whole thing is Flash made
[Nexus S Android Development] morfic:
once neldar ports it, i am missing bln.

everyone go buy neldar's app in market, seeing money come in may help his motivation to port it. :)
[Nexus S Android Development] mbh87:
In order for his app to work you need to add BLN support I thought.
[Nexus S Android Development] morfic:
Correct, and neldar knows his code better than anyone, so until he ports it, no bln.

I jokingly said a lot of people buying his app, (asking for nexus s support) may generate enough motivation on his part.
[Nexus S Android Development] mbh87:
Gotcha, guess if it was easy to do you would have done it. I'm a n00b to Samsung phones so don't mind me lol.
[Nexus S Android Development] Greenarcher707:
I've browsed thru the entire thread but i didn't find the stock kernel. Someone post it please. Thanks.
[Nexus S Android Development] morfic:
updated OP with link to Trinity13 kernel for stock roms, includes ext4 mount fix.
[Nexus S Android Development] Greenarcher707:
You are the man! Thanks a lot. Wait, if it's a stock kernel why does it still have that bootlogo? don't mean to knock your work bro, i just want to go back to real stock everything.
[Nexus S Android Development] morfic:
For those that asked about the fps fix, build JPX source for 2.2.1, it seems it's taken care of in source now w/o a fix using the aries_eur_defconfig.

Samsung changed frequency to 72Hz from 60Hz, except when building for "Latona"
[Nexus S Android Development] unremarked:
Its his sort of signature.
[Nexus S Android Development] morfic:
This is Trinity for Stock Roms, not stock stock kernel.
[Nexus S Android Development] thejron:
"Stock rom" kernel working good on CM 7 alpha?
[Nexus S Android Development] 651stp:
morfic what did you get? i just got 60.3 in nenamark!! :D!
[Nexus S Android Development] morfic:
updated OP
[Nexus S Android Development] Marmle:
Trinity2.0 IS working with Unofficial CM7.. Im currently using #26 going to update to #28 in a min.

Updated to Unofficial CM7 #28 and then re applied Trinity2.0 and works just peachy.

Thanks
[Nexus S Android Development] jlevy73:
Anyone test to see if BT is working on this with CM7?
[Nexus S Android Development] icandy75:
Friend just tested works 100% on both CM and Bionix.
[Nexus S Android Development] jlevy73:
Woot! Excellent to hear. Thank you
[Nexus S Android Development] simms22:
oh man im all over this one if its working with CM7! backing up now!!!
[Nexus S Android Development] smelian:
is there version for Modaco Rom ?
[Nexus S Android Development] icandy75:
Just for the record I'm running Bionix and my friend is running CM. He SAYS he has no BT issues. I KNOW I don't.
[Nexus S Android Development] simms22:
with cm7, 1st time i flashed i lost my rom. second time i reflashed the rom then the kernel and all is greaaaat! thank you :)
[Nexus S Android Development] daffyno:
do u have flash cm7, reboot and flash kernel?

or flash cm7, flash kernel and reboot?

thx a lot :)

p.s.

do u have Ext3 emulation mode hack too?
[Nexus S Android Development] 651stp:
Confirmed: Bluetooth Works.

Thanks so much Morfic
[Nexus S Android Development] simms22:
backup, flash rom, flash kernel, reboot.
[Nexus S Android Development] dylchow:
2.0 gets stuck at bootlogo for me... using stock :(
[Nexus S Android Development] Anderdroid:
Ugh.

Say what you want but I don't think I can keep it. This huge red explosion logo is too painful.

And before you call my troll blahblah I've donated a hefty sum to teamwhiskey already so blah.

Whatevz though I'll deal. Won't boot on stock 2.3.1 though.

Either way, this would be a much nicer splash :P
[Nexus S Android Development] Anderdroid:
Sigh. Wish this would have stayed stock. /cries and waits for next kernel dev that sticks on stock. Awesome work nonetheless

I was never a fan of bionix custom init or even CM. Guess I'm weird. To each his own I guess. Back to my Nandroid...
[Nexus S Android Development] thejron:
Running this with CM. Seems pretty slick. Thanks!
[Nexus S Android Development] generalagony:
Getting status 7 error when trying to flash via cwm. Any suggestions? Using #28 nightly btw.
[Nexus S Android Development] generalagony:
Nm redownloaded and flashed. Must have had a corrupted file. Any suggestions on Setcpu settings and profiles?
[Nexus S Android Development] mrmarshall428:
Will this work on Modaco Rom?
[Nexus S Android Development] mbh87:
Why not try it and see? Worse that can happen is you will bootloop.
[Nexus S Android Development] mrmarshall428:
I will try it, just wondering if someone had already tried it.
[Nexus S Android Development] zps123:
setcpu crashes after flashing the newest kernel :confused:
[Nexus S Android Development] simms22:
uninstall it then reinstall it
[Nexus S Android Development] jlevy73:
BT not working for me. Tried several different iterations all end up with BT trying to turn on but never does.

Edit: CM7 with latest Trinity kernel
[Nexus S Android Development] zps123:
thx for the help! but worked after a reboot :p
[Nexus S Android Development] defysword:
can you wake up the phone using a screen off profile (100 min, 400 max)? I got frozen on stock rom 1G.
[Nexus S Android Development] DroidRC1:
Im having the same issue when I use the screen off profile..but mine is only when its changing...
[Nexus S Android Development] zps123:
yes, i was having the same issue, but seemed work fine after i pulled the battery off and reboot.... since i have 2 extra batteries... i deleted the profile :p
[Nexus S Android Development] simms22:
bluetooth working over here without a problem. cm7, v2 of the kernel.
[Nexus S Android Development] Taquitoz:
Seemed to disable my 3g on tmobile. Now only getting an "H" where it usually says "3G"
[Nexus S Android Development] defysword:
Hi Morfic,

Are your kernels UV ones? What are the actual voltages for all frequencies?
[Nexus S Android Development] tominater12:
How do I tell if I have the new kernel?
[Nexus S Android Development] ikon8:
You see a nuclear explosion when you boot up your phone, seriously.
[Nexus S Android Development] DroidRC1:
H is 3g..matter fact its better...its HSPA...are you using CM mod?
[Nexus S Android Development] tominater12:
Then I am good to go. (I am able to overclock to 1.3 GHz but I wanted to be sure)
[Nexus S Android Development] ikon8:
Using v2.0 on cm crackflash dailies, I was getting reboots while in screen off. I currently setup a setcpu profile for screen off for 200/800 and now it seems to be working great. Also, when I have setcpu autodetect settings I can only adjust the setting in the increments of 100,200,800, 1000, and 1300 is this how it is for everyone? I saw some people saying they're using 400mhz but my slider just goes from 200 right to 800. This is using ondemand scaling.
[Nexus S Android Development] defysword:
I want longer battery life, anyone else interested in a UV kernel?
[Nexus S Android Development] hkoutso:
Can confirm that Trinity 2.0 won't work on stock 2.3.1 - it gets stuck at boot on morfic's boot logo -

Maybe this has to do with the Ext4 tweaks once more ?
[Nexus S Android Development] spyz88:
Does anyone notice that if you flash v2 of the kernel, in the system information it still says Trinity13 v1.3? Wouldn't it says v2?
[Nexus S Android Development] rb9228:
I have that same issue.
[Nexus S Android Development] icandy75:
I'm just speculating but since Morfic releases different kernels with different clock speed I'm assuming v1.3 just refers to what your clock speed. V2 is def. not the same because BT works but everything else remains the same so why change the build number?
[Nexus S Android Development] spyz88:
If it was changed that dramatically it would definitely get a new build number. It was prolly just not changed by mistake.
[Nexus S Android Development] dinan:
Just flashed the ROM with the trinity kernel. Working well so far, very snappy!

However, I notice my gmail and other push related messaging being delayed. Sometimes when I turn the screen on, the 3G indicator and signal bars turn from green to grey, like it's losing connection or something. Then I'll get my emails flooding in shortly after it reconnects, but it doesn't seem to be able to fetch them while the screen is off.

Anyone else having issues like this?

EDIT: Woops this was meant to go in the ROM thread, not the KERNEL one, sorry!
[Nexus S Android Development] PeartFan40:
Trinity Update

So glad you released this update. Every time I turned on bluetooth, the phone would slow down to a crawl. Almost unresponsive. I've noticed on the power control widget, the green indicator bar for bluetooth is a faint green. Is that jsut a small bug?
[Nexus S Android Development] morfic:
that's called rushing to deliver the goods with no time left before rushing to work.

ignore this, i will make sure the next kernel will properly say Trinity14_V1.0

I will not rush this one as i want to make sure 1.4GHz gives more than just higher Linpack.

Trinity14 is stable so far. I will not release it until after i return from nightshift.

For now, if the .zip says Trinity13_V2.0 that's what's inside......
[Nexus S Android Development] morfic:
Just to clear up the confusion the non edit in build.prop stirred up:

Trinity13 is 1.3 GHz, V1.3 is the revision of it. (coincidence both have a 1 and a 3 ;) )

With BFS added and fixed bluetooth it became V2.0

DoW14 for Vibrant was a 1.4GHz kernel, just for reference.

Trinity14_V0.9 is on my phone right now.

Based on how nightshift goes, you will see something tonight (US, Central time, after 4am) or early tomorrow.
[Nexus S Android Development] icandy75:
Thanks for clarifying Morfic and holy crap... it appears we have an e.t.a. without even asking!
[Nexus S Android Development] hkoutso:
Morfic thanx once more for clarification.

Your kernel (v1.3 without Bluetooth fix) is super stable as I 've been running it for the past 2 days. As I am in stock 2.3.1 I tried v2.0 but it gets stuck at boot. Is it only Bionix NS compatible as of v2.0 ?

Appreciate your work ;)
[Nexus S Android Development] generalagony:
Would like clarification on this also. I am having the same issues.
[Nexus S Android Development] generalagony:
I am getting extremely low frame rates on Dungeon Defenders when running this kernel along with CM7. Frame rate is fine while running stock CM kernel. Anyone else experience this?
[Nexus S Android Development] gundamboy:
I love this kernel! the only thing i don't like ( and i'm sorry but i know you need to brand it somehow ) is the bootup logo :(

SO FAST! :D