Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.
Related
Does anyone know of a resolution to the device going to sleep after a specified time and not re-waking? I tried the Backlight setting and Power setting, but the device seems to go to sleep and not wake up. I have to soft-reset it get it to respond and even phone calls go straight to voice mail.
any help is much appreciated
I had the same problem. It's so random that it's hard to find out a reason
feareddevil said:
Does anyone know of a resolution to the device going to sleep after a specified time and not re-waking? I tried the Backlight setting and Power setting, but the device seems to go to sleep and not wake up. I have to soft-reset it get it to respond and even phone calls go straight to voice mail.
Click to expand...
Click to collapse
What ROM are you running? What radio and ipl/spl do you have? I have to say I've never seen this on any of the WM6 roms I've been on (MBE, mUn, nottoosmart, faria, xplore). I wonder if its some 3rd party app thats misbehaving / conflicting with WM6? Are you running any Spb programs (a couple of those seem to have issues with WM6 in other ways).
Not sure how often it happens, but if possible you should go back to a clean flash of the rom and try using it just that way to see if the problem still happens.
3DES.2 ROM
SoftBank X01HT
Cingular Network
ROM: 3.23.0.2
Radio:1.38.30.10
OS:5.2.968 (B 17736.0.2.0)
Protocol:32.71.7020.12H
HERM200
I am concerned about reflashing, since I already bricked a device trying to roll back to an original rom (and I did read wiki) Any help is greatly appreciated. I boot fresh and do nothing but press the power button to turn off the screen and it happens everytime, the greenlight still blinks but nothing happens.
feareddevil said:
HERM200
Click to expand...
Click to collapse
Well, keep reading this forum and you will probably brick it again! You do realize you are reading the Wizard forum and not the Hermes forum???
If I set the minimum cpu speed to 130mhz or below I get the exact same problem, Are you using battery status or some other omap scalar program?
uugg-- sorry guys, I read the Hermes forum, but clicked the wrong link when I was mobile and posted the first message.
I am not sure if I am running a slower mhz. Is that default on 3DES.2? I will research how to change but if you can tell me quickluy - I will gladely take instructions to test.
The only way to change the speed is if you are running something like BatteryStatus or OMAPCLOCKplus or XCPUSCALER. Those will allow you to set a "min" on your phone and will drop your CPU down to the min when you aren't doing anything. So if the min is set to low, you phone can lock up similar to what you are describing.
You'll have to find out from other Hermes users what a good min is for your device. Personally on my Wizard I set the Min to 143 or 147Mhz. It can go lower, but I don't think it makes that much difference and don't care to find the bottom that works before I have problems. Just like I run a max of 260Mhz. I know I can run 273, but I don't see much difference, and really don't want to have issues by running faster when I can't see a performance gain (but thats just me).
Good luck!
Thank you everyone. I have narrowed it down to the powersave.dll. When I disable this - it no longer causes the lockup issues. I did not try adjusting the min value but it does appear to be the issue as I will assume - that powersave option does exactly as you outlined above.
regards and thanks again.
This is a common problem if you have installed a "Today" application on a storage card (the microSD card). If you did this, reinstall to the main memroy any Today application or any application that is in the "'windows\startup" folder.
ever since the android port came out and i tried it ive loved how the hardkeys light up when you touch them and then immediatly go away. is there anyway to get that on wm?
yeah same here. thats so f#$*n awesome
love to have it on wm
soulds like it would require a touch detector hardware system along with the full preasure detector there already is
Rudegar said:
soulds like it would require a touch detector hardware system along with the full preasure detector there already is
Click to expand...
Click to collapse
it already works with our device. Its just part of the android port that can be found here http://www.htc-android.com/viewtopic.php?f=5&t=237
im suprised no ones tried to do this yet?
i have to say i honestly loved that too. though i would miss the touch to light up all keys so i could see them in the dark. then again, thinking as im typing, i would trade for the android style. i dont think i can make up my mind!
Mine does that already.
are you running android or something? if you got it to work with windows share with the class.
Mr.Sir said:
Mine does that already.
Click to expand...
Click to collapse
How did you get this working?
Please share what you know
android still doesnt let us make calls texts or data on our raphael right?
yep, no sound, data, text, phone, proper keyboard support, wifi, bluetooth. but atleast the capacitive navipad works.
haha that navipad is most important
i tried using android last night followed the instructions . how long did bootup take for you guys? it sat on the text page with the blue box for like 40 minutes and never went farther
Wow, didn't know we could boot Android on our phones.
I didn't try that yet, because from tomorrow I will be traveling for a week, and I will need my phone.
I downloaded it though, and on the installation instructions it says to launch haret.exe, I didn't get that, is this some kind of virtual machine, or will it shut down WM and launch Android?
Smaniac said:
Wow, didn't know we could boot Android on our phones.
I didn't try that yet, because from tomorrow I will be traveling for a week, and I will need my phone.
I downloaded it though, and on the installation instructions it says to launch haret.exe, I didn't get that, is this some kind of virtual machine, or will it shut down WM and launch Android?
Click to expand...
Click to collapse
It shuts down WM and launches Android. It isn't a permenant flash because not everything works on it. Android itself loads fine, but there are still some key linux drivers that are required for normal day to day use. The more important thing is the microphone/speaker. The phone works and things like SMS.
player you have obviously had it working
how long does it take to boot for you?
i have the tmp folder on my card with the boot folder in that. in there i click haret18.exe then the box comes up saying it will run default.txt then linux starts and i just get all the small writing on screen but it never goes farther
EDIT- i was told it must be the wrong version. i have the fuze so which raph is that? i tried two diff versions already
you need to either rename the text files in the boot folder or choose the one you want.
If you have the fuze use the raph100 I think it is...don't have my phone on me, but it isn't the 800 one.
I just renamed the default.txt to something else and then the default _raph100 or whatever to default.txt and it worked fine.
Before I realized this I had the same issue you did.
thanks i got it running
so is there really anything we can do at this point? or just play around with the home screen
soooo anyway back to the question i asked... lol
has anyone or is there a way to make it work to when you touch the pad only the area you touch only lights up like it does in the android port?
Wow after loading up the latest port of android, I finally understand what the OP means, this is really cool! I would love to have this. Not only does it look cool, but it will actually reduce error due to pressing the wrong part of the button.
lbhocky19 said:
thanks i got it running
so is there really anything we can do at this point? or just play around with the home screen
Click to expand...
Click to collapse
No, as of right now nothing is really working besides Andriod running. No data or voice services work yet...
you can mess with home AND navipad. cant forget what this thread is all about. i think the fact that you can run android and do it without wiping wm is pretty amazing. theres alot of work that needs to be done if you are planning on doing something useful with android. the phone was meant for wm and is set more up with drivers, configuration, and development for such. hopefully in the future it will do both well and your epeen length will grow as you show off to everyone what your phone can do.
Hi I don't know if this is the right place to put this info.
I see lots of people are having the dialer battery drain issue in pretty much every version of android 2.3.3. And I haven't seen a working solution anywhere other than upgrade to a newer version of android.
Any way, I'm using a HTC legend a gingerbread version 2.3.3, and I have always had the dreaded dialer battery drain issue.
I have found a work around that helps stop the drain, at least on the HTC legend 2.3.3 version I'm using.
In my case it is simply having the line
gsm.proximity.enable=false
In the build.prop
It would seam to stop the proximity sensor from working with the dialer part of phone.
The only side effect I have seen so far is that the screen won't turn off when u hold phone upto your ear, you can of course turn screen off with power button, at least from a legend point of view.
I hope this information will help others with android 2.3.3 on other phones that also have dialer battery drain.
Sent from my HTC Legend using XDA App
Hi, here's a bit of an update for those that are interested, even though the proximity sensor has been disabled for phone calls after adding the line to build.prop, here is a work around to allow the proxy to turn off screen again.
Down load "proximity screen off" from the market, in the settings, select enable during calls only.
Now on my phone the other settings seam to be a bit screwy so you'll have to play with them to suite your device for the way you want it to work.
I am still testing to see how battery life is, but so far its looking good.
If you feel like it, I would appreciate some feedback regarding these mods.
Thanks
Sent from my HTC Legend using XDA App
another point of attack
So.. It seems CyanogenMod team has identified these proximity sensor issues and actually fixed most all of them (on the devices they support). The answer is complicated and nestled into the code. But basically one could say there has been an omission of suspend and wake calls that now make MANY HTC devices not function properly. So, besides this there are SoD issues with some devices after a call.. Same type fix used to resolve and that one usually is resolved with an OTA fairly quickly... But ummm, why can't HTC users ban together and make HTC perfect their sources? They are after all the manufacturer and Sense roms are just copies of their source (modified here and there perhaps)... so the problems have been identified, solutions have been committed by an OPEN SOURCE team... good lord HTC, this has been going on since the Desire.. and just browsing I found Legend, Wildfire S and several others effected..
Great work-a-rounds btw... I just really think the consumers should petition on these issues as they are all related and fixable. Most just hear battery life sucks on the Android and assume their phone going dead after 5 hrs is normal... Well it's not. Just my 2c.
Rob
helppp...!!! pls
im also usin ogoo's rom having battery drain problem.. im kinda noob
cn u tel me specifically wht to do?
nd wht is? build.prop
akashj17 said:
im also usin ogoo's rom having battery drain problem.. im kinda noob
cn u tel me specifically wht to do?
nd wht is? build.prop
Click to expand...
Click to collapse
Well my friend , I was a noob about 7 or 8 months ago too, I did lots of reading and learning and used Google to find my answers.
But here's some quick help to get you started....
Before you do anything if you haven't already do a nandroid backup.
You are using ogos gingerbread so you must be rooted yeah, OK so next we need to find out how u rooted, if you went down the hboot 1.02 and unlocked boot loader method, that is great makes my job much easier.
Build.prop is a file located in the
/system/ folder
It is basically a text file that contains a list of settings/commands/startup options.
In my ogos rom the command in question has a # in front of it which disables that line.
You need to edit that file and remove the #. To do this I used es file explorer with root turned on in settings, then just went to /system and opened it with es file explorer.
Or you could get build.prop editor from market and add the line that way, however you need to leave out the = and put the stuff in front in the top field and the 1 In the other.
Simple as that....
If you are say hboot 1.01 and s-on then that's a lot harder for me :-(
You'll only be able to do it via fastboot method, reboot phone into fast boot menu volume down then power. Connect to your PC, it is properly set up isn't it yeah? use android commander to copy that file to your PC, edit file using notepad then copy it back.
If you done it right, good if not, ummm you might need to search for answers for to what you need.
You could always send your phone to me and pay me I only charge $100 per hour lolol
Sent from my legend using XDA
Thnxxx........ Ranger
I am running Dman's rooted stock UCLB3 with Entropy's DD and Voodoo Lagfix. I love the setup but one this is really bothering me: I can't set the screen security time. I like the screen to go off in 15 - 30 seconds, but I want to be able to decide how long it will be until I have to use the security unlock. Now, there used to be a setting for this under Location and Security, but for some reason it is no longer there. Is it this ROM or is this missing from all 2.3.6 builds (i.e. stock)?
In case you aren't following me, I am attaching two screenshots, one from Samsung's website, the other from my phone. As you can see there is no "Timeout" menu on my phone. Was this somehow stripped from Dman's ROM (not impossible since the android.policy.jar file - the one that I believe is related to this menu - sometimes encounters issues from deodexing) or is this feature just gone from the phone? If it was stripped, how might I go about getting it back?
This is driving me mad right now, so I'd love to hear a definitive answer.
The setting that you are looking for can be found under Settings / Display. It wasn't stripped, you're just not in the correct menu.
No, that is a different setting. You'll notice that the display setting is to determine when the display will go to sleep (when it will automatically turn off), the setting I am talking about determines when the screen will lock after the screen turns off.
There are two programs with similar functions: Delayed Lock and JuiceDefender Ultimate. However, I suspect that the phone setting is still partially alive somewhere because both programs seem to wreak havoc with whatever settings are now default.
Oh, okay, now I understand. That feature isn't available in stock UCLB3, and there were no issues when deodexing.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Thanks. That's basically the answer I wanted. I've been poking through the guts of both the stock and rooted builds trying to find out what happened. It is really irritating that it's not there (well, for me it is!) because the security screen seems to have a mind of its own, particularly if you introduce alternative lockers into the mix.
For anyone who may be interested, you may be able to set the timeout by editing values in the android.policy.jar file in framework folder. Search around, you'll find instructions. I haven't tried this.
The two apps I have found that enable this functionality are Delayed Lock and Juice Defender Ultimate. However, neither app works well with 3rd party security locks such as Go Locker. The lock delay apps trigger the system security screen lock so you may have to go through as many as 3 screens before you get to your home screen.
Sorry, there is one other app: Password Delay. I did not try this because I want to use a pattern lock. PD does not work with patterns.
Yeah, join the club lol. I just learned to deal with it after a while. But I hear you. Tried looking for some alternative ideas... and I just kept unlocking everytime.
Sent from my A500 using Tapatalk 2
Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!
My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.
What rom?
Sent from my LG-P999 using XDA
redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/