yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] sm_abu:
Youu will not get root access if you flashed it via odin, download cmw version of it and.flash
[Galaxy S II Q&A, Help & Troubleshooting] droid_s2:
philz kernel

first of all i clicked thanks already. Hehe.

Could you please send me the link where i can download philz kernel for jb.

It would be a great help.

I have stocked jb leaked and i want to change to rainbox.

Ill click thanks again just guide me where can i download the file.
[Galaxy S II Q&A, Help & Troubleshooting] ankur.co.in:
Here is the link bro sorry for late reply btw thanks for your thanks ;)

http://xdaforums.com/showthread.php?t=2031042
[Galaxy S II Q&A, Help & Troubleshooting] aboalghool:
hey all.. im a newbie looking for some help

i did root my sgs2 phone jb version with cwm and i have superuser app installed and i have verified that it is rooted.

however i download beats audio which jammed my music player ..

so i was wondering if i can flash the stock jb again via odin ??? and will my phone if flashing works make it unrooted again?
[Galaxy S II Q&A, Help & Troubleshooting] ankur.co.in:
Yeah after flashing the firmware via odin ur phone will be unrooted :)
[Galaxy S II Q&A, Help & Troubleshooting] ssbnasa:
That 'exynos exploit' by 'chaingire' can also be used to root XXLSJ in just one click, without any flashing etc. :)
[Galaxy S II Q&A, Help & Troubleshooting] match_stick:
Hi I hope someone on here can help me...

I recently flashed my girlfriends sgs2 (via odin pc) with the new XXLSJ jelly bean leak. Because its not 'officially' released we have to use Philz kernel, is that correct? I basically want completely stock and the update WITHOUT ROOT AND YELLOW TRIANGLE...

Is this possible?

I myself have the same phone and have custom rom based on this leak and Philz kernel, but for some reason have no triangle? ?

So, I want...

- Jelly Bean Stock rom

- No Root/Triangle.

Thanks. ..

Maybe I should have waited for the official release..

sent from the unknown
[Galaxy S II Q&A, Help & Troubleshooting] ssbnasa:
When u flashed that leaked firmware, ur phone was already in stock but with TW 5 unrooted condition.

Secondly, for that triangle problem....Use the 'triangle away' app from play store.

Also, if u want official update then for few weeks more :/
[Galaxy S II Q&A, Help & Troubleshooting] match_stick:
Cool. I've heard some stories of hardbrick when using that app... but will most likely wait for the official update

sent from the unknown
[XPERIA X8 Q&A, Help & Troubleshooting] Davez100:
I want install a cooked rom to my X8, it's better put an ice rom or gingerbread one? what is the most stable and fast?

Tahenk You
[XPERIA X8 Q&A, Help & Troubleshooting] mujeeb999:
us gingerdx v22 with alfs kernel if you can unlock your bootloader. it is fastest rom I've experienced.
[XPERIA X8 Q&A, Help & Troubleshooting] Davez100:
I have the bootloader unlocked and the sim lock removed, can I use that rom?

Thank You
[XPERIA X8 Q&A, Help & Troubleshooting] sonurockspunk:
Yes first flash the Kernel & then the ROM

I am not earning money by helping u so If I helped you or gave my time dont only say thanx please press thanx;)

Device History:Nokia N72,Nokia 5130,Samsung L700,Samsung 525,LG P500(HARD BRICKED),HTC WILDFIRE S(STOLEN),NOW W8 Lets see what happens to this..
[XPERIA X8 Q&A, Help & Troubleshooting] Davez100:
Okay I try, other rom for ics? :confused:
[XPERIA X8 Q&A, Help & Troubleshooting] NRG001:
Gingerdx is not an ics rom
[XPERIA X8 Q&A, Help & Troubleshooting] nag xperia:
gdx 29 the best:D
[XPERIA X8 Q&A, Help & Troubleshooting] tp_wireless:
Install GingerDX v29 with alfs kernel or if you want to use a ICS rom, install aTouch v1.4 with nAa ICS or OXYDOS ICS kernel.
[Sprint HTC EVO 4G LTE] tootseroel:
I have tried many browsers, but i cant seem to find one that will swipe to last page or jump forward with a swipe of the finger. any suggestions?
[Sprint HTC EVO 4G LTE] rubyknight:
Maxthon Browser. You just have to enable it in the browser settings. It's a pretty decent all around browser as well with flash support and add-ons.
[Nexus 4 Q&A, Help & Troubleshooting] MattSkeet:
Just spotted today on google factory images that N4 is called OCCAM when previously it was MAKO. Does that mean anything? what about updates?

