IM NOT RESPONSIBLE FOR YOUR PHONE:IF YOU DO THIS AND IT BREAKS IM SORRY BUT IM NOT RESPONSIBLE
http://forum.xda-developers.com/showthread.php?p=5123531#post5123531
I'm done this to my Eris but I didn't benchmark before (and I still haven't done a speedtest after lol)
I can tell you I haven't broken anything so it won't ruin anything to try it. Just simply edit the build prop with these values (acording to Amon_RA) but this is just for the Hero, I don't know how it'll work on the Eris.
Two of these values should already be in your build prop:
Credit goes to Amon_Ra for specific values:
Code:
ro.ril.hep=1
ro.ril.hsxpa=2
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
ro.ril.hsupa.category = 5
Anyone who knows more about this, can you give some input?
To edit build prop open up the command prompt to your tools:
Code:
adb remount
ADB pull /system/build.prop build.prop
This puts it in your tools folder.
Open it in notepad or wordpad and input the values listed above, I suggest checking that they aren't already in there.
Save and close it
command prompt to tools with this input:
Code:
adb push build.prop /system/
Reboot
I really only know what some of those have to do with... a lot of them don't mean anything to me.
Some people reported some serious speed increases, in the topic I saw up to 4x the speed.
Be sure to backup your build prop file prior to modification..
Sent from my FroyoEris using XDA App
I might be wrong, but most of those don't look like they would have an effect on our device (since we operate on a different technology than the MT3G).
Hungry Man said:
I really only know what some of those have to do with... a lot of them don't mean anything to me.
Some people reported some serious speed increases, in the topic I saw up to 4x the speed.
Click to expand...
Click to collapse
Who exactly is, "some people"?
Code:
ro.ril.hsxpa
ro.ril.gprsclass
ro.ril.hsdpa.category
ro.ril.hsupa.category
Those are for GSM related, have no effect on CDMA
Who exactly is, "some people"?
Click to expand...
Click to collapse
In the Hero thread.
Those are for GSM related, have no effect on CDMA
Click to expand...
Click to collapse
Good to know.
I might be wrong, but most of those don't look like they would have an effect on our device (since we operate on a different technology than the MT3G).
Click to expand...
Click to collapse
I sorta figured but is there some way similar to apply this to CDMA?
Information you're seeking for... I'm not well verse in this.... however, Android was orginally designed for GSM network until version 1.6 they've offically start supporting CDMA.
It'll take quite bit of research, I would suggest start digging around at android developers http://developer.android.com/index.html which is good starting point.
interesting. looking forward for updates!
firestrife23 said:
Information you're seeking for... I'm not well verse in this.... however, Android was orginally designed for GSM network until version 1.6 they've offically start supporting CDMA.
It'll take quite bit of research, I would suggest start digging around at android developers http://developer.android.com/index.html which is good starting point.
Click to expand...
Click to collapse
That makes no sense being that the eris is CDMA and originally ran on 1.5
So, I wanted to give this a shot, but did not have any luck with being able to open the .prop. Then the light bulb flashed and I got the idea of changing it to a .txt file (after copying it of course...) and that worked. Just a heads up for some people who aren't 100% computer savvy.
PS. Now that I edited it, I resaved as build.prop but I'm not sure that it will stay in the correct format. Anyone have any ideas before I try to push this back to my phone and mess it up? heh...only 75% computer savvy here it seems.
es0tericcha0s said:
So, I wanted to give this a shot, but did not have any luck with being able to open the .prop. Then the light bulb flashed and I got the idea of changing it to a .txt file (after copying it of course...) and that worked. Just a heads up for some people who aren't 100% computer savvy.
PS. Now that I edited it, I resaved as build.prop but I'm not sure that it will stay in the correct format. Anyone have any ideas before I try to push this back to my phone and mess it up? heh...only 75% computer savvy here it seems.
Click to expand...
Click to collapse
Instead of changing the extension, right-click and select "Open with..." and then notepad or whatever. Then .prop files will always open with Notepad.
Thank you for the advice, but that isn't an option that I have. My only option to open with is Open and there is not a selection for Open With... When you select Open it says that I don't have anything installed that will read a .prop file, which is why I had to change the extension to .txt. Running Windows 7 Ultimate.
PS. Nevermind, figured it out. I just recently started using Windows again after a long stint with Linux, so still getting the hang of some of the smaller things.
I know I am nub to this forum, but have years of experience in CDMA/UMTS technologies...these values will not support the eris.
For UMTS most definitely as the device was probably shipped CAT6/7 and now your adding HSPA CAT8 to the device giving higher down/up link tput capability.
So anyone see any changes to their 3g connection speeds??
Sent from my Eris using Tapatalk
vash8806 said:
So anyone see any changes to their 3g connection speeds??
Sent from my Eris using Tapatalk
Click to expand...
Click to collapse
No because this doesn't apply to our phones.
Related
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
seansk said:
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
Click to expand...
Click to collapse
anyone? please???
seansk said:
anyone? please???
Click to expand...
Click to collapse
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
frodoboy said:
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
Click to expand...
Click to collapse
Yes thats exactly what I did in root explorer in sys/camera_led_status/low_cap_limit, I set it to 5, 1, 0, did not make any difference. Also Its retarded that you cannot use flash while you're in a call....if you talking to someone and trying to take a picture it says you cannot use flash since you're in a call....wtf does that have to do with the flash!!! There should be a file somewhere in the sense UI system to change these settings, If anyone has found anything please share...or if you can think of something please share as well...
I actually like the dialer and contact aspect of sense UI and how it integerates and automatically finds linked friends, how it updates friends status in facebook and twitter, (although they still need to integrate google plus)...all the other stuff of sense I do not like...I've changed to ADW ex...and widget locker...
I doubt there's a way to get that stuff with a senseless rom since its so integerated into the system...If there is I would flash another rom in a sec and just install that aspect of sense....
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Binary100100 said:
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Click to expand...
Click to collapse
you gotta be kidding me!!!!
question 1. Are the other roms the same?? I"m unlocked and rooted but on stock rom. do senceless, beastmod or revolution have the same problem...I'm guessing they would since they use the same camera apk...or maybe not, If not i'm flashing to something else RIGHT NOW.
questions 2. are we ever going to see CM9 on the amaze....screw sense I want ICS AOSP asap...
seansk said:
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
Click to expand...
Click to collapse
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
frodoboy said:
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
Click to expand...
Click to collapse
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
seansk said:
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
Click to expand...
Click to collapse
I would suggest in the forum that consists of the kernel that you are using.
Example:
If you have QuikSense then post the request in the QuikSense forum or PM the developer (in this case xboarder56) directly.
If you use Faux's kernel then post it in that thread.
No need to start a new thread for a request. However if you feel that it is absolutely necessary do it in General because the Development section is not really a section mod requests.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
Thanks Binary. You are sooooo smart!!
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
faux123 said:
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
Click to expand...
Click to collapse
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
seansk said:
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
Click to expand...
Click to collapse
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Binary100100 said:
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Click to expand...
Click to collapse
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
seansk said:
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
Click to expand...
Click to collapse
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Binary100100 said:
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Click to expand...
Click to collapse
omg rotflmao........so basically we really can't fix the hotspot issue or the call issue!!....I'm beginning to not like HTC...and I definitely don't like sgs2...I better start designing my own phone....the N1 never had this kind of BS problems....I used it as hotspot...called...took pictures alll the way down to 0 battery and it was made by HTC...what changed??? I still like my N1 better lol...hopefully next year we'll get
new years resolution dream phone:
720p super amoled PLUS "not pentile" screen
8 or more Mega pixel back side illuminated sensor with a f/2.2 or less and a wide lense camera lense with good optics and good audio quality while recording video.
able to use flash without limitations!!!!!!!!!!!!!!!!!!!!!!!!!
no flash bleed into camera sensor that requires 3 rounds of electrical tape
No screen bleed from the soft buttons
10 hour talk talk battery preferably over 2200 mAMp battery
STOCK ICS with custom amazing camera software like that amaze has now.
NO CARRIER BRANDING NO BLOATWARE. is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them...ok maybe this last one is asking too much.
is this so much to ask???
seansk said:
...is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them... is this so much to ask???
Click to expand...
Click to collapse
Ummm... yes. I believe the best you can do is create a phone with a jackhammer for a vibration mode, shove it in the patients mount and keep calling it. But of course some other people would use it for... inappropriate purposes.
Example from one of SassyBoB's reviews: https://market.android.com/details?...t=W251bGwsMSwyLDEsImNlbml4LmFuZHJvaWQudmJyIl0.
This is a mod to remove the data throttle from your rom. This does make a big difference if you use a lot of data. This is not a one size fits all solution. In order to make one for your rom, I will need your services.jar file in /system/framework. This will break the Mobile Network settings in your rom. You can easily get the throttle back with the remover mod. OP WIP. Attach your services.jar file to a post and say what rom you want it for. A thanks wouldn't hurt either
Thanks:
-Wildstang83 for being an awesome friend and showing me how to do this a while back
-sino8r for the original version of this mod
Downloads in post #2
DOWNLOADS:
Bamf 1.02: DOWNLOAD
One more just in case....
Last one (Maybe )
dmeadows013 said:
This is a mod to remove the data throttle from your rom. This does make a big difference if you use a lot of data. This is not a one size fits all solution. In order to make one for your rom, I will need your services.jar file in /system/framework. This will break the Mobile Network settings in your rom. You can easily get the throttle back with the remover mod. OP WIP. Attach your services.jar file to a post and say what rom you want it for. A thanks wouldn't hurt either
Click to expand...
Click to collapse
When I get time I will get you the code edits to umbreak the mobile network settings
Sent from RezROM
lllboredlll said:
When I get time I will get you the code edits to umbreak the mobile network settings
Sent from RezROM
Click to expand...
Click to collapse
Awesome! Thanks bored!
sub'd This looks promising
So VZW has a data throttle in services.jar and your tweak removes them but breaks other things and bored is going to fix what is broke?
Can you post the code changes please?
Also: Sprint locks ther hotspot and it can be unlocked in services.jar. Has anyone tried that with the VZW hotspot? I started parsing the tethergaurd and see some calls that authenticate or force to authenticate... Just wondering if you had any thoughts on that? Would be a nice little gift
scrosler said:
So VZW has a data throttle in services.jar and your tweak removes them but breaks other things and bored is going to fix what is broke?
Can you post the code changes please?
Click to expand...
Click to collapse
Yeah. Bored is going to post them when he gets some time. All you have to do to remove the throttle is decompile Services.jar and delete the files beginning with throttle in /com/android/server
dmeadows013 said:
Yeah. Bored is going to post them when he gets some time. All you have to do to remove the throttle is decompile Services.jar and delete the files beginning with throttle in /com/android/server
Click to expand...
Click to collapse
Wow... Ok. So I am assuming bored is going to remove the refernces to the smali files elsewhere in the code to eliminate them from being called?
Also, did you see my edit about hot spot? Any thoughts on that?
IM pretty sure with some effort we could crack the native hotspot.
scrosler said:
Wow... Ok. So I am assuming bored is going to remove the refernces to the smali files elsewhere in the code to eliminate them from being called?
Also, did you see my edit about hot spot? Any thoughts on that?
IM pretty sure with some effort we could crack the native hotspot.
Click to expand...
Click to collapse
As far as I know... I think that would be a cool project to do. I know I would use that a lot, and I've always wanted to hack a hotspot
Sent from my ADR6425LVW using Tapatalk
dmeadows013 said:
As far as I know... I think that would be a cool project to do. I know I would use that a lot, and I've always wanted to hack a hotspot
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I am pretty sure we could do it. I had asked if anyone had a ROM with a hacked hot spot (like we do on Sprint) and was told no one has done it yet.
With VZW, I am sure it will be differnt than Sprint, because VZW uses two different APK's while sprint uses one. To hack sprint you need to hack the services.jar (I think) and it would bypass the subscription check.
I looked at tetherign guard, thats the actual APK that does the checking and allows for authentication and saw some interesting stuff but never got a chance to follow up on it because shortly after we got unlocked and I have been focusing on ROM ever since.
I have Wed and Thur off so I might tear it down again and start looking at the code more closely.
testing the my patch right now... well actually ifthp69's from back in the Inc days
Sweet!!
lllboredlll said:
testing the my patch right now... well actually ifthp69's from back in the Inc days
Click to expand...
Click to collapse
Sent from my ADR6425LVW using XDA App
Figures old tricks don't work. The way we use to do it is rem out all the lines I'd code that had datausage except for the iput variable for mbuttondatausage the phone.apk settings.smali
Sent from RezROM
lllboredlll said:
Figures old tricks don't work. The way we use to do it is rem out all the lines I'd code that had datausage except for the iput variable for mbuttondatausage the phone.apk settings.smali
Sent from RezROM
Click to expand...
Click to collapse
For Hotspot or for Throttle... Sorry, I totally derailed this thread
I'm currently rooted, but still on stock, I'm not on any ROM. I'm confused on what this does? Are all are phones currently throttled? If I install this now do my speeds increase?
for the fc you get when you go to settings/wireless/mobile networks after the throttle is removed
the call what in the phone.apk settings.smali.... i'll mess with it more but i need to spend some time with my family for awhile
bal1985 said:
I'm currently rooted, but still on stock, I'm not on any ROM. I'm confused on what this does? Are all are phones currently throttled? If I install this now do my speeds increase?
Click to expand...
Click to collapse
When you go over a certain amount of data usage per month, Verizon decreases your data speeds. It is called throttling. This removes throttling. All Rezounds without this mod have it.
Back on the X2, this is what we did. Any chances it could be so simple for the Rezound? I know for damn sure I don't get throttled because I get ridiculous speeds all the time, lol.
L2_n19h7m4r3 said:
DISCLAIMER:
I cannot be held responsible for what YOU do to YOUR phone. With that said let's start!
(FYI: I use Root Explorer for this)
1. Preform a NAND Backup if you do not have one already
2. Make sure you are in WiFi or Airplane mode, or are not connected to 3G
3. Open root explorer and navigate to '/data/system/'
4. Find the 'throttle' folder and change the folder permissions to 'Owner:' 'Read' and 'Execute' only. (r-x------)
5. Open up the 'throttle' folder, you should have 2 files in here, one is 'temp' and the other is something like '-1226839461'. Backup these files to your SD card in case you have problems.
6. DELETE both files in the 'throttle' folder.
7. Reboot.
I am getting constant speeds of 2.31Mbps down and .7+ up. (On Eclipse 1.2RC1) Keep in mind this is only a theory for now, until I can get confirmation that it works for you guys also.
Click to expand...
Click to collapse
Are you having "my phone won't boot past the splash screen" issues with the latest OTA, and you're not using one of the Stock ROMs?
Mine wouldn't boot either, and it was because of this line in build.prop
debug.sf.hw=1
It was part of the "use gpu to render" tweaks that I'm not even sure do anything.
Anyway, remove that line and all should be well.
freeza said:
Are you having "my phone won't boot past the splash screen" issues with the latest OTA, and you're not using one of the Stock ROMs?
Mine wouldn't boot either, and it was because of this line in build.prop
debug.sf.hw=1
It was part of the "use gpu to render" tweaks that I'm not even sure do anything.
Anyway, remove that line and all should be well.
Click to expand...
Click to collapse
Hmm, I have no idea why but my build.prop has the "debug.sf.hw=1" line in it, I'm not using a stock rom and I have no problem booting after flashing freeza's (your) AIO (didn't flash the whole OTA).
The comment in front of the debug.sf.hw=1 line in build.prop says "#Render GUI with GPU instead of CPU", so if you remove the debug.sf.hw=1 line are you giving up hardware acceleration on GUI?
oldjackbob said:
Hmm, I have no idea why but my build.prop has the "debug.sf.hw=1" line in it, I'm not using a stock rom and I have no problem booting after flashing freeza's (your) AIO (didn't flash the whole OTA).
The comment in front of the debug.sf.hw=1 line in build.prop says "#Render GUI with GPU instead of CPU", so if you remove the debug.sf.hw=1 line are you giving up hardware acceleration on GUI?
Click to expand...
Click to collapse
The thing is, it doesn't affect the firmware or radio updates, only the actual OTA. That's why you're not having any problems.
After a bit of research, I've come to the conclusion that that line isn't really responsible for GPU rendering at all. In fact, I'm not sure any of those do anything. That one for sure doesn't.
freeza said:
The thing is, it doesn't affect the firmware or radio updates, only the actual OTA. That's why you're not having any problems.
After a bit of research, I've come to the conclusion that that line isn't really responsible for GPU rendering at all. In fact, I'm not sure any of those do anything. That one for sure doesn't.
Click to expand...
Click to collapse
It actually does make a difference, but for some reason it seems to only work with the OTA before this one. Yes, this is far from scientific proof, but try scrolling the app drawer without the setting and then again with it on. You will notice a difference. Its far from major but it's really noticeable. It's also the only way I could notice a difference. But like I said, its enough that you can tell that at least it does something... seriously, roll back and see for yourself, I promise you will see it too.
but for some reason it doesn't seem to do work with this OTA.. maybe there's a connection... idk.
That line was needed for crt animations to work. Removing it made crt animations stop working, so it did (or used to) do something.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Though there is a question in the o.p., I dont think the thread in general is a question.
Via My HTC Evo 3D On The Now Network From Sprint.
another mod i come across have tried the first mod with flow control set to 10 slowed me down it seemed but I left it blank and seems like huge improvement maybe just me figured I share see what else others can get. haven't tried the second mod looks a little risky to me if you try it please post results for others and if it works for you make sure to thank the right person (not me)
;-)
http://forum.xda-developers.com/showthread.php?t=1466245
spleef said:
another mod i come across have tried the first mod with flow control set to 10 slowed me down it seemed but I left it blank and seems like huge improvement maybe just me figured I share see what else others can get. haven't tried the second mod looks a little risky to me if you try it please post results for others and if it works for you make sure to thank the right person (not me)
;-)
http://forum.xda-developers.com/showthread.php?t=1466245
Click to expand...
Click to collapse
Do you intend to try the Mod 2? I'm going to try this in a bit and will post my results.
El Shaddai's Wrath said:
Do you intend to try the Mod 2? I'm going to try this in a bit and will post my results.
Click to expand...
Click to collapse
yeah thinking about it going to spend next 20-30 reading through all the info surrounding it then if i understand how to do it and how to go back to the way it was before ill give it a go
spleef said:
yeah thinking about it going to spend next 20-30 reading through all the info surrounding it then if i understand how to do it and how to go back to the way it was before ill give it a go
Click to expand...
Click to collapse
I can not find code: "persist.ril.uart.flowctrl=1"
Tried Root Explorer and Rom Toolbox and neither showed this. I am running Joker's 1.4 kernal not sure if that could possibly make any difference???
what rom cm doesn't have it think its only stock or stock based I'm on rocko and its there also just did the file swap can't say it helped yet but no problems with it so far don't think in going to try the unthrottle mod though looks terribly risky of having to sbf the line in my prop is immediately after cdma ril........
Sent from my MB855 using xda premium
Currently running CM7.2 and the code literally isn't there at all which leads me to believe that you could just delete the entire thing and it would either help or hurt your speed on Sprint's network.
El Shaddai's Wrath said:
Currently running CM7.2 and the code literally isn't there at all which leads me to believe that you could just delete the entire thing and it would either help or hurt your speed on Sprint's network.
Click to expand...
Click to collapse
idk thread says if you put a 0 you lose internet and zep was looking into it saying it can only be turned on or off not adjusted but then again said maybe it could be seems like it needs more research/testing but hell as horrible as sprint network in my areas is especially without 4g and flakey wifi anything that can help im trying
so i have been running this for a full day now and can say both mods seemed to have improved my stability and speed of internet saying this because in my are the 3gs are more like no gs and withe mod1 and 2 in place ive gotten a very reliable connection and much improved ( not to the point of worth shouting about but ) i a using null settings on mod 1 just leaving it blank and ive done the file swap in the second mod i want to try the unthrottle bit but im no dev and dont want to play with it not knowing exactly what it could do to my magnificent mopho. gl folks hope this works for you guys as well as it "appears" to be for me
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
grimproductions said:
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
Click to expand...
Click to collapse
Coolness think im going to try the unthrottle today i just flashed new rom havent set anything up yet if it messes things up wont lose nothing starting over
Sent from my MB855 using xda premium
So doesn't Zep's 3G Tweak script do essentially the same or is this different somehow?
As far as I know his scripts don't but he is testing it to maybe include it or thats what I understood from reading his posts.....
Just did the whole unthrottle mod was much easier than I thought everything running great no problems at all too early to tell if it improved anything but we will see and ill report if anything has
Sent from my MB855 using xda premium
grimproductions said:
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
Click to expand...
Click to collapse
You still running that mod without problems? Have you tried adding the line to CM7.2 RIL section?
jbb2388 said:
You still running that mod without problems? Have you tried adding the line to CM7.2 RIL section?
Click to expand...
Click to collapse
using rocko's unlocked rom with it nulled out (left it blank) maybe placebo but feels like its better so far as adding it to cm i think cm already removes the flow control im not 100% on that but if you wanna try it make sure you nandroid and or put a .bak after your prop so you can fix if something goes awry.
grimproductions said:
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
Click to expand...
Click to collapse
Any specific place u added the line? And guessing # precedes it?
Sent from my CM9 Electrify.
Android 17 said:
So doesn't Zep's 3G Tweak script do essentially the same or is this different somehow?
Click to expand...
Click to collapse
his script took me from 200-500kpbs to 1000-2000kpbs 3g supercharged script with 1-5 settings setting 5 experimental took me to 2000 but up and down whole way setting 3 was pretty constant on 1500 so that is where i stayed
grdead25 said:
his script took me from 200-500kpbs to 1000-2000kpbs 3g supercharged script with 1-5 settings setting 5 experimental took me to 2000 but up and down whole way setting 3 was pretty constant on 1500 so that is where i stayed
Click to expand...
Click to collapse
Be nice to get speeds like this with CM9.
i thought i read some post where it worfed on cm9 not sure thou read the v6 scrip and look for the info there in the theme section
grdead25 said:
i thought i read some post where it worfed on cm9 not sure thou read the v6 scrip and look for the info there in the theme section
Click to expand...
Click to collapse
Good Question!
I an trying to know that too.
Sent from my MB855 using Tapatalk
roundeye1987 said:
Any specific place u added the line? And guessing # precedes it?
Sent from my CM9 Electrify.
Click to expand...
Click to collapse
The location should'nt matter. You definitely dont want a # before a line that you want parsed. A # is essentially voiding that line out. It is called a comment in technical terms.
Sent from my MoPho. All typos are the phones fault.
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
I wanna know too...
bump.
vipirius said:
I was wondering, since there aren't as many roms for the gsm 3vo as I would like, and since the Sensation is very similar to our phone expect the camera, would it be possible to port a sensation rom to the gsm evo 3d? Or even better would it work out of the box(except camera of course) by only flashing an evo kernel?
Click to expand...
Click to collapse
HMZX said:
I wanna know too...
bump.
Click to expand...
Click to collapse
I think you can definitely test w/o causing permanent damage. For the smoothest test experience, you'll want to be familar with a custom recovery and the backup/restore modes available along with the type of internal memory unlock used on the device (Revolutionary or HTC official method).
Once you're familar with the basics, it would be fairly simple to test. The combinations for testing, off the top of my head, would be:
1) Sensation kernel and EVO 3D ROM.
2) Sensation kernel and Sensation ROM.
3) EVO 3D kernel and Sensation ROM.
Speaking from experience, once you're familar with how to load kernels and ROMs, the process is fairly generic across devices once write access to the internal memory is obtained.
Again, I'll re-iterate the importance of making a proper backup and being familar with the restoration process.
There are only two main hazards which come to mind:
1) Make sure NOT to flash the radio, bootloader, or any other file. ONLY flash kernel/system partitions.
2) Before flashing kernel/system partitions ensure the partition sizes between devices are the same, or EVO 3D is larger. Not sure the device limits and stops partitions from overwriting each other as I know some older devices did not and this caused an unrecoverable damage.
I'm sure if I missed anything, somebody else will post up. Hope that helps provide some technical background and logic to the approach! Keep us updated!
Thanks for the reply. I'm already familiar with flashing kernels/roms and how to make a nandroid backup etc so that isn't a problem. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Yeah I have a GSM phone so that's why I said GSM. Also wouldn't porting to the GSM version be easier then to the CDMA version since the sensation is also GSM?
Anyways I'm kinda busy today but I will try to see if it boots on my phone tomorrow and post my results. I'll.also try to get the camera to work by copying libs like you suggested.
Sent from my HTC EVO 3D X515m using XDA App
vipirius said:
Thanks for the reply. However I have 1 question, how exactly would I find the partition sizes of the sensation, I couldn't find it on the internet and I don't have a sensation that I can check.
Anyways I found a few posts on the forums of people claiming sensation roms work almost flawlessly except for the camera, so the next question would be if there are any apk's/libs etc. I can copy to the sensation rom to get the camera working. I'm no dev myself so I don't have a clue, but if someone could tell me I would appreciate it. Thanks.
Click to expand...
Click to collapse
Answer to first question: partition sizes are generally mentioned in a handful of different locations depending on the device: /proc/partition(s), /proc/emmc or /proc/mtd off the top of my head. Since the devices are similar and others have already tried this approach, probably not a concern, but none the less never hurts to learn more!
Answer to second question: the cameras (2 of them for 3D) on this device, along with the 3D display are the two biggest difficulties in porting AOSP such as CM to this device, in my opinion. they use closed source proprietary code from HTC. this requires a bit of reverse engineering and kanging from other random sources in order to get a final working product. personally, i wouldnt invest the time/effort into it, but others might find it a beneficial endeavor for themselves. either way, you're guaranteed to learn a bit about cameras! as stated above, all android libraries are loaded in /system/lib.
For the camera, I view android as having essentially three components contributing to a fully functional camera.
1) Camera drivers in the kernel
2) Camera libraries in /system/lib
3) Camera application apk file for Android UI
These three need to work together to at least some degree in order for there to be some functionality in the camera.
Gumby63 said:
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
Click to expand...
Click to collapse
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
joeykrim said:
Might be more off topic but could related also to this OP depending on his approach. If you encounter the boot animation this is generally a good sign the kernel has fully loaded and is handing off to the ramdisk/init process.
There are two possible situations at this point
1) If the boot animation loops, i.e. starts over and over, this shows there is an issue with Android/ramdisk init process. Adb has generally been loaded by this point and the issue should be outlined in logcat showing the specific .apk file along with line number which makes for a great starting point in troubleshooting.
2) If the boot animation starts/completes but the device completely reboots back to the splash screen, this is more difficult to troubleshoot. I'm not aware of a great approach to this but I might start by glancing at the /proc/last_kmsg file along with executing adb logcat as soon as I see the boot animation in an attempt to grab the logcat before the device reboots itself.
Good luck and keep us updated!
Click to expand...
Click to collapse
Well yeah it completely reboots back to the splash screen. During the bootanimation, I can't get a logcat and adb says there is no device connected. This isn't my first port but I've never had this happen lol. I'll look into what you said.
Sent from my HTC Flyer P510e using Tapatalk
Well, I successfully installed Android Revoltion HD 3.6.13, It boots, everything seems to work, however I didn't test GPS and BT yet. And the camera is well, half working I guess. The camera app opens, and i can see the controls etc but no image comes, and when I press the capture button the flash pops but the app FC's after that. I'm gonna try flashing [MOD] Camera from HTC Amaze 4G, v0.11 and see if it works. If it doesn't I'll copy over all the camera related libs I can find from my old ROM and see if it works then.
Edit: Hahahaha yessss it works I just flashed the Amaze camera app and now camera works only 2D of course but it's enough for me. I'll keep testing for a few days and of there aren't any serious bugs I can find I'll be using this as my daily driver from now on
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
vipirius said:
Edit2:Audio doesn't seem to work If I can't get that fixed then this ROM will be useless :/
Click to expand...
Click to collapse
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
t3project said:
then move over the proper sound drivers also located in /system/lib, /system/lib/modules and /system/lib/soundfx
Click to expand...
Click to collapse
Yeah that's what I was going to do, but thanks anyways. I'll report back on my success.
Gumby63 said:
Well you can't just flash a sensation ROM out of the box. You would at least need to change the mount points in the updater script otherwise you will get nothing. Regarding the camera, there are libs in /system/lib like liboemcamera.so and such. Not sure fixing the camera would be as simple as copying libs over from our phone though.
Sent from my PG86100 using Tapatalk
EDIT: Well I took a sense 3.6 ICS rom from the sensation forums, changed the mount points, and replaced the boot.img with ours. It boots to the bootanimation and then reboots by itself. So it is possible I may look at it more tonight.
EDIT 2: I just saw you were talking about the gsm 3d, I did this on the CDMA. The process would be the exact same though.
Click to expand...
Click to collapse
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
im not sure what you read but IT WAS WRONG..........
while you can do some of this stuff from your phone, you can not do a complete port properly without a computer
PMGRANDS said:
When you say Replaced the Boot.img, How'd you do that? Was it done with a ROM kitchen? Reason I'm asking because I read something saying that a Complete Rom Port could be achieved just with Apps on our phones... Using something like Root Explorer and whatever else (Can't Remember?) But I was wondering is that True?
And as for Extracting the Kernel can that Also be done Without the use of a Computer? In other words straight from a phone?
Thanx in Advance guys!!
Click to expand...
Click to collapse
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Gumby63 said:
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
vipirius said:
Aren't you on the CDMA EVO? If you are wouldn't the radios be completely different since the sensation is a GSM device? So maybe that's what's causing the reboot issues. I mean as far as I know even porting from the CDMA EVO to the GSM EVO is hard so wouldn't porting from the sensation to the CDMA EVO be even harder?
Click to expand...
Click to collapse
this is only patrialy the problem. flashing roms doesnt affect the radio so that wouldnt change but i there are some other libs that need to be moved that are associated with communication to the radio. cant remember which off the top of my head
Gumby63 said:
Yeah like t3project said, that is wrong.
But anyhow, I replaced the boot.img simply by opening the two ROMs with winrar and then deleting and replacing it. And to extract the kernel, you would need to split the boot.img either using a kitchen or some other tools that do the job.
A little update on my port: I still haven't gotten it to fully boot, it just keeps restarting
Click to expand...
Click to collapse
Yeah I thought the article I read was Bull****! I wish I could remember where I read it to show you guys what it said but just can't remember for ****... Lol!
Well Thanks for Confirming guys...