yashsingh1/xdaforums huggingface dataset:
[Shield Q&A] nielo360:
Gangstar vegas works with touchscreen + high graphics mod from xda :D plays awsome

Im going to try mapping keys to it.
[General Questions and Answers] old-man48:
Hi Sir,

Maybe it sounds stupid, so forgive me.

I just downloaded 4 SGS3 rom's ( V4, till V5 updated from Mr. Sniper)

I know I'v to wipe data, cache and dalvik, I know to install from stock rom, but....

Should this be done everytime when I update a new version of this Rom ?

Or only the first time ans then update, update etc,.

Maybe not the right place to ask, forgive me, I'm a newbie, I'm from the Netherlands.

I have read the threat, but didn't see, couldn't find an answer.

If I have to do, I;; do, but if it isn't needed, would be better.

Hope you can help me ( hope this is the right place to ask).

Thnx for the excellent work on this Forum. It was very helpfull many times !!!

Greetz to you all, hope my English isn't too bad.

Old_man
[Nexus 4 Q&A, Help & Troubleshooting] prash97:
Anybody seen the new motorola x phone's touchless google now feature??

can it be ported to the nexus 4??

please devs try to port it when phones come out..

i am sure many people would want it.:D:p

Thanks!
[Nexus 4 Q&A, Help & Troubleshooting] trol0lo:
The moto x uses an extra CPU for that feature so it either wont be possible or very battery and hardware hungry.
[Nexus 4 Q&A, Help & Troubleshooting] Mikeonic:
Tasker plus voice commands
[Nexus 4 Q&A, Help & Troubleshooting] Ace42:
Yep it's a specialized DSP-core that's NOT ARM based.
[Nexus 4 Q&A, Help & Troubleshooting] prash97:
So does that mean it woudnt be ported...

Or it would be ported but would drain the battery life?
[Nexus 4 Q&A, Help & Troubleshooting] prash97:
Sir, would it drain battery life?
[Nexus 4 Q&A, Help & Troubleshooting] CoolApps:
Yep, pretty badly.
[Nexus 4 Q&A, Help & Troubleshooting] Ace42:
It will likely be ported, but according to the Moto article it specifically stated this special DSP allows them to have such great battery. The Nexus has a DSP, however the X has two new DSPs from Moto(as part of the "octo X8").
[Nexus 4 Q&A, Help & Troubleshooting] Lord Hades:
Two of the promoted features of the Moto X are Active Display and Always-on google now. To answer your question directly, yes they will be ported. But, will it be practical to use in everyday life? Probably not. This is because of the battery drain that these would have. Both these feature have some specialized hardware support (different screen, special CPU cores etc) for these functions and are kind of the main selling points of the device. So, it is unlikely that we're going to see this in full force on our Nexus devices.
[Nexus 4 Q&A, Help & Troubleshooting] prash97:
Thanks for the information!!
[Samsung Galaxy Mega] Ten Quid:
Hey guys,

Are there any Galaxy Mega users going back to the Note 2? I went back after using the Mega 6.3 for around 2 weeks and I gotta tell ya, I'm happy I went back.

The Mega feels so slow and laggy, I'm constantly finding myself having to clear the RAM and close all tasks just to speed things up.

Swiping left to right always have a slight lag, opening the app draw has lag, heck even returning via home button is laggy. Exiting Apps like the browser seems to drop the animation of exiting it down to like 20fps.

Everything just feels like it stutters and lags, the phone feels like it's constantly crawling and the "pinch-in" lag is back too.

Don't get me wrong I love this phone, mostly for it size but in no way is it a bad phone. But I am slightly disappointed a phone with a processor that has similar instructions A15 isn't 100% smooth.

I've seen alot of you guy say you have a buttery smooth Mega, I wish my was the same, but it's far from buttery.

All in all, I'm happy I went back to the Galaxy Note 2, it feels so much faster and smoother.

