yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Depressed T.Bear:
I've actually had similar experiences when I tried 240dpi while flashing. Also, my Play Store was force closing all the time.

Then I decided to change the dpi back to 320 and applied 240 only for the apps of my choice via AppSettings.

After uninstalling the Xposed PlayStoreFixes module even my Play Store is running rock stable ;)

Just give it a try. I am sure it will help you too. :silly:
[Galaxy S III Android Development] SuperAce609:
So I'm guessing the whole rom has to be 320 in order for the keyboard to work. Oh well, Google keyboard it is. Thanks!
[Galaxy S III Android Development] Depressed T.Bear:
I dunno if it has to be the whole rom... But I just made the experience that those problems were gone this way ;) You're welcome!
[Galaxy S III Android Development] k6?:
I don't know if anyone else has had this experience but I now have no sound on my phone after updating to latest version. Notifications work fine but I have no media sound?

Any ideas?
[Galaxy S III Android Development] AssassinGEO:
Full wipe or dirty flash? Had this. Wipe helped.
[Galaxy S III Android Development] rfdz82:
Battery not charging as before.

Kinda new to android but I´ve been trying some roms on XDA.

About a week ago my battery started to underperform so I tried flashing different roms in order to discard some bug but no luck. So I decided to get a new battery since theyre cheap where I live but unfortunately I´m having the same charging issues even with Archidroid without touching any of the preset values for charging.

My question is.. How much should I raise the charge value to get a faster charge without damaging the battery? or Could there be a hardware issue I should test for before I start tweaking charge settings?

The new battery holds its charge pretty well and charges ok when the phone is off. The issue is charging when the phone is on. (GS3 I9300) I´ve made sure power hungry apps are off while charging in order to eliminate that as an option

Thanks.
[Galaxy S III Android Development] abhibnl:
Check with galaxy charging app that how much mA is your charger supplying to battery? And slower charging while using phone is normal!

Sent from Galaxy S3 Powered by Temasek + Boeffla
[Galaxy S III Android Development] SuperAce609:
Yeah bro, sounds like a faulty charger. If you're on boeffla kernel, you can use the app itself to see the voltage you're receiving from your charger. A good one should max out at the value you set it to.

For example, mines charges at 1200mAh constantly. But it's an HTC cable with a Samsung wall plug. Gotta find what works for ya.
[Galaxy S III Android Development] malachow:
For sure I don't.

Actually Ace, long time ago when I was choosing in aroma only stock keyboard every time I decided to experiment with its DPI - I changed value to 320 (my system DPI is always 280) & recognized it had become oversized. Then I reverted changes in app settings module and, surprisingly in comparison to your experiences, after that keyboard just started to work flowlessly again. Without any particular FC.

:)
[Galaxy S III Android Development] SuperAce609:
That's amazing. Mine resized back to normal but the force closing stays :(
[Galaxy S III Android Development] malachow:
I consider you as a pro-user around here, but I must ask if you try any of these universal steps after these FCs?

#0 (favourite one :D) reboot device

#1 clear app data (or at least cache)

#2 re-install app by taking keyboard apk from AD .zip & placing into /system/app

#3 logcat

:)
[Galaxy S III Android Development] SuperAce609:
I didn't think any of those applied since i was just messing with the DPI. I'll try them now :D
[Galaxy S III Android Development] malachow:
Ok, waitting for report back. :D

Btw, in #2 I would firstly completely uninstall keyboard using some TB, then place apk into /system/app. :)
[Galaxy S III Android Development] SuperAce609:
Too late. I cleared the keyboard data which was a whopping 170MB and now context provider FCs and freezes the phone upon boot. Trying to reinstall Google keyboard from the aroma installation to see if that'll fix anything. Horrible timing to get a soft brick.
[Galaxy S III Android Development] malachow:
Argh, my fault probably :(

Reflash should do the trick.
[Galaxy S III Android Development] SuperAce609:
Oh never mind. Got extremely lucky. Thank Archi for introducing me to cool tool. Apparently some other processes were maxing out the processor so the phone was crawling. After tapping and waiting, I managed to enable back google keyboard as default and the context provider FCs stopped. Everything is fine now. Lucky because I have to go to work in 6 hrs. I'll make a backup tomorrow and keep messing with the keyboard.

Don't know why the Samsung keyboard is so problematic though. Thanks for all the hints, knowing myself I'll try them all out. :D

Edit: Ended up having to reflash. Uninstalled the keyboard and messed up the whole rom. Either way, now I installed with the Samsung keyboard and stock Archi Kernel so phone is running better than before. No regrets except my loss of sleep.
[Galaxy S III Android Development] franatic08:
Is the edit shortcut on the lock screen a new Sammy feature?

I really like to get rid of that annoying pencil icon.
[Galaxy S III Android Development] SuperAce609:
No idea how to. I've already looked almost everywhere possible. Not like it works either way, since personal messages always stay blank no matter what you write.
[Galaxy S III Android Development] franatic08:
To display lockscreen text you need to have Sammy fonts installed.

Now to get rid of that pencil icon...
[Galaxy S III Android Development] iamezio:
You go to lockscreen -> shortcuts and tap on the icons .
[Galaxy S III Android Development] AssassinGEO:
It isn't any new. I have it on my old MK6,but only when I swipe down (if you're exactly about that).

