yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General (US Carriers)] Esoteric68:
Okay so here's what I learned this morning from Sprint, and btw if you are like me and tend to have a few phones just hanging around not activated on your account you will want to pay close attention.

It took three phone calls to Sprint, the first this morning at 1:45am when I realized what had happened, got left on hold for an hour when the person went home after claiming she was getting her manager on the line to help. Called Sprint again at 7am and they sent me to the fraud department. The guy I spoke to in the fraud department claims it wasn't any attempt at fraud. Apparently the person whose information ended up in my phone had been having trouble with their phone for the past few days, so a Sprint customer rep tried to do a three way swap using a dummy EIN, well guess what dummy he grabbed the EIN from? Yeah, that would be me.

It seems when they are attempting this procedure they just randomly start swapping the last few digits of EINs associated with the same model of phone, in this case the SGSIII, to find one available for use and just happened to land on my number. Now I don't understand the reasons for this procedure, but it sure seems like a major screw up on Sprint's part.

Now magically between 1:40am cst this morning when I spoke to a friend of the person whose information ended up in my phone (she just so happened to call the number last night when I turned the phone on) and told them I'd be calling Sprint's fraud department first thing this morning and 8am when I talked to the fraud department, the EIN had been released, so I don't believe this was an accidental EIN grab at all.

Now I'm wondering if my other two currently de-activated phones are at risk of having their EINs hi-jacked and how to prevent it. I'm not a novice at this, I always keep a de-activated device around as my insurance plan in case I lose or break my current phone. I've never had this happen before and I am not impressed.

So after a fretful night with little sleep the problem has been resolved and the phone is re-activated on my account.

I very much appreciate the comments and advice.
[Galaxy S III General (US Carriers)] animal7296:
Glad to hear it eso.
[Galaxy S III General (US Carriers)] someguyatx:
Wow that really sounds like a bs story. I miss Tmobile and sim cards. I could swap whenever I wanted between my nokia, sony, or blackberry.
[XPERIA X10 Q&A, Help & Troubleshooting] Ishan Sardar:
okay..so I have

Latest Flashtool - checked

Unlocked Bootloader - checked

Rooted Device - checked

Busybox installed - checked

Flashtool Driver installed - checked

ADB driver - checked

Here's some fail attempt to flash kernel...can anyone tell me what am I doing wrong?? I'd really appreciate it.

WATCH IT ON FULLSCREEN

http://youtu.be/V3jpk3bkfDA
[XPERIA X10 Q&A, Help & Troubleshooting] z28tovette:
Did you drag and drop the kernel.ftf?
[XPERIA X10 Q&A, Help & Troubleshooting] z28tovette:
Don't use fast boot mode.
[XPERIA X10 Q&A, Help & Troubleshooting] Ishan Sardar:
well no cuz the kernel was in the menu for me to select and flash.
[XPERIA X10 Q&A, Help & Troubleshooting] z28tovette:
Drag and drop the kernel.
[XPERIA X10 Q&A, Help & Troubleshooting] Ishan Sardar:
did u see the video? I'm not really sure where do I drag and drop it...I mean when I press flash i can select the kernel I want to flash and then press ok. could u be a little more specific please?
[XPERIA X10 Q&A, Help & Troubleshooting] z28tovette:
Holy smokes, sorry dude . I didn't finish watching the video.
[XPERIA X10 Q&A, Help & Troubleshooting] BordenG:
copy kernel.ftf to C:\Flashtool\firmwares\ folder.

and use Flashmode not Fastboot.

and i've noticed you're flashing .ftf with your phone turned on.

How to...

- copy kernel.ftf to Flashtool\firmwares folder.

- open flashtool, then use flashmode, choose the .ftf you want to flash.

- follow the prompt that will appear. turn- OFF your phone, press the back button while connecting the USB cable.

that's it, you should wait for flashing to get through.
[Nexus 7 Q&A, Help & Troubleshooting] kettlecorn:
Would anyone that owns a Galaxy Note be able to post a size comparison shot of the two? It's a shot in the dark cause most people don't have their tablets but if by some chance there's some nice enough out there with some free time on their hands, with a Nexus 7 and a Samsung Galaxy note that can post up a side-by-side size comparison photo, It'd be much appreciated.

