yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] varcor:
It's fairly obvious Samsung is maximizing profits over performance. The S22 Ultra is the biggest debacle since the Note 7, maybe bigger!
[Samsung Galaxy S22 Ultra] Mr. Orange 645:
Uh...how so? I mean, it hasn't blown up yet, and it seems to be a great device.
[Samsung Galaxy S22 Ultra] Fatmonk8:
Not even close
[Samsung Galaxy S22 Ultra] varcor:
In case you haven't noticed 128GB of internal memory, which is actually 106GB after system memory is accounted for is ridiculous. That's all you'll have no matter how long you keep the device. The OP has made a clear case for why it's insufficient, especially on a flagship device. Another question, why did Samsung eliminate MicroSD on the S21 when almost all the rest of there mid and low price devices include it? To copy iPhone? Nope, they choose to do it for PROFITS! The cost to upgrade from 128GB to 512GB on the S21 Ultra is $400 USD, what a scam! Who will be surprised when the S23 rolls out with 64GB?
[Samsung Galaxy S22 Ultra] Mr. Orange 645:
In case you hadn't noticed, I have a 512GB

In case you hadn't noticed, ALL devices have a lower usable storage than advertised. The advertised storage is the TOTAL storage. The OS and stock apps take up some space. So that's 100% normal.

You go off the rails here a bit talking about the S21. This is the S22 forum, and that's the decide we are discussing. The upgrade on the S22 from 128 to 512 wasn't $400. Matter of fact it was a $100 during preorder.

Can't argue about the microSD. THAT is all about profits. Of course the whole phone is all about profits.

All of that amounts to features/choices you don't like. It's doesn't put it on the debacle level anywhere near the Note 7. What you're saying is you'd rather have an exploding phone, since this is a BIGGER debacle.
[Samsung Galaxy S22 Ultra] Guyinlaca:
I think more than just the RAM, the higher storage is likely improving performance. In the Note20 Ultra days, Samsung had a disclaimer that 512 GB models would have significantly faster read and write speeds than the 128 GB models.
[Samsung Galaxy S22 Ultra] varcor:
"It's doesn't put it on the debacle level anywhere near the Note 7"

Really? Browse these posts then comment on how the S22 Ultra isn't a disaster.

https://xdaforums.com/t/s22-ultra-very-laggy-and-slow.4403983/

https://xdaforums.com/t/samsung-s22-ultra-the-phone-that-disappointed-me-the-most.4419671/

Class Action Lawsuit on the Note 7 and now the S22 Ultra.

Samsung Phone Lagging? Class Action Alleges the Company Misled Consumers on Speed and Performance

A proposed class action alleges Samsung Electronics America has misled both reviewers and the general public with regard to the speed, battery life and overall performance of certain Galaxy smartphones.

www.classaction.org

At least with the Note 7 Samsung knew what the problem was about and how to fix it. Refund the customers and ditch the model. Samsung is chasing their tail with the S22 Ultra, they have made multiple attempts and the device is still an absolute mess! It is what it is!
[Samsung Galaxy S22 Ultra] derausgewanderte:
sorry to hear that. I have the SD 128Gb version and I have none of the problems you posted - luckily.
[Samsung Galaxy S22 Ultra] Mr. Orange 645:
You're hilarious, dude. My S22 is great, but yeah. I'm glad the Note 7 only exploded. At least it didn't lag sometimes. That's so much worse.

And Samsung never fixed the Note 7. They recalled it. With the S22, the issues with the 128GB model were preempted with free upgrades ro the 256 with more RAM.
[Samsung Galaxy S22 Ultra] Tysss:
I had a… similar ish experience. It lead me to believe that it isn’t actually the 8gb RAM variant that is the problem.

I have had two 256/12gb now. The first was atrocious and was getting roasting hot just starting up, as you described, and the battery life was horrendous.

The new one is a little warm sometimes, but the battery is superb. Like iPhone 13 Pro superb.

No idea what’s happening at Samsung but they can’t seem to get consistent 5nm SoC?
[Samsung Galaxy S22 Ultra] Slade8525:
The Note7 battery issue was WAY overblown. I had 2, traded one for the S22U, and i still have a 2nd one. The keyboard and UI lag was HORRIBLE, and neither of mine nor any other people with Note7's i knew blew up.
[Samsung Galaxy S22 Ultra] Limeybastard:
Maybe your 128GB was defective?
[Samsung Galaxy S22 Ultra] DaReDeViL:
I will only discuss the SD card part.

