yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] amir karimi2:
4.2

yes there is :D

http://xdaforums.com/showthread.php?t=2000656
[Galaxy S I9000 Q&A, Help & Troubleshooting] TheRippaG:
will work 4.2 camera for this phone or not? because I have an SGS+ and 4.2 camera doesn't work
[Galaxy S I9000 Q&A, Help & Troubleshooting] GrippingSphere:
Camera 4.2 works in SGS. But the photosphere function is not supported because SGS has no gyroscope, a requirement for photosphere to work.
[Nexus 4 Q&A, Help & Troubleshooting] Miragej:
So my severe lack of patience got the better of me and I ended up buying a nexus 4 on pay from O2 today however my contract is with Three. I highly doubt it but is there any free way to sim unlock it right now, without going through one of those online unlock websites?

Thanks for any help,

Josh
[Nexus 4 Q&A, Help & Troubleshooting] IINexusII:
It should come unlocked?
[Nexus 4 Q&A, Help & Troubleshooting] ed10000:
Heard this from multiple people who also bought one from O2 - apparently it is ALREADY unlocked even though you've been assured by O2 that it is locked to their network. Just try inserting a SIM from another network to verify. :)
[Nexus 4 Q&A, Help & Troubleshooting] kaiowas82:
I bought it today from o2 and works fine with my 3 contract
[Nexus 4 Q&A, Help & Troubleshooting] Miragej:
Thanks for the quick reply guys, I took it to one of the shops in town straight away to get it unlocked and after about 40 minutes of waiting, he couldn't get an unlock code for it so just out of curiosity he tried a Vodafone sim in it and it worked fine with it and he was able to make a call. From this, I too assumed that it was already unlocked but when I try my Three sim in it, it won't find the network :/ and the sim is definitely working because when I replace it in my temporary phone, it works fine. I also then found out that O2 and Vodafone have linked networks, so I assumed that's why it worked on the Vodafone sim but not my three one, pretty damn confused haha
[Nexus 4 Q&A, Help & Troubleshooting] Miragej:
Hmm that's interesting, and only adds to the confusion :/
[Nexus 4 Q&A, Help & Troubleshooting] Miragej:
Right, so my replacement three sim has just become active (needed a micro sim instead of my normal sim) and it still wont work in my N4, but does work in my spare phone. No idea what's going on.
[Nexus 4 Q&A, Help & Troubleshooting] Miragej:
Never mind, it's decided to work now, thanks for the info.
[HTC One V] Enpo:
Hi. I was flashing AOKP rom, and everything went normal, until i came to a point where i should flash boot.img. I tried to flash it, but there was a following message: "error: cannot load "jellyboot7.img" I have tried all things I can imagine to fix this

-Re-Flash ROM

-Different USB port

-Different boot.img

-Reboot

-reset computer

Boot.img is in same folder as fastboot, and fastboot is installed and apb too.

Anyone knows solution for this?
[HTC One V] donhashem.dh:
Is that on linux ??
[HTC One V] cybervibin:
What command did u write?

Sent from my One V
[HTC One V] mihirengg19:
error loading boot.img is usually due to typing wrong command in command window....like if my boot img is named cm10(for ex), and i type...-

fastboot flash boot cm1.img(miss the 0)

then it says error loading.......

so,rename ur boot.img as"boot.img" and not some complicated name which can lead to mistakes.....
[HTC One V] evoshifter2107:
I had the exact same problem. What you need to do is extract the rom you were trying to flash and flash the boot.img in the rom. The same thing happened to me like 30 min ago, fixed it and now im running the 11-14-12 AOKP nightly. (ps. if it is the 11-15-12 nightly your trying to flash then, its just not going to work something went wrong when the developer was uploading it. He said he would fix it asap)
[HTC One V] cybervibin:
Make sure ur file path is correct

Sent from my One V
[HTC One V] mihirengg19:
boot.img should be IN the FASTBOOT FOLDER, not in the same folder as fastboot.....!!
[EVO Shift 4G Q&A, Help & Troubleshooting] OrbofInsolence:
Hello, I'm currently replacing the cracked LCD screen of my HTC Evo Shift 4G phone. I've been using the RepairsUniverse video to aid me.