I have one on preorder (N7) but I'm wondering if I should just save some money and not get a tablet all together if the Galaxy Note can do what I need? If the size is comparable that is.
[Nexus 7 Q&A, Help & Troubleshooting] tri0xinn:
I may post a photo tomorrow... If i receive my n7.
[Nexus 7 Q&A, Help & Troubleshooting] kanzlerin:
Seconded! And please make a literal shot in the dark if it's not too much trouble, with only the two screens lit up. I've found that's the most demonstrative way to compare screen size, without the distraction of form and shape of the rest of the devices. :o
[Nexus 7 Q&A, Help & Troubleshooting] e.mote:
http://versusio.com/en/google-nexus-7-vs-samsung-galaxy-note
[Nexus 7 Q&A, Help & Troubleshooting] kiro187:
I also have a n7 on preorder but I am contemplating canceling and getting or waiting for the note/note 2. Not sure yet.
[Nexus 7 Q&A, Help & Troubleshooting] Souai:
ive got the note and my nexus should be arriving this week.

im actually contemplating swapping my note for something more compact since i'll now have a tablet and i dont really use the S-pen features of my note.
[Nexus 7 Q&A, Help & Troubleshooting] Izzue:
Don't know why the orientation is wrong but here ya go.
[Nexus 7 Q&A, Help & Troubleshooting] kettlecorn:
Sweet thanks, much appreciated. guess I'm keeping the nexus!
[Nexus 7 Q&A, Help & Troubleshooting] Slap-Yourself :):
From the first picture it's a huuuge difference.. From the second, it doesn't seem that bad. :/ I was wanting to buy a Note and a Nexus 7 {Both} for school benefits. But It still doesn't seem to clear it up for me lol.
[Nexus 7 Q&A, Help & Troubleshooting] Souai:
just got my google nexus 7. its a fair chunk bigger than the galaxy note.

if you're comparing viewable screen size, the length of the galaxy note's display is only a few mm longer than the width of the nexus 7 display. the nexus 7 display has around twice the surface area of the galaxy note display. its a noticeable difference. the nexus 7 is also fairly smooth as well. not sure if i want to load spb shell 3d or not since its fine in portrait mode.
[Nexus 7 Q&A, Help & Troubleshooting] Izzue:
I've been using the n7 for a day and I can tell you that the larger screen size is definitely noticeable as compared to the note. The brightness and image quality of the notes super amoled however, is far superior. Then again it costs 400 more.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] HotShot619:
I'm rooting Galaxy Note GT-N7000 of my friend for him

he has DDLPA kernal but i cant find a CF-root kernal for it

so i was wondering can I use a DDLP8 to root this device without having his phone bricked???
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dr.ketan:
If you want just root then go for CWM.zip method

find guide from my signature
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] @HOSCHI@:
Thanks:)

Gesendet von meinem GT-N7000 mit Tapatalk 2
[Android Q&A, Help & Troubleshooting] Ethan5150:
Well I've successfully rooted my G2x and am now on Android 2.3.4. I'm trying to flash the Cyanogen nightly build using Clockwork Mod Rom Manager but I'm running into trouble. I've placed the .zip file on my SD card and I go into CMRM, choose Install ROM from SD Card, choose the Cyanogen build and hit Ok. But then, the phone reboots and hangs on the little Android dude and the box with the arrow coming out of it - that's it, it just sits there forever. What am I missing? Is this the best way to get the Cyanogen ROM onto my phone? Any thoughts anyone?
[Nexus 7 Original Development] Clienterror:
Flashed with CWR and it doesn't boot past the Google screen :( Is there something special I need to do?

*Edit*

I am on the new 4.1.1 "D" or whatever but right now I'm using the Atlantis "1.5" kernel and it works so I donno.
[Nexus 7 Original Development] cwc3:
Thanks for another addition to the nexus 7 kernel community, love having different kernels to try.
[Nexus 7 Original Development] _motley:
Thx, please grab the dmesg output while booting or last_kmsg if you can. Working fine here, but this why I put it out as an alpha. Even if you boot off another kernel, if you can send a dmesg captured right after boot, that would help so I can see your SoC/Process ID numbers. There are two lines written just after boot with the info. On the Prime, we had different CPUs in some models, but it may just be a voltage issue. I have run Antutu and Quadrant several times without issues though. Not sure about the D update...I I have 4.1.1.

Edit: Version 1.0.1 released, please test again and leave feedback when you can. Please let me know when you received your tab. Is it an early IO version? If this doesn't do it, I most likely will need to increase voltages a bit. Hopefully I won't have to do this so we can keep battery life at it's best.
[Nexus 7 Original Development] demandarin:
oh s^&*, you developing here also. oh yeah! glad to see you here buddy. so you have your nexus 7 already? now that i see you here also, i will be unlocking my nexus 7, once it arrives, sooner than i thought. welcome aboard...glad to see familiar faces around here :)
[Nexus 7 Original Development] Sobai:
I had the same issue. Couldn't pass the boot screen after flashing. On 4.1.1 latest update as of July 15th :(
[Nexus 7 Original Development] _motley:
Thanks, I am dying to take a look at a log to see how I am so lucky to have it working! I've added LastKMSG.zip to the OP. If someone with a booting problem can do the following, I would really appreciate it:

