yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neozyklon:
3rd party apps have huge fonts(200-300% zoom)

I recently flashed 06.07.2013 AOKP on my SG3 and I am noticing that all 3rd party apps (non-playstore apps) that I installed using .apk files have huge fonts. I cannot reduce them. I tried the same .apk on my other devices (Nexus 7 on Stock;Capitvate on CM10), they seems to look fine.

The fonts are so huge that I am unable to configure those apps. This may not be a problem with this version of AOKP alone. I remember noticing this in earlier versions of AOKP. Doesn't anyone have a similar problem ? Or any solution to this problem ?

Thanks,

neo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
The stock DPI for that device is different than the stock S3. I don't know if there is a difference in apk files between devices, eg. Tablet and phone, phone/phone but I'm sure Google will help. I would try a different apk or change the DPI to see if there is a difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
Error Installing ZIP

After build 5.9.2013 I am not able to update the ROM

Tried TWRP

Full Wipe

Factory reset

System Wipe

Data Wipe

Delvik/Cache wipe

Bootloader update as mentioned by task via ODIN

Downloaded update ROM via browser (No OTA)

Still "Error Installing zip" via TWRP

back to nandroid for past month or so

tried this various times.

dunno where to go from here....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Did you check your bootloader version to see if you successfully updated it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
How can I check as baseband shows updated to I747UCDLK3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Fail

Baseband has nothing to do with anything. That is the modem. Flash the boot loaders again if you have to. Sounds like they didn't flash the first time. Also make sure your download isn't corrupt and redownload the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
Checked via root checker and boot loader is I747UCDLK3

downloaded rom 4th time today

no luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
I think you are mistaken. Something about swyping to the right shows you your boot loader in that app. (Root Checker-by free android tools) You are looking at the modem like mentioned in the previous post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
Did swype to right n got this under board specs the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
My phone is kind of busted. Whenever I press home slightly, it goes into multitasking. Is there a way to set it so that I have to hold it for a few milliseconds longer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Posting a screen shot might help us understand better what you did wrong. Sounds like you flashed the boot loader wrong like task said. Make sure you are using the latest Odin and follow the boot loader update instructions.

If you some how flashed the latest modem to your boot loader I am not even sure your phone would boot. Task would know the answer to that one.

---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------

It would be easier for you to not use the button and add the nav bar with a home and multitask button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
Sorry

Attached are screenshots

http://i42.tinypic.com/2ppijxd.png

http://i43.tinypic.com/2ius81.jpg

Followed instructions for bootloader installation from here:

http://xdaforums.com/showpost.php?p=41535366&postcount=26684

Used Odin 3 communicator via win7 to flash I747UCDLK3 (AT&T) which was smooth and successful.

dunno what went wrong...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Wow. That one flew right over my head. I'm lost. 5.9.13 is the build you are on. I updated fine when the last release came out. I love that it's so quiet in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
Could the removal of emulated folder be cause, i removed '0' then emulated n brought all contents to root folders couple of weeks before. But phone never stopped working. It just random restart 5-6 times a day pushing me to update rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Possibly. I would wipe your internal and external along with the OP instructions, then put the flash able files on your SD and try again. Its worth a try if you haven't. It seems that your boot loader is up to date. Don't restore any apps.

