yashsingh1/xdaforums huggingface dataset:
[Samsung Gear VR] TheDynamo:
Sent mine back. Like being an early adopter but as others have said not enough new content and also the SDE annoyed me and the fog that constantly filled my vision lol.

I will stand on the fence between Oculus rift and the HTC one ;)
[Samsung Gear VR] samipower:
But for example MX Player Pro v1.7.41.nightly.20150703 DTS & AC3 can play ac3 sound without problem in exynos-lollipop

Recompile this plugins for oculus cinema app ?? and replace in data/app/com.oculus.cinema//lib/arm ???
[Samsung Gear VR] MacInTheNet:
Hi guys : )

Nothing yet for Lollipop on a Note 4, right?

Thanks :p:p
[Samsung Gear VR] riso123:
I've manually edited the media_codecs.xml file on my s7 and placed the .so files in the relevant folder, as well as lib64, but this made no difference to anything I'm afraid.

Its a shame, but not a show stopper. Would have been nice to watch all movies natively on the VR headset is all, without needing to re-encode them.
[Samsung Gear VR] Lukephua:
HELP!!

Anyone running Exynos 6.0.1 for the S7 edge can upload their 'original' codex here?

I replaced mine over without backing it up and realised it doesn't work!! Can't even play regular movies now.. no more VR!!

Please help!
[Samsung Gear VR] Netricho:
Hi, i also f*cked up, without backup. But i could manage to work again. I have a custom ROM (Audax Plus M 1.3)

So, i simply opened the ROM's .zip file which i downloaded, and installed before, and searched for the original " media_codecs.xml " in System/etc.

Then copied to the phones directory ( system/etc ), reboot, and thats it. It works again.

So, if you have also a custom ROM then do the same.

(If you have, delete those two files ( libsac3d.so & libsomxac3d.so ) in the folder system/lib.)
[Samsung Gear VR] Lukephua:
Could you upload them here for me in a zippy?

Thanks mate
[Samsung Gear VR] AGPPC:
Here you go , make sure to change the permissions of each file to 0644 using total comander.#
[Samsung Gear VR] Quet5490:
is there a working solution for the S7? my last try ended with a bootloop...
[Samsung Gear VR] Lukephua:
Follow whats up there mate.

Make sure to change permissions <--- this is vital.

And delete the other 2 files.

Reboot and it should work fine.
[Samsung Gear VR] Ezzine:
https://github.com/dtsinc/DTS-Eagle-Integration_CAF-Android-device-qcom-common/tree/master/media

Can anyone with field knowledge confirm whether this xml codec file, would work on android to have access to DTS codec?
[Samsung Gear VR] lvnatic:
This method doesn't work for me. I edited my original media xml file - solved nothing, I then replaced it with the one from op - solved nothing. I added the other two lib files in system/lib - solved nothing.

Is there any updated root method to add this codec on a s7 edge running marshmallow please?
[Samsung Gear VR] lvnatic:
Anyone?
[Motorola Droid 3] Josephdbrewer25:
Ok I have searched the forum for a way to root without having a pc and nothing came up but I found an app that did. Is is safe to not use the rooting mothed for this phone??
[Motorola Droid 3] sd_shadow:
That's really not the concern.

The question is: Is the app, that you found somewhere on the web, safe?

Did the Dev include malware, spyware, adware, keylogger....

If the app is not open source, there is no guaranteed way to check.

The other questions is, does it root the device? That is fairly easy to check use Root checker

---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------

I have requested that this thread be moved to Q&A
[Motorola Droid 3] Josephdbrewer25:
reply::

It rooted the phone. I used safestrap and install ICS. The app wasn't fully in English tho. Part of it was but mostly in something like Chinese or Japanese or something. I really don't know if it had a virus or anything but it did root the phone.
[Motorola Droid 3] corby2geek:
Can you post the app ?