just my few pennies.

P.S - Forgot my username and email address so had to make a new acount, doh!
[Samsung Galaxy Mega] inurb:
I hear you. The only slowness I am experiencing is the android notification bar. But its getting progressively worse. I disabled all animations and it sped the notification for a little but but now it's slow again. The device is very snappy but the ridiculously slow notification bar swipe is unacceptable. I am waiting for the Note 3 now......

sorry to hear you are having poor performance. Again I've only experienced iit when swyping down on the notification bar.
[Samsung Galaxy Mega] numbnutsuk:
Hmmm I've been playing with my mega a week. I should of put that better ha .

It is a bit laggy n jerky now and again. But for £300 I'm really impressed and it exceeds my needs. Especially with screen size, design and how slim it is.

I'm selling my note 2 on eBay. And staying with the mega 6.3.
[Samsung Galaxy Mega] Titanicology:
I'm positive that a software update will fix the lags. I feel like Samsung rushed the software for the Mega 6.3 that's why it's not that optimized for the processor.
[Samsung Galaxy Mega] jtrakx:
I own both Note II and Mega 6.3 I9205. The slowdown you mentioned has got something to do with samsung launcher and the rom itself. Update

the ROM to the latest version available. I think that was XXUAMG4 or better yet download the customized one available in this forum (android development). The mega launcher was entirely different from GS4 and Note2. It support landscape mode and the built-in widget resizes accordingly.

I think this was taken from touchwiz tablets. Try to use Nova Launcher instead, then see if you still experience noticeable slowdowns. My mega 6.3 is butter-smooth with Nova launcher. I have never experienced any slowdowns at all, and will never go back to samsung's laggy default laucher. Also try to enable "Force GPU rendering" in the Developer's Section settings. Do not under-estimate power of Snapdragon 400 vs Exynos 4212. It's a hell lot faster in FPU. In fact in most benchmark, its faster than note 2 specially the graphics department. I confirmed this using the latest 3DMark. Dual-core vs quad-core does not make sense anymore. The CPU architecture is what really matters.

Also, the 1.5GB ram is more than enough for daily tablet/phone use. That includes gaming. My Nexus 7 is very fast running JB 4.3 with only 1GB of ram. My Windows 7 Pro netbook, which am using right now, only comes with 1GB of ram but still perform quite decently in multitasking considering that Windows 7 has got more bloatwares in it that Android JB and IOS combined.
[Samsung Galaxy Mega] gx3k:
I also use Nova Launcher and never had any slowdowns. I find my Mega smoother than my Nexus 7 and my original Note on custom ROM.
[Samsung Galaxy Mega] Ten Quid:
Thanks, I'll have to update it then because right now, whether it's the launcher or ROM it's ruining the experience.

I tried Nova Launcher and it was equally as bad if not worse the Touchwiz, it was still jerky and laggy.

And I agree, the benchmarks for the Snapdragon 400 are great and beat the Exynos 4 alot, but for me personally at the moment in terms of everyday use the Note 2's performance is so much better and smooth. I'd really like to keep the Mega, but unless the performance improves dramatically within a new update then I'll be keeping the Note 2. I'll try a custom ROM and the latest update, fingers crossed.
[Samsung Galaxy Mega] inurb:
I experienced the slow notification bar and I was running ADW launcher. I disabled animations and it still was slow. I returned my Mega because of this. It was a total deal breaker.
[Samsung Galaxy Mega] Warnahly:
Yes your right it lags sometimes

But thats why I am waiting CM team hopefully or anyone to build AOKP or CM or AOSP

When it reaches the mega it will be awesome :D
[Samsung Galaxy Mega] SquirtingCherry:
I have been thinking about going back, but i think i'm gonna sit it out till the Note III gets released.