It was there since 4.3 was released.
[Galaxy S III Android Development] Hexo07:
Hey. I just want to say Thank you Archi for this amazing ROM.

I used it now since some month and everything is running well.

Perfect.

THANKS

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] franatic08:
I know about the swipe down, but I mean the pencil icon on the right.

See screenshot.

Edit:

Screenshot wont upload from XDA app.
[Galaxy S III Android Development] SuperAce609:
Thank you for taking your time to tell me that. After having said it, no one bothered to tell me.
[Galaxy S III Android Development] k6?:
I had no sound after a force update. I'll try clearing the cache before wiping as I don't really want to if can be helped.
[Galaxy S III Android Development] coolnand:
When I get new message, it just shows new message instead of content. I believe this is an old bug. Will removing and adding Google account rectify it? Its been a long time and I was in 4.4 archis for a long time. If its not any trouble, do help me out. :)
[Galaxy S III Android Development] snnrkn:
It's not a bug. Go to settings in messages app. You'll see the option to whether see or not the content of the message. It's been there for a long time.
[Galaxy S III Android Development] snidhin08:
Thanks..was looking for this..:D..
[Galaxy S III Android Development] Buckycasuals:
Any idea why Archi reverted back to na8 modem?
[Galaxy S III Android Development] malachow:
Changelog:
[Galaxy S III Android Development] franatic08:
Does this camera issue affect more users?

See screenshot.

Also, yesterday I posted about the pencil icon on the lockscreen, but couldn't upload the screenshot. I managed to attach it now. Anyone know how to get rid of that?
[Galaxy S III Android Development] Gastozz:
Hi, is possible to get internal storage visible in recovery programs on PC. I want try to recover some files.
[Galaxy S III Android Development] franatic08:
Try mounting USB from recovery on the phone.
[Galaxy S III Android Development] snnrkn:
Hey [MENTION=5161352]JustArchi[/MENTION]

When can we expect a fix release for busybox problem. I'll wipe my phone for a clean installation. I'm waiting for the fixed release.
[Galaxy S III Android Development] JustArchi:
It's not a major problem, so in next release.
[Galaxy S III Android Development] normeck:
it is because you using non stock dpi... change to stock dpi and the pencil will gone
[Galaxy S III Android Development] SuperAce609:
Is it something we can fix ourselves by flashing a file or something?

---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------

Resize camera back to 320 using app settings xposed module. You don't have to change the whole rom back.
[Galaxy S III Android Development] JustArchi:
Yes, just take /system/xbin/busybox from older release :).
[Galaxy S III Android Development] SuperAce609:
Oh alright. Just copy and replace then reboot?

.........or are you being sarcastic? >_>
[Galaxy S III Android Development] JustArchi:
Why should I be sarcastic? I'm only sarcastic to questions being answered three times per day and ETA questions :).

Don't forget about proper permissions. It must be 755.
[Galaxy S III Android Development] rfdz82:
I just realised I had 5 cables with a different spec lying around the house. Problem solved.

Thanks alot
[Galaxy S III Android Development] SuperAce609:
No problem. Just make sure you leave other charging settings intact. Like ignore unstable current, ect.

Archi, switched busy box with version 1.7.17 and still error. Copied and pasted into the destined location, replacing the previous one, then set permisions to rwxr-xr-x like you stated as well.
[Galaxy S III Android Development] JustArchi:
And why you're trying to use swapon as user and not root? :o
[Galaxy S III Android Development] franatic08:
OK thanks.

I really like the default AD DPI, I'm nog gonna change it back.