One of the reasons OEMs ditched it is performance, especially video cam. Flagships can record at very high framerates which needs a very fast read/write storage and counting on SD cards, even the best of them, will be highly problematic. That's also the reason why they keep offering SD cards slots in their midrange or budget phones, as it will never deteriorate their modest performance.
[Samsung Galaxy S22 Ultra] JazonX:
Damn!

I thought I was the only one holding on to a N930FD.

Hope it's running well!

My battery is kinda weak, and the charge doesnt hold much longer.

Cant blame.. It's been a long time.

Like you said .. Yeah, None I knew blew up.

I owned around 5 of them at different times.
[Samsung Galaxy S22 Ultra] knuschit:
Possibly but seeing all the other reports on here now that say the same thing, im thinking it wasn't.
[Samsung Galaxy S22 Ultra] strongsteve:
I can't imagine anyone wanting to buy the 128GB.. that's just nucking futs
[Samsung Galaxy S22 Ultra] derausgewanderte:
the SD 128GB is perfectly fine for me. I am using the camera for a decent amount and I have a DJI Mini 2 and I have not run out of space yet. Currently 60Gb still available. I have not seen RAM go above 6Gb use yet either.

Sure, I would have loved to get my pre-ordered 256Gb model, but I probably would still be waiting.

cheers
[Samsung Galaxy S22 Ultra] Mr. Orange 645:
Not as overblown as the S22 problems.

Besides I think you missed the point of my post.
[Samsung Galaxy S22 Ultra] varcor:
Good to read some users are happy considering all the reports of users who aren't. What does a free upgrade of storage have to do with the multiple defects surrounding the S22 Ultra?
[Samsung Galaxy S22 Ultra] Rubby1025:
Some think that the entry level S22 ultra doesn't have enough ram with 8GB and Samsung knew it was causing a lag issue and hence was giving out free upgrades to 256/12GB.

Given how Google hides low level task execution info for security reasons nobody really knows. Users are frustrated as they are unable to get to a solid root cause, software or hardware.

I've seen 128/8GB users indicating they have no lag issues and other 12GB users indicating they have lag issues. Go figure.
[Samsung Galaxy S22 Ultra] varcor:
That may have been one of the considerations in eliminating external memory but even that is contradictory. If you've recording numerous hi-res videos the internal storage is being gobbled up at a rapid pace. Additionally, external memory has many other uses besides storing 4k or 8k videos. One can transfer data from an old phone to your new device in seconds compared to hours without external memory. I currently have a significant library of movies on a 512GB MicroSD in my S10+ and the playback is fine, no frame drops whatsoever. Everyone has their own theories, I'm firmly in the camp it was primarily done to boost profits.
[Samsung Galaxy S22 Ultra] varcor:
They aren't preempeted since the 128GB device is still being sold as the higher GB variants sell out much faster.

If you think the only problem with the S22 variants is it's 128GB device then you're extremely myopic. The S22 Ultra is logging more defects not only on XDA but across the entire web universe than any device in recent memory. If your device is holding up good for you.

Samsung reduced it's prices for the S22's in Korea by 50% on April 1st. You think that happened because someone at Samsung was overcome by a fit of generosity? No, it's due to overwhelming dissatisfaction from users and Samsung is also facing an investigation by Korea's Federal Trade Commission.

Shareholders want heads to roll!

Samsung is also getting hammered for eliminating the Vapor Chamber (which is sorely needed) but this was highly touted by Samsung pre-release. They also attempted to cover up a refresh rate that couldn't drop below 48Hz.

The S22 is a joke everywhere you look, from marketing, chipset, software, battery drain, "fast" charging, display issues, overheating, GOS throttling, random reboots, lagging, stuttering, insufficient ram, pathetic app management, multiple class action lawsuits and delisting by Geekbench just to name a few.

Ever heard of any device getting blackballed by Geekbench? Even worse the updates fix one problem then create two more.

You can attempt to defend this POS all you like but that doesn't help thousands of users who feel they got seriously worked!

Care to read an unbiased, unfiltered review from someone who could care less if Samsung gives him a free smartphone?

