yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] dasmanul:
If you have fastboot set up, you can unlock your bootloader with "fastboot oem unlock", reboot your device once, then boot into the latest TWRP recovery via "fastboot boot <IMG file name>". Once in TWRP select "Backup" and be sure "Boot" is selected on the backup screen.
[Nexus 7 (2013) General] xdacinq:
But TWRP 2.6.1.0 is not available yet for N7 LTE. And 2.6.0.0 may result in multi touch issue. I will try Wug's Nexus Root Kit instead.

Will i be asked if i want to update via OTA or do i get them without influence by myself?
[Nexus 7 (2013) General] jak3z:
You are not flashing TWRP with that command, you are booting an image just for 1 time, so it's temporary.

fasboot flash xxx xxx.img > flashes an image permanently

fasboot boot xxx xxx.img > boots with that image for once
[Nexus 7 (2013) General] xdacinq:
ok, understood.

[MENTION=3289998]TheManii[/MENTION] do you need the files from my version?
[Nexus 7 (2013) General] TheManii:
03.05 is the same as flo on JWR66N, because of that I already have a good copy of it.

If there's enough interest I could pack it into a custom recovery flashable update zip.
[Nexus 7 (2013) General] dasmanul:
Careful, though! If I read this thread correctly, booting an image even just once can affect your touchscreen firmware. However, the same thread could also offer a remedy if you actually experience problems.

For the record: I have TWRP 2.6.0.0 flashed on my LTE model and haven't experienced any multitouch issues. I have, however, probably never tried to use more than 2 fingers at once.
[Nexus 7 (2013) General] xdacinq:
So would you recommend to install the OTA?
[Nexus 7 (2013) General] dasmanul:
In case you're asking me: I don't feel I have had the device long enough to give any recommendations. All I can say is that mine came with JSS15J out of the box and I haven't had any issues. I've unlocked my bootloader, rooted the device in order to install XPosed and XPrivacy and flashed TWRP 2.6.0.0. I haven't received any OTA updates yet.
[Nexus 7 (2013) General] sfhub:
You read correctly.

This post has a more detailed explanation of what is going on:

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

TWRP 2.6.0.0 = JSS15J touchscreen firmware

TWRP 2.6.1.0 = JSS15Q touchscreen firmware

This has nothing to do with whether you boot into it temporarily vs flashing it on your tablet. As long as you run ANY kernel (including the kernels bundled into TWRP/CWM/etc.) it will try to upgrade your firmware if the one in the kernel is newer, and then that is the firmware your tablet uses until a newer one comes along. Going back to your old kernel/ROM will NOT restore your older touchscreen firmware but there are solutions for that now.
[Nexus 7 (2013) General] ptau:
There is now JLS36C, that may fix that.

JSS15J:

[ 2.481475] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa038

[ 2.483581] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x007e

[ 2.485656] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00d2

[ 2.487670] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029

[ 2.489746] [ektf3k]:[elan] __fw_packet_handler: boot code id: 0x6047

JLS36C upgrade:

[ 16.772674] [ektf3k]:[ELAN] Start HW reset!

[ 17.275085] [ektf3k]:[elan] firmware_update_header: hello packet 55:55:55:55

[ 17.277191] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xa042

[ 17.279266] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x007e

[ 17.281280] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00d2

[ 17.283355] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029

[ 17.285369] [ektf3k]:[elan] __fw_packet_handler: boot code id: 0x6047

[ 17.285552] [ektf3k]:Finish the touch firmware update!
[Nexus 7 (2013) General] dasmanul:
Just thought of that yesterday: I did a nandroid backup of my N7 before ever fully booting into the OS and thus have an image of the original bootloader. Is there any way to get the version number from that? I guess I could boot it via fastboot, but the info should also be in the file somewhere, shouldn't it?
[Nexus 7 (2013) General] sfhub:
Same version as JSS15Q. I think this is just LTE's version of JSS15Q.

I imagine you'll have the same experience as everyone on JSS15Q for wifi.