If I replace the lockscreen on the latest AD 1.x will I break anything? I'll go ahead and see if I can install aosp lockscreen.

Also, I somehow managed to screw up the AD install with appsettings app to resize the camera app. I'll replace that with the aosp camera on a fresh installation.

Thanks for all the hints and tips!
[Galaxy S III Android Development] SuperAce609:
I give up. Lol
[Galaxy S III Android Development] JustArchi:
This is not the error I'm fixing :).
[Galaxy S III Android Development] franatic08:
I'm not into requesting devs for added ROM features.

I just want to say I'd really appreciate an aosp lock screen.

Not requesting or asking for it, just saying..:cool:;):D
[Galaxy S III Android Development] SuperAce609:
Well, anything you fix is always good. Time to play the waiting game.

Go Archi!
[Galaxy S III Android Development] cloudx720:
Shall I wait for xx based firmware or is ubu the same? Thanks.
[Galaxy S III Android Development] malachow:
Altough AD1.7.17 based on UBU had some issues, AD1.7.18 based on the latest UBU works like a charm. Download & flash. ;)
[Galaxy S III Android Development] killerfrog:
Going to flash from Imperium. Which kernel do you suggest? Archi or Boeffla?
[Galaxy S III Android Development] malachow:
Farstly try with ArchiKernel. :good:
[Galaxy S III Android Development] schooner:
How do i screen shot.?
[Galaxy S III Android Development] benedictros:
Hold power button and home button for 2-3 seconds. Should take screenshot
[Galaxy S III Android Development] gabyif:
Power+Home

Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
[Galaxy S III Android Development] franatic08:
Or enable the handswipe gesture in settings.
[Galaxy S III Android Development] SuperAce609:
Enable it in power menu with gravity box
[Galaxy S III Android Development] rchtk:
The installer said I should report at xda dev my impressions.

This ROM kicks a$$ !!

Thanks a lot for your time!
[Galaxy S III Android Development] Totemic_tHiRp:
I tried a lot of different Roms (99% of times with Stock-Based - I can't use my phone with buggy camera app and with bad quality), and nothing is compared with Archidroid 1.x. It's like AOSP system perfomance in Stock rom. It's really awesome.

But one thing is making me thoughtful... We all know that S3 won't get official Kitkat update. In other words, S3 won't be updated anymore. I also tested your port (ArchiPort) and QS port, and I liked both. So, the question is: [MENTION=5161352]JustArchi[/MENTION] , do you think to "bring" ArchiDroid 1.x to 4.4 ports? I mean, your work on 4.3 it's awesome, and see this on "stock" 4.4 would be much more awesome :D (Because a lot of users - like me - don't want to use aosp roms due some bugs like camera, battery drain, etc, and think it's "unacceptable" to have our S3 with buggy and bad quality camera, for example).

I'm just curious, because it's a little bit scary think that ArchiDroid 1.x and other 4.3 stock based roms will "die" in this version. :silly:
[Galaxy S III Android Development] malachow:
And here comes the answer:

:)
[Galaxy S III Android Development] JustArchi:
As I said some time ago.

ArchiDroid 2.X offers cutting-edge AOSP experience, is based on CyanogenMod, gets better over time but due to our crappy Exynos family it will never get close to what ArchiDroid 1.X offers, especially in terms of closed-source proprietary drivers, such as camera, bluetooth drivers (including headsets), or hw composer.

ArchiDroid 1.X is proven to be rock stable, bloat-free, as fast as possible considering the Samsung framework and really well-made.

ArchiPort simply doesn't satisfy me, it doesn't fit. It requires much more work to be done, and even with that I don't think that it'll come anywhere close to what we currently have with AD 1.X. ArchiDroid 1.X is my daily ROM, because it has excellent battery life, it's fast as hell and ultimately stable. I DON'T want to sacrifice it for unstable WIP port, which is nowhere close to that.

Currently I see no point in using AP, and probably I never see one. If you want stock stable experience, you have AD 1.X, if you like living on the edge, you have AD 2.X. ArchiPort doesn't offer 2.X's speed or cutting edge, neither AD 1.X's battery or stability. It's like throwing all advantages of my both ROMs for no reason, just to have something that works.
[Galaxy S III Android Development] kas0009:
If you have time make new release v 3.x
[Galaxy S III Android Development] t24ever:
Agree ..

I totally agree regarding 1.X

Tested a bunch of Roms but always restores my ArciDroid