The Mega has it's slow points now but i trust in samsung fixing some in the upcomming updates.
[Samsung Galaxy Mega] kipue:
And maybe CM coming over on the big screen ^^
[Samsung Galaxy Mega] jtrakx:
I don't know exactly why some mega 6.3 owners experienced some significant slowdowns.

Maybe because of the ff:

1. Outdated ROM. Try to install the latest available rom even if its not for your country (XXUAMG4).

2. Stock launcher from samsung. Use Nova launcher or any other payware launcher of your choice.

3. Use Seeder program. I may help speed things up.

4. Flash stock kernel after rooting and stop using vcore2 kernel

5. You may have a faulty slow microSD.

6. Some other apps you have installed maybe affecting your otherwise speedy JB 4.2.2
[Networking] blackest_knight:
ok here's the problem

you want to connect to a wired network or even simply a single pc connecting to the net on a broadband or dialup connection.

if there was a wireless router then it wouldnt be a problem. your pda would connect to the wireless network and the wireless router would give your pda an address and everything would work.

without the wireless router you don't get allocated an ip address.

well problem solved www.nat32.com has a program called nat32e which you can get a demo version of (works for an hour before needing to be restarted)

essentially this is a nat router which runs on any pc running windows

you need a wireless card in addition to its ethernet connection to the net.

I did this with 2 wireless cards so in theory it could be used to extend the effective range of an existing wireless network too

installation is simple but basically you give the wireless card i used a belkin usb 54g dongle type on channel 6 a fixed address and tell it to connect to an adhoc network called "whatever"

you add a network packet driver, nat32 holds your hand installing this,

then the pc needs a reboot.

first time you run nat32 it runs through the configuration you tell it what card connects to the internet and which card connects to your private net

(that is your adhoc wireless network) it sets things up

scan for a network on your pda tell it to look for adhoc networks connect to "whatever" and tell it when it asks, it connects to work.

you should then have wireless access to the net.

if your doing this with two wireless cards make sure you have seperate channels set up for your infrastructure network and your adhoc network.

the belkin 54g usb wireless dongle costs about 25 from staples or 30 from pc world (both are local for me)

the host pc will run fine without any problems with nat32 running or not

no proxys need configuring a registered verion of nat32 costs from

$25 but this gets you registered for just one pc and really you want it so you can roam with a usb wireless card in your pocket and your pda.

I think adhoc wireless networking works for up to 30 wireless points.

i did it with a pda, mdaIII and a laptop.

basically like ics but with less problems

I think you can do this with bluetooth as well but that really isn't fun

hope this is useful sorry its so rough but i have to get to work
[Networking] Astro1:
Think you may be on the trail of a problem that I am stuck on at the moment . I have the XDA11i and want to connect it via blue tooth to a blue tooth modem connected in turn to to a BT wall socket ( in that way I can surf for 1p per min !!!) no matter what I seem to do whilst the PDA will recognise the Modem as a serial modem ( and form a secure link ) it wont talk to it and get it to dial up . Zoom ( Hayes ) are wondering if 02 have disabled the element in blue tooth that lets this work ? Any thoughts . with the above I dont need to lug my lap top round with me .

Regards

Astro1

London England
[Nexus 4 Android Development] itlnstln:
Here is a ROM I pieced together that includes:

GApps from the OTA including Phone.apk with Autocomplete

Build.prop tweaks for Wallet and OTA sound defaults

OTA Ringtones, Alarms, Notifications, etc.

Bluetooth audio improvements based on http://xdaforums.com/showthread.php?t=2386032 (328 version)

Removed VoiceDialer.apk, Gallery2.apk, LatinIME.apk (AOSP), Quicksearch.apk, Music.apk, and Calendar.apk. Added OTA Gallery, OTA Play Music, OTA Calendar.apk and Google Keyboard from OTA (also called LatinIME.apk)

Bluetooth works fine on this build in my limited testing (paired headphones and listened to music)