However, in the video there is no orange film where the image attached shows.

What do I do with this? And how do I safely remove it and place it back? I don't want to harm the phone.
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
The orange film is there as a protective Layer. What I do is peel it back CAREFULLY with an Exacto knife. Just enough so it's out of the way. Then you undo the the white clips one at a time CAREFULLY. When I first undid the clips I used the tip of the Exacto knife blade. Now I just use my fingernail. Just be sure your undoing them in the correct direction. Then slowly pull out the Ribbon connections one at a time. After that continue following the Video.
[EVO Shift 4G Q&A, Help & Troubleshooting] OrbofInsolence:
I'll keep doing what's shown on the video, but damn. The little chip thing came off the ribbon cable.

Is this fixable?
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
I hate to be the one to say it. But no :( . Time for a New Ribbon :( . If you had a Micro Soldering tool maybe. But I don't know to many people who own those.
[EVO Shift 4G Q&A, Help & Troubleshooting] OrbofInsolence:
I'm gonna try and re-assemble it anyways and hope it works.

The model used in the video must be different or something.

I hope it works.
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
It in all probability it will not work correctly, if at all. You can check THIS thread for the site where you can get repair parts. Also I have seen them on Ebay.
[EVO Shift 4G Q&A, Help & Troubleshooting] OrbofInsolence:
Using precision level accuracy, I re-attached the chip and put it back together. IT WORKS PERFECTLY.

I'm the human solder baby. :cool:

Thanks for the help prboy1969.
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
I stand corrected. You are talented :thumbup: :D

TEAM MiK

MikROMs Since 3/13/11
[EVO Shift 4G Q&A, Help & Troubleshooting] Chad The Pathfinder:
WOW dude! I was really feeling sorry for you but you're the man! :thumbup::thumbup::beer::beer:

Edit: Wait a min, the date in the pic is 1/02/2007. Are you messin' with us? JK! :D
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
Whoa :screwy: . I just noticed the date on the Device. June 5th 1980 :eek: what the heck :eek: . What happened ? Did you manage to turn the Shift into a Time Shifter :p

TEAM MiK

MikROMs Since 3/13/11
[EVO Shift 4G Q&A, Help & Troubleshooting] Apxiundns:
Interesting how in one photo you have two totally different date/time stamps (from two completely different decades). You sure your phone is working right?
[Motorola Droid X2] kmedeiros:
Hey guys,

I just installed CM7.2 RC1 (2 times now) after a wipe/factory and davlik cache as well and I can't get the Droid X2 second core script to function properly. I used this and knew it was working in Eclipse 2.xx but not on CM7.2 RC1. I've setup the script with the proper permissions in init.d and can even change the /sys/devices/cpu/cpu01/online file to 1 manually, but the script is either not running or something is overwriting whatever the script changes every boot.

Anyone else still running CM7.2 RC1 on a Droid X2 and run the Second Core Script?:confused:
[Motorola Droid X2] tallyforeman:
Here's a thread that may help or give you some info:

http://xdaforums.com/showthread.php?t=1569198
[Motorola Droid X2] kmedeiros:
That's the thread I was using to troubleshoot, but I've exhausted all those options! lol. I may SBF again and install again to see if that fixes anything. I'm not sure what could have gone wrong as I followed the instructions precisely. :\
[Motorola Droid X2] kmedeiros:
I've had some success running the script via script manager, but even when set to run at boot it does not. It does however activate the core when I run it after boot.

Something in CM7.2 RC1 isn't allowing the changing of the online file to 1 instead of 0 for CPU1. I'm thinking people may have been running this script a while ago before the latest RC1 release and may not even know it's not running anymore..?

I dunno, but I give up on activating the second core all the time under CM7.2 RC1 on this Droid X2.
[Samsung Galaxy Nexus] tiny4579:
Reserved
[Samsung Galaxy Nexus] disynthetic:
fwiw here's the proper link to your goo.im kernels : http://goo.im/devs/tiny4579/kernels/gnex
[Samsung Galaxy Nexus] tiny4579:
Fixed. I didn't realize my links copied over bad.
[Samsung Galaxy Nexus] sparkplugDev:
Hey Tiny!

Glad to see you're getting into the game for the Gnex as well! Downloading now!
[Samsung Galaxy Nexus] tiny4579:
I've actually been posting this kernel on rootz since September but today decided to mirror it on xda.
[Samsung Galaxy Nexus] aggrophobik:
Thanks for sharing your work here as well.
[Samsung Galaxy Nexus] Alton (Halo 2):
DEFINITELY downloading this I loved ur kernels on droid inc :)
[Samsung Galaxy Nexus] tiny4579:
Thanks. Just a word of advice. I've heard reports that the 4.2 kernel (2.0) breaks bluetooth on 4.1 ROMs. For now stick with 1.7 if you want to use a Jellybean 4.1 ROM.
[Samsung Galaxy Nexus] yoyomonk:
Tiny, thank you for your great work. I used your kernels all the time on the Droid Inc and look forward to trying this out!
[Samsung Galaxy Nexus] Talkdj:
Tiny! Bless you my long last friend. You're BACK!!! Now we're talking!
[Samsung Galaxy Nexus] tiny4579:
2.0.0 has gone stable. No changes from the 2.0.0-exp1 release but since it's good enough to be stable I wanted the build to reflect that.

I didn't add NTFS or CIFS support but I can if there's a request for it.
[Samsung Galaxy Nexus] bubbayang:
I am unable to enable bluetooth after I loaded up 2.0.0. Now I don't know if the kernel affects bluetooth or not. Anybody experiencing this issue?
[Samsung Galaxy Nexus] tiny4579:
You probably don't want to be running 2.0.0 unless you're on a 4.2 ROM. Just my guess. No problems enabling bluetooth on 2.0.0 on a 4.2 ROM.
[Samsung Galaxy Nexus] bubbayang:
Yeah, i'm on CNA 3.8 4.1.2 I guess I'll just roll back to the older kernel. Thanks
[Samsung Galaxy Nexus] ArnieG:
2.0.0 is running fine with mmuzzy's 11/16 4.2 build. Thanks for the great work.
[Samsung Galaxy Nexus] LexusBrian400:
What are you guys using to ramp up the GPU? Franco kernel app is showing 2Mhz. Any help?
[Samsung Galaxy Nexus] tiny4579:
It uses LeanKernel's interface so the app TricksterMod should work.
[Samsung Galaxy Nexus] LexusBrian400:
Ok thank you
[Samsung Galaxy Nexus] xolanir:
I just had an oddity using trickster's mod with the kernel. After applying settings when I tweaked the GPU OC to 387MHz, the screen got a blue tint/hue. Did I do something wrong or is the mod buggy with 4.2? I'm running Muzzy's AOSP 4.2 ROM. I had Franco's r313 before trying tinykernel, but I wasn't getting any deep sleep. Still not deep sleeping even on this kernel. Did I bad flash or could there be something else happening? Thx in advance for the help.
[Samsung Galaxy Nexus] laureanop:
Actually Tiny I've been giving exp b another shot and indeed it is snappier than A on interactive x, with no lock screen lag. I also just noticed all the extra interactive governor settings. Screen on battery seems better on B as well. (Cm 10.1 01-04)

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
Tell me if this helps with ix lag. Copy to /system/lib/hw, change permissions to read/write for owner and read for group and others. Then reboot.

http://d-h.st/MQS

It will overwrite your ROMs powerHAL but will work fine on all JB ROMs. Nandroid first to be safe but it should be fine.
[Samsung Galaxy Nexus] laureanop:
I see. The stuff you were discussing with IMO in his thread. Installed and everything works OK.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] BOY_:
I'm using trickster also. The pegging is, perhaps a bit much... I am entering deep sleep and the CPU is spending its time at 350 MHz with screen off, 350-700 MHz or 1400 MHz. The only logged time in between is from when I switched to I. The thing that concerns me is that I don't see core 1 getting any activity...
[Samsung Galaxy Nexus] BOY_:
OK, so I tried a reboot and the phone didn't come back. Did a battery pull and now trickster is reporting much b more normal behavior. I'll keep an eye on it.
[Samsung Galaxy Nexus] nate6138:
Still using exp2 didn't even realize how long it's been since I've had it off the charger wow.
[Samsung Galaxy Nexus] BillLee3:
Tried the exp3b and it seemed about like most of your kernels on this device - fast, great on battery when idle and I guess acceptable under use (which is as good as any kernel gets on the Nexus).

