Database Info

Problen in xdandroid

I have a touch pro, I'm trying to use the xdandroid, but all the versions he has a great sensitivity on the keys below the screen, where it has four buttons plus the round, and all I gotta do it changes the screen to be clutching automatic these buttons, I've tested on 2 htc touch pro and the same thing, has to be clean this area not to activate the buttons, have any setting to disable this?
Sorry my bad english!
Obs.: posted here as to post in the area of the android must have a minimum 10 posts

I'm guessing you are talking about how the button lights go crazy and a means to disable those buttons. To my knowledge, there isn't a way around this. Also, I haven't notice my buttons on my Fuze/RAPH110 going crazy since FRX04. Then again, I am also constantly updating files such as the rootfs and kernel packages. Just out of curiosity, which version of XDAndroid are you running? Yes, there are a total of at least 6 versions now, to include a Gingerbread alpha version.

Now i use http://files.xdandroid.com/GBX0A_Full_Bundle_11.3.2011.zip
What your version?

Keep in mind the Gingerbread port is still in the alpha phases. Somethings will work and other things won't. I use FRX06 because it is more a complete port but even it has some bugs. You can download the full package or just the system. I am also testing various kernel packages to see what works(for me); what's broken and the sort. I would also encourage you to download the ts-calibration file found in the FRX06 thread (first post). Till you figure out how it works and what you can do to change your experience with XDAndroid. Additionally, once you download the ts-calibration file, you'll need to extract it and place it under the same folder/directory as haret. Should be \FRX06\ IF you extract the full package as is.
If you encounter any problems, it is suggested to start over with a fresh microSD(format FAT32 with something other than windows) and push everything up one dirctory. So, if everything is under \FRX06\, cut and paste the contents under that folder to the root of your microSD. The folder is there to organize the builds; for those who run multiple builds or have more than just FRX06 on the microSD. XDAndroid is supposed to run regardless but if you do encounter any problems, that is just one of the many work arounds or solutions to try.

Thank you for answers, my biggest problems are that the button, the high power consumption and catch him and have to give a reset

Yeah, the battery issue has always been a pain. Though, it surely is better now than the 1 hour(and less) run time we had when this project first started! Some report a whole 8 hours, I have yet to see it but not saying that it couldn't happen. I suppose I could turn off the extra services such as sync and weather updates but then I'd be running a similar setup as winmo...
What everyone has to realize that with added availability, comes added problems. Especially if you aren't usually running google sync and other background data services 24/7 while in winmo!
Keeping in mind, I usually get a little longer(maybe 12 hours?) run time while in winmo. With data running in the background 24/7, a couple dozen txts and an hour at the most of talking per day. So, I remain unconvinced it isn't our devices that is the actual problem...

[Q] Changing the boot sound on a Nexus 7 running base Android

Hey everyone!
Long story short, I have a Nexus 7 that is running base AOSP, version 4.2. I've managed to change the boot animation with relatively little trouble (took way too long to realize I needed a damn newline at the end of the file), but I'm a bit stuck on changing the boot sound. Or, more specifically, adding a boot sound, as there was none before.
I've found all kinds of tutorials that said all kinds of things (put PowerOn.ogg in /system/media/audio/ui/ which makes the most sense to me; put PowerOn.wav in /system/etc/; other such things) and none of them worked. I suspect it may be because no market devices use this bare-bones version of Android, and there's some trick to enabling this functionality, but really, I don't know.
I'm not sure how many people out there have had experience with this, but any advice would be appreciated.
Thanks!

For the benefit of future generations, I have determined that the only way to enable this is to do so before the image is compiled by changing some default config files in the ROM. So if you have an image that doesn't support boot sounds, you're out of luck, unless you have the liberty to rebuild it yourself.
Granted, I still have yet to accomplish this goal, as the boot sound still won't play, but I think this has to do with the sound device being unavailable at boot time. I don't know if this is the case, but my experiments indicate that I can't play sounds with stagefright as early in the boot process as I thought.
Just figured I'd jot this down for anyone in the future who finds this thread and needs help.

[Q] CM10.1 Lockscreen & Multi Folder