WiFi Tweaks based on http://xdaforums.com/showthread.php?t=2300873. Only changes: gDataInactivityTimeout=200, gEnableApOBSSProt=1, gChannelBondingMode5GHz=1. For WiFi update only: http://xdaforums.com/showpost.php?p=44315789&postcount=16

Download - ItlnStln Version (use Holcomb227's version)

Download - Holcomb227 Version

See here for details on Holcomb227's version.

Download - All System App Version

Built from Holcomb227's version with all apps in /system/apps

Download - All System Apps + LTE

Built from Holcomb227's version with all apps in /system/apps and includes build.prop/apns.conf changes for LTE support

Feel free to mirror should you wish. Flash at your own risk.

Credits:

XupModz and Holcomb227 (fixes) for the base ROM build

cbaronne for the Bluetooth tweaks

kalo86 for the WiFi tweaks
[Nexus 4 Android Development] itlnstln:
I tested Bluetooth further in my car with no problems. Pairing, audio quality, and metadata all work properly.
[Nexus 4 Android Development] itlnstln:
Compatible Mods

Here are a couple of mods that are compatible with this ROM:

Quicksettings: http://xdaforums.com/showpost.php?p=44086678&postcount=738

4-Way Multi-Reboot (use the 4.3 Deodexed version for JSS15J): http://xdaforums.com/showthread.php?t=1771307

I use both of these on this ROM with no problems. For the quicksettings mod, you may have to mount System in recovery when flashing.
[Nexus 4 Android Development] wolf230:
I've always dreamed to do this: FIRST !

Thanks for your work
[Nexus 4 Android Development] itlnstln:
Thanks for checking it out; let me know what you think. I've been using the ROM since I've posted it and haven't run into anything.
[Nexus 4 Android Development] Necrodaemon:
Thanks, testing in my Nexus 4 , the rom looks interesting

Edit : Phone.apk force closed after a clean install with TWRP 2.6.0.0 :(
[Nexus 4 Android Development] itlnstln:
Did you try fixing permissions? What ROM are you coming from? I haven't had an FC at all. I wiped cache, Dalvik, data, and system before flashing. I use TWRP 2.6 as well.
[Nexus 4 Android Development] Necrodaemon:
Yes, Fix Permissions in TWRP, my previous rom was Stock/Deodexed JWR66V, Wipe Data/Cache and installed rom, Fix Permissions y reboot, but FC only in Phone.apk, install another rom from JSS15J and the problem does not happen , I will try with another recovery

Thanks
[Nexus 4 Android Development] itlnstln:
Did you wipe system? Try wiping system as well and let me know. I'm going to make a NANDroid real quick and try re-flashing from scratch and see what I come up with.

EDIT: I'm using TWRP 2.5 not 2.6. I was having problems with 2.6.

EDIT 2: Using TWRP 2.5, I wiped cache/Dalvik/data/system, flashed the ROM, fixed permissions, rebooted. No FC's. I'll re-upload the ROM to Drive.
[Nexus 4 Android Development] itlnstln:
I re-uploaded the ROM just in case.
[Nexus 4 Android Development] Necrodaemon:
New rom uploaded work with Philz Recovery 5.08.5, clean install : wipe data/cache, format /system ...

Thanks
[Nexus 4 Android Development] itlnstln:
Excellent. I hate random FCs. Thanks for checking out the ROM!
[Nexus 4 Android Development] Necrodaemon:
Yes, me too , i'm testing your work , look is stock and mods work
[Nexus 4 Android Development] itlnstln:
Genius, thanks! I prefer OTA's over straight AOSP as, IMO, there is a lot of "clean-up" work done to prep the build for the device, so that's what I was trying to achieve here. As far as I can tell, there isn't much difference between this ROM and the original OTA.

Thanks again for checking this out. My usage pattern is pretty simple, so I don't personally test every single thing in a ROM whether I compile it myself or tweak an existing build.
[Nexus 4 Android Development] itlnstln:
See OP for updated ROM with WiFi performance fixes. If you don't want to download and reflash the whole ROM, attached is the updated WCNSS_qcom_cfg.ini. Flash in recovery, reboot. Alternatively, grab the file out of the zip, push to system/etc/wifi, fix permissions, reboot.
[Nexus 4 Android Development] gpvecchi:
Voice dialer not working as in many AOSP ROMs...
[Nexus 4 Android Development] itlnstln:
Let me look into this a bit. I think I read somewhere Voice Dialer was depricated or something and replaced by Now. If that's the case, I'll just remove it from the build. I don't think the OTA has voice dialer.

EDIT: The OTA does not have Voice Dialer. I am going to remove it from the build and reupload.
[Nexus 4 Android Development] itlnstln:
ROM reuploaded with Voice Dialer removed.
[Nexus 4 Android Development] Holcomb227:
Hey itlnstln, I've been working on this rom you posted and managed to fix quite a few things.

Almost exactly like like google's 4.3 OTA except for these changes:

• Latest kernel JSS15J (deodexed) base with touchboost and backup sync fixed

• AOSP browser included

• Bluetooth bit rate (sound quality) increased

• WiFi Optimizations

• Newest Google apps fresh from the play store (let me know if they need updating)

• Removeable Google apps*:

• Chrome

• Youtube

• Google Earth

• Currents

• Wallet

• Google Plus

• Hangouts

• Play Books

• Play Magazines

• Play Music

• Play Games

• Play Movies/TV

• Hindi, Korean, and Pinyin keyboard

• Talkback (accessibility app)

Download

*Removeable Google apps will not be kept when resetting your phone from the settings menu.

-Updated: Slimmed zip by 50mb (unused libs) and added Google Play Services to /system
[Nexus 4 Android Development] itlnstln:
Awesome, man! Thanks! I'll put it in the OP. I'll play around with it tomorrow.
[Nexus 4 Android Development] Holcomb227:
Was that you who requested to be able to edit my uploaded file?
[Nexus 4 Android Development] itlnstln:
No, sir. Not me.
[Nexus 4 Android Development] b00bs:
Can you also removed Aosp browser in next build? Because I'm a purist :D
[Nexus 4 Android Development] Holcomb227:
I could give you a pure build if you want. I was thinking I should make a rom exactly like stock, with absolutely no modifications. That could be my build. itlnstln's build could have a few tweaks that most people believe are important, like stock browser, wifi/bluetooth optimizations, ect. I dont know, I need feedback on this.
[Nexus 4 Android Development] itlnstln:
That's fine by me.

My version is to get as close to an OTA as possible.
[Nexus 4 Android Development] Holcomb227:
So would you delete the stock AOSP browser? I really like it and OTA doesn't have it.
[Nexus 4 Android Development] Necrodaemon:
I try to download it from Google Doc to test your rom, but I asked about the file permissions

@ Ish, the updated rom works great, thanks again

Rodrigo A.
[Nexus 4 Android Development] itlnstln:
I don't, but that's probably the only visible deviation I make. The AOSP browser has a lot of utility.
[Nexus 4 Android Development] gpvecchi:
Holcomb227 & itlnstln, I suggest you to work together and provide two different ROMs in this thread: one JSS15J TOTALLY AOSP, and one JSS15J TOTALLY stock.

These are the two missing ones outside there...
[Nexus 4 Android Development] Gnome:
Yeah +1 to that, I really like the Pure AOSP build no GApps, just AOSP. And right, thats the only thing that is not out there in the development section. ;)

☆★ Click "Show Content" on my sig for my Guides and MODs. ☆★​
[Nexus 4 Android Development] itlnstln:
I'm checking out your build now, and I like it a lot better than mine - it's super clean. I'm uploading a copy to Drive with the WiFi and BT fixes (I don't know if you included the BT fixes or not), and I'll put it in the OP. If you want to start your own thread; that's cool, too. I'll just shut mine down if that's the case. Thanks!
[Nexus 4 Android Development] apatal:
How about the touchboost fixes? Might be a good idea to include that too, since your builds include the stock kernel. :)
[Nexus 4 Android Development] itlnstln:
Holcomb227 already had them incorporated:

