yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] gokul.s.vlr:
Dear all,

i just bought this Dual sim android 2.3.6 Karbonn A7 mobile:confused:.i could not find drivers at the company website or any other website. i need it to connect to my pc to acess internet via mobile.:confused:
[General Questions and Answers] prasad12ka4:
Head here:

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

Go above for methods
[Samsung Galaxy Nexus] Xleogun:
I have recently purchased my Nexus it was working fine but i got this screen yesterday while booting. I tired to connect it to my PC but no luck all it does is tells me that the drivers failed to install. I called up google, they didn't know how to help me. They told me to take it back to the place i bought it. I tried looking for this type of error no luck.

Can someone help me out with this please ? Thanks.

View attachment 1170297
[Samsung Galaxy Nexus] imnuts:
You're missing the kernel and/or recovery. What did you try to flash that failed?
[Samsung Galaxy Nexus] rjcapp:
sorry never seen that particular screen. Besides rebooting what have you done to the phone? mods? etc....
[Samsung Galaxy Nexus] efrant:
That screen means your bootloader got corrupt somehow. You need to re-flash your device to stock using Odin. Assuming you have a GSM device, see this thread for details. Note that since your bootloader is corrupt, you can't boot into "odin mode", but Odin will download the images to your device if you are booted to the screen you are currently showing.
[Samsung Galaxy Nexus] Xleogun:
Thank you for your quick response i will read up on this try it out. :)
[Samsung Galaxy Nexus] imnuts:
It's not the bootloader, it's the kernel and/or recovery. I had the same screen on my Charge with a failed flash of the kernel, same with a failed recovery flash. I would also recommend using fastboot over Odin as it is generally "safer".
[Samsung Galaxy Nexus] efrant:
Not sure about the Charge, but I have tried wiping my kernel and recovery previously, and have never seen that screen. From other users experiences on the Galaxy Nexus, that screen appears when the bootloader is corrupt, so the phone cannot load up anything.

As for your recommendation to use fastboot (instead of Odin), how can you use fastboot when you can't boot into fastboot mode? :confused:
[Samsung Galaxy Nexus] imnuts:
Wiping the kernel or recovery is different then a failed flash of kernel or recovery. Wiping recovery just writes '0's to the partition in all likelihood. As far as the phone knows, it was successfully flashed, even if it doesn't boot.

As for not getting into bootloader mode, if you can't boot due to a corrupted bootloader, how are you booting into download mode? The phone is still booting, just to a different system. I would guess that if you can access download mode, you can access bootloader mode. Hold both volume keys while turning on the phone and you should get to bootloader mode where you can use fastboot. Volume down plus power is download mode.

EDIT: I've also seen users on the Stratosphere, Continuum, and Fascinate (all Samsung phones) that had a failed Odin flash (usually recovery, sometimes kernel) and when the phone restarted, that was the screen it was left on.
[Samsung Galaxy Nexus] efrant:
Well, I disagree with that - I do not think the device knows the difference from a bunch of zeros or half a kernel flash.

But that's the whole point: on a GNex, if you see that screen, you can't boot into download mode or into the bootloader. You can only boot into that particular screen. However, Odin still pushes the files to your device when in that screen.

If you're right and he can still boot into the bootloader, then I agree, he should use fastboot over Odin. But I don't think he can.
[Samsung Galaxy Nexus] jjc_01:
If you take out the battery, put it back in, and hold volume +, volume -, and power, what does your phone do?
[Samsung Galaxy Nexus] Xleogun:
nothing it doesn't go into recovery.
[Samsung Galaxy Nexus] efrant:
As I had figured, your bootloader is corrupt - when that happens, that is the only screen you will see. You need to use Odin to re-download the stock images to your devices.
[Samsung Galaxy Nexus] Xleogun:
Thanks, any idea where i would find the stock images ?

