[ROM][v2.1][WIP] FirefoxOS dualboot with Cyanogenmod 10.2 for SGSII (i9100 /i777)

[ROM][v2.1][WIP] FirefoxOS dualboot with Cyanogenmod 10.2 for SGSII (i9100 /i777) - Galaxy S II Android Development

[ROM][v2.1][WIP] FirefoxOS dualboot with Cyanogenmod 10.2 for SGSII (i9100 /i777)
UPDATES
30 - Jun - 2014
- Updated to lastet Gecko and Gaia versions (v2.1!!). CHECK THE NEW INTERFACE!!
- Some stuff is broken like SIM recognition... but it's a common error for most of 2.1 devices. There's a patch on the way.
- Colors swapping issue
Download: ffos-sgs2-jb-30-Jun-2014.zip
23 - Feb - 2014
- Updated to latest Gecko and Gaia versions (yesterday builds). Lot of new cool stuff!!
- Graphic errors fixed!!! Now it's *really* smooth
Click to expand...
Click to collapse
Hi there!,
I've been working on supporting Samsung Galaxy S2 (mostly i9100, partially i777) with FirefoxOS for a long time, and I would like to share my work with you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dualboot
General info
System files (/system) are installed on the HIDDEN partition () so they DON'T conflict with CyanogenMod 10.2 ROM.
I use CyanogenMod Kernel with no modifications, all dualboot stuff is based on initramfs (indeed is based on Siyahkernel approach).
How to dual-boot
It's a rudimentary mechanism so far. You have to: adb shell, and type (no matter where ROM you are):
If you want to boot into CM10.2 - Note: If you don't have installed CM10.2, please don't do this!!:
Code:
# cr.sh 1
If you want to boot into FirefoxOS - Note: it can be any number different from 1, i.e: cr.sh 3, cr.sh 5:
Code:
# cr.sh 2
Your device will reboot in this very moment, and will boot into the selected ROM.
The first time, FirefoxOS ROM will be booted by default.
Downloads
I'm providing a CWM installable .zip so you can test it without having to build the whole system.
File: ffos-sgs2-jb-22-Feb-2014.zip
File: ffos-sgs2-jb-30-Jun-2014.zip
Click to expand...
Click to collapse
Installing
Boot into recovery mode with CWM.
Make a backup (as always).
Save your backup in other place than your device (no matter what partition you are using), please.
adb push ffos-sgs2-jb-version-2014.zip /emmc
Install zip from sdcard
Insall zip from internal sdcard
Select the .zip file
Install it!!!
Click to expand...
Click to collapse
In case you want to go further and compile everything from scratch, I would suggest you to see my G+ post with detailed instructions on how to build it by yourself.
Of course, all my work is available under my Github account.
Features at a glance:
Dual boot with CM10.2 (if you have installed it)
Rooted
Adb Insecure
FirefoxOS v1.4
What's not working:
Flickering graphics
Camera
Mobile data
Wifi on i777
Hardware Home button on i777
Do not expect a very stable version!
Thanks to
Cyanogenmod, cause it's amazing work on this device despite Samsung, I'm using your kernel.
Siyahkernel, cause my dualboot solution is inspired by yours.
All the people helped me testing very first releases, risking their devices .
Enjoy!
_AtilA_ (@longor)
XDA:DevDB Information
[ROM][v2.1][WIP] FirefoxOS dualboot with Cyanogenmod 10.2 for SGSII (i9100 /i777), ROM for the Samsung Galaxy S II
Contributors
_AtilA_
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Alpha
Created 2014-01-16
Last Updated 2014-07-02

I Download and make video what looking that

I install rom and after booting i dont have desktop, only black screen, power button work, after pull display power menu, volume buttons also working, after pull screen display volumebar, but desktop is black :/

arekmelerski said:
I install rom and after booting i dont have desktop, only black screen, power button work, after pull display power menu, volume buttons also working, after pull screen display volumebar, but desktop is black :/
Click to expand...
Click to collapse
The first .zip I provided was wrong, if this is the one you've installed (it's less than 100 Mb) download the new one (just click in the link) and install it again.

Nice work mate! Much appreciated

No, i have this issuses on ffox-sgs2-jb-14-Jan-2014.zip, size 197mb
I install 2x, wipe, format itd

I run again FF OS, same black screen, no desktop but i have sms notifikation, but can't i touch this ;/

This ROM is missing the data file and that is why no desktop comes up.
Sent from my XT1058 using xda app-developers app

arekmelerski said:
I run again FF OS, same black screen, no desktop but i have sms notifikation, but can't i touch this ;/
Click to expand...
Click to collapse
hmmm... I'm having a lot of fun trying to figure out wich files are necessary and which are not... Anyway, I think I solved the problem... new .zip uploaded.
I hope this one works

t989
any chance of seeing this on a T-989 galaxy s2 ? I've been very curious about firefox OS

when camera and mobile data will be fixed ? just asking no hurries because i wanna try it

amirfida said:
when camera and mobile data will be fixed ? just asking no hurries because i wanna try it
Click to expand...
Click to collapse
Working on it! I can't give you a date right now. I'll probably fix the camera first, release a new updated version (Gaia/Gecko) and then fix the mobile data.
Stay tunned

