Hi everybody,
I installed a cool ROM on my phone but one if its features included dimming the haptic buttons on my phones. I liked them bright before when I had stock. Is there any mod I could flash to help fix the dim haptic buttons. They're a little too dim for me but the Rom is way better than stock.
Thanks
Sent from my PG86100 using XDA App
Hiya Buddy said:
Hi everybody,
I installed a cool ROM on my phone but one if its features included dimming the haptic buttons on my phones. I liked them bright before when I had stock. Is there any mod I could flash to help fix the dim haptic buttons. They're a little too dim for me but the Rom is way better than stock.
Thanks
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
It depends on whether the dim setting was done in the kernel itself or not. Go check this:
/sytem/etc/init.d/ <- open the various scripts in there and look for a reference to this:
/sys/devices/platform/leds-pm8058/leds/button-backlight/currents
if there IS a script in there, it *might* have the currents set to 2 or 5 or something. The stock brightness is 20, so you could either change the value you find in the script to 20, or whatever you like, OR delete the script altogether.
if there is NOT a script in there, the setting is probably built into the kernel, so the only way around it would be to ask the ROM or kernel dev to remove it or allow an option to change it. You could also flash a different kernel that does NOT have the setting built in.
Thanks I can find the init.d folder and its contents but I don't think that script you mentioned is there. I'll post a screenshot of the init.d folder. If you're right about it being built in to the kernel would you know what kernel I would need to flash in order to do this???
P.S. Not sure if I should PM the dev who created the ROM or try to post in the rom's forum. Unfortunately, I need to get my post count up to post in that forum seeing as I'm still considered a noob.
P.S.S. I forgot to mention the rom's name. Its called Olympus Trinity XE Prime and its by theAndroidOsX (something along the lines of that...forgot how to spell it...)
Thanks again for your help!
Hiya Buddy said:
Thanks I can find the init.d folder and its contents but I don't think that script you mentioned is there. I'll post a screenshot of the init.d folder. If you're right about it being built in to the kernel would you know what kernel I would need to flash in order to do this???
P.S. Not sure if I should PM the dev who created the ROM or try to post in the rom's forum. Unfortunately, I need to get my post count up to post in that forum seeing as I'm still considered a noob.
P.S.S. I forgot to mention the rom's name. Its called Olympus Trinity XE Prime and its by theAndroidOsX (something along the lines of that...forgot how to spell it...)
Thanks again for your help!
Click to expand...
Click to collapse
Hey bro, try flashing this, and see if it works. It will add a script to your init.d folder (50NormalLed) that *should* set your LEDs to full power whenever you reboot your phone.
Let me know if it works
If you have root explorer you can also just go to sys/devices/platform/leds-pm8058/leds/button-backlight/ long press 'currents,' select 'Open in text editor,' and change the variable to 20. Hit menu and select: 'save changes.' Only thing is that every time you reboot your phone you have to redo this process
@Bamba1260 tried flashing the zip. Its in the init.d folder but the haptic keys still have the same low brightness. Any other suggestions???
Hiya Buddy said:
@Bamba1260 tried flashing the zip. Its in the init.d folder but the haptic keys still have the same low brightness. Any other suggestions???
Click to expand...
Click to collapse
ask the ROM dev if he built the dim leds INTO the kernel, if so, ask him to make you a zip that disallows this, so you can set your own brightness. Or try a kernel without the lights hacked, if there are any.
Thanks, looks like I have to PM the dev of the ROM. I figured I wasn't flashing right since I have H.BOOT 1.5 and S-ON so I tried it through fastboot. That didn't work either, thanks for trying to help me though.
Hiya Buddy said:
Thanks, looks like I have to PM the dev of the ROM. I figured I wasn't flashing right since I have H.BOOT 1.5 and S-ON so I tried it through fastboot. That didn't work either, thanks for trying to help me though.
Click to expand...
Click to collapse
Hmm... il Duce is probably on to something with it being in the kernel then lol. I thought a script would override that, but apparently not.
Good luck with the dev, I hope you figure something out
Woah a long time lol
The ROM was olympus trinity/titan. I loved that rom, but the only issue I had were the dim haptic keys. I think they were built into chad's kernels, so not sure of how to fix that other than flashing a diff kernel that doesnt dim the haptic keys.
Related
mySlide-1.0.2
YOU PROBABLY DON'T WANT THIS...DON'T WASTE YOUR TIME!!!!!
This is just what I want, not necessarily what you want http://www.mediafire.com/?tstgikwhfezj6ph
This Rom will mostly be unsupported and unmaintained.
Flash at your OWN RISK.
What it is:
Stock slide rom.
added busybox
added netcat (busybox nc isn't good enough for me)
added bash
added htop
removed link toolbox->df (prefer the one in busybox)
removed link toolbox->rm (prefer the one in busybox)
changed the default animated boot ADVERTISEMENT and jingle
pngcrushed and zipaligned apks (with the execption of one) to save some space
Kangs:
what isn't.
maybe a few more little changes I forgot.
changes:
from 1.0.0 to 1.0.1:
added a2sd (from eugene373's smr5r1. breaks boot animation)
added default themes back.
from 1.0.1 to 1.0.2
added e2fsck
mySlide-1.0.0-signed
mySlide-1.0.1-signed
mySlide-1.0.2-signed
Themes in this are broken (1.0.0 only). If you want the default themes back then flash this...
themes-signed.zip
hey dumfuq glad to see you over on the slide section now. can we expect some overclocked kernals from you like on the g1?
jriv said:
hey dumfuq glad to see you over on the slide section now. can we expect some overclocked kernals from you like on the g1?
Click to expand...
Click to collapse
I sure hope so, but only time will tell.
That would be sick wonder how high this processer can go?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Is the IM app erased in this and the tmobile app pack? i hate those apps
Nevermind i used ur rom and erased the files and signed it again. Thanks for the rom
dumfuq said:
YOU PROBABLY DON'T WANT THIS...DON'T WASTE YOUR TIME!!!!!
Click to expand...
Click to collapse
Not sure why you say that (in those words), but this does look decent!
Also, noob question, but are the stock ROMs (apps included) not zipaligned by default?
Yup they were already zipaligned. At least the ones I just checked
Honesty I didn't even look first. The crush actually takes off about 10Mb though.
yo dumfuq quick question... what exactly is required in editing a kernel to allow for overclocking and undervolting?
kingofyo1 said:
yo dumfuq quick question... what exactly is required in editing a kernel to allow for overclocking and undervolting?
Click to expand...
Click to collapse
Not exactly sure if this is what your asking but basically...
You need the kernel source code to edit (the legend kernel source has the espresso board files),
A handy dandy text editor (like vim),
a cross-compiler (There is one under prebuilt/linux-x86/toolchain in an AOSP or cyanogenmod build environment),
and a linux environment (cygwin might work not really sure).
1. download source
2. unpack source
3. edit source
4. set environmental variables
4. compile source
5. make a boot.img or an update.zip
Obviously that's incredibly simplified, but hopefully you get the idea.
Ok quick question to the maker of this rom... How can i add the themes back to this rom? I want to put the themes back but i dont kno which folder to put them in. Also which folder is where i can change the boot animation you have installed to stock? Thanks
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
btate0121 said:
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
Click to expand...
Click to collapse
good question. a2sd is a plus
you don't put them in anywhere. you can download and install them. there's a thread already with a small pack of themes to download and install. You install like any other APK. Search this forum section for them.
NiN39Z said:
Ok quick question to the maker of this rom... How can i add the themes back to this rom? I want to put the themes back but i dont kno which folder to put them in. Also which folder is where i can change the boot animation you have installed to stock? Thanks
Click to expand...
Click to collapse
The PNG crush killed the stock themes. If you want them back you can either boot to recovery and push the original ones to /system/app/ or just flash this...themes-signed.zip. That is just an update.zip that will copy the original themes back to your phone.
btate0121 said:
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
Click to expand...
Click to collapse
Nope, no a2sd.
any plans to add a2sd? I mean seriously... this would be PERFECT for my needs if it only had a2sd. I'm happy with a stock rom... i just want a2sd.
btate0121 said:
any plans to add a2sd? I mean seriously... this would be PERFECT for my needs if it only had a2sd. I'm happy with a stock rom... i just want a2sd.
Click to expand...
Click to collapse
Nope. Currently I don't use a2sd, or this rom really. I made this just for an optimized stock rom to bounce back to when needed. Currently I'm running a customized version of eugene's cm6 as my daily driver.
in your experience.. how hard would it be for a novice to add a2dp to this? I did a quick google and found about 3 good pages of data.. but it seems pretty complicated (packing and repacking boot.img looks to be pretty intense on a windows machine without any experience from what i can tell). Do you think i should attempt this? LOL.
dumfuq said:
Nope. Currently I don't use a2sd, or this rom really. I made this just for an optimized stock rom to bounce back to when needed. Currently I'm running a customized version of eugene's cm6 as my daily driver.
Click to expand...
Click to collapse
what is the difference between your customized version and the regular?
btate0121 said:
in your experience.. how hard would it be for a novice to add a2dp to this? I did a quick google and found about 3 good pages of data.. but it seems pretty complicated (packing and repacking boot.img looks to be pretty intense on a windows machine without any experience from what i can tell). Do you think i should attempt this? LOL.
Click to expand...
Click to collapse
what were the links they seem like the ones i have been looking for lol! i can already unpack and repack a boot.img im just looking for the steps i need to add to get aps2sd to work! i had a link explaining it but i cant find it anymore or google it!
I originally made it to copy the functionality of stock MyTouch 4G ROM, but then I thought it might be a nice addition to Desire / Desire HD ports on Nexus too.
First trackball press wakes up the phone, the second one puts it back to sleep (as long as the phone's screen is locked).
This mode is only working for ROMs that have trackball wake implemented, and allows the lockscreen to put the phone back to sleep. This
mod doesn't include trackball wake. For this reason it won't work on Gingerbread-based Sense ROMs or older Sense ROMs that don't have trackball wake implemented.
Original thread in MyTouch 4G forum
For Nexus I've made it to work with eViL D:'s NXSense, NXSenseHD (1.1 BETA only!) and MicroMod's SuperHybrid DesireHD.
Instructions:
Flash the attached file in recovery. It should work with CWM3.x - it uses Edify scripting.
Known issues:
When the phone is turned on using power button - the first trackpad press won't put it back to sleep, but pressing once again will. I'll try to look into it and solve it, if it's something that can be solved without touching the framework.
Uninstallation:
Extract HtcLockScreen.apk (located in /system/app/) from your ROM's ZIP file.
Execute: adb push HtcLockScreen.apk /system/app/
Or just reflash the corresponding attached Stock_* ZIP in recovery.
Remarks:
The mod involves HtcLockScreen.apk, found only on Sense ROMs. It's possible to achieve the same functionality on various CM7 flavors, but the mod needs to be compiled into the framework and possibly use another mechanism to put the phone to sleep. My Nexus is now my wife's, and I have absolutely no wish to load CM7 on it, and being unable to test the mod in its framework variation, I won't be able to create one.
13-Apr:
Updated the MicroMod version to avoid bootloop.
Added mod for NXSenseHD Gamma, including RNGuy's trackball wake. WARNING: Some of the notification texts are messed up. I don't have time to clean it - need to return the Nexus, I'd be really glad if someone else did it. The strings are in patched android.policy.jar.
Jack_R1 thanks for this, do you think you could have a go at the desire S?
I see the same requests on MT4G forum...
I guess I'll have to attempt, just have to pick a day for a non-functional phone (as I'll have to back it up, wipe and load Desire S ROM for experiments).
How do I undo / uninstall this mod?
ali3nfr3ak said:
Jack_R1 thanks for this, do you think you could have a go at the desire S?
Click to expand...
Click to collapse
Edited the OP, added the reason for the inability to do Desire S. I believe that more experienced guys already tried to take on the Gingerbread framework and find hooks for trackball wake, if they didn't find anything - my chances are low. There might be places in HTC framework to hook the trackball wake - since it was done for G2 and MT4G trackpads. I just don't have enough time/skills/phone to research it.
Jack_R1 said:
Edited the OP, added the reason for the inability to do Desire S. I believe that more experienced guys already tried to take on the Gingerbread framework and find hooks for trackball wake, if they didn't find anything - my chances are low. There might be places in HTC framework to hook the trackball wake - since it was done for G2 and MT4G trackpads. I just don't have enough time/skills/phone to research it.
Click to expand...
Click to collapse
Ok, thanks for your efforts anyway
hi I'm running "evil nxsense hd v1.0 gamma and have flashed this but all it does is mess up my lock screen and the trackball does not wake the phone any ideas? thanks in advance
I've updated the OP, relocating and making bold the relevant section.
This mod DOESN'T ADD trackball wake. It is based on existing trackball wake. On NXSense 1.1 Gamma there is NO trackball wake.
If you want it to work on Gamma - you need to add trackball wake to Gamma (can probably be done by pushing android.policy.jar from Beta to /system/framework/), and if it works - my mod will work. I can't test it, having no Nexus to play with.
If the mod will work but the screen graphics will be messed up - please post and I'll recompile it for Gamma and create update.zip to include android.policy.jar.
Jack_R1 said:
I've updated the OP, relocating and making bold the relevant section.
This mod DOESN'T ADD trackball wake. It is based on existing trackball wake. On NXSense 1.1 Gamma there is NO trackball wake.
If you want it to work on Gamma - you need to add trackball wake to Gamma (can probably be done by pushing android.policy.jar from Beta to /system/framework/), and if it works - my mod will work. I can't test it, having no Nexus to play with.
If the mod will work but the screen graphics will be messed up - please post and I'll recompile it for Gamma and create update.zip to include android.policy.jar.
Click to expand...
Click to collapse
oh right sorry my mistake thought this would add trackball wake to my rom thanks anyway
Hello, i am using MM's SuperHybrid (HD-Desire v1.7-FINAL 720p HD-RECORDIN) ROM from here: http://forum.xda-developers.com/showthread.php?t=784260 and after falshing this Wake_Sleep_lockscreen_Passion_MicroMod_SuperHybrid_DHD, my N1 is still booting in loop!
Is there something wrong with this ROM?
No, there shouldn't be.
To restore to stock lockscreen, follow the guide for uninstallation. I've uploaded the stock lockscreens from those ROMs, so if you're having trouble with ADB commands - you can just pull out the battery, boot to recovery and install the stock ZIP.
If you don't have trouble with ADB commands - please send me the logcat.
In the meanwhile, I'll try to get a Nexus for a couple of hours to test it.
Thanks.
Thanks for your mod, but you should conside that the best Desire HD rom is the nxsense 1.0 gamma. The beta sucks a lot of battery and other bugs
I'll check if trackball wake is easily ported from Beta to Gamma, and if yes - I'll add it to the mod.
Jack_R1 said:
No, there shouldn't be.
To restore to stock lockscreen, follow the guide for uninstallation. I've uploaded the stock lockscreens from those ROMs, so if you're having trouble with ADB commands - you can just pull out the battery, boot to recovery and install the stock ZIP.
If you don't have trouble with ADB commands - please send me the logcat.
In the meanwhile, I'll try to get a Nexus for a couple of hours to test it.
Thanks.
Click to expand...
Click to collapse
Thx for the quick answer. I have everithing working to use ADB but i don't know what you need.
If you explain to me, i can give you what you want to see.
Sory for my english
It's ok, I convinced my wife to give me her Nexus for a couple of hours
I've debugged the problem, very sorry - I put the wrong file in the ZIP. I've recompiled the mod for MicroMod's DHD port and tested it, it's 100% working now. Uploaded the newer version.
Trying to mod NXSense Gamma now.
Updated the OP with additional mod for Gamma. Put attention - this mod has the notifications with wrong strings, and I'm unable to fix it - returned the Nexus. I hope someone else can. Please search the NXSenseHD ROM thread for possible solutions. RNGuy's mod is linked in the OP.
Yeah, it works! THX Jack_R1!!
Does this MOD will work on any other sense ROM like RunnymedeMOD007, Hypersense, etc?
alisabki said:
Does this MOD will work on any other sense ROM like RunnymedeMOD007, Hypersense, etc?
Click to expand...
Click to collapse
No.
This method never compatible N1 GB
Sent from my Nexus One using XDA App
Thanks mate. But unfortunately it doesnt work with my desire, non of them.
Iam using rom: ROM/MOD 4.0.4][Stable Android 4.0.4 with good video recording][v3.5 08.03.2013]
on this link: http://forum.xda-developers.com/showthread.php?t=2095658
Could you please prepare a good file for this rom.
After all this framework hack does not work well under too many ROMs and causes lots of confusion about version. I accidentally found a universal solution to Home Button vibration that works with JKay theme and won't break anything. So this method is abandoned.Hi everyone. I have been Hellraising i9100 ROMs since Entropy's release, however was puzzled by the Home button which lags and won't give any feeling of touch when pressed.
After some research I finally figured out how to fix this. I made 2 versions, one for XXKI3 and another for XXKI4
Currently ROMs incorporates JKay theme mods (Sensation) are not working.
(Sorry I was too excited to notice I compiled both file from custom ROMs that were containning extended power menu, the fix is not universal and try at your own risk!).
Installtion Instructions:
1. Place the zip file into your Internal SD
2. Reboot into Recovery and select "install zip from sdcard"
3. Select "install from SD card", choose YES
4. hit return and reboot
You should have haptic feedback on Home now, also the Home button should respond instantly.
Caution:
Only apply to ROMs that are based on supported Samsung builds.
android.policy.jar varies from build to build so can not hybrid with different versions.
Credit:
gtg465x - home button lagfix code reference
DesignGears - home button haptic fix code reference
Ande definitely Entropy512, for the awesomeness of Hellraiser!
Please let me know if anything happens.
Downloads
Currently not working with JKay themes.
For i9100XXKI3 based ROMs:
View attachment XXKI3-hapticfeedbackfix.zip
For i9100XXKI4 based ROMs:
This file is modified from an i9100 ROM with extended power menu and header, might not work if the menu had the header removed!
View attachment XXKI4-hapticfeedbackfix.zip
amtrakcn said:
Hi everyone. I have been Hellraising i9100 ROMs since Entropy's release, however was puzzled by the Home button which lags and won't give any feeling of touch when pressed.
After some research I finally figured out how to fix this. I made 2 versions, one for XXKI3 and another for XXKI4.
Installtion Instructions:
1. Place the zip file into your Internal SD
2. Reboot into Recovery and select "install zip from sdcard"
3. Select "install from SD card", choose YES
4. hit return and reboot
You should have haptic feedback on Home now, also the Home button should respond instantly.
Caution:
Only apply to ROMs that are based on supported Samsung builds.
android.policy.jar varies from build to build so can not hybrid with different versions.
Credit:
gtg465x - home button lagfix code reference
DesignGears - home button haptic fix code reference
Ande definitely Entropy512, for the awesomeness of Hellraiser!
Please let me know if anything happens.
Click to expand...
Click to collapse
Thanks.... can you please post what code is changed within it (FOR HOME HAPTIC FEEDBACK) so I can mod the one for the rom I'm using. I don't want to use a generic one.
Thanks!
EDIT: Its rom specific.....you can't do generic addons.... It broke my rom which is why posting the actual change would be best. It booted but broke JKAY mods
shoman94 said:
Thanks.... can you please post what code is changed within it so I can mod the one for the rom I'm using. I don't want to use a generic one.
Thanks!
Click to expand...
Click to collapse
I think KI4 version works for checkROM. However just forget I modified both from custom ROMs so does not work universally...
There are multiple places in smali that needs to edit. So you might want to compare your original file with the attachment.
It's <decompiled dex folder>\com\android\internal\policy\impl\PhoneWindowManager.smali
View attachment PhoneWindowManager.zip
amtrakcn said:
I think KI4 version works for checkROM. However just forget I modified both from custom ROMs so does not work universally...
It's more than one place in smali so you might want to compare with the attachment.
View attachment 780701
Click to expand...
Click to collapse
I've been doing that but there are so many differences that I can't tell which is which.
Can't you just say which lines were changed....?
shoman94 said:
I've been doing that but there are so many differences that I can't tell which is which.
Can't you just say which lines were changed....?
Click to expand...
Click to collapse
Line 3841 to 4568... actually works just override all differences.
amtrakcn said:
Line 3841 to 4568... actually works just override all differences.
Click to expand...
Click to collapse
errors out.....
to good to be true. I've been messing with this all night and I"m not winning.
shoman94 said:
errors out.....
to good to be true. I've been messing with this all night and I"m not winning.
Click to expand...
Click to collapse
Like what kind of error you are encountering? During recompile or during testing?
I don't have time to poke at this (busy sobering up after a party...) but: I suggest providing the modded version,a nd the original, and diffing them.
Note that according to Mikey, designgears' patch accidentally caught a bunch of changes that weren't related to home-button.
And yes, just copying the smali will cause an epicfail most likely, ESPECIALLY if targeting a JKay theme, as JKay did dome significant mods to that smali file.
FYI, shoman94, you've gotten as far as I ever did - I never got a working mod, but I've been pretty busy this week.
Entropy512 said:
I don't have time to poke at this (busy sobering up after a party...) but: I suggest providing the modded version,a nd the original, and diffing them.
Note that according to Mikey, designgears' patch accidentally caught a bunch of changes that weren't related to home-button.
And yes, just copying the smali will cause an epicfail most likely, ESPECIALLY if targeting a JKay theme, as JKay did dome significant mods to that smali file.
FYI, shoman94, you've gotten as far as I ever did - I never got a working mod, but I've been pretty busy this week.
Click to expand...
Click to collapse
Thanks for pointing out, I recalled many other other modifications to the android.policy.jar after I posted but I cannot edit the title of thread now...
When comparing the 2 smali files (Original and DesignGear modified), except the lines for home button I only saw difference in conditions, which I don't really understand. It was a experiment that I just copyed the whole PhoneWindowManager.smali then compiled. The compiled file worked.
The file I posted is from a KI4 ROM with extended power menu with header, however since header modification is in GlobalActions.smali I think this should not affect compiling.
Tell me if I got anything wrong, first time looking into the bytecodes
Will be very thankful if you have time to look at this
View attachment OriginalPhoneWindowManager.zip
View attachment ModifiedPhoneWindowManager.zip
amtrakcn said:
Like what kind of error you are encountering? During recompile or during testing?
Click to expand...
Click to collapse
Well I installed your file and it booted fine but jkay mods were broken. I've been trying different combination for the last 8 hrs trying to get this to work. Epic fail.
I might have to post a message to JKAY for some help.
shoman94 said:
Well I installed your file and it booted fine but jkay mods were broken. I've been trying different combination for the last 8 hrs trying to get this to work. Epic fail.
I might have to post a message to JKAY for some help.
Click to expand...
Click to collapse
Since JKay moded other places than the Home Button as Entropy mentioned... this should happen.
You'll need precise modification that just target the Home button...
amtrakcn said:
Thanks for pointing out, I recalled many other other modifications to the android.policy.jar after I posted but I cannot edit the title of thread now...
When comparing the 2 smali files (Original and DesignGear modified), except the lines for home button I only saw difference in conditions, which I don't really understand. It was a experiment that I just copyed the whole PhoneWindowManager.smali then compiled. The compiled file worked.
The file I posted is from a KI4 ROM with extended power menu with header, however since header modification is in GlobalActions.smali I think this should not affect compiling.
Tell me if I got anything wrong, first time looking into the bytecodes
Will be very thankful if you have time to look at this
View attachment 781002
View attachment 781001
Click to expand...
Click to collapse
and the differences are attached but don't work with JKAY mods.... some things may need to get incorporated. IDK
amtrakcn said:
Since JKay moded other places than the Home Button as Entropy mentioned... this should happen.
You'll need precise modification that just target the Home button...
Click to expand...
Click to collapse
exactly my friend. I've been trying to get some help from DG but he is preoccupied. He tried a quick patch but resulted in the same issues I was getting myself.
I can confirm that it worked for checkrom2.0 but when I updated to checkrom 3.0 and relflashed the mod my phone would bootloop as soon as the phone booted. The first thing that popped up was a fc on com.android.phone (or something that had phone in it
Sent from my SGH-I777 using xda premium
jgrimberg1979 said:
I can confirm that it worked for checkrom2.0 but when I updated to checkrom 3.0 and relflashed the mod my phone would bootloop as soon as the phone booted. The first thing that popped up was a fc on com.android.phone (or something that had phone in it
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It worked on 2.0 but broke the jkay mod.... extended power menu was out of whack.... AOSP style lock screen stopped working.... etc
jgrimberg1979 said:
I can confirm that it worked for checkrom2.0 but when I updated to checkrom 3.0 and relflashed the mod my phone would bootloop as soon as the phone booted. The first thing that popped up was a fc on com.android.phone (or something that had phone in it
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It looks like the new checkrom is kj3 based. That haptic fix is for ki3 and ki4. Probably why is messed up.
Sent from my SAMSUNG-SGH-I777 using XDA App
can you post the fix for sensation 1.9.
would be greatly appreciated
nmandi said:
can you post the fix for sensation 1.9.
would be greatly appreciated
Click to expand...
Click to collapse
Hi, I compiled the file but since I'm not on Sensation ROM I did not try it myself.
Let me know if you run into any problem.
THX!
View attachment 782532
amtrakcn said:
Hi, I compiled the file but since I'm not on Sensation ROM I did not try it myself.
Let me know if you run into any problem.
THX!
View attachment 782532
Click to expand...
Click to collapse
i'm getting com.android.phone force close
I have been having numerous issues trying to get ICScrewd to run on my phone and I am almost certain its a kernel issue.
It was suggested that I swap out the kernel before flashing and that sounds like a great idea to me.
Except...... I don't know how.
Is it as simple as taking the zImage from the kernel zip I want and placing it in the rom zip I want?
Can I ignore the META-INF folder or do I need to somehow merge that over too?
I am sure there is a wiki or a how-to on this but I have looked and cant find it. Its probably because I don't know phrase my search.
But anyway, if someone could point me in the right direction I would be very grateful.
FireRaider said:
.
Is it as simple as taking the zImage from the kernel zip I want and placing it in the rom zip I want?
Click to expand...
Click to collapse
Yup it is that simple, just replace the file with the one you want.
You can also clean up with kernel cleaning script then flash entropy kernel in recovery
Sent from my SGH-I777 using Tapatalk
yoderk said:
Yup it is that simple, just replace the file with the one you want.
Click to expand...
Click to collapse
Working on it now. Thanks.
jivy26 said:
You can also clean up with kernel cleaning script then flash entropy kernel in recovery
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
My poor phone locks up even in recovery running Siyah. Its crazy.
I am going to try this like you suggested in your thread.
I should be reporting back soon.
It worked!
So far, so good.
I havent had a single locked up screen or SOD since I flashed.
Thanks guys!
Interesting, i've been using siyah for a long time and never experienced any issues.
Sent from my GT-I9100 using Tapatalk
im running icscrewed with siyah and its working just fine
Just curious since I have never tried a mod with any major changes, what are the benifits of changing out the Kernel, and what are the differences between them?
crimsonconcepts said:
Just curious since I have never tried a mod with any major changes, what are the benifits of changing out the Kernel, and what are the differences between them?
Click to expand...
Click to collapse
For myself the benefit was actually being able to run the ICScrewd rom at all.
In my experience of several years of flashing, some kernels just wont work with some phones.
It sound odd and all that, but my real world experience has led me to give each kernel I am interested in several tried and if they continually crash my phone I move on. I have no idea why this would be. Coming from the Captivate I tried all sorts of kernel and rom combinations. If they didn't work well I just moved on.
As far as different kernels go, some have better battery life than others due to built in tuning I believe. They can be cleaned up to help your phone run faster. And obviously from my experience here in this thread, help your phone be stable.
Excuse my noobness, please. I figured this would be a pretty relevant thread to post this question.
I flashed Siyah 2.6.9 via Odin and then in recovery installed ICScreweD. Did doing so revert my kernel to the older version of Siyah used in the rom?
If so, can I just flash in the newer version using Odin or should I research another method?
This is my first root/mod so I'm still a little nervous about messing up.
Kasdarack said:
Excuse my noobness, please. I figured this would be a pretty relevant thread to post this question.
I flashed Siyah 2.6.9 via Odin and then in recovery installed ICScreweD. Did doing so revert my kernel to the older version of Siyah used in the rom?
If so, can I just flash in the newer version using Odin or should I research another method?
This is my first root/mod so I'm still a little nervous about messing up.
Click to expand...
Click to collapse
yes this reverted to the older kernel included in the rom, to flash the newest kernel. Load the zip of the kernl onto your sd card, enter CWM and flash the zip. Much easier to do than with odin.
Thanks! I was pretty sure that was the case but figured I should ask anyway. I've been lurking these forums for a while and it's awesome how helpful this community is to everyone.
While on the subject of ICScreweD, is there anything I will lose by going to the green edition? The website is kinda unclear as to if there are any features not yet available in the green edition.
Kasdarack said:
Thanks! I was pretty sure that was the case but figured I should ask anyway. I've been lurking these forums for a while and it's awesome how helpful this community is to everyone.
While on the subject of ICScreweD, is there anything I will lose by going to the green edition? The website is kinda unclear as to if there are any features not yet available in the green edition.
Click to expand...
Click to collapse
This is the list of things that differ from the Blue edition which is 2.0.1 and the green edition which is still 1.6.2. Quiet a few differences and it is more up to date.
Version 2.0.1 (Changes since 2.0 are blue) (Full Wipe Required) BLUE EDITION ONLY AT THIS MOMENT
Updated to XWKL1 (Much smoother and improved battery life. Also resolves WiFi issues.)
Siyah v2.6.7
Added Roboto Font
Updated to Jkay v13.4.1
Added LiveWallpapers Support back
ICS & GB Ringtones, Alarms, and Notifications
ICS Boot Animation much sharper and true black
Bluetooth On icon enabled
Removed screenstate scalling
Removed Fancy Rotations (It will be added to the add-ons section)
CPU Governor set to OnDemand
Double Setup is fixed. It was being caused by GoLauncher. So setup will not be prompted when phone first boots. You will see the normal homescreen then about 20 secs later it will appear.
Added CWM Manager v3.0 by Chainfire
Removed MiLocker (You can grab it from the market if you want to continue using)
Phone APK
- Rethemed it slightly again.
Camera APK themed thanks to ssconceptz Click here to show him love
Google Music moved to Data/App/ (So you can remove it and add any music app if you do not want to use it.)
GTalk issues fixed.
Updated Following Apps
BLN Control v1.3.8
File Manager v1.12.4
GO Launcher EX v2.76
Kies Air v2.1.112201
Maps v6.1.1
Voice Search v2.1.4YouTube v2.3.4
yoderk said:
This is the list of things that differ from the Blue edition which is 2.0.1 and the green edition which is still 1.6.2. Quiet a few differences and it is more up to date.
Version 2.0.1 (Changes since 2.0 are blue) (Full Wipe Required) BLUE EDITION ONLY AT THIS MOMENT
Updated to XWKL1 (Much smoother and improved battery life. Also resolves WiFi issues.)
Siyah v2.6.7
Added Roboto Font
Updated to Jkay v13.4.1
Added LiveWallpapers Support back
ICS & GB Ringtones, Alarms, and Notifications
ICS Boot Animation much sharper and true black
Bluetooth On icon enabled
Removed screenstate scalling
Removed Fancy Rotations (It will be added to the add-ons section)
CPU Governor set to OnDemand
Double Setup is fixed. It was being caused by GoLauncher. So setup will not be prompted when phone first boots. You will see the normal homescreen then about 20 secs later it will appear.
Added CWM Manager v3.0 by Chainfire
Removed MiLocker (You can grab it from the market if you want to continue using)
Phone APK
- Rethemed it slightly again.
Camera APK themed thanks to ssconceptz Click here to show him love
Google Music moved to Data/App/ (So you can remove it and add any music app if you do not want to use it.)
GTalk issues fixed.
Updated Following Apps
BLN Control v1.3.8
File Manager v1.12.4
GO Launcher EX v2.76
Kies Air v2.1.112201
Maps v6.1.1
Voice Search v2.1.4YouTube v2.3.4
Click to expand...
Click to collapse
Green is upto date thought I removed the blue only thing
Sent from my SGH-I777 using Tapatalk
Flash with cwm and enjoy, bdw prees thanks buton
igorkode said:
Flash with cwm and enjoy,
Click to expand...
Click to collapse
Will this work in ICS 4.0.4? Could you improved the code to suite it the the latest update. Thanks...
Same stuff in ICS... look in /system/etc and you'll find the hw_config.sh
I tried on CM7.2 but I see no difference.
The screen does not adapt to the environment light, even blocking the sensor with my finger does nothing.
any ideas?
thanks in advance,
Aris
Out of the box - SE did not enable the Ambient Light Sensor... In order to get this working one needs to modify the /system/etc/hw_config.sh file.
FXP appear to have missed this going even as far as closing an open 'issue' (issue N° 254 here) that is complete with a full description on the fix without actually fixing the problem...
igorkode's .zip allows you to easily fix this using CWM however I feel this is a little drastic... Don't get me wrong- it works but it overwrites the hw-config.sh and als_curve.conf files without regard for what was there before.
I suggest that you look through the optimisation guide here as this explains in more detail the modifications necessary.
works great for me, i dont care about the automatic light sensor anyway.
fixed the "low brightness after standby"-issue for me and thats all i wanted
thanks!!
Hi all! Will this work in CM9?
deckHUN said:
Hi all! Will this work in CM9?
Click to expand...
Click to collapse
Yes, it works in CM9.
It works well on FXP130!