I did follow instructions on this thread [http://xdaforums.com/showthread.php?t=1586807 but now it's showing a blank screen.

it showed my this message after the process was completed.

<OSM> All threads completed. (succeed 0 / failed 0)

<ID:0/007> Added!!

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> bootloader.img

<ID:0/007> NAND Write Start!!

<ID:0/007> boot.img

<ID:0/007> recovery.img

<ID:0/007> system.img

<ID:0/007> userdata.img

<ID:0/007> radio.img

<ID:0/007> RQT_CLOSE !!

<ID:0/007> RES OK !!

<ID:0/007> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/007> Removed!!
[Samsung Galaxy Nexus] efrant:
Based on what you posted, that was a successful Odin flash. Are you saying when you reboot, you don't see anything at all anymore?

The files you flashed were the stock images.
[Samsung Galaxy Nexus] Xleogun:
yeah just blank and when I plug the device into my PC it told me drivers failed to install.

hmm okay. yeah I used stock IMM76D ROM.

Maybe i bricked it...
[Samsung Galaxy Nexus] efrant:
Strange. I have never seen that before after a successful Odin flash.

Regardless, you have one other option before I would consider it bricked: OMAP Flash. I don't have the thread handy, but search for OMAPFlash_tuna.zip
[Samsung Galaxy Nexus] Xleogun:
I found the download link to it.

I tried finding a guide to follow but i don't see any posted.
[Samsung Galaxy Nexus] efrant:
I believe the instructions are included in a text file within the zip.
[Samsung Galaxy Nexus] harveydent:
I borked a kernel flash last night and didn't get that screen. I got as far as the boot animation then it just stays there. I just pushed the kernel through fastboot to get out
[Galaxy S II Q&A, Help & Troubleshooting] lsrzj:
I noticed that all kernels I tried are with kernel_max set to 1 making the second CPU core disabled. If you go to /sys/devices/system/cpu and do a cat online it will appear 0, doing a cat offline will show 1 indicating that cpu 1 is disabled and if you do a cat /proc/cpuinfo it will show informations only for cpu0. If it's a dual core phone, why to put the second cpu offline?
[Galaxy S II Q&A, Help & Troubleshooting] spytrek:
I stumbled into the "cpu1" issue in proc yesterday while doing some comparisons between my S2 and my S3. My S3 has its original ROM (heck, I only just got it yesterday...) and cpuinfo e.g. shows me only cpus 0,2 and 3. /proc/cpuinfo of my S2 shows me only cpu0. To me it looks like as if /proc/cpuinfo ignores existing cpu1. (/proc might be depricated, but then why is it still there on ICS 4.0.3/4 ?)

/sys/devices/system/cpu/online on the other hand will ALWAYS show the correct amount of online cpu's. In my case on S2 (litening ROM/ litepro kernel) the output of /sys/devices/system/cpu/online is 0-1, on my unflashed S3 0-3.

My tip. Reboot your smartphone and look then at /sys/devices/system/cpu/online. I have the impression that either some app, the kernel itself or a bug turns a core off at somepoint. It happened to me yesterday (S2) which is what brought me into the search in the first place. I was having issues with my dialer/contacts freezing when trying to call. Something that should never ever happen (It's still a phone god damn it!! Imagine you need to do an emergency call and have to reboot the thing first!)
[Galaxy S II Q&A, Help & Troubleshooting] postfatal:
The core isn't permanently disabled, it's only disabled at that time to conserve battery performing an operation that only requires one core. Depending on the hotplug settings the phone with use core 1 when it needs to, which naturally the people who create kernels try to keep to a minimum to conserve battery. There are very few situations at this time that honestly require 2 cores. 1000 Mhz on 1 core can handle 99.9% of tasks.
[Nexus 7 Original Development] zaventh:
This is my first kernel build ever (not just for the Nexus 7). Just a starting point for more hacking on the Nexus 7.

Flashable zip package attached.

It should go without saying that anything you do with this package you do at your own risk.

Features

Insecure

init.d support

Overclocked to 1.5GHz

Voltage tweaks at OC clocks

BFQ scheduler

smartassv2 governor

lagfree governor

Made kernel version not suck

Notes

You should root and install busybox into /system/xbin before flashing this kernel. Don't flash this if you don't know what you're doing as I'm too lazy to include n00b instructions.

Credits

Thanks to Virtuous team for their updater-script for this device.

Source

https://github.com/zaventh/nexus7-kernel-grouper

Blog post

http://www.jeffmixon.com/custom-nexus-7-kernel-atlantis-r2-released/

Screens

Cheers...
[Nexus 7 Original Development] Caliyork:
That CPU score is sexy!
[Nexus 7 Original Development] MC153:
Great work! Now I definitely can't wait for my nexus to ship.

Edit: If you could try adding smartassv2. This is a popular governor that I would really enjoy on the nexus 7.
[Nexus 7 Original Development] jarjar124:
this is compatible with the stock rom right? ik it has to be rooted btw :P
[Nexus 7 Original Development] zaventh:
Yes it is... :cool:

Sure. I'll be adding several custom governors to choose from.

Yes, it's compiled from stock kernel sources.
[Nexus 7 Original Development] evilstewie23:
Thanks so much man. Can't wait to get my nexus so I can flash this. Hopefully before the 18th which is my birthday. I had heard though that smartass didn't work so well with more than 1 core though. Could you clarify on that.

Sent from my Rezound
[Nexus 7 Original Development] sparksco:
Smartass v1 was made for single core cpu's. Smartass v2 was made for dual core cpu's, so v2 might work better on a quad core? V2 doesn't really work all that well on my single core cpu for the phone I have.
[Nexus 7 Original Development] MC153:
Nice work! Can't wait to see the future of this kernel.
[Nexus 7 Original Development] zaventh:
Exactly right. I actually never really liked smartassv2 in general, but I think it is working out fairly well on the N7, actually.

This is after just a little bit of game time, some regular usage, and some sleep time. I may need to tweak some of the higher clock values so it scales up a bit more gracefully. At any rate, there will be plenty of options to play around with.
[Nexus 7 Original Development] danielsf:
So whats the heat production and stability like at 1.5ghz? When you say 1.5ghz, is that like the htc one x where it is actually 1.4ghz but you can go to 1.5ghz when only using one core, or is it all four cores clocked at 1.5 please? :) Got to admit that a gpu OC would be really nice. :) This looks great, thanks :)
[Nexus 7 Original Development] foxorroxors:
any chance of getting some gpu over clocks in then kernal, screw battery life give me mmmhhhzzz! :-)
[Nexus 7 Original Development] sparksco:
Is it possible to get scary gov on this? I think it's based on smartassv1 but not really sure. It gives me a good balance between performace and battery. Or perhaps we could make a scaryV2 lol?
[Nexus 7 Original Development] lhayati:
Great work for a first Kernel :)