Samsung Galaxy S22 Ultra review: The slab phone retirement plan

Samsung stands still while the competition is better than ever.

www.google.com.mx
[Samsung Galaxy S22 Ultra] Mr. Orange 645:
TL;DR
[Samsung Galaxy S22 Ultra] blackhawk:
This appears to be true. Towards the end of this vid the N10+ which was only slightly slower, at first, just plain thumps Samsung's glorious new flagship to pieces once the ram starts filling up.
[Samsung Galaxy S22 Ultra] Limeybastard:
True story that. Samsung quality is a not what I expected with the S22U. Maybe it was designed and made during covid coupled with the chip shortages ?
[Samsung Galaxy S22 Ultra] blackhawk:
Good news... the N975U1 has the copper vapor phase cooling...🤣
[Samsung Galaxy S22 Ultra] Limeybastard:
You certainly know how to make a grown man smile.
[Samsung Galaxy S22 Ultra] blackhawk:
I had taken it for granted that Samsung would use the copper vapor phase cooling on the S22U given the past hot running graphene fails.

This is what they did. Problem is you still have relatively the same surface area to dissipate the heat no matter how effectively you collect it. It may be the cpu chipset is a mismatch or who knows what?

Real life the S22U is only slightly faster than the N10+, and that turns completely around once the rams start loading up. Then the N10+ completely dusts it, not by milliseconds but seconds. I still think scoped storage is giving some of the performance hit, the question is how much?
[Samsung Galaxy S22 Ultra] Limeybastard:
Indeed. All I know is from the S10 onwards, meaning Note 20U , S21U and S22U in particular the thermals got hotter.
[G1 Android Development] drak0:
What about public key authentication? Have you tried that?

BTW, awesome news! :)
[G1 Android Development] staulkor:
No, I have not tried that. Ill give it a shot :)
[G1 Android Development] jriley60:
running

is it fine to just leave dropbear running? or should we kill it when not in use
[G1 Android Development] staulkor:
I dont know. I think it should be fine, but it may eat some extra battery. We will need to test battery life with it running. My guess is that it probably wont impact the battery life.
[G1 Android Development] jriley60:
k

i'll be sure to keep informed about mine too
[G1 Android Development] humble:
thanks staulkor, you even followed though with the walk-though. now its time for you to catch some Z's you desserved it.:D
[G1 Android Development] jriley60:
ugh

i'm stumped

:confused:
[G1 Android Development] jriley60:
what's with all the fish names lol if anyone is trying brute force add a list of fish names hehe. i'm going to have to crash i have tried everything i know how and looked through almost everyfile i could think to look through.
[G1 Android Development] cookzitall:
sry if this is a dumb qustion

can someone explain wat exactly running dropbear on the g1 allows us 2 do? im just a little confused
[G1 Android Development] staulkor:
Nothing yet since we cant login, but once we can, ssh brings with it a lot of goodies like tunneling :)
[G1 Android Development] CleverJake37:
Howdy Boys

A few notes I made whilst following the walkthrough

busybox cp -s busybox cp

this was failing without me cd'ing over to /system/bin on the telnet terminal

not sure why, since it is in the binaries file, but, whatever

secondly

I think you meant

cp /sdcard/download/android-dropbearkey-0.51.rev1.asc /system/bin/dropbearkey

not

cd /sdcard/download/android-dropbearkey-0.51.rev1.asc /system/bin/dropbearkey

enough pety stuff, to the meat and potatoes

Just because there is a prompt for a password, doesnt mean the password exists, or even if that user exists

for proof try to

ssh CleverJakeis1337@<ip address with an SSH server>

now I may be 1337, but definitely not 1337 enough to have made my own password on your 'puter :)

so, the bigest thing would be assigning a password with good ol passwd

since staulkor and the gang has been great enough to get busybox over there, we need to get a user with which we have the password, I chose the aptly named user "ssh"

so I ran

adduser ssh -HD && passwd ssh

but that returns

