yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G2x] TwitchyEye:
It sounds like you probably have a borked baseband due to incorrectly partitioning the phone as a p999. Search the p990 forums for a partitioning tool that should enable you to flash the correct ROMs and will hopefully fix your baseband issue.

Edit: here's one http://xdaforums.com/showthread.php?t=2020737

Edit2: there is also a slight chance that you have a freakish phone and that nothing will work. Just thought I'd throw that out there as an alternative possibility.
[T-Mobile LG G2x] stickyiky:
thanks dude but i did that nothing seems to happend, i tried flashing another rom and the 3g appear but i can't make calls or even access my sd card.... it didn't seems to mount my sd card!!!
[T-Mobile LG G2x] stickyiky:
thanks dude am on that trying to see if that would help me!!
[Nexus 7 (2013) Original Android Development] tiny4579:
*NOTE* I have switched the kernel base to CM's from stock so it can properly support the CM ROM. This will mean dated releases instead of the numbered releases. It also means that it's possible that it won't work with older CM builds and may not work properly with stock at all. Sorry for any inconvenience. I will try to stay on top of CM's kernel changes as much as I can and will update when I see an update on their end or when adding new features.

/* NON-STANDARD DISCLAIMER:
I understand that if I disable fsync I am liable for any possible data corruption that could result. While dynamic fsync has been added, there is still the risk of data corruption.
*/

NOTE: Remember this is beta and it may not work on everyone's device

Changelog:

09/27/2013

latest kernel merges from CM (for best results, you should be on the 9/26 build or later

GPU OC to 450MHz (currently not selectable)

Faux123 Sound Control

User Voltage Control

Kexec-hardboot support (for Multi-ROM)

Battery gauge driver enhancements from tni.andro

USB fast charge support

09/13/2013

S2W/S2S and DT2W off by default

enhanced Simple GPU governor

cgroups: timer_slack: forward port timer_slack to 3.4. http://lwn.net/Articles/431847/

adjust sweep2wake, suppress if more than one finger down

Makefile adjustments

Add shortsweep option

rework s2w and dt2w, now we're getting somewhere

fix for app-mounted directories (thanks [MENTION=1951402]mkasick[/MENTION])

sweep2wake/doubletap2wake adjustments

update ARM topology and add cpu_power driver

Makefile optimizations

switch: do_fsync() to fget_light()

Sweep2wake and Doubletap2wake for the Nexus 7 (flo)

arm optimized crypto algorithms

use glibc memcpy and libstr

add intellidemand governor

add /dev/frandom

fiops and sio schedulers

Linaro 4.8 fixes

synced with CM's kernel/google/msm kernel

Downloads:

http://goo.im/devs/tiny4579/flo/kernels

mirror broken right now

Mirror (thanks MBQ_ for hosting space):

http://mbqonxda.net/tiny4579/flo/kernels

You can help MBQ_ with hosting costs by donating to him.

Source:

https://github.com/tiny4579/tinykernel-flo

cm-10.2 branch for Android 4.3

Installation Instructions:

1. (Optional) wipe dalvik+cache.

2. Flash in recovery
[Nexus 7 (2013) Original Android Development] teh roxxorz:
Anything special? Or just unsecure? Any governors?

And appreciated.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Original Android Development] drdrewdown:
good lookin out, just flashed & booted up fine. Will experiment with it for a bit
[Nexus 7 (2013) Original Android Development] tiny4579:
A few tweaks for now. Overclocking and voltage control. I also added the simple GPU governor.

It's a zimage kernel so if you wanted insecure you'd need to flash that one first before this one.
[Nexus 7 (2013) Original Android Development] teh roxxorz:
Ahhh, sweet. Appreciate it.