Is the extra battery drain worth that .2ghz of extra horsepower? Because i've heard it's a perfectly capable device @ 1.3ghz.
[Nexus 7 Original Development] zaventh:
Thanks. Naturally, it's a matter of personal preference of course if it is "worth" it to OC any processor. OC'ing the N7 was more of a "because I can" thing than for any practical reason. The CPU is impressive as is.

The N7 is probably the fastest and most responsive mobile device I've ever seen even at stock, mostly thanks to the hardware but also due to Jelly Bean's ability to leverage this kind of raw power.

The actual battery drain between 1.3GHz -> 1.5GHz will all depend on how much time you spend at those higher clock speeds, of course.
[Nexus 7 Original Development] Dark_Knight2:
Thank you for this kernel. I cant wait for my nexus 7 :D

Sent From A Rotary Phone
[Nexus 7 Original Development] emergant:
Do we know at what speed the ram is clocked?

The transformer infinity uses DDR3 at 1600. The 300t is much lower though
[Nexus 7 Original Development] sparksco:
It's been confimred in the Q&A section that the N7 has DDR3 ram :beer:
[Nexus 7 Original Development] emergant:
Thanks. But DDR3-667 as in tf300 or DDR-1600 as in Tf700 or something else

I thought about putting this in QA but thought the dev might know. Sorry if that was a bad call
[Nexus 7 Original Development] sparksco:
Whops I meant general not Q&A

