yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I've fixed pio mode on the SD driver, this means it should now boot with radios other than 1.65.24.x, can somebody with a different radio try this kernel:

http://cs-alb-pc3.massey.ac.nz/vogue/zImage-kaiser

If you want to build it, its the latest commit in the vogue tree (select vogue and kaiser machine types).

The smem driver still crashes amss for me though, it works but after a short time prints a long error log like this.

[ 2.150000] SD Init
[ 2.178613] mmc_sd_init_card: Delay 250 ms
[ 2.438393] clk_set_rate 21:25000000
[ 2.542423] mmc0: host does not support reading read-only switch. assuming write-enable.
[ 2.549468] SD Init Retry
[ 2.550071] mmc0: new SD card at address 2df3
[ 2.555280] mmcblk0: mmc0:2df3 SD02G 1921024KiB
[ 2.560571] mmcblk0: p1
[ 4.673663] EXT2-fs warning (device loop0): ext2_fill_super: mounting ext3 filesystem as ext2
[ 5.059926] init: cannot open '/initlogo.rle'
[ 5.259285] [2] <6>warning: `rild' uses 32-bit capabilities (legacy support in use)
[ 6.276708] smd_open(0)
[ 6.390156] receiving 12 bytes from ch 0:(@HTCCSQ: 3
[ 6.394845] )
[ 6.409403] sending 8 bytes to ch 0:(ATE0Q0V1)
[ 6.414131] [1] sending 1 bytes to ch 0:(^M)
[ 6.418345] [2] receiving 6 bytes from ch 0:(
[ 6.420000] OK
[ 6.420000] )
[ 6.420060] [1] sending 8 bytes to ch 0:(ATE0Q0V1)
[ 6.704791] [1] sending 1 bytes to ch 0:(^M)
[ 6.708883] [2] receiving 6 bytes from ch 0:(
[ 6.710000] OK
[ 6.710000] )
[ 6.710060] [1] Old radio found: Audio Disabled
[ 13.152295] [2] receiving 285 bytes from ch 0:(^M[WCDMA] FATAL: ^A<80>/4"^K%^A+5 (WCDM:PFault > ExIP
C: Page Fault 15010c @ b759a1, tid=19c001:00268)
[ 13.160000] [WCDMA] +FATAL: ** AMSS Fatal Error **^M[WCDMA] +FATAL: ---------------------------------
----^M[WCDMA] +FATAL: Exp Version : 0xae000002 (0xae000002)^M[WCDMA] +FATAL: RTC : 2009/1/13 14:41:35^M)
[ 13.160000] receiving 7713 bytes from ch 0:([WCDMA] +FATAL: TimeTick : 0xe51c16^M[WCDMA] +FATAL: Fata
lFileName : WCDM:PFault > ExIPC: Page Fault 15010c @ b759a1, tid=19c001:0x10c^M[WCDMA] +FATAL: FormatMs
g : UNKN^M[WCDMA] +FATAL: ErrorTask : ^M[WCDMA] +FATAL: SMSM host state 0:0x829 ^M[WCDMA] +FATAL: SMSM h
ost state 1:0x10929 ^M[WCDMA] +FATAL: SMSM aArm Mask :0x0^M[WCDMA] +FATAL: SMSM aArm pending :0x0^M[WCDM
A] +FATAL: SMSM aArm sleep :0x0 sclk^M[WCDMA] +FATAL: SMSM AT Cmd Ready Flag : 1^M[WCDMA] +FATAL: SMSM D
x spin lock : 0x0^M[WCDMA] +FATAL: SMSM Clkrgm spin lock : 0x0^M

and so on.....

Perhaps I am basing my code on a broken version of kaiser-smd.c, anybody seen this before?
[Tilt, TyTN II, MDA Vario III Android Development] imfloflo:
Nice work DZO can you explain this line please i have the same things on my Polaris
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Dzo, the only kaiser smd code i got working was the board-htckaiser-old-smd.c. ( Problem is I dont know if this is because im using it on a Polaris but I think the smd works the same for Kaiser/Polaris )

But this code isnt using buffer-start-open in smd open.

But some strange this were going on. I could setup a data connection using this smd code. But I couldnt launch android because it would reset.

The only way this code booted was when i put in a new data.gz and it had to be extracted. Maybe it boots because of a time delay or something? Tried to set all kind of delays in the initrd (init/setupmodem), but no luck to reproduce it working.

It crashes as soon as I enable the zygote service.

Hopefully this info can help you a bit.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
PCM audio is only supported on Vogue. It depends on rpc and adsp code, older vogue radios also don't work so the code checks for a recent vogue radio and disables audio if it's not found (this is not audio in calls just for ringing and playing music).

Once the smd code is working we can get rpc working and then the adsp code and then you will have audio.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
http://www.linuxtogo.org/~lgorris/diffs/g1-diff-18-11-08.diff

The smd code i mentioned can be extracted from this diff file. I didnt test all others, it has board-htckaiser-oldsmd.c/kaiser-smd.c and the one i refered to the board-htckaiser-old-smd.c
[Tilt, TyTN II, MDA Vario III Android Development] janditze:
Hi I flashed my Radio to *.*.24.36 and now Android Boots! NICE

But my Touchscreen doesnt work?
[Tilt, TyTN II, MDA Vario III Android Development] lanroth:
I'm using radio 1.71.09.01 but cannot get it to boot.

I downloaded this file:

android1.0_zImage_100109.zip

from this post:

http://xdaforums.com/showpost.php?p=3152576&postcount=1931

and replaced the zImage.bin with the zImage-kaiser from your post

This is the first time I've tried to get this version of Android working (I had a play around with 0.8 a while back) so I might be doing something wrong.

It stops booting with a panic. The last line is:

[ 1.814858] Kernel panic - not syncing: Attempted to kill init!

Thanks for your work on this. Please ask if you need more information.

Regards,

Lanroth
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
I tried booting your new zImage from the above URL, but got the same kernel panic as the poster above.

Radio I used is the 1.65.21.18 (current shipping ATT radio for WM 6.1)

Previously, Android would boot with 1.65.24.36.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Dzo, I just build a new zImage from your latest commit and used my own initrd which has another setupmodem.sh.

smd0 seems to be working, i get creg messages with status 1 and signal strength messages, but using pppd on smd1 doesnt setup a connection.

This is when i disable the zygote service so android doesnt start.
[Tilt, TyTN II, MDA Vario III Android Development] janditze:
I am using the 1.65.24.36 and got the same error with this zImage
[Tilt, TyTN II, MDA Vario III Android Development] adderz91:
Hey guys, thought it might be appropriate to start a new development thread as this one has become very difficult to follow. I'll be around so any new info that needs to be added just PM me, or i might give my username and password to a senior member.

We can let this thread be just for thanking the devs and for the newbies who cant get it running (like the wrong radio etc).

Just a thought...
[Tilt, TyTN II, MDA Vario III Android Development] janditze:
Good Idea.

And if possible always the newest dl-links on top!

And maybe some instructions, how-to, which configuration (ROM etc)

That would avoid half of the traffic!
[Tilt, TyTN II, MDA Vario III Android Development] adderz91:
Well heres the link for the new thread

http://xdaforums.com/showthread.php?t=470649

Whats the consensus for the most stable ROM to run Android off?
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
I've never had a problem booting Android within any of the following ROMS

PDA.Corner

Hyperdragon.III

Duttys Diamond V1

AT&T Official 6.1
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Make sure your MTYPE is set to 1553 in default.txt and the files are all on the SD card.
[Tilt, TyTN II, MDA Vario III Android Development] eezak:
Setting MTYPE to 1553 in default.txt with the new kernel makes my kaiser reboot after the "old radio, no audio" line.

Euro kaiser radio 1.65.24.36

older kernel used to boot to android.

UPDATE: It has to do with DEFAULT.TXT formatting, i saved it as a word file and i m getting some android_power wake up messages

UPDATE 2: it never gets to boot android still displaying android power wake up messages
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
After changing MTYPE to 1553 in default.txt, (and making sure the files were on the card) I got a different kernel panic.

Kernel panic - not syncing: Fatal exception

[2] receiving 12 bytes from ch 0:(@HTCCSQ: 3)
[Tilt, TyTN II, MDA Vario III Android Development] THDBASED:
Got the same error...
[Tilt, TyTN II, MDA Vario III Android Development] Rash1981:
Tried the new zImage with the 1553 adjustment to default.txt and using the packaged stuff from mullin (the megaupload zip)

(still) stuck at

[2.575048] mmcb1k0: p1

And it just stays there, not even a kernel panic

it also mentions it failed to load the sd card

(just like my previous attempt)

I think all kaiser phones are the same; or are there hardware differences between (for instance) the American AT&T Tylt II and T-mobile vario III?

Never had any trouble flashing roms ... what gives?

Is everyone who is getting it to work using the same edition (the tylt II)?

EDIT: Now booting to a black screen after the p1 message, or is that just the booting kernels screen saver?

ps; i know a llittle java, and program php/flash for a living (pure OOP). Anyway i could help out in development or (at the least) testing?
[Tilt, TyTN II, MDA Vario III Android Development] nato2k:
dzo: I booted up your new kernel on the 1.65.24.36 radio. I did have to change the MTYPE to 1553, otherwise i got a kernel panic. I noticed that huge fatal. I also noticed that in android the touch screen behaved very very poorly. Also something that I have not seen before is that I was able to touch the title bar at the top and it would drop down saying something to the effect of no messages.

with 1.71.09.01 I received the same kernel panic as the people before but i left it going for a while and it alternated between a few different messages similar to the ones in previous posts.

[2] receiving 24 bytes from ch 0:(+CREG: 1, DE40, "5688"

[2] receiving 24 bytes from ch 0:(+CREG: 1, DE40, "568E"

[2] receiving 24 bytes from ch 0:(HTCCSQ: 2, DE40 [325.286660]) /this [address] changed over time

[2] receiving 24 bytes from ch 0:(HTCCSQ: 1, DE40 [472.2800000])

these would also vary from 12 to 24 byte packets.

its been going for a while, doesnt look like android is going to boot. im no expert but it looks like its some sort of communication that would normally be in the background once android is running. the address at the beginning keeps getting larger, almost like its some kind of timestamp.

edit: i will double check once i change radios again but I noticed my bluetooth led was blinking and I dont remember that during kernel boot.

edit: same exact behavior with 1.70.19.09 and false alarm on the bluetooth led
[Tilt, TyTN II, MDA Vario III Android Development] mullins07:
Dzo:

I built your most recent code yesterday Dzo and tried it but it reset the device after the 'Old Audio' warning for me.

I am using the ROM that came with the device and the 1.65.24.36 radio, MTYPE=1553 and all files on SD card. I assume the build works for you so what ROM are you using?

I have improved the touch screen code which I will get dcordes to commit this weekend. It can be improved more but it is functional for the moment.

Guys:

Note that any images I posted were based on Vogue code and used MTYPE=1667, for Dzos latest image and from this image forward, the MTYPE should be 1553.

If you are having issues, ensure that this is correct. For either of my 2 previous images, use 1667. For Dzos recent, use 1553.
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
Can you upload your kernel build for kaiser with the latest git revision? tia
[Tilt, TyTN II, MDA Vario III Android Development] mullins07:
This is the latest GIT revision kernel dcordes:

It boots Angstrom but not Android for me.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Mullins what is your problem booting? I can make the latest commit boot on a Polaris with some modifications only not really consistent because of the crashing smd.

Best way to get it started for me is to have the phone and data connection enabled in winmo. It will throw you the errors but from time to time it will continue.
[Tilt, TyTN II, MDA Vario III Android Development] adderz91:
Just to let you know guys, a new development thread has been set up.

http://xdaforums.com/showthread.php?t=470649

Its in the sticky list.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
But we like this one... it has sentimental value.... :D
[Tilt, TyTN II, MDA Vario III Android Development] stylez:
Is this not against the rules and clasified as SPAM?
[Tilt, TyTN II, MDA Vario III Android Development] mikehoot2020:
It absolutely is SPAM, and he has posted the same post in 20 threads today. Take a look at his previous posts... :confused:
[Tilt, TyTN II, MDA Vario III Android Development] msd24200:
ok just tried the build from the new thread and it wont boot on my tilt with pdacorner V16 rom, ill post the error code later when i get home from work. have a few more things i'd like to try as well!
[Tilt, TyTN II, MDA Vario III Android Development] Civil:
Did not work for me

I am using the stock AT&T WM6.1 ROM with Radio 1.65.24.36. I had android booting 100% of the time

touchscreen works, though it's not accurate yet

keyboard works, but if you hold the Fn key down, the numbers are not accurate

any changes I make are maintained across multiple boots

I downloaded this zImage, and I was no longer able to boot Android. I switched back to this version, and I am back up and running (partially).
[Tilt, TyTN II, MDA Vario III Android Development] mullins07:
I am not sure, the device resets after the Old Audio error.

I tried it with a version compiled without the SMD stuff but the same thing happened.

I did not try any more as Dzo is still working on it and he is aware it is not 100% yet.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
OK, I think I've figured out the problem, there's some data right in the middle of physical memory that's shared with the A9 or the hardware so it crashes as soon as it tries to write to that region of memory.

The 1.65.24 radio keeps going (but AMSS is dead) while other radios cause a bus error.

I've changed the kernel to use discontiguous memory around the region and it boots fine into android 1.0 for me on radio 1.71.09.01 with DMA enabled.

I pushed the changes to the git repo and there's a kernel here:

http://cs-alb-pc3.massey.ac.nz/vogue/zImage-kaiser

Things are still broken with this kernel, the TS doesn't work and I don't know if the SMD driver works but at least there are no problems with SD.

UPDATE: just checked and it received a call so SMD works (no audio in calls yet though).
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
I want to test
[Moto G7 Power Questions & Answers] slipchicken:
Hello,

I've rooted my G7 Power and am trying to install a security update as per the instructions here (github.com /topjohnwu/Magisk/blob/master/docs/tutorials.md), but when I try to do the 'Uninstall > Restore Images' step, Magisk gives me the message "Stock backup does not exist!"

I have tried downloading the retail image (XT1955-5_Retail_US_Pie_boot.img) into the internal storage directory on the phone, but that hasn't changed anything. When I search for it in Magisk's 'downloads' and 'modules' the file appears grayed out. Some threads mention TWRP, but I do not have that, nor do I know how to get it.

I am a gigantic noob and need detailed instructions on how to make this 'stock backup' happen so that I can complete the process and install the security update.
[ASUS ROG Phone II Questions & Answers] TheZohard:
Can someone verify if a Type C headphone jack can be used at the side (the orange port)?
[ASUS ROG Phone II Questions & Answers] bluegizmo83:
The orange port is NOT to be used with a type c cable of any kind. The phone specific warns you during setup to never plug a USB type c anything into the orange port. Your suppose to use the port next to the orange one, but NOT the orange one. I think it's actually slightly smaller anyway, as I accidentally started to plug a cable into the orange port and it didn't want to go in.

But as to the USB C headphone jack, I believe it will work just fine in either of the actual USB C ports (bottom or side).
[ASUS ROG Phone II Questions & Answers] cypherflowgamingnation:
Yes during setup, they specifically said "do not connect anything" to the orange port.

The lighting case even has a protection notch over it.
[Samsung Galaxy S7 Edge Questions and Answers] OptimusDarko:
Hi All,

I got FRP locked since developer options were accidentally turned off, first it got loop with that message (Custom binary locked by FRP Lock), so i tried to flash it with the latest ROM, *note that it was 6.0.1 Android, so i got Oreo ROM flashed, after that everything gets worse, there is loop with no command error with huge errors (showed in picture below) , can't access recovery menu, only Download mode works.

Tried many different roms, as i only can flash 6 binary (RP SWREV: B:6 K:4 S:5), with the same result, tried stock rom recovery.img, boot.img flash, no luck, tried combination files, and what not.

Maybe i'm missing something, could yall please help :D

Output from Download mode:

ODIN MODE

DOWNLOAD SPEED: FAST

PRODUCT NAME: SM-G935F

CURRENT BINARY: Samsung Official

SYSTEM STATYS: Custom

FRP LOCK: ON

Secure Download: Enabled

WARRANTY VOID: 1 (0x0500)

RP SWREV: B:6 K:4 S:5

Thank you in advance.
[Samsung Galaxy S7 Edge Questions and Answers] SteveMurphy:
Follow this guide, it will help you. You will need to download an older ROM version for you device than what you had before the FRP lock. So if you were running Oreo, flash down to N or, better yet, MM. Unfortunately you will lose everything on the phone.
[Samsung Galaxy S7 Edge Questions and Answers] OptimusDarko:
I did try older rom, but i can't install other than binary 6, and i can't install TWRP since its FRP Locked
[Samsung Galaxy S7 Edge Questions and Answers] SteveMurphy:
It needs to be the stock ROM for your device, so forget TWRP until you find one that Odin will flash. Once you've booted into the system you can then root and start over again.
[Samsung Galaxy S7 Edge Questions and Answers] OptimusDarko:
Yes, i understand the procedure, the thing is that i can't find stock rom, i have tried almost every latest roms from (imei.info/download-firmware/samsung/samsung-g935f-galaxy-s7-edge/SM-G935F/) 8.0 Android.
[Samsung Galaxy S7 Edge Questions and Answers] SirCoval:
I have the same problem but my binary device is 5 :confused::confused::confused:

Help us please
[Samsung Galaxy S7 Edge Questions and Answers] SteveMurphy:
Check Sammobile; you'll find every ROM released for your devices. One of them definitely will work, you just have to test which one is right for you (both).
[Samsung Galaxy S7 Edge Questions and Answers] shohagik555:
same problam here

some one please help. after flashing rom it say no command
[Samsung Galaxy S7 Edge Questions and Answers] Rapidfayaround:
Did you fix it? Im having the same problem but my binary device is 7.
[Samsung Galaxy S7 Edge Questions and Answers] Youdoofus:
solid advice man! one thing i didnt see mentioned is that SamFirm and the Frija tool will allow you to download archived FirmWare sets without paying. all you need to know id the full file name for pda and csc. Put those in the Frija tool or SamFirm and itll download them. I have personally verified this with both tools
[Samsung Galaxy S7 Edge Questions and Answers] Raydavis1:
help

am having same problem am on binary 8. any solution yet?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] smartt699:
Hey guys, I've order alot of screen protector non fit perfectly. Any links to a good one?

Thanks for your help
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] fubugang:
https://www.amazon.com/dp/B07SG1LBD2?ref=ppx_pop_mob_ap_share

Fits pretty good
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] rounakr94:
I use plastic screen protector called HammerGlass. Its like the Motorola Shattershield and works great with the fp sensor.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] smartt699:
Link
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] rounakr94:
I got it from a local shop. 3 for 3$
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Windroid-user:
Might as well get this for that that price though:

https://s.click.aliexpress.com/e/3cKwuB76

Also why are you making this thread when one already exists in accessories section...
[Galaxy S 5 Q&A, Help & Troubleshooting] XxXPhantomXxX:
Hello everyone,

I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
[Galaxy S 5 Q&A, Help & Troubleshooting] GuestD2287:
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom
[Galaxy S 5 Q&A, Help & Troubleshooting] lecorbusier:
Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).

Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.
[Galaxy S 5 Q&A, Help & Troubleshooting] GuestD2287:
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It

Oh If You Want To Know My ROM I'm Using : Resurrection Remix.
[Galaxy S 5 Q&A, Help & Troubleshooting] yerrag:
Since it's old, possibly hardwqre related.

Recently, I had that with my stock s5 s906s.

I reloaded stock firmware but to no avail.

Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.

But then, it does not always boot well even after giving it a long rest.

I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.

So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.

Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.

It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.