Ok guys
As the title said, this is a Post-flashing problems thread. If you are looking for answers/solutions BEFORE flashing anything, please go to these thread and read first.
Frequently Asked Questions writen by hasoon2000
READ THIS FIRST writen by seansk
[HOW TO] ROOT HTC RUBY / AMAZE 4G writen by Binary
====================================
This thread is an attempted to save new Amaze owners / first time flasher / Android newbies from being flamed and/or being yelled at for a reason. I'm by no means claiming to be a Dev or techies or computer geek at all - just simply gathering all the common problems newbies facing after flashing a new rom.
Others veterans please joined me in this thread for any additional info that you think might be helpful to save us all from questions that either making you laugh your a** off or ruining your day
=========
1. Wi-fi and Bluetooth not working / error
You need to flash the kernel using Kernel Flashing Tool. Kernel Flasher Tool is available on the Amaze 4G Android Development section. Those who seeks shall find.
* What's is a kernel?
In the Rom package that you downloaded, there is a file name boot.img inside - that's the kernel (sometimes Dev will included a link for kernel download on his first post as well - Xboarder56 has been known for doing this with his Roms). Double click on the ROM package and drag the kernel out to flash (How? Read the Kernel Flashing Tool thread)
* As of today (Jan.09.2012) The Amaze only has two kernels. One custom made by Faux and the stock kernel made by HTC. Most of the Rom at present came with stock kernel unless otherwise stated by the Dev that his Rom is built with Faux's kernel. Make sure you read the first, the second and the third post of ANY Rom thread. Read it thoroughly. The first post is descriptions of the Rom, the second post usually contains information regarding any changed (change log) during it's life span for each version. Read it to get an idea of what works and not and what has been fixed.
You can use Faux's kernel for any Rom that you like. If you find bugs or en-counting problems, please re-read Faux's kernel thread and report it there. DO NOT report it on any Roms' thread that did not came with Faux's kernel.
2. My soft-key lights will not light up
This problem has been reported and confirmed that it is related to Faux's kernel. Please note that it doesn't means Faux is produced a bad kernel. He is a great Dev and he is working hard to bring more exciting stuff for the whole Android community - not just the Amaze. Problems are came from HTC for they did not fully released all the necessary files hence he has to work on it blindly. If you continued to use his kernel, great! Helps him by reporting new problems (make sure you read the whole thread so that you are sure it is a NEW problem.) Otherwise, please re-flash the kernel that originally came with your Rom and DO NOT report the soft-key light's at any threads - including your Rom of choice's thread
Second common reason for this soft-light keys problem is due to the CRT enabler. If you did flashed the Crt then that is the reason. If you don't know what's Crt is, congratulation! Your chance of having issue with soft-light keys has been reducing in half and your chance of being yelled at has been significantly erased unless you jump into a thread and asked "What is Crt?"
3. Battery draining
This is the most repeating issue on any forum in XDA and on the internet as a whole. There are many myths and assumptions and theories regarding how to make your battery last longer, heck, there are even tons of apps that tried to helps users en-longing their battery life. Over all, most of veteran Android users known that battery hog mostly came from:
A. Display:
Your Android phone featured a massive screen and it needs juice to bright up your day. One can always go back to a featured-phone to get many days out of their battery or you can dim your screen brightness to 5% and carry a flash-lite with you - either ways are find
B. Radio signals:
Including Cellular signals, Wi-fi signal, GPS signal and Bluetooth signal. Wi-fi has been blamed in the past for battery consuming but with the new 4G, the star of the whole battery drama is now belong to the 4G signal. Live with it or buy a feature phone with no internet connection (j/k). Actually if you do a little research on this matter you might be able to squeezed out, perhaps, a few more hours from your battery.
C. Rogue apps:
Played a big part and hard to tracked down but it is our responsiblity as an end user. This is a pain in the neck process but it is our problems - not Devs'. You'll need to track those apps down - one-by-one
D. User setting:
Syncing also playing a big part in draining your battery and there are tons of apps that come with sync's function. Facebook is notoriously on this matter so did email and some other apps. Make sure your email app doesn't sync every 5 minutes and your Facebook too.
All of these 4 reasons mentioned can partly solved by users' setting. By doing a little research you will find methods on how to reduced battery consumption on your phones but don't expect much though. In the end your phone is a smartphone, a mini computer, a game console, a portable TV/DVD player and a Walkman. Heck, your girlfriend may have has used it as a B.O.B (Battery Operated Boyfriend) while you are away , so, please DO NOT report or opening a new thread regarding battery life UNLESS you are using one specific Rom for a long time and through many versions and just found a significantly changed in battery drainage on a new version.
4. Tethering don't work and/or it take me to the Tmobile selling page?
You need to change your APN (Access Points Name) setting. How to change APN? There is a thread of APN collection setting for many regions/countries in the world in the Amaze forum as well as all over XDA. Again, please search.
5. When I flashed a Rom, update a file. I got an error saying: error, invalid, can not find file ect ...
For some reasons, HTC loves to tested their customer's courage when it comes to flashing custom Roms and rooting phone . Do it twice! Re-flash, re-update, re-do it .... most of the times you will be success after second attempted - especially with the kernel flashing. Please don't ask me why just do it twice.
6. Wi-fi calling not working
You'll needs:
A. A new SIM Card that came with the Amaze or if you don't have one - request a new one from your Tmobile
B. Asked Tmobile to add you on the Wi-fi calling plan - free of charge
C. Registered your address on your Tmobile account
7. Power Advance Menu
You just noticed the Power Advance Menu wrongly displaying text and seem to messed up? Don't worry and DON'T REPORT as this is a well known problem and a minor one. All the function are perfectly working - just the text is wrongly displayed. The corrected way to distinguished it's functions is by looking at the icons and/or the second line of )small) text under each option. You'll get used to it after few times using the Menu. Since it's a minor issue, purely cosmetic, hence the Devs decided to concentrated their efforts on other more important issues to make sure we have a smooth working Rom, so, please DO NOT mentioned this issue at all. Believes me, nothing upset Devs more than someone posting about this issue
8. Black Screen - Phone will not wake-up
I'm accidentally find out and solved the problem of Black Screen during in-coming call (BulletProof 2.2.0). By replacing the service.jar from the previous version (BulletProof 2.1.0) with the intention to get rid of the CRT file in my system, by doing this I am also discovered that the black screen problem is gone. However, this problem can be easier solved by simply dis-able the screen-on/off animation setting instead of replacing the service.jar with the one from previous build which doesn't have CRT.
It's worth to be note that during my old days with the HTC HD2 running Nandroid I've encountering similar problem of black screen when waking up the phone and it was caused by the CRT as well. This, at least happened to me with more than 3 Rom, including the famous AmeriCanAndroid, HyperDroid and Tytung's ...
So if you are experiences Black Screen problem, please check to see if you did flashed the CRT and/or enable it?
Tips and Tricks:
* After flashing a new Rom and/or rooting my phone to get rid of some apps, I missed some stock stuff such as animation, Tmobile apps ... and I wanted it back. Where to find them?
There is a zip package named Tmobile Bloater v1.0.0 in the development forum. You can download the package and un-zip it to extract everything stock inside. Use the forum's search function for the keyword "Tmobile Bloater v1.0.0"
* I tried to use the search function in the forum but it was down at the moment
This is not a good reason for posting repeating questions. There is a litle trick to search in the forum. Try to open a new topic (but DO NOT post it), when you typed in your question / threa title, the forum will showed you several similar topics to your problem - if any - which might has been already posted by others. That's the alternative method to search, but then, again - DO NOT post before you read through them.
* The infamous screen bleed / light leakage
Workarounds Solution has been wrote by vw671 from the early days of the forum. Please read it
Also, you can turn-off the soft-key light by using terminal. Command as follows:
#From the terminal
# Turn On
chmod 0644 /sys/class/leds/button-backlight/brightness
echo 255 > /sys/class/leds/button-backlight/brightness
# Turn Off
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 0444 /sys/class/leds/button-backlight/brightness
Although this method of turning off the light may not invented by heyodee but I found his replied trying to help a fellow member in this post and I think credit should be properly giving toward his effort. Thanks mate.
* Wi-fi signal affected by phone case?
Solved by darll
* Kernel Flashing problem
As always, we should read but I will not blamed you if the thread is too long and sometime the Dev didn't update minor change for just one particular version in his first post.
As with Faux's kernel. Most of the time you can flash it using command line from ADB with the exception from version #008 Alpha 7 and later - you MUST flashing it using Easy Kernel Flasher tool. I will keep this note up-to-date should there are any changes
definitely not an attempted to increasing post
very nice!!
seansk said:
very nice!!
Click to expand...
Click to collapse
Please join me and helps by adding more common problems that you found on other subject.
antiquezip said:
Please join me and helps by adding more common problems that you found on other subject.
Click to expand...
Click to collapse
People are always going to have questions and problems....thats why these forums exist, we just try to minimize the common problems...once binary, hasoon and I put those stickies almost all the questions about, unlock, recovery and root went away...now most common problems are how to get back to stock...I'm going to be busy this month, I have other responsibilities in my life and I tried to help as much as I could (when I had more time off) and will continue to help in my time off. There are some things that need fixing some zip files... I figured out why people are having problems with them...and get stuck at fastboot etc. There are also 3 different kernels not 2, one is faux's one is for tmobile that is for the latest update 1.3 and another one for the older ones like 1.6 and 1.5. xboarder has the old boot.img kernel as the orinigal on his kernel flasher tool site, he needs to put another one up for the latest one...I will try to put all this in my stickie and update all that stuff, so people can find it in one place.
I will make a good page about it once I have more time and patience!!! I also need to update my zip file for flashing recovery, I don't know much about programming but someone mentions that there is a syntax error in the way the scripts are programmed both by xboarder and binary flash.bat (when ran under administerator and in some other circumstances) so does not execute in the current directory... when I get time I'm going to try to update my script which is basically binary's and I just added an extra script for mac and linux and added adb and all that stuff for mac and linux... I'll probably edit and update xboarders kernal flasher (to execute in current directory) IF people have problems with it, but for now I havn't seen any
for now when people run those scripts tell them to just run it and not run it as administrator.
P.s, I'll add a s link to this thread under my sticky, under problems.
I'll need to do some research on how to use the code to shorten a link ([a href .. something, I forgot, haven't using it for years on forum]. Tomorrow I will link yours, Binary's and hasoon2000's sticky into this as a Pre-root and Technical FAQ. Mine is purely Post-flashed and root and all I do is just monitoring threads to noticed common problems that newbies keep repeatedly asks and add them in here - hopes to saves Devs, Themers and Geeks from wasting their time on all too common jokes/headaches
antiquezip said:
I'll need to do some research on how to use the code to shorten a link ([a href .. something, I forgot, haven't using it for years on forum]. Tomorrow I will link yours, Binary's and hasoon2000's sticky into this as a Pre-root and Technical FAQ. Mine is purely Post-flashed and root and all I do is just monitoring threads to noticed common problems that newbies keep repeatedly asks and add them in here - hopes to saves Devs, Themers and Geeks from wasting their time on all too common jokes/headaches
Click to expand...
Click to collapse
just linked you under my sticky, under common problems
Bump for kernel flashing (Faux's 008 alpha 7)
I need help plese my HTC Amaze 4g can't turn on just get e screen HTC and tun off and when is off flash is triping like in that video plz watch
https://www.youtube.com/watch?v=_cEFSJQ3BqU
There is info: Ruby PVT SHIP S-ON RL
HBOOT-193.0002
eMMC-boot
Mar 15 2012,21:46:51
Related
I have an HTC HD2 and I'm on T-mobile. What I've noticed is that my phone doesn't ring sometimes and then I'll just get a voicemail notification (if voicemail was left). It's an intermittent issue, I've tested it several times from another line.
Does anybody know what the issue is? I did a search on Google and there seems to be a lot of the same issues others are having across other networks and other versions of the HTC but, haven't found a solution.
Thanks
i had never heard of this issue until yesterday, when my phone simply did not ring, then i got a txt asking why i didnt answer. very confusing. only seemed to happen once. i have done a lot of tweaks, so maybe ive changed something i shouldnt have. if it helps im using a generic, unbraded, factory unlocked HD2, with CleanEX DsE 3.5 and radio 2.11. have you tried re-flashing the ROM and seeing if that helps?
interestingly, i have noticed that my signal can be irratic at times, often just dropping for no reason, then coming back about 30 seconds later. i live in a full signal area, so i know thats not a problem. also my data connection will 'freeze' at times, where it shows its connected, but nothing is able to use it, i have to disconnect and reconnect, and this may take 2 or 3 attempts before it connects and is usable. have you experienced the same issues?
matthewharmon102 said:
i had never heard of this issue until yesterday, when my phone simply did not ring, then i got a txt asking why i didnt answer. very confusing. only seemed to happen once. i have done a lot of tweaks, so maybe ive changed something i shouldnt have. if it helps im using a generic, unbraded, factory unlocked HD2, with CleanEX DsE 3.5 and radio 2.11. have you tried re-flashing the ROM and seeing if that helps?
interestingly, i have noticed that my signal can be irratic at times, often just dropping for no reason, then coming back about 30 seconds later. i live in a full signal area, so i know thats not a problem. also my data connection will 'freeze' at times, where it shows its connected, but nothing is able to use it, i have to disconnect and reconnect, and this may take 2 or 3 attempts before it connects and is usable. have you experienced the same issues?
Click to expand...
Click to collapse
I haven't tried flashing the ROM, I've been hesitant on doing that since I feel like I might mess something up. I'm not sure how to either. I have SPB backup, so I would hope if I messed something up then I would be able to easily restore it.
I haven't really noticed any dropping, my call qualities have been good. I've tried to dial a number before and it might drop right then while it's trying to make the call. So, I'll redial the number but, once I'm connected I haven't noticed any issues with calls dropping.
Data connection has been working pretty good as well, I've been using the wifi quite a bit and not really had any issues. I don't have a data plan setup with T-Mobile so I just use the wifi. I don't know if using the actual data connection would give different results than using the wifi.
flashing a rom is really easy it's all autoinstall, just have to read carefully / look at the video's, there A LOT of them out there.
HectiQ said:
flashing a rom is really easy it's all autoinstall, just have to read carefully / look at the video's, there A LOT of them out there.
Click to expand...
Click to collapse
updating the rom may help, as it will also update the radio drivers. what i would suggest, if you dont have much experience in flashing a ROM is to have a look on the official HTC support site. on there it will give you a list of updates avalible for your phone. download the latest ROM for your phone (for me, this is WWE 1.66 with radio 2.06) and install that. any data on an sd card will remain intacted, but sync you phone with outlook and backup stuff like contacts, messages etc before you do it. i personally use microsoft myphone to do all that.
flashing the ROM with an official one is very straight forward, and as quoted above, its all auto install on the phone, and there are about 3 or 4 steps that you need to do PC side (this is all explained in the update program you download). i would give that a go and see if things improve, you will also gain improved performance, new features and better battery life with newer ROMs, so its worth doing
custom roms are a bit more tricky to install, but often offer more features and improvements over stock roms. if you need help with this have a search on the forums, there are lots of guides and help on how to flash with a custom rom
matthewharmon102 said:
updating the rom may help, as it will also update the radio drivers. what i would suggest, if you dont have much experience in flashing a ROM is to have a look on the official HTC support site. on there it will give you a list of updates avalible for your phone. download the latest ROM for your phone (for me, this is WWE 1.66 with radio 2.06) and install that. any data on an sd card will remain intacted, but sync you phone with outlook and backup stuff like contacts, messages etc before you do it. i personally use microsoft myphone to do all that.
flashing the ROM with an official one is very straight forward, and as quoted above, its all auto install on the phone, and there are about 3 or 4 steps that you need to do PC side (this is all explained in the update program you download). i would give that a go and see if things improve, you will also gain improved performance, new features and better battery life with newer ROMs, so its worth doing
custom roms are a bit more tricky to install, but often offer more features and improvements over stock roms. if you need help with this have a search on the forums, there are lots of guides and help on how to flash with a custom rom
Click to expand...
Click to collapse
I have a T-Mobile HTC HD2 (U.S.) and I went to the HTC site and on the download page for the ROM update it has ROM Version: 1.66.707.1. When I check the ROM version on my phone it is: 2.10.531.1.1 (82076) WWE
Also it says on there - Note: This update is not intended for use on T-Mobile(US) HTC HD2, and doing so may have undesired side effects.
So, I suppose I'll have to start looking into the custom ROM's.
ubaidabcd said:
I have a T-Mobile HTC HD2 (U.S.) and I went to the HTC site and on the download page for the ROM update it has ROM Version: 1.66.707.1. When I check the ROM version on my phone it is: 2.10.531.1.1 (82076) WWE
Also it says on there - Note: This update is not intended for use on T-Mobile(US) HTC HD2, and doing so may have undesired side effects.
So, I suppose I'll have to start looking into the custom ROM's.
Click to expand...
Click to collapse
good job you didnt flash that, the 'undesired side effect' of flashing that official rom (or any other non tmous official rom) on your tmous phone would have been a permanently dead phone.
im not sure about tmous roms, maybe have a look on the t-mobile us support site and see if anything is listed there. if you want to look at custom roms the first thing you will need to do is get hspl (the latest version is hspl3, which i believe is compatible with tmous). if you search on the forums you can find the official thread. this removes the security checks and allows you to install custom roms. after that you will need to choose a radio version. again search on the forum and find the latest one compatible with your hd2 (there is an official radio thread which i would look at). this normally comes with an updater program included, but if not, search for 'custom ruu' and follow the instructions on the thread. finally you need to pick a custom rom. there are literally 100s to choose from, with different features, looks, apps and even some android builds. personally, i use cleanex dse because of its speed and stability. im not sure if this is tmous compatible, so check on the rom threads.
alternativly, you could have a hardware fault with your phone, which will be repaired under warrenty, so you could go down this route. personally, i would do this first and see if things improve, as although custom roms can be uninstalled and the steps can be reversed, the warrenty is voided by using hspl and installing custom roms.
still have the problem? Might not need a hard reset. Try this solution here:
(LINK)
One of your programs might have deleted the "Volatile" folder, so
no Volatile folder => no WMPlayer => no MP3 playback => no ringtone.
Re-creating an empty "\Application Data\Volatile" folder usually brings it all back.
If it fixes the problem temporarily and recurs again, you might have to change the temp folder as outlined in the link above, or just install that CAB.
Hope this helps. If this solves your problem, please edit/add [solved] to your title.
atlaswing said:
still have the problem? Might not need a hard reset. Try this solution here:
(LINK)
One of your programs might have deleted the "Volatile" folder, so
no Volatile folder => no WMPlayer => no MP3 playback => no ringtone.
Re-creating an empty "\Application Data\Volatile" folder usually brings it all back.
If it fixes the problem temporarily and recurs again, you might have to change the temp folder as outlined in the link above, or just install that CAB.
Hope this helps. If this solves your problem, please edit/add [solved] to your title.
Click to expand...
Click to collapse
I did what u said and installed the cab but still the same problem. Doesn't ring sometimes
Plz if anyone had this problem and knows how to solve it, I'll be so thankful if you help me. It has been irritating me for a month :S
Same here...and its flooded in the net....still no solution..check this out and if anything comes to you...do pls let me know...
http://forum.xda-developers.com/showthread.php?t=850280
I have the same problem. Sometimes incoming call does't ring, altough the phone vibrates. I'm using an european HD2 with the original 1.48 rom. I didn't found the reason... the changed tweak... the influencing application installed. It seems happening randomly, I can get a call without incoming call ring and after a few minutes I can get a second call from the same caller with a normal ring.
Hi,
This update.zip is for Cm7 users having the problem, that if the screen goes off the phone reboots/goes off. Jerpelea has included a baseband folder into his updates and mentioned that the rom only works with this modded baseband correct, but if you use this fix please also flash the following ftf bundle with flashtool.
Requirements:
Cm7 by Jerpelea
Files:
435FW+bb52_from_bb-collection.ftf
Cm7_when_screen_off_fix.zip
Installation:
Flash the ftf bundle with flashtool
boot into recovery and flash the when_screen_off_fix.zip
boot into rom
Info:
Before saying: "After flashing this my phone only WLODs or FC's", please try a clean install first!:
Flash the ftf bundle using flashtool
Go to recovery
Flash the newest Cm7 rom
Flash right after the rom the fix
reboot
here you are
I AM NOT RESPONSABLE IF YOU BREAK YOUR DEVICE OR DROP YOUR COFEE !
Cheers,
L
good idea...
yea, i wrote a long reply in my other thread. With this solution i haven't to make always a new update.
@9Lucas5
Hey buddy, good idea on the thread, it will be easier to follow as this does not confuse the busybox issue for wifi fix.
Anyway, how about a instruction of use for the op also clearing up questions like do we have to flash them everytime a new cm7 release is out, what sequence do we flash these ie before/after flashing the rom.
Lastly Doomlord has been trying for weeks to find the cause of this issue, at my request, J & Z have given there thoughts, we all appreciate everybodies help with the fixes and input, i read your post and explaination and respect what give to our forum, i think doomlord was confused about the busybox issue and probally thought you knew more about the system bin/xbin, we will find a solution working together, thanks for all your hardwork.
The problem just started for me, I think it is because my batery went bellow 20% is this fix also for that or only for when it happens always ?
depulle87 said:
The problem just started for me, I think it is because my batery went bellow 20% is this fix also for that or only for when it happens always ?
Click to expand...
Click to collapse
I only know that my fix fixes the reboots appearing right after turning off the screen. I don't think that it fixes also this, but try it.
tried it and you are right it didn't fix it, I'm wrong here cause it just happened when screen on so it is the low bat issue not the screen off issue.
however your method did not break anything and for the first time my phone said it was booting into custom kernel
does this fix random wlod and reboots ?
ok, I'll repeat again. I don't know what this maybe is fixing too, but i think it's nothing, cause there aren't many files in it. There are only the miniloader and the splboot.ko in the update.zip. I only know and say, that it fixes the screen off = reboot problem. Other things, please simply try. If it fixes anything else you can post it.
Shouldn't be getting WLOD on This version!
I take it your using the loader that came with the main update.zip?
superleeds27 said:
Shouldn't be getting WLOD on This version!
I take it your using the loader that came with the main update.zip?
Click to expand...
Click to collapse
I'm using the loader came with z's incall volume fix kernel
Battery below 25% reboot.
depulle87 said:
The problem just started for me, I think it is because my batery went bellow 20% is this fix also for that or only for when it happens always ?
Click to expand...
Click to collapse
The below 25% battery issues got fixed for me when i reset the battery stats on the xrecovery. this got really fixed just doing that right after fully charging the battery. I think this most likely is the battery issue, because it one of the only variables between phones. The battery stats reset should always be done when the battery is totally full or very near that.
this patch saved my fathers phone - and so saved my evening!
thanks a lot! there actually ARE people out there with that screen off reboot issue.
i wonder why the xperia community seems to have less team spirit than i am used to (from other phone communities i participated in) - i would at least expect that this issue is mentioned and this thread linked on the first post of cm7 - i also dont understand, why various hardware issues are solved on various roms, but not overall...
like i said - this community is "different" to me anyways, thanks for solving this issue, giving my dad latest stable cm7 (including my personal work and taking care of this device anyways
regards
Download links no longer working so thread closed...
To allow Q&A to be separated from bugs/development - this is the Q&A thread for the I9100 Hellraiser found at http://forum.xda-developers.com/showthread.php?t=1335377
I intend to put FAQs here, along with keeping a list of tested ROMs. Keep general discussion here, and only use the other thread for bug reports and development.
In general: If it's listed as a known issue, and you don't have a fix, keep it out of the development thread. If you're not sure if it's Hellraiser-specific and common to multiple ROMs, keep it out of the development thread. In short, if you ask "Is this a bug?" in that thread, I will report it to the moderators. If you report a bug that is ROM-specific and not a Hellraiser issue, I will report those to the moderators starting tomorrow.
Tested ROMs:
I9100 XXKI3 Based:
SensatioN 1.8 by Crysis21 - Tested by myself with Alpha 0.2.1 - Fully working except 0.2.1 Known Issues, defaults to "good" AT&T APNs except for it has the "Broadband" APN which may cause the Tether Police to nail you if you tether. I suggest deleting that one.
VillainROM 3.0 + JKay Deluxe Themes v12 - Tested by myself with all versions, and my current "testbed"
I9100 XXKI4 Based:
CheckROM Revolution HD 2.0.0 - A few user reports indicate this may have WiFi issues when Hellraised similar to UCKJ2/J4 for I777
I9100 XWKJ2 Based:
CriskeloROM V30 + JKay Deluxe V12.1 - Reported by simpl3lang, seems to be working
If you have a report for a ROM, please indicate which I9100 firmware it is based on (XXKI3, XXKI4, etc.)
Also, I have seen reports that XWKK5 bases (like the latest CheckROM as of 1/8/2012) have the same issues with Bluetooth HID not working as UCKK6 - even when not Hellraised.
If someone posts a good, in-depth review of a ROM, I may link to it from this list. (Time permitting...)
Frequently Asked Questions:
Q: The home button lag is back, why?
A: The ROM has the annoying Vlingo double-tap support. Either smali it out (look for tips in the UnNamed ROM git repos, or look for a fix for that ROM.) - A commonly available fix may be flashing a JKay Deluxe Theme appropriate for the base of your ROM
Q: Home button haptic feedback is not working, why?
This is something that can't be "universally fixed" with Hellraiser. It must be modified in an individual manner for every ROM in android.policy.jar with some smali magic. It was the same deal with I9000 ROM ports to the Captivate.
Q: Where do I find themes/mods?
Look through the I9100 Themes/Apps forum for mods/themes appropriate to your ROM. Nothing I do in the Hellraising process should break any of these compatibility-wise.
i finally jumped on board and installed an i9100 rom. so far so good. im loving it. first install went smooth. root working and all. i dont know about battery life (my phone still plugged in while testing this out).
okay here is the rom ive installed "CriskeloRom V30-S-BAR-12/7-Tog-BLN-CallREC-Overscroll-7Locks-PWR-M-Esxt-(XWKJ2-2.3.5)"
http://forum.xda-developers.com/showthread.php?t=1168836
i have also installed JKAY DELUXE SETTINGS v12.1 <--great addon. lets you have multiple slide to unlock (AOSP lockscreen). option to remove home double tap. option to customize power options (extended). crt off/on animation. overscroll glow. all these options and more on this DELUXE SETTINGS app. http://forum.xda-developers.com/showthread.php?t=1154278
so far im loving it. this will be my rom for now. thanks ENTROPY for the great HELLRAISER.. you the man
edit: alright i have tried wifi tether. its not working. i know its mentioned in the known issues. the workaround doesnt seem to work for me at least ......i enabled changed ssid and password. but once i exit settings, it reverts back to borkness lol. any other workaround? thanks
Edit 2: nevermind i figured it out. I rmmbered i replaced the Settings.apk with one that has a theme i like. That borked wifi tether for me. I returned the settings apk i replaced, rebooted, and all is good
I just wanted to bump this to the top... this thread needs to be stickied! How do I ask a mod to sticky it?
Sent from my GT-I9100 using xda premium
Good question - I know in the Infuse section some ROM Q&As were stickied, but they don't do that in other forums.
Plus at least this is CLEARLY linked to from the main Hellraiser thread.
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
selfassembled said:
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
Click to expand...
Click to collapse
You must be doing something wrong... I am running 1.9 and have been since the test build.. I will post some screen shots in a moment
Sent from my GT-I9100 using xda premium
Here are some screen shots... check out my battery life ..
I did have it hooked to a computer while 1.9 downloaded and that's why you see that slight bump...
Sent from my GT-I9100 using xda premium
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
selfassembled said:
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
Click to expand...
Click to collapse
I had 1.8 flashed 1.9 on top without wipe.
Mounted system and data and then flashed hellraiser on top. And haven't had any issues.
Sent from my GT-I9100 using xda premium
An i9100 modem/kernel will NOT work, that's for sure.
In fact some of the behaviors you mention sound kind of like a classic example of accidentally running an I9100 modem. The rest sound like a classic example of not wiping or doing an improper TiBu restore.
I'll try to test tonight.
It may have been titanium backup, I also didn't remount before hell raising. I'll get it working if he did
Hi Entropy, do you have any idea why the tethering settings are not persistant?
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
amtrakcn said:
Hi Entropy, do you have any idea why the tethering settings are not persistant?
Click to expand...
Click to collapse
Not yet, haven't had time to mess with it yet.
selfassembled said:
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
Click to expand...
Click to collapse
Titanium backup always give me problems so I just don't use it anymore...
Have you tried a fresh install without titanium backup?
Sent from my SGH-I777 using xda premium
CheckROM RevolutionHD v3.1.1
I tried raisin' hell with CheckROM RevolutionHD 3.1.1 last night. This is an XWJK3 based ROM, and seemed to work fine. I was intrigued with the idea of having a kitchen in the ROM to customize it and wanted to check it out. Everything seemed to run and work ok. Home button lag and lack of haptic feedback were known and expected. There were a couple of things though -
1) The phone ran really hot. Like skin singeing hot. There was another post on the CheckROM thread that talked about the phone running hot. But I noticed the same problem with a hellraised VillainROM as well. So not sure if that is a hellraiser issue or a ROM specific issue. I do know about the media scanner crashing due to incompatible codecs between Samsung derived ROMs and CM7/MIUI, I didn't get a chance to see if getting rid of my media would fix it because of issue 2...
2) The kitchen app while great in theory, isn't quite there in practice yet it seems like. I tried installing a few mods from the kitchen, but a lot of times downloads failed. I tried installing the BlueMonkey theme from the kitchen and it caused the phone to bootloop. There are quite a few people talking about bootloops on the ROM page, so I am leaning towards this being a ROM or kernel incompatibility issue. I have never had bootloops or anything nearly as funky with any of the native I777 ROMs. I had to flash back to bone stock to recover. Thank god for Nandroids
So, I guess it is ok to the add XWJK3 based ROMs to the compatible list if Entropy thinks both of the above two issues are not hellraiser related.
I've never had heat problems on VillainROM hellraised.
I've been starting to hear that CheckROM 3.1.1 has a lot of issues with the kitchen app - as in 3.1.1 has issues in general. I've seen lots of comments about people sticking with 2.0.0 until it matures.
I only tried CheckROM VERY briefly - enough to confirm that wifi worked (as there was a negative report on wifi with CR 2.0.0)
I'll update the list later this week.
GingerMod
Thank you for this awesome tool, Entropy! You can add GingerMod (http://forum.xda-developers.com/showthread.php?t=1220283) to your list of XXKI3 ROMs that work well Hellraised.
I've quickly tested out everything I can think of from a fresh install (wipe everything, format/system) and no problems to report. Wifi tethering has the minor problem of reverting to default settings, but they work, so it's not an issue in the slightest for me. Default APN settings are the same as on UnNamed--ATT Phone and ATT WAP. Home button haptic works out of the box--I didn't do anything.
For those interested, some quick hits about this great ROM:
- Most Samsungyness removed, really convincing AOSP feel. It's not just a theme, it's rebuilt. Just a few niceties such as Camera, Browser, FM Radio remain. You can add back whatever Samsung features you want.
- Small, 1/2 size compared to stock ROMs
- There is no lengthy screen on delay during calls when removing phone from your face (present in UnNamed)
- Customizable via included "Extras" settings and JKay app
- Been stable for awhile. Over at the thread, you won't notice a lot of random issues or people clamoring for "fixes". It's just really complete.
Hi all,
Since i'm unable to start a thread in the android development forum I try here. Hopefully Arrrrgh won't get Arrrrgh'd at me for posting this..
I have a problem which I hopefully get support for. I have tried all Android roms for the touch pro2 which none will boot or get past the ACL bootlogo.
I've tried every imaginable way to get it working but all are resulting in a kernel panic. I tried the NAND versions and the SD versions but both options results in the same kernel panic.
First I thought it was the SD formatting problem but after trying 4 different sizes and brands I excluded this as a possible cause.
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
I'm able to pull logs i'm ready and willing to pass the logs for supporting this device. I've found a similar thread by Z!nk / Z1nk but he gave up on the device before the developers could get to it.
So hopefully there is a developer willing to add this version to the android roms.
Thanks for reading and hope to hear from anyone soon.
Cheers,
Alchedin
[edit] The device has security unlocked and is HSPL'd [/edit]
Alchedin said:
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
Click to expand...
Click to collapse
How can we correct you if you're wrong - you need to tell us what phone variant you have. There's a surefire way to know as well...
It's kind of the first question in the FAQ...
Either way, the fact that you can't boot either makes me think you have a clone. There was another fellow with a clone (perhaps the one you mentioned?) that was unable to boot XDAndroid because he didn't have the same hardware. If you run HaRET.exe with no startup.txt, what does it say?
Edit - Regardless, I would focus on one build and try to get that to work. FRX07.1 is probably the "simplest" from that perspective.
Edit2 - Also, you seem to indicate it's a kernel panic. Why no logs?
Dear Arrrghhh,
Thanks for replying.
Ok, looking at the faq it states my phone should be a Rhod100 (complete: NM8RHOD100) which seems, when googeling, to be some kind of T-Mobile version. At the moment i'm running a deepshining
I ran the rom without a startup.txt and it gave me the following message: Found machine Rhodium. Hope this is the info you needed?
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Will keep you informed since I'm not at home.
Alchedin said:
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Click to expand...
Click to collapse
Logs? How do you know it's a kernel panic? What kernels have you tried?
arrrghhh said:
Logs? How do you know it's a kernel panic? What kernels have you tried?
Click to expand...
Click to collapse
Hi Arrrghhh,
Attached are the adb logs, which I hope is the info you need. This is what I get when using FRX07.1 like you advised.
But I have three questions if i'm not too bold:
1. Did you advise this version because it's more thoroughly when it comes to finding a issue?
2. When looking at the logs, is there something wrong with sound or something?
3. I'm able to pull logs of NAND builds if you like? They seem to be more complete when it comes to information on boot.
Cheers,
Alchedin
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Alchedin said:
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Click to expand...
Click to collapse
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
arrrghhh said:
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
Click to expand...
Click to collapse
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
arrrghhh said:
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
Click to expand...
Click to collapse
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Alchedin said:
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Click to expand...
Click to collapse
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
wizardknight said:
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Click to expand...
Click to collapse
I used the same ts-calibration file that was created during the first boot of gbx0c. Like I stated earlier, I only replaced/removed the zimage, module and data.img file every time I switched kernel.
Should I also re-calibrate every time when switching kernels?
arrrghhh said:
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
Many thanks for your interest and pointers arrrghhh, I will look into kernel stuff and such, maybe i'll get some of it working :fingers-crossed:
I have little to no development/linux/android skills but I can at least try to learn it.
Cheers
P.S: In a earlier stage playing around with NAND builds I managed to use the boot.img of the CM9-ICS_X1_testbuild1 in combination with the CM7.2 of walter79 and got it running in landscape mode, if this worked for me I can go from there.
Bit by bit i'm getting a hang of it.
Alchedin said:
Should I also re-calibrate every time when switching kernels?
Click to expand...
Click to collapse
No, as I state in all my threads about calibration - once you get a good calibration file, save 15,000 copies of it and re-use it constantly. There's no need to constantly recalibrate.
Ok here we go, sorry for the big read..
I hope I can be as precise as possible. This is about the NAND builds i've tested.
I installed ICS like in my last post again and made a CWM backup of the whole phone.
After this I did a new task29 and reflashed everything till I got back into CWM.
This time I installed the OMGB stable release with the kernelpatch + gapps.(seems the most advised build) Factory reset/data/cache/etc just to be sure.
Rebooted the device and let OMGB do it's thing, thus resulting in a kernel panic - can not sync issue. This is clearly a default message on this phone which I am in peace with. (log1)
Now for the fun part, I had this ICS testbuild backup up earlier and only did a restore of the boot part. Cleared the data/cache/etc again and rebooted.
This time it just boots fine into OMGB... (log2) previous attempts resulted in a landscape layout which i wasn't able to adjust myself, but this time I got the portrait mode correct! The only part which isn't working is the keyboard and hardware buttons.
Seems the "default" startup process is hanging in the part of the AudioFlinger? I compared the 2 logs but I can't see anything really which normally would result in a kernel panic.
Attached are the logs for the default OMGB boot (log1.txt) and the ICS modified boot + OMGB system (log2.txt)
Is this still different from any other Rhod100 or just a small adjustment? If this is really unknown I will break the phone to pieces and give up on it :silly:
I'll keep this config on the phone a bit longer since data and phone is working.
Thanks for reading
Cheers
-No sound
[Update]
Made a finding myself, the problem for my phone lies within the libhtc_acoustic.so removing this file made NAND boot up for the first time on this phone. Now looking for a compatible acoustic replacement which generates sound.
Going to try copying/pushing the file from FRX0.7 to NAND CM7.2 and see what it does. Including replacing my csv's from WinMo in the /system/etc folder.
[Update2]
Installed CM7.2 2.6.27 version today and used the FRX0.7 aucoustic.so, which resulted in a perfectly working android without sound...
now going after the csv's, which I hope gets me sound.
arrrghhh said:
[snip]...
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Alchedin said:
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Click to expand...
Click to collapse
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
arrrghhh said:
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
Click to expand...
Click to collapse
The interesting parts were the updates I posted. I did copy the csv's from the WinMo earlier, which were instructed by you (using total commander and such), but can't remember if it did produced sound.
But then...
I switched over to NAND CM7.2 by Walter79 and replaced the csv's in the CM7.2 zip file at location /system/etc (audioparatable.csv etc.)
Also I used the libhtc_acoustic.so from here
And ADB pushed the .so into the /system/lib folder.
When running logcat I see that the csv's are used and the audio routing is ok, but still didn't produce sound. Thought there were some other locations were the csv's are stored which I will also replace with mine. But didn't get to that yet.
Just tinkering with files really.. that's as far as I can go since I'm no developer.
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Alchedin said:
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Click to expand...
Click to collapse
I don't know how else to phrase that...
Although, I might have misread your statement. I thought you said you replaced a lib from FRX07.1 - which wouldn't boot for you. GBX0C did boot, so it seems the new acoustic code actually helps your phone.
So now I'm not sure what the deal is. I know OMGB uses the new acoustic, and I was under the impression that the CM ROM did as well. Did you try GBX0*? Basically the NAND version of GBX0C.
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Messed_sensation said:
Hello everyone,
I am a complete noob and hopefully you guys can help me out. I have tried to wrap my head around all the new android terms and my head is spinning. Anyways, I was given a HTC Sensation 4G Z710a on the Bell network. I registered on the htcdev to unlock the bootloader and following the steps, I fail to get the token. I have tried on two PC's and my friend tried on his MAC. My friend thinks the reason it fails is because the phones software is not up to date. Is it possible that it cannot get the token because the software is out of date? We tried to update the software and it fails. The problem looks like it is due to the installation of a clockworkmod. I have tried using the factory reset and the the cwm to do a factory reset and nothing has changed. Other than this, it looks like the phone has S-OFF and is not rooted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
es0tericcha0s said:
Kind of hard for us to tell you if the issue is the software update, when you haven't told us which update it's on. However, since the phone has already been modded, and is S-Off, that means the bootloader is already unlocked so using the HTCdev website is not needed. You can just update via a custom rom since you already have CWM.
Click to expand...
Click to collapse
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Messed_sensation said:
Thank you for your reply with the good news. This is probably irrelevant now that you said i can update via a custom rom. Under software information: Android Version; 2.3.3, HTC Sense Version; 3.0, Software Number 1.35.666.1.
It looks like now I need to research how to update via a custom rom and which rom to get. (Update. I looked into flashing a ruu and my cid is SuperCID 11111111. As long as I find a ruu that is Pyramid TMOUS, it should be good?) I am exited to be getting rid of my junky iphone. Do you have any suggestions as to what rom to get??
Click to expand...
Click to collapse
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Thank you for all your help and suggestion:good:. I am now running the Android Revolution HD.
This is a huge change from my iphone 4.
es0tericcha0s said:
I would upgrade the phone to ICS via the RUU. I suggest this for 2 reasons - 1) so you can have the newest update and firmware as just flashing an ICS rom by itself will not be a good idea as you will have issues with the touch sensors and radios (touch screen won't respond and signal issues) and 2) so you can have experience on how to put the phone back to stock in case there's an issue during flashing a rom, or you need to resell it. Once you have the RUU and know it works, then flashing roms will be much less scary as there aren't many things you can do that would not be fixable by it. You can get away with just flashing the rom and the firmware as well, but I speak with many years of experience and 100s of phones under my belt, and I know that whenever I play with a new phone, I learn how to fix it first before I learn how to mod it.
As far as suggestions, I would start with something simple and solid like Android Revolution HD. See what you like and dislike and go from there.
Click to expand...
Click to collapse
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Messed_sensation said:
Here is another update, and I am not sure if you can help. I thought everything was fine with the install, but it seems like my mobile network is not working. I followed all the steps from http://forum.xda-developers.com/showthread.php?t=1098849 except I used Clockwork Mod instead of 4EXT Touch Recovery. I looked through all the related settings and even tried changing them, rebooting and seeing if it made any changes. I also even followed the steps a second time and got the same result.
Click to expand...
Click to collapse
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
es0tericcha0s said:
Is it just data or are you unable to make calls and texts as well? If it's just data, then most likely it is an issue with the Bell APN needing set correctly. If you don't get a signal or any connection to the cell towers, then you might not have the right firmware or radio. Did you update to the last update HTC put out for it?
Click to expand...
Click to collapse
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Messed_sensation said:
:good:You are good! It was just my data that was not working, and you were right on the money. After reading your reply, I checked my APN settings and adjusted them accordingly to what my carrier states. It is working perfectly now. Thank you so very much for your help. Take care.
Click to expand...
Click to collapse
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
es0tericcha0s said:
I do this kinda stuff for a living. Glad all is well. Enjoy your "new" phone. :victory:
Click to expand...
Click to collapse
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Messed_sensation said:
I have been getting around 12 hours out of my battery with not too much use on the phone. I am running the SebastionFM Kernel. I read that I will get better battery life on the Bricked Kernel. Can you tell me if that is the way to go? I am trying to dl the kernel to flash it, but I am not sure which file to download. http://forum.xda-developers.com/showthread.php?t=1256668. Also, when I flash the Kernel, Is it pretty straight forward or are there settings that I would need to choose.
Thanks again.
Click to expand...
Click to collapse
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
es0tericcha0s said:
Depends on which rom you are using... The developer of the kernel mentioned near the end of the thread that his kernels are a little outdated for the newer Sense roms that are out there, so you might need to proceed with caution. Whenever you are flashing kernels, you should both make sure you have things backed up somewhere safe (Google, your PC, etc) as well as make a nandroid backup in recovery before flashing. It's typically recommended to wipe the cache and dalvik cache before installing new kernels (since you are S-Off, S-On users need a slightly different path to upgrade...). You might look into why your battery life is not as good as it could be in it's current configuration first before changing major components such as the kernel. Look into Greenify to hibernate apps while the screen is off and something like GSam Battery Monitor or Better Battery Stats or Wakelock Detector to break down the battery stats and wakelocks as those typically cause the biggest loss of battery life.
Click to expand...
Click to collapse
I think it is my battery. I picked up an Anker and the phone is now at 20% after 21hrs. Is there a way to get Emoji to work on my phone? When people SMS me, on the lock screen they show up as a question mark in a box but when i go to read the text message there is nothing there.
Using a different keyboard will let you send Emojis, but not really sure about enabling the view from other people's messages off the top of my head, sorry. I recommend SwiftKey for a great keyboard replacement with lots of built in Emojis.