1) Put LastKMSG.zip on your /sdcard along with the newest kernel zip

2) Flash the kernel zip

3) Wait for it to boot, give it a few seconds and then hold power down to reboot if it doesn't do it on its own.

4) Go back into recovery and flash LastKMSG.zip

5) Flash another booting kernel or your current rom to recover.

6) Boot and retrieve the file /sdcard/last_kmsg

7) Attach the log here or PM me with a dropbox link or whatever.

Thanks!
[Nexus 7 Original Development] _motley:
Just got some good news from a gentleman that didn't have enough posts to share with us here yet, so he PM'ed me and said that I can share the details of his experience.

First report was more of the same, sounded familiar, more bad news...

Flashed your kernel and couldn't boot pasted Google screen. Restarted in to boot and couldn't get into recovery. Was stock rooted on the latest 4.11. Went back to stock. Looking forward to trying again, now I'm on Modaco's latest. I'll let you know how it goes.​

Next report was good using the latest version in the OP. Not sure, but this may help others.

Thanks! This kernel is fantastic! Makes this thing a real beast! Sorry I didn't give you the info you asked for! I got it Thursday from GameStop. The problems may have stemmed from the fact that I updated to 4.11 , rooted then side updated the newest little update and then ran a su zip to regain root (Paul o' Brian ROM) . I was also on his first cwm and then updated to his new one after I started from scratch. Loaded up his new ROM, rebooted then applied your 2nd kernel and this thing is hitting 15626 in CF benches!​

Not sure what is going on, but I can't explain it. It may be my 2nd version of the kernel that fixes it, but I am not sure since I haven't seen a log yet. I suppose something may be jacked up with the early versions of recovery or roms, but the I was using the the same early versions when I tested just fine....maybe folks are losing recovery and don't realize it? I did the second step to keep recovery that is now automated in r2. If anyone has any ideas, let me know.
[Nexus 7 Original Development] _motley:
New version released

New version released...see OP. GPU OC to 446MHz (up from stock 416)

Looking for more feedback:cowboy:

View attachment 1204164
[Nexus 7 Original Development] danielsf:
Just out of curiously, would you ever try 520mhz for the gpu, to try to get it to t30 speeds? Or maybe would you consider some kind of app interface like extweeks for the galaxy s2 & s3 to control the GPU clock speed and maybe voltages instead of different kernels. As I would personally love to get the GPU to about 460-500mhz :) Anyway when I get my n7 (hopefully in a day or two) I can't wait to try this out :) (I am spoilt by the much more powerful 440mhz mali-400mp in the s3, so I would love to try to narrow the power difference between the devices GPU wise) :D
[Nexus 7 Original Development] Clienterror:
Nice man! The new versions fixed everything boots great! Now if we can just figure out how to make the Overclock stick after you turn the screen on/off. I'm not sure how to tell if the GPU OC is sticking.
[Nexus 7 Original Development] _motley:
Sure, we may push the GPU OC version a bit, but I always like to walk before we run to see how things go. I would like to monitor heat output, battery usage etc. and then move forward in steps. I am very happy with it right now, but dynamic configuration would also be cool. Let me know what you think once you have it hand.

Awesome, glad to hear it! I don't think I see this issue with the OC sticking after you turn the screen off/on, but I will do more checking after work today.
[Nexus 7 Original Development] Clienterror:
Thanks a ton! Yea if you go into setcpu and make it 1.6 then turn the screen off then on (unlock) set CPU slider still shows 1.6 but if you read under that the smaller text says its actually set at.1.3 again. It seems to be a problem with the Atlantis kernel also something to do with hardcoded CPU freqs I think. Oh I wanted 5k soooo bad rofl got this twice rofl.
[Nexus 7 Original Development] evonc:
I've just made profiles that automatically set the clock to 1.5 when the screen turns on again and back to 1.5 when the screen turns off.

Edit*

Just tried the newest version and it failed to boot. Got stuck at the Google Logo. Here is the last_kmsg. Hopefully it helps :)