[CODE[passwd: unknown uid 0 [/CODE]

meaning, as far as I know, that its trying to change the password, but it does not have one for user 0 (aka root), so its looped into an error

so I did

busybox echo root:x:0:0:root:/root:/ > /etc/passwd

to add the root user to the passwd file, allowing for it to define passwords

note - I am not sure what the home dir and the shell directory (/system/bin/sh?) should be officially, but this seems to work, for the time being

from there passwd works

passwd: no record of ssh in /etc/shadow, using /etc/passwd
Changing password for ssh
New password:
Bad password: too weak
Retype password:
Password for ssh changed by root

the bad password error comes up even with a 16 alphanumeric, so im not sure wtf thats about

ssh still does not work when I try, however

busybox login ssh[/]

returns a password prompt, which accepts when entered correctly, which takes me to an ash shell, as prompted to in the /etc/passwd file

I hope that helps some.

Im pretty sure you could set the root password, now that its empty set, but I haven't studied the boot procedure
and I do not want to bork up something that mounts as root expecting no password.

Id rather have a locked phone than an unlocked brick =]

anyone have the guts to try?
[G1 Android Development] staulkor:
Wow, good info :) Thanks for catching my typos. I have edited the first post with the corrections.

Looks like you are getting somewhere with applying a password. The only reason I said to ssh to root@<ip address> was because I was assuming that would be the account ;) I do know that you can put cupcakes@<ip address> and it will still try to authenticate, but I think root is a reasonable assumption.

Anyways, I am off to bed soon, so android development will cease until tomorrow after class.

My plan is to configure dropbear to take public authentication keys instead of passwords.

I am pretty sure it will work, but I just need to confirm.
[G1 Android Development] staulkor:
Looks like somebody beat you to it!

http://www.upche.org/doku.php?id=wiki:android4

This is only confirmed on the emulator. I guess install dropbear on the emulator (watch out, when you close the emulator, you will have to reinstall everything again the next time it boots up) and then try this out and see if you can login.
[G1 Android Development] staulkor:
I have been messing with public key authentication for about an hour now. It is accepting it, but saying "Permission denied (publickey)". I am assuming its saying that because I honestly have no idea where the authorized_keys file goes. I put it in /system/etc/dropbear thinking it will look in the same spot where the private keys are for the server, but no luck.

The only setting in the options.h file before I compile is to enable pub key auth (and yes, it is enabled). I guess tomorrow I will hunt through the code looking to see how it looks for this file.
[G1 Android Development] drak0:
make sure authorized_keys2 has permissions of '600' (chmod 600 authorized_keys2). That *might* be why dropbear is *****ing...

Although, this assumes you are putting it in the correct place - usually ~/.ssh/... but if $HOME isn't defined... *shrug*

Good luck! :)
[G1 Android Development] biktor_gj:
You can clone the root user id and you don't need to touch the "root's line" or his password for anything...

echo root:x:0:0:root:/root:/ > /etc/passwd

echo justme:x:0:0:justme:/justme:/ >> /etc/passwd

So you have a second user with the same uid, with a different password on shadow or passwd file. This way, when you enter the username justme with justme's password, you should get a root shell based on the uid. This works normally on Fedora and Debian, it should work on android too (even with busybox...)
[G1 Android Development] CleverJake37:
Nada

that didnt do it

though that is a neat trick

thanks, im gonna use it in teh future

=]

so I ran

dropbear -F -E

to monitor to stout and not background it

I tried sshing in via root@ and ssh@

and its returned

[792] Nov 07 02:48:57 login attempt for nonexistent user from 192.168.0.11:47790

confirming my earlier beliefs