My N4 in build.prop is called MAKO as well
[Nexus 4 Q&A, Help & Troubleshooting] Rusty!:
Phone is Mako, software is Occam.
[Nexus 4 Q&A, Help & Troubleshooting] wing_addict_usa:
weird
[Nexus 4 Q&A, Help & Troubleshooting] Rusty!:
No it's not, it's standard Google behaviour.
[Nexus 4 Q&A, Help & Troubleshooting] wing_addict_usa:
other companies dont do it

did the g1?
[Nexus 4 Q&A, Help & Troubleshooting] EddyOS:
I'm guessing it's the same with the Galaxy Nexus - maguro and tuna are the same thing but it's known as maguro
[Nexus 4 Q&A, Help & Troubleshooting] Rusty!:
The GSM GN is worse, family is Tuna, hardware is Maguro, software is Takju, Yakju plus regional variants like Yakjux
[Samsung Galaxy SL i9003] silentcontrole:
That's how you can Unlock your Samsung Galaxy SL or Galaxy S

****************************************************************************

1. Root your phone

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

2. Install busybox from the play store

https://play.google.com/store/apps/details?id=stericson.busybox&feature=search_result

3. Install galaxy s unlocker from the play store

https://play.google.com/store/apps/...sMSwxLDEsImNvbS5oZWxyb3ouZ2FsYXh5c3VubG9jayJd

4. Open the app busybox and click install the latest version

5. Open the app galaxy s unlock and click and step 1 after that click steup 2 (the phone should reboot now) after that reopen the app and click step 3

6. Reboot and now your phone is unlocked ;)
[Samsung Galaxy SL i9003] joan.scat@gmail.com:
Unlock procedure does not work

Hi. Nice post but does not work for me.

I have i9003 rooted and with a different ROM from stock. I have XWLF2. My carrier is Yoigo in Spain.

I have tried the method in this post, and also the method in http://xdaforums.com/showthread.php?t=1210289. None of them worked.

What happens with this post's method is that the Network Lock is still ON. All other locks are OFF, but they were off already.

COMMENT: Galaxy S unlock (not "unlocker") . After step 2, my phone did not reboot. Step 2 indicates that if the signal works, use step 3. If it does not, reboot and apply step 3. My signal works but the phone is still Network Locked. If I reboot and apply step 3 nothing changes.

Doing *#7465625# indicates Network Lock ON.

Is all that related to the fact that I do not have a stock ROM installed? Any ideas?

(I'll post the symptoms for the other method in that post.)

Thank you so much

Joan
[Microsoft Surface] Malte1234511:
Hey guys,

for days I tried to get my O2 Surftstick to run on my Microsoft Surface Tablet. I'm not sure if there are any Drivers for the build in

USB Modem (Huawei E173), but thats not the mainproblem. This is that the device has 2 USB Modes. The one is a mass storage device with the Windows Drivers (this is the device detected by Surface) and the other one is the USB Modem mode. The Problem ist that the USB Modem is normally detetcted after installing those Drivers on mass storage. No Problem on Windows 8, but in Windows RT there is no way to install a 3rd Party Software including the Drivers. Without the drivers the USB Modem is not detected and I cant even see if there would be drivers for it. I tried a lot of things, f.e. porting all Software Data and even the Registry Entrys to my Surface. The result ist that my Surface Shows the Software (in my case Mobile Partner) as installed,

but detects still only the Mass Storage. I tried some other things, but they all had no effect, so I wrote an email to

Huawei asking for Windows RT Support but they didnt asnwer. I think if we would find a way to Change USB Mode it would

be a benefit to make more Surfsticks from other carriers working.

Please help, I have no more Ideas but would really like to see my Surface working with my Surfstick,

Malte1234511
[Microsoft Surface] killall:
See my post from another thread.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] rak.subramanian:
I have tried Mesa,krsh,rage,extended stock.

