yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] le0.br4zuc4:
I'm not sure very big fan of TW launcher but I do like the full calendar widget which is very useful for me.

So I really want a TW launcher modified for 4 X 5 grid like I had in the GS3 and Note 2.

Does anyone know if that's already being done? After sometime searching i could not find anything.

Thanks for lot for the help.
[Verizon Samsung Galaxy S 4] brizey:
I think Nottach (the Xposed module) has it.
[Verizon Samsung Galaxy S 4] urcboss07:
I also want to have 4X5 touchwiz but try Nottach, it doesn't work.
[Verizon Samsung Galaxy S 4] le0.br4zuc4:
I tried and before posting here, didn't work
[Verizon Samsung Galaxy S 4] prerav31:
Try this

http://xdaforums.com/showthread.php?p=41255823
[Verizon Samsung Galaxy S 4] le0.br4zuc4:
Thanks for this. I am using this now but some widgets I use won't get resized from 4 X 2 to 5 X 2 so it looks weird.

The icons are really small too, but for now, I am using this launcher :)

Thanks for lot
[Verizon Samsung Galaxy S 4] theresin:
I'm throwing a vote in for this as well .. it's a major PITA making one of these work (sizing/pixels/etc) .. so major props and all my thanks to the dev that puts in the effort!
[Verizon Samsung Galaxy S 4] ProfEngr:
I have CR4.8 on the company Note2. Used the 4x5 option in aroma & Scott also had it coded for 5x5 app drawer. Would love to have that config on the S4. Doesn't mess with widgets & there's plenty of room for 5x5 in the app drawer. If I get some time I might look into what's required to make the mods for it. Could easily get in over my head though.

Sent from my SGS4 using one opposable thumb.
[Verizon Samsung Galaxy S 4] rwc95:
I made a 4x5 homescreen, 4x5 app drawer version if anyone here interested.

http://xdaforums.com/showthread.php?p=42131780#post42131780
[Verizon Samsung Galaxy S 4] le0.br4zuc4:
Using it. Love it. Thanks a lot man.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] skeith223:
Has anyone had issues with storybook force closing after pics added. I cleared data and restarted and still force closing.
[MDA II, XDA II, 2060 ROM Development] findus:
Hi, I was just wondering if anybody would be able to post the Extended ROM from their UK Orange M2000 for us to have a look at as I have searched and can't find anything! Any help would be much appreciated!

Fin
[Galaxy Note II Q&A, Help & Troubleshooting] mazdamiata210:
On the US version of any galaxy phone when a picture message is received it shows up full screen when tapped on... On my n7100 it shows up in this weird photo viewer slideshow thing... Any way to port over the US version of the MMS app to the n7100? Just moving the secmms.apk and secmms.odex didn't seem to work.
[Defy General] xsasuke:
Hello everybody!

I'm here to ask you whats your score on AnTuTu Benchmark.

Why?

Cause my Defy+ just got 2872 points and i see people with 7000 points without overclocking on the rank. (With overclock to 1350mhz it got 8396 points).

I use Quarx ROM 4.1.2 and the people that made 7000 points haves 4.1.2 too.

I have my crashes at my Defy+ i just have it stable if i close all apps =/ its normal? (Ik the defy its just single-core 1Ghz we cant wait a very good performance but the galaxy Y 850mhz of my friend answer fast the commands than my defy+ 1ghz).

If you have something to make the Defy+ faster and make more points at AnTuTu tell me.

Thanks!
[Defy General] deweylewie:
Here's mine, all original:View attachment 2018654
[Defy General] Mavasilisk:
I've already scored like 3000-3300. Dont you know that benchmarks can be manipulated? You can make your 350mhz 128 ram device to show a score like Galaxy S4 but it will be stil the same crap. Benchmarks are not the best way to test a device. Play around with it for about a day and you will decide if your device is faster with the changes you did.
[Defy General] coolshahabaz:
Mine is about 3500....I am on cm10@1.2 Ghz....I recommend u to underclock ur device 1350 is not that stable....after under clock u again test ur device m sure I'll get more score :)....