sent from the 7th nexus of 2013
[Nexus 7 (2013) Original Android Development] plh233391:
Download link bad
[Nexus 7 (2013) Original Android Development] drdrewdown:
works fine here.
[Nexus 7 (2013) Original Android Development] plh233391:
Are you downloading from computer or tablet? Cause on chrome and opera from the tablet I get 404 error
[Nexus 7 (2013) Original Android Development] drdrewdown:
pc, i uploaded to dropbox for you http://db.tt/qGyWyzIn
[Nexus 7 (2013) Original Android Development] Crooke356:
Request desktop site if your having issues finding the link
[Nexus 7 (2013) Original Android Development] Albinoman:
Working great so far!

Sent from my Nexus 7 2.0
[Nexus 7 (2013) Original Android Development] dark2099:
Going to guess the preferred method of adjusting options is via TricksterMod for now?
[Nexus 7 (2013) Original Android Development] klobkelosh:
Hey tiny!
[Nexus 7 (2013) Original Android Development] Jeremiah_1988:
Tiny, ran your stuff on my gnex, glad to give this a shot!
[Nexus 7 (2013) Original Android Development] nhidog:
Nice I undervolted everything by 100mw and over clock to max speed and running stable.
[Nexus 7 (2013) Original Android Development] DJBBOX:
USB-OTG?
[Nexus 7 (2013) Original Android Development] Malvarose:
How's the kernel? Any good? Worth flashing? Features?
[Nexus 7 (2013) Original Android Development] ChemicalSymphony:
Tiny is the reason I can still use my old incredible. I'll try this as soon as my N7 gets here.

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] jlevy73:
Thanks for the kernel, working perfectly thus far.
[Nexus 7 (2013) Original Android Development] tiny4579:
At some point probably. I just wanted a basic feature set and release something that has some benefits over stock.

Since this a beta I didn't post a change log. Read my post on the previous page or check my github.
[Nexus 7 (2013) Original Android Development] tiny4579:
OTG is already supported in the stock kernel. If you mean USB drive mounting, that's a ROM thing.
[Nexus 7 (2013) Original Android Development] DJBBOX:
USB-OnTheGo in order to work needs kernel patches which makes it a kernel thing not a ROM thing in my understanding. Like CM kernel USB-OTG is listed as a kernel feature. But thanks. Somebody shoukd realeased something soon:good:
[Nexus 7 (2013) Original Android Development] tiny4579:
USB OTG worked out of the box on the OG N7 and Galaxy Nexus as long as the device was low powered. I did a little Google search and the Nexus 4 didn't support OTG out of the box. WIth another quick Google search I see some reports of OTG working on N7. What does not work for you? USB sticks or mouse/keyboard? USB stick functionality does NOT work out of the box on AOSP or stock.
[Nexus 7 (2013) Original Android Development] tiny4579:
A known issue with beta1. It won't undervolt below 850 mV even if you select lower. That is because I forgot about the voltage regulators which actually regulate the voltage. Incredikernel users on the incredikernel may remember something that Chad had to fix as the undervolting wasn't actually working properly at the intended lower values.
[Nexus 7 (2013) Original Android Development] DJBBOX:
Yes! Storage! Thumb drives does not mounts. I founf patches for N7 grouper but not for flo
[Nexus 7 (2013) Original Android Development] tiny4579:
If it's what I think it is, it's the ramdisk and I don't touch the ramdisk. Personally, I like to keep the existing ramdisk for better ROM compatibility. It will be added to the custom ramdisks eventually. For now try stickmount in the play store.
[Nexus 7 (2013) Original Android Development] immunityx:
Can you raise the overclock more? The snapdragon 600 chips are stock 1.7ghz and Google underclocked the chips to 1.5. These chips can easily run stable at 2.0ghz like on the HTC one
[Nexus 7 (2013) Original Android Development] tiny4579:
I've yet to see concrete evidence that this chips are 600's. Most of what I'm reading points to s4 pro. I've built a test build that clocks to 2.16 but it doesn't even boot for me. I was going to take a middle ground of 1.9ghz as I don't want to mess with pushing voltages much higher.
[Nexus 7 (2013) Original Android Development] immunityx:
Hey tiny, heres the info - http://www.androidauthority.com/nexus-7-2013-s-4-pro-snapdragon-600-249594/

