yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] coal686:
Try flashing the camera mod here:

http://xdaforums.com/showthread.php?t=1717113

Known issue. Since you are s-off, you can flash GB Roms if you downgrade your hboot first. Then play the games. See s-off is nice. :D

Read, Search, Read again, ... Then Ask with Tapatalk 2
[HTC EVO 3D] GAPO:
Thanks. And yeah Gameloft has said that their games for the Evo 3D are not yet compatible with Android 4.0 for the 3D. Yet. Who knows if/when...?

Also, on MeanROM ICS, I accidentally hit the Blockbuster app icon, and got a warning from within the app that said:

"Tampering detected! You will not be able to download or view any encrypted content."

lol
[HTC EVO 3D] coal686:
Yeah, that app checks for root. :D

Read, Search, Read again, ... Then Ask with Tapatalk 2
[HTC EVO 3D] GAPO:
Anything else I can flash to maximize my MeanROM experience?
[HTC EVO 3D] coal686:
You could also try the coolexe beats mod.

Read, Search, Read again, ... Then Ask with Tapatalk 2
[HTC EVO 3D] GAPO:
Anybody know if Hotspot works on MeanROM?
[Off-topic] xz1llox:
Ok so I've had my custom built pc for two years now and I've hit a snag I just can't figure out...

Specs

-AMD Phenom 1055T stock specs

-Asus M4A87TD mono

Corsair GS700 PSU

-4GB ocz gold

-PNY 550T GPU

-Corsair H60 CPU cooling

-Seagate Barracuda HD

First error I received was "Enter setup to reset default bios settings.USB over current status detected system will shut down in 15 seconds"

Looked into the error message and all I could find is that the front USB ports could be defective so I disconnected them and rebooted and still nothing.

When I try to boot into the bios settings it still sends me straight to the error message. I took everything apart to check for a possible short to the case and found nothing.

After reassembly the computer is not detected by the monitor anymore what so ever. Everything is receiving power all components are operating (so it seems. All fans running HD is spinning etc) but no image will be displayed.

Anyone have any idea what my issue could be? Open to any and all suggestions before I start throwing parts at it.

Thanks,

Dan
[Off-topic] Archer:
There's a thread for PC issues...

http://xdaforums.com/showthread.php?t=1765837

Thread closed.
[Samsung Galaxy W I8150] eryzerz:
Hello, i'm new here. Sorry for noob question, i use v6 supercharge to this rom for better management ram. But, when i play temple run its very lag. Before i use v6 the game is still smooth, but when i run of a lot app its bit laggy and free ram is very low. I know its risk if i use ics. But, is there any script to manage the ram and its compatible with paranoid rom?

Sorry*again* for my bad english.:D i hope @doomsday94 see this:rolleyes:
[HTC Inspire 4G] Riomaru:
I tried to acheive S 0ff by this method

Make sure you have already gained radio S-OFF by following the above-mentioned steps.
Download the Engineering HBoot for HTC Desire HD and extract the contents of the zip files.
Enable USB debugging (if not already enabled) and connect your phone to the computer.
On your computer, launch Command Prompt/Terminal, navigate to the folder where you extracted the files in Step 2 and enter these commands:
adb push hboot-eng.img /data/local
Finally, launch Terminal Emulator on your phone and enter these commands, being EXTREMELY careful not to make any mistake here:
su
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18

After I finished I rebooted and my phone will not turn back on, I can plug in the charger and the LED will turn orange but other than that nothing.

Any help will be most appreciative
[HTC Inspire 4G] glevitan:
If your phone was shipped with gingerbread then you messed your bootloader. You are advice not to do that....
[Samsung Captivate Glide] inthepit:
its real nice to finally have some ICS goodness on my phone, but i have found some issues.

my Motorola Roadster 2 bluetooth speakerphone does not work well with this version of ICS. will not let me use the call/text button.

i am finding some apps not working correctly, i.e. Pushover - the notifications do not make a sound. Not sure if that is an app issue, or an ICS issue.

*edit* ok so it seems that i am not getting any notification sounds. sms, voicemail, etc...

also the volume in general does not seem as loud as the 2.3.6 firmware was.

anyone else find any issues?