_AtilA_ said:
Working on it! I can't give you a date right now. I'll probably fix the camera first, release a new updated version (Gaia/Gecko) and then fix the mobile data.
Stay tunned
Click to expand...
Click to collapse
yahoo actually mobile data is not really much much important okay well how to dual boot ? i mean does this zip file include dual boot thingy ? means cm 10.3 is already there or i need to follow some steps ?

how to install ? it says you need cm 10.1 installed and i installed then also tried but its same

amirfida said:
how to install ? it says you need cm 10.1 installed and i installed then also tried but its same
Click to expand...
Click to collapse
Where does it say you need cm 10.1?
All the instructions are in the first post: http://forum.xda-developers.com/showpost.php?p=49484692&postcount=1
If you want dualboot (it's not mandatory) you cannot install CM10.2 after installing ffos.zip, cause the boot.img (zImage on SGS2) I modifed would be overwritten with the one from CyanogenMod, wich is not dualbootable.
So:
1º - Install CM10.2
2º - Install FFOS

expo1122 said:
any chance of seeing this on a T-989 galaxy s2 ? I've been very curious about firefox OS
Click to expand...
Click to collapse
Oh! I only have a I9100 for testing
You'll have to try and cross your fingers
Anyway, if you can install CM10.2 you could proably run FFOS without problems..

_AtilA_ said:
Where does it say you need cm 10.1?
All the instructions are in the first post: http://forum.xda-developers.com/showpost.php?p=49484692&postcount=1
If you want dualboot (it's not mandatory) you cannot install CM10.2 after installing ffos.zip, cause the boot.img (zImage on SGS2) I modifed would be overwritten with the one from CyanogenMod, wich is not dualbootable.
So:
1º - Install CM10.2
2º - Install FFOS
Click to expand...
Click to collapse
oops sorry i meant 10.2 i installed cm 10.2 first and then firefox OS it says that i need cm 10.2 installed which i have already i asked you on google plus and you said me to follow some procedure but where shall i follow it in recovery or booted up device ?

amirfida said:
oops sorry i meant 10.2 i installed cm 10.2 first and then firefox OS it says that i need cm 10.2 installed which i have already i asked you on google plus and you said me to follow some procedure but where shall i follow it in recovery or booted up device ?
Click to expand...
Click to collapse
Your device with CM10.2 booted up

_AtilA_ said:
Your device with CM10.2 booted up
Click to expand...
Click to collapse
yeah it did

okay i managed to install it
now review time
first of all this rom is still sluggish i don't know why it's like that despite being dual core mobile it's still laggy :/ when laggines will be fixed ?

Related

[BETA V1][STABLE] [08/10/2013] Firefox OS [This is NOT Android] [Fixed mobile data!]]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU CAN NOT DUAL BOOT THIS.
This is a project page to get the Galaxy SII i9100 back to a tier 2 device,
it is currently using the latest Firefox OS source code from the v1.1.1.
We've done it guys! We have reached the first milestone, BETA! This ROM is now considered stable enough for daily use.
- Microphone (needs testing!)
- Wrong DPI
- Hardware acceleration
- Camera
- Others I may not have discovered yet.
Installation Instructions said:
1. Go to cwm recovery and do a complete backup of your phone.
2. Extract the content of firefoxos_beta_v1_10102013.zip file to your hard drive, using your preferred rar/zip archiver (ex: WinRAR)
3. From your phone, go to mounts and storage, and select the last option, mount USB storage.
4. Copy the folder you extracted from the archive 2013-10-10.16.12.39 to your sdcard in the folder clockworkmod/backup (if you don't have that folder, create it)
5. Wipe data/factory reset (make sure you have a backup)
6. From your phone go to backup and restore -> restore -> 2013-10-10.16.12.39
7. reboot system now
Click to expand...
Click to collapse
As a final note DO FRICKIN' NOT format your /system, /data or /cache partitions
through the Firefox OS CWMR if your device is susceptible to a eMMC brickbug.
You have been warned.
This release is purely for testing, I need to know what does and doesn't work.
But I'm no programmer, fixes may take a while to be released unless others decide
to contribute.
Download links are here: REMOVED
XDA:DevDB Information
Firefox OS - GT i9100, a ROM for the Samsung Galaxy S II
Contributors
abtekk
ROM OS Version: 4.0.x Ice Cream Sandwich
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Must be rooted with Clockwork Mod Recovery
Based On: B2G - Boot2Gecko
Version Information
Status: Beta
Current Beta Version: v1
Created 2013-10-07
Last Updated 2014-02-03

Reserved
Download mirrors:
REMOVED

Reserved

Thanks for reviving the project mate Almost forgot about this OS until I saw this thread :good:

-Grift- said:
Thanks for reviving the project mate Almost forgot about this OS until I saw this thread :good:
Click to expand...
Click to collapse
No worries, I'm happy to be working on it

Preliminary/quick sneak peek into the alpha...
The Setup Wizard cannot seem to detect the Time Zone and whatnot in the specific section, but the time adjusted itself after the phone was setup
Messages work (send and receive)
Sound notifications work. Not sure for music/audio.
Importing of contacts via vcf works
Notification Center/Status Bar is laggy.
No built in screen off when in call ( I assume proximity is not working?)
Calls do not seem to work
Lock/unlock/power button works
Menu and Back button are useless (I assume we can use these somehow?)
For an alpha, this is good progress.If we get HW acceleration working, it would be much bearable. As much as I want to be a tester for it, I'm afraid that will have to wait. Good luck with the project!
EDIT @abtekk once I find the time, I'll try to setup a dualboot with it as well and see what I can do.

!n0x said:
Preliminary/quick sneak peek into the alpha...
The Setup Wizard cannot seem to detect the Time Zone and whatnot in the specific section, but the time adjusted itself after the phone was setup
Click to expand...
Click to collapse
I think that's to do with geolocation. I'll take a look, though.
!n0x said:
Notification Center/Status Bar is laggy.
Click to expand...
Click to collapse
I believe that is hardware accel.
!n0x said:
No built in screen off when in call ( I assume proximity is not working?)
Click to expand...
Click to collapse
Probably not.
!n0x said:
Calls do not seem to work
Click to expand...
Click to collapse
No microphone support, that's why.
!n0x said:
Menu and Back button are useless (I assume we can use these somehow?)
Click to expand...
Click to collapse
Firefox OS isn't designed for use of these buttons. I could maybe bind them to another function.
!n0x said:
Good luck with the project!
Click to expand...
Click to collapse
Thank you.

Is possible to install as second rom?

marbutina said:
Is possible to install as second rom?
Click to expand...
Click to collapse
You can with Siyah Kernel.

abtekk said:
You can with Siyah Kernel.
Click to expand...
Click to collapse
Thanks. Maybe I try it then.

marbutina said:
Thanks. Maybe I try it then.
Click to expand...
Click to collapse
Great, let me know how you get on.

!n0x said:
Preliminary/quick sneak peek into the alpha...
EDIT @abtekk once I find the time, I'll try to setup a dualboot with it as well and see what I can do.
Click to expand...
Click to collapse
Sounds good. Could you report the bugs you found in to the bug tracker, please.

WiFi now works.
The camera is next on my list.

It is possible dual boot with dorimax kernel?

hocruxx said:
It is possible dual boot with dorimax kernel?
Click to expand...
Click to collapse
You can dual boot with any kernel that has the dualboot feature. Siyah is the recommended, though.

Ok i will try as secondary rom

I tried with the latest Dori 9.41 stable, and it doesn't seem to boot to the Firefox partition properly. Needless to say, I'll have to try Siyah later.
EDIT: Seems that prealpha 2 is way smaller than 1. Why is this so? Do we flash it on top of alpha 1 or is it good to go for clean flash?

!n0x said:
I tried with the latest Dori 9.41 stable, and it doesn't seem to boot to the Firefox partition properly. Needless to say, I'll have to try Siyah later.
Click to expand...
Click to collapse
Siyah must be the only compatable one, then.
!n0x said:
EDIT: Seems that prealpha 2 is way smaller than 1. Why is this so? Do we flash it on top of alpha 1 or is it good to go for clean flash?
Click to expand...
Click to collapse
Just manage to purge useless crap out of the second release. It's good for a clean flash .

https://bugzilla.mozilla.org/show_bug.cgi?id=755405
This might help you with the microphone
Sent from my MB886 using xda app-developers app

wildchild048 said:
https://bugzilla.mozilla.org/show_bug.cgi?id=755405
This might help you with the microphone
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thank you. I'll see if I can sort it.

[DISCONTINUED][ROM][4.4.2 - UEU2CNE2][N5110] Terok Nor v3 Release 6 - 06/30

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
***Disclaimer***I am not responsible if you break your stuff. Use at own risk!
I am not a developer and do not pretend to be one. I'm an Android enthusiast.
Why no Aroma?
Because I've made this ROM to my liking for myself, removing apps I'd never use. I have no need for a customized installer. I'm sharing this with you all because I'm sure there's somebody else who wants a simple, optimized ROM with the basic, stable features. If you want more options or customizations, this ROM isn't for you.
No complaints
I do this in my spare time.
Special requests
I'll accept special requests, but that doesn't mean they'll come true.
Bug Reports
Bug reports are welcome! Keep in mind: This is mostly stock and most bugs will be official firmware bugs.
Updates will come along when I have time and when I see something I'd like changed :good:
ROM: Terok Nor
Based on UEU2CNE2 US Official Firmware
DeKnoxed system and kernel
Deodexed
build.prop improvements
Slimmed down
Busybox
AOSP 4.4 KitKat system sounds
Added AOSP 4.4 ringtones, alarms, notifications, and UI sounds
Removed power on sound
Custom, smaller S Pen pointer
Scrolling Wallpaper enabled in SecLauncher3.apk (TouchWiz Launcher)
Android L Keyboard
Galaxy S5 Boot Animation
SELinux: Permissive
Special Feature: @civato SphereKat blazing fast kernel with S Pen fix! For more info on his kernel, please see the SphereKat thread!
*
Samsung Milk Music - Powered by Slacker
- Milk is supposedly available for all Galaxy devices, except it's not available for all Galaxy devices. I've added it here for you all to enjoy
*
Amazon Kindle for Samsung
Special Note:
* Images are copyright to their respective owners
A GT-N5110
One of the latest recoveries that supports Andoird 4.4. I recommend the latest PhilZ recovery: Found here, flash in ODIN
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
IF YOU DO NOT MEET THESE REQUIREMENTS.. STOP HERE!
A full wipe is only necessary if coming from a different ROM, including Terok Nor v2. All updates to v3 r1+ can be dirty flashed (unless otherwise noted).
1. BACKUP BACKUP BACKUP!
2. Flash
3. Reboot
(click the image ^)
MD5 hash: 25e41bad0695fc543dd75bde681fefb0
Don't forget to hit the thanks button!
XDA:DevDB Information
Terok Nor v3, ROM for the Samsung Galaxy Note 8.0
Contributors
MrHyde03
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: 4.4.2 Bootloader and TZ
Based On: UEU2CNE2 Official 4.4.2
Version Information
Status: Stable
Created 2014-05-26
Last Updated 2014-08-18

2014-06-30
Release 6
Added Android L Keyboard!
Added Galaxy S5 Boot Animation
Updated @civato 's SphereKat to v4.0
2014-06-10
Release 5
Removed S Note 3.1 (If you want, the install this APK S Note 3.1 APK
Rebuild on UEU2CNE2 US Official Firmware (XAR)
Now released with @civato's SphereKat kernel! Make sure you hit THANKS in his SphereKat thread and send him a beer!
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
2014-05-27
Release 3
Corrected issues brought on by R2 where the device would not boot after a clean flash.
2014-05-26
Release 2
Enabled Scrolling wallpaper in SecLauncher3.apk (TouchWiz Launcher)
Corrected Text Cursor offset in framework-res.apk, Thanks Civato
2014-05-26
Release 1
Initial release
Civato
All others who've made modding Android possible
Thanks to all who have donated I hope I can continue bringing a stable, smooth experience to the great people here at XDA :good:
Each * represents an additional donation! Much appreciated!!
rfb813 *

There are currently two versions of S Note installed. The orange-red icon is the new version which is available on the GS5 as a "Galaxy ESSENTIAL". The brown icon is the stock Note 8 version. I may remove one of them in future updates.
STOCK KERNEL AND RECOVERY
Download this zip file and extract. The kernel (boot) and recovery are in their own .tar.md5 archives. Flash each in ODIN.

yay!

@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.

civato said:
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
Click to expand...
Click to collapse
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.

Updated to Release 2! Check Change Log for details.

Clean flashing to R2 is broken. Only works if dirty flashing. Because of this I've pulled R2 from the download. Go back to R1 if you're having issues with booting. I know what the issues are, I just don't have time tonight. It's late.
I've udpated the download URL to reflect R1.

MrHyde03 said:
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Click to expand...
Click to collapse
Yep they should release it . But some delay is expected.

Fixed the issues from R2. R3 is out and stable.

I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app

glockman4519 said:
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Yep.. that was my fault.. sorry. I didn't properly recompile a few APKs, but we're all good now.

Release three working fine! Thanks and have one on me:4C4716763M934291T.

rfb813 said:
Release three working fine! Thanks and have one on me:4C4716763M934291T.
Click to expand...
Click to collapse
Glad you're enjoying it! Thanks!

2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app

I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.

mletchworth said:
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
Click to expand...
Click to collapse
That is odd.. I flashed and reflashed and wiped then reflashed over and over to make sure I didn't have any more duds like R2 was and haven't had any issues with R4. Regardless, I'm glad you got it to flash.
Let me know if you have any other issues.

MrHyde03 said:
Let me know if you have any other issues.
Click to expand...
Click to collapse
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...

mletchworth said:
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
Click to expand...
Click to collapse
If you're restoring from the same version recovery the backup was created with, then you shouldn't have any issues. That's been my experience. I've always had things break if I restore with a different recovery.

Should you update the firmware to the new Canadian firmware found on samfirmware? It was released after the UK firmware and Canada is closer to the US but there are probably no differences... just asking

[ROM][LP] [5.1.1-r4][Unofficial] PACMAN rom [2015-07-04]

Hello everybody,
I've just compiled PACMAN-ROM for my new Z3C. Current version is PAC-LP MR1 Beta2.
Device trees are CyanogenMod's so probably all device specific CM-bugs will be there too.
The boot.img inside the zip contains CM 12.1 kernel and "Cyanogen Recovery" (no backup right now!).
For alternative recoveries/kernels scroll down to "TESTED - WORKING"...
If the rom is stable for daily use (as I hope) I'm gonna build newer version periodically (depending on PAC & CM updates).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDITS:
2015-07-09:
i've been trying to get rid of the latest problems, i.e. crashing android browser, opera browser, voice recorder and google apps (if installed). tried 4 or 5 builds in the meantime. i've got no idea why and not the skills to search in log files.
if anyone likes to test and find out, i uploaded version from july 4th.
2015-06-25:
New Version - updated CM & PAC sources. Some new PAC features there!
Version is PAC-LP MR1 Beta2 now. Unstable with crashes.
2015-05-24:
New Version - updated CM & PAC sources
2015-05-12/13:
New Version - updated CM & PAC sources
Volume bug on in-call got solved today!
2015-05-01:
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's!
http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Flash it before or after installing the PACROM zip. It contains the zip's
kernel + DualRecovery. Installing the rom zip will overwrite recovery again
so for backups it might be necessary
to flash it always before installing a new zip, e.g.
2015-04-29:
- Screenshots
- Yes! I got it running. After some hours of use, it seems really smooth & snappy. No reboots.
- How I installed everything: Root on Kitkat stock rom, backup TA-partition, install
Dual-recovery, update to Lollipop rooted, make nandroid backup of hole system,
unlock bootloader, flash PACMAN boot.img, wipe data/caches,
flash PACMAN zip + GAPPS ... quite some hours of work.
TESTED - WORKING:
- 2G, 3G, 4G
- wifi, wifi hotspot
- bluetooth audio
- nfc
- usb otg
- GAPPS (mentioned below)
- titanium backup
- PAC customizations (not all tested)
- video playback on youtube, vlc, mxplayer
- camera & video recording
- GPS using Google Maps
- headphone sound
- XZDR recovery (version 2.8.15 not working): http://nut.xperia-files.com/
- FOTA TWRP recovery (persistent in fota kernel partition): http://forum.xda-developers.com/z3-...12-nightly-t3010550/post58854063#post58854063
- M5 kernel (CM12.1 based): http://forum.xda-developers.com/z3-compact/orig-development/kernel-m5-kernel-t3115498
BUGS:
- phone call volume loud / not reducable in dialer app. (skype & whatsapp calls are alright) solved on 150512
- If alarm clock is set active -> reboot leads to normal shutdown -> deactivate alarm for that case
- photo: Little fish-eye effect on short distance (it's not that little actually)
NOT TESTED YET:
- encryption
Installation notes: Unlocked bootloader required
- flash boot.img (rashr on phone/ fastboot on pc), then boot into custom recovery
- wipe cache, wipe art/dalvik cache
- when coming from a different rom wipe data (factory reset)
- when changing between different gapps packages format system may be useful
- flash rom zip
- if needed flash gapps zip
Download PACMAN: https://www.androidfilehost.com/?w=files&flid=30581
Download GAPPS: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Device trees used: https://github.com/filou76/manifest/blob/master/z3c.xml
Credits!!!:
PACMAN project for their great and cool work!! www.pac-rom.com/#Home
All CM developers for giving a solid custom rom ground!!
All Z3C developers who are trying hard to make this great phone ready for daily use, especially those couple of root/bootloader/recovery hackers!! bilbao1 for the great howto root/backup etc! [NUT]'s for this very cool online kernel builder!
Google, of course

Screen shots please...

I guess its a cm based. So we need unlocked bl right?

shakkirk said:
Screen shots please...
Click to expand...
Click to collapse
It's the same as any Lollipop based PAC ROM, so just search the web for pics.
basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
Yes.

at least a custom rom for z3c. thanks man for your efforts...

basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
I think PAC is AOSP & CM based. Custom kernel. Unlocked bootloader, yes.

drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
Happy to build actually it's not that difficult with CM device support. Probably I'll build some monthly versions or so...

drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)

becks0r said:
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)
Click to expand...
Click to collapse
:good: In case of resurrection remix you only need to add/edit 1 file (local_manifest) to be able to compile a working rom. All the rest it just setting up ubuntu, init/sync repo an start building ...

Hmm it could be a reason to unlock bootloader.,)

XZDualRecovery
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's! http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Just flash it before or after installing the PACROM zip. It contains the original kernel + DualRecovery. CyanogenRecovery really sucks, not even a way to make backups. Now we can

does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!

beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
there's nothing like this included. as far as i know custom roms/ custom kernels can't handle drm keys from TA partition. not sure about flashable drm replacement, i don't think it will work, but maybe it does
perhaps someone knows more about this sony image processing stuff.
isn't that all software based? if so, i could imagine that a good camera app (FV-5 or something like) can bring the same results.

Great work mate. Been running a few hours with the updated boot.img
Hopefully there is no "memory leak"

beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
That fix is only useful on stock Sony based rom's.

bugs update
(1) i found a small, almost funny bug. couldn't reboot to recovery today because phone always ended with shutdown. i desperately flashed the boot.img again but no change. only after deactivating everything i thought not being active at installation the problem disappeared.
well, it's the active alarm, that i use every morning ...
(2) in call volume issue seem's to be somewhere hidden in android_device_sony_z3c/audio/mixer_paths.xml of the repo. just in case someone likes to search :laugh:

I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk

mrrflagg said:
I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
Hi, thank's for that! I've just reproduced what you wrote. On my phone this is also connected to active alarm clock. It's rebooting fine when alarm is off. So, quite the same as my last post.
I have no suggestion about real bug reports, because of 2 reasons: this is an unofficial build, primarily for myself ... but shared. I would stop building if Z3C would get official PAC support. And I've just started building roms 2 months ago. So, I'm not having the skills (yet) for advanced debugging. Right now it's more like being voluntary apprentice :laugh: ... I'm gonna add your input it into 1st post.
For now stability of this rom is mainly dependent on PACROM itself and official CM support.

Im glad you could reproduce the same bug. I think you have done a great job mate. I'm loving this ROM and appreciate your efforts. I'm trying to figure the dev side of things myself, not having much luck yet.
Sent from my Xperia Z3C using Tapatalk

Good job, m8!
Can someone post a picture, taken by camera on this phone with this rom ?
A picture of a door , or a wall, for example. Any picture featuring a rectangular shape with straight lines.
I had a broblem be4 on CM12 @z3c , the camera ( any camera app ) took pictures, distorting proportions, like there was a fisheye filter applied

Aosp 6.0 - e2303 / e2306

Really really thanks for the rom.
Will OTG work on this rom?
Thanks for your hard work as well.

Finally! Thank you for your hard work!!
I hope will be fixed some major things...!

newsony said:
Really really thanks for the rom.
Will OTG work on this rom?
Thanks for your hard work as well.
Click to expand...
Click to collapse
OTG will work
alby_var said:
Finally! Thank you for your hard work!!
I hope will be fixed some major things...!
Click to expand...
Click to collapse
I am working very hard, it's hard to make AOSP when Sony didn't release their vendor blobs

jeffreyvh said:
OTG will work
I am working very hard, it's hard to make AOSP when Sony didn't release their vendor blobs
Click to expand...
Click to collapse
So have you tried it , otg ?
Thanks for the great work.
I will flash and check it out tommorrow.

Thanks for releasing the rom . Would this rom possibly work on other firmwares and variants, and is adb force enabled? I'll test the rom when I get home in 3 hours

ardentis said:
Thanks for releasing the rom . Would this rom possibly work on other firmwares and variants, and is adb force enabled? I'll test the rom when I get home in 3 hours
Click to expand...
Click to collapse
It already boots, so force adb isn't needed anymore. And yes, I think it should work on other variants as well.
report it
Btw, flashing it on an other model isn't really tricky, if it doesn't work you can just unbrick

jeffreyvh said:
It already boots, so force adb isn't needed anymore. And yes, I think it should work on other variants as well.
report it
Btw, flashing it on an other model isn't really tricky, if it doesn't work you can just unbrick
Click to expand...
Click to collapse
Flashing is not the problem, but force enabling adb would be nice if there are problems with setup or touch

Good work as always! I will try it soon

Okay here's my report.
1) WiFi appears to work fine
2) Sound does not work
3) Camera does not work and neither does the camera button
4) Rotation does not work
5) Browser fails to download anything so I cant install apps
6) There is no file manager
7) Everything looks fine so far
Good work! But another thing is that I didnt realize that installing this rom would wipe my data. That would have been nice to know
Now when I go to TWRP to flash a new zip or restore a backup, it says there is no OS installed.
It seems that this isnt an issue anymore but it was weird.
Nope nevermind. Everytime it tries to boot up, I see the same boot screen as I saw with your rom. This is just getting weirder and weirder...
I figured it out Im totally fine. Sorry if I scared anyone during this adventure.