I believe 2.1 ghz was the limit on htc one phones as well many users couldnt boot at that speed but the 2.0ghz speed step was stable, im not sure of the actualy speed step i believe it was the low 2000mhz step if thats possible or it might have been a high 1900's mhz step.

Hope this helps

Thanks
[Nexus 7 (2013) Original Android Development] tiny4579:
I think its safer to take the middle ground regardless if it's a 600 or a pro. They're pretty similar. If its the 600 it should be able to go higher than the s4 but notice it doesn't say apq8064t which is a snapdragon 600. Is this request just for bragging rights? Real world difference would be insignificant between the clock speeds.
[Nexus 7 (2013) Original Android Development] immunityx:
I agree i think it would be much safer and theres probably no difference besides pointless benchmarks at the 2ghz clock, just tested myself on the wife's htc one it scored higher at the 1.9 clock then the 2.1ghz clock.
[Nexus 7 (2013) Original Android Development] bmakk2055:
Could you add this to your kernel http://mehrvarz.github.io/nexus-7-kernel-download-page/ from Nexus 7 grouper? To charge from a y Cable.
[Nexus 7 (2013) Original Android Development] Waynato:
[Q] : (Ok took me forever to get to 10 post but i needed to ask this here). Is there a way to enable your kernel to support loopback devices or add it to your kernel "also is that called multirom"? This is very important to me right now was i am trying to run linux. Thanks in advance
[Nexus 7 (2013) Original Android Development] Poser:
Fwiw the step is 1998, for 2ghz
[Nexus 7 (2013) Original Android Development] jdhas:
This would be a wonderful thing to have....
[Nexus 7 (2013) Original Android Development] Tuanies:
I wonder if the SoC in the N7 (2013) can hit the 1.9 GHz the S600 in the GS4 is clocked at. Would make for an interesting comparison, clock for clock.
[Nexus 7 (2013) Original Android Development] nhidog:
Same I tired 2160 and it just hung at Google logo, although 1890 boots and benches just fine. Trying to overclock the GPU to 450 but doesn't seem to want to take the value. Then again I'm new to this kernel compiling, I could just be doing it wrong.
[Nexus 7 (2013) Original Android Development] jassycliq:
GPU only allows for a maximum of 4 frequency slots. If you're just adding the freq it won't work. Also it should be 487mhz or 533mhz replace 400 with one of those, for examples look through some of the N4 kernel repos
[Nexus 7 (2013) Original Android Development] immunityx:
Give 1998 a try
[Nexus 7 (2013) Original Android Development] nhidog:
Tried 1998 and 1945 (or whatever step is below it), neither worked. 1890 appears max, well least to my limited kernel oc knowledge.

---------- Post added at 02:03 PM ---------- Previous post was at 02:02 PM ----------

Yeah I was looking at elementalx htc one which has 450. I'll check some of the other ones out.

Updated: Cool got it to boot 487.
[Nexus 7 (2013) Original Android Development] tiny4579:
I can't get mine to boot at 1890. What did you change from the source I pushed to github to make it work?
[Nexus 7 (2013) Original Android Development] nhidog:
I removed the default 1512 so there's a more even spread. Also found GPU @ 450 is same as 600. Probably anything over 450 is just placebo.

File is attached, should be able to drop it in.
[Nexus 7 (2013) Original Android Development] tiny4579:
New beta for those who care.

It has 1890 Mhz support and 450 MHz GPU overclocking. Also, I fixed an issue where voltages would not drop below 850 even though you could select those voltages in Trickster Mod. This was a regulator issue. I know jassycliq took care of it first. I had it fixed a few days ago but didn't push code up.
[Nexus 7 (2013) Original Android Development] jerrylzy:
Higher PVS chips may be able to boot at a higher frequency. Mine is PVS 4 and can boot at 2160mhz
[Nexus 7 (2013) Original Android Development] Crwolv:
Awwww. Download link is dead
[Nexus 7 (2013) Original Android Development] Txwolf1980:
Tiny, I know you've probably walked away from this, by now. But, if not, I'll be happy to do beta work for you. I just got my flo, and was excited to see your name.
[Nexus 7 (2013) Original Android Development] tiny4579:
No. I haven't walked from this kernel. I just havent spent as much time on android kernels as much lately. My plsn is to migrate over to cm support but I was getting some weird bootloop issued trying to boot it and didnt get around to a lot of troubleshooting to fix it. (Something to do with the rsmdisk even though I use the roms ramdisk).