(I'm currently on the 2/19 Nightly)
I posted this in General a couple times but don't think I ever saw an answer. Is lockscreen rotation currently MIA? Ever since 4.2, I don't have it. If so, is this a known issue? I could not find mention of it on the CM bug tracker. Additionally, if there are those of you that have lock screen rotation, please let me know as then I know it's me, not everybody.
Secondly, I had read about this before but I don't know what the proper search terms would be. As I understand it, w/ multi-user support, multiple SD folders (?? I think; SD/0, SD/1, etc) are created but multi-user support is not/will not be available for phones, just tablets. I thought I had read somewhere that this cause confusion for some users.
I've lately had some folders disappear, as well as had errors installing apps due to "storage space insufficient" warnings. I've got a 16G SD card installed and not really a lot of stuff on it so space shouldn't be an issue. What I've found is folders that I should have that contain pictures, as created when installing an app instead of user created, are not available, say, thru Gallery.
All that said, I'm not sure if the process of creating all the folders was something that could be "fixed" or remedied and so what I'm asking for is either a link to discussion on this topic, or if you're feeling less generous than that, just the proper search terms and I'll scour the web and XDA.
I just don't know how this is generally referred to and not knowing the correct search terms makes finding the relevant information more difficult.
Thank you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

USB mic on Android?

G'day guys and girls. I'm a bit of an audiophile and like to create my own speakers for home theatre systems and I do custom installs in my car to compete in sound quality comps.
For the tuning of my system I use a USB condenser microphone designed for this purpose, plugged into laptop and using various programs.
However I want to make a more portable solution that will run through my Samsung note 10.1 (older model). The problem is though, usb microphones aren't supported,and the one app out there that has gotten them to work, only allows it to be used within the app to do recording, not real-time-analysing on other RTA apps.
I read somewhere that you could possibly recompile a custom kernel with the appropriate Linux driver installed, but then I read somewhere else that the app you wanted to use would also need to support the ability to select the usb microphone somehow.
Then I came accross this website
studiosixdigital.com/audio-hardware/usbPrecisionMic. html
That makes mention of apps that support usb audio input, but doesn't mention any names of these so-called apps.
I have not modified anything on my android devices before so know little to nothing about what is required.
Before I go trying to recompile the kernel with the Linux drivers in, can someone confirm if it'll be a waste of time without the ability to select which microphone to use within the apps themselves, and if so, are there any apps out there that can do this?
The RTA app I would like to use is Speedy Spectrum Analyser and it allows selection of front or default mic, so would the option for usb mic come up once connected?
Sorry for long winded post, but it's something that has bugged me for a while now and I was hoping new versions of Android would solve this for me

Nothing? No one can suggest anything?

Just to clarify, I'm not expecting anyone to do the work for me, I just want to know from peoples experienced opinions if they think it'll be possible for an app to choose the microphone if I do manage to recompile the kernel with the correct driver

[WIP] 100% Native Android 6.0 TMO ROM

Greetings,
I am currently working on a 100% Android Marshmallow v6.0.1 variant for the Samsung On5 SM-G550T/1 (T-Mobile).
THIS IS NOT A THREAD ON HOW TO ROOT YOUR PHONE
This thread assumes you have already rooted and installed TWRP on your phone and have basic understanding on to backup and recover your phone.
If you need that sort of help, please see my other thread:
https://goo.gl/jWNVNX​
Reasons for Project:
I started this project for two reasons:
- Frustration for the lack of support for an otherwise great phone.
- Stumbling across the Samsung Factory Test Rom doing research for other projects.
This ROM has a a 100% Native Driver Set for Android v6.0.1 on the SM-G550T/1. The driver set is identical for the TMO or MetroPCS variants, but the EFS folder will remain different for each.
I'm going to outright confess that I am not a programmer and this is truthfully the first ROM I am trying to develop on my own. I'm a Project Manager and Software Designer by trade, but I rarely get this deep into ROM developments. I figured it was a good project to take on to learn the nitty griddy of what a truly pure Android Experience looks like. That being said, I'd greatly appreciate any help anyone can contribute and will make all my work freely available to anyone wanting to help provided that everyone participating goes into it with good faith that they have no intent on making substantial gains from this project.
Usage of these ROMs/Files/Programs are subject to the following licenses:
- Google's Android Open Source Project Licnese (AOSP):
https://source.android.com/setup/start/licenses
- Google's Individual Contributor License Agreement:
https://cla.developers.google.com/about/google-individual
- Apache Software License, Version 2.0
http://www.apache.org/licenses/LICENSE-2.0
- Samsung Open Source Release Center (OSRC) License:
http://opensource.samsung.com/reception/
That being said, I believe this remains a good enough device, IMHO, to transition people into Android or to provide to people not requiring a fully featured phone.
KNOX Status:
The Factory Test ROM is mostly clean having all the drivers intact and lacks most Samsung Bloatware "tampering". It *DOES* have some preliminary containers for KNOX installed, but none of it is active and takes up less then 1 MB of total space after cleaning passes to remove as many traces as could be removed without breaking things. It is currently being "managed" by an init.d script that generates the folders. I haven't been able to track down yet.
Known Issues:
- 100% Pure Android Menus.
- Rooted/Super User.
- Sound, Camera, GPS, TMO Modem, Wifi, Bluetooth 100% working.
- 100% Native Tethering.
- Adblocker pre-installed (for both Apps and Websites).
- The smallest amount of KNOX installations outside of Lineage. >1mb of KNOX is present with the only items being present are installer containers.
- I'm trying to track down Init.d files that loads with Android and automatically disables/flushes WIFI.
- By default, the power button is set a 100ms push time to turn off (not show power menu). I'm trying to figure out a work around for this.
- I'm trying to find a compatible Contacts Storage file.
- There is no shutdown menu.
Please note that any released versions of this ROM will have makeshift ways to get around these issues.
Downloads:
Please see the second post in this thread.
How to Install:
#01.) Backup your device.
#02.) Download the zip file for the TWRP backup.
#03.) Unzip the TWRP backup.
#04.) Load the downloaded restore into your TWRP Backup Directory.
#05.) Boot into TWRP Recovery.
#06.) Restore the ROM copied into your TWRP Backup Directory.
#07.) Reboot.
Note: No personal data has been configured.
References:
Update Log:
https://goo.gl/CEGCx9|
Required System Apps for Samsung Phones:
https://goo.gl/emTvgX
Things I Could Use Help On:
- A very good way to figure out what Init.d files are doing what without reading through them.
- A good way to change the PIT so we can move 2 gig from the System Rom into the User Rom space.
- Easy methods for changing key button presses.
- A shutdown menu setup.
- A way to make this into an installer.
Note that all those things I'm working on ALREADY, but suggestions would be helpful.
Thanks in advance for any help anyone offers.
Donations Welcomed:
Dev elopement of this ROM is timely, I appreciate any contributions you wish to provide.
https://goo.gl/esVVqA

DOWNLOAD LINKS:
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Google
https://www.androidfilehost.com/?fid=1395089523397913770
- Note, due to Google Now being installed on this one, I can't configure the home long press as the restart menu.
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Diagnostics
https://www.androidfilehost.com/?fid=1395089523397913771
[2019-03-02] Android [v6.0.0] Build #10F [RC]
https://www.androidfilehost.com/?fid=1395089523397908668

i would love to test this rom

Its been taking a little longer then I expected to get it working correctly --- I've been having trouble tracking down some bugs, but with a little luck, I'll post the Google variant tomorrow.

Here is a "working" version to look at:
https://www.androidfilehost.com/?fid=1395089523397901430
It's a restore for TWRP (not an install).
It has all the aforementioned bugs, but is pretty clean only with a few basic utilities installed on it.
I'm trying to track down a number of things:
How to change the Power Button function:
In my most current build, I have made the power button simply put the device to sleep with a long hold of the home button bringing up the power menu. I can't for the life of me figure out where the power button menu lives at or how to define it.
Normally, you'd go edit /system/usr/keylayout/Generic.kl, however, editing it button 116 (the power button) for "Power" only makes it turn off. I can remap it easily as sleep. I compared several other ROMs who use the exact same parameter.
My current version, I just use an app to remap several of those functions; but I don't feel like that's a "release worthy" fix.
Factory Mode:
I can't figure out how to get this version of the ROM to get out of factory mode. The only real problem this causes is, on bootup, it will display a message saying as such and then disable WIFI and turn off the sound. Both, of which, can be immediately be turned back on. It also disables power saver modes.
At first, I thought this was an Init.d file, but after doing some digging I determined this has to the /efs/factoryapp/factorymode file. I may need to swap elements from another EFS to get this fixed.
Contacts Storage:
This is another one I can't seem to track down, but I have a working idea how to fix it. At current, anything that uses Contact Storage won't work. I wonder if the contact storage I have on the system is simply incompatible for some reason. I'm going to try to pull over those system apps from another working rom.
Storage
I've mapped out all the partitions but am having trouble figuring out how to actually change the partitions. There is a whole 2 GB being wasted on the system partition. I'm actually very surprised that no one has ever released a rom with this fixed.
I've tried using parted, but my ADB Install is messed up something major and I cant track down that problem. Reinstalled ADB hasn't fixed it. Its largely a PC problem on my end; a problem I'm dragging my feat going and trying to fix. This is an issue I REALLY wish I could use PC tools for :-\. I've done these changes a thousand times on Windows based machines, but never on a Linux based OS.
Now that I think about it, maybe I should try doing this from the terminal prompt in TWRP. I just wish the keyboard in TWRP didn't suck :-\.
Other Thoughts:
Beyond those very vexing bugs, I have to honestly say that I feel like this experience on this rom is vastly superior to that of the stock Samsung Experience. Sure, these issues are vexing, but I'm also seeing much less system overhead (CPU usage, RAM usage) with this Rom then anything else outside of Lineage.

Update
Here's an update for everyone who might be interested:
The last couple of week's I spent an ENORMOUS amount of time trying to track down as much as I can to get this ROM to work as intended.
For those interested, I've developed a completely new spreadsheet describing everything that's bloatware versus needed items:
https://goo.gl/emTvgX
This spreadsheet will probably be handy for EVERYONE working on Samsung related devices. When its a little more clean, I'll throw it some place better; but since this is specific towards this device, I'll keep it here for now.
It describes everything in /system/app/ and /system/priv-app/ in Samsung's default install and which of those items are actually needed for a 100% clean Android Experience.
I've also rolled through the architecture and have cleaned a lot of "junk" out of the system. Overall, I've pulled it the system from around 1.3 gb installed all the way down to about 800 mb and still feel confident I can trim more out of it.
I've also made it a point to install as much updated system apps as possible. Its been a game of juggling Google, Samsung and other ROM apps to find what works. In general, there are only one major programs left that are Samsung based in any way and that's the Samsung Phone Service app; which seems like its required to interface with the specific hardware on the phone. I've tracked down a number of native Google teleservice.apk-s and none have worked to date.
I am, sadly, still having the aforementioned problems:
- Contacts won't sync despite being able to connect to the contact services and seeing what backups are available. Manual restores work and updating contacts TO the server works now.
- The Power Button turns off the device immediately. The problem resides in a configuration somewhere that's telling the "Power" function to not bring up the power menu. The power menu is in the system, but appears to be renamed or something. I'm having trouble tracking this down. For documentation sake, in theory you should be able to just go to /system/usr/keylayout/General.kl and edit button 116, but that doesn't work.
- The phone is still locked into "Factory Mode". Various documentation says that if you go to /efs/FactoryData/factorymode and edit the contents to "ON", it should resolve this issue, but it doesn't. I feel that the problem resides in the CSC folder and EFS folder, but I haven't gotten around to testing yet. I suspect if you swap the CSC and EFS folders out and set all the correct permissions it might fix that. As it stands now, however, its only a minor inconvenience.
Overall, there's a lot more junk to sift through on the last two problems. The first problem I am kind of stumped on.
If you want to download the ROM and look at it or run it, you can follow the below link. It's currently setup with my "trouble shooting environment" making key places to tinker with easily accessible.
DOWNLOAD HERE:
https://goo.gl/MuPqE3

@LighthammerX
Im very grateful for this site where we can come and learn from one another. I just wanted to say thanks for taking time to work on this device and then sharing your findings. I've been using my on5 for 2 months now after other device died. I'm in the process of moving now but once I'm done with that I'm going to scope out this bad boy and see if I can figure out a few things. Appreciate you sharing your information with us all. Cheers.
Sent from my on5ltemtr using XDA Labs

Thanks. I'm glad to see there's some interest here. IMHO, with the right setup, this little phone is actually a very nice device today.
I actually took a lot of what I learned from hack this ROM apart and applied it to Super Starz to get it running a lot cleaning as my daily runner until/if I get these few bugs figured out.
Personally, I think the most valuable thing I've been learning is just how bloated Samsung Devices truly are out of the box.

I'm going to go ahead and dump my progress log here too so you guys can see what I've been toiling with in hopes someone has some specific feedback on issues and if I am in the right place or not:
https://goo.gl/CEGCx9
As of the writing of this post, I'm virtually confident any problems I am experiencing has nothing to do with /efs/ or /system/csc/.
I've found some inconsistencies in /etc/ and in a few other directories in /system/.
I still wonder if there isn't a init.d file I haven't tracked down yet, but personally I find folder compares faster and easier to try to normalize then I do init.d files.
When it comes to folder compares, I can do a fast reboot and see if things break. When it comes to lines of code, I have to do a bulk of edits, reboot and hope for the best.
Just as an FYI, I plan on completely rewriting the OP when things are at a place where things work.

For anyone following the thread, the Downloads Section has been updated.

This seems really interesting ? I've been trying to find a good ROM for a while with little success, so hopefully this might be the one. I just have one question: what are the differences between the Google and Diagnostics versions of this ROM?