Database Users

Voodoo & clockwork on telus fascinate!!

ive been testing kernals on my telus fascinate t959d to see if there was any way to get around the no developer issue and came across the love off my live.
the kernels name is "Voodoo-stable-5.0.-Froyo-GT-I9000-odin-pda".
From leaked stock 2.2, i flashed this kernel over the stock through odin. during the initial boot, the female droid voice walked me thru voodoo setup. wait afew minutes after your phone is done loading to allow voodoo to completely enable itself or u will get fc issues. To get to Red clockwork recovery, while your phone is off, hold both volume bottons and the power button. continue holding those 3 buttons until the 2nd i9000 popsup then release all 3 buttons. That should load u into clockwork recovery voodoo. This just basically opened the floodgates for rom testing for me. im running nero v4.1 on my TELUS FASCINATE t959d with no errors at all.
imma upload and post the link
this is the omega leaked 2.2 files in cause u need emergency odin reflash
http://forum.xda-developers.com/showthread.php?t=868829
this is the voodoo enabled kernel
http://rapidshare.com/files/442330146/Voodoo-stable-5.0.1-Froyo-GT-I9000-odin-pda.tar to install this, just download odin, get yout phone into download mode, place the file in the pda slot, and go. i suggest u go back to stock b4 u start for a wiped stock install. if u need help, email me at [email protected] Thx to omega for creating my interest in android custom roms

UPDATE!!!
i just exchanged the previous kernal for a i9000 advanced zoodoo OC/UV and its working mint with nero 4.1. heres the thread to the other kernals
http://forum.xda-developers.com/showthread.php?t=909540
telus fascinate users rejoice!!!!! we r now up to date with everything

after playing around some more ive realized the telus t959d can use most i9000 kernels with no issues. the only 2 issues ive found running advanced voodoo is theres no home button but since i hate having apps running in the background that doesnt bother me and when your phone completely dies, and u plug it in, the battery charge screen gliches out and needs a battery pull. i can easily get around both for the features of a overclocked or undervolted kernel. as far as roms go, most i9000 roms and most vibrant roms work! after i got the rom up and running i just reflashed the proper kernel 4 my phone and the telus modem pulled from omegas leak and bam! ive tested both i9000s darkys v8.0 gingerbread but didnt like the icons for sms and gmail and also nero v4.1 for vibrant with flashed telus modem and i9000 kernel which works mint. running right now. advanced voodoo comes with a custom boot which overwrites the poopy i9000 image and replaces it with a red voodoo anvanced screen. so instead of seeing the sght959d then i9000, it says sgh t959d then advanced voodoo then nexus x boot. looks sweet