What other device do you remember me from?
[Nexus 7 (2013) Original Android Development] tiny4579:
I'll probably work on it tomorrow night.
[Nexus 7 (2013) Original Android Development] Txwolf1980:
Toro. I'm glad you're sticking with it. Yours is my goto for my phone.

The link is dead though. It may have gotten shuffled when MBQ did his revamp the other day.
[Nexus 7 (2013) Original Android Development] tiny4579:
I'm using goo now. Check the OP. I hope you don't mind my rebase to CM's kernel. I added timer_slack and edited the ramdisk for timer slack support.
[Nexus 7 (2013) Original Android Development] aamitabh28:
Wow Big update..Thanks..wil test and report back
[Nexus 7 (2013) Original Android Development] Txwolf1980:
Nope. Honestly, I'm still learning kernels. I know how the basic stuff works (clocking, voltages, governor, scheduler), but not the in depth stuff (modules, tweaks like fsync and what not) do I don't know enough to be picky about something like a rebase to cm. Besides, all of the roms I've run on this is cm kernel, and they've proven to very stable.

At the risk of being presumptuous, one feature is really like to see is the ability to use dynamic sound (I think that is the proper term. If not, education is welcome). Where you can increase volume in trickster. The 1-3 scale, if I'm being clear.

I don't know if you happen to have I us in, yet (I'm getting ready to download it, now), but, if not, what are the chances of it?
[Nexus 7 (2013) Original Android Development] tiny4579:
Is it fauxsound you're talking about? I can add a sound mod. I don't see a problem with that.

I'll add overclocking and undervolting later, I just wanted a stable base. My booting issues earlier turned out to be an issue with the way the boot.img was packaged (start of actual ramdisk address in the image - so part of the ramdisk was overwritten).
[Nexus 7 (2013) Original Android Development] tiny4579:
Anyone else having a problem with WiFi staying asleep when the phone going to sleep and causing major wakelock issues? I haven't changed anything from cm that should cause this. I don't know if it's a kernel issue or not but when switching between this and cms kernel I can reproduce the issue only on this kernel.
[Nexus 7 (2013) Original Android Development] freeza:
Looking forward to voltage control and oc support. Loving the cm branch build. The cm kernel is the only one that hasn't given me issues.
[Nexus 7 (2013) Original Android Development] tiny4579:
There was someone talking that undervolting doesn't help that much with battery life as the SOC has built in AVS support which lets it adapt to its needed voltage. It even kicks in after setting the initial voltage so battery savings would be minimal. I don't have the link but it was in the ElementalX kernel thread for M7. It still should be relevant on the N7 flo due to the SOC similarities.

Though I will still probably add it anyways due to the desire to tinker. What really interests me is flar2's new GPU OC. It will allow on the fly GPU speed control. I'm thinking about bringing that in.

So far the kernel wifi dropping issue still exists for me on this kernel. It usually happens within an hour or two of the tablet going to sleep. When this happens I have to manually toggle wifi but it takes a bit to connect. It's easiest to reboot. After over a day on franco I'm not having this problem. It's also not an issue on CM's stock kernel. I'd rather go straight from CM's source to ensure the best CM compatibility.

It must be a patch I introduced but what I haven't had a chance to narrow down yet. It's weird that no one has posted about this issue yet. Must either be an issue only on my device or not a lot of traffic in this thread.
[Nexus 7 (2013) Original Android Development] freeza:
That's interesting, because I don't have this problem at all and I've been running your kernel since yesterday. Let my tablet idle overnight and WiFi was still connected this morning. Your kernel and stock CM, surprisingly, has been the only ones to function properly on my tablet for long periods. Every single other kernel I have tried exhibits this weird graphical glitch after I've played a game.

