jamesd1085
Well-Known Member
Did you undervolt?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][PORT] Sharp ROM 2.2.2 for the Triumph (Updated: 12/16/12)
- Thread starter BSydz
- Start date
-
- Tags
- motorola triumph
I have only had like 1 or 2 random reboots ever with this ROM. I have had reboots that I know what I was doing, and it was bound to reboot, lock up or not work, but that was mainly trying to get the phone to do things it can't. The new kernel seems to help with the 3G a bit, but so far it is anecdotal at best, I would suggest the script I posted, to see if setting the MTU helps. Plus you have to think about tower switching while you are driving. Like does it happen every 10 miles or every few minutes. I would suggest reflashing the ROM or like you said see what happens on stock.
Has anybody else had any random reboots? Let me know and try to include as many details as possible.
Thanks for the feedback everybody.
No random reboots. Very stable. Reboots could be caused by overclocking or undervolting.
craig71200
Well-Known Member
I have never had a reboot with any rom on my Triumph... My 3g does seem better, but I also switched Prl to 61087.... I also use Kick ass kernel optimizer
beaviskob1
Member
[Quote/
Has anybody else had any random reboots? Let me know and try to include as many details as possible. /QUOTE]
Only when i overclock too high
Has anybody else had any random reboots? Let me know and try to include as many details as possible. /QUOTE]
Only when i overclock too high
whohasaquestio
Newbie
Hi Bsydz,
Do you have any plan to improve data speed, touch responsiveness or the camera? Data speed for obvious reason...touch responsiveness because it simply misses too many inputs....camera because the picture/video quality is usually poor.
If any of these concerns has already been addressed in the new kernel...please let us know. Thanks!
Do you have any plan to improve data speed, touch responsiveness or the camera? Data speed for obvious reason...touch responsiveness because it simply misses too many inputs....camera because the picture/video quality is usually poor.
If any of these concerns has already been addressed in the new kernel...please let us know. Thanks!
Well, I have found the touch driver and see some things I can do to help out there, but that is kernel related, not ROM. But, as far as data and camera, I don't know of any fixes for those. If you have any input on those 2, I would be very interested to hear about them. The camera, to me anyway, seems better than Stock, at the least. Have you tried the stock camera app to see if it would have any effect? I can't change the limitations of the device or network but I am willing to try to make it better. If you have any ideas let me know. You can always try out the U9000 ROM, as it is different even from this ROM, though the same principle applied, try not to use anything from the Triumph.
Neither of these ROMs have anything from the Triumph, except some framework code to get them to work, wifi drivers, and the zImage from the boot.img, So, other than rebuilding the kernel, there is no source code for this ROM or the other to fix other things. Hope this answers your question, if you want to experiment, let me know your outcomes.I have not loaded the new kernel yet, but I can get random reboots at any time. The worst is while using GPS in unfamiliar cities.
jamesd1085
Well-Known Member
If you want your touchscreen to be more responsive you can always extract austries init.d tweaks from his miui 4.0 rom which has an awesome touchscreen tweak as well as many others that seem to make things run really fast and smooth...not that it doesn't already run great...there are a few tweaks that i think are ics only that you can remove of you want, but i left them and the ones that dont work dont apear to have any negative effects...or you can give it a while and bsydz will probable have performance updates...i mean come on, he bought a p.o.s. device and turned it into a device worth the 300 virgin robbed us of!
P.s. dont forget to wipe cache and dalvik cache in recovery or adding these tweaks will have little to no effect!
P.s. dont forget to wipe cache and dalvik cache in recovery or adding these tweaks will have little to no effect!
I am still using v6 of this ROM, with no kernel changes, and I was using GPS in unfamiliar (to the phone) cities this past week, and I didn't have any random reboots.
jamesd1085
Well-Known Member
Idk how you have your triumph set up...but i have mine under/overclocked undervolted a.d some other performace related tweaks all with the new kernel and i have not had a single random reboot...if you are overclocking you may knock your max frequency down one notch.
I think i will load the stock ROM for a while and see if the problems I'm having are due to my phone or this ROM. I was doing some traveling Monday and my phone was a disaster. Initially GPS locked but then it kept dropping out. 3G coverage which is fine in the area I was traveling through disappeared, it was impossible to load a web page. Phone usually displayed 1X, 90% of the time. Previously on the same roads I always got 3G. At several points phone ceased to function and had to rebooted, plus I had a random reboot or two. Made a long day even longer.
One thing I notice is that GPS keeps searching for signal all the time. I'm running the same apps I always run and never had this issue before, causes the battery to drain faster. In everyday use this ROM is fine but when I put it to the test it didn't stand up to my needs. will go stock for a while then do a clean install of v.7 and see what happens. Hate to loose the smoothness and speed of this ROM but I need functionality.
One thing I notice is that GPS keeps searching for signal all the time. I'm running the same apps I always run and never had this issue before, causes the battery to drain faster. In everyday use this ROM is fine but when I put it to the test it didn't stand up to my needs. will go stock for a while then do a clean install of v.7 and see what happens. Hate to loose the smoothness and speed of this ROM but I need functionality.
Thanks for the feedback everybody. I would like some info about the system setup on the phones that are having problems. My setup is below for reference.
My Setup:
Recovery: CWMR 5.0.2.7
ROM: Ver7
Kernel: My custom kernel try 3/ Original kernel until about 6 days ago
Tweaks: None. (Anything other than removing unwanted apps, like init.d scripts or other tweaks.)
Installation Procedure: Backup, Factory Reset, Wipe Dalvik, Flash ROM, Reboot.
Setup: Install all of my apps from SD card (backed up by copying apks from data/app). I use Titanium backup to restore game data, sms/mms and call log. I also use root explorer, once I install it, to apply voicemail fix, then reboot.
Battery/System optimizers: None. Like Juice Defender, or Tasker.
These are areas that I think may hold clues to any issues that people are having.
Thanks again everybody for the feedback.
On mine all I did was a wipe/reset, clear dalvic cache, install V7. no other tweaks or changes. Just reload all my app that I have been using for years.
from phone:
model--SH8188U
Android version -- 2.2.2
baseband version -- PRS
Kernal version -- Apps_2.6.32.9-perf
Build number --7016_2_30H
CWM RECOVERY V.5.0.2.6
from phone:
model--SH8188U
Android version -- 2.2.2
baseband version -- PRS
Kernal version -- Apps_2.6.32.9-perf
Build number --7016_2_30H
CWM RECOVERY V.5.0.2.6
tcross8361
Well-Known Member
I don't know if this is a rom thing or something else. I'll throw it out there. When clicking on a link for youtube in the facebook app, it doesn't give me the option to open it in the youtube app. I always have to open it with a browser that takes me to the youtube website.
Is this something limited to Ver. 7? I'm using Ver. 6, and love it. It's perfect for me except that I wish the MTU issue would go away, so I'm very interested in this working. I haven't installed Ver. 7 because so far, Ver. 6 has been perfect for me except for the MTU issue, and I don't want to break what is working.
I don't have an init.d inside system/etc so I created one. When I try to run it, or even manually typing the command inside the script in a terminal emulator after typing su, I get "error: SIOCSIFMTU (Invalid argument)"
I am a bit of a noobie in Linux/Android so I'm not sure what I'm doing wrong, unless this is a Ver. 7 only hack.
Thanks for all your work making this phone so much better!
(There we go... It let me post it this time!
)You have to hit enter after su and then enter the command. I haven't been on Ver6 for a while, but I would have to say it is one of 3 things if that isn't it.Is this something limited to Ver. 7? I'm using Ver. 6, and love it. It's perfect for me except that I wish the MTU issue would go away, so I'm very interested in this working. I haven't installed Ver. 7 because so far, Ver. 6 has been perfect for me except for the MTU issue, and I don't want to break what is working.
I don't have an init.d inside system/etc so I created one. When I try to run it, or even manually typing the command inside the script in a terminal emulator after typing su, I get "error: SIOCSIFMTU (Invalid argument)"
I am a bit of a noobie in Linux/Android so I'm not sure what I'm doing wrong, unless this is a Ver. 7 only hack.
Thanks for all your work making this phone so much better!
(There we go... It let me post it this time!
First, go in to superuser and check for updates, then check that you have su access with a root explorer. There were some issues with one of the updates and sometimes you need usb debugging enabled.
Second try a number lower than 1472 by 4's like 1452 or 1464. This will determine if it is a kernel thing. Make sure that what ever method you are using gets root access. If the lower number works but higher doesn't, try my new kernel.
Third, it may be the differences in the versions, but I highly doubt it.
If the above doesn't answer your question, or these didn't lead you to the answer then I'll flash back and test it out. Just let me know.
You need to be more specific, do you mean the dialer from Ver6 and before? If so, you can just delete the 2 contacts apks and replace them with the ones from the older ROMs. If you are using Ver6 or before then check out Ver7 it has a more of a stock look. Sorry, I can't be sure what you are asking, from the context of the question. If this doesn't answer your question then feel free to ask away, just include as many details as possible, so I can help you better.
First,
Sorry for not saying it before, This ROM is absolutely awesome.
I've used almost all of the Triumph Roms and this is by far the best.
I work in an area with very lousy cell coverage and my Cell Standby time is up near 100% while I'm there. This is the only ROM that leaves me with any battery time left when I leave the office. When I'm at home, my battery drainage is 1-2% an hour. Unreal. If I forget to charge my phone overnight, it isn't dead in the morning. Also the GPS lock time is incredible.
As for the dialer, I'm on version 7, which has the stock looking dialer.
I miss the old dialer from before ver6 which had T9 lookup as you entered numbers. I know there are dialers in the appstore which do that, but I liked the one that came the earlier versions as it seemed more lightweight. (no lag time to load when clicking on it.)
Thanks, in that case you can just swap the contact apks in the system/app folder with a root explorer and fix the permissions. You may need to wipe caches if anything is acting funky. If you use Titanium Backup and have a nandroid of Ver6 then you can either use TB to extract it from the nandroid or restore the nandroid then backup the 2 contact apps, then restore back to Ver7 and do the swap in TB by uninstalling then installing the ones you want. If you search this thread, somewhere around the 4th page or after, people were talking about the opposite, but should give you the details you may need to do this. Hope this helps.
Is therr a way to use the default ics keyboard? Im using hackers keyboard but that takes up 10mb of ram! I want to use a kboard that is low memory and doesnt need a ridiculus amount of permissions like ANY of the GO products... and for the lockscreen id like a way to jump straigt to camera.. golocker and others have this but they all use too many permissions in my opinion to do a simple task... any thoughts? Same request for a better camera app all the ones on the play store require too many permissions i just want an app that takes a pic lol dont care for gps tag or internet... yeah im paranoid. Thoughts? Sorry for the typos using my triumph for this post on a bumpy bus!
OK, I'm not quite THAT much of a noob!
I was at the # prompt in the terminal emulator and superuser reported granting privileges to terminal and everything. It just didn't work, and I wasn't sure why. Path, kernel, etc?Anyway, I tried again using the 1452 as the MTU size as you suggested, and that worked, so I guess an update to Ver. 7 and your new kernel is in order, or will the new kernel work with Ver. 6? I missed the posts related to the release of Ver. 7, and apologize if this has been asked/answered, but can I install Ver.7 over Ver. 6 without wiping anything so I don't lose my apps and data, etc? It worked doing the "dirty install" of Ver. 6 over the deodexed stock for the fixing voicemail trick. Will that work again putting Ver. 7 on there?
Thanks again!
Yeah, I added the hit enter thing last minute after rereading your post, cause I had gotten an error trying to put in su like sudo not thinking. I wasn't inferring anything, with the wide variety of people with differing skill levels I try to make my "support" answers as detailed as possible, just in case somebody else has the same issue. I would flash the new kernel, if you want to stay on Ver6. I don't suggest flashing over Ver6, as people have reported mixed outcomes, you may run in to Gapps problems. If you want to try, I would suggest doing a backup then wiping the caches then installing Ver7, but I can't promise anything. Try the command after you flash the new kernel then we will know if it is a system difference, I can't remember all the stuff I changed in the framework now. That will be the easiest thing to test, should only take about 2 minutes. Hope this helps, let me know how it goes.OK, I'm not quite THAT much of a noob!
Anyway, I tried again using the 1452 as the MTU size as you suggested, and that worked, so I guess an update to Ver. 7 and your new kernel is in order, or will the new kernel work with Ver. 6? I missed the posts related to the release of Ver. 7, and apologize if this has been asked/answered, but can I install Ver.7 over Ver. 6 without wiping anything so I don't lose my apps and data, etc? It worked doing the "dirty install" of Ver. 6 over the deodexed stock for the fixing voicemail trick. Will that work again putting Ver. 7 on there?
Thanks again!