Thx
[Motorola Droid 3] andone87:
For example: framaroot, towelroot
[Motorola Droid 3] sd_shadow:
guessing Rootmaster http://xdaforums.com/showthread.php?p=50863317
[Motorola Droid 3] corby2geek:
Thanks :)
[Motorola Droid 3] Josephdbrewer25:
Here ya go
[Motorola Droid 3] Josephdbrewer25:
Don't really know the name. It may have been root master.
[Motorola Droid 3] Josephdbrewer25:
That link said file not found btw.
[Motorola Droid 3] sd_shadow:
last post in thread
[ONE Q&A, Help & Troubleshooting] Kildimo89:
I am returning my device to OnePlus due to an issue the phone had since I bought it, however for the short time I had it I tried a custom ROM and also then flashed back stock CM.

I am currently back to stock 44s, however once I wipe the device and return it what happens in regard to the unlock state and tamper bit? I re-locked after flashing but can OnePlus tell by this tamper bit it has been flashed and possibly use it as a way of avoiding warranty?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Unlocking the bootloader doesn't void your warranty. By their own statement you can do whatever you want to the device and it'll be covered by warranty, as long as you don't brick it. What is the fault?
[G4] jerome31000:
hello i'm noob with G4 or G3, ive got one G4 device, but i do unlock the provider code, is it now a G4 unlocked, or is there another method ?:confused:
[G3 Q&A, Help & Troubleshooting] pswatts7309:
I just recently rooted the question is will I still get the 5.0 update when it comes out
[G3 Q&A, Help & Troubleshooting] keithleyson:
Yes you can. You will lose root.
[G3 Q&A, Help & Troubleshooting] meyerweb:
It's not that simple. If you still have the stock recovery, and haven't deleted any of the built-in apps / bloatware, then the OTA will probably work. If you've installed TWRP, or deleted bloatware, the OTA may fail to run. Or, worst case, the OTA will attempt to install but soft-brick your phone.

It's never a good idea to accept an OTA if you're rooted. Either restore to stock, then take the OTA, or wait for a rooted version of lollipop to install. If you accept the 5.0 OTA, you'll lose root, and it could be a long time before 5.0 can be rooted on this phone.
[Moto E Android Development] prince trishi:
Nice work :d

Good to see new ROM coming up!!! finally something new.....

Downloading for MOTO E (XT1022) will test and report it ASAP!

Thanks for the ROM dev!!
[Moto E Android Development] GeekyDroid:
You're very welcome! Thanks for testing the Dual SIM feature. :)
[Moto E Android Development] iTudorS:
how about battery life? :)
[Moto E Android Development] KagamiNator:
Zip file is corrupt, please fix it
[Moto E Android Development] gtsfreak:
Awesome ROM used on my s3 very good ROM will try soon for moto e :D:thumbup:

Sent from my GT-I9300
[Moto E Android Development] Zeroemd:
Thank you for taking my suggestion, I am eager to try it but the zip file is corrupt. I have tried using a download manager and chrome and both times it shows as corrupt. please reupload it.
[Moto E Android Development] paul vity:
The zip is corrupt, please re-upload the rom

Thanks

Enviado desde mi XT1021 mediante Tapatalk
[Moto E Android Development] marceloterorist:
Holy Mother of all God. How many features this ROM have? XD

I will test this ROM too in my XT1022, when the OP has get the link working.

Meanwhile, good work. It's very good see new ROM's here.
[Moto E Android Development] VeerAmrit:
Thanks a lot for bringing up a new ROM. Will give it a try and later a review.
[Moto E Android Development] magdeoz:
Plz re-upload the ROM ?
[Moto E Android Development] VeerAmrit:
Tried to flash it, but it says corrupt. Please re-upload it again. Thanks again.

EDIT : aosb_kk_1.3.7_condor.zip: CRC failed in META-INF\com\google\android\updater-script. The file is corrupt