Not quite "mint" from your own description.
These are some of the problems I had running kernels / Roms meant for other phones, are you experiencing any of the same?
1- Reversed volume buttons
2- GPS not working (as in won't even start)
3-No FM radio
4- Plugging in the USB cable caused the phone to go into a shutdown/boot loop

GREAT NEWS!!! FINALLY!
Tho.. since Im noob in this world.. Im going to wait a little more until we find suitable (i.e. no homekey error stuff ) and stable!!
Great Great Great GREAT! Thanks LINKSLOVESANDROID!!!!
Please update more and more about your "experiment" Hehehe

daoom said:
Not quite "mint" from your own description.
These are some of the problems I had running kernels / Roms meant for other phones, are you experiencing any of the same?
1- Reversed volume buttons
2- GPS not working (as in won't even start)
3-No FM radio
4- Plugging in the USB cable caused the phone to go into a shutdown/boot loop
Click to expand...
Click to collapse
i had these same issues while running a vibrant kernel. install a i9000 kernel. use 1 of the 1s i packaged in the 1st 2 posts. i flashed a i9000 kernel to get clockwork. then used clockwork to flash nero v4.1 which comes with a vibrant kernel in the rom which automatically overwrites your previous i9000 kernel u flashed b4 hand to get clockwork running. i then used odin to flash a i9000 kernel over the vibrant kernel. Then used the telus modem pulled from omegas 2.2 leAK and flashed that over phone in odin Which left my telus fascinate with the following
-1.3 Ghz Overclock / Undervolted Kernel(Thx U Voltage Control)
-Advanced Voodoo v666.2 i think.... with voodoo sound and advanced voodoo bootscreen
-Nero v4.1 Gingerbread Looks NICE!!!
-working voice calls and text messages
-3d gaming working mint with overclock
-google maps is working properly- navigation seems to not b able to find location thou i didnt wait long and i was indoors
-fm radio is not there because it was not made 4 i9000s just the t959d but isnt a big deal 4 me cause u need to have the headphones that came with the phone hookedup to use as a antenna. if u dont have those exact heapdhones plugged in, the phone says something like please attach headphones for antenna signal." better to just geta internet streaming radio app
- flashing the i9000 kernel solved the following issues
proper volume rockers configuration
and the charging issue. now charging works fine. the only time i had a issue was when i charged my phone while it was turned off and it needed a battery pull. but then i plugged it back in while off and it worked fine.
basically, the only issue i can see being a problem for some is the no home button just 2 back buttons. but honestly, the android os told me to use back more often then home so it saves system ram and doesnt have too much background apps running.
so basically, if your want a custom rom, the only downside is theres no home button and navigation MAY not work.
on the plus side, your phone will become super fast to the point stock rom is slow. ill b posting a video in the coming days of my rom setup from phone startup to shutdown to PROVE this method works

Another user has asked supercurio to make us a custom kernel, supercurio said in his vibrant kernel thread that he would, but that was a couple of days ago. Please post the vid, this intrests me, I can live with the back and home button problems, but am worried about the usb boot loop.
EDIT: I've just flashed the kernel you suggested. Home acts like back, but everything else seems fine so far. I booted into clockwork and enabled voodoo, plus I also O/C to 1200mghz. When I get home i'm going to plug it into usb and see what happens. Hopefully no bootloop!
OK so I have big market place problems, from what I can gather, the phone is recognized by the market as an i9000, which means I can't get some apps that i've had before...everything works but home...just sucks that the market does not work...will try to fix with market enabler...

roccos_van said:
Another user has asked supercurio to make us a custom kernel, supercurio said in his vibrant kernel thread that he would, but that was a couple of days ago. Please post the vid, this intrests me, I can live with the back and home button problems, but am worried about the usb boot loop.
EDIT: I've just flashed the kernel you suggested. Home acts like back, but everything else seems fine so far. I booted into clockwork and enabled voodoo, plus I also O/C to 1200mghz. When I get home i'm going to plug it into usb and see what happens. Hopefully no bootloop!
OK so I have big market place problems, from what I can gather, the phone is recognized by the market as an i9000, which means I can't get some apps that i've had before...everything works but home...just sucks that the market does not work...will try to fix with market enabler...
Click to expand...
Click to collapse
i just noticed it wont lemmie donwload afew games on the market cause of the i9000 kernel. if u find a fix lemmie know..i just stumbled across a 1.6 ghz overclocked kernel. gonna check to see fi thias wqorks

LINKSLOVESANDROID said:
i just noticed it wont lemmie donwload afew games on the market cause of the i9000 kernel. if u find a fix lemmie know..i just stumbled across a 1.6 ghz overclocked kernel. gonna check to see fi thias wqorks
Click to expand...
Click to collapse
Market is totally f'd up. Tried to fix by:
- go back to stock kernel - no good
- factory reset - no
- clockwork wipe data/cach - no good
- flash a new rom and start fresh - no good
I'm going to ODIN back to complete stock now, and re-root. I would recommend to NOT FLASH this kernel, the market does not work properly. Nothing is there; no rom manager, no sgs anything and your paid apps will be GONE.

I'm so glad that this topic is on its way!
A question from a noob tho... Is flashing other ROM kernel is the only way we can have custom ROMS?
Why can't we have our own?? (

If you can post up a video so i can check out what you've posted, i would be willing to help out and find solutions for some of the problems at hand.
Right now i'm alittle wary about this.

cowvun said:
If you can post up a video so i can check out what you've posted, i would be willing to help out and find solutions for some of the problems at hand.
Right now i'm alittle wary about this.
Click to expand...
Click to collapse
There are two problems i had:
1. The market is f'd up...i'm on some wierd test market and can't get access to my paid apps, or any other apps for that matter, only test apps. See here: http://forum.xda-developers.com/showthread.php?t=878181&page=5 and here: http://forum.xda-developers.com/showpost.php?p=10736976&postcount=89
2. Home acts like back, which is a big problem since you can't multitask because as you hit back to do the next thing, you will close whatever you were doing before.
Other than those two problems everything worked fine.

wwowz said:
I'm so glad that this topic is on its way!
A question from a noob tho... Is flashing other ROM kernel is the only way we can have custom ROMS?
Why can't we have our own?? (
Click to expand...
Click to collapse
until a developer decides we are a big enough group of users that we deserve our own "hiding spot" we will have to use i9000 kernels to use custom roms. rumor has it the creator of voodoo supercurio is developing a kernel for our phones which will lead to custom roms. until then, i9000 kernels r the way togo. i have a i9000 advanced voodoo kernel overclocked at 1.28 ghz and undervolted to save battery running a vibrant custom rom called nero v5 which basically skinned the entire setup to look like gingerbread and got rid of the samsung bloatware. honestly, even after we have our own custom kernel ill b sticking with i9000 kernels. just because development has been rediculously slow with the telus t959d fascinate. its taken this long b4 a kernel was even thought about. until it has its own development team creating new roms like every other sgs model on a weekly basis, i9000 wuill have the go ahead. i9000 kernels can run i9000 roms and vibrant roms. and there development communitys are huge! try the above method using custom i9000 kernel. the only issue is theres no home button and afew apps wont download because it thibnks your ussing a i9000. only app i notcied was that 3d mmorpg wont download. i cant remember the name of it. but other then that its great. i got psx4droid running final fantasy 9 overclocked with voodoo. runs MINT!!!! ill gladly walk u through the entire process over msn or facebook etc. send me a email [email protected].

roccos_van said:
There are two problems i had:
1. The market is f'd up...i'm on some wierd test market and can't get access to my paid apps, or any other apps for that matter, only test apps. See here: http://forum.xda-developers.com/showthread.php?t=878181&page=5 and here: http://forum.xda-developers.com/showpost.php?p=10736976&postcount=89
2. Home acts like back, which is a big problem since you can't multitask because as you hit back to do the next thing, you will close whatever you were doing before.
Other than those two problems everything worked fine.
Click to expand...
Click to collapse
i jhad no problems with market. works perfect for me. i just got my girlfriends hd camera so imma record a video at some point tonight. most likely start a fresh thread with proper step by step instructions to get it up to the point i have mine

thanks for the reply! I would go ahead with the kernel but the only downside I'm worried about is the home key I use it all the time XD

LINKSLOVESANDROID said:
ive been testing kernals on my telus fascinate t959d to see if there was any way to get around the no developer issue and came across the love off my live.
the kernels name is "Voodoo-stable-5.0.-Froyo-GT-I9000-odin-pda".
From leaked stock 2.2, i flashed this kernel over the stock through odin. during the initial boot, the female droid voice walked me thru voodoo setup. wait afew minutes after your phone is done loading to allow voodoo to completely enable itself or u will get fc issues. To get to Red clockwork recovery, while your phone is off, hold both volume bottons and the power button. continue holding those 3 buttons until the 2nd i9000 popsup then release all 3 buttons. That should load u into clockwork recovery voodoo. This just basically opened the floodgates for rom testing for me. im running nero v4.1 on my TELUS FASCINATE t959d with no errors at all.
imma upload and post the link
this is the omega leaked 2.2 files in cause u need emergency odin reflash
http://forum.xda-developers.com/showthread.php?t=868829
this is the voodoo enabled kernel
http://rapidshare.com/files/442330146/Voodoo-stable-5.0.1-Froyo-GT-I9000-odin-pda.tar to install this, just download odin, get yout phone into download mode, place the file in the pda slot, and go. i suggest u go back to stock b4 u start for a wiped stock install. if u need help, email me at [email protected] Thx to omega for creating my interest in android custom roms
Click to expand...
Click to collapse
i cannot find a cwm_froyo.tar for telus fascinate anywhere. every link in these forums give me a recovery zip but only has recovery.bin in it..anyone help? this is going to be my first attempt at flashing a new rom so i am pretty nervous and i dont want to brick my phone, i amalready rooted, i have cw rom manager on my phone and everytime i flash cwm recovery it says it was successful i go to recovery and my phone reinstalls stock recovery without cwm, any info or links to tuts would be apreciated...
this is the thread i have been trying to use...http://forum.xda-developers.com/showthread.php?t=948722

question
figured this one out

wwowz said:
thanks for the reply! I would go ahead with the kernel but the only downside I'm worried about is the home key I use it all the time XD
Click to expand...
Click to collapse
use Galaxy Tuner.... enables gestures to replace the missing home key. works great

Need help with loading other ROM

Hey guys. Hope that someone can help me out here, I'm stuck trying to load a new ROM on a friends Iconia A500.
I searched the internet for a simple rooting tool. Came across Blackthunder, used it to root the Iconia. Rooted without any problems. Afterwards I download the Acer Recovery tool from the market. Flashed with CWM.
Problem is that when I reboot into recovery it keeps on saying "booting recovery kernel image", nothing happens. On my own Transformer I just boot into CWM and flash with whatever I'd like.
Can someone please guide me to a step by step tutorial, or explain what I did wrong here?
Cheers!

ldeijkva said:
Hey guys. Hope that someone can help me out here, I'm stuck trying to load a new ROM on a friends Iconia A500.
I searched the internet for a simple rooting tool. Came across Blackthunder, used it to root the Iconia. Rooted without any problems. Afterwards I download the Acer Recovery tool from the market. Flashed with CWM.
Problem is that when I reboot into recovery it keeps on saying "booting recovery kernel image", nothing happens. On my own Transformer I just boot into CWM and flash with whatever I'd like.
Can someone please guide me to a step by step tutorial, or explain what I did wrong here?
Cheers!
Click to expand...
Click to collapse
Well, the big question...Which version of android do you currently run?
Which version of CWM did you try to flash?
Second question, which bootloader are you currently on? To find out, just run the acer recovery app and it will tell you when it starts.
And finally, which rom are you trying to install.
Then we can give you a more precise answer.
MD

Thanks. I managed to make a few steps in the right direction.
New problem though. I managed to get CWM working correctly. It feels a bit buggy, with some backbuttons not responding. Downloaded Lightspeed 4.7., seems like the fastest rom out for the Iconia.
Factory reset + /system format. Installed the zip, everything looks ok.
When I boot up the tablet the first few seconds the screen looks fubar'd. Like a really nasty system crash, with white lines running all over the screen. Afterwards you get a standard boot animation & ICS loads up. If you put the tablet on standby though it goes into deep sleep after about 10 minutes.
I downloaded Taboonay just to be sure it's something in the rom. Taboonay works, but feels significately slower.

ldeijkva said:
Thanks. I managed to make a few steps in the right direction.
New problem though. I managed to get CWM working correctly. It feels a bit buggy, with some backbuttons not responding. Downloaded Lightspeed 4.7., seems like the fastest rom out for the Iconia.
Factory reset + /system format. Installed the zip, everything looks ok.
When I boot up the tablet the first few seconds the screen looks fubar'd. Like a really nasty system crash, with white lines running all over the screen. Afterwards you get a standard boot animation & ICS loads up. If you put the tablet on standby though it goes into deep sleep after about 10 minutes.
I downloaded Taboonay just to be sure it's something in the rom. Taboonay works, but feels significately slower.
Click to expand...
Click to collapse
Glad you made some steps.
You still didn't answer my questions about bootloader.
The reason you got the screwy screen on boot, is because that rom you tried to install, used a "hacked" kernel so that ICS could run on an HC bootloader. It's perfectly normal. The deep sleep you refer to, is called SOD, (sleep of death) and usually you have to reboot.
This is why I asked which bootloader you were currently running. Because it makes a big difference since the release of ICS. Acer changed the playing rules.
Once again I ask you, to run AcerRecovery, and just get the version bootloader you are currently running. Upgrading to the ICS Unlocked bootloader makes things a whole lot smoother.
MD

Hmmm, thought it had something to do with that.
Installed Acer Recovery Installer. Am on bootloader version 0.03.11-ICS
Recovery version CWM rev1.7 (v5.5.0.x). Asus Transformer has it's fair share of SOD's, but those are random. With the Lightspeed rom I tried it was like clockwork.
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?

ldeijkva said:
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
Click to expand...
Click to collapse
Moscow Desire said:
The reason you got the screwy screen on boot, is because that rom you tried to install, used a "hacked" kernel so that ICS could run on an HC bootloader. It's perfectly normal. The deep sleep you refer to, is called SOD, (sleep of death) and usually you have to reboot.
Upgrading to the ICS Unlocked bootloader makes things a whole lot smoother.
MD
Click to expand...
Click to collapse
nuff' said,.

ldeijkva said:
Hmmm, thought it had something to do with that.
Installed Acer Recovery Installer. Am on bootloader version 0.03.11-ICS
Recovery version CWM rev1.7 (v5.5.0.x). Asus Transformer has it's fair share of SOD's, but those are random. With the Lightspeed rom I tried it was like clockwork.
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
Click to expand...
Click to collapse
If you plan on running ICS correctly now, and in the future, it is highly advisable to upgrade your bootloader to an ICS Unlocked version.
Civato posted a guide for doing just that (dev forums). It has all the info you need.
The reason SOD happens, is that in order to get a good root, and have an unlocked bootloader, certain things have to be done (hacks). With them. Remember, ICS kernel and bootloader communicate with each other. The hack to the kernel, resulted in the screwy display on boot. Also, SOD's can happen also (power management issue with wake loks). But at the time, in the beginning, it was a good method for getting ICS to run on a HC bootloader.
The unlocked ICS bootloader is the way to go. Every Dev's rom (made for ICS BL) has the kernel modified so that you not only get full root with no issues, you rarely get SOD anymore. Also some other enhancements have been added such as GPS tweaks for example.
If you get SOD, as I said, it happens so rarely now days that most can't remember that maybe they shut their tab off!
Most of the dev's (myself included) have quit support for HC BL based ICS roms. No reason for it.
Also remember, Acer is just starting to push ICS to the tabs a little. So builds will change on a regular basis. And the early builds will not be 100% stable. 95% probably. The rom you install today, may have a new version in a week. Who knows.
MD

or nightly versions ,sometimes its hard to keep up , I think ICS not only changed the rules but the "skys the limit" now and Devs see stuff and change it quickly!

Issues/Things to note about 4.04 (not brick related)

Ok been running 4.04 for a sometime now. I got it as it first came out.
Some issues that u have noted outside of the bricking issue. **disclaimer I am running my own built version of this ROM deoxeded zipaligned bla bla bla plenty of tweaks etc and the ROM is faultless(not really it has its faults and I am about to list them) with exception of a few things that may or may not be kernel related. IT DID NOT flash the new .pit file. I have built the ROM as according to 4.03 builds and used Siyah kernel.
1. initial boot and dalvik cache build takes an extremely long time. Easily mistaken for bootloops and possibly another reason people prematurely ejected this ROM
2. Android is upgrading/updating splash does not exist. Further adds to the concern that phone has enternal bootloops...it doesn't it just doesn't warn you. It goes back to the gingerbread days where you wore a big question mark ? on your head "What is my device doing?"
3. Bluetooth enablement does not work. We go from 4.03 that had wifi issues much similar to fixed wifi and issues with bluetooth. Sux. Guess you cant win eh?
My guess is that this is specifically related to the kernel and framework. Ihave the framework decompiled now and I will be looking into maybe making some adjustments to allow for the bluetooth drivers in 4.03 kernels to interact with 4.04, rather than a whole new re-reslease of kernels just to combat this issue.
4. USB not detectable in Windows 7? Hmmm I am not sure what happened here? It worked flawlessly for 2 days and then all of a sudden not recognised? USB speeds were perfect when it did work, reflashing the ROM did not fix this? My guess is that this is also kernel<->framework related. Also to note here that within the siyah recovery you can mount USB no issues and transfere, so no eMMC corruptions before you freak out.
5. Vol down + power button for screen capture does not work? This again maybe because of the kernel used?
Can anyone give any reason for me not running the new pit and flashing stock kernel? Does the stock kernel require that there is a repartition or is this an assumption?
Additional notes: Further testing my eMMC with Gotbrickbug *MASSIVE thanks to chainfire for this support* personal thanks from me. Thanks Chainfire you're a legend! After testing it revealed oddly enough that my eMMC was inconclusive, so not that it helped me much, but I have flashed this firmware now several times and have not had any issues. Everything working smoothly and 100% except for the above mentioned.
I am tempted to flash the standard kernel now (again no repartition) and then do CFroot for the stock kernel image on this firmware to see if these issues are alleviated in 4.04?
Additional to this is that I have the 15 toggles mod by Jkay translated and compiled with exception of the last file on systemUI for 4.04. I would REALLY love to have this ROM running for everyone.
Any input suggestions warnings (besides the brick scare - I am not scared cause I doubt my phone will brick considering I have flashed it so many times now with the phone acting the same every single time)are welcomed. Please use your head when you respond and not your bricked phone, I would like intelligent answers and discussions. Preferrably not from n00bs or those that are only rehashing all that has spilled out across the petition thread already.
My understanding is that it is a repartition issue with bricking not a kernel or ROM issue its self. My understanding is that I can flash any kernel I like I can flash the stock one and I should be able to flash a rooted one after it to get back if I want?
Proceedure now:
Flash ROM
Flash kernel
Flash CFroot
Flash Modded recovery
Happy days?

I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.

Again flashed this ROM no problems.
I also attempted to run 4.04 czech republic version of this ROM to which it did not boot or run. Just to let those know that were considering doing this. I had 3 apks from that 4.04 build that refused to deodex? Also the sizes of all apks in this version of 4.04 (which does not come with a supplied .pit file) are vastly different to those in the Euro 4.04 supplied with .pit?
Yet to download and try 4.04 Chinese version? I figured someone else has probably already done this....the chinese are fast lil buggers. They don't much around! haha. If anyone has feel free (and please I would like you to contribute) to comment in this thread on your findings?
James
PS: Just about to flash standard kernel on unpartitioned GS2 if all goes well I will implement CF-Root. Cheers

donalgodon said:
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Click to expand...
Click to collapse
Did you re-partition when you flashed stock kernel? I like the sounds of this. I have the 4.04 working nicely.....if i can achieve the above I will create a ROM and upload. Thank you for your valuable input
I may even test with the czec 4.04 kernel and see what happens there? Hmmm
Kernels are identicle sizes but not the same?
czec zimage: MD5 2A4AE1B758D934E2AD1791E318F94424
europe zimage: MD5 FCB26E67AE9E7F701793B6014E4AF7D2
see attached for additional size details? I am wondoering if czec might be better for no repartition was/is used in this 4.04 build?
James

WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!

Jarmezrocks said:
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Click to expand...
Click to collapse
No fix for USB enablement? I have switched the customboot.sh for the MTP application. I however don't have MTP.apk in system? I may place this apk and then re-try to see if I might be able to get the thing to be recognised by my PC.

USB Mass storage is now working via the old method. I need to have the MTP client in system/app for this to work. No longer getting the USB device not recognised which is great.
Any kernel devs want to share with me how to embed the correct components in the kernel to allow for customboot.sh to work? I am certain then that USB mass storage will work when that script can be run and enabled at boot. I dare say that boot animations should work then also.
4.04 is starting to shape up nicely now

Black lines scare?

Remember some months back there was a huge scare of kernels or roms causing permanent black lines on the screen. Was there any consensus to what was causing them and how people can avoid them?

@Manbot27 nobody still knows what causes it since it happens on random things I have read, you cannuse dr87 twrp recovery, try to flash roms without charger connected, if you are on stock based rom flash dorimanx kernel maybe, search the thread for more stuff .

wulsic said:
@Manbot27 nobody still knows what causes it since it happens on random things I have read, you cannuse dr87 twrp recovery, try to flash roms without charger connected, if you are on stock based rom flash dorimanx kernel maybe, search the thread for more stuff .
Click to expand...
Click to collapse
Is it still happening it was on a temporary scare?

[Q] TWRP /w heat protection?

http://forum.xda-developers.com/showpost.php?p=53605359&postcount=10351
I just incountered this today.
What does that mean?
Is it just V2.7.1? Are newer ones also heat protected? Why make them "non-heat protected" in the first place?
It says in the thread: "They do not run all cores online and maxed as TWRP does right now".
I am running 2.7.0 and my cores aren't running on max and not all of them work all the time. I checked with Antutu. So.. What does that mean?
Thanks.

-MaoR- said:
http://forum.xda-developers.com/showpost.php?p=53605359&postcount=10351
I just incountered this today.
What does that mean?
Is it just V2.7.1? Are newer ones also heat protected? Why make them "non-heat protected" in the first place?
It says in the thread: "They do not run all cores online and maxed as TWRP does right now".
I am running 2.7.0 and my cores aren't running on max and not all of them work all the time. I checked with Antutu. So.. What does that mean?
Thanks.
Click to expand...
Click to collapse
Your recovery uses a different kernel than your rom... There's no possible way you can run antutu in recovery.
The official builds just don't have the kernel setup right so they run full throttle
Sent from my LG-VS980 using XDA Free mobile app

Yoinx said:
Your recovery uses a different kernel than your rom... There's no possible way you can run antutu in recovery.
The official builds just don't have the kernel setup right so they run full throttle
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
So when is it running max? Only when I use the recovery itself?
BTW, I found this: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705.
All I need to do to intall it is simply flash it through recovery?
And the warning in the post means that flashing this recovery will change partition type AND will wipe everything?

-MaoR- said:
So when is it running max? Only when I use the recovery itself?
BTW, I found this: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705.
All I need to do to intall it is simply flash it through recovery?
And the warning in the post means that flashing this recovery will change partition type AND will wipe everything?
Click to expand...
Click to collapse
No no no no. You got it ALL wrong =).
Let me explain.
One basic thing you need to understand is that the recovery and the ROM do not interfere with each other. If they did, you wouldn't be able to recover your device if you messed something up ROM-wise.
SO: Your recovery has a "kernel" and your ROM has a kernel. You can't use the same kernel for both recovery and ROM, heck, in most cases you can't even change the recovery kernel unless you flash an entirely new recovery.
What you see in Antutu is your ROM kernel and how it behaves. So put that aside as it has practically no value when you are talking about the recovery.
To your question:
Why would you build a recovery without thermal protection in the first place?
The answer is pretty simple: On most devices nothing has ever happened running a recovery without thermal protection. Most actions in recovery take a maximum of 3-4 minutes and then you're out of there again. The second thing is that since you're operating with a really tiny bit of storage (for the kernel) it's hard to incorporate many codes. AFAIK the whole recovery thing can only take up about 16 MB of storage. That's not much at all!
But a few months back some G2 owners got permanent white/black lines on their screen. It was later proven that heat caused the issue and that it often occured in recovery when flashed. So dr87 made the custom 2.7.1.0 recovery with thermal protection which basically throttles the cpu when it reaches a specific temperature. That would limit the generated heat and save your device - but most recovery actions (like restoring/installing and so on) take a few more seconds to complete but it isn't noticable.
For the recoveries. You have linked to two threads: 2.7.1.0 by dr87 and 2.8.0.2 by blastagator.
I personally still use 2.7.1.0 by dr87 and I've had 0 issues till date. You install that by finding the proper recovery for your device and flash it in the recovery. It is that simple.
The 2.8.0.2 by blastagator also has thermal throttling but I have not used that. No, it will NOT wipe your data UNLESS you change your file system from EXT4 to F2FS. So you can safely flash that but if you choose to change the file system then your data will be wiped.
I hope this answers your questions.

vPro97 said:
No no no no. You got it ALL wrong =).
Let me explain.
One basic thing you need to understand is that the recovery and the ROM do not interfere with each other. If they did, you wouldn't be able to recover your device if you messed something up ROM-wise.
SO: Your recovery has a "kernel" and your ROM has a kernel. You can't use the same kernel for both recovery and ROM, heck, in most cases you can't even change the recovery kernel unless you flash an entirely new recovery.
What you see in Antutu is your ROM kernel and how it behaves. So put that aside as it has practically no value when you are talking about the recovery.
To your question:
Why would you build a recovery without thermal protection in the first place?
The answer is pretty simple: On most devices nothing has ever happened running a recovery without thermal protection. Most actions in recovery take a maximum of 3-4 minutes and then you're out of there again. The second thing is that since you're operating with a really tiny bit of storage (for the kernel) it's hard to incorporate many codes. AFAIK the whole recovery thing can only take up about 16 MB of storage. That's not much at all!
But a few months back some G2 owners got permanent white/black lines on their screen. It was later proven that heat caused the issue and that it often occured in recovery when flashed. So dr87 made the custom 2.7.1.0 recovery with thermal protection which basically throttles the cpu when it reaches a specific temperature. That would limit the generated heat and save your device - but most recovery actions (like restoring/installing and so on) take a few more seconds to complete but it isn't noticable.
For the recoveries. You have linked to two threads: 2.7.1.0 by dr87 and 2.8.0.2 by blastagator.
I personally still use 2.7.1.0 by dr87 and I've had 0 issues till date. You install that by finding the proper recovery for your device and flash it in the recovery. It is that simple.
The 2.8.0.2 by blastagator also has thermal throttling but I have not used that. No, it will NOT wipe your data UNLESS you change your file system from EXT4 to F2FS. So you can safely flash that but if you choose to change the file system then your data will be wiped.
I hope this answers your questions.
Click to expand...
Click to collapse
Thank you for the long comment. Appreciate the time it takes you to answer an Androfool like me
About the black\white lines u mentioned. Its a pretty weird thing.. I mean.. No way their device got so hot at recovery (hotter than when playing games or other heavy usage) that it messed up the screen.
I also heard about people who got screen damage for no apparent reason.
And if we are talking about the lines already, I recently heard that the LG has 2 panel types and that ROM\Kernel need to fit it. To avoid screen damage problems or something. That is pretty weird for me.
About recovery, shouldn't you use the latest available version? I mean.. I dont think they release new ones just cause.
And just because I got curious: What does changing file system gives me?
Thanks again.