Hynix HTC2G83CFR DDR3 RAM

Hope that helps

http://xdaforums.com/showthread.php?t=1748933
[Nexus 7 Original Development] Adi_Pat:
Smartass V2 doesn't support scaling upto 4 cores ;)

Its useless for this device!
[Nexus 7 Original Development] emergant:
Yes apparently thats the Same as a MacBook not sure if that means its clocked at 1600 though

Thanks
[Nexus 7 Original Development] refx:
According to the following spreadsheet, found via the Hynix webpage for H5TC2G83CFR, it may be between 1066-1600, depending on what the chips were speed-binned to. Worst case, they can do 1066MHz at CL7, while best case, they can do 1600MHz at a massive CAS Latency of 11 :P I can't imagine there would be much difference between the performance of 1066 @ CL7 versus 1600 @ CL11.

Note: Remove the [dot] ;)

skhynix[dot]com/inc/pdfDownload.jsp?path=/datasheet/pdf/dram/Computing_H5TC2G4(8)3CFR(Rev0.2).pdf

Sorry for the further derail!
[Nexus 7 Original Development] sparksco:
http://xdaforums.com/showpost.php?p=28262649&postcount=9
[Nexus 7 Original Development] emergant:
That sounds like very good news to me

Either of those extremes places it ahead if a prime or a tf300 in terms of memory speed. Excellent value
[Nexus 7 Original Development] jutley:
18th is also my birthday and also waiting for my nexus 7.

---------- Post added at 12:03 PM ---------- Previous post was at 11:58 AM ----------

Can someone try this core control on nexus7 it will drop the quad CPU down to 2 cores saving battery life whilst screen is on.

http://xdaforums.com/showthread.php?t=1652136
[Nexus 7 Original Development] danslides:
Thanks for the work. It's fast!

Side note, I do notice more heat from this. Anyone else?
[Nexus 7 Original Development] zaventh:
I'm sure that app will work, but you won't need it. The kernel SMP logic is actually extremely efficient already. Only one core is online by default until the others are needed, and it is VERY hard to even stress this thing enough to get all 4 cores to turn on. I have to run artificial load scripts to bring all four cores online for over 1 second. Battery life is amazing even at 1.5ghz...
[Nexus 7 Original Development] MrPhilo:
Seems like Asus has put a poor memory in. The i/o is terrible, just like the Transformer Prime. Transfer speed must be bad?
[Nexus 7 Original Development] lhayati:
Well one thing that I have learnt from past experience is that quadrant lies.
[Nexus 7 Original Development] haloimplant:
According to the data sheet the eMMC chip is capable of sequential 28 MB/s read and 14 MB/s writes. I'd be very happy to see 10+ MB/s file writes though USB. I asked in the Q&A section if anyone has tested this yet.
[Nexus 7 Original Development] Locklear308:
Only 4000? My Galaxy s2 can now reach 3800 without overclocking.
[Nexus 7 Original Development] Seamonkey79:
I once downloaded a tweaked kernel for my Acer Iconia A500 that let it get over 4100 at 1.0Ghz on the Tegra2.

Quadrant relies far too heavily on relatively minor things to be anything more than a way to make people come out of the woodwork and say 'only XXXX I got XXXX on my NNN NNNNN 3' :cyclops:
[Nexus 7 Original Development] chichoko:
Exactly this. It's been stated many times that, unless you are running a resource heavy app/game, only one core will be active while using the OS for browsing, listening to music, watching movies etc. so battery life should be exceptional to say the least.

Thanks for the kernel mate! I'll surely try it out when I get my hands on my N7.

And I'll jump on the bandwagon aswell and announce that:

I CAN'T F***ING WAIT FOR MY N7 TO ARRIVE :D
[Nexus 7 Original Development] zaventh:
R2 release... mostly added BFQ scheduler and some aforementioned governors.
[Nexus 7 Original Development] cwc3:
Could I pester you for some benchmarks from my favorites:

AnTuTu Benchmark

NenaMark2
[Nexus 7 Original Development] zaventh:
AnTuTu doesn't support JB/N7 apparently.

NenaMark2:
[Nexus 7 Original Development] cwc3:
Silly AnTuTu... Anyways, much appreciated! :)
[Nexus 7 Original Development] Kidromulous:
Running this kernel now. So far so good. Seems very solid.
[Nexus 7 Original Development] DynaMight:
Running fine for me so far.

Running at 1.5Ghz

---------- Post added at 11:28 PM ---------- Previous post was at 11:20 PM ----------

Actually, just noticed with overclocking the same thing is happening that happened on my Galaxy Nexus running Jelly Bean. You set the clock speed to say 1.5Ghz, it'll run at that speed until you turn off the screen, then it'll reset back to 1.3Ghz again.

This was fixed by editing a file, no idea what was changed. Heres a link to a custom kernel for the GN: http://rootzwiki.com/topic/11552-gn...sotgfiopsv018jun-07/page__st__940#entry795598
[Nexus 7 Original Development] zaventh:
Interesting, thanks. I was looking in that... thought it was some kind of kernel bug. Have you tried replacing that file on the N7 yet?
[Nexus 7 Original Development] DynaMight:
Nope. I assume its custom to the Galaxy Nexus since the device name is actually 'Tuna'.

Just checked on the Nexus 7 and the same file appears to be called 'Power.default.so'
[Nexus 7 Original Development] zaventh:
Thanks. Going to be super annoying if I have to compile JB from scratch to fix it... but I'll check it out. For now you can use an app like SetCPU to reapply the OC value when the screen turns back on.
[Nexus 7 Original Development] sadegh1993:
hello

have this Kernel support GPU OC ?

Thank you
[Nexus 7 Original Development] Rich_RH:
Wondering does this kernel work with KRAKD?

http://xdaforums.com/showthread.php?t=1745904
[Nexus 7 Original Development] zaventh:
No reason it shouldn't. Just flash the custom ROM first, then this kernel. If you update the ROM, you'll have to reflash the kernel again.

There's no GPU OC in this kernel right now only because I don't see any point currently. Nothing I've tested even touches the 12-core GPU.
[Nexus 7 Original Development] evonc:
Flashed the kernel last night and no issues whatsoever. Everything running flawlessly. Great work!

Sent from my Nexus 7
[Nexus 7 Original Development] :
Flashed this kernel, no issues since last night. Thanks for developing for this kickass tablet!

I'm using interactive governor and noop scheduler while the screen is on. Powersave and deadline when screen is off. Any recommendations to improve battery life without significant lag?

Sent from my Nexus 7 - 1.5 Ghz OC Atlantis R2
[Nexus 7 Original Development] :
What apps are you guys using to adjust the CPU?

Is it only setCPU?
[Nexus 7 Original Development] demandarin:
system tuner would be even better. that app does EVERYTHING set CPU does & alot more.
[Nexus 7 Original Development] :
System Tuner is also free. I use Setcpu because I paid for it and it is only focused on cpu tweaking.

MB860, CM7.2.0, Faux 026b1 1Ghz
[Nexus 7 Original Development] zaventh:
Cool. No special tips for the N7... same battery-saving techniques as any device apply here. I am adding a few more things to the kernel that should boost power efficiency a bit all around, though.
[Nexus 7 Original Development] :
Thank you Sir! Will be anxiously awaiting your new kernels. :D

Sent from my Nexus 7 - 1.5 Ghz OC Atlantis R2
[Nexus 7 Original Development] ericsch333:
Nice job so far so good running great and installed with tarp
[Nexus 7 Original Development] dude2k5:
Niceee
[Nexus 7 Original Development] psouza4:
Hmm... interesting scores, but I'm not able to get anywhere near them. In fact, my scores have dropped considerably since flashing this kernel.