https://dl.dropboxusercontent.com/u/17013328/N7screentearing.mp4

Your kernel has been the smoothest experience by far.
[Nexus 7 (2013) Original Android Development] tiny4579:
Do you have wifi set to sleep or always on?
[Nexus 7 (2013) Original Android Development] freeza:
always on.
[Nexus 7 (2013) Original Android Development] tiny4579:
Mines set to sleep to save battery. Maybe a problem with WI-FI suspend or something. I might have time to check it out tomorrow. Is start by revering some cherry picks. It might be a defconfig issue.
[Nexus 7 (2013) Original Android Development] flar2:
The undervolting comment was in this forum. I haven't looked into AVS yet, I'm going to try disabling it. AVS isn't enabled on teh m7.
[Nexus 7 (2013) Original Android Development] tiny4579:
Hey, do you know what might be causing wifi to fail to suspend properly for me?

<3>[ 1335.587738] wlan: [6:E :HDD] hdd_is_apps_power_collapse_allowed: do not allow APPS power collapse-pmcState = 1 scanRspPending = 0 inMiddleOfRoaming = 0
<3>[ 1335.587738] wlan: [6:E :HDD] wlan_suspend: Fail wlan suspend: not in IMPS/BMPS
<3>[ 1335.587768] wlan: [6:F :HDD] hddDevSuspendHdlr: Not able to suspend wlan
<3>[ 1335.587768] dpm_run_callback(): platform_pm_suspend+0x0/0x54 returns -1
<3>[ 1335.587799] PM: Device wcnss_wlan.0 failed to suspend: error -1
<3>[ 1335.587799] PM: Some devices failed to suspend

I only saw a few posts by faux, and I don't have this problem on franco's or CM's. I know I pulled some of your patches. Check my github if you want to know which ones. I don't see how any of them are wifi related though. Maybe a defconfig setting?
[Nexus 7 (2013) Original Android Development] tiny4579:
I believe to have figured out the WiFi sleep issue.

Edit: Scratch that. It's still a problem. A workaround for now is to have the wifi set to always on or turn it off manually when not in use.
[Nexus 7 (2013) Original Android Development] tiny4579:
Man, this CM kernel is such a pain to maintain. It doesn't seem to like the tweaks as much. Adding overclocking gave me SOD's even without touching any of the other defaults and keeping a safe max of 1566.

Also, the WiFi sleep bug still exists and check OP for some workarounds.

Anyway, it's updated.
[Nexus 7 (2013) Original Android Development] tiny4579:
Does no one else have the WiFI sleep problem? I tried reverting something and it still didn't fix it. I also had the issue with Wifi set to always on.
[Nexus 7 (2013) Original Android Development] Luigi_2:
I mostly use wifi at home so no problems for me now :good:
[Nexus 7 (2013) Original Android Development] tni.andro:
You may want to try the latest CAF driver. It literally has hundreds of bug fixes over the standard Prima 3.2.2.17b.

http://xdaforums.com/showthread.php?t=2461735
[Nexus 7 (2013) Original Android Development] tiny4579:
EDIT: Ok. I just realized my stupidity. I was applying your diff against the old version. I was supposed to extract the drivers. My brain overlooked that part. Nevermind
[Nexus 7 (2013) Original Android Development] Luigi_2:
So that means it'll be fixed?
[Nexus 7 (2013) Original Android Development] tiny4579:
What do you mean? Didn't you just say you didn't have any problems?
[Nexus 7 (2013) Original Android Development] tiny4579:
Same issues with the new driver:

<3>[ 903.286956] PM: Device wcnss_wlan.0 failed to suspend: error -1
<3>[ 903.478820] wlan: [153:E :HDD] hdd_is_apps_power_collapse_allowed: do not allow APPS power collapse-pmcState = 1 scanRspPending = 0 inMiddleOfRoaming = 0
<3>[ 903.478820] wlan: [153:E :HDD] wlan_suspend: Fail wlan suspend: not in IMPS/BMPS