The speed, stability and battery life is unbeatable
[Galaxy S III Android Development] szotaa:
So right now no kitkat theme at all? I mean removal of AOSP theme = removal of Kitkat Revolutionary theme?
[Galaxy S III Android Development] AssassinGEO:
I agree about 1.x AD,but disagree about that bad instability of AOSP. For me,it was pretty stable for the time being on it (5 months). The only instability I had was SystemUI crash once-twice a day. Also,the camera was amazing,I have some pictures taken and quality never bothered me (but,yeah,stock one is still better). Games were running even smoother on AOSP (ex. is Real Racing 3. That thing lags BADLY on my stock 4.3).

The reason why touchwiz works is just because it's done by samsung,but I would disagree about it being perfect. 4.3 is the worst touchwiz update for our S3. Yesterday,I held S3 with 4.1.2 installed and used it for 10 mins. God,that thing rocked solid. So smooth,so fast,response is fast,animations are so fluid. What is funny most is that the girl bought that S3 just after it came out and done only one format,and never touched anything since then. She just doesn't know this stuff like rooting,custom launcher and etc,so everything was stock and phone was unrooted,and I was amazed... Phone worked better than my ultimately configured 4.3 to get the smoothness,but after using stock 4.1.2 without any modifications,I still understood that my phone was far from the fluidity and speeds of that phone which was bloated with stock apps and etc.

So,again,4.3 sucks,to be honest. But oh,well,it's stock,so it's still considered as the best choice for our S3 for now.
[Galaxy S III Android Development] Totemic_tHiRp:
Exactly. Sometimes I think about back to 4.1.2 Stock or try a Stock based 4.1.2 rom. We (S3 Users) complained a lot of Samsung because they launched 4.3 on S3 very late, and also because they "skipped" Android 4.2 on S3. And when they launched, it just transforms S3 from smooth phone to a laggy phone. In my opinion, it's unacceptable to use Stock 4.3 with that perfomance. So, here am I, using Archidroid to save me from the lags.

unfortunately I came to this conclusion:

CM, AOKP, PA, Omni or any aosp roms: Awesome perfomance. Battery not that good and bad camera quality. Also, bad sound recording in video and voice. (One day I recorded a racing car and sounds terrible compared to Stock). But, the most updated Android.

4.1.2 Stock = Works very good. The SIII that we always loved worked like this. Good base to custom roms but outdated Android version.

4.3 Stock = Stock is terrible. Much more lags in UI, the classic wake up lag and (the more stupid) music lagging when screen is locked, for example. For daily use is annoying due the lags.

4.4 Ports = Works good. Remembers me 4.1.2 in performance aspect. Battery it's isn't good as 4.1 or 4.3, and this can be a problem.

So, what I'm trying to say is: I'm stuck on 4.3 at the moment. AOSP frustrates me by the camera and battery, but is much better in speed. I know someday we won't have more ports and I'll use aosp - until I update my phone -, but, I really miss the 4.1.2 perfomance. Even with stock bloated rom.

Btw, can I just download a custom 4.1.2 rom and flash it normally with philz recovery and everything "from" 4.3? (yes, it's a noob question, but, I've seen some people having problems when did this - i don't know why).
[Galaxy S III Android Development] AssassinGEO:
Ofc not. If you don't have EFS v1 backup,then you already will hit some problems. But you will need to format your S3 completely and do a fresh start,that's for sure.
[Galaxy S III Android Development] Totemic_tHiRp:
yeah, I know. But, my modem it's the same as the official Stock from december 2013 here in Brazil, and the efs format it's the same as the last 4.1.2 here (yes, I back to 4.1.2 from 4.3 someday and worked normally).
[Galaxy S III Android Development] JustArchi:
Not really, EFS V2 was introduced in XXEMG4, which was on 4.1.2. Flashing XXEMG4 or any later 4.1.2 software will result in no EFS problems.
[Galaxy S III Android Development] Totemic_tHiRp:
true. I had problems with this one day. I was with efs v1 and tried a custom stock based rom which has XXEMG4 modem (the rom does'nt have aroma or any option to don't change modem). The rom had some bugs and I decided to back to stock. So, I flashed stock rom in Odin and the efs problem appears. I searched a lot and found several methods to "recover" imei. Due the fact this problem was a "mistery" in that time, I tried a method who I deleted my EFS folder...................... Solution: Technical Support. Only months later I discovered that I was able to solve my problem just flashing a stock MG4 rom in my phone, but, you know... Making mistakes we learn.

So, technically, If I decide to flash a custom stock based 4.1.2 in my phone, will work normally? And what about modem? If I don't change my modem in aroma installer, will work a 4.1.2 rom with 4.3 modem?
[Galaxy S III Android Development] gabyif:
ArchiDroid has no version based on Android 4.1.2 right? :(

Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
[Galaxy S III Android Development] JustArchi:
It had, 1.5.X :).
[Galaxy S III Android Development] malachow:
Ohh, those days.. :angel: :highfive:

Over a year with a AD on a board & forum support, that's not a considance. That was, is and always will be intended & proven to be the best choice ever. :cool:
[Galaxy S III Android Development] satudarah:
re

Hello Guy's

i,m new here on xda. so don't blame me for noob questions.

i have a S3 I9300 running on stock 4.3 and stock kernel

like everybody have problems with battery and ect..

wanna know with this rom the stock camera and video recording work, because i need them for my work,

regards..
[Galaxy S III Android Development] malachow:
Works like it should work. ;)
[Galaxy S III Android Development] gabyif:
Excuse me [MENTION=5264108]malachow[/MENTION], do you use AD 1.5 as daily driver?

