yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Questions & Answers] Az Biker:
Try just using the charging cable connected to the PC, it's all I use to connect to my Win 10 PC, and the only thing I have to do is make sure the device is set to MTP, I never have to mess with drivers on the PC.

Are your drivers up to date? Are you saving any changes on the PC after making them? Not sure why you're getting the MTP Usb / MTP Device option unless it's related to using the dongle (which I never have)...
[Google Pixel 2 XL Questions & Answers] three west:
It's not Win10 dude, I connect a few times a week for Andromeda purposes, plug and go.
[Google Pixel 2 XL Questions & Answers] wtherrell:
In my case it WAS Win 10. None of my phones would connect for MTP. I frequently use ADB and windows was trying to use those drivers by default. After messing around in device manager I finally was able to select the windows MTP drivers. After that all my phones were able to connect with windows via MTP.
[Google Pixel 2 XL Questions & Answers] juancarlosgzrz:
Wtherrell how did you do that? my phone won't even show up on device manager
[Google Pixel 2 XL Questions & Answers] wtherrell:
I I R C I had to delete all the old ones and start fresh. Some of the old ones were not obvious but somewhere on line or in the forums I found some clues about what to look for and delete. I wish I could remember exactly where but I can't at the moment.
[Advantage X7500, MDA Ameo ROM Development] Goatmaster:
The final version is out and it doesn't work with the 96 DPI on the athena. The tabs are missing in the settings list, which isn't a problem but the tabs have no icons on the home screen. This program looks really useful and I am hoping we can find a way to make it work.

Mods please don't move this thread, it is device specific and I believe the issue would be overlooked in the main thread in the general forums.
[Advantage X7500, MDA Ameo ROM Development] xvanwaart:
Working great over here at 96 DPI! I've installed the final version (2.0.0 build 3275) And so far I haven't seen any drawbacks. Works very smooth, animations without hasitation and a few nice new features.
[Advantage X7500, MDA Ameo ROM Development] sabes143:
Hi

Can you see the home tab icons? Can you see the Tab settings list?

see my screenshots there are still problems.
[Advantage X7500, MDA Ameo ROM Development] sabes143:
Hi

The tabs can be Replaced in 192 DPI if you using spb weather or phone suite or diary then switch back to 96 DPI, but Home tab you cannot do anything.

Tab settings list still missing in 96 DPI.

See my screen shots and see my previous post.
[Advantage X7500, MDA Ameo ROM Development] techntrek:
A blogger on ZDNet reviewed SPB on an Athena, and said it worked well.

http://blogs.zdnet.com/mobile-gadgeteer/?p=927
[Advantage X7500, MDA Ameo ROM Development] Goatmaster:
Good find however I believe he is ignoring the problems with the 96 DPI. Look at his screen shot the list of tabs are missing. And he has no screen shots of the home plugin, which I thought was a big feature of this application.

Thanks sabes143, I forgot to move the information about 192 DPI in this thread.
[Advantage X7500, MDA Ameo ROM Development] apd:
I agree. It is completely useless. It is impossible to get the tabs working or showing anything meaningful and impossible to get the other menus to stay on the homepage. I would steer clear.
[Advantage X7500, MDA Ameo ROM Development] bairda:
No joy here either with 2.0. No tabs. Today screen plugin is totally useless without them.

Too bad, there are some pieces of it I like!
[Advantage X7500, MDA Ameo ROM Development] Goatmaster:
I saw this posted in the development forum: Password for dat files that are really zip files: b0fm18zq Maybe this will help make the icons show up on the tabs...
[Advantage X7500, MDA Ameo ROM Development] apd:
Their forums also note that they don;t support RealVGA - that could be the problem (and if it is, that is really shortsighted on their part)...
[Advantage X7500, MDA Ameo ROM Development] mojo2000:
same problem here,

mobile shell works fine with RealVGA and the 192 dpi setting

but is pretty useless with 92 or 128 dpi activated.

besides the today plugin not working:

in the spb menu (right softkey by default) the icons of all my custom programs look totally crappy, and next to each icon half of the icon of another program is visible.
[Advantage X7500, MDA Ameo ROM Development] eaglesteve:
I have the same issues, except that on my today screen, there are three other icons appearing next to all the icons.

I don't like having so many gestures to go access my applications. Currently my setup is far better than spb mobile.This is what I have:

1.I have date and time on the task bar so what I can see it everywhere. In addition, I have the big clock on my today screen provided by spb time. This lets be have fuller function than spb mobile.