It looks like it's not a driver issue. I think it's a defconfig difference and since CM may not have their current defconfig up to date (they're updating cyanogen_flo_defconfig, but device/asus/flo points to flo_defconfig. I guess I can try rebasing to cyanogen_flo_defconfig
[Nexus 7 (2013) Original Android Development] Luigi_2:
Yeah, i mean i usually dont change my wifi or turn it on and off often so I dont have problem with it, but I faced it once when I cant turn it off and had to reboot.
[Nexus 7 (2013) Original Android Development] tiny4579:
Yep, that's the issue that I'm trying to fix. I am able to force it back on without a reboot when it crashes (highlighted wifi icon), but I usually reboot to reset WiFi to connect efficiently.

I'm checking with cyanogen_flo_defconfig to see if things improve. I only went with flo_defconfig as that is what it says in device/asus/flo for CM.
[Nexus 7 (2013) Original Android Development] tiny4579:
Still having issues with WiFi not waking up after the device sleeps for a while. It's not an issue on CM's kernel which this is based off of so I don't know what's going on.
[Nexus 7 (2013) Original Android Development] tiny4579:
Due to the lack of time to work on it and the ever changing CAF base of this kernel I have decided to close this project for now. The troubles with WiFi sleep and other tweaks I've tried to make to it aren't worth the debugging as they didn't exist on the AOSP base I originally had. It's a shame CM had to complicate a working kernel base.
[Nexus 4 Q&A, Help & Troubleshooting] jonze5:
Hey XDA!,

So today i dropped my phone in a little bit of rain.. it didnt shatter. or anything.. physically not even a ding (i am surprised too) but after when i tried to make a call i couldnt hear a thing unless i put it on speaker or use headphone. Im not sure the other person can hear me either.

I got this phone as gift. So when i called google they want the email adress of that person which i dont have and been trying to contact that person.. no luck. so called lg and they will chrge me.

Any ideas??

EDIT : just tried to call using viber. and earpiece works. Not when on a regular call tho
[Nexus 4 Q&A, Help & Troubleshooting] filthykid:
Try restarting the phone
[Nexus 4 Q&A, Help & Troubleshooting] jonze5:
that was done obviously . and no results
[Samsung Galaxy S 4 Zoom] zamgiobarmovie:
how about this?:fingers-crossed:
[Samsung Galaxy S 4 Zoom] gavinfabl:
Try a panoramic photo please. My S4 Zoom produces rubbish quality. File size is around 170-300kb. It should be 20mb plus.
[Samsung Galaxy S 4 Zoom] Jonny:
Closed, please use this thread >>> http://xdaforums.com/showthread.php?t=2379199
[Sony Xperia Miro, Tipo (Dual), J, E] ivan290:
Is there any rom like aosp?

Sorry for my english

I want a aosp like rom

or only stock phone.apk and contacts.apk compatible with tipo in ICS
[Galaxy S II Q&A, Help & Troubleshooting] alexisdub21:
Im stucked on download mode ... Been looking for a stock claro pr rom for daaaaaaaays anc cant flash nothing .... Or atleast any rom so i can get back and restore my nandroid backup i have pleeeeeeaase help

i9100uhlpg

SOLVED BY ODIN

http://xdaforums.com/attachment.php?attachmentid=2082246&d=1372641561

ALL THANKS TO

immortalneo

http://xdaforums.com/member.php?u=3556242
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
You have an I9100 right? Why not download any stock firmware from www.sammobile.com and flash via odin?

What error do u get when flashing?

"To err is human, to forgive is divine."

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] alexisdub21:
i did..

i did but its stuck at settup connection... ive tryed maaaaaaaany stocks but gives me red error

plz help

idk if this is useful but my baseband version was Uhlpg and i was from stock 4.0.3 claro pr

THANKS FOR REPY!!

and i have noo recovery option...