#hit thanks if I helped :)
[T-Mobile, Samsung Galaxy SIII] silver709:
Can someone please explain why I bricked my galaxy s3 phone. I have a Samsung galaxy S3 sgh-t999. Phone had a 4.1.1 system and it was rooted. I installed MS Team HD 11.0 from here: http://xdaforums.com/showthread.php?t=1886332 after installation was completed phone asked to reboot and never came back. Black screen and no buttons responding. Was that rom not for my phone? Also that Rom was in the phone memory not SD card.
[T-Mobile, Samsung Galaxy SIII] rawdaddymagraden:
That would be because you flashed a rom for the i9300 international model not for the t999. It is always important to read read read before diving into things. Sorry to hear your situation.
[T-Mobile, Samsung Galaxy SIII] mongo41:
Yep what he said.
[T-Mobile, Samsung Galaxy SIII] Sud0lit3:
Look on the forum directory.

It reads "> Samsung Galaxy S III I9300, I9305 > Galaxy S III Android Development >"

from that we can assume that all posts made in this section are for international S3 devices.
[T-Mobile, Samsung Galaxy SIII] silver709:
Thanks a lot! I will try modding again after fixing the phone.
[T-Mobile, Samsung Galaxy SIII] mongo41:
Thats the spirit!!!!
[T-Mobile, Samsung Galaxy SIII] Sud0lit3:
This is why I love XDA :) everyone here is super nice and super helpful
[T-Mobile, Samsung Galaxy SIII] Don_Perrignon:
People on XDA are not nice. You happened to get the very small percentage of them that are.
[T-Mobile, Samsung Galaxy SIII] unciviilized:
Do you know where to repair your phone from the brick? I recently bricked my s3 flashing the t999v bootloader but luckily for me there's a guy here in Dallas, TX that repaired for $30 he has a listing in ebay
[T-Mobile, Samsung Galaxy SIII] Josh McGrath:
You can either pay to have it jtag or you can just call tmobile and tell them you don't know what happened. You gotta have insurance though. Don't worry about the no warranty fee cause they won't be able to tell anything about the phone in that condition because nothing works lol. ....reason I know is cause I did the same thing to my sprint s3.

tmobile s3 running wicked. I still use a t9 text app so excuse the errors :)
[T-Mobile, Samsung Galaxy SIII] winmx1:
mobiletechvideos .com

I had my phone hard bricked too, he fixed it for me and everything was great afterwards :]

good luck!
[T-Mobile, Samsung Galaxy SIII] Bendezium:
Thank you so much! I nearly forgot I've been paying handset protection for the last year and a half! I got a phone en route.
[T-Mobile, Samsung Galaxy SIII] ryro04:
Fix

I sent mine to Mobiletechvideos.com as well and they were able to fix it.
[Nexus 4 Q&A, Help & Troubleshooting] mor_1228:
guys got my Nexus yesterday and today when I did to play nfs I couldn't see anything. I also feel white is not pure white is kind of yellow tint in all over the mobile screen.
[Nexus 4 Q&A, Help & Troubleshooting] scream4cheese:
It's the application.

Take a look at the game reviews. You're not the only one having those issues with the black screen.
[Nexus 4 Q&A, Help & Troubleshooting] mor_1228:
i was not having this in earlier devices i owned but in n4 only. u know how to solve this ?
[Xperia Z Q&A, Help & Troubleshooting] finoqq84:
Another issue found, the mic muting issue has not be solved on .253 . Still needs to restart or turn off the noise suppression option.
[Xperia Z Q&A, Help & Troubleshooting] x102x96x:
What's ur issue exactly?

Anyway if these kindda problems remain on ur phone after updates or flashing another stock kernel or Rom just take ur phone to service

Sent via my Sony Xperia Z | C6602
[Xperia Z Q&A, Help & Troubleshooting] micheled:
The Reason for the microphone issue is the newest update for Google Search. Uninstall this update an do not update this app until Google releases a new version with bug fixing.
[Xperia Z Q&A, Help & Troubleshooting] finoqq84:
Thanks MICHELED, :fingers-crossed: for your PROPER solution. I will try it out and see if the issue still exists. As this issue happens not only on my XZ , but also with my wife's and brother's XZ, I don't think that i would be so unlucky to have bought 3 faulty phones, right, x102 ? :D
[Xperia Z Q&A, Help & Troubleshooting] stefanopimenta:
Same problem here. How to solve it?

I already uninstaled google search, but nothing happens...
[Galaxy S 4 Accessories] ivesdotkom:
I was wondering if anyone gad this batrery cover or something like it. I just ordered it but I cant find any reviews for it.

http://www.amazon.com/gp/aw/d/B00CM234DO/ref=pd_aw_sbs_cps_3?pi=SL500_SY115
[Galaxy S 4 Accessories] likeitnot:
D@MN, that is one nice looking battery door replacement cover.