2. I have spb phone suite on my today screen.This is better than what spb mobile offers because in addition to what spb mobile offers, I also havethe ability to switch on/off bluetooth,wifi etc.

3. I use SBSH weather watch today plugin, which of better than spb mobile's weather program because it shows more info,occupies less space,and has much more comprehensive weather stations for smaller towns.

4. I use ilauncher to launch programs. It is much easier and effortsless to configure and customise the icons for all dpi. I also get the safe mode reset capability.

5. I use today agenda to show my calendar and tasklist on my today screen. This is better than pocket informant IMHO because each item takes only one line, so more items could be shown on less space on today screen.

All items are visible at once on my today screen, without any need to swipe any fingers, which is a fun thing to do for just the first few seconds, but is really annoying after that for me.
[Advantage X7500, MDA Ameo ROM Development] dheerajjuneja:
Don't know, but even i don't like the way it behaves.

Its quite jerky when it does the so called "Animation" when you open contacts or any sub screen.

Its far better to use spb pocket plus or even resco today plugin and get the basic things you need right on your today screen.

Though, its something good to play around for a few days ... but then eventually it boils down to performance. It the device is not snappy, no matter what you do, it will not satisfy ...
[Advantage X7500, MDA Ameo ROM Development] jessegreene:
Let's give 'em a call!

Has anybody tried to contact SPB Softwarehouse and gave them a version of the TrueVGA to test it with their software? I would think we are a large community with a voice!:rolleyes:
[General Questions and Answers] rauliordache:
Hi everyone!

Let's consider that we are talking about rooted devices (with Android).

Where can we find the settings that states the baud rate and the refresh rate/update rate/frequency (in Hz) for the GPS module?

For example, here is a project where we can change the max_rate using:

ro.kernel.android.gps.max_rate=5​