(had to put a .txt extension on it btw. Uploader wont let me upload w/o extension)
[Nexus 7 Original Development] MrPhilo:
The Nexus 7 GPU is better than the Transformer Prime due to the faster RAM, so more bandwidth? If I'm correct? Thats why we see a higher Nenamark score at a lower clock?
[Nexus 7 Original Development] hanthesolo:
This kernel looks very promising, excellent work! How much "play" have you had with upping the voltages, before the battery quits? On my TF, I can only go so far before the battery cannot provide enough juice, and it freezes on me. It would be interesting to know for people who want to OC really high. Does anything above 1.6 GHZ actually boot (heat and battery drainage aside)? It would be nice to OC up to 2.0 GHZ, if only for a proof-of concept. Finally, what are the temps you are getting on the higher clocks? It sounds like overheating may start becoming a real issue, and I was just curious.
[Nexus 7 Original Development] Kidromulous:
The ram disk version rendered my tablet unbootable had to flash the Atlantis kernel from fast boot to get it back up and running.
[Nexus 7 Original Development] killer23d:
Good work there, I would suggest adding Smartassv2 as well since it has been a good choice for many dev
[Nexus 7 Original Development] parcsalooc:
I for the life of me can't get this kernel to OC. Tried System Tuner, Setcpu etc. Max only reads 1300mhz nothing shows higher beyond 1300. I have no clue what the deal is. I've tried wiping also. Even tried Atlantis' kernel. on his, it won't allow me to set anything. Max shows 0 and Min shows zero. I am running Pauls Modaco Jr3 and even tried it on EOS' new release. I'm beginning to wonder if its something diff internally. Anyone have any guesses?Also showing root as setcpu requests superuser permissions.

This is what my device shows

Board: grouper

Product: nakasi

Model: Nexus 7

Device: grouper

Build: JRO03D (Modaco Custom ROM Jr3)

google/nakasi/grouper:4.1.1/JRO03D?402395:user/release-keys

Manufacturer:asus

Brand:google

CPU ABI: armeabi-v7a

Kernel

Linux version 3.1.10-motley+(cainm@motleyville) (gcc version 4.6.3 (GCC)) #6 SMP

PREEMPT Tue Jul 17 00:52:59 EDT 2012
[Nexus 7 Original Development] _motley:
Yep, fixed OP to clarify, both should work fine.

Two things to consider.

1) When the device sleeps and you wake it, it is going back to 1.3GHz. I am working on this and hope to have a fix before long. This is an OS limitation/feature, not a kernel issue.

2) Dynamic EDP will throttle the tab back when you hit 60C, so if your tab gets warmer, it is falling back to 1.3GHz and your scores won't be as high. If I open this up, scores will increase dramatically even when the tab is warm. I think most want performance, but not at the cost of an overheated cpu. So, when I need to bench over and over to test stability, I set it the AC vent to keep it cool.

Just tested with V(R) and got a 4999 on the first try. I am running the latest Modaco ROM right now.

Try Antutu for overall testing and Nenamark2 for GPU, they is better. With Antutu, make sure you keep your tab cool, it will hit the 60C temp throttle easy if you bench over and over.

Hi, which model do you have, 8 or 16GB? We should start comparing as we discuss this. My 16GB N7 kills my prime with i/o speed. Quadrant is not a good i/o testing tool at all. My last Antutu gave me 18.3Mb/s write (150) and 32MB/s read (194). However, I read somewhere that ICS was beating JB at i/o performance, not sure why. Try playing around with the i/o scheduler (sio or vr work best). Also, make sure you don't have some app causing a lot of i/o in the background when you are running tests. That will certainly do it.
[Nexus 7 Original Development] _motley:
Good to hear brother!
[Nexus 7 Original Development] CooLoserTech:
My device has been heating up lately on the left side. Im going to flash the latest build and see if that solves anything like said in OP
[Nexus 7 Original Development] danielsf:
Everything is working great, although I still am not sure about undervolting, set cpu as we know just doesn't set, voltage control app says I am running at 0mV (impossible) and system tuner shows much lower voltages currently being used than set cpu does, not only that system tuner shows two voltages for near enough the same cpu frequency. Combine these two from system tuner and the one from set cpu, I now have 3 different sets of different voltages for the same frequencies and no idea which ones are safe and the right one, and which frequencies out of the two sets in system tuner are the ones I can edit. I am really sorry if this made no sense as it is kind of hard to explain, there are screen shots of the three different sets of voltages to help illustrate what I am trying to explain.

Also, coming from the stock kernel, I swear the amazing spider man game now plays smoother, on stock I didn't even what to play it as it was just so laggy, now it seems playable. I don't know if that in my head, but if defiantly feels like it has a few FPS higher generally :)