Screenshots
I've added a screenshot now

jeffreyvh said:
Features
- Pure AOSP (Stock Android, just like on the Nexus devices)
- No bloatware
- No extra features, just as clean as possible
What's Working
- Wi-Fi
- Boot
- Screen
- Vibration
What Isn't Working
- Everything else
Downloads
DOWNLOAD HERE
How To Install It
1. Be sure that the bootloader is unlocked and that you are on official firmware : 26.1.A.1.128 (Here is the ftf)!
2. Download the 3 files from the 6.0 release (e.g. "6.0-#1") the files you need are ( boot.img , system.img , userdata.img )
3. Download the Google SDK (fastboot, adb and etc)
4. Extract the zip in the same folder as the fastboot.exe (for example like this, C:/SDK/fastboot.exe | C:/SDK/system.img and etc)
5. Hold shift and right click somewhere in the folder (in an empty space)
6. Click open command prompt here...
7. Put the device in fastboot
8. Type "fastboot flash boot boot.img" and hit enter
9. Type "fastboot flash system system.img" and hit enter
10. Type "fastboot flash userdata userdata.img" and hit enter
11. Type "fastboot reboot" and hit enter
12. Enjoy it
Thanks To
Google - For Android
@jeffreyvh - That's me
Sony - For the source of the kernel and for the device
XDA:DevDB Information
AOSP 6.0 - E2303, ROM for the Sony Xperia M4 Aqua
Contributors
jeffreyvh
Source Code: http://github.com/AOSPERIA
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader, 26.1.A.1.128
Based On: AOSP
Version Information
Status: Testing
Created 2015-12-15
Last Updated 2015-12-16
Click to expand...
Click to collapse
I like that someone is work on a Rom. Not many for this device.