(I want 5(5Hz) fixes/second, instead of 1Hz (1 pos/sec)). This project is for a serial GPS device (configuring an USB receiver, let's say).

But there can we find the same settings for the built-in GPS module (MTK chip/Qualcomm, doesn't matter)? I don't think I need a custom ROM for this small modification. Could it be /system/etc/gps.conf ?

Thanks!
[G4 Q&A, Help & Troubleshooting] popos1:
Hi,

I have a H815.

I was updated rom to nougat v29a, using LGUP and stock tot file.

My question is how to enable VoLTE and VoWiFi?

(my operator already turned on this function on his side)
[G4 Q&A, Help & Troubleshooting] Foto-AG:
After flashing the tot file and configuiring i put my Sim in and got after 30 sec a SMS from Vodafone with configuration details. I have followed the instructions and it rums well.

You should go to your Operators Website and search for the APN config tab. Only the idea i have for you.
[G4 Q&A, Help & Troubleshooting] popos1:
I was tested my sim card on galaxy s6 and vowifi and volte was working, but here when i turn a flight mode and wifi to on, it doesnt work, any help with setup volte and vowifi?
[G4 Q&A, Help & Troubleshooting] popos1:
Refresh

Wysłane z mojego LG-H815 przy użyciu Tapatalka
[General Questions and Answers] PlasticMonster:
Hi All,

I was going to refresh my Note pro 12.2 SM-P900 unit but things have gone awry. I was installing version TWRP boot-loader/recovery to then upgrade to lineage.

The TWRP recovery load via Odin completed but the install didn't mesh.

The device is now determined to stay turned on at the black and white Samsung loading page with RECOVERY IS NOT SEANDROID ENFORCING in hurtful red letters.

I can get to the "this is dangerous, press vol down page" but if I click down (or up) it restarts. If I try to go straight into download mode it just restarts as well.

Obviously cant take out the battery (currently letting it run down and see if that helps). I've read a number of guides on the various home, volume and power combinations and have done this on numerous devices before but this is the first time I've really managed to mess things up but statistically after the number of times I've don't this stuff it was going to go wrong eventually. If I could get it into download i'd be able to re flash a recovery and I'm sure all would be well but that doesn't seem like an option!

I think this may be the end of the line for it, but any and all suggestions welcome at this point.

PM
[General Questions and Answers] Ibuprophen:
I don't have this device but, your best bet is to post this question within the following Official TWRP thread for your device.

https://xdaforums.com/showthread.php?t=2706982

I believe that one or more of the following threads may also be helpful for what you need.

https://xdaforums.com/showthread.php?t=3154362

https://xdaforums.com/showthread.php?t=3568690

https://xdaforums.com/showthread.php?t=3550359

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[General Questions and Answers] PlasticMonster:
Thankyou Ibuprophen,

Appreciate you taking the time to call these out.

The boot loop resolved when I allowed it to fully power down and then recharged and followed the instructions again.

Just in case anyone else runs into this, take time, have a up of tea, let it drain and die. Then follow the instructions called out above.

PM
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​

* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.

Odin

- Odin3 v3.13.3

Heimdall

- Glass Echidna

TWRP for Samsung Galaxy S III (International LTE)

How to flash TWRP with Odin​

1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.

2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.

3. Pull the battery as soon as your phone vibrates.

4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy S III").

How to flash TWRP within a previous version of TWRP​

1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy S III").

2. In TWRP, tap "Install" then "Install Image".

3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.

4. Select the "Recovery" radio button.

5. Move the slider to the right to flash the TWRP image.

6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.

Changelog

- See post #2.

Bugs

- You tell me!

Credits

- Option58, rgib, stek-kravari, and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the i9305.

Sources

- Option58

- rgib

- i9305 repository

- TWRP repository

XDA:DevDB Information

TWRP 3.5.0_9-0, ROM for the Samsung Galaxy S III I9300

Contributors

ripee

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.0.x

Version Information

Status: Stable

Current Stable Version: 3.5.0_9-0

Stable Release Date: 2020-12-28

Created 2018-01-27

Last Updated 2022-12-09
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Reserved

CHANGELOG

The official build is now available!

* My thanks to everyone who tested my beta builds and left feedback :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Reserved
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
Is there any difference between this twrp and [MENTION=4315222]Option58[/MENTION] twrp?

https://androidfilehost.com/?w=files&flid=225362
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Other than the file size? I've seen his build but he doesn't have any publicly available device tree repo with which I could compare mine. If he adapted his build from any rom's source repos, mine should work as well as his. Two possible reasons for the difference in file size are a different compression method, or a different number and nature of entries in the BoardConfig.mk file, which contains the bare minimum hardware parameters and TWRP flags. Perhaps he included a few extra entries which may or may not be essential to the functionality of TWRP? Either way, I just want to contribute a TWRP device tree that could be used for future versions, as I intend on submitting it for official support just as soon as there is sufficient positive feedback. :good:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
I just flashed your twrp and i could not boot up my phone, it gives me error:

Could not do normal boot, invalid kernel lenght
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Option58:
My sources are in the official LineageOS repo:

https://github.com/LineageOS/androi...mmit/e5734d09a16b97b7d55d3acf9d3e63e1b4653bd8

I didn't use any of the TWRP sources other than well...TWRP. Kernel, device tree and all that are from lineage-14.1.

Feel free to use it, might be more useful when next TWRP version arrives because I don't have build env set up anymore on my PC.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
That's exactly what I thought you did and the difference I described in my previous post. Both methods are equally correct, with the difference in file size being that the LineageOS BoardConfig.mk contains many more entries that are irrelevant for recovery mode. I know that both methods produce equally fully functional TWRP builds because I built TWRP for my tablet, gts210wifi, boths ways and both worked.

The reason why having a dedicated TWRP device tree is beneficial in the long term is that it's the preferred source code for submission for official support, given that the lack of unnecessary entries in the TWRP device tree reduces the chances that future versions of TWRP won't be able to be successfully built even with the backwards compatibility of the TWRP repo itself, omnirom/android_bootable_recovery. Less code, fewer bugs, fewer errors.

My other reason for building a dedicated TWRP device tree for i9305 is as a favor to a friend as well as the lack of a current official maintainer. Please report back whatever feedback you can and I will eventually submit it for official support.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Option58:
Well I was just trying to fix bug where LineageOS OTA updates didn't work in the official TWRP. That's the main reason for this. It was only later when I found out official didn't boot. Make sure you include /misc partition please. :D

My personal opinion: I don't agree with that 'less code, fewer bugs, fewer errors' situation as you now have new TWRP device trees to maintain. Anyway building TWRP was not my main goal it's building lineage - but I can get easy TWRP whenever I want it. And this wasn't made for i9305 I don't even own i9305 - it's made for all smdk4412-common - that how I supported like 6 devices at once.

But, yeah, you can't use what I did for official TWRP and official TWRP needs to get fixed properly so thanks for you work :) Also if you notice anything wrong with the code in lineage (like wrong line or something) feel free to let me know.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
I don't own the i9305 either, I only have occasional access to one. I know very well that the smdk4412 source supports multiple devices, as I've also built TWRP for i9100.

As for Lineage, I've built for i9305 from its official repos in the past myself. It worked then so I'm sure your recent builds work just fine as well.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
[MENTION=6005084]ripee[/MENTION] I just flashed your twrp and i could not boot up my phone, it gives me error:

Could not do normal boot, invalid kernel lenght
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Ok thanks for letting me know! I will let you know when the revised build is available.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
New build is up! Rather than taking partition values from the i9305 device tree, I took them from the smdk4412-common tree. Thank you, Option58, for your advice that proved to be correct.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
Link?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
OP
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
[MENTION=6005084]ripee[/MENTION] With new version now the phone loops samsung logo
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
I'll take another look, thank you!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Ok, try it now. I had the wrong board kernel pagesize in the BoardConfig.mk.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
Same thing again
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Try again please.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
Link is the same?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Unless I specify otherwise, that would be the safest guess ;)

Edit: Actually, nevermind for now! I took another look at the link to the TWRP building instructions Option58 posted and I made that change in the kernel. I'll run a regular lineage build and add the kernel file from it to my TWRP repo, then build again. So hold off for now!

Edit 2: Ok, try the build that's up now.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
I noticed that both the img and tar files have been downloaded many times already. , but as I don't have regular access to an S3 LTE, I'd greatly appreciate any and all feedback, both good and bad.

Given the bootloops reported by stek-kravari, I know it's easier to try something and then forget about it if it doesn't work. But I intend on making it work and eventually submittig it for official support.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] stek-kravari:
[MENTION=6005084]ripee[/MENTION] Its working now, good job :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Thank you! Do all the functions work? Backup, restore, encrypted backup, time zone? lol