aosb_kk_1.3.7_condor.zip: The archive is corrupt
[Moto E Android Development] Prashanth Meesara::
Glad to see your first ROM for moto e , and I will test it soon
[Moto E Android Development] GeekyDroid:
I'm using it till yesterday and if you use Greenify to hibernate some apps like Whatsapp, Facebook, etc. then the battery life is awesome! :)

Sorry guys! It's my net speeds fault! :rolleyes:

Will reupload now! The new link will be available in an hour or so! :good:

Yeah, also had flashed this ROM on my S3 :D

Nice to see a S3 member here :D

Welcome! Don't worry it will be re-uploaded soon. Then you'll be able to test :)

Yeah, a really feature filled ROM! ;)

Thank you!

Welcome! :)

Thanks brother! :cool:
[Moto E Android Development] GeekyDroid:
Okay guys!

Now it is ready and should be working fine! Links are updated. Feel free to test it now! :)

Oh yeah, all XT1022 users please test Dual SIM feature!

Thanks!
[Moto E Android Development] Deleted member 5225837:
Constant system ui fc on xt1022.

But I liked the bootanimation. Its cool.[emoji6]
[Moto E Android Development] GeekyDroid:
Okay, thank you for testing. Will fix that in the next build!

Seems like Dual SIM isn't applied on the Statusbar. Because on mine it is working fine, as I'm using XT1021 which is single SIM(no FC obviously). It is fixable! Need to do some research.
[Moto E Android Development] Rio257:
Not working in XT1022 System ui force close simultaneously

sad news for XT1022:crying: and good for others:D
[Moto E Android Development] lokesh.3440:
Oh.I really loved Aosb ROM on galaxy tab 2. Hope [MENTION=225651]op[/MENTION] will fix it soon
[Moto E Android Development] GeekyDroid:
Good news for XT1022 users!

I fixed it in build 2. It's currently uploading(15%). :D

Don't worry XT1022 guys, you will get a working build within an hour or so! :good:
[Moto E Android Development] VeerAmrit:
Thanks, for that.
[Moto E Android Development] :
Hang on

Geekydroid is updating it
[Moto E Android Development] Prashanth Meesara::
Waiting ....
[Moto E Android Development] VeerAmrit:
[MENTION=5225837]dhruvmu[/MENTION]

Yes I edited my post, that was a while back. Waiting! Cheers to OP!
[Moto E Android Development] iTudorS:
Le bug :)

Also I get constant systemUI FC after reboot. I mean: Install rom -> reboot -> SystemUI FC all time..

Edit, solved the FC of SystemUI, I deleted the app Weather and that causes FC, restored app and now all working fine :D
[Moto E Android Development] :
Hahahha[emoji23] [emoji23]

Thats some serious issue[emoji13]
[Moto E Android Development] GeekyDroid:
Just enable Apps and not cache in RAM settings.
[Moto E Android Development] paul vity:
Thanks for reupload

Good job

Enviado desde mi XT1021 mediante Tapatalk
[Moto E Android Development] Rio257:
Too fast sir thanks
[Moto E Android Development] KagamiNator:
Thanks for this awesome ROM! Works very well on XT1021, hope you can do more stuff for our beloved device
[Moto E Android Development] tugagear:
tanks tested en mi device

tested on moto e xt1023 us. tanks is a great rom excuse not to write much my English is bad :good:
[Moto E Android Development] GeekyDroid:
Yeah, I need some suggestions for new ROMs.

No problem!

BTW new build is up! All XT1022 users, please test this build now! :)
[Moto E Android Development] :
Is the 2nd build uploaded!!!

Download link shows b2.
[Moto E Android Development] GeekyDroid:
Yeah b2 means 2nd build. The SystemUI FC should be fixed now.
[Moto E Android Development] dchatterjee172:
[MENTION=5027322]GeekyDroid[/MENTION]

can i use titanium backup to to backup my apps and data...

and restore in this rom ?

currently i'm on cm11
[Moto E Android Development] Prashanth Meesara::
Anyone used the new build in xt1022? Everything working fine?
[Moto E Android Development] GeekyDroid:
Normally it should work fine as it has the same base. AOSB is based on CM11 so I think it should work! ;)
[Moto E Android Development] :
Tried the 2nd build. Still the same problem.[emoji20] [emoji20]