EDIT: I know I sound like a total dumbass, but what is touchboost anyway? I tried Googling it, but all I found was a car turbo app.
[Nexus 4 Android Development] gpvecchi:
Oh, a changelog in first page would help, too...;)
[Nexus 4 Android Development] itlnstln:
Huh? That's basically the whole OP. I also want to see what Holcomb227 wants to do about his ROM thread-wise. This is basically his/her work, now, so if Holcomb wants to start a thread, I will defer to him/her on how to structure that.
[Nexus 4 Android Development] Gnome:
[MENTION=2910255]itlnstln[/MENTION] do you still have the base AOSP ROM? Yhe one w/o any mods? Where GApps restore works?

☆★ Click "Show Content" on my sig for my Guides and MODs. ☆★​
[Nexus 4 Android Development] itlnstln:
The OP has a link (in the credits) to the version I used which was base AOSP. This version does not contain any of the fixes (touchboost, restore) that Holcomb227 added. The version that Holcomb227 posted; however, is not a "raw" AOSP build, but an OTA-like build.
[Nexus 4 Android Development] Gnome:
Anyways, what was the fix for the restore? I'll just cherry pick that one out and push to the Stock AOSP, but if you have them, would it be possible for you to attach it? I'm planning to make this as a base. Thanks!

☆★ Click "Show Content" on my sig for my Guides and MODs. ☆★​
[Nexus 4 Android Development] itlnstln:
Unfortunately, I don't know. Holcomb227 knows how to work some magic. It usually involves replacing some lib files. I'm pretty busy at work, so I haven't had time to compare libs from the OTA vs AOSP to see which ones needed replacing or were just missing in the AOSP build.* The same goes for the touchboost fix. Hell, I don't even know what touchboost is. As far as I can tell, it's an app for managing your car's turbo system.