Mesa apparently gives better battery life but it takes so long to boot, almost 2 mins tops!

which is the best in terms of performance?i dont actually care about the battery life :p
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Ikmalblack95:
try panic

http://xdaforums.com/showthread.php?t=1861905
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] pitchblack5691:
threads comparin Roms and/or kernels are strictly not entertained here. Try different kernels for your phone and get your own opinion or read each and every supported kernel's thread and post there. Please friends, don't reply and bump this thread.

.:goutham:.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] rak.subramanian:
I dint know i shouldnt post here,

That said, is it really important that you warn people? Lol
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] seljachina:
:fingers-crossed::fingers-crossed::fingers-crossed:

I am on xperia mini GB

Where can i find stock kernel with only two way call recording patch? plus maybe root, not busybox(on rage kernel is very old version) and not other stuff..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] AvRS:
Closed as best kernel/ROM threads are not allowed, this one must've slipped past.

Thanks

AvRS
[Samsung Galaxy Nexus] 5pace:
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.

I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.

So let's start:

1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.

(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)

2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu

(To revert you can flash this (PLEASE NOTE THIS IS Version 2 and please use this version to revert successfully previous version had some flaws in it): http://www.mediafire.com/?d4n1fx3cj446k1l)

3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.

4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.

5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".

6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".

Voila you have a proximity sensor that no more interferes into calls or anything else!

What I did?

Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".

What it does?

The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.

CREDITS:

A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.

Alexander T. for figuring out production date.

Thank you :)
[Samsung Galaxy Nexus] orph:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
[Samsung Galaxy Nexus] yuryvrn:
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.

I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
[Samsung Galaxy Nexus] 5pace:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys. :)
[Samsung Galaxy Nexus] yuryvrn:
I have the stock JOP40D, yakju, the phone is rooted. My sensors.tuna.so is attached. I am new to android, did I understand you correctly all I have to do is to replace the original sensors.tuna.so by the modified file you will send back? Or I need to apply your patch as described in the 1st post (since my ROM is stock)?
[Samsung Galaxy Nexus] PaXGeN:
THX 5pace,

i have the annoying bug of 8C :crying:

Paranoid Android 2.99 beta8

- sensors.tuna.so

- sensors.goldfish.so

The fix is ok, the proximity sensor is disabled.
[Samsung Galaxy Nexus] puertorecon:
I have this issue too. I am on CM 10.1 EuroSkank on stock kernel. Is there a zip file I can flash? Thanks for the fix!!!
[Samsung Galaxy Nexus] LKNim:
Is it compatible on other roms such as Xylon?

I got the same annoying problem
[Samsung Galaxy Nexus] PaXGeN:
You can try the Fix, if it doesn't work properly you can restore the backup with the Un-Fix :good:
[Samsung Galaxy Nexus] Joe_6pak:
Proximity Sensor Blues!

I'm new to this forum, so bear with me. I've been having the Proximity Sensor Blues lately and am in need of a cure. I've got a Verizon GNex (rooted and unlocked) running JB Sourcery 4.0 (soon to be 4.1 unless you tell me different) with their most recent "stock" kernel. I've attached the two files you requested, but have not tried the fix yet.

Considering the ROM I'm running and the attached files, is it OK for me to try the fix? Should I try a different kernel? Does it matter if I have TWRP instead of CWM? Please help!
[Samsung Galaxy Nexus] pafimal:
Everything its ok
[Samsung Galaxy Nexus] 5pace:
Sorry guys, I didn't have much time to reply this topic I had exams plus real life hassles to deal with, again I am sorry for the delay.

I've attached flashable zips files and appended your appropriate usernames with them, you can download and flash these files as per your usernames. If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler

After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.