And for the suggestion would love to see dirty unicorn, liquid smooth and miui.[emoji16]

And thanks for the quick response.
[Moto E Android Development] GeekyDroid:
OMG! What?

Can't believe it!

How? OMG.

Sorry, for XT1022 guys, but I thought the patch I found would fix it. :(

Here is the patch: http://review.pac-rom.com/#/c/2146/
[Moto E Android Development] shobitm:
Force Close issue is still there.. Just tested
[Moto E Android Development] VeerAmrit:
Downloaded the second version. Still ui force closed.
[Moto E Android Development] shobitm:
Does it mean that you won't be working for XT1022?
[Moto E Android Development] GeekyDroid:
No! Definetly not! I would never drop support for XT1022! I'm just tired right now, so I'll continue with it tomorrow. It just means that XT1022 users have to wait till I fix that.
[Moto E Android Development] prince trishi:
Amazing!!! :D

Waiting for the fix bro!!! Would love this ROM to come up!!

Thanks again!
[Moto E Android Development] VeerAmrit:
Will it support single sim? If I remove the second sim from tray?
[Moto E Android Development] prince trishi:
Its not like tat bro!! you will still face the FCs!! just be patient until he uploads a fixed update for us!! he aint leaving the support for xt1022!! so dont worry! :)
[Moto E Android Development] shobitm:
Go On.!! Take your time. Will definately love this one..
[Moto E Android Development] Zeroemd:
Thank you for you hard work, maybe you should ask other devs.
[Moto E Android Development] GeekyDroid:
If someone of the XT1022 users could provide a logcat, that'd be great. Just flash the ROM reboot abd after it booted and the FC's are comming take logcat. Thanks.
[Moto E Android Development] :
[MENTION=5027322]GeekyDroid[/MENTION]

Unfortunately cant get the logs. adb shows device as unauthorised. seems USB debugging is not enabled by default!!

can't enable it manually bcoz of FC.

Any Workaround??
[Moto E Android Development] Yousef Algadri:
Thanks and Credits for this build :

percy_g2

JackpotClavin

Optima Team

ashwin007

XDA:DevDB Information

AOSB for Moto E, ROM for the Moto E

Contributors

GeekyDroid

Source Code: https://github.com/AOSB/

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Stable

Current Stable Version: 1.3.7

Stable Release Date: 2015-01-03

Created 2015-01-03

Last Updated 2015-01-03[/QUOTE]

It is for single sim?
[Moto E Android Development] :
[MENTION=5885640]Jawaad_S[/MENTION]

Don't quote the full op

Plz edit it.

The ROM is currently working proper on xt1021 but we are getting system ui fc on xt1022.
[Moto E Android Development] divyang vyas:
system ui fix

plz make patch for xt1022

and please port slimkat rom
[Moto E Android Development] :
Sorry bro but I don't have knowledge to build a ROM..[emoji16]

Geekydroid is working on fixing for our device. Have patience.

[MENTION=5027322]GeekyDroid[/MENTION]

Unfortunately cant get the logs. adb shows device as unauthorised. seems USB debugging is not enabled by default!!

can't enable it manually bcoz of FC.

Any Workaround??
[Moto E Android Development] GeekyDroid:
Delete SystemUI.apk in system/priv-app before flashing and then flash the ZIP. Now the ROM will boot without a SystemUI, so there'll be no FC but there will be also no Statusbar :p

Then you should be able to get it authorised.
[Moto E Android Development] :
But then if there is no fc!! And you want log for fc[emoji14] [emoji14]

Wait. I'll try something else.
[Moto E Android Development] dchatterjee172:
1st turn on usb debugging->authorize ..... then again put systemUI apk in priv-app and reboot.....