Let us know if it's legit/worth it after you get yours. Hopefully, for your sake and mine (since I will buy it if legit), it's well worth it!!
[Galaxy S 4 Accessories] ivesdotkom:
I will post pics and review when its delivered. I hope its gonna look hiw I want it too...lol
[Galaxy S 4 Accessories] likeitnot:
lol, yeah, hopefully the picture doesn't even do it true justice (and not the other way around lol).

And thanks, I've already set this topic to my favorites so I can keep an eye out for your update since this is something I really really want.
[Galaxy S 4 Accessories] likeitnot:
Bumping* Just want to see if you got your case yet?
[Galaxy S 4 Accessories] sneekerpimpz:
Those covers ar nice but if you ever use NFC, Android beam, or S-Beam it blocks those fuctions. Cant penetrate through the aluminum, but if you dont use it, they always improve on the phones looks.
[Galaxy S 4 Accessories] ivesdotkom:
Didnt even think about that but ive never used those features anyway.

Nope not yet should be here next week!
[Galaxy S 4 Accessories] rahulsuneja:
Looks gorgeous.. I just hope amazon brings those goodies to India soon. They just launched their opetations in India with books & movies only a couple of days ago!
[Galaxy S 4 Accessories] sneekerpimpz:
Do you guys get ebay in India? The same products can usually be found on there as well.
[Sony Ericsson Xperia Neo, Pro] Men_in_black007:
Hi!!!

Is It Possible To Port Xperia J Custom Rom For Xperia Neo V??

As All The Hardware Are Same!!!:svetius::svetius:

Suggest Me Is That Possible!!

If Is It Then I Will Try To Port It!!:D:D
[Sony Ericsson Xperia Neo, Pro] Phillip Wu:
But the board are differnet you'll suffer No Camera , wifi ...etc

And the only possible way is to use it as base and use CM rom as main , and porting some libs and apps

IT is such a pain
[Sony Ericsson Xperia Neo, Pro] Men_in_black007:
Does Porting Rom Will Take Weeks??
[Sony Ericsson Xperia Neo, Pro] Phillip Wu:
Depend on your ability :angel: , If you are clever enough to figured out what to with X , what to do with Y !!!

Then it take less than a weeks ,

Try to get many many testers and co-dev as possible , the more idea you have , the better rom you have :highfive:

I'm not experienced enough to help you ;) , guess you should find someone else

Here is a guide

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

No need to spam ;) , Do hit the thank if you wanna thank me no need to post again and again
[Sony Ericsson Xperia Neo, Pro] Men_in_black007:
Can You Help In Porting A Xperia J Rom???

Can You Guide Me??
[Sony Ericsson Xperia Neo, Pro] Men_in_black007:
Thanks For Help!!!

But It Is easy to port Xperia Ray And Arc Rom For Neo V??
[Sony Ericsson Xperia Neo, Pro] mr.nou:
You can't use methode port of xperia 2011 to 2011 on it

Because the /lib framework is so different

U have to do full port i think
[Sony Ericsson Xperia Neo, Pro] avinashrocks1990:
The best way to port is to compile using the source rom code and use hardware configuration manifest for your device

You won't face any problem and everything will work
[Sony Ericsson Xperia Neo, Pro] vishal_android freak:
Me to started with this thing bro.. Ur hardware and device line up ( meaning 2011 Xperias, 2012 Xperias n soo) is important which decides the time needed and how successful will the port be.. As avinash said, thats the perfect way to do it.. But if you want to port it with softmods and stuff, a little knowledge about what are you doing is needed.. So read some porting guides.. :) you will surely get some help.. ;)
[Sony Ericsson Xperia Neo, Pro] Furak07:
Sony xperia rom port j ha ... I think it would be nice to think that could have been the most popular rom.
[T-Mobile Samsung Galaxy S II SGH-T989] Dennisalex:
Well xposed is installed and i have lag problems with batteries icon change, NCB1 custom background on Notification Panel, i also use icon theme with a galaxys4 theme does anyone else having these lag problems.

Current kernel is Cerux 2 with Intellidemand,noop, and sometimes Interactive ,Noop.
[Nexus Q Android Development] hharte:
I have been using my Nexus Q for about a year via the audio amplifier outputs. When the last Music update broke Q functionality, I decided to give CM10.1 a try on the Q. After fighting some installation issues, where all audio output except "Alarms" were silenced, I found that audio is only working on the HDMI output.