On a side note I knew about the app (even before making this mod), but I wanted my proximity sensor to be disabled without depending upon an app so I eventually came up with disabling it through lib file which was far more efficient. And these files aren't supposed to disable all the other sensors, using other ROM libs on another ROM will stop the functioning of other sensors, it's just because every ROM is unique in it's own way so these files require to be modded according to their respective ROMs source files. And yeah, again I do not guarantee this mod would work because after applying it to my Nexus, it still rebooted but the reboots were less occurring as compared to when the proximity was enabled.

P.S. I re-purchased Galaxy Nexus, the old one was a C8 (White color), and luckily the new one was a C2 (Black color) and it can do wonders in overclocking and undervolting. :p
[Samsung Galaxy Nexus] bacekoko:
On my Nexus C8 not work this trick with disabling the proximity sensor :(

I use Xylon ROM, with his kernel...

What alse i can try to resolve the problem?
[Samsung Galaxy Nexus] 5pace:
You may want to try this:

If it doesn't help in your case, then I am sorry as I am out of ideas. :(
[Samsung Galaxy Nexus] Joe_6pak:
So far, so good. Got fed up with the PS on my phone and tried this today. The sensor is disabled as far as I can tell. THANKS!
[Samsung Galaxy Nexus] HoetBlack:
It worked for me, thanks.
[Samsung Galaxy Nexus] zeroburn92:
All sensors are Off

Thakyou for this fix.

Not even a single call drop since i installed but none of the sensors are working.

I don't want any sensors but just the Camera so please if u can make it work I'll be very thankful.

Currently I'm on 4.1.1 JRO03C

I tried it on JDQ39 (4.2.2) it disabled only the proximity but calls were still dropping.

If possible then please make a fix to disable all sensors on 4.2.2 except camera and sound.

Thanx again.
[Samsung Galaxy Nexus] daniozzo83:
I've a gnex with installed custom rom( minco v5 4.1.2 )

I've tried your mod for proximity sensor fix and it worked but it disabled light sensor too. I've tried app on playstore but it does the same.

I really need to disable proximity sensor to get my phone working good, but i won't to disable light sensor. Can you help me?

thank's,

Daniele.
[Samsung Galaxy Nexus] ryza666:
My sensor PLS

Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device :) PLS.... I am on CM 10.1 M3 with leankernel 6.4
[Samsung Galaxy Nexus] ryza666:
I've use PaXGeN's sensors modified by you 5pace and there are working on my CM 10.1 M3 ( on every kernel ). I think PaXGeN pack sensors will work on every single custom rom based on jb 4.2.2. My proximity sensor is disabled but everything else is working smooth. I've checked efficiency by Android Sensor Box. Thanks for this thread.
[Samsung Galaxy Nexus] mbrentrowe:
I've got my fingers crossed that this will work. I'm on stock 4.2.2.
[Samsung Galaxy Nexus] ryza666:
:)

It will be ok :) man :)
[Samsung Galaxy Nexus] PaXGeN:
I'm sorry bro, but the bug has not been resolved with the last update (4.2.2). It's a hardware problem about "Sharp GP2A Proximity sensor" on 8C series :crying:
[Samsung Galaxy Nexus] ryza666:
Which fix you've used ? from the first post in the first site ? if you are on stock 4.2.2 you don't have "sensors.goldfish.so"

"It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys

so please write what you've done ? :)
[Samsung Galaxy Nexus] 5pace:
I didn't even catch up with this thread (my apologies). The thing I've noticed on my previous Nexus was that, when I was on CM 10.0 everything was fine, no call drops or anything but as soon as I upgraded to CM 10.1, the things changed, I edited CM 10.1 sensors file for myself, it indeed disabled Proximity sensor but the calls were still dropping. Give me an hour or 2 and I'll catch up with you guys regarding these files, most probably it would need some testing, so backup your ROMs. :)