*UPDATE* after wiping within cwmr most of my issues were no longer present. the only problem i had still was that notification sounds didnt work after a couple hours. i dont know the cause, but i used audio manager widget and set the profile to loud, and restarted phone. havent had them go out since.
[Samsung Captivate Glide] jayjayjoker2:
I have all these issues except tue bluetooth thing
[Samsung Captivate Glide] inthepit:
atleast it is not me.

i am going to reflash my phone to see if it may be an issue with not clearing out the phones memory and storage first...
[Samsung Captivate Glide] Tyfighter:
My wifi didn't work for a while. It would see my access point but wouldn't connect. Reset the router and everything went back to normal. GPS works, Stereo BT/OBEX works, 4G works, camera works. Those were my big items, as I'm sure they are most people's.

My only issues are that I can't switch to 2g (At&t rom....) and how friggin Touch-wizzy everything is. I was expecting them to embrace the whole holo thing a lot more, but all the buttons feel like they belong in GB, same with the notification menu and the settings icons.

EDIT: I am on rogers, in case any rogers people see this so they know that everything works on our network
[Samsung Captivate Glide] inthepit:
i wiped via cwmr and reflashed the ics rom. notifications work again. have not rooted yet, wondering if that may have been an issue with it...
[Samsung Captivate Glide] Gab1288:
Changing the lcd DPI causes the rom to corrupt i guess, since when i do it, after the reboot, i get to the samsung "logo" and then black screen, and it feels like the device has shut down. The only app that would say "success" when i change the value is Lcd Density Modder.

- i had the notification sound bug, but then i changed the notification sounds to my likings, and then i used Audio Manager widget to set the volume loud, no problems ever since.
[Samsung Captivate Glide] inthepit:
ok rooted and all is fine. maybe i just had a bad flash. my bluetooth speakerphone still doesnt work, but that is an issue that i will have to research
[Samsung Captivate Glide] braintweaker:
For me, i had the only issue with ICS (excluding the known thing with the keyboard not flashing) - timezones from 2011 year with wrong summer times.

Luckyly fixed it with timezone fixer from google play.
[Samsung Captivate Glide] chyckyn:
Tethering doesn't work, seems to be broken and results in a blackscreen.. Both Usb and Wifi Hotspot give this issue.. Anyone else getting this:confused:
[Samsung Captivate Glide] AzraelsKiss:
One weird thing my phone does is when it's been asleep for a while, the lockscreen clock will fall behind and when I wake it up, it'll catch up a couple dozen minutes at a time.

~Azrael's Kiss~
[Samsung Captivate Glide] Nardholio:
Wifi is slooow, getting 800k when I should be getting 20mbs
[Samsung Captivate Glide] jvuong:
My wifi still not working

I'm on rogers too and my wifi is till giving me trouble. I haven't tried the resetting the router yet, but at work it doesn't connect too. Anyone else having this problem.:eek:
[Samsung Captivate Glide] ninthsense:
I've rogers version but unlocked and working with a local carrier. Wifi is not a problem at all, i'm getting the same speed and used wifi continuously for over 2 hrs to download all my apps back after the update.
[Samsung Captivate Glide] doode2011:
When typing with the keyboard, pressing the alt. Key once makes it select all the special characters. I liked the older one where if you press it once, it operates just once when selecting the special character, and pressing it twice makes it select more than one. Not that big of an issue but to some people it may be.

Also, the brightness thing. When I turn off the screen, and turn it on again, it flashes from the highest brightness to the current.
[Samsung Captivate Glide] bakageta:
On AT&T here, and having wifi issues as well... Once the phone drops wifi at idle, it doesn't want to pick it back up unless I turn wifi off and back on again. Setting the wifi to never sleep has been my only workaround.

Also having some issues with the button backlights. If I don't touch the phone long enough for the button backlight to turn off, touching the buttons won't turn the light back on. Touching the screen turns the backlight on again, but it's slightly annoying.
[Samsung Captivate Glide] bobbinthreadbare:
I haven't noticed any wifi issues and I use my Glide exclusively as a wifi device. I'm copying my backup of Inception v2 back right now though because the battery drain on the ICS ROM is definitely an issue. Losing like 10% an hour with my phone just sitting there with the screen off.
[Samsung Captivate Glide] inthepit:
so weird everyone having battery problems. mine runs better than it did on stock 2.3.6 and the battery lasts longer....
[Samsung Captivate Glide] bobbinthreadbare:
Have you ever took note of your battery life with a custom ROM or kernel? When I picked up my Glide it had a stock ROM but I only had it for an hour before I put a custom on it. I didn't mess with the stock one at all so I can't compare to stock 2.3.5/6. But with Inception v2/ardatdat, it was definitely better.