boho555 said:
I like that someone is work on a Rom. Not many for this device.
Click to expand...
Click to collapse
i tried on E2363 (26.1.B.2.129), it boots and then boot loops, it get to Android is starting, optimizing 1 of 64 and boot loops.
is it possible to create a 16Gb userdata.img (i think its 12213813248 bytes), just a request.

RohitBopnna said:
i tried on E2363 (26.1.B.2.129), it boots and then boot loops, it get to Android is starting, optimizing 1 of 64 and boot loops.
is it possible to create a 16Gb userdata.img (i think its 12213813248 bytes), just a request.
Click to expand...
Click to collapse
Hmm, probably the rom won't work on your model.
I can make a 16GB userdata, yeah.
But first let me fix the most bugs (Random reboots, Ril, Bluetooth)
After that I fixed those I will surely make a 16GB userdata.img
A new build should be up in max. 3 hours.
I don't know if I fixed stuff, but I tried it
I will update the op(First post) once my tester tested it.

ardentis said:
Okay here's my report.
1) WiFi appears to work fine
2) Sound does not work
3) Camera does not work and neither does the camera button
4) Rotation does not work
5) Browser fails to download anything so I cant install apps
6) There is no file manager
7) Everything looks fine so far
Good work! But another thing is that I didnt realize that installing this rom would wipe my data. That would have been nice to know
Now when I go to TWRP to flash a new zip or restore a backup, it says there is no OS installed.
It seems that this isnt an issue anymore but it was weird.
Nope nevermind. Everytime it tries to boot up, I see the same boot screen as I saw with your rom. This is just getting weirder and weirder...
I figured it out Im totally fine. Sorry if I scared anyone during this adventure.
Click to expand...
Click to collapse
The problem with the browser is caused by the permissions of Android 6.0

New build
The new build takes quite long, much longer then the previous ones.
But I am afraid that it's up within some hours (Max. 8, I think maybe next hour)
Anyone who wants to help testing,
Message me on Telegram : +31642056201
Message me on Hangouts : [email protected]
or Pm me (I don't like pm because you are not talking the way you do on the others)
Thanks for your support

work on e2333 dual???

Martia.Qa said:
work on e2333 dual???
Click to expand...
Click to collapse
Try it by yourself, it isn't too difficult to unbrick it

jeffreyvh said:
Hmm, probably the rom won't work on your model.
I can make a 16GB userdata, yeah.
But first let me fix the most bugs (Random reboots, Ril, Bluetoot
Click to expand...
Click to collapse
A 16gb userdata.img would be good for the 16gb devices. I'm not exactly sure but I think that the 8gb userdata.img limited my storage but unfortunately I can't fix it in TWRP. Diskinfo lists 16gb but Storage settings list only 8gb. Also do you mind if I text you over SMS and what timezone are you in?

ardentis said:
A 16gb userdata.img would be good for the 16gb devices. I'm not exactly sure but I think that the 8gb userdata.img limited my storage but unfortunately I can't fix it in TWRP. Diskinfo lists 16gb but Storage settings list only 8gb. Also do you mind if I text you over SMS and what timezone are you in?
Click to expand...
Click to collapse
I need to pay for sms, so I'd rather like to use whatsapp or telegram.
Ps, what theme are you using. I'm loving it

Flyme7.8.7R For the Leeco X720 and X727

(7.1) Flyme7. Fingerprint infrared V3 For the Leeco X720 and X727 ( Updated on 9/5/2018 )
AKA: The newest version of Flyme Original Chinese Name : 7to-X720.flyme7.指纹红外V3.zip
Developer: Cold and Ruthless
Original Link: http://rom.7to.cn/romdetail/1030273
Link: https://mega.nz/#F!xYJgXYxK
Key: !QNUTt-aMXA-Kvl39hOMp9A
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flyme:
LeTV pro3 transplant Flyme7.8.21R V3
Redesigned interface, better overall experience
Advanced settings root card brush package
Optimized sound
Author: Cold ruthless
Release Date: 2018-09-04
Android version: 7.1.x
UI type: Flyme ROM
Size: 1270.00MB
Experience the new interface, with advanced settings, high speed, theming options, and excellent call and sound quality, all are hallmarks of the Meizu Official Experience
Applicable models: LeEco LEX720, LEX727
Optimization of the optimized
volume of the bottom package update sound.
Temperature control based on port from: Charm Blue Note 6 Build
Double Wipe> reboot to Recovery, if you have an error you may need to format storage
The first boot is very slow, please wait for the Meizu official latest experience version transplant
Past Bluetooth issue resolved.
Optimization scheduling
New interface new experience, advanced settings and optimization
Installation Notes:
First Boot may be slow, so if it takes a while for the first system boot, the solution is just to wait longer.
Flyme Account http://forum.flymeos.com/
Create an Official Flyme account if you want to gain access to tons of addons.
Meizu is Port friendly and Flyme Account Provides:
Forum advice
Plugins,
Apps,
3rd party themes etc.
Download Flyme 7 Launcher, Stock Wallpapers, and Apps (Flyme 7 stock APK)
https://www.androidsage.com/2018/05/15/download-flyme-7-launcher-stock-wallpapers-apps-apk/
As always, flash anything under your own discretion
Root
This Rom comes with Magisk root, You can easily flash Magisk 17.1 overtop after setting up the system and then rebooting to recovery.
Gapps: I am using BeansGapps-Mini-7.1.x-20170725.zip
Helpful files:
https://mega.nz/#F!JMYSSCLQ
Key: !xgQFTB69PE-hL8RTUbpUIw
Firmware
https://mega.nz/#F!oAZ3yC4b!
Key: MDwbHXNTRdrpgMvQ42yviw
If you have safetynet issues, follow the steps below
Extract the boot.img file from the rom, and placed the boot image into storage.
Open Magisk and use install to Patch Magisk to the boot.img.
Reboot to recovery, install the patched boot.img to boot
Flash addonsu-15.1-arm-signed.zip, and then reflash Magisk again, from storage then use advanced options to clear cache, and then reboot to system.
With these steps you will always Pass Safetynet and be playstore certified
https://forum.xda-developers.com/showpost.php?p=77367331&postcount=4790
Build Prop Recommendations
After the installation and initial testing period,. you may decide to continuing using Flyme for a while:
If so you can further optimise the ROM with these build prop and edits posted below.
First backup your existing buildprop
* ro.product.locale.language = en ( or your language)
* ro.product.locale.region = IN or your country
* persist.sys.timezone = your country ( see proper entry here: https://gist.github.com/arpit/1035596)
* persist.sys.meizu.region =
or use persist.sys.oem.region= your country google correct acronym for your country

Reserved for future hints

Thanks I will try and feedback

i get error code 3 when i try to flash

rob_z11 said:
i get error code 3 when i try to flash
Click to expand...
Click to collapse
Me Too!
Yes, I tried it and the same thing happened to me, it must be a corrupt download because people are giving the release a 8.3/10. I found a slightly older but highly rated rogue pig version. ( see same link above)
I installed it successfully and must say, it's actually extremely good.
Corruption
The original newer file is probably just corrupted so I am going to try redownloading it. Until then, check out the other version that I placed in the same megadrive folder see the link above. Yes, it's a little older but its actually awesome!
I just attempted to find the newer rom by cold ruthless on the BBS website, has he been banned. I had a bookmark saved and when I click I get this message " Authors are banned or deleted automatically blocked" Not sure if its the same person or not, if this next download is corrupt. I would still recommend flyme_LEX720_rogue_6.8.3.17R-beta, I am testing it right now and like it alot.

Does Android Pay work with this ROM?

I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach

3llawi said:
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
Click to expand...
Click to collapse
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..

3llawi said:
I flashed the ROM after the boot I face a black screen and a bar with Chinese written and I can't do anything only control the volume...I only flash the ROM with wipe the data,system and delvic cach
Click to expand...
Click to collapse
It looks like what happened to me when going from an Oreo rom to Nougat, you have to format data not only wipe data. Format data, write "yes" and then install the rom. Always have a backup of your data before.

flyme is one of the best system , the official one is good but it's old , be sure to have eui firmware before flashing flyme .

rob_z11 said:
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
Click to expand...
Click to collapse
Please can you put the link of old recovery version

rob_z11 said:
No issue like this. Everything worked. It booted fine. You may have to use the recovery version from earlier in the month of Jan.
Everything worked for me except volte which is no big deal. Really impressive build. Thanks for downloading @tsongming..
Click to expand...
Click to collapse
Did you format internal storage?

3llawi said:
Did you format internal storage?
Click to expand...
Click to collapse
No because I have always been on miui10

can some1 link me the gapps?

collisiion said:
can some1 link me the gapps?
Click to expand...
Click to collapse
Look at the post #1

Thanks to troubleshooting from @ rob_z11, I plan to post a working version of the Cold Ruthless file late tonight EST.

andrew2401 said:
Does Android Pay work with this ROM?
Click to expand...
Click to collapse
I believe so, though I haven't tried it yet. I will let you know late tonight

tsongming said:
I believe so, though I haven't tried it yet. I will let you know late tonight
Click to expand...
Click to collapse
Okay thank you how's the battery so far?; I've owned Meizu phones and there is was always good for battery optimization

tsongming said:
Thanks to troubleshooting from @ rob_z11, I plan to post a working version of the Cold Ruthless file late tonight EST.
Click to expand...
Click to collapse
Ok, this is what I have found. Your original latest flyme seems to be working ok. Here is what I have done. Using RAR apk, I unzipped it, and it complained about one apk in mizu-apk folder, and I ended up removing that folder completely, and zipped the ROM again. It flashed without any issue, but I can't seem to get Data to turn-on. It turns on briefly during the boot, but it goes away. I think if I compare the build.prop from older version with newer version, I may be able to find the fix.

andrew2401 said:
Okay thank you how's the battery so far?; I've owned Meizu phones and there is was always good for battery optimization
Click to expand...
Click to collapse
Extremely good, at the moment my phone has no OS at all..
I only glanced at battery life briefly yesterday with Gsam battery tool. Plus, I installed BlackScreen 5.3 r2 which worked fine, I would rather wait for a real answer. Otherwise it would just be a guess.

Better Mobile App

welcome