Basically for some people it will be great. For others no change. For the unlucky it makes the tablet unusable with sticky buttons and dead spots.

People on WiFi Nexus 7 were so looking forward to A042 and initial results looked promising, but over time more and more people started having issues.

BTW would you mind sending me your kernel version (the full text) from about tablet?
[Nexus 7 (2013) General] ptau:
If you insist, you could just compare the old with the new one, but It's highly unlikely, that google ever updates the bootloader:

(Update: Well, I was wrong ;)

Hardware: QCT APQ8064 DEB

OS: JSR78D

Bootloader: FLO-03.05

Radio: DEB-F00_1.17.0_0607

Kernel Version: Linux version 3.4.0-g1f57c39 (android-build@vpbs1.mtv.corp.google.com) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jun 13 16:35:05 PDT 2013

OS: JSS15J

Bootloader: FLO-03.14

Radio: DEB-G00_1.23.0_0720

Kernel Version: Linux version 3.4.0-g365a6e0 (android-build@vpbs1.mtv.corp.google.com) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Thu Jul 18 17:10:40 PDT 2013

OS: JLS36C

Bootloader: FLO-03.14

Radio: DEB-G00_2.25.1_0802

Kernel Version: Linux version 3.4.0-g6537a16 (android-build@vpbs1.mtv.corp.google.com) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Aug 14 11:00:30 PDT 2013
[Nexus 7 (2013) General] jak3z:
Got my Device delivered, same bootloader as all the people here, FLO-03.14, rev_e, product name deb.

Guess all 4G versions got sent with this bootloader... or renamed maybe?
[Nexus 7 (2013) General] sfhub:
Ok, the JLS36C kernel for lte is exactly the same as the JSS15Q kernel for wifi.

I verified the source used for the build is exactly the same.

Also, not as definitive as looking at the source, but the build time is exactly the same also. At first I thought maybe the kernel is built with different options, but I think the build time points at the kernels being the same.

I'm talking about the kernel only. The ROM likely has differences but probably shares a lot. The GPS update in JLS36C is exactly the same as the JSS15Q update, byte for byte.
[Nexus 7 (2013) General] ptau:
Looks like I am the lucky one.

I had the exact same troubles with sticky buttons and dead spots before, now everything seems to work as expected (knock, knock, knock).

(Note: I saw that TWRP recovery messes with the hardware, so I never ran it.)
[Nexus 7 (2013) General] sfhub:
It isn't that TWRP is purposely messing with the hardware.