I was going to restore my backup but copying it back to my phone made me realize how painful it is to copy backups with CWMR 6 compared to 5. That new blobs folder makes so many files that it took 3 hours to copy 3 of my backups over USB. Ouch.

But since last night, the battery life seems to be behaving better. Its been sitting here and not just dying. :) I'm wondering if it could be the battery stats file. Maybe I'll try wiping it. I'm sure once we get a lower voltage kernel and I can underclock with profiles for the screen-off and stuff, it'll be fine again.

Unrelated but has anyone taken a screenshot with the ROM yet? ICS is supposed to have it built in, power button + volume down at the same time for a few seconds from what I read, but didn't seem to work.

Edit: Its home + power button at the same time.
[Samsung Captivate Glide] jvuong:
Damn i hope its not my phones wifi:crying:
[Samsung Captivate Glide] inthepit:
when you flashed ICS did you wipe everything then run the ics installer? my first install sound and such didnt work, so i wiped the phone in cwmr and reflashed ics and it is better that it was on 2.3.6
[Samsung Captivate Glide] Tyfighter:
Wifi has been a continuing issue for me. I usually have to reset the router when I get home from work. It just won't connect until I do so... a bit of a hassle but I can deal.

I also have been unable to use the built in wifi AP. Haven't tried a third party app for it yet... haven't found one that's worked for me in the past evenunder more optimal conditions so I don't know if I'll even bother.

I have just discovered what I think my be my favourite UI update though. There is a notification bar icon for vibrate+silent instead of an icon for vibrate and an icon for silent. I usually keep my phone in vibrate+silent so it used to drive me insane that I had to devote two icons of space to that in my notification bar.
[Samsung Captivate Glide] bobbinthreadbare:
Nah. It appeared that the ICS flash program wiped everything on the internal memory anyways. My battery is still acting much better. I haven't done anything to it, but whatever. ICS appears to be working spot on now.
[Samsung Captivate Glide] tienlp:
- Asphalt 6 and 7 purchased from the Play Store is incompatiable, they always say "Invalid license"

- Some other licensed games like Where's My Perry freeze in a few seconds right after opening, the only solution is restart the phone by removing the battery

- No back light for the external keyboard

- Themes, launcher and lockscreen are the same, actually no one would believe that i'm using an ICS ROM until I show them the system information

- I couldn't unlock it, repeat the same unlocking way as 2.3.6 but the phone still display the "no service" dialog everytime i try to make a phone call
[Samsung Captivate Glide] Tyfighter:
Hey! Be fair! They're all ever so -slightly- different from the gb ones.
[Samsung Captivate Glide] tienlp:
yep there are differencies =D but nvm they should focus on improving the compatibility rather than changing the theme :laugh:
[Samsung Captivate Glide] roothorick:
Mine unlocked first try with the code I bought with it originally. I've rebooted several times and it remained unlocked every time. The hack method may not work but codes definitely still do.
[Samsung Captivate Glide] ludacris1:
This rom is unstable... everytime when a force close dialog should apear the phone freezes completely and sometimes it loses root acces and the only way to restore it is to reflash the rom (not the superuser zip)
[Samsung Captivate Glide] doode2011:
What is force closing and did you update superuser? Today, there was an update for superuser from the market and I updated it. Then every root asking application I had would freeze and I would need to restart the phone. Don't update the superuser, because if you do, you'll have more freezes.
[Samsung Captivate Glide] ludacris1:
When an app is ''hanging'' or is very busy a dialog came up in gingerbread asking if you want to force close it or wait.

Also I've tried a app which i know won't work on ics.. on other phones with ics it just gave a force close and didn't open, here it frozen up everything.

On the ics leak i've never seen such a dialog, the rom simply freezes completely instead.

I used SU 3.2-RC3 from androidsu.com/superuser/

and I also tried the cwm flashable rom from today.. same issues. :mad:
[Samsung Captivate Glide] doode2011:
I suggest that you get the superuser zip again and the es file explorer (enable root) to verify if superuser is working. And from there on, every time you go on es file explorer, it'll give you a notification that it has root access. Then if random apps still freeze, it might be a bad rom flash. I'm just trying to give you suggestions to weed out the causes of freezing and be able to act upon it.
[Samsung Captivate Glide] joshua_tam:
I can confirm that freezing occurs when some app is long waiting / force closed, as currently I use this leak in the development device, I found that the phone will freeze everything I got something wrong.