However, I hooked it up to my Win8 machine and the device showed up in Explorer very inconsistently. When I did see it, the internal storage didn't show up. Thought maybe I had fast charge on or something.... Although, it also didn't seem to be charging very well. Finally downgraded to 2.4.2 and everything is back to normal.

Certainly would suggest others check me on this 'cause this is a clean Win8 install on a brand new motherboard, cpu, memory, etc. Can't be certain it's not my install or my hardware.

Thanks for your hard work!
[Samsung Galaxy Nexus] T-Keith:
Does the interactivex kernel cause sod with pgm? I had a lot of trouble with that on lean kernel.
[Samsung Galaxy Nexus] tiny4579:
Double check the lean thread again. He posted a new build with a fix to the reboot issue.

But you're talking about sod. No ive never gotten an sod with pgm. But I've gotten a non responsive touchscreen - ie lock screen is frozen but can wake and sleep the phone - which should be fixed as of 1.13 of pgm. 1.10 is supposed to work fine. I can't remember what version started the problem but it should be fine.

Anyway the best explanation for the issue is that the touch panel doesn't wake up after phone wakes. If you get that issue on the latest pgm report it to the Devs thread. Not sure about sod. And I'd rather say pgm causes an issue with the kernel.
[Samsung Galaxy Nexus] laureanop:
Pgm updated today

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] T-Keith:
I'm aware of the screen responsive issue, which can be solved with a three finger pinch. The problem I had on leankernel was a straight out black screen, won't wake from sleep. I posted on that thread and was told it was a pgm issue, but I was also told it was an interactivex issue.

