I have been a long time Cell phone modder, and I have just gotten my first Android Phone, the HTC Evo 4G.
I have been reading androidforums.com and these forums for about a week now trying to get my head wrapped around things, but I still have some lingering questions.
I feel I have a good grip on how to get my phone rooted/nand unlocked, but its the what to do after that, which bothers me.
What I would like to accomplish:
More customized look and feel
Better battery life (without disabling half the features of the damn phone)
Free Wifi Hotspot
Removal of the pre-packaged crapware
Froyo
What I would not like to lose in the process:
Any of the phones functionality, including GPS/4G/Camera/Video/Bluetooth/etc.
Nice features that Sense has, such as Facebook contact syncing
Reliability or usability of the phone in general
As I have gotten older, my desire to mod has become less and less, and I get more tempted to just leave the phone alone and wait for OTA updates to come out, but when I just tried to do the wifi hotspot and learned I would have to pay an additional $30 on top of the $10 "premium data access" I made the decision to root. That being said, I don't want my phone to be something I am flashing every day. I want it to be as stable as possible so that I can get it all set up how I want without having to worry about re-flashing and losing all my data week after week to keep up with bugfixes and such.
What I don't understand is the differences between all the roms. The opinion at large seems to be that CM6 is the way to go, but it seems a lot of stuff is broken in CM6 atm, like 4G among other things.
Since this is my first android phone, I am already getting used to the Sense UI, but I have seen some other peoples home screens that just look amazing.
I guess what I am looking for is some advice, or a bit of a rundown (since I cant find all of this information in one place) about what is the best course of action to get from point A(stock phone) to point B(customized rooted phone which is "stable") over a path of least resistance.
Thanks in advance!
[also making this same post on androidforums.com]
You can accomplish everything you mentioned except froyo. If you do not want to lose any functionality then flashing a froyo rom is out of the question right now because they all have small issues. CM6 is a froyo rom.
The difference between roms is some are based on 2.2 (froyo) and others are based on 2.1 (stock for evo). Then they also differ in terms of what comes pre-installed, some remove all bloatware even sense and others do not, and then there are some in between. Any rom based on 2.1 will likely have everything working. I can tell you from experience that Damage Control and Backed Snack worked very well on my phone. The best thing to do is just try them out. Once your phone is rooted it is very easy to switch between roms.
Lastly the easiest way to achieve root is using simple root program which can be found here: http://forum.xda-developers.com/showthread.php?t=720565 (that link is assuming you have latest OTA update, if not search for simple root and you will find the one pre update)
try dc 3.2.3 very stable release(has all the features working; 4g, camera, ect) and has good battery life(don't need to disable half of your phones features), it also allows for a lot of customization(DCupdater allows you to download themes and flash them straight from your phone), and you can pick and choose what bloatware to remove using DConfig, a froyo release is suppose to come out sometime this weekend.
Another option for you is to root and then flash the latest rooted "stock" rom. then flash the latest radio and wimax. then you can use a file manager to remove bloatware. I use "root explorer" from the market. be careful what you remove as removing some things can cause problems. I am currently running this on one of my evo's with no problems everything works and battery life will get me through a day. if you need more info as removing the bloatware feel free to pm me and ill help with what i can. I'm sure using the stock rom will be sufficient for you. On the phone i have running i have all features enabled and am pushing my pop3 accounts through gmail, 4g wifitether, all works just fine.
First I would like to give credit to everyone who has worked on GBX0* in any way. ACL, arrrghhh, detule, and Stinger22 to name a few important faces around here. I do not take credit for 99% of this. It is a modded version of the GBX already published on XDA.
Stinger22 is responsible for building the killer new kernel. I packaged the kernel into a boot.img and collected all the compatible updates into a single installable Zip with lots of tweaks.Stinger22 deserves big thanks for his work here.
There will be limited support for this build. Feel free to ask questions, and even better if you can help answer them. If you know how to fix something that is broken I would love to hear from you. I would be happy to include anything that you can contribute.
Due to the number of people unhappy with the RHOD100s phones and this rom, we do not recommend it for the RHOD100s (not that we ever did as we only have RHOD400s to test with).
New install guide.
Now what you came for:
GBX*
Includes:
GBX 5-8-12 lib update.
Slightly smoother boot animation used.
Build.prop tweaks.
Added a couple of ringtone/media sounds.
Superuser replaced with SuperSU .97
Modded audio.conf file to allow for the streaming of media metadata from apps like Pandora when the advanced menu / car bluetooth mode is enabled in the app. Also this change should allow for more Bluetooth devices to connect to the phone. Does only appear to support AVRCP 1.0, so no metadata without extra app support. However track forward/back/pause will work with some setups.
Added circle battery icons with %s for more precise gauging. Shows in 5% blocks. What you see is +/-3% of what the battery is really reporting. Based off the themes here. It is better than a half filled bar IMHO. It might take a full discharge or two before the battery gague/acl code becomes accurate. The battery also tends to drop quickly in the first 10% and then levels off.
RHOD300 keyboard fix. Credit to Detule
Changed RHOD100 from default keyboard to RHOD100_UK keyboard map.
Fix to ramdisk to resolve error reported during boot.
Fix to bluetooth main.conf to prevent bluetooth media devices from crashing OS. *only included in the 3.4.26.1 and newer full build*
-Still have issues where connecting/disconnecting the sink device can sometimes cause the phone to reboot. Seems sink device dependent. Mostly fixed in 3.4.26.13
Fixed bluetooth typo bug to 3.4.26.1 in 3.4.26.11
Boot animation in 3.4.26.13 credit.
3.4.17 Kernel update:
Including ACL's newer battery code.
More accurate readings from battery gague.
Maybe slightly better sleep battery usage.
Small Bluetooth fix (I find paring to be easier).
Kernel panic fix that may help prevent phone lockup if apps crash.
Many other small patches.
Fixed USB detection issue in 3.4 kernels.
Overclocking still supported. (SetCPU is free to XDA members)
Added a hack supplied by detule to prevent the sd card reader from suspending to prevent unexpected sd card removal errors.
Added a kernel splash screen to cover up some of the rolling text during boot time. Credit.
Sleep works with wifi turned on. - Battery life should improve where wifi prevented sleep before. Wifi tethering will prevent wifi sleep.
Zoom slider bar now works. Acts like a two finger touch moving from the center of the screen. If you tap on the zoom bar it will be just like tapping in the middle of your screen. Something to keep in mind if you get unexpected touches while holding the bottom of your phone. More benefit than a draw back IMHO. Added permission files. Link at bottom for those who just need this (based off of mankineko's work).
3.4.24 Kernel *minor update*
Includes updates from source.
Added code to cause system to reboot rather than hang from a system crash.
3.4.26 Kernel
Reboot function in shutdown menu has been fixed (power off is still broken)
Host file is no longer over written on boot up. This had been preventing ad blocker apps from working correctly.
ACL's panel code has been used. Hopefully this will resolve some issues for the RHOD100 users. We have no way to test, so it is as-is.
Auto brightness has been fixed. You may need to press the power button and force the lcd off, after it has been enabled, before it will take effect.
Device name is no longer reported as 00000000 by ADB. It should show as the serial number.
3.4.35 Kernel
Slight performance tweaks.
Added CrossBreeder mod. Basically helps tethering internet.
Added "Smartassv2" cpu governor. Can be set using apps like SetCPU. Should be slightly better performance, but may come at the cost of battery life.
Added "row" scheduler.
3.4.41 Experimental Rhod400 Kernel.
Shutdown working
Fps limit fixed, plus a slight gpu performance boost (previously was benching about 19fps for both 2d/3d, now I'm getting up to 60fps 2d, 26fps 3d)
Enabled more compiler optimizations. Kernel is slightly larger, but seems to perform a bit better
USB: No need to plug/unplug once before adb works, faster cable connection detection
Other miscellaneous tweaks that may or may not help battery life
Known bugs:
Many of these bugs are found in the 3.X kernels, and so they may be found here too.
MMS does not work out of the box. Add this APN info if you want it.
Google maps newer than 5.9 shows graphic distortions with street names, and other graphic issues sometimes. Waze is a good gps alternative if you want something with more features.
Shutdown and reboot options on the power button menu do not work.
Auto backlight does not work.
8-15-12 RIL update breaks radio (on CDMA for sure/no reports from GSM owners).
SD card unexpected removal errors when the phone wakes from sleep on *some* phones. -try a non SDHC sd card if all other standard troubleshooting fails. I have been able to use a 512mb and 1gb card micro sd card without issue. However all my 4,8,16, and 32gb micro SDHC cards have this issue. Hacked work around as of update 3.4.17.
May have to remove and reinsert USB cable a few times before the phone will recognize it has been plugged into a data port. Also you may need to turn features on/off to get the correct tethering/usb storage/usb debug to work correctly.
No front facing camera support for RHOD100.
Deleting bluetooth.apk may be necessary to get the phone to connect to some Bluetooth devices that have any advanced features.
If Bluetooth is left on and the phone is rebooted/crashes, the unit may bootloop. I have not found a fix other than reloading the Rom from recovery.
This bug seems to effect A2DP and other audio streaming devices the most v.s a bluetooth mono ear piece for calling with. This is a bug I have been able to repro on the GBX*+ 3.3.6 kernel as well. Make backups before using Bluetooth. If you are a CDMA user, you could try the original Ril from inside the GBX+3.x rom. It seemed to cause the reboot loop a little less. However GSM users must have the 5-8 Ril to use this Rom.
Found that this bug seems to be for devices that support multiple profiles. I have a Bluetooth receiver that will use phone and media profiles. If the phone profile is disabled the lock-ups do not happen. This work around will not let you use the phone features, but you can stream media. You need to pair the device. Then long touch it to get a to an options menu. Uncheck the phone profile option to stop the crashes when playing any media.
Sometimes if the phone locks up during the boot animation from this issue, then you reboot once or twice, and leave it alone for a long long time it will sometimes finally finish booting. It is worth a couple of reboots, and a lot of waiting vs reloading the rom. It also seems to help if you plug the phone into the usb on a computer after the boot process has passed the blue screen.
Pandora's internal/advanced bluetooth settings must be turned off, otherwise it may crash the phone on device disconnect.
Bluetooth is not 100% stable, and may crash the phone on connecting or disconnecting devices. During use it is stable.
If the phone crashes while bluetooth is turned on it may boot loop. If this happens connect the phone's usb port to a charger or usb port on a computer. This should cause it to boot correctly on the next time around.
Sprint phones must be activated on the Sprint network in WM before loading Android. Android can not activate everything correctly.
It has been reported that the keymap for the RHOD300 is not correct.
Not an Android bug, but Sprint DNS services are crap. I found good working links not working correctly due to bad dns info. Of course you can use any public dns server you like.
A suggestion for getting your own dns in more easily is this App.
If you tether on Sprint I suggest that you put your own DNS server in under the TCP/IP settings on client device as it will only use sprint's by default. I leaned this the hard way.
RHOD100 WIFI may not reconnect to access point automatically upon waking from sleep. Disable and reconnect to work around.
This Rom was only tested on the Sprint TP2 RHOD400. It will probably work on any that worked with the GBX0* + 3.3.x kernel, but we can't promise it.
Updated RIL from Skysoft here. Not included in any build. 4-16-2013
Full Downloads:
GBX0*+3.4.17 Full.
GBX0*+3.4.24 Full
GBX0*+3.4.26 Full
GBX0*+3.4.26.13 Full *feedback on if Bluetooth is still crashing the phone after a clean rom load would be interesting.*
GBX0*+3.4.35 Full
Kernels:
3.4.26 Kernel update.
3.4.24 Kernel update.
3.4.17 kernel update.
3.4.35 kernel update.
3.4.41 Experimental Rhod400 Kernel.
If you download please hit thanks at the bottom and/or post feedback. I'm curious as to how many people are downloading.
New install guide.
Old install directions for all other NAND roms.
It is assumed that you have unlocked your phone. If not read here and/or here, and/or here.
If you are running the 8-15 ril that was patched, and you are unable to get a cell signal, I would highly suggest that you install the older patch ril file.
If you want to add just the permission files for the zoom bar (and a few other things) rather than downloading the whole thing again here they are. When I did this it broke Zeam. I had to add another launcher, and then switch between the two. That fixed it for me.
As always BACKUP, BACKUP, BACKUP before doing anything. Please use at your own risk.
*Related goodies*
Gapps package.
For those of you who want an ICS facelift, check out the modded Zeam launcher.
Most recent recovery thread. - this recovery creates a md5 error on a backup's restore. Anyone know how to fix it?
ACL's known good recovery.
Good chance you will need to calibrate your touch screen. This thread covers that,and how to make it stick.
I may have found a launcher that is more lightweight than Zeam from what I can tell. I am running Lighting Launcher, and am quite happy. Seems to have an even smaller memory footprint, which is great for phones without much memory.
Swapper2 app. This is an interesting thing I found the other day. It allows you to use your SD card for swap (Virtual ram). I did verify that a 64mb swap file (did not test swap partition) can work on our phones. I would love to hear some feedback from people who might be interested in playing with it. I would suggest a Micro sd card with a high random read/write speed. Here is a guide that is already made if you want to use a swap partition rather than a swap file. It will probably wear out your sd card faster, but sd cards are cheap these days. Also note that SD storage vie USB may not work if you use this mod.
Update.
I got out my 32gb high random speed sd card today, and I whipped up a swap partition according to the guide above. I bumped the swappyness setting to 100. I was in a generous mood, so I lopped off 1gb of space for swap (256mg would have probably been a better choice). I did get a name error when I enabled it, but it seemed to work just fine. The swap space of 1gb showed up by the free command, and the swap space showed use after I ran a few apps. It is a subjective observation, but I think multitasking is a little smoother. I plan on leaving it setup like this for now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did manage to max out the cpu, and crash the system resulting in a reboot. I was running two gps apps, and two music apps, and two or three other apps all at the same time (abit poorly though). It might not have liked having multiple apps access the same resources.
Here is a handy app for rebooting the phone quickly, and entering into recovery.
Possible way to disable the proxmity sensor for people who have bad ones causing a non-waking screen here. Credit.
*Bonus for Sprint RHOD400 TP2 users*
If you are tired of the white HTC splash screen here are two nbh files you can flash just like a rom from the SD card. They should only touch the splash screen. Everything else is left alone. Flash one, or both in any order. These probably work on other Rhod phones, but I have no way to test them. So no screaming if something gets bricked. Based off the work in this thread. Reported not working on RHOD100 by this post. Reported working on RHOD300 here.
If you know of an image (480x800 res) that is even more amazing than these, and you feel it would be a good replacement drop me a link to it. If I love it, it will make it to the first post. Otherwise I might just whip one up special for you for contributing.
Primary
Secondary
As of 3-25-13 I have moved onto the EG4G/SII phone after reading about it and SERO legacy at Howardforums.
I will stop in from time to time, and if I am given a newer kernel I will post it. However I will no longer be using this phone.
So long, and thanks for all the fish.
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Slipdoozy said:
i tried a lil last night and today on your lite version. had a few issues with it but i think that was caused by my mistake. i know you said NO support with the lite version. so later on today im gonna try the "full" one without any of my added stuff.
thank you for your time in putting this together for us and everyone else who kept this old phone working so long.
edit: i have rhodium 400 btw
Click to expand...
Click to collapse
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
wizardknight said:
You are welcome to ask questions about the light version. Just don't *expect* any help with it. If I know the answer I will respond. Sorry if I came across as stern. Someone else might know the answer too.
I wanted to set the tone to be caveat emptor (to quote Stinger22). As the lite version is missing a whole lot it might be broken, or broken by anything. It is just something I whipped up to play with, and decided to share incase someone else wanted to play.
I am glad to keep up the fight. These are still great phones, even if they don't play the newest games.
Thanks for your comments.
Click to expand...
Click to collapse
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Slipdoozy said:
hi again. i did the lite version again with my tweaks... meaning i hate using goole play or any of the google apps in general (privacy concerns deleted apk's after flash and successful boot).
im currently using it on my rhodium without service (have two, one on sprint service). so i cant confim it works in those aspects. wifi works otb. didnt try blue tooth. camera works as expected. didnt try audio/video yet (we all know rhod dont have HW support lol). miss the keyboard but can install if needed. couldnt for the life of me figure out how to use the modded zeam you suggested (not a deal breaker i like the orginal one). decent battery life but not what i expected. phone went from 8 hrs @ 70% then down to 10% within next hour. turn off dont work so well sometimes it wrks most times not. on [ACL]'s rom ive been using app called "quick boot" to bypass this goofy activity. works like a charm from widget.
can this be reworked into a gsm phone? kinda know i need to security unlock. but what im getting at return to winmo, change security, finda gsm phone provider, reflash this rom and good to go? or just skip those crazy ideas lol?
again thank you for the rom you shared with us :good:
Click to expand...
Click to collapse
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
wizardknight said:
Most of Google's stuff was left in place because more people than not consider accessing the Google account info critical. Even if only for contacts and such. Matter of personal choice I say.
I cut the keyboard APKs as we have a physical keyboard. You can just side load them or put them back in the install zip. I am using the ICS keyboard from the market. I like it better for my virtual keyboard with a stone bold theme.
This is based off the GBX* rom, so it should probably work with the GSM variants of the the RHODs. I didn't dev the new kernel, but it should work. You could try the most recent ril, but I know it breaks cdma phones. The most recent ril had a GSM signal loss tweak in it. I don't know of any security you need to deal with, and I can't recall coming across any comments in the original GBX* thread about that.
If you are talking about unlocking the sim so you can use a CDMA device on a GSM network, that is unrelated to the rom for the most part.
If you are running the lite version I posted, just uninstall Zeam with something like titanium backup, and replace it with the apk that is linked.
Otherwise you could swap it out in the zip file before you install. It is located in /system/apps.
If you manually delete the apk from the phone /system/app and paste the new one into it's place while Zeam is running it will probably require a reboot before Zeam works. Probably not the best way to go about it assuming nothing explodes.
If you can't get it to work I can make up a version with the other ICS themed zeam.
Maybe that will help a bit.
*edit*
Been fooling around a little with the modded Zeam on the lite version. For some reason it doesn't install the icons right if there is not a non-zeam launcher running. *shrug*
I installed launcher2 apk from the full rom for the install. Then was able to side load the modded zeam.
*edit 2*
I posted an ultra lite rom with the classic launcher.
Click to expand...
Click to collapse
im not happy with google selling my info so i refuse to give them any space on my phone lol
i tried the modded zeam all the ways i could think of, before flash, after flash, through adb didnt matter. maybe corrupt apk?
no worries. ill try to redownload it and try it your way with launcher2 first
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Slipdoozy said:
i tried the modded zeam all the ways i could maybe corrupt apk. before flash, after flash, through adb didnt matter.
no worries.
~unlocking the sim so you can use a CDMA device on a GSM network... yeah im not looking forward to paying to sim unlock it
but i am hella glad you got the zoom bar working :good:.
Click to expand...
Click to collapse
Be ok with loosing the money. Some people have reported that they didn't get the unlock info, and the dev for that is next to impossible to get to respond.
You might check this thread. Not sure if they got it working.
Most of the credit goes to Stinger22. The man is kicking some serious code butt!
I would try re-downloading the apk. I was able to install it with a adb install. Not sure what else it could be. Did you hold your tongue just right while dancing madly during the install?
Slipdoozy said:
im not happy with google selling my info so i refuse to give them any space on my phone lol.
Click to expand...
Click to collapse
You do realize where Android is coming from... Right? lol
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it... Glad it did not get forgotten!
Zoombar!!
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Caldair said:
Wow. Great work! I can't wait to try this when I get back from vacation.
If someone asked me to make a list of features I wanted to see in android on the rhodium it would go something like this:
1 Zoom bar
2 Zoom bar
3 ZOOM BAR!
Seriously never thought I would see it happen again though, so one more time; Great Work and Thank You!
(Sorry, I just didn't feel that the 'thanks' button alone was enough this time :laugh
Click to expand...
Click to collapse
HAHA. I didn't think the zoom bar would be the selling feature of this rom, but I am glad you are happy.
arrrghhh said:
Regardless, kudos on getting the zoombar to work - I was hoping someone would take mankineko's work there and adapt it.
Click to expand...
Click to collapse
Didn't know who did the base work. - Gave credit in the post.
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
CodaHighland said:
Oh sweet, the zoom bar works now? I'd been hoping for that one. XD It's a shame I've moved on, but I may pull out the ol' TP2 as a backup device.
Click to expand...
Click to collapse
Wow. I had no idea that the zoom bar was so popular. Just doing what we can to keep the phone going.
Thank you so much for your hard work (especially fixing zoom bar!!!.)
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
Yes, overclocking is supported. This should be the same as 3.3.6. I believe the frequency range you can choose from is 122-825. Download your favorite overclocking app from the market, and have at it. I use quick cpu overclock lite.
*edit. I think we have some new governor options. Link for descriptions.
karimkahale said:
I have one question, does the kernel supports overclocking, and if yes to what frequency?
Thanks
Click to expand...
Click to collapse
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Slipdoozy said:
i havent tried to OC past 710 on my rhodium 400. but ive never been able to stay stable much past that on any rom. cpu jus freezes up past that on this phone for me.
Click to expand...
Click to collapse
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
wizardknight said:
710 is a respectable overclock. As all overclocking is concerned, YMMV. No one has a way to predict the speed you will be able to overclock to successfully. You might try reading this or this thread if you want to be educated on overclocking the TP2. Overclocking is usually 99% hardware limited. The rom you run is not likely to have much influence.
Click to expand...
Click to collapse
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Slipdoozy said:
oops i do have a addon to this... i have two rhodium 400's both are sprint versions. the one that doesnt have have service is the one i test roms with. i believe it is an early made phone and thats why the limit of OC is kinda low. i can do 729 and 748 sometimes but why risk the ~40 mhz for stabililty (app i use is setcpu and this GBX0* rom). now the second one i have was a referb one and does have service. build date is much later and i can OC it over 800mhz but i usually only set it for 787mhz. again why risk the ~20mhz for stablility. (same setcpu but [ACL]'s OMGB rom). basically i agree with wizardknight its HW limited and the luck of the draw.
goodtimes guys!:good:
side note: (related to second rhodium, first one works fine with zoom bar) any way to port this to acl's rom? i used the flash from OP but the zoom bar is no go. heck idk if the zoom bar even works on this phone. guess ill be doing a flash dance on the one the zoom bar works. wizard i know it not your rom jus thought id ask again thank you for putting this together.
Click to expand...
Click to collapse
I am assuming that you mean OMGB by ACL's rom. To the best of my knowledge there is no way to port the feature without building your own kernel. It is my understanding that the 3.x kernels (what we use) are not compatible with that rom. OMGB userland is no longer receiving updates, so unless another dev adopts that rom it will never work.
I will take the 1% credit for this rom. I have done behind the scenes, packaging, some Bluetooth mods, and testing stuff. The other 99% goes to everyone (esp Stinger22) who has worked on it before me or with me.
On the phone that the zoom bar is not working, did you download that rom zip before or after 11-3? I didn't change the file names or links with the last update. You might try downloading the perms file at the end of the post, and installing that. Otherwise I would re-download, wipe, and reinstall.
If you are still having trouble let me know, and I will go check the zips to make sure that something didn't get busted in the last round of updates.
Hi, I am a new owner of OnePlus 7T, I bought it used yesterday, and it runs Oos 11.0.1.1HD85BA
I'm pretty happy with it although I've noticed some overheating when playing games (just 10 minutes of geshin impact or dead cells), when scrolling tiktok or yt.
In general with average use, with about 5/10 minutes of gaming at most, the battery reaches 15/20% in the evening. I think for an used phone it's good? Or for OP standard is not so good?
Another bug I've noticed is the inability to launch the task manager at times, some inaccuracies in gesture handling, that is pretty imprecise, also I've notice that sometimes notification when the screen is off are not so precise. So I thought:
Do you guys think it's better to go back to Android 10? (if possible, i've read that most of OP user loves OOS10 more than 11) Or is it better to wait for more hotfixes for 11?
I do not know the oneplus world so I rely on you, I've already installed all my apps and backup from my old phone, and If I have to format I won't continue to organize my things.
Just one things: if you have some optimization tips, or something to do when you first have the phone, please tell me... I don't even own a AMOLED display before and I've read that it could become green!!!! What can I do to avoid this problem?
Thank you all in advance
Reset all data
If above does not fix then unlock bootloader, root, install Dora kernel latest, sdcardfs version