Sent from my GT-I9300 powered by ArchiDroid+ArchiKernel
[Galaxy S III Android Development] malachow:
No, sir, of course not. I would be mad if after so many updates and improvements given from Archi to his masterpiece I would be still using outdated 1.5. :)
[Galaxy S III Android Development] emanuelparedes:
I've flashed this ROM today, and I'm loving it, so far. One major problem, though. The camera doesn't work.

When I open the camera app, I get an error (something like "error connecting to camera") and the app closes. I also tried Instagram, and I get the same error.

What can I do? :s
[Galaxy S III Android Development] ezhilmxlock:
Same here .. Pls help
[Galaxy S III Android Development] gabyif:
No problem here,try to reflash the ROM with full wipe
[Galaxy S III Android Development] JustArchi:
1.2

- Updated Shark and Yank Kernels

- Added Siyah Kernel

- Removed Adam Kernel

- Removed even more bloatware

- Fixed google store (via MrxSiN) & I've also managed to fix this issue even better through special xposed module, it's universal now. Please point directly to Q&A for more info about 280dpi playstore fix.

- Fixed problem in my aroma script with some kernel options.

- Updated bootloader flashing code a bit. Also it doesn't work for some reason (flashing a bootloader works but it's reverted back to default after reboot). I'm investigating this issue but it doesn't cause any problem, even if you select such option.

- I've temporarily added custom perseus config but it'll get overrided after next boot. It's just a simple test feature.

- More to come!

Experimental: ArchiDroid 1.2 GD

If this version won't have any other issues then I'll eventually upload minor 1.2.1 (bootloader fix + perseus config) and mark it as next stable.

Have a nice flashing!
[Galaxy S III Android Development] galza:
Thanks my friend just downloaded to my phone and will flash asap :)
[Galaxy S III Android Development] JustArchi:
It's quite silent today :).

So I guess everything works fine :fingers-crossed:
[Galaxy S III Android Development] galza:
yep,just installed it in 280dpi with nova and arrange my stuff (a lot of work) and working really good and i tried to fix the play store problem like you said with modules but still facebook cant installed but its doesnt matter because i installed it through aroma so no big deal,the other stuff worked :D still need to set the rom as i want it and after that nandroid backup so all will be fine.

oh by the way 1.3 is on the way heheh :laugh:
[Galaxy S III Android Development] jezmll:
Hi mate looking very forward to flashing your rom some time this week seems very promising. Keep up the good work :)
[Galaxy S III Android Development] JustArchi:
Did you follow my advice from Q&A? I've personally tested it and it works just fine. You just need to open Xposed, click install/update, then activate playstore fix module (tap checkbox on modules page) and reboot the device.

BTW Nova has a very nice feature to "save" current homescreen, so you can use it for later :).

EDIT:

I've updated DPI Q&A to provide even more details:

It should work like a charm :).
[Galaxy S III Android Development] anthonys2r:
Downloaded! Will check this rom out in the next day or two, looks promising!
[Galaxy S III Android Development] megapinky:
Hi, for the lock screen disaligned we need to wait for jkay, or theres is a fix?

The rom looks nice but little problem on 240 icons

Crossbreeder gives me problem, it freeze if you select none and after select crossbreeder

:)
[Galaxy S III Android Development] galza:
oops!!

just found out today when receving a call i dont get the speaker option?! thats a big issue for me.what can i do? :(