Edit: One more thing, my cpu isn't spiking to 1.6ghz anymore, this is my daily driver now, thank you very much :) Also may I ask, did you edit the way the cpu scales compared to stock, as in on single threaded application one core could go to 1.3 whilst if more than one cores was active for multi-threaded applications the cpu was limited to ~1.2ghz. Just looking at some of the performance increases, has this lowering of the max cpu frequency when more than one core is active been removed? :) Are you ok with me putting a link to your kernel in my signature please? I like to share what kernel I am using with what device in my signature, as you can see with my other device below. I just thought I should ask your permission as it is your kernel :)
[Nexus 7 Original Development] CooLoserTech:
result: a bit cooler actually, runs smoother too
[Nexus 7 Original Development] _motley:
Thanks, I know exactly what you mean:good: Looking into this as well...

Cool, It won't be anything dramatic, especially as related to bench testing. Exactly why I didn't turn off EDP completely and just let it smoke. We'll see how these voltages go and then lower a bit if we think we can get away with it. Some claim they are unstable at 1.6, but I have never had any issues pushing it to the max.
[Nexus 7 Original Development] DJLamontagneIII:
Flashed b39 and eos ROM and its running like butter at 1.6 thanks a lot bro
[Nexus 7 Original Development] Shano56:
So I did some testing, and found something odd. I can successfully set the CPU speed to say 1ghz. CPU spy verifies this. However, once the screen turns off, it resets back to 1.3 (and CPU spy shows activity at 1.6)

Edit: Hmm, just saw your post about it resetting. But still, CPU spy shows 1.6 after screen off/screen on
[Nexus 7 Original Development] paddycr:
Great work as always motley. Good to see you deving for the Nexus 7
[Nexus 7 Original Development] nicknowsky:
Flashed and testing now, so far so good, will push it a little more now
[Nexus 7 Original Development] Dsmforlife92:
Any one try this on modaco jr 5
[Nexus 7 Original Development] katestar:
Thank you so much, my cpu is staying at 1.4ghz now instead of jumping to 1.6ghz when set to 1.4 :D I am so looking forward to eventually pushing that GPU a little higher :D and working undervolting. Thank you so much mate :)
[Nexus 7 Original Development] brizey:
Running it right now. No issues.
[Nexus 7 Original Development] nicknowsky:
quadrant scores look good
[Nexus 7 Original Development] Prey521:
With the old kernel, I couldn't step down the voltage more than 4 steps @ 1.6ghz without it bootlooping. With the new 39 build, I have it currently stepped down 5 steps and 10 passes in the cpu stress test app and it hasn't crashed yet though obviously warming up. Gonna try to step it down to a 6th step across all the cpu frequencies to see how it holds up. Lovin this kernel!!!
[Nexus 7 Original Development] demandarin:
Just flashed the 39 build. Seems to be working great so far. I uses system tuner pro to raise the Max CPU speed to 1.6ghz. Mines take the overclock fine. I left it on sio scheduler and didn't mess with none of the voltages(as I've never messed with that aspect of tweaking and don't want to mess anything up). First run of quadrant went well. Scored a little higher than the poster above me. This kernel gives high fps.

Where is that zram located in the file system? Couldn't find it. I could just use Script manager to execute it with SU and boot, correct? Would I choose is script or executable? I remember you said a few pages back you was going to add a script to enable zram but I didn't see it. What is the script, if what I said won't work? I just enter the script in script manager alone or I need to do this through terminal emulator first? Sorry for the questions but can't find the zram file to try out what I said first.
[Nexus 7 Original Development] Prey521:
Quadrant is useless :)
[Nexus 7 Original Development] P1 Wookie:
Kerenel running good on eom aside from the already known issues.

Notice very little time is spent at the 860-1200 range. Mostly 340 or 1300.
[Nexus 7 Original Development] demandarin:
Damn Motley..lol. I just ran RL SQlite benchmark(I/O performances) My score overall was 33.941 secs. I'm at the very top of the list above all other devices. I would do a screenshot but don't know how to on jellybean. Damn, lightyears faster than prime. I faster than all other devices listed. Build 39 rocks for sure ;)

Who said I/O performance was worse on jellybean? Lmfao
[Nexus 7 Original Development] M3drvr:
Hold volume down and power for screenshot
[Nexus 7 Original Development] demandarin:
thanks. just did it. here is my screenshot attached. I love the fact that opera mobile allows you to upload files from nexus 7 file system like a pc.
[Nexus 7 Original Development] CooLoserTech:
I pushed it to 1400 and not so much heat any more. Runs smooth in TASM and TDKR