=[

I also tried the -s option in dropbear to allow for passwordless logins, but to no avail

return from

ssh -v 192.168.1.8

OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.0.8 [192.168.0.8] port 22.
debug1: Connection established.
debug1: identity file /home/patrick/.ssh/identity type -1
debug1: identity file /home/patrick/.ssh/id_rsa type -1
debug1: identity file /home/patrick/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version android-dropbear_0.51
debug1: no match: android-dropbear_0.51
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host '192.168.0.8' is known and matches the RSA host key.
debug1: Found key in /home/patrick/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/patrick/.ssh/identity
debug1: Trying private key: /home/patrick/.ssh/id_rsa
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/patrick/.ssh/id_dsa
debug1: No more authentication methods to try.
Permission denied (publickey).[\CODE]

seems like its attempting to read the key, but its not able to for some reason

I think the biggest issue is creating a userbase that dropbear can read from
[G1 Android Development] Woobins:
I was googling around for solutions to the 'nonexistent user' error and came across this post: http://www.mail-archive.com/dropbear@ucc.asn.au/msg00193.html

Basically it looks like dropbear logins will fail if there is no /etc/nsswitch.conf and associated libnss* libraries. I haven't had a chance yet to test this solution myself, but I thought I'd point it out in case it can help someone else.
[G1 Android Development] Dimath:
Ah, what a crap...

I downloaded the sources of dropbear, it gives this message when some function "getpwnam((char*)username)" returns NULL. It's system function or something, I mean, it's not a part of dropbear. Description from Internet: "getpwnam - get passwd record given user login name". Searching around, I guess is looking in /etc/passwd for the record for given username.

I tried to create /etc/passwd file and /etc/group, and I am even able to use /system/bin/login to login as root (with password) or as a user created by 'adduser', but all that does not affect anyhow to dropbear error message.

So, I runned out of ideas :-/ Would be good to compile dropbear from sources to know for sure what it is doing, but sounds too complicated. Actually, people who compiled the android version should know how it works...
[G1 Android Development] Dimath:
BTW, sshd returns "Segmentation fault", which is also could be related to getpwnam("username") returning NULL (if you try to use the returned structure which is NULL you'll get this error).

So, any ideas so far?
[G1 Android Development] Stericson:
This keeps failing on me:

busybox cp -s busybox cp

Even when I am in /system/bin why is this?

I gave busybox 4755 permissions.

[Edit]

I got it to work...I had to go into the adb shell....strange
[G1 Android Development] mzet:
broken links

Hi,

links are broken. Can someone please post dropbear as attachment?

Thanks
[G1 Android Development] jblomer:
If you don't want to setup a user database (/etc/passwd), you can also patch the dropbear code a little. I have it done here.
[G1 Android Development] threaded:
Please, somebody, share 'dropbear' and 'dropbearkey' binaries

I also confirm that the author's links are broken. I ask somebody to share the binaries or to send them to my email: dark.diver (at) mail.ru

Thnx
[G1 Android Development] oma:
I don't have the original binaries posted in this thread, but I have ones I compiled myself. It's dropbear-0.52 with patches from:

http://jblomer.web.cern.ch/jblomer/android.htm

http://www.mail-archive.com/android-freerunner@android.koolu.org/msg01076.html

Mostly the former with just the openpty function from the latter (because it couldn't open a pty otherwise on my Samsung Galaxy).

Just put dropbear, dropbearkey and scp in /system/bin and then start dropbear as described in the first link.
[G1 Android Development] glock30:
does the file that says patch need to be on the phone?
[G1 Android Development] oma:
No, this is only needed if you want to build it yourself. The files you really need on your phone are dropbear, dropbearkey, and scp.

(scp isn't strictly necessary, but it's quite convenient for copying files to/from your phone over wifi. Also, after you've generated your host key, dropbearkey isn't needed any longer.)
[G1 Android Development] glock30:
Thanks for the quick response... I'm going to try later on tonight.
[G1 Android Development] superg05:
this tread is very interesting
[G1 Android Development] professordes:
dropbear on HTC Hero anyone?

I had a go at running dropbear on a rooted HTC Hero and was a bit puzzled by the behaviour. When I booted the phone using the boot.img.insecure originally used to carry out the rooting as described in:

http://phandroid.com/2009/08/04/how-to-gain-root-access-on-your-htc-hero/

and started dropbear with:

dropbear -A -N justme -U 0 -G 0 -C <passwd> -r /system/etc/my_rsa_key -p 2222

(where justme was a cloned root user I had set up) I found I could happily ssh into the phone with ssh justme@ipaddress -p 2222. However, when I executed the same command after booting the phone from the native ROM it would hang after asking for the password. Would anyone have an idea what is going on?
[G1 Android Development] oma:
I don't know what's wrong, but you can see what's going on if you add "-F -E" to the dropbear command.
[G1 Android Development] Bieh:
So, I've managed to get this running properly ('dropbear -A paul -C <passwd> -R /sdcard/authorized_keys -U0 -G0'). I had an issue where upon logging in $PATH would be set incorrectly, but I added a .profile file to fix this. I also use 'ash && exit' at the bottom of .profile, which makes it start ash on login, then logout when ash exits. All seems to work great now.

However I still have to start dropbear manually - I tried adding the launch line to /system/init.rc, but no luck. Anyone have any tips on how to make the dropbear service start on boot?