It is that the bundled kernel is upgrading the touchscreen firmware underneath the hoods.
[Nexus 7 (2013) General] ptau:
A "recovery" kernel definitely shouldn't do any persistent firmware upgrade.
[Nexus 7 (2013) General] sfhub:
Philosophically, I agree (at least for 99% of the situations, the 1% being when you touchscreen is screwed and you can't boot).

Just telling you what is happening in reality.
[Nexus 7 (2013) General] ptau:
I believe, then there should be a knob for that 1% (holding a vol+ key or something). Writing a wrong data to some eeprom sounds like a very bad idea for me. The user-space drivers could afterwards smash a calibration data, ..., I don't know.

What ever, I'm scared enough to break my new baby. I don't like the enormous complexity of the TWRP source code either. I'm about to build a simple, old style recovery with just USB + root adbd enabled. If someone else were interested, let me know :highfive:
[Nexus 7 (2013) General] ptau:
I see, you are right. The kernel sha1 matches the AOSP source branch here:

https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-jb-mr2

Unfortunately there isn't update for the JLS36C user space.

I still hope someone will continue Queru's work. Merging different builds together is no fun.

https://android.googlesource.com/device/asus/deb/

The touch fw fixes since A038 are:

TouchScreen: update touch firmware to A042.

Fix/Improve issue:

1.ghost touch probelm that caused by lcm slef-noise.

2.broken line in particular area.

TouchScreen: update touch firmware to A040.

Fix/Improve issue:

1.[Issue 9692415] Touch screen on flo is broken for games.

2.Broken line.

3.Two Fingers Tapping Easy Connectivity.

4.co-axis problem with two finger.

TouchScreen: Add 20ms delay after hw-reset to enter iap update mode.

to avoid unexpected retry command in firmware update mechanism.

[9867254]Need to wait for 20 ms before starting communicate with touch IC for

boot-code initialization after the hw reset.
[Nexus 4 General] peteyboy24:
Hi everyone

just wondering what rom everyone is using and any suggestions of what rom i should pick, on stock at the moment but rooted and TWRP installed but cant decided what rom

any suggestions would be greatly appreciated

thanks in advance
[Nexus 4 General] Dark Emotion:
Dude... http://xdaforums.com/showthread.php?t=2136677
[Sony Xperia T, TL, TX, V] Arioman:
hi

i sale my Arcs Phone for having problem with Wifi ( wep or wap password ) and Weak Connection , low speed and keep dropping

now i want to buy Xperia T , some people say that it fixed in new Roms , but i want to be sure

is that True ??

some other people say this problem came from Android and no matter which brand

if not , maybe i choose HTC or other Brand
[Sony Xperia T, TL, TX, V] BigD18t:
Never had an issue with my T, Wifi is fine.
[Sony Xperia T, TL, TX, V] Arioman:
good to hear this but try to seach " Xperia T Wifi keep Dropping " in google and see what comes
[Sony Xperia T, TL, TX, V] Supersonic335:
wifi is bad in Xperia T in comparison with other phones..4 years old nokia have better signal reception:D
[Sony Xperia T, TL, TX, V] AndroidHoneyComb:
I'm pretty sure your 4 year old Nokia does do badder reception
[Sony Xperia T, TL, TX, V] mr_torture:
I'm coming from Arc S too, and while I never had such a big issues with Arc S Wi-Fi (on stock GingerBread), I can say that Wi-Fi reception on T is both, more stable, and with stronger signal.

Xperia Arc/S problems with signal are mostly related to bad ICS update, because on GB it was much better.

Regarding Google search, you know, nowadays people are searching for all kind of things, for reason and for no reason, and Google is remembering all that.

So basically, whatever nonesense you enter into Google search, you will most likely get some results, less or more relevant.
[Sony Xperia T, TL, TX, V] gregbradley:
Mine is fine...
[Sony Xperia T, TL, TX, V] Supersonic335:
Xperia T could have much better wifi reception if Sony want...HW is ok but SW is killing its potencial

I have problems since I bought it,keep dropping connection(every 2 minutes reconnect )

ON Cyanogenmod theres no such issues,on TX firmware no problem too + wifi range 2x better than with stock T Firmware

Check this,its definetly not HW problem..

http://xdaforums.com/showthread.php?t=2335379
[Sony Xperia T, TL, TX, V] nreuge:
I confirm that there are some issues : http://xdaforums.com/showthread.php?t=2245462&highlight=wifi+unstable

(it was my first thread on XDA :o)
[Sony Xperia T, TL, TX, V] Pollie81:
Agree, WiFi on Xperia is good except the range.. It sucks! My old LG optimus black was far better..

Verstuurd van mijn LT30p met Tapatalk
[Sony Xperia T, TL, TX, V] peter-k:
That is it. And this is why Google search will become irrelevant, sooner than we might believe.

From "XYZ has the best Wifi ever" to "XYZ's wifi reception is worst" ........ I assume that everything is all right.

Wifi reception in Singapore is sometimes difficult, bcs of the tight space, 20 or more Wifi transmitters locally, and so on. Also I believe in some cases there is a certain intention, since people shall be more encouraged using (pay) data connections.
[Sony Xperia T, TL, TX, V] ironwick:
I have same issue. Wifi signal is very poor in my Xperia T and it loses the connection all the time. I compared the Wifi reception with an Alcatel One Touch Idol and it was 2xbetter in same point. I think it has to be a SW problem, as the HW is the same than other devices and it works fine.
[Verizon Samsung Galaxy S 4] waderedsox:
i am aware that this question has been posed in slightly different form before, but it has not been addressed to this specific situation, i have a 4.3 rom and i would like to be able to use the stock s4 keyboard, does anyone else know how to get this working?, i have tried to just extract the apk, but it wont install, any ideas?
[Moto X Q&A] butters72:
I currently have the Droid Razr M and if I ever try to take a video of a concert or other loud environment the audio is always atrocious. I am hoping that the X has decent quality audio recording.

My Razr currently sounds like the S3 in this video:

http://www.youtube.com/watch?v=SaL87kEqZ4Y

Can someone upload a video they've taken with the X at a concert? Or even just crank up the volume of some music on your home theater (with bass) and see how it performs.

I am hoping that the X can approach the One!
[JAM, MDA Compact, S100 General] thormdac:
:evil:

Hi everyone,

am deperately needing your advice!!!

Just yesterday I rechieved an exchange mdac from tmobile showing serial version v1.02 when put in bootloader mode(previously v1.01).

When trying to flash whatever rom once transferred via ntrw to my sd card, my mdac does simply nothing but stay in bootloader showing serial v1.02. No flashing like in my old one starts.

On removing the sd card it comes out freshly formatted, before it definately was formatted with raw as usual once working with ntrw.

Result : I can not upgrade my system to mksbigstorage or any other rom like i could with my" old one". (same sd card!!!)

Tried downgrading to an older rom version via original upgrade routine and from there flashing via sd card: same problem!, tried other sd card: no solution either!

Any ideas, solutions, people with the same problems?

:?:

Appreciate your help

Thanx
[JAM, MDA Compact, S100 General] thormdac:
romflashing

Seems to have nothing to do with flashing routine.

Card simply gets formatted once inserted.

Any way to stop this?
[JAM, MDA Compact, S100 General] gguyaz:
Hi! I have had many problems after flashing and re-flashing my rom.

Try boot loader mode and USB then execute (from your PC)MaupgradeUT_noid with a Shipped_rom on XDA ftp. It may work.

Have a look at this link: http://www.mtekk.com.au/forums/viewtopic.php?p=32876

Regards
[JAM, MDA Compact, S100 General] shamus:
Try to write SD card with winhex not ntrw. Simply choose open disc feature and write file directly do SD it works every time for me (with ntrw it was roulette). I have 1.02 bootloader :)
[JAM, MDA Compact, S100 General] gguyaz:
Thanks Shamus but can you explain in details how do you do this with Winhex? my bootloader is 1.00