I think it is not related to SuperUser app.
[Samsung Captivate Glide] ludacris1:
I don't think this has something to do with the superuser.. I think it also occurs on pure stock, but I'm too lazy to flash again,

I'll stick with gingerbread until a new rom is out.
[Samsung Captivate Glide] :
Just want to give a head's up: fast force close on the market fixes the freezing issue.
[Samsung Captivate Glide] ludacris1:
It would close everything even if its just hanging, wouldn't it?

Because freezing also occurs when a app is hanging, not only if its going to be force closed. :rolleyes:
[Samsung Captivate Glide] :
Actually, I think you're right. Some very odd things happen when I have that enabled, like superuser won't throw up a prompt and won't grant root access unless I have it set to auto allow. So it does seem to be blocking anything from freezing the system, not just force closes.

I haven't been able to confirm it yet, but I have a suspicion the force close freezes have to do with this ROM waiting for a debugger. The only way to change the debugger settings though is through development.apk, and it requires the system key. You'd have to resign the kernel with a different key or set it to unsecure. I'm going to have a look later to try and figure out how to actually do that.
[Samsung Captivate Glide] etherfish:
insights into keyboard backlight issue.

These types of efforts only achieve great things if everyone pitches in, right? So, here's my first attempt. Regarding the 4.0.4 leaked ROM, it struck me that missing keyboard backlight support was probably not a core-kernel feature. I suspect that lighting the backlight is done in a userland library responsible for reacting to keypresses. So, I set out searching for clues. I've had my captivate glide now for 8 hours or so.

I initially disregarded /sys/class/sec as likely to do with paranoid security stuff, but a recursive grep for stmpe (the chip from st micro doing the keyboard matrix) discovered an entry:

/sys/class/sec/sec_stmpe_bl

A guess is maybe "stmpe backlight?" The other files in that directory seem to be somewhat secondary/ancilliary function, as if /sys/class/sec was a bit of a dumping bucket. In hindsight, it may be an attempt at a uniform place for GPIO handlers? Anyways, inside that sec_stmpe_bl directory is a virtual file called backlight with rw permissions. cat'ing it gives a strange invalid length error (hexdump reveals that it's EIO). However, echo 1 > backlight turns the keyboard backlight on. echo 0 > backlight turns it off. If you turn on the backlight and let the screensaver/sleep whatever engage, it turns the backlight off.

Hence, I believe that something isn't properly engaging the backlight. Continuing with my hypothesis that a userland app is responsible for switching on the backlight, I greped the strings output of /system/lib/libinput.so for "ack" and found a string " to control touch backlight at bottom " - not sure what that means. From the look of the mangled C++ symbol names, it's clear that there's an elaborate system for disjoint pieces to register for callbacks on input events, etc.

I suspect that in some java or other UI code there's a missing line that says, "if key is pressed, enable backlight." That or some other library. It's 5:30 am, so I'm going to go to sleep. I'd have posted this in the developer boards, but I'm unable to until I post enough posts. I guess I'm a, "long time reader, first time poster."

Cheers, hope this helps.

p.s. on 4.0.4 leaked rom w/ the root instructions involving superuser and such.
[Samsung Captivate Glide] ninthsense:
Found a difference in the GB boot.img vs the leaked ICS boot.img. In the init.n1.rc the following line is missing from the ICS boot.img :

# STMPE QWERTY backlight

chown system radio /sys/devices/virtual/sec/sec_stmpe_bl/backlight

I guess the init file is responsible for initialization of the library ?
[Samsung Captivate Glide] etherfish:
that line appears to set the permissions on the virtual control file allowing non-root, system programs to change it. Incorrect permissions could certainly cause whatever is supposed to be controlling it to fail. Is it very difficult to modify /init.n1.rc to add such a line?

Unfortunately, another possibility, according to the stored kernel build configuration in /proc/config.gz is that the LED driver class is missing. I only mention that because most people expected the backlight control to be somewhere else. I'm sorry, i'm so very new to this.

cheers.
[Samsung Captivate Glide] :
Don't have time to try this, but I wonder if

