yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] congogr:
The ROM is amazing, Thank You for that!

I DO have an annoying problem though...

I was st*pid enough to enable the "Phone Scheduler" which is on my Main Programs Menu which allows to switch the Phone functionality On and Off on certain times during the night.

How could one Disable it???... It seems I cannot use the "NIL:NIL" setting or something... PLEASE if anyone know, let us know. :)
[Touch Cruise ROM Development] s_john8686:
I see you asking around for the same question in different posts :o

It's amazed me too, I think we just pick the stable rom (whichever it's) with the desired ram you would want. But bear in mind one thing :

Roms with higher ram (100+MB) can't accept new radio rom with 1.59.xxxx. It only can take on radio with 1.58.xx.xxx

- Bepe's rom (older build) without Manila2D is the best to me, high ram version.

- Maxniper rom (newer build) with Manila2D is also quite stable to me, lower ram version.

- c_shekhar rom (newer build) with Manila2D with hgih ram, but has device lock problem.

Your choice :)
[Touch Cruise ROM Development] c_shekhar:
Yes you are right. do it with NIL:NIL . Or simply kill the notification using the dotfred task manager...and you are done...
[Touch Cruise ROM Development] Olioaglio:
cshekkar is using (as explained in first post) the 1.60 drivers in OEM section

of this rom. All ROMs which using (older) 1.60 drivers give the 101.xx MB of

RAM, but aren't compatible with the 1.59.xx Radio ROMs.

The newer drivers 3.13 or 3.18 give only 84.xx MB of RAM, but they

are compatible with 1.59.xx Radio ROMs, but not with the older ones.

That's it.

Though it would indeed be very interesting to find out, why the newer OEM

drivers "eat" 16MB more valuable RAM. For me the most disapointing fact is,

that the 1.60 drivers aren't comaptible with the amazing 1.59.44.02 Radio.

I used this with another (own) rom build and loved it as it had (has) the

lowest memory drain and very good performance for me.

The cream pie would be a (modified) 3.13+ OEM driver set which would give the missing 16MB, but I have no idea if this would be pssible to do....

Olioaglio

101MB
[Touch Cruise ROM Development] amarguli:
Lite Version

Hi C_Shekhar,

Thank you for the lite version. Testing it right now. So far found only one minor bug: reset command in start menu is not working since it relies on FdcSoft task manager that was removed.

One small question: is SIPChange_Fix.CAB required also for lite version?
[Touch Cruise ROM Development] c_shekhar:
Sorry fellows. While stripping the ROM I forgot about that (Reset). It is a ver minor fix which I can post quickly.

2. No, you dont require the SIPChange_Fix in this.
[Touch Cruise ROM Development] martint235:
Device lock

Has anyone figured out a way of locking the device yet? I've tried various ways but the only one that seems to work is by having a lock option on my SecondToday screen which isn't ideal.

Thanks for all the hard work, other than this small problem, the ROM is excellent.
[Touch Cruise ROM Development] peter01:
Wow! c_shekhar

LITE version is out. But I find that there would be very few people who would be enjoying the LITE version. The programs and tools you have provided in your full version are very useful and I am enjoying every part of it.

BTW the guy @devdaeshan has sent the donation? Oh sorry sorry why am I asking this?

The comments were very strange from him..
[Touch Cruise ROM Development] NeoTO:
c_shekhar, thanks. It's a nice build. But I can't say it is the fastest. For the last few months I have been using one of the bepe's distributions and it was lightingly fast (I mean UI response).

I would just like to know, how to disable HTC's system/ring volume dialog. Default quick menu is much better, I think. Another thing I find annoying is the dialog (with big icons) that appears after clicking on the status icons. How to disable this?

Keep up with good work!

Regards,

NeoTO
[Touch Cruise ROM Development] tacginc:
Yes.

I like the battery Icon, but I had to go back to 755 release becasue this one was acting up. Is there anyway to get just the battery icons zip of for install with 755 release?
[Touch Cruise ROM Development] ultracy:
VTCall

Hi bro CS,

I am using your fabulous 1.60, however i have just realize that it doesnt come with VT Call? i have tried to use another phone to 3G call in, it rangs on his phone but not mine. i also cannot fine the VT Call function in call history or under Contacts. please advice if i have mislooked. thank you for your super rom! cheers
[Touch Cruise ROM Development] c_shekhar:
This ROM has onlt 2G dialler. For having 3G dialler you have to separately install the suitable dialler using a cab from this forum...enjoy..
[Touch Cruise ROM Development] medkid:
just curious , how can you create 4 icons in 1 row like this ?

:)
[Touch Cruise ROM Development] c_shekhar:
I hope you like them....:)
[Touch Cruise ROM Development] ultracy:
I have tried three types of the 3G dialer from forum, but non of them looks as cool as the ROM 2G dialer. eg. 3Litxx, it caused the battery icon, call history, answering UI and the keypad change. Which no longer give that kewl feel. would you be building a 3G dialer soon? looking forward to a kewl 3G dialer from you!!! Happy new year
[Touch Cruise ROM Development] tytn88:
loved your rom, it's been good til now, the screen is not responing like it should, sometimes not at all, not sure what's going on with it, hard reset and i'm stuck at the screen alignment, can't not align the screen. any ideas of what i can do? thanks
[Touch Cruise ROM Development] jpl69:
Do you have the tranparent Screen protector on it ? i have a friend that had the same problem and once he removed it the problem disapeared. Let us know.
[Touch Cruise ROM Development] tytn88:
i don't have the screen protector on it, it's gotten worse now, the touch screen is not working at all, only able to use the wheel, which i'm limited as to what i could do with the phone, what should i do? thanks
[Touch Cruise ROM Development] Scalpos:
Well, I hope for you it is not a hardware issue...

I'm not using this ROM, but actually the wheel and the right direction of my Polaris are defective, and I bet it is hardware related...

Simply try to do an entire backup (Spb, Sprite or Resco Backup) of your device and see what happens after a hard reset before blaming the ROM itself.
[Touch Cruise ROM Development] Tunndoc:
Fantastic ROM

Hi, thanx. Fantastic Rom indeed. I've been using your rom for a while now. No troubles so far except

1. Bluetooth settings fail to show add new device command in the bluetooth > devices tab.

2. I paired my Vista laptop and it syncs fine. though the laptop is not visible on

bluetooth>devices tab.

3. It turns on Ok and is discoverable by other devices, the problem comes when i NEED to pair the wireless headset, as I can't choose the headset in the Polaris Bluetooth settings as it doesnot give me n option to add new devices.

Anyone else had the same problem. I have already hardreset twice. The options comes on after a hardreset but disappears after a couple of pairings. Any solutions? Please help.

Ciao
[Touch Cruise ROM Development] besly:
Hello,

I just test this rom and I have to say what is really good.

Question: Is it that we can change the keyboard by a azerty ?
[Touch Cruise ROM Development] nemiers:
Best rom so far!

c_shekhar any new roms sheduled? ;)
[Touch Cruise ROM Development] c_shekhar:
Coming up with build 21014 AKU 1.6 soon. Testing right now on my device and every thing seems to be working fine so far.

Core of AKU 1.6 is reportedly supposed to be faster than all the builds of AKU 1.5.
[Touch Cruise ROM Development] jpl69:
C_shekhar let me tell you that i'm using build 21014 with PhamQuang's rom using the 3.18.457 version 45, latest radio and it's very stable, no need to use old kitchen for this. It means more battery life and improved signal.
[Touch Cruise ROM Development] amarguli:
Do you plan to use 1.60 or 3.18 drivers?
[Touch Cruise ROM Development] c_shekhar:
No 3.16 or 3.18 for now. I an glued to 1.60 drivers.:D

Dont want to have meagre 25-30MB prog Memory and live in tension. With 1.60 drivers and 1.58.XX.XX Radio I have been enjoying ~50MB Prog mem and rocking radio performance. No regrets at all.

I dont want to be crazy for seeing the higher numbers on my "Device Info".;)
[Touch Cruise ROM Development] koekwouskoekwous:
Can you test the lock? I like your ROM, but I've removed it because of the lock problems.

Get the GPS a quick fix with this build?
[Touch Cruise ROM Development] amarguli:
Excellent! That's what I wanted to hear :D

Eagerly waiting for the new ROM. I hope you will make light version as well.
[Touch Cruise ROM Development] c_shekhar:
Lock is working perfect. Dont worry... GPS was never a problem with any of my ROMs. ;)
[Touch Cruise ROM Development] alinescoo:
I have tested TranMinhMan's ROM with Core 21109 and this Core seems the fastest I've tried. What is courious is that I have smooth scroling in Settings. I can say that from all the ROM's I tried, your's with the 1.60 drivers was by far the fastest and smoothest. Looking forward for your next release which I hope it will be this days (you did day that everything works fine ;)
[Touch Cruise ROM Development] Kirgas:
Waiting for your ROM as well

Go for it :-)
[Samsung Galaxy Tab A7 Lite] AndriusDo:
Hi everyone,

I have an odd issue with my tablet. Suddenly the touchscreen becomes glitchy.

This situation just started without any reason.

The touchscreen not responding. Can not swipe to unlock. I need to press the power button 10 - 15 times until I can swipe and unlock it. The tablet will work as normal while you using it. You can turn it off, restart will work as normal. But if you leave your tablet unused for 30 min or longer you can not swipe to unlock it again. I need to press the power button 10 - 15 times again until I can swipe to unlock it again.

I did restart, factory reset, and updated the system, but nothing helped.

Does anybody have any ideas?
[Samsung Galaxy Tab A7 Lite] striker59:
I would contact Samsung, might have to send it to them.
[Samsung Galaxy Tab S8] metorm:
I updated my s9 ultra to Android 13 a few weeks early. Then I tried to get the root back following the below thread.

https://xdaforums.com/t/root-guide-for-galaxy-tab-s8-s8-s8ultra.4423095

On that day, the newest magisk version was 25.0, I followed all the steps in the above thread but the device was still bricked (boot loop).

I searched the error log and figured out that this was due to something called "avb flag":

Samsung system init check fstab avb flag cause boot loop · Issue #6141 · topjohnwu/Magisk

Device: Samsung Tab S7 Plus (T976B) Android version: 12 Magisk version name: 25.2 Magisk version code: 25201 For some reason, samsung decided to make their /system/bin/init check for avb flags in f...

github.com

Since I don't have much time on this, I simply did a factory reset and kept using the tab without root.

I am actually not sure whether the "avb flag" is the root cause. The only thing I am sure of is using magisk 25.0 and s8ultra android 13 ROM leads to a boot loop.

Today, I found that magisk is now updated to 25.3, and nobody here mentioned the boot loop.

So, I want to know whether magisk 25.3 is working well with the newest ROM. If it works OK, I will give it another try.
[Samsung Galaxy Tab S8] FerretallicA:
I have a Tab S8 Ultra which was on Android 12 / OneUI 4.1 rooted / Magisk. I just finished updating it to Android 13 (image SM-X906B_2_20221208191241_81t9w4gald_fac) without any dramas. I did a factory reset before flashing the patched AP, not sure if that helped avoid any potential bricks or you were just unlucky.

I'm only on Magisk 25.2 though - I don't see the 25.3 that you mention anywhere. So make sure you're downloading from topjohnwu's GitHub page, not some other sketchy place. That might be a factor.
[Samsung Galaxy Tab S8] metorm:
Well, I think “25.3” is a typo. I always download the magisk APK from github. I also tried a factory reset.

May the issue is already fixed in a way. I'll try it again some time.
[Android Q&A, Help & Troubleshooting] bvk182:
why isn't thr a similar program like SPSS for Android?

i mean user friendly with similar UI
[Android Q&A, Help & Troubleshooting] alecxs:
maybe because most android devices are smartphones? most smartphones don't have physical keyboard or mouse.
[JAMin, XDA Neo, S200 Software Upgrading] coolb4all:
Hi All,

I've tried to upgrade the ROM of my QTEK S200.

It got completely stuck!!! I had to remove the battery. Now it stays black. Even a hard-reset does nothing. No bootloader, no white screen, nothing. It's like the device doesn't recognize the battery anymore. Same problem with another battery. When I connect the power supply, the light stays red for 5 seconds and then goes out again. No charging (orange) light.

Does this mean that the device was short-cutted (hardware problem) or can this be fixed with some manipulation?

Anybody an idea how I can fix the hardware (if broken) myself? Can't be to difficult if it just blew a fuse ;-):confused:

Thanks
[JAMin, XDA Neo, S200 Software Upgrading] NEO130:
If the accu not charge, I think he is dead. You need a new one. For flashing new rom, you need a good acco over 50 %. Than you go to bootloader modus and flash a WM5 Rom WM5Rom.
[JAMin, XDA Neo, S200 Software Upgrading] timmymarsh:
Yep, hes dead alrite, make a good paper weight:D sorry bro...
[JAMin, XDA Neo, S200 Software Upgrading] coolb4all:
not the battery

of course I tried a new battery

same problem
[JAMin, XDA Neo, S200 Software Upgrading] NEO130:
Can you make a downgrade to WM5 ? Ist the battery charged now ?
[JAMin, XDA Neo, S200 Software Upgrading] JustBored:
DC Adapter 4,5 V

I had the same problem.

Remove the battery and connect the pin nr 1 (nearest to the cam) to + and the pin nr 5 to -. I think 3,7 to 5 V is ok. Then bootloader and connect to computer.

Don't blame me if anything goes bad ;-)
[JAMin, XDA Neo, S200 Software Upgrading] coolb4all:
how to proceed?

I've tried to do as explained...

I've taken an old charger (5v) and connected the cables (black/white striped to 1 and black to 5). I'm not 100 percent sure about + and -, but normally black is always -, if I'm not mistakin'

What should happen? How should I proceed?

My device does nothing... No light. Power button does nothing, hard reset does nothing.

Does this procedure work with a QTEK S200?

Maybe the charger (old gsm) is too old or broken?

Maybe + is black...

Sooo many options ;-)
[JAMin, XDA Neo, S200 Software Upgrading] JustBored:
Worked on mine S200

Of course You must know if the adapter is working and +/-.

When I connected 1 to + and 5 to - I could operate the mobile as if the battery was mounted and working.

My problem began because the battery isn't charging in bootloader mode.

And I'm still stuck there... Because it's a G4 device flashed with G3 SPL... Anyone got a suggestion how to solve this?
[JAMin, XDA Neo, S200 Software Upgrading] Bynx:
I Did the same thing '''''HELP""":mad:
[JAMin, XDA Neo, S200 Software Upgrading] deltav13:
What you should do

Keep the device on for 2 hours connect it to the electricity.

Install the original rom with the PDA connected like that to the PC, if it does not enter the Rom update continue trying by doing a hard reset with the stylus and pressing the left com button on the left side of the device, then retry the rom install, if it says unable to connect continue trying, using the procedure i explained before, thats what i did when the same stuff happen to me i was without my device working for a month, now i´m using WM6 with the Diamond Rom, so its possible, to do this you just have to keep trying.
[JAMin, XDA Neo, S200 Software Upgrading] srbwap:
my prophet is block and after try of hard reboot is dont turn on.. its not turn on on any way, no detect charger ether ( no red led ) battery was almost full when its go off..

plz help, can i try 1-5 pins solution?
[JAMin, XDA Neo, S200 Software Upgrading] timmymarsh:
My friend. A few people have tried the pin method and one or two have succeeded. IMHO i would not try it, for fear of frying your phone, yourself or starting a fire.

Take out the battery for a good couple of hours. Take out SIm card and SD card. Put battery back in and try to charge for at least 5 hours, even if the light does not show (might just be LED issue).

Then see if you can start in boot loader, u now how to yes? (keep camera button pressed, soft reset with stylus, then let go of camera button after few sconds). What happens?
[JAMin, XDA Neo, S200 Software Upgrading] coolb4all:
pins to power

I've tried connecting the extreme small pins to the (big) cables of the charger but nothing happens over here. The screen stays black.

To All,

Any hints on how to connect these cables to the pins, without the fact that they're constantly coming off the pins and constantly touching other pins?

You try and tell me about your experience ;-)
[JAMin, XDA Neo, S200 Software Upgrading] coolb4all:
revive prophet revive ;-)

I was just playing with my qtek when I noticed that after connecting and disconnecting it to the AC for 5 times or so (with red light going on and off for a second), it tries to startup, but drops dead after a fraction of a second. Damned ;-) No chance of going into bootloader.

Almost there ;-))
[JAMin, XDA Neo, S200 Software Upgrading] timmymarsh:
keep it plugged in for about 5 hours, dont play with it or turn it on lol, give a go unless u have done already and just havent said :D
[JAMin, XDA Neo, S200 Software Upgrading] coolb4all:
Direct Connection to 220v doesn't work

The workaround of connecting the pins directly to the charger doesn't seem to work on a QTEK S200 G4.

Since mine is a G4, I wasn't lucky... I'm left with a cut charger cable.

I'll try to charge it for 5 hours but since no led is going on I don't think this will have any effect.
[JAMin, XDA Neo, S200 Software Upgrading] deltav13:
Listen keep it plug in to the electricity for 12 hours, then try to put it in bootloader mode by pressing the, com button on the left side of the device after you hard reset it, with the stylus after you manage to enter the bootloader mode, you only need to follow the steps described on several posts on the forum. :D
[JAMin, XDA Neo, S200 Software Upgrading] deltav13:
if nothing works connect the device and try to install the original rom, my device is a g3 so i´m not sure if the g4 works the same way.
[Huawei Watch GT 3] steveboss:
View attachment 5830233

➡️uniQue - touch of perfection for Huawei Watch 3/Pro, GT 3/Pro, GT 2/Pro.

NOW ON HUAWEI HEALTH STORE...

🔸Search "uQ003o" or "steveboss" on store. Thank you for support.

🔸Direct links: (open only on mobile with Huawei Health installed)

🔸I am also preparing my own website, where all watch faces will be in one place...

🔸Alternatively you can follow my facebook page...

Mod edit: DL links removed
[Huawei Watch GT 3] Badger50:
Thread closed. @steveboss, please check your PM inbox.

-Regards: Badger50
[Vivo X90 Pro Plus] Kenshin1870:
I see this option on this device, and I got connected to my network (200mb) and I got a neighbor with 40mb plus, I connect the device to both of them but I run a test and only see my 200mb.

I am doin something wrong or I need something else? In theory i can accelerate to 240mb but it is not.

Thanks
[Google Pixel 7] manjaroid:
For anybody with unlocked bootloaders and root no longer passing the usual 2 out of 3 Play Integrity checks, maybe this helps.

After flashing yesterday's TQ1A.230205.002 update, MEETS_DEVICE_INTEGRITY consistently failed which was something new. Sometimes it would pass after repeated attempts and/or clearing the app's storage, but mostly it failed. Long story short, it's now passing after 1) switching from safetynet-fix 2.40 back to Displax's modified 2.3.1; and 2) uninstalled and reinstalled the Integrity Check app. Either one, the other or both seems to have helped. Occasionally I'll get a fail but it's mostly passing now instead of the other way around.
[Google Pixel 7] V0latyle:
Yeah, a lot of people are having issues with USNF 2.4.0.
[Google Pixel 7] jofa news:
Hi,

may I ask exactly which version you went back to:

- v2.3.1-MOD_2.1

- v2.3.1-MOD_2.0 or

- v2.3.1-MOD

Greetings
[Google Pixel 7] manjaroid:
I went back to 2.3.1-MOD_2.0 since it was already on the phone. I didn't even know about MOD_2.1 until you mentioned it, so that's what I'll do next. I didn't know about 2.4.0 problems either. I guess I need to get out more often, subscribe to an extra forum or two. :unsure:
[Google Pixel 7] salamdiab:
i had the same proplem

buy aftel clear data and cash memory about 3 times for google service and google play store and last google wallet , evrey think get bake norml
[Google Pixel 7] jofa news:
I have read about the problems with USNF 2.4 here

MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
[Google Pixel 7] seanho12345:
Did you reboot the phone after clearing it? I've been wiping it a few time but it still not seemed to work.
[Google Pixel 7] salamdiab:
this morrning evrey thing not work

i try a lot of thing but no help
[Google Pixel 7] manjaroid:
All seemed fine yesterday after installing safetynet-fix-v2.3.1-MOD_2.1 but it's a bigger mess today. Unlike yesterday, Safetynet CTS profile fails and Play Protect shows device not certified. I even managed to get an API throttle error from the Integrity Check app, which presumably means I'm SOL for a while.

More gory details...

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-150
[Google Pixel 7] Pixel86:
Hiding the Magisk app solves the issue. Just hide then reboot phone. Profit.
[Google Pixel 7] manjaroid:
Thanks to @Displax everything passes with safetynet-fix 2.3.1-MOD_3.0.

Release v2.3.1-MOD_3.0 · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Release v2.3.1-MOD_3.0 · Displax/safetynet-fix

github.com
[Google Pixel 7] Basselsakka:
Thanks, its working 👍
[Google Pixel 7] BesoC:
Magisk hidden, Zygisk enabled, safetynet-fix 2.3.1-MOD_3.0 installed

Force stop, clear cache and storage for Google Play Services, Play Store and Wallet, reboot.

Repeat 4 times

Still Play Integrity API Checker shows red cross for MEETS_DEVICE_INTEGRITY

EDIT:

Uninstall USNF, reboot, check with Integrity API Checker - got 3 red crosses, predictable.

Reinstall USNF, reboot - MEETS_DEVICE_INTEGRITY is red :(
[Google Pixel 7] manjaroid:
Is Enforce DenyList enabled and DenyList configured?
[Google Pixel 7] BesoC:
DenyList is enforced, There are Google Play Store and Wallet in DenyList
[Google Pixel 7] manjaroid:
Try clearing storage for the Integrity Check app or uninstall and reinstall it. Avoid checking too often also, the app gave me an error about limits and throttling when problems were ongoing a couple days ago. Sorry, I don't have any other ideas.
[Google Pixel 7] BesoC:
Still not working, but thanks for your efforts :)
[Google Pixel 7] Bxperiaz3:
Whats working on pixel 7 pro for me

SafetyNet displax mod 3.0

Shamiko module

Magisk hide

All Google apps hidden in deny list

Deny list enforced disabled

Clear cache from wallet and playstore

Reboot
[Google Pixel 7] BesoC:
Thank you for your advise. Did exactly as you wrote, still MEETS_DEVICE_INTEGRITY is red :(
[Google Pixel 7] Lughnasadh:
Maybe try the new USNF mod Displax just put out...

v2.4.0-MOD_1.0
[Google Pixel 7] BesoC:
Wow, that did the trick! Thanks a ton mate 🙂👍🥳 I didn't even have to clear wallet's storage
[Google Pixel 7] DroidRommer:
After trying everything to get CTS profile match this is what worked for me! Thanks
[Google Pixel 7] salamdiab:
good evning

i had to say that is somthing not good with USNF 2.4.0 mod 1

or USNF 2.3.1 mod 3

for USNF 2.4.0 mod 1 somtimes the meets dvice intgreaty work somtime red

i try alot of times

for USNF 2.3.1 mod 3 else somtime work and other no, pluse somtimes google search not work until i do clear storge and cash

after feb/update not quite good all the USNF mod
[Google Pixel 7] jhwbg:
Hi

The latest version is working for me v2.4.0-MOD_1.1
[Google Pixel 7] salamdiab:
Hi.. i will check now..

Thanks