I'm no expert but I try a lot of things before reporting issues. I have no random reboots anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gixxer_j:
If I want to revert to stock AT&T ROM (to test out some issues i'm having) from Task650's 6.7.2013 build, is there anything I should be aware of? (ie is the updated bootloader going to cause problems etc etc)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I would go ask this in the Q & A forum as its not related to this ROM at all. The boot loader is something that was released officially and is what comes on sgs3's sold today. It won't cause issues. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Are there plans to add HALO to this ROM? I was running this ROM for a few days, then I tried the Vanilla Rootbox for a few days and I prefer this ROM. HALO is the only little thing I miss, the other being a custom lockscreen background which isn't a big thing at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Nope. Halo is still in beta and only works properly about 50% of the time and it also breaks some pretty major functionality. Not something I'm going to add unless it can be integrated to work 99% correctly. There is an app on the market that does the same thing. It's called Floating Notifications.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
Awesome, thank you very much for the information. I went through all the Rootbox options but for me, since I don't use them, not having them means more stability so that's why I think this ROM will be just right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HolyGhostBoy1:
task you are the best developer i ever seen in updating roms they just keep coming i wont forget to hit the thanks button. my question is are u a android?:eek: lol i went to other roms but none update as fast as you i had to come back :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Trying to keep everything updated in Post 2 of this thread. I'm on vacation at the beach and doing the best I can to keep up with Task and Ktoon. I added the changelog which answered the 72 questions about the LED's and between Task's OP and this thread I think most of the questions asked here have been answered. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdubcramp:
And now my LED notifications are working as they should. Very odd. Didn't do anything special. :victory:

Recommend everyone wait a little bit to see if they correct themselves (as foolish as that sounds) before reporting issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pudge12:
I'm aware plenty of people are having issues with their led consistently flashing, but when you change the color in settings, has anyone else found a bright colored option aside from the default "white". If i change to blue or red, its a dull color which wouldnt really catch my eye in a dark room. Maybe im just picking bad colors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Can someone with LED blinking problems try this:

1. Go into LED notifications

2. Tap to change color

3. Tap "Holo" - color block should change to ICS blue

4. Tap on the right-hand color bar to pick a different color (for now, don't use the larger block)

5. Tap "Set".

6. Use back button to get out to home screen.

7. Reboot, and test.

Note: I had to do this twice to get it to stick (the first time I didn't pick "Holo" first), but this fixed the LED notifications for me with GMail and Touchdown.

---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------

I picked a nice royal blue from the bar on the right, and it's bright enough even in a bright room.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] House M.D.:
can anyone confirm if the google wallet app is working in this rom?

Please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pudge12:
I tried your steps to get the led to stop blinking. On reboot it stops, but so far once i get a notification it keeps blinking. I tried a few times, a few different ways. Only question I had about your steps, Once you choose your color in the right bar (step 4), in order to make the color stick you need to touch the small box above the words holo and set. Do you do this before or after set if at all? Ive tried it a few different ways, still cant get it to work so i wanted to ask. Thanks for trying either way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
question, on 2nd post i saw this "SMS>160 charcters won't send. Reported" I am on ICS version of the ROM Jul 16, (cant upgrade to JB without A2DP since i use daily) i noticed today i am having the same issue SMS>160 fails unless i convert to MMS (which i cant since i dont have MMS plan), is the reported problem on JB or ICS as well? if its JB anyone on ICS has this issue and any possible fix?

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tocirahl:
I believe this is default/expected behavior for AOSP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I just tapped on the color on the right side (the box changed to blue), then tapped set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uzii305:
Guys, Google wallet is not working on my phone. Any know hack or steps to take to make it work? It was working before on stock rooted ROM with a flash zip I found somewhere, but then I flashed this ROM with the K747 KERNEL and now its not working. Any1 know how to get it to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glwilliams4:
I'm running 7/28 and my LEDs work just right, don't have any problems with them that I've noticed. Did they work for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
I had a question go un answered, does anyone know why apps don't stay in cache the way they should. They reload after a couple minutes of inactivity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
They worked fine for me as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] House M.D.:
Anyone!?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
It's not unanswered, there is no answer - posting repeatedly about it is not going to get any better response. Task reads all the posts, and is subscribed, so when he has something to say about it, he will. You might not like the answer...:D

---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------

8/1 and 7/28 JB versions, when I try to make a call with the S3 included headphones plugged in, the phone dials out, then call ends before ring or answer on other end. I have no problem making or receiving calls with it as a handset.

Just reporting it since I haven't seen it posted. No response needed unless someone wants to thank me :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Well I was hoping anyone with maybe the knowledge other then op would see and answer. I don't really care how a person responds to anyone's question , but grown or not people should still have respect for one another. At the end of the day it's just a phone life goes on!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
hmmm, i know Captivate and S III are different phones, but phone come from AOSP, and this was working fine on Captivate AOKP. I could send SMS>160 with no problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
Where did you think they all went?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Then it was a custom messaging app. There doesn't seem to be one for this yet, but AOKP isn't even supported for the S3 - it's all Task and Ktoonsez :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
It's not working yet. Plus google just updated the app to not support rooted phone ex....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
In the latest release changelog, GSM mode is mentioned. Any idea what this functionality does?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zuchitnix:
http://i42.tinypic.com/2n6u7o0.jpg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Its not for this device. That is a generic change log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Haunt3r:
Is there any way to disable the hardware keys? I've looked everywhere under rom control. Am I just blind? I know it used to be possible, I used the search function on this thread and the rom thread itself.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Read the OP of this thread. We've made a ton of information available there.

This...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CorleReeFer:
Is it possible to add power on and power off sounds? I have the poweron.ogg file in system/media/audio/ui but cannot seem to get it to work... am I missing something? I also tried using power.ogg also with no luck... I am using the SGH-I737 if that makes any difference from the I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You can add anything you choose. Set the permissions to rw-r-r.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CorleReeFer:
Just for verification... do I need to also place

samsungpowersoundplay.bin in system/bin and make that rw-r-r also? And is it PowerOn.ogg or Power.ogg?

*edit* I just tried both power and poweron I believe they are case sensitive so I made sure that was right.. all permissions were rw-r-r yet it still does not seem to be working... any ideas? Or kno where I'm going wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Do we have the option of sound +vibrate on this ROM. I can see the option but only one works at a time either sound Orff vibration mode..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
Sound State toggle set to Sound On + Vibrate when ringing checked under sound settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
Has anyone else seen battery drain? I haven't used my phone much at all today but my phone has been draining battery and in battery I see "sec-ril" | "phone" taking up the battery... I searched Google and I see people suggesting to flash a different radio?

Sorry if this has been mentioned but I don't see anyone mention in ROM thread or here. I've never had this issue until 6/14 flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CorleReeFer:
Does anyone have any idea abt how to get the power on/power off sounds to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Double posting will not get you an answer any faster. People already saw your question, if someone knows, he will answer you. Since it is not specific to this ROM, you would have better luck if you opened a thread in the q&a section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CorleReeFer:
Well apparently there's smthg abt the ROM considering I've followed all of the directions listed on xda abt the subject... hence the reason I came to this q&a
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J-Wall:
I have downloaded the ROM twice and had two full wipes but my call log crashed every time I scroll too far on it. Here is the logcat for the crash (first time with catlog so if its not there I'll try again), thanks for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Are you restoring your call logs?

Wayne Tech Nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J-Wall:
Yes. The weird thing is that if I change it to missed or outgoing calls it won't crash. I think it has to do with the amount of call logs I have saved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
It very well could be as the phone and contacts apk was recently updated and restoring stuff from the older apks will cause issues. It is never advice's to restore system info like this. Do to it cause random issues

Wayne Tech Nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
I just had a phone lockup and reboot. I was in car streaming BT music and turned car off. Went inside house, tried to turn in phone and it was locked up. Not sure of is BT related or not. It also seems like music is skipping now over BT like stuttering. I didn't hear anything like that on last build. Here's the logs. I will look at them as well see if I see something, although I'm no SME :D thanks again everyone/task! I love the ROM ! Just want to get BT stable then I'm set!

http://db.tt/Aeo7PNiK
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] simonsayz31:
Constant Reboots

I have always used Task650 Roms on my S3. Everything always worked perfect until any ROM after April 19, 2013.

What happens...constant rebooting. Most of the time during boot (red task650 with gears, would freeze and reboot) and sometimes right after boot screen finishes.

What I have tried/done:

Clean wipes, updated bootloader, changed from CWM to TWRP (just in case), researched everywhere.

What I believe is wrong: GAPPS

The reason I say GAPPS because I used to install both ROM and GAPPS at the same time. For troubleshooting purposes I installed ROM (6.14.13 ROM) first and rebooted. S3 boots up perfectly fine. Went back in recovery, cleared cache and dalvik, installed GAPPS (6.12.13 GAPPS, even tried the install twice because the OP said sometimes the first try doesn't work), cleared cache and dalvik, reboot... and constant reboots. This happens every single time no matter how I wipe system, cache, etc...

Once again, 4.19.13 ROM was the last ROM that worked for me with GAPPS. Every ROM afterwards does the constant rebooting. I see all the updates Task has done and would really like to get the latest ROM.

Any help will be GREATLY appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Try and re-download the whole set from the OP it all works great here. Make sure you dl the right one for your carrier. TWRP it's fine.

You should have updated your bootloader as well, since that was only a few releases back.

Happy Fathers Day to all you mothers :)

-- nice story, bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddiehl:
In theory will Ktoonzes (sp) play nice with this Rom, or vice versa? Just wondering since I've seen credit to each others work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Ktoonsez's kernel will work with this ROM. And very well at that. Just keep in mind that Task only supports what he provides in the OP of his dev thread. Meaning if you run into issues after flashing Ktoonsez's kernel, don't come to Task for support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddiehl:
Thanks, and I understand the support aspect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
Hi Task,

Many thanks for this great ROM! :thumbup::)

Sent from my Galaxy S III ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nbrent1007:
Are you using an up to date recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Had you looked task has already said it would take be added due to the bugs that it brings

Wayne Tech Nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
No...I've failed to find it...but thanks...I'll remove the request...:(

Sent from my Galaxy S III ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
I will be adding a date to the thread title. This means that on that date something has been added to, modified or deleted from the FAQ which is the first 3 posts of this thread. Included, along with the date anything in red will mean it is an update or change. Hopefully this will help keep repetitive questions out of both threads and you won't have to read the entire three threads to see if something is new. I will try to update as frequently as needed. And Happy Father's Day to all you dads. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Try booting without gapps and up the voltages by 50mV each. Perhaps your CPU can't take the lowered voltages and initializing gapps puts too heavy a load on your CPU at the present voltages. They are set much lower than stock... it is worth a try. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] simonsayz31:
Have re-downloaded them several times. No change on outcome. :crying: Did update bootloader when it was first posted and tried it again to double check. I know how Task doesn't like it when people don't read OP and try some troubleshooting before posting on the forum...so I tried everything I read or could think of :p

Yup. Just installed TWRP version 2.5 before attempting more 'troubleshooting' procedures. :silly:

That makes sense. My last attempt was with my battery at around 50% but the power cord plugged in. Does battery level matter...I know it is recommended to do it with a battery as full as possible. Never had a problem before, so didn't think it was a factor.

Anyways back to voltage regulation...I am assuming that 'Trickster MOD' can change it? I am currently running a different ROM until I got some help with Task650 ROM from you wonderful people! :good::good:

Since I am running a different ROM can anybody confirm that voltage regulation is available with the Task650's base ROM? The reason I ask is because it looks like it is a premium feature or 'donate key.' If it is, I am not sure how I would be able to get that installed without having GAPPS because, if I remember correctly, there isn't a file explorer with the base ROM for me to install an APK. There is a terminal application i think, should I try to install the apk there from sd or external sd?

Last question, you recommended 50mV increments. Looking at the pictures in the play store for Trickster MOD, the voltage value for example would be 950 at a certain frequency. Is that seen as 0.950 V so an increment of 50mV would be 1 V?

THANK YOU ALL FOR ALL THE HELP! :highfive: HAPPY FATHERS DAY!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Trickster Mod comes with the ROM, found under Kernel Settings in Settings. Anyway you can adjust all of the voltages up by 25mV (950mV = .950V yes) with a single click in Trickster at the top of the Voltage Settings. I would try upping by 50mV since your phone crashes so easily.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dave the Knave:
Correct. .950V + 50mV is 1V. 50mV increments seem to work best. My phone seems to be a bit more picky and needed a 75mV increase across the board. But damn is it smooth!

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] simonsayz31:
Thanks guys for the help. Unfortunately it didn't work.:crying:

So, I did a clean wipe, installed only the Task650 base (6.14.13), wipe dalvik and cache, and rebooted. It rebooted once while pink Task startup, once while 'updating apps' before it gets to home screen, and then finally we are in! Went to Trickster MOD, increased voltage by 50mv and hit apply. Gave it some time to make sure everything was ok, then just did a reboot to make sure nothing got messed up before I would try to install GAPPS.

Phone was in constant reboot, will not go pass the grey task boot screen. I'll let it reboot about 10 times. Each reboot was more painful than the other. Haha.

To double check, I did the above again but this time it never boots to home screen just keeps looping on either grey or pink task startup screen.

I just don't know what it could possibly be. It sucks because I can't get back to try to increase the voltage some more. Sucks so bad!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EK2:
is it possible to export my current contacts to sim card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
is there any way to setup pptp vpn and enable screen lock via Slide (not PIN, pass or graph key) ?