For the "sensors.goldfish.so"; it is a unique Cyanogenmod file, which is used for android emulator (so most probably it doesn't interfere with this issue). As most of the ROMs are based on Cyanogenmod so this file happens to be in every ROM. So, from now on we don't need "sensors.goldfish.so". :D

EDIT: It's an alpha version of the fix (completely removed proximity stuff). So guys, give it a go and provide feedback!
[Samsung Galaxy Nexus] daniozzo83:
can you help me too???

I use minco v5 as daily rom. It's a 4.1.2 rom, but when i installed your mod i lost light sensor too.

I really need to disable proximity sensor to get my phone working good, but i won't to disable light sensor. Can you help me?

I tried app on playstore too..... withouth success.

Please help me! :)

p.s.

i attach my sensors files(i understood you need sensor.tuna and sensors.goldfish)
[Samsung Galaxy Nexus] Murrzeak:
Mine's C7 (July 2012) and I just recently found out the issue. I'm sure it wasn't there from the beginning. Have installed the app from the market and and seems to be working. Oh Sammy...
[Samsung Galaxy Nexus] lost_:
Not sure if it's the same problem; My maguro C2's proximity and light sensors were dead even though front camera was fine (C2=Feb 2012). I swapped it and it's working fine now. Lookie here:

Just swapped the proximity/light sensor board (maguro - toroplus).

I ordered a an aftermarket proximity sensor from a Chinese seller on Aliexpress for the toroplus ($6.95 shipped) and will update the above thread when it comes.
[Samsung Galaxy Nexus] mbrentrowe:
It's been nearly two weeks and I have had zero problems. Maybe this is finally the solution. Thank you so much for this fix. It has honestly made me like my phone again.
[Samsung Galaxy Nexus] PaXGeN:
Hi guys, the bug seems to be resolved with "ProximityFix.zip by 5pace" :good:
[Samsung Galaxy Nexus] blackbird5308:
I tried the patch, and i works for the sensor error, but it completely breaks camera :/

Is there another way?
[Samsung Galaxy Nexus] bimasakti85:
Camera is working here after flashing this patch. Maybe you can provide your logcat so the developer can examine it?
[Samsung Galaxy Nexus] blackbird5308:
No need :) my bad, after a cm10.1 clean flash is all good ;)
[Samsung Galaxy Nexus] stcindia:
It worked for me

Thanks for the fix, it smoothly works for me on JDQ39
[Samsung Galaxy Nexus] player911:
Mine is overly sensitive. When using it on the other ear, there is a gap between the phone and my ear and starts pressing buttons.

It works on one side well but not on my left side.
[Samsung Galaxy Nexus] dietdoank:
I have the same screen problem as well. Would you prepare for me my sensor files for my device... I am on MTK6575 device
[Samsung Galaxy Nexus] KreNtal:
Does it work with jb 4.3? Anyone have tested?
[Samsung Galaxy Nexus] mbrentrowe:
I flashed it and yes it works on 4.3. I've had no issues.
[Samsung Galaxy Nexus] bluedude1:
Camera got disable

Hi,

first of all thanks for the great solution.

just flashed your v2 of proximity fix. It got disabled perfectly with any issues but it also disabled my camera and showing error "Can't connect to the camera" :confused: :(

After i flashed proximity revert camera works back to normal.

Can you please tell me whats the issue and did i had done something wrong. Please help me out.

I am using Stock 4.3 (odexed).

Thanks

Regards :good:
[Samsung Galaxy Nexus] bluedude1:
Hi,

Can you please tell how to get logcat, to submit here for review?

Thanks
[Samsung Galaxy Nexus] inihccor:
Stock odexed 4.3. It works and I love you :D you solved a big problem!

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] KreNtal:
I can confirm, works perfectly on CM 10.2
[Samsung Galaxy Nexus] raistland:
CM 10.2 It's work

I install from zip and it works. But I can't use camera and other sensors

My android is 4.3.1 CM10.2-20131119-nightly-magura.

Anyone help me ?
[Samsung Galaxy Nexus] inihccor:
Try to flash the ROM and the mod again

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] RickyBlock43:
Hey guys! This fix run with cyanogenmod 11 or other rom based 4.4 android kitkat? Thanks!
[Samsung Galaxy Nexus] inihccor:
It works with cm11. Just flash it after everything else.

Inviato dal mio Galaxy Nexus utilizzando Tapatalk