If there are any minor bugs, I'll work on them quickly because I just submitted my device tree for official support!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] public3n3my:
Hey there.. I tried your build just now, and i cant select sdcard (whether to install or mount or backup) on the menu.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Thanks for letting me know! What file format is your SD card in?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] public3n3my:
Fat32 n exfat(2 different card) i tried both..

Note*

It working fine while using the build from option58.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
I added a couple TWRP flags to the BoardConfig.mk file. Please try this build:

twrp-3.2.1-0-i9305.img

twrp-3.2.1-0-i9305.tar
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] public3n3my:
Still fail to detect the card..
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
I took out an older TWRP flag from BoardConfig.mk. Please try the above link again.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] public3n3my:
Now It's detect the card! :svetius:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
Great! I'll push the changes to TeamWin and ask them to build version 3.2.1-1.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] public3n3my:
:good::good:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] KubaFKubaF:
I cannot install ROMs with your build from OP. It says "Failed to map file".

Installing modems and recovery images works.

Also the recovery freezes for ~3 seconds occasionaly while in the File Manager just going up folders.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] Atexor:
After long time I decided to root and install custom ROM on my second i9305. Eveyrthing was fine until I wanted flash LOS or AICP. I changed SD and got mapping error.

I flashed older TWRP (3.0.2.1) via Odin and it worked. LAtest TWRP is broken.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djrzgl:
Just to confirm, using older TWRP 3.0.2.1 via Odin as mentioned solves mapping error... Just installed brand new ROM :cool:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
3.2.1-2

Please try this, I changed the recovery.fstab file to that of the cm-13.0 branch from which 3.0.2-1 was built:

twrp-3.2.1-2-i9305.img

twrp-3.2.1-2-i9305.tar
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rojanor:
I just tried the twrp-3.2.1-2-i9305.img

Full wipe, and tried LOS unofficial, but still "failed to map file blabla"

Im ready for more testing :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] ripee:
3.2.1-3

twrp-3.2.1-3-i9305.img

twrp-3.2.1-3-i9305.tar

I borrowed the partition maps from the older cm-13.0 branch.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] rojanor:
Flashed twrp-3.2.1-3-i9305.tar with odin, full wipe all partitions, still failed to map file with lineage-14.1-20180301-UNOFFICIAL-i9305.zip
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] GabrielMartinez:
I just tried the latest Twrp- 3.2.1-2 - I9305.img

After i boot on recovery i try to wipe the cache partition and this is the result

Failed to mount cache invalid argument after that when i boot my phone i stuck on logo. Then when i back in recovery mode i try to factory data reset after that situation i reboot my phone and it worked the bootloop was gone please help to solve the new twrp :)