-MaoR- said:
Thank you for the long comment. Appreciate the time it takes you to answer an Androfool like me
About the black\white lines u mentioned. Its a pretty weird thing.. I mean.. No way their device got so hot at recovery (hotter than when playing games or other heavy usage) that it messed up the screen.
I also heard about people who got screen damage for no apparent reason.
And if we are talking about the lines already, I recently heard that the LG has 2 panel types and that ROM\Kernel need to fit it. To avoid screen damage problems or something. That is pretty weird for me.
About recovery, shouldn't you use the latest available version? I mean.. I dont think they release new ones just cause.
And just because I got curious: What does changing file system gives me?
Thanks again.
Click to expand...
Click to collapse
Hello again, and no problem. I'd appreciate it if you took the time to hit the thanks button
Even though your device feels warm when playing games like Asphalt 8 it's nowhere near the temperatures the device can reach without throttling. On stock roms the CPU throttle kicks in at about 70 degrees which lowers the cpu frequency and saves the device from heat damage. In recovery, however, there is no such protection by default. Therefore the CPU can get extremely hot - around 90 degrees (without being sure, I think it can hit 95 degrees before shutting off, if it shuts off) and that's what damages the screen.
The white lines you are talking about are not persistent/permanent. They're just there due to incompatibilities between panel type and kernel type. So that's no damage to hardware, just software not working properly.
And yes, some people have gotten permanent lines on a completely stock device. Once again, I tend to think that heat is the problem because that's what many people reported. But surely, faulty hardware is to blame, too.
About the recovery, well, both yes and no. Some updates are crucial and necessary, while others bring new features like a new UI or something like that. When it comes to recovery, I like to play it safe and I use a version as long as it's working as it should but when a newer version is deemed stable I'll use that. So that's just me, but feel free to get the newest.
Changing file system has some benefits in terms of speed - I doubt it's noticable to the average user, but it should be faster when benchmarking etc. Read more about it here: http://forum.xda-developers.com/showthread.php?t=2697069
Keep in mind that changing file systems will WIPE everything, so don't do this unless you have a OTG micro SD reader.