SPV_M500, ROM 1.12.02 FRE

RADIO 1.12.10

EXTRom no more
[HTC Butterfly] Bassie39:
Does anyone has the stock recovery of een x920e europe
[HTC Butterfly] An69:
Welcome,stock recovery x920e europe 4.1.1

https://docs.google.com/file/d/0B3A01FFPvvH1amRpQjc4VE83Q2c/edit
[HTC Butterfly] Bassie39:
how to go back to stock completely tried to lock the bootloader and run ruu.zip from the HTC dev site but doesn't work. Also tried backup from phone in twrp and fails to. Still on Virtuous Rom but want to try the ota 4.2.2 for x920e.
[LG Optimus Black] sarry86:
Hi guys, yesterday i downloaded a software called Palm Reader from the market, played with it a little then i left my phone switched on as i always do till morning, today when i woke up i took it and found it has already switched itself off! i tried to switch it on, tried switching on while holding the G button but nothing just stuck on lg logo, i decided to reflash it using r&d tool but it still stuck on lg logo, tried even with smartflash, all ICS V30XX doesn't work anymore :( only V20T work but the phone laggy i never seen the slow phone like this before! when it goes to deep sleep it ain't come back to normal till i remove the battery and insert it again and power it again where it takes like 7-8 minutes to come to standby screen, can somebody tell me what to do to revive my phone back to the normal ICS V30I or V30J??
[Sony Xperia S, Acro S, Ion] Yakandu:
Well, as said in the title, here you have it (It does not contain any Kernel and it doesn't wipe data):

I deleted branded apps (customization) from the system, its as clean as the World generic and it wont show the roaming R.

Original FTF: (Thanks to [MENTION=5093470]ska67[/MENTION]) http://xdaforums.com/showthread.php?t=2423025

ROM: http://dfiles.eu/files/wo3rkrtji

- Flash Doomlords .96 stock kernel

- Flash the ROM with CMW

- (Wipe data if coming from AOSP based ROM)

(use google to find how to download fast and free from depositfiles) :D

Try it and say me if it works (it should)
[Sony Xperia S, Acro S, Ion] luaifarah:
gonna try it now! :)
[Sony Xperia S, Acro S, Ion] r0bot:
Just flashed the ROM on my SL, everything is working fine. Thanks for this nice contribution!
[Sony Xperia S, Acro S, Ion] huzi7868:
is this for xperia s too because title says xperia sl
[Sony Xperia S, Acro S, Ion] Redstarr1:
SL = SL and S = S. How about looking on the second page? http://xdaforums.com/showthread.php?t=2417655