Running stock ROM and this kernel (all I've done is make sure its max freq is indeed 1500 Mhz and that it's using the smartassv2 governor).

Quadrant dropped from ~3600 from stock to ~2800 on this kernel.

Any thoughts?

UPDATE: using motley's kernel (alpha v1.0.3 #17) I get scores around ~4500. Went back to this kernel and same ~2800 scores. Something peculiar going on...
[Nexus 7 Original Development] DJLamontagneIII:
Have you tryed a different governor.. Smartass v2 is really slow for me but interactive or ondemand are nice and fast
[Nexus 7 Original Development] psouza4:
Thanks for the recommendation -- I shouldn't assume that the smartass governor is stable yet.

I can push 4250 with performance and 4300 with interactive, but am surprised that smartass performs so dramatically poor (again: 2800). Incidentally, my test with motley's kernel was using interactive, though he clocks @ 1600 max and also OC'd the GPU, so the slightly higher score is expected. I still can't reach 4500+ with this kernel, but can live with using only interactive for now until smartass is stable on this device.
[Nexus 7 Original Development] M3drvr:
I believe interactive works the best since it is the stock governor on Jelly bean. I've always had best results with it.
[Nexus 7 Original Development] churchrickshaw:
have you guys had your tablet power off by itself? it's happened twice already but i actually get "powering off"
[Nexus 7 Original Development] bovineyard:
Can't change cpu setting in SetCPU?/ Support USB OTG?

Does this kernel hold at 1500mhz? It won't change in SetCPU.

Also, does it support USB OTG (On the go) for USB sticks?

Thanks.
[Nexus 7 Original Development] DJLamontagneIII:
It stays at 1.5 its when the screen shuts off it reverts back to 1.3 because JB has built in screen off profiles you can fix this by setting a screen on profile in setcpu
[Nexus 7 Original Development] :
+1 on what he said. Mine goes into deep sleep when screen is off.

Sent from my MB860, CM7.2.0, 1.3 Ghz Faux

Here's some benchmarks I ran...

Stock kernel, interactive 1.3 Ghz

Atlantis R2 interactive 1.3 Ghz

Atlantis R2 Smartass V2 1.5 Ghz

Hope this helps!
[Nexus 7 Original Development] primetechv2:
Hey, one more dumb question (I'm downloading your kernel anyway to see if I can figure it out):

Does this support IPTables (and thus proxying/Orbot)? I have rooted my device and realized it needs a new kernel to boot.
[Nexus 7 Original Development] oasis9389:
WHat settings is everyone using with this kernel. I'm simply on interactive with snoop.. any suggestions _
[Nexus 7 Original Development] drewzee:
I have a boot loop after flashing the kernel. Came from cm10 nightly with stock kernel. Flashed and then wiped cache/dalvik and now I'm looping. Can't get to recovery either. Anybody get this?
[Nexus 7 Original Development] breakingspell:
I just got done reflashing CM10 in order to fix this issue. I had to go in with fastboot and reflash the recovery just to get in and reapply the zip. I'll probably have to wipe data and system in case there's stuff in there that'll come back to get me for sloppily reflashing a ROM

I've tried this kernel with the two CM10 roms floating around, and the other kernels as well, but each time, it perpetually shows the CM9 boot animation (can't wait for CM10's). Is this kernel meant only for stock ROMs?
[Nexus 7 Original Development] drewzee:
That's what I ended up doing as well. Its weird that it locked up recovery as well, I've never had that happen after flashing a kernel. Oh well.
[Nexus 7 Original Development] lightninbug:
So after reading the last couple comments I figure I'd ask first...is this kernel 100% safe to use with Paul's kitchen ROM jr5?
[Nexus 7 Original Development] zaventh:
This kernel is for stock ROMs only. It will not work with AOSP/CM.