*To build my version of the OTA, I did took the GApps from someones' zip, added the missing system apks/removed the apks I didn't want, added the missing libs, replaced the media folder from the OTA, and updated the build.prop. The whole process took about 5 minutes. In the old days, I would have done a full file diff against the OTA to find missing libs or libs of different sizes and add/replace as necessary (or just compile the damn thing myself), but I just don't have time anymore. Holcomb227 is a lot more thorough than I am.
[Nexus 4 Android Development] ELB27:
Touchboost increases the CPU frequency every time you touch the screen which results in a smoother experience when scrolling for example.
[Nexus 4 Android Development] alexinc:
http://timos.me/blog/tag/mpdecision
[Nexus 4 Android Development] Gnome:
So I just need to find the right libs then. Hmm, alright then that is settled. Any advice where to start? Lol! :beer:

☆★ Click "Show Content" on my sig for my Guides and MODs. ☆★​
[Nexus 4 Android Development] itlnstln:
You can download the base ROM in the link in the OP and I would say jakdillard's AOSP ROM. I usually do this by eye, so I extract both ROMs and open the contents in two windows. I then go through each folder and look for files with the same name and check the filesizes. I also look for files that might be missing. Many of the files you'll be looking for will be in /system/lib, but there will be stuff sprinkled through /system/etc, /system/vendor, and so on. It can be fairly painstaking at first, but once you get a system down, you can breeze through a ROM pretty quickly. The problem in this case is that I can't think of a good base ROM to look at, but jakdillard's should be good. He modified/removed some apks, so I would ignore /system/app/. Focus on files that end in .lib, .xml, .conf, or no extension.

I'm sure there is an easier way to do this or even an app that can look in some of the files, too, but I'm old school and do **** the hard way.