After digging through the code and doing a bit of analysis of the stock Audio HAL, I figured out how to make an audio HAL that supports the TAS5713 audio amplifier used in the Q. As of now, it only supports one audio output device (either HDMI, S/PDIF, or TAS5713) at a time, and the output can only be changed during compile time.

But with some work, this HAL could eventually support all three outputs (HDMI, S/PDIF, TAS5713.) The issue is that Android only appears to support one output device at a time. In order to overcome this, I believe the audio HAL would have to replicate the PCM data stream and send a separate copy to each device.

Through experimentation, I found that the TAS5713 requires a 48KHz audio stream, and S/PDIF also works well with this rate.

Another challenge is that the TAS5713 amplifier volume is controlled by the kernel driver, so you have to tell Android that the Audio HAL will do the volume control itself (ie, not rely on the mixer in Android.) For this reason, if all three output devices are eventually supported, volume control for S/PDIF and HDMI would have to be done in software. Perhaps it can be done while duplicating the PCM stream by taking each of the 16-bit values and multiplying it by the volume level.

Looking through the Steelhead kernel, you can see that Google put some work into being able to synchronize the three audio output devices. This would also have to be added to the HAL for proper operation.

Anyway, I'm putting the changes out there in GitHub in case someone wants to do some more improvement to this audio HAL.

The fork of CyanogenMod/android_device_google_steelhead is hharte/android_device_google_steelhead:

https://github.com/hharte/android_device_google_steelhead

For binaries that you can flash to your Q (TAS5713 audio amplifier and S/PDIF) please scroll down to post #9 and choose the correct binary. Each binary only supports one audio output.
[Nexus Q Android Development] THE_KINGDOM:
Please make this a reality.. I'm dying to have the analogue outputs working at the same as HDMI. it was possible on the stock Nexus Q image.
[Nexus Q Android Development] Malnilion:
Thank you for the work you've put into making this a reality. I would love to try out a build with the amplifier selected as the output device, but it sounds like you can't control the volume natively?
[Nexus Q Android Development] mahler47:
Thanks for doing this!

After cloning your repository, I wasn't sure what to modify to have audio output through S/PDIF or TAS5713. Would you mind giving some advice to someone new to building CM?

Thanks in advance.
[Nexus Q Android Development] hharte:
In device/google/steelhead/audio/audio_hw.c, change the following line in the function adev_open():

adev->card = CARD_STEELHEAD_TAS5713;

Change CARD_STEELHEAD_TAS5713 to one of:

CARD_STEELHEAD_HDMI,

CARD_STEELHEAD_SPDIF,

CARD_STEELHEAD_TAS5713

Volume control should work fine for each of these, based on my last commit:

https://github.com/hharte/android_d...mmit/a15f772b5651e0b14c65f6ff1a6d498d2951e081

Then "brunch steelhead" to re-build CM10.1 for Nexus Q. After it is done building, you can go into out/target/product/steelhead/ and do "fastboot -w flashall" to wipe and flash the new CM image. If you are making minor mods, no need to use "-w" to wipe.

Please let me know if you find any issues. One of the main things I've struggled with when using CM10.1 on Nexus Q is that sometimes after installing gapps, the audio is completely silent. I have not found a good way to fix this other than downloading and installing "Audio Manager" from the Play Store.

-Howard
[Nexus Q Android Development] mahler47:
Howard, YOU ROCK!

This is amazing. My Nexus Q is nearly back to the functionality that I once had with stock firmware, and it's once again a useful device.

Here's my setup:

1) 2013-06-12 nightly build with your changes merged, and as instructed above, audio sent to S/PDIF. My Q is connected to the stereo via optical cable.

2) VNC Server is installed on the Q, and it turns on upon boot. I am using this VNC Server, but I bet others would work.

https://play.google.com/store/apps/details?id=com.schumi.vncs

3) I also have FTP server and ADB Wireless turned on upon booting so I can push files and mess with the Q remotely.

4) VNC Viewer installed on my other devices.

With all of that, I can basically control the Q remotely from my phone, tablet, or computer. VNC is slow, even with a wired connection, but it works.

Prior to your good work, I had to have the TV on to hear anything out of my Nexus Q. However, with the changes you've implemented, I no longer have to do that. My Q lives again!! :victory:

Thanks so much--things can only get better and better from here. This is exactly why the Android community is so amazing.
[Nexus Q Android Development] hharte:
Glad to hear that it is working for you. I'm using AirBubble and Bubble uPnP apps on my Q along with "Remote for iTunes" on my phones/tablet. This allows me to actually use my iTunes library on the Q remotely, and DLNA as well.