http://modmymobile.com/forums/562-m...2-there-fix-keypad-backlight-not-working.html modified with our device name would work while someone is modifying the boot image (although making this change to the boot image would be trivial)
[Samsung Captivate Glide] etherfish:
That's a clever approach. I'd increase the sleep value to something like 5 or 10. It's not as ideal as a proper fix, but it may just do for the time being. The filename would need to be changed, yes, but it could very well work. I think I'll try it when I get up.
[Samsung Captivate Glide] etherfish:
potentially discovered typo

The thing that has nagged me, is that the backlight is correctly deactivated when the screen is locked/blanked. Anyways, I did a more thorough search for stmpe-bl in the original 2.3.6 and discovered /system/lib/hw/lights.n1.so. In the file (5k pretty small.) I found the following strings:

backlight

buttons

keyboard

lights

write_int failed to open %s

sys/class/sec/sec_stmpe_bl/backlight

/sys/class/misc/melfas_touchkey/brightness

/sys/class/backlight/pwm-backlight/brightness

NVIDIA Ventana lights module

however, in my 4.0.4 version, I found:

backlight

buttons

lights

write_int failed to open %s

/sys/class/misc/melfas_touchkey/brightness

/sys/class/backlight/pwm-backlight/brightness

SAMSUNG BOSE lights module

Notice in the newer version, the "keyboard" and sec_stmpe_bl entries are omitted. I wonder if using the 2.3.6 lights.n1.so on 4.0.4 would work?
[Samsung Captivate Glide] :
THANK YOU IT WORKED!!!!

Here's my modified boot.img and the /system/lib/hw/lights.n1.so from Gingerbread. Modifications made to boot.img: Kernel set to debuggable and unsecure. Seems to fix force close related freezing. Permissions for keyboard backlight added to init.n1.rc. Note that flashing the boot image will not be necessary if all you want to do is make the keyboard light up. Just copy the lights file over your existing one and reboot.

EDIT: Both files are in fact required.

Instructions for flashing boot.img from adb command line:

NOTE: I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. DO NOT DO THIS IF YOU DON'T EVEN KNOW WHAT ADB IS.

0. Ensure at least 50% battery charge

1. Copy boot.img to sdcard

2. Open a terminal window and type su or open adb shell and type su or open adb shell from CWM (recommended to do from CWM)

3. If using CWM, ensure /sdcard is mounted

4. Execute following commands

dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9

5. I wiped cache and dalvik cache, not necessary but doesn't hurt

6. Reboot.

7. If it doesn't work for whatever reason, reflash stock ICS available in the development section
[Samsung Captivate Glide] jayjayjoker2:
Adding to my ROM
[Samsung Captivate Glide] inthepit:
copying the file does not seem to enable the keyboard lights. i copied the file over, checked and changed permissions, reboot, and no keyboard lights...

is there something i should check?
[Samsung Captivate Glide] bakageta:
This does fix the keyboard lights, but doesn't fix my issue with the button lights, namely if you let the lights time out, touching a button won't light them back up, you have to touch the screen. Also note that I wasn't able to get /sdcard mounted in CWM 6.0.0.1 for some reason (user error? *shrugs*), I flashed back to CWM 5.x and had no problems.
[Samsung Captivate Glide] ninthsense:
The difference is that 'bakageta' is flashing the boot.img which has the .so file already baked in it vs. 'inthepit' is copying the file manually from some explorer. Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.

I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work for the keyboard light and bring them back to life.

I would have confirmed it myself but do not have the resource to do so until i return home ( 8 hrs to go.... :crying: )
[Samsung Captivate Glide] :
Ok so maybe you do need both files. I didn't think it was necessary. The boot.img does not contain the lights file, only the permissions for the lights folder. Didn't think system needed the rights but I guess it does.

Also thank you again etherfish and ninthsense for discovering what was wrong! As to the question of the capacitive lights, the only thing that is making them turn on is touching the screen, but other things, like using the keyboard makes them stay on if they're on...
[Samsung Captivate Glide] ninthsense:
Hi Nardholio, can you confirm the procedure you use to copy the .so file ? From my understanding it resides inside boot.img, so you've to flash the boot.img first and then copy the .so file and reboot to make it work? Are you using terminal in CWM for copying ?

I maybe missing something very basic here, please ignore for so many question as i'm trying to learn.