I've been very happy on this kernel though.
[Samsung Galaxy Nexus] zerocool79346:
That's an SOD and is pretty prevalent on any 4.2 kernels. Has nothing to do with interactivex or pgm as it affects those with pgm as well as those without and kernels that don't have interactivex (Franco and trinity for example).
[Samsung Galaxy Nexus] Jose Viegas:
I never had any of those with tiny and pgm, no mater the version.
[Samsung Galaxy Nexus] T-Keith:
Had constant sod with pgm on, none with it off. None with tiny's kernel. I don't think it affects all 4.2.
[Samsung Galaxy Nexus] baggar11:
Just wanted to give you a little more input on the kernels. I was unable to run the B kernel while using interactivex. The device became unresponsive and the screen wouldn't turn back on after about 45-60 minutes. A seems to run fine on interactivex though. I know I'm a little late to the 24hr testing period.
[Samsung Galaxy Nexus] tiny4579:
That is an SOD and it seems to be quite common with 4.2. Nothing to do with the kernel or interactiveX. Whatever caused it wasn't related to B.
[Samsung Galaxy Nexus] tiny4579:
The SOD issue you all are reporting has occurred even on complete stock unrooted so no it's not an issue with custom kernels but the only time I ever had an SOD on Android 4.2 was using Trinity which is a conflicting statement but it's my experience. I don't know if it's the kernel's fault though.
[Samsung Galaxy Nexus] laureanop:
Geez! I have not had a single SOD on any 4.2 ROM, or on any kernel with a variety of settings, governors, io schedulers.

