yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] whobutme:
So I am curious did you unlock developers mode and get a mock location app to spoof your location, devs use that all the time to test applications and make it seem like phone is in different locations. You can also download apps from the play store that do the same thing. Rooting a Samsung phone is a bad idea because Knox is tied into a hell of a lot on Samsung phones and it also opens the door for warranty issues.
[Samsung Galaxy S22 Ultra] SergiuNik:
Can't you use Mock location apps to fake your location? Would not be easier?

It's under developers option and you can download (at least you could some years ago) directly from Google Play a Mock location app.

I mean, if you can fake location in this way for Google Maps, maybe it will work for Pokemon Go
[Samsung Galaxy S22 Ultra] Genebaby:
Hi, what happened with Expansys? I had them down as a decent store.
[Samsung Galaxy S22 Ultra] numloxx1978:
Agreed. I haven't rooted a phone since the S8 plus.. there is no need to anymore really. And especially not for CHEATING IN A GAME!!!

I play Ingress a lot and would never cheat in it.

And once you root it, it'll never be original ever again. It breaks Knox.
[Samsung Galaxy S22 Ultra] BillGiovanni:
I ended getting a Google pixel 6 pro and rooted it. Just having issues now with mock location jumping to my real location. I'm using fake mock locations for LSPosed and gps joystick. Can anyone help me with that?
[Samsung Galaxy S22 Ultra] mookiexl:
Sounds good but you can't on OneUi 4. Only black screen action
[Samsung Galaxy S22 Ultra] MuhannadYT:
Try sending them a email prob a bug, gl
[Samsung Galaxy S22 Ultra] BillGiovanni:
So spend money on the game and have it cheat you instead? 🤔😂 No thanks man.
[ASUS ZenFone 8] NTICompass:
I just got a Zenfone 8, and I updated it to Android 12 (UL-I006D-ASUS-31.1010.0410.43-1.1.25-2202-user.zip). I installed Nova Launcher, and I cannot widgets.

Video: https://drive.google.com/file/d/10N5oYJ3oG_wWFjtLtrKT5C0awkV49P75/view?usp=sharing

Looking at Nova's logs, I see:

java.lang.NullPointerException: Attempt to read from field 'com.android.server.appwidget.AppWidgetServiceImpl$ProviderId com.android.server.appwidget.AppWidgetServiceImpl$Provider.id' on a null object reference

So, it seems ASUS's Android 12 build is missing something from its settings app.

Does anyone else have an issue adding widgets? I tried Lawnchair and have the same issue. ASUS Launcher obviously works fine.
[ASUS ZenFone 8] M1chiel:
I have experienced no problems adding widgets with the same firmware version: neither on Nova nor on Microsoft launcher.
[ASUS ZenFone 8] NTICompass:
Really? Weird. I've had issues on Nova and Lawnchair.

Could it have something to do with my phone being rooted?

There's lot I can try, it's curious that I'm having this issue though. Clearly, I'm doing something wrong, but I don't know what.
[ASUS ZenFone 8] M1chiel:
Mu guess is that you accidentally uninstalled an essential app while debloating. Could that be the case?
[ASUS ZenFone 8] NTICompass:
I didn't "debloat," per se. Though I guess I did disable some apps that I don't use. I didn't think I disabled anything too important, but I can check that.
[ASUS ZenFone 8] Josipeen:
Actually NTI, the same thing just happening to me without root on my ZP8.

I've been on A12 for a couple weeks, but my battery life was dismal. So yesterday, I decided to do a factory reset. Battery life improved, but now I cannot place widgets in third-party launchers. (The launcher app's stock widgets do seem to work, but that's it.)

I attached a quick video showing the issue. (Side note – notice how mine says, "Settings has stopped" when I try to add a widget.)

The real pain is this did not happen until I factory reset the other day. In other words, I

was

able to place widgets in Nova on Android 12 without issue.

I reached out to Nova, who told me that this is an issue with all third-party launchers on the Zenfone 8 running A12. I then tried placing a widget on a few others and found the same problem.

Nova then sent me to talk to Asus, who told me, "Sadly we wouldn't be able to assist with a 3rd party launcher."

5-star response. Anyway, I'm just glad to see others bringing this up. Hopefully Asus makes a fix for the bug.
[ASUS ZenFone 8] NTICompass:
I switched to using Niagara Launcher, and I am happy and am able to live without widgets... but it would be nice to use them. I assumed re-installing Android 12 would fix it, but I didn't try that. I'm hoping ASUS eventually pushes a new Android 12 build, and that installing that will fix whatever is missing.

In my video, I have the same issue where it says "settings has stopped."

EDIT:

So, I went to ASUS' website and found the download for Android 12 (WW-31.1010.0410.43). And in the description, I see:

I don't know what version of Android 11 was on the phone when I got it. I got the phone, booted it up, skipped through the setup screen and immediately upgraded to Android 12. Then I unlocked the bootloader, thus factory resetting the phone and then I went though the setup for real. After that, I installed Magisk.

So, maybe I needed to upgrade to the latest Android 11 first? But, that makes no sense as the Android 12 upgrade worked. No idea why I (and you) are having this issue and others aren't.
[ASUS ZenFone 8] Adaoh:
I was able to update to .43 from android 12, but maybe it was no supposed to work lol
[ASUS ZenFone 8] Josipeen:
I'm not sure. But it's super frustrating because I was on A12 without an issue like this. As far as I know, only the Asus ZenUI Launcher allows me to have widgets now.

What part of a factory reset—weeks after I installed the latest update—would cause widgets to stop working in third-party launchers? So annoying. Lol
[Samsung Galaxy S21 Ultra] |||||:
Hi Guys,

Since I came from a S10, where I had an extra Bixby Button, wich I remapped then to pause/play - wich was also really useful:

to take or end calls fast or quickly stop the audiobook or music, when someone talks to me etc.

Or to quickly activate the flashlight.

So after looking for a while, I found a good way:

Just install this app:

Button Mapper: Remap your keys – Apps bei Google Play

Remap Hardware-Tasten starten jede App, Verknüpfung oder Aktion

play.google.com

And configure your buttons as you wish.

There is also an root Function, wich allows you to use it while its on screen off, wich is really nice.

Just check the screenshots here or in Playstore, there are many other things you can do.

For me personally I choose:

VOL UP HOLD = fast forward

VOL UP 2x = flashlight

VOL DOWN HOLD = rewind

VOL DOWN 2x = PAUSE/PLAY or take/end a call fast

I might change it to next song or before song, but for now, this is good for me, as Iam listining more audiobooks.

Ok have a nice one.

Best regards

|||||
[Samsung Galaxy S21 Ultra] shaharofir:
You can achieve all of that and more using Tasker.
[Samsung Galaxy S21 Ultra] richhaynes:
As the other commenter stated, Tasker is a much better app for this as it is popular and well maintained so bugs are few and far between.

As for needing to remap buttons, I find the buttons do exactly what I want them to do already and thats with bixby button remapped to be a camera button. Can do this in bixby without any extra apps.
[Samsung Galaxy S21 Ultra] basem55:
@richhaynes

Yes i use Tasker but i think Tasker can't detect those buttons by its own, so i use (AutoInput) plug in to trigger those buttons.

If I'm wrong please tell me how.

Thanks.
[Treble-Enabled Device Guides, News, & Discussion] 971shep:
My local box store had a PrePaid TCL A30 at a good price which I bought with the intent of building/installing my own privacy firmware. It comes with Android 11 so it should be treble compatible.

TCL A30 specs at gsmarena

Background. I currently run GrapheneOS on a Pixel 3A with F-Droid apps only and have built firmware with OpenWRT (MediaTek MT7621a based router build accepted), and test built GrapheneOS,, Treble_experimentations and Lineageos.

I like the barebones minimalist approach that GrapheneOs took with the included apps with a few added apps from F-Droid.

I think there are several ways to reach that goal.

GrapheneOS has a generic build but I am worried about the lack of Mediatek roms. Still, if it is truly Treble compatible, theoretically, it should work. Anyone tried a GrapheneOS GSI?

phhusson treble_experimentations with FOSS seems ideal although I would like to substitute either Vanadium or Ungoogled Chromium for browser/webview.

Has anyone gone down this road?
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
Hello guys,

After a little research, I have successfully ported

MIUI 13 (v22.2.17)

to

Mi 8

. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help

TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:

1) MIUI 13.0.10 for Mi 8

2) POCO OS for Pocophone F1 (choose the latest)

3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)

4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)

AND HERE WE START:

--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]

--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]

--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]

ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);

When done, we add the above vendor files and META-INF folder to (another) archive

--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:

* overlay

* etc/selinux

IN THE END WE HAVE...

> To flash system.img as image ["base system" step]

> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]

> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]

> To flash the extracted boot.img ["base boot" step]

> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.

Due to deodex, the whole boot should be finished in approximately 4 minutes

MISSING FEATURES:

> No NFC support

> No multilingual rom (but there are also some MIUI R roms here)

SPECIAL THANKS TO:

> romKTpro (for POCO OS)

> UOTAN (for vendor files)

> Tech Karan (for his similar guide)

> and to all the other developers who made the required and useful tools and mods
[Xiaomi Mi 8 Guides, News, & Discussion] nsfnd:
Link for this this "Tech Karan (for his similar guide)"?
[Xiaomi Mi 8 Guides, News, & Discussion] nsfnd:
I was able to install it mate thanks.

Working fine, very smooth.

Mi Login doesnt work tho, which i dont mind.
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
You are right, sorry for forgetting this link. I have just edited the first post
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
Yes, I have found this bug, too. This happens because there is the same one on Poco F1 (base rom).

Also, there are some missing applications, which can be installed as normal .apk files from APKMirror:

-> Mi Browser

-> Mi Cleaner

-> Mi Scanner
[Xiaomi Mi 8 Guides, News, & Discussion] nsfnd:
They made an Android 12, MIUI 13 version for Poco F1.

I tried to do the same technic explained above for that.

But Jancox Tools failed to extract with errors.

(imgextractor.py and ext4.py, NameError: name 'xattr' is not defined)

Link for the rom.

PocoOs Stable Channel (Official)

╭━┳━┳━┳━╮╭━┳━━╮ ┃╋┃┃┃╭┫┃┃┃┃┃━━┫ ┃╭┫┃┃╰┫┃┃┃┃┣━━┃ ╰╯╰━┻━┻━╯╰━┻━━╯ MIUI 13.0.4 EU rom Based on Android 12, Code name:Ignition🔥 ======================= Maintained by @facerracer4u ======================= About PocoOs: PocoOs comes with all poco standards We do not include harmful mods, and we...

t.me

Maybe you want to check it out.
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
Unfortunately, we have to make a compatible vendor.img for Mi 8. Otherwise, every MIUI 13 (Android 12) ROM cannot be booted (the existing vendor files are compatible with Android 11 MIUI ROM's). I will try to port /vendor, but I am not promising anything

At least, there is a compatible kernel (No Gravity v3.x.x)

Edit: NoGravityKernel does not support /system_ext (so for most MIUI S ROM's it is not compatible)
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
OK, ιt's been a long time since my last post, but I have found a bootable Android 12 version of MIUI 13, but I have not managed to fix the common bugs from Pocophone F1:

<!> audio

<!> camera

<!> slow motion while watching videos (due to the audio bug)

Also, this ROM does not have NFC support (Poco F1 does not come with)

In order to install it, I have flashed:

-> the ROM (by deleting the first line in /META-INF/com/google/android/updater-script

-> permissiver v5

-> dfe (disable forced encryption)

-> XDKernel-2.6
[Xiaomi Mi 8 Guides, News, & Discussion] lycanwrath:
Well done, That's great!!!

Hoping to see a fully working android 12 and MIUI 13 soon on our MI8 :)
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
So, after replacing some audio policy files from /vendor/etc, the sound comes out normally. However, I still have bugs such as slow videos and silent sounds coming as media when earphones are not connected. Are there some files at /vendor/etc to be replaced? I haven't found anything else, yet

(Also, I haven't looked for the required files for NFC support)
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
OK, now it's ported with no bugs.

Missing features: NFC support (Due to my inexperience, I cannot make bootable system and vendor .img files by using image kitchens and it's more difficult to set the correct permissions to files in the /bin folders from recovery)

The files to be changed are mentioned in this uploaded .txt file
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.

Instructions:

We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel

We mount /vendor

We flash the patch
[Xiaomi Mi 8 Guides, News, & Discussion] lycanwrath:
Thanks for sharing your progress, its exciting indeed.

Is it possible for you in the future to share a simpler way for us non advanced users to easily upgrade to MIUI 13, e.g through recovery zip from TWRP.
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
Because I don't own these ROM's, please check some Telegram channels. The file name of this one (with the mentioned changes) may remind you something
[Xiaomi Mi 8 Guides, News, & Discussion] alexgugla12:
Hello, is this manual suitable for mi mix 3?
[Xiaomi Mi 8 Guides, News, & Discussion] lycanwrath:
Hello I am new to this, but I already have an unlocked bootloader.

Can you please confirm :-

1. Which tool I need to use to flash the ROM .img files, Xiaomi Flash Tool?

2. Which latest MIUI 13 ROM is most suitable, POCO OS •13.0.12.0 EU [ IGNITION 4.0 ].zip?

3. Which beryllium2dipper-patch.zip patch I need to use for the Mi 8?

4. Only bug is NFC right? Will audio, camera, safetynet, banking apps, xiaomi account and cloud work?

Edit:

I am not sure if the steps are correct and which beryllium2dipper-patch.zip patch file I should use

View attachment 5728291
[Xiaomi Mi 8 Guides, News, & Discussion] Advanced Gears:
To begin with, the steps are not difficult. we have to flash the following files:

--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img

as images from a recovery which supports cust images, such as OrangeFox.

--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files

--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..

(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.

(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)

Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.

When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.

Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
[Xiaomi Mi 8 Guides, News, & Discussion] lycanwrath:
Thanks for the explanation, I have flashed successfully with minor tweaks.

To resume:-

Prerequisites:

1. MIUI13 Android 12 firmware (POCO OS IGNITION 2.0) feels more responsive

2. Phone ROM with unlocked bootloader and OrangeFox recovery.

3. Phone ROM must be on latest Official ROM (Global/China)

4. Phone ROM must not encypted or /data formatted

Boot to OrangeFox recovery:

1. Flash .img files; system.img, cust.img (system_ext), vendor.img, boot.img (POCO OS IGNITION 2.0)

2. Flash .zip files; DFE (disable forced encryption), latest stable beryllium2dipper-patch, permissive and XD kernel

3. Reboot phone to system and enjoy

Edit:

I have reverted back to my old ROM (xiaomi.eu MIUI12.5} as I feel its more polished and optimised but its nice to see Android 12 with MIUI13 fully working ported to the Mi 8.
[OnePlus 6T  Questions & Answers] wiiznokes2:
Hello,

I got the error " error installing zip file " while a try to flash oos 11.1.2.2.

I try sideload instead by it Failed instantly. I tried to format data and wipe without any change. I also tried to boot other version of TWRP (I currently use a custom version of TWRP 3.6.0), but I always got a Crash Dump error.

I was able to install rom with this version of TWRP before and I have wanted to install PixelExperience but I have forgotten to flash oos 11.1.2.2 before and i think is that witch broken TWRP.

I also tried to reinstall TWRP.

Any ideas on this?
[OnePlus 6T  Questions & Answers] Brettroth:
I had that error before from a bad copy of oos. I would download it again and copy to USB again if that's what you're using. Also use this twrp to fastboot boot it works I actually just had to do it a min ago.
[OnePlus 6T  Questions & Answers] wiiznokes2:
Thank you, I will try that. Can you send me a link of oos that I should install, I'm not sure if it's that one https://www.oneplus.com/fr/support/softwareupgrade/details?code=PM1574156215016 .

Also, shoud I use "flash current TWRP" before flashing the ROM?
[OnePlus 6T  Questions & Answers] Brettroth:
Yeah definitely flash current twrp first. The oos you used is not the latest I'll just upload it. The latest and last ever update from OnePlus is 11.1.2.2
[OnePlus 6T  Questions & Answers] wiiznokes2:
That worked, thank a lot!
[OnePlus 6T  Questions & Answers] Brettroth:
You're welcome
[POCO M3 Questions & Answers] NuxiPoco:
How To Fix Gyro Delay No root on poco m3?
[POCO M3 Questions & Answers] GargantuanOrangutan:
i guess you can try calibrating it by dialing * # * # 6484 # * # * on your device but let's face it, the sensor itself is pretty trash so idk how much that'll help.
[General Topics] ansar.ath.gr:
Mobile Vista 3.00 Premium Rom Structure

Rom Structure

This is the structure of Mio_A701_WWE_WM6.1_CEOS_5.2.20755_Build_20755.1.0.0_Mobile_Vista_3.00_Premium:

***************

OEM

***************

->ExtendedPKG

->LangDB

->NEWAPPS

->NEWDRIVERS

->NEW_Lang_0409

->OEMAPPS

->OEMDRIVERS

->OEMMISC

->OEMOPERATORS

->OEMVERSION

->OEM_DPI_96

->OEM_DSM

->OEM_Lang_0409

->OEM_Modem

->OEM_USB

->OperatorPKG

->OperatorPKG_PT

->SecurityOff

OEM.cer

***************

SYS

***************

->.ROM

->.VM

->Ansar Tweaks

->AutoRunCFG

->AUTOUPDATE

->Autoupdate_Lang_0409

->Backup

->Base_DPI_96

->Base_dpi_96_resh_240_resv_320

->Base_Lang_0409

->Base_Lang_0409_DPI_96

->Base_Lang_0409_DPI_96_RESH_240_RESV_320

->BaseApps

->BaseAppsFiles

->Bluetooth

->Bluetooth_Lang_0409

->BROWSING

->Browsing_DPI_96

->Browsing_Lang_0409

->BROWSINGCORE

->BTDUN

->Bth_A2DP

->Bth_A2DP_Lang_0409

->Bth_HID

->Bth_HID_Lang_0409

->Catalog

->Catalog_Lang_0409

->CommonNonEA

->DRM

->Enterprise

->Enterprise_DPI_96

->Enterprise_Lang_0409

->Enterprise_Lang_0409_DPI_96

->Entertainment

->Entertainment_DPI_96

->Entertainment_Lang_0409

->Entertainment_Lang_0409_DPI_96

->FWUPDATE

->Fwupdate_Lang_0409

->GPSID

->INTERNETSHARING

->IPSECVPN

->IPSECVPN_DPI_96

->IPSECVPN_Lang_0409

->Keyboardskins

->MediaOS

->MediaOS_dpi_96_resh_240_resv_320

->MediaOS_Lang_0409

->MediaOSFiles

->Metadata

->MSXIPKernel

->MSXIPKernelLTK

->NetCF 3.5

->Office

->Office_DPI_96

->Office_Lang_0409

->Office_Lang_0409_DPI_96

->OneNote

->OneNote_lang_0409

->OS

->OSFiles

->Phone

->Phone_DPI_96

->Phone_dpi_96_resh_240_resv_320

->Phone_Lang_0409

->Phone_Lang_0409_DPI_96

->PhoneRedist

->PhoneRedist_DPI_96

->PhoneRedist_Lang_0409

->PhoneRedist_Lang_0409_DPI_96

->Pocket Screen Capture

->ppgprov

->Redist

->Redist_DPI_96

->Redist_dpi_96_resh_240_resv_320

->Redist_Lang_0409

->Redist_Lang_0409_DPI_96

->RUNTIMES

->SampleMusic

->Shell

->SIM_TKit

->SMIME

->SMS_Providers

->SQLCE

->SqlCeMobile

->SqlCeMobile_Lang_0409

->SQM

->Transcriber

->Transcriber_Lang_0409

->Transcriber_Lang_0409_DPI_96

->Vista Driven

->Vista Themes

->WelcomeCenter

->WelcomeCenter_Lang_0409

->WinCENLS_WWE

->WindowsLive

->WindowsLive_DPI_96

->WindowsLive_Lang_0409

->WWAN

Regards, ansar

_________________

HTC TyTN II owned, thnx to my friends

IPL CPLD-8

SPL 1.0.OliPof

CE image CE OS 5.2.20755 Build 20755.1.0.0 D3D M2D Mobile Premium Vista 3.00

Mio A701

UBoot R48

CE image CE OS 5.2.20755 Build 20755.1.0.0 Mobile Premium Vista 3.00

GSW 3.2.2_3.1.00.12 - SDK.003P1.01a

Mio C510 and C220 for dev, thnx to L and H.

Mio P350 and P550 for dev, thnx to D and S.
[General Topics] ansar.ath.gr:
Reserved

Hi,

This is reserved for future use

Regards, ansar

_________________

HTC TyTN II owned, thnx to my friends

IPL CPLD-8

SPL 1.0.OliPof

CE image CE OS 5.2.20755 Build 20755.1.0.0 D3D M2D Mobile Premium Vista 3.00

Mio A701

UBoot R48

CE image CE OS 5.2.20755 Build 20755.1.0.0 Mobile Premium Vista 3.00

GSW 3.2.2_3.1.00.12 - SDK.003P1.01a

Mio C510 and C220 for dev, thnx to L and H.

Mio P350 and P550 for dev, thnx to D and S.
[General Topics] PTomos:
I'll try this now !!

tell you later what the veredict :)

thanks for the great job
[General Topics] Belzebuth.:
What is your verdict?
[General Topics] drizztje:
Thanks bro. Nice work. I'll try it now
[General Topics] robertobarreiro:
Great rom

I´ve installed yesterday this ROM on my MIO a701 and works perfectly!

follow the instructions and worked like a charm!

The Rom is beatiful and very fast, just noticed a small delay on the access of the fotos and videos and music on the first access but after thar its great.

i´ve still not tried all feaures but for now it´s great!

Great Job Ansar :D
[General Topics] Belzebuth.:
What did you use to flash the new ROM?
[General Topics] Gazzz:
ansar, great little rom here mate. Been using it for the past two days.

Couple of problems though.

When receiving sms via touchflo, there is no way to 'save as read' without going into the inbox. This means that on the screensaver etc etc it's saying that the sms you have read, is new.

Any it is DESTROYING batteries??!! A full charge of my 1450MaH battery lasts only 7 hours, most of that on standby.