Anyway, I bet you could put this on XS without issues (it doesn't contain a kernel) but why bother, the XS version is almost identical and has been available longer.
[Sony Xperia S, Acro S, Ion] mekels:
Im on a Locked Bootloader

I have .96 Stock Firmware And Kernel Already. rooted, Installed busybox , installed CWM.

If I install this via CWM recovery. Will I lose CWM? Will I need to Flash .96 Stock Kernel Again?

I can't flash kernel Using flashtool cuz i Have my USB connectivity not working. or damaged trim area
[Sony Xperia S, Acro S, Ion] Ahyricks:
Yup you will lose your cwm but can reinstall that's wat happened to me and now all good
[LG Optimus L9 P760, P765, P768, P769] zanakorus33:
Hi all, wanted to say bye to all of u guys thanks for almost a year of fun with community and lg l9.

Its a great phone but i leaks few things that i found in old samsung galaxy s2.

I remember when we were starting l9 things on this forum in a threat.

Long way, now we have custom kernels , roms.

Sad for me, but i sold my l9. Have fun with it.

Btw for all wating for 4.3 official , they will first release l9 II. Bye guys.

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[LG Optimus L9 P760, P765, P768, P769] luq529:
Bye, I think 4.3 or 4.2 will be for 2/3 months. Or never :P
[Android Apps and Games] Androidman994:
I cannot find the Stock Market Simulator Plus full apk. All the links are dead. Can someone post a link for it?
[Android Apps and Games] Archer:
No requests for paid apps are allowed. Also, please post questions in Q&A forums.

Thread closed.
[Ouya General] Hogman500:
I've been working on tweaking the stock ouya kernel but as I'm new to this I'm having trouble figuring out which config to start working with I tried the one pulled from /proc/config.gz but, it produces a missing file error specifically mach/iomap.h. after that I tried Tegra3_android_defconfig which compiled then repackaged produces nothing but, a black screen. Not sure exactly what I'm doing wrong but any help will be greatly appreciated.
[Ouya General] gianptune:
Do a git pull to grab the kernel source again. I was able to build it like you described.

checkout source code

pull /proc/config.gz and extract it to ouya_defconfig

make ouya_defconfig

make
[Ouya General] Hogman500:
Thanks I must have had a corrupted download our something of the sort because that did it I can now compile a functioning kernel.
[Ouya General] Hogman500:
I'm now wondering if anyone has any experience with overclocking I know which lines to edit from looking at code from other tegra 3

Devices but am having trouble figuring out this line.

{ 12000000, 1700000000, 6, 1, 8}

I know the first number is the same for each grouping and the second is the frequency you are trying to add but the last three numbers I'm not sure what they are. Such as if I want to add.

{ 12000000, 1800000000, ?, ?, ?}

And I know there are 5 sets of these lines per clock frequency just didn't want to type them all out.
[Ouya General] nchantmnt:
I'm at work right now, so I.m just quoting a different thread atm:

Maybe i get some time to have a closer look.

Source:

http://xdaforums.com/showpost.php?p=26288492&postcount=2 thx @ guevor
[Ouya General] Hogman500:
Thank you for the link it's hard to look for info on kernel tweaking because, when you search for it all you come up with are hundreds of kernels for assorted devices. I figured out the Tegra3_clocks.c and am working on the voltages now.
[Ouya General] nchantmnt:
hmm just study commits for other tegra3 kernels. there sould be some around ;)