I guess my phone cannot be used as a parameter for anything because it can handle anything I throw at it

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] BOY_:
So tiny, which ROM is the winner?
[Samsung Galaxy Nexus] tiny4579:
It'd probably be B.
[Samsung Galaxy Nexus] techspecs:
I've never had an SOD on muzzy's ROM. I'm playing with cm10.1 now and had one earlier. Tiny on both. Muzzy for president!
[Samsung Galaxy Nexus] BOY_:
With the patch please :) seemed yo do the trick.
[Samsung Galaxy Nexus] gt5oh:
Can anyone share input on running this (Tiny Kernel 2.4.2) and Shiny Rom 1/3/2013 -- How do they work together?
[Samsung Galaxy Nexus] tiny4579:
My kernel works on all ROMs.
[Samsung Galaxy Nexus] d00dr:
Finally jumped on the 4.2 wagon and am here to stay. The latest RasBeanJelly and TinyKernel 2.4.2 is killin'! Haven't had a chance to try out any of the experimental builds yet. Any suggestions as to A or B?
[Samsung Galaxy Nexus] normanx:
Use b
[Samsung Galaxy Nexus] tiny4579:
Kernel update:

2.5.0

update kernel to 3.0.57

numerous interactive governor updates

interactiveX support with butter (imoseyon)

various patches to help reduce lag (various)
[Samsung Galaxy Nexus] tiny4579:
Two new updates:

1.10.0

add Vegas, Veno, and H-TCP TCP congestion schedulers

update kernel to 3.0.57

numerous interactive governor updates

interactiveX support with butter (imoseyon)

various patches to help reduce lag (various)

2.5.1

add Vegas, Veno, and H-TCP TCP congestion schedulers
[Samsung Galaxy Nexus] Jose Viegas:
Thanks!

What would you recomend to use? I have no idea what they do :)
[Samsung Galaxy Nexus] tiny4579:
I added the congestion schedulers on request. If you aren't sure, don't change it from default which is cubic.
[Samsung Galaxy Nexus] Jose Viegas:
Thanks, 2.5.1 flying!!!!
[Samsung Galaxy Nexus] laureanop:
2.5.1 and imo's 5.6.exps fly on this phone on interactive x. You guys nailed it with the new interactive patches. There's a before and after with 4.2 kernels after these modifications. Definetely milestone releases.Great job, thank you.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] ocman40:
Should deep sleep show as unused for this kernel and interactivex?

Hmm now it's showing. Weird
[Samsung Galaxy Nexus] Jose Viegas:
It wont if you have it charging
[Samsung Galaxy Nexus] tiny4579:
It won't if it's charging via USB but will when it's charging over a/c.
[Samsung Galaxy Nexus] ocman40:
Thanks. It was not charging, just took a few minutes. Feels quick though.
[Samsung Galaxy Nexus] cms5423:
Make sure you refresh the stats. Sometimes you need to manually refresh the stats to make them accurately reflect the cpu state times
[Samsung Galaxy Nexus] Jose Viegas:
Just had a SOD on 2.5.1 with default values.
[Samsung Galaxy Nexus] tiny4579:
I've heard that can happen on completely bone stock 4.2. I'm curious if you were using PGM as for me it always increased the chance of a non-responsive touch screen. 1.14 supposedly has that fixed.
[Samsung Galaxy Nexus] Jose Viegas:
It wasn't the unresponsive screen, it was the not waking at all after being sleeping, not even with the power button. I just raised the max freq when screen off, let's see if it happens again :)
[Samsung Galaxy Nexus] cyberpyr8:
I had a similar problem last night. It was charging and locked. I went to open the screen and the phone locked hard. I had to pull the battery. It happened one more time to me later so I rolled back to 2.4.2. That is stable again. I am running Muzzy's 12-18-12 release.
[Samsung Galaxy Nexus] tiny4579:
I'm repeating myself but SODs happen on bone stock kernels as well. Did you changed the governor?
[Samsung Galaxy Nexus] cyberpyr8:
No I haven't changed it.
[Samsung Galaxy Nexus] elwood1229:
I have had this issue several times on different versions of the kernel and have not been able to find a solution. It seems to happen most often when there is an issue switching from Wi-Fi to 4g or the other way around. I am currently running MMuzzy's ROM though it has happened with other Roms as well. It happens even after clean flashing a ROM and wiping cache before flashing the kernel. Any help wrote would be appreciated.
[Samsung Galaxy Nexus] ocman40:
Have this kernel 350. 1200. 700. Interactivex. Fastest kernel I have ever used.
[Samsung Galaxy Nexus] T-Keith:
Where would we change the congestion scheduler?
[Samsung Galaxy Nexus] jekern77:
Been using b for three days with no problems at all. In fact, haven't had a single SOD since flashing this kernel. No SOD in three days? I love u tiny...:D
[Samsung Galaxy Nexus] tiny4579:
Try trickster mod.
[Samsung Galaxy Nexus] Jose Viegas:
No issues with max screen off freq of 700mhz so far
[Samsung Galaxy Nexus] inspire4gfreak:
+1! Not a single issue since two versions ago! International GNex on Xylon 15 stable build.
[Samsung Galaxy Nexus] tiny4579:
GOOGLEPLEASEFIXITNOW!