What needs to be done next (but not sure when I will have time to do it) is to make some changes to the Audio HAL to replicate the audio stream for each output (HDMI, Amplifier, S/PDIF) and implement software volume control for the HDMI and S/PDIF.

Another really cool thing would be to be able to make the Q into a Bluetooth A2DP sink. Then you could pair it to your phone and use it as a set of bluetooth speakers.

Google obviously put a lot more effort into the Q than I have done (making a remote management app that is simple to use, and put a lot of work into making sure that the three audio outputs are synchronized.) So there is a lot more work that needs to be done.

Maybe eventually Cyanogenmod can take my audio HAL. At least it seems to be working as well as the one included in the CM10.1 nightly, and adds the choice of using the other audio outputs, although only as a compile option unfortunately.
[Nexus Q Android Development] Malnilion:
I'm embarrassingly uninformed about the inner workings of Android, but is ALSA in Android in any way like it is in Linux? Because I think in Linux when you use ALSA to configure your sound devices and let's say you use Pulse Audio, you have to define in the ALSA config which devices to output sound to and also expose them somehow to the PA mixer. It sounds like what you're doing is only compiling one alsa module whereas a HAL more like the one Google's would be 3 separate modules, right? And then I have no idea how the Android mixer works, but in Linux you'd have a master slider that would control the digital sound and then separate sliders for each output device. Is that sort of behavior replicable in Android?

On a different note, I'm really really sorry to beg because I'm so close to getting a CM build environment set up for the first time, but could either of you gentleman upload a working TAS5713 build? I feel pathetic because it's taken me 2 days just to get a VM image set up on my wife's laptop and most of the CM repo synced and I just *know* that this rom is going to take hours to compile (assuming I was competent enough to set it up right and create a proper manifest). Once/if I get everything set up, I think I'm going to go ahead and commit to merging your amazing work with CM10.1 final when it's out and uploading the zip so that all 5 of us Nexus Q owners out there don't each have compile it from source, but for now, I'd appreciate any help y'all can give me :P
[Nexus Q Android Development] hharte:
Hello,

Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:

These files ar enow being hosted at AndroidFileHost

TAS5713 (Audio Amplifier):

Download: https://www.androidfilehost.com/?fid=95784891001602467 (148MB)

MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip

SPDIF:

Download: https://www.androidfilehost.com/?fid=95784891001602468 (148MB)

MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip

HDMI: Use stock CM 10.1 nightly build.

Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.

To install:

Boot into recovery mode:

fastboot boot recovery.img

When Q has reached recovery mode, push the cm-10.1-....zip to /sdcard using adb, ie:

adb push cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip /sdcard/

push gapps (if desired) to /sdcard/

gapps-20130301.zip http://goo.im/gapps/gapps-jb-20130301-signed.zip md5: b7e53e96e1c8b1a1c4865bf29418c8e0

From within recovery, "install zip from sdcard" and browse to cm zip file. After this has installed, it is a good idea to wipe data and cache. Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps .zip file.

If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:

Unplug power for Nexus Q and wait about 10 seconds.

Plug Q back in.

When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.

As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.

Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.

Please let me know how these work for you. I'm using these TAS5713 and SPDIF builds now and they are working fine for me.
[Nexus Q Android Development] Malnilion:
Thank you so much! My foray into rom building was initially a disaster. I got what I thought was a good virtual image built and configured, but then I found out a fundamental error on my part...I had built a 32bit image. So, I finally just installed Ubuntu on a system partition and finally yesterday built my first stock CM image. I'm going to keep going so I can build for myself, but at least now I can listen to my music on my nexus q speakers while I'm working :D

Your build is working just great for me. The only times I've had volume issues on stock, I just had to wiggle the nexus q top and tap mute/unmute a couple times. I don't know if your HAL is any different or not yet, but so far, so good! Thanks again!

Edit:

I've mirrored your files and intend for this to be the place I'll put my builds in the future. I'm fairly sure Google Drive doesn't have bandwidth limits, so anybody reading...have at it!
[Nexus Q Android Development] hharte:
Make sure you have plenty of RAM in your VM. I'm building on a Mac Pro running Ubuntu (not in a VM) and it takes about 35 minutes to build.

Tried once in a VM running under Windows and killed it after about a day... but the VM only had 1GB of RAM allocated to it.