then you can take the log for FC
[Moto E Android Development] GeekyDroid:
Follow [MENTION=6045132]dchatterjee172[/MENTION] instructions.

Thank you very much, I forgot to mention that! Really smart. :D
[Moto E Android Development] :
Sorry Guys. Tried different things but i cant get the adb confirmation dialog box(Allow USB debugging mentioning computer id) on my phone while its working properly with other ROM.:(:confused:

Any one else can try.
[Moto E Android Development] GeekyDroid:
Yeah, please! It's really important to me. I cannot do anything without logcat right now. I tried two different patches to get it fixed and both didn't work. So now it's your turn. Without a logcat, this ROM stays stable only for single SIM users.
[Moto E Android Development] Zeroemd:
I cannot test as I have a single sim variant. Maybe there is a way to activate USB debugging vía build.prop.

I am from muy phone now, when I get home I will try to upload a flashable zip to activate USB debugging.
[Moto E Android Development] GeekyDroid:
I already said that guy but he said it is still the same. He get's unauthorised phone when he types "adb devices".

These lines should be added in build.prop:

persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
[Moto E Android Development] :
Yes tried this

Still not working!!
[Moto E Android Development] robsonsilva:
"systemui has stopped"

Does not work in xt1022 and xt1025 "systemui has stopped"
[Moto E Android Development] Raj1986:
Not working in XT1022 System ui force close simultaneously :(

Not working in XT1022 System ui force close simultaneously :(

Using latest build ..pls check
[Moto E Android Development] GeekyDroid:
Please read the thread before flashing or posting. It's already there in bugs section. Someone needs to provide logcat, but nobody wants to or cannot do it, so I can't help you. I'm using single SIM variant and it's working fine(also confirmed by other single SIM users).
[Moto E Android Development] benhu85:
logcat systemui FC issue

I am new to this debugging.

I will update the logs . Let me know if "alogcat" application will be fine for debugging the current issue. ? or suggest any other directly on device . "as i don't have admin rights on office lappy"

Will install this ROM on my XT1022 in evening:(. Now in office :o
[Moto E Android Development] Rio257:
Yes you can get logcat via app but due to msim layout bug create system ui fc so we cant even acces the device so how do you get logcat

Hence there is only way to get logcat is through adb command
[Moto E Android Development] benhu85:
logcat for systemui FC issue

hmm , then It may be difficult for me to study and generate it .

let me know if anyone has some basic steps . Can give a try .

regards

ben
[Moto E Android Development] GeekyDroid:
Do you know ADB?

First be sure you have adb installed on your PC. For this follow this guide until step 5. Then you can take a logcat by typing:

adb logcat -v long > name of problem.txt

After the ">" you should give a path i.e Desktop and a .txt file. I like getting logcats directly on Desktop that's why I type:

adb logcat -v long > Desktop/systemuifc.txt

It should look like this or something like that.

And if you don't get the device when you type adb devices then copy this to build.prop:

persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

Thanks.
[Moto E Android Development] marceloterorist:
What do you mean? Open the aosb_kk_1.3.7_condor_b2.zip, and delete the systemui.apk and then install the ROM? This don't get any error when trying to install? I will try soon a can get time and make the logs.
[Moto E Android Development] :
First check if you are able to get the device accessed with adb by normally flashing the zip.

If you r getting device access as unauthorised just as I got then delete the system ui.apk from system-priv app folder and then flash the zip.(remember you wont be having nav bar to navigate so better first add shortcuts to lock screen which will be beneficial to navigate) This will remove to system ui fc. After that try to get adb access and after getting it push the system ui.apk to system- priv app folder and then get the logs for fc.

Or even if this doesn't work add the lines mentioned by geekydroid in build.prop and then try to get the logs.

Unfortunately I tried both the ways but can get the access msg on my phone which I expalined in earlier post. You can try. May be it works with you.
[Moto E Android Development] ANDROmodderHD:
ROM is awesome

looking forward to using this rom, it looks so cool and has many outstanding features. Well done dev:D:fingers-crossed::highfive:
[Moto E Android Development] benhu85:
logcat for systemui FC issue

Hello ,

I tried , Used minimal ADB and fastboot ,Fastboot detects the device but ADB doesn't .

So i added "persist" code as mentioned above and prepared the zip.

Its saying "Error in flashing zip '/externak_sd/aosb_.........' --> for modified one.

Is this a proper method just to extract , change the build.prop and again zip it ? :rolleyes:

Thanks

Ben
[Moto E Android Development] GeekyDroid:
Just use WinRAR and extract just the build.prop, edit it and again put it into the ZIP and flash. I guess you have selected .rar as file and not .zip while compressing, that's why the error came.
[Moto E Android Development] marceloterorist:
No, not working. Same problem with "unauthorised device"... I get the logcat running, usb debugging working (for me he was activated by default, but adb can't connect or communicate...). Will try again other time with another method, changing the systemui with one by cyanogenmod, or anything more crazy...
[Moto E Android Development] linuxsociety:
Anyone tested on cdma variants like the xt1019?
[Moto E Android Development] nisu4717:
Op can you work on repaxperiS.

There is guide available too
[Moto E Android Development] benhu85:
First I tried with 7 zip both exncryptions as well normal store :( not working .

then tried using winrar too ,but getting same error message.
[Moto E Android Development] iTudorS:
I think I found a bug, the option of checking sensor before waking up the screen isnt working for me, I have D2W enabled and my phone wakes up with sensor covered, also it wakes up by button with covered sensor.

Sorry for my english I'm Spanish :)
[Moto E Android Development] GeekyDroid:
I guess that nobody tested it, but it should work fine, if it is dual SIM. Please test and report back.

As I said in general thread, no.

Please just drag and drop the build.prop. Don't unpack whole ROM and repack. That's nonsense.

Is it working in other bugs? This is maybe a feature which isn't included in the ROM. I will try to search on github. Are you on the kernel which is there in the ZIP or on a custom kernel?
[Moto E Android Development] iTudorS:
This feature was working on PacRom, aospa and CM11. I tried with stock and with furnace kernel on your rom and It's not working.
[Moto E Android Development] GeekyDroid:
Well, can you tell me the exact name of this feature? Then I can probably add this in this ROM.
[Moto E Android Development] iTudorS:
This one, under screen & lights menu. its there but it doesn't work.
[Moto E Android Development] GeekyDroid:
Well, the feature is already present. This should be a ROM issue. I don't know exactly how to fix that. You can try to search for some Xposed modules.

Gravity Box have this feature I think. Try installing it and enable it. If it doesn't work then there is some lib missing. (I missed to include it while building then.)
[Moto E Android Development] iTudorS:
With gravitybox is working, thank you :)
[Moto E Android Development] bryanchapman9999:
SMS

Anyone have a problem with receiving text messages?

Sending fine, can receive nothing
[Moto E Android Development] Hit Sappen:
I have same problem. I Can't receive SMS
[Moto E Android Development] bryanchapman9999:
Cool. Anyone else or is there a known fix??
[Moto E Android Development] GeekyDroid:
Hmm, just confirmed it now. Try some 3rd party SMS app, it may work.
[Moto E Android Development] bryanchapman9999:
Hi, tried stock and the google messaging also chomp.

Even called vodafone blaming them!

Reverted to a near stock ROM and all fine.
[Moto E Android Development] GeekyDroid:
Okay, then something is really messed up. Adding to buglist.
[Moto E Android Development] linuxsociety:
I've had issues with messaging myself but I have the cdma version (xt1019)

I fixed the problem by ensuring voice+ is frozen completely, and also some build.prop changes I can paste in here later but they are mostly cdma and us cellular specific so hate to paste them and someone screw there gsm phone up heh..

I pretty much have to use hangouts app for sms to work on here though.

I've not been able to get the default aosp messaging app to work right but I'm a Google voice user also so hangouts works fine for my particular needs.