I'm atm trying to get sio, gpu-oc and some random "Cleanups" running on my kernel. most of this is just copy and paste from other kernels.
[Ouya General] Hogman500:
That's mostly what I've been doing but so far even though I have all the changes in your link and another kernel commit I've seen the frequency I try to add still does not show up.
[Ouya General] nchantmnt:
So how is everybody doing in kernel-development?

I am building one myself and should be ready to go into closed beta the next days. Anyone interested?

Don't expect anything fancy just yet but we are surely making progress.

So if some of you are willing to test and not afraid of bricking their device, just hit me up via pm.

Gesendet von meinem HTC One X+ mit Tapatalk 2
[Ouya General] Asadullah:
I'm not i have my private messages turned off but when your ready ill turn em back on
[Ouya General] Feche:
I am facing the same issue, I don't understand how to add new frequencies.. anyone got sorted it out?
[Ouya General] blackstripe:
I'm compiling the stock kernel right now with the intention of adding CIFS support as I'd like to be able to access ROMs on a samba server. When running 'make menuconfig' I see that I can check mark the CIFs option, but I'm not sure if I need any additional files to make this work? Anyone have any info on adding cifs?
[Ouya General] nchantmnt:
Should be enough. But why not just use precompiled kernel module which is already available?

Gesendet von meinem HTC One X+ mit Tapatalk
[One (M7) Q&A, Help & Troubleshooting] mrb1ue:
I'm running CyanogenMod 10.2 nightlies on my Sprint HTC One and was having issues with the proximity sensor while making phone calls in the recent build. I found the following post by codeworkx:

http://xdaforums.com/showthread.php?p=45010774&nocache=1

I was able to find the minimum value that would work with my phone:

"0x0 0xFFFF2201"

I don't have 10 or more posts in order to respond directly in that thread otherwise I would. But I'm hoping that the finding of a working value for my Sprint HTC One might help other Sprint users having the same issue.
[One (M7) Q&A, Help & Troubleshooting] felipey:
I was having the same problem but didn't want to edit the code and found that by disabling the "Volume button wake" fixed it.
[One (M7) Q&A, Help & Troubleshooting] mrb1ue:
Huh, my "Volume button wake" was never enabled.

And now I'm not sure the value I tried was high enough. I just made a few calls and the screen still turns off and stays off during the call. I'm trying a higher value now, 0xFFFF2400, and see how that goes.
[One (M7) Q&A, Help & Troubleshooting] dotpage:
Having the same issue here... did you find a fix yet?
[One (M7) Q&A, Help & Troubleshooting] mrb1ue:
I updated to the latest nightly which fixed the issue for me (except 09/06 & 09/07 as they are broken).
[Galaxy Note II Q&A, Help & Troubleshooting] pemell:
As the title asks, should I upgrade from xxdmc3 to xxdmg1? Which advantages can I expect?
[Galaxy Note II Q&A, Help & Troubleshooting] thedadio:
Im sticking with dmc3. Outstanding battery life
[Galaxy Note II Q&A, Help & Troubleshooting] hoaxdream:
Stick with dmc3
[Galaxy Note II Q&A, Help & Troubleshooting] pemell:
As no one is trying to convince me otherwise I'll guess I'm staying put. :cool: