Database Develop

Mistreak7 [miui][cm9]

For the few who wanted MIUI ported to the streak, you may get it soon
MIUI FOR THE STREAK7 IS NEAR OPERATIONAL STANDARDS
STOCK PARTITIONS REQUIRED!
WILL NOT WORK WHEN COMING FROM HS-R1 THROUGH HS-R6 OR ICS-B1 THROUGH B4 FROM GIVEEN
​
This is still a work in progress (that means not everything works, there will be bugs)
:victory:WE HAVE BOOT!:victory: however its followed by many more of them if you lock the device
landscape lock screen and portrait general use... for now
​
3G AND 4G HAVE NOT BEEN TESTED HOWEVER CODE IS IN PLACE FOR THEM
NO CAMERA BECAUSE ITS MORE SH!T TO WORRY ABOUT
TWRP2 or CWM 6.0.1 required ​
as always if you flash it and its now FUBAR its your fault
There is a possibility you will f*** up, if you do the responsibility for repairing it is yours (why would I fix your mistakes)
Bug report is to be user fed. If you have hardware faults or have something not work that you think should work (apart from the camera) then submit a logcat
Thanks to DJ_steve and Giveen for ICS B4, TheManii for porting ICS B4 to stock partitions, a bunch of crazy guys who made MIUI possible and Linus Torvalds for linux kernel​
Download links will probably be up in the next 72hours
English only as XDA is in english only

If flashing through CWM doesn't work then push the files across with adb/fastboot then reboot
complaint report:
1. No GApps: you have to flash them post install. the end.
2. wouldnt it be easier if?: no, this is my way of doing it, be thankful you got this rather than being negative about the way I work
3. camera: decided you can live without it (however I may change my mind at a later date)
4. wifi: untested (though it should work)
5. possible lock ups every 20-30min: its a beta, don't expect it to be perfect
6. 3g/4g: untested
7. bluetooth: untested (though it should work)
8. when will the next rom be ready: see my signature
9. why doesnt the rom boot properly when I have CWM6.0.1.x?: because you probably came from HS-r6, have one of the failed build that I accidentally uploaded or havent cleared your caches
10. whats with the intermittent reboots?: I'm not a f***ing miracle worker here guys, I just do this in my spare time when I have had enough to drink to care about the wants of other people

Now this will be interesting!
Sent from my Galaxy Nexus using xda premium

ElfinJNoty said:
Now this will be interesting!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What's the point in waiting for something you should get the thanks for

looking forward to it!

as are many other people, if there is anything you want included in it then its up to you guys to inform me (gApps will be removed, as always- if I include them then they are there, dont judge me)

Second build is up

I cant download this ROM from Google Docs because of access error, pls check

nicolay.n said:
I cant download this ROM from Google Docs because of access error, pls check
Click to expand...
Click to collapse
link fixed, try now

Flashable from CWM? Any wipes needed?

CWM 6.0.1.x would be worth a try and try wiping dalvik cache and perform a fac reset if it doesnt boot preoperly

Nocturnal_50, tried to flash from HoneyStreak R7 + CWM 6.0.1.0 twice. It says "MIUI ICS port ..." and so on, installing complete and... nothing changes, im on R7 with all of my apps and settings

nicolay.n said:
Nocturnal_50, tried to flash from HoneyStreak R7 + CWM 6.0.1.0 twice. It says "MIUI ICS port ..." and so on, installing complete and... nothing changes, im on R7 with all of my apps and settings
Click to expand...
Click to collapse
did you do a fac reset and clear dalvik?

Nocturnal_50 said:
did you do a fac reset and clear dalvik?
Click to expand...
Click to collapse
Before or after flashing? And factory - user data only or with internal storage?

nicolay.n said:
Before or after flashing? And factory - user data only or with internal storage?
Click to expand...
Click to collapse
try both and all options, if it works then awesome, if not then I may have uploaded the wrong image or have forgotten something in this build

Nocturnal_50 said:
try both and all options, if it works then awesome, if not then I may have uploaded the wrong image or have forgotten something in this build
Click to expand...
Click to collapse
Tried wipe before and after. Still welcome screen from HoneyStreak

nicolay.n said:
Tried wipe before and after. Still welcome screen from HoneyStreak
Click to expand...
Click to collapse
provide a printscreen/picture of your about tablet section so I can see if its flashed any settings across, perhaps flash with twrp/push the rom with adb

Nocturnal_50 said:
provide a printscreen/picture of your about tablet section so I can see if its flashed any settings across, perhaps flash with twrp/push the rom with adb
Click to expand...
Click to collapse
I cannot because it hangs on welcome screen, press on Begin button do nothing. I flashed B4 now

nicolay.n said:
I cannot because it hangs on welcome screen, press on Begin button do nothing. I flashed B4 now
Click to expand...
Click to collapse
how long have you given it on initial boot? try 15min at least

Nocturnal_50 said:
how long have you given it on initial boot? try 15min at least
Click to expand...
Click to collapse
After flashing and wiping it boots in 3 minutes and shows me welcome honeycomb screen, which from i cannot continue to set time settings and begin working with device. I will give them 15 or 20 minutes, if they need, but it boots in 3

What ROM should I choose?

Hello gents and ladies
I have been using the LQB version of the Serbian official Jellybean update since it went out on Sammobile. Though I am experiencing some unpleasant things which I wish to get rid of.
I use this phone for basic things such as listening to music, browsing, texting and calling but I was negatively surprised that this firmware has lots of issues. At first I had problems sending and receiving messages, then the phone started acting weird when I tried to multitask (switching from the music list to the message box) then problems with the camera that has big issues with video recording and also video playback (video playback is a general issue, not a camera specific one). I have also had problems that lead the phone acting however he liked and freezing for long periods of time.
I just wanted to ask: is there anyone here that has the time and kindness to point me a ROM that is ready for daily use and to hand me a completely noobish tutorial on how to install the ROM?
I would also like to specify that I have installed the LQB firmware accordingly - reseted the phone, restored to factory settings and setting the render 2d thing from the developer options.
Thank you very much and I would really appreciate the effort of an useful reply.
Sent from my GT-I9070 using xda app-developers app

Just take look in the Development Section, there's now a lot of ROMs to choose from... You can try Pure Vanilla, JellyMod, HarshJelly or LightJB... they are all good :good:
Or wait for about a week and give my ROM a try

And as for any ROM, the installation is quite simple.
First things first: root your phone.
You can root it by flashing the zip file Shaaan provided in the Original Development forum. Flash it through temporary CWM ( also by Shaaan in that section )
We're getting fired up now.
You're now rooted.
Flash the ROM:
1. Put in sd card
2. Boot into recovery ( vol up + home + power )
3. Select: apply update from external sd
4. Flash temporary CWM
5. Select again: apply update from external sd
6. Search for your file
7. Flash it
To enhamce your performance flash a kernel.
I'd suggest Pure Vanilla with CoCoreE 7.0!
Sent from my GT-I9070 using Tapatalk 4 Beta
---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------
Sami Kabir said:
Just take look in the Development Section, there's now a lot of ROMs to choose from... You can try Pure Vanilla, JellyMod, HarshJelly or LightJB... they are all good :good:
Or wait for about a week and give my ROM a try
Click to expand...
Click to collapse
Cant wait for Sami OS Android and desktop!!!
Sent from my GT-I9070 using Tapatalk 4 Beta

Hey guys, thanks a million for your replies!
I do also have another question: I've lost my SD Card (phone was starting doing crazy stuff so I removed the SD Card and put it in my wallet but I can't seem to find it anymore now). Is there anyway I can root without the SD Card (Odin maybe) ?
Thank you,
Adrian

atomik1337 said:
Hey guys, thanks a million for your replies!
I do also have another question: I've lost my SD Card (phone was starting doing crazy stuff so I removed the SD Card and put it in my wallet but I can't seem to find it anymore now). Is there anyway I can root without the SD Card (Odin maybe) ?
Thank you,
Adrian
Click to expand...
Click to collapse
As far as I know, I don't think you can do it without a sdcard... I have heard of Mobile Odin - but I don't think its compatible with SGSA....

back up all your data like contacts etc..
and wipe cache/data (factory reset)..

jaycm1130 said:
back up all your data like contacts etc..
and wipe cache/data (factory reset)..
Click to expand...
Click to collapse
Hello Jaycm1130!
Can you please expand the information written in your reply please?
Thank you and also, thank you Sami for the fast reply. I will probably wait til my salary kicks in to buy myself a new SD Card!

atomik1337 said:
Hello Jaycm1130!
Can you please expand the information written in your reply please?
Thank you and also, thank you Sami for the fast reply. I will probably wait til my salary kicks in to buy myself a new SD Card!
Click to expand...
Click to collapse
SD cards are not that expensive.
But in CWM you can flash from internal storage too! So try that.
Sent from my GT-I9070 using Tapatalk 4 Beta

Jeroenvk94 said:
SD cards are not that expensive.
But in CWM you can flash from internal storage too! So try that.
Sent from my GT-I9070 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the advice, but:
1. What exactly is the definition of CWM? I have seen it around here but I couldn't figure out what it is.
2. I would like to avoid doing experimental things since it's my only phone and I don't wanna brick it or do permanent damage to it.
Thank you!

atomik1337 said:
Thanks for the advice, but:
1. What exactly is the definition of CWM? I have seen it around here but I couldn't figure out what it is.
2. I would like to avoid doing experimental things since it's my only phone and I don't wanna brick it or do permanent damage to it.
Thank you!
Click to expand...
Click to collapse
CWM aka Clockworkmod Recovery. It's a custom recovery used to take nandroid backup, flashing roms, etc. Search for a thread in general section for more (it pinned up there so it's easy to find). There's another recovery which serves the same purpose as CWM which is TWRP (team win recovery project). You can use either one of those and the only difference, twrp is touch screen while cwm uses the keys on the your device to navigate. However, there's now a cwm touch which basically cwm but you can navigate by touch.
As long as you follow the steps correctly and take necessary precaution, you have lower chance to brick your device.
Hope this helps.

arffrhn said:
CWM aka Clockworkmod Recovery. It's a custom recovery used to take nandroid backup, flashing roms, etc. Search for a thread in general section for more (it pinned up there so it's easy to find). There's another recovery which serves the same purpose as CWM which is TWRP (team win recovery project). You can use either one of those and the only difference, twrp is touch screen while cwm uses the keys on the your device to navigate. However, there's now a cwm touch which basically cwm but you can navigate by touch.
As long as you follow the steps correctly and take necessary precaution, you have lower chance to brick your device.
Hope this helps.
Click to expand...
Click to collapse
Thank you for your reply, it really helped. So the CWM is the recovery mode? (The one that is similar to the download mode?)
I'll probably give it a shot, but I'll have to read the tutorial carefully.
Thanks again!

atomik1337 said:
Thank you for your reply, it really helped. So the CWM is the recovery mode? (The one that is similar to the download mode?)
I'll probably give it a shot, but I'll have to read the tutorial carefully.
Thanks again!
Click to expand...
Click to collapse
Yeah, you can access it by using the three buttons pressed. Here would be a good place to start reading.

atomik1337 said:
Thanks for the advice, but:
1. What exactly is the definition of CWM? I have seen it around here but I couldn't figure out what it is.
2. I would like to avoid doing experimental things since it's my only phone and I don't wanna brick it or do permanent damage to it.
Thank you!
Click to expand...
Click to collapse
CWM is a custom recovery image.
It allows you to flash .zip files which are not signed ( which is impossible in stock recovery ).
There is a tutorial somewhere in the Q&A or General section of the forum you should take a look
Sent from my GT-I9070 using Tapatalk 4 Beta

See my signature for CWM guide...
Sent from CM 10.1

[Recovery][05.04.2014][tf701t] CWM 6.0.4.7 Advanced Edition / PhilZ Touch 6.25.9

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
WARNING...
VERY IMPORTANT:
Some people were having SOUND ISSUES since flashing the new touch recovery mentioned later below. If you do not want to risk having what MAY BE PERMANENT sound issues it is better to not flash this.
Here is an updated philz touch advanced recovery 6.59.0/6.0.5.1 (fully working with touch afaik,no longer officially supported)
Possible past sound issues hopefully unrelated. Here is an updated philz touch advanced recovery 6.59.0/6.0.5.1 (fully working with touch afaik,no longer officially supported)
WARNING:
Possible past sound issues.
Seems to be unrelated.
Sound is ok here.
Read the thread. Decide for yourself.
https://www.dropbox.com/s/6n91kqmwzwe7wdw/philz_touch_recovery.img?dl=0
Thanks to all who helped.
USE AT YOUR OWN RISK.
To reboot into bootloader:
adb reboot-bootloader
To try the recovery before flashing:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Thanks goes to Phil3759. pershoot
https://www.dropbox.com/s/6n91kqmwzwe7wdw/philz_touch_recovery.img?dl=0

Thanks a lot! Every feature work correctly. I needed custom restore, and in this recovery it to be!

I really want to get f2fs support with touch

I would settle for ANY recovery with touch support
Sent from my K00C using Tapatalk

berndblb said:
I would settle for ANY recovery with touch support
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Me Too...i have CWM/Philz with touch on my Note 8.0 and it is very cool but with all the extra features it would be a little tedious to navigate.

Nicely done!!!
Sent from my SGH-T889 using XDA Premium 4 mobile app

Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper

Trel725 said:
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Click to expand...
Click to collapse
Very interesting and the holy grail of the 701! :laugh:

sbdags said:
Very interesting and the holy grail of the 701! :laugh:
Click to expand...
Click to collapse
Just flashed it Thats absolutely fantastic! And they said it couldn't be done!

YayYouFixedIt said:
Just flashed it Thats absolutely fantastic! And they said it couldn't be done!
Click to expand...
Click to collapse
I am SO psyched about this! Can we now get a TWRP for our tablet? We should be able to integrate touch drivers using the same principle into TWRP!

michaave said:
I am SO psyched about this! Can we now get a TWRP for our tablet? We should be able to integrate touch drivers using the same principle into TWRP!
Click to expand...
Click to collapse
It may happen

Trel725 said:
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Click to expand...
Click to collapse
What a relief! THANKS! :victory:

Sigh.
To good to be true?
I did some tests on the Philz recovery, did a nandroid then a factory reset followed by a restore and ended up with pretty distorted speaker sounds. Now, this COULD be unrelated, but I wonder....
Decided to dirty flash CROMi-X 7.0.3 and Aroma completely froze halfway through the installation screens....
I'm back on CWM.... :crying:

berndblb said:
Sigh.
To good to be true?
I did some tests on the Philz recovery, did a nandroid then a factory reset followed by a restore and ended up with pretty distorted speaker sounds. Now, this COULD be unrelated, but I wonder....
Decided to dirty flash CROMi-X 7.0.3 and Aroma completely froze halfway through the installation screens....
I'm back on CWM.... :crying:
Click to expand...
Click to collapse
Sound seems to be pretty good here. Might be unrelated. Maybe Give noozxoide a try to see if that helps belt it out. Tested with speakers, line out, netflix and music

http://forum.xda-developers.com/showthread.php?t=2039716
That is not a root app. Just seems to make the sound clearer and open it up a little.

My recovery is just a demo! I don't have enough knowledge in android recoveries, so I just include rm-wrapper and necessary libs (in /touch_libs). Also /system/bin/linker needed for correct works. Be careful now, and maybe someone else will make really good recovery.

Trel725 said:
My recovery is just a demo! I don't have enough knowledge in android recoveries, so I just include rm-wrapper and necessary libs (in /touch_libs). Also /system/bin/linker needed for correct works. Be careful now, and maybe someone else will make really good recovery.
Click to expand...
Click to collapse
Proof of concept is all we really needed to take off on this! Thank you!
I'm unfamiliar with /touch_libs... Where is that?
Also, which other libs ended up being required?

Maybe the touch recovery is affecting the sound eventually. You wouldn't think but to be safe maybe hold off til the problem is found. Could it be something else. Find out a bit later if it is something else like maybe it is one of the ROMs or a setting. My sound is good afaik.

michaave said:
Proof of concept is all we really needed to take off on this! Thank you!
I'm unfamiliar with /touch_libs... Where is that?
Also, which other libs ended up being required?
Click to expand...
Click to collapse
It is in recovery's root. Extract recovery.img by abootimg and then initrd.img by cpio.

I reinstalled CROMi-X 7.0.3 totally clean, formatted everything but /boot and ext-sd (data/media/ needed a cleanup anyway, he, he), still the same. The speaker seems to be shot. But how installing or using Philz would cause this is beyond me. It's gotta be unrelated....

Can we dual boot on our note 4

So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.

egren58 said:
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
Click to expand...
Click to collapse
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.

glm0025 said:
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
Click to expand...
Click to collapse
I swt tw as primary patched cm12 and gapps. But recovery was freezing so i tried to manually paych the file as stated. But than when i got to flash vie recovery it says fail. I have no idea what to do since i did exactly as it said.

My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4

BACARDILIMON said:
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
Click to expand...
Click to collapse
Good idea. But for some reason i cant find the dam thread now. Wtf.

