can someone test the wpa_supplicant provided (which is in system/bin) on galaxy player 5.0 (2.35) to see if any one work and can connect to adhoc View attachment wpa_supplicant.rarnetwork?
first, rename it to wpa_supplicant and test them one by one,thanks!
OK, I'll try it.
their is an app in the market called:
"WiFi Ad Hoc enabler" by AREND
I would try it, but I don't have a SGP rom, so if my wifi config was to get trashed, I'd be in trouble
when i find a rom for the SGP 4.0, I might try this, I've been wanting ADhoc for a while now.
The file wpa_supplicant3 works well on my YP G70 2.3.6. Now I can use ad hoc.
---------- Post added at 06:29 AM ---------- Previous post was at 06:22 AM ----------
Well, you can use a terminal to run each file, and you will see the version number. If there is a "ah" word after the number, it's an ad hoc supported file. Otherwise, you don't need to try it. Besides, you should run your system's orginal file to know the right version for your current system.
noisyfox said:
The file wpa_supplicant3 works well on my YP G70 2.3.6. Now I can use ad hoc.
---------- Post added at 06:29 AM ---------- Previous post was at 06:22 AM ----------
Well, you can use a terminal to run each file, and you will see the version number. If there is a "ah" word after the number, it's an ad hoc supported file. Otherwise, you don't need to try it. Besides, you should run your system's orginal file to know the right version for your current system.
Click to expand...
Click to collapse
How do I run them? I tried copying them to my SD then running with connect bot,
but it said "permission denied" so I tried "chmod +x" and it said bad mode
chmod 755,not +x, that's not original Linux.
I tried that too (see attachment)
What would happen if I was to copy wpa3 and it was the wrong version?
would my SGP still boot? I made a backup, so if it would not cause any serious harm I could just go ahead and try #3.
Of course it will boot. Wrong file only cause Wi-Fi connection failed or nothing. And I suggest copy the files into /system/bin and then run them.
---------- Post added at 09:16 AM ---------- Previous post was at 09:09 AM ----------
By the way, you don't need to reboot after replacing the file. You just need to turn off the WiFi and turn on it. If it works, you will find your adhoc connection point in the list. So you needn't be afraid of not booting.
#3 worked for me too
SGP 4.0.
Thaks a Lot
Congratulations~
I'm wondering whether G70 support wifi tethering and bluetooth DUN. I have a s60 with 3g.
sweet worked perfectly #3
Samsung Galaxy Player 5.0 U.S. Running CM7.2.0-RC0-venturi_usa-KANG Kernel Version 2.6.35.7-G70UEK18-CL56626
Compatibility is a GO!
Ok, so I have been using linux since long and I managed to write many scripts for my personal management, using crontabs for auto-execute etc. I also played with rc.local in linux. Fortunately It was all easy to find the relevant info whenever I want. But not with Android. I have been searching but no exact solution so far.
I want to know how to auto-execute script on start up? I have put script in /system/etc/init.d changed its permission to 755. Made chown to root, but Fail.
Also tried to use "Script Manager" but that force closes everytime. I switched to Cm7.2 Sedan yesterday and same case with this ROM too. (So I don't think Its a ROM related). This the same ROM Turbo-boost or other scripts works fine.. What is it that I'm missing here?
Afaik userinit script at /data/local/userinit.d
Rushyang said:
What is it that I'm missing here?
Click to expand...
Click to collapse
Since you're saying that other scripts get properly executed, than it must be your custom script itself, which poses some problems here? Btw, nobody is right in your head or is a visionary and able to give you some help, if you don't give some bits of code to tell, what might be basically wrong with it. ...
Just jump over to slaid's scripting threads. There are some hints and tips how to log and debug initd scripts. Or you can just strip from g_BonE's script the debugging code and apply it to your own script.
Happy scripting! ...
[xXx]
---------- Post added at 08:21 PM ---------- Previous post was at 08:15 PM ----------
As a matter of fact, iandol was so kind enough and did already strip the necessary code for you. ...
[xXx]
I've been trying to learn to build my devices (n8013) image for Ubuntu Touch. I did n't get too far. So here is what I did
1.) [email protected]:/home/christian# git clone https://github.com/mamenyaka/android_device_samsung_n8013.git
Cloning into 'android_device_samsung_n8013'...
remote: Counting objects: 101, done.
remote: Compressing objects: 100% (56/56), done.
remote: Total 101 (delta 48), reused 86 (delta 36)
Receiving objects: 100% (101/101), 19.20 KiB, done.
Resolving deltas: 100% (48/48), done.
2.) [email protected]:/home/christian# cd android_device_samsung_n8013
[email protected]:/home/christian/android_device_samsung_n8013#
3.) [email protected]:/home/christian/android_device_samsung_n8013# . build/envsetup.sh
bash: build/envsetup.sh: No such file or directory
4.) Would be:
[email protected]:/home/christian/android_device_samsung_n8013#brunch n8013
Obviously I'm missing something, anyone now what I need to do? Am I in the wrong directory.
Why aren't you using the phablet tools? You can't just run a git clone of a device tree, you don't have the kernel or the Ubuntu Touch sources!
Use phablet-dev-bootstrap to initialize your working folder and then go through the rest of the setup like everyone else. You can't skip steps, it just doesn't work that way.
Sent from my SGH-T999 using Tapatalk 4 Beta
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
Your first clue should have been the 101 objects. It took me about 2 hours to sync the UT and CM repos on a 50Megabit connection.
Sent from my SGH-T999 using Tapatalk 4 Beta
Thanks
EtherealRemnant said:
Why aren't you using the phablet tools? You can't just run a git clone of a device tree, you don't have the kernel or the Ubuntu Touch sources!
Use phablet-dev-bootstrap to initialize your working folder and then go through the rest of the setup like everyone else. You can't skip steps, it just doesn't work that way.
Sent from my SGH-T999 using Tapatalk 4 Beta
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
Your first clue should have been the 101 objects. It took me about 2 hours to sync the UT and CM repos on a 50Megabit connection.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Figured it out. I had to revert to an earlier version of Ubuntu and didn't reinstall phablet tools. It seems I've also been working in the wrong directory. I'll have to start from step 1. I had it working last week and couldn't figure out why it wouldn't anymore, then it dawned on me when you said "phablet tools wasn't installed", my dumb mistake. Thanks, I appreciate the help.
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
/ * Your warranty is now void. Knox 0x1.
/* We are not responsible for bricked devices, dead SD cards, lost data due to failed backups, etc, etc. flash at your own risk
*/
How to flash this ROM:
1. Download the zip file.
2. Make sure this zip file is saved to your device (I prefer transferring to sd card to allow for full wipe of data on tablet).
3. If you want Google Play functionality, download OpenGApps (link below). (optional)
4. Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
5. Make a backup (optional).
6. Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (I like wiping internal data too, do NOT wipe SD Card!)
7. Flash the ROM you just downloaded.
8. Flash OpenGApps ARM for Android 9.0 if you want Google services (optional).
9. If you want root, flash Magisk.
10. Reboot and proceed normally with installation.
11. ????
12. Profit!
Download links:
SM-T350
OpenGApps ARM 9.0 (I use pico)
Source code:
LineageOS
iesous-kurios (forked from LineageOS, and rest of the developers mentioned in the following Credits) on Github
Galaxy MSM-8916
Credits:
The LineageOS Team (and specifically haggertk )
elginsk8r
VirsysElectron
Nubianprince
And awesome tester : retiredtab (saved me sooo much time and has been huge asset in getting bugs fixed)
And of course the Galaxy MSM-8916 team for all of their hard work on our device specific code.
Version Information:
ROM OS Version: Android 9.0 Pie
Known Bugs:
Static while playing mp3s with stock music player (download vlc player to play mp3 files)
Overwhelming sense to brag that your old tablet has newer version of Android on it than a lot of people's expensive phones.
All other functions seem to be working fine. Please report bugs with logcat. I am just starting out on being able to troubleshoot bugs and make edits to code to fix problems, so a majority of bugs will be fixed by the official devs and maintainers of Lineage but I'm trying to learn how to help out too and you have to start somewhere, right?
1st
2nd
3rd
Looking forward to this, thank you!
Thanks for the nice ROM, older bugs are gone! Runs very smoothly with frequent lock-ups.
Issues:
Some apps from Google Play Store are not available saying "not compatible" when you can install their APKs (i.e. Instagram...etc.)
Lockups are annoying
Jfuginay,
Thanks for compiling this ROM. Your work is appreciated.
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
I will check tomorrow to see if there is a newer TWRP that can work with the updater script. I saw in another thread that the SM-T550 updater script is failing because TWRP can't report the model number.
I do need external audio working. I see that SM-T550 which is the bigger version of this A tablet does have audio working as per
https://forum.xda-developers.com/showpost.php?p=78720468&postcount=22
Perhaps there is something in that SM-T550 code that we can use to help with the SM-T350.
retiredtab said:
On my SM-T350, I get the following message when trying to install the 16.0 ROM
updater process ended with error: 7
error installing zip file /sdcard/Download/lineage-16.0-20190221-UNOFFICIAL-gt58wifi.zip
Click to expand...
Click to collapse
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
retiredtab said:
Okay the above error was due to TWRP version 3.1.0. I upgraded to 3.2.1 and now the updater-script installs 16.0 onto my SM-T350.
I found TWRP 3.2.1 at
https://androidfilehost.com/?fid=962339331458992706
TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi.tar
for the Samsung Galaxy Tab A 8.0, by Austcool Walker
MD5 = 6455c0cfa01b9f71cf575c553df18733
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
I also noticed a newer build today (dated 20190223).
External audio still doesn't work. Headphone jack works.
---------- Post added at 12:11 PM ---------- Previous post was at 11:55 AM ----------
Here is the SM-T550 thread where virsys got external audio working.
https://forum.xda-developers.com/showpost.php?p=78972270&postcount=70
I'm looking through the SM-T550 commits, but unsure what might be needed for the SM-T350?
The most obvious difference between
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/tree/lineage-16.0
and
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
is the entire configs folder in the SM-T350 code.
I also found
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/tree/lineage-16.0
Click to expand...
Click to collapse
Glad you got it to boot.
I noticed that missing config folder too, so I just added that to my build directory and am compiling that now to test it out. I didn't add the camera files, since it is only bluetooth and speaker I'm trying to troubleshoot. Don't think the camera is having problems, but honestly haven't tried it out yet.
I noticed the missing config folder when checking out the device.mk file for each device. I added the links to the config folder in the device.mk file and added the bluetooth and sound folders from config file to my build directory, so I'm hoping once that compiles it will fix our problems.
Will do a dirty flash first, then if it still isn't working, I'll do full wipe and test it out. If it boots up and fixes anything I'll upload it for people do download, if the same problems persist I won't bother uploading the new build.
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
retiredtab said:
One of my links that I found got messed up.
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi
In the above, virsys does some OSS-audio cleanup for 16.0
---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------
Regarding the stock 16.0 camera, I get the following error message
Camera error
Can't connect to the camera
If I download open camera from play store, the back camera gives an error message
"failed to start camera preview"
However, the front facing camera shows a preview, but can't save the picture/photo
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
Also had a complete reboot while using Clash Royale game. I hit the news tab and the tablet completely rebooted.
I will try to reproduce, if I can, and get a logcat.
Playing Clash Royale seems okay, but I have to use the headphone jack vs external audio to get sound.
My SM-T350 is a completely fresh install with only gapps pico. Nothing else.
---------- Post added at 04:59 PM ---------- Previous post was at 04:29 PM ----------
Looking at the commit history between the SM-T350 and SM-T550, it looks like deadman96385 didn't add the config/audio files for the SM-T350, but did for the SM-T550 on April 18, 2018
SM-T350
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/commits/lineage-16.0
SM-T550
https://github.com/Galaxy-MSM8916/android_device_samsung_gt510wifi/commits/lineage-16.0
I wonder if the non working external audio is due to missing config folder?
Click to expand...
Click to collapse
I'm hoping it's those config files. I did a build with them in but I'm not sure they were included because of my ccache being enabled. I'm not 100 percent convinced that ccache can tell the difference between slightly modified files well enough to know to include the changed files in new build, so I cleared out my ccache files and ran make clobber and am building fresh right now with those config files in there.
Will do full wipe and flash this and report back if it made any difference.
Adding those config files didn't fix anything. Found several differences in some proprietary.mk files so attempting to see if any of those do the trick. New build compiling now. Will probably need to disable ccache and do make clobber to clear directory so I'll probably let it build over night while I sleep.
Let's hope I wake up to a fixed ROM !
Jfuginay said:
Adding those config files didn't fix anything.
Click to expand...
Click to collapse
Darn, I was hoping the config would fix it.
I left a message in the SM-T550 thread asking virsys what was done to fix the external audio because it's not obvious to me where the commit is that fixed it.
In this post
https://forum.xda-developers.com/showpost.php?p=78170903&postcount=9
dated Nov 15, 2018 virsys says "Audio is working now".
At github
https://github.com/VirsysElectron/android_vendor_samsung_gt510wifi/commits/lineage-16.0
there is a commit for Nov 16, 2018 entitled
Cleanup for OSS-audio and improved lineage-16.0 compatibility
I wonder if this commit fixed the external audio?
Just out of curiousity, how are you building this ROM? Locally or on some clould computer?
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
retiredtab said:
Another idea/suggestion?
At
https://github.com/Galaxy-MSM8916/a...8wifi/blob/lineage-16.0/proprietary-files.txt
it says the proprietary files are from (line 1)
# Samsung Package Version T550XXU1CQL5_T550OJV1CQK3_TUR (unless otherwise specified and/or tagged)
The SM-T550 has 2 external speakers while the SM-T350 only has 1. I wonder if we have to grab the proprietary files from a SM-T350. Maybe the drivers from the SM-T350 know how to work with just 1 speaker?
Click to expand...
Click to collapse
I'll check out a working 14.1 ROM and see if it has specific proprietary files there which differ from what we are using now.
Virsys responded back on how he/she got the SM-T550 external audio working. See
https://forum.xda-developers.com/showpost.php?p=78978788&postcount=74
"I've fixed the whole audio framework by editing and importing my own mixer_paths.xml to /system/etc"
I wonder if we can download his SM-T550 ROM image, extract that mixer_paths.xml file to see what changed?
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
retiredtab said:
So I downloaded the SM-T550 code and looked at the
/system/vendor/etc
directory.
There are 28 files there. In the SM-T350 /system/vendor/etc, there are only 27 files.
The additional file in SM-T550 is called audio_platform_info.xml.
It has definitions for speaker out. I'm not sure of all the definitions or how it's linked yet? I don't know if this file has to be part of the actual rom compilation process or it gets read at boot/runtime.
In addition, there have been additional entries put into the mixer_paths.xml file in the 550 that virsys referred to.
In the SM-T550 /system/etc directory, there 3 additional XML files named
A05QF_sr544_module_info.xml, B05QF_sr544_module_info.xml and C05QF_sr544_module_info.xml.
Not sure if these files are needed or not?
Click to expand...
Click to collapse
Thanks for all the ground work, gives me a good place to look into tonight when I get home from a meeting and have some time to tinker with the code.
K, I looked through a lot of proprietary code for both the gt58 and 511, and hopefully found all the discrepancies. Added over 20 files and lines of code to gt58 proprietary folders and renamed one file to match the dependency in another file.
Compiling now, so cross your fingers that it fixes our sound!
Are your changes up on github?
https://github.com/jfuginay
I'm newish to github and just learning how to navigate and look around.
What I find confusing is the seemingly incredible amount of layers of abstraction in defining the speakers. That is, A->B, B->C, C->D, D->E, E->F, F->G. Anything missing is enough to break it.
I understand why the layers are required, but without a flow chart or visualization of how these things work, it's difficult to follow all the necessary definitions and files needed.
I also have noticed some of the people using github have no documentation on why the code change was required. The changes are there, but why? Was it because something was broken? Was it because it wasn't defined properly in the first place? Was it because there was a potential security problem?
If you have any URL resources that would help explain some of this, I would appreciate some pointers.