In seriousness, since it's been reported on the stock kernel, I doubt it's anything on my end. If it's a kernel bug that Google fix, I'd gladly incorporate it but the cause is still unknown and I don't think any ROM's or kernels are causing the SOD issue.

And before anyone thinks I'm angry above with that first line, I'm just having fun.
[Samsung Galaxy Nexus] andrewc513:
I got my first SOD ever (owned this GNex since Thanksgiving) with 2.5.1, CM10.1 nightlies, using InteractiveX/SIO and default everything else. It's been smooth, fast, and flawless otherwise. Great job!
[Samsung Galaxy Nexus] elwood1229:
Thank you for that piece of info. It has probably been because I didn't understand what I was reading, but in all the forums I have read I had not picked up on the fact that this was a known issue (some SODs yes, but not my particular version of it). While it doesn't fix the problem, at least I have a better understanding. I appreciate your help and work. Your kernel works better on my phone than does any other.
[Samsung Galaxy Nexus] elwood1229:
Sorry, posted in wrong forum and I don't know how to delete it.

problems
[Samsung Galaxy Nexus] Jose Viegas:
Finnaly I went back to 2.50exp-b as it gives me same preformance and no sod compared to 2.5.1
[Samsung Galaxy Nexus] tiny4579:
Hmm, that's funny because this change was the only one other than the new TCP schedulers. A highly unlikely culprit for sod.

https://github.com/tiny4579/tinykernel-gnex/commit/03610a35c53e26ffe4a3b1cc45f6e986b97e2cce

But in truth theres no need to use stable.

Just remember just because you changed kernels and are now not getting sods doesn't mean the kernel change fixed it.
[Samsung Galaxy Nexus] Jose Viegas:
Hey Tiny, I believe you, I had SODs with most kernels (and ROMs) since 4.2.1 came out. In fact, that was the main reason why I stayed with you kernels since the first time I flashed one. They all have worked great, no SODs and full PGM compatibility. They worked when the famous kernels failed. Only after 2.5.1 was released I started having SODs, and it happened with a couple of different ROMs. That's why I returned to this b version, and so far, after 2 days, no problem, let's hope it keeps tat way :fingers-crossed:
[Samsung Galaxy Nexus] Dapman02:
Hey Tiny,

I love the kernel, haven't had any issues for about a week.
[Samsung Galaxy Nexus] normanx:
Me either.. not one issue.
[Samsung Galaxy Nexus] zerocool79346:
Same here. 2.5.1 and my phone don't get along at all.
[Samsung Galaxy Nexus] tiny4579:
How about 2.5.0 guys with sod issues?
[Samsung Galaxy Nexus] Jose Viegas:
None here
[Samsung Galaxy Nexus] zerocool79346:
I never had any. Literally never had one on any of your kernels until 2.5.1, not sure what was up.
[Samsung Galaxy Nexus] tiny4579:
I mean 2.5.0 stable which is not the same as 2.5.0-exp3b. Its actually newer with the only change after it being the new TCP schedulers. Anyone have issues on that?

Also can someone running Exp3b report the part of the version that's g and 8 numbers? I want to confirm the changes as I don't tag betas or exps in any way in my git.