egren58 said:
Good idea. But for some reason i cant find the dam thread now. Wtf.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3058835
All u need
BAD ASS NOTE 4

http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can confirm this works in T-Mobile note 4. You just have to follow the steps.

It works trust me, I'm a senior member

I managed to get it to flash but....
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?

Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
It should when you reboot the device.

Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...

suhridkhan said:
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
Click to expand...
Click to collapse
you cant dual boot stock Samsung roms for some reason...

frr1 said:
you cant dual boot stock Samsung roms for some reason...
Click to expand...
Click to collapse
Just got it working, after so much trouble. Tmobile Note4 running TW Rapture as primary and CMRemix as secondary. Still no luck with the second step of patching, but manual patch has worked. This one is a better written guide, I suppose.
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/

I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211

jazzmachine said:
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
Click to expand...
Click to collapse
AOSP roms has very small footprint, that's why they are insanely fast... The roms itself with gapps only takes about a gigabyte, if it's CM or other aosp roms. If you dual boot 2 TW roms, of course it's gonna take huge space. It also depends on how many apps you are going to install on the second rom

[WIP] [Discussion] Multirom

I have started looking into this recently and is WIP yet.
What works:-
1. MROM recovery, we can use as regular recovery as well, no issues
2. We can install secondary ROMs and store them in internal/external memory
3. Swapping Primary ROM with any of the installed secondary ROM
What doesn't work:-
1. Auto-boot dialogue during boot, i guess this is not working in MM roms, seems source bug. But we can live without it.
2. The big thing, booting into secondary ROMs.
What we need the most is the working kexec hard boot patch, working on this one still. I need help from kernel developers too to look at the patch and see that we can have a working patch.
The kernel patch commits are:
https://github.com/premaca/android_...mmit/8da6b7c9ef5abc67543ae26079a9ae5bd46baa3a
https://github.com/premaca/android_...mmit/fab89b4609ab42960854588b03066615db831d47
Downloads: https://www.androidfilehost.com/?w=files&flid=57465
Installation:
- install multirom zip through recovery
- install recovery.img through fastboot
- to get rid of multirom, install uninstaller zip through recovery
- install regular twrp recovery through fast boot, if you prefer it.

Wow

Okay. Here is the latest status on this -
1. Auto-boot dialogue appears now, but immediately gets cancelled and started booting into Primary ROM. Alternative is, to chose option 'long-press-vol-up' while rebooting gives you mrom menu, this works fine. The regular option, i will try fixing this anyway
2. The big thing, kexec.. It is really buttfire to make this work, but i made some progress. Now, if I select reboot to Secondary, it goes to Mi-Logo and stuck (multirom code detected some kind of race-condition, i need to look into and solve this). But then, a long-press-power-button reboots the device, and indeed into the secondary ROM. So the kexec patch seems to start working and may require little refinement;
So i need to solve few glitches here and there, and probably we may have a working mrom in future.

Awesome wrk sir btw u can get help from @TheStrix he had compiled multi rom recovery AFAIK he may help u wish u a gud luck sir

salahXDA6805 said:
Awesome wrk sir btw u can get help from @TheStrix he had compiled multi rom recovery AFAIK he may help u wish u a gud luck sir
Click to expand...
Click to collapse
Hopefully I have crossed all those levels, now i m into fully device specific stuff which i alone have to do, or some one having our device and expertise in kernel code. Anyway, i may be few hurdles behind to get this fully working. Lets see;

BTW sir im waiting for the com.android phone fc on boot to be fixed soon did u find any fix for it?

salahXDA6805 said:
BTW sir im waiting for the com.android phone fc on boot to be fixed soon did u find any fix for it?
Click to expand...
Click to collapse
Ha ha.. wrong thread, Ya. I never get time for that, But will fix it eventually. The msim commit in telephony has caused this, i need to figure out way to fix that. Probably have to maintain the fix locally :crying: apparently as other devices (gzr) are not having this issue.

DELETED

Check this out https://youtu.be/e1pTIxU_rKA

premaca said:
Check this out https://youtu.be/e1pTIxU_rKA
Click to expand...
Click to collapse
Victory..! [emoji7]
Thanks for your hardwork..!
Sent from my 2014818 using Tapatalk

premaca said:
Check this out https://youtu.be/e1pTIxU_rKA
Click to expand...
Click to collapse
thank you ...you are always awesome...
and when you guys are releasing it..???